For pathologists and diagnostics centres

An ECG report before the patient leaves the building.

Run the ECG as part of the visit and have a measured, signed report in the record while the patient is still there — without a cardiologist sitting in the building to measure intervals.

Role in the system: DoctorHolds clinical authority

Request access How the pipeline works

What changes

What this means for pathology & diagnostics, 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.

Interpretation at the point of the visit

The recording is measured and graded as it is stored, so the report a pathologist signs is based on computed intervals rather than on counting small squares by eye.

Quality decided before the patient leaves

A trace that cannot be interpreted reliably is identified at acquisition, which is when repeating it costs a minute rather than an appointment.

Findings with their evidence attached

Severity, the measurement behind each finding and the engine version are on the report, so an external reader or a referring physician can follow the reasoning.

One queue for the whole centre

ECGs join the same worklist and the same audit trail as everything else the centre records, with alerts for the findings that need somebody immediately.

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.

The ECG is the one result that waits for a person

Chemistry, haematology and imaging have a workflow. The ECG goes to somebody to look at, and until they look at it the visit is not finished.

Sending it out costs days

Referring every trace to an external reader turns a same-visit result into a follow-up phone call, and the patient carries the uncertainty home.

Measured values with no measurement behind them

An ECG report that states a rate and an axis is only useful if the reader can see how those figures were arrived at and what the trace looked like.

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.

A diagnostics centre reporting ECGs alongside laboratory work is an ordering physician in this system: read the trace, review the automated findings, sign the report. The organisation’s administrator holds the facility role.

Doctor

10 permissions held

See patient demographics: Name, hospital number and encounter details, for patients in this facility.
See the study list and its metadata: Which recordings exist, when they were taken, and what state each is in.
View the waveform: The stored samples themselves, rendered on calibrated ECG paper.
Read interpretations: Measurements, findings and severity for a study, including anything a clinician has written.
Record a clinical review: State agreement or disagreement with the automated interpretation, with a note.
Sign an interpretation: Attach a named, digest-bound signature to the exact interpretation it covers.
Generate a narrative report: Produce the written summary, which describes validated findings and may not introduce new ones.
Transmit a signed study: Release a signed interpretation to another system over FHIR or HL7.
See critical alerts: The worklist of findings that need a person, and its acknowledgement state.
Acknowledge an alert: State that a person has seen it, so it is never left unattended.

Screens this role opens

ECG Queue/queueReports/reportsWaveform viewer/ecgCritical Alerts/alerts

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 the ECG and release it without a signature: an unsigned study is not transmissible, so a report in the record is always attributable to a person.
You cannot overrule the quality gate by signing harder — a withheld interpretation is recorded as withheld, and a manual read is recorded as a manual read.

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