Anti‐inflammatory effects of nitric oxide‐releasing hydrocortisone NCX 1022, in a murine model of contact dermatitis
Bibliographic record
Abstract
1 The concept that nitric oxide (NO) release can be beneficial in inflammatory conditions has raised more attention in the recent years, particularly with the development of nitric oxide-releasing anti-inflammatory drugs. There is considerable evidence that NO is capable of enhancing the anti-inflammatory benefits of conventional anti-inflammatory drugs. 2 Since hydrocortisone is the most widely used anti-inflammatory drug for the treatment of skin inflammation, we compared the anti-inflammatory effects of hydrocortisone to an NO-releasing derivative of hydrocortisone, NCX 1022, in a murine model of irritant contact dermatitis, induced by epidermal application of benzalkonium chloride. 3 Topical pre- and post-treatment with NCX 1022 (3 nmol) in C57BL6 mice not only reduced ear oedema formation in a dose-dependent manner, but also was significantly more effective than the parent compound during the initial stages of inflammation (from 1 to 5 h). NCX 1022, but not hydrocortisone, significantly inhibited granulocyte recruitment (tissue myeloperoxidase activity). Histological samples of mouse ears treated with NCX 1022 showed significant reduction in both the number of infiltrated cells and disruption of the tissue architecture compared to hydrocortisone-treated tissues. 4 With intravital microscopy, we observed that both pre- and post-treatments with NCX 1022 were more effective than hydrocortisone in terms of inhibiting benzalkonium chloride-induced leukocyte adhesion to the endothelium, without affecting the flux of rolling leukocytes or venule diameter. 5 These results suggest that by releasing NO, NCX 1022 modulates one of the early events of skin inflammation: the recruitment of leukocytes to the site of inflammation. Overall, we have shown that NO-hydrocortisone provided faster and greater protective effects, reducing major inflammatory parameters (leukocyte adhesion and recruitment, oedema formation, tissue disruption) compared to its parental compound.
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.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.002 |
| 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".