For the people accountable for the service

More ECGs read, by the same team.

Turn readings around faster without adding a reader, because the measuring and the sorting happen before anyone opens the trace. Your organisation is one workspace with its own users, thresholds and records — and the usage is visible on one screen.

Role in the system: Hospital AdministratorNo clinical authority — separation of duties

Request access How the pipeline works

What changes

What this means for hospitals & clinics, 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.

Capacity from the same headcount

Measurement is arithmetic, and it is now done by the engine. What is left for a human is judgement — which is the part that needed the training, and the part that gets faster with a severity-ordered worklist.

A view of the service, on your own numbers

Turnaround, throughput and worklist measures are on the analytics screen with their definitions attached, so a figure taken into a meeting can be explained in the same breath.

One workspace per organisation

Your users, recording devices, escalation thresholds and records belong to your organisation. Colleagues are invited by role, and someone who leaves is suspended rather than deleted — their acts stay in the record with their name on them.

Spend that is visible and does not surprise you

Usage is one unit per published interpretation, shown as a ledger of which studies were counted. A recording refused for quality costs nothing. A period is bought deliberately, one payment at a time, and nothing renews behind your back.

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 bottleneck is reading time, not recording capacity

A department can record more ECGs than it can interpret, so the queue grows and the delay lands on the report. Overtime is the usual answer, which is expensive and does not hold.

Nobody can say where the delay actually is

“Slow turnaround” is a symptom. Whether it is acquisition quality, reader availability or work arriving in the wrong order is usually a matter of opinion, and opinions do not survive a budget conversation.

Good recordings are repeated anyway

A repeat costs a technician, a room and a patient’s time. When a trace is only judged later, repeats happen for reasons that were knowable at the bedside.

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.

Hospital Administrator

20 permissions held

Administer the facility: Departments, facilities and their settings, inside this organisation only.
Manage users and roles: Invite staff, assign roles, suspend and disable accounts.
Configure integrations: Endpoints, credentials and the outbound interface configuration.
Read the governance register: Which algorithm versions exist and under what intended use.
Manage the governance register: Change the register. Separate from the clinical role that uses the engine.
Configure alert rules: Set the thresholds at which a study is escalated to a person.
Record validation evidence: State which algorithm versions have been validated, for what, by whom.
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.
Manage ECG devices: Register and configure the machines that produce recordings.
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.
Acquire and transmit a recording: Create a study from a device or an upload.
Clear labelled demonstration recordings: Remove synthetic studies and the records they were filed against, so a host can be returned to a clean clinical state. Real recordings are outside this permission.
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.
Read usage and purchases: What has been analysed, what it cost, and the ledger behind it.
Buy a period: Spend the organisation’s money on more allowance. Held by the hospital administrator.

Screens this role opens

Dashboard/dashboardAnalytics/analyticsBilling & Usage/billingSystem & Integration/systemAudit Log/audit

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 sign a clinical interpretation. Administrative authority and clinical authority are separate, so the person who configures the service is not the person who signs it off.
You cannot hide the usage ledger or rewrite the audit trail: both are append-only in the database, so your own record of what happened cannot be tidied up afterwards.
You cannot turn metering into a clinical limit. Running out of allowance stops new analyses and says so; nothing stored is hidden, altered or deleted.

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.

Cardiologists

Spend your hour on the ECGs that need you.

Read Radiologists

ECG reporting that fits between the other lists.

Read Doctors

An answer attached to the trace, at the point of care.

Read Nurses

You will know when something needs a person.

Read ECG Technicians

Record it once, properly, with the judgement written down.

Read Pathology & diagnostics

An ECG report before the patient leaves the building.

Read Audit & quality

Interrogate the record without being able to alter it.

Read

Regulatory position

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