Global Regulatory Monitor
Regulatory News, Week 5 · 2026/8

Rating cleaning validation as critical and then bundling container closure integrity, aseptic process simulation and process validation into a non-compliance statement shows sterile sites being judged on the whole of their sterility assurance system rather than on isolated findings. Quality and regulatory teams running or outsourcing sterile manufacture should check whether cleaning validation and container closure integrity testing are sitting as long-standing open findings, and whether the correction history is documented.

Suspending manufacture because product was shipped again on the view that filing the completion report ended the recall confirms that it is the regulator, not the recall obligor, that decides when a recall closes. Teams running recalls should confirm that the affected lots stay locked in a shipment hold until the written notice from the competent regional office is in hand.

Grading the suitability of the microbial limit test method as major in a pre-approval inspection of an overseas site shows that the validity of the method used to judge a specification is examined alongside the specification itself. Quality teams sourcing finished product from overseas sites should confirm that method suitability data, microbial limit testing included, is in place before the inspection rather than after it.

Treating a contract manufacturer's failure to follow its own standard as a breach of contract management responsibility, and carrying it through to a surcharge in place of a dosage form suspension, signals that a loss of contemporaneity in records is read as a failure of manufacturing control rather than a documentation defect. Quality teams manufacturing through contract arrangements should look at whether they verify contemporaneous completion of the contractor's manufacturing instruction and record on the floor, not by collecting paperwork afterwards.

Consecutive findings that the quality system, cleaning and disinfection, and computerised systems could not be found in the site master file show the master file being treated as the entry point to an inspection rather than as a formality. Quality teams that own the site master file should confirm it is kept current against how the site actually operates.

Publishing the result confirms that the same split applies throughout, with critical and major deficiencies going to administrative action and other deficiencies to correction. Quality teams that carry this site as a supplier should read the deficiency grades and follow-up status from the published inspection result itself.

Asking for legacy systems whose data integrity cannot be assured to be managed through risk assessment, in the same inspection as findings on retention and functional verification of automated records, shows an approach that demands documented control where replacing the equipment is not practical. Quality teams running ageing equipment should check that the risk assessment, the compensating controls and the rationale for cleaning validation sampling locations exist on paper.

Publication of an API site's post-approval inspection confirms the same structure, where a critical or major grade goes to administrative action and other findings go to correction. Quality teams buying active ingredients should confirm that the inspection outcome, deficiency grades and follow-up status are recorded in supplier management, and read the published inspection result for the detail of individual findings.

A quality management finding at an API site shows that the same quality system expectations applied to finished product sites are being applied upstream. Quality teams managing API suppliers should confirm that the remediation plan and closure of quality management findings feed into the supplier requalification cycle.

Raising the level of detail in batch records and the data integrity of legacy systems in the same inspection shows the completeness of the record and the trustworthiness of the system being treated as one axis. Quality teams that own manufacturing records should check that the record format follows the actual sequence and granularity of the operating procedure, and that a control plan exists for legacy systems.

Publishing an API inspection that closed without a single deficiency shows that results are disclosed regardless of whether findings were raised. Quality teams assessing API suppliers should confirm they also collect and retain clean inspection outcomes as evidence supporting supplier qualification.

A recall triggered by the product name being wrong on one panel only, while the front panel is correct, shows that a labelling error confined to a single face is still enough to bring product back from the market. Quality teams that manage packaging artwork should confirm that proofing and approval compare against every face of the print layout, not only the front.

A product presented as herbal in which a prescription drug ingredient was detected, escalating to the highest risk class, shows that the recall class follows what is actually found rather than what the label declares. Quality teams handling botanical and herbal materials should confirm that the possibility of undeclared synthetic adulterants is captured as a test in the supply chain.

A mandatory recall on the acid-insoluble ash test alone shows that a purity indicator is not a secondary specification but can trigger a recall on its own. Acid-insoluble ash is generally associated with soil and foreign matter carried in with the material, so quality teams handling crude drugs should look at whether the test is performed at goods receipt and at how the supplier is managed.

A mandatory recall of a herbal preparation on the ground of sulfur dioxide shows that residues entering at the material stage lead straight to a recall, not only the finished product specification. Sulfur dioxide is generally associated with treatments used in drying and storage of crude drugs, so quality teams should confirm the supplier's processing history and the sulfur dioxide test applied at goods receipt.

A mandatory recall on the description test alone shows that sensory and appearance specifications are not supporting attributes but stand on their own as grounds for recall. Quality teams handling crude drugs should confirm that the acceptance criteria for description, the training of the people who judge it and the records of their judgement match the specification document.

Naming the individual pesticide in a mandatory recall of a herbal product shows pesticide control narrowing from a total-residue concept to the level of the individual substance. Quality teams handling crude drug materials should confirm that the cultivation history of each supplier and the range of individual pesticides tested for meet the specification.

Naming cadmium specifically in a mandatory recall shows heavy metal specifications being managed and applied element by element rather than as a total. Cadmium is generally associated with the soil the material was grown in, so quality teams handling crude drugs should confirm the heavy metal testing history by growing region and the criteria used to manage suppliers.

Handling an incorrect dose display on an injection as a product quality recall shows that on a combination product a defect in the display is treated as a quality defect in its own right. Quality teams working with injector-combined products should confirm that inspection of the display is part of finished product release testing.

An impurity out of specification in a peptide injection leading to a product quality recall shows specification failures found after release still being carried through to the market. Quality teams working with peptide preparations should confirm the basis on which impurity specifications were set, and whether an out-of-specification result during stability testing triggers review of batches already released.