prepare-safety-committee-exposure-input

Solid

Prepares the exposure contribution to a safety signal review - whether an event tracks exposure, and what the available data could have shown either way. It justifies the exposure metric against the event mechanism rather than defaulting, counts affected subjects lacking PK data and states the bias direction since those cases are usually the sickest, reports stratum event counts before any rate because a rising percentage across two three and four events is not a relationship, and reports the observed exposure range alongside any negative finding so no relationship observed is distinguished from could not have observed one. Use it for a signal review or periodic safety discussion. Example: "Please a signal review or periodic safety discussion." Do not use for escalation decision packs, for submission exposure-safety sections, for nonclinical margins, for committee documentation, or to judge causality or recommend a dose change.

Code & Development 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

# Safety committee exposure input ## Who this is for A clinical pharmacologist asked what exposure has to say about a safety signal — for a safety committee, a signal review, or a benefit–risk discussion where the question is whether exposure explains anything. ## When to use this skill - Preparing the exposure contribution to a safety signal review. - Assembling exposure evidence for a periodic safety discussion. - Answering whether an observed event tracks exposure. - Establishing what exposure data can and cannot say about a signal. - Preparing exposure input where a dose change is being considered by others. ## When NOT to use this skill - **Escalation-decision packs** — use `prepare-escalation-committee-package`. That answers a dose-escalation question; this answers a signal question. - **Exposure–safety in a submission** — use `review-ctd-2734-exposure-safety`. - **Nonclinical margins** — use `review-exposure-safety-margins`. - **Committee documentation** — use `document-safety-committee-decisions`. - **Judging causality, or recommending a dose change.** Refused. Causality assessment belongs to pharmacovigilance and the accountable physician. ## Operating modes | Mode | Question it answers | Minimum inputs | |---|---|---| | `SIGNAL` | Does this event track exposure in the available data? | event data, exposure data | | `INDIVIDUAL` | What was the exposure in the affected subjects? | case data, exposure data | | `POWER` | Could this data have detected a relat...

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

Code & Development Solid

prepare-escalation-committee-package

Assembles the exposure content a safety or escalation committee decides from, derived from the governing rule rather than from whatever data happens to be available. It reports subjects dosed, evaluable, and with the parameter as three distinct denominators, presents every parameter with its precision at the current sample size, states the implication for the next dose level rather than leaving the committee to extrapolate from the current one, and makes what the pack cannot show a named section rather than a footnote. Use it to assemble or review an escalation pack before committee. Example: "Please assemble or review an escalation pack before committee." Do not use for the escalation design itself, for interim look permissions, for committee minutes, or to make or recommend the escalation decision.

6 Updated 6 days ago
malekokour
Code & Development Solid

prepare-dose-justification-evidence

Assembles and organises the evidence behind a registration or dose-optimisation dose justification — exposure-response integration, intrinsic and extrinsic factor coverage, formulation-bridging logic, dose-modification rules — arranged against the questions clinical pharmacology reviewers ask, with every claim carrying a locator and every gap named. Use this skill when someone asks to assemble, index, organise or gap-check the evidence supporting a proposed dose or regimen — for example "pull together what supports the 200 mg dose", "map our dose-modification rules to their evidence", or "which intrinsic factors are uncovered before we file". Do not use for first-in-human starting-dose review, for assessing a development plan for study gaps, or for any request to select, recommend, adjust or justify a dose — that decision belongs to a qualified human and this skill never makes it.

6 Updated 6 days ago
malekokour
AI & Automation Solid

prepare-briefing-package-content

Drafts and reviews the clinical pharmacology portion of a regulatory briefing package — answerable questions to the agency, applicant positions with their supporting evidence, and validated annex cross-references — aligned to the public structure of clinical pharmacology review. Use this skill when someone asks to draft, structure, stress-test or QC the CP content of a briefing book or meeting package — for example "draft the clin pharm section of our pre-NDA briefing package", "which questions should we ask", or "check every position in this package is actually supported". Do not use for responding to questions an agency has already sent, for writing the meeting request itself, for CTD summary or labelling content, or for any request to decide whether a position will be accepted.

6 Updated 6 days ago
malekokour