

Caladrius
Caladrius is a privacy first AI triage assistant. It aims to cut through the inefficiencies of triage intake and inequities in prioritization, while maintaining a privacy first HIPAA compliant ethos. Awarded 2nd place in HackGT 12's track for social impact.
HackGT story
HackGT was the first time I decided to just go big with my hack. We built Caladrius, a privacy first AI triage assistant for hospitals. We worked with encrypted medical passports on mobile devices, secure QR code transmission of data, AI medical agents, injecting real time information into reasoning, and giving human control to the medical professionals that make everything run. We won 2nd place in the Curator's Cause track for social impact. Working with Avyukta Nagrath, Michael Chan, and Joshua Okonkwo, even through hours of frustration, scrapping ideas, and merge conflicts, we were able to put it all together in the end. Over 900 hackers at HackGT, and we still made something that mattered.
Why triage
My teammate had just been to the hospital. He remembered sitting down and filling out a long form. Then, after he got a room, the nurse read the form, left, spoke with another person about the symptoms, and only then came back to order some initial tests. We were talking and thought, what if that entire setup process was taken care of? That meant loading the medical history quickly and seamlessly, intelligently asking questions based on symptoms and medical history, and then writing up an initial prognosis along with reasoning, adjustable priority, and recommended next steps. Since this initial screening is largely general medical knowledge, we can automate a significant amount of the initial data gathering and decision making with an agentic system using a medical model. There was no reason for a sick person to do unneeded data entry, or for the nurse to then spend time making a general knowledge based medical prognosis and sifting through the patient's medical history to make an informed decision. It was inefficient and wasted time that the nurse could have spent caring for the patient.
Why HIPAA was non negotiable
We wanted it to be as realistic as possible. Every person we called about the problem (teammate's mom works in hospital data processing, teammate's dad was a doctor) mentioned that the entire difficulty of building good healthcare products is that we need to maintain HIPAA compliance. So, we took the first step to modeling that reality.
Multi agent architecture
We needed a questioning loop with feedback. One agent evaluates the Q&A to see if it has enough information to produce a diagnosis, and if not, it identifies a missing information gap. The other agent then questions the user interactively in order to fill that gap, and the loop repeats. Finally, a third agent compares the result against the other existing diagnoses in a certain severity category to assign it to a precise priority that's adjustable by the triage nurses. The point of the multi agent system is to separate the evaluator from the questioner and the diagnoser, reducing bias and overfitting in the reasoning process.
The pitch
The judges latched on to the fact that we were solving a real problem and accounted for real factors that affected the industry in practice. This meant things like encryption, deleting data after processing, using local models, separating bias, and the human in the loop involvement throughout the process, especially at the end during the adjustable priority of diagnoses in the triaging room. Our pitch went something like this: Imagine you're sitting in a triage room, sick and dizzy, and you're given a form that's 20 questions. It doesn't seem that long, but then after that form is submitted, it gets processed into a computer. After that, the computer reads the data, and the nurse has to look at it. They then pull your history, take your symptoms, and compare all three of those things together. Maybe in stages, maybe other people do it who have no context of the situation. After all that is done, finally, after two hours, they order some tests. Imagine how much of that process could be streamlined if the questions were intelligent, the history was easily pulled, and the general knowledge based diagnosis was automatic with priority baked in. I knew it landed when the judge for our track had worked at a medical practice and knew exactly the challenge we were talking about. He saw how we carefully dealt with the exact priorities and issues that a real doctor and a real triage nurse would care about in that scenario. We wouldn't have known that unless we spoke with the people we did, doctors and real hospital data processing workers.
For startups and founding teams
Karthik Thyagarajan is a founder-engineer studying Computer Science and Artificial Intelligence at Purdue. At Samsung Research America, he co-architected an always-on AI agent runtime for XR glasses. He is currently building Tavi, a voice teammate for engineering standups, and co-founded buildpurdue, a founder community at Purdue. His work spans agent infrastructure, on-device AI, product engineering, and evaluation.
For an early team building AI products, his strongest demonstrated fit is owning a broad technical problem from product decisions through implementation and evaluation. His current interests are live voice and video AI, AI-first wearables, and infrastructure that lets agents discover and use internet services.
Substantial ownership of agent systems
At Samsung Research America (May to August 2026), he co-architected an always-on agent orchestrator in Kotlin and owned half of a 25+ module runtime. His reported on-device router achieved 95% signal suppression and 90% intent-routing accuracy. His work also covered tool permissions, model routing, memory, and phone control, connecting model behavior to a usable device experience.
Builds teams and operating systems around a problem
As buildpurdue's co-founder and co-president, he helped turn an informal gathering into a founder community with a selective cohort, weekly co-working, funding, and founder-led problem-solving workshops. He built much of its web platform and integrated CRM, applications, events, and check-ins. His account describes data on around 500 students and a mailing list of about 1,000.
Makes technical claims testable
He built PARM, an open-source causal benchmark for when an agent should use personal memory: 157 frozen scenarios and 471 executable cases, with deterministic scoring and versioned replay artifacts. Its portfolio account explicitly distinguishes development results from held-out claims. He also built google-tools-mcp, a published MCP server exposing 169 Google Workspace tools through one OAuth flow.
Pursues difficult product problems
He is currently building Tavi, a voice teammate intended to answer codebase questions and handle small action items during engineering standups. The project tackles multi-person turn-taking, when to stay quiet, sandboxed coding, and synthetic meeting evaluations. This is ongoing work, rather than a claim of shipped adoption. His published interests explain the direction behind it.
Co-founder who ships and thinks about distribution
At Repple (November 2025 to June 2026), he co-founded a competitive fitness app released on the App Store and built the entire FastAPI, PostgreSQL, and Supabase backend, including synchronized workouts, ELO matchmaking, and weekly competition logic. His firsthand account also describes marketing before the UI existed, campus distribution, and why local community density mattered to the product.
This brief summarizes Karthik's public portfolio and firsthand accounts. Employment contributions and internal performance metrics are self-reported; linked code and artifacts provide additional evidence where available.