Method and system for merging extensible data into a database using globally unique identifiers

• US 20090150377A1
• Filed: 12/07/2007
• Published: 06/11/2009
• Est. Priority Date: 12/07/2007
• Status: Active Grant

• Current Assignee: Roche Diabetes Care Inc. (Roche Holding AG)
• Original Assignee: Roche Diagnostics Operations Incorporated (Roche Holding AG), Software Engineering Professionals, Inc.
• Inventors: Beck, Timothy L., Gejdos, Igor, Young, Morris J., Mott, David Patrick
• Granted Patent: US 8,112,390 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof

Abstract

A method of merging data from one database into another database uses metadata identifiers to indicate the type of data. One of the databases can be stored on a medical device, and the other of the databases can be stored on a computer. When transferring data from the first database to the second database, the metadata identifiers are used to identify and merge common data types.

Claims

1. A method of transferring a first set of data from a first database to a second database comprising the steps of:

comparing a metadata identifier assigned to a first set of data to a plurality of metadata identifiers associated with the second database; and

combining the first set of data in the first database with a set of data in the second database having the same metadata identifier.

2. The method as set forth in claim 1 further comprising the step of adding the first set of data to the second database if the metadata identifier does not match any of the plurality of metadata identifiers.

3. The method as set forth in claim 1 further comprising the step of configuring a portion of the first database to store the first set of data.

4. The method as set forth in claim 1 wherein the metadata identifier is assigned to the first set of data when a user creates the first set of data.

5. The method as set forth in claim 1 further comprising the step of configuring a portion of the second database to store a set of data of the same type as the first set of data in the first database.

6. The method as set forth in claim 1 wherein the first database is stored on a device.

7. The method as set forth in claim 1 wherein the second database is stored on a computer.

8. The method as set forth in claim 1 wherein the first database is stored on a first computer and the second database is stored on a second computer.

9. A method for combining at least one subset of a set of data comprising a first database with a set of data comprising a second database, the method comprising the steps of:

assigning a metadata identifier to each subset of data comprising the first database;

assigning a metadata identifier to at least one subset of data comprising the second database;

comparing each metadata identifier of the first database with at least one metadata identifier of the second database; and

combining a subset of data of the first database with the second database if the metadata identifier of the first database is the same as the metadata identifiers of the second database.

10. The method as set forth in claim 9 further comprising the step of adding a subset of data from the first database to the second database if the metadata identifier of the first database differs from the metadata identifiers of the second database.

11. The method as set forth in claim 9 wherein the first database is stored on a medical device.

12. The method as set forth in claim 9 wherein the second database is stored on a computer.

13. The method as set forth in claim 9 wherein the metadata identifier for a specific subset of data in the first database is identical to the metadata identifier for a specific subset of data in the second database when the type of data comprising the specific subsets of data is identical.

14. The method as set forth in claim 9 further comprising the step of associating the metadata identifier of the first subset of data of the first database with the metadata identifier of the subset of data of the second database.

15. The method as set forth in claim 9 further comprising the step of naming each subset of data.

16. The method as set forth in claim 9 further comprising the step of adding an additional subset of data to the second database.

17. The method as set forth in claim 16 further comprising the step of generating a metadata identifier relating to the additional subset of data.

18. The method as set forth in claim 17 further comprising the step of comparing the metadata identifier of the additional subset of data to the metadata identifiers of the second database.

19. The method as set forth in claim 18 further comprising the step of adding the additional subset of data to the second database if the metadata identifier of the additional subset of data is not identical to any of the metadata identifiers of the second database.

20. The method as set forth in claim 18 further comprising the step of combining the additional subset of data with a subset of data on the second database identified by a metadata identifier identical to the metadata identifier associated with the additional subset of data.

21. The method as set forth in claim 9 wherein each metadata identifier of the first database is compared with each metadata identifier of the second database.