Supplier integration into the machtfit platform
Initial
situation
Our client, machtfit, offers a platform that provides employee health benefits and that connects providers with companies who offer these benefits to their employees.
As an extension of the existing services, machtfit started a collaboration with a third-party health platform. This platform is exclusively available to users through their employer. Unlike other similar offers, direct access is not possible. machtfit wanted to act as an intermediary between the third-party supplier and employers, simplifying the negotiation process and expanding the range of health benefits available to companies.
DURATION
June – August 2024
TEAM
2 Developers
1 Team & Product Coach
INDUSTRY
Health
SCOPE
- Discovery phase with workshop to understand business goal and technical implications
- Development of adapter connection between third-party supplier and machtfit
Our
approach
Hands-on workshop: Aligning goals and dividing tasks.
In an initial workshop, we worked with the client to define the technical objective of integrating the third-party platform. We also analyzed the current technical status and assessed how this integration could be achieved within the existing system.
Based on the workshop results, we clearly divided responsibilities between the client's internal team and our own. Our team took ownership of the technical integration and the provision of relevant information such as user details, subscription processes and similar data flows. In parallel, the machtfit team focused on enhancing its core processes, such as embedding the new subscriptions into their product offering, designing user interactions and managing invoicing.
Solution &
results
Smooth integration without disrupting core system.
We developed a technical adapter, that acts as an anti-corruption layer between the third-party platform and machtfit, keeping the machtfit core application free from external details. Between the adapter and the machtfit core application we implemented an API and workflows that use machtfit-specific domain language.
This ensures that the machtfit core application receives all relevant events and data and can trigger events on the third-party platform without being influenced a by its specific implementation details.
Technologies used
Django
Django
Python
Python
Celery
Celery
REST
REST
sftp
sftp
