It explains how to write a Data Privacy Statement for compliance with EU General Data Protection Regulation (GDPR). What the regulations mean is described for all four primary compliance areas: SOPs, software features, infrastructure qualification, and validation. It gets you on the right track for using electronic records and signatures to greatly increase productivity and ensure compliance.
AREA COVERED
- Which data and systems are subject to Part 11 and Annex 11
- How to write a Data Privacy Statement
- What the regulations mean, not just what they say
- Avoid 483 and Warning Letters
- Requirements for local, SaaS, and cloud hosting
- Understand the current industry standard software features for security, data transfer, audit trails, and electronic signatures
- How to use electronic signatures, ensure data integrity, and protect intellectual property
- SOPs required for the IT infrastructure
- Product features to look for when purchasing COTS software
- Reduce validation resources by using easy to understand fill-in-the-blank validation documents
WHO WILL BENEFIT?
- GMP, GCP, GLP, Regulatory Professionals
- QA/QC
- IT
- Auditors
- Managers and Directors
- Software vendors, Hosting Providers
- Which data and systems are subject to Part 11 and Annex 11
- How to write a Data Privacy Statement
- What the regulations mean, not just what they say
- Avoid 483 and Warning Letters
- Requirements for local, SaaS, and cloud hosting
- Understand the current industry standard software features for security, data transfer, audit trails, and electronic signatures
- How to use electronic signatures, ensure data integrity, and protect intellectual property
- SOPs required for the IT infrastructure
- Product features to look for when purchasing COTS software
- Reduce validation resources by using easy to understand fill-in-the-blank validation documents
- GMP, GCP, GLP, Regulatory Professionals
- QA/QC
- IT
- Auditors
- Managers and Directors
- Software vendors, Hosting Providers