Systems and methods for continuous glucose monitor communities

Abstract

A device forms a group of users of a continuous glucose monitor (CGM) service, including creating a database association between identifiers, where each identifier is associated with a different user. The device identifies CGM sensor data for the users, including identifying a portion of the CGM sensor data associated with each user. Each portion of the CGM sensor data was generated by a corresponding CGM sensor and received from a corresponding computing device associated with the user. The device generates a CGM data report from the CGM sensor data, and the CGM data report includes glycemic data for at least two of the users. The device sends the CGM data report to a computing device associated with a user. Upon receipt of the CGM data report, the computing device displays a visual representation of the glycemic data for the subset.

Description

SYSTEMS AND METHODS FOR CONTINUOUS GLUCOSE MONITOR COMMUNITIESBACKGROUND

[0001] The detection and / or monitoring of analyte levels, such as glucose, ketones, lactate, oxygen, hemoglobin A1C, or the like, can be vitally important to the overall health of an individual, particularly for an individual having a chronic health condition, such as diabetes mellitus. Patients suffering from diabetes can experience complications including loss of consciousness, cardiovascular disease, retinopathy, neuropathy, and nephropathy. Individuals with diabetes are generally required to monitor their glucose levels to ensure that they are being maintained within a clinically safe range, and may also use this information to determine if and / or when insulin is needed to reduce glucose levels in their bodies, or when additional glucose is needed to raise the level of glucose in their bodies.

[0002] Growing clinical data demonstrates a strong correlation between the frequency of glucose monitoring and glycemic control. Despite such correlation, however, many individuals diagnosed with a diabetic condition do not monitor their glucose levels as frequently as they should due to a combination of factors including convenience, testing discretion, pain associated with glucose testing, and cost.

[0003] To increase patient adherence to a plan of frequent glucose monitoring, in vivo analyte monitoring systems can be utilized, in which a sensor control device may be worn on the body of an individual who requires analyte monitoring. Such sensor control devices can be referred to as on-body units or on-body sensors, and are often part of continuous analyte monitor (CAM) systems. For example, contemporary continuous glucose monitor (CGM) systems generally employ an in vivo glucose sensor, a smartphone app or proprietary reader that reads glucose levels from the glucose sensor and displays those glucose levels, and a report generation system (e.g., a cloud service). To increase comfort and convenience for the individual, CAM sensors may be assembled and / or applied by the individual with a sensor applicator. The application process includes inserting a sensor, such as an analyte sensor that senses a user's analyte level in a bodily fluid, using an applicator or insertion mechanism, such that the sensor comes into contact with a bodily fluid. The sensor control device may also be configured to transmit analyte data to another device, from which the individual or the individual's health care provider can review the data and make therapy decisions.

[0004] The subject matter claimed herein is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described supra. Instead, thisbackground is only provided to illustrate one example technology area where some embodiments described herein may be practiced.SUMMARY

[0005] In some aspects, the techniques described herein relate to a method, implemented at a computer system operating a continuous glucose monitor (CGM) service, the method including: forming a group of a plurality of users of the CGM service by creating a database association between a plurality of identifiers, each identifier associated with a different user; identifying CGM sensor data for the plurality of users, wherein the CGM sensor data is: generated by a corresponding CGM sensor associated with each user, and received from a corresponding computing device associated with each user; generating a CGM data report from the CGM sensor data, the CGM data report including glycemic data for at least a subset of the plurality of users; and sending the CGM data report to a first computing device associated with one of the plurality of users, wherein the first computing device is configured to display a visual representation of the glycemic data for the subset.

[0006] In some aspects, the techniques described herein relate to a computer system, including: a processor system; and a computer storage medium that stores computer-executable instructions that are executable by the processor system to at least: form a group of CGM service users by creating a database association between identifiers, each identifier associated with a different user; identify CGM sensor data for the users, including identifying a portion of the CGM sensor data that is associated with each user, wherein the CGM sensor data is: generated by a CGM sensor associated with each user, and received from a corresponding computing device associated with each user; generate a CGM data report from the CGM sensor data, the CGM data report including glycemic data for two or more of the users; and send the CGM data report to a first computing device associated with a first user, wherein the first computing device is configured to display a visual representation of the glycemic data for the two or more users.

[0007] In some aspects, the techniques described herein relate to a method, implemented at a computer system operating a CGM service, the method including: receiving, from a first computing device associated with a first user of the CGM service, a specification of one or more additional users to add to a group; determining a plurality of identifiers, including an identifier for the first user and a corresponding identifier for each additional user; forming the group, including creating a database association between the plurality of identifiers; receiving CGM sensor data, including receiving a first portion of the CGM sensor data that is associated with the first user, and receiving a corresponding portion of the CGM sensor data that isassociated with each additional user; and based on the CGM sensor data, sending a CGM data report to the first computing device associated with the first user, wherein, upon receipt of the CGM data report, each computing device is configured to display a visual representation of the CGM data report.

[0008] In some aspects, the techniques described herein relate to a computer system, including: a processor system; and a computer storage medium that stores computer-executable instructions that are executable by the processor system to at least: receive, from a first computing device associated with a first user of a CGM service, a specification of one or more additional users to add to a group of users; determine a plurality of identifiers, including an identifier for the first user and a corresponding identifier for each of the additional users; form the group of users, including creating a database association between the plurality of identifiers; receive CGM sensor data, including receiving a first portion of the CGM sensor data that is associated with the first user, and receiving a corresponding portion of the CGM sensor data that is associated with one or more additional users; and based on the CGM sensor data, send a CGM data report to the first computing device associated with the first user, and to a corresponding computing device associated with each of the one or more additional users, wherein, upon receipt of the CGM data report, each corresponding computing device is configured to display a visual representation of the CGM data report.

[0009] This Summary introduces a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] To describe how the advantages of the systems and methods described herein can be obtained, a more particular description of the embodiments briefly described supra is rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. These drawings depict only typical embodiments of the systems and methods described herein and are not, therefore, to be considered to be limiting in their scope. Systems and methods are described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0011] Figure 1 illustrates an example of the use of a continuous glucose monitor (CGM) system by a patient or comrade.

[0012] Figure 2 illustrates an example of a network architecture of a CGM system.

[0013] Figure 3 illustrates an example of a glucose chart.

[0014] Figure 4 illustrates an example of a network architecture in which a CGM service facilitates the organization of various CGM users into communities.

[0015] Figure 5 illustrates an example of a CGM service that facilitates the organization of various CGM users into communities.

[0016] Figures 6A and 6B illustrate examples of mobile user interfaces for initiating the formation of a CGM community.

[0017] Figure 7 illustrates an example of a shared glucose graph for a community.

[0018] Figure 8 illustrates a flow chart of an example of a method for the community sharing CGM data.

[0019] Figure 9 illustrates a flow chart of an example of a method for initiating the formation of a community for sharing CGM data.DETAILED DESCRIPTION

[0020] Even with the convenience of in vivo continuous analyte monitor (CAM) systems, such as continuous glucose monitor (CGM) systems, many individuals (referred to herein as a "patient") who are diagnosed with a chronic condition such as diabetes continue to struggle to consistently maintain their analyte levels (e.g., glucose) within a clinically safe range. Often, a contributing factor is a lack of understanding and support from other individuals— such as family, friends, coworkers, etc.— in the patient's social circle. For example, social situations often involve the consumption of food and beverages, and patients in these situations often make poor nutritional choices. The reasons for these poor nutritional choices are varied but can include an attempt to avoid feeling or looking like an outsider or bending to social pressures. For example, with a lack of knowledge of how various nutritional choices affect glucose levels, individuals in a patient's social circle may unintentionally pressure the patient to make poor nutritional choices in social situations. Even apart from social situations, individuals in a patient's social circle can directly affect the patient's nutritional choices and options. For example, a patient's spouse / partner or caregiver may have an outsized influence on the patient's everyday nutritional options and choices.

[0021] Additionally, given the exposure they have to CGMs through a patient, nondiabetic individuals (e.g., individuals not diagnosed with diabetes or as pre-diabetic) in the patient's social circle are often curious about CGMs and may be interested in trying a CGM themselves. Motivations for non-diabetic individuals to try a CGM vary, but include an interest in monitoring and improving their own health, a desire to better understand the challenges thepatient faces, a desire to better understand how various foods and beverages affect glucose levels, a desire to better understand how various physical activities affect glucose levels, a desire to better understand how their glucose levels affect various physical activities or their mood, etc.

[0022] At least some embodiments described herein are directed to systems and methods for facilitating the experience of wearing a CAM, such as a CGM, and sharing analyte data (e.g., glucose data) amongst a network of connected users. In this description, and in the claims, a non-diagnosed (e.g., non-diabetic) individual in a network of connected users may be referred to as a "comrade." In this description, and in the claims, a group of connected users may be referred to as a "community" or a group. A given community may be made up of only patients, of only comrades, or of a mix of one or more patients and one or more comrades.

[0023] For concreteness, the examples herein focus on CGMs and forming communities around glucose / diabetes management. However, it will be appreciated that the embodiments described herein can be applied to a variety of sensors (e.g., alcohol, blood oxygen, heart rate, blood pressure) and analytes (ketone, lactate, alcohol, etc.) to form communities around a variety of conditions or health concerns.

[0024] In some embodiments, the systems and methods described herein provide features to enhance the knowledge and health of comrades, and to promote empathy and support for patients. Doing so can improve health outcomes for patients and comrades alike. For patients, the systems and methods described herein help comrades encourage the patient to make better choices (e.g., nutritional and physical activity), which help the patient consistently maintain their glucose levels within a clinically safe range. For comrades, the systems and methods described herein help the individual gain the knowledge to make better choices (e.g., nutritional and physical activity) that will help them feel better and avoid developing diabetes at a later time. Further, for comrades, the systems and methods described herein help an individual with a pre-diabetic condition become aware of that condition at an early phase and take affirmative steps to ensure that it does not develop into a diabetic condition.

[0025] Figure 1 illustrates an example 100 of the use of a CAM system (e.g., CGM system, continuous ketone monitor system, continuous lactate monitor system) by an individual, such as a patient or comrade. In example 100, a CGM unit 102 (e.g., a glucose sensor and sensor control unit) is affixed to the arm of an individual 101 (e.g., patient or comrade). The CGM unit 102 actively measures the individual's glucose levels in vivo via a glucose sensor in contact with bodily fluid, such as interstitial fluid in the individual's skin. In some embodiments, CGM unit 102 measures the individual's glucose regular intervals, such as every minute, every five minutes,every ten minutes, etc. The CGM unit 102 communicates (e.g., continuously, periodically) these measured glucose levels to a personal device 103 that operates as a CGM reader.

[0026] Personal device 103 can be any type of device used by individual 101, including any type of wearable device or mobile device. Examples of personal device 103 include, but certainly are not limited to, any type of special-purpose CGM reader device, smartwatch, smartphone, tablet, laptop, desktop, and so on. In embodiments, personal device 103 executes a CGM application that configures personal device 103 to communicate with CGM unit 102, and with a remote CGM service. In some embodiments, the CGM application is a native application installed locally on the personal device 103. In other embodiments, the CGM application is a web application provided by the remote CGM service, and that executes in a web browser on the personal device 103. Combinations of native and web applications are also possible, such as a native application that operates as a web wrapper. Although not required, in example 100, personal device 103 provides a visualization of the tracked data (e.g., a graph or trace of glucose levels over a period of time).

[0027] Figure 2 illustrates an example of a network architecture 200 of a CGM system. In network architecture 200, a CGM unit 201 (e.g., the CGM unit 102 of example 100) wirelessly communicates sensor data 202 indicative of an individual's glucose levels to a personal device 203 (e.g., the personal device 103 of example 100). CGM unit 201 communicates with personal device 203 using any type of short-range wireless communication technology, such as BLUETOOTH, near-field communication (NFC), radio-frequency identification (RFID), and the like. As a result, sensor data 202 is transmitted from CGM unit 201 to personal device 203 over that communication protocol. In some implementations, the sensor data 202 is encrypted or otherwise integrity-protected by CGM unit 201 to ensure tampering does not occur.

[0028] In embodiments, personal device 203 includes an application 207 (e.g., a locally installed CGM application, a CGM web application, device firmware) that configures personal device 203 to communicate with CGM unit 201 and with CGM service 205. In embodiments, application 207 aggregates and communicates sensor data via network 204 to a CGM service 205. In some implementations, application 207 encrypts or otherwise integrity-protects this aggregate sensor data to ensure tampering does not occur. Network 204 represents any combination of networks that can transport data from personal device 203 to CGM service 205, including, for example, any combination of one or more personal area networks (PANs), one or more local area networks (LANs), and one or more wide-area networks (WANs) such as the Internet. CGM service 205 comprises one or more automated programs that are tasked with performing different actions based on input.

[0029] In some implementations, CGM service 205 is a cloud service operating in a cloud computing environment. In some implementations, CGM service 205 is a local service operating on a local device (e.g., personal device 203). In some implementations, CGM service 205 is a hybrid service that includes a cloud component and a local component operating on a local device. In some cases, CGM service 205 can be a deterministic service that operates fully given a set of inputs without a randomization factor. In other cases, CGM service 205 can include an artificial intelligence (Al) or machine learning (ML) engine, enabling CGM service 205 to operate even when faced with various randomization factors. As used herein, reference to any type of ML or Al may include any type of ML algorithm or device, convolutional neural network(s), multilayer neural network(s), recursive neural network(s), deep neural network(s), decision tree model(s) (e.g., decision trees, random forests, and gradient boosted trees) linear regression model(s), logistic regression model(s), support vector machine(s) ("SVM"), Al device(s), or any other type of intelligent computing system. Any volume of training data may be used (and perhaps later refined) to train the ML algorithm to dynamically perform the disclosed operations.

[0030] In embodiments, CGM service 205 is tasked with various operations that include collecting sensor data for a variety of users, analyzing that sensor data, and determining the impact of that sensor data with respect to each user associated with the sensor data. To do so, CGM service 205 can include an analytics component capable of performing data analysis on the collected sensor data (e.g., using deterministic and / or AI / ML techniques). The CGM service 205 generates output data 208 as a result of performing that analysis. For example, such output data can reflect glycemic insights, such as a glycemic impact for the user. Glycemic impact generally refers to a patient's bodily state with respect to blood sugar levels. In embodiments, this output data can be displayed at personal device 203 (e.g., a user's smartphone via an installed application), and / or at some other device, such as device 206 (e.g., a user's laptop via a web application displayed in a web browser).

[0031] Figure 3 illustrates an example 300 of a glucose chart, which can be displayed by personal device 203 and / or device 206 of Figure 2. The glucose chart in example 300 displays the sensor data (e.g., sensor data 202 of Fig.2), which is reflective of the user's glucose levels over a period of time. For instance, the horizontal axis reflects the glucose levels over a minutes-based time period. In example 300, the glucose chart indicates a recommended healthy range (e.g., between dashed lines) for glucose values to fall within.

[0032] As mentioned, the embodiments described herein facilitate the experience of patients and comrades wearing CGMs, and sharing glucose data amongst communities. Figure 4 illustrates an example of a network architecture 400 in which CGM service 205 facilitates theorganization of various CGM users into communities (described further with reference to Figure 5). In particular, network architecture 400 shows that CGM service 205 has created two communities, community 401a and community 401n, each comprising a plurality of users. An ellipsis between community 401a and community 401n indicates that CGM service 205 can create any number of communities. In the example, community 401a includes user 402a, user 402b, and user 402n, though an ellipsis within community 401a indicates that community 401a could include any number (e.g., two or more) of users. Similarly, community 401n includes user 403a, user 403b, and user 403n, though an ellipsis within community 401n indicates that community 401n could include any number (e.g., two or more) of users. In the context of Figure 4, CGM service 205 facilitates the sharing of CGM data among users in community 401a. Additionally, CGM service 205 facilitates the sharing of CGM data among users in community 401n. In some examples, CGM service 205 facilitates the sharing of CGM data and / or point data between communities (e.g., between community 401a and 401n). In this way, two or more communities may share group member CGM data and / or enter competitions based on earned points by group / community members. In some examples, the CGM data shared between groups / communities may be deidentified. In some examples, the data shared between groups / communities may contain user point data without CGM data.

[0033] In some examples, each community can comprise any mix of patients and comrades. For example, an asterisk associated with user 402a indicates that user 402a is a patient. Thus, community 401a includes a patient (i.e., user 402a) and comrades (i.e., user 402b and user 402n). Community 401n, on the other hand, includes only comrades. Variations could include communities of only patients, communities that have more than one patient and along with comrades, etc. In some embodiments, a single user may be part of more than one community.

[0034] Figure 5 illustrates an example 500 of the CGM service 205 of Figure 3 and Figure 4. In particular, example 500 shows various components that CGM service 205 may include to facilitate the organization of various CGM users into communities, including sharing CGM data among and between those communities. Each component of CGM service 205 depicted in Figure 5 represents various functionality that CGM service 205 may implement under the embodiments described herein. These components— including their identity and arrangement— are presented merely as an aid in describing example embodiments of CGM service 205.

[0035] As mentioned, in some implementations, CGM service 205 is a hybrid service that includes a cloud component and a local component operating on a local client device, such as personal device 203. Thus, in various implementations, one or more components illustrated inexample 500 may execute, wholly or partially, on a personal device (e.g., as part of a native CGM application locally installed on the personal device; as part of a CGM web application provided by CGM service 205 and that executes in a web browser on the personal device; or combinations thereof).

[0036] CGM service 205 is shown as including a user registration component 501, which creates database records for new users of CGM service 205. In embodiments, a user interacts with user registration component 501 to register with CGM service 205 via an application (e.g., application 207) on a personal device (e.g., personal device 203), or via a web page on some other computing device (e.g., device 206). In example 500, CGM service 205 includes, or is associated with, a database 507 that stores user records. In example 500, database 507 includes user record 508a to user record 508n, with an ellipsis indicating that database 507 can include any number of user records.

[0037] User record 508a details example data fields that could be maintained for each user. As shown, examples include a user name 509, a user identifier 510, a sensor identifier 511, permissions 512, community information 513, and glucose data 514 (e.g., sensor readings, such as sensor data 202). An ellipsis indicates that a user record can include any number of data fields. In some embodiments, user name 509 stores a "human-friendly" name to which the user is referred, with examples being the user's legal name, a user-selected nickname, an email address, and the like. In some examples, user identifier 510 stores a unique identifier for a user within CGM service 205, such as a globally unique identifier (GUID) such as a randomly generated text string (e.g., 64-bit, 128-bit, 256-bit). In some examples, user identifier 510 is a username, email, or phone number associated with the user. In some embodiments, sensor identifier 511 stores one or more unique identifiers, such as serial numbers, of one or more sensors (e.g., CGM unit 201) to which the user is associated. In embodiments, permissions 512 stores one or more user- configurable permissions, such as permissions for the sharing of glucose data within a community. In some embodiments, community information 513 stores information about a community to which the user belongs, such as a community identifier, sensor identifiers for sensors in the community, user identifiers for users in the community, and the like. In embodiments, glucose data 514 stores raw and / or aggregated glucose readings for the user. In one example, upon creation of a user, user registration component 501 configures one or more of user name 509, user identifier 510, sensor identifier 511, and permissions 512.

[0038] CGM service 205 is also shown as including a community formation component 502, which manages the formation of a community comprising patients and / or comrades. The particular manner of forming a community can vary, but common elements include creating auser record for each community member, associating a CGM sensor with each user record, and forming a community based on associating various user records. In one example, user records are associated with each other based on storing, within community information 513 of one or more user records, an identifier for a community in each participating user record. In another example, user records are associated with each other based on storing, within community information 513 of one or more user records, the user identifiers and / or the sensor identifiers associated with other members of the user's community. In another example, user records are associated with each other based on storing a list of user identifiers that are part of the community (e.g., as part of a separate community record in database 507, not shown). Combinations of the foregoing are also possible.

[0039] In some embodiments, the formation of a community is initiated by a patient, e.g., based on interaction with application 207 at personal device 203. In one example, an existing CGM user receives a notification (e.g., in-app or system-wide) for forming a CGM community. For example, Figure 6A shows an example 600a of a mobile user interface, in which a user receives an in-app notification 601 while browsing their glucose data, and which enables the user to initiate a community formation or join an existing community (e.g., a "Learn More" button, a "Find People Like Me" button). In alternatives, application 207 could surface the availability of CGM communities in other manners, such as via a news feed, a settings menu, an in-app storefront, and the like. Embodiments could surface the availability of CGM communities in manners separate from application 207, such as via an email, via a website associated with CGM service 205, and the like.

[0040] In some embodiments, and as shown in example 600b of Figure 6B, a community initiation page 602 may enable the user to directly invite other users, such as by specifying the email addresses or phone numbers of the invitees. In these embodiments, the invitees may receive an email or text message inviting them to register at CGM service 205 and install an application on their personal devices. In some embodiments, patients and comrades use applications having the same functionality, while in other embodiments there are different applications for patients and comrades, with differing functionality. In some embodiments, community initiation page 602 enables the user to acquire CGM sensors for the individuals they invite (e.g., to purchase or order over-the-counter CGM sensors), with those sensors being automatically linked to the invitees, and / or to the community, when they register. In additional or alternative embodiments, the user obtains a link they can send (e.g., via email or text), to one or more individuals they would like to invite. In some embodiments, this link includes a unique identifier code (e.g., the user's unique identifier, a unique community identifier) that can be usedby community formation component 502 to connect users who register via the link as being part of a community.

[0041] It will be appreciated, in view of the disclosure herein, that there are a variety of mechanisms beyond those just described for connecting users, facilitating the acquisition and linkage of sensors, and facilitating the installation of appropriate applications on personal devices. Any applicable mechanism falls within the scope of this disclosure. However, the embodiments just described, which can be initiated by one user who invites others, provide a streamlined, simplified process for end-users where connections can be made automatically.

[0042] Turning back to Figure 5, CGM service 205 is also shown as including a data acquisition component 503, a data analysis component 504, a data presentation component 505, and a data privacy component 506. In embodiments, data acquisition component 503 acquires glucose data from a variety of personal devices and stores that glucose data in database 507, associating it with an appropriate user record (e.g., glucose data 514) based on identifying data (e.g., user identifier, sensor identifier) associated with that data.

[0043] In embodiments, the data analysis component 504 performs any form of analysis on acquired glucose data, such as aggregating glucose data, filtering noise from glucose data, determining if glucose data is in range, etc. The data analysis component 504 can also perform analysis on a variety of other types of data received, such as video, audio, pictures, etc.

[0044] In embodiments, data presentation component 505 generates reports for presenting glucose data on personal devices (e.g., personal device 203) and / or other devices (e.g., device 206). In one embodiment, data presentation component 505 provides a list of users in the community, and a user interface control permits a user to select one of the users on the list to display that user's glucose plot. In another embodiment, the plot may display the glucose traces for all, or a subset, of users overlayed on the same plot. Each user's trace may be identified by different trace attributes, such as color, line texture, or line markers. Another embodiment is to show the traces on separate adjacent plots, or toggle among the traces by clicking, swiping, etc.

[0045] For example, Figure 7 illustrates an example 700 of a shared glucose graph for a community, such as community 401a of Figure 4. In example 700, the shared glucose graph includes a glucose plot for three users, user 701 (e.g., user 402a), user 702 (e.g., user 402b), and user 703 (e.g., user 402n). In embodiments, the time scale range may be automatically scaled or manually set. One embodiment has the time scale fixed by default at 24 hours, with the time starting in the morning (e.g., 4:00, 5:00., or 6:00 a.m.) so the users can see how their glucose changes throughout the day. In embodiments, a shared glucose graph provides a variety ofinteractive features such as zooming (e.g., changing the granularity of one or more of the axes), panning (e.g., changing the time period being viewed), emphasizing or emphasizing one more user's glucose plot (e.g., by changing line style, line weight, line color, etc.), selectively changing which user's plots are visible, and the like. In some embodiments, the shared glucose graph includes a toggle control to show a recent time window (e.g., the most recent eight hours). In some examples, each user can modify their own time scale such that each user can see different time scales (e.g., user 402a may use a 12 hour time scale and user 402b may use 24 hour time scale).

[0046] Some embodiments are based on the recognition that many patients with diabetes may not want their comrades to be able to view their glucose readings, but would value having their comrades experience monitoring their glucose and understanding how eating and activity can affect their glucose, and thereby better empathize with the patient. In these embodiments, data presentation component 505 does not share the patient's data with the other users in the community but only the other comrade's data. In some examples, the patient may see the other comrade's data (data shared with him or her), but the comrades may not see the user's data.

[0047] In embodiments, data privacy component 506 enables a user to manage the privacy of their data (e.g., by managing permissions 512). Examples of privacy management functionality include privacy settings such as data retention settings and data sharing settings. As examples, privacy settings or data sharing settings may include the granularity of data shared, the time periods over which data is shared or not shared, users and communities to whom data can be shared, what information can be shared (e.g., name, username, email, glucose data, sensor type, and / or other data capable of being collected by CGM service 205), and the like. Thus, in embodiments, CGM service 205 is configurable by each user as to the level of sharing they are willing to make. A sharing user interface could include, as examples, a menu of check-boxes and data description for each check-box, or a screen-by-screen check-box and text that describes the data that could be shared. These data-sharing elements may consist of glucose traces, various glucose metrics (such as daily glucose time-in-range, number of low glucose alarms, number of high glucose alarms, number of urgent low alarms, number of sensor scans), notifications such as those described hereinafter, or other data that may be available to the system (such as new sensor starts or purchases, location information, etc.).

[0048] One example of a metric that may be shared is an indication of a bad glycemic day for a comrade. For instance, CGM service 205 may be configured to notify one or more comrades if one of the comrades has a day where their glucose time-in-range (or other glucosemetric) for the day exceeds a threshold. This threshold may be constant (and configurable) or may be determined by data analysis component 504, for instance, as the 90thpercentile of past daily time-in-range metrics for the past week, or some other calculation based on prior days. In embodiments, thresholds may have default values, but may also be configurable (e.g., per comrade, and by the comrade). In some embodiments, the threshold is the same for each member of a group / community. In some embodiments, the threshold is set / edited by a user for the entire group / community. Some embodiments enable each community member to configure their own glucose range. In embodiments, non-diabetes comrades would use a much narrower range (e.g., 65-120 mg / dL) than diabetes patients (e.g., 70-180 mg / dL). In embodiments, the range is displayed on a glucose plot (e.g., example 700) and can be used in time-in-range calculations. In some examples, threshold values may be shared / the same between all users in a group / community. In some examples, threshold values may be the same for all users in a particular category. For example, all users with diabetes may have the same threshold values, all pre-diabetic users may have the same thresholds, all users with gestational diabetes may have the same thresholds, and all comrades may have the same thresholds.

[0049] In some embodiments, based on analysis of an individual's glucose data, CGM service 205 initiates notifications to members of that individual's community. In one example, with appropriately permissive privacy / sharing settings in place, a meal detection algorithm (e.g., data analysis component 504) could detect that a patient is eating a meal (e.g., based on rising glucose levels, or based on photos or videos uploaded by the individual). This detection could initiate a notification to each of the patient's comrades to indicate that the patient is eating. If the patient's personal device is connected to an insulin delivery device, the data analysis component 504 may also detect if the patient has not injected meal-time insulin and send a corresponding notification to the community. In this example, the community receives information that can help them act to favorably support the patient in keeping their glucose levels in check.

[0050] In another example, with appropriately permissive privacy / sharing settings in place, data analysis component 504 could detect when the patient has a peak glucose level, which triggers the detection of the peak glucose for all of the comrades near the time that the patient has a peak glucose value (e.g., one-half hour before, and two hours after the patient's peak), and send this information to the community. In this example, the community members are encouraged to support each other to control their peak glucose levels.

[0051] In some embodiments, data analysis component 504 may be configured to detect diabetes or pre-diabetes for non-diagnosed comrades. In this embodiment, data analysiscomponent 504 processes each user's glucose data to detect potential pre-diabetes or diabetes and notify that user. In embodiments, the identification and displaying of key diabetes metrics, such as average glucose above a threshold, fasting glucose above a threshold (with fasting glucose determined, e.g., by detecting the minimum glucose level or the fifth-percentile glucose level), variability above a threshold (e.g., coefficient of variation or standard deviation), or a measure of excursion after meals above a threshold). In embodiments, is highlighted for the afflicted comrade by sending them a notification, or an in-app display that explicitly highlights the condition and possibly indicates that the patient should seek confirmation from a medical professional.

[0052] In some embodiments, rather than being based on a social circle, a community may be made up of individuals who share a common diabetes activity, like starting a new medication such as insulin or glucagon-like peptide-1 (GLP-1). In these embodiments, a community can function as a "journey group" that facilitates camaraderie and support among individuals going through a common experience, by enabling the exchange of messages to provide support and education specific to the new regimen. In embodiments, "journey group" communities may be comprised of diabetes patients, their caregivers, a facilitator, and the like. In some examples, journey groups may be formed from and / or associated social media groups. In this scenario, some members of the group may not even be using a sensor, such as the caregivers or facilitators.

[0053] Some embodiments use communities to facilitate the care of a diabetic child (e.g., a child with type-1 diabetes). In these embodiments, a caregiver or parent configures a community for the patient, and perhaps other comrades. In embodiments, there are different versions of application 207 for the caregiver / parent and the child. In embodiments, a caregiver / parent version of application 207 may provide rich data about a child's current and past analyte levels, while a child version of application 207 may provide a simpler indication of the child's current and past analyte levels. For example, a caregiver / parent version of application 207 may utilize charts, data points, etc. to convey analyte levels, while a child version of application 207 may utilize colors (e.g., green for good levels, red for good levels), cartoon characters (e.g., heroes and villains), emotions (e.g., emoticons such as a smiley face for good levels, a frowny face for bad levels), and the like. In embodiments, the child version of application 207 provides kidfriendly interaction mechanisms to encourage engagement with application 207, such as shaking personal device 203 to reset, single tap to home-screen, gesture controls, earning badges for analyte time-in-range, friendly competition with other kids for achieving metrics, rewarding streaks with award or points system, virtual coaching, and the like.

[0054] Some embodiments include a variety of mechanisms to increase community engagement. Some embodiments implement an award or points system that rewards a user for their engagement in the system (e.g., for data logging streaks, for sensor scanning frequency, for app usage frequency and / or duration), for maintaining healthy glucose levels (e.g., based on time-in-range metrics), for recruiting additional members to a community, for creating a community, and the like. For example, a user may receive point(s) for each hour he or she stays in range. In various examples, rewards may include prestige such as digital rankings within a community; in-app badges that visually reward a user for achievements and that give a user achievements to work towards; a digital currency that can be applied, e.g., towards the purchase of sensor units or subscriptions, towards gift cards, etc., and the like. For instance, some examples present the top users (e.g., the top ten users, based on their digital rankings) in a community / group or general population. In some examples, users in a community or group may share CGM data and / or points data with other users in that community or group. In some examples, CGM data and / or points data between groups or communities. In this way, communities / groups may have point competitions (e.g., what team accumulates the most points for a particular duration of time. In some examples, an operator of CGM service 205 partners with other companies or organizations to provide awards and / or prizes based on earned points.

[0055] Some embodiments support engagement through the use of real-world evidence. For example, embodiments may show how an individual's time-in-range result, average glucose, etc. compares to other members of the community or the general population, such as compared to other people in the individual's city, state, or country. One example enables a user to select a location on a map and see how their metrics (e.g., time-in-range, average glucose) compare to people in any country or region of the user's choice. Some embodiments compare a user's metrics directly to similar users (e.g., based on having similar medical conditions, similar treatment plans, similar glycemic reaction profiles, etc.).

[0056] Some embodiments provide a digital coaching experience in which a virtual coach provides customized or individualized recommendations to a user (e.g., based on that user's sensor data, based on data from an activity tracker, based on data from a diet tracking app). For example, a virtual coach may encourage a user to make healthier diet choices based on past glucose readings and diet tracking app data, may encourage a user to engage in additional or different forms of physical activity based on past glucose readings and activity tracker data, etc. In embodiments, digital coaching experiences tie in with award / points systems, where a user is rewarded for engagement with a digital coach and / or is rewarded for making behavioral changes based on digital coaching recommendations. For example, the digital coachingexperience may grant a user points in response to the user following a recommendation to go for a 10-minute walk following a meal. In embodiments, digital coaching includes generating a workday report with positive reinforcement to celebrate successes and motivate.

[0057] The following discussion now refers to a number of methods and method acts. Although the method acts are discussed in specific orders or are illustrated in a flow chart as occurring in a particular order, no order is required unless expressly stated or required because an act is dependent on another act being completed prior to the act being performed.

[0058] Figure 8 illustrates a flow chart of example method 800, such as a method implemented by CGM service 205, for the community sharing of CGM data.

[0059] Referring to Figure 8, in embodiments, method 800 comprises act 801 of forming a community of CGM users. In some embodiments, act 801 comprises forming a group of a plurality of users of the CGM service by creating a database association between a plurality of identifiers, each identifier associated with a different user. For example, community formation component 502 forms an association between user 402a, user 402b, and user 402n in database 507 in order to create community 401a. In embodiments, each identifier is a CGM sensor identifier (e.g., sensor identifier 511) or a user identifier (e.g., user identifier 510).

[0060] In some embodiments, creating the database association between the plurality of identifiers comprises creating a group data record, which is associated with each of the plurality of identifiers. In other embodiments, creating the database association between the plurality of identifiers comprises, for each user of the plurality of users, storing at least a subset of the plurality of identifiers in a user record for the user, the subset including an identifier associated with each other user in the plurality of users. For example, for user record 508a, community information 513 stores identifiers associated with other community users. In other embodiments, creating the database association between the plurality of identifiers comprises, for each user of the plurality of users, storing a group identifier in a user record for the user (e.g., storing a group identifier in community information 513 for each user).

[0061] Method 800 also comprises act 802 of identifying CGM data from the community. In some embodiments, act 802 comprises identifying CGM sensor data for the plurality of users. In embodiments, the CGM sensor data is generated by a corresponding CGM sensor associated with each user and received from a corresponding computing device associated with each user. For example, data acquisition component 503 receives CGM sensor data from devices corresponding to each of user 402a, user 402b, and user 402n, with that data having been generated by CGM sensors paired to those devices. In some embodiments, the portion of the CGM sensor data associated with each user is associated with a correspondingsensor identifier. In other embodiments, the portion of the CGM sensor data associated with each user is associated with a corresponding user identifier.

[0062] Method 800 also comprises act 803 of generating a CGM data report from the CGM data. In some embodiments, act 803 comprises generating a CGM data report from the CGM sensor data, the CGM data report including glycemic data for at least a subset of the plurality of users. In some embodiments, the subset includes two or more of the plurality of users. For example, data presentation component 505 generates a report for display at devices corresponding to user 402a, user 402b, and user 402n. The nature of these reports can vary, but examples include a plot of historic glycose levels for each user and a historic time-in-range for each user.

[0063] Method 800 also comprises act 804 of sending the CGM data report to user device(s). In some embodiments, act 804 comprises sending the CGM data report to the computing device associated with one of the plurality of users, wherein the computing device is configured to display a visual representation of the glycemic data for the subset. For example, data presentation component 505 sends the report to devices corresponding to user 402a, user 402b, and user 402n, which then display the reports (e.g., based on application 207).

[0064] In some embodiments, method 800 also comprises analyzing the CGM sensor data and generating a glycemic insight for one or more users. For example, glycemic insights could include the identification of a potential pre-diabetic condition for a user, that a time-in- range exceeds a threshold for a user, that a user is eating a meal, that a user has missed insulin, that a peak glucose level has been reached for a user, and the like. In embodiments, method 800 also comprises sending a notification to one or more users based on the glycemic insight (e.g., to notify the user or the group of the insight).

[0065] In some embodiments, method 800 also comprises receiving, from one or more users of the plurality of users, a selection of a privacy setting or a sharing setting. In these embodiments, the method includes excluding corresponding glycemic data for one or more from the CGM data report based on the setting.

[0066] In some embodiments, method 800 includes mechanisms to increase user engagement, such as tracking a point count for each user based on their participation in a CGM community. For example, a user may earn points for sharing CGM sensor data, for maintaining healthy glucose levels, for inviting additional group members, for creating a group, for encouraging other community members, and the like. In embodiments, these points may affect a user's ranking or standing within a group or may be redeemed for some reward (e.g., reduction in health insurance premiums, products, services, gift cards).

[0067] Figure 9 illustrates a flow chart of an example method 900 for initiating the formation of a community for sharing CGM data. Referring to Figure 9, in embodiments, method 900 comprises act 901 of receiving, from a first user, a specification of users to add to a community. In some embodiments, act 901 comprises receiving, from a first computing device associated with a first user of the CGM service, a specification of one or more additional users to add to a group. For example, using a personal device, user 402a sends, to CGM service 205 contact information (e.g., email address) for user 402b and user 402n. In some embodiments, the first user (e.g., user 402a) is an individual diagnosed with a diabetic condition, and at least one of the one or more additional users (e.g., user 402b, user 402n) is a non-diabetic individual (e.g., family members, coworkers, friends).

[0068] In some embodiments, CGM service 205 sends, to each user specified by the first user, a notification inviting them to register for the CGM service and join a community (e.g., a "family group" for user 402a). In some embodiments, based on the first user specifying the additional user(s), CGM service 205 initiates a purchase (e.g., by the first user) of CGM sensors for each invited user. In some embodiments, based on the first user specifying the additional user(s), CGM service 205 creates a corresponding user record (e.g., in database 507) for each invited user. In some embodiments, based on the first user specifying the additional user(s), CGM service 205 determines a corresponding CGM sensor identifier for each invited user (e.g., based on a CGM sensor purchased by the first user), associates the corresponding CGM sensor identifier to a user record for each invited user.

[0069] Method 900 also comprises act 902 of determining identifiers for each user in the community. In some embodiments, act 902 comprises determining a plurality of identifiers, including an identifier for the first user and a corresponding identifier for each additional user. In embodiments, each identifier is a CGM sensor identifier (e.g., sensor identifier 511) or a user identifier (e.g., user identifier 510).

[0070] Method 900 also comprises act 903 of forming the community. In some embodiments, act 903 comprises forming the group, including creating a database association between the plurality of identifiers. For example, community formation component 502 forms an association between user 402a, user 402b, and user 402n in database 507 in order to create community 401a. In some embodiments, creating the database association between the plurality of identifiers comprises creating a group data record, which is associated with each of the plurality of identifiers. In other embodiments, creating the database association between the plurality of identifiers comprises, for each user of the plurality of users, storing at least a subset of the plurality of identifiers in a user record for the user, the subset including an identifierassociated with each other user in the plurality of users. For example, for user record 508a, community information 513 stores identifiers associated with other community users. In other embodiments, creating the database association between the plurality of identifiers comprises, for each user of the plurality of users, storing a group identifier in a user record for the user (e.g., storing a group identifier in community information 513 for each user).

[0071] Method 900 also comprises act 904 of receiving CGM sensor data for community members. In some embodiments, act 904 comprises receiving CGM sensor data, including receiving a first portion of the CGM sensor data that is associated with the first user, and receiving a corresponding portion of the CGM sensor data that is associated with each additional user. For example, data acquisition component 503 receives CGM sensor data from devices corresponding to each of user 402a, user 402b, and user 402n, with that data having been generated by CGM sensors paired to those devices. In some embodiments, the portion of the CGM sensor data associated with each user is associated with a corresponding sensor identifier. In other embodiments, the portion of the CGM sensor data associated with each user is associated with a corresponding user identifier.

[0072] Method 900 also comprises act 905 of sending a CGM data report to all community members. In some embodiments, act 905 comprises, based on the CGM sensor data, sending a CGM data report to the first computing device associated with the first user, wherein, upon receipt of the CGM data report, each computing device is configured to display a visual representation of the CGM data report. For example, data presentation component 505 sends the report to devices corresponding to user 402a, user 402b, and user 402n, which then display the reports (e.g., based on application 207). In some examples, each computing device only displays the report upon request by the corresponding user. In some examples, personal device 203 is configured to display glucose data for two or more users concurrently.

[0073] In some embodiments, method 900 also comprises receiving, from one or more users of the plurality of users, a selection of a privacy setting or a sharing setting. In these embodiments, the method includes excluding corresponding glycemic data for one or more from the CGM data report based on the setting.

[0074] In embodiments, user computing devices are configured (e.g., by application 207, by CGM service 205) to provide user experiences that enhance user engagement. Examples include enabling a user to use gesture controls to navigate data reports (e.g., to zoom and scroll through displayed data; to reset a data report, such as by shaking personal device 203; to go to a home screen with a single cl ick / tap); displaying rewards (e.g., points that can be redeemed forsensors, etc.) for achievements (e.g., logging meals all week); and providing competitions to encourage the personal drive to log meals, eat well, time insulin and meals, etc.

[0075] In some embodiments, a group / community can be formed based on a doctor's patients, enabling the doctor to view patient information (e.g., as a comrade, admin, or caretaker). In these embodiments, CGM service 205 may provide patient analytics to doctors, which can encourage doctors to work to achieve better patient outcomes (e.g., by trying to achieve an overall time-in-range of over 90% for their patients).

[0076] Notably, any of the embodiments described in connection with method 800 are also applicable to method 900 and vice versa.

[0077] For concreteness, the examples herein focused on CGMs and forming communities around glucose / diabetes management. However, it will be appreciated that the embodiments described herein can be applied to a variety of sensors (e.g., alcohol, blood oxygen, heart rate, blood pressure) and analytes (ketone, lactate, etc.) to form communities around a variety of conditions or health concerns.

[0078] The present invention can also be described in accordance with the following numbered clauses.

[0079] Clause 1. A method, implemented at a computer system operating a continuous glucose monitor (CGM) service, the method comprising: forming a group of a plurality of users of the CGM service by creating a database association between a plurality of identifiers, each identifier associated with a different user; identifying CGM sensor data for the plurality of users, wherein the CGM sensor data is: generated by a corresponding CGM sensor associated with each user, and received from a corresponding computing device associated with each user; generating a CGM data report from the CGM sensor data, the CGM data report including glycemic data for at least a subset of the plurality of users; and sending the CGM data report to a first computing device associated with one of the plurality of users, wherein the first computing device is configured to display a visual representation of the glycemic data for the subset.

[0080] Clause 2. The method of clause 1, wherein each of the identifiers is a CGM sensor identifier.

[0081] Clause 3. The method of clause 1, wherein each of the identifiers is a user identifier.

[0082] Clause 4. The method of clause 1, wherein each portion of the CGM sensor data that is associated with each user is associated with a corresponding sensor identifier associated with the user.

[0083] Clause 5. The method of clause 1, wherein each portion of the CGM sensor data that is associated with each user is associated with a corresponding user identifier.

[0084] Clause 6. The method of clause 1, wherein creating the database association between the identifiers comprises creating a group record, the group record associated with each of the identifiers.

[0085] Clause 7. The method of clause 1, wherein creating the database association between the identifiers comprises storing at least a subset of the identifiers in a user record.

[0086] Clause 8. The method of clause 1, wherein creating the database association between the identifiers comprises storing a group identifier in a user record.

[0087] Clause 9. The method of clause 1, wherein at least one corresponding computing device is a special-purpose CGM reader device.

[0088] Clause 10. The method of clause 1, wherein at least one corresponding computing device is a smartphone.

[0089] Clause 11. The method of clause 1, wherein the method further comprises receiving the identifiers from the first computing device associated.

[0090] Clause 12. The method of clause 1, wherein the glycemic data includes a plot of historic glucose levels for each user in the subset.

[0091] Clause 13. The method of clause 1, wherein the glycemic data includes a historic time-in-range for each user in the subset.

[0092] Clause 14. The method of clause 1, wherein the method further comprises, analyzing the CGM sensor data; and generating a glycemic insight for two or more users.

[0093] Clause 15. The method of clause 14, wherein the glycemic insight is one of: a potential pre-diabetic condition; time-in-range exceeds a threshold; eating a meal; missed insulin; or a peak glucose level.

[0094] Clause 16. The method of clause 14, wherein the method further comprises sending a notification to one or more of the users based on the glycemic insight.

[0095] Clause 17. The method of clause 16, wherein the notification indicates at least one of: that at least one user may have a pre-diabetic condition; that at least one user has a time- in-range that exceeds a threshold; that at least one user is eating a meal; that at least one user has missed insulin; or that at least one user has a glucose level that reached a peak.

[0096] Clause 18. The method of clause 1, wherein the method further comprises receiving, from at least one user, a selection of a privacy setting or a sharing setting.

[0097] Clause 19. The method of clause 18, wherein the method further comprises, based on the selection of the privacy setting or the sharing setting, excluding corresponding glycemic data for the at least one user from the CGM data report.

[0098] Clause 20. The method of clause 1, wherein the method further comprises tracking a corresponding point count based on user participation.

[0099] Clause 21. The method of clause 20, wherein tracking the corresponding point count based on user participation includes tracking one or more of: adding one or more points for sharing CGM sensor data; adding one or more points for maintaining healthy glucose levels; adding one or more points for inviting additional group members; or adding one or more points for creating a group.

[0100] Clause 22. The method of clause 20, wherein a point count affects a user's ranking within a group.

[0101] Clause 23. The method of clause 20, wherein a point count rewards a user with an in-app badge.

[0102] Clause 24. The method of clause 20, wherein a point count rewards a user with a digital currency.

[0103] Clause 25. The method of clause 1, wherein each corresponding computing device is configured to present a digital coaching message to an associated user.

[0104] Clause 26. The method of clause 25, wherein the digital coaching message is based on CGM sensor data received by the corresponding computing device.

[0105] Clause 27. The method of clause 25, wherein the digital coaching message is based on diet tracking data received by the corresponding computing device.

[0106] Clause 28. The method of clause 25, wherein the digital coaching message is based on activity tracker data received by the corresponding computing device.

[0107] Clause 29. The method of clause 1, wherein at least one corresponding computing device is configured to present a child-focused user interface.

[0108] Clause 30. The method of clause 29, wherein the child-focused user interface presents a glucose level using at least one of a color, a character, or an emotion.

[0109] Clause 31. The method of clause 1, wherein each corresponding computing device is configured to present a comparison of an associated user's glucose data with a population.

[0110] Clause 32. The method of clause 1, wherein the plurality of users includes at least one patient diagnosed with a diabetic condition and at least one comrade who is a non-diabetic individual.

[0111] Clause 33. The method of clause 1, wherein the subset includes two or more of the plurality of users.

[0112] Clause 34. A computer system, comprising: a processor system; and a computer storage medium that stores computer-executable instructions that are executable by the processor system to at least: form a group of continuous glucose monitor (CGM) service users by creating a database association between identifiers, each identifier associated with a different user; identify CGM sensor data for the users, including identifying a portion of the CGM sensor data that is associated with each user, wherein the CGM sensor data is: generated by a CGM sensor associated with each user, and received from a corresponding computing device associated with each user; generate a CGM data report from the CGM sensor data, the CGM data report including glycemic data for two or more of the users; and send the CGM data report to a first computing device associated with a first user, wherein the first computing device is configured to display a visual representation of the glycemic data for the two or more users.

[0113] Clause 35. The computer system of clause 34, wherein each of the identifiers is a CGM sensor identifier.

[0114] Clause 36. The computer system of clause 34, wherein each of the identifiers is a user identifier.

[0115] Clause 37. The computer system of clause 34, wherein each portion of the CGM sensor data that is associated with each user is associated with a corresponding sensor identifier.

[0116] Clause 38. The computer system of clause 34, wherein the portion of the CGM sensor data that is associated with each user is associated with a corresponding user identifier.

[0117] Clause 39. The computer system of clause 34, wherein creating the database association between the identifiers comprises creating a group record, the group record associated with each of the identifiers.

[0118] Clause 40. The computer system of clause 34, wherein creating the database association between the identifiers comprises storing at least a subset of the identifiers in a user record.

[0119] Clause 41. The computer system of clause 34, wherein creating the database association between the identifiers comprises storing a group identifier in a user record.

[0120] Clause 42. The computer system of clause 34, wherein at least one corresponding computing device is a special-purpose CGM reader device.

[0121] Clause 43. The computer system of clause 34, wherein at least one corresponding computing device is a smartphone.

[0122] Clause 44. The computer system of clause 34, wherein the computer-executable instructions are also executable by the processor system to receive the identifiers from the corresponding computing device associated with one user.

[0123] Clause 45. The computer system of clause 34, wherein the glycemic data includes a plot of historic glucose levels for each of the two or more users.

[0124] Clause 46. The computer system of clause 34, wherein the glycemic data includes a historic time-in-range for each of the two or more users.

[0125] Clause 47. The computer system of clause 34, wherein the computer-executable instructions are also executable by the processor system to, analyze the CGM sensor data; and generate a glycemic insight for at least one user.

[0126] Clause 48. The computer system of clause 47, wherein the glycemic insight is one of: a potential pre-diabetic condition; a time-in-range exceeds a threshold; eating a meal; missed insulin; or a peak glucose level.

[0127] Clause 49. The computer system of clause 47, wherein the computer-executable instructions are also executable by the processor system to send a notification to one or more of the users based on the glycemic insight.

[0128] Clause 50. The computer system of clause 49, wherein the notification indicates at least one of: that one or more user may have a pre-diabetic condition; that one or more user has a time-in-range that exceeds a threshold; that one or more user is eating a meal; that one or more user has missed meal-time insulin; or that one or more user has a glucose level that reached a peak.

[0129] Clause 51. The computer system of clause 34, wherein the computer-executable instructions are also executable by the processor system to receive, from at least one user, a selection of a privacy setting or a sharing setting.

[0130] Clause 52. The computer system of clause 51, wherein the computer-executable instructions are also executable by the processor system to, based on the selection of the privacy setting or the sharing setting, exclude corresponding glycemic data for the at least one user from the CGM data report.

[0131] Clause 53. The computer system of clause 34, wherein the computer-executable instructions are also executable by the processor system to track a corresponding point count based on user participation.

[0132] Clause 54. The computer system of clause 53, wherein tracking the corresponding point count based on user participation includes tracking one or more of: adding one or more points for sharing CGM sensor data; adding one or more points for maintaininghealthy glucose levels; adding one or more points for inviting additional group members; or adding one or more points for creating a group.

[0133] Clause 55. The computer system of clause 53, wherein a point count affects a user's ranking within a group.

[0134] Clause 56. The computer system of clause 53, wherein a point count rewards a user with an in-app badge.

[0135] Clause 57. The computer system of clause 53, wherein a point count rewards a user with a digital currency.

[0136] Clause 58. The computer system of clause 53, wherein each corresponding computing device is configured to present a digital coaching message to an associated user.

[0137] Clause 59. The computer system of clause 58, wherein the digital coaching message is based on CGM sensor data received by the corresponding computing device.

[0138] Clause 60. The computer system of clause 58, wherein the digital coaching message is based on diet tracking data received by the corresponding computing device.

[0139] Clause 61. The computer system of clause 58, wherein the digital coaching message is based on activity tracker data received by the corresponding computing device.

[0140] Clause 62. The computer system of clause 34, wherein at least one corresponding computing device is configured to present a child-focused user interface.

[0141] Clause 63. The computer system of clause 62, wherein the child-focused user interface presents a glucose level using at least one of a color, a character, or an emotion.

[0142] Clause 64. The computer system of clause 34, wherein each corresponding computing device is configured to present a comparison of an associated user's glucose data with a population.

[0143] Clause 65. The computer system of clause 34, wherein the grouping includes at least one user diagnosed with a diabetic condition and at least one user who is a non-diabetic individual or is not pre-diabetic.

[0144] Clause 66. A method, implemented at a computer system operating a continuous glucose monitor (CGM) service, the method comprising: receiving, from a first computing device associated with a first user of the CGM service, a specification of one or more additional users to add to a group; determining a plurality of identifiers, including an identifier for the first user and a corresponding identifier for each additional user; forming the group, including creating a database association between the plurality of identifiers; receiving CGM sensor data, including receiving a first portion of the CGM sensor data that is associated with the first user, and receiving a corresponding portion of the CGM sensor data that is associated with each additional user; andbased on the CGM sensor data, sending a CGM data report to the first computing device associated with the first user, wherein, upon receipt of the CGM data report, each computing device is configured to display a visual representation of the CGM data report.

[0145] Clause 67. The method of clause 66, wherein each of the plurality of identifiers is a CGM sensor identifier.

[0146] Clause 68. The method of clause 66, wherein each of the plurality of identifiers is a user identifier.

[0147] Clause 69. The method of clause 66, wherein the method further comprises sending a notification to each of the one or more additional users, the notification inviting each of the one or more additional users to register for the CGM service.

[0148] Clause 70. The method of clause 66, wherein the method further comprises, initiating acquisition of a CGM sensor for each of the one or more additional users.

[0149] Clause 71. The method of clause 66, wherein the method further comprises, creating a corresponding user record for each of the additional users.

[0150] Clause 72. The method of clause 66, wherein the method further comprises: determining a corresponding CGM sensor identifier for each of the additional users; and associating the corresponding CGM sensor identifier to a user record for each of the additional users.

[0151] Clause 73. The method of clause 66, wherein the method further comprises, receiving, from a user, a selection of a privacy setting or a sharing setting.

[0152] Clause 74. The method of clause 73, wherein the method further comprises, based on the selection of the privacy setting or the sharing setting, excluding corresponding CGM sensor data for the user from the CGM data report.

[0153] Clause 75. The method of clause 66, wherein the first user is an individual diagnosed with a diabetic condition, and at least one of the one or more additional users is a nondiabetic individual.

[0154] Clause 76. The method of clause 66, wherein the method further comprises sending the CGM data report to a corresponding computing device associated with each additional user.

[0155] Clause 77. A computer system, comprising: a processor system; and a computer storage medium that stores computer-executable instructions that are executable by the processor system to at least: receive, from a first computing device associated with a first user of a continuous glucose monitor (CGM) service, a specification of one or more additional users to add to a group of users; determine a plurality of identifiers, including an identifier for the firstuser and a corresponding identifier for each of the additional users; form the group of users, including creating a database association between the plurality of identifiers; receive CGM sensor data, including receiving a first portion of the CGM sensor data that is associated with the first user, and receiving a corresponding portion of the CGM sensor data that is associated with one or more additional users; and based on the CGM sensor data, send a CGM data report to the first computing device associated with the first user, and to a corresponding computing device associated with each of the one or more additional users, wherein, upon receipt of the CGM data report, each corresponding computing device is configured to display a visual representation of the CGM data report.

[0156] Clause 78. The computer system of clause 77, wherein each of the plurality of identifiers is a CGM sensor identifier.

[0157] Clause 79. The computer system of clause 77, wherein each of the plurality of identifiers is a user identifier.

[0158] Clause 80. The computer system of clause 77, wherein the computer-executable instructions are also executable by the processor system to send a notification to each of the one or more additional users, the notification inviting each of the one or more additional users to register for the CGM service.

[0159] Clause 81. The computer system of clause 77, wherein the computer-executable instructions are also executable by the processor system to, based on receiving the specification of the one or more additional users, initiate an order of a CGM sensor for each of the one or more additional users.

[0160] Clause 82. The computer system of clause 77, wherein the computer-executable instructions are also executable by the processor system to, based on receiving the specification of the one or more additional users, create a corresponding user record for each of the one or more additional users.

[0161] Clause 83. The computer system of clause 77, wherein the computer-executable instructions are also executable by the processor system to, based on receiving the specification of the one or more additional users: determine a corresponding CGM sensor identifier for each of the one or more additional users; and associate the corresponding CGM sensor identifier to a user record for each of the one or more additional users.

[0162] Clause 84. The computer system of clause 77, wherein the computer-executable instructions are also executable by the processor system to, receive, from a user, a selection of a privacy setting or a sharing setting.

[0163] Clause 85. The computer system of clause 84, wherein the computer-executable instructions are also executable by the processor system to, based on the selection of the privacy setting or the sharing setting, exclude corresponding CGM sensor data for the user from the CGM data report.

[0164] Clause 86. The computer system of clause 77, wherein the first user is an individual diagnosed with a diabetic condition, and at least one of the one or more additional users is a non-diabetic individual.

[0165] Clause 87. The computer system of clause 77, wherein the computer-executable instructions are also executable by the processor system to send the CGM data report to the corresponding computing device.

[0166] Embodiments of the disclosure comprise or utilize a special-purpose or general- purpose computer system (e.g., CGM service 205, application 207) that includes computer hardware, such as, for example, a processor system and system memory, as discussed in greater detail below. Embodiments within the scope of the present disclosure also include physical and other computer-readable media for carrying or storing computer-executable instructions and / or data structures. Such computer-readable media can be any available media accessible by a general-purpose or special-purpose computer system. Computer-readable media that store computer-executable instructions and / or data structures are computer storage media. Computer-readable media that carry computer-executable instructions and / or data structures are transmission media. Thus, embodiments of the disclosure can comprise at least two distinctly different kinds of computer-readable media: computer storage media and transmission media.

[0167] Computer storage media are physical storage media that store computerexecutable instructions and / or data structures. Physical storage media include computer hardware, such as random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), solid state drives (SSDs), flash memory, phase-change memory (PCM), optical disk storage, magnetic disk storage or other magnetic storage devices, or any other hardware storage device(s) which store program code in the form of computer-executable instructions or data structures, which can be accessed and executed by a general-purpose or special-purpose computer system to implement the disclosed functionality.

[0168] Transmission media include a network and / or data links that carry program code in the form of computer-executable instructions or data structures that are accessible by a general-purpose or special-purpose computer system. A "network" is defined as a data link that enables the transport of electronic data between computer systems and other electronic devices. When information is transferred or provided over a network or another communicationsconnection (either hardwired, wireless, or a combination thereof) to a computer system, the computer system may view the connection as transmission media. The scope of computer- readable media includes combinations thereof.

[0169] Upon reaching various computer system components, program code in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa). For example, computerexecutable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module and eventually transferred to computer system RAM and / or less volatile computer storage media at a computer system. Thus, computer storage media can be included in computer system components that also utilize transmission media.

[0170] Computer-executable instructions comprise, for example, instructions and data which when executed at a processor system, cause a general-purpose computer system, a special-purpose computer system, or a special-purpose processing device to perform a function or group of functions. In embodiments, computer-executable instructions comprise binaries, intermediate format instructions (e.g., assembly language), or source code. In embodiments, a processor system comprises one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs), and the like.

[0171] In some embodiments, the disclosed systems and methods are practiced in network computing environments with many types of computer system configurations, including personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, and the like. In some embodiments, the disclosed systems and methods are practiced in distributed system environments where different computer systems, which are linked through a network (e.g., by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links), both perform tasks. As such, in a distributed system environment, a computer system may include a plurality of constituent computer systems. Program modules may be located in local and remote memory storage devices in a distributed system environment.

[0172] In some embodiments, the disclosed systems and methods are practiced in a cloud computing environment. In some embodiments, cloud computing environments are distributed, although this is not required. When distributed, cloud computing environments may be distributed internally within an organization and / or have components possessed across multiple organizations. In this description and the following claims, "cloud computing" is a modelfor enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). A cloud computing model can be composed of various characteristics, such as on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth. A cloud computing model may also come in the form of various service models such as Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (laaS), etc. The cloud computing model may also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, etc.

[0173] Some embodiments, such as a cloud computing environment, comprise a system with one or more hosts capable of running one or more virtual machines (VMs). During operation, VMs emulate an operational computing system, supporting an operating system (OS) and perhaps one or more other applications. In some embodiments, each host includes a hypervisor that emulates virtual resources for the VMs using physical resources that are abstracted from the view of the VMs. The hypervisor also provides proper isolation between the VMs. Thus, from the perspective of any given VM, the hypervisor provides the illusion that the VM is interfacing with a physical resource, even though the VM only interfaces with the appearance (e.g., a virtual resource) of a physical resource. Examples of physical resources include processing capacity, memory, disk space, network bandwidth, media drives, and so forth.

[0174] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described supra or the order of the acts described supra. Rather, the described features and acts are disclosed as example forms of implementing the claims.

[0175] The present disclosure may be embodied in other specific forms without departing from its essential characteristics. The described embodiments are only illustrative and not restrictive. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

[0176] When introducing elements in the appended claims, the articles "a," "an," "the," and "said" are intended to mean there are one or more of the elements. The terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements other than the listed elements. Unless otherwise specified, the terms "set," "superset," and "subset" are intended to exclude an empty set, and thus "set" is defined as a non-empty set, "superset" is defined as a non-empty superset, and "subset" is defined as a non-empty subset. Unless otherwise specified, the term "subset" excludes the entirety of its superset (i.e., thesuperset contains at least one item not included in the subset). Unless otherwise specified, a "superset" can include at least one additional element, and a "subset" can exclude at least one element.

Claims

CLAIMSWhat is claimed:

1. A method, implemented at a computer system operating a continuous glucose monitor (CGM) service, the method comprising: forming a group of a plurality of users of the CGM service by creating a database association between a plurality of identifiers, each identifier associated with a different user; identifying CGM sensor data for the plurality of users, wherein the CGM sensor data is: generated by a corresponding CGM sensor associated with each user, and received from a corresponding computing device associated with each user; generating a CGM data report from the CGM sensor data, the CGM data report including glycemic data for at least a subset of the plurality of users; and sending the CGM data report to a first computing device associated with one of the plurality of users, wherein the first computing device is configured to display a visual representation of the glycemic data for the subset.

2. The method of claim 1, wherein each of the identifiers is a CGM sensor identifier.

3. The method of claim 1, wherein each of the identifiers is a user identifier.

4. The method of claim 1, wherein each portion of the CGM sensor data that is associated with each user is associated with a corresponding sensor identifier associated with the user.

5. The method of claim 1, wherein each portion of the CGM sensor data that is associated with each user is associated with a corresponding user identifier.

6. The method of claim 1, wherein creating the database association between the identifiers comprises creating a group record, the group record associated with each of the identifiers.

7. The method of claim 1, wherein creating the database association between the identifiers comprises storing at least a subset of the identifiers in a user record.

8. The method of claim 1, wherein creating the database association between the identifiers comprises storing a group identifier in a user record.

9. The method of claim 1, wherein at least one corresponding computing device is a special-purpose CGM reader device.

10. The method of claim 1, wherein at least one corresponding computing device is a smartphone.

11. The method of claim 1, wherein the method further comprises receiving the identifiers from the first computing device associated.

12. The method of claim 1, wherein the glycemic data includes a plot of historic glucose levels for each user in the subset.

13. The method of claim 1, wherein the glycemic data includes a historic time-in- range for each user in the subset.

14. The method of claim 1, wherein the method further comprises, analyzing the CGM sensor data; and generating a glycemic insight for two or more users.

15. The method of claim 14, wherein the glycemic insight is one of: a potential pre-diabetic condition; time-in-range exceeds a threshold; eating a meal; missed insulin; or a peak glucose level.

16. The method of claim 14, wherein the method further comprises sending a notification to one or more of the users based on the glycemic insight.

17. The method of claim 16, wherein the notification indicates at least one of: that at least one user may have a pre-diabetic condition; that at least one user has a time-in-range that exceeds a threshold; that at least one user is eating a meal; that at least one user has missed insulin; or that at least one user has a glucose level that reached a peak.

18. The method of claim 1, wherein the method further comprises receiving, from at least one user, a selection of a privacy setting or a sharing setting.

19. The method of claim 18, wherein the method further comprises, based on the selection of the privacy setting or the sharing setting, excluding corresponding glycemic data for the at least one user from the CGM data report.

20. The method of claim 1, wherein the method further comprises tracking a corresponding point count based on user participation.

21. The method of claim 20, wherein tracking the corresponding point count based on user participation includes tracking one or more of: adding one or more points for sharing CGM sensor data; adding one or more points for maintaining healthy glucose levels; adding one or more points for inviting additional group members; or adding one or more points for creating a group.

22. The method of claim 20, wherein a point count affects a user's ranking within a group.

23. The method of claim 20, wherein a point count rewards a user with an in-app badge.

24. The method of claim 20, wherein a point count rewards a user with a digital currency.

25. The method of claim 1, wherein each corresponding computing device is configured to present a digital coaching message to an associated user.

26. The method of claim 25, wherein the digital coaching message is based on CGM sensor data received by the corresponding computing device.

27. The method of claim 25, wherein the digital coaching message is based on diet tracking data received by the corresponding computing device.

28. The method of claim 25, wherein the digital coaching message is based on activity tracker data received by the corresponding computing device.

29. The method of claim 1, wherein at least one corresponding computing device is configured to present a child-focused user interface.

30. The method of claim 29, wherein the child-focused user interface presents a glucose level using at least one of a color, a character, or an emotion.

31. The method of claim 1, wherein each corresponding computing device is configured to present a comparison of an associated user's glucose data with a population.

32. The method of claim 1, wherein the plurality of users includes at least one patient diagnosed with a diabetic condition and at least one comrade who is a non-diabetic individual.

33. The method of claim 1, wherein the subset includes two or more of the plurality of users.

34. A computer system, comprising: a processor system; and a computer storage medium that stores computer-executable instructions that are executable by the processor system to at least: form a group of continuous glucose monitor (CGM) service users by creating a database association between identifiers, each identifier associated with a different user; identify CGM sensor data forthe users, including identifying a portion of the CGM sensor data that is associated with each user, wherein the CGM sensor data is: generated by a CGM sensor associated with each user, andreceived from a corresponding computing device associated with each user; generate a CGM data report from the CGM sensor data, the CGM data report including glycemic data for two or more of the users; and send the CGM data report to a first computing device associated with a first user, wherein the first computing device is configured to display a visual representation of the glycemic data for the two or more users.

35. The computer system of claim 34, wherein each of the identifiers is a CGM sensor identifier.

36. The computer system of claim 34, wherein each of the identifiers is a user identifier.

37. The computer system of claim 34, wherein each portion of the CGM sensor data that is associated with each user is associated with a corresponding sensor identifier.

38. The computer system of claim 34, wherein the portion of the CGM sensor data that is associated with each user is associated with a corresponding user identifier.

39. The computer system of claim 34, wherein creating the database association between the identifiers comprises creating a group record, the group record associated with each of the identifiers.

40. The computer system of claim 34, wherein creating the database association between the identifiers comprises storing at least a subset of the identifiers in a user record.

41. The computer system of claim 34, wherein creating the database association between the identifiers comprises storing a group identifier in a user record.

42. The computer system of claim 34, wherein at least one corresponding computing device is a special-purpose CGM reader device.

43. The computer system of claim 34, wherein at least one corresponding computing device is a smartphone.

44. The computer system of claim 34, wherein the computer-executable instructions are also executable by the processor system to receive the identifiers from the corresponding computing device associated with one user.

45. The computer system of claim 34, wherein the glycemic data includes a plot of historic glucose levels for each of the two or more users.

46. The computer system of claim 34, wherein the glycemic data includes a historic time-in-range for each of the two or more users.

47. The computer system of claim 34, wherein the computer-executable instructions are also executable by the processor system to, analyze the CGM sensor data; and generate a glycemic insight for at least one user.

48. The computer system of claim 47, wherein the glycemic insight is one of: a potential pre-diabetic condition; a time-in-range exceeds a threshold; eating a meal; missed insulin; or a peak glucose level.

49. The computer system of claim 47, wherein the computer-executable instructions are also executable by the processor system to send a notification to one or more of the users based on the glycemic insight.

50. The computer system of claim 49, wherein the notification indicates at least one of: that one or more user may have a pre-diabetic condition; that one or more user has a time-in-range that exceeds a threshold; that one or more user is eating a meal; that one or more user has missed meal-time insulin; or that one or more user has a glucose level that reached a peak.

51. The computer system of claim 34, wherein the computer-executable instructions are also executable by the processor system to receive, from at least one user, a selection of a privacy setting or a sharing setting.

52. The computer system of claim 51, wherein the computer-executable instructions are also executable by the processor system to, based on the selection of the privacy setting or the sharing setting, exclude corresponding glycemic data for the at least one user from the CGM data report.

53. The computer system of claim 34, wherein the computer-executable instructions are also executable by the processor system to track a corresponding point count based on user participation.

54. The computer system of claim 53, wherein tracking the corresponding point count based on user participation includes tracking one or more of: adding one or more points for sharing CGM sensor data; adding one or more points for maintaining healthy glucose levels;adding one or more points for inviting additional group members; or adding one or more points for creating a group.

55. The computer system of claim 53, wherein a point count affects a user's ranking within a group.

56. The computer system of claim 53, wherein a point count rewards a user with an in-app badge.

57. The computer system of claim 53, wherein a point count rewards a user with a digital currency.

58. The computer system of claim 53, wherein each corresponding computing device is configured to present a digital coaching message to an associated user.

59. The computer system of claim 58, wherein the digital coaching message is based on CGM sensor data received by the corresponding computing device.

60. The computer system of claim 58, wherein the digital coaching message is based on diet tracking data received by the corresponding computing device.

61. The computer system of claim 58, wherein the digital coaching message is based on activity tracker data received by the corresponding computing device.

62. The computer system of claim 34, wherein at least one corresponding computing device is configured to present a child-focused user interface.

63. The computer system of claim 62, wherein the child-focused user interface presents a glucose level using at least one of a color, a character, or an emotion.

64. The computer system of claim 34, wherein each corresponding computing device is configured to present a comparison of an associated user's glucose data with a population.

65. The computer system of claim 34, wherein the grouping includes at least one user diagnosed with a diabetic condition and at least one user who is a non-diabetic individual or is not pre-diabetic.

66. A method, implemented at a computer system operating a continuous glucose monitor (CGM) service, the method comprising: receiving, from a first computing device associated with a first user of the CGM service, a specification of one or more additional users to add to a group; determining a plurality of identifiers, including an identifier for the first user and a corresponding identifier for each additional user; forming the group, including creating a database association between the plurality of identifiers;receiving CGM sensor data, including receiving a first portion of the CGM sensor data that is associated with the first user, and receiving a corresponding portion of the CGM sensor data that is associated with each additional user; and based on the CGM sensor data, sending a CGM data report to the first computing device associated with the first user, wherein, upon receipt of the CGM data report, each computing device is configured to display a visual representation of the CGM data report.

67. The method of claim 66, wherein each of the plurality of identifiers is a CGM sensor identifier.

68. The method of claim 66, wherein each of the plurality of identifiers is a user identifier.

69. The method of claim 66, wherein the method further comprises sending a notification to each of the one or more additional users, the notification inviting each of the one or more additional users to register for the CGM service.

70. The method of claim 66, wherein the method further comprises, initiating acquisition of a CGM sensor for each of the one or more additional users.

71. The method of claim 66, wherein the method further comprises, creating a corresponding user record for each of the additional users.

72. The method of claim 66, wherein the method further comprises: determining a corresponding CGM sensor identifier for each of the additional users; and associating the corresponding CGM sensor identifier to a user record for each of the additional users.

73. The method of claim 66, wherein the method further comprises, receiving, from a user, a selection of a privacy setting or a sharing setting.

74. The method of claim 73, wherein the method further comprises, based on the selection of the privacy setting or the sharing setting, excluding corresponding CGM sensor data for the user from the CGM data report.

75. The method of claim 66, wherein the first user is an individual diagnosed with a diabetic condition, and at least one of the one or more additional users is a non-diabetic individual.

76. The method of claim 66, wherein the method further comprises sending the CGM data report to a corresponding computing device associated with each additional user.

77. A computer system, comprising: a processor system; anda computer storage medium that stores computer-executable instructions that are executable by the processor system to at least: receive, from a first computing device associated with a first user of a continuous glucose monitor (CGM) service, a specification of one or more additional users to add to a group of users; determine a plurality of identifiers, including an identifier for the first user and a corresponding identifier for each of the additional users; form the group of users, including creating a database association between the plurality of identifiers; receive CGM sensor data, including receiving a first portion of the CGM sensor data that is associated with the first user, and receiving a corresponding portion of the CGM sensor data that is associated with one or more additional users; and based on the CGM sensor data, send a CGM data report to the first computing device associated with the first user, and to a corresponding computing device associated with each of the one or more additional users, wherein, upon receipt of the CGM data report, each corresponding computing device is configured to display a visual representation of the CGM data report.

78. The computer system of claim 77, wherein each of the plurality of identifiers is a CGM sensor identifier.

79. The computer system of claim 77, wherein each of the plurality of identifiers is a user identifier.

80. The computer system of claim 77, wherein the computer-executable instructions are also executable by the processor system to send a notification to each of the one or more additional users, the notification inviting each of the one or more additional users to register for the CGM service.

81. The computer system of claim 77, wherein the computer-executable instructions are also executable by the processor system to, based on receiving the specification of the one or more additional users, initiate an order of a CGM sensor for each of the one or more additional users.

82. The computer system of claim 77, wherein the computer-executable instructions are also executable by the processor system to, based on receiving the specification of the one or more additional users, create a corresponding user record for each of the one or more additional users.

83. The computer system of claim 77 , wherein the computer-executable instructions are also executable by the processor system to, based on receiving the specification of the one or more additional users: determine a corresponding CGM sensor identifier for each of the one or more additional users; and associate the corresponding CGM sensor identifier to a user record for each of the one or more additional users.

84. The computer system of claim 77, wherein the computer-executable instructions are also executable by the processor system to, receive, from a user, a selection of a privacy setting or a sharing setting.

85. The computer system of claim 84, wherein the computer-executable instructions are also executable by the processor system to, based on the selection of the privacy setting or the sharing setting, exclude corresponding CGM sensor data for the user from the CGM data report.

86. The computer system of claim 77, wherein the first user is an individual diagnosed with a diabetic condition, and at least one of the one or more additional users is a nondiabetic individual.

87. The computer system of claim 77, wherein the computer-executable instructions are also executable by the processor system to send the CGM data report to the corresponding computing device.

Images