Map the data path and the control path separately
A CGM integrated smart pen proposal should show two different paths. The data path explains how glucose readings and injection records reach an application. The control path explains whether any output changes treatment or operates a delivery mechanism. Putting two datasets on one screen does not establish automatic control. A continuous glucose monitor and a manually operated pen can remain separate devices even when an app displays both. Ask which integrations are currently supported, what timing or completeness limitations apply and what actions the user must still perform. Record whether the system offers visualization, reminders, recommendations or automated actuation. These distinctions make terms such as smart pen glucose trend analysis and real time dose adjustment pen precise enough for engineering review, procurement and clear commercial communication.
Parameters & review checklist
- Data visualization versus control
- Supported CGM and app combinations
- Missing-data behavior
- Monitoring responsibilities
Apply this guide to your project
Use these configuration briefs to record the requirements discussed above, then prepare the document and quotation requests for your project.
Platform comparison and downloadable buyer worksheets ↗
Sample references and supplier evidence checklist ↗
Common questions
Is a smart pen plus CGM a closed-loop system?
Not by default. Data sharing is different from an authorized algorithm controlling automated drug delivery.
Sources & further reading
- Medtronic: InPen system and important safety information Reference page checked 15 September 2026.
- FDA: medical device cybersecurity Reference page checked 15 September 2026.
External references describe their publishers’ products or guidance. Procurement tables are editorial decision aids; they do not establish conformity of a Hytanbio-Tech configuration.