The 2015 Medicaid 90/10 rule made eligibility-system funding permanent and tied it to how states buy IT
CMS's final rule of December 4, 2015 kept the 90 percent federal match for Medicaid eligibility and enrollment systems on an ongoing basis. It also set conditions on modularity, reuse, documentation and named state staff, and aligned federal prior approval of state IT contracts.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
CMS's final rule of December 4, 2015 kept the 90 percent federal match for Medicaid eligibility and enrollment systems on an ongoing basis. It also set conditions on modularity, reuse, documentation and named state staff, and aligned federal prior approval of state IT contracts.
- The week A federal match rate reads like a budget number.
- The money made the eligibility system a permanent federal partnership The 90 percent rate is in the statute. [1] Section 1903(a)(3)(A)(i) of the Social Security Act provides it for the design, development and installation of mechanized claims processing and information retrieval systems the Secretary determines are likely to make administration more efficient. [1] Section 1903(a)(3)(B) provides 75 percent for operation. [1] The question was which systems counted.
- The conditions turned funding into design rules The rule required a system to meet conditions in 42 CFR 433.112(b) for CMS to approve it. [1] A later CMS letter described them as 22 conditions the planning document must satisfy. [4] Several bear directly on how a state designs and buys.
- The approvals reached individual contracts As we see it, federal approval takes time, and time is scarce in a state IT project.
- The definitions shaped the market The rule's new definitions mattered as much as its conditions. [1] They decided which kinds of products could be bought at 90 percent.
- The proof moved from checklists to outcomes Funding for operations at 75 percent required CMS approval of the system. [1] [5] The rule named new MMIS certification rules among its planned guidance subjects. [1] How CMS checked systems changed over the following years.
- With hindsight What we cannot say from the sources we opened is whether the rule's savings projections came true. [1] The 2015 rule projected legacy system retirements and lower operating costs through 2025. [1] We found no CMS document in our sources that measured them, and we make no claim either way.
The week
On December 4, 2015, the Centers for Medicare & Medicaid Services published a final rule titled "Mechanized Claims Processing and Information Retrieval Systems (90/10)." [1] The rule said it would be effective January 1, 2016. [1] It finalized a proposal published April 16, 2015. [1]
The rule's summary said it would extend enhanced funding for Medicaid eligibility systems as part of a state's mechanized claims processing system. [1] It said it would update the conditions and standards for such systems, including those for Medicaid Management Information Systems, known as MMIS. [1]
The mechanism was a definition. [1] The rule revised the regulatory definition of Medicaid mechanized claims processing and information retrieval systems to include Medicaid eligibility and enrollment systems on an ongoing basis. [1] That made available to those systems the enhanced federal financial participation in section 1903(a)(3) of the Social Security Act. [1]
The rates were set out in the rule. [1] Enhanced federal funding would be available, under certain circumstances, at a 90 percent match for design, development and installation, and at a 75 percent match for maintenance and operations. [1] The rule's statement of need said the enhanced match reduced the states' share to 10 percent of the costs, compared with the 50 percent burden otherwise in place. [1]
The background explained why the change was needed. [1] A 1989 rule had excluded eligibility determination systems from the definition, so the enhanced match did not apply to them. [1] A 2011 rule had temporarily reversed that exclusion after the Affordable Care Act required sweeping changes to eligibility and enrollment systems. [1]
Under the 2011 rule, the 90 percent rate for development applied to eligibility systems that were operational by December 31, 2015. [1] CMS said it had previously expected fundamental changes to state systems to be completed well before that date. [1] It said it was now clear that additional improvements would benefit states and the federal government. [1]
The rule described the states' progress. [1] It said states were in varying stages of completing their eligibility systems, with work ahead to maximize automation, streamline processes and migrate non-MAGI Medicaid programs into the new systems. [1] It said a majority of states were integrating their systems with human services programs. [1]
The rule also added new definitions. [1] It defined commercial off-the-shelf software, open source, proprietary, service, shared services, software-as-a-service and module. [1] It expanded the definition of the claims processing system to include the concept of a "system of systems" made up of interoperable modules. [1]
It changed the conditions states had to meet. [1] It added that key state personnel must be identified by name in the planning document. [1] It extended to eligibility systems conditions on documentation and portability that had applied to MMIS. [1]
And it changed federal approval of state contracts. [1] It amended 45 CFR 95.611 to align prior approval requirements for all Medicaid IT with existing MMIS policy. [1] The rule set dollar thresholds above which a state would need federal approval to release solicitations or execute contracts. [1]
The rule said CMS intended to follow it with a series of State Medicaid Director letters on discrete subjects. [1] It named the new conditions for enhanced funding, commercial software, new planning document requirements, new MMIS certification rules and reuse. [1]
A federal match rate reads like a budget number. In our reading, in Medicaid IT it works as procurement policy. [1] The 90 percent rate covers that share of what a state spends to build a system, if CMS approves the plan and the system meets the conditions. [1] The conditions decide what the state may build and how it may buy. [1]
Our argument is that the December 2015 rule traded permanence for control. It made the 90 percent rate available to eligibility and enrollment systems on an ongoing basis. [1] In return, it attached conditions that reached into state contracting: modular design, reuse, documentation that would let other contractors run the system, named state staff, and federal approval of large contracts. [1] CMS's guidance to states built on those conditions for years after. [2] [3] [4] [5]
For state Medicaid directors, CIOs and procurement officers, the rule is a reminder that the funding source writes much of the contract. In our view, for vendors and partners it explains why Medicaid IT procurements carry terms on ownership, portability and modularity that other state contracts may not.
We take it in five parts, in the order a state would meet them:
- The money: what the rule paid for, and what CMS projected it would cost and save.
- The conditions: what a system had to be to qualify.
- The approvals: how federal review reached individual contracts.
- The market: how definitions of software and modules shaped what vendors could sell.
- The proof: how CMS checked systems, and how that changed by 2022.
The money made the eligibility system a permanent federal partnership
The 90 percent rate is in the statute. [1] Section 1903(a)(3)(A)(i) of the Social Security Act provides it for the design, development and installation of mechanized claims processing and information retrieval systems the Secretary determines are likely to make administration more efficient. [1] Section 1903(a)(3)(B) provides 75 percent for operation. [1] The question was which systems counted.
From exclusion to temporary to permanent
The rule recounted the history. [1] A final rule published October 13, 1989 excluded eligibility determination systems from the definition. [1] In April 2011, a rule temporarily included them, with the enhanced rate available for systems operational by December 31, 2015. [1] The 2015 rule made the inclusion permanent. [1]
The rule explained why. [1] It said eligibility and enrollment systems are integral to the overall claims processing systems and must be designed and operated as a coordinated part of them. [1] It said that without ongoing enhanced funding, state eligibility systems were likely to become out of date. [1]
What the federal government expected to spend
The rule's regulatory impact analysis gave projections. [1] It estimated federal net costs from fiscal year 2016 through 2025 of approximately $3 billion. [1] That included approximately $5.1 billion in increased federal costs for design, development and installation, offset by lower anticipated maintenance and operations costs. [1]
For states, it estimated net costs over the same period of approximately negative $1.1 billion: a saving. [1] That included approximately $572 million in state costs for development, offset by lower operations costs. [1] The rule said the figures were derived from states' actual system development and maintenance costs. [1]
These were CMS's projections in 2015, not results. [1] The rule acknowledged that it was difficult to predict state behavior. [1] It assumed all states would comply with the conditions to receive the 90 percent rate. [1]
The savings logic
The rule's savings came from retiring old systems. [1] It projected lower costs over the ten-year budget window from operating one eligibility system per state and eliminating legacy systems. [1] It said costs would shift over time from 90 percent development funding to 75 percent operations funding. [1]
It set out its assumptions. [1] It said 9 states had relatively new eligibility systems and were making modular improvements. [1] It assumed an additional 19 states would retire legacy systems within 2 to 3 years with ongoing 90 percent funding. [1] It assumed new systems would cost $50 million on average over 3 years per state. [1]
In our reading, the savings case rested on states actually turning off old systems. Building a new system at 90 percent federal cost is attractive. Retiring the old one requires migrating every program and every case, including the non-MAGI populations the rule said had yet to move. [1] The savings arrive only when the last program leaves the legacy platform.
Who carried the residual risk
At 90 percent federal funding, a state pays 10 cents of each development dollar. [1] That ratio changes the internal economics of a state IT project. In our reading, it makes a state budget office more willing to approve a large build. It also means a failed project costs the state relatively little and the federal government a great deal. That is the context for the conditions that follow: they are the federal government's protection for its 90 percent.
The operations rate and the long tail
The 75 percent rate for maintenance and operations matters more over time than the 90 percent rate. [1] A system is built once and operated for years. The rule's own projection assumed that federal costs would shift from development funding to operations funding over the budget window. [1]
In our reading, that shift changes what a state should negotiate at award. Development pricing is visible and competed. Operations pricing, including hosting, licenses, help desk and change requests, runs for the life of the contract. A state that wins a low development price and accepts open-ended operations terms has moved its costs into the years when the federal share is lower.
The March 2016 guidance drew the line clearly. [2] Initial software licensing is a development cost at 90 percent; ongoing licensing is an operations cost at 75 percent. [2] For subscription products, the subscription is the long tail. A state's financial model should carry it at the operations rate from the start.
How the match can distort a business case
A business case built on the state's share alone can mislead. We think that at a 10 percent state share for development, almost any build looks affordable to a state budget office. [1] The full cost, the larger part of it federal, is what the program actually spends.
In our reading, a sound state business case shows both: the total cost of ownership across development and operations, and the state's share of each. It compares options on total cost first, then on state cost. Consider a design that minimizes the state's share by shifting work into development while raising long-run operating costs. It can pass a state budget review and still fail the efficiency test the statute sets for the enhanced rate. [1] The statute ties the 90 percent rate to systems the Secretary determines are likely to provide more efficient, economical and effective administration. [1] A state's business case is the first document that should show it.
The conditions turned funding into design rules
The rule required a system to meet conditions in 42 CFR 433.112(b) for CMS to approve it. [1] A later CMS letter described them as 22 conditions the planning document must satisfy. [4] Several bear directly on how a state designs and buys.
Standards and interoperability
One condition required alignment with industry standards adopted by the Office of the National Coordinator for Health IT. [1] It listed HIPAA privacy, security and transaction standards, and accessibility standards under section 508 of the Rehabilitation Act or greater. [1] It also listed federal civil rights laws and standards adopted under sections 1104 and 1561 of the Affordable Care Act. [1]
Another required coordination and integration with the Marketplace and the Federal Data Services Hub. [1] It also required interoperability with health information exchanges, public health agencies, human services programs and community organizations providing enrollment assistance, as applicable. [1]
The seven conditions behind the twenty-two
The rule built on earlier guidance. [1] It recounted that in April 2011 CMS issued the "Medicaid IT Supplement Version 1.0; Enhanced Funding Requirements: Seven Conditions and Standards," outlining new standards and conditions for enhanced funding. [1] The March 2016 letter said eligibility systems remained subject to the Medicaid Information Technology Architecture conditions and standards. [2]
In our reading, the architecture framework gave the conditions their technical meaning. A condition that asks for modular, standards-based, interoperable systems needs a reference model to measure against. The architecture framework, with its state self-assessment, supplied it. The March 2016 letter listed performing that self-assessment among the activities eligible for 90 percent funding. [2]
Proof that the system worked
For eligibility systems, the state had to have delivered acceptable MAGI-based system functionality. [1] That had to be demonstrated by performance testing and results based on critical success factors, with limited mitigations and workarounds. [1] The rule described the critical success factors CMS had identified in December 2012, such as accepting a single streamlined application and verifying eligibility from electronic data sources. [1]
The state also had to submit plans with strategies for reducing the operational consequences of failing to meet requirements for major milestones and functionality. [1] In our reading, that is a contingency plan written into the funding conditions.
Contingency plans as a funded deliverable
The contingency condition deserves attention. [1] The state had to submit strategies for reducing the operational consequences of failing to meet requirements for major milestones and functionality. [1] The March 2016 letter listed preparing contingency, business continuity, disaster recovery and security plans among activities eligible for 90 percent funding. [2]
In our reading, that pairing made resilience planning a funded part of the build rather than an afterthought paid from operating budgets. A state that skips it loses both the plan and the federal money for writing it. For a Medicaid agency, those plans also answer the questions an auditor or a federal reviewer will ask after an outage, so they serve twice.
People
The rule added a staffing condition. [1] The state, in writing through its planning document, had to identify key state personnel by name, type and time commitment for each project. [1] The rule's list of changes from the proposal noted that it had added the requirement to identify them by name. [1]
In our reading, this condition targeted a known weakness of outsourced builds: a state that cannot name who will own the system on its side. Naming people is a commitment the state's human resources and budget offices have to support, since vacancies become a funding compliance issue.
Integration with human services
The rule recognized that eligibility systems reach beyond Medicaid. [1] It said a majority of states were integrating their systems with human services programs. [1] One of its conditions required interoperability with human services programs, as applicable. [1]
That integration has a cost-sharing side. A commenter told CMS of its commitment to work with other federal partners on acquisition costs and thresholds for all benefiting programs in an integrated system. [1] The partners it named were the Administration for Children and Families and the Department of Agriculture's Food and Nutrition Service, which oversees SNAP. [1] In our reading, an integrated eligibility system answers to several federal funders, each with its own rules. The 90 percent Medicaid rate covers Medicaid's share, not the whole system.
Portability
Two conditions dealt with whether a state could change vendors. [1] Systems and modules developed with 90 percent match had to include documentation of components and procedures such that the systems could be operated by a variety of contractors or other users. [1] For software developed with 90 percent match, the state had to consider strategies to minimize the cost and difficulty of operating it on alternate hardware or operating systems. [1]
The rule's list of changes said it struck "MMIS" from both conditions, to make them apply to eligibility systems as well. [1] In our reading, these are anti-lock-in conditions. They require a state to buy documentation and portability along with the system.
A catch-all
The final condition allowed other conditions for compliance with existing requirements, issued through formal guidance procedures and determined by the Secretary to be necessary. [1] In our reading, that gave CMS a route to update expectations through guidance rather than new rulemaking. The series of letters that followed used that route. [2] [3] [4]
The approvals reached individual contracts
The rule changed federal review of state IT contracts. [1] It amended 45 CFR 95.611, the prior approval rule, to align all Medicaid IT with existing MMIS policy. [1] It said what was acceptable at the regular match would be acceptable at the enhanced match as well. [1]
The thresholds
The rule set out the thresholds. [1] With an approved planning document in place, prior approval would be required to release solicitations or execute contracts expected to exceed $500,000. [1] An exemption from prior approval could be assumed in the planning document's approval if three things held. [1] The acquisition summary gave enough detail, the acquisition did not deviate from it, and it was not the initial acquisition for a high-risk activity such as software application development. [1]
For noncompetitive acquisitions, including amendments, expected to exceed $1,000,000, the state would submit a sole source justification. [1] If a state did not use an exemption or an acquisition checklist, it would submit contracts above set amounts before execution. [1] For software application development those were $6,000,000 competitive and $1,000,000 noncompetitive. [1] For hardware and commercial software they were $20,000,000 competitive and $1,000,000 noncompetitive. [1]
What the thresholds do to a schedule
As we see it, federal approval takes time, and time is scarce in a state IT project. In our reading, the thresholds created an incentive to structure acquisitions so they fit an exemption or a checklist. They also rewarded a planning document whose acquisition summary was detailed enough to support an exemption.
They also gave CMS a view of contracts before signature. A sole source justification over $1,000,000 put noncompetitive awards in front of a federal reviewer. [1] For a state, we think that is both oversight and a defense: a contract CMS reviewed is harder to criticize later.
Amendments and the 20 percent line
The rule also addressed contract growth. [1] For amendments within the scope of the base contract, prior approval would be required before executing an amendment involving cost increases that cumulatively exceed 20 percent of the base contract cost. [1] In response to a comment, CMS said the $500,000 threshold applied to a specific procurement or contract action, not in the aggregate. [1]
In our reading, the 20 percent line is the one that catches troubled projects. A system that runs late and over budget grows by amendment. Once the cumulative increase crosses the line, federal reviewers see the contract again. For a state, that is a natural checkpoint to decide whether to continue, restructure or rebid.
The planning document as the control point
The advance planning document sat at the center of this process. [1] It carried the named personnel, the acquisition summary and the description of commercial software costs. [1] The rule said the nature and extent of commercial software costs eligible for 90 percent funding must be expressly described in the approved planning document. [1]
In our reading, the planning document became a central procurement artifact for the state. What it said decided what could be bought at which rate, and which contracts needed separate approval. A state program office that treats it as paperwork misses that it is the contract with the funder.
A hypothetical state's procurement
Consider a hypothetical state replacing a legacy eligibility system. Under the 2015 rule, its planning document would describe the modules it intends to buy and the commercial products it expects to license. [1] It would name the state staff, and carry an acquisition summary detailed enough to support exemptions. [1]
It might buy a commercial eligibility rules engine through a competitive procurement below the $20,000,000 threshold for commercial software, and an integrator to configure it. [1] The license and configuration would draw 90 percent funding, if described in the approved planning document. [1] [2] Its custom portal development would need care: initial acquisitions for high-risk activities such as software application development fall outside the assumed exemption. [1]
The state's contract with the integrator would carry the ownership clause for anything custom, documentation sufficient for another contractor to operate it, and a plan for running it on other platforms. [1] [4] If the project later grew by amendment beyond 20 percent of the base cost, the state would return to CMS for approval. [1]
The definitions shaped the market
The rule's new definitions mattered as much as its conditions. [1] They decided which kinds of products could be bought at 90 percent.
Commercial software at the enhanced rate
The rule said development costs include the initial licensing of commercial off-the-shelf software. [1] They also include the minimum necessary costs to analyze its suitability, install, configure and integrate it, and modify non-commercial software to coordinate operations. [1] It deleted a sentence from the proposed definition that would have excluded software developed for public assistance programs, to allow its inclusion where appropriate. [1]
CMS's guidance letter of March 31, 2016 gave examples. [2] At 90 percent, it listed planning activities, interfaces, integration and configuration, contingency and security plans, initial software leasing or licensing including software-as-a-service and commercial software, and configuration and minimal customization of commercial software. [2] At 75 percent, it listed maintenance, operation, ongoing software leasing or licensing, and training of operating staff. [2]
In our reading, the split is the commercial logic of the rule. A state could buy a commercial product's first license and its configuration at 90 percent. The ongoing subscription would be paid at 75 percent. That lowered the state's cost of choosing commercial or hosted products over custom builds at the start, while leaving operating costs on the regular enhanced rate.
Shared services and hosted software
The rule's definitions opened routes beyond a state-owned build. [1] It defined a shared service as a service, including software-as-a-service, used by one part of an organization or group, including states, and made available to others. [1] It said the providing department effectively becomes an internal service provider. [1]
It defined software-as-a-service as software managed and licensed by its vendor-owner on a pay-for-use or subscription basis, centrally hosted, on demand and common to all users. [1] It defined commercial software as specialized software available for sale or lease in the commercial marketplace and usable with little or no modification. [1]
In our reading, these definitions let a state buy what another state or a vendor already runs, rather than building its own. They also raised new questions for a state program office. How should it meet the documentation and portability conditions for a hosted product it does not own? How does the ownership clause apply to a subscription? The conditions on portability were written with custom software in mind. [1]
Modules and the end of the monolith
The rule expanded the definition of the claims processing system to describe a system of systems made up of interoperable modules. [1] It said "subsystem" and "module" had the same meaning. [1] It deleted "non-proprietary" from the description of modules, removing that limitation. [1]
CMS's March 2016 letter said it believed modular development provided the most efficient and cost-effective long-term solution for states. [2] It said modular development may include commercial products or software-as-a-service. [2] Its August 2016 letter addressed modular certification of MMIS. [3]
In our reading, modularity changed the shape of procurements. A state could buy eligibility, claims, provider management and data warehouse functions as separate modules from different vendors. That lowered the stakes of any one award, and raised the importance of integration and of the state's own architecture role.
What vendors had to offer
The conditions and definitions together described what a competitive Medicaid IT offer would contain. In our reading, a vendor bidding for a 90 percent funded module needed to show four things. Its product had to fit the module definition: discrete, interoperable and reusable. [1] Its documentation had to let another contractor operate the system. [1] Its design had to minimize the cost of moving to alternate hardware or operating systems. [1] And its terms had to fit the ownership and reuse expectations for anything built with federal money. [4]
For commercial vendors, the rule's definition of commercial software was the entry point. [1] Software usable with little or no modification could be licensed and configured at the development rate. [1] [2] Heavily customized software risked falling outside that definition. In our reading, the rule rewarded products that states could adopt with configuration, and penalized the custom builds that had locked states into single vendors.
Reuse and ownership
The rule listed reuse as a subject for guidance. [1] CMS's April 2018 letter addressed it. [4] It said one of the conditions required states to promote sharing and reuse of Medicaid technologies and systems within and among states. [4]
The letter tied reuse to ownership. [4] It cited 45 CFR 95.617, which requires a clause in state procurement instruments on ownership. [4] Under it, the state or local government has all ownership rights in software and modifications designed, developed or installed with federal funding. [4] It said CMS expected states receiving federal funding to make project artifacts, documents, system components and code available to other states for reuse. [4] It said CMS was providing a reuse repository for that purpose. [4]
In our reading, the ownership clause and the portability conditions together set a floor for vendor contracts. A vendor building custom software with 90 percent federal money could not retain exclusive rights to it. A vendor selling a commercial product licensed it rather than transferring ownership, which is one reason the definition of commercial software mattered.
The proof moved from checklists to outcomes
Funding for operations at 75 percent required CMS approval of the system. [1] [5] The rule named new MMIS certification rules among its planned guidance subjects. [1] How CMS checked systems changed over the following years.
The 2016 approach
CMS's August 2016 letter addressed modular certification of MMIS. [3] A later letter recorded that the 2016 letter had discussed the Medicaid Enterprise Certification Toolkit and the Medicaid Eligibility and Enrollment Toolkit. [5] In our reading, those toolkits reflected the rule's checklist of conditions: a system was certified by showing it met them.
The 2022 shift
On April 14, 2022, CMS issued a letter introducing Streamlined Modular Certification. [5] It said that, effective immediately, it sunset the existing toolkits. [5] It said states should not use them for projects initiated after the letter's publication. [5]
The letter described the new approach as an interim step toward outcomes-based certification for Medicaid enterprise systems. [5] It said the approach was designed to demonstrate measurable improvements to a state's Medicaid program from each new module or enhancement. [5] It said the approach would use data and testing to inform CMS's assessment of delivered systems and future investments. [5]
The letter listed examples of modules in a Medicaid enterprise system. [5] They included eligibility and enrollment, claims processing, financial management, provider management, third-party liability, program integrity and health information exchange, among others. [5]
Why certification is a funding gate
Certification is the step that turns on the operations rate. [5] The 2022 letter began from the regulation that makes 75 percent funding available for operating a system approved by CMS. [5] It said that to obtain approval for any enterprise system or component going forward, states should follow the streamlined certification process. [5]
In our reading, that makes certification a revenue event for the Medicaid agency. Until a module is approved, its operations may not draw the enhanced rate. A state that delays certification planning until after go-live risks a period of operations at a lower federal share. The evidence for certification should be designed into the project from the start.
What outcomes-based certification asks of a state
In our reading, the 2022 shift completed the logic of the 2015 rule. The rule paid for modules and asked for portability and reuse. [1] Certification by outcomes asks whether each module improved the program. [5] For a state, the evidence moves from documents describing the system to data showing what it did.
That requires metrics defined before a module is built, and data collected after it goes live. A state that writes outcome measures into its planning document and its vendor contracts is ready for this approach. One that does not will struggle to show results it never measured.
The data a state needs for outcomes
Outcomes-based certification needs a baseline. In our reading, a state replacing an eligibility module should record, before the switch, the measures it expects to improve: application processing times, renewal completion through automated data checks, error rates, call center volume. The 2022 letter said its approach would use data and testing to inform CMS's assessment of delivered systems. [5]
That changes procurement documents. Vendor contracts should require the module to produce the data needed for those measures, in a form the state can use. A module that works but cannot report its own performance leaves the state unable to show the improvement certification now asks for.
The strongest case against our argument
A fair objection is that the framework was old. The 2011 rule had already codified conditions at 433.112(b) for enhanced funding, and CMS had issued its seven conditions and standards guidance in April 2011. [1] On this view, the 2015 rule changed only the time limit.
The rule itself answers part of this. [1] Its amendatory text added paragraphs (b)(17) through (22) to section 433.112. [1] It added the named-personnel condition, extended the documentation and portability conditions to eligibility systems, broadened modules and commercial software, and aligned prior approval thresholds for all Medicaid IT. [1] In our reading, more important, by making the 90 percent rate available to eligibility systems on an ongoing basis, it made those conditions lasting features of state eligibility procurement. [1] A temporary rate with conditions is a project rule. A permanent one is a market rule.
A second objection is that the enhanced rate encouraged spending, not savings. The rule's projections assumed legacy retirement that states controlled. [1] We have no source measuring actual retirement against the projection, and we make no claim either way.
A third objection is that the conditions burden smaller states most, since every state faces the same planning documents, thresholds and certification steps regardless of size. The rule did not scale its conditions by state size. [1] In our reading, the definitions of shared services and hosted software were the rule's answer: they let a smaller state use what another state or vendor already operates, rather than building and certifying its own. [1] Whether that route is practical depends on the products and partners available, which the sources we opened do not measure.
What the rule did not change
The rule did not change the statutory rates. [1] Sections 1903(a)(3)(A)(i) and 1903(a)(3)(B) set 90 and 75 percent; the rule changed which systems qualified and on what conditions. [1] It did not change the funding rules of other programs that share eligibility systems with Medicaid, which have their own federal partners. [1]
It did not settle how states would show compliance. The rule promised subregulatory guidance on the conditions, commercial software, planning documents, certification and reuse. [1] It said guidance would take precedence over obsolete content in the State Medicaid Manual until that manual was updated. [1] In our reading, that left much of the practical meaning of the rule to letters that came in the following years. [2] [3] [4] [5]
What we would tell a state Medicaid agency today
Treat the planning document as the governing contract. Name the state staff and their time, and fund those positions as part of the project. Write ownership, documentation and portability into every vendor agreement for a federally matched system, as the conditions and the ownership rule require. [4] [6]
Plan acquisitions around the prior approval thresholds and their exemptions, and put approval time in the schedule. [1] Define outcome measures for each module before procurement, since certification now asks for them. [5] And when buying commercial or hosted products, budget for the ongoing subscription at the operations rate, not the development rate. [2]
With hindsight
CMS followed the rule with the series of State Medicaid Director letters it had promised. [1] One, SMD #16-004, issued March 31, 2016, addressed enhanced funding and commercial software. [2] It said the rule had become effective January 1, 2016, and had made permanent the applicability of enhanced federal matching rates to eligibility and enrollment systems. [2]
The letter said CMS anticipated states would use the resources to further integrate with Marketplace and human service program systems while retiring outdated legacy systems. [2] It said CMS expected up-front investments in new systems to reduce long-term costs. [2] It also said eligibility systems remained subject to the Medicaid Information Technology Architecture conditions and critical success factors. [2]
The August 16, 2016 letter, SMD #16-010, described itself as the third in the series and addressed modular certification of MMIS. [3] The April 18, 2018 letter, SMD #18-005, described itself as the fourth and addressed reuse. [4] It said CMS expected states receiving federal funding to make artifacts and code available to other states, and that CMS was providing a reuse repository. [4]
On April 14, 2022, SMD #22-001 introduced Streamlined Modular Certification. [5] It sunset the certification toolkits discussed in the 2016 letter, effective immediately, for projects initiated after its publication. [5] It described the new process as an interim step toward outcomes-based certification for Medicaid enterprise systems. [5]
The conditions the 2015 rule set remain in the regulation. [6] The current text of 42 CFR 433.112, as checked on 2026-11-16, still requires key state personnel to be identified by name, type and time commitment in the planning document. [6] It still requires systems and modules developed with 90 percent match to be documented so that a variety of contractors or other users could operate them. [6] It still provides 90 percent federal funding for development of an eligibility system that meets the subpart's requirements. [6]
The 2022 letter also carried a standard notice. [5] It said its contents did not have the force and effect of law and were not meant to bind the public, unless specifically incorporated into a contract. [5] In our reading, that notice explains why the conditions in the regulation, rather than the guidance, are the firm ground for a state's contracts. [6]
What held up from December 2015 was the permanence of the rate and its conditions. [1] [6] The regulation text we checked still carries the conditions the 2015 rule added, though its source note also lists later amendments to the section in 2016, 2023 and 2024, and CMS's guidance built on those conditions for years. [2] [3] [4] [5] [6]
What changed was how CMS judged success. [5] The 2015 rule's conditions read as a checklist, and the 2016 toolkits reflected that. [1] [5] By 2022, CMS was asking states to show measurable program improvements from each module. [5]
What we cannot say from the sources we opened is whether the rule's savings projections came true. [1] The 2015 rule projected legacy system retirements and lower operating costs through 2025. [1] We found no CMS document in our sources that measured them, and we make no claim either way.
Spotted an error? Tell us and we will check it and correct the article where needed.