Identity, registration and scheduling · C0555
Does AuroraMed support name history: legal, chosen, previous, alias, with pronouns and display rules?
In the pilot (v0.2.0, synthetic data)
Short answer
REQ-0208 is a top-priority requirement for all three tiers: the system must support name history: legal, chosen, previous, alias, with pronouns and display rules. The pilot covers part of this. The rest is designed, not built. What v0.2.0 does today: Preferred name/name fields, data-quality tab, visits (AMB/IMP/EMER), edit history stores field names only with values encrypted; not the full spec model. To verify it, the specification says chosen name appears on banner and wristband per site policy while legal name is retained for billing.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-0208
- 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
- Who has to approve a patient merge or unmerge, and does it notify other systems? 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 record race, ethnicity and language with multi-select, declined option and interpreter need? Designed
- Does AuroraMed support unknown-patient (Doe) registration with temporary identity, later merge to a real identity, and full reversal (unmerge)? Pilot
See it in context: Patient identity and master patient index · Search the help center · Ask a question