Patchability
The designed-in ability to deploy security updates to a fielded medical device in a timely, controlled, and verifiable manner.
Definition
Patchability is the architectural and operational capacity to ship and apply security updates to a fielded medical device throughout its supported lifetime - including the update mechanism itself (signed packages, secure boot, rollback), the over-the-air or operator-driven delivery channel, and the regulatory pathway for the change. FDA's 2023 cybersecurity guidance treats patchability as a first-class security property, with a specific architecture view dedicated to updateability and patchability.What this means in practice
Devices designed without an update path become security debt the moment they ship. Mature MedTech teams design the update mechanism as part of the system architecture (cryptographic signing, A/B partitions, dual-bank firmware, secure boot, audit logging) and validate it in V&V - not as a post-launch project. Hospitals increasingly refuse to procure devices without a credible patching story.Examples
- A hospital IT department reviews a new infusion pump's technical documentation to confirm its ability to receive secure over-the-air firmware updates without requiring physical access to each device.
- During a pre-market submission, a MedTech manufacturer demonstrates to the FDA how their surgical robot's embedded operating system can be updated via signed software packages that prevent tampering and ensure authenticity.
- A device's design incorporates dual-bank firmware, allowing a security patch to be installed and verified on a secondary partition before being activated, providing a safe rollback option if issues arise.
- •Designing the device first and bolting on an update mechanism later - the architecture won't support it.
- •Shipping an update channel without cryptographic signing or rollback - a single compromised update can brick a fleet.
- •Confusing 'patchable' with 'auto-updating' - clinical environments often need controlled, scheduled updates.
Frequently asked questions
Cross-references
See also
Related terms
Grouped by themeEditor's picks
· Hand-selected related conceptsRemote, network-delivered software or firmware updates to a fielded medical device.
FDA's framework for ongoing vulnerability monitoring, risk assessment, and remediation of medical device cybersecurity issues after a device is on the market.
The bundle of cybersecurity artifacts a sponsor includes in a 510(k), De Novo, PMA, or HDE submission for a cyber device.
The federal statute that gives FDA explicit premarket authority over cybersecurity for cyber devices.
More in Cybersecurity
· Same categoryA chain-of-trust mechanism that ensures only cryptographically signed firmware and software can run on a device.
AAMI/ANSI standard establishing requirements for medical-device cybersecurity activities throughout the lifecycle.
AAMI Technical Information Report providing MedTech-specific guidance on cybersecurity risk management.
AAMI Technical Information Report on post-market security risk management for medical device manufacturers, the operational companion to TIR57.
Where this term appears across MedTech Terms.
Latest in MedTech
Sources
3 sourcesSources support the definition or relevant regulatory context, not necessarily every claim on this page. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.
- 1FDA Cybersecurity Guidance (Sept 2023)Tier 2 VerifiedFDAfda.gov
- 2Deciding When to Submit a 510(k) for a Software Change to an Existing DeviceTier 2 VerifiedFDAfda.gov
- 3HSCC - Health Sector Coordinating CouncilTier 4 VerifiedHSCChealthsectorcouncil.org
Inline markers like [1] jump to the matching reference above.