web stats
Limitations of Mirth connect - Page 2 - Mirth Community

Go Back   Mirth Community > Mirth Connect > General Discussion

Reply
 
Thread Tools Display Modes
  #11  
Old 09-13-2010, 11:39 AM
lgoran lgoran is offline
Mirth Newb
 
Join Date: Sep 2010
Posts: 14
lgoran is on a distinguished road
Default

Quote:
Originally Posted by jacobb View Post
If you could be a little more clear with the exact feature you want I definitely encourage it as a feature request in our JIRA. We are generally quick about adding features users see as limitations.
Yes, it is exactly the same scenario as Piet describes (temporary filename) I am
talking about.
In many cases you can not assume that the receiving application checks for file age,
and in such cases Mirth can not be used to send files, which is a pity since it is not a big change in the connectors. You need an extra option to specify a temporary
directory or file extension to use during the transfer, and then the connector should rename the file when writing is finished.
Have a look at Apache Camel or BizTalk or .....
Reply With Quote
  #12  
Old 09-14-2010, 09:30 AM
geraldb geraldb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 314
geraldb is an unknown quantity at this point
Default

This is a good suggestion. We went ahead an opened a feature request for it:

http://www.mirthcorp.com/community/i...wse/MIRTH-1564
__________________
Gerald Bortis | Chief Information Officer | Mirth Corporation
Reply With Quote
  #13  
Old 09-21-2010, 04:12 AM
lgoran lgoran is offline
Mirth Newb
 
Join Date: Sep 2010
Posts: 14
lgoran is on a distinguished road
Default

Quote:
Originally Posted by geraldb View Post
This is a good suggestion. We went ahead an opened a feature request for it:

http://www.mirthcorp.com/community/i...wse/MIRTH-1564
Great !!
But it it is not perfect unless you add the possibility to write to a different
directory and move the file from there, because you can not be sure that the
receiver does not use "*" as file selector, and in that case it does not help
to use a ".tmp" extension to the file name during transfer.
Reply With Quote
  #14  
Old 09-24-2010, 06:26 AM
panickc panickc is offline
OBX.3 Kenobi
 
Join Date: Dec 2007
Posts: 127
panickc is an unknown quantity at this point
Default

Quote:
Originally Posted by mourisj View Post
The only limitation I'm aware of is support for large files. The limits people here on the forum have noticed are not always the same; I don't know what influences on the limits observed. On our site we have trouble already with files of some 7MB; currently I wouldn't recommend Mirth in our environment if files larger than 5 MB have to be processed.
Large files simply remain there unprocessed, the channel getting unresponsive, even other channels become unmanageable as Administartor seems to get stuck.
I suppose it depends on your implementation. I have a routine to convert an HL7 file to flat file and the files I send to it are 100MB+; in one example 105,000 HL7 messages. No issues ever.

-cp
Reply With Quote
  #15  
Old 09-24-2010, 12:57 PM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

Quote:
Originally Posted by panickc View Post
I suppose it depends on your implementation. I have a routine to convert an HL7 file to flat file and the files I send to it are 100MB+; in one example 105,000 HL7 messages. No issues ever.

-cp
Good to know. I think the issues arise when a single message is that large, rather than a batch of messages. It sounds like the problem with larger files is more likely to happen with dicom messages, and not with HL7 messages. Even HL7 messages with base64 encoded pdf's, images, etc. don't seem to have this issue.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #16  
Old 09-25-2010, 04:59 AM
mourisj mourisj is offline
Mirth Guru
 
Join Date: Feb 2007
Location: Luxembourg
Posts: 407
mourisj is an unknown quantity at this point
Default

Those causing trouble to us are of type "delimited", and indeed one file is considered one single message.
In fact, what we want to do with it, is moving them to appropriate locations in a first step. If this would work, I'd also dare trying to extract some data to inform the users about basic information contained in the file.
__________________
JJ Mouris
FFE Luxembourg
IT-Department
Reply With Quote
  #17  
Old 10-08-2010, 04:55 AM
lgoran lgoran is offline
Mirth Newb
 
Join Date: Sep 2010
Posts: 14
lgoran is on a distinguished road
Default Connector retry

Hi,
In my opinion it is definitely a limitation that connectors
like FTP, and SOAP lack retry functionality similar to
the LLP and TCP connectors.
Reply With Quote
  #18  
Old 10-12-2010, 09:00 AM
J.T. J.T. is offline
OBX.1 Kenobi
 
Join Date: Nov 2009
Posts: 39
J.T. is on a distinguished road
Default

Out of the box printer destinations is lacking for me. That was/is a limitation for our use case.

in the document writer destination, I've also not found a way yet to control the number of pages, or to push the footer down to the bottom of the page.

Other limitations like having to redeploy all channels seem to have been addressed in the upcoming 2.0 version.

Last edited by J.T.; 10-12-2010 at 09:03 AM.
Reply With Quote
  #19  
Old 05-08-2011, 10:04 PM
sunil_sdk sunil_sdk is offline
What's HL7?
 
Join Date: May 2011
Location: Mumbai
Posts: 1
sunil_sdk is on a distinguished road
Arrow Re:Limitations of Mirth connect

Quote:
Originally Posted by ramkrishna View Post
Hi,

Can anyone give me some limitations of mirth connect as i am preparing some documentation on mirth connect...quick reply is highly appreciated..

Thanks in advance..

Ram
Hi Ram,

I am also started working on Mirth Connect documentation. If you have added pros/cons or limitations about Mirth Connect, Can you please forward it to me?

Thanks in advance.
Sunil
(sunil.sdk@gmail.com)
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 12:23 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation