Written and maintained by CASRAI Editorial Board
Published · Last updated
On this page
Commure and Augmedix operate as a unified enterprise healthcare technology and ambient clinical intelligence organization following Commure’s acquisition of Augmedix in October 2024. Announced on July 19, 2024, and completed on October 2, 2024, as an all-cash transaction at $2.35 per share (valuing Augmedix at approximately $139 million), the merger combined Augmedix’s pioneering ambient medical documentation suite and corpus of more than 10 million clinical encounters with Commure’s enterprise healthcare operating system (Commure OS), patient engagement tools (Commure Engage), revenue cycle management (RCM) platform (built on Commure’s 2023 merger with Athelas), and native Commure AI Scribe.
For health system CIOs, CMIOs, and clinical informatics teams evaluating ambient documentation vendors alongside Abridge competitors, understanding how legacy Augmedix products (Augmedix Prep, Augmedix Go, Augmedix Assist, and Augmedix Live) compare and converge with the broader Commure platform is essential for contracting, EHR integration, and clinical workflow design.
What Is the Difference Between Augmedix and Commure?
Prior to their October 2024 combination, Augmedix and Commure evolved from complementary layers of the hospital technology stack:
- Augmedix (Founded 2012): Originated as a real-time remote medical documentation company using smart glasses and smartphones, and progressively built an ambient AI platform powered by proprietary medical speech recognition and fine-tuned clinical large language models (LLMs). Its primary differentiation is its four-tier service spectrum that lets health systems match pure self-service generative AI or human-in-the-loop (HITL) Medical Documentation Specialist (MDS) support to clinician preference and specialty acuity.
- Commure (Founded 2017, Merged with Athelas in 2023): Built an enterprise cloud platform (
Commure OS) centered on HL7 FHIR interoperability, clinician workflow orchestration, autonomous medical coding and revenue cycle management (RCM), remote patient monitoring (RPM), and a self-service generative ambient scribe (Commure Ambient AI).
Head-to-Head Product & Architecture Comparison
| Dimension | Augmedix Product Suite (Now Part of Commure) | Commure Enterprise Platform (Commure Ambient / OS / RCM) |
|---|---|---|
| Core Focus | Multi-tiered ambient clinical documentation and pre-visit chart preparation across outpatient, ED, and inpatient care | End-to-end hospital operating system: self-service ambient AI scribe, patient engagement, autonomous coding, and RCM |
| Documentation Tiers |
|
|
| Human-in-the-Loop (HITL) Options | Optional asynchronous (Assist) or synchronous real-time (Live) human quality review |
Primarily autonomous generative AI with clinician review at sign-off (augmented by RCM coding specialists for billing services) |
| Revenue Cycle & Coding Integration | Captures structured E/M elements and ICD-10-CM diagnoses within the clinical note | Directly links ambient clinical notes to Commure/Athelas autonomous coding, claim scrubbing, denial management, and prior authorization |
| Hardware Footprint | iOS/Android mobile app, workstation web interface, or optional hands-free smart glasses (for Augmedix Live) |
iOS/Android mobile app, browser web app, and embedded EHR SMART on FHIR frame |
How Do Augmedix and Commure Integrate with EHR Systems?
A primary driver of the Commure–Augmedix merger was uniting Augmedix’s deep hospital deployment footprint (across health systems using Epic, Oracle Health/Cerner, MEDITECH Expanse, and athenahealth) with Commure’s FHIR integration engine (`Commure OS`). Across the combined platform, EHR integration operates through four standardized mechanisms:
- HL7 FHIR R4 and SMART on FHIR Launch: Using ONC (ASTP) 45 CFR § 170.315(g)(10) standardized APIs, the scribe launches directly within Epic Hyperspace/Haiku/Canto, Oracle Health PowerChart, or MEDITECH Expanse via OAuth 2.0 / OpenID Connect context tokens. It reads
Patient,Encounter,Condition,MedicationRequest, andObservationresources to power pre-visit summaries (such asAugmedix Prep) and writes completed notes back viaDocumentReferenceresources. - Bidirectional Section-Level Note Population: In Epic, note sections map directly to SmartData Elements (SDEs) and NoteWriter templates so generated HPI, ROS, Physical Exam, and Assessment and Plan text lands in its designated structural block without overwriting active medication or vitals macros. In Oracle Health Millennium, notes populate Dynamic Documentation (
DynDoc) and PowerNote fields via FHIR R4 or HL7 v2 MDM^T02/T08 interfaces. - HL7 v2 ADT and SIU Schedule Synchronization: For ambulatory clinics and emergency departments using mobile capture, HL7 v2 SIU (`S12`–`S26`) scheduling feeds and ADT (`A01`–`A08`) registration events automatically populate the clinician’s daily worklist on the mobile application.
- Meditech Expanse Collaboration: Augmedix established an early partnership with MEDITECH to integrate ambient documentation directly into MEDITECH Expanse web and mobile clinical workflows, which continues under the unified Commure Ambient portfolio.
Is Augmedix or Commure HIPAA Compliant for Clinical Workflows?
Yes. Both the Commure enterprise platform and all Augmedix product tiers operate as HIPAA-compliant AI scribe solutions built for regulated U.S. health systems (including Epic and Cerner AI scribe deployments):
- Business Associate Agreement (BAA): Commure executes formal HIPAA Business Associate Agreements (45 CFR §§ 164.502(e), 164.504(e)) covering all autonomous AI (
Commure Ambient,Augmedix Go) and specialist-assisted (Augmedix Assist,Augmedix Live) workflows. - Encryption and SOC 2 Type II Controls: All clinical audio streams, transcripts, and structured FHIR payloads are encrypted in transit using TLS 1.2/1.3 and at rest using AES-256 encryption within SOC 2 Type II-audited cloud environments.
- Audio Retention and Model Training Governance: Health systems can configure ephemeral audio processing policies in which raw encounter audio is deleted upon note finalization, and contractual data governance terms prevent protected health information (PHI) from being exposed to public third-party foundation models.
- Clinician Final Attestation: Regardless of whether a draft is generated purely by generative AI (
Augmedix Go/Commure Ambient) or reviewed by a trained Medical Documentation Specialist (Augmedix Assist/Live), the note enters the EHR in an unsigned preliminary state. The treating clinician must review, edit, and electronically sign the note before it becomes part of the legal medical record.
Frequently Asked Questions
What is the difference between Augmedix and Commure?
Augmedix pioneered a four-tiered ambient clinical documentation suite—Augmedix Prep (pre-visit chart summaries), Augmedix Go (self-service generative AI scribe), Augmedix Assist (AI plus asynchronous human review), and Augmedix Live (real-time synchronous documentation support)—while Commure built an enterprise healthcare operating system (Commure OS), autonomous coding/RCM suite (via Athelas), and self-service Commure Ambient AI. On October 2, 2024, Commure completed its $139 million acquisition of Augmedix, uniting both product lines under Commure.
How do Augmedix and Commure integrate with EHR systems?
Commure and Augmedix integrate with Epic, Oracle Health (Cerner), MEDITECH Expanse, and athenahealth using SMART on FHIR (OAuth 2.0) launch contexts, HL7 FHIR R4 clinical read APIs and DocumentReference write-backs, Epic SmartData Elements (SDEs), and HL7 v2 SIU/ADT/MDM interfaces for schedule synchronization and section-level note population.
Is Augmedix or Commure HIPAA compliant for clinical workflows?
Yes. Commure (including the integrated Augmedix product line) is fully HIPAA compliant, executing Business Associate Agreements (BAAs) with covered entities, enforcing TLS 1.2+ in-transit and AES-256 at-rest encryption under SOC 2 Type II security controls, supporting configurable zero-retention audio policies, and requiring clinician review and electronic signature before any note is finalized in the EHR.
