Diabetes management systems, methods, and apparatus for user reminders, pattern recognition, and interfaces
阅读说明：本技术 用于用户提醒、模式辨识和接口的糖尿病管理系统、方法及设备 (Diabetes management systems, methods, and apparatus for user reminders, pattern recognition, and interfaces ) 是由 詹尼弗·L·加斯 姚·雷蒙德·L 罗伯特·W·莫林 劳伦·N·博克 弗拉迪斯拉夫·米伦科维奇 于 2018-03-27 设计创作，主要内容包括：用于管理糖尿病的系统、方法和设备,包括便携糖尿病管理系统(DMS)装置。DMS装置包括处理器、数据存储装置、触摸屏显示器、以及无线通信设施。交互显示屏幕被配置为显示在触摸屏显示器上,列出有关DMS装置接收的血糖测量数据的多个不同的检测到的模式的可选子集。基于可在处理器上执行的多个算法来检测模式。基于检测到模式的频率来确定检测到的模式的子集,并对检测到的模式指定优先级。提供数种其他方面。(Systems, methods, and apparatus for managing diabetes include a portable Diabetes Management System (DMS) device. The DMS device includes a processor, a data storage device, a touch screen display, and a wireless communication facility. The interactive display screen is configured to be displayed on the touch screen display listing a selectable subset of a plurality of different detected patterns related to blood glucose measurement data received by the DMS device. The pattern is detected based on a plurality of algorithms executable on the processor. A subset of the detected patterns is determined based on a frequency of the detected patterns and priorities are assigned to the detected patterns. Several other aspects are provided.)
1. An apparatus for managing diabetes, the apparatus comprising:
a portable Diabetes Management System (DMS) device comprising a processor, a data storage device, a touch screen display, a wireless communication facility, a pattern recognition engine stored in the data storage device and executable in the processor, and a user interface structure stored in the data storage device and executable in the processor, the user interface structure comprising a plurality of user interface displays configured to be displayed on the touch screen display; wherein:
one of the plurality of user interface displays comprises a list of selectable subsets of a plurality of different patterns based on blood glucose measurement data received by the DMS device, the selectable subsets of patterns based on a frequency with which the different patterns are detected by the pattern-recognition engine.
2. The apparatus of claim 1, wherein the different modes comprise at least one of: critical low meter reading, critical high meter reading, low test frequency, medium test frequency, good test frequency, mostly simultaneous testing, high time of day, low time of day, best time of day, high fasting, low fasting, high before lunch, low before lunch, high before dinner, low after dinner, gradually high, gradually low, low on monday, and high on monday.
3. The apparatus of claim 1, wherein the pattern-recognition engine comprises a plurality of algorithms, each algorithm configured to recognize a respective one of the different patterns.
4. The apparatus of claim 1, wherein the pattern recognition engine is configured to recognize a pattern based on 14 to 21 days of the blood glucose measurement data received by the DMS device.
5. The apparatus of claim 1, wherein each user interface display is linked to, or reachable via, at least one other user interface display of the plurality of user interface displays, or presented as a result of a pattern detected by the pattern recognition engine.
6. The device of claim 1, wherein one of the plurality of user interface displays further comprises a screen for selecting a number of blood glucose tests to be performed per week.
7. The device of claim 6, wherein one of the plurality of user interface displays further comprises a reminder screen to perform a blood glucose test, the reminder screen displayed on the touch screen display in response to the pattern recognition engine detecting less than the selected number of blood glucose tests to be performed per week (selected via the screen for selecting the number of blood glucose tests to be performed per week).
8. The device of claim 1, wherein one of the plurality of user interface displays further comprises a pattern manager screen comprising an interaction list of detected patterns that are active, attached, and sequestered.
9. The device of claim 1, wherein one of the plurality of user interface displays further comprises a mode details screen comprising a summary area, a chart area, a status area, an explanation area, and a "further links" area.
10. A method for managing diabetes, the method comprising the steps of:
a receiving step of receiving, at the portable wireless device, a blood glucose measurement result from the blood glucose meter;
a storage step of storing the blood glucose measurement in a data storage device of the portable wireless device;
identifying, by a processor of the portable wireless device, one or more patterns based on the blood glucose measurements, the processor executing a pattern recognition engine stored in the data storage device; and
a prompting step of prompting a user via a user interface of the portable wireless device to take an action in response to the recognizing step recognizing one or more of the patterns.
11. The method of claim 10, wherein the pattern comprises at least one of: critical low meter reading, critical high meter reading, low test frequency, medium test frequency, good test frequency, mostly simultaneous testing, high time of day, low time of day, best time of day, high fasting, low fasting, high before lunch, low before lunch, high before dinner, low after dinner, gradually high, gradually low, low on monday, and high on monday.
12. The method of claim 10, wherein the identifying of one or more of the patterns is based on the receiving blood glucose measurements at the portable wireless device within 14 days to 21 days.
13. The method of claim 10, further comprising the steps of: storing user interface structures in the data storage device, the user interface structures executable in the processor.
14. The method of claim 10, wherein the prompting step of prompting the user to take an action comprises the steps of: prompting the user to set a pattern target regarding the one or more patterns identified.
15. The method of claim 10, wherein the prompting step to prompt the user to take an action comprises at least one of: prompting the user to test their blood glucose levels, take medical measures, record activity, and record carbohydrate intake.
16. The method of claim 10, wherein the prompting step of prompting the user to take an action via the user interface comprises the steps of: generating and presenting at least one of a recommendation, a reminder, and an alert to the user on a display of the portable wireless device.
17. The method of claim 16, further comprising the steps of: limiting the frequency at which the reminder is presented.
18. The method of claim 16, further comprising the steps of: prioritizing the presenting step of presenting the at least one of the recommendation, the reminder, and the alert on the display based on a predetermined priority stored in the data storage.
19. The method of claim 10, wherein the prompting step of prompting the user to take an action via the user interface comprises the steps of: presenting at least one of a recommendation, a reminder, and an alert on a display of the portable wireless device by a higher intensity or more frequently than others of the recommendation, the reminder, and the alert.
20. The method of claim 19, wherein the higher intensity comprises one of: larger text, brighter highlighted prompts, different colors and sounds.
Technical Field
Cross reference to related applications: this application claims priority to U.S. provisional application No. 62/478,023, filed on 28/3/2017, the contents of which are hereby relied upon and incorporated by reference.
The invention relates to diabetes management systems, methods and apparatus for user reminders, pattern recognition and interfaces.
Background
Diabetes is a serious life-long disease that is still incurable to date. In the united states alone, about 200 million people are diagnosed with diabetes annually, which is the seventh leading cause of death in the united states. In 2012, 8600 thousands of americans over the age of 20 had pre-diabetes; this is more than 7900 million people in 2010. In 1993, there were about eight million diagnosed cases of diabetes in the united states, the number of which has currently increased to about 2100 ten thousand diagnosed cases. In addition, there are at least 8 million undiagnosed cases.
The impact of diabetes on the healthcare system is surprising. In the united states, the costs of hospitalization, supply, unemployment, disability payment, and premature death due to diabetes have exceeded $ 2450 billion in a
Studies conducted by the national institutes of health have shown that people with diabetes enjoy significant health benefits if they closely monitor and control their Blood Glucose (BG) levels. Continuous management of diabetes, including diet, exercise, and active monitoring and control of blood glucose levels, can reduce the risk of serious complications, and possibly reduce some diabetes-related conditions by more than half.
This study further shows that active treatment of diabetes can reduce ocular disease by up to 76%, renal disease by up to 50%, and neurological disease by up to 60%. Furthermore, treatment regimens require tight control of blood glucose levels, which essentially results in an increased risk of more frequent hypoglycemic episodes. A very real problem facing many diabetics is the fear that they may be unable to get help externally in the event of a hypoglycemic coma or other diabetic emergency. Similarly, many parents and guardians of diabetic patients are also confronted with fear of developing diabetic emergencies in children or other family members. Because of the potential for diabetic emergencies, diabetics and guardians are hampered from living in an actively independent manner. Accordingly, there is a need for improved diabetes management systems and methods.
Disclosure of Invention
In a first aspect, an apparatus for managing diabetes is provided. The apparatus includes a portable Diabetes Management System (DMS) device. The DMS device includes a processor, a data storage device, a touch screen display, a wireless communication facility, a pattern-recognition engine stored in the data storage device and executable in the processor, and a user interface structure stored in the data storage device and executable in the processor. The user interface structure includes a plurality of user interface displays configured to be displayed on the touch screen display, one of the plurality of user interface displays including a list of selectable subsets of a plurality of different patterns based on blood glucose measurement data received by the DMS device, the selectable subsets of patterns based on a frequency with which the different patterns were detected by the pattern-recognition engine.
In a second aspect, a method for managing diabetes is provided. The method comprises the following steps: receiving, at the portable wireless device, a blood glucose measurement from a blood glucose meter; storing the blood glucose measurement in a data storage device of the portable wireless device; identifying, by a processor of the portable wireless device, one or more patterns based on the blood glucose measurements, wherein the processor executes a pattern recognition engine stored in a data storage device; and in response to recognizing the one or more patterns, prompting the user to take action via a user interface of the portable wireless device.
According to these and other aspects of the invention, several other aspects are provided. Other features and aspects of the present invention will become more fully apparent from the following description, the appended claims and the accompanying drawings.
Drawings
FIG. 1 is a schematic block diagram depicting an example system in accordance with an embodiment of the present invention.
FIG. 2 is a schematic block diagram depicting an example apparatus in accordance with a specific embodiment of the present invention.
FIG. 3 is a schematic diagram depicting an example Diabetes Management System (DMS) database in accordance with an embodiment of the present invention.
FIG. 4 is a screen shot of an exemplary interface for selecting a mode type in accordance with a specific embodiment of the present invention.
FIG. 5A is a screen shot of an exemplary interface for selecting a test frequency target in accordance with an embodiment of the present invention.
FIG. 5B is a screenshot of an exemplary interface for presenting and managing detected patterns, according to a specific embodiment of the present invention.
FIG. 6A is a screenshot of an example interface for presenting details of a detected "improve" mode, according to a specific embodiment of the present invention.
FIG. 6B is a screenshot of an example interface for presenting details of a detected "effort" mode, according to a specific embodiment of the present invention.
FIG. 7 is a block diagram illustrating an example architecture of a system software architecture according to an embodiment of the present invention.
FIG. 8 is a flow diagram depicting an example method for an Information and Motivational Behavior (IMB) module, according to an embodiment of the invention.
FIG. 9 is a block diagram depicting an example workflow in accordance with a specific embodiment of the present invention.
FIG. 10 is a block diagram illustrating details of an exemplary Information and Motivational Behavior (IMB) module portion of a system software architecture according to an embodiment of the present invention.
Fig. 11-31 are flowcharts depicting various example methods for detecting patterns in accordance with embodiments of the present invention.
Fig. 32-35 are flowcharts depicting various example methods of transitioning in a schema map flow in accordance with a specific embodiment of the present invention.
Detailed Description
For the purposes of promoting an understanding of the principles of embodiments of the invention, reference will now be made to the examples illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, and any alterations and further modifications in the illustrated embodiments, and any further applications of the principles of the invention as illustrated therein as would normally occur to one skilled in the art to which the invention relates are contemplated herein.
Embodiments of the present invention provide systems, devices and methods for improving a Diabetes Management System (DMS). In order to control their disease, diabetic patients (each referred to as "PWD") typically test their blood glucose levels multiple times a day and track their carbohydrate intake, exercise, and insulin dosage. To record these pointers and ensure that they remain in the test scenario, the PWD may manually track the messages by a paper pen, by a computer, or on a smart device. However, identifying multiple patterns on blood glucose readings over time is useful for PWDs to better manage their health. Examples of such patterns include critical low meter reading, critical high meter reading, low frequency of testing, medium frequency of testing, good frequency of testing, mostly simultaneous testing, high time of day, low time of day, best time of day, high fasting, low fasting, high before lunch, low before lunch, high before breakfast, low before dinner, high after dinner, low after dinner, high gradually, low on monday, high on monday, and the like. The number of useful patterns and data involved in identifying these patterns is enormous, and it is impractical for a user to manually track all of the information required to identify the occurrence of a pattern, let alone detect the occurrence of an event in real time. Thus, embodiments of the present invention automate data collection and storage, as well as pattern recognition. Moreover, many patterns may occur and be detected in a relatively short length of time, which may present an excessive amount of notifications and reminders to the user. Embodiments of the present invention provide interface facilities and features to assist users in managing, filtering, and prioritizing notifications and reminders.
Embodiments of the present invention include software applications and systems adapted to provide an enhanced system for managing diabetes. Using a portable wireless device, such as, for example, a smartphone, to communicate with a blood glucose meter (BG meter, or BGM), embodiments of the invention include a software application, such as a DMS app, operable to receive blood glucose measurements and store the measurements in a DMS database to associate the measurements with user activities and patterns. Some embodiments of the present invention make the PWD more proactive in managing diabetes by allowing for the reception of reminders from the DMS App. Some PWDs may be less active in the management process because they are easily forgotten or not reminded. Providing a facility to receive reminders to test blood glucose, take medical measures, or perform other work related to diabetes management may help PWDs to participate more actively in their health management.
According to embodiments of the present invention, the user may set reminders within the DMS App that, when triggered, will instruct the user to test blood glucose levels, take medical measures, record activities, record carbohydrate intake, and/or any other diabetes related work. Alerts may be automatically triggered based on patterns identified by the DMS application in response to BGM data received by the DMS device of the user. In other words, in response to the DMS application identifying one or more patterns in the BGM data (e.g., group patterns that cooperatively indicate a particular condition state), the DMS application may generate and present suggestions, reminders, and/or alerts to the user. In some implementations, the presented reminders can be prioritized based on a user-defined priority and/or medical priority. Higher priority reminders may be presented before lower priority reminders, or higher priority reminders may be presented more strongly (e.g., in larger text, brighter highlighted prompts, different colors, sounds, etc.) and/or presented more frequently. In some embodiments, the frequency with which particular reminders are presented to a user may be constrained or limited. For example, if a user who has not recorded any motion for three days is presented with a reminder to record motion, then subsequent reminders triggered after three days for the same reason may be suppressed. In this way, redundant alerts are avoided from being applied to the user.
Turning now to fig. 1, an example of a
In some embodiments, a Health Care Provider (HCP) or user may operate the
Turning now to fig. 2, details of the
The processor 202 may be coupled to a display 208, and the display 208 may include any number of output devices (e.g., such as such displays, audio speakers, haptic devices, vibrators, Light Emitting Diodes (LEDs), printers, audio outputs, USB and LAN ports, etc.). The display 208 may be used to communicate with the user to present reminders as well-known output functions.
The processor 202 may be coupled to a wireless transceiver 210, and the wireless transceiver 210 may include cellular communication facilities and two-way radio signal communication facilities, such as Wi-Fi, bluetooth, and other communication modules. In other words, the wireless transceiver 210 may include any type of device and/or software capable of communicating over the
The processor 202 may be coupled to an input device 212, the input device 212 may include any number of input devices (e.g., such as a touch screen, soft "programmable buttons/keys, hardware buttons and switches, a keyboard, optical and magnetic readers/scanners, cameras, sensors, transducers, accelerometers, microphones, audio inputs, USB and LAN ports, etc.), for example. The input device 212 may be used to communicate with the user to set reminders or other parameters, as well as input functions as is well known.
The processor 202 may be coupled to a data storage device 214, such as a non-volatile memory, to allow persistent storage of data structures, data, and instructions that may be loaded into the memory 204 for use/execution by the processor 202. The data storage 214 may be implemented using one or more solid state drives, hard drives, memory cards, and the like. The data storage 214 includes data structures that may include a DMS App 216 (including an integrated pattern recognition engine 218 in some embodiments), a
The DMS App 216 implements the methods and procedures described herein. The DMS App 216 uses a pattern recognition engine 218 to implement actions (e.g., via recognizing patterns in the acquired BGM, via user input, and other data) that detect events that result in assistance or adverse events (e.g., good or bad glycemic control). An example of a pattern recognition system is disclosed in U.S. patent No. 8,758,245 issued to Ray et al, which is hereby incorporated for all purposes. An example of the
Turning now to FIG. 3, an example of a
Each entry in the illustrated
The blood
In some embodiments, the
FIG. 4 is a screenshot of an
Fig. 5A is a screenshot of an
FIG. 5B is a screenshot of an example schema
Fig. 6A is a screenshot of an
In an alternative embodiment, the DMS application may be implemented as part of an
FIG. 9 is a block diagram depicting an IMB workflow 900. When connected to the BG meter 902, the BG meter 902 may provide BG readings to a communication manager 904 within the application (e.g., via a Bluetooth Low Energy (BLE) protocol). The BG record manager 906 module will identify BLE data (e.g., whether the input data identifies a BG reading, meal flag, or set data), pause and reform the data into a corresponding record (e.g., blood glucose/meal flag record, etc.), and communicate the record to the database manager 908 for storage in the database. The database manager 908 will store the blood glucose/meal flag/device setting data in a database (e.g., SQLite database) and will perform data reading operations based on the database. Once the new BG reading arrives, the IMB manager 704 executes the IMB module and the IMB data will be stored in the database by the IMB schema manager and the IMB notification will be communicated to the IMB user interface 802 for display. The user interface manager 802 is the gateway to the
FIG. 10 depicts more details of the structure and components of the IMB manager 704. In some embodiments, the IMB manager 704 includes an IMB module 1002 and a schema manager module 1004. The IMB manager 704 also interacts with a reminder trigger module 1006.
The IMB module 1002 includes three sub-modules: an IMB data setting/verification sub-module 1008; an IMB algorithm execution sub-module 1010; and an IMB cache submodule 1012. Once a new BG reading is received, the IMB data setup/validation sub-module 1008 is utilized whether the BG reading is from a BG meter or a manual project. The IMB module 1002 will enter a setup mode, validate the data, and decide whether to execute the IMB algorithm. The setting or verification is done via: first fetch target range values, then reset the IMB cache 1012, check the IMB execution eligibility status based on the current/last execution BG timestamp, and then check and update the mode "timeout" status for the detected IMB mode in the mode manager module 1004. The IMB algorithm execution sub-module 1010 is responsible for executing IMB algorithms; updating the IMB cache for UI notifications 1012; and updates/inserts the newly detected pattern into the pattern manager module 1004. The IMB cache submodule 1012 acts as a local buffer and maintains information about the IMB mode currently being detected. The information may include an IMB ID and whether the mode is a deferred mode.
The schema manager module 1004 includes three sub-modules: an IMB status update submodule 1014; UI update sub-module 1016; and an IMB reminder updates sub-module 1018. The IMB state is an important property of the IMB pattern. The mode manager module 1004 updates the IMB mode state. The IMB status update submodule 1014 may include a number of status information. For example, the information may include detected New mode information, mode classification updates (e.g., active/sealed), mode status updates (e.g., read/unread), and mode status updates (e.g., New/Started/Hold Int/work/Hold/cat/call/alert/time/done/set/cancel/modified/Invalid/attention/needed/Improvement/timeout (d-Out)). In some embodiments, a New (New) state may be assigned to the newly detected Pattern, prior to presenting the Pattern Interface (Pattern Interface) screen to the user; the Started state may be assigned to a mode if the user selects to proceed from the IMB process on the mode Detection (Pattern Detection) screen; keep Int (On-Hold Int) state can be assigned to a mode if the user turns off the mode interface screen; the in-work (Working) state may be assigned to a mode if the user chooses to proceed from the IMB flow on the Possible reasons (Possible Cable) screen; keep the Cau (On-Hold Cau) state may be assigned to a mode if the user turns off the possible cause screen; the Reminder set (Rem-Setup) state may be assigned to a mode if the user chooses to proceed from the IMB process on the Reminder required (Need Reminder) screen; the Dismissed _ Rem state may be assigned to mode if the user chooses not to start with an IMB flow on the reminder required screen; the completed (Finished) state may be assigned to a mode if the user completes and confirms setting reminders during the IMB flow for all other modes; a unset _ Setup state may be assigned to the mode if the user does not confirm the Reminder Setup (i.e., turns off the Reminder Setup screen); improved (Improved) state may be assigned to a pattern in the following two cases: (1) after positive feedback is obtained after follow-up; and (2) resolving the schema if the new or changed recording contribution; after obtaining negative feedback after follow-up, a tracking (Followed) state may be assigned to the mode; the need to improve (records Improvement) state may be assigned to Critical (Critical) mode if before mode Improvement or before mode timeout; an Overcorrected (Overcorrected) state may be assigned to a Critical High (Critical High) or Critical Low (Critical Low) mode if found after retesting BG records; and a timeout (Timed-Out) state may represent each mode having a predetermined time period, wherein the timeout state will be specified. Once the mode times out, the mode moves to the sequestration zone (see description below). The active mode may time out if not improved in the exclusive period of the mode.
The UI update sub-module 1016 is responsible for presenting IMB patterns detected in the UI. If an alert has been generated during the IMB mode flow, the IMB alert update sub-module 1018 performs an update to the alert ID for the corresponding IMB mode and an update to the IMB alert trigger state. The reminder trigger module 1006 represents a UI 1020 or native 1022 (e.g., Android or IOS) notification center that initiates generation of a reminder, triggers the reminder, and updates the status of the reminder.
The IMB module 1002 may be configured to recognize and manage any number of patterns. The following twenty-one modes are described in detail below: critical high meter reading, critical low meter reading, low test frequency, medium test frequency, good test frequency, mostly simultaneous testing, high time of day, low time of day, best time of day, high fasting, low fasting, high before lunch, low before lunch, high before dinner, low after dinner, gradually high, gradually low, low on monday, and high on monday.
The IMB module 1002 informs the user of detected patterns from the user's history of BGM data (e.g., records from the DMS database 220) and provides a mechanism for better management of diabetes. In some embodiments, the IMB mode detection will generally look at a BGM data history for 14 days. Note, however, that some modes consider a history of up to 21 days, while some modes use only a single BG reading. If the user enters an annotation on any applicable IMB interface screen, this annotation will be stored in the DMS database and the associated BG readings can be viewed in an Edit View/Notes (Edit View/Notes) tab.
DMS App 216 initiates execution of the IMB algorithm (e.g., triggering an IMB mode) via IMB algorithm execution sub-module 1010, either when DMS App 216 acquires one or more new BG records, or when an existing (e.g., previously acquired) BG record is modified. Each IMB algorithm accepts similar inputs including a group BG record, each input having a BG read value (referred to herein as BGRecordValue) and a BG read timestamp (referred to herein as BGRecordTimeStamp). Further, each of the IMB algorithms accepts additional inputs, such as, for example, a threshold value and/or a target value. Each of the example IMB algorithms described herein is used to trigger a corresponding pattern based on BG readings and time.
Each algorithm has the same output type: a BOOLEAN (BOOLEAN) value of "0" if no associated pattern is detected and "1" if an associated pattern is detected. As previously described, the output of the IMB algorithm is one of the inputs to the schema manager module 1004. If a particular mode is detected, the mode manager module 1004 triggers notification of the new mode. Upon recognition of this notification, a series of UI messages (e.g., screen displays), called IMB Pattern Maps (IMB Pattern Maps), will be presented to the user in sequence according to the selection hierarchy made by the user on each screen. The IMB modes can be classified into critical IMB modes and non-critical IMB modes.
An example of an algorithm or method 1100 for recognizing a critical low pattern is illustrated as a flow chart in fig. 11. When a new BG record is acquired (or when a previously acquired record is modified), the DMS App will trigger this mode if the BG record value is below a value specified as CriticalLowThreshold. The method 1100 begins when a new BG record is acquired (or when a previously acquired record is modified) (1102). A most recent BG record is taken (1104), and it is determined whether the blood glucose value is less than the stored parameter CriticalLowThreshold (1106). If so, a critically low mode is triggered (i.e., detected) and the mode manager module 1004 is notified (1108) by the IMB algorithm execution sub-module 1010 and the method 1100 is complete (1110). If not, the method 1100 is directly complete (1110).
An example of an algorithm or method 1200 for recognizing a critical high pattern is illustrated as a flow chart in FIG. 12. When a new BG record is acquired (or when a previously acquired record is modified), the DMS App will trigger this mode if the BG record value is higher than the value specified as criticai highthreshold. The method 1200 begins (1202) when a new BG record is acquired (or when a previously acquired record is modified). A most recent BG record is taken (1204) and it is determined whether the blood glucose value is greater than the stored parameter CriticalHighThreshold (1206). If so, then the critically high mode is triggered (i.e., detected) and the mode manager module 1004 is notified (1208), and the method 1200 completes (1210). If not, then the method 1200 is directly complete (1210).
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or method 2700 for recognizing a low pattern after dinner is illustrated as a flow chart in FIG. 27. Method 2700 begins when a new BG record is acquired (or when a previously acquired record is modified) (2702). When a new BG record is acquired (or when a previously acquired record is modified), the DMS App will trigger this mode if it detects numcondthreshold (data within two weeks from the timestamp of the latest BG reading) that is below the predetermined parameter PostMealLowTarget or more consecutive BG readings that occur within a dinner minute and that are marked "before dinner" with a meal. BG readings were taken for the last two weeks (2704). The BG record index "Current" is initialized to zero (2706) and the count "numcos" is initialized to zero (2708). A check is made to determine if the index reaches the latest BG record (2710). If so, method 2700 completes directly without triggering 2724. If not, then the value of the current BG record is compared to PostMealLowTarget (2712). If the value of the current BG record is greater than PreMealLowTarget, the index is incremented (2714) and flow returns to reset the count "NumCons" to zero (2708). Otherwise, numcos is incremented (2716) and it is checked whether numcos is greater than or equal to numcondthreshold (2718). If not, the index is incremented (2720) and flow returns to check to determine if the index has reached the latest BG record (2710). Otherwise (i.e., numcos is greater than or equal to NumCons threshold), late postprandial low-IMB mode is triggered (2722), and method 2700 is complete (2724). In other words, the first (most recent) BG reading with a value below premelallowtarget is found from the 14-day history. Counts counting the number of low readings after consecutive nights were incremented by 1. Check the previous BG reading. If the previous BG reading is above PostMealLowTarget, then the count is reset (NumCons ═ 0), the first next reading below PostMealLowTarget is found (look back), and the method 2700 starts over. If the previous BG reading is below PreMealLowTarget, then the count is incremented by 1 (NumCons. NumCons +1) and method 2700 proceeds in the same manner until the first reading above PreMealLowTarget is found. Once found, the count value is checked. If numcos > -NumCons threshold, then the mode is triggered, informing the mode manager module 1004 of the time range in which the mode was detected. The method 2700 starts from the beginning until the latest BG record is reached.
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
An example of an algorithm or
Within the IMB manager 704, a mode manager module 1004 is responsible for calling the aforementioned IMB algorithms (via IMB algorithm execution sub-module 1010), processing detected modes, generating and scheduling notifications for identified modes, scheduling execution of IMB mode maps (e.g., relevant user interface display and interaction menus), allowing the user to set mode targets, initiating and removing constraints and filters for mode notifications (e.g., Band/test frequency target/Quarantine (Band/Testing frequency goal/Quarantine)), continuing the process of managing modes by notification and reminder, providing informational, motivational, and behavioral messages, and recording the user's comments about the associated trigger mode, and BG records about the associated mode, if applicable.
The mode manager module 1004 communicates to the user that a mode has been newly detected by different means. The user may be presented with a notification of the detection of a particular mode, and subsequently a corresponding IMB mode map (depending on the user's decision). If more than one IMB pattern is detected, the DMS App may limit the notification to a single notification that includes multiple names of the detected patterns in a prioritized list for easy viewing of the patterns by the user. Further, the user may access the detected patterns via a pattern viewer that presents the patterns in an organized and prioritized manner. If the DMS App is active, the schema manager will take control of the screen of the smart device and present a "schema detection screen" -a notification of the detected schema in which the user is provided with the option to browse the schema map flow and is guided through the details and interpretation of the detected schema.
The mode manager operates based on the following parameters (defining each mode): band (Band), Type (Type), Rank (Rank), Quarantine (Embargo) period, latency (Incubation) period, and minimum time interval. The band parameters represent a hierarchy of "mode feedback" in which the user may choose not to be notified of all modes detectable by the mode manager. In other words, even if the mode manager detects a particular mode, this event will not be communicated to the user as a notification of the detection of a new mode if the band selected by the user does not include this particular mode (e.g., "out-of-band" mode) (as opposed to the case of "in-band" mode).
The following table provides example settings for organizing patterns into bands. The user may select which mode bands to receive notification.
The Type (Type) parameter represents the grouping of all patterns based on the event Type of the trigger pattern. This is relevant when multiple patterns are detected simultaneously. For example, persistent hyperglycemia is estimated in several different ways. This allows the DMS to avoid bombarding the user with seemingly redundant individual alarms for patterns of similar nature.
The level parameter represents a priority level for a particular mode. A rank parameter is assigned to each pattern in the group (type) and is unique to this particular pattern within the type (in some embodiments, no two patterns within the same type have the same rank). Only one mode of each type is automatically set to the "Active" state by the mode manager. This will be the mode with the highest priority. For example, a "gradually high" mode and a "high after dinner" mode may be triggered simultaneously. "progressively higher" may be a sign of a potential acute abnormality, while "high after dinner" may indicate a need for drug adjustment. Consideration of acute anomalies would be a higher priority pattern to alert the user.
The parameters also prevent the user from being overwhelmed by notifications during quarantine (barring). If the user is notified of a particular mode at the "now" point, the mode manager ensures that the user will not receive the same mode notification until the quarantine period expires. This means that the maximum block time that this particular mode will be allowed to trigger again, is the "now" point in time plus the isolation period. This feature also ensures that the user has time to react to improve or handle a particular mode before being alerted. The following table plots illustrate example isolation periods:
the latency period (MinReqBGhistory) parameter relates to the start of the DMS App. To ensure accuracy, the App delays responding to some triggered patterns until sufficient blood glucose data has been received to improve reliability for recognition and adjudication patterns. Thus, App uses a "benefit period" (MinReqBGhistory) in which triggered patterns belonging to some groups are ignored.
The minimum time interval (MinReqBGrecordTimeDiff) parameter, representing the minimum allowable difference between the timestamps of two consecutive BG records, to be included in the algorithmic calculations for detecting, dismissing or improving a particular IMB pattern. This feature prevents multiple readings taken around the same time from being counted as a pattern.
Patterns are characterized and presented in three different categories: active, Additional, and encapsulated. The active mode is a newly recognized mode (whether read or unread), which is currently processing data that is considered the highest priority information that should alert the user. The "active" mode is kept as small as possible at any time to prevent the user from being overwhelmed with information. The goal of the "active" mode is to drive the user through a particular mode map process (user interface) at which the user can achieve an "improved" or "tracked" state. Priority levels ("levels") and "types" are considered to determine the active mode. Further, the user may select any of the Additional (Additional) modes to promote to active if the user wants to participate in attempting to process more mode map flows. The number of active modes that may exist may be the same as the number of mode "types", e.g., critical modes (critical high and critical low) as one type, and three other mode types in addition to the critical mode. The active class fills before the additional classes start filling. The mode details page is accessed by selecting the mode. The unread mode will prompt the user through the mode map flow. Selecting the unread mode changes the mode state to "open" (Read). If a critical mode is detected, this mode will be raised to the top of the active list when triggered and held there until resolved-a non-critical mode in the same extreme range is taken, or the sequence is "complete". When the mode becomes active, a "timeout" timer for the "active" mode is started. In some embodiments, the DMS App prevents more than one pattern from the same type from being active at the same time, regardless of the total number of active patterns.
An "additional" mode is a recognized mode, read or unread, that is announced, does not collect data, and will not automatically change to an "improved" state. The additional classification mode is given more time than active (to give the user more time to act) before timing out and moves to the sequestration section of the mode viewer. Additional classification modes are determined by priority level ("level"), "type", and date of detection. There is no limit to the number of additional modes presented in the mode viewer. To view the additional mode, the user selects the additional mode and displays the mode details (in the upper half of the mode details page) along with the question: "do you want to know this mode better, try to improve it and move it to active mode? The answer is the mode map flow that will bring the user into this mode and move this mode to active. The answer "no" will keep the mode in the append and the question as available. To change the additional mode to active, the user may answer questions indicating that they want to struggle with the mode. By moving the additional mode to the active mode, the mode is added to the active section of the mode viewer screen.
The "sequestration" mode is assigned to this classification by the DMS App when they reach one of the following states: dismissed _ reminders, Completed (Finished), Dismissed _ Setup (Dismissed _ Setup), Improved (Improved), tracked (fallen), Improved-Rework (Improved-Rework), Improved-Completed (Improved-Completed), Improved-Modified (Improved-Modified), tracked-Rework (fallen-Rework), tracked-Completed (fallen-Completed), Good _ Int, Good _ Note, Good _ Add, or timeout (d-Out).
In some embodiments, the pattern manager may automatically transition the detected pattern to another classification, condition, and/or state in response to a new BG record, or after a predetermined amount of time has elapsed. For example, if the conditions shown below are met, the pattern manager may change the pattern classification belonging to the active classification to a sequestered classification and specify an improved state:
in some embodiments, if the active mode improves before the follow-up time (based on receiving a new BG record), the mode manager may present an "improved follow-up" screen and move the mode to a sequestration category with an "improved" state. In some embodiments, if the active mode improves before the follow-up time (based on receiving a new BG record), the mode manager may cancel (via the mode map flow) the regularly scheduled "follow-up" notifications and associated reminders (if they were set during the mode map flow).
In some embodiments, the pattern manager may change a pattern classification belonging to the "active" classification to the "sequestered" classification, and specify a "time out" state if, within a time period specified in the following table, none of these events have occurred:
mode is not improved; or
The user does not go through the entire mode map flow to set follow; or
The pattern is never read.
In some embodiments, the timeout period may count down from the Pattern registration time (Pattern registration moment). If the active mode times out (based on time), the mode manager may move the mode and timeout states to the sequestration class without notifying the user.
In some implementations, transitions within the schema map flow can occur. For example, during a pattern map flow, the pattern manager may specify classifications, conditions, and/or states for transitions within the pattern map flow after a trigger according to algorithm or method 3200, as illustrated in the flow chart of fig. 32, and specify classifications, conditions, and/or states for transitions within the pattern map flow (active classification not on state) upon access from the pattern manager according to algorithm or method 3300, as illustrated in the flow chart of fig. 33, for the following patterns:
hollow height
Empty stomach low
Height before lunch
Low before lunch
High before dinner
Before dinner, the lower part
High after a night meal
Low after a night meal
High recently
Recently low
When the day of the week is low
When the height is higher on the weekday
As illustrated in fig. 32, in response to a trigger mode at processing module 3201, method 3200 may proceed to detection screen decision module 3202, where the result may generate a mode transition 3203 or 3204. From mode transition 3204, method 3200 may proceed to interpretation screen decision module 3205, where the result may generate mode transition 3206 or 3207. From mode transition 3207, method 3200 may proceed to possible cause decision module 3208, where the result may generate mode transition 3209 or 3210. From mode transition 3210, method 3200 may proceed to alert? Decision module 3211, where the result may result in a mode transition 3212 or 3213. From mode transition 3213, the method 3200 may proceed to a reminder set decision module 3214, where the result may generate a mode transition 3215 or 3216. From mode transition 3216, the method 3200 may proceed to follow feedback decision module 3217, where the result may generate mode transition 3218 or 3219.
As illustrated in fig. 33, in response to accessing an active (unread) mode from the mode manager at processing module 3301, method 3300 may proceed to interpretation screen decision module 3302, where the result may generate a mode transition 3303 or 3304. From mode transition 3304, method 3300 may proceed to possible cause decision module 3305, where the result may yield mode transition 3306 or 3307. From mode transition 3307, method 3300 may proceed to alert? Decision block 3308, where the result may produce a mode transition 3309 or 3310. From the mode transition 3310, the method 3300 may proceed to the alert setting decision module 3311, where the result may result in a mode transition 3312 or 3313. From the mode transition 3313, the method 3300 may proceed to follow feedback decision module 3314, where the result may result in a mode transition 3315 or 3316.
In some embodiments, other transitions within the pattern map flow may additionally or alternatively occur. For example, during a pattern map flow, the pattern manager can specify classifications, conditions, and/or states according to an algorithm or
critical low
Critical height
As illustrated in fig. 34, in response to triggering the critical mode at the
In some implementations, transitions within the schema map flow can occur as a result of user actions within the schema manager viewer. Taken to the contrary, the pattern manager may change the classification, status, and/or state of the active pattern based on user interaction within the pattern manager viewer, according to an algorithm or method 3500 (in some embodiments) to transition within the pattern map flow upon a trigger, as illustrated by the flow diagram of fig. 35. When the user selects the active mode at the
In some embodiments, in addition to the information provided in the usual "mode interpretation" screen, the "modified mode interpretation" screen may allow the user to: (1) view a record of the contribution to this detected pattern (starting with the first reading of the contribution to the detected pattern and ending with the reading of the trigger pattern); (2) recording the annotation; (3) viewing a related reminder set during a mode map procedure; and (or) (4) a sequestration mode.
In some embodiments, upon the user selecting the active mode (and selecting "sealed mode" in the "modified mode interpretation" screen), the mode manager may designate this mode as the "Dismissed" state in the mode viewer and change the actual state of this mode to "Finished _ Dismissed". In some embodiments, the schema manager may allow a "sealed" schema to change state from Unopened (unopended) to opened (Opended) (only in the schema manager, not in the schema viewer). In some embodiments, the schema manager may not allow "canned" schemas to change classifications and conditions.
In some embodiments, upon a user selecting a sequestration mode in the "dismiss" ("dismiss reminder", "dismiss setting") or "timeout" state, the mode manager may display a "modified mode interpretation" screen at the
In some embodiments, upon a user selecting a sequestration mode in the "improve" or "track" state, the mode manager may display a "modified mode interpretation" screen that may allow the user to, in addition to information provided in the usual "mode interpretation" screen: (1) a viewing state; (2) selecting from the following options: (a) viewing a record of the contribution to this detected pattern with or without improvement (tracking) (indicating the beginning of the first reading of the contribution to the detected pattern and ending with the most recent reading of the relevant pattern before the expiration of the following period); (b) recording the annotation; and (c) view the associated reminders set during the mode map procedure.
In some embodiments, when the user selects a containment mode belonging to the Critical mode group, the mode manager may display a Critical mode following (Critical Pattern Follow-Up) screen that may allow the user to, in addition to the information provided in the usual "mode interpretation" screen: (1) a viewing details state interpretation; (2) recording the annotation; and (3) view relevant readings set during the pattern map procedure (e.g., all readings beginning with the reading that triggered the pattern and ending with the most recent reading on the pattern recorded before the pattern improvement time (or before the pattern timeout period expires).
In some embodiments, the critical mode may precede the non-critical mode, and the mode manager may store and not allow manual deletion of any active or sequestered modes. In some embodiments, up to 50 recent active and sealed patterns (i.e., first-in-first-out) may be stored and maintained for up to 90 days, wherein patterns over 90 days may be deleted.
Returning to fig. 35, the
Several embodiments are described in this disclosure, which are presented for purposes of illustration only. The described embodiments are not to be taken in a limiting sense (and are not intended to be limiting). It will be apparent from this disclosure that the invention disclosed herein is widely applicable to a variety of embodiments. Those skilled in the art will recognize that the disclosed invention may be practiced with various modifications and alterations (e.g., structural, logical, software, and electrical modifications). Although particular features of the disclosed invention may be described with reference to one or more particular embodiments and/or drawings, it should be understood that such features are not limited to use in describing the particular embodiment or embodiments or drawings to which such features are referred, unless otherwise expressly specified.
This disclosure is neither a literal description of all embodiments nor a listing of features of the invention that must be present in all embodiments.
The name of the invention (set forth at the beginning of the first page of the disclosure) should not be construed as limiting the scope of the disclosed invention in any way.
The term "article" means any machine, manufacture, and/or composition of matter as claimed in clause 21 of the patent Law, unless explicitly stated otherwise.
Each procedure (whether referred to as a method, a generic act, an algorithm, or otherwise) inherently includes one or more steps, and thus, all references to one or more "steps" of a procedure have an inherent antecedent basis for a mere recitation of the term "procedure" or similar terms. Accordingly, any reference in the claims to one or more "steps" of a program has sufficient antecedent basis.
Where a ordinal number (such as "first", "second", "third", etc.) is used as an adjective before a term, such ordinal number (unless otherwise expressly specified) is used merely to indicate a particular feature, such as to distinguish one particular feature from another feature described by the same or similar terms. For example, the name of "first widget" is simply distinguished from (e.g., "second widget"). Thus, the use of the sequence numbers "first" and "second" before the term "widget" does not indicate any other relationship between the two widgets, and similarly, does not indicate any other characteristic of either or both widgets. For example, the sequence numbers "first" and "second" are used before the term "widget": (1) it does not indicate that any widget is in front of or behind any other widget in order or position; (2) does not indicate that any widget occurs before or after any other widget in time; and (3) does not mean that any widget is higher or lower in importance or quality than any other widget. Furthermore, the use of serial numbers does not define a numerical limit on the features identified by the serial numbers. For example, the use of the sequence numbers "first" and "second" before the term "widget" does not indicate that there should be no more than two widgets.
Where a single device, component, structure, or article is described herein, more than one device, component, structure, or article (whether or not they cooperate) may be used instead of a single device, component, or article as described. Thus, functionality described as being possessed by a device may alternatively be possessed by more than one device, component, or article (whether or not they cooperate).
Similarly, where more than one device, component, structure, or article is described herein (whether or not they cooperate), a single device, component, structure, or article may alternatively be used in place of the more than one device, component, structure, or article described. For example, multiple computer-based devices may be replaced by a single computer-based device. Thus, various functionalities described as being possessed by more than one device, component, structure, or article may instead be possessed by a single device, component, structure, or article.
The functionality and/or the features of a single means illustrated may be alternatively embodied by one or more other means which have been illustrated but which have not been explicitly illustrated as having such functionality and/or features. Thus, other embodiments need not include the illustrated device itself, but may relatively include one or more other devices having such functionality/features in such other embodiments.
Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. Rather, such devices need only send to each other when necessary or desired, and may actually stop exchanging data for most of the time. For example, a machine that communicates with another machine via the internet may not send data to the other machine for weeks. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.
The description of a particular embodiment with several components or features does not imply that all (or even any) of such components and/or features are required. On the contrary, various optional components are described to illustrate the wide variety of possible embodiments of the present invention. No element and/or feature is essential or required unless explicitly stated otherwise.
Also, while process steps, algorithms or the like may be described as having a sequential order, such programs may be configured to work in a different order. In other words, the order or sequence of any steps that may be explicitly described does not necessarily indicate a need to perform the steps in that order. The process steps described herein may be performed in virtually any order. Also, some steps may be performed concurrently, although illustrated (or implicitly) as occurring non-concurrently (e.g., because one step is illustrated after another step). Moreover, the illustrations of the programs depicted in the drawings are not meant to imply that the illustrated programs preclude other variations and modifications, are not meant to imply that the illustrated programs (or any steps thereof) are essential to the invention, and are not meant to imply that the illustrated programs are preferred.
While a process may be described as including multiple steps, this does not imply that all (or even any) of the steps are necessary or desirable. Various other embodiments within the scope of the described invention include other procedures in which some or all of the described steps are omitted. No step is necessary or required unless explicitly stated otherwise.
Although an article may be described as including a plurality of components, aspects, qualities, characteristics, and/or features, this does not imply that all of these plurality of components, aspects, qualities, characteristics, and/or features are necessary or desirable. Various other embodiments within the scope of the described invention include other articles in which some or all of the various components, aspects, qualities, characteristics and/or features described are omitted.
The listed objects (which may or may not have a number) do not imply that any or all of the objects are mutually exclusive unless expressly stated otherwise. Similarly, the listing of objects (which may or may not have a number) does not imply that any or all of the objects are comprehensive of any classification unless explicitly stated otherwise. For example, the listing of "computer, laptop, PDA" does not imply that any or all of the three objects of this list are mutually exclusive, and does not imply that any or all of the three objects of this list are comprehensive for any classification.
The section headings provided in this disclosure are for convenience only and should not be construed as limiting this disclosure in any way.
Determining things can be performed in a variety of ways, and thus, the term determining (and similar terms) includes calculating, computing, deriving, looking up (e.g., in a table, database, or data structure), confirming, recognizing, and the like.
The term "display," as used herein, is an area that conveys information to a viewer. The information may be dynamic, in which case LCD, LED, CRT, Digital Light Processing (DLP), rear projection, front projection, etc. may be used to form the display.
The present disclosure may refer to a "control system," an application program, or a program. The terms used herein: the control system, application program, or program may be a computer processor coupled with an operating system, device drivers, and appropriate programs (collectively referred to as "software"), and having instructions to provide the functionality illustrated for the control system. The software is stored in an associated memory device (sometimes referred to as a computer-readable medium). While it is contemplated that a suitably programmed general purpose computer or computing device may be used, it is also contemplated that hardwired circuitry or custom hardware, such as an Application Specific Integrated Circuit (ASIC), may be used in place of or in combination with software instructions of a program to implement various specific embodiments. Thus, embodiments are not limited to any specific combination of hardware and software.
"processor" means any one or more microprocessors, Central Processing Unit (CPU) devices, computing devices, microcontrollers, digital signal processors, or the like. An exemplary processor is an INTEL PENTIUM or AMD ATHLON processor.
The term "computer-readable medium" represents any suitable medium that participates in providing data (e.g., instructions), which may be read by a computer, processor or similar device. Such a medium may take many forms, including but not limited to, non-volatile media, and transmission media of a particular proprietary type. Non-volatile media includes, for example, optical or magnetic disks and other persistent memory. Volatile media include DRAM, which typically constitutes a main memory. Suitable types of transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to the processor. Common forms of computer-readable media include, for example, magnetic disks, floppy disks, hard disks, magnetic tape, any other magnetic medium, CD-ROMs, Digital Video Disks (DVDs), any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAMs, PROMs, EPROMs, FLASH-EEPROMs, USB memory sticks, server keys (dongle), any other memory chip or cartridge, carrier wave, or any other medium from which a computer can read. The terms "computer-readable memory" and (or) "tangible medium" specifically exclude signals, waves and waveforms, or other intangible or non-transitory media (although readable by a computer).
Various forms of computer readable media may be involved in carrying a sequence of instructions to a processor. For example, the instruction sequence: (i) may be transferred from RAM to the processor; (ii) may be carried over a wireless transmission medium; and (or) (iii) may be formatted according to several formats, standards, or protocols. For a more exhaustive list of protocols, the term "network" is defined as follows and includes many exemplary protocols that may also be applied herein.
It will be readily apparent that the various methods and algorithms described herein may be implemented by a control system and/or that software instructions may be designed to perform the processes of the present invention.
Having described the database and/or data structures, one of ordinary skill in the art will appreciate that: (i) database structures alternative to those illustrated can be readily utilized; and (ii) other memory structures besides databases may be readily utilized. Any iconic description or illustration of any example database/data structure presented herein is an illustrative arrangement for the stored information representation. Any number of other arrangements may be utilized other than those suggested by, for example, the figures or other illustrated tables. Similarly, any illustrated database items, merely represent exemplary information; those of ordinary skill in the art will appreciate that the number and content of items may vary from those illustrated herein. Moreover, although databases may be depicted as tables, other formats (including relational databases, object-based models, hierarchical electronic archive structures, and/or distributed databases) may be used to store and manipulate the types of data described herein. Similarly, object methods or behaviors of the database may be used to implement various processes, such as the processes described herein. Further, the database may be stored locally in a known manner, or remotely from a device that accesses data in such a database. Further, while the database may be well known, the database may also be distributed and/or replicated among the various devices.
As used herein, "network" generally represents an information or computing network that may be used to provide an environment in which one or more computing devices may communicate with each other. Such devices may communicate directly or indirectly via a wired or wireless medium, such as the Internet, a LAN, WAN or Ethernet (or IEEE 802.3), token ring, or via any suitable communication means or combination of communication meansTMTime Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), General Packet Radio Service (GPRS), wideband CDMA (wcdma), Advanced Mobile Phone System (AMPS), digital AMPS (D-AMPS), IEEE802.11(WI-FI), IEEE 802.3, SAP, best systems (BOB), system-to-system (S2S), and the like. Note that if a video signal or large archive is communicated over a network, a broadband network may be used to ease the delay associated with the transmission of such large archive, however, this is not strictly required. Each device is adapted to communicate over such a communication means. Any number and type of machines may communicate via a network. Where the network is the internet, the communication over the internet may be through a website maintained by the computer on a remote server, or through a proprietary data network, including commercial online service providers, bulletin board systems, and the like. In other embodiments, the devices may communicate with each other via RF, cable TV, satellite link, etc. Where appropriate, encryption or other security means such as login account numbers and passwords may be provided to protect proprietary or confidential information.
Communications between the computer and the device may be encrypted by any of a variety of means well known in the art to ensure privacy and prevent fraud. Suitable cryptographic PROTOCOLS for enhancing system security are described IN APPLIED CRYPTOGRAPHY, PROTOCOLS, ALGORITHMS, AND SOURCE CODE IN C, John Wiley & Sons, inc.2d ed, 1996, by Schneier, which is incorporated herein by reference IN its entirety.
It will be readily apparent that the various methods and algorithms described herein may be implemented, for example, by appropriately programmed general purpose computers and computing devices. Typically, a processor (e.g., one or more microprocessors) will receive instructions from a memory or similar device and execute the instructions, thereby executing one or more programs defined by the instructions. Further, programs embodying such methods and algorithms may be stored and transmitted in a number of ways using a variety of media (e.g., computer readable media). In some embodiments, hard-wired circuitry or custom hardware may be used in place of or in combination with software instructions to implement programs of the various embodiments. Thus, embodiments are not limited to any specific combination of hardware and software. Thus, the description of the program equally describes at least one device for executing the program, and also at least one computer-readable medium for executing the program and/or a memory for performing the processing. An apparatus for performing a process may include components and devices (e.g., processors, input and output devices) adapted to perform the process. The computer readable medium may store program elements adapted to perform the method.
This disclosure provides those of ordinary skill in the art with an enabling description for implementing several embodiments and/or inventions. Some of these embodiments and/or inventions may not be claimed in this application but may nevertheless be claimed in one or more subsequent applications claiming benefit of the priority rights of this application. The applicant intends to submit additional applications seeking patents on subject matter that have been disclosed and allowed but are not claimed in this application.
The foregoing description discloses only exemplary embodiments of the invention. Modifications of the above disclosed apparatus and methods that fall within the scope of the invention will be readily apparent to those of ordinary skill in the art to which the invention pertains. For example, although the examples discussed above are shown with respect to the medical device market, particular embodiments of the present invention may be practiced with respect to other markets.
Therefore, while the present invention has been disclosed in connection with exemplary embodiments thereof, it should be understood that other embodiments may fall within the spirit and scope of the invention, as defined by the following claims.