pdl encapsulation characters for HL7

[Bob Schmid]

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

#}#

Topic

[Michael Hertel]

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

[Bob Schmid]

why xb ?

[Bob Schmid]

hci_pd_msg_style basic phrase:basic-msg

                             field:data

                             resync:\xb

‘ failed: invalid command name “resync:xb”

[Michael Hertel]

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

#}#

[Bob Schmid]

/* 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

#}#

[Michael Hertel]

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.  😳

[Jim Kosloskey]

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.

[William Rowley]

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.

[Bob Schmid]

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  😯

[Bob Schmid]

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

[Author]

Replies