Bahmni uses an Atom Feed based framework created by ThoughtWorks ICT4H team for data synchronization between OpenMRS, OpenELIS and OpenERP (in fact also with Reference Data app). For more information on this read:
- http://github.com/ict4h/atomfeed
- https://github.com/ICT4H/simplefeed
- How to create a sample Atomfeed integration with Bahmni: Github Link
| Tip | ||
|---|---|---|
| ||
In version v0.86 of Bahmni an Atom Feed viewer has been released with Bahmni which can allow you to see Failed events in Bahmni. It can be accessed at url: http://<ip>/atomfeed-console. For instance here is the online demo url for atomfeed console: https://demo.mybahmni.org/atomfeed-console. The Github project for Atom Feed console is: https://github.com/ict4h/atomfeed-console |
The tables used in Atom Feed are:
| Table Name | Used in Mode | Description | ||||||
|---|---|---|---|---|---|---|---|---|
| event_records |
| This tables holds the list of events which are to be published by Atom Feed for others to consume. The category column is used to indicate the event types (like patient, encounter, etc). Note: For the same patient updates there might be multiple rows. So to see unique rows: "select distinct object from event_records where category = 'patient';" | ||||||
| markers |
| This table holds marker entries to indicate the records which have ALREADY been processed. | ||||||
| event_records_offset_marker |
| This table holds cached records for faster event process by the CONSUMER. | ||||||
| failed_events |
| This table holds the list of events which failed and could not be consumed. They are retried later by a different event handler. | ||||||
Note: The PUBLISH mode is when the system is publishing its events on an Atom Feed. The CONSUME mode is when the system is reading events from another system and writing/updating its own data based on consumed events. OpenMRS, OpenELIS, Odoo – all act as Publisher and Consumer depending on the scenario. For instance, when a Patient is created in Bahmni(OpenMRS), then Bahmni is PUBLISHER and ELIS/Odoo are CONSUMERS. When a Lab result is entered in ELIS, then ELIS is PUBLISHER and Bahmni/OpenMRS is CONSUMER of results. Therefore, these 4 tables will exist in each sub-system that acts as Atom Feed publisher & consumer. Example URL for OpenMRS Encounter Feed: view-source:https://demo.mybahmni.org/openmrs/ws/atomfeed/encounter/recent (select View-Source in browser)
Different Components like OpenMRS, OpenERP and OpenELIS are kept in Sync using the "Atom Feed Based Synchronization". The following is the depiction:
Lets take an example of Drug creation in bahmni. The following are the sequence of events:
- Administrators create Drugs using OpenMRS or using the "CSV Upload" feature on Bahmni's Admin module
- Once the drug is created, an event is published (more technical details in the github links above)
- The "OpenERP atom feed service" contains batch jobs that are scheduled to consume these atom feed events.
- The job then creates an event in OpenERP.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Explanation of Atom Feed Integration Design AtomFeed Overview Notes (OpenMRS meeting) Discussion about ERP and OpenELIS Integration |