DME claims fail on paperwork that was never captured at the point of care.

The paperwork is the claim. If the certificate of medical necessity and the authorization are not captured and linked at the point of care, the denial arrives weeks later and the device has already been dispensed.

What the workflow enforces

• The clinical assessment recorded against the patient and the prescriber, before a prescription can be raised.
• The certificate of medical necessity captured as structured data, not as a scan nobody can query.
• The preauthorization request assembled with the prescription and the certificate attached, and the payer response recorded against it.
• A block on dispensing where authorization is absent, with a named override and a reason when a clinician decides otherwise.
• The full chain retained: assessment, prescription, certificate, authorization, dispensing, delivery.

That last line is what turns a disputed claim into a document you can send.

DME is physical. A device has a serial number, a warranty, a location and a patient, and losing any one of those creates a problem that paperwork cannot fix.

What we track

• Device identity: model, serial number, supplier, purchase date and warranty position.
• Where it is now, and who holds it: patient, ward, store or out for repair.
• Rental against sale, with the obligations each carries.
• Returns, refurbishment and reissue, with the device history following the unit rather than resetting.
• Stock levels against demand, so a preauthorized device is actually available to dispense.

For a provider running rentals across multiple sites, this is the difference between an asset register and a guess.

The policy leaves maintenance responsibility with the dispensing entity. Service, corrective and preventive maintenance all stay yours after the device is in the patient's home.

What the system schedules and proves

• Preventive maintenance due dates per device class, driven by the manufacturer's interval rather than by memory.
• Corrective maintenance raised against the device, with fault, action and parts recorded.
• Engineer visits, with completion evidence attached to the device history.
• Devices overdue for service surfaced before they become an incident, not after.
• A per-device service record you can produce when an assessor or a payer asks.

This is also where an ADHICS assessment touches DME, because a connected device is an information asset and its maintenance and access records are in scope.

We build the DME platform and connect it to the systems you already run, so the clinical, authorization and logistics records stop living in three places.

A typical engagement

1. Map the current path from assessment to dispensing to maintenance, and find where records go missing.
2. Build the workflow with authorization and medical necessity enforced at the point they are created.
3. Connect to the EHR for the clinical side, and to inventory and finance for the device and claim side.
4. Migrate the existing device register, serial numbers and service history.
5. Hand over with the maintenance schedule running and the audit trail populated.

It deploys inside your environment. Patient-linked device data falls under the same residency and access rules as the rest of your clinical record, so it stays where your other patient data stays.