clinical-reports
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.
What this skill does
# 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:** ```bash 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
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.