Skip to main content
All articles
Healthcare8 min readSeptember 27, 2026

The Health Stack: Seven Products. One Lifecycle.

The health stack is now seven products spanning the full lifecycle from institutional AI strategy to cancer survivorship navigation. Healthcare Playbook plans. VITAL tests. MedConsult AI executes. SOMA researches. STRIDE records. Prosthetic Atlas educates. STILL navigates. Each product serves a different phase. None replaces another.

Healthcare technology portfolios are usually a list of products that happen to serve the same industry. A clinical workflow tool here, a compliance platform there, maybe a telehealth widget. They sit next to each other in a slide deck. They do not connect.

This health stack is different. Seven products, each serving a distinct phase of a single lifecycle. Remove one and the lifecycle has a gap. Add one from outside and it does not fit the architecture. The stack compounds because each product generates the input the next one needs.

The lifecycle

The seven products map to seven phases:

PhaseProductWhat it does
PlanHealthcare PlaybookStrategy — what to deploy, in what sequence, governed by which frameworks
TestVITALSandbox — whether the workflow survives contact with clinical reality
DeployMedConsult AIExecution — the clinical workflow in production
ResearchSOMAFrontier design — prosthetic care centred on lived experience
RecordSTRIDEPersonal ledger — the wearer’s daily observations structured as evidence
EducateProsthetic AtlasShared vocabulary — the knowledge that makes both sides of the conversation productive
NavigateSTILLSurvivorship — the life timeline when cancer and limb loss collide

Plan → test → deploy → research → record → educate → navigate.

Healthcare Playbook: the strategy layer

Healthcare Playbook answers the institutional question: what should we deploy, in what order, and how do we govern it?

Eight domain deep dives. Twenty-nine plays with step-by-step guidance and KPIs. A readiness assessment that generates a four-quarter roadmap. An ROI modeler that separates soft value from hard value. A governance toolkit aligned to NIST AI RMF, HIPAA, FDA, and Joint Commission. A vendor landscape cataloging 128+ tools across 32 categories.

All processing runs locally in the browser. No data leaves the device. The planning tool itself creates no PHI risk.

What it feeds forward: the sequenced deployment plan that VITAL tests before any system touches a patient.

VITAL: the sandbox layer

VITAL answers the operational question: will this workflow survive deployment?

Eighteen clinical and operational workflows across six domains. Fifty-four synthetic scenario configurations. Case studios where clinicians run the case, challenge the result, and define what the next pilot needs to prove.

VITAL does not test model accuracy. It tests workflow design. A 99% accurate model deployed into a workflow where nobody acts on the output is still a failure.

What it feeds forward: a deployment specification — not a score — that tells MedConsult AI what the workflow needs to prove in production.

MedConsult AI: the execution layer

MedConsult AI is the clinical workflow in production. HIPAA-focused documentation, AI-assisted consultations, voice dictation, and secure patient communication.

The Playbook told the institution what to deploy. VITAL proved the workflow would survive. MedConsult AI runs it.

What it feeds forward: the production reality that informs SOMA’s research agenda — what works, what breaks, what the next generation of care should address.

SOMA: the research layer

SOMA answers the design question: what should the next generation of prosthetic care look like?

Three guided care journeys tracking pressure, volume, and discomfort across a full day. Seven research frontiers: sensory return, interface sensing, adaptive sockets, muscle interfaces, shared control, regional materials, and digital-twin modelling. 3D inspection shows what a design is. 4D inspection shows what a design does over time.

SOMA centres design on lived experience rather than fitting mechanics. Person → experience → design.

What it feeds forward: the research insights that STRIDE’s wearers validate against daily reality, and the design vocabulary that Prosthetic Atlas teaches.

STRIDE: the recording layer

STRIDE answers the wearer’s question: what is actually happening between appointments?

Four daily actions: describe the prosthesis, check in when the fit changes, keep photos and clinical advice, compare the same activity between morning and evening. Time-gated entries capture variation. Photo annotation creates traceable evidence. Revocable case linking shares one concern without opening the full record.

What it feeds forward: the structured daily observations that Prosthetic Atlas helps the wearer articulate, and the evidence that SOMA’s researchers study.

Prosthetic Atlas: the education layer

Prosthetic Atlas answers the conversation question: do both sides have the vocabulary to understand each other?

Three content pathways: Motion (gait comparison), Fit (daily comfort dynamics), The Visit (Brief Builder for appointment preparation). 3D anatomical explorer. K1–K4 classification. Sock ply management. Red flags vs. non-urgent triggers.

What it feeds forward: the shared language that makes STRIDE’s records interpretable and SOMA’s research accessible to the people it serves.

STILL: the navigation layer

STILL answers the question nobody else is assigned to: what about the life timeline?

Four journey pathways: facing what’s next, finding footing, living on my terms, here for someone. Trusted resource links to Memorial Sloan Kettering, Amputee Coalition, and National Cancer Institute. Real patient narratives. Prosthetic possibilities. Storytelling prompts. Support connection directory.

The clinical team handles the treatment timeline. STILL handles the life timeline — the one where identity, daily routines, relationships, and becoming continue after the protocol ends.

What it feeds forward: the human context that makes every other product in the stack meaningful. Technology serves people. STILL centres the person.

Why the stack compounds

Point products don’t compound. They coexist. This stack compounds because each product generates information the next one consumes:

  • The Playbook’s strategy defines what VITAL tests.
  • VITAL’s deployment spec defines what MedConsult AI runs.
  • MedConsult AI’s production reality defines what SOMA researches.
  • SOMA’s research insights define what STRIDE’s wearers validate.
  • STRIDE’s daily records define what Prosthetic Atlas teaches.
  • Prosthetic Atlas’s vocabulary defines how STILL’s users articulate their needs.

Seven products. One data flow. Each product makes the next one more useful.


All seven products are live and free to use.

Healthcare Playbook → — strategy.

VITAL → — sandbox.

MedConsult AI → — execution.

SOMA Studio → — research.

STRIDE → — records.

Prosthetic Atlas → — education.

STILL → — navigation.

Explore the full portfolio →

Richard Leclézio

Richard Leclézio

Enterprise Transformation & AI Delivery Leader

ShareLinkedInX