A two-way sync between a healthcare scheduling platform and a CRM
A healthcare operator needed its scheduling platform and its CRM to agree with each other. I built a two-way integration across three FHIR resource types, so a change in either system lands in the other.
- 3
- FHIR resources synced
- Two-way
- Direction
- HL7 FHIR
- Standard
The situation
Scheduling lived in a healthcare platform that exposes an HL7 FHIR API. Sales and client communication lived in a CRM. Neither knew what the other was doing.
What was actually broken
- Patient and provider records existed in two systems with no agreement between them.
- Anything entered on one side had to be re-entered on the other, which meant it often was not.
- FHIR is a clinical standard, not a CRM one, so the two data models did not line up on their own.
What I built
- A two-way integration across the Patient, Practitioner, and RelatedPerson FHIR resources.
- A mapping layer that translates between the clinical data model and the CRM data model in both directions.
- Handling for the cases that break naive integrations, including partial records and updates that arrive out of order.
What changed
- A change made in either system appears in the other without anyone retyping it.
- Patient, practitioner, and related-person records stay consistent across both platforms.
Stack
HL7 FHIR Python CRM API Webhooks
This client is not named. If you want a reference before signing, ask on the call and I will arrange one where the client has agreed to it.