Is anyone using CL to connect medical devices to EHRs or HIS

Hey, Rey,

If you’re referring to sending patient vitals from bedside/surgical devices to an EMR, yes, we are here at Trinity, if indirectly.  We have such interfaces at several of our hospitals.  The data comes from the device, then to a database server, either directly or through a terminal server, which then sends the data on to Cloverleaf.  Some of the vendors we have for the database servers include GE, CapsuleTech, and Philips.  We are currently rolling out this technology to the OR’s and ICU’s in most of our hospitals.

HTH,

TIM

hey Ray,

At Mt. Sinai, we are interfacing all devices thru Capsule, and then from Capsule thru cloverleaf to Epic. Capsule is fed by all patient monitoring equipment in the facility. We are using Raw routes, and capsule is translating. We decided not to save any messages, and we have alerts that go off if there are more than 10 messages in 2 minutes, and if connection drops for 2 mintues. We are moving close to 300,000 messages per day, as vitals are pushed out about every 2minutes.

We’re in the process of implementing Capsule with Epic.  We’re also integrating Spacelabs, but that’s going through Capsule.

We have been using CL for Philips IntelliiVue and multiple Capsule servers for several years now to interface with EPIC.  In most cases we have multiple source systems going to EPIC.  The inbound threads are established as clients.  The outbound thread to EPIC is also a client.  They tend to send in bursts of messages and do not want ACKs back.  So far they work fine.  The engine purely mimics what they had when they were point-to-point with the exception of being able to direct many to one.