This was going to be a five year relook at Practice Fusion. Back then, I’d written a critical review saying I wouldn’t be a PF consultant. Going over PF now, I found it greatly changed. For example, I criticized it s not having a shared task list. Now, it does. Starting to trace other functions, a question suddenly hit me. Why did I think an EHR should have a shared task list or any other workflow function for that matter?
It’s a given that an EHR is supposed to record and retrieve a patient’s medical data. Indeed, if you search for the definition of an EHR, you’ll find just that. For example, Wikipedia defines it this way:
An electronic health record (EHR), or electronic medical record (EMR), refers to the systematized collection of patient and population electronically-stored health information in a digital format. These records can be shared across different health care settings. Records are shared through network-connected, enterprise-wide information systems or other information networks and exchanges. EHRs may include a range of data, including demographics, medical history, medication and allergies, immunization status, laboratory test results, radiology images, vital signs, personal statistics like age and weight, and billing information.
Other definitions, such as HIMSS are similar, but add another critical element, workflow:
The EHR automates and streamlines the clinician’s workflow.
Is this a good or even desirable thing? Now, before Chuck Webster shoots out my porch lights, that doesn’t mean I’m anti workflow. However, I do ask what are workflow features doing in an EHR?
In EHRs early days, vendors realized they couldn’t drop one in a practice like a fax machine. EHRs were disruptive and not always in a good way. They often didn’t play well with practice management systems or the hodgepodge of forms, charts and lists they were replacing.
As a result, vendors started doing the workflow archeology and devising new ones as part of their installs. Over time, EHRs vendors started touting how they could reform not just replace an old system.
Hospitals were a little different. Most had IT staff that could shoehorn a new system into their environment. However, as troubled hospital EHR rollouts attest, they rarely anticipated the changes that EHRs would bring about.
Adding workflow functions to an EHR may have caused what my late brother called a “far away” result. That is, the farther away you were from something, the better it looked. With EHR workflow tools, the closer you get to their use, the more problems you may find.
EHRs are designed for end users. Adding workflow tools to these assumes that the users understand workflow dynamics and can use them accordingly. Sometimes this works well, but just as often the functions may not be a versatile as the situation warrants. Just ask the resident who can’t find the option they really need.
I think the answer to EHR workflow functions is this. They can be nice to have, like a car’s backup camera. However, having one doesn’t make you a good driver. Having workflow functions shouldn’t fool you into thinking that’s all workflow requires.
The only way to determine what’s needed is by doing a thorough, requirements analysis, working closely with users and developing the necessary workflow systems.
A better approach would be a workflow system that embeds its features in an EHR. That way, the EHR could fit more seamlessly its environment, rather than the other way around.
This post originally appeared at EMRandEHR.com.