Skip to main content

Team Name: Ctrl All Delete

Description: Triage happens once, at the door. After that, a patient can sit in the waiting room for hours while their heart rate climbs and their oxygen drops, and nobody notices until it gets serious. Atria watches what happens after triage, so care goes where it’s needed most.

Part 1: Patient intake (patient-facing). Patients check in from their phone with their symptoms and a pain score. They get a ticket and can see their place in line (ticket numbers only, never other people’s names). They can tell staff “I feel worse” or send a new pain score at any time.

Part 2: ER operations dashboard (staff-facing). Nurses set priority 1 to 3 and record re-checks: heart rate, oxygen and pain. Atria checks every new reading. If a patient gets worse on every check, they get a red alert, even if they were triaged as low priority. The nurse can ask for a re-check (it shows up on the patient’s phone), acknowledge the alert and raise the priority, which moves the patient up the line. Nurses can also ask Atria questions like “who should be re-checked next?” A Nearby ERs view uses Raleigh / Wake County open data to show the emergency facilities around the hospital (names, locations and listed services), so staff know the other options in the area if a patient needs to go elsewhere.

Part 3: Guardrails and trust layer. Atria never sets priority, diagnoses or decides treatment. A nurse does. Every nurse action is saved to an audit log. Answers from Gemini are checked against the recorded readings, and if one cites a number that isn’t in the data, we show an answer built directly from the readings instead, clearly labeled. All patients in the demo are made up.

https://atria-er.vercel.app/

Built with

pythonjavascriptnode.jsgithubpostgresqlsqlvercelgeminidockernext.jsfastapireactsentry

AI tools

Coded withClaude CodeCodexGemini 3.5 Flash Lite

Prize Categories Entered

  • Google

    Best Use of the Google Gemini API

    Submitted

    Nurses use "Ask Atria" to ask plain questions about the waiting room, like who to re-check next, and Gemini (gemini-3.5-flash) answers using only the recorded readings. We check every answer against that data, and if Gemini cites a number that isn't there, we show a labeled answer built straight from the readings instead.

  • Tiger Data Q3 2026 - Q2 2027

    Best Use of Tiger Data

    Submitted

    Tiger Data is our main database: check-ins, every vital reading and the nurse audit log all live there. Readings also go into a TimescaleDB hypertable with continuous aggregates and compression, which powers the vitals trends page for each patient.

  • Event prize

    Sentry Raffle

    Submitted

    Sentry traces every backend request, with our own spans for check-ins, re-checks, the patient and waiting-room rules, audit writes and each Gemini call. That lets us follow a single alert from the reading that caused it to the nurse who acted on it.

  • Event prize

    Best Use of Raleigh Open Data

    Submitted

    We use Wake County's public GIS dataset "Hospitals, Wake County and Surrounding" to show staff the 22 emergency facilities in and around Raleigh, with their locations and listed services. It's kept separate from our made-up patient data, and the page notes that the dataset doesn't include live capacity or wait times.