Network Variable Services for Patient Care Device Node Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing patient care devices face difficulties in updating and redesigning due to the need for rewriting inter-node communication instructions whenever changes are made, such as adding or removing nodes, changing communication mediums, or updating software, which complicates the process.
Innovation Solution
The implementation of an embedded communication system that utilizes network variables managed by services running on nodes, allowing data to be shared transparently and treated as local, eliminating the need for mainline applications to track data sources or recipients, and enabling changes without modifying the applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If inter-node communication instructions are hard-coded in mainline applications, then data communication between nodes is reliable, but any changes to node configuration or communication medium require rewriting the applications
Solution Approach 1:
The patent introduces a service layer as an intermediary between mainline applications and inter-node communication. This service layer handles all data transmission, reception, and processing between nodes, allowing applications to interact with remote data through simple variable access rather than complex communication protocols. The service layer translates high-level application requests into low-level communication actions, thereby providing adaptability to configuration changes without requiring application modifications.
Solution Approach 2:
The patent segments the communication system into distinct layers: mainline applications, service layer, and communication infrastructure. This segmentation allows each layer to operate independently, with the service layer absorbing the complexity of node configuration changes, communication medium variations, and data routing. Applications remain simple and unchanged while the service layer adapts to accommodate system modifications.
2Ease of operation
If mainline applications directly manage data retrieval and tracking across nodes, then data access is precise and controlled, but applications become complex and difficult to maintain
Solution Approach 1:
The service layer implements self-service mechanisms by automatically managing data retrieval, transmission, and synchronization between nodes. When a mainline application accesses a network variable, the service layer autonomously handles the complexity of locating the data source, establishing communication channels, and ensuring data integrity. This eliminates the need for applications to implement complex data tracking logic while maintaining precise and controlled data access.
3Reliability
If communication protocols are embedded in mainline applications, then communication control is tight and reliable, but system updates and redesigns become difficult
Solution Approach 1:
The patent extracts communication protocol implementation from mainline applications and consolidates it into a dedicated service layer. This extraction allows communication protocols to be updated, modified, or improved without affecting application code. The service layer acts as a buffer that absorbs protocol changes, ensuring that reliability is maintained while ease of updates is improved. Applications continue to rely on the service layer for communication, ensuring reliability without being coupled to specific protocol implementations.
Data Source
AI summary
A first node of a patient care device processes data relating to the patient care device and sets a public variable equal to a value of the data. A second node receives the public variable from the first node, sets a private variable equal to the value of the public variable, and executes a software program that reads the private variable but not the public variable. In other embodiments, the second node checks to see if the public variable is registered at the second node, and if so, uses the private variable in carrying out a function. The first node executes a first software program that sets the public variable to the value and relies on a service to share the value with the second node. The sharing occurs despite the first software program not containing any instructions for transmitting the value or variable to the second node.