Cath Copilot Book a demo

FAQ · Pilot

Cath Copilot: frequently asked questions

A local-first, chat-first desktop copilot for the cardiac catheterisation lab. Pre-case flags, a live in-room timeline, reconciliation, a cited procedure-note draft, handover, and audit, with every fact cited and every action confirmed by a person.

What Cath Copilot is

What is Cath Copilot?

Cath Copilot is a local-first desktop copilot for the cardiac catheterisation lab, made by Zapx Labs. It gives the team pre-case flags, a live in-room timeline, reconciliation, a cited procedure-note draft, handover and audit, with every fact cited to its source record and every action confirmed by a person. It is a prototype running on synthetic data only.

Who is Cath Copilot for?

Interventional cardiology teams: operators, cath lab nurses, cardiac physiologists, radiographers, coordinators and quality leads, plus the IT and information governance staff who would deploy it. Each role sees and can do different things.

Is Cath Copilot a medical device?

No. It is a prototype that is not a medical device, is not CE or UKCA marked and is not for clinical use. The design keeps to documentation, reconciliation and routing, and a regulatory assessment against UK medical device rules would come before any live use.

Does Cath Copilot make clinical decisions?

No. It recommends, drafts and routes; it never diagnoses, orders treatment or decides. Questions asking for clinical advice, such as whether to proceed or what dose to give, are declined, and pre-case flags come from deterministic local rules rather than AI.

Does it replace the physiological recording system, the EPR or PACS?

No. Cath Copilot reads from the systems the lab already uses and those systems remain the record; it is additive. Live haemodynamics are shown for information only, and monitoring and alarms stay on the clinical system.

Is Cath Copilot used in hospitals today?

No. It is a prototype shown with synthetic patients only and has not been deployed in, or assessed by, any hospital. It has no NHS approval.

Before, during and after a case

What does Cath Copilot do before a case?

It builds a pre-case brief with the source record on every field, and seven local rules flag gaps such as an unrecorded allergy status, a renal result that is old or missing, an anticoagulant with no documented last dose, unsigned consent or a missing weight. A person resolves each flag with a note, assigns it or escalates it. The rules are illustrative and would need local clinical governance approval.

What happens in the room during the case?

Events from the physiology system, PACS, device scanning and dictation arrive on a live timeline, and the team validates each one. The in-room screen has a dim theme for the darkened lab. Live haemodynamics from IEEE 11073 SDC monitors are display only, and a monitor is linked to a case only when the room and the patient ID match.

What happens when two systems disagree?

Reconciliation shows the two values side by side for devices, contrast, radiation and medications. A mismatch, such as 145 mL of contrast on the injector and 140 mL in the nursing record, must be confirmed by a person with a reason before the note can be signed, and the confirmation is audited. The confirmed value then feeds the note, the audit return and the handover.

Can Cath Copilot write the procedure note?

It drafts the note in the local template from validated events, either as a structured draft or with the local AI, and cites every statement. Findings and Plan are left to the operator. A claim check marks any sentence whose drug, dose, route or number is not in its cited source as unsupported, signing locks until it is fixed, and only the operator signs.

How does handover to CCU, recovery or the ward work?

When the patient leaves the room, Cath Copilot drafts a cited handover from the record, covering closure, anticoagulant, medicines held, the latest renal result, contrast, radiation and open items. The lab sends it and the receiving nurse acknowledges it on the shared record. It states facts and gaps only, never instructions.

Does it follow up results after the case?

Yes. Results the lab has flagged, recommendations in reports, results still awaited and doses above the local notification level become items with an owner, acknowledgement, escalation when overdue and a closed action. It never interprets a result.

Can I talk to it?

Yes. Push-to-talk speech is transcribed on the hospital's own machine and only fills the chat box, so the person reads it before sending and nothing runs by voice alone. The audio is discarded after transcription and the audit log records the clip length, never the words.

Stock, implants and recalls

How does Cath Copilot record the devices used in a case?

A USB barcode scanner reads the GS1 or HIBC code on the packaging, and the hub reads the product code, lot, expiry and serial and looks the product up in the site's item master. When a person confirms, the device is recorded on the case and appears in the note, the handover, the audit return and implant recall search. The raw code is kept alongside what was read.

What happens if a scanned device is out of date?

An expired device is flagged. It is still recorded if a person confirms it, because the record must show what was actually used.

Can it find every patient who received a recalled implant?

Yes. The operator or quality lead can search by lot or model across all cases, with every scan cited and the search itself audited. Filing the field safety notice turns every affected patient into an owned follow-up item.

Is Cath Copilot a cath lab inventory management system?

No. It records the devices used on each case; it does not manage stock levels or reordering. A Lab Operations module for utilisation, turnover and stock signals is planned but not built.

Audit and registry pre-fill

Does Cath Copilot fill in the national PCI audit?

It pre-fills an audit return from the record, with the source of every value, and a person confirms each field and code. The hub refuses to export until the note is signed and every required field is confirmed. In the prototype the dataset and codes are an illustrative subset, not mapped to the current national dataset.

Does it submit data to NICOR?

No. In the prototype the export writes to a local mock outbox, and only the quality lead can export. A real site would map Cath Copilot to its national audit dataset version and agree how submissions are made.

How are procedure codes suggested?

Codes are suggested by rules, each with the evidence behind it, and a person accepts or rejects every one. An optional local AI pass may only pick from the site's code table and is claim-checked like everything else.

Is there an audit trail?

Yes. An append-only, hash-chained audit log records every sign-in, failed sign-in, role switch, emergency access with its reason, action, export and device-link decision, and the chain can be verified at any time. AI prompts and replies are stored as hashes, not text.

Data, privacy and local AI

Where does patient data go?

Nowhere outside the hospital network. The hub runs on the same PC, on one lab PC shared with the room, or on a server run by hospital IT, and the AI model runs locally through Ollama. There is no cloud AI and no telemetry, models are installed from signed offline packs, and IT configures every connection explicitly.

Which AI model does Cath Copilot use?

A model running locally through Ollama; the demo uses llama3.1:8b. IT installs models from a signed offline pack, a model is used only after it passes qualification tests on the hospital's own hub, and cloud models are always refused.

How does it stop the AI making things up?

Every statement must cite a source record, and drafted notes are checked sentence by sentence against those records. A drug, dose, route or number that is not in the source makes the sentence unsupported and blocks signing. A changed model has to pass qualification again.

Who can see what?

Access is field-level across seven roles, so the same patient looks different to each: for example a nurse sees the planned access but not the full order, and site IT sees no patient data. Data a user may not see is labelled Restricted rather than silently left out, and the assistant sees only what the signed-in person can see.

How does emergency (break-glass) access work?

It needs a reason, is audited, and lasts only for that case for 30 minutes, after which it ends by itself and the ending is audited too.

Is the data encrypted and backed up?

Yes. The hub's database is encrypted at rest with SQLCipher (AES-256), with the key kept in a separate file. Checked, encrypted backups run every 24 hours, and a restore is checked, keeps the replaced data aside and is audited.

Deployment and IT

How would Cath Copilot run in a hospital?

It is a desktop app built for macOS and Windows (the Windows build has not been tested yet), with a hub that holds the shared record, access rules, audit log and local AI. The hub can run inside the app on one PC (Solo), on one lab PC shared with the others (Lab host), or on a hospital server that every app connects to (Connect), which is the recommended set-up for production.

Which systems can it connect to?

FHIR R4 servers with SMART Backend Services sign-in, DICOMweb PACS with DICOM C-ECHO, HL7 v2 feeds over MLLP including mutual TLS, IEEE 11073 SDC monitors and GS1 or HIBC barcode scanners. Each source can be switched between mock and live on its own, and the signed note can be written back to the EPR.

How do staff sign in?

With their organisation account through OpenID Connect (Microsoft Entra ID, AD FS or NHS CIS2), or their Windows username and password checked against Active Directory over LDAPS. Directory groups decide the role and no mapped group means no access. Passwords are never stored or logged, and sessions end after 30 minutes idle or 12 hours at most.

Does Cath Copilot control the x-ray system or the monitors?

No. From PACS it reads study metadata and dose values, never image pixels, and live monitor data is display only. It does not operate imaging or monitoring equipment.

Pilot and getting started

Can I see a demo?

Yes. Book a demo and we will run it with you on synthetic data, then talk through what a departmental pilot would need.

How much does Cath Copilot cost?

There is no public price. Book a demo to discuss a pilot.

What would a pilot involve?

Configuration rather than development: each source system is switched on separately, read-only first. Before any real patient data, a clinical safety and information governance process would come first.

What has to happen before Cath Copilot is used with real patients?

A clinical safety case and hazard log (DCB0129), the hospital's deployment assessment (DCB0160), a DPIA, a penetration test, code-signed installers and a regulatory assessment. Every local rule and threshold would also need clinical governance approval.

Watch Cath Copilot working, with a full transcript →

Cath Copilot is pilot-stage software shown on synthetic data. Cath Copilot is a prototype running on synthetic data only. It is not a medical device and is not for clinical use. It recommends, drafts, and routes; it never diagnoses, orders, or decides. A clinical safety and information-governance process precedes any use with real patient data.

See Cath Copilot on synthetic data

Cath Copilot is a pilot. Book a demo and we'll walk through it on synthetic data, then talk about what a pilot under your own governance would need.

Book a demo

Or email hi@zapxlabs.com.