Retention Time of SMAT

Clovertech Forums Cloverleaf Retention Time of SMAT

  • Creator
    Topic
  • #122557
    Rich Brant
    Participant

      Team – We have a ninety day retention, and are running out of space, which is approaching 300G.  What is the industry norm for SMAT retention?

    Viewing 1 reply thread
    • Author
      Replies
      • #122558
        Vince Angulo
        Participant

          Working off an old ‘best practices’ document (V20.x) from infor, I don’t see a standard recommendation.

          It does say that SMAT files should be on a separate files system (esp. if SMATDB is not being used), which is what we do — 180 days on an attached storage appliance.

        • #122559
          Tim Pancost
          Participant

            I don’t know about “industry norm”, I imagine there would be many factors that might affect how long you keep messages resident on the engine machine.  For us, we default to 7 days.  Our train of thought is that if a customer/vendor/whomever can’t realize that there’s an issue within a week, there are likely other issues that need to be addressed first, especially in such a time-sensitive industry as healthcare.  For our BMDI sites, we only keep 3 days-worth, as those values definitely become stale very quickly, not to mention the sheer volume of messages on that type of interface.

            That being said, there are also instances where we go significantly longer, up to 90 days.  These are mostly state agencies(immunization recording, HIE’s, etc…).  They either have regulations on how long messages need to be saved, and/or they are significantly slower in identifying issues that might require resends.

            That that being said, it can also depend somewhat on your main EHR system.  We keep messages in our main system for 90 days.  So, worst come to worst, we can always go there to find messages, if need be.

            HTH,

            TIM

            Tim Pancost
            Trinity Health

        Viewing 1 reply thread
        • You must be logged in to reply to this topic.