# 837 construction code and serviceLine

**URL:** <https://community.open-emr.org/t/837-construction-code-and-serviceline/3353>\
**Category:** Day-to-Day Users\
**Created:** [April 13, 2009, 1:15pm UTC](https://community.open-emr.org/t/837-construction-code-and-serviceline/3353 "2009-04-13T13:15:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [April 13, 2009, 1:15pm UTC](https://community.open-emr.org/t/837-construction-code-and-serviceline/3353/1 "2009-04-13T13:15:52Z")

</div>

**[srinile](https://sourceforge.net/u/srinile/)** wrote on [Monday, April 13, 2009](https://sourceforge.net/p/openemr/discussion/202504/thread/599345b3/#2004):

Hi,

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

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

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

document for each segment&nbsp; other than hardcoded value&nbsp; which

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

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

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

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

message. and How openEMR handling 835 remittence Advice

Regards  
srinil

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [April 19, 2009, 1:09pm UTC](https://community.open-emr.org/t/837-construction-code-and-serviceline/3353/2 "2009-04-19T13:09:59Z")

</div>

**[srinile](https://sourceforge.net/u/srinile/)** wrote on [Sunday, April 19, 2009](https://sourceforge.net/p/openemr/discussion/202504/thread/599345b3/#2004/4605):

any idea on this topic&nbsp; please replay

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [April 23, 2009, 10:02pm UTC](https://community.open-emr.org/t/837-construction-code-and-serviceline/3353/3 "2009-04-23T22:02:57Z")

</div>

**[ideaman911](https://sourceforge.net/u/ideaman911/)** wrote on [Thursday, April 23, 2009](https://sourceforge.net/p/openemr/discussion/202504/thread/599345b3/#2004/89ad):

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.&nbsp; ALL the fields are being required by some payers, while others are using only some of those.&nbsp; 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.&nbsp; Hope that helps.&nbsp; Please let us know what version you are using and the OS platform you use as well in future to help us help you.&nbsp; Thanks.

Joe Holzer&nbsp;&nbsp;&nbsp; Idea Man  
[http://www.holzerent.com](http://www.holzerent.com)