Challenge
One fax carries a referral, a lab result and a face sheet together.
Agnotic approach
Documents are split before they are classified, so each part routes on its own.
AI / Fax Intake
AI fax intake automation for referral and records faxes
Faxes pile up in a shared inbox, staff open each one to work out what it is, and referral details are retyped into the EHR. Agnotic Technologies builds AI fax intake automation that sorts each fax, routes it to the right queue, drafts the EHR entry and sends uncertain pages to a person.
Fax classificationQueue routingReferral to EHRHuman review rules
Trusted by global innovators
What is AI fax intake automation?
AI fax intake automation is software that takes every inbound fax from your fax server or cloud fax service, splits transmissions that carry several documents, reads each page, labels what it is, such as a referral, lab result, records request or prior authorization reply, matches it to a patient and routes it to the right work queue. For referrals it drafts the referral and files the documents in the EHR, so staff check instead of retype. Agnotic Technologies builds it with HIPAA-ready engineering and with rules that send low-confidence, urgent or unmatched faxes to a person before anything reaches the chart.
This page covers the fax inbox: sorting, routing, referral entry and review rules. Our medical document processing page covers OCR and field extraction for faxes, PDFs and scans in general.
Fax triage
Can AI sort and route our incoming faxes?
Yes. A classification model labels each document in a fax, and a routing table sends it to the queue that owns that document type, so nobody has to open every fax to decide where it goes. Your team keeps control of the routing rules.
Receive
Each fax arrives from your fax server or cloud fax service as an image, with the sending number and time.
Split
Cover sheets are separated, and a transmission holding several documents is split into each one.
Classify
Each document is labeled: referral, lab or imaging result, records request, prior authorization reply, refill request or other.
Match
The patient is matched on name, date of birth and any record or referral number, and the sender on the referring practice.
Route
The document goes to the queue for its type, department, location and urgency.
Track
Every fax keeps a status until someone works it. Nothing is deleted, and unworked items escalate as they age.
Human review rules
Which faxes should still go to a person for review?
Any fax where a wrong guess could harm a patient or misfile protected health information goes to a person first. These are the review rules we start from; your team sets the thresholds.
| Fax situation | Why it needs a person | What the reviewer does |
|---|---|---|
| No confident patient match | A wrong match files health information in another patient's chart | Confirms the patient or starts a new record |
| Urgent, STAT or critical result wording | Speed matters more than routing order | Routes it at once and follows the urgent result procedure |
| Low confidence on a key field | A name, date of birth, medication or diagnosis may be misread | Corrects the field against the fax image |
| Handwritten pages | Handwriting is read less reliably than print | Checks every field taken from the page |
| Unknown document type | The model has not been trained on it | Labels it, which adds to the retraining set |
| Fax meant for another practice | The health information was not meant for you | Follows your misdirected fax procedure |
| Records requests and legal documents | Releasing records needs authorization checks | Sends it to health information management |
Everything else can route on its own once accuracy on your own faxes meets the threshold your team agrees. Automatic decisions are logged and sampled for review.
Referral entry
How do we stop retyping referral faxes into the EHR?
Let the software draft the referral from the fax and write it to the EHR as a pending referral or task for a coordinator to confirm. Agnotic Technologies builds that step through the interface your EHR supports, such as HL7 FHIR R4 or HL7 v2, and attaches the original fax so the coordinator checks each field against the source.
Fields the model is unsure of are highlighted. The coordinator's corrections are kept, so the model can be retested on your own referral formats.
Failure points
Where does fax automation go wrong?
Problems we design for from the first release.
Challenge
The patient match is close but not exact.
Agnotic approach
Anything short of a confident match goes to review rather than to the nearest chart.
Challenge
Faxes disappear when the queue is cleared.
Agnotic approach
Every fax keeps a status and an owner until it is worked, and nothing is deleted.
Challenge
The model drifts as senders change their forms.
Agnotic approach
Reviewer corrections are sampled and used to retest the model on a schedule.
Challenge
An urgent result waits behind routine paperwork.
Agnotic approach
Urgent wording jumps the queue and alerts the right team.
What do we build for fax intake?
Modules from the fax line to the work queue and the chart.
Fax line connection
Inbound faxes from your fax server or cloud fax API, with sender and time kept.
Document splitting and classification
Multi-document faxes split and labeled by type, with a confidence score.
Field reading
Patient, provider, reason and urgency read from each page for a person to confirm.
Patient and sender matching
Matches to existing patients and referring practices, with uncertain matches held.
Routing rules
A routing table your team edits by document type, department, location and urgency.
EHR write-back
Referrals, tasks and filed documents through HL7 FHIR R4 or HL7 v2.
Review queue
The fax image beside the extracted fields, with low-confidence fields highlighted.
Audit log
Every receipt, label, route, review and write-back recorded against the fax.
Facts and sources
Which HIPAA rules apply to fax intake?
HIPAA rules that shape how faxed health information is stored, shared and logged, each linked to the eCFR.
The HIPAA definitions in 45 CFR 160.103 say transmissions of paper via facsimile are not transmissions via electronic media if the information did not exist in electronic form immediately before the transmission, while electronic storage material, such as computer hard drives, is electronic media.
Source: 45 CFR 160.103 (eCFR)The HIPAA Security Rule's audit controls standard, 45 CFR 164.312(b), requires hardware, software or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information.
Source: 45 CFR 164.312(b) (eCFR)Under 45 CFR 164.502(e)(1), a covered entity may allow a business associate to create, receive, maintain or transmit protected health information on its behalf if it obtains satisfactory assurance that the business associate will appropriately safeguard the information.
Source: 45 CFR 164.502(e) (eCFR)45 CFR 164.506(c) allows a covered entity to use or disclose protected health information for its own treatment, payment or health care operations, and to disclose it for the treatment activities of another health care provider.
Source: 45 CFR 164.506(c) (eCFR)
Which privacy and security standards shape fax intake?
01
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
02
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
03
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
04
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
05
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
06
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
07
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
08
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
09
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
Interoperability
Standards for the EHR handoff
FHIR R4 DocumentReferenceFHIR R4 ServiceRequestFHIR R4 TaskHL7 v2 MDMICD-10-CM
Related builds
Where does fax intake connect?
Fax intake feeds referrals, the chart and wider document and workflow automation.
Medical document processing automation
OCR and field extraction for faxes, PDFs and scans of every type.
Referral management software
The referral loop after intake: scheduling, status and reports back to the referring practice.
EHR integration services
The Epic, Oracle Health (Cerner) and athenahealth connections the write-back uses.
Healthcare workflow automation
Multi-step work across EHR, revenue cycle and CRM systems after a fax is filed.
Who it is for
Teams still working a fax inbox
Teams whose referrals and results still arrive by fax.
Specialty practices
Referral packets from primary care, routed to schedulers with the referral drafted.
Hospital access centers
High fax volumes split across departments and locations.
Imaging and lab centers
Orders and prior authorization replies matched to scheduled patients.
Post-acute and home health
Discharge packets and orders that need fast routing to intake nurses.
Scope
What decides the size of a fax intake build?
We do not publish prices. These are the drivers we size on the scoping call.
Fax lines and volume
How many fax numbers and services, and how many faxes arrive each day.
Document types
How many types the first release classifies and routes.
EHR and interface
Your EHR and the interface it allows for referrals and documents.
Queues and rules
Departments, locations and the routing rules between them.
Review workflow
Who reviews which faxes, and the thresholds for each rule.
Hosting
Your cloud account or ours, under a business associate agreement.
Engagement
How does a fax intake automation project run?
We start with a sample of your own faxes, under a business associate agreement.
1.
Scoping call
We walk through your fax inbox, the queues it feeds and how referrals reach the EHR today.
Scope2.
First release for referrals
A fixed-scope first release: fax connection, splitting, classification, routing and the review queue, with referral drafting for one department.
Build3.
More types and automatic routing
More document types, more departments and automatic routing where accuracy is proven, with support after launch.
ScaleFrequently Asked Questions
Only where your team allows it. The model labels and routes faxes that meet your confidence thresholds. Faxes that match a review rule, such as an uncertain patient match or urgent wording, go to a person first.
EHRs that offer an interface for referrals and documents, such as HL7 FHIR R4 or HL7 v2, including Epic, Oracle Health (Cerner) and athenahealth where your organization has that access. We confirm the interface on the scoping call.
Yes. The software connects to your existing fax server or cloud fax service, so senders keep using the same numbers.
Yes. Agnotic signs a business associate agreement before any protected health information is shared with our team, and any AI service used to read faxes must be covered by the same kind of agreement.
Document processing is the reading and extraction engine for faxes, PDFs and scans. Fax intake automation is the inbox around it: splitting, classifying, matching, routing, review rules and referral entry.
We do not publish prices. Fax volume, document types, the EHR interface, routing rules and the review workflow decide the size, and we agree a fixed first release on the scoping call.