Da Vinci 2 Payer Provider Ex Generic

This profile serves as an example of 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 the patient data to the Provider in the form of CDS cards in a human-readable form.

PatientView Route

This route picks up a request to provide information on a specific patient. The route retrieves the required data from the Payer's FHIR server, and then posts the requested data to the Provider's FHIR Server.

Prepare Bundle Route

This subroute retrieves information on medications for a specific patient from the Payer's FHIR Server and aggregates all the patient's data previously pulled from the FHIR and the medication data into a single file. Then the route updates the MedicationStatement, forms a new FHIR Bundle, and sends the data for further processing to the parent route Upload to Provider.

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 patient data from the Payer's FHIR server by using the patient's first and last names.