INTRO MISSING. Add in Atlas for Oracle Health Insurance Claims Adjudication 3.22.1.0.12.
Enhancements
ID | Summary | Patch |
---|---|---|
AUT-2954 |
Include JVM GC metrics in Prometheus Metrics for GC monitoring have been added, controlled by a number of system properties: JVM metrics are enabled by ohi.instrumentation.gather.jvm (this used to be ohi.instrumentation.gather.jvmtelemetry) System metrics are enabled by ohi.instrumentation.gather.system (this used to be ohi.instrumentation.gather.jvmtelemetry) Garbage Collection metrics are enabled by ohi.instrumentation.gather.gc |
3.22.2.0.3 |
UI Changes
Ref | Action | Description |
---|---|---|
NXT-26785 |
Added |
Adjudication Limit Counters Added new JET UI Page. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
34882273 |
3-31454344411 |
NXT-26038 |
BP |
Covered Amount is set to null on claim line when line is denied with fatal message |
Description: |
Covered Amount set to null on claim line when line is denied with fatal message at Manual Adjudication |
|||
Resolution: |
On a denied claim the total covered amount is set to zero in the default currency. On an approved claim that includes claim lines with covered amounts in different currencies, the total covered amount and currency is left empty, i.e., set to null. |
|||
35043763 |
3-31945494731 |
NXT-26346 |
BP |
Time-Valid flex codes are not showing nested properties |
Description: |
Flex codes configured under procedure is not showing up in Claim lines. |
|||
Resolution: |
Users can now configure a floorplan at claim lines level for flex codes configured under procedure level. |
|||
34979337 |
3-31477093221 |
NXT-26207 |
BP |
Financial message not created for reversal transactions when covered amount on claim is null |
Description: |
If a claim processing involves currency conversion, a manual fatal message attached to the claim/claim lines can cause covered amount and covered amount currency (on claim and claim line) to be null. |
|||
Resolution: |
Financial messages for reversal transactions are now created when covered amount on the claim is null. |
|||
35109398 |
3-32181209591 |
NXT-26501 |
BP |
Assigned column name of flex code field usage when creating it from ADF UI is not correct sometimes |
Description: |
Assigned column name of flex code field usage when creating it from ADF UI is not correct sometimes |
|||
Resolution: |
The column name which was assigned while creating a flex code field usage after an error message was thrown, was incorrect. After the correct columnName is assigned, the deletion of dynamic records using method deleteDynamicRecord on key value works fine. |
|||
35130259 |
3-32265793401 |
NXT-26533 |
BP |
CLA - JET UI : The placing of decimal point is different in JET and ADF |
Description: |
For any scalar dynamic field in the response data for an entity, the value always came as a string "BigDecimalDynField": "12.34". but expected is "BigDecimalDynField": 12.34. |
|||
Resolution: |
ScalarAttributeGetHandler did not resolve the value for the dynamicFieldObject earlier, now it extracts the value of from a dynamicFieldObject to basic datatype like BigDecimal, integer etc. |
|||
35175270 |
3-32295832461 |
NXT-26625 |
BP |
Translatable attributes of flex codes are not migrated for all the installed languages using CMT |
Description: |
Translatable attributes of flex codes are not migrated for all the installed languages using CMT |
|||
Resolution: |
Translatable attributes of flex codes for all the installed languages are now migrated using CMT. Earlier, these variables were updated based on their source language that was causing conflicts. The fix now updates variables based on their current language. |
|||
35233829 |
NXT-26703 |
BP |
Dynamic records for Specialty is not working |
|
Description: |
Dynamic records for Specialty is not working due to which user cannot find it in view objects . |
|||
Resolution: |
This is resolved and we can see the dynamic records for Specialty in view objects . |