Finally…FDASIA Health IT Regulation Report Released

15 April 2014 Health Care Law Today Blog

The U.S. Food and Drug Administration (FDA), along with HHS’ Office of the National Coordinator for Health Information Technology (ONC) and the Federal Communications Commission (FCC, together with FDA and ONC, the “Agencies”) published their long-awaited report, FDASIA Health IT Report: Proposed Strategy and Recommendations for a Risk-Based Framework. The report, mandated by the Food and Drug Administration Safety and Innovation Act (FDASIA), proposes strategies and recommendations for a risk-based framework to regulate health information technology (HIT).

The agencies are seeking public comment for 90 days following publication of the report on April 3, 2014.

The proposed HIT regulatory scheme seeks to strike a balance between patient safety and the rapid innovation of new HIT that has the potential to offer tremendous benefits to patients and providers. As anticipated, the proposed strategy reiterates a critical point made in the FDA’s final guidance for mobile medical applications, published last year — that the FDA will focus on functionality of the HIT in question, and not on the platforms or devices on which they run.

Three-Tiered Classification of HIT

A main feature of the report is the introduction of a three-tiered classification of HIT based on functionality and the level of risk of patient harm.

  • First-tier – products with administrative HIT functions (e.g. billing, scheduling or claims processing HIT).
  • Second-tier – products with health management HIT functions (e.g. health information and data management, medication management, provider order entry and most clinical decision support software).
  • Third-tier – products with medical device HIT functions (e.g. computer-aided detection software, bedside monitor/alarm software or radiation treatment software).

The Agencies propose no regulation of first-tier products (administrative HIT) because such products pose little or no risk to patient safety. Similarly, the agencies propose decreased oversight of second-tier products (health management HIT) if such products meet the definition of “device” under the Federal Food, Drug, and Cosmetic Act. The agencies do, however, propose relying primarily on ONC-coordinated activities and private-sector capabilities to leverage quality management principles, industry standards and best practices to regulate second-tier products. Lastly, the proposed regulatory scheme allows the FDA to continue to regulate third-tier products (medical device HIT) because such products pose heightened risks to patients if they do not perform as intended.

The proposed framework also calls for the creation of a public-private HIT Safety Center that would help set standards and facilitate learning and sharing of best practice ideas and information focused on quality and patient safety.

Report Comes Amid an Already Clouded HIT Regulatory Environment

Although there has been genuine interest in the proposed scheme, the Agencies recommendations have not won universal acclaim and the release of the report comes amid an already clouded HIT regulatory environment. As the regulators attempt to develop a coordinated approach, there are two pieces of pending legislation on capitol hill, the PROTECT Act and the SOFTWARE Act, both of which seek to limit the FDA’s ability to regulate low-risk HIT by removing third-tier HIT (medical device HIT) from the scope of the FDA’s regulatory authority. While some applaud the publication of the FDASIA report, many critics argue that it is too little, too late and call for clearer, less nuanced regulatory guidance to allow the industry to continue to innovate with clear expectations. Needless to say, this will be a particularly interesting area to watch as it develops over the coming months and years.

This blog is made available by Foley & Lardner LLP (“Foley” or “the Firm”) for informational purposes only. It is not meant to convey the Firm’s legal position on behalf of any client, nor is it intended to convey specific legal advice. Any opinions expressed in this article do not necessarily reflect the views of Foley & Lardner LLP, its partners, or its clients. Accordingly, do not act upon this information without seeking counsel from a licensed attorney. This blog is not intended to create, and receipt of it does not constitute, an attorney-client relationship. Communicating with Foley through this website by email, blog post, or otherwise, does not create an attorney-client relationship for any legal matter. Therefore, any communication or material you transmit to Foley through this blog, whether by email, blog post or any other manner, will not be treated as confidential or proprietary. The information on this blog is published “AS IS” and is not guaranteed to be complete, accurate, and or up-to-date. Foley makes no representations or warranties of any kind, express or implied, as to the operation or content of the site. Foley expressly disclaims all other guarantees, warranties, conditions and representations of any kind, either express or implied, whether arising under any statute, law, commercial use or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Foley or any of its partners, officers, employees, agents or affiliates be liable, directly or indirectly, under any theory of law (contract, tort, negligence or otherwise), to you or anyone else, for any claims, losses or damages, direct, indirect special, incidental, punitive or consequential, resulting from or occasioned by the creation, use of or reliance on this site (including information and other content) or any third party websites or the information, resources or material accessed through any such websites. In some jurisdictions, the contents of this blog may be considered Attorney Advertising. If applicable, please note that prior results do not guarantee a similar outcome. Photographs are for dramatization purposes only and may include models. Likenesses do not necessarily imply current client, partnership or employee status.

Related Services

Insights