Move-ins and move-outs

Convert client changes in ONS into completed move-in and move-out requests in TOPdesk.

Overview

When a client's care ends, the room and location change must be registered in TOPdesk. This automation retrieves recent care terminations from ONS, translates the client's room into the correct location, submits the request, and skips clients who have already been processed or whose data is incomplete.

What has changed

  • Less manual administration
  • Client departures are processed faster
  • Room and location changes are registered consistently every time

At a glance

SECTOR:
VVT
System:
Nedap ONS, TOPdesk, Excel
RUNS:
Every 2 hours
Technique:
Rule-based

In één oogopslag

SECTOR:
VVT
Systeem:
Nedap ONS, TOPdesk, Excel
RUNS:
Every 2 hours
Techniek:
Rule-based

Overzicht

When a client's care ends, the room and location change must be registered in TOPdesk. This automation retrieves recent care terminations from ONS, translates the client's room into the correct location, submits the request, and skips clients who have already been processed or whose data is incomplete.

Wat er verandert

  • Less manual administration
  • Client departures are processed faster
  • Room and location changes are registered consistently every time

How it works.

Nedap ONS recent care endings
Client #3102done
Client #3115done
Client #3121running
Already processed: skipped
Every 2 hours
Y
Yara maps room
to location
TOPdesk requests submitted
Room 2.14 · site Asubmitted
Room 1.03 · site Bsubmitted
Client #3121incomplete
Clients marked as processed
Every result is logged, nothing is done twice.

What it does per client

  1. Generates a report of recent care terminations from ONS
  2. Skips clients who have already been processed or have incomplete data
  3. Looks up the client's main location and room
  4. Translates the room into a TOPdesk location using a mapping file
  5. Fills out and submits the TOPdesk request
  6. Logs the result and records that the client has been processed

Rules

A client is only processed if the data is complete and the client has not been handled previously. Care type and room are translated into TOPdesk values via mapping files. Every run follows the same logic and is logged for review, leaving no room for guesswork.

Frequently asked questions.

Do we need to change our system?

No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.

Who builds and maintains the automation?

Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.

Can we see what it did?

Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.

What happens if something goes wrong?

Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.

Can it work for our process, even if it differs from this example?

Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.

Process not found?

Don't see your process listed? Let us know. We'll start with an automation scan to see what can be automated.