domains / families / research / clinpgx-database

clinpgx-database

combined

Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions. Access ClinPGx pharmacogenomics data (successor to PharmGKB) when you need to query gene-drug interactions, CPIC guidelines, allele functions, and drug-label PGx content for precision medicine and genotype-guided dosing.

When to use

• **Gene-drug interactions**: Querying how genetic variants affect drug metabolism, efficacy, or toxicity
• **CPIC guidelines**: Accessing evidence-based clinical practice guidelines for pharmacogenetics
• **Allele information**: Retrieving allele function, frequency, and phenotype data
• **Drug labels**: Exploring FDA and other regulatory pharmacogenomic drug labeling
• **Pharmacogenomic annotations**: Accessing curated literature on gene-drug-disease relationships
• **Clinical decision support**: Using PharmDOG tool for phenoconversion and custom genotype interpretation
• **Precision medicine**: Implementing pharmacogenomic testing in clinical practice
• **Drug metabolism**: Understanding CYP450 and other pharmacogene functions

When not to use

• Do not use this skill when the required source data, identifiers, files, or credentials are missing.
• Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
• Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.

Skill page

Conflict

The copies overlap heavily on the ClinPGx REST API endpoints and rate limits, but they disagree on the execution model and add different material steps. The Vibe-Skills and OpenClaw copies are near-identical, providing a detailed API reference with inline Python examples. The aipoch copy is a wrapper that mandates a specific packaged script (scripts/query_clinpgx.py), a different dependency version (requests>=2.31.0), and a specific retry/backoff implementation. Because the aipoch copy provides a distinct, more robust execution path (script-based with retries) while the others provide a direct API reference, crowning one would hide the alternative implementation strategy.