The unique identifier assigned by the provider to reference a single patient
Submitted By: Robert C Dieterle
/ On behalf of the Da Vinci Project
Data Element Information
Use Case Description(s)
Use Case Description
The capture and exchange of Medical Record Numbers (MRNs) with all clinical and administrative transaction will help to eliminate issues with patient matching by allowing the recipient of the transaction to capture the number and the assigner to ensure that future exchange can be on a deterministic basis and not rely on a probabilistic match base on patient demographic.
Estimated number of stakeholders capturing, accessing using or exchanging
All providers assign unique identifiers to their patients. EHRs capture (or assign) these unique identifiers. Other providers, payers, and suppliers use the MRN, when available, to identify the unique patient with respect to the assigning provider. This will include >7,000 hospitals and > 50,000 ambulatory facilities that assign individual MRNs. This will be used by all payers (>1,800), clinical laboratories (>260,000) and by patients (>350 Million)
Improving patient experience of care (quality and/or satisfaction)
Reducing the cost of care
Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Structural standards exist for the capture and exchange of MRNs and are part of all EHRs and standard transaction. However, there is no global assignment of an identifier to an individual patient.
All exchange standards that support individual patient identification support MRNs.
In FHIR R 4.0.1 the Patient resource provides for inclusion of a MRN and its ‘system’ in the Patient.identifer element
This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
Number of organizations/individuals with which this data element has been electronically exchanged
5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Restrictions on Standardization (e.g. proprietary code)
Restrictions on Use (e.g. licensing, user fees)
Privacy and Security Concerns
This data, like any patient data should be exchanged securely. Current processes exist, governed by CMS and ONC, to securely transfer this data.
Estimate of Overall Burden
Since all EHRs capture the MRN and all relevant transactions support the inclusion of the MRN, there should be limited effort to capture, use and exchange MRNs