Official Website of the Office of the National Coordinator for Health Information Technology
Data used to categorize individuals for identification, records matching, and other purposes.
Data Element |
||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Identifier
Description
An identifier for the patient |
||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||
Submitted by jessilott on
TDH-OIA supports the inclusion of the Patient Identifier data element in v7. TDH-OIA also recommends that ASTP/ONC consider explicitly including the identifiers "type" and "source/assigning authority" as part of this data element. These attributes are critical for distinguishing among multiple identifiers, ensuring correct interpretation, and supporting consistent interoperability across systems.
Submitted by rdillaire on
CMS CCSQ supports the inclusion of Patient Identifier in USCDI v7.
Submitted by CDC_DSMH_WG on
CDC supports the inclusion of Patient Identifier in USCDI v7 and the element being added to Patient Demographics/Information. Patient identifier is an important component for related person in a birth event and is used in Health IT standards to properly identify both the mother and baby. During labor and delivery, the mother’s medical record is created or actively available, and after delivery of baby a new patient record is created. For mother and newborn relationships, a patient identifier would support these relationships among electronic medical records, as well as a linkage with birth registration systems. An identifier such as the medical record number for both the mother and infant is also captured within the facility worksheet for live birth certificate.
Sources: RelatedPerson - FHIR v6.0.0-ballot4 (https://build.fhir.org/relatedperson.html); Facility Worksheet for the Live Birth Certificate (https://www.cdc.gov/nchs/data/dvs/facility-worksheet-2016-508.pdf)
Submitted by CDC_DSMH_WG on
a. In addition to producing restricted use data files that link the National Hospital Care Surveys and National Ambulatory Medical Care Survey (NAMCS) to other federal data sources (e.g. National Death Index, the U.S. Department of Housing and Urban Development, etc.), we’ve also published example projects to demonstrate the utility of these linked files. For example, please find the National Health Statistics Report Number 201 “National Hospital Care Survey Demonstration Projects: Examination of Maternal Health Outcomes by Housing Assistance Status” at https://www.cdc.gov/nchs/data/nhsr/nhsr201.pdf. Another example of work demonstrating the need for these identifiers can be found with the publication of the National Ambulatory Medical Care Survey Health Center Component 2021 & Transformed Medicaid Statistical Information System linked file found here: https://www.cdc.gov/nchs/linked-data/namcs/namcs-hcc-medicaid.html. NCHS will be able to publish additional example projects as data are successfully linked to other data sources.This data element will increase the ability to track unique patients, improving accuracy and quality in these produced datasets.
b. Location of data element in the current HCS CDA IG V1.2: x-path /ClinicalDocument/recordTarget/patientRole/patient/id)
c. This data element is in C-CDA 4.0. Link in the C-CDA IG- https://hl7.org/cda/us/ccda/StructureDefinition-USRealmHeader.html
d. Description of what DHCS currently receives in production: The majority of EHR files submitted for NAMCS and National Hospital Care Surveys have identifier data for patient name (first, middle, and last), date of birth, and patient address. All EHR files submitted to NHCS lack medical record number (MRN) and Health Insurance Claims Number (HIC). In addition, NHCS would like to expand the availability of identifiers to include patient control number (PCN).
Submitted by csnewman on
The Patient Identifier description should include the type and source of the identifier (ie which pool of identifiers the ID came from) - note that a single organization may assign multiple different identifier types from multiple different pools of IDs
Submitted by CDC_DSMH_WG on
National Hospital Care Surveys (NHCS) and National Ambulatory Medical Care Survey (NAMCS) both conduct data linkages to other datasets (e.g. National Death Index, the U.S. Department of Housing and Urban Development, etc.) and publish them as restricted use data files. This data element will increase the ability to track unique patients, improving accuracy and quality in these produced datasets.
Location of data element in the current HCS CDA IG V1.2: x-path /ClinicalDocument/recordTarget/patientRole/patient/id)
This data element is in C-CDA 4.0. Link in the C-CDA IG- https://hl7.org/cda/us/ccda/StructureDefinition-USRealmHeader.html
Description of what DHCS currently receives in production: The majority of EHR files submitted for NAMCS and NHCS have identifier data for Social Security Number (SSN), patient name (first, middle, and last), date of birth, and patient address. All EHR files submitted to NHCS lack medical record number (MRN) and Health Insurance Claims Number (HIC). In addition, NHCS would like to expand the availability of identifiers to include patient control number (PCN).
National Center for Immunization and Respiratory Diseases (NCIRD) propose the inclusion of "Identifier" as a standardized data element in USCDI v7 due to its critical role in enhancing immunization efforts. As a unique identifier, it ensures that vaccination records are accurately matched to individual patients, which is essential for effective immunization programs.
Standardizing the Identifier significantly enhances the ability of public health authorities to monitor immunization coverage, assess vaccine effectiveness, and identify populations that are under-vaccinated. This capability is particularly important for coordinating responses to vaccine-preventable disease outbreaks and managing mass vaccination campaigns during public health emergencies, such as pandemics.
Furthermore, precise patient matching enabled by a consistent Identifier helps prevent duplicate immunization records, ensuring that individuals receive vaccines according to recommended schedules. This is vital for maintaining accurate immunization histories, which are crucial for effective patient care and public health reporting.
The inclusion of the Identifier also facilitates accurate reporting to Immunization Information Systems (IIS), supporting real-time public health decision-making and resource allocation. By ensuring that vaccination data is consistently linked to the correct patient, health authorities can make informed decisions about vaccine distribution and outreach efforts.
Moreover, a standardized Identifier can improve communication and coordination among healthcare providers involved in immunization efforts. It allows for seamless sharing of vaccination records, ensuring that all providers have access to the most current and accurate patient information, which is essential for effective immunization strategies.
The Identifier can also empower patients by enabling easier access to their vaccination records, fostering greater engagement in their own care and encouraging adherence to vaccination schedules. When patients can easily verify their immunization status, they are more likely to seek necessary vaccinations and participate in public health initiatives.
Incorporating the Identifier into health information technology systems will enhance data analytics capabilities, allowing for more effective tracking of vaccination trends and outcomes. This can inform public health strategies and improve the overall quality of immunization services provided to patients.
We strongly advocate for the inclusion of the "Identifier" in USCDI v7, as it promises to significantly improve the accuracy of patient identification for immunizations. Its adoption will enhance public health surveillance capabilities and ensure the successful implementation of national immunization strategies, ultimately leading to better health outcomes for the population.
Submitted by CDC_DSMH_WG on
CDC is requesting that Identifier added for consideration to USCDI V6 to inform hospital and ambulatory medical care survey data collection efforts.
Justification: National Healthcare Surveys and NAMCS both conduct data linkages to other datasets (e.g. National Death Index, the U.S. Department of Housing and Urban Development, etc.) and publish them as restricted use data files. This data element will increase the ability to track unique patients, improving accuracy and quality in these produced datasets.
Submitted by BLampkins_CSTE on
CSTE supports inclusion of this data element in USCDI V6. Please see previously submitted CSTE comments for additional recommendations.
Submitted by Riki Merrick on
APHL recommends to add this element to V6 as this is a critical element for linking patients within organizations, and every organization assigns some form of patient identifier to their patients. It is also called out in CLIA regulation 42 CFR 493.1291(c)(1) = "For positive patient identification, either the patient's name and identification number, or a unique patient identifier and identification number." (https://www.ecfr.gov/current/title-42/part-493/section-493.1291#p-493.1291(c)(1)) and in §493.1241(c)(2) = "The patient's name or unique patient identifier." (https://www.ecfr.gov/current/title-42/part-493/section-493.1241#p-493.1241(c)(2))
APHL also recommends to include the assigning authority with ANY identifier data element (in all HL7 products this is part of the various supported identifier type data type). Thus we propose to update the definition to: "Alphanumeric value that should uniquely identify the patient over time - at minimum within one organization, ideally at the national level), including a means to identify the organization or system that assigned it."
If ONC wants to support generic identifiers, then the elements should also include the identifier type Patient Identifier Type (https://www.healthit.gov/isp/taxonomy/term/3661/level-2), to be able to differentiate what is being shared.
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.
To specify which data class your comment addresses:
To specify which data element your comment addresses:
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.
Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.
If you cannot find the appropriate data class or element for your comment:
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.
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.
If you need to comment on multiple data classes or elements:
Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.
The platform allows you to upload supporting documentation to enhance 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.
Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.
If you need to pause your work and return to complete your comment later:
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.
Once you have completed your comment:
Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.
Submitted by BLampkins_CSTE on
Patient Identifier - CSTE Comment
CSTE supports the inclusion of Patient identifier in USCDI v7. CSTE also recommends the inclusion of 2 additional data elements to provide data critical to supporting the usability of the patient identifier data element. These include the Type of Patient Identifier (which would detail whether the identifier is, for example, a medical record number, a Medicare number, a social security number, a laboratory patient identifier) and the Patient Identifier Assigning Authority (which would provide information on which organization has assigned the identifier - for example, which health care organization, which governmental agency etc.).
1. The patient identifier field is incredibly helpful for person matching and deduplication which currently requires a huge amount of manual effort at STLT public health agencies to manage the many potential duplicates across and within data streams (even with the best algorithms and automation for patient deduplication, often health department staff spend countless hours deduplicating partially matched patient records).
2. It is critical for identifying patients for follow-up - as in when medical information is sought as part of a case investigation or when additional demographics or contact information are needed in order to quickly reach a patient, or when lab results are needed from a hospital.
3. For any type of automated or semi-automated query of an HIE or another clinical repository (as will hopefully be possible through TEFCA), MR number will be invaluable in narrowing the query and ensuring the returned results pertain to the correct individual - this will save an enormous amount of time and frustration, as well as serve to protect patient privacy by reducing or eliminating records returned for a potential patient match.
4. For any bidirectional data exchange it would be invaluable to the receiving health care org to be able to use medical record to route the data to the correct medical record.