Bahmni facilitates the synchronization of patient data and generates quotations in Odoo for orders processed on the EMR. To enable this atomfeed synchronization, a service called odoo-connect has been incorporated into our Bahmni Docker Compose specification.
Before proceeding with the steps below, ensure you have completed the masterdata migration and required transactional data migration process as mentioned here and validated it.
Also go through Sales Module Configuration to understand the required metadata setup for proper atomfeed sync. This includes order types, shops, order type shop maps, syncable units maps.
Step 1: Backing up Markers information
As we have already migrated the product, customer and outstanding information, the atomfeed markers should be set to the position from where the migration has been initiated. Run the below query in OpenERP or Odoo 10 database to get a dump output of the markers table entries.
OpenERP 7:
pg_dump -U openerp --column-inserts --data-only --table=markers openerp
Odoo 10:
pg_dump -U odoo --column-inserts --data-only --table=markers odoo
Copy the insert statements from the output to a text file. Replace the host IP and port in the URLs as openmrs:8080. (Example: http://openmrs:8080/openmrs/ws/atomfeed/drug/108)
Step 2: Initialising atomfeed schema in Odoo database
Since the Odoo database is a fresh database, the markers table will not exist on the database. Follow the steps below to start the atomfeed service to initialise the required schema.
Update the .env file for the variables
OPENMRS_ATOMFEED_USER,OPENMRS_ATOMFEED_USERand set the value asdummy. This is important so that the sync would not start from the first positionBring up odoo-connect service
docker compose up -d odoo-connectWait for the odoo connect service to come up and it to execute the liquibase migrations.
Check the logs until it completes liquibase migrations.
Now stop the service
docker compose stop odoo-connectReset the atomfeed credentials as it was before.