For state agencies and health plans

Program integrity you can defend.

When Louisiana’s community engagement requirement starts on January 1, 2027, the state needs activity it can verify, evidence that is ready for review, and controls against fraud, waste and abuse that do not catch eligible people in the net.

Civistara calculates status from the evidence and routes it to state staff; the state agency decides.

For
State Medicaid agencies · legislators · health-plan program-integrity teams
Louisiana start
January 1, 2027
Decision authority
The state agency
01

Activity you can verify.

When a member chooses location check-in at a registered work or volunteer site, the app sends heartbeats throughout the session. Each heartbeat consumes a server-issued, single-use nonce, so a replayed packet is rejected, and the server checks each reported position against the site’s registered boundary rather than taking the app’s word for it.

Mock-location and impossible-accuracy signals raise anomaly flags. A flag routes the record to staff review; it is a prompt for a person to look, not a finding. Native device attestation is on the roadmap: Android Play Integrity verification is implemented, with production enforcement planned for general availability, and Apple App Attest on iOS is planned.

Mechanism · Verified check-in
Replay protection
Single-use, server-issued nonce on every heartbeat · replays rejected
Location check
Server-side distance check against the registered site boundary
Anomaly flags
Mock-location and impossible-accuracy signals · routed to staff review
Device attestation
Roadmap · Android Play Integrity implemented, production enforcement planned for general availability · Apple App Attest planned
02

Attestations that show who confirmed the hours.

Employers and partner organizations confirm hours through their own portals. Employer attestations record signer identity, time, IP and device.

When employer-reported and member-reported hours disagree, the mismatch goes to a caseworker with a dispute path. An employer or partner cannot change a member’s status directly; attestations are evidence for state staff.

Mechanism · Attestation integrity
Employer attestations
Signer identity · time · IP · device
Mismatches
Employer vs. member hours surface for caseworker review · formal dispute path
Authority
Attestations are evidence · they do not change status on their own
03

Evidence that is ready for review.

Audit and ledger records are append-only: database triggers reject changes or deletion, and a correction is a new entry. Status calculations are deterministic and tied to a rule version, so a reviewer can see which rules applied and reconstruct how a status was reached.

State-changing operations are designed to roll back when their audit write fails, and staff actions are role-attributed. The design principles are described in full on the platform page and in the public architecture decision records.

Mechanism · Audit-ready evidence
Records
Append-only audit and ledger tables · corrections are new entries
Rules
Versioned · deterministic calculation · no AI input path
Attribution
Staff actions timestamped and role-attributed
Detail
/platform · /decisions
04

The agency decides.

Civistara calculates status from the evidence and routes it to state staff; the state agency decides. Civistara does not make eligibility determinations and does not replace the state’s eligibility system. It is built to run alongside it.

Federal rules bar states from delegating compliance decisions to Medicaid health plans. Health-plan dashboards in Civistara show which of a plan’s own members may need outreach before a deadline; they are not a decision surface. AI may speed up clear approvals; it can never deny coverage.

Mechanism · Decision authority
State agency
Makes every eligibility and coverage decision
Civistara
Calculates status from the evidence · routes it to state staff
Health plans
Outreach view of their own members · no compliance decisions
AI
May speed up approvals · never denies · CivicAI is read-only

Security and compliance

What is built, what is in progress, what is planned.

SOC 2 Type II and FedRAMP Moderate can be purchasing criteria. We state their status precisely on/security-compliance: what the platform does today, what is under way, and what we are pursuing. We do not display seals for certifications we do not hold.

Providers and community organizations will help many of the people this requirement affects keep their coverage. See how the same platform serves them on/for-providers.

Schedule a state briefing