I’m speaking at #HIMSS17! Extending EHR Value – Technologies for Making Data More Actionable

Monday, from 1:00pm to 2:00pm, at HIMSS17, I’m moderating an invite-only Lunch & Learn panel, Extending EMR Value – Technologies for Making Data More Actionable.

I’m speaking for 10 minutes, giving an industry perspective on “actionable data”, and then moderating a panel of experts (Kenneth Mandl, MD, MPH, Harvard Medical School and Boston Children’s Hospital; Lidia L Fonseca, Senior Vice President and Chief Information Officer, Quest Diagnostics).

Here is the panel description:

In 2017, payers and providers require more actionable insights from their data. Progress will be made, however, and through its historical health IT connectivity across half of U.S hospitals, Quest Diagnostics will share best practices for using data to drive decisions that improve financial performance and patient outcomes. This session will explore health IT solutions that extend EMR value, why they’re important and which investments to make now.

I look forward to synthesizing my views on actionable data (I might mention workflow…), and then listening to panel presentations, discussion, and answers to questions from the audience.

Stay tuned. I’ll write up and publish what I learn.

@wareFLO On Periscope!


Patient/Payer/Provider Collaboration: The Workflow Tech Angle (Learning Healthcare Systems!)

[This post is part of a series I am writing as a HIMSS17 Social Media Ambassador (four years in a row!) in the run up to HIMSS17, in Orlando, February 19-23. Stop by and meet me at the first ever HIMSS Makerspace, booth 7785 in the Innovation Zone!]

#HIMSS17 is a great opportunity to revisit my 2016 Actuarial Science, Accountable Care Organizations, and Workflow post, in which I predicted what ACO IT will look like in ten years.

(adapted from the The Patient Experience “Stack”)

I’ll recapitulate my five predictions of what ACO IT will look like, in ten years, here.

1. ACO IT will leverage process-aware workflow engines executing models of patient/payer/provider workflows

2. ACOs will simulate behavior of patient/payer/provider workflows to predict population health outcomes and costs.

3. ACOs will focus on patient/payer/provider pragmatic workflow interoperability, not just data interoperability.

See my two five-part series on Task-Workflow Interoperability and Pragmatic Interoperability.

4. ACOs, using activity-based cost integrated with business process management, will know exactly what each patient/payer/provider workflow (enrollment, chronic diagnosis, procedure, claims processing, etc.) costs.

5. Virtual ACO enterprises will systematically optimize system-wide outcomes, experience, and expense across patient/payer/provider workflows. If each of the above predictions, 1-4, become true (workflow tech infrastructure, workflow simulation, pragmatic workflow interoperability, and exact costs tied to specific workflows), ACOs will become truly intelligent learning healthcare systems.

Practically speaking, how does this optimized healthcare workflow nirvana relate to our present circumstances? Particularly regarding payer/provider collaborative workflows?

Let’s take a look at quotes regarding payer/provider collaboration and workflow.


Payer-Provider Collaboration In Accountable Care Reduced Use And Improved Quality In Maine Medicare Advantage Plan

“The patient population in the pilot program had 50 percent fewer hospital days per 1,000 patients, 45 percent fewer admissions, and 56 percent fewer readmissions than statewide unmanaged Medicare populations. NovaHealth’s total per member per month costs across all cost categories for its Aetna Medicare Advantage members were 16.5 percent to 33 percent lower than costs for members not in this provider organization. Clinical quality metrics for diabetes, ischemic vascular disease, annual office visits, and postdischarge follow-up for patients in the program were consistently high.”

Health Data Management:

“No single program reimburses for the end-to-end PHM workflow–and this makes it difficult for physicians and practices to embrace value-based reimbursement…. If payers coordinate their efforts to ensure that, together, their programs reimburse for more PHM workflows and outcomes, providers will have the critical reimbursement mass they need to invest in value-based care.”

From Availity’s blog:

“Providers aren’t taking full advantage of proprietary portals because they have so many different ones to navigate, and each has its own unique design and workflow…. A better approach is a multi-payer platform, which allows providers to log in to one site and process transactions for multiple payers using a common navigation and workflow.”

TriZetto (under the Payer-Provider Collaboration heading):

“bidirectional technology platform enables data availability to provide real-time administrative and clinical tools integrated directly into the physician’s workflow, thereby enabling new care delivery models”

The American Journal of Managed Care (“the leading peer-reviewed journal dedicated to issues in managed care”)

With respect to physician engagement, it was imperative to not change their workflow or at least to find common ground and include them into discussions on why those changes were important

What are some specific payer/provider collaborative workflows that we must support with the right information technology? Here are some examples:

  • Streamline workflows for provider contracting and engagement
  • Support provider workflows directed at optimizing patient experience and engagement
  • Simplify provider workflows for claims and encounter data

Collaboration is intrinsically about workflow. Therefore it’s worth reviewing the Wikipedia entry for Collaborative Workflow.

“Collaborative workflow is the convergence of social software with service management (workflow) software.”

“collaborative workflow is derived from both workflow software and social software such as chat, instant messaging, and document collaboration”

The goals of collaborative workflow include:

  1. “Improving effectiveness on joint tasks by removing the communication barriers between team members
  2. Minimizing organizational boundaries and information silos
  3. Allowing online social interaction to be goal oriented, structured, and measured”

“collaborative workflow is a collection of parallel and sequential tasks that rely on communication and coordination to achieve a desired outcome”

Finally, the attributes of a collaborative workflow management system include:

  • Collaboration to accomplish defined goals or tasks
  • Management of a collaborative goal, task, or project from start to finish
  • Integration of collaboration and workflow objects within a secure framework for enterprise applications
  • Project and task infrastructure enabling work to be accomplished in an organized fashion (in contrast to pure-play social software)
  • Skill-based task assignment to teams or individuals
  • Ad hoc projects that span organizational boundaries, and minimize information silos

All of these attributes apply to streamlining, supporting, and simplifying patient/payer/provider collaborative workflows. A goal may be getting well or getting paid. End-to-end, start-to-finish, interacting clinical and financial workflows are the key. We need to model, execute, monitor, and improve all workflows, including patient/provider, patient/payer, and payer/provider. Due to the sensitive nature of this clinical and financial information, we must do so within secure enterprise infrastructure. Social collaboration, even secure social collaboration is not enough. Workflow models must capture and observe healthcare organizational goals and constraints. Roles, of patient, of provider, and of payer, must be modeled and used to drive the right task to the right person at the right time, and make sure it is done right. However, at the same time all this workflow structure is imposed, exceptions and ad-hoc interactions, among patient, provider, and payer, must also be expected, handled, and supported gracefully.

Obviously, APIs (Application Programming Interfaces) are essential to exposing and updating data about patients, providers, and payers within their respective, evolving IT systems (see How Easy Is It To Integrate Availity APIs Into Your Payer-Provider Workflow? Very!). However, APIs are just half the IT battle, when it comes to workflow.

Without workflow, data is just another bottleneck.

It will be the marriage of both data technology and workflow technology that will deliver on the promise of truly optimal collaborative patient/payer/provider workflows.

Luckily, this marriage is happening. Every year since 2011 I’ve searched every website of every exhibitor at the annual HIMSS conference. I look for workflow-related content and trends. A wide variety of collaboration and workflow software vendors are showing up at HIMSS17 for the first (and, by now, even a second or third) time. And a wide variety of indigenous health IT vendors are adding collaboration- and workflow-related functionality to their products and services.

Great collaboration and great workflow, among patients, providers, and payers, requires great collaboration and workflow technology. Look for it.

@wareFLO On Periscope!


@MrRIMP #HITsm Tweetchat on Healthcare Robots: Direct, Indirect & Home Carebots!

Mr. RIMP (@MrRIMP on Twitter & Youtube) is all growed up! And hosting a #HITsm tweetchat all by hisself: Healthcare Robots! #HITsm, from noon to 1PM, EST, is an hour long. Dear little Mr. R put together an hour-long robot-themed mixtape, with lots of music videos about robots! So open two browsers, one for Twitter and the other for this post, and exactly at noon EST (so you all are listening to the same songs at the same time), start playing Mr. R’s mixtape! And, please, comment, positively, or negatively, about the music videos during #HITsm!

From @Techguy’s blog post:

We’re excited to share the topic and questions for this week’s #HITsm chat happening Friday, 2/3 at Noon ET (9 AM PT). This week’s chat will be hosted by Mr RIMP (@MrRimp, Robot-In-My-Pocket), mascot of the first ever #HIMSS17 Innovation Makerspace! (Booth 7785) (with assistance from @wareflo) We’ll be discussing the topic “Healthcare Robots!” and so it seems appropriate to have a robot hosting the chat….

In a first, #HIMSS17 has a #makerspace (Booth 7785), in the HIMSS17 Innovation Zone. It has robots! They are rudimentary, but educational and fun. One of those robots is @MrRIMP, for Robot-In-My-Pocket. Here is an YouTube interview with @MrRIMP. As you can tell, little Mr. R. has a bit of an attitude. He also wrote the questions below and will moderate tweets about them during the #HITsm tweetchat.

From the recent How medical robots will change healthcare (@PeterBNichol), there are three main areas of robotic health:

1. Direct patient care robots: surgical robots (used for performing clinical procedures), exoskeletons (for bionic extensions of self like the Ekso suit), and prosthetics (replacing lost limbs). Over 500 people a day loses a limb in America with 2 million Americans living with limb loss according to the CDC.

2. Indirect patient care robots: pharmacy robots (streamlining automation, autonomous robots for inventory control reducing labor costs), delivery robots (providing medical goods throughout a hospital autonomously), and disinfection robots (interacting with people with known infectious diseases such as healthcare-associated infections or HAIs).

3. Home healthcare robots: robotic telepresence solutions (addressing the aging population with robotic assistance).

Before the #HITsm tweetchat I hope you’ll watch Robot & Frank, about a household robot and an increasingly infirm retiree (86% on Rotten Tomatoes, available on YouTube, Amazon, Itunes, Vudu, and Google for $2.99) I’ll also note a subcategory to the direct care robots: pediatric therapy robots. Consider, for example, New Friends 2016, The Second International Conference on Social Robots in Therapy and Education. I, Mr. RIMP, have a special interest in this area.

Join us as we discuss Healthcare Robots during the February 3rd #HITsm chat. Here are the questions we’ll discuss:

T1: What is your favorite robot movie? Why? How many years in the future would you guess it will take to achieve similar robots? #HITsm

T2: Robots promise to replace a lot of human labor. Cost-wise, humanity-wise, will this be more good than bad, or more bad than good? #HITsm

T3: Have you played with, or observed any “toy” robots. Impressed? Not impressed? Why? #HITsm

T4: IMO, “someday” normal, everyday people will be able design and program their own robots. What kind of robot would you design for healthcare? #HITsm

T5: Robots and workflow? Connections? Think about healthcare robots working *together* with healthcare workers. What are potential implications? #HITsm

Bonus: Isn’t @MrRIMP (Robot-In-My-Pocket) the cutest, funniest, little, robot you’ve ever seen? Any suggestions for the next version (V.4) of me? #HITsm

2/16 #KareoChat: #HIMSS17! What’s Hot? How To Participate? Who To Follow? #HIMSS2117? Workflow!

[This post is part of a series I am writing as a HIMSS17 Social Media Ambassador (four years in a row!) in the run up to HIMSS17, in Orlando, February 19-23. Stop by and meet me at the first ever HIMSS Makerspace, booth 7785 in the Innovation Zone!]

I am so excited! No, not about HIMSS17, though yes I am excited about that.

I am so excited to host my first #KareoChat! Thank you KareoChat! In fact, Thursday, February 16, is my last day in the office, so to speak, before hitting the road. You see, I’m driving from Columbus, Ohio, to Orlando, Florida, hauling a car-load of makerspace stuff to HIMSS17 set up the first ever HIMSS conference Makerspace (booth 7785 in The Innovation Zone). But, no, this KareoChat is not about that, either.

This KareoChat is about #HIMSS17, itself. What’s hot? How to participate? Who to follow? Faster, better, cheaper! Workflow! (Of course!). And finally, imagine that you can step into a time machine to travel 100 years in the future to #HIMSS2117. What might you see?


And the questions are… (drum roll please!)

1. What topics will be top-of-mind at the upcoming #HIMSS17 conference? Number one? Two? Three? #KareoChat

2. How will you participate in #HIMSS17? In person? Exhibit only? Twitter? Presenting? (congrats) Other? #KareoChat

3. @HIMSS & present company excepted, who do you count on for #HIMSS17 1) news, 2) commentary & 3) humor? #KareoChat

4. Imagine #HIMSS17, #HIMSS2117 that is! What #SciFi health IT will be old hat by then? #KareoChat

5. Fast, Good or Cheap. Pick Two! Can #HIMSS17 help get to three? If no, why not? If yes, how? #KareoChat

6. Quick! Google #HIMSS17 +workflow What product (or class of product) pops up on your radar? What’s interesting? #KareoChat

@wareFLO On Periscope!


Newsman Tom Sullivan Usually Asks The Questions: We Ask Tom About #HIMSS17, Heroes, and #HITsm

[This post is part of a series I am writing as a HIMSS17 Social Media Ambassador (four years in a row!) in the run up to HIMSS17, in Orlando, February 19-23. Stop by and meet me at the first ever HIMSS Makerspace, booth 7785 in the Innovation Zone!]

Tom Sullivan treads a fine line. He is a reporter and the editor-in-chief for the influential health IT publication, Healthcare IT News. And he’s on Twitter, as @SullyHIT, and part of a sprawling and energetic #HITsm Health IT Social Media community.

Sometimes the health IT industry seems a bit like The Game Of Thrones. The large companies are like warring families. They join together into alliances to gain temporary advantage. Meanwhile, unbeknownst to the ruling clans, upending technologies — dragons, magic, wildfire — threaten to change everything. Tom chronicles these campaigns and wild cards from a uniquely appropriate perspective, as you will see.

Journalists usually interview, not be interviewed. I asked Tom Sullivan, Healthcare IT News Editor-in-Chief, the same questions he asked HIMSS17 Social Media Ambassadors (including me). Here are his answers.

What are you most looking forward to at HIMSS17?

The surprising. Literally. By that I mean emerging technologies or upstart companies that bring tools no one else has thought off or was able to pull off. I don’t think it’s a stretch to say the show floor is a bastion of innovation and as someone who is fascinated by technology and has made a career out of writing about it, that makes it a fun place.

What issues do you think are top-of-mind for your readers?

Population health, ransomware, security in general, big and small data, analytics, interoperability, of course. That list goes on. We are also seeing considerable and exciting interest in innovation right now. Artificial intelligence, cognitive computing, machine learning. Those technologies really resonate with our readers and, selfishly here, they’re really fun to write about. Just this week I talked to three provider innovation officers kicking off proofs-of-concept with Amazon Echo to improve the patient experience by making voice interaction a realistic part of it.

Who’s your favorite healthcare reporting hero? Why?

I’ll give you two for the price of one. First up: my old man. While he was actually on the sales side of business-to-business publishing and in plastics rather than healthcare he started as a reporter both working in his hometown of Sioux City, Iowa for a local TV station and in Vietnam for the armed forces newspaper Stars and Stripes. I’m including him here because in 1994 he found himself out of a job with two kids in college and a third in private high school. So he took his chances and started a publication, Injection Molding Magazine, and ultimately succeeded on the virtue of serving readers above all else with quality content. Journalistic integrity.

A hero particular to health IT reporting is none other than Jack Beaudoin, the founding editor of Healthcare IT News – and, no, I’m not saying that to toe the corporate line because he has since moved on. Jack started HITN well before Obamacare and the HITECH Act brought health IT into the national discourse and, in fact, even prior to former President George W. Bush establishing the Office of the National Coordinator for Health IT. That took not just real vision but the guts and gravitas to leave a promising career for a speculative opportunity at a time when big, established B2B IT publishers were merely dabbling in healthcare with a new e-newsletter or supplement instead of boldly building entire publications or companies around the topic.

All that said, I have many heroes and could go on and on but will leave it at those two.

What’s your pet peeve? (Either on- or off-line?)

A lot of reporters might list PR pros or some of their techniques, but not me. I appreciate them. Rather, my pet peeve is people who talk but don’t listen. It doesn’t matter whether you are a brilliant CEO or a stranger on the street I am hard-wired to walk away from one-way conversationalists. Perhaps that’s why I’m a writer.

What is something your readers do not know about you?

I started my career in the enterprise IT business-to-business reporting realm at a publication called Mobile Computing & Communications Magazine, followed by a great run at ent Magazine (we received many inquiries from people thinking ent stood for ear, nose and throat but it was an IT pub) and then I spent nearly a decade at IDG’s InfoWorld covering just about everything from app dev to Web services – and I’ve been telecommuting for 18 of those years.

Bonus question: What is your guesstimate re percent of your readers not on Twitter versus readers who arrive via Twitter?

We really get a nice boost traffic-wise from the collective of social media channels and have the thriving #HITSM community and others to thank for that. For me personally social media is about even more than driving traffic to our website. It’s about finding sources, generating story ideas, actually getting to know people and having a human connection with readers in ways that really aren’t possible otherwise.


Tom Sullivan
Healthcare IT News

The Patient Experience “Stack”: From API to Experience Through Workflow

[This post is part of a series I am writing as a HIMSS17 Social Media Ambassador (four years in a row!) in the run up to HIMSS17, in Orlando, February 19-23. Stop by and meet me at the first ever HIMSS Makerspace, booth 7785 in the Innovation Zone!]

When I cross-index “patient experience” and “API” in Google, the number one ranked result is The Untapped Potential of Health Care APIs in Harvard Business Review. It was published in 2015. I’ve read it before. It was tweeted around when first published. Some of what the paper predicted has come true. It’s still a great read. And a great pivot to my favorite topic: healthcare workflow and workflow technology.

Here are some quotes (my emphases):

“Leaders of most internet-based businesses have realized the critical importance of using open application programming interfaces (APIs) to expand the reach of their organizations. If the health care industry followed suit, the impact on the quality and cost of care, the patient’s experience, and innovation could be enormous.”

APIs are programming routines or protocols that allow software applications to share data…. Ultimately, this type of innovation serves the end customer — creating better functionality and experience for the user.”

“Cultural and workflow issues within health systems must be addressed…. At Ochsner Health System, a pilot program to prevent heart failure and hypertension used an API to collect body weight and blood pressure data from over 500 individuals’ connected devices…. results from these and other pilots across the country have shown the potential of APIs to improve care and create a better experience for patients and providers alike.”

Sounds great! What’s missing? (Though it’s hinted at in that last quote…)

What is the single most important concept and technology to leverage APIs to improve patient experience? Workflow and workflow technology. Let me lay out my case.

There is a wonderful phrase from the hospitality industry: The System Behind the Smiles. It actually originated in a book about marketing, written by someone who had been extremely successful at selling automobiles. Here is the key quote.

“What’s needed in restaurants, car dealerships, department stores, and every place else is systems–not just smiles–that guarantee good service. Every business is composed of systems. These systems must work together to create a process that is efficient and responsive to a customer’s wants.”

What do systems engineers think when they hear “system”? They think, “workflow” (or “process” in highly automated industries). The reason they think in terms of workflow, not systems, is system is a very general term. However, workflow is very specific term, concerning the order in which things happen and their inputs and outputs. Great patient experience requires great workflow. Great workflow requires great workflow inputs. One of those important inputs is data. Where will this data increasingly come from? APIs.

Lets think about patient experience in terms of a software concept, a “stack.” A stack is a set of layers, each layer depending on the layer below, and adding functionality depended upon by the next layer up. For example, there is the LAMP stack (Linux OS, Apache web server, MySQL database, PHP programming language). You may have heard of such a thing as a “full stack” developer. They are proficient at all layers and how they fit together.

If it seems odd to include experience in a software stack, I assure you it’s a great idea. Even Intel, which makes most of its money from the very bottom layer (silicon), thinks in term of stack all the way up to experience.

I’d like to return to the “The System Behind The Smiles” concept. It really means “The Workflows Behind the Smiles.” Here is a sequence of slides from a presentation I gave last year.

One of the most popular definitions of patient experience is that of the Beryl Institute.

Let’s break it apart to understand what are the smiles versus what are the workflows.

First there is what happens to the patient and how they experience it.

There there are the systemy/workflowy stuff causing things to happen the patient.

Let’s drill down into interactions and continuum of care…

That word “orchestration”? It’s workflow. Or rather it is what is done to create great workflow. For patients to have Smile experiences, all the System workflows need to be perfectly orchestrated. And great orchestration requires great interoperability, to which APIs contribute.

You may have heard of syntactic and semantic interoperability. Syntax is the shape of data and ability to move it between systems. “Shape” is important because data structures must be generated and parsed to travel. Semantics is meaning. Does data mean the same thing before and after transit? In addition to syntactic and semantic interoperability, there is a third layer of interoperability that is less mentioned. Task-workflow interoperability. (This kind of interoperability is also known as pragmatic interoperability.)

The very top of the patient experience stack is, well, patient experience (not shown above). But what’s between the bottom, data-centric syntactic and semantic layers and the top layer, patient experience? You guessed it. Workflow. I’ve written two separate five-part series about this layer, one from a engineering point of view and the other from a linguistic science point of view. Workflow determines patient experience.

If workflow determines patient experience, what technology is most relevant to patient experience? Workflow technology. What is workflow technology? Why is it important to patient experience. How to we accelerate use of workflow technology to improve patient experience?

To understand workflow technology you must understand workflow. Workflow is a series of steps, consuming resources, achieving goals. Workflow faces in two directions, towards people and towards technology. Steps may be tasks, screens, activities, or even experiences.

Similar, by analogy, to database management systems, which rely on on data models; workflow management systems rely on workflow models. These workflow models look a lot like workflows you’ve probably scribbled on a napkin as some point in your life. We draw workflows to think and communicate. The magic of workflow technology is that these diagrams become actual programs, executable by workflow engines. The best known examples of workflow technology today are business process management suites. BPMSs are examples of what researchers call Process Aware Information Systems. But many other technologies, not traditionally identified as workflow technologies, are becoming process-aware. These include customer relationship management (CRM) systems, data science and machine learning systems, chatbots and natural language processing systems, as well as traditional health IT systems, such as laboratory reporting and imaging systems. What all these disparate systems have in common is a pivot from sole focus on data to more equal emphases on data and workflow.

Workflow technology is finally being use to improve both patient and health IT user experience. Two years ago, in a five-part, 7000 word series in Healthcare IT News on task-workflow interoperability, I predicted the following:

“We will see a plethora of clinically- and patient-oriented workflow platforms. Many have already obtained considerable investment and beginning to expand their market footprints. It’s early days yet. But, within five years we’ll see as much, or more, about facilitating workflow at the point-of-care and point-of-health as the emphasis on population health and patient engagement at the recent HIMSS conference in Chicago. In fact, population health and patient engagement are playing critical roles in driving adoption of process-aware workflow technologies in healthcare. If you drill down through the layers of technology necessary to do both, efficiently, effectively, and flexibly at scale, you’ll invariably find some form of workflow orchestration engine. In some cases these will be based on third-party business process management suites. In some cases the workflow engines will be proprietary. It’s often hard to tell which is which, since many vendors do not wish to reveal they are relying on an embedded third-party product.” (Task-Workflow Interoperability)

However, adoption of process-aware workflow technology in healthcare and health IT is not happening fast enough. How to we accelerate use of workflow technology to improve patient experience? I wrote about a healthcare workflow triple aim on the Health Standards website two years ago.

  • Educate all healthcare stakeholders about workflow, workflow technology, and process-awareness. (This post, crafted in advance of the Availity tweetchat about patient experience, is an example.)
  • Highlight healthcare workflow success stories. (For example, every year since HIMSS11 I’ve searched every website of every HIMSS conference exhibitor for workflow related material. I use the #POWHIT hashtag, for People and Organizations improving Healthcare with Information Technology, to publish and organize on social media.)
  • Recruit current and potential healthcare workflow technology solution providers to create and market excellent process-aware workflow solutions. (Talking or writing or tweeting about healthcare workflow and workflow technology all day long won’t accomplish a thing, until and unless actual workflow products and services get into everyday use.)

If I have convinced, or at least, intrigued you, about how healthcare workflow and workflow technology is the missing link between APIs on the one hand and patient experience on the other, I hope you take a wee keek at any of the following posts, articles, or series.

@wareFLO On Periscope!


Wonderful Video Chat About Microservices in Healthcare, With Real Code Examples!

[This post is part of a series I am writing as a HIMSS17 Social Media Ambassador (four years in a row!) in the run up to HIMSS17, in Orlando, February 19-23. Stop by and meet me at the first ever HIMSS Makerspace, booth 7785 in the Innovation Zone!]

Youtube Archive of Firetalk Event

Learn about microservices in healthcare from the co-developer of the first programming language specifically for creating microservices, @JolieLang! A recent Firetalk (19 viewers, 71 messages) got into actual programming code! For general background about microservices in healthcare, read my From APIs to Microservices: Workflow Orchestration and Choreography Across Healthcare Organizations. There’s also an excellent 5-minute Youtube explanation of microservices. You’ll see the obvious connection from microservices to workflow and workflow tech, since a microservices are like tasks in workflow management system. They need to be orchestrated to create complete workflows. Furthermore, since Jolie microservices are intrinsically distributed, as soon as you write them, one can imagine building health IT applications with workflows orchestrated across multiple health IT organizational silos. I’d love to network with anyone I can interest in Jolie at HIMSS17. You can contact me through my Twitter account @wareFLO or this blog’s Contact Me page.

The code Claudio Guidi refers to was written by Balint Maschio. It’s a toy, but executable, program illustrating how microservices written in Jolie might serve medical images. Claudio spent about twenty minutes discussing the Balint’s code, most of the time in the orchestrator service file named server.ol. Claudio is very good about systematically referring to line numbers in the Jolie code. When he does so, just scroll down to inspect the code while continuing to listen to Claudio. Server.ol refers to other services, which you can get to via the Github link. He briefly discusses OrchestratorInterface.iol, so I’ve appended that code below as well.




For my own experiments writing Jolie microservices, see the postscript to my more general post about microservices in healthcare.

See you at HIMSS17! By the way, I have my own booth this year. I’m running the first makerspace at a HIMSS conference. It’s Booth 7785 in the Innovation Zone.

@wareFLO On Periscope!


Workflow Discussed At Connected Health Conference! IMO Healthcare Needs More BPM (Business Process Management)

I’m delighted to see workflow being discussed at the Connected Health Conference!

Here are some of my own #Connect2Health tweets about workflow.

There’s a great book to learn about true workflow automation in healthcare.

Please check out the latest edition of Business Process Management In Healthcare. I contributed a chapter and wrote the foreword!

@wareFLO On Periscope!


Hello world! (Moving From ChuckWebster Dot Com to Wareflo Dot Com)

I’m moving my blog from chuckwebster dot com to wareflo dot com (@wareFLO being my Twitter handle). I am taking the opportunity to reorganize the over 650 posts I’ve made since 2009 (including 400 plus draft posts I’ve apparently not completed!). You may notice an occasional broken link or missing image. Please excuse the dust and construction!

Oh, I hope you have a wonderful 2017!

PS Follow me on Twitter at @wareFLO!

@wareFLO On Periscope! firetalk-button2