Signal Management Audit Readiness
- Signal Management Audit Readiness
- Introduction
- What Inspectors Are Trying to Determine
- The Audit Readiness Principle
- Inspection Readiness Across the Signal Lifecycle
- Regulatory Context and Inspection Relevance
- Governance and Oversight Considerations
- Evidence Requirements and Redacted Template Examples (Inspection-ready)
- Metrics Definitions and Demonstrable Timelines (Inspection-ready)
- Audit-trail Screenshots — Practical Capture and Redaction Guidance
- Demonstrable Inspection Pack — What to Provide to Inspectors
- Governance: Roles, Responsibilities and Demonstrable Oversight
- Practical Implementation Checklist — Prepare Before the Inspection
- Appendix: Templates (Redacted, Inspection-ready)
- Final Remarks
- References
Introduction
Signal management is one of the most frequently examined pharmacovigilance processes during audits and regulatory inspections. Inspectors view signal management as a critical control process because it influences the identification, evaluation and management of safety concerns throughout the lifecycle of a medicinal product.
A common misconception is that inspection readiness consists primarily of ensuring that procedures exist and documents are available. In reality, inspectors generally seek evidence that signal management activities are functioning effectively in practice.
The central inspection question is often straightforward:
Can the organisation demonstrate that it identifies, evaluates, escalates and manages potential safety concerns in a systematic and scientifically justified manner?
Audit readiness therefore depends less on presentation and more on process maturity, governance effectiveness and documentary evidence.
What Inspectors Are Trying to Determine
Although inspection approaches vary, signal management reviews commonly focus on several fundamental questions:
- How potential signals are identified
- How observations are reviewed
- How decisions are made
- How significant concerns are escalated
- How actions are implemented
- How oversight is maintained
Most inspection findings arise when organisations cannot clearly answer one or more of these questions. The issue is frequently traceability and governance rather than scientific disagreement.
The Audit Readiness Principle
A useful way to think about audit readiness is through reconstruction.
An inspector should be able to select a signal and reconstruct its lifecycle from beginning to end. The reviewer should be able to determine:
- When the observation was detected
- How it was reviewed
- Why validation decisions were made
- How prioritisation occurred
- What assessment activities were performed
- What actions were implemented
- How the signal was closed
If this reconstruction cannot be performed reliably, audit risk increases substantially.
Inspection Readiness Across the Signal Lifecycle
Readiness should exist across every stage of signal management.
Detection
↓
Validation
↓
Prioritisation
↓
Assessment
↓
Governance Review
↓
Action Implementation
↓
Closure
Each stage should generate evidence that demonstrates:
- Process execution
- Scientific rationale
- Appropriate oversight
- Adequate documentation
Inspectors frequently trace signals through multiple stages to assess process consistency.
Regulatory Context and Inspection Relevance
Key references auditors and inspectors commonly use include:
- EMA GVP Module I (Pharmacovigilance Systems and Their Quality Systems) — quality systems and audit expectations
- EMA GVP Module III (Pharmacovigilance Inspections) — inspection scope and evidence expectations
- EMA GVP Module IX (Signal Management) — procedural expectations for signal detection, validation, prioritisation and assessment
- Directive 2001/83/EC and Regulation (EC) No 726/2004 — legal obligations for market authorisation holders
- Commission Implementing Regulation (EU) No 520/2012 — pharmacovigilance system master file aspects
Inspectors expect traceability, scientific justification, demonstrable timelines and effective governance in line with the above. They will seek to reconcile what procedures require with what actually occurs in practice.
Governance and Oversight Considerations
Governance is an inspection focus equal to technical capability. Audit-ready governance demonstrates:
- Clear decision-making authority (committee charters, committee membership and delegation logs)
- Documented escalation pathways and triggers (including thresholds for Emerging Safety Issues (ESIs))
- QPPV visibility (evidence of oversight, not necessarily operational tasking)
- Vendor oversight (SLAs, quality metrics, audit reports, evidence of incorporation into core processes)
- Version-controlled procedures and change-control records
Well-documented governance reduces risk that a strong technical process will still generate inspection findings due to poor oversight or unclear responsibilities.
Evidence Requirements and Redacted Template Examples (Inspection-ready)
The following tables provide inspection-ready evidence requirements and redacted template examples for every stage of the signal lifecycle. Each stage includes:
- Minimum evidence that inspectors are likely to request
- Practical implementation notes (what to collect and how to present it)
- A redacted template example suitable for inclusion in an inspection pack
- Example of audit-trail screenshot content and capture guidance
All templates are intentionally redaction-friendly: include unique record identifiers and links to source documents but redact patient identifiers and proprietary analytics. Use hashed user IDs or role descriptions rather than personal full names when appropriate.
Notes on redaction: Maintain demonstrable linkage between redacted material and source records. If names are redacted, provide a separate, secure mapping document for inspectors on request (not included in the general inspection pack). Ensure all redactions are consistent across all documents.
Stage A — Detection
Table: Evidence Requirements for Detection
| Evidence item | Minimum content | Implementation notes |
|---|---|---|
| Source inventory entry | Data source, query name/version, frequency, owner | Exportable list from PV analytics system showing last run date |
| Initial observation record | Date/time detected, system-generated ID, brief description, source snapshot | Capture system screenshot showing highlighted signal candidate |
| Screening log entry | Reviewer, date/time, preliminary flag (Y/N), brief rationale | Use electronic screening log with audit trail |
| Detection SOP excerpt | SOP version, effective date, relevant section reference | Include SOP section that defines detection frequency and responsibilities |
| Metrics snapshot | Number of new detections per period, detection latency | From signal tracking dashboard |
Redacted Detection Template (inspection-ready)
Signal ID: SIG-2025-0001
Product: [Redacted product name]
Detection Source: Spontaneous reports database (Query: QT-ADR-Cardio-v3)
Date/Time detected: 2026-05-08 09:23 UTC
Automatic flag: Yes
First reviewer (role): PV Screening Specialist (USR_HASH_12)
Screening note (redacted): "Cluster of [preferred term redacted] in patients ≥65; signal strength low/moderate; source consistent with medication start window."
Linked evidence: CaseIDs [redacted], Query run report (File: QueryReport_QT-ADR-Cardio-v3_20260508.pdf)
Action: Proceed to Validation (date triggered)
Audit-trail Screenshot Guidance — Detection
- Capture the system state showing the record list and the selected record highlighted, including:
- System name and version (top-left)
- Unique Record ID (SIG-2025-0001)
- Timestamp of detection
- User role / user ID (hashed) who exported the detection
- Query name and parameters
- Ensure the search filter and query run log lines are visible.
- Redact personal data but preserve timestamps and system IDs.
Placeholder screenshot caption: [ Screenshot A1: Detection list view — columns: Record ID | Product | Source | Detected On | Status | Owner (example values) ]
Stage B — Validation
Table: Evidence Requirements for Validation
| Evidence item | Minimum content | Implementation notes |
|---|---|---|
| Validation decision record | Date/time, validator, criteria applied, decision (validate/not validate), rationale | Saved within signal tracking system and linked to source evidence |
| Supporting evidence list | Case extracts, literature hits, database query outputs | Provide redacted extracts with file references |
| Risk filter applied | Description of filters (e.g., seriousness, temporality) and threshold used | Include SOP reference and version |
| Validation workflow audit trail | Timestamps for each action, user IDs, change reason | Export from workflow system |
| Metrics | Time from detection to validation, % validated within target | Present historical KPI for inspection context |
Redacted Validation Template (inspection-ready)
Signal ID: SIG-2025-0001
Validation ID: VAL-2025-089
Validator (role): Signal Validation Scientist (USR_HASH_45)
Date validation initiated: 2026-05-08 10:12 UTC
Date validation completed: 2026-05-10 14:30 UTC
Validation criteria applied: Temporality, dechallenge/rechallenge, case clustering, seriousness
Decision: Validated for further review (reason summary)
Rationale (redacted): "Aggregate pattern of [adverse event class] temporally associated with initiation; case series meets pre-defined clustering threshold; no alternate explanation sufficient."
Supporting files: CaseExtracts_redacted.zip; QueryReport_QT-ADR-Cardio-v3_20260508.pdf; PubMedHits_20260509.pdf
Next step: Prioritisation
Audit-trail Screenshot Guidance — Validation
- Capture sequential workflow actions: "Validation initiated", "Assigned to validator", "Validation completed".
- Show timestamps, user role hashed, and change reasons.
- Include a version history snapshot if a validation note was updated.
- Example fields visible: Action | Performed by | Date/Time | Comments | Status
Placeholder screenshot caption: [ Screenshot B1: Validation workflow audit trail — shows timestamps and validator actions for VAL-2025-089 ]
Stage C — Prioritisation
Table: Evidence Requirements for Prioritisation
| Evidence item | Minimum content | Implementation notes |
|---|---|---|
| Prioritisation record | Date/time, triage owner, priority score/category, justification | Use numeric or categorical scoring with documented thresholds |
| Prioritisation matrix | Criteria and weights used (seriousness, frequency, public health impact, labelling status) | Include SOP or scoring tool snapshot |
| Committee triage minutes (if applicable) | Attendees (roles), key discussion points, decision | Redact personal names but show roles and votes |
| Metrics | % of signals escalated per priority band, average time to prioritise | Provide historical dashboards |
| Escalation trigger log | Date/time when priority triggered governance pathway | Link to governance notification record |
Redacted Prioritisation Template (inspection-ready)
Signal ID: SIG-2025-0001
Prioritisation record: PRI-2025-033
Triage date: 2026-05-11 09:05 UTC
Triage owner (role): Signal Triage Lead (USR_HASH_78)
Priority score: 7/10 (High)
Scoring factors: Seriousness 4/4; Case count 2/3; Temporal association 1/1; Public health impact 0/1
Rationale summary: "High seriousness with clustering in elderly population and plausible mechanism; escalate to full assessment and governance notification."
Escalation: Pharmacovigilance Risk Committee (PRC) notified 2026-05-11 09:20 UTC
Next step: Full assessment initiated
Audit-trail Screenshot Guidance — Prioritisation
- Show scoring tool input screen with criteria ticked and resulting score.
- Show history of score changes, the user who applied the score, and timestamps.
- Include screenshot of automated notification to PRC (email or system alert with timestamp).
Placeholder screenshot caption: [ Screenshot C1: Prioritisation scoring tool — criteria, weights, final score and notification sent ]
Stage D — Assessment
Table: Evidence Requirements for Assessment
| Evidence item | Minimum content | Implementation notes |
|---|---|---|
| Assessment report | Versioned report with authorship (roles), dates, methods, evidence summary, conclusion, confidence level | Store in controlled document repository with version history |
| Analyses and datasets | Line listings, aggregate tables, disproportionality outputs, sensitivity analyses (redacted) | Provide redacted extracts and analysis logs |
| Literature review | Search strategy, databases, results, selection rationale | Include date-stamped search output files |
| Alternative hypothesis log | Considered confounders, competing explanations, limitations | Documented within report |
| Assessment timelines | Start date, milestones (interim reports), completion date | Demonstrable against SOP targets |
| Governance notification | Governance package sent to committee with attachments, delivery receipts | Include proof of distribution |
Redacted Assessment Template (inspection-ready)
Signal ID: SIG-2025-0001
Assessment Version: v1.0
Assessment lead (role): Signal Assessment Lead (USR_HASH_21)
Assessment start date: 2026-05-11
Interim update: 2026-05-25 (v0.5)
Assessment completion date: 2026-06-08
Objective: To determine plausibility and magnitude of association between [redacted AE class] and product X in age ≥65
Methods: Case series review; disproportionality analysis in spontaneous reporting database; literature review (PubMed, Embase up to 2026-06-01)
Key findings (redacted): Increased reporting rate compared with background; temporal clustering around initiation; biological plausibility supported by mechanism-related literature.
Conclusion: Association plausible; further pharmacoepidemiology study recommended; regulatory notification recommended.
Attachments: AssessmentData_v1.0_redacted.zip; LitSearch_20260601.pdf; DPA_outputs_20260602.csv
Next steps: PRC review scheduled 2026-06-10
Audit-trail Screenshot Guidance — Assessment
- Capture document repository entry showing version history (v0.5 → v1.0), editor roles and timestamps.
- Show analytics platform export with query time, dataset name, user ID.
- Include screenshot of the assessment workflow showing assignment, reviews, and approvals.
Placeholder screenshot caption: [ Screenshot D1: Assessment report version history and attached analysis files ]
Stage E — Governance Review
Table: Evidence Requirements for Governance Review
| Evidence item | Minimum content | Implementation notes |
|---|---|---|
| Committee package | Agenda, minutes, attendees (roles), material presented, decisions, action owners, due dates | Minutes should capture scientific rationale and votes/decisions |
| Escalation log | Proof of notification, time-to-notification, recipient roles | Include automated alerts and read receipts where available |
| QPPV sign-off evidence | QPPV notes, sign-off date/time, summary of oversight | QPPV should be able to demonstrate visibility |
| Committee charters | Authority, remit, membership and quorum rules | Link to current charters with effective dates |
| Metrics | Meeting frequency vs. target, backlog of items awaiting governance | Provide dashboard exports |
Redacted Committee Minutes Template (inspection-ready)
Committee: Pharmacovigilance Risk Committee (PRC)
Meeting date: 2026-06-10
Attendees (roles): PRC Chair (Medicines Safety Officer), QPPV (QPPV_HASH), Head of PV (USR_HASH_04), Epidemiology Rep (USR_HASH_55), Regulatory Affairs (USR_HASH_11)
Agenda item: SIG-2025-0001 — [Adverse event class redacted]
Summary of discussion (redacted): Key points discussed included plausibility, public health impact, need for additional epidemiology, and urgency of regulatory notification. Alternative explanations considered and discounted: [redacted].
Decision: Recommendation to file expedited notification to authorities and commission pharmacoepidemiological study (vote: unanimous).
Actions:
- Regulatory affairs to prepare expedited notification (Owner: RA Lead (USR_HASH_11); Due: 2026-06-15)
- Epidemiology to design protocol draft (Owner: Epidemiology Rep; Due: 2026-06-24)
QPPV oversight note: QPPV concurs with decision and requested weekly monitoring updates until closure.
Minutes prepared by: PRC Secretary (USR_HASH_09)
Audit-trail Screenshot Guidance — Governance Review
- Capture committee package upload with timestamps and file versioning.
- Show meeting attendance record (role-based), action assignments and due dates in action tracker.
- Include a screenshot of the official notification sent to regulators (redacted) with timestamp and delivery confirmation.
Placeholder screenshot caption: [ Screenshot E1: Committee meeting record showing agenda, attendees (roles) and actions assigned ]
Stage F — Action Implementation
Table: Evidence Requirements for Action Implementation
| Evidence item | Minimum content | Implementation notes |
|---|---|---|
| Action tracking record | Owner, due date, status, completion evidence, verification | Use central action tracker with audit trail |
| Regulatory submission evidence | Submission cover, submission date/time, acknowledgement/receipt | Redact confidential content, provide acknowledgement screenshots or tracking IDs |
| Study documentation | Protocol, approvals, milestones, data lock, interim reports | Store in study management system with version history |
| Product information change records | Change request, approval, implementation date | Link to post-implementation verification |
| Vendor deliverables | Evidence of deliverables received, QC checks, change control | Include vendor sign-off logs |
| Metrics | % actions completed on time, overdue action backlog | Provide dashboards with trend history |
Redacted Action Tracking Template (inspection-ready)
Signal ID: SIG-2025-0001
Action ID: ACT-2026-112
Action description: Submit expedited safety notification to EMA (DSUR/CI procedures)
Owner (role): Regulatory Affairs Lead (USR_HASH_11)
Date assigned: 2026-06-10
Due date: 2026-06-15
Status: Completed
Completion evidence: Submission confirmation (TrackingID: EMA-ACK-20260614) [redacted copy attached]
Verification: QPPV verified submission upload and confirmation (QPPV_HASH) on 2026-06-14 17:02 UTC
Notes: Notification included assessment summary and planned epidemiology study.
Audit-trail Screenshot Guidance — Action Implementation
- Capture action tracker entry with history: created date, updates, completion toggle, evidence attachments.
- Show regulatory portal submission acknowledgement with timestamp and tracking ID (redact content but preserve ID).
- Include vendor deliverable acceptance logs with timestamps and reviewer roles.
Placeholder screenshot caption: [ Screenshot F1: Action tracker entry showing status transitions, attachments and final verification ]
Stage G — Closure
Table: Evidence Requirements for Closure
| Evidence item | Minimum content | Implementation notes |
|---|---|---|
| Closure report | Rationale for closure, summary of evidence, post-action surveillance plan | Version-controlled and signed-off by responsible roles |
| Post-closure monitoring plan | Metrics to monitor, frequency, responsible owners | Include surveillance timelines and triggers for reopening |
| Final actions log | All actions closed with evidence, date of closure, verification | Action tracker closed items exported with audit trail |
| Archival evidence | Repository location, retention period, access controls | Provide record of archived package and index |
| Metrics | Time to closure, re-open rate, outcomes of post-closure monitoring | Dashboard export for trend analysis |
Redacted Closure Template (inspection-ready)
Signal ID: SIG-2025-0001
Closure report: CL-2026-042
Closure date: 2026-12-01
Closure author (role): Signal Assessment Lead (USR_HASH_21)
Summary of rationale (redacted): Post-implementation surveillance through 2026-11 showed no increase in confirmed cases after label update and risk minimisation. Epidemiological study interim analysis did not show statistically significant association. Benefit-risk considered maintained.
Final actions: All action items completed and verified (see ACT- records)
Post-closure monitoring: Quarterly dashboard monitoring for 12 months; trigger for re-open: confirmed case cluster > pre-defined threshold or new external evidence
Archival location: PV Document Repository / Signals / SIG-2025-0001 / archive_20261201 (access restricted)
Approvals: QPPV (QPPV_HASH) sign-off: 2026-12-02
Audit-trail Screenshot Guidance — Closure
- Capture final action tracker export showing all related ACT-IDs closed and verification stamps.
- Show closure report version history and QPPV sign-off entry.
- Include screenshot of archived package index (no patient data) showing file names and timestamps.
Placeholder screenshot caption: [ Screenshot G1: Closure report version history and action tracker closed-item export ]
Metrics Definitions and Demonstrable Timelines (Inspection-ready)
Inspectors will expect metrics that are: accurate, consistently defined, tied to SOP targets, trended over time and used in governance. Below are recommended metrics with definitions, calculation method and suggested inspection thresholds. These should be aligned with internal SOPs and regulatory expectations (GVP Module IX).
Table: Core Signal Management Metrics — Definitions and Targets
| Metric | Definition | Calculation | Suggested target | Inspection relevance |
|---|---|---|---|---|
| Detection frequency | Number of candidate signals detected per period | Count of new records entered into detection log per month | Context dependent (trend monitoring rather than absolute target) | Demonstrates surveillance activity and source coverage |
| Detection latency | Time from event occurrence (or case report receipt) to detection | Median days between CASE_RECEIVED and DETECTION_TIMESTAMP | ≤ 30 days for spontaneous; ≤7 days for automated pharmacovigilance monitoring | Inspectors check timeliness—high latency suggests gaps |
| Validation timeliness | Time from detection to validation decision | Median days between DETECTION_TIMESTAMP and VALIDATION_COMPLETED | ≤ 7 calendar days for routine; ≤48–72 hours for ESIs | Shows responsiveness and process control |
| Prioritisation timeliness | Time from validation to prioritisation decision | Median days between VALIDATION_COMPLETED and PRIORITISATION_COMPLETED | ≤ 7 calendar days | Shows effective triage and escalation |
| Assessment cycle time | Time from assessment initiation to final assessment report | Median days between ASSESSMENT_START and ASSESSMENT_COMPLETION | 30–90 days depending on complexity; interim updates should be timely | Inspectors expect documented rationale for timeline selection |
| Governance notification latency | Time from prioritisation to committee notification | Median hours/days | Within next scheduled committee for non-urgent; within 24–72 hours for high priority/ESI | Demonstrates governance visibility |
| Action implementation rate | % of actions completed on or before due date | (On-time completed actions / total completed actions) *100 | ≥90% | Demonstrates follow-through capability |
| Time-to-closure | Time from detection to closure | Median days | Variable; provide justifying SOP-based targets | Inspectors will assess whether durations are justified and monitored |
| Re-open rate | % of closed signals re-opened | (Re-opened signals / total signals closed) *100 | Low (<5%) | High re-open rate may indicate premature closure or insufficient monitoring |
| QPPV visibility | % of signals with documented QPPV oversight | (Signals with QPPV note / total signals assessed) *100 | ≥95% for high-priority signals | QPPV visibility evidence supports effective oversight |
Practical Implementation Notes
- Define metrics in SOPs with precise field mappings to your IT system (e.g., DETECTION_TIMESTAMP = system field DetectionDateTime).
- Provide metric calculation scripts or spreadsheet formulas as part of your inspection pack.
- Produce trend charts for at least 12 months showing moving averages and exceptions annotated with explanations.
- For ESIs, maintain a separate rapid-response KPI set (time-to-escalate, time-to-notify authorities).
Demonstrable Timelines and Evidence
Inspectors will want to see demonstrable timelines tied to evidence. Recommended approach:
- For every timeline (e.g., detection → validation), present a table for sampled signals showing:
- Signal ID
- Detection timestamp (system)
- Validation completed timestamp (system)
- Prioritisation timestamp
- Assessment start/completion timestamps
- Committee notification timestamp
- Action assigned/completed timestamps
- Closure timestamp
- Attach corresponding audit-trail screenshots that show each timestamp and the user role who executed the step.
Sample Timeline Table (for inspection)
| Signal ID | Detected | Validated | Prioritised | Assessment Start | Assessment Complete | PRC Notified | Regulatory Submission | Actions Closed | Closed |
|---|---|---|---|---|---|---|---|---|---|
| SIG-2025-0001 | 2026-05-08 09:23 | 2026-05-10 14:30 | 2026-05-11 09:05 | 2026-05-11 | 2026-06-08 | 2026-06-10 10:05 | 2026-06-14 | 2026-10-31 | 2026-12-01 |
Accompany this table with links to the exact system snapshots and document versions.
Audit-trail Screenshots — Practical Capture and Redaction Guidance
Inspectors commonly ask to see audit trails to confirm the authenticity and chronology of events. Good practice for audit-trail screenshots:
- Include context:
- System name/version
- Record unique ID prominently visible
- Page URL (redact domain if necessary for proprietary reasons but keep system path)
- Show sequential actions:
- Creation, edits, status changes, assignments, attachments uploaded
- User role or hashed user ID for each action
- Clear timestamps with timezone indication
- Preserve before/after states:
- If a field was changed, capture both previous and updated values with the edit comment
- Include attachments view:
- Show filenames, upload timestamps and user who uploaded
- Redaction rules:
- Remove or mask personal data (patient identifiers, staff personal contact)
- Do not redact timestamps, system IDs, or role descriptors
- If redacting large textual content, show the redacted placeholder plus a file reference and a secure mapping file available to inspectors on request
Example of what an audit-trail screenshot should capture (textual representation for inclusion in packs):
[Audit Trail — Signal Record: SIG-2025-0001]
Action: Record Created
Performed by: System_Auto (Query: QT-ADR-Cardio-v3)
Timestamp: 2026-05-08 09:23 UTC
Action: Assigned to PV Screening Specialist (USR_HASH_12)
Timestamp: 2026-05-08 09:26 UTC
Action: Validation completed
Performed by: Signal Validation Scientist (USR_HASH_45)
Timestamp: 2026-05-10 14:30 UTC
Change note: "Validated for further review — summarised rationale" (redacted)
Attachment: QueryReport_QT-ADR-Cardio-v3_20260508.pdf (uploaded 2026-05-08 09:24 UTC)
Include such text blocks alongside images for accessibility and to reduce reliance on images alone.
Demonstrable Inspection Pack — What to Provide to Inspectors
An inspection-ready pack for sampled signals should include:
- Index document listing all materials with document IDs and repository locations
- Exported signal record (PDF) with redactions applied and an audit-trail narrative
- Redacted case extracts that support validation/assessment conclusions
- Assessment report with version history and analyses (redacted as needed)
- Committee package and minutes (redacted names, show roles)
- Action tracker export with completion evidence and verification
- Regulatory submission acknowledgement (redacted) and submission timeline
- Metrics dashboard export for the relevant reporting period
- SOP extracts and governance documentation that applied during the lifecycle
- Mapping document (secured separately) linking hashed user IDs to person, if requested under inspection confidentiality protocol
Provide the inspection team with a single index PDF that links to the referenced artifacts and a clear contact point for secure access to any non-redacted material required under controlled conditions.
Governance: Roles, Responsibilities and Demonstrable Oversight
For inspection readiness ensure that:
- Committee charters and delegation logs are up to date and accessible
- QPPV notes are present on high-priority signals with sign-off dates
- Governance escalations are demonstrably triggered according to SOP-defined thresholds
- Internal audit and management review findings relating to signal management have action plans with tracked closure
- Vendor oversight records (KPIs, audits, CAPAs) are linked to signal activities where outsourced work contributed to detection, analysis or actions
Evidence examples for governance:
- Delegation log showing that PRC has authority to recommend regulatory submissions
- QPPV oversight email (redacted) with reference to Signal ID and date/time confirming awareness and concurrence
- Vendor performance report demonstrating delivery of requested analyses (with timestamps and reviewer sign-off)
Practical Implementation Checklist — Prepare Before the Inspection
- Map system fields to SOP definitions for all timeline metrics (create a one-page mapping document).
- Prepare a curated sample of 3–5 signals at different life-cycle stages with full package files (redacted).
- Export audit trail segments for each sample signal showing complete chronology.
- Produce metric trend charts and provide calculation methods.
- Ensure committee minutes capture scientific reasoning and actions (not just attendance).
- Confirm QPPV signatures/notes are present on high-priority signals.
- Confirm action tracker contains verification evidence (e.g., submission receipts).
- Prepare a single index and navigation guide to the signal packages.
- Create a secure mapping file for hashed user IDs and provide under inspector confidentiality terms if requested.
Appendix: Templates (Redacted, Inspection-ready)
Below are templates that can be used directly in inspection packs. Replace bracketed placeholders and apply redaction rules before inclusion.
1) Detection record (template)
Signal ID:
Product:
Detection Source:
Query name/version:
Detected on:
Detected by (role):
System Record ID:
Initial screening note:
Linked artefacts:
Next step:
2) Validation record (template)
Validation ID:
Signal ID:
Validator (role):
Validation start:
Validation complete:
Criteria applied:
Decision:
Rationale (concise):
Supporting files (list):
Next step:
3) Prioritisation record (template)
Prioritisation ID:
Signal ID:
Triage lead (role):
Date:
Priority score:
Scoring details:
Escalation required:
Escalation timestamp:
Next step:
4) Assessment report header (template)
Signal ID:
Assessment version:
Assessment lead (role):
Start date:
Completion date:
Methods summary:
Key findings (concise):
Conclusion:
Recommendations:
Attachments:
Approval signatures (roles & dates):
5) Committee minute excerpt (template)
Committee:
Meeting date:
Agenda item:
Attendees (roles):
Summary of discussion:
Decision (verbatim):
Actions (ID / Owner / Due date):
QPPV oversight note:
Minutes prepared by:
6) Action tracker entry (template)
Action ID:
Signal ID:
Description:
Owner (role):
Date assigned:
Due date:
Status:
Completion evidence:
Verification (role & timestamp):
7) Closure report (template)
Signal ID:
Closure author (role):
Closure date:
Closure rationale:
Evidence of outcomes:
Post-closure monitoring plan:
Archived location:
Approvals:
Final Remarks
Inspection readiness for signal management is demonstrable: it is not achieved by producing lengthy documents at short notice but by operating a mature, well-documented, and governed process that consistently records decisions, timestamps, and evidence. The materials described above — structured templates, audit-trail exports, time-series metrics, and governance records — provide inspectors with the necessary reconstruction of the signal lifecycle. Preparing a curated inspection pack that maps SOP requirements to evidence and showing how metrics are calculated will materially reduce inspection risk and demonstrate control.
References
- EMA Good Pharmacovigilance Practices (GVP) Module III – Pharmacovigilance Inspections.
- EMA Good Pharmacovigilance Practices (GVP) Module IX – Signal Management.
- EMA Good Pharmacovigilance Practices (GVP) Module I – Pharmacovigilance Systems and Their Quality Systems.
- Commission Implementing Regulation (EU) No 520/2012.
- Regulation (EC) No 726/2004.
- Directive 2001/83/EC.
- CIOMS VIII Practical Aspects of Signal Detection in Pharmacovigilance.
- ICH E2E Pharmacovigilance Planning.