# Project export: AtriaAI

This document was generated by HackStack to give an AI agent context about a hackathon project. Sections are labeled with their provenance; content marked as truncated was cut to keep this document small.

## Project metadata

- Hackathon: TreeHacks 2026
- Tagline: Autonomous voice agents to support families during health emergencies and optimize recovery plans post discharge.
- Devpost: https://devpost.com/software/atriaai
- GitHub: not linked
- Demo: https://www.youtube.com/watch?v=C4xo_87xCiQ
- Video: https://www.youtube.com/embed/C4xo_87xCiQ?enablejsapi=1&hl=en_US&rel=0&start=&version=3&wmode=transparent
- Team: contributor stats unavailable

## Devpost submission (written by the team)

### Overview

When a loved one is rushed into emergency surgery, families are often left in silence. Clinicians focus on stabilizing the patient, so updates are brief, delayed, or filled with medical jargon. That gap creates anxiety for families and constant interruptions for care teams. We wanted to make critical care more transparent — giving families real-time clarity without adding work for providers. AtriaAI is a real-time, voice-enabled clinical copilot that keeps families informed during emergencies and guides them through recovery after discharge. In our demo, a college student undergoes an emergency appendectomy. Because she previously received a kidney transplant and takes immunosuppressants, her infection risk is higher. Her mother — located remotely — accesses a secure dashboard that shows: Live surgery updates in plain language Contextualized vital sign changes Confidence + stability scoring Personalized recovery plans Monitoring and cost tradeoffs After surgery, the system evaluates post-care pathways — standard recovery, extended monitoring, or ICU observation — modeling complication risk, healing timelines, and out-of-pocket costs. When the family selects ICU monitoring, the care plan updates instantly. We built a multi-agent reasoning system that breaks medical decision support into structured components: Hypothesis generation → Recovery + monitoring pathways Evidence retrieval → Guidelines + literature grounding Safety validation → Risk adjusted for comorbidities Response composition → Clear family-facing updates Simulated EHR data drives real-time updates to risk scores, recovery timelines, and monitoring recommendations. The frontend visualizes reasoning through update cards, pathway comparisons, and live care timelines — with voice interaction layered on top. Frontend React + TypeScript + Vite Tailwind CSS + Radix UI + MUI Framer Motion animations Recharts data visualization Web Speech API + ElevenLabs TTS Backend Python + FastAPI WebSockets (real-time updates) LangGraph (agent orchestration) Pydantic validation AI & Data OpenAI (GPT-4o-mini / GPT-4 reasoning) Jina AI embeddings Elasticsearch hybrid search Synthetic FHIR EHR data (Synthea) Infra Modal (scalable inference compute) Docker (Elasticsearch local deployment) Twilio (SMS alerts) Structuring AI reasoning safely instead of relying on one LLM output Modeling realistic medical risk without overwhelming families Designing confidence scoring that reflects real physiological events Built a true multi-agent clinical reasoning system Modeled safety vs monitoring vs cost tradeoffs in real time Created emotionally intelligent, transparent medical updates Healthcare AI must be structured, observable, and explainable — not just conversational. Separating reasoning into agents dramatically improved safety and clarity, especially in high-stress care moments. Next, we plan to integrate live FHIR hospital data and expand recovery modeling to trauma, cardiac, and oncology care. Our goal is to become the real-time alignment layer between families and care teams.

## README (from the GitHub repository)

No README available.

## Detected evidence (automated analysis)

No repository was indexed for this project. Claimed technologies below could not be checked against code.
- Docker (technology) — claimed on Devpost, not found in the code
- FastAPI (technology) — claimed on Devpost, not found in the code
- Python (language) — claimed on Devpost, not found in the code
- Tailwind CSS (technology) — claimed on Devpost, not found in the code
- TypeScript (language) — claimed on Devpost, not found in the code
- Vercel (technology) — claimed on Devpost, not found in the code

## Codebase structure

No repository index available.

## Key source files

No repository index available; no source files included.