On September 25, 2013, FDA issued its final Mobile Medical Applications guidance for industry and FDA staff. The final guidance is based on the draft guidance issued July 21, 2011, but includes useful additional information.
First, the Agency has added Section V. B., and included Appendix B, which identify types of mobile applications (apps) for which FDA intends to exercise enforcement discretion. That is, FDA has identified examples of mobile apps that could be regulated as medical devices, but which the Agency has decided not to hold to the requirements of the Food, Drug & Cosmetic Act (the law encompassing medical devices). FDA has used enforcement discretion periodically over the years in a wide variety of regulatory situations. Section V. B. and Appendix B provide much a better clarification of the dividing line between FDA-regulated and non-regulated apps than was available in the 2011 draft guidance.
Second, the final guidance includes Appendix F: Frequently Asked Questions with substantive responses to 10 key questions. Apps developers should take particular note of FDA’s recommendations about software development processes to ensure high quality, ‘bug-free’ apps.
Of course, many apps will fall under FDA’s jurisdiction as regulated medical devices and many of these will require premarket notifications [510(k) submissions] before placing on the US market.
Please reach out to us at namsa.com/contact-us for support in a) complying with FDA’s expectations for software development, b) assessing whether your app is a medical app and/or requires a 510(k), and c) preparing and submitting any necessary 510(k)s.