Walk through the shared workspace.

Use fictional information and provisioned demo accounts. Complete this review on desktop and a phone-sized screen. Tick an item only after observing its expected result. Automated checks support this walkthrough; they do not replace your review.

These checkboxes and notes stay on this page until reload or navigation. Print or save this page as PDF to retain your review. Completing it does not approve clinical records or authorize production use.

ReviewerReview dateBuild or PR reviewedBrowser / device

Open shared workspace in another tab · Keep this checklist open while testing.

1. Sign-in, dashboard and facility scope

Sign in and confirm the account role and authorized facilities. Switch facility and verify that records belong to the selected facility. Open the six section filters; compare overview counts with saved records. Combine a saved-title search with a workflow queue, then clear the filters. Open a record, change a field without saving and switch filters: the unsaved text remains. Cancel a discard prompt when changing facility and confirm the draft remains. Use a viewer account and confirm that editing and creation are unavailable. Sign out and confirm the dashboard clears.

2. Readiness, audits and finding follow-up

Create an assessment with reviewer, date, scope and method. Add a dated finding, owner and due date, save, reload and verify its text. Add samples for two different questions, using 8/10 and 0/4. Confirm separate 80% and 0% rates rather than one combined rate. Create the finding’s clinical review. Verify the observation and source assessment link; the finding remains open and no second review is created for it. Try to document closure without evidence, then supply the required reviewer, date and evidence reference. Confirm that closure documentation does not grant assessment approval.

3. Clinical review, PIP and survey POC

Create a clinical review routed to PIP and create its linked draft. Confirm the four corrective-action steps start unfinished, with root-cause notes separate from Step 2. Enter the four steps, owner and next review date. Add an action and measurement sample; save and verify them after reload. Create a separate review routed to POC, then its linked draft. Complete multiple findings and verify that citation, narrative and corrective actions stay with the correct finding. Submit a plan, inspect its read-only state, approve using a clinical lead, then request changes before editing it again. A past-due date remains a documentation reminder, not proof of completion.

4. Staff education and QAPI

Create linked education from a concern or plan. Enter the teaching objectives, outline, knowledge check and competency plan. Save attendance/observation documentation and confirm it is not presented as verified attendance or competency. Create linked QAPI from a saved PIP, attach its saved evidence snapshot and inspect the captured PIP revision. The review remains unfinished until monitoring results and committee review are documented. Create a QAPI review directly and verify its optional PIP selection. Submit it, then use a QAPI chair to mark it reviewed; a clinical-lead role alone must not grant that decision.

5. Reports, conflicts and local migration

Open a saved connected report. Inspect its exact record links, saved revisions and evidence, export JSON, and print or save a PDF. Unsaved editor changes must be excluded. Use two signed-in tabs to edit the same record. Save the first, then save the stale second: confirm the conflict retains the second draft and requires explicit reconciliation before saving again. Download a local draft backup, preview selected migration, verify facility and scope, and explicitly commit. Local originals remain. Repeat the preview and verify existing shared counterparts are reused. Inspect migrated legacy closure labels, audit references and attendance: they remain context and do not become shared approval, verified rates or verified attendance.

6. Operator recovery drill

Use the offline commands in RELEASE_READINESS.md from the repository. Stop the server, back up the demo database, verify it and restore into a new file. Point the server at that recovered file and sign in again.

Compare saved records, links, revisions, audit events and migration receipts with the original. Confirm the original database and backup are unchanged. Confirm accounts remain usable, prior sessions do not carry into the recovered file, and a new edit saves with the next revision. Confirm database, backup and source-file URLs return 404; Home and the shared tools still load.

Findings and decision

Record the section, steps, expected result and observed result. Treat lost data, wrong facility, broken provenance, incorrect report content or unauthorized changes as a blocking issue.

Issues and follow-up Walkthrough outcome and reviewer notes

This review covers a local fictional-data demonstration. Production hosting, identity management, operational controls and facility-specific clinical or regulatory acceptance remain separate release decisions.