Sorry, i never had to handle such triggers, but if i had to, i will produce an ACK - unless the sender doesn't need them. In specs, there is no ACK^R22 following de OUL^R22 definition but i can't say it's a mistake or not.

Le 12/06/2013 16:46, vijayaratha vijayasingam a écrit :
Hi Viot;
Sorry i sent different initial sample message ;Please check my later replies; Im getting following[1] ACK in MSH-9 filde fro my OUL^R22 message. Is that valid?
*ACK^R22^ACK|*
*
*
Thanks


On 12 June 2013 17:11, VIOT Yves <[email protected] <mailto:[email protected]>> wrote:

    Hi,
    This is valid
    Here is what you can find in the HL7 2.5 documentation, following
    the ADT^A01^ADT_A01 messages structure definition.
    ACK^A01^ACK
    To get rid of it just get the MSH-9-1 with the terser.

    Yves

    Le 12/06/2013 13:25, vijayaratha vijayasingam a écrit :
    Hi all;
    Anyone have clue..?:(
    I badly need this to sort out..
    thanks


    On 12 June 2013 15:31, vijayaratha vijayasingam
    <[email protected] <mailto:[email protected]>> wrote:

        Hi all;
        Im using Hapi 2.1 version release an dit works perfect. But i
        have an issue with an error response which i get from Hapi.
        My request is;
        MSH|^~\&|||||20130612143324.392+0530||ADT^A01^ADT_A01|2601|T|2.5

        And My response is;
        MSH|^~\&|||||20130612152510.448+0530||ACK^A01^ACK|1623|T|2.5
        MSA|AE|2601
        ERR|||207^Application internal error^HL70357^^^^^^OOPS|E


        In the above response , if you check the MSH-9 filed , it is;

        */ACK^A01^ACK
        /*

        Shouldn't that be "|ACK". because it is additionaly adding
        "*/AO1/*" message to that filed, which is not valid. And i
        suspect that , it picks from that from original request.

        Can anybody help me on this? Ho w can i avoid that invalid
        segment?
        Why Hapi additionally adds that filed in the MSH-9 filed?

        Thanks
        -ratha




    
------------------------------------------------------------------------------
    This SF.net email is sponsored by Windows:

    Build for Windows Store.

    http://p.sf.net/sfu/windows-dev2dev


    _______________________________________________
    Hl7api-devel mailing list
    [email protected]  
<mailto:[email protected]>
    https://lists.sourceforge.net/lists/listinfo/hl7api-devel


    
------------------------------------------------------------------------------
    This SF.net email is sponsored by Windows:

    Build for Windows Store.

    http://p.sf.net/sfu/windows-dev2dev
    _______________________________________________
    Hl7api-devel mailing list
    [email protected]
    <mailto:[email protected]>
    https://lists.sourceforge.net/lists/listinfo/hl7api-devel



<<attachment: yves_viot.vcf>>

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Hl7api-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Reply via email to