LLC iScreen

Recipient:iScreen, LLC
Product: Class II ophthalmic camera
Date: 10/2/2007

This inspection revealed your ophthalmic cameras are adulterated within the meaning of Section 501(h) of the Act [21 USC 351(h)], in the methods used in, or the facilities or controls used for, their manufacture, packing, storage, or installation are not in conformity with the Current Good Manufacturing Practice (CGMP) requirements of the Quality System (QS) regulation found at Title 21, Code of Federal Regulations, Part 820 (21 CFR 820). We received a response from you dated September 18, 2007, concerning our investigator’s observations noted on the Form FDA 483, List of Inspectional Observations, which was issued to you. We address this response below, in relation to each of the noted violations. These violations include, but are not limited to, the following:

1. You have not established or implemented written procedures for performing corrective and preventive actions (CAPA). In addition, your firm does not document or conduct CAPA activities such as trend analysis of sources of quality data, investigations of causes of nonconformities, or the actions needed to prevent recurrence of nonconforming product [21 CFR 820.100(a)].

For example: Your firm was aware the laptop computers and iScreen cameras eventually would have problems communicating with each other and made the decision to only upgrade the software for individual devices as customers began to experience problems with the devices. You performed corrective action following complaints but did not make an effort to prevent the same complaints for all customers prior to problems occurring.

2. You did not establish and maintain procedures for the identification, documentation, validation or, where appropriate, verification, review, and approval of design changes before their implementation [21 CFR 820.30(i)].

For example: You changed the software which controls the user interface program and digital and analog cameras for the iScreen ophthalmic camera to a new version, version and were unable to provide any documentation to show validation or verification procedures were conducted prior to installing the program into all of your systems.

3. Your device master records (DMR) failed to include or refer to the location of all installation, maintenance, servicing, packaging, labeling, process and quality assurance procedure specifications (21 CFR 820.181).

For example: The “Engineering Drawing of the Device” originally provided to the contract manufacturer of the ophthalmic camera did not include most of the required specifications, such as labeling and software changes.

FDA New Orleans 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.