DME ordering software digitizes how durable medical equipment and supplies (DMEPOS) are ordered for a patient: capturing the order, documenting medical necessity, verifying insurance, collecting the physician's signature, and recording proof of delivery. LucasAI adds AI-assisted documentation and built-in Medicare compliance checks to every one of those steps, so orders are complete and audit-ready before they ship, not after a denial.
Today, LucasAI DME ordering is built for insurance-based wound care: collagen dressings and the secondary dressings that go with them, for chronic and post-surgical wounds. The ordering practice and the manufacturer work on one shared order, with every document, signature, and status change in one place.
Why DME orders get denied
DME claims are reviewed against detailed coverage rules. For wound care dressings, reviewers working from Medicare's Surgical Dressings LCD (L33831) look for a valid standard written order, wound assessments with measurements and exudate, a product and size that fit the wound, the right HCPCS codes, and proof that the patient actually received the supplies. Missing any one of these can turn a sound clinical decision into a denied claim or a failed prepayment review.
In most practices that documentation is still assembled by hand. Demographics are re-keyed from a facesheet, a medical necessity letter is written from scratch, signatures are chased by phone and fax, and delivery slips are filed on paper. Problems surface weeks later, when the claim is reviewed. LucasAI moves those checks to the moment the order is created.
| Step | Manual DME ordering | With LucasAI |
|---|---|---|
| Order intake | Demographics and insurance re-keyed from the facesheet | Pre-filled from the uploaded facesheet and clinical documentation |
| Medical necessity | Written from scratch for every order | AI-drafted from the clinical documentation, regenerated on demand, reviewed by the physician |
| Product and HCPCS | Chosen by hand, so size and code mismatches slip through | Size and HCPCS code calculated from the wound measurements |
| Compliance | Gaps found at review, after the claim is filed | Checked against MAC requirements before the physician signs |
| Insurance | Phone calls and payer portals | Verified automatically when documents are uploaded |
| Signature | Printed, signed, and sent back | PIN e-signature after reviewing the full order |
| Proof of delivery | Paper slips that are easy to lose | QR scan, patient e-signature, and a timestamped PDF record |
| Audit response | Documents gathered from several systems | Audit packet and a full ZIP download from the order |
How DME ordering works in LucasAI
Every order follows the same six steps, from the first upload to the patient's signature on delivery.
- UploadDrop in the patient facesheet, clinical documentation, and wound photos, then pick the wound type and date of service. LucasAI extracts the details to pre-fill the order and starts insurance verification in the background.
- CompleteA guided form walks through Patient, History, Wounds, Necessity, and Sign. Products, sizes, and HCPCS codes are calculated from the wound, the medical necessity is drafted for you, and a completion guide jumps to the next incomplete item.
- SignThe assigned physician scrolls through the full order, accepts the electronic signature consent, and signs with a PIN. Only the assigned physician can sign.
- ReviewThe manufacturer reviews the insurance verification and the CMS-1500 claim form, selects a credentialed DME supplier, and approves the order, or sends it back with the additional information needed.
- ShipThe carrier and tracking number are recorded, a packing slip is generated and attached, and the practice can track the shipment right from the order.
- DeliverThe patient scans the QR code on the package, verifies their identity, and signs. A proof of delivery record is generated and the order is marked delivered.
Each order moves through clear statuses on a board or table view, so everyone knows what is waiting on whom:
Orders that need more information move to Additional Info Needed with the reasons attached, and return to the flow once the practice responds.
Medicare compliance, checked before signature
LucasAI maps every order to its Medicare DME MAC from the patient's state: Noridian for jurisdictions A and D, CGS for jurisdictions B and C. A color-coded compliance shield on every order shows what share of that contractor's prepayment review requirements the order meets, and its readiness level:
The requirements cover the areas a reviewer checks: Standard Written Order, Medical Records, Collagen Coverage Criteria, Claim Requirements, and Supporting Documents. Before an order goes to the physician, an order completion guide lists anything still missing and jumps straight to the next incomplete item, so staff fix gaps now instead of guessing what an auditor will ask for later.
Guardrails while the order is built
LucasAI applies the Surgical Dressings LCD (L33831) as the order is filled in, not after it is submitted:
- Exudate is required. An order with no documented exudate cannot be submitted, because the LCD requires it for collagen coverage.
- Admissibility warnings. Wounds that may not qualify, for example because of heavy exudate, partial-thickness depth, or staging, are flagged on the spot.
- Contraindications stop the order. If collagen is contraindicated, such as with active vasculitis or third-degree burns, product selection is disabled until a signed clinical addendum justifies the order.
- Wound-specific diagnosis codes. LucasAI checks for a wound-type ICD-10 code (for example L89.x, L97.x, E11.62x, or Z48.0x) and lets you mark the primary diagnosis.
- Timing rules. Home Health patients' dressings must ship before the episode start date, and orders respect a 3-day processing window.
Changes after signature stay on the record
When something needs to change after the physician signs, it is documented with a clinical addendum: quick picks such as "Change in clinical status" or "Wound has improved with treatment", voice dictation, and PIN signature. If the order changes after an addendum is signed, LucasAI asks for a signed amendment. Signed addenda are append-only, so the audit trail stays intact.
Automatic product sizing and HCPCS codes
A dressing that doesn't match the wound, or a code that doesn't match the dressing, is one of the easiest ways for a correct order to fail review. LucasAI calculates both from the wound itself:
- Collagen size from wound measurements. The pad size is selected from the wound's length and width using a sizing matrix, and the HCPCS code follows the product: A6021 for the 1x1, 2x2, and 4x4 pads (16 sq in or less) and A6023 for the 7x7 and 5x10 pads (over 48 sq in).
- Tunneling handled automatically. When tunneling is documented, collagen powder (A6010) is selected.
- Linked secondary dressings. The secondary dressing is chosen from the exudate amount and sized to cover the primary product. It stays linked, so it updates whenever the primary changes.
- Overrides are visible. A supervisor can choose a size outside the matrix, but LucasAI marks it as an override that may draw scrutiny on audit.
Diagnoses are captured as ICD-10 codes on the order, and the claim line summary includes the wound-count modifiers payers expect. For coding across the rest of the encounter, see LucasAI medical coding.
See DME ordering with your own orders
Walk through an order from upload to proof of delivery with our team.
Insurance verification on upload
With the insurance verification add-on, LucasAI verifies coverage as soon as the facesheet is uploaded and fills the results into the order. If the payer on file can't be found, insurance discovery suggests the likely payer for you to apply. The verification report covers:
- Financial responsibility: deductible, out-of-pocket maximum, and coinsurance.
- Coverage details for wound care supplies and collagen products.
- Authorization and referral requirements, including existing authorizations and approved units. See also Prior AuthAI.
- Payer details: payer ID, filing limit, and claims address.
- DME contact information: NPI, PTAN, and NSC.
Plan types include HMO, PPO, EPO, POS, and HDHP plans, Medicare Part B and Medicare Advantage, Medicaid, Tricare, and VA.
Audit-ready documents, generated for you
Every document an order needs is generated from the order itself, so records are ready before a payer or auditor asks for them.
MAC audit packet
One PDF, organized the way a Medicare reviewer reads it:
- Letter of medical necessity, with a list of enclosed documentation
- Standard written order for surgical dressings
- Medical necessity narrative written to LCD L33831
- Patient risk profile with complicating factors
- Dressing size justification
- Wound assessment details for each wound
- Claim line summary with HCPCS codes and modifiers
- Compliance attestation and audit trail
CMS-1500 claim form
Filled in automatically from the order and reviewed by the manufacturer before approval.
Insurance verification report
Coverage, financial responsibility, and authorization requirements in one PDF.
Order form and addenda
The signed order, with any clinical addenda attached.
Packing slip
Generated and attached when the order ships.
Proof of delivery record
The patient's signed delivery confirmation, with time and device details.
Single ZIP download
Every document on the order in one download, ready to send to a payer or auditor.
QR proof of delivery
Medicare expects DME suppliers to keep proof that the patient received their items. LucasAI makes that part of the delivery itself:
- Every shipment carries a QR code linked to the order.
- The patient scans it and reviews the delivery details: prescriber, DME supplier, and the products delivered.
- They take a quick identity verification photo and sign on their phone.
- LucasAI records when, where, and on which device the signature happened, and attaches a Proof of Delivery electronic record PDF to the order.
The order moves to Delivered on its own. For packages that can't be scanned, a manual delivery override keeps the record complete.
One shared order for practice and manufacturer
Practice staff, physicians, and the manufacturer's team all work from the same order, with Overview, Conversation, Attachments, History, and Internal Notes in one drawer, instead of an email thread.
- Board and table views with filters, search, and a mobile-friendly board for reviewing orders on the go.
- Conversation on every order, with attachments, @-mentions, and voice dictation.
- Urgent flags and scheduled email reminders for orders that can't wait.
- Notifications your way. Choose email, in-app, both, or off for order progress, action needed, and EOBs received, and optionally only for orders assigned to you.
- A "since you've been gone" digest of what changed while you were away and what needs your attention.
- Export orders to a spreadsheet or a printable PDF, with presets for shipping, billing, or everything.
- English and Spanish interface.
- Security built in. Access to patient information is audit-logged, and signatures are captured with explicit electronic signature consent. Read more on HIPAA & security.
Onboarding happens in the app too. Practices sign their required account documents online and set up billing, either with their own DME company or through the manufacturer's credentialed DME supplier.
DME medical necessity in the clinical note
DME needs often come up in the exam room before anyone thinks about an order. When equipment such as a wheelchair, walker, hospital bed, nebulizer, commode, oxygen, or CPAP is discussed during the visit, LucasAI's ambient scribe adds a DME Medical Necessity section to the note:
- One entry per item, with a suggested HCPCS code, the supporting ICD-10 diagnosis, functional limitation, duration of need, face-to-face encounter, and alternatives tried. Only what was said in the visit is documented. Nothing is inferred.
- A documentation check compares each item to its Medicare LCD criteria and flags what is missing, for example "Missing: Home accessibility" for a manual wheelchair.
- Diagnosis codes stay in sync. If the supporting diagnosis isn't among the encounter's ICD-10 codes, add it in one click. Non-billable category codes are flagged so you can pick a specific one.
- It goes to the EHR with the note. The section is pasted into the EHR with the rest of the documentation, while the checks stay in LucasAI.
The section is available in primary care, home and assisted-living, transition-of-care, pulmonology, and neurology notes. For chiropractic practices, a DME prescriber in the follow-up note produces a medical-necessity certification for devices such as TENS units, cervical collars, and lumbar and knee orthoses, with diagnoses, duration of need, and provider auto-sign in one click.
Who it's for
- Wound care clinics and practices, including podiatry, that order collagen and secondary dressings for chronic and post-surgical wounds.
- Practices caring for Home Health and SNF patients, where care setting and ship dates affect what gets covered.
- Wound care manufacturers and DME suppliers who review, approve, ship, and defend orders, with credentialed DME management, claim form review, and audit packets.
- Billing and compliance teams who need clean claims and a fast, complete answer when a MAC asks for records.
DME ordering is part of LucasAI, the ambient AI clinical platform built by providers. Explore the rest of the platform on the features page, or contact us to set up DME ordering for your practice or company.
Frequently asked questions
What is DME ordering software?
DME ordering software digitizes how durable medical equipment and supplies are ordered for a patient: capturing the order, documenting medical necessity, verifying insurance, collecting the physician's signature, and recording proof of delivery. LucasAI adds AI-assisted documentation and built-in Medicare compliance checks to each of those steps.
Which DME products does LucasAI support?
DME ordering in LucasAI currently supports insurance-based wound care: collagen dressings (pads and powder) and the secondary dressings used with them, for chronic and post-surgical wounds. Separately, the ambient scribe documents medical necessity for equipment discussed during a visit, such as wheelchairs, walkers, hospital beds, and nebulizers.
How does LucasAI help DME orders pass Medicare review?
Each order is mapped to its Medicare DME MAC (Noridian or CGS) from the patient's state and checked against that contractor's prepayment review requirements and the Surgical Dressings LCD (L33831). A readiness level, from Audit Ready to Will Not Pass Review, shows where the order stands, and inline guardrails and a completion guide catch gaps before the physician signs.
Does AI write the medical necessity documentation?
LucasAI drafts the medical necessity narrative from the uploaded clinical documentation, and you can regenerate it at any time. The physician reviews the full order before signing it. The narrative is included in the MAC audit packet alongside the letter of medical necessity, standard written order, and wound assessments.
How does DME proof of delivery work in LucasAI?
Every shipment carries a QR code linked to the order. The patient scans it, reviews what was delivered, takes an identity verification photo, and signs on their phone. LucasAI records when and where the signature happened and generates a proof of delivery PDF that is attached to the order.
Does LucasAI verify the patient's insurance?
Yes, with the insurance verification add-on. Coverage is verified automatically when the facesheet is uploaded, and the results, including deductible, coinsurance, coverage for wound care supplies, and prior authorization or referral requirements, are filled into the order. If the payer on file can't be found, insurance discovery suggests the likely payer.
Do we need our own DME company to use LucasAI DME ordering?
No. Billing setup supports practices that have their own DME company, by entering its NPI, PTAN, NSC, and Tax ID, as well as practices that bill through the manufacturer's credentialed DME supplier.
Is LucasAI DME ordering HIPAA compliant?
DME ordering is part of the LucasAI platform, which follows HIPAA-compliant security policies, encrypts protected health information in transit, and works under Business Associate Agreements. Within DME orders, access to patient information is audit-logged and signatures are captured with explicit electronic signature consent.
How do I get started with LucasAI DME ordering?
Book a demo with the LucasAI team. Setup includes enabling the DME product line for your practice, signing the required account documents online, and configuring DME billing, either with your own DME company or through the manufacturer's credentialed DME supplier.
Does LucasAI make the coverage decision?
No. LucasAI helps assemble a complete, compliant order and its documentation. The physician remains responsible for the order and its medical necessity, and the payer makes the coverage decision. Compliance checks reflect Medicare documentation requirements and are not a guarantee of payment.
LucasAI is an ambient AI clinical platform built by providers, based in Miami, FL. DME ordering supports documentation, compliance checking, and order management; it does not make coverage determinations or guarantee payment. Coverage criteria, LCDs, and documentation requirements vary by payer and change over time, and HCPCS codes, LCD references, and MAC jurisdictions are provided for reference. All orders are reviewed and signed by the prescribing physician. This page is informational and is not legal, billing, or compliance advice.