Third Party Sample Monitoring

Abstract

Digital and graphical user interfaces for third party analyte monitoring applications are provided. For example, various embodiments of methods, systems, and interfaces for connection interfaces, alarm notification setting interfaces, and logbook interfaces in third party analyte monitoring applications are disclosed herein. Also described are various embodiments of interface improvements including enhanced visibility modes, interfaces for setting up the third party analyte monitoring application, and the like.

Description

Related Applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 143339, filed January 29, 2021, which is incorporated herein by reference in its entirety for all purposes. [Technical field]

[0002] The subject matter described herein generally relates to third-party analyte monitoring and related systems, methods, and devices. [Background technology]

[0003] Detection and / or monitoring of analyte levels, such as glucose, ketones, lactate, oxygen, hemoglobin A1C, etc., can be critical to the health of individuals with diabetes. Patients with diabetes can experience complications including loss of consciousness, cardiovascular disease, retinopathy, neuropathy, and nephropathy. Diabetic patients are generally required to monitor their glucose levels to ensure they are maintained within a clinically safe range, and this information may be used to determine if and / or when insulin is needed to lower glucose levels in the body, or when additional glucose is needed to raise glucose levels in the body.

[0004] A growing body of clinical data shows a strong correlation between frequency of glucose monitoring and glycemic control. However, despite this correlation, many individuals diagnosed with the diabetic condition do not monitor their glucose levels as frequently as they should due to a combination of factors including convenience, testing discretion, pain associated with glucose testing, and cost.

[0005] In order to increase patient compliance with a frequent glucose monitoring regimen, in vivo analyte monitoring systems may be utilized. In these systems, a sensor control device may be worn on the body of an individual requiring analyte monitoring. To increase the comfort and convenience of the individual, the sensor control device has a small form factor and may be applied by the individual using a sensor attachment device. The attachment process includes inserting at least a portion of a sensor that detects an analyte level in a bodily fluid within a layer of the user's body using an attachment device or insertion mechanism such that the sensor contacts the bodily fluid. The analyte monitoring system may also be configured to transmit analyte data, alerts, and alert information to another device where a third party, such as a caregiver, parent, or spouse, can review the data, receive alerts, and / or take appropriate responsive action.

[0006] However, despite their advantages, some third parties are reluctant to use sample monitoring systems for a variety of reasons, including the complexity and volume of data presented, the learning curve associated with the software and user interface for sample monitoring systems, and the overall lack of information presented and available.

[0007] Therefore, there is a need for a digital interface, a graphical user interface, and related systems, methods, and apparatus for third party analyte monitoring that enable a robust, easy to use, timely, and actionable response. Summary of the Invention [Means for solving the problem]

[0008] Digital and user interface embodiments for third party analyte monitoring are provided herein. In particular, systems, methods, and interfaces are described herein that relate to a analyte monitoring application on a third party display device for monitoring analyte-related information of one or more monitored users. The third party may be a caregiver, parent, spouse, or any other individual, group, or entity interested in monitoring one or more users equipped with a sensor controlled device.

[0009] According to one embodiment, various connection interfaces for third party analyte monitoring applications are provided. According to one embodiment, a single connection interface may include a profile card portion (with the monitored user's name, current analyte level value, and trend direction arrows) and an analyte graph portion (with analyte trend lines, shaded areas indicating target analyte ranges, and alarm threshold lines). In another embodiment, multiple connection interfaces are provided with multiple profile cards, each for a monitored user.

[0010] According to another embodiment, various alarm notification setting interfaces for a third party analyte monitoring application are provided. According to one aspect of the embodiment, the third party analyte monitoring application may be configured to display one or more alarm notification setting interfaces based on sensor type information for a monitored user's sensor control device received from a trusted computer system. In some embodiments, a first set of alarm notification setting interfaces, which may include, for example, glucose reading settings, may be displayed based on a determination that the monitored user has a sensor control device of a first sensor type. In some embodiments, a second set of alarm notification setting interfaces, which may include no recent data settings, may be displayed based on a determination that the monitored user has a sensor control device of a second sensor type.

[0011] According to another embodiment, various register interfaces for a third party analyte monitoring application are provided. According to one aspect of the embodiment, the third party analyte monitoring application may be configured to display a register interface including a plurality of register entries grouped by date for a predetermined time period. In many embodiments, the register interface may include a first register entry including an analyte level value, a trend direction arrow, and a time stamp. In some embodiments, a second register entry may include a textual indication that the monitored user's analyte level is above an upper reportable analyte level limit. In some embodiments, another register entry may include a low glucose alert or a high glucose alert. In yet other embodiments, the register entries may comprise entries manually entered by the monitored user.

[0012] Many of the embodiments provided herein are highly intuitive and easy-to-use improved GUIs or GUI features for third-party analyte monitoring applications, allowing quick access to important physiological information for monitored users. More specifically, these embodiments allow a third party to easily navigate and move between different user interfaces that can quickly show a third party various physiological conditions of a monitored user, without the third party having to go through the arduous task of sifting through large amounts of data. Some of the GUIs and GUI features and interfaces also provide versatility in allowing a third party to simultaneously monitor multiple users having different models and versions of sensor control devices. Other improvements and advantages are also provided. Various configurations of these devices are described in detail as merely example embodiments.

[0013] Other systems, devices, methods, features, and advantages of the subject matter described herein will become apparent to one of ordinary skill in the art upon examination of the following figures and detailed description. All such additional systems, devices, methods, features, and advantages are intended to be included within the description, be within the scope of the subject matter described herein, and be protected by the appended claims. These features of the embodiments should not be construed as limiting the appended claims in any way, unless there is an express recitation of the features in the claims. [Brief description of the drawings]

[0014] Details regarding both the structure and operation of the subject matter set forth herein may be apparent from a consideration of the accompanying drawings, in which like numerals refer to like parts. The parts in the drawings are not necessarily to scale, with emphasis instead being placed on illustrating the principles of the subject matter. Additionally, all figures are intended to convey concepts, and relative sizes, shapes, and other detailed attributes may be illustrated diagrammatically, but not precisely or precisely. [Figure 1] FIG. 1 is a system schematic diagram of an analyte monitoring system, comprising a sensor attachment device, a sensor control device, a reader device, a network, a trusted computer system, and a local computer system. [Figure 2A] FIG. 2 is a block diagram illustrating an embodiment of a reading device. [Figure 2B] FIG. 2 is a block diagram illustrating an embodiment of a sensor control device. [Figure 2C] FIG. 2 is a block diagram illustrating an embodiment of a sensor control device. [Figure 3A] FIG. 1 is a schematic diagram of a system for third-party analyte monitoring, the system including a sensor control device, a monitored user reader device, a network, a trusted computer system, and a third-party display device. [Figure 3B] FIG. 1 is a schematic diagram of another system for third-party analyte monitoring, the system including multiple sensor control devices, multiple monitored user readers, a network, a trusted computer system, and multiple third-party display devices. [Figure 4A]13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4B] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4C] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4D] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4E] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4F] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4G] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4H] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4I] 13 is an embodiment of a GUI for a analyte monitoring application for allowing and / or disallowing third party analyte monitoring. [Figure 4J] FIG. 1 is a flow diagram illustrating an embodiment of a method for setting up third-party analyte monitoring between a monitored user and a third party. [Figure 5A] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5B] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5C] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5D] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5E]13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5F] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5G] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5H] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5I] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5J] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5K] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5L] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5M] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5N] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5O] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5P] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5Q] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5R] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 5S] 13 is an embodiment of a GUI related to setting up a third-party analyte monitoring application. [Figure 6A]FIG. 1 is a flow diagram illustrating an embodiment of a method for displaying a connection interface of a third-party analyte monitoring application. [Figure 6B] 1 is an embodiment of a GUI for an analyte monitoring application involved in establishing a connection with a monitored user. [Figure 6C] 1 is an embodiment of a GUI for an analyte monitoring application involved in establishing a connection with a monitored user. [Figure 7] 1 illustrates an embodiment of a single connection interface for a third party analyte monitoring application, including an analyte graph portion. [Figure 8A] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8B] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8C] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8D] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8E] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8F] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8G] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8H] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8I] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 8J] 1 illustrates an embodiment of a connection interface for a third party analyte monitoring application, including connection interfaces for multiple monitored users. [Figure 9A] 13 is an additional embodiment of a connection interface for a third party analyte monitoring application. [Figure 9B] 13 is an additional embodiment of a connection interface for a third party analyte monitoring application. [Figure 9C] 13 is an additional embodiment of a connection interface for a third party analyte monitoring application. [Figure 9D] 13 is an additional embodiment of a connection interface for a third party analyte monitoring application. [Figure 9E] 13 is an additional embodiment of a connection interface for a third party analyte monitoring application. [Figure 10A] 1 is a GUI embodiment illustrating a register interface of a third party specimen monitoring application. [Figure 10B] 1 is a GUI embodiment illustrating a register interface of a third party specimen monitoring application. [Figure 10C] 1 is a GUI embodiment illustrating a register interface for a third party specimen monitoring application. [Figure 10D] 1 is a GUI embodiment illustrating a register interface of a third party specimen monitoring application. [Figure 10E] 1 is a GUI embodiment illustrating a register interface of a third party specimen monitoring application. [Figure 10F] 1 is a GUI embodiment illustrating a register interface of a third party specimen monitoring application. [Figure 10G] 1 is a GUI embodiment illustrating a register interface of a third party specimen monitoring application. [Figure 10H]1 is a GUI embodiment illustrating a register interface of a third party specimen monitoring application. [Figure 10I] FIG. 13 is a flow diagram illustrating an embodiment of a method for displaying an alert notification settings interface of a third-party analyte monitoring application. [Figure 11A] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 11B] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 11C] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 11D] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 11E] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 11F] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 11G] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 11H] 13 illustrates an embodiment of an alert notification configuration interface for a third party analyte monitoring application. [Figure 12A] 13 is an additional embodiment of a glucose reading notification setting interface for a third party analyte monitoring application. [Figure 12B] 13 is an additional embodiment of a glucose reading notification setting interface for a third party analyte monitoring application. [Figure 13A] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 13B] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 13C] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 13D] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 13E] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 13F] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 13G] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 13H] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 14A] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 14B] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 14C] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 14D] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 14E] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 14F] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 14G] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15A] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15B] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15C]13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15D] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15E] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15F] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15G] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 15H] 13 is an additional embodiment of an alert notification setting interface for a third party analyte monitoring application. [Figure 16A] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 16B] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 16C] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 16D] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 16E] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 16F] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 16G] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 16H] 13 is an embodiment of an alert notification interface for a third party analyte monitoring application. [Figure 17A] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17B]1 is an embodiment of a third party analyte monitoring application interface. [Figure 17C] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17D] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17E] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17F] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17G] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17H] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17I] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17J] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17K] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17L] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17M] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17N] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 17O] 1 is an embodiment of a third party analyte monitoring application interface. [Figure 18A] 1 is an embodiment of a menu interface for a third party analyte monitoring application. [Figure 18B] 13 is another interface embodiment of a third party analyte monitoring application. [Figure 18C] 13 is another interface embodiment of a third party analyte monitoring application. [Figure 19A] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19B] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19C] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19D] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19E] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19F] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19G] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19H] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19I] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19J] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19K] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19L] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19M] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. [Figure 19N] 1 illustrates an embodiment of an interface in enhanced visibility mode for a third-party analyte monitoring application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Before describing the present subject matter in detail, it is to be understood that the present disclosure is not limited to particular embodiments described, 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. The scope of the present disclosure is limited only by the appended claims.

[0016] As used herein and in the appended claims, the English singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0017] The disclosures discussed herein are provided solely for their disclosure prior to the filing date of the present application. The disclosure should not be construed as an admission that the invention is not entitled to antedate such publication by prior disclosure. Additionally, the publication dates provided may be different from the actual publication dates, which need to be independently confirmed.

[0018] In general, embodiments of the present disclosure include GUIs and digital interfaces for third-party analyte monitoring, and associated systems, methods, and devices. Thus, many embodiments include in vivo analyte sensors that are structurally configured such that at least a portion of the sensor is or can be placed within the body of a monitored user to obtain information about at least one analyte in the body. However, it should be noted that the embodiments described herein may be used with in vivo analyte monitoring systems that have in vitro capabilities as well as purely in vitro or ex vivo analyte monitoring systems (including completely non-invasive systems).

[0019] Also, for each and every embodiment of the methods disclosed herein, systems and devices capable of performing each of these embodiments are included within the scope of the present disclosure. For example, embodiments of sensor control devices, readers, displays, local computer systems, and trusted computer systems are disclosed, which may include one or more sensors, analyte monitoring circuitry (e.g., analog circuitry), memory (e.g., for storing instructions), power sources, communication circuitry, transmitters, receivers, processors and / or controllers (e.g., for executing instructions) that may perform or enable the performance of any and all method steps.

[0020] As mentioned above, embodiments described herein provide improved GUIs for third party analyte monitoring applications, e.g., resident in the memory of a caregiver's reader. These GUIs are useful, easy to use, and allow fast access to physiological information of a monitored user. According to some embodiments, methods and interfaces are provided for a connection interface, e.g., in a third party analyte monitoring application. The connection interface may be configured to provide real-time (or near real-time) analyte information and an interactive interface. According to other embodiments, methods and interfaces are provided for an alarm notification setting interface for a third party analyte monitoring application with certain features available based on the sensor type used by the monitored user. In this regard, the third party analyte monitoring application may be flexible and robust to simultaneously support multiple monitored users with different types and versions of sensor control devices. Another improved digital and user interface for an analyte monitoring software application is described.

[0021] Collectively and individually, these methods, systems, and digital and user interfaces improve the utility and flexibility of third party analyte monitoring by enabling caregivers to receive improved information and interfaces regarding the status of a monitored user, and by improving the alarm capabilities of the analyte monitoring system. Other improvements and advantages are also provided. Various configurations of these devices are described in detail as merely example embodiments.

[0022] However, before describing these aspects of the embodiments in detail, it is desirable to first describe examples of devices that may be present, for example, in an in vivo analyte monitoring system, and examples of their operation, all of which may be used in conjunction with the embodiments described herein.

[0023] Various types of in vivo analyte monitoring systems exist. For example, a continuous analyte monitoring system (or continuous glucose monitoring system) can transmit data from a sensor controller to a reader automatically and continuously, e.g., according to a schedule without prompting. As another example, a flash analyte monitoring system (or flash glucose monitoring system or simply flash system) can transfer data from the sensor controller in response to a scan or data request by the reader, e.g., using near field communication (NFC) or radio frequency identification (RFID) protocols. In vivo analyte monitoring systems may also operate without the need for finger stick calibration.

[0024] In vivo analyte monitoring systems may be distinguished from ex vivo systems, which contact a biological sample outside the body and typically include a meter having a port for receiving an analyte test strip carrying a bodily fluid of the monitored user that can be analyzed to determine the monitored user's blood glucose level.

[0025] An in-vivo monitoring system may include a sensor located within the body for contacting and detecting an analyte level in a bodily fluid of a monitored user. The sensor may be part of a sensor control device attached to the body of the monitored user that contains electronic circuitry and a power source to enable and control analyte detection. The sensor control device and variations thereof may also be referred to as a "sensor control unit," "body-attached electronics" device or unit, "body-attached" device or unit, or "sensor data communication" device or unit, etc.

[0026] An in-vivo monitoring system may also include a device that receives, processes, and / or displays the sensed analyte data from the sensor control device in any number of formats to the monitored user or a third party interested in monitoring the monitored user's analyte levels (e.g., a caregiver, parent, spouse, or health care provider). This device and variations thereof may be referred to as a "handheld reader," "reader" (or simply "reader"), "handheld electronic device" (or simply "handheld"), "portable data processing" device or unit, "data receiver," "receiving" device or unit (or simply "receiver"), or "remote" device or unit, "display," or the like. Other devices, such as personal computers, have also been utilized with or incorporated into in-vivo and in-vivo monitoring systems.

[0027] Embodiments of an In-Vivo Analyte Monitoring System FIG. 1 is a conceptual diagram illustrating an embodiment of an analyte monitoring system 100, which includes a sensor attachment device 150, a sensor control device 102, and a reader device 120. The sensor attachment device 150 may be used to deliver the sensor control device 102 to a monitoring location on the skin of a monitored user. The sensor 104 is maintained in place for a period of time by an adhesive patch 105. The sensor control device 102 is further described in FIGS. 2B and 2C and may communicate with the reader device 120 via a communication path 140 using wired or wireless technology. Exemplary wireless protocols include Bluetooth, Bluetooth low energy (BLE, BTLE, Bluetooth SMART, etc.), NFC, etc. The monitored user may view and use applications installed in the memory of the reader device 120 using a screen 122 (which may be a touch screen in many embodiments) and input 121. The device battery of the reader device 120 may be recharged using a power port 123. Although only one reader 120 is shown, the sensor controller 102 may communicate with multiple readers 120. Each reader 120 may communicate with and share data with each other. Further details of the reader 120 are described below with respect to FIG. 2A. The reader 120 may communicate with a local computer system 170 via communication path 141 using a wired or wireless communication protocol. The local computer system 170 may include one or more of a laptop, desktop, tablet, phablet, smartphone, smart watch, wearable electronic device, health tracker, set-top box, video game console, or other computing device, and the wireless communication may include any applicable wireless network protocol including Bluetooth, Bluetooth Low Energy (BTLE), Wi-Fi, etc. Similar to the way the reader 120 may communicate with the network 190 via communication path 142 using a wired or wireless communication protocol as described above, the local computer system 170 may communicate with the network 190 via communication path 143. Network 190 may be any network, such as a private network, a public network, a local area network, or a wide area network.The trusted computer system 180 may include a cloud-based platform or server, enabling authentication services, secure data storage, and report generation, and may communicate with the network 190 via communication path 144 using wired or wireless technology. Additionally, while Figure 1 depicts the trusted computer system 180 and the local computer system 170 in communication with a single sensor controller 102 and a single reader 120, one skilled in the art will appreciate that the local computer system 170 and / or the trusted computer system 180 may communicate with multiple readers and sensor controllers, respectively, using wired or wireless communication.

[0028] Reading Device Embodiments 2A is a block diagram illustrating an embodiment of a reader 120, which in some embodiments may be a smartphone. In some embodiments, the reader 120 may include a display 122, an input component 121, and a processing core 206 including a communication processor 222 coupled to a memory 223 and an application processor 224 coupled to a memory 225. It may also include another memory 230, an RF transceiver 228 having an antenna 229, and a power source 226 having a power management module 238. In addition, the reader 120 may also include a multi-function transceiver 232 that may include wireless communication circuitry and be configured to communicate via Wi-Fi, NFC, Bluetooth, BTLE, and GPS using an antenna 234. As one skilled in the art will appreciate, these components are electrically and communicatively coupled to form a functional device.

[0029] An embodiment of a sensor control device 2B and 2C are block diagrams illustrating an embodiment of a sensor controller 102 having an analyte sensor 104 and sensor electronics 160 (including analyte monitoring circuitry). The sensor electronics may contain most of the processing power to make the final result data suitable for display to a monitored user or third party. FIG. 2B illustrates a single semiconductor chip 161, which may be a custom application specific integrated circuit (ASIC). Certain high level functional units are shown within the ASIC 161, including an analog front end (AFE) 162, a power management (or control) circuit 164, a processor 166, and a communication circuit 168 (which may be a transmitter, receiver, transceiver, passive circuitry, etc., depending on the communication protocol). In this embodiment, both the AFE 162 and the processor 166 are used as analyte monitoring circuitry, although in other embodiments, either circuitry may perform the analyte monitoring function. The processor 166 may include one or more processors, microprocessors, controllers, and / or microcontrollers (each of which may be distributed across (and be part of) separate chips or multiple different chips).

[0030] The memory 163 may also be included in the ASIC 161, shared by the various functional units present in the ASIC 161, or distributed among two or more of them. The memory 163 may also be a separate chip. The memory 163 may be a volatile and / or non-volatile memory. In this embodiment, the ASIC 161 is coupled to a power source 172, which may be a coin cell or the like. The AFE 162 interfaces with and receives measurement data from the in vivo analyte sensor 104 and outputs the data in digital form to the processor 166, which processes the data to obtain final result glucose individual values ​​and trend values, etc. This data may be provided to the communication circuitry 168 for transmission via the antenna 171 to the reader 120 (not shown), where resident software applications require minimal additional processing to display the data. For example, according to some embodiments, current glucose values ​​may be transmitted from sensor controller 102 to reader 120 every minute, and historical glucose values ​​may be transmitted from sensor controller 102 to reader 120 every five minutes.

[0031] In some embodiments, data obtained from the sensor control device 102 may be stored in the reader 120. According to one aspect of some embodiments, such data may include the model number and serial number of the sensor control device 102, as well as information regarding the status of the sensor control device 102, market code, or network address. In some embodiments, such data may also include error events detected by the sensor control device 102. Additionally, in some embodiments, either or both of the current glucose value and the historical glucose value may include one or more time stamps (e.g., factory time, UTC time, user local time based on time zone, and current time zone).

[0032] In some embodiments, the sensor controller 102 may load data into the reader 120 when the reader 120 re-establishes communication with the sensor controller 102 if the reader 120 is not in communication with the sensor controller 102 (e.g., the reader 120 is out of wireless communication range, is powered off, or is otherwise unable to communicate with the sensor controller 102). According to some embodiments, the data that may be loaded may include, but is not limited to, current and historical glucose values ​​and error events. Further details regarding data loading may be found in U.S. Pat. No. 1,0820,842 and U.S. Patent Application Publication No. 2021 / 0378601, both of which are incorporated herein by reference in their entireties.

[0033] According to some embodiments, each current and / or historical glucose value obtained from the sensor control device 102 may be further verified by the reader 120, for example, by performing a CRC integrity check to ensure the data was transferred accurately. In some embodiments, a data quality mask may be checked, for example, for the current and / or historical glucose values ​​to ensure the readings are accurate and displayed by the reader 120 as valid readings.

[0034] According to another aspect of some embodiments, the reader 120 may include a database for storing any or all of the above data. In some embodiments, the database may be configured to retain data for a predetermined period of time (e.g., 30 days, 60 days, 90 days, 6 months, 1 year, etc.). According to some embodiments, the database may be configured to delete the data after it is uploaded to the cloud server. In other embodiments, the database may be configured for a clinical situation where data is retained for a longer period of time (e.g., 1 year) than in a non-clinical situation. In addition to the above data (e.g., current and / or historical glucose values, error events, etc.), the reader 120 database may also store user configuration information (e.g., login ID, notification settings, regional settings, and other settings) and application configuration information (e.g., cloud settings, URLs for uploading data and / or error events, version information, etc.). The database may be encrypted to prevent a user from directly viewing the data contents even when the operating system of the reader 120 is not functioning properly.

[0035] In some embodiments, to conserve power and processing resources of the sensor controller 102, the digital data received from the AFE 162 may be transmitted to the reader 120 (not shown) with minimal or no processing. In other embodiments, the processor 166 may be configured to generate certain predefined data types (e.g., current glucose value, historical glucose value) for storage in memory 163 or transmission to the reader 120 (not shown) and identify certain alarm conditions (e.g., sensor fault conditions), while other processing and alarm functions (e.g., high / low glucose threshold alarms) may be performed by the reader 120. Those skilled in the art will appreciate that the methods, functions, and interfaces described herein may be performed in whole or in part by processing circuitry of the sensor controller 102, the reader 120, the local computer system 170, or the trusted computer system 180.

[0036] FIG. 2C is similar to FIG. 2B, but instead includes two separate semiconductor chips 162 and 174, which may be packaged together or separately. AFE 162 resides in ASIC 161. Processor 166 is integrated with power management circuitry 164 and communication circuitry 168 on chip 174. AFE 162 may include memory 163, and chip 174 includes memory 165, which may be separate or distributed. In one embodiment, AFE 162 is combined with power management circuitry 164 and processor 166 on one chip, and communication circuitry 168 is on another chip. In another embodiment, both AFE 162 and communication circuitry 168 are on one chip, and processor 166 and power management circuitry 164 are on another chip. Note that other chip combinations are possible, including three or more chips, each performing a different function or sharing one or more functions for fail-safe redundancy.

[0037] Embodiments of a System for Third Party Analyte Monitoring Embodiments of systems, methods, and devices for analyte monitoring systems are described. First, the term "third party" may refer to any person, entity, or person other than the monitored user who is interested in monitoring the analyte levels of the monitored users and information thereabout. In some embodiments, for example, the third party may be a caregiver, parent, or spouse, and the monitored user may be an elder, child, spouse, or patient. According to one aspect, the embodiments described herein include systems, methods, and devices similar to those described with respect to the analyte monitoring system 100, but also include one or more secondary displays used by the third party to monitor the analyte levels of one or more monitored users. The third party secondary displays may include the same or similar components as the monitored user's reader device 120, including one or more processors coupled to a memory for storing instructions. The instructions, when executed by the one or more processors, cause the processors to execute a third party analyte monitoring application configured to monitor the analyte levels of one or more monitored users.

[0038] FIG. 3A is a conceptual diagram illustrating an embodiment of a system 100-A that can communicate analyte data and other related information of a monitored user to a third party. According to one aspect of the embodiment, the system 100-A shares several similarities with the analyte monitoring system 100 described with respect to FIG. 1. In particular, the system 100-A can include a sensor control device 102 (worn by the monitored user 25) that communicates wirelessly with a reader 120-1 via a communication link 140. According to various embodiments, the sensor control device 102 can include communication circuitry configured to wirelessly communicate data with the reader 120-1, for example, via a Bluetooth communication protocol or an NFC protocol. Also, according to some embodiments, the reader 120-1 can be a smartphone, a smartwatch, a wearable electronic device, a dedicated receiver, or a glucose meter. Although one reader 120-1 is depicted in FIG. 3A, the monitored user 25 can have multiple readers (e.g., smartphones, glucose meters, dedicated receivers, etc.) that can each be used to obtain analyte data from the sensor control device 102. Additionally, the reader 120-1 can wirelessly communicate with the trusted computer system 180 over the network 190. In some embodiments, the reader 120-1 can include communication circuitry configured to wirelessly communicate data with the trusted computer system 180 via an 802.11x communication protocol or a cellular communication protocol.

[0039] 3A, the analyte monitoring system 100-A further includes a secondary display device 120-2 carried by a third party 50. As previously discussed, the third party 50 may be a caregiver, parent, spouse, or any other individual, group, or entity interested in monitoring the analyte levels of the monitored user 25. The secondary display device 120-2 may include communications circuitry configured to wirelessly communicate data with a trusted computer system 180 via an 802.11x or cellular communications protocol over a network 190. According to many embodiments, the network 190 may be the Internet.

[0040] As previously discussed, in many embodiments, the sensor control device 102 worn by the monitored user 25 includes an analyte sensor configured to be disposed at least partially within the body of the monitored user 25 to sense a biological analyte level in the monitored user 25. The sensor control device 102 can wirelessly communicate data indicative of the analyte level in the monitored user 25 to a reader 120-1, which can wirelessly communicate the data to a trusted computer system 180.

[0041] According to another aspect of the embodiment, the secondary display device 120-2 (which may comprise a smartphone, a smartwatch, a wearable electronic device, or a dedicated receiver) may be configured to receive data indicative of the analyte level of the monitored user 25 (wirelessly communicated to the secondary display device 120-2 via the network 190 by the trusted computer system 180). The secondary display device 120-2 may also include a third party analyte monitoring software application stored in a memory of the secondary display device 120-2. The third party analyte monitoring software application may be configured to display the analyte information of the monitored user 25 to a third party 50.

[0042] In this manner, the third party 50 may receive timely information regarding analyte information of the monitored user 25. In some embodiments, a third party analyte monitoring software application installed on the third party's display device 120-2, for example, may be configured to receive alerts related to the analyte levels of the monitored user 25.

[0043] FIG. 3B is a conceptual diagram illustrating an embodiment of a system 100-B that can communicate analyte data and other related information of one or more monitored users to one or more third parties. According to one aspect of the embodiment, the system 100-B shares many similarities with the systems 100 and 100-A described with respect to FIGS. 1 and 3A. In particular, FIG. 3B illustrates a system 100-B that can communicate analyte data and other related information of one or more monitored users (25A, 25B, 25N) to one or more third parties (50A and 50B). In some embodiments, the system 100-B can include one or more sensor control devices 102A, 102B, 102N (worn by the monitored users 25A, 25B, and 25N, respectively) that are in wireless communication with corresponding reading devices (e.g., 120-1A, 120-1B, and 120-1N, respectively). Although only one reading device is depicted for each monitored user, one skilled in the art will appreciate that each monitored user may have multiple reading devices (e.g., smartphones, glucose meters, dedicated receivers) (each of which may be configured to receive analyte data from a corresponding sensor control device).

[0044] According to another aspect of many embodiments, each sensor control device (e.g., 102A, 102B, 102N) may include communication circuitry configured to wirelessly communicate with a corresponding reader device (e.g., 120-1A, 120-1B, 120-1N), for example, according to a Bluetooth, Bluetooth Low Energy, or NFC protocol. Also, according to some embodiments, each reader device (e.g., 120-1A, 120-1B, 120-1N) may be a smartphone, a smartwatch, a wearable electronic device, a dedicated receiver, or a glucose meter, and may wirelessly communicate with a trusted computer system 180 over a network 190. In some embodiments, each reader device (e.g., 120-1A, 120-1B, 120-1N) may include communication circuitry configured to wirelessly communicate data with a trusted computer system 180 according to an 802.11x communication protocol or a cellular communication protocol.

[0045] Still referring to FIG. 3B, system 100-B further includes one or more secondary display devices (e.g., 120-2A, 120-2B) carried by one or more third parties (50A, 50B), respectively. As previously mentioned, each third party (e.g., 50A, 50B) may be a caregiver, parent, spouse, or any individual, group, or entity interested in monitoring the analyte levels of one or more monitored users (e.g., 25A, 25B, 25N). Each secondary display device (e.g., 120-2A, 120-2B) may further include communication circuitry configured to wirelessly communicate data with a trusted computer system 180 via a 802.11x or cellular communication protocol over a network 190. According to many embodiments, network 190 may be the Internet.

[0046] According to one aspect of the embodiment, each sensor control device (e.g., 102A, 102B, 102N) includes an analyte sensor configured to be disposed at least partially within the body of a monitored user (e.g., 25A, 25B, 25N). Each sensor control device (e.g., 102A, 102B, 102N) can wirelessly communicate data indicative of the analyte level of the monitored user (e.g., 25A, 25B, 25N) to a corresponding reader (e.g., 120-1A, 120-1B, 120-1N), which can wirelessly communicate the data to a trusted computer system 180. According to another aspect of the embodiment, each secondary display device (e.g., 120-2A, 120-2B) can include a third party analyte monitoring application stored in a memory of the secondary display device and configured to be operated by a third party (e.g., 50A, 50B). Additionally, each sub-display device (e.g., 120-2A, 120-2B) may be a smartphone, a smartwatch, a wearable electronic device, or a dedicated receiver and may be configured to receive data indicative of the analyte level of a monitored user (e.g., 25A, 25B, 25N) that is wirelessly communicated by trusted computer system 180 over network 190 to a third party display device (e.g., 120-2A, 120-2B).

[0047] According to some embodiments, the sensor control devices 102A, 102B, and 102N may comprise a first type sensor control device, a second type sensor control device, and a third type sensor control device, respectively. In some embodiments, for example, the first type sensor control device may be configured to transmit data indicative of the monitored user's analyte level according to an NFC protocol, and the second type sensor control device may be configured to transmit data indicative of the monitored user's analyte level according to a Bluetooth or Bluetooth low energy communication protocol. In other embodiments, the first type sensor control device may be configured to transmit data indicative of the monitored user's analyte level and "trigger" an alarm (i.e., an alarm indication generated according to settings set by the monitored user). The second type sensor control device may be configured to transmit data indicative of the monitored user's analyte level (and optionally the monitored user's alarm settings), and a determination of an alarm condition (e.g., whether an analyte threshold is exceeded) may be made by the trusted computer system or the secondary display device, or both. Additionally, the third type sensor control device may be an unknown or incompatible sensor control device. As described in further detail below, the third party analyte monitoring software application installed on the third party display device (120-2A or 120-2B) may be configured to present different types of alerts, an alert setting interface, and other features and GUIs based on the type of sensor control device of the monitored user. Additional details regarding the different types of alerts for third party analyte monitoring can be found in U.S. Patent Application Serial No. 17 / 478,447, which is incorporated herein by reference in its entirety.

[0048] In this manner, each third party (e.g., 50A, 50B) may receive timely information regarding analyte information for one or more monitored users (e.g., 25A, 25B, 25N). In some embodiments, a third party analyte monitoring software application installed on, for example, the third party's display device 120-2A may be configured to receive alerts related to the analyte levels of monitored users 25A and 25B. In other embodiments, a third party analyte monitoring software application installed on, for example, the third party's display device 120-2B may be configured to receive data indicative of the analyte levels of monitored users 25A, 25B, and 25N. Similarly, in some embodiments, the analyte monitoring software installed on, for example, the monitored user's reader device 120-1A may be configured to share data indicative of the analyte level of monitored user 25A with third party 50A (but not 50B). One of ordinary skill in the art will appreciate that other combinations and permutations are possible and are fully within the scope of the present disclosure.

[0049] Examples of digital and graphical user interfaces for third-party specimen monitoring Embodiments of a digital interface and GUI for third-party analyte monitoring and related systems, methods, and devices are described. At the outset, one skilled in the art will appreciate that the GUIs and related methods described herein comprise instructions stored in memory of the reader 120, the secondary display 120-2, the local computer system 170, the trusted computer system 180, and / or any other device or system that is part of or in communication with the analyte monitoring system 100, 100-A, or 100-B. These instructions, when executed by one or more processors of the reader 120, the secondary display 120-2, the local computer system 170, the trusted computer system 180, or any other device or system of the analyte monitoring system 100, 100-A, or 100-B, may cause those processors to perform the method steps and / or output the GUIs described herein. One skilled in the art will appreciate that the GUIs described herein may be stored as instructions in the memory of a single centralized device or may be distributed across multiple individual devices at geographically dispersed locations.

[0050] An embodiment of a GUI for permitting / prohibiting third-party specimen monitoring 4A-4I are illustrative embodiments of GUIs for enabling / disabling and configuring third party analyte monitoring for an analyte monitoring software application. Initially, the GUIs described in this section relate to interfaces for an analyte monitoring software application stored in the memory of a monitored user's reader device. (In contrast, many of the other GUIs and interfaces described below relate to interfaces for third party analyte monitoring applications stored in the memory of a third party's secondary display device.) 4A, GUI 401 depicts an interface for an analyte monitoring software application that allows a monitored user to configure, enable, or disable third-party analyte monitoring. According to some embodiments, GUI 401 includes a button 402 that, when pressed, causes another interface to be displayed that allows the monitored user to review and / or configure settings related to third-party analyte monitoring. In some embodiments, GUI 401 may also include other buttons or links that cause other configuration interfaces or other features of the analyte monitoring software application to be displayed.

[0051] 4B is another GUI 403 depicting an interface for a analyte monitoring software application that allows a monitored user to enter information about a third party with whom the monitored user would like to share their analyte data. In some embodiments, the GUI 403 may include a first name field 404, a last name field 406, and an email address field 408, as well as an "Add" button 410 that, when pressed, generates an invitation to the third party.

[0052] Referring now to Figure 4C, GUI 411 depicts another interface for the analyte monitoring software application, which includes a third party label 412 showing the name and email address of a recently added third party, an invitation status 414 indicating that an invitation has been sent to the third party, a remove link 416 allowing the monitored user to prevent sharing of analyte data with a particular third party, and a "Done" button 418 allowing the monitored user to return to the previous screen (e.g., GUI 401 or 421). Figure 4D depicts GUI 411 in a different state than Figure 4C, where a "Resend invitation" link 420 is provided in place of the invitation status. Also, when remove link 416 is selected, a connection remove modal 432 is displayed as shown in Figure 4I.

[0053] Figure 4E is another GUI 421 depicting an alternative interface for the analyte monitoring software application that includes a pending connections portion 422 that lists any pending connections (e.g., the third party has not yet responded to the invitation) and an "Add Connection" button that, when pressed, returns the monitored user to GUI 403. Figure 4F depicts a different state of GUI 421 from Figure 4E that includes the pending connections described above and a connections portion 426 that lists all established connections (e.g., if the third party has accepted the invitation to share the monitored user's analyte data).

[0054] Referring now to Figure 4G, the GUI 411 is depicted in a different state than the interface depicted in Figures 4C and 4D. In particular, Figure 4G depicts the GUI 411 after the third party has accepted the invitation and a connection has been established. In some embodiments, the GUI 411 also includes a stop sharing link 428 that, when pressed, displays a stop sharing modal 430 as depicted in Figure 4H. According to one aspect of the embodiment, the stop sharing modal 430 allows the monitored user to stop sharing analyte data (and other related information) with the third party.

[0055] Those skilled in the art will understand that although each individual graphical element (e.g., modals, buttons, and links) is described in terms of a particular interface, each and every one of these elements may be rearranged in various configurations within a single interface or combined with other elements in different interfaces to achieve the same functions and / or results, and that such other combinations and / or arrangements of graphical elements and interfaces are fully within the scope of the present disclosure.

[0056] GUI embodiment for setting up a third-party analyte monitoring application FIG. 4J is a flow diagram illustrating an embodiment of a method 450 for setting up a third-party analyte monitoring application (also referred to as a third-party analyte monitoring software application or third-party analyte monitoring app) to enable third-party analyte monitoring by, for example, a caregiver, parent, or spouse. In step 452, the monitored user sends an invitation to the third party to share analyte data and other information. According to some embodiments, the monitored user can send the invitation via a analyte monitoring software application (as described with respect to FIGS. 4A-4H) resident on the monitored user's reading device. In other embodiments, the monitored user can send the invitation to the third party through a web-based interface (e.g., a web browser) separate from the analyte monitoring application. In many embodiments, the invitation can consist of an email received by the third party that includes a link to download and install the third-party analyte monitoring application. In step 454, the third-party analyte monitoring application is downloaded and installed on the third party's display device (also referred to as a secondary display device) if the third party has not already done so. Next, in step 456, the third-party analyte monitoring application is launched on the third party's display device. At step 458, the third-party analyte monitoring application prompts the third party to create a user account or, if the third party already has a user account, prompts the third party to log in to a trusted computer system (e.g., a cloud-based server) through the third-party analyte monitoring application (see, e.g., Figures 5A-5Q). Once the third party has successfully logged in, at step 460, the third party receives notification through the third-party analyte monitoring application that the monitored user wishes to share their analyte data, and the third party is prompted to accept the request (see, e.g., Figure 6C). Once the third party accepts the request, at step 462, the third-party analyte monitoring application begins receiving and displaying the monitored user's analyte levels and other relevant information on the third party's display device (see, e.g., Figures 7, 8A-8J, and 9A-9C).

[0057] An embodiment of a GUI for setting up a third-party analyte monitoring application is described below. One of ordinary skill in the art will appreciate that the interfaces described in this section may be used in combination with any of the other embodiments described herein, including but not limited to the method 450 and the interfaces described with respect to FIGS. 4A-4I.

[0058] 5A, a GUI 501 depicts the initial interface that is displayed when a third-party analyte monitoring application is launched. According to one aspect of an embodiment, the GUI 501 includes a "Get Started" button 502 for first-time third-party users and a "Login" button 504 if the third party already has a user account.

[0059] 5B, GUI 505 depicts an introductory interface that is displayed when a third party selects the "Get Started" button 502 on GUI 501. As shown in FIG. 5B, GUI 505 may include informational text about the third party analyte monitoring application and a "Create an Account" button 506.

[0060] 5C, GUI 507 depicts a region setting interface that is displayed when a third party selects the "Create Account" button 506 in GUI 505. As shown in FIG. 5C, GUI 507 may include a pull-down menu 508, a dial, or a free text field in which the third party may enter a country or region. According to some embodiments, certain features of the third party analyte monitoring application may be enabled or disabled based on the country or region entered by the third party. In other embodiments, the units of measure ("UOM") displayed in various interfaces may also be dependent on the country or region entered by the third party.

[0061] Once the country or region is entered using menu 508 and the "Continue" button 510 is selected, the third-party analyte monitoring application displays an End User License Agreement ("EULA") 511 and a Privacy Policy 513, each of which includes modals 512, 514 (depicted in Figures 5D and 5E) that prompt the third party to accept the terms of the respective agreement. In some embodiments, the third-party analyte monitoring application will not proceed beyond these interfaces unless the third party accepts the terms of the EULA or Privacy Policy.

[0062] Referring now to FIG. 5F, GUI 511 depicts an interface of a third-party analyte monitoring application that allows a third party to create a user account. According to one aspect of some embodiments, GUI 511 includes a number of fields 518 where the third party can enter the information required to create a user account, such as first name, last name, birth date, email address, password, and password confirmation. Once the third party enters the requested information into the number of fields 518 and selects the "continue" button 520, the third party is prompted to confirm the entered email address (as shown in GUI 521 of FIG. 5G). GUI 521 also includes a "resend" link in case the third party inadvertently deletes or loses the original confirmation email. (FIG. 5H depicts an embodiment of an email message that includes a confirmation link 526 that confirms the third party's new account. Although FIG. 5H shows an email message addressed to the user by a "first name" field followed by a "last name" field, one skilled in the art will appreciate that the email message may be addressed to the user in other ways. According to some embodiments, the email message may be addressed to the user by "last name" followed by "first name" if the user is in a given country, region, or market.) According to another aspect of the embodiment, once the verification process is complete and the third party selects the “Continue” button 524 (FIG. 5G) of GUI 521, a series of information and settings interfaces, FIGS. 5I-5M, are displayed to the third party. In some embodiments, for example, GUI 527 (FIG. 5I) may be displayed initially after the account is created, and includes a confirmation message that the third party's account was successfully created. Similarly, GUI 529 (FIG. 5J) may display a message that the third party analyte monitoring application requires an internet connection (e.g., via a Wi-Fi or cellular connection) to function properly. Also, GUI 531 (FIG. 5K) may display instructions to the third party to enable notification permissions through the display device's operating system. Next, modal 534 is presented to the third party (as shown in GUI 533 of FIG. 5L) to allow the third party to enable the required notification permissions. In some embodiments, the third party analyte monitoring application may be configured to be inoperable or partially operable until notification permissions are properly enabled. Finally, as shown in FIG. 5M, GUI 535 may display a warning that the third party analyte monitoring application should not be used for therapeutic or dosing decisions.

[0063] Returning to Figures 5A and 5F, if the third party already has an account, they can select "Login" button 504 or link 516 (as shown in Figure 5N), which may cause a login GUI 537 to appear. According to one aspect of the embodiment, the third party can log into their user account by entering their email address and password in login field 538. Alternatively, if the third party has forgotten their password, they can select "Forgot Password" link 540, which causes a series of password reset interfaces to appear (see, e.g., GUIs 541 and 543 in Figures 5O, 5P, and 5Q).

[0064] According to another aspect of the embodiment, once the third party has successfully logged in, a “New Features” interface 545, shown in FIG. 5R, may be displayed. In some embodiments, the “New Features” interface 545 may only be displayed if the user has not logged in since the last update of the third party analyte monitoring application. In other embodiments, the “New Features” interface 545 may be displayed according to a predefined timeline. In some embodiments, the “New Features” interface 547 may include a safety banner notification 548 to further emphasize that the third party analyte monitoring application is not intended for therapeutic decision making. In some embodiments, the safety banner notification 548 may be configured to auto-dismiss after a predetermined period of time (e.g., 5 seconds, 15 seconds, 30 seconds, etc.). In other embodiments, the safety banner notification 548 may be configured to remain on the interface 547 until the third party manually clears the notification 548 so that the third party has sufficient time to view and read the message. Although the safety banner notification 548 is shown with respect to the "New Features" interface, the same or a similar safety banner notification 548 may be temporarily overlaid on any of the interfaces described herein based on one or more different conditions, such as upon login, or when a third party analyte monitoring application is brought to the foreground, or when a particular, predefined interface is displayed. Additionally, one of ordinary skill in the art will appreciate that while the banner notification 548 depicted in FIG. 5S pertains to treatment decisions, other urgent or important messages may be displayed and are fully within the scope of the present disclosure.

[0065] Embodiments of a Connection Interface for Third Party Analyte Monitoring Applications An embodiment of a connectivity interface for a third-party analyte monitoring application is described. Initially, a connectivity interface refers to an interface for presenting data indicative of analyte levels of one or more monitored users. Those skilled in the art will also appreciate that the interfaces described herein may include instructions stored in a memory of a secondary display device (e.g., a smartphone, a smartwatch, a wearable electronic device, a dedicated receiver, etc.) owned by a third party.

[0066] FIG. 6A is a flow diagram illustrating an embodiment of a method 600 of displaying a connection interface of a third-party analyte monitoring application. In step 602, the third-party analyte monitoring application is launched on a secondary display device owned by the third party. As previously described, the secondary display device may comprise a smartphone, a smartwatch, a wearable electronic device, or a dedicated receiver. In step 604, the third party logs in via the third-party analyte monitoring application with their account and password. In some embodiments, the third-party analyte monitoring application passes the third party's credentials to a cloud-based server for authentication. In other embodiments, the third party's user account and password may be authenticated locally by the third-party analyte monitoring application itself or by the secondary display device. In step 606, it is determined how many connections are active for the third party based on the third party's user account. If the third party has not yet established any connections, in step 608, a no connection interface is displayed (see, e.g., FIG. 6B). If the third party has one connection, a single connection interface is displayed in step 610 (see, e.g., FIG. 7). If the third party has multiple connections, a multiple connection interface is displayed on the secondary display device in step 612 (see, e.g., FIG. 8A).

[0067] With reference to FIG. 6B, GUI 651 illustrates an embodiment of a no connection interface displayed by a third-party analyte monitoring application when a third party does not have an active connection. In many embodiments, GUI 651 includes informational text indicating that there is not yet a connection, and may further include a "Learn More" link that provides additional instructions and / or information regarding adding a connection. FIG. 6C illustrates GUI 651 in another state where the monitored user has requested a third party to share analyte data, in which case modal 652 is displayed to the third party. According to some embodiments, the third party can accept or reject the request to share via a respective button in modal 652. In other embodiments, modal 652 may be informational only, and the connection may be established automatically.

[0068] Referring now to FIG. 7, a GUI 701 illustrates an embodiment of a single connection interface displayed by a third-party analyte monitoring application. According to one aspect of the embodiment, the GUI 701 may include a menu glyph 702, a settings glyph 704, a profile card portion 710, an analyte graph portion 720, and a logbook button 730. In many embodiments, the profile card portion 710 may further include a connection name 712 (e.g., the name of the monitored user, which may be displayed as the first name followed by the last initial, or the first name followed by the last name, or for certain given countries or markets, the last name followed by the first name, as shown in FIG. 7), a time stamp 716, and a current analyte level value 714. In some embodiments, the current analyte level value 714 may include a numerical value (which may be displayed in units of measurement determined by the third party region or country) and a trend direction arrow indicating whether the monitored user's analyte level is rising or falling. The profile card portion 710 may also have a background color that indicates whether the monitored user's analyte level is above, below, or within a target analyte range. For example, if the monitored user's analyte level is below the target range, the background color of the profile card portion 710 may be red. If the monitored user's analyte level is within the target range, the background color of the profile card portion 710 may be green. According to some embodiments, the target range may be a pre-defined analyte level range set by the monitored user. In other embodiments, the target range may be set by a third party via a third-party analyte monitoring application.

[0069] 7, the analyte graph portion 720 is located near the profile card portion 710 and may include an analyte trend line 722 reflecting the analyte levels of the monitored user over a period of time. For example, as shown in FIG 7, the x-axis of the analyte graph portion 720 may include time units (e.g., 5 minute increments, 15 minute increments, etc.) over a 12 hour period, while the y-axis may include the measured analyte concentrations of the monitored user. Those skilled in the art will recognize that other periods of time (e.g., 4 hours, 24 hours, 48 ​​hours, etc.) may be reflected on the x-axis and are fully within the scope of the present disclosure.

[0070] The analyte graph portion 720 may further include a shaded area indicating a target range for the monitored user (shown by shaded area 726) and one or more alarm thresholds, depicted in FIG. 7 as dashed lines 728A (high glucose threshold) and 728B (low glucose threshold). In some embodiments, the alarm thresholds may be set by the monitored user. In other embodiments, the alarm thresholds may be set by a third party via a third-party analyte monitoring application. In still other embodiments, the analyte graph portion 720 may not include alarm thresholds (e.g., if the third party or monitored user has disabled alarms or if the monitored user's sensor control device does not support alarms).

[0071] In accordance with another aspect of many embodiments, the connection interface may be interactive in real-time or near real-time. In some embodiments, for example, the information reflected in the profile card portion 710 (e.g., the current analyte level value 714) and the information reflected in the analyte graph portion 720 (e.g., the analyte trend line 722) may be automatically updated and / or refreshed at a predetermined frequency (e.g., every 30 seconds, every minute, every 5 minutes, etc.). In some embodiments, the current analyte level value 714 and the analyte trend line 722 may be updated when the connection interface is brought to the foreground on a secondary display device. In yet other embodiments, the current profile card portion 710 and the analyte graph portion 720 may be updated in response to a predetermined input by a third party (e.g., when a third party pulls down on the screen with their finger or some other predetermined gesture).

[0072] Also, according to another aspect of the embodiment, the profile card portion 710 may be configured to display historical analyte data based on a third party's interaction with the analyte graph portion 720. In some embodiments, for example, when a third party interacts with a point on the analyte trend line 722 (e.g., by touching the point on the analyte trend line 722), the profile card portion 710 may be updated to display historical analyte level values ​​based on the location of that point on the analyte trend line 722. Similarly, the time stamp 716 and background color of the profile card portion 710 may be updated to reflect the time stamp of the historical analyte level value being displayed and whether the historical analyte level value was within or outside of the target analyte range depending on the point or portion of the analyte trend line 722 being touched (see, e.g., FIG. 8C ).

[0073] As shown in FIG. 7, a point or portion of the analyte trend line 722 displayed on the profile card portion 710 may be indicated by a colored circle 724 on the analyte trend line 722. In some embodiments, a third party may touch the colored circle 724 and drag it along the analyte trend line 722, and the information displayed on the profile card portion 710 may be immediately updated with historical analyte level data based on the point or portion of the analyte trend line 722 that the third party is touching (see, e.g., FIG. 8C). According to one aspect of some embodiments, the connection interface may also be configured to return the selected point to the current time (also referred to as the current glucose level) in response to a third party tapping on the profile card portion 710. In some embodiments, the connection interface may be configured to return the selected point to the current time / current glucose level in response to a third party tapping on the right edge of the analyte graph portion 720. In some embodiments, the connection interface may be configured to return the selected point to the current time / current glucose level in response to a third party tapping in combination with a drag-to-the-right gesture on any portion of the analyte graph portion 720. Those skilled in the art will recognize that any of the above gestures may be performed alone or in combination.

[0074] 8A-8J depict an embodiment of a connection interface displayed by a third party analyte monitoring application when a third party has multiple connections. Referring first to FIG. 8A, GUI 801 depicts a multiple connection interface including multiple profile cards 802, 804, 806, and 808. In general, each profile card in GUI 801 is similar to profile card portion 710 described with respect to FIG. 7. For example, profile card 802 includes a connection name, a time stamp, and a current analyte level value (including a numerical value and a trend direction arrow). As previously described, each connection name may be displayed as a first name followed by a last name initial, as shown in FIG. 8A, or as a first name followed by a last name, or alternatively, for certain given countries or markets, as a first name followed by a last name. Additionally, profile card 802 may have a background color that indicates whether the monitored user's analyte level is within or outside of a target analyte range. According to another aspect of the embodiment, when a third party selects a profile card 802, for example by pressing a corresponding area of ​​a touch screen, a corresponding individual connection interface 811 is displayed (as shown in FIGS. 8B and 8C). As previously described, a third party can interact with the GUI 811 by dragging the colored circle 812 along the analyte trend line to cause the profile card portion 814 to display the corresponding historical analyte level value and corresponding time stamp associated with the point on the analyte trend line where the colored circle 812 is located.

[0075] Returning to FIG. 8A, the profile card 804 also includes the connection name and time stamp. However, instead of the current analyte level value, the profile card 804 displays a low glucose alert text and a pictogram to indicate that a low glucose threshold condition has occurred. According to some embodiments, when a third party selects the profile card 804, a corresponding individual connection interface 813 is displayed (as shown in FIG. 8D). However, in some embodiments, the GUI 813 maintains the "Low Glucose Alert" and pictogram in the profile card portion, and the analyte trend lines are static and cannot be interacted with. In other embodiments, the analyte trend lines in the interface 813 may continue to update and the third party may be able to interact with them, but the analyte trend lines may display gaps.

[0076] Returning to FIG. 8A, the profile card 806 also includes the connection name and time stamp. However, instead of a current analyte level value, the profile card 806 displays three dashes to indicate that no recent data has been received. This may be due to a loss of signal condition, such as the monitored user's smartphone malfunctioning or going out of wireless communication range along with the monitored user's worn sensor control device. Additional details regarding loss of signal conditions can be found in U.S. Patent Application Serial No. 17 / 478,447, which is incorporated herein by reference in its entirety.

[0077] According to another aspect of some embodiments, when the third party selects the profile card 806, a corresponding respective connection interface 813 is displayed (as shown in FIGS. 8E, 8F, and 8G). As previously described, the third party can interact with the GUI 813 by touching (or near) the analyte trend line, causing the profile card portion 816 to display the corresponding historical analyte level values ​​(if any) and corresponding time stamps associated with the point on the analyte trend line with which the third party is interacting. For example, FIG. 8F shows that at the selected point 818, there is no historical analyte data for the corresponding time of 8:33 AM, as indicated by the three dashes. Returning to FIG. 8E, the profile card portion 816 also indicates there is no recent data with an information glyph. In some embodiments, pressing the information glyph further displays an information modal 820 (as shown in FIG. 8G), which can provide additional information regarding the possible causes of the no recent data condition.

[0078] Returning to FIG. 8A, the profile card 808 also includes a connection name and a time stamp. However, instead of a current analyte level value, the profile card 808 displays the letters "HI" to indicate that the monitored user's analyte level is above the upper reportable analyte level limit (similarly, a letter "LO" indication may indicate that the monitored user's analyte level is below the lower reportable analyte level limit). As shown in FIG. 8A, the profile card 808 may have an orange background color to indicate that the analyte level value is above the target analyte range. When the third party selects the profile card 808, a corresponding respective connection interface 821 is displayed (as shown in FIGS. 8H, 8I, and 8J). As previously mentioned, the third party may interact with the GUI 821 by touching (or adjacent) the analyte trend line, causing the profile card portion 822 to display the corresponding historical analyte level value (if any) and the corresponding time stamp associated with the point on the analyte trend line with which the third party is interacting. For example, FIG. 8I shows that at the selected point 824, the monitored user's analyte level is above the upper reportable limit at the corresponding time, 4:55 p.m. Returning to Figure 8H, the profile card portion 822 also includes a message that the monitored user's analyte level is out of range and an informational glyph, in some embodiments, pressing the informational glyph may cause a modal 826 to appear, as shown in Figure 8J, which may provide additional information regarding the out-of-range glucose condition.

[0079] 9A-9E are additional embodiments of connection interfaces 901, 903, 905, 909, and 911. FIG. 9A is a connection interface 901 including a red colored dot 902 indicating that a selected point is below a target range. According to some embodiments, the colored dot 902 may be displayed in a predetermined color based on whether the dot's location on the analyte trend line reflects a value that is above, below, or within a predetermined target range. For example, in FIG. 9B the colored dot is green, indicating that the selected point is within the target analyte range. In FIG. 9C the colored dot 908 is orange, indicating that the selected point is above the target analyte range.

[0080] Referring to FIG. 9B, the connectivity GUI 903 includes an analyte trendline with a portion 904 displayed in red indicating that a historical analyte level value is below a fixed low glucose threshold. According to some embodiments, the fixed low glucose threshold can be a threshold (e.g., below 70 mg / dL) independent of the target range and / or alarm threshold (shown in FIG. 9C), and the red portion 906 of the analyte trendline is independent of the low glucose alarm threshold and the target analyte range. Referring now to FIGS. 9D and 9E, the connectivity GUIs 909 and 911 depict an interface that uses different units of measurement (mmol / L) than FIGS. 9A-9C (mg / dL). The different units of measurement are shown for the current analyte value in the profile card section and along the y-axis in the analyte graph section. In some embodiments, the units of measurement may be a configurable setting within the third party analyte monitoring application. In other embodiments, the units of measurement may be determined based on a region and / or country selection during configuration or setup of the third party analyte monitoring application.

[0081] According to another aspect of the embodiment, the analyte data displayed on the connection interface may reflect analyte data collected and combined from multiple reading devices used by the monitored user. In some embodiments, for example, the monitored user may collect analyte data from a sensor control device using multiple reading devices, such as a smartphone, a dedicated receiver, and / or a glucose meter. Each reading device of the monitored user may transmit collected analyte data to a trusted computer system 180 (e.g., a cloud-based server). In many embodiments, the collected analyte data may then be combined by the trusted computer system 180, e.g., to resolve discrepancies and remove duplicate records, and then transmit the data to a third-party secondary display device. In other embodiments, the collected analyte data may be combined by a third-party analyte monitoring application on a third-party secondary display device. Additional details regarding methods for combining analyte data collected by multiple reading devices may be found in U.S. Patent Application Publication No. 2021 / 0378601, which is incorporated herein by reference in its entirety.

[0082] One skilled in the art will recognize that any one or more of these methods or states for updating or interacting with the displayed sample information may be implemented alone or in combination with each other and may depend on the monitored user's configured settings, a third party's configured settings, or the type of sensor control device worn by the monitored user.

[0083] Embodiments of a Register Interface for a Third Party Specimen Surveillance Application

[0043] An embodiment of a register interface for a third-party analyte monitoring application is now described. At the outset, one of ordinary skill in the art will appreciate that the interfaces described herein may include instructions stored in the memory of a secondary display device (e.g., a smartphone, a smartwatch, a wearable electronic device, a dedicated receiver, etc.) owned by a third party.

[0084] As discussed above with respect to FIG. 7, each connection interface may include a logbook button 730. According to one aspect of the embodiment, when the logbook button 730 is selected, a logbook interface is displayed in the third-party analyte monitoring application (as shown in FIGS. 10A-10H). Each logbook interface may include multiple logbook entries for a given time period (e.g., last 2 weeks, last month, last 6 months). According to another aspect of the embodiment, the logbook interface may include logbook entries from different types of sensor control devices. In some embodiments, the logbook entries may be generated automatically, for example, when the monitored user's sensor control device is scanned by the monitored user's reader device. In other embodiments, the logbook entries may be generated automatically when an alarm is activated and / or presented to the monitored user's reader device. In yet other embodiments, the logbook entries may be generated automatically when an alarm is activated and / or presented to the third-party secondary display device. In other embodiments, the logbook entries may be manually entered by the monitored user into the analyte monitoring application in the monitored user's reader device.

[0085] FIG. 10A illustrates an embodiment of a register GUI 1001 for use in a third-party analyte monitoring application. The register GUI 1001 includes multiple register entries grouped by date, and each register entry may include a analyte level value, a trend direction arrow, a background color, and a time stamp. For example, the register GUI includes a register entry 1003 that indicates a monitored user's analyte reading at 12:14 PM, with a analyte level of 117 mg / dL, an elevated analyte level (e.g., upward trend arrow), and a analyte level within a target analyte range (e.g., green background). According to another aspect of the embodiment, when the record entry 1003 is selected, an information modal 1015, shown in FIG. 10G, is displayed to provide additional information regarding the record entry. Additionally, the register GUI 1001 may further include register entries that indicate when a monitored user's analyte level exceeds the upper reportable analyte level limit. For example, the register entry 1002 displays the letters "HI" to indicate that the monitored user's analyte level exceeds the upper reportable analyte level limit. (Similarly, an "LO" indication may indicate that the monitored user's analyte level is below the lower reportable analyte level limit.) Also, according to the depicted embodiment, selecting record entry 1002 displays information modal 1004, shown in FIG. 10B, which may provide additional information regarding the out-of-range condition.

[0086] FIG 10C illustrates another embodiment of a register GUI 1005 for use in a third party analyte monitoring application. FIG 10C illustrates a register interface similar to the register GUI 1001 described with respect to FIG 10A and 10B, except that the GUI 1005 further includes a register entry 1006 reflecting a low glucose alert. As previously discussed, the register entry 1006 may be generated automatically in response to a low glucose alert or a high glucose alert being activated and / or presented to the monitored user's reader. Also, according to the depicted embodiment, selecting the record entry 1005 displays an information modal 1008, shown in FIG 10D, which may provide additional information regarding the low glucose alert (e.g., the time of the alert).

[0087] FIG 10E illustrates another embodiment of a register GUI 1010 for use in a third party analyte monitoring application. FIG 10E illustrates a register interface similar to register GUIs 1001 and 1005, except that all register entries illustrated in GUI 1010 are initiated and / or automatically generated in response to an alert presented on a third party secondary display. For example, record entry 1012 includes an analyte level value (e.g., 69 mg / dL), a trend direction arrow, a background color, an alert pictogram, and a time stamp. Also, according to the illustrated embodiment, selecting record entry 1010 displays information modal 1014, shown in FIG 10F, which may provide additional information regarding the low glucose alert (e.g., the time of the alert).

[0088] Also, like the connection interface, the analyte data displayed in the logbook interface may reflect analyte data collected and combined from multiple reading devices utilized by the monitored user. In some embodiments, analyte data may be collected using multiple reading devices, such as a smartphone, dedicated receiver, and / or glucose meter, from, for example, a sensor control device worn by the monitored user. Each reading device of the monitored user may transmit collected analyte data to a trusted computer system 180 (e.g., a cloud-based server). In many embodiments, the collected analyte data may then be combined by the trusted computer system 180, e.g., to resolve discrepancies and remove duplicate records, and then transmit the data to a third-party secondary display device. In other embodiments, the collected analyte data may be combined by a third-party analyte monitoring application on a third-party secondary display device. Additional details regarding methods for combining analyte data collected by multiple reading devices may be found in U.S. Patent Application Publication No. 2021 / 0378601, which is incorporated herein by reference in its entirety.

[0089] Those skilled in the art will also recognize that any of the connection interfaces depicted and described herein, including the register interfaces, can be configured to display analyte level values ​​in different units of measurement. For example, register GUI 1001 (FIG. 10A) depicts analyte level values ​​in mg / dL, while register GUI 1013 (FIG. 10H) depicts analyte level values ​​in mmol / L. Those skilled in the art will also recognize that the different types of register interfaces described herein can be implemented alone or in combination with each other and may depend on the monitored user's configured settings, a third party's configured settings, or the type of sensor control device worn by the monitored user.

[0090] Embodiments of an Alert Notification Configuration Interface for a Third Party Analyte Monitoring Application

[0036] An embodiment of an alarm notification configuration interface for a third party analyte monitoring application is now described. At the outset, one of ordinary skill in the art will appreciate that the interfaces described herein may include instructions stored in the memory of a secondary display device (e.g., a smartphone, a smartwatch, a wearable electronic device, a dedicated receiver, etc.) owned by a third party.

[0091] According to one aspect of the embodiment, the third party analyte monitoring application may be configured to present one or more alert notification settings interfaces based on the type of sensor control device worn by the monitored user. FIG. 10I is a flow diagram illustrating an embodiment of a method 1050 for displaying an alert notification settings interface for a third party analyte monitoring application. Initially, prior to step 1052, the method 1050 may require the third party to first install the third party analyte monitoring application on the secondary display device (e.g., a smartphone, a smartwatch, a wearable electronic device, or a dedicated receiver) and create a user account (as described above with respect to FIGS. 5A-5M). At step 1052, a connection with the monitored user is established by the third party analyte monitoring application on the secondary display device of the third party. The process of establishing the connection may utilize the methods and interfaces described with respect to FIGS. 4A-4J and 6B, 6C. At step 1054, the third party analyte monitoring application receives sensor type information. According to some embodiments, the sensor type information may include a version number, a version name, a model name, a model number, a serial number, a sensor code, or any other type of identifier indicative of the type of sensor control device worn by the monitored user involved in the connection. In some embodiments, the sensor type information may be sent from the trusted computer system (e.g., a cloud-based server) to the third-party analyte monitoring application once a connection is established, while in other embodiments, the third-party analyte monitoring application may periodically request the sensor type information from the trusted computer system.

[0092] Referring again to FIG. 10I, at step 1056, the third-party analyte monitoring application determines an alert notification settings interface based on the received sensor type information. For example, at step 1058, a first set of alert notification settings may be displayed if it is determined that the monitored user associated with the connection is using a sensor control device with a first sensor type. Similarly, at step 1060, a second set of alert notification settings may be displayed if it is determined that the monitored user associated with the connection is using a sensor control device with a second sensor type. Also, in some embodiments, if the sensor type of the monitored user associated with the connection cannot be determined (or, as another example, if the monitored user's sensor type is determined to be incompatible), a third set of alert notification settings may be displayed. Also, according to some embodiments, prior to displaying the notification settings interface to a particular monitored user (steps 1058, 1060, or 1062), the third-party analyte monitoring application may receive the monitored user's notification settings via a trusted computer system. If this is the first time a third party has seen the monitored user's notification settings, the third-party analyte monitoring application may automatically configure the notification settings with the monitored user's alert settings. Next, according to some embodiments, the third party may change the monitored user's notification settings within the third-party analyte monitoring application, and the third-party analyte monitoring application may save any changes and proceed.

[0093] In this regard, the third-party analyte monitoring application provides flexibility and can be configured to work with a variety of sensor control devices, optionally adopting the monitored user's alert settings and allowing the third party to change them moving forward. This can be beneficial if the third party needs to support multiple connections with multiple monitored users or if the monitored user changes their sensor control device. According to another aspect of some embodiments, when a change is detected in the monitored user's sensor control device and / or the analyte monitoring software application, the third-party analyte monitoring software can dynamically change certain interfaces and settings without user intervention. As a non-limiting example, the third-party analyte monitoring application can detect if the monitored user's sensor control device has been upgraded from a scanning-based device (e.g., sending data in response to a request or scan) to a streaming device (e.g., sending data autonomously). In response to detecting that the sensor control device has been upgraded, a notification can be output to prompt the third party to update the third-party analyte monitoring application (FIG. 17I). Once the third-party analyte monitoring application is updated, a notification can be output to inform the third party that real-time monitoring of the monitored user with the upgraded sensor control device is available (FIG. 17J). Also, a modified set of notification settings may be associated with the monitored user to support the new functionality of the upgraded sensor control device. For example, if a monitored user's sensor control device is upgraded from a scanning-based device to a streaming device, the third-party analyte monitoring software that previously displayed a first type of notification settings (e.g., FIGS. 13A-13H) may display a second type of notification settings (e.g., FIGS. 15E-15H). Similarly, if a monitored user's sensor control device and / or analyte monitoring software application is changed, the displayed logbook interface may also change.For example, according to one embodiment, if a monitored user's sensor control device is upgraded from a scanning-based device to a streaming device, the third-party analyte monitoring software may change the log associated with that monitored user from a first type log (e.g., FIG. 10A) to a second type log (e.g., FIG. 10E).

[0094] As another non-limiting example, a third party analyte monitoring application can automatically detect when a monitored user's sensor control device that was communicatively coupled to a primary display device (e.g., a monitored user's smartphone) is subsequently communicatively coupled to a secondary display device (e.g., a dedicated reader device) and the sensor control device is no longer streaming data to the monitored user's primary display device. The third party analyte monitoring application can then output an alert or notification (e.g., FIGS. 17E-17H) and then automatically display an appropriate set of notification settings on the secondary display device. For example, when the monitored user's sensor control device is communicatively coupled to the secondary display device, the third party analyte monitoring software that previously displayed a second type of notification setting (e.g., FIGS. 13A-13H, 14A-14G, or 15E-15H) can display the first type of notification setting (e.g., FIGS. 12A, 12B).

[0095] 11A-11H depict an embodiment of a set of alarm notification settings interfaces for a third-party analyte monitoring application. In some embodiments, these interfaces may include the third set of alarm notification settings described with respect to step 1062 of method 1050 (FIG. 10I).

[0096] 11A, an alarm notification setting GUI 1101 includes a glucose reading switch 1102 (depicted in an off state), a low glucose alarm setting 1104 (depicted in an on state), and a high glucose alarm setting 1106 (depicted in an off state). According to one aspect of an embodiment, the glucose reading switch, when turned on, may cause an alarm notification to be displayed on a third party secondary display device when the monitored user takes a glucose reading (e.g., scans the sensor control device with a reader). According to another aspect of an embodiment, the low glucose alarm setting 1104 may further include text indicating a low glucose threshold.

[0097] When the third party selects the high glucose alarm setting 1106 in GUI 1101, the third party analyte monitoring application displays a separate alarm notification setting GUI 1107 (as shown in FIG. 11B). GUI 1107 includes a high glucose alarm switch 1108 (depicted in the off state). According to some embodiments, when the third party attempts to switch the high glucose alarm setting 1108 to the on state, a modal 1110 is displayed (as shown in FIG. 11C) indicating that the monitored user is "using a sensor or app that is not compatible with this alarm" or that the monitored user "turned this alarm off within the application." According to one aspect of the embodiment, the modal 1110 may be displayed based on sensor type information regarding the type of sensor control device used by the monitored user associated with this connection.

[0098] Returning to Figure 11A, when the third party selects low glucose alarm setting 1104, another alarm notification setting GUI 1111 is displayed. As can be seen in Figure 11D, GUI 1111 includes a low glucose alarm switch (depicted in an on state) and a low glucose alarm threshold setting 1112 (including an informational pictogram). When low glucose alarm threshold setting 1112 is selected, modal 1114 is displayed as shown in Figure 11E, indicating that this setting may only be changed by the monitored user from the analyte monitoring application. Again, modal 1114 may be displayed based on sensor type information regarding the type of sensor control device used by the monitored user involved in the connection.

[0099] 11F-11H depict another embodiment of a set of alarm notification settings GUIs where certain information regarding the monitored user's alarm settings is unknown. Referring to FIG. 11F, for example, GUI 1115 is similar to GUI 1101 of FIG. 11A, except that, for example, low glucose alarm setting 1116 indicates that the low glucose threshold is unknown. When the third party selects low glucose alarm setting 1116, another alarm notification settings GUI 1117 is displayed. As can be seen in FIG. 11G, GUI 1117 is similar to GUI 1111 of FIG. 11D, except that a text indicator 1118 is displayed (instead of the low glucose threshold setting) that the connection's alarm settings are unknown. Similarly, when information glyph 1118 is selected, modal 1120 is displayed (as shown in FIG. 11H) providing additional information regarding the status of this particular alarm setting.

[0100] 12A and 12B depict another embodiment of a set of alarm notification settings GUIs for a third party analyte monitoring application. In some embodiments, these interfaces may include the first set of alarm notification settings described with respect to step 1058 (FIG. 10I) of method 1050. Referring to FIG. 12A, alarm notification settings GUI 1201 includes a glucose reading switch 1202A depicted in an OFF state. FIG. 12B depicts the same GUI 1201 with a glucose reading switch 1202B depicted in an ON state. As previously described, when the glucose reading switch 1202B is enabled, the third party analyte monitoring application may be configured to cause an alarm notification to be displayed on the third party's secondary display device when the monitored user takes a glucose reading (e.g., scans the sensor control device with their reader).

[0101] According to one aspect of the embodiment, GUI 1201 does not include other settings (e.g., low glucose alert, high glucose alert, etc.) because such settings are not supported by the sensor control device used by the monitored user involved in the connection, as indicated by the sensor type information received by the third-party analyte monitoring application.

[0102] 13A-13H depict another embodiment of a set of alarm notification settings GUIs for a third-party analyte monitoring application. In some aspects, these interfaces are substantially similar to the interfaces depicted in FIGS. 11A-11H and may also include the first set of alarm notification settings described with respect to step 1058 (FIG. 10I) of method 1050. Referring first to FIG. 13A, alarm notification settings GUI 1301 is similar to GUI 1101 (FIG. 11A) in that GUI 1301 also includes a glucose reading switch 1302 (depicted in an off state), a low glucose alarm setting 1304 (depicted in an on state), and a high glucose alarm setting 1306 (depicted in an off state). Similarly, according to one aspect of the embodiment, glucose reading switch 1302, when turned on, may cause an alarm notification to be displayed on a third-party secondary display device when the monitored user takes a glucose reading (e.g., scans the sensor control device with a reader). Similarly, according to another aspect of an embodiment, the low glucose alarm settings 1304 may further include text displaying the low glucose threshold.

[0103] When the third party selects the high glucose alarm setting 1306 in GUI 1301, the third party analyte monitoring application displays a separate alarm notification setting GUI 1307 as shown in FIG. 13B. GUI 1307 includes a high glucose alarm switch 1308 (depicted in the off state). According to some embodiments, when the third party attempts to switch the high glucose alarm setting 1308 to the on state, modal 1310 is displayed indicating that the monitored user has turned off this particular alarm via the analyte monitoring application on the monitored user's reader. According to one aspect of the embodiment, modal 1310 may be displayed based on sensor type information regarding the type of sensor control device used by the monitored user associated with the connection.

[0104] Returning to Figure 13A, when the third party selects low glucose alarm setting 1304, another alarm notification setting GUI 1311 is displayed. As can be seen in Figure 13D, GUI 1311 includes a low glucose alarm switch (depicted in an on state) and a low glucose alarm threshold setting 1312 (including an informational pictogram). When low glucose alarm threshold setting 1312 is selected, modal 1314 is displayed as shown in Figure 13E, indicating that this setting may only be changed in the analyte monitoring application by the monitored user. Again, modal 1314 may be displayed based on sensor type information regarding the type of sensor control device used by the monitored user involved in the connection.

[0105] 13F-13H depict another embodiment of a set of alarm notification settings GUIs where some information regarding the monitored user's alarm settings is unknown. GUI 1315 is similar to GUI 1301 of FIG. 13A, except that, for example, low glucose alarm setting 1316 indicates that the low glucose threshold is unknown. When the third party selects low glucose alarm setting 1316, another alarm notification settings GUI 1317 is displayed. As can be seen in FIG. 13G, GUI 1317 is similar to GUI 1311 of FIG. 13D, except that a text indicator 1318 is displayed (instead of the low glucose threshold setting) that the connection's alarm settings are unknown. Similarly, when information glyph 1318 is selected, a modal 1320 is displayed providing additional information regarding the status of this particular alarm setting.

[0106] 14A-14G depict another embodiment of a set of alarm notification settings GUIs for a third-party analyte monitoring application. In some embodiments, these interfaces may include the second set of alarm notification settings described with respect to step 1060 of method 1050 (FIG. 10I).

[0107] 14A, the alarm notification settings GUI 1410 includes a low glucose alarm setting 1402 (depicted in an on state) and a high glucose alarm setting 1404 (depicted in an off state). According to one aspect of these embodiments, the GUI 1410 also includes a no recent data setting 1406 (depicted in an on state) and does not include a glucose reading switch (as shown in FIG. 11A) because the sensor type information received by the third-party analyte monitoring application indicates that the monitored user's sensor control device is configured to autonomously stream analyte data to the monitored user's reader device (e.g., via Bluetooth or Bluetooth low energy protocols). According to another aspect of the embodiment, the low glucose alarm setting 1402 may include text indicating a low glucose threshold and the no recent data setting 1406 may include text indicating that a threshold time has passed since the most recent valid current glucose reading.

[0108] 14B-14D depict additional embodiments of the alarm notification setting GUI for a low glucose alarm. In particular, according to some embodiments, selection of low glucose alarm setting 1402 (FIG. 14A) may cause a low glucose alarm GUI 1407 to be displayed. FIG. 14B shows the low glucose alarm GUI 1407 with low glucose alarm switch 1408A in an off state. FIG. 14C shows the low glucose alarm GUI 1407 with low glucose alarm switch 1408B in an on state, which also causes a low glucose alarm threshold setting 1410 to be displayed. According to some embodiments, when low glucose alarm threshold setting 1410 is selected, a low glucose alarm threshold GUI 1411 is displayed. As seen in FIG. 14D, the low glucose alarm threshold GUI 1411 includes a wheel interface 1412 that allows a third party to select a low glucose threshold. Those skilled in the art will recognize that other user interface features for selecting a value, such as a pull-down menu or a free text field, may be utilized and are fully within the scope of the present disclosure. Once the low glucose threshold has been selected, the third party can select the save button 1414 to apply any changes to the low glucose alarm settings.

[0109] 14E-14G depict additional embodiments of an alarm notification setting GUI for a No Recent Data alarm. In particular, according to some embodiments, selection of the No Recent Data setting 1406 (FIG. 14A) may cause the No Recent Data alarm GUI 1415 to be displayed. FIG. 14E shows the No Recent Data alarm GUI 1415 with the No Recent Data alarm switch 1416A in an off state. FIG. 14F shows the No Recent Data alarm GUI 1415 with the No Recent Data alarm switch 1416B in an on state, which also causes the Threshold Time Elapsed setting 1418 to be displayed, indicating that a threshold time has elapsed since receiving the last valid current glucose reading before activating the No Recent Data alarm. Also, according to some embodiments, when the Threshold Time Elapsed setting 1418 is selected, the Threshold Time Elapsed GUI 1419 is displayed. As can be seen in FIG. 14G, the Threshold Time Elapsed GUI 1419 includes a wheel interface 1420 that allows a third party to select a threshold time lapse value. Again, one of ordinary skill in the art will recognize that other user interface features for selecting a value, such as a pull-down menu or free text field, may be utilized and are fully within the scope of the present disclosure. Once a threshold time lapse value is selected, the third party may select the save button 1422 to apply any changes to the current no data setting.

[0110] 15A-15D depict another embodiment of a set of alarm notification settings interfaces for a third-party analyte monitoring application. In some aspects, these interfaces are substantially similar to the interfaces depicted in FIGS. 13A-13H and may also include the first set of alarm notification settings described with respect to step 1058 (FIG. 10I) of method 1050. Referring first to FIG. 15A, alarm notification settings GUI 1501 is similar to GUI 1301 (FIG. 13A) in that GUI 1501 also includes a glucose reading switch 1502 (depicted in an on state), a low glucose alarm setting 1506 (depicted in an on state), and a high glucose alarm setting 1508 (depicted in an off state). GUI 1501 also includes an emergency low glucose alarm 1504 (depicted in an on state). According to another aspect of the embodiment, the low glucose alarm setting 1506 and the emergency low glucose alarm setting 1504 may include text indicating the respective thresholds.

[0111] When the third party selects the emergency low glucose alarm setting 1504 in GUI 1501, the third party analyte monitoring application displays the emergency low glucose alarm GUI 1509 as shown in Figure 15B. GUI 1509 includes an emergency low glucose alarm switch 1510A (depicted in the off state). Figure 15C depicts GUI 1509 with the emergency low glucose alarm setting in the on state, which also displays the emergency low glucose threshold 1512 and an informational glyph. When either the emergency low glucose threshold 1512 or the informational glyph is selected, a modal 1514 is displayed as shown in Figure 15D, indicating that the emergency low glucose alarm setting cannot be changed. The modal 1514 may be displayed based on sensor type information regarding the type of sensor control device used by the monitored user associated with the connection.

[0112] 15E-15H depict another embodiment of a set of alarm notification settings interfaces for a third-party analyte monitoring application. In some aspects, these interfaces are substantially similar to the interfaces depicted in FIGS. 14A-14G and may also include a second set of alarm notification settings as described with respect to step 1060 (FIG. 10I) of method 1050. Referring first to FIG. 15E, an alarm notification settings GUI 1521 includes a low glucose alarm setting 1524 (depicted in an on state) and a high glucose alarm setting 1526 (depicted in an off state). The low glucose alarm setting 1524 may include text indicating a low glucose threshold and the no recent data setting 1528 may include text indicating a threshold time has passed since the last valid current glucose reading.

[0113] Also, according to one aspect of these embodiments, the GUI 1521 includes both a glucose reading switch 1522 (depicted in an on state) and a no recent data setting 1528 because the sensor type information received by the third-party analyte monitoring application indicates that the monitored user's sensor control device is configured for both (1) scan-based or request-based analyte data transmission and (2) autonomous streaming of analyte data (e.g., via Bluetooth or Bluetooth low energy protocols).

[0114] 15F-15H depict additional embodiments of the alarm notification setting GUI for a high glucose alarm. In particular, according to some embodiments, selection of high glucose alarm setting 1526 (FIG. 15E) may cause high glucose alarm GUI 1531 to be displayed. FIG. 15F shows high glucose alarm GUI 1531 with high glucose alarm switch 1532A in an off state. FIG. 15G shows high glucose alarm GUI 1531 with high glucose alarm switch 1532B in an on state, also causing high glucose alarm threshold setting 1534 to be displayed. According to some embodiments, when high glucose alarm threshold setting 1534 is selected, high glucose alarm threshold GUI 1541 is displayed. As seen in FIG. 15H, high glucose alarm threshold GUI 1541 includes a wheel interface 1542 that allows a third party to select a high glucose threshold. One of ordinary skill in the art will recognize that other user interface features for selecting a value, such as a pull-down menu or free text field, may be utilized and are fully within the scope of the present disclosure. Once a high glucose threshold is selected, the third party may select a save button 1544 to apply any changes to the low glucose alarm setting. In this regard, similar to the previous embodiment described with respect to Figures 14A-14H, a third party can select a glucose alert threshold that is independent of the monitored user's glucose alert threshold.

[0115] Although the alarm notification settings GUI and certain elements thereof are described in particular combination with certain sensor control devices, one of ordinary skill in the art will understand that these interfaces and elements may be implemented in other combinations and permutations, and that such configurations are fully within the scope of the present disclosure.

[0116] Alarm Notification Interface and Other Interface Embodiments for Third Party Analyte Monitoring Embodiments of an alarm notification interface and other types of interfaces for third-party analyte monitoring are described below. At the outset, one of skill in the art will appreciate that the interfaces described herein may include instructions stored in a memory of a secondary display device owned by a third party (e.g., a smart phone, a smart watch, a wearable electronic device, a dedicated receiver, etc.). One of skill in the art will also recognize that any of the alarm notification interfaces may be used in combination with any of the alarm notification configuration interfaces described above.

[0117] 16A-16H and 17A-17O are embodiments of alarm notification interfaces and other interfaces for third party analyte monitoring. Referring first to FIG. 16A, an alarm interface 1601 illustrates an embodiment of a new sensor notification indicating that a monitored user has begun using a new analyte sensor at a particular time. FIG. 16B illustrates an alarm interface 1603, illustrating an embodiment of a glucose reading notification. The notification may indicate, for example, that the monitored user has scanned their sensor control device. The alarm interface 1603 may also show the analyte level value (e.g., 281 mg / dL), a trend direction arrow indicating whether the monitored user's analyte level is rising or falling, and a time stamp. FIG. 16C illustrates an alarm interface 1605, illustrating an embodiment of a high glucose alarm indicating that the monitored user's analyte level has exceeded the high glucose alarm threshold at a particular time. Similarly, FIG. 16D illustrates another embodiment of a high glucose alarm interface, alarm interface 1607, with an indication "HI" indicating that the monitored user's analyte level is above the upper reportable analyte level limit.

[0118] Referring now to FIG. 16E, an alarm interface 1609 illustrates an embodiment of a low glucose alarm notification indicating that the monitored user's analyte level has fallen below the low glucose alarm threshold at a particular time. FIG. 16F illustrates an alarm interface 1611 illustrating a cleared low glucose alarm notification indicating that the monitored user has cleared the low glucose alarm on his / her reading device at a particular time. FIG. 16G illustrates an alarm interface 1613 illustrating a no recent data notification, which may indicate that a valid current analyte level has not been received since a particular time. In some embodiments, for example, a no recent data notification may indicate that a third party analyte monitoring application on the secondary display device has not received a valid current analyte level reading from a trusted computer system. In other embodiments, a no recent data notification may indicate that an analyte monitoring application on the monitored user's reading device has not received a valid current analyte level reading from a sensor control device. In still other embodiments, a no recent data notification may indicate either or both of the above conditions, or any other condition that prevents a third party analyte monitoring application from receiving a valid current analyte level reading.

[0119] 16H, an alert interface 1615 illustrates an embodiment of a sensor termination alert notification that may indicate that a monitored user's sensor control device has expired. In some embodiments, the sensor termination notification may also indicate whether the monitored user's sensor control device has been terminated for other reasons, such as a sensor failure condition.

[0120] 16A-16H, each alert notification interface may be configured such that touching or tapping the alert notification area will cause the third-party analyte monitoring application to come to the foreground and display a connectivity interface related to that alert notification. According to another aspect of the embodiment, any or all of the alert notification interfaces described herein may be displayed without a time stamp.

[0121] 17A, an alert interface 1701 illustrates an embodiment of a notification interface 1701 indicating that a monitored user has stopped sharing analyte information with third parties. According to one aspect of an embodiment, the alert interface 1701 may be displayed in response to a third-party analyte monitoring application receiving an indication that a monitored user has stopped sharing his or her analyte information with third parties. In some embodiments, this indication may be generated, for example, when a monitored user selects the stop sharing link 428 in the monitored user's analyte monitoring application (see, e.g., FIG. 4H). In other embodiments, this indication may be generated when a monitored user selects the delete link 416 in the monitored user's analyte monitoring application (see, e.g., FIG. 4C). In other embodiments, this indication may be generated when a monitored user deletes his or her account.

[0122] 17B is an embodiment of an emergency low glucose alarm notification interface 1703 for a third party analyte monitoring application. According to one aspect of the embodiment, the emergency low glucose alarm notification interface 1703 may be implemented with the alarm notification settings interface described with respect to FIGS.

[0123] 17C is an embodiment of a maintenance alert notification interface 1705 for a third party analyte monitoring application. According to one aspect of the embodiment, the maintenance alert notification interface 1705 may be initiated and updated by a trusted computer system (e.g., a cloud-based server).

[0124] 17D is an embodiment of a notification interface 1707 indicating that a monitored user has resumed sharing sample information with third parties. Similar to the previous embodiment, depending on the user's particular country or market, the notification interface 1707 may be displayed with the patient's first name followed by the patient's last name, the patient's first name followed by the initial of the patient's last name, or the patient's last name followed by the patient's first name.

[0125] 17E is an embodiment of a notification interface 1709 in the form of a warning indicating that real-time glucose and alerts are unavailable to the monitored user. This warning may be displayed when the third party analyte monitoring application detects that the monitored user has communicatively coupled his or her sensor control device to the secondary display device and that the monitored user's sensor control device is no longer streaming data to the primary display device.

[0126] 17F is an example third party analyte monitoring application interface 1711 that includes an in-app notification 1712 indicating that real-time glucose and alerts are unavailable to the monitored user. The in-app notification 1712 may be displayed when the third party analyte monitoring application detects that the monitored user has communicatively coupled their sensor control device to the secondary display device and that the monitored user's sensor control device is no longer streaming data to the primary display device.

[0127] 17G and 17H are example interfaces for a third party monitoring application that include an in-app modal 1713 and an information modal 1715 to indicate that real-time glucose and alerts are unavailable to the monitored user.

[0128] 17I is an embodiment of a notification interface 1717 for prompting a third party to update their third party analyte monitoring application. According to some embodiments, this notification may be displayed after it is determined that a monitored user's sensor control device and / or analyte monitoring software application has been changed.

[0129] 17J is an embodiment of a notification interface 1719 for notifying a third party that real-time glucose is available for a monitored user. According to some embodiments, this notification may be displayed after it is determined that the monitored user's sensor control device and / or analyte monitoring software application has been changed and the third party analyte monitoring application has been updated.

[0130] 17K-17N are embodiments of coaching interfaces 1721, 1723, 1725, and 1727 that may be displayed in a third-party analyte monitoring application connection interface for a monitored user after the monitored user's sensor control device and / or analyte monitoring software application are upgraded. According to some embodiments, coaching interfaces 1721, 1723, 1725, and 1727 may only be displayed the first time the monitored user's sensor control device and / or analyte monitoring software application are upgraded. Then, as shown in FIG. 17O, when another monitored user's sensor control device is upgraded, only dismissible reminder 1731 is displayed and the third party does not need to be presented with the coaching interfaces again. However, if the third party wishes to view the coaching interfaces again, the third party can touch the "Learn More" link shown in FIG. 17O to launch coaching interfaces 1721, 1723, 1725, and 1727. In other embodiments, the instructional interfaces 1721, 1723, 1725, and 1727 may be displayed each time a monitored user's sensor control device and / or analyte monitoring software application is upgraded.

[0131] Please note that the above alarm notification interfaces are intended to be merely exemplary and are by no means intended to be exhaustive. Additional details regarding alarm interfaces for analyte monitoring can be found in U.S. Patent Application Publication No. 2021 / 0282672, U.S. Patent Application Publication No. 2021 / 0378601, and U.S. Patent Application No. 17 / 478447, all of which are incorporated herein by reference in their entireties.

[0132] Additional GUI embodiments for third-party specimen monitoring Additional GUI embodiments for third party analyte monitoring are now described. Referring first to FIG. 18A, a menu GUI 1801 for use with a third party analyte monitoring application is depicted. In some embodiments, the menu interface 1801 may include a number of selectable options, including, but not limited to, a manage connections option 1802, an account settings option, a help option, and an about software option. When the manage connections option 1802 is selected, a manage connections GUI 1803 is displayed as shown in FIG. 18B. According to one aspect of the embodiment, the manage connections GUI 1803 may include a list of one or more connections (if any), each connection being displayed by the name of the monitored user. In some embodiments, each connection may also include a selectable glyph 1804 for deleting the connection. According to another aspect of the embodiment, when the selectable glyph 1804 is pressed, a confirmation modal 1806 is displayed prompting the third party for confirmation before deleting the connection.

[0133] 19A-19N, an embodiment of a GUI for an enhanced visibility mode (also called "dark mode") is described. In some environments, it may be desirable to enhance the display of a third-party secondary display device for better visibility of many of the interfaces described herein. For example, color irregularities in a chart or graph may be difficult to spot in low light settings due to a lack of contrast between colors. As another example, an interface may be modified to utilize a certain background color that may reduce eye strain in low light settings.

[0134] For example, Figure 19A illustrates a third-party analyte monitoring application initial interface 1901 in an enhanced visibility mode, which is similar to initial interface 501 of Figure 5A. As another example, Figure 19B illustrates a multiple connection interface 1903 in an enhanced visibility mode, which is similar to multiple connection interface 801 of Figure 8A. Similarly, Figures 19C-19F illustrate connection interfaces 1905, 1907, 1909, and 1911, Figure 19G illustrates a register interface 1913, and Figure 19H illustrates an alarm notification settings interface 1915, all shown in the enhanced visibility mode.

[0135] 19I-19N depict embodiments of interfaces 1917, 1919, 1921, 1923, 1925, and 1927 of a third party analyte monitoring application in an enhanced visibility mode. According to one aspect of the embodiment, interfaces 1917, 1919, 1921, 1923, 1925, and 1927 are similar to interfaces 1709, 1711, 1713, and 1715 described with respect to FIGS. 17E-17H in that these interfaces depict warnings or notifications to a third party that real-time glucose data and alerts are unavailable to the monitored user. According to another aspect of the embodiment, interfaces 1917, 1919, 1921, 1923, 1925, and 1927 may be displayed when the third party analyte monitoring application detects that the monitored user has communicatively coupled his or her sensor control device to the secondary display device and that the monitored user's sensor control device is no longer streaming data to the primary display device.

[0136] Also, in some embodiments, the enhanced visibility mode may be enabled by a user-configurable setting in the display device's operating system (e.g., iOS, Android). In other embodiments, the enhanced visibility mode may be a user-configurable setting within a third-party analyte monitoring application (e.g., an in-app setting). In still other embodiments, the enhanced visibility mode may be automatically enabled in response to detection of light above or below a predetermined activation threshold by a light sensor (e.g., a photoelectric device, a photodetector, a phototransistor, a photovariable resistor, and / or a photodiode). In still other embodiments, the enhanced visibility mode may be enabled / disabled according to a predetermined timetable (e.g., 6 p.m. to 6 a.m.) or seasonal timetable (sunset to sunrise). One of ordinary skill in the art will appreciate that other activation mechanisms may be utilized and are fully within the scope of the present disclosure. Additional details regarding the enhanced visibility mode may be found in U.S. Patent Application Serial No. 17 / 478,447, which is incorporated herein by reference in its entirety.

[0137] Digital and graphical user interfaces for third party analyte monitoring applications are provided. For example, various embodiments of methods, systems, and interfaces for connection interfaces, alarm notification setting interfaces, and logbook interfaces in third party analyte monitoring applications are disclosed herein. Also described are various embodiments of interface improvements including enhanced visibility modes, interfaces for setting up the third party analyte monitoring application, and the like.

[0138] Those skilled in the art will understand that any of the GUIs (or portions thereof) described herein are intended to be merely exemplary, and that any individual element or combination of elements depicted and / or described in a particular embodiment or figure may be freely combined with any other element or combination of other elements depicted and / or described with respect to other embodiments.

[0139] It is intended that all features, elements, components, functions, and steps described with respect to any embodiment provided herein can be freely combined and substituted with those of any other embodiment. If a feature, element, component, function, or step is described with respect to only one embodiment, it should be understood that the feature, element, component, function, or step can be used with all other embodiments described herein, unless otherwise specified. Thus, this paragraph serves as a prelude and support for the introduction of claims combining features, elements, components, functions, and steps of multiple different embodiments, or substituting features, elements, components, functions, and steps of one embodiment with those of another embodiment, even if such combinations or substitutions are not specified in a specific example of this description as being possible. It is clearly recognized that specifying all possible combinations and substitutions would be an undue burden, given that one skilled in the art would readily recognize that all such combinations and substitutions are permissible.

[0140] Although the embodiments are susceptible to various modifications and alternative forms, specific examples thereof have been shown and described in detail herein. However, these embodiments are not limited to the specific forms disclosed, but rather, these embodiments should be understood to include all modifications, equivalents, and alternatives falling within the scope of the present disclosure. Also, any feature, function, step, or element of the embodiments may be described or added to the claims, and negative limitations may be described that define the scope of the claims by features, functions, steps, or elements that are not within the scope of the claims.

[0141] Representative embodiments of the present invention will be described below in detail.

[0142] EMBODIMENT 1 1. A system for third-party specimen monitoring, comprising: a sensor control unit including an analyte sensor configured to contact at least a portion of a bodily fluid of a monitored user; a first reader configured to wirelessly receive data indicative of an analyte level of the monitored user from the sensor control device, the first reader further configured to transmit the data indicative of the analyte level to a trusted computer system; A sub-display device, a wireless communication circuit configured to receive from the trusted computer system sensor type information of the sensor control device and data indicative of the analyte level of the monitored user; and a sub-display device having one or more processors coupled to a memory; Equipped with The memory stores a third party analyte monitoring application that, when executed by the one or more processors, causes the one or more processors to display one or more connection interfaces reflecting data indicative of the analyte level of the monitored user.

[0143] EMBODIMENT 2 2. The system of embodiment 1, wherein the first reading device is a smartphone.

[0144] EMBODIMENT 3 3. The system of embodiment 1 or 2, wherein the sub-display device is a smartphone.

[0145] EMBODIMENT 4 A system described in any of embodiments 1 to 3, wherein the one or more connection interfaces reflecting data indicative of the sample level of the monitored user include a first connection interface including a profile card portion and a sample graph portion.

[0146] EMBODIMENT 5 5. The system of embodiment 4, wherein the profile card portion includes the name of the monitored user.

[0147] EMBODIMENT 6 The system of any one of claims 4 to 5, wherein the profile card portion includes analyte level values ​​and trend direction arrows based on data indicative of the analyte levels of the monitored user.

[0148] EMBODIMENT 7 7. The system of any one of embodiments 4 to 6, wherein the profile card portion includes a background color that indicates whether the current analyte level is within the target analyte range.

[0149] EMBODIMENT 8 The system according to any one of embodiments 4 to 7, wherein the sample graph portion includes a sample trend line.

[0150] EMBODIMENT 9 The system of any one of embodiments 4 to 8, wherein the sample graph portion includes one or more lines indicating a low glucose alarm threshold or a high glucose alarm threshold.

[0151] EMBODIMENT 10 the secondary display device further comprising a touch screen, the third party analyte monitoring application, when executed by the one or more processors, receiving an input from the touch screen corresponding to a selected point on the analyte graph portion; The system according to any one of embodiments 4 to 9, further comprising updating the profile card portion based on the input received from the touch screen.

[0152] EMBODIMENT 11 the secondary display device further comprises a touch screen, and the third party analyte monitoring application, when executed by the one or more processors, further receiving an input from the touch screen corresponding to a pull-down gesture; A system according to any one of embodiments 4 to 10, which updates the profile card section and the sample graph section based on the received input.

[0153] EMBODIMENT 12 A system according to any one of embodiments 4 to 11, wherein the profile card portion and the analyte graph portion are automatically updated at a predetermined frequency based on data indicative of the analyte level of the monitored user.

[0154] EMBODIMENT 13 A system described in any of embodiments 4 to 12, wherein the monitored user is a first monitored user, the one or more connection interfaces include a multiple connection interface including one or more profile card units, and the one or more profile card units include a first profile card unit related to the first monitored user.

[0155] EMBODIMENT 14 14. The system of embodiment 13, wherein the one or more profile card portions further include a second profile card portion relating to a second monitored user.

[0156] EMBODIMENT 15 The system of embodiment 14, wherein the first profile card portion is configured to display a first analyte level value based on data indicative of an analyte level of the first monitored user, and the second profile card portion is configured to display a second analyte level value based on data indicative of an analyte level of the second monitored user.

[0157] EMBODIMENT 16 16. The system of any one of embodiments 1 to 15, further comprising the trusted computer system, the trusted computer system comprising a cloud-based server.

[0158] EMBODIMENT 17 17. The system of any one of claims 1 to 16, wherein the sensor control device is configured to wirelessly transmit data indicative of the analyte level of the monitored user to the first reader device according to a Bluetooth or Bluetooth Low Energy communication protocol.

[0159] EMBODIMENT 18 18. The system of any one of claims 1 to 17, wherein the sensor control device is configured to wirelessly transmit data indicative of the analyte level of the monitored user to the first reader device according to a short-range wireless communication protocol.

[0160] EMBODIMENT 19 19. A system according to any one of the preceding embodiments, wherein the wireless communication circuitry of the sub-display device is configured to communicate with the trusted computer system according to an 802.11x or cellular communication protocol.

[0161] EMBODIMENT 20 A system as described in any of embodiments 1 to 19, wherein the first reading device is configured to wirelessly communicate with the sensor control device according to a first wireless communication protocol, and the first reading device is further configured to wirelessly communicate with the trusted computer system according to a second wireless communication protocol different from the first wireless communication protocol.

[0162] EMBODIMENT 21 1. A system for third-party specimen monitoring, comprising: a sensor control unit including an analyte sensor configured to contact at least a portion of a bodily fluid of a monitored user; a first reader configured to wirelessly receive data indicative of an analyte level of the monitored user from the sensor control device, the first reader further configured to transmit the data indicative of the analyte level to a trusted computer system; A sub-display device, a wireless communication circuit configured to receive from the trusted computer system sensor type information of the sensor control device and data indicative of the analyte level of the monitored user; and a sub-display device having one or more processors coupled to a memory; Equipped with The memory stores a third party analyte monitoring application that, when executed by the one or more processors, causes the one or more processors to display one or more alarm notification setting interfaces based on the sensor type information.

[0163] EMBODIMENT 22 22. The system of embodiment 21, wherein the first reading device is a smartphone.

[0164] EMBODIMENT 23 23. The system of embodiment 21 or 22, wherein the sub-display device is a smartphone.

[0165] EMBODIMENT 24 the third party analyte monitoring application, when executed by the one or more processors, further determining a type of the sensor control device based on the received sensor type information; and displaying a first set of alarm notification setting interfaces in response to determining that the type of the sensor control device is a first sensor type; in response to determining that the sensor control device type is a second sensor type, displaying a second set of alarm notification setting interfaces; 24. The system of any of embodiments 21-23, wherein the first sensor type is different from the second sensor type and the first set of alarm notification configuration interfaces is different from the second set of alarm notification configuration interfaces.

[0166] EMBODIMENT 25 25. The system of embodiment 24, wherein the first set of alarm notification setting interfaces includes a glucose reading switch.

[0167] EMBODIMENT 26 26. The system of embodiment 25, wherein the second set of alarm notification setting interfaces does not include a glucose reading switch.

[0168] EMBODIMENT 27 27. The system of any of embodiments 24-26, wherein the second set of alert notification setting interfaces includes a no recent data setting.

[0169] EMBODIMENT 28 28. The system of embodiment 27, wherein the first set of alert notification setting interfaces does not include a no recent data setting.

[0170] EMBODIMENT 29 29. The system of any one of embodiments 24 to 28, wherein the first set of alarm notification setting interfaces includes an emergency low glucose alarm setting.

[0171] EMBODIMENT 30 30. The system of embodiment 29, wherein the first set of alarm notification setting interfaces further includes an emergency low glucose threshold.

[0172] EMBODIMENT 31 The system of embodiment 30, wherein the emergency low glucose threshold is a non-changeable setting.

[0173] EMBODIMENT 32 32. The system of any one of embodiments 24-31, wherein the first set of alarm notification setting interfaces and the second set of alarm notification setting interfaces each include a low glucose alarm setting.

[0174] EMBODIMENT 33 33. The system of any of embodiments 24-32, wherein the first set of alarm notification setting interfaces and the second set of alarm notification setting interfaces each include a high glucose alarm setting.

[0175] EMBODIMENT 34 the third party analyte monitoring application, when executed by the one or more processors, further in response to determining that the type of the sensor control device is an unknown or unsupported sensor type, displaying a third set of alarm notification setting interfaces; 34. The system according to any of embodiments 24-33, wherein the third set of alert notification configuration interfaces is different from the first set of alert notification configuration interfaces and the second set of alert notification configuration interfaces.

[0176] EMBODIMENT 35 35. The system of embodiment 34, wherein the third set of alarm notification setting interfaces includes a non-alterable low glucose threshold setting or a non-alterable high glucose threshold setting.

[0177] EMBODIMENT 36 The system of any one of embodiments 21 to 35, further comprising the trusted computer system, the trusted computer system comprising a cloud-based server.

[0178] EMBODIMENT 37 37. The system of any of embodiments 21-36, wherein the sensor control device is configured to wirelessly transmit data indicative of the analyte level of the monitored user to the first reader device according to a Bluetooth or Bluetooth Low Energy communication protocol.

[0179] EMBODIMENT 38 38. The system of any one of embodiments 21 to 37, wherein the sensor control device is configured to wirelessly transmit data indicative of the analyte level of the monitored user to the first reader device according to a near-field wireless communication protocol.

[0180] EMBODIMENT 39 39. The system of any one of embodiments 21 to 38, wherein the wireless communication circuitry of the sub-display device is configured to communicate with the trusted computer system according to an 802.11x or cellular communication protocol.

[0181] EMBODIMENT 40 A system described in any of embodiments 21 to 39, wherein the first reading device is configured to wirelessly communicate with the sensor control device according to a first wireless communication protocol, and the first reading device is further configured to wirelessly communicate with the trusted computer system according to a second wireless communication protocol different from the first wireless communication protocol.

[0182] EMBODIMENT 41 1. A system for third-party specimen monitoring, comprising: a sensor control unit including an analyte sensor configured to contact at least a portion of a bodily fluid of a monitored user; a first reader configured to wirelessly receive data indicative of an analyte level of the monitored user from the sensor control device, the first reader further configured to transmit the data indicative of the analyte level to a trusted computer system; A sub-display device, a wireless communication circuit configured to receive from the trusted computer system sensor type information of the sensor control device and data indicative of the analyte level of the monitored user; and a sub-display device having one or more processors coupled to a memory; Equipped with The memory stores a third party analyte monitoring application that, when executed by the one or more processors, causes the one or more processors to display a logbook interface reflecting data indicative of the analyte level of the monitored user.

[0183] EMBODIMENT 42 42. The system of embodiment 41, wherein the first reading device is a smartphone.

[0184] EMBODIMENT 43 43. The system of embodiment 41 or 42, wherein the secondary display device is a smartphone.

[0185] EMBODIMENT 44 44. The system of any one of embodiments 41 to 43, wherein the logbook interface includes a plurality of logbook entries for a given time period.

[0186] EMBODIMENT 45 45. The system of embodiment 44, wherein the plurality of register entries are grouped by date.

[0187] EMBODIMENT 46 46. ​​The system of embodiment 44 or 45, wherein the plurality of register entries includes a first register entry, the first register entry including an analyte level value, a trend direction arrow, and a time stamp.

[0188] EMBODIMENT 47 47. The system of embodiment 46, wherein the plurality of logbook entries further includes a second logbook entry, the second logbook entry including a textual indication that the monitored user's analyte level is above an upper reportable analyte level limit.

[0189] EMBODIMENT 48 48. The system of embodiment 46 or 47, wherein the plurality of log book entries further includes a second log book entry, the second log book entry including a low glucose alert.

[0190] EMBODIMENT 49 49. The system of any of embodiments 46-48, wherein the first register entry further includes an alarm pictogram.

[0191] EMBODIMENT 50 50. The system of any one of embodiments 46-49, wherein the plurality of logbook entries includes a second logbook entry, the second logbook entry comprising an entry manually entered by the monitored user.

[0192] EMBODIMENT 51 The system of any one of embodiments 41 to 50, further comprising the trusted computer system, the trusted computer system comprising a cloud-based server.

[0193] EMBODIMENT 52 52. The system of any one of embodiments 41 to 51, wherein the sensor control device is configured to wirelessly transmit data indicative of the analyte level of the monitored user to the first reader device according to a Bluetooth or Bluetooth Low Energy communication protocol.

[0194] EMBODIMENT 53 53. The system of any one of embodiments 41 to 52, wherein the sensor control device is configured to wirelessly transmit data indicative of the analyte level of the monitored user to the first reader device according to a short-range wireless communication protocol.

[0195] EMBODIMENT 54 54. The system of any one of embodiments 41 to 53, wherein the wireless communication circuitry of the sub-display device is configured to communicate with the trusted computer system according to an 802.11x or cellular communication protocol.

[0196] EMBODIMENT 55 A system described in any of embodiments 41 to 54, wherein the first reading device is configured to wirelessly communicate with the sensor control device according to a first wireless communication protocol, and the first reading device is further configured to wirelessly communicate with the trusted computer system according to a second wireless communication protocol different from the first wireless communication protocol. [Explanation of symbols]

[0197] 25 Monitored Users 50 Third party 100 Sample Monitoring System 102 Sensor control device 104 Analyte Sensor 105 Adhesive Patches 120 Reading device 121 Input Parts 122 Display 123 Power Port 140, 141, 142 Communication Channels 150 Sensor Mounting Tool 160 Sensor Electronic Circuit 162 Analog Front End 170 Local Computer System 180 Trusted Computer Systems 190 Network 222 Communications Processor 223, 225, 230 Memory 224 Application Processor 226 Power supply 228 RF Transmitter / Receiver 232 Multi-function Transmitter / Receiver 401, 403, 411 GUI (Graphical User Interface)

Claims

1. 1. A system for third-party specimen monitoring, comprising: a sensor control unit including an analyte sensor configured to contact at least a portion of a bodily fluid of a monitored user; a first reader configured to wirelessly receive data indicative of an analyte level of the monitored user from the sensor control device, the first reader further configured to transmit the data indicative of the analyte level to a trusted computer system; A sub-display device, a wireless communication circuit configured to receive from the trusted computer system sensor type information of the sensor control device and data indicative of the analyte level of the monitored user; and a secondary display device having one or more processors coupled to a memory; Equipped with The memory stores a third party analyte monitoring application that, when executed by the one or more processors, causes the one or more processors to display one or more connection interfaces reflecting data indicative of the analyte level of the monitored user.

2. 2. The system of claim 1, wherein the one or more connection interfaces reflecting data indicative of the analyte level of the monitored user include a first connection interface including a profile card portion and an analyte graph portion.

3. The system of claim 2 , wherein the profile card portion includes a name of the monitored user.

4. 3. The system of claim 2, wherein the profile card portion includes analyte level values ​​and trend direction arrows based on data indicative of the analyte levels of the monitored user.

5. 3. The system of claim 2, wherein the profile card portion includes a background color that indicates whether a current analyte level is within a target analyte range.

6. The system of claim 2 , wherein the analyte graph portion includes an analyte trend line.

7. 3. The system of claim 2, wherein the analyte graph portion includes one or more lines indicating a low glucose alarm threshold or a high glucose alarm threshold.

8. the secondary display device further comprising a touch screen, the third party analyte monitoring application, when executed by the one or more processors, receiving an input from the touch screen corresponding to a selected point on the analyte graph portion; The system of claim 2 , further comprising: updating said profile card portion based on said input received from said touch screen.

9. the secondary display device further comprises a touch screen, and the third party analyte monitoring application, when executed by the one or more processors, further receiving an input from the touch screen corresponding to a pull-down gesture; The system of claim 2 , further comprising: a processor configured to update the profile card portion and the analyte graph portion based on the input received.

10. 3. The system of claim 2, wherein the profile card portion and the analyte graph portion are automatically updated at a predetermined frequency based on data indicative of the analyte levels of the monitored user.

11. 3. The system of claim 2, wherein the monitored user is a first monitored user, and the one or more connection interfaces include a plurality of connection interfaces including one or more profile card portions, the one or more profile card portions including a first profile card portion relating to the first monitored user.

12. The system of claim 11 , wherein the one or more profile card portions further include a second profile card portion associated with a second monitored user.

13. 13. The system of claim 12, wherein the first profile card portion is configured to display a first analyte level value based on data indicative of an analyte level of the first monitored user, and the second profile card portion is configured to display a second analyte level value based on data indicative of an analyte level of the second monitored user.

14. The system of claim 1 , further comprising the trusted computer system, the trusted computer system comprising a cloud-based server.

15. 2. The system of claim 1, wherein the sensor control device is configured to wirelessly transmit data indicative of the analyte level of the monitored user to the first reader device according to Bluetooth, Bluetooth Low Energy communication protocol, or a near field communication protocol.

16. 2. The system of claim 1, wherein the first reading device is configured to wirelessly communicate with the sensor control device according to a first wireless communication protocol, and the first reading device is further configured to wirelessly communicate with the trusted computer system according to a second wireless communication protocol different from the first wireless communication protocol.

17. The system of claim 1, wherein the third-party sample monitoring application, when executed by the one or more processors, causes the one or more processors to display one or more alarm notification setting interfaces based on the sensor type information.

18. The third-party analyte monitoring application, when executed by the one or more processors, further comprising: determining a type of the sensor control device based on the received sensor type information; and displaying a first set of alarm notification setting interfaces in response to determining that the type of the sensor control device is a first sensor type; in response to determining that the sensor control device type is a second sensor type, displaying a second set of alarm notification setting interfaces; 20. The system of claim 17, wherein the first sensor type is different from the second sensor type and the first set of alarm notification setting interfaces is different from the second set of alarm notification setting interfaces.

19. The system of claim 18, wherein the first set of alarm notification setting interfaces includes a non-alterable glucose threshold setting, and the second set of alarm notification setting interfaces does not include the non-alterable glucose threshold setting.

20. The system of claim 18, wherein the first set of alarm notification setting interfaces includes a no recent data setting, and the second set of alarm notification setting interfaces does not include the no recent data setting.

Images