STANDARD DATA DICTIONARY #53.77 -- BCMA UNABLE TO SCAN LOG FILE 3/24/25 PAGE 1
STORED IN ^PSB(53.77, *** NO DATA STORED YET *** SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 3.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
The Bar Code Medication Administration (BCMA) Unable to Scan Log file is to contain information pertaining to BCMA Scanning and
BCMA scanning "failures". This file has been created in effort to support refinement of the BCMA scanning process and BCMA
scanning equipment.
DD ACCESS: @
RD ACCESS: @
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
APPLICATION GROUP(S): PSB
CROSS
REFERENCED BY: UAS EVENT DATE/TIME(ASFDT), USER ID(B)
53.77,.01 USER ID 0;1 POINTER TO NEW PERSON FILE (#200) (Required)
LAST EDITED: NOV 12, 2008
HELP-PROMPT: The user at the time of the scan event.
DESCRIPTION:
The user at the time of the scan event.
CROSS-REFERENCE: 53.77^B
1)= S ^PSB(53.77,"B",$E(X,1,30),DA)=""
2)= K ^PSB(53.77,"B",$E(X,1,30),DA)
53.77,.02 PATIENT ID 0;2 POINTER TO PATIENT FILE (#2)
LAST EDITED: NOV 12, 2008
HELP-PROMPT: The patient involved in the scan event.
DESCRIPTION: The patient (if known) involved in the scan event. This information may automatically be derived
from user supplied data.
53.77,.03 UAS EVENT LOCATION 0;3 FREE TEXT
INPUT TRANSFORM: K:$L(X)>50!($L(X)<1) X
LAST EDITED: NOV 06, 2008
HELP-PROMPT: The patient location at the time of scan event.
DESCRIPTION: 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.
TECHNICAL DESCR:
File #2 Field# .1 _ "/" _ File #2 Field # .101
53.77,.04 UAS EVENT DATE/TIME 0;4 DATE
INPUT TRANSFORM: S %DT="ESTR" D ^%DT S X=Y K:X<1 X
LAST EDITED: NOV 14, 2008
HELP-PROMPT: The date and time at which the scan event occurred.
DESCRIPTION:
Date and time the scan event documentation occurred.
CROSS-REFERENCE: 53.77^ASFDT
1)= S ^PSB(53.77,"ASFDT",$E(X,1,30),DA)=""
2)= K ^PSB(53.77,"ASFDT",$E(X,1,30),DA)
This an index to maintain MSF log file (53.77) entries, by date/time.
53.77,.05 UAS TYPE 0;5 SET (Required)
'MUAS' FOR MEDICATION UNABLE TO SCAN;
'WUAS' FOR WRISTBAND UNABLE TO SCAN;
'MKEY' FOR MEDICATION KEYED ENTRY;
'WKEY' FOR WRISTBAND KEYED ENTRY;
'MMME' FOR MEDICATION MAN MED ENTRY;
'MSCN' FOR MEDICATION VIA SCANNER;
'WSCN' FOR WRISTBAND VIA SCANNER;
LAST EDITED: NOV 06, 2008
HELP-PROMPT: The type of scan event that was recorded.
DESCRIPTION: 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.
53.77,.06 UAS REASON 0;6 FREE TEXT
INPUT TRANSFORM: K:$L(X)>30!($L(X)<1) X
LAST EDITED: NOV 06, 2008
HELP-PROMPT: The UTS reason recorded at the time of the scan event.
DESCRIPTION: 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
53.77,.07 UAS E-MESSAGE ID 0;7 POINTER TO MESSAGE FILE (#3.9)
LAST EDITED: OCT 27, 2008
HELP-PROMPT: The MailMan message ID of the sent message for the UTS event.
DESCRIPTION: 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.
53.77,.08 ORDER NUMBER 0;8 FREE TEXT
INPUT TRANSFORM: K:$L(X)>11!($L(X)<2) X
LAST EDITED: NOV 14, 2008
HELP-PROMPT: The order number and type from the Pharmacy Patient file.
DESCRIPTION: 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.
TECHNICAL DESCR: The order number from Pharmacy Patient, with a "U" or "V" appended to specify an order type of Unit
Dose or IV order. This is only recorded if the order number is available and meaningful to the UTS
event. Because of the appended letter, this is not a pointer strictly speaking.
For unit dose orders, the order number is recorded in Pharmacy Patient (File 55) at the level:
^PS(55,D0,5,D1,0)= (#.01) ORDER NUMBER [1N] ^ The order type is at the same level in field 4, TYPE.
For IV orders, the order number is recorded in Pharmacy Patient (File 55) at level:
^PS(55,D0,"IV",D1,0)= (#.01) ORDER NUMBER The order type is at the same level in field .04, TYPE
53.77,.09 ENTERED COMMENT 1;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>250!($L(X)<1) X
LAST EDITED: NOV 07, 2008
HELP-PROMPT: The user comment for the event, up to 250 characters in length.
DESCRIPTION:
Optional comment entered by the user when documenting a BCMA Unable To Scan event.
TECHNICAL DESCR: This field contains comments from two sources. The system generates messages to document certain
events, such as use of the five rights mechanism to administer a medication. The end user can also
enter a comment from the client application. If both are entered, both will display, system comment
first. System comments are enclosed in brackets.
53.77,10 DISPENSE DRUG 2;0 POINTER Multiple #53.771
DESCRIPTION:
The dispensed drug from the order associated with the UTS event.
53.771,.01 DISPENSE DRUG 0;1 POINTER TO DRUG FILE (#50)
LAST EDITED: NOV 14, 2008
HELP-PROMPT: The dispensed drug IEN associated with the UTS event.
DESCRIPTION:
The dispensed drug IEN associated with the UTS event.
CROSS-REFERENCE: 53.771^B
1)= S ^PSB(53.77,DA(1),2,"B",$E(X,1,30),DA)=""
2)= K ^PSB(53.77,DA(1),2,"B",$E(X,1,30),DA)
53.771,1 DRUG NAME 0;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>60!($L(X)<1) X
LAST EDITED: OCT 27, 2008
HELP-PROMPT: The dispensed drug name associated with the UTS event.
DESCRIPTION:
This is the drug name associated with the Dispense Drug.
53.77,11 ADDITIVE 3;0 POINTER Multiple #53.7711
DESCRIPTION:
List of additives from the order associated with the UTS event.
53.7711,.01 ADDITIVE 0;1 POINTER TO IV ADDITIVES FILE (#52.6)
LAST EDITED: OCT 27, 2008
HELP-PROMPT: The additive associated with the UTS event.
DESCRIPTION:
The IEN of the additive associated with the UTS event.
CROSS-REFERENCE: 53.7711^B
1)= S ^PSB(53.77,DA(1),3,"B",$E(X,1,30),DA)=""
2)= K ^PSB(53.77,DA(1),3,"B",$E(X,1,30),DA)
53.7711,1 ADDITIVE NAME 0;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>60!($L(X)<1) X
LAST EDITED: OCT 27, 2008
HELP-PROMPT: The name of the additive that is associated with the UTS event.
DESCRIPTION:
The name of the additive that is associated with the UTS event.
53.77,12 SOLUTIONS 4;0 POINTER Multiple #53.7712
DESCRIPTION:
The list of solutions contained in the medication associated with the UTS event.
53.7712,.01 SOLUTIONS 0;1 POINTER TO IV SOLUTIONS FILE (#52.7)
LAST EDITED: NOV 07, 2008
HELP-PROMPT: The solution IEN associated with the UTS event.
DESCRIPTION:
The list of solutions contained in the order associated with the UTS event.
CROSS-REFERENCE: 53.7712^B
1)= S ^PSB(53.77,DA(1),4,"B",$E(X,1,30),DA)=""
2)= K ^PSB(53.77,DA(1),4,"B",$E(X,1,30),DA)
53.7712,1 SOLUTION NAME 0;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>60!($L(X)<1) X
LAST EDITED: NOV 07, 2008
HELP-PROMPT: The solution name in the medication that is associated with the UTS event.
DESCRIPTION:
Name of the solution contained in the medication that was Unable to Scan.
53.77,13 UNIQUE ITEM ID 0;9 FREE TEXT
INPUT TRANSFORM: K:$L(X)>30!($L(X)<1) X
LAST EDITED: NOV 16, 2008
HELP-PROMPT: The ID associated with an IV medication that is UTS.
DESCRIPTION: 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.
TECHNICAL DESCR: The IV Unique ID is stored in the 10th "^" piece of the BCMA Medication Log File. The specific
field is #.26, IV UNIQUE ID. The pointer to the BCMA Medication Log File is not retained in this
global, so it is not stored a a pointer.
If the IV Unique ID contains the letters "WS", then the IV bag was created during ward stack
activity.
The IEN for the BCMA Medication log entry for the IV Unique ID can be located using the "AUID"
cross reference:
^PSB(53.79,"AUID",PATIENT ID,ORDER NUMBER,IV UNIQUE ID,IEN)=""
53.77,14 IV ORDERABLE ITEM 5;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>32!($L(X)<1) X
LAST EDITED: NOV 24, 2008
HELP-PROMPT: The IV orderable item ID for the IV order associated with the UTS event.
DESCRIPTION: 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.
53.77,15 ORDERABLE ITEM NAME 5;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>71!($L(X)<3) X
LAST EDITED: APR 06, 2010
HELP-PROMPT: Enter the name of the orderable item (3-71 characters) that is associated with the UTS event.
DESCRIPTION: 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.
TECHNICAL DESCR: The Orderable Item Name entry can be located in file # 50.7 by using the value of field 14 of this
file as a pointer. We are storing the value rather than pointing to it for historical purposes. We
do not want this field to change if there is a change in file # 50.7. Our goal is to store the
value at the time of the UTS event. When the medication only contains a solution with no additive,
the Orderable Item Name will be the Name (#.01) field of the Pharmacy Orderable Item file (#50.7)
followed by a blank character followed by the Name (#.01) field from the Dosage Form (#50.606)
file. The Dosage form can be located in file # 50.606 by using the value of field .02 of the # 50.7
file as a pointer.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
FILES POINTED TO FIELDS
DRUG (#50) DISPENSE DRUG:DISPENSE DRUG (#.01)
IV ADDITIVES (#52.6) ADDITIVE:ADDITIVE (#.01)
IV SOLUTIONS (#52.7) SOLUTIONS:SOLUTIONS (#.01)
MESSAGE (#3.9) UAS E-MESSAGE ID (#.07)
NEW PERSON (#200) USER ID (#.01)
PATIENT (#2) PATIENT ID (#.02)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):