evaldoc 1.0.0

package/docs/DOCTOR_TUTORIAL.md

@@ -0,0 +1,467 @@
+# EvalDoc Doctor Tutorial Guide
+
+## 🎯 Welcome, Doctor!
+
+This guide will help you get started with EvalDoc and make the most of the platform to serve your patients efficiently.
+
+---
+
+## 📋 Table of Contents
+
+1. [Getting Started](#getting-started)
+2. [Setting Up Your Profile](#setting-up-your-profile)
+3. [Sharing Your Link](#sharing-your-link)
+4. [Managing Your Inbox](#managing-your-inbox)
+5. [Understanding AI Responses](#understanding-ai-responses)
+6. [Replying to Patients](#replying-to-patients)
+7. [Analytics Dashboard](#analytics-dashboard)
+8. [Best Practices](#best-practices)
+9. [Troubleshooting](#troubleshooting)
+
+---
+
+## 1. Getting Started
+
+### Step 1: Sign Up
+
+1. Visit `https://evaldoctor.ai/app`
+2. Click **"Create Account"**
+3. Enter your email and create a password
+4. Click **"Create account"** button
+
+### Step 2: Sign In
+
+1. Enter your email and password
+2. Click **"Sign in"**
+3. You'll be taken to the onboarding screen
+
+---
+
+## 2. Setting Up Your Profile
+
+### Required Information
+
+**Display Name**: Your professional name (e.g., "Dr. Sarah Amina")
+
+**Specialty**: Your medical specialty (e.g., "Family Medicine", "Pediatrics")
+
+**Country**: Your practice location (e.g., "United States", "United Kingdom", "Nigeria")
+
+**Handle**: Your unique URL identifier (e.g., "dr-sarah-amina")
+- This becomes your shareable link: `evaldoctor.ai/dr-sarah-amina`
+- Must be unique across the platform
+- Use only letters, numbers, and hyphens
+
+### Optional Branding
+
+**Welcome Message**: Custom greeting for your patients
+- Default: "Welcome. Choose a topic to get started."
+- Example: "Hello! I'm Dr. Sarah. How can I help you today?"
+
+**Brand Colors**:
+- Primary Color: Main accent color (default: teal)
+- Secondary Color: Secondary accent
+
+**Logo**: Upload your practice logo (coming soon)
+
+### Topics Configuration
+
+Select which topics your AI assistant can help with:
+
+- ✅ **Medication Information & Safety**: Questions about medications
+- ✅ **Appointments & Preparation**: Scheduling and prep info
+- ✅ **General Health Information**: Basic health education
+- ✅ **Clinic Services & Hours**: Your practice information
+- ✅ **Insurance & Billing FAQ**: Payment and insurance questions
+- ✅ **Post-Procedure Guidance**: Recovery instructions
+
+**Tip**: Start with all topics enabled, then refine based on your practice needs.
+
+### Profile Status
+
+- **Draft**: Your profile is not public yet
+- **Published**: Your link is active and patients can chat
+- **Suspended**: Temporarily disabled
+
+**Remember to set status to "Published" when ready!**
+
+---
+
+## 3. Sharing Your Link
+
+### Your Unique Link
+
+Once published, your link is:
+```
+https://evaldoctor.ai/your-handle
+```
+
+Example: `https://evaldoctor.ai/dr-sarah-amina`
+
+### Ways to Share
+
+#### 1. **WhatsApp**
+```
+Hi [Patient Name],
+
+You can now chat with my AI assistant 24/7 for quick health questions:
+https://evaldoctor.ai/dr-sarah-amina
+
+I review all conversations and will step in when needed.
+
+- Dr. Sarah
+```
+
+#### 2. **SMS**
+```
+Your doctor is now available 24/7 via AI assistant: evaldoctor.ai/dr-sarah-amina
+Dr. Sarah monitors all chats.
+```
+
+#### 3. **QR Code** (Coming Soon)
+- Download QR code from your dashboard
+- Print on business cards
+- Display in clinic waiting room
+- Add to appointment reminder cards
+
+#### 4. **Email Signature**
+```
+Dr. Sarah Amina, MD
+Family Medicine
+📱 Chat 24/7: evaldoctor.ai/dr-sarah-amina
+```
+
+#### 5. **Social Media**
+- Add to Facebook/Twitter bio
+- Share in patient groups
+- Post on clinic social media
+
+---
+
+## 4. Managing Your Inbox
+
+### Accessing Your Inbox
+
+1. Sign in at `https://evaldoctor.ai/app`
+2. Click **"Inbox"** in the navigation menu
+3. You'll see all patient conversations
+
+### Inbox Layout
+
+#### Left Sidebar: Conversation List
+- **Green name**: Patient identifier (name, email, or session)
+- **Gray text**: Last message preview
+- **Time**: How long ago (e.g., "2h ago", "3d ago")
+- **Badge**: "⚠️ Escalated" for urgent cases
+
+#### Right Panel: Conversation Detail
+- **Patient Info**: Name, email, phone (if provided)
+- **Message Count**: Number of messages in conversation
+- **Timestamp**: When conversation started
+- **Messages**: Full conversation history
+
+### Filtering Conversations
+
+Use the filter buttons at the top:
+
+- **All**: Show all conversations
+- **Escalated**: Only urgent cases flagged by AI
+- **Today**: Conversations from today
+- **This Week**: Last 7 days
+
+### Understanding Message Types
+
+- **👤 PATIENT**: Message from the patient
+- **🤖 AI ASSISTANT**: Response from the AI
+- **👨‍⚕️ YOU**: Your manual response (coming soon)
+
+### Color Coding
+
+- **Light Green Background**: Patient messages
+- **Gray Background**: AI responses
+- **Dark Green Background**: Your manual replies
+
+---
+
+## 5. Understanding AI Responses
+
+### What the AI Does
+
+✅ **Educational Information**
+- Explains medical concepts in simple terms
+- Provides general health guidance
+- Suggests when to seek care
+
+✅ **Red Flag Detection**
+- Identifies serious symptoms
+- Escalates urgent cases
+- Notifies you immediately
+
+✅ **Safe Boundaries**
+- Never diagnoses conditions
+- Never prescribes medications
+- Always includes disclaimers
+
+### AI Response Quality
+
+**Primary AI**: DeepSeek (better medical accuracy)
+**Fallback AI**: Google Gemini (if DeepSeek fails)
+
+The AI has been trained to:
+- Use simple, patient-friendly language
+- Be empathetic and supportive
+- Err on the side of caution
+- Encourage professional consultation
+
+### When AI Escalates
+
+The AI flags conversations when it detects:
+- Chest pain or pressure
+- Difficulty breathing
+- Severe bleeding
+- Loss of consciousness
+- Suicidal thoughts
+- Severe pain (8-10/10)
+- Allergic reactions
+
+**You'll see**: ⚠️ URGENT badge on the conversation
+
+### Example Conversations
+
+**Good AI Response:**
+```
+Patient: "What should I do about my child's fever?"
+
+AI: "For a child with fever:
+- Monitor temperature regularly
+- Keep them hydrated
+- Use a cool compress
+- Give them rest
+
+⚠️ Seek immediate care if:
+- Fever over 38.5°C (101.3°F)
+- Lasts more than 3 days
+- Child is very sleepy or irritable
+- Has trouble breathing
+
+This is educational information. For medication advice,
+please contact Dr. Sarah directly."
+```
+
+**AI Escalation:**
+```
+Patient: "I have severe chest pain"
+
+AI: "🚨 URGENT: Chest pain requires immediate medical attention.
+
+Please:
+1. Call emergency services NOW
+2. Do NOT wait
+3. This could be serious
+
+Dr. Sarah has been notified of this urgent message.
+
+⚠️ This is a medical emergency. Go to the nearest
+hospital or call emergency services immediately."
+```
+
+---
+
+## 6. Replying to Patients (Coming Soon)
+
+### When to Reply Manually
+
+- AI has escalated the conversation
+- Patient asks a specific question about your practice
+- You need to provide personalized medical advice
+- Patient requests an appointment
+- Follow-up on a recent visit
+
+### How to Reply
+
+1. Open the conversation in your inbox
+2. Scroll to the bottom
+3. Type your message in the reply box
+4. Click **"Send Reply"**
+
+Your reply will:
+- Show as "👨‍⚕️ YOU" in the conversation
+- Be marked with dark green background
+- Override AI for this conversation
+- Notify the patient (future feature)
+
+### Reply Best Practices
+
+✅ **Be Clear**: Use simple language
+✅ **Be Prompt**: Reply to urgent cases within 1 hour
+✅ **Be Professional**: Maintain doctor-patient boundaries
+✅ **Document**: Treat as part of medical record
+
+❌ **Don't**: Give detailed diagnoses via chat
+❌ **Don't**: Prescribe without proper consultation
+❌ **Don't**: Share sensitive info without verification
+
+---
+
+## 7. Analytics Dashboard
+
+### Accessing Analytics
+
+1. Sign in at `https://evaldoctor.ai/app`
+2. Click **"Analytics"** in the navigation
+
+### Key Metrics
+
+#### Summary Cards
+
+**Total Doctors**: Number of providers on platform
+**Active Doctors**: Published profiles
+**Total Conversations**: All chat sessions
+**Unique Patients**: Individual users served
+
+#### Doctor Performance Table
+
+View detailed stats:
+- **Conversations**: Total chat sessions
+- **Unique Patients**: Different users
+- **Messages**: Total message count
+- **Join Date**: When you signed up
+
+### Time Filters
+
+- All Time
+- Today
+- This Week
+- This Month
+- This Quarter
+
+### Using Analytics
+
+**Monitor Growth**: Track patient engagement
+**Identify Patterns**: See peak usage times
+**Measure Impact**: Conversations handled by AI
+**Plan Capacity**: Anticipate when manual replies needed
+
+---
+
+## 8. Best Practices
+
+### Setting Up
+
+✅ Complete your full profile
+✅ Upload a professional photo (coming soon)
+✅ Write a warm welcome message
+✅ Enable relevant topics for your practice
+✅ Set status to "Published"
+
+### Sharing Your Link
+
+✅ Add to all patient touchpoints
+✅ Include in appointment reminders
+✅ Mention during consultations
+✅ Share on social media
+✅ Print on business cards
+
+### Managing Conversations
+
+✅ Check inbox daily (at least once)
+✅ Respond to escalated cases within 1 hour
+✅ Review AI responses periodically
+✅ Reply manually when needed
+✅ Document significant conversations
+
+### Patient Communication
+
+✅ Set expectations: "AI handles routine, I handle medicine"
+✅ Clarify: "This is for education, not diagnosis"
+✅ Encourage: "I review all conversations"
+✅ Reassure: "I'm here when you need me"
+
+### Safety & Compliance
+
+✅ Treat chats as part of medical records
+✅ Follow local telemedicine regulations
+✅ Maintain patient confidentiality
+✅ Document any medical advice given
+✅ Don't diagnose or prescribe via chat without proper consultation
+
+---
+
+## 9. Troubleshooting
+
+### Common Issues
+
+#### "My link doesn't work"
+- Check profile status is "Published"
+- Verify handle is correct (no spaces)
+- Try opening in incognito/private browsing
+
+#### "I'm not receiving conversations"
+- Confirm patients are using correct link
+- Check internet connection
+- Sign out and sign in again
+- Clear browser cache
+
+#### "AI is giving poor responses"
+- Review which topics are enabled
+- Consider adjusting enabled topics
+- Contact support if issues persist
+
+#### "Can't access inbox"
+- Ensure you're signed in
+- Try refreshing the page
+- Clear browser cookies
+- Use Chrome/Firefox/Safari
+
+#### "Analytics not loading"
+- Check internet connection
+- Try different time filter
+- Refresh the page
+- Contact support if persists
+
+### Getting Help
+
+**Email Support**: helpme@evaldoctor.ai
+
+**Include in Your Message**:
+- Your doctor handle
+- Description of issue
+- Screenshots (if applicable)
+- Browser and device info
+
+**Response Time**: Within 24 hours
+
+---
+
+## 🎓 Quick Start Checklist
+
+Use this checklist to get started quickly:
+
+- [ ] Sign up for account
+- [ ] Complete profile information
+- [ ] Set handle (your custom URL)
+- [ ] Write welcome message
+- [ ] Enable topics
+- [ ] Set status to "Published"
+- [ ] Copy your unique link
+- [ ] Share link with first 10 patients
+- [ ] Check inbox daily
+- [ ] Review first conversations
+- [ ] Adjust settings as needed
+
+---
+
+## 📞 Need Help?
+
+- **Support Email**: helpme@evaldoctor.ai
+- **Website**: evaldoctor.ai
+- **Documentation**: Check this guide regularly for updates
+
+---
+
+**Welcome to EvalDoc! We're excited to help you serve your patients more efficiently.** 🎉
+
+---
+
+*Last Updated: January 2026*
+*Version: 1.0*

package/docs/FIREBASE_STORAGE_CORS_FIX.md

@@ -0,0 +1,131 @@
+# Firebase Storage CORS Configuration Fix
+
+## Issue
+File uploads to Firebase Storage are failing with CORS errors when running on `http://localhost:8080`.
+
+## Error Message
+```
+Access to XMLHttpRequest at 'https://firebasestorage.googleapis.com/...' from origin 'http://localhost:8080'
+has been blocked by CORS policy: Response to preflight request doesn't pass access control check
+```
+
+## Solution
+
+### Option 1: Using Google Cloud Console (Recommended)
+
+1. **Install Google Cloud SDK** (if not already installed)
+   ```bash
+   # macOS (using Homebrew)
+   brew install google-cloud-sdk
+
+   # Or download from: https://cloud.google.com/sdk/docs/install
+   ```
+
+2. **Authenticate with Google Cloud**
+   ```bash
+   gcloud auth login
+   ```
+
+3. **Set your project**
+   ```bash
+   gcloud config set project evaldocplatform
+   ```
+
+4. **Apply CORS configuration**
+   ```bash
+   gsutil cors set cors.json gs://evaldocplatform.firebasestorage.app
+   ```
+
+5. **Verify CORS configuration**
+   ```bash
+   gsutil cors get gs://evaldocplatform.firebasestorage.app
+   ```
+
+### Option 2: Using Firebase Console
+
+1. Go to [Firebase Console](https://console.firebase.google.com/)
+2. Select your project: **evaldocplatform**
+3. Go to **Storage** in the left sidebar
+4. Click on the **Rules** tab
+5. Update your storage rules to be more permissive (temporary fix for development):
+
+```javascript
+rules_version = '2';
+service firebase.storage {
+  match /b/{bucket}/o {
+    match /certificates/{userId}/{allPaths=**} {
+      // Allow authenticated users to upload their own certificates
+      allow write: if request.auth != null && request.auth.uid == userId;
+      // Allow read for authenticated users (for verification)
+      allow read: if request.auth != null;
+    }
+
+    match /{allPaths=**} {
+      allow read, write: if request.auth != null;
+    }
+  }
+}
+```
+
+### Option 3: Alternative Upload Strategy (Quick Fix)
+
+Instead of uploading directly from the browser, we can upload via the backend server:
+
+**Update**: This would require backend changes and is more complex. Stick with Option 1 or 2.
+
+## Testing After Fix
+
+1. Restart your local development server:
+   ```bash
+   # Kill existing server if running
+   pkill -f "node server.js"
+
+   # Start server
+   node server.js
+   ```
+
+2. Clear browser cache and try uploading a certificate again
+
+3. Check browser console for any remaining errors
+
+## CORS Configuration File (cors.json)
+
+The `cors.json` file has been created with the following configuration:
+
+```json
+[
+  {
+    "origin": ["*"],
+    "method": ["GET", "POST", "PUT", "DELETE", "HEAD"],
+    "maxAgeSeconds": 3600,
+    "responseHeader": ["Content-Type", "Authorization"]
+  }
+]
+```
+
+**Note**: Using `"origin": ["*"]` allows all origins. For production, you should restrict this to your actual domains:
+
+```json
+[
+  {
+    "origin": ["http://localhost:8080", "https://evaldoctor.ai", "https://yourdomain.com"],
+    "method": ["GET", "POST", "PUT", "DELETE", "HEAD"],
+    "maxAgeSeconds": 3600,
+    "responseHeader": ["Content-Type", "Authorization"]
+  }
+]
+```
+
+## Recommended Approach
+
+**For now (development)**: Use Option 1 with wildcard origin to unblock development.
+
+**For production**:
+1. Apply CORS with specific domain origins
+2. Ensure Firebase Storage Rules are properly configured for security
+3. Add file size limits and file type validation in storage rules
+
+## Additional Notes
+
+- The "Unable to load provider" error in the console is expected for new users who haven't created a provider profile yet. It's caught and handled properly.
+- The CORS error is the main blocker for file uploads.

package/docs/FIXES_APPLIED.md

@@ -0,0 +1,128 @@
+# Fixes Applied - EvalDoc
+
+## Issues Fixed
+
+### 1. ✅ Firebase Storage CORS Error
+
+**Problem:**
+```
+Access to XMLHttpRequest at 'https://firebasestorage.googleapis.com/...' from origin 'http://localhost:8080'
+has been blocked by CORS policy
+```
+
+**Solution Applied:**
+- Created `cors.json` with permissive CORS configuration
+- Applied CORS configuration using: `gsutil cors set cors.json gs://evaldocplatform.firebasestorage.app`
+- Verified configuration: CORS is now properly set to allow all origins (*)
+
+**Files Created:**
+- `cors.json` - CORS configuration file
+- `storage.rules` - Firebase Storage security rules (5MB limit, PDF/images only)
+- `firebase.json` - Updated to include storage rules reference
+
+### 2. ✅ "Unable to load provider" Error
+
+**Problem:**
+```
+Error in checkOnboarding: Error: Unable to load provider
+```
+
+**Analysis:**
+- This error is **expected behavior** for new users who haven't created a provider profile yet
+- The error is properly caught and handled in `app.js` (lines 263-269)
+- When the error occurs, the app correctly shows the onboarding form
+- **No fix needed** - this is working as intended
+
+**How it works:**
+1. New user signs up → No provider profile exists
+2. `/api/me` returns 404 → `loadProvider()` returns `null`
+3. If any other error occurs → Caught by try/catch block
+4. User is shown onboarding form to create provider profile
+
+### 3. ✅ Theme Updated with Feyti Medical Group Colors
+
+**Changes:**
+- Homepage (`/public/index.html` + `/public/css/styles.css`)
+  - Updated to Feyti green (#297B56) and off-white (#FBFBFB)
+  - Changed font from Space Grotesk to Inter
+  - Added complete company information in footer
+
+- Provider Console (`/public/app/` files)
+  - Updated `app.css` with Feyti Medical Group theme
+  - Changed font to Inter to match homepage
+  - All buttons, links, and interactive elements use green theme
+
+## Next Steps for Testing
+
+1. **Test the file upload now:**
+   ```bash
+   # The server should already be running on port 8080
+   # If not, start it:
+   node server.js
+   ```
+
+2. **Register a new doctor:**
+   - Go to http://localhost:8080/app
+   - Create a new account
+   - Fill in the onboarding form
+   - Upload a test certificate (PDF or image, under 5MB)
+   - Submit the form
+
+3. **What should happen:**
+   - ✅ File uploads without CORS error
+   - ✅ Provider profile is created in Firestore
+   - ✅ Certificate is stored in Firebase Storage under `certificates/{userId}/`
+   - ✅ Dashboard loads with provider information
+
+## Firebase Storage Security
+
+The storage rules now enforce:
+- ✅ Only authenticated users can upload
+- ✅ Users can only upload to their own `certificates/{userId}/` folder
+- ✅ Maximum file size: 5MB
+- ✅ Only PDF and image files are allowed
+- ✅ Any authenticated user can read (for admin verification purposes)
+
+## For Production Deployment
+
+When deploying to production, update `cors.json` to restrict origins:
+
+```json
+[
+  {
+    "origin": ["https://evaldoctor.ai", "https://yourdomain.com"],
+    "method": ["GET", "POST", "PUT", "DELETE", "HEAD"],
+    "maxAgeSeconds": 3600,
+    "responseHeader": ["Content-Type", "Authorization"]
+  }
+]
+```
+
+Then reapply:
+```bash
+gsutil cors set cors.json gs://evaldocplatform.firebasestorage.app
+```
+
+## Files Modified/Created
+
+### Created:
+- `cors.json`
+- `storage.rules`
+- `FIREBASE_STORAGE_CORS_FIX.md`
+- `FIXES_APPLIED.md` (this file)
+
+### Modified:
+- `firebase.json` (added storage rules reference)
+- `public/css/styles.css` (Feyti theme)
+- `public/index.html` (Feyti theme + company info)
+- `public/app/app.css` (Feyti theme)
+- `public/app/index.html` (Inter font)
+
+## Summary
+
+✅ CORS issue is fixed - file uploads should work now
+✅ Theme is updated across the entire app
+✅ Firebase Storage security rules are in place
+✅ "Unable to load provider" is expected behavior, not a bug
+
+**You can now test the provider registration flow!**