Wellsheet

The grade describes the mechanism, not the quality, and the product is a good one. Large language models genuinely drive the core modules: chart summarisation, generated documentation and the pathway agent. But a substantial part of what a buyer is purchasing is not the model. It is an EHR agnostic integration layer, listing in the Oracle, Epic and athenahealth marketplaces, a prioritised workflow interface that predates the generative features, and licensed third party clinical content. The product's own lineage makes this plain: it was sold as a Smart EHR UI, a predictive workflow platform, before the summarisation layer arrived. The Elsevier acquisition sharpens the point rather than softening it, since the strategic logic is explicitly the pairing of an evidence content library with an EHR embedded delivery surface. Compare a pure summarisation engine, which has nothing to sell if the model is removed.

A wide generative and decision shaping surface with no described gate. The product generates hospital course narratives, assessment and plan text and discharge summaries, answers clinical questions conversationally in the EHR, and delivers what the company calls the AI's chosen answer when walking a clinical pathway. No confidence signal, routing threshold, abstention behaviour or required review step was located for any of it. The pathway feature does present supporting chart evidence next to its answer, which is a real verification affordance and the reason this is not lower. One risk specific to this product deserves naming because it is invisible in a demo. The contextual views adapt to the clinician's specialty, role AND USAGE PATTERNS, which means the system personalises what it shows based on what that clinician has looked at before. A prioritisation layer decides what is surfaced and therefore also decides what is not, and personalising that on prior behaviour can quietly harden an individual clinician's blind spot rather than correcting it. Ask what the adaptation is trained on, whether anything is ever suppressed entirely rather than ranked lower, and whether the clinician can see what was deprioritised.

The company states that large language models perform the summarisation, which is more than many admit, and the pathway feature presents supporting evidence from the patient's chart alongside the answer it produced, which is a genuine output level transparency feature. Against that, no model or model family is named, no accuracy figure is published, no omission or false negative measure exists, and no evaluation methodology was located. One structural problem compounds all of it: the site's own footer states that certain described features are illustrative of potential capabilities and not currently in the product, without saying which. That makes every capability claim on the marketing surface unverifiable from outside, including the transparency features themselves. Ask for a demonstration on a real long chart and confirm which described behaviours ship today.

Real deployment at real scale with third party attention, and claims that do not reconcile. On the credit side: Ascension has deployed the product system wide, corroborated by Ascension's own newsroom rather than only by the vendor, and KLAS Research published a report specifically on that deployment. Named use also at Baptist, Indiana University Health, Robert Wood Johnson, Concord and San Juan Regional Medical Center. Applying the standing precision, this is a KLAS report, not Best in KLAS, and it is a case study of one customer rather than a comparative ranking. Held at B for three reasons. The efficiency claims are unreconciled across the company's own surfaces: charting time cut by 50 percent, time in the EHR cut by 40 percent, and two hours saved per clinician daily are three different figures for adjacent claims and none carries a stated denominator or method. The user counts are also unreconciled, with over 30,000 clinicians in earlier material, over 65,000 in a 2026 release and 10,000 plus on the current homepage. And the substantive evidence is gated: the KLAS report needs KLAS access and the vendor white paper sits behind a lead capture form, so a buyer cannot read either without identifying themselves.

No retention period, no statement on whether customer data trains or improves models, and no de identification posture was located. Not Rated records absent evidence rather than an assessed weakness. One minor observation for the diligence list rather than the grade: the privacy policy is published as a PDF hosted on a consumer file sharing link rather than as a maintained page on the company's own domain, which is a weaker artifact than a versioned policy for a product deployed across a health system of Ascension's size.

No HIPAA compliance statement and no business associate agreement terms were located on any retrieved surface. A BAA plainly exists given system wide deployment at a health system of Ascension's scale, but the index grades what is disclosed and nothing is. Worth establishing whether the contracting entity changes following the Elsevier acquisition.

A SOC 2 badge appears on the site and the certification is claimed for the company itself rather than for a hosting provider or supplier, which is the right subject and puts it above the supplier certification watchlist. Graded C rather than higher because the report type is not stated anywhere. Type I versus Type II is the entire assurance question, since one describes controls as designed at a point in time and the other tests them over a period, and this index asks that of every SOC 2 claim. No trust centre, no security page, no status page and no scope statement was located, so nothing here is independently checkable. Ask which report exists, over what period, and to see it under NDA.

No FDA clearance, device authorisation, regulatory pathway statement or clinical decision support exemption analysis was located. Not Rated reflects absent retrieval. Three capabilities make the question live and a buyer should raise all three: the pathway feature delivers a chosen answer on treatment questions, the product surfaces lab interpretations, and discharge alerts flag patients as due for discharge. Guideline grounding in licensed published content may place much of this within clinical decision support exemption criteria, which is the same analysis this index flagged for Avo, but that reasoning should be documented by the vendor rather than assumed by the buyer.

Two genuine positives sit alongside one structural concern. First, the clinical guidance is grounded in licensed, editorially maintained third party content rather than in model inference, with UpToDate pathways, calculators and lab interpretations pre filled from the chart, and the pathway output presents supporting chart evidence. That is the guideline grounding property this index credited in Avo: a clinician can trace the recommendation to a citable source and disagree with it on the evidence. A caution that follows and generalises: grounding the RECOMMENDATION does not ground the INPUTS. A validated calculator pre filled with a value the model extracted incorrectly returns an authoritative looking wrong answer, and the guideline provides no protection against that. Ask how extracted values are verified before they populate a calculator. Second and separately, this record introduces a gradient distinct from the coding gradient this index usually tracks. The discharge module benchmarks against geometric mean length of stay and raises alerts for patients due for discharge, and the company's stated purpose includes ensuring no discharge is delayed. That applies financial pressure to a clinical timing decision. It is not coding intensity and should not be conflated with it, but premature discharge carries readmission and safety consequences and no counterweight measure, readmission rate or otherwise, was located. Separately again, no fairness, subgroup or demographic performance disclosure of any kind was found.

The strongest EHR distribution position in this category and it is verifiable rather than asserted. Three major systems are named explicitly, Oracle Cerner, Epic and athenahealth, and the product is listed in all three vendor storefronts: the Oracle Cloud Marketplace, the Epic Showroom and the athenahealth Marketplace. Being carried in a competitor EHR's own catalogue is a form of external validation, since each vendor applies its own technical review before listing. The company describes a deliberately EHR agnostic stack built so health system IT teams can deploy enterprise wide quickly, and a system wide rollout at Ascension demonstrates that at genuine scale rather than in a pilot. The product layers on top of the record and complements native functionality rather than requiring replacement.

No hosting model, cloud provider, region, residency commitment or customer hosted option was located, and nothing describes where chart data is processed. Marketplace availability on Oracle Cloud implies cloud delivery but does not establish where data resides or who controls it. Not Rated reflects absent retrieval. The Elsevier acquisition adds a question that did not exist before: whether data handling or hosting changes under the new parent.

No price, tier or pricing mechanism is published and every route terminates in a contact form. Not Rated is the house convention for absent pricing rather than a low grade. Two related observations. The supporting evidence is also gated, with the vendor white paper behind a lead capture form and the KLAS report behind KLAS access, so the material a buyer would use to justify the purchase is not openly readable. And the footer disclaimer that some described features are illustrative rather than shipping means the scope of what is being priced cannot be established from public materials at all.

Inpatient acute care is the centre of gravity and the role coverage is genuinely broad within it. The product supports multidisciplinary rounding across physicians of all specialties, nursing and case management, and covers hospital course documentation, assessment and plan, discharge summaries and discharge planning. Contextual views adapt by specialty and by role rather than presenting one layout to everyone. Ambulatory clinics are also served. Graded B rather than A because the depth is in inpatient workflow and care team coordination rather than in specialty specific instruments: nothing equivalent to registry abstraction, safety indicator review or a specialty coding schedule was located.