Skip to Main Content
InterSystems Ideas
We love hearing from our users. Tell us what you want to see next and upvote ideas from the community.
* Bugs and troubleshooting should as usual go through InterSystems support.
ADD A NEW IDEA

All ideas

Showing 97

Make Every Operation and Service Expose its message classes

Every Interoperability Business Service sends a message of a certain type. Every Operation receives a request message of a certain type and then sends back a response message of a certain class type. Currently it is not clear which are the these c...
Evgeny Shvarov over 1 year ago in InterSystems IRIS 0 Future consideration

Custom Visualizations for Physicians

Enable physicians to track specific health data using charts and graphs. Physicians can easily monitor trends and make informed clinical decisions.
Ikram Shah over 1 year ago in InterSystems IRIS for Health 3 Future consideration

%NormalizeObject to cater for serial, list of objects and user call-back

It will be helpful if the %NormalizeObject method had the same depth of functionality as %ValidateObject. %ValidateObject has the checkserial argument. Adding the same type of argument to %Normalize will make things simpler when it comes to normal...
Stefan Cronje over 1 year ago in InterSystems IRIS 0 Future consideration

Public API for access to shared memory

Sometimes we need to have a resource shared among several processes, e.g. some application counters, that we don't want to be looked up by users. Globals don't fit this need for evident reason. The idea is to provide an API which allow shared (whi...
Alexey Maslov over 1 year ago in InterSystems IRIS 1 Future consideration

Automatic XML Formatting of XData in DTL, BPL and Rulesets

The basic idea is that when a DTL, BPL or ruleset is edited on the SMP, that is formats the XML in the XData block. With large DTL, Rulesets and BPL, it is sometimes easier to open the class, collapse some sections of the XML and check the flow. P...
Stefan Cronje almost 2 years ago in InterSystems Products 3 Future consideration

Add address standardization to Normalization (using Project US@ standards)

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 ...
Susan Saul about 2 years ago in InterSystems HealthShare 0 Future consideration

Do not change formatting when compiling through GUI

In mixed development environments where some team members use the GUI and others use VS Code, the latter will remove the formatting (comments, algebraic assignment notation, spacing) performed by the former when compiling.
Jonathan Anglin about 2 years ago in InterSystems IRIS 2 Future consideration