Information related to interactions between healthcare providers and a patient.

Data Element

Encounter Participant


Support to Advance Encounter Participant

  • 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 to link providers responsible for a patient’s care across encounters. This use case is valuable for chronic-like infectious conditions like HIV, viral hepatitis, and tuberculosis.

Unified Comment from CDC

  • Data element description: Encounter Participant is defined by HL7 US Core as “The list of people responsible for providing the service.” for the encounter. (
  • General Comment: Encounter Participant is a Must Support data element in the US Core Encounter Profile. Encounter Participant for the MedMorph Health Care Surveys use case is used to link participating providers to an ambulatory encounter. and the MedMorph Cancer Registry Reporting use case can use encounter participant to link providers responsible for a patient’s care across encounters.
  • Additional Use Cases: Among many other clinical and payment related use cases, Da Vinci Payer Data Exchange 1.0.0 - STU1 ( uses Encounter Participant.
  • Additional Applicable Standards: Da Vinci Payer Data Exchange

MedMorph submitted multiple…

MedMorph submitted multiple elements for the Encounter class that were modeled directly from the mustSupport elements of the US Core Encounter profile. What has been proposed in USCDI does not reflect the same structure and we believe will cause difficulty by those using the US Core structure. We are struggling to figure out the linkages between USCDI classes. It has been noted that several elements of an Encounter Participant (e.g., role, NPI, name, etc.) are found in the Care Team Member class, but what information would be exchanged using USCDI Encounter Participant?  Can you get a list of the Participant names? Or, is the Encounter Participant element simply "link" to the Care Team Member class where you can get Name, NPI, etc. ? If so, that needs to be defined/explained in USCDI. 

Encounter Participant is widely available

This data element appears in HL7 V2 Messages in PV1-7,8,9 and 17 and PD1-4, and are exchanged 40-80% of the time (depending on field) in HIEs I have direct experience with.

In C-CDA Documents it can be found in performer (see performer at, and as demonstrated in is widely available and supported in many EHR systems, and other evidence available through participation in prior IHE Connectathons demonstrates that it covered by EHR systems that are available to 85% or more of the provider market.

In FHIR DSTU2 it can be found in Encounter.participant, and in the current US Core (FHIR R4 based) is a must support element (see )

In other words, it is widely available, implemented in software products, and exchanged in physician practice, HIE and in some cases to public health as well.





Log in or register to post comments