InterSystems IRIS for Health

when exchaning patient documents over information networks, it is demanded to sign these documents digtally. whilst we support cryptogprahy for XML documents, we do not have similar functionality available for serialized json documents.

IRIS (for Health, HS HC, HS) DICOM interoperability adapters use the filesystem to store raw messages, the directory used can be configured in the StorageLocation production settings, obviously this is a big issue in mirrored environments if/when ...

In a large XML message being sent (i.e. a sql snapshot) the XML can be so long when you click Contents or open it up via the message it will time out the portal. I.E. viewing EnsLib.SQL.Snapshot with 8733 rows This is two suggestions: either: 1) t...

audience is often required form recorded body SettSC=tHttpRequest.SetHeader("Content-Type","application/json")SettSC=tHttpRequest.SetHeader("audience","https://patientlist-api-cqa.drdoctor.co.uk/") DotHttpRequest.InsertFormData("client_secret",cr....

While the ability to save a MessageViewer Search in one namespace is helpful, it would be even better if we could access these saved searches to different namespaces. Right now the only way to do that is to open the Saved search in the namespace w...

Managing queue when we need to reprocess messages from business process is not easy in HealthShare at the moment. Any ability to hold current queue in business operation while repossessing large number of older failed messages from business proces...

See the justification and workaround here: https://community.intersystems.com/node/546311 The workaround above has drawbacks, so a formal, ISC-supported mechnism for providing captions for custom properties would be a benefit.