- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
Since building benchmarks and QA datasets is a lengthy and resourceful process, this paper proposes an automatic approach to do the same in the medical field. MedAgentBench is a system of LLM agents that takes as an input a user request and a raw medical dataset and produces a set of questions and answers relevant to the query and dataset.
The framework works in two stages: benchmark design and data construction. Benchmark design includes 4 agents (planner, solver, architect, and builder) and aims to provide template items. Data construction takes the template items, retrieves data samples from the existing datasets, annotates the goal of the template if it doesn’t exist in the dataset, and then provides a list of QA. Both building blocks are supported with a tool manager that includes existing tools and is backed by external tool search.
The framework works in pathology, CT, ECG, colonoscopy videos, and EHR. It is evaluated with a mixture of human input and LLM input.
Critical strengths
The scope of the paper covers five modalities under one framework and includes many tools as evidence that agents can use. The results show that MedBenchAgent provides considerable improvements to all five modality benchmarks.
Evaluation is rigorous and comprehensive. The combination of 3 LLMs, finetuning-based metrics, and human evaluation make the benchmark design more stable. The iterations that the annotator agent takes and training a field-level quality model encourage less mistakes coming from automation.
Critical weaknesses
The main concern is medical accuracy and reliability, which is claimed to be addressed in Fig.1 in the introduction. Since the framework is evaluated using design-related rubric, more focus on medical correctness is needed. This is apparent in the low focus on the clinical relevance in A.3: validation of templates and Table 8: LLM jury evaluation, compared to general design metrics. The usage of questions that are not validated based on their clinical reliability decreases the strength of the paper, especially that it is introduced to fill the gap in medical benchmark construction. Considering the sample size of the testing and training datasets, it is challenging to take human input on every sample. However, uncertainty metrics would be an asset and can help exclude any clinically inaccurate QA generation.
Moreover, it would be good to include the specialty of these medical experts, especially that the 5 modalities are in different fields, and some of them require more depth of expertise (cancer, colonoscopy).
It is also recommended to clarify the motivation of the paper as a one that builds benchmarks rather than evaluates models on QA. It gets misleading in some sections of the paper (for example: finetuning metric and A.6). Additionally, since all methods draw on the same existing datasets, what is the claimed gain: more clinically important questions, or better executed ones?
Questions for authors
-
In 3.1 - Input: Please give more examples of the user requests. How do the generated template items differ with high level user requests compared to detailed ones?
-
3.2 - Benchmark Design: How does the planner decide the relevant subtasks when the user request is high level? Does it know anything about the dataset?
-
3.2 - Benchmark Design: Does the builder know any information about the source data before generating the template items? For example, the builder could generate template items that need clinical data to get a correct answer, while the dataset only contains images.
-
If the quality model scores a specification before any template items exist, why do you think this improves correctness compared to evaluating the quality after the builder step?
-
In A.3 - Semantic validation: Where does the medical evidence come from? Also, the data dependence states that the item should not require annotation and should be answerable from the template alone. Since this needs to be true, why is the annotator then needed?
-
3.2 - Data Construction: How do you guarantee that the tools used for annotation are accurate? These models have inherent errors, even when they are trained on the data. How do you then create reliable questions without ensuring the tool accuracy? This is even riskier when the agent reaches the tool expansion step, where there is no supervision on the choice of the tool in the first place.
-
3.3 - Evidence-guided annotation: How is the relevance of the medical evidence validated? Even if it was relevant, it is good to keep track of the resources that instantiated items rely on, since medical resources can sometimes vary across regions.
-
Table 1: Why are the human approval percentages in the same range despite how challenging a domain is? For example, the FT accuracy is the lowest for CT analysis (expected), but the human approval percentage remains similar to the ECG understanding task and even higher than colonoscopy QA (0.68 accuracy)
-
Figure 5 – Please clarify why the example provided by SpatialMed is poor. The liver volume is of high clinical priority when assessing liver cancer, and the task design involves reasoning over anatomical structures (A. 1). Additionally, a generic medical reference is valid as long as it refers to normal liver volume.
-
Why is fine-tuning a valid approach for benchmark quality? It measures usefulness as training data and depends on similarity to the test set format.
-
What motivated your choice of the chosen retrieval models?