Try it
The engine, running in your browser.
Paste a remittance, an acknowledgment, an eligibility or claim status answer, or a claim; run the sandbox payers; write an appeal letter; follow up on open claims and count your own denials; write a prior authorization; or estimate what a patient owes. Payerworks reads each with the same code its API runs and answers in words, on this page, without sending anything anywhere.
Runs in your browser. Nothing you paste is sent anywhere.
Nothing leaves your browser
The page loads the engine itself and runs it on your machine: there is no request to make, so a file with patients on it stays where it is.
The samples are invented, from the patient to the member id. To run the same checks from your own system, the Developers page lists the API and gives you a test key.
The sandbox payers are invented too: how the member ID ends decides what each answers, from a rejected or denied claim to a plan not found or a claim the payer cannot find yet, so you can see every path before a real payer is involved.
Some checks run only in the API, because what they read is too large or too heavy for a page: the diagnosis and HCPCS code releases, Medicare’s DMEPOS fee schedule, the payer directory, and the 837I and 837D readers. A claim checked here says which code checks it could not run, a payment compared with Medicare’s rate here says the rate is not held on this page, and an institutional or dental claim file pasted here is named, not read.
The page loads its engine when it opens, and each newer tool’s part only the first time you run it, so a newer tool you never open is never downloaded.
Talk to us
What happens next
- 1
A person at Payerworks reads what you sent, usually within a business day.
- 2
One reply by email names the next step: our trading partner details, where each of your payers stands, or a key for the API.
- 3
Nothing follows unless you answer. There is no sequence behind this form.
Or write to hello@payerworks.com.