InterSystems IRIS for Health

The idea would be to create a subset of message headers that can be used as the basis of a message search so any future work on that subset can be referenced without querying the full bank of messages. Potentially more than one person could use th...

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....

We may run the rules chain by using Rule Editor with DTL, which is applicable if regarding protocols-transformation and fields-mapping from sources to targets It is expected to run the rules chain by using Rule Editor without DTL, namely against a...

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...

The are huge amount of business rules needed in transferring and transforming data

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.

Most of the time, when using the Message Viewer in Health Connect, I need to search by PatientID for fault finding or analytical purposes. It would be handy if there was a field already on the Message Viewer page to search by PatientID, instead of...

{"children":[{"type":"paragraph","children":[{"text":"Just like creating regular, as well as Interoperability enabled namespaces,allow for seperate default code/data databases, specifying physical location, security and other parameters, creating ...

We utilise the Export feature to export classes from a production ready for a deployment. We already have a list of classes to deploy from our source control history. It would be handy if we could list out the classes/production items/ LUTs etc., ...