Hello Anon,
The FDA has stated they are not regulating MDDS, though may be done at discretion depending on the software and claims being made. So in essence, as not regulated, there is no requirement to complete design controls. However, if this non-device MDDS software is part of a medical device, you may still need to do a minimum number of items like risk management, interoperability, configuration management, or change control. It might be recommended to treat this non-device MDDS software as an OTS software and apply the respective risk assessment from the FDA guidance document for OTS software:
https://www.fda.gov/regulatory-information/search-fda-guidance-documents/shelf-software-use-medical-devices. It might give some thoughts and insight on what might need to document for this non-device MDDS.
------------------------------
Richard Vincins RAC
Vice President Global Regulatory Affairs
------------------------------
Original Message:
Sent: 25-Feb-2021 22:25
From: Anonymous Member
Subject: Design control for Non-Device-MDDS component that is part of a medical device
This message was posted by a user wishing to remain anonymous
Hi All,
Is design control needed for a non-device MDDS (software) that is part of a medical device? Based on 520(o)(1)(D), it looks like there is no design control requirement for non-device MDDS (software) component, even if it is part of a medical device. Please share your thoughts.
Per section "520(o)(1)(D) of the Federal Food, Drug, and Cosmetic Act:
Software functions that are solely intended to transfer, store, convert formats, and display medical device data or medical imaging data, are not devices and are not subject to FDA regulatory requirements applicable to devices. The FDA describes these software functions as "Non-Device-MDDS."
Thanks in advance