Custom app development for record access and logging in healthcare
As soon as a record is also opened outside the organisation, the logging challenge changes. A community nurse in a living room, a doctor on a locum shift, a practitioner at a second location: each of these moments is an action the patient is entitled to see, and they take place on a device that doesn't have to belong to the organisation.
Why mobile use makes this harder
The Wabvpz gives patients the right to free electronic access to their record and to an electronic copy, as well as the right to see the access log: who viewed or made available which data, and when. Both rights have applied since 1 July 2020.
As long as all access takes place from a workstation on the premises, this is a technical matter within a single system. With mobile use, that shifts. The question of who looked becomes the question of who was actually behind that screen, and that is harder to answer on a shared device in a car than on a workstation with a badge.
Then there is the capacity in which someone acts. A healthcare professional can open a record on the basis of a treatment relationship, as a cover for a colleague, or as part of an on-call shift. For logging, that difference matters, because it is exactly what a patient wants to know when they see a name they don't recognise. An app that only records that someone looked leaves that question unanswered.
How we build this
The action on the device is the unit that matters here. If who looked and why is recorded there, the logging on the back-office side is complete rather than partial.
Which roles open a record outside the organisation, and on which device. At most organisations there are more than expected, and some of them use a personal phone.
Treatment relationship, cover or on-call duty. Not a free choice after the fact but a precondition up front, because otherwise the log contains a reason nobody actually chose.
What is on the device can leave with it. We show what is needed for the visit rather than the full record, and clear it as soon as the visit is closed.
Patient access is a different app with different identity-verification requirements. We deliberately keep the two apart, even though they partly show the same data.
What the app actually does
The app serves two groups who must not see anything of each other. Which components you need depends on whether you build only the healthcare professional side or the patient side as well.
Opening with a reason
When opening a record, the healthcare professional states their capacity: treatment relationship, cover or on-call duty. That is the data point that gives the log its meaning, and it cannot be reconstructed afterwards.
Every action logged, on the device too
Viewing, changing, sharing and exporting are recorded with time and person, even if the action took place offline. An action that only reaches the system at synchronisation gets the time at which it actually happened.
Access for the patient
Patients view their data and their log in plain language, with an identity check appropriate to the sensitivity. That is a separate environment, not an extra screen in the same app.
Working without a connection
In a living room, a lift or a basement, the network drops out. The app keeps working with what is needed for that visit and synchronises afterwards, with the log intact.
Alerts on unusual access
A record opened without a treatment relationship, or unusually often. Noticing that before a patient asks is the difference between an internal conversation and a complaint.
Connection to your record system
The data stays in your existing system. We build the mobile layer alongside it through integrations and write the log back to the same place as the office side.
Who we build for
Where work happens outside the organisation differs greatly by type of care. Four situations.
District nursing and home care
The record is opened in the client's living room, on a device shared between shifts. The question of who actually looked is hardest to answer here and at the same time the most important.
Ambulatory and mobile teams
On the move, with changing locations and sometimes no signal. What is recorded offline must later end up in the log with the correct time, not the moment of synchronisation.
Cover and on-call duty
Outside office hours, someone opens a record without a fixed treatment relationship. That is precisely the access a patient asks questions about, and it is precisely where the reason is usually not recorded.
Occupational physicians and occupational health services
The relationship is more sensitive because the employer pays and the employee is the patient. Being able to show who viewed what is not a formality here but the core of trust. Complaints arising from this follow their own route; see complaints management software.
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
The app is a window onto your record system, not a second record. Everything it records ends up in the same log stream that the office side feeds.
Why Appfront
Who looked is a real question on a shared device
We tie permissions to the user, not the device, and enforce the capacity in which a record is accessed at the point of opening it. Without both, your logging is formally complete and substantively empty.
Offline, logging must not shift
An action gets the time at which it happened, not the time of synchronisation. Otherwise the timeline the patient sees will be wrong.
Don't show the patient your technical log
What is recorded is technical; what is shown should be readable. That translation is part of the design, not a presentation layer added afterwards.
One logging stream, not a second reality
The app writes to the same place as your office systems; see Wabvpz software for that side.
Security and privacy
A device holding patient data that leaves the premises calls for stricter choices than a workstation. We limit offline storage to what is needed for the visit at hand, clear it after the visit is closed, tie permissions to the user rather than the device, and make sure a lost device can be disconnected remotely without bringing colleagues' work to a halt.
The patient side calls for its own assessment, which carries more weight than in an ordinary app. Electronic access means you must be certain who is on the other end, and in healthcare the required level of assurance is high. That choice determines not only security but also how many patients actually log in. The logging overview is itself sensitive, because it shows which staff member opened which record; we therefore separate what a patient sees about themselves from what a manager may see about a staff member. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.
Frequently asked questions about the Wabvpz app
That's possible, and for part of the work it is enough. What a web version rarely does well is work offline and limit what remains stored locally. In community nursing and ambulatory teams, those are exactly the two things that decide whether it gets used in practice or whether a paper list appears instead.
No. Specified consent is in the law but never came into force; years were spent looking for a workable implementation, and none proved possible. Anyone building an app around it now is building around a rule that has no legal effect. Which consent framework does apply in your situation is something to agree with your own legal adviser.
By tying permissions to the user rather than the device, and by enforcing the capacity in which a record is accessed at the point of opening it. A shared login makes your logging formally complete and substantively worthless, because a team name appears where a person should be.
It gets the time at which the action actually took place, not the moment of synchronisation. Otherwise the timeline the patient sees will be wrong, and that is exactly the overview on which they base their question.
We advise against it. Care providers and patients need different permissions, different identity checks and a different view. We build this as two environments on the same data source, even though they look alike.
Usually, provided that system offers an integration for retrieving data and writing events back. What is available varies greatly by supplier; we map this out beforehand and promise no integration until we have seen what the system provides.
This app is about the moment a record is opened outside the organisation. The Wabvpz software collects the events from all your systems and translates them into an overview a patient can read. They share a single logging stream.
That depends on whether only the care provider side needs to be included or the patient side too, and on which login method you choose. Mobile access with logging is usually quick to get up and running; the patient side with identity verification takes more. We give a well-founded estimate after the discovery phase.
Logging access from outside the organisation?
Ask how many records were opened outside the premises last week, and whether the capacity in which they were opened was recorded. The gap between those two answers is the work. We build this as a standalone app and as part of a broader custom app or custom software project.