CareBridge is a modern healthcare platform built to replace legacy patient-record systems, distinguished by an AI oversight layer that proactively detects cross-specialty clinical gaps — the dangerous patterns that individual specialists, each focused on their own slice of a patient’s care, routinely miss. Every clinical data mutation flows through an event queue where a deterministic rules engine and an LLM review evaluate the patient’s complete picture across specialties, not just the latest chart entry. The motivating example is concrete: a cancer patient with a known DVT history presents with a new headache; her oncologist adjusts chemo and her radiologist checks her IVC filter, but neither connects malignancy-driven hypercoagulability plus established venous thromboembolism plus a new neurological symptom into a textbook stroke-risk pattern. CareBridge catches that automatically.
Quick Links
- Architecture Overview — the event-driven monorepo, services, and data flow
- AI Oversight Layer — the rules engine, LLM review, and BullMQ worker
- Clinical Domain Model — patients, charts, flags, and the database schema
- Developer Guide — setup, commands, conventions, and how to extend the system
- Compliance and Safety — HIPAA, PHI encryption, and the CDS non-device posture
- Design Decisions — the architectural choices and their rationale
Key Facts
| What it is | Cross-specialty healthcare platform with an AI clinical-safety oversight layer |
| Stack | TypeScript (strict, ESM), Turborepo + pnpm, Fastify + tRPC, Next.js 15 + React 19, Drizzle ORM + PostgreSQL 16, BullMQ + Redis 7, Zod, Claude API |
| Structure | Monorepo: packages/ (shared libraries), services/ (backend), apps/ (clinician + patient portals), tooling/ |
| Status | Active development — DB schema, seed data, AI oversight engine, and core services complete; notifications, FHIR gateway, scheduling, and portal UIs scaffolded |
| License | MIT |
| Source of truth | The CareBridge repository — this wiki mirrors its README.md, CLAUDE.md, and docs/ |
The canonical, always-current details live in the source repo. Where a page references a specific design or runbook, it links to the file in github.com/blamechris/carebridge as the authoritative source.