|Submitted By: A. Taylor / ONC
|Data Element Information
|Use Case Description(s)
|Use Case Description
|A user can record a patient’s sexual orientation according to HL7 Version 3 and SNOMED CT® codes. The user must be able to record whether the patient declined to specify sexual orientation. Note that while sexual orientation is included in this 2015 Edition “demographics” certification criterion and the 2015 Edition Base EHR definition, it is not included in the Common Clinical Data Set definition. This means that sexual orientation is not required to be exchanged using certain standards, only that systems enable a user to record sexual orientation. [see also 80 FR 62619]
We provide the following OID to assist developers in the proper identification and exchange of health information coded to certain vocabulary standards.
SNOMED CT® code system OID: 2.16.840.1.113883.6.96 [see also 80 FR 62612]
Health IT Modules can present for certification to a more recent version of the U.S. Edition of SNOMED CT® than the September 2015 version. [see also 80 FR 62612]
|Estimate the breadth of applicability of the use case(s) for this data element
|Users of the 572 certified health IT products, out of 901 total products certified to ONC's 2015 Edition, that successfully tested to the 170.315(a)(5) demographics
certification criterion has the ability to record, change, and access gender identity data within these products.
|Link to use case project page
|Maturity of Use and Technical Specifications for Data Element
|This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
|Extent of exchange
|Restrictions on Standardization (e.g. proprietary code)
|While it is required under the 2015 Edition 170.315(a)(5) demographics certification criterion to be able to record, change, and access sexual orientation data, it is not required for exchange. One restriction may be the ability to restrict exchange based on patient consent by element.
|Restrictions on Use (e.g. licensing, user fees)
|Privacy and Security Concerns
|Estimate of Overall Burden
|Already implemented for record, change, and access, but not for exchange.