Changes Triggered by Recall in Tanzania

1. Key takeaways

TMDA/DMD/MDA/G/003 §6.2 (Changes Triggered by Recall) establishes a dedicated procedure for changes arising from a recall. The official wording reads:

Changes occurring as a result of a recall are to be assessed to determine if they are significant, including design changes or design specification changes required to bring a medical device back in line with previous performance specifications.

Cover letters accompanying device applications in response to a recall should clearly identify that the application for change is being submitted for this purpose.

Applicant should contact TMDA directly before submission of application for change if nature of the product changes is associated with recalls.

Following a recall, the review time of these changes applications will be determined in consideration of both the nature of the changes involved and any potential safety concerns.

Four rules follow from this text:

1. The change must be assessed for whether it is a significant change, including design changes or design specification changes required to bring the device back in line with its previous performance specifications;
2. The cover letter accompanying the application must clearly identify that the change application is being submitted in response to a recall;
3. Where the nature of the change is associated with a recall, the applicant must contact TMDA directly before submission;
4. The review time for such change applications after a recall is determined in light of both the nature of the changes and any potential safety concerns.

The practical consequence is that a recall-triggered change never follows the ordinary change calendar. It is presumptively significant, it carries a pre-submission communication duty, its cover letter must disclose its purpose, and its timeline is deliberately left open-ended, so project planning for recall remediation must build in slack rather than rely on standard processing times.

2. Legal basis

3. Expert insights

Insight 1: Design changes after a recall are presumed significant, and the burden of arguing otherwise lies with the company.

The first sentence of §6.2 requires changes to be assessed to determine whether they are significant, and lists design changes or design specification changes required to bring the device back to its previous performance specifications as the paradigm case. Combined with the definition of significant change in §3.3 (a potential impact on function, performance, usability or safety shown by risk analysis), a recall-triggered change will almost invariably fall into the major or minor category and is unlikely to qualify as notifiable.

Insight 2: Contact TMDA before submission – a procedural step unique to this rule.

§6.2 expressly provides that the applicant should contact TMDA directly before submission, a pre-submission communication duty found only in the recall scenario. Its practical purpose is that during a recall the change review runs in parallel with the recall handling, and TMDA needs advance knowledge of the nature of the change in order to organise it. Skipping this step risks the application being shelved, and the contact record is itself part of the compliance evidence.

Insight 3: The open-ended review time is the biggest scheduling risk of this rule.

The final sentence of §6.2 provides that the review time will be determined in consideration of both the nature of the changes involved and any potential safety concerns. This means the 10-day implicit approval mechanism for minor changes cannot be assumed, and standard timelines cannot be used for planning. Project schedules must reserve an unspecified duration for recall-triggered changes and treat any committed date as conditional.

Insight 4: Recall, vigilance and PMS obligations must run in parallel on three tracks.

The recall itself is governed by Articles 63–66 (including Class I/II/III classification with maximum recall periods of 14/21/30 days); where the event triggering the recall meets the conditions of Article 41, reporting follows the 24-hour/14-day timelines of Article 42; and recalls, together with FSCA and FSN, must be included in the biennial PMS report (notice of 17 August 2026). A single recall therefore triggers four parallel obligation lines: recall classification and timelines, case-specific vigilance reporting, PMS inclusion, and the change application.

Insight 5: The recall handling duty of the LRP lands precisely here.

Article 9(c) requires the local responsible person to handle medical device recalls. When a recall triggers a change, the LRP is both the executing party and the communication channel – the foreign manufacturer must complete the pre-submission contact with TMDA under §6.2 and all subsequent submissions through the LRP, so the LRP’s availability and record-keeping directly determine the pace of the remediation.

4. Practical recommendations

1. Prepare recall-triggered changes as major or minor from the outset; do not plan for the notifiable category.
2. Have the LRP contact TMDA directly before submission and retain the communication records (§6.2).
3. State in the first paragraph of the cover letter that the change application is submitted in response to a recall, citing the recall reference and date.
4. Do not apply the 10-day implicit approval mechanism to scheduling; reserve an open-ended duration.
5. Run four registers in parallel: recall classification and timelines, vigilance reporting, PMS inclusion, and the change application.
6. Include verification data showing restoration to the previous performance specifications in the change dossier – this is the very scenario named in §6.2.

5. Verification checklist

• □ The assessment of whether the change is significant has been completed, including design/design specification changes.
• □ The LRP contacted TMDA directly before submission and records are retained (§6.2).
• □ The cover letter clearly identifies the purpose of responding to a recall.
• □ Scheduling does not rely on the 10-day implicit approval mechanism for minor changes.
• □ Four registers are maintained in parallel: recalls (Articles 63–66), vigilance (Articles 41–42), PMS (2026 notice) and changes.
• □ The change dossier contains verification data on restoration to the previous performance specifications.

Regulatory information verified as of 29 October 2026. All provisions cited in this document were checked against the official texts published by TMDA (TMDA/DMD/MDA/G/003 §6.2 and §3.1–§3.3; GN. No. 315, Article 9(c), Articles 41–42 and 63–66; TMDA public notice of 17 August 2026); the review is repeated whenever the regulations are updated.

• Tanzania local resources: GRZAN can coordinate licensed local responsible person (LRP) and distributor resources covering online submission, sample delivery, quality audit support and port release.
• Service capabilities: classification determination, registration and listing pathway selection, preparation and localisation of technical documentation (CSDT/STED), GMDN and grouping strategy, clinical evidence organisation, software and AI device submissions, change management, vigilance and PMS reporting, annual retention fee and renewal management.
• Contact: hito.lin@grzan.cn; website www.grzan.cn.