chore: Added Section for HIPPA Enabled Orgs

Author: roshan-vapi

fern/assistants/structured-outputs-quickstart.mdx

@@ -638,14 +638,16 @@ You can attach multiple structured outputs to extract different types of data:
 {
   artifactPlan: {
     structuredOutputIds: [
-      customerInfoId,    // Extract customer details
-      appointmentId,      // Extract appointment requests
-      feedbackId         // Extract satisfaction feedback
+      "550e8400-e29b-41d4-a716-446655440001",    // Customer details extraction
+      "550e8400-e29b-41d4-a716-446655440002",    // Appointment requests extraction  
+      "550e8400-e29b-41d4-a716-446655440003"     // Satisfaction feedback extraction
     ]
   }
 }
 ```
 
+<Note>The `structuredOutputIds` are UUIDs returned when you create each structured output configuration.</Note>
+
 ### Conditional extraction
 
 Use conditional logic in your schema to handle different scenarios:

fern/assistants/structured-outputs.mdx

@@ -756,9 +756,21 @@ if (data.result === null) {
 ### Partial extraction
 
 - Make fields optional if they might not be mentioned
-- Check if schema complexity exceeds limits
 - Verify data types match expected values
 
+## HIPAA compliance
+
+<Warning>
+**Important for HIPAA-enabled organizations:**
+
+If your organization has HIPAA compliance enabled (`hipaaEnabled: true`), structured outputs are **disabled by default** to protect PHI (Protected Health Information).
+
+To use structured outputs with HIPAA compliance:
+- Contact the Vapi team to enable structured outputs
+- Ensure you understand the implications for PHI handling
+- Follow all HIPAA compliance best practices when extracting sensitive health data
+</Warning>
+
 ## Limitations
 
 <Warning>