#HealthShare

Have Docker running in Ubuntu and successfully downloaded IRIS Healthcare ML Community to local machine.

Cannot figure out how to launch IRIS...help!

Thanks, all...

Martin Arnold

I am trying to find the presentation for the User Group Sessions that were given at Global Summit last week. In particular the Healthshare Provider Directory presentation, so I can share the ideas with others at my organization. Does anyone know where I can find those? I am not seeing them under the Global Summit tag.

Thanks

Scott Roth

The Ohio State University Wexner Medical Center

Hi,

Any idea how to reference Header and Body properties of a message in a Routing rule?

We have a situation where we want to save the patient photo (or any other attachment) received via FHIR to a persistent property without decoding it. When it is sent out again using FHIR is is stored in the encoded format and need not be encoded. We do not need to decode it for our application. We always use it on another system that retrieves it or saves it via FHIR and therefore it is always received or sent embedded in JSON.

we are getting number of msgs from multiple facilities into our HIE solution, now which facilities is sending bad quality data and put some process around it to improve the msg quality

so where to start to generate this report, any guidance would be appreciated.

Hi

This morning I noticed that the ISCAgent.log for one of my high availabilty healthconnect servers has many entries that say:

"Mirror remote control command requested access to instance directory not found in registry."
Requested:d:\intersystems\healthconnect\

In addition, Messages.log has many of the following entries:

Given the number of new features in this release, InterSystems has decided to add this fifth preview as part of the 2024.1 developer preview program. This extended developer preview release only includes InterSystems IRIS^® for Health^TM, and HealthShare^® Health Connect.

❗This announcement does not apply for InterSystems IRIS^®

We are receiving XML documents and storing them. When we click to go into the clinician portal and again to view a patient, we can see the documents but none of the data is mapped to their respective buckets, i.e. allergies or medications.

I am thinking that I need to build an XSLT parser and change the format to SDA3, is this an appropriate approach? Or would using the Data Transformation (Ensemble -> Build -> Data Transformation) be a better idea? Lastly, if the XSLT idea is preferred, where would I call it within the stack?

Environment: Cache for Windows (x86-64) 2015.2.2 (Build 811U) Thu Mar 3 2016 12:55:48 EST [HealthShare Modules:Core:14.01.351

When try the following to send back SOAP Fault, is the following correct way?

Set fault=##class(%SOAP.Fault).%New()
Set fault.faultcode=$$$FAULTServer
Set fault.faultstring="Processing Error"
Set fault.detail= "Error on server"
Do ..ReturnFault(fault)

I only recently noticed the presence of a local database named CACHE alongside the more familiar CACHESYS, CACHELIB, CACHETEMP and CACHEAUDIT.

A bit of digging through the documentation archive led me to conclude that the CACHE database arrived in 2010.2, where the release notes say:

I need to create a document with a root like this:

<?xml version="1.0" encoding="UTF-8"?>
<RCMR_IN200002FI01 xmlns="urn:hl7-org:v3" ITSVersion="XML_1.0">
...

</RCMR_IN200002FI01>

However, the CreateDocument in %XML.Document only allows namespace as an additional argument.

I did override this method, but trying to do something like

Do document.SetAttribute("ITSVersion",,"XML_1.0") only results an empty document with the <?xml> declation only.

-Pasi-

I was searching for the most simple way to connect from visual studio code to my local instance via terminal without having to change any window.

I know this can also be achieved via telnet but seems a bit overhead if you're in your local machine.

For me the simplest sollution is to open a terminal window in VS Code, navigate to the /bin folder of your instance installation and run .\csession.exe INSTANCENAME

For simplicity you can just include your /bin folder in your path so you don't even need to navigate there

This message contains four recent HealthShare Advisories, which are available below.

This is the seventh in a series of releases that are part of the developer preview program for 2022.2 Future preview releases are expected to be updated biweekly and we will add features as they are ready. Many updates, fixes and enhancements have been added in 2022.2, in SQL management, cloud integration, Kafka and JMS adapters, the SQL Loader, and other areas.