Get started
Revenue cycleLive · in the productMoney

ClaimsUS

US claims as X12 837 files, with 999, 277CA and 835 read back in.

Offered in: United States only.
Get ClaimsUSOpen the appAvailable nowHow pricing works →

What it is

A US practice’s claims in the format US payers take: X12 005010. A professional (837P) or institutional (837I) claim is built from one of your own finalised bills — the lines and their HCPCS or CPT codes from the bill’s service items, the ICD-10-CM diagnoses from the chart — and held in draft with the reason until it is complete (member id, place of service or facility type, the subscriber when it is not the patient). Ready claims go into an interchange that is checked against the implementation guide’s structure — envelope, control numbers, segment counts, loop order, NPI check digit, codes and pointers — before it is kept, byte for byte with its hash. The clearinghouse’s answers are read back in: a 999 accepts or rejects the file, a 277CA accepts or rejects each claim with its category code, and an 835 records what the payer paid, the adjustment group and reason codes, and whether each claim balances; an unmatched remittance line is held, never guessed. Sending is not connected until your clearinghouse trading-partner agreement exists: the file is downloaded and uploaded on the clearinghouse’s portal meanwhile. Billing provider, submitter and receiver ids are your own settings; none ship.

Who uses it
Built for: Every specialty
Reads
Finalised bills, service-item HCPCS/CPT codes, ICD-10-CM diagnoses
Writes
837P/837I files, claim states, 999/277CA acknowledgements, 835 remittances
Never
It does not invent a code to make a claim pass — a line with no code or a claim with no diagnosis does not go — and it does not send to a clearinghouse or post a remittance to the bill: the connection needs your trading-partner agreement, and posting stays a person’s job in Billing.
Access
Only people whose role includes it — the clinic owner decides who
Your data
Full PHI. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

In the product

Who uses it
Finance manager — the demo profile it is best tried as
Where it opens
Revenue cycle › US payer claims /claims-us
Permission
claimsus.read
Every revenue cycle app in the handbook →

How it works

  1. Set up onceEnter your billing NPI (its check digit is checked), EIN, address, and the submitter and receiver ids your clearinghouse gives you; add each payer with its payer id.
  2. Build and fileBuild a claim from a finalised bill; fill what it says is missing until it is ready, then make the 837 file, checked against the guide, and download it for the clearinghouse’s portal.
  3. Read the answers inPaste the 999, the 277CA and the 835: rejected claims come back to be corrected, accepted ones carry the payer’s claim number, and payments land on each claim.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not invent a code to make a claim pass — a line with no code or a claim with no diagnosis does not go — and it does not send to a clearinghouse or post a remittance to the bill: the connection needs your trading-partner agreement, and posting stays a person’s job in Billing.

AI in ClaimsUS

AskQuestions about what is on screen — “What needs attention in ClaimsUS today?” — answered with the records it read.
DraftSummaries and notes for the team, marked as drafts until a person signs.
Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Live product
01US payer claims — Turn a US bill into an X12 837 claim and read the 999, 277CA and 835 back inCaptured from the running demo clinic
ClaimsUS — US payer claims — Turn a US bill into an X12 837 claim and read the 999, 277CA and 835 back in
1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

See the whole clinic →

Questions clinics ask

What does ClaimsUS do?
US claims as X12 837 files, with 999, 277CA and 835 read back in. A US practice’s claims in the format US payers take: X12 005010. A professional (837P) or institutional (837I) claim is built from one of your own finalised bills — the lines and their HCPCS or CPT codes from the bill’s service items, the ICD-10-CM diagnoses from the chart — and held in draft with the reason until it is complete (member id, place of service or facility type, the subscriber when it is not the patient). Ready claims go into an interchange that is checked against the implementation guide’s structure — envelope, control numbers, segment counts, loop order, NPI check digit, codes and pointers — before it is kept, byte for byte with its hash. The clearinghouse’s answers are read back in: a 999 accepts or rejects the file, a 277CA accepts or rejects each claim with its category code, and an 835 records what the payer paid, the adjustment group and reason codes, and whether each claim balances; an unmatched remittance line is held, never guessed. Sending is not connected until your clearinghouse trading-partner agreement exists: the file is downloaded and uploaded on the clearinghouse’s portal meanwhile. Billing provider, submitter and receiver ids are your own settings; none ship.
What data does ClaimsUS read and write?
ClaimsUS reads finalised bills, service-item HCPCS/CPT codes, ICD-10-CM diagnoses and writes 837P/837I files, claim states, 999/277CA acknowledgements, 835 remittances. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
What does ClaimsUS deliberately not do?
It does not invent a code to make a claim pass — a line with no code or a claim with no diagnosis does not go — and it does not send to a clearinghouse or post a remittance to the bill: the connection needs your trading-partner agreement, and posting stays a person’s job in Billing.
What happens to our data if we uninstall ClaimsUS?
Every record stays; only the workflow leaves.
Is ClaimsUS available today?
Yes — ClaimsUS is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.
Where is ClaimsUS offered?
ClaimsUS is offered in United States only: it is built on that market's own systems and rules.

Want to see ClaimsUS running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Revenue cycle

All 36 →