fsgl wrote on Monday, April 07, 2014:
Our local Blue Shield carrier just announced that taxonomy codes are required for all claims effective June 15, 2014.
See first attachment for paper claims. What code changes are needed in the gen_hcfa_1500_02_12.inc.php file?
A greater priority is to get the 837P in shape for the deadline. See second attachment. What needs to be added to the gen_x12_837.inc.php file?
yehster wrote on Monday, April 07, 2014:
Here’s the spot in the code where the changes would like go.
yehster wrote on Monday, April 07, 2014:
You should be able to add
$out .= “PRVBIPXC*your taxonomy code~”;
at that spot in gen x12.
More work would be needed to have a proper user interface/mechanism to choose an appropriate taxonomy. However, hard coding the change will keep you going in a pinch.
yehster wrote on Monday, April 07, 2014:
source forge seems to be formatting my asterisks instead of leaving them as literals…
yehster wrote on Monday, April 07, 2014:
Looks like a very large list. Seems like the interface should just use freetext rather than trying to maintain the options in openemr.
fsgl wrote on Tuesday, April 08, 2014:
Thank you for the quick response.
If other Blues make the same demand, it would be good to have a mechanism to grab the code from the Edit User dialog box.
fsgl wrote on Wednesday, April 16, 2014:
Sent a file off to Office Ally yesterday, which was rejected.
I didn’t know how to italicize BI in the php file which caused the rejection. Was advised by the nice young person to insert an asterisk before and after BI as separators.
She also advised that the taxonomy code can be submitted for all carriers and that it is not necessary to send non-Blue Shield claims without the taxonomy code and the Blue Shield claims with the code. This makes for far less work.
fsgl wrote on Friday, April 17, 2015:
The Transaction Set Trailer at the end of each claim tallies the total number of segments for that claim. It’s the number after SE.
Office Ally is not particularly fussy if the actual count does not equal the SE number, but our local Blue Shield is rather fastidious.
Error message on 999 Acknowledgment:
4 - Number of Included Segments Does Not Match Actual Count
Be certain to add the following before the taxonomy snippet:
++$edicount;
fsgl wrote on Sunday, November 01, 2015:
The above posts concern insertion of the Taxonomy code for the solo practitioner in the 2000A loop.
Note, however, that for members of a group practice, no insertion is required. The 2310B loop even comes with its own segment counter. Follow the instructions of the carrier if the other PRV segments need tweaking. See attachment 1.
If the group submits paper claims, snippets must be added to gen_hcfa_1500.inc.php as explained here.
fsgl wrote on Sunday, November 01, 2015:
If all members of a group practice are of the same specialty, the static text for the Taxonomy code can be used on paper claims.
For multi-discipline practices, the Taxonomy codes must be pulled from the users table.
Something like the following will go into Line 516:
put hcfa($lino, 68, 12, $claim->providerTaxonomy());
aethelwulffe wrote on Wednesday, December 02, 2015:
And what about the issue for users with multiple taxonomy codes (and state license numbers)? Hmmm? Previously, the admin users separated them with semicolons. Not working anymore. The field validation requires a specific length…