Healthcare still runs on fax. A referral, a lab result, a prior-auth, a records request: most of it arrives as a fax, a scan from the copier, a voicemail, or an email with a PDF stapled on. The large systems paper over this with two expensive line items: a legacy fax server, and a separate service that reads and routes the documents. A regional non-profit or a single clinic gets quoted the same per-page and per-seat pricing as a hospital network, for a problem that has not actually gotten smaller.
Faxart is for those clinics.
What it is
Faxart runs on your own hardware and catches every way a document or message reaches the front desk. A fax on the trunk. A scan from the Ricoh by the nurses’ station. A voicemail. An email with a PDF. It reads each one where it lands: OCR, classification, the patient identifiers, on a GPU you own, then helps a knowledgeable person get it onto the right chart and notify the right people. A person always confirms before anything reaches a record.
It is web-native, so it works in a locked-down browser with no desktop client to install on every machine. And it is open source: you can read the code, run it, and host it yourself.
What it replaces
Two bills, folded into one stack you run:
- The fax server: send and receive, folders, cover sheets, retries, fax-to-print to the trays you already have.
- The bolt-on classifier: the reading and routing you were paying a second vendor a subscription for, done on-prem instead of in someone else’s cloud.
No per-page fee. No per-seat fee. The cost is the hardware in your closet and the time to stand it up.
Why on-prem is the whole point
For a smaller organization, the cheapest way to keep PHI safe is to never let it leave the building. Faxart’s reading runs locally by a hard rule: the page image, the voicemail audio, the message body, none of it goes to a cloud service, even one that will sign an agreement. Every read is logged at the database, not just in the app. See Keeping PHI on-prem for how that line is drawn and enforced.
It assists; it does not decide
This matters most where budgets are thinnest and staff wear the most hats. Faxart does the legwork (it reads the document, proposes the chart and the people to notify, and queues it for review), but a person makes the call. Routing is written in plain English, not a black box, and a rule only starts acting on its own after it has agreed with your staff enough times to earn it, with brakes that pull it back if it drifts.
Honest about what is here
Shipping today: fax send and receive, voicemail, scan-to-fax and scan-to-email from your copiers, on-prem reading and routing, MEDITECH filing with a human confirming the patient, fax-to-print, the directory and self-service numbers, a searchable archive, and an audit floor. Embedded EHR web chat and dictation are on the way, treated as just more ways a message arrives, and we will say so plainly until they land.
Try it
Stand it up with Docker Compose, point it at your trunk and your copiers, and retire the old server. Start with the deploy guide, or read how an inbound item flows.