Updateability is part of the device design
Connected medical devices need a controlled approach to software maintenance. Cybersecurity fixes, compatibility changes, and model revisions may have different implications, but each needs appropriate authorization and verification. FDA’s cybersecurity guidance addresses design, labeling, and supporting documentation for devices with cybersecurity risk. A product described as connected should therefore have a credible maintenance plan. An update feature is not complete simply because a server can send a new file to the device.
Verify origin, compatibility, and execution
Define how the device recognizes an authorized update and rejects unsuitable or altered packages. Record compatible hardware, software, and model combinations. Test how the update process handles interruption, insufficient resources, or a failed verification step. Specific implementation and recovery choices depend on the device’s requirements. Use qualified engineering review rather than a generic promise of seamless maintenance. The aim is to preserve the intended function and prevent unsupported states, not to eliminate every visible maintenance step.
Coordinate with the operating organization
Manufacturers and device operators need an agreed process for notification, deployment timing, exceptions, and incident escalation. A hospital may have operational constraints that affect a maintenance window. Conversely, postponing an important security fix indefinitely can introduce risk. Provide enough information for the responsible teams to assess the change and carry out their roles. Keep records of update status so unsupported or partially updated equipment can be identified rather than assumed to match the current fleet configuration.
Distinguish maintenance from functional expansion
A security patch and an AI feature change should not be described as equivalent merely because both arrive electronically. Consider the applicable verification and regulatory obligations for the specific modification. FDA’s PCCP guidance can be relevant to certain planned AI-device updates within its authorized scope. Future wireless connectivity may simplify distribution in some settings, but it does not replace change control. Sustainable device support combines trustworthy delivery, product-specific evidence, and clear responsibility when an update does not proceed as intended.