Monitor Mirth Connect with Loft

Prerequisites

The Loft desktop app installed and signed in. Loft is a Pro product; it provides the pidgeon loft commands and the local Bridge on localhost:5100. The free dotnet tool install --global Pidgeon.CLI build does not include loft.
Access to Mirth Connect’s file writer output directories.
A vendor profile for your message patterns (optional but recommended). pidgeon config analyze is in the free CLI.

Step 1: Identify Mirth output directories

Mirth Connect file writer destinations typically save to a configured directory. Common paths:

/var/mirth/outbound/er-adt/
/var/mirth/outbound/lab-results/
/var/mirth/outbound/pharmacy/

Check your Mirth channel configuration for the exact paths.

Step 2: Create a vendor profile

If you have sample messages from each interface, create a profile so Loft knows what “correct” looks like:

pidgeon config analyze --samples /var/mirth/outbound/er-adt/ --save mirth_er_adt
pidgeon config analyze --samples /var/mirth/outbound/lab-results/ --save mirth_lab

Step 3: Start monitoring via CLI

Watch a single interface:

pidgeon loft watch \
  --path /var/mirth/outbound/er-adt/ \
  --profile mirth_er_adt

Loft monitors the directory, validates each new .hl7 file as it arrives, and alerts on failures.

Step 4: Create interfaces via the Bridge API

For production setups, create interfaces through the Loft desktop app’s local Bridge sidecar so they persist and appear in the Sources panel. The Bridge runs on localhost:5100 while the Loft app is open. There is no hosted API; every call below is local to the machine running Loft:

curl -X POST http://localhost:5100/api/loft/interfaces \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Mirth ER ADT",
    "directoryPath": "/var/mirth/outbound/er-adt/",
    "profileName": "mirth_er_adt",
    "filePattern": "*.hl7"
  }'

Repeat for each interface (lab results, pharmacy), changing name, directoryPath, and profileName. The Interface Monitoring page has the full field reference.

Step 5: Configure alerting

Set up alerts in the Loft desktop app or via the Bridge API. Loft has six channels: local log, webhook, Slack, Microsoft Teams, email, and PagerDuty. Payloads to off-device channels are scrubbed of message content before they leave the machine. See Alerting for the full channel model and routing options.

Step 6: Monitor metrics

Check interface health through the local Bridge API:

# Get metrics for the last 24 hours
curl http://localhost:5100/api/loft/interfaces/{id}/metrics?sinceHours=24

Or view the dashboard in the Loft desktop app’s Dashboards panel.

Step 7: Trace patient journeys

Track a specific patient’s messages across interfaces:

curl "http://localhost:5100/api/loft/traces?patient_id=MRN12345&since=2026-02-01"

This returns every message processed for that patient across all monitored interfaces, with timestamps and validation results.

Live updates

Subscribe to live updates via SignalR for dashboard integration, against the local Bridge:

const connection = new HubConnectionBuilder()
  .withUrl("http://localhost:5100/hubs/loft", {
    accessTokenFactory: () => token
  })
  .build();

connection.on("AlertReceived", (alert) => {
  console.log("Alert:", alert.severity, alert.message);
});

await connection.start();
await connection.invoke("SubscribeToAll");

Next steps

Configure alerting for your notification channels
Explore analytics for trend analysis and reporting

Getting Started

Install

Desktop Apps

Post (Testing Tool)

Conform (Conformance)

Flock (Population Engine)

Loft (Observability)

Migrate (Bulk Data Migration)

Guides & Tutorials

Support

Monitor Mirth Connect with Loft

Prerequisites

Step 1: Identify Mirth output directories

Step 2: Create a vendor profile

Step 3: Start monitoring via CLI

Step 4: Create interfaces via the Bridge API

Step 5: Configure alerting

Step 6: Monitor metrics

Step 7: Trace patient journeys

Live updates

Next steps

​Prerequisites

​Step 1: Identify Mirth output directories

​Step 2: Create a vendor profile

​Step 3: Start monitoring via CLI

​Step 4: Create interfaces via the Bridge API

​Step 5: Configure alerting

​Step 6: Monitor metrics

​Step 7: Trace patient journeys

​Live updates

​Next steps

Prerequisites

Step 1: Identify Mirth output directories

Step 2: Create a vendor profile

Step 3: Start monitoring via CLI

Step 4: Create interfaces via the Bridge API

Step 5: Configure alerting

Step 6: Monitor metrics

Step 7: Trace patient journeys

Live updates

Next steps