How DMEDesk works

From intake to return-to-service in one workflow.

Start with your existing patients and equipment. Each order stays connected from the first request to delivery, billing, pickup and maintenance.

Preview an order →See the launch plan
  1. 01 · Review the orderDocuments and requested equipment
  2. 02 · Assign the unitSerial number and availability
  3. 03 · Deliver and signDriver stop and signed POD
  4. 04 · Invoice the serviceContract rate and billable dates
  5. 05 · Pick up and maintainHeld until inspection releases it

Core first. AI when it is ready.

Launch

A real launch, not a sandbox.

Target: about two weeks for qualified shops with clean data. Scope and data readiness set the actual schedule; it is not a guarantee.

  1. 01 · Map

    Bring the records you have.

    Patients, coverage, catalog, serials, rentals, orders and documents. Source IDs are preserved and rejected rows are reviewed.

  2. 02 · Review

    Nothing applies silently.

    Dry-run totals, change previews and owner sign-off. Re-importing the same file does not create duplicate records.

  3. 03 · Run

    One accountable cutover.

    Set the source of truth, train each role, and complete a delivery, pickup and invoice. A full export stays available.

Changes apply only with owner approval.Explore import / sync / export ↗

First-release scope

What “sync” means in the first release.

Explicit file workflows and reviewed changes. No connector is advertised that does not exist.

Versioned CSV imports, not a one-click connector

Re-import or upsert using stable source IDs, review conflicts and approve changes. No one-click Brightree or NikoHealth connection is advertised.

Accounting stays explicit

A restricted accounting export can support your bookkeeper. There is no automatic QuickBooks payment sync in the first release, and no patient details go into accounting exports without an approved lawful data path.

Work-account sign-in is planned

Google Workspace and Microsoft 365 sign-in are planned. Sign-in does not sync operational data.

AI is a separate readiness gate

The future Growth intake assistant cites its source and asks staff to approve. Core operations do not depend on AI availability.

Explore the Acme demo

Review the Acme workspace.

Explore fictional orders, inventory, deliveries, maintenance and hospice billing.

Explore the workspace →See how it works ↗PlatinumMED example ↗
Interactive design concept · Fictional records · Not a live operations system