The effect of pregnancy on lupus nephritis
Bibliographic record
Abstract
OBJECTIVE: To evaluate the effect of pregnancy on lupus nephritis with respect to renal activity and renal deterioration. METHODS: Seventy-eight pregnancies occurred in 53 women with systemic lupus erythematosus (SLE) and renal disease. Seventy-eight nonpregnant SLE patients with evidence of renal disease were matched to the study population by age at the time of each pregnancy and by the presence of a renal manifestation at the beginning of the study. The nonpregnant controls were seen within 2 years of the assessment dates of the pregnant patients with whom they were matched. Renal activity was defined as the presence of active urine sediment or proteinuria, and changes in these parameters were monitored throughout the study period in both study populations. Renal deterioration was defined as an increase in the serum creatinine level that was >20% above the baseline value or an increase to >120 mmoles/liter. RESULTS: Renal disease activity patterns were available for 74 pairs of pregnancies and controls. Renal disease became active during the study period in 33 pregnancies (44.6%) and 31 controls (41.9%). Serial serum creatinine levels were available for 75 study pairs, among which 62 pregnancies (82.7%) and 57 controls (76.0%) showed no deterioration. Comparison of the treatments received by both the pregnant and the nonpregnant patients showed no significant difference in the amount of steroids taken. A significantly lower amount of immunosuppressive and antimalarial agents were taken during the pregnancies. CONCLUSION: During pregnancy in patients with SLE and renal disease, changes in renal disease activity and deterioration in renal function are similar to those which occur in nonpregnant patients with lupus nephritis.
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
Direct model labels (unvalidated)
Per-model category and study-design labels from the labeling rounds. They are machine output, unvalidated, and the disagreement between models ships as data. No study design here is MEDLINE-validated yet.
| Model arm | Categories | Study design | Confidence |
|---|---|---|---|
| gpt | no category Domain: not available · Genre: Empirical About the Canadian research system: no · About a Canadian topic: no | Observational | high |
| grok | no category Domain: not available · Genre: Empirical About the Canadian research system: no · About a Canadian topic: no | Observational | high |
| opus | no category Domain: not available · Genre: Empirical About the Canadian research system: no · About a Canadian topic: no | Observational | high |
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 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.000 | 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, unvalidatedLabeled directly by 3 models reading the full record.
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".