ajperezcrespo wrote on Thursday, December 01, 2011:
Hi,
Although 5010 was given a 90 day breather…any Idea when it will be released as part of OpenEMR? It just makes providers happier knowing it’s there.
Thanks
sunsetsystems wrote on Thursday, December 01, 2011:
The important part (claims) is already in the master branch. I’ve got a client using it now, and another one starting next week. Just waiting for more testing feedback … I think Tony is doing some testing also.
After that, could either do a release or back-port it to 4.1.
I’ve not heard anything new about 5010 ERA’s. That’s bound to generate some interest soon, and hopefully won’t be a big deal. 
bradymiller wrote on Thursday, December 01, 2011:
Hi,
When this is considered stable, can always just include it in the next 4.1 patch.
-brady
weesnerkim wrote on Thursday, December 01, 2011:
I just completed changes for 5010 and have passed testing with several clearing houses and medicare.
weesnerkim wrote on Thursday, December 01, 2011:
I would like to get current with development on the 5010 issue. I had talked to ROD several months ago about 5010 but had bad medical problem. All better now and ready to go. There was some issues in implementing 5010 that I would like to discuss.
sunsetsystems wrote on Thursday, December 01, 2011:
Hi weesnerkim - you can go to https://github.com/openemr/openemr/commits/master and look at the 3 commits for November 18. Those are the ones containing my 5010 updates. Any questions or things you want to add, please let me know! My email is rod at sunsetsystems dot com.
tmccormi wrote on Thursday, January 05, 2012:
We ran across a 5010 issue that the current code does not seem to handle. Does anyone else have this issue?
When the service location matches the billing location you should NOT have both listed. This is according to rejects we are getting from Availity. Related to NM1*77
-Tony
tmccormi wrote on Thursday, January 05, 2012:
This is an issue as well. essentially - Onset date cannot be the same as date of service, so ONSET date must be blank
Error Initiator: CONV_HIPAA Message Type: R
Error Code: 0x393941d
Error Message: Date - Onset of Current Illness or Symptom should not be used. Invalid data: 20111229
Version: 5010A1
sunsetsystems wrote on Friday, January 06, 2012:
There is logic already to skip service location (loop 2310D) if facility NPI is the same as billing facility NPI. So maybe you just need to plug a missing NPI into one of those.
tmccormi wrote on Friday, January 06, 2012:
That is excellent! I love Open Source!
-Tony