tsinkala / jempi

The Jembi MPI, also known as JeMPI, is a standards-based client registry (CR) or master patient index (MPI). JeMPI facilitates the exchange of patient information between different systems and holds patient identifiers that may include patient demographic information

JeMPI

The Jembi MPI, also known as JeMPI, is a standards-based client registry (CR) or master patient index (MPI). JeMPI facilitates the exchange of patient information between different systems and holds patient identifiers that may include patient demographic information. This is a necessary tool for public health to help manage patients, monitor outcomes, and conduct case-based surveillance. JeMPI’s primary goal is to act as a tool in order to solve the issue of multiple or duplicated patient records that are submitted from multiple point of service systems such as electronic medical records, lab systems, radiology systems and other health information systems. This is achieved by matching the various patient records from different systems under a Master Patient record with a unique ID. This allows for downstream applications, such as surveillance, to accurately display data and information on patient records without the worry that the data contains multiple records for the same patient.

Requirements

• linux (bash >= 4.x)
  • docker (non-root)
    • https://docs.docker.com/engine/install/ubuntu/
    • https://docs.docker.com/engine/install/linux-postinstall/
  • sdk manager (https://sdkman.io/)
  • maven
    • sdk install maven 3.8.6
  • sbt
    • sdk install sbt 1.8.0
  • java
    • sdk install java 17.0.8.1-tem
  • python 3.7
    • wxpython
    • requests

Installation

• Directory structure
  • <base>
    • JeMPI - [email protected]:jembi/JeMPI.git
• Requirements
  • ping `hostname` must ping a LAN IP address (not 127.x.x.x)
• Run
  1. <base>/JeMPI/docker/conf/env
     1. if you have less than 32Gb of ram, run ./create-env-linux-low-1-.sh. If you have 32Gb of ram or more, run ./create-env-linux-high-1-.sh
  2. <base>/JeMPI/docker/helper/scripts
     1. bash ./x-swarm-a-set-insecure-registries.sh
        • this clobbers /etc/docker/daemon.json
  3. <base>/JeMPI/docker
     1. ./a-images-1-pull-from-hub.sh
     2. ./b-swarm-1-init-node1.sh
     3. ./c-registry-1-create.sh
     4. ./c-registry-2-push-hub-images.sh
     5. ./z-stack-3-build-all-reboot.sh

Development

It's possible to run the whole stack local without having to use a local registry using the command :

./launch-local.sh

In order to remove the stack, you could use the following command :

docker stack remove jempi

Support for Mac OS

For MacOS users, the envsubst command will fail, so you'll need to add it :

brew install gettext
brew link --force gettext 

Other bash commands may fail (such as "declare -A"). So you may want to update bash >=v4:

brew install bash
bash --version

Then to run the stack locally, you will need to switch to bash first :

bash ./launch-local.sh

Note that currently, there is no Dgraph Ratel docker image compiled for M1 CPU, so most certainly you would run into a "Unsupported platform" error. For this you could either decide not to run the Ratel service by setting export SCALE_RATEL=0 in docker/conf/env/create-env-linux-1.sh and use https://play.dgraph.io/ instead.