How biofiles/studio-clinical works
Project type and purpose
• Full-stack single-page application (SPA) built with Vite, React, TypeScript, Tailwind CSS, and shadcn-ui.
• Uses Supabase (Auth, Database, Storage) as the backend and Supabase Edge Functions for FHIR/CDISC operations.
• Purpose: clinical research platform handling participants, investigators, scheduling, questionnaires, e-consent, FHIR export/import/validation, and CDISC exports.
File structure
• src/ – React components (UI, pages, contexts, hooks, integrations, lib).
• supabase/ – Edge Functions (cdisc-export, fhir-client, fhir-export, fhir-import, fhir-validate) + database migrations.
• integrations/supabase/client.ts – Supabase client wrapper for API calls.
• lib/fhir-client.ts – shared FHIR logic.
• Contexts – manage Auth, Study, Onboarding, Language.
• UI Pattern – component folder for each feature; /ui subfolder for shadcn UI primitives.
README for additional insights
• Tech stack: Vite, TS, React, shadcn-ui, Tailwind.
• Deployment via Lovable (static hosting + automatic CI).
• Supabase handles data, auth, edge functions.
Main components and their relationships (stacked vertically)
a. Client Layer
– Browser (React SPA)
– UI Contexts & Routing (/src/pages, /contexts)
– UI Components (/src/components)
b. API Layer
– Supabase JavaScript Client (/src/integrations/supabase/client.ts)
– REST calls & WebSocket subscriptions to Supabase
– Edge Functions HTTP endpoints (cdisc-export, fhir-export, fhir-import, fhir-validate, fhir-client)
c. Data Layer
– Supabase Database (tables, migrations)
– Supabase Auth (users, roles)
– Supabase Storage (documents, e-consents)
d. External Services
– External FHIR Server(s) (for import/export/validation)
– CDISC conversion tool (invoked by Edge Function)
Architectural patterns & design principles
• Single-page app with Context API for global state (Auth, Study, Language, Onboarding).
• “API-first” serverless backend via Supabase client + Edge Functions.
• Separation of concerns:
– UI (components/pages)
– Business logic (hooks, lib)
– Data access (integrations, supabase functions)
• Migrations ensure reproducible database schema.