go to post Leon Wilson · Mar 9, 2022 Thank you all for your input and advise the $ZCVT() did the trick.
go to post Leon Wilson · Mar 7, 2022 Good Morning Julian, Thank you for the response, I have added some more examples to show what happens when the RAW DFT gets pulled into IRIS.
go to post Leon Wilson · Mar 4, 2022 Just wanted to share a test message. The RAW is the original message and the Blue one is what IRIS is transforming it into.
go to post Leon Wilson · Mar 4, 2022 What I really need is to do the translation to do the following. è eé eê eë eì ií iî iï ið oñ nò oó oô oõ oö o à aá aâ aã aä aå a ù uú uû uü uý y ..... just so our system/server dont throw an error everytime. Thank you again for your help. This was one of two attempts, just to give you an idea.: $TRANSLATE(source.RawContent,$CHAR(223)_$CHAR(225)_$CHAR(233)_$CHAR(237)_$CHAR(241)_$CHAR(243)_$CHAR(250)_$CHAR(161)_$CHAR(191)_$CHAR(224)_$CHAR(226)_$CHAR(227)_$CHAR(228)_$CHAR(232)_$CHAR(233)_$CHAR(234)_$CHAR(236)_$CHAR(237)_$CHAR(238)_$CHAR(242)_$CHAR(244)_$CHAR(245)_$CHAR(249)_$CHAR(250)_$CHAR(251)_$CHAR(253)_$CHAR(169)_$CHAR(192)_$CHAR(193)_$CHAR(194)_$CHAR(195)_$CHAR(200)_$CHAR(201)_$CHAR(202)_$CHAR(204)_$CHAR(205)_$CHAR(206)_$CHAR(209)_$CHAR(210)_$CHAR(211)_$CHAR(212)_$CHAR(213)_$CHAR(217)_$CHAR(218)_$CHAR(219)_$CHAR(221)_$CHAR(8482)_$CHAR(8242)_$CHAR(180)_$CHAR(8217)_$CHAR(8216)," aeinou aaaaeeeiiiooouuuy AAAAEEEIIINOOOUUUY ") ..ToUpper($TRANSLATE(source.{PID:PatientName().FamilyName},$CHAR(223)_$CHAR(225)_$CHAR(233)_$CHAR(237)_$CHAR(241)_$CHAR(243)_$CHAR(250)_$CHAR(161)_$CHAR(191)_$CHAR(224)_$CHAR(226)_$CHAR(227)_$CHAR(228)_$CHAR(232)_$CHAR(233)_$CHAR(234)_$CHAR(236)_$CHAR(237)_$CHAR(238)_$CHAR(242)_$CHAR(244)_$CHAR(245)_$CHAR(249)_$CHAR(250)_$CHAR(251)_$CHAR(253)_$CHAR(169)_$CHAR(192)_$CHAR(193)_$CHAR(194)_$CHAR(195)_$CHAR(200)_$CHAR(201)_$CHAR(202)_$CHAR(204)_$CHAR(205)_$CHAR(206)_$CHAR(209)_$CHAR(210)_$CHAR(211)_$CHAR(212)_$CHAR(213)_$CHAR(217)_$CHAR(218)_$CHAR(219)_$CHAR(221)_$CHAR(8482)_$CHAR(8242)_$CHAR(180)_$CHAR(8217)_$CHAR(8216)," aeinou aaaaeeeiiiooouuuy AAAEEEEIIINOOOUUUY "))
go to post Leon Wilson · Jan 19, 2022 Thank you Neil, I had the same issue and by mirroring the HSSYS database solved our issue. now we have the same ClientID and Secret between the DBs. Much appreciated.
go to post Leon Wilson · Aug 10, 2020 Not too worry I figured the issue out and resolved the error. instead of using this class EnsLib.HL7.MsgRouter.RoutingEngine you need to use this class. EnsLib.MsgRouter.RoutingEngine
go to post Leon Wilson · Aug 7, 2020 Good afternoon, Could you please let me know what kind of DocType you used to the transformation, and this is for the record mapper and not for the HL7. I am receiving the following error with in the production process. .....ERROR <Ens>ErrException: <PROPERTY DOES NOT EXIST>zOnRequest+1 ^EnsLib.MsgRouter.VDocRoutingEngine.1 *DocType....... Your help would be super appreciated.
go to post Leon Wilson · Sep 9, 2019 Thanks Paul, I will give it a try and will update the post.. Once more thanks
go to post Leon Wilson · Sep 4, 2019 Here is an additional thought. I know that the results wont always come in the same, some might be positive. My objective is the removal of the OBX if this makes sense to anyone. However this is all test results.. this is NOT Live.