Background:  Ethan, a 40-year-old teacher with type 1 diabetes, arrives at his endocrinologist’s office excited to share his plans about starting AndroidAPS. He has already ordered the necessary pump and downloaded the app.

HCP’s Role: His DCES listens carefully, acknowledges his enthusiasm, and explains the distinction between support and advocation. The DCES documents the discussion, clarifies that the system is not FDA-approved, and reviews Ethan’s basal and carb ratio settings for accuracy. Together, they discuss a backup plan for system downtime and ensure Ethan has injectable insulin and CGM supplies available. They also work on a plan for downloading app data to an online account so that reports can be shared.

Outcome: By setting clear boundaries and reinforcing safe practices, the DCES empowers Ethan to proceed responsibly while reducing clinical liability and maintaining trust.

Background: Sophia, a 16-year-old with type 1 diabetes, has been using the Loop app for four months under her parents’ supervision. She reports improved glucose control but feels frustrated by system updates and occasional pump and CGM connectivity failures.

HCP’s Role:  Her DCES:

1. Validates her frustration and normalizes the learning curve.
2. Walks her through reviewing Nightscout data, highlighting where algorithm adjustments may be needed.
3. Helps her create a troubleshooting checklist for common issues, such as pump disconnects or app crashes.
4. Points her toward reliable peer forums and LoopDocs for technical support beyond the clinic.

Outcome: With renewed confidence and structured troubleshooting strategies, Sophia continues using her system successfully. The HCP’s role as an educator and coach reinforces her independence while ensuring safe practices.