Printer Friendly, PDF & Email

Patient Demographics

Data Element

Applicable Vocabulary Standard(s)

Current Address

Includes street name, number, city/town, state, and zip code

Date of Birth

Email Address

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)
First Name

Last Name

Middle Name (including middle initial)

Phone Number

  • 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, and 
  • 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

Preferred Language

Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009

Adopted at 45 CFR 170.207(g)

Previous Address

Includes street name, number, city/town, state, and zip code

Previous Name

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)
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) 

Suffix

Data Element

Applicable Vocabulary Standard(s)

Current Address

Includes street name, number, city/town, state, and zip code

Date of Birth

Email Address

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)
First Name

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)
Last Name

Middle Name (including middle initial)

Phone Number

  • 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, and 
  • 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

Preferred Language

Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009

Adopted at 45 CFR 170.207(g)

Previous Address

Includes street name, number, city/town, state, and zip code

Previous Name

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)
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)
Suffix

Comment

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. 

Log in or register to post comments