Radionics Xknife Stereotactic Radiosurgery System

Radionics 22-March-99 Xknife Stereotactic Radiosurgery System

1. Failure to establish and maintain procedures to ensure that formal documented
reviews of the design results are planned and conducted at appropriate stages of the device’s design development, that appropriate representatives are included, and that the results of a design review, including identification of the design, the date, and the individual(s) performing the verification, are documented in the design history file as required by 21 CFR 820.30(e). For example:

a. Procedures were not established to ensure that formal and systematic design
reviews were conducted for the “Xknife 4” treatment planning software change.
While design reviews were allegedly conducted, the results of those reviews,
including identification of the design, the date, and individuals performing the
review were not documented.

b. There is no documentation to show that the results of in-house verification testing underwent a design review prior to transfer of the design to production.

2. Failure to establish and maintain procedures for the identification, documentation,
validation or where appropriate, verification, review and approval of design changes before their implementation as required by 21 CFR 820.30(i). For example:

The Design Control Changes Procedure, QS3-04-0006 Rev. A (approved 3/6/97)
lacks necessary detail in many areas:

a) It does not contain, nor does it cross reference to any other procedures regarding required verification, validation and reviews of design changes.

b) It implies that validation of design changes may be optional, but it does not
address any criteria whereby verification of design changes could be determined
sufficient in lieu of an otherwise mandatory validation requirement for design
changes.

c) It does not specify how design changes to be made to existing marketed
products/software are to be initiated, approved, documented and controlled.

3. Failure to establish and maintain design input procedures that ensure that design
requirements relating to the device are appropriate, address intended use of the
device, and the needs of the user and patient; failure to include a mechanism for
addressing incomplete, ambiguous, or conflicting design requirements, as required
by 21 CFR 820.30(c). For example:

Design input procedures were not established for the “Xknife 4” treatment planning
software change and there was no documented mechanism for addressing
incomplete, ambiguous, or conflicting design requirements.

4. Failure to establish and maintain procedures for validating the device design;
failure to document the results of the design validation, including identification of
the design, method(s), the date, and the individual(s) performing the validation in
the design history file, as required by 21 CFR 820.30(g). For example:
Procedures were not established for validating the “Xknife 4” treatment planning
software change.

5. Failure to establish and maintain procedures for verifying the device design, to
confirm that the design output meets the design input requirements, as required by
21 CFR 820.30(f). For example:

The results of testing show that the design/system requirements were not met for the Auto Contour/Contour procedures on page 5 and 8, the Jaws procedure on page 20, and the Autoplan procedure on page 22 of the test plan. There is no documented justification for accepting the design with these discrepancies left unresolved.

6. Failure to establish and maintain procedures to ensure that the device design is
correctly translated into production specifications as required by 21 CFR 820.30(h).
For example:

There was no established procedure for transferring the “Xknife 4” treatment
planning software to production.

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 offerings:

  • Americas: 11-13 February 2025
  • EU/Eastern Europe/Middle East/Africa/Atlantic/eastern South America: 18-20 February 2025
  • Southern Central Northeastern Pacific: 24-26 February 2025
Register using form at this link:     Agile Course Post Promo

 

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.