For internal audit, quality and assurance

Interrogate the record without being able to alter it.

Read the trail of who did what, the operational measures and the algorithm register — with no ability to touch a clinical record, which is what makes your read independent.

Role in the system: AuditorNo clinical authority — separation of duties

Request access How the pipeline works

What changes

What this means for audit & quality, specifically.

Each item below corresponds to something in the build: a screen, a permission or a guard. Nothing here is a study result — this build has no clinical evidence base, and inventing one would be the worst possible way to sell it.

Read-only by construction

The audit role holds no permission that changes a clinical record. There is no configuration in which your access becomes an ability to act.

Access and acts, both attributable

Sign-ins, refusals, reviews, overrides and signatures are recorded against a named person and an organisation, so a sample can be traced rather than assumed.

Measures with their definitions attached

Operational analytics state what they count and what they exclude. No diagnostic accuracy figure is reported anywhere in this system, because none has been established for it.

A register of what the engine is

Which algorithm versions exist, under what intended use, validated by whom — readable without being writable.

What it removes

The arrangement this replaces.

Stated as problems rather than statistics, because they are the ones a reader recognises from their own week.

Assurance work needs read access, not power

An auditor who can change what they are auditing has no independent evidence. Most systems cannot grant one without the other.

Metrics that flatter are worse than none

A dashboard that reports turnaround without saying what it excludes cannot be used in a quality review.

The evidence is spread across conversations

Who reviewed what, who disagreed, and which version of the rules was in use are usually reconstructable only by asking the people involved.

Permissions held

What this role can do, read from the access-control table.

Generated from the same permission table the API enforces, so it describes access that exists rather than access that was described. If a permission is added to this role it appears here; if one is removed, it disappears.

Auditor

4 permissions held

Read the audit trail: The append-only, hash-chained record of who did what, and when.
Read operational analytics: Throughput, turnaround and worklist measures. Not a diagnostic accuracy figure.
See system health: Which components are configured and answering, and which are not.
Read the governance register: Which algorithm versions exist and under what intended use.

Screens this role opens

Audit Log/auditAnalytics/analyticsGovernance & Validation/governance

Navigation is filtered by permission rather than by role name, so a screen this role cannot open is rendered as a label explaining which permission it would need — rather than as a link that fails when it is clicked.

Separation of duties

What this role cannot do, and why that protects them.

Every access model is also a statement about accountability. These limits are the ones that make the audit trail worth having — and the ones that stop a signature meaning something it does not.

You cannot read patient-identifying data or clinical content. Audit access is deliberately scoped to the record of acts, not the records themselves.
You cannot alter or delete an entry: the trail is append-only through database triggers, so tampering is a gap that is detectable rather than a change that succeeds.

Read together with the full pipeline

The limits above are enforced by the same rules that govern the pipeline described in how it works, and the regulatory position — including what this build does not establish — is stated on safety & limits.

Other audiences

This is one seat in the room.

The system is designed around the fact that the person who records an ECG, the person who reads it and the person accountable for the service are three different people.

Hospitals & clinics

What this is not

This is a demonstration-grade clinical system. It is not a medical device, it holds no regulatory clearance anywhere, and it has not been validated against a clinical dataset.

It does not diagnose and it does not replace clinical assessment. Every interpretation is decision support for a qualified professional, who reviews, overrides and signs it — and the record shows which professional.

No sensitivity, specificity, agreement or accuracy figure appears on this site, because none has been established for this build. Any such figure would be invented. Read the full position.

See it on your own recordings.

Send a request, and a person reviews it. If it is approved you get a link that creates your own organisation, with the first 2 analysed studies included and no card details — and you are its administrator from the moment you set your password.

Request access Who it is for