Language Support

The Knidian AI API supports multiple languages for clinical history analysis, allowing healthcare professionals around the world to utilize our differential diagnosis capabilities in their native language.

Supported Languages

Currently, the Knidian AI API supports the following languages:

Language Code	Language Name
en	English
es	Spanish
pt	Portuguese

Language Detection

If you don't specify a language in your API request, the system will attempt to automatically detect the language of the provided clinical history. However, for optimal results, we recommend explicitly specifying the language using the language parameter.

Using the Language Parameter

To specify the language of your clinical history, include the language parameter in your API request:

{
  "clinical_history": "Un hombre de 45 años presenta dolor en el pecho, dificultad para respirar y fatiga durante los últimos 3 días. El dolor se describe como una presión que se irradia al brazo izquierdo y empeora con el esfuerzo.",
  "language": "es"
}

Language-Specific Considerations

English (en)

English is the primary language of the Knidian AI API and generally provides the most comprehensive results. When using English:

• Standard medical terminology is well-recognized
• Both American and British English spellings are supported
• Medical abbreviations common in English-speaking countries are recognized

Spanish (es)

When using Spanish:

• Include accent marks and proper Spanish punctuation for optimal results
• Spanish medical terminology is recognized, but avoid highly regional medical slang
• Common Spanish medical abbreviations are supported

Portuguese (pt)

When using Portuguese:

• Both European and Brazilian Portuguese variants are supported
• Include proper Portuguese diacritical marks for optimal results
• Common Portuguese medical abbreviations are supported

Best Practices for Multilingual Use

1. Be Consistent: Use a single language throughout the clinical history
2. Avoid Code-Switching: Mixing languages within the same clinical history may reduce accuracy
3. Use Standard Terminology: Stick to standard medical terminology in your chosen language
4. Include Context: Cultural or regional health practices may need additional explanation
5. Check Translations: If translating from another language, verify medical terms are correctly translated

Language-Specific Response

The API will return the differential diagnosis in the same language as the input clinical history. This includes:

• Disease names and descriptions
• Explanations of why each diagnosis is being considered
• Triage justifications and recommendations
• Diagnostic test recommendations
• Standard of care information
• Medication information

Example: Spanish Request and Response

Request

{
  "clinical_history": "Un hombre de 45 años presenta dolor en el pecho, dificultad para respirar y fatiga durante los últimos 3 días. El dolor se describe como una presión que se irradia al brazo izquierdo y empeora con el esfuerzo.",
  "language": "es"
}

Response (Simplified)

{
  "diagnosis": {
    "diseases": [
      {
        "name": "Infarto Agudo de Miocardio",
        "icd10_code": "I21.9",
        "probability": 0.85,
        "why": "El paciente presenta síntomas clásicos de infarto de miocardio: dolor en el pecho que se irradia al brazo izquierdo, dificultad para respirar y fatiga. El dolor se describe como una presión y empeora con el esfuerzo.",
        "diagnostic_tests": [
          "ECG de 12 derivaciones",
          "Niveles de troponina cardíaca",
          "Hemograma completo",
          "Panel metabólico básico",
          "Radiografía de tórax"
        ],
        "category": "most-likely"
      }
    ]
  },
  "triage": {
    "triage_level": "RED",
    "triage_justification": "Los síntomas del paciente son consistentes con un síndrome coronario agudo, que es una emergencia potencialmente mortal que requiere atención médica inmediata.",
    "triage_recommendation": "Evaluación inmediata en el departamento de emergencias con monitoreo cardíaco, ECG de 12 derivaciones y biomarcadores cardíacos."
  }
}

Future Language Support

We are continuously working to expand our language support. If you require support for a language not currently listed, please contact our support team to discuss your needs.