Oregon EVV Third Party Vendor Testing Specifications

Oregon EVV Third Party Vendor Testing Specifications

Third-Party Vendor Testing Onboarding

This page outlines the Oregon Phase 3 DCI EVV Data Aggregator testing scenarios that third-party vendors must complete during onboarding. Vendors are expected to execute each scenario, record the applicable client, employee, or visit identifier, and submit the completed checklist to the Aggregator team for review.

Vendor submission expectation: Complete every required scenario listed below, fill out the Vendor Test Case Checklist PDF, and attach the completed checklist to the active vendor onboarding Zendesk ticket when testing is finished. Incomplete or inaccurate checklist information may delay review or production credential distribution.

Project details

Project name

Oregon Phase 3

Last reviewed

Feb 17, 2026

API environment and endpoint examples

Use the sandbox API environment link to build Aggregation Manager API endpoints for testing: https://xcore-sandbox-api.dcisoftware.com/

The base environment is https://xcore-sandbox-api.dcisoftware.com/. Append the Aggregation Manager path and object route for the endpoint you need.

  • Client endpoint example: https://xcore-sandbox-api.dcisoftware.com/api/aggregationManager/client

  • Employee endpoint example: https://xcore-sandbox-api.dcisoftware.com/api/aggregationManager/employee

  • Visit endpoint example: https://xcore-sandbox-api.dcisoftware.com/api/aggregationManager/visit

  • Update endpoint pattern: https://xcore-sandbox-api.dcisoftware.com/api/aggregationManager/{object}/{identifier}

Downloadable checklist

Vendors must download and complete the Vendor Test Case Checklist PDF, then send the completed checklist to the Aggregator team for review through the active vendor onboarding Zendesk ticket.

file://user/fileupload/2626d460-3047-40f2-a65e-2398b21b9c4a

Required testing scenarios

The scenarios below are the minimum onboarding test cases vendors must complete. Each scenario includes the scope, required preconditions, execution steps, expected results, and post-condition or system response to verify.

Phase 1: General validation scenarios

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

AEV-001-001

1

Happy Path Client

Create Client is accepted by the Aggregation Manager.

Code 200; GUID of the Client

AEV-001-002

1

Happy Path Employee

Create Employee is accepted by the Aggregation Manager.

Code 200; GUID of the Employee

AEV-001-003

1

Happy Path Visit

Create Visit is accepted by the Aggregation Manager.

Code 200; GUID of the Visit

AEV-001-004

1.1

Server Error

The target object is not accepted by the Aggregation Manager.

Code 500; An internal error occurred during your request.

AEV-001-005

1.2

Unable to Authenticate Username

The target object is not accepted by the Aggregation Manager.

Code 401; Unauthorized

AEV-001-006

1.2

Unable to Authenticate Password

The target object is not accepted by the Aggregation Manager.

Code 401; Unauthorized

AEV-001-007

1.2

Unable to Authenticate User Permissions

The target object is not accepted by the Aggregation Manager.

Code 401; Unauthorized

AEV-001-008

1.3

Incorrect Payload or Schema for Client

Create / Update Client is not accepted by the Aggregation Manager.

Code 400; Your request is not valid.

AEV-001-009

1.3

Incorrect Payload or Schema for Employee

Create / Update Employee is not accepted by the Aggregation Manager.

Code 400; Your request is not valid.

AEV-001-010

1.3

Incorrect Payload or Schema for Visit

Create / Update Visit is not accepted by the Aggregation Manager.

Code 400; Your request is not valid.

AEV-001-011

1.4

Data Not Formatted Correctly for Client

Create / Update Client is not accepted by the Aggregation Manager.

Code 400; The [field name] has an invalid format.

AEV-001-012

1.4

Data Not Formatted Correctly for Employee

Create / Update Employee is not accepted by the Aggregation Manager.

Code 400; The [field name] has an invalid format.

AEV-001-013

1.4

Data Not Formatted Correctly for Visit

Create / Update Visit is not accepted by the Aggregation Manager.

Code 400; The [field name] has an invalid format.

AEV-001-014

1.5

Min/Max Character Validation Failure for Client

Create / Update Client is not accepted by the Aggregation Manager.

Code 400; Value violates min/max requirements.

AEV-001-015

1.5

Min/Max Character Validation Failure for Employee

Create / Update Employee is not accepted by the Aggregation Manager.

Code 400; Value violates min/max requirements.

AEV-001-016

1.5

Min/Max Character Validation Failure for Visit

Create / Update Visit is not accepted by the Aggregation Manager.

Code 400; Value violates min/max requirements.

AEV-001-017

1.6

Missing a Required Field for Client

Create / Update Client is not accepted by the Aggregation Manager.

Code 400; The [field name] is required.

AEV-001-018

1.6

Missing a Required Field for Employee

Create / Update Employee is not accepted by the Aggregation Manager.

Code 400; The [field name] is required.

AEV-001-019

1.6

Missing a Required Field for Visit

Create / Update Visit is not accepted by the Aggregation Manager.

Code 400; The [field name] is required.

Phase 1: Object-specific create and update scenarios

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

AEV-002-001

2

Create Client: Client ID already exists

Create Client is not accepted by the Aggregation Manager.

Code 403; Client already exists.

AEV-003-001

3

Update Client: Client Update Success

Update Client is accepted by the Aggregation Manager.

Code 204

AEV-003-002

3.1

Update Client: Client does not exist

Update Client is not accepted by the Aggregation Manager.

Code 403; Client with ID [client_identifier] does not exist.

AEV-003-003

3.2

Update Client: Client Update Failure

Update Client is not accepted by the Aggregation Manager.

Code 403; Client status cannot change from Valid to Incomplete.

AEV-004-001

4

Create Employee: Employee ID already exists

Create Employee is not accepted by the Aggregation Manager.

Code 403; Employee already exists.

AEV-005-001

5

Update Employee: Employee does not exist

Update Employee is not accepted by the Aggregation Manager.

Code 403; Employee with ID [employee_identifier] does not exist.

AEV-005-002

5.1

Update Employee: Employee Update Failure

Employee Update is not accepted by the Aggregation Manager.

Code 403; Employee status cannot change from Valid to Incomplete.

AEV-005-003

5.2

Update Employee: Employee Update Success

Employee update is accepted by the Aggregation Manager.

Code 204

AEV-006-001

6

Update Visit: GUID represents a Visit not in Incomplete status

Update Visit is not accepted by the Aggregation Manager.

Code 403; You can only update visits with the status “Incomplete”.

AEV-006-002

6.1

Create Visit: Client does not exist

Create Visit is not accepted by the Aggregation Manager.

Code 403; Client with identifier [client_identifier] does not exist.

AEV-006-003

6.2

Create Visit: Employee does not exist

Create Visit is not accepted by the Aggregation Manager.

Code 403; Employee with identifier [employee_identifier] does not exist.

AEV-007-001

7

Update Visit: Client does not exist

Update Visit is not accepted by the Aggregation Manager.

Code 403; Client with identifier [client_identifier] does not exist.

AEV-007-002

7.1

Update Visit: Employee does not exist

The target object is not updated in the Aggregation Manager.

Code 403; Employee with identifier [employee_identifier] does not exist.

Phase 2 scenarios

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

AEV-008-001

8

General Phase 2: Incomplete Client

The object is created in the Aggregation Manager in a status of Incomplete.

Client is created in a status of Incomplete.

AEV-008-002

8.1

General Phase 2: Incomplete Employee

The object is created in the Aggregation Manager in a status of Incomplete.

Employee is created in a status of Incomplete.

AEV-008-003

8.2

General Phase 2: Incomplete Visit

The object is created in the Aggregation Manager in a status of Incomplete.

Visit is created in a status of Incomplete.

AEV-009-001

9

Create Client Phase 2: Happy Path Client

The Client is created successfully in the Aggregation Manager.

Client record is in a Valid status in the Aggregation Manager.

AEV-010-001

10

Update Client Phase 2: Address an Incomplete Client

The Client is created successfully in the Aggregation Manager.

Client record is in a Valid status in the Aggregation Manager.

AEV-010-002

10.1

Update Client Phase 2: Update Client

The Client is updated in the Aggregator.

Target fields on Valid Client record are updated.

AEV-011-001

11

Create Employee Phase 2: Happy Path Employee

The Employee is created successfully in the Aggregation Manager.

Employee record is in a Valid status in the Aggregation Manager.

AEV-012-001

12

Update Employee Phase 2: Address an Incomplete Employee

The Employee is created successfully in the Aggregation Manager.

Employee record is in a Valid status in the Aggregation Manager.

AEV-012-002

12.1

Update Employee Phase 2: Update Employee

The Employee is updated in the Aggregator.

Target fields on Valid Employee are updated.

AEV-013-001

13

Create Visit Phase 2: Happy Path New Visit

The New Visit is created successfully in the Aggregator; Visit has a status of Received.

Visit is in a status of Received.

AEV-013-002

13.1

Create Visit Phase 2: Happy Path Updated Visit

Updated Visit is created successfully in the Aggregator; Visit has a status of Received.

Visit is in a status of Received.

AEV-014-001

14

Update Visit Phase 2: Address an Incomplete Visit

The New Visit is created successfully in the Aggregator; Visit has a status of Received.

Visit is in a status of Received.

AEV-014-002

14.1

Update Visit Phase 2: Update a Valid Visit

New Visit is created successfully in the Aggregator; Visit has a status of Received.

Visit is in a status of Received.

Phase 3 scenarios

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

Test Case ID

Use Case

Scenario

Expected result

Post-condition / response

AEV-015-001

15

Create Visit Phase 3: Happy Path

The Visit in the Aggregation Manager has an Aggregation Result of Success; Visit has a status of Received.

The Visit in the Aggregation Manager has an Aggregation Result of Success.

AEV-015-002

15.1

Create Visit Phase 3: Validation Failure

The Visit in the Aggregation Manager has an Aggregation Result of Failure and an Aggregation Result Description with all failure reasons.

Aggregation Result of Failure and Aggregation Result Description includes all failure reasons.

AEV-016-001

16

Update/Cancel Visit Phase 3: Happy Path

The Visit in the Aggregation Manager has an Aggregation Result and Description; Visit has a status of Submitted.

Update visits: Success result and Success description. Cancel visits: None result and “Not applicable for Cancelled Visits” description.

AEV-016-002

16.1

Update/Cancel Visit Phase 3: Validation Failure

The Visit in the Aggregation Manager has an Aggregation Result and Result Description including all available failure reasons; Visit has a status of Submitted.

Update visits: Failure result with detailed failure reasons. Cancel visits: None result and “Not applicable for Cancelled Visits” description.

Execution guidance for vendors

  1. Confirm access to the Aggregator API and that the vendor user has the required permissions for client, employee, and visit create/update transactions.

  2. Execute each test case using the scenario scope and expected response listed above.

  3. Record the successful client, employee, or visit element ID for each scenario in the Vendor Test Case Checklist PDF.

  4. Review the checklist for completeness and accuracy before submitting.

  5. Attach the completed checklist to the active vendor onboarding Zendesk ticket for Aggregator team review.

Important: Production credential distribution should not proceed until the Aggregator team has reviewed and accepted the completed vendor checklist.