DME face-to-face documentation: 22 codes join the list on 28 October
A dated post on purpose. The list that governs this changes on 28 October 2026, and the codes that move onto it are ones most practices order.
On 28 October 2026, 22 HCPCS codes join the required face-to-face and written order list, bringing the total to 105. DME face-to-face documentation must show the encounter occurred within the six months preceding the written order date, and for listed items the order must reach the supplier before delivery.
The six-month clock does not run to delivery. It runs to the date of the written order.
That single distinction is the most common error in practice-manager guidance on this subject, and it is the one that turns a compliant encounter into a non-compliant claim. The regulation says the treating practitioner must document and communicate to the supplier that there has been a face-to-face encounter with the beneficiary within the six months preceding the date of the written order or prescription.
Preceding the order. If the encounter happened in March and the order was written in October, the encounter is outside the window — regardless of when the wheelchair actually arrives. Practices that track this against delivery dates are measuring the wrong interval, and the error is invisible until a review.
The second reason to read this now is a date. On 28 October 2026 the list of items subject to these requirements grows by 22 codes, and the additions are not obscure. Standard and heavy-duty wheelchairs are on it.
What changes on 28 October 2026 for wheelchair order requirements
A Federal Register rule published on 30 July 2026 adds 22 HCPCS codes to the required face-to-face encounter and written order prior to delivery list. CMS states the result plainly: a total of 105 codes will be subject to face-to-face encounter and written order prior to delivery as a condition of payment.
The additions cluster in four groups. Eight wheelchair codes, covering standard, hemi, lightweight, high-strength lightweight and heavy-duty chairs along with a power wheelchair code. Three home ventilators. Seven orthoses across the lumbar-sacral, lower-limb and upper-limb categories. One oxygen system and one air-fluidized bed.
This is the second expansion in a year. A rule published on 13 January 2026 and effective on 13 April 2026 added eight oxygen codes, taking the list from 75 to 83. The July rule takes it from 83 to 105. A practice whose DMEPOS workflow was built against the 2024 list is now two revisions behind.
The distinction matters more than the numbers. The Master List is a watchlist — CMS describes it as a library of codes flagged as potential vulnerabilities. Nothing follows from membership alone. The face-to-face and written order list is the one that changes what an ordering provider has to do. The prior authorization list is a separate, additional step requiring advance approval from the contractor before delivery.
Eight of the codes moved by the July rule landed on both the face-to-face list and the prior authorization list simultaneously. For those, a practice needs the encounter, the order and the approval — three things, in sequence, before anything ships.
The DME prior authorization list has a phased rollout. This is not it
The July rule phases in prior authorization for upper limb orthoses by state: New York, Michigan, Florida and California from 28 October 2026; Pennsylvania, Massachusetts, Ohio, Illinois, Texas, Georgia, Arizona and Oregon from 26 January 2027; nationwide from 26 April 2027.
That phasing applies to prior authorization for upper limb orthoses. It does not apply to the face-to-face and written order additions, which take effect everywhere on 28 October 2026. A New Jersey practice reading the phase list and concluding it has until 2027 would be reading the wrong provision.
Written order prior to delivery: what it has to contain
Six elements, and they are shorter than most order templates assume: the beneficiary’s name or Medicare Beneficiary Identifier, a general description of the item, the quantity to be dispensed where applicable, the order date, the treating practitioner’s name or NPI, and the treating practitioner’s signature.
Two timing tiers govern where that order has to be by when. For items on the required list, the order must be communicated to the supplier prior to delivery. For all other DMEPOS, it must be communicated prior to claim submission. Moving 22 codes onto the required list moves them from the second tier to the first, which is a workflow change rather than a paperwork change.
Is your DMEPOS workflow checking the encounter against the order date?
We will look at how your system dates and sequences DME orders, and whether the codes moving on 28 October are in your check.
Face-to-face encounter timing, and why condition of payment is the right phrase
It is worth being precise about consequences, because most content on this subject is not. We could not find language in the regulation, in either 2026 rule, or in the DME contractor documentation article stating that a claim will be denied. What 42 CFR 410.38 does is categorical in a different way: the requirements described in this paragraph are conditions of payment applicable to DMEPOS items.
A condition of payment that is not met means the item does not qualify for payment. That is the accurate framing and it is strong enough. Quoting a denial sentence that no primary source contains is how compliance guidance becomes folklore.
Note also that the regulation itself was last amended in November 2023. The 2026 activity updates the lists, not the rule. Practices that checked the regulation and found nothing new have checked the wrong document — the list is where the change lives.
The DMEPOS master list is not your build list: three changes
First, make the order date the anchor. The system should refuse to finalise a DMEPOS order for a listed code unless a qualifying encounter exists within the preceding six months, measured against the order date rather than against today or against an expected delivery date.
Second, load the current list rather than a remembered one. The list has changed twice in 2026. Whatever your ordering module checks against should be a maintained reference with a version date attached, not a hard-coded set from an implementation two years ago — which is a template development decision as much as a compliance one.
Third, record how the encounter happened. Telehealth encounters qualify where the telehealth conditions are met, which is genuinely useful for wheelchair and ventilator orders where getting the patient in is the bottleneck. But qualifying depends on conditions, so the modality belongs in the record rather than being assumed. This is ordinary workflow optimization work and it is part of our EHR solutions.
DMEPOS orders and encounters: common questions
When exactly must the face-to-face encounter occur?
What changes on 28 October 2026?
What is the difference between the Master List and the required lists?
What happens if the written order does not reach the supplier before delivery?
Does HIPAA restrict sending the order and encounter note to the supplier?
Does a telehealth visit count as the face-to-face encounter?
Let’s meet
Qventive supports specialty and primary care practices across New Jersey. Thirty years healthcare IT, one team for EHR and infrastructure.
- The six-month encounter window measured against the written order date, the two order-communication tiers, the six required order elements, and the conditions of payment language. ecfr.gov
- The addition of 22 HCPCS codes, the resulting total of 105, the 28 October 2026 effective date and the phased prior authorization rollout for upper limb orthoses, published 30 July 2026. federalregister.gov
- The required face-to-face encounter and written order prior to delivery list as it stands from 28 October 2026. cms.gov
- The earlier 2026 update adding eight oxygen codes, published 13 January 2026 and effective 13 April 2026. federalregister.gov
- The Master List, the required lists and the description of the Master List as a library of codes flagged as potential vulnerabilities. cms.gov