Surgical Control Subsystem Dynamic Software Version Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current teleoperated surgical systems require multiple full systems for different hardware and software configurations, leading to high testing burdens for manufacturers and limiting the ability to use different subsystems interchangeably without extensive testing.
Innovation Solution
A method and system that allow a single control subsystem to manage and configure multiple patient-side subsystems with different hardware and software configurations, enabling a common software version to be used across subsystems, and allowing for dynamic reconfiguration and updating of software versions without interrupting surgical functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple full systems are used for different hardware and software configurations, then system compatibility and functionality are ensured, but device complexity and testing burden increase
Solution Approach 1:
The control subsystem is designed to universally support multiple patient-side subsystems with different hardware and software configurations through a common interface and configuration management mechanism, eliminating the need for separate dedicated control systems for each configuration type
Solution Approach 2:
The system is divided into independent modular components where the control subsystem manages configuration information and software versions separately from the patient-side subsystems, allowing each component to be updated and configured independently without affecting the entire system
2Adaptability or versatility
If multiple full systems are used for different configurations, then subsystem interchangeability is supported, but testing burden and time increase
Solution Approach 1:
The control subsystem pre-configures and validates software versions and configuration information before subsystem connection, maintaining a database of valid hardware-software combinations to enable rapid subsystem interchange without requiring extensive runtime testing
Solution Approach 2:
The system implements validation mechanisms that provide feedback on configuration compatibility, automatically detecting and reporting incompatible hardware-software combinations to prevent invalid configurations from being deployed
3Reliability
If software versions are updated across subsystems, then system consistency is improved, but system downtime and operational interruption occur
Solution Approach 1:
The control subsystem dynamically manages software version distribution and updates across multiple patient-side subsystems, allowing selective updating of individual subsystems while maintaining overall system operational continuity through staged deployment and rollback capabilities
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods, systems, and apparatuses for controlling surgical systems. In one aspect, a method includes obtaining, at a control subsystem associated with a surgical system, hardware configuration information from a first patient side subsystem that is communicatively coupled to and controlled by the control subsystem; determining a software version to be used by the control subsystem and the first patient side subsystem, wherein determining the software version includes selecting the software version from among a plurality of software versions, and wherein each software version of the plurality of software versions is associated with a particular patient side subsystem; instructing the first patient side subsystem to use the software version; determining whether the software version is currently loaded on the control subsystem; in response to determining that the software version is not currently loaded on the control subsystem, loading the software version on the control subsystem; and initializing the surgical system.