pixv3-iti46 component
The pixv3-iti46 component provides interfaces for actors of the PIX Update Notification v3 IHE transaction (ITI-46), which is described in the IHE IT Infrastructure Technical Framework, Volume 2b , Section 3.46..
Actors
The transaction defines the following actors:
Producer side corresponds to the Patient Identifier Cross-Reference Manager actor. Consumer side corresponds to the Patient Identifier Cross-Reference Consumer 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-hl7v3</artifactId>
<version>${ipf-version}</version>
</dependency>
Endpoint URI Format
Producer
The endpoint URI format of the pixv3-iti46 component producers is:
pixv3-iti46://hostname:port/path/to/service[?parameters]
where hostname is either an IP address or a domain name, port is a port number, and path/to/service represents additional path elements of the remote service. URI parameters are optional and control special features as described in the corresponding section below.
Consumer
The endpoint URI format of pixv3-iti46 component consumers is:
pixv3-iti46:serviceName[?parameters]
The resulting URL of the exposed IHE Web Service endpoint depends on both the configuration of the deployment container and the serviceName parameter provided in the Camel endpoint URI.
For example, when a Tomcat container on the host eHealth.server.org is configured in the following way:
port = 8888
contextPath = /IHE
servletPath = /ws/*
and serviceName equals to iti46, then the pixv3-iti46 consumer will be available for external clients under the URL
http://eHealth.server.org:8888/IHE/ws/iti46
Additional URI parameters are optional and control special features as described in the corresponding section below.
Example
This is an example on how to use the component on the consumer side:
from("pixv3-iti46:iti46?audit=true")
.process(myProcessor)
// process the incoming request and create a response