Hey Thomas,

Sorry for such a long delay in responding. I have been working on a variety on things and this site fell through the cracks.

Thank you for the pull request! This is great work. Keep us posted with how we can continue to help enable your work. I look forward to hearing from you again.

Jeff

Hi guys,

Right now the simulated infusion pump's parameters e.g. meds, rates, etc. are hardcoded. There has always been intent to extend the functionality but it has not been a priority. All of the other simulators are controllable with the Supervisor Simulation Controller. Check out the new documentation for the Sim Controller here: https://www.openice.info/docs/3_apps.html#simulation-control.

Here's a little OpenICE Easter egg - if you have a Fluke ProSim 6 or 8, you can connect the Fluke's serial port to an OpenICE Fluke ProSim Device-Adapter and the Simulation Controller app will control the Fluke as well as the virtual devices!

Thanks,
Jeff

Hi Hyungi,

Thanks for writing. Each medical device exports medical data in a proprietary format that is unique to the device. The format of the data can be found in the technical reference manual of each device. I cannot redistribute the manuals due to licensing, so please talk to the vendor or search other sources. We do however publish the OpenICE Device-Adapters to connect devices to the OpenICE network. The device nomenclature codes (names of vital signs, units, etc) are taken from hRTM which is largely IEEE 11073-10101 nomenclature.

The OpenICE Device Adapter software can be found here: https://github.com/mdpnp/mdpnp/tree/master/devices.
The structure and format of data found in OpenICE is described in IDL and found here: https://github.com/mdpnp/mdpnp/blob/master/data-types/x73-idl/src/main/idl/ice/ice.idl.
If you would like more information about how our system works, check out our new documentation here: https://www.openice.info/docs/1_overview.html.

Thanks,
Jeff

Hey Nathan,

Sorry for taking so long to respond! I've been working on a variety of things lately and this site has slipped through the cracks.

This is fantastic information. We have not had the man power or equipment to debug the mysterious rev K issue so this information is very welcomed! Let us know if you find anything more definitive and consider submitting a pull request if you know how to fix it.

As usual, thanks for contributing your work back to the community.
Jeff

Hey Thomas,

This is really cool! Thanks for sharing your progress - keep us posted.

Thanks!
Jeff

Hi JD,

Thanks for your question! The short answer is that EMR communication/integration is done through HL7 (http://www.hl7.org/). Our preferred HL7 version is the development version of HL7 FHIR (http://hl7-fhir.github.io/). If you're interested in using HL7 FHIR and java (what OpenICE uses), a fantastic learning resource is the HAPI FHIR project (http://jamesagnew.github.io/hapi-fhir/).

We have only begun to experiment with EMR integrations, but our current state is best illustrated by the OpenICE Supervisor app 'HL7 Exporter'. You can use the app by installing OpenICE: http://mdpnp.sourceforge.net/. And you can check out the code here: https://sourceforge.net/p/mdpnp/code/ci/master/tree/interop-lab/demo-apps/src/main/java/org/mdpnp/apps/testapp/hl7/. The app will take data from the active patient and export it via HL7 at a user defined time interval.

Our HIMSS15 demo app illustrated some mock "auto-validation" of medical device data that was then exported using the HL7 export app to a fake EMR. That system is representative of some of our future development ideas that will be on our roadmap eventually. For now, there is still a lot of work to do in this area...

Feel free to continue the conversation. Thanks,
Jeff

Hey Rado,

Well... no, not at this point. We have never really built anything for the use case of integrating medical devices with OpenICE without the integration to any other system or device.

I will certainly make note of this for a potential future feature. Not being able to start OpenICE without a network connection a known issue. The problem with your scenario right now is that technically you are running two applications that are communicating over a network. 1 is PB840 device-adapter. 2 is OpenICE Supervisor data recorder app. In this case, the communication network you want to use is via the loopback adapter - which DDS doesn't currently accept as a network interface. Since this is a known issue with a use case behind it now, there might be something we can do but at this time it isn't possible.

Thanks,
Jeff