Medical Device Server Interoperability via Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The interoperability of medical devices is hindered by proprietary communication standards, making it difficult for caregivers to coordinate usage, monitor status, and schedule maintenance across different devices and locations, particularly for medical infusion pumps.

Innovation Solution

A medical device network system that employs a medical device server to manage and communicate with various medical devices using metadata-based messaging, allowing for interoperability across different brands and types of devices, enabling remote monitoring, therapy administration, and maintenance scheduling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proprietary communication standards are used by different medical devices, then each device can maintain its own operational integrity and reliability, but interoperability among devices deteriorates, making coordination and monitoring difficult

Engineering Contradiction:
Improvedevice operational integrityVSAvoidinteroperability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a server as an intermediary component that receives data from multiple medical devices using different proprietary standards and presents unified access to caregivers. The server acts as a mediator that translates and harmonizes communications between devices with incompatible standards, enabling interoperability without requiring changes to the devices themselves. This resolves the contradiction by maintaining device reliability while achieving system-level adaptability through the mediating server.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The server is designed with universal functionality to handle multiple types of medical devices with different proprietary standards simultaneously. It provides a unified interface for caregivers to access and control various devices, making the system adaptable to diverse device types while maintaining each device's operational integrity. This multi-functional approach enables interoperability across different device ecosystems.

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

2Adaptability or versatility

If multiple types of software and hardware are used to access medical device information, then comprehensive access to device data is achieved, but system complexity increases, making therapy administration difficult

Engineering Contradiction:
Improvedevice data accessVSAvoidsoftware and hardware requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the complexity of interfacing with multiple proprietary device standards from the caregiver's workflow and consolidates it in the server. The server handles all the complex communication protocols and data formatting, presenting a simplified unified interface to caregivers. This extraction reduces the apparent complexity for users while maintaining comprehensive device data access capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The server serves as an intermediary that absorbs the complexity of multiple device interfaces and communication protocols. Instead of requiring caregivers to manage multiple software and hardware interfaces, the server mediates all communications, translating diverse device data into a unified format that simplifies therapy administration and device monitoring.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If medical devices are distributed in different locations, then patient care coverage is improved, but device status monitoring and usage coordination become more difficult

Engineering Contradiction:
Improvepatient care coverageVSAvoiddevice status monitoring
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where devices automatically report their status, usage data, and operational parameters to the server. The server collects this feedback from distributed devices and presents consolidated information to caregivers, enabling remote monitoring of device status across different locations. This automated feedback system makes distributed device monitoring as easy as centralized monitoring.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system enables self-service monitoring where devices automatically transmit their status information to the server without requiring manual intervention from caregivers. The server autonomously collects, stores, and presents device status data, allowing distributed devices to be monitored as if they were locally present, thereby improving patient care coverage without increasing monitoring difficulty.

Inventive Principle:
Principle #25Self-service

4Ease of manufacture

If manual maintenance scheduling is used for medical infusion pumps, then maintenance can be performed, but time loss and inefficiency increase due to lack of automated tracking

Engineering Contradiction:
Improvemaintenance performanceVSAvoidmaintenance scheduling time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent implements self-service maintenance tracking where the medical infusion pump automatically monitors its own operational parameters, usage hours, and maintenance requirements. The device self-reporting data to the server eliminates the need for manual maintenance scheduling and tracking, reducing time loss while ensuring maintenance is performed based on actual device needs rather than estimates or memory.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes continuous feedback between the infusion pump and server regarding device status and maintenance requirements. The pump provides real-time feedback on operational metrics, and the server uses this feedback to automatically generate and manage maintenance schedules, eliminating manual scheduling time loss while ensuring timely maintenance performance based on actual device conditions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3540741B1System for controlling medical devices
Publication Date: 2022.10.26 SMITHS MEDICAL ASD INC
  • EP3540741B1 patent drawingFigure 1
  • EP3540741B1 patent drawingFigure 2
  • EP3540741B1 patent drawingFigure 3

AI summary

Methods and systems of patient treatment are disclosed. The methods and systems include use of medical device informatics to modify and validate therapies and drugs used in those therapies. In certain embodiments, a medical device, such as a medical infusion pump, interfaces with a server to administer the patient treatments. In one such embodiment, a method for use of metadata on medical devices is disclosed. A method includes associating metadata with one or more medical devices, the metadata corresponding to an attribute of the medical devices. The method also includes storing the metadata on a server, the server configured to communicate with each of the medical devices by using the metadata.