CPC A61M 5/1723 (2013.01) [A61B 5/14532 (2013.01); A61B 5/4839 (2013.01); A61B 5/7405 (2013.01); A61B 5/742 (2013.01); G06F 9/54 (2013.01); G06F 9/546 (2013.01); G06F 16/2228 (2019.01); G06F 16/955 (2019.01); G06F 21/606 (2013.01); G08B 21/0453 (2013.01); G08B 25/08 (2013.01); G16H 10/60 (2018.01); G16H 20/17 (2018.01); G16H 40/63 (2018.01); H04L 9/0637 (2013.01); H04L 9/0822 (2013.01); H04L 9/0833 (2013.01); H04L 9/0861 (2013.01); H04L 9/0891 (2013.01); H04L 9/14 (2013.01); H04L 9/30 (2013.01); H04L 63/0428 (2013.01); H04M 1/72409 (2021.01); H04W 12/084 (2021.01); A61M 2205/3584 (2013.01); A61M 2205/50 (2013.01); A61M 2205/502 (2013.01); A61M 2230/201 (2013.01); H04L 2209/80 (2013.01); H04M 1/724095 (2022.02); H04M 1/72412 (2021.01)] | 20 Claims |
1. A method of providing an alert to a user using a mobile computing device, comprising:
receiving analyte data from a continuous analyte monitor;
determining the analyte data warrants providing an alert to the user;
determining an alert level of the alert based on an alert profile of the user;
detecting the mobile computing device is in a state inhibiting a first notification type;
in response to detecting the mobile computing device is in the state inhibiting the first notification type, providing the alert via the mobile computing device with a second notification type;
determining whether the user has acknowledged the alert provided with the second notification type within a first defined time period;
in response to determining the user has not acknowledged the alert via the second notification type within the first defined time period, escalating the alert based on the alert level, wherein escalating the alert comprises overriding the state inhibiting the first notification type; and
providing the alert via the mobile computing device with the first notification type.
|