The following is a list of enhancements included in R4+ v8.1.17. All fixes are cumulative (each new release contains all new fixes as well as all fixes from the previous release).
Where FP17 andFP17O Claims are submitted to COMPASS if a Patient's has an NHS Number this is used to assist in Patient Matching and identification for the Claim. COMPASS will now return the NHS Number for Patients if none was recorded on a Patient or if the NHS Number is found to be different to that on the existing Patient Record.
R4+ will now always update the Patient Record with the received Number when processing Claim Responses to ensure consistency with the NHS Record.
Where FP17 andFP17O Claims are submitted to COMPASS if a Patient's Name or Gender is found to be different to the NHS Patient Record then the NHS Record will now be updated with those received and the old details returned when processing Claim Responses to indicate changes, this information will simply be made visible via the Patients Scheme tab for informative purposes.
However, if the Patient's Name or Gender is found to be different during NHS Number matching the NHS Record will not be updated in COMPASS when the claim is processed, and the NHS held details instead returned and shown in the Patients Scheme Tab to indicate a detected difference between the NHS Record and local Patient Record details.
The HSC has confirmed an increase in the NHS Prior Approval Limit Threshold from £280 to £380, R4+ will apply this new limit to NHS Courses Accepted from April1st, 2023.
The PSA after further consultation with Clinicians highlighted older ongoing Orthodontic claims require fee support for Discontinued Bite Planes so new 32 and 33 Suffixes have been added to Codes 3290 and 3292 for SDR Periods between2013 to 2021 to accommodate this, new fee updates have now been added in R4+ v8.1.17.
R4+ has implemented OAuth 2.0 Authentication Support when using Google for email services with the R4+ Scheduler Internal Mail Client for email Communication.
Scheduler Settings now provides an Auth Provider option to change your authentication type then the necessary client and secret ID’s can be set under the More Settings window before undertaking authentication for use.
NOTE: If a token has expired and requires a new interactive authorisation to refresh when undertaking any immediate SMS Send If that auth attempt fails or is prematurely closed by the userR4+ may seem to no longer respond and hang, R4+ will automatically recover within 2 minutes of the attempt being made this is due to limitations in Googles client Auth.
The following is a list of issues addressed in R4+ v8.1.17.
A defect which caused R4+ to not recognise Codes 5836 & 1441 when calculating between Band 2B and 2C has been fixed in R4+ v8.1.17.
A defect which caused R4+ to not recognise any new Filling or Extraction Codes when calculating between Band 2B and 2C has been fixed in R4+ v8.1.17.
A defect which caused R4+ to not correctly encode Triage FP17 Claims so would not be recognised by COMPASS has been fixed in R4+ v8.1.17.
A defect which caused R4+ to not correctly prompt users if attempting to use incorrect treatments in an Urgent NHS Course has been fixed in R4+v8.1.17.
After discussion with the PSA, it has been ascertained that Referral Treatment Codes cannot be identified upfront of an approval so these could be added to a Course after approval, but before completion and subsequent Final Payment Claim Submission allowing these treatments to be added or removed freely without requiring Re-Approval from MIDAS, this has been addressed in R4+ v8.1.17.
After discussion with the PSA the Orthodontic Assessment Left and Right Canine Relationship can now be individually specified instead of requiring both to be set as a pair, but the PSA still expect Clinicians to record this correctly when necessary, this has been fixed in R4+ v8.1.17.
A defect which caused R4+ to include invalid Surface information on any Teeth Annotations defined as Present or Missing with Space Closed resulting in rejection by MIDAS has been fixed in R4+ v8.1.17.
A defect which caused R4+ to not correctly set the right end time on the last day of each month under contract where it was automatically extended has been addressed. Also, any existing shortfall detected in the current active period will automatically be patched prior to nearing the next extension period, this has been fixed in R4+ v8.1.17.
A defect where if a new Authentication Token required user input the Scheduler would halt, if Jobs are scheduled out of hours these would never run so if a token need were affecting the running job it will now automatically fail and record this to allow all other pending jobs to complete, users can observe the failed result the following day and reauthenticate to allow the next scheduled run to complete normally if unattended. This has been corrected in R4+ v8.1.17.
If a user accidentally set a DCP User within a FP17 Claim they were then unable to remove them, a new N\A entry has been added to allow users to correct this without being forced to transmit a DCP User who was not involved in a Treatment Claim, this has been fixed in R4+ v8.1.17.
If an administrator has planned changes to DPB Codes that come into effect from a future date they were then unable to delete these pending changes,this has been addressed in R4+ v8.1.17.
Under certain conditions when updating from older versions of R4+ the Patient Search and EDI Claim Search result would start to display incorrectly,this has been addressed in R4+ v8.1.17.