Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed references to OAuth2.0 since this is OOS for the Dec Connectathon.

...

Connectathon Report-Out:  View filenameDa Vinci Connectathon 22 Wrap Up PCDE.pptxheight250TBD

This track will use what version of FHIR.

...

Mark Scrimshire, mark@ekivemark.com

Joe Minieri/MITRE, , jminieri@mitre.org  

Expected participants

The PCovEx IG is focused on Payer to Payer Exchange. Three to four payer organizations are expected to participate in the Connectathon.

IMO (Possibly - GDolin will confirm ASAP)


Track Orientation

A webinar will be hosted on Go To Meeting to share further participation information about this track.

...

Present a HL7 FHIR R4 API with a capabilityStatement that supports the profiles and documents identified in the Payer Coverage Decision Exchange IG

The API should be protected via OAuth2.0 that complies with the SMART-on-FHIR app launch framework

Role 2 Receiving Server

Scenarios

For a newly enrolled member initiate an OAuth 2.0-based connection to the member's prior payer by following the SMART-on-FHIR app launch framework.

Query the source FHIR Server for the member and retrieve a Treatment Plan document.

...

  • Manually compiled Treatment plan with minimum information.
  • Receiving Server is registered in Source Server system with valid OAuth2.0 credentials


Success Criteria: Publish Treatment Plan via OAuth2.0 REST API

Bonus point:

Scenario Step 2 Retrieve Diabetes Treatment Plan

Action: Receiving Server retrieves Coverage Decision Exchange Document via an OAuth2.0 transaction by New Payer querying old payer for the newly enrolled member.

...

  • Receiving Server is registered in Source Server system with valid OAuth2.0 credentials
  • The member ID for former (old) payer is known.

Success Criteria: Plan successfully retrieves a FHIR document containing a Diabetes Treatment Plan document.

...

  • FHIR Documents to support a treatment plan are available.
  • Receiving Server is registered in Source Server system with valid OAuth2.0 credentials

Success Criteria: Receiving Server successfully retrieves a Treatment Plan

...

Action: Retrieve Coverage Decision Exchange Document via an OAuth2.0 transaction

Precondition: 

  • FHIR Documents to support a treatment plan are available.
  • Receiving Server is registered in Source Server system with valid OAuth2.0 credentials

Success Criteria: Plan successfully retrieves a FHIR document containing a CarePlan and supporting information.

...

Security and Privacy Considerations

Identify any expectations around security (e.g. will TLS, mutual-TLS, OAuth, etc. be required to participate

The exchange will not be OAuth2.0 based for this Connectathon.

OAuth 2.0 will be used for Authorization. Connections will follow the SMART-on-FHIR app launch framework.

A Receiving Server should be authorized to search for any member via their Member ID and retrieve the data for that member.

...