pam-iti31 component
The pam-iti31 component provides interfaces for actors of the Patient Encounter Management IHE transaction (ITI-31), which is described in the IHE IT Infrastructure Technical Framework, Volume 2b , Section 3.31..
Actors
The transaction defines the following actors:
Producer side corresponds to the Patient Encounter Source actor. Consumer side corresponds to the Patient Encounter 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-mllp</artifactId>
<version>${ipf-version}</version>
</dependency>
Endpoint URI Format
The endpoint URI format of the pam-iti31
component is identical for producers and consumers:
pam-iti31://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.
Transaction Options
This transaction defines the following options; at least one of them must be chosen to be supported:
BASIC
(default)INPATIENT_OUTPATIENT_ENCOUNTER_MANAGEMENT
PENDING_EVENT_MANAGEMENT
ADVANCED_ENCOUNTER_MANAGEMENT
TEMPORARY_PATIENT_TRANSFERS_TRACKING
HISTORIC_MOVEMENT_MANAGEMENT
MAINTAIN_DEMOGRAPHICS
The options are represented as enumeration in the class Iti31Options.
Support for one or more options is configured using the optional options
parameter, followed by a comma-separated list of
options to be supported. If options
is provided, the default option (see above) is used.
The endpoint will reject event types that are outside the scope of the configured option.
Example
This is an example on how to use the component on the consumer side:
from("pam-iti31://0.0.0.0:8777?audit=true&secure=true&iheOptions=BASIC,INPATIENT_OUTPATIENT_ENCOUNTER_MANAGEMENT")
.process(myProcessor)
// process the incoming request and create a response
Basic Common Component Features
Basic MLLP Component Features
- Message types and exception handling
- Secure transport
- File-Based payload logging
- Mina options (until IPF 4.3.x)
- Netty options (as of IPF 4.4.x)