Avo

The foundation is curated clinical content, not a model. Avo Pathway, described by the company as its foundational product, is a library of digitised society guidelines and calculators, and the platform's stated business model invites content publishers and evidence based organisations to embed their intellectual property into Avo powered copilots.

That is the moat is the dataset pattern this index applies to Reveleer and Haystack: strip out the generative layer and a valuable guideline library and no code tool builder remain. The AI is real and does substantial work on top of it, which is why this is B rather than C.

The widest clinical suggestion surface of any product in the scribe portion of this index, with no published limits. Beyond note generation it drafts orders, identifies care gaps, produces differential diagnoses, generates treatment recommendations and suggests DOSING. Dosing in particular is a recommendation with direct patient consequence. No confidence threshold, escalation path, abstention behaviour or acceptance rate was located for any of it.

Credit where due on design philosophy: Avo positions itself explicitly against alert driven decision support, arguing for standardising care with love rather than alerts, which is a considered stance on alert fatigue rather than a marketing line. But a philosophy is not an oversight mechanism.

No accuracy figure, model card, named models, hallucination rate or evaluation methodology was located. The closest thing to a performance statement is a customer testimonial saying they have not seen hallucination issues, which is impression rather than measurement. For a product generating differential diagnoses and dosing suggestions, published error characterisation matters more than it does for a note writer, and none exists.

This record splits in an unusual direction and a buyer should see both halves, because the vendor draws its data line in a place most do not. On patient content the commitment is strong and architectural: clinical data collected to assist decision making, including data drawn through record system integrations, is processed only in real time and is not stored or saved after processing, and patient clinical data is stated not to be stored, saved or sold.

That matters more here than at most vendors because the integrations read deeply, across care summaries, radiology reports, laboratory results, vitals, medications, notes, problem list items, diagnoses and demographics. A no retention commitment is a stronger answer than an encryption claim and few vendors in this index make it. On clinician content the same policy goes the other way.

Usage information is defined to include the clinician's name, national provider identifier, email, specialty, geography and institutional affiliations, the site participates in a healthcare communications network under which registration includes registration with that network, and professionally relevant contact information is disclosed to the network and its members by default. The policy then subordinates itself, resolving conflicts in favour of the network's policy.

So identified clinician data flows to a third party network by default while patient data is not retained at all. On enumeration the model layer is unnamed and no sub processor list was located. Ask which entities the network comprises and whether clinician disclosure can be declined.

Stronger than most in this category and one claim needs verifying before it is relied on. Avo states that randomised controlled trials have shown it saves clinicians around 50 percent of their time and improved emergency department admission delays by 30 percent.

If accurate that would be among the best evidence in this index, but the claim appears on a marketplace listing with no citation, publication, author list or trial registration located in this pass, so it is graded as asserted rather than verified.

Independent of that, named institutional customers are real and specific, including Children's of Minnesota, Driscoll Children's Hospital, PM Pediatric Care and Harbor Health, alongside implementation of a RAND consensus pathway for vertebral fragility fractures. Ask for the trial citations; they would move this to A.

The patient data commitment is the strongest in this segment and it is architectural rather than procedural. The privacy notice states that when patient related clinical data are collected to assist clinical decision making, including data collected via electronic health record integrations, that data is processed only in real time and is not stored or saved after processing, and that patient clinical data is not stored, saved or sold.

That matters here more than at most vendors because the integrations read deeply, covering care summary data, radiology reports, lab results, vitals, medications, notes, problem list items, diagnoses and demographics. A no retention commitment is a different and stronger answer than an encryption claim, and few vendors in this index make it. Held below the top grade for reasons concerning the clinician rather than the patient.

The same policy defines usage information as including the clinician's name, national provider identifier, email, specialty, geography and institutional affiliations, and separately discloses that the site participates in a healthcare communications network, under which registration at the site includes registration with that network and the clinician's contact and professionally relevant information is disclosed to the network and its members by default.

The policy then subordinates itself, stating that where its own notice conflicts with the network's policy, the conflict resolves in favour of the network's policy. A vendor that will not retain patient data while routing identified clinician data to a marketing network by default has drawn its privacy line in an unusual place, and a buyer should see both halves.

This assessment rests on documents that were read rather than on a search that came up empty, which is the distinction that matters. The full privacy notice and terms of use were retrieved and read, and neither mentions HIPAA, a business associate agreement, a covered entity or a business associate anywhere.

The notice is structured as a GDPR shaped instrument, with rights of access, rectification, erasure, portability, restriction and objection, complaint routes to national data protection authorities, and specific California and Nevada notices, but the United States health privacy framework is simply absent from it.

That is a real gap for this particular product rather than a formality, because the platform reads labs, vitals, medications, clinical notes, problem lists and diagnoses out of Epic, MEDITECH, athenahealth and Juno, and writes clinical notes and pended orders back. A vendor operating that deep inside the chart is functioning as a business associate whatever its public documents say.

The limit should be stated honestly: absence from the public legal documents is not proof that no agreement exists, and an enterprise subscriber agreement very probably contains one, since health systems of the size named as customers would not sign otherwise. SOC 2 Type II is separately attested and linked from the site footer, which is the adjacent assurance. But this axis measures what a buyer can establish before entering a sales conversation, and on that basis there is nothing. The agreement and its execution path are the single highest value questions to put to this vendor.

SOC 2 Type II is stated with the type explicitly specified, surfaced in the site footer on every page and linked to a dedicated announcement. That answers the question worth putting to every SOC 2 claim, and specifying Type II matters because it is an audit of controls operating over a period rather than a point in time design review, so a vendor stating it is telling a buyer it has been examined across months of real operation.

The placement is a small credit in itself, since it sits in the persistent footer rather than being buried on a compliance page a buyer has to hunt for. Held below a higher grade on specific missing items. There is no public trust centre, so the attestation is asserted on the vendor's own site rather than surfaced through an independent platform in the way some competitors in this segment manage.

No ISO 27001, HITRUST, penetration testing statement, vulnerability disclosure policy or named subprocessor list was located. The privacy notice describes safeguards only in general terms, an internal framework of policies and minimum standards with need to know access limits, without naming an encryption standard, a key management practice or a control framework. Attestation and description are different goods, and vendors in this segment tend to be strong on one or the other rather than both.

No FDA clearance, none claimed and none apparently sought. The clinical decision support exclusion position is argued harder in this vendor's own legal text than at any comparable product, and the terms of use do the work. The services are stated to offer health related information in an easily accessed format for educational purposes only, the information is stated as not intended to replace clinical decision making by a qualified professional, clinicians are stated to be ultimately responsible for decisions on diagnostics, symptoms and therapeutic treatments, the company states plainly that it does not give medical advice and does not provide medical or diagnostic services, and it states that its content is not intended for use by patients.

The substantive basis for the exclusion is present rather than merely asserted, since recommendations are anchored to named published guidelines including medical society pathways, recovery milestones and consensus pathways, so a clinician can go and read the source. The open question is one this segment will eventually have to answer, and it is sharper here than at comparable products: this product does not only inform, it acts.

It pends orders into Epic and drafts clinical notes back into Epic, athenahealth and Juno. An educational purposes disclaimer fits comfortably around a reference that answers a question and less comfortably around a system that stages an order in the chart, however firmly a human remains the one who signs it. Worth asking for the regulatory rationale for the order pending function specifically rather than for the platform in general.

Graded up on a structural property rather than a disclosure document.

Avo's recommendations are anchored to named published sources, including medical society guidelines, MCG recovery milestones and RAND consensus pathways, rather than to model inference or to an institution's own historical patterns. That is the same property that earned Nym Health credit for being anchored to published AMA, CMS and WHO guidance rather than to institutional intensity: a clinician can trace a recommendation to its source and disagree with it on the evidence.

The no code builder also means the health system, not the vendor, decides which guidelines are deployed, which puts content governance with the organisation.

Held at B because no fairness statement, subgroup analysis or accent and dialect performance disclosure was located, despite support for 50 or more languages.

Two passes located no accuracy figure, no hallucination rate, no published limitations, no evaluation methodology and no warranty, indemnity or remediation commitment, and the output makes that the most consequential absence recorded in this backfill so far outside regulated devices. This product generates differential diagnoses and dosing suggestions.

A dosing suggestion is not documentation of a clinician's decision, it is an input to one, and an error in it can reach a patient through a prescription rather than through a record. A differential shapes what is investigated and what is ruled out, so an omission is as harmful as a wrong inclusion and considerably harder to notice. For output of that kind, published error characterisation is not a nice to have, it is the basis on which a clinician decides how much scrutiny to apply.

The closest thing to a performance statement located is a customer testimonial reporting that they have not seen hallucination issues, which is an impression from one user about the absence of a phenomenon they would only sometimes detect, and it is the weakest evidential form this index tracks. Ask for an error rate on dosing suggestions specifically, for what the system does when it is uncertain, and for what the vendor commits to when a suggestion is wrong.

This is the deepest electronic health record position in the clinical decision support segment, and it clears the top grade on three independent grounds. First, marketplace credentials on two major systems, which is the stronger integration signal: a live Epic Showroom listing and a listing on the athenahealth Marketplace, alongside MEDITECH Expanse via the external applications dock and Juno Health.

Second, the integration is bidirectional and writes to the chart, which almost nothing else in this segment does. It reads care summary data, radiology reports, lab results, vitals, medications, notes, problem list items, diagnoses and demographics, and it sends back clinical notes and pends orders directly into Epic, with note write back also into athenahealth and Juno. Reading the chart is table stakes; staging an order in it is a different order of integration.

Third, the implementation cost is published as a number: an Epic integration build stated at under 20 hours, with a named access route per system. A published integration effort figure is rare and directly answers the question a chief information officer asks first.

The contrast within this segment is instructive: a competitor that deliberately holds no protected health information needs no clinical data exchange at all and carries no patient context into its answers, while this product sits inside the chart in both directions. Those are opposite design choices with opposite consequences rather than different degrees of the same thing. Held short of a perfect record only by the absence of a named FHIR or SMART on FHIR conformance statement.

Delivery spans standalone web and native iOS and Android applications plus embedded deployment inside four named electronic health records, and the implementation shape is published rather than gated: the Epic integration build is stated at under 20 hours, after which clinicians reach the product from an activity tab in Epic.

Access routes are named per system, including the external applications dock in MEDITECH Expanse and the left hand sidebar within a patient chart in athenahealth, with athenahealth activation handled jointly by the vendor and an athenahealth representative.

A data residency statement exists, which puts this record ahead of most of the segment: the privacy notice states plainly that the services and their servers are located in the United States, and warns non United States users that their information may be transferred to and processed in a jurisdiction whose privacy laws may be less protective than their own.

Named deployments span a genuine size range, from children's hospitals and large academic systems to smaller value based care organisations, alongside dedicated propositions for rural and small hospitals, large and mid size hospitals and ambulatory care. Held below a higher grade on two points.

The residency statement is a country and nothing finer, with no region, failover location or subprocessor list, and it sits in tension with the company's self description in the same document as a global organisation. And no customer count, uptime commitment or support model was located.

No pricing page, no published enterprise rate and no rate card. What the vendor does publish is real but peripheral and buried: the terms of use disclose actual consumer subscription prices for two specialty applications, at 19.99 dollars a year for one after a 30 day free trial and 9.99 dollars a year for the other after a 90 day trial, with auto renewal terms and cancellation windows stated.

Those are genuine published prices and they earn credit, but they price two narrow applications rather than the platform a health system actually buys, and they sit inside legal text rather than anywhere a buyer would find them. The enterprise tier, which is the whole commercial relationship for the named hospital customers, is entirely gated behind a demo request.

A comparative pricing claim without a number is made on the products page, describing competitive pricing compared to other ambient solutions, which asserts a position on cost while disclosing nothing that would let a buyer test it. Third party aggregators publish estimated ranges, which are not treated as vendor disclosure here.

One structural fact belongs on this axis rather than being left to the privacy note, because it is a revenue fact: the privacy notice states that commercial clients including life sciences companies use the vendor's marketing solutions to fund and distribute clinical guidelines and to present clinicians information about clinical trials and innovative therapies. Part of the content a clinician sees is industry funded, and that is disclosed in a privacy policy rather than in a published advertising or sponsorship policy.

The broadest and most carefully specified coverage in this part of the index. Capture handles three or more participants across 50 or more languages, with the participant mix named explicitly as child, parent, translator and clinician. That is the encounter shape most ambient scribes quietly fail at, and it is the norm in paediatrics and in any consultation using an interpreter. The customer base matches, with several named children's hospitals.

Clinician coverage extends beyond physicians to advanced practice providers, medical assistants, dieticians and behavioral health providers, and workflow coverage spans admission, rounding, discharge, charting and care planning rather than the outpatient visit alone.