Doctor Connect

Current state

The product is in development with an MVP scope covering doctor discovery, timezone-aware booking, secure video consultations, payments and protected consultation records.

Overview

Doctor Connect explores a structured digital bridge between patients seeking more accessible specialist/second-opinion consultations and qualified doctors in South Asia. The product concept combines credentials, scheduling, video, payments and consultation history in one experience.

Problem

Cross-border healthcare questions are often handled informally through personal contacts and messaging. A product in this space needs clearer doctor discovery, verified profiles, scheduling across time zones and secure consultation workflows.

My contribution

• Founded the venture and own product direction, architecture and hands-on development.
• Design patient, doctor, scheduling, consultation and record workflows.
• Build the Next.js web app, NestJS backend and React Native mobile experience.
• Own video, multi-currency payment and secure-history product direction.

Technical approach

The architecture is being designed around explicit separation of doctor discovery, appointment scheduling, consultation sessions and patient-controlled records. WebRTC supports video, Stripe supports payment flows, and the data layer is planned around access-controlled consultation history.

Engineering highlights

• Timezone-aware instant and scheduled consultation journeys.
• Cross-platform web/mobile product architecture.
• Video, payments and protected consultation-history features planned as first-class workflows.

Key features

• Verified doctor directory by speciality.
• Instant and scheduled booking.
• Secure video consultation flow.
• Patient-controlled consultation history.
• Multi-currency payments.
• Consultation notes / e-prescription direction.

Result

The venture is in development. The current priority is validating the consultation workflow and trust model before making broader claims around scale or clinical adoption.

Development timeline

• Concept
  Defined patient/doctor value proposition and target consultation use cases.
• Architecture
  Designed scheduling, video, payment and record boundaries.
• Build
  Developing core web, API and mobile flows.
• Next
  Validate with appropriate clinical/legal input before wider product rollout.

Product screens

Placeholder frames for now — real Web / iOS / Android screenshots land here as builds ship.

Who it’s for

Cost-conscious UK/US patients, and South Asian doctors who want international consult income.