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

Partner and General Manager, Brian Pate is ISO 1385:2016 Lead Auditor certified for Medical Device Quality Management Systems (MD), and ISO 19011:2018 Management Systems Auditing (AU) and Leading Management Systems Audit Teams (TL). Brian started his medical device career in anesthesia clinical research in 1985 and has since worked both academia and industry including many years with Johnson & Johnson, Baxter Healthcare, and GE Medical. Brian’s roles have included software engineering, systems engineering, quality assurance, and regulatory affairs. Brian has served on multiple AAMI TIR working groups, including TIR32-2008 (Application of ISO 14971 Risk Management to Software; now IEC 80002-1) and TIR45-2012 (Guidance on the use of Agile practices in the development of medical device software) and served as a reviewer for the 2nd edition of TIR45. Brian serves on the AAMI Software Committee and as an AAMI instructor for the software, design controls, and agile methods courses. Brian also is a member of the Underwriters’ Laboratories (UL) Standards Technical Panel for UL1998 (Software in Programmable Components) and or UL5500 (Remote Software Updates).

SoftwareCPR Training Courses

ISO13485:2016 ISO 13485 Internal Audit(or) Training Course (Live, 3-day)

IEC 62304 and other Emerging Standards Impacting Medical Device Software (Live, 3-day)

Being Agile & Yet CompliantISO 14971 SaMD Risk Management

Software Risk Management

Medical Device Cybersecurity

Software Verification

IEC 62366 Usability Process and Documentation

Or just email training@softwarecpr.com for more info.

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.