Back in the mid-90s, doctors who bought EHR systems were trying to solve specific problems.   These early adopters would listen as I listed the many ways that EHR systems would change their lives, acknowledge the issues I raised, then buy an EHR anyway.   More often than not, however,Continue Reading

No, the title is not a mistake. It simply reflects what I have come to realize over the last month or so. Innovation is about solving problems and, as the saying goes, “Necessity is the mother of invention.”   Misery is a source of innovation, and the loudest cries about EHRContinue Reading

Early on in the development process, most of the information gathered from future users consists of documents (e.g., forms, policy/procedure) and interview data (e.g., feature descriptions, desired functions, specific dislikes, wish-list items, etc.). As a software designer using object-oriented design, the next major step in making this information actionable isContinue Reading

This is the longest period I have ever gone without writing a post.  The long pause was necessary because of changes in personal goals and the world at large.   EHR Science has covered a range of topics over the years—everything from EHR market trends to discrete mathematics.   TopicsContinue Reading

Traditionally, clinical software has been organized around data.  The reason for this is the paper chart, which is a process-agnostic information source.  At the outset of creating a new software product, this question has to be answered early on: Is this a data-focused system or a process-focused one?  The architecturalContinue Reading