Ramipril-Associated Hepatotoxicity
Bibliographic record
Abstract
CONTEXT: Angiotensin-converting enzyme inhibitors are prescribed for many cardiovascular and renal diseases. Adverse hepatic events, especially cholestasis, have rarely been reported with captopril, enalapril, lisinopril, and fosinopril. To date, hepatic injury associated with ramipril has not been reported. OBJECTIVE: To describe 3 patients who developed hepatitis, with or without jaundice, after receiving ramipril. DESIGN: Medical records and liver biopsies of the 3 patients were reviewed. Clinical, laboratory, and histologic findings were compared with findings in other cases of angiotensin-converting enzyme inhibitor-induced liver injury reported in the literature. RESULTS: The 3 patients were middle-aged men. In 2 patients, jaundice appeared 4 and 8 weeks after starting ramipril. Bilirubin levels peaked at 15.5 and 5 mg/dL, and alkaline phosphatase values peaked at 957 and 507 U/L. Aminotransferase levels were mildly elevated. Endoscopic retrograde cholangiopancreatography and ultrasonography showed no bile duct obstruction. Liver biopsies from the jaundiced patients were similar, with cholestasis, duct necrosis, and extravasation of bile, ductular proliferation, and portal inflammation. Cholestasis improved in 1 patient 6 weeks after stopping ramipril and was prolonged for 14 months in the other, in whom biliary cirrhosis was present on biopsy. The third patient developed hepatitis without jaundice 3 weeks after starting ramipril; symptoms resolved after stopping the drug. Ramipril-associated liver injury is similar to that seen with other angiotensin-converting enzyme inhibitors, but liver biopsy findings of duct necrosis and extravasation of bile have not been reported previously. CONCLUSION: Prolonged cholestatic hepatitis and biliary cirrhosis may result from the use of ramipril. Monitoring of liver enzymes is advisable for patients starting on ramipril.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".