Storage Custody Sovereignty
100%
Data persists in public UK GovCloud
Theft & Resale Threat
0%
Non-custodial enterprise license
Semantic Lock-In Friction
46 / 100
Ontology requires dbt translation
Estimated Migration Effort
8 Months
14 Person-Months across engineering
Interactive Multi-Tier Architecture Blueprint
Mode: Operational State
Decommission Active: Palantir Foundry middleware severed. Sovereign data lake remains intact with 100% data retention. Migration bridges activated.
Sovereign Public Storage (UK Controlled)
Commercial Semantic Middleware (Palantir)
Target Replacement Bridge
Operational End-User Applications
Technical Fear vs. Architectural Reality
| Public Allegation | Technical Reality | Verdict |
|---|---|---|
| "Vendor steals & sells NHS records" | Palantir operates strictly as a data processor / non-custodial software layer; UK Gov holds physical encryption keys. | Misconception (0% Risk) |
| "Data is trapped in proprietary silo" | Underlying lake uses standard Parquet / Iceberg formats queryable via ANSI SQL / Trino without Palantir. | Open Standard (100% Sovereign) |
| "Ontology logic creates lock-in" | Object links, writeback actions, and derived event pipelines require schema mapping to dbt / SQL semantic models on exit. | Real Risk (Medium Friction) |
| "Front-end clinical apps become sticky" | User interfaces (e.g. Bed Management) are tightly coupled to Workshop workflows; requires frontend UI rewrites. | Real Risk (High Migration Effort) |
5-Step Sovereign Exit & Decommission Plan
-
1. Open Table Format Enforcement: Ensure all Foundry transforms write back to sovereign Apache Iceberg or Delta Lake tables in NHS-owned AWS S3/Azure storage.
-
2. Parallel dbt Semantic Extraction: Mirror dynamic ontology definitions (Patients, Beds, Pathways) into open dbt-core semantic YAML schemas.
-
3. Action & Audit Writeback Capture: Maintain dual-write event streams for transactional workflow mutations to an independent PostgreSQL / Kafka sink.
-
4. Open UI Replacement Layer: Stage bespoke NHS design-system React frontends connected directly to the open semantic APIs.
-
5. Revocation of Vendor Tokens: Decommission Foundry runtime compute instances without losing a single historical record or relational mapping.