T-012-026 Product Validation Phase 5 Checklist
Actors
| Name | Title | Meaning | Approved Date & Time |
|---|---|---|---|
Change history
| Revision | Summary | Date |
|---|---|---|
Process overview
The purpose of the Product Validation Phase 5 Checklist review is to ensure the Product satisfy the criteria listed in the next section
Project information
- Project title:
- Project manager (name and function):
Planning
| Phase | Object | Done |
|---|---|---|
| Phase 1 Product Design Review | Establish input data | |
| Phase 2 Software Design Review | SRs, Architectural Design and UI Prototypes | |
| Phase 3 Software Candidate Release | Coding, integration and test plan | |
| Phase 4 Software Verification Review | Software version verified and residual anomalies | |
| Phase 5 Product Validation Review | Validation activities, Technical Documentation and DHF |
Previous reserves
If there were any reserves or outstanding issues identified during Phase 2, list them here. Include a brief description of each reserve, the actions required to address them, and assign an owner and targeted completion date. See T-012-024 Software Candidate Release Phase 3 Checklist for an example.
| N° | Documents / Purpose / Actions to implement | Owner | Targeted Date | Satisfying |
|---|---|---|---|---|
Final Risk Assessment
Per GP-013 Risk Management, verify that the final risk assessment is complete before proceeding with commissioning.
| Object | Records & Comments | Satisfying | Reserves |
|---|---|---|---|
| All risks have been identified and assessed in T-013-002 Risk Management Record | |||
| All risk control measures have been implemented | |||
| "Verification of Effectiveness" column in T-013-002 is completed for all risk control measures | |||
| All residual risks are within acceptable limits | |||
| No unacceptable new risks were introduced by risk control measures | |||
| If unacceptable risks exist, they are outweighed by benefits as documented in Clinical Evaluation Report | |||
| T-013-003 Risk Management Report is finalized | |||
| Software Safety Classification (R-TF-012-041) is finalized |
Outputs review
| Object | Records & Comments | Satisfying | Reserves see |
|---|---|---|---|
| Version Delivery Description | |||
| Clinical Evaluation plan | |||
| Clinical Evaluation report | |||
| Clinical Investigation report | |||
| Usability Summative Evaluation Report | |||
| AI/ML Evaluation Report | |||
| Cybersecurity Report | |||
| PMS Plan (R-TF-007-001) | |||
| PMCF Plan (R-TF-007-002) | |||
| Labeling and IFU verified per T-012-037 | |||
| DMF is updated |
Regulatory requirement review
| Key | Summary | Description | Satisfying | Reserves |
|---|---|---|---|---|
Reserves
| N° | Documents / Purpose / Actions to implement | Owner | Targeted Date |
|---|---|---|---|
Commissioning activities
Per GP-029 Software Delivery And Commissioning, commissioning activities must be completed and documented before design transfer.
| Object | Records & Comments | Satisfying | Reserves |
|---|---|---|---|
| T-029-001 Deployment & Configuration Commissioning is completed | |||
| T-029-002 Functional & Interface Commissioning is completed | |||
| T-029-003 Clinical Workflow & Operational Readiness Commissioning is completed | |||
| Software version behaves as expected on the production environment |
Post-Commissioning Risk Review
Per GP-013 Risk Management and ISO 14971:2019, after commissioning activities are completed, confirm that no new risks were identified.
| Object | Records & Comments | Satisfying | Reserves |
|---|---|---|---|
| No new risks were identified during deployment and configuration commissioning (T-029-001) | |||
| No new risks were identified during functional and interface commissioning (T-029-002) | |||
| No new risks were identified during clinical workflow commissioning (T-029-003) | |||
| No existing risk control measures were found to be ineffective in the production environment | |||
| T-013-002 Risk Management Record is updated if any new risks were identified | |||
| Overall residual risk assessment and risk-benefit analysis remain valid | |||
| Risk Management File closure is confirmed |
Design Transfer
| Object | Records & Comments | Satisfying | Reserves |
|---|---|---|---|
| T-012-039 Validated Version Transfer is completed and approved | |||
| Design transfer documentation reviewed - artefacts suitable for deployment in target servers | |||
| Customer success department notified and prepared for necessary actions |
Conclusion
Phase 5 Closure Confirmation
Upon approval of this checklist (T-012-026) and T-012-039 Validated Version Transfer, Phase 5 is complete and the Technical File for this version is formally closed.
| Closure criteria | Confirmed |
|---|---|
| All validation activities have been completed satisfactorily | |
| All regulatory documentation is complete and consistent | |
| All procedural reports (Clinical, Risk Management, Usability, Cybersecurity, AI/ML) are finalized | |
| Risk Management File has been closed with no outstanding risks | |
| Design History File (DHF) contains all required records for this version | |
| Version is ready for regulatory submission and market release |
Distribution countries
Comments
- Does the IFU and labelling contain all expected information?: yes/no
- Approval for the product certification and registration?: yes/no
- Regarding the mentioned reserves, has the review been accepted?: yes/no