vaVairag Akbari

Projects / Planning Stage

Health Map — Healthcare & Wellness Discovery Platform

Planned geospatial discovery platform to help users find healthcare and wellness services across Bengaluru, including hospitals, clinics, diagnostic centers, fitness facilities, and wellness providers.

Planning / Architecture

Project Status: Planning & Architecture Stage

This project is currently in the planning and system design phase. The architecture, features, and technical approach described below represent proposed solutions based on requirements analysis and research, not deployed implementation.

Problem & Solution

Problem

Finding appropriate healthcare and wellness services in a large city like Bengaluru is challenging. Users need to discover nearby providers, understand services offered, filter by specialization, and make informed decisions. Providers need a platform for listing verification and accurate information management.

Proposed Solution

A geospatial discovery platform using React.js frontend, FastAPI backend, and PostgreSQL with PostGIS for efficient location-based queries. Focus on accurate provider information, privacy-conscious data handling, and user-friendly discovery workflows.

Technology Stack

Frontend

React.jsTypeScriptInteractive mapsSearch & filtering

Backend

FastAPIPythonREST APIsAuthentication

Database

PostgreSQLPostGISGeospatial indexing

Proposed

Provider onboardingListing verificationAdmin management

Proposed Architecture

Health Map architecture emphasizes geospatial performance, data accuracy, and privacy. PostgreSQL with PostGIS extension provides robust geospatial capabilities. FastAPI enables rapid API development with automatic documentation. React.js frontend consumes geospatial APIs for interactive discovery.

Frontend Application

React.js, TypeScript, Map libraries

Planned
  • User interface for discovery and search
  • Interactive map with provider markers
  • Filter and search controls
  • Provider detail views
  • Responsive design

API Layer

FastAPI, Python

Planned
  • REST API endpoints for discovery
  • Geospatial query execution
  • Provider CRUD operations
  • Authentication and authorization
  • Onboarding workflow APIs
  • Admin management APIs

Application Services

Python business logic

Planned
  • Discovery service (proximity search)
  • Provider service (CRUD, verification)
  • Onboarding service (workflow management)
  • Admin service (review, approval)
  • Notification service

Database Layer

PostgreSQL with PostGIS extension

Planned
  • Provider data storage
  • Geospatial point data (lat/long)
  • Spatial indexing (GIST indexes)
  • User and provider accounts
  • Verification workflow state
  • Audit logs

Geospatial Queries

PostGIS functions and operators

Planned
  • ST_Distance for proximity calculations
  • ST_DWithin for radius search
  • Spatial indexes for query performance
  • Coordinate reference systems (WGS 84)

Engineering Decisions & Tradeoffs

PostgreSQL with PostGIS over MongoDB geospatial

Rationale: PostGIS offers more sophisticated geospatial operations, better performance for complex queries, industry-standard coordinate system support, and stronger data integrity for healthcare information.

Considerations: PostGIS is more complex to learn but provides significantly better geospatial capabilities. For healthcare discovery, accuracy and performance are critical.

FastAPI for backend

Rationale: Modern Python framework with automatic OpenAPI documentation, type validation with Pydantic, async support for performance, and excellent PostgreSQL integration.

Considerations: FastAPI is newer than Flask/Django but has strong community, excellent documentation, and is well-suited for API-first development.

React.js for frontend

Rationale: Component-based architecture for map interactions, rich ecosystem of map libraries (Leaflet, Mapbox), TypeScript support for type safety, good mobile performance.

Considerations: Considered Next.js but discovery platform doesn't require SSR. React provides flexibility for interactive map features.

Separate frontend and backend

Rationale: FastAPI backend provides clean API layer; React frontend can be deployed independently; clear separation of concerns; easier to scale services separately.

Considerations: More deployment complexity than monolith but better scalability and maintenance.

Project Roadmap

Problem Scoping & Requirements

In Progress

Define user needs, provider needs, feature scope, technical requirements

Deliverables: Requirements document, User stories, Feature prioritization

Architecture & Design

In Progress

System architecture, database schema, API design, UI wireframes

Deliverables: Architecture diagram, Database schema, API specification, Wireframes

Database & Geospatial Modeling

Planned

PostgreSQL setup, PostGIS configuration, schema implementation, spatial indexes

Deliverables: Database setup, Schema migrations, Test data, Geospatial queries

FastAPI Implementation

Planned

API endpoints, authentication, geospatial queries, provider CRUD, onboarding workflow

Deliverables: Working API, API documentation, Authentication, Core endpoints

React Frontend & Maps

Planned

UI components, interactive maps, search and filter, provider details, responsive design

Deliverables: Working frontend, Map integration, Search UI, Provider profiles

Provider Onboarding & Admin

Planned

Onboarding workflow, admin dashboard, verification tools, provider management

Deliverables: Onboarding flow, Admin dashboard, Verification system

Testing & Deployment

Planned

Testing, security review, deployment setup, monitoring

Deliverables: Test suite, Security audit, Deployment, Monitoring

← Back to all projects