none
allow empty fields in BTAHL72XReceivePipeline

    Question

  • Hi,

    I want to allow empty fields in an HL7 message passed through BTAHL72XReceivePipeline, in a same way how we allow trailing delimiters.

    Is there a way to do this, I have seen configuration and properties but didn't find anything.

    Early response is much appreciated.

    thanks

    noor syed

    Thursday, November 10, 2016 4:45 PM

Answers

  • The reason it fails to parse is that you are including ^ in the value and the parser tries to split it into sub component values but as I mentioned earlier, remove the ^ in the message and it will work fine (Because in xml the field where you are using ^ needs to be a record which is not in your case)

    Regards


    Mandar Dharmadhikari




    Monday, November 14, 2016 2:53 PM
    Moderator

All replies

  • Hi Noor,

    I want to allow empty fields in an HL7 message passed through BTAHL72XReceivePipeline, in a same way how we allow trailing delimiters.

    I believe that you do not require to do any setting to send empty data...you just need to ensure that in what ever field you are passing the data should have proper pipe set after it and that the schema for the particular HL7 (MSH or Body) should accept the empty data

    Regards


    Mandar Dharmadhikari

    Friday, November 11, 2016 3:26 AM
    Moderator
  • Hi Mandar,

    below is the message i have


    as you said empty pipes just work fine, but i have fields(highlighted in the above message) with empty carets give me error

    Segment Id: OBR
    Sequence Number: 1
    Field Number: 21
    Error Number: 102
    Error Description: Data type error
    Encoding System: HL79999
    i guess there is something we need to do to allow these empty carets in fields







    • Edited by noor syed Sunday, November 20, 2016 4:47 PM
    Friday, November 11, 2016 4:38 AM
  • Hi Noor,

    can you paste the actual HL7 message and I would requets you to paste the message with dummy data..Also I observer that you have used the ^ on the FillerField2 (if you check the OBR schema, youwill find that FillerFieeld2 is a single node not a record and hence the ^ will not work in that case) and I guess that is why you get the data Type Error. Remove the Seperator ^ and It will solve your problem.

    Regards,


    Mandar Dharmadhikari


    Friday, November 11, 2016 5:34 AM
    Moderator
  • Hi Noor,

    Any update on the issue?

    Regards


    Mandar Dharmadhikari

    Monday, November 14, 2016 9:49 AM
    Moderator
  • Hi Mandar,

    Message works fine if I remove those emtpy carets, but there is situation when these can  be empty, at that time the pipeline fails to parse it. I'm looking for  a way to allow these.

    Monday, November 14, 2016 1:12 PM
  • The reason it fails to parse is that you are including ^ in the value and the parser tries to split it into sub component values but as I mentioned earlier, remove the ^ in the message and it will work fine (Because in xml the field where you are using ^ needs to be a record which is not in your case)

    Regards


    Mandar Dharmadhikari




    Monday, November 14, 2016 2:53 PM
    Moderator
  • Hi Mandar,

    Sorry for delayed response, i was busy finishing other stuffs,

    you are right OBR 21 Filler Field 2 is just a string field not record value is allowed, but what's you say on OBX 15 Producer's ID ( i have highlighted it as well in the message)

    also for your convenience laying down hl7

    MSH|^~\&|XX|XXX,52||16|20161102080107||ORU^R01|895|P|2.3
    PID|1|CEU-000104|11666||Ahmed^Abrar^NA||19161007120000|M|||||||en-US
    ORC|RE|ON0966NA||16|CM||||20161102|||^^^^^
    OBR|1|ON0966NA|ON0966NA|^^^450^Blood Culture^|R|20161102135500|20161102135500|||||||20161102135500|||||||^^^^^^|20161102080106|||F|||||||
    OBX|1|TX|^^^4643^Isolated Organism(s) (Blood Culture)^||20|AI|15--25,--||||F|||20161102080107|^^^^^^|
    OBX|2|TX|^^^7252^Gram Stain(Blood Culture)^||10|µg/L|5--15,--||||F|||20161102080107|^^^^^^

    looking forward to you early response

    thanks


    • Edited by noor syed Sunday, November 20, 2016 4:45 PM confidentail
    Sunday, November 20, 2016 1:10 PM
  • Hi Noor,

    What error do you get for the OBX15??\

    Well if you check each of the field of the BOX15 records,

    Some of them have enumeration applied on them, meaning for OBX 15 NameOfCoding System has a predefi8ned value and it cannot accept empty string. Similarly for other fields. Please compare

    Regards,


    Mandar Dharmadhikari


    Monday, November 21, 2016 6:50 AM
    Moderator
  • Hi Mandar,

    thanks for your response,

    The error description is 'Data type error'. I was investigating the HL7 definition, found OBX 15 supports 6 subfields, i was passing 7 subfields which BizTalk isn't accepting.

    Is there any way to do away with such validation.

    Monday, November 21, 2016 8:23 AM
  • Hi Noor,

    The Structure for the xml is defined, you can use the min occurs and max occurs properties in the xml and then do not pass the fields if not required...

    Regards,


    Mandar Dharmadhikari

    Monday, November 21, 2016 9:07 AM
    Moderator