Overview
- Field: cs.AI, cs.SE
- Authors: Felipe Ocampo Osorio, Sebastián Andrés Cajas Ordoñez, Maximin Lange, Rafi Al Attrach, Sahil Kapadia, Zakaria Laouabdia Sellami, Angelo Antonio Talio, Leo Anthony Celi
- arXiv: 2609.10728
- With formulas and gold variables supplied and both routes reading the whole note, handing off to the solver is not a reliable advantage at 7B (75.31% vs 72.02%, paired +3.29 points, 95% calculator-cluster interval of [-3.49, 10.38]).
- At 32B it is an advantage (90.53% vs 83.47%, +7.05 [0.47, 14.60], clear of zero).
- The hand-written library is exact on its 440 supported cases but abstains elsewhere (40.0% overall).
- Adding an executor helps some open-weight models more than others even under matched formula, variable, and note access, and is not a substitute for verified formulas or reliable variable extraction either way.
Abstract
Large language models are unreliable at arithmetic, which is a problem for clinical calculators where a single numerical error changes the recommendation. The standard response is to hardcode each calculator as a validated function, one at a time. The authors test an alternative: the model does not calculate. Instead, it writes case-specific Python that a restricted local executor runs as a deterministic solver, and the model's task reduces to deciding how to use it.
They evaluate this Program-Solve interface on MedCalc-Bench Verified (1,100 cases, 55 calculators) against direct model arithmetic and a hand-written 22-calculator library, using Qwen2.5-7B and Qwen2.5-32B-AWQ, after auditing the benchmark's formulas against current clinical guidelines and flagging 16 of 55 with version, use, or coefficient concerns.
Key Findings
*Auto-collected on 2026-09-13.*