T-006-004 Stakeholder NC Notification Template
Document Information
| Field | Value |
|---|---|
| NC Reference | [NC-YYYY-XXX] |
| NC Criticality | [ ] High / [ ] Medium / [ ] Low |
| Notification Date | [YYYY-MM-DD] |
| Notification Method | [ ] Email / [ ] Phone / [ ] Portal / [ ] Official Letter / [ ] Regulatory Submission System / [ ] Other |
| Prepared by | [Name, Role] |
| Approved by (JD-004) | [Name] |
| Stakeholder Type | [ ] Customer / [ ] Notified Body (NB) / [ ] Competent Authority (CA) / [ ] Distributor / [ ] Partner / [ ] Other |
Stakeholder Information
| Field | Value |
|---|---|
| Organization Name | [Organization/Authority name] |
| Stakeholder Type | [ ] Customer / [ ] Notified Body / [ ] Competent Authority / [ ] Distributor / [ ] Partner / [ ] Other |
| Contact Person | [Contact name] |
| Title/Role | [Title or role] |
| [Email address] | |
| Phone | [Phone number] |
| Address | [Official address, if applicable] |
| NB/CA Reference Number | [NB ID or CA reference, if applicable] |
| Affected Product(s) | [Product name/version/UDI] |
| Certificate Reference | [EC Certificate number, if applicable] |
Notification Content
Subject Line
- For Customers: [IMPORTANT] Legit Health Product Notification - [Brief NC Description] - Reference: [NC-YYYY-XXX]
- For Notified Bodies: Manufacturer Notification - Non-Conformity Report - [Product Name] - EC Certificate [Cert No.] - Reference: [NC-YYYY-XXX]
- For Competent Authorities: Manufacturer Notification per MDR Article [XX] - [Product Name] - Reference: [NC-YYYY-XXX]
Notification Body
Dear [Contact Name / To whom it may concern],
For Customers: We are writing to inform you of a non-conformity that has been identified which may affect your use of [Product Name].
For Notified Bodies: In accordance with our obligations under MDR 2017/745 and the terms of our Quality Management System certification, we hereby notify you of a non-conformity identified in relation to [Product Name], covered under EC Certificate [Certificate Number].
For Competent Authorities: In accordance with our obligations under MDR 2017/745 Article [XX], we hereby notify [Authority Name] of a non-conformity identified in relation to [Product Name].
1. Product Identification
| Field | Value |
|---|---|
| Product Name | [Product name] |
| Product Version/Model | [Version] |
| UDI-DI | [UDI-DI if applicable] |
| EC Certificate Number | [Certificate number] |
| Risk Class | [Class I / IIa / IIb / III] |
| Notified Body | [NB name and ID] |
2. Description of the Non-Conformity
[Provide a clear description of the non-conformity. For regulatory stakeholders, include technical details. For customers, use non-technical language where appropriate.]
- Date of Detection: [YYYY-MM-DD]
- Detection Method: [How the NC was discovered - internal audit, customer complaint, post-market surveillance, etc.]
- Affected Units/Scope: [Number of affected units, software versions, geographical scope, etc.]
3. Risk Assessment
| Aspect | Assessment |
|---|---|
| Severity | [Critical / Major / Minor] |
| Probability | [High / Medium / Low] |
| Risk Level | [High / Medium / Low] |
| Patient Safety Impact | [Description of potential patient safety impact] |
| Regulatory Impact | [Impact on compliance with essential requirements] |
4. Root Cause Analysis
[Summary of root cause analysis. Include methodology used (e.g., 5 Whys, Fishbone) and conclusions.]
5. Actions Taken and Planned
Immediate Actions (Containment):
- [Immediate action taken]
- [Additional containment measures]
Corrective Actions:
| Action | Responsible | Target Date | Status |
|---|---|---|---|
| [CA 1] | [Name] | [Date] | [Status] |
| [CA 2] | [Name] | [Date] | [Status] |
Preventive Actions:
| Action | Responsible | Target Date | Status |
|---|---|---|---|
| [PA 1] | [Name] | [Date] | [Status] |
| [PA 2] | [Name] | [Date] | [Status] |
- Expected Full Resolution Date: [YYYY-MM-DD]
6. Impact on Certified QMS / Technical Documentation
[Describe any impact on the certified Quality Management System or Technical Documentation. Indicate if updates to the Technical File are required.]
- No impact on QMS certification
- QMS documentation updated (specify documents)
- Technical Documentation updated (specify sections)
- Risk Management File updated
- Clinical Evaluation updated
7. Interim Measures / Customer Guidance
While we work on the permanent resolution, we recommend the following interim measures:
- [Workaround or temporary measure, if applicable]
- [Additional guidance]
If no interim measures are applicable, state: "No interim measures are required at this time."
8. Contact Information
For any questions or concerns regarding this notification:
- Quality Manager (JD-004): [Name], [Email], [Phone]
- Regulatory Affairs (JD-005): [Name], [Email], [Phone]
- General Contact: [support email]
We remain committed to ensuring the safety and performance of our products and appreciate your attention to this matter.
Best regards,
[Name]
[Role]
Legit Health
[Address]
Internal Use Only
Notification Tracking
| Field | Value |
|---|---|
| Stakeholder Type | [ ] Customer / [ ] NB / [ ] CA / [ ] Distributor / [ ] Other |
| Required Notification Time | [24h / 72h / 5 days / As per regulation] |
| Actual Notification Time | [X hours/days] |
| Within Timeframe? | [ ] Yes / [ ] No |
| Acknowledgment Received | [ ] Yes / [ ] No |
| Acknowledgment Date | [YYYY-MM-DD] |
| Follow-up Required by NB/CA? | [ ] Yes / [ ] No |
| Additional Information Requested | [ ] Yes / [ ] No - Details: [...] |
Regulatory Notification Requirements
| Stakeholder Type | Regulatory Basis | Timeframe |
|---|---|---|
| Notified Body | MDR 2017/745, QMS Agreement | As per agreement / Without undue delay |
| Competent Authority | MDR 2017/745 Art. 10(12), Art. 83-86 | As per incident type |
| Customer | GP-006 Internal Policy | High: 24h / Medium: 72h / Low: 5 days |
Follow-up Actions
| Date | Action | Responsible | Status |
|---|---|---|---|
| [Date] | [Follow-up action] | [Name] | [Status] |
| [Date] | [Response to NB/CA queries] | [Name] | [Status] |
| [Date] | [Resolution confirmation] | [Name] | [Status] |
| [Date] | [Stakeholder satisfaction check] | [Name] | [Status] |
Linked Records
- NC Report:
T-006-001Reference: [NC-YYYY-XXX] - CAPA Report:
T-006-003Reference: [CAPA-YYYY-XXX] (if applicable) - Vigilance Report:
GP-004Reference: [If applicable] - FSCA/FSN: [Field Safety Corrective Action / Field Safety Notice reference, if applicable]
Template Signature Meaning
Delete this section when you create a new record from this template.
- Author: JD-004
- Review: JD-005
- Approval: JD-001
Signature meaning
The signatures for the approval process of this document can be found in the verified commits at the repository for the QMS. As a reference, the team members who are expected to participate in this document and their roles in the approval process, as defined in Annex I Responsibility Matrix of the GP-001, are:
- Author: Team members involved
- Reviewer: JD-003 Design & Development Manager, JD-004 Quality Manager & PRRC
- Approver: JD-001 General Manager