GSoC 2025: Intergrate OpenELIS with Odoo(OpenER)

Community GSOC
1

Hello everyone here, I am writing to express interest in the project titled “Integrate OpenELIS with Odoo (OpenERP)” project as part of Google Summer of Code (GSoC). This project aims to enhance OpenELIS Global2 by integrating it with Odoo to support billing functionalities within the OpenELIS order workflow.

Seeking Clarifications

To better define the scope, I would appreciate guidance on:

  1. Is there a preferred technology stack for the integration layer (e.g., Apache Camel, custom REST APIs, message queues like Kafka)?
  2. Should the billing process be triggered at the order placement, test completion, or both?
  3. Will OpenELIS and Odoo communicate using OAuth2, API keys, or another authentication method?

I would love to hear insights from the community, maintainers, and mentors to refine the scope further. Looking forward to your thoughts and feedback!

Cc: @reagan @mherman22 @Moses_Mutesasira

Take Care,
Vickabire,
GSoC Aspirant | OpenELIS Contributor

4 Likes
2

I have spent the last couple of weeks looking into the approach to take for this project. An enterprise integration pattern came into mind, using debezium to track events from the source.

  • Write-Ahead Log (WAL), which records changes to the database as they occur is the source.

  • From each event an appropriate Camel route should decide whether it is relevant or not.

For instance if the business requirement only involves the integration of orders, then you don’t need to take action on persons, or patients.It hydrates the Debezium event into a model.The default model should be FHIR.

The hydrated event, so the model, is routed to wherever it needs to go with further Camel routes.

2 Likes