GovernAtlasSubmit your product ↗
Discover platforms/Blueprint

GOVERNATLAS / PRODUCT DOSSIER

Blueprint

Blueprint describes AI documentation and practice workflows for therapists, alongside an existing EHR or within its own EHR. Its security documentation explains BAA availability and clinician approval of records.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate Blueprint 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

The security page says a BAA is included at signup and a signable copy is available. It describes optional recording and clinician review; confirm the agreement and settings for the selected workflow. 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

Use a fictional encounter to compare a recording-based draft with a manually prepared note. Follow edits and clinician sign-off, then identify which data and permissions differ when used alongside an existing EHR versus in the full platform.

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

Blueprint describes optional recording and clinician review and sign-off before content becomes part of the client record. These workflow descriptions do not establish clinical correctness or demonstrate that a customer's review process is effective.

Source, dates & preserved provenanceBlueprint — Privacy and data handling ↗

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

Artifact SHA-256: 8cc11b6f6c22a2e347572d91cf8a7ef2913aaa93481374e93bfcde30ac48135b

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

02
vendor asserted

Blueprint's security page says a HIPAA BAA is included at signup and a signable copy is available for records. This is documentation of a vendor process, not proof of an executed agreement for a buyer.

Source, dates & preserved provenanceBlueprint — Privacy and data handling ↗

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

Artifact SHA-256: 8cc11b6f6c22a2e347572d91cf8a7ef2913aaa93481374e93bfcde30ac48135b

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

03
vendor asserted

Blueprint describes AI documentation workflows that can be used alongside an existing EHR or within its own EHR offering. Scope and entitlements must be confirmed for the service selected by the buyer.

Source, dates & preserved provenanceBlueprint — Official product overview ↗

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

Artifact SHA-256: a28e9352a41d1cee6d91602aa146f65db72349e364968798bafa781fce535045

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

Source register

Blueprint — Official product overview ↗vendor owned · captured 2026-11-02
Blueprint — Privacy and data handling ↗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

The security page says a BAA is included at signup and a signable copy is available. It describes optional recording and clinician review; confirm the agreement and settings for the selected workflow.

Read the source-attributed statement

Blueprint's security page says a HIPAA BAA is included at signup and a signable copy is available for records. This is documentation of a vendor process, not proof of an executed agreement for a buyer.

vendor asserted

Blueprint — Privacy and data handling ↗

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 ↗