Identity, registration and scheduling · C0554
Who has to approve a patient merge or unmerge, and does it notify other systems?
In the pilot (v0.2.0, synthetic data)
Short answer
The pilot covers part of this. The rest is designed, not built. In the pilot: Unknown-patient registration and two-person MERGE (virtual, unmerge supported); no ADT A40/A37 or FHIR Linkage emission. REQ-0207 says merge and unmerge must require two-person approval and must emit ADT A40/A37 (or FHIR Linkage/Patient replaced-by) to interfaces. Its acceptance check: single-person merge attempt is blocked; downstream systems receive the event.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-0207
- Specification priority
- P1 (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 unknown-patient (Doe) registration with temporary identity, later merge to a real identity, and full reversal (unmerge)? Pilot
- Does AuroraMed support name history: legal, chosen, previous, alias, with pronouns and display rules? Pilot
- Does AuroraMed record sex and gender data as separate fields (administrative sex, sex for clinical use, gender identity, sexual orientation) with a declined option? Designed
- Does AuroraMed support two-identifier verification prompts at registration, order entry, specimen collection, medication administration and transfusion? Designed
See it in context: Patient identity and master patient index · Search the help center · Ask a question