Adverse Event Reporting under GN-03: LRP Obligations in Hong Kong, China

1. Key takeaways

Post-market adverse event reporting in Hong Kong, China is borne by the Local Responsible Person (LRP), not by the overseas manufacturer. The governing instrument is Guideline GN-03, Guidelines on Medical Event Reporting by Local Responsible Persons. The Medical Device Division (MDD) of the Department of Health issues two reporting forms — one for completion by the LRP and one for completion by users — and each corresponds to a separate reporting route. The mechanism forms part of the MDACS post-market surveillance system, and its purpose is to detect safety signals early. The obligation is attached to the LRP, which is why it must be the first clause written into any delegation agreement.

• The duty sits with the LRP. An overseas manufacturer cannot discharge it by pointing to its distance from the market.
• Two forms serve two information sources: the user form lets a healthcare institution notify the MDD directly, while the LRP form is the channel through which the statutory duty is performed.
• Reporting is tied to listing status. The obligation covers events related to listed medical devices, so the boundary of the system is drawn by the register, not by the product portfolio.
• Reporting history affects eligibility. Note 1(b) of the expedited approval programme requires no ongoing recall, field safety corrective action or adverse event, whether local or global.
• Record keeping is one of the four post-market duties of the LRP and is open to inspection by the Medical Device Division.

2. Legal basis

The reporting regime rests on one guideline, two MDD forms, the code of practice for LRPs and the published overview of the listing process. The table below records the instruments relied on, their identifiers, publication status and the provisions engaged. Regulatory information was verified as of 29 October 2026; where an official document has since been updated, the latest published version prevails.

Two features of this legal basis deserve emphasis. First, the guideline does not create a free-standing duty on the manufacturer; it addresses the LRP as the reporting party. Second, the forms are issued by the MDD rather than by the guideline, so the version in use must be checked against the MDD website rather than against an archived copy held in a quality file.

3. Expert insights

Insight one: the reporting target is an event related to a listed medical device. The official formulation refers to reports of events related to listed medical devices. The consequence is that the reporting duty is bound to listing status: unlisted products fall outside the coverage of the system. That is a statement about the design boundary of the system, not a form of exemption. A manufacturer that reads it as an exemption will discover the gap at the point of procurement or at the point of a future listing application, when the absence of a reporting history becomes visible.

Insight two: the two routes were designed around the source of the information. The form for users allows a healthcare institution to raise a concern with the MDD directly, without routing it through a company first. The form for the LRP is the channel through which the LRP performs its own obligation. The design recognises that information about a device in use often originates with the clinician, and that a company cannot be the sole gatekeeper of what reaches the regulator. The LRP must not assume that a user report substitutes for its own duty. A user filing and an LRP filing are parallel acts; the second is not discharged by the first.

Insight three: reporting is directly linked to eligibility for the expedited approval programme. Note 1(b) of the programme requires that there be no ongoing recall, field safety corrective action or adverse event, locally and globally. The condition is written at the level of the corporate and product record, not at the level of a single application. One event that was not handled properly can therefore affect both an existing listing and eligibility for future accelerated routes. This is the reason a reporting file should be maintained as a regulatory asset rather than as a departmental correspondence folder.

Insight four: record keeping is an obligation that can be tested. The official overview of the listing process lists keeping records for inspection by the Medical Device Division as one of the four post-market duties of the LRP. The records concerned are not only the submitted forms. They include the investigation record and the conclusion reached. An inspection that asks what happened after a report was filed is testing whether the file closes, not whether the form was sent. In practice the commonest weakness is a complete set of submitted forms and an incomplete set of investigation conclusions.

Insight five: the timetable has two sides. The LRP can only report within its own deadline if it learns of the event in time. For a device manufactured outside Hong Kong, China, the information arrives through the manufacturer. Where the manufacturer’s global notification to the LRP is slower than the LRP’s reporting obligation to the MDD, the LRP is in breach through no fault of its own process. The contract, not the quality manual, is the instrument that fixes this, because the manufacturer’s global escalation route is outside the LRP’s operational control.

4. Practical recommendations

• Build an event grading rule. Define in the quality system which events must be reported and which need only an internal record, and state the basis for the distinction so that the same decision is reached by different people.
• Connect the manufacturer and the LRP information chain. Agree the time limit within which the manufacturer must notify the LRP after learning of a global event, and make that limit shorter than the LRP reporting deadline.
• File the investigation with the conclusion. Reporting is not the end point. The investigation and the final handling conclusion should form a closed record that can be produced as one file.
• Re-check eligibility conditions periodically. For products used in the expedited approval programme, re-verify the three conditions in paragraph 1 before each submission rather than once at the outset.
• Control the form version. Confirm that the form in use is the current MDD version, and record the version and download date in the file.

5. Verification checklist

• □ Event grading and reporting rules established under GN-03
• □ A named reporting owner on the LRP side
• □ Manufacturer-to-LRP notification time limit written into the contract
• □ Reporting, investigation and conclusion records closed and archived together
• □ Forms in use confirmed as the current MDD versions
• □ The three eligibility conditions of the expedited approval programme re-checked periodically
• □ User reports logged separately, so that no LRP obligation is treated as discharged by a user filing

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for Hong Kong, China. Our team manages adverse incident reporting and recall coordination with the Department of Health, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com