My Oracle Support Banner

Privacy Data Is Not Working In E2B Or CIOMS Reports - Why ? (Doc ID 1333300.1)

Last updated on JULY 01, 2011

Applies to:

Adverse Event Reporting System - Version: 4.7 and later   [Release: 4 and later ]
Information in this document applies to any platform.


Cannot successfully configure a field to be "private" to the Owning
User Group.

A "private" field is one that can only be viewed and updated by a
member of the User Group that owns the case.

Specifically, privacy data is not hiding patient's initials per E2B job.

The resulting .xml file still shows the patient's initials when job is submitted per someone outside the user group.

  1. Created a user group called "PV_FRANCE".
  2. Created one user called "FUSER1"
  3. In Global Maintenance, created a code list "PV_FRANCE", with one user group value "PV_FRANCE".
  4. Login as FUSER1, created a case A.
  5. In Patient Initial field, Goto Help -> FAT, added "PV_FRANCE" to Private In User Group List.
  6. Login as Superuser (not in user group PV_France), open case A.
  7. Patient Initial field displayed as "***" . This is correct.
  8. Run E2B or CIOMS reports as Superuser.
  9. Patient Initial value is displayed as the actual value.

Why is step 6 not returning 'PRIVACY' to hide the patient's initials ?


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

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