CounterInboundtoOHI: Records Written to OHI are being Displayed Under the Same Aggregation Level
(Doc ID 2577294.1)
Last updated on AUGUST 26, 2019
Applies to:Oracle Health Insurance Claims Adjudication - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.9 version, Integration Points
If we try to create and update the new counter consumption period using write batch consumption IP,
then the records are getting displayed under the existing period/level.
If a member has counters from period 1/1/2018 to 12/31/2018 and we try to create new counter period from 1/1/2019 to 12/31/2019 using counter consumption IP then the records are getting written at 2018 level.
However in database it does show correct counter consumption.
(Please note: if the counters are being created by the OHI claims then it is working fine. The issue is when AMS is trying to create and update a counter period or aggregation level that doesn’t exist (not created by claims)).
In 2.16.1 world- We can create and update counters for any counter periods we want and it updates and create the counters accordingly in both DB and UI.
The expected behavior is that it should create new counter for new counter period or for new aggregation level
The issue can be reproduced at will with the following steps:
1 select a member having limit counter created from 1/1/2018 to 12/31/2018
2. try to create 1 new counter using counter consuption IP for service date in 2019 and you will see the records are showing at 2018 level
The issue has the following business impact:
Due to this issue, users cannot .
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