Company: Tecan US
Product: Tecan Clinical Workstation and Tecan Genesis RSP
Date: 10/8/04

Failure to have complete validation of the _____ software program, as required by 21 CFR 820.30(g). Your firm did not have documentation of complete requirements specifications and software design specification for the entire _____ software program. Documentation of the software program provided by the original developer of the software was limited and did not show a complete validation of the software program. Additionally, validation of the software upgrades was limited to the changes or additions made to the software program by the upgrades. Validation has not been conducted on the entire _____ software program. Test cases only tested the software modifications with no references or linkage to an overall software program validation. (FDA 483 item #1)

Failure to establish and maintain procedures for implementing corrective and preventive actions, as required by 21 CFR 820.100(a)(4). Corrective and preventive actions have not been verified or validated to ensure that the action is effective and does not adversely affect the finished device. Specifically, your firm implemented two corrective actions in response to potential patient sample mismatches occurring with the use of the Tecan Clinical Workstation with _____ software. These corrective actions included a manual workaround for patient sample identification and new purging instructions. Your firm failed to verify or validate these corrective actions prior to implementation in the field. (FDA 483 item # 2 & 13)

Failure to establish and maintain procedures to control the design of the device in order to ensure that specified design requirements are met, as required by 21 CFR 820.30(a). There were no overall design procedures. Your firm did pot have any written design control procedures in place. Your firm did not have procedures for making or controlling software changes during the software development process. (FDA 483 item #3)

We acknowledge receipt of your letters dated May 28, 2004, June 14, 2004, June 29, 2004, July 26, 2004, and August 31, 2004 which were in response to the FDA 483. Your responses are currently being reviewed and will be addressed in a separate letter. We also acknowledge that you indicated in your June 29, 2004 letter that relevant software, engineering, manufacturing, integration and assembly personnel will be transferred to your sister facility, Tecan Systems, in San Jose, CA. You may refer to your responses in your answer to this Warning Letter. Please send your response to the attention of Serene N. Ackall, Compliance Officer at the address noted in the letterhead. If you have any questions about this letter, you can contact Serene Ackall at 404-253-1296.

FDA District: Atlanta District Office

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:

Being Agile & Yet Compliant (Public)

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

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

3 days virtual (Zoom) with group exercises, quizzes, examples, Q&A.

Lead Instructor: Mike Russell

Next public offering: Dec 3, 4, & 5, 2024 – 12:00 pm to 5:00 pm CET

Register Now


 

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

Call or email now to schedule a private, in-house class. The fall schedule is filling up!

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

Registration Link:

TBD

 


 

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.