Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mims-harvard/tooluniverse-clinical-data-integration
End-to-end drug safety review integrating FDA labels, FAERS adverse event reports, PRR/ROR disproportionality, pharmacogenomic biomarkers, clinical trial data, and published literature.
Passed 14 of 18 test cases with the skill, and 13 of 18 without it.
2 fixed16 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
When calling the PubMed article search tool during Phase 5 literature extraction, does the tool return articles inside a nested dictionary key like '{"articles": [...]}' or directly as a plain list of article objects?
| Checked | Without skill | With skill |
|---|---|---|
| States that the PubMed article search tool returns a plain list of article dictionaries | Missed | Passed |
The instructions your model reads when the skill loads.
End-to-end drug safety review pipeline that integrates FDA label information, FAERS spontaneous reports, disproportionality signal detection, pharmacogenomic biomarkers, clinical trial data, and published literature. Designed for regulatory assessments, pharmacovigilance, and clinical decision support.
Guiding principles:
Clinical data integration starts with data harmonization. Different hospitals code the same diagnosis differently (ICD-10 vs SNOMED). Before merging datasets, verify the coding system. Missing data is informative — a missing lab value may mean the test wasn't ordered (patient was stable) not that the result was normal.
When uncertain about any scientific fact, SEARCH databases first rather than reasoning from memory. A database-verified answer is always more reliable than a guess.
Differentiation: This skill emphasizes regulatory-grade data integration across the full drug lifecycle. For focused FAERS signal detection with quantitative scoring, see tooluniverse-adverse-event-detection. For general pharmacovigilance workflows, see tooluniverse-pharmacovigilance.
When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.
Typical triggers:
| Source | Type | Best For |
test cases passed, vs 13 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.