Correct diagnosis date
Identifies clients whose diagnosis date is after their first treatment contact and corrects them.
Overview
In some files, the DSM diagnosis date occurs after the first treatment contact. This automation identifies these clients, retrieves the first treatment date, and corrects the classification date with an evaluation note. It skips clients under 18 and non-editable statuses, and every result is logged and emailed.
What has changed
- Less manual correction
- Clinical and administrative data are aligned
- Reports become more reliable
At a glance
In één oogopslag
Overzicht
In some files, the DSM diagnosis date occurs after the first treatment contact. This automation identifies these clients, retrieves the first treatment date, and corrects the classification date with an evaluation note. It skips clients under 18 and non-editable statuses, and every result is logged and emailed.
Wat er verandert
- Less manual correction
- Clinical and administrative data are aligned
- Reports become more reliable
How it works.
What it does per client
- Downloads recent ZPM exports and extracts the client numbers
- Excludes clients under 18 and logs them as exceptions
- Searches for the first treatment date in the care records
- Opens the current DSM classification and checks the status
- Adjusts the classification date and adds an evaluation note
- Logs every result and emails the outcomes
Rules
Clients under 18 are excluded, and a diagnosis date is only adjusted if the classification status allows it. Everything else is logged as an exception. The same input always leads to the same outcome, and every run leaves behind a logbook that can be audited.
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.