xds-iti8 component

The xds-iti8 component provides interfaces for actors of the Patient Identity Feed IHE transaction (ITI-8), which is described in the IHE IT Infrastructure Technical Framework, Volume 2a , Section 3.8.

Actors

The transaction defines the following actors:

ITI-8 actors
ITI-8 transaction and actors

Producer side corresponds to the Patient Identity Source actor. Consumer side corresponds to both Document Registry actor.

Dependencies

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

    <dependency>
        <groupId>org.openehealth.ipf.platform-camel</groupId>
        <artifactId>ipf-platform-camel-ihe-mllp</artifactId>
        <version>${ipf-version}</version>
    </dependency>

Endpoint URI Format

The endpoint URI format of the xds-iti8 component is identical for producers and consumers:

xds-iti8://hostname:port[?parameters]

where hostname is either an IP address or a domain name, and port is a number. For the consumer side, the host name 0.0.0.0 allows the access from any remote host. These two obligatory URI parts represent the address of the MLLP(S) endpoint which is to be served by the given consumer or accessed by the given producer. URI parameters controlling the transaction features are described below.

HL7v2 Codec

Until IPF 4.3.x, all HL7v2-based transactions are realized using the camel-mina and camel-hl7 components and requires that an HL7v2 Mina Codec is available in the Camel registry.

As of IPF 4.4.x, all HL7v2-based transactions are realized using the camel-netty and camel-hl7 components and requires that an HL7v2 Netty Codec is available in the Camel registry.

Example

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

    from("xds-iti8://0.0.0.0:8777?audit=true&secure=true")
      .process(myProcessor)
      // process the incoming request and create a response

Basic Common Component Features

Basic MLLP Component Features

Advanced MLLP Component Features

Remarks for this component

Watch out! ITI-8 is the only HL7v2-based transaction that uses HL7 v2.3.1, while most of the others use HL7 v2.5