Daily Hypernovelty Lead · November 7, 2026
Medical Software Now Has a Medicare Payment Lane
The Centers for Medicare & Medicaid Services published a final rule on November 6 that gives algorithm-based clinical software a distinct place in Medicare's hospital outpatient payment system.

The Centers for Medicare & Medicaid Services published a final rule on November 6 that gives algorithm-based clinical software a distinct place in Medicare's hospital outpatient payment system. Beginning January 1, CMS will use the name Software as a Medical Service, or SaMS, and a new payment status called O1 for qualifying services.
The change moves medical software into the machinery that determines how a hospital outpatient service can be paid. It also draws a firm boundary around what the new category proves. O1 describes payment treatment. It does not establish that Medicare covers a service, that the service is medically necessary, or that an algorithm has been shown to improve care.
Medicare's Outpatient Prospective Payment System groups services into Ambulatory Payment Classifications, known as APCs. Each group has a payment amount. A status indicator attached to the service's billing code determines how that payment is handled. Under O1, qualifying SaMS receives a separate payment without the discount Medicare sometimes applies when several procedures are billed together.
For 2027, CMS is placing these services in new technology APCs and generally trying to preserve their 2026 payment levels. The agency calls this an interim policy while it develops a longer-term method for software costs and value. A payment category now exists, but the permanent rules for measuring these services are still being built.
One part of the rule shows how consequential the category line can become. CMS is moving 14 stand-alone algorithmic analyses of previously generated laboratory data from the Clinical Laboratory Fee Schedule into the hospital outpatient system. For payment purposes, the agency will treat them as "other diagnostic tests" rather than diagnostic laboratory tests.
CMS used the service descriptions attached to the billing codes to draw the line. Codes describing a separate computer-based analysis of existing laboratory data were included. Codes that combined software analysis with wet-lab work, such as physical specimen processing, stayed out of this subset. Two services may both produce an algorithm-assisted clinical result, yet their payment path can differ because one description separates the computational step and the other includes it inside a laboratory process.
Verification bottleneck
The scarce check is no longer limited to whether software produced an answer. Hospitals, developers, clinicians, and Medicare now need a record that distinguishes several different questions: how the service is classified, whether it is covered in a particular case, what evidence supports its clinical use, what oversight applies, and what it costs to operate safely.
FDA authorization adds another boundary. CMS says some SaMS must have FDA marketing authorization to receive Medicare payment, while the subset involving secondary analysis of prior laboratory data does not currently face that CMS payment condition. That does not make every service in the subset exempt from other requirements. It means the payment rule and the medical-product regulatory system answer different questions.
The final rule leaves important work open. CMS acknowledges unresolved questions about definitions, billing, cost sharing, laboratory oversight under CLIA, and the permanent payment method. The agency expects future rulemaking to refine the category.
A clean public record will therefore need to keep payment status from becoming a shorthand claim about clinical validity. A service can have a code and a payment rate while still requiring a separate coverage decision and its own evidence of safety, performance, and appropriate use.
Opportunities
Commenters told CMS that a durable payment method should account for more than a software license. They pointed to implementation, staff training, system integration, cybersecurity, monitoring, and clinician oversight. CMS said it will consider those inputs as it works on later policy.
That creates a practical builder opportunity: a SaMS evidence and cost ledger. For each service, it could preserve the code description, payment category, coverage basis, FDA status where relevant, clinical evidence, integration work, monitoring plan, human review, incidents, maintenance costs, and the source behind each claim. Such a ledger would help a hospital understand its own operating burden and prepare evidence for future rulemaking without treating O1 as a shortcut to reimbursement or clinical acceptance.
The deeper operational change is simple. Once software receives a payment lane, its surrounding work becomes visible enough to measure. The next policy fight will be over which costs count, which evidence closes the gap between payment and patient use, and who remains responsible when the software's output enters a clinical decision.
Sources
- Federal Register: CMS-1850-FC, CY 2027 hospital outpatient and ambulatory surgical center final rule published November 6, 2026; effective January 1, 2027. Relevant section: X.B.