AuroraMed v0.2.0 is a synthetic-data pilot. See exactly what's built →

Privacy

Your rights over your health record, and how the design supports them

This page describes the design. The pilot has no patient portal and no request workflow, holds only synthetic data, and makes no claim of legal compliance.

How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration

How a patient request is designed to flowA patient proves identity, signs a consent request, the request is fulfilled through the consent flow, and the access is recorded in the audit trail that the patient can later see.Patient provesidentitySigns a request(consent, hashed text)Fulfilment throughthe consent flowAccess recorded inaudit; patient can see itIn the pilotDesigned, not builtSimulatedDecision / caution

Diagram: designed, not built.

RightDesign approachStatus
Access to your recordPatient-initiated request with identity verification, fulfilled through the consent flow; access history shown from auditDesigned, not yet built
CorrectionCorrections are appended amendments; the original stays for legal retentionDesigned, not yet built
Restriction and consentConsent captured per purpose, data category and recipient, with the exact rendered text hashed and signed, revocable; revocation affects future access onlyDesigned, not yet built
PortabilityStructured export in standard formats; export tooling not builtDesigned, not yet built
Deletion where law allowsDestroy the keys (crypto-shredding), write a tombstone, propagate to replicas and backups; retention duties may require keeping data; legal opinion pendingDesigned, not yet built
Who accessed my recordA patient-facing accounting of disclosures and access history; the pilot has this for privacy staff onlyDesigned, not yet built
Speed of a records requestA design goal to cut the 72-hour norm through consent-based fulfilment. Never measured, never promised. Legal review steps are not compressedDesigned, not yet built

What exists in the pilot

Privacy staff can produce a per-patient access report and a disclosure log; sensitive patients can be flagged VIP or restricted; national IDs are masked with audited reveal; break-glass access is reviewed. Patients themselves cannot use the pilot.

Country specifics

Laws differ. Preview pages for Peru, Mexico, Colombia, Chile, Argentina and Brazil name the laws the design considers, with no compliance claim. Whether an approach satisfies a given law needs advice from counsel in that country.

Questions about your own data? Write to [email protected]. This site holds no patient records.

Privacy questions?

The help center has a section on patient rights.

See the synthetic-data demo first.Request a demo