none
BizTalk 2009 EDI HIPAA 277 Output Error RRS feed

  • Question

  • I am having a problem when writing out the actual 277 EDI message.  The problem I am having is that the XML 277 that is sent through the pipeline is in the correct format and validates against the schema.  However, after passing through the pipeline, the EDI message has the last segment in the wrong place, at the end of the message.

    I imagine there is something i left out in the party configuration or possibly something i need to change int he default schema.  I have batching setup so when i write these edi messages to an output directory and it picks them back up, it bombs out with parsing errors.  I have included the XML for the original 277 sent to the pipeline and also what is parsed on the batch receive.

    Any help is appreciated.

     

    This is the example of the end of the XML file that is passed in.

     

    - <ns0:STC11_C043U87_TS277A1_2200D>

      <STC11_C04301U88_HealthCareClaimStatusCategoryCode>A2</STC11_C04301U88_HealthCareClaimStatusCategoryCode> 

      <STC11_C04302U89_HealthCareClaimStatusCode>20</STC11_C04302U89_HealthCareClaimStatusCode> 

      </ns0:STC11_C043U87_TS277A1_2200D>

      </ns0:STC_ClaimLevelStatusInformation_TS277A1_2200D>

    - <ns0:REF_TS277A1_2200D_SubLoop>

    - <ns0:REF_PayerClaimIdentificationNumber_TS277A1_2200D>

      <REF01__ReferenceIdentificationQualifier>D9</REF01__ReferenceIdentificationQualifier> 

      <REF02__PayerClaimControlNumber>32132132132321</REF02__PayerClaimControlNumber> 

      </ns0:REF_PayerClaimIdentificationNumber_TS277A1_2200D>

      </ns0:REF_TS277A1_2200D_SubLoop>

      </ns0:TS277A1_2200D_Loop>

      </ns0:TS277A1_2000D_Loop>

      </ns0:TS277A1_2000C_Loop>

      </ns0:TS277A1_2000B_Loop>

      </ns0:TS277A1_2000A_Loop>

      </ns0:X12_00401_277>

     

     

    This is the example of the end of the XML file that is parsed from the EDI message that is outputted from the pipeline.

     

    - <ns0:STC11_C043U87_TS277A1_2200D>

      <STC11_C04301U88_HealthCareClaimStatusCategoryCode>A2</STC11_C04301U88_HealthCareClaimStatusCategoryCode> 

      <STC11_C04302U89_HealthCareClaimStatusCode>20</STC11_C04302U89_HealthCareClaimStatusCode> 

      </ns0:STC11_C043U87_TS277A1_2200D>

      </ns0:STC_ClaimLevelStatusInformation_TS277A1_2200D>

      </ns0:TS277A1_2200D_Loop>

      </ns0:TS277A1_2000D_Loop>

      </ns0:TS277A1_2000C_Loop>

      </ns0:TS277A1_2000B_Loop>

      </ns0:TS277A1_2000A_Loop>

    - <ns0:REF_PayerClaimIdentificationNumber_TS277A1_2200D>

      <REF01__ReferenceIdentificationQualifier>D9</REF01__ReferenceIdentificationQualifier> 

      <REF02__PayerClaimControlNumber>32132132132321</REF02__PayerClaimControlNumber> 

      </ns0:REF_PayerClaimIdentificationNumber_TS277A1_2200D>

    - <SE>

      <SE01>14</SE01> 

      <SE02>3019</SE02> 

      </SE>

      </ns0:X12_00401_277>

     

    Notice how the REF is now at the end of the message.

     

    • Edited by shawncutter Saturday, August 7, 2010 2:23 PM added note to end
    Saturday, August 7, 2010 2:12 PM

All replies

  • It looks like you have a looping functoid or a link to the REF segment. Take the link out to the segment and you should get it to work.
    Please Indicate "Mark as Answer" if this Post has Answered the Question
    Monday, August 9, 2010 1:04 PM
  • I double checked the map and there are no looping functoids being used.  This issue is actually happening after the xml from the map is created.  I have grabbed the XML before it goes to the EDI send pipeline and everything is in the right place.  But after the pipeline gets a hold of it, it is out of order.

    Any idea if this could be caused by something in the party or possibly the pipeline?

    Monday, August 9, 2010 5:33 PM
  • Hi:

    No, there is nothing in the BizTalk Party configuration or 277 Schema that would cause a REF segment to be displaced.  This kind of problem usually occurs in a map.

     

    1.       What version of the HIPAA 277 schema is being used in BizTalk Server 2009 -- 004010A1 or 005010?

    2.       Where does the mapping occur -- Receive Port, Orchestration, or Send Port?

    3.       Please do one of the following:

    Temporarily change the Send Port Pipeline from “EDI Send” to “Passthru” 

    OR 

    Create an additional “FILE” Send Port that uses the “Passthru” pipeline and that subscribes to the 277 message. 

     

    Next, resubmit the 277 message to BizTalk.  Does the REF segment still appear as displaced / disordered after having been delivered through a “Passthru” pipeline ?

     

    Thanks

    Wendell

    Friday, August 13, 2010 8:27 PM
  • Wendell,

     

    Thanks for your help.  If I write out the messages as XML it looks good, all nodes and elements are in the correct spot.  I do some some more info on this strange problem though from some of the other testing i have done.  I am beginning to think that the issue is actually caused by the disassemble component when the individual messages are being read back in for the batching side of things.  Meaning, i have the files being written out to a directory where they are being picked up by the batching orchestration for the batch i have configured for the party. 

    The sample message i posted in my original post, was pulled from the suspended message, which it says that the ref was in the wrong place.  I even attempted to overcome this issue with another pipeline component that simply fixes the xml.  But the problem is that the EDI disassemble component throws an exception whcih in turn suspends the message.  

     

    Any other ideas?  Should I write out the xml rather than the EDI for the batching component.  Is there another alternative to the method i am using to batch these up every 10 minutes?

     

    Thanks

    Sunday, August 15, 2010 2:32 PM
  • What happens if you take the output file and pass it through the map. Can you create a compliant file when you test it?
    Please Indicate "Mark as Answer" if this Post has Answered the Question
    Monday, August 16, 2010 3:09 PM
  • Hi:

    Sorry for the delay.

    Two questions for you:

    What version of the 277 schema is used in your BizTalk application?

    and

    If Batching is disabled and the mapped 277 Xml is passed directly to a Send Port, EDI Send pipeline (no custom pipeline),  does the validation error occur?

    Wendell

    Tuesday, August 24, 2010 8:21 PM