Government  Health IT
TwitterFacebookLinkedIn
  • Home
  • Topics
    • ARRA/Stimulus
    • Election 2012
    • Electronic Health Record
    • ePrescribing
    • Health Information Exchange (HIE)
    • Medicaid
    • Medicare
    • Military Health
    • Mobile/ Wireless
    • NHIN
    • Policy & Legislation
    • Population Health
    • Privacy and Security
    • Quality and Safety
    • Telehealth
    • Workforce Management
  • Issues
    • Sept/Oct 2011
    • July/August 2011
    • May/June 2011
    • March/April 2011
    • Jan/Feb 2011
    • Nov/Dec 2010
  • Webinars
    • On Demand Webinars
  • White Papers
  • Blog
  • Events
  • Jobs
  • RSS
  • Slideshows
  • Videos
  • Newsletters
  • Advertise
  • LOGIN
  • REGISTER
  • SUBSCRIBE
Home » News » Mobile/ Wireless | Telehealth
Receive News
By Email

  • del.icio.us
  • Digg
  • Facebook
  • Google
  • Reddit
  • StumbleUpon
  • RSS Icon
  

FDA lays out regulation of certain mobile medical apps

July 19, 2011 | Mary Mosquera

Suggested Content

  • VA shifts tablet initiative into higher gear
  • 5 of the most disruptive mobile health technologies today
  • Info security is critical when VA allows iPhone, iPad
  • VA will allow more mobile devices Oct. 1
  • Physicians go mobile
  • Physicians go mobile
  • ONC reveals mobile data best practice initiative
  • How to turn a tablet into a security tool
  • Year-end: 3 security threats and 4 tips for protecting health data

Related Resources

  • The Power of User Virtualization: Meeting Meaningful Use, Optimizing IT and Clinical Productivity
  • Best Practices to Deploy ECM Technologies: Ensure Decisions are Made Based on all the Information, not a Portion of it
  • Mobility and Population Health: A Clinical Case Study on the Role of Mobile Devices-The mCare Project
  • Best Practices for the Implementation of Telepresence in a Telehealth Solution
  • Ten Things to Ask Your SAAS Vendor Before Entering the Cloud

The Food and Drug Administration has proposed regulation of some medical applications that run on smartphones and other mobile computing devices that could affect the operations of other medical devices already under its governance.

The agency’s draft guidance released July 19 outlines its “current thinking” and focuses on a small subset of mobile medical apps because they can influence the performance or functionality, and potentially the safety, of currently regulated medical devices.

The mobile medical apps that FDA has in mind are those used as accessory to a medical device already regulated by the agency, such as one that enables a provider to make a diagnosis by viewing a medical image from a picture archiving and communication system (PACS) on a smartphone or other mobile device.

The other set of apps under FDA’s scrutiny are those that transform a mobile communications device into a regulated medical device by using attachments, sensors or other devices. An example of this is an attachment of electrocardiograph (ECG) electrodes to a mobile platform to measure, store and display ECG signals to detect abnormal heart rhythms or if a patient is experiencing a heart attack. 

FDA said that its oversight consideration does not include mobile apps that perform the functionality of an electronic health record system or personal health record system.

The agency said it seeks feedback on its oversight approach. Once the proposed guidance is published, the public may comment for 90 days. FDA will update the guidance based on that feedback. 

Mobile medical apps perform a variety of functions, including monitoring calorie intake, helping people manage healthy weight, and allowing physicians to view a patient’s radiology images on their mobile communications device. The use of mobile medical apps on smart phones and tablets is revolutionizing healthcare delivery, said Dr. Jeffrey Shuren, director of the FDA’s Center for Devices and Radiological Health.

“Our draft approach calls for oversight of only those mobile medical apps that present the greatest risk to patients when they don’t work as intended,” he said. FDA will continue to evaluate how these technologies might improve health care, reduce potential medical mistakes and protect patients.

Mobile medical apps could pose risks due to the unique characteristics of their platform. For example, the 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 said it intends to take these limitations into account in assessing the appropriate regulatory oversight for these products.

[Related: FCC, FDA pave the way for wireless medical devices.]

Examples of apps that FDA said are not part of its oversight consideration include electronic "copies" of the Physician’s Desk Reference and other medical textbooks, teaching aids or reference materials to provide clinicians with training or reinforce training previously received. However, mobile apps that allow the user to input patient-specific information along with reference material to automatically diagnose a disease or condition are considered mobile medical apps.

FDA also will not oversee mobile apps that are used to develop or maintain general health and wellness, such as dietary logs and appointment reminders, and those that automate general office operations.

Under FDA regulation, a manufacturer would register annually and list the mobile medical apps being marketed so the agency knows who is marketing what. The manufacturer also must supply certain labeling information with the product. Mobile medical app makers would have to meet quality system requirements to assure that the products are safe and effective and establish consistent methods to design, produce, and distribute their devices or software.

Finally, the mobile medical app maker would report to FDA information about serious adverse incidents related to use of their product.
 

Related Topics:
  • Online Only
  • Mobile/ Wireless
  • Telehealth
  • Person Career
  • Quotation
  • computing
  • healthcare
  • Federal Communications Commission
  • Food and Drug Administration
  • http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/ucm263280.htm
  • http://www.govhealthit.com/news/fda-fcc-accelerate-wireless-device-path-market
  • http://www.govhealthit.com/news/hhs-panel-considers-ehr-risks-reports-detail-injuries-deaths&nbsp
  • Jeffrey Shuren
  • mobile computing
  • mobile device
  • smart phones
  • Smartphone
  • smartphones

Reader Comments (1)Login to Post a Comment

Jesse_EngAmer says: Dangerous Regulation
July 19, 2011 | 12:41PM GMT

I don’t remember the first amendment being repealed do you?

Within the draft exists an affront on the constitutional protection of the Internet granted by the Supreme Court in 1997, a contradiction, a rather worrisome clause that sets a dangerous precedent and removal of funding from more pressing matters.

1) Many apps are extensions of mobile sites and Websites. Like the unenforced 1989 medical software bill, the FDA is looking to enforce the 1996 bill outlining regulation of online medical information
2) Some apps to be regulated use algorithms to compute specific patient treatment, when electronic textbooks available on mobile platforms with the same algorithms will not be regulated.
3) One clause states “when the intended use of a mobile app is for the diagnosis of disease or other conditions” the app will be regulated. Many doctors consult medical apps. Internet and social media have often led to a diagnosis a doctor could not come up with.
4) The FDA cannot afford to carry out the 2011 Food Safety and Modernization Act (FSMA).  The FDA stated that “Half of all medical devices used in this country are imported” and that “it would take 9 years just to inspect every high-priority pharmaceutical facility alone” ignoring those of lower priority. The money spent regulating mobile apps could be put to much better use ensuring the safety of a much higher percentage of medical devices.

Most Popular

Latest Headlines
Most Popular
  • If HHS delays ICD-10 long enough, could the U.S. adopt ICD-11 instead?
  • AHIMA, HIMSS reassert ICD-10 vigilance
  • HHS Secretary Kathleen Sebelius announces intent to delay ICD-10 compliance date
  • HIMSS takes over mHealth Summit
  • Sebelius says $3.1B paid out for EHR incentives
  • CMS expected to release stage 2 proposed rule Thursday
  • Stage 2 ready for primetime
  • AHIMA: Time to think about training - and keeping - your coders
  • AHRQ plans registry of patient registries
  • S&I's Doug Fridsma on NwHIN enabling the next Amazon, eBay or Facebook

WEBINARS AND WHITE PAPERS

  • ON DEMAND WEBINARS
    Improving Care Coordination with Online Services
  • WHITE PAPERS
    Event Log Management & Compliance Best Practices: For Government & Healthcare Industry Sectors
  • ON DEMAND WEBINARS
    VMware View for Healthcare: Improve Clinician Workflow
  • ON DEMAND WEBINARS
    Better Outcomes in Healthcare IT | Key Lessons from an IT Leader
  • ON DEMAND WEBINARS
    Best Practices to Deploy ECM Technologies: Ensure Decisions are Made Based on all the Information, not a Portion of it
More Resources
Syndicate content

HIMSS JOBMINE

  • Manager, Specialty Education - HIMSS - Chicago, IL
  • Implementation Consultants - Peer Consulting - USA/Canada
  • SW engineer - Healarium - Boston, MA
  • Vice President & Chief Information Officer (VP/CIO) - Greater Hudson Valley Health System - Middletown, NY
  • Director of Measurement Services - URAC - Washington, DC
more jobs
Follow Government Health IT on TwitterFan Government Health IT on FacebookJoin Government Health IT on LinkedInRSS Subscriptions
Digital EditionBlogEvents
JobsMobile SiteMobile App
 
Healthcare IT NewsHealthcare Finance News EHRWatch Healthcare Payer News HITECHWatch ICD10Watch mHIMSS PhysBizTech NHINWatch
©2012 MedTech Media Government Health IT is a publication of MedTech Media
Subscribe Advertise About Us Privacy Policy