American Blood Resources Association

Company: American Blood Resources Association
Date: 7/31/01
Product: Blood Bank Deferral Software

During an inspection of your facility located in Annapolis, Maryland, on June 18 through 22, 2001, Food and Drug Administration (FDA) investigators determined that you manufacture and distribute, Blood Bank Deferral Software. This software is a device within the meaning of section 201(h) of the Federal Food, Drug and Cosmetic Act (the Act). The device is considered adulterated within the meaning of section 501(h) of the Act, in that the methods used in, or the facilities or controls used in the manufacture, processing, packaging, storage, or distribution of this software are not in conformance with the Quality System Regulation for Medical Devices, as specified in Title 21, Code of Federal Regulations (CFR), Part 820, as follows:

Failure to document and validate design changes in that the National Donor Deferral Registry (NDDR) software was changed with regard to year 2000 update, modification of program files _____ and _____, without documenting the design changes, testing, validation, and verification as required by standard operating procedures (SOPs)(21 CFR 820.30(i)).

Failure to maintain a complete Device Master Record (DMR). For example, the DMR lacked complete specifications for software installed on the host server and deferral record activity codes (21 CFR 820.181).

Failure to establish and maintain adequate document change controls in that the business practice was changed regarding the use of computer generated _____ as opposed to the use of _____ numbers, for donor identification. The NDDR user manuals and design specifications were not changed to reflect this new practice. Also, approval of standard operating procedures was not documented in that the procedures lacked signatures of the individuals approving the documents and/or dates of approval. For example, SOP 33.003, “User Record Maintenance” and SOP 33.004, “Monthly Activity Report,” were not signed as being approved (21 CFR 820.40(b)).

Failure to conduct and document quality audits to assure the quality system is in compliance with quality system requirements (21 CFR 820.22) and to document the evaluation of contractors (21 CFR 820.50(a)). For example, there was no documentation available to show that either internal quality audits or an evaluation of the contract software developer had ever been performed.

FDA District: Baltimore

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.

SoftwareCPR Training Courses:

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:

Register Now

 


 

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

Corporate Office

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