2nd DSTU Draft For Comment

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

U.S. Data Access Framework (DAF) List Profile (Conformance Package)

Scope and Usage

This profile sets expectations for use of the List resource to return results for DAF queries within the Data Access Framework (DAF) Implementation Guide. This profile identifies which core elements,extensions,vocabularies and value sets must be supported by DAF actors.

For the purposes of this profile, Supported means the following:

Query Results:

Query Responders responding to queries SHALL use the DAF List profile to return results which contain more than one resource in the result set. This includes problem list, medication lists, allergies list.
Query Results returned by DAF Query Responder SHOULD contain the data elements identified as MUST SUPPORT in the profile.
Query Results returned MAY contain data elements not tagged as MUST SUPPORT by the this profile.
Query Requestor SHALL process the Query Results containing additional data elements without indicating that the response is an erroneous response.

Missing Information:

Query Responders SHALL use the DAF List profile to return a List with no entries and an appropriate emptyReason when queries for a Patient's problem list, allergies list and medication list result in no entries to be returned.
When Query Results do not contain a particular data element identified as MUST SUPPORT, Query Requestors SHALL interpret the results to mean that the Query Responder did not have information and there is no further qualifying information as to why the information is missing.
In cases, where the Query Responder knows precisely the reason why the data is missing (e.g notasked in the data-absent-reason value set), then Query Responders MAY provide this additional information using the extension element as part of the data element. Query Requestors SHALL correctly process the data-absent-reason extension without rejecting the response as an erroneous response.

SearchParameters:

DAF Query Requestor (client) SHALL be capable of querying the List resource using one or more of the search parameters for data elements tagged as MUST SUPPORT in this profile.
DAF Query Responder (server) SHALL be capable of receiving the queries submitted by the DAF Query Requestor and provide Query Results or error responses per the FHIR specifications.
DAF Query Responder MAY provide valid or error responses when the query parameters submitted contain data elements which are not tagged as MUST SUPPORT by this profile.

Relationship to Meaningful Use

The DAF Medication profile provides a mapping for the following Meaningful Use data elements to FHIR data elements.

Meaningful Use Data Element Name	FHIR Resource Mapping
Problem List	List with item referring to DAFCondition
No known Problems	List with no entries and a valid emptyReason
Allergies List	List with item referring to DAFAllergyIntolerance
No known Allergies	List with no entries and a valid emptyReason
Medication List	List with item referring to DAFMedicationStatement
No known Medications	List with no entries and a valid emptyReason
Immunization List	List with item referring to DAFImmunization
No known Immunizations	List with no entries and a valid emptyReason
Lab Results List	List with item referring to DAFResults
No known Results	List with no entries and a valid emptyReason
Patient List	List with item referring to DAFPatient
Encounter List	List with item referring to DAFEncounter
DiagnosticReport List	List with item referring to DAFDiagnosticReport

Meaningful Use Data Element Name

FHIR Resource Mapping

Problem List

List with item referring to DAFCondition

No known Problems