This project has moved and is read-only. For the latest updates, please go here.


Aug 17, 2016 at 10:02 PM
Hi all.. this is great.. using the example for OopFactory.X12.Hipaa.ClaimParser is super simple. Now hopefully not to hard to get the updated 1500. Any direction would be awesome and greatly appreciated.

I also have a few data elements that I see on my samples on the new form that are not on the current 1500 so I may also need some direction on how I can place other elements on the form.

Again really appreciate any help with this..

Much thanks in advance.
Aug 18, 2016 at 4:09 AM
Got it.. I found the branch

Need to add some fields to the form, the data is in the xml but not on the pdf.

Direction on this would be awesome... Ill keep hunting in the meantime..

Aug 18, 2016 at 3:51 PM
  1. REF*D9 I need to print on the pdf in Box 19 on the 1500 as "ICN: 000000000000000"
I have a few other missing items from my sample pdf to the pdf generated with OopFactory but if someone could get me started with the above I could probably figure it out.

Thanks much...
Aug 18, 2016 at 3:55 PM
Id also like to name the PDF generated as the REF*D9
Aug 25, 2016 at 12:23 PM
All transaction sets are embedded in the source code. To see details of the 837 look at the xml spec for it here:

This will tell you what is in the 2010 loops. There are actually multiple depending on what the NM1's entity ID code is.

To be able to split your claims until multiple PDFs, I suggest you unbundle the file first into claims using the 2300 loop. See the OopFactory.X12.UnbundleX12 console app code to see how to do this. You don't have necessary have to write out the claims into individual files, but code will show you how to unbundle. Then you can take that serialize the individual interchanges back to X12. Once you the individual claim as an isolated X12, you can send that to your transform and it will spit out however many pages you need to represent that claim.
Aug 25, 2016 at 1:23 PM
thanks much, Good direction to start..