clinical-data-cleaner
Veto GatesRequired pass for any deployment consideration
| Dimension | Result | Detail |
|---|---|---|
| Scientific Integrity | PASS | The archived review kept this workflow anchored to supplied data fields and observable execution behavior, not fabricated results. |
| Practice Boundaries | PASS | Practice boundaries held because the package remained focused on Use when cleaning clinical trial data, preparing data for FDA/EMA submission, standardizing... rather than overclaiming what the records supported. |
| Methodological Ground | PASS | The legacy review kept the package aligned with its named analysis library, data structure, or processing workflow. |
| Code Usability | PASS | The archived review preserved a usable code path with named scripts, expected inputs, and a recognizable output contract. |
Core Capability88 / 100 — 8 Categories
Medical TaskExecution Average: 84.4 / 100 — Assertions: 17/20 Passed
The Use when cleaning clinical trial data, preparing data for FDA/EMA... scenario completed within the documented Use when cleaning clinical trial data, preparing data for FDA/EMA submission, standardizing... boundary.
The Use this skill for data analysis tasks that require explicit... scenario completed within the documented Use when cleaning clinical trial data, preparing data for FDA/EMA submission, standardizing... boundary.
The Use when cleaning clinical trial data, preparing data for FDA/EMA... path verified the packaged helper command without exposing a deeper execution issue.
The preserved weakness for Packaged executable path(s): scripts/main.py was concentrated in one point: Script execution path is available (command exit code is 0).
The preserved weakness for End-to-end case for Scope-focused workflow aligned to: Use when cleaning clinical trial data, preparing data for FDA/EMA submission, standardizing SDTM datasets, handling missing values in clinical studies, detecting outliers in lab results, or converting raw CRF data to CDISC format. Cleans and standardizes clinical trial data for regulatory compliance with audit trails was concentrated in one point: The output stays within declared skill scope and target objective.
Key Strengths
- Primary routing is Data Analysis with execution mode B
- Static quality score is 88/100 and dynamic average is 84.4/100
- Assertions and command execution outcomes are recorded per input for human review