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.1 Introduction

The nation is reaching a critical mass of HealthIT systems (EHRs, Data Warehouses etc) that comply with data and vocabulary standards including Meaningful Use Stage 2 (MU2) standards. The wide deployment of Meaningful Use Stage 2 compliant HealthIT systems has created unique opportunities for providers, provider support teams, healthcare professionals and organizations, etc. to access and use the patient data that is already collected during clinical workflows.

The deployed Health IT systems provide many access paths through their pre-defined interactions between a user and the system. However, they are limited in their support for data queries, APIs, or services to access data sets as needed. Where Health IT systems provide data access, they likely do not use industry standard access methods. Increasing support for this class of data access, using industry standards, would enable other applications to expand the ability of users to create value out of their data without having to rely on the predefined access paths.

Allowing access to this data can enable a provider to further analyze the collected data to understand a patient's overall health, the health of a provider's collective patient population, and use the data to power innovative new applications and tools to take better care of patients and populations.

The Data Access Framework (DAF) Initiative tries to leverage the HL7 FHIR and existing IHE standards to standardize access to Meaningful Use Stage 2 structured information both within the organization and from external organizations. DAF uses existing IHE profiles (XCA, MHD v2) to standardize access to documents such as a CCD, History and Physical Note etc. while HL7 FHIR is leveraged to access granular information such as problem lists, medications and patient demographics.

The standards and guidance incorporated into this implementation guide were based on the requirements defined in the DAF Use Cases document. Users of this implementation guide will benefit greatly from review of the DAF Use Case document. A very high level overview of the DAF actors and their interactions are as shown below:

The actors and their definitions are as follows

• DAF Requestor: The system that initiates the data access. This can be thought of as the client in a client-server interaction.
• DAF Responder: The system that responds to the data access request. This can be thought of as the server in a client-server interaction.

2.14.2.1.1 Initiative Overview

The Data Access Framework Initiative identifies and recommends standards for the interoperable representation and transmission of the following using the notion of a Query Stack which modularizes the various layers of the Data Access Framework. The DAF Query Stack using FHIR is as shown in the diagram below.

The DAF FHIR Implementation Guide will provide requirements and implementation guidance for the various layers of the DAF Query Stack which includes:

• Queries including structure, vocabularies and value sets
• Query Results including structure, vocabularies and value sets
• Transport Requirements
• Security and Privacy controls required for data access

This implementation guide provides guidance on the use of FHIR profile(s) for DAF. The profiles in this implementation guide will be used to meet DAF project objectives of:

• encouraging consistency around how data access is accomplished between healthcare systems within and across organizations between healthcare systems.
• encouraging consistency around what data is accessed including vocabularies and value sets.
• encouraging consistency around security standards used to allow authentication, authorization and auditing of data access.

2.14.2.1.2 Purpose

This implementation guide provides implementers with guidance on how to achieve conformance with the standards recommended by the Office of the National Coordinator for Health Information Technology (ONC) Standards & Interoperability Framework (S&I), DAF Initiative.

The implementation guide will explain how the FHIR resources (using the defined profiles) can be used to enable data access within and across enterprises. As well, it will describe secure interaction specifications using Representational State Transfer (REST) services to allow access to the desired resources.

The DAF profiles on the resources will identify the resource elements and extensions that must be supported to meet DAF use cases as well as constraints on their use.

Out of scope for this implementation guide:

• Describing Patient Matching algorithms
• Discovery of RESTful Resource endpoints
• Describing Patient Consent standards
• Specifying local policies related to data access, data disclosure or auditing
• Specifying code development languages for DAF