Complaint Handling, Recall Records and Device-Level Traceability

1. Key takeaways

South Africa’s vigilance system is built on verifiable records: adverse events are submitted on form GLF-MD-11A with one form per device; Field Safety Corrective Actions (FSCAs) require a complete initial report and provable delivery records; and upstream of all of this sit the complaint handling and recall records. Complaints are the first source of reportable events, and recalls are the last resort of risk control — the quality of the records for both directly determines the outcome of SAHPRA inspections and vigilance investigations. A company whose complaint file, recall file and vigilance submissions tell a consistent story, indexed by device and batch rather than by customer or order, will move through an inspection with far less friction than one whose records must be reconstructed after the fact.

2. Legal basis

3. Expert insights

Insight one: the one-form-per-device rule dictates that records must be organised by device. SAHPRA requires adverse event reports to be submitted with one form per device. This means the company’s complaint and event register must be indexed by device, model and batch, not by customer or purchase order. A register organised by customer requires extensive splitting and reassembly at submission time, which is one of the most common sources of delay, and delay is precisely what the reporting timelines leave no room for.

Insight two: a complaint is not an adverse event, but complaints are the entry point for events. The scope of a complaint is broader than that of an adverse event, covering quality, logistics and service issues as well. Companies must have an explicit decision rule for which categories of complaints are escalated into adverse event reports. That rule should be written into the SOP, applied with a recorded rationale for each complaint, rather than resting on the personal judgement of whichever staff member happens to open the file.

Insight three: Regulation 18 provides the basis for SAHPRA’s investigative powers. The 2016 Regulations contain Regulation 18 (Investigation), placed next to Regulation 19 (Offences and penalties). This arrangement shows that records are not merely an internal management tool but the first source of evidence when SAHPRA opens an investigation. Missing records make the subsequent handling materially worse, because the absence of documentation is itself interpreted against the company rather than treated as a neutral fact.

Insight four: recall records must prove scope and effectiveness. The FSCA initial report requires a list of affected countries, product codes and batch numbers, and an explanation of why other batches are not affected. This demands that the company’s traceability reaches at least the granularity of locating distribution flows by batch number — which is the real capability requirement that the South African vigilance system places on companies. Anything less turns a recall from a controlled exercise into a scramble.

Insight five: the exemption decision itself must also leave a trail. The four exemption categories in Annex 2 of SAHPGL-MD-03 give companies room not to report, but the exemption decision must be supported by a documented rationale. If SAHPRA later questions a specific event, the company must be able to explain why it was judged exempt at the time. An exemption without a record is no exemption at all.

4. Practical recommendations

1. Organise the register by device and batch: matching the one-form-per-device requirement.
2. Write the complaint-to-adverse-event escalation rule into the SOP: and keep the decision record for each case.
3. Use recall records to prove scope and effectiveness: batch flows, notifications and retrieval outcomes.
4. Document exemption decisions: record the rationale and the responsible person.
5. Retain FSCA delivery evidence: e-mail receipts, registered mail, visit records.
6. Run periodic record completeness self-checks: simulate the SAHPRA inspection perspective.

5. Verification checklist

• □ The complaint and event register is organised by device and batch
• □ Submissions are made on GLF-MD-11A with one form per device
• □ The complaint-to-adverse-event escalation rule is in the SOP with decision records retained
• □ Traceability reaches the granularity of locating flows by batch number
• □ Recall records include batch flows, notifications and retrieval outcomes
• □ Exemption decisions are documented with rationale and responsible person
• □ FSCA delivery evidence is archived (4 categories of channels)
• □ A periodic record completeness self-check mechanism is in place

Regulatory information verified as of 29 October 2026. The regulations, guidance and effective dates described in this article are limited to the official sources listed in the legal basis section above as published on that date; where official documents have been updated, the most recently published version prevails.

• Local resources in South Africa: GRZAN assists manufacturers from the Chinese mainland and other markets with SAHPRA medical device establishment licence (MDEL) applications and product registration preparation, including authorised representative (AR) scheme design, ISO 13485 certification pathway planning and CAB selection, GMDN coding and classification determination, technical documentation, and the setup of vigilance and adverse event notification mechanisms.
• Service capabilities: product attribute determination and risk classification (Class A, B, C, D), establishment licence applications and renewals, reliance pathway argumentation, technical documentation and essential principles conformity argumentation, labelling and instructions for use localisation in English, and support for post-market vigilance and annual compliance submissions.
• Contact: info@grzanglobal.com; hito.lin@grzan.cn; website www.grzan.cn.