> For the complete documentation index, see [llms.txt](https://fieldworker.gitbook.io/fieldworker-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fieldworker.gitbook.io/fieldworker-docs/fundamentals/faq/how-to/evv-checklist.md).

# EVV checklist

To utilize HHAX with Fieldworker app, users need to complete the following steps:

1. Contact your Account Manager to enable visit verification.
2. In Fieldworker:
   * Clients’ addresses need to be [geolocated](https://community.centralreach.com/s/article/How-to-Geocode-Existing-Locations).
   * Set up clients’ Medicaid Insured IDs in their Payors section.
   * Input the HHAX production credentials in the Visit Verification Settings.
   * In the organization’s “Accepted Insurances” section, identify the payor as Medicaid (select the **Medicaid** checkbox).
   * Add the billing provider’s Tax ID in the organization’s Claims Settings.
   * Enter employees’ first name, last name, DOB, and hire date to the Basics section of their profile, and make sure the information is synced in their [Claim Settings](https://community.centralreach.com/s/article/How-To-Add-and-Edit-Employee-Claim-Settings).
   * Ensure the appropriate staff have the necessary [CR Mobile and billing permissions](https://community.centralreach.com/s/article/How-to-HHAeXchange-HHAX-Permissions), including the (Billing > Visit Verification) permission.
3. In the organization account, navigate to (Settings > Visit Verification Settings > +Add Credentials) to input your HHAX production credentials, which should have been emailed to you from HHAX.
   * The email should contain a secure message for users to create a password and access production credentials.
4. Complete all EVV appointments in CR Mobile.
5. Complete draft timesheets by inputting EVV reason codes, adding session notes, or addressing any other next steps.
6. Generate claims before sending visits to HHAX.
7. Submit [visit verification data](https://community.centralreach.com/s/article/How-To-View-the-Status-of-Visit-Verification-Data) in the Billing module.
   * If records are accepted, access the HHAX Portal for any pre-billing and billing edits. If records are not accepted, review errors and resend the visit(s). For questions contact CR Support.

### Setting up a new company for EVV

Settings for Company (Provider)

·   Which payer do you work with? NJ FFS? (Use Settings to establish)

·   What provider services do you provide? (Use Task code mapping to establish them)

·   Do you have multiple offices? Do these have separate tax ID? Or NPI?

·   Ensure Federal Tax ID is in the system

 

EVV onboarding

1. Payer - The company is presented with the list of approved payers for the state. Each company is expected to be working in one state and is expected to be working with single-payer only. Payer information is captured in the company table as well.
2. EVV procedure code - Once the company has selected all task types (or added new task types, as needed), they will need to map the Fieldworker task types to EVV procedure codes. This can be done by selecting the three dots options from the Settings screen.
3. EVV Billing - This will be a new option under ‘Billing and EVV settings’. This would allow setting/changing the bill rate for various procedures mapped for your company.

For each employee (caregiver), capture

·   Date of birth

·   Gender (Male/Female/Other)

·   Email

·   Phone number

·   Professional License Number

·   Hire Date

·   State

·   Zip code

·   Caregiver type (Skilled/Non-skilled/Both)

·   SSN (A default of 999999999 can be used)

 

For each customer (patient, or member)

·   Name

·   Address (all locations)

·   Phone number

·   Medicaid ID

·   Ensure that the project start and end date are same as MCO contract date

 

For each visit (captured in task)

·   Visit type

·   Patient

·   Date of the service

·   Location

·   Caregiver

·   Time starts and end


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://fieldworker.gitbook.io/fieldworker-docs/fundamentals/faq/how-to/evv-checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.