US2025168221A1PendingUtilityA1

Connectivity tolerant medical information system and method

31
Assignee: HALO TECH CORPPriority: Nov 22, 2023Filed: Nov 22, 2023Published: May 22, 2025
Est. expiryNov 22, 2043(~17.4 yrs left)· nominal 20-yr term from priority
H04L 67/1097G06F 16/1752G16H 30/20G06F 3/0661G06F 3/0641G16H 10/60G06F 16/1744G06F 3/0608G06F 3/067G06F 16/1794H04L 67/10
31
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system, method, and device for providing a service to a set of client systems is disclosed. The method includes (i) connecting, by one or more processors associated with an edge system, to a cloud service, (ii) maintaining an edge index of data stored locally at the edge system, (iii) syncing, based on the edge index, at least a subset of the data comprised at the edge system with cloud data stored at the cloud service, and (iv) providing access to the data stored locally at the edge system to one or more client systems connected to the edge system.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A system for providing a service to a set of client systems, comprising:
 an edge system, comprising:
 one or more processors configured to:
 connect to a cloud service; 
 maintain an edge index of data stored locally at the edge system; 
 sync, based on the edge index, at least a subset of the data comprised at the edge system with cloud data stored at the cloud service; and 
 provide access to the data stored locally at the edge system to one or more client systems connected to the edge system; and 
 
 a memory coupled to the one or more processors and configured to provide the one or more processors with instructions. 
   
     
     
         2 . The system of  claim 1 , wherein the data at the edge system and the cloud data stored at the cloud service comprises patient information. 
     
     
         3 . The system of  claim 2 , wherein the patient information comprises one or more of medical images, medical requisition information, or patient biographical information. 
     
     
         4 . The system of  claim 1 , wherein in response to determining that a connection between the cloud service and the edge system is lost, the one or more client systems use the data stored locally at the edge system, and new data generated by the one or more client systems is stored locally at the edge system until the connection is restored between the cloud service and the edge system. 
     
     
         5 . The system of  claim 4 , wherein in response to determining that the connection is restored, causing at least a subset of the new data to be synced with the cloud service. 
     
     
         6 . The system of  claim 1 , wherein the edge system is an on-premises deployment of the service. 
     
     
         7 . The system of  claim 1 , wherein the one or more client systems comprise an imaging system that performs a medical imaging of a patient. 
     
     
         8 . The system of  claim 1 , wherein syncing the at least the subset of the data comprises:
 translating the data stored locally at the edge system to translated data that is in a predefined data format associated with the cloud service; and   causing the translated data to be transferred to the cloud service.   
     
     
         9 . The system of  claim 8 , wherein the data stored locally at the edge system is formatted according to a Digital Imaging and Communications in Medicine (DICOM) standard format. 
     
     
         10 . The system of  claim 1 , wherein the edge system pre-fetches files that are expected to be used within a threshold period of time. 
     
     
         11 . The system of  claim 1 , wherein a particular piece of data is transferred to the edge system based at least in part on schedule information that indicates when the particular piece of data is expected to be used at a client system connected to the edge system. 
     
     
         12 . The system of  claim 1 , further comprising:
 a cloud system to provide the cloud service to the edge system, the cloud system comprising:
 one or more processors configured to:
 connect to the edge system; 
 maintain a cloud index of the cloud data stored locally at the cloud system; and 
 sync, based on the cloud index of the cloud data, at least the subset of the data comprised at the edge system with the cloud data stored at the cloud system; and 
 
 a memory coupled to the one or more processors and configured to provide the one or more processors with instructions. 
   
     
     
         13 . The system of  claim 12 , wherein syncing the at least the subset of the data comprised at the edge system with the cloud data stored at the cloud system comprises:
 determining the subset of the data to be transferred between the edge system and the cloud system based at least in part on the edge index and the cloud index.   
     
     
         14 . The system of  claim 13 , wherein determining the subset of the data to be transferred between the edge system and the cloud system comprises:
 determining the cloud data to be transferred from the cloud system to the edge system, including:
 determining a set of cloud files to be transferred to the edge system; 
 determining a plurality of cloud chunks corresponding to the set of cloud files to be transferred; 
 determining, based at least in part the edge index, a subset of cloud chunks of the plurality of cloud chunks to transfer to the edge system based on a determination of which of the plurality of cloud chunks the edge system stores copies as edge chunks; and 
 causing the subset of the cloud chunks to be transferred to the edge system. 
   
     
     
         15 . The system of  claim 14 , wherein the subset of the cloud chunks is transferred based on a deduplication of the edge chunks stored at the edge system. 
     
     
         16 . The system of  claim 15 , wherein after performing the deduplication, the cloud system performs a compression on a deduplicated set of cloud chunks. 
     
     
         17 . The system of  claim 15 , wherein the deduplication of the edge chunks is determined based at least in part on a hash or a signature associated with each edge chunk or cloud chunk. 
     
     
         18 . The system of  claim 14 , wherein the causing the subset of the cloud chunks to be transferred to the edge system comprises:
 grouping the subset of the cloud chunks into a group of blocks, wherein a first block of the group of blocks comprises a plurality of chunks comprised in the subset of the cloud chunks; and   transferring the group of blocks to the edge system.   
     
     
         19 . The system of  claim 1 , wherein the edge system is connected to a medical service system that stores medical data in a predefined medical data format. 
     
     
         20 . A method, comprising:
 connecting, by one or more processors associated with an edge system, to a cloud service;   maintaining an edge index of data stored locally at the edge system;   syncing, based on the edge index, at least a subset of the data comprised at the edge system with cloud data stored at the cloud service; and   providing access to the data stored locally at the edge system to one or more client systems connected to the edge system.   
     
     
         21 . A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for:
 connecting, by one or more processors associated with an edge system, to a cloud service;   maintaining an edge index of data stored locally at the edge system;   syncing, based on the edge index, at least a subset of the data comprised at the edge system with cloud data stored at the cloud service; and   providing access to the data stored locally at the edge system to one or more client systems connected to the edge system.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.