Medical Software Update Management in Heterogeneous Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for maintaining and updating medical practice software in heterogeneous computing environments are cumbersome, error-prone, and require lengthy user-machine interactions, especially in medical practices or laboratories with diverse computing hardware and operating systems, making it difficult to connect and extract data from both legacy and modern medical devices.

Innovation Solution

A method and system for updating medical practice software in a local network that involves determining software versions, receiving and transmitting software patches to devices that need updates, and installing them automatically, without requiring user intervention, using a centralized computing device that can manage and maintain a local database of software versions and communicate securely within the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual update methods are used in heterogeneous computing environments, then user control and compatibility checking are improved, but update time and operational complexity increase significantly

Engineering Contradiction:
Improveupdate compatibilityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The computing devices automatically perform update operations including downloading, installing, and configuring software updates without requiring manual user intervention. The system self-manages the entire update lifecycle, eliminating the time-consuming manual processes while maintaining compatibility through automated version checking and dependency resolution.

Inventive Principle:
Principle #25Self-service

2Stability of the object's composition

If centralized update management is implemented, then update consistency across network is improved, but network bandwidth consumption and server load increase

Engineering Contradiction:
Improvesoftware version consistencyVSAvoidnetwork bandwidth
Core Design Contradiction:
Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The update distribution process is segmented into multiple stages: central server prepares update packages, local caching servers store updates locally, and computing devices download from the nearest available source. This hierarchical segmentation reduces central server load and distributes network traffic efficiently, maintaining version consistency while minimizing bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Update packages are prepared, validated, and staged in advance on central and local servers before actual distribution to computing devices. This preliminary action allows for pre-processing and optimization of update content, reducing the actual transfer time and network load during deployment.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automatic update installation is enabled, then user intervention time is reduced, but risk of installation errors and system conflicts increases

Engineering Contradiction:
Improveupdate installation speedVSAvoidinstallation stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements comprehensive feedback mechanisms including pre-installation compatibility checks, real-time installation monitoring, and post-installation validation. Each update operation generates status feedback that is analyzed to determine success or failure, allowing the system to automatically rollback or notify users of issues, thereby maintaining high reliability while enabling automatic installation.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Before automatic installation executes, the system performs preliminary compatibility assessments, creates system state backups, and validates update packages against known conflict scenarios. These cushioning measures prevent installation errors from propagating, ensuring system stability while maintaining automated operation.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS20230386657A1Medical software for displaying and analyzing blood glucose data for use in a heterogeneous computing network in medical practices
Publication Date: 2023.11.30 ROCHE DIABETES CARE INC
  • US20230386657A1 patent drawing
  • US20230386657A1 patent drawing

AI summary

A method for updating medical practice software for a plurality of computing devices of a local network, comprising: determining, by a first computing device of the plurality of computing devices, what versions of the medical software are installed on the plurality of computing devices; receiving, at the first computing device, at least one software patch comprising at least one update for a version of the medical software installed on the plurality of computing devices; identifying, by the first computing device, which of the computing devices of the plurality of computing devices has installed thereon a version of the software that requires the software patch; transmitting, by the first computing device, a copy of the software patch to at least one of the computing devices that have been identified; and installing the software patch to update the medical practice software on the at least one computing device.