Book demo
Book demo
Digital intake and consent migration for therapy EMRs. Digital consent capture, intake form migration from prior EMR, and structured demographic import. SDOH fields captured at intake for value-based-care readiness.
VIDEO EMBED · REPLACE WITH <iframe>
MyTherapyWizard includes a native form builder for consent, intake, and insurance-collection forms, built, sent, submitted, and stored entirely within MyTherapyWizard's HIPAA-compliant infrastructure. No third-party form platform. No webhook endpoint. No Apps Script. No form content ever transmitted to AI.
Admin builds forms using a drag-and-drop form builder (the same dnd-kit component that powers evaluation and POC templates). Each form has a name, description, form type (Consent / Intake / Insurance Collection), audience (Parent / Guardian / Adult Patient), send permission level, and active/inactive status. Platform templates, read-only, MyTherapyWizard-provided, sit alongside org custom forms. 'Use as Starting Point' creates a fresh org copy pre-populated with the template content for editing.
Forms send in two modes: known-patient (patient token appended to form URL, completion auto-links to patient) or public / unlinked (no token, completion routes to an admin-resolvable unlinked inbox). Org branding, org name and optional logo, displays in every form header and every generated PDF. Forms never show Therapy Wizard branding to the recipient. Completed submissions generate a pdf document that stores to S3 at patients/{patient_id}/consents/{uuid}.pdf and attaches automatically to the patient's consent record.
Product screens, workflow diagrams, and example outputs. Replace each slot with a real screenshot or illustration.
The technical architecture, API integration points, and data model that make this feature work the way it does.
org_id, form_name, form_type, audience, form_schema (field definitions, labels, order, required flags), send_permission, org_branding_name, org_branding_logo_url, active boolean. Platform templates stored with org_id = null and source = platform_template, globally read-only.
Patient token generated as HMAC-SHA256(patient_id + org_id + send_timestamp). Single-use per send event. Embedded in the form URL for automatic patient linkage on submission.
Form submitted → PDF rendered via react-pdf → stored in S3 at patients/{patient_id}/consents/{uuid}.pdf → consent record created with document_url = S3 key → form_send_log status flips to Completed. Synchronous for known-patient submissions.
Public-link submissions with no patient token route to pending_submissions: submission_id, consent_form_id, org_id, submitted_at, field_values (JSON), pdf_s3_key, status (pending_review / matched / discarded). Admin matches to existing patient, creates new patient, or discards, PDF moves to the patient path on resolution.
Native builder replaces JotForm, Google Forms, DocuSign for consent and intake. One vendor, one login, one audit trail.
No external form vendor, no webhook endpoint, no third-party credentials to rotate. Form data stays within MyTherapyWizard AWS infrastructure end-to-end.
Sent-forms log per user, with pending / completed / expired status. Completions auto-create consent records and attach PDFs. No 'did they ever send it back?' anxiety.
Book a 30-minute walkthrough with our clinical team. We will show the exact workflow for your discipline and caseload.