...
History of EVV
In December 20062016, President Barack Obama signed the 21st Century Cures Act into law. The 21st Century Cures Act states that any home health or provider agency that receives reimbursement from the government must have an electronic visit verification system in place. States must require EVV for Medicaid-funded home services for people with intellectual or developmental disabilities no later than January 1, 2020. The The development of the EVV system stemmed from the federal government looking for ways to reduce incidences of fraud and abuse. Medicaid and Medicare fraud cases have been on the rise—potentially costing the government millions and millions of dollars. As just one example, in June of 2016, the the Medicare Fraud Strike Force charged 301 individuals from across the nation with filing approximately $900 million in false billings. With EVV, filing false paper-based attendant timesheets would not be possible.
...
Identify team member(s) responsible for EVV visit maintenance
Log in to your aggregator portal daily
View EVV visits and aggregation status in the aggregator portal
- Triage EVV errors with your state and/or aggregator as a first point of contact
Review DCI EVV Aggregation reports that are emailed to you daily
Perform visit maintenance in DCI to correct visit errors
Review all six required aggregation requirements
Type of service performed
Individual receiving the service
Date of the service
Location of the service
Individual providing the service
Time the service begins and ends
- If the error in DCI can not be resolved independently, submit a help desk ticket (zendeskZendesk) for DCI
DCI Generated EVV Aggregation Reports
EVV entries are aggregated daily generating a daily report by DCI to inform each organization on their entries aggregation status. The DCI aggregation report may vary by each organization based on the required data per aggregator. An example of column columns that may be included are listed below:
- Date of Service - Date the punch entry was created
- Punch Entry ID - An unique id # for the punch entry in DCI
- Punch Class - Type of service i.e., hourly, group service
- Punch Type - status of the punch i.e., new, update
- Client Profile ID - An unique id # for the client profile in DCI
- Employee Profile ID - An unique id # for the employee profile in DCI
- Bill Code - Billing codes used in DCI for each funding source.
- Result - Result of the aggregation for each punch entry id i.e., Success, Failure
- Result Reason - The If the punch entry id has a result of failure, the reason for aggregation failure will be listed in this column
The ID number for each object is located in the URL of the object entries page. Please see the article, How to view the details page by changing the URL? for additional information.
EVV Aggregation by State
Click on your state to see more state specific information.
Submitting a DCI Support Ticket for EVV Aggregation Issues & Resolutions
As a reminder, your organization must log in to the Aggregator portal and review your aggregation results daily. The Aggregator will always be your first point of contact to triage any rejections, as they are the experts on visit failures, reasoning, and verbiage. If the visits require DCI intervention to re-aggregate, please submit a Help Desk support ticket (Zendesk). Please see the help center article for detail instructions, Submitting a DCI Support Ticket for EVV Aggregation Issues & Resolutions.
EVV and EVV Compliant Field
For information on this topic please view the following article: What do the fields EVV and EVV Compliant mean in DCI?