E2B Tag Values Not Decoding Appropriately When FIELD_CODE_LIST Table Is Truncated (Doc ID 601336.1)

Last updated on MARCH 01, 2016

Applies to:

Adverse Event Reporting System - Version 4.6.1 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

In the generated E2B XML file, the following tags values are saved as text:
reporttype, serious, all seriousness criteria tags (seriousnesslifethreatening,
seriousnessdisabling, seriousnesscongenitalanomali, seriousnessother),
patientsex, medicallyconfirmed, actiondrug, patientagegroup.

EXPECTED BEHAVIOR
It is expected that these tag values to be saved as code numbers.

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Generate an E2B report;
2. Open the generated E2B XML file;
3. Verify the contents of reporttype, serious, all seriousness criteria tags
    (seriousnesslifethreatening, seriousnessdisabling, seriousnesscongenitalanomali,
    seriousnessother), patientsex, medicallyconfirmed, actiondrug, and patientagegroup tags.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms