Comments on: HIStalk Interviews Michael McNeal, President and CEO of Emergin http://histalk2.com/2007/06/20/histalk-interviews-michael-mcneal-president-and-ceo-of-emergin/ Healthcare IT News and Opinion Thu, 29 Jul 2010 05:14:23 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Art Vandelay http://histalk2.com/2007/06/20/histalk-interviews-michael-mcneal-president-and-ceo-of-emergin/comment-page-1/#comment-26 Art Vandelay Thu, 21 Jun 2007 12:49:47 +0000 http://histalk2.com/2007/06/20/histalk-interviews-michael-mcneal-president-and-ceo-of-emergin/#comment-26 I attended one of his grassroots sessions and was extremely impressed with his grasp of the baseline technologies, his ability to bridge communications between the often separate worlds of the biomedical/clinical engineer and an IT propeller head, and his understanding of workflow in a healthcare environment. If anyone has the chance, he is a must-see presenter with thought-provoking commentary AND facts. I strongly believe they need to add three modules to their product and more strongly market another capability: 1. Take-on Capsule (or buy them) for the EMR integration as well as leveraging the event notification features and many-to-many connectivity capabilities they already have on their Enterprise Service Bus - think of this as a pre-screen before the events/transactions get to the interface engine and subsequently the EMR. As the medical device manufacturers have been painfully slow in adopting HL7, this is a requirement in the near future. Also, healthcare organizations will have more legacy equipment that will take years to weed out of the environment without basic HL7 communication capabilities. 2. Work to define an isolated architecture (to allow simplified FDA approval) that can be resold to medical device manufacturers or to larger organizations with strong development shops for true alarm notification and consolidation. Welch Allyn has released something (http://medicalconnectivity.com/2007/05/24.html), Cardinal is working on something, but these will likely not be service-oriented nor easily extensible to the myriad of medical device and communication platforms that exist in an environment. Can anyone say proprietary? Tim Gee has a recent post mentioning the limitations of GE's CareScape Mobile Viewer as well as some great ones on alarm notification: http://medicalconnectivity.com/2006/01/30.html#a539 http://www.psqh.com/janfeb07/pointofcare.html 3. A positioning system integration architecture with a dashboard view of real-time operations focusing on the technologies providing real-time data - the medical devices. Think of this as a visual dashboard - a CAD of your facility, like a bedboard - with configurable views of positioning information, bed status, combined with critical real-time alarm notifications or current status information. Market the Capability of EMR notification back to mobile devices - They need to market this to the EMR vendors or better yet, directly to the organizations (EMR vendors probably see this as a threat and will try and knock-off his intellectual property). The ESB in #1 above can communicate the basics like critical lab or radiology values but the EMR, as a repository, has information for cross-correlation. Hey Michael, my price is low but Florida is too hot for me most of the year. I attended one of his grassroots sessions and was extremely impressed with his grasp of the baseline technologies, his ability to bridge communications between the often separate worlds of the biomedical/clinical engineer and an IT propeller head, and his understanding of workflow in a healthcare environment. If anyone has the chance, he is a must-see presenter with thought-provoking commentary AND facts.

I strongly believe they need to add three modules to their product and more strongly market another capability:

1. Take-on Capsule (or buy them) for the EMR integration as well as leveraging the event notification features and many-to-many connectivity capabilities they already have on their Enterprise Service Bus – think of this as a pre-screen before the events/transactions get to the interface engine and subsequently the EMR. As the medical device manufacturers have been painfully slow in adopting HL7, this is a requirement in the near future. Also, healthcare organizations will have more legacy equipment that will take years to weed out of the environment without basic HL7 communication capabilities.

2. Work to define an isolated architecture (to allow simplified FDA approval) that can be resold to medical device manufacturers or to larger organizations with strong development shops for true alarm notification and consolidation. Welch Allyn has released something (http://medicalconnectivity.com/2007/05/24.html), Cardinal is working on something, but these will likely not be service-oriented nor easily extensible to the myriad of medical device and communication platforms that exist in an environment. Can anyone say proprietary? Tim Gee has a recent post mentioning the limitations of GE’s CareScape Mobile Viewer as well as some great ones on alarm notification: http://medicalconnectivity.com/2006/01/30.html#a539 http://www.psqh.com/janfeb07/pointofcare.html

3. A positioning system integration architecture with a dashboard view of real-time operations focusing on the technologies providing real-time data – the medical devices. Think of this as a visual dashboard – a CAD of your facility, like a bedboard – with configurable views of positioning information, bed status, combined with critical real-time alarm notifications or current status information.

Market the Capability of EMR notification back to mobile devices – They need to market this to the EMR vendors or better yet, directly to the organizations (EMR vendors probably see this as a threat and will try and knock-off his intellectual property). The ESB in #1 above can communicate the basics like critical lab or radiology values but the EMR, as a repository, has information for cross-correlation.

Hey Michael, my price is low but Florida is too hot for me most of the year.

]]>