top of page

TechTips: Integrating an Interoperability Library

Overview:

Standard medical device interoperability and communication consist of a lot of details. The InnoVision Medical Device Interoperability Library simplifies this by encapsulating all those details. Instead, you can focus on just delivering the data to our API and the work of compliance is taken care of. The Interoperability Library supports many standard communication protocols (TCP/IP, DNS, HTTP, NTP, TLS, SSL, X.509, HL7, IHE PCD, IEEE 11073, etc.), but if customization is desired then the API is extensible.


Getting Started:


The DeviceProfile contains information about the sender’s device. Here we are storing the sending application, the sending facility, the device ID (EUI-64), the manufacturer, and the model. This information is used by the client to help build messages.

We create the InteropClient with the device profile.

We add a generic HL7 data endpoint that will connect using a standard MLLP protocol using the following properties. From left to right are the name, host, port, tls, receiving application, and receiving facility. The receiving information is a detail of HL7 messaging and represents the name of the receiver and its facility. This endpoint will send the typical device observations (settings, measurements, and mode).

Now that we have an endpoint to send data to, we run the client.

As data becomes available, we call sendData on the client and pass in the data using the DataCache class.



24 views0 comments

Comments


bottom of page