New features, improvements and fixes in each TherapyCRM release.
v1.0.15 ·
secure AI agent access
TherapyCRM 1.0.15 adds a comprehensive Model Context Protocol interface so authorized AI agents can discover and use staff workflows through the same validated, tenant-scoped, role-protected APIs as the web application.
New features
Authorized AI agents can connect to TherapyCRM through a standards-based Streamable HTTP MCP endpoint with OAuth 2.1 authorization-code and refresh-token flows
The MCP catalog covers staff-facing application capabilities and includes generic API access for documented exceptional lanes
Agents can search the catalog in natural language and retrieve machine-readable operation contracts with required and optional fields, validation rules, roles, prerequisites, side effects, examples, and error guidance
A local stdio transport remains available for trusted automation and development workflows
Improvements
OAuth discovery, dynamic client registration, PKCE S256, exact resource binding, consent, token rotation, revocation, and MCP session handling are documented and testable end to end
MCP requests reuse the existing HTTP authorization middleware, preserving practice isolation, role permissions, branch access, and therapist row-level client scoping
The registry now includes password reset, profile, workflow close, document download, attendance, emergency contact, staff rotation group, and invoice download operations used by the web application
Strict pagination and query contracts now describe the parameters the underlying routes actually accept
Bug fixes
Fixed MCP registry gaps discovered by systematically comparing frontend API calls with registered agent operations
Fixed operation search so natural-language queries match relevant catalog terms regardless of word order
Fixed progress-note and related strict-query documentation that could otherwise cause valid agent calls to be rejected
v1.0.14 ·
guided practice activation
TherapyCRM 1.0.14 adds a Getting Started guide to the dashboard that walks new practice owners through the first actions that make the platform productive: building their team, adding their first client, and scheduling their first appointment.
New features
Practice owners and administrators see a Getting Started checklist on the dashboard with live progress across branch setup, therapy types, team invitations, the first client, and the first appointment
Each pending step links directly to the page where it is completed, and finished steps are marked done automatically from real practice data
Improvements
Steps already completed by new-practice defaults are credited immediately so new owners start with visible progress
The guide disappears automatically once every step is complete and can be dismissed at any time
Dismissing the guide is remembered per signed-in user, so one person hiding it on a shared computer does not hide it for colleagues
v1.0.13 ·
connected clinical plans and scheduling
TherapyCRM 1.0.13 introduces a comprehensive treatment-plan workflow that reuses practice clinical libraries, preserves the signed clinical record, and carries operational requirements into scheduling and session delivery.
New features
Clinicians can build discipline-specific treatment plans with reusable goals, interventions, equipment, assessments, home practice, workflows, and plan templates configured by their practice
Measurable goals support observable outcomes, conditions, baselines, mastery criteria, data collection, supports, and generalization details
Signed clinical plans produce frozen, downloadable documents containing the selected goals, interventions, recommendations, and equipment
Treatment schedules are managed separately from the immutable clinical plan and connect authorized dosage, therapist assignment, equipment, rotations, appointments, and session delivery
New practices receive published goals, interventions, equipment, assessments, workflows, and home practice covering all 14 therapy types, with matching presets recommended first inside treatment plans
Improvements
Treatment-plan creation now guides users from plan setup through formulation, goals, recommendations, review, and signing with therapy-type-aware templates
Practice libraries can be reused directly while still allowing client-specific goals and interventions
Scheduling readiness offers clearer, actionable fixes and updates schedule-owned therapist details without changing a signed clinical plan
Schedule runs, appointment provenance, fulfillment, equipment requirements, and session delivery now share one treatment-schedule source of truth
New practices receive discipline-specific plan-template mappings automatically
Paid onboarding now waits for a verified, idempotent starter setup covering therapy types, branches, rooms, clinical forms, plan mappings, billing services, quick phrases, lead workflows, and every clinical preset library
Bug fixes
Fixed signed-plan snapshots becoming stale or being overwritten during document workflows
Fixed rich-text template fields rendering incorrectly in the document editor and generated clinical PDFs
Fixed ambiguous locked-plan errors that exposed API instructions instead of telling users how to return a pre-signature plan to draft or amend a signed plan
Fixed scheduling links, dosage drift handling, authorization checks, rotation linkage, and appointment references after separating clinical plans from operational schedules
Fixed therapy-type template mapping edge cases, including ABA remapping false matches and missing mappings for newly provisioned practices
Fixed a Stripe webhook and browser-confirmation race that could report checkout success before starter-data provisioning had finished
Breaking changes
Signed clinical and dosage content is intentionally immutable; post-signature clinical revisions create an amendment while operational schedule assignments remain editable through scheduling
Legacy service-delivery-plan storage is replaced by the treatment-schedule model, with migrations preserving existing operational data
v1.0.12 ·
practice-branded customer emails
TherapyCRM 1.0.12 makes practice-authored customer communications feel consistent with each therapy centre while preserving TherapyCRM identity for platform-owned security, account, billing, and operational messages.
New features
Practice-authored transactional emails now use the sending practice name in the friendly From label when practice context is available
Improvements
Appointment, intake, client, staff, portal, document, clinical, billing, and practice communication paths resolve sender branding through one consistent practice-aware email contract
Practice-name normalization provides a safe TherapyCRM fallback when a practice name is missing or unusable
Bug fixes
Fixed customer-facing emails that always appeared from TherapyCRM even when the message was authored and sent on behalf of a specific practice
Fixed inconsistent sender-name handling across direct email services, template dispatch, notifications, scheduled communications, and queued delivery
Breaking changes
No public API field was removed and no recipient, Reply-To, delivery, or authorization behavior changed
v1.0.11 ·
smarter day-to-day practice operations
TherapyCRM 1.0.11 strengthens the complete therapy-centre workflow from lead intake and consultation through client onboarding, clinical care, scheduling, parent communication, staff coverage, billing visibility, and owner decision support. Agent Chat now handles more operational questions and approval-gated actions with clearer names, safer evidence boundaries, and visuals only when they materially improve understanding.
Added deterministic one-time appointment creation and rescheduling support with slot, resource, treatment-plan, and working-hours checks before approval
Added practice-owner operational briefings, staff-utilization reporting, saved-schedule risk analysis, and hypothetical sick-call or half-day impact analysis with coverage options
Added clearer clinical-session readiness, document review, authorization-risk, portal vacation, unread-message, and follow-up views using client and staff names instead of internal ids
Improvements
Agent Chat now defaults to concise text for counts, yes-or-no questions, clinical queues, portal messages, and lead follow-up; dashboards and charts are opt-in for genuinely useful multi-metric comparisons
Consultation scheduling, lead-to-client conversion, assessment review, appointment plan defaults, document signatures, and staff schedule setup now use safer context-aware defaults
Parent vacation and schedule requests now expose their affected appointments and route staff to the exact review workflow
Scheduling, My Day, portal, treatment-plan, document, staff, billing, notification, and clinical-session workflows provide clearer links, labels, empty states, and error recovery
Bug fixes
Fixed lead creation and appointment creation failures in Agent Chat, including guardian-versus-client identity handling and human-friendly record resolution
Fixed report date boundaries, staff-utilization calculations, cancellation and no-show summaries, and cancelled-visit workload inflation
Fixed Canadian province normalization, date-of-birth persistence, consultation defaults, guardian relationship mapping, and lead conversion handoffs
Fixed clinical document, assessment, signature, session-data, notification, parent-portal, staff leave, and last-minute scheduling edge cases found during realistic multi-role browser testing
Breaking changes
No public API field was removed; Agent Chat tool inputs are stricter and may reject ambiguous or unscoped internal requests that previously produced misleading answers
v1.0.10 ·
faster delivery with clear deployment identity
TherapyCRM 1.0.10 is a deliberately small release used to measure the complete guarded delivery path. It adds an explicit service identity to the public deployment information endpoint and hardens deployment verification so configuration failures are reported immediately.
New features
The public app information endpoint now returns a stable TherapyCRM service identity for monitoring and deployment verification
Improvements
Kubernetes deployment verification now checks read access before entering the rollout wait loop
The release follows the standard feature-to-develop-to-main-to-production promotion path using one immutable image
Bug fixes
Missing production verifier permissions now produce an immediate actionable error instead of a misleading 15-minute GitOps timeout
Breaking changes
The additional public app information field is backward compatible; no existing response field or product workflow is changed