Patient Interface Device Local Database for Network Independence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current patient interface devices in healthcare are limited in their contextual awareness, relying on continuous connectivity to patient databases for medication delivery protocols, making them vulnerable to network failures and unable to utilize the full extent of available data for enhanced automated medication delivery.

Innovation Solution

A system of communicatively interconnected patient interface devices that store patient databases locally, with a gateway for automatic updates from patient-affiliated data sources, enabling each device to generate patient-specific guidance data sets for independent operation and data management, including medication administration and monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If patient interface devices continuously connect to patient databases via wired or wireless means, then contextual awareness is maintained, but system reliability deteriorates due to network failure vulnerability

Engineering Contradiction:
Improvecontextual awarenessVSAvoidnetwork connectivity reliability
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The system segments the centralized database functionality into distributed local databases on each patient interface device. Each device maintains its own database and can operate independently, eliminating the single point of failure represented by continuous network connectivity while preserving contextual awareness through local data storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by pre-loading patient data and medication protocols into local databases before network disconnection occurs. This allows devices to maintain full operational capability and contextual awareness even when disconnected from central networks, resolving the reliability issue while preserving information access.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If patient interface devices store patient databases locally, then device independence and reliability are improved, but device complexity increases

Engineering Contradiction:
Improvedevice independenceVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a universal data synchronization protocol that enables each patient interface device to function both as a standalone unit with local database and as a networked device. This multi-functionality allows the same device architecture to support both independent operation and centralized connectivity, managing complexity through standardized interfaces.

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

Solution Approach 2:

The system uses copying by creating local replicas of patient databases on each device rather than requiring complex distributed database management. This simplifies the architecture by using straightforward data duplication and synchronization mechanisms instead of complex consensus protocols or distributed query systems.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If automated logic devices are implemented in infusion pumps, then medication delivery precision is improved, but system vulnerability to network failures increases

Engineering Contradiction:
Improvemedication delivery precisionVSAvoidautomated system reliability
Core Design Contradiction:
Manufacturing precisionVSReliability

Solution Approach 1:

The system changes the operational parameter from network-dependent automated control to locally-stored automated control. By storing medication delivery protocols, patient-specific parameters, and decision logic locally in each device's database, the automated logic continues to provide precise medication delivery while becoming independent of network status, thus improving reliability without sacrificing precision.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10811131B2Systems and methods for intelligent patient interface device
Publication Date: 2020.10.20 BAXTER INT INC
  • US10811131B2 patent drawing
  • US10811131B2 patent drawing
  • US10811131B2 patent drawing

AI summary

A system for use with one or more sources of patient-affiliated data corresponding with a group of patients. The system may contain a plurality of patient interface devices for interfacing with the group of patients. Each patient interface device may store a database that includes information related to each patient of the group of patients. Each patient interface device may be operable to generate a patient-specific guidance data set that may be used by the patient interface device to interface with a patient of the group of patients. The plurality of patient interface devices may be communicatively coupled to patient-affiliated data and a therapy database via a patient interface device gateway. The patient-specific guidance data sets may be automatically updated.