OpenICE Community Support Forum

Hi Jeff

We are doing a POC and are planning to add a new device to OpenICE platform. Do you have any documentation that describe the standard process for adding a new device in terms of communication for initial handshake/protocol that needs to be implemented by this device. 

Regards
Vinod

Hi,

I noticed that at least one other user has had difficulties using OpenICE with Philips Rev K devices.

I have been able to successfully connect to Philips MP70 and MP50 devices with Rev G (and I believe the MD PnP lab has Rev J).

I recently had the opportunity to test OpenICE on a Philips X2, Rev K.2. The X2 does not have a serial port, so I used the LAN port on the external battery pack, and ran the monitor in demo mode. OpenICE was able to successfully connect, and is able to extract the numerics alright, but there are problems with the waveforms. Initial waveforms appear in the GUI, but then stop (I was using version 0.6.3 of OpenICE).

The log file shows that the waveforms have "no new samples to emit", and that the physioId of one of the signals is being read in as 0. There is also a DDS error indicating that the participant information was not available for device identity publication (see log file excerpt below).

Initially, and occasionally afterwards, there is valid waveform data in the sample array updates (viewed in the debugger). However, very quickly after starting, the updates start coming back empty. I have written code to export the numerics/waveform data to csv; the numerics data is written fine, but not even the first packet of waveform data is recorded.

I remember seeing the flags INVALID | QUESTIONABLE | UNAVAILABLE in the debugger for the MeasurementState of SampleArrayObservedValue objects (with physioId = 0).

I later tried testing on an X2 with rev J, and the software worked without problems. So there does seem to be a problem with rev K (and possibly newer) devices.

I have compared the export interface manuals for both Rev H and Rev K, and the differences between the two appear to be minimal (a few new objects have been defined).

Unfortunately I have had to send back the X2 rev K I had on loan, so I am unable to do much more hands-on troubleshooting myself at the moment. I do still have log files, and I did spend some time with a java debugger stepping through the code (mostly in AbstractDemoIntellivue and AbstractDevice), so I might be able to answer some questions... But hopefully the above information will be helpful when one of you needs to troubleshoot rev K or higher devices!

Regards,
Nathan

---------------------------------------------------

2015-05-26 14:38:23,524 | WARN | Bean with key 'timeManager' has been registered as an MBean but has no exposed attributes or operations | org.springframework.jmx.export.MBeanExporter | JavaFX Application Thread
2015-05-26 14:38:23,576 | ERROR | [D0000|Reader(80000807)|T=DeviceIdentity|GET_MATCHED Participant DATA]DDS_DataReader_get_matched_publication_participant_data:ERROR: Failed to get discovered_participant_data | com.rti.dds | EventLoopHandler
2015-05-26 14:38:23,576 | WARN | Unable to get participant information for DeviceIdentity publication | org.mdpnp.apps.testapp.DeviceListModelImpl | EventLoopHandler
2015-05-26 14:38:23,617 | INFO | Connecting to >126.3.145.100< | org.mdpnp.devices.DeviceDriverProvider$SpringLoadedDriver | Thread-15
2015-05-26 14:38:23,849 | INFO | Start emit fast data for period 2000ms | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | Network Loop
2015-05-26 14:38:24,375 | INFO | ProductionSpecification | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:24,376 | INFO | [[specType=SERIAL_NUMBER,componentId=ID_COMP_PRODUCT,prodSpec=DE037A8036], [specType=PART_NUMBER,componentId=ID_COMP_PRODUCT,prodSpec=M3002A], [specType=PART_NUMBER,componentId=ID_COMP_APPL_SW,prodSpec=S-M8102-1501A ], [specType=SW_REVISION,componentId=ID_COMP_APPL_SW,prodSpec=K.21.39 ], [specType=PART_NUMBER,componentId=ID_COMP_CONFIG,prodSpec=S-M8102-1401A ], [specType=SW_REVISION,componentId=ID_COMP_CONFIG,prodSpec=K.21.39 ], [specType=PART_NUMBER,componentId=ID_COMP_BOOT,prodSpec=S-M8000-1301A ], [specType=SW_REVISION,componentId=ID_COMP_BOOT,prodSpec=A.16.24]] | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:24,378 | ERROR | [D0000|Reader(80000807)|T=DeviceIdentity|GET_MATCHED Participant DATA]DDS_DataReader_get_matched_publication_participant_data:ERROR: Failed to get discovered_participant_data | com.rti.dds | EventLoopHandler
2015-05-26 14:38:24,379 | WARN | Unable to get participant information for DeviceIdentity publication | org.mdpnp.apps.testapp.DeviceListModelImpl | EventLoopHandler
2015-05-26 14:38:24,382 | ERROR | [D0000|Reader(80000807)|T=DeviceIdentity|GET_MATCHED Participant DATA]DDS_DataReader_get_matched_publication_participant_data:ERROR: Failed to get discovered_participant_data | com.rti.dds | EventLoopHandler
2015-05-26 14:38:24,382 | WARN | Unable to get participant information for DeviceIdentity publication | org.mdpnp.apps.testapp.DeviceListModelImpl | EventLoopHandler
2015-05-26 14:38:27,442 | WARN | No ObservedValue for 0 | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:27,443 | WARN | No ObservedValue for 0 | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:27,444 | WARN | No ObservedValue for 0 | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:27,469 | WARN | No SampleArraySpecification or RelativeTime for handle=2006 rt=null sas=null sar=null unitCode=null | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:28,002 | WARN | MDC_IMPED_TTHOR 1827 will repeat 109 old samples to make up a shortfall | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,002 | WARN | MDC_IMPED_TTHOR 1827 filling in 109 zeros; this should not continue happening | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,006 | WARN | MDC_ECG_LEAD_III 1817 will repeat 872 old samples to make up a shortfall | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,006 | WARN | MDC_ECG_LEAD_III 1817 filling in 872 zeros; this should not continue happening | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,020 | WARN | MDC_ECG_LEAD_II 1817 will repeat 872 old samples to make up a shortfall | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,020 | WARN | MDC_ECG_LEAD_II 1817 filling in 872 zeros; this should not continue happening | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,034 | WARN | MDC_ECG_LEAD_I 1817 will repeat 872 old samples to make up a shortfall | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,034 | WARN | MDC_ECG_LEAD_I 1817 filling in 872 zeros; this should not continue happening | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:28,464 | WARN | No ObservedValue for 0 | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:28,466 | WARN | No ObservedValue for 0 | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
...
org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:30,001 | WARN | MDC_IMPED_TTHOR 1827 no new samples to emit | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:30,002 | WARN | MDC_ECG_LEAD_III 1817 no new samples to emit | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:30,002 | WARN | MDC_ECG_LEAD_II 1817 no new samples to emit | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:30,002 | WARN | MDC_ECG_LEAD_I 1817 no new samples to emit | org.mdpnp.devices.philips.intellivue.DemoEthernetIntellivue | taskExecutor-1
2015-05-26 14:38:30,516 | WARN | No ObservedValue for 0 | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:30,518 | WARN | No ObservedValue for 0 | org.mdpnp.devices.philips.intellivue.AbstractDemoIntellivue$IntellivueExt | Network Loop
2015-05-26 14:38:30,518 | WARN | No ObservedValue for 0 |
...
2015-05-26 14:38:33,593 | ERROR | [D0000|Reader(80000807)|T=DeviceIdentity|GET_MATCHED Participant DATA]DDS_DataReader_get_matched_publication_participant_data:ERROR: Failed to get discovered_participant_data | com.rti.dds | EventLoopHandler
2015-05-26 14:38:33,593 | WARN | Unable to get participant information for DeviceIdentity publication | org.mdpnp.apps.testapp.DeviceListModelImpl | EventLoopHandler


-----------------------------------------------

Hi,

How do I time sync my BBB with time server present on my local network.
At times, time also sets back to Mar 1 2015 after reboots.

Please advise.

Regards

Hello,

I am trying to build the mdpn repo but it looks like https://build.openice.info/artifactory is down. 

This are the error i get:

* What went wrong: A problem occurred evaluating project ':data-types:x73-idl-rti-dds'. > Could not resolve all dependencies for configuration ':data-types:x73-idl-rti-dds:rtiddsgen'.    > Could not resolve org.anarres:cpp-bin:1.2.8-SNAPSHOT.      Required by:          org.mdpnp:x73-idl-rti-dds:0.6.3-SNAPSHOT       > Unable to load Maven meta-data from https://build.openice.info/artifactory/libs-snapshot/org/anarres/cpp-bin/1.2.8-SNAPSHOT/maven-metadata.xml.          > Could not GET 'https://build.openice.info/artifactory/libs-snapshot/org/anarres/cpp-bin/1.2.8-SNAPSHOT/maven-metadata.xml'.             > peer not authenticated       > Unable to load Maven meta-data from https://build.openice.info/artifactory/libs-release/org/anarres/cpp-bin/1.2.8-SNAPSHOT/maven-metadata.xml.          > Could not GET 'https://build.openice.info/artifactory/libs-release/org/anarres/cpp-bin/1.2.8-SNAPSHOT/maven-metadata.xml'.             > peer not authenticated       > Unable to load Maven meta-data from https://build.openice.info/artifactory/remote-repos/org/anarres/cpp-bin/1.2.8-SNAPSHOT/maven-metadata.xml.          > Could not GET 'https://build.openice.info/artifactory/remote-repos/org/anarres/cpp-bin/1.2.8-SNAPSHOT/maven-metadata.xml'.             > peer not authenticated

Hello,

We are trying to use openICE for integration with several different medical devices at the University of Pennsylvania and the surrounding hospitals. We are able to use the demo app that is pre-built but we are having trouble building the code from source.

We have tested this on Windows, Mac and Ubuntu and get to the same stage. We are able to import the project using the eclipse plugin for gradle but there are some bits that don't compile. In particular, the main problem is that the ice environment that is defined in a few idl files is not correctly recognized by the java files (so the most common error is "ice cannot be resolved to a type"). As far as I understand, some java code has to be generated by these specifications but we cannot get eclipse to do it.

Is there some other pluging that we need to install? Or do you think there is some other problem?

Thanks,
Rado

I'd like to email in questions. Is this supported?

Hello Jeff. We're in Missoula working on an OR music volume controller project using OpenICE and Philips MP70 monitors. Do you know what's in the queue for drivers for the newest monitors such as Spacelabs (Xpression), Nihon Kohden BSM 6000 series, Mindray DPM, GE Carescape, Drager Perseus. I know some communication protocols are openly available for NK, Mindray and GE, but wasn't sure if and when they would make their way into OpenICE.
-Alistair MacDonald

hello, I'm looking into this community as a noob to the EMR, EHR, MD PnP, Payer, Provider etc. There is a lot to wrap my head around.

My questions are more related to how you are interfacing with EMRs, and what format you're pushing that data? From a more technical perspective, are you exposing the data through an API? Or are you publishing that data directly to a system? Would love to get a quick overview, from a quasi-technical perspective.

Thanks.

JD
jdietrich@croocial.com