D.3.1 Definitions, Interpretations and Requirements common to all DAF actors

This section outlines important definitions used in the DAF FHIR IG including interpretations that need to be used in the context of DAF and conformance requirements common to all DAF actors. The conformance verbs used are defined in FHIR Conformance Rules.

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

• DAF Responders SHALL be capable of including the data element as part of the query results as specified by the DAF conformance resources.
• DAF Requestors SHALL be capable of processing resource instances containing the data elements.
• In situations where information on a particular data element is not present and the reason is unknown, DAF Responders SHALL NOT include the data elements in the resource instance returned as part of the query results.
• When querying DAF Responders, DAF Requestors SHALL interpret missing data elements within resource instances as data not present in the DAF Responder's systems.
• In situations where information on a particular data element is missing and the DAF Responder knows the precise reason for the absence of data, DAF Responders SHALL send the reason for the missing information using values from the value set where they exist or using the dataAbsentReason extension.
• DAF Requestors SHALL be able to process resource instances containing data elements asserting missing information.
• NOTE: DAF Responders who do not have the capability to store or return a data element tagged as Supported in DAF profiles can still claim conformance to the DAF profiles using the DAF conformance resources.

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

• DAF Responders SHALL use the codes from the value sets identified by the DAF profiles, unless the value set does not contain codes that can be used at any level of granularity. For example, if the value set allows red, green and blue and your concept is "navy", you cannot use a new code, you have to use "blue" which subsumes this concept. However, if your concept is "white", you can use a new code.

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, and 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. The DAF FHIR IG does not require specific algorithms to be used as part of the implementation.

D.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.

• Conformance requirements for DAF Requestor actor, which is responsible for creating and initiating the queries for information about an individual patient or a set of patients.
• Conformance requirements for DAF Responder actor, which is responsible for providing responses to the queries submitted by the DAF Requestors.

D.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 Meaningful Use regulations, they are derived from the ONC 2014 Edition S&CC, which references other HL7 standards such as C-CDA, and HL7 v2.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. On review of C-CDA an implementer would find that the 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 the MU2 conceptual data elements and referenced standards, the DAF community further refined these data elements as DAF priority data elements in the individual profiles.