Panacea: Clinical Decision Support That Stays Inside the NHS Trust
Panacea runs against live patient records under the NHS DSP Toolkit without a single byte of special-category data crossing into a public-cloud AI boundary.
The boundary problem nobody talks about
Most clinical AI demos work beautifully on a stage and fall apart at the Trust gate. The reason is rarely the model. It is the boundary. The moment a tool needs patient data to be useful, that data has to leave the building, cross a public-cloud edge, and land inside an environment the Trust does not own, cannot inspect line by line, and cannot prove was never copied. Under the NHS Data Security and Protection Toolkit, UK GDPR special-category rules, and the long reach of the US CLOUD Act, that crossing is the whole risk. A Caldicott Guardian cannot reasonably sign it off, and an information governance lead is right to refuse it.
Panacea is built for the other answer. It is the clinical Studio module inside Mickai, the sovereign AI operating system. It runs against patient records where those records already live, inside the Trust's own walls, on-premises and air-gapped. No special-category data crosses into a public-cloud AI boundary because there is no crossing in the architecture. The model comes to the data. The data never goes to the model.
What Panacea actually does
Panacea is clinical decision support that a Trust owns and operates, not a service it rents through someone else's tenancy. It reads structured and unstructured patient data, surfaces relevant history, flags interactions and contraindications, drafts documentation for clinician review, and helps triage and prioritise workloads. Every one of those actions is a decision a clinician remains accountable for, and Panacea is designed around that accountability rather than around replacing it.
The difference from a public-cloud clinical assistant is not the output. It is where the work happens. Panacea executes inside the Trust network. Inference runs on hardware the Trust controls. The patient record is queried in place. Nothing is sent to an external API, nothing is logged to a vendor's servers, and nothing depends on a connection to the public internet to function. For a Trust running under the DSP Toolkit, that turns a conversation that usually ends in a refusal into one that can actually be approved.
Why on-premises and air-gapped is the only honest answer
The sovereign-AI thesis is simple. There is a large and growing class of organisations that legally cannot send their data to public-cloud AI, and healthcare sits at the centre of it. We size the wedge at roughly 0.85 million UK businesses, about 15 percent of the total, and around 5 million across the EU. The drivers are not preferences, they are obligations: NHS DSP Toolkit, UK GDPR special-category handling, PRA SS2/21 in finance, the EU AI Act high-risk classifications that cover clinical decision support, the NIS Regulations, and the extraterritorial pull of the US CLOUD Act over anything sitting in a US-headquartered cloud. Independent sizing of the sovereign-AI market runs from around USD 40 billion in 2025 to about USD 148 billion by 2032.
A Trust does not need a slide on any of that. It needs to know one thing: can this run without the data leaving. Panacea answers yes because Mickai was built air-gapped from the first line. This is not a public-cloud product with a private mode bolted on. The sovereign posture is the default, and the cloud connection is the thing that was never there to begin with.
The audit record is the trust mechanism
Clinical decision support carries a particular weight. If a tool influenced a decision about a patient, someone will eventually ask what it did, when, on what inputs, and on whose authority. Most AI systems cannot answer that with any rigour because their reasoning evaporates the moment the response is returned.
Every action Panacea takes is written to the Mickai Operational Audit Record, the OAR. The OAR is tamper-evident and post-quantum-signed, which means the log of what the AI did is itself cryptographically defensible and cannot be quietly edited after the fact. For a Trust that has to satisfy information governance, internal audit, and in the worst case a coroner or a regulator, that record is not paperwork. It is the mechanism that makes the AI auditable instead of merely plausible. The accountability that clinical governance demands becomes a property of the system rather than a promise from a vendor.
Built and live, with the IP to back it
Mickai is built and live, not a concept deck. Panacea is one of a family of Greek-named Studio modules that run on the same sovereign substrate: Nemesis for fraud and AML, Plutus for finance and FP&A, Tyche for underwriting, Prometheus for forecasting, Iris for customer service, Nomos for compliance, Astraea for legal, Pythia for business intelligence, and Aletheia for audit, alongside Trust Agent, the AMT, and Vinis voice. A Trust adopting Panacea is adopting a clinical front end onto an operating system that the wider organisation can extend into finance, compliance, and back-office work under the same boundary and the same audit record.
Underneath sits the moat. Mickai LTD holds 104 filed UK patent applications, roughly 2,340 claims, with Micky Irons as named inventor. These are filed rather than granted, which is the point: they establish priority and a prior-art position around sovereign, auditable, on-premises AI. As a dated third-party momentum signal, in June 2026 Micky Irons was ranked number 4 on the Crunchbase CB Rank for a person, verified live, with the Mickai company profile sitting in the top 1 to 2 percent globally. That is a snapshot of attention at a point in time, not a permanent claim, and we treat it as such.
Mickai is an ally, not a replacement
It is worth being clear on what this is not. Panacea is not positioned against the frontier labs, and Mickai is not an OpenAI killer. The public-cloud providers are extraordinary at what they do, and for the large majority of workloads they are the right answer. The dual-buyer thesis is that a different class of organisation exists, the regulated firm that cannot use those tools for its most sensitive data no matter how good they are, and that firm needs sovereign infrastructure to do AI at all. Panacea serves the buyer the public cloud structurally cannot reach. That is a complement to the broader AI ecosystem, not a war against it.
The opportunity to get involved early
Mickai is a UK company with manufacturing secured in Birmingham, and we are building to scale. As part of that, a pre-seed window is currently open to a selected group of partners who want to be involved early, while the IP position, the live product, and the regulated-market wedge are still ahead of the broad market understanding them. This is an invitation to the right partners, not a search born of need.
If you run information governance, clinical safety, or digital strategy inside a Trust and want to see Panacea run against records without anything leaving your walls, or if you are an investor who reads the sovereign-AI wedge the way we do, the door is open.
Micky Irons, founder and CEO of Mickai. Contact: micky@mickai.co.uk
Frequently asked questions
Does Panacea send patient data to a public cloud?
No. Panacea runs on-premises and air-gapped inside the Trust's own network. The model comes to the data, and the patient record is queried in place, so no special-category data crosses into a public-cloud AI boundary.
How does Panacea fit the NHS DSP Toolkit and UK GDPR?
Because nothing leaves the Trust's walls, the usual blocker under the DSP Toolkit and UK GDPR special-category rules is removed. Inference runs on hardware the Trust controls, with no external API calls and no dependence on the public internet.
How is what the AI did made auditable?
Every action Panacea takes is written to the Operational Audit Record (OAR), which is tamper-evident and post-quantum-signed. The log is cryptographically defensible and cannot be quietly edited after the fact, which satisfies information governance, internal audit, and regulators.
Is Panacea a finished product or a concept?
Built and live. Panacea is one of Mickai's Greek-named Studio modules running on the same sovereign substrate, and the wider organisation can extend the same operating system into finance, compliance, and back-office work under one boundary and one audit record.
Is Mickai competing with OpenAI or the major clouds?
No. Mickai is an ally, not a replacement. Public-cloud AI is the right answer for most workloads. Mickai serves the regulated buyer those tools structurally cannot reach, the firm that cannot send its most sensitive data to public-cloud AI at all.
What is the moat behind Mickai?
Mickai LTD holds 104 filed UK patent applications, roughly 2,340 claims, with Micky Irons as named inventor. They are filed rather than granted, establishing priority and a prior-art position around sovereign, auditable, on-premises AI. As a dated third-party signal, in June 2026 Micky Irons ranked number 4 on the Crunchbase CB Rank for a person.