Table of contents
At a glance
Which computerised systems and databases need to be described in the PSMF?
Article 2(3) of Implementing Regulation (EU) No 520/2012 requires the PSMF to describe the location, function and operational responsibility of systems and databases used to receive, collate, record and report safety information and to assess their suitability. GVP Module II also recommends an overview covering validation status of important functions, change control, test types, backups, main electronic repositories and available documentation. The PSMF summarises the evidence and does not replace it.
- The PV function determines the description, not the product name alone.
- Several applications and outsourced services must establish a clear data pathway.
- Validation status and operational records are consolidated and clearly referenced.
Correctly define the scope of the PSMF system section
The focus is on the pharmacovigilance system for approved medicinal products for human use in the EU. GVP Module II.B.4.4 deals with computer systems and databases in the PSMF. Its description is to be distinguished from a general IT inventory list and from a complete technical architecture manual.
Start with the PV tasks: Where do security information entries originate, where are they processed, which data are aggregated for evaluation, and how do alerts reach the intended recipient? A system may be relevant to multiple tasks. Conversely, a single task may depend on multiple applications and organizations. Exactly this interdependence should become visible.
Sources: [1]
Integrate functions and validation evidence within a matrix approach
The following internal work aid translates the information from Module II into questions for PV and IT. Use clear internal identifiers and specific references. A general statement such as "a validated cloud solution" neither specifies the covered functions nor the scope of operational responsibility.
| Description field | Question to ask | Relevant evidence reference |
|---|---|---|
| Function and Data | What security information is assumed or used here? | Process and data flow |
| Site and Responsibility | Where is the function performed, and who operates and is responsible for it? | Organization and Service Provider Description |
| Suitability and Status | What usage and key functions are covered? | Validation assessment and associated documentation |
| Change and Testing | How are relevant changes evaluated and reviewed? | Change control procedure and test documentation |
| Backup and Storage | Which information and repositories are essential? | Operating procedures and retrievable data repositories |
Location and Responsibility for Outsourced Systems
For hosted or outsourced solutions, the relevant organisations and responsibilities must remain clearly defined. Describe who provides and operates the service, who is responsible for professional usage, and which information is materially relevant to the respective PV process. The name of a manufacturer alone does not address these questions.
GVP Module II links the system description to outsourced activities and relevant agreements. Under Module I, the marketing authorisation holder retains responsibility for its pharmacovigilance system when activities are outsourced. It need not perform every service itself, but it needs appropriate oversight and evidence of the services actually used.
Provide precise rather than generic representation of validation status
Describe the validation status of key functions and the type of evidence available. This may include the scope of usage covered, changes that have been implemented, and any existing limitations. A historical release for an earlier data pathway must not be considered valid evidence for a subsequent interface without proper evaluation.
The PSMF summary does not need to include all protocols, but it should lead to the relevant documentation and clearly indicate its subject matter. Supplier documentation may provide pertinent evidence; its adequacy depends on the actual coverage. Supplier documentation is not automatically fully sufficient nor inherently merely a meaningless baseline record.
Sources: [1]
Expected case: the intake portal changes and the repository stays
Example: A small company previously captured safety information through Portal Alt. Attachments were stored in a protected document folder and referenced in the Safety Database. Following a system transition, Portal Neu now receives reports; older source documents remain accessible in the same folder. The new data transfer pathway has been technically implemented, but the existing PSMF description still lists Portal Alt as the active entry point.
The required alignment distinguishes the new entry point, the continued use of the existing archive, and the safety database. The "Portal Alt" is no longer to be displayed as the current entry point; however, its remaining purpose and access to historical information must be clarified. The existing archive must not be removed solely because a new portal is being utilized.
In this example, the team reviews a new incoming record and a subsequent amendment to an older case. Expected are correct case assignments, accessible attachments, and traceable entry times. These review cases serve as a standalone work aid. They do not claim a predefined test volume or actual product testing performed.
| Component | Actual Status | PSMF-Required Specification | To be clarified: evidence required |
|---|---|---|---|
| Legacy portal | No new receipt; previous information affected | Purpose and access explanation | Transfer and availability of prior activities |
| Portal Neu | Active ingress and new transfer pathway | Record function, operator, and data pathway | Suitability of the new process and interface |
| Document repository | Existing and new relevant sources remain there | Furthermore, describe as a key retention point. | Access, case assignment, and operating procedures |
| Safety Database | Processing of new and existing cases | Connect existing function with modified input. | Traceable assignment of new cases and amendments |
Identify additional repositories and handovers
In addition to the safety database, other folders can be highly relevant for fulfilling PV tasks: for example, source documents, literature evaluation decisions, or evidence of submissions. The actual role these folders play within the described system is critical. A private working copy with no substantive function should be classified differently from the sole accessible folder containing a relevant source.
Describe necessary dependencies such that a reader can understand the path from entry to usage. Where a diagram is helpful, it should illustrate key stakeholders and transfer points. The level of technical detail should align with this purpose. A PSMF overview does not need to explain every server port, but it must not obscure a data transfer critical to case handling.
Checklist for Joint Maintenance by PV and IT
Review the system specification, particularly when there are changes to task allocation, application usage, interfaces, data storage, or operational responsibility. Periodic review alone is insufficient if key information has become outdated. The following questions help maintain alignment between technical descriptions and underlying documentation.
Establish a feasible information flow: Who identifies a relevant change, who assesses its impact on PV requirements, and who prepares the description? The PSMF will be easier to maintain when it refers to controlled, searchable documentation and ensures that the same information does not fragment across multiple independent lists.
- Are systems defined according to their actual PV function?
- Are the location, operator, and professional responsibility clearly defined?
- Are multiple applications and data repositories interconnected?
- Does the validation status relate to current usage?
- Have changes, test type, and relevant backups been consolidated?
- Are reliable references available for verification?
- Are service providers and agreements appropriately assigned?
- Does a relevant operational change eliminate the need to assess the impact on the PSMF?
What the PSMF provides and what remains outside its scope
The PSMF describes the pharmacovigilance system. Case files, validation documents, operational logs and complete agreements serve separate purposes. A good summary explains how the evidence fits together and where to find it without duplicating every document.
Therefore, for small teams, a robust functional overview is most beneficial initially. Effort arises from unclear responsibilities, scattered work logs, and undocumented changes. Simply increasing text does not resolve these issues. The most significant improvement is often a clear reference with defined ownership and a comprehensible statement regarding the covered operational status.
Sources: [1]
Project experience and collaboration
Reconcile the IT section with the actual flow of pharmacovigilance data
With Pharmacovigilance and IT, we follow a prepared safety case through the database, interface and related repositories. We compare the PSMF description with actual functions, sites and operating responsibilities. Clear processes may need only more precise references to existing records. Outsourced tasks or unexplained copies need additional coordination and evidence. We support the technical inventory. Your PV owners assess and maintain the authoritative PSMF description.
Frequently asked questions about Computerised systems in the PSMF
Does only the central safety database belong to the system module?
No. Module II.B.4.4 relates to systems and databases for acceptance, consolidation, capture, and reporting of safety information. The interrelationships among multiple applications should be clearly demonstrated. Therefore, additional relevant data repositories and functions may also need to be described; the central product identifier alone often does not fully represent the actual process.
Sources: [1]
Must every IT system of the company be included in the PSMF?
Not solely because it exists. Its role within the pharmacovigilance system is significant, as is the information required to describe that role. Start with the pharmacovigilance tasks and data pathways. A general inventory list may assist, but it neither replaces the professional delineation nor provides a clear description of the systems actually relevant to the process.
Sources: [1]
What specific information does Module II.B.4.4 require?
The binding basis is Article 2(3) of Regulation (EU) No. 520/2012: The location, function, operational responsibility, and suitability assessment of systems and databases used for safety information must be described in the PSMF. GVP Module II.B.4.4 recommends, as additional guidance, a comprehensive overview and summary of the validation status of key functions, change control, test type, backup procedures, critical data retention, and available documentation. This enables clear identification of which tasks are supported electronically and where the underlying evidence resides.
Does the PSMF state "the system is validated"?
Such a statement is often insufficiently informative when the intended use and scope of coverage remain unclear. Describe the status of key functions and the type of associated documentation. A new interface or altered usage may require different validation evidence than that originally assessed for the initial state. A product designation alone does not constitute proof of coverage.
Sources: [1]
Must all test protocols be fully copied into the PSMF?
The addressed section requires a summary and description of available documentation. This does not justify the wholesale copying of all protocols into the PSMF. However, appropriate references must lead to the relevant and accessible documentation. A list lacking a clear objective or reliable retrievability does not fulfill this practical purpose.
Sources: [1]
How are cloud providers and service vendors presented?
Describe the functions actually used, organisations involved, operational responsibilities and relevant agreements. Outsourcing does not remove the marketing authorisation holder's responsibility for its PV system. Internal teams need not repeat all services. Assess supplier evidence against its suitability and actual coverage.
Are tables and paper-based processes also relevant?
Yes, to the extent that it performs critical functions within the described PV system. Module II also addresses paper-based systems and their data management, integrity, and accessibility. A procedure is not irrelevant solely because it does not utilize specialized software. Describe the actual usage and the associated controls.
Sources: [1]
What must be updated after a portal change?
Review the description of the active input, data pathways, responsibilities, and supporting evidence. Concurrently, clarify which prior information must remain accessible. In the example of this article, document retention remains relevant, even though the intake portal is being replaced. Technical commissioning alone does not correct outdated PSMF descriptions.
Is the PSMF our IT emergency response handbook?
No. It primarily summarizes relevant backup procedures and data retention practices. However, the operational disaster recovery plan must include specific, actionable instructions and defined responsibilities. An appropriate reference should link both levels. Extensive technical recovery details do not need to be duplicated in the PSMF unless there is clear and demonstrable value.
How can the care effort be limited?
Use a common functional overview, clear responsibilities and controlled references to existing documents. Link relevant changes to the examination of the PSMF effect. This is a separate organizational recommendation; it does not create a general fixed update frequency. A true description of the actual pharmacovigilance system remains crucial.
Sources and review date
Source date: 7 October 2026. Focus is GVP Module II Revision 2, particularly Section II.B.4.4. The system matrices are standalone reference tools. The full PSMF structure and other obligations are not exhaustively addressed herein.
- EMA: GVP Modul II – Pharmacovigilance System Master FileRev. 2 as of 28.03.2017 (EMA/816573/2011 Rev 2), effective from 31.03.2017; Section II.B.4.2–4.7, in particular II.B.4.4, pages 10–13
- EMA: GVP Module I – Pharmacovigilance Systems and Quality Management SystemsEMA/541760/2011; applicable from 02.07.2012; I.B.10–11.3, p. 9–12; I.C.1.5, p. 18–19
- European Union: Implementing Regulation (EU) No. 520/2012, Article 2, paragraph 3Binding PSMF statements regarding computerized systems and databases. Article 2 paragraph 3 as of 18.10.2026 additionally verified against the official original text; further implementation recommendations in GVP Module II are presented separately.
Sources checked: .
Integrate PSMF with the actual system landscape
We help you organize relevant systems, data dependencies, and validation evidence in a clear and understandable manner. Together with PV and IT, we finalize the descriptions and identify gaps in responsibility and documentation.
- 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.

