The following is a list of enhancements included in R4+ v8.1.15. All fixes are cumulative (each new release contains all new fixes as well as all fixes from the previous release).
R4+ v8.1.15 has been updated to recognise CCN 51 changes for NHS England patients which comes into effect from November 25th, 2022. CCN 51 affects the compensation for practitioners involving more complex Band 2 treatments. It is important that the CDS treatments, especially endodontics, fillings, and extractions, are recorded and transmitted properly since they will affect the UDA awarded. Band 2 has been divided into three parts:
Band 2(b) covers courses of treatment involving either Non-Molar Endodontics to permanent teeth or a combined total of three or more teeth requiring either permanent fillings or extractions. 5 UDA will be awarded for Band 2(b) treatments.
Band 2(c) covers courses of treatment involving Molar Endodontics on permanent teeth. 7 UDA will be awarded for Band 2(c) treatments.
Band 2(a) covers all other Band 2 treatments. 3 UDA will continue to be awarded for Band 2(a) treatments.
The following is a list of issues addressed in R4+ v8.1.15.
A defect where the DMF values would incorrectly reset to 0 after any changes are saved to claims has been corrected in R4+ v8.1.15.
A defect which occurred if any of the Last Cancelled Appointment mail merges from the Last Cancelled Appointment mail merge menu are used in a document template, it would report the last known Cancelled appointment that wasn't WNB. This has been fixed in R4+ v8.1.15.
A defect where a user attempts to return to normal Patient Search mode (by name) after having used Telephone Search prevented the search field label from being returned to DOB (which is appropriate). This problem has been resolved in R4+ v8.1.15.
A defect where sites with the scheduled DPDE task caused the scheduler to stop running, which prevented all recurring reminder tasks from executing has been fixed in R4+ v8.1.15.
Some R4+ sites which actively used Tutor were experiencing issues due to the large size of the database and the associated Transaction Log. The DB recovery model will be adjusted to Simple to reduce the size of the database given this is a Training database with lower operational concerns.