How brian-munene/mt_hims works
Avocent is a clinic-care management application with a Next.js dashboard and Django API. Staff authenticate, then work across patient records, bookings and clinical workflows, with laboratory, pharmacy and billing as distinct operational stages. The booking service excerpt specifically supports queue/status handling and consultation creation, then generates invoice lines from consultation, lab and prescription data. The tree also documents administration, compliance, telemedicine, notifications and audit capabilities. The README is empty; unsampled subsystems are shown as capabilities, without asserting internal call paths.
Main entry points: services.py Booking and queues · (dashboard) Clinic dashboard · page.tsx Login flow · auth Auth routes
Components 21
Web application
- Clinic dashboard
avocent-frontend/src/app/(dashboard) - Login flow
avocent-frontend/src/app/(auth)/login/page.tsx - Auth routes
avocent-frontend/src/app/api/auth - API proxy
avocent-frontend/src/app/api/proxy/[...path]/route.ts
Identity and access
- Users and roles
avocent-backend/users
Care operations
- Patient records
avocent-backend/patients - Booking and queues
avocent-backend/booking/services.py - Encounters
avocent-backend/encounters - Clinical records
avocent-backend/clinical - Laboratory
avocent-backend/laboratory - Pharmacy
avocent-backend/pharmacy - Telemedicine
avocent-backend/telemedicine
Clinic operations
- Billing
avocent-backend/billing - Payments
avocent-backend/payments - Compliance
avocent-backend/compliance - Clinic administration
avocent-backend/organization - Notifications
avocent-backend/notifications - Audit trail
avocent-backend/audit
Backend platform
- Django API
avocent-backend/avocent_backend/urls.py - Application database
Other components
- Clinic staff
Connections 15
- Clinic staff → Login flow: signs in
- Clinic staff → Clinic dashboard: uses
- Login flow → Auth routes: submits credentials
- Auth routes → Users and roles: authenticates
- Clinic dashboard → API proxy: requests data
- API proxy → Django API: forwards API calls
- Booking and queues → Application database: reads and writes
- Booking and queues → Encounters: creates encounter
- Booking and queues → Laboratory: reads lab items
- Booking and queues → Pharmacy: reads prescription items
- Booking and queues → Billing: creates invoice lines
- Patient records → Application database: reads and writes
- Users and roles → Application database: reads and writes
- Telemedicine → Application database: stores chat state
- Audit trail → Application database: records events