Worked examples and prototypes.
The pieces below are demonstrations of how I work, built to make the approach concrete. They are not commercial products and not for sale. If one is close to what you need, the real version gets built with you, for your context.
Hazard catalogue
A structured library of reusable clinical safety hazards and standard controls, organised by what a system actually does. It shows how I break a system down, surface the hazards that apply, and tie each one to a control and a clear risk rationale.
See the catalogueWhat it demonstrates
- ✓ Hazards organised by system capability rather than by abstract risk type
- ✓ Each hazard carries causes, clinical impact, suggested scoring, and a standard control
- ✓ Standard NHS 5x5 risk matrix and ALARP-based acceptability
- ✓ A reusable starting point a Clinical Safety Officer can adapt, rather than a blank page
Clinical pathway template
An acute heart failure pathway taken from national guidance down to the level an EHR team would actually configure. It demonstrates the translation step that usually gets missed: from what the guideline says to what the system needs to do.
See the exampleWhat it demonstrates
- ✓ National guidance (NICE, ESC, GIRFT) mapped to configurable elements
- ✓ Coded data, order sets, and decision support specified at build level
- ✓ Vendor-agnostic, using SNOMED CT and standard terminologies
- ✓ Each decision point traced back to its source evidence
CSO hazard-log builder
An early concept for turning the hazard catalogue into a tool that helps draft a hazard log: describe a system, surface the hazards that apply, and assemble a first draft for a Clinical Safety Officer to review and own.
Talk to me about itAn honest note
This is a concept I am developing, not a product you can buy. It is not built, deployed, tested, or clinically assured, and nothing here should be used to make safety decisions about a real system.
A tool that touches clinical safety has to be held to the same standard as the systems it documents. I would rather show the thinking honestly than dress up a prototype as something it is not. If the idea is useful to you, I am happy to talk it through.
Want the real version, for your system?
These examples show the approach. The actual work gets built with you, around what you are deploying and the context you are deploying it into.
Get in Touch