TL;DR
CGM review is still a three-tab workflow in most clinics: one tab for Dexcom or Libre, one for the EHR, and one for RPM, telehealth, or billing follow-up. That is not a minor usability flaw. It is a clinical, cognitive, and reimbursement problem.
The clinical value of CGM is already established. A meta-analysis of 8 randomized trials with 541 adults with type 2 diabetes not using insulin found a pooled HbA1c difference of -0.37 percentage points favoring CGM over usual care or blood glucose monitoring. This is evidence about CGM in that population, not a Thyra outcome.
A true single-tab CGM workflow puts device trends, longitudinal chart context, inbox actions, documentation, and RPM/CCM/RTM support into one review surface.
This is also the practical difference between an AI scribe and an EHR overlay. A scribe helps document an encounter. An overlay can unify the work that happens before, during, and after the clinical decision.
Platforms that offer AI scribe plus inbox triage are still rare. Most tools do one or the other.
Thyra includes Smart Inbox, relevant chart context, and a CGM interpretation and documentation workflow for physician review. Integration availability depends on your EHR and the workflow you want to use. We confirm the data source, permissions, and any read or write connection before a pilot begins.
A surprising amount of endocrinology work in 2026 still depends on browser-tab memory. A clinician opens a Dexcom or Libre portal to inspect overnight trends, flips to the EHR to check the last A1c and medication changes, then opens a third system to document outreach, capture RPM time, or route a task to a nurse or CDCES. The software may be integrated at the connection layer, but the work is still fragmented at the decision layer.
That distinction matters because endocrinologists do not need one more feed. They need a workflow that reduces chart hunting, supports remote diabetes management, and makes it easier to coordinate with primary care without adding more administrative drag.
Why Does CGM Review Still Require Three Browser Tabs in 2026?
CGM review still requires three browser tabs because most health IT stacks separate device analytics, chart context, and reimbursement workflows into different systems.
Assess connectivity by checking the actual data available and the workflow it supports. An imported PDF, data tile, or app launch does not by itself establish a complete clinical review workflow.
What does the three-tab workflow usually look like?
For many endocrinologists, the pattern is predictable:
- CGM portal tab for Dexcom or Libre trend analysis, ambulatory glucose profile, and event-level detail
- EHR tab for medications, prior A1c values, insulin changes, problem list, and recent visit history
- RPM, telehealth, or task dashboard tab for outreach documentation, scheduling, time capture, and billing reconciliation
That design creates three operational burdens.
First, it increases cognitive load because the clinician has to mentally assemble the patient story across screens.
Second, switching tools can make it harder to review history. Measure the navigation and review time in your own practice rather than applying an assumed saving.
Third, it weakens reimbursement capture. Short review intervals can still be clinically meaningful, but they are often poorly documented when the review surface is disconnected from the billing workflow.
| Workflow step | Typical fragmented setup | Operational consequence |
|---|---|---|
| Review glucose trends | Dexcom or Libre portal | Full analytics live outside the chart |
| Check history and meds | EHR | Context retrieval is manual and slow |
| Assign follow-up | Inbox, task tool, or telehealth dashboard | Care coordination becomes a separate step |
| Document and code | EHR note plus RPM tool | Time capture and billing logic can be missed |
| Communicate with PCP | Fax, message, or note routing | Handoffs are delayed or incomplete |
Why Is the Three-Tab Problem More Important in 2026?
The three-tab problem matters more in 2026 because CGM evidence is stronger, reimbursement is more favorable, and distributed diabetes care is more viable than the workflows supporting it.
The industry has already done the hard part on data generation and clinical validation. What remains is the less glamorous problem of making that data usable inside real outpatient operations.
What changed in policy and payment?
Under the CY2026 Medicare Physician Fee Schedule final rule, the conversion factor increased +3.26% for clinicians who are not qualifying alternative payment model participants (non-QPs) and +3.77% for qualifying participants (QPs), compared with CY2025. These conversion-factor changes do not establish payment for a particular CGM service or promise a practice's reimbursement.
Confirm the applicable coding, coverage, supervision, and documentation requirements with the payer before billing. A software workflow does not establish service eligibility or payment.
The business implication is simple: better reimbursement now depends on better workflow precision.
Why does stronger clinical evidence raise the stakes?
The CGM meta-analysis cited above concerns glycemic outcomes in adults with noninsulin-treated type 2 diabetes. It does not measure Thyra workflow speed, billing performance, or clinical outcomes.
That makes one point especially citation-worthy: the barrier to better CGM-enabled care in 2026 is increasingly not whether the data exists, but whether the clinician can review it in context fast enough to act on it consistently.
What Does a Single-Tab CGM Workflow Actually Look Like?
A single-tab CGM workflow means one clinical review surface where normalized device data, longitudinal history, follow-up actions, and billing support appear in the same flow.
This is where market language often gets sloppy. Many vendors offer connected systems. Very few offer a workflow where the clinician can review, decide, route, document, and support reimbursement without leaving the same working surface.
What should be visible in one review surface?
A useful integrated workflow should let an endocrinologist do five things without leaving the review:
- See Dexcom and Libre trends with clear normalization across CGM brands
- Pull in the longitudinal patient record, including prior A1c, medication changes, insulin titration history, and recent messages
- Trigger inbox triage for outreach, refill adjustments, or PCP communication
- Generate documentation that reflects the clinical decision, not just a note stub
- Support RPM, CCM, and RTM workflow with traceable time and action capture
How does Thyra deliver this in practice?
Thyra brings relevant context beside an inbox item for physician review. See the longitudinal patient record discussion. Integration availability depends on your EHR and the workflow you want to use. We confirm the data source, permissions, and any read or write connection before a pilot begins. Confirm exit and data-handling arrangements before starting.
This is the architectural answer to a problem that connectivity alone cannot solve. The further reading on the longitudinal patient record explains why CGM trends, prior A1c values, and medication changes need to arrive at the message level rather than after a chart hunt.
Frequently Asked Questions
How is a single-tab CGM workflow different from standard CGM integration?
Standard CGM integration usually means data can be imported, viewed, or launched from the EHR. A single-tab workflow goes further by combining device review, chart context, inbox actions, documentation, and billing support in one working surface.
Why does CGM review need a longitudinal patient record?
CGM trends are only clinically meaningful when read against the patient's history. A glucose dip at 3 AM means one thing for a patient with a recent basal insulin titration and another for a patient with new-onset kidney disease. Without the longitudinal record attached to the review surface, the clinician spends review time reconstructing context that should already be present.
How can clinics pilot a single-tab CGM workflow without replacing their EHR?
A SMART on FHIR overlay deploys on top of the existing EHR through standard interfaces. The overlay adds the workflow surface; the underlying system continues as the source of truth. Pilots can begin on a single provider or one clinic, run for four to six weeks, and be removed without disruption if the evaluation does not meet expectations.
Sources
- Aleppo G et al. The Effect of Discontinuing Continuous Glucose Monitoring in Adults With Type 2 Diabetes Treated With Basal Insulin. Diabetes Care, 2024.
- Centers for Medicare & Medicaid Services. CY2026 Medicare Physician Fee Schedule Final Rule (CMS-1832-F).
- American Medical Association. CPT 2026: New codes for remote physiologic and remote therapeutic monitoring.
- Thyra blog: The Longitudinal Patient Record: What Endocrinology Needs That No EHR Provides.
