Is the SEPCHARS USERDATA key used by Xlate??

This topic has 6 replies, 3 voices, and was last updated 17 years ago by Jim Kosloskey.

Creator

Topic
January 8, 2008 at 9:09 pm #49732
Jim Kosloskey
Participant
All,

Does anyone know if the Xlate uses the SEPCHARS USERDATA Keyed list?

If not, how does one change the separators the Xlate places in the message?

Thanks,

Jim Kosloskey

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

Topic

Viewing 5 reply threads

Author

Replies
- January 9, 2008 at 2:47 pm #63328
  Steve Carter
  Participant
  I’m not sure about the metadata, but you can just map your new separators in the Xlate.
  
  Here’s an example out of an Xlate:
  
  { { OP COPY }
  
  { ERR 0 }
  
  { IN =^~!& }
  
  { OUT 0(0).MSH(0).00002(0) }
  
  }
  
  Your message will be processed based on the input separators, but will be written with the new separators.
  
  Hope this helps.
  
  Steve
- January 9, 2008 at 3:03 pm #63329
  Jim Kosloskey
  Participant
  Steve,
  
  Thanks for the reply but the solution you express is for HL/7.
  
  X12 is different and the seperators are not a part of a segment the Xlate sees such as the MSH with HL/7.
  
  In the Cloverleaf(R) world as it is constituted today X12 is reliant in large extent upon the presence of the SEPCHARS keyed list in the USERDATA Metadata field (at least for the provided Tcl packages and procs).
  
  What I need to know is if there is SEPCHARS present in a message’s Metadata USERDATA field at Xlate time will those separator characters be used?
  
  If not, how does one influence the separators implanted by the Xlate for X12?
  
  Thaks,
  
  Jim Kosloskey
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- January 9, 2008 at 3:54 pm #63330
  Bob Richardson
  Participant
  Greetings,
  
  Jim, we have an X12 translation for 270/271 Eligibility and the Xlate procedures must reference the SEPCHARS metadata field. How else would it know their values as the message is a single ST? In my previous post, a sample of the SEPCHARS metadata field was supplied as an example.
  
  I am thinking that you could override the values in this field prior to xlate in a tcl proc or perhaps the following would work at xlate time:
  
  something like
  
  COPY @null To @null with a pre-proc inline tcl that updates the SEPCHARS field prior to any other action like BULKCOPY?
  
  Never tried that yet but what you need to do may become my problem down the road.
  
  Hopefully these ideas are useful.
  
  Let us know what you came up with as a solution!
  
  Enjoy.
- January 9, 2008 at 4:07 pm #63331
  Steve Carter
  Participant
  I just assumed HL7 since you didn’t specify X12.
  
  Good luck finding a solution.
  
  Steve
- January 9, 2008 at 7:17 pm #63332
  Jim Kosloskey
  Participant
  Teve,
  
  Sorry about that 🙁 – I should have been more explicit.
  
  Thanks,
  
  Jim Kosloskey
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- January 9, 2008 at 7:24 pm #63333
  Jim Kosloskey
  Participant
  Bob,
  
  Well, when I use the Xlate tester and create an X12 message from an FRL, there cannot be a SEPCHARS entry in the USERDATA and yet the Xlate places seperators.
  
  So I am guessing Xlate has a default set it uses.
  
  I guess I will try adding SEPCHARS to a the FRL message’s USERDATA and see if the seperators change.
  
  If that is successful, it means I cannot use the tester to generate X12 messages with other than the default seperators Cloverleaf(R) has – bummer!
  
  Thanks again,
  
  Jim Kosloskey
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
Author

Replies

Viewing 5 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.