Audit-ready
Append-only audit records, versioned rules, fail-closed audit writes. Built so a record can be reviewed years later.
§71119 · Effective Jan 1, 2027
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.
Append-only audit records, versioned rules, fail-closed audit writes. Built so a record can be reviewed years later.
Designed for H.R. 1 §71119. Runs alongside the state’s eligibility system; it does not replace it.
Exclusions on file, response deadlines tracked, notices and status in 15 languages.
Civistara calculates status from the evidence and routes it to state staff. The state agency decides.
Program integrity you can defend.
Nobody eligible loses coverage.
Members use the Civistara app to see their status, report activity or an exclusion, and answer notices in their own language.
02 · Illustrative scenario
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.
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 appThe volunteer coordinator confirms attendance through the partner attestation portal. The confirmation is attached to her record as evidence.
Civistara attestation portalThe 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 consoleCivistara 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 consoleThe 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.
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.
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.
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.
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.
View / mutation separation. Read endpoints are built not to change a member’s record as a side effect of someone viewing it.
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.
Who decides matters. So does what Civistara is not.
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.
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.
“In progress” and “Roadmap” items are forward-looking. They are not current certifications, authorizations, or attestations.