# US 2025/0168221 A1 · Connectivity tolerant medical information system and method > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0168221 A1 - Document ID: US20250168221A1 - Status: Published application - Kind: A1 - Application number: 18/517,265 - Filed: 2023-11-22 - Published: 2025-05-22 - Earliest claimed: 2023-11-22 - Applicants: Halo Tech Corp. - Inventors: Aram Compeau; Aleksandar Kolev; Kiril Nedialkov; Ilia Vatahov; Aleksandar Gudev - Web page: https://patentgrep.com/patent/US20250168221A1 ## CPC - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - G06F 3/0608: {Saving storage space on storage systems} - G06F 3/0641: {De-duplication techniques} - G06F 3/0661: {Format or protocol conversion arrangements} - G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]} - G06F 16/1744: {using compression, e.g. sparse files} - G06F 16/1752: {based on file chunks} - G06F 16/1794: {Details of file format conversion} - G16H 10/60: for patient-specific data, e.g. for electronic patient records - G16H 30/20: for handling medical images, e.g. DICOM, HL7 or PACS - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## 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 ### Claim 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. ### Claim 2 (depends on 1) The system of claim 1, wherein the data at the edge system and the cloud data stored at the cloud service comprises patient information. ### Claim 3 (depends on 2) The system of claim 2, wherein the patient information comprises one or more of medical images, medical requisition information, or patient biographical information. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 4) 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. ### Claim 6 (depends on 1) The system of claim 1, wherein the edge system is an on-premises deployment of the service. ### Claim 7 (depends on 1) The system of claim 1, wherein the one or more client systems comprise an imaging system that performs a medical imaging of a patient. ### Claim 8 (depends on 1) 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. ### Claim 9 (depends on 8) 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. ### Claim 10 (depends on 1) The system of claim 1, wherein the edge system pre-fetches files that are expected to be used within a threshold period of time. ### Claim 11 (depends on 1) 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. ### Claim 12 (depends on 1) 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. ### Claim 13 (depends on 12) 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. ### Claim 14 (depends on 13) 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. ### Claim 15 (depends on 14) 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. ### Claim 16 (depends on 15) The system of claim 15, wherein after performing the deduplication, the cloud system performs a compression on a deduplicated set of cloud chunks. ### Claim 17 (depends on 15) 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. ### Claim 18 (depends on 14) 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. ### Claim 19 (depends on 1) 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. ### Claim 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. ### Claim 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.