Single venom-based immunotherapy effectively protects patients with double positive tests to honey bee and Vespula venom
Bibliographic record
Abstract
BACKGROUND: Referring to individuals with reactivity to honey bee and Vespula venom in diagnostic tests, the umbrella terms "double sensitization" or "double positivity" cover patients with true clinical double allergy and those allergic to a single venom with asymptomatic sensitization to the other. There is no international consensus on whether immunotherapy regimens should generally include both venoms in double sensitized patients. OBJECTIVE: We investigated the long-term outcome of single venom-based immunotherapy with regard to potential risk factors for treatment failure and specifically compared the risk of relapse in mono sensitized and double sensitized patients. METHODS: Re-sting data were obtained from 635 patients who had completed at least 3 years of immunotherapy between 1988 and 2008. The adequate venom for immunotherapy was selected using an algorithm based on clinical details and the results of diagnostic tests. RESULTS: Of 635 patients, 351 (55.3%) were double sensitized to both venoms. The overall re-exposure rate to Hymenoptera stings during and after immunotherapy was 62.4%; the relapse rate was 7.1% (6.0% in mono sensitized, 7.8% in double sensitized patients). Recurring anaphylaxis was statistically less severe than the index sting reaction (P = 0.004). Double sensitization was not significantly related to relapsing anaphylaxis (P = 0.56), but there was a tendency towards an increased risk of relapse in a subgroup of patients with equal reactivity to both venoms in diagnostic tests (P = 0.15). CONCLUSIONS: Single venom-based immunotherapy over 3 to 5 years effectively and long-lastingly protects the vast majority of both mono sensitized and double sensitized Hymenoptera venom allergic patients. Double venom immunotherapy is indicated in clinically double allergic patients reporting systemic reactions to stings of both Hymenoptera and in those with equal reactivity to both venoms in diagnostic tests who have not reliably identified the culprit stinging insect.
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.001 | 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.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".