Implementing H.R. 1 in the open
Rapidly meet H.R. 1 Medicaid requirements, on your terms
OSCER is Nava’s ready-to-deploy, open source compliance tool that works alongside existing Medicaid systems. Vendor-agnostic; no license fees.
H.R. 1 Medicaid Compliance
States must comply with H.R. 1 community engagement requirements by January 1, 2027. This poses many risks for states, such as high implementation costs, “ripping and replacing” a legacy system that wasn’t built for continuous reporting, and facing procurement timelines that do not align with the H.R. 1 deadline.
Eligible beneficiaries who are exempt from the new requirements may lose coverage erroneously — state systems must be able to automatically identify exemptions to prevent unnecessary churn.
Nava understands the pressure states are facing, and we’re here to help.
The fastest, lowest-risk path to compliance
OSCER is Nava’s open source community engagement reporting tool. You don’t need to “rip and replace” to implement OSCER. It’s a sidecar application, meaning it sits alongside existing eligibility systems and vendors. This approach enables states to achieve compliance by extending system functionality without getting locked into proprietary platforms or expensive customizations.
For many beneficiaries, OSCER can verify community engagement compliance without requiring any action from the beneficiary. Here’s how:
Implementation steps:
Step 1: Schedule a private demo
Step 2: Two-month MVP implementation deployed to your infrastructure and configured to your policy, with Nava’s support
Step 3: Deepen integrations, add data sources, customize rules
Why OSCER
Expand data access
OSCER can connect data sources many state systems can’t reach, such as the U.S. Department of Veteran Affairs (VA) Lighthouse application programming interface (API) for Veteran exemptions or employment data for income compliance.
Automate compliance checks
OSCER uses a rules engine, which is configurable to states’ unique policies, to automatically identify exempt or compliant beneficiaries. States do not need to change the code to adapt to policy updates.
OSCER also offers a simple, human-centered beneficiary interface for those who must manually report.
Deploy in two months
In two months, states can deploy an MVP of OSCER to their infrastructure (pending credentialing). With the MVP, states can start to connect to their existing data sources and configure their state policies. From there, states can deepen integrations and expand capabilities as their needs evolve.
Full feature list
Feature | Status |
|---|---|
Rules engine | Available |
Ex parte verification using state data | Available |
External data integration | VA available, others planned |
Mobile-friendly beneficiary interface | Available |
Beneficiary-facing exemption screener | Available |
Case management tools | Available |
Email and SMS that integrates with existing state notification systems | Email available, SMS coming soon |
Audit-tested reporting and dashboard | In progress |
Document AI | Available |
Custom state branding | Available |
SSO integration | Available |
Flexible integration option
We designed OSCER’s components to work with one another. However, states don’t have to adopt everything at once. OSCER’s integration options allow for easy implementation and deeper integration when a state is ready.
Deliver without compromise
OSCER is the only solution on the market that fully aligns with government’s long-term, no lock-in technology, and vendor ecosystem interests.
OSCER is also state-driven, meaning every state using OSCER benefits from new features we build. For example, if we build batch processing to meet one state’s needs, then every OSCER state can use the batch processing feature.
OSCER | COTS Products | SaaS Products | Custom Development | |
|---|---|---|---|---|
Roadmap control | Yes | Sometimes | No | Yes |
Own your data and code | Yes | Sometimes | No | Yes |
Ready-to-use | Yes | Yes | Yes | No |
Upfront cost | $ | $$$ | $$ | $$$ |
Long-term cost | $ | ﹩﹩﹩﹩ | ﹩﹩﹩﹩ | $$$ |
Vendor agnostic | Yes | No | No | Sometimes |
State-driven | Yes | No | No | No |
Building in the open
We’re committed to building OSCER in the open. We made our roadmap public so you can always see what we’re working on and what’s planned for the future.
Our code repository is also public, and we regularly host public demo days, publish progress reports, and share lessons learned from states.
You can watch all of our previous demo days by clicking below.
Schedule a private demo
Get in contact with our Medicaid team to learn more about what we can do together.