Patient Demographics/Information

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

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Suffix
Previous Name
Date of Birth
Race	Both standards are required The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.0 (March 2000) Adopted at 45 CFR 170.207(f)
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.0 (March 2000) Adopted at 45 CFR 170.207(f)
Birth Sex	Birth sex must be coded in accordance with HL7 Version 3 (V3) Standard, Value Sets for AdministrativeGender and NullFlavor attributed as follows: Female. F Male. M Unknown. nullFlavor UNK 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 ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 ITU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
Phone Number Type
Email Address

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Suffix
Previous Name
Date of Birth
Race	Both standards are required The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.0 (March 2000) Adopted at 45 CFR 170.207(f)
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.0 (March 2000) Adopted at 45 CFR 170.207(f)
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: Female. F Male. M Unknown. nullFlavor UNK 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: Lesbian, gay or homosexual. 38628009 Straight or heterosexual. 20430005 Bisexual. 42035005 Something else, please describe. nullFlavor OTH Don't know. nullFlavor UNK Choose not to disclose. nullFlavor ASKU Adopted at 45 CFR 170.207(o)(1)
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: Male. 446151000124109 Female. 446141000124107 Female-to-Male (FTM)/Transgender Male/Trans Man. 407377005 Male-to-Female (MTF)/Transgender Female/Trans Woman. 407376001 Genderqueer, neither exclusively male nor female. 446131000124102 Additional gender category or other, please specify. nullFlavor OTH Choose not to disclose. nullFlavor ASKU Adopted at 45 CFR 170.207(o)(2)
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 ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 ITU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
Phone Number Type
Email Address

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Name Suffix Name component following family name that may be used to describe a person's position in a family.
Previous Name
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: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Tribal Affiliation Tribe or band with which an individual associates.
Sex Documentation of a specific instance of sex.	SNOMED International, Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT®) U.S. Edition, March 2022 Release
Sexual Orientation A person’s identification of their emotional, romantic, sexual, or affectional attraction to another person	SNOMED International, Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT®) U.S. Edition, March 2022 Release
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: Male. 446151000124109 Female. 446141000124107 Female-to-Male (FTM)/Transgender Male/Trans Man. 407377005 Male-to-Female (MTF)/Transgender Female/Trans Woman. 407376001 Genderqueer, neither exclusively male nor female. 446131000124102 Additional gender category or other, please specify. nullFlavor OTH Choose not to disclose. nullFlavor ASKU Adopted at 45 CFR 170.207(o)(2)
Preferred Language	IETF (Internet Engineering Task Force) Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 Adopted at 45 CFR 170.207(g)(2)
Current Address Place where a person is located or may be contacted.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Previous Address Prior place where a person may have been located or could have been contacted.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Phone Number Numbers and symbols to contact an individual when using a phone.	Both standards are required: ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 ITU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
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)	Occupational Data for Health, version 20201030
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)	Occupational Data for Health, version 20201030

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Name Suffix Name component following family name that may be used to describe a person's position in a family.
Previous Name
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: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Tribal Affiliation Tribe or band with which an individual associates.
Sex Documentation of a specific instance of sex.	Both values must be supported: SNOMED CT U.S. Edition: 248152002 (Female) SNOMED CT U.S. Edition: 248153007 (Male)
Preferred Language	IETF (Internet Engineering Task Force) Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 Adopted at 45 CFR 170.207(g)(2)
Current Address Place where a person is located or may be contacted	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Previous Address Prior place where a person may have been located or could have been contacted.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Phone Number Numbers and symbols to contact an individual when using a phone.	Both standards are required: ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 ITU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
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)	Occupational Data for Health, version 20201030
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)	Occupational Data for Health, version 20201030

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Name Suffix Name component following family name that may be used to describe a person's position in a family.
Previous Name
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: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Tribal Affiliation Tribe or band with which an individual associates.
Sex Documentation of a specific instance of sex.	Both values must be supported: SNOMED CT U.S. Edition: 248152002 (Female) SNOMED CT U.S. Edition: 248153007 (Male)
Preferred Language	IETF (Internet Engineering Task Force) Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 Adopted at 45 CFR 170.207(g)(2)
Current Address Place where a person is located or may be contacted	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Previous Address Prior place where a person may have been located or could have been contacted.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Phone Number Numbers and symbols to contact an individual when using a phone.	Both standards are required ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 ITU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
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.	Occupational Data for Health, version 20201030
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.	Occupational Data for Health, version 20201030

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Name Suffix Name component following family name that may be used to describe a person's position in a family.
Previous Name
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: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.2 (July 2021)
Tribal Affiliation Tribe or band with which an individual associates.
Sex Documentation of a specific instance of sex.	Both values must be supported: SNOMED CT U.S. Edition: 248152002 (Female) SNOMED CT U.S. Edition: 248153007 (Male)
Preferred Language	IETF (Internet Engineering Task Force) Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 Adopted at 45 CFR 170.207(g)(2)
Interpreter Needed Indication of whether a person needs language interpretation services.	Logical Observation Identifiers Names and Codes (LOINC) version 2.77 SNOMED Clinical Terms® (SNOMED CT®) U.S. Edition, March 2024 Release
Current Address Place where a person is located or may be contacted. Usage note: If the address pattern is not supported in the standard, implementations should align as closely as possible and avoid truncating any values.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Previous Address Prior place where a person may have been located or could have been contacted. Usage note: If the address pattern is not supported in the standard, implementations should align as closely as possible and avoid truncating any values.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Phone Number	Both standards are required ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 ITU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
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.	Occupational Data for Health, version 20201030
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.	Occupational Data for Health, version 20201030

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Name Suffix Name component following family name that may be used to describe a person's position in a family.
Previous Name
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: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.3 May 2025
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 CDC Race and Ethnicity Code Set Version 1.3 May 2025
Tribal Affiliation Tribe or band with which an individual associates.
Sex Documentation of a specific instance of sex.	SNOMED Clinical Terms (SNOMED CT) U.S. Edition, March 2025 Release Both values must be supported: SNOMED CT U.S. Edition: 248152002 (Female) SNOMED CT U.S. Edition: 248153007 (Male)
Preferred Language	IETF (Internet Engineering Task Force) Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 Adopted at 45 CFR 170.207(g)(2)
Interpreter Needed Indication of whether a person needs language interpretation services.	Logical Observation Identifiers Names and Codes (LOINC) version 2.80 SNOMED Clinical Terms® (SNOMED CT®) U.S. Edition, March 2025 Release
Current Address Place where a person is located or may be contacted. Usage note: If the address pattern is not supported in the standard, implementations should align as closely as possible and avoid truncating any values.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Previous Address Prior place where a person may have been located or could have been contacted. Usage note: If the address pattern is not supported in the standard, implementations should align as closely as possible and avoid truncating any values.	Project US@ Technical Specification for Patient Addresses, Final Version 1.0
Phone Number Numbers and symbols to contact an individual when using a phone.	Both standards are required: ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 ITU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
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.	Occupational Data for Health, version 20201030
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.	Occupational Data for Health, version 20201030

Data Element	Applicable Vocabulary Standard(s)
First Name
Last Name
Middle Name (Including middle initial)
Name Suffix Name component following family name that may be used to describe a person's position in a family.
Previous Name
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: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15 CDC Race and Ethnicity Code Set
Ethnicity	Both standards are required: The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15 CDC Race and Ethnicity Code Set
Tribal Affiliation Tribe or band with which an individual associates.
Sex Documentation of a specific instance of sex.	Both values must be supported: SNOMED CT U.S. Edition: 248152002 (Female) SNOMED CT U.S. Edition: 248153007 (Male)
Preferred Language	IETF (Internet Engineering Task Force) Request for Comment (RFC) 5646, “Tags for Identifying Languages” Adopted at 45 CFR 170.207(g)(2)
Interpreter Needed Indication of whether a person needs language interpretation services.	Logical Observation Identifiers Names and Codes (LOINC®) SNOMED Clinical Terms® (SNOMED CT®) U.S. Edition
Current Address Place where a person is located or may be contacted. Usage note: If the address pattern is not supported in the standard, implementations should align as closely as possible and avoid truncating any values.	Project US@ Technical Specification for Patient Addresses
Previous Address Prior place where a person may have been located or could have been contacted. Usage note: If the address pattern is not supported in the standard, implementations should align as closely as possible and avoid truncating any values.	Project US@ Technical Specification for Patient Addresses
Phone Number Numbers and symbols to contact an individual when using a phone.	Both standards are required: ITU-T E.123, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - General provisions concerning users: Notation for national and international telephone numbers, email addresses and web addresses, February 2001 TU-T E.164, Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors, International operation - Numbering plan of the international telephone service, The international public telecommunication numbering plan, November 2010 Adopted at 45 CFR 170.207(q)(1)
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.	Occupational Data for Health
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.	Occupational Data for Health
Accommodation Modifications, tools, technologies, and other supports necessary to access care.	SNOMED Clinical Terms (SNOMED CT®) U.S. Edition
Patient Identifier Sequence of characters assigned by an organization to uniquely refer to a patient. Examples include but are not limited to Medical Record Number.
Deceased Indicator Indicates if the person is deceased or not.

Data Element
Birth time
Mother's Maiden Name
Accommodation
Identifier
Patient Identifier Type
Deceased Indicator

Data Element
Patient Social Security Number
Patient Marital Status
Patient's Primary Care Provider
Patient Birth Place
Variation in Sex Characteristics

Data Element
Income
Medical Record Number
Multiple Birth Order
Patient Address Use Period
Patient Vital Status
Country of Usual Residence
Organ Donor
Tribal Enrollment
Country of Nationality
HL7-Identifier
<prTag>identifier
<prTag>timestamp
<prTag>status
Rurality

Comment

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.

ACOEM Comment re Work Information Data.pdf

Submitted by CDC_DSMH_WG 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

Add Veteran Status to Patient Demographic Data Class

ONC should add Veteran Status as a data element to this data class. Such a step would help with care coordination across VA's network and private sector providers. In addition, such information would be helpful at the point of care as clinicians reference social determinants of health data, and ensure that veterans are availing themselves of all the benefits that they are owed given their service to our nation.

For the past several years, the Department of Defense (DoD), Department of Veterans Affairs (VA), and ONC have collaborated to modernize our military and Veteran’s Electronic Health Record (EHR) system. Seamless integration of care and health data across DoD, VA, and the private sector is a key component of this effort. Information exchange is vital to improving the overall readiness for our military, while guaranteeing Service members and beneficiaries receive the quality care they deserve. In addition, ensuring alignment with nationally-recognized data standards, industry best practices, and continuity of care as our nation’s Service member’s transition to Veteran status is critical to the success of our nation’s DoD and VA’s EHR modernization efforts. Moreover, appropriately leveraging USCDI makes certain this information is available and accessible for exchange and remains a key component of broader nationwide interoperability goals.

The latest data maintains that nearly six out of 10 Veterans receive some portion of their health care from private sector providers, making Veterans a strong business case for broader interoperability. Adding Veteran Status to USCDI will ensure that more information is available to appropriately treat Veterans, and allow our health system to better coordinate their goals, care plans, and benefits across the continuum of care.

Form Guide

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:

In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
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.
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:

In the "Data Element" drop-down menu, select the specific data element you want to comment on.
The drop-down menu will display only the elements available under the data class you selected in the previous step.
You can use the search function within the drop-down to quickly locate a specific data element.
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.

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:

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."
This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.

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:

After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
A new comment section will appear, allowing you to enter details for your additional comment.
For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
Complete the Subject and Comment fields for your additional comment.
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.

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:

Click the "Save and Exit" button at the bottom of the form.
Your comment will be saved as a draft that you can access and complete later.
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.
Click this button to continue working on your draft.
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:

Click the "Review and Submit" button at the bottom of the form.
This will take you to a review screen displaying your comment(s) in full.
Review all information for accuracy and completeness.
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
The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.

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

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Data Element

Data Element

Comment

Addition of Previous Phone Numbers and Email

Tribal Affiliation

ACOEM Comment re Work Information Data

CDC Unified Comment: California Department of Public Health

Add Veteran Status to Patient Demographic Data Class

Add a New Comment

Review comment and Submit

Patient Demographics/Information

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Applicable Vocabulary Standard(s)

Data Element

Data Element

Data Element

Comment

Addition of Previous Phone Numbers and Email

Tribal Affiliation

ACOEM Comment re Work Information Data

CDC Unified Comment: California Department of Public Health

Add Veteran Status to Patient Demographic Data Class

Help

1. Optional: Background Text / Cover Letter

2. Select the Data Class

3. Select the Data Element

4. Optional: Propose New Data Class or Element

5. Complete the Comment Form

6. Optional: Add Additional Comments

7. Optional: Upload Supporting Files

8. Optional: Save and Exit

9. Review and Submit

USCDI Comments

Add a New Comment

Review comment and Submit