Safeguards · Member protections

Coverage is harder to lose than to keep. By design.

The five member protections below are built into the database schema, the route layer, and the mobile app rather than left to policy. Civistara calculates status from the evidence and routes it to state staff; the state agency decides. Reviewers can examine the relevant code under NDA.

Each safeguard pairs the platform-side mechanism with what the member sees in the app. The same record that supports the state’s program integrity also protects an eligible member’s coverage.

Procedural depth
15states in the noncompliance procedure · notice, cure, hearing and appeal branches
Response window
30days to respond to a notice · tracked on every open case
Linguistic reach
15languages in the member app · including Spanish and Vietnamese
Accessibility
22mobile screens reviewed against WCAG 2.1 AA · on-device testing of 5 in progress

Updated

Safeguard 01

No step in the process can be skipped.

Civistara Compliance tracks the state’s process as a 15-state noncompliance procedure with notice, cure, hearing and appeal branches. A case moves only along the procedure’s defined transitions, so a step cannot be skipped, and each transition is timestamped and written to an append-only audit record.

Trying to move a case to closure before the response deadline raises an exception; the workflow refuses it in code, not only in policy. The caseworker review step is role-gated, and the state agency makes the decision at each step. The member sees the countdown, what they can do, and the current state in their mobile app. When the app is offline on a compliance-critical screen, a non-dismissible banner indicates the data may not reflect the latest state decision. Statutory basis: 42 U.S.C. § 1396a(xx)(6).

Mechanism · Due process procedure
Depth
15 states · notice, cure, hearing and appeal branches · role-gated caseworker review
Enforcement
Database layer + service layer · refuses a closure recommendation before the response deadline
Beneficiary surface
Real-time countdown · 4-tier urgency · cure steps · non-dismissible stale-banner on compliance-critical screens
Authority
42 U.S.C. § 1396a(xx)(6)

Read the full architectural record at/decisions/phased-noncompliance-procedure.

Safeguard 02

In progress: a pause while a person waits for a placement.

In progress: cure periods pause while a person waits for a volunteer placement. The pause is recorded today when a person is on a volunteer-placement waitlist; counting it in the hours calculation and applying it automatically are still being built.

The design is informed by federal court decisions on earlier Medicaid work-requirement waivers. Gresham v. Azar, 950 F.3d 93 (D.C. Cir. 2020) affirmed the lower-court vacatur of Arkansas Works; Stewart v. Azar, 366 F. Supp. 3d 125 (D.D.C. 2019) vacated the approval of Kentucky HEALTH. Both courts faulted approvals that failed to consider the effect on coverage. Whether a capacity pause applies in a given state is that state’s policy decision.

Mechanism · Cure-period tolling under capacity shortage
Status
In progress · cure period pauses while the person is on a volunteer-placement waitlist
Still being built
Reflecting the pause in the hours calculation · applying it automatically
Decision
Whether a pause applies is the state’s policy decision
Precedent
Gresham v. Azar, 950 F.3d 93 (D.C. Cir. 2020) · Stewart v. Azar, 366 F. Supp. 3d 125 (D.D.C. 2019)

Read the full architectural record at/decisions/capacity-shortage-tolling.

Safeguard 03

Hours are checked where they happen.

When a member chooses location check-in at a registered work or volunteer site, the app sends adaptive-cadence heartbeats throughout the session, reporting more often near the site boundary. Each heartbeat consumes a server-issued, single-use nonce, so a replayed packet is rejected. Location check-in is optional proof for the member, and treatment sites are never geofenced. Native device attestation is on the roadmap: Android Play Integrity verification is implemented, with production enforcement planned for general availability; Apple App Attest on iOS is planned.

On the platform side, the reported position is checked against the site’s registered boundary on every tick. Mock-location and impossible-accuracy signals raise anomaly flags for staff review; a flag is a prompt for a person to look, not a finding. The server does not take an hour entry on the app’s word alone.

Mechanism · Source-of-record hour verification
Verification
Adaptive-cadence heartbeat · single-use, server-issued nonce on every tick · replays structurally rejected
Provenance
On-device geofence + server-side distance check · anomaly flags on mock-location and impossible-accuracy signals for staff review
Device attestation
Roadmap · Android Play Integrity verification implemented, production enforcement planned for general availability · Apple App Attest planned
Standard
IETF RFC 4122 (UUID) · TLS pinned to issuing CA
Safeguard 04

Tamper-evident appeal timelines, and the member can read the trail.

Endpoints that return member data are designed to write an entry to the append-only audit record. The member can read their media access log from the mobile app: who accessed which uploaded document, when, and with what role.

Appeal timelines are tamper-evident and hash-chained: each appeal event carries a hash chained to the previous one, and the chain can be verified on demand. Single-use download tokens prevent replayed PHI access. Screen-capture and app-switcher protections block exfiltration from the device side. The append-only record described in /platform Decision 01 becomes something the member can read.

Mechanism · Bilateral audit visibility
Coverage
PHI-read audit middleware on member-data endpoints · tamper-evident hash-chained appeal timelines, verifiable on demand · append-only audit record
Member access
Mobile-readable media access log · appeal timeline visible to the member
Device hardening
Single-use PHI download tokens · screen-capture and app-switcher protection · device-only encryption keys
Designed to support
HIPAA technical safeguards (45 CFR § 164.312) · individual right of access (45 CFR § 164.524) · design intent, not a certification
Safeguard 05

No AI denials. No shadow rules.

The status calculation is a deterministic, version-pinned rule evaluation with no AI input path. The CivicAI assistant is read-only by design: it can answer questions about a member’s situation, but it cannot call or change any function that affects compliance status. AI may speed up clear approvals; it can never deny coverage. The state agency makes the decision.

Compliance rules cannot be invented at runtime. Statuses and audit actions are closed sets (see /platform Decision 05 on closed-set actions). A new rule requires a code change, a rule-version bump, and a deployment, not a configuration tweak. Louisiana’s 13 exclusions are LDH’s list; see /for-providers.

Mechanism · Architectural separation of AI and compliance
Calculation
Deterministic rule evaluation · rule-version pinning · no AI input path to compliance status
Invariant
AI may speed up approvals only · never denies benefits or ends coverage · CivicAI is read-only
Closed sets
Statuses and audit actions from fixed lists · database-level constraint enforcement
Authority
42 U.S.C. § 1396a(xx)(7) · H.R. 1 § 71119

Read the full architectural record at/decisions/ai-auto-approve-only.

On the roadmap

What's next.

Civistara Compliance ships continuously. In development now: a cure-period pause while a person waits for a volunteer placement, 42 CFR Part 2 consent handling, clinician attestation for medical-frailty exclusions, and a staff-assisted path for members without a smartphone. Native device attestation is on the roadmap. See /security-compliance for status.

Detailed roadmap and timing are available under NDA. Request a private briefing.

Request a private briefing