The attempt here is to create a central data repository that ensures FHIR-based synhronization of patient data between two instances of OpenMRS. The demonstrated communication workflow involves the following components:
- Master Patient Index (MPI) / Client Registry
- Shared Health Record (SHR)
- Two instances of OpenMRS
The communication between these systems utilizes the FHIR clinical data standard for representing clinical data, and is orchestrated by the OpenHIM middleware.
git clone https://github.com/mherman22/openmrs-module-cdr.git
sudo docker-compose -f docker-compose.yml pull
sudo docker-compose -f docker-compose.yml up -d openhim-core openhim-console mongo-db
sudo docker-compose -f docker-compose.yml up -d openhim-config
sudo docker-compose -f docker-compose.yml up -d shr-fhir opencr-fhir opencr-es
sudo docker-compose -f docker-compose.yml up -d shr opencr
sudo docker-compose -f docker-compose.yml up -d openmrs-db-mysql openmrs-facilityA
sudo docker-compose -f docker-compose.yml up -d openmrs-referenceapplication-mysql openmrs-referenceapplication
username: root@openhim.org
password: Admin123
Below are a few useful Docker commands that will allow you to have better visibility into your OpenHIM/Docker setup.
Now that we have our OpenHIM successfully created and running, we might need to check up on our Docker processes running to find some additional metadata on our containers. Execute the below command to find all the running Docker processes.
docker ps
To access the OpenHIM core logs, execute the below command within your terminal to see and follow (-f) the output of the container logs.
docker logs -f openhim-core
docker stop <container_name or container_id>
To stop all the running OpenHIM Docker services, we need to execute the below command.
docker stop $(docker ps -a)
docker inspect <container_name>
docker network ls
docker exec -it <container_name> bash