Skip to content

Talk to a person

See it on a recording, with somebody who built it.

A walkthrough is a conversation rather than a slide deck. It runs through one study end to end on a demonstration dataset and stops wherever the questions are.
  1. 01

    A recording, from arrival to signature

    The whole path on one demonstration study: what arrives, what the quality engine decides about it, what the deterministic engine measures, and what a clinician then does with it. Nothing is skipped because it is unglamorous.

  2. 02

    The worklist, and how the order is decided

    Why a normal trace recorded at nine o’clock sits below a critical one recorded at nine-fifteen, and what your own escalation thresholds would do to that order.

  3. 03

    What happens when the signal is unusable

    A recording graded inadequate for automated interpretation, shown rather than described — because the difference between “normal” and “withheld” is the single most important thing this system has to get right.

  4. 04

    The parts that are missing

    No pager, SMS or email delivery; no automatic renewal; no invoices or refunds; no diagnostic accuracy figure anywhere. Each of those is reported as absent by the deployment’s own status endpoint, and you will be shown that endpoint.

  5. 05

    Your integration route

    How recordings would arrive from your machines and how signed reports would leave over FHIR R4 or HL7 v2.5 — including what is not implemented on either side today.

  6. 06

    Procurement, security and data handling

    Where patient data lives, what leaves the deployment and when, what the audit trail actually records, and what the validation register currently says — which, for this build, is that no clinical validation has been performed.

This software is not a medical device

A walkthrough shows a demonstration build. It has not been validated against a clinical dataset, it holds no regulatory clearance anywhere, and no diagnostic accuracy figure exists for it. Nothing you are shown is evidence of clinical performance, because no such evidence exists.

About the confirmation step

There is no one-time-code check on this deployment. The form records your work address and mobile number and a person reads them before arranging a time; a free mailbox is refused, so the organisation behind the request has to be real.

What this page will not show you

There are no customer logos and no testimonials on this site, because this build has no customers to name yet. Every proof point a clinical buyer needs — validation, clearance, a reference site — is either not yet established or stated plainly where it is missing. A wall of borrowed logos would make the rest of this page worth less.

Arrange a walkthrough

Tell us who you are and where you work. Sending this creates nothing: it records the request and confirms your two contact details, and somebody replies to arrange a time.

Your hospital, clinic, laboratory or practice domain. A code is sent here, so it has to be a mailbox you can open.

A code is sent here too. This is the number an urgent finding would reach you on later.

Optional. e.g. Consultant cardiologist, ECG technician, IT lead.

Optional.

Optional. What you read ECGs on today, how many a day, what you would want first.

Sending this form creates nothing: no account, no workspace and no password. The next step confirms your address and number, and a person reviews the request after that.

Would rather have a workspace to try it in? Request access — an approved request gets its own organisation, with the first analyses included.