04

Sep

2008

Mavidon Medical Products

0

Recipient: Mavidon Medical Products
Product:Class II Mavidon Medical Electrode Jelly.
Date: 8/8/2008

7. Failure to validate, according to an established protocol, computer software for its intended use, when that software is used as part of the Quality System or part of production as required by 21 CFR 820.70(i). The regulation under 21 CFR 820.70(i) requires that when computers or automated data processing systems are used as part of production or the quality system, the manufacturer shall validate computer software for its intended use according to an established protocol. All software changes shall be validated before approval and issuance. These validation activities and results shall be documented. Your firm implemented in 2007 a computer automated system for manufacturing and inventory control for raw material, however there is no validation of the software.

We have reviewed your response, dated June 24, 2008, and have concluded that it is inadequate because software validation should have been completed prior to manufacturing and release of your product. Your response to this observation is inadequate because it does not describe the specific steps that your firm will take at the present time to ensure compliance with the requirements of 21 CFR 820.70(i).

FDA Florida District Office

About the author

Amy Sellers

Amy enjoys researching and writing about developments in medical technology and how that intersects with US law. She received her J.D. from the University of Florida Levin College of Law in 2020 and now works as a Regulatory Associate for SoftwareCPR®, a general-purpose regulatory consulting firm that is recognized globally for their expertise with standards and national regulations pertaining to medical device, mobile medical app, and HealthIT software.

IEC 62304 and other emerging standards for Medical Device and HealthIT Software

Our flagship course for preparing regulatory, quality, engineering, operations, and others for the activities and documentation expected for IEC 62304 conformance and for FDA expectations. The goal is to educate on the intent and purpose so that the participants are able to make informed decisions in the future. Focus is not simply what the standard says, but what is meant and discuss examples and approaches one might implement to comply. Special deep discount pricing available to FDA attendees and other regulators.

3-days onsite with group exercises, quizzes, examples, Q&A.

Instructor: Brian Pate

Next public offering: TBD

Email training@softwarecpr.com to request a special pre-registration discount. Limited number of pre-registration coupons.

Registration Link:

TBD

Being Agile & Yet Compliant (Public or Private)

Our SoftwareCPR unique approach to incorporating agile and lean engineering to your medical device software process training course is now open for scheduling!

Agile principles that align well with medical
Backlog management
Agile risk management
Incremental and iterative software development lifecycle management
Frequent release management
And more!

2-days onsite (4 days virtual) with group exercises, quizzes, examples, Q&A.

Instructors: Mike Russell, Ron Baerg

Next public offering: March 7 & 28, 2024

Virtual via Zoom

Registration Link:

Medical Device Cybersecurity (Public or Private)

This course takes a deep dive into the US FDA expectations for cybersecurity activities in the product development process with central focus on the cybersecurity risk analysis process. Overall approach will be tied to relevant standards and FDA guidance documentation. The course will follow the ISO 14971:2019 framework for overall structure but utilize IEC 62304, IEC 81001-5-1, and AAMI TIR57 for specific details regarding cybersecurity planning, risk characterization, threat modeling, and control strategies.

2-days onsite with group exercises, quizzes, examples, Q&A.

Instructor: Dr Peter Rech, 2nd instructor (optional)

Next public offering: TBD