Design SQLite schema for a Zocdoc-like telehealth app
Session from traceweave on Hugging Face by Samarth0710 · MIT · condensed by Coders Talk
1msession
0interventions
GOAL
Design a complete SQLite database schema (tables, keys, indexes, constraints) to support booking telehealth/in-network appointments and managing family member profiles with insurance and pharmacy details.
- +0Prompt · +0Design a complete SQLite schema covering booking a dermatologist telehealth appointment with insurance/rating filters, and adding a spouse family member with insurance, pharmacy, and PCP appointment booking. Return only DDL as JSON.
- +0mAgent did · +0mCreated users, specialties, and providers tables with ratings and specialty foreign keys.
- +0mAgent did · +0mAdded insurance_plans, user_insurance, and provider_insurance tables to model carrier/plan relationships and network participation.
- +0mAgent did · +0mAdded pharmacies, family_members, and family_member_insurance tables to support dependent profiles and their coverage.
- +1mAgent did · +1mAdded provider_availability and appointments tables linking users, family members, providers, and time slots.
- +1mAgent did · +1mCreated all supporting indexes and verified 11 tables exist via sqlite_master query.
- +1mOutcome · +1mDelivered final JSON DDL for 11 tables covering both booking and family-member scenarios.
VERDICT
I'd ask for the full entity list and relationship diagram upfront rather than letting the agent build tables incrementally, since that step-by-step approach worked fine here but wastes turns on straightforward schema design. No corrections were needed this run, the agent handled both scenarios and verified table creation itself.