IEC TC62/SC62D/MT23 Report

SoftwareCPR’s partner Dr. Peter Rech convened the IEC TC62/SC62D/MT23 Infusion Pumps working group meeting held from April 22nd to 26th at the AAMI headquarters in Arlington, VA. The attendants included international experts and guests joining from governmental agencies, infusion pump manufacturers, test houses, and clinical research institutions.

Progress was made on a variety topics:

  • Pump classification will be simplified.
  • The requirements on the system configurations for delivery accuracy tests were clarified.
    It was decided that the “trumpet” curve and associated testing will be removed from the 3rd edition document.
  • Alarms information will be refactored after identifying issues with the existing documentation approach which requires alarms that may not be applicable to a specific pump.

The discussions around reliability and robustness started with a pareto of causes from the MAUDE (FDA Maude Database) basis. It must be noted that the current 60601 series of standards focuses on the evaluation and testing of basic safety and essential performance of medical devices. Reliability is not pursued in the current form. It was observed that the 60601 series of standards does not sufficiently define the expected stresses and constraints of general pump use environments. The series provides additional information limited to home health care (-1-11) and emergency transportation (-1-12) settings. The working group intends to establish requirements for general use environments and expected stresses within the scope of the standard.

Fruitful discussions occurred around secondary infusion. This type of infusion is broadly used across medical fields and supported or automated by some pumps today but lacking recognition in the -2-24 standard. Typically two infusion bags are used for this type of infusion and both bags are upstream of a single infusion pump. Various intricacies of secondary infusion could lead to under- or over-delivery. While it may be desirable to automate manual processes around the secondary infusion it is foreseeable that secondary infusion will continue to be used without such provisions. The working group intends to define basic safety requirements, a suitable test method, and requirements for disclosure.

Many infusion pumps offer remote interoperability today. Functionalities leveraging interoperability include dose error reduction, digital communication of prescription information to the pump, remote infusion monitoring and alarming, health record integration, pump firmware updates and others. While other standards and standardization activities may tackle various aspects of remote interaction and communication with the pump, an inspection of the standards revealed a lack of specificity to the infusion pump uses. The group intends to integrate a minimum consensus of basic safety and essential performance requirements around remote control into the -2-24 standard.

While work has started for the 60601 series 4th edition, the working group will continue to focus its efforts to the edition 3.2 of the 60601 series. The group received training during the meeting in ISO and IEC standard documentation practices.

An upcoming challenge to the group poses a new IEC policy which may require a reconstitution of the group in the future. It is not expected that this would have an impact on ongoing work.

To conclude this abbreviated summary I would like to thank all those experts, guests, and parties who made this face to face working group meeting possible and successful. I want to thank all of the participants for the open discussions and unbiased inputs. Thank you to AAMI for hosting us. Thank you to SoftwareCPR for supporting me in my role as convenor of the group.

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