Custom software for electronic access and logging in healthcare
The Wabvpz is usually summarised as the right to electronic access. Almost everyone builds that part. The second right gets neglected: patients may see who has viewed or made available which data, and when. That is not a small screen but a requirement on your entire architecture, because you can only show what you have recorded along the way.
Two rights, and a third that does not exist
The Wabvpz (Additional Provisions on the Processing of Personal Data in Healthcare Act) gives every patient the right to electronic access to their record and to an electronic copy of it, free of charge. That is Article 15d, and it has applied since 1 July 2020. In addition, Article 15e gives the right of access to the log: who viewed or made available which data, and when.
That second right is the difficult one. Showing access can be done from your existing record; showing the log is only possible if who did what has been recorded along the way, in a form someone without a technical background can understand. Many systems do log something, but in technical terms, spread across components and often without the context the patient is looking for.
There is one more point where things structurally go wrong, and it goes the other way. The law also contains specified consent, under which patients would give consent per category of data and per category of care provider. That part never entered into force: after years of searching, a workable implementation proved impossible. Anyone who builds a system around specified consent is building around a rule that legally does not exist.
As soon as a record is also opened outside the institution, the question of who looked changes. How to record that on a shared device is covered on the Wabvpz app page.
How we build this
Here the event is the unit: one action, one person, one moment. If it is recorded at the moment it happens, log access becomes a view rather than a reconstruction.
We look at which actions your current systems register and what is missing. At most care providers it is not that little, but it is unusable because the context is missing.
A log line saying that a user account accessed a resource is no answer for a patient. For each action, we design what is shown and to whom.
The patient sees a view, not how you maintain your records. That separates responsibilities and prevents a change in your system from affecting the right of access.
We run through a request for log access and see how much manual work sits underneath. That figure is what each request will cost you.
What the software actually does
Recording events underpins everything; access and copy are views of that. Which components you need depends on what your record system already provides.
Logging in an understandable form
For each event: who, when, which data and for what reason, written the way a patient can read it. A technical log line does not satisfy a right intended for the patient themselves.
Electronic access and copy
Patients view their data and obtain a copy, free of charge. The copy is a representation of the record at that moment, not a copy of your database.
Disclosure recorded separately
Not only who looked, but also to whom data was made available. That is a separate event, and precisely the one patients ask about.
Consents as they actually apply
Recording what a patient has permitted and to whom, under the framework that actually applies. We don't build a structure around specified consent, because it never came into force.
Alerts on unusual access
A record opened outside the treatment relationship, or unusually often. Spotting that before a patient asks is the difference between an internal conversation and a complaint.
Connection to your record system
Data stays in your existing system. We build the access and logging layer alongside it using integrations, rather than creating a second record.
Who we build for
What you need to build yourself depends on your system and your size. Four situations.
Organisations with their own record system
You manage the record yourself and so carry the full obligation. Logging often exists but is spread across components and cannot be shown to a patient. If you also fall under the Cybersecurity Act, you will need a separate duty-of-care file as well.
Practices using a supplier's package
Your supplier provides access, but access to the logs is often limited or missing. The question then is what you add yourself and what you leave with your supplier; that is a contractual question as much as a technical one. We build a dedicated patient environment as a portal on top of your package.
Care with many chain partners
When organisations collaborate, disclosure becomes more important than access. Every exchange with another provider is an event the patient is entitled to see, and it takes place outside your screen, usually via integrations with a chain partner.
Occupational physicians and occupational health services
The relationship is more sensitive here because the employer pays and the employee is the patient. That is precisely why being able to show who viewed what is not a formality but the core of trust. You set up a reporting channel for incidents separately; see the incident reporting portal.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
A lot is changing around data exchange in healthcare, including through the Wegiz (Dutch Healthcare Data Exchange Act) with designated exchanges. Everything connected to this should be configurable and stored per version.
Why Appfront
Logging is the real build
Showing access can come from your record system; showing logs is only possible if you have recorded along the way who did what, in language a patient understands.
We don't build around a rule that doesn't apply
Specified consent is in the law but never came into force. We say so, rather than selling you a module for it.
Your record system stays in place
We build the access and logging layer alongside it using integrations. Migrating a record system just to obtain a right of access is the most expensive route.
The log overview is itself sensitive
Anyone who can see who opened which record also learns something about your staff. We apply separate permissions to this and show the data subject only what concerns them.
Security and privacy
This topic turns the usual security question on its head. Normally you protect data from being viewed; here you have to make access possible for the data subject, without letting anyone else look over their shoulder. The logging overview is itself sensitive: it shows which employee opened which record. That is why we separate what a patient sees about their own record from what a manager may see about an employee, and we also record access to the logging itself.
The identity side is the second half. Electronic access requires you to be certain who is on the other end, and in healthcare that level is high. This is not something you build yourself but an integration you choose, and that choice determines how many patients actually log in. On the retention side, events must be immutable and the logging must be kept longer than an ordinary application log, because the right of access looks backwards. How we handle security ourselves is set out in our information security policy; external reports go through our CVD policy.
Frequently asked questions about the Wabvpz
Free electronic access to their record and an electronic copy of it, plus access to the logging: who viewed or made available which data, and when. Both have applied since 1 July 2020. In practice, the second right is implemented far less often than the first.
No. Specified consent is in the law but never came into force; a workable implementation was sought for years and proved impossible. Anyone building a system around it now is building around a rule that does not legally apply. Check with your own legal adviser which consent framework does apply in your situation.
Enough to answer the patient's question: who, when, which data, and whether it was a matter of access or of making data available to someone else. A technical log line with a user ID and a table name is not sufficient, because the right is intended for the patient themselves. That means translating it into plain language is part of the design.
Usually not. Systems generally log for administration and debugging, with a short retention period and without context. What the law requires is a longer-retained, understandable view for the data subject. We first look at what already exists and build only what is missing; that is almost always cheaper than starting over.
Yes, and that is the recommended route. The data stays where it is and we build the access and logging side alongside it, connected via integrations. A record migration just to fulfil a right of access is a big project for a small goal.
That is a separate track. The Wabvpz is about the patient's rights to access and logging; the Wegiz makes electronic data exchange mandatory for designated exchanges between healthcare providers. They overlap, because every exchange is a disclosure the patient is entitled to see. Which exchanges are designated for you changes over time; check this separately.
The patient, for their own record. Within your organisation the overview is more sensitive than it seems, because it also shows which of your employees opened what, and that touches on their employment relationship. We set up separate permissions for this and also record access to the logging itself.
That depends on what your current system already records, how many systems need to be integrated and which login method you choose. A logging view on existing events is usually quick to make usable; completing the recording in older systems takes more. We provide a substantiated estimate after the discovery phase.
Ready to implement access and logging?
Ask your system administrator who looked at a random record last month, and whether that answer could be shown to a patient. The difference between those two is the work. We build this as a standalone application and as part of a broader custom software project.