I suggest clicking "Dismiss", logging out, and logging in again.
- Log in to post comments
I suggest clicking "Dismiss", logging out, and logging in again.
Windows Terminal > Edit > Network Encoding: UTF8.
The agreement weight is the basic amount to add if they agree. The disagreement weight is the basic amount to add if they disagree. That's why the latter is negative. Tuning is complicated: You need representative data that has both records that agree and records that disagree.
You can get the query the page is using and run the query yourself: https://docs.intersystems.com/iris20252/csp/docbook/DocBook.UI.Page.cls…
I think the Web app has to be /csp/healthshare/fhirdemo, i.e., you can't include .well-known in the Web app. At least, I've never seen a Web app like that. Do the docs say to do that?
If you do Management Poral > System Administration > Security > Auditing > View Audit database, it may tell you something about the error. You may first have to enable the %System/%Security/Protect error in Auditing > Configure System Events.
Did you mean you are using IRIS for Health?
I've never tried this with an IP address. When you configured Network Host Name and Secure Communication in the Installer Wizard, didn't you use a hostname?
Can you use the Service Registry? https://docs.intersystems.com/healthconnect20241/csp/docbook/Doc.View.c…
This is a bug. The WRC is handling it.
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.
Maybe you can use the ##class(%XML.Reader).Correlate method.
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.
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.
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?
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.
Do you mean the streamlet is in a different Edge than the documents?
Are you using Unified Care Record? Health Insight?
https://docs.intersystems.com/hs20222/csp/docbook/DocBook.UI.Page.cls?K…
"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. ..."
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 Functions
https://docs.intersystems.com/hs20222/csp/docbook/DocBook.UI.Page.cls?K…
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…
How do you do that?
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.
If you write custom code that uses HS.SDA3.QuickStream, it is your responsibility to clear the stream when it should be cleared.
Health Connect can be deployed using Kubernetes. Please see
https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.U…
Which HealthShare product do you mean?
I don't think this is a feature of the product.
Oh. Maybe some bad data. If you need this to work, you should probably contact Support.
Don't know. If you reset the Clinical Viewer, does the error stop?
Does it work if the SDACodingStandard is RXNORM? Did you follow the instructions in the docs: https://docs.intersystems.com/hs20221/csp/docbook/DocBook.UI.Page.cls?K…
Did you mean to make it a class method? Is SetSensor a class method?