CA2688123C - Architecture for health monitoring systems - Google Patents
Architecture for health monitoring systems Download PDFInfo
- Publication number
- CA2688123C CA2688123C CA2688123A CA2688123A CA2688123C CA 2688123 C CA2688123 C CA 2688123C CA 2688123 A CA2688123 A CA 2688123A CA 2688123 A CA2688123 A CA 2688123A CA 2688123 C CA2688123 C CA 2688123C
- Authority
- CA
- Canada
- Prior art keywords
- program components
- modules
- software
- daughter circuit
- circuit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 230000036541 health Effects 0.000 title abstract description 17
- 238000012544 monitoring process Methods 0.000 title abstract description 17
- 238000004891 communication Methods 0.000 claims abstract description 64
- 230000006870 function Effects 0.000 claims abstract description 28
- 238000007726 management method Methods 0.000 claims description 21
- 238000010200 validation analysis Methods 0.000 claims description 10
- 230000001960 triggered effect Effects 0.000 claims description 3
- 238000013502 data validation Methods 0.000 claims 3
- 230000002708 enhancing effect Effects 0.000 claims 1
- 238000005516 engineering process Methods 0.000 abstract description 29
- 238000013459 approach Methods 0.000 abstract description 15
- 229940079593 drug Drugs 0.000 abstract description 7
- 239000003814 drug Substances 0.000 abstract description 7
- 238000012360 testing method Methods 0.000 description 70
- 239000008103 glucose Substances 0.000 description 33
- 239000000047 product Substances 0.000 description 33
- 238000000034 method Methods 0.000 description 28
- 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 20
- 239000012491 analyte Substances 0.000 description 17
- 210000004369 blood Anatomy 0.000 description 17
- 239000008280 blood Substances 0.000 description 17
- 230000008569 process Effects 0.000 description 17
- 206010012601 diabetes mellitus Diseases 0.000 description 16
- 238000012545 processing Methods 0.000 description 13
- 238000012384 transportation and delivery Methods 0.000 description 11
- 210000001124 body fluid Anatomy 0.000 description 10
- 238000011161 development Methods 0.000 description 9
- 238000005259 measurement Methods 0.000 description 9
- 239000010839 body fluid Substances 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 7
- 238000006243 chemical reaction Methods 0.000 description 6
- 239000003153 chemical reaction reagent Substances 0.000 description 6
- 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 6
- 108090000790 Enzymes Proteins 0.000 description 5
- 102000004190 Enzymes Human genes 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 229940088598 enzyme Drugs 0.000 description 5
- 239000012530 fluid Substances 0.000 description 5
- 238000012356 Product development Methods 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 238000000840 electrochemical analysis Methods 0.000 description 4
- 239000012467 final product Substances 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 230000033001 locomotion Effects 0.000 description 4
- 102000004877 Insulin Human genes 0.000 description 3
- 108090001061 Insulin Proteins 0.000 description 3
- 230000006399 behavior Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 210000004027 cell Anatomy 0.000 description 3
- 235000005911 diet Nutrition 0.000 description 3
- 230000037213 diet Effects 0.000 description 3
- 238000003487 electrochemical reaction Methods 0.000 description 3
- 229940125396 insulin Drugs 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000000717 retained effect Effects 0.000 description 3
- BPYKTIZUTYGOLE-IFADSCNNSA-N Bilirubin Chemical compound N1C(=O)C(C)=C(C=C)\C1=C\C1=C(C)C(CCC(O)=O)=C(CC2=C(C(C)=C(\C=C/3C(=C(C=C)C(=O)N\3)C)N2)CCC(O)=O)N1 BPYKTIZUTYGOLE-IFADSCNNSA-N 0.000 description 2
- 238000004422 calculation algorithm Methods 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
- 238000013523 data management Methods 0.000 description 2
- 210000003722 extracellular fluid Anatomy 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000012956 testing procedure Methods 0.000 description 2
- 210000003813 thumb Anatomy 0.000 description 2
- 208000006545 Chronic Obstructive Pulmonary Disease Diseases 0.000 description 1
- 229930091371 Fructose Natural products 0.000 description 1
- RFSUNEUAIZKAJO-ARQDHWQXSA-N Fructose Chemical compound OC[C@H]1O[C@](O)(CO)[C@@H](O)[C@@H]1O RFSUNEUAIZKAJO-ARQDHWQXSA-N 0.000 description 1
- 239000005715 Fructose Substances 0.000 description 1
- 108010050375 Glucose 1-Dehydrogenase Proteins 0.000 description 1
- 108010015776 Glucose oxidase Proteins 0.000 description 1
- 239000004366 Glucose oxidase Substances 0.000 description 1
- 102000007513 Hemoglobin A Human genes 0.000 description 1
- 108010085682 Hemoglobin A Proteins 0.000 description 1
- JVTAAEKCZFNVCJ-UHFFFAOYSA-M Lactate Chemical compound CC(O)C([O-])=O JVTAAEKCZFNVCJ-UHFFFAOYSA-M 0.000 description 1
- 238000002835 absorbance Methods 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- WQZGKKKJIJFFOK-VFUOTHLCSA-N beta-D-glucose Chemical compound OC[C@H]1O[C@@H](O)[C@H](O)[C@@H](O)[C@@H]1O WQZGKKKJIJFFOK-VFUOTHLCSA-N 0.000 description 1
- 230000036772 blood pressure Effects 0.000 description 1
- 238000009530 blood pressure measurement Methods 0.000 description 1
- 238000009529 body temperature measurement Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000013626 chemical specie Substances 0.000 description 1
- 235000012000 cholesterol Nutrition 0.000 description 1
- 239000013078 crystal Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000002405 diagnostic procedure Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- YAGKRVSRTSUGEY-UHFFFAOYSA-N ferricyanide Chemical class [Fe+3].N#[C-].N#[C-].N#[C-].N#[C-].N#[C-].N#[C-] YAGKRVSRTSUGEY-UHFFFAOYSA-N 0.000 description 1
- 210000003811 finger Anatomy 0.000 description 1
- 238000001506 fluorescence spectroscopy Methods 0.000 description 1
- -1 for example Proteins 0.000 description 1
- ZZUFCTLCJUWOSV-UHFFFAOYSA-N furosemide Chemical compound C1=C(Cl)C(S(=O)(=O)N)=CC(C(O)=O)=C1NCC1=CC=CO1 ZZUFCTLCJUWOSV-UHFFFAOYSA-N 0.000 description 1
- 229940116332 glucose oxidase Drugs 0.000 description 1
- 235000019420 glucose oxidase Nutrition 0.000 description 1
- 238000009532 heart rate measurement Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 229940063711 lasix Drugs 0.000 description 1
- 230000000670 limiting effect Effects 0.000 description 1
- 150000002632 lipids Chemical class 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 235000012054 meals Nutrition 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 210000000496 pancreas Anatomy 0.000 description 1
- 230000037081 physical activity Effects 0.000 description 1
- 230000004962 physiological condition Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 210000002381 plasma Anatomy 0.000 description 1
- 238000012019 product validation Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000002829 reductive effect Effects 0.000 description 1
- 230000029058 respiratory gaseous exchange Effects 0.000 description 1
- 238000013215 result calculation Methods 0.000 description 1
- 238000012419 revalidation Methods 0.000 description 1
- 210000002966 serum Anatomy 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 238000010561 standard procedure Methods 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 238000002235 transmission spectroscopy Methods 0.000 description 1
- 150000003626 triacylglycerols Chemical class 0.000 description 1
- 210000002700 urine Anatomy 0.000 description 1
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/145—Measuring characteristics of blood in vivo, e.g. gas concentration, pH value; Measuring characteristics of body fluids or tissues, e.g. interstitial fluid, cerebral tissue
- A61B5/14532—Measuring characteristics of blood in vivo, e.g. gas concentration, pH value; Measuring characteristics of body fluids or tissues, e.g. interstitial fluid, cerebral tissue for measuring glucose, e.g. by tissue impedance measurement
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/16—Constructional details or arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/266—Arrangements to supply power to external peripherals either directly from the computer or under computer control, e.g. supply of power through the communication port, computer controlled power-strips
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
- G06F13/385—Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4063—Device-to-bus coupling
- G06F13/4068—Electrical coupling
- G06F13/4081—Live connection to bus, e.g. hot-plugging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/22—Social work or social welfare, e.g. community support activities or counselling services
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H20/17—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered via infusion or injection
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/40—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/63—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for local operation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/16—Constructional details or arrangements
- G06F1/1601—Constructional details related to the housing of computer displays, e.g. of CRT monitors, of flat displays
- G06F1/1605—Multimedia displays, e.g. with integrated or attached speakers, cameras, microphones
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- Business, Economics & Management (AREA)
- Biomedical Technology (AREA)
- Public Health (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Life Sciences & Earth Sciences (AREA)
- Software Systems (AREA)
- General Business, Economics & Management (AREA)
- Epidemiology (AREA)
- Computer Hardware Design (AREA)
- Tourism & Hospitality (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Surgery (AREA)
- Emergency Medicine (AREA)
- Heart & Thoracic Surgery (AREA)
- Animal Behavior & Ethology (AREA)
- Veterinary Medicine (AREA)
- Pathology (AREA)
- Biophysics (AREA)
- Optics & Photonics (AREA)
- Molecular Biology (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Child & Adolescent Psychology (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Chemical & Material Sciences (AREA)
- Medicinal Chemistry (AREA)
- Multimedia (AREA)
Abstract
An architecture allows individual system components to be developed and tested individually, i.e., as distinct modules, and to be subsequently combined through standardized electrical and communication interfaces. Any combination of these modules can be implemented to form different products that provide any number of functions, such as an integrated system for monitoring a health condition and/or delivering a medication. The architecture also provides an approach for dynamically updating the product and offering its users the latest generation of technology even after the users have already purchased the product. In particular, the embodiments employ the communication interfaces to also provide connection to a remote network that can update or upgrade the product's software when the product is out in the field.
Description
ARCHITECTURE FOR HEALTH MONITORING SYSTEMS
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Application No. 60/932,286, filed May 30, 2007, U.S. Provisional Application No. 61/012,721, filed December 10, 2007, and U.S. Provisional No. 61/012,718, filed December 10, 2007 FIELD OF THE INVENTION
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Application No. 60/932,286, filed May 30, 2007, U.S. Provisional Application No. 61/012,721, filed December 10, 2007, and U.S. Provisional No. 61/012,718, filed December 10, 2007 FIELD OF THE INVENTION
[0002] The present invention relates generally to a method and system for developing healthcare devices. More specifically, the method and system of the present invention provides an architecture that allows any combination of modules with different functions to be easily assembled to form an integrated system for monitoring a health condition and/or delivering a medication. In addition, the method and system provides an architecture that allows the modules to be updated dynamically during operation in the field.
BACKGROUND OF THE INVENTION
BACKGROUND OF THE INVENTION
[0003] The quantitative determination of analytes in body fluids is of great importance in the diagnoses and maintenance of certain physiological conditions. For example, individuals with diabetes frequently check the glucose level in their bodily fluids. The results of such tests .can be used to regulate the glucose intake in their diets and/or to determine whether insulin or other medication needs to be administered.
[0004] Diagnostic systems, such as blood-glucose systems, may employ a meter or instrument to calculate the glucose value in a blood sample from an individual. Such instruments operate by measuring an output, such as current or color, from a reaction with the glucose in the sample. The test results typically are displayed and stored by the meter. Basic systems allow the user to access the test results directly from the meter via a keypad or other interactive component.
[0005] Other diagnostic systems, however, provide more advanced functionality to allow a user to process and manage test results. For example, some systems allow a user to load test results from a blood-glucose meter onto a processing device, such as a conventional desktop personal computer (PC), and to process and display the results with a data-management application. However, using the processing power of PC technology to organize results from a blood-glucose meter is just one example of how diagnostic systems provide more functionality by incorporating different technologies into a diagnostic process.
[0006] Although integrating different technologies and functions may yield highly sophisticated and extremely useful diagnostic systems, the introduction of such systems into the marketplace is slowed by current approaches to product design and development in the industry. For example, current approaches to the design of multi-function products employ complicated system architectures that interconnect the variety of functional elements via distinct and non-standard techniques. Accordingly, a functional element must be developed with the specific final product and the other functional elements in mind. In other words, the complex architecture results in dependencies between functional elements, and thus does not allow each element to be developed independently and/or in parallel. As such, the development process requires more time as more components are added and complexity is increased.
[0007] In addition, although the final integrated product may provide the features and advantages of a variety of technologies, the rapid pace of change in these technologies may outdate the final product before the final product is introduced to the market, particularly because product development takes such a long time. In other words, current approaches to product development make it difficult to ensure that the users of the product have the latest generation of technology. Where the cost of integrated products may be relatively high due to the greater amount of functionality, consumers may find less justification in purchasing such products when their technology may become quickly outdated.
[0008] In view of the foregoing, there is a need for design and development approaches that simplify the process of combining different technological components into a single product while meeting the high quality standards for medical devices. In particular, there is a need for an approach that simplifies interfaces between components and therefore permits different combinations of components to be easily and reliably integrated regardless of the number of components. Moreover, there is a need for an approach that allows the final product to be dynamically and continuously updated to offer its users the most current technology.
SUMMARY OF THE INVENTION
SUMMARY OF THE INVENTION
[0009] The embodiments described herein address the needs identified above by providing an architecture that allows individual system components to be developed and tested individually, i.e., as distinct modules, and to be subsequently combined through standardized electrical and communication interfaces. Any combination of these modules can be implemented to form different products that provide any number of functions, such as an integrated system for monitoring a health condition and/or delivering a medication.
100101 Although the architecture makes it more feasible to shorten a product's development cycle and to introduce the product to consumers more quickly, the embodiments also provide an approach for dynamically updating the product and offering its users the latest generation of technology even after the users have already purchased the product. In particular, the embodiments employ the communication interfaces to also provide connection to a remote network that can update or upgrade the product's software when the product is out in the field. This process is known as a field upgrade.
[0011] Because the interfaces and communication protocols are designed to facilitate connection between different components and the rest of the system, the embodiments also provide functionality that ensures that unauthorized individuals or devices cannot connect with the system and compromise the security of data, such as personal medical information, which may be collected, stored, and handled by the system. With this underlying security functionality, particular technologies, such as wireless communication, can be implemented as components of medical diagnostic systems without concern over unauthorized access to personal information.
[0012] In addition, due to the important medical functions associated with the assembled product, embodiments employ validation procedures to ensure that any data transferred to the product, for example, during field upgrade, does not corrupt the data or the software stored by the product and that the product continues to operate as expected.
[0013] Still other aspects, features, and advantages of the present invention are readily apparent from the following detailed description, by illustrating a number of exemplary embodiments and implementations, including the best mode contemplated for carrying out the present invention. Accordingly, the drawings and descriptions are to be regarded as illustrative in nature, and not as restrictive.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG. IA illustrates a diagram of an architecture according to aspects of the present invention.
[0015] FIG. 1B illustrates a diagram of another architecture according to aspects of the present invention.
[0016] FIG. 2A illustrates an example security measure that can be employed by an architecture according to aspects of the present invention.
[0017] FIG. 2B illustrates another example security measure that can be employed by an architecture according to aspects of the present invention.
[0018] FIG. 2C illustrates a further example security measure that can be employed by an architecture according to aspects of the present invention.
[0019] FIG. 2D illustrates yet another example security measure that can be employed by an architecture according to aspects of the present invention.
[0020] FIG. 3 illustrates an example diabetes-management system employing an architecture according to aspects of the present invention.
[0021] FIG. 4 illustrates another diagram of an architecture according to aspects of the present invention.
[0022] FIG. 5 illustrates an example of a diagnostic system employing an architecture according to aspects of the present invention.
[0023] FIG. 6 illustrates another example of a diagnostic system employing an architecture according to aspecis of the present invention.
[0024] FIG. 7 illustrates yet another example of a diagnostic system employing an architecture according to aspects of the present invention.
[0025] FIG. 8 illustrates a field-upgradeable architecture according to aspects of the present invention.
[0026] FIG. 9 illustrates an example for employing a field upgrade according to aspects of the present invention.
DESCRIPTION OF ILLUSTRATED EMBODIMENTS
[0027] The embodiments described herein provide a system architecture that allows individual system components, or modules, to be developed and validated independently (as distinct modules) and subsequently combined through standardized electrical and communication interfaces. The standardized interfaces facilitate the combination and configuration of these modules to form different products that provide any number of functions. While the architecture can be used to form a fixed combination of components, the approach also permits reconfigurable or expandable combinations where different components may be easily removed or added to the system. In addition, as described further below, the architecture provides an approach for dynamically updating the modules after they have been integrated into the product.
[0028] FIG. 1A illustrates a conceptual diagram of a modular architecture according to aspects of the present invention. As shown in FIG. 1A, a modular architecture system 1 includes central engine 10 that is connected to a plurality of modules 30A, 30B, 30C, and 30D, each of which provides a functionality for a health monitoring and delivery system.
The central engine 10 enables the modules 30A, 30B, 30C, and 30D to work as an effective system. For example, the central engine 10 allows information to be communicated between the modules 30A, 30B, 30C, and 30D. For example, module 30D may be a computing device with software that processes data received from the other modules 30A, 30B, and 30C via the central engine 10. As FIG. 1A further illustrates, interface elements 22A, 22B, 22C, and 22D
of the central engine 10 connect with respective interface elements 24A, 24B, 24C, and 24D
to establish communications between the central engine 10 and the modules 30A, 30B, 30C, and 30D. The interfaces may provide wired, i.e. physical, and/or wireless communications.
Advantageously, the centralized organization of the interface architecture facilitates the integration of modules 30A, 30B, 30C, and 30D, which can be developed and tested separately from each other. Moreover, although the interface elements 22A, 22B, 22C, and 22D of the central engine 10 do not have to follow the same communications protocol, the interface elements 22A, 22B, 22C, and 22D can employ the most widely-used standard protocols so that the central engine 10 is more likely to be compatible with a given module.
[0029] Although the modules 30A, 30B, 30C, and 30D of FIG. 1A may all communicate information with each other, it is contemplated that a module connected to the central engine does not have to communicate with all of the other modules. Indeed, a module may be communicatively isolated from any, including all, of the other modules. For example, the nature of data and/or software on a particular module may be highly sensitive, so the module may be isolated from the other modules to enhance the security and/or integrity of the data.
[0030] In one embodiment, the central engine 10 is implemented on a mother board, while each module is separately implemented on a daughter board. The daughter boards are standardized so that they may connect to a single mother board to be integrated with the system. In other words, specific interfaces with boards corresponding to other modules do not have to be developed each time a new module is implemented. Due to this standardized approach, using commercial off-the-shelf (COTS) hardware for the mother and daughter boards becomes more feasible. Advantageously, using COTS hardware requires less development time than an application-specific integrated circuit (ASIC) approach.
[0031] In some embodiments, the mother board and the daughter boards may physically reside on separate circuit boards. In other embodiments, the mother board and the daughter boards may all be physically integrated onto the same circuit board. In further embodiments, the mother board and a combination of daughter boards may be physically integrated onto the same circuit board, while other daughter boards reside on separate circuit boards. Moreover, in some embodiments, the mother board and the daughter boards, whether on the same circuit boards or not, may all be disposed in the same housing, or casing. Meanwhile, in other embodiments, some or all of the daughter boards may be disposed in one or more housings separate from the mother board's housing. In general, the components of embodiments may be subject to varying degrees of physical integration regarding assembly on different circuit boards or within different housings, etc. To accommodate this variation in physical configuration, more than one interface type may be required to connect the daughter boards to the mother board, but as discussed previously, the interfaces between the central engine and the modules do not have to follow the same communications protocol. The interface elements associated with the mother board can employ the most widely-used standard protocols so that the central engine is more likely to be compatible with a given module.
[0032] The centralized architecture using standardized interfaces facilitates the development of compatible modules. When adding functionality to the system, integration with the architecture is easily achieved by employing a compatible interface element.
Moreover, the new module can be developed independently of the other modules, because only a single interface with the central engine 10 is required. In other words, even if the new module must communicate with other modules in the system, the new module does not have to be designed for a direct connection with the other modules, so the communications configuration of the other modules is not a significant design consideration for the new module. Accordingly, the ability to independently develop additional modules that easily connect with the central engine 10 enables systems employing this architecture to be flexible and reconfigurable. For example, such a system can be expanded with new modules or upgraded with new versions of existing modules.
[0033] Although FIG. IA illustrates an embodiment with the single central engine 10 connected to modules 30A, 30B, 30C, and 30D, the central engine 10 in some embodiments may also connect to a secondary central engine 40 as illustrated in FIG. 1B.
As shown in FIG. 1B, the central engine 10 is connected to modules 30A, 30B, and 30C via corresponding interface elements 22A/24A, 22B/24B, and 22C/24C. Meanwhile, the central engine 40 is connected to modules 60A, 60B, and 60C via corresponding interface elements 52A/54A, 52B/54B, and 52C/54C. As with the modules 30A, 30B, and 30C, the modules 60A, 60B, and 60C may be developed independently of the other modules according to a modular architecture that only requires a single interface with the central engine 40.
As further illustrated in FIG. 1B, the central engine 10 may be connected to the central engine 40 via interface elements 22D and 52D. Like the other interface elements, the interface elements 22D and 52D may provide wired, i.e. physical, or wireless communications. In some embodiments, the central engine 10 assumes a host function for the central engine 40. For example, if the central engine 10 connects to the central engine 40 according to universal serial bus (USB) communication protocol, standard USB requires a host-slave relationship between the two systems.
[0034] In the embodiment of FIG. 1B, the central engine 10 may access the functionalities provided by the modules 60A, 60B, and 60C, and conversely, the central engine 40 may access the functionalities provided by the modules 30A, 30B, and 30C. Even though the resulting combination may function like a single central engine connected to all six modules 30A, 30B, 30C, 60A, 60B, and 60C, the central engines 10 and 40 may be developed separately. As such, the development of a set of modules can be advantageously organized into separate subsets. For example, medical diagnostic systems may include critical medical devices, such as a blood-glucose meter, as well as other types of devices, such as a heart rate monitor. The critical medical devices may require very rigorous product validation during development and may be subject to government regulations.
Meanwhile, the other types of devices may not require the same type or same level of validation. As such, modules involving critical medical devices may have very different timelines and guidelines for product development compared to the other types of health care devices. Thus, in this case, it may be advantageous to organize the modules into two product development groups. In addition, every time a product involving critical medical devices is redeveloped or updated to include new features, government regulations may require revalidation of the product even if the new features may be relatively minor. For example, if a heart rate monitor is added to a central engine that is already connected to a blood-glucose meter, the entire system may have to be revalidated at great cost and effort, even though the new modules is a less critical health care device. However, the central engine connected to the blood-glucose meter can remain unchanged if the central engine already has the capability to connect to a secondary central engine that in turn is connected to the heart rate monitor. In other words, deploying new modules involving other health care devices and other features through the secondary central engine provides a way to expand the overall product without changing the architecture associated with the primary central engine.
Moreover, any validation of the architecture associated with the secondary central engine may be conducted without affecting the architecture associated with the primary central engine.
[0035] Although an advantage of the architectures described herein is the ease by which new modules can interface with the system and establish communications and data exchange, issues relating to the security of personal medical data have discouraged using highly compatible communication technologies with medical devices, such as personal testing devices that measure and store health data. To address these issues, embodiments according to aspects of the present invention provide functionality that helps to ensure that unauthorized individuals or devices cannot connect with the system and compromise the security of any personal medical information. The central engine 10 may be responsible for providing security measures. Alternatively or additionally, a component or module with special security functions may be employed to promote system security. With such security functionality, particular technologies, such as wireless communication, can be implemented as components of medical diagnostic systems without heightened concern over unauthorized access to personal information.
[0036] FIGS. 2A-D illustrate examples of security techniques that may be employed by an architecture according to aspects of the present invention. As shown in FIG. 2A, the central engine 10 may prompt the user for a user ID and password, personal identification number (PIN), or other authentication information, when a module 30 attempts to interface with the central engine 10 or to access data through the system. The module 30 is only allowed connection or data access if the response to the security prompt corresponds with authentication information stored at the system. For example, the module 30 may be a PC
executing a data-management program that uploads test data from a blood-glucose meter connected to the central engine 10. When the program attempts to communicate through an interface connection or tries to access data, the user must submit a user ID
and password.
The authentication information may be entered through a user interface, e.g. a keypad or keyboard, on the PC or the central engine 10. If the module 30 is used frequently to access data through the central engine 10, the user may find it inconvenient to enter authentication information repeatedly. Thus, some embodiments may allow a user to set a time period (from zero to infinity) between authentications from the particular module 30.
The central engine 10 records a unique identifier, e.g. device ID, for module 30 to keep track of the time period. For instance, a security prompt may be required if the specified time, e.g. one day, has passed since the last authentication. Alternatively, the user may stop all further security prompts from occurring after the first authentication. In this alternative case, the first authentication acts as a registration with the central engine 10 to permit all future access from the module 30.
[0037] As shown in FIG. 2B, a unique identifier, e.g. device ID, for module 30 may be registered with the central engine 10. This unique identifier may be entered by the user or recorded when the authentication process shown in FIG. 2A is completed for the first time.
Alternatively, registration of the module 30 may be achieved through an initial, e.g. factory, set-up process. In this alternative case, registration of additional modules may be prohibited after the initial set-up, thereby fixing the number of modules in the system.
When the module 30 subsequently attempts to connect or access data, the central engine 10 automatically recognizes the module 30 and permits access.
[0038] In the embodiments of FIGS. 2A and 2B, the module 30 is authenticated or registered in a one-way process. In other words, the central engine 10 is not required to be authenticated or registered with the module 30. In contrast, as shown in FIG.
2C, both the central engine 10 and the module 30 are required to be registered with each other. Matching of unique identifiers for the pair is required before any communication takes place between the central engine 10 and the module 30. This pair matching is particularly applicable to wireless communication between two devices. The process prevents intentional unauthorized access, and also prevents interference between two different systems. For example, if a user is in a setting, such as a hospital or clinic, where others are using similar wireless analyte-testing devices, such as blood-glucose meters, pair matching prevents another person's blood-glucose meter from accidentally communicating with the user's diagnostic system and providing the wrong data.
[0039] Data security may also be enhanced by using encrypted data during communications, as shown in FIG. 2D. This is also particularly applicable to wireless communications, so that any intercepted data will be unreadable. The data encryption may be achieved by using private encryption keys.
[0040] Data security may be further enhanced by ensuring that all data is stored by the central engine 10 within memory in the architecture and is not transferred to any connected modules. Thus, a user may, for example, use a public computer to interface with the system and no data will be transferred to the public computer for others to access.
[0041] FIG. 3 provides a non-limiting example of a diabetes-management system 100 that can be formed from the architecture approach described herein. The diabetes-management system 100 is advantageous to those individuals who are actively involved in monitoring and recording measurements of their blood glucose concentrations and/or other analytes of interest.
[0042] As shown in FIG. 3, the diabetes-management system 100 includes a blood-glucose meter (BGM) 310, a continuous glucose monitoring (CGM) module 320, an insulin-delivery device 330, and a computing device 370, which may include diabetes data management software 375. The modules 310, 320, 330, and 370 are combined, as described further below, using the architecture approaches described herein to provide health monitoring and delivery functions for the diabetes-management system 100. In particular, the BGM 310 provides point-in-time measurements of blood-glucose concentrations in blood samples; the CGM module 320 provides continuous measurements of blood-glucose concentration; and the insulin-delivery device 330 delivers insulin to the user.
[0043] In addition, the computing device 370 executes the software 375 to receive data from the modules 310, 320, and 330 and provides advanced data processing and management capabilities. The computing device 370 may be selected from a variety of processing devices, such as desktop or laptop personal computers (PCs), handheld or pocket personal computers (HPCs), compatible personal digital assistants (PDAs), and smart cellular phones.
The processing devices may employ a variety of operating systems and configurations. For example, if the computing device 370 is a desktop or laptop personal computer, the operating system may be a version of Microsoft Windows . Alternatively, if the computing device 370 is a PDA, the operating system may correspond with those of PALM
handhelds from Palm, Inc., or Blackberry devices from Research in Motion Limited. In general, computing device 370 includes a processor that is capable of receiving and executing any number of programmed instructions.
[0044] The data-management software 375 on the computing device 370 may be a collection of programs or computer code that receives and processes data measured by the modules 310 and 320, for example. The software 375 processes and/or displays this input in a manner that is desired by the user. This information may be used by, for example, a user, home care provider (HCP), and/or a physician. The measured data from the modules 310 and 320 may include, for example, the concentration of glucose and/or other analytes in a person's blood or other bodily fluid. Advantageously, the software 375 can provide the advanced displays and data processing that may be required by a user who tests multiple times a day (e.g., about six to about ten times a day). For example, the software 375 may include a product similar to WINGLUCOFACTS Diabetes Management Software available from Bayer HealthCare LLC (Tarrytown, New York). As such, the software 375 may provide a complete tool kit that receives and stores test results from a blood-glucose measurement system, receives and stores other testing information such as test times and meal markers, tracks test results in an electronic logbook, calculates averages and provides statistical analysis of outlier test results, summarizes and provides feedback on the test results, provides a customizable graphical user interface, displays user-friendly charts and graphs of the test results, tracks test results against user-specific target ranges, provides predictive analysis, and/or sends data to healthcare professionals via fax, email, etc. As described previously, data security is enhanced if the software 375 does not upload data from the modules 310 and 320 to the computing device 370 and the data is always stored within a single central storage device.
[0045] As described further below, the use of software or programmed instructions is not limited to the computing device 370. Moreover, the use of embodiments of the present invention are not using the particular modules 310, 320, 330, and 370. FIG. 4 illustrates a broader system diagram with other modules 300. For instance, as FIG. 4 illustrates, an A 1 c module 340, which monitors glucose control over time, may also be used in a diabetes-management system. The modules 300 also include other health monitor modules 350, such as blood pressure and heart rate monitors. Indeed, modules 300 may measure and/or record health data that do not require analyte testing, such as temperature measurements, blood pressure measurements, heart rate measurements, breathing measurements for chronic obstructive pulmonary disease (COPD) analysis, weight measurements for analyzing Lasix use, and the like. In further systems, other utility device modules 360 may include training modules, connectivity modules providing further connection to other systems, and other modules that improve or enhance a user's experience with the system. For example, it is contemplated that entertainment or media modules such as game modules or music player modules may be combined with the systems described herein. Providing entertainment features, for example, may encourage patients, particularly young patients, to keep the diagnostic systems with them wherever they go, so that health conditions, such as diabetes, can be monitored regularly. Furthermore, in some systems, the architecture may also employ open source code so that additional custom or specialized modules may be developed by users or third parties for integration with the architecture described herein.
Accordingly, an endless variety of modules providing any type of functionality may be employed.
[0046] As shown in FIG. 3, the system 100 includes a central engine 110, such as a digital engine, for the architecture and enables the modules 300 to be easily and effectively combined. For example, the central engine 110, the BGM 310, the CGM module 320, and the insulin-delivery device 330 can be effectively combined to create an artificial pancreas.
Alternatively, the central engine 110, the BGM 310, and the CGM 320 can be combined to form a CGM with an embedded BGM unit. Or as a further example, the central engine 110, the BGM 310, and the insulin-delivery device 330 can be combined to form a pump controller with an embedded BGM unit.
[0047]
Referring again to FIG. 4, the central engine 110 may include a processor 112 and a power management element 114. The processor 112 is capable of receiving and executing any number of programmed instructions, and may be a microcontroller, microprocessor, digital signal processor, or the like. The programmed instructions to be executed by the processor 112 may be embedded or may be retrievable from a storage device 250, a connected module 300, or another source such as an Internet website. The processor 112 centrally manages communications with the modules 300. In some cases, the processor 112 may also execute software that handles the operation of some modules 300.
Moreover, the processor 112 may give the modules 300 access to common resources or features such as the user interfaces 220 described further below.
[0048]
Power management element 120 distributes power from a power supply to the processor 112 as well as modules 300 that do not have their own power source.
The power management system 114, for example, may be configured to enter a standby mode to minimize power use when the system is idle. Additionally, if a rechargeable battery is employed, the power management system 114 may also handle the recharging of the battery.
[0049] As also shown in FIG. 4, the central engine 110 is connected to input/output interfaces 200, which can be divided into two different categories:
communication interfaces 210 and user interfaces 220. The communication interfaces 210 govern the exchange of data between the central engine 110 and the modules 300. In general, the communication interfaces 210 can accommodate wired and/or wireless communications.
Wired communications include, for example, communications by universal serial bus (USB) connection. Wireless communications include, for example, radio-frequency (RF) links (e.g., a short-range RF telemetry), infrared (IR) links, and/or Wi-Fi. Some known RF
technologies, for example, include Bluetooth wireless technologies, Zigbee, ZSenseTM
technology, FitSense, and BodyLANTM system. It is understood that other communication technologies, or protocols, may be employed.
[0050]
Referring again to FIG. 3, a wired, or physical, connection 212 exists between the central engine 110 and the computing device 370 while a wireless connection 214 exists between the central engine 110 and each of the CGM module 320 and the insulin-delivery device 330. It is noted that the BGM 310 is assembled with the central engine 110 in the housing 101. As such, the interface between the central engine 110 and the BGM
involves a wired connection (not shown). Indeed, as FIG. 3 illustrates, the modules 300 may be combined in any suitable arrangement in relation to the central engine 110 and to other modules 300. Like the BGM 310, some modules 300 may be assembled with the central engine 110 within the same housing, while other modules 300 may be provided in separate housings and arranged remotely from the central engine 110. It is also contemplated that in addition to other configurations described herein, some modules 300, having the form of circuit components, for example, may be assembled on the same printed circuit board assembly (PCBA) as circuit components for the central engine 110 with a circuit connection providing the interface 210.
[0051] FIG. 5 illustrates a further example of a connection between the central engine 110 and a module 300, namely the BGM 310. Unlike FIG. 3, the BGM 310 of FIG. 5 is not disposed in a housing 101 with the central engine 110, but the description provided with reference to FIG. 5 is equally applicable to the configuration in FIG. 3.
[0052] Referring to FIG. 5, the BGM 310 with a test sensor 316 is illustrated. The test sensor 316 is configured to receive a fluid sample which is analyzed using the BGM 310.
Analytes that may be analyzed include glucose, lipid profiles (e.g., cholesterol, triglycerides, LDL and HDL), microalbumin, hemoglobin A lc fructose, lactate, or bilirubin.
It is contemplated that other analyte information may be determined (e.g., analyte concentrations).
The analytes may be in, for example, a whole blood sample, a blood serum sample, a blood plasma sample, other body fluids like ISF (interstitial fluid) and urine, and non-body fluids.
[0053] The test sensor 316 includes a fluid-receiving area for receiving a sample of body fluid. For example, a user may employ a lancet or a lancing device to pierce a finger or other area of the body to produce the blood sample at the skin surface. The user may then collect this blood sample by placing the test sensor 316 into contact with the sample.
The fluid-receiving area may contain a reagent which reacts with the sample to indicate the concentration of an analyte in the sample.
[0054] The test sensor 316 may be an electrochemical test sensor. An electrochemical test sensor typically includes a plurality of electrodes and a fluid-receiving area that contains an enzyme. The fluid-receiving area includes a reagent for converting an analyte of interest (e.g., glucose) in a fluid sample (e.g., blood) into a chemical species that is electrochemically measurable, in terms of the electrical current it produces, by the components of the electrode pattern. The reagent typically contains an enzyme such as, for example, glucose oxidase, which reacts with the analyte and with an electron acceptor such as a ferricyanide salt to produce an electrochemically measurable species that can be detected by the electrodes. It is contemplated that other enzymes may be used to react with glucose such as glucose dehydrogenase. In general, the enzyme is selected to react with the desired analyte or analytes to be tested so as to assist in determining an information related to an analyte (e.g.
analyte concentration) of a fluid sample. If the concentration of another analyte is to be determined, an appropriate enzyme is selected to react with the analyte.
100551 Alternatively, the test sensor 316 may be an optical test sensor.
Optical test sensor systems may use techniques such as, for example, transmission spectroscopy, diffuse reflectance, or fluorescence spectroscopy for measuring the analyte concentration. An indicator reagent system and an analyte in a sample of body fluid are reacted to produce a chromatic reaction, as the reaction between the reagent and analyte causes the sample to change color. The degree of color change is indicative of the analyte concentration in the body fluid. The color change of the sample is evaluated to measure the absorbance level of the transmitted light.
100561 Some commercially available test sensors that may be used by the embodiments described herein include those that are available commercially from Bayer HealthCare LLC
(Tarrytown, New York). These test sensors include, but are not limited to, those used in the Ascensia CONTOUR blood glucose monitoring system, the Ascensia BREEZE and BREEZEO2 blood glucose monitoring system, and the Ascensia Elite and Elite XL
blood glucose monitoring system. It is contemplated that other test sensors, in addition to the ones listed above, may be incorporated into the methods and systems of the present invention.
100571 As illustrated in FIG. 5, the BGM 310 receives and engages the test sensor 316.
The BGM 310 includes a reaction-detection system for measuring the concentration of analyte for the sample collected by the test sensor 316. For example, the reaction-detection system may include contacts for the electrodes to detect the electrochemical reaction for an electrochemical test sensor. Alternatively, the reaction-detection system may include an optical detector to detect the chromatic reaction for an optical test sensor.
To calculate the actual concentration of analyte from the electrochemical or chromatic reaction measured by the reaction-detection system and to generally control the procedure for testing the sample, the BGM 310 employs at least one processor 312, which may execute programmed instructions according to a measurement algorithm. Data processed by the processor 312 may be stored in a memory 313. Furthermore, the BGM 310 may have a user interface 315 that includes a display, which, for example, may be a liquid-crystal display.
Pushbuttons, a scroll wheel, touch screens, or any combination thereof, may also be provided as a part of the user interface 315 to allow a user to interact with the BGM 310. The display typically shows information regarding the test results, the testing procedure and/or information in response to signals input by the user.
[0058] Although the BGM 310 can store test results and provide a user interface 315 to display test results, the data-management software 375 on the computing device 400 provides more advanced functionality for managing, processing, and displaying test results and related information. Therefore, the test-related data collected by the BGM 310 can be communicated via the central engine 110 to the computing device 370 for use with the data-management software 375. As shown in FIG. 5, the BGM 310 includes a BGM interface element 311 that enables the BGM 310 to connect with the central engine 110 via the engine interface element 111. Furthermore, the central engine 110 is connected to the engine interface element 116 which in turn is connected to computer interface element 376 of computing device 370. The BGM interface element 311, the computer interface element 376, and the engine interface elements 111 and 116 may employ the interface technologies described above to make the devices compatible and enable the appropriate data connections. For example, engine interface 111 and BGM interface 311 may connect via Bluetoothe wireless, while the engine interface 111 may connect to the computer interface 376 through a connection to a USB port.
Thus, it is readily seen that although the BGM 310 and the computing device 370 may not have compatible interfaces, the architecture of FIG. 5 enables data to be exchanged between them. Moreover, it is also readily contemplated that the development of the BGM 310 can be accomplished without regard to direct compatibility with USB interface of the computing device 370.
[0059] As discussed previously, the central engine 110 has the power management 114 which may include a power supply that is rechargeable via the connection with the computing device 370 or some other power source. When the central engine 110 and the BGM
310 are connected, a rechargeable battery can be recharged via power management 314.
[0060] As described previously, the BGM 310 in FIG. 5 employs at least one processor 312, which may execute programmed instructions. Moreover, the BGM 310 may have a user interface 315, which includes a display to present information to the user, as well as pushbuttons, a scroll wheel, touch screens, or any combination thereof to enable interaction by the user. With such components, the BGM 310 generally controls the whole procedure for testing the sample and calculates the test results. Indeed, the description provided with reference to FIG. 5 generally explains how the test results already calculated by the BGM 310 may be subsequently shared with other modules such as the computing device 370.
However, it is contemplated that the processor 112 of the central engine 110 can also provide a wider range of functions. In fact, it is further contemplated that the processing in a health monitoring and delivery system can be distributed among the components, including the central engine 110, in varying manners.
[0061] For example, FIG. 6 illustrates a sensor-receiving module 380 that requires other components to handle substantially all of the processing. Like the BGM 310, the sensor-receiving module 380 is configured to receive a test sensor 316. However, the sensor-receiving module 380 does not have a processor to manage the testing procedure or to calculate test results. In addition, the sensor-receiving module 380 has no user interface to communicate with the user. In general, the sensor-receiving module 380 is designed to merely receive a test sensor 316 and to provide an interface element 381 for physical connection to the rest of the diagnostic system. As a result, analysis of the test sample on the test sensor 316 is only possible when the sensor-receiving module 380 connects with a device that has a processor to analyze the sample via the interface element 381.
[0062] As shown in FIG. 6, the interface element 381of the sensor-receiving module 380 is connected to the interface element 111, which in turn is connected to the digital sensor 110.
It is noted that the connection between the sensor-receiving module 380 and the central engine 110 may require a host function, such as the USB host function, to be employed by the central engine 110. In one embodiment, the digital sensor 110 is also connected to the interface element 376 of the computing device 370. The interfaces between the sensor-receiving module 380, the central engine 110, and the computing device 370 may employ any of the interface technologies, such as USB or BluetoothiD technology, described above.
Accordingly, the computing device 370 can execute software 377 to control the procedure for testing a sample and calculating the test results in a manner similar to the processor 312 on BGM 310 in FIG. 5. In operation, the sensor-receiving module 380, the central engine 110, and the computing device 370 are connected as shown in FIG. 6. The test sensor 316 is used to collect a fluid sample, such as a blood sample. If, for example, the test sensor 316 is an electrochemical test sensor, the sensor-receiving module 380 system may include electrical contacts to receive the electrical signal from the electrochemical reaction that occurs between the sample and the reagent on the test sensor 316. The connection between the sensor-receiving element 380 and the central engine 110 is connected to the circuit containing the electrical sensors so that the central engine 110 receives the electrical signal from the electrochemical reaction. This signal can then be passed to the computing device 370 to process the signal and determine the test results using a measurement algorithm. The user interface on the computing device 370 can be used to display the test results or to receive instructions from the user.
[0063] It is understood that other techniques may be employed to communicate a signal from the sensor-receiving module 380. For example, a test sensor 316 may be an optical test sensor and the sensor-receiving system 380 may include an optical detector to detect a chromatic reaction. If the sensor-receiving module 380 requires any power to receive or process a signal from the test sensor 316, the power can be drawn through its connection with the central engine 110.
[0064] Alternatively, in another embodiment, the computing device 370 is not employed in the system, so that the sensor-receiving module 380 is only connected to the central engine 110 as shown in FIG. 7. As such, the test result calculations are completed by the processor 112 of the central engine 110 and the test results are displayed on a user interface connected to the central engine 110. As shown in FIG. 7, a user interface 115 may be incorporated into the housing 101.
[0065] The measurement software 253 for controlling the test process and determining the results may be available through the storage device 250 as illustrated in FIG. 7. As illustrated in FIG. 4, the storage device 250 corresponds with another type of input/output interface 200. The storage device 250 may be a flash memory device, such as a universal serial bus (USB) flash drive or a memory card. USB flash drives are also known as thumb drives, handy drives, flash sticks, or jump drives. Memory cards may have a variety of formats, including PC Card (PCMCIA), CompactFlash (CF), SmartMedia (SM/SMC), Memory Stick (MS), Multimedia Card (MMC), Secure Digital Card (SD), xD-Picture Card (xD), Intelligent Stick (iStick), ExpressCard, or some variation thereof.
Flash memory devices may employ non-volatile memory so that the software associated with the measurement software 253 may be retained in the storage device 250 even when the storage device 250 receives no power. In some embodiments, the memory in the storage device 250 may include execute-in-place (XIP) memory, such as NOR flash memory, so that the measurement software 253 stored on the memory can be executed directly. It is also contemplated that the storage device 250 may employ other storage media, such as floppy disk or optical disc (CD, DVD, Blu-ray disc).
[0066] The storage device 250 may be assembled with the central engine 110 in the housing 101, as shown in FIG. 7, or it may be connected to the central engine 110 in a manner similar to an external module (e.g., module 300). Particularly in the latter case, the storage device 250 may interface with a communications interface 210 and connect to the central engine 110. The interface enables data communications between the storage device 250 and the central engine 110 and permits the measurement software 253, or any other software, to be used with central engine 110. In particular, the storage device 250 has an interface element that is compatible with an interface element 210. In some embodiments, the storage-device interface element physically engages the interface element 210 to form a serial hardware interface. For example, the storage device 250 may be a USB
flash drive, and the storage-device interface element may be a USB connector that is received into a USB
port, which acts as the communications interface element 210 for the central engine 110.
[0067] As a further example, the storage device 250 may be a Secure Digital (SD) memory card with a series of contacts that act as the interface element, and the communication interface 210 may be an expansion slot that receives the contacts of the memory card. In this example, the central engine 110 and the storage device 200 may comply with SDIO (Secure Digital Input Output) interface specifications. It is contemplated that other memory card formats having different interface specifications may be employed.
However, having an SDIO is advantageous because many hosts such as PDAs, HPCs and smart cellular phones include an expansion slot that is SDIO compatible.
[0068] As the central engine 110 in FIG. 7 is filling the role of the computing device 370 in the example of FIG. 6, higher-powered processing devices may be required.
For example, some embodiments may employ handheld or pocket personal computers (HPCs), compatible personal digital assistants (PDAs), or smart cellular phones. As discussed above, these processing devices may employ a variety of operating systems and configurations. For example, if the computing device 370 is a PDA, the operating system may correspond with those of PALM handhelds from Palm, Inc., or Blackberry devices from Research in Motion Limited. Advantageously, PALM handhelds and Blackberry devices provide a portable device with enough processing power to reliably execute advanced data management software for results collected from the sensor-receiving module 380. Moreover, such devices provide rich user interfaces that provide advanced graphical display capabilities. In addition, because these handheld devices connect to external networks, such as the Internet, new software or software upgrades/patches can be readily installed. Furthermore, the connection to the telecommunications network enables test results to be easily transmitted to doctors and other healthcare professionals for monitoring or evaluation. Because many consumers already carry these or similar devices, many users of a diagnostics system, such as a diabetes-management system, would conveniently incorporate the system in devices they already own and carry regularly.
[0069]
Because embodiments may employ many different types of modules 300 that may be situated on different types of hardware, the communication interfaces 210 generally have to accommodate more than one type of communication technology, or protocol.
However, to minimize the number of communication interfaces 210 while providing the widest range of compatibility between the central engine 110 and the various modules 300, the communication interfaces 210 can employ widely-used and standardized interface technologies, such as USB or Bluetooth technology. Preferably, the communication interfaces 210 employ technologies that minimize the amount of configuration required to establish communication between a module 300 and the central engine 110.
Indeed, some communication technologies, such as USB connectivity, provide plug-n-play (PnP) capability. In these embodiments, the module 300 is physically connected, for example, through a conventional USB port. Then in response, the central engine 110 immediately recognizes the module 300 and establishes immediate communication with the module 300, [0070]
The communication interfaces 210 not only provide communication between modules 300, but they also enable secure communication with external networks.
As such, embodiments may employ a connection to an external network to download updates, upgrades, or additions to the software in the central engine and/or the modules 300 when the product is out in the field. In other words, the embodiments may provide field upgradeable software functions.
Advantageously, embodiments allow the user to update any software/firmware in the integrated system, e.g., software for the central engine 110 and/or the modules 300, by using program files provided by, or purchased from, the manufacturer or an authorized third party. Existing system software can be updated or patched with newer versions, or new software may be added to the system, without requiring the user to contact the manufacturer or third party for direct assistance. The new software allows the user to customize and/or expand the functionality of the system. In some cases, a product may be essentially converted to a new product. Field upgrades make the latest product features available to users who have already purchased a product. Moreover, field upgrades making existing product compatible with other newly released accessories or devices.
For example, in a diabetes-management system, if the BGM 310 uses a test sensor to test blood for blood glucose concentration, and the BGM manufacturer develops a new test sensor that improves accuracy or test time, embodiments would allow the user to upgrade the firmware in the device so that the BGM 310 is capable of reading the new test sensor.
[0071] The central engine may manage aspects of the field upgrade validation in combination with a download engine. The download engine, described further below, can receive system components from a server, e.g., the field upgrade server, the external network via a communication interface and deliver the system components for validation and deployment. Additionally or alternatively, the server on the external network can manage aspects of the field upgrade process.
[0072] In addition, due to the important medical functions associated with the modules 300, embodiments employ validation procedures before employing the new software or configuration information to ensure that any field upgrade does not corrupt the data or the software stored by the product and that the product continues to operate as expected. For example, check-sum routines may be employed to confirm that data or software has been successfully downloaded in its entirety. For example, the central engine 110 may validate downloads according to an associated data update file (DUF) or other component that ensures that the software has been successfully downloaded. For additional data security, the field upgrade process may employ data encryption/decryption.
[0073] In an example embodiment illustrated in FIG. 9, once a connection is established with a field upgrade server in an appropriate external network (act 502), an available field upgrade is identified for an existing system component, e.g., new software or configuration information, (act 504). The connection to the server may be triggered automatically when a connection to the network may be established, or a user may manually initiate communication with the field upgrade server. To identify an available field upgrade, the central engine or the server may employ a version management program to determine which system components in the architecture are compatible with, and can be replaced by, newer or different versions stored on the field upgrade server. The new system component is then downloaded from the field upgrade server to a memory, i.e., data storage area, that is separate from the memory area storing the existing system component. An area of memory may be specifically dedicated for field upgrade operations. In other words, the existing system component is retained, rather than deleted or written over at least until validation is complete.
The new system component is validated with a system check (act 508), and if the download has been successful and the system operates properly, the new system component is deployed for regular system operation. Thus, if the field upgrade fails, the previous version of the system component is still available and provides a recovery or restore option.
The new system component is removed with a failed field upgrade. In some embodiments, the new version may replace the previous version in memory after the new version is validated. In other embodiments, the one or more previous versions are retained even after validation and users may have the option to restore one or more previous versions of a system component if an older version is preferred.
[0074] An example embodiment is described with reference to FIG. 8. In the embodiment of FIG. 8. the diabetes-management system 400 may include modules 402, 403, 404, and 405 which collect fluid samples. The digital engine 406 controls each module, user interface 413, memory 407, and the download engine 408. Download engine 408 provides an interface between one of the communication modules, digital engine 406, and memory 407.
The communications modules may include USB interface 409 which provides, for example, communication between a computing device USB port and the system 401. The communication module may also include a Bluetooth interface 410 which provides wireless communication between the system 400 and a computing device, cell phone, and/or other devices capable of communicating with the system 400. Furthermore, a Wi-Fi interface 411 provides communication between a wireless network and the system 400.
Additionally, the Ethernet interface 411 provides communication between a local area network and the system 400. Each communication module can be used to upgrade/update the meter's software in the field upon the user's direction. The following features may also be downloaded per user request: new firmware for new functions; new firmware to update the behavior of current system functions; user interface language; screen updates and customization;
games and other standalone applications; gauges; and other software or configuration settings/updates.
[0075] For example, the user interface may communicate in many languages, but all the data required for those languages does not have to be stored locally, as users may download language files as required to customize the operation of their systems. In addition, users can customize the appearance of the user interface display by installing custom pictures to display on the screen or by downloading display layouts made available by a manufacturer or an authorized third party. Furthermore, users can customize the behavior of the system by installing standalone applications (such as games) that can run on the system processor and be played when the system 400 is not being used to analyze body fluids. Users can also customize system behavior by installing software that changes the way body fluid analysis results are displayed, as results may be presented as digital readouts, simulated analog gauges, qualitative feedback, etc.
[0076] Referring again to FIG. 4, the input/output interfaces 200 also include user interfaces 220, which generally allow the modules 300 to display information, such as test results, to the user. The modules 300 may transmit such information to the central engine 110 via communication interfaces 210, and the central engine 110 may in turn present the information on the display interfaces 220. Although centralized handling of communications may be preferred, the modules 300, in some cases, may interface directly with the display interfaces 220. As shown in FIG. 2, the display interfaces may include graphic liquid crystal display (LCD) or organic light-emitting diode (OLED), segment LCD or OLED, MP4 playback, or the like.
[0077] In addition, the input/output interfaces 200 may allow information to be communicated to and from the user via audio signals. For example, the input/output interfaces 200 may include a speech synthesizer, MP3 playback, or the like, for communicating audio information to a user. Additionally, the input/output interfaces 200 may also include a speech recognition mechanism to receive audio information from a user.
[0078] Furthermore, the user interfaces 200 may allow the user to input information or instructions into the system. For example, the user may be required to respond to simple prompts or make menu selections to guide one of the modules 300 during operation. Or as a further example, the user may want to enter instructions to retrieve information, such as test results, and to present the information on the display interfaces 220.
Mechanisms for providing input, for example, may include a keypad, a touch screen, a thumb wheel, or the like.
[0079] As shown in FIG. 7, a user interface 115 may be incorporated into the housing 101 in which the central engine 110 and corresponding communication interfaces 210 are assembled. As such, the housing 101 may form a portable device 101 for a health monitoring and delivery system. As discussed previously with reference to FIG. 3, some modules 300, such as the BGM 310, may be incorporated into the device, while other modules, such as CGM 320 and the insulin delivery module 330, may be externally connected to the portable device 101 through the communication interfaces 210. The modules 300 connected to the digital engine 310 have access to the interface [0080] Systems employing the architecture support various types of electronic networks and communications. Modules 300 may be employed, for example, to provide cellular activity. Other embodiments, alternatively or additionally, may employ global positioning system (GPS) technology, which has become widely accessible to civilian applications such as road navigation, people tracking, and timing services. With the technology becoming more and more mature, the cost of integrating this technology into consumer products and medical device has been significantly reduced. GPS receiver chipsets are currently available on market and can be easily integrated with consumer or medical device to provide information on device location, velocity and Universal time. As such, GPS may be provided to enhance the functionality of a system employing architecture to form an integrated system for monitoring a health condition and/or delivering a medication.
[0081]
With GPS, a diabetes-management system, for example, can provide additional information associated with glucose tests. Accurate timestamps and locations can be associated with readings. The erroneous timestamps generated by conventional meters have been the source of confusion and difficulty when readings from multiple meters are downloaded and merged into one database file, or uploaded to computers or web servers that do not have their local time in sync with the meters. Patient movement and exercise can be tracked automatically, facilitating patient logging effort tremendously. The data may include distance and speed. This information can be used for patient daily activity planning for exercise, diet, medication and blood glucose test frequency, etc. It also enables comprehensive analysis of correlation between reading patterns and daily activities Furthermore, patients can be located in emergencies.
[0082]
The additional timing, location and physical activity information obtained with GPS, combined with logged diet, medication information, can assist the diabetes-management system to make more accurate predictions on patients' daily blood glucose patterns.
The diabetes-management system can make real-time daily activity recommendations that will help them to control their blood glucose levels in the prescribed range. The system can then remind patients to take the right number of tests daily at the right moments.
[0083]
Accordingly, GPS may be employed to synchronize a system's device's real time clock (RTC) to UMT with high precision so that glucose readings can be associated with correct timestamp. As power for the GPS functionality may be a consideration, the GPS
receiver may only need to be activated once a day or a week depending on the device crystal quality. Assuming that each time the GPS consumes 0.175 mAhr power (calculated based on Xemics XE1600 receiver using Trimble chipsets), and the device takes a GPS
measurement once a day, 63.9 mAhr is consumed in a year for the GPS related calculation which is roughly about 10 ¨ 20% of a regular cell phone battery capacity.
[0084] As discussed previously, some portable embodiments of an integrated monitoring/delivery system may connect with a computing device 370 for advanced data management. This situation provides the opportunity for applying the NAVSYS
GPS
recorder model (TrackTag) to the portable device to track patient movement and activity.
Because a GPS recorder simply takes snapshots of satellite signals without processing them, a significant amount of power can be saved. Assume the device takes a GPS
snapshot once every 150 sec, then in one year this GPS recorder only consumes about 280 mAhr, which is roughly about < 50% of a regular cell phone battery capacity. If the device can stop taking snapshots at night then further energy can be preserved. The trade off in using the TrackTag approach is the required amount of on-device memory required. Every snapshot takes about 15 kbyte, so at the above snapshot rate, there will be about 200,000 snapshot per year which requires about 3Gbyte memory. Of course, once GPS data is downloaded from the device to computer and processed, the device memory can be freed up and reused. It seems that one Gbyte memory may support 4 months of location tracking for the portable device. Using modern flash memory technology, one Gbyte device memory can be easily accommodated.
[0085] The GPS functionality may be a built-in central function. In a more modular example, however, the GPS functionality may be provided by a connected module, i.e. a detachable GPS receiver. Indeed, if the GPS receiver module has its own memory to store time and position information, then the GPS may not need to be connected all the time with the DM device. The GPS receiver may be connected with the system once a day or one every few days depending on how often the device clock needs to be synchronized and also on the availability of GPS receiver memory. Advantageously, the use of a detachable GPS receiver module minimized the impact on hardware/software design of the central engine 110 and other aspects of the system. Moreover, power management is facilitated.
[00861 While the invention is susceptible to various modifications and alternative forms, specific embodiments and methods thereof have been shown by way of example in the drawings and are described in detail herein. The scope of the claims should not be limited by the preferred embodiments set forth in the examples, but should be given the broadest interpretation consistent with the Description as a whole.
100101 Although the architecture makes it more feasible to shorten a product's development cycle and to introduce the product to consumers more quickly, the embodiments also provide an approach for dynamically updating the product and offering its users the latest generation of technology even after the users have already purchased the product. In particular, the embodiments employ the communication interfaces to also provide connection to a remote network that can update or upgrade the product's software when the product is out in the field. This process is known as a field upgrade.
[0011] Because the interfaces and communication protocols are designed to facilitate connection between different components and the rest of the system, the embodiments also provide functionality that ensures that unauthorized individuals or devices cannot connect with the system and compromise the security of data, such as personal medical information, which may be collected, stored, and handled by the system. With this underlying security functionality, particular technologies, such as wireless communication, can be implemented as components of medical diagnostic systems without concern over unauthorized access to personal information.
[0012] In addition, due to the important medical functions associated with the assembled product, embodiments employ validation procedures to ensure that any data transferred to the product, for example, during field upgrade, does not corrupt the data or the software stored by the product and that the product continues to operate as expected.
[0013] Still other aspects, features, and advantages of the present invention are readily apparent from the following detailed description, by illustrating a number of exemplary embodiments and implementations, including the best mode contemplated for carrying out the present invention. Accordingly, the drawings and descriptions are to be regarded as illustrative in nature, and not as restrictive.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG. IA illustrates a diagram of an architecture according to aspects of the present invention.
[0015] FIG. 1B illustrates a diagram of another architecture according to aspects of the present invention.
[0016] FIG. 2A illustrates an example security measure that can be employed by an architecture according to aspects of the present invention.
[0017] FIG. 2B illustrates another example security measure that can be employed by an architecture according to aspects of the present invention.
[0018] FIG. 2C illustrates a further example security measure that can be employed by an architecture according to aspects of the present invention.
[0019] FIG. 2D illustrates yet another example security measure that can be employed by an architecture according to aspects of the present invention.
[0020] FIG. 3 illustrates an example diabetes-management system employing an architecture according to aspects of the present invention.
[0021] FIG. 4 illustrates another diagram of an architecture according to aspects of the present invention.
[0022] FIG. 5 illustrates an example of a diagnostic system employing an architecture according to aspects of the present invention.
[0023] FIG. 6 illustrates another example of a diagnostic system employing an architecture according to aspecis of the present invention.
[0024] FIG. 7 illustrates yet another example of a diagnostic system employing an architecture according to aspects of the present invention.
[0025] FIG. 8 illustrates a field-upgradeable architecture according to aspects of the present invention.
[0026] FIG. 9 illustrates an example for employing a field upgrade according to aspects of the present invention.
DESCRIPTION OF ILLUSTRATED EMBODIMENTS
[0027] The embodiments described herein provide a system architecture that allows individual system components, or modules, to be developed and validated independently (as distinct modules) and subsequently combined through standardized electrical and communication interfaces. The standardized interfaces facilitate the combination and configuration of these modules to form different products that provide any number of functions. While the architecture can be used to form a fixed combination of components, the approach also permits reconfigurable or expandable combinations where different components may be easily removed or added to the system. In addition, as described further below, the architecture provides an approach for dynamically updating the modules after they have been integrated into the product.
[0028] FIG. 1A illustrates a conceptual diagram of a modular architecture according to aspects of the present invention. As shown in FIG. 1A, a modular architecture system 1 includes central engine 10 that is connected to a plurality of modules 30A, 30B, 30C, and 30D, each of which provides a functionality for a health monitoring and delivery system.
The central engine 10 enables the modules 30A, 30B, 30C, and 30D to work as an effective system. For example, the central engine 10 allows information to be communicated between the modules 30A, 30B, 30C, and 30D. For example, module 30D may be a computing device with software that processes data received from the other modules 30A, 30B, and 30C via the central engine 10. As FIG. 1A further illustrates, interface elements 22A, 22B, 22C, and 22D
of the central engine 10 connect with respective interface elements 24A, 24B, 24C, and 24D
to establish communications between the central engine 10 and the modules 30A, 30B, 30C, and 30D. The interfaces may provide wired, i.e. physical, and/or wireless communications.
Advantageously, the centralized organization of the interface architecture facilitates the integration of modules 30A, 30B, 30C, and 30D, which can be developed and tested separately from each other. Moreover, although the interface elements 22A, 22B, 22C, and 22D of the central engine 10 do not have to follow the same communications protocol, the interface elements 22A, 22B, 22C, and 22D can employ the most widely-used standard protocols so that the central engine 10 is more likely to be compatible with a given module.
[0029] Although the modules 30A, 30B, 30C, and 30D of FIG. 1A may all communicate information with each other, it is contemplated that a module connected to the central engine does not have to communicate with all of the other modules. Indeed, a module may be communicatively isolated from any, including all, of the other modules. For example, the nature of data and/or software on a particular module may be highly sensitive, so the module may be isolated from the other modules to enhance the security and/or integrity of the data.
[0030] In one embodiment, the central engine 10 is implemented on a mother board, while each module is separately implemented on a daughter board. The daughter boards are standardized so that they may connect to a single mother board to be integrated with the system. In other words, specific interfaces with boards corresponding to other modules do not have to be developed each time a new module is implemented. Due to this standardized approach, using commercial off-the-shelf (COTS) hardware for the mother and daughter boards becomes more feasible. Advantageously, using COTS hardware requires less development time than an application-specific integrated circuit (ASIC) approach.
[0031] In some embodiments, the mother board and the daughter boards may physically reside on separate circuit boards. In other embodiments, the mother board and the daughter boards may all be physically integrated onto the same circuit board. In further embodiments, the mother board and a combination of daughter boards may be physically integrated onto the same circuit board, while other daughter boards reside on separate circuit boards. Moreover, in some embodiments, the mother board and the daughter boards, whether on the same circuit boards or not, may all be disposed in the same housing, or casing. Meanwhile, in other embodiments, some or all of the daughter boards may be disposed in one or more housings separate from the mother board's housing. In general, the components of embodiments may be subject to varying degrees of physical integration regarding assembly on different circuit boards or within different housings, etc. To accommodate this variation in physical configuration, more than one interface type may be required to connect the daughter boards to the mother board, but as discussed previously, the interfaces between the central engine and the modules do not have to follow the same communications protocol. The interface elements associated with the mother board can employ the most widely-used standard protocols so that the central engine is more likely to be compatible with a given module.
[0032] The centralized architecture using standardized interfaces facilitates the development of compatible modules. When adding functionality to the system, integration with the architecture is easily achieved by employing a compatible interface element.
Moreover, the new module can be developed independently of the other modules, because only a single interface with the central engine 10 is required. In other words, even if the new module must communicate with other modules in the system, the new module does not have to be designed for a direct connection with the other modules, so the communications configuration of the other modules is not a significant design consideration for the new module. Accordingly, the ability to independently develop additional modules that easily connect with the central engine 10 enables systems employing this architecture to be flexible and reconfigurable. For example, such a system can be expanded with new modules or upgraded with new versions of existing modules.
[0033] Although FIG. IA illustrates an embodiment with the single central engine 10 connected to modules 30A, 30B, 30C, and 30D, the central engine 10 in some embodiments may also connect to a secondary central engine 40 as illustrated in FIG. 1B.
As shown in FIG. 1B, the central engine 10 is connected to modules 30A, 30B, and 30C via corresponding interface elements 22A/24A, 22B/24B, and 22C/24C. Meanwhile, the central engine 40 is connected to modules 60A, 60B, and 60C via corresponding interface elements 52A/54A, 52B/54B, and 52C/54C. As with the modules 30A, 30B, and 30C, the modules 60A, 60B, and 60C may be developed independently of the other modules according to a modular architecture that only requires a single interface with the central engine 40.
As further illustrated in FIG. 1B, the central engine 10 may be connected to the central engine 40 via interface elements 22D and 52D. Like the other interface elements, the interface elements 22D and 52D may provide wired, i.e. physical, or wireless communications. In some embodiments, the central engine 10 assumes a host function for the central engine 40. For example, if the central engine 10 connects to the central engine 40 according to universal serial bus (USB) communication protocol, standard USB requires a host-slave relationship between the two systems.
[0034] In the embodiment of FIG. 1B, the central engine 10 may access the functionalities provided by the modules 60A, 60B, and 60C, and conversely, the central engine 40 may access the functionalities provided by the modules 30A, 30B, and 30C. Even though the resulting combination may function like a single central engine connected to all six modules 30A, 30B, 30C, 60A, 60B, and 60C, the central engines 10 and 40 may be developed separately. As such, the development of a set of modules can be advantageously organized into separate subsets. For example, medical diagnostic systems may include critical medical devices, such as a blood-glucose meter, as well as other types of devices, such as a heart rate monitor. The critical medical devices may require very rigorous product validation during development and may be subject to government regulations.
Meanwhile, the other types of devices may not require the same type or same level of validation. As such, modules involving critical medical devices may have very different timelines and guidelines for product development compared to the other types of health care devices. Thus, in this case, it may be advantageous to organize the modules into two product development groups. In addition, every time a product involving critical medical devices is redeveloped or updated to include new features, government regulations may require revalidation of the product even if the new features may be relatively minor. For example, if a heart rate monitor is added to a central engine that is already connected to a blood-glucose meter, the entire system may have to be revalidated at great cost and effort, even though the new modules is a less critical health care device. However, the central engine connected to the blood-glucose meter can remain unchanged if the central engine already has the capability to connect to a secondary central engine that in turn is connected to the heart rate monitor. In other words, deploying new modules involving other health care devices and other features through the secondary central engine provides a way to expand the overall product without changing the architecture associated with the primary central engine.
Moreover, any validation of the architecture associated with the secondary central engine may be conducted without affecting the architecture associated with the primary central engine.
[0035] Although an advantage of the architectures described herein is the ease by which new modules can interface with the system and establish communications and data exchange, issues relating to the security of personal medical data have discouraged using highly compatible communication technologies with medical devices, such as personal testing devices that measure and store health data. To address these issues, embodiments according to aspects of the present invention provide functionality that helps to ensure that unauthorized individuals or devices cannot connect with the system and compromise the security of any personal medical information. The central engine 10 may be responsible for providing security measures. Alternatively or additionally, a component or module with special security functions may be employed to promote system security. With such security functionality, particular technologies, such as wireless communication, can be implemented as components of medical diagnostic systems without heightened concern over unauthorized access to personal information.
[0036] FIGS. 2A-D illustrate examples of security techniques that may be employed by an architecture according to aspects of the present invention. As shown in FIG. 2A, the central engine 10 may prompt the user for a user ID and password, personal identification number (PIN), or other authentication information, when a module 30 attempts to interface with the central engine 10 or to access data through the system. The module 30 is only allowed connection or data access if the response to the security prompt corresponds with authentication information stored at the system. For example, the module 30 may be a PC
executing a data-management program that uploads test data from a blood-glucose meter connected to the central engine 10. When the program attempts to communicate through an interface connection or tries to access data, the user must submit a user ID
and password.
The authentication information may be entered through a user interface, e.g. a keypad or keyboard, on the PC or the central engine 10. If the module 30 is used frequently to access data through the central engine 10, the user may find it inconvenient to enter authentication information repeatedly. Thus, some embodiments may allow a user to set a time period (from zero to infinity) between authentications from the particular module 30.
The central engine 10 records a unique identifier, e.g. device ID, for module 30 to keep track of the time period. For instance, a security prompt may be required if the specified time, e.g. one day, has passed since the last authentication. Alternatively, the user may stop all further security prompts from occurring after the first authentication. In this alternative case, the first authentication acts as a registration with the central engine 10 to permit all future access from the module 30.
[0037] As shown in FIG. 2B, a unique identifier, e.g. device ID, for module 30 may be registered with the central engine 10. This unique identifier may be entered by the user or recorded when the authentication process shown in FIG. 2A is completed for the first time.
Alternatively, registration of the module 30 may be achieved through an initial, e.g. factory, set-up process. In this alternative case, registration of additional modules may be prohibited after the initial set-up, thereby fixing the number of modules in the system.
When the module 30 subsequently attempts to connect or access data, the central engine 10 automatically recognizes the module 30 and permits access.
[0038] In the embodiments of FIGS. 2A and 2B, the module 30 is authenticated or registered in a one-way process. In other words, the central engine 10 is not required to be authenticated or registered with the module 30. In contrast, as shown in FIG.
2C, both the central engine 10 and the module 30 are required to be registered with each other. Matching of unique identifiers for the pair is required before any communication takes place between the central engine 10 and the module 30. This pair matching is particularly applicable to wireless communication between two devices. The process prevents intentional unauthorized access, and also prevents interference between two different systems. For example, if a user is in a setting, such as a hospital or clinic, where others are using similar wireless analyte-testing devices, such as blood-glucose meters, pair matching prevents another person's blood-glucose meter from accidentally communicating with the user's diagnostic system and providing the wrong data.
[0039] Data security may also be enhanced by using encrypted data during communications, as shown in FIG. 2D. This is also particularly applicable to wireless communications, so that any intercepted data will be unreadable. The data encryption may be achieved by using private encryption keys.
[0040] Data security may be further enhanced by ensuring that all data is stored by the central engine 10 within memory in the architecture and is not transferred to any connected modules. Thus, a user may, for example, use a public computer to interface with the system and no data will be transferred to the public computer for others to access.
[0041] FIG. 3 provides a non-limiting example of a diabetes-management system 100 that can be formed from the architecture approach described herein. The diabetes-management system 100 is advantageous to those individuals who are actively involved in monitoring and recording measurements of their blood glucose concentrations and/or other analytes of interest.
[0042] As shown in FIG. 3, the diabetes-management system 100 includes a blood-glucose meter (BGM) 310, a continuous glucose monitoring (CGM) module 320, an insulin-delivery device 330, and a computing device 370, which may include diabetes data management software 375. The modules 310, 320, 330, and 370 are combined, as described further below, using the architecture approaches described herein to provide health monitoring and delivery functions for the diabetes-management system 100. In particular, the BGM 310 provides point-in-time measurements of blood-glucose concentrations in blood samples; the CGM module 320 provides continuous measurements of blood-glucose concentration; and the insulin-delivery device 330 delivers insulin to the user.
[0043] In addition, the computing device 370 executes the software 375 to receive data from the modules 310, 320, and 330 and provides advanced data processing and management capabilities. The computing device 370 may be selected from a variety of processing devices, such as desktop or laptop personal computers (PCs), handheld or pocket personal computers (HPCs), compatible personal digital assistants (PDAs), and smart cellular phones.
The processing devices may employ a variety of operating systems and configurations. For example, if the computing device 370 is a desktop or laptop personal computer, the operating system may be a version of Microsoft Windows . Alternatively, if the computing device 370 is a PDA, the operating system may correspond with those of PALM
handhelds from Palm, Inc., or Blackberry devices from Research in Motion Limited. In general, computing device 370 includes a processor that is capable of receiving and executing any number of programmed instructions.
[0044] The data-management software 375 on the computing device 370 may be a collection of programs or computer code that receives and processes data measured by the modules 310 and 320, for example. The software 375 processes and/or displays this input in a manner that is desired by the user. This information may be used by, for example, a user, home care provider (HCP), and/or a physician. The measured data from the modules 310 and 320 may include, for example, the concentration of glucose and/or other analytes in a person's blood or other bodily fluid. Advantageously, the software 375 can provide the advanced displays and data processing that may be required by a user who tests multiple times a day (e.g., about six to about ten times a day). For example, the software 375 may include a product similar to WINGLUCOFACTS Diabetes Management Software available from Bayer HealthCare LLC (Tarrytown, New York). As such, the software 375 may provide a complete tool kit that receives and stores test results from a blood-glucose measurement system, receives and stores other testing information such as test times and meal markers, tracks test results in an electronic logbook, calculates averages and provides statistical analysis of outlier test results, summarizes and provides feedback on the test results, provides a customizable graphical user interface, displays user-friendly charts and graphs of the test results, tracks test results against user-specific target ranges, provides predictive analysis, and/or sends data to healthcare professionals via fax, email, etc. As described previously, data security is enhanced if the software 375 does not upload data from the modules 310 and 320 to the computing device 370 and the data is always stored within a single central storage device.
[0045] As described further below, the use of software or programmed instructions is not limited to the computing device 370. Moreover, the use of embodiments of the present invention are not using the particular modules 310, 320, 330, and 370. FIG. 4 illustrates a broader system diagram with other modules 300. For instance, as FIG. 4 illustrates, an A 1 c module 340, which monitors glucose control over time, may also be used in a diabetes-management system. The modules 300 also include other health monitor modules 350, such as blood pressure and heart rate monitors. Indeed, modules 300 may measure and/or record health data that do not require analyte testing, such as temperature measurements, blood pressure measurements, heart rate measurements, breathing measurements for chronic obstructive pulmonary disease (COPD) analysis, weight measurements for analyzing Lasix use, and the like. In further systems, other utility device modules 360 may include training modules, connectivity modules providing further connection to other systems, and other modules that improve or enhance a user's experience with the system. For example, it is contemplated that entertainment or media modules such as game modules or music player modules may be combined with the systems described herein. Providing entertainment features, for example, may encourage patients, particularly young patients, to keep the diagnostic systems with them wherever they go, so that health conditions, such as diabetes, can be monitored regularly. Furthermore, in some systems, the architecture may also employ open source code so that additional custom or specialized modules may be developed by users or third parties for integration with the architecture described herein.
Accordingly, an endless variety of modules providing any type of functionality may be employed.
[0046] As shown in FIG. 3, the system 100 includes a central engine 110, such as a digital engine, for the architecture and enables the modules 300 to be easily and effectively combined. For example, the central engine 110, the BGM 310, the CGM module 320, and the insulin-delivery device 330 can be effectively combined to create an artificial pancreas.
Alternatively, the central engine 110, the BGM 310, and the CGM 320 can be combined to form a CGM with an embedded BGM unit. Or as a further example, the central engine 110, the BGM 310, and the insulin-delivery device 330 can be combined to form a pump controller with an embedded BGM unit.
[0047]
Referring again to FIG. 4, the central engine 110 may include a processor 112 and a power management element 114. The processor 112 is capable of receiving and executing any number of programmed instructions, and may be a microcontroller, microprocessor, digital signal processor, or the like. The programmed instructions to be executed by the processor 112 may be embedded or may be retrievable from a storage device 250, a connected module 300, or another source such as an Internet website. The processor 112 centrally manages communications with the modules 300. In some cases, the processor 112 may also execute software that handles the operation of some modules 300.
Moreover, the processor 112 may give the modules 300 access to common resources or features such as the user interfaces 220 described further below.
[0048]
Power management element 120 distributes power from a power supply to the processor 112 as well as modules 300 that do not have their own power source.
The power management system 114, for example, may be configured to enter a standby mode to minimize power use when the system is idle. Additionally, if a rechargeable battery is employed, the power management system 114 may also handle the recharging of the battery.
[0049] As also shown in FIG. 4, the central engine 110 is connected to input/output interfaces 200, which can be divided into two different categories:
communication interfaces 210 and user interfaces 220. The communication interfaces 210 govern the exchange of data between the central engine 110 and the modules 300. In general, the communication interfaces 210 can accommodate wired and/or wireless communications.
Wired communications include, for example, communications by universal serial bus (USB) connection. Wireless communications include, for example, radio-frequency (RF) links (e.g., a short-range RF telemetry), infrared (IR) links, and/or Wi-Fi. Some known RF
technologies, for example, include Bluetooth wireless technologies, Zigbee, ZSenseTM
technology, FitSense, and BodyLANTM system. It is understood that other communication technologies, or protocols, may be employed.
[0050]
Referring again to FIG. 3, a wired, or physical, connection 212 exists between the central engine 110 and the computing device 370 while a wireless connection 214 exists between the central engine 110 and each of the CGM module 320 and the insulin-delivery device 330. It is noted that the BGM 310 is assembled with the central engine 110 in the housing 101. As such, the interface between the central engine 110 and the BGM
involves a wired connection (not shown). Indeed, as FIG. 3 illustrates, the modules 300 may be combined in any suitable arrangement in relation to the central engine 110 and to other modules 300. Like the BGM 310, some modules 300 may be assembled with the central engine 110 within the same housing, while other modules 300 may be provided in separate housings and arranged remotely from the central engine 110. It is also contemplated that in addition to other configurations described herein, some modules 300, having the form of circuit components, for example, may be assembled on the same printed circuit board assembly (PCBA) as circuit components for the central engine 110 with a circuit connection providing the interface 210.
[0051] FIG. 5 illustrates a further example of a connection between the central engine 110 and a module 300, namely the BGM 310. Unlike FIG. 3, the BGM 310 of FIG. 5 is not disposed in a housing 101 with the central engine 110, but the description provided with reference to FIG. 5 is equally applicable to the configuration in FIG. 3.
[0052] Referring to FIG. 5, the BGM 310 with a test sensor 316 is illustrated. The test sensor 316 is configured to receive a fluid sample which is analyzed using the BGM 310.
Analytes that may be analyzed include glucose, lipid profiles (e.g., cholesterol, triglycerides, LDL and HDL), microalbumin, hemoglobin A lc fructose, lactate, or bilirubin.
It is contemplated that other analyte information may be determined (e.g., analyte concentrations).
The analytes may be in, for example, a whole blood sample, a blood serum sample, a blood plasma sample, other body fluids like ISF (interstitial fluid) and urine, and non-body fluids.
[0053] The test sensor 316 includes a fluid-receiving area for receiving a sample of body fluid. For example, a user may employ a lancet or a lancing device to pierce a finger or other area of the body to produce the blood sample at the skin surface. The user may then collect this blood sample by placing the test sensor 316 into contact with the sample.
The fluid-receiving area may contain a reagent which reacts with the sample to indicate the concentration of an analyte in the sample.
[0054] The test sensor 316 may be an electrochemical test sensor. An electrochemical test sensor typically includes a plurality of electrodes and a fluid-receiving area that contains an enzyme. The fluid-receiving area includes a reagent for converting an analyte of interest (e.g., glucose) in a fluid sample (e.g., blood) into a chemical species that is electrochemically measurable, in terms of the electrical current it produces, by the components of the electrode pattern. The reagent typically contains an enzyme such as, for example, glucose oxidase, which reacts with the analyte and with an electron acceptor such as a ferricyanide salt to produce an electrochemically measurable species that can be detected by the electrodes. It is contemplated that other enzymes may be used to react with glucose such as glucose dehydrogenase. In general, the enzyme is selected to react with the desired analyte or analytes to be tested so as to assist in determining an information related to an analyte (e.g.
analyte concentration) of a fluid sample. If the concentration of another analyte is to be determined, an appropriate enzyme is selected to react with the analyte.
100551 Alternatively, the test sensor 316 may be an optical test sensor.
Optical test sensor systems may use techniques such as, for example, transmission spectroscopy, diffuse reflectance, or fluorescence spectroscopy for measuring the analyte concentration. An indicator reagent system and an analyte in a sample of body fluid are reacted to produce a chromatic reaction, as the reaction between the reagent and analyte causes the sample to change color. The degree of color change is indicative of the analyte concentration in the body fluid. The color change of the sample is evaluated to measure the absorbance level of the transmitted light.
100561 Some commercially available test sensors that may be used by the embodiments described herein include those that are available commercially from Bayer HealthCare LLC
(Tarrytown, New York). These test sensors include, but are not limited to, those used in the Ascensia CONTOUR blood glucose monitoring system, the Ascensia BREEZE and BREEZEO2 blood glucose monitoring system, and the Ascensia Elite and Elite XL
blood glucose monitoring system. It is contemplated that other test sensors, in addition to the ones listed above, may be incorporated into the methods and systems of the present invention.
100571 As illustrated in FIG. 5, the BGM 310 receives and engages the test sensor 316.
The BGM 310 includes a reaction-detection system for measuring the concentration of analyte for the sample collected by the test sensor 316. For example, the reaction-detection system may include contacts for the electrodes to detect the electrochemical reaction for an electrochemical test sensor. Alternatively, the reaction-detection system may include an optical detector to detect the chromatic reaction for an optical test sensor.
To calculate the actual concentration of analyte from the electrochemical or chromatic reaction measured by the reaction-detection system and to generally control the procedure for testing the sample, the BGM 310 employs at least one processor 312, which may execute programmed instructions according to a measurement algorithm. Data processed by the processor 312 may be stored in a memory 313. Furthermore, the BGM 310 may have a user interface 315 that includes a display, which, for example, may be a liquid-crystal display.
Pushbuttons, a scroll wheel, touch screens, or any combination thereof, may also be provided as a part of the user interface 315 to allow a user to interact with the BGM 310. The display typically shows information regarding the test results, the testing procedure and/or information in response to signals input by the user.
[0058] Although the BGM 310 can store test results and provide a user interface 315 to display test results, the data-management software 375 on the computing device 400 provides more advanced functionality for managing, processing, and displaying test results and related information. Therefore, the test-related data collected by the BGM 310 can be communicated via the central engine 110 to the computing device 370 for use with the data-management software 375. As shown in FIG. 5, the BGM 310 includes a BGM interface element 311 that enables the BGM 310 to connect with the central engine 110 via the engine interface element 111. Furthermore, the central engine 110 is connected to the engine interface element 116 which in turn is connected to computer interface element 376 of computing device 370. The BGM interface element 311, the computer interface element 376, and the engine interface elements 111 and 116 may employ the interface technologies described above to make the devices compatible and enable the appropriate data connections. For example, engine interface 111 and BGM interface 311 may connect via Bluetoothe wireless, while the engine interface 111 may connect to the computer interface 376 through a connection to a USB port.
Thus, it is readily seen that although the BGM 310 and the computing device 370 may not have compatible interfaces, the architecture of FIG. 5 enables data to be exchanged between them. Moreover, it is also readily contemplated that the development of the BGM 310 can be accomplished without regard to direct compatibility with USB interface of the computing device 370.
[0059] As discussed previously, the central engine 110 has the power management 114 which may include a power supply that is rechargeable via the connection with the computing device 370 or some other power source. When the central engine 110 and the BGM
310 are connected, a rechargeable battery can be recharged via power management 314.
[0060] As described previously, the BGM 310 in FIG. 5 employs at least one processor 312, which may execute programmed instructions. Moreover, the BGM 310 may have a user interface 315, which includes a display to present information to the user, as well as pushbuttons, a scroll wheel, touch screens, or any combination thereof to enable interaction by the user. With such components, the BGM 310 generally controls the whole procedure for testing the sample and calculates the test results. Indeed, the description provided with reference to FIG. 5 generally explains how the test results already calculated by the BGM 310 may be subsequently shared with other modules such as the computing device 370.
However, it is contemplated that the processor 112 of the central engine 110 can also provide a wider range of functions. In fact, it is further contemplated that the processing in a health monitoring and delivery system can be distributed among the components, including the central engine 110, in varying manners.
[0061] For example, FIG. 6 illustrates a sensor-receiving module 380 that requires other components to handle substantially all of the processing. Like the BGM 310, the sensor-receiving module 380 is configured to receive a test sensor 316. However, the sensor-receiving module 380 does not have a processor to manage the testing procedure or to calculate test results. In addition, the sensor-receiving module 380 has no user interface to communicate with the user. In general, the sensor-receiving module 380 is designed to merely receive a test sensor 316 and to provide an interface element 381 for physical connection to the rest of the diagnostic system. As a result, analysis of the test sample on the test sensor 316 is only possible when the sensor-receiving module 380 connects with a device that has a processor to analyze the sample via the interface element 381.
[0062] As shown in FIG. 6, the interface element 381of the sensor-receiving module 380 is connected to the interface element 111, which in turn is connected to the digital sensor 110.
It is noted that the connection between the sensor-receiving module 380 and the central engine 110 may require a host function, such as the USB host function, to be employed by the central engine 110. In one embodiment, the digital sensor 110 is also connected to the interface element 376 of the computing device 370. The interfaces between the sensor-receiving module 380, the central engine 110, and the computing device 370 may employ any of the interface technologies, such as USB or BluetoothiD technology, described above.
Accordingly, the computing device 370 can execute software 377 to control the procedure for testing a sample and calculating the test results in a manner similar to the processor 312 on BGM 310 in FIG. 5. In operation, the sensor-receiving module 380, the central engine 110, and the computing device 370 are connected as shown in FIG. 6. The test sensor 316 is used to collect a fluid sample, such as a blood sample. If, for example, the test sensor 316 is an electrochemical test sensor, the sensor-receiving module 380 system may include electrical contacts to receive the electrical signal from the electrochemical reaction that occurs between the sample and the reagent on the test sensor 316. The connection between the sensor-receiving element 380 and the central engine 110 is connected to the circuit containing the electrical sensors so that the central engine 110 receives the electrical signal from the electrochemical reaction. This signal can then be passed to the computing device 370 to process the signal and determine the test results using a measurement algorithm. The user interface on the computing device 370 can be used to display the test results or to receive instructions from the user.
[0063] It is understood that other techniques may be employed to communicate a signal from the sensor-receiving module 380. For example, a test sensor 316 may be an optical test sensor and the sensor-receiving system 380 may include an optical detector to detect a chromatic reaction. If the sensor-receiving module 380 requires any power to receive or process a signal from the test sensor 316, the power can be drawn through its connection with the central engine 110.
[0064] Alternatively, in another embodiment, the computing device 370 is not employed in the system, so that the sensor-receiving module 380 is only connected to the central engine 110 as shown in FIG. 7. As such, the test result calculations are completed by the processor 112 of the central engine 110 and the test results are displayed on a user interface connected to the central engine 110. As shown in FIG. 7, a user interface 115 may be incorporated into the housing 101.
[0065] The measurement software 253 for controlling the test process and determining the results may be available through the storage device 250 as illustrated in FIG. 7. As illustrated in FIG. 4, the storage device 250 corresponds with another type of input/output interface 200. The storage device 250 may be a flash memory device, such as a universal serial bus (USB) flash drive or a memory card. USB flash drives are also known as thumb drives, handy drives, flash sticks, or jump drives. Memory cards may have a variety of formats, including PC Card (PCMCIA), CompactFlash (CF), SmartMedia (SM/SMC), Memory Stick (MS), Multimedia Card (MMC), Secure Digital Card (SD), xD-Picture Card (xD), Intelligent Stick (iStick), ExpressCard, or some variation thereof.
Flash memory devices may employ non-volatile memory so that the software associated with the measurement software 253 may be retained in the storage device 250 even when the storage device 250 receives no power. In some embodiments, the memory in the storage device 250 may include execute-in-place (XIP) memory, such as NOR flash memory, so that the measurement software 253 stored on the memory can be executed directly. It is also contemplated that the storage device 250 may employ other storage media, such as floppy disk or optical disc (CD, DVD, Blu-ray disc).
[0066] The storage device 250 may be assembled with the central engine 110 in the housing 101, as shown in FIG. 7, or it may be connected to the central engine 110 in a manner similar to an external module (e.g., module 300). Particularly in the latter case, the storage device 250 may interface with a communications interface 210 and connect to the central engine 110. The interface enables data communications between the storage device 250 and the central engine 110 and permits the measurement software 253, or any other software, to be used with central engine 110. In particular, the storage device 250 has an interface element that is compatible with an interface element 210. In some embodiments, the storage-device interface element physically engages the interface element 210 to form a serial hardware interface. For example, the storage device 250 may be a USB
flash drive, and the storage-device interface element may be a USB connector that is received into a USB
port, which acts as the communications interface element 210 for the central engine 110.
[0067] As a further example, the storage device 250 may be a Secure Digital (SD) memory card with a series of contacts that act as the interface element, and the communication interface 210 may be an expansion slot that receives the contacts of the memory card. In this example, the central engine 110 and the storage device 200 may comply with SDIO (Secure Digital Input Output) interface specifications. It is contemplated that other memory card formats having different interface specifications may be employed.
However, having an SDIO is advantageous because many hosts such as PDAs, HPCs and smart cellular phones include an expansion slot that is SDIO compatible.
[0068] As the central engine 110 in FIG. 7 is filling the role of the computing device 370 in the example of FIG. 6, higher-powered processing devices may be required.
For example, some embodiments may employ handheld or pocket personal computers (HPCs), compatible personal digital assistants (PDAs), or smart cellular phones. As discussed above, these processing devices may employ a variety of operating systems and configurations. For example, if the computing device 370 is a PDA, the operating system may correspond with those of PALM handhelds from Palm, Inc., or Blackberry devices from Research in Motion Limited. Advantageously, PALM handhelds and Blackberry devices provide a portable device with enough processing power to reliably execute advanced data management software for results collected from the sensor-receiving module 380. Moreover, such devices provide rich user interfaces that provide advanced graphical display capabilities. In addition, because these handheld devices connect to external networks, such as the Internet, new software or software upgrades/patches can be readily installed. Furthermore, the connection to the telecommunications network enables test results to be easily transmitted to doctors and other healthcare professionals for monitoring or evaluation. Because many consumers already carry these or similar devices, many users of a diagnostics system, such as a diabetes-management system, would conveniently incorporate the system in devices they already own and carry regularly.
[0069]
Because embodiments may employ many different types of modules 300 that may be situated on different types of hardware, the communication interfaces 210 generally have to accommodate more than one type of communication technology, or protocol.
However, to minimize the number of communication interfaces 210 while providing the widest range of compatibility between the central engine 110 and the various modules 300, the communication interfaces 210 can employ widely-used and standardized interface technologies, such as USB or Bluetooth technology. Preferably, the communication interfaces 210 employ technologies that minimize the amount of configuration required to establish communication between a module 300 and the central engine 110.
Indeed, some communication technologies, such as USB connectivity, provide plug-n-play (PnP) capability. In these embodiments, the module 300 is physically connected, for example, through a conventional USB port. Then in response, the central engine 110 immediately recognizes the module 300 and establishes immediate communication with the module 300, [0070]
The communication interfaces 210 not only provide communication between modules 300, but they also enable secure communication with external networks.
As such, embodiments may employ a connection to an external network to download updates, upgrades, or additions to the software in the central engine and/or the modules 300 when the product is out in the field. In other words, the embodiments may provide field upgradeable software functions.
Advantageously, embodiments allow the user to update any software/firmware in the integrated system, e.g., software for the central engine 110 and/or the modules 300, by using program files provided by, or purchased from, the manufacturer or an authorized third party. Existing system software can be updated or patched with newer versions, or new software may be added to the system, without requiring the user to contact the manufacturer or third party for direct assistance. The new software allows the user to customize and/or expand the functionality of the system. In some cases, a product may be essentially converted to a new product. Field upgrades make the latest product features available to users who have already purchased a product. Moreover, field upgrades making existing product compatible with other newly released accessories or devices.
For example, in a diabetes-management system, if the BGM 310 uses a test sensor to test blood for blood glucose concentration, and the BGM manufacturer develops a new test sensor that improves accuracy or test time, embodiments would allow the user to upgrade the firmware in the device so that the BGM 310 is capable of reading the new test sensor.
[0071] The central engine may manage aspects of the field upgrade validation in combination with a download engine. The download engine, described further below, can receive system components from a server, e.g., the field upgrade server, the external network via a communication interface and deliver the system components for validation and deployment. Additionally or alternatively, the server on the external network can manage aspects of the field upgrade process.
[0072] In addition, due to the important medical functions associated with the modules 300, embodiments employ validation procedures before employing the new software or configuration information to ensure that any field upgrade does not corrupt the data or the software stored by the product and that the product continues to operate as expected. For example, check-sum routines may be employed to confirm that data or software has been successfully downloaded in its entirety. For example, the central engine 110 may validate downloads according to an associated data update file (DUF) or other component that ensures that the software has been successfully downloaded. For additional data security, the field upgrade process may employ data encryption/decryption.
[0073] In an example embodiment illustrated in FIG. 9, once a connection is established with a field upgrade server in an appropriate external network (act 502), an available field upgrade is identified for an existing system component, e.g., new software or configuration information, (act 504). The connection to the server may be triggered automatically when a connection to the network may be established, or a user may manually initiate communication with the field upgrade server. To identify an available field upgrade, the central engine or the server may employ a version management program to determine which system components in the architecture are compatible with, and can be replaced by, newer or different versions stored on the field upgrade server. The new system component is then downloaded from the field upgrade server to a memory, i.e., data storage area, that is separate from the memory area storing the existing system component. An area of memory may be specifically dedicated for field upgrade operations. In other words, the existing system component is retained, rather than deleted or written over at least until validation is complete.
The new system component is validated with a system check (act 508), and if the download has been successful and the system operates properly, the new system component is deployed for regular system operation. Thus, if the field upgrade fails, the previous version of the system component is still available and provides a recovery or restore option.
The new system component is removed with a failed field upgrade. In some embodiments, the new version may replace the previous version in memory after the new version is validated. In other embodiments, the one or more previous versions are retained even after validation and users may have the option to restore one or more previous versions of a system component if an older version is preferred.
[0074] An example embodiment is described with reference to FIG. 8. In the embodiment of FIG. 8. the diabetes-management system 400 may include modules 402, 403, 404, and 405 which collect fluid samples. The digital engine 406 controls each module, user interface 413, memory 407, and the download engine 408. Download engine 408 provides an interface between one of the communication modules, digital engine 406, and memory 407.
The communications modules may include USB interface 409 which provides, for example, communication between a computing device USB port and the system 401. The communication module may also include a Bluetooth interface 410 which provides wireless communication between the system 400 and a computing device, cell phone, and/or other devices capable of communicating with the system 400. Furthermore, a Wi-Fi interface 411 provides communication between a wireless network and the system 400.
Additionally, the Ethernet interface 411 provides communication between a local area network and the system 400. Each communication module can be used to upgrade/update the meter's software in the field upon the user's direction. The following features may also be downloaded per user request: new firmware for new functions; new firmware to update the behavior of current system functions; user interface language; screen updates and customization;
games and other standalone applications; gauges; and other software or configuration settings/updates.
[0075] For example, the user interface may communicate in many languages, but all the data required for those languages does not have to be stored locally, as users may download language files as required to customize the operation of their systems. In addition, users can customize the appearance of the user interface display by installing custom pictures to display on the screen or by downloading display layouts made available by a manufacturer or an authorized third party. Furthermore, users can customize the behavior of the system by installing standalone applications (such as games) that can run on the system processor and be played when the system 400 is not being used to analyze body fluids. Users can also customize system behavior by installing software that changes the way body fluid analysis results are displayed, as results may be presented as digital readouts, simulated analog gauges, qualitative feedback, etc.
[0076] Referring again to FIG. 4, the input/output interfaces 200 also include user interfaces 220, which generally allow the modules 300 to display information, such as test results, to the user. The modules 300 may transmit such information to the central engine 110 via communication interfaces 210, and the central engine 110 may in turn present the information on the display interfaces 220. Although centralized handling of communications may be preferred, the modules 300, in some cases, may interface directly with the display interfaces 220. As shown in FIG. 2, the display interfaces may include graphic liquid crystal display (LCD) or organic light-emitting diode (OLED), segment LCD or OLED, MP4 playback, or the like.
[0077] In addition, the input/output interfaces 200 may allow information to be communicated to and from the user via audio signals. For example, the input/output interfaces 200 may include a speech synthesizer, MP3 playback, or the like, for communicating audio information to a user. Additionally, the input/output interfaces 200 may also include a speech recognition mechanism to receive audio information from a user.
[0078] Furthermore, the user interfaces 200 may allow the user to input information or instructions into the system. For example, the user may be required to respond to simple prompts or make menu selections to guide one of the modules 300 during operation. Or as a further example, the user may want to enter instructions to retrieve information, such as test results, and to present the information on the display interfaces 220.
Mechanisms for providing input, for example, may include a keypad, a touch screen, a thumb wheel, or the like.
[0079] As shown in FIG. 7, a user interface 115 may be incorporated into the housing 101 in which the central engine 110 and corresponding communication interfaces 210 are assembled. As such, the housing 101 may form a portable device 101 for a health monitoring and delivery system. As discussed previously with reference to FIG. 3, some modules 300, such as the BGM 310, may be incorporated into the device, while other modules, such as CGM 320 and the insulin delivery module 330, may be externally connected to the portable device 101 through the communication interfaces 210. The modules 300 connected to the digital engine 310 have access to the interface [0080] Systems employing the architecture support various types of electronic networks and communications. Modules 300 may be employed, for example, to provide cellular activity. Other embodiments, alternatively or additionally, may employ global positioning system (GPS) technology, which has become widely accessible to civilian applications such as road navigation, people tracking, and timing services. With the technology becoming more and more mature, the cost of integrating this technology into consumer products and medical device has been significantly reduced. GPS receiver chipsets are currently available on market and can be easily integrated with consumer or medical device to provide information on device location, velocity and Universal time. As such, GPS may be provided to enhance the functionality of a system employing architecture to form an integrated system for monitoring a health condition and/or delivering a medication.
[0081]
With GPS, a diabetes-management system, for example, can provide additional information associated with glucose tests. Accurate timestamps and locations can be associated with readings. The erroneous timestamps generated by conventional meters have been the source of confusion and difficulty when readings from multiple meters are downloaded and merged into one database file, or uploaded to computers or web servers that do not have their local time in sync with the meters. Patient movement and exercise can be tracked automatically, facilitating patient logging effort tremendously. The data may include distance and speed. This information can be used for patient daily activity planning for exercise, diet, medication and blood glucose test frequency, etc. It also enables comprehensive analysis of correlation between reading patterns and daily activities Furthermore, patients can be located in emergencies.
[0082]
The additional timing, location and physical activity information obtained with GPS, combined with logged diet, medication information, can assist the diabetes-management system to make more accurate predictions on patients' daily blood glucose patterns.
The diabetes-management system can make real-time daily activity recommendations that will help them to control their blood glucose levels in the prescribed range. The system can then remind patients to take the right number of tests daily at the right moments.
[0083]
Accordingly, GPS may be employed to synchronize a system's device's real time clock (RTC) to UMT with high precision so that glucose readings can be associated with correct timestamp. As power for the GPS functionality may be a consideration, the GPS
receiver may only need to be activated once a day or a week depending on the device crystal quality. Assuming that each time the GPS consumes 0.175 mAhr power (calculated based on Xemics XE1600 receiver using Trimble chipsets), and the device takes a GPS
measurement once a day, 63.9 mAhr is consumed in a year for the GPS related calculation which is roughly about 10 ¨ 20% of a regular cell phone battery capacity.
[0084] As discussed previously, some portable embodiments of an integrated monitoring/delivery system may connect with a computing device 370 for advanced data management. This situation provides the opportunity for applying the NAVSYS
GPS
recorder model (TrackTag) to the portable device to track patient movement and activity.
Because a GPS recorder simply takes snapshots of satellite signals without processing them, a significant amount of power can be saved. Assume the device takes a GPS
snapshot once every 150 sec, then in one year this GPS recorder only consumes about 280 mAhr, which is roughly about < 50% of a regular cell phone battery capacity. If the device can stop taking snapshots at night then further energy can be preserved. The trade off in using the TrackTag approach is the required amount of on-device memory required. Every snapshot takes about 15 kbyte, so at the above snapshot rate, there will be about 200,000 snapshot per year which requires about 3Gbyte memory. Of course, once GPS data is downloaded from the device to computer and processed, the device memory can be freed up and reused. It seems that one Gbyte memory may support 4 months of location tracking for the portable device. Using modern flash memory technology, one Gbyte device memory can be easily accommodated.
[0085] The GPS functionality may be a built-in central function. In a more modular example, however, the GPS functionality may be provided by a connected module, i.e. a detachable GPS receiver. Indeed, if the GPS receiver module has its own memory to store time and position information, then the GPS may not need to be connected all the time with the DM device. The GPS receiver may be connected with the system once a day or one every few days depending on how often the device clock needs to be synchronized and also on the availability of GPS receiver memory. Advantageously, the use of a detachable GPS receiver module minimized the impact on hardware/software design of the central engine 110 and other aspects of the system. Moreover, power management is facilitated.
[00861 While the invention is susceptible to various modifications and alternative forms, specific embodiments and methods thereof have been shown by way of example in the drawings and are described in detail herein. The scope of the claims should not be limited by the preferred embodiments set forth in the examples, but should be given the broadest interpretation consistent with the Description as a whole.
Claims (17)
1. A system for managing healthcare data, comprising:
a mother circuit including a processor and a mother circuit memory area storing a first updatable software;
a first daughter circuit interfacing with the mother circuit, the first daughter circuit including a first daughter circuit memory area storing a second updatable software that provides a healthcare function;
a second daughter circuit interfacing with the mother circuit and being communicatively isolated from the first daughter circuit thereby enhancing the integrity of the healthcare function provided by the first updatable software, the second daughter circuit including a second daughter circuit memory area storing a third updatable software that provides a second function;
one or more communication interfaces providing a connection to a remote server, the remote server storing one or more program components;
a download engine receiving the one or more program components from the remote server via the one or more communication interfaces, the one or more program components for replacing (i) an older version of the first updatable software running on the mother circuit with an updated version of the first updatable software, (ii) an older version of the third updatable software running on the second daughter circuit with an updated version of the third updatable software, or (iii) both (i) and (ii); and a restore component that restores the older version of the first updatable software or the older version of the third updatable software when a validation component determines that the updated version of the first updatable software or the updated version of the third updatable software operates incorrectly or has not been downloaded properly, thereby ensuring that the system, including the healthcare function and the second function, continues to operate as expected.
a mother circuit including a processor and a mother circuit memory area storing a first updatable software;
a first daughter circuit interfacing with the mother circuit, the first daughter circuit including a first daughter circuit memory area storing a second updatable software that provides a healthcare function;
a second daughter circuit interfacing with the mother circuit and being communicatively isolated from the first daughter circuit thereby enhancing the integrity of the healthcare function provided by the first updatable software, the second daughter circuit including a second daughter circuit memory area storing a third updatable software that provides a second function;
one or more communication interfaces providing a connection to a remote server, the remote server storing one or more program components;
a download engine receiving the one or more program components from the remote server via the one or more communication interfaces, the one or more program components for replacing (i) an older version of the first updatable software running on the mother circuit with an updated version of the first updatable software, (ii) an older version of the third updatable software running on the second daughter circuit with an updated version of the third updatable software, or (iii) both (i) and (ii); and a restore component that restores the older version of the first updatable software or the older version of the third updatable software when a validation component determines that the updated version of the first updatable software or the updated version of the third updatable software operates incorrectly or has not been downloaded properly, thereby ensuring that the system, including the healthcare function and the second function, continues to operate as expected.
2. The system of claim 1, further comprising a version management component that determines whether the one or more program components is compatible with the mother circuit, the first daughter circuit, or the second daughter circuit before the download engine receives the one or more program components.
3. The system of claim 1, wherein the updated version of the third updatable software is downloaded to a third daughter circuit memory area contained in the second daughter circuit that is separate from the second daughter circuit memory area storing the older version of the third updatable software such that the older version of the third updatable software remains available to be restored.
4. The system of claim 1, wherein the one or more program components provides a patch for software running on the first daughter circuit, the second daughter circuit, or both.
5. The system of claim 1, wherein the one or more program components provides a new function to be executed by the first daughter circuit, the second daughter circuit, or both.
6. The system of claim 1, wherein the one or more program components includes configuration information for software running on the first daughter circuit, the second daughter circuit, or both.
7. The system of claim 1, wherein the download engine is manually triggered by a user to receive and deliver the one or more program components.
8. The system of claim 1, wherein the download engine is automatically triggered to identify the one or more program components when communication to the remote server can be established.
9. The system of claim 1, wherein the one or more interfaces include at least one of a USB interface, a radio frequency (RF) interface, a Wi-Fi interface, and an Ethernet interface.
10. The system of claim 1, wherein when communication to the remote server is established when the download engine is in range of a wireless network.
11. The system of claim 1, further comprising a data validation component to validate the one or more program components before the one or more program components is deployed.
12. The system of claim 11, wherein the data validation component determines whether the one or more program components are not corrupted.
13. The system of claim 11, wherein the data validation component determines, with a check-sum routine, whether the one or more program components has been completely transferred from the remote server via the download engine.
14. The system of claim 11, wherein the one or more program components are removed if the date validation determines that the one or more program components are corrupted.
15. The system of claim 1, wherein the second function is different than the healthcare function provided by the second updatable software.
16. The system of claim 1, wherein the second function is a healthcare function.
17. The system of claim 1, wherein the one or more program components are further for replacing an older version of the second updatable software running on the first daughter circuit with an updated version of the second updatable software.
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US93228607P | 2007-05-30 | 2007-05-30 | |
US60/932,286 | 2007-05-30 | ||
US1272107P | 2007-12-10 | 2007-12-10 | |
US1271807P | 2007-12-10 | 2007-12-10 | |
US61/012,718 | 2007-12-10 | ||
US61/012,721 | 2007-12-10 | ||
PCT/US2008/006814 WO2008150428A1 (en) | 2007-05-30 | 2008-05-29 | Architecture for health monitoring systems |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2688123A1 CA2688123A1 (en) | 2008-12-11 |
CA2688123C true CA2688123C (en) | 2016-07-12 |
Family
ID=39711897
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2997497A Abandoned CA2997497A1 (en) | 2007-05-30 | 2008-05-29 | Method and system for managing health data |
CA2688046A Expired - Fee Related CA2688046C (en) | 2007-05-30 | 2008-05-29 | Method and system for managing health data |
CA2688123A Expired - Fee Related CA2688123C (en) | 2007-05-30 | 2008-05-29 | Architecture for health monitoring systems |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2997497A Abandoned CA2997497A1 (en) | 2007-05-30 | 2008-05-29 | Method and system for managing health data |
CA2688046A Expired - Fee Related CA2688046C (en) | 2007-05-30 | 2008-05-29 | Method and system for managing health data |
Country Status (14)
Country | Link |
---|---|
US (11) | US8401873B2 (en) |
EP (6) | EP3474283A1 (en) |
JP (2) | JP5721029B2 (en) |
CN (4) | CN102841976A (en) |
AR (2) | AR066808A1 (en) |
BR (2) | BRPI0812315A2 (en) |
CA (3) | CA2997497A1 (en) |
CL (2) | CL2008001599A1 (en) |
ES (3) | ES2712778T3 (en) |
HK (1) | HK1139754A1 (en) |
MX (2) | MX2009012937A (en) |
RU (1) | RU2611019C2 (en) |
TW (5) | TWI552105B (en) |
WO (2) | WO2008153825A2 (en) |
Families Citing this family (143)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010011224A1 (en) | 1995-06-07 | 2001-08-02 | Stephen James Brown | Modular microprocessor-based health monitoring system |
WO2002078512A2 (en) * | 2001-04-02 | 2002-10-10 | Therasense, Inc. | Blood glucose tracking apparatus and methods |
US7811231B2 (en) | 2002-12-31 | 2010-10-12 | Abbott Diabetes Care Inc. | Continuous glucose monitoring system and methods of use |
US8771183B2 (en) | 2004-02-17 | 2014-07-08 | Abbott Diabetes Care Inc. | Method and system for providing data communication in continuous glucose monitoring and management system |
US7587287B2 (en) | 2003-04-04 | 2009-09-08 | Abbott Diabetes Care Inc. | Method and system for transferring analyte test data |
US8066639B2 (en) | 2003-06-10 | 2011-11-29 | Abbott Diabetes Care Inc. | Glucose measuring device for use in personal area network |
US8112240B2 (en) | 2005-04-29 | 2012-02-07 | Abbott Diabetes Care Inc. | Method and apparatus for providing leak detection in data monitoring and management systems |
US7766829B2 (en) | 2005-11-04 | 2010-08-03 | Abbott Diabetes Care Inc. | Method and system for providing basal profile modification in analyte monitoring and management systems |
US8226891B2 (en) | 2006-03-31 | 2012-07-24 | Abbott Diabetes Care Inc. | Analyte monitoring devices and methods therefor |
US8123686B2 (en) | 2007-03-01 | 2012-02-28 | Abbott Diabetes Care Inc. | Method and apparatus for providing rolling data in communication systems |
TWI364208B (en) * | 2007-04-23 | 2012-05-11 | Inventec Corp | Data updating method and electric device using the same |
US8456301B2 (en) | 2007-05-08 | 2013-06-04 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods |
US7928850B2 (en) | 2007-05-08 | 2011-04-19 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods |
US8461985B2 (en) | 2007-05-08 | 2013-06-11 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods |
US8665091B2 (en) | 2007-05-08 | 2014-03-04 | Abbott Diabetes Care Inc. | Method and device for determining elapsed sensor life |
ES2712778T3 (en) | 2007-05-30 | 2019-05-14 | Ascensia Diabetes Care Holdings Ag | Method and system to manage health data |
US8105841B2 (en) * | 2007-10-15 | 2012-01-31 | Bayer Healthcare Llc | Method and assembly for determining the temperature of a test sensor |
JP5065075B2 (en) * | 2008-02-12 | 2012-10-31 | 株式会社リコー | Information processing apparatus, information processing method, and program |
US20090259493A1 (en) * | 2008-04-11 | 2009-10-15 | Venon Medhi O | Mobile health book |
US8133197B2 (en) | 2008-05-02 | 2012-03-13 | Smiths Medical Asd, Inc. | Display for pump |
CN102089656B (en) * | 2008-07-07 | 2015-01-14 | 埃葛梅崔克斯股份有限公司 | Integrated blood glucose measurement device |
CA2739091A1 (en) * | 2008-10-03 | 2010-04-08 | Bayer Healthcare Llc | System and method for predicting ambient temperature in a fluid analyte meter |
US9954976B2 (en) * | 2008-11-03 | 2018-04-24 | Viavi Solutions Inc. | System and method for remotely displaying data |
US20100125463A1 (en) * | 2008-11-20 | 2010-05-20 | John Frank Stagl | Personal Information Gathering, Storing, and Transfer System |
US20120278106A1 (en) * | 2008-11-20 | 2012-11-01 | John Frank Stagl | Personal Information Gathering, Storing, and Transfer System and Method of Use |
WO2010127050A1 (en) | 2009-04-28 | 2010-11-04 | Abbott Diabetes Care Inc. | Error detection in critical repeating data in a wireless sensor system |
US9656092B2 (en) | 2009-05-12 | 2017-05-23 | Chronicmobile, Inc. | Methods and systems for managing, controlling and monitoring medical devices via one or more software applications functioning in a secure environment |
US9184490B2 (en) | 2009-05-29 | 2015-11-10 | Abbott Diabetes Care Inc. | Medical device antenna systems having external antenna configurations |
JP2012527981A (en) * | 2009-05-29 | 2012-11-12 | ユニバーシティ オブ バージニア パテント ファウンデーション | System coordinator and module architecture for open-loop and closed-loop control of diabetes |
US8595607B2 (en) * | 2009-06-04 | 2013-11-26 | Abbott Diabetes Care Inc. | Method and system for updating a medical device |
JP5112394B2 (en) * | 2009-07-21 | 2013-01-09 | 富士ソフト株式会社 | Medical information system and program |
US8993331B2 (en) | 2009-08-31 | 2015-03-31 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods for managing power and noise |
US9314195B2 (en) | 2009-08-31 | 2016-04-19 | Abbott Diabetes Care Inc. | Analyte signal processing device and methods |
CN104951647B (en) | 2009-09-08 | 2018-06-22 | 艾伯特糖尿病护理公司 | The method and product of safety-critical application program are accommodated on uncontrolled data processing equipment |
US20110208531A1 (en) * | 2010-02-25 | 2011-08-25 | Wavelight Ag | Medical Office, Particularly for Surgical Eye Treatments |
EP2372490A1 (en) * | 2010-03-31 | 2011-10-05 | Robert Bosch GmbH | Circuit arrangement for a data processing system and method for data processing |
DE102010003521A1 (en) * | 2010-03-31 | 2011-10-06 | Robert Bosch Gmbh | Modular structure for data processing |
US20110256024A1 (en) * | 2010-04-16 | 2011-10-20 | Abbott Diabetes Care Inc. | Modular Analyte Monitoring Device |
US8726266B2 (en) * | 2010-05-24 | 2014-05-13 | Abbott Diabetes Care Inc. | Method and system for updating a medical device |
JP2014500538A (en) | 2010-10-12 | 2014-01-09 | タニス,ケヴィン ジェイ. | Medical equipment |
US8383056B2 (en) * | 2010-10-15 | 2013-02-26 | Roche Diagnostics Operations, Inc. | Blood glucose test instrument kit having modular component parts |
US20120096451A1 (en) * | 2010-10-15 | 2012-04-19 | Roche Diagnostics Operations, Inc. | Firmware update in a medical device with multiple processors |
US20130211854A1 (en) * | 2010-10-26 | 2013-08-15 | Lantronix, Inc. | Decoding, Model and Presentation System |
US10201296B2 (en) | 2010-11-11 | 2019-02-12 | Ascensia Diabetes Care Holdings Ag | Apparatus, systems, and methods adapted to transmit analyte data having common electronic architecture |
US20120157795A1 (en) * | 2010-12-15 | 2012-06-21 | Ross Medical Corporation | Patient Emergency Response System |
TWI536195B (en) * | 2011-03-02 | 2016-06-01 | 緯創資通股份有限公司 | Devices and methods for receiving a physiological signal |
US9009455B2 (en) * | 2011-05-03 | 2015-04-14 | Western Digital Technologies, Inc. | Booting from a secondary storage device in order to accumulate disk drive performance data |
EP4122384A1 (en) | 2011-06-16 | 2023-01-25 | Abbott Diabetes Care, Inc. | Temperature-compensated analyte monitoring devices, systems, and methods thereof |
WO2013002122A1 (en) * | 2011-06-28 | 2013-01-03 | Fukutome Toshifumi | Program and storage medium for storing patient information |
US8977727B2 (en) | 2011-08-02 | 2015-03-10 | Roche Diagnostics Operations, Inc. | Remote configuration and selective distribution of product content to medical devices |
US8893109B2 (en) | 2011-08-02 | 2014-11-18 | Roche Diagnostics Operations, Inc. | Software distribution amongst medical devices taking into account dependencies between devices |
US8806473B2 (en) | 2011-08-02 | 2014-08-12 | Roche Diagnostics Operations, Inc. | Managing software distribution for regulatory compliance |
US9565156B2 (en) | 2011-09-19 | 2017-02-07 | Microsoft Technology Licensing, Llc | Remote access to a mobile communication device over a wireless local area network (WLAN) |
US9247004B2 (en) * | 2011-10-25 | 2016-01-26 | Vital Connect, Inc. | System and method for reliable and scalable health monitoring |
EP2775918B1 (en) | 2011-11-07 | 2020-02-12 | Abbott Diabetes Care Inc. | Analyte monitoring device and methods |
US9172583B1 (en) * | 2011-11-22 | 2015-10-27 | Crimson Corporation | Actively provisioning a managed node |
US8669863B2 (en) * | 2012-01-03 | 2014-03-11 | Fahad M. F. S. Alhuwaishel | Medical information band |
ITVI20120034A1 (en) * | 2012-02-09 | 2013-08-10 | Bentel Security S R L | DEVICE AND METHOD FOR THE MANAGEMENT OF ELECTRONIC BUILDING INSTALLATIONS |
CN102599899B (en) * | 2012-03-16 | 2014-03-19 | 姚国康 | Heart-rate monitoring method based on mobile phone |
US8874379B2 (en) | 2012-04-05 | 2014-10-28 | Welch Allyn, Inc. | Central station integration of patient data |
US9381297B2 (en) | 2012-06-07 | 2016-07-05 | Tandem Diabetes Care, Inc. | Sealed infusion device with electrical connector port |
US9921208B2 (en) | 2012-07-26 | 2018-03-20 | Ascensia Diabetes Care Holdings Ag | Apparatus and methods for reducing electrical shock hazard from biosensor meters |
US9968306B2 (en) | 2012-09-17 | 2018-05-15 | Abbott Diabetes Care Inc. | Methods and apparatuses for providing adverse condition notification with enhanced wireless communication range in analyte monitoring systems |
US9736210B2 (en) * | 2012-10-01 | 2017-08-15 | Dexcom, Inc. | Analyte data retriever |
US20150264513A1 (en) * | 2012-10-09 | 2015-09-17 | Google Inc. | Usb audio and power transmission |
US9659488B2 (en) * | 2012-12-17 | 2017-05-23 | Itron, Inc. | Metrology with universal serial bus (USB) connection |
KR102037416B1 (en) * | 2012-12-17 | 2019-10-28 | 삼성전자주식회사 | Method for managing of external devices, method for operating of an external device, host device, management server, and the external device |
US10888662B2 (en) * | 2013-01-15 | 2021-01-12 | Sanofi-Aventis Deutschland Gmbh | Apparatus for recording information concerning the use of an injection device |
US9439567B2 (en) * | 2013-02-06 | 2016-09-13 | Abraham Carter | Updating firmware to customize the performance of a wearable sensor device for a particular use |
CN111024955A (en) * | 2013-03-12 | 2020-04-17 | 豪夫迈·罗氏有限公司 | Method and hand-held glucose meter for transmitting glucose measurements |
CA2902634C (en) | 2013-03-14 | 2023-01-10 | Smith & Nephew Inc. | Systems and methods for applying reduced pressure therapy |
US9737649B2 (en) | 2013-03-14 | 2017-08-22 | Smith & Nephew, Inc. | Systems and methods for applying reduced pressure therapy |
US9215075B1 (en) | 2013-03-15 | 2015-12-15 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US9242043B2 (en) | 2013-03-15 | 2016-01-26 | Tandem Diabetes Care, Inc. | Field update of an ambulatory infusion pump system |
US9830673B2 (en) * | 2013-04-26 | 2017-11-28 | Roche Diabetes Care, Inc. | System portal control for a diabetes management system |
CA2915615A1 (en) * | 2013-05-10 | 2014-11-13 | Amiigo, Inc. | Platform for generating sensor data |
CN103309709B (en) * | 2013-06-08 | 2018-10-09 | 华为终端有限公司 | A kind of firmware upgrade method, device and communication equipment |
US20150050678A1 (en) * | 2013-08-13 | 2015-02-19 | Lifescan Scotland Limited | Modular analytical test meter |
JP6673835B2 (en) * | 2013-10-25 | 2020-03-25 | アセンシア・ダイアベティス・ケア・ホールディングス・アーゲーAscensia Diabetes Care Holdings AG | Hardware key system for device protection |
US20160334385A1 (en) * | 2014-01-10 | 2016-11-17 | Ascensia Diabetes Care Holdings Ag | Methods and apparatus for representing blood glucose variation graphically |
WO2015105612A1 (en) | 2014-01-10 | 2015-07-16 | Bayer Healthcare Llc | Setup synchronization apparatus and methods for end user medical devices |
US9904765B2 (en) * | 2014-01-13 | 2018-02-27 | Carefusion 303, Inc. | Monitoring medical device states to determine update timing |
WO2015118629A1 (en) * | 2014-02-05 | 2015-08-13 | 三菱電機株式会社 | Communications device, communications method, and program |
CN106461638A (en) | 2014-04-11 | 2017-02-22 | 安晟信医疗科技控股公司 | Wireless transmitter adapters for battery-operated biosensor meters and methods of providing same |
JP6373657B2 (en) * | 2014-06-27 | 2018-08-15 | 吉田 一雄 | Watch system |
US10306444B2 (en) | 2014-07-07 | 2019-05-28 | Ascensia Diabetes Care Holdings Ag | Device pairing with a dual use piezoelectric acoustic component and vibration sensor |
US11598763B2 (en) * | 2014-08-11 | 2023-03-07 | Ascensia Diabetes Care Holdings Ag | Reconfigurable measurement system |
EP3192023A1 (en) * | 2014-09-10 | 2017-07-19 | Ascensia Diabetes Care Holdings AG | Smart logging for management of health-related issues |
RU2705053C2 (en) * | 2014-09-15 | 2019-11-01 | Ф.Хоффманн-Ля Рош Аг | Method of generating control signal using monitoring means or security module |
US10061833B2 (en) * | 2014-09-25 | 2018-08-28 | Senslytics Corporation | Data insight and intuition system for tank storage |
US11107574B2 (en) * | 2014-09-30 | 2021-08-31 | Baxter Corporation Englewood | Management of medication preparation with formulary management |
US20180011973A1 (en) * | 2015-01-28 | 2018-01-11 | Os - New Horizons Personal Computing Solutions Ltd. | An integrated mobile personal electronic device and a system to securely store, measure and manage users health data |
CN107209803A (en) | 2015-02-10 | 2017-09-26 | 德克斯康公司 | System and method for being distributed continuous glucose data |
EP3289534A1 (en) * | 2015-04-29 | 2018-03-07 | Ascensia Diabetes Care Holdings AG | Location-based wireless diabetes management systems, methods and apparatus |
CN104887206A (en) * | 2015-05-26 | 2015-09-09 | 陆聪 | Intelligent wearable device system |
US10185513B1 (en) | 2015-06-05 | 2019-01-22 | Life365, Inc. | Device configured for dynamic software change |
US9974492B1 (en) | 2015-06-05 | 2018-05-22 | Life365, Inc. | Health monitoring and communications device |
US10560135B1 (en) | 2015-06-05 | 2020-02-11 | Life365, Inc. | Health, wellness and activity monitor |
US11329683B1 (en) | 2015-06-05 | 2022-05-10 | Life365, Inc. | Device configured for functional diagnosis and updates |
US9836296B2 (en) * | 2015-06-11 | 2017-12-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and systems for providing updates to and receiving data from devices having short range wireless communication capabilities |
WO2017007795A1 (en) * | 2015-07-07 | 2017-01-12 | Intuitive Surgical Operations, Inc. | Control of multiple devices |
SI3138489T1 (en) * | 2015-09-02 | 2020-10-30 | F. Hoffmann-La Roche Ag | Kit for determining an analyte concentration |
BR112018005503A2 (en) * | 2015-09-23 | 2018-10-09 | Koninklijke Philips N.V. | Modular pulse oximeter platform with interchangeable modules for patient use and method for operating a modular pulse oximeter platform with interchangeable modules for patient use |
CN108292529A (en) | 2015-10-07 | 2018-07-17 | 史密夫和内修有限公司 | System and method for application decompression treatment |
ITUB20155775A1 (en) * | 2015-11-20 | 2017-05-20 | Inno Tech S R L S | QUICK PROTOTYPING SYSTEM |
JP6720465B2 (en) * | 2016-01-14 | 2020-07-08 | オプテックス株式会社 | Portable information terminal, control method for portable information terminal, and control program |
US11797706B2 (en) | 2016-02-09 | 2023-10-24 | Health2047, Inc. | Mobile device network traffic modification and user based restrictions on data access |
US10541987B2 (en) | 2016-02-26 | 2020-01-21 | Tandem Diabetes Care, Inc. | Web browser-based device communication workflow |
US10346406B2 (en) * | 2016-03-28 | 2019-07-09 | International Business Machines Corporation | Decentralized autonomous edge compute coordinated by smart contract on a blockchain |
US10810084B2 (en) * | 2016-04-01 | 2020-10-20 | Intel Corporation | Update failure rebooting and recovery for a smart device |
KR101898569B1 (en) * | 2016-05-10 | 2018-09-13 | 주식회사 스마티랩 | Internet of things based health monitoring and assessment system |
CN109155019A (en) | 2016-05-13 | 2019-01-04 | 皇家飞利浦有限公司 | For tracking the system and method unofficially observed by caregiver about nursing recipient |
EP3454917B1 (en) | 2016-05-13 | 2022-04-06 | Smith & Nephew, Inc | Automatic wound coupling detection in negative pressure wound therapy systems |
US11062798B2 (en) * | 2016-06-07 | 2021-07-13 | Aseko, Inc. | Managing insulin administration |
EP3363349A1 (en) * | 2016-08-25 | 2018-08-22 | seca ag | Measuring device for determining physiological values of a patient and sensor unit |
JP6638610B2 (en) * | 2016-09-20 | 2020-01-29 | 株式会社島津製作所 | Mobile X-ray equipment |
WO2018064077A2 (en) | 2016-09-29 | 2018-04-05 | Smith & Nephew, Inc. | Construction and protection of components in negative pressure wound therapy systems |
EP3327596A1 (en) * | 2016-11-23 | 2018-05-30 | F. Hoffmann-La Roche AG | Supplementing measurement results of automated analyzers |
CN108271093B (en) * | 2016-12-30 | 2019-12-17 | 维沃移动通信有限公司 | Processing method of access equipment and mobile terminal |
CN110545766A (en) | 2017-03-07 | 2019-12-06 | 史密夫和内修有限公司 | Reduced pressure treatment systems and methods including antennas |
US11712508B2 (en) | 2017-07-10 | 2023-08-01 | Smith & Nephew, Inc. | Systems and methods for directly interacting with communications module of wound therapy apparatus |
CN107870237A (en) * | 2017-08-29 | 2018-04-03 | 苏州荣磐医疗科技有限公司 | A kind of blood glucose meter |
CN107871146A (en) * | 2017-10-20 | 2018-04-03 | 柴建霖 | A kind of high-tension apparatus partial discharge electrification detection intelligent management system based on Internet of Things |
CN108039202B (en) * | 2017-11-29 | 2021-12-10 | 上海联影医疗科技股份有限公司 | Correction table upgrading method, medical image reconstruction method and system |
WO2019122139A1 (en) | 2017-12-20 | 2019-06-27 | Rhodia Operations | High heat resistance polyamide molding compound |
US11056244B2 (en) * | 2017-12-28 | 2021-07-06 | Cilag Gmbh International | Automated data scaling, alignment, and organizing based on predefined parameters within surgical networks |
CN108362831A (en) * | 2018-01-18 | 2018-08-03 | 深圳市可飞科技有限公司 | Atmospheric components detection device |
CN108732353A (en) * | 2018-03-14 | 2018-11-02 | 重庆唐晟宝科技有限公司 | Blood glucose early warning system and method |
CN110941401A (en) * | 2018-09-25 | 2020-03-31 | 北京京东尚科信息技术有限公司 | Printing method and device |
JP2022506114A (en) * | 2018-10-23 | 2022-01-17 | イーノシックス、インコーポレイテッド | Microcomponents for data integration and methods of data integration |
GB201820668D0 (en) | 2018-12-19 | 2019-01-30 | Smith & Nephew Inc | Systems and methods for delivering prescribed wound therapy |
WO2020160326A1 (en) * | 2019-01-30 | 2020-08-06 | The Regents Of The University Of Colorado, A Body Corporate | Health sticker: a modular adhesive platform monitoring vital signals |
CN109884040A (en) * | 2019-02-12 | 2019-06-14 | 深圳市象形字科技股份有限公司 | A kind of urine detection method based on image recognition and OTG technology |
US11526619B2 (en) * | 2019-06-28 | 2022-12-13 | Bank Of America Corporation | System for securing and allowing access to electronic data in a data storage container |
US11275574B2 (en) * | 2020-02-03 | 2022-03-15 | Dell Products L.P. | Recovering the last successful device update on a computing system |
US11361354B2 (en) * | 2020-04-27 | 2022-06-14 | Swiftly Systems, Inc. | Method, computer-readable non-transitory storage media, and system for distributing and updating product catalogs to wireless devices |
US20210343378A1 (en) * | 2020-05-01 | 2021-11-04 | Axion Partners Llc | Medical status personal device |
US11631493B2 (en) | 2020-05-27 | 2023-04-18 | View Operating Corporation | Systems and methods for managing building wellness |
TWI771697B (en) * | 2020-06-12 | 2022-07-21 | 佳易科技股份有限公司 | Memory card device with a data upload function and a data upload method applied thereto |
DE102020118234A1 (en) | 2020-07-10 | 2022-01-13 | Testo SE & Co. KGaA | measuring device |
RU2746667C1 (en) * | 2020-07-29 | 2021-04-19 | Вадим Валерьевич Ганин | Complex and method for remote pre-trip inspection and waybill formation |
CN114358212B (en) * | 2022-01-25 | 2024-01-30 | 电子科技大学 | Cancer prescriptions index data analysis system based on K-means |
CN114947835A (en) * | 2022-04-25 | 2022-08-30 | 山东第一医科大学附属省立医院(山东省立医院) | Blood glucose analysis system fusing BGM and CGM data |
Family Cites Families (292)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3578405A (en) | 1968-07-22 | 1971-05-11 | Texaco Inc | Method and apparatus for analysis of fluid mixtures |
US4215275A (en) | 1977-12-07 | 1980-07-29 | Luxtron Corporation | Optical temperature measurement technique utilizing phosphors |
FR2510254A1 (en) | 1981-07-21 | 1983-01-28 | Guillaume Michel | METHOD AND DEVICE FOR MEASURING TEMPERATURE USING A DIFFRACTION NETWORK |
US4482261A (en) | 1982-07-15 | 1984-11-13 | Owens-Corning Fiberglas Corporation | Method for simultaneous reference junction compensation of a plurality of thermocouples |
US5001656A (en) | 1984-09-04 | 1991-03-19 | Chrysler Corporation | Ambient temperature monitoring technique |
US4718777A (en) | 1986-02-28 | 1988-01-12 | John Fluke Mfg. Co., Inc. | Isothermal block for temperature measurement system using a thermocouple |
US4935345A (en) | 1987-04-07 | 1990-06-19 | Arizona Board Of Regents | Implantable microelectronic biochemical sensor incorporating thin film thermopile |
US4741476A (en) | 1987-07-07 | 1988-05-03 | Honeywell Inc. | Digital electronic thermostat with correction for triac self heating |
US4836442A (en) | 1988-12-14 | 1989-06-06 | Honeywell Inc. | Compensation circuit for sensor lag to reduce undershoot and overshoot |
US5304405A (en) | 1991-01-11 | 1994-04-19 | Anelva Corporation | Thin film deposition method and apparatus |
ES2164641T3 (en) | 1991-02-27 | 2002-03-01 | Roche Diagnostics Corp | COMMUNICATION METHOD WITH INSTRUMENTS CONTROLLED BY MICROCOMPUTER. |
US6063233A (en) | 1991-06-27 | 2000-05-16 | Applied Materials, Inc. | Thermal control apparatus for inductively coupled RF plasma reactor having an overhead solenoidal antenna |
US5199637A (en) | 1992-05-05 | 1993-04-06 | Honeywell Inc. | Electronic thermostat having correction for internally generated heat from load switching |
US5899855A (en) | 1992-11-17 | 1999-05-04 | Health Hero Network, Inc. | Modular microprocessor-based health monitoring system |
US5307263A (en) | 1992-11-17 | 1994-04-26 | Raya Systems, Inc. | Modular microprocessor-based health monitoring system |
US20010011224A1 (en) | 1995-06-07 | 2001-08-02 | Stephen James Brown | Modular microprocessor-based health monitoring system |
US5304495A (en) | 1992-12-29 | 1994-04-19 | Abbott Laboratories | Method for determining flush interference in measurement of chemical and physical parameters with indwelling probe |
US5405511A (en) | 1993-06-08 | 1995-04-11 | Boehringer Mannheim Corporation | Biosensing meter with ambient temperature estimation method and system |
US5704366A (en) * | 1994-05-23 | 1998-01-06 | Enact Health Management Systems | System for monitoring and reporting medical measurements |
US5626139A (en) | 1994-09-23 | 1997-05-06 | Artech Industries, Inc. | Tympanic thermometer |
US20010044588A1 (en) | 1996-02-22 | 2001-11-22 | Mault James R. | Monitoring system |
JP3588920B2 (en) * | 1996-07-04 | 2004-11-17 | 株式会社日立製作所 | Community health information system |
JPH1055398A (en) * | 1996-08-08 | 1998-02-24 | Seiko Epson Corp | Information equipment for health control and health control system |
US5972715A (en) | 1996-12-23 | 1999-10-26 | Bayer Corporation | Use of thermochromic liquid crystals in reflectometry based diagnostic methods |
US6360244B1 (en) | 1997-04-11 | 2002-03-19 | Fujitsu Limited | System and method for multi-level memory domain protection |
US6391645B1 (en) | 1997-05-12 | 2002-05-21 | Bayer Corporation | Method and apparatus for correcting ambient temperature effect in biosensors |
US6066243A (en) | 1997-07-22 | 2000-05-23 | Diametrics Medical, Inc. | Portable immediate response medical analyzer having multiple testing modules |
US6144922A (en) | 1997-10-31 | 2000-11-07 | Mercury Diagnostics, Incorporated | Analyte concentration information collection and communication system |
EP1025530A2 (en) * | 1997-10-31 | 2000-08-09 | Amira Medical | Analyte concentration information collection and communication s ystem |
NZ524205A (en) | 1997-12-04 | 2004-05-28 | Roche Diagnostics Corp | Key mounting for biological measurement instrument |
US7390667B2 (en) | 1997-12-22 | 2008-06-24 | Roche Diagnostics Operations, Inc. | System and method for analyte measurement using AC phase angle measurements |
US7407811B2 (en) | 1997-12-22 | 2008-08-05 | Roche Diagnostics Operations, Inc. | System and method for analyte measurement using AC excitation |
US7494816B2 (en) | 1997-12-22 | 2009-02-24 | Roche Diagnostic Operations, Inc. | System and method for determining a temperature during analyte measurement |
AU738325B2 (en) | 1997-12-22 | 2001-09-13 | Roche Diagnostics Operations Inc. | Meter |
US6151606A (en) * | 1998-01-16 | 2000-11-21 | Visto Corporation | System and method for using a workspace data manager to access, manipulate and synchronize network data |
US6141683A (en) * | 1998-01-30 | 2000-10-31 | Lucent Technologies, Inc. | Method for remotely and reliably updating of the software on a computer with provision for roll back |
US6718547B2 (en) * | 1998-02-17 | 2004-04-06 | Fuji Photo Film Co., Ltd. | Medical network system |
US6068400A (en) | 1998-02-27 | 2000-05-30 | Tektronix, Inc. | Temperature compensated adapter for a DMM |
US7542878B2 (en) | 1998-03-03 | 2009-06-02 | Card Guard Scientific Survival Ltd. | Personal health monitor and a method for health monitoring |
DE19810802A1 (en) * | 1998-03-12 | 1999-09-16 | Ericsson Telefon Ab L M | Software processing device with software actualization function |
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 |
US6175752B1 (en) | 1998-04-30 | 2001-01-16 | Therasense, Inc. | Analyte monitoring device and methods of use |
US6949816B2 (en) | 2003-04-21 | 2005-09-27 | Motorola, Inc. | Semiconductor component having first surface area for electrically coupling to a semiconductor chip and second surface area for electrically coupling to a substrate, and method of manufacturing same |
DE69910003T2 (en) | 1998-05-13 | 2004-04-22 | Cygnus, Inc., Redwood City | MONITORING PHYSIOLOGICAL ANALYSIS |
DE69914319T2 (en) | 1998-05-13 | 2004-11-18 | Cygnus, Inc., Redwood City | SIGNAL PROCESSING FOR MEASURING PHYSIOLOGICAL ANALYSTS |
EP1460516B1 (en) | 1998-07-31 | 2008-05-07 | Abbott Laboratories | Docking station for receiving a hand-held analyte test instrument |
US6558320B1 (en) | 2000-01-20 | 2003-05-06 | Medtronic Minimed, Inc. | Handheld personal data assistant (PDA) with a medical device and method of using the same |
US6283628B1 (en) | 1998-09-11 | 2001-09-04 | Airpax Corporation, Llc | Intelligent input/output temperature sensor and calibration method therefor |
US6131096A (en) * | 1998-10-05 | 2000-10-10 | Visto Corporation | System and method for updating a remote database in a network |
TW460689B (en) | 1998-10-07 | 2001-10-21 | Gen Electric | Fluid analyte measurement system |
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 |
JP3668382B2 (en) | 1998-11-19 | 2005-07-06 | テルモ株式会社 | Component measuring device |
US6301709B1 (en) * | 1998-11-30 | 2001-10-09 | Lucent Technologies, Inc. | Circuit pack system with semi-or fully-automatic upgrade capability |
US6238085B1 (en) | 1998-12-31 | 2001-05-29 | Honeywell International Inc. | Differential thermal analysis sensor |
ATE394989T1 (en) * | 1999-03-29 | 2008-05-15 | Beckman Coulter Inc | MEASURING DEVICE WITH INTEGRATED DATABASE AND SIMPLIFIED TELEMEDICINE CAPABILITY |
JP2001043073A (en) * | 1999-08-02 | 2001-02-16 | Nippon Telegr & Teleph Corp <Ntt> | Software changing method of communication equipment, and communication equipment |
US7028114B1 (en) * | 1999-08-11 | 2006-04-11 | Henry Milan | Universal serial bus hub with wireless communication to remote peripheral device |
CA2385573A1 (en) * | 1999-09-24 | 2001-04-26 | John Sanderson | Physiological monitor and associated computation, display and communication unit |
US6293700B1 (en) | 1999-09-24 | 2001-09-25 | Fluke Corporation | Calibrated isothermal assembly for a thermocouple thermometer |
DE19952215C2 (en) | 1999-10-29 | 2001-10-31 | Roche Diagnostics Gmbh | Test element analysis system |
US6602191B2 (en) * | 1999-12-17 | 2003-08-05 | Q-Tec Systems Llp | Method and apparatus for health and disease management combining patient data monitoring with wireless internet connectivity |
US7060031B2 (en) * | 1999-12-17 | 2006-06-13 | Medtronic, Inc. | Method and apparatus for remotely programming implantable medical devices |
US7156809B2 (en) * | 1999-12-17 | 2007-01-02 | Q-Tec Systems Llc | Method and apparatus for health and disease management combining patient data monitoring with wireless internet connectivity |
US6976958B2 (en) * | 2000-12-15 | 2005-12-20 | Q-Tec Systems Llc | Method and apparatus for health and disease management combining patient data monitoring with wireless internet connectivity |
US6780296B1 (en) | 1999-12-23 | 2004-08-24 | Roche Diagnostics Corporation | Thermally conductive sensor |
US7286894B1 (en) * | 2000-01-07 | 2007-10-23 | Pasco Scientific | Hand-held computer device and method for interactive data acquisition, analysis, annotation, and calibration |
US7483743B2 (en) * | 2000-01-11 | 2009-01-27 | Cedars-Sinai Medical Center | System for detecting, diagnosing, and treating cardiovascular disease |
JP4602502B2 (en) * | 2000-01-31 | 2010-12-22 | 株式会社デンソー | Card type telephone system, IC card and card type telephone apparatus |
US6728787B1 (en) * | 2000-03-31 | 2004-04-27 | Mitsubishi Electric Research Labs, Inc | System and method for locating and installing device drivers for peripheral devices |
US20030036683A1 (en) | 2000-05-01 | 2003-02-20 | Kehr Bruce A. | Method, system and computer program product for internet-enabled, patient monitoring system |
IT1314759B1 (en) | 2000-05-08 | 2003-01-03 | Menarini Farma Ind | INSTRUMENTATION FOR MEASUREMENT AND CONTROL OF THE CONTENT OF GLUCOSIOLACTATE OR OTHER METABOLITES IN BIOLOGICAL FLUIDS |
JP2001319193A (en) * | 2000-05-09 | 2001-11-16 | Jsk Sinapusu:Kk | Reader-writer |
US20040172427A1 (en) * | 2000-05-16 | 2004-09-02 | Thomas Trent M. | Self-contained application disk for automatically launching application software or starting devices and peripherals |
WO2001093557A1 (en) * | 2000-05-31 | 2001-12-06 | Arkray, Inc. | Remote data control system and measuring data gathering method |
EP1662989B1 (en) | 2000-06-16 | 2014-09-03 | BodyMedia, Inc. | System for monitoring and managing body weight and other physiological conditions including iterative and personalized planning, intervention and reporting capability |
WO2001097686A1 (en) * | 2000-06-22 | 2001-12-27 | Fridolin Voegeli | System for maintenance and management of health |
DE10032015A1 (en) | 2000-07-01 | 2002-01-10 | Roche Diagnostics Gmbh | Test strip analysis unit for bodily fluid, employs temperature history correction system which will not drain batteries |
US20030172135A1 (en) | 2000-09-01 | 2003-09-11 | Mark Bobick | System, method, and data structure for packaging assets for processing and distribution on multi-tiered networks |
US7447643B1 (en) * | 2000-09-21 | 2008-11-04 | Theradoc.Com, Inc. | Systems and methods for communicating between a decision-support system and one or more mobile information devices |
JP4504579B2 (en) * | 2000-10-03 | 2010-07-14 | オリンパス株式会社 | Electronic camera |
WO2002049509A2 (en) * | 2000-12-21 | 2002-06-27 | Insulet Corporation | Medical apparatus remote control and method |
US7165109B2 (en) | 2001-01-12 | 2007-01-16 | Microsoft Corporation | Method and system to access software pertinent to an electronic peripheral device based on an address stored in a peripheral device |
US6907530B2 (en) * | 2001-01-19 | 2005-06-14 | V-One Corporation | Secure internet applications with mobile code |
US6993402B2 (en) * | 2001-02-28 | 2006-01-31 | Vigilanz Corporation | Method and system for identifying and anticipating adverse drug events |
US6898451B2 (en) | 2001-03-21 | 2005-05-24 | Minformed, L.L.C. | Non-invasive blood analyte measuring system and method utilizing optical absorption |
US8458689B2 (en) * | 2001-03-30 | 2013-06-04 | Roderick A. Barman | Method and apparatus for reprogramming engine controllers |
WO2002078512A2 (en) * | 2001-04-02 | 2002-10-10 | Therasense, Inc. | Blood glucose tracking apparatus and methods |
WO2002080762A1 (en) | 2001-04-06 | 2002-10-17 | Medic4All Inc. | A physiological monitoring system for a computational device of a human subject |
WO2002084484A2 (en) * | 2001-04-18 | 2002-10-24 | Domosys Corporation | Method of remotely upgrading firmware in field-deployed devices |
US20050009101A1 (en) | 2001-05-17 | 2005-01-13 | Motorola, Inc. | Microfluidic devices comprising biochannels |
EP1399059B1 (en) | 2001-05-18 | 2006-08-30 | Polymer Technology Systems, Inc. | Body fluid test apparatus with detachably mounted portable tester |
US7103578B2 (en) * | 2001-05-25 | 2006-09-05 | Roche Diagnostics Operations, Inc. | Remote medical device access |
WO2003001423A1 (en) | 2001-06-22 | 2003-01-03 | Arkray, Inc. | Information communication system |
US7160255B2 (en) | 2001-07-12 | 2007-01-09 | Vahid Saadat | Method and device for sensing and mapping temperature profile of a hollow body organ |
AU2002365071A1 (en) | 2001-08-06 | 2003-06-30 | Vanderbilt University | Device and methods for monitoring the status of at least one cell |
JP3775263B2 (en) | 2001-08-10 | 2006-05-17 | ニプロ株式会社 | Recording medium and blood glucose measurement system using the recording medium |
US6678542B2 (en) | 2001-08-16 | 2004-01-13 | Optiscan Biomedical Corp. | Calibrator configured for use with noninvasive analyte-concentration monitor and employing traditional measurements |
EP1559364A1 (en) | 2001-08-20 | 2005-08-03 | Inverness Medical Limited | Wireless diabetes management devices and methods for using the same |
SE0102918D0 (en) * | 2001-08-30 | 2001-08-30 | St Jude Medical | Method of providing software to an implantable medical device system |
RU2215471C2 (en) * | 2001-08-31 | 2003-11-10 | Кленов Сергей Иванович | Method of complex evaluation of man health state and device for method embodiment |
JP2003070771A (en) | 2001-09-07 | 2003-03-11 | Omron Corp | Equipment and system for organism information measurement and method of organism information measurement management |
KR20040045490A (en) | 2001-10-09 | 2004-06-01 | 코닌클리케 필립스 일렉트로닉스 엔.브이. | Device having touch sensitivity functionality |
US6989891B2 (en) | 2001-11-08 | 2006-01-24 | Optiscan Biomedical Corporation | Device and method for in vitro determination of analyte concentrations within body fluids |
US20030175806A1 (en) | 2001-11-21 | 2003-09-18 | Peter Rule | Method and apparatus for improving the accuracy of alternative site analyte concentration measurements |
AU2002346486A1 (en) | 2001-11-21 | 2003-06-10 | James R. Braig | Method for adjusting a blood analyte measurement |
EP1459251B1 (en) * | 2001-11-22 | 2008-08-13 | Liberate Software Limited | Portable storage device for storing and accessing personal data |
DE10159120B4 (en) | 2001-12-01 | 2006-08-17 | Lts Lohmann Therapie-Systeme Ag | Steroid hormone-containing transdermal therapeutic systems containing propylene glycol monocaprylate and its use |
US6725323B2 (en) * | 2001-12-06 | 2004-04-20 | Kabushiki Kaisha Toshiba | Apparatus and method for updating flash ROM in an electronic apparatus having a plurality of boards |
US7034691B1 (en) * | 2002-01-25 | 2006-04-25 | Solvetech Corporation | Adaptive communication methods and systems for facilitating the gathering, distribution and delivery of information related to medical care |
GB0205751D0 (en) * | 2002-03-12 | 2002-04-24 | James Barry E | Improvements relating to memory devices |
US7361830B2 (en) | 2002-03-21 | 2008-04-22 | Rtd Company | Polymer encapsulated micro-thermocouple |
US6866758B2 (en) | 2002-03-21 | 2005-03-15 | Roche Diagnostics Corporation | Biosensor |
US20030235817A1 (en) | 2002-03-22 | 2003-12-25 | Miroslaw Bartkowiak | Microprocessors, devices, and methods for use in analyte monitoring systems |
JP2003288225A (en) * | 2002-03-28 | 2003-10-10 | Anritsu Corp | Public communication terminal, terminal management device, and main program updating system |
JP2003302406A (en) * | 2002-04-05 | 2003-10-24 | Sony Corp | Self blood sugar measurement system and self-blood sugar measurement unit |
US6743635B2 (en) | 2002-04-25 | 2004-06-01 | Home Diagnostics, Inc. | System and methods for blood glucose sensing |
US8996090B2 (en) | 2002-06-03 | 2015-03-31 | Exostat Medical, Inc. | Noninvasive detection of a physiologic parameter within a body tissue of a patient |
GB0214303D0 (en) * | 2002-06-21 | 2002-07-31 | Koninkl Philips Electronics Nv | Server side configuration management |
JP2004030249A (en) | 2002-06-26 | 2004-01-29 | Moss Institute Co Ltd | System, apparatus, method, and program for clinical examination document management |
US7478235B2 (en) * | 2002-06-28 | 2009-01-13 | Microsoft Corporation | Methods and systems for protecting data in USB systems |
US7156109B2 (en) * | 2002-08-08 | 2007-01-02 | Sampson Mark A | Smoking cessation oral hygiene device |
JP2004096152A (en) * | 2002-08-29 | 2004-03-25 | Fuji Xerox Co Ltd | Processing apparatus |
US6836657B2 (en) * | 2002-11-12 | 2004-12-28 | Innopath Software, Inc. | Upgrading of electronic files including automatic recovery from failures and errors occurring during the upgrade |
JP4245374B2 (en) | 2002-11-01 | 2009-03-25 | 株式会社サスライト | Detachable device and control circuit |
CN1512173A (en) | 2002-12-26 | 2004-07-14 | 力捷电脑股份有限公司 | Blood sugar long term observation chart establishing method for helping self control of blood sugar value |
TWI317503B (en) * | 2002-12-31 | 2009-11-21 | Hon Hai Prec Ind Co Ltd | System and method for remote installation of application programs in mobile derices |
US20040132171A1 (en) | 2003-01-06 | 2004-07-08 | Peter Rule | Wearable device for measuring analyte concentration |
US6983177B2 (en) | 2003-01-06 | 2006-01-03 | Optiscan Biomedical Corporation | Layered spectroscopic sample element with microporous membrane |
US7644406B2 (en) * | 2003-01-21 | 2010-01-05 | Hewlett-Packard Development Company, L.P. | Update system capable of updating software across multiple FLASH chips |
US7338637B2 (en) | 2003-01-31 | 2008-03-04 | Hewlett-Packard Development Company, L.P. | Microfluidic device with thin-film electronic devices |
US7433712B2 (en) * | 2003-02-06 | 2008-10-07 | Modu Ltd. | Multi-access solid state memory devices and a telephone utilizing such |
JP2004261255A (en) * | 2003-02-28 | 2004-09-24 | Tanita Corp | Memory unit for biological information acquisition device and biological information acquisition device using the same |
US20060004974A1 (en) * | 2003-03-13 | 2006-01-05 | Paul Lin | Portable non-volatile memory device and method for preventing unauthorized access to data stored thereon |
US20040186746A1 (en) | 2003-03-21 | 2004-09-23 | Angst Wendy P. | System, apparatus and method for storage and transportation of personal health records |
US7171606B2 (en) * | 2003-03-25 | 2007-01-30 | Wegener Communications, Inc. | Software download control system, apparatus and method |
US7587287B2 (en) | 2003-04-04 | 2009-09-08 | Abbott Diabetes Care Inc. | Method and system for transferring analyte test data |
WO2004090661A2 (en) * | 2003-04-08 | 2004-10-21 | Medic4All A.G | A portable wireless gateway for remote medical examination |
US8088333B2 (en) | 2003-04-28 | 2012-01-03 | Invoy Technology, LLC | Thermoelectric sensor for analytes in a gas |
US8722417B2 (en) | 2003-04-28 | 2014-05-13 | Invoy Technologies, L.L.C. | Thermoelectric sensor for analytes in a fluid and related method |
US20060229502A1 (en) | 2003-06-03 | 2006-10-12 | Bayer Healthcare Llc | Portable medical diagnostic apparatus |
US20070025877A1 (en) | 2003-06-03 | 2007-02-01 | Hansen Christian M | User interface for portable medical diagnostic apparatus and method of using the same |
US8066639B2 (en) | 2003-06-10 | 2011-11-29 | Abbott Diabetes Care Inc. | Glucose measuring device for use in personal area network |
US7597793B2 (en) | 2003-06-20 | 2009-10-06 | Roche Operations Ltd. | System and method for analyte measurement employing maximum dosing time delay |
US7452457B2 (en) | 2003-06-20 | 2008-11-18 | Roche Diagnostics Operations, Inc. | System and method for analyte measurement using dose sufficiency electrodes |
US20070264721A1 (en) | 2003-10-17 | 2007-11-15 | Buck Harvey B | System and method for analyte measurement using a nonlinear sample response |
US7488601B2 (en) | 2003-06-20 | 2009-02-10 | Roche Diagnostic Operations, Inc. | System and method for determining an abused sensor during analyte measurement |
US9529762B2 (en) | 2003-06-30 | 2016-12-27 | Becton, Dickinson And Company | Self powered serial-to-serial or USB-to-serial cable with loopback and isolation |
US20050055243A1 (en) * | 2003-06-30 | 2005-03-10 | Dave Arndt | Method and apparatus for managing data received from a medical device |
US20050021372A1 (en) * | 2003-07-25 | 2005-01-27 | Dimagi, Inc. | Interactive motivation systems and methods for self-care compliance |
US8200775B2 (en) | 2005-02-01 | 2012-06-12 | Newsilike Media Group, Inc | Enhanced syndication |
AU2003270322A1 (en) * | 2003-09-05 | 2005-04-21 | Itron, Inc. | Synchronizing and controlling software downloads, such as for utility meter-reading data collection and processing |
WO2005037095A1 (en) | 2003-10-14 | 2005-04-28 | Pelikan Technologies, Inc. | Method and apparatus for a variable user interface |
JP2005122402A (en) * | 2003-10-15 | 2005-05-12 | Systemneeds Inc | Ic card system |
US20050091359A1 (en) * | 2003-10-24 | 2005-04-28 | Microsoft Corporation | Systems and methods for projecting content from computing devices |
CN1287279C (en) * | 2003-11-14 | 2006-11-29 | 中兴通讯股份有限公司 | A method for downloading software from server side on client side in distributed system |
WO2005054992A2 (en) * | 2003-11-25 | 2005-06-16 | Cordis Corporation | Medical device radiofrequency identification system and method |
US20050148003A1 (en) | 2003-11-26 | 2005-07-07 | Steven Keith | Methods of correcting a luminescence value, and methods of determining a corrected analyte concentration |
US20050132351A1 (en) * | 2003-12-12 | 2005-06-16 | Randall Roderick K. | Updating electronic device software employing rollback |
CN1791102B (en) * | 2003-12-18 | 2010-12-29 | 腾讯科技(深圳)有限公司 | Network download tool |
WO2005083988A1 (en) * | 2004-02-23 | 2005-09-09 | Dyna Llc | Systems and methods for enhancing the provisioning and functionality of wireless instruments |
US7142848B2 (en) * | 2004-02-26 | 2006-11-28 | Research In Motion Limited | Method and system for automatically configuring access control |
JP2005245669A (en) * | 2004-03-03 | 2005-09-15 | Tanita Corp | Body composition information acquisition system |
WO2005093629A2 (en) | 2004-03-26 | 2005-10-06 | Novo Nordisk A/S | Device for displaying data relevant for a diabetic patient |
KR101228356B1 (en) * | 2004-04-08 | 2013-02-05 | 바이오매트리카 인코포레이티드 | Integration of sample storage and sample management for life science |
US7904608B2 (en) * | 2004-05-04 | 2011-03-08 | Price Robert M | System and method for updating software in electronic devices |
WO2005108968A1 (en) | 2004-05-12 | 2005-11-17 | Matsushita Electric Industrial Co., Ltd. | Biosensor, container for biosensor, and biosensor measuring apparatus |
WO2005119555A2 (en) | 2004-06-01 | 2005-12-15 | Lifescan, Inc. | Methods and systems of automating medical device data management |
CA3090413C (en) | 2004-06-04 | 2023-10-10 | Abbott Diabetes Care Inc. | Glucose monitoring and graphical representations in a data management system |
US20060005264A1 (en) * | 2004-06-10 | 2006-01-05 | Lin H M C | Computer security system |
US7590522B2 (en) | 2004-06-14 | 2009-09-15 | Hewlett-Packard Development Company, L.P. | Virtual mass storage device for server management information |
US20060001538A1 (en) | 2004-06-30 | 2006-01-05 | Ulrich Kraft | Methods of monitoring the concentration of an analyte |
WO2006003181A2 (en) | 2004-07-01 | 2006-01-12 | Novo Nordisk A/S | Method and drug administration device for enchanced display of diary data |
US20060009684A1 (en) | 2004-07-07 | 2006-01-12 | Steven Kim | System for monitoring compliance to a healthcare regiment of testing |
US8027165B2 (en) * | 2004-07-08 | 2011-09-27 | Sandisk Technologies Inc. | Portable memory devices with removable caps that effect operation of the devices when attached |
JP4870915B2 (en) * | 2004-07-15 | 2012-02-08 | 株式会社日立製作所 | Storage device |
WO2006009199A1 (en) * | 2004-07-21 | 2006-01-26 | Matsushita Electric Industrial Co., Ltd. | Blood sugar level management system |
US7344500B2 (en) | 2004-07-27 | 2008-03-18 | Medtronic Minimed, Inc. | Sensing system with auxiliary display |
US8313433B2 (en) * | 2004-08-06 | 2012-11-20 | Medtronic Minimed, Inc. | Medical data management system and process |
US7460958B2 (en) | 2004-10-07 | 2008-12-02 | E.I. Du Pont De Nemours And Company | Computer-implemented system and method for analyzing mixtures of gases |
JP2006134080A (en) | 2004-11-05 | 2006-05-25 | Ntt Docomo Inc | Portable terminal, and individual adaptive context acquiring method |
EP1830693A1 (en) | 2004-11-23 | 2007-09-12 | Medical Digital Developers LLC | Medical media capture system and method |
GB2420659B (en) * | 2004-11-25 | 2006-10-11 | Simon Richard Daniel | Collapsible rechargeable battery assembly with integral connector |
JP2006155411A (en) * | 2004-11-30 | 2006-06-15 | Houken Corp | System, method, and program for constructing medical treatment prediction model, system, method, and program for verifying / offering medical treatment content, method of downloading health management data, and detachable storage medium |
US7712086B2 (en) * | 2004-12-15 | 2010-05-04 | Microsoft Corporation | Portable applications |
US20080133146A1 (en) | 2004-12-17 | 2008-06-05 | Chang Kc Shu Kun | Device Having a Trend-Indicating Display |
US7867716B2 (en) | 2004-12-21 | 2011-01-11 | The Texas A&M University System | High temperature ion channels and pores |
US7364353B2 (en) | 2005-01-26 | 2008-04-29 | Carrier Corporation | Dynamic correction of sensed temperature |
US7424327B2 (en) * | 2005-02-04 | 2008-09-09 | Rockwell Automation Technologies, Inc. | System and method for automatically matching programmable data of devices within an industrial control system |
US7311417B1 (en) * | 2005-02-22 | 2007-12-25 | Ocean Management Systems Inc. | Waterproof flashlight including electronic power switch actuated by a mechanical switch |
WO2006094171A1 (en) * | 2005-03-01 | 2006-09-08 | Masimo Laboratories, Inc. | Multiple wavelength sensor drivers |
US7243856B2 (en) * | 2005-03-24 | 2007-07-17 | Sandisk Il Ltd.. | Loading internal applications on a smartcard |
JP4598825B2 (en) | 2005-03-31 | 2010-12-15 | テルモ株式会社 | Puncture device and puncture tip |
EP1713206A1 (en) | 2005-04-11 | 2006-10-18 | Last Mile Communications/Tivis Limited | A distributed communications network comprising wirelessly linked base stations |
EP1722310A1 (en) | 2005-04-12 | 2006-11-15 | Roche Diagnostics GmbH | Medical software download to mobile phone |
DE602005003452T2 (en) | 2005-04-14 | 2008-03-06 | Agilent Technologies Inc., Santa Clara | Measuring device with measured data buffer |
US7964089B2 (en) | 2005-04-15 | 2011-06-21 | Agamatrix, Inc. | Analyte determination method and analyte meter |
JP4744921B2 (en) * | 2005-04-27 | 2011-08-10 | 三菱電機株式会社 | Software failure recovery system |
US20070143529A1 (en) * | 2005-04-28 | 2007-06-21 | Bacastow Steven V | Apparatus and method for PC security and access control |
TW200639732A (en) * | 2005-05-02 | 2006-11-16 | Acer Inc | Medicare management system and method used thereby |
US7467065B2 (en) * | 2005-05-02 | 2008-12-16 | Home Diagnostics, Inc. | Computer interface for diagnostic meter |
US7751533B2 (en) * | 2005-05-02 | 2010-07-06 | Nokia Corporation | Dynamic message templates and messaging macros |
US7945788B2 (en) * | 2005-05-03 | 2011-05-17 | Strong Bear L.L.C. | Removable drive with data encryption |
US8032705B2 (en) * | 2005-05-17 | 2011-10-04 | Kid Group Llc | Method and apparatus for providing games and content |
US20070033074A1 (en) | 2005-06-03 | 2007-02-08 | Medtronic Minimed, Inc. | Therapy management system |
EP1909097B1 (en) | 2005-06-06 | 2012-04-18 | Nikkiso Company Limited | Biosensor and biosensor cell |
US20070010721A1 (en) | 2005-06-28 | 2007-01-11 | Chen Thomas C H | Apparatus and system of Internet-enabled wireless medical sensor scale |
US20070004969A1 (en) | 2005-06-29 | 2007-01-04 | Microsoft Corporation | Health monitor |
DE102005030590B4 (en) * | 2005-06-30 | 2011-03-24 | Advanced Micro Devices, Inc., Sunnyvale | Safe patch system |
US20070022232A1 (en) * | 2005-07-20 | 2007-01-25 | Jvsd Technologies | Cellular telephone with integrated usb port engagement device that provides access to multimedia card as a solid-state device |
US7429920B2 (en) * | 2005-07-20 | 2008-09-30 | Cardiac Pacemakers, Inc. | Radio frequency identification and tagging for implantable medical devices and medical device systems |
CA2890945C (en) | 2005-07-20 | 2016-11-29 | Bayer Healthcare Llc | Gated amperometry |
US20070022233A1 (en) * | 2005-07-20 | 2007-01-25 | Lexmark International, Inc. | Document processing device with USB drive |
CN1745698A (en) * | 2005-07-21 | 2006-03-15 | 高春平 | Modular combined personal and digital healthy assistant device |
US8051414B2 (en) * | 2005-08-01 | 2011-11-01 | Siemens Aktiengesellschaft | Method and system for remote software updating of a medical device |
CN2840921Y (en) * | 2005-08-05 | 2006-11-29 | 创惟科技股份有限公司 | Portable integrated medical measuring device |
US7737581B2 (en) | 2005-08-16 | 2010-06-15 | Medtronic Minimed, Inc. | Method and apparatus for predicting end of battery life |
EP1758039A1 (en) | 2005-08-27 | 2007-02-28 | Roche Diagnostics GmbH | Communication adaptor for portable medical or therapeutical devices |
DE102005044483A1 (en) * | 2005-09-16 | 2007-03-29 | Electronic Thoma Gmbh | Transportable, configurable information carrier and method for this purpose |
US7802909B2 (en) * | 2005-09-20 | 2010-09-28 | Noble Marketing, Inc. | Multifunctional medical examination instrument |
US7760082B2 (en) * | 2005-09-21 | 2010-07-20 | Chon Meng Wong | System and method for active monitoring and diagnostics of life signs using heartbeat waveform and body temperature remotely giving the user freedom to move within its vicinity without wires attachment, gel, or adhesives |
US20100125646A1 (en) * | 2005-09-27 | 2010-05-20 | Ceedo Technologies (2005) Ltd | System For Enabling Host-Independent Software Portability Of A Self-Contained Device |
US20070165049A1 (en) * | 2005-10-14 | 2007-07-19 | General Electric Company | Configurable system and method for results review |
US7766829B2 (en) | 2005-11-04 | 2010-08-03 | Abbott Diabetes Care Inc. | Method and system for providing basal profile modification in analyte monitoring and management systems |
US20080281170A1 (en) * | 2005-11-08 | 2008-11-13 | Koninklijke Philips Electronics N.V. | Method for Detecting Critical Trends in Multi-Parameter Patient Monitoring and Clinical Data Using Clustering |
US20080015422A1 (en) | 2005-12-29 | 2008-01-17 | Guidance Interactive Healthcare, Inc. | Combined peripheral and health monitoring devices |
US9149215B2 (en) | 2005-12-30 | 2015-10-06 | Roche Diabetes Care, Inc. | Portable analytical device |
US20070152683A1 (en) | 2005-12-30 | 2007-07-05 | Karl Werner | Electronic device for analysis of a body fluid |
US20070198995A1 (en) | 2006-01-31 | 2007-08-23 | Richard Dellacona | System and method for automated delivery of software |
US20070177426A1 (en) | 2006-01-31 | 2007-08-02 | Richard Dellacona | System and method for automated delivery of software payload |
US20070185545A1 (en) | 2006-02-06 | 2007-08-09 | Medtronic Emergency Response Systems, Inc. | Post-download patient data protection in a medical device |
CA2577655C (en) * | 2006-02-14 | 2011-04-05 | Angstrom Power Incorporated | Fuel cell devices and method therefor |
WO2007100677A2 (en) | 2006-02-22 | 2007-09-07 | Vivum Nexus Llc | Method and device for analyte measurement |
CA2643163C (en) | 2006-02-27 | 2020-01-28 | Bayer Healthcare Llc | Temperature-adjusted analyte determination for biosensor systems |
US7653425B2 (en) | 2006-08-09 | 2010-01-26 | Abbott Diabetes Care Inc. | Method and system for providing calibration of an analyte sensor in an analyte monitoring system |
US7618369B2 (en) | 2006-10-02 | 2009-11-17 | Abbott Diabetes Care Inc. | Method and system for dynamically updating calibration parameters for an analyte sensor |
US7738264B2 (en) | 2006-03-31 | 2010-06-15 | Lifescan Scotland Ltd. | Devices and methods for protecting handheld electronic devices from electrostatic discharge |
US20070231846A1 (en) | 2006-04-03 | 2007-10-04 | Cosentino Daniel L | Glucose meter communication method and system |
US8696597B2 (en) * | 2006-04-03 | 2014-04-15 | Nipro Diagnostics, Inc. | Diagnostic meter |
US8770482B2 (en) | 2006-04-26 | 2014-07-08 | Roche Diagnostics Operations, Inc. | Apparatus and method to administer and manage an intelligent base unit for a handheld medical device |
US20070255126A1 (en) | 2006-04-28 | 2007-11-01 | Moberg Sheldon B | Data communication in networked fluid infusion systems |
US20070258395A1 (en) | 2006-04-28 | 2007-11-08 | Medtronic Minimed, Inc. | Wireless data communication protocols for a medical device network |
US20070253380A1 (en) | 2006-04-28 | 2007-11-01 | James Jollota | Data translation device with nonvolatile memory for a networked medical device system |
US7558622B2 (en) | 2006-05-24 | 2009-07-07 | Bao Tran | Mesh network stroke monitoring appliance |
CN100429667C (en) | 2006-05-15 | 2008-10-29 | 李永和 | Medical treatment data processing system and processing method |
US7539533B2 (en) * | 2006-05-16 | 2009-05-26 | Bao Tran | Mesh network monitoring appliance |
US20070276197A1 (en) * | 2006-05-24 | 2007-11-29 | Lifescan, Inc. | Systems and methods for providing individualized disease management |
US20080027288A1 (en) * | 2006-07-31 | 2008-01-31 | Jorg Renz | RFID enabled apparatus for monitoring a medical status and a method thereof |
US8149131B2 (en) * | 2006-08-03 | 2012-04-03 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US20080215360A1 (en) | 2006-10-24 | 2008-09-04 | Kent Dicks | Systems and methods for medical data interchange interface |
US8126734B2 (en) | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for adapter-based communication with a medical device |
US8126730B2 (en) | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for storage and forwarding of medical data |
US8126732B2 (en) | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for processing and transmittal of medical data through multiple interfaces |
US8579853B2 (en) * | 2006-10-31 | 2013-11-12 | Abbott Diabetes Care Inc. | Infusion devices and methods |
US7512743B2 (en) * | 2006-11-07 | 2009-03-31 | Spansion Llc | Using shared memory with an execute-in-place processor and a co-processor |
EP2086393A1 (en) * | 2006-11-23 | 2009-08-12 | Lifescan Scotland Limited | Blood glucose meter capable of wireless communication |
US20080121045A1 (en) | 2006-11-29 | 2008-05-29 | Cole Matthew C | Multiplexed sensor array |
US7740492B2 (en) * | 2006-12-21 | 2010-06-22 | Kingston Technology Corporation | Portable computer universal serial bus device with an extendable connector secured by multiple locking mechanisms |
US20080161666A1 (en) | 2006-12-29 | 2008-07-03 | Abbott Diabetes Care, Inc. | Analyte devices and methods |
US8601470B2 (en) | 2007-01-05 | 2013-12-03 | Moka5, Inc. | Symbiotic smart peripherals |
US20080234943A1 (en) | 2007-03-20 | 2008-09-25 | Pinaki Ray | Computer program for diabetes management |
US20080235053A1 (en) | 2007-03-20 | 2008-09-25 | Pinaki Ray | Communication medium for diabetes management |
US8758245B2 (en) | 2007-03-20 | 2014-06-24 | Lifescan, Inc. | Systems and methods for pattern recognition in diabetes management |
US20080249385A1 (en) | 2007-04-04 | 2008-10-09 | Luong Ngoc Phan | Isolated intravenous analyte monitoring system |
CA2683930A1 (en) | 2007-04-14 | 2008-10-23 | Abbott Diabetes Care Inc. | Method and apparatus for providing data processing and control in medical communication system |
CA2683959C (en) | 2007-04-14 | 2017-08-29 | Abbott Diabetes Care Inc. | Method and apparatus for providing data processing and control in medical communication system |
WO2008130898A1 (en) | 2007-04-14 | 2008-10-30 | Abbott Diabetes Care, Inc. | Method and apparatus for providing data processing and control in medical communication system |
ES2461090T3 (en) | 2007-04-14 | 2014-05-16 | Abbott Diabetes Care Inc. | Procedure and apparatus for providing data treatment and control in a medical communication system |
EP3741291A1 (en) | 2007-04-14 | 2020-11-25 | Abbott Diabetes Care, Inc. | Method and apparatus for providing data processing and control in medical communication system |
US7928850B2 (en) | 2007-05-08 | 2011-04-19 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods |
US8260558B2 (en) | 2007-05-14 | 2012-09-04 | Abbott Diabetes Care Inc. | Method and apparatus for providing data processing and control in a medical communication system |
US20080294024A1 (en) | 2007-05-24 | 2008-11-27 | Cosentino Daniel L | Glucose meter system and monitor |
US8151257B2 (en) * | 2007-05-29 | 2012-04-03 | Sap Ag | Managing different versions of server components regarding compatibility with collaborating servers |
ES2712778T3 (en) | 2007-05-30 | 2019-05-14 | Ascensia Diabetes Care Holdings Ag | Method and system to manage health data |
JP5680960B2 (en) | 2007-06-21 | 2015-03-04 | アボット ダイアベティス ケア インコーポレイテッドAbbott Diabetes Care Inc. | Health care device and method |
WO2009002622A2 (en) * | 2007-06-27 | 2008-12-31 | F. Hoffman-La Roche Ag | Patient information input interface for a therapy system |
EP2031527A1 (en) | 2007-07-27 | 2009-03-04 | Sensile Pat AG | Portable medical device |
EP3540741B1 (en) * | 2007-08-10 | 2022-10-26 | Smiths Medical ASD, Inc. | System for controlling medical devices |
JP4385306B2 (en) * | 2007-08-17 | 2009-12-16 | ソニー株式会社 | Information processing apparatus, information processing method, and information processing program |
US8105841B2 (en) | 2007-10-15 | 2012-01-31 | Bayer Healthcare Llc | Method and assembly for determining the temperature of a test sensor |
US8000918B2 (en) | 2007-10-23 | 2011-08-16 | Edwards Lifesciences Corporation | Monitoring and compensating for temperature-related error in an electrochemical sensor |
US20090118604A1 (en) | 2007-11-02 | 2009-05-07 | Edwards Lifesciences Corporation | Analyte monitoring system having back-up power source for use in either transport of the system or primary power loss |
US7581970B2 (en) * | 2007-11-16 | 2009-09-01 | Sony Ericsson Mobile Communications Ab | Multipurpose universal serial bus cable |
BRPI0820583A8 (en) | 2007-12-10 | 2015-09-22 | Bayer Healthcare Llc | fast charging and battery-powered fluid analyte power management |
JP5430555B2 (en) | 2008-03-27 | 2014-03-05 | パナソニック株式会社 | Ambient temperature measurement method, liquid sample measurement method, and measuring device for biosensor |
JP5487467B2 (en) | 2008-06-16 | 2014-05-07 | パナソニックヘルスケア株式会社 | Analytical object measuring method, biosensor and measuring instrument |
US20090319299A1 (en) * | 2008-06-20 | 2009-12-24 | Medidata Solutions, Inc. | System and techniques for reporting adverse effects |
CA2739091A1 (en) | 2008-10-03 | 2010-04-08 | Bayer Healthcare Llc | System and method for predicting ambient temperature in a fluid analyte meter |
EP2851676B1 (en) | 2008-12-18 | 2016-12-28 | Ascensia Diabetes Care Holdings AG | Test sensor with grating for determining the temperature of the sensor |
US8801273B2 (en) | 2009-06-08 | 2014-08-12 | Bayer Healthcare Llc | Method and assembly for determining the temperature of a test sensor |
WO2010151592A1 (en) | 2009-06-23 | 2010-12-29 | Bayer Healthcare Llc | System and apparatus for determining temperatures in a fluid analyte system |
TWI429225B (en) | 2009-11-16 | 2014-03-01 | Mstar Semiconductor Inc | Target signal determination method and associated apparatus |
US8893109B2 (en) * | 2011-08-02 | 2014-11-18 | Roche Diagnostics Operations, Inc. | Software distribution amongst medical devices taking into account dependencies between devices |
-
2008
- 2008-05-28 ES ES12182106T patent/ES2712778T3/en active Active
- 2008-05-28 ES ES08754798.0T patent/ES2693097T3/en active Active
- 2008-05-28 EP EP18206507.8A patent/EP3474283A1/en not_active Withdrawn
- 2008-05-28 EP EP12182106.0A patent/EP2535830B1/en active Active
- 2008-05-28 EP EP08754798.0A patent/EP2156348B1/en active Active
- 2008-05-29 MX MX2009012937A patent/MX2009012937A/en active IP Right Grant
- 2008-05-29 MX MX2009012936A patent/MX2009012936A/en active IP Right Grant
- 2008-05-29 US US12/129,562 patent/US8401873B2/en active Active
- 2008-05-29 CN CN2012101961952A patent/CN102841976A/en active Pending
- 2008-05-29 US US12/129,555 patent/US20080300919A1/en not_active Abandoned
- 2008-05-29 CA CA2997497A patent/CA2997497A1/en not_active Abandoned
- 2008-05-29 CN CN2008800236572A patent/CN101689228B/en active Active
- 2008-05-29 JP JP2010510343A patent/JP5721029B2/en active Active
- 2008-05-29 EP EP19157223.9A patent/EP3518243A1/en not_active Withdrawn
- 2008-05-29 CN CN201610659736.9A patent/CN106294245A/en active Pending
- 2008-05-29 BR BRPI0812315-2A2A patent/BRPI0812315A2/en not_active IP Right Cessation
- 2008-05-29 WO PCT/US2008/006812 patent/WO2008153825A2/en active Application Filing
- 2008-05-29 JP JP2010510344A patent/JP5629574B2/en active Active
- 2008-05-29 ES ES11177231T patent/ES2908754T3/en active Active
- 2008-05-29 CA CA2688046A patent/CA2688046C/en not_active Expired - Fee Related
- 2008-05-29 US US12/129,547 patent/US9618967B2/en active Active
- 2008-05-29 BR BRPI0812011-0A2A patent/BRPI0812011A2/en not_active IP Right Cessation
- 2008-05-29 CA CA2688123A patent/CA2688123C/en not_active Expired - Fee Related
- 2008-05-29 EP EP08754800A patent/EP2156349A1/en not_active Ceased
- 2008-05-29 EP EP12182104.5A patent/EP2557516B1/en active Active
- 2008-05-29 WO PCT/US2008/006814 patent/WO2008150428A1/en active Application Filing
- 2008-05-29 US US12/129,570 patent/US8978026B2/en active Active
- 2008-05-29 CN CN200880022843A patent/CN101689227A/en active Pending
- 2008-05-30 CL CL2008001599A patent/CL2008001599A1/en unknown
- 2008-05-30 TW TW103139822A patent/TWI552105B/en not_active IP Right Cessation
- 2008-05-30 TW TW104117537A patent/TWI544443B/en not_active IP Right Cessation
- 2008-05-30 TW TW097120333A patent/TWI466054B/en not_active IP Right Cessation
- 2008-05-30 TW TW105111551A patent/TW201627945A/en unknown
- 2008-05-30 AR ARP080102311A patent/AR066808A1/en unknown
- 2008-05-30 AR ARP080102308A patent/AR066805A1/en unknown
- 2008-05-30 TW TW097120331A patent/TWI493495B/en not_active IP Right Cessation
- 2008-05-30 CL CL2008001598A patent/CL2008001598A1/en unknown
-
2010
- 2010-06-09 HK HK10105698.2A patent/HK1139754A1/en not_active IP Right Cessation
-
2013
- 2013-03-09 US US13/792,009 patent/US9189598B2/en active Active
- 2013-05-24 RU RU2013123983A patent/RU2611019C2/en active
-
2015
- 2015-01-28 US US14/607,631 patent/US9471098B2/en active Active
- 2015-10-08 US US14/878,125 patent/US10347371B2/en active Active
-
2016
- 2016-09-20 US US15/270,780 patent/US10176888B2/en active Active
-
2017
- 2017-02-24 US US15/441,386 patent/US10468127B2/en active Active
- 2017-05-31 US US15/610,339 patent/US11094402B2/en active Active
-
2018
- 2018-12-04 US US16/209,302 patent/US20190103176A1/en not_active Abandoned
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10176888B2 (en) | Architecture for field upgrade of a health monitoring system | |
EP2273400A1 (en) | Method and system for managing health data | |
RU2493591C2 (en) | Health monitoring system architecture |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |
Effective date: 20210531 |
|
MKLA | Lapsed |
Effective date: 20210531 |