sakthimaran-venom/curatrack-v2

1. System Purpose and Deployable Surfaces

CuraTrack is a healthcare platform spanning a Next.js web/doctor portal, a separate mobile client, and a FastAPI clinical-services API. Its core workflows are health-record ingestion, patient monitoring, care access, telemedicine, emergency sharing, and benefits/safety analysis. Main entry points are backend/main.py, frontend/app/page.tsx, and mobile/app/page.tsx.

2. Identity, Persistence, and Access Boundary

Supabase is the shared system of record for PostgreSQL data, authentication, RLS authorization, and realtime signaling. Web uses Supabase client/server integrations; backend has privileged service access configured through environment variables. Database schemas encode the platform contract, including telemedicine and SDOH extensions.

• frontend/lib/supabase/client.ts

• frontend/lib/supabase/server.ts

• frontend/supabase/complete_v3_schema.sql

• frontend/supabase/telemedicine_schema.sql

3. FastAPI Domain API and Service Layer

The Python API composes route modules for patient-facing and clinical functions, with services separating persistence, parsing, LLM access, audit logging, JWT handling, and eligibility logic. It is the boundary for secrets and server-side integrations, rather than exposing those directly from clients.

• backend/main.py

• backend/routes/ingest.py

• backend/routes/passport.py

• backend/services/patient_data.py

• backend/services/audit_logger.py

4. Medical Document Ingestion Pipeline

Uploaded records enter the ingestion/OCR routes, are processed through Tesseract and AI parsing, then become structured patient data suitable for records and insight views. The backend supports Gemini and likely local Ollama/Llama fallback through a dedicated LLM service; sample ingestion JSON is retained locally under backend/data/.

• backend/routes/ocr.py

• backend/routes/ingest.py

• backend/services/ocr_service.py

• backend/services/parser_service.py

• backend/services/llm_service.py

5. Clinical Intelligence, Safety, and Assistance

Backend route families calculate health risks and SDOH outcomes, generate insights, check medicines against openFDA, and match insurance/government-scheme eligibility. These features consume patient records/vitals and external APIs, then return actionable summaries to web and mobile screens.

• backend/routes/health_risks.py

• backend/routes/sdoh.py

• backend/routes/drug_checker.py

• backend/routes/insurance.py

• backend/services/insights_service.py

• backend/services/government_schemes.py

6. Web Care Portals and Telemedicine

The Next.js App Router supplies patient dashboard areas, doctor workflows, role onboarding, QR passport access, and dynamic WebRTC call rooms. WebRTC media is peer-to-peer; Supabase Realtime acts as signaling infrastructure. Google STUN is an external connectivity dependency. The frontend also has server routes for auth and Google Fit OAuth/data proxying.

• frontend/app/(dashboard)/dashboard/page.tsx

• frontend/app/doctor/page.tsx

• frontend/app/call/[roomId]/CallClient.tsx

• frontend/lib/webrtc.ts

• frontend/app/api/auth/google/route.ts

7. Mobile and Native Delivery

mobile/ is a distinct mobile-oriented Next/Expo-style client surface with health, records, alerts, appointment, scheme, and drug-checker flows, sharing Supabase and backend API patterns. frontend/ additionally contains a Capacitor Android wrapper for its web application, with native startup at MainActivity.

• mobile/app/dashboard/page.tsx

• mobile/lib/api.ts

• mobile/lib/supabaseClient.ts

• frontend/capacitor.config.ts

• frontend/android/app/src/main/java/com/curatrack/app/MainActivity.java

8. Emergency Passport Flow

A patient passport route generates expiring JWT-backed QR access; token verification retrieves a constrained emergency health summary and is expected to audit access. This is a high-sensitivity boundary: token signing, Supabase RLS/service access, client QR rendering, and public token routes must remain coordinated.

• backend/routes/qr.py

• backend/routes/passport.py

• backend/services/jwt_helper.py

• frontend/app/passport/[token]/page.tsx

• frontend/components/PassportQRModal.tsx