What clinical audit in Rhazes does
Rhazes reads a set of clinical records against standards you define and reports compliance, with quoted evidence for every judgement.
Updated
The idea
You define the standards. Rhazes reads every record against every standard and tells you which met it, which did not, which were never in scope, and which had a valid reason not to comply.
Every judgement comes with the quote from the record that produced it. That is the part that matters. An audit result you cannot trace back to a line in a note is a number nobody can defend at a meeting.
What it replaces
The part of audit that is genuinely awful: sitting with a stack of notes and a proforma, reading each one against each criterion, and tallying. That work is mechanical, it takes days, and it is where the errors come from because attention degrades long before the pile does.
Rhazes does not replace designing the audit or interpreting the result. Those are the parts that need a clinician, and they are the parts worth your time.
How an audit is put together
Four things, built in that order:
- A purpose. What this audit is for, in your own words.
- Standards. The criteria each record is judged against, each with its own inclusion criteria, optional exceptions and a target.
- Records. The notes, letters and documents to audit.
- The run. Rhazes reads each record, decides a status per standard, and quotes its evidence.
See Starting an audit.
What comes out
- A status per record per standard: met, not met, exception, or excluded.
- A compliance percentage per standard, against the target you set.
- The evidence behind every one of those decisions.
- A downloadable report once the run finishes.
Availability
Auditing is an enterprise capability and is not switched on for every account. If you cannot see Audits, it has not been enabled for yours. Talk to us about turning it on.