Identity, registration and scheduling · C0553
Does AuroraMed support unknown-patient (Doe) registration with temporary identity, later merge to a real identity, and full reversal (unmerge)?
In the pilot (v0.2.0, synthetic data)
Short answer
The system must support unknown-patient (Doe) registration with temporary identity, later merge to a real identity, and full reversal (unmerge). That is REQ-0206, a top-priority requirement for all three tiers. The pilot covers part of this. The rest is designed, not built. Where the code stands: Unknown-patient registration and two-person MERGE (virtual, unmerge supported); no ADT A40/A37 or FHIR Linkage emission. Test in the specification: merge then unmerge restores both records byte-identical in content; audit shows both.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-0206
- 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
- Does AuroraMed support two-identifier verification prompts at registration, order entry, specimen collection, medication administration and transfusion? Designed
- Who has to approve a patient merge or unmerge, and does it notify other systems? Pilot
- Does AuroraMed support name history: legal, chosen, previous, alias, with pronouns and display rules? Pilot
- How does AuroraMed find duplicate patients, and can the matching weights be tuned? Pilot
See it in context: Patient identity and master patient index · Search the help center · Ask a question