Goal
The goal of the Clinical Message Delivery(CMD) system is to route incoming messages from MirthResults to designated Provider Groups.
History
The Clinical Message Delivery System replaces the external feed.
Where do the providers come from?
Currently the providers are pulled from hl7 messages coming into MirthResults. The hl7 fields currently checked are:
- PV1.7,8,9,17
- PD1.4
- ORC.12
- OBR.16,28
- PD1.4
- ROL.4
Configuration
Requirements
- MirthResults 2.2 or later
- MirthConnect (the latest version if highly recommended)
Configuring MirthResults
Provider Group Configuration
- Start by creating a new Provider Group. The Provider Group area of MirthResults can be found by clicking the "Setup" menu item and then selection "Provider Groups" located in the "Provisioning" sub group.
- You should be now on a page with a list which may or may not contain Provider Groups.
- In the task action area of the page click "New Provider Group".
- Now you will see an edit page with some info required to create a new provider group.
Provider Group Configuration |
||
|---|---|---|
Label |
Description |
Required |
ID |
The unique id of the group |
Yes |
Label |
The easy to read label of the group |
Yes |
Group Type |
The type of Provider Group, currently General is the only option |
No |
Associated Subject Group |
Optionally pair a subject group with a provider group |
No |
Description |
Add any extra information here |
No |
Clinical Message Delivery Configuration
- Clinical Message Delivery is configured on the same page as the Provider Group as they are closely coupled.
- Currently there are 2 destination types and both will be covered below.
General Clinical Message Delivery Configuration |
||
|---|---|---|
Label |
Description |
Required |
Allowed Message Types |
A set of message types that are allowed to be passed through. |
No |
Destination Type |
There are currently 2 types of destinations, HTTP and MirthConnect 2.1.1. Each destination types has it's own set of properties. |
No |
Destination Types
 | Warning Switching between destination types will clear previously entered values for the destination type! |
 | Useful Information Be sure to test your settings by hitting the "Test Alert" task action AFTER saving your settings! |
HTTP Destination |
|||
|---|---|---|---|
Label |
Description |
Example |
Required |
Channel Name |
A set of message types that are allowed to be passed through. |
TEST_CHANNEL |
No |
Host |
IP/URL of where to send the message to |
http://localhost |
Yes |
Port |
Port to send the message to |
92001 |
Yes |
Mirth Connect 2.1.1 Destination |
|||
|---|---|---|---|
Label |
Description |
Example |
Required |
Channel Name |
The name of the channel we are sending to |
TEST_CHANNEL |
Yes |
Host |
IP/URL of the host of the MirthConnect box |
http://localhost |
Yes |
Password |
password of the user being used |
****** |
Yes |
User Name |
user name being used for this operation |
admin |
Yes |