- Risk management for IT-supported applications
- Risk management of spongiform encephalopathies to our API and products
- Safety risk assessments
- Testing activities conducted at contract facilities
- Testing of research materials.
Roles |
Responsibilities |
Management |
|
Quality Unit |
|
Personnel |
|
- The principles of QRM in the preparation of medicinal products are described in ICH Guidance for Industry Q9 -Quality Risk Management. In alignment with ICH Q9 recommendations, this QRM plan is built around the following steps: Risk Assessment, Control, Communication and Review.
- QRM is a critical component of quality systems and feeds from the investigations and inspections program and is leveraged to guide change management. Risk management is implemented with practices appropriate to the stage of project development.
- ICH Q9 defines risk as to the combination of the probability of occurrence of harm and the severity of that harm for the intended patients. As an organization developing analytical knowledge and methods, another fitting definition for risk is that of the ISO 31000 Risk Management Standard which defines risk as uncertainty in reaching objectives. This QRM intends to both address potential harm to patients and uncertainty in objectives. The primary focus of risk management is to control the risk to data on product attributes, as this data is used to both determine the suitability of products for clinical programs and to propose specifications utilized in the evaluation of manufacturing process control. Other objectives include accurate data for the proposal of labeling information; development and validation of robust methods, and testing in support of manufacturing activities (e.g., water testing).
- Risks are proactively identified in deliverables by conducting risk assessments to the type of tests that evaluate product quality attributes used in the decision for batch release. Failure modes are identified by experts in the technique and ranked. Multiple sources are used for further identification of risks to be evaluated as well as to trigger a review of processes for risk assessment. These sources include Quality Unit and regulatory inspections, benchmarking, internal self-inspections, investigations on operational alerts, and trend evaluations. These risks are analyzed and evaluated for inclusion in the Risk Register.
- Multiple tools will be used for the estimate of risk posed by the hazards identified. Subject matter experts will consider the risk to be evaluated and select a tool appropriate to the complexity of the system or activity under evaluation. Informal risk management may be used, including empirical evaluations where appropriate, flow charts, checklists and procedures.
- For the analysis and evaluation of data for batch release, Failure Mode and Effect Analysis was chosen as it can guide the evaluation of numerous failure modes, summarizing the effect and quantitative ranking for guiding control efforts. For the FMEA risk analysis of tests for the release testing activity, the table presented below outlines the starting point. A team using this tool can further refine this table to suit the risk question and should capture the analysis table in the documentation of the risk assessment.
Score |
SEVERITY |
OCCURRENCE |
DETECTION |
10 |
Passing
a failing product can result in the release of an adulterated product |
Frequent |
Cannot be detected |
7 |
Not
used to ensure the assessment of severity is most conservative.* |
Moderate, occasional |
Very Low |
3 |
The additional introduction of error, expands the uncertainty of the method while still
meeting specification |
Infrequent or has occurred ** |
Moderate |
1 |
Data
representative of product attribute |
Remote or unlikely |
Almost Certain |
- Each failure mode is assigned a Risk Priority Number
- The purpose of a risk management program is to decide, for the hazards identified, what controls are possible and when they should be sought and implemented. Evaluation of risk controls will consider the following questions:
- Is the risk currently managed at an acceptable level?
- What can be done to reduce or eliminate the risk?
- Is there other data that helps manage the process, and evaluation and can be used in place of a control?
- What is the appropriate balance among benefits, risks, and resources?
- Does implementation of the control introduce new risks?
Final Risk Level |
Decision Guidance |
High |
Risk
is unacceptable and action to reduce risk is required. Design
New Controls: Actively
work to mitigate these through design, systems, procedures and other
controls. |
Medium |
The decision required accepting risk
or taking action to reduce risk. Take action: If
detectability of risk is poor (e.g, 7-10), consider whether action is
required and seek to develop a clear understanding on how to recognize when
this failure mode occurs. An action might include awareness/training or the development of new controls. Observe/Accept:
If detectability of risk is good (e.g., 1-3) or severity is low (1-3),
maintain vigilance (operational alerts program). |
Low |
Residual
risk is acceptable, the risk is detectable and of low severity, and no further action
is required. Knowledge of the actual process is well
understood. |
- The goal of risk communication is to, by way of sharing information on risks identified and their controls, increase risk awareness and promote controls that support quality. This means that personnel in different roles have different needs regarding the communication of risk.
- Personnel conducting activities will need to be informed of risks so that they maintain behaviors that support best practices sustain vigilance and understand processes to help control risk. These communications are achieved through training, method details, formal procedures, and aides such as checklists to enhance their ability to control risk. Management is responsible to allocate resources for activities; therefore, they must support the identification of risks and stay informed of risks that require additional controls.
- Management is also responsible to commit resources to the development of those controls or accept residual risk. This communication will be achieved and documented through their approval of plans, procedures, formal change controls, and the risk register.
- Formal documentation of risk assessment and other risk management activities will be at the discretion of management and the Quality Unit observing the guiding principle of documentation effort commensurate with the impact of the risk. Formal risks assessments will utilize a template that will include the following elements:
- Contain a unique number
- Define the risk assessment method /tool and rationale for selection
- Conducted by appropriately trained personnel
- Discuss controls and risk acceptance (if appropriate)
- Define periodic review cycle
- Include approval by the Quality Unit when analyzing a process for purpose of a buildup of the risk register or used to justify changes to procedures.
- Low-impact risk assessments for easily understood or specific situations/processes may be analyzed and documented by an SME. These will be managed informally, documented in the process tools (e.g. TrackWise record, instrument qualification document, notebook record), or incorporated into a procedure
- A risk register(s) will be maintained to be comprised of a ranking of risks identified through risk assessment of the major deliverables and processes. The Business Unit and the Quality Unit will review the risks identified and decide which risks should be managed through the risk register based on the potential impact on patients and the quality of deliverables.
- Each risk listed in the register will:
- SEQUENTIAL NUMBER / SITE
- SEQUENTIAL NUMBER = 1, 2, 3 etc (individual risk within the risk assessment)
- It is intended that the register will list high risks and can include medium risks agreed upon during the review as requiring remediation.
- The risk register will be approved by Management and the Quality Unit.
- To remain effective, the risk register review will consider the impact of trends in quality events, change controls, and lessons learned from audits/inspections, and its review documented at a minimum once every 3 years. This review will also document the removal of risk from the register due to risk reassessment.
0 Comments