Quick answer: Fax triage software classifies inbound PAP compliance downloads, certificates of medical necessity, DME supplier forms, and payer documentation requests as their own document types, extracts the compliance data payers require — nights used, hours per night, the adherence window — and routes each one to the person who has to act on it before the deadline. That's the difference between a compliance download that reaches your DME coordinator the day it arrives and one that sits in a general fax queue until the coverage window has already closed.
Why DME and PAP paperwork is the worst fax workflow in the practice
Ask a pulmonary practice administrator which document type causes the most trouble and the answer is rarely sleep studies. It's the paperwork that follows them.
Three things make this workflow break more reliably than any other.
The documents arrive on someone else's schedule. A DME supplier sends a compliance download when their reporting cycle produces it, not when your practice is ready. A payer sends a documentation request when their review process reaches the claim. Neither event is on your calendar, which means nobody is watching for it.
The formats are all different. Every supplier has its own compliance report template. Certificates of medical necessity and written orders vary by payer and by supplier. There's no standard layout for a classifier — or a staff member — to anchor on.
The clock is unforgiving. Medicare's coverage standard for PAP therapy requires documented use of at least four hours per night on at least 70% of nights during a consecutive 30-day period within the first 90 days of therapy, plus a follow-up visit documenting clinical benefit (CMS LCD L33718). Seventy percent of thirty nights means the patient has to hit four hours on at least 21 of them. If the download proving it lands in a queue nobody works for a week, the practice may miss the window to act on a patient who was trending toward failure — and the resulting denial isn't a billing problem, it's a patient who loses device coverage.
None of that gets fixed by faster fax delivery. It gets fixed by recognizing what the document is on arrival and putting it in front of the right person with the deadline attached.
The document taxonomy this workflow actually needs
Generic fax triage buckets — referral, lab, correspondence — collapse this entire category into "other." A pulmonary practice needs these as distinct types:
- PAP compliance downloads. Device usage data from the supplier or the device manufacturer's portal, printed and faxed. The single most deadline-sensitive document in the set.
- Certificates of medical necessity and written orders. Supplier-initiated paperwork requiring a physician signature, often with a turnaround expectation the supplier states on the form.
- DME supplier confirmations and delivery tickets. Lower urgency, but they close the loop on whether the patient actually received equipment.
- Payer requests for additional documentation. Usually tied to a pending or denied claim with a response deadline.
- Oxygen qualification and recertification paperwork. Its own recurring cycle, with its own testing and documentation requirements.
- Resupply authorization requests. Recurring, high volume, and mostly routine — which is exactly why they get deprioritized until they aren't routine.
Each of those goes to a different person and carries a different clock. That's the whole argument for treating them as separate classes rather than as one "DME paperwork" bucket.
What should the software extract from a compliance download?
Classification gets the document to the right desk. Extraction is what lets the practice act without reading the page.
From a PAP compliance download, the fields that matter are the reporting period start and end dates, total nights in the period, nights with usage of four or more hours, percentage of nights meeting the threshold, average usage hours, and the device serial number tying the report to the right equipment. Those six values are the entire adherence determination.
From a CMN or written order, extract the ordering physician, the equipment and HCPCS codes, the length of need, the date the supplier needs it back, and whether a signature is already present.
From a payer documentation request, extract the payer, the claim or reference number, the specific documents being requested, and the response deadline. That last field is what turns a piece of paper into a task with a due date.
Honey Health's Fax Triage and Data Fetching agents pair at exactly this step — classifying the document type on arrival, pulling the structured values, and writing them into the chart alongside the filed image rather than leaving the numbers locked inside a PDF nobody will open twice.
How does deadline-aware routing work in practice?
Routing without a deadline is just a nicer inbox. The useful pattern attaches time to every task the moment the document is classified.
For a compliance download, the routing rule should do three things at once: file the report to the patient's chart, create a task for the DME coordinator, and set the task's due date from the adherence window rather than from the date the fax arrived. A download showing a patient at 40% adherence on day 55 of a 90-day window is a different task than one showing 85% on day 88, and the system should be able to tell them apart from the extracted values.
For a payer documentation request, the deadline comes off the letter. Extract it, set the task due date, and escalate on a schedule rather than waiting for someone to notice.
For CMNs and written orders, route to whoever handles physician signatures with the supplier's requested turnaround attached.
Two configuration details separate a working setup from a frustrating one. Route to a role, not to an individual — the person who owns DME paperwork changes, and rules pointed at a named user break silently when they go on vacation. And build an escalation path, so a task that ages past a threshold surfaces to a supervisor rather than aging quietly.
Building an audit trail that survives a payer review
The compliance value of this workflow is separate from the efficiency value, and it's the one that matters when a payer asks questions months later.
For any document the system files, you should be able to reconstruct: what it was classified as, what confidence the match carried, which chart it landed in, what values were extracted, who reviewed it if anyone did, and when each of those happened. That's not an exotic requirement — it's the same standard any document-handling process should meet — but it's worth confirming during vendor evaluation rather than assuming.
The practical test is to ask a vendor to show you the audit view for a single filed document, not a summary dashboard. Dashboards show throughput. Audit trails answer the question a payer or an auditor actually asks, which is always about one specific patient and one specific date.
Retention matters too. Ask how long the vendor stores the original fax image, whether your practice can export it, and what happens to the record if you leave. A compliance trail that lives only in a vendor's system is a compliance trail with an expiration date.
What automation does not fix
Being honest about the limits is what makes the rest credible.
Fax triage software cannot make a DME supplier send a compliance download that the supplier never generated. If a patient's device isn't transmitting, or the supplier's reporting cycle is slow, or the paperwork simply wasn't sent, no amount of inbound classification produces it. That's an outbound follow-up problem, and it needs a tracking mechanism on your side — a list of patients in an active adherence window with an expected download date, checked against what actually arrived.
It also can't resolve genuinely illegible transmissions, split multi-patient batch faxes with perfect reliability, or make a clinical judgment about whether a marginally adherent patient should continue therapy. Those stay with people.
What it does fix is the failure mode where the document arrived, on time, and nobody saw it. In most practices that's the majority of missed deadlines — not documents that were never sent, but documents that were sent and swallowed.
Frequently Asked Questions
Can fax triage software read PAP compliance data off a supplier's report?
Yes, when the report arrives as a clean digital fax with the usage table in text. Supplier report formats vary, so accuracy is highest on templates the classifier has seen. Ask a vendor to run extraction against reports from your actual DME suppliers during evaluation rather than a generic sample.
Does this help with Medicare's 90-day PAP adherence requirement?
Indirectly but meaningfully. The software doesn't change the requirement — at least four hours per night on 70% of nights in a consecutive 30-day period within the first 90 days. What it changes is whether the download proving it reaches your DME coordinator in time to act on a patient trending toward failure.
What happens to a document the system can't classify?
It routes to an exception queue rather than filing incorrectly. New supplier templates are the most common reason a DME document lands there. Once the classifier has seen a few examples of that supplier's format, the review rate for it drops.
Can it set task due dates from a payer's response deadline?
That depends on the platform, and it's worth asking directly. The capability requires extracting the deadline from the letter and using it to drive the task rather than defaulting to the arrival date. A system that only timestamps arrival leaves the deadline tracking to a person.
How do we keep an audit trail for payer reviews?
Ask any vendor to show you the per-document audit view: classification, confidence, chart matched, values extracted, reviewer, and timestamps. Confirm retention length and whether you can export the record. A trail that exists only inside a vendor's platform is a risk if the relationship ends.
