Medical Device Faceplate with Wireless Update Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Smart IV pumps face challenges in updating their formularies efficiently, as hospital personnel must manually track down each pump or use a wireless network, which requires constant power and bandwidth, limiting updates to once or twice a year due to the need for all pumps to be powered on and connected simultaneously.

Innovation Solution

A wireless computer integrated into a medical device faceplate with a machine-readable identifier and a communication port that allows updates to be stored and installed when the device is ready, reducing unnecessary bandwidth consumption and eliminating the need for constant power and manual tracking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If wireless network updates are pushed to all pumps simultaneously, then all pumps can receive updates, but all pumps must be constantly powered on and connected to the network, increasing energy consumption and bandwidth usage

Engineering Contradiction:
Improveupdate installation reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The faceplate module stores update files in its local memory before the medical device is powered on or before the update needs to be installed. This preliminary storage action eliminates the need for constant wireless network connectivity and reduces bandwidth consumption, while ensuring updates are readily available when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The faceplate module acts as an intermediary storage device between the wireless network and the medical device. It receives and stores update files from the network, then transfers them to the medical device when ready, decoupling the update process from continuous network connectivity requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual tracking of each pump is performed, then updates can be installed on each device, but hospital personnel must track down each pump individually, increasing time and labor requirements

Engineering Contradiction:
Improveupdate installation completenessVSAvoidupdate deployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The faceplate module automatically receives update files from the wireless network and stores them locally. The medical device can then self-install updates from the stored files without requiring personnel to manually track down each device, enabling autonomous update deployment across the hospital.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Update files are preliminarily stored in the faceplate module's memory in advance, so when the medical device needs an update, it can immediately retrieve and install from the stored files without waiting for network access or manual intervention, significantly reducing deployment time.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If updates are pushed through wireless network only when pumps are powered on and not pumping, then updates can be installed without disrupting operations, but updates can only be installed once or twice a year due to scheduling constraints

Engineering Contradiction:
Improveoperational continuityVSAvoidupdate frequency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The faceplate module stores update files in its memory in advance during periods when the medical device is not in use or when network bandwidth is available. This preliminary storage enables updates to be installed immediately when the device is ready, increasing update frequency without disrupting medical operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The faceplate module serves as an intermediary buffer that decouples the update delivery process from the medical device operational schedule. Updates can be staged in the faceplate at convenient times and installed when the device is ready, eliminating the need to coordinate updates with device availability and enabling more frequent updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10940262B2Protective medical device faceplate
Publication Date: 2021.03.09 CERNER INNOVATION INC
  • US10940262B2 patent drawing
  • US10940262B2 patent drawing
  • US10940262B2 patent drawing

AI summary

Devices are provided that include a faceplate for a medical device. In embodiments, an identifier chip adapted to be affixed to an exterior portion of a faceplate provides a unique identifier for the faceplate. Accordingly, the identifier chip enables tracking and monitoring of an associated medical device. And, in embodiments, the faceplate includes a visual communication alert indicator to enable the faceplate to provide visual cues a user. As such, the status of the medical device and the faceplate can be easily communicated to the user. Methods to use the faceplate are also provided.