Immediate Hypersensitivity to Moxifloxacin with Tolerance to Ciprofloxacin: Report of Three Cases and Review of the Literature
Bibliographic record
Abstract
OBJECTIVE: To report 3 cases of immediate hypersensitivity reactions to moxifloxacin in patients who tolerated ciprofloxacin. CASE SUMMARIES: A 71-year-old man, a 44-year-old woman, and a 70-year-old woman with a history of a moxifloxacin reaction developed an immediate hypersensitivity reaction upon oral challenge with moxifloxacin in our Drug Safety Clinic. The reaction was mainly characterized by pruritus and urticaria, although dyspnea and hypotension were noted in the first and second patient, respectively. Two of the patients had negative oral challenge tests with ciprofloxacin and all 3 patients tolerated full treatment courses of oral ciprofloxacin. In all 3 cases, use of the Naranjo probability scale indicated a highly probable adverse drug reaction. DISCUSSION: Moxifloxacin, similar to other fluoroquinolones, can cause immediate hypersensitivity reactions. Previous publications have reported both cross-reactivity and a lack of cross-reactivity among various fluoroquinolones. The 3 patients discussed demonstrated a lack of cross-reactivity between moxifloxacin and ciprofloxacin since they tolerated oral challenge tests and full treatment courses of ciprofloxacin. Moxifloxacin has unique side chains at positions 7 and 8 on its bicyclic ring structure. Antigenic specificity to particular side chains at positions 7 and 8 on the bicyclic ring structure of moxifloxacin may explain this lack of cross-reactivity. Higher reporting rates of anaphylaxis to moxifloxacin compared to other fluoroquinolones may also be related to side chain specificity, although definitive evidence for this is lacking. CONCLUSIONS: Based on our experience, patients who develop immediate hypersensitivity reactions to moxifloxacin may receive ciprofloxacin therapy in an appropriately monitored setting if they have previously tolerated full treatment courses of ciprofloxacin. Research into whether there is a specific side chain reaction unique to moxifloxacin is warranted.
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.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.003 | 0.001 |
| Research integrity | 0.005 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 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".