How anmol8070/mulkmed works
This is a Laravel healthcare platform with patient and tourist APIs, doctor and appointment management, an admin portal, and health-service integrations. A central user journey is finding a doctor and managing an appointment, with separate tourist-appointment, AI health analysis, and social-content capabilities. The graph also retains documented reels, chatbot, reminders, and payment capabilities. Source excerpts establish several model and service relationships; route dispatch and unsampled subsystems are not assumed, so uncertain entry links are dashed.
Main entry points: Appointments.php Appointments · UsersController.php Patient API · SenoclockAiService.php Health AI Service · Doctors.php Doctor Records
Components 23
Access and Admin
- API Routing
routes/v1/api.php - Web Routing
routes/web.php - Patient API
app/Http/Controllers/v1/UsersController.php - Doctor Management
app/Http/Controllers/DoctorController.php - Care Finder Admin
app/Http/Controllers/SMOController.php
Care and Appointments
- Doctor Records
app/Models/Doctors.php - Appointments
app/Models/Appointments.php - User Records
app/Models/Users.php - Patient Profiles
app/Models/AddedPatients.php - Doctor Identity
app/Models/Doctor.php
Tourist Care
- Tourist API
app/Http/Controllers/v2/TouristController.php - Tourist Appointments
app/Models/TouristAppointments.php
Health Intelligence
- Health AI Service
app/Services/SenoclockAiService.php - Biomarker Analysis
app/Services/LabReportBiomarkerAnalyzerService.php - Senoclock Service
app/Services/SenoclockService.php - Vital Records
app/Models/AI_Vital.php
Platform Features
- Reels
app/Http/Controllers/ReelController.php - Appointment Reminders
app/Models/AppointmentReminders.php - Shared Functions
app/Models/GlobalFunction.php
Other components
- Patient
- Admin User
- Health API
- Payment Gateway
Connections 26
- Patient → API Routing: requests
- Admin User → Web Routing: uses portal
- API Routing → Patient API: routes to
- Web Routing → Doctor Management: routes to
- Web Routing → Care Finder Admin: routes to
- Patient API → Appointments: queries
app/Http/Controllers/v1/UsersController.php - Patient API → Doctor Records: queries
app/Http/Controllers/v1/UsersController.php - Patient API → User Records: queries
app/Http/Controllers/v1/UsersController.php - Patient API → Patient Profiles: queries
app/Http/Controllers/v1/UsersController.php - Doctor Management → Appointments: queries
app/Http/Controllers/DoctorController.php - Doctor Management → Doctor Records: queries
app/Http/Controllers/DoctorController.php - Doctor Records → Doctor Identity: loads identity
app/Models/Doctors.php - Appointments → User Records: relates user
app/Models/Appointments.php - Appointments → Doctor Records: relates doctor
app/Models/Appointments.php - Appointments → Patient Profiles: relates patient
app/Models/Appointments.php - User Records → Patient Profiles: lists patients
app/Models/Users.php - Tourist API → Tourist Appointments: queries
app/Http/Controllers/v2/TouristController.php - Health AI Service → Health API: sends requests
app/Services/SenoclockAiService.php - Health AI Service → Biomarker Analysis: uses analyzer
app/Services/SenoclockAiService.php - Health AI Service → Senoclock Service: uses service
app/Services/SenoclockAiService.php - Health AI Service → Vital Records: stores results
app/Services/SenoclockAiService.php - Shared Functions → Appointment Reminders: uses reminders
app/Models/GlobalFunction.php - Patient → Reels: views content
- Patient → Health AI Service: uses health bot
- Appointments → Appointment Reminders: notifies
- Patient → Payment Gateway: pays