The mllp component allows for custom MLLP-based interfaces to benefit from all features that are available to MLLP-based IHE transactions, e.g. message fragmentation, ATNA auditing, message dispatching etc. This is particularly valuable if you already use IHE transaction components but you need additional interfaces for which there is no defined IHE profile.


Both consumer and producer sides are supported. There is no mapping to a particular actor.


In a Maven-based environment, the following dependency must be registered in pom.xml:


Endpoint URI Format

The endpoint URI format of the mllp component is identical for producers and consumers:


where hostname is either an IP address or a domain name, and port is a number. For the consumer side, the host name allows the access from any remote host. These two obligatory URI parts represent the address of the MLLP endpoint which is to be served by the given consumer or accessed by the given producer.

Additionally, the URI parameter hl7TransactionConfig references a bean of type org.openehealth.ipf.commons.ihe.hl7v2.Hl7v2TransactionConfiguration that defines the contract of the transaction.

The clientAuditStrategy and serverAuditStrategy within that hl7TransactionConfig transaction contract are mandatory unless ATNA auditing is disabled in the endpoints. The audit strategies must reference an instance of type org.openehealth.ipf.commons.ihe.core.atna.AuditStrategy.

HL7v2 Codec

All HL7v2-based transactions are realized using the camel-mina2 and camel-hl7 components and requires that an HL7v2 Codec is available in the Camel registry.


This is an example on how to use the component on the consumer side:

      // process the incoming request and create a response

Explicitly configured mllp component instances

As the hl7TransactionConfig is a property of the component and not of the endpoint, you cannot use two mllp endpoints with different hl7TransactionConfig parameters. Instead, you need to create separate component beans and refer to them by their scheme ID.

In the following example, we define two component instances as mllp1 and mllp2, configured with distinct hl7TransactionConfig :

    <bean id="mllp1" class="org.openehealth.ipf.platform.camel.ihe.mllp.custom.CustomMllpComponent">
        <property name="transactionConfiguration" ref="hl7TransactionConfig1"/>

    <bean id="mllp2" class="org.openehealth.ipf.platform.camel.ihe.mllp.custom.CustomMllpComponent">
        <property name="transactionConfiguration" ref="hl7TransactionConfig2"/>

In the route definition, they can be used like this:

      // process the incoming request and create a response

      // process the incoming request and create a response

Basic Common Component Features

Back to top

Version: 3.5-SNAPSHOT. Last Published: 2018-04-20.

Reflow Maven skin by Andrius Velykis.