New CDER Guidance on Platform Software

This new draft guidance explains when a Type V DMF may be used to submit information regarding a combination product for which the Center for Drug Evaluation and Research (CDER) has primary jurisdiction (i.e., CDER-led combination product) and the device portion has electronics and/or software that is planned to be used as a platform, that is, may be used in multiple CDER-led combination products.  The guidance also describes the administrative process and outlines the recommended content for these Type V DMF submissions and amendments.

Alternatively, applicants may also choose to incorporate by reference device constituent part information available in other submission types, such as a premarket notification submission (510(k)); premarket approval application (PMA); request for classification submitted under section 513(f)(2) of the Federal Food, Drug, and Cosmetic Act (FD&C Act) (De Novo request); or device master file (MAF).

The guidance gives these examples as possible applications:

  • Facilitate drug delivery in a manner that may include patient input or analysis (e.g., an electro-mechanically driven pen injector with software that allows input of patient or dosing information or that analyzes dosing or device use information).
  • Provide information that is used in making a decision regarding treatment, therapy, or drug delivery.
  • Interface with other devices or systems to provide patient use or other information to the user or health care provider (e.g., physiological parameters).
  • Control or drive the features of the user interface.

The guidance describes the necessary information for a Type V DMF submission and, as one would expect, “software information and documentation” is an expectation in the Technical Information section.  We would expect similar documentation as specified by CDRH in the Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices  (May 11, 2005).

Download the draft guidance: Type V DMFs for CDER-Led Combination Products Using Device Constituent Parts With Electronics or Software Guidance-2019

Need help with a combination product submission?  With Type V DMF strategy for a “software ecosystem” master file?  Contact us to discuss.

About the author

Brian is a biomedical software engineer - whatever that is! Started writing machine code for the Intel 8080 in 1983. Still enjoys designing and developing code. But probably enjoys his garden more now and watching plants grow ... and grandkids grow!

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.