Changelog
Highlights of the current multi-clinic SaaS, AI productization, and generated docs upgrade.
June 28 2026Multi-clinicAIDocs
Details
Current Revision
This docs build reflects the shift from a single-clinic app into a central-platform plus clinic-tenant product surface.
- Central platform models, memberships, switcher, and health page.
- Tenant-aware scheduler and AI job fan-out.
- Dashboard hardening and clinic-local readiness cards.
- Coherent AI Run Log, settings, and draft actions.
- Generated HR1-style docs with search, coverage, demo flow, and developer notes.
Upgrade Notes
Release Impact
| Area | What To Verify |
|---|---|
| Multi-clinic tenancy | Membership switching, clinic-local records, health status, and no cross-tenant access. |
| Appointments and consultations | Doctor schedule eligibility, queue ownership, check-in, EMR drafts, and finalization. |
| AI workflows | Provider settings, queued runs, stale-state protection, human review, and audit history. |
| Operations | Scheduler, workers, storage, communications, pharmacy reminders, and readiness cards. |
Checklist
Before And After Upgrade
- Back up the central database, every clinic database, storage, and environment configuration.
- Read migration and queue-impact notes; place the app in the documented maintenance state.
- Run migrations and cache rebuilds, then restart workers with the deployed code.
- Smoke-test platform health, tenant switching, patient search, appointment booking, consultation, billing, pharmacy, and one notification.
- Record the deployed revision and rollback point in the operations log.