STEP BY STEP

Document Sample
STEP BY STEP
Shared by: amberp
Stats
views:
68
posted:
11/6/2008
language:
English
pages:
3
AUTOMATION









No need to panic: A structured

approach takes the sting out of

validation of computerised systems

in medical technology

(Figure: photocase.de)









STEP BY STEP

RISK ASSESSMENT MINIMISES EFFORT IN THE VALIDATION OF COMPUTERISED SYSTEMS The introduction of

computerised individual plant, production lines, analytical equipment in the laboratory, or overarching IT sys-

tems (such as ERP or MES) in the production, storage, and control of medical devices are GMP-relevant, as in the

case of the pharmaceutical sector, and therefore have to be validated. This means that the principles of vali-

dation set out in the rules of Good Manufacturing Practice (GMP) and appropriate annexes have to be observed

and implemented. Although this represents a huge obstacle for many companies, especially smaller enterprises,

it can be overcome step by step.







I

f a computerised system takes the Active Substances), GMP Guideline and gineering (ISPE), and “Good Practice for

place of a likewise GMP-relevant its Annex 11, have increasingly been the Computerised GXP-Environments” of

manual process, neither the quality focus of attention in recent years. Yet the the Pharmaceutical Inspection Co-Oper-

nor the safety of the products may de- general demands applicable to the vali- ation Scheme (PIC/S PI011–2). Legal de-

teriorate. Nor may information be lost dation of computerised systems within mands upon a computerised system,

through reduced personnel participation. the GMP guidelines provide only a very which provide the very basis needed in

The very specific demands of CFR Part 11 general framework for the extent and order to undertake and complete GMP-

regarding the handling of electronic rec- depth of validation activities. It is not easy compliant validation in the first place, are

ords and electronic signatures, which go for a manufacturing company to decide laid down in so-called Predicate Rules.

beyond the general validation obligations which measures it has to adopt on the These also include CFR 21 Part 11.

of the German AMWHV Ordinance (Or- basis of these requirements.

dinance on the Production of Drugs and More specific proposals concerning Validation Master Plan as Basis

the approach to qualification of hardware Validation of complex, overarching ERP

and validation of software are to be found systems such as SAP or Manufacturing

in the recommendations of interest Execution (MES) or document manage-

Author groups and associations. For example, ment systems should be divided up into

Wolfgang Hähnel, Head of Sales and these include GAMP 4 (Good Automated three phases.

Marketing, Gempex/GMP Con- Manufacturing Practice), “Validation of In Phase 1 (initialisation) the pro-

sulting & Execution, Mannheim, Process Control Systems” of the Inter- cedure and strategy within the project are

w-haehnel@gempex.com national Society of Pharmaceutical En- set out in a validation plan (VP). Owing to







68 MedPLAST · May 2007

MARKET OPPORTUNITIES

Set-by-Step Validation

Complex systems or control of large-scale sequences of events are

no longer insurmountable barriers in the qualification of hardware

and the validation of software if a step-by-step approach is adopted.

Classification according to a well-structured risk assessment mini-

mises the effort required and provides clarity.









the complexity and the differing respon-

sibilities of computerised system it is rec-

ommended that a separate validation

plan be drawn up for these systems. This

document, known as the VMP, provides

the responsible departments, manage-

ment, and the relevant authorities with a

comprehensive update of all validation

activities.

In parallel, the User Requirement

Specifications (URS) identify and record

the GMP-critical process parameters and

other quality-relevant requirements. The

URS should therefore describe all de-

mands on the system to be acquired and

on the vendor in a very consistent, well-

structured manner, including as many

details as possible. Among others, the fol-

lowing points should be addressed:

relation to VMP,

predicate rules relating to the process

chain,

consideration of the actual status

wherever possible,

description of the sequence of pro-

cesses, target status of process chain,

nature and execution of the new intro-

duction or of the release change,

hardware specifications (PCs, servers,

redundant systems, etc.),

security concept (firewalls, virus scan,

etc.),

business process continuity (failure,

down-time, etc.),

fall-back scenario (reversion to former

release or system when problems

occur),

archiving concept for GMP-relevant

data,

demands of programming rules/

guidelines in the specifications,

demand of source-code review by im-

partial persons,

consideration of third-party systems,

assessment of vendors and audit (ob-

ligatory from software category 4),

list of vendors’ suppliers,

maintenance, hot line, service agree-

ments,

personnel training.









MedPLAST · May 2007 69

AUTOMATION









Validation strategy in three steps









In an second step, i.e. in Phase 2, all

business modules and business processes

classed as GMP-relevant are subjected to

a detailed risk analysis and assessed for

their risk potential at the transaction

level. However, this step can only take

place after transfer of the GMP-relevant

demands of the URS into the supplier

specifications. Because it is only then that

the precise branching within the modules

and the number of transactions are

known. Risk analysis can be based, for

example, on the FMEA (Failure Mode

and Effects Analysis) method.

The resulting assignment to a risk cat-

egory provides the basis for specification

of the extent of testing, the depth of test-

ing, and the level of documentation of

validation. Proof of validity has to be

documented for every individual transac-

tion considered to be critical.

Moreover, within the risk analysis the

interfaces between the transactions and

the possible third-party systems are to be

examined and assessed for their GMP-

relevance. If necessary, the validity of the

individual interfaces has to be established

In addition to the validation plan and Risk assessment serves, on the one by corresponding operational tests and

the URS, the Standard Operating Pro- hand, to establish whether the system documented during operational qualifi-

cedures (SOPs) have to be considered in under consideration is a so-called legacy cation (OQ).

the first phase. All instructions necessary system and, on the other, to identify the In Phase 3 (Implementation) user-

for subsequent operation and mainten- GMP-relevant business processes in- specific programming, factory acceptance

ance should be listed here. stalled by the company or the cor- testing (FAT) and site acceptance testing

responding third-party systems. (SAT), as well as the validation activities

Required by the Authorities: Alongside the predicate rules ap- installation qualification (IQ), oper-

Risk Assessment plicable to the computerised system, the ational qualification (OQ), and perform-

One of the most important instruments basis of risk classification is provided by ance qualification (PQ) are undertaken

for performing a well-structured vali- the process sequence plans, with the aid within the development, validation, and

dation of these systems, without going of which the individual business pro- productive system.

beyond what is actually required, is a risk cesses can be described as a sequence of

assessment as demanded by the auth- functionally related business activities.

orities. This has the goal of identifying There ultimately results an overview

those processes, from among the totality of all business processes which

of all processes involved and their result- describes the assignment of transactions infoDIRECT

ing functions, with which GMP-relevant to the desired functionality. Within Supplementary documents are available for

data can be generated, displayed, erased, the framework of risk classifica- download: Schematic of GMP risk assess-

or modified in the individual depart- tion all third-party systems ment, form for risk classification, example of

ments. In large computerised systems, with an interface to the ERP system FMEA risk analysis.

such as ERP, GMP risk assessment should also have to be identified and ca- www.plastverarbeiter.de

be divided into two separate sections. tegorised. Searching: MedPlast07Gempex









70 MedPLAST · May 2007


Share This Document


Related docs
Other docs by amberp
How do you prepare for the Lord s Supper
Views: 30  |  Downloads: 0
ISM Step by Step Installation Guide
Views: 58  |  Downloads: 3
Choosing and Using a Health Plan
Views: 14  |  Downloads: 0
NAME
Views: 33  |  Downloads: 0
RoboFesta-UK 2nd Annual Open Meeting
Views: 4  |  Downloads: 0
How do you get your ideas
Views: 40  |  Downloads: 0
by registering with docstoc.com you agree to our
privacy policy

You are almost ready to download!

You are almost ready to download!