For Australian Users of Bp Premier
On 23rd November 2018, a notification was sent to our customers advising of potential errors being generated for limited report types. In essence the notification covered 2 scenarios in which these errors can be generated and subsequent steps that can be taken to minimise the generation of said errors.
We would like to take this opportunity to provide a refresher on the issues, an update regarding resolution of these issues and appropriate next steps that our customers can take.
Potential Issue 1:
This applies to users of Bp Premier on all versions from Lava up to and including Jade.
Users may experience issue with duplicate payments showing on payment reports if multiple people perform a ‘Check for Payments’ simultaneously or if a user double clicks rather than single clicking on the 'Check for Payments' button.
Potential Issue 2:
This applies to users of Bp Premier on Lava and Indigo.
Users may experience an error (Subquery returned more than 1 value) when running Services - By Account Type (Grouped by item) Reports and similar reports.
This error may be caused by performing multiple service adjustments within Online claiming. This issue can occur when a Medicare item has been adjusted or resent multiple times, and a batch that contains that item is reset via Bp Premier’s 'Get Processing report' function. This error could also occur if the same invoice is updated simultaneously on two or more screens.
Further information on these issues can be found by clicking here.
Since this issue was first reported, we have not only worked to minimise the risk of these issues occurring, but have also spent many hours reconciling impacted reports and continue to do so. With that said, we highly recommend that customers invest time and effort in upgrading their version of Bp Premier to JADE SP1, when released this month. This will assist with minimising the continuation of these errors and avoid the protracted time reconciling impacted reports and dealing with any negative ramifications.