Book a call

Choose who to talk to

Pick who you’d like to speak with and book a time that works for you.

Dima Blyshchyk, CEO & Founder at Mitrix

Dima Blyshchyk

CEO & Founder

Max Fedaraka, Head of Business Development at Mitrix

Max Fedaraka

Head of Business Development

Industries / Healthcare / DME

DME software development from order to delivery.

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.

US DME network93% within 6 hoursHL7 / EMRHIPAA-aware
US DME network
Order 2481 · hospital bedSupplier confirmed
Delivery · Tuesday 09:00Out for delivery
Proof of deliverySigned 14:32
Claim · consolidatedReady to bill
93%orders within 6 hours
93%orders within 6h
64%faster order creation
25%lower equipment spend
2×settlement velocity
01 — Capabilities6 connected areas

What we build.

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.

01

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.

ReferralEligibilityAuthorization
02

Supplier network

Match items to suppliers by service area, stock, payer and delivery capacity. Record substitutions, approvals and network pricing.

SourcingInventorySubstitutions
03

Delivery and proof of delivery

Scheduling, dispatch, tracking and handover. Capture the recipient, signature, timestamp, items, serial or lot numbers and setup check, including offline.

DispatchPODOffline
04

Billing and reconciliation

Turn the delivery into claims-ready data. Reconcile ordered, delivered and billed quantities before the claim leaves the building.

ClaimsBillingReconciliation
05

Patient portal and resupply

Patients manage orders, resupply, documents, preferences and guest orders. The operations queue sees the same state and the reason an order is blocked.

PortalResupplyPreferences
06

Reporting and analytics

Order-to-delivery time, first-time delivery, denials, resupply due, equipment spend and settlement. Reports operations uses on Monday, not vanity dashboards.

OperationsFinanceResupply
02 — WorkflowEnd to end

The workflow we cover.

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.

01

Referral

Capture the referral, documentation and equipment need.

Intake · Documents · Validation
02

Eligibility

Check coverage, authorization and payer rules before sourcing.

Payer · Auth · Benefits
03

Supplier

Confirm stock, service area, price and substitutions.

Network · Inventory · Price
04

Delivery

Schedule, dispatch, track and capture proof of delivery.

Route · POD · Handover
05

Bill

Send claims-ready data and reconcile the loop.

Claim · Recon · Audit
06

Resupply

Check eligibility, contact the patient and start the next cycle.

Interval · Outreach · Recurring
03 — Where it breaksFour failure points

The first order is not the hard part.

The 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.

01

Eligibility checked once

Coverage and authorization change between intake, dispatch and billing. Check at each step and keep the response and timestamp.

02

Supplier availability is not a number

Service area, rental pool, stock and substitutions decide whether a supplier can actually deliver. Show confirmed availability, not a hopeful estimate.

03

Proof of delivery is still paper

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.

04

Billing reconstructs the story

Every re-keyed field is a chance to lose margin. The order should produce claims-ready data with the documentation that supports it.

04 — ModulesShipped or scoped per workflow

What the build is made of.

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.

01Order intake

Referral, patient, equipment and document validation.

02Supplier network

Availability, pricing, substitutions and approvals.

03Delivery and POD

Dispatch, tracking, signatures, serials and setup.

04Patient portal

Orders, resupply, documents, preferences and guest orders.

05EMR sync

HL7, flat files and third-party database ingestion.

06Billing and reporting

Claims-ready data, reconciliation and operational metrics.

05 — EvidencePublic proof

What it produced.

Representative healthcare work. Client names are under NDA; the workflows and numbers are what we can share.

US DME network

Hospitals, hospices and suppliers in one process

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 case
Patient portal

Orders and resupply, self-service

Patients manage orders, resupply, documents, preferences and guest orders. A browser extension gives care teams patient context and clinical fields.

Read the resupply guide
Integrations

EMR, eligibility and ERP

The platform integrates with hospice and SNF EMRs, Waystar eligibility, ERP and accounting systems, and supplier operations without re-keying the loop.

Read the integration guide
06 — ApproachBuild, buy or extend

Keep the EHR. Own the loop.

Most 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.

01

Build when the network, payer rules or delivery workflow differentiate the business.

02

Buy when the workflow is standard and the EHR module already covers it.

03

Start with one order type and one supplier group, then expand.

04

Integrate with the EHR instead of replacing it.

07 — StackChosen per constraint

What we build it with.

Existing platforms respected, new surfaces kept boring. The stack follows the integration and compliance constraints.

.NET 8ASP.NET CoreAngularAzure FunctionsAzure SQLService BusBlob StorageHL7REST APIsPlaywright
Platforms and systems
PointClickCareHomecare HomebaseNiko HealthWaystarSageDynamics GPQuickBooksInfor Lawson
08 — FAQShort answers

Questions buyers ask.

If yours is not here, send it. We answer in plain language, with the constraints we would check first.

What does DME software need to do?

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.

Can we keep our existing EHR?

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.

How long does a DME platform take to build?

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.

Which integrations matter most?

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.

Do you have DME experience?

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.

Is the platform HIPAA-aware?

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.

Bring us the workflow that hurts.

Tell us where the handoff breaks: intake, eligibility, delivery, reconciliation, billing or the patient experience.