355. DEVELOPMENT OF A CUSTOM RELATIONAL DATABASE FOR INTEGRATING CLINICAL AND RESEARCH DATA FOR THE STUDY FOR ESOPHAGEAL ADENOCARCINOMA
Bibliographic record
Abstract
Abstract Background With the advent of next-generation sequencing, digital pathology, and other high-dimensional data sources used in modern research, improved data management is required to maintain organization and relationship to the corresponding patient and their outcomes. The complexity of the data often limits interpretation by clinicians not highly versed in its analysis. Conversely, data scientists may not be able to interpret the data in the correct clinical context. We describe here a relational database and custom tools which coordinates clinical, organoid, and genomic data in the study of esophageal adenocarcinoma. Methods Database architecture was designed with pillars of clinical data and outcome, organoid culture data, and next-generation sequencing data. Data dictionaries were composed for all tables in the database architecture. Oracle Database was utilized and populated with datasets formatted to adhere to data dictionaries. Application Express was used to develop web applications for users to enter, query, and analyze data. Automatic nightly backups, robust login security, and tiers of access protect confidential data against system failures, human error, and data theft. Custom tools with graphical user interfaces were developed for survival curve generation and organoid drug-screening results, to facilitate clinician use. Results This database now encompasses over 21 data tables comprising clinical, surgical, recurrence, treatment response, tissue sample storage, organoid research, and genomic data. Data scientists can link omic data directly to patient clinical data and clinician researchers can rapidly obtain patient and organoid survival data for covariates of choice using a graphical user interface. Conclusion Proper data management requires a substantial initial investment in designing of database architecture, deployment of software and servers, formatting of data, and the creation of front-end user applications. The investment is well worth the cost, however, as a centralized database allows for rapid querying of data that would otherwise be scattered or require individualized analysis for each project. This also facilitates the interactions between data scientists and clinician researchers.
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.008 | 0.010 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.003 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.011 | 0.007 |
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".