MiniMed 670G: a closed-loop claim needs one system evidence map
The 2016 hybrid system ties sensor, algorithm, pump, user tasks, and clinical evidence together.
ClarusBIOTECH REVIEWRead, listen & keep
Narration has not been recorded for this article’s current text. The written article is available to download.
Revised September 30, 2026 · Historical case analysis

Dates, outcomes, and decision boundaries
| Measure | Reported result | Context & source |
|---|---|---|
| Original FDA approval | September 28, 2016 | PMA P160017 [1] |
| Pivotal enrollment | 124 subjects | Study exposure has a defined boundary [1] |
| Study design | 2-week run-in + 3 months | Historical pivotal program [1] |
| Automation boundary | Basal adjustment; meal tasks remain | Hybrid system, not task-free therapy [1] |
The FDA summary does not provide a universal acquisition price, training cost, or routine-care adoption rate. Those need a separate service and access dataset.
The original MiniMed 670G authorization is a concrete drug-delivery device case. FDA's September 28, 2016 approval concerned a hybrid closed-loop insulin-delivery system for the specified type 1 diabetes population. The system joined a glucose sensor, transmitter, control algorithm, pump, infusion set, and user workflow. [1]
Read the word hybrid literally
The historical FDA summary explains that the system could adjust basal insulin while users still entered meal information and administered meal boluses. An automated component did not eliminate all human tasks. That boundary belongs in both the product claim and the usability plan. [1]
The pivotal configuration and exposure matter
The pivotal program used a two-week run-in followed by a three-month study phase, with 124 enrolled subjects. A finite, selected study is useful evidence, but it does not prove zero risk during lifelong use or in every population. The device components and software configuration assessed should remain visible when a later design change is considered. [1]
Link technical and clinical milestones
Sensor performance, algorithm behavior, infusion reliability, training, alarms, and clinical outcomes form one chain. A strong result for one component cannot replace integration evidence for the complete system. The development roadmap should identify which failures degrade measurement, which alter delivery, and which require user action.
Adoption needs a service model
For a launch plan, assess setup, training, ongoing support, consumables, and continuity of supply. Measure sustained use and reasons for interruption instead of equating device shipment with functioning therapy. The milestone is a system that supports the intended care workflow under the authorized use conditions, with a clear evidence plan for any subsequent version.
Source adaptation: the BioClarus drug–device milestone paper informed the dependency map. This article applies it to a documented insulin-delivery system rather than repeating the women's-health example.
What to measure for the next decision
| Dimension | KPI to collect | Decision use |
|---|---|---|
| System integrity | Sensor-to-delivery failure pathways | Assign owners for every component interface. |
| Human factors | Critical-task errors and support burden | Test the authorized user workflow. |
| Adoption | Sustained use and interruption reasons | Separate shipment, activation, and continuation. |
THE NEXT VALUE INFLECTION
What would change the decision
For a launch plan, assess setup, training, ongoing support, consumables, and continuity of supply. Measure sustained use and reasons for interruption instead of equating device shipment with functioning therapy. The milestone is a system that supports the intended care workflow under the authorized use conditions, with a clear evidence plan for any subsequent version.
Editorial record
Prepared by Clarus Biotech Review editorial team. Updated 10/1/2026.
Publication relationship: ClarusReview is connected to BioClarus Consulting. No article-specific sponsorship is recorded.
Report a correctionDiscuss this paper
Share evidence, ask a question, or offer a professional perspective. Community guidelines
Loading discussion…