Announcement

Collapse
No announcement yet.

Mirth Database

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mirth Database

    Hello there, I’m new to Mirth Connect. I would like to know data storage events in mirth database. I know mirth does have default database derby and we can configure to SQL server.
    Performance wise, is it a good way to store data (patient details and other log information) in mirth database or would it be good to keep derby as default and store data outside mirth?

    Scenario is, can we save all incoming data in mirth database and once decision is made on record, move that record to client database. Is this possible?
    If yes, will there be any performance issues?

  • #2
    Do not use Derby for anything production. In fact I would suggest you never use it at all, instead configure mirth to use a real database server engine.

    Mirth needs a database for its stuff, it is not intended to be the "application" database. It can of course sit on a server that has other databases.

    Your application(s) database should sit in some other database. By "application" I mean the thing / process / stuff you are connecting to with mirth, and EHR for example.
    pacmano
    Mirth Guru
    Last edited by pacmano; 01-11-2022, 12:39 PM.
    Diridium Technologies, Inc.
    https://diridium.com

    Comment


    • #3
      Hello Pacmano,

      Thank you for your response.

      Comment


      • #4
        Originally posted by hellothere View Post
        [FONT=Calibri][FONT=Sanskrit Text]

        Scenario is, can we save all incoming data in mirth database and once decision is made on record, move that record to client database. Is this possible?
        If yes, will there be any performance issues?

        Technically you can, but you really shouldn't do it. Like Pacmano said, that DB is for mirth's internal working.
        HL7v2.7 Certified Control Specialist!

        Comment

        Working...
        X