05

Apr

2017

EU Medical Device Regulation

eu, regulatory, samd

0

The EU MDR of April, 5, 2017 is at the link below. Clause (19) states:

“It is necessary to clarify that software in its own right, when specifically intended by the manufacturer to be used for one or more of the medical purposes set out in the definition of a medical device, qualifies as a medical device, while software for general purposes, even when used in a healthcare setting, or software intended for life-style and well-being purposes is not a medical device. The qualification of software, either as a device or an accessory, is independent of the software’s location or the type of interconnection between the software and a device.”

Article 2 Definitions mentions software several times as well as interoperability.

Annex I General Safety and Performance mentions risk of negative interaction between software and IT environment and other requirements for software including mobile computing for security development life cycles risk management and V&V.

Annex VI UDI Clause 6.5 defines UDI requirements related to software including the requirement display of the UDI, when changes are made to the software, and how the UDI is displayed or placed on labeling.

Annex VII indicates software that drives or influences a device is classified the same as the medical device .Rule 11 sets classification requirements for standalone software (SaMD) Class I , IIa, II and III. This is different and not directly related to Safety classification in IEC 62304.

View the new regulation at https://eur-lex.europa.eu/legal-content/ENG/TXT/PDF/?uri=CELEX:32017R0745&from=EN

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:

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