adverse-event-reporter

Adverse event monitoring and reporting skill for MDR/MEDWATCH compliance

509 stars

Best use case

adverse-event-reporter is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Adverse event monitoring and reporting skill for MDR/MEDWATCH compliance

Teams using adverse-event-reporter should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/adverse-event-reporter/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/domains/science/biomedical-engineering/skills/adverse-event-reporter/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/adverse-event-reporter/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How adverse-event-reporter Compares

Feature / Agentadverse-event-reporterStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Adverse event monitoring and reporting skill for MDR/MEDWATCH compliance

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Adverse Event Reporter Skill

## Purpose

The Adverse Event Reporter Skill supports adverse event monitoring and regulatory reporting for medical devices, ensuring compliance with FDA MDR requirements and EU vigilance obligations.

## Capabilities

- MDR reportability assessment
- FDA Form 3500A population assistance
- MEDWATCH submission guidance
- EU vigilance reporting templates
- Trend analysis and signal detection
- PSUR data compilation
- Field safety corrective action templates
- Complaint coding (MedDRA)
- Risk assessment updates
- Corrective action tracking
- Regulatory notification timelines

## Usage Guidelines

### When to Use
- Assessing adverse event reportability
- Preparing regulatory reports
- Conducting trend analyses
- Managing field actions

### Prerequisites
- Complaint information received
- Investigation completed
- Device information available
- Regulatory requirements identified

### Best Practices
- Assess reportability promptly
- Document decision rationale
- Track reporting timelines
- Integrate with risk management

## Process Integration

This skill integrates with the following processes:
- Post-Market Surveillance System Implementation
- Clinical Evaluation Report Development
- Medical Device Risk Management (ISO 14971)
- EU MDR Technical Documentation

## Dependencies

- FDA MAUDE database
- EUDAMED system
- MedDRA coding dictionary
- Complaint management systems
- Risk management databases

## Configuration

```yaml
adverse-event-reporter:
  reporting-systems:
    - FDA-MDR
    - EU-vigilance
    - Health-Canada
    - TGA
  report-types:
    - death
    - serious-injury
    - malfunction
    - field-safety-corrective-action
  timelines:
    - 30-day
    - 5-day
    - annual
```

## Output Artifacts

- Reportability assessments
- FDA Form 3500A drafts
- EU vigilance reports
- Trend analysis reports
- PSUR contributions
- FSCA notifications
- Risk management updates
- Corrective action plans

## Quality Criteria

- Reportability assessed per regulations
- Reports submitted within timelines
- MedDRA coding accurate
- Trend analysis comprehensive
- Risk management updated
- Documentation audit-ready

Related Skills

event-loop

509
from a5c-ai/babysitter

Expert skill for high-performance event-driven I/O programming and optimization

patient-safety-event-analysis

509
from a5c-ai/babysitter

Investigate patient safety events using RCA, FMEA, and other systematic analysis methods to identify contributing factors and develop corrective actions

pythia-event-generator

509
from a5c-ai/babysitter

Pythia event generation skill for proton-proton and lepton collisions at high energies

discrete-event-simulator

509
from a5c-ai/babysitter

Discrete event simulation skill for modeling and analyzing complex systems with stochastic processes.

speaking-events

509
from a5c-ai/babysitter

Speaking opportunity discovery and conference management

kaizen-event-facilitator

509
from a5c-ai/babysitter

Rapid improvement workshop planning and execution skill with team coordination, metrics tracking, and follow-up management

event-sourcing-migrator

509
from a5c-ai/babysitter

Migrate to event-sourcing architecture with event extraction, store setup, and CQRS implementation

process-builder

509
from a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Workflow & Productivity

babysitter

509
from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)

yolo

509
from a5c-ai/babysitter

Run Babysitter autonomously with minimal manual interruption.

user-install

509
from a5c-ai/babysitter

Install the user-level Babysitter Codex setup.

team-install

509
from a5c-ai/babysitter

Install the team-pinned Babysitter Codex workspace setup.