go to post Colin Brough · Mar 26 Thanks, @Enrico Parisi, that looks a good starter for the kind of thing we are exploring.
go to post Colin Brough · Mar 26 Thanks for the link, but as we are stuck on Ensemble (not Iris), we can't make use of this.
go to post Colin Brough · Mar 25 Thanks, that's helpful. Our end goal was the perennial XML to JSON conversion conundrum, or HL7 to JSON, and as we're currently stuck on Ensemble 2018, we've not got access to %JSON.Adapter, so we're... limited. Our immediate goal was, given a particular message/document, visit all nodes holding data within the document (traverse the tree), and do some processing for each node - eg output a JSON representation of the data held at that node so that a JSON serialisation of the whole document can be produced; but the general case, not just the JSON case, is of interest. Current application is taking an HL7 feed and sending (a subset of) the data in the HL7 and sending to be consumed by a downstream system via a REST web-service. The downstream in this case is being developed by another team within our organisation, and they can take XML - we've built a transformation to extract the relevant data into an EnsLib.EDI.XML.Document, and we've developed an XML schema for the data so we can validate it before sending on. But it would have been easier for them to consume JSON, so we were exploring how to do that - and are conscious that future requirements might include sending JSON rather than XML...
go to post Colin Brough · Mar 17 Thanks @Eduard Lebedyuk , that was helpful. As you describe, headers are not re-used from a previous call. On closer inspection, our confusion arose from the fact that if you provide a set of credentials as a setting on the operation which is implemented by EnsLib.HTTP.OutboundAdapter, even if you don't explicitly set the Basic Authentication headers yourself, they are created for you by the adapter using the provide credentials - we didn't realise this, and so when we removed our own explicit setting of the headers (for testing) we were confused by the headers still arriving in the downstream system!!
go to post Colin Brough · Mar 5 Update: this was answered by @Brett Saviano on the GitHub discussion forum for the VS Code extension: Should the extension change line feeds on compilation? · intersystems-community/vscode-objectscript · Discussion #1495
go to post Colin Brough · Feb 25 I was going to respond and say something like, "I'm sure that does answer the question, but I'm not sure I understand the answer!" So thanks for the executive summary! And thanks @Robert Cemper for the background information.
go to post Colin Brough · Jan 29 With help from WRC, looks like this is something of our own doing - we were using sub-transforms in ways that caused us problems. Our sub-transforms above were outputting whole new XML documents, when at the very least they should have been taking existing partially produced XML from the top-level transform and using that existing document to output. We "solved" the node ordering issue by moving everything into a single transform, so there was no mismatch between top level and sub-transforms.
go to post Colin Brough · Jan 29 For the sake of other people being able to find an answer, we took this up with WRC. Suspicion is this is a bug/aberrant behaviour in Ensemble (and they suspect recent versions of Iris). WRC were going to check in with development, and we are still waiting to hear back from them around that.
go to post Colin Brough · Jan 13 Note that this issue arises in a transformation we are also having other, we suspect unrelated issues with, discussed here: DTL Transformation output: maxOccurs bug? | InterSystems Developer
go to post Colin Brough · Jan 10 Its a virtual document: EnsLib.EDI.XML.Document, with the XML schema applied having been loaded into Ensemble via Ensemble -> InterOperate -> XML -> XML Schema Structures.
go to post Colin Brough · Jan 10 Thanks @Enrico Parisi and @Jeffrey Drumm - knew there'd be a way of dodging the limitation!
go to post Colin Brough · Jan 10 Additional info: if we change the order of <allergies> and <patientNotes> in the schema, it does not change the order of elements produced in the XML.
go to post Colin Brough · Nov 22, 2024 If only MSH-18 were set... 🙄 Up-stream system isn't setting it! And until yesterday supplier of upstream system was claiming they were sending UTF-8 when we thought the feed looked awfully like Windows-1252. Yesterday they admitted/confirmed they are sending Windows-1252, so at least now we know!!
go to post Colin Brough · Nov 20, 2024 We've got the same issue, but with an incoming HL7 feed with embedded, encoded characters - would be nice to be able to detect what's coming in, but I take it from this discussion that's not (reliably) possible. Don't really want to scan the whole text of every incoming message to heuristically look for possible encodings. Upstream say/think they are sending UTF-8, but we seem to be getting Window-1252, for the characters we've seen in the (limited) testing. Who knows what will come through the feed once it goes live!
go to post Colin Brough · Oct 28, 2024 Never mind, our support people had updated the Java version, despite what the logs said! And because they hadn't restarted Ensemble/the server, it still had the old JAVA_HOME in its environment. We are currently banging their heads against the nearest wall for them! 🙄
go to post Colin Brough · Sep 30, 2024 Thanks Ben, that confirms what we suspected and gives us a tool to try and remedy the situation if (as we suspect) the supplier of the "interfering" system isn't very interested in fixing something affecting a tiny number of developers!
go to post Colin Brough · Sep 27, 2024 Auto-adjust / design question 4: we'd find this useful, especially if it handles bulk renames - a bunch of classes implementing a data type, all being moved in one go from one place in the class hierarchy to another and all being consistently renamed. So files X/Y/A.cls, X/Y/B.cls, X/Y/C.cls, and containing classes X.Y.A, X.Y.B, and X.Y.C being moved to Q/P/A.cls and Q.P.A etc. Especially if Properties defined in X.Y.A as "Property pp As X.Y.B" becomes "Property pp As Q.P.B" when renamed.
go to post Colin Brough · Sep 18, 2024 Closing off an old question for completeness, we never did get Zen working. In the end we used Apache FOP directly: HL7 -> XML as described in the original question call Apache FOP using $ZF(-100, $$$fopbat, "-xml", XMLfilename, "-xsl", StyleSheetFilename, "-pdf", PDFfilename) This puts the output PDF onto the filesystem from where, in our solution, it is later picked up for onward transmission to a downstream system.
go to post Colin Brough · Sep 18, 2024 For the sake of closing off this old question, and to answer my own question, in light of more experience and some testing... side effects of the transformation could, in theory, change the behaviour - but it'd have to be a transformation that had side-effects (eg kept some kind of state across executions, whether in globals or on the filesystem or in some other way) performance could be affected, since transformation is called twice rather than once, but in most cases the difference is likely to be negligible.
