Skip to content

Full Call Workflow — implement router + UI against existing types #78

@thefiredev-cloud

Description

@thefiredev-cloud

Type contract exists at components/tools/full-call/types.ts (commit 6e4f48be or successor). Defines FullCallGenerateInput, FullCallGenerateResult, per-subsystem status types.

Implementation scope:

  • server/routers/tools/full-call.ts — fan-out procedure calling existing tools.radioReport.generate, tools.handoff.generate, tools.epcr.draft (single Claude call with 3-output system prompt, or parallel calls with shared PHI-redact)
  • app/tools/full-call.tsx — route
  • components/tools/full-call/FullCallWorkflow.tsx — UI: one narrative input, 3-tab result view (Radio | Handoff | ePCR)
  • Shared rate limit: 10/hour/user
  • Partial-failure handling via warnings[] + status object

Plus Demo Mode:

  • app/demo.tsx — 6 curated scenario showcase (no LLM calls, hardcoded sample data)
  • Scenarios: Cardiac Arrest, Peds Fever, STEMI, Refusal/AMA, Trauma MVC, Stroke

Branch autonomous-2026-04-22-night already has the 3 individual agents merged. This PR just composes them.

Related planning docs

Acceptance

  • tools.fullCall.generate mutation exists + returns typed shape
  • UI renders 3 tabs with copy-to-clipboard per output
  • Demo mode accessible from Tools tab
  • 12+ tests covering happy path + partial failures + demo scenario validity
  • pnpm check clean

Metadata

Metadata

Assignees

No one assigned

    Labels

    autonomous-followupFollow-up from autonomous branch workfeatureNew feature implementationh2Horizon 2: mid-term, 2-6 weeks

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions