Omalizumab: Practical considerations regarding the risk of anaphylaxis
Bibliographic record
Abstract
Omalizumab has demonstrated efficacy among patients with moderate to severe persistent allergic asthma, whose symptoms are inadequately controlled with other controller agents. This therapy is generally well tolerated, but there are some safety considerations, the most important of which is the rare, but potentially life-threatening, occurrence of omalizumab-associated anaphylaxis.In Canada, data from the manufacturer of omalizumab indicate that the frequency of anaphylaxis attributed to Xolair in post-marketing use is approximately 0.2%. Other researchers, including the American Omalizumab Joint Task Force (OJTF), have suggested a lower overall frequency of 0.09%.This paper provides a summary of the epidemiologic research carried out to date and presents a concise, practical set of recommendations for the prevention, monitoring and management of omalizumab-associated anaphylaxis. Prevention tips include advice on patient education measures, concomitant medications and optimal administration. For the first three injections, the recommendation is to monitor in clinic for two hours after the omalizumab injection; for subsequent injections, the monitoring period should be 30 minutes or an appropriate time agreed upon by the individual patient and healthcare professional.In the event that a patient does experience omalizumab-associated anaphylaxis, the paper provides recommendations for handling the situation in-clinic and recommendations on how to counsel patients to recognize the potential signs and symptoms in the community and react appropriately.
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.031 | 0.085 |
| Meta-epidemiology (narrow) | 0.003 | 0.001 |
| Meta-epidemiology (broad) | 0.003 | 0.002 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.003 | 0.004 |
| Scholarly communication | 0.009 | 0.011 |
| Open science | 0.004 | 0.004 |
| Research integrity | 0.021 | 0.029 |
| Insufficient payload (model declined to judge) | 0.006 | 0.006 |
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".