Better tools. Better news.
Sunday, November 22, 2026 · UTC
World

CMS Establishes New HCPCS Codes for TOMAC RLS Therapy

The Centers for Medicare & Medicaid Services created new HCPCS codes for the TOMAC wearable device to treat restless legs syndrome.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 8 placed sources from 2 publishers.
The Centers for Medicare & Medicaid Services (CMS) established two dedicated Healthcare Common Procedure Coding System (HCPCS) codes for the TOMAC system effective October 1, 2024. [1] Code E0743 is billed per unit, meaning two units are required for bilateral therapy, and staff must not assume the code descriptor covers both legs automatically. [2] Payer policies commonly require documentation that the patient is refractory to medications or unable to tolerate them, such as gabapentin, dopamine agonists, or opioids. [3] The TOMAC system is classified as durable medical equipment (DME) and is priced as a capped rental rather than a one-time supply or implanted neurostimulator. [4] According to CAQH, eligibility runs 96% electronically, but prior authorization is only 40% fully electronic, and attachments sit at 24% in medical spaces. [5] CMS-0057-F requires payers to expose FHIR APIs, including for prior authorization, by January 1, 2027, which will convert execution from brittle screen-scraping into a clean engineering problem. [6] HFMA reported that up to 65% of denied claims are never reworked because there are more defensible denials than biller-hours available to defend them. [7] Most RCM AI tools function as coordination systems that recommend actions, score denials, and draft appeal letters, but they route the final task back to a person to log in and finish the work. [8]
Proof8 sources · 2 publishers
What this stands on
  1. The Centers for Medicare & Medicaid Services (CMS) established two dedicated Healthcare Common Procedure Coding System (HCPCS) codes for the TOMAC system effective October 1, 2024. · American Academy of Sleep Medicine - Association for Sleep Clinicians and Researchers
  2. Code E0743 is billed per unit, meaning two units are required for bilateral therapy, and staff must not assume the code descriptor covers both legs automatically. · American Academy of Sleep Medicine - Association for Sleep Clinicians and Researchers
  3. Payer policies commonly require documentation that the patient is refractory to medications or unable to tolerate them, such as gabapentin, dopamine agonists, or opioids. · American Academy of Sleep Medicine - Association for Sleep Clinicians and Researchers
  4. The TOMAC system is classified as durable medical equipment (DME) and is priced as a capped rental rather than a one-time supply or implanted neurostimulator. · American Academy of Sleep Medicine - Association for Sleep Clinicians and Researchers
  5. According to CAQH, eligibility runs 96% electronically, but prior authorization is only 40% fully electronic, and attachments sit at 24% in medical spaces. · Forbes
  6. CMS-0057-F requires payers to expose FHIR APIs, including for prior authorization, by January 1, 2027, which will convert execution from brittle screen-scraping into a clean engineering problem. · Forbes
  7. HFMA reported that up to 65% of denied claims are never reworked because there are more defensible denials than biller-hours available to defend them. · Forbes
  8. Most RCM AI tools function as coordination systems that recommend actions, score denials, and draft appeal letters, but they route the final task back to a person to log in and finish the work. · Forbes
1 of the 2 publishers publishes from United States. We do not know which country the other one publishes from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 8 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Tuesday, September 1, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
1 of the 2 publishers publishes from United States. We do not know which country the other one publishes from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)e22463d2b5d16b6d4160b87605f566a1693eb80388ebc8c47e704512ec45ca5b
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.