| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | user id(+) | 0;1 | POINTER | 200 | B | The user at the time of the scan event. |
| .02 | patient id | 0;2 | POINTER | 2 | The patient (if known) involved in the scan event. This information may automatically be derived from user supplied data. | |
| .03 | uas event location | 0;3 | FREE TEXT | The location where the scan event occurred. The attempt to scan should be at the patient's bedside, therefore this patient's location data is derived from the patient's file. | ||
| .04 | uas event date/time | 0;4 | DATE-TIME | ASFDT | Date and time the scan event documentation occurred. | |
| .05 | uas type(+) | 0;5 | SET OF CODES | MUAS:MEDICATION UNABLE TO SCAN WUAS:WRISTBAND UNABLE TO SCAN MKEY:MEDICATION KEYED ENTRY WKEY:WRISTBAND KEYED ENTRY MMME:MEDICATION MAN MED ENTRY MSCN:MEDICATION VIA SCANNER WSCN:WRISTBAND VIA SCANNER | The type of scan event. The value stored is one of a FileMan set. The value that is placed here is determined by the user's actions when attempting to scan a medication/wristband during an administration. Those types beginning with the "M" are events dealing with medications; those beginning with "W" are events with wristbands. "*UAS" occur when the user actually uses the "unable to scan" functionality to document the activity. "*SCN" are types that occur during normal scanning activities. The "*KEY" designate a type of event where the user has by-passed the BCMA scanning system by "keying", via the system's keyboard device, BCMA input data. | |
| .06 | uas reason | 0;6 | FREE TEXT | When documenting an "Unable To Scan Event", the user must select an approximate reason as to why the usual BCMA scanning system must be bypassed. That "Unable To Scan Reason" is stored in this field. These are the values available in the GUI application for this field: Damaged Medication Label Damaged Wristband Dose Discrepancy Inactive Patient Manual Medication Entry No Bar Code Scanning Equipment Failure Unable to Determine | ||
| .07 | uas e-message id | 0;7 | POINTER | 3.9 | A MailMan message will be sent per documented Unable To Scan Events. That message is referenced by this field, confirming a "given notice" of the Unable To Scan event and documentation. | |
| .08 | order number | 0;8 | FREE TEXT | This field logs the Pharmacy Patient order number of the order involved in the Unable To Scan event, if the order number is available and pertinent. | ||
| .09 | entered comment | 1;1 | FREE TEXT | Optional comment entered by the user when documenting a BCMA Unable To Scan event. | ||
| 10 | dispense drug | 2;0 | MULTIPLE | 53.771 | The dispensed drug from the order associated with the UTS event. | |
| 11 | additive | 3;0 | MULTIPLE | 53.7711 | List of additives from the order associated with the UTS event. | |
| 12 | solutions | 4;0 | MULTIPLE | 53.7712 | The list of solutions contained in the medication associated with the UTS event. | |
| 13 | unique item id | 0;9 | FREE TEXT | This field will document the identifier of the IV bag associated with the unable to scan event. This item cannot be identified via a specific medication identifier since an IV is made up of one or more Solutions and one or more Additives. | ||
| 14 | iv orderable item | 5;1 | FREE TEXT | This field is to document the Orderable Item assigned to the IV bag that is contained in the order that is associated with the unable to scan event. | ||
| 15 | orderable item name | 5;2 | FREE TEXT | The Orderable Item Name of the medication that is contained in an order that is associated with the UTS event. When the medication only contains a solution with no additive, the Orderable Item Name will include both the Pharmacy Orderable Item and the Dosage Form. |
Not Referenced