Description (*Please confirm or update this field for the new USCDI version*)
Physical location of available services or resources.
Submitted By: Keith W. Boone
/ Audacious Inquiry
Data Element Information
Rationale for Separate Consideration
Patient Address is similar, but not the same as Facility Address. Facility Address should have at least the same constraints.
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.
CDC has recommended inclusion of this field since USCDIv4 supporting a number of applications.
Facility address is an important piece of information for deaths, births and fetal deaths that occur in health care settings and are reported via an EHR, so support for a facility address data element as a core element would be beneficial.
Deaths in Hospital: The place of death for in-hospital deaths may be provided by a funeral director or the medical certifier. Since medical certifiers may document place of death, it would be useful to have facility information as a core data element within the medical certifier’s EHR.
Births and Fetal Deaths in Healthcare Settings: Most births and fetal deaths occur in a hospital or other health care facilities like birthing centers or clinic/doctor’s offices. When the mother or infant are transferred to another facility, the address of that facility also needs to be recorded.
Sources: U.S. STANDARD CERTIFICATE OF DEATH -- REV. 11/2003; Physician’s Handbook on Medical Certification of Death; Facility Worksheet for the Live Birth Certificate
Additionally, the facility address is required in both laboratory domain and public health. In the laboratory domain, the test ordering facility address needs to be included in the data as required by the CLIA Regulation §493.1241(c)(1). The address of the test-performing laboratory is also required as indicated by the CLIA regulation §493.1291(c)(2). Test ordering facility is also an “R” or a required field in Public health profiles in both Laboratory Orders Interface (LOI) and Laboratory Results Interface (LRI). We strongly support including this element USCDI V6.
Furthermore, CDC is requesting an Organization/Hospital Identifier data element be included as part of Facility Address. Explanation to request an Organizational Identifier.
The National Health Care Surveys includes two separate surveys: National Hospital Care Survey and National Ambulatory Medical Care Survey (NAMCS)
Facility Identifier: National Hospital Care Surveys would benefit from a Facility Identifier because they sample at the hospital level (i.e. the hospital from the sampled location is the only site of interest) and it is associated with the physical place of available services or resources.
The recommendation differs for NAMCS Health Center Component who samples at the health center level (i.e. every subsidiary care delivery site under the sampled health center is sampled along with the health center). For that reason:
Facility Managing Organization Identifier: NAMCS Health Center Component samples all care delivery sites under the sampled health center. To increase NAMCS quality control it would be helpful to receive Facility Managing Organization Identifier, as it is associated with health care provider locations and ambulatory providers.
Comment: CMS CCSQ supports the inclusion of "Facility Address" in USCDI Version 6 as it will supplement the core set of information necessary to identify facilities and link service and outcome data to a specific physical institution or facility.
The Alliance for Nursing Informatics (ANI) supports the inclusion of this data element and add our comments below. Please see previously submitted ANI comments for additional recommendations.
Consider how this applies to mobile or EMS services, which may not be tied to a fixed address. Excluding EMS from facility-based exchange risks missing data about care delivery at the first point of patient contact.
Guidance should clarify how to represent facilities spanning multiple physical locations and therefore have multiple addresses or alternatively have no addresses (i.e., mobile/EMS services).
Recommendation:Add the Facility Address data element to Final USCDI v6.
Rationale: The Facility Address data element will supplement the core set of information necessary to identify facilities and link service and outcome data to a specific physical institution or facility. Currently, in the absence of a unique Organization/Hospital Identifier data element in the USCDI, it can be difficult to differentiate specific service locations and link data or records for public health and healthcare purposes, such as monitoring hospital capacity and respiratory disease burden in acute care hospitals, identifying and responding to outbreaks in facilities, and tracking patient safety events. Accurate facility information, including name, address, and identifier, is essential to analyze facility level data and inform the allocation of resources such as therapeutics, supplies, staffing, and personal protective equipment (PPE) to prepare for and respond to emergency events.
CDC supports the inclusion of this data element in USCDI v5 as it is an element that may be necessary for calculation of our digital quality metrics from FHIR data.
Thank you for opportunity to comment on this data element. The Centers for Medicare and Medicaid Services (CMS) and the Centers for Disease Control and Prevention (CDC) emphasize the importance of patient safety being reflected in the USCDI standards. Identifying facility information, such as Facility Address, is critical to differentiate specific service locations and link data/records for public health and healthcare purposes. CMS and CDC strongly recommend the Facility Address data element (Level 2) in the Facility Information data class be added to USCDI. This addition would promote patient safety.
CMS-CCSQ recommends this Level 2 data element be added to USCDI v5. Together with the Facility Identifier, Facility Type, and Facility Name, the Facility Address data element will supplement the core set of information necessary to identify facilities and link service and outcome data to a specific physical institution or facility. This was previously identified as a joint CMS-CDC priority. Currently, in the absence of a unique Organization/Hospital Identifier in the USCDI, it can be difficult to differentiate specific service locations and link data or records for public health and healthcare purposes. Location information is routinely captured in EHR systems. Since Facility Names and Facility Identifiers (e.g., CCNs) can be shared by separately located facilities, Facility Address can provide critical identifying information to differentiate specific locations and accurately link data to optimally track care quality and health outcomes.
The facility address is required in both Laboratory Domain and public health. In the laboratory domain, the test ordering facility address needs to be included in the data as required by the CLIA Regulation §493.1241(c)(1). The address of the test-performing laboratory is also required as indicated by the CLIA regulation §493.1291(c)(2). Test ordering facility is also an “R” or a required field in public health profiles in both Laboratory Orders Interface (LOI) and Laboratory Results Interface (LRI). We recommend inclusion of this element USCDI V5
NAACCR comment: For cancer registry (and other public health) reporting, facility address is required to determine the jurisdiction with authority to collect and report the test and results.
CSTE Comment: CSTE agrees with CDC's recommendation for this data element.
The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.
If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.
If you are only commenting on a single data class or element, you may leave this field blank.
2. Select the Data Class
To specify which data class your comment addresses:
In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
Note that the Data Class field will automatically populate based on your current location in the platform:
If you are on a data class page, the field will be set to that specific data class
If you are on a data element page, the corresponding data class will be pre-selected
3. Select the Data Element
To specify which data element your comment addresses:
In the "Data Element" drop-down menu, select the specific data element you want to comment on.
The drop-down menu will display only the elements available under the data class you selected in the previous step.
You can use the search function within the drop-down to quickly locate a specific data element.
If you are commenting on the data class itself rather than a specific element, you may leave this field blank.
Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.
4. Optional: Propose New Data Class or Element
If you cannot find the appropriate data class or element for your comment:
Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.
5. Complete the Comment Form
Fill out the required fields in the comment form:
Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.
Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.
6. Optional: Add Additional Comments
If you need to comment on multiple data classes or elements:
After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
A new comment section will appear, allowing you to enter details for your additional comment.
For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
Complete the Subject and Comment fields for your additional comment.
Repeat this process for each additional comment you wish to submit.
Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.
7. Optional: Upload Supporting Files
The platform allows you to upload supporting documentation to enhance your comment:
Locate the "File Upload" section at the bottom of the comment form.
Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.
Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.
Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.
8. Optional: Save and Exit
If you need to pause your work and return to complete your comment later:
Click the "Save and Exit" button at the bottom of the form.
Your comment will be saved as a draft that you can access and complete later.
When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
Click this button to continue working on your draft.
You will be taken to a review page where you can:
Select "Submit Comment" to officially submit your feedback.
Click "Edit" to return to the comment form and make changes
Select "Discard Draft" to delete the saved draft and start fresh
Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.
9. Review and Submit
Once you have completed your comment:
Click the "Review and Submit" button at the bottom of the form.
This will take you to a review screen displaying your comment(s) in full.
Review all information for accuracy and completeness.
On this review screen, you have three options:
Click "Submit Comment" to officially submit your feedback
Click "Edit" to return to the comment form and make changes
Click "Discard Draft" to delete the comment and start fresh
The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.
Submitted by nedragarrett_CDC on
CDC's Comment for draft USCDI v6
CDC has recommended inclusion of this field since USCDIv4 supporting a number of applications.
Facility address is an important piece of information for deaths, births and fetal deaths that occur in health care settings and are reported via an EHR, so support for a facility address data element as a core element would be beneficial.
Deaths in Hospital:
The place of death for in-hospital deaths may be provided by a funeral director or the medical certifier. Since medical certifiers may document place of death, it would be useful to have facility information as a core data element within the medical certifier’s EHR.
Births and Fetal Deaths in Healthcare Settings:
Most births and fetal deaths occur in a hospital or other health care facilities like birthing centers or clinic/doctor’s offices. When the mother or infant are transferred to another facility, the address of that facility also needs to be recorded.
Sources: U.S. STANDARD CERTIFICATE OF DEATH -- REV. 11/2003; Physician’s Handbook on Medical Certification of Death; Facility Worksheet for the Live Birth Certificate
Additionally, the facility address is required in both laboratory domain and public health. In the laboratory domain, the test ordering facility address needs to be included in the data as required by the CLIA Regulation §493.1241(c)(1). The address of the test-performing laboratory is also required as indicated by the CLIA regulation §493.1291(c)(2). Test ordering facility is also an “R” or a required field in Public health profiles in both Laboratory Orders Interface (LOI) and Laboratory Results Interface (LRI). We strongly support including this element USCDI V6.
Furthermore, CDC is requesting an Organization/Hospital Identifier data element be included as part of Facility Address. Explanation to request an Organizational Identifier.
The National Health Care Surveys includes two separate surveys: National Hospital Care Survey and National Ambulatory Medical Care Survey (NAMCS)
Facility Identifier: National Hospital Care Surveys would benefit from a Facility Identifier because they sample at the hospital level (i.e. the hospital from the sampled location is the only site of interest) and it is associated with the physical place of available services or resources.
The recommendation differs for NAMCS Health Center Component who samples at the health center level (i.e. every subsidiary care delivery site under the sampled health center is sampled along with the health center). For that reason:
Facility Managing Organization Identifier: NAMCS Health Center Component samples all care delivery sites under the sampled health center. To increase NAMCS quality control it would be helpful to receive Facility Managing Organization Identifier, as it is associated with health care provider locations and ambulatory providers.