How boscine/mediq works
MediQ is a healthcare staff portal with authentication and role-specific administration and doctor workspaces. The web routing establishes the user flow: staff sign in, then reach an authorized role area; doctors manage appointments, patients, schedules, visit history, and profiles, while administrators oversee accounts, specialties, audit logs, and settings. Session services mediate domain state and API access. The README is empty, and several pages and integrations are represented only by the tree or SOURCE INDEX, so their internal connections are omitted where not evidenced.
Main entry points: app.routes.ts Application routing · supabase.service.ts Supabase client · admin-session.ts Admin session · doctor-session.ts Doctor session
Components 21
Entry and authentication
- Application routing
mediqweb/mediqweb-fe/src/app/app.routes.ts - Staff login
mediqweb/mediqweb-fe/src/app/auth/pages/staff-login/staff-login.ts - Account signup
mediqweb/mediqweb-fe/src/app/auth/pages/auth-signup/auth-signup.ts - Authentication state
mediqweb/mediqweb-fe/src/app/core/api/auth.service.ts
Administration
- Admin routing
mediqweb/mediqweb-fe/src/app/admin/admin.routes.ts - Admin pages
mediqweb/mediqweb-fe/src/app/admin/pages - Admin session
mediqweb/mediqweb-fe/src/app/admin/admin-session.ts - Admin analytics
mediqweb/mediqweb-fe/src/app/admin/admin.analytics.ts - Admin models
mediqweb/mediqweb-fe/src/app/admin/admin.models.ts
Doctor workspace
- Doctor routing
mediqweb/mediqweb-fe/src/app/doctor/doctor.routes.ts - Doctor pages
mediqweb/mediqweb-fe/src/app/doctor/pages - Doctor session
mediqweb/mediqweb-fe/src/app/doctor/doctor-session.ts - Schedule editor
mediqweb/mediqweb-fe/src/app/doctor/pages/doctor-schedule/doctor-schedule.ts - Schedule date rules
mediqweb/mediqweb-fe/src/app/doctor/doctor.dates.ts - Doctor models
mediqweb/mediqweb-fe/src/app/doctor/doctor.models.ts
Shared services
- Patient API gateway
mediqweb/mediqweb-fe/src/app/core/api/http-patient-gateway.ts - Admin API gateway
mediqweb/mediqweb-fe/src/app/core/api/http-admin-gateway.ts - Supabase client
mediqweb/mediqweb-fe/src/app/core/api/supabase.service.ts - Toast service
mediqweb/mediqweb-fe/src/app/core/services/toast.service.ts
Other components
- Staff user
- Supabase
Connections 18
- Staff user → Application routing: opens portal
- Application routing → Staff login: routes to
mediqweb/mediqweb-fe/src/app/app.routes.ts - Application routing → Account signup: routes to
mediqweb/mediqweb-fe/src/app/app.routes.ts - Application routing → Admin routing: loads admin
mediqweb/mediqweb-fe/src/app/app.routes.ts - Application routing → Doctor routing: loads doctor
mediqweb/mediqweb-fe/src/app/app.routes.ts - Admin routing → Admin pages: loads pages
mediqweb/mediqweb-fe/src/app/admin/admin.routes.ts - Doctor routing → Doctor pages: loads pages
mediqweb/mediqweb-fe/src/app/doctor/doctor.routes.ts - Admin session → Admin API gateway: requests data
mediqweb/mediqweb-fe/src/app/admin/admin-session.ts - Admin session → Patient API gateway: requests data
mediqweb/mediqweb-fe/src/app/admin/admin-session.ts - Admin session → Toast service: records notices
mediqweb/mediqweb-fe/src/app/admin/admin-session.ts - Schedule editor → Doctor session: updates availability
mediqweb/mediqweb-fe/src/app/doctor/pages/doctor-schedule/doctor-schedule.ts - Schedule editor → Schedule date rules: uses date rules
mediqweb/mediqweb-fe/src/app/doctor/pages/doctor-schedule/doctor-schedule.ts - Doctor session → Patient API gateway: requests records
mediqweb/mediqweb-fe/src/app/doctor/doctor-session.ts - Doctor session → Schedule date rules: uses date rules
mediqweb/mediqweb-fe/src/app/doctor/doctor-session.ts - Admin API gateway → Supabase client: uses client
- Patient API gateway → Supabase client: uses client
mediqweb/mediqweb-fe/src/app/core/api/http-patient-gateway.ts - Authentication state → Supabase client: reads auth
mediqweb/mediqweb-fe/src/app/core/api/auth.service.ts - Supabase client → Supabase: connects