Closing medical coding
Close eligible diagnosis records for day admissions in HiX if they meet predefined rules.
Overview
Medical coders close diagnosis records for day admissions one by one. This automation opens unchecked day admissions in HiX, applies the closing rules, closes eligible diagnoses, and skips the rest with a reason. Each run provides totals and a shareable log.
What has changed
- Less repetitive work for coders
- Diagnoses are processed according to consistent rules
- Every adjustment and skipped record is traceable
At a glance
In één oogopslag
Overzicht
Medical coders close diagnosis records for day admissions one by one. This automation opens unchecked day admissions in HiX, applies the closing rules, closes eligible diagnoses, and skips the rest with a reason. Each run provides totals and a shareable log.
Wat er verandert
- Less repetitive work for coders
- Diagnoses are processed according to consistent rules
- Every adjustment and skipped record is traceable
How it works.
What it does per patient
- Opens the admission review screen in HiX
- Filters by closing date, 'unchecked' status, and day admissions
- Opens each patient and reads the diagnosis records
- Skips records that do not meet a rule, such as chronic ICD-10 codes from a reference file
- Populates the closing field with the closing date and verifies it
- Logs every adjustment and every skipped record with a reason
Rules
A diagnosis is only closed if it passes every rule. It is skipped if it is already closed, is not of the correct type, has a code on the chronic codes list, has flags already checked, or falls after a cutoff date. The same input always leads to the same outcome, and every run leaves a verifiable log.
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.