Beam Health

The AI arrived after the business did. Beam was a telehealth and virtual workstation platform covering video, scheduling, payments, patient registration and marketing, and the company describes its move into auto scribing as a pivot into uncharted territory rather than its founding purpose. Strip the AI modules out and a functioning telehealth business remains, which is the moat is not the model pattern applied in this category to Conveyor AI, Chartnote, iScribeHealth and Playback Health.

The marketing sells the absence of a review step rather than describing one. Charting is presented as completing in ONE CLICK, notes are pushed to the record, and the developer documentation states that the API can create SOAP notes, look up billing codes and POST THEM AUTOMATICALLY to the EHR. Automatic posting through an API is the furthest end of this category's autonomy range for documentation, and no confidence threshold, acceptance rate, review gate or accuracy figure was located for it. The AI Revenue module automating billing and coding compounds the question rather than answering it.

Graded up for answering the question this index now puts to every vendor in the lane: whose model is it. Beam publicly stated that its AI features were built on OpenAI models, which almost nobody else in this category discloses, and it publishes developer documentation describing the integration concretely, down to the number of endpoints required to autoscribe a consultation and post the note. Held at B because that disclosure dates from a 2023 announcement covering earlier features rather than a current statement about the shipping scribe, and because no accuracy figure, model card or evaluation methodology was located.

Named clinician testimonials including a dermatologist and a group practice principal, alongside vendor claims of two hours returned daily, hundreds of thousands in annual savings and users increasing revenue by 79 percent annually. None carries a denominator, cohort or method, and the revenue figure describes the whole platform including marketing and patient acquisition rather than the scribe. No study, controlled evaluation, accuracy benchmark or third party rating located.

One control here is engineered rather than promised and deserves credit. On the AdvancedMD integration the vendor states that PATIENT CONSENT IS REQUIRED AND NO DATA IS TRANSMITTED WITHOUT IT, which makes consent a gate on transmission rather than a policy statement, and it is one of very few consent mechanisms located anywhere in this wave. Asynchronous telehealth content is protected behind authenticated links and two factor authentication. Held at B because no retention schedule, de identification practice or training use statement was located.

HIPAA compliance is stated consistently across the platform and its video, payments and messaging components. Business associate agreement terms are not published for inspection.

Not assessed, and one attribution needs stating so it is not misread. Beam's AdvancedMD partner page notes that ADVANCEDMD is HIPAA compliant and SOC 2 Type 2; that certification belongs to the integration partner, not to Beam. No named or dated attestation for Beam itself, and no trust centre, was located.

Not a regulated medical device and none claimed or required for ambient documentation.

One language access capability, no governance disclosure. Beam ships a translation feature intended to let patients and providers communicate across language barriers, which extends access beyond the note itself, and that is worth crediting. Against it, no fairness statement, subgroup analysis or accent and dialect performance disclosure was located, and the AI Revenue module automates billing and coding without any published accuracy or oversight description. The 79 percent revenue claim is platform wide rather than coding specific, so this sits below the coding gradient's aggressive end rather than on it.

Named, varied and architecturally described, which is more than most. AdvancedMD connects through a one click toggle inside the Beam platform with consent gated data flow and automatic synchronisation. Healthie connects through a Chrome extension sending the generated note to the patient chart in one click. Beyond fixed integrations, an API and SDK let other platforms embed the scribe directly, and the company has written publicly about building an auto scribe against a DOM based EHR integration, which is browser level interaction rather than a sanctioned data channel and carries the same brittleness this index notes for robotic process automation. Held at B because integration depth per system was not verified and no certification programme membership was located.

Not assessed. Cloud delivered with browser extension and API access, but no hosting region, residency option or sub processor detail was located, which matters more than usual given a disclosed dependency on a third party model provider.

No published rate card, tier structure or pricing model located. Access runs through a demo and a signed contract, and partner documentation refers to fees due to Beam without stating them. Because five modules are sold both together and separately, a buyer cannot determine what the scribe alone would cost.

Telehealth native rather than specialty defined, covering live video consultation and asynchronous store and forward encounters where a patient submits an intake form and the clinician replies with a recorded video, which is a documented encounter type almost nothing else in this category addresses. Dermatology appears through a named user. Translation extends reach to non English speaking patients. Held at C because no specialty count, specialty tuning claim, note format list or supported language list was located.