Oregon EVV Vendor Documentation

Program Overview

Introduction

In compliance with Centers for Medicare and Medicaid Services (CMS) Electronic Visit Verification (EVV) regulations, Acumen collaborates with the Oregon Department of Human Services (ODHS) and the Oregon Health Authority (OHA) to provide State of Oregon EVV Data Aggregation. The Direct Care Innovations (DCI) Data Aggregator receives, consolidates, and processes EVV data from multiple providers, vendors, or agencies and submits it to the appropriate oversight entity.

This guide supports project management and technical teams at designated Alternate EVV Vendors implementing the Oregon EVV interface. Updates are distributed by email as system capabilities, functionality, or State requirements change.

Key Contacts and Support

Transmission Method

DCI provides an Application Programming Interface (API) for Alternate EVV Vendors. Vendors are contacted by the EVV Aggregation Support Team to commence onboarding, validated, and scheduled for an implementation wave to complete testing and integration.

Transmission Frequency and Limits

DCI utilizes a single transaction API. For optimal system performance, DCI recommends that visit data is sent in near real-time as it is added, changed, or deleted in the Alternate EVV Vendor data collection system. Data that is unchanged should not be resent to DCI.

General Rules

Three independent types of data are provided through the EVV interface: Client, Employee, and Visit.

• Client: For clientIdentifier, Oregon requires use of the client’s Medicaid Number.

• Employee: For employeeIdentifier, Oregon requires use of the employee’s Social Security Number (SSN).

• Visit: Reason code requirements are defined by the State and must be submitted when required for manual or edited visit entries.

For rules that prevent a visit from reaching Aggregation Success, the issue should be resolved in the Alternate EVV Vendor data collection system and the information retransmitted.

Onboarding Process

1. Oregon Department of Human Services sends an introduction email to the EVV Vendor.

2. Acumen sends the Oregon EVV Vendor Specifications and a link to the online Vendor Onboarding Form.

3. EVV Vendor completes the Vendor Onboarding Form online.

4. Acumen provides the implementation wave start date and estimated duration.

5. Acumen generates test environment login credentials and distributes Oregon PTC Phase 3 Alternate EVV Vendor Test Specifications.

6. EVV Vendors and provider agencies complete testing requirements and request production credentials.

7. Acumen and the State review and accept the Test Completion Report.

8. Acumen distributes production credentials and live data submission begins.

API & Technical Details

Editor checklist (API includes)

1. Create the shared Confluence page for the API topic, using the exact page title shown in the placeholder.

2. Paste and maintain the generic API content on that shared page only; do not add Oregon-specific rules to the shared API page.

3. Confirm page permissions: vendor documentation readers must be able to view the shared page, and editing should be limited to API/documentation owners.

4. Return to this State page, open the matching expandable section, type /include, select the Include Page macro, and choose the shared page.

5. Verify the included content renders correctly for a non-editor or standard viewer before publishing broadly.

Reason Codes

Reason codes are used to explain manual or edited entries and are subject to change based on State requirements.