Update X12 to match spec for transaction set wrapper, 1 ST/SE pair

OpenEMR Development
1

bradymiller wrote on Sunday, April 26, 2015:

Hi,

Need some developers with billing expertise to review Tony’s code here:

thanks,
-brady
OpenEMR

2

aethelwulffe wrote on Wednesday, April 29, 2015:

I have an issue with appended claims being hard-code set as “CPT4”. I also would prefer that allowing the insurance company to effectively write billing line items to our tables be a moderated feature. It really bags stuff up sometimes.

3

bradymiller wrote on Thursday, April 30, 2015:

Hi Art,

Is this a specific issue with Tony’s commit or a more general issue?

-brady
OpenEMR

4

tmccormi wrote on Thursday, April 30, 2015:

It’s not related to my commit. but I did find a small bug in testing that I will be pushing out tomorrow.

5

tmccormi wrote on Friday, May 08, 2015:

This turns out to be a big problem to fix. The process is designed around creating a complete batch for each encounter to be billed and the packing them together by stripping the header and reassembling it into one big batch.

Leaving the ST/SE wrappers around each claim (not to spec) allows for a set of repeating headers BHT/PER/NM1*40/NM1*41 and allows the HL* subscriber counters to be reset to 1 between claims.

That all fails if you try and put all claims into one ST/SE pair (as specified).

So … working on a plan to redesign the driver in billing_process.php to assume batches of multiple claims and handle the header wrappers outside of gen_x12 or some similar approach.

Any thoughts would be good. The gen_x12_837 is one huge 1300 line function. Simple enough if all you are doing is dropping thru the code, but that’s not the case now.