How adlmks/qtime works
QTime is a patient intake and appointment-management web application. The main patient journey starts at the home page, proceeds through patient registration, and then reaches appointment booking and its success page. Administrators have a separate dashboard for reviewing and managing appointment status; appointment actions also support SMS notifications. The graph reflects the sampled registration and action code; several route and form implementations were not sampled, so uncertain caller-to-action links are omitted.
Main entry points: RegisterForm.tsx Registration form · appointment.actions.ts Appointment actions · app/page.tsx Home page · new-appointment/page.tsx Booking page
Components 15
Patient intake
- Home page
app/page.tsx - Patient form
components/forms/PatientForm.tsx - Registration page
app/patients/[userId]/register/page.tsx - Registration form
components/forms/RegisterForm.tsx
Appointments
- Booking page
app/patients/[userId]/new-appointment/page.tsx - Appointment form
components/forms/AppointmentForm.tsx - Booking success
app/patients/[userId]/new-appointment/success/page.tsx - Appointment actions
lib/actions/appointment.actions.ts
Administration
- Admin dashboard
app/admin/page.tsx - Appointment table
components/table/DataTable.tsx
Services and validation
- Patient actions
lib/actions/patient.actions.ts - Form validation
lib/validation.ts
Other components
- Patient
- Appwrite
- SMS messaging
Connections 12
- Patient → Home page: opens
- Home page → Patient form: renders
- Registration page → Registration form: renders
- Registration form → Patient actions: registers patient
- Registration form → Booking page: navigates
- Booking page → Appointment form: renders
- Appointment actions → Appwrite: reads and writes
- Appointment actions → SMS messaging: sends notification
- Appointment actions → Admin dashboard: revalidates
- Admin dashboard → Appointment table: renders
- Registration form → Form validation: validates with
- Appointment form → Form validation: validates with