Testing Computers Systems for FDA/MHRA Compliance

Overview

There is no substitute for extensive testing when it comes to IT systems. Recognition that problems are easier and cheaper to fix before the system is in use (rather than after), has turned testing into a cost-effective tool. However, when developing computer systems for pharmaceuticals manufacturing, testing to meet regulatory requirements adds an additional layer of complexity. Testing Computers Systems for FDA/MCA Compliance focuses on software module, software integration, hardware, and system acceptance ...

See more details below
Hardcover
$147.33
BN.com price
(Save 6%)$157.95 List Price
Other sellers (Hardcover)
  • All (3) from $140.87   
  • New (2) from $140.87   
  • Used (1) from $197.52   
Sending request ...

Overview

There is no substitute for extensive testing when it comes to IT systems. Recognition that problems are easier and cheaper to fix before the system is in use (rather than after), has turned testing into a cost-effective tool. However, when developing computer systems for pharmaceuticals manufacturing, testing to meet regulatory requirements adds an additional layer of complexity. Testing Computers Systems for FDA/MCA Compliance focuses on software module, software integration, hardware, and system acceptance testing. Reflecting the renewed emphasis of the FDA and other global regulatory agencies towards systematic inspections and risk-based validation with an underlying scientific rationale, this guide focuses on current best practices in computer systems testing in the regulatory environment. David Stokes demonstrates how the principles detailed in the GAMP 4 Guide can be used to define a pragmatic approach to testing. He includes techniques for testing large Internet-based systems for compliance with the stringent requirements of regulations such as 21CFR Part 11, and clarifies the relationship and responsibilities of the system "user" and "supplier". The author also delineates where testing starts in the project lifecycle, who performs what testing, where the lines of responsibility start and end, and the differences in the terminology used in the healthcare and general IT sectors. A checklist of questions to be used when developing System Test Specification(s), and templates for documenting typical system test results, round out the features that make this book a practical guide for all those involved in the development and implementation of IT systems for the pharmaceutical and related healthcare manufacturing industries. Senior managers, team project leaders, project team members, and industry trainees, will all benefit from this clear and practical guide.

Read More Show Less

Product Details

  • ISBN-13: 9780849321634
  • Publisher: Taylor & Francis
  • Publication date: 11/14/2003
  • Pages: 136
  • Product dimensions: 7.20 (w) x 10.30 (h) x 0.51 (d)

Table of Contents

PURPOSE

SCOPE
What this Guideline Covers
When this Guideline is Applicable?
Who this Guideline is Intended for?

WHY DO WE TEST?
Because the Regulators Require Us to...
Because the Quality Assurance Department Require Us to...
Because We've Always Done it this Way...
Because it Saves Money!

WHAT TO TEST
GxP Priority
Software/Hardware Category
Test Rationale and Test Policies
Testing or Verification?

THE TEST STRATEGY
Risk Based Rationale
The Relationship Between Test Specification(s)
Integrating or Omitting the System test Specification(s)
The Role of Factory and Site Acceptance Tests
Roles and Responsibilities
Relationships with Other Lifecycle Phases and Documents (Inputs and Outputs)

THE DEVELOPMENT LIFECYCLE OF A TEST SPECIFICATION
Recommended Phasing; Interfaces Between and the Dependencies of Activities
Milestones in the Process
Inputs to the Development of a Test Specification
Document Evolution
Constraints on the Development of a Test Specification
Constraints on the Testing
Conducting the Tests
Outputs from the Testing

RECOMMENDED CONTENT FOR SYSTEM TEST SPECIFICATION(S)
Overview
General section
Individual Test Cases

GOOD TESTING PRACTICES
Prepare for Success
Common Problems
Testing in the Life Science Industries is Different
Prerequisite Training
An Overview of the Test Programme
Roles and Responsibilities
Managing a Test Programme
Checking Test Scripts in and out
Recording Test Results
To Sign or Not to Sign
The Use of Test Witnesses
Capturing Test Evidence (Raw Data)
Proceed or Abort? (Test Incident Management)
Categorising Test Incidents
Impact Assessment
Test Execution Status
Test Data Status
Test Log-On Accounts (User IDs)

SUPPLIER SYSTEM TEST REPORTS/QUALIFICATION

THE USE OF ELECTRONIC TEST MANAGEMENT AND AUTOMATED TEST TOOLS
The Need for Test Tools in the Pharmaceutical Industry
Test Tool Functionality
Electronic Records and Electronic Signature Compliance
The Availability of Suitable Test Tools
Test Script Lifecycle
Incident Lifecycle
Flexibility for Non-GxP Use
Project and Compliance Approach
Testing Test Tools
Test Record Integrity
Features to Look Out For

Appendix A - Hardware test specification and testing
Appendix B - Package Configuration Test Specifications and Testing
Appendix C - Software Module Test Specifications and Testing
Appendix D - Software Integration Test Specifications and Testing
Appendix E - System Acceptance Test Specifications and Testing
Appendix F - Risk Based Testing
Appendix G - Traceability Matrices
Appendix H - Test Script Templates
Appendix I - Checklists
Appendix J - References and Acknowledgements

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)