FDA Issues Final Guidance on Mobile Medical Apps

FDA Issues Final Guidance on Mobile Medical Apps

A bit more than two years after releasing their draft guidance, FDA has released the final guidance (pdf) on mobile medical apps (FDA press release). FDA also put up a new page on their web site with information on mobile medical apps.

In this final guidance, FDA has chosen to use two factors to distinguish between mobile medical apps that are low risk that they do not intend to regulate, and higher risk apps that will be regulated. FDA will regulate those mobile medical apps intended:

  • to be used as an accessory to a regulated medical device; or
  • to transform a mobile platform into a regulated medical device.

As always with FDA, the question of whether a mobile app is regulated or not, will be decided on the intended use or claims made by the manufacturer as described in promotional materials, user manuals and similar content and communications.

FDA references two pages of examples of mobile medical apps.  The first list includes Class II medical devices that have received premarket clearance (aka, a 510k). Anyone can submit a 510k for clearance for any kind of device – whether FDA really thinks its a medical device or not. Consequently, this list is not an absolute guide to what FDA considers a mobile medical app that they want to regulate. Unfortunately, the page does not include any links to product information or information on the 510k summary for each product. A search on the “K number” in the FDA’s 510k database, e.g., K020866 for Abbott’s Freestyle Tracker Diabetes Management System, will return a 510k summary for the product, including intended use, classification and product code.

The second list is a reproduction of the final guidance Appendix C, Examples of mobile apps that are the focus of FDA’s regulatory oversight (mobile medical apps). Here, examples of products FDA intends to regulate are described, along with possible product codes. (For more information, FDA’s page on product codes is here.)

Another list is found in Appendix B, Examples of mobile apps for which FDA intends to exercise enforcement discretion. According to Bakul Patel of FDA, “the term “enforcement discretion” means that even if the medical app may meet the definition of a medical device, the FDA can choose to not enforce our requirements because we have determined that the risk to patients is low.” To clarify, the list of products in Appendix B are products that do meet the legal definition of a medical device, however the FDA has said they will not pursue enforcement of the regulations.

This guidance process was not without some controversy. One group, lead by Brad Thompson and the mHealth Regulatory Coalition, was pushing for a quick publication of the final guidance in an effort to end the existing ambiguities around regulating mobile medical apps. Another group, was lobbying for a delay of the final guidance (and apparently hoping to avoid regulation by FDA) until the FDASIA Workgroup completed their recommendations on the potential (inevitable, really) regulation of health care IT (HIT) by the FDA. Thompson replied, noting that waiting for legislation as suggested by the “delay guidance” group would take months or years, and the market would benefit from a reduction of ambiguity regarding mobile medical apps now.

Interestingly, the FDASIA Workgroup recommendations are mostly in line with FDA’s final guidance on mobile medical apps. It appears that FDA sought to reduce regulatory uncertainty regarding mobile medical apps in the short term, while looking to address some of the more broad issues raised by the FDASIA Workgroup in the medium to long term.

So, does the final guidance change anything? No, not really.

In this final guidance FDA has repeated, once again, that if a product meets the legal definition of a medical device, FDA can regulate it as a medical device – regardless of whether it’s something traditional like a stethoscope or patient monitor, or something that was never envisioned when the FDA was created, like computer software or mobile computing platforms. (The same goes for HIT, but that’s a topic for another blog post.)

For a developer of mobile apps a first step is to determine whether FDA is going to want to regulate it. Any company making products for health care should complete an analysis of whether their product is a medical device or not – and why. This determination should include details on how the intended use and claims of the product might or might not shift the product from not being regulated to being a regulated medical device, and vice a versa. If you’re not already regulated, with a regulatory affairs staff, get an outside regulatory affairs expert to assist.

In the guidance and on their mobile medical apps web page, FDA encourages companies to seek clarification from FDA. Certainly in matters of controversy, the FDA is the final and ultimate word. Be aware that how one goes about asking questions of the FDA can unintentionally commit the company to a certain course of action with FDA. If your company is not already regulated, always get a knowledgeable person to frame things and interact with FDA to maintain maximum flexibility in how, or whether, your product is regulated.

UPDATE: Brad Thompson posts a great overview of this final guidance on MD+DI Device Talk.

Tim Gee is Principal of Medical Connectivity Consulting. He is a master connectologist, technologist and strategist working for medical device and IT companies and various provider organizations. You can learn more about Tim here.

Share

10 comments

  1. William Hyman

    On late October, 2013 legislation was introduced in the House to “better explain” which mobile apps were to be regulated by the FDA and which were not.

    http://beta.congress.gov/113/bills/hr3303/BILLS-113hr3303ih.pdf

    The acronym gurus worked hard on this one to come up with the title of “Sensible Oversight for Technology which Advances Regulatory Efficiency Act of 2013″, which, yes, the perceptive got it already…the “SOFTWARE Act of 2013″.

    The Act adds some specific language about software that provides recommendations to the definition of a medical device, and for the first time specifically asserts that software that provides certain functionality is a regulated medical device. It then distinguishes “clinical” software from “health” software. It then says that further work should be done to establish an appropriate regulatory framework.

    Of course legislation being introduced can be far from ever becoming law.

  2. Howdy. Just needed to ask an instant query. Now i am putting together my blog
    as well as wish to know wherever you still have ones design?
    Had been this totally free? Or even seemed to be this settled?
    I cannot manage to locate something as effective as this blog,
    and so preferably you possibly can well then, i’ll
    recognize. Cheers. PS, the i’m sorry. English is not the primary terminology.

  3. Hello there. Simply desired to consult a simple issue.

    Now i’m putting together my own web site in addition to wish to understand
    where you’ve got ones concept? Had been this no cost?
    Or perhaps ended up being that paid out? Could not often discover
    anything as good as this blog, therefore ideally you are able to allow
    me to understand. Many thanks. PS, the i’m sorry.
    Language isn’t my personal initial dialect.

  4. Hi. Simply wanted to ask an instant issue. Now i am setting up my own, personal web
    site in addition to wish to understand where you still have your
    current topic? Seemed to be it cost-free? Or perhaps has been the idea paid for?
    I can not appear to locate something as good as this place, thus with luck ,
    you can allow me to recognize. Thank you. PS, my own apologies.

    Uk is not the primary vocabulary.

  5. Hi there! Do you use Twitter? I’d like to follow you if that would be okay.

    I’m definitely enjoying your blog and look forward to new updates.

  6. This piece of writing offers clear idea designed for the
    new visitors of blogging, that genuinely how to do running a
    blog.

  7. Hi. Only needed to inquire a rapid dilemma. I’m piecing together
    my personal website as well as would choose to understand wherever you were given ones concept?
    Has been that cost-free? Or even has been the idea paid
    for? I can’t manage to find everything just like this,
    so hopefully you possibly can ok, i’ll know. Thank you.
    PS, my i’m sorry. The english language is not my very first terminology.

  8. Having read this I thought it was very informative. I appreciate you taking the time and
    effort to put this informative article together.
    I once again find myself personally spending a lot of time
    both reading and leaving comments. But so what, it was still worth it!

  9. each time i used to read smaller posts that as well clear their
    motive, and that is also happening with this piece of writing which I am reading now.

  10. Howdy. Simply wanted to question a rapid dilemma. I’m putting together my blog and would like to recognize where by you have ones topic?

    Was this totally free? Or even ended up being it paid out?
    I am unable to apparently come across anything as
    good as this place, thus hopefully you can allow me
    to understand. Cheers. PS, my own i’m sorry. Uk is not our initial vocabulary.

Trackbacks/Pingbacks

  1. FDA Regulation of Mobile Medical Apps | Bob on Medical Device Software - […] Also see: FDA Issues Final Guidance on Mobile Medical Apps. […]
  2. FDASIA Report on Regulating HIT | Medical Connectivity - […] risk-based health information technology framework, including mobile medical applications [already published], that “promotes innovation, protects patient safety, and avoids …

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>