|Submitted By: Nedra Y Garrett / CDC|
|Data Element Information|
|Use Case Description(s)|
|Use Case Description||Physicians, nurses, epidemiologists, and anyone using laboratory reports for patient care, including patients, will depend on the correct representation of units of measure of laboratory results.|
|Estimate the breadth of applicability of the use case(s) for this data element||Level 2 – elements pertain to most or all patients, providers or requestors.
About 1,000,000 practicing physicians, 120,000 physician assistants, 290,000 licensed nurse practitioners, and almost all of the population of the USA who will get a laboratory result with a numerical value will be involved in the capture, asses, use, or exchange of Laboratory Results Units of Measure.
|Maturity of Use and Technical Specifications for Data Element|
|Applicable Standard(s)||The Unified Code for Units of Measure (UCUM).
|Current Use||Extensively used in production environments|
This data element is exchanged extensively in the current production environment in all electronic exchanges of laboratory test results as it is part of CLIA regulations. It is mapped to UCUM as a standard in most of these exchanges.
US Core Observation Clinical Test Result FHIR Profile has included Units of Measure as a mandatory and must support element and must be coded in UCUM. See link #1 below.
In the US Core Implementation Guide JSON representation example in link #2, this element is also used in UCUM.
For Laboratory Results Interface (LRI), the applicable standard provided in the IG is UCUM.
|Extent of exchange||5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.|
“Units of measure” is a CLIA requirement under 42 CFR 493.1291(c)(6). See the link below in 1:
Because it is a regulatory requirement, all numerical test results include this data element. Hence it is used extensively in the production environment.
|Restrictions on Standardization (e.g. proprietary code)||No restriction.|
|Restrictions on Use (e.g. licensing, user fees)||No restriction.|
|Privacy and Security Concerns||No concerns.|
|Estimate of Overall Burden||Very low burden. This element should already be part of the EHR due to its laboratory regulatory requirement (CLIA)|
|Other Implementation Challenges||None.|