Appointment Scheduling Integration - Application
Setup guide
Prerequisites
Prior to deploying this application, ensure your EHR has required permissions for Appointment Scheduling APIs and configured with the necessary scopes.
Dependent Applications
This solution leverages the following applications:
- Generic FHIR Client to connect with an EHR system. It can be configured to use JSON Web Token (JWT) or Client Credentials as the authorization protocol (will vary depending on the supported protocols by the EHR system).
Note:
- Required EHR authorization parameters are being sent as headers from the Process API when invoking the Generic FHIR Client. Please set the Authorization Protocol to None for the Generic FHIR Client.
- In this use case, we are using JSON Web Token (JWT) as the authorization protocol for Epic and Client Credentials as the authorization protocol for Cerner.
UI Configuration Properties
Configure the following properties to connect with related EHR system.
| Property Name | Description |
|---|---|
| cerner.baseUrl | Cerner EHR Base URL |
| cerner.tokenUrl | Cerner EHR Token URL |
| cerner.clientId | Cerner EHR Client Id |
| secure::cerner.clientSecret | Cerner EHR Client Secret |
| epic.baseUrl | Epic EHR Base URL |
| epic.tokenUrl | Epic EHR Token URL |
| epic.clientId | Epic EHR Client Id |
| secure::epic.privateKey | Epic EHR Private Key |
| primary | Primary EHR System |
Note:
- If you are using only one of the EHR system either Cerner or Epic, then configure other EHR system properties with dummy values.
- Primary EHR System value(primary) is case sensitive. This value must be epic or cerner based on EHR system used.