Clinical trial: intravenous pantoprazole vs. ranitidine for the prevention of peptic ulcer rebleeding: a multicentre, multinational, randomized trial
Bibliographic record
Abstract
BACKGROUND: Controlled pantoprazole data in peptic ulcer bleeding are few. AIM: To compare intravenous (IV) pantoprazole with IV ranitidine for bleeding ulcers. METHODS: After endoscopic haemostasis, 1256 patients were randomized to pantoprazole 80 mg+8 mg/h or ranitidine 50 mg+13 mg/h, both for 72 h. Patients underwent second-look endoscopy on day 3 or earlier, if clinically indicated. The primary endpoint was an overall outcome ordinal score: no rebleeding, rebleeding without/with subsequent haemostasis, surgery and mortality. The latter three events were also assessed separately and together. RESULTS: There were no between-group differences in overall outcome scores (pantoprazole vs. ranitidine: S0: 91.2 vs. 89.3%, S1: 1.5 vs. 2.5%, S2: 5.4 vs. 5.7%, S3: 1.7 vs. 2.1%, S4: 0.19 vs. 0.38%, P = 0.083), 72-h clinically detected rebleeding (2.9% [95% CI 1.7, 4.6] vs. 3.2% [95% CI 2.0, 4.9]), surgery (1.9% [95% CI 1.0, 3.4] vs. 2.1% [95% CI 1.1, 3.5]) or day-3 mortality (0.2% [95% CI 0, 0.09] vs. 0.3% [95% CI 0, 1.1]). Pantoprazole significantly decreased cumulative frequencies of events comprising the ordinal score in spurting lesions (13.9% [95% CI 6.6, 24.7] vs. 33.9% [95% CI 22.1, 47.4]; P = 0.01) and gastric ulcers (6.7% [95% CI 4, 10.4] vs. 14.3% [95% CI 10.3, 19.2], P = 0.006). CONCLUSIONS: Outcomes amongst pantoprazole and ranitidine-treated patients were similar; pantoprazole provided benefits in patients with arterial spurting and gastric ulcers.
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.005 | 0.006 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.005 | 0.003 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.013 | 0.002 |
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".