Da Vinci 2 Payer Provider Ex Generic

This profile illustrates a Payer-Provider data exchange scenario. In this scenario, the parties exchange data in the form of CDS hooks. The Payer receives a hook, extracts the patient data from the hook, and then uploads all the patient data onto the Provider's FHIR server. The Payer returns patient data to the Provider in the form of CDS cards in a human-readable form

PatientView Route

1. The route receives a POST request that carries a patient-view CDS hook.
2. The route extracts the CDS hook and retrieves the patient's first and last names, the Provider's FHIR server URL, as well as other patient-related information. Then, the route builds a FHIR bundle for the patient (Internal REST Route) by using the patient's first and last names.
3. The route uploads the created bundle to the Provider's FHIR server by retrieving the Provider's FHIR server URL from the received CDS hook.
4. As a result, the route returns a set of JSON-formatted CDS cards to the Provider. The cards contain patient-related information, such as general patient information, observations, allergies, and so on.

Upload to Provider Route

This route creates a new FHIR bundle with the patient data and uploads the bundle to the Provider's FHIR server.

Internal REST Route

The route retrieves the patient data from the FHIR server by using the patient's first and last names.