IDE Software Scope And Deferred Items
Status: Reviewer summary
Owner: BionicLoop engineering
Last updated: 2026-04-07 12:32 EDT
Purpose
State clearly what engineering is claiming in the current IDE software packet, what is deferred, and what belongs to the receiving quality/submission team.
In Scope For The Current Packet
| Topic |
Current Position |
| Local app/runtime/algorithm/device software docs |
In scope |
| Software verification structure and STP ownership mapping |
In scope |
| Software-facing IFU package and screenshots |
In scope |
| Study-relevant software risk summary |
In scope |
| Proportionate cybersecurity summary for local software posture |
In scope |
Deferred From The Current Packet
| Topic |
Current Position |
Why Deferred |
| Cloud / device-to-cloud verification closure |
Deferred |
Current handoff is focused on local controller software readiness, not cloud-system closure. |
| Part 11 readiness package |
Deferred |
Requires broader system and quality-process decisions beyond this software handoff slice. |
SRS-SEC-003..009 auth/provider/session-continuity closure |
Deferred |
These rows still involve broader provider-policy, auth-model, and cloud/compliance scope decisions. |
SRS-BG-008 / TV-BG-007 step-0 BG rescue |
Deferred |
Current accepted baseline keeps step 0 CGM-only. |
Accepted Current-Baseline Decisions
| Item |
Accepted Decision |
SRS-MEAL-004 |
Late meal submit executes on the current due step. |
SRS-CLIN-002 |
Current clinician gate remains the investigational passcode control with explicit transition required before production release. |
TV-MEAL-003 |
Remains in scope because it reflects accepted current meal behavior. |
Not Engineering-Owned In This Pass
| Topic |
Current Position |
| Formal review and approval signatures |
Receiving quality/submission team |
| Final IDE submission assembly and release authorization |
Receiving quality/submission team |
| Residual-risk acceptance signoff |
Receiving quality/submission team |
| Supplier/manufacturing/training/non-software QMS artifacts |
Outside engineering-owned packet |
Practical Review Rule
If a reviewer asks whether a topic must block this software packet, default answer should be:
yes only if it is part of the accepted local software baseline being claimed for study useno if it is deferred from the current packet or outside the engineering-owned software handoff scope
Primary Support References