This wiki has undergone a migration to Confluence found Here


From HL7 Argonaut Project Wiki
Revision as of 13:04, 12 April 2016 by Brett Marquard (talk | contribs) (Created page with "Back to Argonaut Implementation Guide ==Introduction== The Argonaut Medications IG provides the API documentation for searching for and fetching a pat...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Back to Argonaut Implementation Guide


The Argonaut Medications IG provides the API documentation for searching for and fetching a patient's medications. It is based on the Data Access Framework (DAF) MedicationStatement Profile, DAF MedicationOrder Profile, and draws requirements from Argonaut Sprint 4. The search criteria provided in the Quick Start are intended to support the 2015 Edition ONC Certification criterion Data Category Request 170.315(g)(8).

Argonaut Success Criteria



  • A server is capable of returning a patient's allergies list using GET /Condition?patient=[id].
  • A server has ensured that every API request includes a valid Authorization token, supplied via:Authorization: Bearer {server-specific-token-here}
  • A server has rejected any unauthorized requests by returning an HTTP 401 Unauthorized response code.

Mandatory Data Elements

The following data-elements are mandatory (i.e data MUST be present). These are presented below in simple human-readable explanations along with sample data to demonstrate the requirements.

Each Condition must have:

  1. One Identification of the condition, problem or diagnosis in Condition.code.
  2. One patient reference in Condition.patient
  3. One clinical status in Condition.clnicalStatus

Additional elements from DAF MedicationStatement Profile] or DAF MedicationOrder Profile] may be present.

Condition Resource Example

Quick Start

Below is a quick overview of the required search and read operations.

GET /Condition?patient=[id]

Support: Mandatory to support search by patient.

Implementation Notes: Search for all conditions (a.k.a. problems) for a patient. Fetches a bundle of all Condition resources for the specified patient (how to search by reference).

Response Class:

  • (Status 200): successful operation
  • (Status 400): invalid parameter
  • (Status 401/4xx): unauthorized request
  • (Status 403): insufficient scope



Open Issues

The following issues have been identified:

  • Status based search


Formalized testing with test scripts and objective results reporting is available through the participation of AEGIS and MITRE (Crucible). The testscript provided can be used to test servers: [todo]


Back to Argonaut Implementation Guide