Learn medical device software vocabulary for IT professionals: FDA 510(k) clearance, SaMD (Software as a Medical Device), FDA device classification, IEC 62304, and software update notification requirements.
0 / 5 completed
1 / 5
What is FDA 510(k) clearance for a medical device?
510(k) clearance is the most common FDA pathway for Class II medical devices. 'Substantially equivalent' means same intended use and same or different technological characteristics, but not raising new safety questions. Software-based medical devices (SaMD) frequently use 510(k) when a predicate exists. Engineers building medical software must understand this pathway affects design controls, documentation, and change management procedures.
2 / 5
What is SaMD (Software as a Medical Device)?
SaMD (defined by IMDRF) is software that runs on commercially available hardware — smartphones, tablets, cloud platforms — and is intended to diagnose, treat, monitor, or prevent disease. Examples include clinical decision support algorithms, AI diagnostic tools, and remote monitoring apps. As a SaMD, the software itself is the regulated medical device, triggering full FDA oversight including 510(k) or PMA, quality system requirements, and post-market surveillance.
3 / 5
When a device is described as 'Class II under FDA classification', what does this indicate?
FDA classifies medical devices into three classes: Class I (low risk, general controls, mostly exempt), Class II (moderate risk, general + special controls, typically 510(k)), Class III (high risk, requires PMA with clinical evidence). Most software-based medical devices that make clinical decisions land in Class II. The classification determines the regulatory pathway, design control requirements, and post-market obligations.
4 / 5
What does IEC 62304 govern in medical device software development?
IEC 62304 is the international standard defining software development lifecycle requirements for medical device software. It classifies software into safety classes (A, B, C based on potential harm if the software fails) and mandates corresponding levels of rigor — Class C software (patient death possible) requires the most stringent design, review, and testing documentation. FDA recognises IEC 62304 and expects manufacturers to comply with it in their Quality Management System.
5 / 5
A project manager says: 'The software update requires FDA notification.' Under what circumstances is this true?
FDA's guidance on software changes distinguishes routine maintenance (bug fixes, security patches that don't affect intended use) from changes that require a new submission. If a software update changes the intended use, modifies an algorithm affecting clinical output, or introduces new risks not covered by the original clearance, a new 510(k) or PMA supplement is required before distribution. Engineers must maintain a software change log and assess each change against FDA's decision-making algorithm.