clinvar-database
Veto GatesRequired pass for any deployment consideration
| Dimension | Result | Detail |
|---|---|---|
| Scientific Integrity | PASS | The legacy audit did not indicate that retrieval outputs were presented as unsupported findings. |
| Practice Boundaries | PASS | The legacy review kept this workflow on the evidence-access side of the boundary, not the advice-giving side. |
| Methodological Ground | PASS | No methodological-grounding issue was recorded for clinvar-database in the archived evaluation. |
| Code Usability | PASS | Code usability passed because the search or lookup workflow still exposed a usable entrypoint and output expectation. |
Core Capability85 / 100 — 8 Categories
Medical TaskExecution Average: 96 / 100 — Assertions: 20/20 Passed
You need to find ClinVar variant records by gene,... remained well-aligned with the documented contract in the preserved audit.
The You want to interpret a variant’s clinical significance... scenario completed within the documented Utilities for querying the NCBI ClinVar database to retrieve variant records, clinical... boundary.
The ClinVar search via NCBI E-utilities using flexible query terms... scenario completed within the documented Utilities for querying the NCBI ClinVar database to retrieve variant records, clinical... boundary.
The archived evaluation treated Clinical interpretation retrieval, including clinical significance... as a clean in-scope run.
The End-to-end case for ClinVar search via NCBI E-utilities using... scenario completed within the documented Utilities for querying the NCBI ClinVar database to retrieve variant records, clinical... boundary.
Key Strengths
- Primary routing is Evidence Insight with execution mode B
- Static quality score is 85/100 and dynamic average is 83.6/100
- Assertions and command execution outcomes are recorded per input for human review
- Execution verification summary: Script verification 2/2; adjustment=5. annotate.py: OK; search.py: OK