SAFETYREPORT


E2B Import

 

A record in AER table is created for this entity.

If authority related information is found, a record in AER_INFM_AUTH is also created.  Following fields are set:

  1. STATUS_AUTH_FLAG = 0

  2. RECORD_OWNER_UNIT = As selected in UI (in E2B Import).

 

If  'reporttype' is available, a record in AER_SOURCE is created. PRIMARY_SOURCE_FLAG is set to 1(Yes)

If the relevant data is available, the records will be created in E2B_REPORT_DUPLICATE table.

If relevant data is available, a record in AER_AE_CHAR is created at AER Level.

 

E2B Export

For this entity the information will be taken from the following tables:

 

AER

AER_SOURCE

AER_AE_CHAR

AER_INFM_AUTH and

E2B_REPORT_DUPLICATE

 

If the PRIMARY_SOURCE_FLAG is equal to 1 in AER_SOURCE record then this record will be considered in determining reporttype.

 

AER Characteristics will be taken from AER level.

 

All the authority records from AER_INFM_AUTH table will be considered for export only when the exported authority (from export UI) has a match in the AER informed authority records.

 

E2B Gateway specific

The information pertaining to the first authority record corresponding to the Authority in the E2B_MESSAGE_QUEUE.RECEIVER_INSTITUTION is considered for export.

 

List of AER_INFM_AUTH fields created/updated when an authority record is inserted/updated

 

 

REPORTING_STATUS, DATE_INFORMED and DATE_INFORMED_PRECISION will not be populated/updated for periodic submissions.

 

ARISgE2B Gateway System create/update Authority record based on values in Transmission ack code and Report acknowledgement code.

 

System create/update AI fields based on the option shown below which is available at Unit level.

 

Update date informed based on

  1. Acknowledgement Received date

  2. MDN Received date

 

When Acknowledgement Received date  is selected at the receiver unit, authority record(s) will be created/updated after acknowledgement is imported by E2B Gateway.

 

The Fields in Inform Authority record will be updated as shown below:

 

 

When MDN Received date is selected at the receiver unit, authority record(s) will be created/updated after MDN is received for an exported ICSR.

 

 

 

Authority Field TYPE_OF_REPORT Mapping Logic

 

System will populate TYPE_OF _REPORT field in IA record based on the message type of the exported ICSR as shown below. For ichicsr cases system will check for the value exported in < fulfillexpeditecriteria>tag and populate TYPE_OF_REPORT as periodic report if <fulfilexpeditecritiria> tag is exported with value '2' and case is exchanged with a partner/authority residing in US territory.

 

<messagetype> in ICSR

Receiver Country

<fulfillexpeditecriteria>    tag value in exported ICSR

AER_INFM_AUTH.TYPE_OF_REPORT

Psur

Non-USA

Any

PSUR

Psur

USA

Any

Periodic report

backlog

Any

Any

backlog

backlogct

Any

Any

Alert report/15 day NDA report

Ctasr

Any

Any

Alert report/15 day NDA report

Ichicsr

USA

2

Periodic report

Ichicsr

USA

1 (or) NULL

Alert report/15 day NDA report

Ichicsr

Non-USA

Any

Alert report/15 day NDA report

 

 

Authority Fields Mapping Logic (Export):

Whenever the receiver of the ICSR case is a health authority, the <casenullification> and <nullificationreason> tags will be populated based on the below conditions.

 

  1. Check the Version No of the case, if the authority records are available for the same version of the case then the latest authority record belonging the same version of the case will be considered.

  2. If the follow up number is present then the nullified is checked, then the tags <casenullification> and <nullificationreason> will be exported otherwise the tags will not be exported.

 

Japanese logic (Export)

Whenever the receiver of the ICSR case is a health authority, the <casenullification> and <nullificationreason> tags will be populated based on the below conditions:

  1. Check for the authority records are available for the same version of the case then the latest authority record belonging the same version of the case will be considered (That is, authority record with max auth seq).

  2. Check if the followup numb is null or 0 or transmission status = 0 then followup number is assigned 1. In case the resubmission flag is null and transmission status is 1 or 2 then follow up numb is incremented.

  3. If the follow up number >1 and nullified is checked, then the tags <casenullification> and <nullificationreason> will be exported with the nullification detail from the authority record. Otherwise the tags will not be exported.

  4. the receiver of the ICSR case is a non health authority then provided  nullified is checked, the tags <casenullification> and <nullificationreason> will be exported with the nullification details from the AER table.

 

Japanese Logic (Import):

Irrespective of the sender type the casenullification details are imported to AER.NULLIFIED if nullified is not NULL and nullificationreason details are imported to AER.REASON_FOR_NULLIFICATION provided reason for nullification is not NULL

 

A.1.0.1 - Safetyreportid

A.1.5.2 - Seriousnesscriteria

A.1.10.1 -  Authoritynumb

A.1.1 - Primarysourcecountry

A.1.6.a & A.1.6.b - Receivedateformat & Receivedate

A.1.10.2 - Companynumb

A.1.2 - Occurcountry

A.1.7.a & A.1.7.b - Receiptdateformat & Receiptdate

A.1.13 - Casenullification

A.1.3a & A.1.3.b - Transmissiondateformat & Transmissiondate

A.1.8.1 - Additionaldocument

 

A.1.13.1 - Nullificationreason

A.1.4 - Reporttype

A.1.8.2 - Documentlist

A.1.14 - Medicallyconfirm

A.1.5.1 - Serious

A.1.9 - Fulfillexpeditecriteria

 

 

Back to ICHICSR Safety Report