Should Specialty Look at Mobile Health?

Specialty Pharmacy Times, January/February 2017, Volume 8, Issue 1

With the growth of fitness apps, electronic health records, and telemedicine, mobile health is poised to enter the specialty pharmacy space.

Mobile health (mHealth) is an emerging area that offers immense potential to reduce costs and achieve greater patient engagement.

Currently, there are more than 97,000 health and wellness mHealth apps, as the projected revenue for mHealth in 2017 is $26 billion. Additionally, 93% of physicians believe mHealth apps can improve patient health.1 However, with the growth of fitness apps, electronic health records, and the greater utilization of telemedicine, the question that many are asking is what is mobile health?

To date, there is no standardized definition of mHealth. Organizations such as the World Health Organization have previously referenced mHealth as “the provision of health services and information via mobile technologies such as mobile phones and personal digital assistants.” The National Institutes of Health Consensus Group referred to mHealth as “the use of mobile and wireless devices to improve health outcomes, healthcare services and health research.”2

Having no clear definition usually creates a Wild West regulatory scheme. Currently, mHealth is overseen by 3 regulatory agencies:

FDA

The FDA’s position on mHealth is that is it “taking a tailored, risk-based approach that focuses on the small subset of mobile apps that meet the regulatory definition of ‘device’ and that: are intended to be used as an accessory to a regulated medical device, or transform a mobile platform into a regulated medical device.

For many mobile apps that meet the regulatory definition of a ‘device’ but pose minimal risk to patients and consumers, the FDA will exercise enforcement discretions and will not expect manufacturers to submit premarket review applications or to register and list their apps with the FDA. The FDA’s mobile medical apps policy does not regulate the sale or general consumer use of smartphones or tablets.”3

FCC

“The Federal Communications Commission (FCC) regulates interstate and international communications by radio, television, wire, satellite and cable. The agency’s jurisdiction extends to non-Federal users of spectrum in the 50 states, the District of Columbia and US possessions. The FCC manages radiofrequency (RF) communications to ensure that RF devices operate efficiently and without interference. In the healthcare area, the FCC authorizes a wide variety of RF-based medical devices including both implanted devices and patient monitoring devices. It also authorizes carriers whose networks are used by a wide variety of mobile devices to access, store or transmit health information, and it establishes technical rules used by Wi-Fi and other similar networks.”4

FTC

The Federal Trade Commission (FTC) protects consumers from fraudulent, unfair or deceptive acts or business practices. “The Federal Trade Commission has created a new web-based tool for developers of health-related mobile apps, which is designed to help the developers understand what federal laws and regulations might apply to their apps. The FTC developed the tool in conjunction with the Department of Health and Human Services’ Office of National Coordinator for Health Information Technology (ONC), Office for Civil Rights (OCR) and the Food and Drug Administration (FDA).

The guidance tool asks developers a series of high-level questions about the nature of their app, including about its function, the data it collects, and the services it provides to users. Based on the developer’s answers to those questions, the guidance will point the app developer toward detailed information about certain federal laws that might apply to the app. These include the FTC Act, the FTC’s Health Breach Notification Rule, the Health Insurance Portability and Accountability Act (HIPAA) and the Federal Food, Drug and Cosmetics Act (FD&C Act).

The guidance, which is maintained on the FTC’s website, links directly to each agency’s information about applicable laws. In addition, the FTC simultaneously released its own best practices guidance for compliance with the FTC Act, by building privacy and security into their apps.”5

Where mHealth is concerned, the FTC has focused on the claims companies have made about the effectiveness of their devices or apps. In late 2015, the FTC became more aggressive in its oversight of mobile health that may cause confusion on who the lead regulator is in this field. The FTC settled with a California-based app developer named Carrot Neurotechnology for $150,000.

The company pledged that their Ultimeyes app improved visual acuity, but the FTC stated that the company’s “promoters did not have the scientific evidence to support their claims that the app could improve users’ vision. Health-related apps can offer benefits to consumers, but the FTC will not hesitate to act when health-related claims are not based on sound science.”6

Why the FTC?

The above example illustrates there is a “Wild West” environment that exists, with no lead regulatory agency. There are many questions around why the FDA has remained silent. Some theories are that the FDA’s current regulatory structure has not caught up with a 21st century issue, such as mHealth.

Additionally, the FDA may not want to give the perception that it stifles innovation. Whatever the case, we could get further clarity on who regulates mHealth with a new Administration. On the legislative policy front, Congress currently has a few bills pending.

  • S 1101, titled the Medical Electronic Data Technology Enhancement for Consumers’ Health Act, or the MEDTECH Act, seeks to exempt certain software that promotes healthy lifestyles from being classified as a medical device subject to FDA oversight.
  • HR 2396, titled the SOFTWARE Act, sponsored by Congresswoman Marsha Blackburn (R-TN) is now part of the 21st Century CURES legislation. This bill seeks to define health software as software that does not acquire, process, or analyze data from an in vitro diagnostic device or signal acquisition system, is not an accessory or part of a medical device, and is not used to prevent disease in the transfusion of blood and blood components. Health software is exempted from FDA oversight, except for software that provides patient-specific recommendations, and poses a significant risk to patient safety.
  • HR 5906, titled the Wi-Fi Capable Mobile Devices Act of 2016, directs the FCC to issue rules to ensure that providers of mobile broadband Internet access service supported through the Lifeline Assistance Program offer mobile devices that are capable of receiving Wi-Fi or other wireless broadband signals using unlicensed spectrum, and sharing a mobile service connection with other compatible hardware or devices.

So, is mHealth something that specialty pharmacy can take advantage of? I believe so. First, it would be best to remain up to date on emerging mHealth technology to educate patients about the latest advances, as some approved products can have an immediate impact on their outcomes. For example, the Mount Sinai Health System in New York has launched an enterprise-wide platform for doctors to prescribe mobile health apps directly to patients.

The platform, RxUniverse, features a curated list of thousands of available health apps that have already been evaluated for their efficacy based on published literature. Israel-based medical device-maker TytoCare has received FDA 510(k) clearance for its digital stethoscope, which pairs with a smartphone to allow users to examine the ears, throat, skin, heart, lungs, and take their temperature.

Data are captured, stored, and shared via a cloud-based telehealth platform with video conferencing. Examinations can be done in real time, or in advance of a telehealth visit. A second suggestion is to be aware of the continued emergence of telemedicine. Telemedicine, an area that has been grouped in with mHealth, has shown strong signs of momentum on both the state and federal level, as policy makers recognize it could help rural patients achieve greater access to care.

Besides expanding the benefits of telemedicine to patients outside of rural areas, and the eventual sorting out of licensure concerns, the only major roadblock that exists in this area is how are providers that engage in telemedicine going to be reimbursed? Finally, mHealth can help specialty pharmacies increase medication adherence. Per the Network for Excellence in Health Innovation, medication nonadherence costs the health care system $290 billion annually.7

We see patients today who are not only more tech-savvy in their use of smartphones, tablets, and other connected devices, but are also more engaged than ever in trying to improve their own outcomes. By developing or utilizing apps, adherence tools, or how-to videos, you can help your patients achieve their personal goals. However, the key is to make sure that these digital resources are simple to use and provide the necessary incentives to keep your patients engaged long-term.

References

  • Greatcall; Is Mobile Healthcare the Future? http://www.greatcall.com/greatcall/lp/is-mobile-healthcare-the-future-infographic.aspx
  • HIMSS Definitions of mHealth http://www.himss.org/definitions-mhealth
  • FDA Mobile Medical Applications http://www.fda.gov/MedicalDevices/DigitalHealth/MobileMedicalApplications/ucm255978.htm
  • HealthIT.gov Overview of Federal Role in Mobile Health https://www.healthit.gov/policy-researchers-implementers/overview-federal-role-mobile-health
  • Federal Trade Commission FTC Releases New Guidance for Developers of Mobile Health Apps https://www.ftc.gov/news-events/press-releases/2016/04/ftc-releases-new-guidance-developers-mobile-health-apps
  • FTC; FTC Charges Marketers of ‘Vision Improvement’ App with Deceptive Claims https://www.ftc.gov/news-events/press-releases/2015/09/ftc-charges-marketers-vision-improvement-app-deceptive-claims
  • NEHI Bend the Curve; Improving Patient Medication Adherence: A $290 Billion Opportunity http://www.nehi.net/bendthecurve/sup/documents/Medication_Adherence_Brief.pdf