Da Vinci 1 Scheduling Generic Profile

The profile walks you through a scenario where a patient schedules an appointment with a Provider by using the Member’s Portal of a Payer:

The profile contains the following routes:

1 Practitioners Route

This route receives a request to return a list of available practitioners and returns the ID of the Provider selected by the patient.

2 Patients Route

This route receives a request to provide information on a specific patient required to schedule an appointment.

3 Slots Route

This route receives a request to provide a list of available appointment slots with a specific practitioner.

4a Provider Appointments Route

The route has two workflows depending on the request type.

Flow 1 (HTTP POST)

The patient selects a suitable time slot and submits a request to schedule an appointment with a Provider. The route receives a request to schedule an appointment with the slot ID and the patient ID that are passed as query parameters. Before the route creates a new appointment, the corresponding subroute retrieves the practitioner ID from the FHIR Server. The route submits the data required to schedule the appointment to the FHIR Server and when the appointment has been created successfully, the route returns a good response.

Flow 2 (HTTP GET)

The patient verifies that the appointment has been created successfully. The route receives a request and passes the patient ID and the appointment date as query parameters. The route searches for the appointment with matching patient ID on the FHIR server and returns a JSON-formatted data file with information on the newly scheduled appointment.

4b Payer Appointments Route

This route submits the information about a new appointment to the Payer's FHIR Server.