ARCHITECTURE FOR HEALTH MONITORING SYSTEMS

• US 20080300919A1
• Filed: 05/29/2008
• Published: 12/04/2008
• Est. Priority Date: 05/30/2007
• Status: Abandoned Application

• Current Assignee: Bayer Healthcare LLC (Bayer AG)
• Original Assignee: Bayer Healthcare LLC (Bayer AG)
• Inventors: Chen, Jun, Gofman, Igor, Lok, Derek, Chen, Lin, Fu, Qiang, Ripley, Paul M., Lieber, Harris, Stefkovic, Gregory, Li, Qiong, Harris, Steven B., Charlton, Steven, Inman, Paul L., Nguyen, Tony, Johnson, Gary J., Sun, Hoi-Cheong Seven
• Application Number:
  US12/129,555
• Publication Number:
  US 20080300919A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: A61B 5/14532 for measuring glucose, e.g. by tissue impedance measurement
• CPC Class Codes: G06F 1/16 Constructional details or arrangements
• CPC Class Codes: G06F 1/1605 Multimedia displays, e.g. with integrated or attached speakers, cameras, microphones
• CPC Class Codes: G06F 1/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
• CPC Class Codes: G06F 13/385 for adaptation of a particular data processing system to different peripheral devices
• CPC Class Codes: G06F 13/4081 Live connection to bus, e.g. hot-plugging current or voltage limitation during live insertion H02H9/004
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 50/22 Social work or social welfare, e.g. community support activities or counselling services
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

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.

Claims

1. 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.

2. The system of claim 1, 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.

3. The system of claim 1, 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.

4. The system of claim 1, 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.

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

6. The system of claim 1, wherein the first set of at least one module provide a diabetes-management system.

7. 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.