Blood Glucose Tracking Apparatus and Methods

• US 20100122074A1
• Filed: 12/03/2009
• Published: 05/13/2010
• Est. Priority Date: 04/02/2001
• Status: Abandoned Application

• Current Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories Incorporated)
• Original Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories Incorporated)
• Inventors: Lipman, Kelley, Bacho, Henrik, Lortz, Mark, Colman, Fredric C., Drucker, Steven, Liamos, Charles T., Jiang, Feng
• Application Number:
  US12/630,722
• Publication Number:
  US 20100122074A1
• Time in Patent Office: Days
• US Class Current: 713/1
• CPC Class Codes: A61B 2562/0295 Strip shaped analyte sensors for apparatus classified in A61B5/145 or A61B5/157 disposable multilayered or laminated electrodes G01N27/307; details of handling chemical test elements G01N33/4875
• CPC Class Codes: A61B 5/14532 for measuring glucose, e.g. by tissue impedance measurement
• CPC Class Codes: A61B 5/742 using visual displays A61B5/339 takes precedence
• CPC Class Codes: A61B 5/743 Displaying an image simultaneously with additional graphical information, e.g. symbols, charts, function plots
• CPC Class Codes: G01N 33/48778 Containers specially adapted therefor, e.g. for dry storage
• CPC Class Codes: G01N 33/48792 Data management, e.g. communication with processing unit for in vivo diagnostics A61B5/0002; transmission systems for measured values G08C
• CPC Class Codes: G16H 10/40 for data related to laboratory analysis, e.g. patient specimen analysis
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: Y10S 435/97 Test strip or test slide

Abstract

A measurement module for glucose testing includes a glucose testing measurement module housing, a test strip receptacle formed in the housing, and a connector portion formed in the housing and shaped to permit mechanical removable attachment of the housing to a hand-held computer. Electronics determine the amount of glucose present in a sample of body fluid, when the test strip is positioned in the receptacle and the body fluid is placed on a test strip, and communicate the glucose amount to the hand-held computer via the connector portion.

Claims

1. (canceled)

2. A system for managing healthcare data, comprising:

a first set of at least one module providing primary healthcare functions;

a first central engine controlling the first set of at least one module;

a second set of at least one module providing secondary healthcare functions;

a second central engine controlling the second set of at least one module; and

a communication interface providing a connection between the first central engine and the second central engine.

3. The system of claim 2, wherein the first central engine is assembled with the first set of at least one module according to a first development process and the second central engine is assembled with the second set of at least one module according to a second development process.

4. The system of claim 2, wherein the communication interface is at least one of a USB interface, a radio frequency (RF) interface, a Wi Fi interface, and an Ethernet interface.

5. The system of claim 2, wherein the first central engine is implemented on a first mother board, the second central engine is implemented on a second mother board, the first set of at least one module is separately implemented on a first set of at least one daughter board, and the second set of at least one module is separately implemented on a second set of at least one daughter board.

6. The system of claim 2, further comprising a first housing including the first central engine and a second housing including the second central engine.

7. The system of claim 2, wherein the first set of at least one module provide a diabetes management system.

8. The system of claim 2, wherein the central engine is implemented on a mother board and the at least one module is separately implemented on a daughter board, the daughter board being standardized for connection with the mother board.

9. A method for managing healthcare data, comprising:

developing, according to a first development process, a first assembly of a first central engine and a first set of at least one module providing primary healthcare functions, the first central engine controlling the first set of at least one module;

developing, according to a second development process, a second assembly of a second central engine and a second set of at least one module secondary healthcare functions; and

connecting the first assembly and the second assembly via a communication interface.

10. A device for managing health data, comprising:

a first housing portion including a data storage system that stores health data; and

a second housing portion including a data communications element that provides data communications between the data storage system and a processing device by connecting with the processing device, the processing device processing the health data according to a data management software,

wherein the first housing portion and the second housing portion are connected by a cable that communicates signals between the data communications element and other components in the first housing portion.

11. The device of claim 10, wherein the data communications element is a USB connector that is received by a USB port in the processing device.

12. The device of claim 10, wherein a length of the cable between the first housing portion and the second housing portion is adjustable.

13. The device of claim 12, wherein the second housing portion includes a storage chamber for storing an excess length of the cable.

14. The device of claim 13, wherein the storage chamber includes a includes a spring device, the spring device drawing the excess length of the cable into the storage chamber.

15. The device of claim 10, wherein the first housing portion includes a storage cavity for receiving the second housing portion.

16. A device for managing health data, comprising:

a first housing portion including a health data management system and a data communications element that provides data communications between the health data management system and an external processing device; and

a second housing portion that is removably coupled to the first housing portion, the second housing portion including at least one component used by the health data management system.

17. The device of claim 16, wherein the second housing portion is a cap for the data communications element.

18. The device of claim 17, wherein the data communications element is a USB connector and the second housing portion is a cap for the USB connector.

19. The device of claim 17, wherein the at least one component is a power source that is provides power, via the data communications element, to the health data management system when the cap is coupled to the first housing portion.

20. The device of claim 19, wherein the power source is a rechargeable battery.

21. The device of claim 19, wherein the rechargeable battery exchanges power with another power source in the first housing portion via the data communications element.

22. The device of claim 19, wherein the power source is a backup for another power source in the first housing portion.

23. The device of claim 19, wherein the power source provides power to the health data management system when the cap is coupled to the first housing portion according to a first orientation, and does not provide power to the health data management system when the cap is coupled to the first housing according to a second orientation.

24. The device of claim 19, further comprising a third housing portion that is removably coupled to the first housing portion, the third housing portion storing test sensors for a health data measurement system included in the health data management system in the first housing portion.

25. The device of claim 16, wherein the health data management system includes a health data measurement system and a user interface that displays results from the health data measurement system.

26. The device of claim 25, wherein the at least one component includes one or more test sensors for the health data measurement system.

27. The device of claim 25, wherein the at least one component includes a temperature sensor that provides a measurement of ambient temperature to the health data management system, the health data management system using the measurement of ambient temperature to determine results from the health data measurement system.

28. The device of claim 27, wherein the temperature sensor measures the ambient temperature at a surface of the cap.

29. The device of claim 28, wherein the temperature sensor measures the ambient temperature of a thin membrane at the surface of the cap.

30. A system for managing healthcare data, comprising:

at least one module providing a healthcare function;

a central engine controlling the at least one module;

one or more communication interfaces providing a connection to a remote server, the remote server storing one or more program components corresponding to the at least one module or the central engine; and

a download engine configured to receive the one or more program components from the remote server via the one or more communication interfaces and to deliver the one or more program components for use with the at least one module or the central engine.

31. The system of claim 30, further comprising a version management component that determines whether the one or more program components is compatible with the at least one module or the central engine before the download engine receives the one or more program components.

32. The system of claim 30, wherein the one or more program components replaces an older version of a software running on the at least one module or the central engine with an updated version of the software.

33. The system of claim 32, further comprising a restore component that restores the older version of the software.

34. The system of claim 33, wherein the updated version of the software is downloaded to a memory area that is separate from the older version of the software, and the older version of the software remains available to be restored.

35. The system of claim 33, wherein the older version of the software is restored when a validation component determines that the updated version of the software operates incorrectly or has not been downloaded properly.

36. The system of claim 30, wherein the one or more program components provides a patch for software running on the at least one module or the central engine.

37. The system of claim 30, wherein the one or more program components provides a new function to be executed by the at least one module or the central engine.

38. The system of claim 30, wherein the one or more program components includes configuration information for software running on the at least one module or the central engine.

39. The system of claim 30, wherein the download engine is manually triggered by a user to receive and deliver the one or more program components.

40. The system of claim 30, wherein the download engine is automatically triggered to identify the one or more program components when communication to the remote server can be established.

41. The system of claim 30, 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.

42. The system of claim 30, wherein when communication to the remote server is established when the download engine is in range of a wireless network.

43. The system of claim 30, further comprising a data validation component configured to validate the one or more program components before the one or more program components is deployed.

44. The system of claim 43, wherein the data validation component determines whether the one or more program components are not corrupted.

45. The system of claim 43, 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.

46. The system of claim 43, wherein the one or more program components are removed if the data validation determines that the one or more program components is corrupted.

47. A system for managing health data, comprising:

a data storage system storing health data, data management software, and an initialization program, the initialization program launching the data management software on a processing device and the data management software processing the health data on the processing device; and

a data communications interface providing data communications between the data storage system and the processing device,

wherein, upon establishment of the data communications between the data storage system and the processing device, the initialization program launches the data management software on the processing device without requiring prior installation, on the processing device, of an additional program component associated with the data management software.

48. The system of claim 47, wherein the data storage system includes at least one of a USB flash drive and a memory card.

49. The system of claim 47, wherein the data storage system is configured according to a memory map indicating security levels for areas of memory in the data storage system, the security levels determining access to data stored in the areas of memory.

50. The system of claim 47, wherein the data storage system includes a first memory device storing the data management software and the initialization program, and a second memory device storing the health data.

51. The system of claim 50, wherein the first memory device is an EEPROM and the second memory device is a flash memory.

52. The system of claim 47, further comprising a data check system validating data to be stored in the data storage system.

53. The system of claim 47, wherein the data management software processes the health data without permanently storing the data on the processing device.

54. The system of claim 47, wherein the data management software removes any data on the processing device associated with the data management software before ending execution.

55. The system according to claim 47, wherein the data management software closes when the data communications between the data portable device and the processing device is terminated.

56. The system of claim 47, wherein the processing device is compatible with an interface protocol configuration allowing data communication to be established between the data storage system and the processing device, and the initialization program reconfigures the data storage system to a software configuration specific to the data management software allowing the data management software to be launched on the processing device, the software configuration being different from the interface protocol configuration.

57. The system of claim 56, wherein the interface protocol configuration is a USB mass portable device (MSD) configuration.

58. The system of claim 47, wherein the data communications interface includes at least one of a universal serial bus (USB) interface, a secure digital (SD) interface, and a radio frequency (RF) link.

59. The system of claim 47, wherein the processing device is a personal computer, a personal digital assistant, or a smart cellular phone.

60. The system of claim 47, wherein the data communications interface further provides data communications between the data storage system and a blood glucose meter.

61. The system of claim 47, wherein, wherein the data communications interface further provides data communications between the data storage system and a printer, and wherein (i) the data storage system provides a ready to print file from the health data and sends the ready to print file to the printer, or (ii) the printer receives, formats, and prints the health data from the data storage system.

62. The system of claim 47, wherein the health data includes analyte data, temperature data, blood pressure data, heart rate data, breathing data or weight data.

63. The system of claim 47, wherein the health data includes blood glucose data.

64. The system of claim 47, wherein the processing device is one of a plurality of types of processing devices that are compatible with the data communications interface.

65. The system of claim 47, further comprising a measurement system determining health data from an individual for storage in the data storage system.

66. The system of claim 65, wherein the measurement system, the data storage device system, and the data communications interface are integrated with a housing.

67. The system of claim 66, further comprising a user interface integrated with the housing, the user interface operable to display the health data.

68. The system of claim 67, further comprising a local processor and local software integrated with the housing, the local processor processing the health data to be displayed via the user interface.

69. The system of claim 47, wherein one processing device is designated as a base station of the data storage system, wherein additional features of the data management software are enabled when the data storage system detects it is connected to the base station.

70. The system of claim 69, wherein the additional features include a download of all health data in the storage device to the base station or a launching of a master version of the data management software.

71. The system of claim 47, wherein a security component controls access by the processing device to the health data in the data storage system.

72. The system of claim 71, wherein the security component prompts a user for authentication information and validates the authentication information when the processing device attempts to access the health data.

73. The system of claim 71, wherein the security component establishes a trusted system by requiring the processing device to be registered with the data storage system.

74. The system of claim 73, wherein the processing device requires the data storage system to be registered and a two way authentication is established.

75. The system of claim 71, wherein the security component encrypts the health data on the data storage system during transmission to the processing device.

76. The system of claim 71, wherein the security component restricts access to the health data to the data management software.

77. The system of claim 71, wherein the security component restricts access to the health data in the data storage system according to data type.

78. The system of claim 71, wherein the health data is encrypted and the data management software is required to decrypt the data.

79. A system for managing health data, comprising:

a portable device including data management software that processes health data, the portable device having a first software configuration corresponding to an interface protocol and a second software configuration specific to the data management software; and

a processing device connected to the portable device, wherein upon connection between the portable device and the processing device, the processing device communicates with the portable device according to the interface protocol, and after the portable device is reconfigured from the first configuration to the second configuration, the processing device executes the data management software.

80. The system according to claim 79, wherein the portable device includes an initialization program, and upon connection between the storage device and the processing device, the initialization program is executed and reconfigures the portable device from the first configuration to the second configuration.

81. The system of claim 79, wherein the interface protocol corresponds to a universal serial bus (USB) and the first configuration is a USB mass portable device (MSD) configuration.

82. The system according to claim 79, wherein the portable device and the processing device are connected via a universal serial bus (USB) interface, a secure digital interface, or a radio frequency (RF) link.

83. The system of claim 79, wherein the processing device is a personal computer, a personal digital assistant, or a smart cellular phone.

84. The system of claim 79, wherein the data management software processes the health data without permanently storing the data on the processing device.

85. The system of claim 79, wherein the data management software removes any data on the processing device associated with the data management software before ending execution.

86. The system according to claim 79, wherein the data management software closes when the data communications between the data portable device and the processing device is terminated.

87. A method for managing health data, comprising:

establishing, for a first time, data communications between a data storage system to a processing device via a data communications interface, the data storage system storing health data, data management software, and an initialization program;

executing, on the processing device, the initialization program upon establishment of the data communications between the data storage system and the processing device, without requiring prior installation, on the processing device, of an additional program component associated with the data management software;

launching, with the initialization program, the data management software on the processing device; and

processing the health data on the processing device with the data management software.

88. The method of claim 87, wherein processing the health data on the processing device comprises processing the health data without permanently storing the data on the processing device.

89. The method of claim 87, further comprising removing any data on the processing device associated with the data management software before termination of the act of processing the health data.

90. The method according to claim 87, further comprising terminating the act of processing the health data when the data communications between the data portable device and the processing device is terminated.

91. The method of claim 87, wherein the processing device is compatible with an interface protocol configuration allowing data communication to be established between the data storage system and the processing device, and the act of executing the initialization program comprises reconfiguring the data storage system to a software configuration specific to the data management software, the software configuration being different from the interface protocol configuration.

92. The method of claim 91, wherein the interface protocol configuration is a USB mass portable device (MSD) configuration.

93. The method of claim 87, wherein the data communications interface includes at least one of a universal serial bus (USB) interface, a secure digital (SD) interface, and a radio frequency (RF) link.

94. The method of claim 87, wherein the processing device is a personal computer, a personal digital assistant, or a smart cellular phone.

95. The method of claim 87, further comprising controlling access by the processing device to the health data in the data storage system.

96. The method of claim 95, wherein controlling access comprises prompting a user for authentication information and validating the authentication information when the processing device attempts to access the health data.

97. The method of claim 95, wherein controlling access comprises establishing a trusted system by requiring the processing device to be registered with the data storage system.

98. The method of claim 95, wherein controlling access comprises requiring the data storage system to be registered and a two way authentication is established.

99. The method of claim 95, wherein controlling access comprises encrypting the health data on the data storage system during transmission to the processing device.

100. The method of claim 95, wherein controlling access comprises restricting access to the health data to the data management software.

101. The method of claim 95, wherein controlling access comprises restricting access to the health data in the data storage system according to data type.

102. The method of claim 95, further comprising encrypting the health data is encrypted and controlling access comprises requiring the data management software to decrypt the data.

104. The method of claim 88, further comprising launching an initialization program from the portable device upon detection of the connection, wherein the portable device is reconfigured by the initialization program.

105. The method of claim 88, further comprising receiving, by the portable device, the health data from a measurement system.

106. The method of claim 88, wherein the interface protocol corresponds to one of a universal serial bus (USB) interface, a secure digital interface, and a radio frequency (RF) link.

103. A method for managing health data, comprising:

detecting a connection between a portable device and a processing device, the portable device containing data management software processing health data and having a first software configuration corresponding to an interface protocol, wherein upon connection between the portable device and the processing device, the processing device communicates with the portable device according to the interface protocol;

reconfiguring the portable device from the first configuration to a second configuration specific to the software; and

launching the software from the reconfigured portable device.

107. A system for managing health data, comprising:

a first device that stores health data, data management software, and an initialization program;

a second device that processes the health data with the data management software; and

a data communications interface providing data communications between the first device and the second device,

wherein upon establishment of the data communications between the data storage system and the processing device, the initialization program launches the data management software on the processing device without requiring prior installation, on the processing device, of an additional program component associated with the data management software.