PL0019 - CGIS VLP.pdf

South Carolina Department of Health and Human Services

(SCDHHS)

Member Management Replacement Program (MMRP)

Health Care Reform (HCR) and

Cúram Global Income Support (CGIS) Integration

Approach Document (AD)

CGIS Verify Lawful Presence (VLP)

CGIS Changes for CGIS AD MMRP Verify Lawful Presence AD V2.0

Version Log

The Version Log maintains a record of the changes made to the document during its life cycle.

Whole number versions are reserved to designate that the document has reached an Approved status. Changes/Revisions made to approved documents will continue with decimals numbers, until the document again reaches an Approved status.

Version Date Drafted by Role Description of Change v0.1 12/19/2019 Tiffany Ortega IBM Functional Consultant

Initial draft.

v0.2 1/29/2020 Ramy Kalioby IBM Functional Consultant

Second draft

V0.3 2/26/2020 Ramy Kalioby IBM Functional Consultant

Third draft

V0.4 3/13/2020 Tiffany Ortega IBM BA Lead Functional Requirement updates

V0.5 3/20/2020 Ramy Kalioby IBM Functional Consultant

Use Cases updates Narrative Flow updates

V0.6 3/27/2020 Ramy Kalioby IBM Functional Consultant

TDS updates

V0.7 4/17/2020 Ramy Kalioby IBM Functional Consultant

Review updates

V0.8 5/1/2020 Ramy Kalioby IBM Functional Consultant

Review updates

V0.9 5/15/2020 Ramy Kalioby IBM Functional Consultant

Review updates Screenshots to OLV design; task templates

V0.10 06/14/2020 Ashish Lirani IBM developer TDS updates for all the sections including new Sequence Diagram in section 6.2 (6 new diagrams) Section 6.2.7 Code tables, DMX, Façade, Service layer, UIM Configuration, Java Classes.

V0.11 6/21/2020 Ramy Kalioby IBM Functional Consultant

Updated:

Formatting Task Templates

INT_VLP_REQ_3.1

INT_VLP_REQ_3.2.

Removed:

INT_VLP_REQ_3.5

Added:

INT_VLP_REQ_11

V0.12 7/1/2020 Ramy Kalioby IBM Functional Consultant

Updated:

Outstanding comments

1.7 Assumptions

Sec 2 Flow Narrative

INT_VLP_REQ_1.2

INT_VLP_REQ_1.3

INT_VLP_REQ_2.1

INT_VLP_REQ_3.9

INT_VLP_REQ_4.1

INT_VLP_REQ_4.2

INT_VLP_REQ_5

Use Case 5.6 Use Case 5.7

V0.13 7/8/2020 Tiffany Ortega IBM BA Lead Updated the hierarchy of the work queues in the Conceptual Flow Narratives. Updated

INT_VLP_REQ_3.9.

V0.14 7/10/2020 Ramy Kalioby IBM Functional Consultant

Updated requirement INT_VLP_REQ_3.9 per OnBase

V0.15 7/14/2020 Ramy Kalioby IBM Functional Consultant

INT_VLP_REQ_3.9 updated per 7/13 meeting

V0.16 7/22/2020 Ramy Kalioby IBM Functional Consultant

Spell Check updates in prep for Final Review.

V0.17 7/31/2020 Tiffany Ortega IBM BA Lead Updated the following items per

CR258:

2.8 Modified Flow – CGIS Guided

Change Wizard

2.8.1 Modified Flow

INT_VLP_REQ_1.3

VLP_UC_05

V1.0 8/5/2020 Erin Coleman SCDHHS MMRP Process & Artifact Development Manager

Updated watermark and version number to reflect approval date, removed all comments, and accepted track changes.

V1.1 10/26/2020 Elena Fiske IBM Business Analyst Updated INT_VLP_REQ_4 for

CR291

V1.2 12/10/2020 Tiffany Ortega IBM BA Lead Updated the tasks in 4.2 Task Templates per CR317. The following tasks were marked as invalid:

2. Task: Eligibility Statement

Code of 37

The Review Logs maintains a record of the State personnel that performed reviews leading up to the document reaching an Approved status. These reviews do not represent final approval of the document. The Approvals are recorded in the Approval Log Section.

Functional Review Log

The Functional Review Log maintains a record of the State personnel that performed the review of the functional design, confirming the understanding of the design. That the design meets the requirements, business requirements as described and is testable.

SCDHHS Role First Review / Review Name

Second Review / Reviewer Name

Third Review / Reviewer Name

DDI Manager 4/6/2020

Product Manager 4/7/2020

Technical Lead 4/7/2020 Renjan Bhasi

4/23/2020 Renjan Bhasi

6/4/2020 Renjan Bhasi

Business Analyst Upendra K. – 4/6/20

UAT Lead

Process & Artifact Development Manager

4/3/2020 Erin Coleman

4/22/2020 Erin Coleman

6/2/2020 Erin Coleman

6/30/2020 Erin Coleman FDS Review

Technical Review Log

The Technical Review Log maintains a record of the State personnel that performed the review of the technical design, confirming the technical approach appropriately addresses the functional design.

6. Task: VLP Step 1 has response code ESC 40

8. Task: VLP Step 1 or 1a response has ESC 32

V2.0 4/11/2021 Erin Coleman SCDHHS MMRP Process & Artifact Development Manager

Updated watermark and version number to reflect approval date, removed all comments, and accepted track changes.

SCDHHS Role First Review / Review Name

Second Review / Reviewer Name

Third Review / Reviewer Name

Technical Lead 5/14/2020 Renjan Bhasi R2 review

IBM Approval Review Log

The IBM Approval Review Log captures that the AD and the Functional and Technical Design

Sections have been reviewed by the IBM team. The documented design, functional and technical components are understood as documented and can be validated through the Use Cases defined.

This signifies that the section/document is ready for SC review and Approval.

Functional Design Section

Technical Design Section

IBM Technical Design Approval Review – v2.0

Role Name Date Comments

CGIS Development Lead Vijay Mujumdar 3/25/2021 Approved v1.2 to v2.0

CGIS Development Team Lead

Pranav Kumar 3/25/2021 Approved v1.2 to v2.0

IBM Functional Design Approval Review – v2.0

CGIS Project Manager Courtney Stevens 3/25/2021 Approved v1.2 to v2.0

CGIS Development Lead Vijay Mujumdar 3/25/2021 Approved v1.2 to v2.0

CGIS BA Lead Tiffany Ortega 3/25/2021 Approved v1.2 to v2.0

CGIS Testing Lead Brian Grieves 3/25/2021 Approved v1.2 to v2.0

IBM Business Analyst Ramy Kalioby 3/25/2021 Approved v1.2 to v2.0

CGIS Development Team Lead

Pranav Kumar 3/25/2021 Approved v1.2 to v2.0

The Approvals Section captures the Approval of the current Approved Major version (whole number per PMP.) The approval tables will be copied to the Approval Appendix when changes are made that require a subsequent round of Approvals.

Approval Logs

Functional Design Section

The Functional Design Section captures the State personnel that reviewed and approved the functional design. Confirming that the design is understood, fulfills the requirements and is testable.

Functional Design Approval v2.0

Role Name Date Comments

SCDHHS Business Analyst

Upendra Koyagura 3/29/21 FDS Approved

SCDHHS Technical Lead

Renjan Bhasi

SCDHHS Product Manager

Abhishek Sahu 4/7/2021 Approved V1.2

SCDHHS DDI

Manager

Timothy Cozine 4/7/2021 Approved V1.2

SCDHHS Process & Artifact Development Manager

Erin Coleman 4/11/2021 Approved ADD

Technical Design Section

The Technical Design Section captures the State personnel that reviewed and approved the technical design. Confirming that the technical approach to fulfilling design is understood fulfills the requirements.

Technical Design Approval v2.0

SCDHHS Technical Lead Renjan Bhasi

Table of Contents

1 Introduction

1.1 Background

1.2 Purpose

1.3 Approach Focus

1.4 Related Documents

1.5 Definitions

1.6 Alignment Overview

1.7 Key Assumptions

1.8 HCR Dependency

2 Conceptual Flow

2.1 Modified Flow – CGIS Citizen Portal Application

2.1.1 Modified Flow Narrative

2.2 Modified Flow – CGIS Worker Portal Application

2.2.1 Modified Flow Narrative

2.3 Existing Flow – CGIS Integrated Case

2.4 Modified Flow – CGIS Integrated Case

2.4.1 Modified Flow Narrative

2.5 Existing Flow – CGIS Application

2.6 Modified Flow – CGIS Application

2.6.1 Modified Flow Narrative

2.7 Existing Flow – CGIS Guided Change Wizard

2.8 Modified Flow – CGIS Guided Change Wizard

2.8.1 Modified Flow Narrative

3 Requirements Realignment

3.1 Requirement Modifications

4 Function

4.1 CGIS Verify Lawful Presence

4.1.1 Design Description

4.1.2 Functional Output

4.1.3 Requirements Addressed

4.2 Task Templates

5 Use Cases

5.1 Citizen Portal Application

5.2 Worker Portal Application

5.3 CGIS Integrated Case

5.4 CGIS IS Application

5.5 CGIS Guided Change

6 Technical Design

6.1 Common Technical Artifacts

6.2 Technical Function

6.2.1 Sequence Diagram – Step 1 VLP Call from Citizen portal and Application Intake

6.2.2 Sequence Diagram – Step 1 VLP Call from COC upon Mark Complete Action .. 63

6.2.3 Sequence Diagram – Step 1 VLP Call from ACR Case Selection Batch

6.2.4 Diagram – Depiction of VLP Wizard flow when initiated from Interface Data Tab

6.2.5 Sequence Diagram – Request & Response processing for the VLP call

6.2.6 Sequence Diagram – Process response for Non-MAGI IC

6.2.7 Sequence Diagram – Process response for Non-MAGI IC

6.2.8 Code Tables

6.2.9 Code Table Details

6.2.10 DMX Table Details

6.2.11 Model

6.2.12 Façade

6.2.13 BPO Method Details

6.2.14 UIM Configuration Changes

6.2.15 Java Classes

6.2.16 IEG Script Changes N/A

6.3 Rules Development

6.4 Unit Testing Scenarios-N/A

6.4.1 Curam Unit Testing Scenarios

6.4.2 Batch Development N/A

7 Appendices

1 Introduction

1.1 Background

Incorporating the CGIS module into MMRP with the implementation focus to remain as close to

Out of the Box (OOTB) as possible, has led to some integration issues that need to be resolved.

There were no specific business requirements that are necessitating the changes, but rather systemic, processing or current MMRP enhancements that give rise to the misaligned circumstances or create conflicting requirements.

1.2 Purpose

The Approach Document describes the conditions that require a solution, to enable the CGIS and

HCR modules to perform similar functions. The Approach Document is used to document and align requirements between the current HCR requirements and the CGIS requirements.

Requirements will be documented from both modules/projects in order to ensure proper alignment and prevent the creation of conflicting requirements.

1.3 Approach Focus

The document covers the changes required in CGIS to add functionality for Verify Lawful

Presence (VLP) version 37 to align with HCR functionality implemented as part of PROD-5531 in Release 4.2.1 as outlined in MMRP CGIS VLP v37 CR100.

1.4 Related Documents

This section lists any key documents that might be helpful to understanding the functionality which are located on the state SharePoint site.

Document Name Location

HCR Production JIRA for VLP v37 https://devtools.scdhhs.gov/jira/browse/PROD-5531

PROD-5531 TDD FINAL

https://devtools.scdhhs.gov/jira/secure/attachment/636 47/PROD-5531_TDD_FINAL.docx

MMRP CGIS VLP v37 CR100 MMRP CGIS VLP v37 CR100

MMRP HCR31 VLP Interface in Cúram FDS v4.0

MMRP HCR31 VLP Interface in Cúram FDS v4.0

MMRP CGIS32 Online Verifications ADD MMRP CGIS32 Online Verifications ADD

CGIS27 Global Verifications Master Spreadsheet

CGIS27 Global Verifications Master Spreadsheet

MMRP HCR31 Verify Lawful Presence TDS V2.0

MMRP HCR31 VerifyLawfulPresence TDS V2.0 https://devtools.scdhhs.gov/jira/browse/PROD-5531 https://devtools.scdhhs.gov/jira/secure/attachment/63647/PROD-5531_TDD_FINAL.docx https://devtools.scdhhs.gov/jira/secure/attachment/63647/PROD-5531_TDD_FINAL.docx https://schhs.sharepoint.com/:w:/r/sites/1211207/CGIS%20Change%20Requests/MMRP%20CGIS%20VLP%20v37%20CR100.docx?d=w60928d3c67eb4556b6ce11c425b25782&csf=1&web=1&e=HCS9mj https://schhs.sharepoint.com/:w:/r/sites/1211207/Business%20Process%20Modeling%20Documents/HCR%20Tracks/Track%20HCR31%20-%20VLP%20Interface%20in%20Curam/Approved%20Documents/MMRP%20HCR31%20VLP%20Interface%20in%20Curam%20FDS%20V4.0.docx?d=w9e332f460d7b401f82bd46875aaea735&csf=1&e=J5Z2RH https://schhs.sharepoint.com/:w:/r/sites/1211207/CGIS%20Business%20Requirements%20and%20Design%20Documents/MMRP%20CGIS32%20Online%20Verifications%20ADD.docx?d=w27316ca85bfa464e8050c95b30020c5a&csf=1&e=quismc https://schhs.sharepoint.com/:x:/r/sites/1211207/CGIS%20Business%20Requirements%20and%20Design%20Documents/CGIS27%20Global%20Verifications%20Master.xlsx?d=wf9a1022972ae4b698ddeb3246f2ff440&csf=1&e=dM4muC https://schhs.sharepoint.com/:w:/r/sites/1211207/Business%20Process%20Modeling%20Documents/HCR%20Tracks/Track%20HCR31%20-%20VLP%20Interface%20in%20Curam/Approved%20Documents/MMRP%20HCR31%20VerifyLawfulPresence%20TDS%20V2.0.docx?d=wad8a452b75a445a29ff5b141659de15b&csf=1&web=1&e=MnKjJl

1.5 Definitions

Term Meaning

ACR Annual Case Review

AD Approach Document

API Application Programming Interface

BRD Business Requirements Document

CGIS Cúram Global Income Support

DHS Department of Homeland Security

DOB Date of Birth

DOD Date of Death

FDS Functional Design Specifications

FPL Federal Poverty Level

HCR Health Care Reform

IC Integrated Case

IEG Intelligence Evidence Gathering

MEDS Medicaid Eligibility Determination System

OOTB Out of the Box

PCAT Payment Category

TDS Technical Design Specifications

VLP Verify Lawful Presence

1.6 Alignment Overview

The alignment will cover the changes required in CGIS to add functionality for Verify Lawful

Presence (VLP) v37 to align with HCR functionality implemented as part of PROD-5531 in

Release 4.2.1 as outlined in MMRP CGIS VLP v37 CR100.

1.7 Key Assumptions

• Any enhancements to VLP functionality which will impact HCR will be completed as a

PROD enhancement by the O&M team. The scope of this document is to bring the existing functionality into CGIS.

• Any defects in the existing functionality will be resolved through the PROD defect process.

• Interface Data display for VLP will be per MMRP CGIS32 Online Verifications ADD.

The scope of this document is to utilize OLV functionality to display VLP responses.

• All user roles who can initiate other verification calls from the OLV screen should be able to trigger the VLP requests as well.

https://schhs.sharepoint.com/:w:/r/sites/1211207/CGIS%20Business%20Requirements%20and%20Design%20Documents/MMRP%20CGIS32%20Online%20Verifications%20ADD.docx?d=w27316ca85bfa464e8050c95b30020c5a&csf=1&e=quismc

• This design assumes the HCR equivalent of the tasks outlined are currently being created in Production. There are no clear requirements in PROD-5531 to indicate previous tasks from v33 being removed. The design was based on the CGIS team interpretation of the

PROD code w/ the help of O&M Resources. During testing some tasks may be found to be invalid and will be revisited at that time.

1.8 HCR Dependency

• VLP v37 functionality implemented as part of PROD-5531 in Release 4.2.1.

2 Conceptual Flow The flows captured within this section provide a high-level overview of the processes. Please refer to section 4 Function for detailed requirements.

2.1 Modified Flow – CGIS Citizen Portal Application

Figure 1 - Modified Process Flow – CGIS Citizen Portal Application

2.1.1 Modified Flow Narrative

Action # Action Label Narration

1 Launch IEG Script The user launches the Citizen Portal IEG Application script.

Existing Process

2 Start Application The user completes the Citizen Portal IEG Application script.

Existing Process

3 “Next” Selected on “Electronic Signature” Page

The user selects “Next” on the “Electronic Signature” page of the Citizen Portal IEG Application Script to submit the application.

Modified Process to Trigger VLP

4 Process VLP Request

The Hub sends and retrieves information related to the VLP request from DHS and sends the response to Cúram.

Existing Process

Action # Action Label Narration

5 Update the VLP section of Interface Data Tab

The results from the VLP request will be updated on the VLP section of Interface Data Tab.

6 Verification Successful?

Decision point to determine if the VLP response successfully verified the applicant’s Lawful Presence.

7 Create Applicable Tasks

If the verification request was not successful, applicable tasks will be created based on the response per the existing HCR design. The task will be sent to one of the VLP Work Queues below pending the requested coverage indicated on the application:

1. Non-MAGI Verify Lawful Presence (VLP) No LTC/OSS or TEFRA/BCCP indicated

2. LTC/OSS Verify Lawful Presence (VLP) LTC/OSS indicated

3. TEFRA/BCCP Verify Lawful Presence (VLP) TEFRA/BCCP indicated OR LTC/OSS and TEFRA/BCCP indicated

Modified Process to Use New Work Queue

8 Clear Citizenship

OV

If the verification request was successful, the system will clear the outstanding verification for Alien and Citizenship with “Verified by VLP” per the CGIS27 Global Verification Master Spreadsheet.

2.2 Modified Flow – CGIS Worker Portal Application

Figure 2 - Modified Process Flow – CGIS Worker Portal Application

2.2.1 Modified Flow Narrative

Launch IEG Script The user launches the Worker Portal IEG Application script.

Existing Process

1 Start Application The user completes the Worker Portal IEG Application script.

Existing Process

2 “Submit” Selected on “Client Rights & Responsibilities” Page

The user selects “Submit” on the “Client Rights & Responsibilities” page of the Worker Portal IEG Application Script to submit the application.

Modified Process to Trigger VLP

3 Process VLP Request

The Hub sends and retrieves information related to the VLP request from DHS and sends the response to Cúram.

Existing Process

4 Update the VLP section of Interface Data Tab

The results from the VLP request will be updated on the VLP section of Interface Data Tab of IC.

5 Verification Successful?

Decision point to determine if the VLP response successfully verified the applicant’s Lawful Presence.

6 Create Applicable Tasks

If the verification request was not successful, applicable tasks will be created based on the response per the existing HCR design. The task will be sent to one of the VLP Work Queues below pending the requested coverage indicated on the application:

1. Non-MAGI Verify Lawful Presence (VLP) No LTC/OSS or TEFRA/BCCP indicated

2. LTC/OSS Verify Lawful Presence (VLP) LTC/OSS indicated

3. TEFRA/BCCP Verify Lawful Presence (VLP)

7 Clear Citizenship

OV

outstanding verification for Citizenship with “Verified by VLP” per the CGIS27 Global Verification Master Spreadsheet.

2.3 Existing Flow – CGIS Integrated Case

Not Applicable

2.4 Modified Flow – CGIS Integrated Case

Figure 3 - Modified Process Flow – CGIS Integrated Case

2.4.1 Modified Flow Narrative

Action # Action Label Narration

Income Support IC The user opens the Income Support Integrated Case.

Existing Process

1 Select “Check Verify Lawful Presence (VLP)…” from the Interface Data screen

The user selects “Check Verify Lawful Presence (VLP)…” from the Interface Data tab on CGIS Integrated Case.

2 VLP Wizard is Displayed

The system displays the VLP Wizard (introduced by HCR).

Existing Process

3 Select Participant(s) and Select “Next”

The user selects the participant(s) for whom they would like to verify or reverify and select “Next” on the VLP Wizard to process request.

VLP wizard will display next step in VLP process for each participant.

Existing Process

4 Display Response on Results Page of VLP Wizard

The Hub system displays the verification response on the Results Page of the VLP Wizard.

Existing Process

5 Process VLP Request

The Hub sends and retrieves information related to the VLP request from DHS and sends the response to Cúram.

Existing Process

6 Update the VLP Interface Data Screen

The results from the VLP request will be updated on the Interface Data Screen.

7 Verification Successful?

Decision point to determine if the VLP response successfully verified the applicant’s Lawful Presence.

8 Create Applicable Tasks

If the verification request was not successful, applicable tasks will be created based on the response per the existing HCR design. The task will be sent to one of the VLP Work Queues below pending the requested coverage indicated on the application:

1. Non-MAGI Verify Lawful Presence (VLP) No LTC/OSS or TEFRA/BCCP indicated

2. LTC/OSS Verify Lawful Presence (VLP) LTC/OSS indicated

3. TEFRA/BCCP Verify Lawful Presence (VLP)

9 Clear Citizenship OVs

2.5 Existing Flow – CGIS Application

2.6 Modified Flow – CGIS Application

Figure 4 - Modified Process Flow – CGIS Application

2.6.1 Modified Flow Narrative

Action # Action Label Narration

Income Support Application

The user opens the Income Support Application.

Existing Process

1 Select “Check Verify Lawful Presence (VLP)…” from the Interface Data Screen

The user selects “Check Verify Lawful Presence (VLP)…” from the Interface Data Screen on the Income Support Application.

2 VLP Wizard is Displayed

The system displays the VLP Wizard (introduced by HCR).

Existing Process

3 Select Participant(s) and Select “Next”

The user selects the participant(s) for whom they would like to verify or reverify and select “Next” on the VLP Wizard.

VLP wizard will display next step in VLP process for each participant.

Existing Process

4 Display Response on Results Page of VLP Wizard

The Hub system displays the verification response on the Results Page of the VLP Wizard.

Existing Process

5 Process VLP Request

The Hub sends and retrieves information related to the VLP request from DHS and sends the response to Cúram.

Existing Process

6 Update the VLP section of Interface Data Screen

The results from the VLP request will be updated on the VLP section of Interface Data Screen.

7 Verification Successful?

Decision point to determine if the VLP response successfully verified the applicant’s Lawful Presence.

8 Create Applicable Tasks

If the verification request was not successful, applicable tasks will be created based on the response per the existing HCR design. The tasks will be in the Non-MAGI: Verify Lawful Presence Work Queue. The task will be sent to one of the VLP Work Queues below:

1. Non-MAGI Verify Lawful Presence (VLP) No LTC/OSS or TEFRA/BCCP indicated

2. LTC/OSS Verify Lawful Presence (VLP) LTC/OSS indicated

3. TEFRA/BCCP Verify Lawful Presence (VLP)

9 Clear Citizenship

OV

If the verification request was successful, the system will clear the

2.7 Existing Flow – CGIS Guided Change Wizard

2.8 Modified Flow – CGIS Guided Change Wizard

Figure 5 - Modified Process Flow – CGIS Guided Change

2.8.1 Modified Flow Narrative

Action # Action Label Narration

Income Support IC The user opens the Income Support Integrated Case.

Existing Process

1 Launch and Complete the Guided Change Wizard

The user launches and completes the Guided Change Wizard.

Existing Process

2 “Finish” Selected Guided Change Wizard

The user selects “Finish” on the Guided Wizard to submit the updates.

Modified Process to Trigger VLP

3 Process VLP Request

The Hub sends and retrieves information related to the VLP request from DHS and sends the response to Cúram.

Existing Process

4 Update the VLP section of Interface Data Screen

The results from the VLP request will be updated on the VLP section of Interface Data Screen.

5 Verification Successful?

Decision point to determine if the VLP response successfully verified the applicant’s Lawful Presence.

6 Create Applicable Tasks

If the verification request was not successful, applicable tasks will be created based on the response per the existing HCR design. The task will be sent to one of the VLP Work Queues below pending the requested coverage indicated on the application:

1. Non-MAGI Verify Lawful Presence (VLP) No LTC/OSS or TEFRA/BCCP indicated

2. LTC/OSS Verify Lawful Presence (VLP) LTC/OSS indicated

3. TEFRA/BCCP Verify Lawful Presence (VLP)

7 Clear Citizenship

OV

If the verification request was successful, the system will clear the

3 Requirements Realignment HCR or

CGIS

Source

Requirement

ID

Business Rule ID

Description System Feature

In Scope (Yes/N o)

HCR LP.1.0 The system must accommodate enhancements in the Cúram Worker Portal based on VLP v37 upgrade specifications.

VLP Yes

HCR LP.1.1 The system must accommodate enhancements in the Cúram Citizen Portal based on VLP v37 upgrade specifications.

VLP Yes

HCR LP.1.2 The citizenship status external evidence fields for VLP information must be re-designed to store the VLP response date.

Note: The SI must conduct the gap analysis to determine all necessary changes related to evidence storage/display.

VLP Yes

HCR LP.1.2.1 The system must store the grant date received from previous VLP response if subsequent step does not have a grant date. (Refer to BSD page 17).

VLP No

HCR LP.1.2.2 The system must display the grant date received from previous VLP response of subsequent step does not have a grant date. (Refer to BSD page

17).

VLP No

HCR LP.1.2.3 The system must store Y, N, P and X as Yes, No, Pending, and Not Applicable respectively in Cúram.

VLP No

HCR LP.1.2.4 The system must display Y, N, P, and X as Yes, No, Pending, and Not Applicable respectively in Cúram.

VLP No

HCR LP.1.2.5 The system must store the ‘AgencyAction’ response code and description on the external citizenship status evidence in Cúram.

VLP Yes

HCR LP.1.2.6 The system must display the ‘AgencyAction’ response code and description on the external citizenship status evidence in Cúram.

HCR LP.1.3 The system shall allow the worker portal user to trigger the VLP verification for a person on an application case or integrated case.

CGIS

Source

Requirement

ID

Business Rule ID

Description System Feature

In Scope (Yes/N o)

HCR LP.1.3.1 The system shall allow the worker portal user to trigger the VLP step 1 request for a person.

VLP Yes

HCR LP.1.3.2 The system shall allow the worker portal user to trigger the VLP step 1a request for a person.

VLP Yes

HCR LP.1.3.3 The system shall allow the worker portal user to trigger the VLP step 1b request for a person.

VLP Yes

HCR LP.1.3.4 The system shall allow the worker portal user to trigger the VLP step 2 request for a person.

VLP Yes

HCR LP.1.3.5 The system shall allow the worker portal user to trigger the VLP step 3 request for a person.

VLP Yes

HCR LP.1.3.6 The system shall allow the worker portal user to initiate and send a VLP request for document verification.

(Refer to the suspected counterfeit document verification process in the

BSD).

VLP Yes

HCR LP.1.4 The system shall allow a user on the worker portal to upload the verification document up to 5mb size for the VLP request step 3. (The acceptable file formats are .pdf, .jpg, .gif, and .png).

VLP Yes

HCR LP.1.4.1 The system shall allow a user on the worker portal to send the verification document up to 5mb size for the VLP step

3. (The acceptable file formats are .pdf, .jpg, .gif, and .png).

VLP Yes

HCR LP.1.5 The system shall initiate the VLP case closure process as per conditions defined in the BSD.

VLP No

HCR LP.1.6 The system must display the mandatory fields for the different document types on the supporting document details page of the Application script, on the Cúram worker portal.

Note: The A-number is optional for the Certificate of Citizenship and Naturalization Certificate document types.

Source

Requirement

ID

Business Rule ID

Description System Feature

In Scope (Yes/N o)

HCR LP.1.6.1 The system must display the mandatory fields for the different document types on the supporting document details page of the COC script, on the Cúram worker portal.

Note: The A-number is optional for the Certificate of Citizenship and Naturalization Certificate document types.

VLP Yes

HCR LP.1.6.2 The system must display the mandatory fields for the different document types on the supporting document details page of the ACR script, on the Cúram worker portal.

Note: The A-number is optional for the Certificate of Citizenship and Naturalization Certificate document types.

VLP No

HCR LP.1.6.3 The system must display the mandatory fields for the different document types on the supporting documents details page of the Application script, on the Cúram citizen portal.

Note: The A-number is optional for the Certificate of Citizenship and Naturalization Certificate document types.

VLP Yes

HCR LP.1.6.4 The system must display the mandatory fields for the different document types on the supporting documents details page of the COC script, on the Cúram citizen portal.

Note: The A-number is optional for the Certificate of Citizenship and

Naturalization Certificate document types.

VLP Yes

HCR LP.1.7 The system shall create a task when the VLP response indicates lawful presence verification pending and the HUB requires additional information to complete the VLP verification process.

Note: The SI shall determine any additional task requirements not listed below.

Source

Requirement

ID

Business Rule ID

Description System Feature

In Scope (Yes/N o)

HCR LP.1.7.1 The system shall create a task when the VLP step 1 response has ESC 37.

Note: The ESC 37 indicates data mismatch or incorrect information. The worker must initiate step 1a or 2 or 3.

VLP No

HCR LP.1.7.2 The system shall create a task when the VLP step 1 response has ESC 40.

Note: The ESC 40 indicates data mismatch or incorrect information. The worker must initiate step 1a or 3.

VLP No

HCR LP.1.7.3 The system shall create a task when the VLP response (step 1, 1a, or 1b) has ESC 5.

Note: The ESC 5 indicates IAV or institute additional verification. The worker must initiate set 2 or step 3 based on the HUB response in the ‘AgencyAction’ field.

VLP Yes

HCR LP.1.7.4 The system shall create a task when the VLP step 1 or 1a response has ESC 32 (as-is).

Note: The ESC 32 indicates the HUB requires the Student and Exchange Visitor Information System (SEVIS) ID to perform lawful presence verification. The worker must initiate the VLP request with the student’s SEVIS ID information.

VLP No

HCR LP.1.7.5 The system shall create a task when the VLP step 2 response code is 015 or 026.

Note: The worker must initiate the VLP step 3 process.

3.1 Requirement Modifications

This section will document any subsequent changes to the RTM that may later be required as discovered through development, test execution, bug fix develop or training activities.

Note: This section is used to highlight requirement changes, changes required to be addressed in by this design will be included in the Function Section as well as the RTM document and Jira.

HCR

or

CGIS

Source Requirement ID

Business Rule ID Description

System Feature

Date Updated

In Scope (Yes or No)

4 Function

4.1 CGIS Verify Lawful Presence

4.1.1 Design Description

This section describes how CGIS will be updated to implement the Verify Lawful Presence functionality.

4.1.2 Functional Output

• Workers are able to trigger VLP requests for members.

• Workers are able to upload verification documents in valid formats.

• The IEG scripts and Guided Change wizard capture the mandatory information for supporting documents required for VLP.

4.1.3 Requirements Addressed

# Requirement Description

1 INT_VLP_REQ_1 The system shall have the ability to verify the citizenship/immigration status and lawful presence for a person through the existing VLP Interface introduced by HCR.

Cúram will initiate Step 1 of the VLP service, passing information via

ESB to the HUB to retrieve the citizenship and immigration status from

SAVE for the majority of cases via the H59 Agency3InitVerif web service per MMRP HCR31 VLP Interface in Curam FDS V4.0.

2 INT_VLP_REQ_1.1 The system shall automatically initiate the verification for citizenship/lawful presence through the VLP interface for a new person at the time of application (triggered via ‘Next’ on Electronic Signature page) through the citizen portal for all CGIS Applications, when all the following conditions are met:

1. RIDP passes on the citizen portal,

2. the applicant attests to be a US Non-Citizen National or Other,

3. the person is applying for Medicaid benefits.

3 INT_VLP_REQ_1.2 The system shall automatically initiate the verification for citizenship/lawful presence through the VLP interface for a new person at the time of application (triggered via ‘Submit’ on Clients Rights and

Responsibilities page) through the worker portal for Non-MAGI

Applications, when all the following conditions are met:

1. the person attests to be a US Non-Citizen National or Other

2. the person is applying for Medicaid benefits.

https://schhs.sharepoint.com/:w:/r/sites/1211207/Business%20Process%20Modeling%20Documents/HCR%20Tracks/Track%20HCR31%20-%20VLP%20Interface%20in%20Curam/Approved%20Documents/MMRP%20HCR31%20VLP%20Interface%20in%20Curam%20FDS%20V4.0.docx?d=w9e332f460d7b401f82bd46875aaea735&csf=1&e=2tKvyJ

# Requirement Description

4 INT_VLP_REQ_1.3 The system shall automatically initiate the verification for citizenship/lawful presence through the VLP interface for a new person added through the CGIS Guided Change Wizard (triggered via ‘Finish on the Guided Wizard), when both the following conditions are met:

3. The person attests to be not a US Citizen and selects “Yes” to US Non-Citizen National, and selects one of the following documents (Certificate of Citizenship, Naturalization Certificate, Passport) from the supporting document drop down.

4. OR The person attests to be not a US Citizen and selects “No” to US Non-Citizen National, and selects “Yes” to “Are you lawfully present in the United States?”

1. The person attests to be a US Non-Citizen National or Other.

2. The person is applying for Medicaid benefits

5 INT_VLP_REQ_2 The system shall allow the worker to manually initiate the VLP process for a person if the VLP request could not be triggered automatically or if the lawful presence is unverified by the system using the “Check Verify Lawful Presence (VLP)…” button on Interface Data screen of the CGIS Application using the VLP Wizard introduced in HCR per section

3.2 Check Verify Lawful Presence (VLP)…Action of the MMRP

HCR31 VLP Interface in Curam FDS V4.0.

6 INT_VLP_REQ_2.1 The system shall allow the worker to manually initiate the VLP process for a person if the VLP request could not be triggered automatically or if the lawful presence is unverified by the system using the “Check Verify Lawful Presence (VLP)…” button on Interface Data screen of the CGIS Integrated Case using the VLP Wizard introduced in HCR per section 3.2 Check Verify Lawful Presence (VLP)…Action of the MMRP HCR31 VLP Interface in Curam FDS V4.0

7 INT_VLP_REQ_2.2 The system shall allow the worker to initiate a VLP verification request for an applicant on the CGIS application or Income Support case if the lawful presence was verified in the past and if member’s Citizen Status on Household Member evidence has changed after the last successful verification.

8 INT_VLP_REQ_2.3 The system shall allow the worker to manually generate a checklist notice when the VLP verification is in process.

9 INT_VLP_REQ_3.1 The system will not trigger the VLP call if all fields required for the VLP call are not provided for the different document types on the supporting documents details page of the Citizen Portal and Worker Portal IEG

Scripts.

10 INT_VLP_REQ_3.2 The system will not trigger the VLP call if all fields required for the VLP call are not provided for the different document types on the supporting documents details page of Guided Change Wizard.

11 INT_VLP_REQ_3.3 When the user provides an Alien Number, Cúram will remove the leading “A” and will add leading zeros to make a 9-digit number before sending the verification request. The manipulation is done only on the data value being sent to HUB, so that it meets the HUB criteria. The system will not update the data saved in Cúram.

https://schhs.sharepoint.com/:w:/r/sites/1211207/Business%20Process%20Modeling%20Documents/HCR%20Tracks/Track%20HCR31%20-%20VLP%20Interface%20in%20Curam/Approved%20Documents/MMRP%20HCR31%20VLP%20Interface%20in%20Curam%20FDS%20V4.0.docx?d=w9e332f460d7b401f82bd46875aaea735&csf=1&e=2tKvyJ https://schhs.sharepoint.com/:w:/r/sites/1211207/Business%20Process%20Modeling%20Documents/HCR%20Tracks/Track%20HCR31%20-%20VLP%20Interface%20in%20Curam/Approved%20Documents/MMRP%20HCR31%20VLP%20Interface%20in%20Curam%20FDS%20V4.0.docx?d=w9e332f460d7b401f82bd46875aaea735&csf=1&e=2tKvyJ https://schhs.sharepoint.com/:w:/r/sites/1211207/Business%20Process%20Modeling%20Documents/HCR%20Tracks/Track%20HCR31%20-%20VLP%20Interface%20in%20Curam/Approved%20Documents/MMRP%20HCR31%20VLP%20Interface%20in%20Curam%20FDS%20V4.0.docx?d=w9e332f460d7b401f82bd46875aaea735&csf=1&e=2tKvyJ

12 INT_VLP_REQ_3.4 When the user provides a SEVIS ID, Cúram will remove the leading “N” before sending the verification request.

13 INT_VLP_REQ_3.5 The Visa Number field will be removed from the Supporting Document Details page of the CGIS IEG Script, from the DHSID Details evidence for CGIS and from the Supporting Document Details page of the Guided Change Wizard to align with HCR per PROD-5531.

Note: The Global IEG, Global Evidence, and CoC designs will be updated to reflect this change.

14 INT_VLP_REQ_3.6 Cúram will store the information received from the VLP services on the External Citizenship Status evidence and the VLP Interfaces Data tab per the including the values returned by the HUB and the details for the most recent step.

15 INT_VLP_REQ_3.7 Cúram will create an outstanding verification on the Citizen Status if the HUB is down or a connection cannot be established with the HUB while running Citizen Portal or Worker Portal IEG scripts or Guided Change wizard.

16 INT_VLP_REQ_3.8 CGIS will allow the workers to use Cúram’s OOTB attachment functionality to attach the document to the case and select the person.

They will use “VLP Attachment” as the “Document Type” which was introduced by HCR. The case worker will select this type, when the document is being attached is for VLP step 3. The file should be accessible through the browse button. Files from OnBase have to be moved locally by the case worker first. HUB accepts files which are less than 5 MB. The file type must be one of the following: JPG, PNG, GIF, or PDF. The attachment will be saved in OnBase.

Cúram will verify the file being attached meets the following conditions, if the selected Document Type is “VLP Attachment”.

File type is one of the following, JPG, PNG, GIF, or PDF File size is <= 5 MB.

A Participant is selected in the participant drop down.

If one or more of the above conditions fail, Cúram will display the corresponding message from the list.

• The file type should be one of the following JPG, PNG, GIF, or

PDF.

• The file size should be less than equal to 5 MB

• Please select a participant from the participant drop down.

17 INT_VLP_REQ_3.9 The OnBase keywords for the VLP attachment on a CGIS case will set as per the CGIS15- OnBase Integration ADD- Section 4.2 Functional Story – Notice Storage in OnBase.

The OnBase doc type will be “MEDS- Notice of Action”

Sr. No. OnBase keyword

Cúram Data

1 HH#/AppID Integrated Case Reference Number.

2 Primary

SSN

Primary Applicant’s SSN

3 Case Date Submitted Date

4 Last Name Primary Applicant’s Last Name

5 First Name Primary Applicant’s First Name

6 Claim Type All the applicable Claim Types as defined in the CGISS15 Onbase Integration ADD – Notices pdf.

r an case with IEG data, the claim type will be set as per the CGIS15 OnBase Integration requirement- R2_CGIS_IOB_1.4.1: The claim type for the keywords based on the responses to the IEG questions should follow the mapping provided in the General Information spreadsheet.

For a case without IEG date, the claim type will be set as per the CGIS15 OnBase

Integration requirements-

R2_CGIS_IOB_2.7- R2_CGIS_IOB_2.7.7

SCDHHS Application Intake IEG Master –

All V

7 Intake or Interview

Intake

8 Site ID County of Residence*

9 Year Year of the application

10 Trailing Document

No

11 Language If preferred language on integrated case is;

- Spanish: use Spanish - English: use English - use Other for everything else

12 Doc Source CGIS

13 Person ID Reference Number from Person Record https://schhs.sharepoint.com/sites/1211207/CGIS%20Business%20Requirements%20and%20Design%20Documents/SCDHHS%20Application%20Intake%20IEG%20Master%20–%20All%20V1.5 https://schhs.sharepoint.com/sites/1211207/CGIS%20Business%20Requirements%20and%20Design%20Documents/SCDHHS%20Application%20Intake%20IEG%20Master%20–%20All%20V1.5

14 Receipt Date

Date the VLP attachment was uploaded on the CGIS IC/Application

15 Notice Type Miscellaneous

16 Form Type NA

18 INT_VLP_REQ_3.10 CGIS will be updated to use the following logic to determine the lawful presence/citizenship of the applicant.

S/N Condition Determination

1 HUB response confirms applicant is US Citizen (USCitizenCode=Y)

US Citizen

2 HUB response confirms applicant is Lawfully present (LawfulPresenceVerifiedCode=Y)

Lawful Presence

19 INT_VLP_REQ_4 The system shall create a task when additional information is required to complete the VLP verification process per the existing HCR design.

All tasks created as part of VLP will be assigned to one of three new work queue. All CGIS user roles will be able to subscribe to VLP work queue. The user roles with access to the work queues are identified in the Tasks and Work Queues master spreadsheet.

20 INT_VLP_REQ_4.1 Following Work queues will be created:

1. Non-MAGI Verify Lawful Presence (VLP)

2. LTC/OSS Verify Lawful Presence (VLP)

3. TEFRA/BCCP Verify Lawful Presence (VLP)

Note: If the member for whom the VLP call is being triggered has applied for both LTC/OSS and TEFRA/BCCP, the task will be created in the TEFRA/BCCP work queue

21 INT_VLP_REQ_4.2 System shall create a task when the VLP response indicates lawful presence verification pending and the Hub requires additional information to complete the VLP verification process

Reference: Sec 4.2 Task Templates

22 INT_VLP_REQ_6 The system will generate a combined daily and monthly control report for the VLP interface that includes the totals listed below for both CGIS & HCR. Exception/Details report will include case/person details indicating whether HCR or CGIS case:

1. The total number of all VLP requests sent (VLP request per step, not per person).

2. The total number and percentage of requests sent for VLP Step

1.

3. The total number and percentage of requests sent for VLP Step

2.

4. The total number and percentage of requests sent for VLP Step

3.

5. The total number and percentage of successful responses for

VLP Step 1.

6. The total number and percentage of cases processed straight through post VLP Step 1.

7. The total number and percentage of VLP Step 1 DHS cases sent to VLP Step 2.

8. The total number of DHS verified cases returned for VLP Step

2.

9. The total number and percentage of successful response for

VLP Step 2.

10. The total number and percentage of cases authorized automatically post VLP Step 2.

11. The total number of DHS verified cases returned for VLP Step

3.

12. The total number of successful responses for VLP Step 3.

13. The total number of cases authorized automatically post VLP

Step 3.

14. The total number and percentage of tasks generated by various task types for VLP.

15. The total number of requests sent for DHS closure.

16. The total number and percentage of DHS cases closed successfully.

17. The total number and percentage of DHS cases failing closure.

18. The total number and percentage of records with errors with unique error (technical vs non-technical error) identifier.

19. Average response time for VLP Step 1 (time begins when Step

1 request was sent, and Step 1 response is received).

20. Average response time for VLP Step 2 (time begins when Step

1 response is received indicating the time Step 2 began until

Step 2 response is received).

21. Average response time for VLP Step 3 (time begins when Step

3 request document upload was sent, and Step 3 response is received).

22. The total number of DHS cases waiting for VLP Step 2 or Step

3 response from the hub for 12 calendar days or more. (time begins when status stays as ‘Step 2 In Progress’ or ‘Step 3 In

Progress’ for 20 calendar days or more).

23 INT_VLP_REQ_7 A details report must be provided for the DHS cases waiting for VLP step 2 or step 3 response form hub for 20 calendar days or more. (time begins when status stays as ‘Step 2 In Progress’ or ‘Step 3 In Progress’ for 20 calendar days or more). Report will modify existing HCR report to add new column for HCR/CGIS indicator.

The following information must be included on the details report:

1. Member First Name

2. Member Last Name

3. Member DOB

4. Member SSN

5. AC/IC Reference Number

6. Case Type (Application/IS)

7. DHS Case Number

8. VLP Step response pending

9. HCR/CGIS indicator

24 INT_VLP_REQ_8 When Citizen Status is verified by VLP, the system will check to see if the member is associated to any other CGIS IC, HCR IC, CGIS application, or HCR application case where they have an OV for the Citizen Status. If yes and the Citizen Status is as defined below, the system will clear associated OVs.

HCR: U.S. National or Alien Lawfully Present

HCR OVs will be marked as E-Verified

CGIS: Alien or U.S. Non-Citizen National

CGIS OVs will be marked as ‘Verified by VLP’

25 INT_VLP_REQ_9 Guided Change wizard will be updated to indicate the Supporting Document field is mandatory when Alien, Refugee, or U.S. Non-Citizen National are selected as the Citizen Status.

4.2 Task Templates

1. Task: VLP Service Not Available

Task Notification

Name: VLP- The system is unable to perform verification for citizenship/lawful presence through the

VLP process.

Purpose A worker must correct/complete the application data and send the VLP request to the

Hub.

Trigger(s) The system shall create a task if the system is unable to initiate the VLP request when the person’s citizenship/lawful presence must be verified through the VLP interface. (VLP.1.7.1).

Allocation Type User Position Job Org Unit Queue

Allocation Strategy Non-MAGI Verify Lawful Presence (VLP), or

LTC/OSS Verify Lawful Presence (VLP), or

TEFRA/BCCP Verify Lawful Presence (VLP)

Link Link Yes No

Primary Action Link IS Application or IS Case

Supporting Information Link Person Page

Subject Subject Text Complete verification of lawful presence for the applicant(s) on the case.

Task Details Deadline Strategy Yes No

Deadline Strategy Details 15 Calendar Days (from date task is created)

Escalation Strategy None

Deadline Override Allowed Yes No

Task Priority Low Medium High

Manual Forwarding Allowed Yes No

Manual Close Allowed Yes No if No, Automatic Task Closure Instructions below must be completed.

Automatic Task Closure

Instructions

Task/Notification

Information

This may be used to place instructions, help or steps to complete the task.

1. Review the applicant’s citizenship/lawful presence information on the case.

2. Initiate the VLP verification request manually if the case information is complete and correct.

3. Request verification from the applicant if the required information is not provided on the case.

4. Please close the task in Cúram once the required action is taken.

5. Please refer to the Verify Lawful Presence

(VLP) job aid for additional information on this task.

Task/Notification

Body Details

Message Body Text N/A

Other Special

Processing

None

2. Task: Eligibility Statement Code of 37

Name: VLP- Initiate the VLP re-verification request to the Hub.

Purpose A worker must verify the VLP Step 1 response and send the VLP re-verification request to the Hub.

Trigger(s) VLP Step 1 has response code ESC 37.

Allocation Type User Position Job Org Unit Queue

Allocation Strategy Non-MAGI Verify Lawful Presence (VLP), or

Supporting Information Link Person Page

Subject Subject Text The applicant’s citizenship or lawful presence was not verified by the external system. Initiate the VLP re-verification request (VLP Step 1a or

2 or 3).

Task Details Deadline Strategy Yes No

Deadline Strategy Details 15 Calendar Days (from date task is created)

Escalation Strategy None

Deadline Override Allowed Yes No

Task Priority Low Medium High

Manual Forwarding Allowed Yes No

Manual Close Allowed Yes No if No, Automatic Task Closure Instructions below must be completed.

Automatic Task Closure

Instructions

N/A

Task/Notification

Information

This may be used to place instructions, help or steps to complete the task.

1. Review the applicant’s citizenship/lawful presence information on the case.

2. Review the Eligibility Statement Code

(ESC), the Response Code and the Agency

Action in the VLP response received.

3. Initiate the VLP Step 1a or 2 or 3 verification request if the case information is complete and correct.

4. Request verification from the applicant if the required information is not provided on the case.

5. Please close the task in Curam once the required action is taken.

6. Please refer to the <job aid> for additional information on this task.

Task/Notification

Body Details

Message Body Text N/A

Other Special

Processing

3. Task: Verify the Qualifying Coverage

Name: VLP- Verify the QC work quarters information from SSA/SVES.

Purpose A worker must verify the work quarters Information and update the evidence and authorize the case.

Trigger(s) The system shall create a task for the worker to verify the QC Information, if the

VLP response indicates the person is applicable to 5-year bar rule and the person has met the 5-year bar (VLP.2.1.1).

Allocation Type User Position Job Org Unit Queue

Allocation

Strategy

Non-MAGI Verify Lawful Presence (VLP), or

Supporting Information Link Person Page

Subject Subject Text Determine the applicant’s Medicaid eligibility based on the 5-Year Bar Criteria and Qualifying

Quarters.

Task Details Deadline Strategy Yes No

Deadline Strategy Details 15 Calendar Days (from date task is created)

Escalation Strategy None

Deadline Override Allowed Yes No

Task Priority Low Medium High

Manual Forwarding Allowed Yes No

Manual Close Allowed Yes No if No, Automatic Task Closure Instructions below must be completed.

Automatic Task Closure

Instructions

N/A

Task/Notification

Information

This may be used to place instructions, help or steps to complete the task.

1. Verify the VLP response received from the external system and determine if the applicant’s Medicaid eligibility is subject to the 5-Year Bar criteria and Qualifying

Quarters.

2. Initiate a verification request for Qualifying

Quarters via SVES or Person Composite

Service, if the information is required for eligibility determination.

3. Request verification from the applicant if the required information is not provided on the case.

4. Determine the applicant’s Medicaid eligibility if all required information is available and verified on the case.

5. Please close the task in Cúram once the required action is taken.

6. Please refer to the Verify Lawful Presence

(VLP) job aid for additional information on this task.

Task/Notification

Body Details

Message Body Text N/A

Other Special

Processing

4. Task: Reminder Task

Name: VLP Reminder task for outstanding verification on the case related to citizenship/lawful presence.

Purpose A worker must check OnBase if the requested information was returned by the client so that the VLP process could be completed.

Trigger(s) The system shall create a VLP task when the due date has passed for the information to be returned (VLP.2.9.1).

Allocation Type User Position Job Org Unit Queue

Allocation

Strategy

Non-MAGI Verify Lawful Presence (VLP), or

Link Yes No

Link

Supporting Information Link Person Page

Subject Subject Text An applicant’s citizenship or lawful presence…