Database networks including advanced replication schemes

• US 20070185869A1
• Filed: 03/15/2007
• Published: 08/09/2007
• Est. Priority Date: 04/28/1999
• Status: Active Grant

• Current Assignee: Alean Kirnak
• Original Assignee: Alean Kirnak
• Inventors: Kirnak, Alean
• Granted Patent: US 10,067,995 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 of updating a database of records having person attributes using an input record containing person attributes and authorization information, wherein the database is associated with a database provider IDs and wherein each record of the database has a unique record provider ID and wherein the authorization information contains a unique record provider ID and a replicate indicator, the method comprising the steps of

generating an output record wherein the output record comprises the input record;

and

writing at least a portion of the input record to the database if the replicate indicator indicates a replica; and

comparing the record provider ID of the input record to the database provider ID; and

upon a match therebetween, writing at least a portion of the input record to the database, and configuring the replicate indicator of the output record to indicate a replica.

2. ) The method of claim 1 applied in a cascade of a first instance and a second instance wherein the database is a first database in the first instance and the database is a second database in the second instance and wherein the output record in the first instance is the input record in the second instance.

3. ) The method of claim 1, wherein the database is stored on a physical storage medium.

4. ) A method of updating a database of records having person attributes using an input record containing person attributes and authorization information, wherein each record of the database has a unique provider ID and wherein the authorization information contains either a unique provider ID or a prior-use indicator, the method comprising the steps of:

comparing a person attribute of the input record to a person attribute of each record in the database and identifying a record in the database as a matched record upon a match therebetween;

creating a composite record from the input record and the matched record;

writing at least a portion of the input record to the database if the authorization information contains a prior-use indicator; and

comparing a provider ID in the authorization information to a provider ID associated with the matched record and generating an output record upon a match therebetween wherein the output record consists of the input record and wherein the authorization information of the output record contains a prior-use indicator,

5. ) The method of claim 4 applied in a cascade of a first instance and a second instance wherein the database is a first database in a first instance and the database is a second database in a second instance and wherein an output record in the first instance is an input record in the second instance.

6. ) The method of claim 4, wherein the database is stored on a physical storage medium.

7. ) An apparatus which allows automatic, ongoing updates to a Hub from Provider healthcare systems within the context of a healthcare interoperability project by implementing notifications among databases, the apparatus comprising:

an enforcement filter for enforcing the Single Source Rule,

wherein the databases are stored on a physical storage medium.

8. ) The apparatus of claim 7, the apparatus comprising:

a second enforcement filter for enforcing the transactional integrity rule.

9. ) The apparatus of claim 7, the apparatus comprising:

a display design which supports the enforcement of the single source rule.

10. ) The apparatus of claim 7, the apparatus comprising:

queries which provide flexibility in configuring domains and functionality within healthcare interoperability systems.

11. ) The apparatus of claim 7, wherein said queries enable medical records to be retrieved from higher-tier domains upon demand, and reduce the need to store or re-enter data locally.

12. ) The apparatus of claim 7, the apparatus comprising:

means for matching of medical records belonging to the same individual person.

13. ) The apparatus of claim 7, the apparatus comprising:

an assigner for assigning person identifiers.

14. ) The apparatus of claim 13, wherein the assigner supports various domains configurations, including tiers, and superset, subset and peer-to-peer relationships among databases.

15. ) The apparatus of claim 7, the apparatus comprising

a filter for filtering data.

16. ) The apparatus of claim 15, wherein the filter is configured to record the source location of data, screen certain data fields from sharing or display, and process the data as the data passes through the apparatus.

17. ) The apparatus of claim 7, wherein databases are cascaded.