Database differences for cases promoted from Safety One Argus

Before

When an E2B record was ingested in the Safety One Intake system and promoted to Argus, some case data could differ from data entered directly in Argus:

• Automatic calculations could overwrite the following field values:
  • Event > Duration
  • Event > Onset Latency
  • Product > Duration of Administration
  • Product > Time Between First Dose/Primary Event
• A Japanese event text was mapped incorrectly to an English term.
• Case form mappings did not persist medical history ingredient data.
• Seriousness from a case assessment was not propagated to the CASE_MASTER.SERIOUSNESS database flag. (Bug 39952474)

After

When an E2B record is ingested in Safety One and promoted to Argus:

• Imported Event Duration,Onset Latency, Duration of Administration and Time between First Dose and Primary Event values are retained.
• Japanese term is not populated with an English term.
• Case form medical history ingredient mappings create the associated ingredient entity.
• A Serious case assessment sets the CASE_MASTER.SERIOUSNESS.

Impacted areas

Intake processing