For the team at the bedside

You will know when something needs a person.

Recordings land in a worklist you can act on, with the escalation state visible — so a critical trace is never sitting unread behind a screen nobody opened.

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

Request access How the pipeline works

What changes

What this means for nurses, 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.

A worklist, not a lookup

Unacknowledged findings that meet escalation thresholds are listed with their state and their target, so the question “has anyone looked at this?” has a visible answer.

Quality feedback at the moment of acquisition

The quality assessment is part of the study, not a later opinion. A trace that is inadequate for automated interpretation says so, which is what makes repeating it a decision rather than a suspicion.

You can always see the trace

The waveform is available to you on a calibrated grid, so you can describe what you are seeing to the clinician you are calling.

Nothing is hidden from you when an allowance is exhausted

If an account has no analyses left, the software declines to analyse a new study and says exactly that. It does not hide, alter or delete anything already recorded — knowing why new analyses stopped is clinical information, so every role that can read an ECG can see the notice.

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 result is somewhere you cannot see

A patient has chest pain now. Whether their ECG has been looked at is not a fact the bedside team usually has.

An acquisition that has to be repeated costs the patient

Lead placement, movement and electrical interference all produce a trace that cannot be interpreted. Nobody finds out until somebody reads it, which may be hours later.

A technician’s judgement is invisible in the record

The person who recorded the ECG often knows the trace is poor. That judgement rarely survives into the system that everyone else reads.

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.

Nurse

6 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.
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

Dashboard/dashboardCritical Alerts/alertsWaveform viewer/ecg

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 produce or sign an interpretation. The system records who acquired a recording and who interpreted it as separate facts.
You cannot override an automated finding. You can always read it and always see whether it has been reviewed.

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