HIMSS 2014 in Review

HIMSS 2014 in Review

The HIMSS conference is so big, with so many different kinds of attendees and exhibitors that it’s almost impossible to have one big theme for any given year. Yet the question of theme for any given HIMSS is something we all talk about. The themes one perceives are at least partially defined by our own interests and area of focus. Consequently, the #HIMSS14 themes for me were:

  • The shifting product and value proposition focus of many of the vendors I track,
  • The tension between spot solutions and enterprise solutions, and
  • The big buzz word of the show, population health.

Two of the market segments that I track with big shifts in value proposition were medical device data systems (MDDS) and messaging middleware. We’ll talk about specific shifts in a moment, but I think it worthwhile to consider why this change in value propositions has occurred. One obvious factor among MDDS vendors is acquisitions. Capsule Tech (registration required), Accent on Integration and iSirona have all been acquired. Acquisitions are major events when everything about a company is reevaluated in an effort to wring greater value from the acquired company. The other factor I think is the growing adoption of MDDS for clinical documentation into EMRs may have caused sales growth to temper a bit, causing vendors to look beyond clinical documentation and explore for ways to add value and differentiate. Let’s look at some examples.

The latest iteration of the Neuron shown at HIMSS14 becomes a vital signs monitor with plug in sensors.

The latest iteration of the Neuron shown at HIMSS14 becomes a vital signs monitor with plug in sensors.

Capsule Tech has released a new version of their Neuron device and transformed it into a vital signs monitor (pictured right). I’ve explored the virtualization of medical devices before in past conference presentations.  This is where the core functionality of the traditional medical device is reduced to its essence and combined with an off the shelf computing platform. Imagine an ultrasound transducer, spirometer or EKG leads with a USB connector. Such products are delivered with software that runs on a laptop or desk top computer, tablet or smartphone. Simply install the software and plug in the sensors via the USB connector, and you have a fully functional medical device. (A more technical description of this may be found in this paper, from the Intel Technical Journal, published in 2006.)

Capsule has taken the general purpose computing functions that make up most of a conventional embedded system device and implemented them in the Neuron. Next they’ve taken sensors with miniaturized electronics that acquire and process the sensor data and convert it to a standard USB interface. Plug a temperature probe, SpO2 sensor, non invasive blood pressure module and similar sensors into the Neuron, and you have the new SmartLinx vital signs monitor, part of Capsule’s medical device information system. This new approach allows sensor vendors and Capsule both to add value at the expense of conventional vital signs monitor manufacturers.

In addition to SmartLinx, Capsule showed a new terminal server called Axon with power over Ethernet and Wi-Fi connectivity, and what they called “clinical analytics.” Capsule’s clinical analytics, really a clinical decision support system,  is presently targeted at identifying patients with a deteriorating clinical condition and diagnosing patients with sepsis.

Accent on Integration (AoI) was acquired by Iatric Systems. AoI has extended their value proposition beyond MDDS and clinical documentation to include infusion pump interoperability whereby their software will be used to program infusion pumps based on orders from CPOE and pharmacy systems. This is one of the first pump interoperability solutions to come from a third party (i.e., not from a pump or EMR vendor). Iatrics is using Meditech’s proclivity to avoid systems integration to enter the pump interoperability market.

Nant Health is a health care IT and medical device company created by serial entrepreneur Dr. Patrick Soon-Shiong. The company’s atypical product portfolio ranges from mHealth to revenue cycle management. Since iSirona was acquired by Nandt Health, the company has received FDA clearance and brought to market an alarm notification solution for acute care. This pulls iSirona squarely into the messaging middleware space.

The company also showed HBox, a new terminal server and connectivity hub with a similar design and capabilities of Qualcomm’s 2net. The HBox includes wireless connectivity via Wi-Fi and a proprietary radio in the Sensium wireless sensor package from Toumaz (what they call a “sticking plaster” in the UK). It appears that Nant Health will be selling the Sensium into the acute care market as a means to identify patients with a deteriorating clinical condition. The HBox will be used as a gateway communicating with the Sensium device and connecting it to the enterprise network, and later HBox will be used to provide connectivity in patient homes.

Besides the changes at the MDDS acquisitions above, similar moves up the value chain away from conventional MDDS solutions are wide spread.

  • Cerner continues to add clinical capabilities on top of their MDDS capabilities, and HIMSS14 was no exception. Besides refining the alarm notification system they’ve had for some time, Cerner showed extensive workflow automation and communications via their care team communications solution.
  • Excel Medical Electronics has shifted into clinical decision support and data analytics by leveraging their MDDS capabilities and IBM’s InfoSphere Streams. Just prior to HIMSS14, Excel announced the AlarmNavagator to help hospitals meet the Joint Commission alarm safety national patient safety goal.
  • Nuvon showed a new clinical decision support solution at HIMSS14. Called informatics on their web site, Nuvon leverages near real time medical device data with other clinical data to create “actionable, practical, useful information that can guide clinical decision-making.”
  • The folks at True Process, another MDDS player, got into the bar code medication administration business two years ago. They also compliment MDDS sales to hospitals with contract product development business helping medical device manufacturers add connectivity to their products. (True Process also had my favorite booth of the conference, very unique!)

In the recent past the MDDS market was dominated by the acquisition of medical device data to populate flow sheets in EMRs – an important but basic enabling technology for higher value activities like alarm notification, clinical decision support systems and other tasks more directly related to patient care and outcomes. After just a few years – lightening speed for the health care market – the MDDS market is undergoing major changes.

Spot vs Enterprise Solutions

Geoffrey Moore’s, Crossing the Chasm, is my favorite market adoption model because it fits health care technology markets so well. At this year’s HIMSS, I was struck by a parallel. Much like the bowling alley strategies described by Moore, what is called the messaging middleware market is driven by a variety of spot solutions. With Moore’s model, once sufficient bowling alley strategies have succeeded, the market enters the tornado where a brief period of rapid adoption occurs where buyers shift from the early adopters to the much larger early majority of the market. These spot markets for messaging middleware all revolve around facilitating communications and automating workflow. Examples of spot solutions include:

  • Integrating nurse call systems with wireless VoIP phones and smartphones to put patients directly in touch with their caregiver where ever they are in the unit;
  • Automating group and individual messaging inside or outside the enterprise;
  • Messaging to on call staff using both BYOD and enterprise owned communications devices;
  • Various workflow automation solutions for managing patient discharge, managing readmission risk, or customized for specific customers;
  • Alarm notification from medical devices to the caregivers responsible for the patient whose medical device generates the alarm;
  • Critical test results delivery via BYOD and enterprise owned communications devices; and
  • Specialized medical device central station with alarm management, surveillance and event review.

These spot solutions match a series of pain points for health care delivery organizations. Various messaging middleware vendors target one or more of these pain points with spot solutions. Since HIMSS14, I’m up to 25 companies that I track in messaging middleware. The product architecture and capabilities of these different company’s solutions are very similar, if not virtually identical. Yet few of these companies see more than a hand full of competitors in their sales efforts. This is because different companies are targeting different sets of pain points with spot solutions. These spot solutions can exist in customer sites as separate systems or they may be integrated to provide different capabilities to the same sets of users.

At some point the market is going to start to swing from spot solutions to enterprise solutions. Much like the transition experienced by Emergin years ago, buyers are going to wake up and recognize they’re buying multiple spot solutions that are technically very similar for their various pain points. The question will arise, “Why can’t we meet these various needs with one solution rather than having to buy one for each problem?” At this point, messaging middleware companies will start to recast themselves as enterprise solutions able to address a wider variety of pain points.

As manufacturers continue to draw outside the lines of conventional market segments, the challenges increase for buyers to select solutions that will serve them for more than the short term. Hospital buyers must complete rigorous requirements assessments to enable a meaningful assessment of competing solutions. And manufacturers will have to stay close to the pain points of buyers if they want to drive sales.

Population Health

The best I could tell population health is something enabled by health information exchanges, or something. It seems vaguely like what the NSA does with our phone calls, smart phone apps, locations, email, webcams, Twitter, Skype, Facebook, Google, etc. Is there real value in all this? The NSA seems to think so. But I wonder if a panopticon of electronic health care data will be any more specific, sensitive or cost effective than conventional double blind clinical trials. Robust clinical trials are not cheap, but then extending the surveillance state to health care won’t be cheap either.

Conclusions

This blog post is part of the #HIMSS14 Blog Carnival #4, Looking Back at HIMSS14. Be sure to check out the carnival to see what other HIMSS14 Social Media Ambassadors though about this year’s event.

Finally, I’d like to thank the folks at HIMSS for letting me attend this year’s event as a Social Media Ambassador. I hope people got something from my tweets during the conference, and this wrap-up blog post.

Tim Gee is Principal of Medical Connectivity Consulting. He is a master connectologist, technologist and strategist working for medical device and IT companies and various provider organizations. You can learn more about Tim here.

Share

2 comments

  1. Great summary, Tim, and great insights. I think that your assessment of the migration of spot solutions to enterprise solutions is very astute especially with respect to the middleware (middleman?) market. As providers and healthcare enterprises wrestle with costs; duplication of functionality will be consolidated.

    With regard to population health, I think of that as big data in healthcare–and HITECH has enabled a platform by which the data can more easily be collected…as evidenced by the ONC priorities. As you say, it is to be seen if this will be effective. The underlying data quality and accuracy and theories and models used for analysis will determine in the end if the results will be accepted.

  2. William Hyman

    It is good to remember that there are some basic questions to ask about such “solutions”. These include whether or no the vendor has proper FDA regulatory status where applicable. The possible responses when asked include yes, not required (which may or may not be correct), and “huh?”.

    Also, which comm products are labeled for use as a primary means of communication of, for example, medical alarms? Which disclaim such use (as Tim noted some time ago)? Which are being marketed and used despite such labeling? If so, are the users unaware, are they ignoring it, or are they pretending that such use is not primary? Can they even identify a primary for which the system actually being used is the secondary? Do they have a backup plan if the system becomes unavailable?

    With respect to the public health/big data aspect it may be true that in theory EHRs can provide all this wonderful data, but I still await even my own multiple medical providers being able to see an integrated EHR instead of relying on faxed, emailed, and hand carried data.

Trackbacks/Pingbacks

  1. Clinical Integration and Alarm Management - Two Sides of the Same Coin | Extension Healthcare - […] recent post on the Medical Connectivity blog discussed the impact of spot vs. enterprise solutions on the […]
  2. Are We Using All the Data We Have? | Hospital EMR and EHR - […] of care. For those who don’t know much background on Capsule, go and read medical device guru Tim Gee’s …

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>