58920 - 485 Cert Date Gaps causing Compliance Issue and potential for Write-Offs
We are finding errors in data entry of cert period start ends dates that are resulting in a gap in coverage between cert periods: Since Cert Dates are all manually entered it is very possible that human error can occur.
This is very serious for compliance and billing reasons.
At a minimum, we need some kind of canned report to monitor for this. (In general, I believe Alayacare should be providing better canned reports.)
If the system generated the episode dates automatically based on SOC date that would eliminate the problem…would anyone else find this helpful?
-
Hi Beth,
We understand your concerns, and will take your suggestion back to our Product team!
The good news is that if the Start Date field in the client's active service is populated, the expected behaviour is that the Certification Start Date will automatically be filled out. One note about this: it will automatically populate with the earliest Start Date in your list of active Services.
As for the End Date, it currently projects 60 days after the Certification Start Date, per Medicaid standards. However, you do have the option of changing this manually if it isn't accurate for your organization.
-
Hi Angela,
The help desk did not tell me the dates are supposed to auto-populate; they said there is no functionality like that, and the tech asked me to submit this item to the forum. She told me to do this so they can gauge how many others think this is a problem that requires action.
Please sign in to leave a comment.
Comments
5 comments