Service · Software development

Custom NEN 7510 compliant software development.

Custom healthcare software that complies with NEN 7510, the Dutch information security standard for healthcare. Audit logging, role management, encryption and data residency are built in from the first design, not bolted on afterwards.

NEN 7510-1/2/3Audit loggingEncryptionEU data residency

NEN 7510 isn't a sticker you add afterwards.

NEN 7510 is the Dutch information security standard for the healthcare sector: a healthcare-specific supplement to ISO 27001, mandatory for any organisation that processes personal health data. The standard consists of three parts: NEN 7510-1 describes the management system, NEN 7510-2 the concrete controls, and NEN 7510-3 sets requirements for audit logging.

In practice, we often see that software that is "made compliant later" retains structural shortcomings: audit logs that the owner can switch off themselves, role models patched together with fixes, or cloud choices that don't pass a Schrems II assessment. We build it the other way round: compliance architecture first, then the features around it.

We work for healthcare institutions (hospitals, mental health care, long-term care), GP cooperatives, dentists and physiotherapists going digital, pharmacists, EHR vendors, insurers in the healthcare domain, healthcare IT suppliers and health-tech startups bringing their first medical product to market. For research institutions (university medical centres, RIVM, ZonMW consortia) we build platforms with pseudonymisation, purpose limitation and strict sub-processor control. We don't build a replacement for the EHR systems of ChipSoft, Epic, CGM, HiX or Topicus, but we do build the modules and portals that run alongside those systems and exchange data via HL7 FHIR or MedMij.

Three types of NEN 7510 programmes.

The standard is the same, but the scope of healthcare software varies widely. In the first conversation we'll advise which approach fits your situation: a patient portal calls for something different from a telemedicine platform or a research environment with pseudonymisation.

Compact project · fixed sprint budget

Patient or client portal

A secure environment where patients can view records, book appointments, complete questionnaires or communicate securely with their healthcare provider. Login with DigiD or MedMij, role-based access, an immutable audit trail and a patient-rights flow for access, correction and data portability.

DigiD / MedMijRole managementAudit logGDPR flow
Mid-sized project · fixed sprint budget

Healthcare module or telemedicine platform

A dedicated healthcare module alongside the EHR: referrer integration, telemedicine consultations, questionnaires with clinical scoring, or a module for specific conditions. Including HL7 FHIR integrations, encryption at rest and in transit, sub-processor management and a DPIA process with your DPO or CISO.

HL7 FHIRDPIAEncryptionSub-processors
Larger project · fixed sprint budget

Research or AI platform with healthcare data

A research platform with pseudonymisation and purpose limitation, or an AI tool that falls under the MDR and the AI Act in addition to NEN 7510. A mission-critical setup with IaC, security scans (Checkov, Trivy), an external pen test before go-live and a mapping document that lets your organisation demonstrably cover the standard.

PseudonymisationMDR + AI ActIaC + scansPen test

What you get at the end.

A working platform and the documentation you need to demonstrate compliance with the NEN 7510 requirements, whether to your own quality function, an external auditor or the Dutch Data Protection Authority.

  • Production-ready softwareProduction and staging environments in an EU region, running in your cloud (GCP, AWS Frankfurt, Azure West Europe) or with us. No US-only services in the critical path.
  • NEN 7510 mapping documentFor each control in NEN 7510-2, we record where and how it is implemented in the system. Ready to use as evidence for your certification.
  • Audit log compliant with NEN 7510-3Immutable logging of who accessed which record, when and from where. Separate storage domain, cannot be switched off by application administrators, configurable retention periods.
  • Codebase, IaC and runbooksFull source code, Terraform/Pulumi infrastructure as code, and runbooks for incident response, restore tests and the 72-hour data breach notification flow for the Dutch DPA.
  • Third-party pen test reportExternal security audit before go-live, with follow-up actions and a retest. We do not deliver until the findings have been resolved.
  • Training for your IT and compliance teamSessions for your application administrators, DPO and CISO on the architecture, using the audit log and the DPIA process for new features.
  • Maintenance contract (optional)Monitoring, backups, security patches, an annual pen test and ongoing development. Fixed monthly price with SLAs per severity category.

When custom NEN 7510 software is the right choice.

Four patterns in which we support healthcare organisations. Standard EHR replacement is not one of them: for ChipSoft, Epic, CGM or HiX we build modules around the system, not alternatives to it.

Alongside the EHR

A module the EHR doesn't offer

The EHR handles the core, but for a referrer portal, questionnaires with scoring or a patient journey app you run into its limits. You want something that connects via HL7 FHIR but sits under your own brand and compliance.

Health tech start-up

Taking your first healthcare product to market

You are building a digital therapeutic, a telemonitoring app or an AI diagnostics tool. NEN 7510 is unavoidable for selling to hospitals, and investors and buyers ask about it explicitly.

Research

Research platform with patient data

A university medical centre, research centre or consortium that needs to analyse data from multiple healthcare providers. Pseudonymisation, purpose limitation and watertight access control are not optional.

Cloud transition

Moving a legacy application to the cloud

An existing healthcare application still runs on-premises or in a setup that no longer passes the standard's assessment. You want to move to a modern EU cloud architecture without losing your compliance footing.

How a NEN 7510 project works.

1

Introduction and scope

A conversation in which we get to grips with your healthcare context: which data, which target group, which EHR, which partners. We identify early on whether the MDR, the AI Act or the WGBO (Dutch Medical Treatment Contracts Act) also plays a role alongside NEN 7510.

2

Compliance blueprint and architecture review

Together with your DPO or CISO, we map the architecture against NEN 7510-2 and NEN 7510-3. Data flows, sub-processors, encryption strategy, key management and the audit log design are fixed before we write any code.

3

Building in sprints with security by default

Two-week sprints with working builds. Secure-by-default frameworks, automated security scans (Checkov, Trivy, dependency checks) in the pipeline, and a DPIA update for every feature that touches personal health data.

4

External pen test and NEN mapping

Before go-live, we have an external security firm run a pen test. Findings go back into a sprint, followed by a retest. In parallel, we finalise the NEN 7510 mapping document so your audit process starts with the evidence in place.

5

Rollout and ongoing maintenance

A phased rollout, training for functional administrators and end users, and — if you wish — ongoing management with an annual pen test, patch management and quarterly DPIA reviews for new features.

The technical controls we set up as standard.

NEN 7510-2 describes controls at a high level. These are the concrete implementations we build into every healthcare application, regardless of scope. The custom work lies in how they come together, not in whether they are there.

Access

Role-based, least privilege, MFA

A role model based on the principle of least privilege, MFA mandatory for all users with access to patient data, session management with automatic logout, and device binding where needed. Login via DigiD, MedMij, or the healthcare organisation's IdP.

Encryption

Data at rest and in transit

AES-256 or stronger for data at rest, TLS 1.2+ for data in transit, client-side encryption for the most sensitive fields, and a key management strategy in which keys are kept separate from the encrypted data — often with a KMS or HSM integration.

Logging

Immutable audit trail

Audit log compliant with NEN 7510-3: write-only storage, a separate domain, impossible for functional administrators to disable, with retention configuration and alert rules for suspicious patterns (bulk queries, access outside office hours, access to your own record).

Patient rights

GDPR flow built in

A self-service or guided flow for access, rectification, restriction, erasure and data portability. In a healthcare context, erasure often means restricting access while retaining data for the statutory retention period — we build that nuance in properly.

Suppliers

Sub-processor management

An inventory of all cloud and SaaS suppliers in the chain, data processing agreements in order, a Schrems II assessment for each supplier with US ownership, and periodic review of the sub-processor register.

Incident

72-hour Dutch DPA notification flow

An incident response runbook with an escalation matrix, pre-drafted notification templates for the Dutch Data Protection Authority (Autoriteit Persoonsgegevens), and rehearsed restore procedures so that you can act within the required deadlines in practice.

Compliance overlays we often build in.

NEN 7510 rarely stands alone. Depending on what the software does, additional frameworks apply. A telemonitoring app that raises alarms is a medical device (MDR). An AI tool that predicts risk falls under the AI Act. A platform that exchanges patient data must comply with MedMij, and interoperability almost always runs via HL7 FHIR — or, for legacy integrations, via HL7v3 or EDIFACT.

We map out these overlays before we begin, so the design supports them rather than running into them. An MDR class IIa classification affects the development process (technical file, post-market surveillance), not just a tick box. In an enterprise healthcare context, we often see this layering in our enterprise software projects, and for research platforms in our broader healthcare software approach.

What we explicitly don't do: tick off NEN 7510 as a checklist and then resume feature work with no connection to it. The standard is a mindset — and we build that mindset structurally into the architecture, the development process and the governance of the team.

Frequently asked questions.

What healthcare clients usually want to know before we start.

What exactly is NEN 7510?
NEN 7510 is the Dutch standard for information security in healthcare and is mandatory for every organisation that processes personal health data. The standard consists of three parts: NEN 7510-1 describes the management system (governance, responsibilities, risk approach), NEN 7510-2 provides concrete controls (access, encryption, supplier management), and NEN 7510-3 sets specific requirements for logging access to patient data.
What is the difference between NEN 7510 and ISO 27001?
ISO 27001 is the international standard for information security across all sectors. NEN 7510 builds on it with healthcare-specific additions: stricter logging requirements, purpose limitation for health data, an explicit patient-rights flow and rules on sub-processors in healthcare. Anyone who meets NEN 7510 effectively also meets the basis of ISO 27001, but not the other way round. We also help with ISO 27001-compliant software if that is the broader scope.
How do NEN 7510, GDPR and MDR relate to each other?
They are three frameworks that stack. GDPR covers the processing of personal data and gives the patient rights. NEN 7510 translates information security into the healthcare context. MDR applies as soon as software classifies, diagnoses or treats, at which point it is a medical device. For AI applications the AI Act comes into play as well, often in the high-risk category. We advise on which frameworks apply and how they overlap. See also our page on GDPR compliance platforms.
What does the audit logging requirement of NEN 7510-3 mean in practice?
NEN 7510-3 requires every access to a patient record to be logged: who, what, when, from where. The logs must be immutable, retained for an extended period, and impossible for the application administrator to switch off, which separates the logging function from the user function. We implement audit logging as a first-class concept in the architecture (separate storage domain, write-only, separate keys), not as a Sentry offshoot added afterwards.
Can patient data be hosted in the cloud with AWS, Azure or Google Cloud?
Yes, provided it is in an EU region, with the right data processing agreement, encryption keys under your control, and a Schrems II assessment of US ownership risks. By default we deploy to AWS Frankfurt, Azure West Europe or GCP europe-west4, with client-side encryption for the most sensitive data. For some healthcare organisations the Schrems II risk weighs heavily enough to choose a European cloud (such as Cleura or a Dutch private cloud), and we keep that option open.
What is the typical scope of such a project?
A first portal module can be up and running within a few sprints. For a module alongside the EHR with FHIR integrations, audit log, DPIA and pen test, we plan a project of several sprints. A research or AI platform with pseudonymisation, MDR overlap and extensive governance is a longer project, which we plan per phase and evaluate along the way. It is comparable to our approach to healthcare software more broadly.
Do you work with our DPO, CISO and quality function?
Always. A NEN 7510 project without the DPO or CISO at the table does not work, as they hold final responsibility for the standard. We deliver architecture documents, DPIA input and mapping tables in a form that fits their review process, and we schedule working sessions at the start and at every major architectural decision. We also liaise directly with an external NEN auditor.
What does a NEN 7510-compliant project cost?
That depends heavily on scope: a single portal module is priced differently from a research platform with AI and MDR. We work with sprint budgets and provide a substantiated estimate per phase after the scoping session. The compliance overhead (DPIA, mapping, pen test, sub-processor management) is a fixed part of every phase, not an afterthought. The same approach applies as in our enterprise software projects.

Talk to us about your NEN 7510 project.

A no-obligation introductory call of half an hour. We listen to your healthcare context (which data, which EHR, which partners) and give direction on where the compliance risks and the solutions lie. No sales talk, just concrete advice. We also run similar compliance projects for KYC/AML compliance in other regulated sectors.

Edit content