Product requirements vs Software requirements

One of the difficult challenges with product development for medical device and HealthIT manufacturers is to properly delineate the design requirements – what is product level versus what is design level.  There are many reasons to get this right because if one doesn’t the impact could cause significant delays in development at least and inadequate testing or even recalls at worst.

Often what is clearly a very detailed software requirement is treated like 21CFR820.30(c) Design Input – which leads to the likelihood that many unnecessary activities may be triggered when that software requirement changes.  Furthermore, very often the product level requirements are absent or poorly written to capture the “real” design input – the intended use and medical claims of the device.

IEC 62304 and IEC 82304 can be helpful in sorting this out.  Additionally, we created this job aid which compares the IEC 62304 and IEC 82304 elements for requirements.  Keep in mind this is only intended to be used as a starting point and requires interpretation based on knowledge of each standard and the type of device or Health IT involved, and as always, the intended use and overall safety risk of the product.

Questions?  Thoughts?  Use the form below to connect with us.

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.