Practitioner Guidance
6 min read
How do I add CGM to my functional medicine practice?
A practical workflow for adding continuous glucose monitoring to a functional medicine practice without creating a second chart or an unmanageable stream of data.
- Written by
- Mike Haney, Editorial Director
- Medically reviewed by
- Sara Szal Gottfried, MD
- Last updated
- September 2, 2026
The short answer
Practices that make CGM stick run it as a defined care program, not as a stand-alone device sale.
The Pro practices we work with land in the same place. Operations staff own ordering and onboarding, patients log context in one spot, someone summarizes patterns before the visit, and decisions go into the existing health record. It holds up because the platform carries the workflow and the chart stays the chart.
At a glance
What each stage of the workflow looks like in practice.
| Workflow stage | What practices put in place | |
|---|---|---|
| 01 | Patient selection | A documented clinical purpose, and a device confirmed appropriate for the patient |
| 02 | Onboarding | One owner for ordering, setup, and support |
| 03 | Observation | Glucose paired with meals, activity, sleep, and symptoms |
| 04 | Review | Patterns summarized before the encounter, decisions recorded in the EHR |
In this guide
Six questions this guide answers.
- 01Where should CGM fit in the care model?
- 02Who should own each part of the workflow?
- 03How should patients capture context?
- 04How should the team review CGM data?
- 05When does this workflow not apply?
- 06What should the practice measure after launch?
Why does CGM need a defined home in the care model?
The practices that get value from CGM start with a named program and a stated clinical question. Metabolic risk reduction, nutrition coaching, weight-management care, wherever glucose feedback informs the plan. The ones that struggle enroll patients because a sensor was available.
Programs that run well settle six things up front:
- the eligibility and exclusion criteria;
- who orders and onboards the patient;
- what the patient logs alongside glucose;
- when a coach or clinician reviews the data;
- what triggers outreach; and
- where the interpretation and care decision are documented.
The NIDDK overview of continuous glucose monitoring covers CGM types, features, and limits. Each practice sets its protocol against the device's instructions and its own scope of practice.
How do practices divide ownership?
| Role | Primary responsibility | Escalates when |
|---|---|---|
| Operations staff | Primary responsibilityEnrollment, ordering, setup instructions, and routine support | Escalates whenA device issue may affect safety or interpretation |
| Coach or nutrition professional | Primary responsibilityLogging support, pattern review, and behavior education within scope | Escalates whenA pattern may require diagnosis or treatment |
| Licensed clinician | Primary responsibilityClinical interpretation, treatment decisions, and chart documentation | Escalates whenSpecialist or urgent evaluation is indicated |
| Patient | Primary responsibilitySensor use, contextual logging, and symptom reporting | Escalates whenReadings conflict with symptoms or instructions |
Practitioners tell us clear ownership is what protects clinician time. It also keeps a dashboard alert or a patient message from reading as continuous clinical monitoring.
How do patients capture context?
Glucose without context is hard to read. Practices that keep review quick give patients one daily workspace for meal photos or descriptions, movement, sleep, and symptoms. A single timeline lets the team see likely relationships without hand-aligning exports from separate tools.
Levels Pro shows CGM, food, and lifestyle data together while the practice keeps diagnoses, orders, and the treatment plan in its EHR. That split avoids a second clinical chart.
What does CGM review look like in practice?
Teams that keep review time manageable work from a repeatable template rather than reading every trace. The shape we see most often:
- data quality and wear context confirmed first;
- recurring patterns weighted over isolated excursions;
- patterns read alongside meals, activity, sleep, and symptoms;
- changes since a prior intervention noted; and
- the interpretation and next action recorded in the EHR.
Pre-visit summaries can help prioritize review, but a qualified practitioner must verify them before using them in care.
Limits of this guidance
When does this workflow not apply?
This workflow does not apply when the selected CGM is contraindicated or outside its labeling, when a patient needs real-time medical monitoring that the practice cannot provide, or when the team lacks a defined escalation pathway. It also does not replace confirmatory testing, diagnosis, medication management, or emergency care.
Patients should follow the device manufacturer's instructions and their clinician's guidance when a sensor reading does not match symptoms or expectations.
What do practices measure after launch?
Practices that expand well check usability first: onboarding failures, unresolved support requests, logging completeness, staff review burden, documented care decisions, and patient-reported usefulness. Expansion works once the team can say who acts on the data, when, and where they record it.
Keep reading
The rest of the practitioner series.
Dashboard
What should a CGM dashboard for clinicians show?
Roster triage, standardized metrics, contextual timelines, and data-quality signals.
Data workflow
How can a clinic use one patient-data workflow?
Connecting labs, CGM, food, and lifestyle data without replacing the EHR.
Between visits
How can a practice use real-time metabolic data?
Protocol-driven coaching, review queues, escalation, and response expectations.
Levels Pro
See the Levels Pro workflow
Levels Pro brings CGM, labs, food logs, and lifestyle data into one practitioner view while your EHR remains the chart.