Microbatch loading

Patent metadata

Field	Value
Publication number	US-10140318-B1
Application number	US-201414292815-A
Country	US
Kind code	B1
Filing date	May 30, 2014
Priority date	Jul 1, 2013
Publication date	Nov 27, 2018
Grant date	Nov 27, 2018

Abstract

A method includes receiving structured clinical data in transactional HL7 messages, aggregating the data in a staging area, and merging only the most updated data into a destination database in ordered, validated, calculated, and manipulated sets.

First claim

What is claimed is:

1. A method comprising:
(a) electronically receiving, over a network, a plurality of HL7 transactional messages containing patient data for a plurality of patients;
(b) electronically sorting, at one or more electronic devices, the plurality of HL7 transactional messages into a plurality of patient queues, each patient queue representing a queue for HL7 transactional messages containing data for a respective particular patient of the plurality of patients;
(c) electronically validating, at an electronic device, a first plurality of HL7 transactional messages for a first particular patient by evaluating the HL7 transactional messages against a plurality of rules;
(d) electronically aggregating, at an electronic device, the first plurality of HL7 transactional messages for the first particular patient, wherein electronically aggregating, at an electronic device, the first plurality of HL7 transactional messages for the first particular patient comprises determining a plurality of CDC operations;
(e) electronically merging, utilizing one or more processors, information corresponding to the first aggregated HL7 transactional messages for the first particular patient into a centralized data repository, one or more servers comprising the centralized data repository;
(f) electronically validating, at an electronic device, a second plurality of HL7 transactional messages for the first particular patient by evaluating the HL7 transactional messages against a plurality of rules;
(g) electronically aggregating, at an electronic device, the second plurality of HL7 transactional messages for the first particular patient;
(h) electronically merging, utilizing one or more processors, information corresponding to the second aggregated HL7 transactional messages for the first particular patient into the centralized data repository;
(i) electronically validating, at an electronic device, a third plurality of HL7 transactional messages for a second particular patient by evaluating the HL7 transactional messages against a plurality of rules;
(j) electronically aggregating, at an electronic device, the third plurality of HL7 transactional messages for the second particular patient;
(k) electronically merging, utilizing one or more processors, information corresponding to the third aggregated HL7 transactional messages for the second particular patient into the centralized data repository;
(l) attempting to electronically validate, at an electronic device, a fourth plurality of HL7 transactional messages for a third particular patient by evaluating the HL7 transactional messages against a plurality of rules; and
(m) determining, based on evaluation of the fourth plurality of HL7 transactional messages against a plurality of rules, that an error occurred when attempting to validate the fourth plurality of HL7 transactional messages.

2. The method of claim 1 , wherein the method further includes accessing, by an electronic device, data from the centralized data repository that was merged into the centralized data repository based on information corresponding to the first aggregated HL7 transactional messages for the first particular patient.

3. The method of claim 1 , wherein the method further includes displaying, via an electronic display of an electronic device, data from the centralized data repository that was merged into the centralized data repository based on information corresponding to the first aggregated HL7 transactional messages for the first particular patient.

4. The method of claim 1 , wherein electronically receiving, over a network, a plurality of HL7 transactional messages containing patient data for a plurality of patients comprises electronically receiving, over a network at a server, a plurality of HL7 transactional messages.

5. The method of claim 1 , wherein the number of messages in the first plurality of HL7 transactional messages for the first particular patient is user configurable.

6. The method of claim 1 , wherein the method further includes receiving, at an electronic device, input from a user via one or more input devices corresponding to an indication of a number of transactional messages to include an in aggregated “bulk”.

7. The method of claim 1 , wherein electronically validating, at an electronic device, a first plurality of HL7 transactional messages for a first particular patient by evaluating the HL7 transactional messages against a plurality of rules comprises evaluating the HL7 transactional messages against a plurality of user-customizable rules.

8. The method of claim 1 , wherein the method further includes receiving, at an electronic device, input from a user via one or more input devices corresponding to an indication of a number of rule to utilize in evaluating HL7 transactional messages.

9. The method of claim 1 , wherein electronically aggregating, at an electronic device, the first plurality of HL7 transactional messages for the first particular patient comprises electronically merging, utilizing one or more processors and the determined CDC operations, information corresponding to the first aggregated HL7 transactional messages for the first particular patient into the centralized data repository comprises.

10. A method comprising:
(a) electronically receiving, over a network, a plurality of transactional messages containing patient data for a plurality of patients;
(b) electronically sorting, at one or more electronic devices, the plurality of transactional messages into a plurality of patient queues, each patient queue representing a queue for transactional messages containing data for a respective particular patient of the plurality of patients;
(c) electronically validating, at an electronic device, a first plurality of transactional messages for a first particular patient by evaluating the transactional messages against a plurality of rules;
(d) electronically aggregating, at an electronic device, the first plurality of transactional messages for the first particular patient, wherein electronically aggregating, at an electronic device, the first plurality of transactional messages for the first particular patient comprises determining a plurality of CDC operations;
(e) electronically merging, utilizing one or more processors, information corresponding to the first aggregated transactional messages for the first particular patient into a centralized data repository, one or more servers comprising the centralized data repository;
(f) electronically validating, at an electronic device, a second plurality of transactional messages for the first particular patient by evaluating the transactional messages against a plurality of rules;
(g) electronically aggregating, at an electronic device, the second plurality of transactional messages for the first particular patient;
(h) electronically merging, utilizing one or more processors, information corresponding to the second aggregated transactional messages for the first particular patient into the centralized data repository;
(i) electronically validating, at an electronic device, a third plurality of transactional messages for a second particular patient by evaluating the transactional messages against a plurality of rules;
(j) electronically aggregating, at an electronic device, the third plurality of transactional messages for the second particular patient;
(k) electronically merging, utilizing one or more processors, information corresponding to the third aggregated transactional messages for the second particular patient into the centralized data repository;
(l) attempting to electronically validate, at an electronic device, a fourth plurality of transactional messages for a third particular patient b

Assignees

• Allscripts Software Llc

Inventors

• Prilutsky Roman

Classifications

• G06F16/23

  Updating · CPC title

• G06F17/30345

  Physics · mapped topic

• G16H10/60 Primary

  for patient-specific data, e.g. for electronic patient records · CPC title

• G06F17/30289 Primary

  Physics · mapped topic

• G06F16/254

  Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses · CPC title