The client's goals, in their own words Reporting per goal, not per shift Evaluation on time and together

Custom support plan app for disability care

Appfront builds apps that let disability care organisations create the support plan the way it was meant to be: the client's goals in their own words, support workers who report per goal instead of per shift, and an evaluation that is scheduled on time and done together. So the plan doesn't disappear into the EHR, but becomes the conversation that comes back every day.

What is a support plan app in disability care?

The support plan in disability care describes what the client wants, what they need and how the organisation works towards it: goals, agreements, risks and their evaluation. The Quality Framework for Disability Care puts the client at the centre, and the Wlz (Long-term Care Act) requires the plan to be discussed and recorded with the client or their representative. An app makes that workable: goals the client formulates themselves, reporting per goal, an evaluation that automatically ends up on the agenda and a plan the client can read.

Without such an app, the plan is a form in the EHR that the key worker fills in once a year, in sentences the client doesn't recognise. Support workers report per shift, not per goal, so the evaluation starts with searching back through a year of reports. The representative receives the plan by post, signs it, and hears nothing more about it until the next evaluation.

We build custom software because the plan has to fit your methodology and your EHR: which domains you use, how you talk with the client and what the behavioural specialist adds. An EHR module is built for registration; the app is built for the conversation with the client and the support worker's daily work.

Planning with the client

Goals in the client's own words, with images or pictograms where language isn't enough, drawn up in conversation and immediately readable for the client and their representative.

Reporting per goal

The support worker reports on the goal in question, briefly and on their phone. The evaluation is then an overview per goal, not a search through shifts.

Evaluation and approval

The evaluation is scheduled before the deadline, completed together, and the new plan receives approval from the client or representative, recorded with name and date.

How we build your support plan app for disability care

We start with three client plans and the reports from recent months: what is in them, what happened, and how one relates to the other. The app follows from that.

1
Mapping methodology and EHR

Which domains and goals you use, how the planning meeting currently works, who attends, how support workers report and what must remain in the EHR for accountability.

2
Plan and goals

The structure of the plan in the app, with goals in the client's language, agreements, risks and the role of the behavioural specialist. Linked to the client and the care assessment in the EHR.

3
Reporting and client portal

Reporting per goal on the phone, the plan readable for the client and the representative, and the evaluation scheduled on time.

4
Integrating and taking over management

The integration with the EHR, approval with name and date, followed by maintenance and extension to day activities or outpatient support.

What a support plan app for disability care actually does

The components below appear at almost every disability care organisation. Which ones you need depends on your methodology and your EHR.

Support plan

Goals, agreements and risks per client, in their own words, with versions and the date on which the plan was adopted.

Reporting per goal

Brief reporting against the goal, on the phone, with the option to add a photo or a short voice note that is transcribed.

Evaluation scheduling

Evaluations scheduled automatically at the interval you use, with a reminder for the personal support worker and an invitation for the client.

Client portal

The client and their representative read the plan, see progress per goal and give their consent, on phone or tablet, with pictograms where needed.

Multidisciplinary consultation

The behavioural specialist, the doctor and the support staff add their input to the goal it concerns, visible in the consultation.

EHR integration

Client details and care assessment from the EHR, with the adopted plan and the reporting written back, so your accountability is accurate without double entry.

Who we build a support plan app for in disability care

The app is intended for organisations where the plan is currently mostly an obligation and where support workers don't use it as a guide in practice.

Residential care

Clients who are there every day, with support workers on rotating shifts. Reporting per goal on the phone and the handover per client are the core.

Day activities

Goals about work and activities, with support workers who see several clients at once. Brief reporting and the plan shared with the residential location matter most.

Outpatient support

Clients at home, with the support worker as a visitor. The plan on the phone and reporting straight after the visit are what's needed.

Organisations with a client council and representatives

Representatives who want to read along and take part in decisions. The portal with the plan, progress and consent is the core.

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

This page is about the support plan and the reporting against it. For the broader care software, see our page on building care software, for the messages with municipalities our page on an iWmo and iJw integration, and when choosing an EHR our EHR requirements list. You can read about our way of working on building custom software.

For drawing up and evaluating the plan in the office, alongside the app, there is our support plan software.

Support plan with versions and adoption Goals in the client's own language Reporting per goal on the phone Voice notes transcribed Evaluation scheduling with reminders Client portal with pictograms Consent from client or representative EHR integration Roles for support staff, behavioural specialist and doctor Reporting for quality accountability

Why Appfront for your support plan app in disability care?

A support plan only works if the client recognises it and the support worker uses it. That's what we build on: the client's plan, in everyday work.

The plan belongs to the client

Goals in their own words, readable on their phone, with their consent. Not a form about them, but a plan made with them.

Reporting happens at the goal

The support worker writes at the goal it concerns, briefly, at the moment itself. The evaluation practically writes itself.

The evaluation comes by itself

Scheduled at the right interval, with the invitation for the client and the representative. Not because the audit is coming, but because the plan calls for it.

Security and privacy for a support plan app in disability care

The app works with special category personal data about health. Access is set up per role and per client: the support worker sees the clients at their location, the behavioural specialist their caseload, and the client and their representative only their own plan. Every view and change is logged, and the app fits with your organisation's NEN 7510 set-up and the data processing agreement with your EHR supplier.

The app runs in a European data centre, with encrypted storage and daily backups. Integrations with the EHR use their own keys, which can be revoked per integration, and clients and representatives log in with two-step verification.

Frequently asked questions about a support plan app for disability care

Questions healthcare organisations ask before getting started.

It builds the plan together with the client, with goals in the client's own words, lets support workers report per goal on their phone, schedules the evaluation on time and records the approval of the client or their representative. The finalised plan goes to the EHR.

No. The EHR remains the record for registration, the care assessment and accountability. The app is where the plan is created and used: the conversation with the client, the goals, the reporting and the evaluation. The finalised plan and the reports go to the EHR via an integration.

With short sentences in the client's own language, pictograms and photos for goals, and a view on the phone or tablet that shows progress per goal. Which pictograms and which language you use will match the methodology your support workers already follow.

The framework asks for care that starts from the client's wishes, with a plan that is drawn up and evaluated together. The app makes that demonstrable: the goals come from the conversation, reporting is recorded per goal, the evaluation is documented and the client's approval is attached.

Yes. The legal representative, or the representative chosen by the client, gets access to the plan and progress, can respond and approves the finalised plan, with name and date. You record who has which role per client.

Arrangements covered by the Care and Compulsion Act (Wet zorg en dwang) are flagged separately in the plan, along with the evaluation points that go with them. The app puts those deadlines in the calendar; the assessment and the registration in the EHR remain part of your own process and your Wzd officer.

Check that first. Every EHR has a plan, and sometimes that is enough. A custom app makes sense if support workers don't actually report in it, if the client can't read the plan, if representatives have no access, or if evaluations only happen once the deadline has already passed.

A plan the client recognises and the support worker actually uses?

Tell us which EHR you use and how many plans are currently past their evaluation deadline. We'll show you what the plan, the reporting per goal and the portal look like.

Edit content