There was a Carestream system issue that flagged all eClaims containing a service date in January, 2019 as pre-authorizations instead of actual claims. Carestream is aware of the problem and is actively working to solve it. All affected claims will be resubmitted shortly.
There is no action needed on your behalf.
We apologize for any confusion and we look forward to continually serving your electronic processing needs.
The issue has been corrected and all claims from 1/1 - 1/7 have been resubmitted, with the exception of real-time claims. If any real-time claims were submitted during that time, they will need to be resubmitted by the practitioners.
This is a huge problem for our cash flow right now. Basically not getting paid for the last two weeks. Anything you are doing to remedy this?
The claims with dates of service in January 2019 were affected only on the following processing days, which include 4 business days (1/2, 1/3, 1/4, and 1/7). All of the affected claims were corrected and re-submitted from Carestream on 1/8/19. At maximum, there was 4 day delay in processing. Measures have been taken to ensure that this does not occur again.
Yes, it affected PracticeWorks claims also. They were all resubmitted on 1/8/19 and there is no action required on your behalf.
Thanks so much for your reply. An error occurred at Carestream and we posted notifications here on the CS Community and also sent out bulletin messages via the eServices reports. We apologize for the inconvenience and the delay of the claims. While it would have been informative to personally call everyone, unfortunately, it wasn't physically possible to place personalized phone calls to the many thousands of clients that were affected.
Please accept our apology for this inconvenience and we look forward to continually serving your electronic processing needs.
The message through the eclaims system didn't go through. The only reason WinOMS users know about this is through the JAWS forum. The claims have not been auto-resubmitted so we are having to manually review and resubmit. I'm assuming this error is due to another upgrade without proper regression testing.
Please provide your account number or phone number and we will have a technician reach out to you ASAP.