DME claims don’t route through FISS — that system handles Part A and Part B institutional and professional claims. DME claims are processed by one of four regional DME MACs (Medicare Administrative Contractors), and DME billing software connects to them through a clearinghouse rather than a direct FISS integration.
Clearing Up the FISS Confusion
This is a common point of confusion for suppliers evaluating software, since FISS is a familiar term across Medicare billing generally. In practice, what matters for a DME supplier is whether their billing platform’s clearinghouse connection reaches the correct DME MAC jurisdiction for their service area — Jurisdiction A, B, C, or D — and whether that connection supports both claim submission and electronic remittance advice (ERA) retrieval, so payment posting can be automated rather than manually keyed from a paper EOB.
What Actually Matters for Connectivity
When evaluating any DME billing platform on this point, ask specifically which clearinghouse it uses, whether that clearinghouse has active connections to all four DME MAC jurisdictions (relevant for multi-state suppliers), and whether ERA files flow back into the system automatically for remittance posting. A platform that only handles claim submission but requires manual remittance entry hasn’t solved the full problem — automated posting is where most of the administrative time savings actually come from.
Suppliers should treat clearinghouse and DME MAC connectivity as a standard due-diligence question for any vendor, and ask for a specific example of a recent claim’s full lifecycle — submission, adjudication, and remittance posting — rather than a general statement that the system is ‘Medicare-connected.’
Multi-Jurisdiction and Ongoing Reliability
This distinction becomes especially important for suppliers operating across state lines, since a business serving patients in two DME MAC jurisdictions needs confirmation that both are actively supported, not just the jurisdiction where the company is headquartered. It’s also worth asking how the platform handles claim rejections that come back from the clearinghouse before they even reach the DME MAC — a well-configured system should catch formatting or eligibility issues at that stage and route them back to billing staff for correction, rather than letting a rejected claim sit unnoticed until someone happens to check the clearinghouse dashboard. Beyond initial connectivity, suppliers should also confirm how quickly the clearinghouse relationship adapts to DME MAC policy updates, since jurisdictional rule changes happen regularly and a lag in adoption can translate directly into avoidable denials. For suppliers who’ve experienced repeated clearinghouse-level rejections with a previous system, it’s worth asking a prospective vendor for their clearinghouse’s typical first-pass acceptance rate, since that single metric says more about day-to-day claim reliability than a general description of Medicare connectivity.
