The National Commission reports. Where the estate meets it.

The National Commission into the Regulation of AI in Healthcare published its report today: 119 pages, 44 recommendations, hosted by the MHRA. None of it is law yet; a cross-government response follows. But the body that advises the regulator has now written down, with page numbers, what this estate has argued from the ward side since July.

Responsibility for safe use cannot sit with one actor. The report names the current arrangement a “liability sink”: the claim lands on the clinician with the clearest duty of care, and the system that put the tool in front of them at three in the morning goes unexamined.

That is the culture term. The estate’s thesis is that deployment risk is capability multiplied by culture, and that regulation has so far assessed only the first factor. Chapter 2 of the report is, in its own words, about the second.

Where the instruments sit

The report asks the health system for things it does not yet have instruments for. Read against the estate’s deployment sequence:

• REC 29Providers must self-assess their readiness to deploy a specific product. Gate and Screen do this before the decision, not after it.
• REC 26 · 28Manufacturers must state the conditions in the user environment that safe use depends on, and every risk control must be allocated before deployment. Specify and the Cultural Safety Case carry those conditions alongside the clinical safety case, where they can be allocated by contract.
• REC 17Performance drift must be escalated with no reportable incident required. Oversee and Measure watch for that drift, with the observable tells written down so a nurse can recognise them without a data scientist.
• REC 20The device and its version must be traceable in the patient record. Record — the Glass Ledger — is a hash-chained, fail-closed ledger built so the entry cannot quietly change after the fact.
• REC 33Staff must be trained on the specific tools they use, as a duty. After the Machine profiles how a clinician’s practice is actually changing around the tool, which is the honest version of that duty.

The report also names DCB0129 and DCB0160 as the mandated baseline and places them inside a wider readiness toolbox: necessary, not sufficient. That baseline was written for software that holds still. The NHS England consultation on revising both standards closes on 11 September; the estate’s response to it is filed separately.

What this entry is not

It is not a claim that the Commission read this estate. The mapping above runs one way: from a published recommendation to a published instrument that already answers it. That is the point of keeping the instruments open, versioned and citable — so that when the direction is written down, the tools are already on the table.

Sources