Proximity-based data access authentication and authorization in a specimen monitoring system

Proximity-based authentication using BLE in medical data systems securely grants access to patient data only when the user is within range, addressing security and usability challenges in existing systems.

JP2024540792APending Publication Date: 2024-11-06DEXCOM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024500356
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-10-22
Filing Date
2022-10-17
Publication Date
2024-11-06

AI Technical Summary

Technical Problem

Existing medical data systems face challenges in securely granting access to patient data while reducing the burden on stakeholders, often relying on outdated methods like passwords or one-time codes, and lack fine-grained permission enforcement.

Method used

Implementing proximity-based authentication and authorization using low-range wireless communication networks, such as Bluetooth Low Energy (BLE), where access is granted only when a device is within a specific range of the patient's sensor system, utilizing identifiable information like recent analyte values or RSSI values to verify authenticity.

Benefits of technology

Enhances security and usability by ensuring only authorized individuals within proximity can access patient data, reducing the risk of unauthorized access and minimizing system burden.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024540792000001_ABST
    Figure 2024540792000001_ABST
Patent Text Reader

Abstract

A method and apparatus are provided for securely gaining access to patient data associated with a patient using a sensor system configured to monitor an analyte level of the patient. In one aspect, the method includes receiving, at a display device, one or more communications from the sensor system, the one or more communications including identifiable information associated with the sensor system and transmitted by the sensor system over an advertisement channel, inserting, at the display device, the identifiable information into a web request, providing, at the display device, the web request including the identifiable information to a data management system requesting access to the patient data, and gaining access to the patient data via the web browser upon the data management system verifying that the identifiable information matches second identifiable information stored in the patient data.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 262,959, filed October 22, 2021, which is assigned to the assignee hereof and is expressly incorporated by reference in its entirety herein as if fully set forth below and for all applicable purposes.

[0002] FIELD OF THEINVENTION The present application relates generally to medical devices such as analyte sensors, and more particularly to systems, devices, and methods relating to securely providing access to patient data, including analyte data generated by analyte sensors. [Background technology]

[0003] Granting or providing secure access to patient data remains difficult. As a result, there is a need for improved systems and methods that allow patient data (including medical device data, such as specimen data) to be securely accessed by patients or physicians while reducing the burden on stakeholders.

[0004] This Background is provided to introduce a brief context for the Summary and Detailed Description that follow. This Background is not intended to aid in determining the scope of the claimed subject matter, nor is it intended to be viewed as limiting the claimed subject matter to implementations that solve any or all of the disadvantages or problems presented above. Summary of the Invention [Means for solving the problem]

[0005] One or more computer systems may be configured to perform particular operations or actions by installing software, firmware, hardware, or a combination thereof on the system that, during operation, causes the system to perform the actions. One or more computer programs may be configured to perform particular operations or actions by including instructions that, when executed by a data processing device, cause the device to perform the actions.

[0006] One general aspect includes a method of securely obtaining access to patient data associated with a patient using a sensor system for monitoring an analyte level of the patient. The method also includes receiving, at a display device, one or more communications from the sensor system, the one or more communications including identifiable information associated with the sensor system and transmitted by the sensor system over an advertisement channel; inserting, at the display device, the identifiable information into a web request; providing, at the display device, the web request including the identifiable information to a data management system requesting access to the patient data; and obtaining access to the patient data via a web browser upon the data management system verifying that the identifiable information matches second identifiable information stored within the patient data. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the method.

[0007] In some embodiments, the sensor system is a continuous analyte sensor system, each of the one or more communications configured to describe an analyte value of the host to a display device, and the identifiable information may include a defined number of most recent analyte values ​​reported by the continuous analyte sensor system, and the sensor system is a continuous sensor system configured to continuously transmit communications to a display device, and the one or more communications may include a defined number of most recent communications transmitted by the continuous sensor system, and the identifiable information may include a received signal strength indicator value for the defined number of most recent communications. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium.

[0008] In some embodiments, the one or more communications are transmitted over a low-range wireless communication network, and the sensor system is configured to communicate over the low-range wireless communication network using a Bluetooth low energy (BLE) chip, and the identifiable information may include chip identifier data associated with the BLE chip. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium.

[0009] In some embodiments, the low range wireless communication network is associated with a communication protocol, which is associated with a set of data channels, and the set of advertisement channels may include an advertisement channel used to transmit one or more communications. Implementations of the described techniques may include hardware, a method or process, or computer software on a computer-accessible medium.

[0010] In some embodiments, the web request may include one or more authentication token fields maintained by the display device, and access to the patient data through the web browser is obtained upon the data management system verifying that the identifiable information matches second identifiable information stored within the patient data and that the one or more authentication token fields match one or more second authentication token fields maintained by the data management system. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium.

[0011] Another general aspect includes a method of authorizing access to patient data associated with a patient using a sensor system to monitor an analyte level of the patient. The method includes receiving, in a data management system, a web request from a display device, the web request indicating a request for access to the patient data and including identifiable information associated with the sensor system, the identifiable information being provided by one or more communications transmitted from the sensor system to the display device over an advertisement channel, verifying, in the data management system, that the identifiable information matches second identifiable information stored within the patient data, and granting, in the data management system, the request for access to the patient data based on the verifying. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the method.

[0012] In some embodiments, the sensor system is a continuous analyte sensor system, each of the one or more communications configured to describe an analyte value of the host to a display device, and the identifiable information may include a defined number of most recent analyte values ​​reported by the continuous analyte sensor system, and the sensor system is a continuous sensor system configured to continuously transmit communications to a display device, and the one or more communications may include a defined number of most recent communications transmitted by the continuous sensor system, and the identifiable information may include a received signal strength indicator value for the defined number of most recent communications. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium.

[0013] In some embodiments, the one or more communications are transmitted over a low-range wireless communication network, and the sensor system is configured to communicate over the low-range wireless communication network using a Bluetooth Low Energy (BLE) chip, and the identifiable information may include chip identifier data associated with the BLE chip. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium.

[0014] In some embodiments, the low range wireless communication network is associated with a communication protocol, which is associated with a set of data channels, and the set of advertisement channels may include an advertisement channel used to transmit one or more communications. Implementations of the described techniques may include hardware, a method or process, or computer software on a computer-accessible medium.

[0015] In some embodiments, the web request may include one or more authentication token fields maintained by the display device, and access to the patient data through the web browser is obtained upon the data management system verifying that the identifiable information matches second identifiable information stored within the patient data and that the one or more authentication token fields match one or more second authentication token fields maintained by the data management system. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium. [Brief description of the drawings]

[0016] [Figure 1A] 1 illustrates an exemplary diabetes management system according to certain embodiments disclosed herein. [Figure 1B] 1B illustrates the example diabetes management system of FIG. 1A in greater detail, according to certain embodiments disclosed herein. [Diagram 2] FIG. 1 is a flowchart diagram of an example process for securely gaining access to patient data associated with a patient collected by a sensor system for monitoring an analyte level of the patient, according to some embodiments disclosed herein. [Diagram 3] FIG. 1 is a block diagram depicting an example computing device configured to authorize access to patient data associated with a patient, in accordance with certain embodiments disclosed herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Currently, most medical device systems implement authentication and authorization using passwords or one-time codes. For example, if an interested party, such as a doctor, wants to access a patient's medical data (e.g., specimen data), the patient must upload this data to a cloud data platform. The doctor then logs into a portal associated with the cloud platform and proceeds to download the patient's previously uploaded data.

[0018] However, for the cloud data platform to allow the physician to download the patient's previously uploaded data, the cloud data platform must be able to identify the physician as authorized by the patient to access the data (e.g., the physician and patient information must be linked). For example, in some cases, the patient may have access to a mobile application that communicates with the cloud data platform, in which case the physician may ask the patient to find a one-time code that is generated by the mobile app and sent to the cloud data platform. After receiving the one-time code generated by the mobile app, the physician enters the code into a portal associated with the cloud data platform to prove that the physician is authorized by the patient to access the data. The cloud data platform then compares the code provided by the physician with the code transmitted by the mobile app to the cloud data platform. If the two codes are the same, the cloud data platform provides the physician with access to the patient's data.

[0019] Furthermore, in many existing medical data systems, once a particular user's authorization is established and access is granted, the user has read access to all medical data (i.e., has all-or-nothing read access). Thus, existing medical data systems are not configured to enforce more fine-grained permissions.

[0020] Thus, how patients and stakeholders interact with medical data may completely change. Today's systems are outdated. If the security and usability of these systems were improved, stakeholders would equally find the systems improved, if not more useful, while reducing the burden of using these systems.

[0021] Thus, certain embodiments described herein involve the use of proximity (e.g., physical distance and / or wireless communication range) to make authentication and authorization highly available and less burdensome. Using proximity in authentication and authorization is advantageous because if an attacker is not within range of a patient's body-worn device wireless signal (e.g., a transmitter Bluetooth Low Energy (BLE)), the attacker cannot hear or intercept data from that signal (e.g., a transmitter BLE antenna signal). In rare cases, some attackers may be equipped with more advanced equipment to extend the listening range of BLE signals. However, if a stakeholder is willing to accept the minimal risks associated with a close-proximity attacker device, the stakeholder can gain a high degree of utility in their health care system.

[0022] 1A depicts a disease management system 100 ("system 100"), such as a diabetes management system, that may be used in connection with embodiments of the present disclosure involving collecting, monitoring, and / or providing information regarding analyte values ​​present in a user's body, including, for example, the user's blood glucose values. System 100 depicts aspects of an analyte sensor system 8 (hereinafter "SS8") that may be communicatively coupled to display devices 110, 120, 130, and 140 and / or a server system 134.

[0023] In some embodiments, the SS8 is provided for measuring an analyte in a host or user. By way of overview and example, the SS8 may be implemented as an encapsulated microcontroller that performs sensor measurements, generates analyte data (e.g., by calculating values ​​of continuous glucose monitoring data), and engages in wireless communication (e.g., via Bluetooth and / or other wireless protocols) to transmit such data to a remote device, such as display device 110, 120, 130, 140, and / or server system 134. Paragraphs

[0137] -

[0140] and Figures 3A, 3B, and 4 of U.S. Patent Application Publication No. 2019 / 0336053 further describe an on-skin sensor assembly that may be used in connection with the SS8 in certain embodiments. Paragraphs

[0137] -

[0140] and Figures 3A, 3B, and 4 of U.S. Patent Application Publication No. 2019 / 0336053 are incorporated herein by reference.

[0024] In certain embodiments, the SS8 includes an analyte sensor electronics module 12 and an analyte sensor 10 associated with the analyte sensor electronics module 12. In certain embodiments, the analyte sensor electronics module 12 includes electronic circuitry associated with measuring and processing the analyte sensor data or information, including algorithms associated with processing and / or calibrating the analyte sensor data / information. The analyte sensor electronics module 12 may be physically / mechanically connected to the analyte sensor 10 and may be integral to (i.e., non-removably attached to) the analyte sensor 10 or may be removably attached to the analyte sensor 10.

[0025] The analyte sensor electronics module 12 may also be electrically coupled to the analyte sensor 10 such that the components may be electromechanically coupled to one another (e.g., (a) prior to insertion into the patient's body or (b) during insertion into the patient's body). The analyte sensor electronics module 12 may include hardware, firmware, and / or software that enables measurement and / or estimation of a level of an analyte in a host / user via the analyte sensor 10 (which may / may include, for example, a glucose sensor). For example, the analyte sensor electronics module 12 may include one or more potentiostats, a power supply for powering the analyte sensor 10, other components useful for signal processing and data storage, and a telemetry module for transmitting data from the sensor electronics module to one or more display devices. The electronics may be affixed to a printed circuit board (PCB) or platform within the SS8 and may take a variety of forms. For example, the electronics may take the form of an integrated circuit (IC), such as an Application-Specific Integrated Circuit (ASIC), a microcontroller, a processor, and / or a state machine.

[0026] The analyte sensor electronics module 12 may include sensor electronics configured to process sensor information, such as sensor data, and generate transformed sensor data and displayable sensor information. Examples of systems and methods for processing sensor analyte data are described in more detail herein and in U.S. Pat. Nos. 7,310,544 and 6,931,327, as well as U.S. Patent Publication Nos. 2005 / 0043598, 2007 / 0032706, 2007 / 0016381, 2008 / 0033254, 2005 / 0203360, 2005 / 0154271, 2005 / 0192557, 2006 / 0222566, 2007 / 0203966, and 2007 / 0208245, all of which are incorporated by reference in their entireties.

[0027] The analyte sensor 10 is configured to measure a concentration or level of an analyte in a host. The term analyte is further defined in paragraph

[0117] of U.S. Patent Application Publication No. 2019 / 0336053, which paragraph

[0117] is incorporated herein by reference. In some embodiments, the analyte sensor 10 includes a continuous glucose sensor, such as a subcutaneous, transdermal (e.g., transcutaneous), or intravascular device. In some embodiments, the analyte sensor 10 can analyze multiple intermittent blood samples. The analyte sensor 10 can use any glucose measurement method, such as enzymatic, chemical, physical, electrochemical, spectrophotometric, polarimetric, calorimetric, iontophoretic, radiometric, immunochemical, etc. Additional details regarding continuous glucose sensors are provided in paragraphs

[0072] -

[0076] of U.S. Patent Application Publication No. 13 / 827,577. Paragraphs

[0072] to

[0076] of U.S. patent application Ser. No. 13 / 827,577 are incorporated herein by reference.

[0028] With further reference to FIG. 1A , display devices 110, 120, 130, and / or 140 can be configured to display displayable sensor information that may be transmitted by sensor electronics module 12 (e.g., in customized data packages transmitted to the display devices based on respective preferences). Each of display devices 110, 120, 130, or 140 may include a display, such as a touchscreen display 112, 122, 132, and / or 142, for displaying sensor information and / or analyte data to a user and / or receiving input from a user. For example, a graphical user interface (GUI) may be presented to the user for such purposes. In certain embodiments, the display device may include other types of user interfaces, such as a voice user interface, instead of or in addition to a touchscreen display, for communicating sensor information to a user of the display device and / or receiving user input. In particular embodiments, one, some, or all of the display devices 110, 120, 130, 140 may be configured to display or otherwise communicate sensor information as it is communicated from the sensor electronics module 12 (e.g., within a data package transmitted to the respective display device) without any additional anticipated processing required for calibration and / or real-time display of the sensor data.

[0029] 1A may include custom or dedicated display devices, such as the analyte display device 110, specifically designed to display a certain type of displayable sensor information (e.g., in certain embodiments, numerical values ​​and / or arrows) associated with the analyte data received from the sensor electronics module 12. In certain embodiments, one of the display devices 110, 120, 130, 140 includes a smartphone, such as a mobile phone 120 based on Android, iOS, or another operating system configured to display a graphical representation of the continuous sensor data (e.g., including current and / or historical data). In certain embodiments, the disease management system 100 further includes a medical delivery device (e.g., an insulin pump or pen). The sensor electronics module 12 may be configured to transmit the sensor information and / or the analyte data to the medical delivery device. A medical delivery device (not shown) may be configured to administer a certain dosage of insulin or another medication to a user based on sensor information and / or analyte data (which may include, for example, a recommended insulin dosage) received from the sensor electronics module 12.

[0030] Server system 134 may be used to collect analyte data directly or indirectly from SS8 and / or multiple display devices, for example, according to embodiments described herein, perform analyses on the analyte data, generate generic or personalized models of glucose levels and profiles, provide services or feedback including from individuals or systems remotely monitoring the analyte data, perform or assist SS8 and display devices 150 with identifying, authenticating, etc. It should be noted that in certain embodiments, server system 134 may represent multiple systems or multiple computing devices performing the functions of server system 134 (e.g., in a distributed manner).

[0031] FIG. 1B illustrates a more detailed view of system 100 including display device 150 communicatively coupled to SS8. In certain embodiments, display device 150 may be any one of display devices 110, 120, 130, and 140 of FIG. 1A. A communication path between SS8 and display device 150 is shown as communication path 180. In certain embodiments, SS8 and display device 150 are configured to communicate wirelessly over communication path 180 using a low-range wireless communication network (i.e., a communication network using one or more low-range and / or low-range wireless communication protocols). Examples of low-range and / or low-range wireless communication protocols include Bluetooth and Bluetooth Low Energy (BLE) protocols. In certain embodiments, other low-range wireless communications may include Near Field Communication (NFC), radio frequency identification (RFID) communication, infrared (IR) communication, and optical communication. In certain embodiments, wireless communication protocols other than low-range and / or low-distance wireless communication protocols, such as WiFi Direct, may be used for communication path 180. Display device 150 is also configured to connect to a network 190 (e.g., a local area network (LAN), a wide area network (WAN), the Internet, etc.). For example, display device 150 may connect to network 190 via a wired (e.g., Ethernet) or wireless (e.g., WLAN, wireless WAN, cellular, mesh network, personal area network (PAN), etc.) interface. Display device 150 may communicate with server system 134 via network 190. A communication path between display device 150 and server system 134 is shown as communication path 181 via network 190.

[0032] It should be noted that in certain embodiments, SS8 may be capable of independently (e.g., wirelessly) communicating with server system 134 via network 190. The independent communication path between SS8 and server system 134 is shown as communication path 182. However, in certain other embodiments, SS8 may not be configured with the hardware / software necessary to establish an independent wireless communication path with server system 134, for example, via network 190. In such embodiments, SS8 may communicate with server system 134 via display device 150. An indirect or pass-through communication path between SS8 and server system 134 is shown as communication path 183.

[0033] System 100 further includes server system 134, which includes a server 135 coupled to storage 136 (e.g., one or more computer storage systems, cloud-based storage systems and / or services, etc.). In certain embodiments, server system 134 may be located or execute within a public or private cloud. In certain embodiments, server system 134 may be located or execute on-premise ("on-prem"). As discussed, server system 134 is configured to receive, collect, and / or monitor information, including analyte data and related information, and encryption / authentication information, from SS8 and / or display device 150. Such information may include inputs responsive to analyte data or inputs (e.g., a user's glucose readings and other physiological / behavioral information) received in association with an analyte monitoring or sensor application operating on SS8 or display device 150. This information may be stored in storage 136 and processed by an analytics engine or the like that may perform analytics on the information. An example of an analyte sensor application that may be executable on display device 150 is analyte sensor application 121, as described further below.

[0034] In certain embodiments, the server system 134 at least partially directs communications between the SS8 and the display device 150, for example, to facilitate authentication between them. Such communications include messaging (e.g., advertisements, commands, or other messaging), message delivery, and analyte data. For example, in certain embodiments, the server 134 may process and exchange messages between the SS8 and the display device 150 related to frequency bands, timing of transmissions, security, alarms, etc. In certain embodiments, the server system 134 may also update information stored in the SS8 and / or the display device 150. In certain embodiments, the server system 134 may transmit / receive information to / from the SS8 and / or the display device 150 in real-time or sporadically. Additionally, in certain embodiments, the server system 134 may implement cloud computing capabilities for the SS8 and / or the display device 150.

[0035] The server system 134 may also be in communication with a web server (as part of a data management system) that provides access to patient data, including specimen data generated by SS8 and transmitted to the server system 134. For example, the web server may be accessed by patients and physicians by web browsers on a variety of devices. The server system 134 may also be accessible by software applications that may be installed locally on the patient or physician devices to access the patient's data.

[0036] FIG. 1B also illustrates the components of the SS8 in more detail. As shown, in certain embodiments, the SS8 includes an analyte sensor 10 coupled to a sensor electronics module 12. The sensor electronics module 12 includes a sensor measurement circuit 13 coupled to the analyte sensor 10 for processing and managing sensor data. The sensor measurement circuit 13 may also be coupled to a processor 11. In some embodiments, the processor 11 may perform some or all of the functions of the sensor measurement circuit 13 for obtaining and processing sensor measurements from the analyte sensor 10. The processor 11 may also be coupled to a storage 14 and a real time clock (RTC) 17 for storing and tracking sensor data. In addition, the processor 11 may further be coupled to a connection interface 15, including a wireless unit or transceiver (TRX) 16 for transmitting sensor data and receiving requests and commands from an external device, such as a display device 150. As used herein, the term transceiver generally refers to a device or collection of devices that allows the SS8 to transmit and receive data (e.g., wirelessly). The SS 8 may further include storage 14 for storing and tracking sensor data and a real-time clock (RTC) 17. In some embodiments, it is contemplated that the sensor measurement circuitry 13 may perform all of the functions of the processor 11, and vice versa.

[0037] The transceiver 16 may be configured with the necessary hardware and wireless communication protocols to enable wireless communication between the SS8 and other devices, such as the display device 150 and / or the server system 134. For example, as described above, the transceiver 16 may be configured with the necessary hardware and communication protocols to establish a Bluetooth or BLE connection with the display device 150. As one skilled in the art will appreciate, in such examples, the necessary hardware may include a Bluetooth or BLE security manager and / or other Bluetooth or BLE related hardware / software modules configured for the Bluetooth or BLE communication standards. In some embodiments in which the SS8 is configured to establish an independent communication path with the server system 134, the transceiver 16 may be configured with the necessary hardware and communication protocols to establish a wireless connection to the network 190 (e.g., a long-range wireless cellular communication protocol, such as GSM, CDMA, LTE, VoLTE, 3G, 4G, 5G communication protocol, etc.) to connect with the server system 134. As discussed elsewhere, other short-range protocols may also be used for communication between the display device 150 and the SS8, such as NFC, RFID, etc.

[0038] 1B also illustrates components of the display device 150 in more detail. As shown, the display device 150 includes a connection interface 128, a processor 126, a memory 127, a real-time clock (RTC) 163, a display 125 for presenting a graphical user interface (GUI), and a storage 123. A bus (not shown herein) may be used to interconnect the various elements of the display device 150 and transfer data between these elements. The connection interface 128 includes a transceiver (TRX) 129 used to receive sensor data from the SS8 and to transmit requests, commands, and / or data to the SS8 and the server system 134. The transceiver 129 is coupled to other elements of the display device 150 via the connection interface 128 and / or the bus. The transceiver 129 may include multiple transceiver modules capable of operating on different wireless standards. For example, transceiver 129 may be configured with one or more communication protocols, such as a wireless communication protocol for establishing a wireless communication path with network 190 and / or a low-range wireless communication protocol (e.g., Bluetooth or BLE) for establishing wireless communication path 180 with SS8. Additionally, connection interface 128 may include additional components for controlling wireless and / or wired connections, in some cases, such as baseband and / or Ethernet modems, audio / video codecs, etc.

[0039] In some embodiments, when a standardized communication protocol is used between the display device 150 and the SS8, commercially available transceiver circuits may be utilized that incorporate processing circuitry for handling low level data communication functions such as managing data encoding, transmission frequency, handshaking protocols, security, and the like. In these embodiments, the processor 126 of the display device 150 and / or the processor 11 of the SS8 may not need to manage these operations, but instead manage high level functions such as providing desired data values ​​for transmission, powering up or down, setting the rate at which messages are transmitted, and the like. Instructions and data values ​​for implementing these high level functions may be provided to the transceiver circuitry via a data bus and transfer protocol established by the manufacturers of the transceivers 129 and 16. However, in embodiments where a standardized communication protocol is not used between the transceivers 129 and 16 (e.g., when a non-standardized or modified protocol is used), the processors 126 and 11 may be configured to execute instructions associated with a proprietary communication protocol (e.g., one or more of the communication protocols described herein) to control and manage their respective transceivers. Additionally, where non-standardized or modified protocols are used, customized circuitry may be used to service such protocols.

[0040] The processor 126 may include a processor sub-module, which may include, by way of example, an application processor that interfaces with and / or controls other elements of the display device 150 (e.g., the connection interface 128, the analyte sensor application 121 (hereinafter “sensor application 121”), the display 125, the RTC 163, the memory 127, the storage 123, etc.). In certain embodiments, the processor 126 is configured to perform functions related to device management, such as, for example, managing lists of available or previously paired devices, information regarding network conditions (e.g., link quality, etc.), information regarding the timing, type, and / or structure of messaging exchanged between the SS8 and the display device 150, etc. The processor 126 may be further configured to receive and process user inputs, such as, for example, a user fingerprint (e.g., for authorizing a user's access to data or for use in authorizing / encrypting data, including analyte data), and analyte data.

[0041] The processor 126 may include and / or be coupled to circuits such as logic circuits, memory, battery and power circuits, and other circuit drivers for peripheral and audio components. The processor 126 and any sub-processors thereof may include logic circuits for receiving, processing, and / or storing data received and / or input to the display device 150, as well as data transmitted or delivered by the display device 150. As described above, the processor 126 may be coupled by a bus to the display 125, the connection interface 128, the storage 123, etc. Thus, the processor 126 may receive and process electrical signals generated by these respective elements, and thus perform various functions. As an example, the processor 126 may access stored content from the storage 123 and memory 127 at the direction of the analyte sensor application 121, and process the stored content for display by the display 125. Additionally, the processor 126 may process the stored content for transmission to the SS8 and / or server system 134 via the connection interface 128. Display device 150 may include other peripheral components not shown in detail in FIG. 1B.

[0042] In certain embodiments, memory 127 may include volatile memory, such as random access memory (RAM), for storing data and / or instructions for software programs and applications, such as analyte sensor application 121. Display 125 presents a GUI associated with operating system 162 and / or analyte sensor application 121. In various embodiments, a user may interact with analyte sensor application 121 via a corresponding GUI presented on display 125. By way of example, display 125 may be a touch screen display that accepts touch input. Analyte sensor application 121 may process and / or present analyte related data received by display device 150 and present such data via display 125. Additionally, analyte sensor application 121 may be used to obtain, access, display, control, and / or interface with analyte data and associated messaging and processes associated with SS8 (e.g., and / or any other medical device (e.g., insulin pump or pen) communicatively coupled to display device 150), as described in further detail herein.

[0043] Storage 123 may be non-volatile storage for storing software programs, instructions, data, and the like. For example, storage 123 may store analyte sensor application 121, which when executed using processor 126, for example, receives input (e.g., via traditional hard / soft keys or touch screen, voice detection, or other input mechanisms) and allows a user to interact with analyte data and associated content via display 125. In various embodiments, storage 123 may also store user input data and / or other data collected by display device 150 (e.g., input from other users gathered via analyte sensor application 121). Storage 123 may further be used to store large amounts of analyte data received from SS8 (or any other medical data received from other medical devices (e.g., insulin pumps, pens, etc.) for later retrieval and use, for example, to determine trends and trigger alerts.

[0044] As described above, the SS8, in certain embodiments, collects analyte data from the analyte sensor 10 and transmits the same or modified versions of the collected data to the display device 150. Data points regarding the analyte value may be collected and transmitted over the life of the analyte sensor 10 (e.g., ranging from 1 to 30 days or more). New measurements may be transmitted frequently enough to adequately monitor the blood glucose level. In certain embodiments, rather than having the transmitting and receiving circuitry of each of the SS8 and the display device 150 in continuous communication, the SS8 and the display device 150 may periodically and / or periodically establish a communication channel between each other. Thus, in such embodiments, the SS8 may communicate with the display device 150 at, for example, predetermined time intervals. The length of the predetermined time interval may be selected to be long enough so that the SS8 does not consume too much power by transmitting data more frequently than necessary, but frequent enough to provide substantially real-time sensor information (e.g., measured glucose values ​​or analyte data) to the display device 150 for output to a user (e.g., via the display 125). The predetermined time interval is every five minutes in some embodiments, although it is understood that this time interval can be modified to be any desired length of time. In other embodiments, transceivers 129 and 16 may be in continuous communication. For example, in certain embodiments, transceivers 129 and 16 may establish a session or connection between them and continue to communicate together until the connection is lost.

[0045] The analyte sensor application 121 may be downloaded, installed, and initially configured / setup on the display device 150. For example, the display device 150 may obtain the analyte sensor application 121 from the server system 134 over a network, such as network 190, or from another source, such as an application store. Following installation and setup, the analyte sensor application 121 may be configured to access, process, and / or interface with analyte data (e.g., whether stored on the server system 134, stored locally by the storage 123, the SS8, or stored by any other medical device). By way of example, the analyte sensor application 121 may present menus including various controls or commands that may be performed in connection with the operation of the SS8, the display device 150, one or more other display devices (e.g., display devices 110, 130, 140, etc.), and / or one or more other partner devices, such as an insulin pump. For example, the analyte sensor application 121 may be used to interface with or control other display devices and / or partner devices, for example to deliver or make available analyte data to other display devices and / or partner devices, including, for example, by receiving / sending analyte data directly from / to other display devices and / or partner devices and / or by sending instructions for the SS8 and other connected display devices and / or partner devices.

[0046] As discussed above, certain embodiments herein include proximity-based authentication and authorization techniques for providing access to patient data. The use of proximity in data access, authentication, and / or authorization in a data management system that controls access to medical data can be illustrated by several exemplary use cases. A first use case may involve a patient who wishes to gain access to his or her own data using a device. A second use case may involve a doctor in a clinic who wishes to gain access to the data of a patient who is in the clinic.

[0047] In a first exemplary use case, a patient who monitors their specimen data using SS8 may wish to view their longitudinal medical data, including specimen data that was previously generated using SS8. For example, SS8 may be used continually by the patient to generate specimen data that is periodically transmitted to server system 134 (e.g., via display device 150) and stored, for example, in storage 136.

[0048] The patient may then reach for a display device (hereinafter "DD") (e.g., display device 150, which may be any one of display devices 120, 130, or a laptop or any other computing system with low or short range communication capabilities and an operating system capable of running a web browser) and proceed to use the browser to bring up a website associated with the data management system that controls access to the data stored in server system 134. Note that in the embodiments described herein, the DD may be different or the same as the display device, which is in constant communication with SS8 to continuously receive the patient's analyte measurements.

[0049] Continuing with the above example, a patient launches a website to access their specimen data (and / or data reports) that may have been previously generated using SS8 or a different sensor system (previous SS). The data management system may be an on-premise or cloud-based server or system and may include a web server configured to provide access to data stored in the server system 134 in response to web requests via a browser running on the DD. The DD may turn on its Bluetooth, Bluetooth Low Energy (BLE) (or any other low range communication component) communication module and antenna and may scan for advertisements from SS8.

[0050] When a patient attempts to access a website to view their data, the browser may be configured to insert SS identifiable data into the web request (e.g., HTTP / HTTPS GET request) generated by the web browser. The SS identifiable data identifies the SS8 and indicates to the data management system that the person requesting access to the data is in proximity to the SS8 and should therefore be trusted. Different types of SS identifiable data that can be verified by the web server (or other component or data management system) as being associated with the patient's SS8 are discussed in more detail below. Once the web server verifies that the SS identifiable data belongs to the SS associated with the patient for whom data is being requested, the web server may then grant access to the data request and perform the login. This login may be accomplished without a password or may be done with a password to achieve multi-factor authentication.

[0051] To configure the web browser to insert the SS identifiable information into the web request, one of a variety of techniques may be used. For example, a software application installed locally on the DD may be configured to receive the SS advertisement and communicate with the web browser to insert the SS identifiable information into the web request. In another example, the web browser may be configured to communicate with an API provided by a low-range communication stack in the DD. For example, the web browser may be configured to communicate with a BLE API provided by a BLE stack in the DD. In such an example, the web browser may receive the SS identifiable information directly from the BLE stack of the DD. In a particular embodiment, the web browser may be configured to continuously communicate with the BLE stack using the BLE API to scan for any BLE advertisements that may be received by the BLE stack.

[0052] Using SS8 advertised data as a method of authenticating a patient is advantageous because an attacker generally cannot access or intercept the data that is within the SS8 advertisements. As long as an attacker is not within range to view (e.g., intercept, listen, etc.) the patient's SS8 advertisements, the patient's access to their own data can be considered a form of secure data access.

[0053] In this model, multiple techniques may be used to further increase the likelihood that an attacker would not be able to gain access to the patient's data. For example, if the attacker is in close proximity and only listening to the patient's SS8, the attacker will gain read access to the patient's data through the website. So, one technique to reduce the attacker's ability to access the patient's data is to require the patient's username (which is not secret but still requires guessing the correct value) on the website. Additionally, the number of times that usernames can be tried on the website for a particular patient may be limited.

[0054] The assumption that an attacker cannot access a patient's data stream when the attacker is not in close proximity to the patient's sensor system is based on another assumption that an attacker cannot guess or brute force the SS identifiable data in the SS8 advertisement when the attacker is not within an acceptable proximity range. Accordingly, certain embodiments described herein propose several ways to enforce or use SS identifiable information that an attacker would not be able to brute force include.

[0055] For example, in certain embodiments, the identifiable SS information may include the last N analyte values ​​(e.g., blood glucose values), where N is a positive integer value. Because the web server has access to the patient's analyte data (e.g., stored in storage 136) that is current and includes the last N glucose values, the web server is able to verify the patient's last N glucose values. Note that the patient's analyte data is generated and provided by SS8 and transmitted (e.g., directly or through the analyte sensor app 121 on the display device 150) to a server system 134 that includes or communicates with a data management system, including the web server. If the web server can determine that the last N glucose values ​​in the patient's data are the same as the last N glucose values ​​in the SS8 advertisement received as part of the web request, the web server allows access to the patient data.

[0056] In another example, the identifiable SS information may include the last N RSSI values. For example, the analyte sensor app 121 running on the display device 150 may have received the last five consecutive signals having five RSSI values ​​and transmit those values ​​as part of the patient data to the server system 134. In such an example, if the web server can determine that the last N RSSI values ​​in the patient data are the same as the last N RSSI values ​​in the SS8 advertisement received as part of the web request, then the web server allows access to the patient data.

[0057] In another example, the identifiable SS information may include a secret value that cannot be easily brute-forced. For example, the secret value may be a 128-bit or 256-bit random secret. This secret value may also be stored as part of the patient's data in the server system 134 and may be used by the web server to compare against secret values ​​in SS8 advertisements received as part of a web request.

[0058] In certain embodiments, the identifiable SS information may include BLE chip specific information associated with the SS8. The BLE chip specific information may be received by the server system 134 as part of the patient data during a pairing process between the SS8 and the display device 150, for example. The web server may match the BLE chip specific information stored as part of the patient data to the BLE chip specific information in the SS8 advertisement received as part of the web request.

[0059] In certain embodiments, the identifiable information may be associated with an analyte sensor application 121 running on a display device 150 that the patient uses to continuously monitor analyte measurements. For example, the identifiable information may include a unique app ID, a signed app value, etc. The app-related identifiable information may be stored as part of the patient's data in the server system 134 and may be used by the web server to compare with identifiable information in SS8 advertisements received as part of a web request.

[0060] In certain embodiments, the identifiable information may be associated with the particular display device 150 that the patient uses to continuously monitor analyte measurements. The display device associated identifiable information may be stored as part of the patient data in the server system 134 and may be used by the web server to compare with identifiable information in SS8 advertisements received as part of a web request.

[0061] In certain embodiments, the identifiable information may be configured to expire to ensure that the data in the sensor system advertisement does not always give one access to the patient data set. Thus, in certain embodiments, the identifiable information is configured to change over time. This can be achieved in many ways. For example, using the last N glucose values ​​or the last N RSSI values ​​as the identifiable information ensures that the identifiable information changes periodically.

[0062] For identifiable information that cannot be guaranteed to change (e.g., a 128-bit or 256-bit random secret), the SS8 may be configured to perform some function such as identifiable information = function (dynamic value, master_secret). In a particular embodiment, the function is a cryptographic hash function such as SHA3 or AES. If the identifiable information is long enough and changes over time, the data management system can determine if the calculated identifiable information is valid as long as the data management system has access to the master_secret and the function used to calculate the identifiable information.

[0063] As an example, SS8 can compute the identifiable information = AES(nonce_counter, tx_master_key). A DD (e.g. laptop) attempting to access the patient's data transmits the identifiable information to the web server as part of the web request. A data management system with access to the tx_master_key can compute the identifiable information because it possesses the tx_master_key. The data management system can therefore compare the tx_master_key it possesses with the tx_master_key in the AES and, if they are the same, grant access to the patient's data.

[0064] In certain embodiments, the identifiable information may expire after a certain amount of time (e.g., T=30 minutes), which may be configurable. When the identifiable information expires, the DD needs to obtain new identifiable information from the SS8. The SS8 may calculate new identifiable information, for example, every T (e.g., 30) minutes. As an example, the new identifiable information may be calculated in the form identifiable information=AES(nonce_counter+1, tx_master_key).

[0065] In certain embodiments, the wireless communication range may be intentionally reduced (by reducing the transmission power) to reduce the likelihood of an attack. Regardless of the distance or wireless protocol used, the probability that an attacker can receive data from a transmitted signal can be reduced by having the SS8 use less transmission power. By using less power, an attacker would 2) have to be much closer to the SS8 to receive the advertisements and 3) have to use better equipment to hear the signals from the SS8.

[0066] In certain embodiments, the number of data points required for authentication to access a patient's information may be increased for added security, and thus any two or more methods or types of identifiable information may be used in combination for authentication.

[0067] As discussed above, a second use case in which proximity may be used in data access, authentication, and / or authorization may involve a doctor at a clinic who wishes to gain access to a patient's data who is at the clinic. In such an example, a patient who is wearing an SS8 and also possesses a display device 150 is scheduled to be seen by the doctor. In some cases, one method of providing the doctor with access to the patient's data may involve having the doctor request the patient's data by clicking on a link and, in response, asking the patient to generate and display a unique code, e.g., a QR code, using the analyte sensor app 121. The doctor can use his or her DD to copy the QR code data and use that data as an authentication token. However, this approach requires multiple actions and interactions to be performed by the doctor and the patient in order for the doctor to gain access to the data.

[0068] Thus, in certain embodiments, a doctor may access a website using a DD (e.g., a laptop, iPad, iPhone, or any other mobile device in a clinic configured with wireless communication capabilities such as Bluetooth or BLE capabilities) to access the patient's data. The website may be associated with the data management system or may communicate with a web server that communicates with the data management system. Similar to the first use case, in the second user case, the doctor's DD may be enabled to scan and / or receive advertisements transmitted by the patient's SS8 and insert identifiable information in the advertisement into the HTTP / HTTPS GET request generated by the web browser to access the website. The identifiable information indicates to the data management system that the person requesting access to the data is in proximity to the SS8 and should therefore be trusted. Different types of SS identifiable data that can be verified by the web server (or other components or data management systems) as being associated with the patient's SS8 have been discussed above.

[0069] To configure the web browser to insert the SS identifiable information into the web request, one of a variety of techniques may be used. For example, a software application installed locally on the physician's DD may be configured to scan and / or receive SS advertisements and communicate with the web browser to insert the SS identifiable information into the web request. In another example, the web browser may be configured to communicate with an API provided by a low-range communication stack in the DD. For example, the web browser may be configured to communicate with a BLE API provided by a BLE stack in the DD. In such an example, the web browser may receive the SS identifiable information directly from the BLE stack of the DD. In a particular embodiment, the web browser may be configured to continually communicate with the BLE stack using the BLE API to scan for any BLE advertisements that may be received by the BLE stack.

[0070] In certain embodiments, the web browser may be configured to determine when a particular patient will visit and automatically send a web request to the web server with the identifiable information received from the patient's SS8 and a list of the names of patients scheduled to visit on that day. For example, the doctor's DD may run software or have access to a website or system that has a list of the names and other information of all patients scheduled to visit during a particular day and the time of the visit. Thus, once a patient's scheduled visit is completed, the doctor's DD may continuously or periodically scan for identifiable information associated with that patient. When the patient's SS sends an advertisement to the doctor's DD, the DD inserts the identifiable information into the web request, as well as any secondary information about the patient (e.g., public information such as name, address, etc.). On the other hand, the web server checks the patient data associated with the patient (based on the patient name) to see if the identifiable data received in the web request matches any of the identifiable dates in the patient data. If there is a match, the web server provides access to the patient's data. In such an example, no interaction is required by either the doctor or the patient.

[0071] In a particular embodiment, there may be more than one patient in the clinic at the same time, in which case the doctor's DD may transmit a request to the display device 150 of the patient scheduled to visit next for the display device 150 to play an audible sound (e.g., a particular audible sound). The doctor's DD may then have a microphone to determine the particular audible sound received. If there is a match, the doctor's DD may determine and confirm that the advertisement being received from the SS belongs to the patient scheduled to visit next. In another example, the doctor's DD may transmit a request to the display device 150 of the patient scheduled to visit next for the display device 150 to transmit the last N RSSI values ​​to the server system 134. In that example, the SS identifiable information received in the advertisement received from the patient's SS8 may include the same N RSSI values. The web server may then compare the RSSI value in the patient data with the RSSI value received in the SS8 advertisement, and if they match, grant the doctor access to the data.

[0072] In a particular embodiment, in the second use case, the DD of the physician or follower may transmit a BLE message that may be picked up by the display device 150 (e.g., by the analyte sensor app 121 running on the display device 150). The message may be a request to allow the DD to access the patient's data for N months (e.g., 24 months). Then, on the display device 150, the patient may see a pop-up window asking the patient for permission to allow the DD to access the patient's data. If the patient approves, the display device 150 transmits a secret token value that allows the display device 150 to retrieve the patient's data for the next N=24 months. At the end of these 24 months, the token times out.

[0073] In another embodiment, the patient can change the length of the token validity period, but this increases the complexity of fine-grained access control. In another embodiment, the person controlling the laptop seeking access (e.g., the patient or doctor) can configure the request to allow N=12 months or N=60 months.

[0074] 2 is a flow diagram of an example process 200 for a DD (e.g., DD 150 of FIG. 1B) to gain access to patient data stored by a server system (e.g., server system 134 of FIG. 1B) using proximity-based authentication techniques. As described above, the patient data stored by the server system may have been collected by and received from an SS (e.g., SS 8 of FIG. 1A-1B) to monitor the patient's analyte levels.

[0075] As depicted in FIG. 2, process 200 begins in block 201 when a DD receives one or more communications from an SS. In some embodiments, the SS transmits the one or more communications over a low-range or short-range wireless communication network. As described above, the low-range wireless communication network may use one or more low-range / short-range wireless communication protocols, such as at least one of Bluetooth, BLE, RFID, or NFC. In some embodiments, the low-range wireless communication network is configured such that only devices within a threshold vicinity of the SS can receive the communications transmitted by the SS using the low-range wireless communication network.

[0076] In some embodiments, the low-range wireless communication network is associated with a communication protocol, which defines a set of data channels and a set of communication channels. A data channel is a communication channel that can be used to transmit data from a sending device to a destination device (e.g., from SS to DD) after establishing a connection between the two devices. An advertisement communication channel is a communication channel that can be used to broadcast data from a sending device (e.g., from SS) without establishing a connection with a receiving device (e.g., with DD). In some embodiments, the frequencies of the advertisement channels are selected to minimize radio interference (e.g., interference from nearby Wi-Fi activity) on these channels. For example, BLE uses three communication channels with frequencies of 2402 MHz, 2426 MHz, and 2480 MHz, respectively. BLE also uses 37 data channels.

[0077] In some embodiments, the SS transmits communications using an advertisement channel of a communication protocol associated with a low-range or short-range wireless communication network. Transmitting communications using an advertisement channel is advantageous because the advertisement channel does not require full connectivity between the SS and any receiving device (e.g., DD), thus minimizing network connection overhead for both the SS and the receiving device. Furthermore, the frequency of the advertisement channel may be selected to minimize radio interference, such as Wi-Fi activity, on these channels, so using the advertisement channel may minimize the impact of the advertisement channel communications on the SS's WiFi-enabled communications (e.g., Wi-Fi-enabled communications between the SS and a server system or other nearby Wi-Fi communications).

[0078] In block 202, the DD inserts identifiable information determined based on the one or more communications into the web request. In some embodiments, the identifiable information includes an authentication token described in the one or more communications. In some embodiments, the DD determines the identifiable information based on calculated features of the one or more communications.

[0079] In some embodiments, the SS is a continuous analyte sensor system configured to transmit one or more analyte values ​​of the host via advertisement channel communications. In such embodiments, the identifiable information may include a defined number (i.e., N) of the most recent analyte values ​​transmitted by the continuous analyte sensor system. In some of the described embodiments, each communication transmitted from the SS via the advertisement channel describes the most recent analyte value of the host, and the identifiable information is determined based on the analyte values ​​described in the most recent N advertisement channel communications. Thus, in some embodiments, to determine the identifiable information based on the advertisement channel communications, the DD (i) collects the most recent N advertisement channel communications from the SS, (ii) extracts the analyte values ​​reported by the collected communications, and (iii) determines the identifiable information based on the extracted analyte values. In some embodiments, in addition to transmitting the analyte values ​​of the host using advertisement channel communications, the SS also transmits the analyte values ​​to a server system via a secure connection.

[0080] As another example, in some embodiments, the sensor system is a continuous sensor system configured to continuously transmit communications to the display device, and the one or more communications include a defined number (N) of the most recent communications transmitted by the continuous sensor system. In some of the described embodiments, the identifiable information includes RSSI values ​​for the defined number of the most recent communications. Thus, in some embodiments, to determine the identifiable information, the SS (i) collects the most recent N advertisement channel communications from the SS, (ii) determines RSSI values ​​of the collected communications, and (iii) determines the identifiable information based on the determined RSSI values. In some embodiments, the SS also transmits a received signal strength indicator value for the advertisement channel communication to the server system over a secure connection.

[0081] In some embodiments, the SS is configured to transmit the communication using a BLE chip, and the identifiable information includes chip identifier data associated with the BLE chip. In some embodiments, a chip identifier of the SS's BLE chip is described in one or more communications transmitted by the SS using an advertisement channel. In some embodiments, the SS also transmits the chip identifier of the BLE chip to the server system over a secure connection.

[0082] In block 203, the DD provides a web request including identifiable information to the server system requesting access to the patient data. In block 204, if the server system authenticates the DD based on the information in the web request, the DD gains access to the patient.

[0083] In some embodiments, the web request includes, in addition to the identifiable information, one or more user authentication token fields maintained by the display device. In some embodiments, the web server allows the DD to access the patient data after the web server verifies that (i) the identifiable information in the web request matches the identifiable information maintained by the web server, and (ii) the one or more user authentication token fields in the web request match one or more user authentication token fields maintained by the server system.

[0084] In addition to the various advantages of the proximity-based authentication techniques described herein, it should be noted that the proximity-based authentication techniques described herein more efficiently utilize computer network resources to transmit identifiable information used for authentication. For example, as described further below, some embodiments include performing authentication based on communications (e.g., sensor output communications) that are transmitted for reasons other than authentication as part of the normal operation of the system. In such examples, transmitting such communications is sufficient to enable the receiving device to perform authentication. Thus, in such embodiments, there is no need to transmit any additional identifiable information using new packets / messages beyond the packets / messages used for communications transmitted as part of the normal operation of the system. Thus, some embodiments reduce the total number of packets / messages transmitted over a network associated with the system.

[0085] 3 is a block diagram depicting an exemplary computing device 300 configured to authorize access to patient data associated with a patient, according to certain embodiments disclosed herein. Although depicted as a single physical device, in embodiments, the computing device 300 may be implemented using virtual devices and / or across several devices, such as a cloud environment. As illustrated, the computing device 300 includes a processor 305, a memory 310, a storage 315, a network interface 325, and one or more input / output (I / O) interfaces 320. In the illustrated embodiment, the processor 305 retrieves and executes programming instructions stored in the memory 310, as well as stores and retrieves data resident in the storage 315. In certain embodiments, the memory 310 is configured to store instructions (e.g., computer executable code) that, when executed by the processor 305, cause the processor 305 to perform operations of the data management system.

[0086] Processor 305 generally represents a single central processing unit (CPU) and / or graphics processing unit (GPU), multiple CPUs and / or GPUs, a single CPU and / or GPU with multiple processing cores, etc. Memory 310 is included generally to represent random access memory (RAM). Storage 315 may be any combination of disk drives, flash-based storage devices, etc., and may include fixed and / or removable storage devices such as fixed disk drives, removable memory cards, cache, optical storage, network attached storage (NAS), or storage area network (SAN).

[0087] In some embodiments, I / O devices 335 (keyboard, monitor, etc.) can be connected via I / O interface 320. Additionally, via network interface 325, computing device 300 can be communicatively coupled to one or more other devices and components. In particular embodiments, computing device 300 is communicatively coupled to other devices via a network, which may include the Internet, a local network, etc. The network may include wired connections, wireless connections, or a combination of wired and wireless connections. As illustrated, processor 305, memory 310, storage 315, network interface 325, and I / O interface 320 are communicatively coupled by one or more interconnects 330. In particular embodiments, computing device 300 is a server running in an on-premise data center or cloud environment.

[0088] Each of these non-limiting examples can stand alone or can be combined in various permutations or combinations with one or more of the other examples. The above detailed description includes reference to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are also referred to herein as "examples." Such examples may include elements in addition to those shown or described. However, the inventors also contemplate examples in which only those elements shown or described are provided. Furthermore, the inventors also contemplate examples that use any combination or permutation of those elements (or one or more aspects thereof) shown or described with respect to a particular example (or one or more aspects thereof) or with respect to other examples (or one or more aspects thereof) shown or described herein.

[0089] In the event of a conflict of usage between this document and any document incorporated by reference, the usage in this document takes precedence.

[0090] In this document, the terms "a" or "an" are used to include one or more, as is common in patent documents, regardless of other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a non-exclusive, such that "A or B" includes "A but not B," "B but not A," "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, i.e., a system, device, article, composition, formulation, or process that includes elements in addition to those listed after such terms in a claim will still be deemed to be within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc., are used merely as labels and are not intended to impose numerical requirements on their objects.

[0091] Geometric terms such as "parallel," "perpendicular," "circular," "square," and the like are not intended to require absolute mathematical precision unless the context indicates otherwise. Instead, such geometric terms allow for variations due to manufacturing or equivalent functions. For example, if an element is described as "circular" or "approximately circular," components that are not exactly round (e.g., those that are slightly elliptical or that are multi-sided polygons) are still encompassed by this description.

[0092] Examples of the methods described herein may be at least partially machine or computer implemented. Some examples may include computer readable or machine readable media encoded with instructions operable to configure an electronic device to perform the methods described in the examples above. Implementations of such methods may include code, such as microcode, assembly language code, high level language code, etc. Such code may include computer readable instructions for performing various methods. This code may form part of a computer program product. Further, in examples, the code may be tangibly stored on one or more volatile, non-transitory, or non-volatile tangible computer readable media, such as during execution or at other times. Examples of these tangible computer readable media may include, but are not limited to, hard disks, removable magnetic disks, removable optical disks (e.g., compact disks and digital video disks), magnetic cassettes, memory cards or sticks, random access memory (RAM), read only memory (ROM), etc.

[0093] The above description is intended to be illustrative, not restrictive. For example, the above examples (or one or more aspects thereof) may be used in combination with each other. Other embodiments may be used, such as those by one of ordinary skill in the art upon reviewing the above description. The Abstract is provided to comply with 37 CFR §1.72(b) to enable the reader to quickly grasp the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or spirit of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. This should not be construed as intending that any unclaimed disclosed feature is essential to any claim. Rather, the subject matter of the invention may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are incorporated into the Detailed Description as examples or embodiments, with each claim standing on its own as a separate embodiment, and it is contemplated that such embodiments can be combined with each other in various combinations or permutations. The scope of the invention should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

[0094] The methods disclosed herein include one or more steps or actions for achieving the method. These method steps and / or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is otherwise specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0095] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. By way of example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).

[0096] The preceding description is provided to enable those skilled in the art to practice the various embodiments described herein. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments. Thus, the claims are not intended to be limited to the embodiments shown herein, but are to be given the full scope consistent with the claim language, in which reference to an element in the singular is not intended to mean "one and only one" unless otherwise stated, but rather "one or more". The term "some" refers to one or more, unless otherwise specifically stated. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are now known or that will become known in the future to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed within the scope of the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. No claim element is to be construed under 35 U.S.C. §112(f) unless the element is expressly recited using the phrase "means for," or, in the case of a method claim, unless the element is recited using the phrase "step for."

[0097] While various examples of the present invention have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various figures may depict exemplary architectural or other configurations for the present disclosure, which configurations are made to aid in understanding the features and functionality that may be included in the present disclosure. The present disclosure is not limited to the illustrated exemplary architecture or configurations, but may be implemented using various alternative architectures and configurations. Furthermore, while the present disclosure has been described above with respect to various exemplary examples and aspects, it should be understood that various features and functions described in one or more of the individual examples are not limited in their applicability to the particular example for which they are described. Instead, those features and functions may be applied, alone or in any combination, to one or more of the other examples of the present disclosure, whether or not such an example is described, and whether or not such features are presented as part of a described example. Thus, the breadth and scope of the present disclosure should not be limited by any of the exemplary examples described above.

[0098] All references cited herein are incorporated herein by reference in their entirety. To the extent that publications and patents or patent applications incorporated by reference conflict with the present disclosure contained herein, the present specification is intended to supersede and / or take precedence over any such conflicting material.

[0099] Unless otherwise defined, all terms (including technical and scientific terms) are to be given their ordinary and customary meanings to those of ordinary skill in the art and are not to be limited to any special or customized meaning unless expressly defined as such herein.

[0100] Terms and phrases used in this application, and variations thereof, unless expressly stated otherwise, particularly in the appended claims, are to be construed as open ended, as opposed to limiting. As an example of the foregoing, the term "including" should be read to mean "including without limitation," "including, but not limited to," and the like. The term "comprising" as used herein is synonymous with "including," "containing," or "characterized by," and is inclusive or open ended and does not exclude additional, unrecited elements or method steps. The term "having" should be interpreted as "having at least." The term "including" should be interpreted as "including, but not limited to." The term "examples" is used to provide illustrative examples of the items in the discussion, not an exhaustive or exclusive listing of such examples. Adjectives such as "known," "usual," "standard," and terms of similar import should not be construed as limiting the items being described to a given period of time or to items available at a given time, but instead should be read to encompass known, conventional, or standard technology that may be available or known at any time now or in the future, and words such as "preferably," "preferred," "desired," or "desirable," and similar imports should not be understood to imply that a particular feature is critical, essential, or even essential to the structure or function of the invention, but instead are merely intended to highlight alternative or additional features that may or may not be utilized in a particular example of the invention. Similarly, a group of items connected with the conjunction "and" should not be read as requiring that any and all of those items be present in the group, but rather should be read as "and / or" unless expressly stated otherwise.Similarly, a group of items connected by the conjunction "or" should not be read as requiring mutual exclusivity among the group, but rather as "and / or" unless expressly stated otherwise.

[0101] As used herein, "comprising" is synonymous with "including," "containing," or "characterized by" and is inclusive or open-ended and does not exclude additional or unrecited elements or method steps.

[0102] All numbers expressing quantities of ingredients, reaction conditions, and so forth used herein should be understood in all instances to be modified by the term "about." Accordingly, unless otherwise indicated, the numerical parameters set forth herein are approximations that may vary depending upon the desired properties sought to be obtained. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of any claims in any application claiming priority to this application, each numerical parameter should be construed in light of the number of significant digits and ordinary rounding approaches.

[0103] Moreover, although the above has been described in some detail by way of illustrations and examples for purposes of clarity and understanding, it will be apparent to those skilled in the art that certain changes and modifications may be practiced. Thus, the description and examples should not be construed as limiting the scope of the invention to the specific examples and embodiments described herein, but rather as covering all modifications and alternatives that come with the true scope and spirit of the invention. [Explanation of symbols]

[0104] 8 Analyte Sensor System 10 Analyte Sensor 11 Processors 12 Analyte Sensor Electronics Module 12 Sensor Electronics Module 13 Sensor measurement circuit 14. Storage 15 Connection Interface 16 Transmitter / Receiver 17 Real-time Clock 100 Disease Management System 110 Display Devices 112 Touch screen display 120 Display Devices 121 Analyte Sensor Applications 122 Touch screen display 123 Storage 125 Display section 126 processors 127 Memory 128 connection interfaces 129 Transmitter / Receiver 130 Display Devices 132 Touch screen display 134 Server 135 Server 136 Storage 140 Display Devices 150 Display Devices 162 Operating Systems 163 Real Time Clock 180 Wireless communication paths 181 Communication Paths 182 Communication Paths 183 Communication Paths 190 Network 200 processes 201 Block Block 202 203 Block 204 Block 300 computing devices 305 Processor 310 Memory 315 Storage 320 I / O Interface 325 Network Interface 330 Interconnection 335 I / O Devices

Claims

1. 1. A method of securely gaining access to patient data associated with a patient using a sensor system for monitoring an analyte level in the patient, comprising: Receiving, at a display device, one or more communications from the sensor system, the one or more communications comprising: including identifiable information associated with the sensor system; and receiving, transmitted by the sensor system via an advertisement channel; inserting the identifiable information into a web request at the display device; providing, at the display device, the web request including the identifiable information to a data management system to request access to the patient data; and obtaining access to the patient data via a web browser when the data management system verifies that the identifiable information matches second identifiable information stored within the patient data.

2. the sensor system is a continuous analyte sensor system; each of the one or more communications configured to describe an analyte value of a host to the display device; The method of claim 1 , wherein the identifiable information comprises a defined number of most recent analyte values ​​reported by the continuous analyte sensor system.

3. the sensor system being a continuous sensor system configured to continuously transmit communications to the display device; the one or more communications include a defined number of most recent communications transmitted by the continuous sensor system; The method of claim 1 , wherein the identifiable information includes received signal strength indicator values ​​for the defined number of most recent communications.

4. The method of claim 1 , wherein the one or more communications are transmitted over a low or short range wireless communications network.

5. the sensor system is configured to communicate over the low-range wireless communications network using a Bluetooth Low Energy (BLE) chip; The method of claim 4 , wherein the identifiable information includes chip identifier data associated with the BLE chip.

6. the low range wireless communications network is associated with a communications protocol; 5. The method of claim 4, wherein the communication protocol is associated with a set of data channels and a set of advertisement channels including the advertisement channel used to carry the one or more communications.

7. the web request includes one or more authentication token fields maintained by the display device; 2. The method of claim 1, wherein access to the patient data through the web browser is obtained when the data management system verifies that the identifiable information matches the second identifiable information stored within the patient data and that the one or more authentication token fields match one or more second authentication token fields maintained by the data management system.

8. 1. A method of authorizing access to patient data associated with a patient using a sensor system for monitoring an analyte level in the patient, comprising: receiving, in a data management system, a web request from a display device, the web request indicating a request for access to the patient data and including identifiable information associated with the sensor system, the identifiable information being provided by one or more communications transmitted from the sensor system to the display device over an advertisement channel; verifying in the data management system that the identifiable information matches second identifiable information stored within the patient data; and in a data management system, granting the request for access to the patient data based on the verifying.

9. the sensor system is a continuous analyte sensor system; each of the one or more communications configured to describe an analyte value of a host to the display device; 9. The method of claim 8, wherein the identifiable information comprises a defined number of most recent analyte values ​​reported by the continuous analyte sensor system.

10. the sensor system being a continuous sensor system configured to continuously transmit communications to the display device; the one or more communications include a defined number of most recent communications transmitted by the continuous sensor system; The method of claim 8 , wherein the identifiable information includes received signal strength indicator values ​​for the defined number of most recent communications.

11. The method of claim 8 , wherein the one or more communications are transmitted over a low or short range wireless communications network.

12. the sensor system is configured to communicate over the low-range wireless communications network using a Bluetooth Low Energy (BLE) chip; The method of claim 11 , wherein the identifiable information includes chip identifier data associated with the BLE chip.

13. the low range wireless communications network is associated with a communications protocol; 12. The method of claim 11, wherein the communication protocol is associated with a set of data channels and a set of advertisement channels including the advertisement channel used to carry the one or more communications.

14. the web request includes one or more authentication token fields maintained by the display device; 9. The method of claim 8, wherein access to the patient data is obtained when the data management system verifies that the identifiable information matches the second identifiable information stored within the patient data and that the one or more authentication token fields match one or more second authentication token fields maintained by the data management system.

15. 1. A system for securely gaining access to patient data associated with a patient using a sensor system for monitoring an analyte level in the patient, the system comprising: a memory including executable instructions; and a processor in data communication with the memory and configured to execute the instructions to cause the system to perform operations of a method, the method comprising: Receiving, at a display device, one or more communications from the sensor system, the one or more communications comprising: including identifiable information associated with the sensor system; and receiving, transmitted by the sensor system via an advertisement channel; inserting the identifiable information into a web request at the display device; providing, at the display device, the web request including the identifiable information to a data management system to request access to the patient data; and obtaining access to the patient data via a web browser when the data management system verifies that the identifiable information matches second identifiable information stored within the patient data.

16. the sensor system is a continuous analyte sensor system; each of the one or more communications configured to describe an analyte value of a host to the display device; 16. The system of claim 15, wherein the identifiable information comprises a defined number of most recent analyte values ​​reported by the continuous analyte sensor system.

17. the sensor system being a continuous sensor system configured to continuously transmit communications to the display device; the one or more communications include a defined number of most recent communications transmitted by the continuous sensor system; The system of claim 15 , wherein the identifiable information includes received signal strength indicator values ​​for the defined number of most recent communications.

18. The system of claim 15 , wherein the one or more communications are transmitted over a low-range wireless communications network.

19. the sensor system is configured to communicate over the low-range wireless communications network using a Bluetooth Low Energy (BLE) chip; 20. The system of claim 18, wherein the identifiable information includes chip identifier data associated with the BLE chip.

20. the low range wireless communications network is associated with a communications protocol; 16. The system of claim 15, wherein the communication protocol is associated with a set of data channels and a set of advertisement channels including the advertisement channel used to transmit the one or more communications.