|Configuring Connectors / Mirth Connect for PeraHealth|
Depending on the configuration you set up, you will need either four or two Mirth channels.
In this integration, the PeraHealth HL7s fields are mapped similar to the CWE HL7s fields and output JSON file. Subsequently it is sent to HL7 folder of Message Generator of CWE.
|PHHL7Receiver.xml||TCP listener channel that listens on port 6661 for HL7 messages. It forwards the individual messages to the 'PHJSONCreator' channel. The destination of this channel is Channel writer.|
|PHJSONCreator.xml||Used to transform the message into JSON and subsequently forwards the JSON to the load balancer on port 6666.|
|PHJSONReceiver.xml||It is the LLP listener that listens on port 6666. The destination of this channel is the file writer that writes the JSON file in the HL7 directory|
|PHMonitor.xml||TCP listener channel, that is, it acts as the monitor channel for load balancer and listens on port 5000.|
Following are the three types of alarms sent from the PeraHealth system:
For a high-availability environment, Vocera recommends the following configuration:
In this configuration, two CWE servers are behind a load balancer, and Mirth Connect is installed on each of these servers. For each copy of Mirth, you must create the following channels:
On each copy of Mirth, follow the instructions in Importing an Existing Channel to import the channels, and then configure the channels as follows:
If it is a single CWE server deployment, then only two channels PHHL7Receiver.xml and PHJSONCreator.xml must be imported and deployed. In this case, the destination of PHJSONCreator should be HL7 directory path instead of LLP sender.
After you have configured your Mirth channels, you can add additional alarm reasons or alarm levels if needed. See Configuring a New Alarm Reason and Configuring a New Alarm Level for more information.