Issues addressed in Pega Smart Claims Engine for Healthcare 8.6
This table describes issues resolved in this release that are of the most interest to and are likely to have the most impact on the Pega user and developer community.
The following ID references are used:
- Reference numbers beginning with “ISSUE ” refer to bugs logged in the Pega issue-tracking system.
- Reference numbers beginning with "INC-" or “SR-” refer to corresponding Support Requests logged in My Support Portal.
| ID | Title and description |
|---|---|
| ISSUE 597025 | An error was displayed when the cost shares were manually updated after splitting the claim using the guided event resolutions. This is fixed with the 8.6 release. |
| ISSUE 81826 | The service unit count defaulted to 1 for all claim types if the value on the incoming file was blank. This is resolved and only dental claims are defaulted to 1 when the field is blank. The system raises event codes if incorrect units are submitted (blank or zero). |
| ISSUE 534149 | Task level SLA’s were not created when claims were retrieved via search and an action was subsequently performed on it. The due dates and urgencies are now added to this task. |
ISSUE 597882 | The system was unable to process 276 xml file due to a parameter limitation on data transforms calling another data transform. This is now resolved in the 8.6 release. |
Previous topic Upgrading from prior versions Next topic Known Issues in Pega Smart Claims Engine for Healthcare 8.6