Skip to content

Latest commit

 

History

History
29 lines (18 loc) · 1.97 KB

data.md

File metadata and controls

29 lines (18 loc) · 1.97 KB

Return to introduction

Note: This repository represents my personal work, done in my personal time and capacity. It is not representative of GSA (my employer at the time of publishing).

Strength 3: Applicant data submission is decoupled from program applications.

A general model for data collection

The practice of collecting the data needed to determine eligibility for individual benefits programs separately was established by the traditional paper applications each program issued. The move to digitize those applications has largely recreated this practice.

Yet we know people are frequently eligible for multiple programs designed to address different need. They need the ability to determine eligibility and apply for multiple programs all in one place, in as few steps as possible.

We've developed some methods of smoothing the process, such as presumed eligibility, aligned eligibility criteria, or data sharing to ease the burden of duplicative re-entry of data. Yet if we’re working to establish a truly intergrated eligibility experience, where a person or household can apply once and eligibility can be determined for a variety of programs, we need to sever the act of data submission and individual program applications.

Data should be entered in aggregate for all relevant programs in the most intuitive way for the applicant (See Exhibit B: Client experiences) and then used to determine individual programs behind the scenes.

Illustration visualizing the 7 points below

  1. Structure aggregate data and understand which programs need what data
  2. Identify the services/programs applicants may need
  3. Collect the data needed for all relevant programs at once
  4. State staff review/verify data
  5. Use the collected data to concurrently apply to programs separately
  6. Determine eligibility based on each application
  7. Issue benefits to applicants