Multilingual Dietary Reasoning

Summary and intended purpose

Scenario families where the correct output depends on locale: available foods, naming conventions, cultural dietary practices, and language. Built on bilingual nutrition workflow experience; coverage for additional languages is scoped per engagement.

Target training or evaluation tasks

• Producing locale-appropriate food substitutions under clinical constraints
• Maintaining constraint adherence across languages
• Respecting stated cultural or religious dietary practices

Clinical scope

• Adult clinical nutrition tasks with locale parameters
• English and Spanish explored in R&D; other languages by engagement

Example record schema

{
  "example_id": "mdr-0001-synthetic",
  "specialty": "clinical_nutrition",
  "task_type": "locale_adapted_substitution",
  "language": "es",
  "locale": "es-MX",
  "scenario": {
    "summary": "Tarea de sustitución de alimentos para un adulto con una restricción de sodio y preferencias alimentarias regionales declaradas.",
    "stated_constraints": [
      "sodium_limit",
      "regional_food_preference"
    ]
  },
  "candidate_response": {
    "substitutions": "<structured_substitutions>",
    "constraints_applied": [
      "sodium_limit",
      "regional_food_preference"
    ]
  },
  "automated_checks": {
    "schema_valid": true,
    "constraints_referenced": true,
    "locale_food_refs_ok": true
  },
  "review_status": "automated_only",
  "generation_version": "gen-v3"
}

Generation methodology

1. 01Locale parameters are part of the scenario specification, not post-hoc translation.
2. 02Candidate outputs are checked for constraint adherence independently of language.
3. 03Food-reference consistency is screened against locale-specific lists where available.

Validation information

• Reviewer language and cultural familiarity are matched to each locale family.
• Review coverage is agreed per engagement.

Known limitations

• Only languages explicitly listed for a delivered dataset are supported; others are not implied.
• Cultural appropriateness checks are specification-driven and require matched reviewers to validate.

Licensing and access process

Licence status: Scoped per engagement. Access is sales-assisted. Licensing is handled by agreement, based on data provenance, rights, permitted uses, delivery, and commercial terms.

1. Step 1Specify target languages, locales, and the clinical constraints that must hold across them.
2. Step 2Feasibility review including reviewer availability for each locale.
3. Step 3Scoped generation and agreed review coverage.