09.07.2015 Views

guidelines on variations to a registered pharmaceutical product

guidelines on variations to a registered pharmaceutical product

guidelines on variations to a registered pharmaceutical product

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Guidelines <strong>on</strong> Variati<strong>on</strong>s <strong>to</strong> a Registered Pharmaceutical ProductMarketing Authorizati<strong>on</strong> of a Pharmaceutical Product for Human Use and itsannexes (Document No. DAR/GDL/005), and Guidelines for registrati<strong>on</strong> ofVeterinary Pharmaceutical Products (August 2001).This guidance document is applicable <strong>on</strong>ly <strong>to</strong> APIs and excipients manufacturedby chemical synthesis or semi-synthetic processes and FPPs c<strong>on</strong>taining suchAPIs and excipients. APIs from fermentati<strong>on</strong>, biological, biotechnological orherbal origin are treated as special cases. The applicant is requested <strong>to</strong> c<strong>on</strong>tactNDA regarding planned variati<strong>on</strong>s <strong>to</strong> such <strong>product</strong>s.The notificati<strong>on</strong> requirements for API-related changes differ depending <strong>on</strong> themanner in which API informati<strong>on</strong> was submitted with the original FPP applicati<strong>on</strong>,namely: use of a WHO prequalified API, use of a European PharmacopoeiaCertificate of Suitability (CEP), or as provided in full within the dossier.The c<strong>on</strong>diti<strong>on</strong>s and documentati<strong>on</strong> stipulated in this guideline for API-relatedvariati<strong>on</strong>s focus primarily <strong>on</strong> those FPPs that relied up<strong>on</strong> the provisi<strong>on</strong> of fullAPI informati<strong>on</strong> within the FPP dossier. When an FPP relies up<strong>on</strong> a CEP ora prequalified API, FPP applicants are required <strong>to</strong> notify NDA <strong>on</strong>ly when theassociated CEP or C<strong>on</strong>firmati<strong>on</strong> of API Prequalificati<strong>on</strong> document has beenrevised.Whenever FPPs have been <strong>registered</strong> <strong>on</strong> the basis of approval by a stringentregula<strong>to</strong>ry authority (SRA) (innova<strong>to</strong>r <strong>product</strong>s or generic <strong>product</strong>s) or WHOprequalificati<strong>on</strong>, subsequent applicati<strong>on</strong>s for variati<strong>on</strong>s should also be approvedby the same SRA and WHO PQP, and NDA should be notified of the approvalof the changes.When a variati<strong>on</strong> leads <strong>to</strong> a revisi<strong>on</strong> of the summary of <strong>product</strong> characteristics(SmPC), patient informati<strong>on</strong> leaflet (PIL), labelling and packaging leaflet,updated <strong>product</strong> informati<strong>on</strong> has <strong>to</strong> be submitted as part of the applicati<strong>on</strong>.For variati<strong>on</strong>s that require generati<strong>on</strong> of stability data <strong>on</strong> the API or FPP, thestability studies required, including commitment batches should always bec<strong>on</strong>tinued <strong>to</strong> cover the currently accepted retest or shelf-life period. NDA shouldbe informed immediately if any problems with the stability appear during s<strong>to</strong>rage,e.g. if outside specificati<strong>on</strong> or potentially outside specificati<strong>on</strong>.Applicants should be aware that some variati<strong>on</strong>s may require the submissi<strong>on</strong>of additi<strong>on</strong>al c<strong>on</strong>sequential variati<strong>on</strong>s. Therefore, for any given change theapplicant should c<strong>on</strong>sider if <strong>on</strong>e or more variati<strong>on</strong>s may be required <strong>to</strong> besubmitted.Doc. No.: DAR/GDL/005 Revisi<strong>on</strong> Date: 8 th July 2013 Review Due Date: 16 th July 2016Revisi<strong>on</strong> No.: 1 Effective Date : 16 th July 2013 Page 4 of 70

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!