Queue Length Time In OHI

(Doc ID 2204884.1)

Last updated on NOVEMBER 21, 2016

Applies to:

Oracle Health Insurance Claims Adjudication - Version 2.14.2 and later
Information in this document applies to any platform.


A relatively long time is experienced between creation of an EnrollmentRequest task and the EnrollmentComplete task (45 seconds in some cases), even though the system does not have a high workload, hence should be able to pick up these tasks very quickly. 

The way it should work in this:  OHI application needs information from a Policies system about enrollment of a member on a product, so the system sends out an enrollment request to the other system. The EnrollmentRequest task spawns 2 tasks: the Enrollment task (which sends out the actual request) and the EnrollmentComplete task, which sits in the queue.
In the ohi-claims.properties file the property "ohi.processing.enrollmentcomplete.interval" indicates how often the EnrollmentComplete task awakes to see if all enrollment requests for this claim have been answered. If not, it will go back on the queue (with a maximum of "ohi.processing.enrollmentcomplete.timeout" seconds, after which it will fail with a timeout error) and wait for another ohi.processing.enrollmentcomplete.interval seconds.

The process_start_datetime of the EnrollmentComplete task is set only for the run that successfully detects that all responses were received. In this example it took 45 seconds between creating the EnrollmentComplete and Enrollment task (and, since that one was picked up immediately, 45 seconds since sending out the enrollment request to the outside system) and the start of the iteration of the EnrollmentComplete that detected that all requests were answered. 
Now this could mean two things: either the EnrollmentComplete task had been sitting idle on the queue for 45 seconds, or it took somewhere between 42 and 45 seconds before the enrollment response was received.
In the technical table CLA$ENROLLMENTS we keep track of when enrollment responses are received by our system. This table should be checked to see which of the two scenarios are in play.




Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms