Signals are distributed.
Appointments, intake completion, resource conflicts, clinical follow-up, and billing readiness are different workflows. A useful surface should connect the handoff without pretending they share one source of truth.
Flagship case study / AI implementation
A calm, recruiter-facing walkthrough of how I translate a messy dental-office workflow into a bounded operating picture: queue the signal, preserve the boundary, and hand the decision to a human.
01 / brief
The design goal is not to make the practice look busy. It is to make operational judgment visible: what is known, what needs a person, and what the system must refuse to imply.
Appointments, intake completion, resource conflicts, clinical follow-up, and billing readiness are different workflows. A useful surface should connect the handoff without pretending they share one source of truth.
The walkthrough moves one synthetic case from an operations queue to an intake signal, then to a clinical signal and a human review handoff. Every transition is visible and reversible.
No PHI, claims, payments, signatures, persistence, or production outcome is hidden behind the interaction. The page is a browser-local read-model demonstration.
02 / critical path
Start with the work queue, inspect the synthetic appointment and intake context, surface the clinical follow-up, and route a review request. This is a deterministic local fixture: no network, no save, no submission.
03 / architecture & evidence
The important architecture decision is not “where can AI go?” It is “where does a signal stop being a projection and require an authorized human or connected service?”
Boundary 01
The source implementation uses a typed presentation projection with explicit safe states. That gives the UI a truthful loading, empty, or error posture before any clinical or financial value is shown.
Boundary 02
A queue item can be classified and routed without becoming a diagnosis, signature, claim, payment, or scheduling mutation. The demo ends at the handoff.
Boundary 03
Production work would add authorization, audit, idempotency, append-oriented clinical history, and recovery. Those are shown as a seam, not claimed as delivered here.
04 / narrative
A recruiter should be able to scan the story quickly and still find enough technical detail to ask a useful follow-up question.
Problem
Staff do not need another dashboard full of counters. They need to know which signal is urgent, what context is safe to show, and who owns the next decision.
Constraints
Approach
I kept the browser artifact small and deterministic while preserving the source behavior vocabulary: schedule/resource status, intake completion, clinical note follow-up, and honest not-connected states.
Key decisions
Unavailable data is a product state, not a blank card. Planned persistence is visually separated from observed prototype behavior so a recruiter can see where implementation work remains.
05 / evidence & QA
The source project has its own validation suite. This case study records what that evidence supports and what this static route adds as a review surface.
The source command-center projection renders deterministic synthetic practice context, appointment/resource statuses, attention items, unsigned-note follow-up, exact money fields, and claim-readiness labels. Its tests also cover safe states, escaping, navigation, and responsive contracts.
Source evidence Reference: integration-command-center worktree at commit 8c47c3d.
This page's walkthrough is intentionally browser-local. The four-step state machine, reset behavior, empty state, unavailable-source state, and loading state are implemented in inline JavaScript with no network reads and no storage writes.
Route evidence Verify by opening the walkthrough, advancing through the handoff, previewing state lab buttons, and resetting.
This is not a HIPAA certification, production deployment, clinical decision support system, payment processor, clearinghouse connection, scheduling system, or measured customer outcome. It is a sanitized portfolio artifact.
Proposed follow-up Connect only after authorization, audit, persistence, test, and operational recovery gates are defined.
06 / claim ledger
The ledger keeps verified source behavior, synthetic demo fixture, observed prototype behavior, and proposed follow-up separate.
| Claim | Classification | Evidence / treatment |
|---|---|---|
Command-center projection surfaces operational, clinical follow-up, and claim-readiness signals. | Verified source behavior | Source renderer and tests; represented here with sanitized fixture labels. |
Walkthrough can route a signal to a human review seam without writing a record. | Observed prototype | Deterministic local state machine in this route; resettable and no network. |
Displayed people, appointment labels, counts, and statuses are real operational outcomes. | Not claimed · synthetic only | All records are fictional fixture values and visibly marked as such. |
Authorization, audit, persistence, and recovery seams should be connected next. | Proposed follow-up | Architecture map shows dashed, disconnected boundaries; no production implementation is implied. |