The integration layer for health-tech teams
CareConnect is the layer through which software in the ecosystem exchanges data, without every vendor rebuilding an integration. Today it is a design, not a product — this page describes the direction.
One integration instead of ten
The problem is familiar: every new partnership starts with an integration project. Three things that ought to change.
Shared interfaces
Tooling for engineers
Consent and provenance
What we are working towards
What follows is design direction, not a delivery promise. We write it down so the people talking to us know what is coming.
Standards first
Building on what exists — FHIR, HL7 and the European agreements — rather than adding another dialect.
Self-service
An engineer should be able to start without going through sales. That is the bar.
Moving with EHDS
The European data space sets the rules. CareConnect follows them rather than standing beside them.
Open about what works
We explain what we build and what we leave alone, including when the answer is 'not yet'.
What CareConnect is not today
This page describes a plan. That is not the same as a product, and the difference belongs here.
- Not built yetThere is nothing to connect to today. We make no commitment on a delivery date and no rights can be derived from this page.
- Aimed at vendors, not at care providersCareConnect targets software vendors and their engineers. A direct connection for care organisations is a later phase.
- Not an announcementWe publish the direction so conversations start honestly. The moment something actually runs, it will say so here — with a date.
Why we write this down already
Because a conversation about connecting only works when both sides know what exists and what still has to be built. An honest state beats a good-looking promise.
- Design phase
- FHIR and HL7
- For software vendors
Do you build integrations yourself?
Then your experience is exactly what this design needs. We would like to hear where you actually get stuck.