Fictional demo practice and SaaS boundary

The public practice is a fictional sample group, not a live customer practice. Five invented staff personas cover administration/scheduling/billing, clinical administration, psychotherapy, supervision and social work. All staff and contacts use reserved example.com mail and 202-555-01xx telephone numbers. The protected owner account stays real but never appears as sample staff.

Fifteen fictional patient records have shared clinician assignments, linked contacts, past/upcoming appointment examples, documents and seeded billing rows. Patient IDs link the practice directory, staff patient lists, contact links, patient charts, calendar, claims and billing transactions. A shared browser-session registry preserves calendar, contact, document, message and remittance edits across client navigation. Admission and demographics use the existing in-memory patient collection. Reload returns disposable records to their original state.

/demo shows the connected roster and counts, with reset/removal controls also available in Master T1. Reset restores patients and clears all shared session edits, then reloads the page to reset component-local settings, cards, portal toggles and to-dos. Removal discards edits and turns off sample practice pages in this browser only, retaining a restoration page. The removal flag is separate from account storage. Neither action modifies real administrator accounts or server data.

Billing examples cover paid, submitted, rejected and self-pay records. Claim history, sample transaction tables and sample revenue read the same ledger. Posting a sample ERA updates linked rows in that ledger idempotently; it does not contact a payer or move money. Seeded signed-note rows are examples, not certification of clinical signing. Remaining nonfunctional workflow controls must continue to be reported honestly by FQL.

Production boundary

Verification

67 unit/navigation tests passed, including fictional staff contact rules, all seeded patient relationships, reset/account-storage isolation, demo disable/restore, idempotent sample remittance and patient schedule synchronization. Browser checks verified demographic edit then reset, contact creation/navigation/reset, calendar-to-chart appointment readback, ERA-to-ledger status readback and demo removal across reload followed by restoration. Five viewport samples (390, 768, 877, 1024 and 1920px) had no document overflow. Protected T1 FQL regression passed implemented selected checks and retained HOLD for the unfinished full clinical journey; no browser runtime errors were observed.

Production boundary details

Real customer practices are not implemented yet. This demo is not a production tenant switcher and client-only removal is not a security boundary or a global disable. Before accepting real data, build authenticated tenant membership and server-enforced row isolation, keep demo tenants separately identified, and remove or explicitly enable demo routes via deployment configuration. Never migrate these fixtures into real patient records, mix sample data with real account entities, or infer permissions from sample staff roles.

Clinical records update

The shared registry now includes 30 fictional notes and 30 questionnaire requests, linked to all 15 patients. Revisions and clinician review states are shared by patient/staff/workspace pages. Three questionnaire types have working patient submissions and clinician processing. Reset clears all clinical edits without touching administrator storage. Sample accounting entry pages allocate to shared ledger rows; no money moves. Full suite passed 97 tests; browser checks covered clinical and accounting readback, all 21 billing action destinations, library navigation, and ten clinical/core routes at 390/768/1024/1920px with no page errors or document overflow.