assess-protocol-amendment-impact

Solid

Assesses what a protocol amendment does to data a running study has already produced and to what the study can still conclude. It states enrolment at the time of amendment because impact scales with it, assesses poolability per analysis rather than once for the study - a sampling change is often poolable for population modelling and not for non-compartmental parameters - names objectives that become unanswerable rather than letting them surface at reporting, and builds the propagation list from the dependent documents rather than the amendment cover note. Use it before implementation, to settle poolability, or to reconstruct an implemented amendment. Example: "Please unplanned deviations, sampling schedule adequacy, analysis plan amendments specifically." Do not use for unplanned deviations, sampling schedule adequacy, analysis plan amendments specifically, or to approve the amendment.

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

# Protocol amendment impact assessment ## Who this is for A clinical pharmacologist assessing what a protocol amendment does to the data a running study has already produced, and to what the study will be able to conclude. ## When to use this skill - Assessing a proposed amendment before it is implemented. - Establishing whether data before and after an amendment can be pooled. - Reviewing an amendment's effect on the analysis plan and the objectives. - Reconstructing, after the fact, what an implemented amendment changed. - Preparing the clinical pharmacology position on an amendment for governance. ## When NOT to use this skill - **Deviation and compliance impact** — use `review-study-conduct-pk`. A deviation is unplanned; an amendment is deliberate, and the analysis differs. - **Sampling schedule adequacy** — use `review-pkpd-sampling-schedule`. - **Analysis plan amendments specifically** — use `review-pk-analysis-plan`, which handles the unblinding-timing question those carry. - **Approving the amendment.** Refused. ## Operating modes | Mode | Question it answers | Minimum inputs | |---|---|---| | `POOLABILITY` | Can pre- and post-amendment data be analysed together? | current and proposed protocol | | `OBJECTIVES` | What can the study still conclude? | protocol, objectives, enrolment status | | `PROPAGATION` | What else must change? | protocol, analysis plan, other documents | | `RECONSTRUCT` | What did an implemented amendment actually change? | protocol ver...

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

prepare-assessment-aid-position

Structures the clinical pharmacology content of an assessment aid or applicant's position document — the tabulated summary an agency requests to facilitate their review. Extracts every CP claim, traces it to its source document, verifies internal consistency, and flags any position statement that crosses into a clinical or regulatory decision. Use when asked to prepare or review an assessment aid's CP section. Do not use for drafting agency responses, for meeting preparation, or for taking a position.

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
Data & Documents Solid

assess-special-population-strategy

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.

6 Updated 6 days ago
malekokour