Produced By: Federal/National Government: Agency
-
Rules as Code – Test, Learn, Repeat
The New South Wales government describes its efforts to connect with other Australian jurisdictions and international colleagues in its move towards making machine-consumable legislation and policy.
-
Rapid Implementation of Policy as Code
Policy changes are often dynamic and occur quickly, but they can only create impact once implemented. The Eligibility APIs Initiative at 18F shares an example from their work that shows the potential for rapid, accurate policy implementation as code.
-
Promoting Public Benefits Access Through Web-Based Tools and Outreach: A National Scan of Efforts. Volume I: Background, Efforts in Brief, and Related Initiatives
Demand for public benefits is rising in response to continued economic pressure on vulnerable people, in addition to changes in eligibility rules for some safety net programs. This report summarizes existing benefits access efforts, studies the successes and challenges of benefits expansion efforts through a subset of in-depth case studies, and analyzes the potential for sustaining, expanding, and replicating successful efforts.
-
Prerequisites for modular contracting
18F describes modular contracting, the process of breaking up large, custom software procurements into a small constellation of smaller contracts. Modular procurement requires agile, product thinking, user-centered design, DevSecOps, and loosely-coupled architecture.
-
OpenFisca: Write rules as code
OpenFisca provides a syntax for writing Rules as Code.
-
Mapping the Applicant Experience of Benefit Enrollment
Applicants to federal aid programs face numerous barriers in accessing benefits they are eligible for. The Centers for Medicaid and Medicare conducted an extensive qualitative user research study to better understand applicant experience in enrolling in public assistance programs. Based on the results, the study emphasizes the need for simplified, streamlined and less burdensome application processes.
-
Implementing rules without a rules engine
It is frequently assumed that when rules are implemented as code, a rules engine is necessary. However, it is possible for policy people and engineers to effectively work together to code logic that drives technological system without needing a mediating rules engine at all.
-
Federal Field Guide
Few large government software projects are successful, as current ecosystems in place at agencies do not support agile development practices. This guide provides instructions to federal agencies on how to effectively budget for, procure, and oversee software development projects.
-
Federal Agencies Need to Strengthen Online Identity Verification Processes
Remote identify proofing is the process federal agencies and other entities use to verify that the individuals who apply online for benefits and services are who they claim to be. If the applicant responds correctly to personal questions, their identity is considered to be verified. However, data stolen in recent breaches could be used fraudulently to respond to knowledge-based verification questions. Alternative methods are available that provide stronger security, but these methods may have limitations in cost, convenience, technological maturity, and they may not be viable for all segments of the public.
-
Exploring a new way to make eligibility rules easier to implement
Programs like Medicaid and SNAP are managed at the federal level, administered at the state level, and often executed at the local level. Because there are so many in-betweens, there is significant duplicated effort, demonstrating the need to simplify eligibility rules to facilitate easier implementation.
-
Eligibility Rules Weekly Recaps
Github page with weekly recaps on the activities taking place during 18F’s Eligibility Rules Service project.
-
Eligibility APIs Initiative
Documentation of 18F's and 10x's Eligibility APIs Initiative