Weekly mutation documents
Identifies client changes in a weekly file and creates, uploads, and emails the registration and deregistration documents.
Overview
Every week, client changes arrive in a file, resulting in registration and deregistration documents. This automation checks for changes, fills in the templates, uploads them to the client file in ONS, and emails them after verifying that details such as the GP and pharmacy are present. If information is missing, the case manager receives a notification.
What has changed
- Less manual administration
- Client changes are handled consistently and on time
- Documents and logs are traceable
At a glance
In één oogopslag
Overzicht
Every week, client changes arrive in a file, resulting in registration and deregistration documents. This automation checks for changes, fills in the templates, uploads them to the client file in ONS, and emails them after verifying that details such as the GP and pharmacy are present. If information is missing, the case manager receives a notification.
Wat er verandert
- Less manual administration
- Client changes are handled consistently and on time
- Documents and logs are traceable
How it works.
the templates
What it does per client change
- Checks if the weekly file is in SharePoint
- Compares it with previous data to see what has changed
- Checks if mandatory information (such as GP and pharmacy) is present
- Fills in the registration and deregistration templates
- Uploads the documents to the client file in ONS
- Emails the documents and the log, and archives the files
Rules
The run only starts if the weekly file is present, and a checksum comparison with previous data determines if anything has changed. Documents are only created if mandatory information, such as the GP and pharmacy, is present; otherwise, the case manager receives a notification. Every run follows the same logic and is logged for review, leaving no room for guesswork.
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.