201601 Data Access Framework (DAF)

DAF Patient, DAF Condition, DAF Medications and DAF Allergies

If creating a client, this track should require minimal work in advance of the connectathon, though at least a bit of preparation/reading on FHIR is recommended. If creating a server, advanced preparation will be required, but this scenario should somewhat limit the effort involved.

Pre-requisites: none

Submitting WG/Project/Implementer Group

Infrastructure and Messaging (I&M)

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 had some testing in outside organizations (e.g. Argonaut) and this is another opportunity to progress the profile up the Maturity Model.

Proposed Track Lead

Coordinator: Nagesth Bahsyam (Dragon)

Expected participants

The expected participants are those implementing DAF profiles, vendors planning to implement FHIR/DAF profiles for 2015 API certification criteria, vendors who are attending a Connectathon for the first time and want to participate, and folks that participated in the Argonaut Sprints in the fall of 2015.

Roles

FHIR Client

Enable the retrieval of the DAF Patient, DAF Condition, DAF Medications and DAF Allergy resources using the defined basic FHIR operations: READ and SEARCH following the conformance requirements http://hl7.org/fhir/dstu2/daf/conformance-daf-query-requestor.html for clients.

FHIR Server

Enable the retrieval of the DAF Patient, DAF Condition, DAF Medications and DAF Allergy resources using FHIR READ and SEARCH operations following the conformance requirements at http://hl7.org/fhir/dstu2/daf/conformance-daf-query-responder.html for servers. Servers are expected to have some data populated for each of the resources specified with appropriate linking between resources.

Steps

1. Retrieve Patient record

Action: DAF Requestor (client) queries the patient Service for a Patient record.

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

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 one or more search parameters.

Precondition: Patients with the search criteria have been created

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

3. Retreive DAF Condition or DAF Medication or DAF Allergy resources

Action: DAF Requestor (client) queries the Server for a DAF condition or DAF Medication or DAF Allergy resources

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

Success Criteria: DAF Condition or DAF Medication or DAF Allergy resource data is displayed in interface.

Bonus point: The Server supports multiple versions and Clients can query and display previous versions of DAF Condition or DAF Medication or DAF Allergy resources

4. Search for a DAF Condition or DAF Medication or DAF Allergy based on one or more parameters specified by DAF Responder conformance statement

Action: DAF Requestor (client) searches the Server for a DAF Condition or DAF Medication or DAF Allergy with one or more search parameters.

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

Success Criteria: DAF Condition or DAF Medication or DAF Allergy resource data is displayed in interface.

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

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.

TestScript(s)

The supporting TestScripts and corresponding fixtures have been committed to the FHIR SVN repository at: http://gforge.hl7.org/svn/fhir/trunk/connectathons/OrlandoJan2016/Connectathon11/

TestScript Definitions

The TestScript resources in this folder represent all of the possible variations** within the tests; i.e. JSON vs. XML content, client vs. server resource id assignment, and bonus vs. no bonus features.

**This representation of the Track 1 - Patient tests is not meant to be definitive and complete. This is one example of how these tests can be defined in the current DSTU2 format of the TestScript resource. Constructive feedback, suggestions and criticisms are welcome.

Based on these testing variations, the following TestScript definitions are available - one for each variation:

FHIR Resource ID Assigned by the Client

• track1-patient-base-client-id-json -- JSON Format - Baseline tests to create, update, retrieve history and search a patient, no extensions with client assigned resource id.
• track1-patient-base-client-id-xml -- XML Format - Baseline tests to create, update, retrieve history and search a patient, no extensions with client assigned resource id.
• track1-patient-bonus-client-id-json -- JSON Format - Baseline (Bonus) tests to create, update, retrieve history and search a patient, with extensions and client assigned resource id.
• track1-patient-bonus-client-id-xml -- XML Format - Baseline (Bonus) tests to create, update, retrieve history and search a patient, with extensions and client assigned resource id.

FHIR Resource ID Assigned by the Server

• track1-patient-base-server-id-json -- JSON Format - Baseline tests to create, update, retrieve history and search a patient, no extensions with server assigned resource id.
• track1-patient-base-server-id-xml -- XML Format - Baseline tests to create, update, retrieve history and search a patient, no extensions with server assigned resource id.
• track1-patient-bonus-server-id-json -- JSON Format - Baseline (Bonus) tests to create, update, retrieve history and search a patient, with extensions and server assigned resource id.
• track1-patient-bonus-server-id-xml -- XML Format - Baseline (Bonus) tests to create, update, retrieve history and search a patient, with extensions and server assigned resource id.

Conventions Used

The execution of the TestScript resources contained in this folder are constrained by the following conventions:

Fixtures - All resource reference values can be either url paths or local local file system paths. The convention for these TestScript resources use local file system paths where the execution engine is expected to resolve this path based on the following:

• Leading '/' character - this is resolved as an absolute path based on a known root path.
• No leading '/' character - this is resolved as a relative path based on the location of the TestScript resource file.