fsgl wrote on Wednesday, September 30, 2015:
We were just notified by our local Blue Shield carrier that our last batch of e-claims had our Tax Payor ID instead of our Submitter ID.
After patching 4.2.0 to 4 it appears that the snippet that we had inserted for the Submitter ID on Lines 102 to 103 had been deleted unbeknownst to us.
If you submit directly to Blue Shield & are required to have your Submitter ID in Loop 1000A, segment NM109, check your 837 files to avoid rejection.
aethelwulffe wrote on Saturday, October 03, 2015:
Yeah, I posted that one quite a while back. I would like to see it in the code base like the one for eclaims EDI.
It really is best to use a diffing utility (if you have ever changed any of your code) before applying patches. I usually use Winmerge myself. If you are not running against a GIT repo for your production code, diff you patch against your code with your sites directory unincluded. It is also smart to clear your calendar SMARTY cache before doing so. Not only will these show as differences that you don’t care about, but the file names that smarty creates for those templates cause serious issues/crashes when comparing the directories (at least with winmerge).
fsgl wrote on Saturday, October 03, 2015:
Life was a lot easier when our local Blue Shield paid Office Ally for their services.
Did not have to worry about ETIN’s, Transaction Set Trailers, decoding the nearly indecipherable 277/999’s or surly behavior from the local electronic claims department.
Thanks for the tips & thank goodness I’m old.
fsgl wrote on Tuesday, October 06, 2015:
Patch 4 also wiped out the Situational PRV segments for Taxonomy code & the snippet to increase the segment count. Both must be re-inserted after patching to 4.
bradymiller wrote on Wednesday, October 07, 2015:
Hi fsgl,
To clarify, are these bugs (is the patch reverting standard code that should not be reverted) or is this customized code that is getting reverted?
-brady
OpenEMR
fsgl wrote on Thursday, October 08, 2015:
The latter.
Submitter ID & Taxonomy code needed only for our local Blue Shield claims. Patch 4 not a problem for our Office Ally submissions.
Florida Blue Shield claims submitted via Availity will have the deletion of Submitter ID, after patching to 4.
Our third BS submission was finally accepted with the 2 re-insertions after we deciphered the rejection messages.
Most practices don’t know how to use Winmerge; therefore it would be helpful to have an advisory for each patch release about customized codes, just like version releases.
aethelwulffe wrote on Thursday, October 08, 2015:
Holy crud! My taxonomy changes didn’t make it through my merging process like three upgrades ago! Must have been a hurried patch! I better check everything all over.
bradymiller wrote on Saturday, October 10, 2015:
Hi,
On the patch page, there is a bolded text warning the user of this along with link to the changed files:
http://www.open-emr.org/wiki/index.php/OpenEMR_Patches#Description
-brady
fsgl wrote on Saturday, October 10, 2015:
Must not have seen the advisory before patching.
Did see the list of changed files after patching.