The first minute counts Report without judgement Works without a connection

Custom app for reporting incidents in healthcare

A calamity starts as something nobody knows the nature of yet. Whether it is established later depends on whether it was reported at all, and that happens in the first minute after a shift, standing in a corridor with a phone in your hand. Every hurdle at that moment costs you a report you needed.

Why the first minute decides everything

The Wkkgz (Dutch Quality, Complaints and Disputes in Healthcare Act) requires care providers to report calamities, violence within the care relationship and dismissals for serious malfunctioning to the inspectorate, each within three working days of being established. You also need to be able to report and investigate incidents internally, because without that internal flow there is nothing to establish anything from.

That internal report is the foundation and, at the same time, the weakest point. It is made by people who have just finished a shift, often not at a desk, and who feel that a report could count against them. A form with thirty fields on a workstation in the team room yields the reports that someone considered important enough to sit down for.

What you miss are the others. The near misses, the things that turn out to be a pattern in hindsight, the event that only proves to be a calamity a week later. These are only reported if reporting takes less effort than not reporting, and that is a design question, not a policy question.

How we build this

The report at the moment itself is the unit here. If it comes in, the organisation can then determine what it is; if it doesn't come in, there is nothing to determine.

1
Looking at where reports aren't made today

We don't ask what has been reported but what hasn't been reported, and why. That conversation produces the design, more so than the report form you have now.

2
Reducing it to a few taps

What, where, when and how serious, in fixed choices with room for free text. Anything beyond that is a reason to skip it.

3
Building in reporting without judgement

The reporter doesn't classify and doesn't assess. They describe, and the organisation weighs. That lowers the threshold and prevents a calamity from coming in as a minor incident.

4
Passing it on for assessment

Every report ends up in the process where it is weighed up to determine what it is. That side is covered on the Wkkgz software page; the app stops at reporting.

What the app actually does

The app does little, and that little must be usable one-handed in a corridor. Which components you need depends on your type of care and your reporting culture.

Reporting in a few taps

What happened, where and when, with fixed choices and room for your own words. The app fills in what it already knows: time, location, reporter and shift.

Describing without classifying

The reporter doesn't say whether it is an incident or a calamity; that is a judgement the organisation makes later. This way, cases that someone thinks aren't serious also come in.

Photo where possible and permitted

For material damage or an unsafe situation, an image is faster than text. For events involving a client, restraint applies, and the app enforces that as a rule rather than as advice.

Working without a connection

At a client's home, in a basement or in a lift. The report is stored locally with the actual time and sent as soon as there is a connection.

Confidential reporting where appropriate

Some reports concern colleagues or the organisation itself. A route where the reporter isn't directly visible to their own manager yields reports that would otherwise never come.

Passing it on to your reporting system

The report ends up in the system your committee works in, via integrations. The assessment and the deadlines are covered on Wkkgz software.

Who we build for

Where and when reports are made varies greatly by type of care. Four situations.

Hospitals and clinics

There is a reporting system and a committee, but reporting happens at a workstation after the shift. The gain lies in the reports that now get stuck in the corridor.

Long-term care and disability care

Incidents between clients also fall under the duty to report. They are often seen as part of everyday reality and so go unreported. What happens with a complaint from a family member or other close relation is handled through complaints management software.

District nursing and outreach teams

The care professional is alone at the client's home with no colleague to talk it over with. Reporting there and then, offline, is the difference between a report and no report at all.

Small practices

No committee and no reporting system, but the same obligation. Here the app is often the entire system rather than the front end of one, with the deadline monitoring from the Wkkgz software alongside it.

Not sure about a large project yet?

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 the front end of your reporting process, not a separate register. What is reported through it ends up where your organisation reviews it.

React Native or native iOS and Android Offline storage with the actual time of the incident Short form with fixed options No classification by the reporter Photos with rules per type of report Confidential route alongside the regular one Integration with your incident reporting system Feedback to the reporter Roles per team and per location Limited offline storage of client data Remote device management Multilingual display where needed Audit logging per report Hosting in the EU

Why Appfront

Reporting must take less effort than not reporting

That is the only measure that counts. We design for the number of taps, not for the completeness of the form.

The reporter does not classify

Anyone who has to choose between an incident and a serious adverse event will choose the lower one. We let the reporter describe what happened and the organisation assess it, because that assessment determines a deadline.

There is no signal at the client's home

The report is saved locally with the actual time it happened. That time matters later, because deadlines depend on it.

Feedback keeps reporting going

A reporter who never hears anything back will not report next time. That is why we build in short feedback, even when the outcome is that nothing was done with the report.

Security and privacy

A reporting app on a device that goes out into the field holds data about clients and sometimes about colleagues. We limit offline storage to the user's own open reports, show no client records in the app, and make sure a lost device can be disconnected remotely. Permissions are tied to the user and not to the device, even when a team shares a single phone.

There is also a matter of trust that shapes the design. A report may concern a colleague's actions or the organisation itself, and if the reporter suspects their name will land with their manager straight away, they will not report. That is why we build a route in which the reporter is not immediately visible to their own line management, with a limited circle who can see the identity when the investigation requires it. That is an organisational choice you make beforehand; we implement it. 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 reporting app

Because the form produces the reports someone sits down to write. What you are missing are the incidents that get thought of in a corridor and then forgotten. In district nursing and outreach teams, there is often no workstation within reach at all at the moment it happens.

No, and that is deliberate. Anyone who has to choose between an incident and a serious adverse event will choose the lower one, and then a report comes in without a deadline attached. The reporter describes what happened; the organisation determines what it is, and only at that point does the three-working-day deadline start.

Fully anonymous reporting often makes investigation impossible, which serves neither the reporter nor the client. What does work is a route where the reporter's identity is known to a limited circle and not to their own line manager. Where that line is drawn is a choice for your organisation; we build it in.

Yes, that is the starting point. The report is stored locally with the actual time and sent as soon as there is a connection. That time matters later, because deadlines are attached to how the report is handled.

In an unsafe situation or in the case of material damage, an image is quicker and clearer than text. For incidents where a client appears in the image, restraint applies and sometimes a ban. We set that rule per type of report in the app rather than leaving it to the reporter's judgement.

They should, and it is the cheapest way to keep reporting behaviour going. Someone who never hears anything back won't report next time. A short piece of feedback is enough, even if the outcome is that nothing further was done with it.

This app is the front end: reporting at the moment itself. The Wkkgz software covers what happens afterwards: the assessment, the determination moment and the deadlines towards the inspectorate. They share a single flow.

That depends on the number of report types, whether the confidential route is needed and which system it is integrated with. Reporting with a photo and offline use is usually quick to get working; the confidential route and feedback cost more. We give a well-founded estimate after the discovery phase.

Getting more reports in?

Ask a nurse what was not reported this month and why not. That answer is your design brief. We build this as a standalone app and as part of a broader custom app or custom software project.

Edit content