Automatically Extracting Numerical Results from Randomized Controlled Trials with LLMs

Automating meta-analysis of clinical trials (randomized controlled trials).

Our paper is available at: paper.pdf :page_facing_up:

:hammer_and_wrench: SETUP

Create conda environment from the environment.yml: conda env create -f environment.yml

Activate the conda environment: conda activate llm-meta-analysis

:bookmark_tabs: DATA

The human-annotated data is available in the data folder as both csv and json formats. The dev set has 10 RCTs with 43 number of total ICO triplets. The test set has 110 RCTs with 656 number of total ICO triplets. Additional dataset statistics can be found in evaluation/data/analyze_data.ipynb file.

:test_tube: EXPERIMENTS

Running Tasks

Evaluating models on different tasks for automating meta-analysis can be by running evaluation/run_task.py

There are 3 tasks:

• outcome_type: given an outcome of an randomized controlled trial (RCT), output the correct type. binary and continuous are the options. Although there are additional categories, these two options are most often found in RCTs.
• binary_outcomes: produce a 2x2 contingency table given the outcome, intervention, comparator, and also the abstract + results section of RCT.
• continuous_outcomes: produce a table of mean, standard deviation, and group sizes given the outcome, intervention, comparator, and also the abstract + results section of RCT.
• end_to_end: runs all 3 tasks. outputs from outcome_type is used for input for binary_outcomes and continuous_outcomes tasks.

Example script for running a specific task on GPT-3.5:

python3 evaluation/run_task.py --model gpt35 --task binary_outcomes --split test --output_path evaluation/outputs/binary_outcomes

Example script for running case study (mortality) on Mistral 7B:

python3 evaluation/run_task.py --model mistral7b --task end_to_end --input_path evaluation/data/meta_analysis_case_study.json --output_path evaluation/outputs/end_to_end --pmc_files_path evaluation/data/no_attributes_case_study_markdown_files

You can change the arguments to run different tasks and models.

Arguments of run_task.py:

• --model: model to evaluate ("gpt35", "gpt4", "mistral7B", "biomistral", "pmc-llama", "gemma7B", "olmo7B", "alpaca13B") - more details of the models can be found in MODELS.md
• --task: task name ("outcome_type", "binary_outcomes", "continuous_outcomes", "end_to_end")
• --split: whether to run "dev" or "test" split of the main evaluation dataset. This is required if input_path is not given
• --prompt: specific prompt to run. if no specific prompt is given, the first prompt for the given task is run. not available for end_to_end task. OPTIONAL
• --input_path: path where json file of the inputs for the model are saved. this is only needed if you want to run some data other than our annotated dataset. please format the input file similarly to annotated_rect_dataset.json
• --output_path: path of directory where json and csv files of the outputs from model should be saved
• --pmc_files_path: path of directory where all the pmc markdown files are saved. this is not required if you will be running our default evaluation dataset.
• --test: adding this flag will only run 10 randomly sampled examples from dataset. this is for debugging purposes.

Prompts

The prompts we used for each model type and task are available in the evaluation/templates folder. You will find the prompts in yaml files organized by model and task. Although the prompts were adjusted to maximize the performance of each model, the core content of the prompts are the same for each task.

Running Evaluation/Calculating Metrics

After getting all the outputs from the models, you can get the metrics by running evaluation/evaluate_output.py. This script will output several different types of metrics:

• number of times the model produced "unknown" answer when it was actually "known" according to reference answers
• number of times the reference produced "unknown" answers
• accuracy
  • exact match: an instance is counted as correct if all the parts are correct
  • partial match: an instance is counted as correct even if only part of the answers are correct
• f score (only for outcome_type task)
• percentage of model ICOs that have enough data to compute point estimates compared with reference data (only for binary_outcomes and continuous_outcome tasks)
• point estimates: log odds ratio for binary_outcomes task and standardized mean differences for continuous_outcome task
• mean absolute error and standard error of the mean absolute error (only for binary_outcomes and continuous_outcome tasks)
• total number of ICOs with chunked input (only for binary_outcomes and continuous_outcome tasks)

Example script for running evaluate_output.py:

python3 evaluation/evaluate_output.py --task binary_outcomes --output_path evaluation/outputs/binary_outcomes/gpt35_binary_outcomes_output_20240208.json --metrics_path evaluation/metrics/binary_outcomes/

Arguments of evaluate_output.py:

• --task: name of the task to evaluate and calculate metrics for
• --output_path: path where the model outputs are located. this should include both model outputs and reference answers.
• --metrics_path: path where the calculated metrics should be saved
• --pmc_files_path: path of directory where all the pmc markdown files are saved. this is not required if you will be running our default evaluation dataset. Only required if you want to run the case study example or other dataset.

:star: CITATION

@inproceedings{yun2024automatically,
  title={Automatically Extracting Numerical Results from Randomized Controlled Trials with Large Language Models},
  author={Yun, Hye Sun and Pogrebitskiy, David and Marshall, Iain J and Wallace, Byron C},
  booktitle={Machine Learning for Healthcare Conference},
  year={2024},
  organization={PMLR}
}