Skip to content
NLBook a call

A day in the Helpman district

De Linde in Groningen is an example company. It is a district nursing team with four routes and a planner.

  1. A colleague calls in sick

    The rota is in Excel and changes go through the group chat.

    Sanne off sick! Split up route 3. Insulin 08:00 first!
  2. Mrs Groen's leg is swollen

    The photo is in the client file, the medication chart is on paper, and the GP does not hear about it until after two.

    Handover bookWed 23 Sep
    Mrs Groen: leg swollen
    phone GP!! (Noor)
    Els comes Thu afternoon
  3. Two billing lines are rejected

    A change to the schedule was never recorded. Now someone has to dig through the care notes to find out what was actually done.

    V
    Vecozo, claim responseto: administratie@delinde-groningen.nl
    16:30
    September billing: 2 lines rejected
    Two services from 23 September have been rejected. Check the care delivered and resubmit them.
  4. Els messages about tomorrow

    It is on one colleague's phone. Tomorrow's route has not been updated yet.

Time not spent with the client

Who takes over Sanne's route?

The rota is in Excel. A colleague off sick means reshuffling in the group chat, and clients phone to ask when someone is coming.

Daily routes that take into account assessed care needs, times and who is qualified to give which care.

Care notes written after the shift, or at the weekend

Notes are written up afterwards, and sometimes twice, in the ECD (the electronic client record) and on paper. Record-keeping takes up to 30 per cent of working time.

Care notes on a phone at the client's home, recording only what differs from the care plan.

A handover that gets stuck in the group chat

What the morning shift saw is in a notebook or a chat message. The evening shift and the GP hear about it too late.

A handover in the app instead of the group chat, and family members who can read it too, where that is allowed.

Is this month's billing right?

Only at billing time does it turn out that a change was never recorded. Then someone digs through the care notes to find out what really happened.

Seeing each day what went to plan and what did not, so the billing is right before it goes out.

The ECD remains the source

We build alongside it, not in place of it. What we build is the part that now lives in Excel and the group chat.

  • Nedap Ons, Ecare or Fieritthe ECD, with care plan and client file
  • Vecozothe Dutch billing platform for care, as it works now
  • the client portalif you already have one
Your systembuilt around how you work

What care organisations ask us

We already have an ECD, and we can't do without it.

Nor do you need to. The ECD remains the source, and we build what is missing alongside it, such as the routes, the handover or the check before billing.

Our carers don't want a second app.

Fair enough. If the work goes to plan, there should be no extra recording, so we make it shorter than it is now and record only what differs.

Is that even allowed, with health data?

That is settled in the design. Client data sits in a secure environment instead of a group chat, and we set who sees what for each role.

Does this also work for care at home under the Wmo (Social Support Act) or the Wlz (Long-term Care Act)?

Yes. In district nursing, the district nurse assesses the care needs, and the records have to match the care plan. For home help and support under the Wmo, what counts is the allocation, the hours and the messages to the local council. Under the Wlz at home, it is about more hours per client and more people around the client.

What does it cost?

One fixed price, agreed after the design, and no charge per client. It depends on what we build first, whether that is the routes, the handover or the check before billing.

With the planner and out in the district

We sit in with the planner and, if we may, cycle round with one of your team for a morning. Afterwards we write up what we would build.

Week 1we visit
Week 3on paper
Week 8 to 10live

Fixed price, agreed once you approve the design. The code and data are in your name.

How those weeks go

For example, which software you use and where things get stuck.

We only use your name, email address and message to reply to you. If nothing comes of it, we delete them within six months. This site sets no cookies. Privacy statement.