How abdulhamid109/careus-backend works
Careus Backend is an Express API for guardian-managed patient care, medication schedules, reports, and phone-based medication check-ins. The main workflow is a client request handled by the API routes, which read or update Mongoose-backed records; scheduled medication calls use Twilio and IVR responses update call-related state. The route excerpt is partial, so the graph includes only evidenced route-to-model interactions and documented-in-code integrations. Although a database connector exists, the visible server entry point does not call it.
Main entry points: apiroutes.js API routes · index.js Server entry · userModal.js Guardian model · patientModal.js Patient model
Components 13
API server
- Server entry
index.js - API routes
routes/apiroutes.js
Care records
- Guardian model
models/userModal.js - Patient model
models/patientModal.js - Report model
models/reportsModal.js
Medication reminders
- Slot model
models/slotModal.js - Tablet model
models/tabletsModal.js - IVR model
models/IVRModal.js - Schedule jobs
routes/apiroutes.js
External services
- Twilio voice
- ImageKit storage
Other components
- API client
- MongoDB
Connections 18
- API client → Server entry: sends requests
- Server entry → API routes: mounts API
- API routes → Guardian model: queries guardian
- API routes → Patient model: manages patients
- API routes → Report model: saves reports
- API routes → Slot model: manages slots
- API routes → Tablet model: manages medication
- API routes → IVR model: reads call records
- API routes → Schedule jobs: schedules calls
- API routes → Twilio voice: places voice calls
- Twilio voice → API routes: posts call events
- API routes → ImageKit storage: uploads reports
- Guardian model → MongoDB: persists guardian
- Patient model → MongoDB: persists patient
- Report model → MongoDB: persists report
- Slot model → MongoDB: persists slots
- Tablet model → MongoDB: persists schedules
- IVR model → MongoDB: persists call state