Tag

warningletter

Software Warning Letters

Cabrini Medical Center Blood Bank 2/8/96 14. Failure to maintain written standard operating procedures for the blood bank’s computer system that include: integration of the computer into daily operations; reverting to manual operations when the system is not functioning; control of changes in hardware and software; security procedures to prevent unauthorized access; and maintenance procedures...
Read More
McGHAN Medical Corporation 2/16/96 mammary prostheses The validation of the computerized dip timer system for software version [purged word] and [purged word] fails to assure that the previous files are overwritten when the maximum number of files [purged word] is reached. This is demonstrated by the fact that there was no verification of the file...
Read More
Ionetics 1/29/96 electrolyte analyzers 1. Failure to ensure specification changes are subject to controls as stringent as those applied to the original specifications of the device [21 CFR 820.100(a)(2)]. For example, your firm failed to document and approve changes made to components and software for your electrolyte analyzers.
Read More
1 8 9 10

SoftwareCPR Training Courses:

IEC 62304 and other Emerging Standards Impacting Medical Device Software

Being Agile & Yet Compliant

ISO 14971 SaMD Risk Management

Software Risk Management

Medical Device Cybersecurity

Software Verification

IEC 62366 Usability Process and Documentation

Or just email training@softwarecpr.com for more info.

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.