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 back-end heavy lifting – servers, always-available access, security and safety of data, and backup of data are all issues that are removed from the clinician.

This is a significant difference compared to legacy client/server software, which require 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 the need to hire an IT consultant, and adds “hidden” cost to the whole EHR installation.

An interesting side-note here is that the computers which run the software (the clients) can have less expensive operating systems with a SaaS approach. In a local area network (a LAN), all the workstations that access the local server need to be able to become members of a Domain, which is established by the server. Windows (any version) Professional version needs to be installed; the Home versions of the operating system is not able to join Domains. There is generally about a $100 additional cost for the Professional version of operating systems, compared to Home versions. With a SaaS-based EHR, all one needs is a browser and an internet connection – joining a domain is not required. Therefore, any off-the-shelf computer with a pre-installed Home version of the operating system will work.

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 (i.e. income stream) can be significant (e.g. 20%) and can last a long time (e.g. months). This is especially concerning for small primary care practices that run very close to the margin – small perturbations in income stream can mean running at a loss. In a fee-for-service system, life as a primary care physician is often a mad hamster-wheel life, with little time for much else other than processing high patient volumes through the office (worthy of an entire tangential blog topic thread). 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 slow-down 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 us of 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.


We're not around right now. But you can send us an email and we'll get back to you, asap.


©2019 EHRchain Partners LLC

Log in with your credentials

Forgot your details?