STU 2 Ballot

This page is part of the Data Access Framework (v1.6.0: STU 2 Ballot 1) based on FHIR v1.6.0. . For a full list of available versions, see the Directory of published versions

D.7.0 U.S. Data Access Framework (DAF) Encounter profile

D.7.0.1 Scope and Usage

This profile sets expectations for use of the Encounter resource within the DAF FHIR IG. This profile identifies which core elements, extensions, vocabularies and value sets must be Supported by DAF actors. For the definition of Supported please refer to DAF FHIR IG. The data elements identified by the profile are based on ONC 2014 Edition S&CC and DAF use cases. The mappings between the ONC 2014 Edition S&CC data elements and DAF data elements are captured in the table below, where the first column identifies the ONC 2014 Edition S&CC data element name, the second column maps the ONC 2014 Edition S&CC data elements to DAF data elements which are derived from ONC 2014 Edition S&CC standards and DAF use cases and lastly the third column identifies the mapping to FHIR resources and attributes.

D.7.0.2 Meaningful Use Data Element Mapping

The DAF-Encounter profile mapping to Meaningful Use data elements and FHIR Resources are as shown below.For an overview of how the DAF profiles and data elements were derived from ONC 2014 Edition S&CC please refer to DAF FHIR IG data mapping section.


Meaningful Use Data Element Name Mapping to Priority DAF Data Elements FHIR Resource Mapping
Encounter Diagnoses
Encounter Start/End Time Encounter.period
Specific Encounter Type Encounter.type
Encounter class Encounter.class
Encounter Location Encounter.location.location
Encounter Admission and Discharge Dates Encounter.hospitalization.period
Performer Encounter.participant.individual
Encounter Reason Encounter.reason

D.7.0.3 Boundaries and Relationships

This profile relies on the following other profiles:

  • DAF-Patient is used by DAF-Encounter profile to refer to patients.
  • FHIR Extensibility defines how extensions can be applied to FHIR resources and data types. Specifically the data-absent-reason extension can be used to code data elements with missing information when appropriate. See DAF FHIR IG for additional guidance.

D.7.0.4 Content

Profiles:
DAF-EncounterDefines constraints and extensions on the Encounter resource for use in querying and retrieving a patient's encounter related information.

D.7.0.4.1 Search Parameters

The full list of supported search parameters are can be accessed at DAF Requestor conformance expectations and DAF Responder conformance expectations.

D.7.0.4.2 Example Usage Scenarios

The following are example usage scenarios for the DAF-Encounter profile:

  • Query for encounters experienced by a Patient
  • Query for all encounters during a time period
  • Query for all encounters based on class(e.g. outpatient,inpatient) and specific encounter reason (e.g diabetes,cancer)
  • Query for encounters based on location

D.7.0.4.3 Profile specific implementation guidance

There is no additional profile specific implementation guidance, please refer to DAF FHIR IG for implementation guidance common to all profiles.