Dedicated medication workflow and shared operational projections such as queue, review, blocked, overdue, and recently completed views.
CASE STUDY 01 / HEALTHCARE WORKFLOW
Treatment Signal
A privacy-aware operational coordination layer for treatment-related work: clear ownership, verification-gated handoffs, human decisions, auditability, and minimum-necessary information without becoming a second clinical record.
PRODUCTHEALTHCAREIMPLEMENTED + TESTED CHECKPOINTSNON-PRODUCTIONSYNTHETIC DATA
01 / HUMAN PROBLEM
Coordination fails between systems.
Treatment work can span medication administration records, EHR documentation, staff queues, prescriber decisions, verification, follow-up, and completion. A person can be clinically documented while the operational next action still has no clear owner.
The product hypothesis was deliberately narrower than “replace the EHR”: create an operational Signal with explicit ownership and state, while preserving clinical source-of-truth boundaries.
02 / WORKFLOW
Make every consequential handoff visible.
CREATE→CLAIM→TRIAGE→ASSIGN→WORK→VERIFY→HUMAN DECISION→RESOLVE→VERIFY COMPLETION→CLOSE
The workflow uses verification gates before a prescriber decision and before final closure. The important product decision is that “done” is not a button label; it is a state supported by evidence and an attributable action history.
03 / SOFTWARE
A bounded application core, not demo chrome.
Server actions flow through policy/state guards into a server-only persistence command boundary and attributable audit behavior.
A dedicated non-production Supabase environment was used for synthetic RBAC, state persistence, reload verification, and access-boundary testing.
Product decisions
- Keep opaque operational identity separate from unnecessary clinical disclosure.
- Represent source-system verification explicitly instead of silently copying full records.
- Make prescriber disposition a human decision state, not an AI action.
- Use minimum-necessary projections rather than reproducing the entire EHR or eMAR.
04 / EVIDENCE
Test the state, not just the screen.
A synthetic Signal traversed create through closure, reloaded as CLOSED, preserved verification/disposition state, and carried 11 linked audit events.
Repository evidence records RLS on operational tables and denial of the mutation RPC to anonymous and ordinary authenticated roles in the non-production environment.
An exact implementation checkpoint passed domain tests, Next.js production build, production server boot, route HTTP assertions, headless Chrome rendering, screenshot artifact generation, and ontology lint.
Password-protection hardening and real production identity/integration gates remained open. No production PHI or live clinical integrations are represented as active.
Evidence basis: repository-backed implementation, validation PRs, synthetic persistence receipts, and non-production security boundaries. Test checkpoints are not silently promoted to production proof.
05 / LIMITS
What this does not claim.
- No production clinical deployment claim.
- No claim that an employer commissioned, approved, or adopted this independent prototype.
- No real patient records displayed in this portfolio.
- No claim that source-system APIs or integrations are active unless separately verified.
- No autonomous prescribing, diagnosis, eligibility, or adverse treatment decisions.
WHAT I LEARNED
In consequential workflows, the useful product is often not another giant record system. It is the missing coordination layer that makes ownership, verification, authority, and completion impossible to hand-wave.
Contact: founder@thehumancode.tech