We are now at the top layer of the clinical care system architecture. In this layer, the concern is how to best provide support for common clinical work needs such as collaboration or decision support. This is very different from EHR system designs inspired by paper charts where the goal
Clinical work consists of processes. Supporting clinical work with software requires support for processes. Process support can be passive or active. Paper charts are examples of passive support. Electronic resources may be passive as well. For example, an online textbook is a passive support. Over the course of training and
Last week’s post looked at the patient information component. This week I want to look at the electronic health record. EHR systems are offered as being both clinical care support systems and replacements for the paper chart, which are two very different things. Paper charts have non-clinical uses, and those
We gain understanding by asking good questions. Questions about even the most common, mundane things can yield wisdom and point the way to important discoveries. According to William Stukeley, Isaac Newton began his research into gravity because he wondered why apples always fell down and never sideways or up (1).
Creating software is hard. The entire process, from deciding that a piece of software is needed to implementation, requires analysis and problem-solving–every step. I was reminded of this reality anew when I began the latest round of coding for my seemingly mythical startup. There are so many decisions to make