Information related to interactions between healthcare providers and a patient.

Data Element

Information from the submission form

Encounter status


Support to Advance Encounter Status

  • The PACIO (Post-Acute Care Interoperability) Project, established February 2019, is a collaborative effort between industry, government, and other stakeholders, with the goal of establishing a framework for the development of FHIR implementation guides to facilitate health information exchange.
  • The PACIO Community has published a Re-Assessment Timepoints FHIR implementation guide ( that profiles the US Core Encounter to support the representation of subsets of the longer encounters such as those found in post-acute care, behavioral health, and other residential settings. Because they represent parts of the larger encounter that is already a data class within USCDI, we believe that field-level requirements within that guide provide anecdotal support to proposed encounter data elements, including status, subject, identifier, participant, and reason for encounter. By providing real-world experience from implementations of the standard, we hope the Re-Assessment Timepoints implementation guide will help motivate the inclusion of these Encounter data elements within a future version of USCDI.
  • The PACIO Community also believes that the concept of an encounter subset that is at the core of the Re-Assessment Timepoints implementation guide is a useful data element to include within USCDI and we will propose this as a new data element.

CDC's Consolidated Comment

Supportive of this data element as an indicator of appropriate use and validity of associated data. More specifically, the status data element will help parse out complete encounter data (where status=finished) from in-progress and/or error encountered data.

Unified Comment from CDC

  • Data element description: Encounter Status is defined by HL7 US Core as the "Current state of the encounter." ( The value set for this data element includes such values as planned, in-progress and finished. (  
  • General Comment: Encounter Status is a required data element in the US Core Encounter Profile. ( The MedMorph Health Care Surveys use case is listed in ONDEC as one of the supporting use cases for this data element. Here is some additional information about how the MedMorph Health Care Surveys use case uses Encounter Status: The Health Care Surveys Content Implementation Guide describes how the MedMorph Backend Services App subscribes to encounter status and uses the encounter status of "finished" as the main trigger to evoke the MedMorph Backend Services App’s evaluation of finished encounter to assess whether it is an encounter that necessitates a health care survey to be generated, thus it is a crucial data element for this use case.  
  •  Estimate the number of stakeholders who capture, access, use or exchange this data element or data class: Encounter Status is captured and maintained in the vast majority of EHR products.  
  •  Additional Use Cases: Among other clinical and payment related use cases, the Da Vinci Payer Data Exchange 1.0.0 - STU1 ( IG includes Encounter Status as required data element. SMART on FHIR apps often need to determine which encounter is currently in-progress in the EHR which they ascertain by Encounter Status. (see:  
  • Additional Applicable Standards: Da Vinci Payer Data Exchange ; . This element is used by CMS Quality Reporting and is marked Required or MustSupport in the FHIR QI Core IG

Log in or register to post comments