Gazelle documentation

PixM Connector

PIXm Connector installation

PIXm Connector is a connector for Patient Registry. It is dedicated to interface FHIR requests defined in PIXm standard to and the Patient Registry API for patient demographics and identifiers test data management.

Sources & binaries (PIXm)

The sources are accessible here: https://gitlab.inria.fr/gazelle/applications/test-execution/simulator/pixm-connector.

Bugs and issue tracking are accessible in the same project as the EHSSoftware : https://gazelle.ihe.net/jira/projects/EHSSOFT/issues. The name of the latest release, can be obtained in the “Releases” section.

To get official artifact (binaries), search for pixm-connector-service in IHE Nexus : https://nexus.ihe-catalyst.net/ and select the pixm-connector-service.war artifact for download.

Installation (PIXm)

Patient Manager dependency (PIXm)

Same as Patient Manager dependency for PATREG

PIXm also needs Patient Registry to be installed:

Matchbox and Http-Validator dependencies (PIXm)

Since 3.0.0 PIXm needs two deployed applications for validation:

  • HTTP-validator with the install documentation here.
  • Matchbox with the install documentation here

Operational Preferences

PIXm connector defines mandatory Operational Preferences that you will have to define in your Application server. To know how to do that, see General considerations for WildFly 18

/!\ Since 3.0.0 PIXm connector needs to be installed in Wildfly version 30.0.1.Final that supports JDK 17. But the tutorial remains the same as Wildfly 18.

Define a resource in your server with name java:/app/gazelle/pixm-connector/operational-preferences.

<subsystem xmlns="urn:jboss:domain:naming:2.0">
<bindings>
<object-factory name="java:/app/gazelle/pixm-connector/operational-preferences" module="net.ihe.gazelle.factories" class="net.ihe.gazelle.factories.PropertiesFactory">
<environment>
<property name="path" value="${DEPLOYMENT_PROPERTIES}"/>
</environment>
</object-factory>
</bindings>
<remote-naming/>
</subsystem>

Replace this property ${DEPLOYMENT_PROPERTIES} with the path to the deployment.properties file (like /opt/pixm-connector/deployment.properties)

This file shall contain the following properties :

Property Name  Description  Example value 
patientregistry.url URL of the Patient Registry Processing Service used to manage patients. https://example.com/patient-registry/PatientProcessingService/patient-processing-service?wsdl
xrefpatientregistry.url URL of the CrossReference Processing Service used to XReference. https://example.com/patient-registry/CrossReferenceService/xref-processing-service?wsdl

Deployment

Copy the war artifact pixm-connector-X.X.X.war (< 3.0.0) or pixm-connector-service-X.X.X.war (>= 3.0.0) in the deployment folder of the wildfly installation under the name pixm-connector.war.
This is important for the path on which connector’s web services will be exposed.

Before 3.0.0:

cp pixm-connector-X.X.X.war /usr/local/wildfly18/standalone/deployments/pixm-connector.war

Since 3.0.0:

cp pixm-connector-service-X.X.X.war /usr/local/wildfly30/standalone/deployments/pixm-connector.war

Start wildfly.

The API can be accessed at (depending on your configured host and port):