Fax is not going away this decade. It should at least behave properly.
Every serious attempt to replace fax in healthcare has run into the same wall: it is not one system to replace, it is thousands of independent organizations who all already agree on one. VitalFax starts from where things actually are.
What we are building
VitalFax is a secure document communications platform that begins with fax. Fax is the first transport because it is the one your referral sources, pharmacies, payers and records departments can already use without asking anyone’s permission.
Underneath, the product is not a fax product. It is a document system with tenant isolation, permissions, routing and an audit trail. Fax is one way a document arrives. Secure exchange is another. Direct messaging, FHIR and EHR connections are designed to be more, once the agreements exist that would make them real.
How we decide what to say
The uncomfortable convention in this category is to imply certification, imply integrations, and let the buyer discover the gap during implementation. We have tried to make that impossible for ourselves:
- Capabilities that require a vendor agreement are labelled as requiring one, on the public site and inside the product.
- The compliance page lists what we do not claim, and the specific work still outstanding before VitalFax should hold real clinical traffic.
- There are no customer logos, testimonials, reviews, uptime figures or award badges on this site, because we do not have any that would be true.
- Research and market data inside our own tools carry a confidence label. An estimate is never displayed as a fact.
Where we are
Early. The product works end to end and the architecture is the part we have been most careful about, because tenant isolation and audit integrity are the things you cannot retrofit. Vendor agreements, legal review and independent assessment are ahead of us, and we publish exactly where each one stands.
The mark is a geometric B built from the same forms as a document edge. Navy and slate, nothing else. It is meant to look like infrastructure rather than a consumer app, because that is what it is.
Principles we actually apply
Isolation before features
A feature that cannot be built without weakening tenant separation does not get built.
Fail loudly, not quietly
A missing provider throws a typed error. It never silently falls back to a simulation.
Least privilege, including us
Support access is an audited, expiring, reason-required event rather than a default.
Say the unflattering thing
If something is not built, not audited or not connected, the product says so where you would look.
Want to be an early customer?
We will show you what works, tell you what does not, and set it up with you.