Rationale and Design of the Registry for Stones of the Kidney and Ureter (ReSKU): A Prospective Observational Registry to Study the Natural History of Urolithiasis Patients
Bibliographic record
Abstract
OBJECTIVES: Registry-based clinical research in nephrolithiasis is critical to advancing quality in urinary stone disease management and ultimately reducing stone recurrence. A need exists to develop Health Insurance Portability and Accountability Act (HIPAA)-compliant registries that comprise integrated electronic health record (EHR) data using prospectively defined variables. An EHR-based standardized patient database-the Registry for Stones of the Kidney and Ureter (ReSKU™)-was developed, and herein we describe our implementation outcomes. MATERIALS AND METHODS: Interviews with academic and community endourologists in the United States, Canada, China, and Japan identified demographic, intraoperative, and perioperative variables to populate our registry. Variables were incorporated into a HIPAA-compliant Research Electronic Data Capture database linked to text prompts and registration data within the Epic EHR platform. Specific data collection instruments supporting New patient, Surgery, Postoperative, and Follow-up clinical encounters were created within Epic to facilitate automated data extraction into ReSKU. RESULTS: The number of variables within each instrument includes the following: New patient-60, Surgery-80, Postoperative-64, and Follow-up-64. With manual data entry, the mean times to complete each of the clinic-based instruments were (minutes) as follows: New patient-12.06 ± 2.30, Postoperative-7.18 ± 1.02, and Follow-up-8.10 ± 0.58. These times were significantly reduced with the use of ReSKU structured clinic note templates to the following: New patient-4.09 ± 1.73, Postoperative-1.41 ± 0.41, and Follow-up-0.79 ± 0.38. With automated data extraction from Epic, manual entry is obviated. CONCLUSIONS: ReSKU is a longitudinal prospective nephrolithiasis registry that integrates EHR data, lowering the barriers to performing high quality clinical research and quality outcome assessments in urinary stone disease.
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.107 | 0.061 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.005 | 0.004 |
| Science and technology studies | 0.003 | 0.003 |
| Scholarly communication | 0.003 | 0.003 |
| Open science | 0.004 | 0.003 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
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".