Peru: Ley 29733 and adapters

C0090Which Peruvian data law applies?

Ley 29733 and its regulation, DS 016-2024-JUS, are the reference. The design maps consent, registration, security measures and ARCO rights. Article-level mapping still needs verification by counsel.

C0091What are ARCO rights?

Access, rectification, cancellation and opposition. The design implements request workflows for each, with legal retention limits explained to the patient.

C0092Does AuroraMed connect to Peruvian health systems?

Adapters for SIS, SETI, RENIPRESS, ICD-10 coding and DNI identifiers are named in the design as signed plug-ins. None is built or live.

C0093Is DNI validated at registration?

National identifier validators are designed but not built. The pilot uses a clinic-prefixed medical record number with a check digit and no national-ID validators.

C0094Can a Peruvian clinic operate with weak internet?

The design is local-first: the on-site server keeps care running when the link drops. The pilot is cloud-only and stops alerts and messaging without connectivity.

C0095Does AuroraMed have approval from Peruvian health authorities?

No. No registration, licence or approval from any Peruvian authority is claimed. Regulatory steps are open.

C0096Are Peruvian hospital reports supported?

A reference catalog lists Peruvian reports and registries from MINSA, SUSALUD, DIGEMID, EsSalud and SIS. They guide design. No report is produced by the pilot.

C0097Will there be Spanish screens for Peruvian staff?

Spanish is a target locale in the specification. The pilot interface is English only, and Spanish pages on this site are a preview of the marketing content, not product support.

C0098Does Peruvian law restrict moving data abroad?

Cross-border flow rules are marked for verification. The design defaults to no cross-border replication.

C0099How is Peruvian consent captured?

The design requires express, informed and prior consent for sensitive data, with language and format set by the Peru profile.