Guidance Needed: Implementation of a Full HIMS in Sri Lanka

Implementing
, , ,
1

Hi everyone,

I am currently working on implementing a comprehensive Hospital Information Management System (HIMS) for a resource-constrained setting in Sri Lanka.

My requirement is to implement a whole hospital ecosystem, not just the EMR. I intend to use Docker for the implementation to ensure ease of deployment and maintenance.

The Goal

I aim to integrate the following components into a unified system:

  • EMR: OpenMRS 3.x (O3)

  • ERP (Billing, Inventory, HR, Admin): ERPNext

  • LIMS (Lab Operations): Senaite

  • PACS (Medical Imaging): Orthanc

  • IAM (Identity Management): Keycloak

  • Analytics: Superset

The Challenge

While exploring the best way to orchestrate this via Docker, I have come across a large number of images on Docker Hub and I am unsure of the best “Base” to start from.

I see two distinct sets of images in Docker Hub:

1. The Standard OpenMRS Images:

  • OpenMRS-core
  • OpenMRS-platform
  • OpenMRS-reference-application
  • OpenMRS-reference-application-3-frontend
  • OpenMRS-reference-application-3-backend
  • OpenMRS-reference-application-3-gateway
  • OpenMRS-reference-application-3-db
  • OpenMRS-reference-application-distro
  • OpenMRS-distro-platform

2. The “DistroHIS” Images: I found a suite of images that seem to target exactly what I need, but I am unsure if this is the community-recommended path:

  • distrohis-keycloak
  • distrohis-openmrs-frontend
  • distrohis-openmrs-backend
  • distrohis-mysql, distrohis-postgre
  • distrohis-proxy
  • distro-his-senaite, distrohis-eip-openmrs-senaite, distrohis-senaite-sso
  • distrohis-erpnext, distrohis-eip-erpnext-openmrs
  • distrohis-eip-odoo-openmrs, distrohis-odoo
  • distrohis-grafana-agent

I also noted that I didn’t see an orthanc container under either naming convention.

My Questions

  1. Where should I start?

  2. Reference Implementations: Does anyone have a docker-compose.yml example or a repo that successfully orchestrates O3, ERPNext, PACS and a LIMS together?

  3. Any advice on the correct architecture to adopt before I start building would be greatly appreciated!

2

Hi @navindu, you may have come across Ozone already. It’s a solid starting point, as it’s actively maintained and receives regular updates, unlike DistroHIS. Both projects are supported by the same team – @Mekom, who would be best placed to weigh in and offer guidance on the best path forward.

2 Likes
3

Hi @ruhanga ,

Thanks for the heads up! I wasn’t aware that Ozone effectively replaces DistroHIS. That sounds like exactly what I need. I’ll shift my focus to the Ozone repos.

4

@navindu that’s not quite accurate. DistroHIS doesn’t get replaced by Ozone. Rather, it builds on Ozone. DistroHIS is the community-maintained distribution, while Ozone is actively developed and maintained by the @Mekom team.

5

That makes sense. I plan to investigate the Ozone repos further

2 Likes