Checking the evidence behind a result

Every judgement shows its working

Open a record in the results and Rhazes shows what it found: the passage from the document, and the reasoning that took it from that passage to the status.

It highlights the source

You are not left comparing a quote against a document by eye. Rhazes finds the evidence in the record itself and highlights it, so you can read the surrounding text and see the context the quote came from.

Occasionally it cannot locate the passage in the document and will tell you so rather than pretending. That is worth investigating on its own.

What to check

• Does the evidence support the status? Read the quote against the standard as written.
• Is it from the right part of the record? A note covering several encounters can support a finding that belongs to a different one.
• Is it documented or inferred? A standard about documentation is only met by documentation. If the evidence is an inference that the thing probably happened, the honest answer is not met.
• For an exception, is the reason actually recorded? An exception resting on an assumption is a failure wearing a better label.

Check the ones that matter

Nobody has time to open every record on a large audit, and you do not have to. Concentrate on:

• Everything in the not-met column, because those are the findings you will be asked to justify.
• A sample of the exceptions, because that is where a generous reading inflates the result.
• A sample of the exclusions, because that is where a wrong inclusion criterion hides.

This is what makes the audit defensible

An audit stands or falls on whether the numbers survive being questioned. A percentage on its own does not survive it. A percentage where every record behind it can be opened and read does.