Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and HIPAA for FREE!!

Are You a Healthcare Data Hoarder?

Posted on October 16, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I’m thinking I need to start a new healthcare reality TV show called “Healthcare Data Hoarders.” We’ll go into healthcare institutions (after signing our HIPAA lives away), and take a look through all the data a healthcare organization is storing away.

My guess is that we wouldn’t have to look very far to find some really amazing healthcare data hoarders. The healthcare data hoarding I see happening in comes in two folds: legacy systems and data warehouses.

Legacy Systems – You know the systems I’m talking about. They’re the ones stored under a desk in the back of radiology. The software is no longer being updated. In fact, the software vendor is often not even around anymore. However, for some reason you think you’re going to need the data off that system that’s 30 years old and only one person in your entire organization knows how to access the legacy software. Yes, I realize there are laws that require healthcare organizations to “hoard” data to some extent. However, many of these legacy systems are well past those legal data retention requirements.

Data Warehouses – These come in all shapes and sizes and for this hoarding article let me suggest that an EHR is kind of a data warehouse (yes, I’m using a really broad definition). Much like a physical hoarder, I see a lot of organizations in healthcare that are gathering virtual piles of data for which they have no use and will likely never find a way to use it. Historically, a data warehouse manager’s job is to try and collect, normalize, and aggregate all of the healthcare organizations data into one repository. Yes, the data warehouse manager is really the Chief Healthcare Data Hoarder. Gather and protect and and all data you can find.

While I love the idea that we’re collecting data that can hopefully make healthcare better, just collecting data doesn’t do anything to improve healthcare. In fact, it can often retard efforts to leverage healthcare data to improve health. The problem is that the healthcare data that can be leveraged for good is buried under all of this useless data. It takes so much effort to sift through the junk data that people just stop before they even get started.

Are you collecting data and not doing anything with it? I challenge you to remedy that situation.

Is your healthcare organization a healthcare data hoarder?

Population Health Management and Business Process Management

Posted on June 13, 2014 I Written By

Chuck Webster, MD, MSIE, MSIS has degrees in Accountancy, Industrial Engineering, Intelligent Systems, and Medicine (from the University of Chicago). He designed the first undergraduate program in medical informatics, was a software architect in a hospital MIS department, and also VP and CMIO for an EHR vendor for over a decade. Dr. Webster helped three healthcare organizations win the HIMSS Davies Award and is a judge for the annual Workflow Management Coalition Awards for Excellence in BPM and Workflow and Awards for Case Management. Chuck is a ceaseless evangelist for process-aware technologies in healthcare, including workflow management systems, Business Process Management, and dynamic and adaptive case management. Dr. Webster tweets from @wareFLO and maintains numerous websites, including EHR Workflow Management Systems (http://chuckwebster.com), Healthcare Business Process Management (http://HCBPM.com) and the People and Organizations improving Healthcare with Health Information Technology (http://EHRworkflow.com). Please join with Chuck to spread the message: Viva la workflow!

This is my fifth and final of five guest blog posts covering Health IT and EHR Workflow.

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:

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.


Patient Safety And Process-Aware Information Systems: Interruptions, Interruptions, Interruptions!

Posted on June 12, 2014 I Written By

Chuck Webster, MD, MSIE, MSIS has degrees in Accountancy, Industrial Engineering, Intelligent Systems, and Medicine (from the University of Chicago). He designed the first undergraduate program in medical informatics, was a software architect in a hospital MIS department, and also VP and CMIO for an EHR vendor for over a decade. Dr. Webster helped three healthcare organizations win the HIMSS Davies Award and is a judge for the annual Workflow Management Coalition Awards for Excellence in BPM and Workflow and Awards for Case Management. Chuck is a ceaseless evangelist for process-aware technologies in healthcare, including workflow management systems, Business Process Management, and dynamic and adaptive case management. Dr. Webster tweets from @wareFLO and maintains numerous websites, including EHR Workflow Management Systems (http://chuckwebster.com), Healthcare Business Process Management (http://HCBPM.com) and the People and Organizations improving Healthcare with Health Information Technology (http://EHRworkflow.com). Please join with Chuck to spread the message: Viva la workflow!

This is my fourth of five guest blog posts covering Health IT and EHR Workflow.

When you took a drivers education class, do you remember the importance of mental “awareness” to traffic safety? Continually monitor your environment, your car, and yourself. As in traffic flow, healthcare is full of work flow, and awareness of workflow is the key to patient safety.

First of all, the very act of creating a model of work to be done forces designers and users to very carefully think about and work through workflow “happy paths” and what to do when they’re fallen off. A happy path is a sequence of events that’s intended to happen, and, if all goes well, actually does happen most of the time. Departures from the Happy Path are called “exceptions” in computer programming parlance. Exceptions are “thrown”, “caught”, and “handled.” At the level of computer programming, an exception may occur when data is requested from a network resource, but the network is down. At the level of workflow, an exception might be a patient no-show, an abnormal lab value, or suddenly being called away by an emergency or higher priority circumstance.

Developing a model of work, variously called workflow/process definition or work plan forces workflow designers and workflow users to communicate at a level of abstraction that is much more natural and productive than either computer code or screen mockups.

Once a workflow model is created, it can be automatically analyzed for completeness and consistency. Similar to how a compiler can detect problems in code before it’s released, problems in workflow can be prevented. This sort of formal analysis is in its infancy, and is perhaps most advanced in healthcare in the design of medical devices.

When workflow engines execute models of work, work is performed. If this work would have otherwise necessarily been accomplished by humans, user workload is reduced. Recent research estimates a 7 percent increase in patient mortality for every additional patient increase in nurse workload. Decreasing workload should reduce patient mortality by a similar amount.

Another area of workflow technology that can increase patient safety is process mining. Process mining is similar, by analogy, to data mining, but the patterns it extracts from time stamped data are workflow models. These “process maps” are evidence-based representations of what really happens during use of an EHR or health IT system. Process maps can be quite different, and more eye opening, than process maps generated by asking participants questions about their workflows. Process maps can show what happens that shouldn’t, what doesn’t happen than should, and time-delays due to workflow bottlenecks. They are ideal tools to understand what happened during analysis of what may have caused a possibly system-precipitated medical error.

Yet another area of particular relevance of workflow tech to patient safety is the fascinating relationship between clinical pathways, guidelines, etc. and workflow and process definitions executed by workflow tech’s workflow engines. Clinical decision support, bringing the best, evidence-based medical knowledge to the point-of-care, must be seamless with clinical workflow. Otherwise, alert fatigue greatly reduces realization of the potential.

There’s considerable research into how to leverage and combine representations of clinical knowledge with clinical workflow. However, you really need a workflow system to take advantage of this intricate relationship. Hardcoded, workflow-oblivious systems? There’s no way to tweak alerts to workflow context: the who, what, why, when, where, and how of what the clinical is doing. Clinical decision support will not achieve wide spread success and acceptance until it can be intelligently customized and managed, during real-time clinical workflow execution. This, again, requires workflow tech at the point-of-care.

I’ve saved workflow tech’s most important contribution to patient safety until last: Interruptions.

An interruption–is there anything more dreaded than, just when you are beginning to experience optimal mental flow, a higher priority task interrupts your concentration. This is ironic, since so much of work-a-day ambulatory medicine is essentially interrupt-driven (to borrow from computer terminology). Unexpected higher priority tasks and emergencies *should* interrupt lower priority scheduled tasks. Though at the end of the day, ideally, you’ve accomplished all your tasks.

In one research study, over 50% of all healthcare errors were due to slips and lapses, such as not executing an intended action. In other words, good clinical intentions derailed by interruptions.

Workflow management systems provide environmental cues to remind clinical staff to resume interrupted tasks. They represent “stacks” of tasks so the entire care team works together to make sure that interrupted tasks are eventually and appropriately resumed. Workflow management technology can bring to clinical care many of the innovations we admire in the aviation domain, including well-defined steps, checklists, and workflow tools.

Stay tuned for my fifth, and final, guest blog post, in which I tackle Population Health Management with Business Process Management.


Usable EHR Workflow Is Natural, Consistent, Relevant, Supportive and Flexible

Posted on June 11, 2014 I Written By

Chuck Webster, MD, MSIE, MSIS has degrees in Accountancy, Industrial Engineering, Intelligent Systems, and Medicine (from the University of Chicago). He designed the first undergraduate program in medical informatics, was a software architect in a hospital MIS department, and also VP and CMIO for an EHR vendor for over a decade. Dr. Webster helped three healthcare organizations win the HIMSS Davies Award and is a judge for the annual Workflow Management Coalition Awards for Excellence in BPM and Workflow and Awards for Case Management. Chuck is a ceaseless evangelist for process-aware technologies in healthcare, including workflow management systems, Business Process Management, and dynamic and adaptive case management. Dr. Webster tweets from @wareFLO and maintains numerous websites, including EHR Workflow Management Systems (http://chuckwebster.com), Healthcare Business Process Management (http://HCBPM.com) and the People and Organizations improving Healthcare with Health Information Technology (http://EHRworkflow.com). Please join with Chuck to spread the message: Viva la workflow!

This is my third of five guest blog posts covering Health IT and EHR Workflow.

Workflow technology has a reputation, fortunately out of date, for trying to get rid of humans all together. Early on it was used for Straight-Through-Processing in which human stockbrokers were bypassed so stock trades happened in seconds instead of days. Business Process Management (BPM) can still do this. It can automate the logic and workflow that’d normally require a human to download something, check on a value and based on that value do something else useful, such as putting an item in a To-Do list. By automating low-level routine workflows, humans are freed to do more useful things that even workflow automation can’t automate.

But much of healthcare workflow requires human intervention. It is here that modern workflow technology really shines, by becoming an intelligent assistant proactively cooperating with human users to make their jobs easier. A decade ago, at MedInfo04 in San Francisco, I listed the five workflow usability principles that beg for workflow tech at the point-of-care.

Consider these major dimensions of workflow usability: naturalness, consistency, relevance, supportiveness, and flexibility. Workflow management concepts provide a useful bridge from usability concepts applied to single users to usability applied to users in teams. Each concept, realized correctly, contributes to shorter cycle time (encounter length) and increased throughput (patient volume).

Naturalness is the degree to which an application’s behavior matches task structure. In the case of workflow management, multiple task structures stretch across multiple EHR users in multiple roles. A patient visit to a medical practice office involves multiple interactions among patients, nurses, technicians, and physicians. Task analysis must therefore span all of these users and roles. Creation of a patient encounter process definition is an example of this kind of task analysis, and results in a machine executable (by the BPM workflow engine) representation of task structure.

Consistency is the degree to which an application reinforces and relies on user expectations. Process definitions enforce (and therefore reinforce) consistency of EHR user interactions with each other with respect to task goals and context. Over time, team members rely on this consistency to achieve highly automated and interleaved behavior. Consistent repetition leads to increased speed and accuracy.

Relevance is the degree to which extraneous input and output, which may confuse a user, is eliminated. Too much information can be as bad as not enough. Here, process definitions rely on EHR user roles (related sets of activities, responsibilities, and skills) to select appropriate screens, screen contents, and interaction behavior.

Supportiveness is the degree to which enough information is provided to a user to accomplish tasks. An application can support users by contributing to the shared mental model of system state that allows users to coordinate their activities with respect to each other. For example, since a EMR  workflow system represents and updates task status and responsibility in real time, this data can drive a display that gives all EHR users the big picture of who is waiting for what, for how long, and who is responsible.

Flexibility is the degree to which an application can accommodate user requirements, competencies, and preferences. This obviously relates back to each of the previous usability principles. Unnatural, inconsistent, irrelevant, and unsupportive behaviors (from the perspective of a specific user, task, and context) need to be flexibly changed to become natural, consistent, relevant, and supportive. Plus, different EHR users may require different BPM process definitions, or shared process definitions that can be parameterized to behave differently in different user task-contexts.

The ideal EHR/EMR should make the simple easy and fast, and the complex possible and practical. Then ,the majority/minority rule applies. A majority of the time processing is simple, easy, and fast (generating the greatest output for the least input, thereby greatly increasing productivity). In the remaining minority of the time, the productivity increase may be less, but at least there are no showstoppers.

So, to summarize my five principles of workflow usability…

Workflow tech can more naturally match the task structure of a physician’s office through execution of workflow definitions. It can more consistently reinforce user expectations. Over time this leads to highly automated and interleaved team behavior. On a screen-by-screen basis, users encounter more relevant data and order entry options. Workflow tech can track pending tasks–which patients are waiting where, how long, for what, and who is responsible–and this data can be used to support a continually updated shared mental model among users. Finally, to the degree to which an EHR or health IT system is not natural, consistent, relevant, and supportive, the underlying flexibility of the workflow engine and process definitions can be used to mold workflow system behavior until it becomes natural, consistent, relevant, and supportive.

Tomorrow I’ll discuss workflow technology and patient safety.


Interoperable Health IT and Business Process Management: The Spider In The Web

Posted on June 10, 2014 I Written By

Chuck Webster, MD, MSIE, MSIS has degrees in Accountancy, Industrial Engineering, Intelligent Systems, and Medicine (from the University of Chicago). He designed the first undergraduate program in medical informatics, was a software architect in a hospital MIS department, and also VP and CMIO for an EHR vendor for over a decade. Dr. Webster helped three healthcare organizations win the HIMSS Davies Award and is a judge for the annual Workflow Management Coalition Awards for Excellence in BPM and Workflow and Awards for Case Management. Chuck is a ceaseless evangelist for process-aware technologies in healthcare, including workflow management systems, Business Process Management, and dynamic and adaptive case management. Dr. Webster tweets from @wareFLO and maintains numerous websites, including EHR Workflow Management Systems (http://chuckwebster.com), Healthcare Business Process Management (http://HCBPM.com) and the People and Organizations improving Healthcare with Health Information Technology (http://EHRworkflow.com). Please join with Chuck to spread the message: Viva la workflow!

This is my second of five guest blog posts covering Health IT and EHR Workflow.

If you pay any attention at all to interoperability discussion in healthcare and health IT, I’m sure you’ve heard of syntactic vs. semantic interoperability. Syntax and semantics are ideas from linguistics. Syntax is the structure of a message. Semantics is its meaning. Think HL7’s pipes and hats (the characters “|” and “^” used as separators) vs. codes referring to drugs and lab results (the stuff between pipes and hats). What you hardly every hear about is pragmatic interoperability, sometimes called workflow interoperability. We need not just syntactic and semantic interop, but pragmatic workflow interop too. In fact, interoperability based on workflow technology can strategically compensate for deficiencies in syntactic and semantic interoperability. By workflow technology, I mean Business Process Management (BPM).

Why do I highlight BPM’s relevance to health information interoperability? Take a look at this quote from Business Process Management: A Comprehensive Survey:

“WFM/BPM systems are often the “spider in the web” connecting different technologies. For example, the BPM system invokes applications to execute particular tasks, stores process-related information in a database, and integrates different legacy and web-based systems…. Business processes need to be executed in a partly uncontrollable environment where people and organizations may deviate and software components and communication infrastructures may malfunction. Therefore, the BPM system needs to be able to deal with failures and missing data.”

“Partly uncontrollable environment where people and organizations may deviate and software components and communication infrastructures may malfunction”? Sound familiar? That’s right. It should sound a lot like health IT.

What’s the solution? A “spider in the web” connecting different technologies… invoking applications to execute particular tasks, storing process-related information in a database, and integrates different legacy and web-based systems. Dealing with failures and missing data. Yes, healthcare needs a spider in the complicated web of complicate information systems that is today’s health information management infrastructure. Business process management is that spider in a technological web.

Let me show you now how BPM makes pragmatic interoperability possible.

I’ll start with another quote:

“Pragmatic interoperability (PI) is the compatibility between the intended versus the actual effect of message exchange.”

That’s a surprisingly simple definition for what you may have feared would be a tediously arcane topic. Pragmatic interoperability is simply whether the message you send achieves the goal you intended. That’s why it’s “pragmatic” interoperability. Linguistics pragmatics is the study of how we use language to achieve goals.

“Pragmatic interoperability is concerned with ensuring that the exchanged messages cause their intended effect. Often, the intended effect is achieved by sending and receiving multiple messages in specific order, defined in an interaction protocol.”

So, how does workflow technology tie into pragmatic interoperability? The key phrases linking workflow and pragmatics are “intended effect” and “specific order”.

A sequence of actions and messages — send a request to a specialist, track request status, ask about request status, receive result and do the right thing with it — that’s the “specific order” of conversation required to ensure the “intended effect” (the result). Interactions among EHR workflow systems, explicitly defined internal and cross-EHR workflows, hierarchies of automated and human handlers, and rules and schedules for escalation and expiration are necessary to achieve seamless coordination among EHR workflow systems. In other words, we need workflow management system technology to enable self-repairing conversations among EHR and other health IT systems. This is pragmatic interoperability. By the way, some early workflow systems were explicitly based on speech act theory, an area of pragmatics.

That’s my call to use workflow technology, especially Business Process Management, to help solve our healthcare information interoperability problems. Syntactic and semantic interoperability aren’t enough. Cool looking “marketectures” dissecting healthcare interoperability issues aren’t enough. Even APIs (Application Programming Interfaces) aren’t enough. Something has to combine all this stuff, in a scalable and flexible ways (by which I mean, not “hardcoded”) into usable workflows.

Which brings me to usability, tomorrow’s guest blog post topic.

Tune in!


Five Guest Blog Posts On EHR and HIT Workflow, Usability, Safety, Interoperability and Population Health

Posted on June 9, 2014 I Written By

Chuck Webster, MD, MSIE, MSIS has degrees in Accountancy, Industrial Engineering, Intelligent Systems, and Medicine (from the University of Chicago). He designed the first undergraduate program in medical informatics, was a software architect in a hospital MIS department, and also VP and CMIO for an EHR vendor for over a decade. Dr. Webster helped three healthcare organizations win the HIMSS Davies Award and is a judge for the annual Workflow Management Coalition Awards for Excellence in BPM and Workflow and Awards for Case Management. Chuck is a ceaseless evangelist for process-aware technologies in healthcare, including workflow management systems, Business Process Management, and dynamic and adaptive case management. Dr. Webster tweets from @wareFLO and maintains numerous websites, including EHR Workflow Management Systems (http://chuckwebster.com), Healthcare Business Process Management (http://HCBPM.com) and the People and Organizations improving Healthcare with Health Information Technology (http://EHRworkflow.com). Please join with Chuck to spread the message: Viva la workflow!

John Lynn is taking a well-deserved week off to attend a family function. He asked if I was interested in five EHR workflow guest blog posts, a blog post a day this week, on EMR and HIPAA. Of course I said: YES!

Here’s the outline for the week:

I blog and tweet a lot about healthcare workflow and workflow technology, but in this first post I’ll try to synthesize and simplify. In later posts I drive into the weeds. Here, I’ll define workflow, describe workflow technology, it’s relevance to healthcare and health IT, and try not to steal my own thunder from the rest of the week.

I’ve looked at literally hundreds of definitions of workflow, all the way from a “series of tasks” to definitions that’d sprawl across several presentation slides. The one I’ve settled on is this:

“Workflow is a series of tasks, consuming resources, achieving goals.”

Short enough to tweet, which is why I like it, but long enough to address two important concepts: resources (costs) and goals (benefits).

So what is workflow technology? Workflow technology uses models of work to automate processes and support human workflows. These models can be understood, edited, improved, and even created, by humans who are not, themselves, programmers. These models can be executed, monitored, and even systematically improved by computer programs, variously called workflow management systems, business process management suites, and, for ad hoc workflows, case management systems.

Workflow tech, like health IT itself, is a vast and varied continent. As an industry, worldwide, it’s probably less than a tenth size of health IT, but it’s also growing at two or three times the rate. And, as both industries grow, they increasingly overlap. Health IT increasingly represents workflows and executes them with workflow engines. Workflow tech vendors increasingly aim at healthcare to sell a wide variety of workflow solutions, from embeddable workflow engines to sprawling business process management suites. Workflow vendors strenuously compete and debate on finer points of philosophy about how best automate and support work. Many of these finer points are directly relevant to workflow problems plaguing healthcare and health IT.

Why is workflow tech important to health IT? Because it can do what is missing, but sorely needed, in traditional health IT, including electronic health records (EHRs). Most EHRs and health IT systems essentially hard-code workflow. By “hard code” I mean that any series of tasks is implicitly represented by Java and C# and MUMPS if-then and case statements. Changes to workflow require changes to underlying code. This requires programmers who understand Java and C# and MUMPS. Changes cause errors. I’m reminded of the old joke, how many programmers does it take to change a light bulb? Just one, but in the morning the stove and the toilet are broken. Traditional health IT relies on frozen representations of workflow that are opaque, fragile, and difficult to manage across information system and organizational boundaries.

Well, OK, I’ll steal my own thunder just a little bit. Process-aware tech, in comparison to hardcoded workflows, is an architectural paradigm shift for health IT. It has far reaching implications for interoperability, usability, safety, and population health.

BPM systems are ideal candidates to tie together disparate systems and technologies. Users experience more usable workflows because workflows are represented so humans can understand and change then. Process-aware information systems are safer for many reasons, but particularly because they can represent and compensate for the interruptions that cause so many medical errors. Finally, BPM platforms are the right platforms to tie together accountable care organization IT systems and to drive specific, appropriate, timely action to provider and patient point-of-care.

The rest of my blog posts in this weeklong series will elaborate on these themes. I’ll address why so many EHRs and health IT systems are so unusable, un-interoperable, and sometimes even dangerous. I’ll argue that modern workflow technology can help rescue healthcare and health IT from these problems.


Population Health Management (PHM) – The New Health IT Buzzword

Posted on May 6, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

For some reason in healthcare IT we like to go through a series of buzzwords. They rotate through the years, but usually have a very similar meaning. The best example is EMR and EHR. You could nuance a difference between the two terms, but in practice they both are used interchangeably and we all know what it means.

With this in mind, I was intrigued by an excerpt from Cora Sharma’s post on Financial Analytics Bleeding into Population Health Management:

It appears that “population health management” (PHM) just has a better ring to it than “accountable care” or “HMO 2.0”. Increasingly, PHM is becoming an umbrella term for all of the operational and analytical HIT tools needed for the transition to value-based reimbursement (VBR), including EHR, HIE, Analytics, Care Management, revenue cycle management (RCM), Supply Chain, Cost Accounting, … .

On the other hand, HIT vendors continue to define PHM according to their core competencies: claims-based analytics vendors see PHM in terms of risk management; care management vendors are assuming that PHM is their next re-branded marketing term; clinical enterprise data warehouse (EDW) and business intelligence (BI) vendors argue that a single source of truth is needed for PHM; HIE and EHR vendors talk about PHM in the same breath as care coordination, leakage alerts and clinical quality measures (CQM); and so on.

Cora is right. Population Health Management does seem to be the latest buzzword and for some reason feels better to people than accountable care. I guess it makes sense. People don’t want to be held accountable for anything. However, they love to help a population be healthy.

Coming out of 30+ meetings with vendors at HIMSS this year I was asking myself a similar question. What’s the difference between an HIE, healthcare analytics, business intelligence, data warehouses (EDW) and even many of the financial RCM products? I see them all coming together into one platform. I guess it will be called population health management.

To Cora’s broader point in the post, there is a real coming together that’s happening between clinical and financial data in healthcare. All I can think is that it’s about time. The division of the data never really made sense to me. The data should be one and available to whatever system needs the data. ACOs are going to drive this to become a reality.

Unlocking The Power of Data Science In Healthcare

Posted on January 29, 2014 I Written By

Kyle is Founder and CEO of Pristine, a company in Austin, TX that develops telehealth communication tools optimized for Google Glass in healthcare environments. Prior to founding Pristine, Kyle spent years developing, selling, and implementing electronic medical records (EMRs) into hospitals. He also writes for EMR and HIPAA, TechZulu, and Svbtle about the intersections of healthcare, technology, and business. All of his writing is reproduced at kylesamani.com

Vinod Khosla, Founder of Sun Microsystems and Khosla Ventures, recently stated that “in the next 10 years, data science and software will do more for medicine than all of the biological sciences together.”

The rise of population health and healthcare analytics companies aligns with Khosla’s claim. There are hordes of companies implementing healthcare analytics and helping providers identify at-risk populations to engage in proactive care. Despite their efforts, most of the analytics companies have been struggling to help providers actually improve outcomes.

Why?

Because data science in and of itself is meaningless. Effective data science can only provide insights. The challenge is in acting on insights provided by data. This is a widely acknowledged problem that every data science / analytics company faces; this problem has been particularly difficult in healthcare where a backwards culture and incentive structure have skewed the system towards complacency and volume rather than proactive care and value.

In healthcare, the actionability and effectiveness of data science hinge on communication between providers and patients, and on patients’ ability to act on those insights. There are a few methods of provider-to-patient communication and actionability:

At the point of care (in person or virtual visit) – providers have been educating patients at the point of care since the dawn of the profession. With advanced data analytics, providers can give more accurate, more customized education during the encounter. But the problem is that patients must act on that information at home when the doctor isn’t looking over the patient’s shoulder. Patients consistently fail to do what providers have asked them to do. The problem here is that the patient education and actionability based on education are intermediated by time and (lack of) context. Patients simply forget or are unwilling to do what their providers ask them to do in order to better care for themselves. Patients aren’t being educated in the right context. Point of care education won’t encourage patients from smoking the next cigarette, taking their meds on time, or skipping cheesecake at the office party.

Patient portals – the federal government has mandated that providers enable patients to engage with providers via patient portals. The basic premise of this mandate is that with access to their own health information, patients will take better care of themselves. Patient portals have some potential to empower patients to learn about their conditions at home and investigate conditions in more depth, but they don’t solve the context problem. Patient portals won’t do anything to help patients order a salad instead of a hamburger.

Messaging and notifications – this is the least explored, least understood, and in my opinion, the most potent communication channel to impact patient behavior. Automated notifications on iOS and Android can be presented contextually provided the device has contextual data to present notifications. Context is king. We live in the age of context. As devices learn more about their owners, devices can present contextual information to help change behavior. If your smartphone (or Google Glass, Jawbone, iWatch, etc) knows that you’re about to smoke a cigarette, it can automatically connect you with your husband/wife so that they can yell at you. If your device knows that you’re out at a steakhouse for dinner with business guests, it can remind you to order grilled chicken instead of a fried steak. The number of opportunities are endless.

To provide a better sense of the power of context, let’s examine Google and Facebook ads. Facebook ads are anything but contextual. When I’m scrolling through my news feed, I don’t care about the latest Hobbit movie, some new workout shake, or Dell’s newest laptop. I logged into Facebook to check out what my friends are up to, not to learn about the Hobbit or a laptop.

But when I Google “flight from Austin to New York January 18th” there’s a huge probability that I’m already committed to spending several hundred dollars to fly to New York, get a hotel, and spend money in NYC. With that search, only relevant advertisers – airlines, taxis, hotels, and local NYC attractions – will bid for my attention; I’m not going to see an ad for The Hobbit when searching for for a trip to NY.

This sense of context is reflected in Facebook and Google’s click through rates (CTR). 1-3% of all Google searches result in the user clicking on an ad. Between .01-.3% of FaceBook ads are clicked on. Google is measurably 10-100x more effective than Facebook. That’s the power of context.

There’s nothing wrong with emailing patients PDFs and interactive digital education tools after an encounter; there’s nothing wrong with patient portals and BlueButton. All of these communication channels fall short in that they don’t take advantage of real-time two way contextual communications. All of these channels are intrinsically one-way and lack context.

Books were the the first few-to-many communication channel. Then newspapers and magazines. Then radios. Then movies and TV. The defining characteristic of the Internet is that it is the first to enable two-way, many-to-many communications. The federal government’s healthcare communication model is fundamentally based on 20th century communication strategies. The power of data science will drive meaningful changes in patient behavior only when communication strategies leverage 21st century communication models.

Physician Focus, Data as King, and Real Time EHR Data

Posted on December 1, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.


I’m a little torn on this tweet. While I agree that there is too much administrative overhead in healthcare that distracts from patients and lifelong learning, I also think that things like EMR could contribute to both. A well implemented EMR software can help doctors focus on patients and help the doctor learn. This is certainly not the way most doctors look at EMR. Is this an EMR image problem or EMR software that’s not living up to its potential?


Of course, you have to take this tweet with a grain of salt since it comes from our very own Big Data Geek, Mandi Bishop. However, it’s an interesting topic of discussion. How important is the EMR data in healthcare today?


This tweet is related to the healthcare data tweet above. We all know that the EHR data isn’t perfect. Although, it’s worth noting that the paper chart wasn’t perfect either. However, I was more interested in the idea of real-time EHR data. I don’t think we’re there yet, but I’m interested to see how we could get there.

Is the ‘Internet of Things’ Health IT’s Next Big Thing?

Posted on October 17, 2013 I Written By

James Ritchie is a freelance writer with a focus on health care. His experience includes eight years as a staff writer with the Cincinnati Business Courier, part of the American City Business Journals network. Twitter @HCwriterJames.

Gartner Inc. has come out with a bullish report on the “internet of things,” which it predicts will add nearly $2 trillion in value to the economy by 2020 and transform the way all businesses operate.

As many as 30 billion devices with unique IP addresses will be connected, the majority of them being products, according to Gartner. That’s compared with a 2009 figure of 2.5 billion, 80 percent of them being devices such as laptops and phones.

One of the most often quoted descriptions of the internet of things comes from Helen Duce, director of the RFID Technology Auto-ID European Centre at the University of Cambridge: “We have a clear vision: to create a world where every object — from jumbo jets to sewing needles — is linked to the Internet.”

Health care would, of course, be part of the vision, which Gartner, a Stamford, Conn.-based IT research and advisory firm, calls the Digital Industrial Economy. The sector receives prominent billing, along with retail and transportation, in Garner’s latest news release on the topic.

The thinking is that physical objects — “from roadways to pacemakers,” as McKinsey & Co. put it in one report — will produce constant data streams that can be analyzed and acted on. The possibilities for systems such as inventory control are obvious enough, as the inventory would report on itself.

In health care, a major application could be in patient monitoring. Marketplace has quoted Dr. Anthony Jones of Philips Healthcare on the possibilities: “If I now have a continuous monitor, and I have that data going up into a central repository, I can write algorithms and put some intelligence into that repository that allows me to look for trends. So part of what the Internet of things will allow is much more sophisticated, much more continuous monitoring.” Sounds a bit like what John described in his post “Every Organ Will Have an IP Address.”

It sounds promising. But it also sounds much more incremental than it’s being portrayed by Gartner and other consultants.

Consider how Peter Sondergaard, senior vice president at Gartner, explained the future in a recent talk covered by ZDNet:

“The Digital Industrial Economy will be built on the foundations of the Nexus of Forces (which includes a confluence and integration of cloud, social collaboration, mobile and information) and the Internet of Everything by combining the physical world and the virtual.”

The predictions — Sondergaard said every object costing more than $100 will be smart by 2020 — look optimistic. Or pessimistic, depending on how you look at it: Gartner also estimates that one in three knowledge workers will be displaced by the new technologies.

About 60 percent of respondents to Gartner’s own recent CEO survey said the idea that the internet of things would replace millions of workers over the next decade-and-a-half was a “futurist fantasy,” according to SiliconANGLE. In health care, it’s hard to imagine that CIOs have much attention to devote to the internet of things amid the Meaningful Use and ICD-10 requirements they’re up against, although, as Jennifer Dennard wrote, health IT nowadays is much more than that.

The internet of things will get here. But it will probably develop in a piecemeal fashion, not in the dramatic way that Gartner envisions. Lots of “things” will get connected as companies see business reasons to put sensors in and bring them online. It will arise ad hoc from existing projects, with some industries joining the trend earlier than others.

When it does get here, there’s a good chance it won’t even be called the internet of things. In 2005, after all, Gartner was calling it the “real-world web.”

It was also predicting: “By 2015, wirelessly networked sensors in everything we own will form a new Web.”