Identity, registration and scheduling · C0562
Does AuroraMed capture patient photos with consent, strip metadata, and use them only for identity verification per policy?
Designed, not yet built
Short answer
The patient identity and master patient index part of the specification (REQ-0215) says the system must capture patient photos with consent, strip metadata, and use them only for identity verification per policy. Designed, not built: there is no code for this in the pilot. Acceptance check: photo capture requires consent flag; EXIF removed.
This is designed, not built.
- Specification item
- REQ-0215
- 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 registration alerts and flags (infection, behavioral, safety) with expiry and review dates? Designed
- Does AuroraMed optionally support biometric identification (palm-vein, fingerprint, iris) as an opt-in per jurisdiction profile, storing templates only? Designed
- Does AuroraMed provide a duplicate-record worklist and overlay/overlap resolution tools for HIM? Designed
- Does AuroraMed support VIP/restricted/confidential patient flags with hidden-flag option and access requirement of relationship or break-glass? Pilot
See it in context: Patient identity and master patient index · Search the help center · Ask a question