A web-based scheduling platform designed to improve patient and administrator experiences in environments where technical infrastructure may be limited.
- Video walkthrough (March 12, 2026): YouTube Demo
- To try the latest interactive version of the demo, email:
fteodoro803@gmail.com
Admin Queue
|
Patient Queue (Mobile)
|
Many clinics and service centers still run scheduling and queueing with fragmented tools (paper lists, spreadsheets, or ad-hoc apps). That leads to missed updates, avoidable wait time, and friction between front-desk workflows and patient expectations.
This project aims to provide a practical, modern baseline for:
- Faster check-in and queue visibility
- Cleaner day-to-day operations for staff
- Real-time updates across the app without manual refreshes
- A mobile-friendly experience that still works in constrained environments
- Reactive Data Sync: Utilising Meteor to enable instant client-server synchronisation.
- Mobile-First Design: Optimised for low-bandwidth environments to ensure accessibility for all users.
- Real-Time Availability: Dynamic scheduling updates to prevent double-booking and reduce wait times.
- Human-Centered Simplicity: Clear, role-oriented screens for admins and patients.
- Queue workflow management
- Provider, service, and patient record management
- Role-based navigation (admin and patient flows)
- Dashboard views and operational stats
- Configurable app settings and theme controls
- React 18 + TypeScript
- React Router 6
- Tailwind CSS 4 + DaisyUI
- Recharts (data visualisation)
- Meteor (publications, methods, and reactive data layer)
- MongoDB (via Meteor collections)
- ESLint + TypeScript ESLint
- Prettier
- Mocha + Chai (Meteor test driver)
client/ # Client entry and styles
imports/api/ # Collections and Meteor methods
imports/ui/ # React UI: pages, components, navigation
imports/contexts/ # Shared client context providers
imports/utils/ # Utility modules
server/ # Server startup and demo seed wiring
tests/ # Unit + integration tests
npm run screenshots:localis the one-command flow for local development: start app, wait, capture all configured screenshots, stop app.npm run screenshotscaptures desktop screenshots.npm run screenshots:mobilecaptures mobile screenshots.npm run screenshotsandnpm run screenshots:mobileexpect the app to already be running athttp://127.0.0.1:3000(orSCREENSHOT_BASE_URL).