Instruction file imported from AndriiKulakovskyi/efondamental (.cursor/rules/bipolar-visit-questionnaire-mapping.mdc). Copyright stays with the author.

Bipolar Vertical: Visit Type Questionnaire Mappings

This rule defines the explicit mapping between questionnaires and Supabase tables for each bipolar visit type. When a questionnaire is reused across visits, responses are persisted in a single shared table to ensure data consistency and longitudinal integrity.

CRITICAL: All table names use the bipolar_ pathology prefix (NOT the deprecated responses_ prefix). The authoritative source of truth for table names is:

1. BIPOLAR_INITIAL_TABLES in lib/services/bipolar-initial.service.ts
2. Service .from() calls in the relevant service files
3. The get_visit_detail_data RPC function in supabase/schema.sql

Visit Types Overview

Screening Visit (5 questionnaires)

Auto Module (Patient Self-Report)

Medical Module (Professional)

Initial Evaluation Visit (57 questionnaires)

Nurse Module (7 questionnaires)

Thymic Module (7 questionnaires)

Auto Module - ETAT Submodule (8 questionnaires)

Auto Module - TRAITS Submodule (9 questionnaires)

Medical Module (19 questionnaires)

Neuropsy Module (22 questionnaires)

Social Module (1 questionnaire)

Biannual Follow-up Visit (25 questionnaires)

Nurse Module (7 questionnaires) - SHARED TABLES

DSM5 Module (3 questionnaires)

Suicide Module (2 questionnaires)

Soin Suivi Module (6 questionnaires)

Thymic Module (7 questionnaires) - SHARED TABLES

Annual Evaluation Visit (70 questionnaires)

Annual visits include ALL questionnaires from Biannual (25) PLUS additional questionnaires from Initial evaluation modules.

Additional Auto Module - ETAT (7 questionnaires) - SHARED TABLES

Additional Neuropsy Module - SHARED TABLES

Additional C-SSRS & SIS - SHARED TABLES

Additional Social Module - SHARED TABLE

Shared Table Rules

One Response Per Visit

All tables have visit_id as UNIQUE constraint. Each visit creates a new response row in the shared table.

Longitudinal Tracking

Query all responses for a patient across visits:

SELECT * FROM bipolar_madrs
WHERE patient_id = ?
ORDER BY created_at;

Cross-Visit Comparison

Shared tables enable longitudinal analysis (e.g., MADRS score trends over time).

Service Layer Mapping

RPC Functions

CRITICAL RPC Rule: When modifying get_visit_detail_data, always use bipolar_* table names (never responses_*). Cross-reference against supabase/schema.sql for the authoritative version.