Table of contents
At a glance
How do redacted GVP source documents stay linked to the safety case?
Link the source as received, the edited version and the information used in the case. Define the purpose and permitted access for each copy. Document and check relevant edits so they do not inadvertently change the medical content. Apply EMA masking rules for the EudraVigilance data fields concerned. They do not require blanket deletion of internal source documents or removal of every personal detail everywhere.
- Classify the protected source, working copy, and actually shipped version separately.
- Data masking for EudraVigilance is a site-specific instruction, not a general deletion rule.
- Staining must not inadvertently destroy the required medical context and case assignment.
1. Answer three different questions
For human pharmaceutical pharmacovigilance, confidentiality, availability of source information, and accurate transmission must be equally considered. The question of who internally may view a document is not equivalent to the question of which information is sent to a partner or to EudraVigilance. Therefore, a single blanket data masking profile does not resolve all use cases.
GVP Module VI calls for accessible source data or a copy for quality control. Module I addresses traceable, protected records. The 2025 Addendum II sets additional rules for masking certain electronically submitted ICSR data. Assess the data protection basis for an individual disclosure separately.
2. Retain the intended use of each batch.
An incoming source may comprise an email, a physician's letter, or a documented telephone inquiry. The derived working copy serves a specific purpose: medical review, internal quality control, or agreed-upon onward transfer. Indicate the relationship such that an reviewer can identify which version formed the basis of a decision.
A revised version must not inadvertently become the apparently unchanged original source without proper documentation. Describe relevant changes and their purpose. Whether the original file, an appropriate copy, or additional records should be retained depends on the specific record concept and applicable requirements. A PDF file extension alone does not address this question.
3. Deriving accesses from the actual task
The internal matrix presents a limited process. The mentioned roles are examples and do not constitute a prescribed organizational structure. Determine which information is required for each task, and implement appropriate technical and organizational controls.
Also check alternative paths outside of document view: downloads, email attachments, support access points, and search indexes can re-expose sensitive information. A properly redacted display provides little protection if the unredacted file remains accessible via the same workflow without appropriate authorization.
| Task | Anticipated Information | Appropriate Control |
|---|---|---|
| Case processing | Source required for data entry and subsequent inquiries | Authorized access and unambiguous case reference |
| Medical Review | Required sequence and relevant findings | Medical content received despite processing |
| Agreed Partner Transfer | Approved version for the intended purpose | Recipient, scope, and sent version verified |
| Technical Support | Extent required for root cause analysis | Restricted and controlled access instead of blanket full access |
| Quality Control | Comparison of the accepted content with the source or an appropriate equivalent representation | Availability assured, confidentiality maintained |
4. Apply the EudraVigilance rules of 2025 in a site-specific manner
GVP VI Addendum II distinguishes between data fields that require masking, fields that should remain blank, and information that remains required for PV processes. For certain existing entries, a null flavour MSK is specified; where data is missing from the sender, alternative acceptable representations shall be evaluated. "Masked" and "not known" do not convey the same meaning.
The addendum specifies certain field names, as well as numerous required information elements for case processing, duplicate detection, and signal management. It simultaneously cautions against excessive masking. The tables are intended for submission to EudraVigilance; they cannot be directly used as a general deletion list for all internal documents.
Sources: [3]
5. Example: A source, two purpose-specific containers
In this example, a synthetic three-sided medical certificate is presented. Page 1 contains direct contact information, Page 2 shows the temporal progression, and Page 3 includes a relevant laboratory result with a unit. The agreed-upon purpose of the document requires medical information, but certain direct identifiers must not be included in the forwarded version.
The team prepares a targeted version and reviews the content against the source. A deliberately embedded error initially masks the unit of the laboratory value. This version must not meet the predefined test specification. The correction restores the unit without exposing the previously defined protected identifiers.
| Object or step | Specified expected result | Assessment |
|---|---|---|
| Source Q-01 | Three pages, clear case reference and controlled access | Basis of the comparison |
| Working version W-01 | Original identifiers removed; medical context retained | Specific intended use documented |
| Error checking | Unit of the laboratory test on page 3 concealed | Not met; meaning of the value is unclear |
| Corrected version W-02 | Unit and history remain readable, with the same scope of protection | Additional comparison prior to further release |
| Shipping | Actually W-02 to the agreed recipient | Shipping document references the correct version. |
| Later Review | Q-01, W-02 and correction decision assignable | No assertion that W-02 is unchanged original |
6. Inspect for visible staining and check stored contents
A black area on the screen does not prove that the underlying information in the issued document is inaccessible. As a standalone testing recommendation, verify appropriate output pathways, text search functionality, copy functions, and relevant metadata of the actually used tools. This is not a claimed behavior of a specific PDF product.
Simultaneously assess the other error direction: Were the required pages, units, time references, or originations accidentally omitted? The test must take into account the agreed-upon protection scope and the required medical content. A simple comparison of file size or page count is insufficient to reliably address these two questions.
7. Handle errors, inquiries, and storage organization processes
If an inappropriate container is issued, the incident must be investigated in a traceable manner. Identify the recipient, affected information, and potential consequences. Corrective actions, further communication, and, if applicable, data protection measures will be decided based on the actual facts of the case; this document does not establish a general reporting obligation.
Define how legitimate queries shall obtain access to the required context thereafter. A strict protection that prevents any quality control activity does not alleviate the PV evidence obligation, nor does unbounded access. Retention and deletion policies shall be determined by the specific data types and applicable requirements. A backup alone does not constitute a defined audit trail system.
8. Checklist for controlled document dissemination
Use this internal checklist prior to a new transfer method or a change in processing tool. In the example, not only the removed identity is relevant, but also the correctly retained medical unit. Both results must match.
For small teams, clear file ownership and a unique release status are particularly helpful. Avoid parallel copies with ambiguous names that may later be selected as the release version. The additional control required depends on the specific process and risk.
- Is the source and edited version clearly linked?
- Purpose and intended user group defined?
- Is medical context required?
- Are edits and corrections traceable?
- Were concealed contents and relevant distribution pathways verified?
- Actually sent version verifiable?
- Are EudraVigilance field guidelines applied separately?
- Is authorized later access and retention governed?
Project experience and collaboration
Assess the need for source evidence alongside access permissions
With case processing, data protection and the system team, we clarify who needs the source document and for what purpose. Using controlled examples, we trace roles, attachments and preparation for onward transfer. Internal quality review needs different information from a submission under EudraVigilance masking rules. We assess whether the controls preserve the evidence needed and demonstrably restrict unauthorised access. The responsible functions retain operational and data protection decisions.
Frequently asked questions about Pharmacovigilance source documents
Must all internal source documents be anonymized?
No. GVP Module VI requires that source data or its representation remain readily accessible for quality control (VI.B.5). Access and processing must be protected in accordance with their intended purpose. EudraVigilance masking applies to specific submission fields and does not imply that all internal source documents should be anonymized independently of their intended use.
Is a darkened PDF automatically an appropriate source copy?
Does MSK mean the same as unknown?
No. The addendum distinguishes between existing data that requires masking and data that is not available to the sender. Use the appropriate representation for the specific field. A blanket substitution of all blank or protected values with the same code distorts this meaning.
Sources: [3]
May we prudently leave more E2B fields blank?
No. When submitting data to EudraVigilance, masking and empty fields should be restricted to the data elements specified in the GVP Addendum II. The required information listed in Table VI.Add.II.3, where available, shall neither be masked nor pre-emptively cleared; these data elements support signal management, duplicate detection, and case handling. For fields explicitly required to be masked, a null flavor shall be applied if data is present. Data transfers to partners outside of EudraViligance shall be evaluated separately based on their intended purpose and data protection framework.
Sources: [3]
Does technical support always require access to the complete source?
What do we assess following a staining event?
Both the intended protection and the retained content. Verify the relevant output and potential residual information using appropriate tools. Additionally, review medical information, units, temporal trend, and case assignment. The example demonstrates that a hidden unit can already constitute a significant error.
Must each distributed copy contain the same information?
Can we delete the source after creating a copy?
Is an unauthorized visible name always to be reported within the same time frame?
No. First, it must be determined whether a breach of personal data protection has occurred. Under Article 33 of the GDPR, the data controller must report such a breach without delay and, where possible, within 72 hours of becoming aware of it to the supervisory authority, unless it is anticipated that the breach will not result in a risk to the rights and freedoms of individuals. Any processor must notify the data controller without delay. Every breach must be documented. In cases where a high risk is anticipated, Article 34 further requires immediate notification to the affected individuals, subject to the specified exceptions. Therefore, access, the personal data involved, and the recipients must be readily traceable.
Sources: [4]
What is the most important organizational control for small teams?
A clear linkage between source, work version, and actual shipment. Identify responsible parties for processing, required review, and inquiries. This enables subsequent evaluation of which information formed the basis of a case decision and which version was received by the recipient.
Sources and review date
Sources checked on 7 October 2026 include GVP Modules I and VI and the 2025 Addendum II to Module VI. Masking fields for electronic transmission differs from editing documents internally. The document case is a practical example.
- EMA: GVP Module I – Pharmacovigilance Systems and Quality Management SystemsEMA/541760/2011; applicable from 02.07.2012; I.B.10–11, p. 9–10: Records, protection and access
- EMA: GVP Module VI – Collection, Processing, and Reporting of Suspected CasesRev. 2, July 28, 2017; applicable from November 22, 2017; VI.B.4–5, p. 17–18; VI.C.6.2.2.6, p. 58
- EMA: GVP Module VI Addendum II – Masking of personal data in ICSR submissionsEMA/178902/2025, 22.07.2025; applicable from 25.07.2025; VI.Add.II.1–6, in particular Tables 1–3, pages 3–7 and 12–14
- EU: General Data Protection Regulation (EU) 2016/679Article 33: Reporting to the supervisory authority, notification to data processors, and documentation; Article 34: Notification to affected parties in cases of anticipated high risk including exceptions. Official text reviewed on 18 October 2026.
Sources checked: .
Jointly design source protection and incident reporting
We support you with purpose-driven data pathways, access rules, and review cases for processed source documents in the PV process.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

