Practitioner Guidance
6 min read
How can a practice use real-time metabolic data between visits?
How practices can use current metabolic data for timely coaching while setting safe expectations for review, escalation, and clinical decisions.
- Written by
- Mike Haney, Editorial Director
- Medically reviewed by
- Sara Szal Gottfried, MD
- Last updated
- September 2, 2026

The short answer
Where this works, current metabolic data runs through a scheduled, protocol-driven coaching workflow. It is not an unmonitored promise of instant clinical response.
Patients see educational feedback, designated staff work a queue of patterns to check, the practice defines coaching scope, and clinical questions escalate to licensed practitioners. Treatment decisions go in the EHR, and the practice states response expectations plainly.
At a glance
What each signal permits.
| Signal | Appropriate between-visit action | |
|---|---|---|
| 01 | Repeated meal or activity pattern | Ask a question and reinforce agreed education |
| 02 | Missing or disconnected data | Resolve setup or logging barriers |
| 03 | Pattern outside the care protocol | Route to the designated licensed practitioner |
| 04 | Symptoms or urgent concern | Follow the practice's clinical escalation instructions |
In this guide
Seven questions this guide answers.
- 01What makes metabolic data timely rather than recent?
- 02Which information belongs in the shared timeline?
- 03Who should review between visits?
- 04How can the team intervene without overreaching?
- 05Where should the resulting decision live?
- 06When does between-visit metabolic care not apply?
- 07How can the practice evaluate the workflow?
What makes metabolic data timely rather than just recent?
Recent data become useful only when the workflow connects them to an action. A patient may see feedback right after logging a meal or syncing a device. A coach may work an assigned queue at set intervals. A clinician may weigh an escalated pattern against history, symptoms, medications, and other evidence.
Calling this "real-time care" does not mean a practitioner watches every reading. The practices that avoid that confusion spell out their review cadence and communication channel.
Which information belongs in the shared timeline?
Only information relevant to the care plan, typically:
- CGM data when appropriate and used according to device instructions;
- meal photos or descriptions;
- activity and sleep from connected sources;
- patient-reported symptoms or notes; and
- the timing of coaching messages and agreed interventions.
The NIDDK overview of continuous glucose monitoring covers CGM types, uses, and limits. Current data are not automatically complete or clinically significant.
Who reviews between visits?
The practice assigns work by role and scope. Operations staff handle setup and connectivity. Coaches ask clarifying questions, support logging, and reinforce education already in the plan. Licensed clinicians interpret findings that may change diagnosis or treatment.
Every queue needs an owner, a review expectation, and an escalation route. Without those, more notifications create ambiguity rather than faster care.
How do teams intervene without overreaching?
The starting point is the plan the patient and clinician already agreed to. A coach points out a recurring observation, asks whether the patient recognizes it, and helps run an approved behavior experiment. Anything that may affect medication, diagnosis, or safety routes to the licensed clinician.
Automated summaries should link to the underlying data and say where they are uncertain. They can prioritize attention. They cannot make a clinical decision.
Where does the resulting decision live?
The metabolic platform carries current context and coordinates the workflow. The EHR carries diagnoses, orders, medications, and the authoritative care plan. When a between-visit review leads to a clinical decision, the clinician documents it according to practice policy.
Levels Pro brings CGM, food, labs, and lifestyle context into a practitioner workspace that runs alongside the EHR.
Limits of this guidance
When does between-visit metabolic care not apply?
This model does not apply to emergency response, inpatient monitoring, or any condition that requires continuous clinical surveillance. It also does not apply when the practice cannot define who reviews data, how quickly, and what triggers escalation.
Patients should not use a dashboard message queue for urgent symptoms. The practice must provide clear instructions for urgent and emergency care and follow device-specific guidance when readings do not match symptoms.
How do practices evaluate the workflow?
Four questions tell you whether it works. Are queues handled as promised? Do escalations reach the right professional? Can staff trace a summary back to its source data? Do clinical decisions reach the EHR? Timeliness is a property of the operating process, not the age of the data.
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.
Care model
What is metabolically informed care?
Combining labs, glucose, and daily behavior without overinterpreting the data.
Workflow
How do I add CGM to my functional medicine practice?
Patient selection, onboarding ownership, contextual logging, and pre-visit review.
Levels Pro
Build a traceable between-visit workflow
Levels Pro connects current glucose, food, labs, and lifestyle context while your practice controls review and escalation.