Protocol
T.30 over PSTN, T.38 over IP, interop, ECM, retransmission.
Practices
T.30 setup
T.38 packet behaviour
gateway interop
Layer 1 of 4
/Services/Fax testing
Fax testing
Fax engineered as regulated infrastructure, not legacy plumbing
QAble runs fax and Fax-over-IP testing across protocol, document fidelity, EHR/ECM integration and HIPAA-aligned compliance, for the healthcare, legal and public-sector workflows that still depend on fax to move evidence between systems.
Fax testing covers:
T.30 and T.38 protocolDocument fidelityCloud and eFaxEHR and ECM integrationCompliance (HIPAA/HITECH)Capacity and reliability
Healthcare and regulated teams that rely on QAble
What it means
What fax testing actually proves
Not that a fax sent, but that the page arrived intact, the integration indexed it correctly and the audit trail can prove it, across protocol, fidelity, integration and compliance.
01
Fax is regulated infrastructure, not legacy plumbing
In healthcare, legal and government it still carries clinical results, signed orders and evidence of record. The cost of failure is regulated; the visibility into failure rarely is.
02
Protocol and fidelity are engineering targets
T.30 and T.38 need real interop coverage and document fidelity needs measurement, not a vendor claim. Both are tested against real endpoints, not simulated round-trips.
03
HIPAA evidence is built, not screenshotted
Audit logging, chain of custody and access control are captured in the format the next audit will read, so external audit becomes a confirmation rather than a discovery exercise.
Choose fax testing when:
fax delivery silently fails on a percentage of pages or recipients but no metric reports it
a cloud fax migration is announced before T.38 interoperability has been tested end to end
PHI documents move through fax channels with weak audit logging and ambiguous chain of custody
document fidelity, page count, OCR readiness, signatures, degrades after a vendor change
EHR or ECM integrations break on edge cases like multi-page, large attachments or encoded documents
The problem
Why fax still needs engineering attention
Fax is not legacy plumbing. The cost of failure is regulated, the visibility into failure is rarely engineered, and silent failures keep moving the workflow as if nothing went wrong.
Treated as legacy plumbing, fax keeps producing
01
Pages drop and recipients miss with no "fax delivery rate" metric and no operational owner
Silent failure02
Cloud fax migration announced before T.38 interop and ECM behaviour are tested end to end
No interop03
PHI carried over fax with weak audit logging and chain of custody rebuilt by hand each audit
No audit trail04
Document fidelity drift after a vendor change, surfacing in OCR pipelines weeks later
Fidelity drift05
EHR integrations that work on the happy path but break on multi-page and encoded edge cases
EHR edge cases06
Peak-hour throughput and retry-storm behaviour never tested, so outages are improvised
No capacity postureThe QAble Solution
Fax testing treats T.30 and T.38 as protocols that need real interop coverage, document fidelity as an engineering target and HIPAA logging as an artefact you build, not a screenshot you collect.
Delivery success rate
Page and recipient delivery measured, not assumed, across the provider matrix.
Document fidelity
Page count, resolution, signatures and OCR readiness validated end to end.
Audit evidence completeness
HIPAA and HITECH evidence captured in audit-ready format.
Interop coverage
T.30 and T.38 behaviour validated against real gateways and endpoints.
Coverage areas
Fax testing layers we cover
Six disciplines applied as one fax engagement, protocol, document fidelity, cloud platform, EHR/ECM integration, compliance and capacity, selected and combined depending on whether the engagement is an audit, a migration or continuous fax QA.
01
Protocol testing
T.30 (PSTN) and T.38 (IP) protocol testing, call setup, capability negotiation, error correction (ECM).
T.30 call setup and ECM
T.38 packet behaviour
gateway and SBC interop
codec and bandwidth posture
02
Document fidelity
End-to-end document fidelity, page count, resolution, signatures, line art, fonts and encoded attachments, validated against original documents and downstream OCR readiness.
page-count and order
resolution and image quality
signature and form fidelity
OCR-readiness validation
03
Cloud and eFax platform
Cloud fax and eFax platforms, provisioning, sender and receiver workflows, webhook delivery, retry semantics and the operational behaviour that determines whether fax becomes reliable in production.
provisioning and number lifecycle
webhook and event reliability
retry and failure semantics
platform capacity validation
04
EHR and ECM integration
Integration with electronic health records (EHR), document management (ECM) and case-management systems, the inbound and outbound paths where most production defects accumulate.
inbound routing and indexing
outbound order and trigger
patient and case identifier matching
duplicate and merge handling
05
Compliance and audit
HIPAA, HITECH and jurisdictional compliance, audit logging, access control, retention, BAA posture and the evidence packs the next audit will read instead of the next outage.
HIPAA and HITECH alignment
audit logging and retention
access control and BAA evidence
data-handling chain of custody
06
Capacity and reliability
Throughput, queue depth and reliability posture, peak-hour validation, retry storm behaviour, line saturation and the recovery drills that make fax outages survivable.
throughput and queue depth
peak-hour and burst tests
retry-storm posture
failure and recovery drills
Coverage layers
The QAble fax coverage layers
Four layers that decide whether fax is regulated infrastructure or invisible risk, protocol, document fidelity, integration and compliance, each with measurable evidence and a defined acceptance threshold.
Document fidelity
Page count, image quality, signature, OCR readiness.
Practices
fidelity matrix
OCR validation
signature retention
Layer 2 of 4
Integration
EHR, ECM, case-management, inbound routing, outbound trigger.
Practices
inbound routing
outbound trigger
identifier match
Layer 3 of 4
Compliance
HIPAA, HITECH, audit logging, access control, retention, BAA.
Practices
audit logging
access control
retention evidence
Layer 4 of 4
Methodology
The QAble fax testing methodology
A six-stage rhythm that takes fax QA from coverage map to release readiness, with documented evidence at every stage.
01
Coverage02
Test03
Run04
Triage05
Release06
ContinuousCoverage map
Map the fax surface, endpoints, gateways, providers, EHR/ECM integrations, document types and the regulated workflows fax actually carries.
Test plan
Build the test plan across the four layers, protocol, document fidelity, integration and compliance, sized to the workflows and document types in use.
Run coverage
Execute coverage, T.30/T.38 protocol, document fidelity comparators, EHR/ECM integration scenarios and audit-log evidence, with packet captures where required.
Triage and evidence
Triage findings against a severity rubric, route to engineering and operations and capture evidence in the format the next HIPAA audit will expect.
Release readiness
Produce the fax release readiness pack, protocol interop, fidelity report, integration validation, compliance evidence and capacity posture.
Continuous stewardship
Quarterly fax QA review, refresh the provider matrix, retire unused workflows and absorb new EHR/ECM integrations or jurisdictions into coverage.
Deliverables
What you receive from every engagement
Documented artefacts at protocol, fidelity, integration and compliance phases, so fax QA becomes evidence engineering, operations and audit can all read.
01
Protocol
A T.30 and T.38 interop matrix, a gateway and SBC report, ECM and retransmission evidence and a codec and bandwidth posture.
T.30 / T.38 interop matrix
gateway and SBC report
ECM and retransmission evidence
codec and bandwidth posture
02
Fidelity
A page-count and order audit, an image-quality scorecard, OCR-readiness validation and a signature and form retention report.
page-count and order audit
image-quality scorecard
OCR-readiness validation
signature and form retention
03
Integration
An EHR and ECM coverage map, inbound routing evidence, outbound trigger evidence and a duplicate and merge audit.
EHR / ECM coverage map
inbound routing evidence
outbound trigger evidence
duplicate and merge audit
04
Compliance
A HIPAA and HITECH evidence pack, an audit-log review, access-control evidence and a BAA-aligned posture report.
HIPAA / HITECH evidence pack
audit-log review
access-control evidence
BAA-aligned posture report
Tools and lab
Tools and lab we run fax testing on
Fax becomes regulated infrastructure when its tooling, lab setup and compliance documentation make protocol behaviour, document fidelity and audit evidence demonstrable.
T.38 / T.30 testing stacks
Protocol-level fax behaviour and gateway interoperability validation
SIP trunk and ATA lab
Real-line and gateway lab for end-to-end fax round-trips
Document fidelity comparators
Page-count, image and OCR-readiness validation pipelines
EHR / ECM test harnesses
Integration test harnesses for Epic, Cerner, OpenText, M-Files
Wireshark / pcap tooling
T.38 packet capture and protocol-level diagnostics
HIPAA audit-log templates
Compliance evidence aligned with HIPAA, HITECH and BAA expectations
Risk patterns
Fax mistakes a structured engagement removes
These are the patterns we replace when QAble takes over a fax workflow, each one quietly converts a regulated channel into invisible operational risk.
Critical01
Silent delivery failures
Pages drop, recipients miss and the workflow keeps moving, there is no metric that says "fax delivery rate" and no operational owner who watches it.
Critical02
PSTN-to-cloud without interop
Cloud fax migration announced before T.38 interoperability and ECM behaviour have been tested end to end with real EHR/ECM integrations and the actual document fidelity matrix.
Critical03
PHI without an audit trail
Fax channels carry protected health information with weak audit logging, chain of custody is reconstructable only by hand and HIPAA evidence is rebuilt for every audit.
High04
Document fidelity drift
Page count, resolution or signature retention regressions after a vendor change, defects show up in OCR pipelines weeks later and force batch re-processing.
High05
EHR edge cases
Inbound and outbound integrations work on the happy path, multi-page, large attachment, encoded document and patient-identifier collision cases break in production.
Medium06
No capacity posture
Peak-hour throughput, queue depth and retry-storm behaviour have never been tested, outages happen when the same conditions recur in production and recovery is improvised.
Engagement Models
Ways to work with QAble
Three engagement shapes covering a focused fax audit, a fax migration programme and continuous fax QA across releases.
Release-Focused
2–4 weeks
Fax audit sprint
A focused audit of the fax surface, protocol, document fidelity, EHR/ECM integration and compliance, with an evidence pack and remediation roadmap.
Deliverables
Four-layer fax audit
Document fidelity scorecard
HIPAA/HITECH evidence pack
Remediation roadmap
Best for
Pre-audit posture
Vendor-change validation
Most Popular
6–12 weeks
Fax migration programme
A time-boxed programme around a fax migration, PSTN-to-cloud, T.30-to-T.38 or vendor change, with end-to-end interop validation and a release readiness pack.
Deliverables
T.38 interop validation
EHR/ECM integration readiness
Capacity and reliability posture
Release recommendation memo
Best for
Cloud fax migration
Vendor change windows
Flexible
Ongoing
Continuous fax QA
A standing fax QA capability across releases, protocol coverage, fidelity monitoring, integration regression and audit-cycle evidence stewarded across releases.
Deliverables
Sprint fax coverage report
Fidelity trend dashboard
Audit-cycle evidence
Quarterly fax QA review
Best for
Healthcare and EHR platforms
Regulated document workflows
Every model includes:
Certified QA engineersNDA on day oneDedicated account managerZero lock-in contracts
Why QAble
Why choose QAble
QAble runs fax QA across four explicit layers, protocol, document fidelity, integration and compliance, with capacity and reliability posture as a fifth pillar around the engagement.
Four-layer fax coverage, protocol, fidelity, integration and compliance, run as one engagement
T.30 and T.38 tested against real fax endpoints and gateways, not simulated round-trips
Document fidelity validated end to end, page count, resolution, signatures and OCR readiness
HIPAA and HITECH evidence captured in audit-ready format, not rebuilt for every audit
QAble fax testing expertise
T.30 and T.38 protocol interop95%
Document fidelity validation94%
EHR and ECM integration92%
HIPAA and HITECH evidence93%
Capacity and reliability posture90%
FAQ
Questions buyers actually ask.
Direct answers to the questions we get on the first advisor call.
Why does fax still matter in 2026?
In healthcare, legal and public-sector workflows, fax is still the channel that carries clinical results, signed orders, court filings and evidence of record. Cloud fax and Fax-over-IP have updated the mechanics, but the regulated nature of the channel, and the cost of silent failure, has not changed. It deserves engineering attention, not legacy treatment.
Do you cover both T.30 (PSTN) and T.38 (FoIP)?
Yes. Both protocols are first-class in the engagement. T.30 over PSTN covers call setup, capability negotiation, error correction (ECM) and retransmission. T.38 over IP covers packet behaviour, gateway and SBC interop, codec posture and the failure modes specific to IP transport.
How do you validate document fidelity?
Document fidelity is validated end to end, page count and order, image resolution, signature retention, line-art quality, font handling and OCR readiness for downstream processing. Comparators run between the original document and the received fax across the matrix of provider and gateway combinations in use.
How do you handle HIPAA and HITECH compliance evidence?
Audit logging, access control, retention and BAA posture are tested as part of the compliance layer. Evidence is captured in the format the next HIPAA audit will expect, chain of custody, access events, retention schedule and BAA-aligned data handling, so external audit becomes a confirmation rather than a discovery exercise.
Can you support cloud fax migrations?
Yes. The fax migration programme is built specifically for PSTN-to-cloud and vendor-change windows. Coverage spans T.38 interop, EHR/ECM integration, the document fidelity matrix across the new provider, capacity and reliability posture under realistic peak hour and the release readiness pack the change board can sign.
How quickly can a fax engagement begin?
Most fax engagements begin within two weeks of scope agreement. The first week maps the fax surface and builds the test plan; lab and provider access is provisioned in parallel. Active coverage begins in week two. For migration windows, engagement can be accelerated with a focused kick-off scoped to interop and fidelity first.
Fax engineered as regulated infrastructure
QAble runs fax and Fax-over-IP testing across protocol, document fidelity, integration and compliance, so the channel that still carries regulated workflows is treated with the rigour those workflows demand.
Fax testing engineered across protocol, fidelity and compliance
QAble runs fax and Fax-over-IP testing as engineering practice, four-layer coverage, a real-line lab, document fidelity comparators and HIPAA-aligned audit evidence.
No sales pitch
Technical walkthrough
No lock-in commitment
Talk to QA Advisor
Direct access to QAble's fax engagement leads.
Response within 24 hours