Custom NEN 7513 integration development
Healthcare providers must record who has viewed or changed which electronic patient record. For this, the Decree on electronic data processing by healthcare providers (Besluit elektronische gegevensverwerking door zorgaanbieders) refers to NEN 7513, the standard for recording actions on personal health information. If that data is spread across the EHR, a portal, an app and integrations, you need an integration that brings the logging together and makes it auditable. Appfront builds that integration.
What is a NEN 7513 integration?
A NEN 7513 integration ensures that, across all your systems, you can show who has viewed, searched or changed which patient record. Article 5 of the Decree on electronic data processing by healthcare providers stipulates that the healthcare provider, as the party responsible for a healthcare information system, and the party responsible for an electronic exchange system, must ensure that the system's logging complies with NEN 7513. The Decree describes logging as the systematic automated recording of data and the files in which that record is stored. According to the Decree, NEN 7513 is the further elaboration of NEN 7510 for recording actions on electronic patient records.
The current edition is NEN 7513:2024, published on 1 December 2024, which replaces NEN 7513:2018. According to NEN, the standard provides a common framework for logging personal health information based on access and search events, with the aim of keeping the complete set of those events across the various information systems and domains auditable. The Decree refers to the latest edition of the standard, and the minister announces a new edition in the Staatscourant (Government Gazette). According to the Decree, the retention period for logging is set by representative organisations of healthcare providers and patients, in consultation with the Dutch Data Protection Authority.
We build this as custom software because logging differs from system to system in practice: the EHR logs in its own way, a portal or app does it differently, and an integration sometimes logs nothing at all. The integration collects the events from each system, converts them into a single, consistent format following the agreements in the standard, and stores them securely so that they cannot be altered afterwards. Your privacy or security officer can search them by patient, by staff member or by period, and have unusual patterns flagged. The Wabvpz (the Dutch act on client data processing in healthcare) also gives a client the right to see, on request, who has viewed or requested information via an electronic exchange system and on what date; the integration produces that overview from the same data.
Complete
Logging from all your systems.
Verifiable
Searching and flagging.
Secured
Cannot be changed afterwards.
How we build your NEN 7513 integration
We start with your systems: which applications display or exchange patient data, what they already log, where that logging is stored and who uses it. Then, based on NEN 7513, which you purchase from NEN yourself, we define which data is recorded per event and how we retrieve it from each system. We connect the system with the most access first, usually the EHR, and compare the result with what the system itself shows. The remaining systems follow, along with the search and flagging functions and the overview for clients. If a new edition of the standard is published, we update the integration.
What logs what, and where.
Recorded in line with the standard.
Connected and compared.
Remaining systems, and maintenance when a new edition is published.
What a NEN 7513 integration actually does
The components below appear in almost every NEN 7513 integration. Which ones you need depends on the number of systems and on what they already record themselves.
Collecting
Events from every system.
Unambiguous
One format for all logging.
Secured
Cannot be changed afterwards.
Search
Per patient or staff member.
Flagging
Unusual patterns reported.
Client overview
Who has viewed what.
Who we build a NEN 7513 integration for
The integration is intended for organisations where patient data is viewed or exchanged in more than one system, and for suppliers who want to get the logging of their package in order.
Healthcare organisations
Logging across all systems.
Exchange systems
Responsible for the logging.
Data protection officers
Checks on lawfulness.
Software builders
Logging in your healthcare package.
Technology and integrations
This page is about logging actions on patient records. If you want to know where your organisation stands on information security as a whole, take the NEN 7510 self-assessment or read about building NEN 7510 compliant software. For the file documenting your data exchanges, there is the NEN 7512 integration file, and for all standards frameworks together, healthcare compliance software. Who has access to which systems is managed with an IAM system. You can read about our approach at building software.
Why Appfront for your NEN 7513 integration?
Logging that sits in a different format in each system, an integration that records nothing, or a client request that takes a lot of digging all make it hard to demonstrate that access was lawful. That is what we build on: logging from all your systems in one format, stored securely and searchable by those authorised to do so.
Full
All systems, one overview.
Reliable
Cannot be altered afterwards.
Usable
Search, flag, report.
Security and privacy in a NEN 7513 integration
Logging of access to patient records is itself sensitive information: it shows who viewed which patient. The integration records only what is needed for the review, protects the storage against modification and deletion, and gives access to search and reporting only to staff with a defined role. Anyone who consults the logs is logged as well.
The integration runs in a European data centre or in your own environment, with encrypted connections and storage. We set the retention period according to what applies to your organisation, and once it expires the logs are deleted. We agree in advance with you which officers may see which reports.
Frequently asked questions about a NEN 7513 integration
Questions that privacy and security officers, information managers and healthcare software suppliers ask before getting started.
The Dutch standard for recording actions on personal health information. According to NEN, it provides a common framework for logging based on access and search events. The current edition is NEN 7513:2024, which replaces NEN 7513:2018.
The Decree on electronic data processing by healthcare providers (Besluit elektronische gegevensverwerking door zorgaanbieders) stipulates that the healthcare provider, as the party responsible for a healthcare information system, and the party responsible for an electronic exchange system, must ensure that logging complies with NEN 7513.
NEN 7510 covers the organisational and technical set-up of information security in healthcare as a whole. According to the Decree, NEN 7513 is a more detailed elaboration of it, specifically for recording actions on electronic patient records.
Yes. Under Article 15e of the Dutch Act on supplementary provisions for the processing of personal data in healthcare (Wabvpz), at the client's request the healthcare provider includes in the copy who has made information available via the electronic exchange system, and who has viewed or requested information, with the date.
The Decree states that organisations representing healthcare providers and patients, in consultation with the Dutch Data Protection Authority, set the retention period, and failing that, the minister does. We configure the integration to the period that applies to your organisation.
Yes, if your systems support it. FHIR has its own resource for recording events, AuditEvent. The integration can receive or provide events in that format, alongside other sources such as log files and databases.
For organisations with multiple systems in which patient data is viewed or exchanged, and for suppliers who want to improve the logging of their package. If you work with a single system that already handles logging and reporting in full, a custom integration is usually not needed.
Your NEN 7513 logging in one place?
Tell us which systems are used to view patient data and what they currently log. We'll show you how an integration brings it together.