Philips VS2 monitors

[Michael Lacriola]

CL 5.8.5, AIX 6.1

Anyone using VS2 monitors with Cloverleaf? Apparently these are direct connect devices to the interface engine. I am trying to utilize multi-server connections.

I’ve divided up the inbound threads based on floor and odd/even. I am also limiting to 100 connections per thread. I am also not sending replies back. The threads do not show connectivity. When they do connect , it should show me how many clients are connected. Is there any other config that I am missing?

What appears to be happening is that the value of OBR-7 (date/time) seems to be way off from the date/time in the MSH (by days). I’m curious if this is because the monitor was in demo mode, or is there some sort of cache going on.

Any insight to configuring these devices for Cloverleaf would be appreciated.

Topic

[David Barr]

We were thinking about getting some of those monitors and interfacing them to Epic, but it looks like we probably won’t do that due to cost issues. Our plan was to use our Capsule Tech DataCaptor server to send the data to Epic.

When I’ve used multi-server threads in the past, the thread status doesn’t show the number of connections. I think you’d have to use the “netstat” command or a similar tool to see how many clients are connected.

The OBR timestamp issue seems like a problem with the device and not with Cloverleaf.

[Michael Lacriola]

I’m now told that they expect replies back (a change from what I was originally told). Does the regular hl7_reply_gen work for multi-server connections?

I received an error back “Unable to deliver to specified server connection.”

[Jim Kosloskey]

Michael,

Your reply proc needs to set the metadata DRIVERCTRL.

Like this:

msgmetaset DRIVERCTL [msgmetaget DRIVERCTL]

At least that is the way I do it.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Brandon Grudt]

David Barr wrote:

We were thinking about getting some of those monitors and interfacing them to Epic, but it looks like we probably won’t do that due to cost issues. Our plan was to use our Capsule Tech DataCaptor server to send the data to Epic.

When I’ve used multi-server threads in the past, the thread status doesn’t show the number of connections. I think you’d have to use the “netstat” command or a similar tool to see how many clients are connected.

The OBR timestamp issue seems like a problem with the device and not with Cloverleaf.

I am getting a DataCaptor server for a project we are doing with Mindray.  From what I hear, it is more specially adapted to bedside monitors.  Do you network most/all your bedside devices through it?  If so, do you also pass them through the Cloverleaf engine so that they hit it for monitoring and tweaking?

[Michael Lacriola]

Jim,

Code seems to be working. More testing to happen next week. I took a copy of hl7_reply_gen and created a tcl file called vs2_reply_gen.tcl. Added the code:

msgmetaset $ackmh DRIVERCTL [msgmetaget $mh DRIVERCTL]

right before:

return “{$disp $mh} {OVER $ackmh}”

and started it all up after adding the vs2_reply_gen to the IB tps proc stack of the threads defined to receive data from those monitors. I’m curious as to why Infor doe snot supply a Tcl proc for multi-server ACK/NAKs. Easy fix, but should not have been necessary.

Thanks. Project moving forward and that’s what matters.

[Charlie Bursell]

Confusing.  hl7Raw_ack already provides for multi-server support.  Either use it as is or modify it

[Author]

Replies