anto-remy/remy-care-connect

Purpose and Runtime

Remy Care Connect is a role-based maternal-health frontend for mothers, community health workers (CHWs), nurses, and facility staff. It provides registration/authentication, care monitoring, assignments, escalations, appointments, and notifications. The browser SPA is built with React/TypeScript and Vite; Tailwind/PostCSS support styling. The stated backend boundary is a FastAPI/PostgreSQL service, accessed from the frontend rather than present in this repository.

Entry points: src/main.tsx, src/App.tsx, and index.html.

Application Composition and Routing

App.tsx is the application shell and route composition point. Page-level entry routes separate public landing/auth flows from role-specific application surfaces:

• Public and role selection: src/pages/LandingPage.tsx, src/pages/Login.tsx, src/pages/RoleSelector.tsx

• Mother surfaces: src/pages/MotherIndex.tsx, src/pages/ModernMotherIndex.tsx

• Worker/facility surfaces: src/pages/CHWIndex.tsx, src/pages/NurseIndex.tsx, src/pages/FacilityIndex.tsx

Protected access is enforced at the UI routing boundary by src/components/ProtectedRoute.tsx.

Identity, Roles, and Onboarding

Authentication state is centralized in src/contexts/AuthContext.tsx; API-facing authentication concerns are isolated in src/services/authService.ts and facility-staff-specific auth in src/services/facilityStaffAuthService.ts. Registration is role-specific, including src/pages/RegisterMother.tsx, src/pages/RegisterHealthWorker.tsx, and src/pages/RegisterFacilityAdmin.tsx.

OTP, profile-photo, and role-selection dialogs support the identity/onboarding journey: src/components/VerifyOTPModal.tsx, src/components/PhotoOnboardingModal.tsx, src/components/ui/RoleSelectionModal.tsx.

Role-Specific Care Workflows

Dashboards are the principal operational views, tailored to each actor:

• Mother self-service, pregnancy status, facility discovery/booking: src/components/mother/ModernMotherDashboard.tsx, src/components/mother/PregnancyJourneyTracker.tsx, src/components/mother/FacilityBookingCard.tsx

• CHW caseload and mother monitoring: src/components/chw/EnhancedCHWDashboard.tsx, src/components/chw/CHWProfile.tsx

• Nurse supervisory workflow: src/components/nurse/EnhancedNurseDashboard.tsx, src/components/nurse/NurseProfile.tsx

• Facility operations: src/components/facility/FacilityDashboard.tsx

Shared navigation/layout components establish the authenticated application frame: src/components/layout/Layout.tsx, src/components/layout/Navigation.tsx, src/components/layout/Sidebar.tsx.

Service and API Boundary

Domain services encapsulate calls to the backend, with common client behavior in src/lib/apiClient.ts. Major care-domain boundaries include:

• Mother records and check-ins: src/services/motherService.ts, src/services/checkinService.ts

• CHW assignment and escalation: src/services/assignmentService.ts, src/services/escalationService.ts

• Facility appointments and facility escalations: src/services/appointmentService.ts, src/services/facilityAppointmentService.ts, src/services/facilityEscalationService.ts

• Supporting clinical data: src/services/nutritionService.ts, src/services/weightService.ts, src/services/ultrasoundService.ts

The primary flow is UI/dashboard → domain service → apiClient → FastAPI/PostgreSQL, with responses driving role-specific state and presentation.

Real-Time Notifications and External Services

Socket lifecycle/state is centralized in src/contexts/SocketContext.tsx, backed by src/lib/socketClient.ts; consumers use src/hooks/useSocket.ts and facility-specific src/hooks/useFacilitySocket.ts. This is the real-time boundary for alerts and workflow updates, alongside src/services/notificationService.ts and src/components/ConnectionBanner.tsx.

Firebase is separately integrated through src/lib/firebaseClient.ts; the browser push worker is public/firebase-messaging-sw.js. This implies Firebase Cloud Messaging for push notification delivery, while sockets serve live in-app updates.

UI and Deployment Boundaries

Reusable accessible UI primitives are housed under src/components/ui/, while responsive behavior is concentrated in src/hooks/use-mobile.tsx, src/components/ui/HamburgerButton.tsx, and src/components/ui/MobileMenuPanel.tsx. Build/runtime configuration is Vite-based: vite.config.ts, package.json, and tailwind.config.ts. CI and security automation are defined in .github/workflows/ci.yml and .github/workflows/security.yml.