We implemented a filtering solution on ADT message based on order messages. I know it seems a bit out of order but we need to filter which vendors get ADT messages based on the orders placed on accounts.... HIPAA thing you know can't send everyone all the data if they don't need it... Anyway our solution works great on Mirth 1.3.2 no hitches or glitches so I have not had to log into the administrator for a long time. Now it takes an hour or more to launch the Administrator. My guess is it has something to do with the total number of messages, I set the interfaces up to only keep a couple of days but it is still killing us to launch the admin. Anyone know of a fix patch or way to purge/reindex the core db to fix this issue?
Announcement
Collapse
Mirth Connect 4.3.0 Released!
Mirth Connect 4.3.0 is now available as an appliance update and on our GitHub page.
This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.
Download | See What's New | Upgrade Guide | Release Notes
For discussion on this release, see this thread.
This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.
Download | See What's New | Upgrade Guide | Release Notes
For discussion on this release, see this thread.
See more
See less
1.3.2 Administrator launch time increasing rapidly
Collapse
X
-
Re:1.3.2 Administrator launch time increasing rapidly
This was a problem with 1.3.2, based on the number of messages in the database and counting them for the statistics. If you upgrade to 1.5+ this slowdown was resolved. There were also a lot of other performance increases.
JacobJacob Brauer
Director, Software Development
NextGen Healthcare
sigpic
Comment