Spruce Health
Align fax intake with your approved patient communication and team workflow.
Discuss your requirements →Custom integrations & managed operations
Your fax path.
Your actual stack.
Scope the integration around the carrier, PBX, clinical system and exception that is costing your team time.
Separate SIP signaling from fax media. Separate a carrier receipt from chart filing. Separate chart filing from a person accepting responsibility. Tailored development follows the interfaces and authorization your installation actually supports.
Clinical communication platforms
Bring your platform and installed configuration. These are platforms to discuss for tailored integration; this list does not assert an existing connector, partnership or certification.
TigerConnect
Keep a clinical notification distinct from document delivery and ownership.
Discuss your requirements →Klara
Connect document arrival to the patient communication workflow you actually use.
Discuss your requirements →OhMD
Scope document hand-off around enabled messaging interfaces and processing rules.
Discuss your requirements →Updox
Reconcile incoming documents with the practice or pharmacy’s document queue.
Discuss your requirements →Halo Health (Symplr)
Define care-team hand-off, ownership and the receipt that proves it happened.
Discuss your requirements →PerfectServe
Map routing and escalation to the team responsible for the document.
Discuss your requirements →Telmediq
Keep clinical alerts, document acquisition and acknowledgement separate.
Discuss your requirements →Luma Health
Connect referral intake to the enabled engagement and scheduling workflow.
Discuss your requirements →Doximity Dialer
Review available interfaces and authority before connecting calling workflows to fax intake.
Discuss your requirements →Where the technical work begins
SIP trunks, PBXs and media paths
Trace SIP re-INVITE, T.38 UDPTL, G.711/RTP, NAT traversal and SBC boundaries. Inspect the existing Asterisk, FreeSWITCH, Avaya IP Office or Aura path. Compose multiple trunks by site, inbound or outbound direction, provider, vendor and authorization as tailored work.
Carrier APIs and billing records
Keep route policy, call identity and provider outcomes together. Reconcile CDRs and reported charges against every attempt, including failures and per-call billing increments. Scope other carrier adapters and capacity policies to your actual account.
Clinical filing and work ownership
Review Epic, Intergy, Raintree, OnBase or RightFax interfaces already enabled in your organization. For a tailored HL7 FHIR R4 integration, inspect CapabilityStatement, DocumentReference, Task and Communication support and the granted SMART on FHIR scopes. A published interface is not proof that your installation permits document writes.
Original documents and protocol extensions
Preserve original content and document provenance. Scope patient matching, reviewed OCR, controlled AI processing and recipient-approved packet reuse. SSLFax, HylaFAX+, adaptive T.30/ECM compression choices and Internet Aware Fax need compatible endpoints and validation before operational use.
Measure the return at the actual billing boundary.
A smaller PDF is not automatically a smaller invoice. Use a comparable observation period and separate estimates, carrier-reported charges and settlement.
All-attempt cost per delivered fax
Count charged failures and retries, not just the successful call. Compare total attributable charges with completed deliveries by destination. Current route ranking uses rate-card estimates and delivery history; optimization by actual all-attempt cost can be tailored to your traffic.
Per-call minimums and batching
Apply the minimum and increment to each call. For approved batching, compare separate calls with the combined call, including separator pages, wait limits, partial outcomes and charge allocation. Time saved inside the same billing increment does not create a saving.
Repeated pages and direct delivery
Count recipient-approved pages omitted from case updates and verified direct deliveries that avoid a telephone transfer. Include partner setup, platform costs and fallback calls. Do not add the same removed fax call to two savings categories.
Intake labor and total ownership cost
Measure time spent acquiring missing documents, matching patients, filing, assigning and chasing acknowledgement. Include carrier rental, channel and software fees, hosting, integration and support labor. Staff time released and cash expense reduced are different results.
Cost per delivered fax = attributable charges for every attempt ÷ confirmed deliveries.
Net benefit = avoided transport expense + measured value of time released − incremental operating and integration cost.
No forecast is a measured customer result. Select the baseline, traffic mix and valuation with your team.
Technical vocabulary, with operational meaning
These are topics for configuration, diagnosis, research and custom scoping. The 24 mechanisms distinguish available behavior from capabilities tailored to your installation.
SIP & fax media
fax over IP (FoIP) · SIP trunking · T.38 · UDPTL · G.711 fax passthrough · RTP · SIP re-INVITE · NAT traversal · SIP ALG · session border controller (SBC) · Asterisk · FreeSWITCH · Avaya IP Office · Avaya Aura · Telnyx · SignalWire · Sinch · Gamma · BT One Voice · Telstra SIP Connect
Routing & carrier economics
independent inbound and outbound providers · destination-based fax routing · provider failover · uncertain send reconciliation · client idempotency · SIP Call-ID correlation · carrier CDR reconciliation · per-call minimums · billing increments · cost per delivered fax · recipient-approved fax batching · DID channel pooling · multi-trunk routing · site-based routing · direction-based routing · vendor-based routing · RBAC route authorization · fax retry cost · marginal delivery cost · fax total cost of ownership · channel utilization · fax ROI
Documents & protocol research
T.30 fax negotiation · DIS/DCS capability negotiation · ECM error correction · PPR partial-page retransmission · V.17 · V.34 · MH compression · MR compression · MMR compression · JBIG · one-bit PDF rasterization · lossless fax optimization · SSLFax · HylaFAX+ · T.38 Internet Aware Fax · encrypted original-PDF delivery · signed delivery receipts · recipient-approved case packets · partial fax recovery · document content fingerprints
Healthcare & enterprise interfaces
healthcare fax integration · EHR document intake · EMR chart filing · Epic · Intergy · Raintree · Hyland OnBase · OpenText RightFax · HL7 FHIR R4 · FHIR DocumentReference · FHIR Task · FHIR Communication · FHIR CapabilityStatement · SMART on FHIR · OAuth 2.0 scopes · patient matching · referral intake · prior authorization workflows · reviewed OCR · controlled AI document processing
Access, acquisition & evidence
role-based access control (RBAC) · mailbox-scoped permissions · scoped API keys · provider webhook verification · durable document acquisition · SMTP intake delivery · owned work queues · owner acknowledgement · acknowledgement deadlines · evidence export · document provenance · retention policy · legal holds · exact-action approvals · REST API · OpenAPI · Python SDK · Node.js SDK · Model Context Protocol (MCP)
Bring the topology and the failing hand-off.
Carrier and PBX versions. Enabled clinical interfaces. Inbound and outbound paths. Permission boundaries. Recipient packet rules. The evidence you need after the transport reports success.
Discuss your integration →