Communication Plan

profilemanijad5
Project_Managment_Plan_Template_for_PMGT_699_Coursehero1.docx

mImplementing Quality Management System in Pharmacovigilance

PMGT 699

Applied Project Management

Prepared By

Sakshi Vaidya

31-Mar-2019

1. Executive Summary

1.1 ..Introduction………………………………………………………………………

1.2 .. Purpose………………………………………………………………………….

1.3... Scope……………………………………………………………………………

2. Project Overview

2.1 Project Description

2.2 Problem Statement

2.3 Goals

2.4 Project Background

2.5 Product Objectives

2.6 ..Business Objectives……………………………………………………………..

2.7 ..Milestones……………………………………………………………………….

2.8 Assumptions, Constraints and Dependencies

2.9 Project Deliverables

2.10.. Project Success Criteria ………………………………………………………..

2.11..Schedule and Budget Summary

2.12..Evolution of the Plan

2.13 ..References

2.14 Definitions and Acronyms

3. Stakeholder Register

4. Schedule

4.1 ..Purpose/Overview………………………………………………………………..

4.2 ..Schedule Baseline……………………………………………………………….

4.3 .. Schedule Control…………………………………………………………………

5. Resource Plan

5.1 .. Overview/Purpose of the Resource Section ……………………………………

5.2 ..Resourcing Strategy & Assumptions….………………………………………….

5.3 .. Resourcing Development………………………………………………………..

6. Risk Management Plan

6.1 .. Purpose/Overview………………………………………………………………

6.2 .. Risk Identification………………………………………………………………

6.3 ..Risk Analysis……………………………………………………………………

6.4 Risk Monitoring Plan …………………………………………………………….

7. Communications Plan

7.1..Overview

7.2..Communication Message and Delivery

7.3..Communications Guidelines

7.4.. Escalation Process

8. Procurement

9. Cost

9.1.. Introduction

9.2.. Estimate Cost

9.3.. Contingency reserve project purpose or justification

9.4..Budget

9.5..Project and Monitoring

9.6.. Project Reports

9.7..Cost Change Control

9.8..Project Budget

9.9..Microsoft Performance Report #1

9.10..Microsoft Performance Report #2

10. Integrated Change Control

1.Executive Summary

1.1 Introduction

The development of medicinal products requires strict adherence to quality standards such as Good Pharmacovigilance Practices, FDA guidelines etc. to ensure that the content of clinical trial data captured in the database is an accurate reflection of the source document. The guidelines state that organizations should have quality objectives and methods of monitoring the efficient operation of the quality system. Currently the global pharmacovigilance systems in many companies are facing compliance issues with data entry and the adverse event case processing that follows data entry. It is important to manage the quality of the adverse event cases that are entered into the safety database as a single error in the entry or a coding error can have a cascading effect on the overall quality review of the case.

1.2 Purpose

Adverse event case processing (AER) is a complex process in pharmacovigilance that requires an effective project management team. Multiple functions in pharmacovigilance cause a bottleneck in adhering to the timelines of submission to the regulatory authorities even after having strict adherences to Standard Operating Procedures (SOPs).

The challenge is to establish a robust quality management system (QMS) to align with industry recommended standards and guidelines for Good Pharmacovigilance Practices. The key project deliverables will be to develop processes that allow effective demonstration of accuracy and consistency of the most important function of the Pharmacovigilance (PV) system - Data Entry (DE) and AER that follows DE. The project management plan will also focus on outlining processes for tools within the QMS that can differentiate between significant and non-significant risks that will impact the quality of a clinical trial and patient data.

1.3 Scope

The scope of the project is to:

· develop a quality management system using quality control methods as performance indicators to monitor the efficiency of the PV system,

· minimize risks of non-compliance for the company

· meet global regulatory requirements

2. Project Overview

2.1 Project Description

The basic need to develop a QMS within pharmacovigilance is to optimize the oversight and compliance of the process of receipt, review, assessment and reporting of adverse events to regulatory agencies from medicines and investigational drugs administered as part of post-marketing studies and different phases of clinical trials. A basic Plan-Do-Check-Act (PDCA) cycle will serve to design and build the processes, followed by training of staff on sub-processes, tools and metrics. A routine controls and measure check to review, improve and adopt any best practices will help increase effectiveness and efficacy of the system on a continuous basis.

2.2 Problem Statement

Implementation of an effective quality management system is the most important goal of a pharmaceutical industry. Requirements to implement a quality management system in pharmacovigilance have been defined by the US FDA and the EMA in the GVP (Good Pharmacovigilance Practices). Companies outsource data entry operations in pharmacovigilance to international contract research organizations to reduce cost and save time. This hampers the quality of data due to errors in data entry given the huge volume of data present in clinical trials. Lack of governance over data handling and monitoring are known to affect the quality of information present in the database.

2.3 Goals

The project is to introduce within the Pharmacovigilance (PV) department a Quality Management System (QMS). This will be a set of procedures either in the form of Standard Operating Procedures (SOPs) or other work instructions (WI) to carry out different processes of adverse event case management. It will also include Key Performance Indicators (KPIs) to monitor the overall performance of the system. The aim of establishing a QMS will be to introduce to the staff and auditors a reference standard for use and review.

2.4 Project Background

Non-compliance across a number of critical pharmacovigilance processes was one of the critical findings reported in the 2017/18 period of the Medicines & Healthcare products Regulatory Agency’s (MHRA) inspection. Late case submission of Individual Case Safety Reports (ICSRs) was one of them. A late submission of ICSRs to health authorities trickles down to the first step of adverse event reporting which starts from receiving the information about an adverse event. In order to comply with the regulatory requirements of having a QMS that will help identify non-compliance and effectively resolve it the project of establishing a QMS is being developed.

2.5 Product Objectives

· To improve compliance and reduce quality costs by streamlining the adverse event assessment and reporting cycle.

· Develop defined processes, detailed activities and tasks for case processing.

· Assess the existing systems and operations within the organization to increase quality and compliance.

· Identify the key performance indicators for each of the processes starting from receipt of data to reporting of adverse events to regulatory authorities

· Identify actions and deliverables for each process

· Develop best practices through continuous improvement

2.6 Assumptions, Constraints and Dependencies

Constraints:

· Outsourcing to a Contract Research Organization has the probability of compromising the quality of data entered in the safety database due to manual errors during data entry

· Insufficient guidelines around the expectations and requirements within a quality management system can be a challenge to build one

· Update to SOPs and WIs channeled without a defined QA&C process within pharmacovigilance

Assumptions:

· Triage of cases is evaluated into respective categories according to the industry defined standards of event seriousness

· 15 day “serious” reports that require submission to regulatory authorities have an additional review round before distribution

2.7 Project Deliverables

· Improve quality and compliance of adverse event reporting

· Achieve organizational goals

· Train all the employees on use of QMS

· Be a system to verify performance indicators to ensure organizational objective of compliance and continuous improvement.

2.8 Schedule and Budget Summary

No.

Schedule/Milestone Summary

Responsible Party

Date

1.

Review of industry standards, policies and procedures relevant to define and map a process

Director of Pharmacovigilance Office

4/30/2019

2.

Define quality policy and objectives

Director of Quality Assurance

5/31/2019

3.

Perform gap analysis of procedures relative to QMS

Manager, Quality Assurance & Compliance

7/31/2019

4.

Develop metrics to track and monitor safety data

Lead, Quality Assurance & Compliance

9/30/2019

5.

Implement UAT for the system

Safety System Supports Group

10/31/2019

6.

Determine Training module for Employees

Head of Training

11/30/2019

Budget Summary:

1. QMS system software costs - $500K

· Software license - $200K

· System implementation -$200K

· QMS design - $100K

2. Functional budget - $500K

· Templates/Forms/CAPA - $200K

· Quality workflow and gap analysis - $100K

· Functional trainings - $200K

3. Resourcing - $500K

· IT programmers - $300K

· Quality specialists - $200K

2.9 Evolution of the Plan

Non-compliance across a number of critical pharmacovigilance processes was one of the critical findings reported in the 2017/18 period of the Medicines & Healthcare products Regulatory Agency’s (MHRA) inspection. Late case submission of Individual Case Safety Reports (ICSRs) was one of them. A late submission of ICSRs to health authorities trickles down to the first step of adverse event reporting which starts from receiving the information about an adverse event. In order to comply with the regulatory requirements of having a QMS that will help identify non-compliance and effectively resolve it the project of establishing a QMS is being developed.

2.10 Definitions and Acronyms

Term/Abbreviation

Definition

AER

Adverse event case processing

DE

Data Entry

EMA

European Medicines Agency

FDA

Food and Drug Organization

GVP

Good Pharmacovigilance Practices

ICSR

Individual Case Safety Report

KPI

Key Performance Indicator

MHRA

Medicines & Healthcare products Regulatory Agency

PV

Pharmacovigilance System

Q A&C

Quality Assurance and Control

QMS

Quality Management System

SOP

Standard Operating Procedure

UAT

User Acceptance Test

US

United States

WI

Work Instruction

3.Stakeholder Register

4.Schedule Component

4.1 Purpose/Overview

The purpose of the schedule component is to provide a break-down structure of the tasks and activities scheduled for the project. The schedule will provide a defined work flow, timeline and set dependencies along with constraints for tasks that are broken down into smaller tasks under the umbrella of a few summary tasks like Project Management, Compliance monitoring etc. The schedule chart will provide a visual representation of the time span for the project and estimate the resources that will be required for each task.

4.2 Schedule Baseline

Tasks

Description

Creation of the Activity List and attributes

The project team comprising of the project manager and the key stakeholders for the project will provide a skeletal framework and contribute to ensuring all the required tasks are defined in the WBS.

Estimation of activity resources

The estimation of resource activity will be done by estimating the materials, equipment and human resources that will required to perform each of the activity listed in the WBS. For e.g. the project requires a software vendor for implementation of the system- this resource will have to be outsourced. This will have to be planned and taking into consideration the organizational policies on resource usage. Another area to consider with HR is to check which resources have the required skill set and historical knowledge to help complete the outlined tasks in the defined timelines. Based on the company policy, approval for the resources will be confirmed in long range planning

Activity duration estimates

An analogous method of estimation will be used to estimate the tasks and activities in this project. Knowledge on development on a QMS from the regulatory group will serve as guidance to carry forward the activity and develop a similar system within the pharmacovigilance group.

Approval of the schedule baseline

The Project Manager will approve the schedule baseline.

4.3. Schedule Control

The approved schedule baseline will be changed only through the formal change control process and only after the impact on the project constrains has been assessed.

Performance reviews

The schedule performance review will be done on a bi-weekly basis in the initial stages of the project. Once the project enters its maintenance phase the schedule will be reviewed on a monthly basis. An actual vs planned review system will be used to monitor the progress of the schedule. The individuals involved in the performance reviews will be the Project Manager; the System supports lead and the Director of quality assurance.

Schedule control thresholds

The acceptable variation from the schedule activities will be by 15%

Schedule performance reporting

The schedule performance will be provided to the key stakeholders of the project in the form of a project board which will have a high level of information as compared to the bi-weekly status reports for performance review. It will provide a summary of the current schedule and whether or not the project is in schedule to meet the key milestones.

5.Resource Plan with RACI

5.1Overview/Purpose

5.2 Resourcing Strategy & Assumption

[Define the resourcing strategy for the project. How will resources be acquired and released from the project?]

5.3 Resourcing Development

[When estimating the resources on the project, have you made any assumptions about those estimates?]

6.Risk Management Plan

6.1 Review of Risk Management Plan

6.2 Risk Identification

6.3 Risk Analysis

6.4 Risk Monitoring Plan

7.Communications Plan

7.1 Overview/Purpose

The purpose of the communication plan is to ensure the Project Management Improvement Project provides relevant, accurate, and consistent project information to project stakeholders and other appropriate audiences. By effectively communicating the project can accomplish its work with the support and cooperation of each stakeholder group.

The communication plan provides a framework to manage and coordinate the wide variety of communications that take place during the project. The communication plan covers who will receive the communications, how the communications will be delivered, what information will be communicated, who communicates, and the frequency of the communications.

The following outlines the targeted audiences, the key communication messages to be delivered, and the method for delivering the information, the communicator, and the frequency of the delivery.

7.2 Communication Message and Delivery (Matrix)

Audience

Message

Delivery Method

Delivery Frequency

Communicator

Example: Project Sponsor

Project Plans

Status Reports

Meeting

Report published in My Web space with DoITnet and PSST link

Weekly

Biweekly

Project Manager

Project Manager

7.3 Communications Guidelines

Communication Guidelines—E-mail, Text:

1) Do not use reply all to emails

2)

3)

4)

5)

6)

Communication Guidelines—Meetings:

1) Meetings must have pre-published agendas, prior to meeting request…agenda must accompany the OUTLOOK meeting request

2)

3)

4)

5)

.

7.4 Escalation Process

8. Procurement

9. Cost

9.1 Introduction

[The purpose of this document is to provide general content of a Cost Management Plan and to describe submission required in Microsoft Project format (.mpp file).]

Cost Management Plan

[A cost management Plan defines cost baseline, modifies it whenever necessary, and uses it for monitoring and controlling cost. A project cost management plan generally includes descriptions, procedures and responsibilities for items such as Costs included, activity resource estimating, cost estimating, cost baseline, budget determination and cost control.]

9.2 Estimate Cost

[Estimate Cost is a process of developing an approximation of monetary resources needed to complete project activities.]

9.3 Contingency Reserve Project Purpose or Justification

[Contingency reserve is money assigned to the project and allocated for identified risks for which contingent responses are developed. Generally, how much money is reserved and its rationale are included here.]

9.4 Budget

[Once the project costs or cost baseline is determined, a time-phased project budget is developed. Project budget shows how the project cost will be incurred by appropriate periods (months, weeks, quarter, etc.) during project performance period. Describe how your budget is developed.]

Cost Control and Monitoring

[The approved project budget with contingency reserves serves as a baseline for project control. This section usually include project approach to monitor actual versus planned performance, approach ( e.g. Earned Value analysis), and how any cost changes will be managed.]

9.5 Performance Monitoring

[Describe your approach to monitor planned versus actual performance and matrices that will be used]

9.6 Project Reports

[Include name and description of 2 to 3 reports that you plan to use for performance monitoring, status reporting or other reports. These are the reports for which you will be submitting a Microsoft Project mpp file. See section below. ]

9.7 Cost Change Control

[Describe briefly how any changes to the cost baseline will be administered and implemented.]

Microsoft Project Deliverables

9.8 Project Budget

[Include your project WBS (in .mpp format) that represents your project cost. Ensure that contingency reserves as a separate line item. The report submission is in Moodle]

9.9 Microsoft Performance Report

[Include report name and describe how the report will be used]

9.10 Microsoft Performance Report

[Include report name and describe how the report will be used]

Example – Communications Plan v1.0.1 Page 6

10. Integrated Change Control

Stakeholder

Register.docx

Stakeholder

Role

Responsibility

Amount of Influence

Impacted by

Notes

Kostas Kidos

VP, Safety Operations and Compliance

Project Sponsor

High

Success of the project

Christy Cole

Director of Quality Assurance

Subject Matter Expert

High

Milestone completion

Allison McCarthy

Manager, Quality Compliance & Assurance

Subject Matter Expert

High

Milestone completion

Sakshi Vaidya

Manager, Safety Operations

Project Manager

High

Project completion and delivery

Gary Sands

Safety Support Lead

UAT testing and validation

High

Milestone completion

Peggie Fraser

Service Provider

Software developer

High

Milestone completion

Linda Curtin

Training Lead

Creation of training manuals

Medium

Milestone status