Multi-Device Patient Encounter Records Without Centralized Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During patient encounters, there is a risk that not all patient data collected by multiple devices will be sent to a server due to network access limitations, resulting in incomplete records.
Innovation Solution
Devices exchange record-identifying information via decentralized networks like WiFi Direct or Bluetooth, allowing a server to request and compile data from all participating devices, ensuring a complete patient encounter record is generated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If devices send patient data to a server only when they have access to a centralized network, then network infrastructure requirements are reduced, but patient data completeness deteriorates
Solution Approach 1:
Devices perform preliminary actions by storing patient data locally and exchanging record-identifying information with other devices via decentralized networks during the patient encounter. This preliminary data collection and identification exchange enables complete data aggregation later without requiring continuous centralized network access during the encounter.
Solution Approach 2:
The patent introduces record-identifying information as an intermediary element that devices exchange during patient encounters. This intermediary contains unique identifiers that enable the server to later request and retrieve data from specific devices, bridging the gap between decentralized data collection and centralized data aggregation.
2Loss of information
If the server requests data from all devices after a patient encounter, then patient data completeness is improved, but system complexity increases
Solution Approach 1:
The patent extracts the critical identification function from complex device-to-device communication protocols by using standardized record-identifying information that can be independently processed. This extraction simplifies the overall system architecture by separating data identification from data transmission and processing.
Solution Approach 2:
The server uses feedback from received record-identifying information to determine which devices participated in each patient encounter. This feedback mechanism enables the server to automatically generate targeted requests to specific devices for their collected data, creating a closed-loop system that ensures completeness without manual intervention.
3Adaptability or versatility
If devices exchange record-identifying information via decentralized networks, then network accessibility is improved, but data retrieval reliability deteriorates
Solution Approach 1:
Devices perform preliminary exchange of record-identifying information during the patient encounter via decentralized networks, establishing a reliable data collection mechanism before returning to centralized network access. This preliminary action ensures that identification data is captured regardless of centralized network availability, enabling subsequent reliable data retrieval.
Solution Approach 2:
The patent uses record-identifying information as a copy or representation of device participation that can be independently transmitted and stored. This copying mechanism allows the system to track device participation through simplified data structures that are more reliable and easier to manage than transmitting complete device datasets through decentralized networks.
Data Source
AI summary
A method includes receiving, by a server, first patient data from a first device. The first patient data was collected by the first device during a patient encounter. The method includes receiving, from the first device, record-identifying information of a second device that was associated with the patient encounter. During the patient encounter, the record-identifying information was shared with the first device. The method include generating a request for second patient data collected by the second device during the patient encounter. The method includes sending the request for the second patient data to the second device based on the record-identifying information. The method includes receiving the second patient data from the second device after sending the request for the second patient data to the second device. The method includes generating a record for the patient encounter based on at least on the first patient data and the second patient data.