EMR Workflow Integration Using Clinical Decision Supports Hooks
Setup
Prerequisites:
- Sign up for an EMR Account and create a client application in the EMR system.
- Set up Salesforce:
- Setup the CDS services in Salesforce core.
- Create a user with required permissions.
Steps:
Set up the CDS application on MuleSoft:
- Log in to Salesforce and navigate to the setup page.
- Search for the ‘Integrations Setup’ page.
- Select the CDS Hooks API application and click Enable.
- Enter the application display name, target business group, and environment for deployment, and click Next.
- Click CDS Hooks API to add the properties.
| Key name | Sample value | Description | |
|---|---|---|---|
| 1 | sf.instanceURL | login.salesforce.com | Salesforce instance URL |
| 2 | sf.username | - | Username for connecting to Salesforce instance |
| 3 | sf.password | - | Password for connecting to Salesforce instance |
- Select the
Generic FHIR Clienttab and select the Authorization protocol as appropriate. - Here’s an example of JWT Authorization Protocol with Cerner sandbox for a generic FHIR client application:
| Key name | Sample value | Description | |
|---|---|---|---|
| 1 | Base URL | https://fhir-ehr-code.cerner.com/r4/123abc-5678-9123 | Base URL of the end system. |
| 2 | Token URL | https://authorization.cerner.com/tenants/123abc-5678-9123/protocols/oauth2/profiles/smart-v1/token | Token URL of the end system. |
| 3 | Client ID | - | Client ID for the end system. |
| 4 | Private Key | - | Upload the private key file |
| 5 | File Password | - | Private Key file password |
- To add an optional configuration, click the Add Additional parameters and enter the required details. For configuration details, refer to the following table:
| SNo | Application property name(Key name) | Sample value | Description |
|---|---|---|---|
| 1 | lob.JWT.algorithm | RS256 | Preferred algorithm for JWT Authentication. Default value: RS256. Supported Algorithms: RS256, RS384, RS512 |
| 2 | lob.JWT.exp | 5 | Expiration time for JWT (In Minutes) Default: 5 |
| 3 | lob.JWT.kid | - | Key Identifier for JWT |
- Click Proceed to deploy the application.
Post-Deployment:
MuleSoft endpoints can be triggered as mentioned in the API Documentation.
Note: The base path for all the endpoints is: /api/v1/. For example, the URL for the /cds-services endpoint is https://{hostname}/{basePath}/cds-services where the base path is ``/api/v1/```.