Mapping CIOMS I to ICH E2B: An Overview
The International Council for Harmonisation (ICH) E2B guideline is the cornerstone for the electronic transmission of individual case safety reports (ICSRs). It evolved from the earlier Council for International Organizations of Medical Sciences* (CIOMS) I format, which was the first structured approach for pharmacovigilance case reporting. Understanding how CIOMS I maps to ICH E2B is essential for regulators, pharmaceutical companies, and software vendors who need to ensure seamless data exchange across global safety systems.
Why Mapping Matters
- Regulatory compliance: Many regions still reference CIOMS I in legacy systems, while new submissions must conform to ICH E2B (including the current E2B(R3) version).
- Data quality: Mapping clarifies which fields are mandatory, optional, or conditional, reducing the risk of missing or inconsistent information.
- Operational efficiency: Automated conversion scripts rely on a welldefined mapping table to transform historic CIOMS I records into the modern E2B structure.
Key Structural Differences
CIOMS I is a flat, tabular document, typically exchanged as an XML or PDF file with one record per line. ICH E2B, on the other hand, introduces a hierarchical, modular XML schema that groups related data (patient, drug, outcome, etc.) into distinct blocks. This shift allows richer context and better support for multiple suspect drugs, dosages, and timelines.
Highlevel comparison
| Aspect | CIOMS I | ICH E2B (R3) |
|---|---|---|
| Document format | Flat XML/ASCII, one case per file | Hierarchical XML, can contain one or many cases per file |
| Data model | Singlelevel list of elements | Nested blocks (e.g., patient, reaction, drug, narrative) |
| Versioning | None, version indicated in file name | Explicit <caseHeader> with version and report type |
| Handling multiple suspect drugs | Repeated drug rows, limited context | <drug> block repeated with full attributes |
| Electronic transmission | Fax/Email, manual parsing | Secure XMLbased messaging (e.g., ICSR stream) |
FieldbyField Mapping
The table below presents the most common CIOMS I elements and their equivalents in ICH E2B(R3). Mandatory (M), optional (O), and conditional (C) status is indicated according to the ICH specification.
| CIOMS I Element | ICH E2B Block / Element | Requirement | Notes |
|---|---|---|---|
| Report Number | <caseReportID> (within <caseHeader>) | M | Unique identifier used for tracking. |
| Report Date | <reportDate> | M | ISO 8601 format (YYYY-MM-DD). |
| Country | <primarySourceCountry> | M | Uses ISO31661 alpha2 code. |
| Patient Initials / ID | <patientInitials> or <patientID> | O | Protected health information must be anonymised. |
| Age | <patientAge> (age + unit) | M | Unit may be YEARS, MONTHS, DAYS. |
| Sex | <patientGender> | M | Values: M, F, UN (unknown). |
| Weight | <patientWeight> | O | Unit kg; required for paediatric cases. |
| Drug Name | <drug> <drugName> | M | Prefer International Nonproprietary Name (INN). |
| Drug Dose | <drug> <drugDose> <doseUnit> | C | Required when dose is known. |
| Start/Stop Dates | <drugStartDate> / <drugStopDate> | O | Both dates use ISO format; stop date may be ongoing. |
| Indication | <indication> | O | Use MedDRA Preferred Term when possible. |
| Adverse Event Term | <reaction> <reactionMedDRA PT> | M | MedDRA coding is mandatory for new submissions. |
| Outcome | <reactionOutcome> | O | Values: RECOVERED, RECOVERING, NOT RECOVERED, DECEASED, UNKNOWN. |
| Seriousness Criteria | <serious> block (multiple flags) | M | Includes death, lifethreatening, hospitalization, etc. |
| Reporters Name | <primarySourceName> | O | May be omitted for anonymous reports. |
| Reporters Qualification | <primarySourceQualification> | O | Uses ICH-defined codes (e.g., HCP, consumer). |
| Report Narrative | <narrative> | C | Required when the case lacks sufficient structured data. |
Practical Mapping Steps
- Extract CIOMS I data. Use a parser that can read the flat XML or the delimited text version. Preserve field order and handle repeatable drug rows.
- Normalize values. Convert country codes, gender symbols, and date formats to the ICHapproved enumerations.
- Map to E2B blocks. For each CIOMS row create a
<caseReport>element. Populate<caseHeader>,<patient>,<drug>, and<reaction>blocks according to the table above. - Validate against the XSD. ICH E2B(R3) provides an XML Schema Definition. Run automated validation to catch missing mandatory elements or invalid codes.
- Handle multiple suspect drugs. CIOMS I often lists drugs sequentially; in E2B each drug becomes a separate
<drug>subelement linked to the same case. - Generate the final XML. Serialize the constructed object model, ensuring UTF8 encoding and proper namespace declarations (
xmlns="http://icsr.ictrp.org/2006"for R3).
Common Pitfalls and Tips
- Missing MedDRA coding. CIOMS I sometimes contains freetext event descriptions. Implement a fallback lookup to MedDRA PTs or flag the case for manual review.
- Duplicate report IDs. Legacy systems may reuse numbers; append a source identifier to guarantee uniqueness in the E2B environment.
- Date ambiguities. A CIOMS DD/MM/YY format can be misinterpreted. Always parse with locale awareness and convert to ISO 8601.
- Conditional fields. The Outcome element is optional in E2B but becomes mandatory if the case is marked as serious and the result is death.
- Version control. Keep a log of the CIOMS version used for each batch; future reprocessing may require different mapping rules.
Resources for Further Reading
- ICH E2B(R3) Guideline ich.org
- CIOMS Working Group Report cioms.ch
- MedDRA Dictionary meddra.org
- FDA Guidance on Electronic Submissions fda.gov
Conclusion
Mapping CIOMS I to ICH E2B is a critical bridge between historic pharmacovigilance data and contemporary electronic reporting standards. By understanding the structural shifts, applying a systematic fieldbyfield conversion, and complying with validation rules, organisations can maintain data integrity, satisfy regulatory expectations, and streamline safety signal detection across the global ecosystem.
HPLC Method Development And Validation As Per ICH Guidelines and Reference File Download L...
ICH Guideline Q14 On Analytical Procedure Development and Reference File Download Link
Satellite Remote Sensing Carbon Stock Mapping dan Link Download File Referensi