201605 Data Access Framework (DAF)

Return to May 2016 Proposals

DAF Observation, DAF DiagnosticReport

Extend DAF connectathon to include retrieval of laboratory results supporting both provider and patient access. This connectathon will address the question whether accessing a patient's laboratory results using the DAF Observation resource the DAF DiagnosticReport resource as the 'entry' point to the information.

DAF Patient, DAF Condition, DAF MedicationStatement and DAF Allergies

This is a continuation of the first DAF connectathon in January.

Pre-Requisites

This track should require minimal work in advance of the connectathon. If creating a server, advanced preparation will be required, but the scenarios listed below should limit the effort.

Review the FHIR Search API including:

• search by token
• search by reference
• search by date

Review U.S. Data Access Framework (DAF) FHIR Implementation Guide (IG) Including:

• DAF Patient Profile
• DAF Condition(Problem) Profile
• DAF MedicationStatment Profile
• DAF Allergies Profile
• DAF Results Profile
• DAF DiagnosticReport Profile

Submitting WG/Project/Implementer Group

Infrastructure and Messaging (I&M)

Orders and Observations (OO)

Justification

• This is a logical next step to FHIR connectathon Track 1 - Patient access that conforms to a specific profile.

• Its purpose is to provide a the next step for folks creating the simple FHIR client for accessing a patient. It is quite feasible to complete the client side of the track within a day with only knowledge of a development environment - no previous FHIR knowledge.

• The Data Access Framework (DAF) profiles have been by the the Argonaut project as a basis for their work. This is another opportunity to use test the profiles, identify issues, and help progress the standard and profile to maturity.

• The subsequent step is extending to accessing patient lab data and investigating how whether the DAF DiagnaosticReport Resource is needed for secondary access of lab data.

Proposed Track Lead

Coordinator: Nagesth Bahsyam (Dragon)

Track Lead: Eric Haas

Expected participants

The expected participants are those implementing DAF profiles, vendors planning to implement FHIR/DAF profiles for 2015 API certification criteria and participated in the Argonaut Sprints in the fall of 2015. This includes LIS Vendors, Large Labs, Application developers.

Roles

FHIR Client

Refer to the 2015 Edition Common Clinical Data Set for more information.

These requirements are intended to meet the 2015 Edition ONC Certification criterion Patient Selection 170.315(g)(7) and 170.315(g)(8).

• Enable the retrieval of the DAF Patient

• Enable the retrieval of all of a patient's Problems

• Enable the retrieval of all of a patient's Allergies

• Enable the retrieval of all of a patient's Medications

• Enable the retrieval of all of a patient's Lab Results

FHIR Server

The server is capable of returning all the search requests listed above following the conformance requirements at http://hl7.org/fhir/dstu2/daf/conformance-daf-query-responder.html for servers.

Servers are expected to have some prepopulated for each of the resources specified with appropriate linking between resources. See Testscript Section below for source files for each of the scenarios listed below: This is a starting point and should be supported by each server.

Please add your system information here: DAF Participant Tracker

Scenarios

1. Retrieve Patient record

Action: DAF Requestor (client) queries the patient Service for a Patient record using GET [base]/Patient/[id]

Precondition: There is a patient that has been created in the system.

Success Criteria: Patient's data is displayed in interface.

Bonus point: The Server supports multiple versions and Clients can query and display previous versions of the Patient using GET [base]/Patient/[id]/_history[vid]

2. Search for a patient based on one or more parameters specified by DAF Responder conformance statement

Action: DAF Requestor (client) searches the patient Service for patients with at least 2 patient elements - for example last name and gender GET [base]/Patient?family=[string]&gender=[code]

Precondition: Patients with the search criteria have been created

Success Criteria: patients displayed in interface. (use browser query to confirm)

3. Search for all Conditions or Medications or Allergies for a patient

Action: Server support query of DAF Condition, DAF MedicationStatement, DAF Allergy resources based on patient.id and Clients can query based on the Patient.id parameter.

Precondition: There is a DAF Condition or DAF MedicationStatement or DAF Allergy resourcesthat has been created in the system.

Success Criteria: All DAF Condition or DAF MedicationStatement or DAF Allergy resource data for a patient are displayed in an interface.

Bonus point: Server supports querying of DAF Condition, DAF MedicationStatement or DAF Allergy resources based on patient.id and date period and Clients can query based on the Patient.id and date period parameters.

4. Search for all Laboratory Results for a patient

Action: Server adn Client support query of DAF-Results (Observation Resource) based on patient.id and category = "laboratory"

NOTE: This assume laboratory tests and panels can be accessed using only the Observation resource instead of the DiagnosticReport resource. It will test whether the workflow based elements ( .request ) and report and display elements ( .codedDiagnosis, and .presentedForm ) in DiagnosticReport are needed for the DAF use cases.

Precondition: DAF-Results have been created in the system.

Success Criteria: DAF Observation resource data is displayed in interface.

Bonus point: Client and Server support date/period based querying of DAF-Results, Support for retrieving imaging data and anatomic pathology data.

Help Links

Here are some links to assist implementers:

• REST API in the Spefication.
• Patient resource in the Spefication.
• Java client sample.
• .net client sample.
• Publicly Available FHIR Servers for testing.

TestScripts

EH -TODOThe supporting TestScripts resources, corresponding test-case examples resources files, and test plan documents have been committed to the FHIR SVN repository at:

EH -TODOhttp://gforge.hl7.org/svn/fhir/trunk/connectathons/MontrealMay2016/Connectathon12/Track-11-LabOrders

>> Use an SVN browser such as Tortoise to view files

EH -TODOThere are 4 TestScripts definitions - one for each original test order:

• Test Order Number 100
• Test Order Number 200
• Test Order Number 300
• Test Order Number 400

EH -TODOFHIR Resource ID

>>todo add bonus testscripts