Fax to EHR automation moves faxed pages into the electronic health record without re-typing, at one of two levels. The first files each fax as a document in the right patient's chart. The second also turns key values, such as lab results and medications, into structured EHR fields, each linked to its source page and logged.
Two levels of fax to EHR automation: filed pages and structured data
The two levels of fax to EHR automation are filed pages and structured data. Filed pages means the fax lands in the patient's chart as an attached document that a person opens and reads. Structured data means values from the page also land in the EHR's own fields, where the system can sort, chart and alert on them.
Level one: filed pages. The fax is matched to a patient, labelled with a document type and date, and attached to the chart. Nothing on the page becomes data. A provider who wants last month's potassium result opens the attachment and reads it. This level removes printing, scanning and hand-filing, and it is where most fax automation starts.
Standards bodies treat this kind of filing as normal. The HL7 FHIR R4 specification's DocumentReference resource page describes a resource for indexing documents "to make them available to a healthcare system", and lists "PDF documents, Scanned Paper, and digital records of faxes" among the documents it can describe. In other words, a filed fax is a document with metadata such as patient, type and date, not a set of values.
Level two: structured data. Fax to structured data goes further. Selected values are read from the page, checked, and written into the matching EHR fields: a lab value into the results table, a medication into the medication list, a follow-up date into the task list. The attached page stays in the chart as the source.
The two levels differ in risk as well as effort. A misfiled page is wrong in one place. A misread value written into a structured field can feed a flowsheet, a reminder or a report. That is why level two needs a review step and a log, covered in the sections below.
Most practices run both: every fax is filed, and a short list of document types gets structured extraction on top.
Which fax fields are worth turning into structured data?
The fax fields worth turning into structured data are the ones staff already re-type and that the EHR uses after entry: lab values, medication lists, referral reasons and encounter dates. A value is worth extracting when it is typed, sits in a predictable place, and drives a later action such as a result review or a scheduled visit.
A quick way to decide is to ask three questions of each candidate field:
- Does someone re-type it into the EHR today?
- Does the EHR do something with it once it is a field, such as trend it, flag it or schedule from it?
- Can a reviewer confirm it quickly against the page?
Fields that pass all three:
- Lab values. Test name, result, units, reference range and flag, from outside lab reports. Trended results only work when they are fields. The post on entering outside lab results into an EHR covers the manual version of this job in detail.
- Medication lists. Drug, strength, dose and frequency from discharge summaries and outside notes, for medication reconciliation.
- Referral reasons. The reason for referral and the referring provider, so a referral can be tracked and scheduled.
- Encounter dates. Admission, discharge and visit dates, which anchor every other value to a point in time.
Fields that usually stay on the page: free-text narrative such as a history of present illness, handwritten notes, and long tables that change layout from sender to sender. They remain readable in the filed document.
A field map from a faxed discharge summary
The map below follows one fictional discharge summary into EHR fields. The patient, dates and values are made up for the example, and the EHR field names are generic labels.
| Value on the fax (example) | Source page | EHR field (generic) | Action |
|---|---|---|---|
| Patient: Lena Example, DOB 06/22/1964 | Page 1, header | Patient match | Used for matching, not written |
| Admission date: 09/03/2026 | Page 1, encounter block | Outside encounter: start date | Write after review |
| Discharge date: 09/07/2026 | Page 1, encounter block | Outside encounter: end date | Write after review |
| Discharge diagnosis: community-acquired pneumonia | Page 1, diagnoses section | Outside problem entry | Send to clinician to accept |
| Procedure: chest X-ray, 09/03/2026 | Page 2, procedures section | Outside procedure history | Write after review |
| Medication: lisinopril 10 mg, once daily (example) | Page 2, discharge medications | Medication list, pending reconciliation | Send to clinician to reconcile |
| Follow-up: primary care visit within 7 days | Page 3, follow-up instructions | Task: schedule follow-up | Create task for front desk |
| Discharging physician: Dr. Sam Placeholder | Page 3, signature block | Outside provider on encounter | Write after review |
Two details make the map useful. Every row names the page and section the value came from, so a reviewer can find it in seconds. And diagnoses and medications do not go straight into the problem list or active medication list: they wait for a clinician, because accepting them is a clinical decision, not a data entry step.
Routes for fax data into the EHR: inbox, document import and interfaces
The routes for fax data into the EHR fall into three groups. An inbox route drops the fax into a work queue where staff file it. A document import route attaches the page to the chart with its metadata. An interface route sends structured values as messages the EHR accepts. Your EHR's support decides what can be automated.
Inbox. Many fax setups deliver every page to a shared electronic inbox inside or beside the EHR. A staff member picks the patient, the document type and the date, then files it. Automation here means pre-filling those choices so the person confirms instead of choosing. How the fax reaches the inbox, through an online fax service or an on-site fax server, is compared in efax vs fax server in healthcare.
Document import. Some EHRs accept documents with metadata through a batch import folder or a document service. The software that splits and matches faxes can then attach each file to the right chart directly. The FHIR DocumentReference resource cited above is one standard shape for this kind of metadata.
Interfaces. Structured values usually enter through an interface, a defined message format the EHR listens for. Interfaces are the most powerful route and the most work: they need the EHR's interface team, a test environment and agreement on codes and units. The message formats themselves are covered in the developer integration posts, not here.
Whatever the route, the page must be matched to the right patient before anything is filed. The matching rules are in chart matching rules for exact, probable and no match results.
What should an EHR fax import log record?
An EHR fax import log should record, for every fax, who or what filed it, when, to which patient and document type, a link to the source page, and every correction made afterwards with who made it and why. The log is what lets a practice answer "where did this value come from?" months later.
A useful log entry holds:
- Receipt: sender fax number, time received, page count, and the identifier of the original file.
- Filing: the patient chart, document type and document date chosen, and whether a person or a rule chose them.
- Extraction: for each structured value, the value written, the EHR field, the page and location it came from, and whether it was reviewed.
- Corrections: the old value, the new value, who changed it, when, and a short reason.
- Moves: if the page was refiled to another patient, both chart identifiers and the reason.
Federal rules give a frame for this. The HIPAA Security Rule's audit controls standard tells covered entities and business associates to "implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information", and its integrity standard asks for policies "to protect electronic protected health information from improper alteration or destruction." Both appear in 45 CFR 164.312 on eCFR. The rule does not prescribe a fax log format; the list above is one practical reading of it, and your privacy and security officials decide what yours must hold.
Schema Care does not receive faxes, but it works this way for the document types it reads, discharge summaries among them: each extracted field carries a link to its place on the page, low-confidence fields wait in a review queue, and every approval or correction is logged with who made it and when. EHR and billing-system integrations are a feature of the Health system plan only, as the Schema Care plans and pricing section shows.
Fax to EHR automation when the EHR has no import path
Fax to EHR automation without an import path is limited to work outside the EHR: splitting, matching, labelling and extraction that a person then files or keys in. When the EHR accepts neither documents with metadata nor structured messages, full automation is not available, and the honest choice may be to stop at level one or not automate at all.
Signs that full automation is the wrong goal:
- The EHR has no document import and no interface the practice can afford to turn on.
- Fax volume is low enough that one person files the day's pages in under an hour.
- Most pages are handwritten or arrive at standard resolution, so extracted values would need a full re-check anyway.
- The practice is moving to a new EHR within the year, and any interface would be rebuilt.
What to do instead:
- Pre-sort the inbox. Split batches, match pages to patients and label document types outside the EHR, then hand staff a short list of confirmed filings.
- Extract to a worksheet. For lab values or medications, produce a reviewed list with source page links that staff key in, which is faster than reading the fax cold.
- Ask the sender for another channel. A hospital or lab that faxes you daily may also offer a portal, Direct secure messaging or an interface on its side.
The cost side of this choice, including when automation pays back at all, is worked through in healthcare fax automation costs, savings and ROI.