Batch ERA process automatically posting charges to fee sheet

system · August 29, 2013, 8:08pm

ryry wrote on Thursday, August 29, 2013:

1- What was the rationale for allowing the batch ERA process to post charges into an already-closed fee sheet via the arPostCharge() function here:

github.com

openemr/openemr/blob/master/library/sl_eob.inc.php#L283




// Determine the next insurance level to be billed.
$ferow = sqlQuery("SELECT date, last_level_billed " .
"FROM form_encounter WHERE " .
"pid = '$patient_id' AND encounter = '$encounter_id'");
$date_of_service = substr($ferow['date'], 0, 10);
$new_payer_type = 0 + $ferow['last_level_billed'];
if ($new_payer_type < 3 && !empty($ferow['last_level_billed']) || $new_payer_type == 0) {
    ++$new_payer_type;
}


$new_payer_id = arGetPayerID($patient_id, $date_of_service, $new_payer_type);


if ($new_payer_id) {
    // Queue up the claim.
    if (!$debug) {
        updateClaim(true, $patient_id, $encounter_id, $new_payer_id, $new_payer_type, $status, 5, '', 'hcfa', '', $crossover);
    }
} else {
  // Just reopen the claim.
    if (!$debug) {

How would an ERA coming back from a clearinghouse contain a charge that was not already on the claim that was sent to them to begin with?

2- I think there may still be a bug here with the addBilling() call inside of arPostCharge() on master, although I’m not sure–the version I tested was from before the 3d4d206e commit. If the codes in the ERA were actually HCPCS codes, it was inserting CPT4 codes (saying “Added by ins1”) and applying payments to them rather than the original HCPCS codes.