Designing a web application for personalized medicine trials.
Bibliographic record
Abstract
e13107 Background: Clinical genomics uses information from a patient's genome in clinical decision-making, an example of personalized medicine. The OICR/UHN Genomics Cohort Study is assessing the feasibility and developing standard operating procedures for clinical genomics in late stage cancer patients to enable larger trials. Tumor DNA from consenting patients is sequenced across 19 genes to identify actionable mutations and inform use of targeted therapeutic agents. Informatics systems are critical as the study involves 40 staff in 5 cancer centres, 2 laboratories, 3 genomics technologies, and spans screening, consent, obtaining/processing biopsy samples, genomic analysis, clinical laboratory verification, and reporting for decision-making. Methods: We used a process-centered method to develop a web system to manage study activities. Initially it tracked patients, samples, genomic results, decisions and reports across the cohort, monitored progress and sent reminders, working alongside an electronic data capture (EDC) system for the trial's clinical and genomic results. We later added a system to read, store, and analyze the genomics data, and a knowledge base of mutations’ tumor frequency (from the COSMIC database) annotated with clinical significance and drug sensitivity to generate reports for clinicians. Results: The web tracker proved highly adaptive. The design method allowed procedural refinements mid-study, including changes in sample preparation, sample sources, and differences in nomenclature across technologies. As the study procedures stabilized, the system provided deeper support for clinical decision making, enabling the generation of draft reports for verification by an expert panel prior to forwarding to the treating physician. The web tracker complemented the EDC system with its fixed modules for collection of clinical data and genomic results. Conclusions: The system effectively complemented clinical trial software. An agile development process enabled procedures to be refined as feasibility issues were found and resolved, and enabled flexible analysis of mutation data. Our design approach helped stabilize effective procedures for a clinical genomics service, and establish means to assess its performance.
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 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.254 | 0.222 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 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, unvalidatedMachine predicted; both teacher heads agree on what is shown here.
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".