@neobiotechlabs/neobiotech-dev-agent-codex 0.1.39

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (87) hide show
  1. package/.codex-plugin/plugin.json +36 -0
  2. package/.mcp.json +20 -0
  3. package/data/cyber_sec.png +0 -0
  4. package/data/hazard_panel.png +0 -0
  5. package/data/review-criteria.md +185 -0
  6. package/data/risk_score.png +0 -0
  7. package/dist/build/plantuml-1.2026.1.jar +0 -0
  8. package/dist/data/Courier-Bold.afm +342 -0
  9. package/dist/data/Courier-BoldOblique.afm +342 -0
  10. package/dist/data/Courier-Oblique.afm +342 -0
  11. package/dist/data/Courier.afm +342 -0
  12. package/dist/data/Helvetica-Bold.afm +2827 -0
  13. package/dist/data/Helvetica-BoldOblique.afm +2827 -0
  14. package/dist/data/Helvetica-Oblique.afm +3051 -0
  15. package/dist/data/Helvetica.afm +3051 -0
  16. package/dist/data/Symbol.afm +213 -0
  17. package/dist/data/Times-Bold.afm +2588 -0
  18. package/dist/data/Times-BoldItalic.afm +2384 -0
  19. package/dist/data/Times-Italic.afm +2667 -0
  20. package/dist/data/Times-Roman.afm +2419 -0
  21. package/dist/data/ZapfDingbats.afm +225 -0
  22. package/dist/data/sRGB_IEC61966_2_1.icc +0 -0
  23. package/dist/doctor.js +15106 -0
  24. package/dist/doctor.js.map +1 -0
  25. package/dist/fonts/LICENSE.txt +94 -0
  26. package/dist/fonts/Pretendard-Bold.ttf +0 -0
  27. package/dist/fonts/Pretendard-Regular.ttf +0 -0
  28. package/dist/index.js +185999 -0
  29. package/dist/index.js.map +1 -0
  30. package/dist/setup-codex.js +164 -0
  31. package/dist/setup-codex.js.map +1 -0
  32. package/package.json +34 -0
  33. package/skills/doc-render/SKILL.md +84 -0
  34. package/skills/role-document-content-reviewer/SKILL.md +68 -0
  35. package/skills/role-mdr-cybersecurity-reviewer/SKILL.md +47 -0
  36. package/skills/role-mdr-regulatory-architect/SKILL.md +48 -0
  37. package/skills/role-requirement-coverage-tracker/SKILL.md +108 -0
  38. package/skills/role-sw-architect/SKILL.md +61 -0
  39. package/vendor/dev-docs-templates/templates/dev_docs/plan_template.md +104 -0
  40. package/vendor/dev-docs-templates/templates/dev_docs/prd_template.md +110 -0
  41. package/vendor/dev-docs-templates/templates/dev_docs/spec_template.md +81 -0
  42. package/vendor/dev-docs-templates/templates/dev_docs/tasks_template.md +122 -0
  43. package/vendor/dev-docs-templates/templates/mdr_docs/CA/checklist-clinical-evaluation.md +81 -0
  44. package/vendor/dev-docs-templates/templates/mdr_docs/CA/checklist-gspr-mdr.md +403 -0
  45. package/vendor/dev-docs-templates/templates/mdr_docs/CA/clinical-evaluation-report.md +492 -0
  46. package/vendor/dev-docs-templates/templates/mdr_docs/CA/instructions-for-use.md +132 -0
  47. package/vendor/dev-docs-templates/templates/mdr_docs/CA/literature-evaluation-table.md +15 -0
  48. package/vendor/dev-docs-templates/templates/mdr_docs/CA/mdr-declaration-of-conformity.md +75 -0
  49. package/vendor/dev-docs-templates/templates/mdr_docs/CA/post-market-clinical-follow-up-plan.md +162 -0
  50. package/vendor/dev-docs-templates/templates/mdr_docs/CA/post-market-surveillance-plan.md +175 -0
  51. package/vendor/dev-docs-templates/templates/mdr_docs/CA/risk-management-cybersecurity-checklist.md +67 -0
  52. package/vendor/dev-docs-templates/templates/mdr_docs/CA/risk-management-report.md +111 -0
  53. package/vendor/dev-docs-templates/templates/mdr_docs/CA/usability-evaluation-report.md +70 -0
  54. package/vendor/dev-docs-templates/templates/mdr_docs/EA/clinical-evaluation-plan.md +154 -0
  55. package/vendor/dev-docs-templates/templates/mdr_docs/EA/list-of-hazard-related-use-scenarios.md +34 -0
  56. package/vendor/dev-docs-templates/templates/mdr_docs/EA/risk-table-fmea.md +155 -0
  57. package/vendor/dev-docs-templates/templates/mdr_docs/EA/software-architecture-description.md +307 -0
  58. package/vendor/dev-docs-templates/templates/mdr_docs/EA/software-detailed-design.md +321 -0
  59. package/vendor/dev-docs-templates/templates/mdr_docs/EA/software-requirements-list.md +156 -0
  60. package/vendor/dev-docs-templates/templates/mdr_docs/EA/soup-list.md +82 -0
  61. package/vendor/dev-docs-templates/templates/mdr_docs/EA/usability-evaluation-plan.md +103 -0
  62. package/vendor/dev-docs-templates/templates/mdr_docs/ER/global/bug-fixes-documentation-list.md +35 -0
  63. package/vendor/dev-docs-templates/templates/mdr_docs/ER/global/change-evaluation-list.md +100 -0
  64. package/vendor/dev-docs-templates/templates/mdr_docs/ER/global/list-of-known-anomalies.md +29 -0
  65. package/vendor/dev-docs-templates/templates/mdr_docs/ER/sprint/algorithm-validation-report.md +170 -0
  66. package/vendor/dev-docs-templates/templates/mdr_docs/ER/sprint/checklist-software-release.md +52 -0
  67. package/vendor/dev-docs-templates/templates/mdr_docs/ER/sprint/checklist-software-requirements-review.md +50 -0
  68. package/vendor/dev-docs-templates/templates/mdr_docs/ER/sprint/software-architecture-checklist.md +41 -0
  69. package/vendor/dev-docs-templates/templates/mdr_docs/ER/sprint/software-system-test-plan.md +155 -0
  70. package/vendor/dev-docs-templates/templates/mdr_docs/ER/sprint/usability-evaluation-protocol.md +63 -0
  71. package/vendor/dev-docs-templates/templates/mdr_docs/PA/configuration-management-plan.md +112 -0
  72. package/vendor/dev-docs-templates/templates/mdr_docs/PA/intended-use.md +116 -0
  73. package/vendor/dev-docs-templates/templates/mdr_docs/PA/mdr-classification-document.md +114 -0
  74. package/vendor/dev-docs-templates/templates/mdr_docs/PA/risk-management-plan.md +198 -0
  75. package/vendor/dev-docs-templates/templates/mdr_docs/PA/security-management-plan.md +101 -0
  76. package/vendor/dev-docs-templates/templates/mdr_docs/PA/software-development-maintenance-plan.md +213 -0
  77. package/vendor/dev-docs-templates/templates/mdr_docs/PA/system-requirements-spec.md +182 -0
  78. package/vendor/dev-docs-templates/templates/mdr_docs/global/information_security/information-security-controls.md +966 -0
  79. package/vendor/dev-docs-templates/templates/mdr_docs/global/information_security/information-security-policy-and-scope.md +99 -0
  80. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/quality-manual-policy-objectives.md +187 -0
  81. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/sop-capa.md +112 -0
  82. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/sop-change-management.md +128 -0
  83. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/sop-clinical-evaluation.md +102 -0
  84. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/sop-feedback-management.md +140 -0
  85. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/sop-integrated-software-development.md +361 -0
  86. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/sop-post-market-surveillance.md +159 -0
  87. package/vendor/dev-docs-templates/templates/mdr_docs/global/qms/sop-software-problem-resolution.md +99 -0
@@ -0,0 +1,116 @@
1
+ # Intended Use
2
+
3
+ <!-- AI AGENT 작성 지침
4
+ 이 문서는 MDR Annex II 1.1, ISO 14971 Cl.5.2, IEC 62366-1 Cl.5.1 기반 사용 목적 정의서입니다.
5
+ PA 단계의 첫 번째 핵심 문서로, 모든 이후 문서의 근거가 됩니다.
6
+
7
+ 작성 지침:
8
+ 1. "Intended Use": 의료 기기의 核心 기능을 명확하고 간결하게 기술하세요
9
+ - 무엇을 하는가? (진단/치료/모니터링)
10
+ - 어떤 방식으로? (AI 분석, 데이터 수집 등)
11
+ - 어떤 결과를 제공하는가? (점수, 권고사항, 시각화 등)
12
+ 예시: "This software is intended to assist clinicians in detecting {CONDITION} by analyzing {INPUT_DATA} and providing a risk score."
13
+
14
+ 2. "Intended Medical Indication": 대상 질환/상태를 구체적으로 기술하고
15
+ "제외 기준(Exclusion Criteria)"을 반드시 포함하세요
16
+
17
+ 3. "Patient Population": 나이, 체중, 동반 질환 등 구체적 특성을 기술하세요
18
+
19
+ 4. "User Profile": 의료 종사자인지 일반 사용자인지 명확히 구분하세요
20
+ - 필요한 교육/자격 요건
21
+ - 기술 숙련도 수준
22
+
23
+ 5. "Use Environment": 병원 환경인지 재택 환경인지 구분하고
24
+ 소음, 조명, 시간 압박 등 환경적 특성을 기술하세요
25
+
26
+ 6. "Operating Principle": 입력 -> 처리 -> 출력 흐름을 명확히 기술하세요
27
+ AI/ML 모델을 사용하는 경우 반드시 "보조 진단 도구"임을 명시하세요
28
+
29
+ 완성 체크리스트:
30
+ [ ] 제품명 및 버전 기재
31
+ [ ] Medical Indication에 제외 기준(Contraindications) 포함
32
+ [ ] 의도된 사용자와 환자 집단 구분 명확
33
+ [ ] MDR 등급 결정을 위한 충분한 정보 제공
34
+ [ ] IFU(instructions-for-use.md)와 내용 일치 확인
35
+ -->
36
+
37
+
38
+ ## Mapping of Requirements to Document Sections
39
+
40
+ | MDR Class | MDR Section | Document Section |
41
+ | --------- | ----------------------------- | ---------------- |
42
+ | (All) | Annex II, 1.1 a) - d), h), i) | (All) |
43
+
44
+ | ISO 14971:2019 Section | Document Section |
45
+ | ---------------------- | ---------------- |
46
+ | 5.2 | (All) |
47
+
48
+ | IEC 62366-1:2015 Section | Document Section |
49
+ | ------------------------ | ---------------- |
50
+ | 5.1 | (All) |
51
+
52
+ ## Product
53
+
54
+ * Name: *\<product name\>*
55
+ * Version: *\<product version\>*
56
+ * Basic UDI-DI: *\<insert UDI-DI, if/when available\>*
57
+
58
+ ## Intended Use
59
+
60
+ > Describe the core medical functionality of your device and how it treats, diagnoses or alleviates a disease.
61
+ > Keep it high-level so that this description is true for as long as possible even when the device is updated.
62
+
63
+ ## Intended Medical Indication
64
+
65
+ > Describe the condition(s) and/or disease(s) to be screened, monitored, treated, diagnosed, or prevented by
66
+ > your software. Importantly, also list exclusion criteria: Maybe patients with a certain diagnosis should not
67
+ > be using your device.
68
+
69
+ ## Contraindications
70
+
71
+ > List anything that you want to explicitly exclude from your intended use.
72
+
73
+ ## Patient Population
74
+
75
+ > Describe the patient population your software is intended to be used on. Note that this may overlap with the
76
+ > user profile (section below), but not necessarily. Your software could be used by physicians to diagnose
77
+ > diseases in patients, so in that case, they don't overlap. Some ideas for characteristics to describe: Age
78
+ > group, weight range, health, condition(s).
79
+
80
+ ## User Profile
81
+
82
+ > Describe the typical user of the software. Some ideas could be: Qualifications, prior training (for your
83
+ > software), technical proficiency, time spent using the software.
84
+
85
+ ## Use Environment Including Software/Hardware
86
+
87
+ > Describe the typical use environment. What sort of devices is this running on? Does the software only run on
88
+ > one device or multiple devices? Is it loud and chaotic like in an emergency ward? How's the lighting?
89
+ >
90
+ > Also, add other software or hardware which is required by your device. Most commonly, apps require users to
91
+ > have a smartphone with a compatible operating system (iOS / Android).
92
+
93
+ ## Operating Principle
94
+
95
+ > It's kind of a stretch to describe the "operating principle" of software. I guess this makes more sense for
96
+ > hardware devices. In any case, I'd just generally state what sort of input goes in and what output comes
97
+ > out, e.g. you could be processing images and returning diagnoses.
98
+
99
+ The device is stand-alone software. It receives input from the user and outputs information.
100
+
101
+ ## Part of the Body / Type of Tissue Interacted With
102
+
103
+ The device is stand-alone software. It receives input from the user and outputs information. It doesn't come
104
+ in contact with tissue or bodily fluids.
105
+
106
+ ## Variants / Accessories
107
+
108
+ > Describe variants and/or accessories of/to this device, if applicable. For typical stand-alone software of
109
+ > startups, this shouldn't be applicable.
110
+
111
+ ---
112
+
113
+ Template Copyright [openregulatory.com](https://openregulatory.com). See [template
114
+ license](https://openregulatory.com/template-license).
115
+
116
+ Please don't remove this notice even if you've modified contents of this template.
@@ -0,0 +1,114 @@
1
+ # MDR Classification Document
2
+
3
+ ## Mapping of Requirements
4
+
5
+ | Medical Device Regulation (MDR) | Document Section |
6
+ | ------------------------------- | ---------------- |
7
+ | Annex VIII | (All) |
8
+
9
+ **Related documents:**
10
+
11
+ * Intended Use
12
+ * SOP Product Certification and Registration
13
+
14
+ ## Summary
15
+
16
+ | Product: | (enter content) |
17
+ |-----------------|-----------------|
18
+ | Version: | (enter content) |
19
+ | Classification: | (enter content) |
20
+ | Rule: | (enter content) |
21
+
22
+ Rationale for the qualification of the product as a medical device (MDR Annex II, para. 1.1.e):
23
+ See Intended Use Statement
24
+
25
+ ## Chapter 1: Applicable Definitions
26
+
27
+ > You will need to carefully check and fill out all rows below. Some rows are pre-filled for applicability
28
+ > under the assumption of a stand-alone software medical device. However, this is quite an essential document
29
+ > and you're better off checking twice.
30
+
31
+ **1. Duration of Use**
32
+
33
+ | Term | Definition | Applicable |
34
+ |------------|-----------------------------------------------------------------|------------|
35
+ | Transient | Normally intended for continuous use for less than 60 minutes. | |
36
+ | Short term | Normally intended for continuous use for not more than 30 days. | |
37
+ | Long term | Normally intended for continuous use for more than 30 days. | |
38
+ | | | |
39
+
40
+ **2. Invasive and Active Devices**
41
+
42
+ | Definition | Applicable |
43
+ | ---------- | ---------- |
44
+ | **2.1 Body orifice** means any natural opening in the body, as well as the external surface of the eyeball, or any permanent artificial opening, such as a stoma. | No |
45
+ | **2.2 Surgically invasive device** means:<br>(a) an invasive device which penetrates inside the body through the surface of the body, including through mucous membranes of body orifices with the aid or in the context of a surgical operation; and<br>(b) a device which produces penetration other than through a body orifice. | No |
46
+ | **2.3 Reusable surgical instrument** means an instrument intended for surgical use in cutting, drilling, sawing, scratching, scraping, clamping, retracting, clipping or similar procedures, without a connection to an active device and which is intended by the manufacturer to be reused after appropriate procedures such as cleaning, disinfection and sterilization have been carried out. | No |
47
+ | **2.4 Active therapeutic device** means any active device used, whether alone or in combination with other devices, to<br>support, modify, replace or restore biological functions or structures with a view to treatment or alleviation of an<br>illness, injury or disability. | |
48
+ | **2.5 Active device intended for diagnosis and monitoring** means any active device used, whether alone or in combination with other devices, to supply information for detecting, diagnosing, monitoring or treating physio logical conditions, states of health, illnesses or congenital deformities. | |
49
+ | **2.6 Central circulatory system** means the following blood vessels:<br>arteriae pulmonales, aorta ascendens, arcus aortae, aorta descendens to the bifurcatio aortae, arteriae coronariae, arteria carotis communis, arteria carotis externa, arteria carotis interna, arteriae cerebrales, truncus brachiocephalicus, venae cordis, venae pulmonales, vena cava superior and vena cava inferior. | |
50
+ | **2.7 Central nervous system** means the brain, meninges and spinal cord. | |
51
+ | **2.8 Injured skin or mucous membrane** means an area of skin or a mucous membrane presenting a pathological<br>change or change following disease or a wound. | |
52
+
53
+ ## Chapter 2: Implementing Rules
54
+
55
+ | Rules | Applicable |
56
+ | ----- | ---------- |
57
+ | **3.1** Application of the classification rules shall be governed by the intended purpose of the devices. | Yes |
58
+ | **3.2** If the device in question is intended to be used in combination with another device, the classification rules shall apply separately to each of the devices. Accessories for a medical device and for a product listed in Annex XVI MDR shall be classified in their own right separately from the device with which they are used. | |
59
+ | **3.3** Software, which drives a device or influences the use of a device, shall fall within the same class as the device.<br>If the software is independent of any other device, it shall be classified in its own right. | |
60
+ | **3.4** If the device is not intended to be used solely or principally in a specific part of the body, it shall be considered and classified on the basis of the most critical specified use. | |
61
+ | **3.5** If several rules, or if, within the same rule, several sub-rules, apply to the same device based on the device's intended purpose, the strictest rule and sub-rule resulting in the higher classification shall apply. | |
62
+ | **3.6** In calculating the duration referred to in Section 1, continuous use shall mean:<br>(a) the entire duration of use of the same device without regard to temporary interruption of use during a procedure or temporary removal for purposes such as cleaning or disinfection of the device. Whether the interruption of use or the removal is temporary shall be established in relation to the duration of the use prior to and after the period when the use is interrupted or the device removed; and<br>(b) the accumulated use of a device that is intended by the manufacturer to be replaced immediately with another of the same type. | |
63
+ | **3.7** A device is considered to allow direct diagnosis when it provides the diagnosis of the disease or condition in question by itself or when it provides decisive information for the diagnosis. | |
64
+
65
+ ## Chapter 3: Classification Rules
66
+
67
+ **4.) Non-Invasive Devices**
68
+
69
+ | Rules | Applicable |
70
+ | ----- | ---------- |
71
+ | ***Rule 1***<br>All non-invasive devices are classified as class I, unless one of the rules set out hereinafter applies. | |
72
+ | ***Rule 2***<br>All non-invasive devices intended for channelling or storing blood, body liquids, cells or tissues, liquids or gases for the purpose of eventual infusion, administration or introduction into the body are classified as class IIa:<br>— if they may be connected to a class IIa, class IIb or class III active device; or<br>— if they are intended for use for channelling or storing blood or other body liquids or for storing organs, parts<br>of organs or body cells and tissues, except for blood bags; blood bags are classified as class IIb.<br>In all other cases, such devices are classified as class I. | No |
73
+ | ***Rule 3***<br>All non-invasive devices intended for modifying the biological or chemical composition of human tissues or cells, blood, other body liquids or other liquids intended for implantation or administration into the body are classified as class IIb, unless the treatment for which the device is used consists of filtration, centrifugation or exchanges of gas, heat, in which case they are classified as class IIa.<br><br>All non-invasive devices consisting of a substance or a mixture of substances intended to be used in vitro in direct<br>contact with human cells, tissues or organs taken from the human body or used in vitro with human embryos<br>before their implantation or administration into the body are classified as class III. | No |
74
+ | ***Rule 4***<br>All non-invasive devices which come into contact with injured skin or mucous membrane are classified as:<br>— class I if they are intended to be used as a mechanical barrier, for compression or for absorption of exudates;<br>— class IIb if they are intended to be used principally for injuries to skin which have breached the dermis or<br>mucous membrane and can only heal by secondary intent;<br>— class IIa if they are principally intended to manage the micro-environment of injured skin or mucous membrane; and<br>— class IIa in all other cases.<br><br>This rule applies also to the invasive devices that come into contact with injured mucous membrane. | No |
75
+
76
+ **5.) Invasive Devices**
77
+
78
+ | Rules | Applicable |
79
+ | ----- | ---------- |
80
+ | ***Rule 5***<br>All invasive devices with respect to body orifices, other than surgically invasive devices, which are not intended for connection to an active device or which are intended for connection to a class I active device are classified as:<br>— class I if they are intended for transient use;<br>— class IIa if they are intended for short-term use, except if they are used in the oral cavity as far as the pharynx, in an ear canal up to the ear drum or in the nasal cavity, in which case they are classified as class I; and<br>— class IIb if they are intended for long-term use, except if they are used in the oral cavity as far as the pharynx, in an ear canal up to the ear drum or in the nasal cavity and are not liable to be absorbed by the mucous membrane, in which case they are classified as class IIa.<br><br>All invasive devices with respect to body orifices, other than surgically invasive devices, intended for connection<br>to a class IIa, class IIb or class III active device, are classified as class IIa. | No |
81
+ | ***Rule 6***<br>All surgically invasive devices intended for transient use are classified as class IIa unless they:<br>— are intended specifically to control, diagnose, monitor or correct a defect of the heart or of the central circulatory system through direct contact with those parts of the body, in which case they are classified as class III;<br>— are reusable surgical instruments, in which case they are classified as class I;<br>— are intended specifically for use in direct contact with the heart or central circulatory system or the central nervous system, in which case they are classified as class III;<br>— are intended to supply energy in the form of ionising radiation in which case they are classified as class IIb;<br>— have a biological effect or are wholly or mainly absorbed in which case they are classified as class IIb; or<br>— are intended to administer medicinal products by means of a delivery system, if such administration of a medicinal product is done in a manner that is potentially hazardous taking account of the mode of application, in which case they are classified as class IIb. | No |
82
+ | ***Rule 7***<br>All surgically invasive devices intended for short-term use are classified as class IIa unless they:<br>— are intended specifically to control, diagnose, monitor or correct a defect of the heart or of the central circulatory system through direct contact with those parts of the body, in which case they are classified as class III;<br>— are intended specifically for use in direct contact with the heart or central circulatory system or the central nervous system, in which case they are classified as class III;<br>— are intended to supply energy in the form of ionizing radiation in which case they are classified as class IIb;<br>— have a biological effect or are wholly or mainly absorbed in which case they are classified as class III;<br>— are intended to undergo chemical change in the body in which case they are classified as class IIb, except if the devices are placed in the teeth; or<br>— are intended to administer medicines, in which case they are classified as class IIb. | No |
83
+ | ***Rule 8***<br>All implantable devices and long-term surgically invasive devices are classified as class IIb unless they:<br>— are intended to be placed in the teeth, in which case they are classified as class IIa;<br>— are intended to be used in direct contact with the heart, the central circulatory system or the central nervous system, in which case they are classified as class III;<br>— have a biological effect or are wholly or mainly absorbed, in which case they are classified as class III;<br>— are intended to undergo chemical change in the body in which case they are classified as class III, except if the devices are placed in the teeth;<br>— are intended to administer medicinal products, in which case they are classified as class III;<br>— are active implantable devices or their accessories, in which cases they are classified as class III;<br>— are breast implants or surgical meshes, in which cases they are classified as class III;<br>— are total or partial joint replacements, in which case they are classified as class III, with the exception of ancillary components such as screws, wedges, plates and instruments; or<br>— are spinal disc replacement implants or are implantable devices that come into contact with the spinal column, in which case they are classified as class III with the exception of components such as screws, wedges, plates and instruments. | No |
84
+
85
+ **6.) Active Devices**
86
+
87
+ | Rules | Applicable |
88
+ | ----- | ---------- |
89
+ | ***Rule 9***<br>All active therapeutic devices intended to administer or exchange energy are classified as class IIa unless their characteristics are such that they may administer energy to or exchange energy with the human body in a potentially hazardous way, taking account of the nature, the density and site of application of the energy, in which case they are classified as class IIb.<br><br>All active devices intended to control or monitor the performance of active therapeutic class IIb devices, or intended directly to influence the performance of such devices are classified as class IIb.<br><br>All active devices intended to emit ionizing radiation for therapeutic purposes, including devices which control or monitor such devices, or which directly influence their performance, are classified as class IIb.<br><br>All active devices that are intended for controlling, monitoring or directly influencing the performance of active implantable devices are classified as class III. | |
90
+ | ***Rule 10***<br>Active devices intended for diagnosis and monitoring are classified as class IIa:<br>— if they are intended to supply energy which will be absorbed by the human body, except for devices intended to illuminate the patient's body, in the visible spectrum, in which case they are classified as class I;<br>— if they are intended to image in vivo distribution of radiopharmaceuticals; or<br>— if they are intended to allow direct diagnosis or monitoring of vital physiological processes, unless they are specifically intended for monitoring of vital physiological parameters and the nature of variations of those parameters is such that it could result in immediate danger to the patient, for instance variations in cardiac performance, respiration, activity of the central nervous system, or they are intended for diagnosis in clinical situations where the patient is in immediate danger, in which cases they are classified as class IIb.<br><br>Active devices intended to emit ionizing radiation and intended for diagnostic or therapeutic radiology, including interventional radiology devices and devices which control or monitor such devices, or which directly influence their performance, are classified as class IIb. | |
91
+ | ***Rule 11***<br>Software intended to provide information which is used to take decisions with diagnosis or therapeutic purposes is classified as class IIa, except if such decisions have an impact that may cause:<br>— death or an irreversible deterioration of a person's state of health, in which case it is in class III; or<br>— a serious deterioration of a person's state of health or a surgical intervention, in which case it is classified as class IIb.<br><br>Software intended to monitor physiological processes is classified as class IIa, except if it is intended for monitoring of vital physiological parameters, where the nature of variations of those parameters is such that it could result in immediate danger to the patient, in which case it is classified as class IIb. All other software is classified as class I. | Yes |
92
+ | ***Rule 12***<br>All active devices intended to administer and/or remove medicinal products, body liquids or other substances to or from the body are classified as class IIa, unless this is done in a manner that is potentially hazardous, taking account of the nature of the substances involved, of the part of the body concerned and of the mode of application in which case they are classified as class IIb. | |
93
+ | ***Rule 13***<br>All other active devices are classified as class I. | |
94
+
95
+ **7.) Special Rules**
96
+
97
+ | Rules | Applicable |
98
+ | ----- | ---------- |
99
+ | ***Rule 14***<br>All devices incorporating, as an integral part, a substance which, if used separately, can be considered to be a medicinal product, as defined in point 2 of Article 1 of Directive 2001/83/EC, including a medicinal product derived from human blood or human plasma, as defined in point 10 of Article 1 of that Directive, and that has an action ancillary to that of the devices, are classified as class III. | No |
100
+ | ***Rule 15***<br>All devices used for contraception or prevention of the transmission of sexually transmitted diseases are classified as class IIb, unless they are implantable or long term invasive devices, in which case they are classified as class III. | No |
101
+ | ***Rule 16***<br>All devices intended specifically to be used for disinfecting, cleaning, rinsing or, where appropriate, hydrating contact lenses are classified as class IIb.<br><br>All devices intended specifically to be used for disinfecting or sterilising medical devices are classified as class IIa, unless they are disinfecting solutions or washer-disinfectors intended specifically to be used for disinfecting invasive devices, as the end point of processing, in which case they are classified as class IIb.<br><br>This rule does not apply to devices that are intended to clean devices other than contact lenses by means of physical action only. | No |
102
+ | ***Rule 17***<br>Devices specifically intended for recording of diagnostic images generated by X-ray radiation are classified as class IIa. | No |
103
+ | ***Rule 18***<br>All devices manufactured utilizing tissues or cells of human or animal origin, or their derivatives, which are non-viable or rendered non-viable, are classified as class III, unless such devices are manufactured utilizing tissues or cells of animal origin, or their derivatives, which are non-viable or rendered non-viable and are devices intended to come into contact with intact skin only. | No |
104
+ | ***Rule 19***<br>All devices incorporating or consisting of nanomaterial are classified as:<br>— class III if they present a high or medium potential for internal exposure;<br>— class IIb if they present a low potential for internal exposure; and<br>— class IIa if they present a negligible potential for internal exposure. | No |
105
+ | ***Rule 20***<br>All invasive devices with respect to body orifices, other than surgically invasive devices, which are intended to administer medicinal products by inhalation are classified as class IIa, unless their mode of action has an essential impact on the efficacy and safety of the administered medicinal product or they are intended to treat life-threatening conditions, in which case they are classified as class IIb. | No |
106
+ | ***Rule 21***<br>Devices that are composed of substances or of combinations of substances that are intended to be introduced into the human body via a body orifice or applied to the skin and that are absorbed by or locally dispersed in the human body are classified as:<br>— class III if they, or their products of metabolism, are systemically absorbed by the human body in order to achieve the intended purpose;<br>— class III if they achieve their intended purpose in the stomach or lower gastrointestinal tract and they, or their products of metabolism, are systemically absorbed by the human body;<br>— class IIa if they are applied to the skin or if they are applied in the nasal or oral cavity as far as the pharynx, and achieve their intended purpose on those cavities; and<br>— class IIb in all other cases. | No |
107
+ | ***Rule 22***<br>Active therapeutic devices with an integrated or incorporated diagnostic function which significantly determines the patient management by the device, such as closed loop systems or automated external defibrillators, are classified as class III. | |
108
+
109
+ ---
110
+
111
+ Template Copyright [openregulatory.com](https://openregulatory.com). See [template
112
+ license](https://openregulatory.com/template-license).
113
+
114
+ Please don't remove this notice even if you've modified contents of this template.
@@ -0,0 +1,198 @@
1
+ # Risk Management Plan
2
+
3
+ <!-- AI AGENT 작성 지침
4
+ 이 문서는 ISO 14971:2019 기반 위험 관리 계획서입니다. PA 단계에서 작성하는 핵심 산출물입니다.
5
+
6
+ 작성 전 반드시 다음 문서를 참조하세요:
7
+ - 사용 목적 정의서(intended-use.md): 의도된 사용자, 사용 환경, 의료 목적 확인
8
+
9
+ 작성 지침:
10
+ 1. 제품명과 버전을 문서 상단에 명시하세요
11
+ 2. 1.2.1 사용량 추정은 실제 제품의 예상 사용자 수와 수명을 기반으로 작성하세요
12
+ - 예: 제품 수명 3년, 일일 100회 사용 -> 총 109,575회 사용
13
+ 3. 1.2.2 중증도 등급(S1~S4)은 실제 제품에서 발생 가능한 위해 예시로 변경하세요
14
+ - 진단 보조 SW의 경우: 오진으로 인한 불필요한 시술, 치료 지연 등
15
+ 4. 1.2.3 확률 등급(P1~P5)의 "Estimated Maximum Event Count"를 실제 사용량 계산 결과로 업데이트하세요
16
+ 5. 1.2.4 위험 허용 매트릭스는 제품의 의료적 이득-위험 균형을 반영하여 결정하세요
17
+ 6. 담당자(Roles) 섹션에 실제 담당자 이름과 역할을 기재하세요
18
+
19
+ 위험 관리 계획서 완성 체크리스트:
20
+ [ ] 제품명/버전 명시
21
+ [ ] 위험 관리자(Risk Manager) 지정
22
+ [ ] 사용량 추정 수치 입력
23
+ [ ] 중증도 정의가 제품 특성에 맞게 수정됨
24
+ [ ] 위험 허용 매트릭스 경영진 승인 완료
25
+ [ ] SOP Integrated Software Development 참조 확인
26
+ -->
27
+
28
+
29
+ The Risk Management Plan contains the risk policy and defines the criteria for risk acceptance. It also
30
+ references relevant processes and activities which will be conducted for product-specific risk management as
31
+ part of the integrated software development process (SOP Integrated Software Development).
32
+
33
+ ## Mapping of Standard Requirements to Document Sections
34
+
35
+ | ISO 14971:2019 Section | Document Section |
36
+ | ---------------------- | ----------------------------------------------- |
37
+ | 4.1 | 1 |
38
+ | 4.2 | 1.2, 3 |
39
+ | 4.3 | (Records of competence are kept as Part of QMS) |
40
+ | 4.4 | (all) |
41
+ | 4.5 | (all) |
42
+ | 5.1 | 1.1 |
43
+ | 7.2 | 1.3 |
44
+ | 10.1 | 1.4 |
45
+
46
+ ## 1. Relevant Processes
47
+
48
+ ### 1.1 Risk Management Process and Activities
49
+
50
+ Risk Management Activities are integrated in the software development lifecycle as described in SOP Integrated
51
+ Software Development. The scope of this risk management plan therefore covers the entire software device lifecycle.
52
+
53
+ When creating a first-time risk analysis for a product, Annex C of ISO 14971 should be reviewed for applicable examples.
54
+
55
+ ### 1.2 Risk Policy and Risk Acceptability
56
+
57
+ The following policy establishes criteria for risk acceptability following ISO 14971:2019 and ISO/TR
58
+ 24971:2020. It applies to all people and activities involved in the design, development and distribution
59
+ process of the medical device, and intends to ensure highest levels of medical device safety consistent with
60
+ stakeholder expectations.
61
+
62
+ The manufacturer defines framework criteria for risk acceptability in the form of estimated usage, severity of
63
+ harm and probability of occurrence. The criteria are initially defined as part of the early software development process and reviewed during each post-market surveillance cycle.
64
+
65
+ Estimated usage, categories of severity / probability and risk matrix acceptance are defined based on
66
+ applicable regulatory requirements, relevant international norms and standards, as well as the generally
67
+ acknowledged state of the art (e.g. accepted results of scientific research, reports published by authorities,
68
+ established industry best practices).
69
+
70
+ Acceptability for individual risks always must be established based on both, the estimated severity and the
71
+ estimated probability of a risk. The risk is deemed acceptable based on a combination of both, following the
72
+ risk matrix defined in para. 1.2.4.
73
+
74
+ All identified risks must be reduced as far as possible (AFAP) without adversely affecting the
75
+ benefit-risk-ratio. Risk control measures implemented to reduce the risks must be chosen in the following
76
+ order:
77
+
78
+ 1. Inherent safety by design
79
+ 2. Protective measures
80
+ 3. Information for safety
81
+
82
+ Users of the device must be informed about any remaining residual risks.
83
+
84
+ Acceptability of the overall residual risk is established as part of the clinical evaluation process by
85
+ weighing benefits from intended use against the overall residual risk. Benefits may be described by their
86
+ magnitude or extent, the probability of experience within the intended patient population, the duration and
87
+ frequency of the benefit. For example, the manufacturer may compare the device to similar medical devices
88
+ available on the market: residual risks can be compared individually to corresponding risks of the similar
89
+ device, considering differences in intended use. The overall evaluation of the benefit-risk-ratio should take
90
+ into account knowledge of the intended medical indication, the generally acknowledged state of the art in
91
+ technology and medicine, and the availability of alternative medical devices or treatments.
92
+
93
+ #### 1.2.1 Estimates for Usage
94
+
95
+ > Define estimates for how much you think your device is going to be used in the market.
96
+
97
+ | Usage | Values |
98
+ | ----------------- | ------------------------------------------------------------------------------------------------------------------ |
99
+ | Product life span | Enter number of years you expect the device to be in the market (from design conceptualization to decommissioning) |
100
+ | Users | Enter number of estimated users here |
101
+ | Usages / user | Enter number of estimated times the device is used per user |
102
+ | Total usages | Do the math! |
103
+
104
+ The software's lifetime is established to be [for example: three years]. This is what is expected to be the
105
+ maximum time until the implementation of a significant change, by which the manufacturer is able to react to
106
+ the relevant changes to the software device environment, such as SOUP changes, cybersecurity innovations, or
107
+ the evolving technological or medical state of the art.
108
+
109
+ Estimated product lifetime may not align with the planned PMS / PMCF surveillance periods, as continuous risk
110
+ management involves continuous updates of the risk management file in order to account for new information in
111
+ a timely manner.
112
+
113
+ #### 1.2.2 Severity of Harm
114
+
115
+ > Define what can go wrong with your product here. Make the examples specific - chances are, your product
116
+ > can't cause skin lacerations. In all likelihood it also doesn't cause death. So, feel free to remove
117
+ > severity rows here. But most importantly, customize the definitions and examples so that they resemble the
118
+ > harms in your product.
119
+
120
+ | Severity | Definition and Examples |
121
+ | ---------------- | --------------------------------------------------------------------------------------------------------- |
122
+ | S1: Negligible | Minor, reversible damage, e.g. superficial skin irritation, delay of non-critical treatment |
123
+ | S2: Marginal | Minor, reversible damage with required medical intervention, e.g. skin laceration requiring stitches |
124
+ | S3: Critical | Major, irreversible damage with required medical intervention, e.g. irreversible deterioration of disease |
125
+ | S4: Catastrophic | Death |
126
+
127
+ #### 1.2.3 Probability of Occurrence
128
+
129
+ > Define your probabilities. You can probably just use these definitions. The idea is that each probability
130
+ > row is 10^2 apart from adjacent ones.
131
+
132
+ > Also, change the "Estimated Maximum Event Count". That's the usage number you estimate for your (not yet
133
+ > released product) during its entire lifecycle (which you need to define). So, if you assume that your
134
+ > product will be on the market for 4 years and that it'll be used 100 times per day, that results in 146.100
135
+ > usages (100 usages/day * 365.25 days/year * 4 years). The numbers in the lower columns of "Estimated Maximum
136
+ > Event Count" are simply the total usage number multiplied by the upper limit probability of the same row,
137
+ > e.g. you want to know "how often can probability P3 occur if the product is being used 100 times per day?"
138
+
139
+ | Probability | Upper Limit | Lower Limit | Estimated Maximum Event Count |
140
+ | --------------- | ----------- | ----------- | ----------------------------- |
141
+ | P5: Certain | 1 | 10^-2 | 1000000 *(change this*) |
142
+ | P4: Likely | 10^-2 | 10^-4 | 10000 |
143
+ | P3: Unlikely | 10^-4 | 10^-6 | 100 |
144
+ | P2: Rare | 10^-6 | 10^-8 | 1 |
145
+ | P1: Unthinkable | 10^-8 | 0 | 0 |
146
+
147
+ #### 1.2.4 Risk Acceptance Matrix
148
+
149
+ > The most important part. You assess each severity-probability combination whether it's acceptable for you as
150
+ > a company. There are no definitive rules on what's deemed acceptable. It depends on your company's risk
151
+ > policy and, more importantly, the benefits of your product which you show in your clinical evaluation. So,
152
+ > for example, if your product saves 10 lives per day, it might be acceptable to cause one death per day. If
153
+ > your product doesn't save any lives, it might not be acceptable to cause any deaths. You get the idea, I
154
+ > hope.
155
+
156
+ | Probability | S1: Negligible | S2: Marginal | S3: Critical | S4: Catastrophic | Estimated Maximum Event Count |
157
+ | --------------- | -------------- | ---------------- | ---------------- | ---------------- | ----------------------------- |
158
+ | P5: Certain | acceptable | **unacceptable** | **unacceptable** | **unacceptable** | 1000000 |
159
+ | P4: Likely | acceptable | **unacceptable** | **unacceptable** | **unacceptable** | 10000 |
160
+ | P3: Unlikely | acceptable | acceptable | **unacceptable** | **unacceptable** | 100 |
161
+ | P2: Rare | acceptable | acceptable | acceptable | **unacceptable** | 1 |
162
+ | P1: Unthinkable | acceptable | acceptable | acceptable | acceptable | 0 |
163
+
164
+ ### 1.3 Verification of Risk Control Measures
165
+
166
+ Risk Control Measures are verified as described in the software development lifecycle as described in SOP
167
+ Integrated Software Development.
168
+
169
+ ### 1.4 Assessment of the overall residual risk
170
+
171
+ After determination of the Risk Control Measures any risk that could arise from the combination of the
172
+ individual risks or mitigating measures is assessed. For this purpose, the probability and severity of the
173
+ possible residual risk are estimated and evaluated using the existing risk matrix.
174
+
175
+ ### 1.5 Collection and Review of Post-Production Information
176
+
177
+ Review and collection of Post-Production information is described in SOP Post-Market Surveillance.
178
+
179
+ ## 2. Related Documents
180
+
181
+ * SOP Integrated Software Development
182
+ * Risk Acceptance Matrix
183
+ * Risk Table
184
+ * Risk Management Report
185
+
186
+ ## 3. Roles
187
+
188
+ | Title | Name(s) |
189
+ | ----------------------------------------------- | ------- |
190
+ | Risk Manager | |
191
+ | Context / Subject Matter Expert, e.g. physician | |
192
+
193
+ ---
194
+
195
+ Template Copyright [openregulatory.com](https://openregulatory.com). See [template
196
+ license](https://openregulatory.com/template-license).
197
+
198
+ Please don't remove this notice even if you've modified contents of this template.
@@ -0,0 +1,101 @@
1
+ # Security Management Plan
2
+
3
+ <!-- AI AGENT 작성 지침
4
+ 이 문서는 IEC 81001-5-1:2021 (Health software — Part 5-1: Security activities
5
+ in the software lifecycle) 및 AAMI TIR57 기반 보안 관리 계획서입니다.
6
+ PA 단계 핵심 산출물로, 본 문서가 보안의 단일 진실의 원천입니다.
7
+
8
+ 작성 전 반드시 다음 문서를 참조하세요:
9
+ - 소프트웨어 개발 및 유지보수 계획서(software-development-maintenance-plan.md): 개발 프로세스
10
+ - 위험 관리 계획서(risk-management-plan.md): 위해 정의, 위험 수용 기준
11
+ - 시스템 요구사항 명세서(system-requirements-spec.md): 시스템 경계, 자산
12
+
13
+ 작성 지침:
14
+ 1. Section 1 (보안 정책): Security by Design 원칙과 조직 보안 정책을 명시
15
+ 2. Section 3 (위협 모델링): 접근법(STRIDE 등)만 명시 — 구체적 위협 목록은 EA 산출물
16
+ 3. Section 5 (보안 V&V): 어떤 검증을 수행할지(SAST/SCA/침투테스트)만 명시 — 도구·절차 세부는 EA
17
+ 4. 본 문서는 PA 'Plan' 성격 — 구현 세부(SBOM 도구명·CVD runbook 등)는 EA/운영 단계로 미룸
18
+
19
+ 완성 체크리스트:
20
+ [ ] 보안 정책(Security by Design) 명시
21
+ [ ] 자산·위협 모델링 접근법 정의
22
+ [ ] 보안 요구사항 도출 기준(CIA) 정의
23
+ [ ] 보안 V&V 접근법(SAST/SCA/펜테스트) 명시
24
+ [ ] 취약점 관리·CVE 모니터링 주기 정의
25
+ [ ] 보안 담당자(Security Manager) 지정
26
+ -->
27
+
28
+ {PROJECT_NAME}의 보안 관리 계획서. 본 문서는 IEC 81001-5-1:2021에 따라 소프트웨어 보안
29
+ 활동을 정의하며, 보안의 단일 진실의 원천이다. 작성자: {AUTHOR}, 티켓: {TICKET_ID}, 일자: {DATE}.
30
+
31
+ ## Mapping of Standard Requirements to Document Sections
32
+
33
+ | Standard | Clause | Document Section |
34
+ | ----------------------- | ------------------------------------------------------------------------------- | ---------------- |
35
+ | IEC 81001-5-1:2021 | 5.1.1 Cybersecurity risk management plan | all |
36
+ | IEC 81001-5-1:2021 | 5.2 Threat modelling | 3 |
37
+ | IEC 81001-5-1:2021 | 5.3 Specification of security requirements | 4 |
38
+ | IEC 81001-5-1:2021 | 5.4 Implementation of security controls (planning) | 4 |
39
+ | IEC 81001-5-1:2021 | 5.5 Cybersecurity risk control verification (approach) | 5 |
40
+ | IEC 81001-5-1:2021 | 7 Cybersecurity activities in the operation phase (approach) | 6, 7 |
41
+ | AAMI TIR57 | Security Risk Management Process | 3, 4 |
42
+
43
+ ## 1. Purpose, Scope and Security Policy
44
+
45
+ > 목적·적용 범위·Security by Design 원칙·조직 보안 정책을 기술.
46
+
47
+ * Security by Design 원칙: 최소 권한, 방어 심도, 보안 기본값(deny-by-default)
48
+ * {SECURITY_POLICY}
49
+
50
+ ## 2. Security Organization and Roles
51
+
52
+ | Title | Name(s) |
53
+ | ----------------- | ------- |
54
+ | Security Manager | |
55
+ | Incident Response | |
56
+
57
+ ## 3. Threat Modelling Approach
58
+
59
+ > 위협 모델링 **접근법**만 명시. 구체적 위협 식별·평가는 EA 산출물로 이관.
60
+
61
+ * 방법론: {THREAT_METHODOLOGY} (예: STRIDE — Spoofing/Tampering/Repudiation/Info Disclosure/DoS/Elevation of Privilege)
62
+ * 자산 식별 범위: {ASSET_SCOPE}
63
+
64
+ ## 4. Security Requirements
65
+
66
+ > 보안 요구사항 도출 기준. CIA(기밀성·무결성·가용성) 관점.
67
+
68
+ 도출 기준:
69
+ * 인증(Authentication): {AUTH_CRITERIA}
70
+ * 권한 부여(Authorization): {AUTHZ_CRITERIA}
71
+ * 암호화(Encryption): {CRYPTO_CRITERIA}
72
+ * 로깅·감사(Logging): {LOGGING_CRITERIA}
73
+
74
+ ## 5. Security V&V Approach
75
+
76
+ > 보안 검증 **접근법** — 무엇을 수행할지만 명시. 도구·절차 세부는 EA.
77
+
78
+ * 정적 분석(SAST): {SAST_APPROACH}
79
+ * 소프트웨어 구성 분석(SCA) / 취약점 스캔: {SCA_APPROACH}
80
+ * 침투 테스트: {PENTEST_APPROACH}
81
+
82
+ ## 6. Vulnerability Management
83
+
84
+ > 취약점 관리·CVE 모니터링 주기 — 계획 수준.
85
+
86
+ * CVE 모니터링 주기: {CVE_MONITORING_FREQUENCY}
87
+ * 취약점 등록·조치: {VULN_TRACKING}
88
+
89
+ ## 7. Cybersecurity Incident Response / CVD
90
+
91
+ > 보안 사고 대응·Coordinated Vulnerability Disclosure 접근법 — 계획 수준.
92
+
93
+ * 사고 대응 절차: {INCIDENT_RESPONSE}
94
+ * CVD 정책: {CVD_POLICY}
95
+
96
+ ## 8. SBOM Management
97
+
98
+ > Software Bill of Materials 관리 방침.
99
+
100
+ * SBOM 형식: {SBOM_FORMAT} (예: SPDX, CycloneDX)
101
+ * 생성·갱신 시점: {SBOM_GENERATION}