Decisions · ADR-006
Phased noncompliance procedure
A 15-state noncompliance procedure with notice, cure, hearing and appeal branches. A case moves only along defined transitions; moving toward closure before the response deadline throws in code. The state agency decides.
Context
Disenrolling a Medicaid beneficiary is high-stakes. The Centers for Medicare and Medicaid Services (CMS) requires a documented due-process procedure: statutory notice, an active cure period, case-worker review, an alternative-eligibility check, and a hearing notice, in that order. Skipping or reordering steps creates legal liability. A naive implementation that treats the procedure as a checklist (with operational shortcuts available to staff under pressure) cannot defend the audit posture when a wrongful-disenrollment lawsuit arrives.
Decision
Civistara Compliance models the noncompliance procedure as a 15-state machine with notice, cure, hearing and appeal branches and explicit valid-transition tables. A case moves only along defined transitions, so a step cannot be skipped. Attempts to move a case toward closure before the response deadline raise an exception in code, not a policy warning. The caseworker review step is role-gated; only authorized state staff can advance the case past it. Civistara calculates status from the evidence and routes it to state staff; the state agency makes the decision.
Consequences
Statutory due process is enforced structurally, not by training. New procedural steps require schema migration and a code change, which produces a documented audit trail of when and why the procedure changed. Auditors can verify procedural compliance by inspecting the ledger transitions. Operational cost: edge-case scenarios (court orders, retroactive restorations) require new phase transitions, which requires engineering effort. The discipline is uniform; staff cannot route around the procedure by clicking through faster.
Alternatives considered
- Policy-based check at deployment time. Rejected: bypassed by hot-fix code paths and operational shortcuts under pressure. The check must live in the code path itself.
- Workflow engine with configurable transitions. Rejected: configurable means tweakable, which means the audit trail of “why did we transition to disenrolled?” can change. The phases need to be hard-coded against the statute.
References
- statute42 U.S.C. § 1396a(xx)(6) (statutory due process for community engagement disenrollment)
- standardProcedure design pattern as the basis for procedural integrity
Related decisions