Order intake and eligibility
Referral, patient, caregiver, prescriber, equipment and documentation in one flow. Eligibility and authorization are checked before an order reaches a supplier.
We build the platform behind a DME network: referral intake, eligibility, supplier sourcing, delivery, proof of delivery, billing and patient resupply. Designed for hospice, SNF and home equipment operations, not a generic order form.
One workflow can touch a referral, a supplier, a delivery team, a patient, a payer and an EMR. We work across the chain, or just the handoff that hurts.
Referral, patient, caregiver, prescriber, equipment and documentation in one flow. Eligibility and authorization are checked before an order reaches a supplier.
Match items to suppliers by service area, stock, payer and delivery capacity. Record substitutions, approvals and network pricing.
Scheduling, dispatch, tracking and handover. Capture the recipient, signature, timestamp, items, serial or lot numbers and setup check, including offline.
Turn the delivery into claims-ready data. Reconcile ordered, delivered and billed quantities before the claim leaves the building.
Patients manage orders, resupply, documents, preferences and guest orders. The operations queue sees the same state and the reason an order is blocked.
Order-to-delivery time, first-time delivery, denials, resupply due, equipment spend and settlement. Reports operations uses on Monday, not vanity dashboards.
Every step is a handoff. The software has to keep the state, the reason and the evidence together, or operations rebuilds the process in spreadsheets.
Capture the referral, documentation and equipment need.
Intake · Documents · ValidationCheck coverage, authorization and payer rules before sourcing.
Payer · Auth · BenefitsConfirm stock, service area, price and substitutions.
Network · Inventory · PriceSchedule, dispatch, track and capture proof of delivery.
Route · POD · HandoverSend claims-ready data and reconcile the loop.
Claim · Recon · AuditCheck eligibility, contact the patient and start the next cycle.
Interval · Outreach · RecurringThe loop breaks at the handoffs. Eligibility goes stale, a supplier cannot deliver, a signature is missing, and billing rebuilds the story from PDFs. Each break is a software problem before it is a staffing problem.
Coverage and authorization change between intake, dispatch and billing. Check at each step and keep the response and timestamp.
Service area, rental pool, stock and substitutions decide whether a supplier can actually deliver. Show confirmed availability, not a hopeful estimate.
A signature is not enough. Capture the recipient, serials, setup check, location and offline state, and give a failed delivery a reason and a next action.
Every re-keyed field is a chance to lose margin. The order should produce claims-ready data with the documentation that supports it.
Modules follow the workflow, not a product catalogue. Each one gets an owner, an integration boundary and a way to reconcile with the system of record.
Referral, patient, equipment and document validation.
Availability, pricing, substitutions and approvals.
Dispatch, tracking, signatures, serials and setup.
Orders, resupply, documents, preferences and guest orders.
HL7, flat files and third-party database ingestion.
Claims-ready data, reconciliation and operational metrics.
Representative healthcare work. Client names are under NDA; the workflows and numbers are what we can share.
Mitrix built a DME network connecting providers, hospice and SNF teams with equipment suppliers, with EMR integration, insurance checking, custom rules and reporting.
See the DME casePatients manage orders, resupply, documents, preferences and guest orders. A browser extension gives care teams patient context and clinical fields.
Read the resupply guideThe platform integrates with hospice and SNF EMRs, Waystar eligibility, ERP and accounting systems, and supplier operations without re-keying the loop.
Read the integration guideMost DME operators already have a clinical record. The gap is the orchestration between referral, supplier, delivery, billing and resupply. That is the layer worth owning.
Build when the network, payer rules or delivery workflow differentiate the business.
Buy when the workflow is standard and the EHR module already covers it.
Start with one order type and one supplier group, then expand.
Integrate with the EHR instead of replacing it.
Existing platforms respected, new surfaces kept boring. The stack follows the integration and compliance constraints.
If yours is not here, send it. We answer in plain language, with the constraints we would check first.
It should cover referral intake, eligibility and authorization, supplier sourcing, order confirmation, delivery, proof of delivery, billing and resupply. The handoffs between those steps matter more than any single screen.
Yes. Most DME operators keep the EHR as the clinical record and build an orchestration layer for the network, delivery, billing and resupply workflow. The two systems integrate instead of replacing each other.
A focused pilot on one order type can run in 4 to 6 weeks. A full network platform with supplier, delivery, billing and resupply usually takes several months, depending on integrations and payer rules.
EMR and referral sources, payer eligibility and authorization, ERP and accounting, and delivery logistics. Start with the EMR and eligibility because they remove the most manual work.
Yes. Mitrix built a US DME network with order intake, supplier sourcing, delivery, proof of delivery, patient portal, billing and reporting. The public case reports 93% of delivery orders within 6 hours and 64% faster order creation.
We build inside HIPAA-aware controls: business associate agreements, role-based access, encryption, audit logs, retention and environment separation. We support your compliance review and do not claim certifications we do not hold.
Tell us where the handoff breaks: intake, eligibility, delivery, reconciliation, billing or the patient experience.
AI Assistant