Synthetic-data pilot boundary

Psychiatric documentation should remain under clinician control.

myPsychAssist structures supplied information and prepares drafts. It is designed to make support, uncertainty, correction, and clinician confirmation visible—not to turn generated language into an autonomous clinical decision.

Current pilot boundarySynthetic information onlyNo real PHIInvited pilot usersDrafts onlyClinician review required
What happens to a statement?

From supplied information
to a clinician decision.

The review path is deliberately visible. Each stage can expose missing support, conflicting information, or language that should remain uncertain.

  1. 01
    Source fragment

    A synthetic encounter detail enters the review path.

  2. 02
    Structured finding

    Meaning and timing remain attached to their source.

  3. 03
    Draft statement

    Draft language is created without becoming a final record.

  4. 04
    Clinician decision

    Confirm, correct, or reject before use.

  1. 1Source information appears
  2. 2Evidence is structured
  3. 3Draft language is generated
  4. 4Support is displayed
  5. 5Clinician confirms, edits, or rejects
  6. 6Final use remains the clinician's decision
Clinician control means

Review is an action,
not a label.

  • 01
    Edit any generated text

    Correct wording, timing, context, and omissions before use.

  • 02
    Reject unsupported statements

    A fluent sentence is not evidence that a fact was established.

  • 03
    Inspect source support

    Review the supplied material linked to important draft statements.

  • 04
    Preserve uncertainty

    Missing, conflicting, or stale information should remain visible.

The system can assist with

  • Structuring supplied information
  • Drafting supported language
  • Highlighting missing support
  • Surfacing contradictions
  • Reusing reviewed facts in drafts

The system does not decide

  • Diagnosis or treatment selection
  • Prescribing
  • Billing-code eligibility
  • Medical necessity
  • Payer compliance or final approval
Evidence, in plain language

Support can be visible
without pretending it is certainty.

Source-linked support

Important draft language can be reviewed beside the supplied fragment that supports it.

Quote and paraphrase

Exact patient-attributed wording is different from a paraphrase. Both still require context and review.

Missing support

If the supplied material does not establish a claim, the draft should not silently convert absence into certainty.

Conflicting information

Different doses, dates, or symptom states should be surfaced for reconciliation rather than collapsed.

Stale evidence

A source change can make an earlier draft statement stale. Review must follow the current source.

Clinician confirmation

Confirmation means the clinician reviewed and corrected the draft; it is not automated approval.

Privacy disclosure

First-party analytics and security logging stay narrowly scoped.

The public site records first-party analytics to understand page views, pilot interest, calculator use, and safe security signals. No third-party advertising pixels are used, analytics data is not sold, and the disclosure does not claim full anonymity.

Pseudonymous analytics

Session and visitor groupings use server-generated identifiers and rotating HMACs. Exact IP addresses are not shown in the normal dashboard.

Campaign attribution

Valid campaign codes can be linked to an active session for the pilot and public pages. Arbitrary or unsafe query text is ignored.

Security logging

Blocked requests, throttling, scanners, and server failures may be recorded for reliability review. Sensitive headers, bodies, and clinical content are excluded.

Retention and contact

Analytics and security data follow configured retention windows. Privacy questions or opt-out requests can be sent to support@mypsychassist.com.

Privacy disclosure

First-party analytics and security logging stay narrowly scoped.

The public site records first-party analytics to understand page views, pilot interest, calculator use, and safe security signals. No third-party advertising pixels are used, analytics data is not sold, and the disclosure does not claim full anonymity.

Pseudonymous analytics

Session and visitor groupings use server-generated identifiers and rotating HMACs. Exact IP addresses are not shown in the normal dashboard.

Campaign attribution

Valid campaign codes can be linked to an active session for the pilot and public pages. Arbitrary or unsafe query text is ignored.

Security logging

Blocked requests, throttling, scanners, and server failures may be recorded for reliability review. Sensitive headers, bodies, and clinical content are excluded.

Retention and contact

Analytics and security data follow configured retention windows. Privacy questions or opt-out requests can be sent to support@mypsychassist.com.

Known limitations

Drafting can still be wrong.

AI-assisted drafting may omit context, overgeneralize source material, misinterpret temporal relationships, flatten uncertainty, or produce language that requires correction.

The review workflow is designed to expose these risks. It cannot guarantee that every omission, contradiction, unsupported statement, or source problem will be detected.

myPsychAssist does not replace professional judgment, the legal health record, payer rules, or the clinician's responsibility for final use.

The Trust Ledger

What is true right now.

A public boundary for the current synthetic-data pilot.

Current pilot

Invited participants using synthetic information only.

Every output

A draft that requires clinician review and correction.

Evidence view

Support and uncertainty remain visible during review.

Final decision

Belongs to the clinician—not the drafting system.

Test the review path

Help us find where
the workflow needs work.

Founding clinicians use synthetic encounters and give direct feedback on drafting, evidence review, and correction.

Apply for the Founding Clinician Pilot →