The Argonaut Data Query Implementation Guide is based upon the core FHIR DSTU2 API and it documents:
This specification describes four use cases and sets search expectations for each. For complete details and background, see Use Cases for the Argonaut Project.
Note, the Common MU Data Set referenced in the Use Cases is now the ONC 2015 Common Clinical Data Set .
The Argonaut data element query IG is intended to meet the 2015 Edition certification criterion for Patient Selection 170.315(g)(7) and Application Access – Data Category Request 170.315(g)(8). They were created for each of the 2015 Edition Common Clinical Data Set. Where applicable they are based on the HL7 U.S. Data Access Framework (DAF) FHIR DSTU2 Implementation Guide. However, the Argonaut use case and requirements per resource are a subset of those of the DAF implementation guide.
The table below lists the FHIR Resources used for the corresponding 2015 Edition Common Clinical Data Set (CCDS) Data elements:
|No||CCDS Data Element||FHR Resource|
|(3)||Date of birth||Patient|
|(9)||Medications||Medication, MedicationStatement, MedicationOrder|
|(11)||Laboratory test(s)||Observation, DiagnosticReport|
|(12)||Laboratory value(s)/result(s)||Observation, DiagnosticReport|
|(14)||(no longer required)||-|
|(16)||Care team member(s)||CarePlan|
|(18)||Unique device identifier(s) for a patient’s implantable device(s)||Device|
|(19)||Assessment and plan of treatment||CarePlan|
The Argonaut Profiles for each of the data element queries is listed below. Each profile defines the minimum mandatory elements, extensions and terminology requirements that MUST be present. Requirements and guidance are given in the profile narrative summary. A formal hierarchical table that presents a logical view of the content in both a differential and snapshot view is also provided along with references to appropriate terminologies and examples.
Note on Searches based on a date or date range:
The Argonaut Document Query Implementation guide defines how a provider or patient can retrieve a patient’s existing clinical document - specifically, transition of care and patient summary C-CDA CCD documents required for Meaningful Use. However other document formats, such as PDF, can be retrieved too. These are exposed in FHIR using a DocumentReference Resource: to index/search for them. This guide provides the minimal requirements to fetch a URL link to either a) patient’s existing documents which have been indexed or b) a “virtual” documents such as a CCD that could be created “on-demand”.
The Document itself can be subsequently retrieved using the link provided from the DocumentQuery search results. The link could be, for example, a FHIR endpoint (FHIR STU3) to a Binary Resource or some other document repository. The details of how to retrieve the document are not covered in this guide.
Patient or Provider search for a patient’s Documents
Assumptions and Preconditions
The Argonaut DocumentReference Profile defines the minimum mandatory elements, extensions and terminology requirements that MUST be present. Requirements and Guidance are given in a simple narrative summary. A formal hierarchical table that presents a [logical view: of the content in both a differential and snapshot view is also provided along with references to appropriate terminologies and examples.