Building a Safer AI Co-Pilot: 3 Architecture Patterns from our ICU Hackathon Project

When building an AI co-pilot for ICU nurses—where mistakes can literally cost lives—you can't just throw a LangChain wrapper around a PDF and hope for the best. Our project, Panacea , acts as a voice-enabled real-time assistant for operating complex medical machines at 3 AM. It’s built on Google’s Agent Development Kit (ADK) and the Gemini Live API. Because we were building for healthcare, we had to reject a lot of standard "hackathon" patterns in favor of strict deterministic architecture. If you are building an AI agent that needs to be fast and safe, here are three architectural patterns we used to build Panacea. 1. The Clean Two-Agent Topology The current trend is to build massive, 20-agent orchestrators where agents debate each other to reach a conclusion. That’s cool for coding assistants, but in a hospital, extra latency and non-deterministic routing are dangerous. We kept our topology dead simple: One agent to talk, one agent to read. The Voice Agent ( gemini-live-2.5-flash-nat