Converting SIU_S14 to A08

This topic has 6 replies, 3 voices, and was last updated 11 years, 6 months ago by Chris Williams.

Creator

Topic
April 4, 2013 at 8:19 pm #53598

Mark Brown
Participant

A vendor is wanting to get some fields from a SIU message and have those field put into a A08 message and then send the A08 to them.

I’ve tried using XLATE and I’ve tried using TCL procs and neither approach seems to work. I thought using XLATE would be the easiest, but it’s not picking up the data in the SIU fields. I got the TCL proc to kinda-sorta work, but it leaves the SIU specific segments in the message and is somehow sending the message twice.

Is there any way to make this work? I’m using CL5.7.
Creator

Topic

Viewing 5 reply threads

Author

Replies
- April 4, 2013 at 10:05 pm #78252
  
  Chris Williams
  Participant
  
  Mark,
  
  We had a similar situation a few years ago. Our solution was to split the processing into two separate parts. You can’t rely on the timing or sequencing of the messages to match them up.
  
  1. When receiving the SIU we extracted the relevant fields, put them into a database, queried for an A08 for that patient, then killed the SIU.
  
  2. When a query response A08 came back to the engine, we would do the database lookup to retrieve any SIU data that was there, insert it into the A08, send that message on to the vendor and delete the SIU data from the database.
  
  Cheers.
- April 5, 2013 at 1:22 pm #78253
  
  Mark Brown
  Participant
  
  Chris,
  
  Wow. That sounds pretty complicated. The vendor only wants two fields from the SIU. I’m thinking now that they should be able to parse that themselves.
  
  Thanks,
- April 5, 2013 at 3:37 pm #78254
  
  Chris Williams
  Participant
  
  In our case, the vendor was unable to handle an SIU. Think of it as an adventure in programming. 🙂
- April 5, 2013 at 5:07 pm #78255
  
  Elizabeth Wilson
  Participant
  
  If all you need is to convert S12 to A08 simple action in xlate should do it.
  
  Pathcopy MSH
  
  copy ADT^A08 to MSH.9
  
  copy A08 to EVN.1
  
  copy MSH.7 to EVN.2
  
  copy SCH.12 to EVN.5
  
  pathcopy PID
  
  Pathcopy PV1
  
  and whatever else you need to have in A08.
- April 5, 2013 at 5:14 pm #78256
  
  Mark Brown
  Participant
  
  It turns out the file I was trying to test with had 0a terminating the lines instead of 0d. I got a new test file and then it worked.
  
  Thanks Jim for letting me know what to check.
- April 5, 2013 at 5:44 pm #78257
  
  Chris Williams
  Participant
  
  Elizabeth,
  
  The caviat comes in the “whatever else you need”. The source system we worked with did not send an SIU with all the ancillary info needed to construct an appropriate A08 to meet the destination system’s requirements. Only by combining data from both could we do that.
  
  Cheers.
Author

Replies

Viewing 5 reply threads

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

Converting SIU_S14 to A08

Forums

Forum Statistics