What this estate does for you — and the doctrine underneath it: own, don’t rent.
The estate is a working set of clinical governance instruments for AI in health and care: hazard casework, oversight structures, a deployment sequence, and the safety arguments to defend them. All of it is open access under CC BY 4.0. Take it, adapt it, cite it, deploy against it. There is no licence fee and no registration wall. If you run a care service and you are being sold AI, these instruments exist so you can govern it on your own terms.
Most AI arrives in care settings as a subscription. The model lives on someone else’s infrastructure, under someone else’s terms, at a price that will change. When the vendor pivots, retires the product, or doubles the fee, your workflows — and the records inside them — are hostages. That is renting intelligence.
The sovereign approach is the alternative: the system runs on infrastructure you control, under governance you can inspect, at a cost you can predict. Independence is not nostalgia for server rooms. It is the position that the cognitive infrastructure of a care organisation belongs to the care organisation.
In the rented arrangement, the flow runs one way: your residents’ and patients’ information leaves the building and makes someone else’s product better. The sovereign arrangement inverts it. The model serves you and learns from your own data alone — inside your boundary, improving your system, never crossing into anyone else’s training set. Care data is among the most intimate data there is. The governance perimeter should sit around it, not behind it.
This is why sovereignty belongs on a governance estate and not a sales page. You cannot discharge clinical safety duties over a system you cannot inspect, cannot version-pin, and cannot switch off. You cannot promise continuity of care on infrastructure a third party can reprice or retire mid-contract. The clinical risk standards assume a manufacturer and a deploying organisation who can each answer for their system; ownership is what lets the deploying organisation answer honestly. It is what makes hazard logs, oversight, and audit mean something.
Read the framework and follow its deployment sequence. Work through the papers that apply to your service. And if you want to talk about what a sovereign deployment would look like for your organisation, write via the contact page — the reply comes from the author, not a pipeline.