Abby now learns from the entire research community. When a researcher builds a successful diabetes cohort, that pattern becomes available to every other researcher. Questions asked three or more times across users automatically become institutional FAQs with vetted answers. Data quality findings discovered by one team warn all teams. Phase 6 completes the Abby 2.0 cognitive architecture.
Abby now has two brains. Simple queries stay local on MedGemma (fast, free). Complex reasoning escalates to Claude via API (powerful, cloud). A PHI sanitizer blocks any patient data from leaving the network, and a cost tracker with circuit breaker keeps spending within budget. Researchers get smarter answers on hard questions without compromising privacy or breaking the bank.
Abby now understands that metformin is a drug used for Type 2 diabetes mellitus, which is a subtype of diabetes mellitus. She traverses OMOP concept hierarchies, finds siblings and related concepts, and warns researchers when they're building on sparse data. Phase 3 turns keyword matching into relational understanding.
Today marked a significant architectural milestone for Abby, Parthenon's AI research assistant: the completion of Phase 1 of the Abby 2.0 memory overhaul. Eighty-six commits landed today, all focused on one goal — giving Abby a durable, queryable memory backed by PostgreSQL rather than ChromaDB, and surfacing user research context directly in the chat interface.
A big day focused on getting the Ask-Abby AI assistant into a genuinely reliable state — squashing a cascade of cold-start failures, wiring up a comprehensive integration test suite, and cleaning up some fixture hygiene issues that were quietly polluting our design exports. Eighty-nine commits landed in Parthenon today, and the platform feels meaningfully more stable for it.
Abby now builds a persistent research profile for every user, tracks conversation topics across turns, and assembles context through a ranked, budget-aware pipeline. Phase 1 of the Abby 2.0 cognitive architecture lays the memory foundation — moving from stateless Q&A to a personalized research assistant that gets better with every interaction.
What started as "Abby's responses are slow" turned into an 18-hour deep dive that touched every layer of the AI stack — from GPU driver backends to embedding model race conditions to the fundamental question of why a 4-billion-parameter medical LLM was confidently inventing researcher names. By the end, Abby went from 15-25 second hallucinated responses to 2-5 second grounded answers backed by 167,000 vectors of medical knowledge — and we found that an 8-megabyte systemd memory lock was silently killing 25% of all GPU inference requests.
Abby can now answer "What concept sets do we have for diabetes?" and "How many patients are in our CDM?" with real data — queried live from the Parthenon PostgreSQL database at response time. Eight contextual tools give her awareness of concept sets, cohort definitions, vocabulary concepts, Achilles characterization stats, data quality results, cohort generation counts, CDM summaries, and analysis executions.
A productive Sunday on the Parthenon platform — 70 commits landed today covering four distinct themes: hardening the real-time Commons presence system, fixing a persistent CSRF authentication bug, overhauling the Grafana observability stack, and significantly expanding the medical knowledge base powering Abby, our AI research assistant.
We stood up the full Parthenon analyses pipeline end-to-end: 11 comparative effectiveness studies across 10 disease areas, 46 generated cohorts, and 26 executed analyses including R-based CohortMethod propensity score matching on populations up to 68,000 patients. Along the way, we found and fixed every null-safety bug that only surfaces when real analysis results hit the frontend.