Thalix Health

Clinical safety and assurance

Hazard log template for health IT, with worked examples

Short answer

A hazard log under DCB0129 or DCB0160 records each hazard a health IT system could pose to patients, its possible causes and existing controls, an initial risk rating, the additional controls (design, test, training, business process change), a residual risk rating, the actions and owners, and a status of open, transferred or closed. NHS England's implementation guidance gives a representative template and an example 5x5 risk matrix; neither is mandatory, and your clinical risk management plan sets the scheme you use.

Sources checked November 2026 · General information, not legal, regulatory or clinical safety advice

Illustration of the Thalix app store: installed, in-review and certified apps, and the review of a tier-2 app
App store — new boards, workflows and agents arrive as apps with a computed risk tier. A tier-2 app needs an app reviewer and the clinical safety officer; certified apps are signed and locked, and any install can be rolled back. Illustration with synthetic data.

The columns

The representative hazard log in the DCB implementation guidance reads from left to right like this:

ColumnWhat goes in it
Hazard numberA unique number
Hazard nameA short descriptive name
Hazard descriptionA short description of the hazard
Potential clinical impactThe effect in the care setting and on the patient
Possible causesTechnical, human error and so on; a hazard can have several
Existing controlsMeasures already in place that will stay in place
Initial riskSeverity, likelihood and the resulting risk rating
Additional controlsDesign, test, training and business process change
Residual riskSeverity, likelihood and rating once those controls are in place
ActionsA summary and an owner
Hazard statusOpen, transferred or closed

"Transferred" means the manufacturer has completed its actions but the deploying organisation hasn't completed its own yet. "Closed" means every action is done. Where a hazard has several causes, you can rate each cause and carry the most pessimistic rating up to the hazard.

The example risk matrix

The guidance offers five severity levels (minor, significant, considerable, major, catastrophic), five likelihood levels (very low, low, medium, high, very high) and this matrix, for illustration only:

LikelihoodMinorSignificantConsiderableMajorCatastrophic
Very high34455
High23345
Medium22334
Low12234
Very low11223

In its example acceptability scheme, 4 and 5 are unacceptable (hazards must be eliminated or controlled), 3 is undesirable (acceptable only if further reduction is impractical), 2 is acceptable where further reduction costs more than it gains, and 1 needs no further action. Because software faults are systematic, the guidance says likelihood is a judgement, and where it can't be quantified you should still list the hazard and use a reasonably pessimistic estimate. DTAC's form adds that no single scheme is mandated across the NHS, so manufacturers state theirs in the safety case report.

Three worked rows (illustrative only)

These rows are made up to show how the columns fit together for a hospital integration and workflow system. They aren't a real assessment; your own clinical safety officer and multidisciplinary group decide the hazards, ratings and controls.

HazardCauseInitialAdditional controlsResidualStatus
H1 Result shown against the wrong patientTwo identifiers wrongly linked to one patientMajor / medium = 3Design: identifiers only link on exact match; conflicts go to a person. Test: merge and conflict cases in the test pack.Major / very low = 2Open
H2 Bed shown as free while still occupiedCancel-discharge (A13) message not processedConsiderable / medium = 3Design: cancellations handled; unmapped messages held, not dropped. Business process: bed manager confirms before allocating.Considerable / low = 2Transferred
H3 Drafted discharge summary leaves out a medicine changeAI draft misses information in the recordConsiderable / medium = 3Design: draft can't be sent until a doctor signs it. Training: reviewers told drafts may be incomplete.Considerable / low = 2Open

Keeping it useful

  • Run hazard identification as a group: the guidance says it should include the clinical safety officer, clinical users from each affected area and IT, with the workshop recorded in the clinical risk management file.
  • Have the clinical safety officer approve every version, and issue a baselined copy with each safety case report.
  • Reopen it for every change: a new feed, model, ward or release.

What it does not mean

  • The matrix isn't national policy. The guidance gives it for illustration; your clinical risk management plan sets the criteria.
  • A template isn't a hazard log. The value is in the hazards your own group identifies and the evidence behind each control.
  • Low residual risk isn't closed. A hazard closes only when every action, including the hospital's, is done.

Where Thalix fits

The worked rows above lean on things Thalix actually does, which is why we chose them: identifiers link only when they match and conflicts are raised for a person instead of merged, ADT cancellations are mapped, messages that can't be mapped become dead letters with the raw message kept, and agent drafts wait for a named person to confirm. Those are design controls your hazard log could cite as evidence, with tests behind them. Thalix doesn't have a hazard log approved by a clinical safety officer for any hospital today.

Thalix is at pilot stage. Demos run on synthetic data, and a hospital deployment needs its own clinical safety case, information governance approval and security review. We don't claim any certification or assessment result the product doesn't have.

Thalix walkthrough video poster See Thalix workingA three-minute walkthrough on synthetic data: the console, agents, workflows and the audit trail →

Questions people ask

What columns should a hazard log have?

NHS England's representative template uses hazard number, name, description, potential clinical impact, possible causes, existing controls, initial risk (severity, likelihood, rating), additional controls (design, test, training, business process change), residual risk, actions and owner, and hazard status.

Is there a mandatory NHS risk matrix for hazard logs?

No. The DCB implementation guidance gives an example 5x5 matrix for illustration, and the DTAC form says no system for quantifying risk is specified for universal use in the NHS. Your clinical risk management plan defines the scheme.

What does a transferred hazard mean?

In the guidance's status scheme, transferred means the manufacturer has completed all its actions for the hazard but the deploying health organisation hasn't completed its own.

Sources

Each source below is an official page, read and checked in November 2026. Where a page and this guide differ, the official page wins.

General information only, written for hospital digital, IT, operations and clinical safety teams. It isn't legal, regulatory, information governance or clinical safety advice, and it doesn't replace your own organisation's processes or the official guidance linked above.

Thalix Health

See Thalix on a demo hospital.

A conversation with us is 45 minutes and free: the work you want to hand to agents, the systems involved, and where Thalix would and wouldn't fit. Demos run on synthetic patients.