ED PulseCheck Interoperability for a High-Performance ED

Interoperability package for ED PulseCheck customers that need to interoperate with their hospital HIS.

Historically, hospital clinicians and administrators believed that specialized systems such as EDIS offer features and functions for the individual clinician that are superior to hospital information systems (HIS) ED modules. However, they were silos and disconnected from everything else in the hospital. With the increased need to interoperate between all departments within a hospital and improve both patient care and safety, an HIS that includes an EDIS module with “good enough” capabilities has been viewed more favorably, despite the obvious tradeoffs.

What in fact is needed is an EDIS that fits into the hospital’s overall IT strategy, driving ED clinical and financial performance while seamlessly providing true bi-directional interoperability with the hospital’s HIS. This solution needs to interoperate with the hospital’s HIS at the same level as an HIS’ own ED module while enabling the ED clinicians to fully address their clinical and medical necessity documentation needs. This solution must also provide the required ED visibility into the status of key hospital resources that directly impact ED performance.

Picis offers Picis ED PulseCheck^® customers proven, operational and true bi-directional interoperability and automation of workflows for major HIS including Eclipsys, GE, McKesson, Meditech, Siemens, Cerner, and Epic in key areas such as medication administration and reconciliation, integration with clinical documentation, orders management and integration with EMR.

ED PulseCheck maintains workflow while co-existing with other systems using the Clinical Context Object Workgroup (CCOW) standard protocol to virtually link different applications together so that the user sees them operate in a cohesive way. A URL link interface also allows another web-based system to be accessed from the ED PulseCheck toolbar. The link passes user and user authentication and patient information back and forth so that patient and user context can be shared without using CCOW. The ED PulseCheck SDK allows another application to call ED PulseCheck in context, and pull up a PDF of the patient’s chart. And TouchPoint ED^® is used to make interface management easier.

The result is that ED PulseCheck provides true bi-directional order entry (orders in and orders out), inbound masterfile updates for service/charges/formulary/physician staff, bi-directional pharmacy, bi-directional admission/discharge/transfer (ADT), outbound discrete, outbound to EMR, inbound Rapid Clinical Record for view into patients’ previous hospital visits, and HIE/CCD. It also supports multiple drug databases and multiple feeds. And TouchPoint ED allows a hospital to configure what data elements are sent, in which Health Level Seven (HL7) segments they are sent, and when they are sent.