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

Identity, registration and scheduling · C0548

Does AuroraMed create a patient record with a unique internal identifier, never derived from a national identifier?

In the pilot (v0.2.0, synthetic data)

Short answer

It is one of the few requirements the pilot meets at MVP scope; nothing has touched real data. Pilot detail: Internal UUID + per-clinic MRN (Luhn); SSN masked by default, reveal needs a purpose and is audited. REQ-0201 says the system must create a patient record with a unique internal identifier, never derived from a national identifier. Its acceptance check: two patients with the same CPF/SSN receive different internal ids; no key or ledger field equals a national id.

This exists in the synthetic-data pilot only.

Specification item
REQ-0201
Specification priority
P0 (of P0 to P3)
Tiers
Small, Medium, Large

Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.

Related answers

See it in context: Patient identity and master patient index · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo