Update prompts

main.py

@@ -67,9 +67,9 @@ class HealthcareChatbot:
         self.endpoints_documentation = endpoints_documentation
         self.ollama_base_url = "http://localhost:11434"
         self.model_name = "gemma3"
-        self.BASE_URL = 'https://ae84-197-54-54-66.ngrok-free.app'
+        self.BASE_URL = 'https://8ac0-197-54-54-66.ngrok-free.app'
         self.headers = {'Content-type': 'application/json'}
-        self.user_id = '18064183-3b7a-4986-b7f2-b92d325bdec7'
+        self.user_id = '9e889485-3db4-4f70-a7a2-e219beae6578'
         self.max_retries = 3
         self.retry_delay = 2
         
@@ -155,141 +155,149 @@ class HealthcareChatbot:
 
         # UNIFIED ROUTER CHAIN - Handles both intent classification AND API routing
         self.router_prompt_template = PromptTemplate(
-                template="""
-            You are a routing system. Your job is simple:
-            1. Understand what the user wants
-            2. Handle any dates/times in their request with PRECISE calculations
-            3. Check if any endpoint can do what they want
-            4. If yes = API_ACTION, if no = CONVERSATION
-
-            ## Available API Endpoints Documentation
-            {endpoints_documentation}
-
-            ## User Query to Analyze
-            Query: "{user_query}"
-            Language: {detected_language}
-            Current Context:
-            - DateTime: {current_datetime}
-            - Timezone: {timezone}
-            - Current Day of Week: {current_day_name}
-
-            ## Step-by-Step Analysis
-
-            **STEP 1: What does the user want?**
-            - If query is in Arabic, translate it to English first
-            - Identify the exact action or information the user is requesting
-            - Focus on understanding their underlying need, not just the words
-
-            **STEP 2: Handle Date/Time Processing with PRECISE Calculations**
-            IMPORTANT: Use the current datetime ({current_datetime}) and timezone ({timezone}) for ALL calculations.
-
-            ### Current Date Reference Points:
-            - Today is: {current_datetime}
-            - Current day of week: {current_day_name}
-            - Current timezone: {timezone}
-
-            ### Arabic Date/Time Expressions Processing:
-            **Basic Relative Dates:**
-            - "اليوم" (today) = {current_datetime} date portion
-            - "غدا" (tomorrow) = current date + 1 day
-            - "أمس" (yesterday) = current date - 1 day
-            - "بعد غد" (day after tomorrow) = current date + 2 days
-
-            **Weekly Expressions - CALCULATE PRECISELY:**
-            - "الأسبوع القادم" (next week) = current date + 7 days
-            - "الأسبوع الماضي" (last week) = current date - 7 days
-
-            **Specific Weekday Calculations - MOST IMPORTANT:**
-            For expressions like "يوم [weekday] القادم" (next [weekday]):
-            1. Identify the target weekday from Arabic names:
-            - الأحد (Sunday) = 0
-            - الاثنين (Monday) = 1  
-            - الثلاثاء (Tuesday) = 2
-            - الأربعاء (Wednesday) = 3
-            - الخميس (Thursday) = 4
-            - الجمعة (Friday) = 5
-            - السبت (Saturday) = 6
-
-            2. Calculate days to add:
-            - Get current weekday number (0=Sunday, 1=Monday, etc.)
-            - Target weekday number
-            - If target > current: days_to_add = target - current
-            - If target <= current: days_to_add = 7 - (current - target)
-            - Final date = current_date + days_to_add
-
-            **Example Calculation:**
-            If today is Sunday (June 1, 2025) and user says "يوم الاربع القادم" (next Wednesday):
-            - Current weekday: 0 (Sunday)
-            - Target weekday: 3 (Wednesday)  
-            - Days to add: 3 - 0 = 3
-            - Result: June 1 + 3 days = June 4, 2025
-
-            **Monthly/Yearly Expressions:**
-            - "الشهر القادم" (next month) = add 1 month to current date
-            - "الشهر الماضي" (last month) = subtract 1 month from current date
-            - "السنة القادمة" (next year) = add 1 year to current date
-
-            **Time Expressions:**
-            - "صباحًا" (morning/AM) = 09:00 if no specific time given
-            - "مساءً" (evening/PM) = 18:00 if no specific time given
-            - "ظهرًا" (noon) = 12:00
-            - "منتصف الليل" (midnight) = 00:00
-            - "بعد ساعتين" (in 2 hours) = current time + 2 hours
-            - "قبل ساعة" (1 hour ago) = current time - 1 hour
-
-            **Date Format Output:**
-            - Always convert final calculated date to ISO 8601 format: YYYY-MM-DDTHH:MM:SS
-            - Include timezone offset if available
-            - For date-only expressions, use 00:00:00 as default time
-
-            **STEP 3: Find matching endpoint**
-            - Read each endpoint description in the documentation
-            - Check if any endpoint's purpose can fulfill what the user wants
-            - Match based on functionality, not keywords
-
-            **STEP 4: Decision**
-            - Found matching endpoint = "API_ACTION"
-            - No matching endpoint = "CONVERSATION"
-
-            **STEP 5: Parameter Extraction (only if API_ACTION)**
-            - Extract parameter values from user query
-            - Use the CALCULATED dates/times from Step 2
-            - Convert all dates/times to ISO 8601 format (YYYY-MM-DDTHH:MM:SS)
-            - List any missing required parameters
-
-            ## Output Format
-            {{
-                "intent": "CONVERSATION|API_ACTION",
-                "confidence": 0.8,
-                "reasoning": "User wants: [what user actually needs]. Date/time processing: [show exact calculation: current date + X days = final date]. Found endpoint: [endpoint path and why it matches] OR No endpoint matches this need",
-                "endpoint": "/exact/endpoint/path",
-                "method": "GET|POST|PUT|DELETE",
-                "params": {{}},
-                "missing_required": [],
-                "calculated_datetime": "YYYY-MM-DDTHH:MM:SS (if date/time was processed)"
-            }}
-
-            ## CRITICAL REMINDERS:
-            1. ALWAYS use the provided current_datetime ({current_datetime}) as your base for calculations
-            2. For "next weekday" expressions, calculate the exact number of days to add
-            3. Show your calculation work in the reasoning field
-            4. Double-check weekday numbers: Sunday=0, Monday=1, Tuesday=2, Wednesday=3, Thursday=4, Friday=5, Saturday=6
-
-            Now analyze the user query step by step and give me the JSON response.
-            
-            **FINAL CHECK BEFORE OUTPUTTING:**
-            🔍 **MANDATORY ARABIC DETECTION:**
-            - Look at your params object
-            - Search for these Arabic characters: ا ب ت ث ج ح خ د ذ ر ز س ش ص ض ط ظ ع غ ف ق ك ل م ن ه و ي
-            - If you find ANY Arabic character, TRANSLATE IT IMMEDIATELY
-            - Do NOT output JSON until params is 100% English
-            
-            **REMEMBER:** "دكتور احمد" MUST become "Dr. Ahmed" - NO EXCEPTIONS!
-            """,
-                input_variables=["user_query", "detected_language", "extracted_keywords", 
-                                "sentiment_analysis", "endpoints_documentation", "current_datetime", 
-                                "timezone", "current_day_name"]
-            )
+              template="""
+          You are a routing system. Your job is simple:
+          1. Understand what the user wants
+          2. Handle any dates/times in their request with PRECISE calculations
+          3. Check if any endpoint can do what they want
+          4. If yes = API_ACTION, if no = CONVERSATION
+
+          ## Available API Endpoints Documentation
+          {endpoints_documentation}
+
+          ## User Query to Analyze
+          Query: "{user_query}"
+          Language: {detected_language}
+          Current Context:
+          - DateTime: {current_datetime}
+          - Timezone: {timezone}
+          - Current Day of Week: {current_day_name}
+
+          ## Step-by-Step Analysis
+
+          **STEP 1: What does the user want?**
+          - If query is in Arabic, translate it to English first
+          - Identify the exact action or information the user is requesting
+          - Focus on understanding their underlying need, not just the words
+
+          **STEP 2: Handle Date/Time Processing with PRECISE Calculations**
+          IMPORTANT: Use the current datetime ({current_datetime}) and timezone ({timezone}) for ALL calculations.
+
+          ### Current Date Reference Points:
+          - Today is: {current_datetime}
+          - Current day of week: {current_day_name}
+          - Current timezone: {timezone}
+
+          ### Arabic Date/Time Expressions Processing:
+          **Basic Relative Dates:**
+          - "اليوم" (today) = {current_datetime} date portion
+          - "غدا" (tomorrow) = current date + 1 day
+          - "أمس" (yesterday) = current date - 1 day
+          - "بعد غد" (day after tomorrow) = current date + 2 days
+
+          **Weekly Expressions - CALCULATE PRECISELY:**
+          - "الأسبوع القادم" (next week) = current date + 7 days
+          - "الأسبوع الماضي" (last week) = current date - 7 days
+
+          **Specific Weekday Calculations - MOST IMPORTANT:**
+          For expressions like "يوم [weekday] القادم" (next [weekday]):
+          1. Identify the target weekday from Arabic names:
+          - الأحد (Sunday) = 0
+          - الاثنين (Monday) = 1  
+          - الثلاثاء (Tuesday) = 2
+          - الأربعاء (Wednesday) = 3
+          - الخميس (Thursday) = 4
+          - الجمعة (Friday) = 5
+          - السبت (Saturday) = 6
+
+          2. Calculate days to add:
+          - Get current weekday number (0=Sunday, 1=Monday, etc.)
+          - Target weekday number
+          - If target > current: days_to_add = target - current
+          - If target <= current: days_to_add = 7 - (current - target)
+          - Final date = current_date + days_to_add
+
+          **Example Calculation:**
+          If today is Sunday (June 1, 2025) and user says "يوم الاربع القادم" (next Wednesday):
+          - Current weekday: 0 (Sunday)
+          - Target weekday: 3 (Wednesday)  
+          - Days to add: 3 - 0 = 3
+          - Result: June 1 + 3 days = June 4, 2025
+
+          **Monthly/Yearly Expressions:**
+          - "الشهر القادم" (next month) = add 1 month to current date
+          - "الشهر الماضي" (last month) = subtract 1 month from current date
+          - "السنة القادمة" (next year) = add 1 year to current date
+
+          **Time Expressions:**
+          - "صباحًا" (morning/AM) = 09:00 if no specific time given
+          - "مساءً" (evening/PM) = 18:00 if no specific time given
+          - "ظهرًا" (noon) = 12:00
+          - "منتصف الليل" (midnight) = 00:00
+          - "بعد ساعتين" (in 2 hours) = current time + 2 hours
+          - "قبل ساعة" (1 hour ago) = current time - 1 hour
+
+          **Date Format Output:**
+          - Always convert final calculated date to ISO 8601 format: YYYY-MM-DDTHH:MM:SS
+          - Include timezone offset if available
+          - For date-only expressions, use 00:00:00 as default time
+
+          **STEP 3: Find matching endpoint**
+          - Read each endpoint description in the documentation
+          - Check if any endpoint's purpose can fulfill what the user wants
+          - Match based on functionality, not keywords
+
+          **STEP 4: Decision**
+          - Found matching endpoint = "API_ACTION"
+          - No matching endpoint = "CONVERSATION"
+
+          **STEP 5: Parameter Extraction (only if API_ACTION)**
+          - Extract parameter values from user query
+          - Use the CALCULATED dates/times from Step 2
+          - Convert all dates/times to ISO 8601 format (YYYY-MM-DDTHH:MM:SS)
+          - List any missing required parameters
+          - **CRITICAL: All parameters must be in English**
+            - Translate any Arabic text to English
+            - Convert names to English equivalents (e.g., "دكتور احمد" → "Dr. Ahmed")
+            - Use standard English terms for all parameters
+
+          ## Output Format
+          {{
+              "intent": "CONVERSATION|API_ACTION",
+              "confidence": 0.8,
+              "reasoning": "User wants: [what user actually needs]. Date/time processing: [show exact calculation: current date + X days = final date]. Found endpoint: [endpoint path and why it matches] OR No endpoint matches this need",
+              "endpoint": "/exact/endpoint/path",
+              "method": "GET|POST|PUT|DELETE",
+              "params": {{
+                  // ALL VALUES MUST BE IN ENGLISH
+                  // Arabic terms must be translated to English equivalents
+              }},
+              "missing_required": [],
+              "calculated_datetime": "YYYY-MM-DDTHH:MM:SS (if date/time was processed)"
+          }}
+
+          ## CRITICAL REMINDERS:
+          1. ALWAYS use the provided current_datetime ({current_datetime}) as your base for calculations
+          2. For "next weekday" expressions, calculate the exact number of days to add
+          3. Show your calculation work in the reasoning field
+          4. Double-check weekday numbers: Sunday=0, Monday=1, Tuesday=2, Wednesday=3, Thursday=4, Friday=5, Saturday=6
+          5. **ALL PARAMETERS MUST BE IN ENGLISH** - translate any Arabic text before output
+
+          **FINAL CHECK BEFORE OUTPUTTING:**
+          🔍 **MANDATORY LANGUAGE CHECK:**
+          1. Examine every value in the params object
+          2. If ANY value contains Arabic characters (ا-ي), you MUST:
+            - Translate it to English
+            - Convert names to English equivalents
+            - Replace Arabic terms with English counterparts
+          3. Only output JSON when ALL parameters are in English
+
+          Now analyze the user query step by step and give me the JSON response.
+          """,
+              input_variables=["user_query", "detected_language", "extracted_keywords", 
+                              "sentiment_analysis", "endpoints_documentation", "current_datetime", 
+                              "timezone", "current_day_name"]
+          )
         ''' Third Approach '''
         # self.router_prompt_template = PromptTemplate(
         #         template="""
@@ -582,70 +590,123 @@ class HealthcareChatbot:
         )
 
         # API RESPONSE CHAIN - Formats API responses for users
-        self.api_response_template = PromptTemplate(
-            template="""
-            You are a professional healthcare assistant. Answer the user's question using the provided API data.
+        # self.api_response_template = PromptTemplate(
+        #     template="""
+        #     You are a professional healthcare assistant. Answer the user's question using the provided API data.
 
-            User Query: {user_query}
-            User Sentiment: {sentiment_analysis}
-            Response Language: {detected_language}
+        #     User Query: {user_query}
+        #     User Sentiment: {sentiment_analysis}
+        #     Response Language: {detected_language}
 
-            API Response Data:
-            {api_response}
+        #     API Response Data:
+        #     {api_response}
 
-            === INSTRUCTIONS ===
+        #     === INSTRUCTIONS ===
             
-            1. Read and understand the API response data above
-            2. Use ONLY the actual data from the API response - never make up information
-            3. Respond in {detected_language} language only
-            4. Write like you're talking to a friend or family member - warm, friendly, and caring
-            5. Make it sound natural and conversational, not like a system message
-            6. Convert technical data to simple, everyday language
-
-            === DATE AND TIME FORMATTING ===
+        #     1. Read and understand the API response data above
+        #     2. Use ONLY the actual data from the API response - never make up information
+        #     3. Respond in {detected_language} language only
+        #     4. Write like you're talking to a friend or family member - warm, friendly, and caring
+        #     5. Make it sound natural and conversational, not like a system message
+        #     6. Convert technical data to simple, everyday language
+
+        #     === DATE AND TIME FORMATTING ===
             
-            When you see date_time fields like '2025-05-30T10:28:10':
-            - For English: Convert to "May 30, 2025 at 10:28 AM" 
-            - For Arabic: Convert to "٣٠ مايو ٢٠٢٥ في الساعة ١٠:٢٨ صباحاً"
+        #     When you see date_time fields like '2025-05-30T10:28:10':
+        #     - For English: Convert to "May 30, 2025 at 10:28 AM" 
+        #     - For Arabic: Convert to "٣٠ مايو ٢٠٢٥ في الساعة ١٠:٢٨ صباحاً"
 
-            === RESPONSE EXAMPLES ===
+        #     === RESPONSE EXAMPLES ===
             
-            For appointment confirmations:
-            - English: "Great! I've got your appointment set up for May 30, 2025 at 10:28 AM. Everything looks good!"
-            - Arabic: "ممتاز! موعدك محجوز يوم ٣٠ مايو ٢٠٢٥ الساعة ١٠:٢٨ صباحاً. كل شيء جاهز!"
+        #     For appointment confirmations:
+        #     - English: "Great! I've got your appointment set up for May 30, 2025 at 10:28 AM. Everything looks good!"
+        #     - Arabic: "ممتاز! موعدك محجوز يوم ٣٠ مايو ٢٠٢٥ الساعة ١٠:٢٨ صباحاً. كل شيء جاهز!"
 
-            For appointment info:
-            - English: "Your next appointment is on May 30, 2025 at 10:28 AM. See you then!"
-            - Arabic: "موعدك القادم يوم ٣٠ مايو ٢٠٢٥ الساعة ١٠:٢٨ صباحاً. نراك قريباً!"
+        #     For appointment info:
+        #     - English: "Your next appointment is on May 30, 2025 at 10:28 AM. See you then!"
+        #     - Arabic: "موعدك القادم يوم ٣٠ مايو ٢٠٢٥ الساعة ١٠:٢٨ صباحاً. نراك قريباً!"
 
-            === TONE GUIDELINES ===
-            - Use friendly words like: "Great!", "Perfect!", "All set!", "ممتاز!", "رائع!", "تمام!"
-            - Add reassuring phrases: "Everything looks good", "You're all set", "كل شيء جاهز", "تم بنجاح"
-            - Sound helpful and caring, not robotic or formal
+        #     === TONE GUIDELINES ===
+        #     - Use friendly words like: "Great!", "Perfect!", "All set!", "ممتاز!", "رائع!", "تمام!"
+        #     - Add reassuring phrases: "Everything looks good", "You're all set", "كل شيء جاهز", "تم بنجاح"
+        #     - Sound helpful and caring, not robotic or formal
 
-            === LANGUAGE FORMATTING ===
+        #     === LANGUAGE FORMATTING ===
             
-            For Arabic responses:
-            - Use Arabic numerals: ٠١٢٣٤٥٦٧٨٩
-            - Use Arabic month names: يناير، فبراير، مارس، أبريل، مايو، يونيو، يوليو، أغسطس، سبتمبر، أكتوبر، نوفمبر، ديسمبر
-            - Friendly, warm Arabic tone
-
-            For English responses:  
-            - Use standard English numerals
-            - 12-hour time format with AM/PM
-            - Friendly, conversational English tone
-
-            === CRITICAL RULES ===
-            - Extract dates and times exactly as they appear in the API response
-            - Never use example dates or placeholder information
-            - Respond only in the specified language
-            - Make your response sound like a helpful friend, not a computer
-            - Focus on answering the user's specific question with warmth and care
-
-            Generate a friendly, helpful response using the API data provided above.
-            """,
-            input_variables=["user_query", "api_response", "detected_language", "sentiment_analysis"]
-        )
+        #     For Arabic responses:
+        #     - Use Arabic numerals: ٠١٢٣٤٥٦٧٨٩
+        #     - Use Arabic month names: يناير، فبراير، مارس، أبريل، مايو، يونيو، يوليو، أغسطس، سبتمبر، أكتوبر، نوفمبر، ديسمبر
+        #     - Friendly, warm Arabic tone
+
+        #     For English responses:  
+        #     - Use standard English numerals
+        #     - 12-hour time format with AM/PM
+        #     - Friendly, conversational English tone
+
+        #     === CRITICAL RULES ===
+        #     - Extract dates and times exactly as they appear in the API response
+        #     - Never use example dates or placeholder information
+        #     - Respond only in the specified language
+        #     - Make your response sound like a helpful friend, not a computer
+        #     - Focus on answering the user's specific question with warmth and care
+
+        #     Generate a friendly, helpful response using the API data provided above.
+        #     """,
+        #     input_variables=["user_query", "api_response", "detected_language", "sentiment_analysis"]
+        # )
+        self.api_response_template = PromptTemplate(
+              template="""
+          You are a professional healthcare assistant. Generate a natural language response to the user's query using ONLY the provided API data.
+
+          User Query: {user_query}
+          User Sentiment: {sentiment_analysis}
+          Response Language: {detected_language}
+
+          API Response Data:
+          {api_response}
+
+          === CORE INSTRUCTIONS ===
+
+          1. Analyze the API response structure and extract relevant data points
+          2. Cross-reference with the user's query to determine what information to include
+          3. Respond in {detected_language} using a warm, conversational tone
+          4. Convert technical data into natural language appropriate for healthcare communication
+
+          === DATE/TIME HANDLING ===
+
+          1. Identify all date/time fields in the API response (look for ISO 8601 format: YYYY-MM-DDTHH:MM:SS)
+          2. For English responses:
+            - Format dates as "Month Day, Year at HH:MM AM/PM"
+            - Convert times to 12-hour format with proper AM/PM
+          3. For Arabic responses:
+            - Format dates as "Day Month Year الساعة HH:MM صباحاً/مساءً"
+            - Use Arabic numerals (٠١٢٣٤٥٦٧٨٩)
+            - Use Arabic month names
+          4. Preserve all original date/time values - only change the formatting
+
+          === RESPONSE GUIDELINES ===
+
+          1. Use ONLY data present in the API response
+          2. Maintain a professional yet friendly healthcare tone
+          3. Adapt to the user's sentiment: 
+            - Positive: reinforce with encouraging language
+            - Neutral: provide clear, factual information
+            - Negative: show empathy and offer assistance
+          4. Structure the response to directly answer the user's query
+          5. Include relevant details from the API response that address the user's needs
+
+          === CRITICAL RULES ===
+
+          1. Never invent or hallucinate information not present in the API response
+          2. If the API response doesn't contain requested information, say so politely
+          3. All dates/times must exactly match the API data
+          4. Maintain strict language consistency (respond only in {detected_language})
+          5. Format all technical data (IDs, codes, etc.) for easy understanding
+
+          Generate a helpful response that addresses the user's query using the API data.
+          """,
+              input_variables=["user_query", "api_response", "detected_language", "sentiment_analysis"]
+          )
 
         # Create the 3 chains
         self.router_chain = LLMChain(llm=self.llm, prompt=self.router_prompt_template)
@@ -1144,7 +1205,6 @@ class HealthcareChatbot:
         print("🗑️ Conversation history cleared.")
 
 
-
 # def main():
 #     """Main function to run the healthcare chatbot"""
 #     try: