nursejeff wrote on Monday, December 26, 2011:
Since upgrading from 4.1.0 (2) to 4.1.0 (5) my biller cannot print claims. When she selects a claim and clicks on “Generate CMS 1500 PDF” the screen turns white and the following error presents: “Data item at (43, 1) precedes current column.”
Please help.
Jeff Guillory Jr.
NP Health Clinic
bradymiller wrote on Tuesday, January 03, 2012:
Hi,
Can anybody else confirm this bug? The 5th patch has some changes for 5010, so possibly could of brought in some bug(s).
-brady
yehster wrote on Wednesday, January 04, 2012:
The 5010 changes have been to only the gen 837 file, they haven’t made changes to the common claim class for 5010 at all, also CMS 1500 with the most recent codebase works for me. Don’t know what is causing Jeff’s issue and a lot more information would be needed to figure it out.
tmccormi wrote on Wednesday, January 18, 2012:
We are getting this issue on one specific claim at one customer. Nothing obvious wrong with the data that we can find, so far. on Patch 5.
-Tony
tmccormi wrote on Tuesday, January 24, 2012:
We are still having this issue at that one customer (windows xampp install). we can not replicate it on any of our other installations. It is very specific to claims that have HCPCS + NDC codes only. It’s not really possible for us to use the customers systems to debug it and it’s only happens there, so we are kind of at a loss. Any ideas?
-Tony
jojohit wrote on Tuesday, January 24, 2012:
>not really possible for us to use the customers systems
I’d recommend to “can” (isolate/package) the EMR system using a VM if the testing does not require external (thrid party) connectivity. Setup a similar LAMP environment in a VM then restore the system onto it.
JP
sunsetsystems wrote on Tuesday, January 24, 2012:
Are we still talking about the “Data item at (43, 1) precedes current column.” error? This indicates that it’s trying to print a data item that overlaps the previous data item, and suggests a logic error. Has someone been customizing gen_hcfa_1500.inc.php?
sunsetsystems wrote on Tuesday, January 24, 2012:
Y’know what - I think this comes from the commit for procedure-specific claim notes. Find this code at or near line 438 in gen_hcfa_1500.inc.php:
//Note Codes.
put_hcfa($lino, 25, 7, $claim->cptNotecodes($hcfa_proc_index));
and move it down about 20 lines so it’s just above this comment:
// 24i and 24j Top. ID Qualifier and Rendering Provider ID
Let me know if that fixes it.
yehster wrote on Tuesday, January 24, 2012:
Rod,
I am certain you found it!
Column 1 stuff was trying to be printed after column 25 (the procedure specific note when it existed)
(This code came after the lines Rod is saying to move).
put_hcfa($lino, 1, 50, "N4$ndc " . $claim->cptNDCUOM($hcfa_proc_index) .
$claim->cptNDCQuantity($hcfa_proc_index));
https://github.com/yehster/openemr/commit/cadedd5b269616f867ebf8635d60d282a042ea19
https://github.com/yehster/openemr/tree/hcfa_ndc_fix
Here’s a branch with Rod’s suggested changes.
tmccormi wrote on Tuesday, January 24, 2012:
That is awesome… We’ll drop this fix in tomorrow on site and see how she goes!
Thanks
Tony
tmccormi wrote on Thursday, January 26, 2012:
So far it has not broken since we put it in. Not definitive since it did not break every time… but good.
-Tony
yehster wrote on Thursday, January 26, 2012:
The key question is did they successfully generate any claims with Drug Information/NDC codes, as that’s the specific scenario this code fixes. Any reports on whether they tried to generate HCFA forms for encounters that previously were breaking?
tmccormi wrote on Thursday, January 26, 2012:
Yes, but they were able to do that before sometimes, it didn’t always break, but it when it did it was NDC related.
-Tony
tmccormi wrote on Thursday, January 26, 2012:
This patch is working fine, I believe it’s good to go. Merge it in. 
Thanks All
-Tony
yehster wrote on Thursday, January 26, 2012:
Pushed to sourceforge.
Good job team!
Brady, this fix should definitely find it’s way into the next patch.
-Kevin Yeh
kevin.y@integralemr.com
bradymiller wrote on Thursday, January 26, 2012:
Will put it in the next patch.
thanks,
-brady
