Identity, registration and scheduling · C0592
Does AuroraMed audit all registration edits with old/new values encrypted?
In the pilot (v0.2.0, synthetic data)
Short answer
The system must audit all registration edits with old/new values encrypted. That is REQ-0320, a top-priority requirement for all three tiers. 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. Test in the specification: audit shows field, actor, time; values decrypt only under privacy officer step-up.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-0320
- 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 patient transport requests and tracking inside the facility? Designed
- Does AuroraMed run front-end claim edits at registration? Designed
- Does AuroraMed support Brazil SUS registration data (AIH/BPA), CNS lookup and CADSUS integration and equivalent country adapters? Designed
- Does AuroraMed support visitor management and visit restrictions? Designed
See it in context: Registration, ADT, bed management and patient access · Search the help center · Ask a question