Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: identified 3 flows for exchange


Role 1 Source Server


There are three scenarios to be tested:

  1. IN-FLOW: Member-authorized Exchange of Patient/$Everything bundle. Member connects to old plan from new plan and authorizes an exchange directly. Previously tested in Jacksonville. This exchange also supports Member-authorized exchange with a third-party application.
  2. INDIRECT-FLOW: Member-authorized exchange of Patient/$Everything bundle via a request made by the Member to the New Payer. i.e. Please go and get my data from my old plan.
  3. ENROLLMENT-FLOW: Payer-to-Payer HIPAA Business, Treatment and Operations covered exchange of Patient/$Everything bundle. When a new Member is enrolled in a health plan the plan identifies the old health plan and requests the Member's information from the old plan without requiring an authorization by the member.

These scenarios can use the same mechanisms to perform the exchange. ie. REST-based GET to an OAuth 2.0 protected API Endpoint . The difference will be the entity requesting an OAuth2.0 token.

Present a HL7 FHIR R4 API with a capabilityStatement that supports the following profiles and operations: