Data used to categorize individuals for identification, records matching, and other purposes.

Data Element
Mother's Maiden Name
Description

Contains information about the patient’s mother’s last name when she was born (i.e., before marriage).
Submitted By: Nedra Garrett / Centers for Disease Control and Prevention
Data Element Information
Use Case Description(s)
Use Case Description Mother’s maiden name and responsible party information is extremely important when matching patient records for minors, especially young infants that may not have name information yet. The IIS uses this information to identify, prevent, and resolve duplicated and fragmented patient records using an automated process.
Estimate the breadth of applicability of the use case(s) for this data element There are multiple stakeholders that currently capture, access, use or exchange these data elements including:
• Electronic Health Records
• Immunization information systems and local and state departments of public health
• Providers
• Vital records
Link to use case project page https://www.cdc.gov/vaccines/programs/iis/index.html
Healthcare Aims
  • Improving the health of populations
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) CDC-defined HL70063
https://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1398?
Additional Specifications This information is contained the NK1-2 field in the HL7 v2 message. Additionally, there is a FHIR resource for related person: relatedperson.name and relatedperson.relationship.
Current Use This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
Supporting Artifacts HL7 v2.5.1 Implementation Guide for Immunization Messaging
HL7 v2.8.2 Implementation Guide: Immunization Messaging
Clinical Decision Support for Immunizations FHIR IG
AIRA Functional Standards Document
CDC Endorsed Data Elements

AIRA Functional Standards Document: https://repository.immregistries.org/files/resources/5a83216a1d369/aira_functional_guide_vol2_final.pdf
https://www.cdc.gov/vaccines/programs/iis/technical-guidance/hl7.html
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 HL7 v2.5.1 Implementation Guide for Immunization Messaging
HL7 v2.8.2 Implementation Guide: Immunization Messaging
FHIR CDSi
AIRA Functional Standards Document
CDC Endorsed Data Elements

CDC Endorsed Data Elements: https://www.cdc.gov/vaccines/programs/iis/core-data-elements.html
https://www.cdc.gov/vaccines/programs/iis/technical-guidance/hl7.html
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) There are no restrictions on these data elements.
Restrictions on Use (e.g. licensing, user fees) There are no restrictions on these data elements.
Privacy and Security Concerns There are privacy concerns with the use and exchange of these data elements, mainly mother’s maiden name.
Estimate of Overall Burden Most EHRs should already store and message mother’s maiden name and next of kin information in HL7 v2 messages.
Other Implementation Challenges N/A
ONC 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 2 - Use cases apply to most care settings or specialties.
Evaluation Comment Assessed to remain at Level 2 due to widespread capabilities to capture and exchange this information, existing and evolving standards, and the need to accurately match pediatric records.

Comment

Submitted by nedragarrett_CDC on

CDC's Consolidated Comment for USCDI v5

  • The "Mother’s Maiden Name" is a proposed vital data element for inclusion in the v5 USCDI, designed to bolster patient identification procedures, particularly for newborns who may not have a name assigned immediately after birth. This data element can significantly enhance the accuracy and security within healthcare systems by serving as an additional, reliable matching criterion for patient records. When standard identifiers such as name and date of birth are insufficient to differentiate between patients, the mother's maiden name can provide an additional layer of certainty, reducing the risk of misidentification and enhancing patient safety. This becomes especially critical in neonatal care settings, where precise identification is paramount for appropriate and timely care delivery. Moreover, "Mother’s Maiden Name" can be a powerful tool to prevent the creation of duplicate patient records. This pervasive issue contributes to administrative inefficiencies, data integrity problems, and potential errors in patient care. As healthcare systems evolve towards more integrated and interconnected models, the importance of precise and secure patient identification continues to grow. The inclusion of the "Mother’s Maiden Name" in the USCDI v5 is a practical, actionable step towards addressing these identification challenges, providing healthcare practitioners with a consistent and reliable means of matching patients to their medical records. We strongly advocate for incorporating the "Mother’s Maiden Name" data element into the USCDI v5, as it promises to markedly improve the reliability, security, and integrity of patient information across the healthcare spectrum.
  • CSTE Comment: CSTE strongly agrees with CDC recommendation for this data element. 
  • NACCHO Comment: Support - While LHDs will rely on the vital records systems for match verification, having this extra component will help ensure LHDs can verify any identification mismatch that occurs.

Submitted by nedragarrett_CDC on

CDC's comment on behalf of CSTE

CSTE strongly recommends that mothers maiden name be moved into USCDI v3. This element is critical to include in eCR and ELR and is used heavily for person matching and deduplication as well as when requesting additional clinical information on a case of reportable disease. This element is in routine use in HIEs and for EHR to IIS data exchange.

Submitted by nedragarrett_CDC on

Unified Comment from CDC

  • Mother’s maiden name is a CDC immunization endorsed data element which is an important component of the medical records of infants and minors especially for those that may not yet have a name. The IIS uses this information to identify, prevent, and resolve duplicated and fragmented patient records using an automated process. This deduplication process, in turn, will help to ensure that the most accurate and up to date information is always available thereby improving data quality, clinical decision making and reporting quality measures (e.g, health disparities).
     
  •  CSTE supports inclusion of this measure into USCDI v3: Inclusion of this element would be useful for patient matching/de-duplication


 

Log in or register to post comments