athenahealth vs CureMD: Sliding-Fee Timing, 2026

Basic Sliding Fee adjusts when the claim is created. Post-adjudication waits until after payer adjudication. athenahealth will not let a blog post turn the second one on: a customer success manager and a waiver are required. If the center is not an FQHC and wants post-adjudication anyway, athenahealth still says speak to the CSM. Case-by-case is not a how-to step.

Registered nurses sit under SOC 29-1141 according to the U.S. Bureau of Labor Statistics. That code does not time a sliding-fee adjustment. Timing is a billing-lead job. A composite FQHC that collects income at registration and still does not know when the adjustment posts is not ready to sign a waiver. Stay on Basic until ten claims show the adjustment on create.

Key Takeaways

• Basic posts the adjustment when the claim is created. Post-adjudication waits until the balance transfers to the patient.

• Post-adjudication needs written authorization and a Technical Request and Waiver Form. A blog cannot enable it. A CSM is in the path.

• athenahealth help on this feature was last updated 28 August 2026. The legal note on that page was revised/approved 9 January 2026.

• CureMD describes automatic transfer after primary insurance pays. That is CureMD product copy, not an athenaOne setting.

• Pilot is Basic only: 10 sliding-fee claims, post-adjudication left off, no UDS rebuild. Kill the pilot if anyone enables post-adjudication from this article.

• Poverty-line dollars are UNKNOWN unless aspe.hhs.gov is opened. Do not invent FPL amounts.

Basic versus post-adjudication is a timing choice

Sliding-fee programs exist so patients below a poverty threshold pay a discounted amount. HRSA puts that program in Chapter 9 according to HRSA. Chapter 9 does not tell athenahealth when to post the adjustment. athenahealth does.

Basic mode creates the sliding-fee adjustment when the claim is created, on the help page last updated 28 August 2026, according to athenahealth. Post-adjudication waits until after the payer adjudicates and the balance transfers to the patient. Those two clocks produce two different patient statements and two different A/R pictures. Billing leads who "just want it to work like CureMD" are asking to change clocks inside a different EHR.

Federally qualified health centers are described in section 1861(aa) according to CMS. Certification does not waive athenahealth's waiver. Non-FQHC centers that still want post-adjudication are told to speak to the CSM. This page will not turn that conversation into a numbered DIY.

Reputation, follow-up, and lab-result workflows are not sliding-fee clocks. Teams that need those maps can use reputation software for medical practices, reputation-management automation, patient follow-up automation, or lab-result notification. Keep this page on when the adjustment posts.

How we evaluated Basic versus post-adjudication

Evaluation used 5 tests: when Basic posts, when post-adjudication posts, whether a blog may enable post-adjudication, whether CureMD copy is an athenahealth toggle, and whether poverty-line dollars were opened. A setting that needs a waiver fails as a how-to step.

CureMD is column three so billing leads stop hunting for a secret athenaOne switch that copies another vendor's marketing page.

Numbered path to Basic, the default pilot

Nine steps stay on Basic. Step 5 is load-bearing.

1. Confirm Sliding Fee Programs is on. If the feature is off, stop. This page does not install the module.

2. Build poverty-based plans with no range gaps. Adjacent brackets should meet. Do not invent FPL dollars here. Poverty-line amounts stay UNKNOWN until aspe.hhs.gov is opened.

3. Keep non-poverty programs separate. A prompt-pay discount is not a sliding-fee plan. Mixing them hides the adjustment you are trying to see.

4. Collect income at registration. US Tech Automations can connect the registration trigger to the income fields the sliding-fee plan reads, queue incomplete intake, and keep a human check before the claim is created.

5. Leave post-adjudication off. If someone enables it from this article, the pilot is dead. Basic is the path.

6. Create a claim and inspect the adjustment. The adjustment should be visible on the claim at create. If it is missing, fix plans and income. Do not "try post-adjudication" as a debug step.

7. Report from Report Builder. A claim you cannot report is not a finished test.

8. Watch 30-day expiration warnings. Plans that expire silently will look like missing adjustments.

9. Only then talk to a CSM about post-adjudication, and only with a written business reason. Bring the ten-claim Basic evidence. Do not bring this blog as permission.

US Tech Automations can connect the registration trigger to a claim-create inspection step, then queue claims that lack a visible sliding-fee adjustment instead of flipping a restricted mode. Post-adjudication stays off.

If, and only if, the waiver exists

athenahealth help last updated 28 August 2026 states that post-adjudication requires written authorization and a Technical Request and Waiver Form according to athenahealth. Quote, not paraphrase:

Post-adjudication requires written authorization and a Technical Request and Waiver Form. Basic creates the adjustment when the claim is created. Post-adjudication waits until the balance transfers to the patient.

The legal note on that help page was revised/approved 9 January 2026. That note is about authorization. It is not about orchestration. Do not soften it into "your team can turn this on after a meeting." Written authorization. Technical Request and Waiver Form. CSM.

After the setting is lawfully on, post-adjudication can exclude services by department, rendering provider, procedure-code group, modifier, or code. Those exclusions are not a DIY checklist on this page. They exist after the waiver. Listing them as enablement steps would pretend a blog can finish the legal path.

Do not invent waiver form IDs. Use the name athenahealth uses: Technical Request and Waiver Form. If your CSM sends a different packet, follow the packet, not a blog filename.

CureMD timing contrast

CureMD's FQHC page states sliding-fee adjustments transfer automatically upon payment even with primary insurance, 1 EHR's copy rather than an athenaOne step, according to CureMD. That is their product copy. It is not an athenahealth setting. Do not tell an athenahealth shop to "do what CureMD does" inside athenaOne.

A billing lead who wants CureMD's clock has two honest options: stay on athenahealth Basic, or start a CSM-and-waiver conversation about post-adjudication. There is no third option called paste CureMD behavior into a hidden toggle. Centers shopping EHRs can read CureMD as contrast. Centers already on athenahealth cannot import it.

Healthcare automation benchmarks will not time this adjustment either. Benchmarks do not replace the waiver.

Feature matrix: clocks, not EHR shopping

This matrix is for an athenahealth shop that heard about CureMD timing. It is not an EHR replacement guide.

Pricing and TCO with UNKNOWN dollars

athenahealth and CureMD commercial SKUs are UNKNOWN on this page. Sliding-fee timing is not a price war. Orchestration, if used, is Growth $372/mo annual as of September 1, 2026, and it does not buy a waiver.

Contact athenahealth for platform dollars. Contact CureMD for platform dollars. Do not treat a sliding-fee timing article as an EHR RFP.

Dated numeric controls you can copy

Copy help-page dates, pilot counts, and policy zeros.

Limitations

Poverty-line dollars are UNKNOWN unless aspe.hhs.gov is opened. Do not paste last year's FPL from memory. Build plans with no range gaps once you have the official table.

The legal note is about authorization, not about a workflow vendor. Quote it. Do not paraphrase it into a softer enablement. Written authorization and a Technical Request and Waiver Form remain required for post-adjudication.

CureMD remains contrast. athenaOne does not grow a CureMD toggle because a blog compared them.

US Tech Automations is the wrong buy when the center actually needed a CSM conversation about post-adjudication. Orchestration cannot sign a waiver. Orchestration cannot be the CSM. A join that collects income at registration and checks for a Basic adjustment is in scope. A join that flips post-adjudication is not.

Non-FQHC centers do not get a secret how-to. athenahealth still says speak to the CSM. Case-by-case stays case-by-case.

Do not rebuild UDS in the pilot. Ten claims are enough to see the create-time adjustment. UDS is a different project with a different owner.

A join that still needs a human income review can sit on agentic workflows while claims without a visible Basic adjustment wait in a queue. Humans remain on income attestation and on any CSM conversation.

Pilot: Basic mode, ten claims

Basic mode only. Ten sliding-fee claims. Success is a visible adjustment on the claim without a waiver conversation. Kill the pilot if anyone enables post-adjudication from this article. No UDS rebuild.

Composite path: ten sliding-fee visits in one department. Income collected at registration. Post-adjudication off. Ten claims created. Ten adjustments visible. Report Builder lists ten. Two plans were about to expire inside 30 days; those warnings were logged, not ignored. Zero CSM tickets. Zero waiver forms. If claim 7 lacks an adjustment, fix the plan gap. Do not enable post-adjudication to "catch" claim 7.

If a director asks to match CureMD's auto-transfer, the answer is this page's direct answer, not a setting change. Schedule the CSM only after Basic evidence exists.

Income at registration, not at checkout

Basic posts at claim create. Income that arrives at checkout arrives after that clock. Registration has to collect household size and income, or the plan cannot choose a bracket, or it chooses a stale bracket. Stale brackets look like wrong adjustments, which look like a reason to "try post-adjudication." They are not. They are late income.

Front desk will want a short form. A short form that skips household size is not short. It is incomplete. Queue incomplete registrations. Do not create the sliding-fee claim until the fields the plan reads are present. Non-poverty discounts can wait in a different bucket. Mixing them with sliding-fee plans was already forbidden in step 3.

Self-attestation still needs a stored record. If income lives only in a paper clipboard, Report Builder will not save you later. Store the attestation with the registration, with a date. When the 30-day warning fires, you need to know which attestation is expiring.

Do not invent FPL dollars while you wait for aspe.hhs.gov. You can still confirm Sliding Fee Programs is on, separate non-poverty plans, and leave post-adjudication off. You cannot honestly finish step 2 without the table. If the table is missing, the ten-claim pilot waits. It does not get replaced by a waiver conversation.

Composite noise: ten registrations, two missing household size, one with income added at checkout. Those three never enter the ten-claim proof. Seven claims with complete registration income, Basic on, post-adjudication off, visible create-time adjustments, are a smaller honest set. Padding to ten with checkout income is how the clock looks broken.

What Report Builder must show on the ten claims

Report Builder is the proof Basic worked. A billing lead who inspected ten claims in a worklist but cannot list them in a report will not survive a CSM conversation later. The report needs claim ID, service date, sliding-fee plan name, adjustment amount, posting timestamp relative to claim create, and a yes/no that post-adjudication is off. If the adjustment amount is blank, the claim is a miss even if someone "saw it on the screen."

Thirty-day expiration warnings belong on a second list, not mixed into the ten-claim proof. A plan that expires during the pilot will look like a missing adjustment. Log the warning. Renew or rebuild the plan with no range gaps. Do not treat expiry as a reason to enable post-adjudication.

Department mix will hide misses. Ten claims from one department is the pilot. Ten claims from five departments is a UDS-shaped project you were told not to start. Stay in one department so a missing adjustment has one owner.

Income collected after claim create will also hide misses. Basic posts at create. Income entered at checkout is too late for that clock. Registration collection in step 4 exists so create has something to read. If registration skipped income, the claim should not have been created as a sliding-fee claim.

Composite noise: ten dental sliding-fee claims, one plan, post-adjudication off. Report Builder lists ten IDs, ten adjustments, ten create-time posts. Two expiration warnings were logged on a different plan that was not in the ten. Zero waiver forms. If the director then forwards a CureMD screenshot, the answer is still the timing contrast section, not a setting change.

Keep the report. The CSM conversation in step 9, if it ever happens, should start from those ten rows, not from a vendor brochure.

FAQs

Can we turn on post-adjudication from this article?

No. Post-adjudication requires written authorization, a Technical Request and Waiver Form, and a CSM. A blog cannot enable it. Leave it off for the ten-claim Basic pilot.

When does Basic post the sliding-fee adjustment?

When the claim is created, on the athenahealth help page last updated 28 August 2026. Inspect the claim. If the adjustment is missing, fix plans and income. Do not switch modes as a debug step.

When does post-adjudication post?

After payer adjudication, when the balance transfers to the patient. That clock is not available as a how-to on this page.

Does CureMD's automatic transfer work inside athenaOne?

No. CureMD's FQHC page is CureMD product copy. Do not tell an athenahealth shop to do what CureMD does inside athenaOne.

What if we are not an FQHC and still want post-adjudication?

athenahealth still says speak to the CSM. Case-by-case is not a numbered enablement path.

Do we need poverty-line dollars before the pilot?

You need plans with no range gaps. The dollar table is UNKNOWN here until aspe.hhs.gov is opened. Do not invent FPL amounts. Do not rebuild UDS in the ten claims.

Basic is the clock you can run without a waiver. Collect income, leave post-adjudication off, and inspect the adjustment on claim create. US Tech Automations can connect the registration trigger to that Basic inspection step, queue missing adjustments, and will not sell post-adjudication as a toggle.