How dhvanil-pansuriya/healthstream works
Project type and purpose
• It supports four user roles (Patient, Doctor, Assistant, Sudo-Admin) each with its own portal, plus shared pages (index.php, signup.php, navbar.php, logout.php).
• It uses Bootstrap (CSS/JS), custom JS (app.js, bot.js), and a MySQL dump (healthstream.sql) for data storage.
File structure
• Top-level files & folders:
• config.php – central configuration (database credentials, session setup)
• DataBase/healthstream.sql – MySQL schema and seed data
• css/, js/, fonts/ – static assets for styling and client-side behavior
• signup.php, index.php, navbar.php, logout.php – shared entry points and UI
• Role-specific directories (MVC-lite):
• Patient/, Doctor/, Assistant/, Sudo-Admin/ – each contains index.php (dashboard), navbar.php, logout.php, plus role-specific actions (e.g., myPatient.php, removeUser.php)
• No explicit “models” or “controllers” folders; logic is embedded in each page.
• No external microservices—this is a single monolithic PHP application.
README
• README only contains the project name “HealthStream,” so there are no additional architectural clues beyond the folder layout.
Critical details
• Four user-role modules distinctly.
• Shared components: config.php, navbar.php, logout.php.
• Single database and its tables (users, patients, doctors, appointments, etc.).