Difference between revisions of "201605 Data Access Framework (DAF)"
| Line 41: | Line 41: | ||
===FHIR Client=== | ===FHIR Client=== | ||
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| − | Enable the retrieval of the DAF Patient, DAF Condition, DAF MedicationStatement | + | Enable the retrieval of the DAF Patient, DAF Condition, DAF MedicationStatement, DAF Allergy, DAF Observation, DAF DiagnosticReports, DAF Specimen, 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=== | ===FHIR Server=== | ||
Revision as of 01:08, 9 February 2016
DAF Result
Extend DAF connectathon to include retrieval of Lab Results supporting both provider and patient access to lab results.
DAF Patient, DAF Condition, DAF MedicationStatement 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)
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 had some testing in outside organizations (e.g. Argonaut) and this is another opportunity to progress the profile up the Maturity Model.
The subsequent step is extending to accessing patient 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, 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.
For Patient Results access the expected participants are those implementing DAF results profiles and vendors planning to implement the DAF profile for provider and patient access to results. This includes LIS Vendors, Large Labs, Application developers.
Roles
FHIR Client
Enable the retrieval of the DAF Patient, DAF Condition, DAF MedicationStatement, DAF Allergy, DAF Observation, DAF DiagnosticReports, DAF Specimen, 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 MedicationStatement 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.
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.
- 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 MedicationStatement or DAF Allergy resources
- Action: DAF Requestor (client) queries the Server for a DAF condition or DAF MedicationStatement or DAF Allergy resources
- Precondition: There is a DAF Condition or DAF MedicationStatement or DAF Allergy resources that has been created in the system.
- Success Criteria: DAF Condition or DAF MedicationStatement 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 MedicationStatement or DAF Allergy resources
4. Search for a DAF Condition or DAF MedicationStatement 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 MedicationStatement or DAF Allergy resourcesthat has been created in the system.
- Success Criteria: DAF Condition or DAF MedicationStatement or DAF Allergy resource data is displayed in interface.
- Bonus point: Server supports querying of DAF Condition, DAF MedicationStatement 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:
