Technical Requirements and the Summary Test Report

1. Key takeaways

Article 10(2) of the Implementation Rules requires, in item (7), the submission of the technical requirements of the medical device, and in item (8), the submission of a summary test report for the medical device issued by the manufacturer of the device or by a third-party testing body. The provision links the two possible sources with the word ‘or’, which means both origins are acceptable; but the basis of reliance differs — a report issued by the manufacturer itself rests on the credibility of its quality management system, which can be verified through the inspection power in Article 12(3), whereas a report from a third-party body rests on that body’s independence and qualifications.

• The technical requirements concretise the device’s indicators and must be read together with the applicable mandatory standards.
• The summary test report need not be a full data package, but ISAF may request supplements under Article 10(5).
• Technical requirements are also mandatory for filing applications via Article 21(2)(4).
• Quality standards give priority to the mandatory national standards of China for medical devices.
• Inspection of the manufacturing site can verify data reliability, with a notice period of only 10 working days.

2. Legal basis

The dual obligation sits in the attachment list of the Implementation Rules, while the substantive test — which standards govern and how compliance can be verified — comes from the founding law. The classification ruling supplies the technical requirement framework, and the registration article of the founding law authorises on-site inspection.

3. Expert insights

First observation: the technical requirements and the quality standards are a matched pair. Article 12(2) provides that quality standards apply with priority to the mandatory national standards of China for medical devices; the technical requirements are the applicant’s concretisation of the device-specific indicators. The two must cite each other and must not conflict — technical requirements set below a mandatory national standard directly constitute non-conformity with the requirements of Article 12 and fall into the refusal scenarios of Article 16. Compilation teams should therefore treat the technical requirements document as a derivation from the applicable standards, with every device-specific indicator traceable to a clause number. Where no mandatory national standard covers a given parameter, the applicable ISAF-accepted standards identified in the classification ruling should be cited instead, and the basis of that acceptance recorded in the document itself.

Second observation: the summary test report requires a summary, not the full set of raw data. The wording of the provision is a summary report, not a complete test report package. This reduces the submission burden, but ISAF may demand supplements under Article 10(5), and the inspection of the manufacturing site under Article 14 can verify the reliability of the underlying data. The summary is thus the visible tip of a test evidence base that must exist and withstand scrutiny, even though it is not filed in full. Organising the underlying records to the same structure as the summary makes any later supplement a matter of retrieval rather than reconstruction.

Third observation: filing also requires the technical requirements. Article 21(2)(4) cites item (7) of Article 10(2) — the technical requirements are one of the few technical documents shared by filing and registration, which shows that the legislator regards them as the basic carrier of the regime. Whatever channel a device travels through, its technical parameters must be fixed in this document and must be identical to what appears on the label and in the declaration of conformity. Keeping a single controlled master version of the technical requirements, referenced by every other dossier component, prevents the silent divergence that file requests typically expose.

Fourth observation: the independence of the testing body is a common point of dispute for overseas applicants. Reports issued by an in-house testing centre belonging to a corporate group may face questions about their independence. When choosing a third-party body, a qualified independent laboratory is the safer choice (practical estimate). The concern is not formal but evidentiary: a reviewer who doubts the independence of the issuer has grounds to probe the data further, which extends timelines.

4. Practical recommendations

• Map every technical requirement to the mandatory national standard: state the standard number, version and conformity conclusion adopted.
• Cover every indicator of the technical requirements in the summary test report: any missing item breaks the evidence chain.
• Prefer third-party bodies for high-risk devices: for Class IIb and Class III devices, reports from a qualified independent laboratory are recommended.
• Retain raw test data for inspection: the inspection stage may verify data reliability, and the notice period for inspection is only 10 working days.

5. Verification checklist

• □ Technical requirements map item by item to the applicable mandatory national standards or standards accepted by ISAF
• □ Indicators in the technical requirements and the summary test report correspond exactly
• □ The issuer of the summary test report is the manufacturer or a third-party testing body, as the provision requires
• □ The need for an independent third-party body has been assessed for high-risk devices
• □ Raw test data have been archived for possible inspection
• □ In the filing scenario, item (7) has been confirmed as mandatory

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for Macao, China. Our team prepares SSM-compliant dossiers, coordinates language and legalisation requirements, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com