Skip to content

Bahmni/snomed-bahmni-docker

Repository files navigation

Bahmni Docker

Refer to this Wiki Page on detailed instructions for running Bahmni on Docker.

Note : This repository is used to run entire SNOMED Integration with Bahmni.

Local Deployment guide is here

SNOMED Integration

This deployment comes with two profiles i.e snomed-clinic and snomed-standard. More details can be found here

We are also bundling snowstorm lite server. More details can be found here

To start SNOMED CLINIC or STANDARD using docker compose (External SNOMED Server)

  1. Go to snomed-clinic or snomed-standard subfolder. For example: cd snomed-clinic.
  2. Execute script: ./run-bahmni.sh. This will give you options for start/stop/view-logs/pull/reset/etc.
  3. Ensure your .env file in the sub-folder has correct PROFILE configured, before executing the above commands. Make sure the JVM argument fhir.terminology-server.url in the environment variable CDSS_JAVA_SERVER_OPTS is set to the valid SNOMED FHIR Server URL.

To start SNOMED CLINIC or STANDARD along with SNOWSTORM LITE Server using docker compose

To use Snowstorm Lite server along with SNOMED CLINIC or STANDARD, please follow the below steps:

  1. Go to snomed-clinic-with-snowstorm-lite or snomed-standard-with-snowstorm-lite subfolder. For example: cd snomed-standard-with-snowstorm-lite.
  2. Update SNOWSTORM_RF2_FILE_PATH with RF2 file path from SNOMED and admin.password in the .env file.
  3. Replace <UPDATE_PASSWORD_HERE> with the same admin.password in the load-data.sh file.
  4. Please update the global properties in openmrs following the below Wiki page: https://bahmni.atlassian.net/wiki/spaces/BAH/pages/3183345706/Bahmni-SNOMED+Integration+Local+Deployment+Guide

Known Issues with SNOMED CLINIC

  1. For any concept supporting multiple languages, the form builder report displays all the languages against the corresponding concept. For more details, refer to this link
  2. 'Procedure Orders' concept is not automatically added as set member under 'All Orderables' after SNOMED CLINIC deployment. As a workaround 'Procedure Orders' needs to be manually added as set member under 'All Orderables' using OpenMRS concept dictionary. For more details refer to this link