Good packaging validation testing can still fail review if the documentation is hard to follow. A 510(k) reviewer or a Notified Body auditor does not re-run your tests — they read your file and decide whether it demonstrates compliance. The packaging chapter of the Design History File (DHF) is where that case is made. A well-structured chapter answers the reviewer's questions in the order they will ask them.
Start with the package definition and risk basis
Open with an unambiguous definition of the sterile barrier system and the protective packaging: materials, format (pouch, header bag, tray-and-lid), seal design, and the device it protects. Tie the packaging requirements to the risk analysis so it is clear why the package has to do what it does. A reviewer who understands the package and its purpose can follow everything that follows.
State the validation strategy and worst-case rationale
Document the strategy before the data: which ISO 11607-1 and ISO 11607-2 requirements are being addressed, how product families are bracketed, and why the tested configuration is the worst case. The worst-case rationale is one of the most frequently requested items in review — putting it up front, in writing, prevents the most common deficiency against packaging files.
Show the protocol with predefined acceptance criteria
Include the validation protocol with methods, sample sizes, statistical rationale, the sterilization sequence, the aging plan, and acceptance criteria fixed before testing. The fact that criteria were defined in advance is itself evidence of a controlled validation. A chapter that presents results without the protocol that called for them invites the question of whether the criteria were chosen to fit the data.
Cover both parts of ISO 11607
Make the Part 1 and Part 2 coverage explicit. Part 1: the sterile barrier system integrity evidence — distribution simulation (ISTA 3A or ASTM D4169), aging (ASTM F1980 accelerated plus real-time), and the integrity battery (ASTM F1886, F1929, F2096, F88, F1140). Part 2: the forming, sealing, and assembly process validation — the IQ/OQ/PQ of the sealing equipment, the defined process window, and the link between validated parameters and production. A file strong on Part 1 but silent on Part 2 is a recurring gap.
Present results so they map to criteria
Lay out the test results next to the acceptance criteria they satisfy, with traceability to sample IDs, timepoints, and the conditions each sample saw (sterilized, aged, distributed). Photographs for visual and dye-penetration results, and statistical summaries for seal strength and burst, let a reviewer verify the conclusion without reconstructing it. The sterilize-then-age-then-distribute sequence should be visible in the sample histories.
Close with the conclusion and revalidation triggers
End with a clear statement that the packaging system meets ISO 11607, the shelf-life claim it supports, and the conditions that would trigger revalidation — changes to materials, sealing process, sterilization modality, or shelf-life claim. This shows the validation is maintained, not one-and-done, which is exactly what an auditor wants to see.
The underlying principle
A reviewer-friendly DHF chapter is one where the strategy, protocol, and results tell a single continuous story with no gaps for the reader to fill in. Boulder Package Testing structures its reports to drop directly into this DHF format — protocol, traceable data, predefined criteria, and conclusion — so the testing is usable in a submission, not just technically complete.
Related Articles
Ready to Discuss Your Validation Project?
Boulder Package Testing executes ISO 11607-1/-2 validation programs co-located with EO and chlorine dioxide sterilization. Talk to us about your device.
Request a Quote