Solventum Fluency Align
Solventum Fluency Align is the ambient documentation product of Solventum, formerly 3M Health Care, and it approaches the category from a direction no other scribe in this index does. Solventum is a coding and revenue integrity company first, author of foundational patient classification methodologies including APR DRGs and Potentially Preventable Events, and Fluency Align sits inside its capture to code suite rather than standing alone.
The product bundles ambient capture with the established Fluency Direct front end speech recognition so clinicians can dictate or work ambiently in one environment, generates a note for review, signature and completion, and surfaces real time coding support, risk factors and documentation opportunities during the encounter. In January 2026 Solventum became a MEDITECH Alliance Accelerator partner with direct integration into MEDITECH Expanse. The thing to weigh is structural: a documentation tool built by a company paid to improve coding capture prompts differently from one built by a company paid to save time.
Capability Axes
An AI Health Index grade measures what a buyer can verify from public sources on the date shown. It is not a rating of how good the product is. A vendor can build an excellent system and grade low on an axis because it publishes nothing an outsider can check. How grades read
Ambient generation is genuinely the product, but the moat is not the model. Solventum's asset is forty years of coding content and the patient classification methodologies it authored, including APR DRGs and Potentially Preventable Events, plus a stated 400 content experts.
That is the moat is the dataset precedent this index applies to Reveleer and Haystack: the classification content would survive the removal of the ambient model, and it is what makes the notes commercially useful downstream. Fluency Align is also one solution among several on the Fluency platform alongside Fluency Direct, Fluency Go and transcription.
Clear review gate, plainly stated: the auto generated note is ready for the clinician to review, sign and complete, and Solventum describes maintaining clinician oversight and EHR workflow integrity as a design commitment rather than an afterthought. Coding support and contextual prompts are presented as suggestions during the encounter rather than applied automatically. Held at B because no confidence threshold, acceptance rate or edit burden figure is published, and because the real time prompting behaviour described below deserves its own scrutiny.
No accuracy figure, no model card, no named models and no evaluation methodology. There is also an unresolved inconsistency in how the company characterises its own technology: corporate materials describe audit defensible DETERMINISTIC AI, which is a positioning claim against probabilistic competitors, while the Fluency Align product materials describe conversational and GENERATIVE AI. Those are different things and a buyer evaluating output variability deserves to know which applies to the ambient path.
Nothing published identifies any party in the chain. No model or model family is named, no foundation model provider is disclosed, no hosting or cloud arrangement is described for this product, and no sub processor list was located in two passes. One published inconsistency makes the absence harder to work around rather than easier.
Corporate materials describe the company's artificial intelligence as deterministic and audit defensible, which is a positioning claim aimed at probabilistic competitors, while the product materials for this ambient offering describe conversational and generative artificial intelligence.
Those describe different systems with different suppliers, different failure behaviour and different data flows, and a buyer cannot tell from anything public which one governs the ambient documentation path or what sits behind it. The parent is a large multinational with an extensive supplier base and an established compliance function, so the information certainly exists internally.
This axis records what a counterparty can establish from published artifacts, and on that basis there is nothing. Ask which technology actually produces the ambient note, and for a sub processor list scoped to this product rather than to the corporate group.
More specific than most vendor claims and still not evidence. Early adopters are reported to have seen a 26 percent reduction in burnout and a 35 percent decrease in time spent charting outside clinic hours, and named site case studies exist including Cherry County Hospital and Clinic and El Camino Health.
What is missing is everything that would make those numbers checkable: no denominator, no cohort size, no measurement instrument named for the burnout figure, no comparison group and no peer reviewed publication. Graded C on the standing precedent that customer reported percentages without design do not substitute for evidence of benefit.
Only baseline controls are named: built in encryption, role based access and audit visibility. Those are table stakes rather than differentiators. Nothing was located on audio or transcript retention periods, de identification, or whether customer data is used to train models, which are the disclosures this index treats as decisive on an axis whose input is recorded clinical conversation. Graded on what is published rather than on what an enterprise vendor of this size is likely to hold internally. Refresh candidate.
No product specific business associate agreement posture, template or scope statement was located.
For an enterprise supplier of this size selling into health systems, executed agreements plainly exist and every customer will have one. The gap this axis measures is different: a prospective buyer cannot establish terms, scope or subprocessor position before entering a sales conversation, and neither can anyone comparing suppliers.
Two things make the question more than routine here.
The first is corporate continuity. This product line has changed hands more than once, having been acquired into a large industrial group and subsequently separated into a standalone healthcare company. Health systems that papered agreements with a predecessor entity should confirm those agreements were properly assigned or novated to the current one, that the named business associate is the entity actually processing today, and that subprocessor consents given historically still describe the current arrangement. Contract continuity across a corporate separation is exactly the sort of thing that is assumed rather than checked.
The second is portfolio breadth. The same organisation supplies coding, clinical documentation integrity and revenue cycle services alongside documentation. Protected health information moving between those functions stays inside one corporate group but serves different purposes, and a buyer should establish whether the agreement covering the ambient product also permits use of that content by adjacent lines of business, or whether each is separately scoped.
Ask for the agreement, the entity named in it, the subprocessor list, and the permitted purposes across the vendor's other services.
No named or dated attestation for this product, and no trust centre, was located in a second pass. What is published is control description rather than examination: encryption, role based access and audit visibility are named as built in, which are the right controls to have and are not evidence that anyone independent has tested them.
One route is available here that fails for most of this category, and it is worth naming as the obvious next source rather than leaving the absence flat. This vendor is a listed company subject to annual reporting obligations, which include describing the processes by which it assesses, identifies and manages cybersecurity risk, along with board oversight and management accountability. That disclosure will exist. It was not retrieved in this pass and it is where a buyer or a future assessment should look first.
Two cautions belong with that route when it is used. A securities filing describes an enterprise programme with named governance; it is not an independent examination of controls, which is what an attestation provides. And an enterprise level disclosure from a company of this size will describe the organisation rather than this module specifically, so it answers a different question from the one a buyer of the ambient product is asking.
Scale and lineage raise the expectation rather than lowering it. This is an established enterprise supplier selling into health systems, with a product line carrying decades of history through multiple owners. Buyers of that profile treat an examined posture as a procurement baseline.
Ask which report is held, of which type and period, and whether its scope covers the ambient documentation product or the wider estate.
No clearance claimed and none required for ambient documentation. The clinician reviews, edits and finalises the note in the record system, and the vendor states plainly that the power remains with the clinician to ensure the generated note reflects the care provided.
What governs is payment integrity, and this vendor sits closer to it than most because documentation is one part of a business that also spans coding, clinical documentation integrity and revenue cycle work. The product is described as offering real time coding support and contextual prompts, and as surfacing relevant risk factors and documentation opportunities during the encounter. Surfacing documentation opportunities in real time is clinical documentation integrity moved to the point of care, which shapes what is recorded while it is being recorded rather than reviewing it afterwards.
One marketing claim deserves examination because it is unusual and consequential. The organisation describes delivering audit defensible, deterministic AI. Determinism means the same input yields the same output, which is a meaningful property for a coding or compliance engine and is plausible for the rules and content based systems this company has built over decades. It is not an ordinary property of generative models, and the ambient note is explicitly generative. A buyer should establish which components the determinism claim covers, because a single phrase is being applied across a portfolio that plainly contains both kinds of system, and the difference matters precisely where audit defensibility is being promised.
Audit defensible is itself a strong formulation. A note is defensible if it reflects the care delivered. Establish what the term is being measured against.
Graded on incentive structure rather than on an absent fairness statement, following the coding drift reasoning this index applied to Candid Health and Charta Health. Fluency Align does not only transcribe: it surfaces relevant risk factors and documentation opportunities in real time, inside a capture to code suite sold by a company whose commercial value is measured in coding accuracy and revenue integrity.
Prompting a clinician toward documentation that supports higher acuity capture, at the moment of the encounter and before the note exists, places the incentive gradient earlier in the workflow than pre bill review does and makes it harder to audit after the fact, because the prompt shaped what was said rather than what was coded. Solventum's audit defensible framing suggests it is alive to this. No fairness, subgroup or accent and dialect disclosure was located.
Two passes located no accuracy or error figure, no published limitations, no performance guarantee, no remediation commitment and no indemnity or warranty language for this product. Only baseline security controls are named, which speak to protecting data rather than to standing behind output. The specific problem on this axis is that the product's own technical description is unstable in public.
Corporate materials describe deterministic and audit defensible artificial intelligence while the product materials describe conversational and generative artificial intelligence, and a buyer cannot write an acceptance test, an error tolerance or a monitoring plan without knowing which applies. Variability is the thing being contracted for here, and the published representation does not settle it.
Set against that, the product is sold into enterprise health system agreements through a large multinational, so a buyer negotiates against a substantial counterparty with real contracting capacity, and the absence of public terms says less than it would for a self serve product.
The remedy is straightforward and belongs in diligence: get the representation about which technology produces the note in writing, together with whatever accuracy commitment the vendor is prepared to attach to it.
Verified in this pass: direct integration with MEDITECH Expanse, formalised in January 2026 when Solventum became an Accelerator partner in the MEDITECH Alliance, described as a longtime partner. That is a meaningful position in the acute segment where MEDITECH is strong and where several ambulatory focused scribes are absent.
Broader EHR coverage is implied by the long deployment history of Fluency Direct across health systems but was not enumerated or verified here, so the grade reflects one confirmed deep integration rather than an asserted list.
No hosting region, residency option or subprocessor list was located, and nothing establishes whether a third party model service processes the encounter or what it retains. Delivery is cloud based with record system integrations including a formal alliance partnership with a major hospital platform, and mobile review and completion.
One capture path on this record has no counterpart elsewhere in the lane and deserves its own questions. Alongside a mobile application, the product supports a dedicated ambient hardware device placed in the room. Every other vendor in this category captures through a phone, tablet or browser the clinician already owns.
A purpose built listening device in an examination room is a materially different data path and a different asset to govern. Establish who owns and manages it, what it holds locally and for how long, how it is provisioned and decommissioned, what network access it requires inside the clinical environment, how it is patched, and how it is known to be off. A device that lives in the room rather than in a pocket is always present, which is an advantage for capture and a distinct question for consent and for security.
The corporate history adds a further scoping point. This product line has moved through more than one owner, having been acquired into a large industrial group and then separated again into a standalone healthcare company. A buyer should establish which legal entity currently operates the infrastructure and holds the data, since the answer has changed more than once.
Ask for the hosting region, the subprocessor list, the model provider, and the full lifecycle of any hardware capture endpoint.
No published rate card. Enterprise sold through Solventum's health information systems organisation and typically procured alongside coding and revenue integrity products rather than as a standalone scribe line item.
Enterprise oriented and workflow flexible rather than specialty enumerated. Its distinguishing coverage claim is modality rather than specialty: a single environment supporting both front end dictation and ambient capture, letting an organisation phase adoption by clinician readiness instead of forcing one workflow, which is a real deployment advantage in mixed acceptance medical staffs. Positioned across medical specialties with acute reach through MEDITECH. No specialty count and no language coverage published.
Compared With
Each comparison carries a written verdict, the buyer conditions that favor each vendor, and a graded side by side. Pairs that cross a category boundary are grouped separately, and their verdicts state where the boundary sits rather than manufacturing a head to head.
Pricing
Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.
| Entry Price | Pricing Basis | BAA Tier | Implementation | Source |
|---|---|---|---|---|
|
Not published. Enterprise sold within the Solventum capture to code suite
|
Enterprise negotiated, typically alongside coding and revenue integrity products rather than as a standalone per provider scribe licence | Not retrieved in this verification pass | Not published. | Vendor Published |
No published price. The commercial shape matters more than the number here: Fluency Align is bought inside a capture to code relationship rather than as a standalone scribe, so the business case presented is usually revenue integrity and coding accuracy rather than minutes saved.
That framing is worth naming explicitly during evaluation, because a documentation tool justified on coding capture is being measured on something other than clinician time, and the two do not always point the same way.