Part three of a three-part series for Mississippi rural healthcare leaders. Part one explained what HTAM is; part two covered what to document. This installment is the one that prevents expensive mistakes: what the funding will and will not pay for.
Start with the question every provider eventually asks
Once a rural provider understands that HTAM will fund technology modernization, a natural and reasonable question follows: can we use it to cover our ongoing IT and cloud costs over the next several years?
The answer is no — and understanding precisely why is the difference between an application that gets funded and one that exposes the organization to repaying the money later. This is the area where well-intentioned providers, and frankly some vendors, get the program wrong. The rules here are not fine print. They are the core design of the program, and they are enforced.
This article explains the mental model the program is built on, the specific cost rules that follow from it, and what all of it means for how a provider should plan.
The mental model: seed capital, not operating subsidy
The single most important thing to understand about HTAM — and the federal program it belongs to — is its purpose. It is transition capital. It exists to fund investments that produce lasting improvement, not to subsidize ongoing operations that will simply stop when the program ends.
The federal guidance is explicit that the funding is not intended for perpetual operating expenses, but rather for investments made within the life of the program that have a sustainable impact beyond it. The lawyers and advisors reading those rules put it more bluntly: treat this as seed capital, and be cautious about relying on it for recurring costs that will leave a hole when the money ends.
HTAM pays to build and modernize. The provider carries the cost of running what gets built. That division is not a loophole to work around — it is the entire point of the program.
Hold that distinction in mind, because every specific rule below follows from it.
The supplanting rule — the one that catches people
"Supplanting" is grant language for using new funding to pay for something you are already paying for. It is prohibited, without exception, and it is the rule that most directly answers the question this article opened with.
If your clinic already pays for cloud hosting, an EHR subscription, or managed IT out of its operating budget, HTAM funds cannot be moved underneath those existing costs. The program funds can expand or scale a program — but only the new elements. They cannot replace a funding source you already have, and they cannot duplicate costs covered by another program.
The practical line is this: a modernization project that creates a new capability — a new security monitoring system, a new HIE connection, a hardware refresh, a new clinical workflow — is fundable. The ongoing operating bill for the systems you already run is not. And critically, the new system's own ongoing operating cost, once it is built, becomes the provider's responsibility too.
This is the trap to avoid at all costs: writing an application that quietly parks existing recurring expenses on grant money. It is the most common way a well-meaning provider crosses into supplanting — and because misused funds can be clawed back, it is the most expensive mistake in the program.
The cost caps
Beyond supplanting, the program limits how much of an award can go to particular categories. These caps shape what a fundable project can actually look like, which is why a plan should be built against them from the start rather than scoped first and checked later. The figures below reflect federal program terms reported as of mid-2026; the binding percentages applicable to Mississippi providers will appear in the state's published application documents.
| Category | General limit |
|---|---|
| EMR / EHR replacement | Capped at roughly 5% of the state's award per budget period — the most constrained technology category |
| Infrastructure and capital investment | Capped at roughly 20% |
| Provider payments | Capped at roughly 15% per budget period; cannot pay for services reimbursable by insurance |
| Administrative costs | Capped at roughly 10% |
The practical takeaway for a technology project: EHR replacement is the tightest category in the program, so a plan that leans heavily on replacing an EHR will compete for a small slice of money. Cybersecurity, hardware modernization, and health-information-exchange work have considerably more room. A well-scoped plan puts the weight where the funding actually is.
What the funding will not pay for at all
Some costs are not capped — they are simply unallowable. While the binding list for Mississippi will come from the state's application documents, the federal program generally excludes:
- New construction and major building expansion;
- Cosmetic upgrades;
- Payment for clinical services that insurance already reimburses;
- Lobbying;
- Using the funds to meet the matching requirements of other federal programs;
- Pre-award costs — expenses incurred before an award is made, including the cost of preparing the application itself;
- And, as above, supplanting any existing funding source.
The pre-award exclusion deserves a moment, because it surprises people. The work a provider does to become fundable — the readiness audit, the documentation, the application preparation — cannot be charged back to the grant. That cost is the provider's to carry. It is also, deliberately, a modest cost: readiness work is meant to be lightweight precisely because the program will not reimburse it, and the substantial funded work begins only after an award.
The sustainability requirement, and why it is good news
The program does not merely permit a provider to plan for life after the funding — it expects it. Evaluators are told to favor projects that are financially viable beyond the five-year window, and to be wary of initiatives that would collapse the moment the money stops.
For a provider, this reframes the ongoing cost of a modernized environment. The monthly cost of running new systems — security monitoring, managed operations, cloud hosting for what gets built — is not a problem to hide from the application. It is the answer to a question the application asks: how will you sustain this? A provider who can show a credible plan to operate the modernized environment on its own budget is demonstrating exactly the sustainability the program is built to reward.
This is genuinely good news, and it is worth stating plainly. Because the grant cannot subsidize ongoing operations forever, the provider builds a durable operating model rather than a dependency that ends in 2030. The modernization is funded; the operation is owned. That is a healthier outcome than a temporary subsidy, and it is the outcome the program is engineered to produce.
The multi-year structure
HTAM is not a single event. The federal program runs in annual budget periods through 2030, and funding is expected each year for states that maintain an approved plan and perform. But the supplanting and sustainability rules apply every year. That means each budget period funds new qualifying work — not the continued operation of what a prior year built.
In practice, a provider's multi-year arc might look like: build and harden in year one; integrate and connect in year two; add a new capability in year three — with the grant funding each new build and the provider's own budget carrying the operation of everything already in place. New investment annually; sustained operations on the provider's books. Planned correctly, that is a five-year modernization runway, not a one-time scramble.
The compliance tail
One last rule shapes how a provider should approach the whole program: the money comes with documentation obligations, and misuse or inadequate records can trigger repayment. A provider that cannot show, in detail, that funds went to allowable purposes can be required to give them back. For an organization operating on thin margins, a clawback is precisely the outcome to avoid.
This is not a reason for caution to the point of inaction. It is a reason to treat documentation as part of the project from day one — allowable-use records, spending evidence, and a clear audit trail — rather than something assembled later if questions arise. Evidence-based execution is not just good practice here; it is financial protection.
What to do with this
Before scoping any HTAM project, a provider should be able to answer three questions clearly: Is this a new investment, or an existing cost we're trying to shift? — only the first is fundable. Does our plan respect the category caps? — if it leans on EHR replacement, it competes for a small pool. Can we sustain what we build after the grant ends? — the application expects an answer, and so will reality.
Getting these right is the difference between a project that wins funding and survives an audit, and one that is rejected or later reversed. It is exactly the kind of judgment that should sit at the front of the planning process, not the end.
BeCloud works with Mississippi rural providers to scope HTAM-eligible projects against these rules from the start — the build funded by the program, the operation sized to a rural budget for life after it. Our $500 Technology Assurance Audit produces the documented foundation that both a fundable application and a clean audit trail depend on. You can read how it fits the funding timeline on our HTAM readiness page.
This article is general information for Mississippi healthcare providers and reflects publicly reported federal program terms as of mid-2026. It is not legal, financial, tax, or grant-compliance advice, and BeCloud is not a law or accounting firm. Cost caps, allowable and unallowable uses, and compliance requirements are determined solely by CMS and the State of Mississippi and will be governed by Mississippi's published Requests for Applications and Initiative Guidance. Providers should obtain qualified professional advice and rely on official program documents before making funding decisions.