Company: 3TP LLC.
Product: 3TP software
Date: 10/5/04

The Diagnostic Devices Branch (DDB), Office of Compliance (OC), Center for Devices and Radiological Health (CDRH), Food and Drug Administration (FDA) has reviewed your Internet website for 3TP Software. Based on our review of your website, it appears that your company is marketing 3TP Software for intended uses beyond the scope of your FDA clearance for the product.

3TP Software is a device as defined within the meaning of section 201(h) of the Federal Food, Drug, and Cosmetic Act (the Act) because it is intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease, or because it is intended to affect the structure or any function of the body.

FDA cleared 3TP Software for the following indications:

The 3TP Software Option is intended to be used as a post processing software package designed to provide a reliable means for visualizing the presence and pattern of contrast induced enhancement on MR datasets. 3TP supports the evaluation of dynamic MR data gathered during the injection of a bolus of contrast media. The resulting time course information can be displayed in a variety of formats, including a parametric image overlaid onto source MR images. In the hands of a trained physician the information provided by the 3TP Software Option could yield information that may assist in the interpretation of dynamic contrast enhanced studies.

Your website demonstrates that 3TP LLC is marketing the 3TP Software for intended uses that do not fall within the existing clearance. For instance, the website states that 3TP Software “facilitates rapid detection of breast cancer.”

“3TP is an innovative software solution that facilitates detection of breast cancer through rapid interpretation of contrast enhanced MRI images.”

Marketing the 3TP Software for indications beyond the scope of your FDA clearance violates the law. Specifically, the device is adulterated under section 501(f)(1)(B) of the Act because you do not have an approved Premarket Approval Application (PMA) to demonstrate that the device is safe and effective for the new intended uses for which you are marketing it. In addition, your device is misbranded under section 502(o) of the Act because you have not submitted a section 510(k) premarket notification to notify the agency of your intent to introduce the device into commercial distribution for these new intended uses. For a product requiring premarket approval, the notification required by section 510(k) of the Act is deemed satisfied when a PMA is pending before the FDA. [21 CFR 807.81(b).]

Issuer: Center for Devices and Radiological Health (CDRH)

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.