Difference between revisions of "201801 Direct Track"
Calvinbeebe (talk | contribs) (Created page with "[http://wiki.hl7.org/index.php?title=Category:201801_FHIR_Connectathon_Track_Proposals Return to Jan 2018 Proposals] Category:201801_FHIR_Connectathon_Track_Proposals|Jan 20...") |
Calvinbeebe (talk | contribs) |
||
| Line 14: | Line 14: | ||
In addition for track 1, participants will need a Direct implementation that can send / receive direct messages with attachments. | In addition for track 1, participants will need a Direct implementation that can send / receive direct messages with attachments. | ||
| + | ==Track Administration== | ||
| + | *Coordinator: Luis Mass, EMR Direct | ||
| + | *Coordinator: Calvin Beebe, Mayo Clinic - cbeebe@mayo.edu | ||
| + | *Management & Communications: Dr. David Kibbe - DirectTrust President and CEO - david.kibbe@directtrust.org | ||
==Expected participants== | ==Expected participants== | ||
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | ||
| − | + | *Luis Mass – EMR Direct | |
| − | + | *Bruce Schreiber – MaxMD | |
| − | + | *Don Jorgenson - Inpriva | |
| − | + | *Jim Fisher — MedAllies | |
==Use Cases== | ==Use Cases== | ||
Revision as of 14:01, 31 October 2017
Contents
Direct
FHIR is a new standard that defines a web API and related specifications for health data exchange. Direct is an existing federal standard that is widely used in the USA for the exchange of healthcare data. Within the Direct community, Direct Trust provides scalable security and a trust framework through legal contracts, formal policies, accreditation, and a PKI-based trust authority. Because there is such expenditure involved in planning, setting up and maintaining trusted distribution networks, there is strong incentive to leverage existing networks as much as possible. Therefore, this track will explore two possible models of leveraging DirectTrust’s trust framework.
They are:
- Sending FHIR resources within a Direct Message as an attachment
- Utilizing DirectTrust certificates with the FHIR RESTful API to enable trust relationships to scale
Pre-Requisites
For all levels of testing the required pre-requisite is the fundamental requirement that all FHIR servers SHALL support the capabilities interaction.
In addition for track 1, participants will need a Direct implementation that can send / receive direct messages with attachments.
Track Administration
- Coordinator: Luis Mass, EMR Direct
- Coordinator: Calvin Beebe, Mayo Clinic - cbeebe@mayo.edu
- Management & Communications: Dr. David Kibbe - DirectTrust President and CEO - david.kibbe@directtrust.org
Expected participants
- Luis Mass – EMR Direct
- Bruce Schreiber – MaxMD
- Don Jorgenson - Inpriva
- Jim Fisher — MedAllies
Use Cases
(Under discussion)
Scenarios
The following scenarios will be exercised within the track:
- Sending FHIR resources within a Direct Message as an attachment
- Tasks will be documented after approval of use case
- Utilizing Direct Trust certificates with the FHIR RESTful API to enable trust relationships to scale
- Tasks will be documented after approval of use case
Help Links
Here are some links to assist implementers:
TestScript(s)
TBD
Results
FHIR Connectathon 17 will be held on January 27-28, 2018 in New Orleans. A link to download the report will be available after the conclusion of the Connectathon
