These release notes describe the most important changes/fixes in version 7.0.2 of the CS R4+ software.
During Trade Trial Beta the tool tip shown when hovering over the NHS / CHI number in the patient banner would simply repeat the number shown which was found to be prone to being misconstrued with patients phone number so the tool tip will now indicate what the displayed number represents i.e. NHS number for England, Wales and Isle of Man and CHI number for Scotland and Northern Ireland.
Feedback received during Trade Trial Beta indicated that only displaying session types as new column in each appointment book was harder for users to see and prone to incorrect bookings.
To mitigate this, we have adjusted the grid so booked appointments or text slots do not overlap with the new session type column and we have also reverted to colouring all unused slots with the session type colour as before in the old Diary design. These changes balance ease of use with the new design layout.
During Trade Trial Beta an error was displayed each time a Group appointment was selected in the Planner, this issue has now been addressed.
During Trade Trial Beta an issue was identified that affected adjusted payment claims that did not require Prior Approval that would display an error when a user attempted to settle the claim, this has now been addressed.
During Trade Trial Beta an issue was identified that affected payment claims which had a portal based Prior Approval, an error would be displayed when attempting to set FTR or Patient Declined on the payment claim stopping the user from setting either option for a claim, this has now been addressed.
During Trade Trial Beta an issue was identified that affected any prior approval which contained seditionist treatment, if the user attempted to edit and untick the seditionist required option an error would be shown and any changes made would be lost, this has now been addressed.
During Trade Trial Beta some claims with CDS data were being rejected, after investigation it was found the Patient Assessment, General Anaesthesia, Incomplete Treatment and Referred out for completion options were encoding to values not recognised for CDS codes, we have now addressed this so any claims rejected with a E000677 error should be resubmitted under this release.
During Trade Trial Beta the Treatment Arrangement and CDS tabs were not being displayed on any Payment Claim that also had a Portal based Prior Approval associated to it, this has now been addressed.
Certain Treatments are expected to have X-Rays and / or Study Casts available if requested by the board as part of a Payment Claim or Prior Approval, under normal circumstances these options are automatically set based on SDR rules.
If a course contains no treatment that expects evidence then the options were entirely removed stopping users that had evidence available anyway to indicate this to the board, we have addressed this so in this situation a user can now specify either evidence available on both a Payment Claim and Prior Approval where appropriate.
The calculation that specified where Commissioner Approval is required or not for a Orthodontic claim was using the wrong date period forcing users to provide it when not allowed and likewise not provide when expected, we have moved this specific validation to allow the user to set themselves or change where necessary if a previous submission was rejected.
Some treatment codes have limited use in single Courses of Treatment however due to how rules are applied to treatment in CS R4+ code 1504 could be applied in a manner the board do not expect, if used in this manner the transmitted Prior Approval would also be incorrect and rejected so we have improved the encoding logic when transmitting a Prior Approval to mitigate this issue.
If charting via Clinical Chart discretionary treatment initially have a zero value until a Suffix is specified to indicate its correct charge so if proposing Discretionary Treatment once on the PA Request form and indicating the Suffix upon returning to Clinical Chart the value would still show as zero, this has now been corrected.
An issue was identified where if any crowns were proposed the additional fee code was not being added, this has now been addressed.
If charting a 4405 this code can only apply a charge once per tooth however depending on the Surface combinations involved users would chart more than once, but each code was charging again on the same Tooth, we have addressed this as follows:
We have updated the DPB Code so any New Courses of Treatment will allow for any necessary combination of surfaces for Deciduous Teeth as needed by the clinician so they can chart only once per tooth where required.
If the treatment code has already been used more than once on the same tooth in an existing open Course of Treatment we will recalculate the charge so to only apply once per tooth in the Treatment Plan (a recalculation will need to be triggered by making a temporary change to the course).
Any Claim submission where this already happened may have received a rejection due to code misuse, we will automatically adjust the next claim submission to indicate a single charge per tooth as expected per SDR rules.
If a Patient had an appointment at a different clinic under a resident clinician then the patient would not show when searching for Patient Recalls under the patients Home clinic, this has now been addressed so the patient will return regardless of where the last appointment was located.
An issue was recently identified caused by large numbers of existing claim records which cause gradual performance loss as new claims were sent before reaching a point where the system would time out and never send anymore claims, this has now been fixed a side effect of which is a substantial performance improvement of 60% so all users will notice an improvement when transmitting.
After discussion with the board any treatment present on a Deciduous tooth in a Retained situation must instead been transmitted under its Permanent Tooth equivalent, we have addressed this so resubmission of any affected claims will submit as the bard expects.
During Trade Trial Beta when transmitting a batch of claims a notification message was displayed to inform the user if the batch did not contain any Prior Approval’s. This message caused confusion as there was concerns that they were then missing expected Prior Approvals when they weren’t, we have now removed this prompt to stop unnecessary concern.
The password check was not operating in the right order meaning if a user had no password to begin with and someone else tried logging in under their user ID, but entering a wrong password that user would be prompted to reset the password effectively locking out the original user, this has now been addressed.
Certain implants which can protrude above the gumline were not showing on the Plaque and Bleed chart stopping the user from able to chart against them, this has now been addressed.
An issue was introduced over the last few releases which stopped DPDE registered users from accessing the Patient Exchange for Candidate Matching, this has now been addressed.
Based on customer feedback we have introduced the current date when printing out a Periodontal Chart so to know when a chart was printed if keeping the paper printouts.
An issue was identified where if a user attempts to baseline a patient mouth where the patient doesn’t have an existing open Course of Treatment it would display errors, this has now been addressed.
Some of the queries available when building a Report using the Report Query wizard would create database queries that would fail due to differences between some of the SQL generated by each, this now been addressed.
Due to differences between databases based on the version of CS R4+ installed and the upgrade path taken the [TQWJoin] table can include empty rows which causes the Report Wizard to fail, we have made changes where reading this table to address this issue.