ch-ppq4 component

The ch-ppq4 component provides interfaces for actors of the Mobile Privacy Policy Bundle Feed IHE transaction (CH-PPQ-4), which is described in the Swiss national EPR FHIR implementation guide

Actors

The transaction defines the following actors:

PPQ-4 actors
PPQ-4 transaction and actors

Producer side corresponds to the Policy Source actor. Consumer side corresponds to the Policy Repository 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-fhir-r4-chppqm</artifactId>
        <version>${ipf-version}</version>
    </dependency>

Endpoint URI Format

Producer

The endpoint URI format of ch-ppq4 component producers is:

ch-ppq4://hostname:port/path/to/service[?parameters]

where hostname is either an IP address or a domain name, port is a number, and path/to/service represents additional path elements of the remote service.

Consumer

The endpoint URI format of ch-ppq4 component consumers is:

ch-ppq4://serviceName[?parameters]

The resulting URL of the exposed FHIR REST Service endpoint depends on the configuration of the deployment container. Consider a Tomcat container on host eHealth.server.org is configured in the following way:

port = 8888
contextPath = /IHE
servletPath = /fhir/*

Then the ch-ppq4 consumer will be available for external clients under the URL http://eHealth.server.org:8888/IHE/fhir.

URI parameters controlling the transaction features are described below.

Example

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

    from("ch-ppq4://service?audit=true&secure=true")
      .process(myProcessor)
      // process the incoming request and create a response

Translation between CH:PPQm and CH:PPQ messages

IPF comes with translators to translate PPQ-4 requests into PPQ-1 requests and vice versa for the responses.

Basic Common Component Features

FHIR Component Features