Skip to main content

HL7 integration monitor

What it does​

The HL7 integration monitor shows a PHI-free message log for this facility's HL7 interfaces and a connectivity score over the last 24 hours. Message bodies are never stored or displayed — only direction, message type, status, control id, and timestamps an operator needs when calling the sending system about a stuck feed.

Where to find it​

Open Integrations → HL7 monitor at /hl7/integration.

Common tasks​

Check interface health​

  1. Open Integrations → HL7 monitor.
  2. Read the Connectivity panel: score, total messages, processed count, and pending / failed / rejected breakdown.
  3. If Oldest unresolved is rising, a feed may have stopped — investigate the oldest pending or failed control ids in the log.

Find a specific message​

  1. Filter by Direction (Inbound / Outbound) and Status (Pending, Processed, Failed, Rejected).
  2. Locate the row by Control ID (MSH-10) — that is how the external system refers to the message.
  3. Use Occurred to correlate with clinical events, not processing time.

Distinguish failed vs rejected​

  • Failed — transport or availability problem; retrying unchanged may succeed.
  • Rejected — the message was understood and refused (for example an unmapped code); retrying unchanged will fail again until configuration is fixed.

Tips & limitations​

  • A null score with zero total means nothing moved in the window — not the same as 100% success.
  • Pending counts include messages on unconfigured channels — that is unfinished deployment, not a clinical failure.
  • You need hl7.message.read to view this screen.