Close client file
Close a client's file in ONS when care ends: claims, locations, documents, notes, care plans, and more.
Overview
When care ends, a client's file needs to be closed in many places within ONS: claims, locations, contacts, documents, notes, and the care plan. This automation runs through that entire sequence for every client on the list, verifies the result after each step, and emails any exceptions that require human attention. It can run as often as the organization needs, even multiple times a day.
What has changed
- Closing follows the same steps for every client
- Fewer incomplete closures
- Staff can see which cases require follow-up
At a glance
In één oogopslag
Overzicht
When care ends, a client's file needs to be closed in many places within ONS: claims, locations, contacts, documents, notes, and the care plan. This automation runs through that entire sequence for every client on the list, verifies the result after each step, and emails any exceptions that require human attention. It can run as often as the organization needs, even multiple times a day.
Wat er verandert
- Closing follows the same steps for every client
- Fewer incomplete closures
- Staff can see which cases require follow-up
How it works.
What it does per client
- Receives the client and end date from a list or via a webhook
- Checks if the client exists and is no longer receiving care
- Closes claims, locations, and addresses
- Removes personal contacts and professionals, and closes staff links
- Archives documents, medical notes, the care plan, and questionnaire results
- Logs every step and emails exceptions that require manual follow-up
Rules
A client is only closed if they are found and are no longer receiving care, and each closing step is verified before the next one begins. How long a client must be out of care varies by organization—two months in one instance and four weeks in another. Because the logic is fixed, the same input always produces the same result, and every run is logged.
Check out other automations.
Frequently asked questions.
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.
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.
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.
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.
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.