go to post David Marcus · Jun 12 Can you use the Service Registry? https://docs.intersystems.com/healthconnect20241/csp/docbook/Doc.View.cl...
go to post David Marcus · Sep 12, 2023 SDA may be too large to instantiate a Container object. Instead, use ##class(HS.SDA3.Container).InitializeXMLParse and ##class(HS.SDA3.Container).GetNextSDA to instantiate each streamlet.
go to post David Marcus · May 15, 2023 If you wrote the transform, then you presumably know what it does. Our transforms have a Canonicalize template. But, I don't think we should be removing an element. My guess is your template isn't really being called.
go to post David Marcus · May 11, 2023 Are you adding this to an XSLT that comes with HealthShare? Our transforms sometimes tidy up the output, so may remove things you don't expect them to remove.
go to post David Marcus · May 10, 2023 Normally we don't put the full SDA into a Container object because it can be quite large. Instead, you are supposed to loop through the streamlets and put each into an object (there are methods for doing this). Do you really need the full SDA as an object?
go to post David Marcus · May 2, 2023 The best place to start is to look at the HS.Sync.Operations business operation in the Registry. Look at the Interoperability/Ensemble Event Log and the Interoperability/Ensemble traces for the messages. Note that errors that occur on the non-Registry instance when loading the sync file are passed back to the HS.Sync.Operations in the Registry, but not put in the Interoperability/Ensemble Event Log. However, they should appear in the Interoperability/Ensemble trace in a message sent to the HS.Util.Trace.Operations component, assuming the TraceOperations setting of the HS.Sync.Operations component is not blank (it is *ERRORSONLY* by default). If TraceOperations is off, then you can look at the SendStatus property of the HS.Message.Sync response.
go to post David Marcus · Apr 6, 2023 Do you mean the streamlet is in a different Edge than the documents?
go to post David Marcus · Feb 27, 2023 https://docs.intersystems.com/hs20222/csp/docbook/DocBook.UI.Page.cls?KE... "19. Beginning in version 2022.2, HealthShare offers stream compression for your Edge Gateways, and provides a conversion utility to compress existing streams in the ECR database at each Edge Gateway. The conversion process is designed to not interfere with regular Edge Gateway data processing, and should complete within a day. ..."
go to post David Marcus · Feb 24, 2023 I don't know what the best approach is. You can call into ObjectScript from an XSLT using the isc:evaluate function. This is handled by the class in the XSLTCallbackHandlerClass property in HS.Util.XSLTTransformer. The HealthShare callback handler is HS.Util.XSLTHelper. You can extend this class to add functions to isc:evaluate and then point the transformer at your callback class. This is discussed in the documentation: HealthShare 2022.2 > Using XML Tools > Performing XSLT Transformations > Specifying Parameters for Use by the Stylesheet > Adding and Using XSLT Extension Functionshttps://docs.intersystems.com/hs20222/csp/docbook/DocBook.UI.Page.cls?KE...
go to post David Marcus · Feb 22, 2023 InstanceGUID returns the GUID of the instance, which does not change. $system.Util.CreateGUID() will generate a GUID. See https://docs.intersystems.com/iris20223/csp/documatic/%25CSP.Documatic.c...
go to post David Marcus · Jan 16, 2023 If you use our (ISC) components, then we should handle the clean up. If we don't, it is either a bug or you are not using the components correctly.
go to post David Marcus · Jan 9, 2023 If you write custom code that uses HS.SDA3.QuickStream, it is your responsibility to clear the stream when it should be cleared.
go to post David Marcus · Oct 31, 2022 Health Connect can be deployed using Kubernetes. Please see https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI...
go to post David Marcus · Oct 18, 2022 Oh. Maybe some bad data. If you need this to work, you should probably contact Support.
