Weekly outstanding results sweep
A scheduled Rhazes workflow that finds results nobody has actioned and files tasks to chase them, so nothing depends on being remembered.
Updated
The problem
Results come back after the encounter that generated them. The system that catches them is usually somebody remembering, and that fails quietly rather than loudly.
The steps
- Patient record, for the patients you are carrying.
- Sources, pointed at whatever your service says about acting on results.
- Ask Rhazes what is outstanding: requested and not returned, returned and not acted on.
- Branch on whether anything needs action, so a clean week produces a short answer rather than a long report you stop reading.
- Create tasks for what needs chasing, due when your service says it should be chased by.
- Output a summary of what it found.
Put it on a schedule
Weekly, at a time you will actually read it. A sweep that runs at 3am on Sunday and is read on Wednesday is a sweep that lost three days.
Check it is still running
A scheduled workflow failing quietly looks exactly like a scheduled workflow finding nothing. Open its recent runs occasionally and confirm they succeeded rather than assuming silence means all clear. See Following a Rhazes workflow run.
What this is not
It is a safety net, not a system of record. It supplements whatever your organisation already requires for results handling and does not replace it. Anything it finds still needs actioning through your normal process, and anything it misses is still your responsibility.