💉 Hypoglycemia Unawareness Pump Alert Simulator

Hypoglycemia Awareness Assessment — Clarke and Gold Questionnaires

Hypoglycemia unawareness is the loss of the ability to sense the early warning symptoms of low blood glucose — shaking, sweating, palpitations, hunger — before cognitive function declines. It develops most often in children and adults with recurrent hypoglycemic episodes, and it is one of the strongest predictors of a future severe, assistance-requiring low. Structured questionnaires give clinicians a reproducible way to detect it before it causes an emergency.

• ~25%: Prevalence in type 1 diabetes (higher with longer disease duration)
• 6×: Severe hypo risk, unaware vs aware (Gold et al. cohort data)
• ≥ 4 / 7: Clarke score threshold (indicates impaired awareness)
• ↓ ~20 mg/dL: Symptom threshold shift (after recurrent antecedent lows)

What blunts hypoglycemia awareness

Every low blood glucose episode triggers a counter-regulatory hormone surge — epinephrine and glucagon — that both raises glucose and produces the classic autonomic warning symptoms (tremor, sweating, tachycardia). Repeated exposure to hypoglycemia habituates this response, much like an alarm that has gone off too many times: each successive low episode blunts the counter-regulatory hormone release and shifts the glycemic threshold at which symptoms appear further downward.

The result is a vicious cycle known as Hypoglycemia-Associated Autonomic Failure (HAAF): lower awareness leads to more frequent and more severe lows, which further blunt awareness. In pediatric patients this is especially dangerous because young children may not reliably self-report symptoms even when awareness is intact, compounding the risk once true unawareness sets in.

A single antecedent episode of hypoglycemia can measurably blunt the counter-regulatory response to a subsequent low occurring within 24 hours — the impairment is rapid to develop and, importantly, reversible with sustained avoidance of lows.

Clarke and Gold questionnaires

Two validated, brief clinical instruments are used to screen for impaired awareness:

• Clarke method (8 questions): asks patients to rate whether they can tell when their glucose is low, at what glucose level they typically first notice symptoms, and how often they experience lows without warning. A score ≥ 4 out of 7 scoring items classifies the patient as having reduced awareness.

• Gold method (single 7-point Likert item): "Do you know when your hypos are commencing?" from 1 (always aware) to 7 (never aware). A score ≥ 4 similarly flags impaired awareness.

Both are quick enough for routine clinic use and correlate well with objective measures such as hypoglycemia symptom threshold during controlled glucose clamp studies. In pediatrics, caregiver-reported versions and continuous glucose monitor (CGM) ambulatory glucose profile review (time below range, frequency of undetected lows) supplement or substitute for self-report in younger children.

Why unaware patients need a different safety architecture

Once impaired awareness is documented, the clinical strategy shifts from relying on the patient to notice symptoms toward building an external, automated safety net. This reframing drives every subsequent stage of pump and CGM configuration: alert thresholds are raised, predictive suspend features are activated as a primary (not backup) defense, caregiver escalation is enabled, and — counterintuitively — glycemic targets may be deliberately relaxed for a period to let the biological warning system recover. The device becomes the symptom the child can no longer feel.

Threshold Alert Configuration — Raising the Warning Floor

The standard CGM low-glucose alert is typically set at 70 mg/dL, matched to the widely used clinical definition of hypoglycemia. For a patient who cannot reliably feel symptoms even at that level, an alert firing at 70 mg/dL may leave too little time to act before further decline. Raising the threshold to 80–90 mg/dL trades a higher rate of alerts for a larger safety margin — more time between "device notices" and "glucose becomes dangerous."

• 70 mg/dL: Standard CGM low alert (ADA consensus threshold)
• 80–90 mg/dL: Unaware-patient alert range (individualized upward adjustment)
• ~15–25 min: Extra warning time gained (at typical descent rates)
• 1–3 mg/dL/min: Typical glucose descent rate (insulin-driven fall)

How the threshold trade-off works

Every CGM low-alert threshold decision balances two competing harms: set it too low and an unaware patient may already be symptomatic or cognitively impaired by the time the alarm fires; set it too high and alarms fire so often during ordinary post-meal dips that the patient or caregiver begins to ignore them (alert fatigue, addressed in Stage 4).

For a documented unaware patient, clinical practice generally favors erring toward an earlier warning: a threshold of 80–90 mg/dL rather than 70 mg/dL. At a typical insulin-driven descent rate of 1–3 mg/dL per minute, that 10–20 mg/dL of extra headroom translates to roughly 15–25 additional minutes of lead time — time in which the patient, a caregiver, or the pump’s own predictive-suspend algorithm can intervene before the glucose reaches a genuinely dangerous range.

Threshold selection is individualized, not fixed: a toddler with brittle overnight lows may be set even higher (90+ mg/dL) with a rate-of-change alert layered on top, while a well-controlled adolescent regaining awareness may be stepped back down toward standard settings over time.

Rate-of-change alerts as a complement

Modern CGM systems layer a second alert type on top of the static threshold: a predicted rate-of-change alarm that fires when glucose is falling quickly (e.g., faster than 2 mg/dL/min) even before the absolute threshold is crossed. For unaware patients this is particularly valuable overnight, when a rapid fall from a comfortable 140 mg/dL can cross 80 mg/dL in well under 30 minutes without any static threshold having been breached earlier in the night.

Combining a raised static threshold with rate-of-change alerting gives two independent triggers, reducing the chance that a fast, unexpected drop goes undetected until glucose is already critically low.

Clinical configuration workflow

1. Confirm impaired awareness via Clarke/Gold score and review of CGM-logged undetected lows 2. Set static low-alert threshold above standard (typically 80–90 mg/dL), individualized to the child’s typical descent rate and caregiver response time 3. Enable urgent-low-soon / predicted-low alerts if available on the platform 4. Layer rate-of-change alerting for rapid overnight or exercise-induced drops 5. Re-assess threshold at each clinic visit — as awareness improves (Stage 5), thresholds are stepped back down to reduce alert burden

Predictive Low-Glucose Suspend — Insulin Delivery Stops Before the Low Arrives

The single most important safety feature for a hypoglycemia-unaware patient is predictive low-glucose suspend (PLGS). Rather than waiting for glucose to actually cross a threshold, the pump algorithm continuously forecasts where glucose is heading over the next 30 minutes using recent CGM trend data, and automatically halts basal insulin delivery when that forecast crosses the low threshold — acting as the symptom-detection system the patient no longer has.

• 30 min: Prediction horizon (forward-looking forecast window)
• ~75%: Reduction in overnight lows (PLGS vs. sensor-augmented pump alone)
• ≤ 2 hrs: Basal resumes automatically (once glucose rises or trend reverses)
• Control-IQ, SmartGuard, Omnipod 5: Systems using PLGS/AID (commercial hybrid closed-loop platforms)

How the predictive algorithm forecasts a future low

PLGS algorithms use the CGM’s recent glucose trajectory — current value, rate of change, and short-term curvature — combined with a simple kinetic model of glucose and active insulin to project where glucose will be at each point over the next 30 minutes. If that projected trajectory crosses the configured low threshold within the horizon, the pump suspends basal insulin delivery immediately, before the actual measured glucose has reached the threshold.

This is fundamentally different from a reactive threshold-suspend feature (which stops insulin only once glucose has already reached the low value): predictive suspend acts on the forecast, buying back the lag time between "insulin still in the body" and "glucose actually falls." Because subcutaneous insulin has a pharmacodynamic tail of 2–4 hours, stopping delivery early is what actually prevents the low rather than merely reacting to it.

Landmark randomized trials (e.g., the ASPIRE In-Home study) found predictive low-glucose suspend reduced overnight hypoglycemic events by roughly 30–75% compared to sensor-augmented pump therapy without suspend — without a rebound increase in mean glucose or ketoacidosis risk.

Why this matters most for unaware patients

For a patient with intact hypoglycemia awareness, PLGS is a convenience — one more layer of protection on top of symptom recognition and self-treatment. For a patient with impaired awareness, PLGS is not a backup; it is functionally the primary defense against severe hypoglycemia, because the biological alarm system (adrenergic symptoms) has been silenced by recurrent antecedent lows.

This reframing has direct clinical consequences: unaware patients are prioritized for automated insulin delivery (AID) systems with predictive suspend capability, PLGS is left enabled even when it causes more frequent basal interruptions than a fully aware patient might tolerate, and any lapse in sensor connectivity (which disables the predictive algorithm) is treated as an acute safety gap requiring immediate caregiver attention rather than a minor technical nuisance.

Resuming delivery safely

Basal suspension is not indefinite. Once CGM data shows glucose has stabilized or begun rising, or a maximum suspend duration (commonly capped around 2 hours to avoid hyperglycemia and ketosis risk) is reached, the algorithm automatically resumes basal delivery. Some systems use a graded resume — restarting at a reduced rate and ramping back to the programmed basal rate over 15–30 minutes — to avoid re-triggering a rapid re-descent immediately after recovery.

Alert Fatigue and Caregiver Escalation — Keeping the Alarm Meaningful

A safety system that alarms constantly eventually gets ignored. Alert fatigue — the well-documented tendency for patients and caregivers to become desensitized to frequent alarms and respond more slowly or not at all — is a recognized barrier to hypoglycemia safety, especially once thresholds have been raised and predictive suspend is firing often. Escalation protocols that route unacknowledged alerts to a caregiver’s phone provide a second line of defense when the primary alert is missed.

• 3–6 / night: Nighttime alarms, unaware patients (typical range at raised thresholds)
• up to 40%: Alarms ignored after fatigue onset (observed in remote-monitoring studies)
• ~5–15 min: Escalation delay to caregiver (if primary alert unacknowledged)
• Dexcom Follow, Tandem Source, LibreLinkUp: Remote monitoring platforms (caregiver-facing companion apps)

The alert fatigue trap

Raising the alert threshold and enabling predictive suspend (Stages 2–3) directly increases how often alarms fire — a child whose glucose oscillates around 90–110 mg/dL after meals may trigger an 80 mg/dL threshold alert several times a day even when never truly at risk. Each unnecessary or non-actionable alarm erodes trust in the system: caregivers snooze notifications, mute the phone overnight, or develop a habit of dismissing alerts without checking glucose first.

This is dangerous precisely because the entire safety architecture for an unaware patient depends on someone — patient, caregiver, or algorithm — actually responding to the alert. A predictive suspend event that nobody checks on, in a household where alarms have become background noise, can mask a sensor error or a situation the pump cannot resolve alone (e.g., a failed infusion set still metabolically active from prior boluses).

Design strategies against fatigue

• Smart snoozing: once an alert has been acknowledged, suppress repeat alerts for the same episode for a defined interval rather than re-alarming every few minutes • Threshold tuning per time-of-day: slightly relax alert sensitivity in predictable post-meal windows while keeping full sensitivity overnight and during exercise • Tiered severity: distinguish an informational "trending low" notice from an urgent "glucose critically low, action required" alarm with different tones/vibration patterns • Periodic re-titration: as data accumulates, threshold and predictive-suspend sensitivity are adjusted at clinic visits to minimize non-actionable alarms while preserving sensitivity to genuine risk • Caregiver rotation and shared load: splitting overnight monitoring responsibility between caregivers reduces fatigue in any one individual

Escalation to caregiver monitoring apps

When the primary alert on the patient’s own device or phone goes unacknowledged for a defined window (commonly 5–15 minutes), remote monitoring platforms escalate the notification to one or more designated followers — typically parents or a school nurse for pediatric patients. These apps (Dexcom Follow, Tandem Source, LibreLinkUp, and equivalents bundled into automated insulin delivery ecosystems) run on a separate device and network path, so a caregiver at work or asleep in another room still receives the alert even if the child’s own device is silenced, out of reach, or the child is unresponsive.

Effective escalation design specifies clear ownership: who is notified first, how quickly escalation occurs if unacknowledged, and what action is expected (check on the child, administer fast-acting carbohydrate or glucagon, call emergency services) — turning a technically successful alert into an actual intervention.

A predictive-suspend event paired with an unacknowledged primary alert is treated as the highest-priority escalation trigger: the pump has already determined a low is imminent, so a non-response window as short as 5–10 minutes before caregiver escalation is common in pediatric configurations.

Awareness Restoration — Loosening Control to Regain a Warning System

The most counterintuitive intervention in hypoglycemia unawareness management is also one of the best supported: deliberately avoiding ALL hypoglycemic episodes — even mild ones — for a sustained period, typically 2–3 weeks, by relaxing glycemic targets. This temporary loosening of control allows the blunted counter-regulatory hormone response to partially recover, restoring the patient’s ability to feel a low coming before the device has to intervene for them.

• 2–3 weeks: Recommended avoidance period (strict zero-hypoglycemia window)
• ~40–60%: Awareness score improvement (reduction in Clarke/Gold score reported)
• Partial, days–weeks: Counter-regulatory recovery (epinephrine response begins rising quickly)
• High if lows resume: Relapse risk (benefit is not permanent without maintenance)

The biological basis for recovery

Because hypoglycemia-associated autonomic failure is driven by repeated exposure to low glucose, strictly avoiding any further exposure removes the stimulus that is suppressing the counter-regulatory system. Clinical studies going back to the 1990s (Fanelli et al. and others) demonstrated that even a few weeks of scrupulous hypoglycemia avoidance measurably restores epinephrine response and symptom awareness in patients with documented unawareness — the impairment, while dangerous, is substantially reversible rather than permanent.

In practice this means temporarily raising CGM/pump glucose targets (e.g., target range shifted upward, more conservative correction dosing, higher temporary basal targets) and treating any glucose reading in the 60–70 mg/dL band as a hypoglycemic event to be avoided in the future, rather than an acceptable routine occurrence.

The strategy directly trades a higher average glucose — and the small associated increase in longer-term complication risk over a few weeks — for restoration of the patient’s own biological alarm system. For a patient with recurrent severe lows, this trade is considered strongly favorable: severe hypoglycemia carries immediate risk of seizure, loss of consciousness, and death, which outweighs weeks of modestly elevated glucose.

Implementing the strategy in a pediatric AID system

1. Temporarily raise the CGM/pump target glucose range (commonly by 20–30 mg/dL above the child’s usual target) 2. Increase the low-alert threshold further during the restoration window, and keep predictive suspend maximally sensitive as a backstop 3. Reduce insulin-to-carb ratios and correction factors conservatively to avoid overcorrection lows 4. Track every glucose value below 70 mg/dL as a "reset" event that restarts or extends the avoidance window 5. Reassess Clarke/Gold awareness score after 2–3 weeks; if improved, gradually step targets and alert thresholds back toward standard values while monitoring for any relapse

Sustaining the gain

Restored awareness is not a one-time fix — it can be lost again if hypoglycemic episodes resume at their prior frequency. Long-term management therefore blends the tools from every earlier stage: predictive low-glucose suspend continues running in the background even after awareness recovers, alert thresholds are stepped down gradually rather than abruptly, and periodic re-screening with Clarke/Gold questionnaires at routine clinic visits catches any early re-blunting before it becomes severe unawareness again. The device and the restored biology work together, each covering the other’s gaps.