Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  All
Print Page as PDF
Global: ^PSB(53.77

Package: Barcode Medication Administration

Global: ^PSB(53.77


Information

FileMan FileNo FileMan Filename Package
53.77 BCMA UNABLE TO SCAN LOG Barcode Medication Administration

Description

Directly Accessed By Routines, Total: 2

Package Total Routines
Barcode Medication Administration 2 PSBOSF    PSBOST    

Accessed By FileMan Db Calls, Total: 2

Package Total Routines
Barcode Medication Administration 2 PSBOSF    PSBVDLU3    

Pointer To FileMan Files, Total: 6

Package Total FileMan Files
Pharmacy Data Management 3 IV ADDITIVES(#52.6)[#53.7711(.01)]    IV SOLUTIONS(#52.7)[#53.7712(.01)]    DRUG(#50)[#53.771(.01)]    
Kernel 1 NEW PERSON(#200)[.01]    
MailMan 1 MESSAGE(#3.9)[.07]    
Registration 1 VA PATIENT(#2)[.02]    

Fields, Total: 15

Field # Name Loc Type Details
.01 USER ID 0;1 POINTER TO NEW PERSON FILE (#200)
************************REQUIRED FIELD************************
NEW PERSON(#200)

  • 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)
.02 PATIENT ID 0;2 POINTER TO VA PATIENT FILE (#2) VA PATIENT(#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.
.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
.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.
.05 UAS TYPE 0;5 SET
************************REQUIRED FIELD************************
  • '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.
.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





.07
UAS E-MESSAGE ID
0;7
POINTER TO MESSAGE FILE (#3.9)
MESSAGE(#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.





.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





.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.





10
DISPENSE DRUG
2;0
POINTER Multiple #53.771
53.771
  • DESCRIPTION:  
    The dispensed drug from the order associated with the UTS event.





11
ADDITIVE
3;0
POINTER Multiple #53.7711
53.7711
  • DESCRIPTION:  
    List of additives from the order associated with the UTS event.





12
SOLUTIONS
4;0
POINTER Multiple #53.7712
53.7712
  • DESCRIPTION:  
    The list of solutions contained in the medication associated with the UTS event.





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)=""





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.





15
ORDERABLE ITEM NAME
5;2
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<3) X
  • LAST EDITED:  NOV 19, 2008
  • HELP-PROMPT:  The name of the orderable item 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.
  • 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 the time of the UTS event.







    



Info | 
Desc | 
Directly Accessed By Routines | 
Accessed By FileMan Db Calls | 
Pointer To FileMan Files | 
Fields | 
All