Who has a live epidural, who needs following up, who is high risk — and the audited record behind every RCoA figure. Used one-handed on a phone on the labour ward at 3am, and at a desk for audit and governance.
Named after the Tuohy needle, the curved-tip needle behind every labour epidural.
The three jobs it does at once
Who has a live epidural, who is waiting, who has a follow-up overdue, and who carries an alert.
Auditable, exportable activity and complication data, with the denominator behind every rate.
Every clinician can export their own activity, without being handed anyone else's.
The desk is the same layout, widened. Every decision in the interface was judged against one question: does this survive a night shift?
At 3am you know who you are dealing with before you know what you are writing. Pick her from the worklist, pick what you did, and the form opens already attached to her open episode — no hospital number typed, no demographics re-entered. Procedures already recorded are ticked.
When a Trust connects its PAS, Tuohy reads the identity fields it needs live by hospital number; the confidential master record never leaves the hospital's servers. Every patient band says where its data came from and when. Address and phone number are never asked for, anywhere.
Every action is logged, and the log is a hash chain — the admin screen tells you whether any entry has been altered since it was written. Exports can be de-identified on the way out. Roles are enforced in both directions: a trainee cannot read a colleague's record, and a governance lead cannot edit a clinical one.
The handover view puts live epidurals, overdue follow-ups and high-risk alerts on one screen. Status is never colour alone — every chip and alert carries its word, so red–green deficiency loses nothing.
Every figure on the stats dashboard can be drilled into, down to the individual cases behind it, and the denominator for each rate is spelled out at the bottom of the screen rather than assumed.
If the PAS is unreachable, that is a warning strip and manual entry carries on. Recording never stops because an integration is down. Nothing the app renders is cached by the browser, so the next person on a shared ward computer cannot press Back into someone's record.
A private copy of the real application, yours for one day. Nothing you type in it reaches anybody else.
Your sandbox is ready.
Never put real patient data in the sandbox. It is a demonstration running on public infrastructure, not a clinical system, and it has not been through any Trust's information governance process. Every sandbox and everything in it is deleted after one day. Use the invented women.
Tuohy is a prototype built by a practising anaesthetist. It is not a Trust-commissioned project, and it is not holding anybody's data today.
The clinical screens, the roles, the audit chain, the exports, the RCoA reporting and the PAS lookup adapter are all built and tested. You can drive the whole thing in the sandbox above.
Consultant colleagues are being asked the only question that matters at this stage: is this how it actually works at 3am? That feedback is what the sandbox is for.
DCB0129 and DCB0160 clinical safety with a named Clinical Safety Officer and a hazard log; authentication beyond local passwords (the auth layer is structured for OpenID Connect); the Data Security and Protection Toolkit; and penetration testing. None of them are started.
That needs a completed DPIA, information governance approval and Trust-approved hosting inside the UK. Until all three exist, Tuohy runs on invented people only — including in the sandbox above.
