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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Guidelines <strong>on</strong> Variati<strong>on</strong>s <strong>to</strong> a Registered Pharmaceutical Product4. GUIDANCE FOR IMPLEMENTATION4.1 Reporting typesThe definiti<strong>on</strong>s outlined in the following reporting types are intended <strong>to</strong> provideguidance with respect <strong>to</strong> the classificati<strong>on</strong> of administrative, quality, safetyand efficacy -related changes. Specific change examples are provided in thisguideline. However, it is <strong>to</strong> be noted that a change not cited in this guideline,should be c<strong>on</strong>sidered as a major change by default. Whenever the applicant isunclear about the classificati<strong>on</strong> of a particular change, NDA should be c<strong>on</strong>tacted.It remains the resp<strong>on</strong>sibility of the applicant <strong>to</strong> submit relevant documentati<strong>on</strong> <strong>to</strong>justify that the change will not have a negative impact <strong>on</strong> the quality, safety andefficacy of the <strong>product</strong>.Individual changes normally require the submissi<strong>on</strong> of separatevariati<strong>on</strong>s. Grouping of variati<strong>on</strong>s is acceptable <strong>on</strong>ly when variati<strong>on</strong>s arec<strong>on</strong>sequential <strong>to</strong> each other, e.g. introducti<strong>on</strong> of a new impurity specificati<strong>on</strong>that requires a new analytical procedureFor the purpose of classificati<strong>on</strong>, an applicati<strong>on</strong> involving two or more types ofvariati<strong>on</strong>s will be c<strong>on</strong>sidered as the highest risk type, e.g. a variati<strong>on</strong> groupingboth a minor change and a major change will be classified as a major change.Applicants are also advised <strong>to</strong> exercise cauti<strong>on</strong> whenever several changes <strong>to</strong>the same FPP are envisaged. Although individual changes may be classifiedas a particular reporting type, classificati<strong>on</strong> at a higher risk category may bewarranted as a result of the composite effect of these changes. In all suchcases, applicants are advised <strong>to</strong> c<strong>on</strong>tact NDA prior <strong>to</strong> submissi<strong>on</strong> of the variati<strong>on</strong>applicati<strong>on</strong> in order <strong>to</strong> obtain guidance in classifying such changes.4.2 Notificati<strong>on</strong>sNotificati<strong>on</strong>s are changes that could have minimal or no adverse effects <strong>on</strong> theoverall safety, efficacy and quality of the FPP. Such notificati<strong>on</strong>s do not requireprior acceptance, but must be notified <strong>to</strong> NDA immediately after implementati<strong>on</strong>(immediate notificati<strong>on</strong> (IN)), or within 12 m<strong>on</strong>ths following implementati<strong>on</strong>(annual notificati<strong>on</strong> (AN)) of the change.It should be highlighted that an IN or AN may be rejected in specific circumstanceswith the c<strong>on</strong>sequence that the applicant must cease <strong>to</strong> apply the alreadyimplemented variati<strong>on</strong>.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 9 of 70

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

Saved successfully!

Ooh no, something went wrong!