Bemafon-Maico Inc.

Lack of written procedures to identify quality assurance problems reported in complaints and repair requests; failure of screening repair and serice requests to identify complaints; and failure of engineering change orders to include a record of software source code changes

3. Software revisions have been made without Engineering Change Order (ECO) control, resulting in the distribution of audiometers with unapproved software. ECOs do not include a record of software source code changes and obsolete versions are not archived [21 CFR Part 820.100 (a)(2)]. Software source code is not controlled under the document control system (21 CFR Part 820.80).

It should be noted that the items regarding software documentation and change, inadequate failure investigations; and identification of complaints when screening repair and service requests were cited on the form FDA-483, Inspectional Observations, that was issued at the close of the previous inspection of your firm on April 24, 1995. Your Engineering Manager, Scott Savre, participated in the discussions of the items on both the previous and current FDA-483s..

Your responses to the concerns referenced in the FDA-483 are noted and are being made part of the official file. The corrective actions that you are taking are appropriate for addressing most of the concerns raised during the April 1997 inspection. However, your response does not address the issue of lack of validation for changes that have already been made to the software (item #5 on the FDA-483). During the next inspection, we will assess the effectiveness of the implementation of the corrective measures that you reference in your letter.

It should be noted that the items regarding software documentation and change, inadequate failure investigations; and identification of complaints when screening repair and service requests were cited on the form FDA-483, Inspectional Observations, that was issued at the close of the previous inspection of your firm on April 24, 1995. Your Engineering Manager, Scott Savre, participated in the discussions of the items on both the previous and current FDA-483s.

About the author

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.

Cybersecurity Review

Our cybersecurity experts are NESSUS Pro Licensed and can quickly remediate cybersecurity deficiencies with your medical device or digital health software.  Planning, requirements, validation, and submissions – we can assist with all.

Interested in having a conversation?  Email us to arrange a Zoom meeting or call us at +1 781-721-2921.

office@softwarecpr.com

Corporate Office

15148 Springview St
Tampa, FL 33624
USA
+1-781-721-2921
Partners located in the US (CA, FL, MA, MN), Canada, and Italy.