HOW IT WORKS
How the connection works
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.
- InterfaceIn force
- HL7 FHIR R4; ISO 13606 semantics for synchronisation with local systems.
- DirectionIn force
- Reads the schedule, patient identity and the clinical resources in scope; writes back signed notes, bookings and completed pathway steps.
- Named systemsReadiness
- Stapro, CGM, Epic: readiness declared. FONS, ADAM and MediCom carry their own pages.
- Live todayIn force
- Stapro and CGM are live at named sites in Slovakia and Czechia. Epic is live at one international site.
- Time to connectIn force
- Between 3 and 6 weeks from the signed scope to the first write-back, measured across the connections made so far.
- PriceIn force
- Paid integrations are priced per system and the figure is stated on that system's page.
- SecurityIn progress
- Art. 32 GDPR controls; immutable, exportable audit trail; ISO/IEC 27001 recertification in progress.
- Who it is forIn force
- Practices and hospitals running an existing system.
- What it does not doIn force
- No migration, no second record, and no write outside the scope agreed with the vendor.
- ExitIn force
- 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
No. Your records stay in the system your team already knows. Hilbi reads through HL7 FHIR R4 and writes structured results back.
No. Hilbi is an overlay and never becomes the system of record. There is no moment where clinical data is in two places at once.
Then the scope of what can be read and written is smaller, and the per-system page states exactly what is possible rather than implying a full connection.
Stated per system on that system's page, once measured. A time is not published before it has been measured.