A healthcare team needed an interactive product demonstration that made its decisions and care-coordination workflow understandable. The starting point was a supplied dashboard prototype, with design and calculation rules that needed to become a coherent hosted experience.
I adapted that material into a React/Next.js demonstration, then extended it with a second release covering member choices, referrals, booking and follow-up. My role was frontend and workflow implementation, including application state, scenario behavior and exportable records.
Making the dashboard interactive
The original demonstration lets reviewers change assumptions and monitoring periods and see the connected behavior of the dashboard. I implemented the supplied rules and linked the decisions into a history that could be inspected, reset and exported.
This gave the team a working demonstration to walk through. Instead of discussing each screen independently, reviewers could change the inputs, follow the resulting sequence and return to a known starting state when they wanted to compare another scenario.

Concept illustration of approvals, member choices, referrals, booking and follow-up in the demonstration.
Extending it into a coordination workflow
The next release brought together sponsor approval, scripted member conversations, referrals, partner acknowledgement, booking and follow-up. It also included situations where a person needs assistance or the normal route through the process does not fit.
These interactions were connected through the demonstration's state. Reviewers could follow a scenario across the different stages and inspect the decisions associated with it. Approved assumptions remained fixed for the relevant scenario, giving the subsequent interactions a consistent starting point.
I also implemented browser-state separation between demonstration accounts and protection against duplicate events. Those details helped keep the walkthrough consistent when reviewers returned to a scenario or repeated an interaction.
Saved state and reviewable records
The prototype uses browser-local persistence so a reviewer can return to saved demonstration state. Reset behavior supports starting a fresh walkthrough, while HTML and JSON exports provide records of the decisions and events from a scenario.
Those exports serve a practical purpose during product review: the team can refer to the same sequence when discussing a change, an exception or the requirements for the next implementation. They are records of the simulated demonstration, not clinical records.

Concept illustration of human-assistance scenarios and exportable decision records in the prototype.
What was delivered
Both hosted demonstration releases were accepted. A separate planning engagement then covered the next pilot implementation, including the reusable frontend foundation, persistence requirements and dependencies for the proposed pilot slice.
The delivered demonstrations use synthetic data and deterministic, scripted scenarios. They do not include a live AI agent, real patient records, production clinical integrations or live messaging and booking services. Their purpose is to make the proposed product behavior tangible before those production connections are built.
Client names and application screens remain private. The accompanying images are concept illustrations of the coordination workflow and its exceptions, not screenshots of a live healthcare system.
0 likes · 2 views · Nov 16, 2026
An interactive React/Next.js demonstration of approvals, member choices, referrals, booking and follow-up, using synthetic data.