Submitted by yale-coredQMRoadmap on 2023-09-19
Data Element |
Applicable Vocabulary Standard(s) |
---|---|
Race
|
Both standards are required
|
Ethnicity
|
Both standards are required
|
Birth Sex
|
Birth sex must be coded in accordance with HL7 Version 3 (V3) Standard, Value Sets for AdministrativeGender and NullFlavor attributed as follows:
Adopted at 45 CFR 170.207(n) |
Preferred Language
|
Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 Adopted at 45 CFR 170.207(g) |
Current Address
Includes street name, number, city/town, state, and zip code. |
|
Previous Address
Includes street name, number, city/town, state, and zip code. |
|
Phone Number
|
Both standards are required
|
Data Element |
Applicable Vocabulary Standard(s) |
---|---|
Race
|
Both standards are required
|
Ethnicity
|
Both standards are required
|
Sex (Assigned at Birth)
|
Birth sex must be coded in accordance with HL7 Version 3 (V3) Standard, Value Sets for AdministrativeGender and NullFlavor attributed as follows:
Adopted at 45 CFR 170.207(n) |
Sexual Orientation
A person’s identification of their emotional, romantic, sexual, or affectional attraction to another person |
Sexual orientation must be coded in accordance with SNOMED CT® and HL7 Version 3 Standard, Value Sets for AdministrativeGender and NullFlavor, attributed as follows:
|
Gender Identity
A person’s internal sense of being a man, woman, both, or neither. |
Gender Identify must be coded in accordance with SNOMED CT® and HL7 Version 3 Standard, Value Sets for AdministrativeGender and NullFlavor, attributed as follows:
|
Preferred Language
|
Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 Adopted at 45 CFR 170.207(g) |
Current Address
Includes street name, number, city/town, state, and zip code. |
|
Previous Address
Includes street name, number, city/town, state, and zip code. |
|
Phone Number
|
Both standards are required
|
Data Element |
Applicable Vocabulary Standard(s) |
---|---|
Name Suffix
Name component following family name that may be used to describe a person's position in a family. |
|
Date of Birth
Known or estimated year, month, and day of the patient's birth. |
|
Date of Death
Known or estimated year, month, and day of the patient's death. |
|
Race
|
Both standards are required
|
Ethnicity
|
Both standards are required
|
Tribal Affiliation
Tribe or band with which an individual associates. |
|
Sex
Documentation of a specific instance of sex and/or gender information. |
|
Sexual Orientation
A person’s identification of their emotional, romantic, sexual, or affectional attraction to another person |
|
Gender Identity
A person’s internal sense of being a man, woman, both, or neither. |
|
Preferred Language
|
|
Current Address
Place where a person is located or may be contacted |
|
Previous Address
Prior place where a person may have been located or could have been contacted. |
|
Phone Number
Numbers and symbols to contact an individual when using a phone. |
Both standards are required
|
Phone Number Type
Contact point when using a phone (e.g., home, work, mobile). |
|
Email Address
Unique identifier of an individual's email account that is used to send and receive email messages. |
|
Related Person's Name
Name of a person with a legal or familial relationship to a patient. |
|
Related Person's Relationship
Relationship of a person to a patient. (e.g., parent, next-of-kin, guardian, custodian) |
|
Occupation
Type of work of a person. (e.g., infantry, business analyst, social worker) |
|
Occupation Industry
Type of business that compensates for work or assigns work to an unpaid worker or volunteer. (e.g., U.S. Army, cement manufacturing, children and youth services) |
|
Data Element |
Applicable Vocabulary Standard(s) |
---|---|
Name Suffix
Name component following family name that may be used to describe a person's position in a family. |
|
Date of Birth
Known or estimated year, month, and day of the patient's birth. |
|
Date of Death
Known or estimated year, month, and day of the patient's death. |
|
Race
|
Both standards are required
|
Ethnicity
|
Both standards are required
|
Tribal Affiliation
Tribe or band with which an individual associates. |
|
Sex
Documentation of a specific instance of sex and/or gender information. |
|
Sexual Orientation
A person’s emotional, romantic, sexual, or affectional attraction to another person. |
|
Gender Identity
A person’s internal sense of being a man, woman, both, or neither. |
|
Preferred Language
|
|
Current Address
Place where a person is located or may be contacted |
|
Previous Address
Prior place where a person may have been located or could have been contacted. |
|
Phone Number
Numbers and symbols to contact an individual when using a phone. |
Both standards are required
|
Phone Number Type
Contact point when using a phone. Examples include but are not limited to home, work, and mobile. |
|
Email Address
Unique identifier of an individual's email account that is used to send and receive email messages. |
|
Related Person's Name
Name of a person with a legal or familial relationship to a patient. |
|
Relationship Type
Relationship of a person to a patient. Examples include but are not limited to parent, next-of-kin, guardian, and custodian. |
|
Occupation
Type of work of a person. Examples include but are not limited to infantry, business analyst, and social worker. |
|
Occupation Industry
Type of business that compensates for work or assigns work to an unpaid worker or volunteer. Examples include but are not limited to U.S. Army, cement manufacturing, and children and youth services. |
|
Data Element |
---|
Data Element |
---|
Comment
Submitted by Sokhen472@ on 2022-04-29
Adding Related Person's Name to Patient Demographic Class
Unified Comment on behalf of the Maternal Health Consortium, funded by the Office of the Secretary’s Patient-Centered Outcomes Research Trust Fund (OS-PCORTF) The rates of maternal mortality have been rising in the United States since 1987. Yet this measure does not capture data related to maternal health. Understanding maternal health before, during, and after childbirth is foundational for developing safer, more effective approaches to maternal care. Clinical data relevant to understanding this trend are not standardized, and data exchange is not interoperable across many relevant settings. Furthermore, maternal health and associated child health are inextricably linked – what happens during gestation, delivery, and after informs health outcomes of both mother and child – but relevant data is often held in separate, unconnected records. These issues impede research on maternal morbidity and longitudinal maternal care and associated impacts to infant health. Research on root causes of maternal mortality, poor outcomes, pediatric developmental problems, and effective treatments requires exchange of information stored in disparate sources, such as electronic health record (EHR) systems, disease registries, and public health agencies (PHAs). Research use case populations as described in the draft Longitudinal Maternal & Infant Health -FHIR Implementation Guide (https://build.fhir.org/ig/HL7/fhir-mmm-ig/):- Pregnancy and subsequent death within a specific time frame: This cohort includes individuals who died within a year (365 days) of a pregnancy regardless of cause of death or pregnancy outcome.
- Hypertensive Disorders of pregnancy: This use case focuses on individuals with a diagnosis of hypertensive disorders of pregnancy.
Submitted by Sokhen472@ on 2022-04-29
Adding Birth Time of Neonate to Date of Birth data element
Unified Comment on behalf of the Maternal Health Consortium, funded by the Office of the Secretary’s Patient-Centered Outcomes Research Trust Fund (OS-PCORTF) The rates of maternal mortality have not improved in the United States since 1987. Yet this measure does not capture data related to maternal health. Understanding maternal health before, during, and after delivery is foundational for developing safer, more effective approaches to care. Clinical data relevant to understanding this trend are not standardized, and data exchange is not interoperable across many relevant settings. Furthermore, maternal health and associated child health are inextricably linked – what happens during gestation, delivery, and after informs health outcomes of both mother and child – but relevant data is often held in separate, unconnected records. These issues impede research on maternal morbidity and longitudinal maternal care and associated impacts to infant health. Research on root causes of maternal mortality, poor outcomes, pediatric developmental problems, and effective treatments requires exchange of information stored in disparate sources, such as electronic health record (EHR) systems, disease registries, and public health agencies (PHAs). In use cases for either defining when an event occurred relative to a delivery, having infant birth time identified is critical. The Consortium recommends adding birth time to the Date of Birth data element in the Patient Demographics data class. Our use cases focus on pregnancy and subsequent death within a specific timeframe and hypertensive disorders of pregnancy (pre, ante, and after pregnancy). The intent is to specify the consistent capture of clinical data of interest to maternal health researchers and outline implementing FHIR resources for that capture. Birth time is already supported in the FHIR interface of major EHR systems such as Cerner https://www.healthit.gov/isa/uscdi-data/birth-time, Epic HL7 Standards Product Brief - HL7 FHIR® Implementation Guide: Vital Records Birth and Fetal Death Reporting, Release 1 - US Realm | HL7 International Current LRI IG (hl7.org), and the FHIR birth time extension https://www.hl7.org/fhir/extension-patient-birthtime.html Research use case populations as described in the draft Longitudinal Maternal & Infant Health Information for Research FHIR Implementation Guide (https://build.fhir.org/ig/HL7/fhir-mmm-ig/):- Pregnancy and subsequent death within a specific time frame: This cohort includes individuals who died within a year (365 days) of a pregnancy regardless of cause of death or pregnancy outcome.
- Hypertensive Disorders of pregnancy: This use case focuses on individuals with a diagnosis of hypertensive disorders of pregnancy.
Submitted by Barry Hieb on 2022-10-19
Timestamp
It appears that the addition of a general timestamp data type is needed. We recommend using ISO 8601 (UTC) as a way to capture the time at which an event occurs.Submitted by ravi.kafle@doh… on 2022-04-29
Addition of Previous Phone Numbers and Email
While USCDI V1 does contain Previous Address which can be very helpful for matching patient records together; two other elements would aid in this regard as well. WA DOH recommends adding previous phone number and email address for the purpose of being able to better identify records belonging to the same patient. This could be useful across data systems as well as in use with a master person index.Submitted by ravi.kafle@doh… on 2022-04-28
Tribal Affiliation
The Washington DOH subject matter experts on Tribal matters have the following comments: "The collection, usage, management, disclosure, and safeguarding of Tribal data is a governance activity that ONC should develop in collaboration with the Tribe(s) whose members are included in the data. The ONC should commit to meaningful consultation with tribal leaders of individual sovereign tribal nations to ensure they have an opportunity to provide timely input before using Tribal data, including Tribal affiliation or any other Tribal identifying information. The U.S. Constitution recognizes that Tribal nations are sovereign governments. As such, they have powers of self-government, upheld, repeatedly, by the U.S. Supreme Court. Tribal governments have the legal authority to administer the collection, ownership, application, and interpretation of their own data, even if it is collected by federal, state, or local governments. Tribal data means public or private facts, statistics or items of information on or about a Tribe or its people subject to tribal rights of ownership and control. This includes, but is not limited to, Tribe of membership, Tribe of affiliation, and identification of tribal facilities, entities, and enterprises. Tribal data means (1) data that is specific to an individual Tribe; or (2) data that is specific to more than one Tribe but does not identify individual Tribe(s)."Submitted by American Colle… on 2021-11-29
ACOEM Comment re Work Information Data
Please see attached comment from ACOEM regarding the inclusion of work information data in USCDI v3.Submitted by nedragarrett_CDC on 2021-10-06
CDC Unified Comment: California Department of Public Health
- Good Morning, The California Department of Public Health recommends adding the following data elements for the Patient Profile in exchange between EHRs:
- Patient Demographics: Expand to cover Social Determinants of Health
- § Number of Dependents
- § Sexual Orientation
- § Gender Identity
- § Sex Assigned At Birth
- § Gender of Sex Partners
- § Preferred Language
- § Country of Birth
- § Last report of homelessness
- § Last report of incarceration
- § Last report of food insecurity
- § Current occupation/occupation history
- § Insurance Status
Submitted by jeffcoughlin on 2021-04-16
Submitted by NCQA on 2023-09-20
NCQA Comment on Pronouns: for USCDI v5
- Pronouns:
NCQA supports adding the Pronouns element to USCDI (as proposed by Gender Harmony and represented in LOINC through “Observation: 90778-2 Personal Pronouns – Reported” and “Answer list: LL5144-2 Personal pronouns 1.3.6.1.4.1.12009.10.1.4011”). Understanding which pronoun(s) to use when referring to someone is important for providing affirming health care. It is important to reliably exchange personal pronouns that the individual has specifically reported they want used.