My Oracle Support Banner

Patient Age Group Mismatch In UI Vs DB (Doc ID 2823663.1)

Last updated on APRIL 29, 2022

Applies to:

Oracle Argus Safety - Version 8.1.2 and later
Information in this document applies to any platform.

Goal

User observed that for the cases booked in from Argus, Patient age group in UI is different from the age group range found in the DB. (eg: Age 64, UI - Adult and DB - Elderly).
Age group
Whereas the Configuration shown in console is as below

 

Adult - 18 to 64.999
Elderly - 65 to 199



After investigating it is observed that when user updates the Event Onset Date/Time on Events tab and saves the case before navigating to Patients tab this issue occurs.

Please see the example below:

Patient DOB: 31-AUG-1954
Event Onset Date/Time: 24-AUG-2020
Age: 65
Age Group: Elderly
DB: Elderly



1. Navigate to Events Tab and update Event Onset Date/Time: 24-AUG-2019
2. Save the case
3. Navigate to Patient tab

Patient DOB: 31-AUG-1954
Age: 64
Age Group: Adult
DB: Elderly



Is this a bug, as system needs to take care of updating any related fields when corresponding fields are updated in UI or is this standard behavior?
 

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.