Skip to main content 홈 크리에이터 thiagofernandes1987-create apex fda-consultant-specialist
fda-consultant-specialist Manage — FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/thiagofernandes1987-create/APEX --skill fda-consultant-specialist명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills Token-aware reasoning workflow with real tools: picks an operating mode to control cost, runs a structured pipeline (decompose → validate → verify → snapshot), and gives Claude Program-of-Thought, RK4/Euler, a code gate, and a safe skill router. Use when: multi-step or high-stakes tasks, real math, precise computation, audits, or the user mentions APEX, PoT, pipeline, or scientific mode.
agent-framework-azure-ai-py **v00.33.0**: Ingested from antigravity-awesome-skills community repo
run multiple local CLI agents in parallel (separate tmux sessions)
thiagofernandes1987-create
thiagofernandes1987-create/APEX
GitHub 저장소 열기 name fda-consultant-specialist description Manage — FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use executor HYBRID skill_id business.ra-qm-team.fda-consultant-specialist status ADOPTED security {"level":"high","pii":false,"approval_required":true} anchors ["business","compliance","security","design"] tier 2 input_schema [{"name":"code_or_task","type":"string","description":"Code snippet, script, or task description to process","required":true}] output_schema [{"name":"plan","type":"string","description":"Strategic plan or design document"},{"name":"next_steps","type":"array","description":"List of recommended next steps"}]
FDA Consultant Specialist
FDA regulatory consulting for medical device manufacturers covering submission pathways, Quality System Regulation (QSR), HIPAA compliance, and device cybersecurity requirements.
Table of Contents
FDA Pathway Selection
Determine the appropriate FDA regulatory pathway based on device classification and predicate availability.
Decision Framework
Predicate device exists?
├── YES → Substantially equivalent?
│ ├── YES → 510(k) Pathway
│ │ ├── No design changes → Abbreviated 510(k)
│ │ ├── Manufacturing only → Special 510(k)
│ │ └── Design/performance → Traditional 510(k)
│ └── NO → PMA or De Novo
└── NO → Novel device?
├── Low-to-moderate risk → De Novo
└── High risk (Class III) → PMA
Pathway Comparison
Pathway When to Use Timeline Cost 510(k) Traditional Predicate exists, design changes 90 days $21,760 510(k) Special Manufacturing changes only 30 days $21,760 510(k) Abbreviated Guidance/standard conformance 30 days $21,760 De Novo Novel, low-moderate risk 150 days $134,676 PMA Class III, no predicate 180+ days $425,000+
Pre-Submission Strategy
Identify product code and classification
Search 510(k) database for predicates
Assess substantial equivalence feasibility
Prepare Q-Sub questions for FDA
Schedule Pre-Sub meeting if needed
Reference: See fda_submission_guide.md for pathway decision matrices and submission requirements.
510(k) Submission Process
Workflow Phase 1: Planning
├── Step 1: Identify predicate device(s)
├── Step 2: Compare intended use and technology
├── Step 3: Determine testing requirements
└── Checkpoint: SE argument feasible?
Phase 2: Preparation
├── Step 4: Complete performance testing
├── Step 5: Prepare device description
├── Step 6: Document SE comparison
├── Step 7: Finalize labeling
└── Checkpoint: All required sections complete?
Phase 3: Submission
├── Step 8: Assemble submission package
├── Step 9: Submit via eSTAR
├── Step 10: Track acknowledgment
└── Checkpoint: Submission accepted?
Phase 4: Review
├── Step 11: Monitor review status
├── Step 12: Respond to AI requests
├── Step 13: Receive decision
└── Verification: SE letter received?
Required Sections (21 CFR 807.87) Section Content Cover Letter Submission type, device ID, contact info Form 3514 CDRH premarket review cover sheet Device Description Physical description, principles of operation Indications for Use Form 3881, patient population, use environment SE Comparison Side-by-side comparison with predicate Performance Testing Bench, biocompatibility, electrical safety Software Documentation Level of concern, hazard analysis (IEC 62304) Labeling IFU, package labels, warnings 510(k) Summary Public summary of submission
Common RTA Issues Issue Prevention Missing user fee Verify payment before submission Incomplete Form 3514 Review all fields, ensure signature No predicate identified Confirm K-number in FDA database Inadequate SE comparison Address all technological characteristics
QSR Compliance Quality System Regulation (21 CFR Part 820) requirements for medical device manufacturers.
Key Subsystems Section Title Focus 820.20 Management Responsibility Quality policy, org structure, management review 820.30 Design Controls Input, output, review, verification, validation 820.40 Document Controls Approval, distribution, change control 820.50 Purchasing Controls Supplier qualification, purchasing data 820.70 Production Controls Process validation, environmental controls 820.100 CAPA Root cause analysis, corrective actions 820.181 Device Master Record Specifications, procedures, acceptance criteria
Design Controls Workflow (820.30) Step 1: Design Input
└── Capture user needs, intended use, regulatory requirements
Verification: Inputs reviewed and approved?
Step 2: Design Output
└── Create specifications, drawings, software architecture
Verification: Outputs traceable to inputs?
Step 3: Design Review
└── Conduct reviews at each phase milestone
Verification: Review records with signatures?
Step 4: Design Verification
└── Perform testing against specifications
Verification: All tests pass acceptance criteria?
Step 5: Design Validation
└── Confirm device meets user needs in actual use conditions
Verification: Validation report approved?
Step 6: Design Transfer
└── Release to production with DMR complete
Verification: Transfer checklist complete?
CAPA Process (820.100)
Identify : Document nonconformity or potential problem
Investigate : Perform root cause analysis (5 Whys, Fishbone)
Plan : Define corrective/preventive actions
Implement : Execute actions, update documentation
Verify : Confirm implementation complete
Effectiveness : Monitor for recurrence (30-90 days)
Close : Management approval and closure
HIPAA for Medical Devices HIPAA requirements for devices that create, store, transmit, or access Protected Health Information (PHI).
Applicability Device Type HIPAA Applies Standalone diagnostic (no data transmission) No Connected device transmitting patient data Yes Device with EHR integration Yes SaMD storing patient information Yes Wellness app (no diagnosis) Only if stores PHI
Required Safeguards Administrative (§164.308)
├── Security officer designation
├── Risk analysis and management
├── Workforce training
├── Incident response procedures
└── Business associate agreements
Physical (§164.310)
├── Facility access controls
├── Workstation security
└── Device disposal procedures
Technical (§164.312)
├── Access control (unique IDs, auto-logoff)
├── Audit controls (logging)
├── Integrity controls (checksums, hashes)
├── Authentication (MFA recommended)
└── Transmission security (TLS 1.2+)
Risk Assessment Steps
Inventory all systems handling ePHI
Document data flows (collection, storage, transmission)
Identify threats and vulnerabilities
Assess likelihood and impact
Determine risk levels
Implement controls
Document residual risk
Device Cybersecurity FDA cybersecurity requirements for connected medical devices.
Premarket Requirements Element Description Threat Model STRIDE analysis, attack trees, trust boundaries Security Controls Authentication, encryption, access control SBOM Software Bill of Materials (CycloneDX or SPDX) Security Testing Penetration testing, vulnerability scanning Vulnerability Plan Disclosure process, patch management
Device Tier Classification
Connects to network/internet
Cybersecurity incident could cause patient harm
All other connected devices
Postmarket Obligations
Monitor NVD and ICS-CERT for vulnerabilities
Assess applicability to device components
Develop and test patches
Communicate with customers
Report to FDA per guidance
Coordinated Vulnerability Disclosure Researcher Report
↓
Acknowledgment (48 hours)
↓
Initial Assessment (5 days)
↓
Fix Development
↓
Coordinated Public Disclosure
Resources
scripts/ Script Purpose fda_submission_tracker.pyTrack 510(k)/PMA/De Novo submission milestones and timelines qsr_compliance_checker.pyAssess 21 CFR 820 compliance against project documentation hipaa_risk_assessment.pyEvaluate HIPAA safeguards in medical device software
references/ File Content fda_submission_guide.md510(k), De Novo, PMA submission requirements and checklists qsr_compliance_requirements.md21 CFR 820 implementation guide with templates hipaa_compliance_framework.mdHIPAA Security Rule safeguards and BAA requirements device_cybersecurity_guidance.mdFDA cybersecurity requirements, SBOM, threat modeling fda_capa_requirements.mdCAPA process, root cause analysis, effectiveness verification
Usage Examples
python scripts/fda_submission_tracker.py /path/to/project --type 510k
python scripts/qsr_compliance_checker.py /path/to/project --section 820.30
python scripts/hipaa_risk_assessment.py /path/to/project --category technical
Why This Skill Exists Manage — FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use
When to Use Use this skill when the task requires fda consultant specialist capabilities.
What If Fails If this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.