Prucka Electrocardiographic amplifiers CardioLab

Prucka 30-June-99 Multi-channel electrocardiographic amplifiers, CardioLab EP System and CardioCath Catheterization Lab System software

2. Failure to establish and maintain procedures for validation of the device design, including software validation, and documentation of the validation, as required by 21 CFR 820.30(g). For example:

a. Standard operating procedures have not been established for software validation.

b. Review of the validation records for CardioLab Cath version 1.1 revealed:

i. The module entitled, “CO Worksheet” lacked complete documentation of testing in that the actual values under Section V. corresponding to the expected values of _____ [Hemoglobin] and _____ [02 capacity] were not documented.

ii. The module entitled “Measurements” does not identify test inputs and outputs.
c. Review of the validation records for CardioLab EP version 4.11 revealed:
i.The test record entitled, “Acquisition w/ Amps, HLT-CLAB II amp, 48 channels” under the Section entitled, “Testing sampling rates: _____ and _____ documented that surface ECG channels 4, 5 and 6 were not available which is contrary to expected results.

ii. The test record entitled, “Stimset/Detect-Clab II amps (32 channels)” documented various instances in which the actual values generated did not meet established specifications.

7. Failure to maintain complete device specifications, including software specifications in the Device Master Record, as required by 21 CFR 820.181(a).
For example:

a. Complete Device Master Records have not been established for the CardioLab EP, CardioLab Cath, or CardioMapp software systems which include software specifications.

b. The document entitled “CardioCath Specifications” is incomplete in that the following parameters are not identified:

i. A description of all files to be created/accessed as well as all reports and or visual displays to be generated.

ii. A description of all limits and parameters to be measured, the frequency of measurement, and the points at which the user is to be alerted and/or data is to be rejected.

iii. A description of all error messages, their cause, and the corrective actions required.

8. Failure of the Device Master Record to include or refer to the location of quality assurance procedures and specification including acceptance criteria, as required by 21 CFR 820.181(c). For example, standard operating procedures have not been established for software quality assurance and acceptance activities.

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.