My #HITsm Health IT Business Process Management Success Story, Plus a Conference Report

While working on my BPM & Case Management Global Summit conference trip report, I saw this tweet about sharing health IT success stories at the Friday, 12 EST, weekly #HITsm Twitter chatup (Health Information Technology Social Media).

As I’ve just given a 45-minute presentation to a workflow tech audience about healthcare and health IT opportunities, I thought, maybe now would be a good time to reflect on progress being made. By the way, I created the following YouTube from my slides and audio from that talk on 6/16.

While I’ve been giving presentations about workflow tech in healthcare literally for decades, I joined Twitter in December of 2008 (averaging 25 tweets a day) and starting blogging in earnest in 2009 (about a post a week). An important part of my strategy has been to blog and tweet about health IT to attract workflow tech community interest and followers. And to blog and tweet about workflow tech to attract health IT interest and followers. And, most important, get both communities engaged, on social media and face-to-face, with each other. Have I seen more sophisticated thinking about workflow and more use of workflow tech close-and-closer to the point-of-care? Yes, I have.

For example, each year I look at every web site of every exhibitor at the yearly HIMSS conference. Sites mentioning workflow tech or emphasizing workflow went from 8 percent in 2013 to 16 percent in 2014. Last week I was honored when John Lynn, without a doubt the top and most trafficked health IT blogger, contacted me about blogging once-a-day about workflow on his website, while he went on a well-deserved vacation. Check out the comments from both health IT and workflow tech professionals. Then there was the BPM and Case Management Global Summit early this week near Washington DC. (BPM stands for Business Process Management). When I started going to BPM and workflow conferences four years ago, there were no health IT folks at all. And the workflow tech folks were just beginning to get curious about opportunities to solve healthcare’s many workflow problems.

This year, there was intense conversation among a variety of health IT and workflow tech thought leaders. In addition, I’ve seen more-and-more healthcare workflow, BPM, and case management success stories. I tweet them whenever I find them. And I archive links to many at http://EHR.BZ.

I was delighted to see @TechyDoc there! I could not agree more wholeheartedly with his tweet!

BPM and Case Management Global Summit Short Trip Report

Well, so far this post has been about counting healthcare workflow tech blessings. I’ve enjoyed it! But it’s back into the weeds, so to speak. The rest of this post focuses on presentations, conversations, and impressions from the recent BPM and Case Management Global Summit. Did I mention I spoke there? Oh, yeah. Please feel free to watch my slides paired with recorded narration, on YouTube. (There’s also this half-as-long outdoor rehearsal, in front of the Capitol dome, recorded with Google Glass, waving printed slides around on a windy day.)

This is what the conference venue looked like. (At a Ritz-Carlton, very nice!)

Jim Sinur kicked off the conference. I especially like this slide about a spectrum of process styles.

I like how the Whitestein Living Systems Process Suite elegantly combines high-goals, organizational roles, and workflow automation. So, let’s say a workflow is executing but assumptions or conditions change. Workflows can also change, on-the-fly, based on reasoning about goals. LSPS is not (yet) used in healthcare, but I can imagine a future EHR workflow system actually helping patients and physicians think through, for example, quantity vs quality of life constraints and tradeoffs.

Here I am hanging out at the Whitestein Living Systems Process Suite booth.

I also enjoyed the Computas FrameSolutions presentation about its adaptive task management platform. I’d love to see FrameSolutions applied to clinical task management.

Nice overview of tasks in enterprises, including healthcare enterprises.

Users can create tasks, execute them, and assign them to others. Task can also be automatically created, assigned, executed, etc., all the while consulting organizational models (which, in healthcare, could include physician, nurse, tech, and so on).

Love it! Integrated tasks management and execution easily integrated with existing systems. Users can easily change the rules that fire, execute, adaptive tasks. Workflows can be programmed, but also “emerge” from user behavior. All the while all these activities are time-stamped and made auditable.

Here’s an interesting diagram. In traditional workflow management and BPM systems models of workflow and their execution are at their core. In other words, users and data are adapted to fit to these models. Of course, these models can be changed in ways that software without executable models (such as most health IT systems) cannot. However, adaptive case management puts data, about, for example, patients, at the core, and then automatically, semi-automatically, and manually triggers snippets of workflow. Instead of big workflow models (rigid during execution, though plastic during design), workflow is actually driven, moment-by-moment, during the work of problems solving, by data at hand, both from previous transformation and newly arrived from the outside world.

More on tasks as process snippets.

Users can create intelligent tasks.

Users can intelligently manage and share tasks.

I tweeted lots more slides from the FrameSolutions presentation, but I do want to get on to Keith Swenson’s presentation, a fitting windup for the conference from my perspective.

Keith has a seven-pillar model framework to compare and contrast different kinds of workflow software. All the way on the left, that’s traditional software development. On one hand, anything is possible since everything is simply a matter of programming. On the other hand, workflow is also “frozen.” To change workflow requires an expensive programmer, who won’t get it right, and even if they do, there will be bugs, so there’s a long and expensive cycle of testing, deployment, and training.

All the way on the right is email, phone calls, Twitter, etc., in which anything goes, but the user has to do all the work too. In between? Those are five general classes of workflow tech, from relatively rigid process models to relatively flexible models that just try to support and empower users, without getting in the way.

I’ll note I think of the seven columns more as rows of layers. On the bottom we have traditional server-based programs. On top of that bottom layer we have process models, starting out rigid and infrequently changed, but, as we ascend the stack, more flexible but also require more work and smarts from users, until we get to the top layer of emails, phone calls, Twitter, etc. All of these layers exist together, interacting, building on each other, but also causing occasional glitches. A programmer might be deep in the bowels of a Java program, but in the next moment tweet snippet of code to his programmer followers.

The following tweet lists the folks at the BPM & Case Management Global Summit with whom I tweeted most frequently. If you’re interested in any of the same things I am, I hope you’ll consider following them on Twitter.

And here is a special shout-out to Nathaniel Palmer, who organized the conference. He even coined the #BPMCM2014 hashtag, without which my above tweets could have been possible — literally!

Leave a Reply

Your email address will not be published. Required fields are marked *