Product Owner vs Registrant: Parallel Obligations in Singapore

1. Key takeaways

In Singapore, the obligations of the Product Owner and the Registrant run in parallel; one does not substitute for the other. The Product Owner is responsible for the safety and performance of the product itself, the truthfulness of the technical documentation and post-market technical support; the Registrant is responsible for the submission in Singapore, holding the certificate, change notifications and the local discharge of vigilance duties. For adverse event reporting, HSA expressly requires each party involved in the event to submit its own report; a report filed by the Registrant does not discharge the obligations of the other parties. The practical consequence is that compliance cannot be delegated away: even when a capable local Registrant handles everything visible to the regulator, the foreign Product Owner remains an independent duty-holder in the same reporting chain.

• Product Owner and Registrant duties are parallel and cumulative, not alternatives.
• The GN-15 Annex 1 LoA is an allocation of obligations, including the Product Owner’s commitment to provide post-market support.
• Where more than one dealer is involved in a reportable adverse event, each must submit its own report.
• The AE reporting clock starts when any personnel of the company, including sales representatives, become aware of the event.

2. Legal basis

The division of obligations rests on the registration guidance, the LoA instrument, HSA’s official adverse event reporting page and Part VIII of the parent Act, which imposes obligations on manufacturers, importers and similar parties.

Together these sources establish that the reporting duty attaches to each entity in the chain individually, and that the LoA is where the Product Owner formally acknowledges its share of the ongoing burden. That dual structure — statutory duties on every dealer plus a contractual-institutional allocation through the LoA — is what HSA relies on to keep foreign manufacturers reachable even though they hold no certificate in Singapore.

3. Expert insights

Insight 1: The GN-15 Annex 1 LoA is not a letter of entrustment; it is a contract allocating obligations. The HSA LoA template requires the Product Owner to expressly authorise the Registrant to submit on its behalf and to commit to providing post-market support. The most frequent problem we find when reviewing clients’ self-drafted authorisation letters is that they state only the authorisation to submit, without covering technical support, documentation updates, vigilance cooperation or cost allocation. Once an adverse event occurs post-market or HSA raises a query, the Registrant has no enforceable basis of obligation in hand, and the risk lands on the Chinese manufacturer itself — because the registration certificate is not in your name. A defective LoA therefore converts a regulatory document into a source of commercial exposure.

Insight 2: Multiple-party reporting is a seriously underestimated compliance risk point. HSA’s wording is direct: if a reportable adverse event involves more than one dealer, each party must submit its own report. This means that if the Registrant reports but the importer does not, the importer remains in breach. When we build vigilance systems for clients, we establish a separate reporting owner and a separate clock for every Singapore local entity. Companies that run a single reporting pipeline through the Registrant discover, often during an inspection, that their other local entities have been silently non-compliant for years.

Insight 3: The reporting clock starts from awareness by any employee. HSA states expressly: The clock for reporting starts as soon as any personnel in your company, including sales representatives, are made aware of the AE. This is where practice most often fails — a sales representative hears about a problem at a customer site, but there is no internal escalation mechanism, and by the time the regulatory department learns of it the 10 calendar day window may already be exceeded. Awareness-based clocks mean that AE training for front-line commercial staff is not an optional extra; it is part of the reporting system itself.

Insight 4: The Registrant’s obligations are not excused by the Product Owner’s non-cooperation. HSA’s enforcement target is the Singapore local entity. A Product Owner delaying technical information cannot justify late reporting by the Registrant. Contracts must therefore set an internal timeline for the Product Owner to relay safety information to the Registrant, and that timeline must be significantly shorter than the statutory one, so that the Registrant always retains enough runway to comply even if the first relay attempt fails.

4. Practical recommendations

• Fix the information relay timeline in the contract: we require clients to set the internal Product Owner-to-Registrant notification timeline in the Singapore AE reporting chain at no more than 5 calendar days, leaving buffer within the 10 calendar day statutory limit.
• Designate a separate vigilance owner for each Singapore entity: one each for the Registrant, the importer and the wholesaler; do not merge the roles.
• Build a sales-as-vigilance-outpost mechanism: bring sales and after-sales staff into AE escalation training, making the awareness-starts-the-clock rule explicit.
• Keep the LoA and the commercial contract separate but cross-referencing: the LoA satisfies HSA’s format requirements; the commercial contract governs fees, responsibilities and exit; their terms must not conflict.

5. Verification checklist

• □ The LoA uses the GN-15 Annex 1 template and includes the post-market support commitment
• □ The contract sets the Product Owner’s timeline for relaying technical and safety information
• □ Every Singapore local entity has an independent AE reporting owner
• □ Sales and after-sales staff have completed awareness-starts-the-clock training
• □ No conflict exists between the commercial contract and the LoA
• □ The party responsible for technical support in answering HSA queries has been identified

Regulatory information verified as of: 26 October 2026

Source level: Tier 2 (GN-15 R15 Annex 1, HSA official adverse event reporting page), Tier 1 (Health Products Act 2007 Part VIII)

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across Southeast Asia, including Singapore. Our team prepares dossiers to ASEAN CSDT structure, manages submissions and deficiency responses with HSA, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com