Operational leads. Human decisions.
TransferSignal is a transfer-operations workspace that turns hospital-to-hospital capacity calls into de-identified, timestamped evidence. Coordinators create and manage searches, maintain approved facility endpoints, monitor calls, resolve exceptions, and prepare human-owned handoffs. CALL-E handles switchboards, holds, transfers, and natural conversation; deterministic application logic decides whether a result is safe to show as a viable operational lead.
The initial wedge is time-critical adolescent behavioral-health placement. This is a synthetic hackathon prototype—not a clinical decision system, emergency service, patient-matching guarantee, bed reservation, or patient acceptance tool.
The Agency for Healthcare Research and Quality documented a rural emergency physician calling 25 hospitals across five states during one shift while three critically ill patients remained in a seven-bed emergency department. Capacity is live, fragmented across institutions, and frequently reachable only through switchboards and transfer desks.
Read the January 2025 AHRQ technical report.
- A coordinator starts a search and enters de-identified operational criteria: service, age band, legal status, accessibility, radius, urgency, and requesting unit.
- They choose destinations from an administrator-managed network of approved facility endpoints.
- TransferSignal previews the exact recipients, CALL-E goal, data boundary, and side effect before calls unlock.
- CALL-E calls up to three authorized test endpoints in a bounded wave.
- A deterministic evidence gate reconciles terminal status, exact recipient, correct desk, service match, possible capacity, review readiness, transcript evidence, contradictions, and freshness.
- The workspace shows one of three outcomes: viable lead, not viable, or manual review. Exceptions also enter a dedicated human-review queue.
- A clinician may generate a secure handoff checklist. The application does not send patient data or accept a transfer.
The seeded demo demonstrates three hard cases in one run:
- an adult-only facility, excluded with transcript evidence;
- an initially positive answer followed by a correction, failed closed for manual review;
- a transfer center that can review a secure referral now, shown as a 15-minute operational lead—not acceptance.
More product screenshots
Requirements: nvm, Node 24.21.0, and npm.
nvm use
npm install
npm run devOpen http://localhost:3000. Demo mode requires no credentials and never places a call.
The product routes are:
/— public product and problem landing page;/dashboard— operations overview;/searchesand/searches/new— search history and the real input workflow;/searches/:id— call execution, evidence, criteria, audit, and handoff;/facilities— approved facility network;/calls— call audit log;/evidence— exception resolution queue;/protocols— versioned call protocols;/settings— CALL-E readiness and application safeguards.
Quality checks:
npm test
npm run lint
npm run buildThe real integration uses the official TypeScript SDK, @call-e/calle@0.7.0, from server-only Next.js routes.
Copy .env.example to .env.local and provide:
LIVE_CALLS=false
CALLE_API_KEY=
CALLE_BASE_URL=https://api.heycall-e.com
CALLE_ALLOWED_PHONES=+15551234567,+15557654321,+15559876543Safety defaults:
LIVE_CALLS=falseunless deliberately enabled.- API credentials never enter browser code.
- The browser submits facility aliases; phone numbers come only from the server-side allowlist.
- A live request is rejected unless the operator has previewed and explicitly confirmed it.
- A durable run key is established before the side effect and converted to a stable idempotency key.
- At most three recipients can be called.
- Public UI masks phone numbers and call identifiers.
- No automatic retry follows an ambiguous outcome.
Live API routes:
GET /api/calls/readiness— reports whether live mode is safely configured.POST /api/calls— submits one allowlisted, explicitly confirmed, idempotent batch.GET /api/calls/:callId— reads a call without returning recipient phone numbers or provider IDs.
Do not use real hospital numbers for the hackathon demo. Use only numbers owned by teammates or people who explicitly authorized the test and know they are playing fictional facility staff.
Coordinator preview + explicit approval
│
▼
CALL-E server-side SDK call
│
▼
status + structured result + transcript evidence
│
▼
deterministic evidence gate
├── viable operational lead
├── evidence-backed exclusion
└── unknown / manual review
│
▼
clinician-approved handoff checklist
The language model gathers and structures evidence. It does not own the final truth condition. The verifier in src/lib/verifier.ts is deterministic and covered by tests for positive, negative, voicemail, contradiction, and missing-evidence paths.
The demo profile may include age band, legal status, service capability, mobility accommodation, distance radius, and urgency. It deliberately excludes patient name, date of birth, diagnosis narrative, medical record number, address, and patient phone number.
Production deployment would require institutional authorization, an approved facility network, privacy/security review, contracts, access control, audit retention, recording-consent analysis, and integration with each organization’s secure referral workflow. This prototype makes no HIPAA-readiness claim.
- 0:00–0:19: Show the official AHRQ and GAO report excerpts documenting 25-hospital and 39-call transfer searches.
- 0:19–0:34: Define TransferSignal plainly and open the multi-route operations workspace.
- 0:34–1:06: Enter the operational need, choose approved facilities, and review the search.
- 1:06–1:26: Confirm the call wave and show CALL-E beginning the work.
- 1:26–1:53: Play 26 uninterrupted seconds of the real CALL-E call with the synchronized transcript.
- 1:53–2:19: Show the deterministic validator and the not-viable, manual-review, and viable outcomes.
- 2:19–2:27: Open the evidence-review queue and compare the conflicting statements.
- 2:27–2:46: Explain the system architecture and boundary between CALL-E, deterministic code, and hospital staff.
- 2:46–2:52: Close with the product description and “Built with CALL-E.”
- Next.js 16, React 19, and TypeScript
- Official CALL-E TypeScript SDK
- Deterministic evidence reconciliation
- Vitest test suite
- Multi-route, responsive operations workspace with a credential-free demo path