QHIN (Kno2) - Integration

(0 reviews)

Setup guide

Prerequisites

  • Before deploying this application, ensure that the necessary entitlements are added into your Health Cloud org to utilize the Salesforce Healthcare APIs.
  • This asset leverages the Salesforce Healthcare APIs to synchronize patient demographics from a document retrieved from a responding provider organization via Kno2.

Dependent Applications

This solution leverages the following applications:

Note: The fields that need to be populated vary for the Generic FHIR Client Application based on the authentication methods supported by EMR system being used, so configure accordingly. Select the None option for the C-CDA to FHIR System API because there are no configurable fields to deploy the application successfully.

Anypoint Runtime Manager configuration

Some of the applications for this solution need to be configured manually.

Follow these steps to configure the Patient Summary - EMR integration application:

  • Enter hls-hc-fhir-r4-sync-prc-api in the Search Applications option.
  • Click the application name, and then click Settings to configure the application.
  • Click on the Runtime tab to configure the Worker size as a minimum of 1 vCore.
  • Click on the Properties tab to configure or override the properties, and then click Apply Changes to restart.

Required property overrides

At a minimum, the following properties must be configured to reflect the target deployment environment:

Property NameDescription
sys.emr.hostHost of the Generic FHIR Client System API instance
sys.emr.clientidClient Id of the Generic FHIR Client System API instance
secure::sys.emr.clientsecretClient Secret of the Generic FHIR Client System API instance

Follow these steps to configure the Generic FHIR Client application:

  • Enter generic-system-app in the Search Applications option.
  • Click the application name, and then click Settings to configure the application.
  • Click on the Properties tab to configure or override the properties, and then click Apply Changes to restart.

Required property overrides

At a minimum, the following properties must be configured to reflect the target deployment environment:

Property NameDescription
scopeList of scopes seperated with a space that are supported by the EHR system that is being configured. Look at the documemntation of the EHR System for supported scopes. For example, Cerner supports the following scopes which can be configured as values to this property as shown: system/Patient.read system/Patient.write system/Practitioner.read system/Practitioner.write

Salesforce Configurations

This solution also requires installation and configuration of a custom component that invokes the Mule APIs deployed. Refer to Patient Sync Lightning Web Component.


Reviews

TypeApplication
OrganizationMulesoft Inc.
Published by
MuleSoft Solutions
Published onMar 21, 2024
Asset overview
Industries CloudHealth
Custom fields

Asset versions for 1.0.x

Asset versions
VersionActions
1.0.2