How irhamzakki/midcare works
MidCare is a role-based mental-health screening and patient-management web app. Its central workflow presents a questionnaire, submits responses for risk clustering, persists screening and patient records, and returns a result; patients can then view history and recovery recommendations. Admin and psychologist branches cover content and clinical oversight. The screening controller excerpt supports the prediction and persistence links shown; other role capabilities are documented in the README, while their detailed routes and controller wiring were not sampled.
Main entry points: ScreeningController.php Screening Handler · database.php Application Database · DashboardController.php Patient Dashboard · Psikolog Psychologist Operations
Components 22
Screening & Results
- Screening Form
resources/views/screening.blade.php - Screening Handler
app/Http/Controllers/ScreeningController.php - K-Means Predictor
Kmeans/predict.py - Screening Records
app/Models/Screening.php - Response Features
app/Models/FiturPengguna.php - Cluster Results
app/Models/HasilClustering.php - Result History
app/Http/Controllers/Pengguna/HasilController.php
Clinical Operations
- Patient Records
app/Models/Pasien.php - Patient Dashboard
app/Http/Controllers/Pasien/DashboardController.php - Psychologist Operations
app/Http/Controllers/Psikolog - Admin Management
app/Http/Controllers/Admin - Patient Screens
resources/views/Pasien - Psychologist Screens
resources/views/Psikolog - Admin Screens
resources/views/Admin
Content & Education
- Articles
app/Models/Artikel.php - Education Materials
app/Models/Edukasi.php - Public Content
resources/views
Access & Application
- Web Routes
routes/web.php - User Accounts
app/Models/User.php - Registration
app/Http/Controllers/Auth/RegisteredUserController.php - Application Database
config/database.php
Other components
- Respondent
Connections 35
- Respondent → Web Routes: opens
- Web Routes → Screening Handler: dispatches
- Screening Handler → Screening Form: renders
- Respondent → Screening Form: answers
- Screening Form → Screening Handler: submits
- Screening Handler → K-Means Predictor: invokes
- Screening Handler → Screening Records: writes
- Screening Handler → Response Features: writes
- Screening Handler → Cluster Results: writes
- Screening Handler → Patient Records: creates
- Screening Handler → Application Database: persists via
- Patient Dashboard → Cluster Results: reads
- Patient Dashboard → Articles: counts
- Patient Dashboard → Education Materials: counts
- Patient Dashboard → Patient Screens: renders
- Result History → Cluster Results: reads and links
- Result History → Application Database: updates ownership
- Psychologist Operations → Screening Records: reviews
- Psychologist Operations → Response Features: analyzes
- Psychologist Operations → Patient Records: monitors
- Psychologist Operations → Psychologist Screens: renders
- Admin Management → Admin Screens: renders
- Admin Management → Articles: manages
- Admin Management → Education Materials: manages
- Registration → User Accounts: creates
- Registration → Patient Records: creates for patients
- Registration → Web Routes: redirects to role pages
- Articles → Application Database: persists via
- Education Materials → Application Database: persists via
- Screening Records → Application Database: persists via
- Response Features → Application Database: persists via
- Cluster Results → Application Database: persists via
- Patient Records → Application Database: persists via
- User Accounts → Application Database: persists via
- Public Content → Respondent: presents resources