The invention relates to a method and system for enhanced data transfer between two or more devices.
Many fields of medical treatment and healthcare require monitoring of certain physiological parameters. Technological advancements in medicine led to the increased use of medical devices, e.g., meters and infusion pumps, to collect medical data, and of healthcare data management systems. Healthcare data management methods and systems traditionally developed for use in healthcare facilities and health management organizations are increasingly used by patients, care givers, and others. U.S. Pat. No. 7,103,578 and U.S. Published Application No. 2004/0172284 disclose two such methods and systems. Some healthcare data management systems are able to transfer data between them.
A common feature of healthcare management systems is the ability to convey information. Information can include raw data, graphical representations of data such as statistical display objects, explanations and textual interpretations, inferential information and so on. Communication and understanding can be improved by using interactive graphs to convey information. In one particular embodiment, the development of graphical user interfaces (GUI) facilitates user interaction with data processing and other software applications. In a typical embodiment, a GUI can display a number of display objects that are individually manipulable by a user utilizing a user input device. For example, the user can utilize a computer keyboard, mouse, touch screen, touch pad, roller ball or voice commands and the like to select a particular display object and to further initiate an action corresponding to the selected display object.
Medical devices may include a data stack where patient data is recorded in anticipation of downloading to a healthcare data management system. Common methods of storing data utilize LIFO and FIFO sequential orders to store data in stacks or files. Generally, the medical device stack is downloaded in its entirety and the data is then managed by the healthcare data management system. Some medical devices retain large amounts of data and have slow transfer rates. Data transfers using those devices require an amount of time which users may consider excessive and which may conflict with their lifestyle.
A system and method for enhanced data transfer is provided. The system comprises a computing device and data management software. The computing device is configured to access a portable device containing data. In accordance with one aspect of the invention, the portable device is a medical device. The method may be implemented in the system.
In accordance with an aspect of the present invention, an enhanced data transfer method is provided. In accordance with the method, a program stores a last record fingerprint corresponding to the newest record downloaded from the portable device and stored. Upon initiation of a download event, the program receives records from the portable device in sequential LIFO order and compares each record to the last record fingerprint to find a match. Once a match is found, the program stops downloading records. Alternatively, a user may opt to download previously downloaded records.
In accordance with another aspect of the present invention, an enhanced data transfer method is provided. In accordance with the method, a program stores a last record fingerprint corresponding to the newest record downloaded from the portable device and stored. Upon initiation of a download event, the program receives records from the portable device in sequential FIFO order. The program compares each downloaded record to the last record fingerprint. Until it finds a match, the program skips further processing steps on each downloaded record. When it finds a match, the program skips further processing steps on the matched record and begins full processing of all subsequent downloaded records.
In accordance with a further aspect of the present invention, a data management system for enhanced data transfer is provided. The data management system comprises a computing device, a portable device, and data management software. The portable device is configured to receive a system fingerprint from the data management software and to adapt its operation based on a relationship between the system fingerprint and the portable device records. The system fingerprint may comprise without limitation a system identifier, a hierarchical level, and a type of data management system.
In accordance with another aspect of the present invention, an enhanced data transfer method is provided. In accordance with the method, a portable device configured to adapt its operation responsive to a system fingerprint prevents deletion of records not yet downloaded to the data management software corresponding to the system fingerprint.
In accordance with another aspect of the present invention, an enhanced data transfer method is provided. In accordance with the method, a portable device configured to adapt its operation responsive to a system fingerprint selectively downloads records to data management software based on the type of data management software.
The foregoing aspects of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description when taken in conjunction with the accompanying drawings.
Corresponding reference characters indicate corresponding parts throughout the several views. 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 exemplification set out herein illustrates embodiments of the invention, and such exemplifications are not to be construed as limiting the scope of the invention in any manner.
Concepts described below may be further explained in one of more of the co-filed patent applications entitled HELP UTILITY FUNCTIONALITY AND ARCHITECTURE Ser. No. 11/999,906, METHOD AND SYSTEM FOR GRAPHICALLY INDICATING MULTIPLE DATA VALUES Ser. No. 11/999,853, SYSTEM AND METHOD FOR DATABASE INTEGRITY CHECKING Ser. No. 11/999,856, METHOD AND SYSTEM FOR DATA SOURCE AND MODIFICATION TRACKING Ser. No. 11/999,888, PATIENT-CENTRIC HEALTHCARE INFORMATION MAINTENANCE Ser. No. 11/999,874, EXPORT FILE FORMAT WITH MANIFEST FOR ENHANCED DATA TRANSFER Ser. No. 11/999,867, GRAPHIC ZOOM FUNCTIONALITY FOR A CUSTOM REPORT Ser. No. 11/999,932, METHOD AND SYSTEM FOR SELECTIVE MERGING OF PATIENT DATA Ser. No. 11/999,859, METHOD AND SYSTEM FOR PERSONAL MEDICAL DATA DATABASE MERGING Ser. No. 11/999,772, METHOD AND SYSTEM FOR WIRELESS DEVICE COMMUNICATION Ser. No. 11/999,879, METHOD AND SYSTEM FOR SETTING TIME BLOCKS Ser. No. 11/999,871, COMMON EXTENSIBLE DATA EXCHANGE FORMAT Ser. No. 11/999,871, METHOD OF CLONING SERVER INSTALLATION TO A NETWORK CLIENT Ser. No. 11/999,876, METHOD AND SYSTEM FOR QUERYING A DATABASE Ser. No. 11/999,912, METHOD AND SYSTEM FOR EVENT BASED DATA COMPARISON Ser. No. 11/999,921, DYNAMIC COMMUNICATION STACK Ser. No. 11/999,934, SYSTEM AND METHOD FOR REPORTING MEDICAL INFORMATION Ser. No. 11/999,878, METHOD AND SYSTEM FOR MERGING EXTENSIBLE DATA INTO A DATABASE USING GLOBALLY UNIQUE IDENTIFIERS Ser. No. 11/999,947, METHOD AND SYSTEM FOR ACTIVATING FEATURES AND FUNCTIONS OF A CONSOLIDATED SOFTWARE APPLICATION Ser. No. 11/999,880, METHOD AND SYSTEM FOR CONFIGURING A CONSOLIDATED SOFTWARE APPLICATION Ser. No. 11/999,894, METHOD AND SYSTEM FOR DATA SELECTION AND DISPLAY Ser. No. 11/999,896, METHOD AND SYSTEM FOR ASSOCIATING DATABASE CONTENT FOR SECURITY ENHANCEMENT Ser. No. 11/999,951, METHOD AND SYSTEM FOR CREATING REPORTS Ser. No. 11/999,851, METHOD AND SYSTEM FOR CREATING USER-DEFINED OUTPUTS Ser. No. 11/999,905, DATA DRIVEN COMMUNICATION PROTOCOL GRAMMAR Ser. No. 11/999,770, HEALTHCARE MANAGEMENT SYSTEM HAVING IMPROVED PRINTING OF DISPLAY SCREEN INFORMATION Ser. No. 11/999,855, METHOD AND SYSTEM FOR MULTI-DEVICE COMMUNICATION Ser. No. 11/999,866, and DEVICE AND METHOD FOR ASSESSING BLOOD GLUCOSE CONTROL Ser. No. 12/040,458, 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.
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. The embodiments disclosed below are not intended to be exhaustive or limit the invention to the precise form disclosed in the following detailed description. Rather, the embodiments are chosen and described so that others skilled in the art may utilize their teachings. It will 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.
The present invention relates to a method and system for enhanced data transfer. The system comprises a computer and data management software including applications and databases. An application, computer program, or program, is here, and generally, conceived to be a sequence of computer instructions representing steps of methods for achieving desired results. The instructions are processed by a computer and require physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Programs may use data structures for both inputting information and producing the desired result. Data structures impart a physical organization on the data stored in computer memory and greatly facilitate data management. Databases include data structures and data.
The actual physical implementation of a database on a general purpose computer may take several forms, from complete individual records storing the substantive information with several key indexes for locating a particular record, to a plurality of tables interrelated by relational operations, to a matrix of cross-linked data records, to various combinations and hybrids of these general types. In particular physical devices, a database may be structured and arranged to accommodate the restrictions of the physical device but, when transferred to a general purpose computer, be able to be stored in a variety of formats. Thus, while certain types of information may be described as being stored in a “database” from a conceptual standpoint, generally such information may be electronically stored in a variety of structures with a variety of encoding techniques.
Although the following description details operations in terms of a graphic user interface using display objects, the present invention may be practiced with text based interfaces, or even with voice or visually activated interfaces.
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 data management. Before delving into the various embodiments of the system and method according to the invention, general healthcare data management system concepts will be described. A healthcare data management system receives medical data from a plurality of sources, including portable devices, and displays the data to facilitate diagnosis and treatment of patients. Data from portable devices is downloaded into the computing device before it may be managed by the system.
Turning now to the figures,
The ACCU-CHEK® 360° software may be installed in a variety of configurations, e.g., personal and professional. The configurations determine whether some options are available to users. The ACCU-CHEK® 360° databases and software programs may be installed in a computing device comprising a personal computer or may be installed on a server. The system may download data from medical devices and may merge data from other databases. For example, a user who had been using another system may choose to upgrade to an ACCU-CHEK® 360° system. The ability to merge data allows the user to use the old data. Methods for merging data are disclosed in the above-identified co-filed patent applications. The ACCU-CHEK® 360° system may also receive medical data from multiple patients. The ACCU-CHEK® 360° software may be installed to operate in one of many languages. In the professional installation, access to a plurality of patient result databases allows the ACCU-CHEK® 360° to display information comparing a particular patient's data to statistical data corresponding groups of patients.
System 100 comprises computing device 102, shown here in the form of a computer having display device 104, in this case a computer video screen or monitor having screen 108, and keyboard 106. While described and depicted herein with specific reference to a computer, the present invention may be utilized in conjunction with any computing device capable of operating healthcare data management software including without limitation a blood glucose meter, an infusion pump, or an integrated device including a glucose measurement engine or an infusion pump. Computing device 102 has mouse 110 connected to it by cable 112. While mouse 110 and keyboard 106 are shown, system 100 may comprise any input device. System 100 includes software (not shown) configured to receive data from input devices. Components of a computing device 102 also include, but are not limited to, a processing unit and system memory.
Computing device 102 may include a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computing device 102 and includes both volatile and non-volatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store computer-readable instructions, software, data structures, program modules and other data and which can be accessed by computing device 102. Computer-readable media may be accessed directly or through a network or the Internet.
Computing device 102 may operate in a network environment using logical connections to one or more remote computers. The remote computer may be a personal computer, a server, a network PC, and typically includes many or all of the elements described above relative to computing device 102. The logical connections include a local area network (LAN) and a wide area network (WAN), but also include other networks. Such network environments are commonplace in office, enterprise-wide computer networks, Intranets, and the Internet. In such computer networks, typically one or more computers operate as a “server,” a computer with large storage media such as hard disk drives and communication hardware to operate peripheral devices such as printers or modems. Other computers, termed “clients” or “workstations,” provide a user interface so that users of computer networks can access the network resources, such as shared data files, common peripheral devices, and inter-workstation communication. The computers have at least one processor for executing machine instructions, and memory for storing instructions and other information. Many combinations of processing circuitry and information storing equipment are possible.
System 100 comprises one or more software programs. System 100 may comprise software configured to download data, to merge data from other origin databases, and to enable users to manually add and modify data. System 100 may also comprise a database for storing, retrieving, organizing, and, generally, for managing data. Data may include general data and patient data. In healthcare data management, the term “patient” refers to a person whose medical information is stored in system 100. As used herein, patient data refers to data that can identify a patient including administrative data such as name, address, phone number, and medical data such as physiological parameter values including without limitation blood glucose values, A1c values, Albumin values, Albumin excretion values, body mass index values, blood pressure values, carbohydrate values, cholesterol values (total, HDL, LDL, ratio) creatinine 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. Patient data may be provided by the patient, a healthcare professional, a medical device, a caregiver, or anyone having relevant data pertaining to a patient. In one embodiment, the databases are relational databases and the database server is the MICROSOFT SQL Server Express 2005. Computer 100 may include other applications required for operation of the SQL Server.
System 100 is configured to provide medical data to, and receive data from, medical device 120. In
Medical devices are devices capable of recording medical data and transferring data to software. While the enhanced data transfer method may be performed with any portable device capable of recording data, the invention is described herein with reference to medical devices, and more particularly, with reference to diabetes management devices, e.g., meters and pumps. Medical devices may include monitors which record values of measurements relating to a patient's physiological condition and information such as the time and date when the measurement was recorded. Medical devices may also be devices configured to provide medications to patients such as, for example, insulin pumps. These devices, generally, record dosage amounts as well as the time and date when the medication was provided. Optionally, medical devices may have their own input devices and display devices. A medical device may also comprise a computing device integrated or coupled with a device for recording medical data including without limitation a computer, personal digital assistants (PDAs), phones, and BLACKBERRYs. Furthermore, system 100 may be integrated with medical device 120 thereby eliminating the necessity of generating and transmitting a modulated signal.
Medical device 120 is, generally, assigned to a patient and associated with that patient in system 100. Thus, when medical data from medical device 120 is transferred to system 100, the medical data from medical device 120 automatically populates database records relating to that patient. A user may associate medical device 120 to system 100 in various ways. In one embodiment, medical device 120 sends an unique device identifier code to the healthcare data management software. The software receives the device identifier code and associates the device with the user presently logged in and using the healthcare data management software. In another embodiment, the healthcare data management software prompts the user for confirmation before making the association. In another embodiment, the software prompts the user to select a patient and then associates the selected patient with the device.
Alternatively, medical device 120 is not associated with a patient in system 100. As disclosed below with reference to an express downloading embodiment, a download utility may receive medical device 120 data without transferring the data to a results database.
System 100 may be used by the patient, a healthcare professional, a caregiver, or anyone having relevant data pertaining to a patient. System 100 may be located in a patient's home, a healthcare facility, or any other convenient place. In an alternative embodiment, two systems may be connected and medical data may be transferred between them. For example, a first system may be located in a place accessible to the patient or a caregiver, and a second system may be located in a healthcare facility. In this embodiment, the first and second systems are configured to transfer medical data between them by any means known in the art such as, for example, via the Internet, cellular communications, or the physical transfer of a memory device such as a diskette, USB key, or compact disc. The first system, or patient system, may be configured to receive medical data from a medical device and the second system may be configured to also receive medical data from a medical device or, alternatively, to use medical data transferred from, passed-through, or accessible from, the first system. The second system, or HCP system, may be configured to receive medical data from a plurality of patient systems and medical devices. Furthermore, the HCP system may be configured to provide comments and other data to the patient system and to remotely control the patient system. In this manner, a physician using the HCP system may interact with the patient system to improve communications with the user of the patient system.
Systems 100, 100′ include one or more downloading utilities configured to transfer data from medical device 120. The download utility may be in the form of a computer program integrated with the healthcare data management software or may be used as an independent program, e.g., capable of independent installation and operation. In one exemplary embodiment, the download utility may be activated from the healthcare data management software after the healthcare data management software has been launched. To download data, a user activates either of download device object 302 or express download object 304. Each of objects 302, 304 are associated with a download utility. Download utilities may perform additional functions. The download utility associated with download device object 302 receives medical data from medical device 120, and performs the additional function of storing the data in a results database. The download utility associated with express download object 304 receives medical data from medical device 120, and performs the additional function of printing the data without requiring the user to access additional menu options. Methods for downloading data from a portable device are disclosed in the above-identified co-filed patent applications.
In another exemplary embodiment, the download utility may be activated without launching the healthcare data management software. A user may launch the download utility or the utility may launch automatically. The user may launch the download utility by activating a display object associated with the utility. For automatic downloading, the user may place medical device 120 such that it may be accessed by communication media 116. The automatic downloading utility may be configured to periodically send out access requests. Upon discovering a response to the request from medical device 120, the download utility may download data from medical device 120. A method for automatic detection of a portable device is disclosed in the above-identified co-filed patent applications.
Data may be stored in various formats depending on how medical device 120 is configured. As used herein, a datapoint means a point in time, or time stamp, when a portable device records data corresponding to a relevant activity, and a device record means all the data recorded by a portable device corresponding to a datapoint. The relevant activity may be the measurement of a physiological parameter, delivery of medication, or any other activity recorded by medical device 120. A device record may include without limitation a time stamp, datapoint value, and unit of measure. Some devices assign a sequence number to each record to signify the sequential order in which records are created, and include the sequence number in each record. The size of the sequence number is determined by the amount of data a portable device is projected to record during its life. The sequence number is particularly useful to identify records whose time stamps appear to be out of order. Time stamps may be out of order when a user resets the clock on the portable device, e.g., to adjust for a time zone change while traveling, or to adjust for daylight savings time changes. The clock reset may cause subsequent records to appear to have been created out of order.
In one embodiment of medical device 120, data is stored and retrieved in a last-in-first-out (LIFO) sequential order. Data may be stored in a stack or in a file or database. Storing and retrieving a device record from a stack may require multiple read/write instructions depending on the width of the stack and the amount of data in the record. A file may use characters to delimit data strings or may rely on a set string size to determine when device records begin and end. As used herein, a device record corresponds to a datapoint regardless of how the record is physically configured in medical device 120. For example, a record may be embodied as a single record in a table or as two records in different tables which are relationally linked. In a LIFO sequential order, the newest record is the first record which may be downloaded from the device. In other words, the newest record is the last record in and is downloaded before all other records are downloaded.
A download event is defined herein as the process of downloading data from medical device 120. The process begins when a download utility accesses medical device 120, and it ends when the utility stops downloading device records. During a download event, one or more device records are downloaded from medical device 120. Re-launching the download utility creates a new download event. In one embodiment, the user waits while the download utility receives data from medical device 120. In another embodiment, the user may continue to use the healthcare data management software while the download utility receives data from medical device 120 in the background.
Referring now to
Generally, a fingerprint may be any data string which may be used to store information corresponding to a record. A last record fingerprint is a fingerprint corresponding to the last record retrieved during a previous download event. A fingerprint may also correspond to a database record. Fingerprints may comprise untransformed data and transformed data, e.g., coded or encrypted. In one embodiment, the last record fingerprint comprises the device record in the form downloaded from medical device 120. In another embodiment, the last record fingerprint is the encrypted value of the last device record downloaded from medical device 120. In yet another embodiment, the last record fingerprint is the hash value of the last device record downloaded from medical device 120. Cryptographic functions, including a hash function, are transformations that take an input string and return a value corresponding to the string. The value is a concise representation of the longer string from which the value was computed. The value is a sort of “digital fingerprint” of its source. A hash value is a cryptographic function that takes a long string and returns a fixed length string. A hash value is also called a digest or checksum of the stream of data that represents the contents. SHA-1, MD5, and RIPEMD-160 are commonly used hashing algorithms. Cryptographic functions may encrypt usable information into a form that is unusable by anyone except an authorized user. An authorized user may decrypt encrypted messages using the cryptographic key used to encrypt them.
Referring to Step 504 of
Referring to Step 508 of
In one embodiment of the enhanced method according to the invention, a bypass is provided. A bypass allows the user to choose whether to prevent downloading previously downloaded records. In one embodiment of the bypass, if the user chooses to bypass, the downloading utility downloads all data from medical device 120 and proceeds to update the last record fingerprint. In another embodiment, the user may choose to bypass on a record-by-record basis. In another embodiment, the user may choose to bypass on a day-by-day basis. In yet another embodiment, the user may choose to bypass records obtained during a date range or a numbered sequence range.
Referring to Step 510 of
In another embodiment of the method according to the invention, an enhanced data transfer method is provided applicable to devices that store and retrieve data in first-in-first-out (FIFO) sequential order. The device may store data in a stack or in a file or database. In a FIFO sequential order, the newest record is the last record successfully downloaded from the device during a prior download event. Whether in a LIFO or FIFO system, the download process may be interrupted before a match is found. In a LIFO system, the interruption may create gaps in the sequence of records stored if the new records are fully processed, e.g., stored. The download utility may recover from the failed download by not fully processing the downloaded records in computing device 102 so as to avoid storing records created more recently than the records that were not downloaded due to the interruption. In a FIFO system according to the invention, on the other hand, records are not fully processed if a match was not found so there is no risk of storing more recent records and not storing earlier records. Consequently, once a match is found, any additionally downloaded record may be fully processed without creating gaps in the sequence of stored records. If there is an interruption, the download utility may successfully complete the download event by storing the fingerprint of the last downloaded record as the last record fingerprint.
The method begins when a download utility retrieves a last record fingerprint from a healthcare data management database. The program compares each downloaded record to the last record fingerprint. Until it finds a match, the program skips further processing steps on each downloaded record. Further processing includes, without limitation, data transformations, parsing, integrity checking, and storage. When it finds a match, the program skips further processing steps on the matched record and begins full processing of all subsequent records. Optionally, the program may provide a bypass to allow a user to fully process all records, or to fully process a selected range of previously fully processed records, in addition to unprocessed records.
In accordance with a further aspect of the present invention, a system and method for downloading data from a portable device is provided. The system comprises system 100′ and medical device 600.
In one aspect of the system according to the invention, medical device 600 is configured to adapt its operation according to the relationship between the device records and a system fingerprint. In one embodiment, the relationship is hierarchical based on the last device record downloaded to one or more healthcare data management systems and the hierarchy of the healthcare data management systems. The adaptation may comprise the prevention of deletion of data that has not yet been downloaded to a system high in the hierarchy. In another embodiment, the medical device may record a plurality of types of medical data and the relationship may be based on the type of medical record and the type of healthcare data management system. The adaptations may be responsive to the system fingerprint of a healthcare data management system.
In one embodiment, the adaptation comprises the prevention of deletion of data that has not yet been downloaded to system 100′. The adaptation may be performed according to the method described below with reference to
Referring now to
Before Step 702 may be performed, the download utility must access medical device 600 in any manner previously disclosed. The download utility downloads device records from medical device 600 until it reaches the last device record to download. The download utility may determine that the last device record to download was reached according to the method described with reference to
Referring to Step 704 of
Referring to Step 708 of
In another aspect of the system according to the invention, medical device 600 comprises a universal patient interface coupled to a device for performing a function including recording medical data or providing medicine. Different devices may be coupled to record different types of medical data and infuse different types of medicines. Depending on the type of device coupled to the interface, medical device 600 records different types of medical data. Medical device 600 may be configured to adapt its operation according to the relationship between the device records and different types of healthcare data management software based upon the different types of medical data recorded. According to one embodiment of the method for adapting its operation, medical device 600 may be configured to associate different system fingerprints with particular types of datapoint values corresponding to different types of devices coupled to the interface, and to only download device records having types of values corresponding to associated system fingerprints. The system fingerprint may be encoded with a code corresponding to the type of healthcare data management software to enable medical device 600 to select records. The system fingerprint may be uploaded to the medical device upon commencement of a download event.
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.
Number | Name | Date | Kind |
---|---|---|---|
4731726 | Allen, III | Mar 1988 | A |
5251126 | Kahn et al. | Oct 1993 | A |
5338157 | Blomquist | Aug 1994 | A |
5376070 | Purvis et al. | Dec 1994 | A |
5658250 | Blomquist et al. | Aug 1997 | A |
5665065 | Colman et al. | Sep 1997 | A |
5795327 | Wilson et al. | Aug 1998 | A |
5954641 | Kehr et al. | Sep 1999 | A |
6024699 | Surwit et al. | Feb 2000 | A |
6068615 | Brown et al. | May 2000 | A |
6102855 | Kehr et al. | Aug 2000 | A |
6110148 | Brown et al. | Aug 2000 | A |
6113578 | Brown | Sep 2000 | A |
6241704 | Peterson et al. | Jun 2001 | B1 |
6314405 | Richardson | Nov 2001 | B1 |
6322502 | Schoenberg et al. | Nov 2001 | B1 |
6368272 | Porumbescu | Apr 2002 | B1 |
6427088 | Bowman, IV et al. | Jul 2002 | B1 |
6470329 | Livschitz | Oct 2002 | B1 |
6544212 | Galley et al. | Apr 2003 | B2 |
6551276 | Mann et al. | Apr 2003 | B1 |
6558320 | Causey, III et al. | May 2003 | B1 |
6562001 | Lebel et al. | May 2003 | B2 |
6564105 | Starkweather et al. | May 2003 | B2 |
6571128 | Lebel et al. | May 2003 | B2 |
6577899 | Lebel et al. | Jun 2003 | B2 |
6585644 | Lebel et al. | Jul 2003 | B2 |
6605038 | Teller et al. | Aug 2003 | B1 |
6635014 | Starkweather et al. | Oct 2003 | B2 |
6648821 | Lebel et al. | Nov 2003 | B2 |
6659948 | Lebel et al. | Dec 2003 | B2 |
6668196 | Villegas et al. | Dec 2003 | B1 |
6671702 | Kruglikov et al. | Dec 2003 | B2 |
6687546 | Lebel et al. | Feb 2004 | B2 |
6694191 | Starkweather et al. | Feb 2004 | B2 |
6714724 | Cook | Mar 2004 | B1 |
6733446 | Lebel et al. | May 2004 | B2 |
6740075 | Lebel et al. | May 2004 | B2 |
6752787 | Causey, III et al. | Jun 2004 | B1 |
6758810 | Lebel et al. | Jul 2004 | B2 |
6781522 | Sleva et al. | Aug 2004 | B2 |
6804656 | Rosenfeld et al. | Oct 2004 | B1 |
6809653 | Mann et al. | Oct 2004 | B1 |
6810290 | Lebel et al. | Oct 2004 | B2 |
6811533 | Lebel et al. | Nov 2004 | B2 |
6811534 | Bowman, IV et al. | Nov 2004 | B2 |
6813519 | Lebel et al. | Nov 2004 | B2 |
6852104 | Blomquist | Feb 2005 | B2 |
6873268 | Lebel et al. | Mar 2005 | B2 |
6958705 | Lebel et al. | Oct 2005 | B2 |
7020508 | Stivoric et al. | Mar 2006 | B2 |
7024236 | Ford et al. | Apr 2006 | B2 |
7029455 | Flaherty | Apr 2006 | B2 |
7039703 | Clancy et al. | May 2006 | B1 |
7041468 | Drucker et al. | May 2006 | B2 |
7063665 | Hasegawa et al. | Jun 2006 | B2 |
7072356 | Clancy et al. | Jul 2006 | B1 |
7082334 | Boute et al. | Jul 2006 | B2 |
7120488 | Nova et al. | Oct 2006 | B2 |
7165062 | O'Rourke | Jan 2007 | B2 |
7171613 | Alexander et al. | Jan 2007 | B1 |
7179226 | Crothall et al. | Feb 2007 | B2 |
7181350 | Oberding et al. | Feb 2007 | B2 |
7436322 | Crank | Oct 2008 | B2 |
20020016568 | Lebel et al. | Feb 2002 | A1 |
20020029776 | Blomquist | Mar 2002 | A1 |
20020040208 | Flaherty et al. | Apr 2002 | A1 |
20020143290 | Bui et al. | Oct 2002 | A1 |
20020193679 | Malave et al. | Dec 2002 | A1 |
20030011646 | Levine et al. | Jan 2003 | A1 |
20030060765 | Campbell et al. | Mar 2003 | A1 |
20030065308 | Lebel et al. | Apr 2003 | A1 |
20030065536 | Hansen et al. | Apr 2003 | A1 |
20030130771 | Crank | Jul 2003 | A1 |
20030163088 | Blomquist | Aug 2003 | A1 |
20030163789 | Blomquist | Aug 2003 | A1 |
20030193409 | Crank | Oct 2003 | A1 |
20030195904 | Chestnut et al. | Oct 2003 | A1 |
20040073464 | Huang | Apr 2004 | A1 |
20040119742 | Silbey et al. | Jun 2004 | A1 |
20040172284 | Sullivan et al. | Sep 2004 | A1 |
20040235446 | Flaherty et al. | Nov 2004 | A1 |
20040254434 | Goodnow et al. | Dec 2004 | A1 |
20040260233 | Garibotto et al. | Dec 2004 | A1 |
20050004947 | Emlet et al. | Jan 2005 | A1 |
20050022274 | Campbell et al. | Jan 2005 | A1 |
20050137653 | Friedman et al. | Jun 2005 | A1 |
20050192844 | Esler et al. | Sep 2005 | A1 |
20060167367 | Stanczak et al. | Jul 2006 | A1 |
20060245530 | Pradhan et al. | Nov 2006 | A1 |
20060248398 | Neel et al. | Nov 2006 | A1 |
20060279431 | Bakarania et al. | Dec 2006 | A1 |
20070033074 | Nitzan et al. | Feb 2007 | A1 |
20070048691 | Brown | Mar 2007 | A1 |
20070112882 | Tysowski et al. | May 2007 | A1 |
20070179352 | Randlov et al. | Aug 2007 | A1 |
20070185869 | Kirnak | Aug 2007 | A1 |
20070219432 | Thompson | Sep 2007 | A1 |
20070248055 | Jain et al. | Oct 2007 | A1 |
20070276197 | Harmon | Nov 2007 | A1 |
20080027679 | Shklarski | Jan 2008 | A1 |
20080266054 | Crank | Oct 2008 | A1 |
Number | Date | Country |
---|---|---|
0 699 046 | Sep 1996 | EP |
0 970 655 | Jan 2000 | EP |
0 649 316 | Dec 2000 | EP |
1 194 864 | Apr 2002 | EP |
1 502 614 | Feb 2005 | EP |
1 722 310 | Apr 2005 | EP |
WO9728736 | Feb 1997 | WO |
WO9935856 | Dec 1998 | WO |
WO0018449 | Feb 2000 | WO |
WO0072181 | Nov 2000 | WO |
WO02078512 | Oct 2002 | WO |
WO02000111 | Nov 2002 | WO |
WO03015838 | Feb 2003 | WO |
WO2004090661 | Oct 2004 | WO |
WO2005011249 | Feb 2005 | WO |
WO2005037095 | Apr 2005 | WO |
WO2005096206 | Oct 2005 | WO |
WO2005114534 | Dec 2005 | WO |
WO2005114535 | Dec 2005 | WO |
WO2006050485 | Feb 2006 | WO |
WO2006108858 | Oct 2006 | WO |
WO2006118763 | Nov 2006 | WO |
WO2007036015 | Apr 2007 | WO |
WO2007051139 | May 2007 | WO |
WO2007093482 | Aug 2007 | WO |
WO2008147567 | Dec 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20090150416 A1 | Jun 2009 | US |