}

Sharing data in healthcare: people, processes and then tech

Effective data sharing in healthcare starts with clear agreements: who needs what information and when?
November 5, 2026
Employee Maarten Bongers
Geschreven door
Maarten

This is part 1 of a two-part series. This article focuses on processes and agreements in healthcare; part 2 explores how to put these into practice from a technical perspective.

Healthcare professionals don't have time to check yet another portal or dashboard to see whether a patient is doing well. Information needs to come to them: when they need it, in the systems that support their workflows. In practice, things often work differently. Each healthcare professional carefully manages information within their own organization. A measurement that is relevant to someone else in the care chain stays in the original patient's record.

‍

Take a patient who returns home after being admitted to hospital with heart failure. The community care nurse weighs the patient and records their weight in their own system. If the patient gains two kilos in three days, this is an early warning sign of fluid retention. But the GP doesn't see it. Neither does the cardiologist. For the patient, this could mean the difference between staying at home and being admitted to hospital again.

‍

Nobody is doing anything wrong here. The problem is that there are no clear agreements about who needs to know what, and when. Which data is relevant to whom? At what point? And what happens when a measurement falls outside the expected range? Only once these agreements are in place can data flow freely and seamlessly, allowing technology to support healthcare professionals in their work rather than the other way around.

‍

Five layers that need to work together

Nictiz describes what is needed for effective data exchange in its five-layer interoperability model. It shows that technology is only part of the story. Let's apply the model to our patient:

  1. Organizational policy: The hospital, community care team and GP agree to share this data and decide who takes the lead after the patient is discharged.
  2. Care process: They define which measurements are relevant to whom, what thresholds trigger an alert, and who needs to take action when that happens.
  3. Information: A patient's weight must mean the same thing across all systems. This is where healthcare information building blocks come in: national agreements on how data should be recorded.
  4. Applications: The electronic patient record (EPR) remains the leading system. Where it doesn't support a process in the way healthcare professionals need, a flexible application can fill the gap.
  5. IT infrastructure: Systems are securely connected through national and regional infrastructure. They speak the same language: healthcare data is stored in openEHR and exchanged via FHIR, allowing every system to read the same information without requiring a separate translation for every integration.

‍

It's tempting to start with layers 4 and 5. But the real value lies in layers 1 and 2, where the agreements are made that determine whether data can flow freely.

No items found.
Martijn van Kuijk
Can we help you?
Contact Martijn!

Layers 1 and 2 in practice: managing by exception

What do these agreements look like in practice? For our patient, the parties involved could agree to work based on exceptions:

  • At discharge, the relevant thresholds are defined.
  • The community care team takes the measurements and records them just once.
  • Only when a threshold is exceeded is a targeted alert sent to the agreed healthcare professional, such as the GP or heart failure nurse.
  • That professional takes action according to the agreed protocol.

‍

Nobody has to go looking for information, and the patient can rest assured that an abnormal measurement won't go unnoticed.

‍

Start with the people around the table, not the system

For the patient, one thing matters: that this morning's weight reaches the right healthcare professional today. Bring the parties in the care chain together and answer three questions: which data is relevant to whom, when is it needed, and what happens when something falls outside the expected range?

‍

Once these questions have been answered, it's clear what the technology needs to do. How this works under the hood, using openEHR, FHIR and a flexible extension to the patient record, is covered in part 2: Under the hood.

‍

Squad Apps helps healthcare organizations turn these agreements into applications that fit the way their professionals work. Interested in how we might be able to help your organization? Contact us! 

‍

From Low-Code to Agentic Enterprise
Close icon
Mendix AI Agentic Enterprise Platform
squad logo mark
Agentic Enterprise Platform