How Omnipod 5 Works

.gnl-ciq-v2 { max-width: 1100px; margin: 0 auto; color: var(–gnl-page-text, #203245); font-family: var(–gnl-body-font, Arial, Helvetica, sans-serif); font-size: 18px; line-height: 1.7; } .gnl-ciq-v2, .gnl-ciq-v2 *, .gnl-ciq-v2 *::before, .gnl-ciq-v2 *::after { box-sizing: border-box; } .gnl-ciq-v2 p { margin: 0 0 16px 0; } .gnl-ciq-v2 h1, .gnl-ciq-v2 h2, .gnl-ciq-v2 h3 { color: var(–gnl-page-navy, #0f2741); line-height: 1.2; margin: 0 0 16px 0; font-family: var(–gnl-font, Arial, Helvetica, sans-serif); } .gnl-ciq-v2 h1 { font-size: 42px; font-weight: 700; } .gnl-ciq-v2 h2 { font-size: 30px; font-weight: 700; } .gnl-ciq-v2 h3 { font-size: 22px; font-weight: 600; } .gnl-ciq-v2 a { color: var(–gnl-page-navy, #0f2741); font-weight: 700; text-decoration: underline; text-underline-offset: 2px; } .gnl-ciq-v2 ul, .gnl-ciq-v2 ol { margin: 0 0 18px 20px; padding: 0; } .gnl-ciq-v2 li { margin-bottom: 8px; } .gnl-ciq-v2__hero { background: linear-gradient(135deg, #f0f6ff 0%, #ffffff 100%); border: 1px solid var(–gnl-page-line, #d7e2ec); border-radius: 18px; padding: 32px; box-shadow: 0 4px 14px rgba(16,38,63,0.06); margin: 0 0 28px 0; } .gnl-ciq-v2__kicker { margin: 0 0 10px 0; font-size: 13px; font-weight: 700; letter-spacing: 0.08em; text-transform: uppercase; color: var(–gnl-page-navy, #0f2741); } .gnl-ciq-v2__title { margin-bottom: 12px; } .gnl-ciq-v2__lead { font-size: 20px; color: var(–gnl-page-text, #203245); max-width: 880px; } .gnl-ciq-v2__card { background: var(–gnl-page-card-bg, #ffffff); border: 1px solid var(–gnl-page-line, #d7e2ec); border-radius: 18px; padding: 28px; box-shadow: 0 4px 14px rgba(16,38,63,0.06); margin: 0 0 24px 0; } .gnl-ciq-v2__card–soft { background: var(–gnl-page-soft, #f7fbff) !important; } .gnl-ciq-v2__card–highlight { background: linear-gradient(135deg, #eef5fb 0%, #f7fbff 100%) !important; } .gnl-ciq-v2__callout { background: var(–gnl-page-callout-bg, #f0f6ff); border-left: 5px solid var(–gnl-page-navy, #0f2741); border-radius: 0 14px 14px 0; padding: 18px 18px 18px 20px; margin: 18px 0; } .gnl-ciq-v2__callout p:last-child, .gnl-ciq-v2__callout ul:last-child { margin-bottom: 0; } .gnl-ciq-v2__small-note { font-size: 14px; color: var(–gnl-page-muted, #607387); margin: 0; } .gnl-ciq-v2__tag-row { margin: 8px 0 18px 0; } .gnl-ciq-v2__tag { display: inline-block; padding: 6px 10px; border-radius: 999px; background: var(–gnl-page-tag-bg, #eef5fb); color: var(–gnl-page-navy, #0f2741); border: 1px solid var(–gnl-page-line, #d7e2ec); font-size: 13px; font-weight: 700; margin: 0 8px 10px 0; } .gnl-ciq-v2__button-row { display: flex; flex-wrap: wrap; gap: 12px; margin: 18px 0 14px 0; } .gnl-ciq-v2__button { display: inline-block; padding: 14px 20px; border-radius: 12px; font-weight: 700; font-size: 15px; line-height: 1.2; text-decoration: none !important; transition: all 0.2s ease; } .gnl-ciq-v2__button–primary { background: var(–gnl-page-navy, #0f2741); color: #ffffff !important; border: 1px solid var(–gnl-page-navy, #0f2741); } .gnl-ciq-v2__button–secondary { background: #ffffff; color: var(–gnl-page-navy, #0f2741) !important; border: 1px solid var(–gnl-page-line, #d7e2ec); } .gnl-ciq-v2__table-wrap { width: 100%; overflow-x: auto; border: 1px solid var(–gnl-page-line, #d7e2ec); border-radius: 16px; background: #fbfdff; margin: 18px 0 22px 0; } .gnl-ciq-v2__table { width: 100%; border-collapse: collapse; min-width: 600px; } .gnl-ciq-v2__table th { background: #eef3f8; color: var(–gnl-page-navy, #0f2741); font-size: 14px; font-weight: 700; text-align: left; padding: 12px 14px; border-bottom: 1px solid var(–gnl-page-line, #d7e2ec); } .gnl-ciq-v2__table td { font-size: 15px; padding: 12px 14px; border-top: 1px solid #e3ebf2; vertical-align: top; } .gnl-ciq-v2__table tbody tr:nth-child(even) { background: #f9fcff; } @media (max-width: 760px) { .gnl-ciq-v2 { font-size: 16px; } .gnl-ciq-v2__hero { padding: 20px; } .gnl-ciq-v2__card { padding: 20px; } .gnl-ciq-v2 h1 { font-size: 30px; } .gnl-ciq-v2 h2 { font-size: 24px; } }

AID System Explainer — Omnipod 5

Omnipod 5: How the system works and what the GNL framework represents

AID Systems Omnipod 5 Educational

The Omnipod 5 is a tubeless, waterproof, fully closed-loop automated insulin delivery (AID) system. This page explains how the system works, how the GNL Multi-System Explorer represents its responsiveness, and what the five educational calibration band levels describe.

Important: the “calibration band” is an educational expression, not a device parameter. The Omnipod 5 app does not contain a setting called a calibration band. This term is used in the GNL framework only as an educational way to describe the range of responsiveness the algorithm can operate within. You will not find it in your Omnipod 5 app. Any discussion about adjusting responsiveness must involve your diabetes care team.

Section 1: What the Omnipod 5 is

The Omnipod 5 is a tubeless, waterproof patch pump system that combines the Omnipod 5 Pod with a Dexcom G6 or G7 continuous glucose monitor (CGM). What makes it architecturally distinctive among AID systems is that the closed-loop algorithm runs on the Pod itself โ€” not on a companion phone or controller. This means the system continues to dose insulin and respond to glucose trends even when the phone is out of range, switched off, or left in another room.

The Pod adheres directly to the skin and contains both the insulin reservoir and the infusion mechanism. There is no tubing. This design removes the physical tether common to other pump systems and is often cited by users as a reason they chose this platform.

What makes Omnipod 5 distinctive

  • Tubeless, on-body design. The Pod adheres directly to skin โ€” no tubing connects pump to cannula. The Pod is waterproof.
  • Algorithm on the Pod, not the phone. Closed-loop dosing continues autonomously even when the phone is not nearby. The phone app is used for bolusing and monitoring, but is not required for the algorithm to function.
  • Personalised glucose target. The user sets a glucose target in the app. This is the primary mechanism through which responsiveness is adjusted. A lower target instructs the algorithm to work more aggressively toward a tighter glucose level; a higher target is more conservative.
  • Algorithm-led at lower responsiveness settings. When the target is set higher and bolusing behaviour is less consistent, the system takes on more of the management. This can be appropriate for periods when active engagement with the system is lower.
  • User behaviour matters more at higher responsiveness settings. When the target is set lower, the algorithm works harder to tighten glucose โ€” but it relies on accurate carb counting and consistent meal bolusing to perform at its best. At the most responsive settings, missing boluses or inaccurate carb entries are more likely to result in visible glucose excursions.
  • Compatible CGMs. Omnipod 5 is currently approved for use with Dexcom G6 and Dexcom G7.

The GNL framework uses the term “calibration band” as an educational label for the range of responsiveness described above. This is not a term or setting that appears in the Omnipod 5 app. It is a representation layer only, created to allow educational exploration of how the algorithm might behave at different points along the responsiveness spectrum.

Section 2: The primary levers โ€” target level and active insulin time

In the GNL Multi-System Explorer, Omnipod 5 responsiveness is represented through two primary levers: target level and active insulin time (AIT). Together, these determine how aggressively or conservatively the algorithm operates within the GNL five-level framework.

Target level

The glucose target set in the Omnipod 5 app is the most direct lever on system responsiveness. The target is expressed in mmol/L (or mg/dL in other regions) and can typically be set between 5.6 mmol/L and 8.3 mmol/L (100 mg/dL to 150 mg/dL). The algorithm continuously works to bring glucose toward this target by adjusting basal delivery and applying automated micro-corrections.

A lower target means the algorithm is working toward a tighter glucose level. The system will reduce basal rate more aggressively when glucose trends low relative to that target, and apply correction insulin more readily when glucose trends high. At these settings, the on-board carb ratio logic is more sensitive to what the user boluses โ€” accurate meal bolusing becomes more important.

A higher target means the algorithm operates with more tolerance. It is less likely to apply aggressive correction and tends to ride glucose at a slightly higher level before responding. This can smooth out the experience for users who are less consistent with meal bolusing, or for periods when life is more variable.

Active insulin time (AIT)

Active insulin time describes how long the system considers insulin to remain active after delivery. A shorter AIT means the system treats insulin as clearing faster, which affects correction behaviour โ€” the algorithm is willing to deliver additional correction sooner because it estimates less insulin is still working. A longer AIT means the system is more cautious about stacking, holding back on additional corrections because it estimates more insulin is still on board.

In the GNL framework, shorter AIT is paired with lower targets at the more responsive levels (Levels 4 and 5), while longer AIT is paired with higher targets at the more conservative levels (Levels 1 and 2). This combination determines the overall aggressiveness profile: lower targets + shorter AIT = more aggressive; higher targets + longer AIT = more conservative.

How target level and AIT map to the five levels

The five levels in the GNL framework combine target level and AIT into discrete bands, each with associated properties: a target style, an AIT setting, a carb ratio expression, a behaviour requirement, and a characterisation of whether the system leans more algorithm-led or more user-led. These are educational approximations of average tendencies across the spectrum โ€” they are not precise descriptions of any individual’s experience.

Target level and active insulin time are the primary levers in the GNL framework for Omnipod 5. The five levels are educational representations of how responsiveness varies along the system’s operating range โ€” always as a starting point for discussion with a diabetes care team, never as a prescription.

Section 3: The five educational calibration band levels

The table below summarises the five levels used in the GNL framework. Each level reflects a different point along the responsiveness spectrum. All descriptions are educational approximations of average tendencies โ€” individual experience varies considerably, and the GNL explorer outputs are a starting point for exploration, not a clinical recommendation.

Reminder: calibration band is an educational label, not a device setting.

LevelLabelAITCalibration band (educational)Target styleCarb ratio expressionBehaviour requirementSystem styleCF mmolCF mg/dL
5Very high2h150–200 mg/dLTightestVery strongVery highUser-tightest901600
4High2h 15175–225 mg/dLTightStrongHighUser-tighter951700
3Medium2h 30200–250 mg/dLBalancedMid bandModerateBalanced1001800
2Low2h 45225–275 mg/dLConservativeWeakLowAlgorithm-led1051900
1Very low3h250–300 mg/dLHighest toleranceVery weakVery lowAlgorithm-led1102000

Level 5 โ€” Very high responsiveness

At this level, the educational calibration band sits at 150–200 mg/dL and the active insulin time is set to 2 hours. The target style is the tightest in the framework, implying the algorithm is working hard to keep glucose close to the lower end of its operating range. The shorter AIT means the system treats insulin as clearing quickly, allowing more frequent corrections. The carb ratio expression is very strong, meaning the system’s on-board carb logic is most sensitive to meal entries. The behaviour requirement is correspondingly very high: this level tends to describe scenarios where the user is consistently counting carbohydrates accurately and bolusing reliably at each meal. The correction factor used in the GNL framework for this level is 90 mmol (1600 mg/dL).

This level is an educational approximation of an engaged user working at the most responsive end of the Omnipod 5 operating range. It is not appropriate for all users or all periods โ€” the higher behaviour requirement means that inconsistent bolusing is more likely to produce visible glucose excursions.

Level 4 โ€” High responsiveness

The calibration band here sits at 175–225 mg/dL and the active insulin time is 2 hours 15 minutes. The target style is tight and the carb ratio expression is strong. The behaviour requirement is high โ€” consistent bolusing and reasonably accurate carb counting tend to characterise users who achieve results toward this end of the spectrum. The correction factor is 95 mmol (1700 mg/dL). The system style leans user-tighter: the algorithm is responsive, but the user’s bolusing behaviour remains a material input to the overall result.

Level 3 โ€” Medium responsiveness

The calibration band sits at 200–250 mg/dL and the active insulin time is 2 hours 30 minutes. Target style is balanced, carb ratio expression is mid-band, and the behaviour requirement is moderate. The correction factor is 100 mmol (1800 mg/dL). This level represents a midpoint on the responsiveness spectrum โ€” the system is neither operating at its most aggressive nor its most tolerant. Many people find that this band reflects their everyday experience on Omnipod 5 when managing meals with reasonable consistency.

Level 2 โ€” Low responsiveness

At this level, the calibration band sits at 225–275 mg/dL and the active insulin time is 2 hours 45 minutes. The target style is conservative and the carb ratio expression is weak, meaning the algorithm’s on-board carb logic has less influence on the output. The behaviour requirement is low. The correction factor is 105 mmol (1900 mg/dL). The longer AIT means the system is more cautious about stacking corrections. The system style is algorithm-led: the system takes more of the management responsibility and is less dependent on consistent user bolusing. This level may reflect periods of lower engagement, illness, or significant life disruption โ€” or simply a preference for more system-led management.

Level 1 โ€” Very low responsiveness

The calibration band sits at 250–300 mg/dL and the active insulin time is 3 hours. The target style is at its highest tolerance and the carb ratio expression is very weak. The behaviour requirement is very low โ€” the algorithm is working at its most autonomous. The correction factor is 110 mmol (2000 mg/dL). The longest AIT in the framework means the system is at its most cautious about correction stacking. The system style is firmly algorithm-led. This level is an educational representation of the system operating in its most conservative mode, with the user providing minimal active input beyond the pump being worn and the CGM functioning. It tends to describe scenarios where the glucose target set in the app is at the more conservative end, or where bolusing is infrequent.

All five levels are educational approximations. They describe average tendencies โ€” not guarantees of performance at any individual setting. Real-world results depend on many additional factors: CGM accuracy, infusion site quality, carbohydrate absorption variability, physical activity, illness, stress, and hormonal variation. The GNL explorer generates exploratory output ranges. These are starting points for conversation with a diabetes care team, not targets to hit or numbers to programme into a device.

Section 4: How the GNL shared engine works

The GNL Multi-System Explorer uses a shared calculation engine that applies the same underlying logic across all four AID systems it covers. This section explains the key components of that engine as they apply to Omnipod 5. All values are educational approximations โ€” they are not device settings and should not be entered into any device without clinical review.

Sensitivity class

The engine assigns each set of inputs a sensitivity class โ€” a broad characterisation of how sensitive the individual’s insulin response is estimated to be. Sensitivity class is derived from the total daily dose (TDD), weight (where entered), and other contextual factors. It influences which region of the correction factor table and carb ratio range the engine draws from. Higher insulin sensitivity tends to be associated with lower TDD and lower body weight; lower sensitivity tends to be associated with higher TDD and higher body weight. These are population-level tendencies โ€” individual variation is considerable.

Correction factor rule

The correction factor (CF) โ€” sometimes called insulin sensitivity factor โ€” describes how far glucose is estimated to fall per unit of correction insulin. In the GNL framework, CF for Omnipod 5 is calculated using a divisor that varies by calibration band level: from 90 (mmol) at Level 5 to 110 (mmol) at Level 1, or equivalently 1600 to 2000 in mg/dL units. These divisors are educational approximations of how AID algorithm responsiveness interacts with correction sensitivity. The formula used is: CF = divisor ÷ TDD. The result is expressed as mmol/L per unit (or mg/dL per unit).

In the actual Omnipod 5 device, correction sensitivity is managed by the algorithm autonomously โ€” users do not programme a correction factor in the same way as a traditional pump. The GNL CF values are therefore an educational lens for exploring how correction sensitivity might vary across the responsiveness spectrum, not literal device settings.

Basal and bolus distribution

The AID system context changes the traditional understanding of basal and bolus distribution. In closed-loop mode, the Omnipod 5 continuously modulates basal delivery based on real-time CGM data, meaning the proportion of insulin delivered as programmed basal versus automated correction is dynamic and will vary from day to day. The GNL engine uses an estimated basal/bolus split as one reference point in the shared calculation model, but this is an approximation โ€” it does not reflect the actual on-device distribution on any given day.

Carb ratio logic

Carb ratio (CR) โ€” the number of grams of carbohydrate one unit of insulin covers โ€” is used in the GNL engine to generate carb-informed output where daily carbohydrate intake is entered. The CR values used in the engine are derived from the TDD and adjusted by the calibration band level, which modifies the carb ratio expression (very strong at Level 5, very weak at Level 1). A stronger carb ratio expression means more insulin per gram of carbohydrate, consistent with a more responsive system setting. A weaker expression means less insulin per gram โ€” more conservative.

In the Omnipod 5 app, carb ratio is a user-programmable setting. However, the algorithm incorporates learning and adapts around the set values over time. The GNL framework’s CR is therefore best understood as an educational representation of how carb coverage might shift across the responsiveness spectrum, not as a direct input recommendation.

Context summary note

When the GNL explorer generates output for Omnipod 5, the context summary shown alongside the output will display the calibration band level as an educational label. This is a representation created by the GNL framework โ€” it is not a parameter from the Omnipod 5 device, its app, or Insulet’s published documentation. It is there to help the user and their care team understand where on the responsiveness spectrum the explorer’s assumptions sit.

Section 5: How to use the explorer output

The GNL Multi-System Explorer generates exploratory output ranges โ€” not prescriptions, not targets, and not device settings. Understanding what the output is and what it is not helps make the most of it.

What the output describes

The output describes a range of estimated insulin parameter values โ€” correction factor, carb ratio, and basal reference โ€” based on the inputs entered and the calibration band level selected. These values represent educational approximations of what those parameters might look like in a person with broadly similar characteristics who is using Omnipod 5 at the corresponding responsiveness level. They are derived from population-average tendencies and well-established insulin dosing relationships.

The output is most useful as a structured starting point โ€” a way to put approximate numbers on a conversation about whether current settings feel broadly appropriate, and to explore how they might shift if responsiveness were changed. Many people find the output helpful for framing a question to bring to a clinic appointment, rather than as an answer in itself.

What the output is not

  • It is not a recommendation to change any device setting.
  • It is not a calculation of your individual insulin requirements.
  • It is not validated against clinical trial data for any individual.
  • It is not a substitute for assessment by a diabetes care team.
  • It does not account for CGM accuracy, infusion site variation, carbohydrate absorption differences, or any of the many individual factors that shape real-world glucose outcomes.

Uncertainty is built in

The output is presented as a range rather than a single number deliberately. The range reflects the genuine uncertainty in applying population-average relationships to any individual. Someone at the lower end of the output range and someone at the upper end may both be entirely reasonable โ€” the spread is an honest acknowledgement that there is no single correct answer.

This is consistent with how AID systems tend to behave in practice: two people with similar characteristics using the same system at the same responsiveness level often end up at different calibrated values because of the many variables the algorithm cannot fully account for at a population level. Your CGM data, reviewed over time with your care team, is the most reliable guide to what is working for you.

The explorer output is a starting point for exploration and discussion โ€” not a prescription. Bring the output to your next clinic appointment and use it as a way to open a conversation, not close one.

Section 6: Limitations and disclaimer

Calibration band: educational representation only

The “calibration band” is an educational expression layer created by GNL. It is not a real parameter in the Omnipod 5 device or app. It is not a term used by Insulet in their clinical documentation, training materials, or device software. It exists solely within the GNL educational framework to describe, at a conceptual level, the responsiveness spectrum the algorithm can operate across. Any reference to “calibration band” in GNL content โ€” including this page, the explorer, and any associated resources โ€” should be understood in this context.

If you encounter the term “calibration band” in any other context in relation to Omnipod 5, it is not connected to the GNL framework and may have a different meaning. Always refer to official Insulet documentation and your diabetes care team for device-specific guidance.

Educational purpose only

This page, and all GNL content relating to the AID system explorer, is for educational exploration. It describes average responses and general principles drawn from insulin dosing literature and general AID system behaviour. It does not constitute individual clinical guidance, and it does not incorporate your personal clinical history, medical records, or device data.

GNL is an educational resource for people living with type 1 diabetes. It is not a clinical decision support tool and does not output clinical recommendations. Nothing on this page should be used as the basis for changing any insulin dose, device setting, or management approach without discussion with a qualified diabetes care team.

No proprietary claims

The GNL framework uses publicly available information about AID systems combined with established insulin dosing principles. It makes no claim to represent the proprietary algorithm logic of Omnipod 5, to have access to Insulet’s internal parameters, or to replicate the behaviour of the on-device algorithm. The five calibration band levels are GNL constructs, not Insulet categories.

Individual variation

Glucose outcomes in type 1 diabetes are shaped by an exceptionally wide range of factors: insulin sensitivity that varies hour to hour and day to day, carbohydrate absorption that varies by food composition and gut transit, physical activity, sleep quality, stress, illness, hormonal cycles, infusion site condition, CGM sensor accuracy, and much more. No population-average framework can capture this variation at an individual level. The explorer output acknowledges this by presenting ranges rather than single values โ€” and by consistently pointing to CGM data and care team review as the appropriate next step.

This content is for educational exploration only. It describes average responses and general principles. It is not medical advice and cannot replace individual clinical guidance from your diabetes care team.

Use the AID system explorer

The GNL Multi-System Explorer generates exploratory output ranges for Omnipod 5 and three other systems. Use it as a starting point for discussion with your diabetes care team.

This content is for educational exploration only. It describes average responses and general principles. It is not medical advice and cannot replace individual clinical guidance from your diabetes care team.

Part of the GNL AID Systems guide

Verified by MonsterInsights