Distributed system architecture for continuous glucose monitoring
By separating data into multiple categories in a distributed system and storing it encrypted in a cloud computing architecture, the problem of data confidentiality management is solved, and secure data access control and system expansion are achieved.
Patent Information
- Application Number
- CN202410965775.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2015-10-30
- Filing Date
- 2016-05-11
- Publication Date
- 2024-11-12
AI Technical Summary
Existing technologies struggle to effectively manage and protect the confidentiality and sensitivity of continuous glucose monitor data transmitted in distributed systems, especially when connected to different system components and third-party applications, posing a risk of data leakage.
By separating data into multiple categories (public and private data), encrypting it before launch, and storing and managing it separately in a cloud computing architecture, permission-based access control is provided, and a common application programming interface is provided using a hub and spoke topology, ensuring that unauthorized entities cannot access restricted data.
It enables secure management of data with varying sensitivity in a distributed system, ensuring the protection of confidential information, simplifying system expansion and access control, and reducing the complexity of regulatory review.
Smart Images

Figure CN118945188A_ABST
Abstract
Description
[0001] This application is a divisional application of a patent application with an application date of May 11, 2016, application number 202110995446.2, and invention name “Distributed System Architecture for Continuous Glucose Monitoring”.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 160,475 filed on May 12, 2015 and U.S. Provisional Patent Application No. 62 / 249,043 filed on October 30, 2015. The entire contents of the foregoing patent applications are incorporated by reference as part of the disclosure of this application. Technical Field
[0004] The present disclosure relates to a continuous glucose monitor for wirelessly transmitting data related to glucose values and controlling the display and distribution of the data. Background Art
[0005] Continuous glucose monitors have become increasingly popular as an easy way to monitor glucose levels. Prior to the use of continuous glucose monitors, users may have found it necessary to sample their blood glucose levels several times throughout the day, such as in the morning, around lunch time, and in the evening, using, for example, test strips that determine glucose levels from small blood samples. Continuous glucose monitors replace these test strips and provide electronic monitoring and display of glucose levels.
[0006] In addition to monitoring glucose levels, continuous glucose monitors can also generate and track a variety of other data related to glucose levels. For example, a continuous glucose monitoring system can track numerous data points, including patient identification information, time stamps, alerts established by the user, diagnostic information of the electronic unit associated with the continuous glucose monitor, and a variety of other information. The continuous glucose monitor can transmit this information to a display device so that the user can view the glucose level.
[0007] Initially, the continuous glucose monitor wirelessly transmits the data related to the glucose level to a dedicated display. The dedicated display is a medical device designed to display glucose levels, trend patterns and other information for users. However, with the increasing popularity of smartphones and software applications (app) executed on smartphones, some users prefer not to carry a dedicated display. Alternatively, some users prefer to monitor their glucose levels using a dedicated software application executed on their mobile computing or smart devices, such as smartphones, tablet computers or wearable devices such as smart watches or smart glasses. By using the software applications on these smart devices, the continuous glucose monitoring system can transmit glucose and continuous glucose monitor information to other devices, software applications and servers. These other devices, software applications and servers can provide enhanced glucose monitoring, allowing additional users to track a person's glucose level (e.g., parents monitor the glucose level of children), provide technical support related to system operation, and provide access to the medical data of patients for several other systems and applications. Summary of the invention
[0008] Systems and methods for controlling the distribution and use of data having multiple sensitivity categories (e.g., restricted, less restricted, etc.) throughout a distributed architecture are described in the present disclosure. Exemplary embodiments allow data to be sent from a continuous glucose monitor to one or more connected display devices and forwarded on to a cloud computing architecture. As described herein, several challenges arise with the distribution of data having different degrees of sensitivity, such as medical data, including, but not limited to, restricting third parties and certain system components from accessing restricted data, such as proprietary, confidential, or patient identifying information, while selectively allowing access to other less sensitive data, thereby ensuring that unauthorized entities cannot access restricted data, and providing a system that can be scaled to receive, store, and selectively grant access to large amounts of data.
[0009] In one illustrative embodiment, the continuous glucose monitor separates the data into multiple categories before transmission. The categories may be based on whether the data identifies the patient, contains proprietary information related to system operation (e.g., error codes, calibration equations, raw data, calibrated data, and the like), or contains information accessible to third parties and other system components. The categories will be referred to herein as public and private data. In other embodiments, a display or cloud computing architecture may separate the data into multiple categories. Subsequently, the cloud computing architecture may store the data separately and restrict access to only one or more of the multiple data categories based on the entity requesting access. Different systems may perform data synchronization at different times.
[0010] In other embodiments, different data streams containing different types of data can be sent to the server separately and stored separately. The data stream may be repeated, such as a continuous glucose monitor transmitting a data stream to two connected displays, each of which forwards its data (together with any other data generated by the display) to the server. This results in two separate data streams from two displays, which can be duplicate data. The cloud computing architecture stores the data streams separately, allowing it to easily grant or restrict access to data, and also allows comparison of data streams to ensure correct system operation. In addition, each display can actually transmit multiple data streams, wherein the data has been properly separated into one or more of a plurality of categories to allow easy classification and access based on permission. For example, each display can send two data streams, resulting in the cloud computing architecture receiving four data streams associated with a single continuous glucose monitor. The server can then continue the transmission with the display based on the transmission recently received from each specific display.
[0011] The continuous glucose monitor transmits the types of data at the same or different times. For example, the continuous glucose monitor transmits some data in real time (e.g., every five minutes) and transmits other data as part of a periodic batch transmission (e.g., every hour). The cloud computing architecture stores real-time and batch data separately. In addition, different components within the cloud computing architecture store real-time and batch data for different durations. This allows for quick access to more recent data, such as data generated in the last thirty days, without requiring a single server to store extremely large amounts of data. Alternatively, the cloud computing architecture stores long-term data in a separate storage device.
[0012] In other exemplary embodiments, the continuous glucose monitor may encrypt at least some of the data prior to transmission. Encryption prevents unauthorized third parties from accessing the data. The continuous glucose monitor encrypts some or all of the data, and only devices authorized to access specific types of data obtain decryption keys. For example, the continuous glucose monitor transmits multiple pieces of data to a display that only has a key to decrypt some of the data. The display forwards the data to a server that has a key to decrypt some or all of the data. In this way, the continuous glucose monitor encrypts private data that remains encrypted during distribution through the system until received by the server.
[0013] Other exemplary embodiments address a common interface for accessing the described distributed system architecture. The system or system component may be an approved medical device, which may require new approval for certain changes to the system design or operation. Again, third parties will request access to medical data, and third parties will use a variety of different types of requests. Third parties create new software applications and servers, which will require changes to the system to grant the requested access. For example, a third-party application requests access to glucose levels for the past week to integrate glucose levels with information about eating. Another application requests access to glucose levels to provide recommendations about insulin injections. These applications may have different interfaces and request access to different types of data (e.g., real-time to batch, glucose levels with or without patient identification information, etc.). To address these issues, the cloud computing architecture implements a hub and spoke topology that provides a set of common application interfaces. Third parties can interface with common application interfaces that have been granted regulatory approval. In addition, the system provides users with a single sign-on, so users do not need to log in to separate systems when users access various system modules.
[0014] In addition, an exemplary embodiment controls access to a patient's medical information by a remote monitor of a specific patient. A remote monitor is a person other than the patient who accesses the patient's glucose level using a continuous glucose monitor. For example, a parent or guardian can track their child's glucose level and be considered a remote monitor. Personal identification information that is kept confidential by system components can be problematic because the information may fall under HIPPA and other regulations. This can include information identifying the remote monitor itself and the location or other information identifying the remote monitor. In order to avoid storing identification information about the remote monitor, the remote monitor can register with the system through an anonymous identifier generator, and the system can store, for example, a unique number that associates the anonymous identification of the remote monitor with a display. The cloud computing architecture therefore does not need to receive or store any specific identification information for the remote monitor.
[0015] Other embodiments solve the challenges associated with the loss of transmission of data from a continuous glucose monitor. For example, a smartphone may be turned off or outside the wireless range, and therefore the data transmission will be lost. The display will therefore show some data loss, and the user may not even receive an alarm when his glucose level drops below or rises above the defined level because the display is outside the communication with the continuous glucose monitor. This same problem of lost data is equally applicable to other components of the entire system, including components in additional displays, third-party applications, and cloud computing architectures. In order to solve this challenge, an embodiment identifies when a specific device is losing data. Subsequently, the lost data can be selectively provided to the device as part of a process called backfill. For example, the display searches for lost data within the last six hours. After identifying the lost data, the display requests and receives the lost data (i.e., "backfill" lost data) from a continuous glucose monitor, another display, or another system component. The display or other system components also search for additional time intervals depending on the component until a defined maximum value, such as one day or thirty days, and backfill other lost data. The display then explains to the user which data was scheduled or received when it was transmitted (i.e., "just in time") versus data received after a delay and through a backfill process. This allows the user to easily identify why the display did not generate an alarm at a given time, such as when the device was out of range and therefore it did not receive any glucose levels to evaluate against the alarm limits.
[0016] Another challenge arises with regard to distinguishing between data received after transmission, either scheduled or through a backfill process. When a user misses an alarm because the device is out of range, but looks at their smartphone and sees that glucose data is available in the time range in which the alarm would have been issued, the user may become confused or assume that the alarm is in error. However, the smartphone does not have the data at the time of the alarm, but backfills the data later. To address this issue, in some embodiments, the display and cloud computing architecture store an indication of whether the data is scheduled after transmission or received later as part of the backfill process. The cloud computing architecture stores the data separately, along with an indication to distinguish the data, for subsequent technical support and other issues. In addition, multiple displays send separate data streams to the cloud computing architecture, which stores the data streams separately, along with an indication of which display sent the data. This allows the cloud computing architecture to identify which display forwarded the data and helps identify the source of any problems.
[0017] In one aspect, a method for securely transmitting data related to glucose levels is described. The method may include: preparing data including glucose levels using a continuous glucose monitor; wirelessly transmitting the data related to glucose levels from a transmitter associated with the continuous glucose monitor to at least one display device; automatically forwarding the data related to glucose levels from the display device to a cloud computing architecture; and storing the data related to glucose levels in a separate group at the cloud infrastructure. The data related to glucose levels may include measured glucose values and diagnostic data.
[0018] Optionally or alternatively, the above method may further comprise including, by the display device, additional data together with the data related to glucose level, wherein automatically forwarding the data comprises automatically forwarding the additional data together with the data related to glucose level.
[0019] Optionally or alternatively, the data related to glucose levels may include a first data set and a second data set, and storing the data related to glucose levels in separate groups may include storing the first data set on a first server and storing the second data set on a second server. Optionally or alternatively, the first data set may include real-time data including one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set includes at least one of information for calibrating the continuous glucose monitor and information for technical support of the continuous glucose monitor.
[0020] Optionally or alternatively, the above method may further include: encrypting the first data set by the transmitter; encrypting the second data set by the transmitter; decrypting and displaying the first data set by the at least one display device; preventing the at least one display device from decrypting the second data set; and decrypting the second data set by the cloud infrastructure.
[0021] Optionally or alternatively, the above method may further include: storing, by the at least one display device, a first key for decrypting the first data set; storing, by the cloud infrastructure, a second key for decrypting the second data set; and preventing the at least one display device from accessing the second key.
[0022] Optionally or alternatively, the above method may further comprise forwarding a subset of the data related to glucose levels from the cloud infrastructure to a second display device, the subset of data comprising at least one of current and past glucose levels.
[0023] Optionally or alternatively, the method may further include selectively determining by the cloud infrastructure whether to grant access to the first data set and the second data set to one or more requesting systems. The requesting systems may include a technical support system, at least one third-party application, and a data warehouse, wherein the cloud infrastructure: grants the technical support system access to the first data set and the second data set; grants the at least one third-party application access to the first data set; and grants the data warehouse access to the first data set and the second data set.
[0024] Optionally or alternatively, the display device may include at least one of a smart phone or a display.
[0025] In another aspect, a system for monitoring data related to glucose levels is disclosed. The system may include: a continuous glucose sensor configured to prepare data related to glucose levels; a wireless transmitter configured to transmit the data related to glucose levels; a display device configured to receive the transmitted data related to glucose levels and automatically forward the data; and a cloud computing architecture configured to receive the automatically forwarded data and store the data related to glucose levels in a separate group. The data related to glucose levels include measured glucose values and diagnostic data.
[0026] Optionally or alternatively, the above system may be further configured to: include additional data together with said data related to glucose levels; and automatically forward said additional data together with said data related to glucose levels.
[0027] Optionally or alternatively, in the above system, the data related to glucose levels may include a first data set and a second data set, and storing the data related to glucose levels in separate groups may include storing the first data set separately on a first server and storing the second data set on a second server.
[0028] Optionally or alternatively, in the above-mentioned system, the first data set may include real-time data, wherein the real-time data includes one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set may include information for calibrating the continuous glucose monitor and at least one of information for technical support of the continuous glucose monitor.
[0029] Optionally or alternatively, in the above system, the transmitter may be further configured to encrypt the first data set and the second data set; the at least one display device may be further configured to decrypt and display the first data set; the at least one display device is unable to decrypt the second data set; and the cloud infrastructure may be further configured to decrypt the second data set.
[0030] Optionally or alternatively, in the above system, the at least one display device may be further configured to store a first key for decrypting the first data set; the cloud infrastructure may be further configured to store a second key for decrypting the second data set; and the at least one display device cannot access the second key.
[0031] Optionally or alternatively, in the above system, the cloud infrastructure may be further configured to forward a subset of the data related to glucose levels to a second display device, the subset of data including at least one of current and past glucose levels.
[0032] Optionally or alternatively, in the above system, the cloud infrastructure may be further configured to selectively determine whether to grant access to the first data set and the second data set to one or more requesting systems. The requesting systems may include a technical support system, at least one third-party application, and a data warehouse, wherein the cloud infrastructure may be further configured to: grant access to the first data set and the second data set to the technical support system; grant access to the first data set to the at least one third-party application; and grant access to the first data set and the second data set to the data warehouse.
[0033] Optionally or alternatively, in the above system, the display device may include at least one of a smart phone or a display.
[0034] In yet another aspect of the present disclosure, a computer-readable medium is described that includes instructions that, when executed by one or more processors, perform a method for securely transmitting data related to glucose levels. The instructions may include: preparing data related to glucose levels using a continuous glucose monitor; wirelessly transmitting the data related to glucose levels from a transmitter associated with the continuous glucose monitor to at least one display device; automatically forwarding the data related to glucose levels from the display device to a cloud computing architecture; and storing the data related to glucose levels in a separate group at the cloud infrastructure. The data related to glucose levels may include measured glucose values and diagnostic data.
[0035] Optionally or alternatively, the instructions may include including, by the display device, additional data along with the data relating to glucose levels, wherein automatically forwarding the data comprises automatically forwarding the additional data along with the data relating to glucose levels.
[0036] Optionally or alternatively, the instructions may include: the data related to glucose levels includes a first data set and a second data set, and storing the data related to glucose levels in separate groups includes storing the first data set and the second data set separately by the cloud infrastructure.
[0037] Optionally or alternatively, the instructions may include: the first data set includes real-time data, which may include one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set may include information for calibrating the continuous glucose monitor and at least one of information for technical support for the continuous glucose monitor.
[0038] Optionally or alternatively, the instructions may include: encrypting the first data set by the transmitter; encrypting the second data set by the transmitter; decrypting and displaying the first data set by the at least one display device; preventing the at least one display device from decrypting the second data set; and decrypting the second data set by the cloud infrastructure.
[0039] Optionally or alternatively, the instructions may include: storing, by the at least one display device, a first key for decrypting the first data set; storing, by the cloud infrastructure, a second key for decrypting the second data set; and preventing the at least one display device from accessing the second key.
[0040] Optionally or alternatively, the instructions may include forwarding a subset of the data related to glucose levels from the cloud infrastructure to a second display device, the subset of data including at least one of current and past glucose levels.
[0041] Optionally or alternatively, the instructions may include selectively determining, by the cloud infrastructure, whether to grant access to the first set of data and the second set of data to one or more requesting systems.
[0042] Optionally or alternatively, the instructions may include: the requesting system includes a technical support system, at least one third-party application, and a data warehouse, wherein the cloud infrastructure: grants the technical support system access to the first data set and the second data set; grants the at least one third-party application access to the first data set; and grants the data warehouse access to the first data set and the second data set.
[0043] Various other embodiments of systems, methods, and computer-readable media associated with securely transmitting data related to glucose levels are also disclosed herein, including, for example: a method for encrypting and transmitting data related to glucose levels from a continuous glucose monitor; a system for encrypting and transmitting data related to glucose levels from a continuous glucose monitor; one or more computer-readable media including instructions that, when executed by one or more processors, perform the method for encrypting and transmitting data related to glucose levels from a continuous glucose monitor; a method for controlling access to data related to glucose levels; a system for controlling access to data related to glucose levels; one or more computer-readable media including instructions that, when executed by one or more processors, perform the method for encrypting and transmitting data related to glucose levels from a continuous glucose monitor; a method for controlling access to data related to glucose levels; a system for controlling access to data related to glucose levels; one or more computer-readable media including instructions a method for controlling access to data related to glucose levels when executed; a method for updating data related to glucose levels in a distributed architecture; a system for updating data related to glucose levels in a distributed architecture; one or more computer-readable media comprising instructions, which when executed by one or more processors execute the method for updating data related to glucose levels in a distributed architecture; a method for synchronizing data related to glucose levels in a distributed architecture system; a system for synchronizing data related to glucose levels in a distributed architecture system; one or more computer-readable media comprising instructions, which when executed by one or more processors execute the method for synchronizing data related to glucose levels in a distributed architecture system; and similar embodiments.
[0044] Further disclosed herein is a system for securely collecting, analyzing, and reporting data related to glucose monitoring levels through multiple continuous glucose monitors. In one aspect, the system includes: multiple continuous glucose monitors (CGMs); multiple display devices that receive data from the multiple CGMs, wherein the data is classified into multiple categories based on data type; a cloud server architecture that includes multiple servers that receive the data from the multiple display devices on an intermittent basis, wherein the data routed to a particular server in the multiple servers is determined by the data type, and wherein the intermittent basis varies depending on the data type; multiple remote monitor display devices that receive data from one of the multiple servers, wherein the data sent to each of the multiple remote monitor display devices depends on the data type and on the display device that transmits the data to the one of the multiple servers, and the data is sent to the multiple remote monitor display devices immediately after being received by the one of the multiple servers; and an analysis and reporting engine, wherein at least a portion of the data received by the multiple servers is transmitted to the analysis and reporting engine, the transmitted data is analyzed by the analysis and reporting engine, and a report is generated by the analysis and reporting engine.
[0045] In one aspect, the plurality of servers constituting the cloud server architecture include at least a real-time server and a batch data collector.
[0046] In one aspect, the data types include real-time data and batch data.
[0047] In one aspect, the real-time data is routed from the plurality of display devices to the real-time server, and the batch data is routed from the plurality of display devices to the batch data collector. In one aspect, the real-time data is routed from the plurality of display devices to the real-time server on an intermittent basis more frequently than the batch data is routed from the plurality of display devices to the batch data collector. In one aspect, the real-time data is routed from the plurality of display devices to the real-time server once every five minutes, and the batch data is routed from the plurality of display devices to the batch data collector once every hour.
[0048] In one aspect, the system further comprises a locator service, wherein the plurality of display devices are connected to the cloud server architecture via the locator service.
[0049] In one aspect, at least one of the plurality of display devices comprises a smart phone.
[0050] In one aspect, at least one of the plurality of remote monitor display devices comprises a smart phone.
[0051] In one aspect, the plurality of display devices includes at least 150,000 devices.
[0052] In one aspect, at least one of the plurality of remote monitor display devices further comprises an application executable by the at least one of the plurality of remote display devices. In one aspect, the application on the at least one of the plurality of remote monitor display devices must be open and running in order to receive the data ready to be sent to the at least one of the plurality of remote monitor display devices, otherwise the data ready to be sent to the at least one of the plurality of remote monitor display devices is maintained by one of the plurality of servers.
[0053] In one aspect, at least one of the plurality of remote monitor display devices receiving data from one of the plurality of servers receives a notification that data is ready to be sent to the at least one of the plurality of remote monitor display devices. The notification may include a text message.
[0054] In one aspect, the application executable by the at least one of the plurality of remote display devices wakes up when the one of the plurality of servers attempts to send the data to the at least one of the plurality of remote display devices. In one aspect, the application requests that the data be sent from the one of the plurality of servers after the application wakes up.
[0055] A method for securely collecting, analyzing, and reporting data related to glucose monitoring levels through multiple continuous glucose monitors is also disclosed. In one aspect, the method includes: receiving data from multiple continuous glucose monitors (CGMs) by multiple display devices; classifying the data into multiple categories based on data type; transmitting the data from the multiple display devices to a cloud server architecture, which includes multiple servers that receive the data from the multiple display devices on an intermittent basis, wherein the data routed to a particular server in the multiple servers is determined by the data type, and wherein the intermittent basis varies depending on the data type; receiving data from one of the multiple servers by multiple remote monitor display devices, wherein the data sent to each of the multiple remote monitor display devices depends on the data type and on the display device that transmits the data to the one of the multiple servers, and the data is sent to the multiple remote monitor display devices immediately after being received by the one of the multiple servers; and receiving at least a portion of the data received by the multiple servers by an analysis and reporting engine, the received data being analyzed by the analysis and reporting engine and a report being generated by the analysis and reporting engine. In one aspect, the plurality of servers constituting the cloud server architecture include at least a real-time server and a batch data collector.
[0056] In one aspect, classifying the data into a plurality of categories based on data type may include classifying the data into real-time data and batch data. The real-time data may be routed from the plurality of display devices to the real-time server, and the batch data may be routed from the plurality of display devices to the batch data collector.
[0057] In one aspect, the real-time data is routed from the plurality of display devices to the real-time server on an intermittent basis more frequently than the batch data is routed from the plurality of display devices to the batch data collector on an intermittent basis. For example, the real-time data may be routed from the plurality of display devices to the real-time server once every five minutes, and the batch data may be routed from the plurality of display devices to the batch data collector once an hour.
[0058] In one aspect, the method may further utilize a locator service, wherein the plurality of display devices are connected to the cloud server architecture via the locator service.
[0059] In one aspect, at least one of the plurality of display devices comprises a smart phone.
[0060] In one aspect, at least one of the plurality of remote monitor display devices comprises a smart phone.
[0061] In one aspect of the method, the plurality of display devices includes at least 150,000 devices.
[0062] In one aspect, at least one of the plurality of remote monitor display devices further comprises an application executable by the at least one of the plurality of remote display devices. In one aspect, the application on the at least one of the plurality of remote monitor display devices must be open and running in order to receive the data ready to be sent to the at least one of the plurality of remote monitor display devices, otherwise the data ready to be sent to the at least one of the plurality of remote monitor display devices is maintained by one of the plurality of servers.
[0063] In one aspect, at least one of the plurality of remote monitor display devices receiving data from one of the plurality of servers receives a notification that data is ready to be sent to the at least one of the plurality of remote monitor display devices. For example, the notification may include a text message.
[0064] In one aspect, the application executable by the at least one of the plurality of remote display devices wakes up when the one of the plurality of servers attempts to send the data to the at least one of the plurality of remote display devices. In one aspect, the application requests that the data be sent from the one of the plurality of servers after the application wakes up.
[0065] Other systems, methods, features and / or advantages will become apparent to one skilled in the art upon review of the following figures and detailed description. It is intended that all such additional systems, methods, features and / or advantages be included within this description and be protected by the accompanying claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0066] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments and, together with the description, serve to explain the principles of the methods and systems:
[0067] Figure 1 An exemplary system for monitoring glucose levels and controlling access and use of medical data is illustrated.
[0068] Figure 2 An exemplary method for providing data streams to a cloud computing architecture is illustrated.
[0069] Figure 3 An exemplary embodiment of a system of a cloud computing architecture according to the present technology is illustrated.
[0070] Figure 4 An exemplary method for storing data in separate groups is illustrated.
[0071] Figure 5 An exemplary system for encrypting medical data is illustrated.
[0072] Figure 6 An exemplary method for encrypting medical data is illustrated.
[0073] Figure 7 An exemplary method for providing a common interface through which access data may be passed is illustrated.
[0074] Figure 8 An exemplary system diagram for handling requests from a display to a cloud computing architecture is illustrated.
[0075] Fig. 9A An example of a continuous glucose monitor application executing on a display is illustrated.
[0076] Fig. 9B An exemplary embodiment of a system according to a cloud server architecture for performing aspects of the described techniques is illustrated.
[0077] Fig. 9C Data and control flow associated with an exemplary locator service is illustrated.
[0078] Fig.9D is a flow chart illustrating a method for securely collecting, analyzing, and reporting data related to glucose monitoring levels via multiple continuous glucose monitors.
[0079] Fig.10 An exemplary method for backfilling missing data is illustrated.
[0080] Fig.11 An exemplary method for backfilling missing data is illustrated.
[0081] Fig. 12A and 12B Various views are illustrated depending on the orientation of the display.
[0082] Fig.13 An exemplary computer for use with the disclosed embodiments is illustrated. DETAILED DESCRIPTION
[0083] The present disclosure relates to techniques for receiving glucose data from a continuous glucose sensor and controlling the use and redistribution of the data so the data is used in an intended manner.
[0084] As used in the specification and the appended claims, the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates otherwise. Ranges may be expressed herein as from "about" one particular value and / or to "about" another particular value. When such a range is expressed, another embodiment includes from a particular value and / or to another particular value. Similarly, when a value is expressed as an approximation by using the antecedent "about", it will be understood that the particular value forms another embodiment. It will be further understood that the endpoints of each of the ranges are significant in relation to the other endpoint and are also significant independently of the other endpoint.
[0085] "Optional" or "optionally" means that the subsequently described event or circumstance may or may not occur, and that the description includes instances where said event or circumstance occurs and instances where it does not.
[0086] Throughout the description and claims of this specification, the word "include" and variations of the word mean "including but not limited to", and are not intended to exclude, for example, other additives, components, integers or steps. "Exemplary" means "an example of..." and is not intended to convey an indication of a preferred or ideal embodiment. "For example" is not used in a limiting sense, but for illustrative purposes.
[0087] Disclosed are components and features that can be used to perform the disclosed methods and systems. These and other components are disclosed herein, and it should be understood that when combinations, subsets, interactions, groups, etc. of these components are disclosed, although specific references to each of the various individual and common combinations and arrangements of these may not be explicitly disclosed, for all methods and systems, each is specifically contemplated and described herein. This applies to all aspects of the application, including (but not limited to) steps in the disclosed methods. Therefore, if there are multiple additional steps that can be performed, it should be understood that each of these additional steps can be performed with respect to any specific embodiment or combination of embodiments of the disclosed methods.
[0088] Distributing glucose information, related health information, and continuous glucose monitor device information throughout the system and to other systems and applications creates challenges associated with protecting patient confidentiality. Glucose information, diagnostic information, and other confidential or proprietary information are not suitable for reproducing to all additional systems and applications. Because additional systems and applications should not have access to all data, it would be beneficial to separate and classify the data and protect the redistribution of some or all of the data in a manner that ensures patient confidentiality.
[0089] In an illustrative example, a continuous glucose monitor can transmit glucose levels, timestamps indicating when the monitor obtains glucose level measurements, and patient identification information to a display. The display forwards this information to a server repository that also stores information from several other patients. Some applications can request access to this information and receive glucose levels, timestamps, and patient identification information. As an example, a patient may wish their doctor's office to access this information. However, patient identification information is unnecessary for providing technical support for users experiencing problems with their continuous glucose monitors. In the example, patient identification information should therefore be excluded and technical support is limited from understanding the identity of the patient.
[0090] Another problem that arises about storing data associated with a continuous glucose monitor at a server includes how to organize and store data. This data may include, for example, data related to a patient's glucose level, raw or calibrated data from a continuous glucose monitor, warning data including warning levels, fault detection data, and similar data. Thousands of patients may use a continuous glucose monitor that forwards a large amount of data to a server based on a rule-based basis. The process of receiving, storing, and providing selective access to third parties, authorized users, and additional system components generates a large processing load on the server. In an illustrative example, a continuous glucose monitor obtains a glucose level reading and an associated time stamp every five minutes. The display forwards the glucose level and time stamp to the server for storage together with the additional data described below. Therefore, in this example, the server receives two hundred and eighty-eight glucose levels, time stamps, and additional data from a single user every day. For 20,000 continuous glucose monitors operating over the course of a month, the server will receive more than 175 million data transmissions including glucose levels, time stamps, and additional data. The same server must archive this information, control access to portions of the information, search for selected portions of the information, and forward the selected portions of the information to authorized entities. This generates a huge processing burden on the server.
[0091] In addition, the challenge is that the continuous glucose monitor can transmit data such as glucose level, time stamp and other associated information wirelessly to multiple displays, and each display can forward data to a server. In an illustrative example, the continuous glucose monitor transmits data to a receiver with a display, as well as a smart phone, smart watch, personal computer, tablet computer or other type of display. In this example, two data streams of each user can be sent to the server, thereby bringing repeated data. In addition, a display may be offline, such as when a smart phone turns off or breaks away from the wireless range of the continuous glucose monitor, so the two data streams from the two displays associated with the same continuous glucose monitor are different. The two data streams may also be different for other reasons. In an example, the two displays can use different calibration values, thereby obtaining different glucose levels based on the same data set received from the continuous glucose monitor. Therefore, it will be beneficial to organize, store and provide accurate regeneration of the data received from multiple displays.
[0092] Another challenge arises with respect to the security of the transmission of data throughout the system. While some components in the distributed architecture should be allowed to access certain data, other components should not be allowed to access. Therefore, it would be beneficial to restrict unauthorized parties from accessing data and to restrict authorized parties from accessing only a subset of data. In addition, there may be a large number of other devices or software applications that access the data stored by the server. Considering the possibility of these large numbers of other devices or software applications, it would be beneficial to provide a standardized interface for allowing access to data. Again, this may be particularly difficult in the field of medical devices where the system may need to obtain regulatory approval as a medical device. Once approved, changes to the system may require further regulatory approval, which may be a time-consuming and costly process. Therefore, a modular, standardized interface that can accommodate many different third-party components and is suitable for different requests from third-party components without requiring changes to the system design would be beneficial.
[0093] The present disclosure is directed to systems and methods for controlling the distribution and use of data with multiple sensitivity categories (e.g., restricted, less restricted, etc.) throughout a distributed architecture. In some example embodiments, an architecture according to the present technology allows data to be sent from a medical device (e.g., a continuous glucose monitor) to one or more connected display devices (e.g., a smart phone, a tablet computer, or a wearable smart device such as a smart watch or smart glasses) and provided to a cloud computing system, which is designed to distribute data according to various sensitivity levels of the data (e.g., for medical data, proprietary, confidential, or patient-identifying information) to control access to data by third parties and / or certain system components based on the determined sensitivity levels. In some embodiments of the present technology, these third parties and / or certain system components will be blocked from accessing restricted data without permission, while being selectively allowed to access other less sensitive data, such as ensuring that unauthorized entities cannot access restricted data, and providing a system that can be scaled to receive, store, and selectively grant access to large amounts of data. Although several examples of distributed architectures are described for continuous glucose monitoring, other example implementations are discussed below throughout the specification, and the scope of the claims should not be limited to only addressing embodiments associated with continuous glucose monitoring.
[0094] The present method and system may be understood more readily by reference to the following detailed description of the preferred embodiments and the Examples included therein and by reference to the drawings and their previous and following descriptions.
[0095] Figure 1 An exemplary system for monitoring glucose levels and controlling access to and use of data associated with such monitoring is illustrated.This data may be defined as having multiple categories, with each category having one or more sensitivity levels. Figure 1 The disclosed system can be used to store and distribute data, wherein data in different categories or with different sensitivity levels can be handled differently within the system. For example, data that identifies or can be used to identify a patient should not be reproduced to all third parties. Only third parties with appropriate permission or authorization should be able to access this data. In addition, other data such as glucose levels can be misused by third parties. As an example, a third party that receives the monitored glucose level may make an erroneous recommendation to the user on how to control his insulin pump. Figure 1 The system allows some data to be processed differently from other data by separating categories of data, such as public data, private data, real-time data (e.g., raw or calibrated), and other batch data, as described below. Figure 1 The system can allow some data to be processed differently from other data by providing permission-based access to the data. Figure 1The system can store and provide access to large amounts of data. For example, Figure 1 The system can temporarily store some data in the cloud computing architecture, such as data within a recently defined time period (e.g., 15 days, 30 days, 60 days, etc.), and periodically transfer other data, such as data older than thirty days, to a longer-term storage device.
[0096] refer to Figure 1 , the continuous glucose sensor units 100a to c obtain a series of measurements related to the patient's glucose level. The continuous glucose sensor units 100a to c can be worn, for example, in the abdominal area of the patient. A small sensor can be extended into the patient's body to obtain a reading of the glucose value using, for example, a subcutaneous glucose or blood glucose reading. The continuous glucose sensor units 100a to c can also be transcutaneous devices, intravascular devices, or non-invasive devices.
[0097] The continuous glucose sensor unit 100a to c includes several components to obtain glucose measurements, store data, calculate glucose levels, and communicate with displays 104a to e. Displays 104a to e may be dedicated receivers associated with the continuous glucose sensor unit 100a to c, such as, but not limited to, smart phones, wearable smart devices such as smart watches and smart glasses, personal computers, tablet computers, and a variety of other computing devices. Although not shown, the continuous glucose sensor unit 100a to c includes a non-volatile memory, a processor, a battery, and a wireless transmitter for storing historical data about glucose values. The continuous glucose sensor unit 100a to c includes a transmitter 102a to c, which can provide any type of wireless communication, such as including a Bluetooth connection, a Wi-Fi connection, an RF connection, and other connections to communicate with the display 104a to e and other computing devices. Wireless communication occurs between paired authenticated devices in some embodiments, and encryption and other cryptographic techniques are used, for example, to ensure that the communication remains confidential.
[0098] Although illustrated as a single unit, portions of the continuous glucose sensor unit 100a to c can be removed from the remainder of the continuous glucose sensor unit. For example, a reusable electronic device portion (e.g., a data transmitter and / or receiver, a battery, a memory, and / or a processor) of the sensor unit 100a to c, which may be referred to as a "transmitter" (e.g., transmitter 102), can be removed from a single-use portion of the sensor unit (e.g., a sensor needle) and reused with a new single-use portion. In addition, the continuous glucose sensor unit 100a to c may include other components to facilitate data communication. For example, the continuous glucose sensor unit 100 includes a wired port, such as a USB port, an Ethernet port, and other ports, for communicating with other devices and providing data related to glucose levels.
[0099] Figure 1 The continuous glucose sensor units 100a-c may obtain samples at predetermined intervals, such as every few seconds, every thirty seconds, every minute, every five minutes, or on demand in response to the occurrence of an event (e.g., a command from a user, detection of a user action such as user movement, and the like). The wireless transmitters 102a-c may be turned off or placed in a low power state to save battery life while taking one or more measurements for a period of time, and then wake up the transmitter to wirelessly transmit the one or more measurements to the displays 104a-e in a batch transmission. For example, the continuous glucose sensor units 100a-c wake up the wireless transmitter every five minutes, transmit data related to the glucose measurements generated in the last five minutes (and any other data), and transmit the data to the displays 104a-e. The wireless transmitters 102a-c may then be turned off again to save battery life. Although an example of transmitting data every five minutes has been provided, it will be appreciated that longer or shorter time periods may be used, and that the time periods may be configured by the user via the displays 104a-c.
[0100] In addition, Figure 1 d can be used by a second patient, the continuous glucose sensor unit 100c and the display 104a to 104b can be used by a third patient; and many other patients can use the continuous glucose sensor unit and the associated display. The display 104a to e or the continuous glucose sensor unit 100a to c transmits data to a distributed cloud computing architecture 106, which is also referred to as a cloud computing infrastructure, as described in more detail below.
[0101] The data transmitted between the continuous glucose sensor units 100a to c and the displays 104a to e can be any type of data related to monitoring glucose values and the operation of the continuous glucose sensor units 100a to c. For example, the continuous glucose sensor units 100a to c exchange calibration data with the corresponding displays 104a to e at initial startup and periodically to maintain the accuracy of the glucose measurements. The user can sample their glucose levels using a single-point glucose meter, enter the value displayed by the test kit into one of the displays 104a to e, and use the value to calibrate the associated continuous glucose sensor unit. Similarly, data can also be exchanged between other physiological monitoring devices (e.g., temperature detection devices, blood pressure monitors, blood oxygen content monitors, etc.) and displays 104a to e, or data can be exchanged between other physiological monitoring devices and continuous glucose sensor units 100a to c.
[0102] Other examples of exchanged data include: the amount of current or voltage measured by the continuous glucose sensor unit (e.g., raw values), converted glucose values in, for example, mg / dL (e.g., calibrated values or estimated glucose values), and timestamps associated with the time when each measurement or value was sampled, alerts associated with glucose levels exceeding predetermined thresholds, faults detected in the system, firmware versions, hardware versions of the continuous glucose sensor and transmitter, calibration status, times when the sensor was started and / or stopped, battery voltage, encryption information, transmitter identifier numbers, and the like. This data may also be forwarded from a service server, such as a server associated with the manufacturer of the continuous glucose sensor unit. Although described as continuous glucose sensor units 100a-c, other medical devices may be used with the disclosed embodiments. For example, Figure 1 The sensor units depicted as continuous glucose sensor units 100a-c in the figure may be any analyte sensors, and the transmitted data may reflect the analyte values generated by the analyte sensor units. Any data of any type transmitted between the continuous glucose sensor units 100a-c and the displays 104a-e, or between the displays 104a-e and the distributed cloud computing architecture 106, or between any one of the continuous glucose sensor units 100a-c and the displays 104a-e and any other physiological monitoring device or any other system, device or person may be considered as data points.
[0103] The displays 104a to e may be computing devices that include displays, such as visual display screens, auditory displays including speakers, tactile displays, and any other type of display. In some embodiments, for example, the displays 104a to e may be used as dedicated displays for use with the corresponding continuous glucose sensor units 100a to c, where dedicated does not necessarily exclude displaying data from the continuous glucose sensor units. For example, the combination of the continuous glucose sensor unit 100 and the display 104 may be an approved medical device, such as a Class III medical device, in one embodiment.
[0104] The display 104 includes a processor for calculating the glucose level based on the received measurement value, a memory for storing the glucose level, a port for wired communication, and wireless communication circuits such as Bluetooth, Wi-Fi or RF circuits. In an embodiment, for example, the display 104a to c receives data related to the glucose level from the continuous glucose sensor unit 100a to c at predetermined time intervals. In addition, the display 104 can determine whether the user's glucose level has a downward trend, remains stable or increases in historical trends. The display 104a to e presents glucose readings over time so that the user can easily monitor the glucose level, and displays the actual value of the current glucose level.
[0105] Displays 104a to e may also be any type of display associated with a personal computer, tablet computer, or smart phone executing an application for displaying data related to glucose levels. Thus, displays 104a to e include hardware components typically associated with a personal computing device, including a processor, memory, wireless connectivity, USB ports, and other components.
[0106] Displays 104a to e can execute multiple applications related to glucose monitoring, health information, exercise activities, control and monitoring insulin injections, eating habits, and other operations, such as software applications ("apps") that include instructions that can be executed by a processor. In one embodiment, the continuous glucose sensor unit 100a transmits multiple data streams, and the display 104a receives the same data that the continuous glucose sensor unit 100a transmits to the display 104b. The display 104a can be a dedicated display associated with the continuous glucose sensor unit 100a, and the display 104b can be a general computing device, such as a smart phone or the like. The example smart phone can execute one or more applications dedicated to use with the continuous glucose sensor unit 100a, as well as other applications. The dedicated application controls the use of the medical data received from the continuous glucose sensor unit 100a, such as the distribution of data to other applications executed on the smart phone to retain confidentiality and user preferences, as described in more detail below. For example, the dedicated application can also be connected to other third-party applications and provide information to them.
[0107] In some embodiments, displays 104a to e receive and display the entire data set received from the corresponding continuous glucose sensor unit 100a to c. For example, the display 104 displays the actual glucose level associated with the measurement performed by the sensor. The continuous glucose sensor unit 100, the operating system executed on the display 104, or the dedicated application (as described above) executed on the display 104 can limit the third party application to receive and display the actual glucose level. In some embodiments, for example, the third party application can receive a more general indicator of the glucose level instead, such as whether the glucose level is low, normal or high. Additional details about the type of data that can be sent to the display 104 and displayed by it will be provided below.
[0108] The displays 104a to e or the continuous glucose sensor units 100a to c transmit data to a distributed cloud computing architecture 106. The distributed cloud computing architecture 106 organizes, stores, and provides access to data to other computers, applications, and third parties. The distributed cloud computing architecture 106 includes multiple different servers, storage systems, and software applications that execute locally and across a distributed network. Figure 3Diagrams of example embodiments of distributed cloud computing architecture 106 are provided and discussed later in this patent document.
[0109] Communications within the system may be subject to several security protocols. For example, communications may be encrypted and secured, such as HTTPS and SSL communications. The cloud computing architecture 106 may include a firewall that allows only specific and secure communications on defined ports. Additionally, a system including the distributed cloud computing architecture 106 may use an authentication session with a login using a name and password for a web service method that a user or remote monitor (described herein) would use to gain access to read or change their information. The login name and password are stored in a secure form using hashing and encryption, and patient data including all data delivery from the monitor may also be encrypted by the cloud computing architecture 106 and stored in a secure form.
[0110] Another security measure includes the use of authentication sessions that time out after a short period of inactivity and may also have a maximum length. The server may maintain an audit trail or history log of all accesses to the system and all changes made to the system. Additionally, third parties accessing data stored by the cloud computing architecture 106 may need to authenticate themselves and may also be further restricted to access only patients they already know. That is, in some instances, a consumer's privileges may require that they already know the patient's internal identifier with respect to the system, which would have been provided by the patient initiating any exchange of identifying information with the consumer.
[0111] Figure 2 An exemplary method for transmitting and storing data streams separately is illustrated. Assuming that a system according to the disclosed technology can support thousands of continuous glucose sensor units 100 transmitting data to a cloud computing architecture 106, each of which can send data through multiple displays 104, the processing requirements may be too large for the cloud computing architecture 106 to receive a single data stream and separate out the parts that should be assigned to different categories (e.g., public to private). One solution is to separate the data streams before transmitting to the cloud computing architecture 106, thereby allowing the cloud computing architecture 106 to store the data streams separately for fast retrieval. Although this will result in redundant data, it may be preferred because it allows the cloud computing architecture 106 to compare, for example, the public streams received from both the first and second display devices to determine whether the two match. If any differences exist, technical support can determine whether there is a problem with the system operation and provide a solution. For example, calibration errors about displays 104a to e can be detected by comparing the data streams received from individual displays among displays 104a to e.
[0112] Another challenge that may arise is the ability of the servers of the distributed cloud computing architecture 106 to quickly retrieve data. A large amount of data streams may be fed into the cloud computing architecture 106, making fast retrieval a problem. Therefore, it would be advantageous to track the data streams and allow retrieval of data from a given point in time.
[0113] exist Figure 2 In the process 200, a continuous glucose sensor unit (e.g., continuous glucose sensor unit 100a) automatically or in response to a request from either of the two displays provides data to a first display (e.g., display 104a) and a second display (e.g., display 104b). The continuous glucose sensor unit 100a separates the data into two streams: a public data stream and a private data stream. For example, generally, the public data includes information presented to the patient in a chart or report, such as glucose values, monitor / calibration values, time adjustments, patient event inputs (such as meals, carbohydrates, exercise, etc.), when the sensor was started / stopped, which transmitter was used and when, and the like, while the private data generally includes information about the system and the devices that make up the system, such as battery levels, screen duration, error logs, raw sensor signals, proprietary algorithm input / output, memory stack dumps, and the like.
[0114] Public data and private data may include one or both of real-time data and batch data. Batch data may, for example, include data points such as system software version information, diagnostic information, other proprietary data, and stored readings (e.g., glucose levels recorded in time periods such as one hour, two hours, etc.); while real-time data may, for example, include data points such as monitored glucose levels, timestamps associated with monitored values, glucose monitor states, and the like. In general, real-time data is data transmitted by the continuous glucose sensor unit 100 or display 104 at or shortly after its creation (e.g., periodically every minute, five minutes, 10 minutes, etc.), while batch data is data that can be stored on the continuous glucose sensor unit 100 or display 104 for a longer time period (e.g., one hour) than real-time data and transmitted less frequently than real-time data. As described in more detail below, some data (batch or real-time, private or public) may be encrypted, while other data are not encrypted.
[0115] In addition, the display 104 can transmit data at different times. For example, the display 104a to e can send real-time and batch data to the cloud computing architecture 106. In some embodiments, both real-time and batch data can be sent to the cloud computing architecture 106 on a periodic basis, wherein each type of data has a different or identical update period. For example, real-time data can be provided to the cloud computing architecture every five minutes and batch data can be provided every hour. The batch data and real-time data transmitted to the display 104 from the continuous glucose sensor unit 100 can be the same batch data and real-time data transmitted from the display 104 to the cloud computing architecture 106, or it can be different. For example, the batch and real-time data transmitted from the display 104 to the cloud computing architecture 106 can include information about the display 104 or user interaction with the display 104. These are only exemplary update time periods, and the embodiments disclosed herein contemplate any time period.
[0116] At processes 202 and 204, the first display 104a and the second display 104b may individually send their data to a server in the cloud computing architecture 106. The data may include a private header, a private data section, a public header, public content, and / or metadata describing the timing of the delivery and the display making the delivery. The first display 104a and the second display 104b may send the data automatically or in response to a request from the cloud computing architecture 106. The display 104-b may also add additional data to the data received from the continuous glucose monitor 100a before transmission.
[0117] The displays 104a-b may send data to the cloud computing architecture 106 as it is received or after collecting data for a period of time. For example, the continuous glucose monitor 100a may provide batch data to the display 104a every hour, and the display 104a may collect batch data for three hours and then provide it to the cloud computing architecture 106.
[0118] In some embodiments, because multiple displays 104a to b associated with the same continuous glucose monitor 100a provide data, the cloud computing architecture 106 can receive redundant data from multiple sources. However, the data may not actually be redundant because it may be slightly different depending on the time when the data is obtained by the display 104. For example, one display 104a may have been outside the transmission range and therefore receive backfilled data, as described below. Another display 104b may have received data such as scheduled from the continuous glucose monitor 100a. All or some of the data can be stored separately in a data stream on both or either of the displays 104 and the cloud computing architecture 106. This allows an audit trail to determine which data came from which device and when it arrived.
[0119] In addition, different alerts can be set on each display device 104a to b. For example, users may want their phones to provide alerts during the day and their receiver displays to provide alerts at night. For example, when a user misses an alert, technical support can access the data stream associated with a specific display from which the user should have received an alert, and determine whether the display receives data in real time or receives data as backfilled data due to missing one or more transmissions from the continuous glucose sensor unit. If the missed alert arrives when the display misses the transmission, the display will not have data to issue an alert, thereby allowing technical support to diagnose the problem. The backfilled data can be marked by the display in a manner different from real-time data to distinguish it for the cloud computing architecture 106. The mark can appear in the metadata, so the cloud computing architecture 106 does not have to check the data separately to determine whether it is obtained in real time or as backfilled data. Additional examples and descriptions of backfilled data are provided below.
[0120] At process 206, the cloud computing architecture 106 stores data from the first display 104a and the second display 104b separately. Metadata may be used to store the data by providing a timestamp of the time when the data was received or delivered to the cloud computing architecture 106. Thus, the cloud computing architecture 106 tracks the time when the last delivery was received from a particular display device. The delivery may contain new data or data that was previously sent, lost in transmission due to an error or other system failure, and then retransmitted. Metadata allows the display and the cloud computing architecture 106 to track the last attempted message transmission from the display and the message transmission received by the cloud computing architecture 106. One or more servers of the cloud computing architecture 106 do not need to examine the actual data transmitted, but rely on the metadata to effectively store and subsequently retrieve the information.
[0121] When a new data record is created in the system, multiple other computers and services with appropriate permissions or authorizations may be alerted about this data by requesting notifications from the cloud computing infrastructure 106. For example, a remote monitor device that may be operated by a remote monitor user remotely monitoring the glucose status of a user of a continuous glucose sensor unit 100 may receive information about glucose levels by requesting notifications of the glucose levels of a particular patient that the remote monitor device is monitoring through the cloud computing infrastructure 106. Third-party applications may thus obtain public information including glucose levels or other information that they have been provided authorization to receive, while technical support teams may also have access to proprietary private data.
[0122] Figure 3An exemplary embodiment of a system according to a cloud computing architecture 106 is illustrated. There are several challenges associated with receiving and storing large amounts of data. One such challenge is simply the volume of data. Receiving data from displays 104a, 104b on a periodic basis, such as every five minutes, places a large load on the server storing the data. This may be exacerbated by thousands of additional displays associated with other patients that are all transmitting data to the same server. The cloud computing architecture 106 can store long-term data that can be used by third parties, technical support, and other systems, and provide quick access to recent data from a large number of patients. In addition, security issues arise for receiving data and storing the data in a secure form and ensuring that only authorized devices gain access to the data. In addition, some data will be sent through the display, but it may be desirable that the display not be able to access the data. An example is system diagnostic information sent from a transmitter to a server via a phone, which can be used by technical support, but is proprietary and should not be displayed to the user. For example Figure 3 The system of the cloud computing architecture 106 depicted in FIG. 1 may allow different data to be processed in different ways, with different system components having different levels of access.
[0123] exist Figure 3 In the example embodiment shown in , the cloud computing architecture 106 includes a service server 300 and / or a back-end computer architecture 306. Displays 104a and 104b transmit data to the service server 300. The service server 300 provides functions for coordinating storage, retrieval, and notifications related to glucose levels in the system. In one embodiment, displays 104a, 104b use, for example, HTTPS network services to transmit data to the service server 300. The data includes, for example, glucose values, raw data, diagnostic data, and other types of information, such as exercise information or other health-related information. Displays 104a and 104b automatically send data to the service server 300 in some embodiments. The data may include data from the continuous glucose sensor unit 100 and additional data added by the display 104.
[0124] The displays 104a-b may transmit more than one category of data. For example, the displays 104a-b may transmit public and private data, as real-time data (e.g., glucose values, event input information, sensor starts / stops, and associated timestamps) and batch data (e.g., calibration, technical support related information, alert timing related information), as described herein.
[0125] Real-time data may be provided, for example, every five minutes from the continuous glucose sensor unit 100 and / or the display 104. Batch data may be provided, for example, once an hour from the continuous glucose sensor unit 100 and / or the display 104. In some embodiments, batch data includes internal system data, such as system operation data, which will not be provided to any third party generally. Real-time data and batch data points may be different or overlapping. For example, batch data may also include glucose values that are also real-time data values. The data may be sent directly from one display 104 (such as a smart phone) to another type of display 104 (such as a personal computer or other computing device), which uploads the data to the service server 300. For example, in some embodiments, the display 104a may be a smart phone or a dedicated receiver device that receives data from the continuous glucose sensor unit 100a, and the display 104b may be a personal computer, wherein the smart phone or receiver provides data to the personal computer, and the personal computer uploads data via a wired or wireless link. In other embodiments, the display 104a may be a dedicated display device associated with the continuous glucose sensor unit 100a that receives data from the continuous glucose sensor unit 100a, and when it is to provide the data to the service server 300 or via a personal computer, it does so via a cradle communication device ("cradle"). For example, the dedicated display device may be placed in a cradle to connect the two devices. The cradle may include a network connection for uploading data to the service server 300. In another embodiment, the display 104b is a smart phone and it uses an application to upload data. Real-time and batch data can be synchronized with the service server 300 in different ways (e.g., at different time intervals) to facilitate separate storage and retrieval of real-time and batch data by the cloud computing architecture 106.
[0126] In one embodiment, the transmitter 102 in the continuous glucose monitor 100 can separate batch data and real-time data. The transmitter 102 can encrypt all or part of the batch data using a key stored on the transmitter 100 and pass it to the service server 300 through the associated display 104. In some embodiments, the display 104 does not have a decryption key for the encrypted batch data, and therefore only acts as a passage for the encrypted batch data, but the shared service server 300 and the back end 306 may include a decryption key for the encrypted batch data. The transmitter 102 can also encrypt all or part of the real-time data using, for example, Bluetooth encryption or other technology, and the display 104 can receive the real-time data, decrypt some or all of it for use and display, and forward the real-time data to the shared service server 300 for storage.
[0127] The service server 300 stores the data for a predetermined amount of time, such as thirty days, and synchronizes the data to other devices, applications, and external companies as well as the backend computer 306. The service server 300 and the backend computer 306 may employ different levels of security for different types of data. Figure 3 In the example embodiment shown in , the service server 300 includes a shared service server 304 and a data synchronization server 302. The shared service server 304 stores real-time data and batch data separately. For example, the display can send data individually or collectively, and the data can be separated into real-time and batch data by the continuous glucose sensor unit 100, the display 104 or the service server 300. In one embodiment, the shared service server 304 stores data for only a predetermined amount of time. For example, this allows for fast search and access to shared data, and also limits the amount of data stored on the shared service server 304. In some embodiments, the shared service server 304 only stores data for the past 30 days, thereby allowing the storage of data to be as long as other devices will need to retrieve data. In other embodiments, the shared service server 300 can store data for a time period greater than or less than 30 days.
[0128] The service server 300 supports collecting data delivery on a patient-by-patient and stream-by-stream basis. Clients such as the patient's display 104, devices associated with other services 318, remote monitor devices, or other system components can then request data by asking for a specific range of data for each patient. The data range can be based on the time when the data is delivered to the server. In some embodiments, each data transmission of the display can be assigned to a delivery identifier. A request can be made to obtain all data deliveries that come after the delivery identifier, which can also be tracked by the client.
[0129] In some embodiments, a system according to an embodiment of the cloud computing architecture 106 maintains a separate record "stream" of delivery information for each patient's source display 104, such as a smart phone and / or receiver dedicated to use with the continuous glucose sensor unit 100. Each delivery can identify the source type by indicating which display delivered the data. This will result in duplicate delivery of patient data from multiple sources. In some embodiments, the service server 300 stores these streams of data delivery separately to reduce the complexity of delivery to the display device by allowing the display device to create incremental delivery only relative to its own self-contained connected data. The consumer can then maintain or report the differences between the streams, or can combine the content of the streams as needed / required.
[0130] The example of other devices that will access the most recent data by the shared service server 304 includes a remote monitor 322 that receives data in real time. The remote monitor 322 is a person who monitors the glucose level of another patient. The remote monitor 322 can use a display 316 (such as a smart phone, tablet computer, personal computer, etc.) that can communicate with the service server 300 to monitor the glucose state of the patient. For example, the remote monitor 322 can be a parent or guardian who accesses and monitors the glucose level of his child using a display 316a and / or 316b that can be operated by the remote monitor 322. In some embodiments, the patient's display 104a transmits glucose data to the shared service server 304, and it stores glucose data for a time period, such as up to thirty days. The display 316a of the remote monitor 322 requests and obtains permission to access the glucose data of a specific patient, and requests glucose data to the shared service server 304.
[0131] One challenge that may arise with respect to the remote monitor 322 is that storing any identifying information of the remote monitor may place those interactions under government privacy laws and regulations, such as HIPPA regulations based on the Health Insurance Portability and Accountability Act (HIPPA) in the United States or other similar laws or regulations in other countries. It would be preferred to avoid storing non-patient (i.e., remote monitor 322) information in the cloud computing architecture 106 to avoid involving any privacy laws or regulations. Therefore, in some embodiments, the cloud computing architecture 106 does not receive or store any of the personal information of the remote monitor. Instead, the remote monitor 322 may be assigned a digital signature or other secure anonymous identifier 308 associated with the remote monitor 322, but the relationship is not stored in the cloud computing architecture 106. For example, the registration process for the remote monitor 322 may result in the generation of a unique number that is an anonymous identification of the remote monitor user. Communications within the system (e.g., between the shared service server 304 and the display device 316a of the remote monitor) according to an embodiment of the cloud computing architecture 106 use the anonymous identifier 308 rather than information that would identify the remote monitor 322.
[0132] In some embodiments, the cloud computing architecture 106 includes a backend computer architecture 306, such as one or more servers in communication with the service server 300. The backend server 306 can receive real-time data from the shared service server 304 and batch data from the data synchronization server 302. In some embodiments, the backend server 306 stores historical data older than thirty days and receives requests for access to data older than thirty days through other service devices 318.
[0133] The back-end server 306 can serve as a data warehouse, which can store data permanently or in a long time period for archiving purposes. In some embodiments, for example, the technical support unit 314 provides automatic technical support for users and patients for any problems of system operation. The technical support unit 314 receives glucose data and other real-time and batch data, and can permanently store the data to assist future technical support issues. For example, the patient sets up an alert on the display 104a, 104b for when the glucose level crosses a defined level or experiences a defined rate of change. When the alert fails to be delivered on the display 104 and the patient thus misses the alert, the patient can call the technical support service center 324 to determine why the alert is not issued. Similarly, for example, the patient may have the problem automatically solved and / or resolved by the technical support unit 314 of the back-end server 306. In this regard, when solving and / or resolving the problem via the technical support unit 314, the technical support service center 324 can only provide human interaction for the patient. The technical support unit 314 can determine why the patient did not receive the alert. In one example, the display 104a may have missed data because it was outside the wireless range of the continuous glucose sensor unit 100, so the display 104a does not have the data that should have issued an alert. In these cases, however, the data may have been subsequently backfilled into the display 104a, as described in more detail below, so the patient viewing the display 104a believes that the display 104a has obtained the data at the correct time.
[0134] The backend server 306 (e.g., including the technical support unit 314) stores an indication of whether the data was received by each display 104a, 104b in real time or as part of a backfill process. By determining that the data in the display 104a is backfilled, the technical support unit 314 can notify the patient that their device did not get data at the relevant time when an alarm should have been issued. Similarly, for example, a technical support service in communication with the technical support unit 314 of the backend server 306 can notify the patient that their device did not get data at the relevant time when an alarm should have been issued. Figure 3 The cloud computing architecture of thus differentiates data based on whether the data is received in real time by a particular device, such as display 104a, display 104b, service server 300, and others, or as part of a backfill process.
[0135] exist Figure 3 In the embodiment shown in , the backend server 306 also includes a product monitoring server 310, which monitors the use of the product, issues updates to the continuous glucose sensor unit, and updates the software on the display and other system devices. As an example, the product monitoring server 310 can determine when the sensor associated with the patient's continuous glucose sensor unit 100 should be replaced, and automatically send an email to the patient as a reminder to order a new sensor.
[0136] exist Figure 3 In the embodiment shown in , the backend server 306 also includes a single sign-on server 312. The single sign-on server 312 provides a single sign-on for patients and users who access several different applications and systems. For example, if the system includes separate systems, applications, and components, the user experience may not be seamless because the user will need to log in to separate systems. In an illustrative example, the display 104 can execute an application for monitoring continuous glucose levels and an application for controlling insulin injection. The application for controlling insulin injection requests glucose information, and therefore may require two or even three separate logins: one for the application for monitoring glucose levels, one for the application for controlling insulin injection, and one for accessing glucose levels through the insulin injection application. This may be cumbersome for the user. An example solution to the challenge according to the disclosed technology is to allow the application for monitoring glucose levels to open other applications in a web view, thereby allowing the use of a single sign-on so that the user enters the login information once and does not need to re-enter the information when the user is directed to other modules of the system. For example, icons may be provided within the continuous glucose monitoring application for other applications, such as an application for viewing a report with more detailed statistics about glucose levels. When the user selects the icon, the application launches a web view. In this example, the web view request may bypass the shared services server 300 to provide the user with a virtually seamless experience of accessing other services by directly accessing the server hosting the second application.
[0137] Thus, smart phones and other displays can log into the system through the cloud infrastructure using the single sign-on server 312. For example, a transmitter identifier can be printed on the continuous glucose sensor unit 100 and used as a login to associate a specific transmitter with a specific patient. Additionally or alternatively, for example, a user can have a login name and password, and a variety of different encryption algorithms can be used in the authentication process.
[0138] Other services 318 may include several other services seeking access to patient data. In some embodiments, other services 318 include computer-based data services, such as databases, data management programs, and / or portals that interface with users or computers that access data. As an example, a doctor 320 using a computing device such as a personal computer, smart phone, tablet computer, etc. may request access to patient data stored by the service server 300 through other services 318. For example, a doctor may request recent and past glucose levels to analyze whether the insulin injection dose should be changed, and track the patient's progress between doctor visits. In one embodiment, other services 318 receive real-time data for a time period (e.g., the past thirty days) through the service server 300. Other services 318 can synchronize data and periodically save data through the service server 300. For example, some other applications may request data every hour, other applications may request data every day, and other applications may request data every week to obtain data from the service server 300. For example, other services 318 may include applications that request data for individual patients and for multiple types of patients to perform data analysis. When other services 318 request data that exceeds the chronological range stored by service server 300, the request is sent to and processed by backend server 306, which stores batch and real-time data for longer-term archives. The timing of when various components of the system can request access to batch and real-time data can vary. For example, cloud computing architecture 106 can limit other services 318 to accessing data only once a day, allow full access at any time, or a variety of other time ranges.
[0139] Will understand, Figure 3 Other embodiments of the cloud computing architecture 106 may include fewer or additional components. Additionally, a system according to an embodiment of the cloud computing architecture 106 may include multiple cloud computing architectures such that less than all displays transmit data to a single cloud computing architecture. For example, multiple connected cloud computing architectures may be used throughout different geographic regions, but other arrangements for distributing computing loads are also possible.
[0140] We will now turn to reference Figure 4, which illustrates a method for storing data in separate groups. In some embodiments, the continuous glucose sensor unit 100 and the display 104 may generate and transmit different types of data (e.g., real-time and batch data, private and public data) that may need to be handled in different ways. In particular, all data may not be suitable for retransmission to a third party or other system components, such as data containing proprietary information about the operation of the system and data that can be used to identify the patient. Separating the data so that the data can be handled in different ways brings challenges, including different storage locations, different strategies for controlling access to the data, and different storage durations. The data may include data related to glucose levels, data about the function of the system, user interaction with the system, and other types of data.
[0141] At process 400, the continuous glucose sensor unit 100 prepares data including glucose levels and other data for transmission. The data includes, for example, measured glucose values and diagnostic data. The data may include a first data set (e.g., real-time data) and a second data set (e.g., batch data). Real-time data may include one or more of the following: glucose value, the current state of the continuous glucose sensor, a time stamp associated with the measurement used to obtain the glucose value, and similar data. Batch data may include one or more of the following: information for calibrating the continuous glucose sensor unit 100, information for technical support of the continuous glucose sensor unit 100, and similar data. For example, the information for calibrating the continuous glucose sensor unit 100 may include the previously discussed values sampled by the patient when using the test kit. In some embodiments, the electronics unit (e.g., transmitter 102) of the continuous glucose sensor unit 100 prepares data by aggregating and / or formatting the data into a form or group to be transmitted. For example, as described in more detail below, the continuous glucose sensor unit 100 may encrypt some or all of the data. In some embodiments, data is prepared in a manner corresponding to a data set, such as real-time data and batch data, which may be prepared in different manners for different data sets.
[0142] At process 402, the continuous glucose sensor unit 100 transmits glucose data and other data to one or more displays 104, some of which may be encrypted. In some of the embodiments, each of the displays 104 may store a decryption key to decrypt some (but not all) of the encrypted data to control patient access to certain types of data. For example, the display 104 may decrypt real-time data including glucose levels, from which the display 104 may generate and display a graph of current and past glucose levels over a time period (e.g., the last hour, six hours, or day). In some of the embodiments, the display 104 does not have a key to decrypt bulk data such as system diagnostic information and / or raw data values in order to keep the data confidential.
[0143] At process 404, one or more displays 104 forward the data to a cloud computing architecture 106, also referred to as a cloud computing infrastructure or cloud infrastructure. In some embodiments, process 404 may occur automatically, for example, upon receipt of the data or at a predetermined time, without a request from a user. The display may send different types of data to the cloud computing architecture 106 at different times. Additionally, the display 104 may add more data to the data received from the continuous glucose sensor unit 100 and automatically forward the additional data to the cloud computing architecture 106. This additional data may include, for example, the time of the alarm, the time to view the data on the display, data further processed by the display 104, and the like.
[0144] At process 406, the cloud computing architecture 106 stores the data in separate groups. In some embodiments, for example, the shared service server 304 may store real-time data, and the back-end server 306 may store batch data. Various components of the cloud computing architecture 106 may store decryption keys for both sets of data to restrict access to certain data types. For example, the back-end server 306 may store decryption keys for both real-time and batch data, so technical support (e.g., technical support unit 314) can access both types of data. However, other services 318 may not store decryption keys for batch data, so that the batch data cannot be accessed through other services 318. Therefore, the cloud computing architecture 106 selectively determines whether to grant access to various data categories (e.g., the first set and the second set) by the data category and one or more requesting systems attempting to access the data. For example, in some embodiments, the cloud computing architecture 106 may include a table that identifies the requesting system. Requests for data received by the cloud computing architecture 106 may identify the system making the request so that the requesting system can only access certain types of data.
[0145] We will now turn to reference Figure 5 and6 , which illustrate example embodiments of an encryption system and a method for encrypting data, respectively. Figure 5 and 6 Techniques are provided to protect sensitive data from unauthorized access by third parties. A challenge in this technology is the ability to distribute data to entities that are only authorized to receive a subset of the data. For example, cloud computing architecture 106 may grant service access to data that does not identify a patient, but deny service access to patient identifying data or system diagnostic data. At the same time, cloud computing architecture 106 may allow other entities, such as technical support, full access to system diagnostic data but not always access to patient identifying data. Various levels of security and authorization may be used, for example, Figure 4 and 5 Technologies such as those in are used to control system components' access to data.
[0146] Conceptually, Figure 5 The system places the message inside a box that is locked at the transmitter 102. Only the intended recipient, such as the service server 300 and / or the backend server 306, has the key. In some embodiments, the transmitter 102 sends the message to a display 104, such as a smart phone or a dedicated receiver, which sends the encrypted message on to the service server 300. The display 104 acts as a pass-through without the ability to decrypt all the data.
[0147] In particular, the transmitter 102a includes a memory 500, which may be any type of non-volatile memory that can store a public key 506, a secret key 504, and private data 502. The public key 506 is a public encryption key, such as a key used for RSA1024 encryption. The secret key 504 is an additional private key used for another level of encryption, such as the Advanced Encryption Standard. The private data 502 may include, for example, the batch data previously described. The secret key 504 may be stored on the transmitter 102a during the manufacturing process.
[0148] The transmitter 102a sends the secret key 504 surrounded by the public key 506 to each of the displays 104a, 104b, as illustrated at 508, and also sends the protected data surrounded by the secret key 504, as illustrated at 510. The displays 104a, 104b do not have the public key 506, so they cannot access the secret key 504 or use the secret key 504 to access the private data 502. Instead, the private data 502 includes data that is transmitted to the service server 300 for decryption by the displays 104a, 104b. In this way, the displays 104a, 104b are restricted from accessing certain private data, while the cloud computing architecture 106 can access the data. In particular, the backend 306 stores the private key, as shown at 514.
[0149] Although not shown, and as described below, the transmitter 102 also transmits other data that the displays 104a, 104b can decrypt and display to the user. This data includes, for example, real-time data, and can be encrypted according to Bluetooth encryption schemes and other technologies. The display 104b can be connected to a PC uploader program 512, which can be executed on a personal computer, tablet computer, or other computing device.
[0150] refer to Figure 6 , corresponding methods for encrypting and transmitting data, such as may be implemented by devices and cloud computing system architectures according to the present technology, will be described. At process 600, the transmitter 102 encrypts a first data set. For example, the transmitter 102 encrypts real-time data including glucose values using Bluetooth encryption. At process 602, the transmitter 102 encrypts a second data set, such as batch data including proprietary information that should not be accessible to the display 104. The second data set may be encrypted using the Advanced Encryption Standard and a variety of other techniques.
[0151] The transmitter 102 transmits the first and second data sets to the display 104 at process 604. The transmitter 102 sends the first and second data sets together or at different times. For example, the first real-time data set may be sent every five minutes, while the batch data may be sent every hour. In this way, the transmitter 102 sends the two data sets to the display 104 as different data streams, each data set encrypted using a different technique.
[0152] At process 606, the display 104 decrypts the first data set. The display 104 presents the data to the user on a user interface, uploads the data to the cloud computing architecture 106, provides the data to other applications, and stores the data in local memory. The display 104 may forward the first and second data sets to the cloud computing architecture 106 at process 608. Process 608 occurs automatically when the data is received, periodically, or in response to a request from a user or the cloud computing architecture 106. In some embodiments, each of the displays receives the first and second data sets in different streams at different times, and automatically forwards the streams to the cloud computing architecture 106 when received. In this way, the cloud computing architecture 106 receives the first and second data sets, each encrypted in a different manner, at different times.
[0153] At process 610, the second data set is decrypted. In one embodiment, the second data set or a portion thereof may be decrypted by the cloud computing architecture 106. In another embodiment, the second data set (or a portion thereof) may be sent to another location, such as an insulin provider having a key and being able to decrypt the second data set. Although the display 104 lacks the decryption key for accessing the second data set, the cloud computing architecture 106 (e.g., in the shared services server 300 and / or the back-end server 306) and / or other locations (e.g., insulin providers) include the decryption key. In some embodiments, the cloud computing architecture 106 receives and decrypts the first data set, and provides it to the local short-term storage device in the cloud service server and the longer-term storage device in the back end.
[0154] We will now turn to reference Figure 7 , which illustrates an exemplary method for providing a common interface through which data can be accessed. The cloud computing architecture 106 may provide an integrated system with many different components, including third-party systems. However, in some instances, this may be problematic from a regulatory perspective because the entire system may need to undergo regulatory review each time a change is made to any one component. To address this issue, for example, the cloud computing architecture 106 may be configured so that each module may be considered independent from a regulatory perspective, so that each module may undergo a separate regulatory review. In particular, the cloud computing architecture 106 may provide a set of standard application programming interfaces to provide a known format for interfacing, thereby allowing the various components to be built and maintained separately.
[0155] Another challenge facing the cloud computing architecture 106 is how to handle the large number of requests to access data of different patients. For example, requests may originate from several different servers, computing devices, and software applications, which may have different formats of requests and capabilities for receiving and processing responses. If the cloud computing architecture system 106 were to change to accommodate each new request and response type, the system would likely need to be recertified as a medical device, which can be a time-consuming and expensive process. Figure 7 The method thus provides a common interface through which requests will be received, thereby ensuring a modular system that does not require changes to new request types.
[0156] In one example, the cloud computing architecture 106 employs a hub and spoke framework, where the hub contains rules about what information each specific spoke can access. In this way, the spokes only have access to information that is appropriate and / or required by the spoke. Examples of spokes include remote monitoring applications, third-party applications, and other services.
[0157] At process 700, the cloud computing architecture 106 defines rules for controlling access to data. The rules may include user permissions, an approval process for remote monitors, an approval process for third parties and other software applications, and rules for controlling access from components of the cloud computing architecture 106 itself. For example, a remote monitor does not need to have access to proprietary bulk data, but technical support can access bulk data. Other examples of rules include controlling the amount of data that can be accessed, controlling the timing of when data can be accessed, and other rules. These rules can be implemented when the system is put in place for the user, or, for example, by an administrator who has permissions and authorizations to set such rules in the cloud computing architecture 106. These permissions and authorizations may have to comply with privacy laws and regulations.
[0158] At process 702, the cloud computing architecture 106 provides a set of application program interfaces for accessing data. The application program interfaces define standardized interfaces through which requests for data can be received. The standardized interfaces are provided to third parties and application developers to generate requests that comply with the application program interfaces. At process 704, a computing device or application provides a request to the cloud computing architecture 106 through one of the application program interfaces.
[0159] Next, at process 706, the cloud computing architecture determines whether to grant the request for access to the data based on the rules defined in process 700. For example, the cloud computing architecture 106 identifies the requestor and determines whether the requestor should obtain access to the requested data. If the cloud computing architecture determines at process 706 that the requestor does not have access to the requested data, then the cloud computing architecture 106 denies the request at process 708. If the cloud computing architecture 106 determines at process 706 that the requestor does have access to the requested data, then the cloud computing architecture 106 grants the request at process 710. Processes 704 to 710 may be performed by several different components within the cloud computing architecture. For example, requests for recent data may flow through the service server 300, while requests for older archived data may be processed by the back-end server 306.
[0160] Figure 8 and 9A 9D illustrate an exemplary method and system diagram for handling requests from a computing device such as display 104 to a cloud computing architecture 106 according to an embodiment of the disclosed technology. As discussed above, handling requests from a number of different servers and applications can present challenges to the cloud computing architecture 106. One solution is to provide a common application program interface at the cloud computing architecture 106, such as Figure 7 Another solution includes using an application (app) executing on the display 104 to make the request in a common format. Figure 8and 9 provide examples of making requests in a common format using an application executing on display 104.
[0161] See also Figure 8 , the display 104 includes a continuous glucose monitor application 800 and a plurality of other applications 802a, 802b. The continuous glucose monitor (CGM) application 800 may be an application designed to interface with both the transmitter 102 of the continuous glucose sensor unit 100 and the cloud computing architecture 106. The applications 802a, 802b provide data requests 804 to the CGM application 800, which may include the information described above with respect to Figure 7 The rule logic is described to determine whether a data request should be granted to the requesting application 802a, 802b.
[0162] If the request should be granted and the data is stored locally, the CGM application 800 provides a data response as shown at 810. In some embodiments, the CGM application 800 forwards the data request 806 to the cloud computing infrastructure 106, which uses Figure 7 802a or 802b.
[0163] Fig. 9A An exemplary embodiment of a user interface of a CGM application 800 executing on the display 104 is illustrated. The CGM application 800 displays information related to glucose levels at 904, including a graph of recent glucose levels, current glucose levels (e.g., 86 mg / dL, and trend patterns (e.g., rising, stable, or falling). In some embodiments, the CGM application 800 displays icons 900, 902 as links to other applications, such as Figure 8 In this example, icon 900 links to the exercise application, and icon 902 links to the insulin application. These links within the CGM application 800 allow the user to log into multiple applications using a single login, as described above with respect to Figure 3 In addition, the link can provide a convenient way for the user to access other information stored by different applications (whether from the same or different manufacturers) related to glucose levels and trends.
[0164] Fig. 9B An exemplary embodiment of a system according to a cloud server architecture 106 for performing aspects of the described techniques is illustrated. In this illustration, the display 104a includes a computer program that performs, for example, Figure 8 The display 104a may be a smart phone with an application such as the CGM application 800 described above. In other examples, the display 104a may be a computing device such as a laptop computer, a desktop computer, a tablet computer, a PDA, a wearable computing device, and the like. For example, the display 104a communicates with the continuous glucose sensor unit 100. The display 104a may communicate wirelessly with the continuous glucose sensor unit 100, or it may be connected to the continuous glucose sensor unit 100 via a wired or optical cable.
[0165] The display 104a can receive multiple types of data from the continuous glucose sensor unit 100 and transmit the multiple types of data to the cloud server architecture 910, which is an example embodiment of the cloud computing architecture 106. The data transmitted from the display 104a to the cloud server architecture 910 can be transmitted at different time periods based on the category assigned to the data. The data can be classified into real-time data and batch data. Real-time data can be transmitted from the display 104a to the cloud server architecture 910 at a higher frequency, such as once every minute, once every five minutes, once every 10 minutes, etc., while batch data can be transmitted from the display 104a to the cloud server architecture 910 at a relatively lower frequency than real-time data, such as once every 30 minutes, once every hour, once every two hours, etc.
[0166] For real-time information, the data transmitted from the continuous glucose sensor unit 100 is received by the display 104a and transmitted to the real-time server 908 included as part of the cloud server architecture 910. Real-time information includes one or more of the following: estimated glucose value (EGV), glucose concentration rate of change information, CGM warning information, raw sensor data, and / or other types of public or private data discussed herein. Real-time data is separated from batch data because it may be necessary to take action based on real-time data in an immediate or timely manner. In addition, real-time server 908 is configured to handle a large amount of real-time data based on a fast basis. For example, a glucose monitoring system may have up to 150,000 or more users, and each user may transmit up to 288 values per day from the display 104a of the corresponding user to the real-time server 908.
[0167] Due to the volume and frequency of data that the real-time server 908 must manage, a locator service may be used in some instances. Fig. 9CThe data and control flow associated with an exemplary locator service are shown in . At the beginning of an application session, a client application such as the CGM application 800 described above, executed on a smart phone, calls a locator service (e.g., running on a real-time server 908) and receives a URL that it uses for subsequent calls. The input parameters typically include the application name, application version, and country code. The locator service uses the parameters to determine where to go for all other services (hence the term "locator"). This approach provides the real-time server 908 with the ability to scale out without changing the application; and the ability of the server to provide different service implementations for different application versions or countries. Existing applications that do not use the locator service continue to work. The locator service contains logic to determine where to send application requests in a dynamic manner.
[0168] Reference again Fig. 9B Various mechanisms may be used to transmit information from the real-time server 908 to the remote monitor 316b. The remote monitor 316b may be a device such as a smart phone executing an application (app), such as a device designed to display information to the remote monitor user related to the real-time server 908. Figure 8800 of the CGM application program 800 described herein. For example, in one example, at least a portion (if not all) of the real-time information is pushed to one or more remote monitors 316b from the real-time server 908. The real-time information can be delivered to the remote monitor 316b based on a periodic basis, such as once every 30 seconds, once every minute, once every two minutes, once every five minutes, once every 10 minutes, etc. In some embodiments, the real-time server 908 can monitor the real-time information of trends and tendencies, and make the remote monitor 316b aware of these trends. When data is pushed to the remote monitor 316b, the remote monitoring application on the device 316b may need to be opened and run. If the remote monitoring application is not opened and run on the remote monitor 316b, the data is queued at the real-time server 908. In some embodiments, once the remote monitoring application is opened on the remote monitor 316b, the data is automatically pushed to the remote monitor 316b. In some embodiments, once the remote monitoring application is opened on the remote monitor 316b, the user is notified to wait for data. Using the remote monitoring application, for example, the remote monitor user can then request that data be transmitted from the real-time server 908 to the remote monitor 316b. In some embodiments, if the remote monitoring application is not open and running on the remote monitor 316b, a notification such as a text message (e.g., SMS or MMS) is sent from the real-time server 908 to the remote monitor 316b, because the remote monitor 316b will not have real-time data readily available to trigger an alert on its own when the remote monitoring application is closed (e.g., in the background on an iPhone).
[0169] In some implementations, real-time server 908 interfaces with the remote monitoring application on remote monitor 316 b and wakes up the remote monitoring application. Once the remote monitoring application wakes up, it requests data from real-time server 908.
[0170] The remote monitor 316b is allowed to access to receive certain information from the real-time server 908. This is information related only to the defined one or more continuous glucose sensor units 100 and their corresponding displays 104 (e.g., operating the CGM application 800). The remote monitor 316b is not allowed to access unauthorized data. In some embodiments, the remote monitor 316b may send a request to the real-time server 908, and the data associated with at least one of the one or more continuous glucose sensor units 100 and the corresponding display 104 that the remote monitor 316b is allowed to read will be delivered to the remote monitor 316b after the request. In some embodiments, the remote monitor 316b may be a smart phone. In some embodiments, the real-time server 908 may include a Class II device as defined by the U.S. Food and Drug Administration (FDA), and the data is processed according to the category.
[0171] In some embodiments, the cloud server architecture 910 further includes a batch data collector (BDC) 912 and a batch data distributor (BDD) 914. In some embodiments, the BDC 912 and the BDD 914 are data processing engines operating on one or more computers (e.g., servers) that communicate with each other. In some embodiments, the display 104a sends batch data (as described herein) to the BDC 912 based on an intermittent basis. For example, the display 104a can send batch data from the display 104a to the BDC 912 once every hour. In some embodiments, the batch data is uploaded to a computer 916, such as a personal computer, from the continuous glucose sensor unit 100. At least a portion of the batch data is then transmitted from the computer 916 to the BDC 912. Similar to the above, data can be transmitted from the computer 916 to the BDC 912 on a periodic basis. For example, data can be transmitted from the computer 916 to the BDC 912 once every hour. The data transmitted to the BDC 912 may include private and public data (as described herein). In some implementations, BDC 912 may comprise a Class II device as defined by the U.S. Food and Drug Administration (FDA), and handle data according to that classification.
[0172] As described, the cloud server architecture 910 also includes a BDD 914. The BDD 914 provides fan-out capabilities for data received from the BDC 912. For example, at least a portion of the data from the BDC 912 can be provided to one or more of the technical support tool 922 and the long-term data warehouse 918. The data stored in the warehouse may include public and private data. The technical support tool 922 may include, for example, a shared support tool, a repository tool, and a transmitter tool. The shared support tool (a tool that provides technical support-related insights for the display 104a and the remote monitor 316b) includes the ability to present data tables and data charts sent from the display 104a (automatically) and the continuous glucose sensor unit 100 (according to user requirements). In some embodiments, the data table can present all data sent from the display 104a and the continuous glucose sensor unit 100 to the data server (real-time server 908 or batch data collector 912), classified by data type (e.g., EGV data, log, etc.) and by the data source (display 104a or continuous glucose sensor unit 100). In some embodiments, the data chart presents the data from the table in a visual form in a chronological order. The data source can be identified in the chart. The repository tool supports data visualization of the display 104a and the continuous glucose sensor unit 100 data as data tables and charts. The repository tool includes support for visualization of continuous glucose sensor unit 100 data. For example, when a user returns a receiver for investigation, this tool can be used to download the receiver to further investigate the complaint internally.
[0173] At least a portion of the data from BDD 914 may be provided to repository 920 for analysis and / or reporting. This information is generally referred to as traceability data. Traceability data may generally be defined as batch data and any real-time data generated in the past. For example, real-time data that was not generated within the last five minutes may be considered traceability data. In some embodiments, BDD 914 may include a Class II device as defined by the FDA, and the data is processed according to that class.
[0174] Generally speaking, control Fig. 9B For example, using the authorization manager ( Fig. 9B914, the traceability data 920, and the data warehouse 918. In some embodiments, the authorization manager may be token-based. Access to certain data may be allowed or restricted based on a token held by the accessing third party. Optionally or alternatively, the patient may provide a third party with access to the information of the particular patient. For example, an adult patient may provide a remote monitor 316b. Based on a response from a third party, a token may be customized for the authorization of the third party. In some embodiments, a third party may access certain information (e.g., data of a certain patient) using, for example, a login through a social media website (e.g., Google, Facebook, Twitter, etc.).
[0175] Fig.9D 9002 is a flowchart illustrating a method for safely collecting, analyzing and reporting data related to glucose monitoring levels by multiple continuous glucose monitors. At process 9002, data is received from multiple continuous glucose monitors (CGM) (e.g., continuous glucose sensor unit 100) by multiple display devices (e.g., display 104). At process 9004, data is classified into multiple categories based on data type. In some embodiments, data is classified into multiple categories based on data type including data is classified into real-time data and batch data. In some embodiments, display 104 classifies received data into multiple categories based on data type, and in other embodiments, continuous glucose sensor unit 100 implements process 9004 before process 9002 to classify data into multiple categories based on data type. In these embodiments, continuous glucose sensor unit 100 can only classify some data, wherein display 104 can classify received unclassified data and / or reclassify received classified data.
[0176] At process 9006, the classified data is transmitted from multiple display devices to a cloud server architecture according to the present technology, such as cloud server architecture 106. Cloud server architecture 106 includes at least multiple servers that receive data from multiple display devices on an intermittent basis, such as a system according to cloud server architecture 910. The multiple servers of the cloud server architecture may include at least a real-time server and a batch data collector, such as real-time server 908 and BCC 912, respectively. In some embodiments, the cloud server architecture may further include a locator service, wherein multiple display devices are connected to the cloud server architecture through the locator service. The data routed to a specific server in the multiple servers is determined by the data type, and the intermittent basis or transmission from the display device to the server may vary depending on the data type. For example, real-time data is routed from multiple display devices to a real-time server, and batch data is routed from multiple display devices to a batch data collector. The intermittent basis on which real-time data can be routed from multiple display devices to a real-time server is more frequent than the intermittent basis on which batch data can be routed from multiple display devices to a batch data collector. For example, real-time data may be routed from the plurality of display devices to a real-time server once every five minutes, and batch data may be routed from the plurality of display devices to a batch data collector once an hour.
[0177] At process 9008, data is received from one of the multiple servers (e.g., real-time server 908) by multiple remote monitor display devices (e.g., remote monitor 316b). The data sent to each of the multiple remote monitor display devices may depend on the data type and the display device that transmits the data to the one of the multiple servers. In some embodiments of process 9008, the data is sent to the multiple remote monitor display devices immediately after being received by the one of the multiple servers of the cloud server architecture. And in some embodiments of process 9008, the cloud server architecture (e.g., real-time server 908) processes the data according to the rules associated with each remote monitor 316, and sends the data to the corresponding remote monitor device according to the rules. At process 9010, at least a portion of the data received by the multiple servers is routed to the analysis and reporting engine. In some embodiments of process 9010, the BDD 914 of the cloud server architecture provides at least a portion of the data to one or more of the technical support tool 922, the data warehouse 918, and / or the repository 920. The data is analyzed by the analysis and reporting engine and a report is generated.
[0178] Backfill
[0179] Fig.10An exemplary method for backfilling data is illustrated. One challenge that can occur when providing data to multiple displays and a distributed cloud computing architecture is ensuring that each application or device contains the latest data. For example, a user may turn off an application, such as CGM application 800, so that an application executing on a display device (e.g., display 104) will not receive data. Alternatively, the display may be turned off. Even if the display is on and receiving data, it may be turned off or disconnected from the network when data is normally forwarded to the cloud computing architecture. If an application or device does not receive data, it will not be up to date. Fig.10 and 11 An exemplary method is described that allows data to be backfilled into an application to bring the application up to date. Up to date can mean that the application or server has all data available to it.
[0180] Additional challenges arise with regard to the use of multiple data streams throughout the system as described herein. For example, real-time and batch data streams may be sent separately by the continuous glucose sensor unit 100 to multiple displays 104, which forward those data streams on to the cloud computing architecture 106. The cloud computing architecture 106 may receive and separately store multiple copies of the data streams from different displays connected to a common continuous glucose monitor. For example, depending on which display forwards the data to the cloud computing architecture 106, there may also be some differences in the data streams due to different calibration values and the ability of the display to add its own additional data to the data stream.
[0181] Another challenge arises as the user is able to distinguish whether data is obtained when it is scheduled to be received ("scheduled data") or obtained as part of a backfill process. Thus, the user interface may display the data differently depending on whether the data is obtained in a scheduled or backfilled manner. For example, the backfilled data may be displayed differently. In one non-limiting example, Fig. 12B As shown in , the backfilled data can be shown by using a dashed line 1204 on the line indicating the glucose level. Another way to show that the backfilled data is different from the scheduled data is to use different color line segments for the backfilled data and the scheduled data. Fig. 12A and 12B In some embodiments, the display 104 may have an orientation sensor, such as available in a smartphone, such that when in portrait view 1200, the backfilled data points are displayed identically to the real-time data points, but when the display is oriented in landscape mode 1202, the backfilled data may be displayed differently. For example, a summary or condensed version of the data may be displayed in portrait view 1200, but when oriented in landscape mode 1202, additional detail may be displayed.
[0182] Return to Fig.10, at process 1000, a continuous glucose monitor (e.g., continuous glucose sensor unit 100) transmits data. The data may include real-time and batch data, which may be encrypted as previously described. The glucose values may be time-stamped to track when the continuous glucose monitor sampled the glucose level, and to facilitate checking to ensure that the various system components contain a complete data set with all glucose samples.
[0183] In some embodiments, the continuous glucose monitor transmits data periodically, such as every five minutes, thereby allowing the monitor and associated transmitter to be placed in a low power state to save battery life. In other embodiments, the continuous glucose monitor transmits data at intervals other than five minutes. Real-time and batch data can be transmitted every cycle, or real-time data can be transmitted every five minutes, while batch data is transmitted less frequently, such as every hour.
[0184] Next, at process 1002, a display device (e.g., display 104) in communication with the continuous glucose monitor distributes the received data, which may include both real-time and batch data. The display distributes the data to the cloud computing infrastructure 106, which may include short-term storage (e.g., up to thirty days) such as in the service server 300 and longer-term storage such as in the back-end server 306. The display may distribute the real-time and batch data to the cloud computing infrastructure 106 as separate data streams.
[0185] Next, at process 1004, components of a data communication ecosystem according to the present technology may identify lost data. Because data streams are distributed throughout the system, it is possible that one or more components that should have received the data after distribution did not receive the data. For example, a display may be outside the wireless range of a continuous glucose monitor, or a network connection within a cloud computing architecture may be interrupted. In some embodiments, a computing device such as a server in a cloud infrastructure may be interrupted or undergo maintenance, and therefore data is not received when the data is distributed.
[0186] Various components of the system can determine whether any data is lost. For example, the display 104 itself can determine whether it loses any real-time data by checking the timestamp associated with the glucose value or other marks indicating the order of the data (for example, each glucose value is associated with the value of the consecutive number). For example, when the glucose value from the continuous glucose sensor unit 100 is expected every five minutes, but the glucose value is not received within fifteen minutes, if there is a gap in the timestamp or other marks, the display 104 identifies the data as lost. Similarly, the cloud computing architecture 106 (for example, including the service server 300 and the back-end server 306) can determine whether any data is lost by checking the timestamp or other marks. In addition, for example, a third-party application can determine whether any data is lost. In some embodiments, the data synchronization server 302 can determine whether any display 104, the service server 300 or the back-end server 306 is losing data. In this way, it can be determined by the cloud computing architecture 106 whether each component of the lost data should be backfilled with the lost data.
[0187] At process 1006, the component that identifies the data being lost determines whether to obtain the lost data. There may be a maximum amount of time to backfill the data. For example, the data previously lost from more than six hours may not be backfilled into the display 104 that loses a large amount of emission from the continuous glucose sensor unit 100. In some embodiments, other components of the system (e.g., backend server 306) can backfill all lost data without time restrictions. Similarly, components of ecosystems such as display 104 can only backfill some types of data after a certain time period has passed (e.g., six hours), without backfilling other types. In addition, the backfill cycle can be less than the cycle in which the data may not yet be available. For example, even after a six-hour window of data loss, batch data can be backfilled, while real-time data cannot. In addition, the backfill cycle can be less than the cycle in which the data may not yet be available. For example, data may not yet be available for the display in the past six hours, but when the data becomes available, the display can only backfill the last two hours instead of all six hours of lost data. In another example, while display 104 may be missing for an extended period (e.g., six hours), the display may only backfill a subset of that time (e.g., two hours) during a given time period in order to conserve resources (e.g., battery life) of components of the system. Determining whether backfilling data may be done because after a certain amount of time, some data may become stale to certain components of the system, backfilling may consume too much battery power for one or more components of the system (e.g., transmitter 102), and / or the component of the system requesting the backfilled data (e.g., display 104) may be configured to display only a certain range of data, such as the last six hours, thereby backfilling further than may be necessary. Computational and storage requirements may also be reduced by only selectively backfilling data.
[0188] If the component determines that it should not obtain the missing data, then Fig.10 The method may return to identify any additional missing data. For example, the display 104 may determine that it is missing data in a continuous ten hour period. In this example, it may determine that no data older than the previous six hours is available, or the transmitter 102 of the continuous glucose sensor unit 100 may have only stored data for the past six hours, and return to identify further missing data in the last six hours at process 1004.
[0189] If the missing data should be obtained, then at process 1008, the component backfills the missing data. In some embodiments, the component backfills from the oldest available data (or the oldest time period required) to the most recent time period. In other embodiments, the component backfills from the most recent data to the oldest data. The process of backfilling the missing data can occur with respect to an individual stream (e.g., real-time or batch data) or two streams. As an example, the display 104 can request the missing data from the continuous glucose sensor unit 100 or from the service server 300. The service server 300 may also be losing data, and it may receive, for example, four data streams associated with a single continuous glucose sensor unit 100 in some embodiments. The continuous glucose sensor unit 100 sends the real-time data stream and the batch data stream to each connected display, such as two displays, resulting in four streams. The service server 300 and other components such as the back-end server 306 in the cloud computing architecture 106 can store not only the indication of the continuous glucose sensor unit 100 that sent the data, but also the indication of which display sends the data. In this way, components of the cloud computing architecture 106 can store separate data streams (e.g., real-time and batch) on a per-display basis. This helps resolve technical support issues through the backend server 306. When a system component obtains backfilled data, the system component also stores an indication that the data was backfilled rather than received at the time of the initial distribution. This also helps diagnose problems, such as when an alert is missed as previously described.
[0190] In addition, storing multiple data streams from multiple displays associated with a single continuous glucose sensor unit 100 allows the cloud computing architecture 106 to verify the data streams against each other. For example, the real-time data stream from the first display can be compared with the real-time data stream from the second display, and any differences can be recorded. The difference can indicate that the two displays are not using the same calibration value, or other system problems. Detection of any difference can result in a prompt to the user on either display, such as a prompt to the user to update the calibration value. Comparing the two streams also allows confirmation that the data is being effectively captured by both displays.
[0191] Fig.11 Another exemplary method for backfilling missing data is illustrated. In some cases, the amount of data to be backfilled should be limited. For example, a user may turn off their display 104 (e.g., turn off their smartphone) for an extended period of time, or even change their smartphone. However, when a user has had their continuous glucose monitor (e.g., continuous glucose sensor unit 100) for an extended period of time, backfilling all previous data can cause system congestion and is unnecessary. Therefore, Fig.11The method searches for any missing data within a defined time interval up to a maximum amount of time, such as one day, 12 hours, six hours, one hour, 30 minutes, ten minutes, five minutes, one minute, etc.
[0192] At process 1100, the system component searches for lost data in the first time interval. As described above, any system component, such as display 104, service server 300, back-end server 306, remote monitor display such as 316, or other components, can search for any lost data. The first time interval may vary based on the device for searching lost data. For example, a user's computing device such as display 104 may have a relatively limited amount of memory compared to a server. Display 104 may search to backfill lost data in a six-hour interval until a maximum of twenty-four hours, while service server 300 may search back to more than the last thirty days of lost data. In some embodiments, display 104 can automatically send backfill data once it has received backfill data; however, the display may need to request data from the transmitter 102 of the continuous glucose sensor unit 100. This may be because the transmitter 102 may have a more limited power source (e.g., battery) than the display 104. At process 1102, the system component backfills any lost data found during the first time interval as described above.
[0193] Next, at process 1104, the system component searches for missing data in additional time intervals. Continuing with the above example, the display 104 can search for missing data in the past six hours, and backfill any missing data by requesting the missing data from the continuous glucose sensor unit 100. Next, the display searches for missing data in additional time intervals (e.g., another six hours). Of course, other time intervals may also be used. The most recent time interval may be the first backfill data starting at the most recent time, or the search may start at the maximum past duration and search towards newer data that may have been lost. At process 1106, the component backfills any missing data from the additional time intervals.
[0194] At process 1108, the system component determines whether the maximum interval has been reached. For example, if the display 104 has searched for more than the last twenty-four hours, it will stop searching at process 1110. However, if additional time intervals exist up to the maximum interval for the particular component search, then process 1104 repeats to continue searching for data that should be backfilled.
[0195] In addition, the backfill technology disclosed herein is applicable to a variety of system components and applications. A challenge that may occur is to provide and backfill data to a remote monitoring application or a remote monitor device. Real-time data can reach the remote monitor device, but the remote monitor device may be offline or outside the wireless range. The remote monitor can set an alarm to issue an alarm when the patient's glucose level is higher than a defined level (e.g., higher than 200 mg / dL) for a time period of, for example, one hour. If the data point does not arrive at the remote monitor device sequentially, it will not be able to track and issue an alarm. In addition, if only thirty minutes of data are backfilled when the device is back online, it will not meet the alarm criteria, because the exemplary alarm depends on one hour of data. In order to solve this problem, the remote monitor device can be backfilled in a defined time range such as six hours as previously described. In one embodiment, data can be sent to the remote monitoring application from the oldest to the latest. In some embodiments, a server such as a real-time server 908 or a service server 300 of the cloud computing architecture 106 initiates an alarm to send to a remote monitor device such as a remote monitor 316b, which indicates that the backfilled data is being provided. The data provided to the remote monitor device as backfilled data may be displayed on the remote monitor device's display differently than the data provided in its normal cycle. This will help the remote monitor device know whether action should be taken based on the backfilled data. Similar to the above, the remote monitoring settings may be configured by a server (e.g., real-time server 908 or service server 300). In an illustrative example, the remote monitor may not want to know that the adult or responsible person "went low" six hours ago because the person may have taken action on themselves to remedy the situation. Therefore, the remote monitor device may configure the data sent in the backfill so that stale data is not displayed, define a time period for the backfill, define a backfill from newest to oldest or oldest to newest, do not backfill certain data points, and the like.
[0196] In general, data is backfilled from the oldest to the latest (most recent). This can cause some confusion in the alarm when the oldest data starts to be backfilled, and the alarm condition may exist. For example, the glucose level may drop to the alarm level or stay at the level that triggers the alarm after a set amount of time. However, when the display that now receives the backfill data has not received real-time data, this condition may have occurred, for example, four hours ago. Instead of triggering an alarm on the display 104 or remote monitor device 316 that is now used for the remote monitor, the server can be configured to continue to backfill data to determine whether the alarm condition clears itself. Moreover, the server of the cloud computing architecture 106 (for example, the real-time server 908 or the service server 300) can be set so that the stale backfill alarm will not be triggered unless there is a rule about the server associated with the specific display that instructs it to do so. For example, the person being monitored may be a child, in which case the remote monitor (for example, a parent) may wish to know that the child has experienced an alarm condition, even if it was in the past and has now corrected itself. Therefore, even if the condition occurred in the previous hours, the parent's monitoring device (for example, the display 316) can also be triggered to sound an alarm. The remote monitor display 316a may also be configured to indicate that the alarm is based on backfill data rather than current data.
[0197] Fig.13 An exemplary computer is shown. The continuous glucose sensor unit 100, display 104, computing devices including associated servers of a cloud computing architecture 106, and other system components may include Fig.13 All or some of the components shown in .
[0198] The computer may include one or more hardware components, such as a central processing unit (CPU) 1321, a random access memory (RAM) module 1322, a read-only memory (ROM) module 1323, a storage device 1324, a database 1325, one or more input / output (I / O) devices 1326, and an interface 1327. Alternatively or in addition, the computer may include one or more software components, such as a computer-readable medium containing computer-executable instructions for performing methods associated with exemplary embodiments. It is contemplated that one or more of the hardware components listed above may be implemented using software. For example, the storage device 1324 may include a software partition associated with one or more other hardware components. It should be understood that the components listed above are exemplary only and are not intended to be limiting.
[0199] The CPU 1321 may include one or more processors, each of which is configured to execute instructions and process data to perform one or more functions associated with a computer for monitoring glucose levels. The CPU 1321 may be communicatively coupled to the RAM 1322, the ROM 1323, the storage device 1324, the database 1325, the I / O device 1326, and the interface 1327. The CPU 1321 may be configured to execute sequences of computer program instructions to perform various processes. The computer program instructions may be loaded into the RAM 1322 for execution by the CPU 1321.
[0200] RAM 1322 and ROM 1323 may each include one or more devices for storing information associated with the operation of CPU 1321. For example, ROM 1323 may include a memory device configured to access and store information associated with the controller, including information for identifying, initializing, and monitoring the operation of one or more components and subsystems. RAM 1322 may include a memory device for storing data associated with one or more operations of CPU 1321. For example, ROM 1323 may load instructions into RAM 1322 for execution by CPU 1321.
[0201] Storage device 1324 may include any type of mass storage device configured to store information that may be required by CPU 1321 to perform processes consistent with the disclosed embodiments. For example, storage device 1324 may include one or more magnetic and / or optical disk devices, such as a hard drive, CD-ROM, DVD-ROM, or any other type of mass media device.
[0202] The database 1325 may include one or more software and / or hardware components that cooperate to store, organize, sort, filter, and / or arrange data used by the CPU 1321. For example, the database 1325 may store data related to monitoring glucose levels, associated metadata, and health information. It is contemplated that the database 1325 may store additional information and / or information different from that listed above.
[0203] The I / O device 1326 may include one or more components configured to communicate information with a user associated with the controller. For example, the I / O device may include a console with an integrated keyboard and mouse to allow the user to maintain an image database, update associations, and access digital content. The I / O device 1326 may also include a display including a graphical user interface (GUI) for outputting information on a monitor. The I / O device 1326 may also include peripheral devices, such as a printer for printing information associated with the controller, a user-accessible disk drive (e.g., a USB port, a floppy disk, a CD-ROM or DVD-ROM drive, etc.) that allows the user to input data stored on a portable media device, a microphone, a speaker system, or any other suitable type of interface device.
[0204] The interface 1327 may include one or more components configured to transmit and receive data via a communication network, such as the Internet, a local area network, a workstation peer-to-peer network, a direct link network, a wireless network, or any other suitable communication platform. For example, the interface 1327 may include one or more modulators, demodulators, multiplexers, demultiplexers, network communication devices, wireless devices, antennas, modems, and any other type of device configured to achieve data communication via a communication network.
[0205] Examples
[0206] The following examples illustrate several embodiments of the present technology. Other exemplary embodiments of the present technology may be presented before or after the examples listed below.
[0207] In some embodiments, according to the present technology (Example 1), a method for securely transmitting data related to glucose levels includes: preparing data including glucose levels using a continuous glucose monitor; wirelessly transmitting the data related to glucose levels from a transmitter associated with the continuous glucose monitor to at least one display device; automatically forwarding the data related to glucose levels from the display device to a cloud computing architecture; and storing the data related to glucose levels in a separate group at the cloud infrastructure.
[0208] Example 2 comprises the method of example 1, wherein the data related to glucose levels comprises measured glucose values and diagnostic data.
[0209] Example 3 includes the method of example 1, further comprising including, by the display device, additional data along with the data related to glucose level, wherein automatically forwarding the data includes automatically forwarding the additional data along with the data related to glucose level.
[0210] Example 4 includes the method of Example 1, wherein the data related to glucose levels includes a first data set and a second data set, and storing the data related to glucose levels in separate groups includes storing the first data set on a first server and storing the second data set on a second server.
[0211] Example 5 includes the method of Example 4, wherein the first data set includes real-time data, the real-time data including one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set includes at least one of information for calibrating the continuous glucose monitor and information for technical support for the continuous glucose monitor.
[0212] Example 6 includes the method of Example 5, which further includes: encrypting the first data set by the transmitter; encrypting the second data set by the transmitter; decrypting and displaying the first data set by the at least one display device; preventing the at least one display device from decrypting the second data set; and decrypting the second data set by the cloud infrastructure.
[0213] Example 7 includes the method of Example 6, further comprising: storing, by the at least one display device, a first key for decrypting the first data set; storing, by the cloud infrastructure, a second key for decrypting the second data set; and preventing the at least one display device from accessing the second key.
[0214] Example 8 includes the method of example 1, further comprising forwarding a subset of the data related to glucose levels from the cloud infrastructure to a second display device, the subset of data including at least one of current and past glucose levels.
[0215] Example 9 includes the method of example 1, further comprising selectively determining, by the cloud infrastructure, whether to grant one or more requesting systems access to the first set of data and the second set of data.
[0216] Example 10 includes the method of Example 9, wherein the requesting system includes a technical support system, at least one third-party application, and a data warehouse, wherein the cloud infrastructure: grants the technical support system access to the first data set and the second data set; grants the at least one third-party application access to the first data set; and grants the data warehouse access to the first data set and the second data set.
[0217] Example 11 includes the method of Example 1, wherein the display device includes at least one of a smartphone or a display.
[0218] In some embodiments, according to the present technology (Example 12), a system for monitoring data related to glucose levels includes: a continuous glucose sensor, which is configured to prepare data related to glucose levels; a wireless transmitter, which is configured to transmit the data related to glucose levels; a display device, which is configured to receive the transmitted data related to glucose levels and automatically forward the data; a cloud computing architecture, which is configured to receive the automatically forwarded data and store the data related to glucose levels in a separate group.
[0219] Example 13 includes the system of example 12, wherein the data related to glucose levels includes measured glucose values and diagnostic data.
[0220] Example 14 includes the system of example 12, wherein the display device is further configured to: include additional data along with the data related to glucose level; and automatically forward the additional data along with the data related to glucose level.
[0221] Example 15 includes the system of Example 12, wherein the data related to glucose levels includes a first data set and a second data set, and storing the data related to glucose levels in separate groups includes separately storing the first data set on a first server and storing the second data set on a second server.
[0222] Example 16 includes the system of Example 15, wherein the first data set includes real-time data, the real-time data including one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set includes information for calibrating the continuous glucose monitor and at least one of information for technical support for the continuous glucose monitor.
[0223] Example 17 includes the system of Example 16, wherein the transmitter is further configured to encrypt the first data set and the second data set; the at least one display device is further configured to decrypt and display the first data set; the at least one display device is unable to decrypt the second data set; and the cloud infrastructure is further configured to decrypt the second data set.
[0224] Example 18 includes the system of Example 17, wherein the at least one display device is further configured to store a first key for decrypting the first data set; the cloud infrastructure is further configured to store a second key for decrypting the second data set; and the at least one display device cannot access the second key.
[0225] Example 19 includes the system of example 12, wherein the cloud infrastructure is further configured to forward a subset of the data related to glucose levels to a second display device, the subset of data including at least one of current and past glucose levels.
[0226] Example 20 includes the system of example 12, wherein the cloud infrastructure is further configured to selectively determine whether to grant access to the first set of data and the second set of data to one or more requesting systems.
[0227] Instance 21 includes the system of Instance 20, wherein the requesting system includes a technical support system, at least one third-party application, and a data warehouse, wherein the cloud infrastructure is further configured to: grant the technical support system access to the first data set and the second data set; grant the at least one third-party application access to the first data set; and grant the data warehouse access to the first data set and the second data set.
[0228] Example 22 includes the system of example 12, wherein the display device includes at least one of a smartphone or a display.
[0229] In some embodiments, according to the present technology (Example 23), one or more computer-readable media, which include instructions, which when executed by one or more processors, perform a method for securely transmitting data related to glucose levels, the method comprising: preparing data related to glucose levels using a continuous glucose monitor; wirelessly transmitting the data related to glucose levels from a transmitter associated with the continuous glucose monitor to at least one display device; automatically forwarding the data related to glucose levels from the display device to a cloud computing architecture; and storing the data related to glucose levels in a separate group at the cloud infrastructure.
[0230] Example 24 includes the computer-readable medium of example 23, wherein the data related to glucose levels includes measured glucose values and diagnostic data.
[0231] Example 25 includes the computer-readable medium of Example 23, wherein the method further includes including, by the display device, additional data along with the data related to glucose levels, wherein automatically forwarding the data includes automatically forwarding the additional data along with the data related to glucose levels.
[0232] Example 26 includes the computer-readable medium of Example 23, wherein the data related to glucose levels includes a first data set and a second data set, and storing the data related to glucose levels in separate groups includes storing the first data set and the second data set separately by the cloud infrastructure.
[0233] Example 27 includes a computer-readable medium of Example 26, wherein the first data set includes real-time data, the real-time data including one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set includes information for calibrating the continuous glucose monitor and at least one of information for technical support for the continuous glucose monitor.
[0234] Example 28 includes computer-readable media of Example 27, wherein the method further includes: encrypting the first data set by the transmitter; encrypting the second data set by the transmitter; decrypting and displaying the first data set by the at least one display device; preventing the at least one display device from decrypting the second data set; and decrypting the second data set by the cloud infrastructure.
[0235] Example 29 includes computer-readable media of Example 28, wherein the method further includes: storing, by the at least one display device, a first key for decrypting the first data set; storing, by the cloud infrastructure, a second key for decrypting the second data set; and preventing the at least one display device from accessing the second key.
[0236] Example 30 includes the computer-readable medium of Example 23, wherein the method further includes forwarding a subset of the data related to glucose levels from the cloud infrastructure to a second display device, the subset of data including at least one of current and past glucose levels.
[0237] Example 31 includes the computer-readable medium of Example 23, wherein the method further includes selectively determining, by the cloud infrastructure, whether to grant access to the first set of data and the second set of data to one or more requesting systems.
[0238] Instance 32 includes computer-readable media of Instance 31, wherein the requesting system includes a technical support system, at least one third-party application, and a data warehouse, wherein the cloud infrastructure: grants the technical support system access to the first data set and the second data set; grants the at least one third-party application access to the first data set; and grants the data warehouse access to the first data set and the second data set.
[0239] Example 33 includes the computer-readable medium of Example 23, wherein the display device includes at least one of a smartphone or a display.
[0240] In some embodiments (Example 34) of the present technology, a method for encrypting and transmitting data related to glucose levels from a continuous glucose monitor comprises: encrypting a first data set by a transmitter associated with the continuous glucose monitor; encrypting a second data set by the transmitter; wirelessly transmitting the first data set and the second data set to at least one display device; decrypting the first data set by the display device; preventing the display device from decrypting the second data set; automatically forwarding the first data set and the second data set to a cloud infrastructure; and decrypting the second data set by the cloud infrastructure.
[0241] Example 35 includes the method of Example 34, wherein the first data set includes real-time data, the real-time data including one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set includes information for calibrating the continuous glucose monitor and at least one of information for technical support for the continuous glucose monitor.
[0242] Example 36 includes the method of Example 34, wherein the transmitter uses an Advanced Encryption Standard when encrypting the first set of data and the second set of data.
[0243] Example 37 includes the method of example 34, further comprising: storing the first set of data on a first server in the cloud infrastructure; and storing the second set of data on a second, different server in the cloud infrastructure.
[0244] Example 38 includes the method of Example 34, wherein the display device includes at least one of a display or a smartphone.
[0245] Example 39 includes the method of example 34, wherein automatically forwarding includes forwarding the first set of data and the second set of data via a personal computer connected to the display, the connection including a wired or wireless connection.
[0246] In some embodiments (Example 40) of the present technology, a system for encrypting and transmitting data related to glucose levels from a continuous glucose monitor comprises: a transmitter associated with the continuous glucose monitor, configured to encrypt a first data set and a second data set, and wirelessly transmit the first data set and the second data set; at least one display device, configured to receive the first data set and the second data set, decrypt the first data set, and automatically forward the first data set and the second data set; and a cloud infrastructure, configured to receive the first data set and the second data set from the at least one display device, and decrypt the second data set, wherein the at least one display device is unable to decrypt the second data set.
[0247] Example 41 includes the system of Example 40, wherein the first data set includes real-time data, the real-time data including one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set includes information for calibrating the continuous glucose monitor and at least one of information for technical support for the continuous glucose monitor.
[0248] Example 42 includes the system of example 40, wherein the transmitter uses an Advanced Encryption Standard when encrypting the first set of data and the second set of data.
[0249] Example 43 includes the system of example 40, further comprising: a first server in the cloud infrastructure configured to store the first set of data; and a second server in the cloud infrastructure configured to store the second set of data.
[0250] Example 44 includes the system of example 40, wherein the display device includes at least one of a display or a smart phone.
[0251] Example 45 includes the system of example 40, further comprising a personal computer configured to receive the first set of data and the second set of data from the at least one display device and forward the first set of data and the second set of data to the cloud infrastructure.
[0252] In some embodiments (Example 46) of the present technology, one or more computer-readable media, which include instructions, which when executed by one or more processors perform a method for encrypting and transmitting data related to glucose levels from a continuous glucose monitor, the method comprising: encrypting a first data set by a transmitter associated with the continuous glucose monitor; encrypting a second data set by the transmitter; wirelessly transmitting the first data set and the second data set to at least one display device; decrypting the first data set by the display device; preventing the display device from decrypting the second data set; automatically forwarding the first data set and the second data set to a cloud infrastructure; and decrypting the second data set by the cloud infrastructure.
[0253] Example 47 includes a computer-readable medium of Example 46, wherein the first data set includes real-time data, the real-time data including one or more of a glucose value, a current state of a continuous glucose sensor, and a timestamp associated with a measurement used to obtain the glucose value; and the second data set includes information for calibrating the continuous glucose monitor and at least one of information for technical support for the continuous glucose monitor.
[0254] Example 48 includes the computer-readable medium of example 46, wherein the transmitter uses an Advanced Encryption Standard when encrypting the first set of data and the second set of data.
[0255] Example 49 includes the computer-readable medium of Example 46, wherein the method further comprises: storing the first set of data on a first server in the cloud infrastructure; and storing the second set of data on a second server in the cloud infrastructure.
[0256] Example 50 includes the computer-readable medium of example 46, wherein the display device includes at least one of a display or a smart phone.
[0257] Example 51 includes the computer-readable medium of example 46, wherein automatically forwarding includes forwarding the first set of data and the second set of data via a personal computer connected to the display, the connection including a wired or wireless connection.
[0258] In some embodiments (Example 52) of the present technology, a method for controlling access to data related to glucose levels includes: defining multiple rules for controlling access to the data related to glucose levels at a cloud infrastructure; providing multiple application interfaces for accessing the data related to glucose levels; receiving a request for the data related to glucose levels through at least one of the application interfaces; determining whether to grant the request for the data related to glucose levels based on the multiple rules and the request for the data; and providing access to the data related to glucose levels after determining that access should be granted.
[0259] Example 53 includes the method of example 52, further comprising: receiving the request through a common application; and providing the request to the cloud infrastructure, wherein providing access includes providing the data related to glucose levels to at least one of the application interfaces through the common application.
[0260] Example 54 includes the method of example 53, further comprising providing a single sign-on including a username and password for the common application and multiple applications using the application program interface.
[0261] Example 55 includes the method of example 53, further comprising launching a web page interface from the common application in response to a request for an application using at least one of the application program interfaces.
[0262] Example 56 includes the method of example 55, further comprising: providing an icon for a second application in the common application; receiving a selection of the icon; directly accessing a server hosting the second application; and executing a result of accessing the server in the common application.
[0263] Example 57 includes the method of Example 52, further comprising: receiving, by the cloud infrastructure, a request from a second display device to access the data related to glucose levels; storing, by the cloud infrastructure, an anonymous identifier associated with the second display device; and providing the data related to glucose levels to the second display device.
[0264] In some embodiments (Example 58) of the present technology, a system for controlling access to data related to glucose levels includes: one or more display devices, which include multiple application interfaces for accessing the data related to glucose levels, and the display devices are configured to receive a request for the data related to glucose levels through at least one of the application interfaces; and a cloud infrastructure, which is configured to define multiple rules for controlling access to the data related to glucose levels, determine whether to grant the request for the data related to glucose levels based on the multiple rules and the request for the data, and provide access to the data related to glucose levels after determining that access should be granted.
[0265] Example 59 includes the system of Example 58, further including a common application executing on the one or more display devices, configured to receive the request and provide the request to the cloud infrastructure, wherein the cloud infrastructure provides access by providing the data related to glucose levels to at least one of the application interfaces through the common application.
[0266] Example 60 includes the system of example 59, wherein a single sign-on including a username and password accesses the common application and multiple applications using the application program interface.
[0267] Example 61 includes the system of example 59, wherein the one or more display devices are further configured to launch a web page interface from the common application in response to a request for an application using at least one of the application program interfaces.
[0268] Example 62 includes the system of Example 61, wherein the one or more display devices are further configured to: provide an icon for a second application in the common application; receive a selection of the icon; directly access a server hosting the second application; and execute a result of accessing the server in the common application.
[0269] Example 63 includes the system of Example 58, further including a second display device configured to provide a request to the cloud infrastructure to access the data related to the glucose level, wherein the cloud infrastructure is further configured to store an anonymous identifier associated with the second display device and provide the data related to the glucose level to the second display device.
[0270] In some embodiments (Example 64) of the present technology, one or more computer-readable media, which include instructions, which when executed by one or more processors, perform a method for controlling access to data related to glucose levels, the method comprising: defining a plurality of rules for controlling access to the data related to glucose levels at a cloud infrastructure; providing a plurality of application interfaces for accessing the data related to glucose levels; receiving a request for the data related to glucose levels through at least one of the application interfaces; determining whether to grant the request for the data related to glucose levels based on the plurality of rules and the request for the data; and providing access to the data related to glucose levels after determining that access should be granted.
[0271] Example 65 includes the computer-readable medium of Example 64, wherein the method further includes: receiving the request through a common application; and providing the request to the cloud infrastructure, wherein providing access includes providing the data related to glucose levels to at least one of the application interfaces through the common application.
[0272] Example 66 includes the computer-readable medium of example 65, wherein the method further includes providing a single sign-on including a username and password for the common application and multiple applications using the application program interface.
[0273] Example 67 includes the computer-readable medium of example 65, wherein the method further includes launching a web page interface from the common application in response to a request for an application using at least one of the application program interfaces.
[0274] Example 68 includes the computer-readable medium of Example 67, wherein the method further comprises: providing an icon for a second application in the common application; receiving a selection of the icon; directly accessing a server hosting the second application; and executing a result of accessing the server in the common application.
[0275] Example 69 includes the computer-readable medium of Example 68, wherein the method further includes: receiving, by the cloud infrastructure, a request by a second display device to access the data related to glucose levels; storing, by the cloud infrastructure, an anonymous identifier associated with the second display device; and providing the data related to glucose levels to the second display device.
[0276] In some embodiments (Example 70) of the present technology, a method for updating data related to glucose levels in a distributed architecture includes: obtaining one or more data points related to glucose levels from a transmitter associated with a continuous glucose monitor; distributing the one or more data points among one or more display devices and one or more servers; identifying a missing data point from a display device or a server, the missing data point being one of the one or more data points; and providing the missing data point to the at least one display device or server when the missing data point falls within a defined time period.
[0277] Example 71 includes the method of example 70, wherein the missing data points include backfilled data sent to the display device or server after the distribution.
[0278] Example 72 includes the method of example 70, further comprising: identifying one or more missing data points from a display device or a server; and providing the one or more missing data points to the display device or the server.
[0279] Example 73 includes the method of Example 70, further comprising: identifying one or more missing data points from a display device or a server; determining which of the one or more missing data points occurred within a subset of the defined time interval; and providing those missing data points that occurred within the subset of the defined time interval.
[0280] Example 74 includes the method of Example 73, further comprising: displaying the one or more data points and the missing data points; and displaying an indication that the missing data points include backfilled data.
[0281] Example 75 includes the method of example 70, wherein the at least one display device or server that received the missing data point was turned off or disconnected when the missing data point was initially available.
[0282] Example 76 includes the method of Example 70, which further includes: identifying one or more lost data points from a display device or server; determining a number of the lost data points to be backfilled based on the device that lost the data; and providing the determined number of lost data points to the display device or server.
[0283] Example 77 includes the method of Example 70, further comprising storing, by the one or more display devices or servers provided with the missing data points, an indication that the missing data points include backfilled data.
[0284] Example 78 includes the method of example 70, further comprising storing, by the one or more display devices and the one or more servers, an indication that the one or more data points were received in real time.
[0285] Example 79 includes the method of Example 70, further comprising: connecting a plurality of display devices to the transmitter; distributing the one or more data points to the plurality of display devices; and forwarding the one or more data points from the plurality of display devices to the one or more servers along with an indication of which display device forwarded the data.
[0286] Example 80 includes the method of Example 79, further comprising: receiving the one or more data points during the distribution of the plurality of data sets; and displaying the one or more data points received during the distribution differently from the missing data points.
[0287] Example 81 includes the method of example 70, wherein the defined time period includes the past six hours.
[0288] In some embodiments (Example 82) of the present technology, a system for updating data related to glucose levels in a distributed architecture includes: a transmitter associated with a continuous glucose monitor, which is configured to obtain multiple data sets related to glucose levels and distribute the multiple data sets among one or more display devices and one or more servers, wherein the one or more display devices and one or more servers are configured to identify missing data sets from the multiple data sets, request the missing data sets, and receive the missing data sets when the missing data sets fall within a defined time period.
[0289] Example 83 includes the system of example 82, wherein the missing data set includes backfilled data sent to the one or more display devices or servers after the distribution.
[0290] Example 84 includes the system of Example 82, wherein the one or more display devices and the one or more servers are configured to: identify multiple missing data sets from the display devices or the servers; request the multiple missing data sets; and receive the multiple missing data sets.
[0291] Example 85 includes the system of Example 82, wherein the one or more display devices and the one or more servers are configured to: identify multiple lost data sets; determine which of the multiple lost data sets were generated within a subset of the defined time interval; and request those lost data sets generated within the subset of the defined time interval.
[0292] Example 86 includes the system of Example 85, wherein the one or more display devices are configured to: display the multiple data sets and the missing data set; and display an indication that the missing data set includes backfilled data.
[0293] Example 87 includes the system of example 82, wherein the one or more display devices or servers that received the lost data set were turned off or disconnected when the lost data set was initially available.
[0294] Example 88 includes the system of Example 82, wherein multiple lost data sets are identified from a display device or server; the number of lost data sets to be backfilled is determined based on the device that lost the data; and the determined number of lost data sets are provided to the display device or server.
[0295] Example 89 includes the system of example 82, wherein the at least one display device or server provided with the missing data set stores an indication that the missing data set includes backfilled data.
[0296] Example 90 includes the system of example 89, wherein the one or more display devices and the one or more servers store an indication that the plurality of data sets are received in real time.
[0297] Example 91 includes the system of Example 82, further comprising: a plurality of display devices connected to the transmitter, wherein the plurality of data sets are distributed to the plurality of display devices; and forwarding the plurality of data sets from the plurality of display devices to the one or more servers together with an indication of which display device forwarded the data set.
[0298] Example 92 includes the system of example 82, wherein the plurality of data sets are received during the distribution of the plurality of data sets; and the plurality of data sets received during the distribution are displayed differently from the lost data sets.
[0299] Example 93 includes the system of example 82, wherein the defined time period includes the past six hours.
[0300] In some embodiments (Example 94) of the present technology, one or more computer-readable media, which include instructions, which when executed by one or more processors, perform a method for updating data related to glucose levels in a distributed architecture, the method comprising: obtaining multiple data sets related to glucose levels from a transmitter associated with a continuous glucose monitor; distributing the multiple data sets among one or more display devices and one or more servers; identifying a missing data set from a display device or a server, the missing data set being one of the multiple data sets; and providing the missing data set to the at least one display device or server when the missing data set falls within a defined time period.
[0301] Example 95 includes the computer-readable medium of example 94, wherein the missing data set includes backfilled data sent to the display device or server after the distribution.
[0302] Example 96 includes the computer-readable medium of example 94, wherein the method further comprises: identifying a plurality of missing data sets from a display device or a server; and providing the plurality of missing data sets to the display device or the server.
[0303] Example 97 includes computer-readable media of Example 94, wherein the method further includes: identifying multiple lost data sets from a display device or a server; determining which of the multiple lost data sets are generated within a subset of the defined time interval; and providing those lost data sets generated within the subset of the defined time interval.
[0304] Example 98 includes the computer-readable medium of Example 95, wherein the method further includes: displaying the plurality of data sets and the missing data set; and displaying an indication that the missing data set includes backfilled data.
[0305] Example 99 includes the computer-readable medium of example 94, wherein the at least one display device or server that received the missing data set was turned off or disconnected when the missing data set was initially available.
[0306] Example 100 includes computer-readable media of Example 95, wherein the method further includes: identifying multiple lost data sets from a display device or a server; determining the number of lost data sets to be backfilled based on the device that lost the data; and providing the determined number of lost data sets to the display device or the server.
[0307] Example 101 includes the computer-readable medium of example 100, wherein the method further includes storing, by the one or more display devices or servers provided with the missing data set, an indication that the missing data set includes backfilled data.
[0308] Example 102 includes the computer-readable medium of example 101, wherein the method further includes storing, by the one or more display devices and the one or more servers, an indication that the plurality of data sets are received in real time.
[0309] Instance 103 includes computer-readable media of Instance 94, wherein the method further includes: connecting a plurality of display devices to the transmitter; distributing the plurality of data sets to the plurality of display devices; and forwarding the plurality of data sets from the plurality of display devices to the one or more servers along with an indication of which display device forwarded the data set.
[0310] Example 104 includes the computer-readable medium of Example 94, wherein the method further includes: receiving the plurality of data sets during the distribution of the plurality of data sets; and displaying the plurality of data sets received during the distribution differently from the lost data sets.
[0311] Example 105 includes the computer-readable medium of example 94, wherein the defined time period includes the past six hours.
[0312] In some embodiments (Example 106) of the present technology, a method for synchronizing data related to glucose levels in a distributed architecture system includes: providing multiple data sets related to glucose levels from a transmitter associated with a continuous glucose monitor to a first display device and a second display device; providing the multiple data sets from the first display device and the second display device to a server; and separately storing the multiple data sets by the server based on whether the multiple data sets are received from the first display device or the second display device.
[0313] Example 107 includes the method of Example 106, further comprising: marking, by the first display device, the plurality of data sets as having been received by the first display device; and marking, by the second display device, the plurality of data sets as having been received by the second display device.
[0314] Example 108 includes the method of Example 106, further comprising: including a first alert on the first display device when the glucose level reaches a first defined level or experiences a first rate of change; and generating a second alert on the second display device when the glucose level reaches a second defined level or experiences a second rate of change.
[0315] Example 109 includes the method of example 106, further comprising: configuring when the plurality of sets of data are provided from the first display device to the server; and configuring when the plurality of sets of data are provided from the second display device to the server.
[0316] Example 110 includes the method of example 106, wherein the server comprises a distributed cloud computing system comprising a plurality of connected computing devices.
[0317] In some embodiments (Example 111) of the present technology, a system for synchronizing data related to glucose levels in a distributed architecture system includes: a transmitter associated with a continuous glucose monitor, which is configured to provide multiple data sets related to glucose levels; a first display device and a second display device, which are configured to receive the multiple data sets and provide the multiple data sets; and a server, which is configured to receive the multiple data sets and separately store the multiple data sets based on whether the multiple data sets are received from the first display device or the second display device.
[0318] Example 112 includes the system of example 111, wherein the first display device marks the plurality of data sets as having been received by the first display device; and the second display device marks the plurality of data sets as having been received by the second display device.
[0319] Example 113 includes the system of Example 111, wherein the first display device is configured to provide a first alert when the glucose level reaches a first defined level or experiences a first rate of change; and the second display device is configured to provide a second alert when the glucose level reaches a second defined level or experiences a second rate of change.
[0320] Example 114 includes the system of example 111, wherein the first display device is configured to provide the plurality of sets of data to the server at a first defined time; and the second display device is configured to provide the plurality of sets of data to the server at a second defined time.
[0321] Example 115 includes the system of example 111, wherein the server includes a distributed cloud computing system including a plurality of connected computing devices.
[0322] In some embodiments (Example 116) of the present technology, one or more computer-readable media, which include instructions, which when executed by one or more processors, perform a method for synchronizing data related to glucose levels in a distributed architecture system, the method comprising: providing multiple data sets related to glucose levels from a transmitter associated with a continuous glucose monitor to a first display device and a second display device; providing the multiple data sets from the first display device and the second display device to a server; and storing the multiple data sets separately by the server based on whether the multiple data sets are received from the first display device or the second display device.
[0323] Example 117 includes the computer-readable medium of Example 116, wherein the method further includes: marking, by the first display device, the multiple data sets as having been received by the first display device; and marking, by the second display device, the multiple data sets as having been received by the second display device.
[0324] Example 118 includes the computer-readable medium of Example 116, wherein the method further includes: generating a first alert on the first display device when the glucose level reaches a first defined level or experiences a first rate of change; and generating a second alert on the second display device when the glucose level reaches a second defined level or experiences a second rate of change.
[0325] Example 119 includes the computer-readable medium of example 116, wherein the method further comprises: configuring when the multiple sets of data are provided from the first display device to the server; and configuring when the multiple sets of data are provided from the second display device to the server.
[0326] Example 120 includes the computer-readable medium of example 116, wherein the server includes a distributed cloud computing system including a plurality of connected computing devices.
[0327] In some embodiments according to the present technology (Example 121), a system for securely collecting, analyzing and reporting data related to glucose monitoring levels through multiple continuous glucose monitors includes: multiple continuous glucose monitor (CGM) devices; multiple display devices that receive data from the multiple CGM devices, wherein the data is classified into multiple categories based on data type; a cloud server architecture that includes multiple servers that receive the data from the multiple display devices on an intermittent basis, wherein the data routed to a particular server in the multiple servers is determined by the data type, and wherein the intermittent basis varies depending on the data type; multiple remote monitor display devices that receive data from one of the multiple servers, wherein the data sent to each of the multiple remote monitor display devices depends on the data type and on the display device that transmits the data to the one of the multiple servers, and the data is sent to the multiple remote monitor display devices immediately after being received by the one of the multiple servers; and an analysis and reporting engine, wherein at least a portion of the data received by the multiple servers is transmitted to the analysis and reporting engine, the transmitted data is analyzed by the analysis and reporting engine and a report is generated by the analysis and reporting engine.
[0328] Instance 122 includes the system of instance 121, wherein the multiple servers comprising the cloud server architecture include at least a real-time server and a batch data collector.
[0329] Example 123 includes the system of any of examples 121-122, wherein the data type includes real-time data and batch data.
[0330] Example 124 includes the system of example 123, wherein the real-time data is routed from the plurality of display devices to the real-time server, and the batch data is routed from the plurality of display devices to the batch data collector.
[0331] Example 125 includes the system of example 124, wherein the real-time data is routed from the plurality of display devices to the real-time server on an intermittent basis more frequently than the batch data is routed from the plurality of display devices to the batch data collector on an intermittent basis.
[0332] Example 126 includes the system of example 125, wherein the real-time data is routed from the plurality of display devices to the real-time server once every five minutes, and the batch data is routed from the plurality of display devices to the batch data collector once every hour.
[0333] Example 127 includes the system of any of examples 121-126, further comprising a locator service, wherein the plurality of display devices are connected to the cloud server architecture through the locator service.
[0334] Example 128 includes the system of any of examples 121-127, wherein at least one of the plurality of display devices includes a smart phone.
[0335] Example 129 includes the system of any of Examples 121-128, wherein at least one of the plurality of remote monitor display devices includes a smart phone.
[0336] Example 130 includes the system of any of Examples 121-129, wherein the plurality of display devices includes at least 150,000 devices.
[0337] Example 131 includes the system of any of Examples 121-130, wherein at least one of the plurality of remote monitor display devices further includes an application executable by the at least one of the plurality of remote display devices.
[0338] Instance 132 includes the system of Instance 131, wherein the application on the at least one of the plurality of remote monitor display devices must be open and running in order to receive the data ready to be sent to the at least one of the plurality of remote monitor display devices, otherwise the data ready to be sent to the at least one of the plurality of remote monitor display devices is maintained by one of the plurality of servers.
[0339] Example 133 includes the system of any of Examples 121-132, wherein at least one of the plurality of remote monitor display devices receiving data from one of the plurality of servers receives a notification that data is ready to be sent to the at least one of the plurality of remote monitor display devices.
[0340] Instance 134 includes the system of instance 133, wherein the notification includes a text message.
[0341] Example 135 includes the system of example 131, wherein the application executable by the at least one of the plurality of remote display devices wakes up when the one of the plurality of servers attempts to send the data to the at least one of the plurality of remote display devices.
[0342] Example 136 includes the system of example 135, wherein the application requests that the data be sent from the one of the plurality of servers after the application wakes up.
[0343] In some embodiments (Example 136) of the present technology, a method for securely collecting, analyzing, and reporting data related to glucose monitoring levels by multiple continuous glucose monitors includes: receiving data from multiple continuous glucose monitor (CGM) devices by multiple display devices; classifying the data into multiple categories based on data type; transmitting the data from the multiple display devices to a cloud server architecture, which includes multiple servers that receive the data from the multiple display devices on an intermittent basis, wherein the data routed to a particular server in the multiple servers is determined by the data type, and wherein the intermittent basis varies depending on the data type; receiving data from one of the multiple servers by multiple remote monitor display devices, wherein the data sent to each of the multiple remote monitor display devices depends on the data type and on the display device that transmitted the data to the one of the multiple servers, and the data is sent to the multiple remote monitor display devices immediately after being received by the one of the multiple servers; and receiving at least a portion of the data received by the multiple servers by an analysis and reporting engine, the received data being analyzed by the analysis and reporting engine and a report being generated by the analysis and reporting engine.
[0344] Instance 138 includes the method of Instance 137, wherein the multiple servers comprising the cloud server architecture include at least a real-time server and a batch data collector.
[0345] Example 139 includes the method of any of Examples 137-138, wherein classifying the data into a plurality of categories based on a data type includes classifying the data into real-time data and batch data.
[0346] Example 140 includes the method of example 139, wherein the real-time data is routed from the plurality of display devices to the real-time server, and the batch data is routed from the plurality of display devices to the batch data collector.
[0347] Example 141 includes the method of example 140, wherein the real-time data is routed from the plurality of display devices to the real-time server on an intermittent basis more frequently than the batch data is routed from the plurality of display devices to the batch data collector on an intermittent basis.
[0348] Example 142 includes the method of example 141, wherein the real-time data is routed from the plurality of display devices to the real-time server once every five minutes, and the batch data is routed from the plurality of display devices to the batch data collector once every hour.
[0349] Example 143 includes the method of any of examples 137-142, further comprising a locator service, wherein the plurality of display devices are connected to the cloud server architecture through the locator service.
[0350] Example 144 includes the method of any of examples 137-143, wherein at least one of the plurality of display devices includes a smart phone.
[0351] Example 145 includes the method of any of Examples 137-144, wherein at least one of the plurality of remote monitor display devices includes a smart phone.
[0352] Example 146 includes the method of any of Examples 137-145, wherein the plurality of display devices includes at least 150,000 devices.
[0353] Example 147 includes the method of any of Examples 137-146, wherein at least one of the plurality of remote monitor display devices further includes an application executable by the at least one of the plurality of remote display devices.
[0354] Instance 148 includes the method of Instance 147, wherein the application on the at least one of the plurality of remote monitor display devices must be open and running in order to receive the data ready to be sent to the at least one of the plurality of remote monitor display devices, otherwise the data ready to be sent to the at least one of the plurality of remote monitor display devices is maintained by one of the plurality of servers.
[0355] Example 149 includes the method of any of Examples 137-148, wherein at least one of the plurality of remote monitor display devices receiving data from one of the plurality of servers receives a notification that data is ready to be sent to the at least one of the plurality of remote monitor display devices.
[0356] Instance 150 includes the method of instance 149, wherein the notification includes a text message.
[0357] Example 151 includes the method of example 147, wherein the application executable by the at least one of the plurality of remote display devices wakes up when the one of the plurality of servers attempts to send the data to the at least one of the plurality of remote display devices.
[0358] Example 152 includes the method of example 151, wherein the application requests that the data be sent from the one of the plurality of servers after the application wakes up.
[0359] Any combination of one or more computer-readable media may be utilized. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing. More specific examples (non-exhaustive list) of computer-readable storage media would include the following: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The program code embodied on the computer-readable medium may be transmitted using any suitable medium, including (but not limited to) wireless, wired, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
[0360] The computer program code may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, Smalltalk, C++ or similar languages, and conventional procedural programming languages such as the "C" programming language or similar programming languages. The program code may be executed entirely on a computing unit.
[0361] It will be understood that each block of the flowchart illustration and / or block diagram and the combination of blocks in the flowchart illustration and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce components for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram.
[0362] It should be understood that the various techniques described herein can be implemented in combination with hardware or software or in appropriate cases. Therefore, the method and apparatus of the subject matter currently disclosed or some aspects or parts thereof can take the form of program code (i.e., instructions) embodied in a tangible medium, such as a floppy disk, a CD-ROM, a hard drive or any other machine-readable storage medium, wherein when the program code is loaded into a machine such as a computing device and executed by the machine, the machine becomes a device for practicing the subject matter currently disclosed. In the case of program code execution on a programmable computer, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or storage element), at least one input device, and at least one output device. One or more programs can be implemented or utilized, for example, through the use of an application programming interface (API), a reusable control or the like, in combination with the process described in the subject matter currently disclosed. These programs can be implemented with high-level programs or object-oriented programming languages to communicate with a computer system. However, when necessary, the program can be implemented with assembly or machine language. In any case, the language may be a compiled or interpreted language and the language may be combined with hardware implementations.
[0363] Although this specification contains many specific implementation details, these should not be construed as limitations on the claims. Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented separately in multiple implementations or in any suitable sub-combination. Moreover, although features may be described above as functioning in certain combinations and even initially claimed, one or more features from the claimed combination may be excluded from the combination in some cases, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination.
[0364] Similarly, although operations are depicted in a particular order in the figures, this should not be construed as requiring that the operations be performed in the particular order shown or in a sequential order or that all illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the above-described embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.
[0365] It should be understood that the logical operations described herein with respect to the various figures may be implemented as: (1) a computer-implemented sequence of actions or program modules (i.e., software) running on a computing device, (2) interconnected machine logic circuits or circuit modules (i.e., hardware) within a computing device, and / or (3) a combination of software and hardware of a computing device. Therefore, the logical operations discussed herein are not limited to any specific combination of hardware and software. The implementation is a matter of choice depending on the performance and other requirements of the computing device. Therefore, the logical operations described herein are referred to in various ways as operations, structural devices, actions, or modules. These operations, structural devices, actions, and modules may be implemented in software, firmware, dedicated digital logic, and any combination thereof. It should also be understood that more or fewer operations may be performed than those shown in the figures and described herein. These operations may also be performed in a different order than those described herein. It will be apparent to those skilled in the art that various modifications and changes may be made without departing from the scope or spirit. Other embodiments will be apparent to those skilled in the art by consideration of the specification and practice disclosed herein. The specification and examples are intended to be considered exemplary only, with the true scope and spirit being indicated by the appended claims.
Claims
1. A method for securely transmitting data, comprising: preparing data containing glucose levels using a continuous glucose sensor unit; wirelessly transmitting said data related to said glucose level from a transmitter associated with said continuous glucose sensor unit to at least one display device; automatically forwarding said data related to said glucose level from said at least one display device to a cloud computing architecture; as well as The data related to the glucose level is stored in a separate group at the cloud computing architecture. 2 . The method of claim 1 , wherein the data related to the glucose level comprises measured glucose values and diagnostic data.
3. The method according to claim 1, further comprising: providing additional data by said at least one display device along with said data relating to said glucose level, Wherein said automatically forwarding said data comprises automatically forwarding said additional data and said data related to said glucose level.
4. The method according to claim 1, wherein: The data related to the glucose level includes a first data set and a second data set, and The storing the data related to the glucose level in a separate group includes storing the first set of data on a first server and storing the second set of data on a second server.
5. The method according to claim 4, wherein: the first set of data includes real-time data including one or more of a glucose value, a current state of the continuous glucose sensor unit, or a timestamp associated with a measurement taken to obtain the glucose value; and The second data set includes at least one of information for calibration of the continuous glucose sensor unit and information for technical support of the continuous glucose sensor unit.
6. The method according to claim 5, further comprising: encrypting, by the transmitter, the first set of data; encrypting, by the transmitter, the second set of data; decrypting and displaying the first data set by the at least one display device; preventing the at least one display device from decrypting the second set of data; as well as The second data set is decrypted by the cloud computing architecture.
7. The method according to claim 6, further comprising: storing, by the at least one display device, a first key for decrypting the first set of data; storing, by the cloud computing architecture, a second key for decrypting the second data set; as well as The at least one display device is prevented from accessing the second key.
8. The method according to claim 1, further comprising: A subset of the data related to the glucose level is forwarded from the cloud computing architecture to a second display device, the subset of data including at least one of current and past glucose levels.
9. The method according to claim 4, further comprising: A selective determination is made by the cloud computing architecture whether to grant access to the first set of data and the second set of data to one or more requesting systems.
10. The method of claim 9, wherein the requesting system comprises a technical support system, at least one third-party application, and a data warehouse, wherein the cloud computing architecture: granting the technical support system access to the first data set and the second data set; granting the at least one third-party application access to the first set of data; as well as The data warehouse is granted access to the first set of data and the second set of data.
11. The method of claim 1, wherein the display device comprises at least one of a smart phone, a tablet computer, a desktop computer, a laptop computer, a wearable display device.
12. A system for monitoring data related to analyte levels, comprising: a continuous glucose sensor unit configured to prepare data related to a glucose level, said continuous glucose sensor unit comprising a wireless transmitter configured to transmit said data related to said glucose level; at least one display device configured to receive said transmitted data related to said glucose level and automatically forward said data; A cloud computing architecture is configured to receive the automatically forwarded data and store the data related to the glucose level in a separate group.
13. The system of claim 12, wherein the data related to the glucose level comprises measured glucose values and diagnostic data.
14. The system of claim 12, wherein the at least one display device is further configured to: providing additional data along with said data related to said glucose level; and The additional data is automatically forwarded along with the data relating to the glucose level.
15. The system of claim 12, wherein the data related to the glucose level comprises a first data set and a second data set, and The cloud computing architecture is configured to store the first set of data solely on a first server and to store the second set of data solely on a second server.
16. The system of claim 15, wherein: the first set of data includes real-time data including one or more of a glucose value, a current state of the continuous glucose sensor unit, or a timestamp associated with a measurement taken to obtain the glucose value; and The second data set includes at least one of information for calibration of the continuous glucose sensor unit and information for technical support of the continuous glucose sensor unit.
17. The system of claim 16, wherein: The transmitter is further configured to encrypt the first set of data and the second set of data; The at least one display device is further configured to decrypt and display the first set of data; The at least one display device is unable to decrypt the second set of data; and The cloud computing architecture is further configured to decrypt the second set of data.
18. The system of claim 17, wherein: The at least one display device is further configured to store a first key for decrypting the first set of data; The cloud computing architecture is further configured to store a second key for decrypting the second set of data; and The at least one display device has no access to the second key.
19. The system of claim 12, wherein the cloud computing architecture is further configured to forward a subset of the data related to the glucose level to a second display device, the subset of data including at least one of current and past glucose levels.
20. The system of claim 15, wherein the cloud computing architecture is further configured to selectively determine whether to grant access to the first set of data and the second set of data to one or more requesting systems.
21. The system of claim 20, wherein the request system comprises a technical support system, at least one third-party application, and a data warehouse, wherein the cloud computing architecture is further configured to: granting the technical support system access to the first data set and the second data set; granting the at least one third-party application access to the first set of data; and The data warehouse is granted access to the first set of data and the second set of data.
22. The system of claim 12, wherein the at least one display device comprises at least one of a smart phone, a tablet computer, a desktop computer, a laptop computer, a wearable display device.
23. One or more computer readable media comprising instructions that, when executed by one or more processors, perform a method for securely transmitting data, the method comprising: preparing data related to glucose levels using a continuous glucose sensor unit; wirelessly transmitting said data related to said glucose level from a transmitter associated with said continuous glucose sensor unit to at least one display device; automatically forwarding said data related to said glucose level from said at least one display device to a cloud computing architecture; as well as The data related to the glucose level is stored in a separate group at the cloud computing architecture.
24. The computer readable medium of claim 23, wherein the data related to the glucose level comprises measured glucose values and diagnostic data.
25. The computer readable medium of claim 23, wherein the method further comprises: Additional data is provided by the at least one display device along with the data related to the glucose level, wherein automatically forwarding the data includes automatically forwarding the additional data along with the data related to the glucose level.
26. The computer-readable medium of claim 23, wherein: The data related to the glucose level includes a first data set and a second data set, and Storing the data related to the glucose level in separate groups includes separately storing, by the cloud computing architecture, the first set of data and the second set of data.
27. The computer-readable medium of claim 25, wherein: the first set of data includes real-time data including one or more of a glucose value, a current state of the continuous glucose sensor unit, or a timestamp associated with a measurement taken to obtain the glucose value; and The second data set includes at least one of information for calibration of the continuous glucose sensor unit and information for technical support of the continuous glucose sensor unit.
28. The computer readable medium of claim 27, wherein the method further comprises: encrypting, by the transmitter, the first set of data; encrypting, by the transmitter, the second set of data; decrypting and displaying the first data set by the at least one display device; preventing the at least one display device from decrypting the second set of data; as well as The second data set is decrypted by the cloud computing architecture.
29. The computer readable medium of claim 28, wherein the method further comprises: storing, by the at least one display device, a first key for decrypting the first set of data; storing, by the cloud computing architecture, a second key for decrypting the second data set; as well as The at least one display device is prevented from accessing the second key.
30. The computer readable medium of claim 23, wherein the method further comprises: A subset of the data related to the glucose level is forwarded from the cloud computing architecture to a second display device, the subset of data including at least one of current and past glucose levels.
31. The computer readable medium of claim 26, wherein the method further comprises: A selective determination is made by the cloud computing architecture whether to grant access to the first set of data and the second set of data to one or more requesting systems.
32. The computer-readable medium of claim 30, wherein the requesting system comprises a technical support system, at least one third-party application, and a data warehouse, wherein the cloud computing architecture: granting the technical support system access to the first data set and the second data set; granting the at least one third-party application access to the first set of data; as well as The data warehouse is granted access to the first set of data and the second set of data.
33. The computer-readable medium of claim 23, wherein the at least one display device comprises at least one of a smart phone, a tablet computer, a desktop computer, a laptop computer, a wearable display device.
34. A method for encrypting and transmitting data related to an analyte level, comprising: encrypting, by a transmitter associated with a continuous glucose monitor device, a first set of data; encrypting, by the transmitter, a second set of data; wirelessly transmitting the first set of data and the second set of data to at least one display device; decrypting the first set of data by the at least one display device; preventing the at least one display device from decrypting the second set of data; automatically forwarding the first set of data and the second set of data to a cloud computing infrastructure; as well as The second set of data is decrypted by the cloud computing infrastructure.
35. The method of claim 34, wherein: the first set of data includes real-time data including one or more of a glucose value, a current state of the continuous glucose monitor device, or a timestamp associated with a measurement taken to obtain the glucose value; and The second data set includes at least one of information for calibrating the continuous glucose monitor device and information for technical support of the continuous glucose monitor device.
36. The method of claim 34, wherein the transmitter uses an Advanced Encryption Standard when encrypting the first set of data and the second set of data.
37. The method of claim 34, further comprising: storing the first set of data on a first server in the cloud computing infrastructure; as well as The second set of data is stored on a second different server in the cloud computing infrastructure.
38. The method of claim 34, wherein the at least one display device comprises at least one of a smart phone, a tablet computer, or a wearable display device.
39. The method of claim 34, wherein automatically forwarding comprises forwarding the first set of data and the second set of data via a personal computer connected to the at least one display device, the connection comprising a wired or wireless connection.
40. A system for encrypting and transmitting data related to analyte levels, comprising: A continuous glucose monitor device comprising a transmitter configured to: encrypting the first data set and the second data set, and wirelessly transmitting the first set of data and the second set of data; At least one display device configured to: receiving the first data set and the second data set, decrypting the first data set, and automatically forwarding the first data set and the second data set; as well as A cloud computing infrastructure configured to: receiving the first set of data and the second set of data from the at least one display device, and The second set of data is decrypted, wherein the at least one display device is unable to decrypt the second set of data.
41. The system of claim 40, wherein: the first set of data includes real-time data including one or more of a glucose value, a current state of the continuous glucose monitor device, or a timestamp associated with a measurement taken to obtain the glucose value; and The second data set includes at least one of information for calibrating the continuous glucose monitor device and information for technical support of the continuous glucose monitor device.
42. The system of claim 40, wherein the transmitter uses an Advanced Encryption Standard when encrypting the first set of data and the second set of data.
43. The system of claim 40, further comprising: a first server in the cloud computing infrastructure, configured to store the first set of data; as well as A second server in the cloud computing infrastructure is configured to store the second set of data.
44. The system of claim 40, wherein the at least one display device comprises at least one of a smart phone, a tablet computer, or a wearable display device.
45. The system of claim 40, further comprising a personal computer configured to receive the first data set and the second data set from the at least one display device and forward the first data set and the second data set to the cloud computing infrastructure.
46. One or more computer readable media comprising instructions that, when executed by one or more processors, perform a method for encrypting and transmitting data related to an analyte level, the method comprising: encrypting, by a transmitter associated with a continuous glucose monitor device, a first set of data; encrypting, by the transmitter, a second set of data; wirelessly transmitting the first set of data and the second set of data to at least one display device; decrypting the first set of data by the at least one display device; preventing the at least one display device from decrypting the second set of data; automatically forwarding the first set of data and the second set of data to a cloud computing infrastructure; as well as The second set of data is decrypted by the cloud computing infrastructure.
47. The computer readable medium of claim 46, wherein: the first set of data includes real-time data including one or more of a glucose value, a current state of the continuous glucose monitor device, or a timestamp associated with a measurement taken to obtain the glucose value; and The second data set includes at least one of information for calibrating the continuous glucose monitor device and information for technical support of the continuous glucose monitor device.
48. The computer-readable medium of claim 46, wherein the transmitter uses the Advanced Encryption Standard when encrypting the first set of data and the second set of data.
49. The computer readable medium of claim 46, wherein the method further comprises: storing the first set of data on a first server in the cloud computing infrastructure; as well as The second set of data is stored on a second server in the cloud computing infrastructure.
50. The computer-readable medium of claim 46, wherein the at least one display device comprises at least one of a smart phone, a tablet computer, or a wearable display device.
51. The computer-readable medium of claim 46, wherein automatically forwarding comprises forwarding the first set of data and the second set of data via a personal computer connected to the at least one display device, the connection comprising a wired or wireless connection.
52. A method for controlling access to biomedical data, comprising: defining, at the cloud computing infrastructure, a plurality of rules for controlling access to data related to glucose levels; providing a plurality of application programming interfaces for accessing said data related to glucose levels; receiving, via at least one of the application programming interfaces, a request for the data related to glucose levels; determining whether to grant the request for the data related to glucose levels based on the plurality of rules and the request for the data; as well as Access to the data related to glucose levels is provided upon determining that access should be granted.
53. The method of claim 52, further comprising: receiving the request via a common application; as well as The request is provided to the cloud computing infrastructure, wherein providing access includes providing the data related to glucose levels to at least one of the application program interfaces through the common application.
54. The method of claim 53, further comprising providing a single sign-on including a username and password for the common application and multiple applications using the application program interface.
55. The method of claim 53, further comprising launching a web page interface from the common application in response to a request for an application using at least one of the application program interfaces.
56. The method of claim 55, further comprising: providing an icon for a second application in the common application; receiving a selection of the icon; directly accessing a server hosting the second application; as well as The result of accessing the server is executed in the common application.
57. The method of claim 52, further comprising: receiving, by the cloud computing infrastructure, a request for access by a second display device to the data related to glucose level; storing, by the cloud computing infrastructure, an anonymous identifier associated with the second display device; and The data related to glucose level is provided to the second display device.
58. A system for controlling access to biomedical data, comprising: one or more display devices including a plurality of application programming interfaces for accessing the data related to glucose levels, the display devices being configured to receive a request for the data related to glucose levels through at least one of the application programming interfaces; as well as A cloud computing infrastructure configured to: defining a plurality of rules for controlling access to data related to glucose levels, determining whether to grant the request for the data related to glucose levels based on the plurality of rules and the request for the data, and Access to the data related to glucose levels is provided upon determining that access should be granted.
59. The system of claim 58, further comprising: A common application executing on the one or more display devices is configured to receive the request and provide the request to the cloud computing infrastructure, wherein the cloud computing infrastructure provides access by providing the data related to glucose level to at least one of the application program interfaces through the common application.
60. The system of claim 59, wherein a single sign-on including a username and password accesses the common application and multiple applications using the application program interface.
61. The system of claim 59, wherein the one or more display devices are further configured to launch a web page interface from the common application in response to a request for an application using at least one of the application program interfaces.
62. The system of claim 61, wherein the one or more display devices are further configured to: providing an icon for a second application in the common application; receiving a selection of the icon; directly accessing a server hosting the second application; and The result of accessing the server is executed in the common application.
63. The system of claim 58, further comprising: a second display device configured to provide a request to the cloud computing infrastructure to access the data related to glucose levels, The cloud computing infrastructure is further configured to: storing an anonymous identifier associated with the second display device, and The data related to glucose level is provided to the second display device.
64. One or more computer readable media comprising instructions that, when executed by one or more processors, perform a method for controlling access to biomedical data, the method comprising: defining, at the cloud computing infrastructure, a plurality of rules for controlling access to data related to glucose levels; providing a plurality of application programming interfaces for accessing said data related to glucose levels; receiving, via at least one of the application programming interfaces, a request for the data related to glucose levels; determining whether to grant the request for the data related to glucose levels based on the plurality of rules and the request for the data; as well as Access to the data related to glucose levels is provided upon determining that access should be granted.
65. The computer readable medium of claim 64, wherein the method further comprises: receiving the request via a common application; as well as The request is provided to the cloud computing infrastructure, wherein providing access includes providing the data related to glucose levels to at least one of the application program interfaces through the common application.
66. The computer-readable medium of claim 65, wherein the method further comprises providing a single sign-on including a username and password for the common application and a plurality of applications using the application program interface.
67. The computer-readable medium of claim 65, wherein the method further comprises launching a web page interface from the common application in response to a request for an application using at least one of the application program interfaces.
68. The computer readable medium of claim 67, wherein the method further comprises: providing an icon for a second application in the common application; receiving a selection of the icon; directly accessing a server hosting the second application; as well as The result of accessing the server is executed in the common application.
69. The computer readable medium of claim 68, wherein the method further comprises: receiving, by the cloud computing infrastructure, a request for access by a second display device to the data related to glucose level; storing, by the cloud computing infrastructure, an anonymous identifier associated with the second display device; and The data related to glucose level is provided to the second display device.
70. A method for updating data in a distributed architecture, comprising: obtaining one or more data points related to glucose levels from a transmitter associated with a continuous glucose monitor device; distributing the one or more data points among one or more display devices and one or more servers; identifying a missing data point from a display device of the one or more display devices or a server of the one or more servers, the missing data point being one of the one or more data points; as well as The missing data points are provided to the display device or the server when the missing data points fall within a defined time period.
71. The method of claim 70, wherein the missing data points comprise backfilled data sent to the display device or server after the distribution.
72. The method of claim 70, comprising: identifying one or more missing data points from a display device of the one or more displays or a server of the one or more servers; as well as The one or more missing data points are provided to the display device or the server.
73. The method of claim 70, comprising: identifying one or more missing data points from a display device of the one or more displays or a server of the one or more servers; determining which of the one or more missing data points occurred within a subset of the defined time interval; as well as Those missing data points occurring within the subset of the defined time interval are provided.
74. The method of claim 72 or 73, further comprising: displaying the one or more data points and the missing data points; as well as Displaying the missing data points includes an indication of the backfilled data.
75. The method of claim 70, wherein the display device or the server that received the missing data point was turned off or disconnected when the missing data point was initially available.
76. The method of claim 70, comprising: identifying one or more missing data points from a display device of the one or more displays or a server of the one or more servers; determining a number of the lost data points to backfill based on the device that lost the data; as well as The determined number of missing data points is provided to the display device or server.
77. The method of claim 70, further comprising: Storing, by the one or more display devices or the one or more servers provided with the missing data points, an indication that the missing data points include the backfilled data.
78. The method of claim 70, further comprising: An indication that the one or more data points are received in real time is stored by the one or more display devices and the one or more servers.
79. The method of claim 70, further comprising: connecting a plurality of display devices to the transmitter; distributing the one or more data points to the plurality of display devices; as well as The one or more data points are forwarded from the plurality of display devices to the one or more servers along with an indication of which display device forwarded the data.
80. The method of claim 79, further comprising: receiving said one or more data points during said distribution of said plurality of data sets; as well as The one or more data points received during the distribution are displayed distinct from the missing data points.
81. The method of claim 70, wherein the defined time period includes the past six hours.
82. A system for updating data in a distributed architecture, comprising: a continuous glucose monitor device comprising a transmitter configured to obtain a plurality of sets of data related to glucose levels and to distribute the plurality of sets of data among one or more display devices and one or more servers; as well as (i) one or both of the one or more display devices and (ii) the one or more servers, wherein the one or more display devices and / or the one or more servers are configured to: identifying a missing data set from among the plurality of data sets, requesting the missing data set, and The lost data sets are received when the lost data sets fall within a defined time period.
83. The system of claim 82, wherein the missing data set comprises backfilled data sent to the one or more display devices or servers after the distribution.
84. The system of claim 82, wherein the one or more display devices and / or the one or more servers are configured to: Identify multiple missing data sets from the display device or server, requesting the plurality of missing data sets, and The plurality of missing data sets are received.
85. The system of claim 82, wherein the one or more display devices and / or the one or more servers are configured to: Identify multiple missing data sets, determining which of the plurality of missing data sets were generated within a subset of the defined time intervals, and Those missing data sets generated within the subset of the defined time interval are requested.
86. The system of claim 85, wherein the one or more display devices are configured to: displaying the plurality of data sets and the missing data sets, and An indication is displayed that the missing data set includes backfilled data.
87. The system of claim 82, wherein the one or more display devices and / or the one or more servers that received the lost data set were turned off or disconnected when the lost data set was initially available.
88. The system of claim 82, wherein: identifying a plurality of missing data sets from among the one or more display devices and / or the one or more servers; determining a number of the lost data sets to backfill based on the device that lost the data; as well as The determined number of lost data sets is provided to the display device or the server.
89. The system of claim 82, wherein the one or more display devices and / or the one or more servers to which the missing data set is provided are configured to store an indication that the missing data set includes backfilled data.
90. The system of claim 89, wherein the one or more display devices and / or the one or more servers store an indication that the plurality of data sets are received in real time.
91. The system of claim 82, further comprising a plurality of display devices in communication with the transmitter, wherein: distributing the plurality of data sets to the plurality of display devices; as well as The plurality of data sets are forwarded from the plurality of display devices to the one or more servers along with an indication of which display device forwarded the data set.
92. The system of claim 82, wherein: The plurality of data sets are received during the distribution of the plurality of data sets; and The plurality of data sets received during the distribution are displayed differently from the lost data sets.
93. The system of claim 82, wherein the defined time period includes the past six hours.
94. One or more computer readable media comprising instructions that, when executed by one or more processors, perform a method for updating data in a distributed architecture, the method comprising: obtaining a plurality of data sets related to glucose levels from a transmitter associated with a continuous glucose monitor device; distributing the plurality of data sets among one or more display devices and one or more servers; identifying a missing data set from a display device of the one or more display devices or a server of the one or more servers, the missing data set being one of the plurality of data sets; as well as The missing sets of data are provided to the display device or server when the missing sets of data fall within a defined time period.
95. The computer-readable medium of claim 94, wherein the set of missing data comprises backfilled data sent to the display device or server after the distribution.
96. The computer readable medium of claim 94, wherein the method comprises: identifying a plurality of missing data sets from a display device of the one or more display devices or a server of the one or more servers; as well as The plurality of missing data sets are provided to the display device or the server.
97. The computer readable medium of claim 94, wherein the method comprises: identifying a plurality of missing data sets from a display device of the one or more display devices or a server of the one or more servers; determining which of the plurality of missing data sets were generated within a subset of the defined time intervals; as well as Those missing data sets generated within the subset of the defined time intervals are provided.
98. The computer readable medium of claim 96 or 97, wherein the method further comprises: displaying the plurality of data sets and the missing data sets; as well as An indication is displayed that the missing data set includes backfilled data.
99. The computer-readable medium of claim 94, wherein the display device or the server that received the missing data set was turned off or disconnected when the missing data set was initially available.
100. The computer readable medium of claim 95, wherein the method comprises: identifying a plurality of missing data sets from a display device of the one or more display devices or a server of the one or more servers; determining a number of the lost data sets to backfill based on the device that lost the data; as well as The determined number of missing data sets is provided to the display device or server.
101. The computer readable medium of claim 100, wherein the method further comprises: An indication that the missing data set includes the backfilled data is stored by the one or more display devices or the one or more servers to which the missing data set is provided.
102. The computer readable medium of claim 101, wherein the method further comprises: An indication that the plurality of data sets are received in real time is stored by the one or more display devices and the one or more servers.
103. The computer readable medium of claim 94, wherein the method further comprises: connecting a plurality of display devices to the transmitter; distributing the plurality of data sets to the plurality of display devices; as well as The plurality of data sets are forwarded from the plurality of display devices to the one or more servers along with an indication of which display device forwarded the data set.
104. The computer readable medium of claim 94, wherein the method further comprises: receiving said plurality of data sets during said distribution of said plurality of data sets; as well as The plurality of data sets received during the distribution are displayed distinct from the lost data sets.
105. The computer-readable medium of claim 94, wherein the defined time period includes the past six hours.
106. A method for synchronizing data in a distributed architecture system, comprising: providing a plurality of data sets related to glucose levels from a transmitter associated with the continuous glucose monitor device to a first display device and a second display device; providing the plurality of data sets from the first display device and the second display device to a server; as well as The plurality of data sets are separately stored by the server based on whether the plurality of data sets are received from the first display device or the second display device.
107. The method of claim 106, further comprising: marking, by the first display device, the plurality of data sets as having been received by the first display device; as well as The plurality of data sets are marked, by the second display device, as having been received by the second display device.
108. The method of claim 106, further comprising: generating a first alert on the first display device when the glucose level reaches a first defined level or undergoes a first rate of change; as well as A second alert is generated on the second display device when the glucose level reaches a second defined level or experiences a second rate of change.
109. The method of claim 106, further comprising: configuring when to provide the plurality of data sets from the first display device to the server; as well as Configuring when the plurality of data sets are provided from the second display device to the server.
110. The method of claim 106, wherein the server comprises a distributed cloud computing system comprising a plurality of connected computing devices.
111. A system for synchronizing data in a distributed architecture system, comprising: a transmitter associated with a continuous glucose monitor device configured to provide a plurality of data sets related to glucose levels; a first display device and a second display device configured to receive the plurality of data sets and provide the plurality of data sets; as well as The server is configured to receive the plurality of data sets and separately store the plurality of data sets based on whether the plurality of data sets are received from the first display device or the second display device.
112. The system of claim 111, wherein: The first display device is configured to mark the plurality of data sets as having been received by the first display device; and The second display device is configured to mark the plurality of data sets as having been received by the second display device.
113. The system of claim 111, wherein: The first display device is configured to provide a first alert when the glucose level reaches a first defined level or undergoes a first rate of change; and The second display device is configured to provide a second alert for when the glucose level reaches a second defined level or experiences a second rate of change.
114. The system of claim 111, wherein: The first display device is configured to provide the plurality of data sets to the server at a first defined time; and The second display device is configured to provide the plurality of data sets to the server at a second defined time.
115. The system of claim 111, wherein the server comprises a distributed cloud computing system comprising a plurality of connected computing devices.
116. One or more computer readable media comprising instructions that, when executed by one or more processors, perform a method for synchronizing data in a distributed architecture system, the method comprising: providing a plurality of data sets related to glucose levels from a transmitter associated with the continuous glucose monitor device to a first display device and a second display device; providing the plurality of data sets from the first display device and the second display device to a server; as well as The plurality of data sets are separately stored by the server based on whether the plurality of data sets are received from the first display device or the second display device.
117. The computer readable medium of claim 116, wherein the method further comprises: marking, by the first display device, the plurality of data sets as having been received by the first display device; as well as The plurality of data sets are marked, by the second display device, as having been received by the second display device.
118. The computer readable medium of claim 116, wherein the method further comprises: generating a first alert on the first display device when the glucose level reaches a first defined level or undergoes a first rate of change; as well as A second alert is generated on the second display device when the glucose level reaches a second defined level or experiences a second rate of change.
119. The computer readable medium of claim 116, wherein the method further comprises: configuring when to provide the plurality of data sets from the first display device to the server; as well as Configuring when the plurality of data sets are provided from the second display device to the server.
120. The computer-readable medium of claim 116, wherein the server comprises a distributed cloud computing system comprising a plurality of connected computing devices.
121. A system for securely collecting, analyzing, and reporting data related to glucose monitoring levels via a plurality of continuous glucose monitors, the system comprising: multiple continuous glucose monitor (CGM) devices; a plurality of display devices that receive data from the plurality of CGM devices, wherein the data is categorized into a plurality of categories based on data type; a cloud server architecture comprising a plurality of servers that receive said data from said plurality of display devices on an intermittent basis, wherein said data routed to a particular server of said plurality of servers is determined by said data type, and wherein said intermittent basis varies depending on said data type; a plurality of remote monitor display devices that receive data from at least one of the plurality of servers, wherein the data sent to each of the plurality of remote monitor display devices depends on the type of data and on the display device that transmitted the data to the at least one of the plurality of servers, and the data is sent to the plurality of remote monitor display devices immediately upon receipt by the at least one of the plurality of servers; as well as An analysis and reporting engine, wherein at least a portion of the data received by the plurality of servers is transmitted to the analysis and reporting engine, and wherein the transmitted data is configured to be analyzed by the analysis and reporting engine, and a report is configured to be generated by the analysis and reporting engine.
122. The system of claim 121, wherein the data types include real-time data and batch data.
123. A system according to claim 121 or 122, wherein the multiple servers of the cloud server architecture include at least a real-time server and a batch data collector.
124. The system of claim 123, wherein the real-time data is routed from the plurality of display devices to the real-time server, and the batch data is routed from the plurality of display devices to the batch data collector.
125. The system of claim 124, wherein the real-time data is routed from the plurality of display devices to the real-time server on an intermittent basis more frequently than the batch data is routed from the plurality of display devices to the batch data collector on an intermittent basis.
126. The system of claim 125, wherein the real-time data is routed from the plurality of display devices to the real-time server once every five minutes, and the batch data is routed from the plurality of display devices to the batch data collector once every hour.
127. The system of any one of claims 121 to 126, further comprising a locator service, wherein the plurality of display devices are connected to the cloud server architecture via the locator service.
128. The system of any one of claims 121-127, wherein at least one of the plurality of display devices comprises a smart phone, a tablet computer, a desktop computer, a laptop computer, or a wearable display device.
129. The system of any one of claims 121-128, wherein at least one of the plurality of remote monitor display devices comprises a smart phone, a tablet computer, a desktop computer, a laptop computer, or a wearable display device.
130. The system of any one of Claims 121-129, wherein the plurality of display devices comprises at least 150,000 devices.
131. The system of any one of claims 121 to 130, wherein at least one of the plurality of remote monitor display devices further comprises an application executable by the at least one of the plurality of remote monitor display devices.
132. A system according to claim 131, wherein the application on the at least one of the multiple remote monitor display devices must be open and running in order to receive the data ready to be sent to the at least one of the multiple remote monitor display devices, otherwise the data ready to be sent to the at least one of the multiple remote monitor display devices is maintained by one of the multiple servers.
133. A system according to any one of claims 121 to 132, wherein at least one of the plurality of remote monitor display devices that receives data from one of the plurality of servers receives a notification that data is ready to be sent to the at least one of the plurality of remote monitor display devices.
134. The system of claim 133, wherein the notification comprises a text message.
135. A system according to claim 131, wherein the application executable by the at least one of the multiple remote display devices wakes up when the one of the multiple servers attempts to send the data to the at least one of the multiple remote display devices.
136. The system of claim 135, wherein the application requests that the data be sent from the one of the plurality of servers after the application wakes up.
137. A method for securely collecting, analyzing, and reporting data related to glucose monitoring levels via a plurality of continuous glucose monitors, the method comprising: receiving data from a plurality of continuous glucose monitor (CGM) devices by a plurality of display devices; classifying the data into a plurality of categories based on data type; transmitting the data from the plurality of display devices to a cloud server architecture including a plurality of servers that receive the data from the plurality of display devices on an intermittent basis, wherein routing of the data to a particular server among the plurality of servers is determined by the type of data, and wherein the intermittent basis varies depending on the type of data; receiving, by a plurality of remote monitor display devices, data from at least one of the plurality of servers, wherein the data sent to each of the plurality of remote monitor display devices depends on the type of data and on the display device that transmitted the data to the at least one of the plurality of servers, and the data is sent to the plurality of remote monitor display devices immediately upon receipt by the at least one of the plurality of servers; as well as At least a portion of the data received by the plurality of servers is received by an analysis and reporting engine configured to analyze the received data and generate a report.
138. The method of claim 137, wherein classifying the data into a plurality of categories based on data type comprises classifying the data into real-time data and batch data.
139. A method according to claim 137 or 138, wherein the multiple servers of the cloud server architecture include at least a real-time server and a batch data collector.
140. The method of claim 139, wherein the real-time data is routed from the plurality of display devices to the real-time server and the batch data is routed from the plurality of display devices to the batch data collector.
141. The method of claim 140, wherein the real-time data is routed from the plurality of display devices to the real-time server on an intermittent basis more frequently than the batch data is routed from the plurality of display devices to the batch data collector on an intermittent basis.
142. The method of claim 141, wherein the real-time data is routed from the plurality of display devices to the real-time server once every five minutes, and the batch data is routed from the plurality of display devices to the batch data collector once an hour.
143. The method of any one of claims 137-142, further comprising a locator service, wherein the plurality of display devices are connected to the cloud server architecture through the locator service.
144. The method of any one of claims 137-143, wherein at least one of the plurality of display devices comprises a smart phone, a tablet computer, a desktop computer, a laptop computer, or a wearable display device.
145. The method of any one of claims 137-144, wherein at least one of the plurality of remote monitor display devices comprises a smart phone, a tablet computer, a desktop computer, a laptop computer, or a wearable display device.
146. The method of any one of Claims 137-145, wherein the plurality of display devices comprises at least 150,000 devices.
147. The method of any one of claims 137 to 146, wherein at least one of the plurality of remote monitor display devices further comprises an application executable by the at least one of the plurality of remote monitor display devices.
148. A method according to claim 147, wherein the application on the at least one of the multiple remote monitor display devices must be open and running in order to receive the data ready to be sent to the at least one of the multiple remote monitor display devices, otherwise the data ready to be sent to the at least one of the multiple remote monitor display devices is maintained by one of the multiple servers.
149. A method according to any one of claims 137 to 148, wherein at least one of the plurality of remote monitor display devices that receives data from one of the plurality of servers receives a notification that data is ready to be sent to the at least one of the plurality of remote monitor display devices.
150. The method of claim 149, wherein the notification comprises a text message.
151. The method of claim 147, wherein the application executable by the at least one of the plurality of remote display devices wakes up when the one of the plurality of servers attempts to send the data to the at least one of the plurality of remote display devices.
152. The method of claim 151, wherein the application requests that the data be sent from the one of the plurality of servers after the application wakes up.
