§71119 · Effective Jan 1, 2027

Compliance infrastructure
for the new Medicaid.

Built for H.R. 1, Section 71119, the federal community engagement requirement that takes effect January 1, 2027. Civistara Compliance organizes the evidence: exclusions on file, verified activity, and response deadlines. Civistara calculates status from that evidence and routes it to state staff; the state agency decides.

For state agencies and health plans, that means program integrity you can defend. For providers and community organizations, it means nobody eligible loses coverage.

Volume
Vol. I · MMXXVI
Status
Available · open for state engagement
Louisiana start
January 1, 2027 · applications and renewals
Domain
Medicaid community engagement

Audit-ready

Append-only audit records, versioned rules, fail-closed audit writes. Built so a record can be reviewed years later.

Purpose-built

Designed for H.R. 1 §71119. Runs alongside the state’s eligibility system; it does not replace it.

Coverage-first

Exclusions on file, response deadlines tracked, notices and status in 15 languages.

State decides

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

02 · Illustrative scenario

One hour, four surfaces, one record.

Patricia is an illustrative scenario built from the synthetic personas we test against. She volunteers at a community organization in New Orleans. Here is how a single hour of community engagement moves through Civistara Compliance, from the moment she checks in to the moment state staff review it.

  1. 01Patricia (member)

    She checks in with the Civistara app.

    She chose to check in with her phone. The location is checked against the organization’s registered boundary on the server, and the hour is timestamped and written to an append-only record.

    Civistara app
  2. 02Community partner (attestation)

    The organization attests to her hours.

    The volunteer coordinator confirms attendance through the partner attestation portal. The confirmation is attached to her record as evidence.

    Civistara attestation portal
  3. 03Her health plan (outreach)

    Her health plan sees an outreach signal, not a decision.

    The plan’s dashboard shows which members may need help before a deadline, scoped to its own members. Federal rules bar states from delegating compliance decisions to health plans.

    Civistara health plan console
  4. 04The state (decision)

    State staff decide, and the record is ready for review.

    Civistara calculates status from the evidence and routes it to state staff; the state agency decides. Append-only records and versioned rules are built so a reviewer can reconstruct what happened years later.

    Civistara state console

Read the full workflow on /approach →

03 · Member app

Where members see where they stand.

The component of Civistara Compliance that beneficiaries actually touch is the Civistara app. It is a state-branded mobile application where members see their status, report work, volunteering or an exclusion, and answer notices.

Every other stakeholder in the ecosystem (state agencies, health plans, employers, community partners) generates outcomes through the beneficiary. A platform that solves for the beneficiary first solves for everyone else by extension.

The Civistara app is built for iOS and Android. What a member submits goes to the Civistara Compliance platform as structured evidence for state staff to review. For members without a smartphone, a staff-assisted path for providers and caseworkers is in development.

Read the full Civistara app capabilities at/app. Read the provider framing at/for-providers.

  • i.
    Optional geofenced check-inMembers who want proof of their hours can check in by location at a registered work or volunteer site. The hour is timestamped and written to an append-only record. Treatment sites are never geofenced.
  • ii.
    15 languagesOnboarding, status, exclusion requests, and in-app guidance in 15 languages, including Spanish and Vietnamese.
  • iii.
    Offline modeOffline-first: an encrypted read cache, queued changes, and automatic sync on reconnect. Built for rural, transit, and low-signal places.
  • iv.
    Community partner matchingIn-app discovery of participating faith-based and community-based organizations that confirm hours through the partner portal.
  • v.
    Accessibility-firstDesigned to WCAG 2.1 AA. All 22 mobile screens reviewed for screen-reader labels, roles, focus order and touch targets; on-device assistive-technology testing of 5 screens is in progress.
04 · Why purpose-built matters

Five design principles, built into the code.

Civistara Compliance was not adapted from an electronic health record, a benefits platform, or a case management tool. It was purpose-built. The five design principles below are built into the database schema and the route layer, not left to the policy manual.

  1. 01
    Records are added, never rewritten.

    Append-only audit records. Database triggers reject attempts to change or delete audit and ledger rows. A correction is a new entry, so the history stays intact.

  2. 02
    Rules are versioned.

    Status calculations are deterministic and tied to a rule version, so the same inputs under the same rules give the same result. Built so a reviewer can reconstruct how a status was reached.

  3. 03
    The platform is designed to fail safe.

    Fail-closed audit. Access is designed to be denied when authentication or tenant context is missing. State-changing operations are designed to roll back when their audit write fails, so changes are not made silently.

  4. 04
    Viewing and changing are separate.

    View / mutation separation. Read endpoints are built not to change a member’s record as a side effect of someone viewing it.

  5. 05
    Only defined actions exist.

    Closed-set audit actions and compliance statuses. Values outside the fixed lists are rejected, so the record never holds a state the rules do not define.

05 · Positioning

What Civistara Compliance is. What it is not.

Who decides matters. So does what Civistara is not.

What Civistara IS

Purpose-built compliance verification, designed as a sidecar.

Civistara is purpose-built compliance verification SaaS. It was designed from first principles for H.R. 1 §71119 and is intended to operate alongside existing state Medicaid Management Information Systems. It is a sidecar, not a replacement.

Civistara calculates status from the evidence and routes it to state staff; the state agency decides. The Civistara app is for members; Civistara Compliance keeps the evidence and the audit record that state staff, providers, partner organizations and reviewers work from.

What Civistara IS NOT

Not an eligibility system. Not generic case management. Not a retrofit.

Civistara does not make eligibility determinations. It does not approve or deny coverage. It does not replace LaMEDS, Maximus, Conduent, Gainwell, or any other state eligibility platform. The state Medicaid agency makes every eligibility and coverage decision. Health plans cannot decide compliance; federal rules bar states from delegating that decision to them.

It is not a generic case management tool, and it is not a retrofit of a legacy referral platform. Open-source sidecars and extended social-care platforms are emerging in the H.R. 1 space. They are different bets, with whatever audit posture their underlying legacy system provides.

Security and compliance, stated precisely.

Read the full status →

Built in today

  • Append-only audit records
  • Tenant isolation
  • AES-256-GCM encryption of sensitive secrets
  • Passkey (WebAuthn) MFA for administrators
  • Designed to support HIPAA technical safeguards

In progress

  • SOC 2 Type II audit planned; controls being implemented now
  • 42 CFR Part 2 consent handling (in development)
  • Clinician attestation (in development)

Roadmap

  • Pursuing FedRAMP Moderate authorization
  • Native device attestation (Android Play Integrity, Apple App Attest)

“In progress” and “Roadmap” items are forward-looking. They are not current certifications, authorizations, or attestations.

06 · Talk to us

Ready to see Civistara Compliance?