clinical-reports

12
0
Source

Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.

Install

mkdir -p .claude/skills/clinical-reports && curl -L -o skill.zip "https://mcp.directory/api/skills/download/2089" && unzip -o skill.zip -d .claude/skills/clinical-reports && rm skill.zip

Installs to .claude/skills/clinical-reports

About this skill

Clinical Report Writing

Overview

Clinical report writing is the process of documenting medical information with precision, accuracy, and compliance with regulatory standards. This skill covers four major categories of clinical reports: case reports for journal publication, diagnostic reports for clinical practice, clinical trial reports for regulatory submission, and patient documentation for medical records. Apply this skill for healthcare documentation, research dissemination, and regulatory compliance.

Critical Principle: Clinical reports must be accurate, complete, objective, and compliant with applicable regulations (HIPAA, FDA, ICH-GCP). Patient privacy and data integrity are paramount. All clinical documentation must support evidence-based decision-making and meet professional standards.

When to Use This Skill

This skill should be used when:

  • Writing clinical case reports for journal submission (CARE guidelines)
  • Creating diagnostic reports (radiology, pathology, laboratory)
  • Documenting clinical trial data and adverse events
  • Preparing clinical study reports (CSR) for regulatory submission
  • Writing patient progress notes, SOAP notes, and clinical summaries
  • Drafting discharge summaries, H&P documents, or consultation notes
  • Ensuring HIPAA compliance and proper de-identification
  • Validating clinical documentation for completeness and accuracy
  • Preparing serious adverse event (SAE) reports
  • Creating data safety monitoring board (DSMB) reports

Visual Enhancement with Scientific Schematics

⚠️ MANDATORY: Every clinical report MUST include at least 1 AI-generated figure using the scientific-schematics skill.

This is not optional. Clinical reports benefit greatly from visual elements. Before finalizing any document:

  1. Generate at minimum ONE schematic or diagram (e.g., patient timeline, diagnostic algorithm, or treatment workflow)
  2. For case reports: include clinical progression timeline
  3. For trial reports: include CONSORT flow diagram

How to generate figures:

  • Use the scientific-schematics skill to generate AI-powered publication-quality diagrams
  • Simply describe your desired diagram in natural language
  • Nano Banana Pro will automatically generate, review, and refine the schematic

How to generate schematics:

python scripts/generate_schematic.py "your diagram description" -o figures/output.png

The AI will automatically:

  • Create publication-quality images with proper formatting
  • Review and refine through multiple iterations
  • Ensure accessibility (colorblind-friendly, high contrast)
  • Save outputs in the figures/ directory

When to add schematics:

  • Patient case timelines and clinical progression diagrams
  • Diagnostic algorithm flowcharts
  • Treatment protocol workflows
  • Anatomical diagrams for case reports
  • Clinical trial participant flow diagrams (CONSORT)
  • Adverse event classification trees
  • Any complex concept that benefits from visualization

For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.


Core Capabilities

1. Clinical Case Reports for Journal Publication

Clinical case reports describe unusual clinical presentations, novel diagnoses, or rare complications. They contribute to medical knowledge and are published in peer-reviewed journals.

CARE Guidelines Compliance

The CARE (CAse REport) guidelines provide a standardized framework for case report writing. All case reports should follow this checklist:

Title

  • Include the words "case report" or "case study"
  • Indicate the area of focus
  • Example: "Unusual Presentation of Acute Myocardial Infarction in a Young Patient: A Case Report"

Keywords

  • 2-5 keywords for indexing and searchability
  • Use MeSH (Medical Subject Headings) terms when possible

Abstract (structured or unstructured, 150-250 words)

  • Introduction: What is unique or novel about the case?
  • Patient concerns: Primary symptoms and key medical history
  • Diagnoses: Primary and secondary diagnoses
  • Interventions: Key treatments and procedures
  • Outcomes: Clinical outcome and follow-up
  • Conclusions: Main takeaway or clinical lesson

Introduction

  • Brief background on the medical condition
  • Why this case is novel or important
  • Literature review of similar cases (brief)
  • What makes this case worth reporting

Patient Information

  • Demographics (age, sex, race/ethnicity if relevant)
  • Medical history, family history, social history
  • Relevant comorbidities
  • De-identification: Remove or alter 18 HIPAA identifiers
  • Patient consent: Document informed consent for publication

Clinical Findings

  • Chief complaint and presenting symptoms
  • Physical examination findings
  • Timeline of symptoms (consider timeline figure or table)
  • Relevant clinical observations

Timeline

  • Chronological summary of key events
  • Dates of symptoms, diagnosis, interventions, outcomes
  • Can be presented as a table or figure
  • Example format:
    • Day 0: Initial presentation with symptoms X, Y, Z
    • Day 2: Diagnostic test A performed, revealed finding B
    • Day 5: Treatment initiated with drug C
    • Day 14: Clinical improvement noted
    • Month 3: Follow-up examination shows complete resolution

Diagnostic Assessment

  • Diagnostic tests performed (labs, imaging, procedures)
  • Results and interpretation
  • Differential diagnosis considered
  • Rationale for final diagnosis
  • Challenges in diagnosis

Therapeutic Interventions

  • Medications (names, dosages, routes, duration)
  • Procedures or surgeries performed
  • Non-pharmacological interventions
  • Reasoning for treatment choices
  • Alternative treatments considered

Follow-up and Outcomes

  • Clinical outcome (resolution, improvement, unchanged, worsened)
  • Follow-up duration and frequency
  • Long-term outcomes if available
  • Patient-reported outcomes
  • Adherence to treatment

Discussion

  • Strengths and novelty of the case
  • How this case compares to existing literature
  • Limitations of the case report
  • Potential mechanisms or explanations
  • Clinical implications and lessons learned
  • Unanswered questions or areas for future research

Patient Perspective (optional but encouraged)

  • Patient's experience and viewpoint
  • Impact on quality of life
  • Patient-reported outcomes
  • Quote from patient if appropriate

Informed Consent

  • Statement documenting patient consent for publication
  • If patient deceased or unable to consent, describe proxy consent
  • For pediatric cases, parental/guardian consent
  • Example: "Written informed consent was obtained from the patient for publication of this case report and accompanying images. A copy of the written consent is available for review by the Editor-in-Chief of this journal."

For detailed CARE guidelines, refer to references/case_report_guidelines.md.

Journal-Specific Requirements

Different journals have specific formatting requirements:

  • Word count limits (typically 1500-3000 words)
  • Number of figures/tables allowed
  • Reference style (AMA, Vancouver, APA)
  • Structured vs. unstructured abstract
  • Supplementary materials policies

Check journal instructions for authors before submission.

De-identification and Privacy

18 HIPAA Identifiers to Remove or Alter:

  1. Names
  2. Geographic subdivisions smaller than state
  3. Dates (except year)
  4. Telephone numbers
  5. Fax numbers
  6. Email addresses
  7. Social Security numbers
  8. Medical record numbers
  9. Health plan beneficiary numbers
  10. Account numbers
  11. Certificate/license numbers
  12. Vehicle identifiers and serial numbers
  13. Device identifiers and serial numbers
  14. Web URLs
  15. IP addresses
  16. Biometric identifiers
  17. Full-face photographs
  18. Any other unique identifying characteristic

Best Practices:

  • Use "the patient" instead of names
  • Report age ranges (e.g., "a woman in her 60s") or exact age if relevant
  • Use approximate dates or time intervals (e.g., "3 months prior")
  • Remove institution names unless necessary
  • Blur or crop identifying features in images
  • Obtain explicit consent for any potentially identifying information

2. Clinical Diagnostic Reports

Diagnostic reports communicate findings from imaging studies, pathological examinations, and laboratory tests. They must be clear, accurate, and actionable.

Radiology Reports

Radiology reports follow a standardized structure to ensure clarity and completeness.

Standard Structure:

1. Patient Demographics

  • Patient name (or ID in research contexts)
  • Date of birth or age
  • Medical record number
  • Examination date and time

2. Clinical Indication

  • Reason for examination
  • Relevant clinical history
  • Specific clinical question to be answered
  • Example: "Rule out pulmonary embolism in patient with acute dyspnea"

3. Technique

  • Imaging modality (X-ray, CT, MRI, ultrasound, PET, etc.)
  • Anatomical region examined
  • Contrast administration (type, route, volume)
  • Protocol or sequence used
  • Technical quality and limitations
  • Example: "Contrast-enhanced CT of the chest, abdomen, and pelvis was performed using 100 mL of intravenous iodinated contrast. Oral contrast was not administered."

4. Comparison

  • Prior imaging studies available for comparison
  • Dates of prior studies
  • Stability or change from prior imaging
  • Example: "Comparison: CT chest from [date]"

5. Findings

  • Systematic description of imaging findings
  • Organ-by-organ or region-by-region approach
  • Positive findings first, then pertinent negatives
  • Measurements of lesions or abnormalities
  • Use of standardized terminology (ACR lexicon, RadLex)
  • Example:
    • Lungs: Bilateral ground-glass opacities, predominant in the lower lobes. No consolidation or pleural effusion.
    • Mediastinum: No lymphadenopathy. Heart size normal.
    • Abdomen: Liver, spleen, pancreas unremarkable. No free fluid.

6. Impression/Conclusion

  • Concise summary of key findings
  • Answers to the clinical question
  • Differential diagnosi

Content truncated.

scroll-experience

davila7

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

6332

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

8125

senior-fullstack

davila7

Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.

8122

senior-security

davila7

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.

6819

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

5414

2d-games

davila7

2D game development principles. Sprites, tilemaps, physics, camera.

4812

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318399

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

340397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

452339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.