Signal Tracking and Documentation

Introduction

Signal management is a structured, regulated decision-making process: observations are detected, validated, prioritised, assessed and — where necessary — acted upon. Documentation is the thread that binds scientific reasoning, governance oversight and regulatory compliance. The capacity to reconstruct how and why decisions were made is a regulatory expectation and an inspection focus. This article sets out both the principles and practical artefacts you should embed within the signal lifecycle so that evidence of compliance is available immediately.

This guidance aligns with EMA GVP Module IX (Signal Management), GVP Module I (Pharmacovigilance Systems and Their Quality Systems), GVP Module III (Pharmacovigilance Inspections) and related EU legislation (e.g., Regulation (EC) No 726/2004, Implementing Regulation (EU) No 520/2012). Templates and completed examples are provided to support direct implementation and inspection readiness.

Why documentation matters (concise summary)

Documentation provides traceability, governance evidence, proof of timely escalation and closure, and a defensible record for inspections. It must capture the decisions made, the supporting rationale, and the operational steps taken to implement outcomes. Clear, contemporaneous records distinguish robust signal management from activities that are scientifically sound but undocumented.

Signal lifecycle and embedded templates

A pragmatic lifecycle:

Detection → Validation → Prioritisation → Assessment → Recommendation → Action or Closure

Each stage below includes: - A practical checklist for minimum required records - A template (blank) for consistent documentation - A completed example demonstrating expected content and inspection-relevant features - Implementation notes on storage, traceability and governance

Notes on use: templates should be version controlled, stored with audit trails, and linked to the signal tracking system (see "Signal tracking systems" section). Templates may be adapted to local systems but must retain key fields shown.

Detection

Purpose: Record how an observation surfaced and why it merited entry to the signal management process.

Detection checklist (minimum required) - Unique Signal ID (system-generated) - Product(s) involved (INN and brand) - Detection date (first observation) - Detection source(s) (spontaneous reports, periodic reports, literature, studies, solicited reports, analytics) - Detection method and tool (disproportionality algorithm, clinical review, trend analysis) - Initial summary of observation - Initial reviewer and date - Immediate actions (e.g., expedited review, hold for monitoring)

Detection template (blank)

Signal ID:
Product(s) (INN/Brand):
Detection date:
Detected by (name/team):
Detection source(s):
Detection method/tool:
Initial summary:
Immediate risk level (low/moderate/high):
Initial action recommended:
Initial reviewer (name, role, signature/date):
Linked documents/attachments (filenames):

Detection template (completed example)

Signal ID: SIG-2026-013
Product(s): DrugX (INN: drugx)
Detection date: 2026-05-02
Detected by: Safety Surveillance Team (automated signal run)
Detection source(s): Spontaneous reports (VigiBase export), periodic signal run
Detection method/tool: Monthly disproportionality screening (EBGM > 3 and n ≥ 5)
Initial summary: Increase in reporting of 'hepatic enzyme elevation' term vs background in 2025–2026; disproportionate signal observed in two countries.
Immediate risk level: Moderate
Initial action recommended: Proceed to validation; request case-level review of first 10 reports; literature search.
Initial reviewer: A. Safety, Senior Signal Scientist (2026-05-04)
Linked documents/attachments: SIG-2026-013_Detection_Run_20260502.csv; SIG-2026-013_VigiBase_Export_20260502.pdf

Implementation notes - Ensure the Signal ID is generated by a tracking system that enforces uniqueness and links to all documents. - Capture the detection tool version and algorithm parameters (e.g., cut-offs) to allow reproducibility. - Retain the output files (e.g., statistical runs) as attachments; do not rely solely on narrative summaries.

Inspection relevance - Inspectors will want to see how the signal first emerged and that the initial decision to validate was contemporaneous and justified. Provide both the summary and underlying outputs.

Validation

Purpose: Determine whether the detected observation represents a potential signal that merits further assessment.

Validation checklist (minimum required) - Validation date and validator identity - Data sources reviewed (cases, literature, study reports) - Criteria used for validation (predefined decision tree or SOP reference) - Result (validated/not validated/suspend for monitoring) - Scientific rationale for result - Required next steps and timelines - Reference to any immediate regulatory notification (if applicable)

Validation template (blank)

Signal ID:
Validation date:
Validated by (name, role, signature/date):
Data sources reviewed:
Validation criteria/reference (SOP/version):
Validation outcome (validated / not validated / monitor):
Rationale for outcome:
Required next steps (if any) and due dates:
Escalation required? (yes/no) -> to whom:
Attachments (filenames):

Validation template (completed example)

Signal ID: SIG-2026-013
Validation date: 2026-05-10
Validated by: B. Clinical Safety Lead (2026-05-10)
Data sources reviewed: 12 spontaneous cases (detailed narratives), VigiBase disproportionality output, internal clinical trial safety database, PubMed search (2000–2026)
Validation criteria/reference: Signal Management SOP v3.1 (Section 4.2: validation decision tree)
Validation outcome: Validated
Rationale for outcome:
- Disproportionality signal persisted after de-duplication (EBGM 4.2, n=12).
- Multiple reports contain temporally plausible onset after drug initiation and aminotransferase elevations >3x ULN.
- No competing pharmacological explanation in 8 reports; alternate cause plausible in 4 reports.
- Literature search found 2 case reports from 2024 suggesting hepatotoxicity.
Required next steps:
- Full signal assessment to be initiated (lead: Clinical Safety), draft due 2026-06-10.
- Assign Action A1: case follow-up for two serious reports (lead: ICSRs team; due 2026-05-20).
Escalation required: Yes — escalation to Safety Management Committee (SMC) at next meeting (2026-05-17).
Attachments: SIG-2026-013_Case_Review_20260509.pdf; SIG-2026-013_PubMed_Search_20260509.pdf; SIG-2026-013_Run_Output_20260502.csv

Implementation notes - Validation must be traceable to SOP criteria. Where organisations use decision matrices, preserve the matrix snapshot with populated scores. - Log who performed de-duplication and how it was done.

Inspection relevance - Inspectors will examine the validation rationale and whether it followed written procedures. Lack of a documented rationale is a frequent finding.

Governance - Validation outcomes for significant signals should be recorded in governance logs (e.g., committee pre-reads) and linked to minutes.

Prioritisation

Purpose: Allocate resources and timelines; document rationale for the urgency and level of assessment.

Prioritisation checklist (minimum required) - Priority level assigned and justification (clinical impact, public health impact, frequency, severity) - Factors considered (vulnerable populations, concomitant medicines, seriousness) - Resource and timeline allocation - Escalation decisions and recipients - Assigned assessment lead and team

Prioritisation template (blank)

Signal ID:
Priority level (low / normal / high / urgent):
Date assigned:
Assigned by (name, role):
Factors considered (list):
Priority justification:
Assessment lead (name, role):
Assessment timeline (start / draft due / final due):
Escalation required? (yes/no) -> details:
Resource implications (analyst time, external experts):
Attachments:

Prioritisation template (completed example)

Signal ID: SIG-2026-013
Priority level: High
Date assigned: 2026-05-11
Assigned by: Safety Management Committee (minute reference SMC-2026-05-17)
Factors considered:
- Grade of event: hepatic enzyme elevation with potential for severe liver injury
- Evidence of temporal association in multiple reports
- Product widespread use in older adults
Priority justification:
- Potential for serious clinical harm; evidence sufficient to justify accelerated assessment.
Assessment lead: Clinical Safety Team (C. Assessor)
Assessment timeline:
- Start: 2026-05-11
- Draft assessment: 2026-06-10
- Final assessment and recommendations: 2026-06-24
Escalation required: Yes — SMC and Medical Governance Board to be informed after draft assessment.
Resource implications: Dedicated 0.5 FTE for 6 weeks; external hepatology consultant retained for case adjudication (if needed).
Attachments: SMC-Agenda-2026-05-17.pdf; SMC-Minutes-2026-05-17.pdf

Implementation notes - Use a prioritisation matrix with weighted criteria; retain the populated matrix as evidence of consistent decision-making. - Link priority decisions to action timelines in the action tracker.

Inspection relevance - Inspectors may assess whether prioritisation reflects risk and whether allocated timelines were met.

Governance - Prioritisation decisions for high/urgent signals should be explicitly recorded in committee minutes with attendees and decisions, and signed by the chair.

Assessment

Purpose: Produce a comprehensive, referenced assessment that synthesises all available evidence, documents uncertainties and provides reasoned recommendations.

Assessment checklist (minimum required) - Assessment report versioning (draft/final) - Assessment lead and author(s) - Signal background and history (including detection and validation) - Data and methodologies reviewed (case-level, aggregated analyses, literature, epidemiology) - Case narratives and clinical evaluation (including causality assessment) - Alternative explanations and data limitations - Quantitative analyses (where applicable) and methods - Conclusions and recommendation(s) - Proposed actions with owners and timelines - Attachments: case listings, statistical outputs, literature appendices, expert opinions - Sign-off(s) and governance record (committee review/approval)

Assessment report template (blank)

Signal ID:
Assessment report v.:
Title:
Assessment lead / author(s):
Date:
Executive summary (concise):
Background (product info, previous signals):
Detection and validation summary:
Evidence reviewed (list and dates):
Case-level evaluation (n, seriousness, key narratives, causality):
Epidemiology/statistics (methods, results):
Literature review summary:
Alternate explanations considered:
Uncertainties and data gaps:
Conclusions (balanced, evidence-based):
Recommendations (actions with owner and timeline):
Action tracker reference (IDs):
Governance review (committee, date, minutes ref):
Signatures (assessment lead, medical reviewer, QPPV):
Attachments (filenames):

Assessment report (completed example — abbreviated for illustration)

Signal ID: SIG-2026-013
Assessment report v.: 1.0 (Draft)
Title: Assessment of elevated hepatic enzymes (ALT/AST) with DrugX
Assessment lead / author(s): C. Assessor, Clinical Safety (2026-06-10)
Date: 2026-06-10

Executive summary:
A validated signal for hepatic enzyme elevation with DrugX was assessed using 18 spontaneous reports (12 initial + 6 identified on follow-up), clinical trial data, VigiBase disproportionality analyses and a focused literature review. Evidence suggests a probable association with a small number of cases progressing to liver injury; however, confounding factors (concomitant hepatotoxic drugs, underlying disease) are present in some reports. Recommendation: escalate to SMC for consideration of targeted label update and intensified monitoring; implement specific case follow-up and pharmacoepidemiology plan (see Actions A1–A4).

Background:
DrugX authorised in 2019 for Condition Y. Known hepatic adverse reactions: elevated transaminases reported in <1% in clinical trials with no serious liver injury signal pre-2024.

Detection and validation summary:
Detected 2026-05-02 via disproportionality (EBGM 4.2). Validated 2026-05-10 (see Validation Record).

Evidence reviewed:
- 18 spontaneous reports (12 serious, 6 non-serious)
- Internal trial safety database (pooled trials n=3,200)
- VigiBase aggregated output (de-duplicated)
- PubMed and Embase search (2000–2026)
- Expert hepatology opinion (consultant report 2026-05-28)

Case-level evaluation:
- Median onset 21 days (range 5–90)
- 10 reports with ALT/AST >3x ULN; 3 reports with ALT>10x ULN
- 2 reports with clinical jaundice; 1 requiring hospitalisation; no fatalities.
- Causality assessment (WHO-UMC): 6 probable, 7 possible, 5 unlikely/insufficient.

Epidemiology/statistics:
- Disproportionality maintained after de-duplication (EBGM 4.2, 95% CI 2.8–6.1).
- No consistent dose-response observed in registries or trials.

Literature review summary:
Two case reports in 2024 describe acute hepatocellular injury temporally associated with DrugX; no controlled studies.

Alternative explanations:
- Concomitant hepatotoxic medications in 6 reports.
- Underlying liver disease in 3 reports.

Uncertainties and data gaps:
- Under-reporting and incomplete narratives limit incidence estimation.
- Lack of denominators precludes robust risk quantification.
- No causality-confirming rechallenge data.

Conclusions:
Evidence suggests DrugX is associated with hepatic enzyme elevations in a minority of patients; the signal merits regulatory attention and further pharmacoepidemiology study.

Recommendations:
- Action A1: Targeted case follow-up for all serious cases (Owner: ICSRs; due 2026-06-01 — in progress)
- Action A2: SMC discussion and decision on PI change (Owner: C. Assessor; SMC meeting 2026-06-24)
- Action A3: Initiate pharmacoepidemiology study (Owner: Epidemiology; protocol draft due 2026-07-31)
- Action A4: Notify regulators per timelines if SMC recommends (Owner: Regulatory Affairs; to be confirmed)

Action tracker reference: See Action Tracker AT-2026-013
Governance review: SMC (agenda 2026-06-24; minutes to include references)
Signatures:
- Assessment lead: C. Assessor (2026-06-10)
- Medical reviewer: M. Med (2026-06-11)
- QPPV acknowledgement: Q. QPPV (2026-06-12)
Attachments:
- SIG-2026-013_Case_Table_v1.xlsx
- SIG-2026-013_Stat_Output_20260502.csv
- SIG-2026-013_PubMed_Appendix.pdf
- SIG-2026-013_Expert_Hepatology_Opinion_20260528.pdf

Implementation notes - Maintain draft and final versions with change logs and sign-offs. Use tracked changes or annotations in the assessment platform to capture discussion. - Where external expert input is obtained, retain the expert's CV, scope, and conflict-of-interest declaration.

Inspection relevance - Inspectors expect to see the evidence base for conclusions, demonstration of balanced assessment (supporting and contradictory evidence), and documented sign-off by appropriate scientific owners and the QPPV.

Governance - Include committee minutes documenting discussion, questions raised, and decisions. Attach or index the assessment in the governance minutes and include references to action tracker IDs.

Recommendation, Action Implementation and Action Tracking

Purpose: Implement recommended measures and provide auditable evidence that actions were assigned, tracked and completed.

Action tracker checklist (minimum required) - Unique Action ID - Signal ID and assessment reference - Action description - Owner and backup owner - Priority and statutory/regulatory deadlines - Due date and status (not started / in progress / completed / blocked) - Completion evidence (documents, submission IDs) - Date completed and closure note - Link to inspection evidence (if applicable)

Action tracker template (blank)

Action ID:
Signal ID:
Assessment ref/version:
Action description:
Action owner (name, role):
Backup owner:
Priority (low/normal/high/urgent):
Assigned date:
Due date:
Status:
Progress notes:
Completion evidence (filenames/links):
Completed date:
Closure comment:
Escalation required? (Y/N):

Action tracker (completed example)

Action ID: AT-2026-013-A1
Signal ID: SIG-2026-013
Assessment ref/version: Assessment v1.0 (2026-06-10)
Action description: Targeted case follow-up for 3 serious cases to obtain missing lab values and concomitant meds.
Action owner: ICSRs Team (lead: L. Caseworker)
Backup owner: K. Backup (ICSRs)
Priority: High
Assigned date: 2026-05-11
Due date: 2026-06-01
Status: Completed
Progress notes:
- 2026-05-15: Initial contact with reporter; requested hospital discharge summaries.
- 2026-05-22: Hospital records received for 2/3 cases.
- 2026-05-28: Follow-up received for 3rd case; lab results show ALT 12x ULN.
Completion evidence:
- SIG-2026-013_Case_001_Hospital_Record.pdf
- SIG-2026-013_Case_002_Hospital_Record.pdf
- SIG-2026-013_Case_003_Lab_Report.pdf
Completed date: 2026-05-28
Closure comment: Key missing data obtained and added to case narratives; evidence uploaded and linked to assessment.
Escalation required?: No

Implementation notes - The action tracker must be current and linked to the signal tracking system. Use status change notifications to trigger governance reviews. - Embed links (or unique file IDs) to completion evidence rather than storing attachments only in email chains.

Inspection relevance - Inspectors will verify that actions listed in assessments were assigned and implemented; they will often request the action tracker and sample completion evidence.

Governance - The QPPV or delegated signatory should periodically review open high-priority actions. Governance reviews should include overdue actions and mitigation plans.

Escalation Log

Purpose: Provide a clear chronological record of when and why a signal or related action was escalated to higher governance or regulatory parties, and the outcomes of those escalations.

Escalation log checklist (minimum required) - Escalation ID (or link to Signal ID) - Date and time of escalation - Reason for escalation - Sender (name, role) - Recipient(s) (names, roles) - Mode (email/meeting/phone/regulatory report) - Decisions reached and agreed actions - Follow-up required and timelines - Attachments (emails, minutes, regulatory correspondence)

Escalation log template (blank)

Escalation ID:
Signal ID:
Date/time:
Escalated by (name, role):
Escalation reason:
Escalation recipients (names, roles):
Mode (email/meeting/phone):
Decisions reached:
Follow-up actions and owners:
Attachments (filenames):
Escalation closed date:

Escalation log (completed example)

Escalation ID: ESC-2026-013-01
Signal ID: SIG-2026-013
Date/time: 2026-05-10 09:30
Escalated by: B. Clinical Safety Lead
Escalation reason: Validation outcome positive; potential for serious liver injury in post-marketing cases.
Escalation recipients: SMC Chair (D. Safety), Head of Medical Affairs (E. MedAffairs), QPPV (Q. QPPV)
Mode: Email with request for SMC agenda inclusion; teleconference scheduled.
Decisions reached:
- SMC to review full assessment on 2026-06-24.
- Interim actions: ICSRs to prioritise case follow-up; Regulatory Affairs to prepare potential expedited notification template pending SMC decision.
Follow-up actions and owners:
- Case follow-up (ICSRs; due 2026-06-01)
- Prepare SMC pre-read (Assessment draft; C. Assessor; due 2026-06-10)
Attachments:
- ESC-2026-013_Email_20260510.pdf
- SMC_Invite_20260624.pdf
Escalation closed date: 2026-06-24 (post-SMC minutes SMC-2026-06-24, see minutes)

Implementation notes - Escalation logs should be part of the signal record and referenced in assessment documents and governance minutes. - Timestamped evidence (emails/meeting invites) is important; preserve redacted versions if necessary for confidentiality during inspections.

Inspection relevance - Inspectors will look for timeliness of escalation and confirmation that recipients were appropriate given the risk.

Governance - Escalation criteria should be defined in SOPs. Maintain evidence that the criteria were applied and that decisions followed governance pathways.

Closure and Archiving

Purpose: Demonstrate why a signal was closed and ensure closure is documented, including any ongoing monitoring responsibilities.

Closure checklist (minimum required) - Closure date and person authorising closure - Reason for closure (e.g., insufficient evidence, action completed) - Evidence reviewed prior to closure - Whether monitoring will continue and by whom - Record of where closure is documented (signal register, periodic report) - Archive location and retention period

Closure template (blank)

Signal ID:
Closure date:
Closed by (name, role, signature/date):
Closure rationale:
Evidence reviewed for closure:
Ongoing monitoring required? (yes/no) -> details:
Archive location (file path/system ID):
Retention period (per PV SOP):
Notes:

Closure template (completed example)

Signal ID: SIG-2026-013
Closure date: 2026-08-01
Closed by: Q. QPPV (2026-08-01)
Closure rationale:
- Final assessment (v2.0) concluded risk manageable with targeted label updates and a pharmacoepidemiology study initiated; immediate regulatory action completed (PI updated — see submission ID).
- Ongoing monitoring assigned to Routine Signal Watchlist (monthly surveillance) due to residual uncertainty.
Evidence reviewed for closure:
- Assessment v2.0
- Regulatory submission evidence (RS-2026-07890)
- Action tracker closed actions A1–A4
Ongoing monitoring required: Yes — monthly disproportionality runs for 12 months (owner: Signal Surveillance)
Archive location: PV SharePoint/SIG-2026-013 (Retention: 10 years)
Notes: Closure recorded in global signal register and included in next PSUR.

Implementation notes - Archive the full evidence package (see inspection evidence pack) with index and access controls. - Document retention periods per local regulations and internal SOPs.

Inspection relevance - Inspectors may request closure rationale, evidence that actions were implemented, and proof that monitoring continues where required.

Inspection Evidence Pack (embedded within lifecycle)

Purpose: Provide a pre-assembled, indexed package inspectors commonly request, containing the minimal set of documents needed to reconstruct the signal lifecycle and demonstrate governance. Maintain a ready-to-deploy version for high-priority signals.

Inspection evidence pack checklist (minimum content) 1. Signal index document (this provides a map of all files and where they are stored) 2. Detection records and raw outputs (statistical runs, export files) 3. Validation records (validation form, rationale) 4. Prioritisation worksheet and committee documentation 5. Assessment reports (drafts and final with versions) 6. Case-level data (case narratives, follow-ups) with de-identification/redaction as required 7. Literature review appendices 8. Statistical and epidemiological outputs (methodology and results) 9. Action tracker export and completion evidence 10. Escalation log and governance minutes (committee agendas, minutes, decision logs) 11. Regulatory correspondence (notifications and submission confirmations) 12. System records: audit trail extracts, access logs for signal record, change control evidence 13. QPPV attestations and sign-offs (as applicable) 14. SOPs referenced (with versions) 15. Expert opinions (CV, scope, conflict of interest statements) 16. Archive/retention confirmation

Inspection evidence pack template (blank index)

Inspection Evidence Pack Index — Signal ID: [SIG-XXXX-XXX]
Prepared by: [name, role]    Date prepared: [YYYY-MM-DD]

A. Index and summary
1. Signal index (this file)

B. Detection
2. Detection_run_[date].csv
3. Detection_summary_form.pdf

C. Validation
4. Validation_form.pdf
5. Validation_attachments.zip

D. Prioritisation & Governance
6. Prioritisation_matrix.xlsx
7. SMC_Agenda_[date].pdf
8. SMC_Minutes_[date].pdf

E. Assessment
9. Assessment_v1_Draft.pdf
10. Assessment_v2_Final.pdf
11. Assessment_attachments (case table, literature, stats)

F. Actions & Escalations
12. Action_Tracker_Export.xlsx
13. Escalation_Log.pdf

G. Regulatory
14. Regulatory_Notification_Docs.pdf
15. Submission_confirmation.pdf

H. System Records
16. AuditTrail_SignalRecord.pdf
17. AccessLog_Report.pdf

I. SOPs & Supporting
18. SOP_SignalManagement_vX.pdf
19. SOP_DocumentRetention_vY.pdf
20. ExpertOpinion_Conflicts.pdf

J. Archive & Retention
21. Archive_confirmation.pdf

Inspection evidence pack (completed example index — partial)

Inspection Evidence Pack Index — Signal ID: SIG-2026-013
Prepared by: L. EvidenceCustodian (Signal Surveillance)    Date prepared: 2026-07-01

A. Index and summary
1. SIG-2026-013_Evidence_Index_20260701.pdf

B. Detection
2. SIG-2026-013_Detection_Run_20260502.csv
3. SIG-2026-013_Detection_Summary_20260504.pdf

C. Validation
4. SIG-2026-013_Validation_Form_20260510.pdf
5. SIG-2026-013_Validation_Attachments.zip (VigiBase export, de-duplication log)

D. Prioritisation & Governance
6. SIG-2026-013_Prioritisation_Matrix_20260511.xlsx
7. SMC_Agenda_20260624.pdf
8. SMC_Minutes_20260624.pdf (contains decision to update PI)

E. Assessment
9. SIG-2026-013_Assessment_v1_20260610_Draft.pdf
10. SIG-2026-013_Assessment_v2_20260630_Final.pdf
11. SIG-2026-013_Assessment_Attachments.zip (case table v2, PubMed appendix, hepatology opinion)

F. Actions & Escalations
12. SIG-2026-013_Action_Tracker_Export_20260701.xlsx
13. SIG-2026-013_Escalation_Log_20260701.pdf (ESC-2026-013-01 to ESC-2026-013-03)

G. Regulatory
14. SIG-2026-013_Regulatory_Notification_RS-2026-07890.pdf
15. SIG-2026-013_PI_Change_Submission_Confirmation.pdf

H. System Records
16. SIG-2026-013_AuditTrail_SignalRecord_20260701.pdf
17. SIG-2026-013_AccessLog_Report_20260701.pdf

I. SOPs & Supporting
18. SOP_SignalManagement_v3.1.pdf
19. SOP_DocumentRetention_v2.0.pdf
20. Hepatology_Expert_CV_COI_20260528.pdf

J. Archive & Retention
21. SIG-2026-013_Archive_Confirmation_20260801.pdf

Implementation notes - Maintain an evidence pack template and populate it incrementally during the signal lifecycle rather than assembling ad hoc at inspection time. - For inspection requests, provide redacted versions where needed (maintain originals with restricted access). - Include a short cover letter (index) explaining reviewer access instructions and relevant file paths or system IDs.

Inspection relevance - An organised evidence pack demonstrates control, traceability and preparedness; disorganised or incomplete packs frequently trigger inspection findings.

Governance - Production of the evidence pack is typically the responsibility of the signal owner or a designated evidence custodian; governance should assign responsibility and timelines for producing the pack when requested.

Signal Tracking Systems — practical implementation

Key system capabilities required for inspection-grade traceability: - Unique identifiers for signals, actions, escalations and documents - Role-based access controls and electronic signatures - Full audit trails capturing who changed what and when - Document linking (assessment ↔ action tracker ↔ case files ↔ governance minutes) - Export capability (PDF/ZIP) to assemble evidence packs - Version control for documents and templates

Implementation details - Use standardized file naming conventions: [SignalID][DocumentType][YYYYMMDD][_vX].ext (e.g., SIG-2026-013_Assessment_v2_20260630.pdf) - Keep attachments in a controlled repository with immutable backups. - Capture system export of audit trails when assembling inspection packs.

Regulatory context - GVP Module I requires pharmacovigilance systems to operate within a quality system; traceability and data integrity are components. GVP Module IX references the need for documented decision-making in signal management. Inspection guidance (GVP Module III) expects demonstrable traceability via system records.

Inspection relevance - Inspectors commonly request system audit trails to verify that records presented as evidence were created and modified as claimed. Provide extracts of audit trails relevant to signal records.

Governance and Roles (practical detail)

Core governance elements and responsibilities - Signal owner: accountable for coordination of assessment and evidence collation. - Assessment lead: responsible for writing the assessment and recommending actions. - ICSRs team: responsible for case follow-up and correction of narratives. - Epidemiology/statistics: provide quantitative analyses and methods documentation. - Regulatory affairs: prepare notifications/submissions and track regulatory timelines. - QPPV: ultimate responsibility for PV system; must be able to explain tracking, escalation and evidence. - Evidence custodian: prepares inspection evidence packs upon request.

Practical governance steps - Record committee agendas and minutes including attendance, declarations of interest, and decisions. Minutes must reference the assessment version and action tracker IDs. - Ensure sign-offs include name, role, date, and signature (electronic signature acceptable if controlled). - Retain conflict of interest declarations for external experts and committee members involved in decisions.

Inspection relevance - Inspectors review whether the QPPV had visibility and whether governance records demonstrate oversight and timely decision-making.

Practical tips for inspection readiness (operationalised)

• Maintain a live action tracker export for each active high-priority signal.
• Populate the inspection evidence pack incrementally; at any point be able to export a zip containing the index and referenced files.
• Ensure that committee minutes explicitly reference signal IDs and action tracker IDs — auditability depends on cross-referencing.
• Keep a short audit summary document for each signal (one-page timeline) included in the evidence pack to aid inspectors’ navigation.
• Ensure the audit trail for the signal record is extracted and included in the evidence pack to show timestamps and user activity.

Recording uncertainty and quality of evidence (operational)

• Explicitly document data limitations in the assessment (missing data, case quality), and note how these limitations influenced conclusions and the choice of actions.
• If actions are conditional (e.g., "proceed to regulatory notification if pharmacoepidemiology confirms increased risk"), document clear triggers and responsibilities; include these in the action tracker.

Inspection relevance - Inspectors expect balanced assessments that acknowledge uncertainty. Absence of documented limitations can suggest bias or weak scientific rigour.

Integration with other PV processes

• Cross-reference signal actions in PSURs/PBRERs and RMPs where applicable; maintain mapping between signal assessments and periodic reports.
• Document regulatory interactions and link submission IDs to signal records.

Inspection relevance - Inspectors may verify that important signals were reflected appropriately in other regulatory deliverables.

Appendices: Blank Templates (copyable)

• Detection template (blank)
• Validation template (blank)
• Prioritisation template (blank)
• Assessment report template (blank)
• Action tracker template (blank)
• Escalation log template (blank)
• Closure template (blank)
• Inspection evidence pack index (blank)

(Blank templates are provided earlier in each lifecycle section for direct copy/paste and adaptation.)

Key takeaways

• Embed standardised checklists and templates at each lifecycle stage to ensure comprehensive and consistent documentation.
• Link templates and records via unique identifiers and store them in validated systems with audit trails.
• Prepare an inspection evidence pack incrementally; include the index and audit trail extracts.
• Ensure governance records (committee agendas, minutes, sign-offs) are consistently cross-referenced with signal and action identifiers.
• Document uncertainties and alternate explanations explicitly; include expert inputs and conflict-of-interest declarations.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module IX – Signal Management.
2. EMA Good Pharmacovigilance Practices (GVP) Module I – Pharmacovigilance Systems and Their Quality Systems.
3. EMA Good Pharmacovigilance Practices (GVP) Module III – Pharmacovigilance Inspections.
4. Commission Implementing Regulation (EU) No 520/2012.
5. Regulation (EC) No 726/2004.
6. Directive 2001/83/EC.
7. CIOMS VIII Practical Aspects of Signal Detection in Pharmacovigilance.
8. ICH E2E Pharmacovigilance Planning.