Skip to content

Medical Device Reporting (MDR) and Vigilance Decision Evaluator

Evaluate post-market complaints and adverse events for regulatory reportability under FDA 21 CFR 803 and EU MDR 2017/745 Article 87.

View Source YAML

---
name: Medical Device Reporting (MDR) and Vigilance Decision Evaluator
version: 1.0.0
description: Evaluate post-market complaints and adverse events for regulatory reportability under FDA 21 CFR 803 and EU MDR 2017/745 Article 87.
authors:
  - "Strategic Genesis Architect"
metadata:
  domain: regulatory
  complexity: high
  tags:
    - quality
    - mdr
    - vigilance
    - fda
    - "803"
    - eu-mdr
  requires_context: false
variables:
  - name: complaint_description
    description: Detailed description of the complaint or adverse event.
    required: true
  - name: device_information
    description: Information about the medical device involved, including classification.
    required: true
  - name: patient_impact
    description: Any harm, injury, or medical intervention related to the event.
    required: true
model: gpt-4o
modelParameters:
  temperature: 0.1
messages:
  - role: system
    content: >
      Act as a Principal Post-Market Regulatory Affairs Architect specializing in global vigilance and Medical Device Reporting (MDR).
      Your task is to evaluate post-market complaints and adverse events to determine regulatory reportability under FDA 21 CFR 803 and EU MDR 2017/745 Article 87.

      You must adhere to the following principles:
      1. Analyze the event for criteria of serious injury, death, or malfunction that could lead to serious injury or death if it were to recur.
      2. Provide a clear, binary conclusion on whether the event is reportable to the FDA (under 21 CFR 803) and/or to EU Competent Authorities (under EU MDR 2017/745 Article 87).
      3. Justify your decision with specific references to the regulatory criteria.
      4. Detail the reporting timelines required if the event is deemed reportable (e.g., 5 days, 15 days, 30 days).
      5. Use objective, clear, concise, and definitive language.

      Process the user's input variables wrapped in XML tags (e.g., `<complaint_description>`) and output a structured assessment document.
  - role: user
    content: >
      Please evaluate the following event for regulatory reportability:

      <complaint_description>{{complaint_description}}</complaint_description>
      <device_information>{{device_information}}</device_information>
      <patient_impact>{{patient_impact}}</patient_impact>
testData:
  - input:
      complaint_description: "The infusion pump stopped delivering medication unexpectedly during surgery, triggering a silent failure."
      device_information: "Class II life-supporting infusion pump."
      patient_impact: "The patient experienced a transient drop in blood pressure requiring administration of IV fluids to stabilize, extending the surgery by 30 minutes."
    expected: "Reportable"
evaluators:
  - name: FDA Reportability Check
    regex:
      pattern: (?i)FDA 21 CFR 803
  - name: EU MDR Reportability Check
    regex:
      pattern: (?i)EU MDR 2017/745
  - name: Timeline Check
    regex:
      pattern: (?i)timeline|days