CloverLeaf reading Lawson Materials Mgmt file

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf CloverLeaf reading Lawson Materials Mgmt file

  • Creator
    Topic
  • #52333
    Patrick Lane
    Participant

      Hi guys, I am trying to take a Lawson Materials Mgmt file and get it into Epic.  The Lawson file consists of MSH,MFI, CD1, CD2, CD3 segments.  However, if I use a translation or a tcl file it is seeing each segment as its own message when I run it as New Line, if I try to run it as End of File he sees all the segments combined as the MSH…Does anyone have any advice?  Any help would be great.  The file from Lawson is an IC527WK and we are running CloverLeaf 5.5PRev1 on a Solaris server.  Many thanks for any help.  Patrick

    Viewing 2 reply threads
    • Author
      Replies
      • #73835
        James Cobane
        Participant

          Patrick,

          It appears as though the file you were given has each segment delimited by a x0d x0a (CR-NL), rather than just the normal x0d (CR).  You’ll need to convert these x0d x0a’s to x0d’s.  If you used FTP from a windows-based machine to transfer this file, it’s very possible that the FTP tried to be “your friend” and convert the x0d’s to x0d x0a’s.  If you can simply re-transmit the file, try specifying a ‘binary’ transfer to preserve the x0d’s.  If not, you’ll need to create a pre-proc to convert these.

          Hope this helps.

          Jim Cobane

          Henry Ford Health

        • #73836
          Robbie Parker
          Participant

            Consider yourself lucky…their MSCM POU charge files export with double spaces between each segment.   I chose to handle it instead of dealing with their resources in the Phillipines.

          • #73837
            Levy Lazarre
            Participant

              Hi Patrick,

              I am also dealing with the Lawson Materials Management file (IC527WK) and I also receive the file from a Windows server. To process this HL7 batch file, I have placed in the TPS Inbound Data a Tcl script that splits the file into individual messages and does the end-of-line (CRLF –> CR) translation.

              I am not sure if your situation is the same, but Lawson is only sending me one MSH and one MFI segments for the whole batch, while the receiving system requires these segments for each message. Consequently, I had to save the MSH and MFI segments so that I can prepend them to each message when I split the batch.  Once this is accomplished, I am able to send each individual message to Translation, with no need to loop inside the Xlate.

              I hope this helps. If desired, I can send you the sample code to give you a starting point.

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