Integrations
It connects to what you already run
FHIR R4 is the source of truth. Hilbi reads the schedule and the record, writes structured results back, and never keeps a second copy. Six systems connected or in build.
- FHIR R4 resources are the record
- No migration
- Reads and writes back
6 systems
connected or in build
3 to 6 weeks
from signed scope to first write-back
How the connection works
Two layers. Resources are the truth. Everything rendered comes from them.
FHIR R4 is the truth
Resources are the record. What Hilbi shows is a rendering of them, never a second copy kept in step by hand.
What Hilbi reads
The schedule, the patient identity and the resources a booking or a pathway needs. Scoped per system, stated on its page.
What Hilbi writes back
The signed note, the booking, the completed step. Written as resources into the system of record.
What a connection takes
A scope agreed with the vendor, credentials, and a test against your own data before a single patient sees it.
What to assess before you connect
In the order an evaluation asks it.
- Interface
- HL7 FHIR R4; ISO 13606 semantics for synchronisation with local systems.
- Direction
- Reads the schedule, patient identity and the clinical resources in scope; writes back signed notes, bookings and completed pathway steps.
- Named systems
- Stapro, CGM, Epic: readiness declared. FONS, ADAM and MediCom carry their own pages.
- Live today
- Stapro and CGM are live at named sites in Slovakia and Czechia. Epic is live at one international site.
- Time to connect
- Between 3 and 6 weeks from the signed scope to the first write-back, measured across the connections made so far.
- Price
- Paid integrations are priced per system and the figure is stated on that system's page.
- Security
- Art. 32 GDPR controls; immutable, exportable audit trail; ISO/IEC 27001 recertification in progress.
- Who it is for
- Practices and hospitals running an existing system.
- What it does not do
- No migration, no second record, and no write outside the scope agreed with the vendor.
- Exit
- The connection is switched off; the record is untouched; the audit log is yours to export.
Connected today
A system is called connected only where a named site is live. Everything else is stated as readiness.
| System | Markets | What the connection carries | Status |
|---|---|---|---|
| Stapro | Czechia, Slovakia | Reads the schedule, patient identity and encounters. Writes the signed report and the completed pathway step. | |
| CGM | Czechia, Slovakia, DACH | Reads the schedule, patient identity and results. Writes the signed report and coded diagnoses. | |
| Epic | United States, international | Reads patient identity, encounters and documents. Writes the structured note. | |
| FONS | Czechia | Reads the schedule and patient identity for booking. | |
| ADAM | Slovakia | Reads the schedule and patient identity for booking. | |
| MediCom | Slovakia | Reads the schedule, patient identity and encounters. |
Questions about connecting a system
Is anything migrated?
Does the record move?
What if our system has no interface?
How long does a connection take?
Monthly briefing
The signal, once a month.
What changed in European health data, what we shipped, and what it means for a provider. Nothing else.