Skip to content

**SiteAtlas** Pump and CGM site rotation tracker#2427

Open
taylorpatterson-T1D wants to merge 260 commits intoLoopKit:devfrom
TaylorJPatterson:feat/SiteAtlas
Open

**SiteAtlas** Pump and CGM site rotation tracker#2427
taylorpatterson-T1D wants to merge 260 commits intoLoopKit:devfrom
TaylorJPatterson:feat/SiteAtlas

Conversation

@taylorpatterson-T1D
Copy link
Copy Markdown

@taylorpatterson-T1D taylorpatterson-T1D commented May 4, 2026

Screenshot 2026-05-04 at 3 52 34 PM

Summary

How many times have you changed your pump site or CGM sensor and thought "wait, where did I put the last one?" Site Atlas tracks where you place your infusion set, tubeless pump or sensors on a visual body map so you never have to guess. Proper site rotation prevents tissue damage (lipohypertrophy) that messes with insulin absorption and sensor accuracy. Inspired by Shaun Sabo's work on Site Cycle. Included in the Loop AI PowerPack.

The Problem That We're Solving

People with Type 1 diabetes need to rotate where they place pump infusion sets and CGM sensors. Reusing the same spots causes scar tissue that absorbs insulin unpredictably and gives less accurate CGM readings. But there's no way to track this in Loop today — most people just try to remember, and memory isn't reliable when you're changing sites every 3 days for decades.

New Feature's Impact

Site Atlas adds a visual body map where you log your pump and sensor placement. Color-coded pins tell you at a glance which areas are fresh (red=avoid) vs. healed (green=safe to reuse). The app suggests where to go next based on which sites are oldest.

What it does

  • Visual body map (front and back) where you tap to log where you placed a site
  • Color-coded pins: red (just placed) → orange (healing) → yellow (almost ready) → green (safe to reuse) over 14 days
  • 12 recommended placement zones — grey highlighted areas on the body map showing where sites should go (abdomen, thighs, arms, buttocks)
  • Toggleable zones — turn off zones you don't use via a collapsible "Enable Placement Zones" section in Settings
  • Next Up recommendations — sorted oldest-first so you always know where to go next
  • Prompted logging — when you deactivate a pump through Loop, it asks you to log the new site
  • Manual logging anytime from Settings
  • Touch-drag-drop pin adjustment with dramatic visual feedback (pin grows large when grabbed)
  • Proximity warning — while dragging a pin, it turns green in safe areas and red when too close to a recently-used site
  • Body bounds enforcement — pins snap to the body outline if dropped outside the silhouette
  • Existing sites shown as faded reference pins when placing a new one
  • Edit any entry's date/time, type, and notes
  • Hide locations you no longer use (swipe right → Hide)
  • Tracks both pump sites and CGM sensors with different icons

User-configurable settings

  • Enable/disable Site Atlas entirely
  • Log Pump Site / Log Sensor Site — manual logging buttons
  • Body map — swipeable front/back view with all your pins
  • Enable Placement Zones — collapsible toggle list (12 zones, shows "X of 12 active")
  • Next Up — oldest-first recommendation list
  • History — grouped by month, tap to edit, swipe to hide or delete
  • Notes — add optional notes to any entry
  • Delete All — clear everything with confirmation

How it works

  1. When you deactivate a tubeless pump in Loop, Site Atlas pops up asking where you placed the new one
  2. Tap the body map to place a pin, drag to adjust
  3. The pin changes color as you drag — green = safe spot, red = too close to a recent site
  4. Grey zones on the map show recommended placement areas
  5. Save the entry — it's stored locally on your device
  6. Next time you need to change sites, check Next Up for the best location
  7. Green-colored entries at the top are your safest choices

Safety considerations

  • All data stored locally on-device only — not synced to iCloud or any external service
  • No changes to insulin delivery or Loop's core algorithm
  • Feature is off by default — must be explicitly enabled
  • 365-day automatic data retention with manual delete option

Architecture

  • 11 new files, all within Loop/Loop/ following Loop's layer-based architecture
  • 3 existing files modified with minimal changes (~21 lines total):
    • Managers/DeviceDataManager.swift — Posts notification on pump deactivation
    • Managers/LoopDataManager.swift — Initializes coordinator singleton
    • Views/SettingsView.swift — Adds NavigationLink to Site Atlas settings
  • Self-contained feature — removing SiteAtlas/ directories + 3 integration lines reverts cleanly
  • No changes to LoopKit or any other submodules
  • Developed from v3.10.0 DEV branch

New files

File Location Purpose
SiteAtlas_FeatureFlags.swift Services/SiteAtlas/ On/off toggle via UserDefaults
SiteAtlas_Models.swift Models/SiteAtlas/ Data types, theme colors, zones, age color scale
SiteAtlas_Storage.swift Services/SiteAtlas/ JSON persistence, 365-day pruning
SiteAtlas_Coordinator.swift Services/SiteAtlas/ Singleton, notification listener, public API
SiteAtlas_BodyMapView.swift Views/SiteAtlas/ Swipeable body map with draggable age-colored pins and zones
SiteAtlas_SiteSelectionSheet.swift Views/SiteAtlas/ Modal for logging new sites with proximity coloring
SiteAtlas_SettingsView.swift Views/SiteAtlas/ Settings, Next Up, zone toggles, history, edit sheet
BodyMapFront.png Resources/SiteAtlas/ Body outline — front
BodyMapBack.png Resources/SiteAtlas/ Body outline — back
Developer.md Documentation/SiteAtlas/ Developer documentation
User.md Documentation/SiteAtlas/ User guide

Screenshots

  1. Settings menu showing the Site Atlas entry (burnt orange map pin icon)
IMG_2180
  1. Body map with color-coded pins (front view)
IMG_2176
  1. Choosing a new site — pin placement with proximity coloring - hovering over recently used spot makes the placement icon orange or red depending on the time since last use. Green icons means good to go!
IMG_2179 IMG_2178
  1. Edit entry sheet (date picker, type, notes)
Screenshot 2026-05-04 at 8 12 12 AM
  1. History list with swipe actions
IMG_2177

Requesting review by @marionbarker based on availability.

taylorpatterson-T1D and others added 30 commits February 10, 2026 17:08
- Absorption time model: conservative adjustments anchored to Loop's
  3-hour default. FPU adds +0/+0.5/+1.0 hr (was +1/+2.5/+4), fiber
  +0/+0.25/+0.5 (was +0/+1/+2), meal size +0/+0.25/+0.5 (was +0/+1/+2).
  Cap reduced from 8 to 5 hours. Updated AI prompt and 3 examples.
- OCR routing fix: raised menu detection threshold from 1 to 5 significant
  lines and always include image on menu path to prevent food photo
  misclassification (fixes "Unidentifiable Food Item" on food photos).
- Inline "Why X hrs?" pill on Absorption Time row replaces standalone
  DisclosureGroup row. Purple centered pill with fixed width, expands
  reasoning on tap. Uses AIAbsorptionTimePickerRow when AI-generated.
Add LoopInsights feature: an AI-driven therapy settings advisor that analyzes
glucose, insulin, and carb data to suggest adjustments to Carb Ratios, Insulin
Sensitivity Factors, and Basal Rates.

Core components:
- Dashboard with therapy settings overview, pattern detection, and AI suggestions
- Configurable AI provider (OpenAI, Anthropic, Gemini, Grok, self-hosted)
- Data aggregation pipeline with test data fixtures from Tidepool
- Suggestion lifecycle: pending → applied/dismissed with full history
- AI personality settings (Supportive Coach, Clinical Expert, Dry Wit, Tough Love)
- Developer mode with auto-apply and test data toggles
- Secure API key storage via Keychain
- Safety guardrails: max 20% change per adjustment, one setting at a time
- Unit tests for models, data aggregation, and suggestion store

22 new files, 4 modified files across Views, View Models, Models, Services,
Managers, Resources, and Tests.
…ng, and UI refinements

- Wire real therapy settings writes via LoopInsightsSettingsWriter closure
- Schedule splitting: insert new entries when AI suggests times not in user's schedule
- Revert feature: restore pre-apply settings from suggestion history
- Settings Score (0-100) with TIR, Safety, Stability, GMI breakdown
- Clinical reasoning framework: AI now understands AID-specific patterns
  (corrections/day, basal/bolus ratio, time-of-day analysis, cross-setting interactions)
- All three settings visible in every AI prompt for cross-setting reasoning
- Pre-computed red flags injected into prompt (algorithm workload, basal % alerts)
- Stale-data guard: excludes manually reverted changes from recent context
- Suggestion merge: consolidates split AI responses into single cards
- Pre-Fill Editor: editable proposed values before applying
- Auto-applied notification banner
- Debug log with Copy Full Log for troubleshooting AI behavior
- Temperature forced to 0.0 for deterministic analysis
… advisor UI

Add Ask LoopInsights chat with AI advisor powered by therapy context and glucose data.
Background monitoring with configurable frequency and notification banners. New Trends
& Insights view with Daily/Weekly/Monthly/Stats/Advisor tabs. Dark gradient styling
for chat and trends views. Banner now includes Ask button to open chat directly.
…ports

Add clinical goal tracking (TIR, A1C, below-range, custom) with progress bars,
AI-powered 30-day pattern discovery with sick day and negative basal detection,
timestamped reflection journal with mood tags, and HTML-to-PDF report generation
with share sheet. Goals & Patterns accessible from the Dashboard navigation section.
… analysis

Add HealthKit biometric data (heart rate, HRV, steps, sleep, active energy, weight)
to the AI analysis and chat pipelines. Biometrics are read-only, independently
authorized, and gracefully degrade when individual types are unavailable.

New file: LoopInsights_HealthKitManager.swift
Modified: Models, DataAggregator, AIAnalysis, ChatViewModel, Coordinator,
FeatureFlags, SettingsView, DashboardView, pbxproj, Localizable.xcstrings
…nsights, Nightscout import

- Ambulatory Glucose Profile (AGP) chart with percentile bands and median line
- Clarity-style dashboard redesign: Glucose card, Time in Range 5-zone stacked bar,
  capsule period picker with exact Clarity colors (#C14F0C, #F0CA4C, #74A52E, #D36265, #7F0302)
- Caffeine tracker with half-life decay modeling and glucose correlation
- Meal insights with food response analysis and per-meal glucose impact
- Nightscout data import support
- Advanced analyzers for pattern detection
- 5-zone TIR breakdown (Very High/High/In Range/Low/Very Low) replacing 3-zone model
- Compact list section spacing for tighter dashboard layout
- Chat view UI refinements
…card fixes

P1: Parallel HealthKit queries via async let (6 concurrent fetches)
P2: Single-pass TIR zone counting (5-zone) replacing multiple filter passes
P3: Pre-fetch raw data in DataAggregator, cache for cross-component reuse
P4: Binary search for glucose lookups in FoodResponseAnalyzer
P5: Pre-sorted glucose samples with binary search in AdvancedAnalyzers
P6: Pre-compute AGP data in ViewModel instead of SwiftUI view body
P7: Static DateFormatter in LoopInsightsTimeBlock.formatTime
P8: Pre-sort schedule items before dose loops, pre-sort in ViewModel
P9: Pre-convert glucose to parallel arrays avoiding repeated doubleValue calls
P10: Pass precomputed hourly averages to circadian profile builder

Also: enhanced step/activity data in AI prompts with time-of-day breakdowns
and activity-glucose correlation analysis (2h lag), and meal card layout cleanup.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…y fixes

Glucose chart now operates in two modes: standard Ambulatory Glucose Profile
(24-hour overlay with percentile bands) for 14-day lookback, and Glucose Profile
(multi-day time series) for all other periods. Both modes include an info button
explaining the visualization. HealthKit glucose data supplements Loop store for
longer analysis periods. Chart data clears on period change to prevent stale labels.

Additional fixes across 22 files: improved HealthKit data pipeline reliability,
enhanced test data provider, refined food response analysis, and minor bug fixes
in background monitor, coordinator, caffeine tracker, and goals/trends views.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…y fixes

Glucose chart now operates in two modes: standard Ambulatory Glucose Profile
(24-hour overlay with percentile bands) for 14-day lookback, and Glucose Profile
(multi-day time series) for all other periods. Both modes include an info button
explaining the visualization. HealthKit glucose data supplements Loop store for
longer analysis periods. Chart data clears on period change to prevent stale labels.

Additional fixes across 22 files: improved HealthKit data pipeline reliability,
enhanced test data provider, refined food response analysis, and minor bug fixes
in background monitor, coordinator, caffeine tracker, and goals/trends views.
Bump all body text, headers, and stat values to full white for readability
on dark backgrounds. Replace .toolbarColorScheme (iOS 16+) with manual
toolbar principal title for compatibility. Restore UINavigationBarAppearance
approach in ChatView.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The 20-char limit was truncating food names (e.g. "Baked pastry with f…")
which made them unreadable in LoopInsights Meal Insights. The RowEmojiTextField
maxLength only restricts keyboard input, so longer programmatic values are safe.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Added steps for creating and using test data in developer mode for demos and feature functionality testing.
…ivity

CoreMotion-based activity detection that automatically applies user-selected
override presets when walking or running is detected. 7 new files, 2 modified.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Safety guardrails (3 layers of defense against dangerous therapy values):
- LoopInsights_SafetyGuardrails struct with clinical bounds mirroring LoopKit
  (CR 4-28 recommended/2-150 absolute, ISF 16-400/10-500, Basal 0.05-10/0.05-30)
- Post-parse validation rejects values outside absolute bounds and >25% changes
- AI prompt now includes absolute bounds with clamping instructions
- confirmApply() hard-blocks absolute violations
- applyEditedSuggestion() validates edited blocks against absolute bounds
- autoApplySuggestion() blocks anything outside recommended range (stricter)
- SuggestionDetailView shows orange warning banner and color-coded values
- DashboardView alert changes to "Safety Warning" with specific warnings
- Suggestion cards show orange triangle badge for guardrail warnings

Data-first AI prompts (all 4 AI interaction points):
- Chat, Analysis, Goals/Patterns, and Trends prompts now require every
  answer to cite the user's specific numbers — no generic diabetes advice
- Added "#1 RULE" blocks emphasizing real data over textbook answers

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Safety guardrails (3 layers of defense against dangerous therapy values):
- LoopInsights_SafetyGuardrails struct with clinical bounds mirroring LoopKit
  (CR 4-28 recommended/2-150 absolute, ISF 16-400/10-500, Basal 0.05-10/0.05-30)
- Post-parse validation rejects values outside absolute bounds and >25% changes
- AI prompt now includes absolute bounds with clamping instructions
- confirmApply() hard-blocks absolute violations
- applyEditedSuggestion() validates edited blocks against absolute bounds
- autoApplySuggestion() blocks anything outside recommended range (stricter)
- SuggestionDetailView shows orange warning banner and color-coded values
- DashboardView alert changes to "Safety Warning" with specific warnings
- Suggestion cards show orange triangle badge for guardrail warnings

Data-first AI prompts (all 4 AI interaction points):
- Chat, Analysis, Goals/Patterns, and Trends prompts now require every
  answer to cite the user's specific numbers — no generic diabetes advice
- Added "#1 RULE" blocks emphasizing real data over textbook answers
Combines FoodFinder (34 files) with LoopInsights (18 files) on a shared
history rooted in feat/LoopInsights. Resolves pbxproj, SettingsView, and
Localizable.xcstrings merge conflicts — both features coexist.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ivity

CoreMotion-based activity detection that automatically applies user-selected
override presets when walking or running is detected. 7 new files, 2 modified.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Passes the user's insulin type (e.g. Fiasp, Novolog) into the therapy
snapshot and AI prompts so the model can distinguish timing issues from
dosing issues based on pharmacokinetics.
# Conflicts:
#	Loop/Views/SettingsView.swift
The additionalSteps > 5 threshold was way too low — 9 steps in a
2-minute window was confirming as "Walking". Now requires a minimum
pace of 20 steps/min (40 steps for 120s window) to filter fidgeting
while still catching slow walks.
Pedometer fires callbacks every ~2.5s even with unchanged step count.
The stop timer was being restarted on every callback, preventing it
from ever reaching 0. Now only restarts when steps actually increase.
iOS delays timers when backgrounded (120s timer firing at 293s).
Using configured interval meant casual steps over 5 minutes passed a
bar designed for 2 minutes. Now uses actual elapsed time and requires
30 steps/min — e.g. 146 steps needed for a 293s delayed timer.
EventKit integration that scans calendars for keyword-matched events and
auto-activates presets with configurable lead time. Supports all calendar
providers, per-calendar filtering, and deactivation on event end.
Replaces the existing minimal chart touch highlight with a rich detail
popup showing glucose, IOB, COB, bolus, basal, preset, AutoPreset, and
heart rate data at any point on the glucose chart. Supports scrubbing
left/right with haptic feedback, auto-fades after 5 seconds, respects
safe areas in both orientations, and works standalone with optional
enhanced data when other features (AutoPresets, etc.) are enabled.
Only on feat/AllFeatures — individual feature branches keep stock Loop icon.
Replaces all 18 tracked PNGs in DerivedAssetsBase with purple PowerPack icon.
Track where you place insulin pump infusion sets and CGM sensors on a visual body map. Color-coded pins show site age (red = fresh, green = safe to reuse). Prompted logging on pump deactivation, manual logging anytime. Drag-and-drop pin adjustment with proximity-based coloring warns when placing near recently-used sites.

11 new files, 3 modified files, ~1,829 lines added.
@taylorpatterson-T1D taylorpatterson-T1D changed the title SiteAtlas — Pump and CGM site rotation tracker **SiteAtlas** Pump and CGM site rotation tracker May 4, 2026
- 12 recommended placement zones as grey ellipses on body map
- Toggleable zones via collapsible DisclosureGroup in Settings
- Pin expands to 110pt with halo on touch-drag
- Proximity-based color (green=safe, red=danger) during drag
- Body bounds clamping prevents pins outside silhouette
- Save button pinned to bottom of selection sheet
- Feature toggle takes effect immediately
- Updated body map images and app icon
- iOS 15 compatible (.strokeBorder instead of .stroke)
Loose PNGs in Resources/SiteAtlas/ weren't being included in the app
bundle despite correct pbxproj registration. Moved to imagesets in
DerivedAssetsBase.xcassets and simplified loading to Image("name").
CLGeocoder often returns shopping center names instead of the specific
restaurant. Added MKLocalSearch refinement that finds the closest food
venue within 100m and replaces the generic geocode name. Also updated
the AI prompt to include the restaurant name in the food title.
"Get help with Therapy Settings" now opens LoopInsights instead of the
blank DemoPlaceHolderView stub when LoopInsights is enabled.
onAppear on therapySettingsView fired too late — at the same instant
TherapySettingsView rendered its body, so the registry was still nil.
Moving it to SettingsView's top-level body ensures it fires when the
user opens Settings, before they navigate to Therapy Settings.
…ghts and AutoPresets

Internal data + thresholds stay canonical mg/dL; conversion happens at the
display + AI-prompt boundary via a new LoopInsights_GlucoseUnitContext helper.
AI prompts get a unit-context block so Claude responds in the user's unit;
canonical JSON fields (target_range_*_mgdl, ISF current/proposed_value) stay
mg/dL by explicit prompt instruction.

LoopInsights_Coordinator.init now requires displayGlucosePreference; the
dataStoresProvider tuple is extended from 5 to 6 elements. AutoPresets_Coordinator
and PreMealAdvisorService get the preference set during boot in LoopAppManager.

Display surfaces fixed: Dashboard, Trends, Meal Insights, Meal Debrief, Endo
Report, Caregiver Digest (text + HTML), Goals report, Suggestion Detail,
Settings tight-range stepper, AutoPresets override editor.

AI prompts updated: ChatViewModel, AIAnalysis (with mg/dL JSON-field rule for
ISF values), TrendsInsightsView, GoalsView, MealInsightsViewModel,
AutoPresets_AIAdvisor (with mg/dL JSON-field rule for target ranges).
A pizza on a paper menu was being identified off the menu text instead of
the visible plate. Three fixes:

- Require text bounding boxes to cover >75% of the image before routing
  through the menu-text path (previously: 5+ lines of any size triggered)
- Reframe menu-path prompt so visible food stays primary; OCR text is
  only used to identify the dish or restaurant
- Hoist LOCATION CONTEXT to the top of every prompt with REQUIRED
  venue-in-title and 📍-prefix rules that apply across image_types
Creates a second timed carb entry alongside the primary to cover the
delayed glucose rise from fat and protein. Toggle + slider live on
CarbEntryView; FoodFinder auto-populates macros and auto-flips the
toggle when computed FPU crosses the threshold (default 1.5).

- 10 new BolusPro files in Models/Resources/Services/Views (no LoopKit changes)
- Math: Trio gram formula (fat × 0.9 + protein × 0.4) × coverage % × slider
- Secondary NewCarbEntry post-dated +60 min, 6 hr absorption, foodType 🥩
- DataLayer bolusProEntry event (12 fields) for population analysis
- LoopInsights BehaviorInsights gains a BolusPro Patterns section
  (adoption, slider drift, auto-detect override, bonus distribution, source mix)
- Item exclusion in FoodFinder recomputes FPU and walks the toggle back
  when it drops below threshold (only when auto-detected)
- Documentation/BolusPro/ user + developer guides
Lifts the DataLayer event-recording call out of BolusPro_DataLayerHook
and into DataLayer_Coordinator's notification observer. BolusPro now
posts a single NotificationCenter event after each carb-entry save and
has zero external dependencies — making the feature shippable in
upstream LoopKit/Loop without DataLayer.
Pump pins fade over 10 days, sensor pins over 5 — clinical safe-reuse
windows for cannula vs filament tissue recovery. Past the threshold the
pin disappears from the body map (and placement-picker reference layer)
so users get an immediate visual signal that the site is safe to reuse.
Entry data is preserved in the Settings list for history.

- Theme.safeReuseDays(for:) returns 10 for pump, 5 for sensor
- ageColor / ageOpacity / shouldDisplayOnBodyMap take type parameter
- Placement-time recencyWeight uses the type-specific window
- Settings "Ready" badge uses type-specific threshold
- Map legend gradient sampled at 0/3/7/10 (pump window) — same ramp for both
When the user fine-tuned carbs via the AI confidence range slider, the
carbs circle still showed the AI's original estimate (e.g. slider at
56g but circle reading 62g). Carbs circle now reads from the bound
carbsQuantity, and calories adjusts proportionally (4 kcal/g) so the
displayed totals stay self-consistent. Fat / protein / fiber are
independent of the carb slider and stay at AI values.
Posts a com.loopkit.Loop.siteAtlasPlaced NotificationCenter event from
addEntry() with type / bodySide / zoneID (point-in-ellipse test against
the recommended zones) / replacementOfHidden flag. Decoupled — this
service has zero DataLayer deps; the matching observer lives in
DataLayer_Coordinator.

Enables real per-feature user counting on the dashboard's Feature
Adoption block alongside FoodFinder/LoopInsights/AutoPresets/BolusPro.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant