Health and Wellness Patient Portal Development
Budget: $8 – $15 USD
I need a web developer to expand the web presence of a premium health and wellness brand with a secure, browser-based patient portal. The core workflow is as follows:
1. A patient signs up through a straightforward username-and-password flow (two-factor or SSO may follow later, but v1 sticks to basic credentials).
2. They upload blood-test PDFs or CSVs, fill in structured medical-history forms, and optionally paste or import their food logs.
3. The system pushes that raw information to the Claude API, receives deep-dive interpretations, and stores both the source data and the generated insights. The API will also generate a patient report.
4. Patients (and me, as an administrator) land on an elegant, interactive dashboard that shows trends, flags critical markers, and lets them download a polished clinical report.
Key pieces I want you to own:
• Secure front-end and back-end architecture (React, Vue, or similar on the front; Node, Django, or another modern stack on the back—your call, but security best practices are non-negotiable).
• Seamless Claude API integration with sensible error handling and logging.
• Data model that supports the three chosen data domains—blood tests, patient medical history, food logs—plus the flexibility to add more later.
• Role-based access limited to Patients and Administrators in this release.
• Responsive design that feels premium on desktop, tablet, and mobile.
• Deployment guidance (Docker or another reproducible approach) so I can spin up staging and production instances quickly.
• Seamless integration into payment gateway.
Acceptance criteria
• Patient can register, verify e-mail, log in, and reset password.
• Data upload interfaces accept the three specified data types and show server-side validation feedback.
• Claude API calls complete within an acceptable timeframe and store results securely.
• Dashboard loads in under two seconds on standard broadband and renders interactive charts without console errors.
• OWASP top-ten vulnerabilities addressed; basic penetration test passes.
• Clear, commented codebase with a README covering local setup, environment variables, and deployment steps.
I've included a sample set of web pages for you for reference ideas.
1. A patient signs up through a straightforward username-and-password flow (two-factor or SSO may follow later, but v1 sticks to basic credentials).
2. They upload blood-test PDFs or CSVs, fill in structured medical-history forms, and optionally paste or import their food logs.
3. The system pushes that raw information to the Claude API, receives deep-dive interpretations, and stores both the source data and the generated insights. The API will also generate a patient report.
4. Patients (and me, as an administrator) land on an elegant, interactive dashboard that shows trends, flags critical markers, and lets them download a polished clinical report.
Key pieces I want you to own:
• Secure front-end and back-end architecture (React, Vue, or similar on the front; Node, Django, or another modern stack on the back—your call, but security best practices are non-negotiable).
• Seamless Claude API integration with sensible error handling and logging.
• Data model that supports the three chosen data domains—blood tests, patient medical history, food logs—plus the flexibility to add more later.
• Role-based access limited to Patients and Administrators in this release.
• Responsive design that feels premium on desktop, tablet, and mobile.
• Deployment guidance (Docker or another reproducible approach) so I can spin up staging and production instances quickly.
• Seamless integration into payment gateway.
Acceptance criteria
• Patient can register, verify e-mail, log in, and reset password.
• Data upload interfaces accept the three specified data types and show server-side validation feedback.
• Claude API calls complete within an acceptable timeframe and store results securely.
• Dashboard loads in under two seconds on standard broadband and renders interactive charts without console errors.
• OWASP top-ten vulnerabilities addressed; basic penetration test passes.
• Clear, commented codebase with a README covering local setup, environment variables, and deployment steps.
I've included a sample set of web pages for you for reference ideas.