Source: http://docplayer.net/1183595-Computer-validation-guide-final-draft.html
Timestamp: 2017-02-28 14:54:43
Document Index: 60228532

Matched Legal Cases: ['art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 1', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11']

Computer validation Guide. Final draft - PDF
Download "Computer validation Guide. Final draft"
1 Computer validation Guide Final draft Version 2 December 2002 Revision History: Version 1 August 2002 Version 2 References to 21 CFR part 11 in Chapter 6. Legal Reference December 2002 COMPVALFINALDRAFTDECEMBER2002.DOC page 1 / 402 Contents 1 Contents Acknowledgement Introduction Glossary Scope Legal requirements Guidance Strategy Approach Analysis Inventory Risk Analysis Economics Compliance Project Plan Description Organisation Project Manager System Owner and Sponsor Users Developer/ Supplier Site Computer Support Quality Unit Responsibility Matrix System Life Cycle Introduction GAMP Categories System Life Cycle Process Planning Specification Supplier / Vendor selection Design and construction Acceptance Testing Implementation and acceptance Ongoing operation; Use of system Security Back up and Restore Disaster recovery Contingency planning Business continuity Preventive maintenance Corrective maintenance (Problem reporting) Change control Audit trail...19 COMPVALFINALDRAFTDECEMBER2002.DOC page 2 / 403 Training Periodic evaluation Archiving Retirement phase Infrastructure Validation deliverables and activities Appendices Acknowledgement 8.1 Practical checklists for computer validation User Requirement Specification Traceability Matrix Definition: Change Control Scope Change control system Matrix Benefits References FDA Web site/fda Guidelines ICH G.A.M.P IEEE 730, 828, 829, 830, ISO Standards Glossary.. 30 This document was prepared by a Task Force consisting of representatives from various companies that participate in the Active Pharmaceutical Ingredients Committee of CEFIC. We thank all the members mentioned below for their efforts, cooperation, creativeness, constructive comments and endurance. Without these elements this document would not have reached its present status. The members of this Task Force are: Lisa Näsman * (Astra Zeneca) Claude Becker (Seloc/PCAS) Gert Beets * (OmniChem) Jean-Pierre Bovee (Aventis) Gerben Canninga * (Diosynth) Nigel Cryer (MSD/Merck) William Cuijpers * (Diosynth) Kees Piket (Solvay Pharmaceuticals) Willy Verhaegen (OmniChem) COMPVALFINALDRAFTDECEMBER2002.DOC page 3 / 404 Allert Wiersema (DSM Anti-Infectives) * these members left prior to finishing the document or joined later 3 Introduction In the last decade, computerised systems have become a vital part in the manufacture of Active Pharmaceutical Ingredients. Typical applications are Process Control Systems (DCS, PLC, SCADA), Laboratory Information Management Systems (LIMS), Laboratory Instrument Control Systems and Business Systems (ERP, MRP II). c regulations imply that the functionality s of those computerised systems, which have influence on the quality of the API, should be validated. Validation shall demonstrate that the parameters defined as critical for its operation and maintenance are properly (adequately) controlled/managed. It is essential that the validation is practical and achievable, adds value to the project, and is concentrated on the critical elements of the system. This Guideline outlines the scope and legal requirements for the validation of computerised systems, chapter 7 gives a comprehensive methodology suitable for most situations within API production control and data handling situations. For some specific cases the coverage may be less extensive and/or subsections may be merged depending on the criticality and the importance of the systems to be validated. Where specialist validation cases are to be handled chapter 8 gives the official guidance, references and industry guidelines. 4 Glossary Refer to chapter Scope This guide is intended for use by manufacturers of Active Pharmaceutical Ingredients (APIs) and intermediates that use computerised systems for various parts of the process leading to the manufacture of an API or intermediate. It provides interpretation of existing c guidelines related to the validation of quality critical computerised. These interpretations aim to be practical on one hand and acceptable for both the industry and authorities on the other. The emphasis is on explaining what to do and to a lesser degree in how to do. Whenever practical and feasible, attention will be paid to linking validation of computerised systems with other types of validation, like process validation and equipment validation. Within this guide attention will be paid to two essential parts of computerised systems: 1. Infrastructure 2. Applications COMPVALFINALDRAFTDECEMBER2002.DOC page 4 / 405 When applying the contents of this guide it should be realised that not all computerised systems will contain all of the elements (a through e) mentioned below. The following aspects will be covered: a. hardware b. operating system c. network system d. data base management system e. system software f. strategy g. compliance h. project plan i. system life cycle j. change control Apart from the above-mentioned subjects, supporting activities as training of personnel, documentation and use of checklists will be covered. Attention will be given to the aspect of risk-analysis in relation to validation of computerised systems. Note Although no guidance will be included in this document related to electronic records and signatures (refer to 21 CFR part 11), this subject area must be considered in the URS (also see chapter 6). 6 Legal requirements Computerised systems used in the manufacture of API s should be properly developed, validated and maintained to assure data and product integrity. The newly developed guidance for the manufacture of API s (ICH Q7a) covers these requirements. It should be noted that according to the current understanding, 21CFR part 11 is not legally binding for API manufacturers; however it is advisable to consider the principles and recommendations contained in this document prior to validating computerized systems as required by ICH Q7a. 7 Guidance 7.1 Strategy In today s business environment computerised systems are used more and more. It is critical to design and validate them so that they are fit for purpose and meet user as well as compliance requirements There is a need for clarification of this very complex and often misunderstood area of compliance. This area is increasingly the domain of a few consultants and experts. This document will provide clear transparent guidance for API-manufacturers. It will help industry to redress the balance between too much, often ineffective, documentation with too little impact on quality assurance. This will bring about a cost effective, added value efficient and effective way of performing validation of computer systems that are maintained in compliance. A strategy to achieve this will be set out in a pragmatic approach using a Validation Plan including the elements below. COMPVALFINALDRAFTDECEMBER2002.DOC page 5 / 406 7.1.1 Approach 1. The approach to validation of computer systems should be based on common sense and use techniques that are familiar within other areas of validation and also business. 2. It is important to establish the final objective of validation and to choose an approach where a positive response is given, every time the following questions are asked: Will this have added value? Is this the most efficient way? Is this the most effective way? Can we achieve 80 % of the objective with 20 % of the effort? 3. One way to assist with these decisions is to use simple flowcharts Analysis A priority for validation activities can be established by analyzing a system inventory for the criticality, validation status, software category and system type. This analysis aids validation planning and prioritisation Inventory For an effective approach the first make an inventory of existing and any proposed systems. In compiling the inventory an assessment should be made on the criticality of each system using a methodical approach. This list should be kept fully updated and the priorities should be assigned once the current inventory is completed. This inventory could include classifications based on potential impact on product quality (e.g. critical, major, minor, none and further subdivide these into direct and indirect impact). The inventory list (which can take the form of a spreadsheet or database) would normally include headings like: system name and version number system type, e.g. legacy system or new system and modules system owner system use, e.g. materials management, process control, analytical control etc. criticality, e.g. product quality, compliance, business validation status implementation date (actual or planned) development category (e.g. off the shelf, user developed etc.) software category e.g. spreadsheets, PLC s, process controls GAMP category CFR 21 part 11 e.g. compliant electronic records and signatures Last validation performance check. Priority (an outcome of risk analysis) Risk Analysis (Ref. ISPE baseline guide for qualification and commissioning) A risk analysis all factors including safety, environment, product quality and financial should be taken into consideration. However the most important one is to define the criticality of the COMPVALFINALDRAFTDECEMBER2002.DOC page 6 / 407 system. Looking at the impact of the system on product quality, the validation status and the potential impact on the business can do this. Product quality can be impacted directly, indirectly or not at all. Examples are as follows: direct impact: process control of final purification step, assay of finished product indirect impact: distribution list of finished products, equipment maintenance program Once validated, all computerised systems must be maintained according to the System Life Cycle approach. The c approach to validation can be used in a total quality approach to computer systems involved in safety, environment, finance, however there is no legal requirement to do that and these systems should not be subject to c inspection Economics As API production usually takes place in a highly competitive environment it is of utmost importance to perform validation in an efficient and cost effective way. To that end each company has to decide how to execute validation. Two main are used: to use own, well educated and trained personnel to hire consultants to guide and organise the validation task The latter option should be considered especially for smaller companies. However, one has to realise that some in-house expertise is needed to stay in control of computer system activities and of the costs. It is a fundamental requirement that the company itself remains responsible for the ultimate results. To assist in control of costs it is useful to recognise that not all computerised systems are in need of the same level of validation. Less critical systems should have appropriate level of documentation. 7.2 Compliance c regulations imply that computerised systems that influence the quality of the API must be validated. The depth and scope of validation depend on the criticality of the computerised functionality. This has to be established by means of a risk analysis at an early stage of the validation process. Compliance critical key points to be considered include: Proven fit for purpose Access control /user management. Data integrity including: prevention of deletion, poor transcriptions and omission. Authorised / unauthorised changes to data and documents Critical Alarms handling (Process) Audit trails Disaster recovery / Back up and retrieval System maintenance and change control Training Evidence of sufficient control of these issues should be demonstrated in the validation documentation. COMPVALFINALDRAFTDECEMBER2002.DOC page 7 / 408 This compliance must be integrated using the system life cycle approach (SLC), and clearly identified in the user requirements phase for any new computerised systems as detailed in chapter 0. For existing systems, for which a life cycle model was not applied, a gap analysis must be undertaken against c compliance issues. Identified issues must be tested and documented following a formal qualification plan/report. For any identified non-conformances, the following alternatives should be considered: upgrading ensuring the requested control level through additional procedure (s) if the upgrading is not feasible replacing/upgrading the system where gaps are substantial and cannot be covered by the previous measures. 7.3 Project Plan Description The project plan is the backbone of any IT validation activity for any system. It describes the objectives, the organization, schedule, step-by-step activities and their chronology including milestones. Among these milestones are the deliverables. It should address measures to control the project such as review and communication. It is assumed that the major aspects covering quality management system are in place. A document describing the current computer validation situation should be available. For the activities undertaken as part of the project plan see section Organisation Special attention should be paid to the project organization Project Manager The Project Manager is responsible for meeting objectives in terms of compliance with URS, while observing quality, time and costs requirements System Owner and Sponsor The System Owner is the formal owner of the system and he is responsible for the validated status of the computerised system The Sponsor provides the necessary investment and resources to support the project Users Key users must be identified prior to writing URS. For instance when a project covers different specific areas, it is worthy to appoint a key user for each specific area. They must approve the following documents: URS Functional/Design Specifications They are involved in testing. It is key that the user has sufficient knowledge of the type of system so that they can become involved in designing the system. If there is a lack of knowledge it is critical that training be provided so that the user can provide an informed opinion. COMPVALFINALDRAFTDECEMBER2002.DOC page 8 / 409 7.3.6 Developer/ Supplier The role of the Developer/ Supplier must be clear regarding the deliverables, document authorization, timing, change control. They must comply with all referenced quality standards. The Developer/Supplier must provide the design specifications that must meet the URS. Increasingly, suppliers are involved in executing part of the validation activities (early testing at supplier s site). These aspects would be covered by the contract established between the customer and the supplier Site Computer Support The site Computer Support defines or at least authorizes the hardware design, taking in account the compatibility of the existing systems, load, infrastructure. Their role regarding installation and maintenance, including documentation must be defined Quality Unit Quality Unit should be involved from the very beginning of the project. They must, review and approve all quality impacting documents Responsibility Matrix Activities and responsibilities are assigned, for example by using a matrix, which lists all the deliverables versus contributors for each task. Responsibilities for writing, approving and authorizing should be assigned. E.g. Contributors Deliverables System owner Project Manager QA Supplier Key User IT Support URS A R A W W IQ/OQ R A W A A protocol Test Scripts R A W A A Etc. Responsibilities: Writing: W Reviewing: R Approving: A 7.4 System Life Cycle Introduction This chapter details the actual validation activities to be performed to provide a computerised system validated to current standards. Validation activities for computerised systems are divided into qualification of infrastructure (computers, system software and network) and validation of applications (including the COMPVALFINALDRAFTDECEMBER2002.DOC page 9 / 4010 application software, interfaces to other applications, equipment and operational procedures) because of the differences in the approach required for each of the groups. The term computerised system is used in the text to designate the combination of both infrastructure and applications. A Validation (Master) Plan should be developed according to company policies and internal procedures, including both infrastructure and applications. Standard Operating Procedures (SOPs) should be in place together with a formal System Life Cycle Concept which describes all the relevant activities for creating and maintaining qualified infrastructure and application Software Categories (GAMP) For applications the software development method or status can determine the validation effort. A very useful reference in this area is the GAMP guide. The GAMP guide is an industrial standard (Ref 0) that defines five validation level categories for software as shown in the matrix below. Categories 4 and 5 are the categories for which major validation efforts are required COMPVALFINALDRAFTDECEMBER2002.DOC page 10 / 4011 Task Force Computer validation 13 January 2003 Software categories according to GAMP Guide GAMP Application Type category example 1 Operating Systems, network software Infrastructure example VMS, MVS, UNI, Windows NT Remarks Established, commercially available operating systems which are used in pharmaceutical manufacture are considered validated as part of any project in which application software operating on such platforms are part of the validation process (i.e. the operating systems themselves are not currently subjected to specific validation other than as part of particular applications which run on them). 2 Standard Instruments, Micro Controllers, Smart Instruments 3 Standard software packages 4 Configurable software packages balances, ph meters, bar code scanners, PID controllers. Office applications, spreadsheet, data base systems LIMS, ERP (eg MRPII based), DCS, SCADA, MES, Chromatography data systems. logic on an interface controller Layered products as DBMS, ACL and communication packages Users specific applications which are PLC based. These are driven by non-user programmable firmware. They are configurable and the configuration should be recorded in the equipment IQ. These are called Canned or COTS (Commercial Off-The-Shelf) configurable packages in the USA. Examples include Lotus 1-2-3, Microsoft Excel software (but not the spreadsheet itself since it includes generally calculations and eventually macros). There is no requirement to validate the software package, however new versions should be treated with caution.. These are called custom configurable packages in the USA. Examples include Distributed Control Systems (DCS), Supervisory Control and Data Acquisition packages (SCADA), manufacturing execution systems and some LIMS and MRP packages. In these examples the system and platform should be well known and mature before being considered in category 4, otherwise category 5 should apply. A typical feature of these systems is that they permit users to develop their own applications by configuring/amending predefined software modules and also developing new application software modules. Each application (of the standard product) is therefore specific to the user process and maintenance becomes a key issue, particularly when new versions of the COMPVALFINALDRAFTDECEMBER2002.DOC/c Word 7.0 Cefic999 page 11 / 4012 GAMP category Type 5 Custom built or bespoke systems Application example exclusively built solutions for a single or few customers Infrastructure example PLC with single purpose dedicated program Remarks standard product are produced. These are custom-build applications and include also the custom-build interfaces implemented when installing a configurable package. For these systems the full Life Cycle should be followed for all parts of the system. It should be noted that complex systems often have layers of software, and one system could exhibit several or even all of the above categories. COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 12 / 4013 Task Force Computer validation 13 January System Life Cycle Process This section gives detailed guidance on the validation effort needed to establish documented evidence that a process will consistently perform according to its predetermined specifications and quality attributes. Depending on the complexity of the computerised system, or on the GAMP category, not all phases and/or activities have to be followed e.g. documentation can be combined (e.g. in the validation plan). The activities and related output, which are described in the following sections, are not mandatory, but should be seen as an example to be adjusted for each specific situation. The System Life Cycle concept describes all aspects of the life cycle of a computerised system that could consist of: planning; specification design construction testing implementation and acceptance ongoing operation; archiving of the system when replaced. In the next chapters the validation activities are discussed step-by-step following the lifecycle concept Planning Typical activities and output in this phase are: Activity Output Define business need/problem Business justification/problem description * Assign project manager Define project-/validation team Describe main system requirements (Main) system requirements * Perform feasibility study Results feasibility study * Allocate project resources Write project plan Project Plan * May be incorporated in the project plan Specification Validation of a computerised system should demonstrate that the system meets predetermined specifications. Testing is needed in several stages of the Life Cycle. Therefore, documented detailed specifications need to be available for each stage of testing. In the Specification Phase the detailed user requirements specification (URS) and the acceptance criteria are specified, based on identified critical requirements. Based upon this specification a supplier market survey may be performed to screen the possible candidate suppliers. Usually, a supplier has detailed information about an existing product in documents like the functional specification and/or the system design. COMPVALFINALDRAFTDECEMBER2002.DOC/c Word 7.0 Cefic999 page 13 / 4014 After approval of the DQ formal change control should be applied to all specification documents. Consider parallel validation activities (see table below) Typical activities and output in this phase, not necessarily in this chronological order, are: Activity Output Develop validation plan Validation plan Define User Requirement Specification (URS) User Requirements Specification (URS) Develop acceptance criteria Acceptance criteria * Perform risk analysis Risk analysis report Develop acceptance test plan (IQ/OQ protocols, PQ protocol if applicable) Acceptance test plan (IQ/OQ/(PQ) protocols) * Request for proposal (i.e. quotation) Request for proposal Supplier review/audit Review/audit report Supplier selection Supplier qualification Draw-up of contract Contract with supplier; with contractual requirements Place order Acquisition order *If the software is developed, these items are part of the System Design and Programming Phase. Generally, before supplier selection, the User Requirements Specification (URS) and the acceptance criteria should be specified. The URS should contain three types of requirements: process/user related requirements (detailing the required functionality's), technical/it related requirements (including not only e.g., hardware and software requirements and required interfaces with other computerised systems, but also addressing the capability of the system to migrate data from previous as well as to future versions or systems), quality/qa related requirements (including -compliance and all requirements from 21 CFR Part 11). All requirements should be unambiguous, complete, verifiable/testable and consistent with each other. Preferably the URS are set up in a way that the traceability matrix can be built up from there (see appendix 8.6) Supplier / Vendor selection Whether the supplier is an outside company or an internal department, the supplier's ability to provide a system that can be validated should be a primary consideration. Knowledge of validation requirements and experience in providing systems for systems are important selection criteria. At least for Category 4 and 5 systems used for activities, a supplier quality review, and if considered relevant an on-site audit, should be performed to assess the validity of potential suppliers. The supplier review and/or audit should cover company information, Quality Management System information, Software Development and Package information. The supplier selection process should be documented and any deviations from the requirements observed during an audit should be addressed. For critical systems, this review and/or audit should be carried out before final supplier selection. COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 14 / 4015 When a supplier has been selected, contractual requirements should be defined. These contractual requirements are usually a blend of user requirements and technical specifications Design and construction This phase is only applicable to computerised systems that belong to GAMP category 4 or 5 and will be mostly the responsibility of the supplier. In the Design Phase a Functional Specification will be developed when customisations on an existing product are needed, or a custom built system. This is a combined activity by both the supplier(s) and the customer. The total design of the system can be checked against the User Requirements Specification to check that all requirements are met. This check is often facilitated by a Design Qualification, DQ. Typical activities and output in this phase are: Activity Define functional specification Design the system Design Qualification Programming and module testing Audit supplier Supply final system description Supply system installation procedure Supply system documentation Output Functional specification Design specification DQ report (can be included in the URS traceability matrix) Software; module test report Audit report System description (including hard/software diagrams) System installation procedure Manuals and user guides The supplier is required to follow a development methodology, programming standards, and Change Control procedures during product development. For purchased systems (GAMP 4 category), (parts of) the design and programming may already have been done. In this case the supplier has to supply documented evidence that a development methodology, programming standards, and Change Control procedures during the development phase were followed and that adequate tests were performed. In case the supplier is doing substantial programming, in this phase possibly an additional supplier audit with a special focus on the SLC, adherence to procedures and proper documentation may be useful Acceptance Testing The objective of this phase is to take a decision on the formal acceptance of the system as delivered by the supplier. For developed systems this can be divided in two parts: Acceptance at the supplier site, Factory Acceptance Test (FAT); Acceptance at the customer site, Site Acceptance Test (SAT). It can also be combined in a general Acceptance Test. During this phase the installation and operation of the computerised system have to be qualified according to the Installation and Operational Qualification (IQ/OQ) protocols for the system. Although a qualification can be, at least partly, performed by the supplier of the system, the project team is responsible for the results. The level of detail of in-house testing is depending upon the GAMP category and upon the testing done by the supplier. Typical activities and output in this phase are: COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 15 / 4016 Activity Installation Qualification Operational Qualification Training of users Audit/review of IQ/OQ and if applicable (parts of) PQ Updated IQ/OQ report to QA for approval Output IQ report (FAT, SAT can be included) OQ report (FAT, SAT can be included) Qualified personnel Internal Audit/review report Final approved IQ/OQ reports If IQ/OQ protocols are used which the supplier develops, these protocols should be reviewed and approved by the project team before starting the IQ/OQ. The IQ/OQ can be executed at the user s site, by the supplier or by a user representative or member(s) of the project team. Each test shall be documented in a way that it can be reconstructed. This can be achieved by creating log files, making printouts, using logbooks etc. If these options are not feasible or practicable, witness testing is allowed. Testers should sign for each test performed. Reviewers should sign for logical sets of tests. In the case of witness testing the witness should sign for the same steps as the tester. Witness testing is required when a vendor or contractor undertakes system testing. Chronology of IQ, OQ and PQ is a critical compliance issue. The critical parts of the IQ should be finished before executing OQ of that particular part, but parallel activities for other parts are possible. If any test or challenge does not meet the specification or other deviations are found, this should be documented and, if necessary covered by corrective actions (e.g. identification of the cause of the deviation, corrective actions and additional tests). After installation, the Operational Qualification (OQ) verifies the functional specifications of any individual system or sub-system. If needed to confirm whether the system meets the contractual requirements, relevant parts of the PQ need to be performed in this phase. (Additional PQ testing against other user requirements is often still required after acceptance). Results from previous testing e.g. FAT can also be used in this phase. These results from an IQ/OQ must be reported as a formal report (combined it is often called an acceptance testing report). At this stage the system is approved for handing over to user for PQ to take place Implementation and acceptance Often at the time of acceptance of the system from the supplier, additional testing and/or documentation is required before the system can be released for use in the production environment. COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 16 / 4017 Typical activities and output in this phase are: Activity Develop implementation plan Performance Qualification (PQ) Develop procedures Complete system description Training of additional users Write validation report Validation review Output Implementation plan PQ report Procedures System description Qualified personnel Validation report Internal Audit report The computer system may be formally released for PQ. PQ will take place in a production environment. During the period of Performance Qualification of the system additional monitoring is undertaken. Depending on the nature of the system the PQ can consist of a monitoring period or process validation (e.g. production of validation batches). The implementation plan specifies the actions for implementing the computer system in its operational environment: Necessary activities and other documentation as required for the ongoing operation phase Training of additional system users Remaining test activities, like production of Process validation batches By approving the final report, the system implementation is completed Ongoing operation; Once a computer-related system has been validated, the validated state has to be maintained. This requires an adequate maintenance system and (a) Standard Operating Procedure(s) that are (is) incorporated in the relevant Quality Management System. The following issues need to be covered as applicable in (a) procedure(s): Use of the system Security Back up and Restore Disaster recovery Contingency planning Business continuity Preventive maintenance Corrective maintenance (problem reporting) Change Control (including configuration management); also see chapter 8.5 Change Control Audit trail (equivalent to alteration of data) Training Periodic evaluation Archiving System retirement (may be addressed in a much later stage) Use of system In this procedure the main tasks and responsibilities of the users should be defined. If needed, detailed instructions on how to use the system can be included. COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 17 / 4018 Security There needs to be proper access control procedures on three levels: 1. Wide and/or Local Area Network level 2. System, or Application level 3. PC level. Items that need to be covered include how access is controlled, a password policy and audit trails. At all three levels there should be continuously updated lists of approved users and their authorisation levels Back up and Restore The following items need to be covered by these documents: back-up and restore procedures frequency of back up verification of the ability to retrieve a back up data and files at least two generations or two copies of back-ups should be kept, unless other measures are taken to prevent back-up versions from damaged. back up copies should be stored separate from the system in a way that it is highly unlikely that both the original and the back-up copy/copies can be damaged. availability of the back up within an appropriate period for systems with a low back-up frequency, back ups should be checked for accessibility, durability and accuracy at a frequency appropriate for the storage medium, which should also be specified, but at least once a year for critical systems. in case of no low frequency back-ups change control should ensure the availability and integrity of back ups by restoring the data on a regular basis (particularly after changes to the system have been made). even with high frequency back-ups, prove the restore system works e.g. one time per year. There is no need to test the full system; this can be done by randomly selecting one or a few files to restore on a special area. Note: if the same tapes are used, the tapes may be getting worse without noticing it. The procedures have to be carried out, controlled and documented Disaster recovery Disaster recovery procedures should be available for the most common disasters, often power failure or hard disk failure. The maximum downtime of the system should be documented, including the measures to meet that. If possible, disaster recovery procedures should be tested Contingency planning In case of complete destruction of the hardware, software and data files, the knowledge and back ups of the system should be available to build up a complete new system. It should be documented whether and if so how the process is continued in case of a disaster (unavailability of the system) Business continuity Measures should be taken to ensure availability of source code in case the system supplier stops business for any reason. This should be addressed in Service Level Agreements and/or in Escrow agreements. COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 18 / 4019 Preventive maintenance Items to be covered are: List of critical system components There should be a system in place (e.g. Service Level Agreement SLA) which ensures that maintenance takes place in time. For hardware components the date of the last and/or next maintenance should be easily visible or retrievable. All maintenance should be documented (e.g., logbook) In case preventive maintenance leads to changes, the change control procedures should be followed Corrective maintenance (Problem reporting) Each problem should be registered under a unique number or code, mentioning the problem, the date, the hard ware (registration number) the chosen solution, by whom it was handled etc. If the solution of a problem leads to a change in hardware or software, the procedures for change control should be followed Change control Refer to section Audit trail Computer generated and time stamped audit trails that independent record the date and time operator entries and actions that create modified or delete electronic records. Record changes shall not obscure previously recorded information. The audit trail should be searchable and be secured from any changes. It must be able to interrogate by dates, time, persons, type of change and reasons for change Training All users of the system should be trained. This training should be documented and where applicable evaluated. Users should be informed about current standards or changes of the system. The training responsibilities should be defined Periodic evaluation At predefined intervals (e.g. once a year) assessments should be made of the performance of the systems using the data from the change control and problem reporting documentation. A decision should be made and documented on the possible need for changes to and/or revalidation of the system. Decisions on periodic evaluation should be approved by at least the system owner and QA Archiving All documentation generated in the Operation and Maintenance and Change Control procedures should be properly archived. Data and the necessary software to retrieve those should be archived. COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 19 / 4020 Retirement phase At a certain point in the computer system s life cycle circumstances can occur which force a decision to retire the computer system. This decision will initiate the Retirement Phase (and probably an Planning Phase for system replacement). In case of system retirement the following steps should be taken: Set up a data preservation plan which could include one of the following options: make sure that a new system will be able to retrieve data from previous systems preserve previous applications archive hard copies (when allowed) Completion of system documentation and validation dossier Execution of the data preservation plan QA audit on the preservation documentation Infrastructure Qualification of the infrastructure e.g. of the local area network, contains the following elements: high level documentation of the network e.g. security, reliability and availability. installation documentation including current schematic diagram. configuration management (an up to date inventory of hardware and software [incl. versions] components) monitoring of the performance of the infrastructure Testing of infrastructure is normally included in the functional testing of the application (e.g. loop testing, process control systems etc) Validation deliverables and activities The system life cycle model as defined in this document serves as the backbone for the validation process. Depending on the complexity and the GAMP category of the computerised system, activities and/or related output may be omitted, rationally combined or further subdivided. Category 1 Operating Systems Well-known operating systems should be used. Record the name and version number in the Hardware Acceptance tests or equipment IQ. New versions of operating systems should be reviewed prior to use and consideration given to the impact of new, amended or removed features on the application. This could lead to a formal re-testing program of the application, particularly where a major upgrade of the operating system has occurred. Category 2 Standard Instruments, Micro Controllers, Smart Instrumentation, Embedded software The configuration should be recorded in the equipment IQ. The unintended and undocumented introduction of new versions of firmware during maintenance must be avoided through the application of rigorous change control. The impact of new versions on the validity of the IQ documentation should be reviewed and appropriate action taken. COMPVALFINALDRAFTDECEMBER2002.DOC/c Cefic999 page 20 / 40 View more
MHRA GMP Data Integrity Definitions and Guidance for Industry Introduction: Data integrity is fundamental in a pharmaceutical quality system which ensures that medicines are of the required quality. This More information Testing Automated Manufacturing Processes
Testing Automated Manufacturing Processes (PLC based architecture) 1 ❶ Introduction. ❷ Regulations. ❸ CSV Automated Manufacturing Systems. ❹ PLCs Validation Methodology / Approach. ❺ Testing. ❻ Controls More information Computerised Systems. Seeing the Wood from the Trees
Computerised Systems Seeing the Wood from the Trees Scope WHAT IS A COMPUTERISED SYSTEM? WHY DO WE NEED VALIDATED SYSTEMS? WHAT NEEDS VALIDATING? HOW DO WE PERFORM CSV? WHO DOES WHAT? IT S VALIDATED - More information MHRA GMP Data Integrity Definitions and Guidance for Industry March 2015
MHRA GMP Data Integrity Definitions and Guidance for Industry Introduction: Data integrity is fundamental in a pharmaceutical quality system which ensures that medicines are of the required quality. This More information OECD DRAFT ADVISORY DOCUMENT 16 1 THE APPLICATION OF GLP PRINCIPLES TO COMPUTERISED SYSTEMS FOREWARD
OECD DRAFT ADVISORY DOCUMENT 16 1 THE APPLICATION OF GLP PRINCIPLES TO COMPUTERISED SYSTEMS FOREWARD 1. The following draft Advisory Document will replace the 1995 OECD GLP Consensus Document number 10 More information This interpretation of the revised Annex
Reprinted from PHARMACEUTICAL ENGINEERING The Official Magazine of ISPE July/August 2011, Vol. 31 No. 4 www.ispe.org Copyright ISPE 2011 The ISPE GAMP Community of Practice (COP) provides its interpretation More information OECD SERIES ON PRINCIPLES OF GOOD LABORATORY PRACTICE AND COMPLIANCE MONITORING NUMBER 10 GLP CONSENSUS DOCUMENT
GENERAL DISTRIBUTION OCDE/GD(95)115 OECD SERIES ON PRINCIPLES OF GOOD LABORATORY PRACTICE AND COMPLIANCE MONITORING NUMBER 10 GLP CONSENSUS DOCUMENT THE APPLICATION OF THE PRINCIPLES OF GLP TO COMPUTERISED More information Considerations When Validating Your Analyst Software Per GAMP 5
WHITE PAPER Analyst Software Validation Service Considerations When Validating Your Analyst Software Per GAMP 5 Blair C. James, Stacy D. Nelson Introduction The purpose of this white paper is to assist More information OMCL Network of the Council of Europe QUALITY ASSURANCE DOCUMENT
OMCL Network of the Council of Europe QUALITY ASSURANCE DOCUMENT PA/PH/OMCL (08) 88 R VALIDATION OF COMPUTERISED SYSTEMS ANNEX 2: VALIDATION OF DATABASES (DB), LABORATORY INFORMATION MANAGEMENT SYSTEMS More information INTRODUCTION. This book offers a systematic, ten-step approach, from the decision to validate to
INTRODUCTION This book offers a systematic, ten-step approach, from the decision to validate to the assessment of the validation outcome, for validating configurable off-the-shelf (COTS) computer software More information Implementing Title 21 CFR Part 11 (Electronic Records ; Electronic Signatures) in Manufacturing Presented by: Steve Malyszko, P.E.
Implementing Title 21 CFR Part 11 (Electronic Records ; Electronic Signatures) in Manufacturing Presented by: Steve Malyszko, P.E. President & CEO Agenda Introduction Who is Malisko Engineering? Title More information Clinical database/ecrf validation: effective processes and procedures
TITOLO SLIDE Testo Slide Testo Slide Testo Slide Clinical database/ecrf validation: effective processes and procedures IV BIAS ANNUAL CONGRESS Padova September, 26 th 2012 PQE WORKSHOP: What's new in Computerized More information The FDA recently announced a significant
This article illustrates the risk analysis guidance discussed in GAMP 4. 5 By applying GAMP s risk analysis method to three generic classes of software systems, this article acts as both an introduction More information OMCL Network of the Council of Europe QUALITY ASSURANCE DOCUMENT
OMCL Network of the Council of Europe QUALITY ASSURANCE DOCUMENT PA/PH/OMCL (08) 69 3R Full document title and reference Document type VALIDATION OF COMPUTERISED SYSTEMS Legislative basis - CORE DOCUMENT More information ISCT Cell Therapy Liaison Meeting AABB Headquarters in Bethesda, MD. Regulatory Considerations for the Use of Software for Manufacturing HCT/P
ISCT Cell Therapy Liaison Meeting AABB Headquarters in Bethesda, MD September 10, 2009 David Doleski, Team Leader, Branch 2 Division of Manufacturing and Product Quality (DMPQ) Office of Compliance and More information Computer System Validation - It s More Than Just Testing
Computer System Validation - It s More Than Just Testing Introduction Computer System Validation is the technical discipline that Life Science companies use to ensure that each Information Technology application More information EUROPEAN COMMISSION HEALTH AND CONSUMERS DIRECTORATE-GENERAL. EudraLex The Rules Governing Medicinal Products in the European Union
EUROPEAN COMMISSION HEALTH AND CONSUMERS DIRECTORATE-GENERAL Public Health and Risk Assessment Pharmaceuticals Brussels, SANCO/C8/AM/sl/ares(2010)1064599 EudraLex The Rules Governing Medicinal Products More information unless the manufacturer upgrades the firmware, whereas the effort is repeated.
Software Validation in Accredited Laboratories A Practical Guide Gregory D. Gogates Fasor Inc., 3101 Skippack Pike, Lansdale, Pennsylvania 19446-5864 USA g.gogates@ieee.org www.fasor.com Abstract Software More information GOOD PRACTICES FOR COMPUTERISED SYSTEMS IN REGULATED GXP ENVIRONMENTS
PHARMACEUTICAL INSPECTION CONVENTION PHARMACEUTICAL INSPECTION CO-OPERATION SCHEME PI 011-3 25 September 2007 PIC/S GUIDANCE GOOD PRACTICES FOR COMPUTERISED SYSTEMS IN REGULATED GXP ENVIRONMENTS PIC/S More information GAMP5 - a lifecycle management framework for customized bioprocess solutions
GE Healthcare Life Sciences GAMP5 - a lifecycle management framework for customized bioprocess solutions imagination at work GE Healthcare s engineering department, Customized Bioprocess Solutions (CBS), More information Manual 074 Electronic Records and Electronic Signatures 1. Purpose
1. Purpose The purpose of this document is to provide an interpretation of FDA 21 CFR Part 11, Electronic Records; Electronic Signatures (ER/ES) and to provide guidance for acceptable practices in the More information How to implement a Quality Management System
How to implement a Quality Management System This whitepaper will help you to implement a Quality Management System (QMS), based on Good Manufacturing Practice (GMP), ISO 9001 or ISO 13485 within your More information Training Course Computerized System Validation in the Pharmaceutical Industry Istanbul, 16-17 January 2003. Change Control
Training Course Computerized System Validation in the Pharmaceutical Industry Istanbul, 16-17 January 2003 Change Control Wolfgang Schumacher Roche Pharmaceuticals, Basel Agenda Change Control Definitions More information Information Security Policy September 2009 Newman University IT Services. Information Security Policy
Contents 1. Statement 1.1 Introduction 1.2 Objectives 1.3 Scope and Policy Structure 1.4 Risk Assessment and Management 1.5 Responsibilities for Information Security 2. Compliance 3. HR Security 3.1 Terms More information GUIDELINES ON VALIDATION APPENDIX 5 VALIDATION OF COMPUTERIZED SYSTEMS
May 2016 Draft document for comment 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 GUIDELINES ON VALIDATION APPENDIX More information Organisation de Coopération et de Développement Économiques Organisation for Economic Co-operation and Development
Unclassified ENV/JM/MONO(2016)13 ENV/JM/MONO(2016)13 Unclassified Organisation de Coopération et de Développement Économiques Organisation for Economic Co-operation and Development 22-Apr-2016 English More information Computer System Validation for Clinical Trials:
Computer System Validation for Clinical Trials: Framework Standard Operating Procedure (F-SOP) Author: Tim Cross Version History: 0.1di DRAFT 24-April-2013 0.2 DRAFT 12-June-2013 Current Version: 1.0 17-June-2013 More information GAMP 4 to GAMP 5 Summary
GAMP 4 to GAMP 5 Summary Introduction This document provides summary information on the GAMP 5 Guide and provides a mapping to the previous version, GAMP 4. It specifically provides: 1. Summary of Need More information OPERATIONAL STANDARD
1 of 11 1. Introduction The International Safe Transit Association (ISTA), a non-profit association whose objective is to prevent product damage and excess packaging usage within the distribution environment. More information R214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION PROGRAM
The American Association for Laboratory Accreditation Document Revised: R214: Specific Requirements: Information Technology Testing Laboratory Accreditation July 13, 2010 Program Page 1 of 26 R214 SPECIFIC More information CONTENTS. List of Tables List of Figures
Prelims 13/3/06 9:11 pm Page iii CONTENTS List of Tables List of Figures ix xi 1 Introduction 1 1.1 The Need for Guidance on ERP System Validation 1 1.2 The Need to Validate ERP Systems 3 1.3 The ERP Implementation More information Guidance on Qualification of existing facilities, systems, equipment and utilities
QUALIFICATION_EXISTING_EQUIPMENT_FINAL page 1 / 16 1. Acknowledgement...3 2. Introduction...3 3. Scope...4 4. Regulatory requirements...4 5. Guidance...4 5.1 Risk Assessment... 4 5.2 Procedure... 7 5.3 More information Information Security Policies. Version 6.1
Information Security Policies Version 6.1 Information Security Policies Contents: 1. Information Security page 3 2. Business Continuity page 5 3. Compliance page 6 4. Outsourcing and Third Party Access More information DATA MANAGEMENT IN CLINICAL TRIALS: GUIDELINES FOR RESEARCHERS
Reference Number: UHB 139 Version Number: 2 Date of Next Review: 14 Apr 2018 Previous Trust/LHB Reference Number: N/A DATA MANAGEMENT IN CLINICAL TRIALS: GUIDELINES FOR RESEARCHERS Introduction and Aim More information A Pragmatic Approach to the Testing of Excel Spreadsheets
A Pragmatic Approach to the Many GxP critical spreadsheets need to undergo validation and testing to ensure that the data they generate is accurate and secure. This paper describes a pragmatic approach More information GCP INSPECTORS WORKING GROUP REFLECTION PAPER ON EXPECTATIONS FOR ELECTRONIC SOURCE DOCUMENTS USED IN CLINICAL TRIALS
European Medicines Agency London, 17 October 2007 Doc. Ref. EMEA/505620/2007 GCP INSPECTORS WORKING GROUP REFLECTION PAPER ON EXPECTATIONS FOR ELECTRONIC SOURCE DOCUMENTS USED IN CLINICAL TRIALS More information The use of computer systems
Technology Update Computer Systems Validation, Part 1 Software Purchase and GCP Compliance Teri Stokes Teri Stokes, PhD, is senior consultant and director of GXP International, 131 Sudbury Road, Concord, More information 4Sight Calibration Management Software
GE Measurement & Control Solutions 4Sight Calibration Management Software 4Sight calibration and maintenance management software provides visibility to the assets, data, and resources that affect maintenance, More information International GMP Requirements for Quality Control Laboratories and Recomendations for Implementation
International GMP Requirements for Quality Control Laboratories and Recomendations for Implementation Ludwig Huber, Ph.D. ludwig_huber@labcompliance.com Overview GMP requirements for Quality Control laboratories More information Guidance for Industry COMPUTERIZED SYSTEMS USED IN CLINICAL TRIALS
Guidance for Industry COMPUTERIZED SYSTEMS USED IN CLINICAL TRIALS U.S. Department of Health and Human Services Food and Drug Administration Center for Biologic Evaluation and Research (CBER) Center for More information BPA. Disclaimer. Applying Critical Thinking to the. Applications, Purchased Applications, and Web-Hosted Applications. RiskVal Life Cycle
BPA Applying Critical Thinking to the Validation of Spreadsheets, Access Applications, Purchased Applications, and Web-Hosted Applications IVT 11 th Annual Computer and Software Validation Conference April More information Sharon Strause 9/10/2010. 15 years with the
Manage Software Development, Testing, and Validation Presented by Sharon Strause, Senior Consultant EduQuest, Inc. IVT s Computer and Software Validation EU Conference The Hilton Dublin Dublin, Ireland More information Back to index of articles. Qualification of Computer Networks and Infrastructure
Back to index of articles Qualification of Computer Networks and Infrastructure R.D.McDowall McDowall Consulting Validation of computerised systems generally focuses on the providing documented evidence More information Computerized System Audits In A GCP Pharmaceutical Laboratory Environment
IVTGXP_july06.qxd 6/28/06 1:09 PM Page 36 Computerized System Audits In A GCP Pharmaceutical Laboratory Environment By Maintaining data integrity for both clinical laboratory processes and patient data More information Risk-Based Validation of Computer Systems Used In FDA-Regulated Activities
September 2, 2003 Risk-Based Validation of Computer Systems Used In FDA-Regulated Activities Purpose This document provides a summary of the requirements relating to use of computer-based systems in activities More information Best practices for computerised systems in regulated GxP environments.
PIC/S Logo PHARMACEUTICAL INSPECTION PH/W 01/2000 (DRAFT) CONVENTION January 2000 PHARMACEUTICAL INSPECTION CO-OPERATION SCHEME PIC/S Guidance Best practices for computerised systems in regulated GxP environments. More information How to Survive an FDA Computer Validation Audit
How to Survive an FDA Computer Validation Audit The Myth Within the pharmaceutical, biotech, and medical device industry there is much fear and concern over approaching FDA audits. The FDA strikes fear More information GOOD LABORATORY PRACTICE (GLP) GUIDELINES FOR THE VALIDATION OF COMPUTERISED SYSTEMS. Working Group on Information Technology (AGIT)
GOOD LABORATORY PRACTICE (GLP) GUIDELINES FOR THE VALIDATION OF COMPUTERISED SYSTEMS Working Group on Information Technology (AGIT) Release Date: 14 December 2007 Version: 02 AGIT - Validation of Computerised More information COTS Validation Post FDA & Other Regulations
COTS Validation Post FDA & Other Regulations TABLE OF CONTENTS 1. Abstract 3 2. What is COTS 3 3. Why should COTS require Validation? 3 4. Risk Based Approach 4 5. Validation Approach 6 6. Applicable Regulations More information 2.2 INFORMATION SERVICES Documentation of computer services, computer system management, and computer network management.
3 Audit Trail Files Data generated during the creation of a master file or database, used to validate a master file or database during a processing cycle. GS 14020 Retain for 3 backup cycles Computer Run More information ACCEPTANCE TEST PLAN DEPARTMENT of INFRASTRUCTURE, ENERGY and RESOURCES
DEPARTMENT of INFRASTRUCTURE, ENERGY and RESOURCES ACCEPTANCE TEST PLAN Version - DOCUMENT ACCEPTANCE and RELEASE More information Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.
INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing More information Considerations for validating SDS Software v2.x Enterprise Edition for the 7900HT Fast Real-Time PCR System per the GAMP 5 guide
WHITE PAPER SDS Software v2.x Enterprise Edition Considerations for validating SDS Software v2.x Enterprise Edition for the 7900HT Fast Real-Time PCR System per the GAMP 5 guide This white paper describes More information 074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements
Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality More information Customer name. Installation Qualification Version 1.0x of gg/mm/aa. Department Signature Name & Function Date
FOFx NF Nzzzzz name Version 1.0x of gg/mm/aa Document and Protocol Preparation Qualitech Srl ss. 235 km 8 27010 Albuzzano (PV) Italy Written by: Tel. +39 0382 480016 Fax +39 0382 481126 E_mail nfo@qualitechsrl.com More information Validating Enterprise Systems: A Practical Guide
Table of Contents Validating Enterprise Systems: A Practical Guide Foreword 1 Introduction The Need for Guidance on Compliant Enterprise Systems What is an Enterprise System The Need to Validate Enterprise More information Validating Cloud. June 2012 Merry Danley
Validating Cloud June 2012 Merry Danley Agenda Validation of Cloud Introduction Environments Definitions Manage Risk by Designation of Systems Why Go Cloud Success Dependencies Validation Personal Experience More information DeltaV Capabilities for Electronic Records Management
January 2013 Page 1 DeltaV Capabilities for Electronic Records Management This paper describes DeltaV s integrated solution for meeting FDA 21CFR Part 11 requirements in process automation applications More information Guidance for Industry Computerized Systems Used in Clinical Investigations
Guidance for Industry Computerized Systems Used in Clinical Investigations U.S. Department of Health and Human Services Food and Drug Administration (FDA) Office of the Commissioner (OC) May 2007 Guidance More information Software Validation in Clinical Trial Reporting: Experiences from the Biostatistical & Data Sciences Department
Software Validation in Clinical Trial Reporting: Experiences from the Biostatistical & Data Sciences Department Andrea Baker Senior Programmer GlaxoSmithKline SeUGI 19 Florence May 29-June 1 2001 Introduction More information TIBCO Spotfire and S+ Product Family
TIBCO Spotfire and S+ Product Family Compliance with 21 CFR Part 11, GxP and Related Software Validation Issues The Code of Federal Regulations Title 21 Part 11 is a significant regulatory requirement More information Software Verification and Validation
Software Verification and Validation Georgia L. Harris Carol Hockert NIST Office of Weights and Measures 1 Learning Objectives After this session, using resources and references provided, you will be able More information SCHEDULE 2. Core It Services SOR
SCHEDULE 2 Core It Services SOR The Agreement V5.0 - In Confidence - Page 1 of 46 Table of Contents 1 Appendices... 4 2 Introduction to the Statement of Requirements... 5 2.1 Introduction... 5 2.2 TfL More information EMA Clinical Laboratory Guidance - Key points and Clarifications PAUL STEWART
EMA Clinical Laboratory Guidance - Key points and Clarifications PAUL STEWART Framework Labs generate data that are used to make decisions on the safety and efficacy of medicinal products; consequently, More information Pharma IT journall. Regular Features
Pharma IT journall The dedicated publication for those working with Computerised Systems, Processes and Software in the Pharmaceutical, Biotechnology, Medical Device, Clinical Research and Supporting Industries More information Compliance Response SIMATIC SIMATIC PCS 7 V8.1. Electronic Records / Electronic Signatures (ERES) Edition 03/2015. Answers for industry.
SIMATIC SIMATIC PCS 7 V8.1 Electronic Records / Electronic Signatures (ERES) Compliance Response Edition 03/2015 Answers for industry. Compliance Response Electronic Records / Electronic Signatures (ERES) More information Monitoring manufacturing, production and storage environments in the pharmaceutical industry
Application Description AD/RandC/005-EN Monitoring manufacturing, production and storage environments in the pharmaceutical industry - Provides independent verification and validation of the manufacture, More information ITIL A guide to service asset and configuration management
ITIL A guide to service asset and configuration management The goal of service asset and configuration management The goals of configuration management are to: Support many of the ITIL processes by providing More information DeltaV Capabilities for Electronic Records Management
September 2004 Page 1 An integrated solution for meeting FDA 21CFR Part 11 requirements in process automation applications using a configurable off-the-shelf (COTS) solution Emerson Process Management. More information Using the ISPE s GAMP Methodology to Validate Environmental Monitoring System Software
Using the ISPE s GAMP Methodology to Validate Environmental Monitoring System Software TEST DOCUMENTS DETAILED DOCUMENTS FUNCTIONAL SPECS USER REQUIREMENTS Introduction Continuous Monitoring Systems (CMS) More information Request for Proposal for Application Development and Maintenance Services for XML Store platforms
Request for Proposal for Application Development and Maintenance s for ML Store platforms Annex 4: Application Development & Maintenance Requirements Description TABLE OF CONTENTS Page 1 1.0 s Overview... More information ORACLE PROCESS MANUFACTURING QUALITY MANAGEMENT
ORACLE PROCESS MANUFACTURING QUALITY MANAGEMENT KEY FEATURES Automated stability study management Lot expiration handling and retesting Potency or variability management Quality holds during receiving More information Auditing Electronic data capture in clinical trials (EDC) The auditor s view
Auditing Electronic data capture in clinical trials (EDC) The auditor s view Where do auditors see such systems? Regulatory basic documents Key requirements Validation Auditfindings - Computer-Systems More information Full Compliance Contents
Full Compliance for and EU Annex 11 With the regulation support of Contents 1. Introduction 2 2. The regulations 2 3. FDA 3 Subpart B Electronic records 3 Subpart C Electronic Signatures 9 4. EU GMP Annex More information GAMP 5 and the Supplier Leveraging supplier advantage out of compliance
GAMP 5 and the Supplier Leveraging supplier advantage out of compliance Paul Osborne Performance PharmaTech Ltd. Overview This document is designed to assist suppliers who wish to sell computer based equipment More information LabChip GX/GXII with LabChip GxP Software
Regulatory Compliance LabChip GX/GXII with LabChip GxP Software Supporting Regulatory Compliance Caliper LabChip GX/GXII suite of instruments provides automated electrophoresis to analyze quality, size, More information STS Federal Government Consulting Practice IV&V Offering
STS Federal Government Consulting Practice IV&V Offering WBE Certified GSA Contract GS-35F-0108T For information Please contact: gsa70@stsv.com 2007 by STS, Inc. Outline Background on STS What is IV&V? More information Calibration & Preventative Maintenance. Sally Wolfgang Manager, Quality Operations Merck & Co., Inc.
Calibration & Preventative Maintenance Sally Wolfgang Manager, Quality Operations Merck & Co., Inc. Calibration: A comparison of two instruments or measuring devices one of which is a standard of known More information Guidance for electronic trial data capturing of clinical trials
Guidance for electronic trial data capturing of clinical trials 1 st November, 2007 Japan Pharmaceutical Manufacturing Association pg. 1 Table of Contents 1. Background... 3 2. Purpose... 3 3. Scope... More information Procedure for Assessment of System and Software
Doc. No: STQC IT/ Assessment/ 01, Version 1.0 Procedure for Assessment of System and Software May, 2014 STQC - IT Services STQC Directorate, Department of Electronics and Information Technology, Ministry More information Declaration of Conformity 21 CFR Part 11 SIMATIC WinCC flexible 2007
Declaration of Conformity 21 CFR Part 11 SIMATIC WinCC flexible 2007 SIEMENS AG Industry Sector Industry Automation D-76181 Karlsruhe, Federal Republic of Germany E-mail: pharma.aud@siemens.com Fax: +49 More information Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor More information U. S. Department of Energy Consolidated Audit Program Checklist 5 Laboratory Information Management Systems Electronic Data Management
U. S. Department of Energy Consolidated Audit Program Checklist 5 Laboratory Information Management Systems Electronic Data Management Revision 4.0 February 2014 Use of this DOECAP checklist is authorized More information Discussion Paper on the Validation of Pharmacovigilance Software provided via SaaS
Discussion Paper on the Validation of Pharmacovigilance Software provided via SaaS June 2012 K Edmonds Page 1 of 10 Page 2 of 10 Contents 1. Introduction... 4 2. Quality Statement ISO 9001:2008... 4 3. More information Installation and Operational Qualification Protocol (Reference: SOP )
Project Name Equipment Process Line/Location Project Number Serial Number Model Number Protocol number WRITTEN BY: REVIEWED BY: Position APPROVAL TO EXECUTE: Position: PROTOCOL COMPLETION APPROVAL: Position: More information Network Qualification: What Is it; What Does it Involve?
JVT_May2007.qxd 4/23/07 8:04 AM Page 210 Network Qualification: What Is it; What Does it Involve? BY ESRA GUVEN, B.Sc.EE, PMP, CCNA WHAT IS A NETWORK? The Food and Drug Administration (FDA) defines a network More information Validation and Part 11/Annex 11 Compliance of Computer Systems
Validation and Part 11/Annex 11 Compliance of Computer Systems by Dr. Ludwig Huber 05 & 06 June 2013, Elite World Hotels, Istanbul - TURKEY Why to attend Computer systems should be validated to demonstrate More information Business Operations. Module Db. Capita s Combined Offer for Business & Enforcement Operations delivers many overarching benefits for TfL:
Module Db Technical Solution Capita s Combined Offer for Business & Enforcement Operations delivers many overarching benefits for TfL: Cost is reduced through greater economies of scale, removal of duplication More information Adoption by GCP Inspectors Working Group for consultation 14 June 2011. End of consultation (deadline for comments) 15 February 2012
10 December 2013 EMA/INS/GCP/600788/2011 Compliance and Inspection Reflection paper on the use of interactive response technologies (interactive voice/web response systems) in clinical trials, with particular More information Using ISO 15489 as an Audit Tool
Using ISO 15489 as an Audit Tool ISO 15489, the first international standard devoted to records management, provides a comprehensive and practical basis for auditing full and partial records management More information Document Number: SOP/RAD/SEHSCT/007 Page 1 of 17 Version 2.0
Standard Operating Procedures (SOPs) Research and Development Office Title of SOP: Computerised Systems for Clinical Trials SOP Number: 7 Version Number: 2.0 Supercedes: 1.0 Effective date: August 2013 More information Supplement to the Guidance for Electronic Data Capture in Clinical Trials
Supplement to the Guidance for Electronic Data Capture in Clinical Trials January 10, 2012 Drug Evaluation Committee, Japan Pharmaceutical Manufacturers Association Note: The original language of this More information Regulatory Asset Management: Harmonizing Calibration, Maintenance & Validation Systems
Regulatory Asset Management: Harmonizing Calibration, Maintenance & Validation Systems 800.982.2388 1 Introduction Calibration, maintenance and validation activity, despite operating within the same department More information 8. Master Test Plan (MTP)
8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across More information GUIDE TO GOOD MANUFACTURING PRACTICE FOR MEDICINAL PRODUCTS ANNEX 15 *
PHARMACEUTICAL INSPECTION CONVENTION PHARMACEUTICAL INSPECTION CO-OPERATION SCHEME PS/INF 11/2015 1 April 2015 GUIDE TO GOOD MANUFACTURING PRACTICE FOR MEDICINAL PRODUCTS ANNEX 15 * * Entry into force: More information NABL NATIONAL ACCREDITATION
NABL 160 NABL NATIONAL ACCREDITATION BOARD FOR TESTING AND CALIBRATION LABORATORIES GUIDE for PREPARING A QUALITY MANUAL ISSUE NO. : 05 AMENDMENT NO : 00 ISSUE DATE: 27.06.2012 AMENDMENT DATE: -- Amendment More information System Development and Life-Cycle Management (SDLCM) Methodology. Approval CISSCO Program Director
System Development and Life-Cycle Management (SDLCM) Methodology Subject Type Standard Approval CISSCO Program Director A. PURPOSE This standard specifies content and format requirements for a Physical More information An Approach to Records Management Audit
An Approach to Records Management Audit DOCUMENT CONTROL Reference Number Version 1.0 Amendments Document objectives: Guidance to help establish Records Management audits Date of Issue 7 May 2007 INTRODUCTION More information IT General Controls Domain COBIT Domain Control Objective Control Activity Test Plan Test of Controls Results
Acquire or develop application systems software Controls provide reasonable assurance that application and system software is acquired or developed that effectively supports financial reporting requirements. More information 2017 © DocPlayer.net Privacy Policy | Terms of Service | Feedback