WO2009071201A1 - Method and system for merging extensible data into a database using globally unique identifiers - Google Patents
Method and system for merging extensible data into a database using globally unique identifiers Download PDFInfo
- Publication number
- WO2009071201A1 WO2009071201A1 PCT/EP2008/009874 EP2008009874W WO2009071201A1 WO 2009071201 A1 WO2009071201 A1 WO 2009071201A1 EP 2008009874 W EP2008009874 W EP 2008009874W WO 2009071201 A1 WO2009071201 A1 WO 2009071201A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- database
- metadata
- computer
- metadata identifier
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- NOESYZHRGYRDHS-UHFFFAOYSA-N insulin Chemical compound N1C(=O)C(NC(=O)C(CCC(N)=O)NC(=O)C(CCC(O)=O)NC(=O)C(C(C)C)NC(=O)C(NC(=O)CN)C(C)CC)CSSCC(C(NC(CO)C(=O)NC(CC(C)C)C(=O)NC(CC=2C=CC(O)=CC=2)C(=O)NC(CCC(N)=O)C(=O)NC(CC(C)C)C(=O)NC(CCC(O)=O)C(=O)NC(CC(N)=O)C(=O)NC(CC=2C=CC(O)=CC=2)C(=O)NC(CSSCC(NC(=O)C(C(C)C)NC(=O)C(CC(C)C)NC(=O)C(CC=2C=CC(O)=CC=2)NC(=O)C(CC(C)C)NC(=O)C(C)NC(=O)C(CCC(O)=O)NC(=O)C(C(C)C)NC(=O)C(CC(C)C)NC(=O)C(CC=2NC=NC=2)NC(=O)C(CO)NC(=O)CNC2=O)C(=O)NCC(=O)NC(CCC(O)=O)C(=O)NC(CCCNC(N)=N)C(=O)NCC(=O)NC(CC=3C=CC=CC=3)C(=O)NC(CC=3C=CC=CC=3)C(=O)NC(CC=3C=CC(O)=CC=3)C(=O)NC(C(C)O)C(=O)N3C(CCC3)C(=O)NC(CCCCN)C(=O)NC(C)C(O)=O)C(=O)NC(CC(N)=O)C(O)=O)=O)NC(=O)C(C(C)CC)NC(=O)C(CO)NC(=O)C(C(C)O)NC(=O)C1CSSCC2NC(=O)C(CC(C)C)NC(=O)C(NC(=O)C(CCC(N)=O)NC(=O)C(CC(N)=O)NC(=O)C(NC(=O)C(N)CC=1C=CC=CC=1)C(C)C)CC1=CN=CN1 NOESYZHRGYRDHS-UHFFFAOYSA-N 0.000 description 44
- 102000004877 Insulin Human genes 0.000 description 22
- 108090001061 Insulin Proteins 0.000 description 22
- 229940125396 insulin Drugs 0.000 description 22
- WQZGKKKJIJFFOK-GASJEMHNSA-N Glucose Natural products OC[C@H]1OC(O)[C@H](O)[C@@H](O)[C@@H]1O WQZGKKKJIJFFOK-GASJEMHNSA-N 0.000 description 21
- 239000008103 glucose Substances 0.000 description 21
- 239000008280 blood Substances 0.000 description 19
- 210000004369 blood Anatomy 0.000 description 19
- 238000005259 measurement Methods 0.000 description 15
- 230000036772 blood pressure Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 238000004519 manufacturing process Methods 0.000 description 5
- 230000001413 cellular effect Effects 0.000 description 4
- 229920001690 polydopamine Polymers 0.000 description 4
- 206010012601 diabetes mellitus Diseases 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 102000009027 Albumins Human genes 0.000 description 2
- 108010088751 Albumins Proteins 0.000 description 2
- HVYWMOMLDIMFJA-DPAQBDIFSA-N cholesterol Chemical compound C1C=C2C[C@@H](O)CC[C@]2(C)[C@@H]2[C@@H]1[C@@H]1CC[C@H]([C@H](C)CCCC(C)C)[C@@]1(C)CC2 HVYWMOMLDIMFJA-DPAQBDIFSA-N 0.000 description 2
- 238000001802 infusion Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 102000017011 Glycated Hemoglobin A Human genes 0.000 description 1
- 108010014663 Glycated Hemoglobin A Proteins 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000009530 blood pressure measurement Methods 0.000 description 1
- 150000001720 carbohydrates Chemical class 0.000 description 1
- 235000012000 cholesterol Nutrition 0.000 description 1
- 238000010367 cloning Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000029142 excretion Effects 0.000 description 1
- IXZISFNWUWKBOM-ARQDHWQXSA-N fructosamine Chemical compound NC[C@@]1(O)OC[C@@H](O)[C@@H](O)[C@@H]1O IXZISFNWUWKBOM-ARQDHWQXSA-N 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 150000002576 ketones Chemical class 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 201000001474 proteinuria Diseases 0.000 description 1
- UFTFJSFQGQCHQW-UHFFFAOYSA-N triformin Chemical compound O=COCC(OC=O)COC=O UFTFJSFQGQCHQW-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/221—Column-oriented storage; Management thereof
Definitions
- the present invention relates to a method of merging data from multiple databases into a single database. Specifically, the present invention relates to utilizing globally unique identifiers in the databases to distinguish between different types of data.
- the databases may include fields of data defined by a name identifier.
- different databases may contain different types of data identified by the same name identifier.
- the fields having the same name identifier from the separate databases may be combined into a single data field, even if those fields represent different types of data.
- An embodiment of the invention comprises a method of transferring a first set of data from a first database to a second database.
- the method includes 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.
- Embodiments of the invention further include the step of adding the first set of data to the second database if the metadata identifier does not match the plurality of metadata identifiers in the second database.
- the method may include the step of configuring a portion of the first database to store the first set of data.
- the metadata identifier is assigned to the first set of data when a user creates the first set of data.
- the method may include 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.
- the first database is stored on a device, and the second database is stored on a computer.
- the first database is stored on a first computer, and the second database is stored on a second computer.
- An embodiment of the invention comprises 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 includes 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 each 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 identifier of the second database.
- Figure 1 depicts an example of an embodiment of a system utilizing the present invention.
- Figures 2 through 7 depict schematic diagrams illustrating embodiments of the present invention utilizing the system depicted in Figure 1 for exemplary purposes.
- the drawings represent embodiments of various features and components according to the present invention, the drawings are not necessarily to scale and certain features may be exaggerated in order to better illustrate and explain the present invention.
- the exemplifications set out herein illustrate embodiments of the invention, and such exemplifications are not to be construed as limiting the scope of the invention in any manner.
- the concepts described below may relate to diabetes management software systems for tracking and analyzing health data, such as, for example, the ACCU-CHEK ® 360° product provided by Roche Diagnostics.
- the concepts described herein may also have applicability to apparatuses, methods, systems, and software in fields that are unrelated to healthcare.
- references in this patent application to devices, meters, monitors, pumps, or related terms are intended to encompass any currently existing or later developed apparatus that includes some or all of the features attributed to the referred to apparatus, including but not limited to the ACCU-CHEK ® Active, Accu- CHEK ® Aviva, ACCU-CHEK ® Compact, ACCU-CHEK ® Compact Plus, ACCU-CHEK ® Integra, ACCU-CHEK ® GO, ACCU-CHEK ® Performa, ACCU-CHEK ® Spirit, ACCU-CHEK ® D- Tron Plus, and ACCU-CHEK ® Voicemate Plus, all provided by Roche Diagnostics or divisions thereof.
- Figure 1 depicts a computer, generally indicated by numeral 10, and a medical device, generally indicated by numeral 12.
- Computer 10 may be any type of computer capable of running software.
- computer 10 is a laptop computer.
- computer 10 includes receiver 14.
- Receiver 14 may be connected to computer 10 in any suitable manner, such as through a USB connection, for example.
- computer 10 includes a hard drive (not shown) capable of storing data in a conventional manner.
- the software stored in the memory of computer 10 generally allows computer 10 to communicate with device 12.
- the software allows computer 10 to communicate with device 12 by way of receiver 14.
- the software installed on computer 10 may be ACCU-CHEK ® 360 ° software manufactured by Roche Diagnostics.
- PDAs personal digital assistants
- infusion pumps blood glucose meters
- cellular phones or integrated devices including a glucose measurement engine and a PDA or cellular device.
- Device 12 may be any suitable medical device capable of communicating with the software stored on computer 10, such as a blood glucose meter, for example.
- Device 12 includes a dynamic memory, thereby allowing the device 12 to store and save various types of data.
- exemplary physiological information in patients such as the blood glucose levels of patients
- the measured values may be saved in the memory of the device 12.
- device 12 may allow a user to add additional data to the memory that is not measured directly by device 12, such as the weight of the patient, for example.
- the data stored in the memory of device 12 may be stored in a database in the memory of device 12.
- the software executed by computer 10 is configured to allow computer 10 to communicate with device 12 by way of receiver 14.
- the communication between device 12 and receiver 14 may occur in any suitable manner.
- device 12 and receiver 14 may communicate wirelessly, such as via infrared signals or via radio frequency signals.
- device 12 may communicate with receiver 14 in a non-wireless manner utilizing a direct connection, such as that which may be established using a suitable cord and plug combination, for example.
- the device 12 may communicate directly with computer 10, in a suitable manner.
- device 12 may communicate with computer 10 in a wireless manner or non-wireless manner without the utilization of receiver 14.
- the data stored in the database of device 12 may be downloaded onto computer 10.
- the user may initiate the download process, or in embodiments, the download process may occur automatically.
- Figure 2 is a schematic that represents the databases in the memory of computer 10 and device 12.
- numerals 20, 22, 24, 26 represent different sets of various types of data stored in the memory of computer 10.
- numerals 30, 32, 34, 36 represent different fields, or sets, of various types of data stored in the memory of device 12.
- the memory of computer 10 includes data relating to blood glucose measurements of a patient, represented by numeral 20, weight measurements of a patient, represented by numeral 22, the type of insulin taken by a patient, represented by numeral 24, and the amount of insulin taken by a patient, represented by numeral 26.
- the memory of device 12 includes data associated with the blood glucose measurements of a patient, represented by numeral 30, the height measurements of a patient, represented by numeral 32, the type of insulin taken by a patient, represented by numeral 34, and the amount of insulin taken by a patient, represented by numeral 36.
- the names identifying the data stored in computer 10 and device 12 may be generated in any suitable manner.
- the names of the different types of data may be selected at the factory, during the manufacture of the software stored on computer 10 and the manufacture of device 12.
- some fields of data may be named either by a health care provider monitoring a patient, or by the patient himself.
- the "blood glucose” data field may be added to the database during manufacture of the computer 10, but a health care provider may select the name "insulin type" 24 to represent the data stored on computer 10 that is associated with the type of insulin utilized by the patient after the provider has purchased the software installed on computer 10.
- a patient may select the name "insulin” 34 to represent the data stored in device 12 relating to the type of insulin utilized by the patient. It should be noted that in the present example, the health care provider has used the title "insulin" to represent the data 26 associated with the amount of insulin being utilized by the patient.
- each field of data 20, 22, 24, 26 stored within computer 10 includes a metadata identifier, or unique global identifier, represented by numerals 20', 22', 24", 26' respectively.
- each field of data 30, 32, 34, 36 stored within device 12 includes a metadata identifier, represented by numerals 30', 32", 34', 36', respectively.
- the metadata identifiers 20', 22', 24 1 , 26', 30', 32', 34', 36' may be associated with the data 20, 22, 24, 26, 30, 32, 34, 36 in any suitable manner.
- identical types of data have identical metadata identifiers.
- the metadata identifier 20' assigned to the blood glucose data 20 stored on computer 10 is identical to the metadata identifier 30' assigned to the blood glucose data 30 stored on device 12.
- the metadata 24' associated with insulin type data 24 stored on computer 10 is identical to the metadata 34' associated with the insulin type data 34 stored on device 12, even though the data fields 24, 34 have different names. It should noted that in embodiments, the data fields 24, 34 may have originally had identical names, but the names of the data fields 24, 34 may have been changed at a later time.
- the metadata identifiers 20 1 , 22', 24", 26', 30", 32", 34", 36" may be generated in any conventional manner.
- the metadata identifiers are created by the application.
- certain types of data including the data field and the associated name, such as blood glucose measurements 20, 30 may be established at the factory during the production of the software utilized by computer 10 and device 12.
- Other types of data, such as the type of insulin utilized by the patient may be configured for storage in the database by either the patient or the health care provider.
- pre-set metadata identifiers may be utilized to identify the pre-set data types. This understanding may hold true in later versions of the software, thereby allowing a specific pre-set data type to utilize an identical metadata identifier in multiple versions of the software and in different products.
- the metadata identifiers generated for data types originating at the factory are consistent for all deployments of software and devices. For example, in previous versions of the software a specific metadata identifier may be associated with measurements relating to blood glucose levels in a patient. Going forward, in each new version of software or each new version of medical device in production, the measurements relating to blood glucose level of a patient are associated with the same metadata identifier. Accordingly, later versions of the software will be capable of identifying various types of data utilized in earlier versions of the software or in older devices.
- the metadata identifiers created by the software or the device, after each has left the factory, are generally not repeated.
- double arrow 40 represents the communication between computer 10 and device 12.
- the communication represented by arrow 40 may occur when a user is downloading data from device 12 onto computer 10.
- the computer 10 compares metadata identifier 30' to the metadata identifiers 20', 22', 24', 26' present within the database resident in the memory of computer 10.
- the metadata identifier 30' matches metadata identifier 20', since both of the metadata identifiers 20', 30' refer to the same type of data.
- the data relating to blood glucose measurements 30 present within the memory of device 12 is merged with the data relating to blood glucose measurements 20 present within the memory of computer 10.
- the merging of the data 20, 30 may be accomplished in any suitable manner.
- Figure 3 illustrates the memory of the computer 10 and the device 12 following the above described process.
- Computer 10 will continue to compare the metadata identifier as additional data is downloaded. Note that in the present example, computer 10 does not include metadata that corresponds to the metadata identifier 32'. Accordingly, the data representative of the height of the patient 32 is copied from device 12 onto computer 10 as a new data field. The data 32 may then be deleted from device 12, thereby leaving the memory of computer 10 and device 12 configured as depicted in Figure 4. In embodiments of the invention, data 32 may not be copied onto computer 10 and may continue to reside on device 12.
- Metadata identifier 34' identifies the data 34 in device 12. Accordingly, computer 10 compares metadata identifier 34' to the metadata identifiers 20', 22', 24', 26', 32' present within the memory of computer 10 in order to determine if computer 10 has a type of data corresponding to insulin 34.
- metadata 34' corresponds to metadata 24', as both types of metadata 24', 34' identify data relating to the type of insulin being taken by the patient.
- the metadata identifiers 24', 34' are identical even though the data identifiers 24, 34 have different names. Accordingly, as shown in Figure 5, the insulin data 34 may be combined with the insulin type data 24 in computer 10, and insulin data 34 may be deleted from device 12.
- device 12 again sends metadata identifier 36' to computer 10.
- Computer 10 compares metadata identifier 36" with all of the metadata identifiers 20', 22', 24', 26', 32' stored in the memory of computer 10.
- metadata identifier 36' corresponds to metadata identifier 26'.
- the data 36 corresponding to metadata identifier 36' has a different name than the data 26 corresponding to metadata identifier 26'. Since metadata 36' corresponds to metadata 26', however, the data represented by data field 36 is copied into the data field 26. Once the data 36 has been copied into the field 26, the data in field 36 may be deleted from device 12.
- the software running on computer 10 utilizes the metadata identifiers 20', 22', 24', 26', 30', 32', 34', 36' to actually identify the different data types
- the different data types may be identified by any name.
- users may add additional data fields to the computer 10 and/or device 12 after the computer 10 and device 12 have been shipped from the factory.
- the software on the computer 10 and device 12 assigns a suitable metadata identifier to the data field.
- the computer 10 and device 12 may generate the metadata identifier in any suitable manner.
- the user of the computer 10 may create a data field configured to store a specific type of data
- the user of device 12 may create a data field configured to store the same specific type of data.
- the user of computer 10 may create a user defined data field to record the blood pressure of the patient.
- numeral 50 represents the blood pressure field of data on computer 10
- numeral 50' represents the metadata identifier of the blood pressure data 50 on computer 10.
- a user may create a field of data capable of storing blood pressure measurements on device 12.
- numeral 52 represents the blood pressure field of data on device 12
- numeral 52' represents the metadata identifier of the blood pressure data 52 on device 12.
- computer 10 when queried to display blood pressure data, will display all data associated with metadata identifiers 50', 52'. In addition, going forward, computer 10 will automatically associate metadata identifier 52' with metadata identifier 50'. Thus, in the future, when device 12 is linked to computer 10 and computer 10 receives metadata identifier 52' from device 12, computer 10 will associate data field 52 with data field 50, in a manner described above.
- the computer 10 is also capable of uploading data onto device 12. Generally, this would occur in a manner similar to that described above, wherein the device would compare the metadata identifier of the newly received data with the metadata identifiers of the data stored on the device before determining whether the newly received data was new data or intended to be combined with data already present on the device.
- PDAs personal digital assistants
- infusion pumps blood glucose meters
- cellular phones or integrated devices including a glucose measurement engine and a PDA or cellular device.
- exemplary physiological information includes A1c values, Albumin values, Albumin excretion values, body mass index values, blood pressure values, carbohydrate values, cholesterol values (total, HDL, LDL, ratio) cheatinine values, fructosamine values, HbA1 values, height values, insulin dose values, insulin rate values, total daily insulin values, ketone values, microalbumin values, proteinuria values, heart rate values, temperature values, triglyceride values, and weight values.
- the invention is described herein with reference to healthcare data management software, and more particularly, with reference to diabetes management software, although the invention may be applied, generally, to data management systems in fields unrelated to healthcare management.
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.
Description
METHOD AND SYSTEM FOR MERGING EXTENSIBLE DATA INTO A DATABASE USING GLOBALLY UNIQUE IDENTIFIERS
Field of the Invention
[0001] The present invention relates to a method of merging data from multiple databases into a single database. Specifically, the present invention relates to utilizing globally unique identifiers in the databases to distinguish between different types of data.
Background of the Invention
[0002] Merging data contained in a plurality of databases is known. The databases may include fields of data defined by a name identifier. In some cases, different databases may contain different types of data identified by the same name identifier. When a user selects the data fields to be merged in the combined database, the fields having the same name identifier from the separate databases may be combined into a single data field, even if those fields represent different types of data.
Summary of the Invention
[0003] An embodiment of the invention comprises a method of transferring a first set of data from a first database to a second database. The method includes 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.
-[0004] Embodiments of the invention further include the step of adding the first set of data to the second database if the metadata identifier does not match the plurality of metadata identifiers in the second database. The method may include the step of configuring a portion of the first database to store the first set of data. The
metadata identifier is assigned to the first set of data when a user creates the first set of data. The method may include 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.
[0005] In embodiments of the invention, the first database is stored on a device, and the second database is stored on a computer. In embodiments, the first database is stored on a first computer, and the second database is stored on a second computer.
[0006] An embodiment of the invention comprises 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 includes 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 each 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 identifier of the second database.
Brief Description of the Drawings
[0007] The above-mentioned and other features of this invention, and the manner of attaining them, will become more apparent and the invention itself will be better understood by reference to the following description of embodiments of the invention taken in conjunction with the accompanying drawings, wherein:
[0008] Figure 1 depicts an example of an embodiment of a system utilizing the present invention; and
[0009] Figures 2 through 7 depict schematic diagrams illustrating embodiments of the present invention utilizing the system depicted in Figure 1 for exemplary purposes.
[0010] Although the drawings represent embodiments of various features and components according to the present invention, the drawings are not necessarily to scale and certain features may be exaggerated in order to better illustrate and explain the present invention. The exemplifications set out herein illustrate embodiments of the invention, and such exemplifications are not to be construed as limiting the scope of the invention in any manner.
Detailed Description of Embodiments of the Invention
[0011] For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings, which are described below. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. The invention includes any alterations and further modifications in the illustrated devices and described methods and further applications of the principles of the invention, which would normally occur to one skilled in the art to which the invention relates. Moreover, the embodiments were selected for description to enable one of ordinary skill in the art to practice the invention.
[0012] Concepts described below may be further explained in one of more of the co-filed patent applications entitled HELP UTILITY FUNCTIONALITY AND ARCHITECTURE (Atty Docket: ROCHE-P0033), METHOD AND SYSTEM FOR GRAPHICALLY INDICATING MULTIPLE DATA VALUES (Atty Docket: ROCHE- P0039), SYSTEM AND METHOD FOR DATABASE INTEGRITY CHECKING (Atty Docket: ROCHE-P0056), METHOD AND SYSTEM FOR DATA SOURCE AND MODIFICATION TRACKING (Atty Docket: ROCHE-P0037), PATIENT-CENTRIC HEALTHCARE INFORMATION MAINTENANCE (Atty Docket: ROCHE-P0043), EXPORT FILE FORMAT WITH MANIFEST FOR ENHANCED DATA TRANSFER (Atty Docket: ROCHE-P0044), GRAPHIC ZOOM FUNCTIONALITY FOR A CUSTOM REPORT (Atty Docket: ROCHE-P0048), METHOD AND SYSTEM FOR SELECTIVE MERGING OF PATIENT DATA (Atty Docket: ROCHE-P0065), METHOD AND SYSTEM FOR PERSONAL MEDICAL DATA DATABASE MERGING (Atty Docket:
ROCHE-P0066), METHOD AND SYSTEM FOR WIRELESS DEVICE COMMUNICATION (Atty Docket: ROCHE-P0034), METHOD AND SYSTEM FOR SETTING TIME BLOCKS (Atty Docket: ROCHE-P0054), METHOD AND SYSTEM FOR ENHANCED DATA TRANSFER (Atty Docket: ROCHE-P0042), COMMON EXTENSIBLE DATA EXCHANGE FORMAT (Atty Docket: ROCHE-P0036), METHOD OF CLONING SERVER INSTALLATION TO A NETWORK CLIENT (Atty Docket: ROCHE-P0035), METHOD AND SYSTEM FOR QUERYING A DATABASE (Atty Docket: ROCHE-P0049), METHOD AND SYSTEM FOR EVENT BASED DATA COMPARISON (Atty Docket: ROCHE-P0050), DYNAMIC COMMUNICATION STACK (Atty Docket: ROCHE-P0051), SYSTEM AND METHOD FOR REPORTING MEDICAL INFORMATION (Atty Docket: ROCHE-P0045), METHOD AND SYSTEM FOR ACTIVATING FEATURES AND FUNCTIONS OF A CONSOLIDATED SOFTWARE APPLICATION (Atty Docket: ROCHE-P0057), METHOD AND SYSTEM FOR CONFIGURING A CONSOLIDATED SOFTWARE APPLICATION (Atty Docket: ROCHE-P0058), METHOD AND SYSTEM FOR DATA SELECTION AND DISPLAY (Atty Docket: ROCHE-P0011), METHOD AND SYSTEM FOR ASSOCIATING DATABASE CONTENT FOR SECURITY ENHANCEMENT (Atty Docket: ROCHE- P0041), METHOD AND SYSTEM FOR CREATING REPORTS (Atty Docket: ROCHE-P0046), METHOD AND SYSTEM FOR CREATING USER-DEFINED OUTPUTS (Atty Docket: ROCHE-P0047), DATA DRIVEN COMMUNICATION PROTOCOL GRAMMAR (Atty Docket: ROCHE-P0055), HEALTHCARE MANAGEMENT SYSTEM HAVING IMPROVED PRINTING OF DISPLAY SCREEN INFORMATION (Atty Docket: ROCHE-P0031), and METHOD AND SYSTEM FOR MULTI-DEVICE COMMUNICATION (Atty Docket: ROCHE-P0064), the entire disclosures of which are hereby expressly incorporated herein by reference. It should be understood that the concepts described below may relate to diabetes management software systems for tracking and analyzing health data, such as, for example, the ACCU-CHEK® 360° product provided by Roche Diagnostics. However, the concepts described herein may also have applicability to apparatuses, methods, systems, and software in fields that are unrelated to healthcare. Furthermore, it
should be understood that references in this patent application to devices, meters, monitors, pumps, or related terms are intended to encompass any currently existing or later developed apparatus that includes some or all of the features attributed to the referred to apparatus, including but not limited to the ACCU-CHEK® Active, Accu- CHEK® Aviva, ACCU-CHEK® Compact, ACCU-CHEK® Compact Plus, ACCU-CHEK® Integra, ACCU-CHEK® GO, ACCU-CHEK® Performa, ACCU-CHEK® Spirit, ACCU-CHEK® D- Tron Plus, and ACCU-CHEK® Voicemate Plus, all provided by Roche Diagnostics or divisions thereof.
[0013] Figure 1 depicts a computer, generally indicated by numeral 10, and a medical device, generally indicated by numeral 12. Computer 10 may be any type of computer capable of running software. In the depicted embodiment, computer 10 is a laptop computer. In addition, computer 10 includes receiver 14. Receiver 14 may be connected to computer 10 in any suitable manner, such as through a USB connection, for example.
[0014] For purposes of the present example, computer 10 includes a hard drive (not shown) capable of storing data in a conventional manner. The software stored in the memory of computer 10 generally allows computer 10 to communicate with device 12. In embodiments, the software allows computer 10 to communicate with device 12 by way of receiver 14. In embodiments, the software installed on computer 10 may be ACCU-CHEK® 360° software manufactured by Roche Diagnostics. Although the software is described herein for operation on a computer (e.g., desktop, laptop or tablet), it should be understood that the principles of the invention may be embodied in software for operation on various devices, including but not limited to personal digital assistants ("PDAs"), infusion pumps, blood glucose meters, cellular phones, or integrated devices including a glucose measurement engine and a PDA or cellular device.
[0015] Device 12 may be any suitable medical device capable of communicating with the software stored on computer 10, such as a blood glucose meter, for example. Device 12 includes a dynamic memory, thereby allowing the device 12 to store and save various types of data. For example, as device 12 is
utilized to measure exemplary physiological information in patients, such as the blood glucose levels of patients, and the measured values may be saved in the memory of the device 12. Furthermore, device 12 may allow a user to add additional data to the memory that is not measured directly by device 12, such as the weight of the patient, for example. In general, the data stored in the memory of device 12 may be stored in a database in the memory of device 12.
[0016] In the present example, the software executed by computer 10 is configured to allow computer 10 to communicate with device 12 by way of receiver 14. The communication between device 12 and receiver 14 may occur in any suitable manner. For example, device 12 and receiver 14 may communicate wirelessly, such as via infrared signals or via radio frequency signals. In embodiments, device 12 may communicate with receiver 14 in a non-wireless manner utilizing a direct connection, such as that which may be established using a suitable cord and plug combination, for example. It should be noted that in embodiments, the device 12 may communicate directly with computer 10, in a suitable manner. For example, device 12 may communicate with computer 10 in a wireless manner or non-wireless manner without the utilization of receiver 14.
[0017] Generally, once a connection between computer 10 and device 12 has been established, the data stored in the database of device 12 may be downloaded onto computer 10. The user may initiate the download process, or in embodiments, the download process may occur automatically.
[0018] Figure 2 is a schematic that represents the databases in the memory of computer 10 and device 12. In Figure 2, numerals 20, 22, 24, 26 represent different sets of various types of data stored in the memory of computer 10. Similarly, numerals 30, 32, 34, 36 represent different fields, or sets, of various types of data stored in the memory of device 12. Specifically, the memory of computer 10 includes data relating to blood glucose measurements of a patient, represented by numeral 20, weight measurements of a patient, represented by numeral 22, the type of insulin taken by a patient, represented by numeral 24, and the amount of insulin taken by a patient, represented by numeral 26. The memory of device 12 includes data
associated with the blood glucose measurements of a patient, represented by numeral 30, the height measurements of a patient, represented by numeral 32, the type of insulin taken by a patient, represented by numeral 34, and the amount of insulin taken by a patient, represented by numeral 36.
[0019] It should be noted that the names identifying the data stored in computer 10 and device 12 may be generated in any suitable manner. For example, the names of the different types of data may be selected at the factory, during the manufacture of the software stored on computer 10 and the manufacture of device 12. In addition, some fields of data may be named either by a health care provider monitoring a patient, or by the patient himself. For instance, in the depicted example, the "blood glucose" data field may be added to the database during manufacture of the computer 10, but a health care provider may select the name "insulin type" 24 to represent the data stored on computer 10 that is associated with the type of insulin utilized by the patient after the provider has purchased the software installed on computer 10. Similarly, a patient may select the name "insulin" 34 to represent the data stored in device 12 relating to the type of insulin utilized by the patient. It should be noted that in the present example, the health care provider has used the title "insulin" to represent the data 26 associated with the amount of insulin being utilized by the patient.
[0020] Referring still to Figure 2, each field of data 20, 22, 24, 26 stored within computer 10 includes a metadata identifier, or unique global identifier, represented by numerals 20', 22', 24", 26' respectively. Similarly, each field of data 30, 32, 34, 36 stored within device 12 includes a metadata identifier, represented by numerals 30', 32", 34', 36', respectively. The metadata identifiers 20', 22', 241, 26', 30', 32', 34', 36' may be associated with the data 20, 22, 24, 26, 30, 32, 34, 36 in any suitable manner. Generally, identical types of data have identical metadata identifiers. For example, the metadata identifier 20' assigned to the blood glucose data 20 stored on computer 10 is identical to the metadata identifier 30' assigned to the blood glucose data 30 stored on device 12. Similarly, the metadata 24' associated with insulin type data 24 stored on computer 10 is identical to the metadata 34' associated with the
insulin type data 34 stored on device 12, even though the data fields 24, 34 have different names. It should noted that in embodiments, the data fields 24, 34 may have originally had identical names, but the names of the data fields 24, 34 may have been changed at a later time.
[0021] The metadata identifiers 201, 22', 24", 26', 30", 32", 34", 36" may be generated in any conventional manner. In the present example, the metadata identifiers are created by the application. As discussed above, certain types of data including the data field and the associated name, such as blood glucose measurements 20, 30 may be established at the factory during the production of the software utilized by computer 10 and device 12. Other types of data, such as the type of insulin utilized by the patient, may be configured for storage in the database by either the patient or the health care provider.
[0022] With respect to the pre-set data types that originate from the factory, pre-set metadata identifiers may be utilized to identify the pre-set data types. This understanding may hold true in later versions of the software, thereby allowing a specific pre-set data type to utilize an identical metadata identifier in multiple versions of the software and in different products. Generally, the metadata identifiers generated for data types originating at the factory are consistent for all deployments of software and devices. For example, in previous versions of the software a specific metadata identifier may be associated with measurements relating to blood glucose levels in a patient. Going forward, in each new version of software or each new version of medical device in production, the measurements relating to blood glucose level of a patient are associated with the same metadata identifier. Accordingly, later versions of the software will be capable of identifying various types of data utilized in earlier versions of the software or in older devices. The metadata identifiers created by the software or the device, after each has left the factory, are generally not repeated.
[0023] With reference still to Figure 2, double arrow 40 represents the communication between computer 10 and device 12. The communication
represented by arrow 40 may occur when a user is downloading data from device 12 onto computer 10.
[0024] As computer 10 receives, for example, the data 30 relating to blood glucose measurements from device 12, the computer 10 compares metadata identifier 30' to the metadata identifiers 20', 22', 24', 26' present within the database resident in the memory of computer 10. In the present example, the metadata identifier 30' matches metadata identifier 20', since both of the metadata identifiers 20', 30' refer to the same type of data. Accordingly, the data relating to blood glucose measurements 30 present within the memory of device 12 is merged with the data relating to blood glucose measurements 20 present within the memory of computer 10. The merging of the data 20, 30 may be accomplished in any suitable manner. Once the blood glucose measurements 30 have been merged with the blood glucose measurements 20, the data relating to the blood glucose measurements 30 stored on device 12 may be deleted from device 12. Figure 3 illustrates the memory of the computer 10 and the device 12 following the above described process.
[0025] Computer 10 will continue to compare the metadata identifier as additional data is downloaded. Note that in the present example, computer 10 does not include metadata that corresponds to the metadata identifier 32'. Accordingly, the data representative of the height of the patient 32 is copied from device 12 onto computer 10 as a new data field. The data 32 may then be deleted from device 12, thereby leaving the memory of computer 10 and device 12 configured as depicted in Figure 4. In embodiments of the invention, data 32 may not be copied onto computer 10 and may continue to reside on device 12.
[0026] The type of insulin utilized by the patient is stored on device 12 in data field 34. Metadata identifier 34' identifies the data 34 in device 12. Accordingly, computer 10 compares metadata identifier 34' to the metadata identifiers 20', 22', 24', 26', 32' present within the memory of computer 10 in order to determine if computer 10 has a type of data corresponding to insulin 34. In the present example, metadata 34' corresponds to metadata 24', as both types of metadata 24', 34' identify data relating to the type of insulin being taken by the patient. It should be noted that the
metadata identifiers 24', 34' are identical even though the data identifiers 24, 34 have different names. Accordingly, as shown in Figure 5, the insulin data 34 may be combined with the insulin type data 24 in computer 10, and insulin data 34 may be deleted from device 12.
[0027] With reference still to Figure 5, device 12 again sends metadata identifier 36' to computer 10. Computer 10 compares metadata identifier 36" with all of the metadata identifiers 20', 22', 24', 26', 32' stored in the memory of computer 10. In the present example, metadata identifier 36' corresponds to metadata identifier 26'. It should be noted that the data 36 corresponding to metadata identifier 36' has a different name than the data 26 corresponding to metadata identifier 26'. Since metadata 36' corresponds to metadata 26', however, the data represented by data field 36 is copied into the data field 26. Once the data 36 has been copied into the field 26, the data in field 36 may be deleted from device 12.
[0028] It should be noted that since the software running on computer 10 utilizes the metadata identifiers 20', 22', 24', 26', 30', 32', 34', 36' to actually identify the different data types, the different data types may be identified by any name. Thus, in embodiments of the invention, users may add additional data fields to the computer 10 and/or device 12 after the computer 10 and device 12 have been shipped from the factory. As the users add new data types to the memory, the software on the computer 10 and device 12 assigns a suitable metadata identifier to the data field. The computer 10 and device 12 may generate the metadata identifier in any suitable manner.
[0029] In embodiments of the invention, the user of the computer 10 may create a data field configured to store a specific type of data, and the user of device 12 may create a data field configured to store the same specific type of data. For example, with respect to Figure 7, the user of computer 10 may create a user defined data field to record the blood pressure of the patient. In the depicted embodiment, numeral 50 represents the blood pressure field of data on computer 10, and numeral 50' represents the metadata identifier of the blood pressure data 50 on computer 10. Similarly, a user may create a field of data capable of storing blood pressure
measurements on device 12. In the depicted embodiment, numeral 52 represents the blood pressure field of data on device 12, and numeral 52' represents the metadata identifier of the blood pressure data 52 on device 12. For purposes of the present example, it is assumed that the user entered different blood pressure data of the same type on computer 10 and device 12.
[0030] Once the link 40 is established between computer 10 and device 12, in a manner similar to that described above, computer 10 will compare metadata identifier 52' to the metadata identifiers 20', 22', 24', 26', 32', 50' stored in the database of computer 10. In this example, since the data fields 50, 52 for the blood pressure data on the computer 10 and device 12 were created independent of each other, the respective metadata identifiers 50', 52' are not identical. Thus, during the download process, the user may manually instruct the computer 10 to consider the metadata identifiers 50', 52' as being identical since the identifiers identify the same type of data. Accordingly, the computer 10 combines data 52 with data 50, and data 52 is deleted from device 12. Thus, computer 10, when queried to display blood pressure data, will display all data associated with metadata identifiers 50', 52'. In addition, going forward, computer 10 will automatically associate metadata identifier 52' with metadata identifier 50'. Thus, in the future, when device 12 is linked to computer 10 and computer 10 receives metadata identifier 52' from device 12, computer 10 will associate data field 52 with data field 50, in a manner described above.
[0031] It should be noted that the computer 10 is also capable of uploading data onto device 12. Generally, this would occur in a manner similar to that described above, wherein the device would compare the metadata identifier of the newly received data with the metadata identifiers of the data stored on the device before determining whether the newly received data was new data or intended to be combined with data already present on the device.
[0032] Although the software is described herein for operation on a computer
(e.g., desktop, laptop or tablet), it should be understood that the principles of the invention may be embodied in software for operation on various devices, including
but not limited to personal digital assistants ("PDAs"), infusion pumps, blood glucose meters, cellular phones, or integrated devices including a glucose measurement engine and a PDA or cellular device.
[0033] In addition to blood glucose values, exemplary physiological information includes A1c values, Albumin values, Albumin excretion values, body mass index values, blood pressure values, carbohydrate values, cholesterol values (total, HDL, LDL, ratio) cheatinine values, fructosamine values, HbA1 values, height values, insulin dose values, insulin rate values, total daily insulin values, ketone values, microalbumin values, proteinuria values, heart rate values, temperature values, triglyceride values, and weight values.
[0034] The invention is described herein with reference to healthcare data management software, and more particularly, with reference to diabetes management software, although the invention may be applied, generally, to data management systems in fields unrelated to healthcare management.
[0035] While the invention is described herein with reference to medical devices, and more particularly, with reference to diabetes management devices, the invention is applicable to any data obtained from any device.
[0036] While this invention has been described as having an exemplary design, the present invention may be further modified within the spirit and scope of this disclosure. This application is therefore intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains.
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.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/999,947 US8112390B2 (en) | 2007-12-07 | 2007-12-07 | Method and system for merging extensible data into a database using globally unique identifiers |
US11/999,947 | 2007-12-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009071201A1 true WO2009071201A1 (en) | 2009-06-11 |
Family
ID=40372144
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2008/009874 WO2009071201A1 (en) | 2007-12-07 | 2008-11-21 | Method and system for merging extensible data into a database using globally unique identifiers |
Country Status (2)
Country | Link |
---|---|
US (1) | US8112390B2 (en) |
WO (1) | WO2009071201A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011048550A1 (en) * | 2009-10-21 | 2011-04-28 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for data exchange in a distributed system |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9818211B1 (en) * | 2013-04-25 | 2017-11-14 | Domo, Inc. | Automated combination of multiple data visualizations |
EP3014490A4 (en) | 2013-06-24 | 2017-02-22 | K2View Ltd. | Cdbms (cloud database management system) distributed logical unit repository |
US9489152B2 (en) | 2014-02-24 | 2016-11-08 | Ricoh Company, Ltd. | Object distribution in advanced function presentation environments |
US10387976B2 (en) | 2015-12-02 | 2019-08-20 | Metropolitan Washington Airports Authority | Federated system for centralized management and distribution of content media |
US11711696B1 (en) | 2018-03-13 | 2023-07-25 | Metropolitan Washington Airports Authority | Systems and methods for implementing an airline ticket counter system in a mobile app |
US11226972B2 (en) | 2019-02-19 | 2022-01-18 | International Business Machines Corporation | Ranking collections of document passages associated with an entity name by relevance to a query |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6748402B1 (en) * | 2001-04-02 | 2004-06-08 | Bellsouth Intellectual Property Corporation | System and method for converting and loading interactive pager address books |
Family Cites Families (107)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US567409A (en) * | 1896-09-08 | Wilson e | ||
US5251126A (en) * | 1990-10-29 | 1993-10-05 | Miles Inc. | Diabetes data analysis and interpretation method |
SG49695A1 (en) | 1992-10-15 | 1998-06-15 | Gen Hospital Corp | An infusion pump with an electronically loadable drug library |
US6330426B2 (en) * | 1994-05-23 | 2001-12-11 | Stephen J. Brown | System and method for remote education using a memory card |
US5951300A (en) * | 1997-03-10 | 1999-09-14 | Health Hero Network | Online system and method for providing composite entertainment and health information |
US7624028B1 (en) * | 1992-11-17 | 2009-11-24 | Health Hero Network, Inc. | Remote health monitoring and maintenance system |
US5497486A (en) * | 1994-03-15 | 1996-03-05 | Salvatore J. Stolfo | Method of merging large databases in parallel |
CA2120447C (en) * | 1994-03-31 | 1998-08-25 | Robert Lizee | Automatically relaxable query for information retrieval |
US5671409A (en) | 1995-02-14 | 1997-09-23 | Fatseas; Ted | Computer-aided interactive career search system |
US6453325B1 (en) * | 1995-05-24 | 2002-09-17 | International Business Machines Corporation | Method and means for backup and restoration of a database system linked to a system for filing data |
US5758355A (en) * | 1996-08-07 | 1998-05-26 | Aurum Software, Inc. | Synchronization of server database with client database using distribution tables |
AU5405798A (en) | 1996-12-30 | 1998-07-31 | Imd Soft Ltd. | Medical information system |
US6032119A (en) * | 1997-01-16 | 2000-02-29 | Health Hero Network, Inc. | Personalized display of health information |
ES2124186B1 (en) | 1997-01-20 | 1999-08-01 | Carpe Diem Salud S L | SECTION AND TELEMATIC CONTROL SYSTEM OF PHYSIOLOGICAL PARAMETERS OF PATIENTS. |
US5995962A (en) | 1997-07-25 | 1999-11-30 | Claritech Corporation | Sort system for merging database entries |
US6024699A (en) * | 1998-03-13 | 2000-02-15 | Healthware Corporation | Systems, methods and computer program products for monitoring, diagnosing and treating medical conditions of remotely located patients |
DE19814219A1 (en) * | 1998-03-31 | 1999-10-07 | Roche Diagnostics Gmbh | Insulin medication control procedures |
US7647237B2 (en) | 1998-04-29 | 2010-01-12 | Minimed, Inc. | Communication station and software for interfacing with an infusion pump, analyte monitor, analyte meter, or the like |
US6602469B1 (en) * | 1998-11-09 | 2003-08-05 | Lifestream Technologies, Inc. | Health monitoring and diagnostic device and network-based health assessment and medical records maintenance system |
WO2000065522A2 (en) * | 1999-04-28 | 2000-11-02 | San Diego State University Foundation | Electronic medical record registry including data replication |
US6651216B1 (en) * | 1999-05-10 | 2003-11-18 | Dave Sullivan | Efficiently navigating a workbook linked to a database |
WO2000072181A2 (en) | 1999-05-20 | 2000-11-30 | Minimed Inc. | Integrated medical information management system |
US7475019B2 (en) * | 1999-11-18 | 2009-01-06 | Visicu, Inc. | System and method for physician note creation and management |
US6804656B1 (en) * | 1999-06-23 | 2004-10-12 | Visicu, Inc. | System and method for providing continuous, expert network critical care services from a remote location(s) |
US6684191B1 (en) * | 1999-11-22 | 2004-01-27 | International Business Machines Corporation | System and method for assessing a procurement and accounts payable system |
US20020007284A1 (en) * | 1999-12-01 | 2002-01-17 | Schurenberg Kurt B. | System and method for implementing a global master patient index |
US6564105B2 (en) * | 2000-01-21 | 2003-05-13 | Medtronic Minimed, Inc. | Method and apparatus for communicating between an ambulatory medical device and a control device via telemetry using randomized data |
US6605038B1 (en) * | 2000-06-16 | 2003-08-12 | Bodymedia, Inc. | System for monitoring health, wellness and fitness |
US20030002848A1 (en) * | 2000-06-28 | 2003-01-02 | Yoshiki Kawaoka | Delivery-medium producing apparatus |
US20020059299A1 (en) * | 2000-07-14 | 2002-05-16 | Frederic Spaey | System and method for synchronizing databases |
US9135393B1 (en) * | 2000-08-02 | 2015-09-15 | Smiths Medical Asd, Inc. | Processing program data for medical pumps |
US6633772B2 (en) * | 2000-08-18 | 2003-10-14 | Cygnus, Inc. | Formulation and manipulation of databases of analyte and associated values |
ES2287156T3 (en) * | 2000-09-08 | 2007-12-16 | Insulet Corporation | DEVICES AND SYSTEMS FOR THE INFUSION OF A PATIENT. |
AU9658801A (en) * | 2000-10-04 | 2002-04-15 | Insulet Corp | Data collection assembly for patient infusion system |
US7207009B1 (en) * | 2000-11-01 | 2007-04-17 | Microsoft Corporation | Method and system for displaying an image instead of data |
US7756722B2 (en) * | 2001-02-01 | 2010-07-13 | Georgetown University | Clinical management system from chronic illnesses using telecommunication |
US8019693B2 (en) * | 2001-03-28 | 2011-09-13 | Hewlett-Packard Development Company, L.P. | Systems and methods for utilizing printing device data in a customer service center |
WO2002078512A2 (en) * | 2001-04-02 | 2002-10-10 | Therasense, Inc. | Blood glucose tracking apparatus and methods |
US7165062B2 (en) * | 2001-04-27 | 2007-01-16 | Siemens Medical Solutions Health Services Corporation | System and user interface for accessing and processing patient record information |
US7179226B2 (en) * | 2001-06-21 | 2007-02-20 | Animas Corporation | System and method for managing diabetes |
US7117225B2 (en) * | 2001-08-13 | 2006-10-03 | Jasmin Cosic | Universal data management interface |
US20030065536A1 (en) * | 2001-08-13 | 2003-04-03 | Hansen Henrik Egesborg | Portable device and method of communicating medical data information |
US6781522B2 (en) * | 2001-08-22 | 2004-08-24 | Kivalo, Inc. | Portable storage case for housing a medical monitoring device and an associated method for communicating therewith |
US20030069758A1 (en) * | 2001-10-10 | 2003-04-10 | Anderson Laura M. | System and method for use in providing a healthcare information database |
US20030098869A1 (en) * | 2001-11-09 | 2003-05-29 | Arnold Glenn Christopher | Real time interactive video system |
US20030199739A1 (en) * | 2001-12-17 | 2003-10-23 | Gordon Tim H. | Printing device for personal medical monitors |
US7082334B2 (en) * | 2001-12-19 | 2006-07-25 | Medtronic, Inc. | System and method for transmission of medical and like data from a patient to a dedicated internet website |
US7647320B2 (en) * | 2002-01-18 | 2010-01-12 | Peoplechart Corporation | Patient directed system and method for managing medical information |
US20030145206A1 (en) * | 2002-01-25 | 2003-07-31 | Jack Wolosewicz | Document authentication and verification |
US6852104B2 (en) * | 2002-02-28 | 2005-02-08 | Smiths Medical Md, Inc. | Programmable insulin pump |
US8504179B2 (en) * | 2002-02-28 | 2013-08-06 | Smiths Medical Asd, Inc. | Programmable medical infusion pump |
US6978268B2 (en) * | 2002-03-16 | 2005-12-20 | Siemens Medical Solutions Health Services Corporation | Healthcare organization central record and record identifier management system |
US7007036B2 (en) * | 2002-03-28 | 2006-02-28 | Lsi Logic Corporation | Method and apparatus for embedding configuration data |
US20030208465A1 (en) | 2002-04-12 | 2003-11-06 | Respironics, Inc. | Method for managing medical information and medical information management system |
US20040030987A1 (en) * | 2002-04-30 | 2004-02-12 | Manelli Donald D. | Method for generating customized patient education documents |
US7120488B2 (en) | 2002-05-07 | 2006-10-10 | Medtronic Physio-Control Manufacturing Corp. | Therapy-delivering portable medical device capable of triggering and communicating with an alarm system |
US7028058B2 (en) * | 2002-05-23 | 2006-04-11 | Hewlett-Packard Development Company, L.P. | System and method for preserving metadata in an electronic image file |
US7020508B2 (en) * | 2002-08-22 | 2006-03-28 | Bodymedia, Inc. | Apparatus for detecting human physiological and contextual information |
CA2443792A1 (en) * | 2002-10-08 | 2004-04-08 | Bayer Healthcare Llc | Method and systems for data management in patient diagnoses and treatment |
DE10250187B4 (en) * | 2002-10-28 | 2005-11-10 | OCé PRINTING SYSTEMS GMBH | Control unit with user accounts for an electrophotographic printing or copying system |
US20040086314A1 (en) * | 2002-11-06 | 2004-05-06 | Peter Chen | Standard keyboard supporting multimedia functions |
DE20217855U1 (en) | 2002-11-19 | 2003-01-16 | Key Mouse Electronic Entpr Co | Multi media function for a standard computer keyboard depends upon use of application program key |
US20040119742A1 (en) * | 2002-12-18 | 2004-06-24 | Microsoft Corporation | System and method for manipulating objects in graphical user interface |
US20040172284A1 (en) * | 2003-02-13 | 2004-09-02 | Roche Diagnostics Corporation | Information management system |
US7063665B2 (en) * | 2003-03-04 | 2006-06-20 | Tanita Corporation | Health care system |
US6873807B2 (en) * | 2003-03-20 | 2005-03-29 | Kabushiki Kaisha Toshiba | Image forming apparatus |
US20040193952A1 (en) * | 2003-03-27 | 2004-09-30 | Charumathy Narayanan | Consistency unit replication in application-defined systems |
US20050010452A1 (en) * | 2003-06-27 | 2005-01-13 | Lusen William D. | System and method for processing transaction records suitable for healthcare and other industries |
US20050004947A1 (en) * | 2003-06-30 | 2005-01-06 | Emlet James L. | Integrated tool set for generating custom reports |
US20070185390A1 (en) * | 2003-08-19 | 2007-08-09 | Welch Allyn, Inc. | Information workflow for a medical diagnostic workstation |
US20050182655A1 (en) * | 2003-09-02 | 2005-08-18 | Qcmetrix, Inc. | System and methods to collect, store, analyze, report, and present data |
EP1680014A4 (en) | 2003-10-14 | 2009-01-21 | Pelikan Technologies Inc | Method and apparatus for a variable user interface |
US6990434B2 (en) * | 2003-10-28 | 2006-01-24 | General Electric Company | System and method for coordinated remote activation of multiple software-based options |
US8038593B2 (en) * | 2003-12-05 | 2011-10-18 | Carefusion 303, Inc. | System and method for network monitoring of multiple medical devices |
US20050159977A1 (en) * | 2004-01-16 | 2005-07-21 | Pharmacentra, Llc | System and method for facilitating compliance and persistency with a regimen |
US20050192844A1 (en) * | 2004-02-27 | 2005-09-01 | Cardiac Pacemakers, Inc. | Systems and methods for automatically collecting, formatting, and storing medical device data in a database |
EP1735729A2 (en) * | 2004-03-26 | 2006-12-27 | Novo Nordisk A/S | Device for displaying data relevant for a diabetic patient |
EP1743267A1 (en) | 2004-03-31 | 2007-01-17 | Neptec Design Group Ltd. | Medical patient monitoring systems, methods and user interfaces |
US20070232866A1 (en) | 2004-03-31 | 2007-10-04 | Neptec Design Group Ltd. | Medical Patient Monitoring and Data Input Systems, Methods and User Interfaces |
US7725498B2 (en) * | 2004-04-22 | 2010-05-25 | International Business Machines Corporation | Techniques for identifying mergeable data |
MXPA06013231A (en) * | 2004-05-14 | 2007-02-28 | Bayer Healthcare Llc | Method and apparatus for implementing automatic detection of meter connection and transfer of data. |
US20050259945A1 (en) | 2004-05-20 | 2005-11-24 | Anthony Splaver | Method and system for automatic management of digital photography processing |
US20060020491A1 (en) * | 2004-07-20 | 2006-01-26 | Medtronic, Inc. | Batch processing method for patient management |
US8313433B2 (en) * | 2004-08-06 | 2012-11-20 | Medtronic Minimed, Inc. | Medical data management system and process |
US20060184524A1 (en) * | 2004-09-14 | 2006-08-17 | Gunter Pollanz | Method and system for automated data analysis, performance estimation and data model creation |
US20070088707A1 (en) * | 2004-09-15 | 2007-04-19 | Scott Durgin | Method for providing extensible software components within a distributed synchronization system |
US8892571B2 (en) | 2004-10-12 | 2014-11-18 | International Business Machines Corporation | Systems for associating records in healthcare database with individuals |
US20060095298A1 (en) * | 2004-10-29 | 2006-05-04 | Bina Robert B | Method for horizontal integration and research of information of medical records utilizing HIPPA compliant internet protocols, workflow management and static/dynamic processing of information |
EP1827215A1 (en) | 2004-11-02 | 2007-09-05 | Lifescan, Inc. | Method and computer program for pattern analysis and reporting of chronic disease state management data |
US20060149601A1 (en) | 2004-11-27 | 2006-07-06 | Mcdonough Medical Products Corporation | System and method for recording medical image data on digital recording media |
US20060161460A1 (en) * | 2004-12-15 | 2006-07-20 | Critical Connection Inc. | System and method for a graphical user interface for healthcare data |
US20060167367A1 (en) * | 2004-12-23 | 2006-07-27 | James Stanczak | Method and system for collecting data on a plurality of patients |
US20060155581A1 (en) * | 2005-01-10 | 2006-07-13 | George Eisenberger | Systems with user selectable data attributes for automated electronic search, identification and publication of relevant data from electronic data records at multiple data sources |
US20060178910A1 (en) * | 2005-01-10 | 2006-08-10 | George Eisenberger | Publisher gateway systems for collaborative data exchange, collection, monitoring and/or alerting |
US7493344B2 (en) | 2005-04-01 | 2009-02-17 | Schlumberger Technology Corporation | Method and system for dynamic data merge in databases |
US7181350B2 (en) * | 2005-05-13 | 2007-02-20 | North America Technology Services, Inc. | Blood glucose meter/modem interface arrangement |
US20070033074A1 (en) * | 2005-06-03 | 2007-02-08 | Medtronic Minimed, Inc. | Therapy management system |
US20060272652A1 (en) | 2005-06-03 | 2006-12-07 | Medtronic Minimed, Inc. | Virtual patient software system for educating and treating individuals with diabetes |
US9081470B2 (en) * | 2005-09-08 | 2015-07-14 | Microsoft Technology Licensing, Llc | Single action selection of data elements |
US20070089071A1 (en) * | 2005-10-14 | 2007-04-19 | Research In Motion Limited | Software mechanism for providing distinct types of time dependent event objects for display in a graphical user interface |
CA2637574C (en) | 2006-01-17 | 2017-10-31 | Accenture Global Services Gmbh | Platform for interoperable healthcare data exchange |
US7805400B2 (en) * | 2006-01-31 | 2010-09-28 | Microsoft Corporation | Report generation using metadata |
US7864995B2 (en) * | 2006-02-11 | 2011-01-04 | General Electric Company | Systems, methods and apparatus of handling structures in three-dimensional images |
WO2007093482A1 (en) | 2006-02-16 | 2007-08-23 | Novo Nordisk A/S | A device and a method for managing data relating to blood glucose level for a person |
US20070276197A1 (en) | 2006-05-24 | 2007-11-29 | Lifescan, Inc. | Systems and methods for providing individualized disease management |
US8579814B2 (en) * | 2007-01-05 | 2013-11-12 | Idexx Laboratories, Inc. | Method and system for representation of current and historical medical data |
US20080263007A1 (en) * | 2007-04-20 | 2008-10-23 | Sap Ag | Managing archived data |
-
2007
- 2007-12-07 US US11/999,947 patent/US8112390B2/en active Active
-
2008
- 2008-11-21 WO PCT/EP2008/009874 patent/WO2009071201A1/en active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6748402B1 (en) * | 2001-04-02 | 2004-06-08 | Bellsouth Intellectual Property Corporation | System and method for converting and loading interactive pager address books |
Non-Patent Citations (1)
Title |
---|
BILENKO M ET AL: "Adaptive name matching in information integration", IEEE INTELLIGENT SYSTEMS, vol. 18, no. 5, 1 September 2003 (2003-09-01), IEEE, New York, NY, US, pages 16 - 23, XP011101993, ISSN: 1094-7167 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011048550A1 (en) * | 2009-10-21 | 2011-04-28 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for data exchange in a distributed system |
US8429138B2 (en) | 2009-10-21 | 2013-04-23 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for data exchange in a distributed system |
Also Published As
Publication number | Publication date |
---|---|
US20090150377A1 (en) | 2009-06-11 |
US8112390B2 (en) | 2012-02-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8315989B2 (en) | System and method for database integrity checking | |
US8112390B2 (en) | Method and system for merging extensible data into a database using globally unique identifiers | |
US8452413B2 (en) | Method and system for multi-device communication | |
US9660857B2 (en) | Dynamic communication stack | |
US20180137252A1 (en) | Patient monitoring systems and methods with event log integration | |
EP3937013B1 (en) | Software distribution to medical devices via an intermediary which enforces maintenance of a transaction log | |
US10535423B2 (en) | Module and system for medical information management | |
US8019721B2 (en) | Method and system for enhanced data transfer | |
US8103241B2 (en) | Method and system for wireless device communication | |
US8893109B2 (en) | Software distribution amongst medical devices taking into account dependencies between devices | |
US20090150439A1 (en) | Common extensible data exchange format | |
US20090150176A1 (en) | Patient-centric healthcare information maintenance | |
US8977727B2 (en) | Remote configuration and selective distribution of product content to medical devices | |
US20090150683A1 (en) | Method and system for associating database content for security enhancement | |
US20090150877A1 (en) | Data driven communication protocol grammar | |
Mužný | Electronic clinical study management system with artificial intelligence-based data processing capabilities | |
US20130246085A1 (en) | Method and apparatus for processing electronic health records and other health data | |
Gengler | Report: Bovine RC5 effort |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08857616 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 08857616 Country of ref document: EP Kind code of ref document: A1 |