Patient-Centric Medical Web Platform

I have the core concept and a technical outline for a new medical platform that puts patients first, and now I need a full-stack developer to turn it into a production-ready application.

Platform focus
The entire experience must revolve around patients—everything from the landing pages to each dashboard screen should guide them effortlessly toward the information or action they need. In addition to the features outlined below, patients will be encouraged to stay engaged through an integrated blog section that delivers health tips and practice news.

Stack and architecture
• Back-end logic is planned in PHP for traditional server tasks and Node.js for any real-time components that benefit from non-blocking I/O.
• A secure SQL database needs to be designed, populated, and tuned to store patient records, appointment data, doctor profiles, service catalogs, and log data. Normalization, strict role-based access, and encryption at rest are essential.
• I expect neat separation of concerns, clean API endpoints, and code that can be containerized for CI/CD.

Core functionality
• Online booking and calendar management that respects each doctor’s availability.
• Service catalog pages that remain editable from an admin panel.
• Doctor profile management with photo upload, specialty tags, and schedule links.
• Strong validation, JWT-based authentication, and rate limiting to keep the platform safe and fast.
• A responsive front end so patients can enjoy the site equally on desktop or mobile browsers.
• Central admin panel for staff to oversee patient data, appointments, and content.

Performance & security goals
Pages should load in under two seconds on a 4G mobile connection. All sensitive data needs field-level validation, hashed credentials, and prepared SQL statements to eliminate injection risk. Automated testing for critical flows is expected.

Deliverables
1. Source code (PHP, Node.js, SQL schema, and any build scripts).
2. Database migration files and seed data.
3. Brief deployment guide for a standard Ubuntu server (Nginx + PM2 or similar).
4. README covering environment variables, build steps, and admin panel credentials for testing.
5. Demo instance or video walkthrough proving every listed feature is operational.

Acceptance criteria
• Successful patient sign-up, secure login, and profile edit flow.
• Booking an appointment reflects instantly in both the patient dashboard and admin calendar.
• Blog posts render with clean URLs and update through the admin panel without downtime.
• OWASP ZAP or equivalent scan produces zero high-severity findings.
• Lighthouse performance score ≥ 90 on mobile.

If you have demonstrable experience building HIPAA-aware or similarly regulated platforms and can hit these benchmarks, let’s discuss timelines and milestones.