X12 and officeally

Management and Administration
1

voipbound wrote on Tuesday, November 22, 2011:

i recently upgraded from 4.0 to 4.1.0.  I imported the gen_x12.php assuming that it would work.  it didn’t.  Instead, I got some invalid ISA segment.  Does anyone know what’s going on?  I didn’t think the jump would be so drastic.  i haven’t even tackle the immunization issue nor the backup. I have to manually dump everyday now.

2

bo2999 wrote on Tuesday, November 22, 2011:

For Office Ally, I would rather use HCFA text batch file for uploading. It works just fine.

-bo

3

gutiersa wrote on Tuesday, November 22, 2011:

Hi

I also use officeally.

with every upgrade to openemr I have to modify my …openemr\library\gen_x12_837.inc.php.
The generated “yyyy-mm-dd-batch.txt” file should be standard, however the original code does not generate the correct file for upload to officeally for my region.

The generated “yyyy-mm-dd-batch.txt” file’s ISA segment with the original …openemr\library\gen_x12_837.inc.php looks like this:

ISA*00*          *00*          **12             **12             *1234567890*2205*U*12345*12345678***:~

the ISA segment officeally needs is:

ISA*00*          *00*          *ZZ*12             *ZZ*12             *123456*1234*U*12345*123456789*0*P*:~

(note the ZZ locations, and “*0*P*” at the end. This isa segment gets uploaded to officeally with no errors)

These are the changes I made to my file above:

line 29:

    “*ZZ” .
//    “*” . $claim->x12gsisa05() .

line 30 or 31:

    “*ZZ” .
//    “*” . $claim->x12gsisa07() .

on or about line 37 to 39:

//    “*” . $claim->x12gsisa14() .
//    “*” . $claim->x12gsisa15() .
“*0” .
“*P” .

Hope this helps

Of course there may be a way to do this in the openemr admin configuration settings that I am missing.

sandra

4

gutiersa wrote on Tuesday, November 22, 2011:

maybe easier to understand:

line 29:

    Replaced    “*” . $claim->x12gsisa05() .  with  “*ZZ” .

line 30 or 31:

   Replaced    “*” . $claim->x12gsisa07() .  with   “*ZZ” .

on or about line 37 to 39:

Replaced:

    “*” . $claim->x12gsisa14() .
    “*” . $claim->x12gsisa15() .

with:

“*0” .
“*P” .

5

sunsetsystems wrote on Tuesday, November 22, 2011:

Hey gutiersa, those are all settings in the X12 Partners form.  Administration -> Practice -> X12 Partners.

Rod
www.sunsetsystems.com

6

yehster wrote on Tuesday, November 22, 2011:

Sandra,
It looks like you never defined an X12 Partner for your billing.
Those values can be configured under Administration/Practice/X12 Partners.

Also, the Claims.class.php file would probably be a better place for coding defaults rather than the gen_x12 file.

For example, change the function

  function x12gsisa05() {
    return $this->x12_partner['x12_isa05'];
  }

to something like.

  function x12gsisa05() {
   if(isset($this->x12_partner['x12_isa05']))
  {
return $this->x12_partner['x12_isa05'];
  }
else
    return "ZZ";
  }
7

gutiersa wrote on Tuesday, November 22, 2011:

Thanks

Actually I did have x12 partner defined in 3.2.0 version. And I still had to make those changes.
However I had not notice the new x12 partners definitions. Look like I dont have some of that information.
Also when I try to change to production and save, it still returns testing.

I will get the numbers I am missing:

Application Sender Code (GS02) 
Submitter EDI Access Number (PER06)

Actually I am not sure what those mean.

I will do above instead.

thanks so much

Sandra

8

gutiersa wrote on Tuesday, November 22, 2011:

also I cannot change acknowledgement requested to Yes

9

cverk wrote on Tuesday, November 22, 2011:

I send X12 under windows routinely with OfficeAlly without any problems.  You do have to send their tech folks a test file for them to set up your account correctly. Maybe its really on their end. There is sometimes a glitch under secondary claims if you have multiple codes on the claim though.

10

gutiersa wrote on Wednesday, November 23, 2011:

Thanks all.

voipbound, incidentally, check out this link:

http://www.officeally.com/files/Office%20Ally%20Forms%20and%20Manuals/Service%20Center%20Manuals_Instructions/File%20Submission%20Guidelines.pdf

11

voipbound wrote on Friday, December 09, 2011:

sorry, I had given up on figuring out  what was the difference.  Everything was working fine until I upgraded from 4.0 to 4.1.  Today, I revisited the issue and saw your posts…  My x12 looks pretty like your Guttiersa.  Except on further inspection, after I had placed my TIN and OfficeAlly into the X12 partners, there’s a trailing space after the ID’s.  6 empty spaces to be exact.  I went back to see if there were trailing spaces in the X12 partners and there wasn’t.  So now I manually took away the spaces and uploaded it.  Let’s see if that was the reason.  Those spaces could throw the whole thing off…

12

voipbound wrote on Thursday, December 15, 2011:

This is so funny.  When I send the file as a “Test”.  It passed fine and is accepted.  But when I move it to production, Office Ally is telling me that it is missing a Tilda “~”.  But, there is a ~ termination throughout the x12…