Hi,
accessing SDA streamlets directly is actually not supported, neither is adding indices. Maybe if you could elaborate a bit what you're exactly trying to do, we can find a way to do this that won't break if we change something in product, etc.
Thanks,
-- Alex
Hi Ephraim,
you can create a custom rule and then change the classifier rule for that property, though on upgrade you'd probably have to change it again since you're re-using an existing field. I'm not sure what the South African ID looks like but you should be able to do similar type pattern matchings and such. Happy to help if you share the general format?
-- Alex
https://docs.intersystems.com/hs20221/csp/docbook/DocBook.UI.Page.cls?K…
Just an update that I got this to work with the help of this article and Steve by setting the port ranges as outlined before:
Set tPortRangeStart=$G(^Ens.Config("FGTelnetRange","start"),63300)
Set tPortRangeEnd=$G(^Ens.Config("FGTelnetRange","end"),63499)
and then in the docker-compose file map them as follows:
ports:
- "8091:1972"
- "8092:52773"
- "63300:63300"
- "63301:63301"
I wouldn't use a DTL for process flow control. I would have a BPL make those decisions and use the DTL strictly for transformation of the message. The BPL diagram can then just fall through to the end once the REST call is successful. The operation doing the REST call should then handle the infinite retry, Failure Timeout of -1 would tell it to never stop retrying as you said.
HealthShare Health Connect would work, which I believe you have, Scott?
Take a look at the EnsLib.HL7.Message class. It has the following method to import from %String:
classmethod ImportFromString(pString As
It also provides similar methods for importing from streams, which could be a file character stream. You can view all of these methods using the class reference from the documentation. Hope that helps.
Hi Joseph,
this is a problem that really needs to be fixed on the Information Exchange side that will then propagate over to Health Insight. However we do not support directly editing the existing streamlets - I believe in later versions there will be a tool to assist with editing existing data but the product team will have to comment on that. So did the AA stay the same but just the OID changed? I'm still not quite clear what the change was and what you mean by custom SQL to pull just the code. Maybe it helps to see a before and after?
Thanks,
-- Alex
Hi Joseph,
how did you update the AA exactly? Did you manually go into the Registry or was it updated by feeding new data into Information Exchange?
Sorry, I meant to say we might change the storage structure. As David mentioned there are other reasons for this, you are only querying a specific edge, without aggregating data, you are avoiding consent policies, etc. etc. Those tables should only be populated as part of HealthShare Information Exchange.
Hi all,
Mirroring is not yet supported for Information Exchange. We also do not support that type of direct access in any reporting environment. It isn't due to performance reasons, it is because we make no guarantees that those tables stay the same. We expose public APIs for these purposes as Robert said. Typically these are the SearchAndFetch type APIs - if you search the documentation for "supported APIs", a list will come up.
Thanks,
-- Alex
I know I am, but I wanted the article to be generic so that others would know what to do if they run into the same issue ;)
Could you share a reproducible case with us (SDA processor class, test patient, term list)? Either support or your Sales Engineering team. We can share what the problem was on here afterwards.
You should have already configured the workbench to use your custom SDA processor class, correct? There shouldn't be any new BP to add. What's the error you are getting?
Hi Nora,
the SDA processor example already includes code to check a DeepSee Term List for sensitive lab values for example, see the following comment:
You could utilize the same type of logic to check diagnosis codes or other values in the SDA against a term list of sensitive codes/values.
Thanks,
-- Alex
You could set up a bad message handler to send out an alert I believe (http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…).
Hi Paul,
what type of XML documents are you receiving (CCDA/CCD?) and how are you getting them into the exchange (IHE?). What version of HealthShare are you running?
Thanks,
-- Alex