Serum Urate During Acute Gout
Bibliographic record
Abstract
OBJECTIVE: To study the frequency of normal serum urate (SU) levels during acute gout in the largest studies of acute gout treatment to date. METHODS: Data collected from 2 randomized controlled clinical trials assessing the efficacy of etoricoxib or indomethacin for 7 days in acute gout were used to assess SU levels during acute gouty attacks. Efficacy was similar with both agents, so both groups were combined for analysis. RESULTS: A total of 339 patients were enrolled in the 2 studies; 94% were male; mean age was 50.5 years. At baseline, 14% of patients had a "true" normal SU (<or=6 mg/dl) and 32% had SU<or=8 mg/dl during acute gout. Baseline mean SU was 7.1 versus 8.5 mg/dl (p<0.001) in those taking allopurinol versus nonusers. Patients taking chronic allopurinol were more likely to have lower SU at baseline compared to those not taking chronic allopurinol (p<0.001) during the acute attack. CONCLUSION: A normal SU level at presentation does not exclude an acute gouty attack. In the largest studies of acute gout to date, attacks still occurred despite SU levels being below 6.8 mg/dl, the saturation level for urate. This may be attributed to persistence of tophi and an increased body uric acid pool. Additional studies are needed to determine the correlation between SU and the body uric acid pool as well as the relationship to timing of changes during acute gout.
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.004 | 0.013 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| 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".