sunsetsystems wrote on Saturday, November 19, 2011:
Oh and note my last fix (on SF only), you’ll probably need that.
weesnerkim wrote on Thursday, December 01, 2011:
The line item control number in the 2400 loop pointed out by Rod would be very useful. I am back in action, how can I help.
sunsetsystems wrote on Thursday, December 01, 2011:
Hi weesnerkim, have you seen the new developer info in the wiki?
http://www.open-emr.org/wiki/index.php/Main_Page#Developer_Manuals
If not, start there. Learning git will be a useful step if you have not done that already.
As for 5010 stuff, suggest you look over my changes for any omissions/problems, and then look at the 835 stuff.
Thanks!
Rod
weesnerkim wrote on Friday, December 02, 2011:
Hi Rod
I got setup with Git yesterday and downloaded the current development version. I like what you did in gen_x12_837.inc.php to allow for 4010 837 and 5010 837p. All the changes that I had made were covered by yours. So I ran out some test billings and it’s looking good with just a couple of issues. In loop 2310B, NM1 82 (Rendering Provider) It generated this line, NM1*82*1*ADMINISTRATOR*****XX*~, which is an error because of the trailing empty field. I havn’t found where this is happening yet, claim->providerLastName($prockey) must have “ADMINISTRATOR” as the string with
claim->providerNPI($prockey) being NULL. This must be happening when the claim array is created.
I am going to focus my efforts toward getting the 835 section going as it looks like you have done a great job here. I will continue to run test billings to make sure it is solid. I am submitting test cases to PalmettoGBA Medicare, Railroad Medicare, Office Ally, and others. Looking good Rod, way to go.
I am seeing a change happening in my area concerning EMR system’s. I have 50+ local offices looking at OpenEMR along with a local HMO (87 offices and clinics, 187 doctors) recommending there members to talk with me about OpenEMR.
Point me to where I can help, I want to be the solution in this area.
Kim Weesner
weesnerkim@hotmail.com
frankrubinomd@sbcglobal.net
714-554-2322
sunsetsystems wrote on Friday, December 02, 2011:
Hi Kim,
I really appreciate your input and willingness to help!
Looks like what is missing on the NM1*82 line is the provider NPI. You probably don’t want the Administrator to be a provider in your system nor chosen as such in the Fee Sheet, and all those who *are* providers should have an NPI entered into their user form.
weesnerkim wrote on Tuesday, December 06, 2011:
Rod
I have some changes that I need to talk to you about. Do you want me to list them here, push them with Git, or something else?
Kim Weesner
sunsetsystems wrote on Tuesday, December 06, 2011:
Kim, whatever you think makes the most sense. If it’s discussion that others may want to participate in, post it here. if you have code that you think is ready for review, a branch on github would be good. If it’s something else not of general interest, email me. Thanks.
weesnerkim wrote on Wednesday, December 07, 2011:
Hi Rod
I have been submitting 5010 test billings directly to PalmettoGBA-J1 Medicare and have encountered a few issues. The problem I am having is understanding the 999 response file tags concerning error location. Do you have the spec for 999 response files, specifically for tags IK3, IK4, and CTX. I have most of the details figured out but some dark areas.
I get this repeat every claim:
IK3*NM1*22*2310*I9~
CTX*SITUATIONAL TRIGGER*NM1*10*2010*9~
CTX*CLM01:3310-8~
22 changes for the HL, 3310-8 changes for our id-encounter #
I think this envolves the NM1 82 tag, might be due to PRV*PE*PXC*207Q00000X tag.
Working on it, any info would be helpful
I will Git code changes on the issues I have solved, very minor and only a couple.
Kim Weesner
Email: frankrubinomd@sbcglobal.net
Phone: 714-554-2322
weesnerkim wrote on Wednesday, December 07, 2011:
Rod
I just got the report from Office Ally, good to go live on 1/1/2012. The clearing houses are not as strict as direct medicare.
Good news for all.
Kim Weesner
sunsetsystems wrote on Wednesday, December 07, 2011:
Hi Kim, no I don’t have any info about 999 transactions.
Good to hear Office Ally likes it. The real test is getting paid. 
weesnerkim wrote on Wednesday, December 07, 2011:
Rod
Isn’t that the truth. Ok guess I have to figure it out, I got it for the most part. Soon as I get the last issues I will Git changes.
Kim Weesner
sunsetsystems wrote on Wednesday, December 07, 2011:
Got another client starting testing now, this time with Zirmed. Looks good so far. For that I ported the 5010 work to a 3.2.0 branch as they are not ready for the 4.x UI yet.
weesnerkim wrote on Thursday, December 08, 2011:
Rod
I think Zirmed will be fine. I solved another one of my issues with PalmettoGBA, just one left. I will Git changes tomorrow, I would like to make them key from processing format in x12partner, ala CMS, but havn’t looked for it yet. Don’t worry they are very minor. The 4.x UI is such an improvment, the whole program feels and works better than 3.2.
Kim
weesnerkim wrote on Thursday, December 08, 2011:
All
Direct 5010 billing to Medicare now works. This envolves no clearing house but it sent directly to PalmettoGBA-J1 in South Carloina via dial-up connection. PalmettoGBA handles CMS for most of the United States.
Thanks go to Rod for his work on the 5010 code base with a little help from me and others for killing bugs.
We will be ready for 1/1/2012.
Kim Weesner
voipbound wrote on Friday, December 09, 2011:
That’s wonderful to hear. Can you instruct me on what I need to do to download it from GIT to also test it? Or should I just wait for the next patch?
bradymiller wrote on Friday, December 09, 2011:
Hi,
Is this ready for release into a 4.1 patch (planning to release a patch soon for a security fix and could include this also) or is more testing time needed?
-brady
sunsetsystems wrote on Friday, December 09, 2011:
I understand Kim has a couple of minor changes for the case where Medicare is the X12 partner. Let’s give him a day or two to get those submitted.
sunsetsystems wrote on Friday, December 09, 2011:
voipbound: You can go to www.open-emr.org, click the Download tab and scroll down to “Unstable Development Releases”.
weesnerkim wrote on Friday, December 09, 2011:
I will Git changes up this morning so we can roll on this.
Kim
weesnerkim wrote on Friday, December 09, 2011:
Well i sent them. Hope i did that right, I am new too Git.
Kim