Source: http://docplayer.net/14301224-Mobile-medical-applications-guidance-for-industry-and-food-and-drug-administration-staff.html
Timestamp: 2018-09-20 05:05:26
Document Index: 498992397

Matched Legal Cases: ['arts 803', 'arts 803', 'arts 803', 'arts 803', 'art 807', 'art 820', 'art 801', 'art 803', 'art 807', 'art 806', 'art 812', 'art 814']

Mobile Medical Applications. Guidance for Industry and Food and Drug Administration Staff - PDF
Download "Mobile Medical Applications. Guidance for Industry and Food and Drug Administration Staff"
1 Mobile Medical Applications Guidance for Industry and Food and Drug Administration Staff Document issued on: September 25, 2013 The draft of this guidance was issued on July 21, For questions regarding this document, contact Bakul Patel at or by electronic mail at For questions regarding this document concerning devices regulated by CBER, contact the Office of Communication, Outreach and Development (OCOD), by calling or U.S. Department of Health and Human Services Food and Drug Administration Center for Devices and Radiological Health Center for Biologics Evaluation and Research - 1 -
2 Preface Public Comment You may submit written comments and suggestions at any time for Agency consideration to the Division of Dockets Management, Food and Drug Administration, 5630 Fishers Lane, rm (HFA-305), Rockville, MD, Submit electronic copies to Identify all comments with the docket number listed in the notice of availability that publishes in Federal Register. Comments may not be acted upon by the Agency until the document is next revised or updated. Additional Copies CDRH Additional copies are available from the Internet. You may also send an request to to receive an electronic copy of the guidance or send a fax request to to receive a hard copy. Please use the document number (1741) to identify the guidance you are requesting. CBER Additional copies are available from the Center for Biologics Evaluation and Research (CBER) by written request, Office of Communication, Outreach and Development (OCOD) (HFM-40), 1401 Rockville Pike, Suite 200N, Rockville, MD , or by calling or , by , or from the Internet at Guidances/default.htm
3 Table of Contents I. INTRODUCTION... 4 II. BACKGROUND... 6 III. DEFINITIONS... 7 A. MOBILE PLATFORM... 7 B. MOBILE APPLICATION (MOBILE APP)... 7 C. MOBILE MEDICAL APPLICATION (MOBILE MEDICAL APP)... 7 D. REGULATED MEDICAL DEVICE... 9 E. MOBILE MEDICAL APP MANUFACTURER... 9 IV. SCOPE V. REGULATORY APPROACH FOR MOBILE MEDICAL APPS A. MOBILE MEDICAL APPS: SUBSET OF MOBILE APPS THAT ARE THE FOCUS OF FDA S REGULATORY OVERSIGHT B. MOBILE APPS FOR WHICH FDA INTENDS TO EXERCISE ENFORCEMENT DISCRETION (MEANING THAT FDA DOES NOT INTEND TO ENFORCE REQUIREMENTS UNDER THE FD&C ACT) VI. REGULATORY REQUIREMENTS APPENDIX A EXAMPLES OF MOBILE APPS THAT ARE NOT MEDICAL DEVICES APPENDIX B EXAMPLES OF MOBILE APPS FOR WHICH FDA INTENDS TO EXERCISE ENFORCEMENT DISCRETION APPENDIX C EXAMPLES OF MOBILE APPS THAT ARE THE FOCUS OF FDA S REGULATORY OVERSIGHT (MOBILE MEDICAL APPS) APPENDIX D EXAMPLES OF CURRENT REGULATIONS APPENDIX E BRIEF DESCRIPTION OF CERTAIN DEVICE REGULATORY REQUIREMENTS APPENDIX F FREQUENTLY ASKED QUESTIONS (FAQS) APPENDIX G ADDITIONAL RESOURCES
4 Mobile Medical Applications Guidance for Industry and Food and Drug Administration Staff This guidance represents the Food and Drug Administration's (FDA's) current thinking on this topic. It does not create or confer any rights for or on any person and does not operate to bind FDA or the public. You can use an alternative approach if the approach satisfies the requirements of the applicable statutes and regulations. If you want to discuss an alternative approach, contact the FDA staff responsible for implementing this guidance. If you cannot identify the appropriate FDA staff, call the appropriate number listed on the title page of this guidance. I. Introduction The Food and Drug Administration (FDA) recognizes the extensive variety of actual and potential functions of mobile apps, the rapid pace of innovation in mobile apps, and the potential benefits and risks to public health represented by these apps. The FDA is issuing this guidance document to inform manufacturers, distributors, and other entities about how the FDA intends to apply its regulatory authorities to select software applications intended for use on mobile platforms (mobile applications or mobile apps ). Given the rapid expansion and broad applicability of mobile apps, the FDA is issuing this guidance document to clarify the subset of mobile apps to which the FDA intends to apply its authority. Many mobile apps are not medical devices (meaning such mobile apps do not meet the definition of a device under section 201(h) of the Federal Food, Drug, and Cosmetic Act (FD&C Act)), and FDA does not regulate them. Some mobile apps may meet the definition of a medical device but because they pose a lower risk to the public, FDA intends to exercise enforcement discretion over these devices (meaning it will not enforce requirements under the FD&C Act). The majority of mobile apps on the market at this time fit into these two categories. Consistent with the FDA s existing oversight approach that considers functionality rather than platform, the FDA intends to apply its regulatory oversight to only those mobile apps that are medical devices and whose functionality could pose a risk to a patient s safety if the mobile app were to not function as intended. This subset of mobile apps the FDA refers to as mobile medical apps. FDA is issuing this guidance to provide clarity and predictability for manufacturers of mobile medical apps. Should FDA determine at a later date that the policy in this guidance should be changed in light of new information, the agency would follow a public process, including the - 4 -
5 opportunity for public input, consistent with FDA s good guidance practices (GGP) regulation in 21 CFR FDA's guidance documents, including this guidance, do not establish legally enforceable responsibilities. Instead, guidances describe the Agency's current thinking on a topic and should be viewed only as recommendations, unless specific regulatory or statutory requirements are cited. The use of the word should in Agency guidances means that something is suggested or recommended, but not required
6 II. Background As mobile platforms become more user friendly, computationally powerful, and readily available, innovators have begun to develop mobile apps of increasing complexity to leverage the portability mobile platforms can offer. Some of these new mobile apps are specifically targeted to assisting individuals in their own health and wellness management. Other mobile apps are targeted to healthcare providers as tools to improve and facilitate the delivery of patient care. In 1989, FDA prepared a general policy statement on how it planned to determine whether a computer-based product and/or software-based product is a device, and, if so, how the FDA intended to regulate it. The document, FDA Policy for the Regulation of Computer Products, became known as the Draft Software Policy. After 1989, however, the use of computer and software products as medical devices grew exponentially and the types of products diversified and grew more complex (and that trend has continued). As a result, the FDA determined that the draft policy did not adequately address all of the issues related to the regulation of all medical devices containing software. Therefore, in 2005, the Draft Software Policy was withdrawn. 1 Although the FDA has not issued an overarching software policy, the Agency has formally classified certain types of software applications that meet the definition of a device and, through classification, identified specific regulatory requirements that apply to these devices and their manufacturers. These software devices include products that feature one or more software components, parts, or accessories (such as electrocardiographic (ECG) systems used to monitor cardiac rhythms), as well as devices that are composed solely of software (such as laboratory information management systems). On February 15, 2011, the FDA issued a regulation downclassifying certain computer- or software-based devices intended to be used for the electronic transfer, storage, display, and/or format conversion of medical device data called Medical Device Data Systems (MDDSs) from Class III (high-risk) to Class I (low-risk). 2 The FDA has previously clarified that when stand-alone software is used to analyze medical device data, it has traditionally been regulated as an accessory to a medical device 3 or as medical device software. As is the case with traditional medical devices, certain mobile medical apps can pose potential risks to public health. Moreover, certain mobile medical apps may pose risks that are unique to the characteristics of the platform on which the mobile medical app is run. For example, the 1 Annual Comprehensive List of Guidance Documents at the Food and Drug Administration (70 FR 824 at 890) (January 5, 2005). 2 Medical Devices; Medical Device Data Systems Final Rule (76 FR 8637) (Feb. 15, 2011). 3 See, for example, Content of a 510(k) -- ns/premarketnotification510k/ucm htm ( Accessories to classified devices take on the same classification as the "parent" device. An accessory such as software that accepts input from multiple devices usually takes on the classification of the "parent" device with the highest risk, i.e., class. ); See also final Rule, Medical Devices, Medical Device Data Systems, 76 FR 8637 at comment 16 and FDA s response (Feb. 15, 2011)
7 interpretation of radiological images on a mobile device could be adversely affected by the smaller screen size, lower contrast ratio, and uncontrolled ambient light of the mobile platform. FDA intends to take these risks into account in assessing the appropriate regulatory oversight for these products. This guidance clarifies and outlines the FDA s current thinking. The Agency will continue to evaluate the potential impact these technologies might have on improving health care, reducing potential medical mistakes, and protecting patients. III. Definitions A. Mobile Platform For purposes of this guidance, mobile platforms are defined as commercial off-the-shelf (COTS) computing platforms, with or without wireless connectivity, that are handheld in nature. Examples of these mobile platforms include mobile computers such as smart phones, tablet computers, or other portable computers. B. Mobile Application (Mobile App) For purposes of this guidance, a mobile application or mobile app is defined as a software application that can be executed (run) on a mobile platform (i.e., a handheld commercial off-theshelf computing platform, with or without wireless connectivity), or a web-based software application that is tailored to a mobile platform but is executed on a server. C. Mobile Medical Application (Mobile Medical App) For purposes of this guidance, a mobile medical app is a mobile app that meets the definition of device in section 201(h) of the Federal Food, Drug, and Cosmetic Act (FD&C Act) 4 ; and either is intended: to be used as an accessory to a regulated medical device; or to transform a mobile platform into a regulated medical device. 4 Products that are built with or consist of computer and/or software components or applications are subject to regulation as devices when they meet the definition of a device in section 201(h) of the FD&C Act. That provision defines a device as an instrument, apparatus, implement, machine, contrivance, implant, in vitro reagent, or other similar or related article, including any component, part, or accessory, that is intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease, in man or intended to affect the structure or any function of the body of man or other animals. Thus, software applications that run on a desktop computer, laptop computer, remotely on a website or cloud, or on a handheld computer may be subject to device regulation if they are intended for use in the diagnosis or the cure, mitigation, treatment, or prevention of disease, or to affect the structure or any function of the body of man. The level of regulatory control necessary to assure safety and effectiveness varies based upon the risk the device presents to public health. (See Appendix D for examples)
8 The intended use of a mobile app determines whether it meets the definition of a device. As stated in 21 CFR 801.4, 5 intended use may be shown by labeling 6 claims, advertising materials, or oral or written statements by manufacturers or their representatives. When the intended use of a mobile app is for the diagnosis of disease or other conditions, or the cure, mitigation, treatment, or prevention of disease, or is intended to affect the structure or any function of the body of man, the mobile app is a device. One example is a mobile app that makes a light emitting diode (LED) operate. If the manufacturer intends the system to illuminate objects generally (i.e., without a specific medical device intended use), the mobile app would not be considered a medical device. If, however, through marketing, labeling, and the circumstances surrounding the distribution, the mobile app is promoted by the manufacturer for use as a light source for doctors to examine patients, then the intended use of the light source would be similar to a conventional device such as an ophthalmoscope. In general, if a mobile app is intended for use in performing a medical device function (i.e. for diagnosis of disease or other conditions, or the cure, mitigation, treatment, or prevention of disease) it is a medical device, regardless of the platform on which it is run. For example, mobile apps intended to run on smart phones to analyze and interpret EKG waveforms to detect heart function irregularities would be considered similar to software running on a desktop computer that serves the same function, which is regulated under 21 CFR ( Electrocardiograph ). FDA s oversight approach to mobile apps is focused on their functionality, just as we focus on the functionality of conventional devices. Our oversight is not determined by the platform. Under this guidance, FDA would not regulate the sale or general/conventional consumer use of smartphones or tablets. FDA s oversight applies to mobile apps performing medical device functions, such as when a mobile medical app transforms a mobile platform into a medical device. However, as previously noted, we intend to apply this oversight authority only to those mobile apps whose functionality could pose a risk to a patient s safety if the mobile app were to not function as intended. 5 The words intended uses or words of similar import refer to the objective intent of the persons legally responsible for the labeling of devices. The intent is determined by such persons' expressions or may be shown by the circumstances surrounding the distribution of the article. This objective intent may, for example, be shown by labeling claims, advertising matter, or oral or written statements by such persons or their representatives. It may be shown by the circumstances that the article is, with the knowledge of such persons or their representatives, offered and used for a purpose for which it is neither labeled nor advertised. The intended uses of an article may change after it has been introduced into interstate commerce by its manufacturer. If, for example, a packer, distributor, or seller intends an article for different uses than those intended by the person from whom he received the devices, such packer, distributor, or seller is required to supply adequate labeling in accordance with the new intended uses. But if a manufacturer knows, or has knowledge of facts that would give him notice that a device introduced into interstate commerce by him is to be used for conditions, purposes, or uses other than the ones for which he offers it, he is required to provide adequate labeling for such a device which accords with such other uses to which the article is to be put. 21 CFR The term labeling means all labels and other written, printed, or graphic matter (1) upon any article or any of its containers or wrappers, or (2) accompanying such article. Section 201(m) of the FD&C Act, 21 U.S.C. 321(m)
9 D. Regulated Medical Device For purposes of this guidance, a regulated medical device is defined as a product that meets the definition of device in section 201(h) of the FD&C Act and that has been cleared or approved by the FDA review of a premarket submission or otherwise classified by the FDA. This definition can include novel devices, whether or not on a mobile platform, that the FDA will clear or approve by the review of a premarket submission or otherwise classify. Examples of regulated medical devices are identified in Appendix D. E. Mobile Medical App Manufacturer For purposes of this guidance, a mobile medical app manufacturer is any person or entity that manufactures mobile medical apps in accordance with the definitions of manufacturer in 21 CFR Parts 803, 806, 807, and A mobile medical app manufacturer may include anyone who initiates specifications, designs, labels, or creates a software system or application for a regulated medical device in whole or from multiple software components. This term does not include persons who exclusively distribute mobile medical apps without engaging in manufacturing functions; examples of such distributors may include owners and operators of Google play, itunes App store, and BlackBerry App World. Examples of mobile medical app manufacturers include any person or entity that: Creates, designs, develops, labels, re-labels, remanufactures, modifies, or creates a mobile medical app software system from multiple components. This could include a person or entity that creates a mobile medical app by using commercial off the shelf (COTS) software components and markets the product to perform as a mobile medical app; Initiates specifications or requirements for mobile medical apps or procures product development/manufacturing services from other individuals or entities (second party) for subsequent commercial distribution. For example, when a developer (i.e., an entity that provides engineering, design, and development services) creates a mobile medical app from the specifications that were initiated by the author, the author who initiated and developed specifications for the mobile medical app is considered a manufacturer of the mobile medical app under 21 CFR For purposes of this guidance, manufacturers of a mobile medical app would include persons or entities who are the creators of the original idea (initial specifications) for a mobile medical 7 Regulatory definitions of the term manufacturer or manufacture appear in 21 CFR Parts 803, 806, 807, and 820. For example -- under FDA s 21 CFR 807.3(d)-- establishment registration and device listing for manufacturers and initial importers of devices--, Manufacture, preparation, propagation, compounding, assembly, or processing of a device means the making by chemical, physical, biological, or other procedures of any article that meets the definition of device in section 201(h) of the act. These terms include the following activities: (1) Repackaging or otherwise changing the container, wrapper, or labeling of any device package in furtherance of the distribution of the device from the original place of manufacture to the person who makes final delivery or sale to the ultimate consumer; (2) Initial importation of devices manufactured in foreign establishments; or (3) Iinitiation of specifications for devices that are manufactured by a second party for subsequent commercial distribution by the person initiating specifications
10 app, unless another entity assumes all responsibility for manufacturing and distributing the mobile medical app, in which case that other entity would be the manufacturer. 8 Software developers of a mobile medical app that are only responsible for performing design and development activities to transform the author s specifications into a mobile medical app would not constitute manufacturers, and instead the author would be considered the manufacturer; Creates a mobile medical app and hardware attachments for a mobile platform that are intended to be used as a medical device by any combination of the mobile medical app, hardware attachments, and the mobile platform; Creates a mobile medical app or a software system that provides users access to the medical device function through a website subscription, software as a service, 9 or other similar means. In contrast, the following are examples of persons or entities that are NOT considered to be mobile medical app manufacturers (i.e., persons not within the definition of manufacturer in 21 CFR Parts 803, 806, 807, and 820). Because they are not manufacturers, none of the persons or entities in these examples would have to register their establishments, list their products with the FDA 10 or submit a premarket application: Manufacturers or distributors of mobile platforms who solely distribute or market their platform and do not intend (by marketing claims -- e.g., labeling claims or advertising material) the platform to be used for medical device functions. When mobile medical apps are run on a mobile platform, the mobile platform is treated as a component of the mobile medical app s intended use. 11 Therefore the mobile platform manufacturer is exempt from the Quality System regulation and registration and listing requirements. 12 For example, if it is possible to run mobile medical apps on BrandNamePhone but BrandNamePhone is not marketed by BrandNameCompany as intended for use as a medical device, then BrandNameCompany would not be considered a mobile medical app manufacturer or a medical device manufacturer. Also, in this example, the BrandName Phone sold to consumers would not be regulated by FDA as a medical device. FDA does not consider entities that exclusively distribute mobile medical apps, such as the owners and operators of the itunes App store or the Android market, to be medical device manufacturers. FDA also does not consider mobile platform manufacturers to be medical device manufacturer just because their mobile platform could be used to run a mobile medical app regulated by FDA. Third parties who solely provide market access to mobile medical apps (i.e. solely distribute mobile apps), but do not engage in any manufacturing functions as defined in 8 See 21 CFR (definition of manufacturer) and 21 CFR (a)(2). 9 By this we mean to include any server software application that provides a service to a client software application on a mobile platform CFR and 21 CFR See 21 CFR 820.3(c) which defines a component as any raw material, substance, piece, part, software, firmware, labeling, or assembly which is intended to be included as part of the finished, packaged, and labeled device CFR (a) and 21 CFR 820.1(a)
11 21 CFR Parts 803, 806, 807, and 820. Examples of such third parties may include owners and operators that are only engaged in providing an online market place that allow mobile medical app manufacturers to commercially distribute their mobile medical apps. Specific examples of such online market places include Google play, itunes store, and BlackBerry App World ; Providers of tools, services or infrastructure used in the development, distribution, or use of a mobile medical app. Examples include providers of internet connectivity (i.e., internet service), providers of general purpose computer or information technology, providers that host the web service for content or software application. Other examples of providers of tools, services, or infrastructure include customer support services, data center hosting services, cloud hosting services, application hosting services, wireless carriers, or providers of software development kits. However, a creator of a mobile medical app or a software system that provides users access to the medical device function through a website subscription, software as a service, 13 or other similar means is considered a mobile medical app manufacturer; Licensed practitioners, including physicians, dentists, and optometrists, who manufacture a mobile medical app or alter a mobile medical app solely for use in their professional practice and do not label or promote their mobile medical apps to be generally used by other licensed practitioners or other individuals. 14,15 For example, if Dr. XYZ, a licensed practitioner, creates a mobile medical app called the XYZ-recorder which enables attaching an ECG electrode to a smartphone, and provides the XYZ-recorder to his/her patient to use it to record the patient s electrocardiographic readings for 24 hours, Dr. XYZ is not considered a mobile medical app manufacturer. If Dr. XYZ is in a group practice (including a telehealth network) and permits other physicians in the practice to provide the XYZ-recorder to their patients, Dr. XYZ is not considered a mobile medical apps manufacturer. However, if Dr. XYZ, the licensed practitioner, distributes the XYZ-recorder and, through labeling or promotion intends to make it generally available to or to be generally used by other physicians (or other specially qualified persons), Dr. XYZ would be considered a mobile medical app manufacturer; Persons who manufacture mobile medical apps solely for use in research, teaching, or analysis and do not introduce such devices into commercial distribution. We note that while persons conducting research using mobile medical apps involving human subjects are exempt from registration and listing, they may instead be subject to investigational device exemption regulations. 16,17 13 See footnote Section 510(g)(2) of the FD&C Act: - Registration of producers of drugs or devices Exclusions from application of section: practitioners licensed by law to prescribe or administer drugs or devices and who manufacture, prepare, propagate, compound, or process drugs or devices solely for use in the course of their professional practice. 15 See 21 CFR (d). 16 See 21 CFR (f). 17 See 21 CFR
12 IV. Scope This guidance explains the FDA s intentions to focus its oversight on a subset of mobile apps. Mobile medical apps as defined in section III include only those mobile apps that meet the statutory definition of a device and either are intended: to be used as an accessory to a regulated medical device; or to transform a mobile platform into a regulated medical device. Appendix A provides examples of mobile apps that FDA does NOT consider to meet the definition of medical device and, therefore, are NOT mobile medical apps for the purposes of this guidance. Section V-B and Appendix B provide examples of mobile apps that MAY meet the definition of a medical device but for which the FDA intends to exercise enforcement discretion because they pose a low risk to patients. 18 This guidance does not address the approach for software that performs patient-specific analysis to aid or support clinical decision-making. FDA s policies regarding accessories to medical devices are not unique to mobile medical apps and go beyond the scope of this guidance. Specifically this guidance does not address FDA s general approach for accessories to medical devices. If you are developing a mobile medical app with an entirely new intended use, we encourage you to contact FDA to discuss what regulatory requirements may apply. 18 This indicates that for certain mobile medical app devices, such as those in Appendix B, the FDA intends not to pursue enforcement action for violations of the FD&C Act and applicable regulations by a manufacturer of a mobile app that meets the definition of a device in section 201(h) of the FD&C Act as specified in this guidance. This does not constitute a change in the requirements of the FD&C Act or any applicable regulation
13 V. Regulatory approach for mobile medical apps As described in this guidance, FDA intends to apply its regulatory oversight to only those mobile apps that are medical devices and whose functionality could pose a risk to a patient s safety if the mobile app were to not function as intended. This approach to overseeing mobile medical apps is consistent with our existing approach to overseeing medical device functionality of a product and the risks it poses to patients regardless of the shape, size or the platform. The FDA believes that this subset of mobile medical apps poses the same or similar potential risks to the public health as currently regulated devices if they fail to function as intended. The FDA strongly recommends that manufacturers of all mobile apps that may meet the definition of a device follow the Quality System 19 regulation (which includes good manufacturing practices) in the design and development 20 of their mobile medical apps and initiate prompt corrections to their mobile medical apps, when appropriate, to prevent patient and user harm. For mobile medical apps, manufacturers must meet the requirements associated with the applicable device classification. If the mobile medical app, on its own, falls within a medical device classification, its manufacturer is subject to the requirements associated with that classification. A mobile medical app, like other devices, may be classified as class I (general controls), class II (special controls in addition to general controls), or class III (premarket approval). 21 A. Mobile medical apps: Subset of mobile apps that are the focus of FDA s regulatory oversight Mobile apps may take a number of forms, but it is important to note that the FDA intends to apply its regulatory oversight to only the subset of mobile apps identified below and in Appendix C. These mobile apps can transform a mobile platform into a regulated medical device by using attachments, display screens, sensors, or other such methods. Regardless of the mechanism behind the transformation, FDA considers such mobile apps to be mobile medical apps. The following are mobile apps that FDA considers to be mobile medical apps subject to regulatory oversight: 19 See 21 CFR part The FDA has found that the majority of software-related device failures are due to design errors. In one study, the most common problem was failure to validate software prior to routine production. See Medical Devices; Current Good Manufacturing Practice (CGMP) Final Rule); Quality System Regulation (61 FR 52602) (October 7, 1996). 21 See footnotes 3 and
14 1. Mobile apps that are an extension of one or more medical devices by connecting 22 to such device(s) for purposes of controlling 23 the device(s) or displaying, storing, analyzing, or transmitting patient-specific medical device data. o Examples of displays of patient-specific medical device data include: remote display of data from bedside monitors, display of previously stored EEG waveforms, and display of medical images directly from a Picture Archiving and Communication System (PACS) server, or similar display functions that meet the definition of an MDDS. Mobile medical apps that display medical device data to perform active patient monitoring are subject to regulations associated with such devices. o Examples of mobile apps that control medical devices include: apps that provide the ability to control inflation and deflation of a blood pressure cuff through a mobile platform and mobile apps that control the delivery of insulin on an insulin pump by transmitting control signals to the pumps from the mobile platform. Mobile medical apps of this type are considered an accessory to the connected device and are required to comply with the controls applicable to that connected device. The FDA considers such mobile medical apps to extend the intended use and functionality of the connected medical device. As a result, the mobile medical app would be required to comply with the regulations applicable to the connected medical device in order to address any associated risks. o Examples of mobile apps that display, store, or transfer medical device data in its original format include: apps that are intended to display or store medical device data, without controlling or altering the functions or parameters of any connected medical device constitute a Medical Device Data System (MDDS) (21 CFR ) and are subject to class I requirements (general controls). Class I are the lowest risk devices with the fewest requirements and generally no premarket submission. Class I general controls include these basics: adequate design controls, registration, device listing, adverse event reporting, and corrections and removals. The FDA believes that requiring general controls sufficiently manages the risks for mobile medical apps that are used as a secondary display to a regulated medical device and are not intended to provide primary diagnosis or treatment decisions (i.e., mobile medical apps that meet the MDDS definition). 2. Mobile apps that transform the mobile platform into a regulated medical device by using attachments, display screens, or sensors or by including functionalities similar to those of currently regulated medical devices. Mobile apps that use attachments, display screens, sensors or other such similar components to 22 To meet this criterion, the mobile medical apps need not be physically connected to the regulated medical device (i.e. the connection can be wired or wireless). 23 Controlling the intended use, function, modes, or energy source of the connected medical device
15 transform a mobile platform into a regulated medical device are required to comply with the device classification associated with the transformed platform. o Examples of these types of mobile apps include: a mobile app that uses a mobile platform for medical device functions, such as attachment of a blood glucose strip reader to a mobile platform to function as a glucose meter; or attachment of electrocardiograph (ECG) electrodes to a mobile platform to measure, store, and display ECG signals; a mobile app that uses the built-in accelerometer on a mobile platform to collect motion information for monitoring sleep apnea; a mobile app that uses sensors (internal or external) on a mobile platform for creating electronic stethoscope function is considered to transform the mobile platform into an electronic stethoscope; manufacturers of such a mobile app are required to follow the requirements of 21 CFR (b) (Electronic Stethoscope); and similarly a mobile app that displays radiological images for diagnosis transforms the mobile platform into a class II Picture Archiving and Communications System (PACS) under 21 CFR The FDA has cleared several mobile medical apps with attachments to a mobile platform. Specifically, patient monitoring mobile apps that monitors a patient for heart rate variability from a signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor are classified as cardiac monitoring software under 21 CFR (Cardiac monitor). Other mobile medical apps that use a hardware attachment or interface to a monitoring system that have been cleared include an automatic electronic blood pressure monitor under 21 CFR and a perinatal monitoring system under 21 CFR Mobile apps that become a regulated medical device (software) by performing patient-specific analysis and providing patient-specific diagnosis, or treatment recommendations. These types of mobile medical apps are similar to or perform the same function as those types of software devices that have been previously cleared or approved. o Examples of mobile apps that perform sophisticated analysis or interpret data (electronically collected or manually entered) from another medical device include: apps that use patient-specific parameters and calculate dosage or create a dosage plan for radiation therapy; Computer Aided Detection software (CAD); image processing software 24 ; and radiation therapy treatment planning software 25. We believe that these types of software present the same level of risk to patients regardless of the platform on which they run CFR CFR
16 The FDA encourages manufacturers of such mobile medical apps that perform patient-specific analysis to contact FDA to discuss what, if any, regulatory requirements may apply to their mobile app. For additional examples see Appendix C. B. Mobile Apps for which FDA intends to exercise enforcement discretion (meaning that FDA does not intend to enforce requirements under the FD&C Act) FDA intends to exercise enforcement discretion for mobile apps that: Help patients (i.e., users) self-manage their disease or conditions without providing specific treatment or treatment suggestions; Provide patients with simple tools to organize and track their health information; Provide easy access to information related to patients health conditions or treatments; Help patients document, show, or communicate potential medical conditions to health care providers; Automate simple tasks for health care providers; or Enable patients or providers to interact with Personal Health Record (PHR) or Electronic Health Record (EHR) systems. Some mobile apps in the above categories and listed below may be considered mobile medical apps, and others might not. For those mobile apps listed below that are devices, FDA intends to exercise enforcement discretion because they pose a low risk to patients. The following examples represent mobile apps for which the FDA intends to exercise enforcement discretion: 1. Mobile apps that provide or facilitate supplemental clinical care, by coaching or prompting, to help patients manage their health in their daily environment. These are apps that supplement 26 professional clinical care by facilitating behavioral change or coaching patients with specific diseases or identifiable health conditions in their daily environment. Examples include: o Apps that coach patients with conditions such as cardiovascular disease, hypertension, diabetes or obesity, and promote strategies for maintaining a healthy weight, getting optimal nutrition, exercising and staying fit, managing salt intake, or adhering to pre-determined medication dosing schedules 27 by simple prompting. 26 By this we mean that the app can be safely used by a patient without active oversight by a medical professional and, when used for serious conditions necessitating professional medical care, use of the app is not intended to replace or discourage seeking treatment from a health care provider. 27 We consider these mobile medical apps as medication reminders Product code NXQ currently defined as A medication reminder is a device intended for medical purposes to provide alerts to patients or healthcare providers for pre-determined medication dosing schedules. The device may incorporate wireless communication. The FDA
17 2. Mobile apps that provide patients with simple tools to organize and track their health information These are apps that provide patients with tools 28 to organize and track health information without providing recommendations to alter or change a previously prescribed treatment or therapy. Examples include: o Apps that provide simple tools for patients with specific conditions or chronic disease (e.g., obesity, anorexia, arthritis, diabetes, heart disease) to log, track, or trend their events or measurements (e.g., blood pressure measurements, drug intake times, diet, daily routine or emotional state) and share this information with their health care provider as part of a disease-management plan. 3. Mobile apps that provide easy access to information related to patients health conditions or treatments (beyond providing an electronic copy of a medical reference) These are apps that provide contextually-relevant information to users by matching patient-specific information (e.g., diagnosis, treatments, allergies, signs or symptoms) to reference information routinely used in clinical practice 29 (e.g., practice guidelines) to facilitate a user s assessment of a specific patient. Examples include: o Apps that use a patient s diagnosis to provide a clinician with best practice treatment guidelines for common illnesses or conditions such as influenza; o Apps that are drug-drug interaction or drug-allergy look-up tools. 4. Mobile apps that are specifically marketed to help patients document, show, or communicate to providers potential medical conditions These are apps that in their labeling or promotional materials are not promoted for medical uses but which, by virtue of other circumstances surrounding their distribution, may meet the definition of a medical device. These products either pose little or no risk, or are the sole responsibility of the health care providers who have used them in medical applications. Examples include: o Apps that serve as videoconferencing portals specifically intended for medical use and to enhance communications between patients, healthcare providers, and caregivers; o Apps specifically intended for medical uses that utilize the mobile device s builtin camera or a connected camera for purposes of documenting or transmitting pictures (e.g., photos of a patient s skin lesions or wounds) to supplement or augment what would otherwise be a verbal description in a consultation between healthcare providers or between healthcare providers and patients/caregivers. 5. Mobile apps that perform simple calculations routinely used in clinical practice These are apps that are intended to provide a convenient way for clinicians to perform various intends to exercise enforcement discretion for this specific product code (NXQ) identified under 21 CFR Daily activity assist device. 28 We consider these mobile apps to be tools which are not intended to provide specific treatment recommendations and/or are not part of diabetes management referred to in 21 CFR 862.9(c)(5). 29 The type of information provided in these apps is from authoritative medical sources, as recognized by the field or discipline that is the subject of the app
18 simple medical calculations taught in medical schools 30 and are routinely used in clinical practice. These apps are generally tailored for clinical use, but retain functionality that is similar to simple general purpose tools such as paper charts, spread sheets, timers or generic mathematical calculators. Examples of such general purpose tools include medical calculators for: o Body Mass Index (BMI) o Total Body Water / Urea Volume of Distribution o Mean arterial pressure o Glascow Coma Scale score o APGAR score o NIH Stroke Scale o Delivery date estimator 6. Mobile apps that enable individuals to interact with PHR systems or EHR systems -- These are apps that provide patients and providers with mobile access to health record systems or enables them to gain electronic access to health information stored within a PHR system or EHR system. Applications that only allow individuals to view or download EHR data are also included in this category. These mobile apps are generally meant to facilitate general patient health information management and health record-keeping activities. See Appendix B for additional examples for the six categories discussed. 30 The types of information in these calculators are available in medical sources which includes medical textbooks used in the curriculum of accredited medical schools
19 VI. Regulatory requirements This guidance, including Appendix C and existing medical device regulatory classifications in Appendix D, is intended to assist manufacturers in determining if a product is a mobile medical app and FDA s expectations for that product. Additional information can be found in Device Advice: Classify Your Medical Device at ice/default.htm. This section describes in greater detail the regulatory requirements applicable to mobile medical apps under this guidance (as described in Section V). Manufacturers of mobile medical apps are subject to the requirements described in the applicable device classification regulation below. Depending on the classification and the associated regulation for the mobile medical apps, manufacturers of mobile medical apps are required to follow associated controls established by the regulation. In general, the associated controls for each class of device is outlined below. Class I devices: General Controls, including: Establishment registration, and Medical Device listing (21 CFR Part 807); Quality System (QS) regulation (21 CFR Part 820); Labeling requirements (21 CFR Part 801); Medical Device Reporting (21 CFR Part 803); Premarket notification (21 CFR Part 807); Reporting Corrections and Removals (21 CFR Part 806); and Investigational Device Exemption (IDE) requirements for clinical studies of investigational devices (21 CFR Part 812). Class II devices: General Controls (as described for Class I), Special Controls, and (for most Class II devices) Premarket Notification. Class III devices: General Controls (as described for Class I), and Premarket Approval (21 CFR Part 814). Appendix E provides a brief summary of the above requirements. Additional information is available at under Overview of Medical Device Regulation and How to Market Your Device. If you need further assistance, you may contact the Division of Small Manufacturers, International and Consumer Assistance: phone: or
20 Appendix A Examples of mobile apps that are NOT medical devices This Appendix provides a representative list of mobile app functionalities to illustrate the types of mobile apps that could be used in a healthcare environment, in clinical care or patient management, but are not considered medical devices. Because these mobile apps are not considered medical devices, FDA does not regulate them. The FDA understands that there may be other unique and innovative mobile apps that may not be covered in this list that may also constitute healthcare related mobile apps. This list is not exhaustive; it is only intended to provide clarity and assistance in identifying when a mobile app is not considered to be a medical device. Specific examples of mobile apps that FDA does not consider to be devices and with no regulatory requirements under the current laws administered by FDA include: 1. Mobile apps that are intended to provide access to electronic copies (e.g., e-books, audio books) of medical textbooks or other reference materials with generic text search capabilities. These are not devices because these apps are intended to be used as reference materials and are not intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease by facilitating a health professional s assessment of a specific patient, replacing the judgment of clinical personnel, or performing any clinical assessment. Examples include mobile apps that are: o Medical dictionaries; o Electronic copies of medical textbooks or literature articles such as the Physician s Desk Reference or Diagnostic and Statistical Manual of Mental Disorders (DSM); o Library of clinical descriptions for diseases and conditions; o Encyclopedia of first-aid or emergency care information; o Medical abbreviations and definitions; o Translations of medical terms across multiple languages. 2. Mobile apps that are intended for health care providers to use as educational tools for medical training or to reinforce training previously received. These may have more functionality than providing an electronic copy of text (e.g., videos, interactive diagrams), but are not devices because they are intended generally for user education and are not intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease by facilitating a health professional s assessment of a specific patient, replacing the judgment of clinical personnel, or performing any clinical assessment. Examples include mobile apps that are: o Medical flash cards with medical images, pictures, graphs, etc.; o Question/Answer quiz apps; o Interactive anatomy diagrams or videos; o Surgical training videos; o Medical board certification or recertification preparation apps; o Games that simulate various cardiac arrest scenarios to train health professionals in advanced CPR skills
21 3. Mobile apps that are intended for general patient education and facilitate patient access to commonly used reference information. These apps can be patient-specific (i.e., filters information to patient-specific characteristics), but are intended for increased patient awareness, education, and empowerment, and ultimately support patient-centered health care. These are not devices because they are intended generally for patient education, and are not intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease by aiding clinical decision-making (i.e., to facilitate a health professional s assessment of a specific patient, replace the judgment of a health professional, or perform any clinical assessment). Examples include mobile apps that: o Provide a portal for healthcare providers to distribute educational information (e.g., interactive diagrams, useful links and resources) to their patients regarding their disease, condition, treatment or up-coming procedure; o Help guide patients to ask appropriate questions to their physician relevant to their particular disease, condition, or concern; o Provide information about gluten-free food products or restaurants; o Help match patients with potentially appropriate clinical trials and facilitate communication between the patient and clinical trial investigators; o Provide tutorials or training videos on how to administer first-aid or CPR; o Allow users to input pill shape, color or imprint and displays pictures and names of pills that match this description; o Find the closest medical facilities and doctors to the user s location; o Provide lists of emergency hotlines and physician/nurse advice lines; o Provide and compare costs of drugs and medical products at pharmacies in the user s location. 4. Mobile apps that automate general office operations in a health care setting and are not intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease. Examples include mobile apps that: o Determine billing codes like ICD-9 (international statistical classification of diseases); o Enable insurance claims data collection and processing and other apps that are similarly administrative in nature; o Analyze insurance claims for fraud or abuse; o Perform medical business accounting functions or track and trend billable hours and procedures; o Generate reminders for scheduled medical appointments or blood donation appointments; o Help patients track, review and pay medical claims and bills online; o Manage shifts for doctors; o Manage or schedule hospital rooms or bed spaces; o Provide wait times and electronic check-in for hospital emergency rooms and urgent care facilities. 5. Mobile apps that are generic aids or general purpose products. These apps are not considered devices because they are not intended for use in the diagnosis of disease or other conditions,