GAMP 5 Good Practice Guide-Matt Safi
GAMP 5 Good Practice Guide-Matt Safi
GAMP 5 Good Practice Guide-Matt Safi
www.chinapat.com
GAMP5
Different Terminology
US FDA
Automated processes. When computers or automated data
processing systems are used as part of production or the quality system, the manufacturer shall validate computer software for its intended use according to an established www.chinapat.com protocol. All software changes shall be validated before approval and issuance. These validation activities and results shall be documented.
EMEA
Validation: The extent of validation necessary will depend on
a number of factors including the use to which the system is to be put, whether the validation is to be prospective or retrospective and whether or not novel elements are incorporated. Validation should be considered as part of the complete life cycle of a computer system. This cycle includes the stages of planning, specification, programming, testing, www.chinapat.com commissioning, documentation, operation, monitoring and modifying.
SFDA
for these applications they should be validated to ensure that critical process requirements are met.
www.chinapat.com
Good Manufacturing Practice for pharmaceutical products, Part II Annex Chapter 12 Terminal Sterilisation:
2 12
5 Pharma Bio Solutions Ltd
Level 3
Batch
Levels 2,1,0 Control Systems
Continuous
Control Systems
Discrete
Control Systems
Configurable
www.chinapat.com
Embedded
Standalone
Controllers, Analysers
PLC+ SCADA
DCS
parameterisation)
pH
GAMP5
(Good Automated Manufacturing Practice) www.chinapat.com A RisK Based Approach to Compliant GxP Computerised System GxP
www.chinapat.com
bodies as a methodology for the development and operation of Control Systems GAMP5 It is about ensuring the Brain of a Machine or a Process work properly and is fit for its intended use. www.chinapat.com It is about Building Quality onto a Control System throughout its Life Cycle. It defines the steps to be taken at each stage of Control System Life Cycle It defines Roles and Responsibilities of User and Suppliers
13
Key Personnel
availability , support, and maintenance of a system and for the security of the data residing on that system
www.chinapat.com
expertise in a particular area or field. SME should take the lead role in the verification of computerised systems. SME responsibilities include planning and defining verification strategies, defining acceptance criteria, selection of appropriate test methods, execution of verification tests and reviewing results
SME SME
15
Yes / No
www.chinapat.com
17
4, configured
Software, often very complex, that can be configured by the user to meet the specific needs of the users business process. Software code is not altered
DAQ systems SCADA DCS BMS HMI LIMS ERP Clinical trail monitoring
Life cycle approach Risk based approach to supplier assessment Supplier QMS Record version number, verify correct installation Risk based testing in a test environment
5, Custom
Internally, externally developed IT applications.IT Internally, externally developed process control applications. Custom ladder logic Custom firmware Spreadsheet (macro)()
Same as cat 4 plus 4 More rigorous supplier assessment, with possible supplier audit Possession of full life cycle Design and source code review
20
Software Category 3 3
www.chinapat.com
21
Software Category 4 4
www.chinapat.com
22
Software Category 55
www.chinapat.com
23
Item Configurable (Controllers, weigher, etc) Embedded Standard (PLC + HMI) Embedded Non-Standard (PLC + HMI) Standalone (DCS, SCADA+PLC)
Hardware Category 1
Software Category 3 3 3, 4 ,5 3, 4 ,5
www.chinapat.com 1
1 or 2 2
24
Controlled Document For Cat 3 written for a specific solution 3 www.chinapat.com For Cat 4 & 5 It is written in general 45 Sufficient, Realistic, Measurable, Achievable Testable: Clear, Precise, basis for formal testing Traceable: Design and testing Define priority: Mandatory, Beneficial, Nice to have
25
Functional Specification
A Functional Specification is a key document in defining how the customer functional requirements, as defined in the user requirements specification, are to be met.
Functional Specification is the responsibility of the supplier www.chinapat.com It is written in response to URS URS It provides the main basis for FAT FAT It needs to be approved by User. Generally may require further revision during the project life cycle.
26
Test Phases
A system test phases depends on its size and complexity
Typical test phases include Software Module testing Internal integrated testing Hardware www.chinapat.com Software FAT test FAT Hardware Software SAT test SAT Hardware (IQ) IQ Software (OQ) OQ
Pharma Bio Solutions Ltd
27
Test Protocols
A Test 'protocol' or 'specification' defines the testing to be carried out to verify that the system (or its individual elements) meets pre-defined requirements.
A project may include Software Module Test Protocol, FAT protocol, SAT protocol FATSAT www.chinapat.com Depending the size of the project there maybe a separate Hardware Test protocol Test Protocols are the responsibility of the supplier They should be approved by User. Generally may require further revision during the FAT. FAT
28
Supporting Processes
Risk Management
Design Review
Traceability
Document Management
On-going Operation
Maintaining compliance and fitness for intended use
of GxP Validted system throughout its life cycle GxP Users of the system must be able to demonstrate that www.chinapat.com they have considered and reviewed maintenance requirement and supports needs for the system and decided what procedures and records should be established and maintained.
30 Pharma Bio Solutions Ltd
31
Project Stages
www.chinapat.com