Skip to main content

myEvolv NX 11.0.0050.01 Acceptance Tests


ECS-55618 Summary | Details
Place of Service Code and Calculate Rate
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • AR Management
  • Billing Batch Management 2.0 Form Set
  • Billing Batches Management
  • Billing Place of Service Code Setup [EDIT]
  • BillingProcessHistory
  • Cash Receipts for Remittance
  • Claim 2.0 [EDIT]
  • Claim Output
  • Claim Output Form Set
  • Claim Output Ready
  • Claim Service Lines NX Subform
  • Claim Submission 2.0 [EDIT]
  • Claim/Invoice Batch [VIEW]
  • Claims Maintenance NX Form Set
  • Claims Submission For Remittance NX [EDIT]
  • FinanceClaims
  • Location Table (Service)
  • Place of Service Location Link Subform
  • Notepad
Scenario 1: Validate Place of Service Updates After Changes To Finance Setup
Specific Setup:
  • Client has two Benefit Assignments.
  • Service is billable to both Benefit Assignments.
  • Service has Location information.
Steps
  1. Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
  2. Create a "Billing Run" to capture "Service" from preconditions.
  3. Upon completion of "Billing Execution Interval", create "837 File".
  4. Validate "Place of Service" information is present for the "Claim".
  5. Mark "Batch" as sent.
  6. Navigate to "Finance > Remittance Processing > Remittance Application > Apply Receipt to Claims".
  7. Select "Check".
  8. Set "Filters" to search on "Claim".
  9. Click "Deny" and "Add Action".
  10. Select "Resubmit to Other" and use "Calculate Rate", save.
  11. Upon completion of "Billing Execution Interval", click on "Submission" and "Batch", create "837 File".
  12. Validate "Place of Service" information is present for the "Claim".
Scenario 2: Validate Place Of Service Code Saves When Using Calculate Rate
Specific Setup:

Requires a service that was billed and "Location/Place of Service" was changed after billing.

Steps
  1. Navigate to "Finance > Remittance Processing > Remittance Application > AR Management".
  2. Select desired "Remittance".
  3. Set parameters to search for desired claim.
  4. Click "Add Action".
  5. "Resubmit" the claim using "Calculate Rate".
  6. Validate "Place of Service" field contains desired place of service code.
  7. Save.
  8. Wait for billing to run.
  9. Open the new submission.
  10. Validate "Place of Service" contains desired place of service code.
  11. Click on the "Batch" link.
  12. Click "Open Batch"
  13. Click on "Create Output".
  14. Download the "837 Output".
  15. Validate the "CLM" line contains desired place of service code.

Topics
• Finance • Finance Setup
ECS-56968 Summary | Details
New Referral/Client Wizard
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Search
  • Merge Utility
  • People Search
  • Person Information [ADD]
  • Wizard
  • Referral Search
Scenario 1: Validate Cannot Create New Client With Duplicate Social Security Number to Another Client
Specific Setup:

Known social security number for a Client in the system.

Steps
  1. Navigate to "Client > Client Information > Personal Information > Demographics".
  2. Click the "Select Client" search box.
  3. Click New and Intake - New.
  4. Enter any Last Name, First Name, Gender.
  5. Enter a Social Security number you know is in use already (do not use blank or all zeros).
  6. Click Proceed.
  7. Confirm that the search includes the client that has the SSN you entered listed.
  8. Check "Create new record..." box and click Proceed.
  9. Confirm that an alert opens showing
  10. Error(s) occurred on save:
  11. New Person record cannot be saved, return to search to address:
  12. Duplicate Social Security #: [SSN ENTERED]
  13. Close alert and Confirm that the Results window is still active (not locked, does not proceed).
  14. Click Previous to return to the Search page.
  15. Enter a valid SSN and client info.
  16. Click Proceed.
  17. Check "Create new record..." box and click Proceed.
  18. Confirm the Wizard continues to the Personal Information page with the new information without validations.
Scenario 2: Validate Cannot Create New Referral With Duplicate Social Security Number to Another People Record
Specific Setup:

Known social security number for a People Record in the system.

Steps
  1. Navigate to "Referral > Agency Referral > Referral Information > Demographics".
  2. Click Search for Referrals.
  3. Click New Referrals Wizard.
  4. Enter any Last Name, First Name, Gender.
  5. Enter a Social Security number you know is in use already (not blank or all 0s, these are ignored).
  6. Click Proceed.
  7. Confirm that the search includes the client that has the SSN you entered listed.
  8. Check "Create new record..." box and click Proceed.
  9. Confirm that an alert opens showing
  10. Error(s) occurred on save:
  11. New Person record cannot be saved, return to search to address errors:
  12. Duplicate Social Security #: [SSN ENTERED]
  13. Close alert and Confirm that the Results window is still active (not locked, does not proceed).
  14. Click Previous to return to the Search page.
  15. Enter a valid SSN and client info.
  16. Click Proceed.
  17. Check "Create new record..." box and click Proceed.
  18. Confirm the Wizard continues to the Personal Information page with the new information without errors.

Topics
• Client • Referral Application
ECS-57378 Summary | Details
Uploading via Client Information Screen
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Information Screen Form Set
  • Client Search
  • FrontDeskCheckIn
  • My Client Information Form Set
  • Personal Information - All Form Set
  • Placement Disruptions: Unknown Location [ADD]
  • Select File for Upload
Scenario 1: Validate Document Can Be Uploaded via Client Information Screen
Specific Setup:
  • Three different clients must be used for testing, one for each location:
  • My Client Widget
  • Client Module Header
  • Front Desk
  • Event service form available with upload document, image upload, signature capture.
  • Available Client scheduled event in Front Desk.
Steps
  1. Navigate to "Taskbar > My Homeview > Homeview Launcher > Homeview".
  2. Select My Clients widget.
  3. Click the Open Client Formset (red box and arrow) for desired Client.
  4. Navigate to desired event form.
  5. Add new event form.
  6. Click "Click to Upload Document" > Upload File.
  7. Select a file and upload.
  8. Validate file is uploaded.
  9. Validate Event Form window is still displaying.
  10. Close and Navigate to "Client > Client Information > Personal Information > Demographics".
  11. Search for a different client.
  12. Click the Client name in the header.
  13. Navigate to desired event form.
  14. Add new event form.
  15. Click "Click to Upload Document" > Upload File.
  16. Select a file and upload.
  17. Validate file is uploaded.
  18. Validate Event Form window is still displaying.
  19. Close and Navigate to "Taskbar > Attendance Check In/Out > Check In/Out > Front Desk NX".
  20. Click the Client name in the scheduled event.
  21. Navigate to desired event form.
  22. Add new event form.
  23. Click "Click to Upload Document" > Upload File.
  24. Select a file and upload.
  25. Validate file is uploaded.
  26. Validate Event Form window is still displaying.
Scenario 2: Validate Image Can Be Uploaded via Client Information Screen
Specific Setup:
  • Three different clients must be used for testing, one for each location:
  • My Client Widget
  • Client Module Header
  • Front Desk
  • Event service form available with upload document, image upload, signature capture.
  • Available Client scheduled event in Front Desk.
Steps
  1. Navigate to "Taskbar > My Homeview > Homeview Launcher > Homeview".
  2. Select My Clients widget.
  3. Click the Open Client Formset (red box and arrow) for desired Client.
  4. Navigate to desired event form.
  5. Add new event form.
  6. Click "Click to Upload Image" > Upload File.
  7. Select a file and upload.
  8. Validate file is uploaded.
  9. Validate Event Form window is still displaying.
  10. Close and Navigate to "Client > Client Information > Personal Information > Demographics".
  11. Search for a different client.
  12. Click the Client name in the header.
  13. Navigate to desired event form.
  14. Add new event form.
  15. Click "Click to Upload Document" > Upload File.
  16. Select a file and upload.
  17. Validate file is uploaded.
  18. Validate Event Form window is still displaying.
  19. Close and Navigate to "Taskbar > Attendance Check In/Out > Check In/Out > Front Desk NX".
  20. Click the Client name in the scheduled event.
  21. Navigate to desired event form.
  22. Add new event form.
  23. Click "Click to Upload Document" > Upload File.
  24. Select a file and upload.
  25. Validate file is uploaded.
  26. Validate Event Form window is still displaying.
Scenario 3: Validate Signature Can Be Uploaded via Client Information Screen
Specific Setup:
  • Three different clients must be used for testing, one for each location:
  • My Client Widget
  • Client Module Header
  • Front Desk
  • Event service form available with upload document, image upload, signature capture.
  • Available Client scheduled event in Front Desk.
Steps
  1. Navigate to "Taskbar > My Homeview > Homeview Launcher > Homeview".
  2. Select My Clients widget.
  3. Click the Open Client Formset (red box and arrow) for desired Client.
  4. Navigate to desired event form.
  5. Add new event form.
  6. Click "Click to Upload Image" > Upload File.
  7. Select a file and upload.
  8. Validate file is uploaded.
  9. Validate Event Form window is still displaying.
  10. Close and Navigate to "Client > Client Information > Personal Information > Demographics".
  11. Search for a different client.
  12. Click the Client name in the header.
  13. Navigate to desired event form.
  14. Add new event form.
  15. Click "Click to Upload Document" > Upload File.
  16. Select a file and upload.
  17. Validate file is uploaded.
  18. Validate Event Form window is still displaying.
  19. Close and Navigate to "Taskbar > Attendance Check In/Out > Check In/Out > Front Desk NX".
  20. Click the Client name in the scheduled event.
  21. Navigate to desired event form.
  22. Add new event form.
  23. Click "Click to Upload Document" > Upload File.
  24. Select a file and upload.
  25. Validate file is uploaded.
  26. Validate Event Form window is still displaying.

Topics
• Client
ECS-57833 Summary | Details
Import Forms Containing Test/Assessment(s)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Look-up Tables Listing (filtered)
  • Columns Pick List NX
  • Form Families
  • FormDesigner
  • Forms
  • Interface Design Form Set
  • NX FIELD [EDIT]
  • NX Sub Form [ADD]
  • NX Test [EDIT]
  • Sub Reports for Users - All
  • Test Header Setup Lookup
  • FileUploadForm
Scenario 1: Form Designer: Validate Form Export Operations
Specific Setup:

The following User-Defined elements must be created in order to be added to a Form: Look-Up Table, Domain & Test, SubReport, and SubForm.

Steps
  1. Navigate to "Setup > User Tools > Interface Designer > Form Designer".
  2. Select desired "Form Family".
  3. Select desired System Form.
  4. Validate the "Export" option is not present under the "Actions" menu.
  5. Select "Copy" from the "Actions" menu.
  6. Set desired "Form Name" and "Form Code".
  7. Add desired "Form Elements".
  8. Fill out required fields for each "Form Elements".
  9. Click "Save".
  10. Validate saving was successful.
  11. Select "Export" from the "Actions" menu on the custom "Form".
  12. Validate a JSON file was created.
Scenario 2: Validate Importing an In Use Test Code Into Form Designer Displays Duplication Error
Specific Setup:

Available UDF form to export from Form Designer.

Steps
  1. Navigate to "Setup > User Tools > Interface Design > Form Designer".
  2. Select a Form Family.
  3. Export a UDF form.
  4. Navigate to "Setup > User Tools > Interface Design > Import Forms".
  5. Upload the exported file.
  6. Validate "Following Test code(s) in file FormExport.json already exists and in use. Please enter a new test code and try again..." error message.
  7. Validate "Form already exists in system:..." error message.
Scenario 3: Validate Ability To Import Forms With Test/Assessments
Specific Setup:

4 forms available to import:

  • Existing form with existing test/assessment that is not in use.
  • Existing form with existing test/assessment that is in use.
  • New form without a test/assessment.
  • New form with a new test assessment.
Steps
  1. Navigate to "Setup > User Tools > Interface Design > Import Forms".
  2. Import each type form.
  3. For existing form with existing test/assessment that is not in use:
  4. Validate "Form already exists in system:..."
  5. For existing form with existing test/assessment that is in use:
  6. Validate "Following Test code(s) in file ... already exists and in use. Please enter a new test code and try again".
  7. Validate "Form already exists in system:..."
  8. For new form without a test/assessment:
  9. Validate successful upload of form.
  10. For new form with a new test assessment:
  11. Validate successful upload of form and test/assessment.

Topics
• Forms • Setup
ECS-57869 Summary | Details
LA IBHIS Outpatient Episodes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission Necessity Code
  • AXIS IV (Psychosocial and Environmental Problems) [ADD]
  • Client Search
  • Conservator Court Status
  • Critical Information
  • Diagnosis - (Axis IV problems)
  • LA County Client Information [EDIT]
  • Level of Hold
  • Placement Events by Agency/Program - People2
  • Program Enrollment [Edit]
  • Program Enrollment From Service Track [ADD]
  • Program Listing By Agency and Worker
  • Program Setup - No Care Day/Respite [EDIT]
  • Provider Sites by Program (Vacancy)
  • Source Of Admission
  • Staff - Service Providers (Caseloads - Zip Zones)
  • Type of Admission
  • Worker Role (to a client or in a workgroup) Table
  • Yes No Unknown Table
  • Diagnosis General - LA DMH SF Subform
  • Diagnosis Search Service
  • Diagnosis Status
  • Primary Diagnosis for a Person (by People_ID)
  • Priority Table
  • Staff - All (by Staff ID)
  • Type of Diagnosis
  • Type Of Discharge
Scenario 1: LA IBHIS - Allow Outpatient Episodes To Be Opened With Multiple Legal Entities
Specific Setup:
  • A client will exist that has all the needed information filled in to Admit into the LA IBHIS System.
  • At least two outpatient programs assigned to the IBHIS code of "00543" in the myEvolv System. In this example they will be the "Outpatient Program1" and "Outpatient Program2".
  • At least one outpatient program assigned to the IBHIS code of "01946" in the myEvolv System. In this example this will be "Outpatient Program3".
  • At least one inpatient program assigned to the IBHIS code of "00543" in the myEvolv System. In this example it will be "Inpatient Program1".
  • An enrollment record is created for an outpatient program, "Outpatient Program1". This client has not been admitted into the IBHIS System.
Steps
  1. Navigate to the " LA County Client Information" form.
  2. Validate the enrollment record in the precondition displays in the "IBHIS Related Program Enrollments on Record" SubReport. In this example "Outpatient Program1".
  3. Validate there is no episode attached to the record.
  4. Navigate to the IBHIS System.
  5. Admit the client.
  6. Validate an episode number is generated, In this example it will be "1".
  7. Refresh the myEvolv form.
  8. Validate the episode displays on the "IBHIS Related Program Enrollments on Record" SubReport. This will be on the "Outpatient Program1" record.
  9. Enroll the client into the third outpatient program, assigned to "01946". In this example this will be "Outpatient Program3".
  10. Admit the client into the IBHIS system.
  11. Validate this program has the next episode number assigned. In this example it will be "2".
  12. Refresh the myEvolv Form.
  13. Validate the sub report is updated with the correct episode number.
  14. Add a 3rd enrollment record to a third outpatient program, assigned to "00543". In this example it will be "Outpatient Prorgram2".
  15. Admit the client to this program in the "IBHIS" system.
  16. Validate the episode number is the same episode as in the first program. In this example it will be "1". In this example "Outpatient Program2" and "Outpatient Program1" will have the same episode number.
  17. Refresh the myEvolv Form.
  18. Validate the episode number is updated with the correct episode number.
  19. Add an inpatient program enrollment record to IBHIS Code "0543". In this example "Inpatient Program1".
  20. Admit the client to the IBHIS System.
  21. Validate the episode number is the next incremented value. In this example "3".
  22. Refresh the myEvolv Form.
  23. Validate the episode number is updated with the correct episode number.
Scenario 2: LA IBHIS - Validate Diagnosis Functions With Multiple Episodes
Specific Setup:
  • A client will exist that is enrolled in at least three episodes, At least one inpatient episode and 1 outpatient episode will exist.
  • One of the episodes will be for a program code of "00543" in the myEvolv system, the other "01946".
  • The diagnosis will occur after the start dates of the episodes.
Steps
  1. Navigate to the "LA County Information" form.
  2. Validate the Diagnosis in the precondition exists on the form.
  3. Access the link for sending data to LA County.
  4. Select the first episode.
  5. Validate the "Evolv Diagnosis Information" displays the diagnosis from the precondition.
  6. Validate the "LA County Diagnosis Returned By GetClientDiagnosis" displays "No records to display".
  7. Select the "Create Client Diagnosis".
  8. Wait for the process to complete.
  9. Validate the "LA County Diagnosis Returned By GetClientDiagnosis" contains the same information as the "Evolv Diagnosis Information".
  10. Redo the above steps with each episode.
  11. Validate the information is updated in the "LA County Diagnosis Returned By GetClientDiagnosis" section.
Scenario 3: LA IBHIS - Validate Discharging and Enrolling Creates A New Episode
Specific Setup:
  • A client exists that has multiple programs in the same episode.
  • The same client has other episodes that exist for other programs.
Steps
  1. Navigate to the "Enrollment" form.
  2. Discharge the client from the 2 programs that share the same episode.
  3. Set the discharge date to an earlier date and time then the current date.
  4. Fill in the required fields for the IBHIS system, in myEvolv, that need to be filled in.
  5. Navigate to the IBHIS system.
  6. Select the episode and discharge the client.
  7. Validate the myEvolv system shows the two programs that shared the episode as discharged.
  8. Create a new enrollment record for a program that the client was discharged from.
  9. Set the enrollment date after the discharge date above.
  10. Validate the myEvolv SubForm shows no episode on that program.
  11. Enter the IBHIS system and admit the client.
  12. Validate the episode is the next incremental value on the list.
  13. Validate the episode number is not duplicated for this enrollment.

Topics
• LA IBHIS
ECS-58066 Summary | Details
Address Overwrite on Claim Output
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Claim 2.0 [EDIT]
  • Claim Output Ready
  • Claim Receivers Setup Form Set
  • Claim/Invoice Batch [VIEW]
  • FinanceClaims
  • Notepad
  • Payor-Facility License Link [EDIT]
  • Payor-Facility License Link Subform
  • Receiver Information - All
  • Receiver Information X12 Submissions [EDIT]
  • Service Facilities Listing
  • Service Facility [EDIT]
Scenario 1: Validate Payer License Address Overwrite On Service Facility Outputs On 837 Claim Output
Specific Setup:

Requires a billing run with at least one claim that is set to output "837P".

Steps
  1. Navigate to "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup X12".
  2. Select desired "Receiver".
  3. Check the flag "Output Service Facility in 837 as Service Facility".
  4. Save.
  5. Navigate to "Agency > Service Locations > Sites/Residentials > General Information".
  6. Select desired "Facility".
  7. Navigate to "Licensing Info".
  8. Add desired "Payer Specific Information" in the SubForm.
  9. Expand the SubForm for to add an "Overwrite Address".
  10. Validate "Do not Output as Rendering Provider" is not checked.
  11. Save.
  12. Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
  13. Select desired "Billing Run".
  14. Open the billing run to generate the output.
  15. Validate NM1*77 row contains desired "Facility".
  16. Validate N3 and N4 row contain the overwrite address.
  17. Navigate to "Agency > Service Locations > Sites/Residentials > General Information".
  18. Select desired "Facility".
  19. Navigate to "Licensing Info".
  20. Check the flag "Do not Output as Rendering Provider".
  21. Save.
  22. Repeat steps 12-14.
  23. Validate NM1*77 row contains desired "Facility".
  24. Validate N3 and N4 row contain the overwrite address.

Topics
• Agency • Finance
ECS-58068 Summary | Details
Collection Type
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • AR Management
  • Claims Maintenance NX Form Set
Scenario 1: Submission Balance and Expected Amount - Collection
Specific Setup:
  • Collection Submitter and Receiver are configured.
  • Collections Processing is configured within the Self Pay Plan.
  • Collection billing batch must be marked as sent.
  • User has access to Finance module.
Steps
  1. Navigate to "Finance > Remittance Processing > Remittance Application > AR Management".
  2. Click on the "View Filters" button.
  3. Within the Search Parameters, check off the "Show Claims Flagged for Collections" and "Include No Remit Claims" fields.
  4. Click on the "Search" button.
  5. On desired claim, click on the "Add Action" link.
  6. Within the "Action" field, select "Resubmit to CCU".
  7. Set the "Amount Type" to "Remaining Balance".
  8. Set the desired "Transaction Month", and click "Save".
  9. Navigate to "Finance > Claim Maintenance > Automatic > Submissions".
  10. Enter the claim for the resubmit that was just performed.
  11. For the collection submission, validate the "Claim Submission Balance" matches the same amount displayed within the "Amount Expected" field.

Topics
• Finance
ECS-58253 Summary | Details
270 Eligibility Files
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • 270 Output File
  • 270 Output Ready
  • Billing Batch Claims Review
  • Billing Batches Management
  • Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management
  • Finance > Imports/Exports > Exports > Eligibility Requests (270)
  • Claim Receivers Setup Form Set
  • EligibilityManager
  • Receiver Information - All
  • Receiver Information 270-271 Setup [EDIT]
Scenario 1: Send 270 to RevConnect From Billing Run
Specific Setup:

Claim receiver "Output 270 in 5010 format" enabled under "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".

Steps
  1. Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
  2. Filter for desired Receiver.
  3. Take note of "Run Description".
  4. Click Actions > Request Eligibility (270).
  5. Download the file.
  6. Validate the output has single file and has "5010" in the code.
  7. Validate the output does not have "4010" in the code.
  8. Click Send to RevConnect.
  9. Validate "270 submitted to SFTP" message.
  10. Click the Claims link.
  11. Click "Request Eligibility (270)".
  12. Download the file.
  13. Validate the output has single file and has "5010" in the code.
  14. Validate the output does not have "4010" in the code.
  15. Click Send to RevConnect.
  16. Validate "270 submitted to SFTP" message.
  17. Navigate to "Finance > Imports/Exports > Exports > Eligibility Requests (270)".
  18. Validate Description cell matches step 3.
  19. Validate Status "File Sent".
Scenario 2: Validate 270 Output File Honors "Output 270 in 5010 format" Option
Specific Setup:

Available Claim receiver to edit under "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".

Steps
  1. Navigate to "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".
  2. Select a receiver and enable:
  3. Break File on Max Clients
  4. Break File on new Provider
  5. Output 270 in 5010 format.
  6. Click Save.
  7. Navigate to "Finance > Imports/Exports > Exports > Eligibility Requests (270)".
  8. Find/create request 270 file with receiver from step 2.
  9. Select "Generate Output File".
  10. Validate the output zip has multiple files and they all have "5010" present in output file.
  11. Validate "4010" is not present in output file.
  12. Navigate to "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".
  13. Select same receiver and disable:
  14. Break File on Max Clients
  15. Break File on new Provider
  16. Output 270 in 5010 format.
  17. Click Save.
  18. Navigate to Finance > Imports/Exports > Exports > Eligibility Requests (270)
  19. Select "Generate Output File" for the same 270.
  20. Validate the output has single file and has "4010" present in file.

Topics
• Finance • Finance Setup
ECS-58373 Summary | Details
835 Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Claims Maintenance NX Form Set
  • Finance File Import
  • FinanceImportListing
  • Report: Claim Details Report
  • Report: Claim Remittance Report
Scenario 1: Validate Remittance Upload With CAS Info In Service Line
Specific Setup:

An 835 file that includes CAS information at service line level for single service line claim(s).

Steps
  1. Navigate to "Finance > Imports/Exports > Imports > Remittance Imports".
  2. Upload 835 file.
  3. Validate that the CAS information has been applied to the claim.
Topics
• Finance

myEvolv_NX_11.0.0050.01_Details.csv