GOVERNATLAS / PRODUCT DOSSIER

Doxy.me

Doxy.me describes a telehealth platform. Its current Free/Premium help documentation discusses HIPAA safeguards, BAAs and subcontractor agreements; buyers should reconcile those statements with their account and selected apps.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate Doxy.me for the specific care-delivery and practice-operations 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

Current Free/Premium help documentation says Doxy.me will sign a BAA. Confirm the account-specific agreement and separate app features; older Clinic-plan guidance should not be generalized to every current service. The public statements remain vendor attributed; no executed customer agreement, clinical validation or independent security testing is established.

2 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

Run a synthetic telehealth appointment, a patient invitation and a clinician role change. Inspect waiting-room access and the account's BAA process, and obtain separate data-lifecycle answers for any recording, scribe or other optional app.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. Retain the fictional workflow, role-access checks and export or offboarding result.
  2. Reconcile the service, communication channels, integrations and agreement applying to each data flow.
  3. Record the owner and follow-up date for retention, incident handling and patient-communication gaps.

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

Doxy.me's help documentation says it has BAAs with subcontractors and vendors interacting with its services. The statement remains vendor asserted and does not independently verify a complete recipient inventory or coverage of a customer's integrations.

Source, dates & preserved provenanceDoxy.me — Official product overview ↗

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

Artifact SHA-256: 7396db53febdeda58aca9064aa9137d3759a07d3d54ab71b29b4273d8c9b8b85

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

02
vendor asserted

Doxy.me's Free/Premium help documentation states that it will sign a BAA acknowledging its HIPAA business-associate role. This documents vendor availability; the buyer must confirm the agreement applying to the account and selected services.

Source, dates & preserved provenanceDoxy.me — Official product overview ↗

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

Artifact SHA-256: 7396db53febdeda58aca9064aa9137d3759a07d3d54ab71b29b4273d8c9b8b85

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

03
vendor asserted

Doxy.me describes a telehealth platform with optional apps and features. Core telehealth documentation does not establish that every app has identical data handling, retention or contract scope.

Source, dates & preserved provenanceDoxy.me — Official product overview ↗

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

Artifact SHA-256: 2ac50a26b54fec9f91174b75b9853d0f69c4533b06a141a7b9e14f5d62401b95

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

Source register

Doxy.me — Official product overview ↗vendor owned · captured 2026-11-02
Doxy.me — 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

Current Free/Premium help documentation says Doxy.me will sign a BAA. Confirm the account-specific agreement and separate app features; older Clinic-plan guidance should not be generalized to every current service.

Read the source-attributed statement

Doxy.me's Free/Premium help documentation states that it will sign a BAA acknowledging its HIPAA business-associate role. This documents vendor availability; the buyer must confirm the agreement applying to the account and selected services.

vendor asserted

Doxy.me — Official product overview ↗

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 ↗