Complying with Global ERES Regulations in the Life Sciences Industry

Size: px
Start display at page:

Download "Complying with Global ERES Regulations in the Life Sciences Industry"

Transcription

1 SAP for Life Sciences Complying with Global ERES Regulations in the Life Sciences Industry Table of Contents 5 Know the Rules 7 ERES Regulations and SAP ERP 21 SAP Software Quality 30 Why Choose SAP Solutions for ERES Compliance 32 Appendixes About the Author Dr. Christoph Roller is solution manager in the global industry business solutions group for life sciences at SAP.

2 By complying with global regulations, your life sciences company can enjoy the benefits of increased overall efficiency and reduced costs for handling and storing traditional paper records. But whatever life sciences business you conduct, there is even more that you can do. With solutions such as the SAP for Life Sciences solution portfolio, you can comply with key electronic signature regulations and limit the costs involved in compliance. TODAY S APPROACH TO COMPLIANCE To compete in this market, your life sciences company needs to comply with various regulations, depending on which markets you do business in. These regulations include those of the U.S. Food and Drug Administration (FDA) such as 21 CFR Part 11 Electronic Records; Electronic Signature the European Commission s Annex 11 Computerized Systems, and Japan s PFSB Notification, No , Electronic Records/Electronic Signature. Regulatory authorities across the globe have acknowledged the importance of computerized systems and records within the life sciences industry. These regulations all share the same intent of ensuring the integrity of electronic data and records. However, applying these requirements to the numerous computerized systems within your life sciences company can translate into millions of dollars in project costs to validate these systems. Also, maintaining these systems in a validated state for their productive lifetime requires significant annual costs. Systems-Based Inspection Approach More and more, regulatory authorities globally are taking a risk-based approach to determine which computer systems are the most critical. They then follow a systems-based approach that aims at conducting and evaluating inspections with regard to specific systems to evaluate risks. For example, a global regulatory agency like the FDA s inspection compliance program consists of six major systems, which is similar to the other agency inspection programs: Quality system Facilities and equipment system Materials system Production system Packaging and labeling system Laboratory control system These systems are not considered discrete entities but instead are part of an integrated system model. The idea underlying this approach is that deficiencies in one system will affect all other systems as well. The integrated systems-based inspection approach recognizes the widespread use of computers to support each company s quality initiatives. Therefore, regulatory agencies review the qualification, validation, and security of integrated computer solutions much more closely than that of stand-alone systems during an inspection. 2 /45

3 Regulatory agencies review the qualification, validation, and security of integrated computer solutions much more closely than that of stand-alone systems during an inspection. Cost of Compliance Figures 1 and 2 illustrate the cost of compliance and noncompliance. Figure 1: Model of Compliance Costs Cost of noncompliance (NC$) Cost NC$ > C$ Optimal area to balance risk versus benefit Not compliant Compliant Overcompliant Compliance Figure 2: Model of Compliance Costs Reduced Through Process Optimization Cost of noncompliance (NC$) Sum of both exponential curves (total $) Sum of both exponential curves (total $) Cost of compliance (C$) C$ > NC$ The goal is to operate in this area. Cost of compliance (C$) Cost of compliance curve enhanced through process optimization and standardization On the basis of global regulations for electronic records and electronic signatures, companies that fail to establish adequate control of their computerized systems face sanctions as for any other significant noncompliance of good practices. Figure 1 shows two opposing exponential curves depicting the cost of noncompliance and compliance. The cost of noncompliance is determined to be a function of regulatory agencies enforcement actions including warning letters, import detention, and consent decree and the time and resources required to remediate regulatory bodies observations. The cost of compliance is determined to be a function of time and resources. The graph also shows that the state of compliance is not dichotomous. Rather, compliance is a state of operation determined by a company s interpretation of pertinent global regulations and the corporate culture applied to the various business processes within the quality system. The three levels of compliance are therefore subjective as depicted by the range for each level. Figure 2 illustrates the beneficial movement of the cost of compliance curve manifested by process optimization and other internal cost reductions including consolidation of IT systems. Therefore, companies can choose to improve their level of compliance in order to significantly reduce costs. Cost NC$ > C$ Vigilance and maturity to manifest this beneficial movement C$ > NC$ Maintenance of same level of compliance with reduced cost Not compliant Compliant Overcompliant Compliance 3 /45

4 Companies can choose to improve their level of compliance in order to significantly reduce costs. A Win-Win Proposition for Life Sciences Many life sciences companies have taken advantage of this win-win proposition and leveraged their SAP ERP application infrastructure to support the following: Enterprise asset Enterprise quality Supplier quality Laboratory information systems Problem reporting and execution of corrective action and preventive action Manufacturing execution and electronic batch records Qualifications (training) Warehouse Customer relationship Product lifecycle Sales and distribution Materials Environment, health, and safety Additionally, specific SAP solutions are available that promote various regulatory and compliance operations, such as: Integrated product development and compliance Supply chain execution Supply network traceability and supply chain integrity Contract Service excellence for medical devices Compliant manufacturing operations Contract manufacturing for life sciences companies Calibration and equipment maintenance Contract lifecycle and compliance Enterprise information Pharmaceutical, medical diagnostics, medical devices, and biotechnology companies continue to promote regulatory compliance, while reducing their costs and maximizing their ROI, by appropriately leveraging their existing systems and implementing new systems and solutions as needed. 4 /45

5 Know the Rules Many functions and features of SAP ERP support technical compliance with global electronic record and electronic signature (ERES) regulations. ERES REQUIREMENTS FROM GLOBAL REGULATORY AGENCIES Many regulations deal with electronic records and electronic signatures. FDA 21 CFR Part 11 FDA regulation 21 CFR Part 11 Electronic Records; Electronic Signatures; Final Rule (referred to here as Part 11) was the result of a six-year effort by the FDA (with input from the industry). The goal was to supply all FDA-regulated companies with requirements on how to maintain paperless (that is, electronic) record systems while still complying with good clinical, laboratory, and manufacturing practices. These include: Good manufacturing practice (GMP): 21 CFR 110 (food), 210 (drugs in general, also includes good manufacturing practices for biologics), 211 (finished pharmaceuticals), and 820 (medical devices) Good laboratory practice: 58 Good clinical practice: 50, 54, and 56 The regulation also details specific requirements for electronic and digital signatures because the FDA considers these signatures to be legally binding. Since its publication in 1997, this regulation has been subject to evolving interpretations by both the FDA and industry. In February 2003, the FDA withdrew all Part 11 guidelines and the Compliance Policy Guide. The Part 11 rule is still valid, but these accompanying guidelines are withdrawn. The reasons for the withdrawal are discussed in the FDA document from August 2003, Guidance for Industry Part 11, Electronic Records; Electronic Signatures Scope and Application, as follows: Concerns have been raised that some interpretations of the part 11 requirements would (1) unnecessarily restrict the use of electronic technology in a manner that is inconsistent with FDA s stated intent in issuing the rule, (2) significantly increase the costs of compliance to an extent that was not contemplated at the time the rule was drafted, and (3) discourage innovation and technological advances without providing a significant public health benefit. These concerns have been raised particularly in the areas of part 11 requirements for validation, audit trails, record retention, record copying, and legacy systems. EU GMP Annex 11: Computerized Systems This regulation states the following: Electronic records may be signed electronically. Electronic signatures are expected to: a. Have the same impact as handwritten signatures within the boundaries of the company b. Be permanently linked to their respective record c. Include the time and date that they were applied 5 /45

6 Pharmaceutical, medical diagnostics, medical devices, and biotechnology companies promote regulatory compliance, while reducing their costs and maximizing their ROI, by appropriately leveraging existing systems and implementing new solutions. ANVISA (Brazil): ANVISA Resolution RDC n. 17 The Technical Regulation of Good Manufacturing Practices of Drugs per the ANVISA Resolution says the following: Article 223. During the production process, all steps undertaken should be recorded, looking at the initial time and final implementation of each operation. The record of implementation of these steps must be properly dated by the executors, clearly identified by signature or electronic password, and ratified by the area supervisor. PFSB/ELD Notification No of Japan In Japan, the Guideline on Control of Computerized Systems in Drug Manufacturing Regulatory Guide provides a number of requirements. These include guidelines for electromagnetic records and electronic signatures used for documents and source documents relevant to applications, notifications, and reports for approval or licensing of drugs, quasidrugs, cosmetics and medical devices, and registrations of conformity assessment bodies. PHARMACEUTICAL CGMPS: A RISK-BASED APPROACH Global regulatory agencies like the FDA have enhanced the regulation of pharmaceutical manufacturing and product quality by applying a scientific and risk-based approach to product quality regulation. This initiative incorporates an integrated quality-systems approach to current good manufacturing practice (cgmp). Regulatory agencies have been developing a more systematic and rigorous, risk-based approach toward compliance and using good science. A justifiable and documented risk assessment, and one that is defensible, has become a predominant theme within recent initiatives of global regulatory agencies. Ultimately, your company must comply with applicable rules. Records that agencies require be maintained or submitted must remain secure and reliable in accordance with the predicate rules. In an agency inspection, the inspection of any computerized system includes a review of the system documentation. The documentation is required to demonstrate that the regulated activities controlled by a computerized system can be reliably performed and reliably repeated as the user intends and as detailed by the system specifications. Regulated records must have the ability to be written to media and recovered without corrupting the original data, and audit trails must document the computer s action related to any changes to the data. As with any regulated processes, computer processes are required to show documented validation, and any changes to the system must be tested and documented through a change control process. This testing needs to be rigorous and designed to stress the system. Documented training of personnel who were involved with system development, validation, deployment, and maintenance is the basic premise of all regulated activities. This is exactly what the life sciences industry does for all processes. 6 /45

7 ERES Regulations and SAP ERP FUNCTIONALITY IN SAP ERP THAT MAY BE REGULATED The determination of whether a transaction performed in SAP ERP has regulatory compliance implications is directly dependent on the business process that is making use of the transaction. Creating a purchase order for sodium chloride to be used for melting ice and snow is drastically different than creating a purchase order for sodium chloride to use in your manufacturing process. The business processes and the subsequent records requirements for materials used in the manufacturing process are subject to the predicate rules associated with the cgmp. The business process that your life science company uses to perform operations must comply with applicable FDA regulations governing good clinical practices, good manufacturing practices, good laboratory practices, and good deployment practices, together referred to as GxP. These regulations require that you retain certain records and documentation to support these activities and demonstrate compliance. When your company uses a computerized system to support execution of all or part of your business processes, and that system creates, modifies, maintains, or transmits records, those records are subject to regulatory requirements. And you need system controls to protect the accuracy, completeness, authenticity, and reliability of those records. SAP ERP is a transaction-based software system. These transactions, when mapped to the business process flows that they use for execution, can be assessed for regulatory relevance. By identifying the tenets of the applicable regulations and attributing them to the corresponding steps of the business process, you can determine the regulated SAP ERP application transactions. The following areas have consistently been shown to be relevant to regulatory issues. Logistics include: Materials Plant maintenance Production planning Production planning for process industries Quality Sales and distribution Logistics execution Environment, health, and safety Human resources and training information Warehouse Central functions include: Batch Handling unit Document Cross-application components include: Engineering change Classification Document Electronic records (audit trail) Digital signature Notifications Records and case Master data governance Business processes addressed by the SAP NetWeaver technology platform include: Audit trail (BC-SRV-ASF-AT) Digital signature (CA-DSG) 7 /45

8 Functional areas that have consistently been demonstrated to be excluded from the FDA scope are finance (financial accounting, controlling, and asset components) and planning (demand, forecasting, profitability analysis, and sales and operations planning components). Appendixes 1 and 2 contain the SAP ERP and FDA cgmp functionality matrix for both pharmaceuticals and medical devices. These matrixes illustrate how SAP ERP promotes compliance with these regulations and provides guidance as to what functionality (and electronic records) may be regulated by the FDA. To demonstrate regulatory compliance, you must document the assessment performed to determine the regulatory applicability of the transaction. The following table features a sample of a regulatory assessment applicable for a pharmaceutical manufacturer. Tcode Description 21 CFR Part 211 QE01 Record results , , , , and QE02 Change results , , , , and The following table is a sample of a regulatory assessment applicable for a medical device manufacturer. Tcode Description 21 CFR Part 820 QE01 Record results and QE02 Change results , , and Assessing the applicability of regulations allows for testing that the electronic record requirements and, if applicable, the electronic signature require ments associated with the records created, modified, or maintained by these transactions are compliant with regulatory requirements. Conversely, if the assessment cannot identify a specific regulatory tenet, the records associated with that transaction code are not considered to be relevant to regulatory issues and therefore are not subject to the same regulatory records requirements. Your life sciences company can dramatically reduce validation costs by performing this assessment and using the results during implementation projects. You can realize additional benefits during the production use of the system when you introduce changes to processes and functionality through change control. 8 /45

9 ELECTRONIC RECORDS In general, global regulatory agencies define an electronic record as follows: information created, stored, generated, received, or communicated by electronic means in a form that a person can perceive and that can be accurately reproduced or distributed by a computer system. If you apply this comprehensive definition to SAP ERP, you find various types of electronic records, such as: Configuration within the implementation guide Transports and business configuration sets used to migrate configuration from one software system to another Master data such as the material master, vendor, resource, recipe, and customer Business processing objects such as purchase orders, process orders, and inspection lots Electronic records for business processes or transaction execution, such as material documents Electronic or digital signatures Other electronic record types maintain change and deletion (that is, audit trail) information for the objects in SAP ERP mentioned above. These include: Change master record (engineering change component) Change document objects Table logging Change Master Record The change master record is a master record that contains information necessary for the and control of changes. A change master record captures the changes made to master data through the engineering change component in SAP ERP. Figure 3 illustrates the master data or object types that you can manage using engineering change. Figure 3: Linked Object Types in Engineering Change Management Master data Material master Substance master Dangerous goods Bills of materials Materials Equipment Sales order Functional location Document structure Task lists Routings Master recipes Inspection plan Equipment task list General maintenance Reference rate routings Reference operation set Documents Standard operations procedure Material safety data sheets Classification system Classes Characteristics Variant configuration Configuration profile Object dependencies 9 / 10

10 The change master record provides a full audit trail or change history of master data and contains data of a descriptive character (such as the reason for the change). It also contains control data (such as effectivity data and object type indicators). Besides this data that the user maintains, there is also data that is automatically updated by the software system ( data). Change Document Object A change document logs changes to a business object. A change document object is defined for a certain business document, captures changes to fields within a changing transaction, and writes this information to a unique record. This record is date and time stamped and maintains the old and new values for each of the fields that have been changed, in addition to the user ID of the person who made the change. SAP ERP runs a report to query and display the audit trail record. Change document objects are available for most of the important business documents. They may require configuration for activation. Figure 4 illustrates a change document object record for a resource substitution within a master recipe. Figure 4: Example of a Change Document Object for Master Recipe Change 10 /45

11 Table Logging Where change masters or change document objects do not exist for a certain business document, you need an alternative method for maintaining an audit trail. Activating the flag log data changes in the technical settings of the database table captures all the changes made to this table and writes this information into a unique record maintained within the DBTABLOG table. Any transaction executed within SAP ERP includes multiple tables where the data is recorded and maintained. Therefore, to view the complete audit trail, you can run a report to query and display each record associated with a specific event. The report provides all the required information for the audit trail, including system date and time stamps and the old and new values for each of the fields that have been changed within each table. The report can also provide the full, printed name of the user instead of the user ID. Figure 5 illustrates the table log record. Table logging may affect system performance, depending on the number of records that are generated. However, table logging is required only in some instances. You should review system configuration when table logging requirements have been identified. Figure 5: Output of Table Log and Change Document Log 11 /45

12 Audit Trail The audit trail (logging) component enables you to log and evaluate changed data in the system. The audit trail facilitates a detailed, consistent, and traceable description of your production processes. You can change logging settings intuitively and without technical modification and carry out an evaluation of the changed data that conforms to FDA requirements. The audit trail is a component of SAP NetWeaver (BC-SRV-ASF-AT) that you can use to log all SAP ERP applications. In addition to the audit trail, the electronic records component in SAP_APPL also provides logging functions (although only for applications in SAP_APPL). Compared with the electronic records component, the audit trail offers enhanced functions plus the advantage that you can use it to log data of all the applications of SAP Business Suite software (as of release 7.0). However, you can use only one of the two components. Parallel use is not possible. If you are already using electronic records, you can switch to the audit trail functions. For further information, refer to the manual Audit Trail (SAP NetWeaver) or Electronic Records (SAP ERP) at help.sap.com. Date and Time Stamp SAP ERP uses Coordinated Universal Time (UTC) for change master record, change document objects, and table-logging activities. UTC is unique and unequivocal. To compare the local times of users in different time zones, SAP software represents times differently externally and internally. External representation of time corresponds to a context-dependent local time. For example, time is represented in Germany in Central European Time and in New York in Eastern Standard Time. SAP software normalizes the internal system time to UTC, which serves as a reference time. UTC corresponds to Greenwich Mean Time. By converting all local, relative times to absolute times based on UTC, the software can compare times and use them in calculations. If you have locations in multiple time zones, you need procedures to define the time zone of the application server and describe how the date and time stamp is to be interpreted by each site. In addition, the procedures should include daylight saving time requirements. These procedures should be included in performance qualification testing. Many functions and features of SAP ERP support technical compliance with global electronic records and electronic signatures (ERES) regulations. 12 /45

13 Electronic Copies for Inspection Because of the systems-based inspection approach of global regulatory agencies, SAP ERP is often included in GMP inspections, as it is routinely used to support the quality system and all other subsystems. You can print reports and electronic records or export them into several industry-standard formats such as Adobe PDF and XML. Retention and Maintenance of Electronic Records You can maintain all electronic records in the active database or archive them to accommodate all required retention periods even when software is upgraded. You can secure access to these records using authorization profiles that are standard in SAP software. In addition, SAP ERP maintains the link between electronic signatures executed to electronic records even after archiving. Hybrid Systems Companies using hybrid systems must comply with ERES requirements. Information that you have recorded in SAP software or activities that you have performed directly in SAP software can be printed or exported into industry-standard formats such as Adobe PDF and XML. An example of a hybrid system with SAP software is a batch record that includes printouts of process instruction sheets that have been executed by operators and quality personnel. Another hybrid system with a different twist is part of an organization s corrective action and preventive action (CAPA) program that uses the quality notification component as the CAPA solution. In this example, paper documents with handwritten approvals, including engineering and laboratory reports, are scanned into the content server component and attached to investigations within SAP ERP. Thus, an investigation within SAP ERP contains electronic records, including electronic signatures, executed as part of the lifecycle of the investigation and electronic images of documents that contain handwritten approvals. All hybrid systems require procedural controls to maintain compliance and need to be included in the scope of your organization s computerized system validation. SAP ERP is a transaction-based software system. These transactions, when mapped to the business process flows that they use for execution, can be assessed for regulatory relevance. 13 /45

14 Digital signatures in SAP ERP satisfy all applicable ERES requirements. ELECTRONIC SIGNATURE Many agencies such as the FDA and EU authorities consider electronic records equivalent to paper records and electronic signatures equivalent to traditional handwritten signatures. For the FDA, the ERES guidance documents specify that these requirements are defined by the predicate rule, such as cgmp for finished pharmaceuticals (21 CFR Part 211) and medical devices (21 CFR Part 820). Note that some passages implicitly call for signatures, for example, wherever the words approved, signed, initialed, authorized, rejected, or verified are used. Electronic and Digital Signatures in SAP ERP Electronic and digital signature definitions are shown in 21 CFR Part 11 as follows: Electronic signature A computer data compilation of any symbol or series of symbols executed, adopted, or authorized by an individual to be the legally binding equivalent to the individual s handwritten signature Digital signature An electronic signature based on cryptographic methods of originator authentication, computed by using a set of rules and a set of parameters such that the identity of the signer and the integrity of the data can be verified Closed system An environment in which system access is controlled by persons who are responsible for the content of electronic records that are on the system Open system An environment in which system access is not controlled by persons who are responsible for the content of electronic records that are on the system Digital Signature Throughout the SAP ERP application, the term digital signature is referenced in each dialog screen during signature execution and electronic record reporting (see Figures 6 and 7). The term electronic signature is not referenced within SAP ERP. This is based on SAP s interpretation of the ERES signature definitions concerning the use of cryptographic encryption techniques such as Public-Key Cryptography Standard #7 (PKCS #7). Public-Key Cryptography Standards are specifications for secure information exchange using the Internet, and PKCS #7 is the standard format in the market. All signatures executed within SAP ERP use crypto graphic encryption techniques. Therefore, SAP defines all signatures within SAP ERP to be digital signatures even when the SAP ERP application is used in a closed system. To ensure the integrity of signatures within an electronic system and protect against falsification and data corruption, the FDA requires that the system actively detect and prevent unauthorized access. This includes reporting these attempts to the system security unit. Many agencies equate the reporting and response of unauthorized access to the way individuals would respond to a fire alarm, as mentioned in the Part 11 rule. To satisfy the requirements defined in ERES, SAP ERP provides many safeguards. 14 /45

15 When the number of failed attempts (for either logon or signature) is exceeded, SAP ERP prevents the user from further access without intervention from the security administration. Note that the number of failed attempts allowed is configurable: SAP ERP generates and sends an express message to a defined distribution list to notify the security administration immediately. In addition, you can interface any Messaging Application Programming Interface (MAPI) compliant messaging system to SAP ERP to send this message externally to systems such as Microsoft Exchange or even a paging system. The security audit log maintains an electronic record of all failed attempts (for either logon or signature). SAP ERP also generates electronic records for the locking and unlocking of users. System signature with authorization by user ID and password has the following attributes: It has been available in SAP software beginning with the first shipment of release 4.6C of SAP R/3 software. It includes the use of the PKCS #7 standard. No external security product is necessary. When logging on, users identify themselves by entering their user IDs and passwords. SAP software then executes the digital signature. The username and ID are part of the signed document. Digital user signature with verification has the following attributes: It has been available in SAP software beginning with the first shipment of SAP R/3 4.0B. An external (third-party) security product is necessary. Users execute digital signatures them selves using their private keys. The executed signatures are automatically verified. Information is available from global.sap.com /partners/directories/searchsolution.epx. Cryptographic hardware and biometrics, using such elements as smart cards and fingerprints, must support the PKCS #7 standard data format. This mechanism is based on Secure Store and Forward mechanisms. Digital signatures in SAP ERP satisfy all applicable ERES requirements. (Please refer to the summary table in Appendix 5 titled How Does SAP ERP Comply with Part 11? ) SAP ERP includes a digital signature tool. This powerful functionality enables you to include signature functionality in any transaction or supported business process within SAP ERP. 15 /45

16 Digital signatures are already implemented in SAP ERP for the following supported business processes and components: Production planning for process industries (PP-PI) Process step completion within process instruction sheets and acceptance of process values outside predefined tolerance limits (transaction code CO60) Production planning for process industries (PP-PI) The user of the industry service sheet for the soft logon process can display only the process industry sheet, and the dialog user must log in and work on a process industry sheet (trans action code CO60). Execution steps (transaction code SXS) repository The status change (transaction code for standard execution step repository) is as follows: approval, withdraw, and obsolete. Engineering change (ECM) The status change of the engineering change order is as follows: change number as well as create and change (transaction codes CC01 and CC02). Engineering change (ECM) The status change of object records (transaction code CC22) allows conversion of a change request to a change order in engineering change. Electronic batch record approval (transaction code COEBR) Quality (QM): inspection lot and results recording (transaction codes QE01, QE02, and QE51N) Quality (QM): usage decision (quality disposition), as well as record and change (transaction codes QA11 and QA12) Quality (QM): physical sample drawing (transaction codes QPR1 and QPR2) Quality (QM): Quality notifications, as well as create and change (transaction codes QM01 and QM02) Document system (DMS): create or change (transaction codes CV01N and CV02N) Potential failure mode and effects analysis (FMEA): preventive action and detection action (transaction codes QM_FMEA and QM_FMEAMONITOR) Audit : preventive and corrective measures (transaction codes PLMD_AUDIT and PLM_AUDITMONITOR) Maintenance processing (PM-WOC-MO) maintenance order: sign-off work operation (transaction code IW32) Easy document system (Easy DMS): front-end tool for DMS create or change (transaction codes CV01N and CV02N); see Note in the SAP Notes tool Approve payments (transaction code BNK_APP) Where multiple signatures may be required, SAP ERP provides signature strategies that define allowed signatures and the sequence in which they must be executed. 16 /45

17 SAP has maintained ISO 9001 certification since The corresponding quality system includes all standards that control the structured development lifecycle. Figure 6: Execution of a Signature in SAP ERP Figure 7: Example of the Electronic Record of a Signature (Transaction DSAL) 17 /45

18 Digital Signature Tool in SAP ERP SAP ERP now includes a digital signature tool (component CA-DSG). This powerful functionality enables you to include signature functionality in any transaction or supported business process within SAP ERP. Additional benefits of the signature tool are: Further modularization of digital signatures Easier implementation of digital signatures in new processes Creation of a uniform flexible programming interface In addition, you can integrate tools into any business-area support in SAP ERP or in other SAP Business Suite applications, such as the SAP Product Lifecycle Management or SAP Customer Relationship Management applications. All transactions and workflow of SAP ERP can include signature functionality with the digital signature tool. If a digital signature is needed within SAP ERP where it s not implemented by the standard digital signature tool in the SAP NetWeaver Application Server (SAP NetWeaver AS) component, you can implement it on a project basis. You must have SAP NetWeaver AS 6.20 or higher to use the digital signature tool. As of enhancement package 2 for SAP NetWeaver AS 7.00, you can archive digital signature tool data and the corresponding metadata of the application. For this, you can use the archiving object DS_ARCH in transaction SARA. For further information, refer to the implementation guide titled Digital Signature Tool (Note ). Date and Time Stamp for Signature SAP ERP uses UTC as the global date and time stamp for signatures. The local date and time stamp for the electronic record of a signature is available but must be configured: it is calculated from UTC. Daylight saving time rules and the time zone are maintained within the user s profile. Many regulatory agencies have stated at industry forums that local data and time stamps are not required as long as the global date and time is unique and unequivocal and procedures exist to correctly interpret local time. SAP Solution Manager can support the compliance of SAP ERP in a crucial manner and reduce the validation and revalidation effort of SAP ERP significantly. 18 /45

19 OTHER INTERNATIONAL GMP GUIDELINES Several other guidelines for good manufacturing practice include ERES regulations. EU GMP Guideline Annex 11 The GMP guideline of the European Medicines Agency, Directive 2003/94/EC, delineates the legal requirements for good manufacturing practice in the EU, including the need to maintain a system of documentation. The main requirements affecting electronic records are that the data is available in human-readable form, available for the required time, and protected against loss or damage. The objective of this guideline is to provide requirements for ensuring reliability in using the electronic record and electronic signature systems in those contexts. The new Annex 11 and EU GMP Chapter 4 requirements on generation, control, and retention of documents are more current, effective July There are many similarities between the regulations of Annex 11 and Part 11 (and Part 11 Guidance). In general, they both include information addressing risk, personnel, validation, system and documentation, software, data, security, audit trails, signatures, printouts, and data storage. Annex 11 introduces new categories that encompass infrastructure, as well as fine-tunes requirements and interpretations. For example, Annex 11 expands computerized systems to include qualification of the IT infrastructure. Part 11 mentions protection of records. In addition, Annex 11 adds information about electronic records backup with the identification of storage location and validation of the storage system. PIC/S Guidance The Pharmaceutical Inspection Convention and Pharmaceutical Inspection Co-operation Scheme (jointly referred to as PIC/S) published guidance called Guide to Good Manufacturing Practice for Medicinal Products, Annex 11 Computerized Systems in January The guidance provides background information and recommendations regarding inspection of and training concerning computerized systems. It contains a section on electronic records and signatures aligned to EU GMP expectations. ICH Guideline The International Conference on Harmonization (ICH) guideline, ICH Q7A, Part II Basic Requirements for Active Substances Used as Starting Materials, is the first GMP guideline that has been harmonized for the United States, the EU, and Japan. ICH Q7A was published as Annex 18 in EU GMP Guidelines in July In addition, ICH Q7A has been adopted by Australia, Japan, and PIC/S. Appendixes 4 and 5 provide summary tables that describe how SAP ERP complies with EU GMP, PIC/S, and ICH guidelines in comparison to the Part 11 rule. 19 /45

20 ANVISA (Brazil) ANVISA Resolution RDC n. 17 was published on April 16, It is called the Technical Regulation of Good Manufacturing Practices of Drugs. The guidance provides details about computerized systems used in manufacturing, holding, packing, and shipping of finished products. Computer system validation requires documented evidence that attests to a high degree of safety that analysis of a computerized system, controls, and records is performed correctly and that data processing complies with predetermined specifications. Canada GMP Regulations Equipment used during the critical steps of fabrication, packaging and labeling, and testing including computerized systems is subject to installation and operational qualification. Further guidance is provided in Health Canada s document Validation Guidelines for Pharmaceutical Dosage Forms (GUI-0029) and in PIC/S Annex 11: Computerized Systems. You can also get guidance from Good Manufacturing Practices (GMP) Guidelines 2009 Edition, Version 2 (GUI-0001), which discusses records and electronic signatures. Japan GMP Regulations Regulatory authorities in Japan provide Guideline on Management of Computerized Systems for Marketing Authorization Holders and Manufacturers of Drugs and Quasi-Drugs, October 21, The guidance provides background information and recommendations regarding validation, inspection, and training concerning computerized systems. It contains a section on electronic records and signatures aligned to Japan GMP expectations. Chinese State Food and Drug Administration The Ministry of Health in China adopted the Good Manufacturing Practice for Drugs on October 19, It was retroactive to March 1, This decree states that manufacturing and quality of drugs shall be per GMP. Manufacturers must establish a quality system covering all factors that influence quality of drugs. GMP must be strictly implemented with integrity. Any falsification and fraud is forbidden. Global agencies such as the FDA and EU organizations acknowledge the complexity and controversy of validating commercial software. 20 /45

21 SAP Software Quality SAP has maintained ISO 9001 certification since The corresponding quality system includes all standards that control the structured development lifecycle. The standards are binding for all employees in development. They help ensure that SAP solutions are examined for completeness and correctness against standardized checklists, have a standard quality when released, and are introduced to the market according to a defined process. The process standards describing the development phases are standard SAP operating procedures. In addition, product standards define the quality criteria for SAP solutions. All deliverables of the lifecycle phases are defined in a master list. The adherence to the process and product standards is documented in internal systems. Quality gates between the phases help ensure that the activities and deliverables defined by the master list are complete. We have developed SAP ERP according to this development lifecycle. Audits of the SAP software development areas are carried out each year by individual companies as well as industry groups such as the Pharmaceuticals Validation Group and the Executive Council for Life Sciences. In conformance to the FDA s general principle of validation, GAMP 5 Guide, and given the fact that SAP software is highly configurable, the SAP ERP application configuration must be validated according to predetermined business requirements. Therefore, companies must deploy a validation methodology as part of a recognized development lifecycle to establish documented evidence providing a high degree of assurance that the con figured system performs as intended. VALIDATION OF SAP ERP IN A GXP-REGULATED ENVIRONMENT The SAP Solution Manager application solution is the platform for application lifecycle from SAP (see Figure 8). It provides the tools, the integrated content, and the gateway to SAP software that you need to implement, support, operate, and monitor your SAP solutions in the life sciences industry. SAP Solution Manager can support the compliance of SAP ERP in a crucial manner and reduce the validation and revalidation effort of SAP ERP significantly. Figure 8: Orchestrating a Solution with SAP Solution Manager Processes and Platform Incident, problem, and request Portfolio and project Run SAP Like a Factory Business process operations Application operations Single source of truth Solution documentation and implementation Change, test, and release Application lifecycle Integration validation Maintenance optimization and security 21 /45

22 With SAP Solution Manager, you can manage your SAP software throughout the entire lifecycle to help ensure reliability, reduce total cost of ownership, and increase ROI. SAP Solution Manager lets you: Manage core business processes and link business processes to underlying IT infrastructure Support both SAP and non-sap software and get more from existing IT investments Manage user requirement specification documents, which are descriptions of the functionalities that you want to run in the software system Use its road map functionality to fully support documentation of the different phases of the project, including predefined accelerators with versioning and status Use its business blueprint functionality to manage and document all kinds of templates, documents, and so on with versioning, status, and definition of electronic signatures Integrate content, tools, and methods for implementation, support, operation, and control Conduct central administration, which provides control of allocated, decentralized applications Use automatic functions to evaluate problems Manage change requests GAMP V-Model and Available SAP Tools Figure 9 shows a high-level representation of the good automated manufacturing practice (GAMP) methodology. The V-model is a high-level concept illustration first introduced by the GAMP Forum. The GAMP Forum was established by represen tatives from major international companies to interpret and improve the understanding of regulations for the development, implementation, and use of automated systems in pharmaceutical manufacturing. SAP has enhanced the V-model to more closely represent the ASAP Focus methodology, but it remains consistent with the formally recognized software development lifecycle. Figure 9: Adaptation of V-Model for SAP Software Implementation DQ User requirement specification Technical specification Technical, functional specification IQ Install system (hardware and software) Configure system Installation tests Integration tests Functional tests Acceptance tests Ongoing operation CC PQ OQ DQ Design qualification IQ Installation qualification OQ Operational qualification PQ Performance qualification CC Change control 22 /45

23 Application Lifecycle Management Application lifecycle (ALM) addresses the challenges of ensuring business continuity, accelerating innovation, and reducing risk as well as total cost of operations while protecting your investments with an integrated IT Infrastructure Library (ITIL) based approach. According to ITIL, the application lifecycle consists of six phases: requirements, design, build and test, deploy, operate, and optimize. ALM solutions from SAP provide processes, tools, services, and an organizational model to manage SAP and non-sap solutions throughout the complete application lifecycle. Instead of just focusing on the individual phases, SAP provides a holistic approach. You can leverage results of the different phases in other phases because of the integration provided by SAP Solution Manager. SAP Solution Manager addresses your entire IT environment by supporting 12 core process areas throughout the ALM process (see Figure 10). Figure 10: SAP Solution Manager Core Process Areas for ALM Landscape transformation Create requirements Solution documentation Upgrade Custom code Maintenance Business process operations Operate Optimize ITIL SAP Solution Manager Design Build and test Solution implementation Template Test Change control Technical operations Deploy IT service 23 /45

24 The following table provides an overview of the functionality of SAP Solution Manager. SAP Solution Manager Features Selection Recommendation Use Project administration Configuration Document Business process change analyzer (BPCA) Use the SAP Solution Manager application solution to perform all central project administration tasks such as defining the project scope and project language, assigning team members, defining the system landscape, selecting the templates for documentation, and so on. Use this feature to manage and perform configuration of the support for business processes in SAP software. Use the document feature to store SAP software related documents in SAP Solution Manager. (Final approval of controlled documents is tracked in SAP Solution Manager. It serves as the final repository.) Use BPCA to compare the objects in a transport to the objects in the technical bill of materials (TBOM) of the target system. (Since every TBOM is clearly assigned to a certain trans action in a certain scenario, business process, or process step, you can determine precisely which parts of a business process hierarchy are affected by the change.) Provide accelerated, risk-based testscope identification for regression tests. Create project for SAP Solution Manager Define project scope Set up and assign team Set up the templates, keywords, and status for reporting Plan configuration (assignments to team members) Manage access to configuration Perform process-based configuration Document the configuration Organize document storage for final approval of documentation Facilitate searching and indexing of the documents Analyze which parts of a business process are affected by the specified change Analyze which parts of a business process are affected by the activation of a business function Use accelerated, risk-based test-scope identification for regression tests 24 /45

25 SAP Solution Manager Features Selection Recommendation Use Test with the adapter of SAP Solution Manager for the SAP Quality Center application by HP SAP Test Acceleration and Optimization application SAP Test Data Migration Server software Support role-specific testing with SAP Quality Center and cover the complete testing process from requirements gathering to test-case definitions and reporting. (The infrastructure is intuitive to implement and use, as it follows the typical testing process for SAP solutions.) Free up test teams to enable them to conduct more extensive tests. Create automated test cases for SAP solutions in an accelerated way. (The acceleration is achieved by automatically creating test components for SAP software transactions that you select.) Create small, intuitive-to-maintain, nonproduction environments with consistent, relevant extracts of business data, minimizing infrastructure and maintenance expenses while maximizing the effectiveness and accuracy of development, test, and training activities. Use the adapter to transfer information about business processes and test assets smoothly to SAP Quality Center, which serves as the main testing environment for your quality teams After test completion, transfer the test results out of SAP Quality Center directly into SAP Solution Manager, automatically displaying the results of the predefined tests Help project leads gain increased control over testing processes and reuse this information during later application phases like upgrades or continuous business improvement projects Track test status by business process Generate automatic tests during regression testing Automatically upload test components into SAP Quality Center (these draft test cases are for single transactions, which you can then consolidate into a scenario test case) Support maintenance of components and test cases by integration into the BPCA of SAP Solution Manager Reduce infrastructure expenditures by greatly reducing the volume of data in the test environment Improve the quality of software developments by improving the quality of test data 25 /45

COMPLYING WITH U.S. FDA TITLE 21 CFR PART 11 FOR THE LIFE SCIENCES INDUSTRY

COMPLYING WITH U.S. FDA TITLE 21 CFR PART 11 FOR THE LIFE SCIENCES INDUSTRY SAP for Life Sciences COMPLYING WITH U.S. FDA TITLE 21 CFR PART 11 FOR THE LIFE SCIENCES INDUSTRY Copyright 2008 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Full Compliance Contents

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

MHRA GMP Data Integrity Definitions and Guidance for Industry March 2015

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

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 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

MHRA GMP Data Integrity Definitions and Guidance for Industry January 2015

MHRA GMP Data Integrity Definitions and Guidance for Industry January 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

U.S. FDA Title 21 CFR Part 11 Compliance Assessment of SAP Records Management

U.S. FDA Title 21 CFR Part 11 Compliance Assessment of SAP Records Management U.S. FDA Title 21 CFR Part 11 Compliance Assessment of SAP Records Management Disclaimer These materials are subject to change without notice. SAP AG s compliance analysis with respect to SAP software

More information

Compliance Response Edition 07/2009. SIMATIC WinCC V7.0 Compliance Response Electronic Records / Electronic Signatures. simatic wincc DOKUMENTATION

Compliance Response Edition 07/2009. SIMATIC WinCC V7.0 Compliance Response Electronic Records / Electronic Signatures. simatic wincc DOKUMENTATION Compliance Response Edition 07/2009 SIMATIC WinCC V7.0 Compliance Response Electronic Records / Electronic Signatures simatic wincc DOKUMENTATION Compliance Response Electronic Records / Electronic Signatures

More information

The Impact of 21 CFR Part 11 on Product Development

The Impact of 21 CFR Part 11 on Product Development The Impact of 21 CFR Part 11 on Product Development Product development has become an increasingly critical factor in highly-regulated life sciences industries. Biotechnology, medical device, and pharmaceutical

More information

21 CFR Part 11 White Paper

21 CFR Part 11 White Paper 21 CFR Part 11 White Paper Version V8.00 SR1 ProLeiT AG Einsteinstrasse 8, D-91074 Herzogenaurach, Germany Phone: +49 (0) 9132 777-0 Fax: +49 (0) 9132 777-150 E-Mail: info@proleit.com Internet: http://www.proleit.com

More information

This interpretation of the revised Annex

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

Electronic records and electronic signatures in the regulated environment of the pharmaceutical and medical device industries

Electronic records and electronic signatures in the regulated environment of the pharmaceutical and medical device industries White Paper No 01 I December 2010 Implementation of 21 CFR Part 11 in the epmotion Software Electronic records and electronic signatures in the regulated environment of the pharmaceutical and medical device

More information

FDA 21 CFR Part 11 Electronic records and signatures solutions for the Life Sciences Industry

FDA 21 CFR Part 11 Electronic records and signatures solutions for the Life Sciences Industry FDA 21 CFR Part 11 Electronic records and signatures solutions for the Life Sciences Industry The Rule 21 CFR Part 11 Handwritten signature means the scripted name or legal mark of an individual handwritten

More information

Oracle WebCenter Content

Oracle WebCenter Content Oracle WebCenter Content 21 CFR Part 11 Certification Kim Hutchings US Data Management Phone: 888-231-0816 Email: khutchings@usdatamanagement.com Introduction In May 2011, US Data Management (USDM) was

More information

Eclipsys Sunrise Clinical Manager Enterprise Electronic Medical Record (SCM) and Title 21 Code of Federal Regulations Part 11 (21CFR11)

Eclipsys Sunrise Clinical Manager Enterprise Electronic Medical Record (SCM) and Title 21 Code of Federal Regulations Part 11 (21CFR11) Eclipsys Sunrise Clinical Manager Enterprise Electronic Medical Record (SCM) and Title 21 Code of Federal Regulations Part 11 (21CFR11) The title 21 code of federal regulations part 11 deals with an institutions

More information

InfinityQS SPC Quality System & FDA s 21 CFR Part 11 Requirements

InfinityQS SPC Quality System & FDA s 21 CFR Part 11 Requirements InfinityQS SPC Quality System & FDA s 21 CFR Part 11 Requirements www.infinityqs.com Copyright InfinityQS International Table of Contents Overview... FDA s 21 CFR Part 11 Requirements... PART 11 ELECTRONIC

More information

Intland s Medical Template

Intland s Medical Template Intland s Medical Template Traceability Browser Risk Management & FMEA Medical Wiki Supports compliance with IEC 62304, FDA Title 21 CFR Part 11, ISO 14971, IEC 60601 and more INTLAND codebeamer ALM is

More information

Declaration of Conformity 21 CFR Part 11 SIMATIC WinCC flexible 2007

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

21 CFR Part 11 Implementation Spectrum ES

21 CFR Part 11 Implementation Spectrum ES 21 CFR Part 11 Implementation Spectrum ES INFRARED SPECTROSCOPY T E C H N I C A L N O T E Introduction Compliance with 21 CFR Part 11 is mandatory for pharmaceutical companies and their suppliers to sell

More information

21 CFR Part 11 Deployment Guide for Wonderware System Platform 3.1, InTouch 10.1 and Historian 9.0

21 CFR Part 11 Deployment Guide for Wonderware System Platform 3.1, InTouch 10.1 and Historian 9.0 Deployment Guide 21 CFR Part 11 Deployment Guide for Authors: Invensys Operations Management and TSD (Total System Design, an Optimation Company) Table of Contents by Section 1 Before you Begin...............................................................................................

More information

Compliance Response SIMATIC SIMATIC PCS 7 V8.1. Electronic Records / Electronic Signatures (ERES) Edition 03/2015. Answers for industry.

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

Supplement to the Guidance for Electronic Data Capture in Clinical Trials

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

Guidance for Industry Part 11, Electronic Records; Electronic Signatures Scope and Application

Guidance for Industry Part 11, Electronic Records; Electronic Signatures Scope and Application Guidance for Industry Part 11, Electronic Records; Electronic Signatures Scope and Application U.S. Department of Health and Human Services Food and Drug Administration Center for Drug Evaluation and Research

More information

21 CFR PART 11 ELECTRONIC RECORDS, ELECTRONIC SIGNATURES 21.11.2013. 21 CFR Part 11 Compliance PLA 2.1

21 CFR PART 11 ELECTRONIC RECORDS, ELECTRONIC SIGNATURES 21.11.2013. 21 CFR Part 11 Compliance PLA 2.1 21 CFR PART 11 ELECTRONIC RECORDS, ELECTRONIC SIGNATURES Compliance of PLA 2.1 21.11.2013 21 CFR Part 11 Compliance PLA 2.1 SEC. 11.2 IMPLEMENTATION. (a) For records required to be maintained but not submitted

More information

Assessment of Vaisala Veriteq vlog Validation System Compliance to 21 CFR Part 11 Requirements

Assessment of Vaisala Veriteq vlog Validation System Compliance to 21 CFR Part 11 Requirements / WHITE PAPER Assessment of Vaisala Veriteq vlog Validation System Compliance to 21 CFR Part 11 Requirements The 21 CFR Part 11 rule states that the FDA view is that the risks of falsification, misinterpretation,

More information

Testing Automated Manufacturing Processes

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

DeltaV Capabilities for Electronic Records Management

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

Software. For the 21 CFR Part 11 Environment. The Science and Technology of Small Particles

Software. For the 21 CFR Part 11 Environment. The Science and Technology of Small Particles Software For the 21 CFR Part 11 Environment The Science and Technology of Small Particles 21 CFR Part 11 Solution confirm Software The Code of Federal Regulations Title 21, Part 11, was implemented by

More information

Clinical database/ecrf validation: effective processes and procedures

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

DeltaV Capabilities for Electronic Records Management

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

What is the correct title of this publication? What is the current status of understanding and implementation?

What is the correct title of this publication? What is the current status of understanding and implementation? GMP Rules and Guidelines in 2013 for Computer System Validation / Computerises Systems / Electronic Records and Signatures/ IT Infrastructure and Application Compliance: What is the correct title of this

More information

LabChip GX/GXII with LabChip GxP Software

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

Implementing Compliant Pharmaceutical and Biotechnology Processes Using Oracle s E-Business Suite

Implementing Compliant Pharmaceutical and Biotechnology Processes Using Oracle s E-Business Suite Implementing Compliant Pharmaceutical and Biotechnology Processes Using Oracle s E-Business Suite A white paper discussing the compliant use of the Oracle E-Records Framework in the Pharmaceutical and

More information

The biggest challenges of Life Sciences companies today. Comply or Perish: Maintaining 21 CFR Part 11 Compliance

The biggest challenges of Life Sciences companies today. Comply or Perish: Maintaining 21 CFR Part 11 Compliance S E P T E M B E R 2 0 1 3 Comply or Perish: The biggest challenges of Life Sciences companies today are maintaining a robust product pipeline and reducing time to market while complying with an increasing

More information

Manual 074 Electronic Records and Electronic Signatures 1. Purpose

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

rsdm and 21 CFR Part 11

rsdm and 21 CFR Part 11 rsdm and 21 CFR Part 11 Meeting the 21 CFR Part 11 Burden without Overburdening The right solutions for smaller biopharma. Nothing more. Nothing less. Prepared by: Ken VanLuvanee www.virtualregulatorysolutions.com

More information

Compliance Matrix for 21 CFR Part 11: Electronic Records

Compliance Matrix for 21 CFR Part 11: Electronic Records Compliance Matrix for 21 CFR Part 11: Electronic Records Philip E. Plantz, PhD, Applications Manager David Kremer, Senior Software Engineer Application Note SL-AN-27 Revision A Provided By: Microtrac,

More information

21 CFR Part 11 Electronic Records & Signatures

21 CFR Part 11 Electronic Records & Signatures Gap Analysis - Checklist 21 CFR Part 11 Electronic Records & Signatures his document is a proposal and starting point only. he type and extent of documentation depends on the process environment. he proposed

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. 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

Guidance for Industry Computerized Systems Used in Clinical Investigations

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

Computer System Validation - It s More Than Just Testing

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

POLICY ISSUES IN E-COMMERCE APPLICATIONS: ELECTRONIC RECORD AND SIGNATURE COMPLIANCE FDA 21 CFR 11 ALPHATRUST PRONTO ENTERPRISE PLATFORM

POLICY ISSUES IN E-COMMERCE APPLICATIONS: ELECTRONIC RECORD AND SIGNATURE COMPLIANCE FDA 21 CFR 11 ALPHATRUST PRONTO ENTERPRISE PLATFORM W H I T E P A P E R POLICY ISSUES IN E-COMMERCE APPLICATIONS: ELECTRONIC RECORD AND SIGNATURE COMPLIANCE FDA 21 CFR 11 ALPHATRUST PRONTO ENTERPRISE PLATFORM This white paper is written for senior executives

More information

ScreenMaster RVG200 Paperless recorder FDA-approved record keeping. Measurement made easy

ScreenMaster RVG200 Paperless recorder FDA-approved record keeping. Measurement made easy Information INF13/147 EN ScreenMaster RVG200 Paperless recorder FDA-approved record keeping Measurement made easy Guidance on the use of the RVG200 paperless recorder for electronic record keeping in FDA-approved

More information

Self-Assessment of eresearch Compliance with 21 CFR Part 11, Electronic Record; Electronic Signatures

Self-Assessment of eresearch Compliance with 21 CFR Part 11, Electronic Record; Electronic Signatures Self-Assessment of eresearch Compliance with 21 CFR Part 11, Electronic Record; Electronic Signatures Subpart A General Provisions Sec. 11.1 Scope. (a) The regulations in this part set forth the criteria

More information

FDA Title 21 CFR Part 11:Electronic Records; Electronic Signatures; Final Rule (1997)

FDA Title 21 CFR Part 11:Electronic Records; Electronic Signatures; Final Rule (1997) www.qadata.co.za Introduction FDA Title 21 CFR Part 11:Electronic Records; Electronic Signatures; Final Rule (1997) INITIAL REGULATION RELEASED High profile audit findings Industry complaints to wasting

More information

Implementation of 21CFR11 Features in Micromeritics Software Software ID

Implementation of 21CFR11 Features in Micromeritics Software Software ID Implementation of 21CFR11 Features in Micromeritics Software Software ID PART 11 ELECTRONIC RECORDS; ELECTRONIC SIGNATURES Subpart A General Provisions Sec. 11.1 Scope. 11.2 Implementation. 11.3 Definitions.

More information

The purpose of this Supplier Quality Standard is to communicate the expectations and requirements of Baxter Healthcare Corporation to its suppliers.

The purpose of this Supplier Quality Standard is to communicate the expectations and requirements of Baxter Healthcare Corporation to its suppliers. Supplier Quality Standard 1.0 Purpose The purpose of this Supplier Quality Standard is to communicate the expectations and requirements of Baxter Healthcare Corporation to its suppliers. These expectations

More information

TIBCO Spotfire and S+ Product Family

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

Tools to Aid in 21 CFR Part 11 Compliance with EZChrom Elite Chromatography Data System. White Paper. By Frank Tontala

Tools to Aid in 21 CFR Part 11 Compliance with EZChrom Elite Chromatography Data System. White Paper. By Frank Tontala Tools to Aid in 21 CFR Part 11 Compliance with EZChrom Elite Chromatography Data System White Paper By Frank Tontala Agilent Technologies Software & Informatics Life Sciences & Chemical Analysis Group

More information

Guidance for electronic trial data capturing of clinical trials

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

21 CFR Part 11 Checklist

21 CFR Part 11 Checklist 21 CFR Part 11 Checklist GUIDE NOTOCORD - 113 Chemin de Ronde - 78290 Croissy-sur-Seine www.notocord.com my.notocord.com support@notocord.com +33 (0)1 34 80 00 00 1. Preliminary information 1.1. Purpose

More information

COTS Validation Post FDA & Other Regulations

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

Implement best practices by using FileMaker Pro 7 as the backbone of your 21 CFR 11 compliant system.

Implement best practices by using FileMaker Pro 7 as the backbone of your 21 CFR 11 compliant system. 21 CRF 11 Electronic Records and Signatures Implement best practices by using FileMaker Pro 7 as the backbone of your 21 CFR 11 compliant system. By Todd Duell What does Title 21 of the Code of Federal

More information

For technical assistance, please contact: Thermo Nicolet Corporation 5225 Verona Road Madison WI 53711-4495

For technical assistance, please contact: Thermo Nicolet Corporation 5225 Verona Road Madison WI 53711-4495 The information in this publication is provided for reference only. All information contained in this publication is believed to be correct and complete. Thermo Nicolet Corporation shall not be liable

More information

Meeting the FDA s Requirements for Electronic Records and Electronic Signatures (21 CFR Part 11)

Meeting the FDA s Requirements for Electronic Records and Electronic Signatures (21 CFR Part 11) Meeting the FDA s Requirements for Electronic Records and Electronic Signatures (21 CFR Part 11) Executive Summary...3 Background...4 Internet Growth in the Pharmaceutical Industries...4 The Need for Security...4

More information

Considerations When Validating Your Analyst Software Per GAMP 5

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

CoSign for 21CFR Part 11 Compliance

CoSign for 21CFR Part 11 Compliance CoSign for 21CFR Part 11 Compliance 2 Electronic Signatures at Company XYZ Company XYZ operates in a regulated environment and is subject to compliance with numerous US government regulations governed

More information

Documenting Distribution Operations: FDA Validation Beyond the Laboratory and Manufacturing Facility

Documenting Distribution Operations: FDA Validation Beyond the Laboratory and Manufacturing Facility Documenting Distribution Operations: FDA Validation Beyond the Laboratory and Manufacturing Facility Kellie Wittman, Tompkins Associates September 2009 www.tompkinsinc.com Contents Introduction 3 Why bother

More information

Monitoring manufacturing, production and storage environments in the pharmaceutical industry

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

Considerations for validating SDS Software v2.x Enterprise Edition for the 7900HT Fast Real-Time PCR System per the GAMP 5 guide

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

21 CFR Part 11 Compliance Using STATISTICA

21 CFR Part 11 Compliance Using STATISTICA 21 CFR Part 11 Compliance Using STATISTICA Last Updated: April 2003 This document was updated to reflect the FDA s latest guidance (released February, 2003) and the withdrawal of previous guidance.! STATSOFT

More information

OPERATIONAL STANDARD

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

ComplianceSP TM on SharePoint. Complete Document & Process Management for Life Sciences on SharePoint 2010 & 2013

ComplianceSP TM on SharePoint. Complete Document & Process Management for Life Sciences on SharePoint 2010 & 2013 TM ComplianceSP TM on SharePoint Complete Document & Process Management for Life Sciences on SharePoint 2010 & 2013 Overview With increasing pressure on costs and margins across Life Sciences, the industry

More information

How To Control A Record System

How To Control A Record System Thermo Scientific Qtegra Intelligent Scientific Data Solution (ISDS) Software for 21 CFR Part 11 Compliant Laboratories Technical Note 43106 Key Words Compliance, Electronic Records, 21 CFR Part 11 Goal

More information

Risk-Based Validation of Computer Systems Used In FDA-Regulated Activities

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

Protecting Business Information With A SharePoint Data Governance Model. TITUS White Paper

Protecting Business Information With A SharePoint Data Governance Model. TITUS White Paper Protecting Business Information With A SharePoint Data Governance Model TITUS White Paper Information in this document is subject to change without notice. Complying with all applicable copyright laws

More information

SolidWorks Enterprise PDM and FDA 21CFR Part 11

SolidWorks Enterprise PDM and FDA 21CFR Part 11 T E C H N I C A L P A P E R SolidWorks Enterprise PDM and FDA 21CFR Part 11 This Technical Paper discusses the technical solutions provided by SolidWorks Enterprise PDM to address the FDA 21 CFR Part 11

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 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

IBM asset management solutions White paper. Using IBM Maximo Asset Management to manage all assets for hospitals and healthcare organizations.

IBM asset management solutions White paper. Using IBM Maximo Asset Management to manage all assets for hospitals and healthcare organizations. IBM asset management solutions White paper Using IBM Maximo Asset Management to manage all assets for hospitals and healthcare organizations. September 2007 2 Contents 2 Executive summary 3 Introduction

More information

Computerized System Audits In A GCP Pharmaceutical Laboratory Environment

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

GAMP 4 to GAMP 5 Summary

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

AutoSave. Achieving Part 11 Compliance. A White Paper

AutoSave. Achieving Part 11 Compliance. A White Paper AutoSave Achieving Part 11 Compliance A White Paper Synopsis This whitepaper provides information related to FDA regulation 21 CFR Part 11 (Part 11) for organizations considering MDT software solutions.

More information

InfoCenter Suite and the FDA s 21 CFR part 11 Electronic Records; Electronic Signatures

InfoCenter Suite and the FDA s 21 CFR part 11 Electronic Records; Electronic Signatures InfoCenter Suite and the FDA s 21 CFR part 11 Electronic Records; Electronic Signatures Overview One of the most popular applications of InfoCenter Suite is to help FDA regulated companies comply with

More information

Software Manual Part IV: FDA 21 CFR part 11. Version 2.20

Software Manual Part IV: FDA 21 CFR part 11. Version 2.20 Software Manual Part IV: FDA 21 CFR part 11 Version 2.20 OPTIMA Software Manual Part IV: FDA 21 CFR part 11 BMG LABTECH This manual was designed to guide OPTIMA users through the software features related

More information

Thermal Analysis. http://www.fda.gov. Subpart A General Provisions 11.1 Scope. 11.2 Implementation. 11.3 Definitions.

Thermal Analysis. http://www.fda.gov. Subpart A General Provisions 11.1 Scope. 11.2 Implementation. 11.3 Definitions. Thermal Analysis 21 CFR 11 Compliance 21 CFR Part 11 Electronic Records; Electronic Signatures General concept The U.S. Federal Food and Drug Administration (FDA) has issued regulations that provide criteria

More information

International GMP Requirements for Quality Control Laboratories and Recomendations for Implementation

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

AS9100 Quality Manual

AS9100 Quality Manual Origination Date: August 14, 2009 Document Identifier: Quality Manual Revision Date: 8/5/2015 Revision Level: Q AS 9100 UNCONTROLLED IF PRINTED Page 1 of 17 1 Scope Advanced Companies (Advanced) has established

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. 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

GAMP5 - a lifecycle management framework for customized bioprocess solutions

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

Agilent MicroLab Software with Spectroscopy Configuration Manager and Spectroscopy Database Administrator (SCM/SDA)

Agilent MicroLab Software with Spectroscopy Configuration Manager and Spectroscopy Database Administrator (SCM/SDA) Agilent MicroLab Software with Spectroscopy Configuration Manager and Spectroscopy Database Administrator (SCM/SDA) Compliance with 21 CFR Part 11 Introduction Part 11 in Title 21 of the Code of Federal

More information

FILEHOLD DOCUMENT MANAGEMENT SYSTEM 21 CFR PART 11 COMPLIANCE WHITE PAPER

FILEHOLD DOCUMENT MANAGEMENT SYSTEM 21 CFR PART 11 COMPLIANCE WHITE PAPER FILEHOLD DOCUMENT MANAGEMENT SYSTEM 21 CFR PART 11 COMPLIANCE WHITE PAPER Copyright 2012 FileHold Systems Inc. All rights reserved. For further information about this manual or other FileHold Systems products,

More information

Data Management PACT Workshop: Design & Operation of GMP Cell Therapy Facilities April 10 th -11 th, 2007

Data Management PACT Workshop: Design & Operation of GMP Cell Therapy Facilities April 10 th -11 th, 2007 Data Management PACT Workshop: Design & Operation of GMP Cell Therapy Facilities April 10 th -11 th, 2007 Data Management Discuss Database Development Design Process Tips Data Normalization Reporting Ideas

More information

Welcome Computer System Validation Training Delivered to FDA. ISPE Boston Area Chapter February 20, 2014

Welcome Computer System Validation Training Delivered to FDA. ISPE Boston Area Chapter February 20, 2014 Welcome Computer System Validation Training Delivered to FDA ISPE Boston Area Chapter February 20, 2014 1 Background Training Conducted on April 24, 2012 Food & Drug Administration Division of Manufacturing

More information

Conducting a Gap Analysis on your Change Control System. Presented By Miguel Montalvo, President, Expert Validation Consulting, Inc.

Conducting a Gap Analysis on your Change Control System. Presented By Miguel Montalvo, President, Expert Validation Consulting, Inc. Conducting a Gap Analysis on your Change Control System Presented By Miguel Montalvo, President, Expert Validation Consulting, Inc. Standards, Regulations, Guidelines related to Change Control Management

More information

ABSTRACT INTRODUCTION WINDOWS SERVER VS WINDOWS WORKSTATION. Paper FC02

ABSTRACT INTRODUCTION WINDOWS SERVER VS WINDOWS WORKSTATION. Paper FC02 ABSTRACT Paper FC02 Implementing SAS using Microsoft Windows Server and Remote Desktop Paul Gilbert, DataCeutics, Inc., Pottstown, PA Steve Light, DataCeutics, Inc., Pottstown, PA DataCeutics provides

More information

Overview of EAM Services. A Fully Integrated Global EAM Service Provider

Overview of EAM Services. A Fully Integrated Global EAM Service Provider A Fully Integrated Global EAM Service Provider Table of Contents Strategy & Process Services Overview... p. 3 Asset Reliability Services Overview... p. 4 Systems & Technology Services Overview... p. 7

More information

In 2001, ISPE issued Baseline Guide Volume

In 2001, ISPE issued Baseline Guide Volume In today s biopharma and pharmaceutical industries, three related, but distinct terms are in common use: commissioning, qualification, and verification. Inconsistent interpretation and application of these

More information

Quality Agreement. by and between. Supplier Name. Address: and. Client Name: Address:

Quality Agreement. by and between. Supplier Name. Address: and. Client Name: Address: NOTE TO USERS This Quality Agreement template was developed by the Bulk Pharmaceutical Task Force (BPTF), an affiliate organization of the Society of Chemical Manufacturers and Affiliates (SOCMA), as a

More information

Risk-Based Approach to 21 CFR Part 11

Risk-Based Approach to 21 CFR Part 11 3109 W. Dr. Martin Luther King, Jr. Blvd., Suite 250 Tampa, FL 33607 USA Tel: 813/960-2105 Fax: 813/264-2816 www.ispe.org Risk-Based Approach to 21 CFR Part 11 The 21 CFR Part 11 regulation is a comprehensive

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. 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

Sage ERP Solutions I White Paper

Sage ERP Solutions I White Paper I White Paper Do You Need a State-of-the-Art ERP Solution? Complete This Gap Analysis to Find Out www.sageerpsolutions.com Table of Contents Executive Summary... 3 Introduction... 3 The Need for Gap Analysis...

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 & 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

Regulatory Asset Management: Harmonizing Calibration, Maintenance & Validation Systems

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

Review and Approve Results in Empower Data, Meta Data and Audit Trails

Review and Approve Results in Empower Data, Meta Data and Audit Trails Review and Approve Results in Empower Data, Meta Data and Audit Trails 2013 Waters Corporation 1 What is an audit trail? Systematic story of the data from creation, through interpretation and final assessment

More information

Guidance for Industry. Q10 Pharmaceutical Quality System

Guidance for Industry. Q10 Pharmaceutical Quality System Guidance for Industry Q10 Pharmaceutical Quality System U.S. Department of Health and Human Services Food and Drug Administration Center for Drug Evaluation and Research (CDER) Center for Biologics Evaluation

More information

Best Practices in Identity and Access Management (I&AM) for Regulatory Compliance. RSA Security and Accenture February 26, 2004 9:00 AM

Best Practices in Identity and Access Management (I&AM) for Regulatory Compliance. RSA Security and Accenture February 26, 2004 9:00 AM Best Practices in Identity and Access Management (I&AM) for Regulatory Compliance RSA Security and Accenture February 26, 2004 9:00 AM Agenda Laura Robinson, Industry Analyst, RSA Security Definition of

More information

Using SharePoint 2013 for Managing Regulated Content in the Life Sciences. Presented by Paul Fenton President and CEO, Montrium

Using SharePoint 2013 for Managing Regulated Content in the Life Sciences. Presented by Paul Fenton President and CEO, Montrium Using SharePoint 2013 for Managing Regulated Content in the Life Sciences Presented by Paul Fenton President and CEO, Montrium Overview Informative Webinar that aims to provide an overview of how SharePoint

More information

ASSESSMENT OF QUALITY RISK MANAGEMENT IMPLEMENTATION

ASSESSMENT OF QUALITY RISK MANAGEMENT IMPLEMENTATION PHARMACEUTICAL INSPECTION CONVENTION PHARMACEUTICAL INSPECTION CO-OPERATION SCHEME PI 038-1 26 March 2012 AIDE-MEMOIRE ASSESSMENT OF QUALITY RISK MANAGEMENT IMPLEMENTATION PIC/S March 2012 Reproduction

More information

A ChemoMetec A/S White Paper September 2013

A ChemoMetec A/S White Paper September 2013 NucleoCounter NC-3000, NucleoView NC-3000 Software and Code of Federal Regulation 21 Part 11; Electronic Records, Electronic Signatures (21 CFR Part 11) A ChemoMetec A/S White Paper September 2013 ChemoMetec

More information

Validation Consultant

Validation Consultant Personal Data Name Title Validation Consultant Contact jsb-validierung Zwischen den Bächen 9 D 79618 Rheinfelden Tel: +49 7623 79 49 82 Mobile: +49 172 737 84 86 E-Mail: Internet: jsb-val@online.de http://www.jsb-validierung.de

More information

The SaaS LMS and Total Cost of Ownership in FDA-Regulated Companies

The SaaS LMS and Total Cost of Ownership in FDA-Regulated Companies The SaaS LMS and Total Cost of Ownership in FDA-Regulated Companies The SaaS LMS and Total Cost of Ownership in FDA-Regulated Companies By Rob Sims, Director, Life Science, UL EduNeering When a Life Science

More information