How mohammedaffan710/hrms works
Careline is a patient-and-clinician telehealth application. Users register or sign in, find clinicians and book appointments; authenticated users then manage appointments and records or enter chat/video consultations. The frontend routes these experiences and calls a Django API; the backend models users, availability, appointments, consultations and clinical records. The source excerpts establish frontend API usage, view-to-model/serializer references, and WebSocket routing. Some implementation details—especially chat and health-information pages—were not sampled, so their internal links are omitted.
Main entry points: App.js Application routes · api.js HTTP API client · models.py Care domain models · VideoConsult.js Video consultation
Components 19
Careline frontend
- Application routes
healthcare_frontend/src/App.js - Sign-in and registration
healthcare_frontend/src/pages/Register.js - Authentication state
healthcare_frontend/src/contexts/AuthContext.js - Language context
healthcare_frontend/src/contexts/LanguageContext.js - HTTP API client
healthcare_frontend/src/services/api.js
Care access
- Clinician search and booking
healthcare_frontend/src/pages/Telemedicine.js - Appointments and profile
healthcare_frontend/src/components/AppointmentList.js - Video consultation
healthcare_frontend/src/pages/VideoConsult.js - Chat consultation
healthcare_frontend/src/pages/ChatConsult.js - Health awareness
healthcare_frontend/src/pages/HealthAwareness.js - Clinician dataset
healthcare_frontend/src/pages/Dataset.js
Backend services
- API views
healthcare_backend/api/views.py - Request and response serializers
healthcare_backend/api/serializers.py - WebSocket routing
healthcare_backend/api/routing.py - Consultation socket
healthcare_backend/api/consumers.py
Clinical records
- Care domain models
healthcare_backend/api/models.py - Application database
Other components
- Patient or clinician
- WebSocket clients
Connections 26
- Patient or clinician → Application routes: uses
healthcare_frontend/src/App.js - Application routes → Sign-in and registration: routes to
healthcare_frontend/src/App.js - Application routes → Clinician search and booking: routes to
healthcare_frontend/src/App.js - Application routes → Appointments and profile: routes to
healthcare_frontend/src/App.js - Application routes → Video consultation: routes to
healthcare_frontend/src/App.js - Application routes → Chat consultation: routes to
healthcare_frontend/src/App.js - Application routes → Health awareness: routes to
healthcare_frontend/src/App.js - Application routes → Clinician dataset: routes to
healthcare_frontend/src/App.js - Application routes → Authentication state: provides
healthcare_frontend/src/App.js - Application routes → Language context: provides
healthcare_frontend/src/App.js - Sign-in and registration → Authentication state: authenticates through
healthcare_frontend/src/pages/Register.js - Authentication state → HTTP API client: calls
healthcare_frontend/src/contexts/AuthContext.js - Clinician search and booking → HTTP API client: requests care data
healthcare_frontend/src/pages/Telemedicine.js - Appointments and profile → HTTP API client: loads appointments
healthcare_frontend/src/components/AppointmentList.js - Video consultation → HTTP API client: manages consultation
healthcare_frontend/src/pages/VideoConsult.js - Chat consultation → HTTP API client: uses consultation API
healthcare_frontend/src/pages/ChatConsult.js - Clinician dataset → HTTP API client: loads data
healthcare_frontend/src/pages/Dataset.js - HTTP API client → API views: sends HTTP requests
healthcare_frontend/src/services/api.js - API views → Request and response serializers: serializes responses
healthcare_backend/api/views.py - API views → Care domain models: reads and writes
healthcare_backend/api/views.py - Request and response serializers → Care domain models: serializes models
healthcare_backend/api/serializers.py - Care domain models → Application database: persists domain data
- WebSocket clients → WebSocket routing: opens consultation channel
- WebSocket routing → Consultation socket: routes to
healthcare_backend/api/routing.py - Consultation socket → Care domain models: persists chat messages
healthcare_backend/api/consumers.py - Video consultation → WebSocket clients: signals consultation