GOVERNATLAS / PRODUCT DOSSIER

Augmedix

Augmedix describes ambient clinical documentation with different levels of automation and human support. Its public terms and BAA distinguish agreement versions and services defined by a statement of work.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate Augmedix for the specific documentation and clinician-review workflow you intend to use. Define who may handle the data and approve the result before considering efficiency claims.

What this record does not establish

Use the current BAA and the terms for the applicable statement of work; the site separately lists an older BAA for agreements before June 20, 2025. Do not mix versions or assume identical scope across AX services. The public statements remain vendor attributed; no executed customer agreement, clinical validation or independent security testing is established.

3 current sources · 3 published assertions
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Request a synthetic encounter in the specific AX service being quoted. Trace any human review, correction and EHR handoff, then identify the contracting entity and BAA version that applies to that statement of work.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. Retain the synthetic scenario, generated draft, corrections and clinical reviewer decision.
  2. Obtain the applicable agreement version, service and integration boundary before sharing PHI.
  3. Assign owners and dates for unresolved consent, retention, training-use and exit questions.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

Augmedix publishes a current business-associate addendum addressing HIPAA-governed PHI. Its separate index also lists an older agreement version, so a buyer must reconcile the BAA with the signed statement of work and selected service.

Source, dates & preserved provenanceAugmedix — Business associate agreement ↗

Authority: vendor owned
Observed 2026-11-02 · Reviewed 2026-11-02 · current until 2026-12-02

Artifact SHA-256: 7bfd72dd9889fdad99e2baa299e73f8f256ce11864fd10d71a86f51532324351

The hash identifies the preserved capture. The live source may have changed.

02
vendor asserted

Augmedix's posted current terms identify Augmedix Operating Corp. and address statements of work entered after June 20, 2025 unless more specific terms apply. These terms reference a BAA; they do not establish the contract version governing an individual buyer.

Source, dates & preserved provenanceAugmedix — Posted platform terms and HIPAA provisions ↗

Authority: vendor owned
Observed 2026-11-02 · Reviewed 2026-11-02 · current until 2026-12-02

Artifact SHA-256: 99328f8ff6bae4be9619586ffe79f091a75ee89adc3dc9dad19e2e0b1cbb597a

The hash identifies the preserved capture. The live source may have changed.

03
vendor asserted

Augmedix describes clinical documentation offerings combining different levels of AI automation and human support. A buyer must identify the particular service; no accuracy, time saving or clinical-outcome result is independently established here.

Source, dates & preserved provenanceAugmedix — Official product overview ↗

Authority: vendor owned
Observed 2026-11-02 · Reviewed 2026-11-02 · current until 2026-12-02

Artifact SHA-256: 86c68e305d4a3121526a9898aacbd6bf45a9e5da1267d094bb34b02afcd1a72b

The hash identifies the preserved capture. The live source may have changed.

Source register

Augmedix — Business associate agreement ↗vendor owned · captured 2026-11-02
Augmedix — Official product overview ↗vendor owned · captured 2026-11-02
Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Which service, plan, region and integrations does the proposed BAA cover?

02

What retention, deletion and model-training terms apply to our exact workflow?

03

Who validates outputs and owns the clinical or operational decision?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

COMPLIANCE / CLAIMS, SCOPE & GAPS

Start with the requirement.
Inspect the support.

Prepare your vendor review ↗

These labels describe this dossier’s current evidence coverage. A published mention may be a framework mapping, a qualified assertion or a limitation; it is not a compliance finding.

HIPAA

Published mention available

US healthcare privacy & security

Vendor documents BAA availability

Use the current BAA and the terms for the applicable statement of work; the site separately lists an older BAA for agreements before June 20, 2025. Do not mix versions or assume identical scope across AX services.

Read the source-attributed statement

Augmedix publishes a current business-associate addendum addressing HIPAA-governed PHI. Its separate index also lists an older agreement version, so a buyer must reconcile the BAA with the signed statement of work and selected service.

vendor asserted

Augmedix — Business associate agreement ↗

Explore HIPAA evidence ↗

For HIPAA-regulated use, request service-specific BAA eligibility, processing scope and responsibility details. Missing evidence here does not establish noncompliance. Payment cannot alter these evidence labels.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗