Bahmni Architecture
Bahmni is made up of four services which are integrated with each other. All integration happens using the atom (this RSS) feeds exposed by the individual services and consumed by the background threads in consuming processes. The first two slides below are for application and reporting architecture (This excludes all of OpenERP and canned OpenELIS reports)
Please see this training video on Bahmni Architecture also: Bahmni - Starting off the Bahmni Journey - Dec 2021 (Training)
Integration between application services
Each service publishes the key state changes via a RSS kind of feed (ATOM). The services also run background jobs which consume the feed published by other services. (e.g. When a patient is registered in OpenMRS then it captures the event for it. Both OpenERP and OpenELIS consume these events via the OpenMRS's change feed)
Integrations
Source | Destination | Source Resource | Destination Resource |
|---|---|---|---|
OpenMRS | OpenELIS | Patient | Patient |
OpenMRS | OpenERP | Patient | Customer |
OpenMRS | OpenELIS | Lab Order | Draft Accession |
OpenMRS | OpenERP | Orders | Quotation |
OpenELIS | OpenMRS | Accession, Sample & Results | Encounter (lab results) |
OpenMRS | OpenELIS | Concept | Sample types, Lab Test, Panel |
OpenMRS | OpenERP | Concept | Drug |
For Bahmni PACS design, please refer to this document: Bahmni PACS Roadmap