Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Reducing the lookups in MySQL DB

  • Filter
  • Time
  • Show
Clear All
new posts

  • Reducing the lookups in MySQL DB

    Hello everyone,

    I have the following situation:

    My channel gets a ORU^R01-Message with many OBX-Segment. The values, extracted from every RBX-Segment of the message are used as parameter for a stored procedure, that makes 3 lookups in the DB(collecting values), before writing to a table in the DB.

    The problem is: for every OBX-segment the stored procedure should make 3 lookups before writing to the DB, which is very unefficient.

    Does anyone know how optimize the performance of the whole situation? Is it possible first to collect the values (before the stored procedure executes) and then execute the stored procedure with the collected values as parameter (which only writes some endvalues to the DB)? If I write a javascript programm, that first collects all the values and then calls the stored procedure, will it be a good optimization? (the looping through every OBX-Segment and the calling of the stored procedure for every OBX-Segment remains).

    I appreciate every advice! Thank you,