The moment determines the message At the client's, not at the office Works without a connection

Custom app for start, stop and hours in youth care

A start message should be about the day the care actually began. In practice, that's the day a care worker first stepped into a family's home, and a week later that date ends up in the system when someone updates their week. That difference of days is exactly what a claim is later rejected on.

Why the moment itself matters

In the Youth Act (Jeugdwet) chain, the messages follow one another: the municipality grants the allocation, the provider reports that care is starting, later reports that it has ended, and claims for what was delivered. Each of those messages contains data, and that data must match each other and the allocation.

The start moment is the trickiest part, because it takes place outside the office. A care worker goes on a home visit, and whether that conversation is already care or still an introduction is a judgement on the substance that they make on the spot. If that judgement is only recorded a week later, it is no longer the judgement but a reconstruction.

The same applies at the end. Care rarely ends on an announced date; it fizzles out, or stops because a family moves. If you only notice this at the quarterly check, you keep claiming for a period in which nothing was delivered, and that comes back as a rejection or a recovery.

How we build this

Here, the contact moment is the unit. If what happened and when is recorded there, the messages follow from it rather than from a weekly close.

1
Shadowing a care worker

We look at what a day looks like, when things are recorded and why not sooner. Almost always, the answer is that it doesn't fit in after a home visit.

2
Reducing recording to a few taps

Who, when, what type of contact, how long. Everything beyond that is postponed, and postponing is exactly the problem we're solving.

3
Offline as the starting point

At a family's home, in a car or at a school. The app keeps working and syncs later, with the actual time.

4
Letting messages follow from the registration

From what has been recorded, the administration compiles the start, stop and claim messages. The care worker has no knowledge of this, and shouldn't need any.

What the app actually does

The app does little, and that little must be usable in a stairwell. Which components you need depends on your forms of care.

Start and end at the moment itself

The care worker records that care has started or ended, with the correct date. That is the date the message rests on, and it can't be reconstructed afterwards.

Recording contact in a few taps

Type of contact, duration and whether it concerns care delivered. Fixed choices, with room for a short note; anything that takes longer doesn't happen after a home visit.

Working fully offline

In a living room, a car or a school, the network drops out. Recording carries on with the actual time and synchronises afterwards.

Alert on deviation from the allocation

More hours than allocated, care outside the allocated period, a product that doesn't match. Seeing that at the moment itself is the difference between adjusting course and recovering payments.

As little as possible on the device

A care worker needs the details of their own clients for that day, not the full file. That limits what is stored offline and what is exposed if a device is lost.

Passing it on to the finance team

What has been recorded goes via integrations to the system that compiles the messages. That side is covered on Youth Act software.

Who we build for

Where and when recording takes place varies greatly by form of care. Four situations.

Outpatient youth care

The care worker is out on the road all day and rarely in the office. This is where the difference between recording at the moment and at the end of the week is greatest.

Residential care and day treatment

Care is continuous and the start date is clear, but changes such as absence and leave do determine what can be claimed. Those arise on the group.

Youth mental health care and specialist care

Care pathways run long and change shape. As a result, the alignment with the allocation gradually shifts, and the practitioner notices this before the administration does.

Freelance care workers and small practices

You are the administration yourself. What matters most then is that recording happens during the work, because there is nobody to straighten it out for you later.

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 field side of your care administration and does not compile messages itself. What it records ends up in the system that builds and sends the iJw messages.

React Native or native iOS and Android Offline storage with the actual time Start and stop registration per care pathway Contact registration with type and duration Alert on deviation from the allocation Limited offline storage of client data Integration with your care administration Roles per team and per care pathway Disconnecting a device remotely Immutable recording of moments Retention periods per data type Multiple municipalities and products Audit logging per action Hosting in the EU

Why Appfront

The date in the message must be the real date

We record start and end at the moment itself. A week later it's a reconstruction, and that is what gets your claim rejected.

There is no signal at a family's home

Offline is the starting point, with the actual time. An app that stalls there gets replaced by a note on a phone.

The care worker is the first to notice a deviation from the allocation

We show the alert there, because adjusting course during the care pathway is cheaper than recovering payments afterwards.

This concerns young people on a device outside the office

We only show that day's clients and not the full file, and keep offline storage as small as possible.

Security and privacy

A device holding data about young people that goes along on home visits calls for stricter choices than a workstation. We limit offline storage to that day's clients and appointments, show no complete records in the app, tie permissions to the user rather than the device, and make sure a lost device can be disconnected remotely.

There is also a boundary of substance that shapes the design. An app that records that care was delivered does not need to record what was discussed; that belongs in the record, not in a registration that administrative staff can also see. We therefore do not build a free-text field for case notes, however handy that may seem. What the app does record, the moments and the duration, must be immutable, because financial accountability depends on it. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.

Frequently asked questions about the youth care app

Because the date in a start or stop message must be the date on which the care actually began or ended. If it is entered a week later, it is a reconstruction, and that is exactly where the discrepancies with the allocation arise that get claims rejected. Entering it afterwards does not save time, it costs money.

No, and that is deliberate. The app records what happened; the administration team then compiles the messages from that and sends them via the switchboard or the data hub. That way a care worker does not need to know anything about message numbers, and responsibility for the claim stays where it belongs.

Yes, that is the starting point. Entries are stored locally with the actual time and sent as soon as there is a connection. On home visits this is not an edge case but the normal situation, especially in older houses and in the car.

Yes, and it helps a great deal. If they can see how many hours or which product has been allocated, they notice for themselves when they are going over, and a new allocation can be requested in time. That is the difference between adjusting course and recovering money afterwards.

We advise against it. What was discussed belongs in the client record, not in a registration that administration and auditors can also see. Keeping the two separate keeps the circle of people who see the substantive data small, which is exactly what you want for this target group.

Yes, and it is usually the reason for the project. Each municipality uses its own product codes and agreements within the same standard. The app shows the care worker only what applies to their client; the differences sit in the administration behind it.

No. Your system remains the client administration and keeps handling the messages; see also Wmo and youth care software. What we add is the field side, so that the data is created at the moment it is accurate.

That depends on the number of care types, whether the signal on the allocation needs to be included, and which system it is integrated with. Start, stop and contact registration are usually quick to get working; the integration and the alerting take more effort. We provide a well-founded estimate after the discovery phase.

Recording moments as they happen?

Ask a care worker when they recorded the care for their most recent new client, and compare that with the start date. That difference is what gets your claims rejected. We build this as a standalone app and as part of a broader custom app or custom software project.

Edit content