Printer Friendly, PDF & Email

Patient Demographics

Data Element

Applicable Standard(s)

First Name
Last Name
Previous Name
Middle Name (including middle initial)
Suffix
Birth Sex Birth sex must be coded in accordance with HL7 Version 3 (V3) Standard, Value Sets for AdministrativeGender and NullFlavor (https://www.healthit.gov/sites/default/files/170299_f_29_hl7_v3_agender_and_nullflavor.pdf) attributed as follows:
  1. Male. M
  2. Female. F
  3. Unknown. nullFlavor UNK
Date of Birth
Race
Ethnicity
Preferred Language Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 (http://www.rfc-editor.org/info/rfc5646) See https://tools.ietf.org/html/bcp47
Current Address
Previous Address
Phone Number ITU–T E.123 (02/2001) International Telecommunication Union E.123: Notation for national and international telephone numbers, e-mail addresses and web addresses ITU–T E.164 International Telecommunication Union E.164: The international public telecommunication numbering plan
Phone Number Type
Email Address

Data Element

Applicable Standard(s)

First Name
Last Name
Previous Name
Middle Name (including middle initial)
Suffix
Birth Sex Birth sex must be coded in accordance with HL7 Version 3 (V3) Standard, Value Sets for AdministrativeGender and NullFlavor (https://www.healthit.gov/sites/default/files/170299_f_29_hl7_v3_agender_and_nullflavor.pdf) attributed as follows:
  1. Male. M
  2. Female. F
  3. Unknown. nullFlavor UNK
Date of Birth
Race
Ethnicity
Preferred Language Request for Comment (RFC) 5646, “Tags for Identifying Languages”, September 2009 (http://www.rfc-editor.org/info/rfc5646) See https://tools.ietf.org/html/bcp47
Current Address
Previous Address
Phone Number ITU–T E.123 (02/2001) International Telecommunication Union E.123: Notation for national and international telephone numbers, e-mail addresses and web addresses ITU–T E.164 International Telecommunication Union E.164: The international public telecommunication numbering plan
Phone Number Type
Email Address

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