Change record: Seven additional DMEPOS codes enter nationwide required prior authorization
CMS added five orthoses codes and two pneumatic compression device codes to the DMEPOS Required Prior Authorization List effective April 13, 2026.
What changed
CMS added five orthoses codes and two pneumatic compression device codes to the DMEPOS Required Prior Authorization List effective April 13, 2026.
This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.
Operating consequence
DME suppliers and patient-access teams need code-level, date-specific requirement discovery and must also track supplier exemption status.
Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.
Capabilities to revisit
Authorization Requirement Discovery
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for authorization requirement discovery.
Clinical Documentation Assembly
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for clinical documentation assembly.
Authorization Status Tracking
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for authorization status tracking.
Audit Trail And Decision Provenance
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for audit trail and decision provenance.
Questions for operating teams
- Which exact population and effective date does the source establish?
- Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
- What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
- What test case would show whether the operational consequence has reached production?
- What record will close, defer, or supersede this review?
Evidence boundary
The source class is Federal program update. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.