Pharmacovigilance is essential to monitor and maintain the safety of medicines throughout their lifecycle. Even after regulatory approval, new or rare adverse effects may emerge when drugs are used in more diverse populations. Monitoring, evaluating, and managing these risks is critical to patient safety.
One of the core tools in pharmacovigilance is the Individual Case Safety Report (ICSR). ICSRs capture detailed information about suspected adverse events experienced by individual patients following the use of medicinal products. When collected and analysed systematically, these reports help identify potential safety risks early and support timely regulatory action.
As medicines are increasingly used across borders, global ICSR reporting has become vital. Sharing individual case data internationally allows regulatory authorities and pharmaceutical companies to detect safety signals earlier.
This article provides a comprehensive overview of ICSRs, including their components, types, collection and processing, standardisation, regulatory requirements, and technology use.
What are Individual Case Safety Reports (ICSRs)?
An Individual Case Safety Report (ICSR) is a structured record that captures information about a suspected adverse event in an individual patient. ICSRs include patient details, the suspected medicinal product, and the adverse event or reaction, along with relevant clinical context.
In practice, an ICSR allows safety teams to assess, code, review, and report a suspected case consistently.
ICSRs do not necessarily establish causality but help identify trends when aggregated. Sources may include healthcare professionals, patients, clinical study sponsors, or published literature. Regulators such as the European Medicines Agency (EMA) and the U.S. Food and Drug Administration (FDA) require standardised ICSRs to monitor safety consistently across systems and sources.
Key Components of an ICSR
Most organisations capture a consistent core set of fields so that cases can be assessed and compared across sources. For a report to be considered, a valid ICSR for processing, they should typically meet the minimum four elements. These include:
Identifiable patient
Adequate information to distinguish the individual, such as age range or gender, without revealing personal identifiers.
Identifiable reporter
The source of the report, such as a healthcare professional, patient or caregiver, allowing follow-up if needed.
Suspected medicinal product
The drug, vaccine, or biologic thought to be related to the event.
Adverse event or reaction
The clinical event experienced by the patient. Supporting clinical details, such as event onset, outcome, medical history, and concomitant medications, enhance utility. Regulatory guidelines emphasise accurate and complete reporting to enable proper evaluation.
Types of ICSRs in Pharmacovigilance
Early classification helps teams apply the right workflow, including the appropriate review steps and reporting timelines. ICSRs are classified based on source, seriousness, and context. Some of the main types include:
- Spontaneous ICSRs: Voluntary reports from healthcare professionals or patients.
- Solicited ICSRs: Reports from structured programmes like registries or support services.
- Clinical trial ICSRs: Captured during clinical studies, including SUSARs (Suspected Unexpected Serious Adverse Reactions).
- Literature ICSRs: From published scientific reports.
- Expedited vs non‑expedited: Accelerated reporting applies to certain ICSR classifications (e.g. serious and unexpected cases in clinical trials), while non‑serious cases follow longer timelines.
This classification ensures that each ICSR is processed and reported appropriately in line with regulatory requirements.
ICSR Collection, Processing, and Reporting Overview
Once a report is received, case processing typically follows a standard sequence designed to support completeness, consistency, and timely submission. Managing an ICSR follows a structured process, including:
- Case intake
Reports arrive through multiple channels and are screened for validity. - Triage and assessment
Cases are evaluated for seriousness, expectedness, and reportability. - Data entry and coding
Clinical events are coded using MedDRA, and products are coded using standard dictionaries (for example, WHODrug, depending on the organisation and system). - Narrative and review
A clear, chronological narrative is prepared and reviewed for quality. - Medical review
Medical assessment, including causality, is performed by a medic. - Reporting and follow‑up
Applicable ICSRs are submitted to the appropriate authorities, with follow-up if required.
This structured approach ensures accurate, timely, and compliant reporting across global pharmacovigilance systems.
Quality and data integrity are typically supported through defined QC checks, role-based review, audit trails in validated safety systems, and procedures to detect and manage duplicates across sources and markets. Follow-up information may be submitted as an update to the original case to improve completeness and clinical context.
ICSR Standardisation and Electronic Reporting Formats
Since ICSRs are exchanged across companies and regulators, harmonised formats help reduce ambiguity and rework.
Standardisation is essential for effective global reporting. The International Council for Harmonisation (ICH) E2B(R3) guideline defines the format and data elements for electronic ICSR submissions. Many regulatory systems rely on the ISO/HL7 27953-2 (the ICSR electronic reporting standard aligned to ICH E2B(R3)) for consistent structure and messaging. In the European Union, an ICSR implementation guide jointly developed by the EMA and Heads of Medicines Agencies (HMA) specifies technical requirements, business rules, and quality principles for electronic submission. This format improves data quality, supports accurate exchange, and strengthens analysis across systems.
Regulatory Requirements for ICSR Reporting
Regulatory expectations focus on submitting the right cases to the right place within the required timelines, with sufficient clinical detail. Regulatory authorities set clear expectations for ICSR reporting.
[KC1] Timelines and reportability rules vary by jurisdiction and context (such as post-authorisation versus clinical trials). For example, in the EU, post-authorisation expedited reporting is commonly associated with 15-day submission timelines for serious adverse reaction reports and 90-day timelines for non-serious cases, while clinical trial expedited reporting is limited to unexpected serious adverse reaction reports within 7 or 15 days (7 for fatal or life-threatening cases), with expected serious adverse reactions only being reported in the annual development safety update report.
The EMA requires use of international standards such as ICH E2B(R3) and ISO ICSR formats for reporting to systems like EudraVigilance, ensuring consistency across the European Economic Area.
Likewise, the FDA references the ISO/HL7 ICSR standard as part of its technical specifications for electronic submission of post‑marketing ICSRs, with options for E2B(R3) and transitional use of E2B(R2) under specific circumstances.
In practice, electronic submissions are routed to central or national repositories depending on region and product context. Common pathways include:
- VigiBase (WHO): Aggregates national reports for international analysis.
- EudraVigilance (EU): Central repository for EU adverse reaction reports, requiring standardised formats.
- FAERS (USA): FDA system for adverse event reporting.
Other regions maintain national systems, often aligned with global standards, enabling cross border safety signal detection.
Technology and Automation in ICSR Management
As case volumes grow, teams often use technology to support faster intake, more consistent processing, and better oversight. Technology aids ICSR handling:
- Electronic case intake and data entry reduces manual workload.
- AI and Natural Language Processing (NLP) help identify relevant data from unstructured text.
- Automated workflows and analytics support compliance tracking and safety signal detection.
Together, these tools can improve quality, speed, and consistency.
Conclusion
Individual Case Safety Reports (ICSRs) are fundamental to pharmacovigilance, supporting global safety monitoring, regulatory compliance, and patient protection. Standardisation, electronic reporting, and technology can improve efficiency and data quality, while adherence to best practices supports reliable signal detection and risk management. Through quality reporting and effective management, ICSRs support robust safety monitoring, risk mitigation, and protection of public health worldwide.
About QVigilance
We are a specialised pharmacovigilance service provider, offering comprehensive pharmacovigilance services to sponsors of clinical trials and manufacturers of authorised medicinal products. QVigilance is adept in supporting customers establishing a compliant pharmacovigilance system to support our customers’ products and safeguard their patients.
FAQs
What is an ICSR in pharmacovigilance?
An Individual Case Safety Report (ICSR) records a suspected adverse reaction in an individual patient to support ongoing safety monitoring.
What are the four elements of a valid ICSR?
An identifiable patient, an identifiable reporter, a suspected medicinal product, and a suspected adverse reaction.
What is the difference in intent between ICSRs and periodic reports, in terms of safety oversight?
ICSRs result in immediate action and awareness of potential safety issues, whereas periodic reports offer a comprehensive and cumulative overview of product safety.
What kind of data does ICSR collect?
Patient demographics, suspected product information, adverse event description, reporter details, and relevant clinical context.