go to post Stuart Byrne · Nov 9, 2022 Hi @Kathy Ward Are you trying to transform from HL7 2.x to HL7 2.x?If that's the case you should be able to map the OBX()-5 from target to source. Regards Stuart
go to post Stuart Byrne · Sep 7, 2022 Your getting that error as your class is named %BI.Adaptor. Create a custom name and extend %BI.Adaptor
go to post Stuart Byrne · Aug 19, 2022 The key (k1) is missing from your targetObj:<subtransform class='ADT.DTL.SDAToPatientIdentifierInfo' targetObj='target.PatientIdentifierInfo.()' sourceObj='source.{Patient.Extension.PatientIdentifiers(k1)}' /> In your master transform is this housed within a foreach loop and k1 defined?
go to post Stuart Byrne · Mar 14, 2021 Hi Joey, @Arun Tiriveedhi is correct that you need to use square bracket syntax, as this returns a comma delimited list. I had a case where I had a whitelist of OBR-4.1 values for filtering result messages to a particular system. @Stephen Renshaw made a great suggestion to create a function to loop through the list and query the lookup table here: https://community.intersystems.com/post/using-lookup-or-exists-repeating-fields-ensemble-business-rule Regards Stuart
go to post Stuart Byrne · Oct 23, 2017 You can also test Data transformations from within the Data Transformation Editor, if you have the message as text.There is no direct way (without writing something) to get 1 message through.An indirect way would be use the throttle delay option for the Business Service, Business Process(es)/Router(s) & Business Operations in Ensemble via the Settings tab in the Additional Settings section.It works in the Milliseconds (1000 milliseconds = 1 second) , so to get one message through with enough time to stop the feed you would set it to 60,000 milliseconds.We used this to assurance test each of our feeds on the day when upgrading to Healthshare 2017.1I hope this helps you.PS you would need to remember to remove this throttle after testing, otherwise in a production environment you would have queues galore.
go to post Stuart Byrne · Jun 29, 2017 After some investigation I found that the method would work with the following:I found a quirk in the testing service, where the rule would not work using the testing service. I created a business Operation that feeds our ADT Business service and the same messages now all work.I'm currently testing with our eMR (Epic's) DEV platform ADT messages and this is also working.It looks like the testing service might works a bit funny when running from the router.Thank you all for your reads and contributions.