Medical Device Communication Interface Protocol Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional medical device management requires the creation of custom device drivers for each medical device, which is costly and inconvenient, especially when multiple external systems need to communicate with devices that have different output protocols.

Innovation Solution

A medical device communication interface that receives, parses, and translates patient parameters from various medical devices in different formats by identifying protocols and modifying configuration parameters such as baud rate, encoding, data output, count, syntax, and software identification, allowing for universal communication without the need for custom drivers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom device drivers are created for each medical device, then communication compatibility is improved, but device complexity and development cost increase

Engineering Contradiction:
Improvecommunication compatibilityVSAvoiddriver complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a communication interface as an intermediary layer between medical devices and external systems. This interface receives data in various device-specific formats, translates it to a standardized internal format, and then outputs it in the required external format. This mediator approach eliminates the need for custom drivers for each device while maintaining full communication compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The communication interface is designed with universal functionality to handle multiple device protocols and formats through a single unified system. It supports various baud rates, encoding schemes, and data formats simultaneously, allowing one interface to serve multiple device types without requiring separate custom drivers for each.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple custom device drivers are implemented to support different output protocols, then protocol compatibility is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidintegration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The communication interface dynamically adjusts its parameters based on the detected device protocol. It automatically modifies baud rate, encoding type, and data format parameters to match the connected device, then translates the incoming data to a standardized format. This parameter adaptation occurs automatically without requiring operators to configure or select specific drivers.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If device-specific communication protocols are used, then device reliability is improved, but adaptability to external systems deteriorates

Engineering Contradiction:
Improvedevice communication reliabilityVSAvoidsystem integration flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The communication system is segmented into distinct functional layers: a device-specific protocol handling layer that maintains reliable device communication, and a standardized translation layer that provides system-wide adaptability. This segmentation allows each layer to optimize for its specific function while working together to achieve both reliability and flexibility.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8750396B2System, method, and software for communicating with medical devices
Publication Date: 2014.06.10 COVIDIEN LP
  • US8750396B2 patent drawing
  • US8750396B2 patent drawing
  • US8750396B2 patent drawing

AI summary

A method for communicating with medical devices includes receiving, at a medical device communication interface, patient parameters from a first and second medical device in a respective first and second format. The method further includes identifying, at the medical device communication interface, a first and second protocol associated with the patient parameters by comparing the patient parameters and the first and second format to a predefined schema. The method further includes modifying, at the medical device communication interface, a respective configuration parameter for each of the first and second medical devices. The method further includes translating the patient parameters based on the first and second identified protocols and the respective configuration parameter for each of the first and second medical devices.