Client system · Team of 5
Preparing for clinic rolloutDorotheo Dental Clinic Management System
March 2025 – March 2026
A multi-portal platform for a real dental practice — patients, staff, and the clinic owner — covering scheduling, clinical records, billing, inventory, and an AI chat assistant, with every change to patient data audited.
- Led a five-person team as Project Manager and full-stack developer
- Django REST backend: 26-model schema, 27 serializers, append-only audit trail
- Deployed across Vercel, Railway, and Azure
- Django
- Django REST Framework
- PostgreSQL
- Supabase
- Next.js 15
- TypeScript
- shadcn/ui
- Redis
- Resend
- Sentry
- Azure Blob Storage
- Docker
Role
Project Manager & Full-Stack Developer
What I did
Project management
- Led a team of five developers
- Wrote sections of the Software Requirements Specification: assumptions and dependencies, design constraints, and external interfaces
Backend and security
- Initialized the Django REST Framework project: custom user model for four roles, middleware stack (CORS, auditing, security), and a customized Django admin with an audit dashboard
- Designed a 26-model schema across 36 migrations, with multi-clinic support in every model
- Built 27 serializers with custom validation and 9 management commands for operations and compliance
- Moved appointment status logic into an 8-state state-machine service and centralized booking rules in a validation service
- JWT authentication and role-based access control on every API surface; rate-limited authentication, strong password validation, token-based password reset, and frontend session timeout
- Append-only audit trail designed around HIPAA audit requirements: pre/post-save signal handlers on 8 models, read-access decorators, and an asynchronous logging engine
Clinical, scheduling, and billing
- Interactive 32-tooth SVG dental chart with per-tooth status tracking
- Treatment plans, dental records, clinical document and X-ray uploads, and patient record export
- Staff and dentist availability, blocked time slots, and two-way appointment change requests
- Invoicing: 3-step invoice wizard, multi-invoice payment allocation, and PDF invoices generated with WeasyPrint
- Owner analytics dashboard built on ORM aggregation, and inventory management with low-stock alerts
- Query and pagination optimization on key pages
Frontend (shared roughly equally with one other developer)
- Co-built the Next.js 15 App Router frontend in TypeScript with shadcn/ui: 47 page routes across the patient, staff, and owner portals
- Three role-based dashboard layouts, role-based routing, and a clinic selector for multi-location use
- Centralized API client with 80+ typed methods and TypeScript types for every API entity
- Notification bell with 30-second polling, a public landing page, and patient self-registration
Integrations and deployment
- Frontend on Vercel; Django backend deployed three ways — Vercel serverless (WSGI handler), Railway (Nixpacks, Procfile, release scripts), and Azure Web Apps — plus a Dockerfile for containerized deployment
- Transactional email through a custom Django email backend for the Resend API, with SPF, DKIM, and DMARC domain authentication records
- Sentry error monitoring and performance tracing, plus production environment configuration and logging
- Redis caching with an in-memory fallback; media on Azure Blob Storage with per-file-type cache policies
- Gemini API for the clinic's chatbot: moved it to the paid tier on Google Cloud free credits when the free tier kept running out, and configured it over SSH on the Azure-hosted backend
Lesson learned: Response times depended heavily on the hosting tier — free tiers were noticeably slower than Azure — so performance claims must be tied to where the system actually runs.