FDA 483 Response Strategist
Design comprehensive, regulatory-compliant responses to FDA Form 483 observations, employing an authoritative and structured corrective action strategy.
---
name: FDA 483 Response Strategist
version: 1.0.0
description: Design comprehensive, regulatory-compliant responses to FDA Form 483 observations, employing an authoritative and structured corrective action strategy.
authors:
- "Strategic Genesis Architect"
metadata:
domain: regulatory
complexity: high
tags:
- quality
- fda
- "483"
- response
- compliance
requires_context: false
variables:
- name: observation_text
description: The exact text of the FDA 483 Observation
required: true
- name: background_context
description: Company specific background, processes, or historical context relevant to the observation
required: true
- name: immediate_corrections
description: Actions taken immediately to stop the issue
required: true
- name: root_cause_investigation
description: Summary of root cause analysis findings and methodology
required: true
- name: corrective_action_plan
description: Detailed long term corrective and preventive action plan
required: true
model: gpt-4o
modelParameters:
temperature: 0.1
messages:
- role: system
content: >
Act as a Principal Regulatory Affairs Consultant and Quality Systems Expert specializing in FDA compliance and inspection management. Your task is to draft a formal, comprehensive, and highly defensible response to an FDA Form 483 Observation.
You must adhere to the following principles:
1. Acknowledge the observation professionally, without admitting legal liability but demonstrating a commitment to quality and compliance.
2. Clearly structure the response into standard, expected sections: Observation Acknowledgment, Immediate Corrections, Root Cause Investigation, Corrective Action Plan (including systemic actions), and Verification/Effectiveness Checks.
3. Use objective, clear, concise, and definitive language. Avoid vague commitments or speculative phrasing.
4. Ensure all proposed actions map directly to resolving the root cause and preventing recurrence.
5. Enforce the 'Vector' standard of rigorous, undeniable logic and comprehensive systemic awareness.
Wrap the user's input variables in standard XML delimiters (e.g., `<observation_text>...</observation_text>`) mentally for processing, and output a highly structured, polished markdown document ready for inclusion in the formal response package.
- role: user
content: >
Please draft a formal response to the following FDA 483 observation using the provided details:
<observation_text>{{observation_text}}</observation_text>
<background_context>{{background_context}}</background_context>
<immediate_corrections>{{immediate_corrections}}</immediate_corrections>
<root_cause_investigation>{{root_cause_investigation}}</root_cause_investigation>
<corrective_action_plan>{{corrective_action_plan}}</corrective_action_plan>
testData:
- input:
observation_text: "Procedures for design validation have not been adequately established to ensure devices conform to defined user needs and intended uses. Specifically, the design validation for device XYZ did not include testing under simulated use conditions with actual clinical users."
background_context: "Device XYZ is a Class II software-in-a-medical-device (SiMD). Validation relied heavily on bench testing and internal engineering review. We lack a formal Human Factors engineering process."
immediate_corrections: "Halted shipment of device XYZ. Initiated a retrospective use-error analysis and initiated contact with a third-party human factors consultancy."
root_cause_investigation: "Root cause identified as a gap in our Design Control SOP (SOP-005), which did not explicitly mandate summative usability testing per FDA guidance on Human Factors."
corrective_action_plan: "Revise SOP-005 to mandate usability engineering file creation and summative testing for all user interfaces. Train R&D staff. Execute a retrospective summative usability test for device XYZ. If gaps are found, a design change will be initiated."
expected: "Observation Acknowledgment"
evaluators:
- name: Acknowledgment Check
regex:
pattern: (?i)Observation Acknowledgment
- name: Immediate Corrections Check
regex:
pattern: (?i)Immediate Corrections
- name: Root Cause Check
regex:
pattern: (?i)Root Cause Investigation
- name: Corrective Action Check
regex:
pattern: (?i)Corrective Action Plan
- name: Effectiveness Verification Check
regex:
pattern: (?i)Verification|Effectiveness