In order to prevent messages accumulating indefinitely, messages may be assigned an expiry date, along with
a flag for whether they will be deleted or archived. The expiry date and flag may be set in the following places:
- On incoming interfaces
- On outgoing interfaces
- Globally via the General Configuration Settings
When the expiry date is set by an interface, the date that the message will expire is stored with
the message and can be seen when browsing the messages. The global setting applies to any messages
that do not have an expiry date set by the interface that handled the message. In all cases, 0 means that the messages do
not expire. Once the expiry date is reached, the message will either be deleted completely, or moved into the archive, depending on the choice when setting up expiration.
There are two different settings for incoming interfaces - how to long to store messages that are routed
to outgoing interfaces, and how long to store un-routed messages. The notion is that messages that
are not routed may need to be handled retrospectively once their fate is determined, so they may need
to be stored for a longer period of time.
There are two different settings for outgoing interfaces - how to long to store messages that are
successfully sent, and how long to store rejected messages. The notion is that messages that
are rejected may need to be resent retrospectively once the problem is determined, so they may need
to be stored for a longer period of time. Messages that are still waiting to be sent to an interface
are never deleted automatically.
Usually a message is received on an incoming interface, and then sent on to multiple outgoing
interfaces. In these circumstances, multiple interfaces may make different rules about how
long a message is stored, and whether it will be deleted or archived. The following rules apply:
- If any rule says that the message is archived not deleted, the message will be flagged for archival
- If no expiry limit is set, the message will be handled according to the global settings
- If more than one expiry limit is set, the latest expiry limit will apply
The Global setting can be found under Administration > Configuration > Message Storage Period.
In order to assess the most appropriate length of time for message storage it may help to set the number of days
storage to 0 (keep indefinitely) when first creating an interface and watch the interface activity for a few weeks.
This will enable administrators to gauge the number of messages received each day and the growth of the database.
The Message storage time can then adjusted appropriately.
Note: Messages received while "Store Messages For" is set to 0 will not have an expiry date.
If they need to be remove from the database they will need to be deleted manually.
© Kestral Computing P/L 2000-2015. HL7Connect v2.00-063 generated on 30-Nov 2015
Keywords: Storage, Message Expiry, Document Expiry, Expiry