skills/biostatistics/clinical-decision-support-documents/SKILL.md
Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports. Covers structure, executive summaries, evidence grading (1A–2C), stats (HR, CI, survival), and biomarker integration. Use for pharma research docs, clinical guidelines, regulatory submissions.
npx skillsauth add jaechang-hits/sciagent-skills clinical-decision-support-documentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Clinical decision support (CDS) documents are analytical reports for pharmaceutical research, guideline development, and regulatory submissions. This knowhow covers two main document types: Patient Cohort Analyses (biomarker-stratified group outcomes) and Treatment Recommendation Reports (evidence-graded clinical guidelines). For individual patient-level treatment plans, use the treatment-plans skill instead.
Patient Cohort Analysis — Group-level statistical comparison of patient subgroups stratified by biomarkers, molecular subtypes, or clinical characteristics.
Treatment Recommendation Report — Evidence-based clinical guidelines with GRADE-graded recommendations for disease management.
The Grading of Recommendations, Assessment, Development and Evaluations (GRADE) system classifies recommendations by strength and evidence quality:
| Grade | Strength | Evidence Quality | Meaning | |-------|----------|-----------------|---------| | 1A | Strong | High | Benefits clearly outweigh risks; consistent RCT data | | 1B | Strong | Moderate | Benefits likely outweigh risks; limited RCT data | | 2A | Weak | High | Trade-offs exist; high-quality evidence but patient values matter | | 2B | Weak | Moderate | Uncertain trade-offs; limited evidence | | 2C | Weak | Low | Very uncertain; expert opinion or observational data only |
| Metric | Abbreviation | Definition | |--------|-------------|------------| | Overall Survival | OS | Time from treatment start to death from any cause | | Progression-Free Survival | PFS | Time to disease progression or death | | Objective Response Rate | ORR | Proportion with CR + PR per RECIST 1.1 | | Duration of Response | DOR | Time from first response to progression | | Disease Control Rate | DCR | Proportion with CR + PR + SD |
Use this framework to select the appropriate document type:
Is this about a POPULATION or an INDIVIDUAL patient?
├── POPULATION (group-level analysis)
│ ├── Comparing outcomes between subgroups? → Patient Cohort Analysis
│ ├── Developing treatment guidelines? → Treatment Recommendation Report
│ └── Both analysis and recommendations? → Combined (cohort analysis + recommendations chapter)
└── INDIVIDUAL (single patient)
└── Use treatment-plans skill instead
| Scenario | Document Type | Key Sections | |----------|--------------|-------------| | Phase 2/3 trial subgroup analysis | Cohort Analysis | Biomarker stratification, survival curves, forest plots | | Clinical practice guideline | Treatment Recommendations | GRADE-graded recs, decision algorithm, evidence tables | | Companion diagnostic development | Cohort Analysis | Biomarker-response correlation, sensitivity/specificity | | Medical affairs strategy | Treatment Recommendations | Competitive landscape, positioning, KOL education | | Real-world evidence study | Cohort Analysis | EMR cohort definition, outcomes by treatment arm |
Always start with a full-page executive summary: Page 1 should contain 3–5 colored summary boxes (findings, biomarkers, implications, statistics, safety) that are scannable in 60 seconds. No table of contents on page 1. This is the single most impactful formatting decision for CDS documents.
Use GRADE consistently: Every treatment recommendation must have a GRADE rating (1A–2C) with documented rationale. Do not mix GRADE with other rating systems within the same document.
Report effect sizes, not just p-values: Always include hazard ratios or odds ratios with 95% confidence intervals. A p-value alone does not convey clinical significance or effect magnitude.
Specify biomarker assay details: Name the platform (e.g., FoundationOne CDx, Ventana PD-L1 SP263), cut-points, and validation status. Biomarker results are only actionable when the assay is known.
Use RECIST 1.1 for response assessment: For immunotherapy cohorts, note iRECIST criteria and pseudoprogression handling. Clearly state which criteria were used.
Include number-at-risk tables: Below every Kaplan-Meier curve, show the number of patients at risk at each time point. This is mandatory for credible survival analysis.
Declare data completeness and follow-up: Report median follow-up time, data maturity (% events), and how missing data was handled (complete case, imputation method).
De-identify per HIPAA Safe Harbor: Remove all 18 HIPAA identifiers before including any patient-level data. Add confidentiality headers for proprietary pharmaceutical data.
Color-code consistently: Blue = data/information, green = biomarkers/positive, orange = clinical implications/caution, red = warnings/safety, gray = statistics/methods.
Date and version all recommendations: Include analysis date, data cutoff date, and planned update schedule. Treatment guidelines become outdated as new trial data emerges.
Mixing population-level and individual-level recommendations: CDS documents analyze cohorts, not individuals. Stating "Patient X should receive..." is inappropriate. How to avoid: Use language like "Patients with biomarker X may benefit from..." or "Evidence supports [therapy] for [population] (Grade 1B)."
Over-interpreting subgroup analyses: Post-hoc subgroup analyses are hypothesis-generating, not confirmatory. How to avoid: Always label exploratory vs pre-specified subgroups. Report interaction p-values. State "These findings require prospective validation."
Omitting confidence intervals: Reporting median PFS = 12.5 months without CI makes the precision invisible. How to avoid: Always format as "median PFS 12.5 months (95% CI: 9.8–15.2)."
Ignoring competing risks: In oncology cohorts, patients may die from non-cancer causes, biasing standard Kaplan-Meier estimates. How to avoid: For OS analysis, note competing causes. For PFS, acknowledge censoring for non-disease events.
Inconsistent GRADE application: Grading one recommendation as 1A but not grading others leaves quality gaps. How to avoid: Grade every recommendation. If evidence is insufficient, assign 2C with "insufficient evidence" note.
Executive summary that is too detailed: A 2-page executive summary defeats the purpose. How to avoid: Limit to page 1 only. Use bullet points in colored boxes, not paragraphs. End with \newpage before TOC.
Missing regulatory compliance elements: Omitting confidentiality notices or HIPAA de-identification in pharmaceutical documents. How to avoid: Add confidentiality header to every page. Include de-identification statement in methods section.
CDS documents use specific LaTeX packages and formatting:
tcolorbox package with color-coded environmentsbooktabs for professional formatting, longtable for multi-page tablespgfplots for survival curves\thispagestyle{empty} + executive summary boxes + \newpageEach CDS document's page 1 should have 3–5 tcolorbox elements:
When stratifying cohorts by biomarkers:
tools
Fast short-read DNA aligner for WGS/WES/ChIP-seq. 2× faster BWA-MEM successor; outputs SAM/BAM with read group headers for GATK. Primary plus supplementary records for chimeric reads. Use STAR for RNA-seq splice-aware alignment; Bowtie2 is a comparable alternative.
tools
smina molecular docking CLI. AutoDock Vina fork with customizable scoring functions, native SDF/MOL2/PDB ligand input, autoboxing, local energy minimization, and per-atom score breakdowns. Pipeline: receptor PDBQT prep -> ligand prep (RDKit/OpenBabel) -> dock via autobox or explicit grid -> rescore/minimize with custom scoring -> rank poses by affinity. Choose smina over Vina when you need custom scoring terms (--custom_scoring), local optimization of an existing pose (--local_only), per-atom contributions (--atom_term_data), or SDF/MOL2 ligands without manual PDBQT conversion. For unknown binding sites use diffdock-blind-docking; for the Python-bindings/Vinardo workflow use autodock-vina-docking.
development
mdtraj molecular dynamics trajectory analysis (Python). Reads DCD/XTC/TRR/NetCDF/H5/PDB topologies and trajectories; computes RMSD vs time, radius of gyration, per-residue RMSF, residue-residue contact frequency maps, phi/psi torsions for Ramachandran plots (general + Gly/Pro), and 8-state DSSP secondary structure. Modules: trajectory I/O, geometry (distances/angles/dihedrals), structural analysis (RMSD/Rg/RMSF/SASA), contacts, hydrogen bonds, secondary structure (DSSP), NMR observables. For broader atom-selection grammar use mdanalysis-trajectory; for running MD simulations use OpenMM/GROMACS.
development
Programmatic PubMed access via NCBI E-utilities REST API. Covers Boolean/MeSH queries, field-tagged search, endpoints (ESearch, EFetch, ESummary, EPost, ELink), history server for batches, citation matching, systematic review strategies. Use for biomedical literature search or automated pipelines.