pdl encapsulation characters for HL7

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf pdl encapsulation characters for HL7

  • Creator
    Topic
  • #51821
    Bob Schmid
    Participant

    SIemens is indicating taht they want encap cahracters to be D..data..

    Iwould assume my resync character sholud be STX (X2) but an error occurs in testing :

    invalid command name “resync:x2”

    pdl is:

    define phrase basic-msg;

     ;

     field data = variable-array( not( ));

     ;

    end phrase;

    /**********************************************************************

    * End of declarative section, TCL management functions start here.   *

    **********************************************************************/

    #{#

    # This can be handled completely using the “basic” style.

    hci_pd_msg_style basic phrase:basic-msg

    field:data

    resync:\x2

    #}#

Viewing 9 reply threads
  • Author
    Replies
    • #71853
      Michael Hertel
      Participant

      resync:\xb (just like regular tcp_mlp.pdl)

    • #71854
      Bob Schmid
      Participant

      why xb ?

    • #71855
      Bob Schmid
      Participant

      hci_pd_msg_style basic phrase:basic-msg

                                   field:data

                                   resync:\xb

      ‘ failed: invalid command name “resync:xb”

    • #71856
      Michael Hertel
      Participant

      xb indicates hex b

      maybe it needs to be indented.

      Here’s where I got my info:

      Code:

      /* $Id: mlp_tcp.pdl,v 1.3 1998/02/21 00:05:27 neuts Exp $ */
      /*
      * Copyright (c) 1995-1996, Healthcare Communications, Inc. All Rights Reserved.
      *
      * tcpipmlp.pdl – TCP/IP Minimal Layer Protocol for HL7 transmision
      */

      define driver tcpip-mlp;
         version: “2.0”;
      end driver;

      /* This driver manages the transmission of messages using the HL7 defined
      * MLP protocol.  Each message is bounded by a start character
      * and a stop string .
      *
      * The phrase basic-msg recognizes this message format.  Once recognized,
      * the message data will be available from the ‘data’ field.
      */

      define phrase basic-msg;
         ;
         field data = variable-array( not( ) );
         ; ;
      end phrase;

      /**********************************************************************
      * End of declarative section, TCL management functions start here.   *
      **********************************************************************/

      #{#

      # This can be handled completely using the “basic” style.

      hci_pd_msg_style basic  phrase:basic-msg
                             field:data
                             resync:\xb

      #}#

    • #71857
      Bob Schmid
      Participant

      /* MLP protocol.  Each message is bounded by a start character

      * and a stop string .

      *

      * The phrase basic-msg recognizes this message format.  Once recognized,

      * the message data will be available from the ‘data’ field.

      */

      define phrase basic-msg;

       ;

       field data = variable-array( not( ) );

       ;

      end phrase;

      /**********************************************************************

      * End of declarative section, TCL management functions start here.   *

      **********************************************************************/

      #{#

      # This can be handled completely using the “basic” style.

      hci_pd_msg_style basic        phrase:basic-msg

                                   field:data

                                   resync:\xb

      #}#

    • #71858
      Michael Hertel
      Participant

      I’m wrong.

      I just checked the ascii table. You are looking for hex 2, not hex b.

      Sorry. Wish I could delete my posts.  ðŸ˜³

    • #71859
      Jim Kosloskey
      Participant

      Robert,

      This does not solve your issue but is Siemens saying what they propose is HL/7 MLP encapsulation?  If so they are incorrect – what they propose looks like an abomination of async and HL/7-HLLP.

      What YOU want is for them to conform to MLP.

      By the way, is this for Soarian?

      email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

    • #71860
      William Rowley
      Participant

      The error “invalid command name” makes this look like a whitespace/continuation problem. The interpreter is parsing out the “resync:” phrase as a command – not an argument to the hci_pd_msg_style command. Check to make sure that there is nothing except a carriage return after the “” on the line with “field:data”. I suggest deleting the lines with “field:” and “resync:” and retyping them. Or do away with the continuation completely and just have one line with all the arguments –

      hci_pd_msg_style basic phrase:basic-msg field:data resync:\x2

      That should eliminate the runtime error.

      Now as to what should be the resync character – I agree with Jim that the vendor should be using the “tried and true” MLP characters.

    • #71861
      Bob Schmid
      Participant

      White space it was…

      hci_pd_msg_style basic        phrase:basic-msg

                                  field:data ” ”   <


                                  resync:\xb

      Jim – “Abomination”

      – yep!…I already talked to their interface guys about this….

      and they are definitely mainframe minded…..like Venus talking to Mars  ðŸ˜¯

    • #71862
      Bob Schmid
      Participant

      By the way…this is for their HDX eligibility system running on OPENLINK.

Viewing 9 reply threads
  • The forum ‘Cloverleaf’ is closed to new topics and replies.

Forum Statistics

Registered Users
5,117
Forums
28
Topics
9,292
Replies
34,435
Topic Tags
286
Empty Topic Tags
10