Practitioner Guidance
6 min read
How can a functional medicine clinic use one patient-data workflow?
How a functional medicine clinic can connect labs, CGM, food, lifestyle data, and patient communication without replacing its EHR.
- Written by
- Mike Haney, Editorial Director
- Medically reviewed by
- Sara Szal Gottfried, MD
- Last updated
- September 2, 2026

The short answer
The practices that solve this keep the EHR as the legal chart and add one patient-data layer for everything that happens between visits.
Patients enter or sync daily context in one app. Labs, CGM, food, activity, sleep. The care team reads one consolidated timeline before visits, checks the patterns that matter, and writes clinical decisions back into the EHR.
At a glance
Which system owns which record.
| System | What belongs there | |
|---|---|---|
| 01 | EHR | Diagnoses, orders, medications, consent, encounter notes, and the legal record |
| 02 | Patient app | Daily food, activity, sleep, symptoms, and device connections |
| 03 | Practitioner data layer | Longitudinal labs, CGM context, trends, and review summaries |
| 04 | Team workflow | Ownership, review cadence, escalation, and follow-up |
In this guide
Seven questions this guide answers.
- 01Why do disconnected tools create clinical friction?
- 02What should the patient do in the shared workflow?
- 03What should the practitioner see before a visit?
- 04How should the team turn a pattern into a care decision?
- 05How should roles be divided?
- 06When does a unified workflow not apply?
- 07How can a clinic evaluate the workflow?
Why do disconnected tools create clinical friction?
A lab portal, CGM viewer, food diary, wearable app, and messaging channel can each work well while the combined workflow fails. The team has to reconcile identities and dates, decide which record is current, and rebuild the story during the encounter.
The problem is not the number of vendors. It is the missing route from patient action to practitioner review to charted decision.
What does the patient do in the shared workflow?
The patient needs one daily home for the information that explains what happened between visits. Depending on the care plan, that tends to include:
- meal photos or descriptions;
- movement and exercise;
- sleep and wearable data;
- symptoms and relevant notes; and
- CGM data when clinically appropriate.
The app gives the patient feedback they can understand while keeping education and medical advice distinct. It also shows missing or disconnected data instead of quietly filling the gap.
What does the practitioner see before a visit?
The views practitioners keep focus on decisions, not data volume. A pre-visit review that earns its place shows lab trends over time, CGM patterns in context, how closely the patient followed the plan, what changed, and the underlying records to check against.
Levels Pro is built for this role. It is a metabolic data layer that pulls labs, glucose, food, and lifestyle context together while the practice's EHR stays the chart. The Levels Pro product overview lists current capabilities.
How does a pattern become a care decision?
The handoff we see working is consistent:
- software surfaces a pattern or change;
- a designated team member verifies the source data;
- the appropriate licensed professional interprets clinical significance;
- the team discusses the finding with the patient when needed; and
- the clinician records the decision and follow-up in the EHR.
That sequence keeps automated summaries from turning into unreviewed treatment recommendations.
How do practices divide roles?
Operations staff manage enrollment, connectivity, and routine support. Coaches help patients use logging tools and reinforce education within their scope. Licensed clinicians interpret findings and make treatment decisions. Each practice defines who monitors messages and what requires escalation.
The practice states response expectations up front. A patient-data platform is not a continuously monitored clinical service.
Limits of this guidance
When does a unified workflow not apply?
This model does not apply when a practice needs inpatient monitoring, emergency response, or a specialty system with functions the data layer does not provide. It also does not justify collecting data that has no defined clinical purpose, owner, retention policy, or place in the care plan.
Do not replace required EHR documentation, professional judgment, device instructions, or privacy and consent procedures with an app workflow.
How do clinics evaluate the workflow?
Four questions to audit against. Can staff trace each summary to its source? Do decisions reach the EHR? Do patients know where to write? Are unresolved data gaps visible? The workflow is working when it cuts reconstruction and keeps accountability, not when it collects more data.
Keep reading
The rest of the practitioner series.
Workflow
How do I add CGM to my functional medicine practice?
Patient selection, onboarding ownership, contextual logging, and pre-visit review.
Care model
What is metabolically informed care?
Combining labs, glucose, and daily behavior without overinterpreting the data.
Dashboard
What should a CGM dashboard for clinicians show?
Roster triage, standardized metrics, contextual timelines, and data-quality signals.
Levels Pro
Connect the metabolic data layer
Levels Pro brings labs, CGM, food logs, and lifestyle context into one practitioner view alongside your EHR.