MEDICAL DEVICES THAT SUPPORT ENHANCED SYSTEM EXTENSIBILITY FOR DIABETES CARE

• US 20120095313A1
• Filed: 10/15/2010
• Published: 04/19/2012
• Est. Priority Date: 10/15/2010
• Status: Abandoned Application

• Current Assignee: Roche Diabetes Care Inc. (Roche Holding AG)
• Original Assignee: Roche Diagnostics Operations Incorporated (Roche Holding AG)
• Inventors: Reinke, Robert E., Gejdos, Igor, Dymshitz, Julia
• Application Number:
  US12/905,471
• Publication Number:
  US 20120095313A1
• Time in Patent Office: Days
• US Class Current: 600/365
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 70/40 relating to drugs, e.g. their side effects or intended usage

Abstract

A medical device or medical software is provided that supports system extensibility for diabetes care. The medical device or software is comprised of an application and particular data structures that support diabetes care. The data structures include: a patient class that has attributes and methods associated with a person receiving medical treatment for diabetes; a patient log class that has a composition relationship with the patient class and attributes and methods that log actions taken by the patient; a treatment plan class that has a composition relationship with the patient class and attributes and methods that define a series of planned actions related to medical treatment of the patient; and an adherence class that has a composition relationship with the patient log class and attributes and methods define relationships between actions planned for the patient and actions taken by the patient. The application instantiates an object from at least one of the patient log class, the adherence class and the treatment plan class, having only external-to-the-composition knowledge of which objects are instantiated, and performs a function using the instantiated object.

Claims

1. A medical device that supports extensibility for diabetes care, comprising:

a patient class implemented in the computer memory of the device, where the patient class has properties and methods associated with a person receiving medical treatment for diabetes;

one or more patient log classes implemented in the computer memory of the device, where the patient log classes have properties and methods associated with a persistent log of actions taken by the patient and are in a composition relationship with the patient class; and

an application that instantiates a patient object from the patient class and fills a patient log composition of the patient class with patient log objects instantiated from the patient log class or subclasses thereof by means of a single coded list in computer memory, where the application uses the instantiated patient object and instantiated patient log objects to perform functions, and the application is computer executable instructions executed by a computer processor in the device.

2. The medical device of claim 1 further comprises a logged action class implemented in the computer memory of the device, where the logged action class has properties and methods associated with entries in a patient log and is in a composition relationship with the patient log class;

where the application further instantiates logged action objects of the patient log composition by means of a single coded list in computer memory where the logged action objects instantiated are instances of the logged action class or subclasses thereof.

3. The medical device of claim 2 wherein the logged action class includes a timestamp and supports logging medication administration, values of physiological state variables, food intake, and exercise, where the application further uses the instantiated logged action objects to modify entries in patient logs.

4. The medical device of claim 2 further comprises a physiological state variable class implemented in the computer memory of the device, where the physiological state variable class has properties and methods associated with measurable or recordable properties of a patient'"'"'s physiology, and is in a composition relationship with the patient class;

the application further instantiates objects of a physiological state variable composition by means of a single coded list in computer memory where the objects instantiated are instances of the physiological state variable class or subclasses thereof; and

the application supports the creation, entry or modification of logged actions corresponding to membership of the physiological state variables composition of the patient class.

5. The medical device of claim 4 further comprises

a medication catalog class implemented in the computer memory of the device;

and

a medication class implemented in the computer memory of the device, where medication class has properties and methods associated with drugs or medicines, and is in a composition relationship with a medication catalog class;

the application further instantiates objects of a medication composition of the medication catalog class by means of a single coded list in computer memory where the objects instantiated are instances of the medication class or subclasses thereof; and

the application supports the creation, entry or modification of logged actions corresponding to membership of the medications composition of the medication catalog class.

6. The medical device of claim 5 wherein the medication class has a method for calculating the dosage of medication from data in the patient logs and knowledge of a specific medication, and said method for calculating dosage is used to make recommendations to the patient on dosage.

7. The medical device of claim 6 further comprises:

one or more treatment plan classes implemented in the computer memory of the device, where the treatment plan classes have properties and methods associated with a series of planned actions related to therapy to be undertaken by the patient, and are in a composition relationship with the patient class; and

an application that instantiates an object from the patient class and fills a treatment plan composition of the patient class with treatment plan objects instantiated from the treatment plan class or subclasses thereof by means of a single coded list in computer memory, where the application uses the instantiated patient object and instantiated treatment plan objects to perform functions, and the application is computer executable instructions executed by a computer processor in the device.

8. The medical device of claim 7 further comprises

a trigger catalog class implemented in the computer memory of the device;

and

a trigger class implemented in the computer memory of the device, the trigger class has properties and methods associated with triggering a planned actions in a treatment plan, and is in a composition relationship with the trigger catalog class;

the application further instantiates objects of a trigger composition of the trigger catalog class by means of a single coded list in computer memory where the objects instantiated are instances of a trigger class or subclasses thereof, and the application supports the creation, entry, modification and use of planned actions that are associated with the trigger composition of the trigger catalog class.

9. The medical device of claim 8 further comprises

an adherence class implemented in the computer memory of the device, the adherence class has properties and methods associated with how well actions taken by a patient match the planned actions of a given treatment plan, and is in a composition relationship with the patient log class;

the application further instantiates objects of a adherence composition of the patient log class by means of a single coded list in computer memory where the objects instantiated are instances of an adherence class or subclasses thereof, and the application supports the creation, entry, modification and use of planned actions and logged actions that are associated with the objects of the adherence composition of the patient log class.

10. The medical device of claim 1 further comprises

an interface definition in the computer memory of the device which identifies names and types of the properties and methods to be supported by objects of the patient log composition;

and

an external manifest that identifies libraries, classes, and instances to be used to fill the patient log composition, where the application uses the manifest to create patient log objects to populate the patient log composition.

11. The medical device of claim 1 further comprises a meter that measures blood glucose.

12. A medical device that supports extensibility for diabetes care, comprising:

a patient class implemented in the computer memory of the device, where the patient class has properties and methods associated with a person receiving medical treatment for diabetes;

one or more treatment plan classes implemented in the computer memory of the device, where the treatment plan classes have properties and methods associated with a series of planned actions related to therapy to be undertaken by the patient, and are in a composition relationship with the patient class; and

an application that instantiates an object from the patient class and fills a treatment plan composition of the patient class with treatment plan objects instantiated from the treatment plan class or subclasses thereof by means of a single coded list in computer memory, where the application uses the instantiated patient object and instantiated treatment plan objects to perform functions, and the application is computer executable instructions executed by a computer processor in the device.

15. The medical device of claim 12 further comprises

one or more patient log classes implemented in the computer memory of the device, where the patient log classes have properties and methods associated with a persistent log of actions taken by the patient and are in a composition relationship with the patient class;

and

the application further instantiates a patient object from the patient class and fills a patient log composition of the patient class with patient log objects instantiated from the patient log class or subclasses thereof by means of a single coded list in computer memory, where the application uses the instantiated patient object and instantiated patient log objects to perform functions.

16. The medical device of claim 15 further comprises a logged action class implemented in the computer memory of the device, where the logged action class has properties and methods associated with entries in a patient log and is in a composition relationship with the patient log class;

where the application further instantiates logged action objects of the patient log composition by means of a single coded list in computer memory where the logged action objects instantiated are instances of the logged action class or subclasses thereof.

17. The medical device of claim 16 wherein the logged action class includes a timestamp and supports logging medication administration, values of physiological state variables, food intake, and exercise, where the application further uses the instantiated logged action objects to modify entries in patient logs.

18. The medical device of claim 16 further comprises a physiological state variable class implemented in the computer memory of the device, where the physiological state variable class has properties and methods associated with measurable or recordable properties of a patient'"'"'s physiology, and is in a composition relationship with the patient class;

the application further instantiates objects of a physiological state variable composition by means of a single coded list in computer memory where the objects instantiated are instances of the physiological state variable class or subclasses thereof; and

the application supports the creation, entry or modification of logged actions corresponding to membership of the physiological state variables composition of the patient class.

19. The medical device of claim 18 further comprises

a medication catalog class implemented in the computer memory of the device;

and

a medication class implemented in the computer memory of the device, where medication class has properties and methods associated with drugs or medicines, and is in a composition relationship with a medication catalog class;

the application further instantiates objects of a medication composition of the medication catalog class by means of a single coded list in computer memory where the objects instantiated are instances of the medication class or subclasses thereof; and

the application supports the creation, entry or modification of logged actions corresponding to membership of the medications composition of the medication catalog class.

20. The medical device of claim 19 wherein the medication class has a method for calculating the dosage of medication from data in the patient logs and knowledge of a specific medication, and said method for calculating dosage is used to make recommendations to the patient on dosage.

21. The medical device of claim 12 further comprises

an interface definition in the computer memory of the device which identifies names and types of the properties and methods to be supported by objects of the patient log composition;

and

an external manifest that identifies libraries, classes, and instances to be used to fill the patient log composition, where the application uses the manifest to create patient log objects to populate the patient log composition.

22. The medical device of claim 12 further comprises a meter that measures blood glucose.

13. The medical device of 12 further comprises

a trigger catalog class implemented in the computer memory of the device;

and

a trigger class implemented in the computer memory of the device, the trigger class has properties and methods associated with triggering a planned actions in a treatment plan, and is in a composition relationship with the trigger catalog class;

the application further instantiates objects of a trigger composition of the trigger catalog class by means of a single coded list in computer memory where the objects instantiated are instances of a trigger class or subclasses thereof, and the application supports the creation, entry, modification and use of planned actions that are associated with the trigger composition of the trigger catalog class.

14. The medical device of claim 13 further comprises:

an adherence class implemented in the computer memory of the device, the adherence class has properties and methods associated with how well actions taken by a patient match the planned actions of a given treatment plan, and is in a composition relationship with the patient log class;

the application further instantiates objects of a adherence composition of the patient log class by means of a single coded list in computer memory where the objects instantiated are instances of an adherence class or subclasses thereof, and the application supports the creation, entry, modification and use of planned actions and logged actions that are associated with the objects of the adherence composition of the patient log class.

23. A medical device that supports extensibility, comprising:

a device model class implemented in the computer memory of the device, the device model class has properties and methods associated with a particular model of medical device;

one or more capability classes implemented in the computer memory of the device, the capability classes have properties and methods associated with a particular capability of a medical device, and are in a composition relationship with a root capability class.

an application that instantiates an object from the device model class and fills a capability composition of the device class with objects instantiated by means of a single coded list in computer memory where the objects instantiated are instances of the capability class or subclasses thereof;

the application uses the instantiated device model object and the instantiated capability objects to perform functions, wherein the application is computer executable instruction executed by a computer processor in the device.

24. The device of claim 23 further comprises:

a parameter definition class implemented in the computer memory of the device, the parameter definition class has properties and methods associated with device configuration parameters, and is in a composition relationship with the capability class;

the application further instantiates objects of the parameter definition composition of the capability class by means of a single coded list in computer memory where the objects instantiated are instances of a parameter definition class or subclasses of that class, and the application uses said instantiated parameter definition composition to support editing configuration parameters based on the objects of the parameter definition compositions of the capability classes.