Hello,
I am trying to export data from the philips intellivue MX800 monitor, using the lan udp protocol.
Does anyone have an idea of how to start, or any manuals for that?
Any help would be much appreciated.
Thank you

hello,

what problem do you encountered during your extraction of data?

The information on programming a LAN (or RS232) data client for the IntelliVue monitors is detailed in the document "X2_MP2_5_20_30_40_50_60_70_80_90_MX800_Patient_Monitor_Rel._H.0___Data_Export_Interface_Program._Guide_M8000-9305H_(ENG).pdf"

You can find this document in the InCenter. If you don't have access to this document in InCenter, you can ask one of your Philips service representatives.

Hai, how much message MX800 will sending out (for 5 minutes) when running in 8waves monitoring to the patient. Thank you for help

It depends on what you query the monitor for. The communication language allows you to ask for specific data at specific intervals, so you are not limited by what is shown on the screen.

You can ask the monitor to send out unsolicited stream of messages containing all the data you have requested, at an interval you specify - in this case, the number of messages can be calculated using the interval.

Or, you can program your data client to actively query the monitor at the interval you prefer. Then, in response to each query you will get a solicited message containing the data you requested.

Hello Dr. Chandana,
I have a questions. About the IntelliVue MX800. How can we send the IHE compliant messages from the device to the EMR/EHR/HIS systems?

Thanks
Tim

Hi Tim,

The IntelliVue LAN data protocol is based on UDP/IP, so the monitor is not able to send TCP/IP based HL7 messages out of the box. For this purpose, you need to use the HL7 communication interface provided by the central station (the IntelliVue Information Center).

The IHE standards use the MDC nomenclature for clinical concepts, while the IntelliVue devices (both the monitor and central station) use the MDIL nomenclature. As most of MDC is derived from MDIL, mapping the concepts to an IHE compliant EMR would not be difficult.

The easiest way to map the HL7 messages from the central station to your EMR (if you don't have an HL7 broker yet), is to use the IntelliBridge Enterprise integration engine, that comes with the concepts from the IntelliVue side pre-mapped.

Hello Dr. Chandana,
Thank you very much for your response. Do you know which IHE profiles and Actors have been verified and tested for the MX800?

I was wondering if you would be so generous to provide me a workflow diagram to help me understand the HL7 messaging between the PCD Device aka MX800 (DEC) and the EHR/HIS (DOC) system? it would greatly help me understand visually.

Also how would an ADT message flow from the HIS to the Device and vice versa? Since as I recall IHE would profile a bidirectional data workflow acknowledgement.

I guess this scenario would only be application if the device is connected to the LAN. However what would be the case if you are at an offsite location and the only way the device can be connected is via the RS232 connection with a stand alone workstation?

Thank you

Best wishes
Tim

Hi Tim,

As I mentioned, the MX800 itself (and the LAN data export interface) does not provide IHE compliant messaging - it is the central station (IntelliVue Information Center) that does so. The communication between the MX800 and IIC is a private protocol.

The IHE conformance statement for IntelliVue Information Center can be found at: http://www.healthcare.philips.com/main/about/Connectivity/ihe_statements/pm_statements.wpd

This conformance statement refers to the integration engine IntelliBridge SC200, which has been renamed to IntelliBridge Enterprise.



If you connect the device to a workstation, you can use the LAN and/or the RS232/MIB connections. The communication protocol is exactly the same - only the transport is different (LAN uses UDP/IP, while the serial uses RS232/IrDA). When using LAN communication with a workstation, you need to provide the monitor with an IP address (as there is no central station online to do that).

In both cases you need to write a client that would parse the messages. The LAN Data Export Guide I reference in an earlier post in this thread shows you how to do that. As the messages are identical, you can use the same client for both LAN and serial communication - as long as you handle the different modes of transport (which is pretty easy, using pre-built classes on .net framework, even if you use a high-level language like Visual Basic).

Our Solutions Architects can help you figure out what works best for your specific needs. Your local Philips representative should be able to put you in touch with them. In case you don't have the contacts of your Philips rep, I can ask him/her to contact you.

Yes. There's a lot to be said for keeping things simple.

Unfortunately, Geoff, when it comes to interoperability, nothing is simple. If you follow Tim Gee's blog (http://medicalconnectivity.com) you can see how complicated things can become, as soon as you try to standardize things. In the past, many standards (OpenInterface, MDIL, MIB) were proposed as standards for medical device connectivity. Some manufacturers invested heavily in complying to those standards - but in the end, no one else did. That left the industry fractured with many different "standards", with hardly anyone willing to invest in the next great thing. I hope IHE will succeed where other efforts have failed.

Yes, I'm aware of Tim's blog.

It seems to me that only one or two of the Big Players (in medical equipment) are true innovators.

Meanwhile, I believe I'm right in saying that that part of the world that makes most of the kit these days have something of a reputation for being great copiers of other folk's technology. Those guys don't invest in technology. Their religion is money, and profit (and only that) is their goal.

Myself, I can't see the over-riding imperative for every piece of equipment to talk to each other. Not unless it's the toaster, the 'fridge and the microwave oven, that is.

Hello Dr. Chandana,
Sorry I was unable to to download the pdf files. Can you please send them to me via e-mail. I'll contact my Philips sales rep, the moment she is available. However going back to IHE standards. I was at the Himms2012 conference, attending the Interoperability section.

I think that not only manufacturers are trying to implement this standard i.e Philips, Drager, Siemens, Mindray, Smith Medical etc to state a few. However I came across EHR/EMR & HIS vendors who are in the process of being IHE compliant as well Cerner, Allscripts, SIS etc.

The interesting part is that not only NIST is taking an active role but also FDA has also shown an interest in the IHE standards.

My other question was are you aware of anyone using their in-house development to develop the middleware (DOR & DOF)? just curious?

Thanks
Tim

I haven't actually heard of anyone developing their own middleware, although that doesn't mean there isn't anyone doing it. However, it seems to me to be a superfluous effort, since there are so many commercial and freeware HL7 brokers available. Even with the free stuff you can download off SourceForge you can do quite a lot, and in some cases you can even get some decent support.

Dr. Chandana,
The interface that you mentioned is no different from what other third party vendors that Phillips cooperates with i.e Capsule.

What makes your interface different from Capsule?. Basically in both cases the user has to pay additional cost to retrieve patient data.

I guess the concept of Plug N play device is far fetched at the moment even with the implementation of IHE standards.

Thanks
Tim

Think of it this way: if you write a client for the LAN data export interface, and have that client forward the same data to your EMR in a format that your EMR understands, how much would that cost you in terms of time and money?

If you answered "Low", then that is the best path, as the LAN data export from the MX800 is free of charge.

If you would rather invest those resources elsewhere, Capsule offers you that client, converting the data from the monitor to the format your EMR understands. The IntelliVue Information Center offers you an independent HL7 stream (generated by data it gets from the monitor) and sends it your EMR with MDIL coding. If your EMR does not support MDIL standard, you need an HL7 broker (either commercial or freeware) to translate.



The biggest problem with the concept of a plug and play device is defining whom it plays with, and what it plays. In order for a complex mix of devices and systems to be plug and play, you need to reduce the functionality of the whole system to the level of the lowest common denominator. This is just one of the many issues that need to be addressed.

Hello Dr. Chandana,
Can you please send me the Interface Data pdf that you had mentioned earlier ago. I am unable to download it. Furthermore are there any open source per say Hl7 interface that you can reccomend that I can have a look at. Just for fun sake.

What is your opinion about MIRTH project?

Thanks

Dr. Chandana,
Can you please send me the Data Export program interface guide for MX800, we are currently on rev H.

Thanks

Hi Tim,

I sent you an email from my Philips address. Once you provide me the details, I will send you the document.

Sorry if this sounds like a commercial, but I think its relevant to this thread. I'll keep it brief:

Rather than starting from scratch and building your own interface to these Philips patient monitors, you might want to save time and avoid re-inventing the wheel:

http://www.medicollector.com

Using the MediCollector product, you can quickly and easy stream and export data from Philips patient monitors onto your hard disk.