ZorgDomein fallback referrals to HiX
Processes ZorgDomein fallback referrals by registering them in HiX and updating the TOPdesk ticket.
Overview
Fallback referrals from ZorgDomein arrive as TOPdesk tickets. This automation extracts the referral and patient details, searches for the patient in HiX, registers the information, sends the message in ZorgDomein, and closes the ticket—or assigns it with a clear error if anything is missing. It processes up to five records per run.
What has changed
- Less manual administration
- Exceptions are handled faster
- HiX and TOPdesk remain consistent, and staff know the outcome
At a glance
In één oogopslag
Overzicht
Fallback referrals from ZorgDomein arrive as TOPdesk tickets. This automation extracts the referral and patient details, searches for the patient in HiX, registers the information, sends the message in ZorgDomein, and closes the ticket—or assigns it with a clear error if anything is missing. It processes up to five records per run.
Wat er verandert
- Less manual administration
- Exceptions are handled faster
- HiX and TOPdesk remain consistent, and staff know the outcome
How it works.
What it does per fallback referral
- Opens the first fallback item in TOPdesk
- Extracts the referral and patient details
- Determines the search code based on the care information
- Searches for the patient in HiX using their BSN
- Registers the information in HiX and sends the message in ZorgDomein
- Updates the TOPdesk status or adds an error note and assigns the ticket
Rules
A single run processes up to five records. If the referrer or BSN is missing, the item is assigned with an error message; the search code is derived from the care information, with an escalation if none is found. 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.