ix

main.py

@@ -241,94 +241,6 @@ class HealthcareChatbot:
 
 
         # API routing prompt (reuse existing router_prompt_template)
-        # self.router_prompt_template = PromptTemplate(
-        #     template="""
-        #     You are an API routing system that operates with strict adherence to documented specifications. Your sole purpose is to precisely match user requests to API endpoints based on the provided documentation.
-
-        #     === ABSOLUTE REQUIREMENTS ===
-        #     1. ENDPOINT SELECTION MUST BE GROUNDED IN DOCUMENTATION
-        #     2. ALL REQUIRED PARAMETERS MUST BE ACCOUNTED FOR
-        #     3. RESPONSE STRUCTURE MUST REMAIN UNCHANGED
-
-        #     === INPUT DATA ===
-        #     Current Context:
-        #     - DateTime: {current_datetime}
-        #     - Timezone: {timezone}
-        #     - User Locale: {user_locale}
-
-        #     API Documentation:
-        #     {endpoints_documentation}
-
-        #     User Request:
-        #     - Query: {user_query}
-        #     - Language: {detected_language}
-        #     - Keywords: {extracted_keywords}
-        #     - Sentiment: {sentiment_analysis}
-
-        #     === PROCESSING INSTRUCTIONS ===
-        #     1. Analyze the user request to determine:
-        #     - Core intent (what they want to accomplish)
-        #     - Target entity/resource
-        #     - Required operation type (CRUD)
-
-        #     2. Examine the API documentation to:
-        #     - Identify all endpoints related to the target entity
-        #     - Verify the endpoint's purpose matches the user intent
-        #     - Confirm the HTTP method aligns with the operation type
-
-        #     3. For the selected endpoint:
-        #     - Extract ALL documented parameters
-        #     - Determine parameter sources (query, history, or defaults)
-        #     - Validate parameter formats against specifications
-        #     - Convert dates/times to ISO 8601 format (YYYY-MM-DDTHH:mm:ss)
-
-        #     4. Validate your selection:
-        #     - The endpoint must directly satisfy the user's primary need
-        #     - All required parameters must be present or explicitly listed as missing
-        #     - No undocumented parameters may be included
-
-        #     === OUTPUT FORMAT ===
-        #     {
-        #         "reasoning": {
-        #             "user_intent": "[concise description]",
-        #             "endpoint_selection": "[exact documentation reference]",
-        #             "parameter_analysis": "[source and validation for each parameter]"
-        #         },
-        #         "endpoint": "/documented/endpoint/path",
-        #         "method": "HTTP_METHOD",
-        #         "params": {
-        #             "param1": "value"  // only if properly sourced
-        #         },
-        #         "missing_required": [
-        #             "param1"  // if required but unavailable
-        #         ],
-        #         "confidence": 0.95  // 1.0 when all parameters are validated
-        #     }
-
-        #     === STRICT ENFORCEMENT ===
-        #     - Empty params objects are prohibited when documentation requires parameters
-        #     - All missing required parameters must be explicitly listed
-        #     - Confidence scores must reflect parameter completeness
-        #     - Date/time formatting must be exact
-        #     - Never assume undocumented functionality
-
-        #     === ERROR CONDITIONS ===
-        #     1. If no endpoint matches:
-        #     - Set "endpoint" to null
-        #     - Explain in "reasoning"
-
-        #     2. If critical parameters are missing:
-        #     - List ALL in "missing_required"
-        #     - Reduce confidence score accordingly
-
-        #     Your response will be validated against these requirements before being accepted.
-        #     """,
-        #     input_variables=[
-        #         "endpoints_documentation", "user_query", "detected_language",
-        #         "extracted_keywords", "sentiment_analysis", "conversation_history",
-        #         "current_datetime", "timezone", "user_locale"
-        #     ]
-        # )
         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.
@@ -341,6 +253,10 @@ class HealthcareChatbot:
                 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:
@@ -359,7 +275,9 @@ class HealthcareChatbot:
                 STEP 3: PARAMETER EXTRACTION
                 - Identify ALL required parameters from the endpoint documentation
                 - Extract parameter values from the user query
-                - Convert data types as needed (dates to ISO 8601, numbers to integers, etc.)
+                - 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 4: VALIDATION
@@ -391,7 +309,7 @@ class HealthcareChatbot:
                 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)
+                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
@@ -405,8 +323,87 @@ class HealthcareChatbot:
 
                 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"]
+                            "extracted_keywords", "sentiment_analysis", "conversation_history",
+                            "current_datetime", "timezone", "user_locale"]
         )
+        # 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}
+
+        #         === 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: 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 3: PARAMETER EXTRACTION
+        #         - Identify ALL required parameters from the endpoint documentation
+        #         - Extract parameter values from the user query
+        #         - Convert data types as needed (dates to ISO 8601, numbers to integers, etc.)
+        #         - Set appropriate defaults for optional parameters if beneficial
+
+        #         STEP 4: 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"]
+        # )
 
         # Conversational response prompt
         self.conversation_template = PromptTemplate(