lnc Seryx

Recipient:Seryx, lnc
Product: Signature Genetics software program
Date:2/22/2007

This letter is in response to the Food and Drug Administration’s (FDA’s) review of your web site www.seryx.com, and the information you provided to The Office oft Vitro Diagnostic Devices (OIVD) in FDA’s Center for Devices and Radiological Health in a telephone conference on May 23, 2006 discussing the Signature Genetics software program. At the May 23, 2006 meeting, FDA suggested that Seryx prepare and send a Pre-Investigational Device Exemption submission as a way to begin a dialog to determine the best way to obtain 510(k) clearance or Premarket Approval for the Signature Genetics software program. Based on our review of your web site and information you provided to us, we have determined that Signature Genetics software is a “device” within the meaning of section. 201(h) of the Act (21 U.S.C. 321 (h)) which is currently being unlawfully marketed.

Seryx’s Signature Genetics system contains software used to analyze data and generate a patient-specific report via [redacted] interpretation of a patient’s genotype for several drug metabolizing enzymes. This software’s rules structure was developed by [redacted] A patient’s genotype test results for these drug metabolizing enzymes are entered into the Signature Genetics program and the software analyzes the laboratory results an other clinical parameters (e.g., drug allergies, concomitant medications) to generate a report, that includes recommendations to the health care provider about whether a patient’s, therapy should be adjusted and/or whether there are possible drug drug interactions. information by Seryx at the May 23, 2006 meeting states that the program is designed to “improve drug therapy.” Based on our review of your web site, you are currently marketing the Signature Genetics software program. The web site explains, for example, that “information provide in the report is intended to inform the physician if specific adjustments and considerations are indicated for patient based on the patient’s drug regimen and genotype results.”

Under section 201(h) of the Act. this software is a device 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 is intended to affect the structure or function of the body. The law requires that manufacturers of devices that are not exempt obtain marketing approval or clearance for their products from FDA before they may offer them for sale. This helps protect the public health by ensuring that new devices are shown to be both safe and effective or substantially equivalent to other devices already legally marketed in this country for which approval is not required.

Our records do not show that you obtained approval or marketing clearance before you began offering your product for sale. The kind of information you need to submit in order to obtain approval or clearance for your device is described on the Internet at http://www.fda.gov/cdrh/devadvice/3122.html. The FDA will evaluate the information you submit and decide whether your product may be legally marketed.

Because you do not have marketing approval or clearance from the FDA, marketing your product is a violation of the law. In legal terms, your product is adulterated under section 502(o) of the Act, 21 U.S.C. 352(o). Your product is misbranded under the Act because premarket notification under section 510(k) of the Act, 21 U.S.C. 360(section 510(k) premarket notification and FDA reviews it and notifies substantially equivalent to other legally marketed devices for which your product is adulterated under the Act because the law requires, an approved premarket approval application that shows your device is safe and effective. For a product requiring premarket approval, the notification required by section 510(k) of the Act is deemed satisfied when a premarket approval application (PMA) is pending 21 CFR 807.81(b).

You should take prompt action to correct these deviations. Failure to promptly correct these deviations may result in regulatory action being initiated by the Food and Drug Administration without further notice.

FDA District: 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:

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.