Conveyor AI by Mobius MD

The ambient generation is real model work, but the company's patented asset and the reason clinicians choose it are not AI. Mobius MD's differentiator is the Conveyor pairing technology, a connectivity invention from 2017 that lets a phone type into any computer without software installation, and the AI scribe was layered onto it later. The moat is not the model: strip out the ambient AI and a valuable universal dictation business remains, which is not true of the pure play scribes.

Conventional draft and review with a structural gate: because output is streamed to wherever the clinician has placed the cursor rather than written into the record through an integration, a clinician is necessarily present and in the document at the moment text arrives. Nothing files itself. No acceptance rate, edit burden figure or confidence threshold is published, and generating 80 percent of a note quickly says nothing about how much of the remaining review burden is correction.

The headline figure measures completeness rather than correctness: more than 80 percent of the note generated within 60 seconds says how much text arrives and how fast, not how much of it is right. Specialty specific models are referenced without being described, and no accuracy figure, model card, named model or evaluation methodology is published. A public blog discusses how ambient scribes work and where they fall short, though that is general education about the field rather than disclosure about this product.

Nothing identifies any party in the chain: no model or model family, no foundation model provider, no hosting arrangement and no subprocessor list is published. Specialty specific models are referenced without being described, so nothing establishes whether those are distinct trained models, configuration of one model, or prompt templates, and the difference matters for who is in the chain. The mobile platform restriction is the only architectural commitment published, and it bounds the client device rather than the processing path behind it.

Named clinician testimonials across orthopedic surgery, internal medicine, family practice, emergency and telemedicine, plus ten verified clients recorded on a third party marketplace listing. No study, controlled comparison, accuracy benchmark or independent evaluation is published. Testimony and client counts are not evidence of benefit.

Claims to exceed the standards specified by HIPAA and HITECH, which is an assertion rather than a control. What lends it some weight is a concrete and costly design decision: the product requires an iOS device and supports no Android path at all, which the company attributes directly to its security requirements. Giving up an entire mobile platform is an unusual thing to do for security theater, so the constraint reads as real. No retention schedule, deidentification practice or training use statement is published.

Compliance with HIPAA and HITECH is stated.

The agreement position comes from the company's own words. In its product listing copy the company states that it provides its service under a signed contract, naming the business associate agreement, and that it requires one. So the agreement is presented as a precondition of service rather than as something available on request, and the answer is given before contacting anyone.

The instrument itself is not published for inspection, no scope statement describes which processing activities it reaches, and nothing establishes whether it extends obligations to subcontractors.

One phrase recurs across this company's material and is not an assurance. It states that the product exceeds the standards specified by HIPAA and HITECH. Those are statutes rather than benchmarks, there is no scale on which a product exceeds them, and no body certifies that it has. It is a marketing formulation rather than a compliance fact, and it sits in the same family as military grade and bank level. It does not undermine the agreement commitment, which is concrete.

No SOC 2 report of either type, no HITRUST certification, no ISO 27001 and no trust center is published.

One product constraint comes with the company's own explanation. The application runs only on Apple mobile devices, and the company states this is due to stringent security requirements. That is a coherent argument on its face, since a single tightly controlled mobile platform offers consistent hardware backed key storage and no sideloading. It is also a design decision presented as a security conclusion, with nothing published to show the analysis behind it or what was rejected. A restriction is not an assurance, and platform exclusivity is not evidence of a posture.

The compliance formulation used alongside it is a non attestation, and it appears across the company's own pages: the product is said to exceed the standards specified by HIPAA and HITECH. Those are laws rather than benchmarks, exceeding them is not a measurable claim, and no body certifies either. It sits with military grade, enterprise grade and bank level in the same family.

Two details are concrete. The hardware dongles are described as bound to a single user account with an encrypted connection to that user's device. The housing carries an antimicrobial additive, which addresses a real infection control problem with shared workstation microphones and is an unusual thing for a documentation vendor to have designed for.

The company has operated since 2011 with a stated United States based team, which raises rather than lowers the expectation that an examination exists somewhere.

No clearance claimed and none required for ambient documentation or dictation. No United States device pathway attaches.

The product is narrow: no coding engine, risk adjustment scoring, decision support, order generation, clinical insight layer, patient facing component, revenue cycle module or billing function is described. The product captures speech and produces text.

The delivery method reinforces how narrow that is. Output arrives wherever the clinician places their cursor rather than into a defined clinical field, so the product has no view of the chart, no access to patient context, and no capacity to act on the patient record. It is a text input method with a clinical vocabulary. That keeps the regulatory position simple.

One consequence runs the other way. Because output is not scoped to a clinical destination, nothing in the product constrains where dictated clinical content ends up. That is a matter of practice governance rather than device regulation, and the tool makes dictating patient information into applications outside the record system as easy as dictating into it.

Markets appear to be United States only, with a stated domestic support and engineering base.

The company publishes no fairness statement, no subgroup analysis, no accuracy breakdown by accent, dialect or speaker population, no evaluation methodology, and no language coverage claim.

The product's lineage is medical dictation, a field where accent handling has been a documented weakness of speech recognition for decades. A vendor building on that lineage is working on a problem the field has known about for a very long time, and is silent about where it stands on it.

One mechanism needs separate attention, because it is presented as a benefit and carries a governance consequence. The system adapts to the individual user. Custom vocabulary can be added, a specialty dictionary selected, and the vendor states that the more it is used the better it gets, with the trained voice profile traveling with the clinician between employers and workstations.

Personal adaptation is useful, and it also obscures how the system performs across different speakers. An adaptive system improves toward each user, which means published accuracy reflects some point along that curve rather than a baseline, and it means the burden of adaptation falls hardest on the users the base model handles worst. A clinician whose speech the underlying model was trained to recognize starts near their ceiling. A clinician with a less well represented accent starts lower and spends longer correcting output before the system catches up, and that unpaid correction work is invisible in any headline figure.

So the disclosure that would matter here is not a single accuracy number but a starting position and a curve.

No accuracy or error figure, no published limitations and no warranty, indemnity or remediation commitment is published.

The headline figure measures the wrong thing. More than 80 percent of the note generated within 60 seconds describes how much text arrives and how quickly, not how much of it is correct, and a buyer reading it as a performance claim would be reading it as something it does not say. Speed and completeness of output are not accuracy.

A pattern seen across this market appears here in a milder form. The company publishes a blog discussing how ambient scribes work and where they fall short, including sound guidance on when a tool should not be trusted with patient information, which is useful category education. It publishes nothing about where its own product falls short. Writing about the failure modes of a technology while declining to characterize your own instance of it leaves a reader better informed about the category and no better informed about the purchase.

One design decision reads as substantive rather than promotional. The product requires an Apple mobile device and supports no alternative path at all, which the company attributes to its security requirements. Giving up an entire mobile platform is an expensive thing to do for appearances, so the constraint is probably real. It speaks to data protection rather than to output correctness.

The company does commit to providing its service under a signed business associate agreement. An agreement governs how information is handled; it does not say what happens when the note is wrong, and those are different protections.

Universal by mechanism rather than by integration, and the distinction is real.

Patented pairing lets an iOS device stream text into any application on any Mac or Windows computer with nothing installed on the computer, so it works with every EMR including Epic, Cerner and MEDITECH without an integration project. A clinician moving between hospitals, systems or employers keeps their profile, templates, dictation preferences and memos, because those live with the clinician's account rather than inside an employer's system. That is a portability argument with real anti lock in consequences for an individual clinician, and it is a different proposition from a vendor that integrates deeply with one record system.

The limits are equally real. Text lands wherever the cursor sits, so there is no structured field population, no chart context flowing in, and no write back. Nothing is read from the record, so the product cannot use prior notes, problem lists or medications as context. Where third party listings say this product integrates with a named EMR, it works alongside rather than connects to.

No hosting region, residency option or subprocessor list is published, and nothing says where transcription and generation run or whether a third party model service is involved.

The architecture is unusual and needs describing, because it changes what the question even is. Capture happens on an iOS device. The text is delivered to a computer either through a thumb sized hardware dongle or a scanned pairing code, and appears wherever the cursor is placed. No software is installed on the computer and no integration with the record system exists. From the record system's perspective, a user is typing.

Two consequences follow that a buyer will not find on a diagram.

The first is scope. Because delivery is to the cursor rather than to a chart, the tool works in any application. The vendor markets this explicitly, naming documents, email and general web use alongside the record system. That is real flexibility, and it also means clinical content can be dictated into destinations with no protection at all, at the user's discretion and outside any administrator's control.

The second is attribution. Text arriving as keystrokes carries no marker distinguishing it from typing, so the record contains no indication that any part of a note was machine generated. That is not a defect in itself, since the clinician is the author of what they send, but an organization that expects to identify AI assisted documentation in its own records will not be able to.

One control is specific: the hardware dongles are described as bound to a single user account and establishing an encrypted connection to that user's device.

Partly published. A seven day free trial with full feature access is offered, the company states there are no costs or surprise fees and that features other platforms charge extra for are included, and roughly $149 a month is cited for unlimited premium dictation.

That figure appears in the vendor's own blog rather than a rate card, and pricing for the AI scribe tier and enterprise options is described as layered on top without being stated, so the price of the ambient product itself is not shown.

Broad by user base rather than by enumeration, with documented use across orthopedic surgery, internal medicine, family practice, emergency department, inpatient and telemedicine, and a dictation heritage that covers operative notes as well as office visits. Customizable templates and phrase libraries carry per clinician. An iOS device is mandatory, and no language coverage beyond English is published.