ECRI Alerts Module Business Rules

• A TMS database might be configured to handle all alerts from the System segment by entering an ECRI Institute Organization ID for the shared segment.

• A TMS database might be configured to handle alerts only in the user segments.  Each user segment will require its own ECRI Institute Organization ID.

• Once received in TMS, an ECRI Institute Alert can be closed in TMS if it is found to be not applicable to the available segments.

• TMS users must be associated with ECRI Institute logins in order to access the ECRI Alerts Module.

• For this functionality to perform as designed for a given asset, the asset must have a UMDNS device code entered as the Asset Sub Category code and a Sourcebase manufacturer code entered as the manufacturer.

• When this functionality is appropriately enabled, TMS will produce a list of assets in the TMS database which match the UMDNS device code and Sourcebase manufacturer code indicated on received ECRI Institute Alerts and email this list to configured email addresses.

• Alerts for which work orders have been created in TMS can only be closed in the Alert Tracker.

• TMS will poll ECRI Institute for updated information on a configurable basis.  TMS will also be able to get the latest information from ECRI Institute on demand.

• The on demand access to ECRI Institute information will follow the same rules as the polling behavior.

• Users must login using the login service and get the GUID to access all the other services.  Users from TMS can only set the status to "Applicable-Open" or "Not Applicable."

Codes for Alert Status

• Applicable Open – "AO" (Case-sensitive)

• Not Applicable – "NA" (Case-sensitive)

Codes for Action Taken

• Issued Work Order – "IWO" (Case-sensitive)

• No Action Taken – " " (Empty string)