Oracle Analytics Cloud and Server Idea Lab

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OAS RPD support for CLOB fields replacing current LONGVARCHAR limit of 32K char

Needs Votes
83
Views
0
Comments

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Oracle HSGBU (HSC)

Description (Required):

The HSGBU Safety Cloud pharmacovigilance application (Argus Safety) contains many CLOB fields e.g. to capture the case narrative for a patient who experienced an adverse event. While often the length of CLOB fields like the case narrative are below 32768 characters which is the limit for long text fields in the OAS/OBIEE RPD, certain cases have more data. Because of the constraint to 32768 characters we need to truncate such fields and our users miss part of what is critical medical information in their queries. It is to be noted that currently in the RPD we do query such CLOB fields using a sparse lookup because our Safety database max_string_size is 4000. We have our asked our product team to consider going to 32K but even then we will keep the same limit in the RPD. OUR IDEA IS TO DESIGN IN OAS RPD THE FUNCTIONALITY TO BE ABLE TO QUERY ON CLOBS WITHOUT LIMIT OF SIZE, IE UP TO 2GB.






Use Case and Business Need (Required):

The use case and business need is for Oracle HSGBU Safety Cloud customers to be able to query/retrieve patient case narratives without loosing information beyond the current 32K limit. Medical information is critical. OAS should enable through the RPD to no lose any information. This request also applies to case attachments : they are the patient adverse event source docs such as lab test reports, hospital reports, literature docs etc. While such docs are stored in BLOBs and have office document types, it would be also great to provide in OAS/RPD the capacity to search and query on such docs (converting office docs to text) and not be limited by 32K. We can then extend this also to images (e.g. scanner images) which it would be good to include in queries via OAS/RPD retrieving them from BLOBS.

The goal is to remove limits and allow OAS/DV to analyze all patient case data which is available.

Enhancement Request / Service Request:

This is an enhancement request generated following an SR 3-30352083351 : OBIEE / OAS limit of LONGVARCHAR to 32768

1
1 votes

Needs Votes · Last Updated