Characterization of Cumulative Joint Damage Patterns in Patients with Rheumatoid Arthritis: A Clinical, Serological, and Gene Polymorphism Perspective
Bibliographic record
Abstract
OBJECTIVE: To characterize cumulative joint damage (CJD) patterns in rheumatoid arthritis (RA) and determine their associations with demographic/clinical features and HLA-DRB1 gene polymorphism. METHODS: Hand and foot radiographs were obtained from 404 patients with RA. CJD patterns were determined by 3 derivations from Sharp/van der Heijde scores, obtained by the mathematical division of scores for hands/feet (Sharp-h/f score), fingers/wrists (Sharp-f/w score), and erosion/space narrowing (Sharp-e/sn score), respectively. DNA and serum were obtained for determination of HLA-DRB1 polymorphism, rheumatoid factor (RF), and anticitrullinated protein antibodies (ACPA). RESULTS: Patients with wrist-dominant CJD pattern were more likely to have severe RA than those with finger-dominant pattern (68.4% vs 46.0%; p = 0.036) as were those with foot-dominant vs hand-dominant CJD pattern (76.5% vs 56.4%; p = 0.044). HLA-DRB1 shared epitope (SE) alleles were associated with erosion-dominant CJD pattern (p = 0.021). Patients with erosion-dominant CJD pattern had higher levels of RF and ACPA than those with space-narrowing-dominant CJD pattern (median RF 71.35 U/ml vs 22.05 U/ml, respectively; p = 0.003; median ACPA 187.9 U/ml vs 143.2 U/ml, respectively; p < 0.001). The majority of triple-positive patients (SE+, RF+, ACPA+) had erosion-dominant CJD pattern (62.3%) while the majority of triple-negative patients (SE-, FR-, ACPA-) had space narrowing-dominant CJD pattern (75%; p = 0.017). ACPA was associated with HLA-DRB1 SE alleles (p < 0.05). Patients with foot-dominant CJD pattern were taller than those with hand-dominant CJD pattern (p = 0.002); those with erosion-dominant CJD pattern had higher weight and body mass index than those with space narrowing-dominant CJD pattern (p = 0.014, p = 0.001). CONCLUSION: CJD patterns were associated with disease severity, HLA-DRB1 SE status, presence and titer of ACPA and RF, and morphometric features.
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.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| 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".