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

Scope and Usage

This profile sets expectations for use of the Medication resource to record medication information that is prescribed,administered or dispensed for a patient 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:

SearchParameters:

• DAF Query Requestor (client) SHALL be capable of querying the Medication 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.

Query Results:

• 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:

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

Relationship to Meaningful Use

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

Boundaries and Relationships

This profile relies on the use of other profiles, some required, others available for use "when necessary":

• FHIR Extensibility defines how extensions can be applied to FHIR resources and data types. Specifically the data-absent-reason extension is used to code data elements with missing information when appropriate.