Quadax makes the claim before the money

At The Ohio State University Wexner Medical Center, the revealing feature of a claims system was permission. When an insurer changed a policy, the billing team wanted to change the corresponding rule itself. Waiting for a vendor could take weeks, an associate director explained in a Quadax case study. Meanwhile, the claim waited too. A medical encounter had become a software dependency.

The rule that holds up the money

Quadax gave the Ohio State team a way to make those adjustments internally. The case study reports claims processing in 18 days from the date of service, against a 30-day target. That is a comparison with a goal, not a before-and-after experiment. It also measures processing, not the arrival of cash. Those distinctions matter in a business where several different clocks are always running.

The lesson travels beyond hospital accounting. An organisation can automate a process and still leave every exception waiting for somebody else. Ask who can change the rule, how that change is checked, and what happens to the work while approval is pending. The bottleneck may be authority.

A computer expensive enough to remember

Quadax began in Cleveland in 1973, founded by Ralph Daugstrup and Tom Hockman after working together at IBM. Its first customer was Ohio Medicaid. Daugstrup wrote a medical billing edits program; Patricia Gallagher, the first employee, helped manage data-entry production. This was healthcare administration with punch cards.

In 1978, the company bought its first computer, an HP3000, for $125,000. That purchase gives the origin story a pleasing weight. Before cloud architecture and conversational analytics, there was a substantial machine purchased to do a particular job. Quadax’s own history dates an early electronic data interchange implementation to 1974. The tools have changed dramatically. The recurring work is still to make healthcare transactions intelligible to the organisations receiving them.

The unglamorous chain of custody

A clearinghouse sits between the provider generating a claim and the payer receiving it. Quadax’s Xpeditor validates claims, applies edits and connects them to payers. XpressBiller supplies custom rules and workflow controls. Think of the edit as a checkpoint: catch a missing or inconsistent detail before it starts a longer journey through somebody else’s system.

The surrounding products address the work on either side. Patient Access checks eligibility, searches for undisclosed insurance and supports authorization and cost estimates. At the other end, RemitMax converts paper explanations of benefits into electronic remittance files called ANSI 835s. That lets payment information enter automated posting and follow-up workflows instead of remaining a document somebody must handle separately.

There is a useful order here. Coverage is checked before the claim; claim details are checked before submission; payment is compared with expectations afterward. Each step produces information the next person needs. When that information remains attached to the work, a billing specialist has fewer places to search before deciding what to do. That is the operational logic behind putting these products together.

Acceptance is only one milestone. A claim can pass the initial checks and still face a coverage dispute or an incorrect payment. Quadax’s May 2026 partnership with SlicedHealth extends the picture to contract modeling and reimbursement intelligence, connecting what a contract says should arrive with what actually does.

Software, people, or both

The customer is buying a way to run an operation. For laboratories, Quadax offers three arrangements: SaaS for teams keeping billing in-house, outsourced services for those handing over the work, and a hybrid for organisations needing additional capacity. The difference is practical. Who maintains the work queue? Who investigates a denial? Who stays accountable when a payment does not match expectations?

Its laboratory page names customers including Lucid Diagnostics, BostonGene and Streamline Scientific. It also reports that 37% of staff have more than ten years of billing experience. That is a company-reported workforce measure, but it helps explain the proposition: the people interpreting payer behavior are part of the purchase.

Quadax remains privately held, a choice it emphasizes when describing its independence. Its market includes other claims and clearinghouse vendors, such as The SSI Group and Experian Health. Product fit depends on the workflow. Quadax’s case rests on configurable controls, payer knowledge and service. KLAS named Xpeditor its 2026 Claims Management & Clearinghouse winner, with a score of 92.8.

The next queue is already here

Hospital software arrives among other hospital software. Quadax supports Epic Resolute workflows and joined the MEDITECH Alliance in August 2025. Its December 2025 Streamline partnership brought its technology into SMARTedi, a clearinghouse offering for behavioral health clients. Integration is central to its place in the market: providers need improvements that fit their existing clinical and financial systems.

On September 28, 2026, Quadax introduced QDXOne, a cloud platform intended to connect work across its solutions. The announcement describes shared task management, exception-based priorities, automation and recommended actions. The ambition is recognisable to anybody who has opened several applications to answer one question: make the encounter visible without another hunt through another queue.

“Don’t buy AI. Buy outcomes.”

Eric Matson’s session, 2026 Xpeditor User Conference recap

At that conference, Quadax showcased AskQ for product guidance, Ask DataIQ for questions about operational data, and CorrectiQ for identifying claim errors and recommending corrections. These are specific jobs for AI. Their usefulness depends on data quality, implementation and staff readiness, challenges the conference itself addressed.

That also makes implementation a management decision. Giving staff control over edits requires agreement about who may alter them and how the results will be reviewed. Outsourcing a queue requires agreement about escalation. Connecting a new tool requires checking what information the existing system actually supplies. A demonstration can show the happy path; a purchasing team should bring an awkward claim and ask to follow it through the exceptions. The answer will reveal more than a dashboard full of averages.

A buyer can borrow the discipline immediately: pick a troublesome handoff, establish its current timing and assign somebody to own the exception. Then measure whether the new workflow changes the work. The claims system earns its place when the next payer rule arrives and the team can keep moving.