Skip to content
AI Ethiek & Governance

NEN 7510 Certification: Is an Official Certificate Mandatory?

Geert Haisma

An official NEN 7510 certificate is not legally mandatory, but demonstrated compliance is. Learn what Dutch regulators expect from care providers and software.

Laboratoriummedewerker in witte jas en handschoenen houdt een buisje bloed boven een analyseapparaat

NEN 7510 Certification: Is an Official Certificate Mandatory?

Formal NEN 7510 certification is not legally required for healthcare providers or software suppliers in the Netherlands, but demonstrable compliance with the NEN 7510 standard is. Statutory regulations stipulate that health information systems must adhere to the current security standard and undergo regular independent assessment. In daily operations, health insurers, regional care purchasing offices, and integrated care partners routinely require an accredited certificate as objective proof.

In short

  • No statutory requirement for a certificate: Neither the Dutch Decree on Electronic Data Processing by Healthcare Providers (Begz) nor the Health and Youth Care Inspectorate (IGJ) mandates a physical certificate.
  • Mandatory compliance with the standards: Healthcare organizations are legally bound to implement the security measures defined in NEN 7510, NEN 7512, and NEN 7513.
  • Independent review required: The IGJ expects organizations to have the operational effectiveness of their Information Security Management System (ISMS) evaluated by an independent party on a regular basis.
  • Procurement demands are stricter: In regional healthcare purchasing tenders (Wlz) and electronic health record integrations (such as Nedap ONS), holding an accredited certificate is almost always a contractual prerequisite.
  • AI adoption requires tight governance: Deploying artificial intelligence on patient records demands transparent logging, granular access controls, and strict data minimization.

What does Dutch law prescribe regarding NEN 7510?

The statutory framework for healthcare cybersecurity in the Netherlands rests upon the Additional Provisions for Processing Personal Data in Healthcare Act (Wabvpz) and its implementing decree, the Begz.

Under Article 3 of the Begz, healthcare providers must guarantee the safe and diligent operation of their health information systems. The decree explicitly refers to NEN 7510 and NEN 7512 as the binding baselines. For audit logging within patient records, the legislation directly points to NEN 7513.

While the law mandates compliance with these standards whenever electronic patient records are processed, it stops short of requiring an accredited third-party certification audit. Providers are technically free to choose how they substantiate compliance, provided the documentation is robust, up to date, and verifiable during regulatory reviews.

How does the healthcare inspectorate evaluate NEN 7510 certification?

The Dutch Health and Youth Care Inspectorate (IGJ) supervises the safety and continuity of medical services. Information security forms a permanent pillar of its supervision program, because cybersecurity breaches and data corruption directly endanger patient safety.

The IGJ confirms in its public guidance that an official NEN 7510 certification is not a formal legal obligation. However, the inspectorate requires every provider to operate a functioning Information Security Management System (ISMS) driven by a continuous Plan-Do-Check-Act cycle.

Furthermore, the IGJ instructs organizations to obtain periodic independent evaluations of their management system and risk controls. Undergoing an external audit by an accredited certification body is the most reliable way to meet this expectation. Organizations operating without an accredited certificate must produce internal audit files, penetration testing reports, and risk assessments upon request, which often leads to complex technical reviews during inspections.

Is certification mandatory for healthcare software vendors?

Software suppliers usually act as data processors under the General Data Protection Regulation (GDPR), while the statutory duties of the Begz target healthcare providers directly. Nevertheless, technology vendors face binding security mandates through two distinct channels:

  1. Contractual supply chain obligations: Under Article 28 of the GDPR and Begz rules, healthcare providers may only engage vendors that demonstrate adequate organizational and technical safeguards. Healthcare institutions therefore mandate NEN 7510 compliance in their data processing agreements.
  2. Operators of data exchange hubs: When a vendor provides an electronic communication system used to exchange patient records between autonomous providers, Article 5 of the Begz imposes a direct obligation. The operator must hold an independent expert audit report, no older than five years, certifying adherence to NEN 7510 and NEN 7512.

In competitive procurement procedures, such as tenders issued by Dutch long-term care administration offices (zorgkantoren), lacking an accredited certificate routinely results in immediate exclusion.

How does statutory obligation compare to market reality?

The table below contrasts formal legal duties with actual market expectations across different actors in the healthcare ecosystem.

Chain ParticipantLegal Duty under BegzStatutory Certificate NeededMarket & Supervisory Reality
Care providers (hospitals, nursing homes)Yes, security aligned with NEN 7510 and NEN 7512No, but demonstrable ISMS and audits requiredIGJ inspects ISMS; care purchasing offices require accredited certificates
Small practices (GPs, therapists)Yes, standards apply regardless of organization sizeNo, structured self-assessments are acceptedPeriodic IGJ spot checks on record confidentiality and access logging
Software vendors (EHR/ECP systems, portals)Indirectly via Article 28 GDPR processor agreementsNo, unless contractually imposed by clientMandatory prerequisite in tenders and API connections such as Nedap ONS
Electronic exchange system operatorsYes, direct conformity required (Begz Art. 5)Independent audit report required (max. 5 years old)Regulatory inspection and scrutiny by participating care providers

How does healthcare AI interact with NEN 7510 requirements?

Introducing generative language models and automated assistants into clinical workflows introduces new risk dimensions. When specialized software drafts progress notes or summarizes patient history, system architecture must comply with the control catalog in NEN 7510-2:2024.

Key compliance requirements include:

  • Data minimization and infrastructure: Clinical data must never be used to train foundational AI models. Data storage must remain within secure European data centers with zero data retention guarantees from model providers.
  • Traceable activity logging (NEN 7513): Every automated consultation of an electronic patient record must generate tamper-evident logs. Professionals must be able to verify when and why an algorithmic component retrieved specific health records.
  • Human oversight for clinical documentation: Automated systems should never autonomously overwrite or delete medical histories. Writing back into the client record must require explicit human review and confirmation.

Organizations exploring general-purpose workspace assistants face similar architectural hurdles. You can read more about these boundary lines in our analysis of Copilot Studio in regulated processes.

How it works at Prudai

Prudai develops specialized AI colleagues for knowledge-intensive domains, including ZIA for the healthcare sector. We believe modern care automation can only succeed when governance, data privacy, and information security are resolved by design.

Prudai is certified to ISO/IEC 27001:2022 and NEN 7510-1:2024. The certificates (NL 3143.1.1 and NL 3144.1.1) were issued by Brand Compliance, accredited by the Dutch Accreditation Council (RvA C 548), and are valid through 29 September 2029. This management system governs all internal engineering and operational routines.

For clinical day-to-day operations, our platform enforces clean technical boundaries:

  • All customer data is stored on dedicated servers in EU data centers (Hetzner), not with hyperscalers. Zero data retention is contractually agreed with model providers.
  • The Nedap ONS integration of ZIA reads the client profile and can write back exactly one item: a daily report, after ZIA presents the draft to the healthcare professional and requests explicit confirmation. No other report type, no edits, no deletions. ZIA always asks for your confirmation first. This integration is disabled by default and requires separate write permissions in Nedap.
  • ZIA operates on a validated source registry with 23 validated sources, ensuring output remains consistent and referenceable.

For the specialist

Data protection officers, information security leads, and health IT attorneys should note several legal mechanics under Dutch cybersecurity law:

Article 3 Begz and dynamic standard references

Article 3(1) of the Begz obliges providers to implement NEN 7510 and NEN 7512. Under Article 7 of the Begz, revisions issued by the Netherlands Standardization Institute (NEN) take effect once officially referenced in the Government Gazette by the Ministry of Health, Welfare and Sport. The current benchmark consists of NEN 7510-1:2024 (ISMS management requirements) and NEN 7510-2:2024+A1:2026 (security controls). Because NEN 7510-1 follows the ISO Harmonized Structure, organizations running ISO/IEC 27001 can integrate the sector-specific controls seamlessly.

Article 5 Begz for electronic exchange systems

When a non-provider operates an electronic data exchange infrastructure, Article 5(1) of the Begz activates a mandatory audit rule. The operator must hold an evaluation report drafted by an independent IT auditor (such as a registered RE auditor) confirming compliance with NEN 7510 and NEN 7512. The validity of this audit report is capped at five years.

Interaction with the EU NIS2 Directive

Healthcare providers designated as essential or important entities under the Dutch implementation of NIS2 (the Cyber Security Act) face statutory obligations for network resilience and risk management across supply chains. Maintaining an audited NEN 7510 management system provides the recognized structural baseline to demonstrate compliance to cybersecurity authorities.

Frequently asked questions

Is NEN 7510 certification legally required for independent medical practices?

No, obtaining a physical certificate is not legally required. However, the Begz mandates that every healthcare provider, regardless of staff size, configure its security management in line with NEN 7510 and NEN 7512. Independent practitioners can meet this standard by documenting risk assessments and implementing proportionate controls without formal certification.

Why do regional care purchasing offices demand an accredited certificate?

Long-term care administration bodies and health insurers bear statutory accountability for care quality and operational risk. In their contractual terms, purchasers have full discretion to demand safeguards beyond statutory baselines. An accredited NEN 7510 certificate provides immediate proof of compliance without requiring individual supplier audits.

Can healthcare organizations procure software without NEN 7510 certification?

Legally yes, provided the healthcare provider conducts its own comprehensive supplier audit and establishes strict data processor agreements. Because executing in-depth security assessments places heavy demands on internal IT and governance teams, institutions typically require vendors to present independent certification credentials upfront.

What is the structural difference between NEN 7510-1 and NEN 7510-2?

NEN 7510-1 specifies the governance requirements for an Information Security Management System (ISMS) and constitutes the normative standard against which certification audits take place. NEN 7510-2 provides the implementation catalog of security controls, covering areas such as cryptographic safeguards, role-based access management, and physical perimeter controls.

Sources

Would you like to know how ZIA combines secure AI support with strict safeguards for patient data and electronic health record integrations? Discover how our AI colleague for healthcare aligns with your information security framework.

Updated on 9 November 2026

AIData PrivacyDigital TransformationPublic Sector

Geert Haisma

Director

Geert Haisma is the co-founder and director of Prudai, an AI specialist that supports organizations in securely and custom-deploying generative AI for improved decision-making and process automation. With a background in public administration and years of experience in making organizations more successful, Haisma is the driving force behind Prudai's strategic and substantive direction.