utkarsharma7/aha

Purpose and Runtime

This is a Next.js App Router healthcare application serving patient, clinician, practitioner, and administrator workflows. The root entry point is src/app/page.js; global application shell and styling begin at src/app/layout.js and src/app/globals.css. It runs as a Node.js/Next.js application with React client/server components and route handlers.

User-Facing Domains

Patient workflows cover health profiles, records, consultations, challenges, journeys, triage, emergency chat, and AI diagnosis. Key route families are src/app/health-profile-2/page.jsx, src/app/records/page.js, and src/app/ai-diagnose-2/page.js.

Plans are a major domain with separate care, diet, and exercise experiences: src/app/plans/care/page.jsx, src/app/plans/diet/page.jsx, and src/app/plans/exercise/page.jsx. Prescription and lab-report detail pages provide analysis, chat, correction, and plan-related views through src/app/prescription/[id]/page.js and src/app/labreport/[id]/page.js.

API Boundary and Backend Integration

The Next.js API layer is primarily a same-origin proxy boundary under src/app/api/proxy. It exposes domain-specific HTTP routes while isolating browser UI code from backend endpoint addressing and request mechanics; shared backend configuration is centered in src/config/api.js and client access is represented by src/services/api.js.

Proxy routes are organized by healthcare aggregate, including src/app/api/proxy/patient/care_plan/overview/route.js, src/app/api/proxy/patient/diet/plan/propose/route.js, and src/app/api/proxy/modules/[moduleCode]/intake/route.js. Dynamic route segments carry resource identity such as patient, plan, chat, report, phase, and invitation IDs.

Care-Plan and Coaching Lifecycle

Care planning is a staged workflow: retrieve an overview, capture/clarify/confirm goals, generate goal-track phases, review phases, and handle advancement decisions. The public UI and proxy implementation boundaries are src/app/plans/care/page.jsx, src/lib/carePlanProxy.js, and src/app/api/proxy/patient/care_plan/phase/[phaseId]/advancement/suggest/route.js.

Diet planning follows an analogous lifecycle: profile questionnaire → goal analysis/confirmation → proposal/plan confirmation → phase outline/generation → daily logging and coaching check-ins. Relevant paths are src/app/plans/diet/components/GoalsManager.jsx, src/lib/dietProxy.js, and src/app/api/proxy/patient/diet/log/route.js.

Conversations, Clinical Records, and Uploads

Chat is modeled as persistent sessions with start, turn, history/list, and specialized diagnosis, emergency, lab, prescription, triage, and care-episode variants. Core routes include src/app/api/proxy/chat/start/route.js, src/app/api/proxy/diagnosisChat/turn/route.js, and src/app/api/proxy/patient/care-episode/[careEpisodeId]/chats/[chatSessionId]/turn/route.js.

Clinical-document ingestion enters through lab-report and prescription uploads, then flows into report/prescription detail, analysis, correction, and care-episode planning. This boundary is represented by src/app/api/proxy/upload/labreport/route.js, src/app/api/proxy/upload/prescription/route.js, and src/app/api/proxy/prescription/[id]/care-episode/plan/route.js.

Roles, Access, and Operations

Authentication has dedicated API handlers, while role-specific UI shells guard patient and doctor views: src/app/api/auth/authenticate/route.js, src/components/AuthGuard.jsx, and src/components/doctor/DoctorAuthGuard.jsx. Doctor workflows are isolated under src/app/doctor/layout.js; invitations and patient selection support clinician-to-patient relationships.

Administrative observability is a separate surface for LLM calls, chat sessions, and turns, backed by an admin API proxy and service layer: src/app/admin/observability/layout.jsx, src/app/api/admin/[...path]/route.js, and src/services/adminObservabilityApi.js. Feature flags are centralized through src/config/featureFlags.js and src/context/FeatureFlagContext.js.