supported devices

Hi Alistair,

First off, thank you for your interest in our project. Developing drivers (device-adapters, as we call them) is a time consuming process and something we generally only do for funded projects and devices we have in the lab. That said, the beauty of open source software is that anyone can write the device-adapters and contribute them back to the community. To enable this activity, generally two things are needed: the protocol manual/description and a device to test your code. I'd love to have a look at the GE, NK and Mindray protocols! I haven't had the time or need to investigate them personally. Would you mind sharing the links or documents below? Maybe we can help enable someone out with our efforts here.

The good news is that we already support several "modern" patient monitors. We have developed a device-adapter for the Philips MX800. We also have existing Drager Medibus device-adapters developed and a Drager Infinity monitor in the lab that we will hopefully have full support for soon. We also have a GE Carescape B850 in the lab that's in the queue. We don't do a particularly good advertising what devices we support. I am going to try and find the time to add this information to our main website.

Thanks,
Jeff

Hello again Jeff-

Thank you for all the support, it's been very helpful.  

We're currently testing our prototype music controller with an MP70 but are limited to a software version "E".  We have access to an Intellevue MP30 with software version "J" and when we connected to the LAN port it was streaming data.  Do you know if the MP70 driver works with the MP30 or any Intellevue MP model with software G-K?  

Also, we just received three MX800 monitors.  Would it be at all possible for us to get the device-driver for the MX800 in case we're not able to upgrade our software for our MP70s? 

Thank you again for all your help.

Best,
Alistair

Jeff-  Great news that you have GE and Drager drivers in the works.  There actually aren't that many different types of anesthesia machines so, not to downplay the work involved, a complete set of drivers doesn't seem impossible.  I don't think I can attach the .pdf file here for Nihon Kohden's RS232 protocol so I'll send it an an email attachment.  (note: our new NK anesthesia machines require the purchase of an $800 interface to establish an RS232 port connection).

Here is a link to Mindray's DIAP protocol:
http://res.mindray.com/na/media/products/document/DIAP%20Communications%20Protocol%20Service%20Manual.pdf

Alistair

P.S> this isn't really a driver, but an open source program for numeric data from a Datex Cardiocap5:  http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3788264/

Thanks for the information Alistair! Hopefully socializing this information will help further the efforts of our community as a whole.

Developing device-adapters in parallel with developing OpenICE is a cart before horse situation. In a perfect world, medical devices would natively 'speak' to OpenICE using a yet to be completed ICE standard. The internal team here at MD PnP is focused on developing the infrastructure that comprises OpenICE, rather than supporting soon to be legacy serial communication protocols. Yet to demonstrate and utilize this new infrastructure's functionality, we need to support current devices - as a matter of fact adoption is impossible without this support! We're stuck walking a fine line between supporting devices and developing new infrastructure functionality. The hope is that we can create enough interest in this effort that community members will help expand our list of support devices. I know MD PnP can't do it alone...

Thanks,
Jeff

Hello Jeff-

will the MP70 driver work with the mx800? We are not having any success with the MP70 version E, MP30 version J, or MX800 version K. We don't know if this is a driver issue or not.

thanks,
Alistair

Hi Alistair,

Please try the connection again with OpenICE v0.6.2. We fixed a critical bug that affected the Philips device-adapter software.

We have successfully tested a MP70 rev J and MX800 rev J with this software revision.

Thanks,
Jeff