# US 2025/0157604 A1 · Time-Based Healthcare Data Management with Partitioned Storage and Compaction

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0157604 A1
- Document ID: US20250157604A1
- Status: Published application
- Kind: A1
- Application number: 19/021,473
- Filed: 2025-01-15
- Published: 2025-05-15
- Earliest claimed: 2014-04-22
- Assignees: Cerner Innovation, Inc.
- Applicants: Cerner Innovation, Inc.
- Inventors: Andrew P. Olson; Bryan J. Baugher; Micah K. Whitacre
- Web page: https://patentgrep.com/patent/US20250157604A1

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G06F 16/258: {Data format conversion from or to a database}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, systems, and computer-readable media are provided for delivering healthcare records with low latency. Healthcare data is collected from various disparate healthcare data sources. The data is filtered in accordance with routing rules to identify healthcare data to deliver to a processing node. The routing rules specify that healthcare data from a particular originating source of a particular data type is to be delivered to a particular processing node. The healthcare data is converted to a local format for use by a computing solution. This system of delivering healthcare data with low latency ensures that the data is delivered to the correct location in the correct format, even if the routing rules change.

## Claims

### Claim 1

One or more non-transitory computer-readable media storing instructions for managing healthcare data in a cloud computing environment which, when executed, cause a set of one or more computing devices to perform a set of operations comprising:
receiving, at a staging platform, healthcare data from a plurality of healthcare data sources;
partitioning the healthcare data into a plurality of data partitions based on at least one of: (a) one or more types of healthcare data indicated by metadata associated with healthcare data or (b) one or more sources of healthcare data indicated by metadata associated with healthcare data; and
for a data partition of the plurality of data partitions:
storing healthcare data of the partition in a plurality of time slices in a long-term storage data store, wherein a time slice of the plurality of time slices corresponds to a defined time period and contains healthcare data of the partition received during that defined time period;
compacting multiple time slices of the plurality of time slices into a larger historical time slice to reduce storage space in the long-term storage data store; and
providing access to healthcare data stored in one or more time slices of the plurality of time slices and the larger historical time slice to one or more processing nodes that subscribe to healthcare data.

### Claim 2 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the set of operations further comprising:
aggregating portions of healthcare data having a same type into a batch; and
after the aggregating, partitioning the batch according to one or more sources of healthcare data indicated by metadata associated with healthcare data.

### Claim 3 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the set of operations further comprising:
storing a first subset of healthcare data received during a first defined time period in a first time slice;
storing a second subset of healthcare data received during a second defined time period in a second time slice; and
wherein the first defined time period is more recent than the second defined time period.

### Claim 4 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the set of operations further comprising:
detecting that a predetermined duration has elapsed; and
compacting the multiple time slices of the plurality of time slices into the larger historical time slice based on detecting that the predetermined duration has elapsed.

### Claim 5 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the set of operations further comprising:
in response to determining that a predetermined time period has elapsed since healthcare data of the multiple time slices was stored, combining the multiple time slices into the larger historical time slice, wherein the multiple time slices each contain healthcare data for a first duration time period and the larger historical time slice contains healthcare data for a second duration time period that is longer than the first duration time period.

### Claim 6

A method of managing healthcare data in a cloud computing environment, the method comprising:
receiving, at a staging platform, healthcare data from a plurality of healthcare data sources;
partitioning the healthcare data into a plurality of data partitions based on at least one of: (a) one or more types of healthcare data indicated by metadata associated with healthcare data or (b) one or more sources of healthcare data indicated by metadata associated with healthcare data; and
for a data partition of the plurality of data partitions:
storing healthcare data of the partition in a plurality of time slices in a long-term storage data store, wherein a time slice of the plurality of time slices corresponds to a defined time period and contains healthcare data of the partition received during that defined time period; and
compacting multiple time slices of the plurality of time slices into a larger historical time slice to reduce storage space in the long-term storage data store; and
providing access to healthcare data stored in one or more time slices of the plurality of time slices and the larger historical time slice to one or more processing nodes that subscribe to healthcare data.

### Claim 7 (depends on 6)

The method of claim 6, wherein partitioning the healthcare data comprises:
aggregating portions of healthcare data having a same type into a batch; and
after the aggregating, partitioning the batch according to one or more sources of healthcare data indicated by metadata associated with healthcare data.

### Claim 8 (depends on 6)

The method of claim 6, wherein storing healthcare data of the data partition in the plurality of time slices comprises:
storing a first subset of healthcare data received during a first defined time period in a first time slice;
storing a second subset of healthcare data received during a second defined time period in a second time slice; and
wherein the first defined time period is more recent than the second defined time period.

### Claim 9 (depends on 6)

The method of claim 6, further comprising:
detecting that a predetermined duration has elapsed; and
compacting the multiple time slices of the plurality of time slices into the larger historical time slice based on detecting that the predetermined duration has elapsed.

### Claim 10 (depends on 6)

The method of claim 6, wherein compacting multiple time slices comprises:
in response to determining that a predetermined time period has elapsed since healthcare data of the multiple time slices was stored, combining the multiple time slices into the larger historical time slice, wherein the multiple time slices each contain healthcare data for a first duration time period and the larger historical time slice contains healthcare data for a second duration time period that is longer than the first duration time period.

### Claim 11 (depends on 6)

The method of claim 6, wherein providing access to healthcare data stored in one or more time slices of the plurality of time slices comprises:
receiving, from a processing node of the one or more processing nodes, a request for a subset of healthcare data, the request specifying:
a particular type of healthcare data,
a particular source of healthcare data, and
a time period;
accessing, from one or more time slices of the plurality of time slices, healthcare data matching the particular type, particular source, and time period specified in the request; and
sending the accessed healthcare data to the processing node.

### Claim 12 (depends on 6)

The method of claim 6, wherein providing access to healthcare data stored in the larger historical time slice comprises:
receiving, from a processing node of the one or more processing nodes, a request for historical healthcare data, the request specifying:
a particular type of healthcare data,
a particular source of healthcare data, and
a historical time period;
accessing, from the larger historical time slice, healthcare data matching the particular type, particular source, and historical time period specified in the request; and
sending the accessed historical healthcare data to the processing node.

### Claim 13 (depends on 6)

The method of claim 6, further comprising:
filtering duplicate portions of healthcare data after receiving the healthcare data at the staging platform but before partitioning the healthcare data, wherein the filtering reduces excess data storage usage while maintaining at least two copies of the healthcare data in geographically-disparate data centers for disaster recovery.

### Claim 14 (depends on 6)

The method of claim 6, further comprising:
receiving, at a collector service acting as a front door to multiple data centers, the healthcare data from the plurality of healthcare data sources;
determining that a first data center hosting the collector service is unavailable; and
in response to determining that the first data center is unavailable, routing the healthcare data to a staging platform of a second geographically-disparate data center.

### Claim 15 (depends on 6)

The method of claim 6, wherein providing access to healthcare data comprises:
generating routing rules defining one or more data types and one or more sources to which each processing node, of the one or more processing nodes, subscribes;
identifying, based on the routing rules, a subset of healthcare data to be delivered with low latency to a first processing node;
delivering the subset of healthcare data to a data sink associated with the first processing node;
converting the subset of healthcare data into a local format specified by the data sink; and
storing the converted subset of healthcare data in a processed storage engine accessible by a computing process associated with the first processing node.

### Claim 16

A system comprising:
a set of one or more computing device;
instructions for managing healthcare data in a cloud computing environment which, when executed, cause the set of one or more computing devices to perform a set of operations comprising:
receiving, at a staging platform, healthcare data from a plurality of healthcare data sources;
partitioning the healthcare data into a plurality of data partitions based on at least one of:
(a) one or more types of healthcare data indicated by metadata associated with healthcare data or (b) one or more sources of healthcare data indicated by metadata associated with healthcare data; and
for a data partition of the plurality of data partitions:
storing healthcare data of the partition in a plurality of time slices in a long-term storage data store, wherein a time slice of the plurality of time slices corresponds to a defined time period and contains healthcare data of the partition received during that defined time period; and
compacting multiple time slices of the plurality of time slices into a larger historical time slice to reduce storage space in the long-term storage data store; and
providing access to healthcare data stored in one or more time slices of the plurality of time slices and the larger historical time slice to one or more processing nodes that subscribe to healthcare data
wherein providing access to healthcare data is based on:
generating routing rules defining one or more data types and one or more sources to which each processing node, of the one or more processing node, subscribes;
identifying, based on the routing rules, a subset of healthcare data to be delivered with low latency to a first processing node;
delivering the subset of healthcare data to a data sink associated with the first processing node;
converting the subset of healthcare data into a local format specified by the data sink; and
storing the converted subset of healthcare data in a processed storage engine accessible by a computing process associated with the first processing node.

### Claim 17 (depends on 16)

The system of claim 16, the set of operations further comprising:
aggregating portions of healthcare data having a same type into a batch; and
after the aggregating, partitioning the batch according to one or more sources of healthcare data indicated by metadata associated with healthcare data.

### Claim 18 (depends on 16)

The system of claim 16, the set of operations further comprising:
storing a first subset of healthcare data received during a first defined time period in a first time slice;
storing a second subset of healthcare data received during a second defined time period in a second time slice; and
wherein the first defined time period is more recent than the second defined time period.

### Claim 19 (depends on 16)

The system of claim 16, the set of operations further comprising:
detecting that a predetermined duration has elapsed; and
compacting the multiple time slices of the plurality of time slices into the larger historical time slice based on detecting that the predetermined duration has elapsed.

### Claim 20 (depends on 16)

The system of claim 16, the set of operations further comprising:
in response to determining that a predetermined time period has elapsed since healthcare data of the multiple time slices was stored, combining the multiple time slices into the larger historical time slice, wherein the multiple time slices each contain healthcare data for a first duration time period and the larger historical time slice contains healthcare data for a second duration time period that is longer than the first duration time period.
