Guidelines For Validation
Guidelines For Validation
Introduction
This is a general guideline aimed at providing RGL with a practical framework for the
introduction or use of any new or change of established processes, equipment, facilities or
systems. The following areas are covered in detail:
Change Control - a formal system for managing proposed or actual change
Validation - documented evidence that the requirements for a specified intended use
or application have been fulfilled i.e. a collection and evaluation of data from the
process design stage through to production which establishes evidence that the
process is capable of consistently delivering the required quality. It is about gaining
knowledge and an understanding of the product/process. This is generally the pre-
purchasing stage and provides assurance that product meets the needs of
stakeholders.
Verification – documented evidence that specified requirements have been fulfilled
i.e. a collection and evaluation of data from production through to implementation,
which establishes evidence that the process is in reality consistently delivering the
required quality. In some quality standards this equates to Process Qualification.
It is the intention of RGL to maintain critical processes and systems in the intended state for
which they were developed and which are in line with regulations, standards and guidelines
that underpin the quality management system.
For this reason, the RGL should:
understand the process variations
detect these process variations and assess their extent
understand the influences on the process
and control such variations depending on the risk they represent
It’s important to remember that a sound understanding of the process will not inherently lead
to a safe process. The validation and verification process needs to include evaluation of
materials, equipment, the environment, and personnel changes to ensure the process can
be maintained when in routine operation.
Change Control
Any new or changed process, equipment, facilities and systems must be through the change
control process. Uncontrolled change carries significant risk of loss of the validated state for
laboratory processes, equipment, facilities or systems. Requests for change may arise from:
Planned change as a result of opportunities
Review of current procedure
Audit findings
Incidents
Complaints
Some laboratory changes may result of using new equipment of the same type or a
relocation of the process in which case the validation may be limited but must still be
documented.
Minor changes or amendments to documented procedures may not need to go through this
process, but will still be managed via the document control procedure.
Specification
A documented specification is an essential document and should take account of the
opinions of all stakeholders. It needs to be produced before the purchase of equipment. The
specification needs to include:
Purpose for which the new process, equipment, facilities or systems are required.
Also Include stakeholder requirements
Describe essential and desirable requirements and functions
Define the operating environment in which the system will operate to ensure staff
safety
Define other requirements such as consumables, time/staff resources (inc. training)
and maintenance schedules and compliance with regulations and standards e.g.
EQA, UKAS, HTA.
Procurement
RGL will comply with the following trust and RGL Policy and Procedures:
Trust ICT Procurement Policy
Trust Standards of Business Conduct
RGL Equipment Management Guidelines (Equip 1)
A summary report will be written detailing the outcome of the validation process and decision
to purchase will be made authorised and recorded.
Following purchase the plan needs to be extended to plan the initial verification
implementation and on-going verification phases.
Once all the SOPs, training and records are in place the new process can be authorised for
use. A summary report (see Appendix 1) will be written detailing the outcome of the
verification process will submitted and authorised and recorded.
Final authorisation before implementation will be made by the appropriate Consultant
Clinical Scientist.
Reports must draw a clear conclusion as to whether or not the process is for purpose and
approved for use. It should also state any limitations and Uncertainty of Measurement (see
Process for assigning Uncertainty of Measurement)
Implementation
All documentation should be kept for a minimum of 11 years or the lifetime of the process,
equipment, facilities or system.
SOPs and record templates must be written and authorised immediately prior to the change
being made.
All staff involved in using the equipment must be trained before using the new process.
Training and competency records will be completed and records kept.
Once implemented considerations should be made and documented as to how the new
process will be maintained as intended.
On-going Verification
There needs to be a periodic review of trends in process and maintenance data when in
routine use. Unplanned process variations i.e. errors and incidents need to be reported and
prioritised and resolved, with regular review, until the new process has become established.
The trends in process data will establish the capability of the process and can be used for
future monitoring. The aim is to improve the process; however improvements need to be
made in a structured way in line with these guidelines.
Appendix I: Change request pro-forma
This form is intended for identifying and collating proposed changes in service affecting
processes, systems or equipment, in order to manage the change process to ensure all
documentation is completed in accordance with the ISO15189:2012 standard.
This form should be completed prior to any significant detailed investigation into the change
to ensure the utility of investigating the change request, in order to minimise any
unnecessary use of resource. More importantly, the completion of this form ensures that
any proposed change follows the specific validation/verification procedures required by the
RGL for compliance with the ISO standard 15189:2012.
1. Section 1.1 should be completed as far as possible to establish the goals of the change
request.
There needs to be sufficient information to enable the authoriser to make a judgment
as to whether to proceed with the proposal or not.
2. Section 1.2 should be completed by the appropriate senior scientist in order to initiate
further detailed investigation of the change request.
The authoriser needs to decide whether a full business case is required and what
detail is expected within this case.
In the case of new equipment being required, the authoriser will need to request
whether a capital (>£5k) or non-capital business case is submitted through the
appropriate channel.
3. Section 1.3 will be completed once the business case has been submitted to the
appropriate persons for detailed consideration. This will be dependent on the type of
change requested and the potential associated cost. Once authorised the full
validation/verification procedure will be implemented.
Authorisation level will depend on the associated cost and impact of the change.
1. Change Request Details
Request name Internal descriptive name Reference Internal ref.
Description of Outline the change being requested and the reasons why this action is
change request required.
Process/ System/
Specify whether this is a change to a process, system or equipment.
Equipment
List any benefit to introducing this change, e.g. improved testing, better
Benefit results, streamlining, quality improvement, reduction in labour/consumable
cost, improved TAT
List any relevant documentation both internal and external indicating the
References derivation of the test and including performance specifications, publications
and any previous validations
Rejected
Lead
Authoriser
1.3 Change request outcome
Approved
Rejected
Authoriser
Appendix II: Generic validation/verification pro-forma
This form is intended as a guide to aid the department in developing a suitable validation/
verification procedure. A suggested methodology for using the form has been given below.
1. Section 1 should be completed as far as possible to establish the goals and general
format of the validation/verification.
Sections 1.1 “Intended use or application” and 1.2 “Requirements” must be
completed at the start of the procedure. The assessment of the validation/verification
depends formally on the confirmation, through the provision of objective evidence,
that these requirements have been fulfilled.
If mentioned (1.2), the “Expected Performance” should be distinguished from the
“Requirements”, which must be shown to have been fulfilled.
o Example: the statement “should detect all known point mutations of hemophilia A”
could be included as a guide in the Expected performance; if it were stated as a
requirement, it would need to be proven!
2. Section 2 covers the validation of the new system which should be carried out for all
validations and verifications. In the majority of cases this section can be completed on
objective evidence from publications, developmental work, design procedures (e.g. SNP
checking primers) or by the use of limitations or controls in the on-going test. Where this
is not the case, work plans for relevant parameters should be prepared as in 3 below.
3. Appropriate parameters for experimental investigation should be identified with the aid of
appendix A – a checklist is also provided at the top of section 3. For each parameter
required, the investigating scientist develops a work plan based on section 3 (these are
referenced 3.1, 3.2 to 3.n) by completing copies of sections 3.n.1 (‘Aims’, ‘Samples’ and
‘Methodology’). It is suggested that these be maintained in a single document.
Note: several parameters may be tested in a single experiment, for example sensitivity
and specificity.
4. The work plan[s] should be agreed and authorised by the investigator and the senior
scientist/Authoriser by signing and dating in the boxes provided.
5. The experimental work is performed and analysed by the investigator who should then
complete the ‘experimental results’ and ‘interpretation’ sections 3.n.2.
6. The ‘outcome and limitations’ should be agreed between the investigating and senior
scientists by signing and dating in the boxes provided.
8. If there is any non-compliance between the experimental results and the required
performance specification detailed in section 1.2 the parameter in question should to be
re-examined to determine if the methodology can be changed or new limitations
introduced to rectify the non-compliance. Any further work should be recorded in a new
section 3 work plan. Alternatively the implementation can be abandoned.
9. Once all the parameters have been satisfactorily investigated the investigating and
senior scientist can agree and sign off the final conclusions in section 4.
10. Assuming the validation / verification has been completed satisfactorily an independent
review can be performed and the whole process signed-off in section 5 by a Consultant
Scientist.
1. Validation / Verification (delete as appropriate) Details
Intended use or Outline the intended results of the test and how they will be used including
application any interpretative considerations; linked to 1.2 Performance Requirements.
Locus / Gene /
Specify analyte[s]
Marker
Reference
e.g. NCBI accession number
Sequence
Outline
Describe the technology and how it will be employed
methodology
List any relevant documentation both internal and external indicating the
References derivation of the test and including performance specifications, publications
and any previous validations
Validation / State whether the study is a validation or verification and the justification for
Verification this course of action.
Other List any other factors that may affect the utility of the test for the intended
considerations purpose. Expected performance can be mentioned here.
2. Validation of new system
Applicability of Is what is being tested appropriate and sufficient to achieve the desired
measurements results? Compared with specification.
Detail any test specific selectivity issues together with limitations and/or
control measures taken to ensure test utility. A validation work plan (section
Selectivity
3) should be drawn up for any specific potential selectivity issues that
cannot be eliminated by limitation or control measure[s].
Detail any test specific interference factors together with limitations and/or
control measures taken to ensure test utility. A validation work plan (section
Interferences
3) should be drawn up for any specific potential interference that cannot be
eliminated by limitation or control measure[s].
Investigator
Authoriser
3.n Validation / Verification (delete as appropriate) for [insert parameter]
Limit of
Sensitivity Accuracy Trueness Cut-offs
detection
Section aims Describe the specific aims of this section of the validation
Investigator
Authoriser
State whether the results fulfil the validation requirements listed in 1.2
Outcome /
List any specific derived limitations to reproduce the outcome (e.g.
limitations controls and how they should be used)
Investigator
Authoriser
4. Validation / Verification (delete as appropriate) Final Conclusions
Estimates of
Give experimentally-derived values for the relevant metrics.
accuracy and
Comment on the potential influence of the uncertainty on the reliability
measures of
of the result.
uncertainty
Limitations and/or
List all limitations and control measures required to maintain the on-
predictable
going test performance
interferences
Investigator
Authoriser
5. Implementation
Training
Competence assessment
Report template
Subscribe to EQA
Update website
Billing procedure
LIMS functionality
Qualitative tests where the true Genotyping for the presence or absence of a
To establish correction
E quantitative signal can only have one
of two possible values
specific mutation (e.g. F508del in CF or
C282Y in hemochromatosis).
++ ++ + factors and/or cut-offs ++ +
Legend Notes
1. Sensitivity = True Positive / (True Positive + False Negative)
Metric used for implementation validation
2. Specificity = True Negative / (True Negative + False Positive)
Metric used for implementation or on going validation
3. Accuracy = True Result / (True Result + False Result)
Metric used for on going validation
4. The term ‘probability’ is used to describe situations where a
++ Recommended parameter probability that the result is correct can be assigned – primarily in
on-going validation
Rejected
Request for Change
No further action
(Complete Form 1)
Approved
Rejected
Complete & submit
No further action
business case
Approved
Develop Specification
Document
Training to SOPs
Verification Report
Implement Competency
sign off
Assessment
Maintenance of
intended process