Let’s agree for the moment that workflows can be parsed into two groups—Easily Repeatable Processes (ERPs) and Barely Repeatable Processes (BRPs). (I read about this concept online via Sigurd Rinde.)
An example of an ERP industry is manufacturing. Healthcare, in many respects, is a BRP industry. BRPs are characterized by collaborative events, exception handling, ad-hoc activities, extensive loss of information, little knowledge acquired and reused, and untrustworthy processes. They involve unplanned events, knowledge work, and creative work.
ERPs are the easy ones to map, model, and structure. They are perfect for large enterprise software vendors like Oracle and SAP whose products include offerings like ERP, SCM, PLM, SRM, CRM.
How can you tell what type of process you are trying to incorporate in your EHR? Here’s one way. If the person standing next to you at Starbucks could watch you work and accurately describe the process, it’s probably an ERP.
So, why discuss ERP and BRP in the same sentence with EHR? The reason is simple. The taxonomy of most, if not all EHR systems, is that they are designed to support an ERP business model. Healthcare providers are faced with the quintessential square peg in a round hole conundrum; trying to get BRPs into an ERP type system. Since much of the ROI in the EHR comes from being able to redesign the workflows, I think either the “R” will be sacrificed, or the “I” will be much higher than planned.
What do you think?
Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy
1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942