Enhancement: Correct MessageOrigins Handled by Default for Predefined Method HasFatalMessage()
Last updated on FEBRUARY 22, 2018
Applies to:Oracle Health Insurance Claims Adjudication - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Typically a rule should not be triggered if a claim(line) has a fatal message. Currently, the predefined method hasFatalMessage() is used in dynamic logic to check if a claim(line) has a fatal message.
This method has an optional input for messageOrigin. If the messageOrigin is not provided as input to the method, all messageOrigins are taken into account by the method.
This may lead to issues in reprocessing of a claim.
A dynamic logic triggered in pricing with the hasFatalMessage method without messageOrigins added, will also see fatal messages that originated in a later processing step (eg benefits) when the claim was first processed. The messages from the first processing run should not be taken into account.
To handle this, all origins applicable should be added as input to the function. Currently there are 14 messageOrigins that need to be taken into account. This is cumbersome and hard to understand.
The enhancement request is to have the applicable messageOrigins (depending on the processing step) handled out-of-the-box as a default setting.
When messageOrigins are provided as input to the method, it then overrules the default behavior
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