837 construction code and serviceLine

Day-to-Day Users
1

srinile wrote on Monday, April 13, 2009:

Hi,

         i gone through the 837EDI generation ‘php’ code,  in that

many  of the things are hard coded and once i compared with the

837   professional EDI document, i saw there are many values in

document for each segment  other than hardcoded value  which

are not at all  using any where in that  837 EDI generation php

code,  and when i  go to Service Level many of the segments   are

skipped. So could any one tell me which all  segments are

necessary(minimal  no of segments ) to make a successful EDI

message. and How openEMR handling 835 remittence Advice

Regards
srinil

2

srinile wrote on Sunday, April 19, 2009:

any idea on this topic  please replay

3

ideaman911 wrote on Thursday, April 23, 2009:

Kumar;

OpenEMR now codes to produce the X12 standard, which has been in force as the replacement for 837P since the introduction of the NPI.  ALL the fields are being required by some payers, while others are using only some of those.  But they still work with the rest of the data.

There have been some specifics which have had problems, but those have been addressed in the forums to fix on a "per payer" basis within the php coding.

As of right now the remittance handling is manually entered using the EOB in the Billing section.  Hope that helps.  Please let us know what version you are using and the OS platform you use as well in future to help us help you.  Thanks.

Joe Holzer    Idea Man
http://www.holzerent.com