RevMaxx

Ambient capture, structured note generation and code assignment are the whole product, with no services layer or adjacent business underneath.

The review gate is described explicitly and in the right order, which is more than several better funded competitors manage: the system generates a structured note with codes, the clinician reviews and edits it, the clinician signs off, and only after approval does the note update the correct patient record in the EHR. Making approval the precondition for the write rather than filing pending review is the safer of the two patterns. Held at B because no acceptance rate, edit burden figure or confidence threshold is published, and because codes are generated alongside the note rather than being separately confirmed.

No accuracy figure, model card, named models or evaluation methodology located. The headline performance claim, automating up to 95 percent of clinical documentation, uses the up to construction that is satisfied by any result at all and cannot be falsified. The pipeline is described mechanically enough, machine learning and natural language processing identifying clinical context and placing content into note sections, but nothing is measured.

Nothing identifies any party in the chain: no model or model family, no foundation model provider, no hosting arrangement and no sub processor list was located in two passes. The two statements standing in for disclosure both contain qualifiers that move the judgement back to the vendor.

Clinical information is said never to be stored or shared without permission, which describes a permission gate rather than a boundary and leaves open what that permission covers, and identities are said to be protected when artificial intelligence is used, with no mechanism, scope or pipeline position given. Neither tells a buyer who receives content.

The product range widens what the question covers, because the company operates both a documentation platform and a revenue cycle platform, so encounter content potentially feeds coding models as well as transcription ones, and those are different chains with different parties and different consequences when wrong. Nothing addresses either. Ask for a sub processor list, and ask the training and sharing questions separately for the documentation and the revenue cycle products rather than as one.

No study, controlled evaluation, accuracy benchmark, third party rating or named health system outcome data located. A sourcing caution applies more strongly here than to most entries: nearly all discoverable material about this vendor, including its comparisons against named competitors, is published on the vendor's own site. Treat it as product claims rather than as market assessment.

The disclosures this axis measures are absent, and two of the statements standing in for them contain qualifiers that shift the judgement to the vendor.

No retention schedule, no deletion commitment with a stated period, and no statement on whether customer audio or transcripts are used to train or improve models were located. Encrypted processing under the health privacy rule is asserted throughout.

The first qualifier is in a retention claim. The vendor states that clinical information is never stored or shared without your permission. That is not a statement that information is not stored. It is a statement that storage and sharing happen with permission, which leaves entirely open what permission was granted, where it was granted, and whether a clinician clicking through terms at signup has already given it. Establish what the terms actually permit rather than reading the marketing sentence as a commitment.

The second is in a de identification claim. The vendor states that when AI is used, patient identities are protected so personal details are never exposed. No mechanism is described, no scope is given, and it is not stated at what point in the pipeline this happens or what is removed. De identification applied before a model call is a meaningful control; a general assurance that identities are protected is not the same thing and cannot be relied on as one.

The training question matters more here than for a narrower product, because this vendor operates both a documentation platform and a revenue cycle platform. Encounter content used to improve coding models is a different proposition from encounter content used to improve transcription, and neither is addressed.

Ask for the retention schedule, the training position in the contract rather than the marketing, and the mechanism behind the de identification claim.

States HIPAA compliant, encrypted processing. Business associate agreement terms are not published for inspection before contracting.

A second pass located no SOC 2 report of either type, no HITRUST certification, no ISO 27001, no penetration testing statement and no trust centre.

What stands in their place is an unusually dense cluster of phrases that sound like standards and are not. Across the vendor's material the security posture is described as enterprise grade, as running on healthcare grade servers, and as following the highest health privacy and record system data protection standards. None of those is a standard. Enterprise grade and healthcare grade are marketing constructions with no defined content, and highest standards names nothing a buyer could ask to see. Three such phrases in one vendor's material is worth noting as a pattern rather than treating each as an isolated overstatement.

The underlying controls that are described, encryption, audit trail logging and monitored access, are the right controls to have and are the ones every competitor also lists. They are statements about design, not examinations of it.

The absence carries more weight than a scribe alone would warrant because of what this organisation handles. It operates a revenue cycle automation platform alongside the documentation product, so the same customer relationship involves clinical records, coding output and claims data. That is a broader concentration of sensitive material than a documentation vendor holds, and a correspondingly larger surface for an examination to cover.

The grade reflects what a counterparty can verify before contracting rather than a judgement that controls are absent. Ask for the report, its type and period, and whether its scope covers both platforms or only one.

No clearance claimed and none required for ambient documentation. No United States device pathway attaches. What governs is payment integrity, and this is the most complete instance of that in the category, beginning with the company's name.

The organisation runs two platforms, one for documentation and one for revenue cycle automation, and describes them as solving the same problem. The scribe adds diagnostic, procedural, hierarchical condition category and evaluation and management codes, and the vendor states that it calculates risk adjustment factor scores so physicians can capture the full complexity of their patient population. Marketing language throughout is explicit: revenue optimised coding, capturing every billable opportunity, preventing revenue leakage, maximising reimbursements.

Risk adjustment scoring is where this record differs from peers that stop at coding suggestions. A risk adjustment factor score determines payment for a patient population under risk bearing arrangements, so a documentation product calculating it is operating directly on the mechanism a published policy analysis identified as the one taxpayers ultimately fund. That analysis recorded ambient scribes producing measurable increases in documented risk adjusted diagnoses per encounter and treated whether that reflects better documentation or more intensive coding as unresolved. Here it is not incidental to the product; it is the product's stated purpose.

Two specific things to press. The vendor describes codes being generated and uploaded into the record system with minimal human intervention, which sits in tension with the clinician review that the entire regulatory position for ambient documentation rests on. And the framing is one directional: undercoding is named as the risk to be reduced, overcoding is not mentioned. A system that only moves one way across a defensible range is not correcting error.

The product also serves dentistry, which runs on different coding and payer rules.

Graded on incentive structure rather than an absent fairness statement, consistent with how this index handles coding adjacent products. RevMaxx generates HCC codes and produces instant RAF score calculations from captured conditions, which places it on the risk adjustment gradient running through this index from MarianaAI at the aggressive end through Sayvant and S10.AI.

It sits at the milder end: RAF is presented as clinical risk and expected cost insight rather than as a marketed revenue uplift, and no percentage revenue claim is attached. Even so, a system that assigns HCC codes from conversation and computes risk scores carries audit exposure the buyer holds, and no governance framework, audit trail description, fairness statement or subgroup analysis was located.

Two passes located no accuracy or error figure, no published limitations, no warranty, indemnity or remediation commitment. The headline claim, automating up to 95 percent of clinical documentation, uses the up to construction that is satisfied by any result at all and therefore commits the vendor to nothing. Two other published statements deserve attention because they read as commitments and are not, and the pattern is worth applying elsewhere in this index.

The first is that clinical information is never stored or shared without your permission. That is not a statement that information is not stored, it is a statement that storage and sharing occur with permission, which leaves entirely open what permission was granted, where, and whether a clinician clicking through terms at signup has already supplied it. The second is that when artificial intelligence is used, patient identities are protected so personal details are never exposed.

No mechanism is described, no scope is given, and nothing states at what point in the pipeline it happens or what is removed. De identification applied before a model call is a meaningful control; a general assurance that identities are protected is not the same thing and cannot be relied on as one. Read both against the actual terms rather than the marketing sentence, and ask for an accuracy figure with a definition alongside them.

A broad named list reached by mixed and mostly shallow means, and the mechanism matters more than the list. Supported systems include Epic, eClinicalWorks, athenahealth, NextGen, Cerner, Tebra, AdvancedMD and PointClickCare, with connectivity described as API, robotic process automation or a lightweight Chrome extension depending on the system.

RPA and browser extension paths reach systems that would otherwise require a build, but they operate through the interface rather than a sanctioned data channel, so naming Epic alongside a Chrome extension describes reach rather than depth. PointClickCare support is the genuinely distinctive entry, since it opens skilled nursing and long term care.

No hosting region, residency option or subprocessor list was located, and the vendor's own material contains an unresolved contradiction that a buyer needs to settle before anything else on this axis matters.

The product is described in most places as cloud based, running on secure cloud infrastructure with data stored on the vendor's servers. On one integration page the same vendor states that all clinical information is encrypted, processed locally, and never stored or shared without permission. Cloud processing and local processing are architectural opposites, not two ways of saying the same thing, and both statements are published by the vendor about the same product.

There may be an innocent explanation. A browser extension performs some work on the client, and a vendor writing marketing copy for one integration may have described that loosely. But a buyer cannot tell from the published material whether encounter audio leaves the practice, and that is the single question this axis exists to answer. Ask it directly and get the answer in writing.

The integration mechanism compounds it. The vendor states that record system integration is achieved through secure interfaces or through robotic process automation, and separately that a browser extension is what a practice installs. That makes this the fifth vendor in this lane reaching the chart by driving the user interface rather than through a purpose built connection. Establish whose credentials the automation runs under, how its writes appear in the audit log, and whether the permission model that constrains a human user constrains it equally.

Ask for the hosting region, the model provider, the subprocessor list, and a definitive statement on where transcription and note generation actually run.

A number is published prominently and the terms around it are stated: 199 US dollars per provider per month, no setup fees, no long term contract, and five free patient visits to start. Publishing any figure puts this ahead of most of the category. Held at B rather than A because it is presented as a starting price with separate plans described for solo, group and enterprise buyers that are not published, so the ladder above the entry point is a contact us conversation. Compare S10.AI, graded A for a flat all inclusive rate with no gate above it.

Ambulatory and hospital coverage with specialty specific templates, extended by PointClickCare support into senior living, long term care and skilled nursing. That last setting is close to unserved in this category, reached otherwise only by voize for nursing documentation and River Records for longitudinal follow up, and it is a segment with high documentation burden and thin technology budgets. Held at B because no specialty count, specialty tuning detail or language coverage is published.