WO2025165721A1 - Systems and methods for diabetes management - Google Patents

Abstract

Systems, devices and methods are provided for incorporating a medication delivery device into a diabetes management system. The diabetes management system may consider and include a subject's adherence to dosing schedules in their treatment. The system may generate reports that correlate the user's adherence to dosing schedules with various glucose metrics. The system may also provide interactive GUIs configured to receive input regarding dosing adherence. The system may also optionally determine dosing adherence based on data from connected delivery devices.

Description

Docket No. A0130.0324.WO 15021WOO1 SYSTEMS AND METHODS FOR DIABETES MANAGEMENT CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claim priority to U.S. Application Serial No.63/626,655, filed January 30, 2024, which is expressly incorporated herein by reference in its entirety for all purposes. This application is also related to WO 2022/031792, which is expressly incorporated herein by reference in its entirety for all purposes. FIELD [0002] The subject matter described herein relates generally to systems, devices, and methods relating to integrated systems for diabetes management such as, for example, an integrated platform that connects insulin pens with a common viewing platform such that data can be shared among many parties. BACKGROUND [0003] The detection and/or monitoring of analyte levels, such as glucose, ketones, lactate, oxygen, hemoglobin A1C, or the like, can be vitally important to the health of an individual having diabetes. Patients suffering from diabetes mellitus can experience complications including loss of consciousness, cardiovascular disease, retinopathy, neuropathy, and nephropathy. Diabetics are generally required to monitor their glucose levels to ensure that they are being maintained within a clinically safe range, and may also use this information to determine if and/or when insulin is needed to reduce glucose levels in their bodies or when additional glucose is needed to raise the level of glucose in their bodies. [0004] Growing clinical data demonstrates a strong correlation between the frequency of glucose monitoring and glycemic control. Despite such correlation, many individuals diagnosed with a diabetic condition do not monitor their glucose levels as frequently as they should due to a combination of factors including inconvenience, testing discretion, pain associated with glucose testing, and cost. [0005] For patients that rely on the administration of medications (e.g., insulin) to treat or manage diabetes, it is desirable to have systems, devices, or methods that can integrate glucose data with insulin dosing data and provide more actionable insights to both patients, caregivers, and HCPs. Manual logging of insulin doses is not only a huge time commitment but often Docket No. A0130.0324.WO 15021WOO1 results in inaccurate dosing logs. Moreover, sharing these manual logs with the HCP is a big hassle for patients and fraught with workflow issues. [0006] Therapeutic management of diabetes often requires the use of multiple drugs that have different delivery frequencies (i.e., daily, weekly) as well as routes of administration (oral or injection). The combination of drug types, delivery frequencies and routes of administration can be difficult to manage, creating significant cognitive burden for a user that often translates to poor dose regimen concordance. Studies have shown that amongst insulin-dependent people with Type 1 diabetes, up to 24% of mealtime rapid acting insulin boluses and 36% of long acting once daily basal doses are missed, leading to poor glucose control and diabetes management. Existing dose logbooks are only as useful as a user wants to make them. Their efficacy is directly correlated to a user’s willingness to log doses and reference past loggings. The dawn of connected dosing technology, such as BLUETOOTH®-enabled insulin pens, has enabled doses to be logged automatically into companion mobile phone applications as they are delivered with no user action required. While useful in day-to-day management, this method suffers from two notable shortcomings: (1) it is not able to correlate directly with glycemic outcomes; and (2) insulin doses are often presented in tabular form that is difficult to read and interpret over a large time window. [0007] Lack of medication adherence can have significant impact on glucose control. There are no methods, however, to track dose adherence in widespread use for patients using oral diabetes medication, GPI injectable, basal therapy or MDI prandial insulin, though connected insulin pen use is becoming more common. There has been a lack of reporting tools that associate glucose data with medication adherence data, or more specifically, associating changes in glucose data associated with changes in medication adherence. [0008] For these and other reasons, needs exist for improved systems, methods, and devices relating to systems for diabetes management and reporting systems. SUMMARY [0009] Provided herein are example embodiments of systems, devices and methods relating to management of diabetes, including integrated managements systems that include an analyte monitoring device, a medication delivery device, a reader device, monitoring software, and reporting software. In many embodiments, the analyte monitoring device (e.g., a continuous or Docket No. A0130.0324.WO 15021WOO1 flash glucose monitor) and the medication delivery device (e.g., an insulin pen) are communicatively coupled with the reader device to enable an easy transfer of analyte data, dose logs, and other information to computing devices that include monitoring and/or reporting software. The integrated system can include GUI displays that instruct and assist the user in connecting a medication delivery device to the monitoring software on, e.g., the reader device, such that dosing logs and other information can be transferred from the medication delivery device. The integrated system also includes reporting software that can produce a plurality of reports that incorporate data regarding analyte levels and metrics and medication dosing amounts and metrics. Systems, devices and methods are provided for incorporating a medication delivery device into a diabetes management system. The diabetes management system may consider and include a subject’s adherence to dosing schedules in their treatment. The system may generate reports that correlate the user’s adherence to dosing schedules with various glucose metrics. The system may also provide interactive GUIs configured to receive input regarding dosing adherence. The system may also optionally determine dosing adherence based on data from connected delivery devices. [0010] Other systems, devices, methods, features and advantages of the subject matter described herein will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, devices, methods, features and advantages be included within this description, be within the scope of the subject matter described herein, and be protected by the accompanying claims. In no way should the features of the example embodiments be construed as limiting the appended claims, absent express recitation of those features in the claims. BRIEF DESCRIPTION OF THE FIGURES [0011] The details of the subject matter set forth herein, both as to its structure and operation, may be apparent by study of the accompanying figures, in which like reference numerals refer to like parts. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the subject matter. Moreover, all illustrations are intended to convey concepts, where relative sizes, shapes and other detailed attributes may be illustrated schematically rather than literally or precisely. [0012] FIGS.1A and 1B are block diagrams of example embodiments of a integrated management system. Docket No. A0130.0324.WO 15021WOO1 [0013] FIG.2A is a schematic diagram depicting an example embodiment of a sensor control device. [0014] FIG.2B is a block diagram depicting an example embodiment of a sensor control device. [0015] FIG.3A is a schematic diagram depicting an example embodiment of a medication delivery device. [0016] FIG.3B is a block diagram depicting an example embodiment of a medication delivery device. [0017] FIG.3C is a schematic diagram depicting an example embodiment of a medication delivery device with a smart button. [0018] FIG.4A is a schematic diagram depicting an example embodiment of a display device. [0019] FIG.4B is a block diagram depicting an example embodiment of a display device. [0020] FIG.5 is a block diagram depicting an example embodiment of a user interface device. [0021] FIG.6 is an exemplary flow diagram of a method for inputting dosing adherence information. [0022] FIG.7 is an example embodiment of a GUI for inputting medication adherence. [0023] FIGS.8A-8G are example embodiments of GUIs for inputting reconciling medication dosing. [0024] FIGS.9A-9C are example embodiments of an assessment report. [0025] FIG.10 is an example embodiment of an intervention report. DETAILED DESCRIPTION [0026] Before the present subject matter is described in detail, it is to be understood that this disclosure is not limited to the particular embodiments described herein, as such may, of course, vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting, since the scope of the present disclosure will be limited only by the appended claims. [0027] Generally, embodiments of the present disclosure include systems, devices, and methods related to integrated diabetes management. The integrated diabetes management system can include smart delivery systems, such as connected, smart insulin pens, glucose sensors, Docket No. A0130.0324.WO 15021WOO1 software to receive and process data from the glucose sensors and smart delivery systems, and a viewing platform capable of determining and visualizing dose analytics. The integrated management system (IMS) can further include reports that include insights as to the effects of various inulin doses and treatment advice, including dosing recommendations. [0028] The integrated diabetes management can be implemented as software and/or firmware instructions stored in a memory of a computing device for execution by at least one processor or processing circuitry thereof. The computing device can be in the possession of a user or healthcare professional (HCP), and the user or HCP can interface with the computing device through a user interface. According to some embodiments, the computing device can be a server or trusted computer system that is accessible through a network, and the integrated management software can be presented to the user in the form of an interactive web page by way of a browser executed on a local display device (having the user interface) in communication with the server or trusted computer system through the network. In this and other embodiments, the integrated management software can be executed across multiple devices, or executed, in part, on processing circuitry of a local display device and, in part, on processing circuitry of a server or trusted computer system. It will be understood by those of skill in the art that when the IMS is described as performing an action, such action is performed according to instructions stored in a computer memory (including instructions hardcoded in read only memory) that, when executed by at least one processor of at least one computing device, causes the IMS to perform the described action. In all cases the action can alternatively be performed by hardware that is hardwired to implement the action (e.g., dedicated circuitry) as opposed to performance by way of instructions stored in memory. [0029] Furthermore, as used herein, a system on which the IMS is implemented can be referred to as an integrated management system. The integrated management system can be configured for the sole purpose of providing integrated management or can be a multifunctional system of which integrated management is only one aspect. For example, in some embodiments the integrated management system can also be capable of monitoring analyte levels of a user. In some embodiments the integrated management system can also be capable of delivering medication to the user, such as with an injection or infusion device. In some embodiments, the integrated management system is capable of both monitoring analytes and delivering medication. Docket No. A0130.0324.WO 15021WOO1 [0030] These embodiments and others described herein represent improvements in the field of computer-based dose determination, analyte monitoring, and medication delivery systems. The specific features and potential advantages of the disclosed embodiments are further discussed below. [0031] Before describing the integrated management embodiments in detail, it is first desirable to describe examples of integrated management systems on or through which the integrated management application can be implemented. Example Embodiments of Integrated Systems [0032] FIG.1A is a block diagram depicting an example embodiment of integrated system 100. In this embodiment, integrated management system 100 is capable of delivering one or more medications, logging medication doses, monitoring one or more analytes, and determining and viewing analytics, and providing treatment advice. This multifunctional example is used to illustrate the high degree of interconnectivity and performance obtainable by system 100. [0033] Here, system 100 includes a sensor control device (SCD) 102 configured to collect analyte level information from a user, a medication delivery device (MDD) 152 configured to deliver medication to the user, and a display device 120 configured to present information to the user and receive input or information from the user. The structure and function of each device will be described in detail herein. [0034] System 100 is configured for highly interconnected and highly flexible communication between devices. Each of the three devices 102, 120, and 152, can communicate directly with each other (without passing through an intermediate electronic device) or indirectly with each other (such as through cloud network 190, or through another device and then through network 190). Bidirectional communication capability between devices, as well as between devices and network 190, is shown in FIG.1A with a double-sided arrow. However, those of skill in the art will appreciate that any of the one or more devices (e.g., SCD) can be capable of unidirectional communication such as, for example, broadcasting, multicasting, or advertising communications. In each instance, whether bidirectional or unidirectional, the communication can be wired or wireless. The protocols that govern communication over each path can be the same or different, and can be either proprietary or standardized. For example, wireless communication between devices 102, 120, and 152 can be performed according to a BLUETOOTH® (including BLUETOOTH® Low Energy) standard, a Near Field Docket No. A0130.0324.WO 15021WOO1 Communication (NFC) standard, a Wi-Fi (802.11x) standard, a mobile telephony standard, or others. All communications over the various paths can be encrypted, and each device of FIG.1A can be configured to encrypt and decrypt those communications sent and received. In each instance the communication pathways of FIG.1A can be direct (e.g., BLUETOOTH® or NFC) or indirect (e.g., Wi-Fi, mobile telephony, or other internet protocol). Embodiments of system 100 do not need to have the capability to communicate across all of the pathways indicated in FIG.1A. [0035] In addition, although FIG.1A depicts a single display device 120, a single SCD 102, and a single MDD 152, those of skill in the art will appreciate that system 100 can comprise a plurality of any of the aforementioned devices. By way of example only, system 100 can comprise a single SCD 102 in communication with multiple (e.g., two, three, four, etc.) display devices 120 and/or multiple MDDs 152. Alternatively, system 100 can comprise a plurality of SCDs 102 in communication with a single display device 120 and/or a single MDD 152. Furthermore, each of the plurality of devices can be of the same or different device types. For example, system 100 can comprise multiple display devices 120, including a smart phone, a handheld receiver, and/or a smart watch, each of which can be in communication with SCD 102 and/or MDD 152, as well in communication with each other. [0036] Analyte data can be transferred between each device within system 100 in an autonomous fashion (e.g., transmitting automatically according to a schedule), or in response to a request for analyte data (e.g., sending a request from a first device to a second device for analyte data, followed by transmission of the analyte data from the second device to the first device). Other techniques for communicating data can also be employed to accommodate more complex systems like cloud network 190. [0037] FIG.1B is a block diagram depicting another example embodiment of integrated management system 100. Here, system 100 includes SCD 102, MDD 152, a first display device 120-1, a second display device 120-2, local computer system 170, and trusted computer system 180 that is accessible by cloud network 190. SCD 102 and MDD 152 are capable of communication with each other and with display device 120-1, which can act as a communication hub for aggregating information from SCD 102 and MDD 152, processing and displaying that information where desired, and transferring some or all of the information to cloud network 190 and/or computer system 170. Conversely, display device 120-1 can receive Docket No. A0130.0324.WO 15021WOO1 information from cloud network 190 and/or computer system 170 and communicate some or all of the received information to SCD 102, MDD 152, or both. Computer system 170 may be a personal computer, a server terminal, a laptop computer, a tablet, or other suitable data processing device. Computer system 170 can include or present software for data management and analysis and communication with the components in system 100. Computer system 170 can be used by the user or a medical professional to display and/or analyze analyte data measured by SCD 102. Furthermore, although FIG.1B depicts a single SCD 102, a single MDD 152, and two display devices 120-1 and 120-2, those of skill in the art will appreciate that system 100 can include a plurality of any of the aforementioned devices, wherein each plurality of devices can comprise the same or different types of devices. [0038] Referring still to FIG.1B, according to some embodiments, trusted computer system 180 can be within the possession of a manufacturer or distributor of a component of system 100, either physically or virtually through a secured connection, and can be used to perform authentication of the devices of system 100 (e.g., devices 102, 120-n, 152), for secure storage of the user’s data, and/or as a server that serves a data analytics program (e.g., accessible via a web browser) for performing analysis on the user’s measured analyte data and medication history. Trusted computer system 180 can also act as a data hub for routing and exchanging data between all devices in communication with system 180 through cloud network 190. In other words, all devices of system 100 that are capable of communicating with cloud network 190 (e.g., either directly with an internet connection or indirectly via another device), are also capable of communicating with all of the other devices of system 100 that are capable of communicating with cloud network 190, either directly or indirectly. [0039] Display device 120-2 is depicted in communication with cloud network 190. In this example, device 120-2 can be in the possession of another user that is granted access to the analyte and medication data of the person wearing SCD 102. For example, the person in possession of display device 120-2 can be a parent of a child wearing SCD 102, as one example, or a caregiver of an elderly patient wearing SCD 102, as another example. System 100 can be configured to communicate analyte and medication data about the wearer through cloud network 190 (e.g., via trusted computer system 180) to another user with granted access to the data. Docket No. A0130.0324.WO 15021WOO1 Example Embodiments of Analyte Monitoring Devices [0040] The analyte monitoring functionality of integrated management system 100 can be realized through inclusion of one or more devices capable of collecting, processing, and displaying analyte data of the user. Example embodiments of such devices and their methods of use are described in Int’l Publ. No. WO 2018/152241 and U.S. Patent Publ. No.2011/0213225, both of which are incorporated by reference herein in their entireties for all purposes. [0041] Analyte monitoring can be performed in numerous different ways. “Continuous Analyte Monitoring” devices (e.g., “Continuous Glucose Monitoring” devices), for example, can transmit data from a sensor control device to a display device continuously or repeatedly with or without prompting, e.g., automatically according to a schedule. “Flash Analyte Monitoring” devices (e.g., “Flash Glucose Monitoring” devices or simply “Flash” devices), as another example, can transfer data from a sensor control device in response to a user-initiated request for data by a display device (e.g., a scan), such as with a Near Field Communication (NFC) or Radio Frequency Identification (RFID) protocol. [0042] Analyte monitoring devices that utilize a sensor configured to be placed partially or wholly within a user’s body can be referred to as in vivo analyte monitoring devices. For example, an in vivo sensor can be placed in the user’s body such that at least a portion of the sensor is in contact with a bodily fluid (e.g., interstitial (ISF) fluid such as dermal fluid in the dermal layer or subcutaneous fluid beneath the dermal layer, blood, or others) and can measure an analyte concentration in that bodily fluid. In vivo sensors can use various types of sensing techniques (e.g., chemical, electrochemical, or optical). Some systems utilizing in vivo analyte sensors can also operate without the need for finger stick calibration. [0043] “In vitro” devices are those where a sensor is brought into contact with a biological sample outside of the body (or rather “ex vivo”). These devices typically include a port for receiving an analyte test strip carrying bodily fluid of the user, which can be analyzed to determine the user’s blood glucose level. Other ex vivo devices have been proposed that attempt to measure the user’s internal analyte level non-invasively, such as by using an optical technique that can measure an internal body analyte level without mechanically penetrating the user’s body or skin. In vivo and ex vivo devices often include in vitro capability (e.g., an in vivo display device that also includes a test strip port). Docket No. A0130.0324.WO 15021WOO1 [0044] The present subject matter will be described with respect to sensors capable of measuring a glucose concentration, although detection and measurement of concentrations of other analytes are within the scope of the present disclosure. These other analytes can include, for example, ketones, lactate, oxygen, hemoglobin A1C, acetyl choline, amylase, bilirubin, cholesterol, chorionic gonadotropin, creatine kinase (e.g., CK-MB), creatine, DNA, fructosamine, glutamine, growth hormones, hormones, peroxide, prostate-specific antigen, prothrombin, RNA, thyroid stimulating hormone, troponin and others. The concentration of drugs, such as, for example, antibiotics (e.g., gentamicin, vancomycin, and the like), digitoxin, digoxin, drugs of abuse, theophylline, and warfarin, may also be monitored. The sensor can be configured to measure two or more different analytes at the same or different times. In some embodiments, the sensor control device can be coupled with two or more sensors, where one sensor is configured to measure a first analyte (e.g., glucose) and the other one or more sensors are configured to measure one or more different analytes (e.g., any of those described herein). In other embodiments, a user can wear two or more sensor control devices, each of which is capable of measuring a different analyte. [0045] The embodiments described herein can be used with all types of in vivo, in vitro, and ex vivo devices capable of monitoring the aforementioned analytes and others. [0046] In many embodiments, the sensor operation can be controlled by SCD 102. The sensor can be mechanically and communicatively coupled with SCD 102, or can be just communicatively coupled with SCD 102 using a wireless communication technique. SCD 102 can include the electronics and power supply that enable and control analyte sensing performed by the sensor. In some embodiments the sensor or SCD 102 can be self-powered such that a battery is not required. SCD 102 can also include communication circuitry for communicating with another device that may or may not be local to the user’s body (e.g., a display device). SCD 102 can reside on the body of the user (e.g., attached to or otherwise placed on the user’s skin, or carried in the user’s clothes, etc.). SCD 102 can also be implanted within the body of the user along with the sensor. Functionality of SCD 102 can be divided between a first component implanted within the body (e.g., a component that controls the sensor) and a second component that resides on or otherwise outside the body (e.g., a relay component that communicates with the first component and also with an external device like a computer or smartphone). In other embodiments, SCD 102 can be external to the body and configured to non-invasively measure Docket No. A0130.0324.WO 15021WOO1 the user’s analyte levels. The sensor control device, depending on the actual implementation or embodiment, can also be referred to as a “sensor control unit,” an “on-body electronics” device or unit, an “on-body” device or unit, an “in body electronics” device or unit, an “in-body” device or unit, or a “sensor data communication” device or unit, to name a few. [0047] In some embodiments, SCD 102 may include a user interface (e.g., a touchscreen) and be capable of processing the analyte data and displaying the resultant calculated analyte levels to the user. In such cases, the integrated management embodiments described herein can be implemented directly by SCD 102, in whole or in part. In many embodiments, the physical form factor of SCD 102 is minimized (e.g., to minimize the appearance on the user’s body) or the sensor control device may be inaccessible to the user (e.g., if wholly implanted), or other factors may make it desirable to have a display device usable by the user to read analyte levels and interface with the sensor control device. [0048] FIG.2A is a side view of an example embodiment of SCD 102. SCD 102 can include a housing or mount 103 for sensor electronics (FIG.2B), which can be electrically coupled with an analyte sensor 101, which is configured here as an electrochemical sensor. According to some embodiments, sensor 101 can be configured to reside partially within a user’s body (e.g., through an exterior-most surface of the skin) where it can make fluid contact with a user’s bodily fluid and be used, along with the sensor electronics, to measure analyte-related data of the user. A structure for attachment 105, such as an adhesive patch, can be used to secure housing 103 to a user’s skin. Sensor 101 can extend through attachment structure 105 and project away from housing 103. Those of skill in the art will appreciate that other forms of attachment to the body and/or housing 103 may be used, in addition to or instead of adhesive, and are fully within the scope of the present disclosure. [0049] SCD 102 can be applied to the body in any desired manner. For example, an insertion device (not shown), sometimes referred to as an applicator, can be used to position all or a portion of analyte sensor 101 through an external surface of the user’s skin and into contact with the user’s bodily fluid. In doing so, the insertion device can also position SCD 102 onto the skin. In other embodiments, the insertion device can position sensor 101 first, and then accompanying electronics (e.g., wireless transmission circuitry and/or data processing circuitry, and the like) can be coupled with sensor 101 afterwards (e.g., inserted into a mount), either manually or with the aid of a mechanical device. Examples of insertion devices are described in Docket No. A0130.0324.WO 15021WOO1 U.S. Patent Publication Nos.2008/0009692, 2011/0319729, 2015/0018639, 2015/0025345, 2015/0173661, and 2018/0235520, all of which are incorporated by reference herein in their entireties for all purposes. [0050] FIG.2B is a block diagram depicting an example embodiment of SCD 102 having analyte sensor 101 and sensor electronics 104. Sensor electronics 104 can be implemented in one or more semiconductor chips (e.g., an application specific integrated circuit (ASIC), processor or controller, memory, programmable gate array, and others). In the embodiment of FIG.1B, sensor electronics 104 includes high-level functional units, including an analog front end (AFE) 110 configured to interface in an analog manner with sensor 101 and convert analog signals to and/or from digital form (e.g., with an A/D converter), a power supply 111 configured to supply power to the components of SCD 102, processing circuitry 112, memory 114, timing circuitry 115 (e.g., such as an oscillator and phase locked loop for providing a clock or other timing to components of SCD 102), and communication circuitry 116 configured to communicate in wired and/or wireless fashion with one or more devices external to SCD 102, such as display device 120 and/or MDD 152. [0051] SCD 102 can be implemented in a highly interconnected fashion, where power supply 111 is coupled with each component shown in FIG.2B and where those components that communicate or receive data, information, or commands (e.g., AFE 110, processing circuitry 112, memory 114, timing circuitry 115, and communication circuitry 116), can be communicatively coupled with every other such component over, for example, one or more communication connections or buses 118. [0052] Processing circuitry 112 can include one or more processors, microprocessors, controllers, and/or microcontrollers, each of which can be a discrete chip or distributed amongst (and a portion of) a number of different chips. Processing circuitry 112 can include on-board memory. Processing circuitry 112 can interface with communication circuitry 116 and perform analog-to-digital conversions, encoding and decoding, digital signal processing and other functions that facilitate the conversion of data signals into a format (e.g., in-phase and quadrature) suitable for wireless or wired transmission. Processing circuitry 112 can also interface with communication circuitry 116 to perform the reverse functions necessary to receive a wireless transmission and convert it into digital data or information. Docket No. A0130.0324.WO 15021WOO1 [0053] Processing circuitry 112 can execute instructions stored in memory 114. These instructions can cause processing circuitry 112 to process raw analyte data (or pre-processed analyte data) and arrive at a final calculated analyte level. In some embodiments, instructions stored in memory 114, when executed, can cause processing circuitry 112 to process raw analyte data to determine one or more of: a calculated analyte level, an average calculated analyte level within a predetermined time window, a calculated rate-of-change of an analyte level within a predetermined time window, and/or whether a calculated analyte metric exceeds a predetermined threshold condition. These instructions can also cause processing circuitry 112 to read and act on received transmissions, to adjust the timing of timing circuitry 115, to process data or information received from other devices (e.g., calibration information, encryption or authentication information received from display device 120, and others), to perform tasks to establish and maintain communication with display device 120, to interpret voice commands from a user, to cause communication circuitry 116 to transmit, and others. In embodiments where SCD 102 includes a user interface, then the instructions can cause processing circuitry 112 to control the user interface, read user input from the user interface, cause the display of information on the user interface, format data for display, and others. The functions described here that are coded in the instructions can instead be implemented by SCD 102 with the use of a hardware or firmware design that does not rely on the execution of stored software instructions to accomplish the functions. [0054] Memory 114 can be shared by one or more of the various functional units present within SCD 102, or can be distributed amongst two or more of them (e.g., as separate memories present within different chips). Memory 114 can also be a separate chip of its own. Memory 114 is non-transitory, and can be volatile (e.g., RAM, etc.) and/or non-volatile memory (e.g., ROM, flash memory, F-RAM, etc.). [0055] Communication circuitry 116 can be implemented as one or more components (e.g., transmitter, receiver, transceiver, passive circuit, encoder, decoder, and/or other communication circuitry) that perform the functions for communications over the respective communications paths or links. Communication circuitry 116 can include or be coupled to one or more antenna for wireless communication. [0056] Power supply 111 can include one or more batteries, which can be rechargeable or single-use disposable batteries. Power management circuitry can also be included to regulate Docket No. A0130.0324.WO 15021WOO1 battery charging and monitor usage of power supply 111, boost power, perform DC conversions, and the like. [0057] Additionally, an on-skin or sensor temperature reading or measurement can be collected by an optional temperature sensor (not shown). Those readings or measurements can be communicated (either individually or as an aggregated measurement over time) from SCD 102 to another device (e.g., display device 120). The temperature reading or measurement, however, can be used in conjunction with a software routine executed by SCD 102 or display device 120 to correct or compensate the analyte measurement output to the user, instead of or in addition to, actually outputting the temperature measurement to the user. Example Embodiments of Medication Delivery Devices [0058] The medication delivery functionality of integrated management system 100 can be realized through inclusion of one or more medication delivery devices (MDDs) 152. MDD 152 can be any device configured to deliver a specific dose of medication. The MDD 152 can also include devices that transmit data regarding doses to the IMS, e.g., pen caps, even though the device itself may not deliver the medication. The MDD 152 can be configured as a portable injection device (PID) that can deliver a single dose per one injection, such as a bolus. The PID can be a basic manually-operated syringe, where the medication is either preloaded in the syringe or must be drawn into the syringe from a container prior to injection. In most embodiments, however, the PID includes electronics for interfacing with the user and performing the delivery of the medication. PIDs are often referred to as medication pens, although a pen-like appearance is not required. PIDs having user interface electronics are often referred to as smart pens. PIDs can be used to deliver one dose and then disposed of, or can be durable and used repeatedly to deliver many doses over the course of a day, week, or month. PIDs are often relied upon by users that practice a multiple daily injection (MDI) therapy regimen. [0059] The MDD can also comprise a pump and infusion set. The infusion set includes a tubular cannula that resides at least partially within the recipient’s body. The tubular cannula is in fluid communication with a pump, which can deliver medication through the cannula and into the recipient’s body in small increments repeatedly over time. The infusion set can be applied to the recipient’s body using an infusion set applicator, and the infusion set often stays implanted for 2 to 3 days or longer. A pump device includes electronics for interfacing with the user and Docket No. A0130.0324.WO 15021WOO1 for controlling the slow infusion of the medication. Both a PID and a pump can store the medication in a medication reservoir. [0060] MDD 152 can function as part of a closed-loop system (e.g., an artificial pancreas system requiring no user intervention to operate), semi-closed loop system (e.g., an insulin loop system requiring seldom user intervention to operate, such as to confirm changes in dose), or an open loop system. For example, the diabetic’s analyte level can be monitored in a repeated automatic fashion by SCD 102, and that information can be transmitted to the application and incorporated in various analytics and reports. [0061] In many embodiments, the integrated management system may include data for different types of insulin (e.g., rapid-acting (RA), short-acting insulin, intermediate-acting insulin (e.g., NPH insulin), long-acting (LA), ultra long-acting insulin, and mixed insulin), and will be the same medication delivered by MDD 152. The type of insulin includes human insulin and synthetic insulin analogs. The insulin can also include premixed formulations. However, the integrated management embodiments set forth herein and the medication delivery capabilities of MDD 152 can be applied to other non-insulin medications. Such medications can include, but are not limited to exenatide, exenatide extended release, liraglutide, lixisenatide, semaglutide, pramlintide, metformin, SLGT1-i inhibitors, SLGT2-i inhibitors, and DPP4 inhibitors. The integrated management embodiments can also include combination therapies. Combination therapies can include, but are not limited to, insulin and glucagon-like peptide-1 receptor agonists (GLP-1 RA), insulin and pramlintide. [0062] For ease of description of the integrated management embodiments herein, MDD 152 will often be described in the form of a PID, specifically a smart pen. However, those of skill in the art will readily understand that MDD 152 can alternatively be configured as a pen cap, a pump, or any other type of medication delivery device. [0063] In some embodiments, the IMS may include a connected pen cap. After the connected pen cap is attached to an insulin pen and is paired with the display device, every time a dose of insulin is delivered, the connected pen cap may automatically transmit dose data to the display device via e.g., BLUETOOTH®. [0064] FIG.3A is schematic diagram depicting an example embodiment of an MDD 152 configured as a PID, specifically a smart pen. MDD 152 can include a housing 154 for electronics, an injection motor, and a medication reservoir (see FIG.3B), from which medication Docket No. A0130.0324.WO 15021WOO1 can be delivered through needle 156. Housing 154 can include a removable or detachable cap or cover 157 that, when attached, can shield needle 156 when not in use, and then be detached for injection. MDD 152 can also include a user interface 158 which can be implemented as a single component (e.g., a touchscreen for outputting information to the user and receiving input from the user) or as multiple components (e.g., a touchscreen or display in combination with one or more buttons, switches, or the like). MDD 152 can also include an actuator 159 that can be moved, depressed, touched or otherwise activated to initiate delivery of the medication from an internal reservoir through needle 156 and into the recipient’s body. According to some embodiments, cap 157 and actuator 159 can also include one or more safety mechanisms to prevent removal and/or actuation to mitigate risk of a harmful medication injection. Details of these safety mechanisms and others are described in U.S. Patent Publ. No.2019/0343385 (the ’385 publication), which is hereby incorporated in its entirety for all purposes. FIG.3C is a schematic diagram of an MDD 152 and a smart button configured to fit over the actuator of the delivery pen. The MDD 152, which may be a single use medication delivery pen, may include a display 158 and a dosing selector such as a rotatable dial to select the dose. A smart button 2190 may fit over the dosing selector and actuator 159 and snap together with the pen 2180. After smart button 2190 is paired with a reader device, the smart button 2190 may track the dose, store the dosing data, and transmit it to the reader device. Medication may be delivered by pushing straight down on the smart button 2190 to inject the dose. The smart button 2190 may also contain a display that can display the recommended dose and/or the dose administered. [0065] FIG.3B is a block diagram depicting an example embodiment of MDD 152 having electronics 160, coupled with a power supply 161 and an electric injection motor 162, which in turn is coupled with power supply 161 and a medication reservoir 163. Needle 156 is shown in fluid communication with reservoir 163, and a valve (not shown) may be present between reservoir 163 and needle 156. Reservoir 163 can be permanent or can be removable and replaced with another reservoir containing the same or different medication. Electronics 160 can be implemented in one or more semiconductor chips (e.g., an application specific integrated circuit (ASIC), processor or controller, memory, programmable gate array, and others). In the embodiment of FIG.3B, electronics 160 can include high-level functional units, including processing circuitry 164, memory 165, communication circuitry 166 configured to communicate Docket No. A0130.0324.WO 15021WOO1 in wired and/or wireless fashion with one or more devices external to MDD 152 (such as display device 120), and user interface electronics 168. [0066] MDD 152 can be implemented in a highly interconnected fashion, where power supply 161 is coupled with each component shown in FIG.3B and where those components that communicate or receive data, information, or commands (e.g., processing circuitry 164, memory 165, and communication circuitry 166), can be communicatively coupled with every other such component over, for example, one or more communication connections or buses 169. [0067] Processing circuitry 164 can include one or more processors, microprocessors, controllers, and/or microcontrollers, each of which can be a discrete chip or distributed amongst (and a portion of) a number of different chips. Processing circuitry 164 can include on-board memory. Processing circuitry 164 can interface with communication circuitry 166 and perform analog-to-digital conversions, encoding and decoding, digital signal processing and other functions that facilitate the conversion of data signals into a format (e.g., in-phase and quadrature) suitable for wireless or wired transmission. Processing circuitry 164 can also interface with communication circuitry 166 to perform the reverse functions necessary to receive a wireless transmission and convert it into digital data or information. [0068] Processing circuitry 164 can execute software instructions stored in memory 165. These instructions can cause processing circuitry 164 to receive a selection or provision of a specified dose from a user (e.g., entered via user interface 158 or received from another device), process a command to deliver a specified dose (such as a signal from actuator 159), and control motor 162 to cause delivery of the specified dose. These instructions can also cause processing circuitry 164 to read and act on received transmissions, to process data or information received from other devices (e.g., calibration information, encryption or authentication information received from display device 120, and others), to perform tasks to establish and maintain communication with display device 120, to interpret voice commands from a user, to cause communication circuitry 166 to transmit, and others. In embodiments where MDD 152 includes user interface 158, then the instructions can cause processing circuitry 164 to control the user interface, read user input from the user interface (e.g., entry of a medication dose for administration or entry of confirmation of a recommended medication dose), cause the display of information on the user interface, format data for display, and others. The functions described here that are coded in the instructions can instead be implemented by MDD 152 with the use of a Docket No. A0130.0324.WO 15021WOO1 hardware or firmware design that does not rely on the execution of stored software instructions to accomplish the functions. [0069] Memory 165 can be shared by one or more of the various functional units present within MDD 152, or can be distributed amongst two or more of them (e.g., as separate memories present within different chips). Memory 165 can also be a separate chip of its own. Memory 165 is non-transitory, and can be volatile (e.g., RAM, etc.) and/or non-volatile memory (e.g., ROM, flash memory, F-RAM, etc.). [0070] Communication circuitry 166 can be implemented as one or more components (e.g., transmitter, receiver, transceiver, passive circuit, encoder, decoder, and/or other communication circuitry) that perform the functions for communications over the respective communications paths or links. Communication circuitry 166 can include or be coupled to one or more antenna for wireless communication. Details of exemplary antenna can be found in the ’385 publication, which is hereby incorporated in its entirety for all purposes. [0071] Power supply 161 can include one or more batteries, which can be rechargeable or single-use disposable batteries. Power management circuitry can also be included to regulate battery charging and monitor usage of power supply 161, boost power, perform DC conversions, and the like. [0072] MDD 152 may also include an integrated or attachable in vitro glucose meter, including an in vitro test strip port (not shown) to receive an in vitro glucose test strip for performing in vitro blood glucose measurements. Example Embodiments of Display Devices [0073] Display device 120 can be configured to display information pertaining to system 100 to the user and accept or receive input from the user also pertaining to system 100. Display device 120 can display recent measured analyte levels, in any number of forms, to the user. The display device can display historical analyte levels of the user as well as other metrics that describe the user’s analyte information (e.g., time in range, ambulatory glucose profile (AGP), hypoglycemia risk levels, etc.). Display device 120 can display medication delivery information, such as historical dose information and the times and dates of administration. Display device 120 can display alarms, alerts, or other notifications pertaining to analyte levels and/or medication delivery. Docket No. A0130.0324.WO 15021WOO1 [0074] Display device 120 can be dedicated for use with system 100 (e.g., an electronic device designed and manufactured for the primary purpose of interfacing with an analyte sensor and/or a medication delivery device), as well as devices that are multifunctional, general purpose computing devices such as a handheld or portable mobile communication device (e.g., a smartphone or tablet), or a laptop, personal computer, or other computing device. Display device 120 can be configured as a mobile smart wearable electronics assembly, such as a smart glass or smart glasses, or a smart watch or wristband. Display devices, and variations thereof, can be referred to as “reader devices,” “readers,” “handheld electronics” (or handhelds), “portable data processing” devices or units, “information receivers,” “receiver” devices or units (or simply receivers), “relay” devices or units, or “remote” devices or units, to name a few. [0075] FIG.4A is a schematic view depicting an example embodiment of display device 120. Here, display device 120 includes a user interface 121 and a housing 124 in which display device electronics 130 (FIG.4B) are held. User interface 121 can be implemented as a single component (e.g., a touchscreen capable of input and output) or multiple components (e.g., a display and one or more devices configured to receive user input). In this embodiment, user interface 121 includes a touchscreen display 122 (configured to display information and graphics and accept user input by touch) and an input button 123, both of which are coupled with housing 124. [0076] Display device 120 can have software stored thereon (e.g., by the manufacturer or downloaded by the user in the form of one or more “apps” or other software packages) that interface with SCD 102, MDD 152, and/or the user. In addition, or alternatively, the user interface can be affected by a web page displayed on a browser or other internet interfacing software executable on display device 120. [0077] FIG.4B is a block diagram of an example embodiment of a display device 120 with display device electronics 130. Here, display device 120 includes user interface 121 including display 122 and an input component 123 (e.g., a button, actuator, touch sensitive switch, capacitive switch, pressure sensitive switch, jog wheel, microphone, speaker, or the like), processing circuitry 131, memory 125, communication circuitry 126 configured to communicate to and/or from one or more other devices external to display device 120), a power supply 127, and timing circuitry 128 (e.g., such as an oscillator and phase locked loop for providing a clock or other timing to components of SCD 102). Each of the aforementioned components can be Docket No. A0130.0324.WO 15021WOO1 implemented as one or more different devices or can be combined into a multifunctional device (e.g., integration of processing circuitry 131, memory 125, and communication circuitry 126 on a single semiconductor chip). Display device 120 can be implemented in a highly interconnected fashion, where power supply 127 is coupled with each component shown in FIG.4B and where those components that communicate or receive data, information, or commands (e.g., user interface 121, processing circuitry 131, memory 125, communication circuitry 126, and timing circuitry 128), can be communicatively coupled with every other such component over, for example, one or more communication connections or buses 129. FIG.4B is an abbreviated representation of the typical hardware and functionality that resides within a display device and those of ordinary skill in the art will readily recognize that other hardware and functionality (e.g., codecs, drivers, glue logic) can also be included. [0078] Processing circuitry 131 can include one or more processors, microprocessors, controllers, and/or microcontrollers, each of which can be a discrete chip or distributed amongst (and a portion of) a number of different chips. Processing circuitry 131 can include on-board memory. Processing circuitry 131 can interface with communication circuitry 126 and perform analog-to-digital conversions, encoding and decoding, digital signal processing and other functions that facilitate the conversion of data signals into a format (e.g., in-phase and quadrature) suitable for wireless or wired transmission. Processing circuitry 131 can also interface with communication circuitry 126 to perform the reverse functions necessary to receive a wireless transmission and convert it into digital data or information. [0079] Processing circuitry 131 can execute software instructions stored in memory 125. These instructions can cause processing circuitry 131 to process raw analyte data (or pre- processed analyte data) and arrive at a corresponding analyte level suitable for display to the user. These instructions can cause processing circuitry 131 to read, process, and/or store a dose instruction from the user, and because the dose instruction to be communicated to MDD 152. These instructions can cause processing circuitry 131 to execute user interface software adapted to present an interactive group of graphical user interface screens to the user for the purposes of configuring system parameters (e.g., alarm thresholds, notification settings, display preferences, and the like), presenting current and historical analyte level information to the user, presenting current and historical medication delivery information to the user, collecting other non-analyte information from the user (e.g., information about meals consumed, activities performed, Docket No. A0130.0324.WO 15021WOO1 medication administered, and the like), and presenting notifications and alarms to the user. These instructions can also cause processing circuitry 131 to cause communication circuitry 126 to transmit, can cause processing circuitry 131 to read and act on received transmissions, to read input from user interface 121 (e.g., entry of a medication dose to be administered or confirmation of a recommended medication dose), to display data or information on user interface 121, to adjust the timing of timing circuitry 128, to process data or information received from other devices (e.g., analyte data, calibration information, encryption or authentication information received from SCD 102, and others), to perform tasks to establish and maintain communication with SCD 102, to interpret voice commands from a user, and others. The functions described here that are coded in the instructions can instead be implemented by display device 120 with the use of a hardware or firmware design that does not rely on the execution of stored software instructions to accomplish the functions. [0080] Memory 125 can be shared by one or more of the various functional units present within display device 120, or can be distributed amongst two or more of them (e.g., as separate memories present within different chips). Memory 125 can also be a separate chip of its own. Memory 125 is non-transitory, and can be volatile (e.g., RAM, etc.) and/or non-volatile memory (e.g., ROM, flash memory, F-RAM, etc.). [0081] Communication circuitry 126 can be implemented as one or more components (e.g., transmitter, receiver, transceiver, passive circuit, encoder, decoder, and/or other communication circuitry) that perform the functions for communications over the respective communications paths or links. Communication circuitry 126 can include or be coupled to one or more antenna for wireless communication. [0082] Power supply 127 can include one or more batteries, which can be rechargeable or single-use disposable batteries. Power management circuitry can also be included to regulate battery charging and monitor usage of power supply 127, boost power, perform DC conversions, and the like. [0083] Display device 120 can also include one or more data communication ports (not shown) for wired data communication with external devices such as computer system 170, SCD 102, or MDD 152. Display device 120 may also include an integrated or attachable in vitro glucose meter, including an in vitro test strip port (not shown) to receive an in vitro glucose test strip for performing in vitro blood glucose measurements. Docket No. A0130.0324.WO 15021WOO1 [0084] Display device 120 can display the measured analyte data received from SCD 102 and can also be configured to output alarms, alert notifications, glucose values, etc., which may be visual, audible, tactile, or any combination thereof. In some embodiments, SCD 102 and/or MDD 152 can also be configured to output alarms, or alert notifications in visible, audible, tactile forms or combination thereof. Further details and other display embodiments can be found in, e.g., U.S. Patent Publ. No.2011/0193704, which is incorporated herein by reference in its entirety for all purposes. Example Embodiments Related to Integrated Management [0085] The following example embodiments relate to an integrated management system (IMS) that will, in many embodiments, be implemented as a set of software instructions stored and/or executed on one or more electronic devices. In some embodiments, the IMS is stored, executed, and presented to the user on the same single electronic device. In other embodiments, the IMS can be stored and executed on one device, and presented to the user on a different electronic device. For example, the IMS can be stored and executed on trusted computer system 180 and presented to the user by way of a webpage displayed through an internet browser executed on display device 120. [0086] Thus, there are many different embodiments pertaining to the number and type of electronic devices that are used in storing, executing, and presenting the IMS or portions thereof to a user. With respect to presentation to the user, the device that is configured to implement this capability will be referred to herein as a user interface device (UID) 200. FIG.5 is a block diagram depicting an example embodiment of UID 200. In this embodiment, UID 200 includes a housing 201 that is coupled with a user interface 202. The user interface 202 is capable of outputting information to the user and receiving input or information from the user. In some embodiments, the user interface 202 is a touchscreen. As shown here, the user interface 202 includes a display 204, that may be a touchscreen, and an input component 206 (e.g., a button, actuator, touch sensitive switch, capacitive switch, pressure sensitive switch, jog wheel, microphone, touch pad, soft keys, keyboard, or the like). [0087] Many of the devices described herein can be implemented as UID 200. For example, display device 120 will, in many embodiments, be used as UID 200. In some embodiments, MDD 152 can be implemented as UID 200. In embodiments where SCD 102 includes a user Docket No. A0130.0324.WO 15021WOO1 interface, then SCD 102 can be implemented as UID 200. Computer system 170 can also be implemented as UID 200. Example Embodiments of the User Experience of a System Incorporating Medication Adherence [0088] The system may generate and display GUIs that allow for medication adherence data to be entered manually. Reporting software may track and display the patient’s medications and dosing regimen. As part of the display, the software may also provide associated fields to enter adherence. In some embodiments, radio buttons may be provided to select a level of adherence (e.g., one of three levels of adherence). Alternatively, each medication or dose may have an associated drop-down menus displaying a number of days (e.g., 0 to 7) where the user may select the number of days per week on average that the patient administers. The software may include GUIs for recording the adherence for each daily dose of oral medication, the daily dose(s) for long-acting insulin, and for each dose per meal of meal-time insulin. [0089] As seen in FIG.7, an interactive GUI 340 for receiving information regarding a subject’s dosing schedule may be displayed. The GUI 340 may list different types of medication 342a-342d, and provide inputs for the amount of medication typically administered or dosed along with a level of adherence to a dosing schedule. [0090] In some embodiments, the dosage and regimen may be imported from electronic medical records (EMR) or the user may need to manually input the dosage amount 344 and dosage regimens 345 into the GUI 340. If the dosage and regimen were imported, the entry may also include a date that the information was last reconciled with the data source. For long-acting insulins 342c, the GUI 340 may include inputs for a morning dose 350a and an evening dose 350b. For rapid-acting insulin 342d, the GUI 340 may include an input field regarding the types of administration 352 from which the user can select an appropriate option. The types of administration 352 may include injections based on a fixed meal dose 352a, injections based on carbohydrate counting 352b, an insulin pump 352c, or experiential dosing 352d. For rapid- acting insulin 342d, the user may also need to enter dosage information for different meals or times of the day 354 corresponding to when they administer the medication. These different meals or times of the day may include breakfast 354a, lunch 354b, dinner 354c, bedtime 354d, and snack 354e. The information entered for each of these different meals or times of the day includes the number of units 356, 356a-e, a correction factor 358, 358a-e, a target glucose 360, 360a-e, and a correction threshold 362, 362a-e. Docket No. A0130.0324.WO 15021WOO1 [0091] For each medication dose regimen entered, the user will also need to indicate a level of dosing adherence for each of the medications listed. In some embodiments, different levels of adherence 347-349 may be presented as radio buttons from which the user can select. For example, the levels of adherence may be rare 347, approximately half 348, or mostly 349, and the user may select the applicable level of adherence for each dose in the radio button aligned with that dose. In other embodiments, the user may enter a numerical value for the level of adherence or may indicate the relative level of adherence using a slider. [0092] After the dosage regimens have been entered, and a period of time has passed during which the subject is administering the medications, the subject’s level of adherence during the period of time can be assessed and the levels adjusted accordingly. The software may provide a plurality of GUIs to facilitate intake and analysis of dosage regimens and adherence levels or indicators for each regimen. The plurality of GUIs may also include a plurality of tabs 381a- 381f for linking and displaying different parts of the application. As seen in FIGS.8A-8G, these include a history/labs tab 381a, a lifestyle tab 381b, a diabetes medications reconciliation tab 381c, a diabetes events tab 381d, and a treatment assessment tab 381e. The plurality of GUIs may also contain a link to reports discussed herein. [0093] As seen in FIG.8A, GUI 380 may be presented to the user to prompt the user to reconcile and update the medications and associated information. GUI 380 may display a plurality of medications 342a, 342b, along with their respective dose amounts 386a, 388a and dosage regimens 386b, 388b. If dosage or regimen information is missing, a message 387 may be displayed requesting the user to enter dosage and regimen information in the medications panel. The GUI 380 may also include a prompt for the user to select if any changes in therapies 382 (dosage amount or schedule) occurred during the time period, then the changed therapies should be entered. The user may be prompted to reconcile values in the medications panel, and select Reload/Next 384 to load updates. [0094] After any changes to medication dosage amounts and regimens have been entered, as seen in FIG.8B, in GUI 390, the reconciled dosages 391a, 393a and dosing schedules 391b, 393b for each medication 386, 388 may be displayed. The user is also prompted to enter the adherence level for each medication for each and dosage for a period of time, e.g., the last two weeks or since the last intervention. The adherence level options may differ depending on the type of medication and dosing schedule. For example, for a medication that is only administered Docket No. A0130.0324.WO 15021WOO1 or taken once daily, the adherence level options 396 may be not taken 392a, 1 missed 392b, or all taken 392c. For other medications, e.g., a medication that has a dosing schedule of two times a day (BID), the adherence level options 398 may be rarely 397a, 398a, sometimes 397b, 398b, mostly 397c, 398c, or always 397d, 398d. Moreover, adherence level options for each dose 397a-d, 398a-c in the regimen will be displayed. The user will need to select one of the adherence level options for each medication and each dose of each medication listed. The selected adherence level 397d, 398c for that medication dose 402 may then be highlighted to clearly indicate the adherence level selected. After the adherence levels are entered, the user may select the next button 399 and move to the next section. [0095] If the user did indicate that there were changes to the medication regimens or if a change was detected from the associated EMR, as seen in FIG.8C, a GUI 410 may be displayed that provides input fields for any changes to dosage amounts 402a, 402b or dosage schedules for long acting insulin 342c. After changes are entered, as seen in FIG.8D, the reconciled or new dosage regimen 422a-422b may be displayed (along with a link to edit the regimen). Similarly, adherence level options 426a-d, 427a-d for each dose in the regimen will be displayed. The user is also prompted to enter the adherence level for each medication for each dosage for a period of time, e.g., the last two weeks or since the last intervention. The adherence levels may be rarely 426a, 427a, sometimes 426b, 427b, mostly 426c, 427c, or always 426d, 427d. The user will need to select one of the adherence level options for each medication and each dose of each medication listed. The selected adherence level for that medication dose 426 may then be highlighted to indicate the adherence level selected clearly. [0096] As seen in FIG.8E, in GUI 440, if changes need to be made to a fast-acting insulin 342d, similar input fields for different meals or times of the day 354a-354e can be entered. The type of dose and method by which the dose was administered may also be selected. The dose may be a fixed meal dose 352a, based on carb counting 352b, or based on experiential dosing 352d. The dose may have been administered via injections 352e or a pump 352c. The applicable type of dose and method of administration may be selected by the user 352a, 352e.The different meals or times of the day may include any one or combination of breakfast 354a, lunch 354b, dinner 354c, bedtime 354d, and snack 354e. The information entered for each of these different meals or times of the day includes the number of units 356a-e, a correction factor 358a-e, a target glucose 360a-e, and a correction threshold 362a-e. After changes are Docket No. A0130.0324.WO 15021WOO1 entered, as seen in FIG.8F, the reconciled or new dosage regimen may be displayed (along with a link to edit the regimen). The meals that have a dosing schedule 354a-c assigned may be displayed. Similarly, adherence level options 462 for each dose in the regimen may be displayed. The user is also prompted to enter the adherence level for each medication for each and dosage for a period of time, e.g., the last two weeks or since the last intervention. The adherence level options may be rarely 397a, 398a, 401a, sometimes 397b, 398b, 401b, mostly 397c, 398c, 401c, or always 397d, 398d, 401d. The user may need to select one of the adherence level options for each medication and each dose of each medication listed. The selected adherence level for that medication dose 397d, 398d, 401d may be highlighted to clearly indicate the adherence level selected. [0097] After the adherence levels are indicated, as seen in FIG.8G, a GUI 480 may display a summary of the reconciled medications, which may include the name of the medication 342d, the type of dose administered 352a, the mode by which the dose is administered 352e, the dosage regimen(s) 486, and the levels of dose adherence for each of the doses 488, 397d,398d, 401d. The dosage regimen(s) 486 may include the number of units 356a-356c, a correction factor 358a- 358c, a target glucose 360a-360c, and a correction threshold 362a-362c for each dose. A link to edit any of these entries may also be provided. [0098] As seen in FIG.6, an exemplary method 300 for receiving adherence data is described. At Step 302, an interactive graphical user interface associating information configured for interactive display and input is provided to a display device. The information may include at least one medication dosing schedule for a patient and an adherence level for the at least one medication dosing schedule in a time period. Exemplary interactive GUIs for receiving this information are described in FIGS.7-8G. [0099] At Step 304, data input via the interactive graphical user interface is received for the each of the at least one medication dosing schedule for the patient and the adherence level for the at least one medication dosing schedule in a time period. [00100] At Step 306, the data input is stored in a record for the patient. Automated Detection of Dosage Adherence [00101] In some embodiments, a patient’s adherence levels may be automatically determined, rather than manually entered. The user may administer the medication (e.g., insulin) from a Docket No. A0130.0324.WO 15021WOO1 connected medication delivery device 152. The medication delivery device 152 may be a smart, connected insulin pen, a connected pen cap, an automated insulin delivery (AID) device in a closed loop system, an insulin pump system, or a connected pill box, as described previously. The user may transfer the dosage information from the medication delivery device 152 to the display device 120. The transfer can be accomplished by methods known in the art. For example, the display device 120 (e.g., a smart phone) may scan the connected medication delivery device 152 and the information may be transferred via NFC. In some embodiments, upon a successful scan of the insulin pen, the monitoring application may display a confirmation screen. Alternatively, the dosage information may be transferred automatically without any further action required from the user. For instance, no scan may be necessary, and the dose information may be transferred automatically via BLUETOOTH® or another wireless communication protocol. For example, in the case of a connected pen cap, a connected insulin pen, or an AID device, the data may automatically transfer to the display device after the detection of an administered dose. The transfer of the medication information can be referred to in many ways, including scanning, transferring, downloading, uploading, exporting, importing, connecting, syncing, pairing, and other equivalent terminology. The data may also be automatically transferred via wireless communication such as BLUETOOTH®. The data being transferred can include data relating to medication (e.g., insulin) injections, shots, events, notes, log entries, or other equivalent terminology. The data may be referred to as insulin data, insulin records, insulin logs, insulin doses, or other equivalent terminology. [00102] The imported data may be analyzed to determine which doses were taken and which doses were missed, and an adherence level may be assigned. For example, if a patient was supposed to take a medication once a day, 0-2 doses taken per week may be assigned a “rare” adherence level, 3-5 doses taken per week may be assigned “approx. half” adherence level, and 6-7 doses taken per week may be assigned a “mostly” adherence level. Alternatively, these ranges may be computed as percentages, for example, such as 0% to 28.6%, 28.6% to 71.4%, and 71.4% to 100%, respectively, or 0% to 30%, 31% to 70%, 71% to 100%. [00103] For each dose to be taken per day (for instance, a patient on multiple-daily-injection insulin therapy often takes one basal insulin dose per day and up to three meal-time insulin doses, for breakfast, lunch and dinner), the adherence level may be determined. Patients may sometimes skip meal doses because they did not eat a meal, or the meal they consumed had low Docket No. A0130.0324.WO 15021WOO1 carbohydrate content. Ideally, these missed doses would not be counted for the adherence level. In some embodiments, dose adherence may be detected directly from the glucose data and the dosing record. The glucose time series data can be analyzed to estimate if there is a meal consumed by the patient. Exemplary meal detection algorithms are described in US 2021/0050085, WO 2022/169856, and US 2018/0197628, which are all hereby expressly incorporated by reference in their entireties for all purposes. The meal detection algorithm detects that a meal occurred and estimates the start time of the meal. In its simplest form, the algorithm looks for a sufficient rate of positive change in glucose to estimate that there was a meal consumed and then looks back to where the glucose rise started to estimate the meal start time. If a dose was not recorded during the time period associated with the meal start, then the dose is not counted as “missed”. The time period may be from 0.5 hour before the meal start time to 2 hours after the meal start time, for instance. For instance, if for a period of 14 days, only 11 meals were detected, and for these 11 meals there was only 8 associated dose records, then the adherence rate for this dose would be 8 / 11 or 72.7%, which would fall in the “mostly” adherent level in the above example. Note that in a report, these values may be converted to “average number of doses missed per week, or (1 – 0.727) * 7 = 1.9 doses per week missed on average. Without the meal detection algorithm, the doses identified in a 14 day period may be counted, and the adherence level may be calculated. For example, 8 doses in a 14-day period, the adherence level may be calculated as 8 / 14 or 57.1% or (1 – 0.571) * 7 = 3.0 doses per week missed on average. Reports [00104] The monitoring application may transfer data, including analyte levels from the SCD 102 and dosing data/logs from the medication delivery device 152, to a reporting application. The reporting application may be able to generate a plurality of reports that summarize and highlight various aspects of the analyte and medication data and history. The reporting application may be run on the display device or on a separate computing device. In some embodiments, the monitoring application may include instructions that, when executed by one or more processors, generates and display reports that include the insulin data in the monitoring application. Docket No. A0130.0324.WO 15021WOO1 Assessment Report [00105] The system may generate and display an assessment report, where changes in adherence are associated with changes in glycemic patterns. The assessment report may display glycose patterns and metrics side-by-side, dosing adherence (a) prior to an intervention (e.g., period of time before a (first) visit with an HCP), and (b) after the intervention (e.g., period of time after the previous (first) visit but prior to a current (second) visit where a report may be viewed). Glucose metrics may include time-in-range metrics, time below low threshold (e.g., 70 mg/dL) metric, time above high threshold (e.g., 180 mg/dL) metric, and/or a measure of glucose variability such as CV. Additionally, or in the alternative, glucose metrics may include glucose metrics defined by a time-of-day period, such as post-breakfast, post-lunch, post-dinner, or overnight periods, defined by specific times of day or by events such as meal-time boluses or valleys in the glucose data indicative of meal starts. The assessment report may also include a summary of the glucose pattern and/or metric changes, and a summary of the medication adherence changes. For example, for a patient using prandial insulin, the summary may indicate a decrease in average glucose after breakfast. This could be associated with an indication of an increase in breakfast dose adherence, e.g., “Breakfast dose average adherence increased from 4 per week to 6 per week.” In this way, the HCP and patient can determine that the improvement in adherence may be responsible for the improvement in post-breakfast average glucose. The summary may also highlight changes for a time-of-day period that was previously indicated by the HCP as a time-of-day period addressed by the HCP at the previous visit. [00106] FIGS.9A-9C depict example embodiments of an assessment report GUI 500. The assessment report provides a comparison of data from a time period before an intervention 540 and a time period after the intervention 510. The intervention may include a consultation, meeting, or communication with an HCP, where the patient’s treatment was discussed. For each time period 510, 540, the report may also include statistics regarding glucose monitoring during the respective time period. The statistics may include the time that the SCD was active 512, 542, and the average number of scans or views per day 514, 544. [00107] As seen in FIGS.9A-9B, the assessment report GUI 500 may also include a summary of the intervention 502, glucose profiles for the pre-intervention 550 and post-intervention 520 periods, summary of medication dosage adherence for the pre-intervention 570 and post- intervention 600 periods, summary of long-acting insulin dosage adherence for the pre- Docket No. A0130.0324.WO 15021WOO1 intervention 584 and post-intervention 614 periods, and a summary of rapid-acting insulin dosage adherence for the pre-intervention 592 and post-intervention 622 periods. [00108] The summary of the intervention section 520 may include a treatment summary 504, an adherence summary 506, a self-care summary 508, and treatment effectiveness summary 509. The treatment summary 504 may include the date of the intervention and details of a change in treatment, such as a change in a dosage amount or dosage schedule of a medication. The adherence summary 506 may include a summary of changes in adherence since the intervention. For example, the adherence summary 506 may include a statement that adherence increased or decreased for specific medications. The self-care summary 508 may include a summary of self- care actions that were discussed at the intervention. For example, the self-care summary 508 may state that the importance of not over-correcting highs was discussed, or that the importance of consistent meals were discussed. The treatment effectiveness summary 509 may include a summary of issues, along with a status for each of the issues, for each time-of-day period (e.g., overnight, morning, afternoon, and evening). In some embodiments, the treatment effectiveness summary 509 may state a pattern associated with each time-of-day period, and may also state if the pattern changed since the intervention. For example, the treatment effectiveness summary 509 may state that lows have been resolved, replaced by highs and some lows, or highs persist with improvement, or lows resolved, or high and some lows persist. [00109] The glucose profiles for the pre-intervention 550 and post-intervention 520 periods may each include glucose metrics for each of the pre-intervention 552-556 and post-intervention 522-526 periods, graphs of glucose levels for each of the pre-intervention 560 and post- intervention 530 periods, and graphs of daily glucose profiles for each of the pre-intervention 568 and post-intervention 538 periods. The glucose metrics may include a percentage of time in range 552, 522, a percentage of time below range 553, 523, a percentage of time above range 554, 524, a glucose management indicator (GMI) 555, 525, and an average glucose 556, 526. The graphs of glucose levels for each of the pre-intervention 560 and post-intervention 530 periods may be AGP graphs. The AGP graph may display the hourly 5^th, 25^th, 50^th (median), 75^th, and 95^th percentiles of glucose readings, presented over the “typical” day based on all days within the respective timeframe. The AGP graph may also include horizontal lines, which indicate a very low threshold, a low threshold, a high threshold, and a very high threshold. The graphs of daily glucose profiles for each of the pre-intervention 568 and post-intervention 538 Docket No. A0130.0324.WO 15021WOO1 periods include a glucose profile for each day of the time period indicated. The AGP graph and each daily glucose profile graph may be color-coded such that glucose levels within a target range (between the low and high thresholds) are color-coded a first color (e.g., green), glucose levels above the high threshold are color-coded a second color (e.g., yellow), glucose levels below the low threshold are color-coded a third color (e.g., red), and glucose levels below the very low threshold are color-coded a third color (e.g., darker red or maroon). The patterns 534a,b and 564a,b for various time-of-day periods may also be labeled on the AGP graph. Patterns that are particularly problematic or the pattern that should be prioritized 564b may be highlighted by bolding or color-coding. [00110] As seen in FIG.9B, the summary of medication dosage adherence for the pre- intervention 570 and post-intervention 600 periods may each include the name of the medication 572, 602, the dose of the medication 574, 604, the dosing schedule (e.g., QD, BID), and the adherence levels 580a,b and 610a,b. For dosing schedules that have multiple doses in a day, a level of adherence for each dose may be displayed. Changes in the level of adherence may be highlighted 610b. The summary of long-acting insulin dosage adherence for the pre-intervention 584 and post-intervention 614 periods may each include the name of the medication 586, 616, the dose of the medication 588a,b and 618a,b, and the adherence levels 590a,b and 620a,b. For dosing schedules that have multiple doses in a day, a level of adherence for each dose may be displayed. The summary of rapid-acting insulin dosage adherence for the pre-intervention 592 and post-intervention 622 periods may include the name of the rapid-acting insulin 594, 624, the type of administration 596, 626, details relating to each dose administered daily 650-653 and 630-633, and the levels of adherence for each dose 654, 634. The types of administration 596,626 may include injections based on a fixed meal dose, injections based on carbohydrate counting, an insulin pump, or experiential dosing. The details relating to each dose administered daily may include the amount of each dose 650a-c and 630a-c, the correction factor 651a-c and 631a-c, and target glucose 652a-c and 632a-c, the correction threshold 653a-c and 633a-c, and the dose adherence levels 654a-c and 634a-c. [00111] Optionally, as seen in FIG.9C, the assessment report may also include a section that highlights changes for a time-of-day period that was previously addressed by the HCP during the intervention. The assessment report may include a section highlighting a time-of-day period. The time-of-day period section 670 may identify the pattern 672 treated in a certain time-of-day Docket No. A0130.0324.WO 15021WOO1 period pre-intervention, and the new pattern 702 in the time-of-day period in the post- intervention period in addition to a status 704 relating to the new pattern. For example, the status 704 may state that the lows persist, but are reduced. [00112] The time-of-day period section 670 may also include a time in range summary for each of the pre-intervention 675 and post-intervention 705 time periods. The time in ranges section may include time-in-ranges (also referred to as Time-in-Range and/or Time-in-Target) graphs, each of which comprise a plurality of bars or bar portions, wherein each bar or bar portion indicates an amount of time that a user’s analyte level is within a predefined analyte range correlating with the bar or bar portion. In some embodiments, for example, the amount of time can be expressed as a percentage of a predefined amount of time. Time-in-Ranges sections 675, 705 may include a single bar graph comprising up to five bar portions including (from top to bottom): a first bar portion indicating that the user’s glucose range is “Very High” or above 250 mg/dL of a predefined amount of time, a second bar portion indicating that the user’s glucose range is “High” or between 180 and 250 mg/dL of the predefined amount of time, a third bar portion indicating that the user’s glucose range is within a “Target Range” or between 70 and 180 mg/dL of the predefined amount of time, a fourth bar portion indicating that the user’s glucose range is “Low” or between 54 and 69 mg/dL of the predefined amount of time, and a fifth bar portion indicating that the user’s glucose range is “Very Low” or less than 54 mg/dL of the predefined amount of time. Time-in-Ranges sections 675, 705 may display text adjacent to each bar portion indicating an actual amount of time, e.g., in hours and/or minutes 676-680 and 706-710. Each bar portion of Time-in-Ranges graphs may comprise a different color. In some embodiments, bar portions can be separated by dashed or dotted lines and/or interlineated with numeric markers to indicate the ranges reflected by the adjacent bar portions. In some embodiments, the time in ranges reflected by the bar portions can be further expressed as a percentage, an actual amount of time (e.g., 4 hours and 19 minutes), or both. [00113] The time-of-day period section 670 may also include a glucose metrics summary for each of the pre-intervention 685 and post-intervention 715 time periods. The glucose metrics sections 685, 715 may include, for example, the glucose management indicator (GMI) 686, 716, the average glucose 688, 718, and the glucose variability 690, 720. [00114] The time-of-day period section 670 may also display an indication of the medication adherence for the time-of-day period in the pre-intervention 692 and post-intervention 722 Docket No. A0130.0324.WO 15021WOO1 periods. The indications of the medication adherence 692, 722 may include a statement as to how many doses were administered during the time-of-day period for the pre-intervention 692 and post-intervention 722 periods. For example, the pre-intervention period 692 may state that for breakfast doses, the patient averaged 3 per week, and the post-intervention period 722 may state that for breakfast doses, the patient averaged 6 per week. The time-of-day period section 670 may also include an adherence summary 724 that may include a correlation between the adherence and the time-in-range statistics or glucose metrics. For example, the adherence summary 724 may state that an increase in breakfast dose adherence of 3 per week is associated with a 4% reduction in time-below-70 mg/dL. Intervention Report [00115] The system may also generate and display an intervention report, which may show the current glucose patterns and the current medication adherence. For example, the report may show that the post-dinner glucose levels are elevated; however, the report may also show that the dinner dose adherence may be low. Without this adherence information, the HCP may be inclined to increase the patient’s dinner insulin. A better course of treatment, however, may be to encourage the patient to increase their adherence and leave the dose amount unchanged. Reporting both the glucose patterns and adherence information in the same report assists the HCP in making better treatment decisions. In addition, the software may detect, for instance, a high glucose pattern that coincides with a low medication adherence (e.g., a dose rate of less than 6 times per week), and display an indication of this condition. Poor adherence could be highlighting this medication dose in some visual way (e.g., red text in contrast to usual black text) or stating this condition in special text display. [00116] FIG.10 depicts an exemplary embodiment of an intervention report GUI 740. The intervention report GUI 740 includes the patient’s name, date range encompassed in the report 742, a glucose metrics summary section 742, a time in range summary section 750, a patterns summary section 770, and adherence summary section 780, and glucose profile section 790. [00117] The glucose metrics summary section 742 may include, for example, the glucose management indicator (GMI) 744, the average glucose 746, and the glucose variability 748. [00118] The time in range summary section 750 may include Time-in-Ranges (also referred to as Time-in-Range and/or Time-in-Target) graphs, each of which comprise a plurality of bars or Docket No. A0130.0324.WO 15021WOO1 bar portions, wherein each bar or bar portion indicates an amount of time that a user’s analyte level is within a predefined analyte range correlating with the bar or bar portion. In some embodiments, for example, the amount of time can be expressed as a percentage of a predefined amount of time. Time-in-Ranges section 750 may include a single bar graph comprising up to five bar portions including (from top to bottom): a first bar portion indicating that the user’s glucose range is “Very High” or above 250 mg/dL of a predefined amount of time, a second bar portion indicating that the user’s glucose range is “High” or between 180 and 250 mg/dL of the predefined amount of time, a third bar portion indicating that the user’s glucose range is within a “Target Range” or between 70 and 180 mg/dL of the predefined amount of time, a fourth bar portion indicating that the user’s glucose range is “Low” or between 54 and 69 mg/dL of the predefined amount of time, and a fifth bar portion indicating that the user’s glucose range is “Very Low” or less than 54 mg/dL of the predefined amount of time. Time-in-Ranges sections 750 may display text adjacent to each bar portion indicating an actual amount of time, e.g., in hours and/or minutes 756-760. Each bar portion of the Time-in-Ranges graph may comprise a different color. In some embodiments, bar portions can be separated by dashed or dotted lines and/or interlineated with numeric markers to indicate the ranges reflected by the adjacent bar portions. In some embodiments, the time in ranges reflected by the bar portions can be further expressed as a percentage, an actual amount of time (e.g., 4 hours and 19 minutes), or both. [00119] The patterns summary section 770 may list the pattern detected for at least one time- of-day period. In some embodiments, the patterns summary section 770 may list the pattern detected for each of the time-of-day periods, e.g., overnight, morning, afternoon, and evening. Alternatively, the patterns summary section 770 may list the time-of-day periods and patterns that are most problematic, e.g., low glucose levels, that should be addressed first. [00120] The adherence summary section 780 may include all of the medications taken by the patient, along with their adherence levels. In some embodiments, the adherence summary section 780 includes a section for medications 782 (e.g., non-insulin medications) and include the name of the medication, the dose of the medication, the dosing schedule (e.g., QD, BID), and the adherence levels. [00121] The adherence summary section 780 may also include a long-acting insulin summary 784a,b that includes the name of the medication, the dose of the medication, and the adherence Docket No. A0130.0324.WO 15021WOO1 levels. For dosing schedules that have multiple doses in a day, a level of adherence for each dose may be displayed. [00122] The adherence summary section 780 may also include a rapid-acting insulin summary 786a-c that includes the name of the rapid-acting insulin, the type of administration, details relating to each dose administered daily, and the levels of adherence for each dose. The types of administration may include injections based on a fixed meal dose, injections based on carbohydrate counting, an insulin pump, or experiential dosing. The details relating to each dose administered daily may include the amount of each dose, the correction factor, and target glucose, the correction threshold, and the dose adherence levels. [00123] The glucose profile section 790 may include an AGP graph. The AGP graph may display the hourly 5^th, 25^th, 50^th (median), 75^th, and 95^th percentiles of glucose readings, presented over the “typical” day based on all days within the respective timeframe. The AGP graph may also include horizontal lines, which indicate a very low threshold, a low threshold, a high threshold, and a very high threshold. The AGP graph may be color-coded such that glucose levels within a target range (between the low and high thresholds) are color-coded a first color (e.g., green), glucose levels above the high threshold are color-coded a second color (e.g., yellow), glucose levels below the low threshold are color-coded a third color (e.g., red), and glucose levels below the very low threshold are color-coded a third color (e.g., darker red or maroon). The patterns 792a,b for various time-of-day periods may also be labeled on the graph. Patterns that are particularly problematic or the pattern that should be prioritized 792b may be highlighted by bolding or color-coding. [00124] The patient may adjust their dosing according to the recommendations received from the HCP in light of the reports described herein. The patient may administer the medication according to the recommended dosing schedules. [00125] Various aspects of the present subject matter are set forth below, in review of, and/or in supplementation to, the embodiments described thus far, with the emphasis here being on the interrelation and interchangeability of the following embodiments. In other words, an emphasis is on the fact that each feature of the embodiments can be combined with each and every other feature unless explicitly stated otherwise or logically implausible. The embodiments described herein are restated and expanded upon in the following paragraphs without explicit reference to the figures. Docket No. A0130.0324.WO 15021WOO1 [00126] In many embodiments, a system includes: wireless communication circuitry configured to receive data indicative of a glucose level; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated received data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: define separate first and second datasets of the received data corresponding to a first and a second time period; determine a first measure of adherence for a first dosing regimen in the first time period and a second measure of adherence for a second dosing regimen in the second time period; determine a first plurality of glucose metrics based on the first dataset and a second plurality of glucose metrics based on the second dataset; determine a glucose pattern for each time-of-day period in the separate first and second datasets; and display a GUI comprising: a first glucose profile based on the first dataset and a second analyte profile based on the second dataset, wherein the first and second analyte profiles each identify at least one glucose pattern determined for a time-of-day period in the first and second datasets; the first plurality of glucose metrics and the second plurality of glucose metrics; and the first measure of adherence and the second measure of adherence. [00127] In some embodiments, the first glucose profile comprises a plot of analyte levels determined from analyte data over the time period, wherein the plot displays a median analyte trace, and a plurality of traces for analyte levels at different percentiles. [00128] In some embodiments, the first measure of adherence and the second measure of adherence are determined based on input from the subject. [00129] In some embodiments, the wireless communication circuitry is further configured to receive dosing data, and wherein the first measure of adherence and the second measure of adherence are determined based on the received dosing data. [00130] In some embodiments, the GUI further comprises a first plurality of daily graphs corresponding to each day of the first period of time and a second plurality of daily graphs corresponding to each day of the second period of time, each graph of the first and second pluralities of daily graphs comprising an x-axis of time, a y-axis of glucose concentration, a plot of a glucose concentration over a 24-hour period. [00131] In some embodiments, the first time period occurred before a clinical intervention of the subject and the second time period occurred after the clinical intervention of the subject. Docket No. A0130.0324.WO 15021WOO1 [00132] In some embodiments, the GUI further comprises a summary of a therapy change from the clinical intervention. [00133] In some embodiments, the GUI further comprises a summary of effectiveness of the clinical intervention for at least one time-of-day period. In some embodiments, the GUI further comprises a summary of effectiveness of the clinical intervention for each time-of-day period. [00134] In some embodiments, the GUI further comprises a summary of changes in adherence since the clinical intervention. [00135] In some embodiments, the GUI further comprises a summary of actions for the subject discussed at the clinical intervention. [00136] In some embodiments, the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a time-in-range metric. In some embodiments, the first plurality of glucose metrics and the second plurality of glucose metrics each further comprise a time-below-range metric and a time-above-range metric. [00137] In some embodiments, the first plurality of glucose metrics and the second plurality of glucose metrics each comprise an average glucose metric. [00138] In some embodiments, the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a glucose management indicator (GMI). [00139] In some embodiments, the GUI further comprises a summary of medication taken during the first time period and the second time period. [00140] In many embodiments, a system includes: wireless communication circuitry configured to receive data indicative of a glucose level; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated received data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: determine a measure of adherence for a dosing regimen in a time period; determine a plurality of glucose metrics based on a dataset comprising received data indicative of a glucose level in the time period; determine a glucose pattern for each of corresponding time-of-day periods based on the dataset; and display a GUI comprising: a glucose profile based on the dataset, wherein the glucose profile comprises a plot of glucose levels determined from the dataset and at least one glucose pattern determined for a time-of-day Docket No. A0130.0324.WO 15021WOO1 period; a plurality of glucose metrics determined from the dataset; and a measure of adherence of at least one dosing regimen during the time period. [00141] In some embodiments, the plot of glucose levels determined from the dataset comprises a median glucose trace, and a plurality of traces for glucose levels at different percentiles. [00142] In some embodiments, the measure of adherence is determined based on input from the subject. [00143] In some embodiments, the wireless communication circuitry is further configured to receive dosing data, and wherein the measure of adherence is determined based on the received dosing data. [00144] In some embodiments, the plurality of glucose metrics comprises a time-in-range metric. In some embodiments, the plurality of glucose metrics further comprises a time-below- range metric and a time-above-range metric. [00145] In some embodiments, the first plurality of glucose metrics and the second plurality of glucose metrics each comprise an average glucose metric. [00146] In some embodiments, the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a glucose management indicator (GMI). [00147] In some embodiments, the measure of adherence comprises an adherence indicator. In some embodiments, the adherence indicator is a numeric value. In some embodiments, the adherence indicator is a graphical representation. [00148] In many embodiments, a method for analyzing medication dosing adherence, includes the steps of: providing, to a display device, an interactive graphical user interface associating information configured for interactive display and input, the information comprising at least one medication dosing schedule for a patient, and an adherence level for the at least one medication dosing schedule in a time period; receiving data input via the interactive graphical user interface for the each of the at least one medication dosing schedule for the patient and the adherence level for the at least one medication dosing schedule in a time period; and storing the data input in a record for the patient. [00149] In some embodiments, the information configured for interactive display further comprises a dosage amount for the at least one medication of the at least one medication dosing schedule. Docket No. A0130.0324.WO 15021WOO1 [00150] In some embodiments, the information configured for interactive display and input for the adherence level comprises a plurality of adherence levels, wherein one or more processors enables selection of an adherence level from the plurality of adherence levels by a user of the interactive graphical user interface. In some embodiments, the plurality of adherence levels comprises at least three levels of adherence. [00151] In some embodiments, at least one medication of the at least one medication dosing schedule is a long-acting insulin. [00152] In some embodiments, at least one medication of the at least one medication dosing schedule is a rapid-acting insulin, and wherein the at least one medication dosing schedule comprises a plurality of dosing schedules. In some embodiments, the plurality of dosing schedules comprises a breakfast dosing schedule, a lunch dosing schedule, and a dinner dosing schedule. [00153] In some embodiments, the at least one medication dosing schedule comprises a bolus meal dose amount. In some embodiments, the at least one medication dosing schedule further comprises a correction factor. In some embodiments, the at least one medication dosing schedule further comprises a target glucose and a correction threshold. [00154] In some embodiments, the method further includes the step of providing, by one or more processors, to the display device a second interactive graphical user interface associating additional information configured for interactive display and input, the additional information comprising changes to at least one medication dosing schedule. [00155] In some embodiments, the method further includes the step of providing, by one or more processors, to the display device for display of a summary of the data inputted for the each at least one medication dosing schedule for the patient and the adherence level for the at least one medication dosing schedule in a time period. [00156] In many embodiments, a system includes: wireless communication circuitry configured to receive data indicative of a glucose level and data indicative of adherence to a dosing regimen; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: display an interactive graphical user interface comprising a first input field for a medication Docket No. A0130.0324.WO 15021WOO1 dosing schedule for a patient, and a second input field for an adherence level for the medication dosing schedule; receive data input via the interactive graphical user interface for the medication dosing schedule for the patient and the adherence level for the medication dosing schedule in a time period; and store the data input received in a record for the patient. [00157] In some embodiments, the first input field comprises a dosage amount for the medication and a dosing schedule for the medication. [00158] In some embodiments, the second input field comprises a plurality of adherence level options, wherein the one or more processors enables selection of an adherence level from the plurality of adherence level options by the subject in the interactive graphical user interface. In some embodiments, the plurality of adherence levels comprises at least three levels of adherence. [00159] In some embodiments, the medication of the medication dosing schedule is a long- acting insulin. [00160] In some embodiments, the medication of the medication dosing schedule is a rapid- acting insulin, and wherein the medication dosing schedule comprises a plurality of dosing schedules. In some embodiments, the plurality of dosing schedules comprises a breakfast dosing schedule, a lunch dosing schedule, and a dinner dosing schedule. [00161] In some embodiments, the medication dosing schedule comprises a bolus meal dose amount. [00162] In some embodiments, the medication dosing schedule further comprises a correction factor. [00163] In some embodiments, the medication dosing schedule further comprises a target glucose and a correction threshold. [00164] In some embodiments, the instructions, when executed by the one or more processors, cause the system to display a second interactive graphical user interface comprising a third input field for a changed medication dosing schedule for the patient. [00165] In some embodiments, the instructions, when executed by the one or more processors, cause the system to: display a GUI comprising: a first glucose profile based on data indicative of glucose levels received in the time period, wherein the first analyte profile comprises at least one glucose pattern determined for a time-of-day period; a first plurality of glucose metrics determined based on the data indicative of glucose levels received in the time period; and a measure of adherence for the medication dosing schedule during the time period. Docket No. A0130.0324.WO 15021WOO1 Clauses Exemplary embodiments are set out in the following numbered clauses. Clause 1. A system comprising: wireless communication circuitry configured to receive data indicative of a glucose level; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated received data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: define separate first and second datasets of the received data corresponding to a first and a second time period; determine a first measure of adherence for a first dosing regimen in the first time period and a second measure of adherence for a second dosing regimen in the second time period; determine a first plurality of glucose metrics based on the first dataset and a second plurality of glucose metrics based on the second dataset; determine a glucose pattern for each time-of-day period in the separate first and second datasets; and display a GUI comprising: a first glucose profile based on the first dataset and a second analyte profile based on the second dataset, wherein the first and second analyte profiles each identify at least one glucose pattern determined for a time-of-day period in the first and second datasets; the first plurality of glucose metrics and the second plurality of glucose metrics; and the first measure of adherence and the second measure of adherence. Clause 2. The system of clause 1, wherein the first glucose profile comprises a plot of analyte levels determined from analyte data over the time period, wherein the plot displays a Docket No. A0130.0324.WO 15021WOO1 median analyte trace, and a plurality of traces for analyte levels at different percentiles. Clause 3. The system of any of clauses 1-2, wherein the first measure of adherence and the second measure of adherence are determined based on input from the subject. Clause 4. The system of any of clauses 1-3, wherein the wireless communication circuitry is further configured to receive dosing data, and wherein the first measure of adherence and the second measure of adherence are determined based on the received dosing data. Clause 5. The system of any of clauses 1-4, wherein the GUI further comprises a first plurality of daily graphs corresponding to each day of the first period of time and a second plurality of daily graphs corresponding to each day of the second period of time, each graph of the first and second pluralities of daily graphs comprising an x-axis of time, a y-axis of glucose concentration, a plot of a glucose concentration over a 24-hour period. Clause 6. The system of any of clauses 1-5, wherein the first time period occurred before a clinical intervention of the subject and the second time period occurred after the clinical intervention of the subject. Clause 7. The system of clause 6, wherein the GUI further comprises a summary of a therapy change from the clinical intervention. Clause 8. The system of clause 6 or 7, wherein the GUI further comprises a summary of effectiveness of the clinical intervention for at least one time-of-day period. Clause 9. The system of clause 8, wherein the GUI further comprises a summary of effectiveness of the clinical intervention for each time-of-day period. Clause 10. The system of any of clauses 6 to 9, wherein the GUI further comprises a summary of changes in adherence since the clinical intervention. Clause 11. The system of any of clauses 6 to 10, wherein the GUI further comprises a summary of actions for the subject discussed at the clinical intervention. Clause 12. The system of any of clauses 1-11, wherein the first plurality of glucose Docket No. A0130.0324.WO 15021WOO1 metrics and the second plurality of glucose metrics each comprise a time-in-range metric. Clause 13. The system of clause 12, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each further comprise a time-below-range metric and a time-above-range metric. Clause 14. The system of any of clauses 1-13, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise an average glucose metric. Clause 15. The system of any of clauses 1-14, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a glucose management indicator (GMI). Clause 16. The system of any of clauses 1-15, wherein the GUI further comprises a summary of medication taken during the first time period and the second time period. Clause 17. A system comprising: wireless communication circuitry configured to receive data indicative of a glucose level; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated received data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: determine a measure of adherence for a dosing regimen in a time period; determine a plurality of glucose metrics based on a dataset comprising received data indicative of a glucose level in the time period; determine a glucose pattern for each of corresponding time-of-day periods based on the dataset; and display a GUI comprising: a glucose profile based on the dataset, wherein the glucose profile comprises a plot of glucose levels determined from the dataset and at least one glucose pattern determined for a time-of-day period; Docket No. A0130.0324.WO 15021WOO1 a plurality of glucose metrics determined from the dataset; and a measure of adherence of at least one dosing regimen during the time period. Clause 18. The system of clause 17, wherein the plot of glucose levels determined from the dataset comprises a median glucose trace, and a plurality of traces for glucose levels at different percentiles. Clause 19. The system of any of clauses 17-18, wherein the measure of adherence is determined based on input from the subject. Clause 20. The system of any of clauses 17-19, wherein the wireless communication circuitry is further configured to receive dosing data, and wherein the measure of adherence is determined based on the received dosing data. Clause 21. The system of any of clauses 17-20, wherein the plurality of glucose metrics comprises a time-in-range metric. Clause 22. The system of any of clauses 17-21, wherein the plurality of glucose metrics further comprises a time-below-range metric and a time-above-range metric. Clause 23. The system of any of clauses 17-22, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise an average glucose metric. Clause 24. The system of any of clauses 17-23, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a glucose management indicator (GMI). Clause 25. The system of any of clauses 17-24, wherein the measure of adherence comprises an adherence indicator. Clause 26. The system of clause 25, wherein the adherence indicator is a numeric value. Clause 27. The system of clause 25, wherein the adherence indicator is a graphical Docket No. A0130.0324.WO 15021WOO1 representation. Clause 28. A method for analyzing medication dosing adherence, comprising the steps of: providing, to a display device, an interactive graphical user interface associating information configured for interactive display and input, the information comprising at least one medication dosing schedule for a patient, and an adherence level for the at least one medication dosing schedule in a time period; receiving data input via the interactive graphical user interface for the each of the at least one medication dosing schedule for the patient and the adherence level for the at least one medication dosing schedule in a time period; and storing the data input in a record for the patient. Clause 29. The method of clause 28, wherein the information configured for interactive display further comprises a dosage amount for the at least one medication of the at least one medication dosing schedule. Clause 30. The method of any of clauses 28-29, wherein the information configured for interactive display and input for the adherence level comprises a plurality of adherence levels, wherein one or more processors enables selection of an adherence level from the plurality of adherence levels by a user of the interactive graphical user interface. Clause 31. The method of clause 30, wherein the plurality of adherence levels comprises at least three levels of adherence. Clause 32. The method of any of clauses 28-31, wherein at least one medication of the at least one medication dosing schedule is a long-acting insulin. Clause 33. The method of any of clauses 28-32, wherein at least one medication of the at least one medication dosing schedule is a rapid-acting insulin, and wherein the at least one medication dosing schedule comprises a plurality of dosing schedules. Clause 34. The method of clause 33, wherein the plurality of dosing schedules comprises a breakfast dosing schedule, a lunch dosing schedule, and a dinner dosing schedule. Docket No. A0130.0324.WO 15021WOO1 Clause 35. The method of any of clauses 28-34, wherein the at least one medication dosing schedule comprises a bolus meal dose amount. Clause 36. The method of any of clauses 28-35, wherein the at least one medication dosing schedule further comprises a correction factor. Clause 37. The method of any of clauses 28-36, wherein the at least one medication dosing schedule further comprises a target glucose and a correction threshold. Clause 38. The method of any of clauses 28-37, further comprising the step of providing, by one or more processors, to the display device a second interactive graphical user interface associating additional information configured for interactive display and input, the additional information comprising changes to at least one medication dosing schedule. Clause 39. The method of any of clauses 28-38, further comprising the step of providing, by one or more processors, to the display device for display of a summary of the data inputted for the each at least one medication dosing schedule for the patient and the adherence level for the at least one medication dosing schedule in a time period. Clause 40. A system comprising: wireless communication circuitry configured to receive data indicative of a glucose level and data indicative of adherence to a dosing regimen; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: display an interactive graphical user interface comprising a first input field for a medication dosing schedule for a patient, and a second input field for an adherence level for the medication dosing schedule; receive data input via the interactive graphical user interface for the medication dosing schedule for the patient and the adherence level for the medication dosing schedule in a time period; and Docket No. A0130.0324.WO 15021WOO1 store the data input received in a record for the patient. Clause 41. The system of clause 40, wherein the first input field comprises a dosage amount for the medication and a dosing schedule for the medication. Clause 42. The system of any of clauses 40-41, wherein the second input field comprises a plurality of adherence level options, wherein the one or more processors enables selection of an adherence level from the plurality of adherence level options by the subject in the interactive graphical user interface. Clause 43. The system of clause 42, wherein the plurality of adherence levels comprises at least three levels of adherence. Clause 44. The system of any of clauses 40-43, wherein the medication of the medication dosing schedule is a long-acting insulin. Clause 45. The system of any of clauses 40-44, wherein the medication of the medication dosing schedule is a rapid-acting insulin, and wherein the medication dosing schedule comprises a plurality of dosing schedules. Clause 46. The system of clause 45, wherein the plurality of dosing schedules comprises a breakfast dosing schedule, a lunch dosing schedule, and a dinner dosing schedule. Clause 47. The system of any of clauses 40-46, wherein the medication dosing schedule comprises a bolus meal dose amount. Clause 48. The system of any of clauses 40-47, wherein the medication dosing schedule further comprises a correction factor. Clause 49. The system of any of clauses 40-48, wherein the medication dosing schedule further comprises a target glucose and a correction threshold. Clause 50. The system of any of clauses 40-49, wherein the instructions, when executed by the one or more processors, cause the system to display a second interactive graphical user interface comprising a third input field for a changed medication dosing schedule for the patient. Docket No. A0130.0324.WO 15021WOO1 Clause 51. The system of any of clauses 40-50, wherein the instructions, when executed by the one or more processors, cause the system to: display a GUI comprising: a first glucose profile based on data indicative of glucose levels received in the time period, wherein the first analyte profile comprises at least one glucose pattern determined for a time-of-day period; a first plurality of glucose metrics determined based on the data indicative of glucose levels received in the time period; and a measure of adherence for the medication dosing schedule during the time period.

Claims

Docket No. A0130.0324.WO 15021WOO1 CLAIMS What is claimed is: 1. A system comprising: wireless communication circuitry configured to receive data indicative of a glucose level; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated received data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: define separate first and second datasets of the received data corresponding to a first and a second time period; determine a first measure of adherence for a first dosing regimen in the first time period and a second measure of adherence for a second dosing regimen in the second time period; determine a first plurality of glucose metrics based on the first dataset and a second plurality of glucose metrics based on the second dataset; determine a glucose pattern for each time-of-day period in the separate first and second datasets; and display a GUI comprising: a first glucose profile based on the first dataset and a second analyte profile based on the second dataset, wherein the first and second analyte profiles each identify at least one glucose pattern determined for a time-of-day period in the first and second datasets; the first plurality of glucose metrics and the second plurality of glucose metrics; and the first measure of adherence and the second measure of adherence. 2. The system of claim 1, wherein the first glucose profile comprises a plot of analyte levels determined from analyte data over the time period, wherein the plot displays a median analyte trace, and a plurality of traces for analyte levels at different percentiles. Docket No. A0130.0324.WO 15021WOO1 3. The system of claim 1, wherein the first measure of adherence and the second measure of adherence are determined based on input from the subject. 4. The system of claim 1, wherein the wireless communication circuitry is further configured to receive dosing data, and wherein the first measure of adherence and the second measure of adherence are determined based on the received dosing data. 5. The system of claim 1, wherein the GUI further comprises a first plurality of daily graphs corresponding to each day of the first period of time and a second plurality of daily graphs corresponding to each day of the second period of time, each graph of the first and second pluralities of daily graphs comprising an x-axis of time, a y-axis of glucose concentration, a plot of a glucose concentration over a 24-hour period. 6. The system of claim 1, wherein the first time period occurred before a clinical intervention of the subject and the second time period occurred after the clinical intervention of the subject. 7. The system of claim 6, wherein the GUI further comprises a summary of a therapy change from the clinical intervention. 8. The system of claim 6, wherein the GUI further comprises a summary of effectiveness of the clinical intervention for at least one time-of-day period. 9. The system of claim 6, wherein the GUI further comprises a summary of effectiveness of the clinical intervention for each time-of-day period. 10. The system of claim 6, wherein the GUI further comprises a summary of changes in adherence since the clinical intervention. 11. The system of claim 6, wherein the GUI further comprises a summary of actions for the subject discussed at the clinical intervention. 12. The system of claim 1, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a time-in-range metric. Docket No. A0130.0324.WO 15021WOO1 13. The system of claim 12, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each further comprise a time-below-range metric and a time- above-range metric. 14. The system of claim 1, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise an average glucose metric. 15. The system of claim 1, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a glucose management indicator (GMI). 16. The system of claim 1, wherein the GUI further comprises a summary of medication taken during the first time period and the second time period. 17. A system comprising: wireless communication circuitry configured to receive data indicative of a glucose level; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated received data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: determine a measure of adherence for a dosing regimen in a time period; determine a plurality of glucose metrics based on a dataset comprising received data indicative of a glucose level in the time period; determine a glucose pattern for each of corresponding time-of-day periods based on the dataset; and display a GUI comprising: a glucose profile based on the dataset, wherein the glucose profile comprises a plot of glucose levels determined from the dataset and at least one glucose pattern determined for a time-of-day period; a plurality of glucose metrics determined from the dataset; and a measure of adherence of at least one dosing regimen during the time period. Docket No. A0130.0324.WO 15021WOO1 18. The system of claim 17, wherein the plot of glucose levels determined from the dataset comprises a median glucose trace, and a plurality of traces for glucose levels at different percentiles. 19. The system of claim 17, wherein the measure of adherence is determined based on input from the subject. 20. The system of claim 17, wherein the wireless communication circuitry is further configured to receive dosing data, and wherein the measure of adherence is determined based on the received dosing data. 21. The system of claim 17, wherein the plurality of glucose metrics comprises a time-in-range metric. 22. The system of claim 21, wherein the plurality of glucose metrics further comprises a time-below-range metric and a time-above-range metric. 23. The system of claim 17, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise an average glucose metric. 24. The system of claim 17, wherein the first plurality of glucose metrics and the second plurality of glucose metrics each comprise a glucose management indicator (GMI). 25. The system of claim 17, wherein the measure of adherence comprises an adherence indicator. 26. The system of claim 25, wherein the adherence indicator is a numeric value. 27. The system of claim 25, wherein the adherence indicator is a graphical representation. 28. A method for analyzing medication dosing adherence, comprising the steps of: providing, to a display device, an interactive graphical user interface associating information configured for interactive display and input, the information comprising at least one medication dosing schedule for a patient, and an adherence level for the at least one medication Docket No. A0130.0324.WO 15021WOO1 dosing schedule in a time period; receiving data input via the interactive graphical user interface for the each of the at least one medication dosing schedule for the patient and the adherence level for the at least one medication dosing schedule in a time period; and storing the data input in a record for the patient. 29. The method of claim 28, wherein the information configured for interactive display further comprises a dosage amount for the at least one medication of the at least one medication dosing schedule. 30. The method of claim 28, wherein the information configured for interactive display and input for the adherence level comprises a plurality of adherence levels, wherein one or more processors enables selection of an adherence level from the plurality of adherence levels by a user of the interactive graphical user interface. 31. The method of claim 30, wherein the plurality of adherence levels comprises at least three levels of adherence. 32. The method of claim 28, wherein at least one medication of the at least one medication dosing schedule is a long-acting insulin. 33. The method of claim 28, wherein at least one medication of the at least one medication dosing schedule is a rapid-acting insulin, and wherein the at least one medication dosing schedule comprises a plurality of dosing schedules. 34. The method of claim 33, wherein the plurality of dosing schedules comprises a breakfast dosing schedule, a lunch dosing schedule, and a dinner dosing schedule. 35. The method of claim 28, wherein the at least one medication dosing schedule comprises a bolus meal dose amount. 36. The method of claim 35, wherein the at least one medication dosing schedule further comprises a correction factor. 37. The method of claim 36, wherein the at least one medication dosing schedule Docket No. A0130.0324.WO 15021WOO1 further comprises a target glucose and a correction threshold. 38. The method of claim 28, further comprising the step of providing, by one or more processors, to the display device a second interactive graphical user interface associating additional information configured for interactive display and input, the additional information comprising changes to at least one medication dosing schedule. 39. The method of claim 28, further comprising the step of providing, by one or more processors, to the display device for display of a summary of the data inputted for the each at least one medication dosing schedule for the patient and the adherence level for the at least one medication dosing schedule in a time period. 40. A system comprising: wireless communication circuitry configured to receive data indicative of a glucose level and data indicative of adherence to a dosing regimen; a display configured to visually present information; and one or more processors coupled with the wireless communication circuitry, the display, and a memory storing instructions and time-correlated data indicative of a glucose level of a subject over a period of time, wherein the instructions, when executed by the one or more processors, cause the system to: display an interactive graphical user interface comprising a first input field for a medication dosing schedule for a patient, and a second input field for an adherence level for the medication dosing schedule; receive data input via the interactive graphical user interface for the medication dosing schedule for the patient and the adherence level for the medication dosing schedule in a time period; and store the data input received in a record for the patient. 41. The system of claim 40, wherein the first input field comprises a dosage amount for the medication and a dosing schedule for the medication. 42. The system of claim 40, wherein the second input field comprises a plurality of adherence level options, wherein the one or more processors enables selection of an adherence level from the plurality of adherence level options by the subject in the interactive graphical user Docket No. A0130.0324.WO 15021WOO1 interface. 43. The system of claim 42, wherein the plurality of adherence levels comprises at least three levels of adherence. 44. The system of claim 40, wherein the medication of the medication dosing schedule is a long-acting insulin. 45. The system of claim 40, wherein the medication of the medication dosing schedule is a rapid-acting insulin, and wherein the medication dosing schedule comprises a plurality of dosing schedules. 46. The system of claim 45, wherein the plurality of dosing schedules comprises a breakfast dosing schedule, a lunch dosing schedule, and a dinner dosing schedule. 47. The system of claim 40, wherein the medication dosing schedule comprises a bolus meal dose amount. 48. The system of claim 40, wherein the medication dosing schedule further comprises a correction factor. 49. The system of claim 40, wherein the medication dosing schedule further comprises a target glucose and a correction threshold. 50. The system of claim 40, wherein the instructions, when executed by the one or more processors, cause the system to display a second interactive graphical user interface comprising a third input field for a changed medication dosing schedule for the patient. 51. The system of claim 40, wherein the instructions, when executed by the one or more processors, cause the system to: display a GUI comprising: a first glucose profile based on data indicative of glucose levels received in the time period, wherein the first analyte profile comprises at least one glucose pattern determined for a time-of-day period; a first plurality of glucose metrics determined based on the data indicative of Docket No. A0130.0324.WO 15021WOO1 glucose levels received in the time period; and a measure of adherence for the medication dosing schedule during the time period.