Computed from this object's own state — a structural condition is unmet. This is not a fixed disclaimer: the conditions below are each testable, and a build in which they are met renders READY.
In Lefamulin versus moxifloxacin in community-acquired bacterial pneumonia, what is the effect on versus moxifloxacin (with or without linezolid in LEAP 1) on early clinical response?
In this section: Registration and administrative information (PROSPERO field set)
| Review title | Lefamulin versus moxifloxacin in community-acquired bacterial pneumonia |
|---|---|
| Review question (PICO) | In Lefamulin versus moxifloxacin in community-acquired bacterial pneumonia, what is the effect on versus moxifloxacin (with or without linezolid in LEAP 1) on early clinical response? |
| Population | Not shown — no prospectively-frozen v1.0 protocol describes this review, so an independent criterion is withheld rather than invented. State: NO_PROTOCOL. |
| Intervention | Not shown — no prospectively-frozen v1.0 protocol describes this review, so an independent criterion is withheld rather than invented. State: NO_PROTOCOL. |
| Comparator | Not shown — no prospectively-frozen v1.0 protocol describes this review, so an independent criterion is withheld rather than invented. State: NO_PROTOCOL. |
| Background / rationale | Not recorded — this object holds no background field, and an introduction generated without one would be argument that no source in this review supports |
| Information sources | 0 source layers, listed on the Extraction tab |
| Search strategy | The executed strings, datetimes, filters and hit counts are on the Search tab |
| Study selection process | Not recorded — this object holds no screening record, so the selection process cannot be described |
| Number of screeners | Not recorded — this object records no screener count |
| Data extraction items | Extracted per trial on this object: registry id. Fields not listed here were not extracted. |
| Outcomes and prioritisation | early clinical response |
| Risk of bias method | RoB 2, per result, five domains — see the risk-of-bias table below |
| Synthesis methods | Pooled under random-effects with the REML estimator. Whether they were prespecified is not recorded on this object. |
| Subgroup analyses | Not recorded — this object records no subgroup-analysis field at all, so whether any were prespecified is UNKNOWN -- which is not the same as none having been |
| Meta-bias assessment | Not recorded — no funnel, Egger or Peters value is held on this object, so no meta-bias assessment is claimed |
| Certainty assessment | GRADE, recorded for 1 outcome(s) (GRADE, following the Cochrane Handbook chapter 14. Randomised evidence starts HIGH and is rated down with reasons.). The ratings are on the Certainty tab. |
| Funding | Not recorded — no funding statement is recorded for this review |
| Competing interests | Not recorded — no declaration is recorded |
| Built | 2026-08-18 |
| Schema | 2 |
In this section: Extraction — every datum linked to its source · Outcome primary · Recompute envelope — the headline against the rows shown · Outcome primary · Absolute effect at a baseline risk the reader chooses · Risk of bias (RoB-2) · Overall judgement per trial · Inter-assessor agreement · References · Included studies · Regulatory documents · Methods and guidance · Sources · early clinical response · early clinical response · Pooled result · Contributing trials
Every per-trial value this review pools, with a link to the record it came from. Derived by ssot/projectors_evidence.py for any topic whose rows carry an NCT, a PMID, an ISRCTN or a source URL.
2 of 2 rows are linked to a source; 0 carry no identifier and are shown as unlinked rather than omitted.
| Trial | Source | Linked via | Effect | Counts as posted | Provenance |
|---|---|---|---|---|---|
| LEAP 1 | NCT02559310 | source_url | RR 0.9683 (0.9123 to 1.0276) | experimental_events 241, experimental_n 276, comparator_events 248, comparator_n 275 | REGISTRY -- ClinicalTrials.gov posted results, read 2026-08-18 |
| LEAP 2 | NCT02813694 | source_url | RR 1.0006 (0.9556 to 1.0476) | experimental_events 336, experimental_n 370, comparator_events 334, comparator_n 368 | REGISTRY -- ClinicalTrials.gov posted results, read 2026-08-18 |
Derived by ssot/recompute_envelope.py. The pooled number is recomputed from the per-trial rows this same page shows, so the arithmetic between the extraction table and the headline is checkable with no tool the reader does not already have.
| Source | Point | 95% CI |
|---|---|---|
| stored on this page | 0.9884 | — |
| fixed effect, recomputed from the rows | 0.9884 | 0.9531 to 1.025 |
| DerSimonian-Laird, recomputed | 0.9884 | 0.9531 to 1.025 |
AGREES -- the stored point lies between the fixed-effect and DerSimonian-Laird estimates computed from the rows this page shows.
Scale used: log. Declared estimator: REML.
DerSimonian-Laird is biased at k below about ten and this project uses REML. DL is here only to WIDEN the envelope so a REML point falls inside it; it is never offered as the review's estimate.
Derived by ssot/absolute_effect.py for any topic with a pooled ratio measure AND a declared indirectness argument. Where either is missing it DECLINES with a reason rather than emitting a table the review has not licensed — a ratio becomes an absolute effect only against a baseline risk, and a baseline risk belongs to a population.
Variant:
Unit assessed: —
Assessor 1: (anthropic family). Assessor 2: (openai family).
| Trial | Result assessed | Domain | Assessor 1 (anthropic) | Assessor 2 (openai) | Agreed |
|---|---|---|---|---|---|
| LEAP 1 | early clinical response | D1 D1_randomisation_process | no information | no information | yes |
| LEAP 1 | early clinical response | D2 D2_deviations_from_intended_intervention | no information | no information | yes |
| LEAP 1 | early clinical response | D3 D3_missing_outcome_data | no information | no information | yes |
| LEAP 1 | early clinical response | D4 D4_measurement_of_the_outcome | LOW | LOW | yes |
| LEAP 1 | early clinical response | D5 D5_selection_of_the_reported_result | LOW | LOW | yes |
| LEAP 2 | early clinical response | D1 D1_randomisation_process | no information | no information | yes |
| LEAP 2 | early clinical response | D2 D2_deviations_from_intended_intervention | no information | no information | yes |
| LEAP 2 | early clinical response | D3 D3_missing_outcome_data | no information | no information | yes |
| LEAP 2 | early clinical response | D4 D4_measurement_of_the_outcome | LOW | LOW | yes |
| LEAP 2 | early clinical response | D5 D5_selection_of_the_reported_result | LOW | LOW | yes |
| Trial | Result assessed | Assessor 1 (anthropic) | Assessor 2 (openai) | Agreed |
|---|---|---|---|---|
| LEAP 1 | early clinical response | some concerns | no overall judgement reached — this assessor answered “no information”, which RoB 2 defines as a response to a signalling question and not as one of the three overall categories (low, some concerns, high) | NO |
| LEAP 2 | early clinical response | some concerns | no overall judgement reached — this assessor answered “no information”, which RoB 2 defines as a response to a signalling question and not as one of the three overall categories (low, some concerns, high) | NO |
This assessment is DUAL — two assessors from different model families, the second asked blind. The agreement rate is withheld pending adjudication. Both readers were given this review’s decision rule; an earlier version of this sentence said the blinding had withheld it, and that was wrong. What the 10 domain comparison(s) show is a reading difference that runs in OPPOSITE directions by domain — on domains 1 to 3 the second assessor more often declines to judge at all, and on domains 4 and 5 it more often judges low. A single agreement rate averages those two behaviours into one number that describes neither. Both assessors’ per-result judgements are shown in the table above, unadjudicated, and neither is this review’s finding. No adjudication has been performed, so this review holds no final risk-of-bias judgement for these results.
| Layer | Source | How it was obtained |
|---|
RR 0.9884 (0.953 to 1.025), 95% interval
early clinical response. random-effects, estimator REML, k = 2.
τ² 0 · I² 0% · Q 0.7313 on 1 df
Checked and clean. Read from the registrations on 2026-08-21: NCT02559310 registers 'Early Clinical Response (ECR)' (population: ECR); NCT02813694 registers 'Early Clinical Response (ECR)' (population: ECR). Both trials register the same primary in the same population, so this pool does not cross an analysis-population boundary. Recorded because a check that only speaks when it finds something cannot be told from a check that was never run.
Whether these are non-inferiority designs is not established: the registration fields fetched do not use the word, and a pooled ratio from non-inferiority trials answers a different question from a superiority pool. Unresolved, not assumed.
The experimental arms are not the same intervention. Read from the pooled analysis (PMID 33964925, BMC Pulm Med 2021): LEAP 1 randomised patients to intravenous lefamulin 150 mg every 12 hours for 5-7 days with an optional intravenous-to-oral switch; LEAP 2 randomised to oral lefamulin 600 mg every 12 hours for 5 days. This object pools them as one intervention.
LEAP 1's comparator is moxifloxacin with OR without linezolid and LEAP 2's is moxifloxacin alone -- corroborated from the registered arm groups. This object's own question already states the comparator difference; The route and duration difference was not previously recorded.
Not that the pool is invalid -- an intravenous-to-oral switch and an oral course of the same drug are a defensible thing to combine, and the published analysis combines them. What is claimed is that a reader meeting one ratio should know the two arms differed in route, duration and comparator, and no field said so.
| Trial | Analysed treatment / control |
RR (95% CI), or events | Source of this cell |
|---|---|---|---|
| LEAP 1 NCT02559310 | 276 / 275 | RR 0.9683 (95% CI 0.9123 to 1.028) | REGISTRY -- ClinicalTrials.gov posted results, read 2026-08-18 · source · read 2026-08-18 recovered from results.by_outcome.primary.per_trial[0]; this trial carries no by_outcome entry on the object, so the cell-level provenance the other rows show is not held for it. |
| LEAP 2 NCT02813694 | 370 / 368 | RR 1.001 (95% CI 0.9556 to 1.048) | REGISTRY -- ClinicalTrials.gov posted results, read 2026-08-18 · source · read 2026-08-18 recovered from results.by_outcome.primary.per_trial[1]; this trial carries no by_outcome entry on the object, so the cell-level provenance the other rows show is not held for it. |
Registered endpoint definitions were read from every contributing registration on 2026-08-18; this text is the object's own record of them.
In this section: early clinical response · Forest plot · Visual abstract · Risk of bias, both assessors · GOSH · Trial-sequential analysis · Meta-regression
Drawn from the same stored estimates the table above lists. Box area is proportional to inverse-variance weight.
x-axis range
⬇ SVG (vector) 1 KB ⬇ PNG 4500x920 97 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: 24ca335922a1c00c), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — forest_fit.eps, 3 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — forest_fit.tiff, 12,129 KB.
⬇ SVG (vector) 1 KB ⬇ PNG 4500x920 95 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: 65330f87fc47d88f), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — forest_w1.eps, 3 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — forest_w1.tiff, 12,129 KB.
⬇ SVG (vector) 1 KB ⬇ PNG 4500x920 93 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: ad112e93739aff35), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — forest_w2.eps, 3 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — forest_w2.tiff, 12,129 KB.
⬇ SVG (vector) 1 KB ⬇ PNG 4500x920 96 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: 31391bdeb5a770a5), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — forest_w3.eps, 3 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — forest_w3.tiff, 12,129 KB.
Changing the range moves the axis window only. The guides stay labelled with the null and the extremes of the plotted intervals, so no plotted value and no printed number differs between these views — and that is checked at build time, not asserted.
⬇ SVG (vector) 2 KB ⬇ PNG 4500x2100 263 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: e4a136bad4fee162), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — visual-abstract.eps, 4 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — visual-abstract.tiff, 27,685 KB.
Projected from the canonical object, so it carries the same k, the same pooled estimate and the same interval as the paper and cannot drift from them. The interval is drawn CROSSING the no-difference line because it does: 0.953 to 1.025 spans 1. A graphical abstract travels without its caption, and one showing a favourable point estimate without showing that its interval includes no effect would overstate a null result.
⬇ SVG (vector) 4 KB
Only the vector format is offered for this figure, by choice: it is line art — discrete marks, glyphs and labels — which SVG reproduces exactly at any size, so a raster would add weight without adding fidelity. The build was able to rasterise; it was asked not to.
Every cell carries BOTH independent cross-family assessments and they are not reconciled: showing one column would be a reconciliation presented as an observation. Glyph as well as colour, so the panel survives greyscale printing and colour-blind reading. A trial with no judgement is shown as a row of not-assessed markers rather than omitted, so a gap in the assessment cannot be mistaken for a clean assessment. Agreement as measured: {'per domain agreed': 10, 'per domain total': 10, 'per domain rate pct': 100.0, 'overall agreed': 0, 'overall total': 2, 'overall is derived': True, 'recomputed from the stored judgements': True, 'why recomputed': 'The stored disagreement tallies were frozen as text and 12 of 22 no longer match the judgements in the object -- a later guidance pass moved 51 the randomisation process judgements and the tallies were never recomputed. This is derived from what the object holds now.'}.
⬇ SVG (vector) 1 KB ⬇ PNG 3500x540 81 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: 9091822e99aa8781), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — gosh.eps, 2 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — gosh.tiff, 5,537 KB.
Deliberately not drawn. Every subset meta-analysis of 2 trials is 3 points; a cloud that small cannot show the multimodality GOSH exists to reveal, and a reader would take the picture as evidence of its absence.
⬇ SVG (vector) 1 KB ⬇ PNG 3500x650 87 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: 25ed9800fdf56614), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — tsa.eps, 2 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — tsa.tiff, 6,665 KB.
TSA boundaries depend entirely on a target information size that must be pre-specified. This review's protocol registers none, so any boundary drawn here would be a parameter chosen after seeing the data -- which is the practice TSA exists to protect against.
⬇ SVG (vector) 1 KB ⬇ PNG 3500x540 87 KB
All raster formats were generated at build time from the same SVG as the graphic above (SHA-256, first 16 hex characters: e35ec93bbc9a1c10), at 600 dpi for a 6-inch print width, on a white ground.
Submission formats written to the figures directory, not embedded here because an uncompressed 600 dpi TIFF is tens of megabytes: EPS (vector, journal's first choice for line art) — bubble.eps, 2 KB; TIFF (uncompressed, 600 dpi -- journal fallback) — bubble.tiff, 5,537 KB.
The protocol pre-specifies no moderator, and at k = 2 a meta-regression would be fitted on 2 points. Not drawn rather than drawn with a caveat: a bubble plot invites reading a slope, and there is no slope here that any reader should read.
In this section: Summary of findings · Reproducibility artifact · Other recorded qualifications · Judgement register — what a harness cannot derive · Outcome primary — 0 of 8 declared, 7 of 8 undeclared
| Outcome | k | Pooled effect | Certainty |
|---|---|---|---|
| early clinical response | 2 | RR 0.988 (0.953 to 1.02) | Pending1 |
| Canonical object | — |
|---|---|
| Registered at | — — |
| Schema | 2 |
| Object last updated | 2026-08-18 |
| Source object SHA-256, first 16 hex characters | b7a8fdbb60370481 |
| Page generated | 2026-09-04 00:00 UTC |
| Generator build | 66c1ed934 (uncommitted generator changes -- NOT REPRODUCIBLE from this stamp alone). The standard this page was built to is NOT ESTABLISHED: this object carries no build_stamp, so the version above is the standard that exists now, not the one this page was built against. |
This page CANNOT be rebuilt from what is recorded here: no canonical object is recorded and no registered commit is recorded. Each figure on the Analysis tab downloads as an SVG carrying exactly the values shown.
Statements this review records about the limits of what it establishes, which are not shown elsewhere on this page. They are reproduced from the object verbatim and are not summarised.
| Why this topic pools when most do not | Of 62 infectious-disease topics, this is one of the few that survives all four limbs without reconciliation: the same experimental drug in the experimental arm of both trials, the same active comparator, the same registered primary outcome measured the same way, and the same infection. The eleven topics closed on 2026-08-18 failed because one of those four differed. This is what a poolable topic looks like. |
|---|---|
| What this does not establish | Not that either trial is free of bias -- no risk-of-bias assessment is recorded, and a pooled estimate without one is an arithmetic result, not a graded finding. Not non-inferiority or superiority: both trials were designed as non-inferiority studies against an active comparator, and a risk ratio near 1 with an interval spanning 1 is the expected result of a successful non-inferiority trial rather than evidence of no difference. Not that the pooled interval is reliable at k=2 -- see the Hartung-Knapp interval, which is the honest width. Not agreement with any published synthesis; none has been checked. |
| A the analysis population was checked and is consistent | Checked and clean. Read from the registrations on 2026-08-21: NCT02559310 registers 'Early Clinical Response (ECR)' (population: ECR); NCT02813694 registers 'Early Clinical Response (ECR)' (population: ECR). Both trials register the same primary in the same population, so this pool does not cross an analysis-population boundary. Recorded because a check that only speaks when it finds something cannot be told from a check that was never run. |
| A the two trials differ in route and duration not only in comparator | The experimental arms are not the same intervention. Read from the pooled analysis (PMID 33964925, BMC Pulm Med 2021): LEAP 1 randomised patients to intravenous lefamulin 150 mg every 12 hours for 5-7 days with an optional intravenous-to-oral switch; LEAP 2 randomised to oral lefamulin 600 mg every 12 hours for 5 days. This object pools them as one intervention. |
| B and the comparators differ as this object already says | LEAP 1's comparator is moxifloxacin with OR without linezolid and LEAP 2's is moxifloxacin alone -- corroborated from the registered arm groups. This object's own question already states the comparator difference; The route and duration difference was not previously recorded. |
| C what is not claimed | Not that the pool is invalid -- an intravenous-to-oral switch and an oral course of the same drug are a defensible thing to combine, and the published analysis combines them. What is claimed is that a reader meeting one ratio should know the two arms differed in route, duration and comparator, and no field said so. |
| Its question as an alternative reading | Lefamulin versus moxifloxacin in community-acquired bacterial pneumonia versus moxifloxacin (with or without linezolid in LEAP 1) on early clinical response? |
| What is not established | The concealment mechanism is not on the registry and no publication was read. LOW is scored on the recorded allocation, not on a mechanism nobody here has seen. |
| Why this is not an adjudicated dispute | A blind second assessor from a different model family disagreed with this domain on 89% of judgements across 22 topics. That would ordinarily be a dispute to adjudicate. It is not one: the tool's own text names this exact evidential situation -- a bare statement that a study was randomised -- and prescribes the answer. The second assessor is not being deferred to; the guidance is being applied. |
| What the registry gives and does not | A ClinicalTrials.gov design module records `allocation: Randomized`. It carries no sequence-generation method and no allocation-concealment mechanism. The original judgement's own note said so before scoring LOW. |
| How this maps to the tool s algorithm | The tool maps 'No information' on 1.1 and 1.2 with no baseline concern to a domain judgement of some concerns. This project writes no information on the domain when it could not be judged from the sources read, and caps the overall at some concerns. Same place, and it keeps 'we could not judge this' distinguishable from 'we judged it and had concerns'. |
| What does not change | No overall rating and no GRADE CERTAINTY moves. All 51 judgements were already capped at some concerns or HIGH by another no information domain. |
| This does not replace the stored judgement | This is the judgement the published algorithm proposes from the signalling responses named here. It does not replace the stored `judgement` beside it, and nothing reads it yet. The tool itself says its algorithms "provide proposed judgements, but users should verify these and change them if they feel this is appropriate" -- so this is an input to a person, not an output to a reader. |
| And it bounds a finding of ours | Class 94 records assessor 2 saying no information on the randomisation process/deviations from the intended intervention/missing outcome data `100 of 100`. Measured across all 23 topics now stored that is 239 of 243, and all four exceptions are the randomisation process=some concerns on `agyw-hiv-prep-review` and `cab-prep-hiv-review` -- two of the three topics asked under the earlier prompt build, the one whose reply ids are bare NCTs. Under that build it is 4 of 6; under the later build 0 of 75. The 100% was measured on the later build's topics. The two-defaults mechanism stands; its universality does not, and what varies with it is the prompt. |
| The rate is still conditional on the same allow list | Both numbers are conditional on the fact list in THE_ALLOW_LIST_THE_RATE_IS_CONDITIONAL_ON above. Neither is a rate of agreement between assessors in general. |
| Inconsistency read from the stored refit | The heterogeneity numbers cited above are quoted from `results.by_outcome.primary.r_output`, which is this object's own captured model output, not a re-derivation. |
| Scope | Early Clinical Response at 96 +/- 24 hours -- the same endpoint this object pools |
| The finding of this comparison | The experimental arms are not the same intervention. Read from the pooled analysis (PMID 33964925, BMC Pulm Med 2021): LEAP 1 randomised patients to intravenous lefamulin 150 mg every 12 hours for 5-7 days with an optional intravenous-to-oral switch; LEAP 2 randomised to oral lefamulin 600 mg every 12 hours for 5 days. This object pools them as one intervention. LEAP 1's comparator is moxifloxacin with OR without linezolid and LEAP 2's is moxifloxacin alone -- corroborated from the registered arm groups. This object's own question already states the comparator difference; The route and duration difference was not previously recorded. Not that the pool is invalid -- an intravenous-to-oral switch and an oral course of the same drug are a defensible thing to combine, and the published analysis combines them. What is claimed is that a reader meeting one ratio should know the two arms differed in route, duration and comparator, and no field said so. |
Judgements a harness cannot derive, per outcome, with the alternative and its consequence. DERIVED AT BUILD TIME by ssot/topic_judgements.py — this table is not written for this topic and the same code produces it for every topic.
| Judgement | State | Decided | Decided by | Alternative | If the alternative had been taken |
|---|---|---|---|---|---|
QUESTION_PICO | UNDECLARED | NOT DECLARED -- missing axes: population, intervention, comparator, outcome | NOBODY. The review question exists as prose and has never been resolved into axes. | Declare it, axis by axis. | ⛔ WITHOUT IT THE INDIRECTNESS DOMAIN CANNOT BE COMPARED AXIS BY AXIS AT ALL. Prose cannot be compared with prose. Any indirectness rating on this topic is therefore a stored judgement or an absence, never a derivation. |
ELIGIBILITY_RULE | UNDECLARED | NO RULE STATES BOTH A COMPARATOR AND AN OUTCOME CRITERION. comparator named: False; outcome named: False | ⚠️ ENACTED RATHER THAN DECLARED. Where a screen tests only phase and randomisation, the comparator and outcome criteria are applied as per-case verdicts, and a harness cannot regenerate the rule from what is written. | State the rule. | ⛔ A CANDIDATE COUNT IS NOT AN ELIGIBILITY DECISION. A drug-only concept block returned an identical 125 candidates across six colchicine topics in this corpus; the count says nothing about which of them belong. |
COUNT_TIER | NOT_APPLICABLE | ONE COUNT BASIS: registry | Recorded per trial. | The other tier, where the trial has one. | NOT COMPUTED -- the store holds only one basis, so the alternative cannot be evaluated without going back to the sources. |
INDIRECTNESS | UNDECLARED | NO STORED JUDGEMENT AND NO DECLARED question_pico. | NOBODY. The domain cannot be derived without both PICOs and it has not been judged by hand either. | Declare question_pico, or judge the domain explicitly. | ⛔ Until one of the two happens the domain is neither rated nor refused -- it is simply missing, which reads to a reader as no concern. |
ESTIMAND | UNDECLARED | ⚠️ CONTRIBUTING TRIALS REPORT 2 DIFFERENT PRIMARY TIME FRAMES: 96 hours +/- 24 hours after first dose of study drug | ECR was assessed 96 +/- 24 hours after the first dose of study drug.. The pool combines them on one scale. | A HUMAN, and often as a SIDE EFFECT of the count tier rather than as its own decision -- a registry reports participants and so forces a risk ratio; a publication reports person-years and so forces a rate ratio. Choosing the document chose the measure. | Pool on person-time instead, which is estimand-consistent under unequal follow-up. | NOT COMPUTED -- person-time denominators are not in this store. Where a topic holds them the alternative is one line. |
IMPRECISION_THRESHOLD | UNDECLARED | NO THRESHOLD DECLARED. | ⚠️ NOBODY. The engine falls back to the Handbook rough guide of 0.75 to 1.25 -- which means the most consequential line on the page is drawn by a default rather than by a clinical judgement. | Declare one, justified from ABSOLUTE effect rather than from the ratio. | The imprecision domain would rest on a stated, arguable line instead of an unexamined default. |
HARMS_POOLING | UNDECLARED | NO HARMS OUTCOME IS HELD. | NOBODY -- the review carries benefit only. | Extract harms. | ⛔ OUTCOME SCOPE IS BENEFIT-ONLY. A reader cannot weigh anything against anything. |
INDEX_ENTRY | UNDECLARED | The object does not carry the sentence the portfolio index shows. | ⚠️ A HUMAN, IN THE INDEX GENERATOR, WITH NO LINK BACK. project_index_cards.py projects the numbers and states that the prose is authored, so the tile's name for this review lives only in the index and nothing reconciles the two. | Store the tile sentence on the object and project it. | ⛔ Until then a re-pointed object updates its NUMBER on the index and keeps its old NAME. Measured 2026-08-30: 1 of 44 mapped index entries names trials the object has never heard of, and the number beside it was correct. See scripts/audit_index_identity_drift.py. |
A topic costs 0 declared judgements on this outcome, not four hundred. That is a stronger claim than "automated", because a reader can check a declared judgement and cannot check an inferred one.
⚠️ It does not make the judgements right, and it does not prove the SLOT LIST is complete -- the list is bounded by what its author enumerated. The honest form is "8 slots checked", never "8 judgements exist".
In this section: Paper · Title · Abstract · Introduction · Methods — search · Methods — synthesis · Results · Risk of bias in the included results · Certainty of the evidence · Comparison with published syntheses · Limitations · Software availability · Note on registration · References · Figures · Trial characteristics · Not reported in this record
Each statement below cites the record it came from; those sources are listed at the end of every section. Where the record holds nothing, the section says so by name rather than being left out, so a procedure that was not carried out can be told from one that simply was never mentioned.
Lefamulin versus moxifloxacin in community-acquired bacterial pneumonia1
titleQuestion. In Lefamulin versus moxifloxacin in community-acquired bacterial pneumonia, what is the effect on versus moxifloxacin (with or without linezolid in leap 1) on early clinical response?1
Methods. estimates were pooled under a random-effects model with the REML estimator; risk of bias was assessed with RoB 2 (Cochrane risk-of-bias tool for randomized trials); and certainty was rated with GRADE, following the Cochrane Handbook chapter 14. Randomised evidence starts HIGH and is rated down with reasons.2
Results. Early clinical response: risk ratio 0.988 (0.953 to 1.02) across 2 trials; 1 of these pooled outcome(s) carries a stated qualification -- a referral or a recorded finding -- given in full in Results and not reproduced here; and no statistical heterogeneity was detected (I-squared 0%), though heterogeneity cannot be reliably assessed with two trials.3
questionresults.by_outcome, risk_of_bias.by_outcome, grade.by_outcomeresults.by_outcome1Background. This review asks: In Lefamulin versus moxifloxacin in community-acquired bacterial pneumonia, what is the effect on versus moxifloxacin (with or without linezolid in leap 1) on early clinical response? It pools 2 randomised trials, against moxifloxacin (with or without linezolid in leap 1). The outcome pooled is early clinical response. Every count and denominator behind those estimates is read as follows. Registry throughout. Every count and denominator in this pool is read from ClinicalTrials.gov posted results. No publication figure is used and no value is imported.
manuscript.introductionPrimary trials. No bibliographic search for primary trials was run. The 2 included trials were identified by reading named registrations on 2026-08-18. Both registrations read from ClinicalTrials.gov on 2026-08-18: conditions, arm groups with types, registered primary outcome measures, and the posted results counts and denominators used in the pool. Published syntheses. PubMed E-utilities esearch + esummary, executed 2026-08-21. Query as executed: (lefamulin[tiab]) and (meta-analysis[pt] OR "systematic review"[pt] OR meta-analysis[tiab] OR "pooled"[tiab] or leap[tiab]). It matched 19 record(s), of which 19 were retrieved and 19 read; 1 appraised.1
bookkeeping_2026_08_21.the_search_its_date_and_its_databasesFor early clinical response, a random-effects model was fitted with the REML estimator.1
Risk of bias was assessed with RoB 2 (Cochrane risk-of-bias tool for randomized trials) (), following . 2 result-level assessments were made.2
A ceiling applies to every risk-of-bias judgement in this review; it is stated with the assessment itself rather than summarised here.3
Certainty of evidence was rated with GRADE, following the Cochrane Handbook chapter 14. Randomised evidence starts HIGH and is rated down with reasons., following . 1 pooled outcome(s) were rated. No domain is rated UP. Rating up for a large effect, a dose-response gradient or opposing plausible confounding applies to observational evidence; these are randomised trials, which start HIGH and can only be rated down.4
results.by_outcome.primary.model, results.by_outcome.primary.estimator_usedrisk_of_bias.tool, risk_of_bias.by_outcomerisk_of_bias.ceilinggrade.approach, grade.by_outcomeThe pooled risk ratio for early clinical response was 0.988 (0.953 to 1.02) across 2 trials, against moxifloxacin (with or without linezolid in leap 1).1
Noted on this pool. Checked and clean. Read from the registrations on 2026-08-21: NCT02559310 registers 'Early Clinical Response (ECR)' (population: ECR); NCT02813694 registers 'Early Clinical Response (ECR)' (population: ECR). Both trials register the same primary in the same population, so this pool does not cross an analysis-population boundary. Recorded because a check that only speaks when it finds something cannot be told from a check that was never run. The experimental arms are not the same intervention. Read from the pooled analysis (PMID 33964925, BMC Pulm Med 2021): Leap 1 randomised patients to intravenous lefamulin 150 mg every 12 hours for 5-7 days with an optional intravenous-to-oral switch; leap 2 randomised to oral lefamulin 600 mg every 12 hours for 5 days. This object pools them as one intervention. Leap 1's comparator is moxifloxacin with or without linezolid and leap 2's is moxifloxacin alone -- corroborated from the registered arm groups. This object's own question already states the comparator difference; The route and duration difference was not previously recorded. Whether these are non-inferiority designs is not established: the registration fields fetched do not use the word, and a pooled ratio from non-inferiority trials answers a different question from a superiority pool. Unresolved, not assumed. Not that the pool is invalid -- an intravenous-to-oral switch and an oral course of the same drug are a defensible thing to combine, and the published analysis combines them. What is claimed is that a reader meeting one ratio should know the two arms differed in route, duration and comparator, and no field said so.2
The trials' results were closely consistent with one another: I-squared, the share of the variation between them that is more than chance alone would produce, was 0%; the estimated variance of the true effects between trials (tau-squared) was 0, the heterogeneity test statistic Q was 0.731, on degrees of freedom 1.3
What this does not establish: Not that either trial is free of bias -- no risk-of-bias assessment is recorded, and a pooled estimate without one is an arithmetic result, not a graded finding. Not non-inferiority or superiority: both trials were designed as non-inferiority studies against an active comparator, and a risk ratio near 1 with an interval spanning 1 is the expected result of a successful non-inferiority trial rather than evidence of no difference. Not that the pooled interval is reliable at k=2 -- see the Hartung-Knapp interval, which is the honest width. Not agreement with any published synthesis; none has been checked.4
The full model output for every pooled outcome -- the call, the estimator, the heterogeneity statistics and the back-transformed interval -- is stored verbatim on this review object at `results.by_outcome.<outcome>.r_output.verbatim`. It is not reproduced as an Extended data section in this article; an earlier version of this sentence said it was, and no such section exists.5
outcomes[id=primary].name, results.by_outcome.primary.pooled, outcomes[id=primary].comparatorresults.by_outcome.primary.POOL_FINDINGS_2026_08_21results.by_outcome.primary.heterogeneity.i2, results.by_outcome.primary.heterogeneity.tau2, results.by_outcome.primary.heterogeneity.q, results.by_outcome.primary.heterogeneity.dfresults.by_outcome.primary.what_this_does_not_establishresults.by_outcomeRisk of bias was assessed with RoB 2 at the level of each reported result, by two assessors reading independently. Their judgements differ on 2 of the 2 results and no adjudication has been performed, so this review holds no final risk-of-bias judgement for these results. Assessor 1 recorded: 2 at some concerns. Assessor 2 recorded: 2 at no information. Both are shown in the risk-of-bias table; neither is the review's finding. The per-domain judgements behind them are recorded with the extracted data.1
risk_of_bias.SECOND_ASSESSOR_2026_08_21.DISAGREEMENT_RATE, risk_of_bias.SECOND_ASSESSOR_2026_08_21.PER_DOMAIN, risk_of_bias.SECOND_ASSESSOR_2026_08_21.RECOUNTED_AFTER_THE_D1_RESOLUTION_2026_08_21, risk_of_bias.SECOND_ASSESSOR_2026_08_21.assessor_1, risk_of_bias.SECOND_ASSESSOR_2026_08_21.each_disagreement, risk_of_bias.SECOND_ASSESSOR_2026_08_21.how_it_was_asked, risk_of_bias.ceiling.statement, risk_of_bias.toolCertainty was rated with GRADE, following the Cochrane Handbook chapter 14. Randomised evidence starts HIGH and is rated down with reasons..1
No domain is rated UP. Rating up for a large effect, a dose-response gradient or opposing plausible confounding applies to observational evidence; these are randomised trials, which start HIGH and can only be rated down.2
This certainty rating is pending, not rated. It rests on a risk-of-bias judgement that this review has not finalised: two assessors read every contributing result independently, they disagree, and no adjudication has been performed, so this review holds no final risk-of-bias judgement for these results. Cochrane rates certainty per outcome by aggregating the risk-of-bias judgements of the results contributing to it, so a certainty rating cannot be more final than the risk-of-bias assessment it reads. The rating this object currently records, and the steps behind it, are shown below as the work so far rather than as this review's answer. No level is published for this outcome -- not the recorded one, not a more cautious one, and not a midpoint -- because choosing one would be the judgement that has not been made.3
LOW certainty. The two trials agree closely and the endpoint is the registered primary assessed under quadruple masking, so the downgrades are for unread deviation and missing-data domains and for k = 2, not for inconsistency or indirectness.4
| Outcome | Certainty | k | Started at | Rating steps |
|---|---|---|---|---|
| early clinical response | Pending | 2 | HIGH | the steps taken so far, not a final rating: risk of bias -- Both results are some concerns. the randomisation process, measurement of the outcome and selection of the reported result are LOW on read registrations -- randomised, quadruple masking including the outcomes assessor, and a single registered primary that is the one pooled -- but deviations from the intended intervention and missing outcome data are no information because the registrations do not carry deviation or missing-data fields. An unjudgeable domain caps the overall at some concerns. (move: HIGH to MODERATE, down 1 level(s)); inconsistency -- The stored refit gives tau^2 exactly zero, Q 0.7316 on 1 df, p = 0.3924. The two intervals -- 0.9683 (0.9123 to 1.0276) and 1.0006 (0.9556 to 1.0476) -- overlap almost entirely and agree in conclusion. Downgrading here would manufacture a caution the numbers do not support. (move: no downgrade); indirectness -- Early Clinical Response is the single registered primary on both trials and is exactly what is pooled. Recorded and not used to downgrade: leap 1's comparator is moxifloxacin with OR without linezolid and leap 2's is moxifloxacin alone. The object discloses this in its own question, and the endpoint definition is unaffected by it, so it is stated rather than converted into a rating. (move: no downgrade); imprecision -- k = 2. The Hartung-Knapp interval is RR 0.9884 (0.7807 to 1.2513 -- and not 0.8079 to 1.2093, which is metafor's RAW unfloored knha interval) on t = 12.7062 with 1 df -- wide enough to include both a meaningful benefit and a meaningful harm. Two trials cannot inform a between-study variance, and no optimal information size is recorded on this object. (move: MODERATE to LOW, down 1 level(s)); publication bias -- k = 2, as above. Handbook 13.3.5.4. (move: Not assessable -- no rating applied) |
grade.approachgrade.not_rated_uprisk_of_bias.by_outcomegrade.by_outcome.primary.summarygrade.by_outcome.primaryPublished syntheses were identified as follows. PubMed E-utilities, executed 2026-08-21. Query, counts and per-record disposition in ssot/lefamulin-cabp-auto-full-review/appraisal/the screen of published syntheses.json.1
published_comparison._how_identifiedWhat this review does not give a clinician: the number of events in each arm, any absolute effect or number needed to treat and any measure of harm. A relative effect cannot be turned into the benefit or the risk facing one patient without them, so this review can support a judgement about what these trials found and not a judgement about what to do.1
results.by_outcome1Analyses were computed under R version 4.6.0 (2026-04-24 ucrt) metafor 5.0.1 run at 2026-08-21.
results.by_outcomeNo PROSPERO registration or protocol record is held on this object. That is not the same as knowing this review was not registered, and neither claim is made. It is recorded here as an absence so that a reader does not have to infer it from silence.1
bookkeeping_2026_08_21.whether_this_review_was_prospectively_registered| Trial | Registration | Registry | Read |
|---|---|---|---|
| LEAP 1 | NCT02559310 | ClinicalTrials.gov | 2026-08-18 |
| LEAP 2 | NCT02813694 | ClinicalTrials.gov | 2026-08-18 |
| Citation | Identifier |
|---|---|
| Lefamulin efficacy and safety in a pooled phase 3 clinical trial population with community-acquired bacterial pneumonia and common clinical comorbidities. BMC Pulmonary Medicine. 2021. | PMID: 33964925 |
| Cited for | Reference |
|---|---|
| risk of bias in the included results | Sterne JAC, Savovic J, Page MJ, et al. RoB 2: a revised tool for assessing risk of bias in randomised trials. BMJ. 2019;366:l4898. doi:10.1136/bmj.l4898 |
| certainty of the evidence | Schunemann HJ, Higgins JPT, Vist GE, et al. Chapter 14: Completing 'Summary of findings' tables and grading the certainty of the evidence. In: Cochrane Handbook for Systematic Reviews of Interventions version 6.5. Cochrane; 2024. |
| the model fitted, as R version 4.6.0 (2026-04-24 ucrt) metafor 5.0.1 run at 2026-08-21 | Viechtbauer W. Conducting meta-analyses in R with the metafor package. J Stat Softw. 2010;36(3):1-48. doi:10.18637/jss.v036.i03 |
| the reporting guideline this manuscript is written against | Page MJ, McKenzie JE, Bossuyt PM, et al. The PRISMA 2020 statement: an updated guideline for reporting systematic reviews. BMJ. 2021;372:n71. doi:10.1136/bmj.n71 |
manuscript.referencesmanuscript.referencesmanuscript.referencesresults.by_outcome.primary.per_trial, results.by_outcome.primary.pooledresults.by_outcome.primary.per_trial, results.by_outcome.primary.pooled| Registration | Trial | Participants | Randomised | Primary outcome measured over | Design |
|---|---|---|---|---|---|
| NCT02559310 | registered condition: Community Acquired Pneumonia | not extracted | ECR was assessed 96 +/- 24 hours after the first dose of study drug. | experimental (241 of 276) vs comparator (248 of 275). No arm-level record is stored on this trial. The counts above are read through to this object's own `as posted` block -- the registry's posted results, uncorrected, read 2026-08-18. They are not a separate copy: this cell is derived, so a correction to the source cannot leave a stale duplicate behind. | |
| NCT02813694 | registered condition: Community Acquired Pneumonia | not extracted | 96 hours +/- 24 hours after first dose of study drug | experimental (336 of 370) vs comparator (334 of 368). No arm-level record is stored on this trial. The counts above are read through to this object's own `as posted` block -- the registry's posted results, uncorrected, read 2026-08-18. They are not a separate copy: this cell is derived, so a correction to the source cannot leave a stale duplicate behind. |
inputs.trialsThe items below were not written because the record does not hold what they would be composed from. They are named here so that an absence is not mistaken for an omission.
| Article area | Item not reported | Reason |
|---|---|---|
| Abstract | The Background sentence of the abstract | Background is argument -- why this question matters -- and no arrangement of the quantities this object holds yields it. It is emitted only from an authored field and there is no composition path for it here |
| Abstract | The Conclusions sentence of the abstract | A conclusion is argument -- what a reader should now believe -- and it is emitted only from an authored field. Composing one from the estimate would be this renderer telling the reader what to conclude, which no field supports |
| Methods — search | A database search for primary trials, which was not carried out for this review; the included trials were identified from named registrations | No further reason is recorded. |
| Methods — eligibility criteria | The eligibility criteria | No further reason is recorded. |
| Methods — how many studies at each stage | The k cascade | No further reason is recorded. |
| Methods — outcomes sought at every registered rank | The statement that outcomes were sought below the primary | No further reason is recorded. |
| Methods — synthesis | The claim that records were screened in duplicate by two independent reviewers | No further reason is recorded. |
| Methods — synthesis | The claim that the review methods were prespecified before data collection | No further reason is recorded. |
| Author contributions | The author-contributions statement | Who did what is a fact about people, and this object records none |
| Competing interests | The competing-interests declaration | F1000Research requires this section on every article, and requires explicit text where there is nothing to declare. It is a statement about the author and not about the evidence: no field of this object implies it and none is invented here |
| Grant information | The grant information | The venue requires each funder's name, the grant number where applicable, and the person the grant was assigned to. None of that is derivable from a synthesis |
| Funding and conflicts of interest | The funding and conflict-of-interest statement -- a content gap | A submission requires it and this object does not carry it; it is not inferable from anything held here |
| Note on registration | The registration note | No further reason is recorded. |
In this section: primary · Absolute effect, at baseline risks you choose
Format: Cochrane Handbook v6.5, chapter 14 (14.1.2 contents, 14.1.3 absolute effects). The FIELDS are fixed by the Handbook so a reader can check the shape of this table as well as its numbers.
| Relative effect | No. participants analysed | No. studies |
|---|---|---|
| RR 0.9884 (0.953 to 1.025) | not held | 2 |
Participants is the number ANALYSED for this outcome, summed from the same per-arm counts the effect above is computed from -- not the number the trials enrolled, which is a larger and different quantity. Where some contributing trial holds no per-arm counts the cell says so rather than showing a sum over the trials that do, because a partial sum is not a total.
No control arm is held for this outcome, so the baselines below are ASSUMED and belong to no population in this evidence. Handbook 14.1.3 asks for absolute effects at STATED baseline risks. This is arithmetic -- the relative effect multiplied by a baseline -- and it asserts nothing about whether this evidence transfers to that population. The table is arithmetic; the refusal below is about transfer. Different claims, kept apart.
| Assumed baseline risk | Risk with intervention | 95% CI | Difference |
|---|---|---|---|
| 1 per 1000 | 1.0 per 1000 | 1.0 to 1.0 | 0.0 |
| 5 per 1000 | 4.9 per 1000 | 4.8 to 5.1 | -0.1 |
| 10 per 1000 | 9.9 per 1000 | 9.5 to 10.2 | -0.1 |
| 50 per 1000 | 49.4 per 1000 | 47.6 to 51.2 | -0.6 |
| 100 per 1000 | 98.8 per 1000 | 95.3 to 102.5 | -1.2 |
| 200 per 1000 | 197.7 per 1000 | 190.6 to 205.0 | -2.3 |
Format: Cochrane Handbook v6.5, chapter 15 (15.6 implications for practice). The twelve considerations below are the GRADE Evidence-to-Decision framework, reproduced in full whether or not this review can answer them.
| Consideration | Answer | From this review |
|---|---|---|
| Is the problem a priority? | NOT ADDRESSED | Whether a problem is a priority ranks it against competing claims on the same budget. The trial populations recorded here say who was studied; they are not a property that can rank the problem, and this review does not rank it. |
| How substantial are the desirable effects? | INFORMED | The pooled relative effect and its interval, with an absolute-effect grid, are in the Summary of Findings tab. Informed by results.by_outcome.primary.pooled. |
| How substantial are the undesirable effects? | NOT ADDRESSED | No harms block is held on this object. THAT IS NOT A FINDING OF NO HARM -- it is an absence of extraction, and a panel must treat it as unmeasured rather than as reassurance. |
| What is the overall certainty of the evidence? | NOT ADDRESSED | No GRADE certainty is stored for any outcome. |
| Is there important uncertainty about how much people value the outcomes? | NOT ADDRESSED | No study of how people weigh these outcomes was sought or synthesised. This is a review of trial effects. |
| Does the balance favour the intervention or the comparison? | NOT ADDRESSED | A balance requires values. With values unaddressed, a balance statement would be the review author's preference wearing a panel's authority. |
| How large are the resource requirements? | NOT ADDRESSED | No cost input of any kind is held. |
| What is the certainty of the resource evidence? | NOT ADDRESSED | No resource evidence is held, so there is no certainty to rate in it. |
| Does cost-effectiveness favour the intervention? | NOT ADDRESSED | No economic evaluation was sought. |
| What would be the impact on health equity? | NOT ADDRESSED | No registry extraction is held on this object. |
| Is the intervention acceptable to key stakeholders? | NOT ADDRESSED | Acceptability studies are outside this review's scope. |
| Is the intervention feasible to implement? | NOT ADDRESSED | Implementation and delivery are outside this review's scope. |
UNSTAMPED — unknown-version. This page carries no build_stamp, so the standard it was built to cannot be established. That is a statement about the record, not a claim that the page is below standard.
Every number on this page is projected from a single canonical object, and each measured cell names the source analysis it was read from. That is what is machine-checked. It does not establish that the underlying sources are right, only that this page faithfully reports them.
| Outcome | Pooled as | Which is | Trials |
|---|---|---|---|
| primary | RR | binary counts | 2 |
The registry records an analysis of an unrecognised type for 2 of the contributing trials.
| Outcome | k | Pooled | Random-effects Wald | Modified Hartung–Knapp | Wider by |
|---|---|---|---|---|---|
| primary | 2 | 0.988 | 0.953 to 1.025 | 0.781 to 1.251 | 6.48× |
At two trials this page reports neither interval as the answer, and says why. With k = 2 the modified interval uses t on ONE degree of freedom — a multiplier of 12.71 against 1.96 — because two trials carry almost no information about how much results vary between trials. The resulting interval is wide by construction and would be nearly as wide whatever the trials had found, so it should not be read as evidence that the treatment does not work: that width is the degrees of freedom, not the data. The Wald interval has the opposite fault — it treats a between-trial variance estimated from two numbers as if it were known, and is too narrow for the same reason. Both are printed above so a reader can see the size of the gap rather than inherit whichever one an author preferred.
The modification is the floor at q* = 1. Unmodified, Hartung–Knapp can return a narrower interval than Wald whenever Q < k−1 — which would let the estimator that carries more uncertainty appear more confident. Flooring it means extra care can never buy a tighter answer.
For primary: 2 trials, τ² = 0.0000, q* = 1.00 (at the floor — without it the more careful estimator would have returned a narrower interval than the Wald one). The t multiplier on 1 degrees of freedom is 12.71 against 1.96 for the normal, so the modified interval is 6.48× wider on the analysis scale.
No comparator is designated for this question, so this page does not state how current it is relative to one. Which published review answers the same question is a judgement, and this component refuses to make it by taking whichever identifier appears first — doing exactly that produced a search date from an adherence review of observational studies on an earlier run. The object mentions PMIDs 33964925; none is marked as the comparator.
primary — no baseline risk, so no absolute effect. no contributing trial carries a labelled control arm with counts (LEAP 1, LEAP 2). Borrowing a baseline from an external population would put a different review's number inside this one's interval.
This object records no outcome besides the one pooled above. That is a statement about what has been extracted into this review, not about what the trials measured: a trial that reported harms this review has not extracted will look, from this page, exactly like a trial that reported none.
This object records event counts from one source per trial and no alternative was sought, so this page cannot tell you whether the registry and the publication agree. ⚠️ That is not the same as saying they do. A registry posts counts as submitted and a publication reports them after endpoint adjudication; where those differ, the adjudicated figure is the trial's own final answer, and a review that never compared them cannot say which it is using.
This object does not record what quantity the contributing trials analysed, so this page cannot say whether the quantity it pools is theirs. ⚠️ That is an unchecked assumption, not a clean bill: a risk ratio over binary counts and a hazard ratio over person-time are different quantities, and a review that pools the first while the trials analysed the second will differ from them whenever follow-up differs between arms.
Each statement above is emitted only when a specific condition holds in this review's own object; none is written by hand. This section makes no recommendation: what to offer, to whom, at what cost and against what alternative is a judgement this page does not hold the inputs for.
What this page cannot tell a clinician, and why. magnitude — no absolute effect for primary (refused: no baseline risk (no labelled control arm with counts)). where it holds — no stratum reads as demonstrated. where it has not been shown — no stratum reads as not demonstrated. harms — no harm outcome is held at the trial-report tier. what it is not — no outcome is recorded as absent or not measurable. what it is conditional on — the object records no background care delivered alongside the intervention, so this page cannot say what its estimate is on top of. efficacy versus use — the object records no adherence finding.
| What | Value | Read from | Sentence it was read from | Fingerprint |
|---|---|---|---|---|
| LEAP 1 | — | https://clinicaltrials.gov/study/NCT02559310 | — | — |
| LEAP 1 | 0.9683 | https://clinicaltrials.gov/study/NCT02559310 | — | — |
| LEAP 2 | — | https://clinicaltrials.gov/study/NCT02813694 | — | — |
| LEAP 2 | 1.0006 | https://clinicaltrials.gov/study/NCT02813694 | — | — |
| trial_identity_check | — | ClinicalTrials.gov API v2 armsInterventionsModule | — | — |
The denominator. 5 records in this object carry a source. 0 of 5 carry the sentence they were read from, and 0 of 5 carry a document fingerprint. ⚠️ A fingerprint says the bytes we read are the bytes we say we read; it does not say the document contained what we claim. What makes a row checkable is the sentence, so rows carrying one are listed first and the rest are visible as the gap they are.
Retrieval routes are recorded per document and a document is marked unreachable only after every route has been tried and named — so a missing document on this page is a record of what was attempted, not a blank.
GRADE, following the Cochrane Handbook chapter 14. Randomised evidence starts HIGH and is rated down with reasons.
No rating is shown. the object does not record a starting certainty, so the certainty cannot be derived from its own steps and a stored value would be an assertion rather than a result.
| Domain | Reading | Levels | Reason |
|---|---|---|---|
| risk of bias | downgraded | -1 | Both results are SOME_CONCERNS. D1, D4 and D5 are LOW on read registrations -- randomised, QUADRUPLE masking INCLUDING the outcomes assessor, and a single registered primary that is the one pooled -- but D2 and D3 are NO_INFORMATION because the registrations do not carry deviation or missing-data fields. An unjudgeable domain caps the overall at SOME_CONCERNS. |
| inconsistency | no downgrade | — | The stored refit gives tau^2 EXACTLY ZERO, Q 0.7316 on 1 df, p = 0.3924. The two intervals -- 0.9683 (0.9123 to 1.0276) and 1.0006 (0.9556 to 1.0476) -- overlap almost entirely and agree in conclusion. Downgrading here would manufacture a caution the numbers do not support. |
| indirectness | no downgrade | — | Early Clinical Response is the SINGLE registered primary on both trials and is exactly what is pooled. RECORDED AND NOT USED TO DOWNGRADE: LEAP 1's comparator is moxifloxacin WITH OR WITHOUT LINEZOLID and LEAP 2's is moxifloxacin alone. The object discloses this in its own question, and the endpoint definition is unaffected by it, so it is stated rather than converted into a rating. |
| imprecision | downgraded | -1 | k = 2. The Hartung-Knapp interval is RR 0.9884 (0.7807 to 1.2513 -- and NOT 0.8079 to 1.2093, which is metafor's RAW unfloored knha interval) on t = 12.7062 with 1 df -- wide enough to include both a meaningful benefit and a meaningful harm. Two trials cannot inform a between-study variance, and no optimal information size is recorded on this object. |
| publication bias | NOT ASSESSABLE | — | k = 2, as above. Handbook 13.3.5.4. |
Not assessable is not the same as no concern. publication bias could not be assessed here, so it neither raised nor lowered the rating. A domain that was never checkable is shown as itself rather than folded into “no downgrade”, which would tell you it had been checked and found clean.
LOW certainty. The two trials agree closely and the endpoint is the registered primary assessed under quadruple masking, so the downgrades are for unread deviation and missing-data domains and for k = 2, not for inconsistency or indirectness.
These are the specific errors that would otherwise be in the numbers above. Each class was derived from a real defect found by auditing this corpus, and each carries the defect that generated it.
Checked against 11 instrumented defect classes. 0 flagged on this build.
| Class | What it catches | The defect that generated it |
|---|---|---|
| unanchored-external-authority | an outside body's position asserted with nothing retrievable behind it | 'WHO has recommended the ring' went live from a conversation, and dropped the conditionality WHO actually attached -- WHO, iris handle 10665/340190, 17 March 2021: the ring 'may be offered ... (Conditional recommendation; moderate-certainty evidence)' |
| single-trial-shown-as-pooled | one trial's result presented as a pool | the front page carried a single trial's HR 0.85 (0.79-0.92) as a two-trial pool |
| unfilled-template-token | a placeholder shipped unsubstituted | 11 pages cited protocols/name_protocol_v1.0.md -- 'name' was the placeholder |
| bare-none-rendered | a Python None reaching rendered output | 1110 dashboards rendered as 626-byte stubs from `None` in a JS literal |
| markup-imbalance | unbalanced tags after a hand edit | div-balance drift after HTML edits, repeatedly |
| estimand-unnamed | a pooled quantity presented without naming what it estimates | binary counts pooled where both trials analysed time to event |
| hksj-unqualified | a small-k interval reported without naming the variance floor | raw HKSJ narrows below Wald when Q < k-1; the q* floor was missing |
| ratio-on-natural-scale | a ratio measure said to be on the natural scale | sglt2-hf rendered 'on the natural scale' for a hazard ratio |
| denial-of-something-held | the page denies what the corpus holds | 92 pages stated no protocol exists while a protocol sat in the repository |
| statistic-rendered-twice | one statistic with two values on one page | the same number rendered from two code paths |
| untraceable-number | a number with no source | stored estimates that do not follow from their own counts: 172 of 178 uncheckable |
Flagged on this build:
Named because a taxonomy that lists only what it catches is marketing.