CS R4+ v6.2.2 Product Release Notes

These release notes describe the most important changes/fixes in version 6.2.2 of the CS R4+ software.

eDental – Claim containing multiple treatment codes sometimes resulting in a “ToothNotation element is invalid” claim rejection

It has been reported that some claims were being rejected as containing invalid tooth notations (E000684), further investigation has identified the issue, any claims currently rejected with this reason should be moved back to “Not Ready” and resubmitted after upgrading to this release to ensure they are accurately re-encoded and transmitted for payment.

eDental – Claim rejections due to Claiming Dentist being transmitted is not the Registered Dentist resulting in a NHS Type that the Board does not recognise

We will attempt to deduce the NHS Type for the transmitted claim where the Patients NHS Type is set to “Continuing care / Capitation” and where the claiming dentist is then compared to the recorded registered dentist in CS R4+, in some situations when the registered dentist record has been changed, but no registration has been previously transmitted this can result in CS R4+’s records no longer matching the boards resulting in a rejection (E000852).

If a claim is still rejected with E000852 due to this drift we have adjusted the claim form to allow the user to resubmit the claim again and change the ‘Acceptance Type’ as shown below on the claim to allow the NHS Type to be transmitted that matches the NHS board’s expectation.

Change claim "Acceptance Type" from

Change claim "Acceptance Type" to

Commence registration with this dentist

Not registered with this dentist

Continue registration with this dentist

Not registered with this dentist

Not registered with this dentist

Commence registration with this dentist

or

Continue registration with this dentist

eDental – Processing Reconciliation response has identified settlement failures if the same list number exists on more than one user

It has been reported that some initial reconciliation responses has reported errors and failed to process leaving some claims as “sent”, we have identified the issue and corrected so future reconciliations will not repeat this issue, for sites already affected as long as upgraded before the January 15th 2018 then the last received reconciliation will be automatically reset to allow full reprocessing correctly.

eDental – Claim Acceptance Date & Exemption History checks extended to 36 months

Previously we were checking a claims acceptance date using a default value of 12 months from the current date to indicate if a claim can be sent or not, additionally the check to ensure the right exemption is encoded for a given claim used the same date range.

It has been identified that claims can remain open up to 36 months which CS R4+ was then not allowing to transmit, we have adjusted these date ranges to 36 months so long standing claims will now encode with the expected exemption and also now transmit under eDental.

eDental – Processing of multiple submissions for the same claim at the same time can result in the wrong Claim status

It has been identified that if multiple submissions for the same claim has occurred in short order its possible for various responses for each submission to be pending for update, if this happened it was possible for the responses to be processed In the wrong order resulting in the claim status not reflecting that of the last submission sent, this has now been addressed.

eDental – Claims Not yet Submitted showing an invalid ‘Last Sent’ date

It had been reported that in certain situations a new claim was showing the “Last Sent” date of a different claim, this has now been corrected so the claim will either show as “Not Sent” or the date time stamp of its own submission.

 

Related Topics

8.2.0

8.1.19

8.1.18

8.1.17

8.1.16

8.1.15

8.1.14

8.1.13

8.1.12

8.1.11

8.1.10

8.1.9

8.1.8

8.1.7

8.1.6

8.1.5

8.1.4

8.1.3

8.1.2

8.1.1

8.1.0

8.0.0

7.0.2

7.0.1

7.0.0

6.8.0

6.7.0

6.6.1

6.6.0

6.5.2

6.5.1

6.5.0

6.4.0

6.3.0

6.2.3

6.2.1

6.2.0

6.1.1

6.1.0

6.0.2

6.0.1

6.0.0