go to post Alex MacLeod · Nov 3, 2016 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
go to post Alex MacLeod · Oct 11, 2016 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
go to post Alex MacLeod · Jul 25, 2016 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.
go to post Alex MacLeod · Jul 25, 2016 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: - If lab result is on the blacklist (DeepSee Term List) never release. This is used for lab results like HIVYou 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
go to post Alex MacLeod · May 31, 2016 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