Maintaining compliance with IEC 62304, the global standard for medical device software lifecycle processes, is critical for gaining regulatory approval from bodies like the FDA and EU MDR/IVDR. Using an IEC 62304 Checklist in XLS (Excel) format is a practical way for engineering and quality teams to perform gap analyses, track deliverables, and ensure audit readiness. Core Components of an IEC 62304 XLS Checklist
This is a structured IEC 62304:2006+AMD1:2015 checklist guide, formatted for easy translation into an Excel (.xls/.xlsx) workbook.
IEC 62304 comprises several key components, including:
Here's an example of what the checklist might look like:
Sarah started her XLS sheet by categorizing their software. She knew that the level of rigor required depended on the potential for harm. : No injury possible. : Non-serious injury possible. : Death or serious injury possible. The Story Note
Failure #2: Forgetting Class C Specifics
| Req ID | Requirement Description | Safety Class Impact | Design Element (Class/Module) | Code File Name | Unit Test ID | System Test ID | Status |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| REQ-001 | User Login Authentication | High (Class C) | Auth_Module | login.py | UT-Auth-01 | ST-Sec-01 | PASS |
| REQ-002 | Display Patient Vitals | Medium (Class B) | UI_Display | vitals.js | N/A | ST-UI-02 | PASS |
| REQ-003 | Log Data Export | Low (Class A) | Logger | export.py | N/A | ST-Func-03 | FAIL |
Maintaining compliance with IEC 62304, the global standard for medical device software lifecycle processes, is critical for gaining regulatory approval from bodies like the FDA and EU MDR/IVDR. Using an IEC 62304 Checklist in XLS (Excel) format is a practical way for engineering and quality teams to perform gap analyses, track deliverables, and ensure audit readiness. Core Components of an IEC 62304 XLS Checklist
This is a structured IEC 62304:2006+AMD1:2015 checklist guide, formatted for easy translation into an Excel (.xls/.xlsx) workbook.
IEC 62304 comprises several key components, including:
Here's an example of what the checklist might look like:
Sarah started her XLS sheet by categorizing their software. She knew that the level of rigor required depended on the potential for harm. : No injury possible. : Non-serious injury possible. : Death or serious injury possible. The Story Note
Failure #2: Forgetting Class C Specifics
| Req ID | Requirement Description | Safety Class Impact | Design Element (Class/Module) | Code File Name | Unit Test ID | System Test ID | Status |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| REQ-001 | User Login Authentication | High (Class C) | Auth_Module | login.py | UT-Auth-01 | ST-Sec-01 | PASS |
| REQ-002 | Display Patient Vitals | Medium (Class B) | UI_Display | vitals.js | N/A | ST-UI-02 | PASS |
| REQ-003 | Log Data Export | Low (Class A) | Logger | export.py | N/A | ST-Func-03 | FAIL |
Field Application EngineeringOur Field Application Engineers are specialists in the capabilities of our products. They support customers with advice and examples on solutions and how to implement functionality in the most efficient way for different use cases and applications, based on our software platform.
Application developmentOur application development services are provided by our experienced team with a broad range of experience of display and on-board computing solutions, including instrumentation, process control, guidance, video, telematics and more.