Open Hazard Log by Bioterafi Get started

A hazard log that keeps up with your product. Agents find and trace hazards as your code changes. Your Clinical Safety Officer decides what goes in.

Open Hazard Log keeps a DCB0129 hazard log current between releases. It proposes hazards from your specs and code, with every source quoted. It checks whether the evidence behind each control still holds. It never changes the log without a named clinician's approval.

Open source under Apache-2.0. Runs on your own computer. No patient data.

Ward Results Viewer 2.3Working draft · v3 issued 12 SepAudit chain intactIssue version
Hazards
14
Residual risk 3 or more
2
Controls verified
23 of 37
Proposals waiting
3

Residual risk

Very high
High
Medium11
Low2431
Very low2
P-031 · New hazard · proposed by the scan
Children's results compared with adult reference ranges
Cause: range table holds adult values only
Control (design): age-banded reference ranges
"…for reviewing results for all inpatients across the Trust."
docs/intended-use.md:3 quote found
Severity…Likelihood…Approve

Illustration with made-up sample data. The CSO rates a new hazard before the agent's suggestion is shown.

The problem

Hazard logs are meant to live as long as the product. Most are written for go-live and then drift.

They go stale

Code, configuration and workflows change every release. The spreadsheet doesn't, and a control can quietly lose the test or document it relied on.

Links live in free text

Hazard, cause, control and evidence sit in spreadsheet cells, so nobody can check them automatically.

Hand-overs get lost

Hazards a manufacturer passes to a deploying organisation travel by email and PDF, and the actions they need are easy to miss.

How it works

Agents propose. The Clinical Safety Officer decides.

The rule is enforced in code, not policy: the agent and the checks can only write proposals. Only a CSO's decision changes the log.

01

Scan

An agent reads your intended use, specs and chosen code. It looks at clinical workflows, failure modes, AI-specific risks and human factors, then proposes hazards with quoted sources.

02

Review

The CSO rates each new hazard before seeing the agent's rating, then approves, edits or rejects it with a reason. Rejections teach the next scan.

03

Track

Every change is signed by a named person in a hash-chained audit trail. Checks flag evidence that changed or disappeared, and code changes that touch a hazard.

04

Issue

The CSO issues numbered, frozen versions of the log. Each exports in the NHS hazard log template layout, with a list of actions for the deploying organisation.

Safety by design

A safety tool should be held to the standard it supports.

Open Hazard Log keeps its own hazard log, and these guardrails are its controls. They aren't promises; each is checked by the test suite.

  • No write path for agentsThe scan can only store proposals. A test fails if any code that writes to the log appears in it.
  • Every quote is checkedA citation must appear word for word in its source. If none can be found, the proposal is hidden from review.
  • Blind ratingThe agent's suggested rating stays hidden until the CSO has entered their own, so it can't anchor them.
  • Tamper-evident historyThe audit trail is append-only and hash-chained. One command finds the first altered entry.
  • Documents are data, not instructionsSource text is passed to the model as data it's told never to obey, and output must match a strict schema.
  • No patient data, on your machineScans read docs and code only, after the CSO confirms there's no patient-identifiable data. The app listens only on your own computer.

NHS clinical risk management standards

Built around DCB0129 and DCB0160.

Each feature maps to a clause of the standards. Your Clinical Risk Management System, Plan and Safety Case Report stay yours. Open Hazard Log holds the hazard log and its evidence.

ClauseThe standard asksOpen Hazard Log
DCB0129 3.3.1Establish and maintain a hazard logA living log with structured hazards, causes, controls and evidence
DCB0129 3.3.2A CSO approves each version of the hazard logIssue version: a signed, numbered, frozen snapshot
DCB0129 4.3.1Identify known and foreseeable hazardsThe scan proposes candidates; the CSO decides
DCB0129 4.4.1, 5.1.1Estimate and evaluate risk against the Plan's criteriaRisk derived from your matrix; only the CSO sets ratings
DCB0129 6.3.1–6.3.3Implement and verify controlsEvidence linked to each control, re-checked by hash
DCB0129 7.3.4Keep an audit trail of all versionsHash-chained event log; issued versions record the commit
DCB0160 2.5.1Deployers use the manufacturer's safety materialDeployer-actions export for the local DCB0160 log

Based on the current 2018 versions (DCB0129 Amd 24/2018, DCB0160 Amd 25/2018). NHS England's review of both standards closed its consultation in September 2026. The risk matrix and template columns are configuration, so they can follow the revision. Open Hazard Log supports your clinical risk management. It doesn't make a product compliant, and it isn't affiliated with or endorsed by NHS England.

Get started

Run it yourself.

Open Hazard Log is open source under the Apache-2.0 licence. The source code is being prepared for release on GitHub.

Once it's out, the demo builds a made-up results viewer with an imported hazard log, a replayed scan and some simulated code changes. You can review proposals without an API key, then point it at your own product.

# set up and build the demo
uv sync
./scripts/demo.sh

# open the dashboard
uv run ohl --db demo.db serve --as cso@demo.local

# your own product
uv run ohl init
uv run ohl user add you@trust.nhs.uk --role cso \
  --name "Your Name" --registration "GMC 1234567"
uv run ohl system add "Your product" --as you@trust.nhs.uk
uv run ohl import hazard-log.xlsx --system 1 \
  --as you@trust.nhs.uk