Patient Identity Record
The master patient index record containing verified identity attributes including demographics, identifiers, and linkages across medical record numbers.
Why This Object Matters for AI
AI duplicate detection requires standardized identity data to match patients; without consistent identity records, AI cannot accurately identify duplicates.
Health Information Management & Medical Records Capacity Profile
Typical CMC levels for health information management & medical records in Healthcare organizations.
CMC Dimension Scenarios
What each CMC level looks like specifically for Patient Identity Record. Baseline level is highlighted.
Patient identity is not formally managed. Each department creates its own patient record when someone shows up. The same patient might be 'John Smith' in the ED, 'Jonathan Smith' in radiology, and 'J. Smith' in the lab — with three different medical record numbers. There is no master patient index and no concept of a unified patient identity.
None — AI cannot link records across systems or provide a unified patient view because no formal patient identity management exists.
Implement a master patient index (MPI) — create a centralized patient identity record that assigns a unique identifier and links all registrations, encounters, and records for the same individual.
A master patient index exists but identity management is inconsistent. Duplicate records are common — some patients have two or three MRNs because registration entered them as new patients at different visits. Name variations, typos, and missing demographics create identity ambiguity. The MPI is a list of registrations, not a source of verified identity.
AI could flag potential duplicates based on demographic matching, but false positive rates are high because the identity records lack verified attributes. Merging duplicates requires manual chart review.
Standardize patient identity verification — implement consistent identity proofing at registration (photo ID, insurance card, date of birth verification) and enforce data quality rules for demographic fields in the MPI.
Patient identity records follow standardized verification practices. Registration staff verify identity with photo ID and insurance documentation. Demographic fields follow data quality rules (name format, address validation, phone number format). Duplicate detection runs at registration. The MPI contains verified identity attributes, though historical duplicates still exist in the system.
AI can perform reliable duplicate detection at registration using verified demographics. Can flag high-probability duplicate records for review. Can generate patient identity quality reports. Cannot resolve identity across external organizations because the MPI only covers internal records.
Link patient identity to cross-organizational identity sources — integrate the MPI with health information exchanges, insurance identity services, and referral management systems to create a patient identity that spans organizational boundaries.
Patient identity records are linked across organizational boundaries. The MPI integrates with health information exchange identity services, insurance member matching, and referring provider patient records. A patient presenting at the ED can be matched to their records at other facilities through cross-organizational identity linkage. Identity is a network, not a local attribute.
AI can resolve patient identity across organizations — matching patients to their records at external facilities, insurance records, and referring providers. Can build comprehensive patient profiles from cross-organizational identity linkage.
Implement formal patient identity schemas with entity relationships — model identity as a structured entity with typed relationships to verified identity documents, biometric data, insurance member records, and cross-organizational linkages.
Patient identity records are schema-driven with full entity relationships. Each identity links to verified identity documents, biometric data (if captured), insurance member records, cross-organizational linkages, and a confidence score for each match. An AI agent can evaluate patient identity with high confidence by traversing the complete identity relationship graph.
AI can perform autonomous patient identity management — high-confidence matching at registration, cross-organizational record linking, and proactive duplicate detection and resolution. Identity decisions for routine scenarios are fully automated.
Implement real-time identity event streaming — publish every identity creation, merge, link, and verification as a real-time event, enabling continuous identity quality monitoring across all connected systems.
Patient identity records are real-time identity intelligence streams. Every registration, verification, cross-organizational match, and identity update flows in real-time. The patient identity record is a living entity that continuously refines itself as new evidence arrives — biometric verification, insurance confirmation, cross-facility matching. Identity is always current, verified, and linked.
Can autonomously manage patient identity in real-time — matching, linking, verifying, and maintaining identity records across all organizational and cross-organizational systems as a continuous identity intelligence engine.
Ceiling of the CMC framework for this dimension.
Capabilities That Depend on Patient Identity Record
Other Objects in Health Information Management & Medical Records
Related business objects in the same function area.
Medical Record Document
EntityThe discrete document within a patient's record including notes, reports, consents, and external records with associated metadata, authorship, and completion status.
Release of Information Request
EntityThe formal request for patient records from external parties including authorization, requested records, date ranges, and fulfillment status.
Clinical Documentation Query
EntityThe CDI specialist's request to a physician for documentation clarification including the specific question, clinical indicators, and physician response.
EHR Access Log
EntityThe audit trail of who accessed which patient records, when, from where, and what actions were taken within the electronic health record system.
Patient Consent Record
EntityThe documented patient authorization for treatment, procedures, research participation, or information sharing including signature, date, and expiration.
Data Quality Metric
EntityThe measured assessment of EHR data completeness, accuracy, and consistency for specific data elements, departments, or documentation types.
What Can Your Organization Deploy?
Enter your context profile or request an assessment to see which capabilities your infrastructure supports.