"My patient finally has a genetic diagnosis... but how do I treat it?"
~ Clinician caring for a rare disease patient


Too often, a genetic diagnosis is just the beginning of a long, uncertain search for therapies. The SAIL AI-Tx Challenge calls on innovators to build AI systems that turn diagnoses into actionable treatment options for rare disease patients.

Challenge Structure


Phase 0: Question Benchmark Curation

No Deadline: Open for Submissions

:pushpin: Overview

The question benchmark curation task will focus on soliciting questions from a community of experts that cover five major categories: (1) Established, Targeted Therapies, (2) Established, Supportive Therapies, (3) identification of and eligibility for Clinical Trials, (4) Drug Development and Repurposing, and (5) Variant Assessment, with an emphasis on information relevant to amenability for genetic therapies. Questions should be answerable using information in public databases and the scientific literature.

Submit your questions here - now open! We welcome contributions from clinical genetics and drug development experts, as well as from patients and families living with rare genetic conditions.


Phase 1: Question-Answering Task

Deadline: June 30, 2026 (submissions closed)

:pushpin: Overview

The question answering (QA) task will test AI models’ ability to answer the therapeutic questions about a patient’s genetic diagnosis that were curated in Phase 0.

Phase 1: Input Format

AI models will be provided with an input JSON object containing entries for hypothetical patients, including 1+ genetic variants, brief clinical context, and a question relevant to the individual/variant’s candidacy for therapeutics. Input tasks will be formatted as follows:

Field Description
id (string) Unique identifier for the task instance (used to link input and output).
patient.genotype (array of objects) List of one or more variant objects, where each object includes:
  • gene (string) – HGNC gene symbol
  • transcript (string) – RefSeq or Ensembl transcript identifier
  • variant_cdna (string) – cDNA HGVS notation
  • variant_protein (string) – Protein HGVS notation
  • zygosity (string) – e.g., "heterozygous", "homozygous", or "hemizygous"
Users can assume that patient.genotype corresponds to a true diagnosis.
patient.clinical_context (string) Brief free-text clinical description.
question.category (string) High-level question category from one of the following options:
  • Established_Targeted
  • Established_Supportive
  • Clinical_Trials
  • Drug_Development_and_Repurposing
  • Variant_Assessment
question.prompt (string) Direct, short-answer question about precision therapy relevance.
question.answer_format (string) Expected answer format from one of the following options:
  • binary
  • multiple_choice
  • numeric_match
  • string_match
question.date_submitted (string) Submission date for time-sensitive questions (e.g., “current”, “ongoing”).

For example,

{
  "id": "AITX-00123",
  "patient": {
    "genotype": [
      {
        "gene": "CFTR",
        "transcript": "NM_000492.4",
        "variant_cdna": "c.1521_1523del",
        "variant_protein": "p.Phe508del",
        "zygosity": "homozygous"
      }
    ],
    "clinical_context": "A 15-year-old male with a diagnosis of cystic fibrosis presents with chronic sinopulmonary disease characterized by persistent respiratory symptoms and recurrent infections. He also has exocrine pancreatic insufficiency requiring enzyme replacement therapy and exhibits features of male infertility consistent with congenital bilateral absence of the vas deferens (CBAVD)."
  },
  "question": {
    "category": "Established_Targeted",
    "answer_format": "binary",    
    "prompt": "Is the c.1521_1523del (F508del) variant eligible for treatment with Trikafta (elexacaftor/tezacaftor/ivacaftor)? Respond with “Yes” or “No”.",
    "date_submitted": "2024-12-10"  
  }
}

Questions are being crowdsourced from a community of experts in clinical genetics and drug development. We would love your contributions!

Phase 1: Output Format & Evaluation

Models must output a JSON object with fields for response and evidence justification. Responses will be auto-scored against reference answers using exact match criteria, while evidence fields provide transparency and factual grounding and may be reviewed by judges. Example specifications are shown below.

Field Description
id (string) Must match the corresponding input task id.
response (string) A concise answer (e.g., "Yes", "GOF", a number, drug name).
evidence (array of objects) List of one or more objects, where each object includes:
  • source (string) – A URL or reference supporting the answer (e.g., ClinVar, PubMed, OMIM)
  • time_accessed (int) – Unix Epoch of Coordinated Universal Time (UTC) when the source URL was accessed; e.g., returned by Python's time.time()
  • justification (string) – A brief (<500 characters) natural language explanation linking evidence.source to the response

For example,

{
  "id": "AITX-00123",
  "response": "Yes",
  "evidence": [
    {
      "source": "https://www.nature.com/articles/s41434-022-00347-0",
      "time_accessed": 1749151852,
      "justification": "Trikafta (elexacaftor/tezacaftor/ivacaftor) was approved by the FDA in 2019 for patients aged 12 and older with at least one copy of the p.Phe508del mutation. As this patient has two copies of the mutation and meets the age requirement, he is eligible for Trikafta therapy."
    },
    {
      "source": "https://www.accessdata.fda.gov/drugsatfda_docs/nda/2019/212273Orig1s000Approv.pdf",
      "time_accessed": 1749162712,
      "justification": "FDA approval letter for Trikafta states an indication for patients 12+ years old with at least one copy of the p.Phe508del mutation, which this patient meets."
    }
  ]
}

Phase 1 Model Submission through Hugging Face is now closed. We welcome your submissions for Phase 2!


Phase 2: Actionability Report Generation

Deadline: November 1, 2026

The Phase 2 Actionability Report Generation task is now open to the general public. (Previously, this task had been advertised as invite-only to top performers from Phase 1.) Hypothetical patients will be released on October 1, 2026.

:pushpin: Overview

The actionability report generation task tests an AI system’s ability to generate a comprehensive therapeutic report for a hypothetical patient. Unlike Phase 1’s short answers, this phase requires open-ended narrative synthesis covering established therapies, investigational options, and repurposing candidates, with optional inclusion of emerging targeted approaches (e.g., ASOs, gene therapies).

Phase 2: Input Format

See Phase 1: Question-Answering Task Input. The input format for Phase 2 is identical, except for the absence of the question fields.

Phase 2: Output Format

Submitted AI models must return a structured, markdown-formatted actionability report as a string within a JSON object. Details below.

Field Description
id (string) Must match the corresponding input task id.
report_markdown (string) Therapeutic actionability report following the required template.


Markdown Report Template

These requirements apply to every section of the report:

  1. Cite a verifiable source for every claim. Not necessarily a paper! A database record (UniProt, ClinVar, OMIM), drug label, guideline, or trial registry entry is fine, given a URL or accession. Same as Phase 1’s evidence.source.
  2. Where no prior report exists, show your reasoning instead. For instance, judging ASO amenability from variant position. Cite the underlying facts, and never cite a reference that doesn’t support the claim.
  3. State conditional actions. If missing patient information would change a recommendation, say so: “If seizures occur more often than once every three days, then XXX. Otherwise, YYY.”
  4. Don’t repeat across sections. Put each action in the single best-fitting section (an ASO approved for the patient’s specific variant and presentation belongs under Targeted Therapies, not again under Bespoke Therapies).
  5. Markdown formatting is required. Subheadings, bullets, links, and references beyond the template are encouraged.
Section Description
Summary The highest-value actions for this patient, ordered by tier, including conditional actions depending on patient-specific clinical variables. If key information that would alter therapeutic options is missing, this should be explicitly noted.
Established Actions Targeted Therapies Approved or guideline-supported treatments directed at the underlying molecular defect or disease mechanism.
Supportive Management* Standard-of-care pharmacologic or procedural management of symptoms and complications rather than the underlying defect.

*Surveillance is currently excluded.
Contraindications and Precautions Agents, doses, or procedures to avoid or modify because of the variant or disease, including anesthesia risks and clinically relevant medication interactions.
Emerging Actions Clinical Trial Eligibility Actively recruiting clinical trials for which the patient may qualify, with potential eligibility assessed against the available clinical and molecular criteria.
Off-label or Expanded-Access Therapies Existing therapies that could potentially be accessed outside standard approval for this indication, and for which human treatment precedent exists — at least one published report of the therapy administered to a patient in the same gene, disease, or variant context.
Hypothesized Actions Bespoke Therapies Assessment of the variant’s amenability to specific DNA- and RNA-directed therapeutic strategies (e.g., ASOs, gene therapies) not already identified as established or emerging, with a verdict and rationale for each.
Drug Repurposing Existing approved or investigational compounds for which no such human treatment precedent exists, but with a mechanistic rationale linking the intervention to the molecular defect.


For example,

{
  "id": "AITX-30001",
  "report_markdown": "## Therapeutic Actionability Report for Patient AITX-30001\n\n### Summary..."
}

Phase 2: Evaluation

Particularly challenging patient cases and anticipated answer keys are being developed by a panel of experts in clinical genetics, translational research, and drug development. User model submissions will be evaluated by these same expert panels. Reports will be scored based on the following dimensions:

Criterion Evaluation
Factual Accuracy Scientific and clinical accuracy of all claims in the response. Incorrect and misleading interpretations will be scored negatively, even if all other required key facts are present and correct.
Completeness Coverage of all prespecified report sections and all expected elements within each section, including whether relevant therapeutic actions, precautions, and uncertainties are identified and adequately addressed.
Evidence & Justification Whether conclusions are logically supported by appropriate, traceable evidence and/or key sources and citations, and whether those claims can actually be verified.
Prioritization & Calibration Whether actions are appropriately prioritized and placed within the prespecified evidence tiers (Established, Emerging, Hypothesized). Confidence and speculation should reflect the strength of the supporting evidence, with major uncertainties explicitly acknowledged.
Clinical Utility Whether findings are clearly translated into patient-specific actions or next steps.

Tutorials: links to databases and video tutorials on utilizing compute resources.
Submit Questions: example input questions which are being crowdsourced from a community of experts in clinical genetics and drug development.
FAQ: responses to questions regarding challenge scope and requirements.


Google logo

SAIL logo           Hugging Face logo           NEJM-AI logo