The following is a list of issues addressed in R4+ v8.2.0. All fixes are cumulative (each new release contains all new fixes as well as all fixes from the previous release).
The following is a list of issues addressed in R4+ v8.2.0.
In December 2022 the Base Prior Approval floor limit was adjusted from £410 to £430, however, since then it has been observed that MIDAS has not always been issuing Tiering Updates to realign Individual List numbers who were previously below the new limit.
During the upgrade we will identify and retrospectively uplift any users who are actively below the current floor limit to £430 from December 14th 2022,to align all affected users with the current MIDAS floor limit. Also, in the case of new dentists being configured, the system's default floor limit has now been raised to £430 in the absence of receiving a Starting PA Tiering Update from MIDAS. This has been fixed in R4+ v8.2.0.
R4+ v8.2.0 has been updated with new postcode Data Zone mapping to prevent MIDAS rejections due to incorrect Childsmile fees being applied.
After the R4+ Upgrade completes, go to Utilities > Import Childsmile from the Main Menu to apply this update to your system.
An issue has been observed since v8.1.13 whereby sites would be receiving DPDE Message updates and sync confirmations but failing to process them, causing an increase in Sync Failures from that moment forwards. We will now successfully decompress the received responses and process them to allow ongoing operation with the DPDE and Direct Registration Services. This has been fixed in R4+ v8.2.0.
If you are using Denplan, due to the length of time messages have not been processed, it is required to schedule a Resync after the upgrade to ensure parity between R4+ and Denplan's records moving forward. Please Contact R4+ Support so the necessary details can be identified to inform Denplan as soon as possible.
R4+ will now Negotiate and Communicate with the Denplan Patient Data Exchange & Direct Registration Services using the TLS 1.2 Protocol. This is required to ensure ongoing operation with the Services due to the planned expiry of Legacy TLS Protocols to adhere to Modern Web Security Standards. This has been fixed in R4+ v8.2.0.