Data related to an individual’s insurance coverage for healthcare.

Data Element
Medicare Patient Identifier
Description

Medicare Beneficiary Identifiers (MBI) used to uniquely identify Medicare patients.
Submitted By: Joel Andress / Centers for Medicare and Medicaid Services (CMS) Center for Clinical Standards and Quality (CCSQ)
Data Element Information
Data Element Description Medicare Beneficiary Identifiers (MBI) used to uniquely identify Medicare patients.
Use Case Description(s)
Use Case Description Medicare beneficiary identifiers (MBI) are a standard patient identifier for Medicare patients across the United States. These patient identifiers are submitted with patient-level data to CMS for quality measure reporting, both for eCQMs and for claims-based measures.

Although an all-payer unique identifier is not yet available, Medicare beneficiary identifiers are fully standardized and available and assist with patient identification and matching, which is a good first step for patient identification.
Estimate the breadth of applicability of the use case(s) for this data element All Medicare beneficiaries have an MBI and all 4,000+ hospitals and providers reporting measure data to CMS currently have access to and are required to report this patient identification information.
Link to use case project page https://www.cms.gov/Medicare/New-Medicare-Card
Use Case Description For providers responsible for the care of a patient population, the ability to transfer and share information from encounters with their Medicare beneficiaries from providers outside of their network supports optimal quality of care.
Estimate the breadth of applicability of the use case(s) for this data element Hospital and outpatient providers participating in alternative payment models for Medicare beneficiaries, which is a growing stakeholder group.
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) MBI format specifications: https://www.cms.gov/Medicare/New-Medicare-Card/Understanding-the-MBI.pdf
HL7 Identifier type value set, see MC (http://hl7.org/fhir/R4/v2/0203/index.html)

https://www.cms.gov/Medicare/New-Medicare-Card/Understanding-the-MBI.pdf
Additional Specifications HL7 FHIR US Core Implementation Guide STU3 based on FHIR R4, Patient Profile require a Patient ID. This profile already required to exchange other patient demographic information included in USCDI v1: https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-patient.html
Current Use This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
Supporting Artifacts Patient Medicare identifiers routinely captured in EHR systems, claims data and is used by hospitals, providers, and other healthcare stakeholders for submission to CMS for quality measurement reporting.
Widely available in EHR systems to support Patient FHIR resource:
https://fhir.cerner.com/millennium/r4/individuals/patient/
https://fhir.epic.com/Specifications?api=932
https://developer.allscripts.com/FHIR?PageTitle=Resources
https://www.cms.gov/Medicare/Quality-Initiatives-Patient-Assessment-Instruments/MMS/Quality-Programs
https://ecqi.healthit.gov/ecqms

https://www.cms.gov/Medicare/Quality-Initiatives-Patient-Assessment-Instruments/MMS/Quality-Programs
Extent of exchange 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Supporting Artifacts Medicare patient IDs electronically exchanged with CMS for quality measure reporting via QRDA files and other electronic exchange platforms; required as part of submission for Medicare beneficiaries included in the measures.
Provider-payer data exchange and member-mediated information exchange are also occurring, and include FHIR Patient profile with a patient ID, being testing in HL7 Connectathons.
https://ecqi.healthit.gov/qrda
https://build.fhir.org/ig/HL7/davinci-ehrx/profiles.html

https://ecqi.healthit.gov/qrda
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) Standard patient IDs only available for Medicare beneficiaries; no unique identifier for all-payer patients.
Restrictions on Use (e.g. licensing, user fees) N/A
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. MBI is a unique randomly generated ID with “non-intelligent” characteristics, which replaced the HIC Number, based on SSN.
Estimate of Overall Burden No/low burden anticipated, as Medicare identifiers already in wide use among stakeholders caring for Medicare beneficiaries. Patient FHIR US Core profile also required by the US Core Capability Statement and required for exchange of other patient demographic data included in USCDI version 1; a patient ID is required for inclusion in this profile. Therefore, all stakeholders complying with ONC CEHRT requirements will have ID data ready for exchange in standards.
Other Implementation Challenges N/A
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 2 - Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Criterion #3
Maturity - Current Exchange		 Level 2 - Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 0 - Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.
Evaluation Comment This data element represents a specific type of an existing USCDI data elements Member Identifier in the Health Insurance Information data class.

Comment

Submitted by minigrrl on

What is the justification…

What is the justification for the demotion of the following Case Reporting data elements in USCDI, specifically:

• Exposure/Contact Information: Exposure/Contact Agent
• Exposure/Contact Information: Exposure/Contact Date
• Exposure/Contact Information: Exposure/Contact Direction
• Exposure/Contact Information: Exposure/Contact Source/Target Participant
• Exposure/Contact Information: Exposure/Contact Type
• Health Insurance Information: Medicare Patient Identifier
• Immunizations: Vaccination Administration Date
• Laboratory: Specimen Collection Date/Time
• Patient Demographics/Information: Patient Birth Place
• Patient Demographics/Information: Tribal Enrollment
• Pregnancy Information: Estimated Date of Delivery
• Pregnancy Information: Gestational Age
• Pregnancy Information: Last Menstrual Period (LMP)
• Provenance: Unique Identifier
• Social Determinants of Health: Housing Instability and Homelessness
• Social History: Congregate Living
• Work Information: Employment Status
• Work Information: Job Employer Address
• Work Information: Job Employer Name
• Work Information: Usual Industry
• Work Information: Usual Occupation

Currently, 21 certified EHR products exchange these elements using electronic Case Reporting (eCR) specifications demonstrating real-world adoption that typically supports promotion, not demotion, within the USCDI maturity model.

Collectively, these elements provide clinical, demographic, occupational, social, and epidemiological context essential to disease investigation and outbreak response for nationally notifiable conditions.

We urge ONC to either reverse this decision or publish a detailed, evidence-based rationale.

Submitted by BLampkins_CSTE on

Medicare Patient Identifier - CSTE Comment

This is one type of patient identifier and there are others which could all be subsumed under Patient Identifier, Patient Identifier type and Patient Identifier Assigning Authority.

Submitted by rdillaire on

CMS-CCSQ Supports Medicare Patient Identifier for USCDI v6

Recommendation 1: CMS CCSQ recommends advancing the Medicare Patient Identifier element to Level 2 and inclusion of the Coverage Period, Group Name, Payer Name, Plan Name, and Medicare Patient Identifier data elements in final USCDI v6.

Rationale: Inclusion of these common health insurance data elements for nationwide interoperability is essential for such use cases as value-based care, including affordability for lower-income individuals, and enabling patients to determine costs and affordability up front. This Health Insurance Information data class is associated with the overall primary and secondary coverage for the individual. In some cases, it may be different from the benefit used for a particular encounter or claim (e.g., worker's comp benefits). While these data elements are already included in the latest Fast Healthcare Interoperability Resources (FHIR) US Core and Consolidated Clinical Document Architecture (CDA) implementation guides (IGs) referenced in the Health, Data, Technology, and Interoperability-1 Final Rules (HTI-1), the implementation community can benefit from more clarity on how to consistently populate these fields—in particular Payer Name and Group Name—as there is variation between what a typical insurance card shows versus what is best used on real-time eligibility (RTE) queries with health plans.

 

Recommendation 2: CMS CCSQ recommends renaming and aligning Medicare Patient Identifier (MPI) with CMS’s naming and use of Medicare Beneficiary Identifier (MBI).

Submitted by BLampkins_CSTE on

CSTE Comment - v6

CSTE supports inclusion of this data element in USCDI V6. Please see previously submitted CSTE comments for additional recommendations.

Submitted by BLampkins_CSTE on

CSTE Comment - v5

This is one type of patient identifier and there are others which could all be subsumed under Patient Identifier, Patient Identifier type and Patient Identifier Assigning Authority.

Submitted by CDC_DSMH_WG on

CDC's Comment for draft USCDI v5

CDC supports the inclusion of this data element in USCDI v5 as it is an element that may be necessary for calculation of our digital quality metrics from FHIR data.

Submitted by CDC_DSMH_WG on

CDC's Consolidated Comment for USCDI v4

  • CDC continues to support inclusion of this data element in USCDIv5.
  • NAACCR Comment:  This data element will be helpful for linkages for public health use and is part of NAACCR standard.

Submitted by CDC_DSMH_WG on

Unified Comment from CDC

  • NOTE - This comment supports the promotion of the Data Class Patient Demographics - Data Element Identifier to USCDI V3 as well as the additional Data Element of Identifier System, including the allowance of multiple instances of Identifier/ Identifier System per patient. We believe that this will allow needed flexibility to accommodate use and exchange of the variety of patient identifiers in current use in the US. An example of this approaches is: Identifier: 1A10B23CD45, Identifier System: http://hl7.org/fhir/sid/us-mbi. If ONC does not choose to incorporate this approach (Identifier + Identifier System) in USCDI V3, we recommend allowing for the following Patient Demographic Data Class Data Elements in USCDI V3: Medicare Patient Identifier, Medical Record Number and Social Security Number.
     
  • General Comment: We suggest changing this data element name from Medicare Patient Identifier to Medicare Beneficiary Identifier because that is what CMS and the Social Security Administration, as well as many health care industry stakeholders call it. (see: https://www.cms.gov/Medicare/New-Medicare-Card)
     
  • Additional Use Cases: The MedMorph Public Health Use Cases of Health Care Surveys and Cancer Registry Reporting are use cases that use Medicare Patient Identifier as an important patient identifier for internal registry and external to registry linking and patient or registrant identification or matching purposes. Links to Use Case Project Pages: https://www.cdc.gov/csels/phio/making-ehr-data-more-available.html, https://www.cdc.gov/nchs/dhcs/nhcs_registry_landing.htm, https://www.cdc.gov/cancer/npcr/
     
  • Additional Applicable Standards: HL7 CDA ® Release 2 Implementation Guide: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, Release 1, DSTU Release 1.1 – US Realm: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=398.
     
  • HL7 CDA® R2 Implementation Guide: National Health Care Surveys (NHCS), R1 STU Release 3 - US Realm: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=385
     
  • HL7 FHIR® US Core Implementation Guide STU3 Release 3.1.1: https://www.hl7.org/fhir/us/core/index.html
     
  • CSTE supports inclusion of this measure into USCDI v3

Submitted by JAndress316 on

Response to Comment on Medicare Patient Identifier

Specific Identifier(s) or general Identifier?
MedMorph supports the addition of Medicare Patient Identifier (level 2), but is concerned with having a general Identifier element (level 2) as well as Medical Record Number (Level 1) and Patient Social Security Number (level 1). What is the intention of Identifier - is it a placeholder for a national identifier of some sort for a patient?  We recommend that USCDI either take a general approach with Identifier Type, Identifier System, and Identifier Value OR be specific with Medical Record Number, Medicare Patient Identifier and Social Security Number elements (and remove the Identifier element).

CMS's intent with the Medicare Patient Identifier data element submission was to specifically recommend inclusion of the Medicare Beneficiary Identifier (MBI) for Medicare beneficiaries, as this ID is currently well defined and captured. 

Log in or register to post comments

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB