Genetic database software as medical devices
Bibliographic record
Abstract
This article provides a primer on medical device regulations in the United States, Europe, and Canada. Software tools are being developed and shared globally to enhance the accessibility and usefulness of genomic databases. Interactive software tools, such as email or mobile alert systems providing variant classification updates, are opportunities to democratize access to genomic data beyond laboratories and clinicians. Uncertainty over the reliability of outputs, however, raises concerns about potential harms to patients, especially where software is accessible to lay users. Developers may also need to contend with unfamiliar medical device regulations. The application of regulatory controls to genomic software could improve patient and user safety, but could also stifle innovation. Legal uncertainty for developers is compounded where software applications are made available globally (implicating multiple regulatory frameworks), and directly to lay users. Moreover, there is considerable uncertainty over the application of (evolving) medical device regulations in the context of both software and genetics. In this article, criteria and examples are provided to inform determinations of software as medical devices, as well as risk classification. We conclude with strategies for using genomic communication and interpretation software to maximize the availability and usefulness of genetic information, while mitigating the risk of harm to users.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| 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.003 | 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 teacher head, 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".