This webinar will evaluate two recently published U.S. FDA Guidance Documents on device changes: 1) “Deciding When to Submit a 510(k) for a Change to an Existing Device Final Guidance for Industry and FDA Staff”; and 2) “Deciding When to Submit a 510(k) for a Software Change to an Existing Device Final Guidance for Industry and FDA Staff”; both published October 25, 2017. Such changes pertain to change to a medical device that a company currently has in commercial distribution or is reintroducing into commercial distribution.Such a device is about to be significantly changed or modified in design, components, method of manufacture, or intended use.Significant changes or modifications that require a premarket notification are: 1) A change or modification in the device that could significantly affect the safety or effectiveness of the device, e.g., a significant change or modification in design, material, chemical composition, energy source, or manufacturing process; 2) A major change or modification in the intended use of the device.The guidances’ also address when a series of less significant changes, evaluated collectively, trigger such premarket notification ( a new 510(k)).Methods to control, track, evaluate and document the change evaluation process. The importance of design control / change control in this process.

The Device CGMPs require (21 CFR 820.30(i) Design changes) that each manufacturer “shall establish and maintain procedures for the identification, documentation, validation or where appropriate verification, review, and approval of design changes before their implementation.” How can this be done?  Systems / documentation  required? What device and/or software changes trigger the requirement to file a new 510(k)? Analysis of the two U.S. FDA Guidance Documents on device and doftware dhanges to determine regulatory expectations. What single changes trigger such action? When a collective series of smaller changes trigger such action?