Reply: Prosthesis−patient mismatch: No consensus yet
Bibliographic record
Abstract
The definition and clinical impact of prosthesis−patient mismatch (PPM) has been a matter of intense debate and controversy.1,2 In response to the manuscript “Why the Categorization of Indexed Effective Orifice Area Is Not Justified for the Classification of Prosthesis−Patient Mismatch,” Ternacle and Pibarot3 proposed a new algorithm to better categorize patients having true severe PPM. They have used solid arguments to demonstrate that although mean transprosthetic gradients (mΔp) may underestimate the presence of true severe PPM, the opposite occurs when using measured effective orifice area indexes (mEOAi) for the same purpose.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.011 | 0.090 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.003 | 0.002 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.003 | 0.005 |
| Scholarly communication | 0.005 | 0.014 |
| Open science | 0.005 | 0.005 |
| Research integrity | 0.037 | 0.054 |
| Insufficient payload (model declined to judge) | 0.012 | 0.014 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".