Milestones and Regulatory MilestonesThe submission process includes a phase for completing the internal tasks to create, review, and approve all of the documents that comprise the submission dossier. After the dossier is complete and delivered to the regulatory authority, another phase occurs dictated by the regulatory authority. That phase includes milestones and phases that support the review process, including any question-and-answer (Interactive Review) phases, and ends with market authorization for the product. This phase of the submission is called the regulatory calendar, and is typically defined in theregulatory guidelines for a specific combination of regulatory context (regulatory context, regulatory context, and regulatory context) and the regulatory context (such as Initial Submission or Renewal). The Schedule page for a submission lets you track both phases in one place. Use a Milestone task (Market Registration adds a milestone purpose attribute to the standard milestone type) during the dossier preparation phase. Use a Regulatory Milestone task during the Regulatory Calendar phase. The Regulatory Information page tab of the Regulatory Information category for a submission lists all milestones that have a purpose defined. When you create a submission project, Market Registration automatically creates these milestones in the schedule:
Do not delete these milestones. You need to complete each milestone before you can complete the next one. For example, you cannot mark the Dossier Submitted milestone complete if the Dossier Ready milestone is still in process. For the regulatory calendar, you can define milestones with these milestone purposes:
If you add milestones directly to the schedule, you need to edit the properties for the milestone to set the purpose. If you use the > Add Subtask Below commands, you can set the milestone purpose in the create dialog box. orMilestones can be defined in a submission template or a regulatory calendar template to be used by submission projects. For a milestone defined in a submission template, only a Regulatory Administrator or the owner of the submission template can edit the milestone purpose. For a milestone defined in a submission, only a Regulatory Lead or the owner of the submission project can edit this attribute. Regulatory Milestone ChecklistsChecklists can be defined for regulatory milestone tasks to track when the milestone is complete. You can define checklists in the context of a submission template or a submission project. One checklist might contain checklist items required for a pre-submission meeting (a milestone). Another checklist could contain checklist items for an investigation plan. The checklist allows you to create a list of all the prerequisites that must be complete for that milestone to be considered complete. The checklist items themselves vary depending on the type of submission, the requirements for that type of submission from that specific regulatory authority, and the country in which authorization is being requested. When working with submission templates and submission projects, checklist items act as prerequisites. For each milestone in the submission schedule, you can associate one or more checklists. When a submission is created based on that template, all checklists for all milestones are copied to the individual submission project. The Regulatory Lead who owns the submission can define additional checklists and checklist items as needed for the specific circumstances of that project. When you define a checklist item, you specify what type of response is required: Yes or No, for example. You edit the Checklists page for the regulatory milestone to enter the response. To promote a milestone to the Complete state, all checklists for that milestone must be completed. To complete a checklist, each checklist item must have a response. The valid responses are determined when the checklist item was created. See the checklist topics in Project Management User's Guide: Working With Gates for general information. See Working with Checklists for Milestones for information on using checklists with regulatory milestones. TasksEach task is designed to deliver a document. You can add tasks to an inactive submission (on hold), but you cannot add tasks to a cancelled submission. When creating a task for a submission project, you choose whether the task must be reviewed. The Needs Review attribute can be set to Yes or No. If you choose Yes, then when the person assigned to this task promotes it from Active to Review, the app automatically creates a review route with the submission owner assigned an approval task. Tasks that require review show the Each task, and its deliverable, can also be associated with a volume. You can select a volume for any type of task (task, phase, gate, interactive review, or review question) but not for a milestone. The Schedule page must be in edit mode to assign tasks to volumes. To submit the deliverable, you can use the file tools on any of these pages:
You can click the name of any task to view additional details, such as deliverables, assignees, risks, or routes associated with that task. The Deliverables page for a task includes the If the higher revision was also added to the task, then this icon is informative. If not, you can click |