Executive Summary
Integration Type:
Doctors Digital Office (DDO) - Full SaaS Platform
Total Effort:
320 person-hours (40 person-days)
Estimated Timeline:
8-10 weeks (with shared resources)
Estimated Budget:
₹3,00,000 INR (~$3,600 USD)
Complexity Level:
High (Multi-tenant SaaS integration)
Recommendation:
Proceed as Phase 2 after current milestone completion
⚠ Important Context: This is a major scope addition requiring formal change order approval as per Bettroi SOP. This estimate assumes completion of current NeuroSense360 milestone before DDO integration begins.
Current Situation & Context
NeuroSense360 is currently in active development under the original project scope (PO: PUR-ORD-2025-00013). The Doctors Digital Office (DDO) integration represents a significant platform enhancement that will enable:
- Doctor Onboarding: Multi-tenant portal for neurologists to create digital offices
- Patient Booking: Online appointment scheduling with payment gateway integration
- Tele-Consultation: Zoom/video integration for remote consultations
- AI Documentation: Automated transcription and clinical note generation
- Billing & Invoicing: Automated payment processing and receipt generation
Impact on Current Timeline: If approved, this CR will be scheduled as a separate phase (Phase 2) beginning after successful completion and client sign-off of the current NeuroSense360 Phase 1 deliverables.
Technical Analysis
1. Application Structure
What type of application do we need to make?
| Component | Screens/Pages | Description |
|---|---|---|
| Public Pages | 6 screens | Doctor profiles, booking, payment, confirmation |
| Patient Portal | 4 screens | Login, appointments, intake forms, documents |
| Doctor Portal | 10 screens | Onboarding, dashboard, calendar, consult workspace, billing, settings |
| Admin Portal | 5 screens | Tenant management, support console, audit logs |
| API Endpoints | 35+ endpoints | RESTful APIs for all operations |
| Total | 25 UI screens + 35+ API endpoints | |
2. Features to Display
What are the key features that we need to show?
Patient-Facing Features:
- Doctor discovery and profile viewing (credentials, specialties, fees)
- Real-time availability calendar with slot booking
- Secure payment processing via doctor's payment gateway
- Booking confirmation with calendar invite (ICS) + Zoom link
- Pre-visit intake form with medical history and file uploads
- Email/SMS reminders at T-24h, T-3h, T-30m
- One-click join for tele-consultation
- Post-visit document downloads (summary, prescription, invoice)
- Satisfaction survey (NPS/CSAT)
- Follow-up booking with differential pricing
Doctor-Facing Features:
- Quick onboarding wizard (< 30 minutes to go live)
- Customizable profile with branding (logo, colors, letterhead)
- Availability management (hours, slots, buffers, blackout dates)
- Payment gateway integration (Stripe/Razorpay/PayTabs)
- Zoom link configuration (static or OAuth)
- Today's appointments dashboard with patient intake status
- Consult workspace with live AI transcription
- Editable clinical notes (SOAP format optional)
- One-click prescription generation on letterhead
- Automated invoice generation and email
- Coupon code management
- Follow-up pricing rules (time-based discounts)
- Analytics (conversion, no-show rate, NPS/CSAT trends, revenue)
Admin Features:
- Tenant (doctor) onboarding and KYC verification
- Support escalation console with session context
- Audit logs (who did what, when)
- Content moderation and compliance controls
- System configuration and feature flags
3. Database Storage Requirements
What information do we need to store in our database?
| Table Name | Purpose | Estimated Size |
|---|---|---|
| ddo_tenants | Doctor organizations, branding, status | ~ 1KB/tenant |
| ddo_doctors | Doctor profiles, credentials, fees, availability rules | ~ 5KB/doctor |
| ddo_patients | Patient demographics, contact info, medical history | ~ 3KB/patient |
| ddo_appointments | Bookings, slots, status, payment links | ~ 2KB/appointment |
| ddo_payments | Payment transactions, provider responses | ~ 4KB/payment |
| ddo_uploads | Patient files, reports, prescriptions metadata | ~ 1KB/file (metadata only) |
| ddo_transcripts | Consultation transcripts and AI summaries | ~ 50KB/consult |
| ddo_invoices | Generated invoices and receipts | ~ 2KB/invoice |
| ddo_surveys | Patient feedback (NPS/CSAT) | ~ 1KB/survey |
| ddo_coupons | Discount codes and usage tracking | ~ 500B/coupon |
| ddo_audit_logs | All system actions for compliance | ~ 500B/action |
| ddo_support_tickets | Escalations and help requests | ~ 5KB/ticket |
| Estimated Storage (1,000 doctors, 10,000 patients, 50,000 appointments/year) | ~ 5 GB database + 50 GB file storage | |
Integration with Existing NeuroSense Schema:
- Link DDO patients to existing NeuroSense user accounts via email/mobile
- Share cognitive assessment results between DDO consultations and NeuroSense platform
- Unified patient record: DDO appointments + NeuroSense assessments
- Cross-reference: ddo_patients.neurosense_user_id (foreign key)
4. DDO Platform Functionality Requirements
What functions/features do we need from the DDO platform?
| Category | Features Required | Technical Approach |
|---|---|---|
| Multi-Tenancy | Isolated doctor portals with tenant_id on all data | PostgreSQL Row-Level Security (RLS), per-tenant S3 prefixes |
| Payment Gateways | Stripe, Razorpay, PayTabs, PayU (doctor's own merchant accounts) | Provider adapter pattern, webhook verification, idempotency |
| Video Integration | Zoom static links (v1), OAuth scheduled meetings (v1.1) | Zoom SDK/API, meeting URL generation, participant tracking |
| AI Transcription | Real-time speech-to-text during consultations | OpenAI Whisper or Azure Speech Services, consent workflow |
| AI Clinical Notes | Generate SOAP notes from transcript | GPT-4/Claude for summarization, editable templates |
| PDF Generation | Branded prescriptions, summaries, invoices | Chromium/Puppeteer, per-tenant letterhead templates |
| Notifications | Email with ICS attachments, SMS/WhatsApp (optional) | SendGrid/SES for email, Twilio for SMS, scheduled jobs |
| File Storage | Secure upload/download of patient reports and prescriptions | S3-compatible storage, signed URLs, virus scanning (ClamAV) |
| Availability Engine | Real-time slot calculation with conflict detection | Redis for locking, PostgreSQL optimistic concurrency |
| Analytics | Doctor dashboards with KPIs (conversion, NPS, revenue) | Aggregated queries, cached reports, chart libraries |
5. Overall Workflow
What will the overall workflow be?
Patient Booking Flow:
1. Patient discovers doctor profile (public page)
→ Views credentials, specialties, fees, reviews
2. Patient selects appointment slot from real-time calendar
→ System checks availability, reserves temporary hold (5 min)
3. Patient proceeds to payment
→ Redirect to doctor's payment gateway (Stripe/Razorpay/etc.)
→ Patient completes payment on provider's secure page
4. Payment webhook received by DDO
→ Verify signature, validate payment
→ Re-check slot availability (race condition protection)
→ If available: Lock slot (atomic), create appointment
→ If taken: Offer alternatives or 1-click refund
5. Confirmation sent to patient & doctor
→ Email with ICS calendar invite
→ Zoom meeting link included
→ Link to pre-visit intake form
6. Pre-visit intake (T-48h to T-2h)
→ Patient uploads reports, scans, prior prescriptions
→ Patient updates medical history
→ Doctor reviews intake before consultation
7. Reminders sent automatically
→ T-24h: "Appointment tomorrow with Dr. X, upload any pending reports"
→ T-3h: "Appointment in 3 hours, join link: [Zoom URL]"
→ T-30m: "Appointment starting soon, click to join"
8. Tele-Consultation
→ Patient & doctor join Zoom meeting
→ Consent banner shown for recording/transcription
→ AI transcribes conversation in real-time
→ Doctor can see transcript during consultation
9. Post-Consultation
→ AI generates draft clinical summary (SOAP format)
→ Doctor reviews, edits, approves
→ Doctor generates prescription on letterhead
→ System creates invoice automatically
10. Documents sent to patient
→ Email with attachments:
- Consultation summary (PDF)
- Prescription (PDF on doctor's letterhead)
- Invoice/Receipt (PDF)
→ All documents downloadable from patient portal
11. Follow-up
→ Patient receives satisfaction survey link (NPS/CSAT)
→ Option to book follow-up with differential pricing
→ If within X days: Discounted follow-up rate applied
→ Previous medical history auto-filled
Doctor Onboarding Flow:
1. Doctor signs up → Creates tenant account
2. KYC verification (ID check, medical license)
3. Profile setup: Bio, credentials, specialties, languages, fees
4. Branding: Upload logo, choose colors, upload letterhead PDF
5. Availability rules: Set hours, slot duration, buffers, max daily consults
6. Payment gateway: Connect Stripe/Razorpay (paste API keys or OAuth)
7. Zoom integration: Paste static meeting link or connect OAuth
8. Policies: Set cancellation, refund, follow-up pricing rules
9. Review & publish → Profile goes live
10. Start accepting bookings immediately
Error Handling Workflow:
- Payment timeout → Retry with exponential backoff (3 attempts)
- Slot conflict → Show nearest alternatives + 1-click refund option
- Zoom link broken → Fallback to manual meeting link entry
- AI transcription fails → Allow manual note entry
- File upload fails → Show clear error, allow retry, support ticket option
- "Escalate to Human" button always visible → Creates support ticket
Detailed Effort Estimate
| Task Category | Sub-Tasks | Hours | Role |
|---|---|---|---|
| Phase 1: Architecture & Setup (32 hours) | |||
| Architecture Design | Multi-tenant schema, RLS, data model | 16 | Tech Lead |
| DevOps Setup | Environment, CI/CD, monitoring | 12 | DevOps |
| Auth & Tenancy | Multi-tenant auth, role-based access | 4 | Backend Dev |
| Phase 2: Core Platform (88 hours) | |||
| Tenant Management | Onboarding wizard, KYC, settings | 20 | Full-stack Dev |
| Doctor Portal | Profile, availability, dashboard | 28 | Frontend Dev |
| Availability Engine | Slot calculation, conflict detection, locking | 24 | Backend Dev |
| Public Booking Pages | Doctor profiles, calendar, checkout | 16 | Frontend Dev |
| Phase 3: Payment & Notifications (40 hours) | |||
| Payment Gateway Integration | Stripe, Razorpay adapters, webhooks | 24 | Backend Dev |
| Email System | Templates, ICS generation, SendGrid/SES | 12 | Backend Dev |
| Reminder System | Scheduled jobs (T-24h/3h/30m) | 4 | Backend Dev |
| Phase 4: Patient Portal (32 hours) | |||
| Patient Auth & Profile | OTP login, profile management | 12 | Full-stack Dev |
| Intake Forms | Medical history, file uploads | 12 | Frontend Dev |
| Appointments Dashboard | Upcoming, past, documents | 8 | Frontend Dev |
| Phase 5: Consultation & AI (48 hours) | |||
| Zoom Integration | Static links (v1), OAuth setup (v1.1) | 12 | Backend Dev |
| AI Transcription | Whisper/Azure Speech, real-time processing | 20 | AI Engineer |
| Clinical Notes Generator | SOAP format, GPT-4 summarization | 16 | AI Engineer |
| Phase 6: Documents & Outputs (32 hours) | |||
| PDF Generation | Prescriptions, summaries, invoices | 16 | Backend Dev |
| Letterhead Templates | Per-tenant branding, dynamic data | 8 | Frontend Dev |
| File Storage & Signing | S3, signed URLs, virus scanning | 8 | DevOps |
| Phase 7: Analytics & Admin (24 hours) | |||
| Doctor Analytics | Dashboards, KPIs, reports | 16 | Full-stack Dev |
| Admin Console | Tenant management, audit logs | 8 | Backend Dev |
| Phase 8: Testing & QA (32 hours) | |||
| Unit Testing | Backend API tests, 80% coverage | 12 | Backend Dev |
| Integration Testing | Payment flows, email delivery, AI | 12 | QA Engineer |
| E2E Testing | Full booking workflows, edge cases | 8 | QA Engineer |
| Phase 9: Deployment & Documentation (20 hours) | |||
| Staging Deployment | Deploy, smoke tests, UAT | 8 | DevOps |
| Production Deployment | Go-live, monitoring setup | 4 | DevOps |
| Documentation | User guides, API docs, runbooks | 8 | Tech Writer |
| Project Management & Coordination (12 hours) | |||
| Sprint Planning & Standups | 8 sprints × 1.5 hours each | 12 | Project Manager |
| Subtotal | 320 hrs | 40 days | |
| Contingency Buffer (20%) | 64 hrs | 8 days | |
| GRAND TOTAL | 384 hrs | 48 days | |
Estimated Timeline
Weeks 1-2: Architecture & Setup
Environment setup, multi-tenant architecture, auth system
Weeks 3-4: Core Platform
Doctor portal, availability engine, booking pages
Weeks 5-6: Payments & Notifications
Payment gateways, email system, reminders, patient portal
Weeks 7-8: Consultation & AI
Zoom integration, AI transcription, clinical notes, PDF generation
Weeks 9-10: Testing & Launch
QA testing, bug fixes, staging deployment, UAT, production launch
Resource Model: Shared resources across projects (4-5 week extension due to multitasking). For dedicated team, timeline compresses to 6-7 weeks.
Cost Estimate
| Component | Hours | Rate (INR/hr) | Amount (INR) |
|---|---|---|---|
| Tech Lead / Architect | 16 | ₹1,000 | ₹16,000 |
| Backend Development | 140 | ₹750 | ₹1,05,000 |
| Frontend Development | 72 | ₹700 | ₹50,400 |
| AI/ML Engineering | 36 | ₹850 | ₹30,600 |
| QA Engineering | 32 | ₹600 | ₹19,200 |
| DevOps | 24 | ₹750 | ₹18,000 |
| Project Management | 12 | ₹700 | ₹8,400 |
| Technical Writing | 8 | ₹500 | ₹4,000 |
| Subtotal (320 hrs) | ₹2,51,600 | ||
| Contingency Buffer (20% - 64 hrs) | ₹48,400 | ||
| Total Development Cost | ₹3,00,000 | ||
Ongoing Costs (Monthly)
| Service | Estimated Cost/Month |
|---|---|
| Cloud Hosting (AWS/GCP) | $200 - $500 |
| Database (PostgreSQL managed) | $150 - $300 |
| File Storage (S3) | $50 - $150 |
| Email Service (SendGrid/SES) | $50 - $100 |
| AI Services (OpenAI/Azure) | $100 - $300 |
| Monitoring & Logging | $50 - $100 |
| Total Monthly Operational Cost | $600 - $1,450 |
Note: Payment gateway fees (Stripe/Razorpay) are paid by doctors from their merchant accounts, not Bettroi. Zoom costs are doctor-specific (their own Zoom accounts).
Dependencies & Risks
External Dependencies
- Payment gateway API access and documentation (Stripe, Razorpay, PayTabs)
- Zoom API access for OAuth integration (v1.1)
- OpenAI/Azure API access for transcription and summarization
- Email service provider (SendGrid/SES) approval and configuration
- SMS/WhatsApp provider (Twilio) for optional notifications
Internal Dependencies
- Current NeuroSense milestone completion (prerequisite before DDO starts)
- Client sign-off on NeuroSense Phase 1 deliverables
- Resource availability (shared team across projects)
- Infrastructure access (staging, production environments)
Technical Risks
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Multi-tenant data isolation breach | Low | High | PostgreSQL RLS, extensive testing, security audit |
| Payment webhook race conditions | Medium | High | Redis locking, idempotency keys, comprehensive testing |
| AI transcription accuracy issues | Medium | Medium | Doctor edits required before sending, manual fallback |
| Zoom API rate limiting | Low | Medium | Static links for v1, implement rate limit handling |
| Email deliverability issues | Medium | Medium | DKIM/SPF/DMARC setup, warm-up sending, fallback SMS |
| Scalability bottlenecks | Low | High | Cloud-native architecture, load testing, caching |
| Third-party API breaking changes | Low | High | Version pinning, API monitoring, adapter pattern |
Assumptions
Technical Assumptions:
- NeuroSense360 Phase 1 is complete and stable before DDO integration begins
- Existing infrastructure (AWS/GCP, Supabase) can support multi-tenant architecture
- Payment gateway APIs (Stripe/Razorpay) are RESTful with comprehensive documentation
- Zoom API allows static link usage or OAuth integration for meeting scheduling
- AI transcription services (OpenAI Whisper/Azure Speech) meet accuracy requirements
- PostgreSQL RLS provides adequate tenant isolation without performance degradation
- Email service (SendGrid/SES) can handle 10,000+ transactional emails/day
Business Assumptions:
- Client approves this estimate and provides formal change order within 2 weeks
- Requirements are stable; no major scope changes during development
- Client provides timely feedback and approvals (SLA: 3 business days)
- Test credentials for payment gateways provided within 1 week of kickoff
- Staging environment available for UAT testing
- Go-live date flexible based on development progress
Resource Assumptions:
- Team members available as per timeline (shared resources model)
- No major holidays or extended absences during development period
- Standard 8-hour workdays; no expectation of overtime
- Access to necessary development tools and environments
- Knowledge transfer from current NeuroSense team available
Out of Scope (Exclusions)
The following items are NOT included in this estimate:
- SMS/WhatsApp notifications (planned for v1.1, separate estimate)
- Zoom OAuth scheduled meetings (static links in v1, OAuth in v1.1)
- Multi-doctor clinic management with shared calendars (v2)
- Insurance claims workflows and e-prescription exchange
- EHR (Electronic Health Record) integrations
- Native mobile apps (iOS/Android) - web-responsive only in v1
- HIPAA Business Associate Agreement (BAA) compliance (if required, separate SOW)
- Pharmacy and lab integrations
- Historical data migration from existing doctor systems
- Custom reporting beyond standard KPI dashboards
- White-label reseller platform
- Dedicated 24/7 support (business hours only in v1)
- On-premise deployment option (cloud SaaS only)
Recommendations
Recommended Approach:
- Complete NeuroSense Phase 1 First: Focus on current milestone completion and client sign-off before starting DDO integration. This prevents scope overlap and ensures clear deliverable boundaries.
- Phased Rollout: Launch DDO with core features (v1) in 8-10 weeks, then add advanced features (SMS, Zoom OAuth, multi-doctor) in subsequent releases (v1.1, v2).
- Shared Resources Model: Use existing NeuroSense team for DDO to maintain continuity and reduce onboarding costs. Accept longer timeline (10 weeks vs. 6 weeks) for cost savings.
- Risk Mitigation Priority: Focus on payment security, multi-tenant isolation, and data privacy from day 1. Allocate extra time for testing these critical areas.
- Client Collaboration: Schedule weekly demos to gather feedback early and avoid late-stage surprises.
Alternative: MVP Approach (Reduced Scope)
If budget or timeline is constrained, consider launching with minimal viable features:
- Single payment gateway (Stripe only)
- Email notifications only (no SMS/WhatsApp)
- Zoom static links only (no OAuth)
- Manual clinical notes (no AI transcription in v1)
- Basic analytics (no advanced reporting)
Reduced Estimate: 220 hours (27.5 days), $22,000 - $26,000 USD, 6-week timeline
Next Steps
For Client (Dr. Sangeeth / Decision Maker):
- Review this estimate and provide feedback within 1 week
- Clarify any open questions or request additional details
- Decide: Approve full scope, request MVP approach, or defer to later phase
- Sign formal Change Request (CR) document
- Provide payment gateway test credentials (Stripe/Razorpay)
- Schedule kickoff meeting after NeuroSense Phase 1 completion
For Bettroi Team:
- Await client approval decision
- Upon approval, finalize detailed project plan and sprint schedule
- Allocate resources (shared team model)
- Set up development environment and multi-tenant architecture
- Kickoff meeting within 1 week of approval
- Weekly progress updates to client (Haritha coordination)
- Demo at end of each 2-week sprint
Estimate Validity: This estimate is valid for 60 days from date of issue (27 Dec 2025 - 26 Feb 2026). After this period, rates and availability may change.
Approval & Sign-Off
|
Client Approval: Name: _________________________________ Title: _________________________________ Signature: _________________________________ Date: _________________________________ |
Bettroi Approval: Name: Dr. Murali B K (BK) Title: Technical Lead Signature: _________________________________ Date: 27 December 2025 |
Payment Terms (upon approval):
- 30% advance upon Change Request approval and project kickoff
- 40% upon completion of Phase 5 (Consultation & AI features)
- 30% upon final delivery, UAT completion, and production deployment
Payment Schedule:
- Payment 1: ₹90,000 (30%) - Upon CR approval
- Payment 2: ₹1,20,000 (40%) - Week 7 milestone completion
- Payment 3: ₹90,000 (30%) - Production go-live