DEMO_EXP — Motivation: "Synchronized Ritual" Concept

Status: Draft — Concept Note for Demo Session Date: June 25, 2026 Engineer: Đạt Trần Tiến (Daves Tran) Context: VKIST-PILOT MSK Pilot Workspace (Sprint 1-6, June 2 - September 2, 2026)

1. The UX Concept: What Is a "Synchronized Ritual"?

In UX and digital design, a Synchronized Ritual is the intentional creation of shared digital experiences or synchronous interactions that connect users across time and space. It takes a basic, habitual app action and elevates it into an emotionally resonant, collective, or deeply personalized experience.

A ritual is not just a repeated action. A synchronized ritual is one where:

Multiple users feel connected to the same event at the same moment, even if they are physically apart
Past, present, and future are visible in a single view — the user feels the arc of what they are part of
A basic action (open a list, tap a button) carries emotional weight beyond its functional outcome

2. Why This Concept Matters for VKIST Specifically

PILOT's user research reveals three structural loneliness problems that Synchronized Ritual directly addresses:

Problem 1: The Isolated Radiologist

Radiologists work in dark, quiet reading rooms, detached from direct patient contact and from the downstream clinicians who consume their reports. Their work is invisible until a Surgeon or PT reads it — sometimes hours or days later.

"They are the vital gatekeepers of clinical safety. Engagement and UX research should be focused entirely on invisible workflow optimization." — User Research Result, UP5 profile

Synchronized Ritual response: Create moments where the radiologist's action immediately ripples outward. When they sign a report, they see — in real time — that the Surgeon's dashboard has pulsed, the PT's session has updated, and the patient has been notified. The radiologist feels their work is part of a collective machine.

Problem 2: The Anxious, Information-Starved Patient

Patients and their caregivers are anxious and overwhelmed, often turning to dangerous folk remedies (leaf-wrapping, aggressive manual adjustment) because no one has translated their scan into understandable terms. The hospital consultation is brief; the patient leaves confused.

"If the AI is expertly presented as a high-tech, highly objective authority that visually validates their human doctor's hurried diagnosis, it can significantly and immediately increase institutional trust." — User Research Result, UP8 profile

Synchronized Ritual response: Transform the AI-generated report into a shared artifact — the doctor's clinical precision and the patient's emotional understanding, synchronized in one view. The patient sees their own healing arc as a narrative of progress, not a stack of confusing documents.

Problem 3: The Information-Siloed PT

Physical Therapists receive only brief text prescriptions — they lack visibility into the radiologist's scan findings, the surgeon's protocol, or the patient's subjective experience. They execute treatment in semi-blindness.

"Vietnamese Physiotherapists struggle to accurately target internal tissue pathologies during therapy because doctors rarely share full digital DICOM imaging data down the chain, providing only brief text prescription sheets, leading to semi-blind therapeutic execution." — User Research Result, UP6 profile

Synchronized Ritual response: Synchronize the PT's treatment session with the radiologist's scan finding and the surgeon's protocol. The PT enters the session already connected to the full clinical chain — not just a one-page prescription.

3. The Four Demo-FRs: How Ritual Maps to Existing FR Scope

Each Demo-FR is an add-on layer on top of existing Functional Requirements. No new backend pipelines are required — the rituals reuse data and infrastructure that already exists or is already planned.

Demo-FR	Ritual Moment	What Becomes Shared	Base FR(s)
01: Morning Cohort Ritual	Opening the patient list	The collective context of each case — who else is working on it, what was last decided	FR-26, FR-25/UC-92006
02: Agreement Moment	Signing a diagnostic report	The act of clinical judgment ripples to Surgeon, PT, Patient simultaneously	FR-25/UC-92006, FR-19, FR-30
03: Daily Progress Ritual	Patient logging symptoms	The daily narrative of recovery, shared between patient and PT before the session begins	FR-28, FR-29, FR-30, FR-20
04: Journey Mirror	Viewing the patient's history	The longitudinal arc of healing, seen through two synchronized lenses (clinical + patient)	FR-16, FR-31, FR-12

4. The Engineering Rationale: Why This Is Not "Just UX Polish"

The Synchronized Ritual concept is grounded in PILOT's hard NFRs and constraints, not in abstract UX theory:

PILOT NFR	How Demo-FRs Respect It
Zero Workflow Friction — no extra clicks, no extra screens	All rituals are embedded in existing actions: opening a list, signing a report, logging a symptom. The ritual is the enriched rendering of data that already exists.
Decree 13 / Data Privacy — strict scrubbing	Ritual data (timestamps, actor names, status chips) is already available in scrubbed form in EMR logs and scan session metadata. No new PII is introduced.
Hardware Heterogeneity — low-spec phones, old GPUs	Ritual UI uses existing rendering pipelines: patient cards, status chips, sprite-sheet thumbnails. Zero-GPU fallback is already required by FR-12.
Air-Gapped Infrastructure — no cloud, no external APIs	All synchronization happens over the local K3s cluster / FastAPI backend. The "sync" in Synchronized Ritual is local data propagation, not cloud-based real-time networking.
Sprint 6 Deadline — only 6 sprints	Demo-FRs are achieved by recomposing existing data (EMR logs, scan sessions, journal entries) into new UI patterns — not by building new data pipelines or ML models.

5. The Stakeholder Narrative: How to Present This

The Synchronized Ritual Demo is not a feature demo. It is a values demo.

"We are not showing you what the system does. We are showing you how it makes every person in this care chain feel connected to each other's work. That is the difference between a tool that processes data and a platform that honors the clinical relationship."

The demo opens with Demo-FR-02 (Agreement Moment) — it has the highest emotional impact: one tap, four lives informed simultaneously. Then peel back to show how each layer (01, 03, 04) builds on the same principle.

The closing argument:

"All of this runs locally at PILOT. No data leaves the hospital. No extra clicks were added to anyone's workflow. And yet — the radiologist who signs a report at 14:30 knows that at 14:30, a surgeon in the OR, a PT in the treatment room, and a patient at home all received a piece of that same moment. That is what we mean by Synchronized Ritual."

6. Risks & Guardrails

Risk	Mitigation
Ritual UI perceived as "extra work" by busy clinicians	All rituals are implicit — they appear in existing views (list cards, sign-off confirmation, journal screen). No new buttons or new screens.
Patient-facing rituals trigger anxiety (e.g., "pain went up" notification)	Ritual feedback uses positive framing — progress arcs, encouragement text, trend arrows. No alarmist language.
Synchronized data introduces a privacy concern	All ritual data is already present in EMR logs and scan sessions. The ritual layer only re-frames existing data — it does not aggregate new data sources.
Demo feels "theatrical" rather than substantive	Demo scripts use realistic synthetic data (e.g., "Case #VN-2048", "Dr. Nguyen", "pain 7->3") and avoid cartoonish UI flourishes. The emotional weight comes from the logic of connection, not decorative animation.
Clinician rejection of "patient-facing" features	Demo-FR-02 and Demo-FR-04 are presented from the clinician's perspective first — the ritual is about their sense of impact, not about "making patients happy."

End of Motivation — Synchronized Ritual Concept for PILOT Demo Session

8.3 KiB Raw Blame History