Skip Headers
Oracle® Argus Interchange User's Guide
Release 8.1

E74380-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Validating ICSR Reports

In order to successfully transmit any E2B Report, it must validated for its mandatory components before transmitting the report.

Why perform an ICSR check?

During case data entry and prior to E2B file generation, the user may want to verify that sufficient data and the quality of data collected will generate a valid E2B file.

To do so, a Data Validation check is required for E2B profiles and to provide a listing of data elements that do not satisfy the criteria required to generate an E2B report.

On performing an ICSR check, the system performs a validation and lists the following types of validation errors for the data elements that are failing the validations in 'E2B Report data check errors and warnings':

  1. Mandatory

  2. Mandatory Optional

  3. Together DTD Element Validation

  4. Other Validation

  5. Date Validation

  6. E2B Generation Validation (Fatal Validations)

You can run an ICSR check by clicking the ICSR icon from the Quick Launch menu shown below.

Surrounding text describes newtoolbar.jpg.

Note:

The ICSR check icon is visible on the Quick Launch Toolbar ONLY if a case is open and active on the user session.

Running an ICSR check validates if the E2B report has all these mandatory elements present that is required for its successful processing.

The following illustration shows a sample ICSR check report that is generated in PDF format:

Surrounding text describes newrep.jpg.

As can be seen in the PDF, the sample report displays the case form fields where the validation error has occurred.

Apart from the case form location where the error occurred, the report lists the type of error, data elements, DTD elements, the actual message/cause of the error, and the profiles which were tested for each validation type.

The validation checks are profile-dependent but every ICSR check report tests for Mandatory Elements check and Mandatory Optional Elements check.

Report Generation Validations

The system performs the following validations at the time of report generations and displays validation error if there are failures:

  1. Missing Mandatory Elements

  2. Missing Mandatory Optional Elements

  3. Length Validation for character data

  4. M2 Code validation

  5. Report File Size validation (for HL7 Reports only)

The system displays an error message in the following scenarios:

  1. While generating draft E2B or eVAERS or eMDR report using Draft tool button, if the default Reporting Destination is not specified for E2B or eVAERS or eMDR in Common Profile Switches.

  2. While generating draft/final E2B or eVAERS or eMDR report for the Reporting Destination which is not configured with valid Message Profile as E2B or eVAERS or eMDR respectively.

  3. While generating E2B(R3) or eVAERS or eMDR report, if the size of inline attachments or overall size of xml file exceeds the maximum file size limit specified in Common Profile Switches.

Validation Rules

E2B Generation validation logic has been enhanced such that rather than executing the validations directly on the case/LM data the validation rules is executed on the generated ICSR report data.

The validation rules that are applicable to individual element is governed by configuration in the Conformance Rules tab for that element for the respective profile.

Validation Rule the elements is categorized amongst the following categories: