Organization and role boundaries
Separate practices and apply defined responsibilities for clinicians, owners, scheduling, billing, privacy, security, and audit work.
ASL Therapy brings scheduling, client coordination, structured notes, assessments, secure communication, invoicing, portal documents, and reviewed court/SOMB reporting into a multi-organization platform.
A practice needs more than a calendar. Client work spans notes, assessments, billing, documents, supervision, privacy requests, court reporting, and support access. When those functions are split across tools, the practice loses the evidence needed to show who did what and whether a control was actually completed.
Separate practices and apply defined responsibilities for clinicians, owners, scheduling, billing, privacy, security, and audit work.
Create DAP, SOAP, and progress-note drafts with signing and amendment states rather than silent edits to finalized records.
Coordinate appointments and prepare approved ASL Meet links for small-group or one-to-one sessions.
Store structured assessment results without automated diagnosis and require human review for court or SOMB reports.
Prepare invoices, superbill-ready records, portal documents, homework, and reports under explicit sharing controls.
Track policies, workforce actions, risk items, incidents, disclosures, support grants, and activation prerequisites.
Configure roles, rates, workflows, documentation, and client visibility using fictional data.
Perform risk analysis, policies, training, vendor agreements, recovery testing, identity acceptance, retention, and incident exercises.
Only after qualified review and acceptance should the operator deliberately enable a practice for live PHI.
ASL Therapy includes organization-scoped access, protected fields, audit evidence, practice-controlled support grants, signed-note amendments, and fail-closed activation. The August 4 host review observed 38 encrypted Therapy columns with blind indexes and a populated, intact hash-chained audit trail. That server evidence is not a HIPAA certification: software alone cannot establish compliance, and every customer must complete its own legal, workforce, vendor, risk, recovery, and operating responsibilities.
No blanket claim is made. The current service is a synthetic-data pilot with live PHI disabled.
The product is designed around organization membership and client-visibility boundaries. Cross-practice access is not part of ordinary use.
Stripe and QuickBooks workflows exist in sandbox and require production credentials, configuration, reconciliation, and acceptance.
The portal model supports explicitly published documents; draft clinical material is not automatically client-visible.
No. Assessments do not diagnose automatically, and court/SOMB reports require human review.
Capabilities reflect the documented Auto Secure Login platform as of August 4, 2026. Availability and onboarding requirements vary by product and organization.
We will map your current workflow, identify the smallest responsible pilot, and document the controls and acceptance criteria before expansion.