MedicationAdministrationRecordAlertComplianc
This table stores metric compliance information for alerts from the MAR. Each MAR alert has one row in this table. Only alerts with types of wrong order scanned; inactive order scanned; different dose than the ordered dose; short-term cumulative dose; additional dose on a completed, expired, or discontinued medication; off-schedule; and multiple required scans warnings are included. Various alert attributes are stored here to allow reports to show the metrics grouped by these attributes and gather details about individual alerts.
| Column Name | Type | Description |
|---|---|---|
| EncounterTypeCategory | VARCHAR | The encounter type category number for the encounter. Use this column to filter out outpatient encounters. |
| AlertUniqueIdentification | NUMERIC | The unique ID of the alert record. |
| AlertCausedOrderPlacementIndicator | NUMERIC | Indicates whether a No Order for Patient alert (34570) or an Order for Wrong Patient alert (34571) caused an order to be placed. If an order for the scanned medication that triggered the alert is placed for the same patient encounter within 1 hour of the alert, then this alert is considered to have caused an order to be placed. In that case, the column stored the value 1. Otherwise, this column stores the value 0. The medication is matched on the exact medication ID or the full GPI for the barcoded medication and ordered medication. |
| IsPossibleOverride | NUMERIC | If this alert is a scanning alert and there was a Medication Not Scanned alert within 5 minutes for the same patient and user, then this alert is considered to have been possibly overridden. In this case, this column stores the value 1. Otherwise, it stores the value 0. |
| AlertWasOverriddenFlag | NUMERIC | If the user chose to override the alert, this column stores the value 1. Otherwise, it stores 0. |
| AlertContactSerialNumber | NUMERIC | A unique serial number for this alert. This number is unique across all alerts in the system. If you use IntraConnect, this is the Unique Contact Identifier (UCI). |
| PatientEncounterContactSerialNumber | NUMERIC | The contact serial number for the patient encounter in which the alert was fired. This number is unique across all patients and encounters in your system. If alerts are triggered in a patient-specific encounter, they are saved in a corresponding encounter. This can be used to join to PAT_ENC.PAT_ENC_CSN_ID to get the encounter information. |
| PatientIdentification | VARCHAR | The unique ID of the patient for whom the alert fired. This column is frequently used to link to the PATIENT table. |
| AlertDateTime | DATETIME | The date the alert occurred. |
| ScannedMedicationIdentification | NUMERIC | For alerts resulting from a barcode scan of a medication, this column stores the unique ID of the medication scanned. For all other alerts, this column stores the unique ID of the medication entered in the order associated with this alert. |
| IsPossibleDuplicateAlert | NUMERIC | If this alert is a scanning alert and it occurred within 5 minutes of another alert of the same type for the same patient and user, then this alert is considered a possible duplicate. In this case, this column stores the value 1. Otherwise this column stores the value 0. |
| ScannedOrderIdentification | NUMERIC | The unique ID of the order scanned for alerts resulting from a barcode scan of an order. For all other alerts, this column stores the unique ID of the order associated with this alert when possible. |
| AlertTypeCategory | INTEGER | The category value of the type of this alert. |
| AlertAcknowledgedOrOverriddenDatetime | DATETIME | The instant when the user acknowledged or overrode the alert. |
| AlertTriggeringUserIdentifier | VARCHAR | The unique ID associated with the user who triggered this alert. This column is frequently used to link to the CLARITY_EMP table. |