Token导航 LogoToken导航

Agent Skill · 研究检索

adverse-event-narrative(不良事件叙述)

adverse-event-narrative 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

adverse-event-narrative 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 16,125。

总安装 7,368周安装 301GitHub Stars 公开资料未说明下载 2,360核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.1.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:adverse-event-narrative(不良事件叙述)
来源仓库:https://github.com/aipoch-ai/adverse-event-narrative
安装命令:
openclaw skills install adverse-event-narrative
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install adverse-event-narrative

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

adverse-event-narrative 用于药物警戒文档生成,适合在 OpenClaw 中创建 CIOMS 合规报告。它根据个案安全报告生成结构化不良事件叙述。通过 clawhub 安装后,可结合来源仓库和 README 验证使用流程。安装前需确认权限范围、维护状态及是否触发敏感数据处理。

建议查阅原始文档了解输入格式和合规要求。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install adverse-event-narrative;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

adverse-event-narrative 怎么安装?

在终端执行 openclaw skills install adverse-event-narrative。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

adverse-event-narrative 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

adverse-event-narrative 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

adverse-event-narrative 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

adverse-event-narrative 用的人多吗?

公开数据是累计安装 7,368 次,近一周安装 301 次,下载 2,360 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

adverse-event-narrative 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
adverse-event-narrative

不良事件叙述 · 本页

7,368—只读MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
adverse-event-narrative
description
Generate CIOMS-compliant adverse event narratives for Individual Case
allowed-tools
[Read, Write, Bash, Edit]
license
MIT
metadata
skill-author
AIPOCH

Adverse Event Narrative Generator

Overview

Regulatory-grade narrative generation tool that transforms adverse event case data into CIOMS-compliant ICSR narratives suitable for submission to FDA, EMA, and other health authorities.

Key Capabilities:

  • CIOMS I Compliance: Standardized narrative structure per international guidelines
  • ICH E2B Integration: Electronic submission format compatibility
  • Temporal Analysis: Timeline reconstruction and causality assessment
  • Medical Accuracy: Clinical terminology and MedDRA coding
  • Multi-Case Processing: Batch narrative generation for periodic reporting
  • Quality Validation: Automated checks for completeness and consistency

When to Use

✅ Use this skill when:

  • Drafting ICSR narratives for regulatory submissions
  • Converting safety case data to standardized text
  • Preparing adverse event reports for health authorities
  • Generating case summaries for signal detection
  • Creating pharmacovigilance documentation for clinical trials
  • Standardizing narrative format across safety teams
  • Training new drug safety associates on narrative writing

❌ Do NOT use when:

  • Case requires medical judgment or causality assessment → Use qualified safety physician
  • Narrative for litigation or legal proceedings → Use legal documentation standards
  • Patient-facing communications → Use lay-summary-gen
  • Aggregate safety summaries → Use safety-summary-reports
  • Coding MedDRA terms from verbatim → Use meddra-coder

Integration:

  • Upstream: meddra-coder (MedDRA term coding), clinical-data-cleaner (data preparation)
  • Downstream: safety-summary-reports (aggregate analysis), regulatory-submission-prep (FDA/EMA filing)

Core Capabilities

1. CIOMS I Narrative Structure

Generate standardized sections per CIOMS guidelines:

from scripts.narrative_generator import NarrativeGenerator

generator = NarrativeGenerator()

# Generate complete narrative
narrative = generator.generate(
    case_data=case_json,
    format="cioms_i",  # or "ich_e2b", "fda_medwatch"
    include_meddra=True
)

narrative.save("ICSR_2024_001_narrative.txt")

Standard Sections:

  1. Patient Demographics - Age, sex, weight, relevant characteristics
  2. Medical History - Significant pre-existing conditions
  3. Concomitant Medications - Other drugs at time of event
  4. Suspect Drug(s) - Medication(s) in question with dosing
  5. Adverse Event - Detailed reaction description with MedDRA terms
  6. Diagnostic Results - Lab values, imaging, procedures
  7. Treatment - Medical management of the event
  8. Dechallenge/Rechallenge - Effect of drug withdrawal/reintroduction
  9. Outcome - Final patient status and sequelae
  10. Causality Assessment - Reporter's relationship evaluation

2. Temporal Relationship Analysis

Reconstruct timeline and assess temporal plausibility:

# Analyze temporal relationships
timeline = generator.analyze_timeline(
    drug_start="2024-01-15",
    drug_stop="2024-02-01",
    ae_onset="2024-01-28",
    dechallenge_date="2024-02-01",
    rechallenge_date=None
)

# Output shows temporal assessment
# "AE onset 13 days after drug initiation, positive dechallenge within 24h"

Assessments Generated:

  • Time to onset (latency period)
  • Dechallenge response (positive/negative/unknown)
  • Rechallenge response (if applicable)
  • Temporal plausibility (consistent with known drug profile)

3. Causality Evaluation Support

Structure causality assessment per WHO-UMC criteria:

# Generate causality section
causality = generator.assess_causality(
    case_data=case,
    criteria="who_umc",  # or "naranjo", "cochrane"
    include_rationale=True
)

# Output structured assessment with points for each criterion

WHO-UMC Categories:

  • Certain - Event reproduced on rechallenge
  • Probable/Likely - Reasonable time, positive dechallenge, alternative causes unlikely
  • Possible - Compatible time, but alternative causes possible
  • Unlikely - Incompatible time or alternative cause probable
  • Conditional/Unclassified - Insufficient information
  • Unassessable/Unclassifiable - Data contradictory or incomplete

4. Multi-Format Output

Generate narratives for different regulatory contexts:

# FDA MedWatch Form 3500A
fda_narrative = generator.generate(
    case_data=case,
    format="fda_medwatch",
    max_length=2000  # Character limit
)

# EMA E2B(R3) electronic format
ema_narrative = generator.generate(
    case_data=case,
    format="ich_e2b",
    version="R3"
)

# CIOMS I paper format
cioms_narrative = generator.generate(
    case_data=case,
    format="cioms_i"
)

Common Patterns

Pattern 1: Serious Adverse Event (Hospitalization)

Scenario: Patient hospitalized for severe drug reaction.

{
  "case_id": "2024-SAE-001",
  "patient_age": "58 years",
  "patient_sex": "Female",
  "suspect_drugs": [{
    "drug_name": "Metformin",
    "dose": "1000 mg BID",
    "dates": "2024-01-15 to 2024-02-01"
  }],
  "adverse_events": [{
    "meddra_pt": "Lactic acidosis",
    "seriousness": "Hospitalization",
    "onset": "2024-01-28"
  }],
  "outcome": "Recovered with sequelae"
}

Narrative Emphasis:

  • Hospitalization details (admission/discharge dates)
  • Severity markers (ICU stay, intubation)
  • Lactate levels and trend
  • Renal function status
  • Complete recovery timeline

Pattern 2: Fatal Outcome Case

Scenario: Death suspected to be drug-related.

# Fatal case handling
narrative = generator.generate(
    case_data=fatal_case,
    format="cioms_i",
    include_autopsy=True,
    cause_of_death_analysis=True
)

Critical Elements:

  • Complete medical history relevant to death
  • Concomitant medications contributing
  • Autopsy findings (if performed)
  • Cause of death per death certificate
  • Alternative causes ruled out
  • Reporter's opinion on contribution to death

Pattern 3: Rechallenge Case

Scenario: Positive rechallenge confirms drug causation.

Key Documentation:

  • First exposure dates and reaction
  • Dechallenge response
  • Rechallenge dates and circumstances
  • Recurrence of same reaction
  • Any differences in severity
  • Conclusion on causality

Narrative Structure:

First Exposure:
- Drug X initiated [date]
- AE occurred [date], [description]
- Drug discontinued [date]
- Dechallenge: [positive/negative]

Rechallenge:
- Drug X reintroduced [date]
- Same AE recurred [date]
- Drug discontinued [date]
- Outcome: [status]

Causality: Certain (positive rechallenge)

Pattern 4: Multi-Drug Reaction

Scenario: Multiple suspect drugs, need to identify most likely culprit.

Analysis Approach:

  • Temporal sequence of drug initiations
  • Time to onset for each drug
  • Known adverse reaction profiles
  • Dechallenge attempts (if any)
  • Rechallenge data (if any)
  • Reporter's primary suspect

Narrative Organization:

  1. List all suspect drugs with indication and dates
  2. Describe temporal relationship for each
  3. Discuss dechallenge/rechallenge for each
  4. Present reporter's causality assessment
  5. Include alternative explanations

Complete Workflow Example

From case data to regulatory submission:

# Step 1: Generate narrative
python scripts/main.py \
  --input case_data.json \
  --format cioms_i \
  --output narrative.txt

# Step 2: Validate completeness
python scripts/validate.py \
  --narrative narrative.txt \
  --check cioms_completeness \
  --output validation_report.txt

# Step 3: Generate E2B format for electronic submission
python scripts/main.py \
  --input case_data.json \
  --format ich_e2b \
  --output e2b_narrative.xml

# Step 4: Medical review markup
python scripts/review.py \
  --narrative narrative.txt \
  --output review_version.txt

Python API:

from scripts.narrative_generator import NarrativeGenerator
from scripts.validator import NarrativeValidator

# Initialize
generator = NarrativeGenerator()
validator = NarrativeValidator()

# Load case data
import json
with open("case_001.json", "r") as f:
    case = json.load(f)

# Generate narrative
narrative = generator.generate(
    case_data=case,
    format="cioms_i",
    include_meddra=True,
    language="en"
)

# Validate
validation = validator.check(
    narrative=narrative,
    criteria=["cioms_completeness", "temporal_logic", "meddra_accuracy"]
)

if validation.passed:
    with open("final_narrative.txt", "w") as f:
        f.write(narrative.text)
    print("✓ Narrative validated and saved")
else:
    print(f"⚠ Issues: {validation.issues}")

Quality Checklist

Pre-Generation:

  • [ ] Case ID unique and formatted per SOP
  • [ ] Patient age/sex complete
  • [ ] Suspect drug(s) clearly identified
  • [ ] Adverse event(s) coded with MedDRA PT
  • [ ] Dates consistent (no future dates)
  • [ ] Reporter information included

Narrative Content:

  • [ ] All CIOMS I sections present
  • [ ] Temporal sequence clear and logical
  • [ ] Dechallenge/rechallenge described (if applicable)
  • [ ] Lab values with reference ranges
  • [ ] Concomitant medications listed
  • [ ] Medical history relevant to event
  • [ ] Outcome clearly stated
  • [ ] Causality assessment justified

Post-Generation:

  • [ ] MedDRA terms accurate and current
  • [ ] No contradictory information
  • [ ] Language objective and factual
  • [ ] No speculation or opinion (except causality section)
  • [ ] Patient identifiers removed or de-identified
  • [ ] CRITICAL: Medical review completed
  • [ ] CRITICAL: Causality assessment by qualified physician

Common Pitfalls

Completeness Issues:

  • ❌ Missing dechallenge information → Cannot assess causality

- ✅ Always document effect after drug discontinuation

  • ❌ Vague temporal information → "Recently started" vs. specific dates

- ✅ Use exact dates when available

  • ❌ Incomplete concomitant medication list → Alternative causes missed

- ✅ Include all medications within relevant timeframe

Medical Accuracy Issues:

  • ❌ Incorrect MedDRA coding → Wrong medical concept

- ✅ Use current MedDRA version; verify with medical reviewer

  • ❌ Confusing correlation with causation → Temporal = causal

- ✅ Clearly state "temporally associated" vs. "causally related"

  • ❌ Omitting alternative diagnoses → Biased toward drug causation

- ✅ Include all differential diagnoses considered

Regulatory Issues:

  • ❌ Opinion in narrative body → "Clearly caused by drug"

- ✅ Reserve opinion for causality section; narrative should be factual

  • ❌ Patient identifiers → HIPAA/privacy violation

- ✅ De-identify per regulatory requirements

  • ❌ Abbreviations not defined → Assumes reader knowledge

- ✅ Spell out on first use in each narrative

References

Available in references/ directory:

  • cioms_i_guidelines.pdf - CIOMS I international reporting standards
  • ich_e2b_specifications.md - ICH E2B(R3) electronic format details
  • meddra_coding_guide.md - MedDRA terminology and coding principles
  • who_umc_causality.md - WHO causality assessment criteria
  • fda_medwatch_guide.md - FDA Form 3500A instructions
  • gvp_module_vi.md - EU Good Pharmacovigilance Practices
  • narrative_templates.md - Example narratives by case type

Scripts

Located in scripts/ directory:

  • main.py - CLI interface for narrative generation
  • narrative_generator.py - Core narrative composition engine
  • temporal_analyzer.py - Timeline reconstruction and analysis
  • causality_assessor.py - Causality evaluation support
  • meddra_integrator.py - Medical terminology and coding
  • validator.py - Completeness and quality checks
  • format_converter.py - Convert between CIOMS, E2B, MedWatch formats
  • batch_processor.py - Multi-case narrative generation

Limitations

  • Medical Review Required: Generates draft only; requires physician review before submission
  • Causality Assessment: Structures reporter's assessment; does not perform independent causality evaluation
  • MedDRA Version: Uses installed MedDRA version; may not have latest terms
  • Language: Optimized for English; other languages may need translation
  • Literature Integration: Does not automatically search literature for similar cases
  • Signal Detection: Individual case narratives only; aggregate analysis requires other tools
  • Legal Proceedings: Not suitable for litigation support or expert witness reports

⚠️ CRITICAL: This tool generates draft narratives for efficiency. All adverse event narratives require review by qualified drug safety physicians before regulatory submission. Causality assessment must be performed by healthcare professionals with access to complete medical records.

平台分布

OpenClaw

79.47%
按下载量换算1,875

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills