top of page
Image by Sigmund


Center for Medical Interoperability

The Center for Medical Interoperability organized medical device suppliers and health care systems to work together to define best practices for interoperability.  This included standards and built an integrating layer between IEEE 11073, IHE, IETF to facilitate true plug and play, with maximum security at every layer.  InnoVision Medical Technologies was the first to be C4MI Verified for a gateway device for the Draeger IACS patient monitor system per the issued specification (Clinical Data Interoperability Based on IHE PCD – Semantics, Syntax and Encoding (I01)). 

C4MI logo_edited.jpg

Point of Care Identity Management

Assuring all data being transmitted by a medical device is stamped with accurate patient and location information is key to full interoperability. A trial specification for Point-of-Care Identity Management (PCIM) is in development and is actively being moved to final text. Implementing PCIM means no more entering patient data on the device, and automatic needing to go to 5 medical devices, many of which are small with challenging user input methods, for the patient and accurately entering patient information on each one. There is a more automated and seamless way, and InnoVision solutions already implement it in early form.  InnoVision Medical is leading the effort in the IHE  DEV working group on authoring change proposals and designing Connectathon tests September 12-16, 2022 in Atlanta, GA. A HIMSS22 video showcases the value that PCIM provides in the ICU and step-down unit using the Epic EMR and alternative a RTLS system from GuardRFID.


Harmonized Rosetta and IEEE 111073 Nomenclature for Medical Devices

IEEE 11073-10101 is the standard nomenclature used by medical devices. This list of terms is continually expanding. Search this list to determine how to accurately output the data from sensors and settings. If a new term must be added, there is an application process and because it takes time for group approval of defined terms, private and proposed terms are allowed in the interim. Available terms can be searched using a useful tool called Harmonized Rosetta (RTMMS for short) and is supplied and managed by the National Institute of Standards and Technology.

NIST logo.png

Why is IHE DEV Important for Medical Devices

The IHE DEV technical framework provides state of the art standards for medical device communication. Most interoperable medical devices and data consumers use this framework. Key profiles include: 

  • Device Enterprise Communication (DEC) - Communicate clinical observations from a device. Major EMR vendors are interoperable and support these messages directly.

  • Alert Communication Management (ACM) - Communicate alerts/alarms from a device. Major alerting systems support these messages directly.

  • Rosetta Terminology Mapping (RTM) - Communicate any kind of observations with full semantic understanding. No need for mapping to be  redone privately at each hospital in non-standard ways. Major EMR vendors, alert systems, support this directly.

Medical devices that support these profiles simplify the integration process and require much less manual integration and configuration.


Connectathons - Testing Interoperability

IHE Connectathons allow the interoperability of systems from different suppliers to be validated together. Until systems actually connect together, true interoperability success is unknown.  InnoVision Medical’s gateway solution attached to a ventilator is an example of a report.  Connectathons are generally held a few times per year.

imt mark only.jpg

Our favorite Resources for effectively connecting medical devices to the hospital data network.  Click on the pictures to access original documents.  Give us a call with questions or to discuss.

bottom of page