Virginia Regulatory Town Hall
Agency
Department of Medical Assistance Services
 
Board
Board of Medical Assistance Services
 
chapter
Standards Established and Methods Used to Assure High Quality Care [12 VAC 30 ‑ 60]
Action Electronic Visit Verification
Stage Proposed
Comment Period Ended on 3/21/2020
spacer
Previous Comment     Next Comment     Back to List of Comments
2/12/20  8:07 pm
Commenter: Diane C, EOR

Exempt Live In Caregivers from EVV
 

Just received this concerning email from CDCN today (2/12/20): 

"Our records indicate you submitted new or adjusted shifts in the CDCN web portal with at least one of the EVV exceptions listed below.

1. The CellTrak mobile application was not working

2. My phone or tablet was not working

Shifts submitted with these exceptions are not EVV compliant. Let us assist you to submit EVV-compliant shifts."

This is so frustrating and insulting, especially #1 -- the app not working is OUR fault making us non-compliant?  #2 Phone isn't working - our cell phone stopped working for 2 days while a shift was running - no way to get into phone or therefore app.  Had NO option but to use the portal (can't use IVR with a shift running on the app; can't use a different cell phone because attendant can only be associated with one phone).  What were we supposed to do?  Why have you made this system so inflexible?  Why can't we have options of using a portal OR a landline OR a mobile app?  How is CDCN going to help us submit EVV compliant shifts when the app or phone aren't working?  Makes no sense.  But it does make for a LOT of false "non-compliance".  Accurately reporting or correcting time worked is NOT non-compliance or fraud; neither is using a portal instead of an app or recording time at the end of a day instead of logging in/out of a cell phone app multiple times/day.

Please listen to us -- exempt live-in providers from EVV.  Let us go back to logging in on the portal OR give flexibility in an app that makes sense for a 24/7 caregiver.    

The inflexibility of this reporting process and the substandard app that was built to support this process is the problem in this situation.  Please change this nightmare.

 

  

 

CommentID: 79057