clinical-reports
The clinical-reports Claude Code skill generates compliant medical documentation including case reports following CARE guidelines, diagnostic reports for radiology and pathology, clinical trial reports meeting ICH-E3 standards, and patient records in SOAP and discharge summary formats. Use this skill when documenting medical cases for journal publication, creating diagnostic assessments, reporting clinical trial data and adverse events, preparing regulatory submissions, writing patient progress notes, or ensuring HIPAA compliance and documentation accuracy across healthcare settings.
git clone --depth 1 https://github.com/K-Dense-AI/claude-scientific-writer /tmp/clinical-reports && cp -r /tmp/clinical-reports/skills/clinical-reports ~/.claude/skills/clinical-reportsSKILL.md
# Clinical Reports ## Purpose Prepare **draft reporting structures**, aggregate tables, and review manifests from verified authorized facts. Route each artifact to the correct reporting guidance, preserve provenance, and stop when source support or qualified review is missing. This skill does not establish legal, regulatory, ethical, journal, accreditation, or institutional compliance. Its scripts check structure and internal consistency only. ## Non-Negotiable Boundary Never: - diagnose, recommend treatment, choose or change dosing, triage, or provide return precautions; - interpret images, specimens, raw laboratory results, symptoms, or other clinical observations; - invent, infer, normalize, “complete,” or silently reconcile observations, results, dates, units, denominators, causality, expectedness, seriousness, outcomes, or conclusions; - create an individual case safety report from patient-level narrative or decide reportability; - sign, attest, approve, file, transmit, submit, amend a source record, or act as a licensed clinician, pathologist, radiologist, laboratorian, safety physician, statistician, privacy officer, attorney, or regulatory professional; - use real PHI in examples, assets, tests, prompts, logs, or external services; - call an external LLM, image service, API, or another skill. All generated artifacts must remain visibly marked: > DRAFT — NOT FOR CLINICAL USE, SIGNATURE, FILING, OR SUBMISSION. Populate only from verified authorized source records. Qualified review and sign-off are required. If the request crosses a boundary, stop the unsafe portion. Offer a blank structured template, a source-fact manifest, or a deterministic structural check. Direct clinical or regulatory decisions to the responsible qualified professional. ## Input Gate Proceed only when all conditions are true: 1. **Purpose is explicit**: publication draft, diagnostic-report scaffold, trial-results manuscript, protocol reporting review, CSR draft, aggregate safety table, or aggregate research summary. 2. **Data class is allowed**: `synthetic`, `deidentified`, or `aggregate`. 3. **Authority is documented**: the requester is authorized to use the records for the stated purpose. 4. **Local-only handling is feasible**: no upload, remote API, telemetry, or credential is needed. 5. **Minimum necessary is defined**: exclude fields not needed for the artifact. 6. **Provenance exists**: every populated field or claim maps to one or more verified source-fact IDs. 7. **Review owner is identified**: qualified clinical, statistical, safety, privacy, legal, journal, and/or regulatory review as applicable. Do not accept raw free-text patient records when a structured source-fact manifest can be supplied. Do not copy direct identifiers into this skill’s templates or scripts. ## Route Before Drafting | Artifact | Primary route | Important boundary | |---|---|---| | Case report for publication | CARE 2013 checklist and 2017 explanation | Publication consent, privacy, journal policy, and clinical accuracy require human verification | | Radiology draft scaffold | ACR 2025 communication practice parameter plus modality-specific ACR material | A qualified radiologist authors findings/impression and handles nonroutine communication | | Pathology draft scaffold | Current specimen-specific CAP Cancer Protocol, if applicable | A qualified pathologist selects the protocol/version and authors diagnosis | | Laboratory draft scaffold | 42 CFR 493.1291 and laboratory policy | The performing laboratory controls results, reference intervals, corrections, and release | | Randomized-trial results report | CONSORT 2025 plus every applicable current extension | CONSORT is reporting guidance, not a conduct or submission standard | | Randomized-trial protocol report | SPIRIT 2025 plus applicable extensions | SPIRIT is for protocols, not results or CSRs | | Clinical Study Report | ICH E3 plus E3 Q&A; consider ICH E6(R3) and regional requirements | E3 is adaptable guidance, not a rigid universal template | | Pre-approval safety report | ICH E2A; E2B(R3) for electronic ICSR data; applicable regional law/guidance | Qualified sponsor/investigator safety assessment controls reportability and timing | | Post-approval individual safety report | ICH E2D(R1), E2B(R3), and regional requirements | Do not automate case assessment, coding, or submission | | Aggregate safety presentation | Protocol/SAP, ICH E3, CONSORT Harms, and applicable FDA/ICH guidance | Aggregate tables never determine individual-case reportability | | Aggregate research summary | Study-design-specific reporting guideline and source protocol/SAP | State population, estimand, denominator, missingness, and limitations exactly as verified | Read `references/report_type_routing.md` before choosing a route. Use the dated primary-source ledger in `references/sources.md`; check the live official source when requirements could have changed. ## Safe Drafting Workflow ### 1. Create a source-fact manifest Use `assets/provenance_manifest_template.json`. Record only local record locators, field paths, verification state, verifier role, verification date, and a SHA-256 value hash. Do not duplicate source content or direct identifiers. Every draft claim or populated field must cite one or more fact IDs. Unsupported content remains `null` or `missing`; never replace it with plausible text. ### 2. Generate the correct template ```bash PYTHONDONTWRITEBYTECODE=1 python3 scripts/generate_report_template.py --list PYTHONDONTWRITEBYTECODE=1 python3 scripts/generate_report_template.py \ --type case-report \ --output ./case-report-draft.json ``` The generator copies a fail-closed JSON template. It does not populate clinical content, create directories, overwrite files by default, or certify readiness. ### 3. Populate verified fields only - Keep `draft_status` unchanged. - Replace `null` only when a verified fact ID supports the field. - Preserve uncertainty and “not ass
Comprehensive citation management for academic research. Search Google Scholar and PubMed for papers, extract accurate metadata, validate citations, and generate properly formatted BibTeX entries. This skill should be used when you need to find papers, verify citation information, convert DOIs to BibTeX, or ensure reference accuracy in scientific writing.
Prepare and validate research-only clinical decision-support evaluation, evidence-profile, cohort, survival, biomarker/model, privacy, and governance artifacts. Use for aggregate or synthetic research documentation and traceability—not patient care or live clinical operation.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.
Create, edit, analyze, or convert Excel spreadsheets (.xlsx, .xlsm, .xltx) where the workbook file is the primary deliverable. Use for formulas, formatting, financial models, multi-sheet workbooks, and tabular cleanup exported to Excel. Also applies to .csv/.tsv when the user wants spreadsheet output. Do NOT use for Word documents, HTML reports, standalone Python scripts, database pipelines, or Google Sheets API work.
Generate or edit images with AI models through the OpenRouter Image API (Gemini, FLUX, Seedream, Recraft, GPT-Image). Use for photos, illustrations, artwork, concept art, visual assets, logos, and image editing or compositing from reference images. For flowcharts, circuits, pathways, and other technical diagrams, use the scientific-schematics skill instead.
Formulate evidence-bounded scientific questions, candidate hypotheses, rival explanations, causal or associational claims, discriminating predictions, measurements, and preregistration-ready analysis plans. Use when turning observations or preliminary findings into transparent, testable research plans without treating hypotheses as facts.