Client data, so NEN 7510 The EHR remains the source Map the interface first

Custom Puur by Ecare API integration development

An integration with an electronic client record is not an ordinary integration. It involves health data, so the question is not only what is technically possible but also what is permitted, who may see it and how you demonstrate that later. That shapes the design from day one, not at delivery.

What makes an EHR integration different

Puur by Ecare is an electronic client record used in healthcare for client data, care plans, scheduling and reporting, among other things. An integration is usually requested because something sits alongside it: your own scheduling tool, a client portal, a billing process or a report the EHR does not provide. The EHR then remains the source; the aim is not to create a second record.

That last point is the most important design rule. Data that you copy and store separately drifts out of line with the EHR, and for a record on which care providers base decisions that is not acceptable. We therefore retrieve as little as possible and store as little as possible, and where data is still needed outside the EHR, we record where it came from and how old it is.

What can actually be exchanged depends on the interface the supplier makes available and on your own contract and modules. We map that out before we commit to anything. We are not a partner of the supplier and we do not promise an integration we have not seen; however, we do know how such a project unfolds and where it usually gets stuck. What NEN 7510 requires of you is set out at nen.nl.

How we build this

The first question is which data is really needed outside the EHR, and that is almost always less than the initial assessment suggests.

1
Mapping the interface

Which exchange the supplier makes available, under what conditions and with what lead time for requesting it. This step more often takes weeks than days, and it determines whether the plan is feasible.

2
Reducing the data requirement

For each field, the question of why it is needed and whether you can do without it. This is not cost-cutting but data minimisation: every field you do not retrieve is one you do not have to secure, store and account for.

3
The integration with the smallest scope first

Every sprint ends with something you can check yourself, and we start with the narrowest useful exchange. You can always expand; you cannot roll back once data has spread.

4
Working alongside you in practice

We work alongside the teams who use it. That shows whether the integration does what is needed, and what still has to be done by hand around it.

What the integration actually does

What is possible depends on the interface. These are the six questions that come up in almost every project like this.

Synchronising client data

Basic data from the EHR to the application alongside it, in one direction and without creating a second record. Which fields, and how often, depends on the interface and on what you actually need.

Scheduling and care delivered

Exchanging appointments and care moments delivered, usually because a scheduling tool or route planner runs alongside. This is where most of the day-to-day value lies, and also the risk of two systems contradicting each other.

Client or family portal

A secured entry point where a client or informal carer can view or submit something. This is a separate component with its own access rules and its own choices about what is and is not visible; it is not a by-product of the integration.

Signals instead of record copies

For reporting and management, a count is often enough rather than a record. Where possible we work with aggregated signals, because that removes the risk without leaving the question unanswered.

Visible error handling

An integration that stops working without anyone noticing is the most dangerous scenario with a care record. Failed exchanges become visible and stay open until someone resolves them.

Logging of what has been exchanged

Which data went where, and when. With health data this is no luxury: it is what you need when a client asks a question or when there is an incident.

Who we build for

The reason for integrating differs greatly between organisations. Here are four situations we come across.

District nursing and home care

Scheduling and routes often sit alongside the EHR, and that is where the integration is missed most. The gain is that a change is made in one place instead of two. If care logistics is involved too, see care logistics software.

Organisations with their own management information

You want figures that the EHR does not provide in that form. The question here is whether you need a record integration or only aggregated data, and that makes a difference to both risk and lead time. For the broader care system, custom care software is the answer.

Care organisations with a client portal

A dedicated environment for clients or family, fed from the EHR. This requires the weightiest judgement about what may be visible and to whom; see also care compliance for the frameworks around it.

Chain partners and collaboration

Sharing data between organisations is legally very different from integrating within a single organisation. Have that legal basis established before anything is built. If an HKZ certification is involved, see HKZ quality manual.

Technology and integrations

Here the frameworks determine the design, not the other way round. NEN 7510 for information security in healthcare, a data processing agreement with every party that processes data, and logging that is sufficient to account afterwards for who saw what.

Node.js / Python / .NET PostgreSQL Exchange via the available interface Data minimisation as a design principle Encryption in transit and at rest Logging of every exchange Error handling with open alerts Roles and authorisation per team Retention periods enforced by the system Pseudonymisation where record data is not needed Support for NEN 7510 measures Data processing agreement and sub-processors documented Audit logging on access Hosting in the EU

Why Appfront

Health data drives the design

It is not the technology but the sensitivity that guides the choices. We design for as little data as possible outside the EHR, rather than for as many features as possible.

The EHR remains the source

A second record that drifts out of sync is worse than no integration at all. We retrieve only what is needed and store as little as possible.

A failure must never go unnoticed

In healthcare, an integration that fails unnoticed is the most dangerous scenario. Failed exchanges stay visibly open until they are resolved.

Honest about what we don't know

We are not a partner of the supplier. What is possible through the interface is established during the discovery phase; we do not promise an integration we have not seen.

Security and privacy

This is health data, and therefore special category personal data. That changes the entire approach: not just encryption and access control, but also the question of whether a given piece of data needs to leave the EHR at all. For many questions a count is enough rather than a record, and in that case we choose the count. What we do retrieve, we retrieve per role rather than per organisation: a planner has no need to see clinical reporting.

On the formal side, this should fit within your NEN 7510 framework, with a data processing agreement for every party that processes data and with sub-processors you know. Logging here is not an afterthought but part of the functionality: when a client asks, or in the event of an incident, you must be able to show which data was exchanged when and who viewed it. Whether your intended exchange is legally permitted is something you assess with your data protection officer; we build within those boundaries. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.

Frequently asked questions about a Puur integration

That depends on the interface the supplier makes available and on your contract and modules. We are not a partner of the supplier and do not promise an integration before we have established what is possible. That assessment is the first step and often takes weeks rather than days, partly because permissions and documentation are involved.

That is exactly what we want to avoid. The EHR remains the source; what we build alongside it retrieves what it needs and stores as little as possible. Data you keep separately will inevitably drift out of sync, and for a record on which care professionals base their decisions that is unacceptable.

Then it has to be visible. An exchange that stops unnoticed is the most dangerous scenario with a care record, because people keep relying on information that is no longer correct. We build failed exchanges as open alerts that only close once someone has dealt with them, and we show how old each piece of data is.

They shape the design, not the other way round. In practice that means data minimisation as the starting point, encryption in transit and at rest, role-based access, logging of who viewed what, and a retention period that the system enforces itself. Whether your intended exchange is permitted is something you assess with your data protection officer; we build within those boundaries.

Sometimes, and it is a heavier decision than reading. Writing back means a system outside the EHR changes the record, with all the questions of responsibility that come with that. We advise starting with read access and only writing back once there is a clearly defined process behind it.

Then the integration has to be redone, and that is a real risk with this kind of custom work. We limit that by isolating the exchange in a separate layer, so that your own application does not depend directly on the EHR. A switch then affects that layer and not the whole system.

We are not a partner of the supplier and we don't present ourselves as one. In practice, contact about the integration runs through you as the client, because you hold the contract. What we do is prepare the technical side so that this contact is concrete: which interface, which fields, which frequency.

That depends mainly on what the interface allows and how much data is really needed. A narrow, read-only integration is a manageable project; two-way traffic with a client portal is several times larger. Allow for the supplier's own lead time for the discovery work on their side. We give a well-founded estimate after the exploratory phase.

Ready to build a Puur integration?

Tell us which process currently runs alongside the EHR and which data is entered twice. The integration you need usually turns out to be narrower than expected. We build this as part of a broader custom software project or through smart API integrations.

Edit content