Glass Health supports eClinicalWorks teams that want ambient documentation and clinical decision support in the same clinician-reviewed workflow. For eClinicalWorks practices, the core question is not whether an AI scribe can create a SOAP note. The more important question is whether the workflow helps clinicians document the visit, reason through the case, answer clinical questions with citations, and draft an assessment and plan without turning the day into another cleanup queue.
Glass is designed for that broader job. It combines ambient scribing with chart-aware clinical support, differential thinking, evidence-backed recommendations, cited Q&A, and documentation drafting. eClinicalWorks remains the EHR workflow the organization governs. Glass supports the clinician’s work around the encounter, and clinicians review output before final use.
Why eClinicalWorks teams evaluate Glass
Many eClinicalWorks practices already understand the value of ambient documentation. eClinicalWorks publicly describes Sunoh.ai as a medical AI scribe that converts natural patient-provider conversations into clinical documentation, prepares draft visit content, and lets providers edit and import information into the Progress Note. That gives eClinicalWorks buyers a concrete documentation baseline.
Glass should be evaluated when the buying question is bigger than documentation alone.
For clinicians, the useful distinction is:
- A documentation-only workflow helps create a note.
- A documentation-plus-CDS workflow helps create the note and supports clinical thinking during review.
Glass is strongest when the practice wants the second workflow. During a real visit, clinicians often need more than a transcript summary. They need help remembering what to ask next, thinking through the differential, checking evidence, and turning a clinical impression into a plan that is ready for review. Glass is built around that combined documentation and reasoning loop.
How Glass fits with eClinicalWorks
Glass should be evaluated as a clinician-facing workspace that supports documentation and clinical reasoning while eClinicalWorks remains the system of record. In an eClinicalWorks-connected workflow, authorized chart context can make the Glass session more relevant. Glass can then help generate note drafts, clinical support, cited answers, and assessment-and-plan content for clinician review.
That gives the team a simple product boundary:
| Workflow area | Glass Health role | eClinicalWorks role | What to test |
|---|---|---|---|
| Encounter capture | Ambient scribing from the patient conversation | Existing EHR workflow remains governed by the organization | Does the note draft reduce cleanup time? |
| Chart context | Helps make documentation and CDS more relevant when authorized context is available | Remains the system of record | Does chart context improve output quality? |
| Clinical support | Differential support, cited Q&A, suggested next steps, and plan drafting | Final clinical documentation remains clinician-reviewed | Do clinicians actually use the reasoning layer? |
| Rollout governance | Narrow pilot, BAA review, clinician review model | Existing operational and compliance process | Can the practice define a safe first cohort? |
This keeps the product boundary useful without exposing implementation mechanics that belong in direct security and integration review.
What to test in an eClinicalWorks pilot
The best eClinicalWorks pilot starts narrow. Pick one clinician cohort, one visit mix, and the exact outputs that matter. The goal is not to prove that AI can produce text. The goal is to decide whether Glass improves the clinician’s real workflow.
For eClinicalWorks teams, useful pilot measures include:
- Progress Note readiness. Does the note draft contain the information clinicians need with less cleanup?
- Template fit. Does the generated documentation match the practice’s preferred structure?
- Chart-close impact. Does the workflow reduce after-hours documentation or only move the work?
- Clinical reasoning usefulness. Are differential support, cited questions, and plan drafting used during review?
- Operational friction. Can clinicians and staff adopt the workflow without a large support burden?
- Compliance readiness. Are the BAA path, user access, and rollout scope confirmed before production use?
The strongest signal is not a single impressive demo note. It is repeated evidence that clinicians use the workflow, trust the output enough to review it efficiently, and end the day with less cleanup.
Stakeholder checklist for an eClinicalWorks evaluation
eClinicalWorks practices often need a practical evaluation, not a sprawling enterprise committee. That does not mean the diligence should be loose. It means the questions should be clear and assigned to the right people.
| Stakeholder | What they should review | What a good answer looks like |
|---|---|---|
| Clinicians | Note quality, CDS usefulness, cleanup effort, and trust | Clinicians can explain when Glass helps and when they still need to edit heavily |
| Practice leadership | Pilot size, visit types, staffing impact, and support owner | The first cohort is narrow enough to manage and broad enough to learn from |
| EHR administrator | eClinicalWorks workflow fit and final documentation process | Everyone understands how reviewed output moves into the established workflow |
| Compliance lead | BAA path, PHI terms, user access, and escalation plan | Production use is not started until the covered workflow is clear |
| Finance owner | Pricing, pilot cost, and expansion trigger | Expansion is tied to measured workflow value, not a vague AI mandate |
That checklist is deliberately plain. The purpose of the pilot is not to admire a demo. It is to decide whether Glass improves the eClinicalWorks workflow enough to justify rollout.
Clinical scenarios worth testing
The first eClinicalWorks pilot should include both routine and complex cases. A routine follow-up shows whether Glass reduces the daily documentation burden. A diagnostic uncertainty visit shows whether clinicians actually value the clinical support layer. A template-sensitive visit shows whether the generated note fits the practice’s documentation habits.
Good scenarios include:
- a routine follow-up where speed and cleanup time are the main measures
- a new patient visit where history organization matters
- a visit with a broad differential where CDS can be evaluated
- a medication or guideline question where cited Q&A may reduce context switching
- a visit that needs a clear assessment and plan
- a visit with a specialty-specific documentation pattern
For each case, collect specific feedback. Did the note capture the important details? Did the clinician trust the assessment-and-plan draft enough to edit it rather than start over? Did the CDS layer provide useful prompts or answers? Did the workflow create any new friction for staff? This is the level of feedback that tells a practice whether the tool belongs in daily use.
Related eClinicalWorks buying guides
If your team is still comparing eClinicalWorks documentation options, start with the best AI scribes for eClinicalWorks guide. It gives buyers a broader view of the ambient scribe market for eClinicalWorks practices and helps separate documentation-only needs from documentation-plus-CDS needs.
For general product context, the best AI medical scribe guide explains the ambient scribe market, and the EHR integration page explains how Glass approaches EHR-connected workflows. Those guides can frame the buying decision before an eClinicalWorks-specific Glass pilot.
How to evaluate Glass alongside Sunoh
Sunoh is an important eClinicalWorks-native baseline because eClinicalWorks publishes a specific page for it. That page describes ambient listening, draft Progress Note content, eClinicalTouch, eClinicalMobile, customization, and the ability for providers to edit and import information into the Progress Note.
Glass should not be positioned by making unsupported negative claims about Sunoh. The cleaner comparison is workflow-based:
| Evaluation question | Sunoh baseline from eClinicalWorks public materials | Glass Health evaluation path |
|---|---|---|
| Is the primary goal faster documentation? | Sunoh is publicly positioned around ambient listening and clinical documentation for eClinicalWorks users | Test Glass note quality and cleanup time |
| Is mobile workflow important? | eClinicalWorks describes Sunoh for iPad and smartphones | Confirm the current Glass workflow for the practice’s device mix |
| Is clinical support beyond the note important? | Confirm current Sunoh capability directly with eClinicalWorks | Test Glass differential support, cited Q&A, suggested next steps, and assessment-and-plan drafting |
| Is chart-aware context important? | Confirm current Sunoh context and import workflow with eClinicalWorks | Confirm the Glass workflow, authorized context, and clinician review path directly with Glass |
| Is pricing clear enough for the first budget model? | Use the current eClinicalWorks and Sunoh commercial materials | Use the Glass pricing page, then confirm current connected-workflow terms directly with Glass |
That comparison gives buyers a practical path. If the team wants the most eClinicalWorks-native documentation product, review Sunoh directly. If the team wants ambient documentation plus clinical decision support in one workflow, evaluate Glass directly.
Security, HIPAA, and review model
Before production use, eClinicalWorks teams should confirm the BAA path, clinician review workflow, implementation scope, and support model directly with Glass. The same diligence should apply to every product in the shortlist.
The clinician review model is central. Glass can draft and organize output, but clinicians should review the result and complete final documentation through the approved workflow. That keeps the deployment aligned with how medical documentation and clinical judgment actually work.
For many practices, the right security and rollout review includes:
- who can access Glass
- which visit types are in scope
- how output is reviewed before final use
- how issues are reported
- which PHI terms apply
- what happens if a clinician does not trust an output
- how the practice decides whether to expand the pilot
The goal is not only compliance. The goal is to make adoption safer and easier because everyone knows what the workflow is supposed to do.
What a strong eClinicalWorks rollout plan looks like
A strong rollout plan is specific. It names the clinician cohort, visit types, note outputs, CDS outputs, support owner, feedback process, and success metrics.
The first cohort should answer these questions:
- Did clinicians use the note draft?
- Did clinicians use the clinical support layer?
- Did chart-close time improve?
- Did note quality improve or stay stable?
- Did the workflow fit the practice’s eClinicalWorks process?
- Did staff understand how to support the workflow?
- Did the pilot produce enough evidence to expand?
If the answers are not clear, keep the pilot small and fix the workflow. If the answers are strong, expansion becomes a disciplined operational decision instead of a leap of faith.
When Glass is a strong eClinicalWorks fit
Glass is a strong fit for eClinicalWorks practices that want ambient documentation and clinical decision support in the same clinician-reviewed session. The product is most relevant when the practice wants to reduce note burden without separating the note from the clinical thinking that happens during the visit.
That makes the evaluation different from a scribe-only comparison. Sunoh and other eClinicalWorks documentation paths may be enough when the main goal is a faster note. Glass is worth evaluating when clinicians also want differential support, cited Q&A, suggested next steps, and assessment-and-plan drafting while they are still working through the case.
Good-fit eClinicalWorks scenarios include:
- complex follow-up visits where the note, plan, and clinical reasoning need to stay aligned
- new patient visits where prior context and diagnostic uncertainty matter
- visits where clinicians already leave the EHR to check references or organize the differential
- practices that want a narrow, BAA-backed workflow before broader rollout
- teams that need a clear clinician-review model before production PHI use
Glass may be less urgent for a practice that only needs dictation or a basic ambient note. The more important question is whether the practice wants one workflow for documentation plus clinical support. If the answer is yes, the eClinicalWorks evaluation should measure both sides: note quality and cleanup time, plus whether clinicians actually use the CDS layer in real visits.
The practical test is simple: can a small eClinicalWorks cohort use Glass on defined visit types, review the output safely, and show where the workflow helps? If the answer is clear, the practice has a stronger basis for expansion. If the answer is mixed, the feedback points directly to template fit, training, visit-type selection, or support changes before the next cohort.
FAQ
Does Glass Health integrate with eClinicalWorks?
Yes. Glass supports eClinicalWorks-connected workflows for ambient scribing and chart-aware clinical decision support. Teams should confirm the current supported workflow directly with Glass during evaluation.
Is Glass the same kind of product as Sunoh?
No. Sunoh is the eClinicalWorks-published ambient scribe baseline. Glass should be evaluated when the team wants ambient documentation plus clinical decision support, including differential support, cited Q&A, suggested next steps, and assessment-and-plan drafting.
Can we run Glass alongside Sunoh in evaluation?
A side-by-side review may be possible depending on the practice environment. Define which clinicians, visit types, capture workflow, note output, and final documentation process each product will use before comparing results.
Who owns final eClinicalWorks documentation?
The clinician owns final review and final chart actions through the approved eClinicalWorks workflow.
What should an eClinicalWorks pilot measure?
Measure note quality, cleanup time, chart-close workflow, clinician adoption, usefulness of the CDS layer, operational friction, and compliance readiness.
Does Glass support BAA-backed workflows?
Yes. Glass supports BAA-backed healthcare workflows. Confirm the exact BAA terms and deployment scope directly with Glass before production PHI use.
Does Glass publish pricing?
Glass publishes plan information on its pricing page. For eClinicalWorks-connected deployments, confirm current packaging, workflow scope, and contracting terms directly with Glass.
What is the safest first step?
Start with a narrow pilot. Define the clinician cohort, visit types, note outputs, CDS outputs, BAA path, review model, and success metrics before production rollout.