Rule-based low-latency delivery of healthcare data

• US 10,319,469 B2
• Filed: 07/29/2015
• Issued: 06/11/2019
• Est. Priority Date: 04/22/2014
• Status: Active Grant

• Current Assignee: Cerner Innovation, Inc. (Oracle Corporation)
• Original Assignee: Cerner Innovation, Inc. (Oracle Corporation)
• Inventors: Olson, Andrew P., Baugher, Bryan J., Whitacre, Micah K.
• Primary Examiner(s): Paulson, Sheetal R
• Application Number:
  US14/812,689
• Publication Number:
  US 20150332010A1
• Time in Patent Office: 1,413 Days
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records

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

1. A computerized method carried out by at least one server having at least one processor for delivering healthcare records with low latency, the method comprising:

generating a set of routing rules, in order to prevent undelivered or incorrectly delivered low latency data and improve efficiency, the set of routing rules defining one or more originating sources, one or more data types, and one or more processing nodes subscribing to the one or more originating sources and the one or more data types;

receiving healthcare data from the one or more originating sources at a staging platform, wherein the staging platform comprises a durable, short-term storage and the healthcare data is indexed at the staging platform such that it is available for low-latency processing;

upon receipt of the healthcare data, utilizing the set of routing rules to identify a subset of healthcare data to be delivered to a processing node of the one or more processing nodes; and

delivering the subset of healthcare data, identified based on the set of routing rules, to the processing node such that the processing node can perform at least one computing solution associated with the processing node, wherein processing speeds are improved and the at least one computing solution is performed more efficiently due to the set of routing rules reducing an amount of data the computing solution needs to sort through.

2. The computerized method of claim 1, wherein the set of routing rules are generated based on the processing needs of the computing solution associated with the processing node.

3. The computerized method of claim 2, wherein multiple processing nodes are associated with the computing solution.

4. The computerized method of claim 1, wherein the set of routing rules are applied to a data sink associated with the processing node and the set of routing rules further define the computing solution to which the subset of healthcare data is to be delivered and a local format to which the subset of healthcare data is to be converted before delivery to the computing solution, wherein the data sink comprises a processing input engine for receiving raw healthcare data from the staging platform.

5. The computerized method of claim 4, wherein multiple data sinks are associated with the processing node.

6. The computerized method of claim 1, further comprising labeling the healthcare data with metadata specifying an originating source and file type.

7. The computerized method of claim 1, further comprising, after receiving the healthcare data at the staging platform, utilizing the set of routing rules to filter and exclude healthcare data of data types and originating sources which are not subscribed to by the one or more processing nodes.

8. The computerized method of claim 1, wherein the set of routing rules are dynamically created, modified, or removed.

9. The computerized method of claim 8, wherein changes to the set of routing rules are automatically discovered and applied.

10. One or more computer-storage media having computer-executable instructions embodied thereon that, when executed, perform a method of dynamically delivering healthcare data for processing with low latency, the method comprising:

receiving healthcare data of different data types from different originating sources at a staging platform, wherein the staging platform comprises a durable, short-term storage;

applying a set of routing rules to the healthcare data, wherein the set of routing rules are generated by a configuration management component and define one or more originating sources, one or more data types, and one or more processing nodes subscribing to the one or more originating sources and the one or more data types;

identifying, based on the set of routing rules, a first subset of healthcare data of a first data type from a first originating source to which a first processing node of the one or more processing nodes subscribes;

delivering the first subset of healthcare data to the first processing node, wherein the first processing node converts the first subset of healthcare data into a first local format required by a computing solution;

identifying, based on the set of routing rules, a second subset of healthcare data of a second data type from a second originating source to which a second processing node of the one or more processing nodes subscribes;

delivering the second subset of healthcare data to the second processing node, wherein the second processing node converts the second subset of healthcare data into a second local format required by the computing solution; and

delivering the first subset of healthcare data in the first local format and the second subset of healthcare data in the second local format to the computing solution based on the routing rules.

11. The media of claim 10, wherein the first local format is different from the second local format.

12. The media of claim 10, wherein the first processing node is located in a different physical location from the second processing node.

13. The media of claim 10, wherein the first processing node is located within a common data center with the second processing node.

14. A system for delivering healthcare records with low latency comprising:

a staging platform for ingesting healthcare records;

a configuration management application for generating and storing a set of routing rules, wherein the set of routing rules define one or more originating sources, one or more data types, and a processing node subscribing to the one or more originating sources and the one or more data types;

a low-latency delivery system for filtering and routing healthcare records, wherein the low-latency delivery system delivers healthcare data records of a specified type from a specified originating source to one or more processing nodes in accordance with the set of routing rules; and

one or more processing nodes comprising;

(A) a data sink, defined by the set of routing rules, for receiving healthcare records, wherein the data sink comprises a processing input engine for receiving raw healthcare data form the staging platform,

(B) a plurality of parallel processors for processing the healthcare records into a local format defined by the routing rules, and

(C) a processed storage engine for storing the converted healthcare records.

15. The system of claim 14, wherein the staging platform labels healthcare data records with metadata type and source.

16. The system of claim 14, wherein the set of routing rules are dynamically created, modified, or removed.

17. The system of claim 16, wherein the low-latency delivery system automatically discovers and applies changes to the set of routing rules.

18. The system of claim 14 wherein the low-latency delivery system filters and excludes healthcare data which does not have a subscription link with a processing node.

19. The system of claim 14, wherein the data sink specifies a computing application to which the subset of healthcare data is to be delivered and a local format to which a subset of healthcare data is to be converted before delivery to the computing application.

20. The system of claim 19, wherein the local format is determined by the needs of the computing application to utilize the converted healthcare records to generate a clinically relevant result.