Fix

main.py

@@ -266,18 +266,20 @@ class HealthcareChatbot:
                 - What type of operation are they requesting? (create, read, update, delete, search, etc.)
                 - What entity/resource are they working with?
 
-                STEP 2: DATE/TIME PROCESSING
-                - Identify any temporal expressions in the user query
-                - Convert relative dates/times using the current context:
-                * "اليوم" (today) = current date
-                * "غدا" (tomorrow) = current date + 1 day
+                STEP 2: DATE/TIME PROCESSING (CRITICAL FOR ARABIC QUERIES)
+                - Carefully identify temporal expressions in Arabic:
+                * "اليوم" (today) = current date ({current_datetime})
+                * "غدا" or "بكره" (tomorrow) = current date + 1 day
                 * "أمس" (yesterday) = current date - 1 day
                 * "الأسبوع القادم" (next week) = current date + 7 days
-                * "بعد ساعتين" (in 2 hours) = current time + 2 hours
-                * "صباحًا" (morning/AM), "مساءً" (evening/PM)
-                - Handle different date formats and languages
-                - Account for timezone differences
-                - Convert to ISO 8601 format: YYYY-MM-DDTHH:MM:SS
+                * "بعد ساعة/ساعتين" (in 1 hour/2 hours) = current time + specified hours
+                * "صباحًا" (morning) = AM time
+                * "مساءً" (evening) = PM time (convert "10 مساءً" to 22:00)
+                - For absolute dates in Arabic format (DD/MM/YYYY), convert to ISO format
+                - ALWAYS verify the calculated date against {current_datetime} to ensure:
+                - "tomorrow" is correctly calculated as current date + 1 day
+                - Time conversions respect the 24-hour format (e.g., 10 مساءً = 22:00)
+                - Final output MUST be in ISO 8601: YYYY-MM-DDTHH:MM:SS
 
                 STEP 3: ENDPOINT MATCHING
                 - Review each endpoint in the documentation
@@ -293,11 +295,10 @@ class HealthcareChatbot:
                 - Numbers to integers
                 - Set appropriate defaults for optional parameters if beneficial
 
-                
-
                 STEP 5: VALIDATION
                 - Ensure ALL required parameters are provided or identified as missing
                 - Verify parameter formats match documentation requirements
+                - Double-check date calculations against {current_datetime}
                 - Check that the selected endpoint actually solves the user's problem
 
                 === RESPONSE FORMAT ===
@@ -307,7 +308,8 @@ class HealthcareChatbot:
                     "reasoning": {{
                         "user_intent": "Brief description of what the user wants to accomplish",
                         "selected_endpoint": "Why this endpoint was chosen over others",
-                        "parameter_mapping": "How user query maps to endpoint parameters"
+                        "parameter_mapping": "How user query maps to endpoint parameters",
+                        "date_calculation": "Detailed explanation of how dates were calculated"
                     }},
                     "endpoint": "/exact_endpoint_path_from_documentation",
                     "method": "HTTP_METHOD",
@@ -321,26 +323,119 @@ class HealthcareChatbot:
                 }}
 
                 === CRITICAL RULES ===
-                1. ONLY select endpoints that exist in the provided documentation
-                2. NEVER fabricate or assume endpoint parameters not in documentation
-                3. ALL required parameters MUST be included or listed as missing
-                4. Convert dates/times to ISO 8601 format (YYYY-MM-DDTHH:mm:ss)
-                5. If patient_id is required and not provided, add it to missing_required
-                6. Match endpoints by PURPOSE, not just keywords in the path
-                7. If multiple endpoints could work, choose the most specific one
-                8. If no endpoint matches, set endpoint to null and explain in reasoning
-
-                === EXAMPLES OF GOOD MATCHING ===
-                - User wants "patient records" → Use patient retrieval endpoint, not general search
-                - User wants to "schedule appointment" → Use appointment creation endpoint
-                - User asks "what appointments today" → Use appointment listing with date filter
-                - User wants to "update medication" → Use medication update endpoint with patient_id
-
-                Think step by step and be precise with your endpoint selection and parameter extraction.:""",
+                1. "غدا" or "بكره" MUST always equal current date + 1 day
+                2. Time expressions like "10 مساءً" MUST convert to 22:00
+                3. Verify all date calculations against {current_datetime}
+                4. Add "date_calculation" field to explain date conversions
+                5. All other rules from previous versions remain unchanged
+
+                Think step by step and be precise with your endpoint selection and parameter extraction.""",
             input_variables=["endpoints_documentation", "user_query", "detected_language",
                             "extracted_keywords", "sentiment_analysis", "conversation_history",
                             "current_datetime", "timezone", "user_locale"]
         )
+        ''' last one  '''
+        # self.router_prompt_template = PromptTemplate(
+        #     template="""
+        #     You are a precise API routing assistant. Your job is to analyze user queries and select the correct API endpoint with proper parameters.
+
+        #         === ENDPOINT DOCUMENTATION ===
+        #         {endpoints_documentation}
+
+        #         === USER REQUEST ANALYSIS ===
+        #         User Query: {user_query}
+        #         Language: {detected_language}
+        #         Keywords: {extracted_keywords}
+        #         Sentiment: {sentiment_analysis}
+        #         Current Context:
+        #         - DateTime: {current_datetime}
+        #         - Timezone: {timezone}
+        #         - User Locale: {user_locale}
+
+        #         === ROUTING PROCESS ===
+        #         Follow these steps in order:
+
+        #         STEP 1: INTENT ANALYSIS
+        #         - What is the user trying to accomplish?
+        #         - What type of operation are they requesting? (create, read, update, delete, search, etc.)
+        #         - What entity/resource are they working with?
+
+        #         STEP 2: DATE/TIME PROCESSING
+        #         - Identify any temporal expressions in the user query
+        #         - Convert relative dates/times using the current context:
+        #         * "اليوم" (today) = current date
+        #         * "غدا" (tomorrow) = current date + 1 day
+        #         * "أمس" (yesterday) = current date - 1 day
+        #         * "الأسبوع القادم" (next week) = current date + 7 days
+        #         * "بعد ساعتين" (in 2 hours) = current time + 2 hours
+        #         * "صباحًا" (morning/AM), "مساءً" (evening/PM)
+        #         - Handle different date formats and languages
+        #         - Account for timezone differences
+        #         - Convert to ISO 8601 format: YYYY-MM-DDTHH:MM:SS
+
+        #         STEP 3: ENDPOINT MATCHING
+        #         - Review each endpoint in the documentation
+        #         - Match the user's intent to the endpoint's PURPOSE/DESCRIPTION
+        #         - Consider the HTTP method (GET for retrieval, POST for creation, etc.)
+        #         - Verify the endpoint can handle the user's specific request
+
+        #         STEP 4: PARAMETER EXTRACTION
+        #         - Identify ALL required parameters from the endpoint documentation
+        #         - Extract parameter values from the user query
+        #         - Convert data types as needed:
+        #         - Dates/times to ISO 8601 format (YYYY-MM-DDTHH:mm:ss)
+        #         - Numbers to integers
+        #         - Set appropriate defaults for optional parameters if beneficial
+
+                
+
+        #         STEP 5: VALIDATION
+        #         - Ensure ALL required parameters are provided or identified as missing
+        #         - Verify parameter formats match documentation requirements
+        #         - Check that the selected endpoint actually solves the user's problem
+
+        #         === RESPONSE FORMAT ===
+        #         Provide your analysis and decision in this exact JSON structure:
+
+        #         {{
+        #             "reasoning": {{
+        #                 "user_intent": "Brief description of what the user wants to accomplish",
+        #                 "selected_endpoint": "Why this endpoint was chosen over others",
+        #                 "parameter_mapping": "How user query maps to endpoint parameters"
+        #             }},
+        #             "endpoint": "/exact_endpoint_path_from_documentation",
+        #             "method": "HTTP_METHOD",
+        #             "params": {{
+        #                 "required_param_1": "extracted_or_converted_value",
+        #                 "required_param_2": "extracted_or_converted_value",
+        #                 "optional_param": "value_if_applicable"
+        #             }},
+        #             "missing_required": ["list", "of", "missing", "required", "parameters"],
+        #             "confidence": 0.95
+        #         }}
+
+        #         === CRITICAL RULES ===
+        #         1. ONLY select endpoints that exist in the provided documentation
+        #         2. NEVER fabricate or assume endpoint parameters not in documentation
+        #         3. ALL required parameters MUST be included or listed as missing
+        #         4. Convert dates/times to ISO 8601 format (YYYY-MM-DDTHH:mm:ss)
+        #         5. If patient_id is required and not provided, add it to missing_required
+        #         6. Match endpoints by PURPOSE, not just keywords in the path
+        #         7. If multiple endpoints could work, choose the most specific one
+        #         8. If no endpoint matches, set endpoint to null and explain in reasoning
+
+        #         === EXAMPLES OF GOOD MATCHING ===
+        #         - User wants "patient records" → Use patient retrieval endpoint, not general search
+        #         - User wants to "schedule appointment" → Use appointment creation endpoint
+        #         - User asks "what appointments today" → Use appointment listing with date filter
+        #         - User wants to "update medication" → Use medication update endpoint with patient_id
+
+        #         Think step by step and be precise with your endpoint selection and parameter extraction.:""",
+        #     input_variables=["endpoints_documentation", "user_query", "detected_language",
+        #                     "extracted_keywords", "sentiment_analysis", "conversation_history",
+        #                     "current_datetime", "timezone", "user_locale"]
+        # )
+        # old one
         # self.router_prompt_template = PromptTemplate(
         #     template="""
         #     You are a precise API routing assistant. Your job is to analyze user queries and select the correct API endpoint with proper parameters.