This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

201801 Direct Track

From HL7Wiki
Revision as of 13:51, 31 October 2017 by 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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Return to Jan 2018 Proposals

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.


Expected participants

  1. Luis Mass – EMR Direct
  2. Bruce Schreiber – MaxMD
  3. Don Jorgenson - Inpriva
  4. Jim Fisher — MedAllies

Use Cases

(Under discussion)


Scenarios

The following scenarios will be exercised within the track:

  1. Sending FHIR resources within a Direct Message as an attachment
    1. Tasks will be documented after approval of use case
  2. Utilizing Direct Trust certificates with the FHIR RESTful API to enable trust relationships to scale
    1. 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

References

Direct, DirectTrust, and FHIR: A Value Proposition