Philippines Sterile, Software and Active Device Data Requirements

1. Key takeaways

Sterile devices must submit additional sterilisation validation material, covering the sterilisation method, the validation report, and shelf life and packaging validation. Devices containing software must submit software validation material, covering the software lifecycle together with verification and validation. Active devices must submit electrical safety and electromagnetic compatibility test reports. All of this material sits within the design verification and validation module of the CSDT, and any gap will trigger a deficiency directly.

GRZAN note: the three categories look unrelated but answer the same question, which is whether a critical process or a critical performance characteristic is demonstrably under control. The requirement set can be remembered as 3 device profiles, 1 dossier module, and 1 rule that the label must state what the validation proved.

• Sterile: sterilisation method, validation report, packaging and shelf life validation;
• Software: lifecycle documentation, verification and validation, locked version number;
• Active: electrical safety and EMC testing to the applicable standards;
• Biocompatibility evidence where the device contacts the patient.

The practical difficulty is that these three workstreams run on different clocks. Sterilisation validation and shelf life studies take time in real elapsed months, electrical safety testing depends on laboratory availability, and software verification depends on a design freeze. None of them can be compressed by administrative effort once the submission date is fixed.

2. Legal basis

The dossier module, the standards that apply to each device profile and the labelling consequences are summarised below. The standards listed are those applied in practice for the corresponding technology, and they are marked as applicable only where the device profile calls for them.

3. Expert insights

Insight 1: the common purpose of all three data sets is to prove that critical processes and critical performance are controlled. The reviewer reasoning is consistent across categories. For a sterile device, the question is whether the sterilisation process brings the product to the claimed sterility assurance level and maintains it throughout the shelf life. For a software-containing device, the question is whether the development process was controlled and whether the running result matches expectation. For an active device, the question is whether electrical safety and electromagnetic compatibility meet the standard. The objective is not to deliver a pile of reports but to let the reviewer see a complete chain from process to validation to conclusion.

Insight 2: the most common gap in sterile files is a shelf life claim disconnected from packaging validation. Many companies submit a sterilisation validation report without connecting packaging integrity validation to shelf life validation. A defensible shelf life requires three things to hold at once: sterilisation effectiveness, package barrier integrity, and transport simulation. If any one link is missing, the shelf life claim does not stand, and the reviewer will read the missing link as an unvalidated claim rather than as a documentation gap that can be answered later.

Insight 3: the documentation burden for software products rises with the risk level. What is required for a software-containing device depends on the consequences a software failure could produce. The higher the safety class of the software itself, the more detailed the lifecycle documentation and verification evidence required. The practical approach is to organise the material around the IEC 62304 software lifecycle framework and to state the software version and configuration explicitly — the version number must match the version actually installed in the declared product, which is a frequent source of deficiency.

Insight 4: accessories and components need a defined boundary. Active devices often come with accessories such as power adapters, probes and cables. Whether these are included in the same application depends on whether they form a functional part of the product. The submission should state the list of supplied accessories and the scope of their application, so that a later accessory change is not treated as a change to the registered device. This is a question of drawing the boundary once and documenting it, rather than of predicting every future configuration.

4. Practical recommendations

• For sterile devices, file sterilisation, packaging and shelf life as one chain. Complete any missing link before submitting.
• For software, organise around IEC 62304 and lock the version number. The documented version must match the physical product.
• For active devices, schedule IEC 60601 series testing early. Test lead times are long, so book capacity first.
• Write the accessory list and its scope into the submission. This reduces later disputes about whether a change requires notification.
• Mark the sterilisation status and method on the label. Keep it consistent with the validation report.

Read together, these five practices follow one principle: the dossier should describe a single product, not a collection of documents. The label, the validation report, the software version and the accessory list all describe the same object, and where they diverge the reviewer has no way of knowing which description is true. Divergence of this kind is rarely the result of carelessness in any one document; it usually appears when documents are produced by different teams at different times and nobody is given the task of comparing them.

5. Verification checklist

• □ Sterile: sterilisation validation report stating method, parameters and conclusion
• □ Sterile: packaging integrity validation report complete
• □ Sterile: shelf life validation linked to sterilisation and packaging
• □ Software: IEC 62304 documentation covering lifecycle, verification and validation
• □ Software: version number consistent between submission and physical product
• □ Active: IEC 60601 series testing covering electrical safety and EMC
• □ Accessory list with scope of application clearly stated
• □ Label stating sterilisation status and method

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