Description (*Please confirm or update this field for the new USCDI version*)
Word or words by which a facility is known.
Submitted By: Keith W. Boone
/ Audacious Inquiry
Data Element Information
Use Case Description(s)
Use Case Description
Facility level data is associated with laboratory tests (the testing facility), and health care provider locations, including hospitals, ambulatory providers, long-term and post acute care, and pharmacy providers.
Location data is used to support reporting of data for public health and emergency response (e.g., situation awareness reporting).
See https://build.fhir.org/ig/HL7/fhir-saner/ for details (note that (minus) - is a legal character in URLs, had to use a bit.ly link to get past validation errors in URL)
Estimate the breadth of applicability of the use case(s) for this data element
Hospitals in the US (Approximately 7000), Laboratories (260,000), pharmacies (88,000), ambulatory physicians (260,000).
5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Restrictions on Standardization (e.g. proprietary code)
None
Restrictions on Use (e.g. licensing, user fees)
None
Privacy and Security Concerns
Locations associated with Critical Access Hospitals, and single provider facilities may constitute PHI (in geographic locations with limited populations) and/or Individual Identifiable Information (e.g., for HCPs working from a combined home/office facility).
Estimate of Overall Burden
Most electronic systems provide the capacity to store location and organization information. Many EHRs already provide access to the Location resource via READ operations, some (e.g., Epic, AthentaHealth) provide search capabilities as well. This information is routinely communicated in HL7 V2 Messages, CDA Documents and some FHIR API transactions. To address gaps, implementers would need to modify interfaces (e.g., for CDA or HL7 V2), or add an endpoint. Estimated effort (based on past experience building EHR systems) is about one two-week sprint to implement the capability by a developer.
Other Implementation Challenges
Standards for location identifier may need flexibility depending on use of Location for reportiong, as there are a number of distinct location identifier systems which may be necessary for different reporting use cases. For example, CDC/NHSN assigns identifiers for HAI reporting, CLIA assigns identifiers to laboratories, CMS provides location identifiers, et cetera.
NCPDP recommends adding the NCPDP SCRIPT Standard v2017071, NCPDP Specialized Standard v2017071, NCPDP Telecommunication Standard Version D.0 and NCPDP Real-Time Prescription Benefit Standard Version 12 as “Applicable Standard(s)”.
CDC considers this element to be high priority and strongly recommends its inclusion in the USCDI V3
CSTE supports inclusion of this measure into USCDI v3: Very useful for this information to be captured in some way and then subsequently used in reporting to PH.
Official Website of the Assistant Secretary for Technology Policy/Office of the National Coordinator for Health IT
Submitted by pwilson@ncpdp.org on
NCPDP Comment
NCPDP recommends adding the NCPDP SCRIPT Standard v2017071, NCPDP Specialized Standard v2017071, NCPDP Telecommunication Standard Version D.0 and NCPDP Real-Time Prescription Benefit Standard Version 12 as “Applicable Standard(s)”.