Turning a 7.8% Sensor Error Into a Safe Alert

Turning a 7.8% Sensor Error Into a Safe Alert

Ada re-derives this chapter’s own numbers step by step, at full precision

foundations
math-foundations
calculation-audit
applications
Ada ADA · CALCULATION AUDIT

Turning a 7.8% Sensor Error Into a Safe Alert

This chapter pairs a program-economics claim with a safety-critical one, and the safety number is the one that must be exactly right: a continuous glucose monitor carries a 7.8% MARD error, so a reading near the 54 mg/dL danger line can drift several mg/dL above the true value. The chapter’s fix is to alert early — at 62 mg/dL, not 54 — sizing the buffer from the sensor’s own error rather than the clinical cutoff. This audit re-derives that buffer to ask how a 7.8% sensor error becomes a genuinely safe alert.

Companion to the chapter Medication Adherence — every number here comes from that chapter.

See the relationship before changing it

The figure reads from left to right. The blue card is low-alert buffer. The middle card applies the page rule. The green card is low alert threshold. Walk the arrows once: set the input, apply the rule, then read the result with its unit.

Low-alert buffer changes low alert threshold An input card leads through the rule threshold = 54 mg/dL x (1 + buffer / 100) to the low alert threshold result. INPUT PAGE INPUT APPLY THE RULE predict calculate check units OUTPUT RESULT
Walk the arrows. The buffer moves the alarm above the danger line to cover sensor error.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline is 15 %.

  2. 2

    Name the relationship. threshold = 54 mg/dL x (1 + buffer / 100)

  3. 3

    Substitute with units. 54 x 1.15 = 62.1 mg/dL

  4. 4

    Read the result. Keep the unit beside the value. Use it only inside the technical boundary on this page.

Predict, then change low-alert buffer

Try Predict the direction of threshold = 54 mg/dL x (1 + buffer / 100). Test another low-alert buffer, then compare low alert threshold.

15 %
Chapter baseline
Low alert threshold

Observe The buffer moves the alarm above the danger line to cover sensor error. Reset low-alert buffer to 15 and compare low alert threshold.

Explain The buffer moves the alarm above the danger line to cover sensor error.

Check yourself

What should you do before trusting a moved-control result?
Answer: Predict its direction, apply the shown relationship, keep the units, and reset to the worked baseline.
What does this small model leave out?
Answer: Only low-alert buffer moves here. Field effects named in the technical boundary stay fixed.

Honesty note. This teaching model changes only low-alert buffer. It is not a field prediction.

TryUse Check derivation with 7.8% MARD, the 54 mg/dL danger line, and the proposed 62 mg/dL low alert.
ObserveAt a true 60 mg/dL, the error span reaches about 55-65 mg/dL, so an unbuffered 54 mg/dL trigger can warn too late.
ExplainThe 62 mg/dL threshold turns the sensor's 7.8% uncertainty into clearance above the clinical cutoff, rather than treating the displayed reading as exact truth.

Ready: use the stated baseline inputs, then compare each displayed result.

Ada: This chapter mixes a program-economics claim with a safety-critical one, and the safety number is the one that must be exactly right. Let me check the adherence return first, then the CGM buffer that decides when an insulin app warns a patient.

  • Adherence savings: 5,000 x (0.72 - 0.52) x 1,200 = 5,000 x 0.20 x 1,200 = 1,200,000 per year; net of a 420,000 program, 1,200,000 - 420,000 = 780,000, paying back in 420,000 / 780,000 x 12 = 6.46, about 6.5 months.
  • CGM low alert: a 15% buffer above the 54 mg/dL danger line is 54 x 1.15 = 62.1, so the app fires at 62 mg/dL, not 54.
  • CGM high alert: a 10% buffer below 250 mg/dL is 250 x 0.90 = 225, firing at 225 mg/dL.
  • Why the buffer is needed: at a true 60 mg/dL, a 7.8% MARD spreads the reading across 60 x 0.078 = 4.68, i.e. about 55-65 mg/dL, so a sensor value sitting comfortably above 54 can still hide a dangerous true glucose.

All consistent. The design meaning is that the safety buffer is not a guess – it is the sensor’s own error spec turned into distance: because the reading can drift several mg/dL above truth near the danger zone, alerting at 62 instead of 54 buys back exactly that uncertainty, which is why a safety-critical IoT design sizes its thresholds from the MARD rather than from the clinical cutoff alone.

Every number above is taken from the chapter’s own material and re-derived step by step.

Technical boundaries. Sensor drift, asymmetric glucose error, alarm delay, patient physiology, treatment response, and clinical consequences are outside the fixed 7.8% error and threshold arithmetic.