clinical-reports

Trigger phrases

Phrases that activate this skill when typed to Claude Code:

• write a case report
• clinical trial report
• SOAP note
• radiology report
• discharge summary

What it does

clinical-reports is a Claude Code skill from K-Dense AI’s scientific-agent-skills repo. It turns Claude into a clinical documentation specialist that writes four categories of clinical reports: case reports following CARE guidelines, diagnostic reports (radiology, pathology, laboratory), clinical trial reports (ICH-E3 clinical study reports, SAE narratives, CSRs), and patient documentation (SOAP notes, history and physical, discharge summaries). All output includes regulatory compliance markers — HIPAA, FDA submission standards, ICH-GCP — and validation checklists.

A session produces a properly structured clinical document with all required sections, appropriate medical terminology, and a compliance checklist for the applicable regulatory standard.

When to use it

Reach for it when:

• You’re writing a clinical case report for journal submission and need CARE guideline structure enforced
• You need to draft SAE narratives or clinical study reports for regulatory submission to FDA or EMA
• You’re training clinical staff on standardized documentation formats (SOAP notes, H&P structure)

When not to reach for it:

• Scientific manuscripts that aren’t clinical documents — use scientific-writing
• Clinical data analysis or ML — use pyhealth

Install

Copy the SKILL.md from K-Dense AI’s clinical-reports folder into .claude/skills/clinical-reports/ in your project.

Trigger phrases: “write a case report”, “clinical trial report”, “SOAP note”, “radiology report”, “discharge summary”.

What a session looks like

A typical session has three phases:

1. Document type and regulatory context. Specify the report type and the applicable guideline or regulatory standard. Claude confirms the required sections, word limits (where applicable), and compliance requirements before drafting.
2. Structured drafting. Each section of the document is drafted in sequence with appropriate clinical terminology, standardized terminology systems (ICD-10, SNOMED CT where applicable), and regulatory language. De-identified patient information is used as instructed.
3. Compliance validation. A checklist is generated confirming that all required sections are present, all mandatory fields are populated, and the document complies with the applicable standard. Gaps are flagged with specific remediation instructions.

Receipts

Where it works well:

• CARE guideline case report structure — the 13-item CARE checklist is enforced systematically, ensuring sections that authors commonly omit (patient perspective, patient consent, timeline) are present
• SAE narrative structure — the regulatory required elements (onset, severity, treatment, outcome, causality assessment) are correctly sequenced for FDA submission

Where it backfires:

• Clinical content accuracy depends entirely on the information you provide — the skill structures and formats the document, but the clinical facts, diagnoses, and assessments must come from a qualified clinician
• Radiology and pathology report language is highly institution-specific; generated drafts require review and editing by the relevant specialist before use

Pattern that works: provide the case facts in bullet points first, then ask the skill to structure them into the required format — it’s faster and more accurate than asking Claude to generate clinical facts from a vague description.

Source and attribution

Originally authored by K-Dense Inc.. The canonical SKILL.md lives in the clinical-reports folder of their public scientific-agent-skills repository.

License: MIT. Install, adapt, and redistribute with attribution preserved.

This page documents the skill from a practitioner’s perspective. For the formal spec and any updates, defer to the source repo.