medical-device-techfile-sted

Maps IMDRF STED six-chapter technical documentation to MDR, FDA 510(k), NMPA, and Japan requirements.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/HalseyYang/Skills-HY --skill medical-device-techfile-sted-halseyyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medical-device-techfile-sted
Source: https://github.com/HalseyYang/Skills-HY/tree/main/medical-device-techfile-sted
Command: npx skills add https://github.com/HalseyYang/Skills-HY --skill medical-device-techfile-sted-halseyyang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing medical device technical documentation separately for each market (EU MDR, US FDA, China NMPA, Japan) causes duplicated effort and inconsistent evidence chains. This Skill provides a unified IMDRF STED six-chapter skeleton with cross-market mapping tables so one core document can be reused across jurisdictions. ## Core Features & Use Cases - STED Six-Chapter Skeleton: Structures technical documentation around device description, labeling, design and manufacturing, safety principles, risk analysis, and verification/validation. - Cross-Market Mapping Tables: Aligns STED chapters with EU MDR Annex II/III, US 510(k) Summary/eSTAR (21 CFR 807.92), China 121/122 announcements (eRPS modules), and Japan technical documentation. - Writing Guidance & Official Portals: Per-chapter drafting points plus direct links to official sources (FDA, EUR-Lex, CMDE, PMDA, IMDRF), all flagged for version verification. - Use Case: A regulatory affairs specialist preparing a device for China, EU, and US markets asks how to avoid writing three separate dossiers, and receives a single STED-based skeleton with market-specific supplements (GSPR checklist for EU, SE argumentation and Summary for US, eRPS modules for China). ## Quick Start Ask how to structure one reusable technical file for NMPA, MDR, and FDA submissions and specify your target markets and device class.

Frequently Asked Questions about medical-device-techfile-sted

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write one technical file for EU, US, and China submissions?

Write a single dossier using the IMDRF STED six chapters as the skeleton, then map it per market: add GSPR conformity for EU MDR Annex II, SE argumentation and a 510(k) Summary for the US, and eRPS modules per China announcements 121/122. The evidence chain is built once and referenced everywhere.

What is the IMDRF STED format for medical device documentation?

STED (Summary Technical Documentation) is an internationally harmonized format with six chapters: device description and specifications, labeling, design and manufacturing, essential safety principles, risk analysis, and verification and validation. It is recognized across multiple jurisdictions as a drafting base.

What must a 510(k) Summary contain under 21 CFR 807.92?

A 510(k) Summary must include device name, classification and intended use, predicate device comparison, technological characteristics, performance data summary, standards conformity, and labeling highlights. Submission is made electronically via the FDA eSTAR template, whose current version should be checked on the FDA website.

Does this skill generate submission-ready technical documentation?

No. It provides the structural skeleton, cross-market mapping tables, and per-chapter drafting points only. You must fill in actual content and verify current official requirements before submission, and it does not replace notified body or review center decisions.

When should I not use this STED documentation skill?

Avoid it for clinical evaluation report work, which belongs to a dedicated clinical-evaluation skill, and for case-specific rulings from review centers or notified bodies. It also does not verify regulation versions online, so all cited versions and links must be rechecked against official sources.