🍬 Sweet MirandaDiabetes Intelligence
… ◐ Theme
…
—
Glucose Target 70–180 Carbs (g) Bolus (U) Micro-bolus (SMB) Basal given · each 5 min (U) Trio suggested Programmed schedule No loop record Trio forecast →
🧪 Simulatordigital twin · rebuilt from her insulin + carbs record with Trio's own math
Starting the simulator…
Real (G6) Twin — the reading N min earlier + what insulin and carbs should have done since Sim forecast (only what is known now) Rose more than the record explains Fell more than the record explains
📊 Forecast scoreboard — which forecast predicts her best?
—
mg/dL
waiting for the sensor…

🔁 Loop no loop data

🎯 Today

Hour by hour

Basal target = what her schedule calls for in that hour · Basal given = what the pod actually delivered (Trio's temp basals, the schedule between them, nothing while the pod was suspended) · Loop ran = share of the hour Trio was looping. Tap an hour to open it 5 minutes at a time.
… 🔔 alerts in this tab

Pattern statistics

Time in range

Every day in the window in range grows up from the line · lows hang below it · dashed line = 70% goal · tap a range above to light it up

Ambulatory Glucose Profile her typical day

How to read it
  • Every day in the window is stacked onto one 24-hour clock. This is what a normal day looks like for her.
  • Bright line = her typical day (the middle reading at that time). It turns cyan in range, yellow/orange when high, pink when low.
  • Dark band = half of her days fall inside it.
  • Faint band = 9 out of 10 days. Top edge = her rough days; bottom edge = her lowest days.
  • Goal: the line and the dark band inside the 70–180 zone. Narrow band = that time of day is predictable; wide band = it changes a lot day to day.
What it is telling us

    Hour of day

    Each column is one hour of the clock across the whole window. In ranges: cyan grows up from the line, lows hang below it, dashed line = 70% goal. Hover or tap a column for the numbers.

    Insulin & carbs

    Day by day basal at the bottom, bolus on top, dashed line = her basal schedule · carbs typed · loop running
    Basal (background insulin) Bolus (meals + corrections) Basal schedule Carbs typed (g)
    When it goes in average per day, by hour of the clock
    Bolus with carbs typed Bolus with no carbs typed (a correction, or carbs not entered) Carbs typed
    Carbs typed into the calculator the endo's ask — every bolus should carry its carbs
    In plain words: basal is the slow background insulin the pod gives all day (Trio raises and lowers it every 5 minutes); bolus is the insulin she gives for food or to bring a high down. Before Trio (Sep 23) the numbers are the Omnipod 5's own daily totals. On Trio days basal is her schedule plus or minus the loop's changes, taken from the Basal tab's 5-minute record — an estimate, marked "est.". A bolus with no carbs typed is either a correction or a meal whose carbs were never entered.

    Lows & long highs

    Week at a glance which days and times run high or low

    How to read it: each tile is her average glucose on that weekday during that part of the day, across the window (small number = % of that time in range). A row full of yellow/orange = a hard day of the week. A column = a hard time of day. A pink dot = lows there (4% of the time or more).

    Where the A1C is hiding the 3-second version

    Day by day

    Worked out straight from the raw record each time this opens — every sensor reading and every dose. Insulin before Trio = the pump's own daily totals. Trio days: bolus = the sum of Trio's boluses; basal = her schedule ± the loop's changes from the Basal tab's 5-minute record (marked est.). Today is so far.
    DayIn rangeLowHighAvgGMICV BasalBolusCarbsSensor data
    A correction is what the pod or the loop did against the schedule — in response to glucose. Above the line: more basal than programmed (usually answering a high). Below: less, or none (usually heading off a low). A big correction on a bad day is the pump answering the day, not the cause of it. What to change belongs to her endocrinologist.

    🧮 Insulin math basal per hour · what 1 unit does · 100 points

    Basal given that hour (average U, fully recorded hours only) Programmed rate

    Why the unit-of-insulin numbers don't come from basal: the loop gives more basal because she is high and cuts it because she is dropping, so basal and glucose move backwards against each other. The clean signal is a correction — insulin with no food — and what her glucose did over the next 3 hours. The 100-point figure is her programmed correction factor, the clinic's number; dose through Trio, whose calculator also subtracts insulin already on board.

    The corrections behind "1 unit lowers her"

    Window

    📉📈 Corrections day by day delivered − programmed, units per day

    More than programmed Less than programmed What Trio wanted (open loop — not delivered) Time in range (right axis)

    Omnipod 5 days: the pump's own daily basal total minus the programmed schedule. Trio days: the sum of every temp basal against the schedule — zero while the loop runs open.

    🔎 One day, every 5 minutes

    Glucose Above schedule Below schedule / stopped Trio wanted Trio auto-bolus (SMB)
    Pod strip: Automated Suspended At maximum Trio temp basal On schedule (Trio) No pod / unknown

    🕐 By hour of day how often basal left the schedule, share of pod time

    At maximum / temp above schedule Suspended — no basal Average glucose

    🧪 Daily study

    Past studies

    🗂️ Where every basal record lives and where the new ones land

    📋 5-minute basal data, day by day

    A slot counts as known when what the pod delivered in that 5 minutes is on record: an Omnipod 5 Auto Events screenshot, a suspended stretch (0 U), a Trio temp basal or suspend, or a Trio pod running its schedule with no temp. Omnipod 5 automated minutes without a screenshot are not knowable — the pump only reported a daily total.

    🫛 Omnipod 5 era · the pod's 5-minute Auto Events (screenshot archive, before Trio took the pod on 9/24)
    What the pod did, every 5 minutes. Read from the Omnipod 5 app's History ▸ Auto Events screenshots Miranda sent to the "My Princess" chat; every glucose value was checked against Dexcom before a screenshot was kept.

    Day

    Glucose and automated insulin

    Sensor glucose (Dexcom) Units the pod gave in that 5 minutes (right axis) 0 U — delivery paused Not captured

    Hour by hour

    Screenshots received last 14 days

    🎯 The goal goal A1C

    🏁 Pace to goal

    Pace line — the last lab to the goal 14-day GMI, day by day Lab draw Projected A1C at the next draw

    📆 This week's effort last 7 days · each tile shows the 7 days before

    🗓️ Fourteen days, day by day colour = average vs the goal average · red badge = lows over 4%

    🧭 Where to do better this week last 7 days · ranked by how much each part of the day adds to the gap

    🧪 Every A1C on record

    DateA1CChangeGMI that monthNote

    📈 GMI trend 14-day rolling estimate vs lab draws

    📚 The 90-day picture — what the lab will actually measure, beside what the pump did

    What the pump is doing on the way last 30 days · each tile shows the 30 days before

    Insulin and pod figures are left ungraded on purpose. The loop sets basal from glucose — it gives more on a day that runs high and suspends when it predicts a low — so these numbers describe how the pump responded, not whether a setting is right.

    Where the gap lives 90 days · glucose beside what the pod and boluses did

    Win days vs loss days 90 days

    Questions on the 90-day path rules only · for the care team

    📄 Reports for the visit

    Report

    Generated from the CGM record for the selected period, compared with the period before it. Saved reports build a history you can hand to the care team — and the full record is archived to B2 nightly, so these stay reproducible long after the vendors have forgotten the data.
    🔒 Her chart
    Kept private. Visit summaries, labs, pump-settings sheets, imaging and body scans live in a private bucket with no public policy at all — every link is signed when you click it and dies 15 minutes later. Only an approved WilHQ account holding Sweet Miranda can open a file.

    📥 Add a document

    📚 Chart

    Every change here is a proposal, not a command. It travels to Miranda's iPhone through our Nightscout; Trio shows her each change and applies it only after her Face ID — or after Face ID on a parent's phone that her phone approved as an approver (LoopFollow ▸ Sweet Miranda). Basal and pump limits go to the pod first, and if the pod refuses, nothing is applied. Maresca knows we loop; a therapy change still deserves a message to her before it is sent.

    📨 Proposal builds itself from your edits below

    🍎 Food bank what her EAT + DOSE screen offers · nutrients feed the Simulator

    🔏 Face ID approvers parents' phones that may approve for her

    🕒 Proposals sent what the phone answered

    🗂️ Snapshots from the phone one per change on the device

    📡 Feeds every source, its last run, and what it can give

    What each source can actually give us

    SourceAPI?DelayGivesVerdict

    🧪 Trio build open-source loop · Omnipod (dev branch)

    Trio is not FDA-cleared and Insulet does not support it. Since 2026-09-24 it owns Miranda's pod; the Omnipod 5 app and spare pods remain the fallback. Its safety limits are her endocrinologist's numbers.

    Setup

    🧭 Open-source map — the DIY diabetes ecosystem (Loop, AAPS, xDrip+, Nightscout and friends)
    DIY closed-loop systems are not FDA-approved. Community projects, entirely your own risk — no manufacturer, no regulator, no support line. Miranda's endocrinologist is part of every decision here.

    Filter