HIMSS17 TOOK PLACE IN ORLANDO, FL
February 19-23, 2017
by Rob Wilder, participant HIMSS Interoperability Showcase™, HIMSS17
Whenever I have the opportunity to travel to a foreign country, I always push myself to learn some key tourist phrases beforehand, like “Which way to the nearest subway stop?” or the ever important, “Where is the bathroom?” No matter how much I study my travel guide in advance of my arrival, I inevitably end up relying on my smartphone and Google Translate™ to help me communicate in real time on the ground.
Speaking the same interoperability language: This scenario reminds me of interoperability in healthcare. Ideally, every system would speak the same language, and information could flow freely between organizations, systems, providers, and patients. This is the long-term goal.
As outgoing National Coordinator for Health Information Technology Vindell Washington, MD, recently stated, there is no such thing as a standard that is static, but we are reaching a time when the expectation is that information will be shareable.
No one would argue that having two parties speak the same language is the most effective way to exchange information, but as we work toward that nirvana, it is critical to have our Google Translate equivalent to realize short-term goals. Modes of information exchange like HL7, HL7 FHIR®, SMTP, and APIs, among others, can work together to share critical elements and relay meaningful messages to caregivers.
Understanding the value of IT systems: Any hospital CIO will tell you they and their teams manage hundreds of IT systems—sometimes thousands, if it is a large health system. That means working with dozens of different vendors and data sources. The value that resides in those systems becomes diluted when there’s no backend integration that allows the systems to “talk” to one another and exchange information that streamlines workflows and benefits patient care.
For example, hospitals often have directory, schedule, and contact preference data stored in separate systems. When integrated, these three vital data feeds can greatly influence the flow of communication. When a person or a system generates a message, the hospital’s directory, schedules, and preference data guide where it flows, to which device, and then, how it might be escalated if not acted on in a pre-determined amount of time.
This kind of information exchange is key to enabling staff with better mobile alerting and communication technology that interoperates with the hospital’s electronic health record (EHR) and helps staff address time-sensitive patient needs as quickly as possible.
For an inpatient medication request,
Another scenario is a consult request:
Through integration with the CPOE and EHR,
When two systems, like the EHR and clinical communications platform in the above use cases, can combine key information via a shared language (or translator engine), the benefits are numerous.
Healthcare organizations can:
This type of interoperability may be classified as “small” (individual patient)—versus “big” (population level and beyond) and “long” data (wrapping around the individual and telling their health story over time)—by the ONC in its nationwide interoperability roadmap. While we all work together to realize our shared vision of a seamless data system, the technology at our fingertips can help provide meaningful advances in patient care today.
Visit Spok and the other vendors in the HIMSS17 Interoperability Showcase to see how we’re collaborating to stay on track with what technology makes possible.
Rob Wilder is a senior product manager for all alerting and workflow solutions at Spok and leads Spok’s Integrating the Healthcare Enterprise (IHE) participation. He has more than 15 years of experience in healthcare software with specialties in product management, feature planning, product launch processes, and integration program management.
Visit the HIMSS17 Interoperability Showcase to see how we’re collaborating to stay on track with what technology makes possible. Come to Booth 9000, Hall F.#EmpowerHIT