{"id":183222,"date":"2026-08-17T13:48:23","date_gmt":"2026-08-17T13:48:23","guid":{"rendered":"https:\/\/pabau.com\/?p=183222"},"modified":"2026-08-18T09:28:32","modified_gmt":"2026-08-18T09:28:32","slug":"837-file","status":"publish","type":"post","link":"https:\/\/pabau.com\/nl\/blog\/837-file\/","title":{"rendered":"What is an 837 file?"},"content":{"rendered":"
\n
\n \"Key\n

Key takeaways<\/h3>\n <\/div>\n
\n
\n
\n \n \n <\/svg>\n <\/div>\n

An 837 file is the electronic healthcare claim providers send to payers, written in the X12 EDI format HIPAA adopted.<\/p>\n <\/div>\n

\n
\n \n \n <\/svg>\n <\/div>\n

Three variants exist: 837P for professional claims, 837I for institutional claims, and 837D for dental claims.<\/p>\n <\/div>\n

\n
\n \n \n <\/svg>\n <\/div>\n

Nobody types an 837 by hand. Billing software generates the file from the invoice and sends it.<\/p>\n <\/div>\n

\n
\n \n \n <\/svg>\n <\/div>\n

Three files come back in order: a 999 confirms the batch parsed, a 277CA accepts each claim, and an 835 reports payment.<\/p>\n <\/div>\n

\n
\n \n \n <\/svg>\n <\/div>\n

A rejected 837 never reached adjudication, so there is nothing to appeal. Fix the data and resubmit.<\/p>\n <\/div>\n <\/div>\n <\/div>\n \n\n\n

An 837 file is the electronic version of a healthcare claim. It is the standard file your practice sends to a payer instead of mailing a paper form. The file is plain text, built to the X12 EDI standard, and it is the format HIPAA requires for electronic claims<\/a>.<\/p>\n\n\n\n

Open one and it looks like machine noise. Rows of capital letters, asterisks and tildes, no labels, no line breaks in the places you expect. But the content is familiar. It carries exactly what a CMS-1500 carries: the patient, the provider, the insurance, the diagnoses, the services, and the charges.<\/p>\n\n\n\n

Most people never need to read one. You do when a claim fails at the clearinghouse<\/a> and the message names a segment you have never heard of. This guide translates the file into plain English, walks a sample fragment line by line, and shows what to do when one comes back rejected.<\/p>\n\n\n\n

837P, 837I and 837D: The three claim types<\/h2>\n\n\n\n

The three 837 variants each replace a different paper claim form. Which one you send depends on the kind of provider you are, not on the treatment or the payer.<\/p>\n\n\n\n

Variant<\/th>Paper equivalent<\/th>Who sends it<\/th><\/tr><\/thead>
837P<\/b> (professional)<\/td>CMS-1500<\/td>Physicians, nurse practitioners, physical therapists<\/a>, med spas, private practices, suppliers<\/td><\/tr>
837I<\/b> (institutional)<\/td>UB-04, also called the CMS-1450<\/td>Hospitals, skilled nursing facilities, hospices, other facilities<\/td><\/tr>
837D<\/b> (dental)<\/td>ADA Dental Claim Form<\/td>Dentists and dental specialists<\/td><\/tr><\/tbody><\/table>
All three are the same transaction number, so “837” on its own never tells you which claim type someone means.<\/em><\/figcaption><\/figure>\n\n\n\n

Federal regulation names each one separately. The professional version is ASC X12N 005010X222, the institutional version 005010X223, and the dental version 005010X224. You will see the professional one written as 5010A1, which is the same guide with its errata applied.<\/p>\n\n\n\n

Everything below uses the 837P, because that is what almost every non-facility practice sends. Office visits, injections and therapy sessions all bill on it. So do the medication reviews an ADHD practice<\/a> runs.<\/p>\n\n\n\n

The implementation guide is not quite the last word, though. Payers publish companion guides that pin down the elements the standard leaves situational. Two plans can want the same field filled in differently, which is one reason a claim accepted by one payer bounces at another.<\/p>\n\n\n\n

What’s inside an 837: Loops and segments in plain English<\/h2>\n\n\n\n

An 837 is organized into segments and loops. A segment<\/strong> is one line carrying one kind of record, and it always starts with a short code naming what it holds. A loop<\/strong> is a group of segments describing one entity, such as the billing provider or a single claim.<\/p>\n\n\n\n

Inside a segment, data elements are separated by a delimiter, usually an asterisk. Sub-elements inside one element are separated by a colon. Every segment ends with a terminator, usually a tilde. Those three characters are all the punctuation the format has.<\/p>\n\n\n\n

Loops are numbered, and the numbers matter because rejection messages quote them. These four carry the claim itself:<\/p>\n\n\n\n