Two systems that need to agree with each other
An integration is easy to demonstrate and hard to run. Moving a record from one system to another takes an afternoon. Keeping two systems in agreement, permanently, while both of them change underneath you, is the actual job. That means deciding which side wins a conflict, handling updates that arrive out of order, and coping with partial records rather than rejecting them.
The hard part is the disagreement
Two systems rarely model the same thing the same way. A person in a scheduling platform and a contact in a CRM are not the same object, even when they describe the same human being.
I built a two-way integration between a healthcare scheduling platform and a CRM across the Patient, Practitioner and RelatedPerson FHIR resources. FHIR is a clinical standard and a CRM is a commercial one, so most of the work was the mapping layer between two data models that were never designed to meet.
Old APIs are still APIs
A lot of the systems businesses run on have interfaces that are old, badly documented, or technically undocumented. That is normal, and it is workable. It is slower, because it involves finding out what the system does rather than reading what it claims to do.
What this looks like as a build
- Two-way syncs where a change on either side lands on the other
- Mapping layers between data models that do not naturally line up
- Webhook handling with validation, retries and replay
- Integrations against old, undocumented or awkward APIs
This is not a separate service with its own price
There is one thing to buy here: a build seat, from $7,500 per month. This page describes one of the things people point a seat at. You set the order, and the seat works one item at a time until each is done.
Questions about this kind of work
- What if the system we use has no public API?
- It often still has a usable interface, just not a documented one. That is worth investigating before assuming it is impossible. If it genuinely cannot be reached, I will tell you that rather than build something fragile against it.
- Can you work with HL7 FHIR?
- Yes. I have built a two-way integration across the Patient, Practitioner and RelatedPerson resources between a FHIR scheduling platform and a CRM.
Start with a call, not a contract
Thirty minutes. You describe what broke, what it is costing you, and what you have already tried. I tell you whether a seat is the right answer, and I will tell you when it is not.
Or reach me directly: +1 385-208-1781 scott@aetenum.com
If you are comparing quotes on price, I am not your cheapest option and I will not pretend otherwise.