High-Performance Message Searching in Health Connect

The Problem

Have you ever tried to do a search in Message Viewer on a busy interface and had the query time out? This can become quite a problem as the amount of data increases. For context, the instance of Health Connect I am working with does roughly 155 million Message Headers per day with 21 day message retention. To try and help with search performance, we extended the built-in SearchTable with commonly used fields in hopes that indexing these fields would result in faster query times. Despite this, we still couldn't get some of these queries to finish at all.

The ability to resend messages easily has always been a strong feature of our Interoperability capabilities.

With v2024.3 coming out soon (available already now as Developer Preview) out already we've made this even easier!

If you had the opportunity to change something in the IRIS Interoperability Message Viewer, what would you do?

Hey community, how are you doing?

How do you exercise your creativity? How do you test new ideas?

Over the years I have always thought about creating new things, modifying existing ones, experimenting, testing, breaking (it always happens), building again, starting over.

The contests promoted by InterSystems are an excellent source of motivation, obviously, the prizes bring a lot of attention and this you cannot deny. But not just prizes/rewards, they also give us a creative challenge, an opportunity to create, reimagine, test, experiment.

If you work with interoperability productions of InterSystems IRIS or Ensemble, no doubt you are familiar with the Message Viewer page. The page supports filtering messages according to filter criteria you enter in the Basic and/or Extended Criteria sections. Extended Criteria conditions are specified as property-operator-value triples. Once you click Search button, such triples become WHERE clause conditions of a generated SQL query executed against message header/body tables.

As a side note, one can view recently generated message queries by following the instructions listed in the doc.

Prefer not to read? Check out the demo video I created: