Patient Responsibility

AngelTrack calculates the patient responsibility [PR] amount separately from the gross balance; however, the calculation is at times ambiguous and so you must understand how it works and how it can fail.

PR Amounts Change the Balance Due

When the Payor is set to "Patient," PR amounts can change the balance due, if a secondary carrier has disallowed any additional amounts or has forbidden patient copays. These additional disallowances are sometimes called "Not Allowed Amounts," or NAA.

To learn more, read how AngelTrack calculates the balance due.

Ambiguous PR Amounts in EOBs

AngelTrack calculates the PR by analyzing the EOBs returned by the carriers. However, this calculation is not always certain.

The main difficulty of PR calculation arises in an ambiguity in how insurance carriers issue their EOBs, be they electronic or on paper, as illustrated by these examples:

In other words, EOBs have an inherent and crucial ambiguity: When they say the PR is zero, it could actually be either zero or the entire balance. When a carrier denies or reverses, and says the PR is zero, they are assuming that no "Promise to Pay" signature is on file... even though such assumption is practically always wrong.

AngelTrack must struggle to decide how to interpret a PR of zero, deciding whether it means "zero due" versus "entire balance."

Ambiguities Resulting From Errors in Payment Event Records

AngelTrack separately calculates the PR set by each of the carriers in play -- primary, secondary, and other -- by analyzing the approval/denial payment events on file from them. The results of these calculations are shown on the "Billing" tab of Dispatch Edit, next to the balance due. The calculation works like this:

  1. Find the payment event representing the most recent claim against, or denial/reversal from, the carrier.
  2. Iterate all approval and reversal payment events on file after that event, and add up all associated PR adjustments (CAS03, not CLP05). CLP05 is ignored because it is often incorrectly set to zero when negative PR adjustments are present.
  3. Any approval or reversal payment event is ignored if it contains CO*18 or OA*18 codes indicating that it is dupe-claim advice.
  4. Any approval or reversal payment event is assumed to have PR of zero if it contains the MA125 remark code, indicating a statutory prohibition of patient copays.

The calculations depend on the accuracy of the payment event records, and so the numbers will be wrong if payment events are misfiled as primary/secondary/other. This can occur when secondary carriers erroneously claim (in CLP02) to be the primary adjudicator, and billers do not always notice and correct this during EDI import. When that secondary carrier specifies a PR but the associated payment is misfiled as being from the primary, then AngelTrack will incorrectly add it to the primary's accumulated PR as though it is a reconsideration.

Automatic Defenses Against PR Errors

To defend against the possibility of overbilling a patient due to an incorrect PR, AngelTrack does the following:

If all PRs on file are thereby ignored, then the patient will be invoiced only for the normal balance. In most cases, the normal balance is the same as whatever PR the carriers intended to set, and so nobody will be under- or over-billed.

PR higher than balance

There are at least three situations where the PR can ask for the patient to be billed for more money than is actually due per the allowed price that the primary carrier adjudicated:

In these cases, AngelTrack will invoice the patient for whichever is lesser of the PR or the balance. If due to a PR error, this can result in a patient being asked to pay less than what the carrier(s) assert is their responsibility, which is a problem.

PR lower than balance

There are at least four situations where the PR can ask for the patient to be billed for less money than is actually due per the allowed price that the primary carrier adjudicated:

Because AngelTrack will invoice the patient for whichever is lesser of the PR or the balance, these situations can cause the patient to be underbilled, but never overbilled.

Manual Correction of PR Errors

If you see a PR that is unexpectedly low, high, or missing, do the following:

  1. Review the payment event records to see if any are misfiled as primary, secondary, or tertiary. The "Pmt Events" tab under Dispatch Edit lists them all, along with their PR determinations if any. Remember that a null (missing) PR determination is not the same as a zero PR determination.
  2. If a carrier's PR is still too high, see if it has been set twice after the latest claim event against that carrier, and if so, add the missing re-claim event between the two approvals, or zero out the PR in the later payment event record(s).
  3. Make sure any full-reversals are filed as denials, so as to clear the zero PR created by the reversal, and thereby revert the PR to be "[Not set]" i.e. the full balance.
  4. If any payment events were hand-typed from paper EOBs, double-check the tables of adjustments to see if any PR/COINS rows contain typographical errors or were accidentally omitted.

*The Problem With OA*100 Payments From Carrier to Patient

When an insurance carrier writes a check directly to the patient, with the intention that EMS is to then bill the patient for it, they are supposed to report the check amount as PR*100 adjustments. That way, AngelTrack knows to add the carrier's check amount to the patient's invoice.

The problem is that carriers will sometimes report the check as an "Other Adjustment" aka OA*100, rather than PR*100. AngelTrack cannot automatically add these OA*100 amounts to the patient's invoice because we have observed cases where carriers erroneously report an OA*100 amount which they did not actually pay to the patient.

If you believe that an OA*100 amount is true and correct, and wish to invoice the patient for it, then you must manually add the amount to the "Patient responsibility" value set in the respective payment event.

Help Index - AngelTrack EMS Billing Software