Patent Publication Number: US-2017364660-A1

Title: Medical devices and related event pattern treatment recommendation methods

Description:
CROSS-REFERENCE TO RELATED APPLICATION(S) 
     This application is a continuation-in-part of U.S. patent application Ser. No. 15/132,126, filed Apr. 18, 2016, which claims the benefit of U.S. Provisional Patent Application Ser. No. 62/243,416, filed Oct. 19, 2015, the entire contents of which are incorporated by reference herein. 
    
    
     TECHNICAL FIELD 
     Embodiments of the subject matter described herein relate generally to medical devices, and more particularly, embodiments of the subject matter relate to generating reports for therapy management based on measurement data pertaining to preceding operation of a fluid infusion device. 
     BACKGROUND 
     Infusion pump devices and systems are relatively well known in the medical arts, for use in delivering or dispensing an agent, such as insulin or another prescribed medication, to a patient. A typical infusion pump includes a pump drive system which typically includes a small motor and drive train components that convert rotational motor motion to a translational displacement of a plunger (or stopper) in a reservoir that delivers medication from the reservoir to the body of a user via a fluid path created between the reservoir and the body of a user. Use of infusion pump therapy has been increasing, especially for delivering insulin for diabetics. 
     Control schemes have been developed that allow insulin infusion pumps to monitor and regulate a user&#39;s blood glucose level in a substantially continuous and autonomous manner. However, regulating blood glucose level is still complicated by variations in the response time for the type of insulin being used along with variations in a user&#39;s individual insulin response and daily activities (e.g., exercise, carbohydrate consumption, bolus administration, and the like). Additionally, manually-initiated deliveries of insulin prior to or contemporaneously with consuming a meal (e.g., a meal bolus or correction bolus) also influence the overall glucose regulation, along with various patient-specific ratios, factors, or other control parameters. 
     Physicians have recognized that continuous monitoring provides a greater understanding of a diabetic&#39;s condition. That said, there is also a burden imposed on physicians and other healthcare providers to adapt to continuous monitoring and incorporate the amount of data obtained therefrom in a manner that allows for a physician to meaningfully assist and improve patient outcomes. While automated reports can be generated based on the data, they can be difficult to parse or appear overwhelming to physicians, which given the limited time available to physicians, may discourage adoption and incorporation of continuous monitoring as part of their practice. Accordingly, there is a need to generate and provide information in a usable form that can be quickly and intuitively interpreted and applied. 
     BRIEF SUMMARY 
     Medical devices and related systems and operating methods are provided. An embodiment of a method of operating a medical device to deliver medication to a body of a patient, such as an infusion device delivering fluid to the body of the patient, is provided. The method involves identifying, based on measurement values for a physiological condition in the body of the patient, a plurality of event patterns within respective ones of a plurality of monitoring periods, prioritizing the plurality of event patterns based on one or more prioritization criteria, resulting in a prioritized list of event patterns, filtering the prioritized list based on one or more filtering criteria, resulting in a filtered prioritized list of event patterns, and providing, on a display device, a respective pattern guidance display for each respective event pattern of the filtered prioritized list. 
     An embodiment of a system including an infusion device and a computing device is also provided. The infusion device is operable to deliver fluid to a body of a patient based on measurement values for a physiological condition in the body of the patient obtained from a sensing arrangement, where the fluid influences the physiological condition. The computing device is communicatively coupled to the infusion device over a network to identify a plurality of event patterns within a plurality of monitoring periods based on the measurement values, prioritize the plurality of event patterns based on one or more prioritization criteria, filter the prioritized list of event patterns based on one or more filtering criteria, and generate a respective pattern guidance display for each respective event pattern of the filtered prioritized list. 
     An embodiment of a method of presenting information pertaining to operation of an infusion device to deliver insulin to a body of a patient is also provided. The method involves obtaining, by a computing device, historical glucose measurement data for the patient from a database and identifying, by the computing device based on the historical glucose measurement data, a plurality of event patterns within respective ones of a plurality of monitoring periods, wherein each monitoring period of the plurality of monitoring periods corresponds to a different time of day corresponding to a different subset of the historical glucose measurement data. The method continues by the computing device prioritizing the plurality of event patterns based on one or more of an event type associated with respective event patterns of the plurality of event patterns and the respective monitoring period associated with respective event patterns of the plurality of event patterns, filtering the prioritized list based on one or more filtering criteria, and generating a respective pattern guidance display for each respective event pattern of the filtered prioritized list. 
     In one embodiment, a system includes an infusion device operable to deliver fluid to a body of a patient based on measurement values for a physiological condition in the body of the patient from a sensing arrangement, the fluid influencing the physiological condition and a computing device communicatively coupled to the infusion device over a network to identify a plurality of event patterns within a plurality of monitoring periods based on the measurement values, prioritize the plurality of event patterns based on one or more prioritization criteria, filter the prioritized list of event patterns based on one or more filtering criteria, and generate a respective pattern guidance display for each respective event pattern of the filtered prioritized list, wherein the respective pattern guidance display for at least one respective event pattern of the filtered prioritized list includes a graphical representation of a remedial action. 
     In another embodiment, a method of presenting information pertaining to operation of an infusion device to deliver insulin to a body of a patient involves obtaining, by a computing device, historical glucose measurement data for the patient from a database, identifying, by the computing device, a plurality of event patterns within respective ones of a plurality of monitoring periods based on the historical glucose measurement data, wherein each monitoring period of the plurality of monitoring periods corresponds to a different time of day corresponding to a different subset of the historical glucose measurement data, prioritizing, by the computing device, the plurality of event patterns based on one or more of an event type associated with respective event patterns of the plurality of event patterns and the respective monitoring period associated with respective event patterns of the plurality of event patterns, resulting in a prioritized list of event patterns, identifying, by the computing device, a remedial action associated with a highest priority event pattern of the prioritized list, and generating, by the computing device, a pattern guidance display for the highest priority event pattern of the prioritized list, wherein the pattern guidance display includes a graphical representation of the remedial action. 
     In another embodiment, a system is provided that includes a display device having rendered thereon a snapshot graphical user interface display comprising a pattern detection region including a plurality of pattern guidance displays corresponding to a plurality of event patterns detected within a time period corresponding to the snapshot graphical user interface display. The plurality of pattern guidance displays corresponding to the plurality of event patterns are prioritized primarily based on a respective event type of a plurality of event types associated with each respective event pattern of the plurality of event patterns and secondarily based on a respective monitoring period associated with each respective event pattern of the plurality of event patterns, and a highest priority pattern guidance display of the plurality of pattern guidance displays includes graphical indicia of a therapeutic remedial action corresponding to a highest priority event pattern of the plurality of event patterns corresponding to the highest priority pattern guidance display. 
     This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       A more complete understanding of the subject matter may be derived by referring to the detailed description and claims when considered in conjunction with the following figures, wherein like reference numbers refer to similar elements throughout the figures, which may be illustrated for simplicity and clarity and are not necessarily drawn to scale. 
         FIG. 1  depicts an exemplary embodiment of a snapshot graphical user interface (GUI) display that may be presented on a display device associated with a computing device in one or more embodiments; 
         FIG. 2  depicts an exemplary embodiment of a patient management system  200  suitable for generating and presenting the snapshot GUI display of  FIG. 1 ; 
         FIG. 3  is a flow diagram of an exemplary snapshot presentation process suitable for use with the patient management system of  FIG. 2  to generate a snapshot GUI display in one or more exemplary embodiments; 
         FIG. 4  is a flow diagram of an exemplary pattern guidance presentation process suitable for use with the patient management system of  FIG. 2  in conjunction with the snapshot presentation process of  FIG. 3  to populate an event pattern detection region of a snapshot GUI display in one or more exemplary embodiments; 
         FIG. 5  depicts an embodiment of a computing device for a diabetes data management system in accordance with one or more embodiments; 
         FIG. 6  depicts an exemplary embodiment of an infusion system; 
         FIG. 7  depicts a plan view of an exemplary embodiment of a fluid infusion device suitable for use in the infusion system of  FIG. 6 ; 
         FIG. 8  is an exploded perspective view of the fluid infusion device of  FIG. 7 ; 
         FIG. 9  is a cross-sectional view of the fluid infusion device of  FIGS. 7-8  as viewed along line  9 - 9  in  FIG. 8  when assembled with a reservoir inserted in the infusion device; 
         FIG. 10  is a block diagram of an exemplary control system suitable for use in a fluid infusion device, such as the fluid infusion device of  FIG. 2, 6 or 7 ; 
         FIG. 11  is a block diagram of an exemplary pump control system suitable for use in the control system of  FIG. 10 ; 
         FIG. 12  is a block diagram of a closed-loop control system that may be implemented or otherwise supported by the pump control system in the fluid infusion device of  FIG. 10  in one or more exemplary embodiments; 
         FIG. 13  is a flow diagram of an exemplary recommendation process suitable for use with the patient management system of  FIG. 2  to recommend remedial actions in conjunction with the snapshot presentation process of  FIG. 3  or the pattern guidance presentation process of  FIG. 4 ; and 
         FIGS. 14-16  depict exemplary embodiments of snapshot GUI displays that may be presented on a display device associated with a computing device in accordance with one or more embodiments of the recommendation process of  FIG. 13 . 
     
    
    
     DETAILED DESCRIPTION 
     The following detailed description is merely illustrative in nature and is not intended to limit the embodiments of the subject matter or the application and uses of such embodiments. As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Any implementation described herein as exemplary is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description. 
     Exemplary embodiments of the subject matter described herein are implemented in conjunction with medical devices, such as portable electronic medical devices. Although many different applications are possible, the following description focuses on embodiments that incorporate a fluid infusion device (or infusion pump) as part of an infusion system deployment. For the sake of brevity, conventional techniques related to infusion system operation, insulin pump and/or infusion set operation, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail here. Examples of infusion pumps may be of the type described in, but not limited to, U.S. Pat. Nos. 4,562,751; 4,685,903; 5,080,653; 5,505,709; 5,097,122; 6,485,465; 6,554,798; 6,558,320; 6,558,351; 6,641,533; 6,659,980; 6,752,787; 6,817,990; 6,932,584; and 7,621,893; each of which are herein incorporated by reference. That said, the subject matter described herein can be utilized more generally in the context of overall diabetes management or other physiological conditions independent of or without the use of an infusion device or other medical device (e.g., when oral medication is utilized), and the subject matter described herein is not limited to any particular type of medication. 
     Generally, a fluid infusion device includes a motor or other actuation arrangement that is operable to linearly displace a plunger (or stopper) of a reservoir provided within the fluid infusion device to deliver a dosage of fluid, such as insulin, to the body of a user. Dosage commands that govern operation of the motor may be generated in an automated manner in accordance with the delivery control scheme associated with a particular operating mode, and the dosage commands may be generated in a manner that is influenced by a current (or most recent) measurement of a physiological condition in the body of the user. For example, in a closed-loop operating mode, dosage commands may be generated based on a difference between a current (or most recent) measurement of the interstitial fluid glucose level in the body of the user and a target (or reference) glucose value. In this regard, the rate of infusion may vary as the difference between a current measurement value and the target measurement value fluctuates. For purposes of explanation, the subject matter is described herein in the context of the infused fluid being insulin for regulating a glucose level of a user (or patient); however, it should be appreciated that many other fluids may be administered through infusion, and the subject matter described herein is not necessarily limited to use with insulin. 
     Exemplary embodiments of the subject matter described herein generally relate to systems for analyzing and presenting information pertaining to operation of the infusion device delivering fluid to a body of a user. In exemplary embodiments, a snapshot graphical user interface (GUI) display is presented on an electronic device, and the snapshot GUI display includes or otherwise provides graphical representations or other graphical indicia of various aspects of the physiological condition in the body of the user that is regulated or otherwise influenced by the fluid delivered by the infusion device. For example, the snapshot GUI display may include graphical representations of a diabetic patient&#39;s glucose levels along with other indicia pertaining to the glycemic control achieved by the infusion device delivering insulin to the patient. 
     In exemplary embodiments described herein, the snapshot GUI display includes a pattern detection region that includes graphical indicia of event pattern(s) detected or otherwise identified based on measurement data for the user&#39;s physiological condition. The detected event pattern(s) are prioritized based on one or more prioritization criteria and filtered based on one or more filtering criteria, resulting in a filtered prioritized list of detected event patterns that includes only those event patterns to be presented to the user. For each retained event pattern in the filtered prioritized list, a respective pattern guidance display is generated or otherwise provided which includes information pertaining to that respective event pattern, such as, for example, an identification of the type of event pattern, an indication of a period of time associated with the event pattern, one or more metric(s) indicative of the frequency and/or severity of the event, and the like. Additionally, the pattern guidance display includes graphical indicia of one or more potential causes of event pattern, which, in turn may be utilized by the patient, the patient&#39;s doctor or other health care provider, or another individual in assessing the efficacy of the regulation achieved by the infusion device and identifying potential actions that may improve the quality of control achieved by the infusion device. As described in greater detail below in the context of  FIGS. 13-16 , in one or more embodiments, information pertaining to a displayed event pattern may be analyzed in connection with other therapeutic or physiological information associated with the patient to identify a remedial action that could potentially resolve, mitigate, correct or otherwise address the event pattern (e.g., adding a new medication, adjusting dosages or delivery rates, and the like) and provide corresponding graphical indicia of the remedial action in connection with the displayed event pattern. 
     Event Pattern Presentation 
       FIG. 1  depicts an exemplary embodiment of a snapshot GUI display  100  or report that may be presented on a display device associated with an electronic device, such as, for example, a computing device, a portable medical device, a sensor device, or the like. The snapshot GUI display  100  includes a plurality of regions  102 ,  104 ,  106 ,  108  that present information pertaining to past operation of a fluid infusion device that delivers insulin to regulate the glucose level of a diabetic patient. A header region  102  is presented at the top of the snapshot GUI display  100  and includes a graphical representation of a preceding time period of operation (e.g., November 3-November 6) associated with the snapshot GUI display  100  for which information is presented in the below regions  104 ,  106 ,  108 . 
     A graph overlay region  108  is presented at the bottom of the snapshot GUI display  100  that includes graphical representations of historical measurement data for the patient&#39;s glucose level over the snapshot time period with respect to time. In this regard, the graph overlay region  108  may include a line graph including a line associated with each day within the snapshot time period that depicts the patient&#39;s sensor glucose measurements values from that day with respect to time of day. Additionally, the graph overlay region  108  may include a line representative of the average of the patient&#39;s sensor glucose measurements across the different days within the snapshot time period with respect to time of day. The illustrated graph overlay region  108  also includes a visually distinguishable overlay region that indicates a target range for the patient&#39;s sensor glucose measurement values. In exemplary embodiments, the graphical representation of the measurements for each different day or date depicted on the graph overlay region  108  is rendered with a unique color or other visually distinguishable characteristic relative to the graphical representations corresponding to other days or dates, with the meal markers on that respective day or date also being rendered in the same color or visually distinguishable characteristic and placed on the line corresponding to that respective day or date. The illustrated graph overlay region  108  also includes graphical representations of multiday averages of the measurement data for different periods or times of day, for example, every three hour segment of the day (e.g., the average sensor glucose measurement for the 12 AM-3 AM time period across the dates encompassed by the snapshot time period is 189 mg/dL). 
     A performance metric region  104  is presented below the header region  102  and includes graphical representations or other indicia of the values for various performance metrics calculated based on the historical measurement data for the patient&#39;s glucose level over the time period associated with the snapshot GUI display  100 . The performance metrics depicted in the performance metric region  104  may include an average sensor glucose measurement value for the patient calculated based on the sensor glucose measurement values over the snapshot time period, an estimated A1C level calculated based on the sensor glucose measurement values over the snapshot time period, and estimated percentages of the snapshot time period during which durations the sensor glucose measurement values were above an upper glucose threshold value (e.g., 150 mg/dL), below a lower glucose threshold value (e.g., 70 mg/dL), or between the upper and lower glucose threshold values. In this regard, the upper and lower glucose threshold values may define a target region for the patient&#39;s glucose level during the snapshot time period. The threshold values defining the target region may be configurable by a user, for example, to vary one or more aspects of the report, or alternatively, to influence the glucose regulation provided by the infusion device while also influencing one or more aspects of the report. The graphical indicia for performance metrics presented in the performance metric region  104  may include textual representations of the respective performance metric values along with charts, graphs, or other visualizations of respective performance metric values. For example, the illustrated embodiment of the performance metric region  104  includes progress bar GUI elements that depict the respective percentages of the snapshot time period during which the patient&#39;s sensor glucose measurement values were above, below, or between upper and lower glucose threshold values. 
     Still referring to  FIG. 1 , the snapshot GUI display  100  also includes a pattern detection region  106  presented between the performance metric region  104  and the graph overlay region  108 . The pattern detection region  106  includes a plurality of pattern guidance displays  120 ,  130 ,  140 , where each pattern guidance display  120 ,  130 ,  140  corresponds to a respective pattern of events identified during the snapshot time period based on the patient&#39;s sensor glucose measurement values for the snapshot time period. In this regard, the historical sensor glucose measurement values are analyzed for different monitoring periods within the snapshot time period. As described in greater detail below in the context of  FIG. 3 , based on the subset of sensor glucose measurement values associated with times of day within a respective monitoring periods, a pattern of one or more events is detected or otherwise identified within that monitoring period, such as, for example, a glucose variability event, a high glucose (or hyperglycemic) event, or a low glucose (or hypoglycemic) event. After identifying a plurality of event patterns within respective monitoring periods, the identified event patterns are prioritized and filtered to limit the number of event patterns for display. For example, in one embodiment, the detected event patterns are prioritized primarily based on event type (e.g., from most significant to least significant) and secondarily based on the monitoring period associated with the respective event pattern, and then filtered to first remove lower priority event patterns having the same associated monitoring period as a higher priority event pattern, and then secondarily remove remaining event patterns above a display threshold that limits the number of displayed event patterns. In this regard,  FIG. 1  depicts an embodiment where the variability event type is prioritized above the hypoglycemic event type and the hyperglycemic event type in that order, and with the display threshold being equal to three to limit the number of pattern guidance displays within the pattern detection region  106  to three. 
     As described in greater detail below in the context of  FIG. 4 , for each remaining event pattern of the filtered prioritized list, a pattern guidance display  120 ,  130 ,  140  is generated that includes a header region  122 ,  132 ,  142  that includes graphical indicia of the event type and the monitoring period associated with the detected pattern, a summary region  124 ,  134 ,  144  that includes graphical indicia of the number, frequency, severity, or other characteristics of the events associated with the detected pattern, and an analysis region  126 ,  136 ,  146  that includes graphical indicia of potential causes or remedial actions for the detected events. It should be noted that the graphical indicia of potential causes or remedial actions may also be prioritized or ordered according to their respective clinical relevance. Additionally, in exemplary embodiments, graphical indicia  128 ,  138 ,  148  of the detected event patterns are presented within the graph overly region  108  in a manner that establishes an association between the detected event pattern, the time of day associated with its corresponding monitoring period, and its relative priority level. Thus, the graphical indicia  128 ,  138 ,  148  facilitate establishing an association between a respective subset of the historical measurement data presented within the graph overlay region  108  and a corresponding event pattern detected based on that subset of historical measurement data. For example, in the illustrated embodiment of  FIG. 1 , a marker  128  is presented overlying the graph overlay region  108  that includes an identifier that indicates the detected event pattern the marker  128  corresponds to (e.g., number  1  to indicate the highest priority event pattern  120 ), and the marker  128  has a width or other dimension that encompasses or otherwise corresponds to the subset of the sensor glucose measurement values associated with the time of day corresponding to the monitoring period associated with the detected event pattern (e.g., the lunch time period). 
       FIG. 2  depicts an exemplary embodiment of a patient management system  200  capable of generating and displaying the snapshot GUI display  100  of  FIG. 1  for review and analysis of a user. The patient management system  200  includes an infusion device  202  that is communicatively coupled to a sensing arrangement  204  to obtain measurement data indicative of a physiological condition in the body of a patient, such as sensor glucose measurement values as described in greater detail below in the context of  FIGS. 6-12 . In exemplary embodiments, the infusion device  202  operates autonomously to regulate the patient&#39;s glucose level based on the sensor glucose measurement values received from the sensing arrangement  204 . 
     In exemplary embodiments, the infusion device  202  periodically uploads or otherwise transmits the measurement data (e.g., sensor glucose measurement values and timestamps associated therewith) to a remote device  206  via a communications network  214 , such as a wired and/or wireless computer network, a cellular network, a mobile broadband network, a radio network, or the like. Additionally, in some embodiments, the infusion device  202  also uploads delivery data and/or other information indicative of the amount of fluid delivered by the infusion device and the timing of fluid delivery, which may include, for example, information pertaining to the amount and timing of manually-initiated boluses and associated meal announcements. Some examples of an infusion device uploading measurement and delivery data to a remote device are described in United States Patent Application Publication Nos. 2015/0057807 and 2015/0057634, which are incorporated by reference herein in their entirety. 
     The remote device  206  is coupled to a database  208  configured to store or otherwise maintain the historical measurement and delivery data received from the infusion device  202  in association with a patient associated with the infusion device  202  (e.g., using unique patient identification information). The remote device  206  generally represents a server or another suitable electronic device configured to analyze or otherwise monitor the measurement and delivery data obtained for the patient associated with the infusion device  202  and generate a snapshot GUI display (e.g., snapshot GUI display  100 ) that may be presented on the remote device  206  or another electronic device  210 , alternatively referred to herein as a client device. In practice, the remote device  206  may reside at a location that is physically distinct and/or separate from the infusion device  202 , such as, for example, at a facility that is owned and/or operated by or otherwise affiliated with a manufacturer of the infusion device  202 . For purposes of explanation, but without limitation, the remote device  206  may alternatively be referred to herein as a server. 
     In the illustrated embodiment, the server  206  generally represents a computing system or another combination of processing logic, circuitry, hardware, and/or other components configured to support the processes, tasks, operations, and/or functions described herein. In this regard, the server  206  includes a processing system  216 , which may be implemented using any suitable processing system and/or device, such as, for example, one or more processors, central processing units (CPUs), controllers, microprocessors, microcontrollers, processing cores and/or other hardware computing resources configured to support the operation of the processing system  216  described herein. The processing system  216  may include or otherwise access a data storage element  218  (or memory) capable of storing programming instructions for execution by the processing system  216 , that, when read and executed, cause processing system  216  to perform or otherwise support the processes, tasks, operations, and/or functions described herein. For example, in one embodiment, the instructions cause the processing system  216  to create, generate, or otherwise facilitate an application platform that generates or otherwise provides instances of a virtual application at run-time (or “on-demand”) based at least in part upon data that is stored or otherwise maintained by the database  208 . Depending on the embodiment, the memory  218  may be realized as a random access memory (RAM), read only memory (ROM), flash memory, magnetic or optical mass storage, or any other suitable non-transitory short or long term data storage or other computer-readable media, and/or any suitable combination thereof. 
     The client device  210  generally represents an electronic device coupled to the network  214  that may be utilized by a user to access and view data stored in the database  208  via the server  206 . In practice, the client device  210  can be realized as any sort of personal computer, mobile telephone, tablet or other network-enabled electronic device that includes a display device, such as a monitor, screen, or another conventional electronic display, capable of graphically presenting data and/or information provided by the server  206  along with a user input device, such as a keyboard, a mouse, a touchscreen, or the like, capable of receiving input data and/or other information from the user of the client device  210 . A user, such as the patient&#39;s doctor or another healthcare provider, manipulates the client device  210  to execute a client application  212 , such as a web browser application, that contacts the server  206  via the network  214  using a networking protocol, such as the hypertext transport protocol (HTTP) or the like. 
     In exemplary embodiments described herein, a user of the client device  210  manipulates a user input device associated with the client device  210  to input or otherwise provide indication of the patient associated with the infusion device  202  along with a period of time for which the user would like to review, analyze, or otherwise assess measurement data associated with the patient. In response, the server  206  accesses the database  208  to retrieve or otherwise obtain historical measurement data associated with the identified patient for the identified time period and generates a snapshot GUI display (e.g., snapshot GUI display  100 ) that is presented on the display device associated with the client device  210  via the client application  212  executing thereon. 
     It should be appreciated that  FIG. 2  depicts a simplified representation of a patient management system  200  for purposes of explanation and is not intended to limit the subject matter described herein in any way. For example, in various embodiments, a snapshot GUI display may be presented on any device within the patient management system  200  (e.g., the server  206 , the infusion device  202 , the sensing arrangement  204 , or the like) and not necessarily on the client device  210 . Moreover, in some embodiments, the infusion device  202  may be configured to store or otherwise maintain historical measurement and delivery data onboard the infusion device  202  and generate snapshot GUI displays on a display device associated with the infusion device  202 , in which case the server  206 , the database  208 , and the client device  210  may not be present. 
       FIG. 3  depicts an exemplary snapshot presentation process  300  suitable for implementation by a patient management system to provide a snapshot GUI display including information pertaining to preceding operation of an infusion device, such as snapshot GUI display  100  of  FIG. 1 . The various tasks performed in connection with the snapshot presentation process  300  may be performed by hardware, firmware, software executed by processing circuitry, or any combination thereof. For illustrative purposes, the following description refers to elements mentioned above in connection with  FIG. 2 . In practice, portions of the snapshot presentation process  300  may be performed by different elements of the patient management system  200 , such as, for example, the infusion device  202 , the sensing arrangement  204 , the server  206 , the database  208 , the client device  210 , the client application  212 , and/or the processing system  216 . It should be appreciated that the snapshot presentation process  300  may include any number of additional or alternative tasks, the tasks need not be performed in the illustrated order and/or the tasks may be performed concurrently, and/or the snapshot presentation process  300  may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein. Moreover, one or more of the tasks shown and described in the context of  FIG. 3  could be omitted from a practical embodiment of the snapshot presentation process  300  as long as the intended overall functionality remains intact. 
     The illustrated snapshot presentation process  300  begins by receiving or otherwise obtaining measurement data for the evaluation period being analyzed (task  302 ). In this regard, in response to receiving indication of a desired time period for the snapshot GUI display  100 , the server  206  accesses the database  208  to obtain the patient&#39;s sensor measurement values having associated timestamps that are within the time period for the snapshot GUI display  100 . For example, for the embodiment of  FIG. 1  where the snapshot time period corresponds to Nov. 3, 2014 to Nov. 6, 2014, the server  206  obtains, from the database  208 , the stored sensor measurement values previously obtained by the sensing arrangement  204  having timestamp indicating an associated date from Nov. 3, 2014 to Nov. 6, 2014. 
     After obtaining the measurement data for the evaluation period, the snapshot presentation process  300  continues by identifying a plurality of different monitoring periods within the evaluation period, identifying event detection thresholds or other parameters or criteria used for detecting event patterns based on the measurement data, and then analyzing the measurement data associated with each of the different monitoring periods with respect to the event detection thresholds to identify event patterns occurring within the respective monitoring periods (tasks  304 ,  306 ,  308 ). In this regard, sensor measurement values are classified into one or more monitoring periods based on the timestamps associated with those values falling within the time period associated with the respective monitoring period(s), and then the sensor measurement values within each monitoring period are analyzed with respect to the various event detection criteria to identify event patterns associated with the respective monitoring period. The sensor measurement values within a monitoring period may be compared to a glucose threshold value to identify a number of times that the sensor measurement values violated the glucose threshold value within the monitoring period, and an event pattern detected when the number is greater than one. For example, a hypoglycemic (or low glucose) event pattern may be identified when sensor measurement values within a monitoring period are below a lower glucose threshold value (e.g., 70 mg/dL) on two or more days within the evaluation period. Similarly, a hyperglycemic (or high glucose) event pattern may be identified when sensor measurement values within a monitoring period are above an upper glucose threshold value (e.g., 150 mg/dL) on two or more days within the evaluation period. 
     In exemplary embodiments, the different monitoring periods within the evaluation period include an overnight time period, a fasting time period, a breakfast time period, a lunch time period, and a dinner time period. Additionally, in some embodiments, additional monitoring periods may be identified relative to other events, such as, for example, meal indications corresponding to a meal bolus. In such embodiments, measurement values within a fixed period of time (e.g., three hours) preceding a meal indication may be associated with a pre-meal monitoring period, while measurement values within another fixed period time after the meal indication may be associated with a post-meal monitoring period. Depending on the embodiment, the monitoring periods may overlap (e.g., some sensor measurement values fall within multiple different monitoring periods), or the monitoring periods may be mutually exclusive so that each sensor measurement value falls within only one of the monitoring periods. Additionally, in some embodiments, the monitoring periods may be customizable on a patient-specific (or per-patient) basis, with the corresponding end points (e.g., starting and stopping times) or other reference values defining the end points (e.g., the amount of time before/after a meal indication for a pre- or post-meal monitoring period) for the different monitoring time periods being stored or otherwise maintained in the database  208  in association with the patient. The monitoring periods may be customizable on a per-user basis (e.g., doctor to doctor) in a similar manner, with the corresponding timing criteria for the different monitoring time periods being stored or otherwise maintained in the database  208  in association with the user of the client device  210 . 
     Once the monitoring time periods to be analyzed are identified, the server  206  classifies or otherwise categorizes the patient&#39;s sensor glucose measurement values into the appropriate monitoring time periods, resulting in a subset of the patient&#39;s sensor glucose measurement values associated with each respective monitoring time period. Thereafter, for each monitoring period, the server  206  analyzes that subset of the patient&#39;s sensor glucose measurement values to identify any hypoglycemic or hyperglycemic event patterns associated with that respective monitoring period. As described above, the server  206  identifies a hypoglycemic event when one or more of the patient&#39;s sensor glucose measurement values within that subset are less than a lower glucose threshold value on at least two different days within the snapshot time period. Similarly, the server  206  identifies a hyperglycemic event when one or more of the patient&#39;s sensor glucose measurement values within the subset are greater than an upper glucose threshold value on at least two different days within the snapshot time period. 
     Additionally, in exemplary embodiments, the server  206  analyzes the subset of the patient&#39;s sensor glucose measurement values for the respective monitoring period to detect or otherwise identify a variability event pattern across multiple days within the snapshot time period. For example, in one embodiment, the server  206  identifies a variability event pattern when one or more the patient&#39;s sensor glucose measurement values for the monitoring period are less than the lower glucose threshold value on at least two different days within the snapshot time period and one or more of the patient&#39;s sensor glucose measurement values within the subset are greater than an upper glucose threshold value on at least two different days within the snapshot time period. In exemplary embodiments, the server  206  also calculates an interquartile range of the daily median sensor glucose measurement values within the monitoring period and detects a variability event pattern when the interquartile range is greater than a variability detection threshold (e.g., 80 mg/dL). It should be noted that the interquartile range is merely one exemplary way in which a variability event pattern may be detected, and in other embodiments, a variability event pattern may be detected based on other statistics calculated based on measurement values for a given monitoring period (e.g., standard deviation values, variance values, or the like). 
     In a similar manner as described above in the context of the monitoring periods, the detection threshold values or other detection criteria for event patterns may be customizable on a patient-specific (or per-patient) basis, with the corresponding detection threshold values (e.g., the lower glucose threshold value, the upper glucose threshold value, the variability detection threshold value, and the lie) being stored or otherwise maintained in the database  208  in association with the patient. Additionally or alternatively, in some embodiments, the detection threshold values or other detection criteria may be customizable on a per-user basis (e.g., doctor to doctor) in a similar manner, with the corresponding detection criteria being stored or otherwise maintained in the database  208  in association with the user of the client device  210 . Thus, the various criteria used for generating the event detection region  106  on the snapshot GUI display  100  may vary depending on either the patient being analyzed or the user of the client device  210 . 
     Still referring to  FIG. 3 , after identifying event patterns associated with the different time periods, the snapshot presentation process  300  continues by prioritizing the event patterns according to one or more prioritization criteria to obtain a prioritized list of detected event patterns. In exemplary embodiments, the snapshot presentation process  300  prioritizes the event patterns primarily based on event type, and secondarily based on the monitoring period associated with the respective event patterns (tasks  310 ,  312 ). For example, in one embodiment, the server  206  prioritizes, sorts, or otherwise orders variability event patterns ahead of both hypoglycemic and hyperglycemic event patterns, with hypoglycemic event patterns being prioritized or ordered ahead of hyperglycemic event patterns. Thus, prioritization by event type results in variability event patterns being ordered first in a list or other data structure containing the detected event patterns, followed by hypoglycemic event patterns, followed by the hyperglycemic event patterns. 
     Thereafter, the server  206  prioritizes, sorts, or otherwise orders event patterns for each event type by their associated monitoring period. For example, the server  206  prioritizes, sorts, or otherwise orders the variability event patterns by monitoring period and orders the prioritized variability event patterns ahead of the hypoglycemic event patterns, which are also prioritized or otherwise ordered by monitoring period. In one embodiment, the server  206  prioritizes event patterns by monitoring period in the following order: the fasting time period or pre-breakfast time period, the overnight time period, the breakfast or post-breakfast time period, the dinner or post-dinner time period, the lunch or post-lunch time period, the pre-dinner time period, and the pre-lunch time period. Thus, in such an embodiment, the event patterns may be prioritized as follows: a variability event associated with the fasting time period or pre-breakfast time period, a variability event associated with the overnight time period, a variability event associated with the breakfast or post-breakfast time period, a variability event associated with the dinner or post-dinner time period, a variability event associated with the lunch or post-lunch time period, a variability event associated with the pre-dinner time period, and a variability event associated with the pre-lunch time period, followed by a hypoglycemic event associated with the fasting time period or pre-breakfast time period, a hypoglycemic event associated with the overnight time period, a hypoglycemic event associated with the breakfast or post-breakfast time period, a hypoglycemic event associated with the dinner or post-dinner time period, a hypoglycemic event associated with the lunch or post-lunch time period, a hypoglycemic event associated with the pre-dinner time period, and a hypoglycemic event associated with the pre-lunch time period, followed by a hyperglycemic event associated with the fasting time period or pre-breakfast time period, a hyperglycemic event associated with the overnight time period, a hyperglycemic event associated with the breakfast or post-breakfast time period, a hyperglycemic event associated with the dinner or post-dinner time period, a hyperglycemic event associated with the lunch or post-lunch time period, a hyperglycemic event associated with the pre-dinner time period, and a hyperglycemic event associated with the pre-lunch time period. 
     For example, referring to  FIG. 1 , prioritization by monitoring period results in a hyperglycemic event pattern detected within a fasting time period being ordered ahead of a hyperglycemic event pattern detected within an overnight time period (e.g., the period of time preceding 5:00 AM) in the prioritized list. In this regard, more significant time periods for purposes of glycemic control may be preferentially displayed over less significant time periods. For example, since the patient may be sleeping or waking up and less likely or less capable of responding to alerts or notifications generated by the infusion device  202 , events occurring overnight or early in the morning prior to eating may require more attention or remedial action than events occurring during the day when the patient is awake and alert and capable of responding to alerts or notifications generated by the infusion device  202 . 
     In a similar manner as described above, the prioritization criteria may be customizable or otherwise configurable on a per-patient or per-user basis and such particular prioritization criteria may be stored or otherwise maintained in the database  208  in association with that patient or user. Additionally, the ordering of the application of the prioritization criteria may be customizable or configurable. For example, in one alternative embodiment, the event patterns are prioritized primarily based on monitoring period and secondarily based on the event type associated with the respective event patterns. 
     In exemplary embodiments, after prioritizing the detected event patterns, the snapshot presentation process  300  continues by filtering the event patterns according to one or more filtering criteria to obtain a reduced prioritized list of detected event patterns for presentation on the snapshot GUI display. In exemplary embodiments, the snapshot presentation process  300  filters the prioritized list of detected event patterns first by event type priority within the respective monitoring periods to remove or exclude lower priority event patterns and thereby select or retain only the highest priority event pattern detected for each respective monitoring period (task  314 ). For example, if a hypoglycemic event pattern (e.g., sensor measurement values below a lower threshold value on at least two days), a hyperglycemic event pattern (e.g., sensor measurement values above an upper threshold value on at least two days), and a variability event pattern (e.g., sensor measurement values above an upper threshold value on at least two days and below a lower threshold value on at least two days) are all detected within a particular monitoring period, the server  206  may remove the hypoglycemic event pattern and the hyperglycemic event pattern associated with that monitoring period from the prioritized list of detected event patterns when the variability event type has the highest priority, so that the list retains only the variability event pattern associated with the monitoring period. In this regard, since remedial actions that may be taken by the patient or user to mitigate or otherwise address the highest priority event pattern may also influence the lower priority event patterns, removing lower priority event patterns allows the patient or user to focus on addressing more significant event patterns, which, in turn, could also result in other event patterns detected within that monitoring period being resolved. As noted above, the event type priorities may be customizable or otherwise configurable on a per-patient or per-user basis, such that particular prioritization criteria may be stored or otherwise maintained in the database  208  in association with that patient or user and the resulting types of events preferentially presented within the pattern detection region of the snapshot GUI display may vary depending on the user or patient. 
     After the filtering the prioritized list of detected event patterns by event type priority within the respective monitoring periods, the resulting list includes only one event pattern for each monitoring period during which an event pattern was detected, with the retained event pattern for a respective monitoring period being the highest priority event pattern within that monitoring period. For example, referring to the embodiment of  FIG. 1 , when the server  206  identifies a variability event pattern and a hypoglycemic and/or hyperglycemic event pattern within the lunch time monitoring period, only the variability event pattern associated with the lunch time period may remain in the prioritized list after filtering the lower priority event patterns detected within the lunch time period. Similarly, if the server  206  identified both a hypoglycemic event pattern and a hyperglycemic event pattern within the pre-dinner time period, only the hypoglycemic event pattern associated with the pre-dinner time period may remain in the prioritized list. 
     Still referring to  FIG. 3 , in exemplary embodiments, after filtering by event type priority within the respective monitoring periods, the snapshot presentation process  300  continues by filtering the list of event patterns based on a display threshold number of event patterns to remove or exclude lower priority event patterns and thereby select or retain only a limited number of the highest priority event patterns for presentation on the snapshot GUI display (task  316 ). For example, in the embodiment of  FIG. 1 , the display threshold number is equal to three, so that all event patterns after the first three event patterns in the prioritized list are removed or otherwise excluded, resulting in a filtered prioritized list that includes only the three highest priority event patterns remaining after filtering by event type priority within the respective monitoring periods. Thus, the hyperglycemic event pattern detected for an overnight monitoring period (e.g., the time period preceding the fasting monitoring period) may be filtered or otherwise removed from the list based on the fasting monitoring period being prioritized over the overnight monitoring period (e.g., task  312 ). Again, it should be noted that the display threshold number may be customizable or otherwise configurable on a per-patient or per-user basis, so that the number of pattern guidance displays presented within the pattern detection region of the snapshot GUI display may vary depending on the user or patient. 
     The snapshot presentation process  300  continues by generating or otherwise providing pattern guidance displays for the remaining event patterns in the filtered prioritized list within the snapshot GUI display along with corresponding indicia for the event patterns on the graph overlay region of the snapshot GUI display (tasks  318 ,  320 ). In exemplary embodiments, the pattern guidance displays are presented in a manner such that higher priority event patterns are preferentially displayed relative to lower priority event patterns, for example, by presenting the highest priority remaining event pattern above and/or to the left of the other remaining event patterns and presenting the lowest priority remaining event pattern below and/or to the right of the other remaining event patterns. The indicia for the remaining event patterns presented on the graph overlay region identify or otherwise indicate the relative priority of the detected event pattern along with the corresponding monitoring period relative to the time period depicted on the graph. 
     Referring to  FIG. 1 , prioritization by event type (e.g., task  310 ) and then by monitoring period (e.g., task  312 ) results in the variability event pattern detected within the lunch time period being ordered first in the prioritized list, followed by a hypoglycemic event pattern detected within the lunch time period, followed by a hypoglycemic event pattern detected within a pre-dinner time period, followed by a hyperglycemic event pattern detected within a fasting time period, followed by a hyperglycemic event pattern detected within an overnight time period, followed by a hyperglycemic event pattern detected within a dinner or post-dinner time period. Thereafter, filtering by event type priority within monitoring period (e.g., task  314 ) removes the lunch time hypoglycemic event pattern from the prioritized list, and filtering based on the display threshold (e.g., task  316 ) removes the overnight hyperglycemic event pattern and the dinner or post-dinner hyperglycemic event pattern, resulting in a filtered prioritized list of three event patterns that includes the lunch time variability event pattern, the pre-dinner hypoglycemic event pattern, and the fasting hyperglycemic event pattern. 
     The server  206  generates or otherwise provides (e.g., on or to the client application  212  on the client device  210 ) a pattern guidance display  120  associated with the lunch time variability event pattern that is preferentially displayed relative to (e.g., to the left of) the pattern guidance displays  130 ,  140  associated with the pre-dinner hypoglycemic event pattern and the fasting hyperglycemic event pattern, with the pre-dinner hypoglycemic guidance display  130  being preferentially displayed relative to the fasting hyperglycemic guidance display  140 . As described above, the server  206  generates a marker  128  associated with the lunch time variability guidance display  120  having a position and dimension that encompasses, overlaps, or otherwise indicates the lunch time monitoring period that also includes an indication (e.g., the number  1 ) that the event pattern associated with the lunch time monitoring period is the highest priority event pattern detected. Similarly, the server  206  generates a second marker  138  having a position and dimension that encompasses, overlaps, or otherwise indicates the pre-dinner monitoring period and includes an indication (e.g., the number  2 ) that the event pattern associated with the pre-dinner monitoring period is the second highest priority event pattern detected, and the server  206  generates a third marker  148  having a position and dimension that encompasses, overlaps, or otherwise indicates the fasting monitoring period and includes an indication (e.g., the number  3 ) that the event pattern associated with the fasting monitoring period is the third highest priority event pattern detected. 
       FIG. 4  depicts an exemplary pattern guidance presentation process  400  suitable for implementation in conjunction with the snapshot presentation process  300  of  FIG. 3  to generate pattern guidance displays within a pattern detection region of a snapshot GUI display, such as pattern guidance displays  120 ,  130 ,  140  within pattern detection region  106  of the snapshot GUI display  100  of  FIG. 1 . The various tasks performed in connection with the pattern guidance presentation process  400  may be performed by hardware, firmware, software executed by processing circuitry, or any combination thereof. For illustrative purposes, the following description refers to elements mentioned above in connection with  FIG. 2 . In practice, portions of the pattern guidance presentation process  400  may be performed by different elements of the patient management system  200 ; however, for purposes of explanation, the subject matter may be described in the context of the guidance presentation process  400  being performed by the server  206 . It should be appreciated that the pattern guidance presentation process  400  may include any number of additional or alternative tasks, the tasks need not be performed in the illustrated order and/or the tasks may be performed concurrently, and/or the pattern guidance presentation process  400  may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein. Moreover, one or more of the tasks shown and described in the context of  FIG. 4  could be omitted from a practical embodiment of the pattern guidance presentation process  400  as long as the intended overall functionality remains intact. 
     In exemplary embodiments, the pattern guidance presentation process  400  is performed for each detected event pattern that remains in the filtered prioritized list (e.g., task  318 ) to populate the pattern detection region on a snapshot GUI display. The illustrated process  400  generates a header for the pattern guidance display based on the event type and monitoring period associated with the detected event pattern along with the priority of the detected event pattern in the filtered prioritized list (task  402 ). In this regard, the pattern guidance header identifies the type of event pattern that was detected, the monitoring period that event pattern was detected within, and the priority level associated with that event pattern based on the prioritization criteria. For example, referring to  FIG. 1 , the server  206  generates a header region  122  for the first guidance display  120  within the event pattern region  106  that identifies the first event pattern is a variability event with respect to the patient&#39;s sensor glucose values (e.g., “Variable SG”) and that the event pattern was detected within a lunch time monitoring period, with the number one indicating the lunch time variability event is the highest priority event pattern detected. Similarly, the server  206  generates a header region  132  for the second guidance display  130  that identifies the second event pattern is a hypoglycemic event with respect to the patient&#39;s sensor glucose values (e.g., “Low SG”) and that the event pattern was detected within a pre-dinner monitoring period, with the number two indicating the pre-dinner hypoglycemic event is the second highest priority event pattern detected. The server  206  also generates a header region  142  for the third guidance display  140  that identifies the third event pattern is a hyperglycemic event with respect to the patient&#39;s sensor glucose values (e.g., “High SG”) and that the event pattern was detected within a fasting monitoring period, with the number three indicating the fasting hyperglycemic event is the third highest priority event pattern detected. 
     In exemplary embodiments, the guidance presentation process  400  also generates a graphical representation of the time of day corresponding to the respective monitoring periods associated with the displayed event patterns (task  404 ). In this manner, the time of day corresponding to a particular named monitoring period and the relationship between sensor glucose measurement values and that monitoring period may be made apparent to the user in conjunction with the markers  128 ,  138 ,  148  presented on the graph overlay region  108 . For a monitoring period defined or otherwise referenced from another event or time (e.g., a meal announcement or maker), the server  206  may calculate or otherwise determine the end points for the current instance of that monitoring period within the current snapshot time period and provide graphical representation of that time period encompassing the period between those end points within the respective header region. For example, in  FIG. 1 , the time of day associated with the current instance of the pre-dinner monitoring period associated with pattern guidance display  130  could be calculated or otherwise determined based on respective timings of meal announcements or markers during the current snapshot time period depicted in the graph overlay region  108  that occur in the evening, while accounting for any offset values that are stored in the database  208  in association with the current patient or user and define the boundaries of the pre-dinner monitoring period relative to those meal announcements. That said, default time period end points may also be used in the absence of sufficient meal announcements within a designated dinner time period (e.g., which could also be defined by default end point values or be customizable). For other monitoring periods, the server  206  may obtain the stored end points associated with that monitoring period in the database  208  for the current patient or user, and provide a graphical representation of the monitoring period time of day. 
     In the illustrated embodiment, the server  206  generates a graphical representation of the time of day associated with the lunch monitoring period (e.g., 11:00 AM-3:00 PM predefined lunch time period since insufficient evening meal announcements exist within that timeframe for calculating based on meal announcement timings) in the first header region  122 , a graphical representation of the time of day associated with the pre-dinner monitoring period (e.g., the 5:00 PM-8:00 PM predefined time period since insufficient evening meal announcements exist within that timeframe for calculating based on meal announcement timings) in the second header region  132 , and a graphical representation of the time of day associated with the fasting monitoring period (e.g., 5:00 AM-7:00 AM) in the third header region  142 . As illustrated, the header may include a footnote symbol or other indicia that indicates whether a monitoring period capable of being adaptively and dynamically calculated based on meal announcements was able to be determined, and if not, provide indication that a fixed time of day is utilized due to insufficient meal announcements within a default timeframe (or predefined range of time) associated with that respective monitoring period. 
     Still referring to  FIG. 4 , the guidance presentation process  400  also generates a graphical representation one or more characteristics summarizing, quantifying or otherwise describing the nature of the displayed event patterns, such as, for example, the severity, frequency, intensity, or the like (task  406 ). Thus, a user may quickly ascertain the relative significance or impact of the individual events that resulted in the detected event pattern with respect to the patient&#39;s physiological condition during the snapshot time period in conjunction with the relative priority of that event pattern. It should be noted that any number of different characteristics or metrics that summarize, quantify or otherwise describe the nature of a detected event pattern or the individual component events of the event pattern may be determined and presented, and the subject matter is not intended to be limited to any particular characteristics or metric presented in a pattern guidance display. 
     For example, for a variability event pattern associated with a given monitoring period, the number of days that a variability event was detected within that monitoring period may be determined and presented, thereby providing indication of the frequency or regularity of the variability event. For example, in the embodiment of  FIG. 1 , based on the sensor glucose measurement values corresponding to the lunch time monitoring period, the server  206  may calculate or otherwise determine that a variability event occurred on four different days within the snapshot time period and provide a graphical representation of the variability event frequency within an event pattern summary region  124  of the pattern guidance display  120  beneath the header region  122 . In this example, a user may readily identify that the variability event is the highest priority event pattern detected within the snapshot time period while also identifying the occurrence of a variability event during the lunch time period on every day of the snapshot time period, and thereby be apprised of the relative importance of addressing the lunch time variability event. 
     For low or high glucose event patterns, the number of days the sensor glucose measurement values violated one or more thresholds within that monitoring period or otherwise fell within distinct ranges of measurement values may also be determined and presented. For example, in the embodiment of  FIG. 1 , based on the sensor glucose measurement values corresponding to the pre-dinner monitoring period, the server  206  may calculate or otherwise determine the number of days within the snapshot time period that the sensor glucose measurement values were within the range between a hypoglycemic glucose threshold (e.g., 50 mg/dL) and a lower glucose target range threshold (e.g., 70 mg/dL) and provide a corresponding graphical representation of the lower severity hypoglycemic event frequency within an event pattern summary region  134  of the pattern guidance display  130 , while also determining the number of days within the snapshot time period that those sensor glucose measurement values were below the hypoglycemic glucose threshold and provide a corresponding graphical representation of the higher severity hypoglycemic event frequency within the event pattern summary region  134 . Similarly, the server  206  may calculate or otherwise determine, based on the sensor glucose measurement values corresponding to the fasting monitoring period, the number of days within the snapshot time period that the sensor glucose measurement values were within the range between an upper target range threshold (e.g., 150 mg/dL) and a hyperglycemic glucose threshold (e.g., 250 mg/dL) and provide a corresponding graphical representation of the lower severity hyperglycemic event frequency within event pattern summary region  144 , while also determining the number of days within the snapshot time period that those sensor glucose measurement values were above the hyperglycemic glucose threshold and provide a corresponding graphical representation of the higher severity hyperglycemic event frequency within the event pattern summary region  144 . 
     Referring again to  FIG. 4 , the guidance presentation process  400  also generates a graphical representation of one or more potential causes for the detected event pattern within the pattern guidance display (task  408 ). In this regard, the potential causes may be stored or otherwise maintained in the database  208  in association with the particular combination of event type and monitoring period (or time of day), with the server  206  retrieving or otherwise obtaining the appropriate potential causes that correspond to the current combination of event type and monitoring period presented on the snapshot display. For example, to populate the event pattern analysis region  126  of the pattern guidance display  120 , the server  206  accesses the database  208  to identify the list of potential causes associated with the variability event type that are also associated with the lunch time monitoring period (or a time of day between 11:00 AM and 3:00 PM) and then generates or otherwise provides a graphical representation of that list of causes in the analysis region  126 . In some embodiments, the potential causes may be phrased in a manner that suggests remedial actions that can be taken to resolve or correct the event pattern. In other embodiments described in greater detail below in the context of  FIGS. 13-16 , potential remedial actions (or corresponding logic rules for determining such remedial actions) may also be stored or otherwise maintained in the database  208  in association with the particular combination of event type and monitoring period (or time of day). In such embodiments, the server  206  may identify or otherwise determine the appropriate potential remedial actions (or logical rules therefor) that correspond to the current combination of event type and monitoring period presented on the snapshot display and then generate graphical representations of those remedial actions within the event pattern analysis region  126 ,  136 ,  146 . 
     Referring to  FIGS. 1-4 , by virtue of the subject matter described above, a user may quickly ascertain or otherwise identify the most significant event patterns detected within a particular time period being evaluated on the snapshot GUI display  100 , while also being able to quickly ascertain the relative impact or significance of the constituent events with respect to the patient&#39;s glycemic control, the temporal characteristics or significance of those events, and the potential causes or remedial actions for those events at the times of day during which they were detected. This is particularly useful in the context of a patient management, such as patient management system  200  of  FIG. 2 , where the doctor or other medical professional or healthcare provider monitoring the glycemic control of the patient associated with the infusion device  202  utilizes a client device  210  to access and review historical data associated with the patient over a select period of time from the database  208  via the server  206 . In exemplary embodiments, the server  206  generates or otherwise provides a snapshot GUI display  100  within a client application  212  on the client device  210  that includes pattern guidance displays  120 ,  130 ,  140  associated with the highest priority event patterns detected based on the patient&#39;s historical measurement data within the desired evaluation period in conjunction with a performance metric region  104  and graph overlay region  108  that also reflect the patient&#39;s historical measurement data within the desired evaluation period. As a result, the snapshot GUI display  100  allows the user of the client device  210  to quickly assess the general characteristics or nature of the glycemic control for the patient achieved by the infusion device  202 , while also apprising the user of the most notable event patterns detected within the desired evaluation period, their relative significance or impact, and their potential causes or remedies. Thus, the snapshot GUI display  100  can aid a doctor or other care provider seeking to integrate continuous glucose monitoring and/or other autonomous glucose regulation by the infusion device  202  into his or her practice in an efficient manner by detecting, prioritizing, filtering, and characterizing event patterns automatically (e.g., without requiring manual input or analysis). This, in turn, facilitates improved patient outcomes. 
     Diabetes Data Management System Overview 
       FIG. 5  illustrates a computing device  500  including a display  533  suitable for presenting a snapshot GUI display  100  as part of a diabetes data management system in conjunction with the processes  300 ,  400  of  FIGS. 3-4  described above. The diabetes data management system (DDMS) may be referred to as the Medtronic MiniMed CARELINK™ system or as a medical data management system (MDMS) in some embodiments. The DDMS may be housed on a server or a plurality of servers which a user or a health care professional may access via a communications network via the Internet or the World Wide Web. Some models of the DDMS, which is described as an MDMS, are described in U.S. Patent Application Publication Nos. 2006/0031094 and 2013/0338630, which is herein incorporated by reference in their entirety. 
     While description of embodiments are made in regard to monitoring medical or biological conditions for subjects having diabetes, the systems and processes herein are applicable to monitoring medical or biological conditions for cardiac subjects, cancer subjects, HIV subjects, subjects with other disease, infection, or controllable conditions, or various combinations thereof. 
     In embodiments of the invention, the DDMS may be installed in a computing device in a health care provider&#39;s office, such as a doctor&#39;s office, a nurse&#39;s office, a clinic, an emergency room, an urgent care office. Health care providers may be reluctant to utilize a system where their confidential patient data is to be stored in a computing device such as a server on the Internet. 
     The DDMS may be installed on a computing device  500 . The computing device  500  may be coupled to a display  533 . In some embodiments, the computing device  500  may be in a physical device separate from the display (such as in a personal computer, a mini-computer, etc.) In some embodiments, the computing device  500  may be in a single physical enclosure or device with the display  533  such as a laptop where the display  533  is integrated into the computing device. In embodiments of the invention, the computing device  500  hosting the DDMS may be, but is not limited to, a desktop computer, a laptop computer, a server, a network computer, a personal digital assistant (PDA), a portable telephone including computer functions, a pager with a large visible display, an insulin pump including a display, a glucose sensor including a display, a glucose meter including a display, and/or a combination insulin pump/glucose sensor having a display. The computing device may also be an insulin pump coupled to a display, a glucose meter coupled to a display, or a glucose sensor coupled to a display. The computing device  500  may also be a server located on the Internet that is accessible via a browser installed on a laptop computer, desktop computer, a network computer, or a PDA. The computing device  500  may also be a server located in a doctor&#39;s office that is accessible via a browser installed on a portable computing device, e.g., laptop, PDA, network computer, portable phone, which has wireless capabilities and can communicate via one of the wireless communication protocols such as Bluetooth and IEEE 802.11 protocols. 
     In the embodiment shown in  FIG. 5 , the data management system  516  comprises a group of interrelated software modules or layers that specialize in different tasks. The system software includes a device communication layer  524 , a data parsing layer  526 , a database layer  528 , database storage devices  529 , a reporting layer  530 , a graph display layer  531 , and a user interface layer  532 . The diabetes data management system may communicate with a plurality of subject support devices  512 , two of which are illustrated in  FIG. 5 . Although the different reference numerals refer to a number of layers, (e.g., a device communication layer, a data parsing layer, a database layer), each layer may include a single software module or a plurality of software modules. For example, the device communications layer  524  may include a number of interacting software modules, libraries, etc. In embodiments of the invention, the data management system  516  may be installed onto a non-volatile storage area (memory such as flash memory, hard disk, removable hard, DVD-RW, CD-RW) of the computing device  500 . If the data management system  516  is selected or initiated, the system  516  may be loaded into a volatile storage (memory such as DRAM, SRAM, RAM, DDRAM) for execution. 
     The device communication layer  524  is responsible for interfacing with at least one, and, in further embodiments, to a plurality of different types of subject support devices  512 , such as, for example, blood glucose meters, glucose sensors/monitors, or an infusion pump. In one embodiment, the device communication layer  524  may be configured to communicate with a single type of subject support device  512 . However, in more comprehensive embodiments, the device communication layer  524  is configured to communicate with multiple different types of subject support devices  512 , such as devices made from multiple different manufacturers, multiple different models from a particular manufacturer and/or multiple different devices that provide different functions (such as infusion functions, sensing functions, metering functions, communication functions, user interface functions, or combinations thereof). By providing an ability to interface with multiple different types of subject support devices  512 , the diabetes data management system  516  may collect data from a significantly greater number of discrete sources. Such embodiments may provide expanded and improved data analysis capabilities by including a greater number of subjects and groups of subjects in statistical or other forms of analysis that can benefit from larger amounts of sample data and/or greater diversity in sample data, and, thereby, improve capabilities of determining appropriate treatment parameters, diagnostics, or the like. 
     The device communication layer  524  allows the DDMS  516  to receive information from and transmit information to or from each subject support device  512  in the system  516 . Depending upon the embodiment and context of use, the type of information that may be communicated between the system  516  and device  512  may include, but is not limited to, data, programs, updated software, education materials, warning messages, notifications, device settings, therapy parameters, or the like. The device communication layer  524  may include suitable routines for detecting the type of subject support device  512  in communication with the system  516  and implementing appropriate communication protocols for that type of device  512 . Alternatively or in addition, the subject support device  512  may communicate information in packets or other data arrangements, where the communication includes a preamble or other portion that includes device identification information for identifying the type of the subject support device. Alternatively, or in addition, the subject support device  512  may include suitable user-operable interfaces for allowing a user to enter information, such as by selecting an optional icon or text or other device identifier that corresponds to the type of subject support device used by that user. Such information may be communicated to the system  516 , through a network connection. In yet further embodiments, the system  516  may detect the type of subject support device  512  it is communicating with in the manner described above and then may send a message requiring the user to verify that the system  516  properly detected the type of subject support device being used by the user. For systems  516  that are capable of communicating with multiple different types of subject support devices  512 , the device communication layer  524  may be capable of implementing multiple different communication protocols and selects a protocol that is appropriate for the detected type of subject support device. 
     The data-parsing layer  526  is responsible for validating the integrity of device data received and for inputting it correctly into a database  529 . A cyclic redundancy check CRC process for checking the integrity of the received data may be employed. Alternatively, or in addition, data may be received in packets or other data arrangements, where preambles or other portions of the data include device type identification information. Such preambles or other portions of the received data may further include device serial numbers or other identification information that may be used for validating the authenticity of the received information. In such embodiments, the system  516  may compare received identification information with pre-stored information to evaluate whether the received information is from a valid source. 
     The database layer  528  may include a centralized database repository that is responsible for warehousing and archiving stored data in an organized format for later access, and retrieval. The database layer  528  operates with one or more data storage device(s)  529  suitable for storing and providing access to data in the manner described herein. Such data storage device(s)  529  may comprise, for example, one or more hard discs, optical discs, tapes, digital libraries or other suitable digital or analog storage media and associated drive devices, drive arrays or the like. 
     Data may be stored and archived for various purposes, depending upon the embodiment and environment of use. Information regarding specific subjects and patient support devices may be stored and archived and made available to those specific subjects, their authorized healthcare providers and/or authorized healthcare payor entities for analyzing the subject&#39;s condition. Also, certain information regarding groups of subjects or groups of subject support devices may be made available more generally for healthcare providers, subjects, personnel of the entity administering the system  516  or other entities, for analyzing group data or other forms of conglomerate data. 
     Embodiments of the database layer  528  and other components of the system  516  may employ suitable data security measures for securing personal medical information of subjects, while also allowing non-personal medical information to be more generally available for analysis. Embodiments may be configured for compliance with suitable government regulations, industry standards, policies or the like, including, but not limited to the Health Insurance Portability and Accountability Act of 1996 (HIPAA). 
     The database layer  528  may be configured to limit access of each user to types of information pre-authorized for that user. For example, a subject may be allowed access to his or her individual medical information (with individual identifiers) stored by the database layer  528 , but not allowed access to other subject&#39;s individual medical information (with individual identifiers). Similarly, a subject&#39;s authorized healthcare provider or payor entity may be provided access to some or all of the subject&#39;s individual medical information (with individual identifiers) stored by the database layer  528 , but not allowed access to another individual&#39;s personal information. Also, an operator or administrator-user (on a separate computer communicating with the computing device  500 ) may be provided access to some or all subject information, depending upon the role of the operator or administrator. On the other hand, a subject, healthcare provider, operator, administrator or other entity, may be authorized to access general information of unidentified individuals, groups or conglomerates (without individual identifiers) stored by the database layer  528  in the data storage devices  529 . 
     In embodiments of the invention, the database layer  528  may store preference profiles. In the database layer  528 , for example, each user may store information regarding specific parameters that correspond to the user. Illustratively, these parameters could include target blood glucose or sensor glucose levels, what type of equipment the users utilize (insulin pump, glucose sensor, blood glucose meter, etc.) and could be stored in a record, a file, or a memory location in the data storage device(s)  529  in the database layer. As described above, preference profiles may include various threshold values, monitoring period values, prioritization criteria, filtering criteria, and/or other user-specific values for parameters utilized by the processes  300 ,  400  described above to generate a snapshot GUI display, such as snapshot GUI display  100 , on the display  533  or a support device  512  in a personalized or patient-specific manner. 
     The DDMS  516  may measure, analyze, and track either blood glucose (BG) or sensor glucose (SG) readings for a user. In embodiments of the invention, the medical data management system may measure, track, or analyze both BG and SG readings for the user. Accordingly, although certain reports may mention or illustrate BG or SG only, the reports may monitor and display results for the other one of the glucose readings or for both of the glucose readings. 
     The reporting layer  530  may include a report wizard program that pulls data from selected locations in the database  529  and generates report information from the desired parameters of interest. The reporting layer  530  may be configured to generate multiple different types of reports, each having different information and/or showing information in different formats (arrangements or styles), where the type of report may be selectable by the user. A plurality of pre-set types of report (with pre-defined types of content and format) may be available and selectable by a user. At least some of the pre-set types of reports may be common, industry standard report types with which many healthcare providers should be familiar. In exemplary embodiments described herein, the reporting layer  530  also facilitates generation of a snapshot report including a snapshot GUI display, such as snapshot GUI display  100  of  FIG. 1 . 
     In embodiments of the invention, the database layer  528  may calculate values for various medical information that is to be displayed on the reports generated by the report or reporting layer  530 . For example, the database layer  528  may calculate average blood glucose or sensor glucose readings for specified timeframes. In embodiments of the invention, the reporting layer  530  may calculate values for medical or physical information that is to be displayed on the reports. For example, a user may select parameters which are then utilized by the reporting layer  530  to generate medical information values corresponding to the selected parameters. In other embodiments of the invention, the user may select a parameter profile that previously existed in the database layer  528 . 
     Alternatively, or in addition, the report wizard may allow a user to design a custom type of report. For example, the report wizard may allow a user to define and input parameters (such as parameters specifying the type of content data, the time period of such data, the format of the report, or the like) and may select data from the database and arrange the data in a printable or displayable arrangement, based on the user-defined parameters. In further embodiments, the report wizard may interface with or provide data for use by other programs that may be available to users, such as common report generating, formatting or statistical analysis programs. In this manner, users may import data from the system  516  into further reporting tools familiar to the user. The reporting layer  530  may generate reports in displayable form to allow a user to view reports on a standard display device, printable form to allow a user to print reports on standard printers, or other suitable forms for access by a user. Embodiments may operate with conventional file format schemes for simplifying storing, printing and transmitting functions, including, but not limited to PDF, JPEG, or the like. Illustratively, a user may select a type of report and parameters for the report and the reporting layer  530  may create the report in a PDF format. A PDF plug-in may be initiated to help create the report and also to allow the user to view the report. Under these operating conditions, the user may print the report utilizing the PDF plug-in. In certain embodiments in which security measures are implemented, for example, to meet government regulations, industry standards or policies that restrict communication of subject&#39;s personal information, some or all reports may be generated in a form (or with suitable software controls) to inhibit printing, or electronic transfer (such as a non-printable and/or non-capable format). In yet further embodiments, the system  516  may allow a user generating a report to designate the report as non-printable and/or non-transferable, whereby the system  516  will provide the report in a form that inhibits printing and/or electronic transfer. 
     The reporting layer  530  may transfer selected reports to the graph display layer  531 . The graph display layer  531  receives information regarding the selected reports and converts the data into a format that can be displayed or shown on a display  533 . 
     In embodiments of the invention, the reporting layer  530  may store a number of the user&#39;s parameters. Illustratively, the reporting layer  530  may store the type of carbohydrate units, a blood glucose movement or sensor glucose reading, a carbohydrate conversion factor, and timeframes for specific types of reports. These examples are meant to be illustrative and not limiting. 
     Data analysis and presentations of the reported information may be employed to develop and support diagnostic and therapeutic parameters. Where information on the report relates to an individual subject, the diagnostic and therapeutic parameters may be used to assess the health status and relative well-being of that subject, assess the subject&#39;s compliance to a therapy, as well as to develop or modify treatment for the subject and assess the subject&#39;s behaviors that affect his/her therapy. Where information on the report relates to groups of subjects or conglomerates of data, the diagnostic and therapeutic parameters may be used to assess the health status and relative well-being of groups of subjects with similar medical conditions, such as, but not limited to, diabetic subjects, cardiac subjects, diabetic subjects having a particular type of diabetes or cardiac condition, subjects of a particular age, sex or other demographic group, subjects with conditions that influence therapeutic decisions such as but not limited to pregnancy, obesity, hypoglycemic unawareness, learning disorders, limited ability to care for self, various levels of insulin resistance, combinations thereof, or the like. 
     The user interface layer  532  supports interactions with the end user, for example, for user login and data access, software navigation, data input, user selection of desired report types and the display of selected information. Users may also input parameters to be utilized in the selected reports via the user interface layer  532 . Examples of users include but are not limited to: healthcare providers, healthcare payer entities, system operators or administrators, researchers, business entities, healthcare institutions and organizations, or the like, depending upon the service being provided by the system and depending upon the invention embodiment. More comprehensive embodiments are capable of interacting with some or all of the above-noted types of users, wherein different types of users have access to different services or data or different levels of services or data. 
     In an example embodiment, the user interface layer  532  provides one or more websites accessible by users on the Internet. The user interface layer may include or operate with at least one (or multiple) suitable network server(s) to provide the website(s) over the Internet and to allow access, world-wide, from Internet-connected computers using standard Internet browser software. The website(s) may be accessed by various types of users, including but not limited to subjects, healthcare providers, researchers, business entities, healthcare institutions and organizations, payor entities, pharmaceutical partners or other sources of pharmaceuticals or medical equipment, and/or support personnel or other personnel running the system  516 , depending upon the embodiment of use. 
     In another example embodiment, where the DDMS  516  is located on one computing device  500 , the user interface layer  532  provides a number of menus to the user to navigate through the DDMS. These menus may be created utilizing any menu format, including but not limited to HTML, XML, or Active Server pages. A user may access the DDMS  516  to perform one or more of a variety of tasks, such as accessing general information made available on a website to all subjects or groups of subjects. The user interface layer  532  of the DDMS  516  may allow a user to access specific information or to generate reports regarding that subject&#39;s medical condition or that subject&#39;s medical device(s)  512 , to transfer data or other information from that subject&#39;s support device(s)  512  to the system  516 , to transfer data, programs, program updates or other information from the system  516  to the subject&#39;s support device(s)  512 , to manually enter information into the system  516 , to engage in a remote consultation exchange with a healthcare provider, or to modify the custom settings in a subject&#39;s supported device and/or in a subject&#39;s DDMS/MDMS data file. 
     The system  516  may provide access to different optional resources or activities (including accessing different information items and services) to different users and to different types or groups of users, such that each user may have a customized experience and/or each type or group of user (e.g., all users, diabetic users, cardio users, healthcare provider-user or payor-user, or the like) may have a different set of information items or services available on the system. The system  516  may include or employ one or more suitable resource provisioning program or system for allocating appropriate resources to each user or type of user, based on a pre-defined authorization plan. Resource provisioning systems are well known in connection with provisioning of electronic office resources (email, software programs under license, sensitive data, etc.) in an office environment, for example, in a local area network LAN for an office, company or firm. In one example embodiment, such resource provisioning systems is adapted to control access to medical information and services on the DDMS  516 , based on the type of user and/or the identity of the user. 
     Upon entering successful verification of the user&#39;s identification information and password, the user may be provided access to secure, personalized information stored on the DDMS  516 . For example, the user may be provided access to a secure, personalized location in the DDMS  516  which has been assigned to the subject. This personalized location may be referred to as a personalized screen, a home screen, a home menu, a personalized page, etc. The personalized location may provide a personalized home screen to the subject, including selectable icons or menu items for selecting optional activities, including, for example, an option to transfer device data from a subject&#39;s supported device  512  to the system  516 , manually enter additional data into the system  516 , modify the subject&#39;s custom settings, and/or view and print reports. Reports may include data specific to the subject&#39;s condition, including but not limited to, data obtained from the subject&#39;s subject support device(s)  512 , data manually entered, data from medical libraries or other networked therapy management systems, data from the subjects or groups of subjects, or the like. Where the reports include subject-specific information and subject identification information, the reports may be generated from some or all subject data stored in a secure storage area (e.g., storage devices  529 ) employed by the database layer  528 . 
     The user may select an option to transfer (send) device data to the medical data management system  516 . If the system  516  receives a user&#39;s request to transfer device data to the system, the system  516  may provide the user with step-by-step instructions on how to transfer data from the subject&#39;s supported device(s)  512 . For example, the DDMS  516  may have a plurality of different stored instruction sets for instructing users how to download data from different types of subject support devices, where each instruction set relates to a particular type of subject supported device (e.g., pump, sensor, meter, or the like), a particular manufacturer&#39;s version of a type of subject support device, or the like. Registration information received from the user during registration may include information regarding the type of subject support device(s)  512  used by the subject. The system  516  employs that information to select the stored instruction set(s) associated with the particular subject&#39;s support device(s)  512  for display to the user. 
     Other activities or resources available to the user on the system  516  may include an option for manually entering information to the DDMS/MDMS  516 . For example, from the user&#39;s personalized menu or location, the user may select an option to manually enter additional information into the system  516 . 
     Further optional activities or resources may be available to the user on the DDMS  516 . For example, from the user&#39;s personalized menu, the user may select an option to receive data, software, software updates, treatment recommendations or other information from the system  516  on the subject&#39;s support device(s)  512 . If the system  516  receives a request from a user to receive data, software, software updates, treatment recommendations or other information, the system  516  may provide the user with a list or other arrangement of multiple selectable icons or other indicia representing available data, software, software updates or other information available to the user. 
     Yet further optional activities or resources may be available to the user on the medical data management system  516  including, for example, an option for the user to customize or otherwise further personalize the user&#39;s personalized location or menu. In particular, from the user&#39;s personalized location, the user may select an option to customize parameters for the user. In addition, the user may create profiles of customizable parameters. When the system  516  receives such a request from a user, the system  516  may provide the user with a list or other arrangement of multiple selectable icons or other indicia representing parameters that may be modified to accommodate the user&#39;s preferences. When a user selects one or more of the icons or other indicia, the system  516  may receive the user&#39;s request and makes the requested modification. 
     Infusion System Overview 
       FIG. 6  depicts one exemplary embodiment of an infusion system  600  that includes, without limitation, a fluid infusion device (or infusion pump)  602 , a sensing arrangement  604 , a command control device (CCD)  606 , and a computer  608 , which could be realized as any one of the computing devices  206 ,  210 ,  500 ,  512  described above. The components of an infusion system  600  may be realized using different platforms, designs, and configurations, and the embodiment shown in  FIG. 6  is not exhaustive or limiting. In practice, the infusion device  602  and the sensing arrangement  604  are secured at desired locations on the body of a user (or patient), as illustrated in  FIG. 6 . In this regard, the locations at which the infusion device  602  and the sensing arrangement  604  are secured to the body of the user in  FIG. 6  are provided only as a representative, non-limiting, example. The elements of the infusion system  600  may be similar to those described in U.S. Pat. No. 8,674,288, the subject matter of which is hereby incorporated by reference in its entirety. 
     In the illustrated embodiment of  FIG. 6 , the infusion device  602  is designed as a portable medical device suitable for infusing a fluid, a liquid, a gel, or other agent into the body of a user. In exemplary embodiments, the infused fluid is insulin, although many other fluids may be administered through infusion such as, but not limited to, HIV drugs, drugs to treat pulmonary hypertension, iron chelation drugs, pain medications, anti-cancer treatments, medications, vitamins, hormones, or the like. In some embodiments, the fluid may include a nutritional supplement, a dye, a tracing medium, a saline medium, a hydration medium, or the like. 
     The sensing arrangement  604  generally represents the components of the infusion system  600  configured to sense, detect, measure or otherwise quantify a condition of the user, and may include a sensor, a monitor, or the like, for providing data indicative of the condition that is sensed, detected, measured or otherwise monitored by the sensing arrangement. In this regard, the sensing arrangement  604  may include electronics and enzymes reactive to a biological or physiological condition of the user, such as a blood glucose level, or the like, and provide data indicative of the blood glucose level to the infusion device  602 , the CCD  606  and/or the computer  608 . For example, the infusion device  602 , the CCD  606  and/or the computer  608  may include a display for presenting information or data to the user based on the sensor data received from the sensing arrangement  604 , such as, for example, a current glucose level of the user, a graph or chart of the user&#39;s glucose level versus time, device status indicators, alert messages, or the like. In other embodiments, the infusion device  602 , the CCD  606  and/or the computer  608  may include electronics and software that are configured to analyze sensor data and operate the infusion device  602  to deliver fluid to the body of the user based on the sensor data and/or preprogrammed delivery routines. Thus, in exemplary embodiments, one or more of the infusion device  602 , the sensing arrangement  604 , the CCD  606 , and/or the computer  608  includes a transmitter, a receiver, and/or other transceiver electronics that allow for communication with other components of the infusion system  600 , so that the sensing arrangement  604  may transmit sensor data or monitor data to one or more of the infusion device  602 , the CCD  606  and/or the computer  608 . 
     Still referring to  FIG. 6 , in various embodiments, the sensing arrangement  604  may be secured to the body of the user or embedded in the body of the user at a location that is remote from the location at which the infusion device  602  is secured to the body of the user. In various other embodiments, the sensing arrangement  604  may be incorporated within the infusion device  602 . In other embodiments, the sensing arrangement  604  may be separate and apart from the infusion device  602 , and may be, for example, part of the CCD  606 . In such embodiments, the sensing arrangement  604  may be configured to receive a biological sample, analyte, or the like, to measure a condition of the user. 
     In various embodiments, the CCD  606  and/or the computer  608  may include electronics and other components configured to perform processing, delivery routine storage, and to control the infusion device  602  in a manner that is influenced by sensor data measured by and/or received from the sensing arrangement  604 . By including control functions in the CCD  606  and/or the computer  608 , the infusion device  602  may be made with more simplified electronics. However, in other embodiments, the infusion device  602  may include all control functions, and may operate without the CCD  606  and/or the computer  608 . In various embodiments, the CCD  606  may be a portable electronic device. In addition, in various embodiments, the infusion device  602  and/or the sensing arrangement  604  may be configured to transmit data to the CCD  606  and/or the computer  608  for display or processing of the data by the CCD  606  and/or the computer  608 . 
     In some embodiments, the CCD  606  and/or the computer  608  may provide information to the user that facilitates the user&#39;s subsequent use of the infusion device  602 . For example, the CCD  606  may provide information to the user to allow the user to determine the rate or dose of medication to be administered into the user&#39;s body. In other embodiments, the CCD  606  may provide information to the infusion device  602  to autonomously control the rate or dose of medication administered into the body of the user. In some embodiments, the sensing arrangement  604  may be integrated into the CCD  606 . Such embodiments may allow the user to monitor a condition by providing, for example, a sample of his or her blood to the sensing arrangement  604  to assess his or her condition. In some embodiments, the sensing arrangement  604  and the CCD  606  may be used for determining glucose levels in the blood and/or body fluids of the user without the use of, or necessity of, a wire or cable connection between the infusion device  602  and the sensing arrangement  604  and/or the CCD  606 . 
     In one or more exemplary embodiments, the sensing arrangement  604  and/or the infusion device  602  are cooperatively configured to utilize a closed-loop system for delivering fluid to the user. Examples of sensing devices and/or infusion pumps utilizing closed-loop systems may be found at, but are not limited to, the following U.S. Pat. Nos. 6,088,608, 6,119,028, 6,589,229, 6,740,072, 6,827,702, 7,323,142, and 7,402,153, all of which are incorporated herein by reference in their entirety. In such embodiments, the sensing arrangement  604  is configured to sense or measure a condition of the user, such as, blood glucose level or the like. The infusion device  602  is configured to deliver fluid in response to the condition sensed by the sensing arrangement  604 . In turn, the sensing arrangement  604  continues to sense or otherwise quantify a current condition of the user, thereby allowing the infusion device  602  to deliver fluid continuously in response to the condition currently (or most recently) sensed by the sensing arrangement  604  indefinitely. In some embodiments, the sensing arrangement  604  and/or the infusion device  602  may be configured to utilize the closed-loop system only for a portion of the day, for example only when the user is asleep or awake. 
       FIGS. 7-9  depict one exemplary embodiment of a fluid infusion device  700  (or alternatively, infusion pump) suitable for use in an infusion system, such as, for example, as infusion device  602  in the infusion system  600  of  FIG. 6 . The fluid infusion device  700  is a portable medical device designed to be carried or worn by a patient (or user), and the fluid infusion device  700  may leverage any number of conventional features, components, elements, and characteristics of existing fluid infusion devices, such as, for example, some of the features, components, elements, and/or characteristics described in U.S. Pat. Nos. 6,485,465 and 7,621,893. It should be appreciated that  FIGS. 7-9  depict some aspects of the infusion device  700  in a simplified manner; in practice, the infusion device  700  could include additional elements, features, or components that are not shown or described in detail herein. 
     As best illustrated in  FIGS. 7-8 , the illustrated embodiment of the fluid infusion device  700  includes a housing  702  adapted to receive a fluid-containing reservoir  705 . An opening  720  in the housing  702  accommodates a fitting  723  (or cap) for the reservoir  705 , with the fitting  723  being configured to mate or otherwise interface with tubing  721  of an infusion set  725  that provides a fluid path to/from the body of the user. In this manner, fluid communication from the interior of the reservoir  705  to the user is established via the tubing  721 . The illustrated fluid infusion device  700  includes a human-machine interface (HMI)  730  (or user interface) that includes elements  732 ,  734  that can be manipulated by the user to administer a bolus of fluid (e.g., insulin), to change therapy settings, to change user preferences, to select display features, and the like. The infusion device also includes a display element  726 , such as a liquid crystal display (LCD) or another suitable display element, that can be used to present various types of information or data to the user, such as, without limitation: the current glucose level of the patient; the time; a graph or chart of the patient&#39;s glucose level versus time; device status indicators; etc. 
     The housing  702  is formed from a substantially rigid material having a hollow interior  714  adapted to allow an electronics assembly  704 , a sliding member (or slide)  706 , a drive system  708 , a sensor assembly  710 , and a drive system capping member  712  to be disposed therein in addition to the reservoir  705 , with the contents of the housing  702  being enclosed by a housing capping member  716 . The opening  720 , the slide  706 , and the drive system  708  are coaxially aligned in an axial direction (indicated by arrow  718 ), whereby the drive system  708  facilitates linear displacement of the slide  706  in the axial direction  718  to dispense fluid from the reservoir  705  (after the reservoir  705  has been inserted into opening  720 ), with the sensor assembly  710  being configured to measure axial forces (e.g., forces aligned with the axial direction  718 ) exerted on the sensor assembly  710  responsive to operating the drive system  708  to displace the slide  706 . In various embodiments, the sensor assembly  710  may be utilized to detect one or more of the following: an occlusion in a fluid path that slows, prevents, or otherwise degrades fluid delivery from the reservoir  705  to a user&#39;s body; when the reservoir  705  is empty; when the slide  706  is properly seated with the reservoir  705 ; when a fluid dose has been delivered; when the infusion pump  700  is subjected to shock or vibration; when the infusion pump  700  requires maintenance. 
     Depending on the embodiment, the fluid-containing reservoir  705  may be realized as a syringe, a vial, a cartridge, a bag, or the like. In certain embodiments, the infused fluid is insulin, although many other fluids may be administered through infusion such as, but not limited to, HIV drugs, drugs to treat pulmonary hypertension, iron chelation drugs, pain medications, anti-cancer treatments, medications, vitamins, hormones, or the like. As best illustrated in  FIGS. 8-9 , the reservoir  705  typically includes a reservoir barrel  719  that contains the fluid and is concentrically and/or coaxially aligned with the slide  706  (e.g., in the axial direction  718 ) when the reservoir  705  is inserted into the infusion pump  700 . The end of the reservoir  705  proximate the opening  720  may include or otherwise mate with the fitting  723 , which secures the reservoir  705  in the housing  702  and prevents displacement of the reservoir  705  in the axial direction  718  with respect to the housing  702  after the reservoir  705  is inserted into the housing  702 . As described above, the fitting  723  extends from (or through) the opening  720  of the housing  702  and mates with tubing  721  to establish fluid communication from the interior of the reservoir  705  (e.g., reservoir barrel  719 ) to the user via the tubing  721  and infusion set  725 . The opposing end of the reservoir  705  proximate the slide  706  includes a plunger  717  (or stopper) positioned to push fluid from inside the barrel  719  of the reservoir  705  along a fluid path through tubing  721  to a user. The slide  706  is configured to mechanically couple or otherwise engage with the plunger  717 , thereby becoming seated with the plunger  717  and/or reservoir  705 . Fluid is forced from the reservoir  705  via tubing  721  as the drive system  708  is operated to displace the slide  706  in the axial direction  718  toward the opening  720  in the housing  702 . 
     In the illustrated embodiment of  FIGS. 8-9 , the drive system  708  includes a motor assembly  707  and a drive screw  709 . The motor assembly  707  includes a motor that is coupled to drive train components of the drive system  708  that are configured to convert rotational motor motion to a translational displacement of the slide  706  in the axial direction  718 , and thereby engaging and displacing the plunger  717  of the reservoir  705  in the axial direction  718 . In some embodiments, the motor assembly  707  may also be powered to translate the slide  706  in the opposing direction (e.g., the direction opposite direction  718 ) to retract and/or detach from the reservoir  705  to allow the reservoir  705  to be replaced. In exemplary embodiments, the motor assembly  707  includes a brushless DC (BLDC) motor having one or more permanent magnets mounted, affixed, or otherwise disposed on its rotor. However, the subject matter described herein is not necessarily limited to use with BLDC motors, and in alternative embodiments, the motor may be realized as a solenoid motor, an AC motor, a stepper motor, a piezoelectric caterpillar drive, a shape memory actuator drive, an electrochemical gas cell, a thermally driven gas cell, a bimetallic actuator, or the like. The drive train components may comprise one or more lead screws, cams, ratchets, jacks, pulleys, pawls, clamps, gears, nuts, slides, bearings, levers, beams, stoppers, plungers, sliders, brackets, guides, bearings, supports, bellows, caps, diaphragms, bags, heaters, or the like. In this regard, although the illustrated embodiment of the infusion pump utilizes a coaxially aligned drive train, the motor could be arranged in an offset or otherwise non-coaxial manner, relative to the longitudinal axis of the reservoir  705 . 
     As best shown in  FIG. 9 , the drive screw  709  mates with threads  902  internal to the slide  706 . When the motor assembly  707  is powered and operated, the drive screw  709  rotates, and the slide  706  is forced to translate in the axial direction  718 . In an exemplary embodiment, the infusion pump  700  includes a sleeve  711  to prevent the slide  706  from rotating when the drive screw  709  of the drive system  708  rotates. Thus, rotation of the drive screw  709  causes the slide  706  to extend or retract relative to the drive motor assembly  707 . When the fluid infusion device is assembled and operational, the slide  706  contacts the plunger  717  to engage the reservoir  705  and control delivery of fluid from the infusion pump  700 . In an exemplary embodiment, the shoulder portion  715  of the slide  706  contacts or otherwise engages the plunger  717  to displace the plunger  717  in the axial direction  718 . In alternative embodiments, the slide  706  may include a threaded tip  713  capable of being detachably engaged with internal threads  904  on the plunger  717  of the reservoir  705 , as described in detail in U.S. Pat. Nos. 6,248,093 and 6,485,465, which are incorporated by reference herein. 
     As illustrated in  FIG. 8 , the electronics assembly  704  includes control electronics  724  coupled to the display element  726 , with the housing  702  including a transparent window portion  728  that is aligned with the display element  726  to allow the display  726  to be viewed by the user when the electronics assembly  704  is disposed within the interior  714  of the housing  702 . The control electronics  724  generally represent the hardware, firmware, processing logic and/or software (or combinations thereof) configured to control operation of the motor assembly  707  and/or drive system  708 , as described in greater detail below in the context of  FIG. 10 . Whether such functionality is implemented as hardware, firmware, a state machine, or software depends upon the particular application and design constraints imposed on the embodiment. Those familiar with the concepts described here may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as being restrictive or limiting. In an exemplary embodiment, the control electronics  724  includes one or more programmable controllers that may be programmed to control operation of the infusion pump  700 . 
     The motor assembly  707  includes one or more electrical leads  736  adapted to be electrically coupled to the electronics assembly  704  to establish communication between the control electronics  724  and the motor assembly  707 . In response to command signals from the control electronics  724  that operate a motor driver (e.g., a power converter) to regulate the amount of power supplied to the motor from a power supply, the motor actuates the drive train components of the drive system  708  to displace the slide  706  in the axial direction  718  to force fluid from the reservoir  705  along a fluid path (including tubing  721  and an infusion set), thereby administering doses of the fluid contained in the reservoir  705  into the user&#39;s body. Preferably, the power supply is realized one or more batteries contained within the housing  702 . Alternatively, the power supply may be a solar panel, capacitor, AC or DC power supplied through a power cord, or the like. In some embodiments, the control electronics  724  may operate the motor of the motor assembly  707  and/or drive system  708  in a stepwise manner, typically on an intermittent basis; to administer discrete precise doses of the fluid to the user according to programmed delivery profiles. 
     Referring to  FIGS. 7-9 , as described above, the user interface  730  includes HMI elements, such as buttons  732  and a directional pad  734 , that are formed on a graphic keypad overlay  731  that overlies a keypad assembly  733 , which includes features corresponding to the buttons  732 , directional pad  734  or other user interface items indicated by the graphic keypad overlay  731 . When assembled, the keypad assembly  733  is coupled to the control electronics  724 , thereby allowing the HMI elements  732 ,  734  to be manipulated by the user to interact with the control electronics  724  and control operation of the infusion pump  700 , for example, to administer a bolus of insulin, to change therapy settings, to change user preferences, to select display features, to set or disable alarms and reminders, and the like. In this regard, the control electronics  724  maintains and/or provides information to the display  726  regarding program parameters, delivery profiles, pump operation, alarms, warnings, statuses, or the like, which may be adjusted using the HMI elements  732 ,  734 . In various embodiments, the HMI elements  732 ,  734  may be realized as physical objects (e.g., buttons, knobs, joysticks, and the like) or virtual objects (e.g., using touch-sensing and/or proximity-sensing technologies). For example, in some embodiments, the display  726  may be realized as a touch screen or touch-sensitive display, and in such embodiments, the features and/or functionality of the HMI elements  732 ,  734  may be integrated into the display  726  and the HMI  730  may not be present. In some embodiments, the electronics assembly  704  may also include alert generating elements coupled to the control electronics  724  and suitably configured to generate one or more types of feedback, such as, without limitation: audible feedback; visual feedback; haptic (physical) feedback; or the like. 
     Referring to  FIGS. 8-9 , in accordance with one or more embodiments, the sensor assembly  710  includes a back plate structure  750  and a loading element  760 . The loading element  760  is disposed between the capping member  712  and a beam structure  770  that includes one or more beams having sensing elements disposed thereon that are influenced by compressive force applied to the sensor assembly  710  that deflects the one or more beams, as described in greater detail in U.S. Pat. No. 8,474,332, which is incorporated by reference herein. In exemplary embodiments, the back plate structure  750  is affixed, adhered, mounted, or otherwise mechanically coupled to the bottom surface  738  of the drive system  708  such that the back plate structure  750  resides between the bottom surface  738  of the drive system  708  and the housing cap  716 . The drive system capping member  712  is contoured to accommodate and conform to the bottom of the sensor assembly  710  and the drive system  708 . The drive system capping member  712  may be affixed to the interior of the housing  702  to prevent displacement of the sensor assembly  710  in the direction opposite the direction of force provided by the drive system  708  (e.g., the direction opposite direction  718 ). Thus, the sensor assembly  710  is positioned between the motor assembly  707  and secured by the capping member  712 , which prevents displacement of the sensor assembly  710  in a downward direction opposite the direction of arrow  718 , such that the sensor assembly  710  is subjected to a reactionary compressive force when the drive system  708  and/or motor assembly  707  is operated to displace the slide  706  in the axial direction  718  in opposition to the fluid pressure in the reservoir  705 . Under normal operating conditions, the compressive force applied to the sensor assembly  710  is correlated with the fluid pressure in the reservoir  705 . As shown, electrical leads  740  are adapted to electrically couple the sensing elements of the sensor assembly  710  to the electronics assembly  704  to establish communication to the control electronics  724 , wherein the control electronics  724  are configured to measure, receive, or otherwise obtain electrical signals from the sensing elements of the sensor assembly  710  that are indicative of the force applied by the drive system  708  in the axial direction  718 . 
       FIG. 10  depicts an exemplary embodiment of a control system  1000  suitable for use with an infusion device  1002 , such as any one of the infusion devices  202 ,  602 ,  700  described above. The control system  1000  is capable of controlling or otherwise regulating a physiological condition in the body  1001  of a user to a desired (or target) value or otherwise maintain the condition within a range of acceptable values in an automated or autonomous manner. In one or more exemplary embodiments, the condition being regulated is sensed, detected, measured or otherwise quantified by a sensing arrangement  1004  (e.g., sensing arrangement  604 ) communicatively coupled to the infusion device  1002 . However, it should be noted that in alternative embodiments, the condition being regulated by the control system  1000  may be correlative to the measured values obtained by the sensing arrangement  1004 . That said, for clarity and purposes of explanation, the subject matter may be described herein in the context of the sensing arrangement  1004  being realized as a glucose sensing arrangement that senses, detects, measures or otherwise quantifies the user&#39;s glucose level, which is being regulated in the body  1001  of the user by the control system  1000 . 
     In exemplary embodiments, the sensing arrangement  1004  includes one or more interstitial glucose sensing elements that generate or otherwise output electrical signals having a signal characteristic that is correlative to, influenced by, or otherwise indicative of the relative interstitial fluid glucose level in the body  1001  of the user. The output electrical signals are filtered or otherwise processed to obtain a measurement value indicative of the user&#39;s interstitial fluid glucose level. In exemplary embodiments, a blood glucose meter  1030 , such as a finger stick device, is utilized to directly sense, detect, measure or otherwise quantify the blood glucose in the body  1001  of the user. In this regard, the blood glucose meter  1030  outputs or otherwise provides a measured blood glucose value that may be utilized as a reference measurement for calibrating the sensing arrangement  1004  and converting a measurement value indicative of the user&#39;s interstitial fluid glucose level into a corresponding calibrated blood glucose value. For purposes of explanation, the calibrated blood glucose value calculated based on the electrical signals output by the sensing element(s) of the sensing arrangement  1004  may alternatively be referred to herein as the sensor glucose value, the sensed glucose value, or variants thereof. 
     In the illustrated embodiment, the pump control system  1020  generally represents the electronics and other components of the infusion device  1002  that control operation of the fluid infusion device  1002  according to a desired infusion delivery program in a manner that is influenced by the sensed glucose value indicative of a current glucose level in the body  1001  of the user. For example, to support a closed-loop operating mode, the pump control system  1020  maintains, receives, or otherwise obtains a target or commanded glucose value, and automatically generates or otherwise determines dosage commands for operating an actuation arrangement, such as a motor  1007 , to displace the plunger  1017  and deliver insulin to the body  1001  of the user based on the difference between a sensed glucose value and the target glucose value. In other operating modes, the pump control system  1020  may generate or otherwise determine dosage commands configured to maintain the sensed glucose value below an upper glucose limit, above a lower glucose limit, or otherwise within a desired range of glucose values. In practice, the infusion device  1002  may store or otherwise maintain the target value, upper and/or lower glucose limit(s), and/or other glucose threshold value(s) in a data storage element accessible to the pump control system  1020 . 
     The target glucose value and other threshold glucose values may be received from an external component (e.g., CCD  606  and/or computing device  608 ) or be input by a user via a user interface element  1040  associated with the infusion device  1002 . In practice, the one or more user interface element(s)  1040  associated with the infusion device  1002  typically include at least one input user interface element, such as, for example, a button, a keypad, a keyboard, a knob, a joystick, a mouse, a touch panel, a touchscreen, a microphone or another audio input device, and/or the like. Additionally, the one or more user interface element(s)  1040  include at least one output user interface element, such as, for example, a display element (e.g., a light-emitting diode or the like), a display device (e.g., a liquid crystal display or the like), a speaker or another audio output device, a haptic feedback device, or the like, for providing notifications or other information to the user. It should be noted that although  FIG. 10  depicts the user interface element(s)  1040  as being separate from the infusion device  1002 , in practice, one or more of the user interface element(s)  1040  may be integrated with the infusion device  1002 . Furthermore, in some embodiments, one or more user interface element(s)  1040  are integrated with the sensing arrangement  1004  in addition to and/or in alternative to the user interface element(s)  1040  integrated with the infusion device  1002 . The user interface element(s)  1040  may be manipulated by the user to operate the infusion device  1002  to deliver correction boluses, adjust target and/or threshold values, modify the delivery control scheme or operating mode, and the like, as desired. 
     Still referring to  FIG. 10 , in the illustrated embodiment, the infusion device  1002  includes a motor control module  1012  coupled to a motor  1007  (e.g., motor assembly  707 ) that is operable to displace a plunger  1017  (e.g., plunger  717 ) in a reservoir (e.g., reservoir  705 ) and provide a desired amount of fluid to the body  1001  of a user. In this regard, displacement of the plunger  1017  results in the delivery of a fluid that is capable of influencing the condition in the body  1001  of the user to the body  1001  of the user via a fluid delivery path (e.g., via tubing  721  of an infusion set  725 ). A motor driver module  1014  is coupled between an energy source  1003  and the motor  1007 . The motor control module  1012  is coupled to the motor driver module  1014 , and the motor control module  1012  generates or otherwise provides command signals that operate the motor driver module  1014  to provide current (or power) from the energy source  1003  to the motor  1007  to displace the plunger  1017  in response to receiving, from a pump control system  1020 , a dosage command indicative of the desired amount of fluid to be delivered. 
     In exemplary embodiments, the energy source  1003  is realized as a battery housed within the infusion device  1002  (e.g., within housing  702 ) that provides direct current (DC) power. In this regard, the motor driver module  1014  generally represents the combination of circuitry, hardware and/or other electrical components configured to convert or otherwise transfer DC power provided by the energy source  1003  into alternating electrical signals applied to respective phases of the stator windings of the motor  1007  that result in current flowing through the stator windings that generates a stator magnetic field and causes the rotor of the motor  1007  to rotate. The motor control module  1012  is configured to receive or otherwise obtain a commanded dosage from the pump control system  1020 , convert the commanded dosage to a commanded translational displacement of the plunger  1017 , and command, signal, or otherwise operate the motor driver module  1014  to cause the rotor of the motor  1007  to rotate by an amount that produces the commanded translational displacement of the plunger  1017 . For example, the motor control module  1012  may determine an amount of rotation of the rotor required to produce translational displacement of the plunger  1017  that achieves the commanded dosage received from the pump control system  1020 . Based on the current rotational position (or orientation) of the rotor with respect to the stator that is indicated by the output of the rotor sensing arrangement  1016 , the motor control module  1012  determines the appropriate sequence of alternating electrical signals to be applied to the respective phases of the stator windings that should rotate the rotor by the determined amount of rotation from its current position (or orientation). In embodiments where the motor  1007  is realized as a BLDC motor, the alternating electrical signals commutate the respective phases of the stator windings at the appropriate orientation of the rotor magnetic poles with respect to the stator and in the appropriate order to provide a rotating stator magnetic field that rotates the rotor in the desired direction. Thereafter, the motor control module  1012  operates the motor driver module  1014  to apply the determined alternating electrical signals (e.g., the command signals) to the stator windings of the motor  1007  to achieve the desired delivery of fluid to the user. 
     When the motor control module  1012  is operating the motor driver module  1014 , current flows from the energy source  1003  through the stator windings of the motor  1007  to produce a stator magnetic field that interacts with the rotor magnetic field. In some embodiments, after the motor control module  1012  operates the motor driver module  1014  and/or motor  1007  to achieve the commanded dosage, the motor control module  1012  ceases operating the motor driver module  1014  and/or motor  1007  until a subsequent dosage command is received. In this regard, the motor driver module  1014  and the motor  1007  enter an idle state during which the motor driver module  1014  effectively disconnects or isolates the stator windings of the motor  1007  from the energy source  1003 . In other words, current does not flow from the energy source  1003  through the stator windings of the motor  1007  when the motor  1007  is idle, and thus, the motor  1007  does not consume power from the energy source  1003  in the idle state, thereby improving efficiency. 
     Depending on the embodiment, the motor control module  1012  may be implemented or realized with a general purpose processor, a microprocessor, a controller, a microcontroller, a state machine, a content addressable memory, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In exemplary embodiments, the motor control module  1012  includes or otherwise accesses a data storage element or memory, including any sort of random access memory (RAM), read only memory (ROM), flash memory, registers, hard disks, removable disks, magnetic or optical mass storage, or any other short or long term storage media or other non-transitory computer-readable medium, which is capable of storing programming instructions for execution by the motor control module  1012 . The computer-executable programming instructions, when read and executed by the motor control module  1012 , cause the motor control module  1012  to perform or otherwise support the tasks, operations, functions, and processes described herein. 
     It should be appreciated that  FIG. 10  is a simplified representation of the infusion device  1002  for purposes of explanation and is not intended to limit the subject matter described herein in any way. In this regard, depending on the embodiment, some features and/or functionality of the sensing arrangement  1004  may implemented by or otherwise integrated into the pump control system  1020 , or vice versa. Similarly, in practice, the features and/or functionality of the motor control module  1012  may implemented by or otherwise integrated into the pump control system  1020 , or vice versa. Furthermore, the features and/or functionality of the pump control system  1020  may be implemented by control electronics  724  located in the fluid infusion device  700 , while in alternative embodiments, the pump control system  1020  may be implemented by a remote computing device that is physically distinct and/or separate from the infusion device  1002 , such as, for example, the CCD  606  or the computing device  608 . 
       FIG. 11  depicts an exemplary embodiment of a pump control system  1100  suitable for use as the pump control system  1020  in  FIG. 10  in accordance with one or more embodiments. The illustrated pump control system  1100  includes, without limitation, a pump control module  1102 , a communications interface  1104 , and a data storage element (or memory)  1106 . The pump control module  1102  is coupled to the communications interface  1104  and the memory  1106 , and the pump control module  1102  is suitably configured to support the operations, tasks, and/or processes described herein. In exemplary embodiments, the pump control module  1102  is also coupled to one or more user interface elements  1108  (e.g., user interface  730 ,  1040 ) for receiving user input and providing notifications, alerts, or other therapy information to the user. Although  FIG. 11  depicts the user interface element  1108  as being separate from the pump control system  1100 , in various alternative embodiments, the user interface element  1108  may be integrated with the pump control system  1100  (e.g., as part of the infusion device  700 ,  1002 ), the sensing arrangement  1004  or another element of an infusion system  600  (e.g., the computer  608  or CCD  606 ). 
     Referring to  FIG. 11  and with reference to  FIG. 10 , the communications interface  1104  generally represents the hardware, circuitry, logic, firmware and/or other components of the pump control system  1100  that are coupled to the pump control module  1102  and configured to support communications between the pump control system  1100  and the sensing arrangement  1004 . In this regard, the communications interface  1104  may include or otherwise be coupled to one or more transceiver modules capable of supporting wireless communications between the pump control system  1020 ,  1100  and the sensing arrangement  1004  or another electronic device  206 ,  210 ,  500 ,  512 ,  606 ,  608  in an infusion system  600  or a management system  200 ,  516 . For example, the communications interface  1104  may be utilized to receive sensor measurement values or other measurement data from a sensing arrangement  604 ,  1004  as well as upload such sensor measurement values to a server  206  or other computing device  210 ,  500 ,  512 ,  1008  for purposes of generating a report including a snapshot GUI display as described above in the context of  FIGS. 1-6 . In other embodiments, the communications interface  1104  may be configured to support wired communications to/from the sensing arrangement  1004 . 
     The pump control module  1102  generally represents the hardware, circuitry, logic, firmware and/or other component of the pump control system  1100  that is coupled to the communications interface  1104  and configured to determine dosage commands for operating the motor  1006  to deliver fluid to the body  1001  based on data received from the sensing arrangement  1004  and perform various additional tasks, operations, functions and/or operations described herein. For example, in exemplary embodiments, pump control module  1102  implements or otherwise executes a command generation application  1110  that supports one or more autonomous operating modes and calculates or otherwise determines dosage commands for operating the motor  1006  of the infusion device  1002  in an autonomous operating mode based at least in part on a current measurement value for a condition in the body  1001  of the user. For example, in a closed-loop operating mode, the command generation application  1110  may determine a dosage command for operating the motor  1006  to deliver insulin to the body  1001  of the user based at least in part on the current glucose measurement value most recently received from the sensing arrangement  1004  to regulate the user&#39;s blood glucose level to a target reference glucose value. Additionally, the command generation application  610  may generate dosage commands for boluses that are manually-initiated or otherwise instructed by a user via a user interface element  1108 . 
     Still referring to  FIG. 11 , depending on the embodiment, the pump control module  1102  may be implemented or realized with a general purpose processor, a microprocessor, a controller, a microcontroller, a state machine, a content addressable memory, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this regard, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by the pump control module  1102 , or in any practical combination thereof. In exemplary embodiments, the pump control module  1102  includes or otherwise accesses the data storage element or memory  1106 , which may be realized using any sort of non-transitory computer-readable medium capable of storing programming instructions for execution by the pump control module  1102 . The computer-executable programming instructions, when read and executed by the pump control module  1102 , cause the pump control module  1102  to implement or otherwise generate the command generation application  1110  and perform the tasks, operations, functions, and processes described in greater detail below. 
     It should be understood that  FIG. 11  is a simplified representation of a pump control system  1100  for purposes of explanation and is not intended to limit the subject matter described herein in any way. For example, in some embodiments, the features and/or functionality of the motor control module  1012  may be implemented by or otherwise integrated into the pump control system  1100  and/or the pump control module  1102 , for example, by the command generation application  1110  converting the dosage command into a corresponding motor command, in which case, the separate motor control module  1012  may be absent from an embodiment of the infusion device  1002 . 
       FIG. 12  depicts an exemplary closed-loop control system  1200  that may be implemented by a pump control system  1020 ,  1100  to provide a closed-loop operating mode that autonomously regulates a condition in the body of a user to a reference (or target) value. It should be appreciated that  FIG. 12  is a simplified representation of the control system  1200  for purposes of explanation and is not intended to limit the subject matter described herein in any way. 
     In exemplary embodiments, the control system  1200  receives or otherwise obtains a target glucose value at input  1202 . In some embodiments, the target glucose value may be stored or otherwise maintained by the infusion device  1002  (e.g., in memory  1106 ), however, in some alternative embodiments, the target value may be received from an external component (e.g., CCD  606  and/or computer  608 ). In one or more embodiments, the target glucose value may be dynamically calculated or otherwise determined prior to entering the closed-loop operating mode based on one or more patient-specific control parameters. For example, the target blood glucose value may be calculated based at least in part on a patient-specific reference basal rate and a patient-specific daily insulin requirement, which are determined based on historical delivery information over a preceding interval of time (e.g., the amount of insulin delivered over the preceding 24 hours). The control system  1200  also receives or otherwise obtains a current glucose measurement value (e.g., the most recently obtained sensor glucose value) from the sensing arrangement  1004  at input  1204 . The illustrated control system  1200  implements or otherwise provides proportional-integral-derivative (PID) control to determine or otherwise generate delivery commands for operating the motor  1010  based at least in part on the difference between the target glucose value and the current glucose measurement value. In this regard, the PID control attempts to minimize the difference between the measured value and the target value, and thereby regulates the measured value to the desired value. PID control parameters are applied to the difference between the target glucose level at input  1202  and the measured glucose level at input  1204  to generate or otherwise determine a dosage (or delivery) command provided at output  1230 . Based on that delivery command, the motor control module  1012  operates the motor  1010  to deliver insulin to the body of the user to influence the user&#39;s glucose level, and thereby reduce the difference between a subsequently measured glucose level and the target glucose level. 
     The illustrated control system  1200  includes or otherwise implements a summation block  1206  configured to determine a difference between the target value obtained at input  1202  and the measured value obtained from the sensing arrangement  1004  at input  1204 , for example, by subtracting the target value from the measured value. The output of the summation block  1206  represents the difference between the measured and target values, which is then provided to each of a proportional term path, an integral term path, and a derivative term path. The proportional term path includes a gain block  1220  that multiplies the difference by a proportional gain coefficient, K P , to obtain the proportional term. The integral term path includes an integration block  1208  that integrates the difference and a gain block  1222  that multiplies the integrated difference by an integral gain coefficient, K I , to obtain the integral term. The derivative term path includes a derivative block  1210  that determines the derivative of the difference and a gain block  1224  that multiplies the derivative of the difference by a derivative gain coefficient, K D , to obtain the derivative term. The proportional term, the integral term, and the derivative term are then added or otherwise combined to obtain a delivery command that is utilized to operate the motor at output  1230 . Various implementation details pertaining to closed-loop PID control and determine gain coefficients are described in greater detail in U.S. Pat. No. 7,402,153, which is incorporated by reference. 
     In one or more exemplary embodiments, the PID gain coefficients are user-specific (or patient-specific) and dynamically calculated or otherwise determined prior to entering the closed-loop operating mode based on historical insulin delivery information (e.g., amounts and/or timings of previous dosages, historical correction bolus information, or the like), historical sensor measurement values, historical reference blood glucose measurement values, user-reported or user-input events (e.g., meals, exercise, and the like), and the like. In this regard, one or more patient-specific control parameters (e.g., an insulin sensitivity factor, a daily insulin requirement, an insulin limit, a reference basal rate, a reference fasting glucose, an active insulin action duration, pharmodynamical time constants, or the like) may be utilized to compensate, correct, or otherwise adjust the PID gain coefficients to account for various operating conditions experienced and/or exhibited by the infusion device  1002 . The PID gain coefficients may be maintained by the memory  1106  accessible to the pump control module  1102 . In this regard, the memory  1106  may include a plurality of registers associated with the control parameters for the PID control. For example, a first parameter register may store the target glucose value and be accessed by or otherwise coupled to the summation block  1206  at input  1202 , and similarly, a second parameter register accessed by the proportional gain block  1220  may store the proportional gain coefficient, a third parameter register accessed by the integration gain block  1222  may store the integration gain coefficient, and a fourth parameter register accessed by the derivative gain block  1224  may store the derivative gain coefficient. 
     Therapeutic Recommendations for Event Pattern Mitigation 
     As described in greater detail below, in exemplary embodiments, at least one of the detected event patterns presented in a snapshot GUI display is analyzed to determine one or more recommended remedial actions for addressing the detected event pattern. In this regard, based on the type of event pattern detected, the patient&#39;s current therapy regimen, and the patient&#39;s physiological condition, recommended modifications or adjustments to the patient&#39;s current therapy regimen may be determined and indicated on the snapshot GUI display. In one or more embodiments, logic rules or formula are maintained and utilized to determine how the patient&#39;s current therapy regimen should be modified given the patient&#39;s current therapy configuration, the patient&#39;s physiological condition, the event pattern type, and potentially other patient-specific variables or factors (e.g., the monitoring period associated with the event pattern, the severity or frequency of events, and the like). Thus, the recommended remedial actions may vary depending on the patient&#39;s current therapy regimen and dosages, the patient&#39;s A1C or glucose levels, the type of event pattern detected, and so on. 
       FIG. 13  depicts an exemplary recommendation process  1300  suitable for implementation by a patient management system in connection with one or more of the presentation processes  300 ,  400  described above to provide recommended therapeutic remedial actions for resolving, correcting, or otherwise mitigating an event pattern presented on a GUI display, such as snapshot GUI display  100  of  FIG. 1 . The various tasks performed in connection with the recommendation process  1300  may be performed by hardware, firmware, software executed by processing circuitry, or any combination thereof. For illustrative purposes, the following description refers to elements mentioned above in connection with  FIG. 2 . In practice, portions of the recommendation process  1300  may be performed by different elements of the patient management system  200 , such as, for example, the infusion device  202 , the sensing arrangement  204 , the server  206 , the database  208 , the client device  210 , the client application  212 , and/or the processing system  216 . It should be appreciated that the recommendation process  1300  may include any number of additional or alternative tasks, the tasks need not be performed in the illustrated order and/or the tasks may be performed concurrently, and/or the recommendation process  1300  may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein. Moreover, one or more of the tasks shown and described in the context of  FIG. 13  could be omitted from a practical embodiment of the recommendation process  1300  as long as the intended overall functionality remains intact. 
     The recommendation process  1300  initializes or begins by identifying or otherwise determining the event pattern to be analyzed for recommending therapeutic remedial actions (task  1302 ). In one or more exemplary embodiments, only the highest priority event pattern from among the prioritized event patterns is identified for analysis. In this regard, remedial actions that may be taken by a patient or user to mitigate or otherwise address the highest priority event pattern could also influence or resolve the lower priority event patterns, and hence, providing multiple different recommended therapeutic remedial actions for multiple different event patterns could be unnecessary and confusing. However, in alternative embodiments, each of the prioritized event patterns displayed on a GUI display (e.g., each of the remaining event patterns in the filtered prioritized list at  318 ) may be identified and analyzed by the recommendation process  1300  to provide multiple different options for therapy modifications that could be undertaken. In yet other embodiments, the recommendation process  1300  may be triggered or initiated by user selection of a particular event pattern for analysis (e.g., from within the event pattern analysis region or another GUI display), whereby the event pattern whose selection triggered the recommendation process  1300  is identified as the event pattern for analysis. 
     In the illustrated embodiment, the recommendation process  1300  continues by identifying, obtaining or otherwise determining physiological information associated with the patient (task  1304 ). In this regard, the server  206  obtains or calculates physiological information associated with the patient, such as, for example, the estimated A1C (or alternatively, glycohemoglobin or glycated hemoglobin) level calculated based on the sensor glucose measurement values over the snapshot time period, the average sensor glucose measurement values over the snapshot time period, the average reference blood glucose measurement values (e.g., from a blood glucose meter) over the snapshot time period, and the like. Depending on the embodiment, the server  206  may obtain the patient physiological information from the database  208  and/or infusion device  202 , or the server  206  may obtain historical sensor measurements from the database  208  and/or infusion device  202  and utilize the obtained historical measurements to calculate the physiological information associated with the patient for the snapshot time period. 
     The recommendation process  1300  also identifies, obtains or otherwise determines current therapeutic information for the patient (task  1306 ). In this regard, the recommendation process  1300  identified or determines the current medications, dosages, types of therapy, and other therapeutic settings or configurations associated with the patient. For example, the database  208  may maintain a patient profile or similar record or entry that maintains an association between one or more patient identifiers and the current therapy assigned or associated with the patient, including, the current medications prescribed to the patient, the type or manner of administration (e.g., basal infusion, boluses or manual injections, oral administration, or the like), the number and/or amount of dosages prescribed to the patient, and potentially other information characterizing the current therapy associated with the patient. The patient profile in the database  208  may also include other clinical or physiological data associated with the patient that may influence suggested or recommended therapy modifications, such as, for example, the patient&#39;s height, weight, cholesterol levels, blood pressure, activity metrics or data, sleep quality data, and the like. In other embodiments, the current therapy information may be stored or maintained at one of the infusion device  202  and the client device  210  and retrieved by the server  206  via the network  214 . 
     The recommendation process  1300  continues by identifying or otherwise obtaining therapeutic modification logic associated with the identified event pattern and corresponding to the physiological condition of the patient and current patient therapy (task  1308 ). In exemplary embodiments, the database  208  maintains one or more tables or lists of logic rules for determining therapy adjustments or modifications in association with a particular combination of event pattern, medications involved in the patient&#39;s therapy, and the patient&#39;s physiological condition. Thus, different types of adjustments or modifications may be indicated for a particular event pattern, depending on the particular physiological condition of the patient. For example, an event pattern could potentially be resolved by increasing or decreasing a dosage of a particular medication rather than adding or removing a medication to the patient&#39;s therapy, depending on the estimated A1C level and/or the mean sensor glucose level for the patient. As another example, adjustments or modifications may be indicated (or not indicated) for a particular event pattern based on the patient&#39;s specific glycemic goals or other objectives that may be established by the patient&#39;s healthcare provider, or whether or not such goals or objectives have already been achieved. In exemplary embodiments, after identifying the event pattern to be analyzed for a particular patient and the relevant physiological information and combination of medications for the patient, the server  206  accesses the database  208  (or alternatively another device  202 ,  210  via the network  214 ) to retrieve the corresponding therapy modification logic rules associated with the identified event pattern and corresponding to the combination of the detected event pattern, combination of medications, and the patient&#39;s physiological condition. 
     Still referring to  FIG. 13 , the recommendation process  1300  continues by determining one or more therapeutic modifications for mitigating, resolving, or otherwise addressing the event pattern by applying the obtained therapy modification logic rules using the patient&#39;s current therapy configuration and physiological condition (task  1310 ). In exemplary embodiments, the server  206  applies the obtained therapy modification logic rules associated with the event pattern to the current dosages associated with the patient&#39;s current therapy to determine recommended therapy modifications for mitigating, resolving, or otherwise addressing the event pattern. For example, if the current dosage of a particular medication or combination of medications is less than a threshold dosage (e.g., one half of the maximum dosage), then the therapy modification logic rules may identify or otherwise indicate an amount by which a particular medication should be increased. Conversely, when the current dosage of the particular medication or combination of medications is greater than the threshold dosage, then the therapy modification logic rules may identify or otherwise indicate another medication that should be added to the patient&#39;s therapy. For dual therapy or other therapy configurations with multiple medications, the therapy modification logic rules may identify or otherwise indicate which of the medications should have its dosage adjusted when the combined dosage is less than a threshold for the combined medications. 
     In some embodiments, the therapy modification logic rules utilized by the recommendation process  1300  may also consider patient physiological information, such as, for example, sensor glucose measurement values or one or more performance metrics calculated based on the historical measurement data for the patient. In this regard, a recommended therapy modification could be influenced by one or more of the estimated A1C level calculated based on sensor glucose measurement values over the snapshot time period or the estimated percentage(s) of the snapshot time period during which the patient&#39;s sensor glucose measurement values were above an upper glucose threshold value (e.g., 150 mg/dL), below a lower glucose threshold value (e.g., 70 mg/dL), or between the upper and lower glucose threshold values corresponding to a target sensor glucose range. Thus, the recommended therapy modification chosen or selected by the recommendation process  1300  may be one that is likely to resolve, mitigate, or otherwise address the identified event pattern, while secondarily being most likely to improve one or more performance metrics or other aspects of regulating the patient&#39;s physiological condition. 
     In various embodiments, the recommendation process  1300  may also account for other patient-specific variables which may be stored or otherwise maintained in association with the patient&#39;s profile or electronic medical record in the database  208 . For example, the patient&#39;s A1C goal, previous therapies, allergies and drug intolerances, information characterizing the patient&#39;s renal function, information characterizing the patient&#39;s hepatic function, and the like may be stored in the database  208  and factored in or otherwise accounted for by the therapy modification logic rules. Thus, the recommended therapeutic remedial actions identified by the recommendation process  1300  may be the most appropriate actions for addressing the identified event pattern, accounting for the patient&#39;s physiological condition or glycemic issues, goals or objectives, allergies and drug intolerances, and potentially other clinical variables. 
     Table 1 represents an exemplary set of therapy modification logic rules that may be maintained in a database  208 . It should be noted that Table 1 merely depicts one particular example of therapy modification logic rules for dual combination therapies with a particular A1C level for a particular event pattern, and in practice, the database  208  may maintain any number of different tables to variously accommodate any number of potential event patterns that may be detected, in combination with any number of potential therapy configurations and dosages (including treatment naïve or naïve therapy, monotherapy, and the like), in association with different A1C levels, glucose levels, or other glycemic statuses. In some embodiments, the therapy modification logic rule tables may be stablished or promulgated by a regulatory agency, however, in alternative embodiments, the therapy modification logic rules may be configurable or otherwise specific to a particular doctor, hospital, or other care provider. Accordingly, the subject matter described herein is not limited to the example therapy modification logic rules of Table 1. 
     Table 1 depicts therapy modification logic rules associated with a hyperglycemic event pattern associated with a post-meal monitoring period for estimated A1C levels below a threshold value of 9%. The logic rules depend on the particular dual combination therapy that the patient it utilizing (e.g., any two of Metformin (Met), a dipeptidyl peptidase 4 (DPP-4) inhibitor, a glucagon-like peptide-1 (GLP-1) receptor agonist, Sulfonylurea or glinide (SU/glinide), Thiazolidenedione (TZD), a sodium-glucose co-transporter 2 (SGLT-2) inhibitor, or basal insulin), and whether or not the current dosage information is less than one half of the maximum dosage associated with the particular dual combination therapy. For example, for a patient with a current therapy configuration of Metformin and a DPP-4 inhibitor (Met+DPP-4) with a current dosage less than one half the maximum dosage of the dual combination, a therapeutic modification of increasing the dosage of the DPP-4 inhibitor may be identified and recommended or otherwise indicated on a snapshot GUI display for the patient. Alternatively, for a patient with a current therapy configuration of Metformin and Thiazolidenedione (Met+TZD) with a current dosage less than one half the maximum dosage of the dual combination, therapeutic modifications of adding one of a DPP-4 inhibitor, a GLP-1 receptor agonist, a SGLT-2 inhibitor, an alpha-glucosidase inhibitor (AGI), or pre-meal rapid-acting insulin may be identified and recommended or otherwise indicated on a snapshot GUI display for the patient, thereby allowing the patient, doctor, nurse, or other clinician to readily identify the need to increase medications and which options are likely to be best for the patient given the patient&#39;s current therapy configuration. 
     
       
         
           
               
               
               
             
               
                 TABLE 1 
               
               
                   
               
               
                 Dual Combination 
                 If . . . &lt;½  
                 If ≧½ Max dose of 
               
               
                 Therapy 
                 Max dose of  
                 Dual Combination, Then 
               
               
                 Configuration 
                 Dual Combination 
                 Add one of the following: 
               
               
                   
               
             
            
               
                  Met + DPP-4 
                 Increase dose of DPP-4  
                 SGLT-2 
               
               
                   
                 if appropriate; Also,  
                 AGI 
               
               
                   
                 Add one of the  
                 Pre-meal rapid- 
               
               
                   
                 drugs on right: 
                 acting insulin 
               
               
                  Met + GLP-1 
                 Increase dose of GLP-1  
                 SGLT-2 
               
               
                   
                 if appropriate; Also,  
                 AGI 
               
               
                   
                 Add one of the  
                 Pre-meal rapid- 
               
               
                   
                 drugs on right: 
                 acting insulin 
               
               
                    Met + SU/glinide 
                 Increase dose of SU/ 
                 DPP-4 
               
               
                   
                 glinide if appropriate;  
                 GLP-1 
               
               
                   
                 Also, Add one of the 
                 SGLT-2 
               
               
                   
                 drugs on right: 
                 AGI 
               
               
                   
                   
                 Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                 Met + TZD  
                 Add one of the  
                 DPP-4 
               
               
                   
                 drugs on right: 
                 GLP-1 
               
               
                   
                   
                 SGLT-2 
               
               
                   
                   
                 AGI 
               
               
                   
                   
                 Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                   Met + SGLT-2 
                 Increase dose of SGLT-2  
                 DPP-4 
               
               
                   
                 if appropriate;  
                 GLP-1 
               
               
                   
                 Also, Add one of the 
                 AGI 
               
               
                   
                 drugs on right: 
                 Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                     Met + Basal insulin 
                 Add one of the  
                 DPP-4 
               
               
                   
                 drugs on right: 
                 GLP-1 
               
               
                   
                   
                 SGLT-2 
               
               
                   
                   
                 AGI 
               
               
                   
                   
                 Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                 SU/glinide + DPP-4    
                 Increase dose of SU/ 
                 Met + SGLT-2 
               
               
                   
                 glinide and/or 
                 Met + AGI 
               
               
                   
                 DPP-4 if appropriate;  
                 Met + Pre-meal  
               
               
                   
                 Also, Add one of  
                 rapid-acting insulin 
               
               
                   
                 the drugs on right: 
                   
               
               
                 SU/glinide + GLP-1    
                 Increase dose of SU/ 
                 Met + SGLT-2 
               
               
                   
                 glinide and/or 
                 Met + AGI 
               
               
                   
                 GLP-1 if appropriate;  
                 Met + Pre-meal rapid- 
               
               
                   
                 Also, Add one  
                 acting insulin 
               
               
                   
                 of the drugs on right: 
                   
               
               
                 SU/glinide + TZD     
                 Increase dose of  
                 Met + DPP-4 
               
               
                   
                 SU/glinide if 
                 Met + GLP-1 
               
               
                   
                 appropriate; Also,  
                 Met + SGLT-2 
               
               
                   
                 Add one of the 
                 Met + AGI 
               
               
                   
                 drugs on right: 
                 Met + Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                 SU/glinide + SGLT-2   
                 Increase dose of SU/ 
                 Met + DPP-4 
               
               
                   
                 glinide and/or SGLT-2 
                 Met + GLP-1 
               
               
                   
                 if appropriate; Also, 
                 Met + AGI 
               
               
                   
                 Add one of the drugs 
                 Met + Pre-meal rapid- 
               
               
                   
                 on right: 
                 acting insulin 
               
               
                 SU/glinide + Basal     
                 Increase dose of SU/ 
                 Met + DPP-4 
               
               
                 insulin 
                 glinide, if appropriate;  
                 Met + GLP-1 
               
               
                   
                 Also, Add one of the 
                 Met + SGLT-2 
               
               
                   
                 drugs on right: 
                 Met + AGI 
               
               
                   
                   
                 Met + Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                 TZD + DPP-4 
                 Increase dose of TZD  
                 Met + SGLT-2 
               
               
                   
                 and/or DPP-4, if  
                 Met + AGI 
               
               
                   
                 appropriate Also, 
                 Met + Pre-meal rapid- 
               
               
                   
                 Add one of the drugs 
                 acting insulin 
               
               
                   
                 on right: 
                   
               
               
                 TZD + GLP-1 
                 Increase dose of TZD  
                 Met + SGLT-2 
               
               
                   
                 and/or GLP-1, if  
                 Met + AGI 
               
               
                   
                 appropriate; Also, Add 
                 Met + SU/glinide 
               
               
                   
                 one of the drugs 
                 Met + Pre-meal rapid- 
               
               
                   
                 on right: 
                 acting insulin 
               
               
                  TZD + SGLT-2 
                 Increase dose of TZD  
                 Met + DPP-4 
               
               
                   
                 and/or SGLT-2, if  
                 Met + GLP-1 
               
               
                   
                 appropriate; Also, Add 
                 Met + AGI 
               
               
                   
                 one of the drugs  
                 Met + SU/glinide 
               
               
                   
                 on right: 
                 Met + Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                    TZD + Basal insulin 
                 Increase dose of TZD,  
                 Met + DPP-4 
               
               
                   
                 if appropriate;  
                 Met + GLP-1 
               
               
                   
                 Also, Add one of the 
                 Met + SGLT-2 
               
               
                   
                 drugs on right: 
                 Met + AGI 
               
               
                   
                   
                 Met + SU/glinide 
               
               
                   
                   
                 Met + Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                 DPP-4 + SGLT-2 
                 Increase dose of DPP-4  
                 Met + AGI 
               
               
                   
                 and/or SGLT-2, if  
                 Met + SU/glinide 
               
               
                   
                 appropriate; Also,  
                 Met + Pre-meal rapid- 
               
               
                   
                 Add one of the  
                 acting insulin 
               
               
                   
                 drugs on right: 
                   
               
               
                 GLP-1 + SGLT-2 
                 Increase dose of GLP-1  
                 Met + AGI 
               
               
                   
                 and/or SGLT-2, if  
                 Met + SU/glinide 
               
               
                   
                 appropriate; Also, 
                 Met + Pre-meal rapid- 
               
               
                   
                 Add one of the 
                 acting insulin 
               
               
                   
                 drugs on right: 
                   
               
               
                 Basal insulin + SGLT-2    
                 Increase dose  
                 Met + DPP-4 
               
               
                   
                 of SGLT-2 if 
                 Met + GLP-1 
               
               
                   
                 appropriate; Also,  
                 Met + AGI 
               
               
                   
                 Add one of the 
                 Met + SU/glinide 
               
               
                   
                 drugs on right: 
                 Met + Pre-meal rapid- 
               
               
                   
                   
                 acting insulin 
               
               
                   
               
            
           
         
       
     
     Still referring to  FIG. 13 , after determining the recommended modifications to the patient&#39;s current therapy configuration, the recommendation process  1300  generates or otherwise provides graphical indicia of the recommended therapy changes in graphical association with the identified event pattern (task  1312 ). In one or more embodiments, the server  206  generates recommended therapy modifications when populating the event pattern analysis region associated with the identified event, for example, by displaying recommended therapy modifications for the highest priority event pattern in its associated event pattern analysis region of the pattern guidance display. In another embodiment, the server  206  generates or otherwise provides the recommended therapy modifications in response to selection of a particular event pattern for analysis (e.g., from within the event pattern analysis region). In various embodiments, the graphical indicia of a recommended therapy modification may be realized as a graphical representation or depiction of text stored in the database  208  (e.g., in association with the therapy modification logic rules, in association the therapy configuration for which the recommended therapy modification is an option, or the like). 
       FIG. 14  depicts an exemplary embodiment of a snapshot GUI display  1400  (or report) that may be presented on a display device associated with an electronic device, such as the client device  210 , in connection with the recommendation process  1300  of  FIG. 13 . Similar to the snapshot GUI display  100  of  FIG. 1 , the snapshot GUI display  1400  includes a pattern detection region  1406  including a plurality of pattern guidance displays  1420 ,  1430 ,  1440  corresponding to patterns of events identified during the snapshot time period based on the patient&#39;s sensor glucose measurement values for the snapshot time period. In the illustrated embodiment of  FIG. 14 , the highest prioritized detected event pattern, a variability event associated with the overnight time period, is identified by the recommendation process  1300  for recommending therapy modifications capable of addressing the overnight variability event given the patient&#39;s current therapy. 
     As described above in the context of  FIG. 13 , the server  206  accesses the database  208  using the patient&#39;s identification information to identify the current therapy configuration for the patient (500 milligrams of metformin twice daily and basal insulin in the evening) and obtain the therapy modification logic rules associated with the dual combination therapy of metformin and basal insulin. In exemplary embodiments, the obtained therapy modification logic rules also correspond to the patient&#39;s estimated A1C level for the snapshot time period. For example, there may be one set of variability event therapy modification logic rules for the metformin and basal insulin dual therapy combination associated with A1C levels below a threshold value of 9% and another set of variability event therapy modification logic rules for the metformin and basal insulin dual therapy combination associated with A1C levels above the threshold value of 9%, with the server  206  selecting the therapy modification logic rules associated with A1C levels below the threshold value based on the patient&#39;s estimated A1C level for the snapshot time period of 5.7%. 
     Based on the obtained therapy modification rules and the patient&#39;s current dosages, the server  206  identifies a recommended therapy modification of reducing the basal insulin dosage to address the overnight variability event. In this regard, the server  206  may identify a modification to the dosage or delivery rate of insulin to be delivered by the infusion device  202  during future instances of the monitoring period associated with the highest prioritized detected event pattern (e.g., the basal dosage during the overnight time period). Thereafter, one or more autonomous operating modes supported by the infusion device  202  may be modified, adjusted, or otherwise reconfigured to autonomously regulate the condition of the patient in accordance with the recommended dosage modification in response to a user input. For example, the patient or other user (e.g., the patient&#39;s doctor or another clinician) could then interact with the infusion device  202  (e.g., by manipulating user interface  1040 ) to reprogram or reconfigure one or more parameters, limits, targets, set points, or other settings associated with the control scheme or algorithm implemented by the infusion device  202  to achieve the modified dosage when autonomously regulating the patient&#39;s glucose level during the time of day corresponding to the monitoring period associated with the detected event pattern (e.g., during overnight closed-loop operation). To reduce the evening basal insulin dosage by 10% to 20% as indicated in analysis region  1426 , the overnight basal infusion rate setting of the infusion device  202  may be reduced by the corresponding percentage, or the amount of insulin injected at bedtime may be reduced by the corresponding percentage. 
     In some embodiments, the graphical representation of a modification to the dosage or delivery rate of insulin to be delivered by the infusion device  202  during future instances of the monitoring period may be selectable or associated with a button or similar selectable GUI element that facilitates the client device  210  or the server  206  automatically reprogramming the infusion device  202  (e.g., by transmitting corresponding commands, code or other programming instructions to the infusion device  202  via the network  214 ) for implementing the modified dosage during the relevant time period. Additionally, in the illustrated embodiment, the server  206  utilizes the obtained therapy modification rules to identify another recommended therapeutic remedial action of adding a bedtime snack to increase the patient&#39;s glucose level. In this regard, in some embodiments, a recommended therapeutic remedial action may be identified based on the patient exhibiting sensor glucose measurement values above or below a threshold (e.g., below the lower glucose threshold value for the overnight monitoring time period associated with the highest priority variability event) and/or a duration of time during which those measurements are exhibited within the monitoring period. 
     In a similar manner as described above in the context of  FIGS. 1-4 , the server  206  generates a header region  1422  with graphical indicia of the overnight variability event. In connection with the recommendation process  1300 , the server  206  generates a current therapy summary region  1424  that includes graphical indicia of the patient&#39;s current therapy configuration along with an analysis region  1426  that includes graphical indicia of the recommended remedial actions identified based on therapy modification rules associated with the patient&#39;s current therapy configuration. In some embodiments, the therapy summary and analysis regions  1424 ,  1426  are presented in response to user selection of the overnight variability event pattern guidance display  1420  or the header region  1422  in lieu of other summary and analysis regions (e.g., regions  124 ,  126 ). In this regard, the recommendation process  1300  may be triggered or initiated to generate and populate the therapy summary and analysis regions  1424 ,  1426  presented in response to user selection of the overnight variability event pattern guidance display  1420  or the header region  1422 . In other embodiments, therapy summary and analysis regions  1424 ,  1426  may automatically be presented for the highest priority event pattern in lieu of other summary and analysis regions (e.g., regions  124 ,  126 ) upon initial generation of the snapshot GUI display  1400 . 
     Although not illustrated in  FIG. 14 , in various alternative embodiments, the recommendation process  1300  may be automatically performed with respect to the other displayed event patterns to populate the remaining pattern guidance displays  1430 ,  1440  in addition to pattern guidance display  1420 . Alternatively, the recommendation process  1300  may be performed with respect to one of the other displayed event patterns in response to selection of the respective pattern guidance display  1430 ,  1440 . However, as noted above, remedial actions that may be taken to mitigate or otherwise address lower priority event pattern could be redundant, unnecessary, and/or confusing in view of recommended remedial actions for the highest priority event pattern. 
       FIG. 15  depicts another exemplary embodiment of a snapshot GUI display  1500  that may be presented on or by an electronic device in connection with the recommendation process  1300  of  FIG. 13 . The snapshot GUI display  1500  includes a patient therapy region  1510  that includes graphical indicia of the patient&#39;s current therapy configuration, which could be rendered outside of or alongside of the pattern detection region. In the embodiment of  FIG. 15 , the event pattern analysis region  1526  of the highest priority pattern guidance display  1520  includes graphical indicia of the recommended therapeutic remedial actions  1528  identified by the recommendation process  1300  while the current patient therapy configuration is concurrently presented within the patient therapy region  1510 . In one or more embodiments, the recommended therapeutic remedial actions  1528  are prioritized or ordered first among the information presented within the event pattern analysis region  1526 , for example, by displaying the recommended therapeutic remedial actions  1528  above the potential causes or other information related to the overnight variability event pattern. 
       FIG. 16  depicts another exemplary embodiment of a snapshot GUI display  1600  that may be presented on or by an electronic device in connection with the recommendation process  1300  of  FIG. 13 . The snapshot GUI display  1600  includes a patient therapy region  1610  that includes graphical indicia of the patient&#39;s current therapy configuration which is displayed proximate the pattern detection region  1606 . In the embodiment of  FIG. 16 , the pattern detection region  1606  includes a menu or list of pattern guidance displays  1620 ,  1630 ,  1640  ranked or ordered according to prioritization, with graphical indicia of the recommended therapeutic remedial actions  1628  being presented below the highest priority event pattern guidance display  1620  in graphical association with or proximity to the highest priority event pattern. In this regard, in some embodiments, the pattern guidance displays  1620 ,  1630 ,  1640  may be expandable or collapsible to display recommended therapeutic remedial actions in response to user selection of respective ones of the pattern guidance displays  1620 ,  1630 ,  1640 . In such embodiments, the recommendation process  1300  may be initiated or otherwise performed with respect to a selected event pattern to determine recommended therapeutic remedial actions for populating the expanded pattern guidance display region upon or in response to user selection of the respective event pattern. 
     The snapshot GUI display  1600  also includes a supplemental information region  1650  that may include disclaimer language or other explanatory information or guidance pertaining to the recommended therapeutic remedial actions  1628 , such as, for example, potential side effects associated with proposed medications to be added to the patient&#39;s therapy regimen, or the like. The supplemental information region  1650  may be displayed adjacent to or otherwise in graphical association with the pattern detection region  1606  or the selected pattern guidance display  1620 . Information presented in the supplemental information region  1650  may be stored or maintained in the database  208  and retrieved by the server  206  for presentation. In other embodiments, rules or formula for generating the supplemental information may be stored or maintained in the database  208  and retrieved by the server  206  for dynamically determining the supplemental information to be presented in the region  1650  based on the patient&#39;s current therapy configuration, physiological condition, or other patient-specific variables or factors. 
     It should be noted that  FIGS. 14-16  depict merely some exemplary GUI displays for presenting recommended therapeutic remedial actions, and the subject matter described herein is not necessarily limited to any particular manner of presentation. By virtue of the recommendation process  1300  of  FIG. 13 , detected event patterns exhibited by a particular patient and that patient&#39;s particular therapy configuration, physiological condition, and potentially other patient-specific variables may be synthesized and analyzed to determine comprehensive therapeutic recommendations for remedying, resolving, mitigating, or otherwise addressing a particular event pattern in a manner that accounts for the patient&#39;s current therapy and physiological condition. The recommended therapeutic remedial actions may also account for various patient-specific variables to provide recommendations that reflect a relatively comprehensive review of the patient&#39;s medical records, history and prior therapies. The recommended therapeutic remedial actions are then presented in connection with other graphical indicia pertaining to detected event pattern, thereby clearly conveying to the patient or other user the nature of the event pattern and potential ways to address the event pattern, which, in turn, leads to better patient outcomes. 
     It should be noted that although the subject matter may be described herein primarily in the context of a patient with Type 2 diabetes taking any one of a wide variety of medications (orals, non-insulin injectables, and insulin) in connection with an infusion device or continuous glucose monitoring, the subject matter described herein is not necessarily limited to use with infusion devices, continuous glucose monitoring, Type 2 diabetes, or the medications described herein. Moreover, in exemplary embodiments, the recommendation processes described herein support modularity or adaptability to accommodate potential new classes of medications and/or new indications for existing classes of medications. For example, the therapeutic modification logic rules may have a modular design that allows for a new module of logic rules pertaining to a new class of medication to be inserted or otherwise configured among logic rules pertaining to existing classes of medications, thereby allowing the therapeutic modification logic rules to be readily updated to accommodate new classes of medication. Similarly, indications for existing classes of medications may be modular, allowing for changes with respect to the indications for those classes or medications that do not impact other classes or medications or the overall hierarchy or flow associated with the therapeutic modification logic rules. Such modularity of the therapeutic modification logic rules facilitates inclusion and prioritization of new classes of medication and/or new indications for existing classes without substantial redesign of the recommendation algorithms or hardware. 
     For the sake of brevity, conventional techniques related to glucose sensing and/or monitoring, bolusing, meal boluses or correction boluses, and other functional aspects of the subject matter may not be described in detail herein. In addition, certain terminology may also be used in the herein for the purpose of reference only, and thus is not intended to be limiting. For example, terms such as “first”, “second”, and other such numerical terms referring to structures do not imply a sequence or order unless clearly indicated by the context. The foregoing description may also refer to elements or nodes or features being “connected” or “coupled” together. As used herein, unless expressly stated otherwise, “coupled” means that one element/node/feature is directly or indirectly joined to (or directly or indirectly communicates with) another element/node/feature, and not necessarily mechanically. 
     While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or embodiments described herein are not intended to limit the scope, applicability, or configuration of the claimed subject matter in any way. For example, the subject matter described herein is not necessarily limited to the infusion devices and related systems described herein. Moreover, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the described embodiment or embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope defined by the claims, which includes known equivalents and foreseeable equivalents at the time of filing this patent application. Accordingly, details of the exemplary embodiments or other limitations described above should not be read into the claims absent a clear intention to the contrary.