Electronic device and method for managing blood glucose data thereof

Abstract

The present invention aims to provide an electronic device and a method for managing its blood glucose data. Specifically, it provides a method for detecting the detachment of a blood glucose sensor based on a blood glucose pattern and for managing the blood glucose data acquired from the detached sensor. [Solution] A method for managing blood glucose data in an electronic device is provided, comprising the steps of: confirming first blood glucose data based on a blood glucose sensor; confirming a validation dataset corresponding to the first blood glucose data; estimating whether at least some of the blood glucose sensors have fallen off the user's body based on a comparison between a pattern corresponding to the validation dataset and a reference pattern; and, if the detachment is estimated, delaying the output of the first blood glucose data to the user.

Description

[Technical Field]

[0001] The present disclosure relates to an electronic device and a blood glucose data management method thereof {ELECTRONIC DEVICE AND BLOOD GLUCOSE DATA MANAGEMENT METHOD THEREOF}. [Background Art]

[0002] A Continuous Glucose Monitoring System (CGMS) is a device that monitors changes in blood glucose of diabetic patients in real time, and has been widely used in recent years due to the convenience that it can measure glucose concentration in subcutaneous interstitial fluid through a percutaneously inserted sensor without requiring the patient to collect blood.

[0003] Although CGMS has many advantages as described above, one of its disadvantages is that if the attachment state of the blood glucose sensor is unstable or the sensor detaches from the patient's skin, the blood glucose measurement value may be distorted or generate unreliable data. This may lead to incorrect treatment decisions and impair patient safety.

[0004] Therefore, reliably detecting whether a sensor has fallen off is extremely important. However, since sensor detachment often occurs without clear physical symptoms, there is a limitation that it is difficult to detect only by a simple inspection of the attachment state.

[0005] Further, due to the characteristic of CGMS that continuously measures blood glucose, a function for statistically managing blood glucose measurement values is basically provided and is recognized as an important function for users. In this aspect, the problem of how to statistically process and manage data obtained from a detached sensor is an important issue that can be considered to improve user experience. Nevertheless, discussions on this matter have not yet been sufficiently conducted. [Summary of the Invention] [Problems that the invention aims to solve]

[0006] The disclosed embodiments aim to provide an electronic device and a method for managing blood glucose data thereof. Specifically, one objective is to provide a method for detecting the detachment of a blood glucose sensor based on a blood glucose pattern and for managing blood glucose data acquired from the detached sensor.

[0007] The technical problems that this embodiment aims to solve are not limited to those described above, and other technical problems can be inferred from the following embodiments. [Means for solving the problem]

[0008] One aspect of this disclosure is a method for managing blood glucose data in an electronic device, comprising the steps of: confirming first blood glucose data based on a blood glucose sensor; confirming a validation dataset corresponding to the first blood glucose data; estimating whether at least some of the blood glucose sensors have fallen off the user's body based on a comparison between a pattern corresponding to the validation dataset and a reference pattern; and, if such detachment is estimated, delaying the output of the first blood glucose data to the user.

[0009] A method for managing blood glucose data, comprising the step of periodically checking blood glucose data based on a blood glucose sensor inserted transcutaneously into the user's body, prior to the step of checking first blood glucose data based on the blood glucose sensor, wherein the first blood glucose data is measured by the blood glucose sensor in the next measurement cycle following the periodically checked blood glucose data.

[0010] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising the steps of: confirming a validation dataset corresponding to the first blood glucose data; confirming at least one preceding blood glucose data in a sequence of blood glucose measurement that is consecutive to the first blood glucose data; and confirming the validation dataset containing the first blood glucose data and the at least one preceding blood glucose data arranged in chronological order.

[0011] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising the steps of: estimating whether at least some of the blood glucose sensors are missing; checking a plurality of time-series arranged blood glucose data included in the verification dataset; checking whether the pattern of the plurality of blood glucose data corresponds to at least one of the first and second reference patterns included in the reference pattern; and, if the pattern of the plurality of blood glucose data corresponds to at least one of the first and second reference patterns, estimating the absence of at least some of the blood glucose sensors.

[0012] Furthermore, in one embodiment of the present disclosure, the first reference pattern includes a method for managing blood glucose data in which, among the plurality of blood glucose data, the second blood glucose data is lower than the first critical value or more compared to the first blood glucose data, in two consecutive blood glucose measurement sequences.

[0013] Furthermore, in one embodiment of the present disclosure, the method for managing blood glucose data further includes a pattern in which the first reference pattern is such that, among the plurality of blood glucose data, the slope between two blood glucose data for which the order of blood glucose measurement is further later than that of the preceding blood glucose data is 0 or less.

[0014] Furthermore, in one embodiment of the present disclosure, the second reference pattern includes a pattern in which at least one of the plurality of blood glucose data is below a second critical value, a method for managing blood glucose data.

[0015] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, wherein the step of estimating whether or not at least some of the blood glucose sensors have fallen out includes the step of adjusting at least one critical value related to the reference pattern based on the user's medical history information.

[0016] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising the steps of adjusting at least one critical value associated with the reference pattern, confirming the medical history information indicating that the user has a predisposition to type 1 diabetes; and adjusting the order of two consecutive blood glucose data sets such that the first critical value of the first reference pattern increases, relating to the decrease in the subsequent blood glucose data set relative to the preceding blood glucose data set.

[0017] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising the steps of adjusting at least one critical value associated with the reference pattern, confirming the medical history information indicating that the user has a history of hypoglycemic shock; and adjusting the second critical value of the second reference pattern to decrease, which is associated with the magnitude of at least one blood glucose data among a plurality of blood glucose data included in the validation dataset.

[0018] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising the steps of: confirming a second blood glucose data that has increased compared to the first blood glucose data based on the blood glucose sensor; releasing the grace period for outputting the first blood glucose data; and outputting the first blood glucose data to the user in a normal manner.

[0019] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data further includes, based on the blood glucose sensor, a step of checking a flag associated with compression noise set for the first blood glucose data, before the step of checking a second blood glucose data which has increased compared to the first blood glucose data, and after the step of delaying the output of the first blood glucose data to the user; and a step of controlling the blood glucose sensor so that the second blood glucose data is measured earlier than the basic cycle, wherein the step of outputting the first blood glucose data to the user includes a step of outputting a notification associated with compression noise to the user.

[0020] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data further comprising the steps of: confirming whether the number of blood glucose data for which output has been continuously deferred corresponds to a number of first criteria; and, if the number of blood glucose data for which output has been continuously deferred corresponds to the number of first criteria, disconnecting the connection with the blood glucose sensor.

[0021] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising the steps of: confirming a new blood glucose sensor that replaces the blood glucose sensor by disconnecting the connection with the blood glucose sensor; confirming blood glucose data based on the new blood glucose sensor; confirming estimated blood glucose data for at least a portion of the continuously deferred output blood glucose data by performing interpolation or extrapolation calculations using the blood glucose data confirmed based on the new blood glucose sensor; and outputting the estimated blood glucose data to the user.

[0022] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data further includes the step of outputting a notification to the user related to the detachment of a sensor.

[0023] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising the steps of: outputting a notification related to the detachment of the sensor to the user; checking the user's parental terminal; and outputting a notification related to the detachment of the sensor to the parental terminal.

[0024] Furthermore, in one embodiment of the present disclosure, a method for managing blood glucose data wherein the notification related to the detachment of the sensor differs from at least some of the measurement notifications, hypoglycemia notifications, and hyperglycemia notifications of the blood glucose sensor in terms of sound volume, vibration volume, and notification form.

[0025] Further, in one embodiment of the present disclosure, a method for managing blood glucose data, comprising: confirming a request for outputting a blood glucose graph from the user; deactivating a portion corresponding to blood glucose data whose output is postponed, including the first blood glucose data, on the blood glucose graph; and outputting, to the user, the blood glucose graph in which the portion corresponding to the blood glucose data whose output is postponed has been deactivated, wherein the deactivation includes at least one of blurring processing for a point on the blood glucose graph, non-response processing upon clicking, and display processing related to output postponement.

[0026] Another aspect of the present disclosure provides an electronic device for managing blood glucose data, comprising: a processor; and a memory storing one or more instructions, wherein the processor executes the one or more instructions to: confirm first blood glucose data based on a blood glucose sensor; confirm a verification data set corresponding to the first blood glucose data; estimate detachment of at least a portion of the blood glucose sensor from a user's body based on a comparison between a pattern corresponding to the verification data set and a reference pattern; and when the detachment is estimated, the electronic device is configured to postpone outputting the first blood glucose data to the user.

[0027] Still another aspect of the present disclosure provides a computer-readable non-transitory storage medium having recorded thereon a program for causing a computer to execute the aforementioned blood glucose data management method.

[0028] Specific details of other embodiments are included in the detailed description and the accompanying drawings.

Effects of the Invention

[0029] According to the proposed embodiment, one or more of the following effects can be expected.

[0030] According to the embodiment of the present specification, detachment of a blood glucose sensor can be detected based on a blood glucose pattern.

[0031] Furthermore, according to the embodiments of this specification, blood glucose data acquired from a detached sensor can be managed.

[0032] Furthermore, according to the embodiments of this specification, the user can be notified of the blood glucose sensor's detachment in a variety of ways.

[0033] The effects of this disclosure are not limited to those mentioned above, and any other effects not mentioned can be clearly understood by those skilled in the art from the description of the claims. [Brief explanation of the drawing]

[0034] [Figure 1] This diagram shows the relationship between an electronic device for managing blood glucose data, a blood glucose sensor, a server, and a parental control terminal according to one embodiment. [Figure 2] This is a flowchart illustrating a method for managing blood glucose data according to one embodiment. [Figure 3a] This figure shows an example where the patterns in the validation dataset correspond to the first criterion pattern. [Figure 3b] This figure shows another example where the patterns in the validation dataset correspond to the first criterion pattern. [Figure 3c] This figure illustrates an example where the patterns in the validation dataset do not correspond to the first criterion pattern. [Figure 4a] This figure shows an example of how a notification related to the detachment of a sensor according to one embodiment is displayed through a notification window. [Figure 4b] This figure shows an example of how a notification related to the detachment of a sensor according to one embodiment is displayed via a banner. [Figure 5a] This figure shows another example in which a notification related to the detachment of a sensor according to one embodiment is displayed through a notification window. [Figure 5b] This figure shows another example in which a notification related to the detachment of a sensor according to one embodiment is displayed via a banner. [Figure 6a]This is an illustrative diagram of a blood glucose graph in which blood glucose data whose output has been delayed according to one embodiment has been deactivated. [Figure 6b] This is an illustrative diagram showing the UI when blood glucose data that has been deferred for output according to one embodiment is clicked after being inactive. [Figure 7] A block diagram of an electronic device according to one embodiment is shown. [Modes for carrying out the invention]

[0035] The terminology used in the embodiments has been selected to the greatest extent possible to be the most widely used and common terminology, taking into account the function described herein, although this may change depending on the intent of the articulators, case law, the emergence of new technologies, etc. In certain cases, the applicant may have arbitrarily selected some terms, in which case their meaning will be described in detail in the relevant sections of the description. Therefore, the terminology used in this disclosure must be defined not merely as a name of a term, but based on the meaning of that term and the overall content of this disclosure.

[0036] When a part of the specification is described as "including" a certain component, unless otherwise stated, this means that it may include other components rather than excluding them.

[0037] The expression “at least one of a, b, and c” as described throughout the specification may encompass “a alone,” “b alone,” “c alone,” “a and b,” “a and c,” “b and c,” or “all of a, b, and c.”

[0038] The term "terminal" as used below can be embodied as a computer or portable terminal that can connect to servers or other terminals via a network. Here, a computer includes, for example, a laptop, desktop, or laptop computer equipped with a web browser, while a portable terminal can include, for example, all types of handheld-based wireless communication devices such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), smartphones, and tablet PCs, as long as portability and mobility are guaranteed.

[0039] The embodiments of this disclosure will be described in detail below, with reference to the attached drawings, so that they can be easily implemented by a person with ordinary skill in the art to which this disclosure pertains. However, this disclosure can be embodied in several different forms and is not limited to the embodiments described herein.

[0040] The embodiments of this disclosure will be described in detail below with reference to the drawings.

[0041] Figure 1 shows the relationship between an electronic device for managing blood glucose data, a blood glucose sensor, a server, and a parental control terminal according to one embodiment.

[0042] Referring to Figure 1, the electronic device 100 can operate in conjunction with the blood glucose sensor 200, the server 300, and the parent terminal 400. On the other hand, Figure 1 only shows the components related to this embodiment. Therefore, a person with ordinary skill in the art related to this embodiment will understand that in addition to the components shown in Figure 1, other general-purpose components may be included.

[0043] The electronic device 100 is a device that configures and provides diverse information. The electronic device 100 can provide the configured information as a web page or application screen, or as information that can be displayed on a receiving terminal as a web page or application screen. According to one embodiment, the electronic device 100 may be compatible with a personal mobile device carried by the user, such as a smartphone or tablet, but is not limited to this. Such an electronic device 100 may be connected to a blood glucose sensor 200 by a wired or wireless communication method. It may also be connected to a server 300 and a guardian terminal 400 via a network.

[0044] The blood glucose sensor 200 can be inserted transcutaneously into the user's body to measure the glucose concentration in the user's interstitial fluid. For example, the blood glucose sensor 200 may include a microelectrode and an enzyme layer that are inserted transcutaneously into the user's body, and the glucose concentration in the interstitial fluid can be indirectly measured by sensing the flow of electrons, i.e., the current value, resulting from the chemical reaction of glucose oxidase occurring in the enzyme layer, as biological data through the microelectrode. However, the blood glucose sensor is not limited to operating by such a principle, and any method of sensor capable of measuring the glucose concentration in the interstitial fluid is applicable to the blood glucose sensor 200 of this disclosure. When the blood glucose sensor 200 operates in the manner described above, the blood glucose sensor 200 is connected to the electronic device 100 by a wired or wireless communication method, as described above, and can transmit periodically measured biological data to the electronic device 100. According to one embodiment, the electronic device 100 can calculate blood glucose data by processing such biological data. For example, the electronic device 100 can perform the above-mentioned calculations based on the mapping relationship between biological data and blood glucose data, but is not limited to this. In the following description, detachment of at least a portion of the blood glucose sensor 200 may mean that all or part of the portion that must be inserted transcutaneously into the user's body detaches and comes into contact with air.

[0045] According to one embodiment, the blood glucose sensor 200 aggregates multiple biometric data measured at short intervals, i.e., current values, and transmits them to the electronic device 100 as a value for a larger period including the short intervals. The electronic device 100 can then confirm the blood glucose data for the larger period based on the transmitted value. For example, the blood glucose sensor 200 can measure biometric data every 10 seconds and transmit the biometric data measured every 10 seconds to the electronic device 100 in 5-minute increments. The electronic device 100 can then calculate the blood glucose data for the corresponding 5-minute period based on the average value of the biometric data measured every 10 seconds or a variety of representative values ​​that can be determined by other means. Of course, the method of measuring blood glucose data is not limited to the above description. For example, after the current value is measured, the blood glucose sensor 200 itself may calculate and derive the blood glucose data, which may then be transmitted to the electronic device 100. Various methods other than those described above in which the electronic device 100 measures blood glucose data based on the blood glucose sensor 200 may be included in this disclosure.

[0046] The server 300 is connected to the electronic device 100 via a network and can perform operations such as long-term backup of the user's blood glucose data collected by the electronic device 100 and providing the backed-up historical blood glucose data to the electronic device 100.

[0047] The parental device 400 is a device belonging to a person designated as the user's parent or guardian, and may, but is not limited to, personal mobile devices such as smartphones and tablets. The parental device 400 may be connected to the electronic device 100 and the server 300 via a network.

[0048] The following describes a method for managing blood glucose data according to one embodiment of this disclosure.

[0049] Figure 2 is a flowchart illustrating a method for managing blood glucose data according to one embodiment.

[0050] In stage S210, the electronic device 100 can verify the first blood glucose data based on the blood glucose sensor 200. In stage S220, the electronic device 100 can verify the validation dataset corresponding to the first blood glucose data. In stage S230, the electronic device 100 can estimate the detachment of at least some of the blood glucose sensors 200 from the user's body based on a comparison between the pattern corresponding to the validation dataset and the reference pattern. In stage S240, if detachment is estimated, the electronic device 100 can delay outputting the first blood glucose data to the user. The following will provide a detailed explanation of each stage.

[0051] First, the electronic device 100 can confirm the first blood glucose data based on the blood glucose sensor 200. As mentioned above, the blood glucose sensor 200 can periodically measure the user's biological data while it is inserted transcutaneously into the user's body. An example of biological data is the current value flowing through a microelectrode inserted transcutaneously into the user's body. Once the biological data is measured in this way, the electronic device 100 can calculate the blood glucose data by processing the biological data. As an example, the electronic device 100 can perform the aforementioned calculation based on the mapping relationship between the biological data and the blood glucose data, but is not limited to this. According to one embodiment, the first blood glucose data may correspond to the data measured by the blood glucose sensor 200 in the next confirmation cycle of the blood glucose data confirmed based on the biological data measured periodically by the blood glucose sensor 200. As an example, the first blood glucose data may correspond to the most recent blood glucose data among the blood glucose data periodically measured by the blood glucose sensor 200. According to other embodiments, the first blood glucose data may correspond to any one of the historically measured blood glucose data. However, for the sake of explanation, the above-mentioned embodiment, i.e., the embodiment in which the first blood glucose data corresponds to the most recent blood glucose data, will be used as the basis for the following explanation. However, the following explanation may also apply when the first blood glucose data corresponds to any one of the historically measured blood glucose data.

[0052] According to one embodiment, the electronic device 100 can verify a validation dataset corresponding to the first blood glucose data. The validation dataset may correspond to a set containing a certain number of consecutive blood glucose data that can verify the pattern of the blood glucose data. The validation dataset corresponding to the first blood glucose data may include the first blood glucose data and at least one preceding blood glucose data that is consecutive in the order of blood glucose measurement, arranged in chronological order. For example, if the system is set to measure blood glucose data at 5-minute intervals, the validation dataset for the first blood glucose data measured at 13:30 on January 1, 2025 may include the first blood glucose data along with blood glucose data measured at 13:25, 13:20, and 13:15 on the same day, arranged in chronological order. The number of blood glucose data included in the validation dataset may be set statically or dynamically. Below, we will describe one embodiment in which the number of blood glucose data included in the validation dataset is set dynamically.

[0053] According to one embodiment, the electronic device 100 can set the number of data points in the validation dataset inversely proportional to the magnitude of the blood glucose level indicated by the first blood glucose data. For example, the electronic device 100 can be set so that when the magnitude of the blood glucose level indicated by the first blood glucose data is small, the number of data points included in the validation dataset increases. Such an embodiment has the advantage of being somewhat conservative and allowing for careful access based on more data to distinguish when the magnitude of the blood glucose level indicated by the first blood glucose data is small from actual hypoglycemia.

[0054] According to one embodiment, the verification dataset may also include, in addition to the multiple blood glucose data mentioned above, error history information, operational history information, and specification information of the blood glucose sensor 200. This can be applied to embodiments in which the critical values ​​for each reference pattern described later are partially adjusted based on such information.

[0055] According to one embodiment, the electronic device 100 can verify a plurality of time-series-arranged blood glucose data included in the validation dataset. The electronic device 100 can then determine whether the pattern of the plurality of blood glucose data corresponds to at least one of the first and second reference patterns included in the reference pattern. If the pattern of the plurality of blood glucose data corresponds to at least one of the first and second reference patterns, the electronic device 100 can estimate the absence of at least some of the blood glucose sensors 200. The first reference pattern may relate to the relative magnitudes between the blood glucose data, and the second reference pattern may relate to the absolute magnitudes of the blood glucose data. First, we will explain the first reference pattern.

[0056] For example, if some of the blood glucose sensors fall off, the sensor may fail to react due to a lack of glucose in the air, or current may not flow to the microelectrode due to the much higher electrical resistance of air compared to interstitial fluid, potentially leading to an excessively low measurement of blood glucose data. Focusing on such cases, according to one embodiment, the first reference pattern may include a pattern in which, among several blood glucose data, two consecutive blood glucose measurements show a decrease of more than a first critical value compared to the preceding blood glucose data. An example of the first critical value may correspond to a decrease in blood glucose not commonly observed even in diabetic patients, for example, a value of around 150 mg / dL, but is not limited to such a value.

[0057] For example, if some of the blood glucose sensors fall out, as mentioned above, it can be predicted that blood glucose data will not be measured again after an excessively low reading has been obtained. Focusing on such cases, according to one embodiment, the first reference pattern may further include a pattern in which the slope between two blood glucose data points, where the order of blood glucose measurement is even later than that of preceding blood glucose data, is 0 or less. For example, the first reference pattern may further include a pattern in which blood glucose data does not increase again after a sharp drop in blood glucose data.

[0058] Below, we will explain examples of the validation dataset patterns corresponding to and not corresponding to the first criterion pattern, referring to Figures 3a, 3b, and 3c.

[0059] Figure 3a shows an example where the patterns in the validation dataset correspond to the first criterion pattern.

[0060] Referring to Figure 3a, we can see an example where the blood glucose data corresponds to 174 mg / dL311, but immediately afterwards, the first blood glucose data312 is measured at 21 mg / dL. In such cases, the pattern corresponding to the validation dataset can be confirmed as corresponding to the first reference pattern.

[0061] Figure 3b shows another example where the patterns in the validation dataset correspond to the first criterion pattern.

[0062] Referring to Figure 3b, we can see an example where the blood glucose data corresponds to 166 mg / dL 321 and is measured as 11 mg / dL 322, and then the blood glucose data continues to increase to 10 mg / dL, 8 mg / dL, 8 mg / dL 323, 324, and 325 without increasing, and the first blood glucose data 326 is still measured as 6 mg / dL. In such cases, since the blood glucose data does not increase again after the sharp drop, the pattern corresponding to the validation dataset can be confirmed as corresponding to the first reference pattern.

[0063] Figure 3c shows an example where the patterns in the validation dataset do not correspond to the first criterion pattern.

[0064] Referring to Figure 3c, which is generally similar to Figure 3b but slightly different, we can see an example where the first blood glucose data 331 increased to 11 mg / dL compared to before. In such cases, since the blood glucose data increased again after a sharp drop, it can be confirmed that the pattern corresponding to the validation dataset does not correspond to the first reference pattern.

[0065] Next, we will explain the second reference pattern. According to one embodiment, the second reference pattern may include a pattern in which at least one of several blood glucose data points is below the second critical value. Here, the second critical value may correspond to a low blood glucose level that is rarely measured even in diabetic patients, for example, around 30 mg / dL, but is not limited to such a value.

[0066] According to one embodiment, the second reference pattern may further include a pattern associated with the time when at least one blood glucose data was measured below the second critical value. For example, the second reference pattern may further include a pattern in which the time when at least one blood glucose data was measured below the second critical value falls within a predetermined time range calculated from the time a hypoglycemia notification was output to the user. It is clear that when a hypoglycemia notification is received, the user will take countermeasures such as consuming food or drink that can raise blood glucose to prevent hypoglycemic shock. However, if the blood glucose data falls below the second critical value again within a predetermined time range calculated from the time the hypoglycemia notification was output, it may be more reasonable to infer that the sensor has partially failed rather than that the user's blood glucose level has actually dropped sharply. The second reference pattern may be set in this manner. In this case, the predetermined time range can be appropriately set as a time range in which it is expected that blood glucose will not drop sharply after the user takes countermeasures.

[0067] Alternatively, the second reference pattern may further include a pattern in which a reference number of blood glucose data are measured below the second critical value, starting from the first blood glucose data measured below the second critical value. This, as mentioned earlier, may take into account the fact that when a hypoglycemia notification is received, the user takes action to raise their blood glucose, so if blood glucose remains very low for an extended period, it may be more reasonable to assume that the sensor has partially failed rather than that it is an actual hypoglycemic state. In this case, the reference number may be set to correspond to the time it is predicted that the user will definitely take action to avoid hypoglycemic shock, considering the measurement cycle.

[0068] According to one embodiment, the electronic device 100 can adjust at least one critical value related to a reference pattern based on the user's medical history information. That is, the electronic device 100 can adjust the first critical value related to the first reference pattern or the second critical value related to the second reference pattern, etc., taking into account the user's disease-related history. The following will provide a detailed explanation of each example.

[0069] For example, in patients with type 1 diabetes, insulin is not synthesized in the body at all, so blood glucose levels can fluctuate significantly compared to patients with other types of diabetes, and therefore, a rapid drop in blood glucose can occur in patients with type 1 diabetes. In such cases, even if blood glucose data drops sharply outside the normal range, caution is needed before assuming this as sensor failure instead of hypoglycemia. Focusing on this point, the electronic device 100 can confirm medical history information indicating that the user has type 1 diabetes, and in this case, the electronic device 100 can adjust the order of two consecutive blood glucose measurements so that the first critical value of the first reference pattern related to the decrease in the subsequent blood glucose data relative to the preceding blood glucose data increases. Through such an embodiment, the estimation of sensor failure in patients with type 1 diabetes can be made conservatively.

[0070] As another example, in patients who have experienced hypoglycemic shock, caution is needed before assuming sensor dropout instead of hypoglycemia, even if the blood glucose data is somewhat low. Therefore, the electronic device 100 can check medical history information indicating that the user has a history of hypoglycemic shock, in which case the electronic device 100 can adjust the second critical value of the second criterion pattern, which is related to the magnitude of at least one of the multiple blood glucose data points included in the validation dataset, to decrease. Through such embodiments, the estimation of sensor dropout in patients who have experienced hypoglycemic shock can be made conservatively. The above explanation relating to the adjustment of critical values ​​is illustrative, and the scope of this disclosure is not limited to the examples described above.

[0071] According to one embodiment, the electronic device 100 can also estimate the detachment of at least some of the blood glucose sensors 200 based on a third reference pattern. Specifically, the electronic device 100 can perform a stabilization operation after the blood glucose sensors 200 have been transcutaneously inserted into the user's body for the first time. During such a stabilization period, the current values ​​of the biometric data measured by the blood glucose sensors 200 may be uneven, that is, the deviation of values ​​may be large in the order of consecutive measurements, and consequently, the blood glucose data that can be confirmed based on the current values ​​may also be confirmed unevenly. As a result, the electronic device 100 can, as at least part of its stabilization operation, refrain from performing a process of confirming or outputting blood glucose data based on such uneven current values, and instead wait until the output value is no longer uneven. Therefore, when the electronic device 100 is performing a stabilization operation, it can predict that the current values ​​will be uneven if the blood glucose sensors 200 are securely inserted without detachment.

[0072] Focusing on these points, according to one embodiment, if the electronic device 100 is confirmed to be performing a stabilization operation, it can compare the pattern of multiple blood glucose data included in the verification dataset with a third reference pattern corresponding to the stabilization operation. Here, the third reference pattern can include a pattern in which the average of the change between two consecutive data points measured in a blood glucose measurement order is greater than or equal to the third critical value. For example, the electronic device 100 can check multiple blood glucose data included in the verification dataset, calculate the average of the change between two consecutive data points measured in a blood glucose measurement order, and then check whether the average is greater than or equal to the third critical value. If the average is greater than or equal to the third critical value, the electronic device 100 can confirm that the pattern of multiple blood glucose data included in the verification dataset corresponds to the third reference pattern and estimate that at least a portion of the blood glucose sensor has not fallen out and has been properly inserted into the user's body. Conversely, if the average is less than the third critical value, the electronic device 100 can confirm that the pattern of multiple blood glucose data included in the verification dataset does not correspond to the third reference pattern. In this case, according to one embodiment, if the blood glucose sensor 200 is properly inserted, the pattern of blood glucose data that should be confirmed by the bumps and grooves will not be the same, so the electronic device 100 can infer that at least a part of the blood glucose sensor 200 has fallen out.

[0073] According to one embodiment, the electronic device 100 can delay outputting the first blood glucose data to the user after estimating sensor detachment by confirming that the pattern of the validation dataset corresponding to the first blood glucose data corresponds to at least one of the first or second reference patterns, or confirming that it does not correspond to the third reference pattern. That is, while the measured blood glucose data is basically output to the user immediately, the output of blood glucose data estimated to have been measured from a detached sensor may be delayed. Here, the output delay encompasses all operations that allow the user to check the complete blood glucose data later than the typical timing for checking blood glucose data, and can encompass a variety of methods for outputting blood glucose data that differ from typical data output methods, such as allowing the user to check only a portion of the blood glucose data before a certain point in time, not being able to check the blood glucose data at all before a certain point in time, only being able to check which range the blood glucose value belongs to, showing it faintly on a graph so that the exact value is not visible, displaying it with another icon so that it is clear that the data in question is estimated to have been measured by a detached sensor, or showing only the trend of increase or decrease in the data. We will now explain, below, several operations that may be linked to this, along with specific examples of such output delay operations.

[0074] First, if it is estimated that at least some of the blood glucose sensors 200 have fallen out and the output of the first blood glucose data is delayed, the electronic device 100 can output a notification to the user related to the sensor detachment. The notification related to the sensor detachment may include a message requesting the user to carefully check the sensors because a sensor may have fallen out. To examine an example of such a notification, refer to Figures 4a and 4b, and Figures 5a and 5b.

[0075] Figure 4a shows an example of how a notification related to the detachment of a sensor according to one embodiment is displayed through a notification window.

[0076] Referring to Figure 4a, an example of a notification related to sensor detachment, displayed through a notification window on a display device operating in conjunction with the electronic device 100, can be seen. The notification related to sensor detachment may display the message "The sensor may have detached." in a relatively large font for emphasis, and below it, in a relatively small font, the message "Please check that the sensor is securely inserted." for emphasis. In one embodiment, the notification of sensor detachment in the form of Figure 4a may correspond to the case where the user is using an application related to the blood glucose sensor 200 with the electronic device 100.

[0077] Figure 4b is a diagram showing an example in which a notification related to the detachment of a sensor according to one embodiment is displayed via a banner.

[0078] Referring to Figure 4b, an example of a notification related to sensor detachment, displayed via a banner on a display device operating in conjunction with the electronic device 100, can be seen. As shown in Figure 4b, unlike notifications provided across a wide area of ​​the display device screen, the notification related to sensor detachment provided via the banner can contain only a concise message, such as "Check for sensor detachment." In one embodiment, the notification of sensor detachment in the form of Figure 4b may correspond to a situation where the user is not using an application related to the blood glucose sensor 200 with the electronic device 100.

[0079] Figure 5a shows another example in which a notification related to the detachment of a sensor according to one embodiment is displayed through a notification window.

[0080] Referring to Figure 5a, we can see another example of a notification related to sensor detachment displayed through a notification window on a display device that operates in conjunction with the electronic device 100, which is similar to, but slightly different from, Figure 4a. In the case of Figure 5a, unlike Figure 4a, a message may be included in addition to a message informing the user that they must perform self-monitoring of blood glucose if they wish to check their blood glucose level, along with a message instructing them to check if the sensor is functioning correctly because an abnormal signal has been detected from the sensor. Here, self-monitoring of blood glucose encompasses a variety of methods in which the user can directly measure their own blood glucose, rather than using the blood glucose sensor 200. One example is, but is not limited to, the self-monitoring of blood glucose (SMBG) method using a blood collection needle and blood glucose meter.

[0081] Figure 5b is a diagram illustrating another example in which a notification related to the detachment of a sensor according to one embodiment is displayed via a banner.

[0082] Figure 5b also shows another example of a notification related to sensor detachment, which is similar to, but slightly different from, Figure 4b, and is displayed via a banner on a display device that operates in conjunction with the electronic device 100. Specifically, Figure 5b corresponds to the example in Figure 5a, and like Figure 5a, it can include a message informing the user that they must perform a blood glucose self-monitoring if they attempt to check their blood glucose level. In one embodiment, the notification of sensor detachment in the form of Figure 5b may correspond to the situation when the user is not using an application related to the blood glucose sensor 200 with the electronic device 100.

[0083] Such notifications may also be transmitted to the parental control terminal 400 configured for the user. Notifications to the parental control terminal 400 may also be displayed through a notification window or banner on a display device that operates in conjunction with the parental control terminal 400, similar to Figures 4a and 4b or 5a and 5b. In this case, the message may also be partially modified or additional messages may be added to suit the needs of the parent operating the parental control terminal 400. For example, if it is estimated that the blood glucose sensor 200 has been detached for a long period of time, the notification to the parental control terminal 400 related to the sensor detachment may further include a message related to the period during which the blood glucose sensor 200 is estimated to have been detached, and a message requesting that it be checked.

[0084] According to one embodiment, a notification related to sensor detachment may differ from other notifications such as measurement notifications output each time the blood glucose sensor 200 measures blood glucose, hypoglycemia notifications output when hypoglycemia is present, hyperglycemia notifications output when hyperglycemia is present, rapid change notifications output when blood glucose fluctuates rapidly, and abnormality notifications output in the event of other sensor malfunctions, in at least some of the various parameters related to notifications, such as volume of sound, intensity of vibration, and notification format. For example, the volume of sound or intensity of vibration may be relatively lower compared to urgent notifications such as hypoglycemia notifications or rapid change notifications, and relatively higher compared to routine notifications such as measurement notifications. In addition, in relation to the notification format, a customizable melody or vibration pattern may be applied only to notifications related to sensor detachment, so that the user can immediately recognize that the notification is related to sensor detachment.

[0085] According to one embodiment, in a situation where there is blood glucose data whose output has been delayed, the user can confirm a request to output a blood glucose graph. Specifically, the request to output a blood glucose graph can be confirmed by user input through an application associated with the blood glucose sensor 200 operating on the electronic device 100. In this case, the electronic device 100 can deactivate the portion of the blood glucose graph corresponding to the blood glucose data whose output has been delayed. As mentioned above, if the output of the first blood glucose data has been delayed, the deactivated portion may include the portion corresponding to the first blood glucose data. After processing in this way, the electronic device 100 can output a blood glucose graph with the portion corresponding to the blood glucose data whose output has been delayed deactivated to a display device linked to the electronic device 100. According to one embodiment, the blood glucose graph may be a graph in which the horizontal axis corresponds to the time axis, the vertical axis corresponds to the magnitude of the blood glucose value, and each point on the graph represents each blood glucose data measured at a given time.

[0086] Here, the deactivation process, according to one embodiment, may include at least some of the following: blurring of points on the graph, unresponsive processing upon clicking, and display processing related to output delay. For example, the blurring process may include blurring the display of points on the graph that correspond to data for which output has been delayed. For example, the unresponsive processing upon clicking may include processing so that, unlike general points where blood glucose data is displayed in detail upon clicking, no other information is displayed when a point for which output has been delayed is clicked. For example, the display processing related to output delay may include processing to display a message indicating that the point corresponds to data for which output has been delayed and that blurring or unresponsive processing upon clicking has been applied. Furthermore, according to one embodiment, the deactivation process may also include displaying blood glucose data using a different icon than other points on the graph. For example, blood glucose data that is presumed not to have been obtained from a detached sensor and blood glucose data that is presumed to have been obtained from a detached sensor can be displayed on the blood glucose graph using different icons to clearly distinguish between the two. As an additional example, the deactivation process may include a process that prevents any UI / UX feedback from being displayed even if a click is input for a graph coordinate corresponding to data whose output has been delayed. When such a deactivation process is applied, the electronic device 100 may display appropriate feedback when a click is input for a graph coordinate corresponding to data whose output has not been delayed, but may not display any feedback for data whose output has been delayed, thereby allowing the user to perceive that data whose output has been delayed cannot be clicked. The deactivation process is not limited to the example described above and can encompass all processes that allow the user to view complete blood glucose data for data whose output has been delayed at a later time than the typical time for viewing blood glucose data.

[0087] Such a blood glucose graph may be requested via the parent terminal 400. In this case, the parent terminal 400 can obtain overall blood glucose data through linkage with the server 200 or electronic device 100, and based on this, can display the blood glucose graph on a display device linked to the parent terminal 400. If there is any blood glucose data that has been delayed in output, as described above, the relevant portion may be deactivated and displayed.

[0088] To examine an example of a blood glucose graph in which deactivation processing was performed on blood glucose data whose output was delayed, refer to Figures 6a and 6b.

[0089] Figure 6a is an illustrative diagram of a blood glucose graph in which blood glucose data whose output has been delayed has been deactivated according to one embodiment.

[0090] Referring to Figure 6a, it can be seen that the value 501, which is estimated to be the blood glucose data measured with the blood glucose sensor 200 detached, is displayed at a lighter point on the blood glucose graph compared to other points. Thus, the value 501, which is estimated to be the blood glucose data measured with the blood glucose sensor 200 detached, can be displayed on the blood glucose graph in a way that distinguishes it from other points.

[0091] Figure 6b is an illustrative diagram showing the UI when blood glucose data that has been deactivated and whose output has been delayed according to one embodiment is clicked.

[0092] Referring to Figure 6b, we can see an example of a notification 502 that may be displayed when the user selects a value 501 which is estimated to be blood glucose data measured with the blood glucose sensor 200 in Figure 6a detached. As can be seen in Figure 6b, it is possible to improve the user experience by clearly informing the user that the value may have been measured with the sensor detached.

[0093] The above examples illustrate situations where blood glucose-related information is requested by a user or guardian in the form of a two-dimensional blood glucose graph. However, this is merely an example, and blood glucose-related information can be requested in a variety of formats other than graphs, such as tabular logs, distribution charts, radial charts, calendar maps, cumulative area charts, and box plots, and is not limited to the examples listed above. The electronic device 100 can provide blood glucose-related information to the user or guardian in a variety of formats, and regardless of the format in which the blood glucose-related information is provided, various processing methods for blood glucose data estimated to have been measured after sensor detachment, such as the deactivation process by output delay described above, can be similarly applied, and this is also considered to be within the scope of this disclosure.

[0094] According to one embodiment, the electronic device 100 can estimate sensor detachment by confirming that the pattern of the validation dataset corresponding to the first blood glucose data corresponds to at least one of the first or second reference patterns, and then confirm the second blood glucose data based on the blood glucose sensor 200 in the next measurement cycle. If the second blood glucose data is the same as or smaller than the first blood glucose data, the electronic device 100 can re-estimate whether the sensor has detached by comparing the pattern of the validation dataset corresponding to the second blood glucose data with the first and second reference patterns. However, if the second blood glucose data is larger than the first blood glucose data, the electronic device 100 can confirm that the first blood glucose data was not measured with the sensor detached. Specifically, as mentioned above, if the blood glucose sensor 200 had actually detached, it can be estimated that the blood glucose data would not increase again. Thus, if the second blood glucose data is larger than the first blood glucose data, it can be estimated that the blood glucose sensor 200 has not actually detached. In this respect, the electronic device 100 can assume that the first blood glucose data was not measured with the sensor detached, and therefore can remove the delay in outputting the first blood glucose data. As a result, the electronic device 100 can output the first blood glucose data to the user normally. In other words, it can remove the deactivation processing applied to the blood glucose graph mentioned above and display the blood glucose data in the same way as at a typical location.

[0095] According to one embodiment, a flag related to compression noise can be selectively set for data whose output has been delayed, such as the first blood glucose data. For example, if compression is applied to the blood glucose sensor 200, the measured value may be relatively small. Therefore, a flag related to compression noise can be set for data suspected to have been underestimated due to such a problem. Such a compression noise flag can be set based on data from a pressure sensor installed together with the blood glucose sensor 200, or for data from time periods when compression frequently occurs due to reasons such as turning over in bed during sleep, and can be set when various conditions are met. Alternatively, an embodiment is also possible in which a flag related to compression noise is basically set for all data whose output has been delayed.

[0096] If it is confirmed that a flag related to compression noise has been set for the first blood glucose data, the electronic device 100 can control the blood glucose sensor 200 so that the second blood glucose data is measured earlier than the basic cycle. That is, if the basic cycle for measuring blood glucose data is 5 minutes, the electronic device 100 can control the blood glucose sensor 200 so that the second blood glucose data is measured again in just 1 minute. Since the compression applied to the blood glucose sensor 200 is usually relieved quickly, the second blood glucose data is measured normally, i.e., higher than the first blood glucose data which was measured lower due to compression noise. In such a case, the electronic device 100 can release the delay in outputting the first blood glucose data, but can output a notification to the user that includes a message indicating that the first blood glucose data is estimated to have been output lower due to compression noise. Alternatively, instead of the first blood glucose data, the device can use the previously measured blood glucose data and the second blood glucose data and output adjusted data to the user after selective interpolation or extrapolation. For example, the electronic device 100 can estimate the accurate blood glucose level at the time of measurement of the first blood glucose data by performing an interpolation operation based on the second blood glucose data, which was measured normally without compression noise, and the most recent blood glucose data measured before the first blood glucose data was measured, instead of the first blood glucose data. As another example, the electronic device 100 can also estimate the accurate blood glucose level at the time of measurement of the first blood glucose data by performing an extrapolation operation using the most recent blood glucose data measured before the first blood glucose data was measured or multiple blood glucose data measured after the first blood glucose data was measured.

[0097] According to one embodiment, the electronic device 100 can check whether the number of blood glucose data for which output has been continuously deferred corresponds to the number of first criteria. If the number of blood glucose data for which output has been continuously deferred corresponds to the number of first criteria, the electronic device 100 can disconnect from the blood glucose sensor 200. Here, the number of first criteria can be appropriately set to the number of data for which it can be estimated that the blood glucose sensor 200 has reliably dropped out, considering the measurement cycle. After the connection with the blood glucose sensor 200 is disconnected, the electronic device 100 can output a notification to the user that includes a message requesting that a new blood glucose sensor be connected because the connection with the blood glucose sensor has been disconnected.

[0098] According to one embodiment, the electronic device 100 can identify a new blood glucose sensor that replaces the blood glucose sensor 200 after the connection with the blood glucose sensor 200 has been disconnected. The electronic device 100 can then verify blood glucose data based on the new blood glucose sensor. The electronic device 100 can verify estimated blood glucose data for at least a portion of the blood glucose data for which output has been delayed for a continuous period by performing interpolation or extrapolation calculations using the blood glucose data verified based on the new blood glucose sensor. For example, the electronic device 100 can perform interpolation calculations using the blood glucose data verified based on the new blood glucose sensor and the most recent blood glucose data from the blood glucose data for which output has not been delayed, to verify estimated blood glucose data for blood glucose data measured at a point in time between two points in time but for which output was delayed. Alternatively, the electronic device 100 can perform extrapolation calculations using multiple blood glucose data verified based on the new blood glucose sensor to verify estimated blood glucose data for blood glucose data measured at a point in time prior to the time when the measurement was performed by the new blood glucose sensor but for which output was delayed. The electronic device 100 can then output the estimated blood glucose data thus verified to the user. For example, when the electronic device 100 detects a request for output of a blood glucose graph, it can replace at least a portion of the data whose output has been delayed with estimated blood glucose data, as described above, and display it on the blood glucose graph, and provide it to the user.

[0099] The various operations of the electronic device 100 described above may be configured to be performed in conjunction with the server 300. For example, the electronic device 100 may be configured to transmit data from the blood glucose sensor 200 to the server 300. In this case, the server 300 can perform the various operations described above on behalf of the electronic device 100 based on the transmitted data. In this case, when a request for the various information described above is input from the user through an application running on the electronic device 100, the server 300 can transmit the various information confirmed through calculations to the electronic device 100 and have it output to the user.

[0100] Figure 7 shows a block diagram of an electronic device according to one embodiment.

[0101] In one embodiment, the electronic device 100 may include a memory 101 and a processor 102. The electronic device 100 shown in Figure 7 only shows components relevant to this embodiment. Therefore, a person with ordinary skill in the art related to this embodiment will understand that, in addition to the components shown in Figure 7, other general-purpose components may be included. In one embodiment, the processor 102 may be included in a controller.

[0102] The processor 102 can control the overall operation of the electronic device 100 and process data and signals. The processor 102 may consist of at least one hardware unit. The processor 102 can also be operated by one or more software modules generated by executing program code stored in memory 101. Since the processor 102 can include memory, it can execute program code stored in memory to control the overall operation of the electronic device 100 and process data and signals.

[0103] The processor 102 may be configured to verify the first blood glucose data based on the blood glucose sensor, verify the validation dataset corresponding to the first blood glucose data, and estimate the loss of at least some of the blood glucose sensors from the user's body based on a comparison between the pattern corresponding to the validation dataset and the reference pattern, and to delay outputting the first blood glucose data to the user if loss is estimated.

[0104] Depending on the embodiment, the electronic device 100 may additionally include a transceiver for wired / wireless communication. The electronic device 100 can communicate with an external electronic device using the transceiver. The external electronic device may be a terminal or a server. The communication technologies used by the transceiver include GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G, WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), and Bluetooth® (registered trademark). TM Possible technologies include RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, and NFC (Near Field Communication).

[0105] The electronic device according to the embodiment described above may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with external devices, and user interface devices such as a touch panel, keys, and buttons. The method embodied in the software module or algorithm may be stored on a computer-readable storage medium as computer-readable code or program instructions executable on the processor. Here, computer-readable storage media include magnetic recording media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical reading media (e.g., CD-ROM, DVD (Digital Versatile Disc)). The computer-readable storage media may be distributed across a network of computer systems, and computer-readable code may be stored and executed in a distributed manner. The medium may be computer-readable, stored in memory, and executed by the processor.

[0106] This embodiment can be represented by functional block configurations and diverse processing stages. Such functional blocks can be embodied by a variety of hardware and / or software configurations that perform specific functions. For example, the embodiment may employ an integrated circuit configuration such as memory, processing, logic, look-up tables, etc., which can perform diverse functions under the control of one or more microprocessors or other control devices. Just as the components can be executed by software programming or software elements, this embodiment includes a variety of algorithms embodied by combinations of data structures, processes, routines, or other programming configurations, which can be embodied in programming or scripting languages ​​such as C, C++, Java, assembler, etc. Functional aspects can be embodied by algorithms executed by one or more processors. Furthermore, this embodiment can employ prior art for electronic environment configuration, signal processing, and / or data processing, etc. Terms such as “mechanism,” “element,” “means,” and “configuration” can be used broadly and are not limited to mechanical and physical configurations. The terms can also include the meaning of a series of software processes (routines) in conjunction with a processor, etc.

[0107] The embodiments described above are merely examples, and other embodiments may be embodied within the scope of the claims described later.

Claims

1. A method for managing blood glucose data in an electronic device, The first step is to check the blood glucose data based on the blood glucose sensor, The step of verifying the validation dataset corresponding to the first blood glucose data, A step of estimating whether at least some of the blood glucose sensors have fallen off the user's body based on a comparison between the pattern corresponding to the validation dataset and a reference pattern, A method for managing blood glucose data, comprising: a step of delaying the output of the first blood glucose data if the aforementioned omission is presumed.

2. Before the step of confirming the first blood glucose data based on the blood glucose sensor, The step includes periodically checking blood glucose data based on the blood glucose sensor inserted into the user's body, The method for managing blood glucose data according to claim 1, wherein the first blood glucose data is measured by the blood glucose sensor in the next measurement cycle following the periodically confirmed blood glucose data.

3. The step of verifying the validation dataset corresponding to the first blood glucose data is: The steps include confirming that the first blood glucose data and at least one preceding blood glucose data set are consecutive in the order of blood glucose measurement, A method for managing blood glucose data according to claim 1, comprising the step of verifying the verification dataset, which includes the first blood glucose data and the at least one preceding blood glucose data arranged in chronological order.

4. The step of estimating whether at least some of the aforementioned blood glucose sensors have fallen out is: The step of reviewing multiple time-series-arranged blood glucose data included in the aforementioned validation dataset, A step of confirming whether the patterns of the plurality of blood glucose data correspond to at least one of the first reference pattern and the second reference pattern included in the reference pattern, A method for managing blood glucose data according to claim 1, comprising the step of estimating the loss of at least some of the blood glucose sensors when the plurality of blood glucose data patterns correspond to at least one of the first and second reference patterns.

5. The first reference pattern is, The method for managing blood glucose data according to claim 4, which includes a pattern in which, among the plurality of blood glucose data, the subsequent blood glucose data decreases by a first critical value or more compared to the preceding blood glucose data, in two consecutive blood glucose data sets measured in the same order.

6. The first reference pattern is, The method for managing blood glucose data according to claim 5, further comprising a pattern in which, among the plurality of blood glucose data, the slope between two blood glucose data where the order of blood glucose measurement is even later than the preceding blood glucose data is 0 or less.

7. The second reference pattern is, The method for managing blood glucose data according to claim 4, comprising a pattern in which at least one of the plurality of blood glucose data is below the second critical value.

8. The step of estimating whether at least some of the aforementioned blood glucose sensors have fallen out is: A method for managing blood glucose data according to claim 1, comprising the step of adjusting at least one critical value related to the reference pattern based on the user's medical history information.

9. The step of adjusting at least one critical value related to the aforementioned reference pattern is: The steps include: confirming the medical history information indicating that the user has type 1 diabetes; A method for managing blood glucose data according to claim 8, comprising the step of adjusting two consecutive blood glucose data sets in the order of blood glucose measurement such that the first critical value of a first reference pattern related to the decrease in the subsequent blood glucose data relative to the preceding blood glucose data increases.

10. The step of adjusting at least one critical value related to the aforementioned reference pattern is: The steps include: confirming the medical history information indicating that the user has a history of hypoglycemic shock; A method for managing blood glucose data according to claim 8, comprising the step of adjusting such that a second critical value of a second reference pattern related to the magnitude of at least one of the multiple blood glucose data included in the verification dataset decreases.

11. Based on the blood glucose sensor, the step is to confirm a second blood glucose data that has increased compared to the first blood glucose data, The step of removing the grace period for outputting the first blood glucose data, A method for managing blood glucose data according to claim 1, comprising the step of outputting the first blood glucose data to the user in a normal manner.

12. Before the step of confirming the second blood glucose data which has increased compared to the first blood glucose data based on the blood glucose sensor, and after the step of delaying the output of the first blood glucose data to the user, A step of checking the flag associated with compression noise set for the first blood glucose data, The method further includes a step of controlling the blood glucose sensor so that the second blood glucose data is measured earlier than the basic cycle, The step of outputting the first blood glucose data to the user is: The method for managing blood glucose data according to claim 11, further comprising the step of outputting a notification to the user related to the compression noise.

13. The first step is to confirm whether the number of blood glucose data for which output has been continuously deferred corresponds to the number of data for the first criterion, A method for managing blood glucose data according to claim 1, further comprising the step of disconnecting the connection with the blood glucose sensor when the number of blood glucose data for which output has been continuously deferred corresponds to the number of the first criterion.

14. The connection to the aforementioned blood glucose sensor is disconnected, and a new blood glucose sensor is identified as a replacement for the aforementioned blood glucose sensor. The steps include: confirming blood glucose data based on the aforementioned new blood glucose sensor; The steps include: confirming estimated blood glucose data for at least a portion of the blood glucose data for which output has been delayed by performing interpolation or extrapolation calculations using the blood glucose data confirmed based on the novel blood glucose sensor; A method for managing blood glucose data according to claim 13, comprising the step of outputting the estimated blood glucose data to the user.

15. The method for managing blood glucose data according to claim 1, further comprising the step of outputting a notification to the user related to the detachment of a sensor.

16. The step of outputting a notification to the user related to the detachment of the sensor is: The step of verifying the user's parental device, A method for managing blood glucose data according to claim 15, comprising the step of outputting a notification to the parent terminal related to the detachment of the sensor.

17. Notifications related to the detachment of the aforementioned sensor are, The method for managing blood glucose data according to claim 15, wherein at least a portion of the measurement notification, hypoglycemia notification, and hyperglycemia notification of the blood glucose sensor differs from at least a portion of the volume of sound, the volume of vibration, and the notification form.

18. The step of confirming the user's request for outputting a blood glucose graph, The steps include: deactivating the portion of the blood glucose graph that includes the first blood glucose data and corresponds to the blood glucose data for which output has been delayed; The step includes outputting to the user the blood glucose graph in which the portion of the output corresponding to the blood glucose data for which the output was deferred has been deactivated, The method for managing blood glucose data according to claim 1, wherein the deactivation process includes at least a part of the following: blurring of points on the blood glucose graph, unresponsive processing when clicked, and display processing related to output delay.

19. A computer-readable non-temporary storage medium recording a program for causing a computer to perform the method according to any one of claims 1 to 18.

20. An electronic device for managing blood glucose data, Processor and Includes memory for storing one or more instructions, The processor performs one or more of the above instructions, An electronic device configured to verify first blood glucose data based on a blood glucose sensor, verify a validation dataset corresponding to the first blood glucose data, estimate the detachment of at least some of the blood glucose sensors from the user's body based on a comparison between a pattern corresponding to the validation dataset and a reference pattern, and, if such detachment is estimated, to delay the output of the first blood glucose data to the user.

Images