Skip to content
Contract-aware revenue integrity for hospitals and health systemsEvery finding cites the contractReport-only, your team decidesHIPAA BAA signed before any data moves

HomeHow it works

One engine at both ends of the claim

How Clinical Speed works

Clinical Speed sits at both ends of the hospital's claim, before the payer adjudicates it and after. The hospital sends the 837 claim, the payer adjudicates it under its reading of the contract, and the 835 remittance comes back with the payment and the payer's reason codes for every adjustment. Clinical Speed checks the claim before it leaves and the remittance after it returns, and both checks run on one executable model of the hospital's contracts. The work has four parts, and each one builds on the model made in the first.

The Resolution Center proving one underpaid claim: $3,881.48 owed, the contract, plan column, rule and result, then every line priced against the contract
Demo Hospital account · payer and patient identifiers blurred

The claim path

The 837 goes out, the 835 comes back, and both are checked

The claim path: 837 to the payer, 835 back, checked on both sides by one contract engineTHE HOSPITALRevenue cycle01Chargemaster setseach price02Coders and billersbuild the 83706835 posted,shortfalls writtenoffTHE PAYERAdjudication04Prices the claimunder its readingof the contract05Sends the paymentand a reason codeon everyadjustmentCLAIM OUTPAYMENT BACKCheck before send837Codes, units and chargesClearinghouseCheck after payment835Paid, adjusted, CARC and RARCRemit routed backONE CONTRACT ENGINEYour contracts, executedBefore the claim leaves, the engine shows whateach line should be paid. After the remitreturns, it proves what the payer underpaid.
The claim path: 837 to the payer, 835 back, checked on both sides by one contract engineCharges postedPrices from your chargemasterCheck before send837Your claim,hospital to payerClearinghousePayer adjudicatesIts reading of your contract835Payment and itsreasonsCheck after paymentPayment postedShortfalls written offONE CONTRACT ENGINEYour contracts, executed

The Underpayment Audit

Four parts, each built on the contract model

See it on a demo
1

The contract becomes executable logic

Clinical Speed digitizes 100 percent of the payer contracts a hospital submits. Engineers and contract analysts code every value on every page, including fee schedules and rate tables, modifier rules, bundling and unbundling, multiple-procedure reductions, carve-outs, stop-loss language, outliers, lesser-of provisions, case rates, per diems, percentage-of-charge terms, timely-filing windows and the policy attachments that govern payment. Each contract is validated with the hospital before coding begins. The models are effective-dated, so a remit is priced on the rate sheet in force on its date of service, and contracts that have since been amended or expired are coded for the dates they governed.

4 to 6 weeks from a complete contract set
2

Every remit is priced against the contract

The engine reads the hospital's 835 remittances and 837 claims in the HIPAA 5010 standard and matches each remit to its claim on the hospital's claim number. The claim supplies what the remit leaves out: the member ID that selects the plan column, the diagnoses and every billed line. This pairing lets the engine work out what the contract allows, subtract the patient's share and any federal sequestration reduction, and compare the result with what the payer paid. Claims paid over several remits through corrections, reversals and re-payments are read as one record, so a later correction is never counted as an underpayment. The forensic calculation typically completes in less than a week once the files are in.

HIPAA 5010 835 and 837 files
3

Each underpayment is proven, line by line

An underpayment is a payment that, with the patient's share, falls below what the contract allows for the service on the rate sheet in force on the date of service, after the lesser-of test. The patient's share and any sequestration reduction are never claimed from the payer. The Resolution Center states, for each underpaid claim, the contract, the plan column, the rule and the result, and then every line in full with the payer's adjustments written out in words beside each CARC and RARC. These lines are also checked against NCCI pair edits and benchmarked against the Medicare amount under IPPS or OPPS for the year of service. The output is a structured file of underpaid claims, each with its variance, its contractual basis and the evidence an appeal requires.

The Resolution Center
4

Verified findings are recovered

The hospital's team reviews every finding, and nothing moves to appeal until it is verified. Our AI then writes the dispute reason for each underpaid line from the structured contract policy, thousands of them an hour, and assembles them into payer-specific appeal packages that cite the contract term and show the calculation. Our appeal-execution partner, named in the client agreement, executes each appeal under the hospital's authority, tracks it against its filing deadline and escalates it level by level. The hospital sees every case, every action and every appeal document on its own read-only screens. Weekly reports follow the work, and a monthly recovery report is delivered by the fifth business day.

Weekly reports, monthly recovery report
Commercial terms

Contingency-based, with no setup fee. Nothing is owed if nothing is recovered.

The 837 and the 835

How a claim is billed and paid, and the two points where we check it

  1. 01

    Charges posted

    Prices come from your chargemaster.

  2. Check before send02

    837 claim

    Your bill, hospital to payer.

  3. 03

    Clearinghouse

    Routes claims and remits.

  4. 04

    Payer adjudicates

    Applies its reading of your contract.

  5. Check after payment05

    835 remit

    The payment and its reasons, payer to hospital.

  6. 06

    Payment posted

    Shortfalls are written off as contractual adjustments.

837

ASC X12 Health Care Claim

Hospital to payer · 837I institutional, 837P professional

“Here is what we did and what we charge.”

Carries
Member ID, ICD-10 diagnoses, CPT and HCPCS codes, revenue codes, modifiers, units and charges
We check
The expected allowed amount for each line, missing elements and bundling conflicts, and the cap-risk flag where a charge sits below what the contract would pay
835

ASC X12 Claim Payment and Advice

Payer to hospital · also called the ERA or remit

“Here is what we paid, what we adjusted and our reason.”

Carries
Paid and allowed amounts, patient share, the EFT trace and a reason code on every adjustment
CO-45CO-97CARCRARC
We check
Each line against the contract in force on the date of service, with the payer's reasons written out in words

What the engine knows

Code policy and dispute reasons from your own contracts

Code-policy expertise from your own contracts

Clinical Speed is expert in code policy because every payer contract and fee schedule the hospital holds is loaded into its system. The engine knows, payer by payer and code by code, how each contract treats modifiers, bundling and unbundling, NCCI pair edits, multiple-procedure reductions, units, revenue codes, DRG and APC grouping, carve-outs, per diems, case rates, outliers, stop-loss and timely-filing windows. A generic rule library describes how payers behave on average, while this model describes how one payer must pay one hospital under the contract both of them signed.

AI that writes the dispute reasons

Our AI writes thousands of contract-cited dispute reasons an hour for the underpaid lines found on the 835. Each reason is drawn from structured policy that our engineers code from the hospital's payer contracts and payment schedules, so each one cites the clause, the plan column, the rule and the calculation behind the amount owed. The reasons are assembled into payer-specific appeal and reconsideration packages for commercial payers, Medicare contractors and state Medicaid programs, so every eligible line is worked, including the small balances manual appeal work leaves behind.

Start with underpayments

One engagement, every product

Most hospitals start with the Underpayment Audit, because underpayments lead the first conversation and the audit costs nothing up front.

That engagement already codes the payer policy and loads the 837 and 835 history, and the same data supports a review for every product. During the engagement, Clinical Speed presents the hospital's own Max Allowable and Encounter Integrity findings, and each installation is then proposed with its scope: the data feeds, the hospital hours required, the time to go-live and the contracts coded.
THE STANDARD ENGAGEMENT

Underpayment Audit

Line-level underpayment findings, each cited to its clause, with overpayments reported to the compliance office. This is the standard engagement.

Commercial terms: Contingency-based, with no setup fee. Nothing is owed if nothing is recovered.

FROM THE SAME DATA

Max Allowable Audit

Lost to Cap in full for the coded payers, and a Contract Basis view of the quoted clauses, the charging pattern, the bundled lines and the 837-to-835 trend.

The installation adds the outbound 837 feed, the CDM Repricing Proposal and the Epic reconciliation report.

FROM THE SAME DATA

Missed Charge Audit

Pattern findings from the claim history, priced through the contract with their filing clocks and shown as counts for documentation review.

The installation adds pre-bill operation, the clinical-event feeds and delivery to the hospital's workqueues.

FROM THE SAME DATA

Care Gap Review

A walk-through of the method for clinical leaders: how each rule is cited and adopted, and what a worklist item looks like.

The installation adds the clinical extracts, committee rule adoption and sign-off by the CMO and the compliance office.

Included with the Max Allowable Audit

Pre-Submission Contract QA

Pre-Submission Contract QA is included with the Max Allowable Audit. It evaluates every outbound institutional and professional claim against the executed contract before it is transmitted, from a scrubber or clearinghouse hold or a pre-bill extract at bill hold.

It returns the expected allowed amount for the claim and each line with the clause behind it, the cap-risk flag where a charge sits below what the contract would pay, denial and underpayment risk scores built from the hospital's own contracts and 835 history, missing elements, bundling conflicts and payer edits, and clause-cited evidence packs. It never suggests a modifier to get past an edit, and it never alters the claim. Epic-native deployment is available for Epic environments, and Clinical Speed runs on any other patient accounting system through standard 835 and 837 files, beside the hospital's existing claim scrubber and EHR edits.
One contract engine with two surfaces: the Underpayment Audit on the 835 and the Max Allowable Audit on the 837ContractsFee schedulesAmendmentsONE EXECUTABLE CONTRACT ENGINEYour contracts, executedEvery value on every page, effective-datedPriced on the rate sheet in forceEvery finding cites the clauseDeterministic expected allowed835 · AFTER THE REMIT RETURNSUnderpayment AuditAfter payment, contingency-based100% contract digitization12 to 24 month lookbackLine-level variancesAI-assisted appealsWeekly reportingRecovered by clause-cited appeal837 · YOUR CHARGES AND OUTBOUND CLAIMSMax Allowable AuditYour chargemaster against your contractsM1Lost to CapM2Contract Basis by service lineM3CDM Repricing ProposalM4Pre-Submission Contract QAM5Cap-risk and denial-risk flagsStopped at the source, report-onlyReport-only by designNothing is written back to the claim, the codes or the ledgerONE ENGINE. TWO SURFACES. ONE COPY OF YOUR CONTRACTS.
One contract engine with two surfaces: the Underpayment Audit on the 835 and the Max Allowable Audit on the 837ContractsFee schedulesAmendmentsONE EXECUTABLE CONTRACT ENGINEYour contracts, executedEvery value on every page, effective-datedPriced on the rate sheet in forceEvery finding cites the clauseDeterministic expected allowed835 · AFTER THE REMIT RETURNSUnderpayment AuditAfter payment, contingency-based100% contract digitization12 to 24 month lookbackLine-level variancesAI-assisted appealsWeekly reportingRecovered by clause-cited appeal837 · YOUR CHARGES AND OUTBOUND CLAIMSMax Allowable AuditYour chargemaster against your contractsM1Lost to CapM2Contract Basis by service lineM3CDM Repricing ProposalM4Pre-Submission Contract QAM5Cap-risk and denial-risk flagsStopped at the source, report-only

Engagement

The engagement, step by step

  1. Agreement. The hospital reviews the Clinical Speed services agreement and the Business Associate Agreement, and onboarding is scheduled.
  2. Contract scope. The payers, products and facilities in scope are identified with the managed care team.
  3. Contract transfer meeting. A one-hour session covers the upload of contracts, fee schedules, amendments and rules, and starts clearinghouse, payer-portal and SFTP access.
  4. Contract validation. Each contract is verified with the hospital before coding.
  5. Coding and digitization. Four to six weeks from a complete contract set.
  6. Data upload. 835 remittances for a 12 to 24 month lookback arrive near the end of coding, and 837 files arrive at the agreed integration point.
  7. Forensic audit calculation. Typically less than a week.
  8. Verification. The hospital reviews the findings. No appeal file moves without that review.
  9. Appeal setup. Verified underpayments are loaded into the appeal platform.
  10. Weekly cadence. New remittances arrive each week, results are reported each week and recoveries are reported monthly. Fees are invoiced only after recovered cash is reconciled and posted to the hospital's accounts.

Roles

Who provides what

What the hospital provides

  • Payer contracts and amendments for the agreed audit scope, including the historical versions that governed the lookback window.
  • 835 remittance files for the lookback, typically 12 to 24 months.
  • 837 claim files or equivalent claim extracts for the same lookback.
  • Provider, plan and department mappings that connect claims to their contracts.
  • A designated contact for review and verification, a weekly file upload and replies to requests within five business days.
  • Named, read-only EHR and payer-portal accounts for the records each appeal needs, issued under the hospital's own access policy.

What Clinical Speed provides

  • Contract coding and model validation.
  • Processing of the authorized 835 and 837 data.
  • The forensic calculation and structured findings.
  • Evidence packs and appeals for every verified finding.
  • Weekly reporting and status tracking.
  • Overpayment findings for the hospital's compliance office, date-stamped.
  • The Max Allowable Audit and Encounter Integrity findings from the same data, with each installation scoped in its proposal.

Request a demo

See the contract model and the proof on a demo

The demo runs on the de-identified Demo Hospital account, with every name replaced and the dollar amounts kept.