4b Payer Appointments Route

The route receives a POST request with a slot ID and a patient ID to create a new appointment on the Payer's FHIR Server. The corresponding route component checks to see if the incoming request contains all of the mandatory parameters, and then the route creates and submits a FHIR resource of Appointment type to the Payer's FHIR server. The appointment resource contains the practitioner ID, the slot ID, and the patient ID  that you extracted in the previous steps. If the appointment is created successfully, the route returns a good response message.

Route Structure

Da Vinci Profile Scheduling Generic Practitioner Route

Route Components Description

Component Name Component Type Description
Request Appointments RESTful Web Service Inbound Receives a request from the Member's Portal.
HTTP Router Redirects the data processing flow based on the request type.
405 Method Not Allowed RESTful Web Service Outbound Sends back an error message that the request type used is not allowed.
Parse JSON JSON Value Extractor Extracts the patient ID and the slot ID from the incoming request.
Required Params Router Checks to see if both of the required parameters have been extracted from the request.
400 Bad Request RESTful Web Service Outbound Sends back an error message that the request is missing a required parameter.
Velocity Velocity Compiles all the information required to create a new appointment.
Create Appointment FHIR Resources Creates a FHIR Resource with the information on the new appointment.
If Debug Mode_1 Router Checks to see if the debug mode is enabled. By default, the value of the DebugMode property in the profile environment is set to false.
Log Response File System Outbound Saves the response to the file system if the debug mode is enabled.
If Debug Mode Router Checks to see if the debug mode is enabled.
Log Request File System Outbound Saves the request to the file system if the debug mode is enabled.
Created? Router Checks to see if the new FHIR Resource for the appointment has been created successfully.
500 Internal Server Error RESTful Web Service Outbound Sends out an internal server error message.
Extract appointment id Groovy Extracts the appointment ID from the incoming data.
201 Created RESTful Web Service Outbound Send out a response that the appointment has been successfully created. The response header Location has a reference to the newly created appointment.
Update Selected Slot FHIR System Action Updates the slot selected for the appointment.
If Debug Mode_2 Router Checks to see if the debug mode is enabled.
Log Response_1 File System Outbound Saves the response to the file system if the debug mode is enabled.
If Debug Mode_3 Router Checks to see if the debug mode is enabled.
Log Request_1 File System Outbound Saves the request to the file system if the debug mode is enabled.
Any Error Error Channel Inbound Triggers the 500 Internal Server Error to send out an internal server error HTTP response when there are processing errors.
500 Internal Server Error RESTful Web Service Outbound Sends out an internal server error message.