Join our Newsletter — 33% off our NHI Course
Architecture & Implementation

MLLP

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Architecture & Implementation

MLLP is a transport wrapper for sending HL7 v2 messages over TCP/IP. It frames each message with start and end bytes, plus an optional carriage return, so receiving systems can detect message boundaries and acknowledge delivery reliably.

How MLLP Works

MLLP is a lightweight framing layer that sits on top of TCP/IP for HL7 v2 traffic. It does not change the clinical message itself, but it gives the sender and receiver a shared way to mark where a message starts and ends, which matters because TCP is a byte stream rather than a message-oriented protocol.

In practice, that framing is what lets downstream healthcare systems parse each HL7 payload reliably, separate one transaction from the next, and know when an application can safely acknowledge receipt.

Why MLLP Exists in HL7 Integration

HL7 v2 messaging was designed for interoperability between clinical, lab, billing, and ancillary systems, but it depends on a transport convention so messages can move cleanly across heterogeneous systems. MLLP solves the boundary problem by adding a simple wrapper around the HL7 content, which is why it became so common in interface engines and point-to-point healthcare integrations.

That simplicity is also the reason it persists. Organisations often prefer a transport wrapper that is easy to implement, easy to debug, and broadly supported by legacy systems. The trade-off is that the wrapper provides framing and acknowledgement semantics, not security by itself.

Message Framing, Acknowledgement, and Reliability

MLLP typically uses a start block marker and an end block marker, with an optional carriage return, to delimit the message body. Those markers help the receiver identify complete messages even when the underlying TCP stream arrives in chunks or multiple messages are delivered back-to-back.

The acknowledgement model is equally important. In many HL7 workflows, the receiving system sends an application-level response to confirm that the message was processed or at least received in a usable state. This helps integration teams distinguish transport success from application success, which is crucial when clinical workflows depend on timely delivery and accurate handoff.

Security Implications for MLLP Transport

MLLP is a transport convention, not a protection mechanism. The protocol does not provide confidentiality, integrity, authentication, or replay protection on its own, so organisations usually rely on surrounding controls such as network segmentation, encrypted transport, endpoint hardening, and interface monitoring. The NIST SP 800-53 Rev 5 Security and Privacy Controls is a useful reference for the control families that typically matter around this kind of integration traffic, including access control, authentication, audit logging, and configuration management.

Because MLLP carries regulated health data in many environments, exposure is often less about the framing itself and more about where the connection is permitted, who can reach it, and whether message content is protected in transit and at rest. A misrouted interface, a flat network, or a weak trust boundary can turn a simple integration path into a sensitive data exposure channel.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 provides the primary governance reference for this term.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-4 — Information Flow EnforcementMLLP message paths depend on enforced network and interface boundaries.
IA-2 — Identification and Authentication (Organizational Users)Operators and interface administrators need verified access to MLLP-connected systems.
AU-2 — Event LoggingMLLP integrations need traceable delivery, acknowledgement, and failure records.
Recommendation — Enforce trusted flow paths for HL7 interfaces and block unauthorized message routing. Require authenticated administrative access to systems that host or broker MLLP connections. Log message delivery, acknowledgement, and parsing events for HL7 interface monitoring.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org