About
Most cloud fax providers run a generic fax service that happens to be used in healthcare. the PHI eXchange (PHIX) was built the other way around: a healthcare-first fax network designed for HIPAA, BAA, hospital revenue cycle, EHR integration, and the operational realities of actual claims documentation. Decades of telecom and healthcare fax engineering live inside the team.
Healthcare fax expertise, by the numbers
What We Do
the PHI eXchange operates a HIPAA-compliant cloud fax network purpose-built for healthcare. We provide inbound fax intake, fax-to-email, email-to-fax, print-to-fax, outbound APIs, fax number portability and migration, Epic-integrated EMR faxing, and outbound fax fallback for the workflows that need it.
We do not generate X12 or HL7 transactions. We do not perform OCR, classification, LOINC coding, or claim matching. We do not replace EHRs or clearinghouses. That is on purpose. Every commitment we make is one we can keep -- and the things we do not do are well covered by partners, vendors, and customer stacks we integrate with.
Our Fax Experts
U.S.-based telecom engineers and developers with careers in secure healthcare document exchange. The bios below are illustrative of the team that customers and partners actually engage with -- editable as the team grows or named team members come onto specific engagements.
Carrier & Network Operations
Multi-carrier Tier 1 routing, geo-redundant active-active data center operations, fax termination engineering, and the carrier relationships that keep critical healthcare fax traffic flowing during outages and surges.
Focus areas: T.38 / G.711 transmission, carrier diversity, outage runbooks, intelligent routing, fax completion-rate optimization.
Security, Privacy, BAA
SOC 2-audited operations, HIPAA technical safeguards, BAA management, encryption-in-transit and at-rest controls, and zero-retention defaults so customer documents do not linger in our systems.
Focus areas: HIPAA Privacy & Security Rule, SOC 2 Type 2, BAA program, audit logs, retention controls.
Epic-native faxing & APIs
Send and receive faxed documents directly from inside Epic and other EMR environments. APIs (REST), webhooks, SFTP, and secure email handoffs designed for clinical and revenue-cycle workflows.
Focus areas: Epic integration, EMR fax printing, API delivery, SFTP, webhook events, dashboard access.
Why It Matters For 2028
BAA, encryption, audit trail, and SOC 2 are table stakes for hospital revenue cycle teams whose claims documentation will travel through the network.
When trading partners are mid-transition and exception workflows fall back to fax, the carrier rail has to actually work. Multi-Tier 1 routing and active-active geo-redundancy are not nice-to-haves -- they are the product.
EHR integration, payer-specific routing patterns, hospital BAA programs, and number-migration tooling are baked in -- not bolted on top of a generic SaaS fax product.
Hospitals, health systems, vendors, and partners can talk to a fax expert directly. We will scope the engagement, walk through trading partner constraints, identify which fax workflows survive the 2028 transition, and put a plan in writing.
Claims Attachment Fax Gateway
Hospitals, vendors, and partners use this gateway because the team behind it has been doing healthcare fax for a long time -- not because they figured it out for CMS-0053-F.
