MaaS360™

The American Recovery and Reinvestment Act (ARRA) of 2009 contained billions of dollars aimed at moving U.S. healthcare onto an electronic platform. Much of it, described in the HITECH section of ARRA, is earmarked for incentive payments to physicians for demonstrating “meaningful use of certified EHRs,” paid out through Medicare and Medicaid. SaaS-based (software-as-aservice) Electronic Health Records (EHRs) are stepping onto the main stage as the most likely way that smaller and solo practices will be able to adopt EHRs in a meaningful way, in time for the 2011 ARRA/HITECH incentive monies.

SaaS-based software has also been referred to as cloudbased computing, web-based software, ASP-delivered software, and other terms (not all exactly the same from a technical standpoint, but often used interchangeably). So what is this new “hot buzz” all about and why is it important in the world of health IT?

Elimination of IT burden
SaaS-based software is Internet hosted, and accessed through an ordinary web browser. That means that the vendor, not the clinician, bears the burden of all the backend heavy lifting—servers, always-available access, security and safety of data, and backup of data are all issues that are removed from the clinician’s concern. This is a significant difference compared to legacy client/ server software, which requires a local installation onto a server, the maintenance of a secure local network (with perhaps a Citrix layer to access it from outside the confines of the office and network), and local policies for safety and security, as well as data backup. This generally requires an IT consultant, and adds “hidden” costs to the whole EHR installation.

Version control
Another limitation of a locally installed legacy client/server system is that, once it is installed, then it is “set.” Upgrades and bug fixes require the application of a patch, or installation of a new version. Often a fee (per upgrade or per year) is charged by the vendor for this support.

A SaaS-based EHR avoids this issue of “version control”— everyone, by definition, is on the same version. When changes or upgrades are deployed, everyone receives these changes on their next session login. From the standpoint of support, this is much easier, and feature updates, as well as bug fixes, can be managed quickly and deployed to everyone at once.

Customizable UI, per role, per specialty
One of the criticisms made about SaaS-based EHR products is that they are “one size fits all.” This may really limit the usability of a given product. Therefore, a customized, specialty-specific EHR may work better, given that the workflows faced by different specialties are, in fact, quite different.

Using modern technology, it is possible to capture many elements of a user upon login, and create a product that delivers a view (the User Interface, or UI) that can be very individualized. Within a given medical practice, different users have different needs, depending on their role—what a front-office check-in staff member and scheduler needs is different than a back-office nurse, which is different from what the clinician needs.

Similarly, what a family physician needs from an EHR may be quite different from what an orthopedist needs, or what an oncologist needs. Such workflow needs are beyond simply presenting a different set of charting templates (though that is certainly a start). Though not fully actualized currently, modern SaaS-based technology can move in this direction such that upon login to a SaaS-based product, the features presented by default (the UI) will vary depending on specialty, role, and individual preferences.

Learning curve
One of the biggest fears about moving from a paper medical record environment to an electronic one is the concern about a prolonged learning curve and a consequent dip in productivity. This dip in productivity can be significant and can last a long time (e.g., months). This is particularly concerning for small primary care practices that run very close to the margin. In a fee-for-service system, physicians have little time for much else other than processing high patient volumes through the office. Anything that introduces a slowdown in this frenetic pace is worrisome. Yet these precise practices are the ones that the Office of the National Coordinator (ONC) wants to get on board with EHRs. Even if the EHR is SaaS-based (minimal IT infrastructure costs), and free, the worry about work slowdown during the adoption phase is an obstacle to adoption and use of an EHR in a meaningful way. Thus, regardless of the style of EHR deployment, the burden is on EHR developers and vendors to create products that minimize the learning curve. Usability is paramount. Incorporation of user suggestions into the product is very important.

A lightweight, intuitive, responsive EHR is the goal for all of us who are creating the tools needed in order to achieve the transformation of U.S. healthcare from a paper-based legacy to a modern electronically connected one.

Robert Rowley, MD is the Chief Medical Officer at Practice Fusion, Inc.