Written by: Chuck Webster
Way back in 2009 I penned a research paper with a long and complicated title that could also have been, simply, Population Health Management and Business Process Management. In 2010 I presented it at MedInfo10 in Cape Town, Africa. Check out my travelogue!
Since then, some of what I wrote has become reality, and much of the rest is on the way. Before I dive into the weeds, let me set the stage. The Affordable Care Act added tens of millions of new patients to an already creaky and dysfunctional healthcare and health IT system. Accountable Care Organizations were conceived as virtual enterprises to be paid to manage the clinical outcome and costs of care of specific populations of individuals. Population Health Management has become the dominant conceptual framework for proceeding.
I looked at a bunch of definitions of population health management and created the following as a synthesis: “Proactive management of clinical and financial risks of a defined patient group to improve clinical outcomes and reduce cost via targeted, coordinated engagement of providers and patients across all care settings.”
You can see obvious places in this definition to apply trendy SMAC tech — social, mobile, analytics, and cloud — social, patient settings; mobile, provider and patient settings; analytics, cost and outcomes; cloud, across settings. But here I want to focus on the “targeted, coordinated.” Increasingly, it is self-developed and vendor-supplied care coordination platforms that target and coordinate, filling a gap between EHRs and day-to-day provider and patient workflows.
The best technology on which, from which, to create care coordination platforms is workflow technology, AKA business process management and adaptive/dynamic case management software. In fact, when I drill down on most sophisticated, scalable population health management and care coordination solutions, I usually find a combination of a couple things. Either the health IT organization or vendor is, in essence, reinventing the workflow tech wheel, or they embed or build on third-party BPM technology.
Let me direct you to my section Patient Class Event Hierarchy Intermediates Patient Event Stream and Automated Workflow in that MedInfo10 paper. First of all you have to target the right patients for intervention. Increasingly, ideas from Complex Event Processing are used to quickly and appropriately react to patient events. A Patient Class Event Hierarchy is a decision tree mediating between low-level events (patient state changes) and higher-level concepts clinical concepts such as “on-protocol,” “compliant”, “measured”, and “controlled.”
Examples include patients who aren’t on protocol but should be, aren’t being measured but should be, or whose clinical values are not controlled. Execution of appropriate automatic policy-based workflows (in effect, intervention plans) moves patients from off-protocol to on-protocol, non-compliance to compliance, unmeasured to measured, and from uncontrolled to controlled state categories.
Population health management and care coordination products and services may use different categories, terminology, etc. But they all tend to focus on sensing and reacting to untoward changes in patient state. But simply detecting these changes is insufficient. These systems need to cause actions. And these actions need to be monitored, managed, and improved, all of which are classic sterling qualities of business process management software systems and suites.
I’m reminded of several tweets about Accountable Care Organization IT systems I display during presentations. One summarizes an article about ACOs. The other paraphrases an ACO expert speaking at a conference. The former says ACOs must tie together many disparate IT systems. The later says ACOs boil down to lists: actionable lists of items delivered to the right person at the right time. If you put these requirements together with system-wide care pathways delivered safely and conveniently to the point of care, you get my three previous blog posts on interoperability, usability, and safety.
I’ll close here with my seven advantages of BPM-based care coordination technology. It…
- More granularly distinguishes workflow steps
- Captures more meaningful time-stamped task data
- More actively influences point-of-care workflow
- Helps model and understand workflow
- Better coordinates patient care task handoffs
- Monitors patient care task execution in real-time
- Systematically improves workflow effectiveness & efficiency
Distinguishing among workflow steps is important to collecting data about which steps provide value to providers and patients, as well as time-stamps necessary to estimate true costs. Further, since these steps are executed, or at least monitored, at the point-of-care, there’s more opportunity to facilitate and influence at the point-of-care. Modeling workflow contributes to understanding workflow, in my view an intrinsically valuable state of affairs. These workflow models can represent and compensate for interruptions to necessary care task handoffs. During workflow execution, “enactment” in BPM parlance, workflow state is made transparently visible. Finally, workflow data “exhaust” (particularly times-stamped evidence-based process maps) can be used to systematically find bottlenecks and plug care gaps.
In light of the fit between complex event processing detecting changes in patient state, and BPM’s automated, managed workflow at the point-of-care, I see no alternative to what I predicted in 2010. Regardless of whether it’s rebranded as care or healthcare process management, business process management is the most mature, practical, and scalable way to create the care coordination and population health management IT systems required by Accountable Care Organizations and the Affordable Care Act. A bit dramatically, I’d even say business process management’s royal road to healthcare runs through care coordination.
This was my fifth and final blog post in this series on healthcare and workflow technology solicited by John Lynn for this week that he’s on vacation. Here was the outline:
- Five Guest Blog Posts On EHR & HIT Workflow, Usability, Safety, Interoperability and Population Health
- Interoperable Health IT and Business Process Management: The Spider In The Web
- Usable EHR Workflow Is Natural, Consistent, Relevant, Supportive and Flexible
- Patient Safety And Process-Aware Information Systems: Interruptions, Interruptions, Interruptions!
- Population Health Management and Business Process Management
If you missed one of my previous posts, I hope you’ll still check it out. Finally, thank you John, for allowing to me temporarily share your bully pulpit.