mosaicgreifswald/gpas repository overview

Current Docker-Version of gPAS: 2026.1.0 (Jul 2026)
Current Docker-Version of TTP-FHIR-Gateway: 2026.1.0, Details from ReleaseNotes⁠

⁠About

The use of pseudonyms is a privacy-enhancing technique supporting privacy-by-design and ensuring non-attribution. Pseudonymisation allows storing directly person identifying data separately and securely from medical data and supports the data controller to meet the GDPR’s data security requirements (Art. 32 lit. 1 EU GDPR).

To facilitate the generation and administration of appropriate pseudonyms the Institute for Community Medicine of the University Medicine Greifswald (UMG) developed the web-service-based gPAS.

The use of pseudonymization domains, the specification of individual alphabets and generator algorithms allow for the free generation of different pseudonyms per data source, application context or study site.

⁠General

This gPAS image is completely identical to the image mosaicgreifswald/wildfly:40⁠,
except that it already contains the deployments and JBoss-CLIs from our gPAS⁠.

⁠API

⁠SOAP

All functionalities of the gPAS are provided for external use via SOAP-interfaces. The JavaDoc specs for the Services⁠ are available online (see package org.emau.icmvc.ganimed.ttp.psn).

Use SOAP-UI to create sample requests based on the WSDL files.

⁠Standard-Service-Interface

The WSDL URL is http://<YOUR IPADDRESS>:8080/gpas/gpasService?wsdl⁠

⁠Standard-Service-Interface with Notifications

The WSDL URL is http://<YOUR IPADDRESS>:8080/gpas/gpasServiceWithNotification?wsdl⁠

⁠Management-Management-Interface

The WSDL URL is http://<YOUR IPADDRESS>:8080/gpas/DomainService?wsdl⁠

⁠FHIR

More details from https://www.ths-greifswald.de/gpas/fhir⁠

⁠IT-Security Recommendations

Access to relevant application and database servers of the Trusted Third Party tools should only be possible for authorised personnel and via authorised end devices. We therefore recommend additionally implementing the following IT security measures:

• Operation of the relevant servers in separate network zones (separate from the research and supply network).
• Use of firewalls and IP filters
• Access restriction at URL level with Basic Authentication (e.g. with NGINX or Apache)
• use of Keycloak to restrict access to Web-Frontends and technical interfaces

⁠Relevant for this Image

⁠ENV-Variables and defaults

⁠Relevant Entrypoints

⁠Usage

"versions" shows all installed tools and components, with their versions.

docker run --rm mosaicgreifswald/gpas versions
  last updated               : 2026-07-20 16:46:59
  Architecture               : x86_64
  Distribution               : Debian GNU/Linux 13.6 (trixie)
  zulu-jre                   : 25.0.3 
  WildFly                    : 40.0.1.Final
  MySQL-Connector            : 9.7.0
  MariaDB-Connector          : 3.5.9
  PostgreSQL-Connector       : 42.7.13
  EclipseLink                : 4.0.9
  gPAS                       : 2026.1.0
  FHIR-Gateway               : 2026.1.0
  Notification-Client        : 2026.1.0
  Notification-Service       : 2026.1.0

⁠Change write permissions

If data is stored on the host-system (via volume), it is created by default with the internal mosaic-user (UID:GID = 1111:1111). You can change the write-user by using the Docker parameter --user/-u.

# change write-user (UID:GID) for writable volumes like logs/
> docker run --rm -d \
    -u 1006:1001 \
    -e WF_SYSTEM_LOG_TO=FILE \
    -v /path/to/your/logs:/entrypoint-wildfly-logs \
    mosaicgreifswald/gpas

> ls -l /path/to/your/logs
insgesamt 8
-rw-r--r--  1 1006 1001    0 13. Jun 10:25 gpas.log

⁠Database

You need a prepared MySQL database to start the gPAS successfully.

# with external db
> docker run --rm -it \
    -e TTP_DB_HOST=host_or_ip \
    -e TTP_DB_PORT=3306 \
    -e TTP_DB_USER=gpas \
    -e TTP_DB_PASS=top-secret \
    -p 8080:8080 \
    mosaicgreifswald/gpas

If you don't have an gPAS database, you can create one yourself. Everything you need to create your own database is already included in this image:

# explore all additional files
> docker run --rm -it mosaicgreifswald/gpas examples

# explore and copy interesting files to your local host
> docker run --rm -it -v "/your/local/path/:/tmp/" -u "$(id -u):$(id -g)" mosaicgreifswald/gpas examples --target-dir /tmp

# or copy directly all files to your host
> docker run --rm -v "/your/local/path/:/tmp/" -u "$(id -u):$(id -g)" mosaicgreifswald/gpas examples --target-dir /tmp --copy-all

You will receive the following directory-tree and can start playing immediately:

|____layer-readme/
|  |____README-gpas.md
|____examples/
  |____compose-gpas/
    |____addins/
    |____demo/
    | |____demo_gpas.sql
    |____docs/
    | |____Docker-Update.md
    | |____gRAS-Einrichtung.md
    | |____TTP-Tools-Keycloak-Einrichtung.md
    | |____TTP-Tools-Keycloak-Realm.json
    |____envs/
    | |____mysql.env
    | |____ttp_commons.env
    | |____ttp_fhir.env
    | |____ttp_gpas.env
    | |____ttp_gras.env
    | |____ttp_noti.env
    |____logs/
    |____sqls/
    | |____create_database_gpas.sql
    | |____create_database_gras.sql
    | |____create_database_noti.sql
    | |____init_database_gras_for_gpas.sql
    |____update_sqls/
    | |____update_database_gpas.sql
    |____docker-compose.yml

You can then start up an empty system directly:

# go to compose-dir and start compose
> cd examples/compose-gpas
> docker compose up

⁠Usage with docker compose

over docker-compose with dependent on mysql-db (example)

# docker-compose.yml
services:
  mysql:
    image: mysql
    environment:
      MYSQL_ROOT_PASSWORD: top-secret
    volumes:
      - /path/to/your/init-sql-files:/docker-entrypoint-initdb.d
  wildfly:
    image: mosaicgreifswald/gpas
    ports:
      - 8080:8080
      - 9990:9990
    depends_on:
      - mysql
    environment:
      WF_ADMIN_PASS: top-secret
      WF_HEALTHCHECK_URLS: http://localhost:8080

⁠Update existing instance

1. Get all update-sqls from additional files:

# copy all update-scripts to your host
> docker run --rm -v "/your/local/path/:/tmp/" -u "$(id -u):$(id -g)" mosaicgreifswald/gpas examples \
    --source-dir /entrypoint-help-and-usage/examples/compose-gpas/update_sqls/ \
    --target-dir /tmp \
    --copy-all

1. Create a backup before you start the update.
2. Run all SQL scripts on your database that are relevant for your current version. Make sure you follow the correct order.
3. Now you can use the new image.

⁠Current Software-Versions on this Image

⁠Additional Information

The gPAS was developed by the University Medicine Greifswald and published in 2013 as part of the MOSAIC-Project⁠ (funded by the DFG HO 1937/2-1).

Selected functionalities of gPAS were developed as part of the following research projects:

• MIRACUM (funded by the German Federal Ministry of Education and Research 01ZZ1801M)

⁠Credits

Concept and implementation: L. Geidel
Web-Client: A. Blumentritt, M. Bialke, F.M. Moser
Docker: R. Schuldt
TTP-FHIR Gateway für gPAS: M. Bialke, P. Penndorf, L. Geidel, S. Lang, F.M. Moser

⁠License

License: AGPLv3, https://www.gnu.org/licenses/agpl-3.0.en.html⁠
Copyright: 2013 - 2026 University Medicine Greifswald
Contact: https://www.ths-greifswald.de/kontakt/⁠

⁠Publications

• https://dx.doi.org/10.3414/ME14-01-0133⁠
• https://dx.doi.org/10.1186/s12967-015-0545-6⁠
• https://dx.doi.org/10.3205/24gmds102⁠
• https://dx.doi.org/10.3205/24gmds101⁠

⁠Supported languages

German, English