What this page covers
- Where the faxes come from, and what stays the same
- How each document is classified
- Patient matching without duplicate charts
- Filing into eClinicalWorks, PointClickCare and Axxess
- What happens to faxes the agent cannot file
- The audit trail each fax leaves
- How this differs from referral and records workflows
- How a Flexbone deployment works, step by step
One group we spoke with described about 900 faxed documents a day keyed by hand into eClinicalWorks. The work behind each fax is the same: open it, decide what it is, find the patient and file it. Flexbone's document agent does that work. It pulls faxes from the inbox or fax server, classifies each document, matches it to the patient chart and files it. A fax it cannot match, or one at risk of becoming a duplicate chart, goes to staff with the reason. This page covers all inbound documents. Referral scheduling and records requests have their own pages, linked below.
Where Do the Faxes Come From?
The agent reads faxes where they already arrive, so referral sources keep sending to the same number. Many offices use an online fax service that emails each fax as an attachment. eFax, for example, delivers received faxes as email attachments, and some groups route them into a shared Gmail inbox. The agent reads that inbox through the mail provider's API and takes each attachment.
Other sources work the same way. A fax server can write each fax to a network folder, and a referral source or records vendor can drop files on an SFTP server. Some EHRs hold faxes in their own inbox, which the agent reads through the EHR's API where one is available. Where a group wants a clean start, Flexbone can provision a HIPAA-compliant fax number.
Get an outside read on your fax automation workflow
In 30 minutes we map your current volume, the payers and systems involved, where staff time goes, and the highest-ROI calls and follow-ups Flexbone can take off your team first, scoped to the work you actually run.
How Does the Agent Classify Each Document?
Each fax is read page by page and sorted into the document types the group files. The common types are referrals, outside records such as consult notes and discharge summaries, authorization determinations, lab and imaging results, and surgical clearance letters. Groups add their own, such as DME orders or refill requests. One fax can carry several documents, so the pages are split before filing.
The agent also captures the fields the next step needs. For a referral, that is the referring provider and NPI, the reason for referral with its ICD-10 codes, and the payer. For an authorization determination, it is the decision, the authorization number, the approved CPT codes and the dates. The categories and fields come from the group's filing SOP, and documents that fit no category go to the exception queue.
How Are Faxes Matched to the Right Patient Without Duplicate Charts?
Patient matching is where fax work goes wrong. A buyer described handwritten referrals that created duplicate charts, because a name was misread or a birth date was transposed. The agent matches on name and date of birth plus a second identifier, such as phone number, address, insurance member ID or medical record number.
Before a new chart is considered, the agent searches the EHR for close matches. These include nicknames, maiden names, swapped first and last names, and one-digit date differences. A close match goes to staff with the candidate charts instead of being merged. New charts from referrals follow the group's rules, and staff confirm any chart the agent is not sure of.
How Are Documents Filed into eClinicalWorks, PointClickCare and Axxess?
Filing uses the EHR's API where the vendor exposes one for documents, and a browser automation in the EHR's web interface where it does not. In eClinicalWorks, Flexbone files documents to the patient's document folders and creates charts from faxed referrals. eClinicalWorks also offers Image AI, which suggests a patient match for staff to approve. If you run eClinicalWorks, compare the two on the document types and volume you receive.
In PointClickCare, the agent works through a user login, and chart creation from referral packets runs the same way. PointClickCare's FHIR APIs follow the USCDI v1 data set, and access requires a partnership application and PointClickCare approval. In Axxess, the agent writes communication notes and PDFs to the patient chart. Axxess Home Health keeps documents attached to a referral as it becomes an active patient, so referral packets can be filed before admission.
What Happens to Faxes the Agent Cannot File?
They go to an exception queue, with the fax, the agent's best reading and the reason it stopped. Common reasons are no patient match, more than one possible match, an unreadable page, or a document type the group has not defined. Staff resolve the item in the queue, and the resolution is used to adjust the rules.
Time-sensitive types get their own routing and can go straight to a named person or queue. Examples are an authorization denial with an appeal deadline, an urgent referral, or a clearance letter for a surgery this week. The group sets which types count as urgent during the audit.
Have Flexbone run your fax automation workflow on real cases
A complimentary six-week pilot once the BAA is signed, with a weekly review of what the agents handled, which results were written back to your system, and the hours your team got back.
What Audit Trail Does Each Fax Leave?
Each document carries a record of what happened to it. The record shows when it arrived, from which number, and how it was classified. It also shows which identifiers matched the patient, where it was filed, and whether an agent or a staff member filed it. When a browser automation files a document, a screenshot of the filing step is kept. When an office calls to ask whether a fax arrived, staff answer from the record instead of searching the inbox.
How Is This Different from Referral Management and Records Requests?
Fax automation is the intake layer for inbound documents. It ends when the document is filed to the right chart or routed to staff, and what happens next belongs to other workflows. Referral management covers scheduling the referred patient and closing the loop with the referring office. Medical records requests covers release of information and chasing outside records. Notes written at the visit are covered by the AI medical scribe.
How Does a Flexbone Deployment Work?
Every deployment starts from the work as your team does it today, not from a product demo. The steps below are the same whether the first agent answers phones, checks eligibility, or files incoming documents.
- Audit first, then automate. We listen to a sample of your calls and read the work queues, then agree with your team on which work to automate first. The audit is complimentary.
- Forward-deployed engineers map your SOPs. An engineer sits with the staff who do the work and turns your written and unwritten rules into agent logic.
- Agents act on your rules, and exceptions go to a person. Each step follows logic built from your SOPs. A case outside those rules, or one the agent is not confident about, goes to your team with the context attached.
- Every action leaves a record. A check in a web application saves a screenshot, a call saves a transcript, and results are written back where your team already looks.
- Start with one or two agents on the systems you already run. The agents work in your EHR, practice management system, phone system, and the web applications your staff use, as they are configured today, so nothing is migrated or rebuilt.
- The same team stays after go-live. We monitor results, tune the agents as payers and workflows change, and add agents as new work is found.
The engagement model is described in more detail in forward-deployed engineering for healthcare contact centers.