Question Yuhong Snyder · Jan 7 is it possible to kill the hl7 message in data transformation Hello, is it possible to kill/suppress hl7 message in the DTL (data transformation). in cloverleaf, it is common practice to check the value in message, for example pv1:7.9. if the value is certain word(assigning authority) then send the message over to destination, if it is not, kill the message how would this be done in InterSystems ? does that need to be done in the rule instead? or can it be done in the data transformation? if it can be done in data transformation, how can it be done? Thanks #DTL #HL7 #HealthShare #Health Connect 1 4 0 79
Question Yuhong Snyder · Dec 23, 2024 in business rule , it cannot valuate the value in iteration? We have a customized doctype with iterated PIDgrp, so I have a rule that needs to evaluate the pv1:3.1 value to decide which operation the HL& message should go, so I debugged the value in the rule and it definitely should go to the when #2 but it just won't. so did I do anything wrong or it is just the InterSystems doesn't like the iteration value here? I only need to evaluate the first pv1:3.1 #Business Rules #Health Connect 0 4 1 73
Question Yuhong Snyder · Nov 21, 2024 hl7 message test fine in DTL, but the message is not transformed correctly in end to end test Has anybody encountered this before? I did a very usual hl7 adt transformation DTL, but it is with a customized schema, like ADT_ALL, it is a structure that tries to cover all the ADT schema scenario so we can use 1 type for all ADT messages. the DTL tests fine in DTL test, with all the segment transformed correctly, but once I put it to test, to send message through source and the message after transformation can only go to MSH, EVN, but won't transform other segment like PID etc. #DTL #HL7 #HealthShare 0 5 0 73