Federal Requirements
On this page
CRAIG is designed to satisfy all mandatory requirements of the CCWIS Final Rule. The key regulatory authorities are:
| Regulation | Subject |
|---|---|
CCWIS project requirements (core mandatory requirements) |
|
Design requirements (modularity, documentation, standards, reusability) |
|
Optional CCWIS functions eligible for federal cost allocation |
|
ACF review and assessment procedures |
|
Cost allocation methodology for CCWIS development and operations |
|
Penalties for failure to comply with approved APD |
|
ADP equipment and services — conditions for federal financial participation |
|
Safeguarding information for federal financial assistance programs |
|
Data security, archiving, and purging requirements |
Mandatory Functional Requirements (§ 1355.52)
CRAIG must support the efficient, economical, and effective administration of Title IV-B and IV-E plans, including:
-
Maintaining all program data required by federal, state, or tribal law or policy
-
Supporting Title IV-E eligibility determinations with identical automated functions for all users
-
Preventing data re-entry through automated functions to the extent practicable
-
Providing electronic request systems to child welfare contributing agencies for current and historical CCWIS data
-
Complying with Section 471(a)(8) of the Social Security Act, 45 CFR § 205.50, and Section 106 of CAPTA for data confidentiality
-
Maintaining National Child Abuse and Neglect Data System (NCANDS) data
-
Maintaining Indian Child Welfare Act (ICWA) compliance documentation
Mandatory Data Exchange Partners (§ 1355.52(e-f))
CRAIG must implement bi-directional data exchanges with the following systems. A single data exchange standard (common data definitions, formats, and values) must be used across all exchanges.
| Exchange Partner | Applicability | Description |
|---|---|---|
Child Welfare Contributing Agencies (CWCAs) |
Mandatory |
Public and private contractors providing investigations, placement, and case management |
Financial Payment and Claims Systems |
Mandatory |
Systems generating Title IV-B and IV-E payments and claims |
Medicaid Eligibility Systems |
Mandatory |
Determining Medicaid eligibility for children in care |
Child Abuse and Neglect Systems |
Mandatory if applicable |
Statewide or tribal systems receiving abuse and neglect reports |
Title IV-A / TANF Systems |
Mandatory if applicable |
Temporary Assistance for Needy Families data systems |
Title IV-D / Child Support Systems |
Mandatory if applicable |
Child support enforcement systems |
External Data Collection Systems |
Mandatory if applicable |
Systems used by Title IV-E agency staff to collect CCWIS data outside the core system |
Court Systems |
To the extent practicable |
Courts with jurisdiction over Title IV-E foster care, adoption, and guardianship cases |
Education Systems |
To the extent practicable |
State or tribal education agencies for educational planning for children in foster care |
Health Agency Systems |
To the extent practicable |
State or tribal health agencies |
Tribal Entities |
Optional (§ 1355.54) |
Federally recognized Indian tribes and tribal organizations |
Data Quality Requirements (§ 1355.52(d))
Data must meet the most rigorous of applicable federal and state or tribal standards for completeness, timeliness, and accuracy. CRAIG must:
-
Include automated functions that monitor data quality on an ongoing basis and alert staff when standards are not met
-
Support biennial comprehensive data quality reviews by the Title IV-E agency
-
Maintain a data quality plan submitted to ACF as part of the APD process (OMB Form 0970-0463)
-
Ensure consistent and uniform data collection across CCWIS and all CWCA systems
Design Requirements (§ 1355.53)
-
Business rules must be separated from core programming (modular design)
-
All automated functions must be documented in plain language
-
Components must adhere to state, tribal, or industry-defined standards
-
Components must be designed for reuse and shareability across other states and tribes
Security Requirements (§ 1355.52(j), 45 CFR § 95.621(f))
-
Biennial security reviews of all ADP systems
-
Data archiving and purging procedures per 2 CFR § 200.334 (formerly 45 CFR § 75.361) and § 95.621(f)
-
Audit trails for all data access, modification, and exchange events
-
Confidentiality controls per Section 471(a)(8), 45 CFR § 205.50, and CAPTA § 106