InterSystems Products

UserValues are a property of every instance of EnsLib.EDI.Document objects (e.g. HL7 Messages). They allow storing of e.g. Metadata alongside the message using dtl and retrieve the information stored in there for example in routing rules. Unfortun...

Currently there is no source control available for different components of the Interoperability production. There is a tool git-source-control that helps with some components, e.g. production itself , but business rules editor doesn't have such a ...

Lookup tables provide a much needed configuration ability that allows us to use different values for different namespaces. However they are not audited so there is no way to track who changed what and when. Please audit them so we can see the chan...

People building Node.js apps commonly use npm as the place they get packages they depend on. Not being able to get the files needed for InterSystems IRIS Native API for Node.js from there adds friction which probably results in some lost opportuni...

Ukrainian translation is also quite horrendous. In some places you can see placeholders instead of words, so it's not even remotely clear what is going on and what is or needs to be done. Studio suffers the most.

Sometimes when we make changes in the data classes, in pivots it can influence on the pivots and dashbords and those stop working. And it is very difficult to find the problem in pivots and dashboards especially if there are a lot of them - e.g. h...

The current spanish translation of IRIS products is...horrible, it's so literal that the most of the time you don't understand the functionality. A lot of concepts used in IRIS are perfectly in english and is not necessary a translation, for examp...

Superset has been mentioned in Thoughtworks Technology Radar 27: https://www.thoughtworks.com/radar/tools?blipid=202005098 I think IRIS should be in the list of supperted databases

Standardizing the address fields would improve autolinking and save time spent on manual review. By using the US@ standards, it would improve interoperability and data sharing. Minutes from the April 2021 meeting are attached. See ONC for further ...

I'm sure that I am not alone in maintain a mass of legacy code, some of which uses the dot syntax for blocks of code. Wouldn't it be great to have a tool to convert this to guaranteed equivalent code using the bracket {} syntax?