Database networks including advanced replication schemes

• US 10,067,995 B2
• Filed: 03/15/2007
• Issued: 09/04/2018
• Est. Priority Date: 04/28/1999
• Status: Active Grant

• Current Assignee: Alean Kirnak
• Original Assignee: Alean Kirnak
• Inventors: Kirnak, Alean
• Primary Examiner(s): Pauls, John A
• Application Number:
  US11/724,227
• Publication Number:
  US 20070185869A1
• Time in Patent Office: 4,191 Days
• Field of Search: 705 2- 4, 707201, 707100, 283101
• 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: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records

Abstract

To update a database of records having person attributes using an input record containing person attributes and authorization information, a person attribute of an input record is compared to a person attribute for each record in the database, and records in the database are identified as matched records. A composite record is created from the input record and the matched record. A portion of the input record is written to the database if the authorization information contains either an authorized provider ID or a prior-use indicator. An output record is thus generated consisting of the input record and authorization information containing a prior-use indicator. A cascade of a first instance and a second instance wherein the database comprises a first database in the first instance and a second database in the second instance may be performed.

Claims

1. A method, executing on a plurality of computers, for creating, updating and retrieving patient record replicas on a plurality of destinations,

wherein patient record replicas comprise replicas of original patient records,

and each original patient record is associated with one patient,

and each original patient record is created at one source in a plurality of sources by executing a create operation at the one source,

and each original patient record is updated by executing update operations at the one source that created the original patient record,

wherein each destination maintains a particular set of provider views,

each provider view in the set is associated with a particular source in the plurality of sources,

each provider view in the set comprises a set of patient views,

wherein each patient view comprises one or more patient record replicas associated with a particular, common patient

and at least one patient record replica in each patient view in a particular provider view is associated with the particular source,

sources in the plurality of sources grouped into a plurality of sets of sources,

for each set of sources in the plurality of sets of sources, at least one destination in the plurality of destinations associated with the set of sources and maintaining the set of provider views wherein one provider view in the set of provider views is associated with each of the sources in set of sources in the plurality of sources,

each set of sources in the plurality of sources chosen to produce overlap in the patient views included in the provider views included in the set of provider views maintained by the destination associated with the set of sources

destinations grouped into a plurality of aggregated sets of destinations,

for each aggregated set of destinations in the plurality of aggregated sets of destinations, at least one destination in the plurality of destinations being associated with the aggregated set of destinations and maintaining the set of provider views wherein one provider view in the set of provider views is associated with each of the sources associated with any provider view maintained by any destination in the aggregated set of destinations,

at least one aggregated set of destinations comprising a comprehensive sets of destinations

for each comprehensive set of destinations in the plurality of aggregated sets of destinations, at least one provider view maintained by at least one destination in the comprehensive set of destinations in the plurality of aggregated sets of destinations is associated with each source in the plurality of sources,

the method comprising:

creating each patient record replica only by replicating a particular create operation and executing the replicated create operation at each destination in the plurality of destinations that maintains the provider view that is associated with the one source in the plurality of sources that executed the particular create operation to create a particular original patient record;

associating the patient record replica with the particular original patient record created by the one create operation;

associating the patient record replica with the source that created the particular original patient record;

updating each patient record replica only by replicating update operations that update the particular original patient record with which the patient record replica is associated and executing the replicated update operations at the destination that created the patient record replica in the order in which the update operations were executed at the source;

each source querying at least one destination in the plurality of destinations associated with the set of sources that includes said source for patient views matching a particular patient,

the queried destination returning the patient view matching the particular patient if one exists within any provider view within the set of provider views the queried destination maintains,

and if no patient view matching the particular patient is found within any provider view within the set of provider views the queried destination maintains, replicating the query and executing it at at least one destination in at least one aggregated set of destinations maintaining the provider view associated with the querying source

the queried destination returning the patient view matching the particular patient if one exists within any provider view within the set of provider views the queried destination maintains,

and if no patient view matching the particular patient is found within any provider view within the set of provider views the queried destination maintains, continuing to replicate the query and execute it in succession at destinations in the aggregated set of destinations maintaining the provider view associated with the querying source

either until a patient matching the particular patient is found if one exists within any provider view within the set of provider views the queried destination maintains

or until at least one destination in the comprehensive set of destinations in the aggregated set of destinations has been queried,

the queried destination returning the patient view matching the particular patient if one exists within any provider view within the set of provider views the queried destination maintains.