E2B Extensions (Applicable for R2 only)
You can use the existing reporting destination configuration to choose an extended E2B profile. The system uses the agency and company identifier to identify the profile to use and sends the information in the following XML elements:
<messagesenderidentifier>Company X</messagesenderidentifier>
<messagereceiveridentifier>Agency Y</messagereceiveridentifier>
The Oracle Argus Interchange utility also supports the defined extended E2B elements as follows:
- A switch in the Interchange utility identifies a profile as either a standard
profile or an extended E2B profile but only for the Receive tab. The additional
fields are formatted as follows:
<XXX>_EXTENSION []
where:
XXX
is the tag name followed by_EXTENSION
to indicate that this is an extended E2B tag elementWhen using this switch:
- Do not enter any blank spaces or underscore characters ( _ ) in
the
XXX
naming convention. - In the extended E2B tags, the element number in the brackets ( [
] ) is always empty. For example,
Patient Ethnicity, Event Hospitalized Start Date / Stop Date
. - This switch is enabled only for profiles copied from the Factory profiles (default unchecked). This flag is disabled for all factory profiles.
- During configuration, GPS updates the DTD profile with this information before it adds any additional E2B elements.
- The system maps extended E2B fields are mapped to existing Oracle Argus Safety fields or to user-defined fields, as appropriate. For example, the system
maps the following extended E2B fields to the following Oracle Argus Safety tables.
E2B + Field Argus Case Form UI Field Name Argus Field Label Description patientethnicity_extension
PATIENT | Patient Ethnicity
Patient Ethnicity
reactionintensity_extension
EVENTS | Event Intensity
Event Intensity
reactionhospstartdateformat_extension
Argus Date entry format YYYYMMDD or YYYYMM or YYYY
Hospitalized Start Date Format
reactionhospstartdate_extension
EVENTS | Hospitalized Start Date
Hospitalized Start Date
reactionhospstopdateformat_extension
Argus Date entry format YYYYMMDD or YYYYMM or YYYY
Hospitalized Stop Date Format
reactionhospstopdate_extension
EVENTS | Hospitalized Stop Date
Hospitalized Stop Date
- The system sends an acknowledgment if the message import is successful and a rejection if the message import is not successful.
- Do not enter any blank spaces or underscore characters ( _ ) in
the
You can view the extended elements for the following:
- E2B Viewer
- No updates to the CIOMS / MedWatch Reports
- The Decoded View / SGML View displays the additional elements added as a part of the Extended E2B
- E2B Difference Report
- When imported, the system displays the additional fields in the current difference report viewer.
- E2B Selective Intake for Initial and Follow up E2B Reports
- You can selectively import the additional fields the system adds to the Extended E2B in the Oracle Argus Safety case.
- The PDF reports display the additional fields added to the Extended E2B.
- The E2B Warnings/Errors display the warnings/errors if warnings or errors defined for the fields added to the Extended E2B.
Parent topic: Configure Oracle Argus Interchange