Forum Replies Created
-
AuthorReplies
-
First, you don’t need the variable. The copy statements don’t overwrite the original message so all you need is this:
copy 1(0).1(0).3(0).0(%g1).OBX(0).#3(0).[1] -> 1(0).1(0).3(0).0(%g1).OBX(0).#3(0).[4]
copy 1(0).1(0).3(0).0(%g1).OBX(0).#3(0).[4] -> 1(0).1(0).3(0).0(%g1).OBX(0).#3(0).[1]
normal copy statement with PID-3.1 in source and destination with that code in preproc window.
We do a similar tcl in a couple of our xlates. It looks like this:
set xlateOutVals [string range $xlateInVals 1 end]
Use an IF- ELSE instead of just IF. Like so:
if {***} {
set mykill = TRUE
} else {
if {XYZ} then {
set mykill = TRUE}
}
Lose the equal sign. You cannot have the “=” and the “@” in the IF statement. It should look something like this:
0(0).EVN(0).#7(0).[0] eq @null &&
0(0).EVN(0).#1(0).[0] eq @nullSo, eq @null not eq =@null
I’m on 19.1.2.1. The site name works for me. Thanks.
June 25, 2020 at 10:26 am in reply to: Implementing Virginia Syndromic Surveillance ADT via HTTPS #117238I am also trying to set up an HTTPS connection. Any help would be greatly appreciated.
That’s perfect! Thank you sir!
Yes, if you could share the code for inside the xlate that would be great.
Yes, I saw that it is there. Just having a hard time figuring out how to use it inside an xlate.
The trigger I have set up just like that. the problem is finding the variable in the action so that it only restarts the thread that isn’t up instead of all of them.
hcicmd -p epic_adt_test -c ” prestart 1″
Our plan is to have this be a synchronous exchange the transaction having ISA, TA1, and IEA and to report either accepted or rejected back to the sending application.
Jim Kosloskey wrote:Alfred,
You will want to research the use of the TA1. Especially converse with your trading partner to see what they expect.
At the minimum the TA1 Transaction set should have an ISA, TA1, IEA.
However, in X12 the TA1 is normally used as a mechanism to communicate to the sending system if there are syntactical errors in the ‘envelope’. So make sure your trading partner is or is not expecting that level of reporting.
Also frequently this exchange is ayschronous. That means the sending system will not wait for the TA1 before sendiing the next message. Instead it will receive the TA1 whenever it returns and act accordingly. So make sure what kiind of exchange your trading partner expects (synchronous cn make life easier).
Asynchronous may also mean more than one connecttion (one to receive the messages another to seend back the replies – TA1 for example) – or not.
Yes, we are looking to create a TA1 acknowledgement as a reply message for each of the messages we receive before they continue downstream to the receiving system. We were of the same opinion in thinking that Cloverleaf would have provided this but they said it wasn’t something they had done and that if we wanted something like this we could easily make changes to hl7Raw_ack.tcl to suit our purposes. Unfortunately, I am pretty new to X12.
-
AuthorReplies