An episode defined by an interaction between a healthcare provider and the subject of care in which healthcare-related activities take place.

Data Element

Information from the submission form

Encounter status

Comment

Unified Comment from CDC

  • Data element description: Encounter Status is defined by HL7 US Core as the "Current state of the encounter." (http://hl7.org/fhir/us/core/StructureDefinition-us-core-encounter-definitions.html#Encounter.status) The value set for this data element includes such values as planned, in-progress and finished. (http://hl7.org/fhir/ValueSet/encounter-status)  
  • General Comment: Encounter Status is a required data element in the US Core Encounter Profile. (http://hl7.org/fhir/us/core/StructureDefinition-us-core-encounter-definitions.html#Encounter.status). 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 (http://hl7.org/fhir/us/davinci-pdex/USCoreEncounter.html) 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: http://www.hl7.org/fhir/smart-app-launch/scopes-and-launch-context/).  
  • Additional Applicable Standards: Da Vinci Payer Data Exchange http://hl7.org/fhir/us/davinci-pdex/STU1/ ; http://www.hl7.org/fhir/smart-app-launch/scopes-and-launch-context/ . 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