Healthcare organizations can begin quantum planning by identifying information that needs lasting confidentiality and the systems that support safe care. Coordinate vendor migration planning with clinical operations, existing cybersecurity work, and a policy-specific insurance review.
Begin with care delivery and sensitive information
Our suggested starting exercise is to choose one clinical workflow and trace it from registration to follow-up. Identify where information is created, exchanged, stored, and recovered after an outage. Include the people who understand practical workarounds, not only the software inventory.
Then distinguish the period a record must be retained from the period its disclosure could cause harm. A retention rule does not by itself answer the confidentiality question. Clinical histories, research information, and records involving children may warrant careful discussion of long-term sensitivity without assuming every record has the same exposure.
Build on existing healthcare security work
HHS publishes voluntary Healthcare and Public Health Cybersecurity Performance Goals. These include practices addressing asset awareness, preparedness, and resilience. They are a useful planning reference; the voluntary goals are not themselves a substitute for applicable legal obligations.
Use existing governance meetings to add quantum-related questions instead of creating a disconnected project. Give privacy, clinical engineering, procurement, security, and leadership clear responsibilities. Current security work still needs attention while the organization learns more about cryptographic dependencies.
Ask suppliers for specific evidence
A broad statement that a product is “quantum ready” is insufficient for procurement. Ask which product version, communication path, authentication process, or stored-data protection the statement addresses. Request an explanation of customer actions, testing requirements, and remaining dependencies.
For systems involved in care, agree on testing and change management with qualified clinical and technical staff. Do not modify medical devices or unsupported components on the strength of a general article. A safe migration plan needs vendor-supported procedures, compatibility evidence, and a workable rollback strategy.
- Which interfaces depend on public-key cryptography?
- What support and replacement timelines apply to older equipment?
- Who validates interoperability with laboratories, pharmacies, and partners?
- What would remain exposed after the proposed upgrade?
Connect service outages to the insurance discussion
Prepare a hypothetical outage involving a scheduling, billing, hosting, or electronic-record provider. Describe what staff could still do, what would stop, and which expenses might increase. Ask the broker to explain how the proposed policy would evaluate those particular circumstances.
Discuss dependent business interruption, privacy response, restoration, regulatory response, and the relationship with other insurance. Do not assume a cyber policy automatically includes patient injury or all consequences of interrupted care. Ask where potential overlaps or gaps require specialist review.
Keep application answers precise
Travelers’ published healthcare and managed-care application supplement asks about topics including encryption of protected health information at rest and in transit. This is one insurer’s illustrative form, not a universal underwriting standard or proof of any organization’s compliance.
Have the responsible teams verify answers against the actual systems in scope. Explain exceptions accurately and use the insurer’s approved process to clarify ambiguity. Quantum migration plans should be identified as plans unless the relevant changes have been implemented and verified.
Make the first month achievable
Our recommended first deliverable is a short dependency map for one important workflow, an owner for quantum planning, and questions for the two suppliers most relevant to that workflow. Record what you know and what still needs investigation.
Bring the same map to the next insurance review. This creates a common reference for operational priorities and contractual questions. It does not certify security, establish regulatory compliance, or determine coverage; those assessments need the organization’s facts and qualified professional review.
- Connect long-term confidentiality with safe clinical operations.
- Request product-specific migration information from suppliers.
- Test realistic provider outages against the actual insurance wording.
Sources & further reading
- Voluntary Healthcare and Public Health Cybersecurity Performance GoalsUS Department of Health and Human Services · External source
- Migration to Post-Quantum CryptographyNIST NCCoE · External source
- Healthcare and Managed Care Supplement CYB-14303, Ed. 01-19 (illustrative form)Travelers · External source