11.07.2015 Views

Managing Compliance with 21 CFR Part 11 - Tangerine Software

Managing Compliance with 21 CFR Part 11 - Tangerine Software

Managing Compliance with 21 CFR Part 11 - Tangerine Software

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Managing</strong> <strong>Compliance</strong> <strong>with</strong> <strong>21</strong> <strong>CFR</strong> <strong>Part</strong> <strong>11</strong>by Tom Heinricher, Sage ERP X3 Senior Business ConsultantTitle <strong>21</strong>, <strong>Part</strong> <strong>11</strong> of the U.S. Food and Drug Administration’s (FDA) Code ofFederal Regulations requires drug makers, medical device manufacturers,biotech companies, biologics developers and other FDA-regulated industries(except food manufacturers) to implement controls – including audits,validation systems and documentation – for software and systems involved inprocessing many forms of data as part of business operations and productdevelopment.The regulation was created to maintain the trustworthiness, reliability andintegrity of electronic records and to ensure that the authenticity ofelectronic records would be equivalent to paper records when submitted. Allcompanies and industries that submit or utilize electronic records and/orsignatures regulated by the FDA must comply <strong>with</strong> this federal regulation.But complying <strong>with</strong> the regulation proves to be a difficult task for mostcompanies. Since <strong>Part</strong> <strong>11</strong> was introduced in 1997, manufacturers haveendured much confusion as the regulation is open to a wide range ofinterpretations. In 2003, the FDA <strong>with</strong>drew previous guidance and issued anew document on the “scope and application” of <strong>Part</strong> <strong>11</strong> which intended toclarify how it should be implemented and would be enforced, but this tooremains a subject of debate. In the near future, the FDA will issue revisedguidance for <strong>21</strong> <strong>CFR</strong> <strong>Part</strong> <strong>11</strong> which promises to offer a lessprescriptive, more risk-oriented approach to electronic recordkeeping.Despite the confusion surrounding <strong>Part</strong> <strong>11</strong>, one thing remainsconstant. The FDA’s interpretation of the followingrequirements has not changed:Controls for closed systems,Controls for open systems, andElectronic signatures.With that in mind, compliance <strong>with</strong> regulatory requirements isa business-critical need that must be maintained, and the FDArecognizes that a technically advanced software solution canhelp companies manage compliance. Specifically, <strong>CFR</strong> <strong>21</strong><strong>Part</strong> <strong>11</strong> states that enterprise resource planning (ERP)systems must provide:Extensive transaction audit functionality<strong>with</strong> field, user, time and date reference,Document signature printing associationfor technical or quality assurancegenerated reports,Digital signature to support field and/orscreen level security authentication <strong>with</strong>change reason codes and accessverification and historical user, time anddate references.(continued)<strong>Compliance</strong> <strong>with</strong>regulatoryrequirements is abusiness-criticalneed that must bemaintained, and theFDA recognizes that atechnically advancedsoftware solution canhelp companiesmanage compliance.


Further requirements are associated <strong>with</strong> the conceptof “validation” – for both the manufacturer (the effortdeployed by manufacturers to document and mapspecific company processes to associated softwarefunctionality) and the software developer (the processor methodology that developers use to test softwarefunctionality). Guidelines require that the company’sneeds and intended uses of its selected softwaresystem are established and that evidence that thecomputer system implements those needs correctly aretraceable to the system design and specification.To help companies adhere to <strong>21</strong> <strong>CFR</strong> <strong>Part</strong> <strong>11</strong>, SageERP X3 offers the following functionality:Audit TrailsAssociated <strong>with</strong> the creation, modificationand deletion of electronic records, audit trailsare now standard in Sage ERP X3. Thefunctionality records user name, date, time,previous data, new data and the reason forthe change.Digital Electronic SignaturesAn electronic signature framework includestables, programs, actions and objects tostore, configure and collect uniquee-signatures, which are permanently linked tothe object and can not be modified or copied.For detailed information about how Sage ERP X3 helpscompanies comply <strong>with</strong> each requirement of <strong>Part</strong> <strong>11</strong>,please see Table 1.While it may seem that complying <strong>with</strong> <strong>Part</strong> <strong>11</strong> is aburdonsome, costly undertaking, adhering to theregulations yields several benefits, including:Reductions in system vulnerability andabuse,Lower compliance-driven costs,Shorter validation time,Reductions in entry errors,Lower costs related to record retention,Improved data integration and modelingcapabilities,Advanced search capability via a decisionsupport system and data warehouse, andIncreased speed of information exchange.Sage ERP X3 can help your company enjoy theinherent rewards of becoming <strong>21</strong> <strong>CFR</strong> <strong>Part</strong> <strong>11</strong>compliant. Contact us for a free assessment of yourcompany’s needs.Document SignaturesDocuments requiring handwritten signatures,such as Certificates of Analysis or TechnicalSheets, are generated <strong>with</strong> an image linked tothe specific document. The image plate iscontrolled and linked to the user profile.Validation ScriptsDocumentation describing various processcontrols deployed by Sage is available. Thesescripts are flexible in design, associated<strong>with</strong> clearly identified and documentedprocedures. They are easily transferred orincorporated into custom validation andcGMP documents to support companyinitiatives.Security FeaturesSeveral security standards safeguard againstunauthorized use, including automatic logoffafter a period of inactivity, auto logout aftertoo many failed logon attempts and logging ofall user activity.2


<strong>Managing</strong> <strong>Compliance</strong> <strong>with</strong> <strong>21</strong> <strong>CFR</strong> <strong>Part</strong> <strong>11</strong>Table 1<strong>Part</strong> <strong>11</strong> Clause<strong>11</strong>.10(a)<strong>11</strong>.10(b)<strong>11</strong>.10(c)<strong>11</strong>.10(d)<strong>11</strong>.10(e)<strong>11</strong>.10(f)<strong>11</strong>.10(g)<strong>11</strong>.10(h)<strong>11</strong>.10(i)<strong>11</strong>.10(j)<strong>11</strong>.10(k)<strong>11</strong>.30Sage ERP X3 CapabilitySage ERP X3 manages audit trails for all electronic records, which are secured fromunauthorized access.All electronic records generated by Sage ERP X3 are accurate, complete andpresented in human readable format, and they can be printed or exported intoindustry standard formats like Adobe PDF and XML.All electronic records can be maintained in the active database or archived toaccommodate all required retention periods, even after software upgrades. Accessis secured and the system maintains the link between electronic signatures andelectronic records even after archiving.Advanced security features ensure that only authorized individuals access thesystem, and changes to security profiles are logged.Electronic records for creating, modifying or deleting data are automaticallygenerated. Records are time and date stamped <strong>with</strong> the user ID of the person whowas logged on to the system. The records maintain the old and new values of thechange and the transaction used to generate the record. All electronic records aremaintained in the active database for required retention periods, as is the link <strong>with</strong>the electronic signature.Process instruction sheets used in the manufacturing process include operationalchecks to enforce permitted sequencing of steps and events.Authority checks, along <strong>with</strong> advanced security features, ensure that only authorizedindividuals can use the system, electronically sign a record, access the operation orcomputer system input or output device, alter a record or perform the operation athand.Terminals, measurement devices, process control systems and other input devicesare maintained by the system’s advanced security features and require authorizationfor connection.Sage requires that all personnel responsible for developing and maintainingSage ERP X3 have the education, training and experience to perform their assignedtasks. Sage offers a wide range of training classes to ensure a process ofcontinual learning.This clause refers to procedures required of the manufacturer and is not related toSage ERP X3.Sage ERP X3 provides a complete electronic library containing extensive field,functional and system related documentation. Consistent updates to documentationis provided to current customers and deployed in a controlled electronic format.For open systems, Sage ERP X3 supports interfaces <strong>with</strong> complimentary softwarepartners that supply ADAPI methods <strong>with</strong> public key infrastructure (PKI) technology.3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!