Compliance

837P Claims for Home Health Agencies: A Practical Guide

What an 837P claim is, what goes into it, where EVV data fits, and how validation, rejection and resubmission work for home health agencies.

Sources checked October 5, 20265 primary sources

The visit is over and the notes are done. Payment still depends on the claim, and for most professional health care billing that claim is an 837P. This guide explains what the 837P is, what goes into one, where EVV fits for Florida Medicaid agencies, and what happens when a claim is rejected.

What is an 837P?

The ASC X12 837 Professional ("837P") is the electronic format HIPAA adopted for professional health care claims. Federal regulation at 45 CFR § 162.1102 names the ASC X12N 837 Health Care Claims: Professional as the standard for that transaction.[1][2]

The "P" stands for professional. Other 837 variants exist for institutional and dental claims.[1] Which variant a home health agency uses depends on the payer and the type of service. Confirm with each payer's companion guide or provider manual.

What information goes into an 837P?

At a high level, a professional claim tells the payer who provided the service, who received it, what was done, when, and how much is being billed. That usually means:

  • Billing and rendering provider identifiers
  • Subscriber/patient identifiers and payer information
  • Diagnosis information
  • Service lines: procedure codes, modifiers, dates of service, units and charges
  • Authorization or referral numbers, when the payer requires them

Your payer's companion guide defines the required fields and values. Use it, not a generic list, as the source of truth for your claims.

Where EVV fits

For Florida Medicaid home health, the visit data and the claim are connected.

  • Federal law requires EVV systems to verify six elements for each in-home visit: type of service, individual receiving the service, date, location, individual providing the service, and begin/end time.[3]
  • In Florida's fee-for-service program, AHCA lets providers use the State's contracted EVV system, or an Agency-approved third-party system that is interoperable with the Agency's EVV claims system for billing purposes.[4]

In practice, the dates, services and units on your claim need to agree with the verified visits behind them. If the visit record and the claim disagree, expect problems. See How to Reduce EVV Claim Problems.

Claim validation before submission

Catching errors before submission is cheaper than fixing them afterward. A practical pre-submission check:

  1. Eligibility and authorization: Is the patient covered, and is the service authorized for these dates and units?
  2. Visit match: Does every billed line trace back to a completed, verified visit?
  3. Coding: Do procedure codes and modifiers match the payer's current requirements?
  4. Provider data: Do provider identifiers on the claim match what the payer has on file?
  5. Format: Does the file pass the payer's or clearinghouse's format edits?

Submission

Agencies typically submit 837P files to a payer directly or through a clearinghouse. Each route has its own enrollment and testing steps, so follow the payer's EDI enrollment instructions.

Rejections vs. denials

These are different, and the difference matters:

  • Rejection: the claim failed format or front-end edits and never entered adjudication. Fix it and resubmit.
  • Denial: the claim was adjudicated and not paid, in whole or in part. The reasons come back on the remittance advice.

Resubmission

For a rejection, correct the error and resubmit. For a denial, follow the payer's corrected-claim or appeal process. Many denials repeat for the same root cause, so fix the upstream visit, authorization or coding problem, not just the one claim.

Reconciliation

After adjudication, payers report payment, adjustments and denials on the X12 835 remittance advice, the HIPAA-adopted standard for claim payment/advice (45 CFR § 162.1602).[5] Reconciling your 835s against submitted 837Ps shows what was paid, what was adjusted and what needs follow-up. See 835 Remittance Advice Explained.

Where Bickle fits

Today, Bickle focuses on capturing clean visit information at the source, so the data that eventually reaches billing is complete.

Built for Florida home health

Explore Bickle's future revenue workflow

Request a walkthrough

Keep going

References

  1. 1.

    45 CFR § 162.1102 — Standards for health care claims or equivalent encounter information transaction. eCFR. https://www.ecfr.gov/current/title-45/section-162.1102 — accessed Oct 5, 2026.

  2. 2.
  3. 3.

    21st Century Cures Act, Pub. L. 114-255, §12006(a). https://www.congress.gov/114/plaws/publ255/PLAW-114publ255.htm

  4. 4.

    Florida Agency for Health Care Administration. Florida Medicaid Comprehensive Quality Strategy (2023 CQS, Final Draft April 2024), "Electronic Visit Verification – Home Health Services," pp. 21–22. https://ahca.myflorida.com/content/download/8651/file/2023%20CQS%20Final%20Draft%20April%202024.pdf

  5. 5.

    45 CFR § 162.1602 — Standards for health care electronic funds transfers (EFT) and remittance advice transaction. eCFR. https://www.ecfr.gov/current/title-45/section-162.1602 — accessed Oct 5, 2026.

General information for agency operators, not legal or billing advice. Payer requirements vary; follow each payer's current companion guide and provider manual.