Data Panda brings your HiX data together with the rest of the hospital stack. From one place, we turn it into dashboards, automations and AI workflows that clinicians, planners and finance use.
HiX is built by ChipSoft, a Dutch software company founded in 1986 in Amsterdam. The product is a fully integrated electronic patient record where one shared dossier covers every department of the hospital, from the medical record and nursing chart through hospital pharmacy, central sterilisation, kitchen and the patient portal. Around fifty Dutch hospitals run on HiX, and the Flemish footprint now includes AZ Delta, AZ Klina, Ziekenhuis Oost-Limburg, Ziekenhuis Geel and the combined ZNA and GZA networks in Antwerp, the largest EPR rollout in Belgium to date.
Pulling HiX into a warehouse matters because the patient record is the only place where clinical events, planning and resource use line up under the same patient identifier. HiX exposes that data through its own warehouse and through Zorgplatform, the certified DVZA that translates requests to HL7 FHIR. We use those exits to land HiX next to the ERP, HR system, finance and patient portal traffic, so capacity, throughput, no-show patterns and cost per care path stop living in three different exports.
Clinical activity, planning and finance combined per care path and per cost centre.
Keep HiX in sync with the systems that surround it.
Use HiX history to forecast demand, flag risk and pre-fill admin.
Small tools on HiX data for people who should not need a HiX licence.
A list of concrete reports, automations and AI features we have built on HiX data. Pick the one that matches your situation.
What is the cost per admission per specialism?
Materials, pharmacy use, OR time and ward time costed and rolled up against the DRG. Shows where the realised cost drifts above the financing per care path, before the year-end reconciliation does.
Where is the planning slipping?
Planned versus realised OR and consultation hours per specialism and per surgeon, against historical baseline. Brings the late-running theatre and the over-booked clinic forward to the planner before they show up in patient complaints.
Which appointments are at risk of no-show today?
Per-appointment no-show probability based on patient history, slot, channel and lead time, scored the night before. Drives the call list and the reminder flow rather than relying on the same generic SMS for everyone.
Cost per admission, cost per DRG and pharmacy spend in one view next to the financing side. The year-end reconciliation stops being the moment the gap between care delivered and care paid for becomes visible.
Patient portal adoption, response times and channel mix per clinic, plus referral inflow and conversion. Patient-experience and access decisions move from loudest-complaint to where the data shows the drop.
OR and consultation load, length of stay and no-show patterns on one board. Capacity decisions move from gut feel to the trend the warehouse already shows.
HiX exposes patient, encounter, observation and medication data through Zorgplatform as HL7 FHIR. Data Panda lands those resources in the warehouse on the same patient identifier as the rest of the hospital systems, so clinical events line up with planning, finance and HR without a custom integration project per use case.
HiX clinical and operational tables land in Snowflake next to ERP, HR and patient portal data, so cost per admission, length of stay and no-show analyses run on one model rather than three exports. Role-based access keeps identifiable patient data scoped to the people who need it.
Care activity from HiX joins AFAS finance and payroll data on cost centre and period, so realised cost per specialism includes labour, materials and overhead. The hospital P&L closes against actual care delivered, not against an allocation key bolted on at the end of the quarter.
Power BI reports for medical management, planners and finance read from the warehouse layer rather than from HiX exports built per request. The same definition of admission, encounter and care path applies across reports, so the OR load in the executive deck matches the one on the planner's screen.
Service requests linked to HiX events, like ward moves, equipment cleaning and incident reports, line up with TOPdesk tickets in the warehouse. Operations sees lead time from clinical event to ticket close per location and per category, instead of judging facility performance only on TOPdesk SLAs in isolation.
These are the 14 tables we currently pull from HiX into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your HiX data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Two paths. The integrated HiX data warehouse exposes structured tables for clinical, planning and operational data, which we land in the central warehouse on a schedule. For exchange-style data and outside-the-walls flows, Zorgplatform translates HiX content to HL7 FHIR; we read those FHIR resources and land them on the same patient identifier. Which path applies depends on the use case and on what the hospital already has licensed.
Patient data is treated as the most sensitive data class on the platform. Identifiable columns are ring-fenced to clinical and authorised analytics roles, while operational and finance views work with aggregated or pseudonymised data. Retention, role-based access, audit logging and the relevant DPA work happen before the first patient record lands in the warehouse, in step with the hospital's data protection officer.
We review your HiX setup and the systems around it. Together we pick the first thing worth building.