This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

2.14.2.0 U.S. Data Access Framework (DAF) FHIR Implementation Guide (IG)

This implementation guide is prepared as a U.S. Realm Specification on behalf of the U.S. Office of the National Coordinator (ONC). However, much of the content is relevant to other jurisdictions.

2.14.2.0.1 Draft Standards for Trial Use (DSTU) Ballot

This DAF FHIR Implementation Guide is undergoing a DSTU ballot. The focus of the ballot is limited in scope to the IG, the profiles, operations, value sets and conformance statements it defines, though comments on the underlying resources will also be accepted. This guide will be balloted separately from the FHIR specification itself.

2.14.2.0.2 Background

2.14.2.0.3 Specification and Conformance Requirements

The DAF FHIR IG contains four sections which as follows

2.14.2.0.3.1 Definitions, Interpretations and Requirements common to all DAF actors

This section outlines important definitions used in the DAF FHIR IG, interpretations that need to be used in the context of DAF and conformance requirements common to all DAF actors. The conformance verbs used along with its interpretation is outlined in FHIR Conformance Rules.

In the context of DAF profiles, Supported on any data element SHALL be interpreted as follows:

Value Set bindings and interpretation: In the context of DAF profiles, value set bindings of (required, extensible) for specific data elements SHALL be interpreted as follows:

FHIR Infrastructure usage: DAF uses FHIR RESTful API based on HTTP protocol along with FHIR data types, FHIR search and both xml and json FHIR Resource Formats.

Search Guidance: DAF profiles support the searching (querying) of resources such as Medications, Encounters, Problems, AllergyIntolerances, Procedures for a particular patient. In order to achieve this in implementation, DAF actors SHOULD use Patient.identifier field to precisely identify the resources relevant to the patient. While other search parameters such as Patient.name, Patient.given could be used as part of the query, incorrect Patient matching could lead to incorrect results.

Patient Matching Guidance: Patient Matching rules and related criteria have to be evaluated by the organization implementing DAF actors to ensure compliance with local policies and regulations. DAF FHIR IG does not require specific algorithms to be used as part of the implementation.

2.14.2.0.3.2 Conformance Requirements for each DAF actor

This section outlines conformance requirements for each of the DAF actors identifying the specific profiles that need to be supported, the specific RESTful operations that need to be supported, and the search parameters that need to be supported. Note: The individual DAF profiles identify the structural constraints, terminology bindings and invariants, however implementers must refer to the conformance requirements for details on the RESTful operations, specific profiles and the search parameters applicable to each of the DAF actors.

2.14.2.0.3.3 DAF profiles, extensions and constraints

This section outlines the DAF profiles created using FHIR resources and include both extensions and constraints on top of the base FHIR Resources. DAF profiles were created for each conceptual data element identified in the ONC 2014 Edition Standards and Certification Criteria (S&CC) related to Meaningful Use Stage 2 (MU2). The table below provides a top-level mapping of the ONC 2014 edition S&CC conceptual data elements to the corresponding DAF Resource profile along with the identification of the base FHIR resource. In addition, within each profile, granular data elements are listed in the "Meaningful Use Data Element Mapping" section of each DAF profile description. While many of these granular data elements were not explicitly mentioned in ONC or CMS MU2 regulations, they are derived from the fact that the ONC 2014 Edition S&CC references other HL7 standards such as CCDA, HL7v2.5.1 implementation guides for lab reporting and immunizations. These standards identify granular data elements to represent the MU2 conceptual data elements and hence are identified in the individual DAF profiles. (For example, MU2 simply says "Medication Allergies" are required. But drilling down into CCDA would indicate that Allergy Substance, Reaction, etc. are part of what comprises a Medication Allergy along with specific constraints on what is required and optional). In addition to deriving the granular data elements from MU2 conceptual data elements and referenced standards, the DAF community further prioritized these data elements and hence are called as DAF priority data elements in the individual profiles.

Meaningful Use conceptual data element DAF profile FHIR Resource
Medication allergies DAFAllergyIntolerance AllergyIntolerance
Laboratory Order(s) DAFDiagnosticOrder DiagnosticOrder
Laboratory Test(s) DAFDiagnosticReport DiagnosticReport
Encounter Diagnoses DAFEncounter Encounter
Family Health History DAFFamilyHistory FamilyHistory
Immunizations DAFImmunization Immunization
Laboratory Result Value(s) DAFLabResults Observation
Medications DAF profiles for medications,DAFMedication, DAFMedicationStatement,DAFMedicationAdministration Medication,MedicationStatement,MedicationAdministration
Patient name, Sex, Date of Birth, Race, Ethnicity, Preferred Language DAFPatient Patient
Problems DAFCondition (Problem) Condition
Procedures DAFProcedure Procedure
Smoking status DAFSmokingStatus Observation
Vital Signs (Height, weight, BP, BMI) DAFVitalSigns Observation
Problems, Medications and Medication Allergies List DAFList List

2.14.2.0.3.4 Security Implementation Guidance

This section outlines security implementation guidance for the DAF FHIR IG.

The following is a list of outstanding issues that need to be addressed.

2.14.2.0.4 Author Information

Author Name
Brett Marquard (Primary)
Nagesh Bashyam (Primary)
Grahame Grieve (Supporting)
Lloyd McKenzie (Supporting)