CMS-1500 → X12 837P
Paper claims in.
Valid 837P out.
Wave-EDI converts printed and paper CMS-1500 claims into X12 837P files your clearinghouse accepts. A claim it cannot read with confidence is refused — not guessed at, and not sent to your payer looking perfectly normal.
Converted by us, or run it yourself. Either way it starts with a free consultation.
What it does
The converter accurately processes each claim, and alerts you if a claim has an issue.
A CMS-1500 is a grid. Wave-EDI finds every field by its row and column, so a value is read from where it actually is rather than guessed at.
Takes the claim in the form you already have
Most claims never touch paper — they are printed to PDF straight out of the billing software. Wave-EDI converts those for you. The column-positional print-image files older practice-management systems produce can go either way: converted by us, or by your own staff in a browser.
- PDFs printed from billing or practice-management software — converted by Wave-EDI
- Print-image claim files, including multi-claim batches — by us, or by you
- Existing field maps from the legacy Wave Translator, imported as they are
- A layout built for your form and proven against your own output before go-live
24F Charges .......... 50 00
28 Total charges .... 215 00
21 Diagnosis A ...... E11.9
21 Diagnosis B ...... I10
33 Billing provider . ELM SAMPLE MEDICAL CENTER
33a NPI .............. 1999999991
Refuses a claim it cannot read, instead of guessing
This is the part that matters. A misread claim still produces structurally valid X12 — it passes a 999 and goes to the payer looking perfectly normal. A decimal point lost in a scan turns $165.00 into $16,500. Wave-EDI is built to stop that file rather than send it.
- Service lines must add up to the total charge, read exactly as the file will carry it
- A value clipped by the edge of its box refuses that claim and names the field
- An all-digit diagnosis code under an ICD-10 qualifier is reported, not shipped
- An NPI with the wrong number of digits refuses the claim — a dropped digit is what a scan actually gets wrong
- Every refusal names the box, the value it read, and why it stopped
28Totalcharges = "21500"
the service lines add up to 16550.00
but the total says 21500.00 — one of
these numbers was read wrongly, and
the claim cannot be right either way
Keeps your trading-partner details straight
Submitter and receiver IDs, the billing entity, the interchange header — set up once per trading partner during configuration, and checked against every file before it converts.
- A file whose Box 33 billing provider is not the selected profile's is refused
- One profile per trading partner, so a second payer is a choice rather than a re-entry
- Which 837 version a partner requires is part of the profile, not a per-file decision
- Submitter
- MERIDIAN FAMILY CLINIC
- ETIN
- SUB123456
- Billing NPI
- 1999999990
- Receiver
- MERIDIAN STATE HEALTH PLAN
- Receiver ID
- RCV987654
- ISA05 / ISA07
- ZZ / ZZ
Getting started
Three steps, and the first one is free
Nothing goes straight into production. We look at what you have, prove the conversion against your own claims, and only then put it to work.
Free consultation
What your claims look like now, roughly how many there are, and who you send them to. No charge, and no obligation to go any further.
Testing and configuration
We build the layout for your form, convert test claims from your own system, and show you the 837P beside what you expected. Your delivery route is set up here too.
Go-live
Claims start converting for real — sent to us, collected over SFTP, or run by your own staff. We stay reachable while it settles in.
Two ways to use it
Run it yourself, or hand it to us
Both start with the same consultation and the same account. What differs is who does the converting — so it is stated here rather than buried.
Your own staff converts, in a secure web browser portal
Print-image claim files can be converted by whoever handles your billing. They sign in to the portal in a browser, the conversion runs on the computer in front of them, and the 837P is saved straight to it.
An account is still needed — it is what holds your trading-partner configuration and the layout we built for your form. There is still nothing to install.
Print-image files. PDFs are converted by us.
Send the claims, get the 837P back
Upload claims to our secure portal, or have your system drop them over SFTP so nobody has to remember to send anything. We convert them and return 837P files ready for your clearinghouse.
This is how every PDF is handled, and what we recommend for print-image claims as well: a claim we convert is a claim we have checked.
Recommended — ask what it involves.
How claims reach us
Not by email. Not by web form.
A claim file is patient data, so how it travels matters as much as what happens to it afterwards. Claims reach us through a secure portal or over SFTP, and by no other route — which one you use is settled with you during configuration.
Secure Portal
Sign in and upload the claims you want converted. Each practice sees only its own files, and the completed 837P is available for download.
Secure File Transfer Protocol (SFTP)
For steady volume, your system drops claims into an SFTP folder and collects the 837P from it. Nobody has to remember to send anything, and nobody retypes a thing.
Other formats
We also convert CSV and Excel to 837P
Plenty of billing software will not print a claim but will happily export one. If what you have is a spreadsheet, send us a sample — we map its columns during configuration, the same way we map a printed form.
Not sure whether your export has what an 837P needs? Send us a sample and we will tell you on the consultation call.
FAQ
Why choose Wave-EDI Services?
A claim processed incorrectly fails silently.
That is the problem this was built around. Over 20 years in healthcare EDI went into the checks we run, and each one catches a mistake before it reaches your payer. See a claim converted.
Does Wave-EDI submit claims to payers?
Wave-EDI produces the 837P file, delivered through the Secure Portal or over SFTP. Next, you send it directly to your clearinghouse or payer. If you would rather we handled that too, please contact us.
What claims can be processed today?
PDFs printed from billing software, and the column-positional print-image files older practice-management systems produce. PDFs are converted by us; print-image files can be converted by us or by your own staff.
Processing PDF files through optical character recognition (OCR) is a service we offer. Contact us so we can convert a sample batch of claims for you.
Do we have to set up the form layout ourselves?
No, we build it during configuration. All it takes to start is sending us sample PDFs or Print Image Text files. The test claims will be converted for your review.
Can you just convert the claims for us?
Yes — and for PDFs that is how it works. Upload them to our secure portal or have your system drop them over SFTP, and 837P files come back ready for your clearinghouse.
It is what we recommend for print-image claims too. Running it yourself is there for practices that would rather keep the work in-house, and we will walk you through both rather than steering you to one.
Which 837 version do you produce?
Version 5010 (005010X222A1) claim files, HIPAA compliant and accepted by clearinghouses and payers. If you need other claims translated into different formats, please contact us.
What if we send a claim that does not meet the minimum requirements?
If a claim does not meet the requirements to be converted, we send a report explaining why it could not be processed. For example, if the billing NPI is not a valid ten-digit number, we exclude that claim from the batch of good claims.
Do you see our patient data?
If we convert your claims, then yes — the claims come to us, because they have to. That is the arrangement, and a signed agreement governs it before a live claim ever reaches us.
If your own staff converts a print-image file, the conversion itself runs in the browser on their machine rather than on a server of ours. That is a property of how the software works rather than a promise about how we behave.
Do we need an account?
Yes, whichever way you transmit the files to us — either Secure Portal or SFTP file transfer. The account holds your trading-partner details and more. There is no software to install.
Do you sign a business associate agreement?
Yes, we can sign a business associate agreement. It covers details such as how claims are handled, how long they are kept, access, and more.
What does it cost?
Pricing is not published yet. Contact us and we can get you a quote.
Tell us what you are converting
A few details about your claims and your clearinghouse is enough to say whether this fits.