Starting the Odoo Connect and sync with EMR

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.

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)

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.

1. Update the .env file for the variables OPENMRS_ATOMFEED_USER, OPENMRS_ATOMFEED_USER and set the value as dummy. This is important so that the sync would not start from the first position
2. Bring up odoo-connect service docker compose up -d odoo-connect
3. Wait for the odoo connect service to come up and it to execute the liquibase migrations.
4. Check the logs until it completes liquibase migrations.
5. Now stop the service docker compose stop odoo-connect
6. Reset the atomfeed credentials as it was before.

1. Now exec into the odoodb container and connect to Odoo database.
2. Execute the insert queries that we acquired from Step 1;
3. Run select * from markers; to verify all the markers information is populated

Now the odoo-connect service can be started again so that the sync will resume from the position it was added.

Now you should have the sync resuming and any new order on EMR should sync to Odoo as it was before.