assess-special-population-strategy

Solid

Assesses the completeness and internal consistency of a programme's special-population evidence strategy — renal impairment, hepatic impairment, paediatrics, pregnancy and lactation, elderly, and other defined sub-populations — against the programme's declared scope, the target product profile, and the guidance-anchored criteria that create study or analysis obligations for each population. Use this skill when someone asks whether the special-population strategy covers what a reviewer will expect, which populations still need characterisation, or whether the strategy documents are internally consistent. Example: "Please the special-population strategy covers what a reviewer will expect, which populations still need characterisation." Do not use for reviewing one organ-impairment study report, for demographic covariate assessment in a PopPK, for pharmacogenomic characterisation, or for any request to decide whether a waiver rationale is sufficient or to commit to a study.

Data & Documents 6 stars 0 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
28
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Special Population Strategy Assessment Assess a programme's special-population evidence strategy for completeness, internal consistency, and traceability to the criteria that create each obligation. Cover renal impairment, hepatic impairment, paediatrics, pregnancy and lactation, elderly, and any other population the programme's scope declares — each mapped to whether it is addressed by a dedicated study, a PopPK covariate analysis, a model-based approach, a written waiver rationale, or nothing. **This skill assesses the strategy. It never decides that a waiver is sufficient, commits to a study, selects a dose for a special population, or determines that characterisation is adequate for filing.** ## Who this is for Clinical pharmacology leads owning a programme's special-population strategy · CP reviewers preparing for a pre-NDA or Type C meeting · regulatory strategists checking that the strategy matches what the evidence expectations demand for each population. ## When to use this skill - "Does our special-population strategy cover what a reviewer will expect?" - "Which populations still need characterisation before we file?" - "Is our paediatric plan consistent with what we told the agency?" - "Map every special population to whether we have a study, a PopPK analysis, a waiver, or nothing" - "Are the renal and hepatic strategies internally consistent with the dose-modification rules?" ## When NOT to use this skill | Request | Why not this skill | Where it belongs...

Details

Author
malekokour
Repository
malekokour/clinpharm-pmx-skills
Created
1 weeks ago
Last Updated
6 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

assess-demographic-covariate-effects

Assesses whether age, sex and body-size covariate effects on exposure are characterised, internally consistent, and traceable to their sources — the PopPK covariate analysis, any dedicated sub-study, the factor-coverage matrix and the labelling concept — and flags effects that are stated without a source, sourced but unstated, or stated inconsistently across documents. Use this skill when someone asks whether demographic covariates are adequately characterised for a programme, whether the age, weight or sex effects in a PopPK report match what the label says, or what demographic gaps remain before filing. Example: "Are age, weight and sex effects characterised for this compound?" Do not use for pharmacogenomic covariates, for renal or hepatic impairment, for drug-drug interactions, for selecting or adjusting a dose, or for any request to decide whether a covariate effect is clinically meaningful.

6 Updated 6 days ago
malekokour
Code & Development Solid

assess-pharmacogenomic-evidence

Assesses whether pharmacogenomic covariate effects are characterised across the programme's evidence base — in-vitro enzyme and transporter genotype data, PopPK covariate analyses, dedicated PGx sub-studies, and the labelling concept — producing a gene-enzyme-phenotype register in which every stated PGx effect traces to its source and every source-identified polymorphism traces to its downstream statement. Use this skill when someone asks whether pharmacogenomic effects are characterised for a compound, whether a PopPK analysis covers the relevant polymorphisms, or what PGx gaps remain. Example: "Please pharmacogenomic effects are characterised for a compound." Do not use for demographic covariates (age, sex, body size), for organ-impairment characterisation, for drug-drug interaction assessment, or for any request to recommend a genotype-based dose adjustment.

6 Updated 6 days ago
malekokour
Code & Development Solid

assess-development-plan-gaps

Assesses a clinical pharmacology development plan against guidance-anchored evidence expectations, classifying every expected element as present, triggered, waivable-with-rationale, or a residual gap, each traced to the criterion that creates the obligation. Use this skill when someone asks what clinical pharmacology evidence a programme is still missing, whether a plan covers what a reviewer will expect, or which studies the drug's own properties have made obligatory — for example "what CP work are we still missing before the pre-NDA meeting" or "does this plan cover the renal and hepatic expectations". Do not use for reviewing one interaction package, for assembling agency-facing briefing content, or for any request to decide whether a gap is acceptable, to commit to a study, or to approve a plan.

6 Updated 6 days ago
malekokour