fda-med-device
De la autor
Reconstructed reference notes on US FDA medical-device software regulation, built from seven public-domain FDA sources (the QMSR final rule 89 FR 7496, FDA device software guidance documents, and the eSTAR program page; pinned 2026-10-12). Use for regulatory pathways and premarket submissions (510(k), De Novo, PMA, eSTAR), premarket software documentation levels (Basic or Enhanced), software validation and Computer Software Assurance, the Quality Management System Regulation (QMSR, 21 CFR 820), medical-device cybersecurity (secure product development, SBOMs, FD&C Act section 524B, labelling), clinical decision support boundaries, off-the-shelf software, MDDS and other software-function scope questions, and the 510(k) software-change trigger. SCOPE LIMITS: US FDA device regulation only; no EU MDR or UKCA content (see `med-device-eu`); no ISO 13485, ISO 14971, or IEC 62304 text, which are named and summarized only as FDA obligations; no drug, biologic, or combination-product rules; reflects the pinned source da
Instalare
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a claude-code
Se instalează în .claude/skills/fda-med-device/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Fără descărcare: licența acestui skill (Personalizată sau neclară) nu ne permite să-i redistribuim fișierele. Comenzile de instalare le iau direct de pe GitHub.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
- Conține text ascuns (caractere invizibile, comentarii lungi sau blocuri codificate)Mediu
De ce 70
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- med-device-eujgsystemsconsulting/jgs-se-knowledge-packsReconstructed reference notes on EU and UK medical-device software, built from six sources captured 2026-10-13: MDCG 2019-11 rev.1 (June 2025), MDCG 2020-6 (April 2020), MDCG 2020-13 (July 2020), MDCG 2020-7 (April 2020), MDCG 2020-8 (April 2020), and the MHRA software-applications guidance (2023-07-01) with its stand-alone software PDF. Use for SaMD qualification and classification, legacy-device clinical evidence, the clinical evaluation assessment report, the PMCF plan, and the PMCF evaluation report, under EU MDCG guidance or UK MHRA guidance. SCOPE LIMITS: EU MDR and UK MHRA device software only; no IEC 62304, ISO 13485, or ISO 14971 text; no MDR or IVDR regulation body text; MDCG guidance is not legally binding; MHRA guidance is UK-specific; synthesized notes, not legal advice. LICENCE: Per-document: European Commission reuse policy (Decision 2011/833/EU, CC BY 4.0, attribution and indication of changes) for the MDCG documents; Open Government Licence v3.0 for the MHRA guidance; reconstructed notes withDocumente★ 98
- medical-device-software-complianceawslabs/hcls-agent-skillsReason about SaMD (Software as a Medical Device) regulatory compliance for FDA, EU MDR, and global submissions. Use when the user asks about IEC 62304 safety classification, ISO 14971 risk management, 21 CFR 820/QMSR quality system requirements, Design History File structure, 510(k)/De Novo/PMA pathway selection, SOUP/OTS assessment, verification and validation planning, cybersecurity for medical devices, PCCP for AI/ML devices, design reviews, traceability matrices, or post-market surveillance. Triggers include "SaMD", "medical device software", "IEC 62304", "ISO 14971", "ISO 13485", "21 CFR 820", "QMSR", "510(k)", "De Novo", "PMA", "design history file", "DHF", "software safety classification", "SOUP list", "risk management", "hazard analysis", "design review", "V&V protocol", "FDA submission", "EU MDR", "clinical evaluation", "PCCP", "predetermined change control", "GMLP", "cybersecurity premarket", "Part 11", "design controls", "design inputs", "design outputs", "traceability matrix", "post-market surveilȘtiință★ 71
- fda-consultant-specialistborghei/Claude-SkillsFDA regulatory consultant for medical device companies, covering 510(k)/PMA/De Novo pathways, QSR (21 CFR 820), HIPAA, and device cybersecurity. Use for FDA submissions, predicate and substantial-equivalence analysis, and premarket strategy.Planificare★ 1K
- iso-standards-readinessK-Dense-AI/scientific-agent-skillsPrepares and structurally reviews readiness evidence for ISO management-system and laboratory-competence standards - ISO 13485 medical device QMS, ISO 14971 device risk management, ISO/IEC 17025 testing and calibration laboratories, and ISO 15189 medical laboratories. Use when organizing declared scope, controlled documents, risk-management files, scope of accreditation, traceability, CAPA, external-provider controls, or bounded local evidence manifests, and when separating ISO certification from laboratory accreditation, FDA QMSR inspection, CLIA certification, MDSAP, and EU MDR/IVDR evidence boundaries. Not for legal applicability, compliance, certification, or accreditation decisions; contains no clause text.Testare★ 56.1K
- easa-rulesjgsystemsconsulting/jgs-se-knowledge-packsReconstructed reference notes on EASA acceptable means of compliance for airborne software and airborne electronic hardware, built from AMC 20-115D (ED Decision 2017/020/R, AMC-20 Amendment 14, consolidated in Amendment 23) and AMC 20-152A (ED Decision 2020/010/R, AMC-20 Amendment 19, consolidated in Amendment 23), read from the Easy Access Rules AMC-20 compilation (Amendment 23, June 2023) and pinned 2026-09-26. Use for EASA software means of compliance, EASA AEH means of compliance, AltMoC, ETSO software, and the joint software and hardware certification workflow. SCOPE LIMITS: the two AMC sections only; no FAA content (use faa-8110-49); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, or supplement clause text (use avionics-signpost to name them); no Part-21 body; no bulk AMC-20; AMC 20-193 and AMC 20-189 are name-only; reflects Amendment 23 as consolidated in the June 2023 EAR, not a later AMC-20 amendment; synthesized reference notes, not legal advice and not the official AMC. LICENCE: per-document (EJuridic★ 98
- nrc-nuclearjgsystemsconsulting/jgs-se-knowledge-packsReconstructed reference notes on US NRC software assurance guidance for digital computer software in nuclear power plant safety systems, built from seven public-domain sources (Regulatory Guide 1.168 Revision 2, July 2013; Regulatory Guides 1.169, 1.170, 1.171, 1.172, and 1.173 Revision 1, July 2013; NUREG-0800 Branch Technical Position 7-14 Revision 6, August 2016; pinned 2026-10-12). Use for software life cycle process questions, software requirements specifications, software configuration management plans, verification and validation with reviews and audits, test documentation and unit testing, and what NRC staff examine in a BTP 7-14 software review of plans, implementation, and design outputs. SCOPE LIMITS: NRC Regulatory Guides and the BTP 7-14 staff review position only; the endorsed IEEE standards (IEEE Std 603-1991, 7-4.3.2-2003, 828-2005, 829-2008, 830-1998, 1008-1987, 1012-2004, 1028-2008, 1074-2006), IEC 60880, IEC 61513, IEC 62138, and IAEA guides are cited by designation and edition only, with nTestare★ 98
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te