Topic starter
06/11/2026 6:34 pm
TL;DR: Hospital records, backups and signed clinical data are exposed to a store-now, decrypt-later threat because today’s RSA and elliptic-curve cryptography may not protect long-lived health information for decades, according to Crayonic. The practical shift is toward cryptographic inventory, PQC migration planning and hybrid key exchange before confidentiality windows close.
Editorial analysis by NHI Mgmt Group, based on content published by Crayonic: “A patient record outlives its encryption: what post-quantum means for hospitals”.
By the numbers:
- England's NHS Records Management Code sets a minimum of 25 years for maternity records and 30 years from diagnosis for cancer records.
- The Global Risk Institute survey rates a cryptographically relevant quantum computer as quite possible, 28 to 49%, within ten years.
- Forescout found that only 31% of more than 5,500 internet-exposed healthcare systems supported TLS 1.3.
Key questions
Q: How should hospitals prioritise post-quantum migration for patient records?
A: Hospitals should prioritise patient records that must remain confidential for ten years or more, then move outward to systems that store or transmit those records.
Q: Why does long-lived medical data create quantum risk before quantum computers exist?
A: Long-lived medical data creates quantum risk because an attacker can capture encrypted records now and keep them until future quantum computers can break the public-key cryptography protecting them.
Q: Why do hybrid certificates matter during post-quantum migration?
A: They let classical and quantum-safe trust coexist while applications, devices, and partners move at different speeds.
Practitioner guidance
- Build a cryptographic inventory Map every place public-key cryptography is used, including TLS endpoints, VPNs, PKI, backups, archives, smart cards and device signing.
- Rank systems by data lifetime Prioritise any control that protects information needing confidentiality for ten years or more, because those assets face the most acute store-now, decrypt-later exposure.
- Add PQC requirements to procurement Require suppliers to state post-quantum roadmap dates, crypto-agility support and migration dependencies before new equipment is approved.
Bottom line: Hospital records create a quantum-era confidentiality problem because their retention periods are far longer than the life of current cryptographic assumptions.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Hospitals are dealing with a governance gap, not a distant science-fiction risk. The real failure mode is assuming confidentiality horizons match technology refresh cycles. In healthcare, retention rules routinely outlast cryptographic assumptions, so encryption strategy has to be judged against the life of the record, not the life of the server. That makes cryptographic inventory and migration planning an identity and access governance issue as much as a cryptography issue.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should teams do first when legacy devices cannot support post-quantum crypto?
A: Teams should first replace unsupported cryptography at the highest-risk boundary, usually by terminating traffic on a modern gateway or proxy that can run post-quantum or hybrid key exchange on behalf of the legacy device. If that is not possible, isolate the device, limit the data it handles, and wrap it with compensating controls such as segmentation and short-lived tunnels while planning replacement. The first step is to stop unsupported public-key use from persisting on exposed links.
👉 Read our full editorial: Post-quantum encryption is now a hospital records problem