Mirth Channel Setup

Create the Synura outbound channel in Mirth Connect. These steps apply to all versions (3.x and 4.x).

Mirth 3.8.1 users: Do not import channel XML. A known XStream bug causes imports to fail with InvalidChannel. Create channels manually through the GUI.

---

1. Create a New Channel

1. Open the Mirth Connect Administrator and log in.
2. In the left panel, click Channels.
3. Click New Channel (or right-click in the channel list and select “New Channel”).
4. Set the following on the Summary tab:
   • Name: Synura MLLPS Send (or any name that makes sense for your organisation)
   • Description: (optional) Sends HL7 messages to Synura over MLLPS
   • Leave all other settings at their defaults.

---

2. Configure the Source Connector

1. Click the Source tab.
2. Set Connector Type to Channel Reader (the default). This lets other channels or manual sends route messages into this channel.
3. No further source configuration needed.

---

3. Configure the Destination Connector

1. Click the Destinations tab.
2. Select Destination 1.
3. Set Connector Type to TCP Sender.
4. Set Transmission Mode to MLLP.

Using the Synura TLS Proxy (Path A) or Enterprise TLS Proxy (Path D)

If you are using the Synura TLS Proxy (stunnel) or your own enterprise TLS proxy:

5. Set Remote Address to:

   localhost

6. Set Remote Port to:

   2575

   (Or whichever port your TLS proxy is listening on.)

7. Do not enable SSL/TLS on the Mirth connector. The proxy handles encryption.

8. Leave all other settings at their defaults:
   • Keep Connection Open: Yes (recommended)
   • Response Timeout (ms): 10000

Using a Commercial TLS Plugin (Path B or C)

If you have the NextGen SSL Manager or Zen SSL Extension installed:

5. Set Remote Address to:

   {subdomain}.synura.io

   Replace {subdomain} with your assigned Synura subdomain.

6. Set Remote Port to:

   443

7. Enable TLS/SSL using your plugin’s settings on the connector. Ensure the minimum TLS version is TLS 1.2.

8. Leave all other settings at their defaults:

   • Keep Connection Open: Yes (recommended)
   • Response Timeout (ms): 10000

---

4. Save and Deploy

1. Click Save Changes (or Ctrl+S).
2. Go to the Dashboard.
3. Select the new channel and click Deploy Channel.
4. Status should change to Started.

---

5. Send a Test Message

1. In the Dashboard, select your deployed Synura MLLPS Send channel.

2. Click Send Message in the toolbar.

3. Paste a valid HL7 v2 message into the text box. A minimal ADT^A01 example:

   MSH|^~\&|SENDING_APP|SENDING_FACILITY|SYNURA|SYNURA|20240101120000||ADT^A01|MSG00001|P|2.3
   EVN|A01|20240101120000
   PID|1||TESTPID001^^^MRN||TEST^PATIENT||19800101|M
   PV1|1|I|WARD1^ROOM1^BED1

   Replace SENDING_APP and SENDING_FACILITY with the values registered in your Synura configuration.

4. Click Process Message.

---

6. Verify the Result

Successful Send

• Message status in the Dashboard shows SENT with a green indicator.

• Response tab for the message shows an HL7 ACK with acknowledgement code AA (Application Accept):

  MSH|^~\&|SYNURA|SYNURA|SENDING_APP|SENDING_FACILITY|20240101120001||ACK^A01|ACK00001|P|2.3
  MSA|AA|MSG00001

• The message appears in your Synura dashboard inbound log.

Failed Send

If the message fails, check the following:

Status	Meaning	What to Do
ERROR	Mirth could not connect to the destination	Check Remote Address and Port. For stunnel users, verify stunnel is running. See Troubleshooting.
QUEUED	Message is waiting to be sent (destination unreachable)	Same as ERROR — check connectivity. The message will retry automatically.
SENT but no response	Message was sent but no ACK came back	Increase Response Timeout. Check that your sending facility is configured in Synura.
SENT with AE or AR	Synura received the message but rejected it	Check the MSA segment in the response for the error reason. Common causes: invalid message format, unrecognised sending facility.

Viewing Message Details

1. Click the channel name in the Dashboard to open the Message Browser.
2. Click a message to expand it.
3. Destination tab shows the raw sent message and response.
4. Errors tab shows failure details if the status is ERROR.

---

Notes

• Channel Reader source means this channel receives messages from other Mirth channels or manual sends. If you need to read from a file, database, or other source, configure that on a separate channel and route messages to this one.
• Keep Connection Open is recommended for performance. Synura supports persistent connections.
• If you have multiple destinations (e.g. sending to Synura and a local archive), add a second destination to the same channel rather than creating a separate channel.