Change is always a challenge, and how much more so when software is involved. Software implementation brings headaches from the software itself (installation, configuration, training) as well as the necessary adaptations in workflows (how work is accomplished) and work habits (how individuals do their jobs). One assumption underlying nearly all
EHR adoption has increased significantly since the passage of HITECH. With increased EHR use, as with any technology, there are bound to be unintended consequences. The same system that eliminates bad handwriting as a safety issue may introduce easily-misinterpreted screens or easily-misused default values. EHR-related malpractice cases are rising
The YAWL platform is a very sophisticated collection of tools that supports not only graphical modeling, but also enterprise-level workflow management capability. It offers a workflow engine, web services, and other features required for business process management. The graphical modeling environment is the focus of this series of posts. The
Having gone from writing FORTRAN programs on mainframes to creating web applications in the cloud, I have seen the computer revolution up close. Change has been the only constant, and yet innovations are consistently overlooked, especially by companies who are next on the endangered species list. Yahoo and Alta Vista
Obviously, I am an advocate of EHR use. Actually, tracking EHR implementation outcomes is somewhat of an obsession. For years, I have kept a folder on my desktop called “failed projects” that contains the woes, assessments, and post mortems of IT projects gone bad. Since HITECH, I’ve noticed something interesting.
In the last post, I alluded to the possibility of using software prototyping tools* as aids to EHR usability testing and product selection. While there are many types of prototyping tools, I have been most intrigued by those that allow the creation of interactive user interfaces. Using these tools, I
The last post focused on state and how this concept helps to portray the interactions between workflow participants. Movement through the Good Care, LLC workflow model followed the paths laid out by arcs connecting places and transitions. You undoubtedly noticed that places are static, and that transitions drive the action