Glass Health supports Epic teams that want ambient documentation and clinical decision support in the same clinician-reviewed workflow. The goal is not to replace Epic as the chart. The goal is to help clinicians move from patient conversation to note, differential, cited clinical questions, and assessment-and-plan thinking while staying grounded in the chart context they are already authorized to use.
Epic organizations usually evaluate AI through a high bar: clinical safety, clinician adoption, informatics fit, security review, and operational clarity. Glass is built for that kind of evaluation. It pairs ambient scribing with real-time clinical support, then leaves final documentation and clinical judgment with the clinician.
Why Epic teams evaluate Glass Health
Epic already has its own AI surface area, so an Epic buyer should not ask a generic question like "Can AI write notes?" The better question is more specific: what work should happen during and after the encounter, and which system should own each part?
Epic’s public Art for Clinicians page describes built-in capabilities for AI Charting, message drafting, patient summaries, ambient order capture, text editing, and other clinician workflows. That gives Epic teams a real baseline. Glass becomes the relevant alternative when the team wants the documentation workflow to sit next to a broader clinical reasoning layer.
For a physician, that means one working session can include:
- ambient capture of the encounter
- a draft note for review
- differential diagnosis support
- suggested history questions and exam maneuvers
- evidence-backed clinical recommendations
- cited clinical Q&A
- an assessment and plan draft that the clinician can edit before final use
That combination matters because much of the cognitive work of a visit happens before the note is final. If AI only helps after the clinician has already reasoned through the case, the tool is mainly a documentation accelerator. If it can also help organize the differential, prompt next questions, and surface evidence while the case is active, the evaluation is more clinically meaningful.
How Glass fits with Epic
Glass should be evaluated as a clinician-facing layer that supports documentation and clinical reasoning while Epic remains the system of record. The Glass EHR integration overview describes the broader connected-workflow model. In an Epic-connected workflow, authorized chart context can inform the Glass session. Glass can then help generate outputs for clinician review, including documentation and CDS artifacts.
That operating model keeps the public product boundary clean:
| Workflow area | Glass role | Epic role | Evaluation question |
|---|---|---|---|
| Encounter capture | Help turn the conversation into usable clinical documentation | Remains the chart workflow that the organization governs | Does the draft note reduce cleanup without losing clinical nuance? |
| Chart context | Use authorized context to make the session more relevant | Remains the system of record | Does chart context make the note, questions, and plan more useful? |
| Clinical reasoning | Support differential thinking, cited Q&A, and assessment-and-plan drafting | Receives final clinician-reviewed documentation through the approved workflow | Do clinicians actually use the reasoning layer during review? |
| Governance | Support a narrow pilot with clinician review and compliance review | Existing Epic, security, and operational governance remains in place | Can the team define a safe pilot before broader rollout? |
The important point is that Glass is not trying to publish an implementation specification. Clinical and operational leaders should be able to understand what the product is for, what to evaluate, and what questions to ask before rollout. Specific implementation details belong in direct review with Glass, the Epic team, security, and compliance.
What the Epic pilot should measure
A serious Epic pilot should be narrower than the buyer’s long-term ambition. Start with one service line, one or two visit types, a defined clinician cohort, and a written scorecard. That makes the review faster and reduces the chance that the pilot becomes an abstract debate about AI.
Useful pilot questions include:
- Does the note draft preserve the clinically important details of the encounter?
- Does the clinician spend less time rewriting the note?
- Does the clinician trust the chart-aware clinical support enough to use it?
- Do suggested questions, exam maneuvers, or next steps improve the live encounter?
- Do cited clinical answers reduce context switching to separate reference tools?
- Does the assessment and plan draft help the clinician move faster without weakening review?
- Does the workflow fit the organization’s Epic review and documentation expectations?
The scorecard should combine qualitative and quantitative signals. Time saved matters, but it is not the whole story. Epic teams should also review note quality, clinician burden, adoption, cleanup effort, chart-close workflow, and whether the clinical reasoning layer improves the encounter.
Related Epic buying guides
Epic teams comparing AI documentation tools should also read the best AI medical scribe guide and the Epic-specific best AI scribes for Epic guide. Those guides help a buyer compare the market before choosing which products deserve a deeper workflow review.
Once Epic is the environment in scope, the practical question is not just whether a product can draft documentation. The real question is whether it can support the clinician’s reasoning, review, and final documentation workflow in a way that is safe enough to pilot.
How to compare Glass with Epic AI Charting
Epic publicly describes AI Charting as a way to draft documentation, show relevant information, and queue up orders from patient conversations. That is an important built-in baseline for Epic teams.
Glass should be evaluated against a different question: do you want an ambient documentation product only, or do you want ambient documentation plus real-time clinical support in the same working session?
| Buyer question | Epic AI Charting baseline | Glass Health evaluation path |
|---|---|---|
| Can the system draft documentation from the conversation? | Epic says AI Charting can draft documentation from patient conversations | Test Glass note quality, cleanup effort, and template fit |
| Can the workflow surface relevant information? | Epic describes showing relevant information | Test whether Glass chart-aware context improves clinical usefulness |
| Can the workflow support orders? | Epic describes queueing up orders for clinician review | Confirm the current Glass workflow and final charting process directly with Glass |
| Can the clinician get clinical reasoning support during the encounter? | Evaluate Epic’s current built-in capabilities with your Epic team | Test Glass differential support, cited Q&A, suggested questions, and assessment-and-plan drafting |
| Can the team run a narrow pilot with compliance review? | Use the organization’s Epic governance process | Define the Glass pilot cohort, BAA path, clinician review flow, and success metrics |
This comparison should be practical, not theatrical. Epic AI Charting may be the right baseline for teams that want to stay fully inside Epic’s built-in AI roadmap. Glass is worth evaluating when the desired workflow includes documentation plus chart-aware clinical decision support.
Start with one controlled Epic cohort
Before production use, name the Epic environment, clinician cohort, visit types, note templates, CDS outputs, final documentation path, support owner, and success measures. Confirm the current integration workflow, BAA terms, user access, and implementation scope with Glass and the organization’s Epic team.
Use both routine visits and cases where chart context, differential support, or cited Q&A could reduce context switching. Score note quality, editing effort, chart-close impact, CDS usefulness, adoption, and workflow failures separately. That makes it possible to distinguish a documentation win from a broader encounter-workflow win.
Epic AI Charting is the native baseline. Glass is most relevant when the organization wants ambient documentation and clinical support in one clinician-reviewed session. If the requirement is limited to Epic-native documentation, evaluate that path first. If the requirement includes differential support, cited clinical questions, and assessment-and-plan drafting, test Glass directly against that larger job.
FAQ
Does Glass Health work with Epic?
Yes. Glass supports Epic-connected workflows for ambient scribing and chart-aware clinical decision support. Teams should confirm the current supported workflow directly with Glass during evaluation.
Does Glass replace Epic AI Charting?
No. Epic remains the system of record, and Epic AI Charting is an Epic-native baseline. Glass should be evaluated when the team wants ambient documentation plus chart-aware CDS, differential support, cited Q&A, and assessment-and-plan drafting in one clinician-reviewed workflow.
What should an Epic pilot measure?
Measure note quality, cleanup effort, chart-close workflow, clinician adoption, usefulness of the CDS layer, and whether the workflow fits the organization’s Epic governance process.
Who owns final documentation?
The clinician owns final review and final chart actions through the approved workflow. Glass can help draft and organize output, but it should not be treated as a substitute for clinician judgment.
Can a BAA apply to the Glass workflow?
BAA availability and scope depend on the specific account and a separate agreement. Confirm the applicable contract, services, and production PHI scope directly with Glass before deployment.
What is the safest first step for an Epic organization?
Start with a narrow pilot. Pick the clinician cohort, visit type, note output, CDS output, BAA path, review model, and success metrics before rollout.
How should we compare Glass with Epic’s public AI tools?
Use Epic’s current Art for Clinicians page as the built-in baseline, then test whether Glass adds enough value through ambient CDS, differential support, cited Q&A, and assessment-and-plan drafting to justify a separate pilot.
Does Glass publish pricing?
Glass publishes plan information on the pricing page. Epic-connected deployments should still confirm current packaging, workflow scope, and contracting terms directly with Glass.