How josephrmartinez/soapnotescribe works
Main Components
A. Client-Side (Frontend)
• Next.js Application Layer
• Audio Recording/Upload Components
• Management Interface
• Patient Management Interface
• Authentication UI
• Real-time Processing Status Display
B. Server-Side Components
• API Routes (Next.js/Vercel Serverless Functions)
• Authentication Service (Supabase)
• Storage Service (Supabase)
• Vector Database (Supabase)
C. External Services
• Replicate (AI Processing)
• OpenAI Integration
• PDF Generation Service
[Client Tier]
• ↕
[Application Tier]
• ↕
[Data & External Services Tier]
Component Relationships to Highlight
a. User Flow Path:
• Auth UI → Dashboard → Audio Upload → Processing → Note Generation → Review/Edit
b. Data Flow Path:
• Audio Upload → Storage → AI Processing → Vector DB → Note Generation
Specific Implementation Details
• /dashboard/* components
• /auth/* components
• /api/* endpoints
• /components/* shared components
Key Architectural Elements
a. Frontend Layer:
• Next.js pages router structure
• Dashboard layout with sidenav
• Audio processing components
• Form handling for notes and patients
b. Backend Layer:
• API routes for webhook handling
• Supabase integration points
• Serverless function architecture
c. Data Storage Layer:
• Supabase tables for patients, notes, and templates
• File storage for audio files
• Vector storage for AI processing results
Integration Points
• Authentication flow with Supabase
• Audio file processing pipeline
• AI model integration points
• PDF generation service