Fax triage software integrates with a dermatology EHR through one of four paths — a modern API, an HL7 interface, direct secure messaging, or supervised UI automation where no interface exists — and files the classified document into the patient chart with the matching task or result entry. It doesn't replace anything your EHR does. Which path applies to your practice depends on what your specific system exposes and what your EHR vendor charges to turn it on, and those two answers should come before pricing does.
What "integration" actually means here
Vendors use the word to describe wildly different levels of connection, so pin it down early.
At the shallow end, "integrates with your EHR" can mean the software gives your staff a link that opens the right patient's chart in a browser tab. That's a bookmark. At the deep end, it means the software writes the document into the chart under the correct category and date of service, creates the results task assigned to the ordering dermatologist, and stamps an audit entry — with no human clicking anything.
The question that separates those two: after the software processes a document, does anyone on my staff have to touch the EHR for that document to be filed? If the answer is yes, you've bought a sorting tool, not a filing tool, and your labor math needs to be rebuilt accordingly.
Everything below assumes you're after the deep version, because that's the one that changes your staffing.
The four integration paths and what each one buys you
Modern APIs (FHIR or proprietary REST). The cleanest option when available. The platform authenticates, writes the document with structured metadata, and creates the associated task. Many dermatology-focused EHRs now publish both certified FHIR endpoints and proprietary APIs — ModMed's developer portal is an example of a vendor documenting these publicly. Certified FHIR is standardized and predictable but often read-heavy; proprietary APIs frequently offer the document-write operations you actually need. Ask which one your use case requires.
HL7 interfaces. The long-standing workhorse, and still the most common path for results. Your EHR receives ORU result messages and MDM document messages, often with the PDF embedded in the message itself. HL7 is well understood and reliable. It's also where the surprise costs live — many EHR vendors charge a one-time build fee plus an annual maintenance fee per interface, and that number belongs in your business case before you sign anything.
Direct secure messaging. Every certified EHR supports Direct addressing. It's underused and worth asking about, particularly for referral documents from other practices. It's a transport mechanism rather than a structured-filing mechanism, so it usually pairs with one of the other paths rather than standing alone.
Supervised UI automation. When the EHR exposes nothing usable — closed systems, older on-prem installs, or vendors unwilling to open an interface for a third party — the platform operates the EHR the way a staff member would, under a service account with defined permissions and full logging. Practices tend to react to this option with suspicion, and it deserves scrutiny on access controls and audit logging. But it works, it's how a real share of deployments run, and it means a closed EHR doesn't disqualify you from automating.
Most practices end up with a hybrid: an HL7 feed from an interfaced path lab, plus fax-based triage for everything else, writing through whichever path the EHR supports.
How dermatology EHRs handle inbound documents differently
The specific shape of your EHR's document module determines how much of the workflow can actually be automated, and derm-focused systems vary more than you'd expect.
Some systems separate documents from results into different modules with different task behaviors. A pathology report filed as a generic document may never generate the results task the ordering dermatologist works from — it just sits in the chart, technically filed and functionally invisible. Confirm with the vendor which module a path report should land in and whether the write path they're using can reach it.
Others handle structured lab results well through an ORU feed and everything else poorly. That's a good outcome for your interfaced lab and no help at all for the four labs that fax.
A third difference is task assignment. Filing the document is half the job; creating the right work item for the right person is the other half. Ask specifically whether the integration can assign a task to the ordering provider rather than dropping it into a shared pool.
And confirm date-of-service handling. Documents should index by date of service, not date received. Some EHR write paths default to the latter, and it's cheap to configure correctly now and expensive to correct across thousands of documents later.
What to ask a vendor before you sign
Take these to the demo and write down the answers.
- Which specific interface would you use for our EHR and version? A vendor who can't name it hasn't done it on your system before. That's not automatically disqualifying, but you should know you're the first.
- Who pays the EHR vendor's interface fee, and how much is it? This is the single most common budget surprise in the category. Get the number in writing before signing.
- Does the document land in the documents module or the results module, and does it generate a task? Ask them to demo it in a sandbox on your EHR, not a generic screenshot.
- What happens on a low-confidence patient match? The right answer is a clear exception showing candidate charts. The wrong answers are a silent guess or a newly created duplicate chart.
- Is there duplicate detection? Outside labs re-send routinely. Without a dedupe rule, automation files the same report three times faster than a person could.
- How is the audit trail preserved? Every filing decision should be logged with what was decided, on what confidence, and by which service account.
- What's the rollback if we cancel? Documents already filed stay in your chart, but confirm that and confirm you keep access to processing history.
Ask for a pilot on your own document mix rather than a canned demo. A classifier that performs well on a vendor's sample set and poorly on your two highest-volume path labs is a problem you want surfaced during evaluation.
What implementation actually looks like
The technical connection is rarely the long pole. Configuration and validation are.
Weeks 1–2: audit and taxonomy. Pull two weeks of inbound faxes, count volume by document type and sending facility, and build the routing map — which document type goes to which queue, and which findings escalate to a named person rather than a queue. Keep the taxonomy to twelve to twenty categories. Forty produces both human misfiling and low machine confidence.
Weeks 2–4: connection. Interface build, credentialing, and test messages. If an HL7 interface is involved, your EHR vendor's build queue is usually the constraint, so start that conversation on day one rather than day thirty.
Weeks 3–6: shadow mode. The software processes every inbound document and records what it would have done while staff work the queue exactly as before. Nothing visibly improves during this phase, which is why practices skip it — and it's the only phase that tells you whether the system understands your document mix. Measure three things: classification agreement with your staff's decisions, patient-match accuracy tracked separately and held to a stricter bar, and confidence calibration.
Week 6 onward: staged cutover. Set the auto-file threshold high so only near-certain decisions file automatically. Expect a large review queue in week one — that's the design working. Audit it, then lower the threshold in steps while watching the error rate.
Honey Health's fax triage agent is built for this sequence, filing into the EHR the practice already runs and surfacing low-confidence cases as an exception queue rather than a second document system your staff has to work alongside the chart.
Security, BAA, and the audit trail
A vendor processing your inbound patient documents is a business associate, and the diligence here is straightforward.
Require a signed BAA before the pilot, not after. Require encryption in transit and at rest. Ask for a SOC 2 Type II report or HITRUST certification — reasonable bars for a vendor handling PHI at volume, and both are things a serious vendor produces on request rather than after three follow-ups.
The audit trail question deserves specific attention when the integration uses UI automation. If a service account is operating your EHR, you should be able to answer: which account, with what permissions, and what does the log show for any given filing decision. Good vendors have crisp answers. Vague answers here are a real signal.
One more item worth confirming: what happens to documents in the vendor's environment after they're filed. Retention period, deletion policy, and whether your documents are used for model training. That last one has become a standard question and a reasonable one to ask.
Frequently Asked Questions
Do we need our EHR vendor's permission to add fax triage software?
For API or HL7 integration paths, yes — you'll work with your EHR vendor to enable the interface, and they may charge for it. Direct messaging and supervised UI automation typically don't require the same approval, though you should confirm your EHR agreement permits third-party access. Start that conversation early; interface build queues are often the schedule constraint.
How long does EHR integration take?
Cloud EHRs with API-based document write can run a few weeks. HL7 interface builds commonly take longer because your EHR vendor's schedule governs, and on-prem or older systems take longer still. In most projects, taxonomy design and shadow-mode validation consume more calendar time than the technical connection.
What if our EHR has no public API?
You still have options. HL7 interfaces exist on nearly every certified system, Direct messaging is universally supported, and supervised UI automation covers what's left. Ask the vendor which method they'd use on your specific system and version, and scrutinize the access controls and audit logging on the automation path.
Will the software write into the patient chart or just organize a queue?
That's the question to ask directly and get answered in writing, because both product types market the same outcome. If a human still has to open the EHR and upload the document, the expensive part of the workflow hasn't moved. Ask for a live demo of the write step on your EHR.
Does adding fax triage software mean replacing our cloud fax service?
No. Cloud fax handles outbound transmission; the triage layer handles inbound comprehension and filing. Most implementations sit behind your existing fax number or read from your current cloud fax inbox, so you keep the number every referring office in your area already has saved.
