Skip to main content
Loft watches the messages flowing through your interfaces and catches what engine dashboards miss: a silently malformed med order, a misrouted lab result. Every catch lands in the Review Queue with a suggested fix for a human to accept or reject. Loft never changes a message on its own. Loft is a desktop app and requires a Pidgeon account sign-in. Watched sources are processed locally; message content never leaves your network, and alert payloads are redacted before they go out to a notification channel.

​
Before you start

  • Install Loft (or on macOS) and sign in.
  • Loft runs its engine in a local Bridge sidecar on localhost:5100. The desktop app can start it for you.
  • Have a directory your integration engine writes messages to (a Mirth pickup/drop folder works), or a folder of sample .hl7 files to try it on.

​
One loop: watch, catch, review, prove

1

Configure a watched source

Open Sources (under Monitor). Add the directory to watch, a file pattern (for example *.hl7), and the vendor profile to validate against.CLI equivalent:
2

Let messages flow

As files land in the watched directory, Loft picks them up, parses them, and validates each against the vendor profile. Dashboards shows the fleet overview; Alerts shows the live alert feed as failures are flagged.To try it without a live feed, drop a few sample messages into the watched directory. Generate broken ones with Post if you want a guaranteed catch.
3

Review the catch

Open Review Queue (under Operate). Each flagged message shows what failed, where, and a suggested fix. Accept or reject the suggestion: a human makes the call, and the decision is logged.
4

Export the evidence

Open Evidence (under Workspace) to export the audit trail of catches, reviews, and outcomes as a report you can hand to your team or attach to an incident.

​
When something fails

​
Next steps