Custom NEN 7512 integration file
The Decree on electronic data processing by healthcare providers (Besluit elektronische gegevensverwerking door zorgaanbieders) requires a healthcare provider to ensure, in line with NEN 7510 and NEN 7512, that its systems and the exchange systems it is connected to are used securely and with care. NEN 7512 covers the basis of trust for data exchange: what assurances parties give one another. If you have many integrations, with hospitals, GPs, pharmacies, labs and municipalities, it is easy to lose track. Appfront builds the integration file: for each exchange, the parties, the data, the risk class, the authentication, the agreements and the evidence, all in one place.
What is software for the NEN 7512 file of your healthcare data exchanges?
A NEN 7512 integration file records, for each electronic data exchange, how it has been set up securely and with care. Article 3 of the Decree on electronic data processing by healthcare providers requires a healthcare provider and the party responsible for an exchange system to comply with NEN 7510 and NEN 7512, that the exchange system works with a healthcare service provider authorised under NEN 7512, and that an administrator who is not a healthcare provider themselves holds an independent audit report that is no more than five years old. According to the explanatory notes to the Decree, NEN 7512 classifies communication by risk, with minimum requirements for authentication and identification for each class.
In practice, that information is scattered. The integration with the hospital was set up at some point by the application manager, the data processing agreement sits with procurement, the supplier's audit report is in a mailbox, and only the person who built it knows which login method belongs to which exchange. When the supervisory authority has a question, an external audit comes up or there is an incident, the search begins. A new edition of a standard, published by the minister in the Staatscourant (the Dutch Government Gazette), also means that every exchange has to be reviewed again.
We build custom software because every organisation has different integrations. A hospital exchanges data with GPs, pharmacies and regional networks, a care organisation for the elderly and long-term care with hospitals, elderly care physicians and municipalities, a lab with hundreds of requesters. Which exchanges you have, via which channels and suppliers, how your ISMS is set up and where your NEN 7513 logging is kept determines what the software does. The standards themselves are available free of charge from NEN; the software refers to them and does not reproduce the requirements.
Per integration
Parties, data, channel.
Risk and login
Class and authentication.
Evidence at hand
Audits and agreements.
How we build your software for the NEN 7512 file of your healthcare data exchanges
We start with your integrations and your paperwork: which exchanges there are, with whom, via which channel and supplier, which agreements and audit reports you hold and how your risk assessment currently works. Then we build a first version with the register of integrations, the risk class and the required authentication, because that is where the overview begins. Your security officer and application management work with it for a while. Monitoring of audit reports, reassessment when a new edition of a standard is published and the link with your ISMS and CMDB follow once that is going well. After that, we maintain the software as the rules or your integrations change.
Parties, channels, paperwork.
The first version.
Deadlines monitored.
Go-live, monitoring, and maintenance when things change.
What software for the NEN 7512 file of your healthcare data exchanges actually does
The components below appear in almost every integration file. Which ones you need depends on the number of exchanges and on your organisation.
Register
Every exchange in one place.
Risk class
Per communication process.
Authentication
Required and set up.
Agreements
Agreements per party.
Audits
Report and date monitored.
Reassessment
On a change or new standard.
Who we build software for the NEN 7512 file of your healthcare data exchanges for
The software is intended for healthcare organisations and operators of exchange systems with so many integrations that a spreadsheet can no longer keep up. The more parties and channels, the more it delivers.
Hospitals
GP, pharmacy, region.
Long-term care and mental health care
Handover and referral.
Labs and diagnostics
Many requesters.
Regional networks
Operator of the system.
Technology and integrations
This page is about the file of your data exchanges. For the security of your own systems as a whole, see our page on NEN 7510-compliant software, and for the full quality and compliance framework, our page on healthcare compliance software. If it is about the exchange itself, take a look at our pages on the ZorgMail integration, the medication handover integration or the zibs integration. You can read about our approach on custom software development.
Why Appfront for your software for the NEN 7512 file of your healthcare data exchanges?
An integration nobody knows the login method of, an operator's audit report that expired years ago, or an exchange that was never reviewed after a new edition of the standard raises questions for a healthcare organisation during an audit and, in the worst case, leads to a data breach. That is what we build on: every exchange with its risk and evidence, deadlines in view in good time, and the file ready when someone asks for it.
Overview
All integrations.
Demonstrable
Evidence per exchange.
Up to date
Reassessment monitored.
Security and privacy in software for the NEN 7512 file of your healthcare data exchanges
The file contains the architecture of your exchanges, and that is sensitive information. Access is set up per role: application management sees the technical details, the privacy officer the agreements, the security officer everything. Patient data is not included. Every change is recorded with name and time, and an uploaded audit report cannot be overwritten.
The software runs in a European data centre, with encrypted connections and storage and daily backups. If you want to run the file in your own environment, alongside your ISMS, that is possible too. We set up the software the way you would yourself for your systems under NEN 7510.
Frequently asked questions about software for the NEN 7512 file of your healthcare data exchanges
Questions that security officers, privacy officers and information managers in healthcare ask before they get started.
The file that records, for each electronic data exchange, who the data is exchanged with, which data, via which channel, with which risk class and which authentication, which agreements are in place and which evidence belongs to it. It shows that the exchange has been set up in accordance with NEN 7512.
Yes, through the Dutch Decree on electronic data processing by healthcare providers (Besluit elektronische gegevensverwerking door zorgaanbieders). Under NEN 7510 and NEN 7512, a healthcare provider must ensure the safe and careful use of its healthcare information system and of the exchange system it is connected to. The same applies to the party responsible for an exchange system.
NEN 7510 covers the information security of a healthcare organisation as a whole. NEN 7512 elaborates on it for the security of data exchange between parties in healthcare, and NEN 7513 for logging actions on electronic health records.
If the operator is not a healthcare provider itself, an independent organisation must have established that the operator and its system comply with NEN 7510 and NEN 7512, backed by an audit report. That assessment may not be more than five years old. The software keeps the report and the date for each operator.
The Decree assumes the latest edition. The minister announces a new edition in the Staatscourant (Government Gazette), with the date on which it takes effect. The software then prepares a reassessment for each exchange, so you can see which integrations have already been reviewed.
No. The standards are available free of charge via NEN. The software refers to the parts you apply and records how you have set this up for each exchange, without copying the text of the standard.
For organisations with many integrations, multiple channels and suppliers, or the role of operator of a regional exchange system. If you have a few exchanges via a single supplier, a well-maintained overview in your ISMS is often enough.
Is the file on your data exchanges in order?
Tell us how many integrations you have, with whom and via which channels, and how the overview is currently maintained. We will show you how the software can handle it.