This patch addresses the issue of one-time meds showing up on the Virtual
Due List from previous movements and even previous admission. As released
the VDL will search back 30 days for one-time orders and display them on
the VDL if there is no associated administration in the BCMA medication
log. With this patch the VDL will now only go back as far as the current
movement eliminating one-time orders from showing up from previous
movements and admissions.
Patch PSB*1*9 contains the following:
[PSBO WA] option is a combination of data that consists
Corrective Action: The user is now able to mark a medication as
NOT GIVEN at the "Admin Status:" prompt in the Edit Medication
Log [PSB MED LOG EDIT] option and it appears correctly on the MAH.
12. Problem: Large volume IV's do not print on the Due List [PSBO DL]
option.
Corrective Action: The Due List [PSBO DL] option has been corrected
to display large volume IV's.
of the ward location and the Room-Bed. When this combination of
13. Modification: Added the COMMENT field (#.3) from the BCMA MEDICATION
LOG file (#53.79) to the Medication Variance Log [PSBO MV] option.
E3R - 13732 and 14810
14. Modification: The message text the VDL displays when a patient has no
orders have been modified. When there are no orders in VISTA for a
selected patient the message, "No Active Orders at this Time" will be
displayed. If there are orders in VISTA, but they do not fall within
the start and stop times selected on the VDL the message,
"No Meds to be Administered for the Time Period Selected!" will be
data exceeds 32 characters it causes the report to print skewed.
displayed. If no schedule types are selected on the VDL the message,
"No Schedule Type(s) Selected!" will be displayed.
E3R - 14680
15. Modification: The process of Auto-update has been added to the BCMA
functionality. Auto update is the process of automatically copying
updated BCMA files from a server network drive to a client.
The prompts "The UNC of the Auto-update Server" and "Autoupdate
Notification Mail Group" have been added to Edit Divisional Parameters
[PSB PARAMETERS] option.
Please read the ReadMe.txt file found in your BCMA directory for a
full description on the GUI update functionality.
Corrective Action: The ward location and Room-Bed will now print
on separate lines.
3. Problem: The "Missing Dose Printer" prompt did not display on the GUI
BCMA Site Parameters.
Corrective Action: The GUI BCMA Site Parameters has been
corrected to display the "Missing Dose Request Printer" prompt.
4. Problem: When BCMA generates an error message to pharmacy because it
cannot determine the schedule. It displays the orderable item number
instead of the name. Below is an example.
Order Number....: 570U
Orderable Item..: 1695 <=====
Patient.........: XXXXXX,SAMUEL (000 00 0000)
1. Problem: The Virtual Due List (VDL) will only display the first
Reason..........: Unable to determine schedule 2X/WEEK
Corrective Action: The error message has been corrected to display
the orderable item name instead of the number.
Order Number....: 570U
Orderable Item..: DIGOXIN TAB <======
Patient.........: XXXXXX,SAMUEL (000 00 0000)
Reason..........: Unable to determine schedule 2X/WEEK
additive and solution for an Intravenous (IV) order.
5. Problem: The following occurs when trying to print a Due List
from the Due List [PSBO DL] option with a patient who has
the same last name and last four digits of the SSN as another patient.
When the last initial and last four digits of the SSN are entered
it displays two choices.
1 M6383 MOUSE,MICKEY 11-13-48 XXXXX6383
2 M6383 MOUSE,MINNIE 4-3-36 XXXXX6383
CHOOSE 1-2: 1
The following question is then asked:
There is more than one patient whose last name is 'MOUSE' and
whose social security number ends with '6383'.
Are you sure you wish to continue (Y/N)? Y
When this question is answered, the Due List screen shifts down
one line, skewing the screen.
Corrective Action: The Due List [PSBO DL] option screen has
Corrective Action: The VDL will now display all additives, strengths,
been corrected to not skew when there is a multiple patient match.
6. Problem: The user receives the following error message when
attempting to start a PRN Piggyback. "Error(s) Filing Transaction
MEDPASS. Business Logic Error: PRN Medications MUST Have a PRN
Reason". The user is then unable to mark it as started.
Corrective Action: The GUI VDL has been corrected to allow
a user to mark a PRN Piggyback as started.
solutions, and volumes for each IV order.
7. Problem: User receives an undefined error when using the Missing Dose
[PSBO MD] option.
Corrective Action: The error was resolved by performing a KILL on the
D0 variable.
8. Problem: An IV order with a status of on call will not
display on the VDL.
Corrective Action: The VDL has been corrected to display IV's with
a status of on call.
9. Problem: When scanning a drug with more than 6 units per dose, only 6
units display in the "MULTIPLE DOSES TO SCAN" GUI window.
Corrective Action: The "MULTIPLE DOSES TO SCAN" window has been
corrected to show and scan more than 6 units of a medication.
10. Problem: When a user leaves the "Print to DEVICE:" prompt blank
within the Due List [PSBO DL] option the user receives a "NULL
2. Problem: The Room-Bed displaying on the Ward Administration Times
SUBSCRIPT" error.
Corrective Action: The "Print to DEVICE:" prompt has been changed
to be a required prompt.
11. Problem: When a user deletes the date and time from an order already
given within the Edit Medication Log [PSB MED LOG EDIT] option, the
medication still appears as given on the Medication Administration
History report (MAH).
Patch PSB*1*10 contains the following:
VDL is opened on Tuesday.
12. Problem: An undefined variable error is generated in the
Missing Dose Report [PSBO MD] option when searching for
an MAS ward.
Corrective Action: The code has been modified to properly
loop through the MAS ward locations and not generate an
error.
13. Problem: If a patient has an 2 orders with the same orderable
item and 2 different dispense drugs, the Ward Administration
Times [PSBO WA] option will only print the first order on
the report.
Corrective Action: The Ward Administration Times [PSBO WA]
option has been corrected to display both orders.
14. Problem: If the administration time and the Virtual Due List
Parameters Start Time: are equal to 2400, the dose would
not display on the VDL.
Corrective Action: BCMA has been modified to no longer
Corrective Action: The VDL has been modified to properly display
the 2400 medication.
15. Problem: An odd schedule order will only print the first two digits
of the administration time on the Due List [PSBO DL] option.
Corrective Action: Odd schedule administration times will now print
military time on the Due List [PSBO DL] option.
16. Problem: If an odd schedule order calculates an administration
generate an error messages to the due list error notification
time to be 2400. The GUI VDL will display "3030@3010" in the
"Admin Time" column.
Corrective Action: The calculated admin time for midnight dose
will now properly display 2400 in the "Admin Time" column.
17. Problem: If an order contained an odd schedule greater than
24 hours, the subsequent doses would not display on the VDL.
For example, if an order has a schedule of Q36H only the first
dose would display on the VDL.
mail group when the VDL is opened on a non scheduled
Corrective Action: BCMA has been modified to properly calculate
the subsequent doses for an odd schedule greater than 24 hours.
18. Modification: The Label Print [PSBO BL] option has been
modified to validate the drug requested for printing and the
patient's current orders. If a drug is selected to print
that the patient does not have a current order on. The
following message will display
administration day.
"Patient not currently on medication: XYZ Med (Qty: 1)"
Do you want to continue?
E3R Number: 13809
19. Modification: When the user performs a right-click on the VDL,
the Start IV status on the VDL has been modified to Start.
20. Modification: The GUI BCMA Site Parameters has been updated to include
the following; Default Bar Code Format, Default Bar Code
Prefix, Using Robot Rx, Allow Multiple Administration for On-Call,
UNC of the Auto Update Server, Auto Update Notification,
Default Prompt for INCL TRANSFERS, One Time Parameter.
The Edit Divisional Parameters [PSB PARAMETERS] option will no
longer be updated or maintained. All future enhancements and
modifications will be made on the GUI BCMA Site Parameters.
21. Modification: The Missing Dose Request [PSB MISSING DOSE REQUEST]
option was modified to prompt the user for the dosage schedule.
In the BCMA MISSING DOSE REQUEST file (#53.68), the SCHEDULE field
2. Problem: The patient's weight displayed in the patient
(#.19) has been added as a required field to store the schedule
information.
22. Modification: The Missing Dose Report [PSBO MD] option was
modified to display the dosage schedule.
E3R Number: 13030
23. Modification: The Missing Dose Request [PSB MISSING DOSE REQUEST]
option was modified to display the patient's social security number
(last four digits), ward location, and room/bed information in the
demographic box on the GUI VDL was incorrect.
e-mail message sent to the missing dose notification mail group.
E3R Number: 12780
24. Modification: Modified the right click 'Display Order'
accelerator key to 'O' to match accelerator key on menu option.
Modified the right click 'Drug IEN Code' accelerator
key to 'D' to match accelerator key on menu option.
Accelerator keys enable the user to access a menu command
from the keyboard by pressing Alt+ the appropriate letter.
E3R Number: 15291
25. Modification: The (MAH) [PSBO MH] option has been modified
to display an asterisk with the initial if a student
administered a medication. In the legend section on the MAH
report, this asterisk will correspond to the student and the
instructors initials, names, and date/time the medication
was given.
E3R Number: 14609
Corrective Action: The calculation for the patient's weight has
26. Modification: The (MAH) [PSBO MH] option has been modified
to print an "***" in the date column when an order is discontinued.
E3R Number: 13413/13852
been modified.
3. Problem: If a drug contains a future inactive date, the Label
Print [PSBO DL] option will not print the drug.
Corrective Action: The Label Print [PSBO DL] option has been modified
to adhere to the future inactive date and print according to the date
entered.
1. Problem: Orders with a day of the week schedule are generating
4. Problem: When a medication has been given and then the dispense
drug has been changed on the order, the VDL will display the
new dispense drug on the already given medication.
Corrective Action: The VDL has been modified to properly display
any changes in dispense drugs on an order.
5. Problem: User received an undefined error when altering a medication
status in Edit Medication Log [PSB MED LOG EDIT] option.
false error messages to the due list error notification mail
Corrective Action: The Edit Medication Log [PSB MED LOG EDIT] option
has been modified to not generate an undefined error, by using
standard coding logic.
6. Problem: The Medication Administration History (MAH) [PSBO MH] option
generates a null subscript error when the nurse or pharmacist initials
are not present.
Corrective Action: The MAH [PSBO MH] option has been modified to not
generate an error when the nurse or pharmacist initials are not
group. This occurs when the Virtual Due List (VDL) is opened
entered. The report will print without the initials.
7. Problem: Orders which contain an odd schedule were not printing on the
Missed Medications [PSBO MM], Ward Administration Times [PSBO WA]
and the Ward Administration Times [PSBO WA] reports.
Corrective Action: The reports have been modified to print
odd schedule orders.
8. Problem: The Last Action column on the Virtual Due List is not
on a day the order is not scheduled to be administered.
displaying the four digit year.
Corrective Action: The Virtual Due List has been modified to display
the full four digit year.
9. Problem: In reference to the Medication Variance Log [PSBO VR]
option, a site noticed that this report indicates only the patient
current ward location when the report is generated. Although the
patient may have received several administrations of medications on
different wards, the report does not denote the patient specific
location when the medication was administrated. The lack of this
information made it difficult for providers to track down the
locations that had irregularities in the administration of medications
to the patients.
Corrective Action: Modifications were made to the Medication Variance
Log [PSBO VR] option to allow the report to display the patient
location associated with each event date/time the medication was
administrated to the patient.
For example, an order with a schedule of MO-WE-FR
10. Problem: Intravenous (IV) orders with a schedule of one-time
generate a "Data Validation Error: 701: The value '.143022'
for field ORDER ADMINISTRATION TIME in file BCMA MEDICATION LOG
is not valid" error when trying to mark them as started.
Corrective Action: BCMA has been modified to allow one-time
IV orders to be marked as started without generating an error.
11. Problem: The VDL is displaying an incorrect message when a medication
will generate an error message to the mail group if the
is marked as held. For example, when a medication is marked as held
and the user tries to mark the next medication as given, the message
"*** NOTICE, Aspirin was given 2 minutes ago" is being displayed.
Corrective Action: The message has been updated to properly
reflect the change in status. The new message displayed in the
above example is;
"*** NOTICE, Aspirin was HELD 2 minutes ago"
A problem was found in PSB*1*10 with how the Bar Code Medication
to the BCMA MISSING DOSE REQUEST file (#53.68) storing the external
room-bed value.
Corrective Action: The Missing Dose Report [PSBO MD] option was
corrected by properly storing the internal room-bed value in
the BCMA MISSING DOSE REQUEST file (#53.68).
2. Problem: Orders that contain administration times (0900-1500) as
a schedule do not display on the VDL. When a
user tries to access the BCMA VDL, a MailMan message will be sent
Administration (BCMA) Virtual Due List (VDL) processes orders with
to the Due List Error Notification Mail Group for the pharmacist
to correct the order. The message that is generated is stated below:
"No Admin time required for non-standard schedules."
Corrective Action: The VDL has been corrected to properly display
orders that contain an administration time (0900-1500) as a schedule.
3. Problem: When printing the Missed Medications [PSBO MM] option report
by ward, there would be no truncation between data. This resulted in
data overlapping, making the report unreadable.
certain schedules. Below are the listed problems found with PSB*1*10.
Corrective Action: To display all the data in a readable format, the
Missed Medications [PSBO MM] option report has been modified by
removing the ward location as a column. The ward location still
displays as a header.
4. Problem: Orders that contain a standard day of the week schedule
(i.e. MO-TU@0900) that are in the ADMINISTRATION SCHEDULE file (#51.1)
do not display properly on the VDL.
Please note: PSB*1*10 should not be removed. PSB*1*15 has been developed
Corrective Action: The VDL has been corrected to properly display
standard day of the week schedules.
5. Problem: IV Piggyback orders that contain a standard schedule (Q8H)
with no frequency defined in the ADMINISTRATION SCHEDULE file #(51.1)
do not display on the VDL.
Corrective Action: The VDL has been corrected to properly display these
these types of orders.
to address these problems.
1. Problem: The Missing Dose Report [PSBO MD] option is generating an
illegal number error when a user tries to run the report. This was due
1. A site reported a problem where a one-time order could not be
system parameter is not defined, the system will use the continuous order
parameters to determine the stop date, rather than the start and stop
date being equal. Then, when BCMA marks the medication as 'Given',
Inpatient Medications will expire the order. NOIS# BUT-0501-20609.
2. Manual Medication Entry [PSB MED LOG NEW ENTRY] option was generating a
false Due List Error Notification message when accessed.
BCMA V. 1.0 has been corrected to no longer generate an e-mail message.
NOIS# NOP-0801-11096
discontinued by the provider because it was expired due to the start and
CTX-0801-72721
This project consists of a master build containing three patches that
work together to accomplish these goals listed in order of install.
Installation of this master build should be coordinated among the three
packages affected since only one installation is necessary. The patches,
in order of install, are:
PSS*1*44 PHARMACY DATA MANAGEMENT V. 1.0
PSJ*5*63 INPATIENT MEDICATIONS V. 5.0
stop date being the same. However, the medication still displayed in Bar
PSB*1*13 BAR CODE MEDICATION ADMINISTRATION V. 1.0
Code Medication Administration (BCMA) V. 1.0 because of the 12-hour rule
for displaying one-time orders on the Virtual Due List. This patch
corrects this problem by changing the way the one-time orders is
calculated. There will be a ward parameter, system parameter and the
standard calculation. The hierarchy will be to check the one-time ward
parameter first, if not defined, check the system parameter. If the
Patch PSB*1*14 contains the following:
2. Problem: In reference to the Missing Dose Request Report [PSB MISSING
DOSE REQUEST] option, the dosage schedule was added to the report
in PSB*1*10; however, each medication order was counted or
displayed individually. The sites would like the report to
display a sum of identical medication orders.
Corrective Action: Modifications were made to display the sum of
medication orders that was identical and had an identical dosage
schedule.
3. Problem: When a user selects to sort or print The Medication Variance
Log [PSBO MV] option by ward, the report displays the variance
information for all Wards. The site would like the report to
display only the variance information related to the Ward selected
via ScreenMan.
Corrective Action: Modifications were made to the option to display
only the variance information related to the selected Ward.
1. Problem: The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT] option
4. Problem: If the user enters in an old date (i.e. 1/21/1931), when
running the Due List [PSBO DL] option, Bar Code Medication
Administration (BCMA) generates an undefined variable error.
Corrective Action: The Due List [PSBO DL] option does not generate
an error when an old date is entered.
5. Problem: If an order was placed with a schedule of Q3MONTHS, it would
display on the Virtual Due List (VDL) everyday.
did not properly refresh after entering an effectiveness past the
Corrective Action: The VDL was corrected to display an order with
a schedule of Q3MONTHS, once every 3 months.
6. Problem: The word missing is misspelled in the report header of the
Missing Dose Followup [PSB MISSING DOSE FOLLOWUP] option. The header
displays "Currently Unresolved Mising Dose Requests"
Corrective Action: The misspelled word has been corrected.
7. Problem: The Missed Medications [PSBO MM] option report does not
allowed time.
display the first dose for an odd schedule.
Corrective Action: The Missed Medications [PSBO MM] option report
has been modified to properly display the first dose for an odd
schedule.
Corrective Action: The refresh command was added to the menu option
to properly display the screen.
Y2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved
printing the station number in front of the Internal Entry Number (IEN)
on the ZEBRA barcode labels. As released labels would print only the
IEN as a barcode for the selected medication. After this patch labels
will be formatted as SiteNumber-IEN if the parameter PSB DEFAULT BARCODE
SITE is set to yes.
2. Use a different server name for the monthly SAGG reporting. Sites will
notice no change with the SAGG update.
Old Server: KMP1-BCMA-SERVER@ISC-ALBANY.DOMAIN.EXT
This patch may be installed during the Y2K Moratorium, either
New Server: KMP90-BCMA-SERVER@ISC-ALBANY.DOMAIN.EXT
3. Further enhancements were done so the One-Time medications do not
appear on the Virtual Due List by discontinuing the order without having
to mark the order as 'Do Not Give'.
*************************************************************************
NOTICE: This patch is released prior to a Y2K Waiver and can only be
installed in a TEST environment until a waiver is received. Upon
granting of the waiver a message will be sent to all sites informing them
BEFORE 12/15/99 or AFTER 1/15/2000.
that this patch may be moved to live.
*************************************************************************
This patch MAY NOT be installed between 12/15/1999 and 1/15/2000
(the Y2K Lockdown Period).
This patch contains 3 improvements.
1. Sites that are scheduled to integrate with a primary site can begin
Y2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved
2. Problem: User input dates in VA Fileman format not accepted by BCMA.
Corrective Action: BCMA was modified to accept and store user inputted
dates in a VA Fileman format.
3. Problem: The administration times report on the GUI Virtual Due List
will only display a 24 hour period, even if a time range is selected.
Corrective Action: The administration times report on the GUI Virtual
This patch may be installed during the Y2K Moratorium, either
Due List was made consistent to the administration times report on the
CHUI by removing the administration time fields.
4. If BCMA has been designated to be used for QA and testing purposes
only, a notification will be displayed when starting BCMA.
5. Problem: If the Client/Server clock variance was greater than the
acceptable limit defined in the PSB Parameters, the Virtual Due List
would display the PC time.
BEFORE 12/15/99 or AFTER 1/15/2000.
Corrective Action: Server/Client clock variance corrected to display
server time.
6. Required functionality added: Means Test Check Alert.
7. Mandatory Security Check - The Director, Health Information Management
Headquarters, and VA General Counsel have requested modifications to patient
look-up functionality in VistA. This request results from a grievance filed by
employees that cites non-compliance with the Employee Privacy Act System of
Records. The citation states that employee Social Security Number(SSN) and
Patch PSB*1.0*3 contains the following fixes:
Date of Birth (DOB) data is presented without soliciting the information from
the system and without notification to appropriate site personnel that this
information has been accessed.
1. Problem: Orphan jobs were left running due to a disconnect in
communication between the server and client.
Corrective Action: Incorporate RPC Broker patch XWB*1.1*6 to allow
orphan jobs to die.
2. Problem: The Missed Medications [PSBO MM] option does not print
Corrective Action: The software has been corrected to not generate an
error.
15. Problem: When running the MAH report, the initials of the nurse who
administered a PRN, on-call and one-time do not print on the report.
Corrective Action: The MAH report has been corrected to properly print
the initials of the nurse who administered an PRN, on-call, and
one-time.
one-time orders.
16. Problem: When running the MAH report, one-time orders outside the date
range are being printed.
Corrective Action: One-time orders will display within selected date
range on the MAH report.
17. Problem: If no action was taken on a one-time order, they would stay
on the VDL for 30 days.
Corrective Action: One-time orders with no action will now drop off
the VDL after 12 hours.
Corrective Action: The Missed Medications [PSBO MM] option will
now print missed one-time orders on the report.
3. Problem: The stop date on the Due List is not recognized when a date is
entered.
Corrective Action: The Stop Date prompt has been removed from the Due
Patch PSB*1.0*4 contains the following fixes:
List.
4. Problem: BCMA did not accept a dosage which contained decimals
(i.e.,0.01)
Corrective Action: BCMA has been corrected to accept a dosage which
contains a decimal.
5. Problem: Medications marked as "Do not give" and "Discontinued" are
printing on the Due List.
Corrective Action: Medications marked as "Do not give" and
"Discontinued" will no longer print on the Due List.
6. Problem: When on-call's are chosen to print on the Due List the
report would print one-times. When one-times are chosen
the report would print on-call's.
Corrective Action: The Due List will now properly print one-times
and on-call's.
1. Problem: An undefined error was generated when running the Medication
7. Problem: The user is unable to document the administration of a
one-time order through the Manual Medication Entry
[PSB MED LOG ENTRY] option.
The message "Error: OKAY to give" 'press return to continue or
^ to exit', would display. No further action can be taken
at this point.
Corrective Action: One-time orders can now be properly documented
through the Manual Medication Entry [PSB MED LOG ENTRY] option.
Administration History (MAH) report.
8. Problem: Within the Edit Divisional Parameters [PSB PARAMETERS] option,
"Allowed Mins Before Sched Admin" would allow the administration of a
medication to be administered based on the minutes prior to an
"Administration Time."
Corrective Action: The functionality of the question has been changed
to allow the administration of a medication based on the number
of minutes prior to the "active time" of an order.
9. Problem: Within the Edit Log Medication [PSB MED LOG EDIT] option ,
a nurse was unable to edit his or her own administration record if
another nurse made an entry to that medication.
Corrective Action: The Edit Log Medication [PSB MED LOG EDIT] option
has been modified to allow a nurse to edit his or her own
administration entries.
10. Problem: Within the Edit Divisional Parameters [PSB PARAMETERS] option
the user was not able to determine which division they had signed on
Corrective Action: The BCMA Software was corrected to not pass an
too.
Corrective Action: The Edit Divisional Parameters [PSB PARAMETERS]
option will now see the following message displayed: "You are
currently logged onto Division: XXX", with XXX being the division
you are logged onto.
11. Problem: On the GUI Virtual Due List (VDL) when the nurse administers
a PRN medication, the previous four PRN administrations are displayed
with the message "Okay to administer - Brief Administration History"
undefined variable, thus not generate an error.
Corrective Action: The display message has been changed to now read
"Brief Administration History".
12. Problem: On-call and PRNs medications would display on the GUI VDL
even if they were not active.
Corrective Action: The GUI VDL will not display an on-call or PRN
order until it has become active.
13. Problem: Within the Label Print [PSBO BL] and Drug File Inquiry
[PSB DRUG INQUIRY] options, the Drug selection would allow the display
and selection of inactive drugs and those marked for other packages.
Corrective Action: The Drug Selection prompt will only display
active rugs and those marked for packages "I" and "U".
14. Problem: When attempting to run the Medication Administration Log
[PSBO ML] option, an error is generated due to incomplete data.
1. Problem: Sites using the Robot Rx are having difficulty with
1.1 The DRUG file #50 cannot contain a synonym that is 16 or 18
2. Problem: Sites which are attempting to integrate are concerned that
the current prompt "Include Site Number" within Edit Divisional
Parameters[PSB PARAMETERS] option may have duplicates numbers at
other sites.
Corrective Action: The prompt "Include Site Number" has been changed
to "Default Barcode Prefix". This will allow each site to enter in
a one to five alphanumeric prefix instead of just the site's prefix.
3. Problem: The GUI Virtual Due List (VDL) does not wrap the "Dosage",
digits in length and begins with a "3". If matches to this
cutting off the dosage display.
Corrective Action. The GUI Virtual Due List has been corrected to
properly wrap the "Dosage".
4. Problem: If a user defines a reason under Reasons a Med is
given PRN, beginning with a numeric value, the GUI Virtual Due List
would display the actual number of the reason, instead of the text.
Please see NOIS HAM-0100-22249 for an example.
pattern exist, they must be changed to a different format.
Corrective Action: The GUI Virtual Due List has been corrected to
properly display the PRN reason defined.
5. Problem: Non-verified medications are printing on the Missed
Medications Report.
Corrective Action: The Missed Medications Report
has been modified to exclude non-verified medications.
6. Problem: When administering an injectable drug from the VDL, you are
Once these are changed, new synonyms matching this format
first prompted with the "Enter Quantity and Units" screen.
Once this screen is completed, the "Injection Site Needed" screen
appears. If you press cancel, the medication entry is logged as given
and no injection site is filed with an entry.
Corrective Action: The VDL has been modified to make injectable site
a required field.
7. Problem: An error "Exception Elist error in module VCLX40.BPL AT
0001A9FS" is generated in GUI when the following scenario occurs.
cannot be entered while using Robot Rx. To search for
The user scans a drug that comes in 5mg doses and patient needs
10mg dose. The user scanned the medication once, then used the
touch screen to make the second check mark on the second dose.
Corrective Action: The dosage screen has been modified to require the
second dose to be scanned in, instead of manually marked.
8. Problem: Scan a PRN that requires an amount to be entered such as an
injection or a cream. The "Enter Quantity and Units" window comes up
and the user enters the amount and hits enter. Next the "Medication
possible matches in the DRUG file #50, please follow
Log" screen is displayed and the user then realizes they incorrectly
entered the amount, so the cancel button is pressed. The "Medication
Log" screen is displayed and says "Order Administration Cancelled"
The user hits enter then scans the med again. The "Enter Quantity
and Units" screen doesn't come up again, but skips straight to the
"Medication Log" and keeps the quantity and units from the first scan.
Corrective Action: When cancel is chosen, BCMA will now properly
cancel out.
these steps.
9. Problem: There are inconsistencies when marking IV's
as held or refused.
Corrective Action: IV's can be marked as started, held or
refused.
10. Problem: The Missing Dose Followup [PSB MISSING DOSE FOLLOWUP] option
would not stop scrolling if more than 14 medications were present.
This did not give the user the ability to select the appropriate dose.
Corrective Action: The Missing Dose Followup [PSB MISSING DOSE
FOLLOWUP] option will now properly scroll, allowing the user the
ability to select a dose.
11. Problem: Within the Drug File Inquiry [PSB DRUG INQUIRY]option,
if an inquiry is done on a drug that has 50 or more characters
in the MESSAGE: field, the screen locks and the process needs to
be stopped.
Corrective Action: The Drug File Inquiry [PSB DRUG INQUIRY]option
has been corrected to no longer lock up if text is greater than 50
characters.
12. Modification: Display the initials and name of the nurse on the
Medication Administration History (MAH) [PSBO MH] option.
13. Modification: The MAH now displays the status of "HOLD".
14. Problem: The Missing Dose Request [PSB MISSING DOSE REQUEST], option
would allow the user to select an inactive drug.
a) Access VA FileMan
Corrective Action: The Missing Dose Request [PSB MISSING DOSE REQUEST]
option has been modified to prevent the selection of inactive drugs.
15. Problem: When the administration time and the stop time for a
continuous order are the same, the system would calculate the
last dose as a dose to be given. Please see example below, were the
last dose of 1900 was calculated because the stop time was 1900.
(1)Orderable Item: MINERALS/MULTIVITAMINS TAB
Bar Code Medication Administration (BCMA) reading the barcode.
Instructions:
(2)Dosage Ordered: 1 TAB (3)Start: 02/10/00 11:43
(4) Med Route: ORAL (5)Stop: 02/10/00 19:00
(6) Schedule Type: CONTINUOUS (7) Self Med: NO
(8) Schedule: Q2H
(9) Admin Times: 01-03-05-07-09-11-13-15-17-19-21-23
(10) Provider: BUNNY,BUGS
(11) Special Instructions: FOR 3 DOSES
This order will display 4 doses on the VDL.
b) Select OPTION: 3 SEARCH FILE ENTRIES and enter in the
Corrective Action: BCMA has been corrected to calculate the
appropriate doses when the stop time and administration
time are the same.
16. Problem: The scanner ready status was inconsistent.
Corrective Action: The scanner status is in a ready status during
most functions in BCMA.
17. Problem: The "Allowed Mins to Enter PRN Effect" prompt within the Edit
=
Divisional Parameters [PSB PARAMETERS] option was being stored
incorrectly.
Corrective Action: The "Allowed Mins to Enter PRN Effect" prompt is
now being stored correctly.
18. Problem: An error occurred when cancelling the GUI BCMA log on.
Corrective Action: The error has been corrected.
information as it appears below.
19. Modification: The full version number for BCMA GUI is now located in
the About BCMA.
20. Problem: If a medication has a med route of intradermal, the injection
site box will not appear on the VDL during administration.
Corrective Action: The injection site box will now appear on the VDL
when intradermal is the med route for a medication.
21. Problem: The following scenario would not generate the message ** NO
SPECIFIED MEDICATIONS TO PRINT **" on the Due List. If a user
choose to print the Due List for a specified schedule and there are no
medications for that particular schedule, but other medications exist
for other schedule types.
Corrective Action: The report was corrected to properly display
the message ** NO SPECIFIED MEDICATIONS TO PRINT **" when there
are no medications to print for the specified schedule type.
OUTPUT FROM WHAT FILE: DRUG//
22. Problem: Users are unable to identify old one-time orders on
Missed Medications [PSBO MM] option.
Corrective Action: The start date/date for a one-time order has been
added to the Missed Medication Report.
====
-A- SEARCH FOR DRUG FIELD: 9 SYNONYM (multiple)
=
-A- SEARCH FOR DRUG SYNONYM SUB-FIELD: .01 SYNONYM
*If your site is not using the Robot Rx system,
===
-A- CONDITION: 3 MATCHES
=
-A- MATCHES: 1"3"15E
=======
-B- SEARCH FOR DRUG SYNONYM SUB-FIELD: .01 SYNONYM
===
-B- CONDITION: 3 MATCHES
=
-B- MATCHES: 1"3"17E
please skip section 1.
=======
-C- SEARCH FOR DRUG SYNONYM SUB-FIELD:<RET>
-C- SEARCH FOR DRUG FIELD:<RET>
IF: A DRUG SYNONYM MATCHES 1"3"15E
=
DO YOU WANT THIS SEARCH SPECIFICATION TO BE CONSIDERED
TRUE FOR CONDITION
-A-
1) WHEN AT LEAST ONE OF THE 'SYNONYM' MULTIPLES SATISFIES IT
2) WHEN ALL OF THE 'SYNONYM' MULTIPLES SATISFY IT
CHOOSE 1-2: 1// 1
=
OR: B Or DRUG SYNONYM MATCHES 1"3"17E
=
DO YOU WANT THIS SEARCH SPECIFICATION TO BE CONSIDERED
TRUE FOR CONDITION
-B-
1) WHEN AT LEAST ONE OF THE 'SYNONYM' MULTIPLES SATISFIES IT
Corrective Action: The BCMA software has been modified to recognize
2) WHEN ALL OF THE 'SYNONYM' MULTIPLES SATISFY IT
CHOOSE 1-2: 1// 1
=
OR:
STORE RESULTS OF SEARCH IN TEMPLATE:
SORT BY: GENERIC NAME// <RET>
START WITH GENERIC NAME: FIRST//<RET>
FIRST PRINT FIELD: .01 GENERIC NAME
the Robot Rx barcode format. In order for BCMA to function with
===
THEN PRINT FIELD: SYNONYM (multiple)
=======
THEN PRINT SYNONYM SUB-FIELD: .01 SYNONYM
===
THEN PRINT SYNONYM SUB-FIELD: <RET>
THEN PRINT FIELD: <RET>
Heading (S/C): DRUG SEARCH//<RET>
DEVICE: 0;80;999 ***
DRUG SEARCH MAR 13,2000 09:57 PAGE
Robot Rx, please follow the directions in the order listed below.
GENERIC NAME SYNONYM
--------------------------------------------------------------------------
ACETAMINOPHEN 325MG TAB APAP
TYLENOL
ACET325
000677000100
051111048893
305111104882120100
1 MATCH FOUND.
1.2 A new prompt "Using Robot Rx" has been added to
Edit Divisional Parameters [PSB PARAMETERS]option.
The user should answer Yes to thE question when they
are now ready to use Robot Rx.
Patch 6 contains the following modifications:
GUI would allow freetext.
Corrective Action: The "reason needed" field will not accept freetext.
3. Problem: The "Last Given" column is updated each time an action
occurs, including refused and held. This can be confusing to the
user since a medication marked as held will also show a date and
time in the last given column.
Corrective Action: The "Last Given" column will be changed to "Last
Action". The last status will also be displayed in the column next to
the date and time.
1. Problem: The verifying nurse initials are not displayed on the Virtual
Due List (VDL).
Corrective Action: The VDL has been modified to display the verifying
nurse initials.
2. Problem: The "reason needed" field on the missing dose screen on the
1. Installing Bar Code Medication Administration (BCMA) on a network
The file roboex32.dll is typically installed into the
c:\windows\system directory or (for Windows NT machines)
the c:\winnt\system32 directory.
C. Share the BCMA directory on the file server. Optionally, the
directory can be set to READ ONLY via the shared directory
properties. In a Windows NT environment, NTFS file
security can be set to further secure this directory.
Additionally, a login script file can be created that will
automatically map the network drive each time a
drive.
user logs in. This helps in the event that a user accidentally
disconnects from the network drive.
2. Pointing the client PC/laptop to the file server.
A. Map each laptop or client PC to the network drive mentioned in the
previous step.
B. Create an icon that points to the file bcma.exe (on the network
drive). Via the icon's properties, set up the necessary command
line parameters to connect to your VistA system.
Using this method, no BCMA files are required on the local client's PC.
When it is time to install the next BCMA GUI patch, have all users log out
of BCMA, install the patch on the file server that is sharing the files
and the upgrade will be complete.
The above installation instructions will only work with patch PSB*1*3 or
later. Previous patches require additional files to be moved to the
shared BCMA directory.
A. To install BCMA on a network drive, install BCMA on the file server
that will perform the file sharing. BCMA is typically installed into
c:\program files\vista\bcma.
B. Perform a file search on the file server to locate the file
roboex32.dll. Copy this file to the file server's BCMA directory.
Patch PSB*1*7 contains the following:
display the nurse's initials when a one-time has been marked
as refused.
9. Problem: Within the Due List [PSBO DL] option, the "On Call:"
prompt will not save the users settings upon exit.
The field defaults to "No" after the user has exited the option.
Corrective Action: The "On Call:" prompt has been modified
to save the users settings upon exiting the option.
2. Problem: A user is unable to distinguish identical one-time
10. Problem: If a medication order has 2 or more units per dose, BCMA will
display the Multiple Doses to Scan screen to allow the user
to scan the second, third, etc doses. If a nurse enters an Internal
Entry Number (IEN) for the second dose and did not press ENTER,
but immediately pressed DONE, the IEN entered would not be marked as
Given.
Corrective Action: Validation is now performed on any text entered
in the "Scan Medication Bar Code" prompt, regardless if the user
pressed ENTER or not.
orders on the Virtual Due List (VDL), when multiple identical
11. Problem: If a user double clicks on an IV order on the VDL, the
"Dosage Ordered:" prompt would display data.
Corrective Action: The "Dosage Ordered:" prompt has been
corrected to not display any data on the VDL if an IV is order.
12. Problem: If a patient has an IEN of "1" from
the PATIENT file (#2) the VDL would generate the error
"RPC ERROR GETORDERLIST" and not display any orders.
one-time orders exist.
Corrective Action: The VDL has been corrected to not error
with a patient who has an IEN of "1".
13. Problem: If a medication is marked as held or refused through the
Manual Medication Entry [PSB MED LOG NEW ENTRY] option, the
MAH report displays the entered date/time, not the
administered date/time.
Corrective Action: The MAH has been corrected to display the
administered date/time instead of the entered date/time.
14. Problem: The Ward Administration Times [PSBO WA] option was
printing medications for incorrect days. For example, if the
medication had a schedule of MO-WE-FR and the report was
printed on Tuesday, the medications for MO-WE-FR would print
on the report.
Corrective Action: The Ward Administration Times [PSBO WA] option
has been corrected to properly print the medications for the correct
Corrective Action: The pop up box, Multiple Orders for Scanned Drugs,
days.
15. Problem: If BCMA is writing to the BCMA MEDICATION LOG file (#53.79)
and an MAH is run a "NULLSUBSCRIPT" error is generated.
Corrective Action: The code has been corrected by using
standard coding conventions.
16. Modification: The "Room/Bed:" prompt has been added to the
Missing Dose Request [PSB MISSING DOSE REQUEST] option.
will now display the Type, Active Medication, Special Instructions,
17. Modification: The "MED ROUTE:" prompt has been added to the
Due List [PSBO DL] option.
18. Modification: The ward location and room-bed have
been added to the BCMA-Order Problem e-mail message.
19. Modification: The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT]
option has been modified to display the ADMINISTRATION MEDICATION
field (#.08) from the BCMA MEDICATION LOG file (#53.79).
Dosage, Schedule, Route, Admin Time, Last Action, and Start
20. Modification: BCMA GUI has been modified to allow column resizing.
Any changes to the column settings will be saved, allowing the user
to re-enter the GUI to the saved settings. The original column
settings can be reset through the Reset User Parameters
[PSB USER PARAM RESET] option.
21. Modification: The Patient Medication Log in GUI has been modified to
display the INCLUDE COMMENTS field (#.28) and the INCLUDE AUDITS
field (#.29). All comments and audits are now viewable through the
date/time for each order. To select the correct order for
GUI.
22. Modification: The Missed Medications [PSBO MM] option and the Ward
Administration Times [PSBO WA] option have been modified to
not display self-medications.
23. Modification: The Medication Administration Log [PSBO ML] option
has been modified to display the START DATE/TIME field (#10).
24. Modification: The ORDER NUMBER field (#.01) has been added to the
administration, highlight the order and then click the OK button.
Missed Medications [PSBO MM] option.
25. Modification: The Missed Medications [PSBO MM] option will only
print one-time medications within the last movement date.
26. Modification: The BCMA GUI screen can now be maximized to fit the
entire screen.
27. Modification: The Manual Medication Entry [PSB MED LOG NEW ENTRY]
option has been modified to display the history of the last four
administrations for a PRN order.
28. Modification: The patient record locking functionality has been
removed, allowing multiple sessions of BCMA to be opened for one
patient.
29. Modification: New key functions.
Shift-Tab - Takes focus off the Scan Medication Bar Code
to the VDL, allowing the user to scroll up and down the
3. Problem: Users were unable to print reports to a slave device within
VDL orders. Press the Enter key to display a highlighted
order.
Right Click - on a selected order and select Display
Order to view detailed order information.
ALT-D,O - Displays detailed order information.
Select Due List [PSBO DL] option, then select
Display Order - To view detailed order information.
all Bar Code Medication Administration (BCMA) CHUI options.
F4 - To view detailed order information.
F5 - Refresh the VDL.
CTRL,O - To open a new patient.
30. Modification: The GUI VDL has been modified to shut down when
a "PSB GETORDERLIST" error is encountered. When such an error is
encountered the VDL would display "No Active Orders". This information
is a result of the broker returning no information. This modification
prevents the user from viewing a VDL with false information when
such an error is generated.
31. Modification: The GUI Broker has a timeout value called
RPCTimeLimit as defined in the quoted text below:
Description
This property is a public integer property that is available at
Corrective Action: BCMA CHUI has been modified to allow the printing
run-time only. It specifies the length of time a client will
wait for a response from an RPC. The default and minimum value of
this property is 30 seconds.
If an RPC is expected to take more than 30 seconds to complete,
adjust the RPCTimeLimit property accordingly. However, it is not
advisable to have a RPCTimeLimit that is too long. Otherwise,
the client-end of the application will appear to "hang", if the
server doesn't respond in a timely fashion.
The BCMA default has been changed from 30 seconds to 60 seconds.
of reports to a slave printer.
This can be changed with the new command line parameter of 'T' for
timeout.
Your command line might look as follows:
"D:\Program Files\vista\Bcma\BCMA.exe" S=BGHAM P=9307 T=30
Any value below 30 seconds will be disregarded.
4. Problem: When entering an order through the Inpatient Order
Entry [PSJ OE] option, for a drug that has a units per dose
of 1, it is not necessary to manually enter a 1 in the
1. Problem: An undefined variable PSBSTRT error is generated
"UNITS PER DOSE:" prompt. If the user chooses to bypass the
"UNITS PER DOSE:" prompt field entry, the system will default
to a 1. When the user elects to view the order detail on the
VDL by double clicking on the order, the" Units" prompt
is left blank.
Corrective Action: The VDL has been corrected to properly display
a 1 in the UNITS PER DOSE field (#.02), when a user views the
detail order information.
within the PRN Effectiveness List [PSBO PE] option when
5. Problem: The wording for the prompts listed below within menu
Edit Divisional Parameters [PSB PARAMETERS] option were incorrect.
Corrective Action: The following prompts have been changed in
the PARAMETER DEFINITION file (#8989.51) in the DISPLAY TEXT
field (#.02).
From: To:
Include Blank Addendums at end Default prompt for INCL BLANKS <Y/N>
Include Continuous Meds Default prompt for INCL CONT <Y/N>
the user chooses a hospital location instead of a nursing
Include IV Med Orders Default prompt for INCL IV MEDS <Y/N>
Include On Call Meds Default prompt for INCL ON-CALL <Y/N>
Include One-Time Meds Default prompt for INCL ONE-TIME<Y/N>
Include PRN Meds Default prompt for INCL PRN <Y/N>
Include Unit Dose Med Orders Default prompt for INCL UD MEDS<Y/N>
6. Problem: Medication orders that have an ODD Schedule do not
display on the VDL. An ODD Schedule is a schedule that is not
evenly divisible by 24 hours (Q18H or Q7H).
location at the "Ward Location:" prompt.
Corrective Action: BCMA has been modified to accept and display ODD
Schedule types on the VDL.
If your site plans on using ODD Schedules, please read the
following NOTES.
***NOTE*** When ordering medications with an ODD Schedule,
DO NOT enter a time into the "ADMIN TIMES:" prompt when placing an
order within the Inpatient Order Entry [PSJ OE] option.
BCMA will automatically calculate the administration time to the
minute, based on the start date/time of the order. If you want the
administration time to display to the nearest hour, edit the
"START DATE/TIME:" prompt field to be on the hour.
For example if the start time is at 0837 for a Q5H, the
administration times will be at 0837, and at 1337. To display the
order on the VDL on the hour, edit the start time to be at 0800.
***NOTE*** If a time is entered at the "ADMIN TIMES:" prompt when
placing an order for an ODD Schedule, that administration time is
Corrective Action: The PRN Effectiveness List [PSBO PE] option
when the medication will be displayed on the VDL everyday.
For example, if an order is placed with a schedule
of Q5H with an administration time of at 0900. The order will appear
on the VDL at 0900 everyday. Do not enter administration times
if you want ODD Schedules to function properly.
***NOTE*** ODD Schedules are NOT to be entered in the ADMINISTRATION
SCHEDULE file (#51.1)
7. Problem: No data is being displayed under the columns U/Ord and U/Gvn,
has been corrected to not error if a hospital location is chosen.
within the medication log report when an IV is ordered.
Corrective Action: The medication log report has been modified to
display "N/A" in the two columns for IV orders.
8. Problem: The Medication Administration History (MAH) report
does not display the nurse's initials when a one-time is marked
as refused.
Corrective Action: The MAH report has been modified to
Patch PSB*1*11 contains the following:
2. Modification: This patch includes a new API between Inpatient
Medications and Bar Code Medication Administration
(BCMA) (Integration Agreement #3174).
The entry point EN^PSBIPM is provided by the Bar Code Medication
Administration (BCMA) package to provide information to Inpatient
Medications to be used in determining the start date for a renewed
order.
The new API will:
a. Pass the ORDER ADMINISTRATION TIME field (#.13) of the BCMA
MEDICATION LOG file (#53.79).
b. Pass the ADMINISTRATION DATE/TIME field (#.06) of the BCMA
MEDICATION LOG file (#53.79).
c. Pass the ADMINISTRATION STATUS field (#.09) of the BCMA
MEDICATION LOG file (#53.79).
1. Problem: When attempting to chart a medication the user receives the
3. The PSBPOST post installation routine re-indexes the BCMA MEDICATION
LOG file (#53.79). The new subscript added is "AORDX".
following error.
310: The IENS> +10+1 conflicts with FDA.
Corrective Action: The error was resolved by performing a NEW command
on the variable PSBFDA.
2. Problem: Version 2.0 beta test sites experienced errors in
routines PSBMD and PSBVDLU1.
Corrective Action: The errors experienced in those routines have
been corrected.
3. Problem: With the installation of BCMA version 2.0, routine PSBIPM was
renamed to PSBAPIM.
Corrective Action: PSBIPM is no longer being used in version 2 and
1. Problem: If a medication is marked from given to not given to
will be removed with this patch.
4. Problem: With the installation of BCMA version 2.0, the Edit
Divisional Parameters [PSB PARAMETERS] option is no longer functional.
Corrective Action: The Edit Divisional Parameters [PSB PARAMETERS]
option will be removed with this patch. Any access to site parameters
needs to be made through the GUI BCMA Site Parameters application.
5. Problem: The Missed Medications [PSBO MM] option was generating
given, the Medication Administration History (MAH) [PSBO MH] option
the Due List Error Notification message, "No admin time required for a
Non-Standard schedule," on expired orders.
Corrective Action: The Missed Medications [PSBO MM] option will no
longer generate the message "No admin time required for a Non-Standard
schedule" on expired orders.
6. Problem: When an order has a schedule in the day of week format, and
had a frequency associated with it, the order was not displaying on
the Virtual Due List (VDL) on the days scheduled.
would display these actions as three separate administration actions
Corrective Action: An order with a schedule in the day of week format
and a frequency associated with it, will display correctly on the
VDL on the days scheduled.
7. Problem: The "Order Num" column was printing next to the "Medication"
column on the Missed Medications [PSBO MM] option. This caused some
confusion with the order number being interpreted as a dosage for
some medications.
of given, not given and given.
Corrective Action: The "Order Num" column was moved to be the
first column on the Missed Medications [PSBO MM] option.
8. Problem: The Edit Medication Log [PSB MED LOG EDIT] option allowed
a medication patch to be marked not given from removed.
Corrective Action: The Edit Medication Log [PSB MED LOG EDIT] option
has been modified to not allow a patch to be marked as not given
from removed.
9. Problem: One-time orders with a future start date/time would print
on the Missed Medications [PSBO MM] option.
Corrective Action: The Missed Medications [PSBO MM] option has been
corrected to only print one-time order when the order start date/time
is within the report start and stop date/time.
10. Problem: IV orders with a future start date and time would display
on the IV tab of the VDL before due.
Corrective Action: The MAH will now properly display these three
Corrective Action: The IV tab of the VDL has been modified to not
display IV order until the order start date and time has been reached.
11. Problem: The GUI generated an error when attempting to display
unit dose orders on the VDL.
Corrective Action: The VDL has been modified to properly display
unit dose orders on the VDL.
actions as one correct action.
Install this patch before installing Patch PSB*2*6. It will perform the
BCMA Order Problem Notification Started on JAN 7,2003@08:24:18.
This will let the user know the date and time the process started.
BCMA Order Problem Notification Finished on JAN 7,2003@08:30:47.
This will let the user know the date and time the process finished.
The person installing this patch will also receive a MailMan message
with the subject: BCMA Pre patch 6 - Order Problem Notification. This will
let the user know that PSB*2*6 will have a problem displaying an order,
same medication order validation as Patch PSB*2*6, and allows Pharmacists
which is identified in the message text. A separate MailMan message
will be generated for each Order Problem.
an opportunity to review "problem" medication orders before your site
installs PSB*2*6. Ensure that PSB*2*6 is installed immediately following
the correction of any problem medication orders. Failure to do so may
result in medication orders not displaying on the Virtual Due List (VDL).
The person installing this patch will receive two separate MailMan
messages with the following subjects:
***NOTE*** Do NOT install this patch until you receive the message
when to display a Continuous medication order on
LOG NEW ENTRY] option, the medication will not display on the VDL for
the nurse to mark it as "Removed."
Corrective Action: Medication orders with a dosage form of "PATCH"
given by a nurse using the Manual Medication Entry [PSB MED LOG NEW
ENTRY] option will now display on the VDL for the nurse
to mark them as "Removed."
12. Problem: The Admin Time column on the IVP/IVPB tab of the VDL is
displaying administration times of "0000" for odd schedule orders.
the Virtual Due List (VDL).
Corrective Action: The Admin Time column on the IVP/IVPB tab of
VDL will now display the correct time for an odd schedule order.
13. Problem: The data entered in the "Enter Quantity and Units" dialogue
box from the IVP/PB tab was not being stored in the medication log.
Corrective Action: The data is now being properly stored in the
medication log.
14. Problem: If a medication order is marked as "Not Given", the user is
unable to update the medication using the Manual Medication Entry
[PSB MED LOG NEW ENTRY] option.
Corrective Action: The user will now be able to update medication
orders that have been marked as "Not Given" using the Manual
Medication Entry [PSB MED LOG NEW ENTRY] option.
15. Problem: If a PRN medication order with the dosage form of "PATCH"
was marked as "Given", it would duplicate on the VDL. The user was
At the end of this installation a post install routine will clean up the
unable to mark the medication as "Removed."
Corrective Action: PRN medication orders with the dosage form of
"PATCH" will follow the "PATCH" business rule.
16. Problem: The Ward Administration Times report displays IV orders with
admin times based on the frequency calculated by IPM. The display of
large volume IV's on this report is confusing to the user.
Corrective Action: IV's with a IV type of Admixture, Hyperal, Syringe
BCMA Medication Log APATCH INDEX. The person installing the patch will be
Not Intermittent, Chemotherapy (Admixture), Chemotherapy (Syringe
Non-Intermittent) will not be displayed on this report.
17. Problem: A Schedule Type of "R" displays in the "Type" column on the
VDL for medication orders that have a dosage form of "PATCH" and
a previous Schedule Type of Fill on Request.
Corrective Action: The correct Schedule Type will display in the
"Type" column on the VDL.
notified the routine has completed successfully via a MailMan email with
18. Problem: A condition exists that causes a medication order to have
the same previous and following order number. Because of this
scenario, the BCMA application is put into an infinite loop or may
cause an error when the VDL is opened.
Corrective Action: In support of several NOIS tickets regarding this
issue, BCMA has implemented a temporary fix that now allows a
medication order with the same previous and following order number to
display on the VDL. This is not a comprehensive fix, but will allow
BCMA to function properly while Inpatient Meds researches the problem.
the subject line "BCMA APATCH INDEX CLEAN HAS COMPLETED".
19. Problem: A one-time medication order marked as "Missing,"
would not display on the Missed Medications [PSBO MM] option.
Corrective Action: A one-time medication order marked as "Missing,"
will now display on the Missed Medications [PSBO MM] option.
20. Problem: Day of the Week schedules that include the "@" sign followed
by a valid time do not display on the Virtual Due List.
Corrective Action: Day of the Week schedules in this format now
display correctly on the Virtual Due List.
1. Problem: The Medication Administration History [PSBO MH] option
"BCMA AADT X-REF CHECK COMPLETED" from the installation of PSB*2.0*9 and
displays medication orders beyond the requested report dates.
Corrective Action: The Medication Administration History [PSBO MH]
option now displays medication orders within the requested report
dates.
2. Problem: When a patient is discharged and reinstated, the MAH
displays "***" in the date column.
Corrective Action: The Medication Administration History [PSBO MH]
the message "BCMA Order Problem Notification Finished" from the
option has been modified to not display "***" in the Date
column for medication orders that have been discontinued and
then reinstated.
3. Problem: PRN last actions listed as "Not Given" display on the
Medication Log Information dialog box.
Corrective Action: The last four actions of a PRN medication order
will not display an action of "Not Given", in the Medication Log
Information dialog box.
installation of PSB*2.0*18. Installing this patch before receiving these
4. Problem: A medication order for a Patch displayed multiple
times on the VDL, if it was marked as "Given", then "Not Given"
and then "Given" again.
Corrective Action: A medication order for a Patch will display
appropriately, regardless of how many times an action has been
applied to the associated patch order.
5. Problem: After a patient receives a patch for the second time
messages may cause the Bar Code Medication Administration (BCMA) program
the "Last Action" column on the VDL displays the incorrect date and
time.
Corrective Action: The "Last Action" column will now display the
correct date and time for patches.
6. Problem: When an active IV order that has an infusing bag is edited
through Computerized Patient Record System (CPRS), via the "CHANGE"
action, the "old" order disappears from the BCMA VDL IV tab.
This prevents clinicians from knowing the status of the old order.
to error.
Corrective Action: Continue to display the status of an edited IV
order on the BCMA VDL IV tab.
7. Problem: The Missed Medications [PSBO MM] option generates
a "String too long" error message for medication orders that contain
a schedule in a minute's format (i.e., Q2').
Corrective Action: The Missed Medications [PSBO MM] option now
displays medication orders that contain a schedule using a minute's
format.
8. Problem: The Medication Administration History [PSBO MH] option
generates a "String too long" error message for medication orders
that contains a schedule in a minute's format (i.e., Q2').
Corrective Action: The Medication Administration History [PSBO MH]
option now displays medication orders that contain a schedule using a
minute's format. However, schedules with a frequency of less than 45
minutes will display the message "Due Every # Minutes", where # is the
This patch contains changes to how BCMA V. 2.0 processes schedule
frequency.
9. Problem: Ward Administration Times [PSBO WA] option generates
a "String too long" error message for medication orders that contain
a schedule in a minute's format (i.e., Q2').
Corrective Action: The Ward Administration Times [PSBO WA] option
now displays medication orders that contain a schedule using a
minute's format. However, schedules with a frequency of less than 30
minutes will display the message "Due Every # Minutes", where # is
information from Inpatient Medications V. 5.0, and how it determines
the frequency.
10. Problem: Medication orders that include a Day of the Week schedule
generate a false Due List Notification Error on a day not due.
Corrective Action: Medication orders that include a Day of the Week
schedule will no longer generate a false Due List Notification Error.
11. Problem: If a medication order with the dosage form of "PATCH" is
administered by a nurse using the Manual Medication Entry [PSB MED
1. Problem: The Medication Administration History [PSBO MH] option and
Corrective Action: The code has been modified to properly display
the patient's medication orders when accessing the VDL.
Manual Medication Entry [PSB MED LOG NEW ENTRY] option are generating
an undefined error, because of a missing orderable item name on a
medication order.
Corrective Action: The undefined error has been corrected.
2. Problem: Users are receiving an undefined variable error in routine
PSBVDLU1 when accessing the patient's medication orders on the VDL.
*** ATTENTION: This patch includes a new GUI.
orders are marked as "Refused."
Request" dialog box is now a required field.
13. Problem: The Right-Click feature used to access the "Take Action
on WS" command was not available for a ward stock IV bag marked as
"Held" on the VDL.
Corrective Action: The Right-Click feature used to access the "Take
Action on WS" command is now available for a ward stock IV bag marked
as "Held" on the VDL.
14. Problem: When users sign on to the BCMA GUI application, and are
prompted to scan the patient's wristband, a lower portion of the
screen display is grayed out.
Corrective Action: The GUI screen display has been corrected.
15. Problem: Reports would not print from the GUI application when
print devices had the same name.
Corrective Action: The GUI printing function has been modified to
Corrective Action: The GUI VDL will not apply the status of "Refused"
print reports to devices that have the same name.
16. Problem: A medication order with a schedule of "AC&HS," displays
on the BCMA VDL with a schedule of "ACHS."
Corrective Action: The GUI has been modified to properly display the
schedule.
17. Problem: The shortcut keys of "ALT+A" used to display "Allergies"
would go to the "Start Time:" field of the "Virtual Due List
to medication orders placed on Provider Hold when marking multiple
Parameters:" section of the VDL.
Corrective Action: The shortcut key for "Allergies" has been changed
to ALT-G.
18. Problem: If a medication order is created or edited using the
Manual Medication Entry [PSB MED LOG NEW ENTRY] option or the Edit
Medication Log [PSB MED LOG EDIT] option, the last action would
display incorrectly on the "Last Action" column of the VDL by
dropping off any trailing zero of the time from the date/time format.
medication orders.
Corrective Action: The last action for a medication order will now
display correctly under the "Last Action" column on the VDL.
19. Problem: Users who mark a PRN medication order, with the dosage
form of "PATCH" as "Given," cannot document a PRN effectiveness using
the Enter PRN Effectiveness [PSB MED LOG PRN EFFECT] option.
Corrective Action: Users can now document a PRN effectiveness for a
"Given" PRN medication order with a dosage form of "PATCH."
20. Problem: Under the IV Medication Tab, if a medication order gets
discontinued when a ward stock IV bag has a status of "Stopped," no
data would display under the "IV Bag Chronology."
Corrective Action: Data will correctly display under the "IV Bag
Chronology" display area when an IV order becomes discontinued and a
ward stock IV bag has status of "Stopped" status.
21. Problem: The Special Instructions pop-up box does not function on
2. Problem: Comments entered when a ward stock IV bag is completed
the IV Medication Tab when the Pharmacist enters an exclamation ("!")
to copy and flag the Provider comments for display in a BCMA
message dialogue box.
Corrective Action: The Special Instructions pop-up box will now
display on the IV Medication Tab when a Pharmacist finishes
an IV order and uses the "!" key to copy and flag the Provider
comments for display on the BCMA VDL.
22. Problem: The "ALLERGIES:" bar on the VDL displays "No allergies on
and another ward stock IV bag begins infusing, are carried from one IV
file" when no assessment was completed.
Corrective Action: The "ALLERGIES:" bar will now display "No Allergy
Assessment" if there are no allergies assessed and "No Known
Allergies"
if there is an allergy assessed, but no allergies.
bag to another.
Installation of this GUI is required in order to see the full
Corrective Action: Comments entered for an IV bag will not carry over
to the next IV bag.
3. Problem: The error message "Missing Data" sporadically displays on
the VDL when a user tries to administer a medication via the "CPRS Med
Order" button.
Corrective Action: The "Missing Data" message has been corrected.
4. Problem: The error message, "'.' Not a valid integer" sporadically
functionality of this patch. ***
displays when a user accesses a patient record on the VDL.
Corrective Action: The VDL has been corrected to not generate the
error message.
5. Problem: Any report printed from the GUI VDL, displays inactive
wards in the "Ward" field under the "Print by" section.
Correction Action: Inactive wards will no longer be available for
selection on reports printed from the GUI VDL.
6. Problem: A medication order with the dosage form of "PATCH" marked
as "Given" using the Manual Medication Entry [PSB MED LOG NEW ENTRY]
option, does not display on the VDL as "Given."
Corrective Action: Medication orders with a dosage form of "PATCH"
marked as "Given" using the Manual Medication Entry [PSB MED LOG NEW
ENTRY] option, will display on the VDL as "Given.
7. Problem: The "Provider:" field on the "Order Manager" dialog
For retrieval and installation instructions, please see the Client
screen does not display all valid Providers when performing a partial
lookup. This was a result of BCMA not validating the inactive date
correctly.
Corrective Action: The code has been modified to perform the
validation on the inactive date. The correct Providers will display
for selection under the "Provider:" field on the "Order Manager"
dialog screen.
8. Problem: Drugs with a future inactive date were not available for
Installation Instructions section.
printing on labels using the Label Print [PSBO BL] option.
Corrective Action: Drugs with future inactive dates are now available
for printing on labels.
9. Problem: BCMA does not perform a version check between the GUI
application and CHUI application side.
Corrective Action: BCMA will validate the version of the GUI
application running on the GUI against the CHUI application.
The client version must match the patch number on the VistA server,
and if compatible, the previous GUI version will be allowed to run.
GUI version will be allowed to run. No prior version will be allowed
to run on the client.
10. Problem: The current "Typical" installation process for the BCMA
GUI application installs both the BCMA client and the BCMA Site
Parameter application. This is not appropriate for an installation
a ward P.C.
1. Problem: Any order displayed as Provider Hold on the GUI Virtual
Corrective Action: The "Typical" installation process has been
modified to only install the BCMA client.
11. Problem: The action of marking multiple medications, as "Held" or
"Refused" does not always apply to every medication on the VDL. For
example, if a medication is already marked as "Given", the action of
"Held" or "Refused" will not apply to that medication order.
Corrective Action: If multiple medications are highlighted on the
VDL, and the action of "Held" or "Refused" does not apply to
Due List (VDL) is also marked as "Refused" when multiple medication
a highlighted order, an Informational dialog box will display with
the message, "Held or Refused will NOT be applied to the following
order(s):" with a list of orders.
12. Problem: The message "ERROR: MISSING DATA - ALL FIELDS ARE
REQUIRED," Missing Field: NEEDED BY DATE/TIME," displays when a user
selects the Missing Dose Followup [PSB MISSING DOSE FOLLOWUP] option,
to complete and save a request.
Corrective Action: The Date@Time Needed field on the "Missing Dose
1. BCMA will display a Notification Popup box, once per patient session,
2. BCMA will now document fractional dose medication orders, which occur
when a medication order contains a units per dose that is not a whole
number. When a user administers a fractional dose medication using BCMA,
a Multiple or a Fractional Dose dialog box will display for documenting
the actual amount and user comments.
3. Three fields have been removed from the Parameters tab of the BCMA Site
Parameters application since the functionality no longer exists. They
include the "General System Error:" field, the "Auto Update Notification:"
for the Unit Dose and IVP/IVPB Medication Tabs. The Popup box displays if
field in the Mail Groups section of the Parameters tab and
the "UNC of the Auto Update Server:" field in the Misc. Options section of
the Parameters tab.
a patient has had a recent movement, and at least one of the last actions
occurred within the specified timeframe defined in the "Patient Transfer
Notification Timeframe:" field on the Parameters tab of the BCMA Site
Parameters application. The Popup box will display the patient movement
type and transaction type within brackets, and the Virtual Due List (VDL)
will display the transaction type in the "Last Action" column for a
medication displayed on the VDL.
Problem: In reference to the Medication Variance Log [PSBO MV] option, a
LOG file (#53.78).
Problem: In reference to the Medication Variance Log [PSBO MV] option,
several sites are experiencing problems with displaying variance
information as a result of incompatible ward names stored in the
BCMA MEDICATION VARIANCE LOG file (#53.78). If the user selects a ward
name from the WARD LOCATION file (#42) that does not match the ward name
store in the BCMA MEDICATION VARIANCE LOG file (#53.78), the variance
log information will not display on the report.
functional discrepancy was discovered in the coding logic used to
Corrective Action: The Ward Name Conversion Process [PSB WARD CONV]
option was add to the Bar Code Medication Administration Manager
[PSB MGR] option to allow each site an opportunity to make the
appropriate corrections to incompatible ward, room and bed names stored
in their local BCMA MEDICATION VARIANCE LOG file (#53.78). The
following functions are incorporated in the Ward Name Conversion Process
[PSB WARD CONV] option:
extract previous variance information stored in the BCMA VARIANCE LOG
o Allow the user to select a specified date range to control the amount
time needed to complete the process and the amount data that will be
changed.
o Automatically, convert Ward Name to Ward IEN if the Ward Name in BCMA
MEDICATION VARIANCE LOG file (#53.78) is identical to the Ward Name in
the WARD LOCATION file (#42).
o Display a list of un-identifiable ward names to the user.
file (#53.78). The report will only show variance information related
o Allow the user to change the un-identifiable ward name to a ward name
stored in the NURS LOCATION file (#211.4) and select the appropriate
room and bed location.
o Send an e-mail message to the user when the Ward Name Conversion
Process is completed.
to patients currently assigned to the selected ward.
Resolution: Modifications were made to rebuild the data structure used
to sort, store, and display the variance information related to all
patients associated with the selected ward stored in the BCMA VARIANCE
NOTE: Patch PSB*2*12 makes changes to the ward-specific IV Parameters
bags on the Virtual Due List (VDL), regardless of the settings for the
patient's respective ward.
Corrective Action: The IV Parameters settings for the "ALL" ward affect
the display of a patient's IV bags VDL only when the settings are not
defined for the patient's respective ward. Please be aware that after you
install this patch, all ward-specific IV Parameters defined for wards
other than "ALL" will work immediately. These parameters control when an
IV bag is valid, and when BCMA warns a user the status of an IV order
has changed. If your site has defined ward-specific IV Parameters,
functionality included in the GUI BCMA Site Parameters application.
please review them BEFORE installing this patch, and notify the
appropriate personnel to ensure that problems are not experienced once
installed.
2. Problem: The PSB DEFAULT BARCODE PREFIX Site Parameter was set to
accept 1 to 5 characters so the user had to specify a prefix in the GUI
Bar Code Medication Administration (BCMA) Site Parameters application. If
none was specified, the barcode number was not recognized when the user
scanned a patient's medication for administration.
Please be sure to read the Problem and Corrective Action statements below
Corrective Action: The PSB DEFAULT BARCODE PREFIX Site Parameter has
been set to accept 0 to 5 characters, so the user does not need to
specify a prefix in the GUI BCMA Site Parameters application. When a
barcode is printed, no prefix is added to the barcode so the label scans
successfully during medication administration.
3. Problem: Changes made to the IV Parameters when using the GUI BCMA
Site Parameters application were not always being saved for the selected
division.
and coordinate the installation of this patch appropriately before
Corrective Action: Changes made to the IV Parameters when using the
GUI BCMA Site Parameters application are now being saved for the selected
division.
4. Problem: When the unit of administration is a patch and that patch
has a "Given" status, the BCMA Virtual Due List (VDL) displayed the last
action date/time of the order in the "Last Action" column. The VDL did
not display the last action date/time of the orderable item.
Corrective Action: When the unit of administration is a patch and
installing it. (See suggestion at bottom of Corrective Action please.)
the patch has a "Given" status, the BCMA VDL displays in the "Last
Action" column the last action date/time of the orderable item.
5. Problem: Text in the "U/Gvn" column of the BCMA Medication Log
Report did not provide word wrapping. This became apparent after
free-text 'quantity and units' data was entered during the administration
of a medication dose.
Corrective Action: After entering free-text 'quantity and units'
data during the administration of a medication dose, information in the
"U/Gvn" column of the BCMA Medication Log Report will appropriately word
wrap.
6. Problem: The following is an example of an error that occurred when
a user attempted to administer a unit dose medication with an "IV Push"
med route:
"^Error(s) Filing Transaction MEDPASS
Data Validation Error: 701: The value 'KCL 20MEQ/D5/NACL {2}'
for field UNIT OF ADMINISTRATION in SOLUTIONS SUB-FIELD in file BCMA
1. Problem: The GUI BCMA Site Parameters application, IV Parameters
MEDICATION LOG is not valid."
The above error occurred under particular conditions associated with the
IV solution.
Corrective Action: The user is able to administer unit dose
medications with an "IV push" medication route, regardless of the IV
solution.
settings for specific wards did function as required. The IV Parameter
settings for the "ALL" ward always affected the display of a patient's IV
1. Problem: The error message "Error(s) Filing Transaction MEDPASS"
file (#53.68), when the user enters a "@" in the "Patient Name:"
prompt.
Correction: The Missing Dose Request [PSB MISSING DOSE REQUEST] option
has been modified to not create an entry in the MISSING DOSE REQUEST
file (#53.68) file, when a user enters a "@" in the "Patient Name:"
prompt.
displays when the infusion rate for an IV Piggyback order includes more
than 30 characters.
Correction: The INFUSION RATE field (#.35) of the BCMA MEDICATION LOG
file (#53.79) was increased from 30 to 47 characters.
2. Problem: The Missing Dose Request [PSB MISSING DOSE REQUEST] option
is creating incomplete entries in the MISSING DOSE REQUEST
Problem: If there is a continuous order, with an admin times, and
corrections.
If a DUE LIST ERROR message is encountered with a Reason of "Invalid
frequency received from order" please do the following.
1. Determine if the schedule listed in the mail message is in FILE# 51.1
the ADMINISTRATION SCHEDULE FILE.
a. If it is not, Log a NOIS.
b. If it is, determine if the TYPE OF SCHEDULE is CONTINUOUS.
i. If it is not, log a NOIS.
the frequency is null, the GUI Bar Code Medication Administration (BCMA)
ii. If it is, determine if the frequency is a valid number
greater than zero.
1. If it is, log a NOIS.
2. If it is not, correct the frequency.
does not display the order on the Virtual Due List (VDL) and a Due List
Error Notification message is not generated.
Corrective Action: BCMA will generate a Due List Error Notification
message for those continuous orders that contain a standard schedule
with admin times and no frequency. This can also occur to non-standard
Schedules. Pharmacy should review the problem order and make necessary
Problem: When a Day of the Week schedule is created with [PSS SCHEDULE
EDIT] option, the order is showing as due everyday on the Virtual Due
List. The Ward Administration Times [PSBO WA] option and the Medication
Due List [PSBO DL] option displays the same problem.
Corrective Action: Day of the Week schedules displays correctly on the
Virtual Due List, Ward Administration Times [PSBO WA] option, and
Medication Due List [PSBO DL] option.
1. Problem: The "BCMA ORDER LAST ACTION:", which is displayed in order
more then two digits. Please see example below.
The value 0.125 for field DOSES GIVEN in dispense drug subfield in file
BCMA MEDICATION LOG IS NOT VALID
The value 0.125 for field DOSES ORDERED in dispense drug subfield in
file BCMA MEDICATION LOG IS NOT VALID
Corrective Action: BCMA has been modified to accept up to four
fractional digits for doses ordered and doses given.
view screen under Inpatient Medications V 5.0., was displaying the
last action by orderable item instead of the order number.
Corrective Action: The "BCMA ORDER LAST ACTION:" has been corrected to
display the last action by order number.
2. Problem: BCMA was generating the message below when a nurse
tried to administer a medication that had a fractional dose ordered of
1. Problem: The GUI Bar Code Medication Administration (BCMA) Site
2. Problem: The Medication History Report, which is available by
performing a right-click on an order from the BCMA Virtual Due List
(VDL), displays incorrect data for an IV medication order. This occurs
when an IV order contains more than one orderable item.
Corrective Action: The Medication History Report will now display the
medication history for each orderable item contained in an IV
medication order.
Parameters application does not perform a version check between the
3. Problem: A user can administer multiple patches for an On-Call
medication order, with a dosage form of "PATCH," without the previous
patch being removed.
Corrective Action: For an On-Call medication order with a dosage form
of "PATCH," a user must first remove the previous patch administered
before allowing any proceeding patches to be given.
4. Problem: The administration times for a medication order that uses a
Day-of-the-Week schedule (i.e., MO-WE-FR@0900) do not print on the
GUI application and the CHUI application.
MAH.
Corrective Action: The MAH will now display the administration times
for a medication order containing a Day-of-the-Week schedule.
5. Problem: The VDL generates displays an error if the user types
special characters (i.e., "^" or "?") when entering a comment for a
medication order.
Corrective Action: Any special characters entered with comments
will be removed when BCMA files the comment.
6. Problem: The option "Take Action on WS" was removed in BCMA patch
PSB*2*20. This option allowed the user to change the status of a ward
stock IV bag.
Corrective Action: The option "Take Action on WS" has been added to
patch PSB*2*19.
7. Problem: The new Reduced Space Symbology (RSS) bar codes contain the
Corrective Action: BCMA will validate the version of the GUI BCMA
National Drug Code (NDC) number in a new format called "Global Trade
Item Number (GTIN)." The GTIN has a 14-digit data structure, which is
used within the EAN.UCC System for the unique identification of trade
items worldwide.
Corrective Action: BCMA GUI will correctly read the GTIN and search
the SYNONYM field (#.01) of the DRUG file (#50) for a matching NDC
number.
8. Problem: The BCMA GUI Due List Report allows the user to select a
Site Parameters application running on the client against the CHUI
stop time that is prior to the start time.
Corrective Action: The BCMA GUI Due List will not allow the user to
select a stop time that is prior to the start time:
9. Problem: The MAH Report only displays the action of "Removed" for a
PRN, On-Call, and One-Time medication order with a dosage form of
"PATCH."
Corrective Action: The MAH Report will now display actions of
application. The client version must match the patch number on the
"Removed" and "Given." for PRN, On-Call, and One-Time medication
orders with a dosage form of "PATCH."
10. Problem: If an IV medication order has an infusing bag and becomes
expired, the infusing bag continues to display on the VDL, along with
the other available bags.
Corrective Action: Available bags will not display when an IV
medication order becomes expired.
VistA server, and if compatible, the previous GUI version will be
allowed to run. No prior version will be allowed to run on the client.
1. Bar Code Medication Administration (BCMA) will provide a visual
check box is selected in the GUI BCMA Site Parameters application. All
other schedule types will remain selected on the VDL by default when the
user opens a patient's record.
3. The VDL will display a BCMA Clinical Reminders marquee at the lower
right hand corner. The "count" is the number of PRN medications
without Effectiveness comments within the hours defined in the
"PRN Documentation" field on the Parameters tab of the GUI BCMA Site
Parameters application or within the current admission whichever is
greater.
indicator on the Virtual Due List (VDL) to identify which schedule types
A mouse-over list displays the last four undocumented PRN orders.
When the user double clicks anywhere on the PRN Effectiveness row of
the BCMA Clinical Reminders marquee, the PRN Effectiveness Log dialog box
displays all PRN orders that need PRN Effectiveness and allowing
documentation of PRN Effectiveness comments for each order listed.
The "count" will update/refresh when the user:
a) opens a patient file.
b) administers a PRN medication order.
c) completes the documentation of a PRN Effectiveness.
have active orders within the specified start and stop date/time for the
d) refreshes the VDL.
A Med History button has been added to display the Medication
Administration History for the order selected.
4. When administering a PRN medication, the units given column
within the Last Four Actions table and a drop down box for the users to
select the PRN Reason have been added to the Medication Log dialog box.
Units given will not display for orders with multiple dispensed drugs.
selected Medication Tab. A green "alert light" to the left of the
5. An updated PRN Effectiveness Log dialog will ease the process of
PRN Effectiveness documentation. It displays a list of undocumented PRN
medications for a specific order, or across orders, including PRN
medications from previous or expired orders. The dialog box
includes a "units given" column, which will not display units for orders
with multiple dispensed drugs. The division column has been removed.
Schedule Type indicates that it has active orders for the specified
timeframe, and a gray "alert light" to the left of the Schedule Type
indicates that it has no active orders for the specified timeframe.
2. PRN medications will display on the VDL if the PRN Schedule Types
***NOTE*** This patch should be discussed at each Department of
menu contains the Documenting Backlog PRNs [PSB PRN DOCUMENTING] option
which will allow a user to run a report for a date range that will
search through the BCMA MEDICATION LOG file (#53.79) for all
undocumented PRNs. The Documenting Backlog PRNs [PSB PRN DOCUMENTING]
option will automatically enter in a comment of "Administrative Closure"
for all undocumented PRNs identified by the report.
In accordance with M1, Part 1, Chapter 5, these blank sections of the PRN
documentation will reflect the term "Administrative Closure" when the
software is used to close these blank portions related to the PRN
Veterans Affairs Medical Centers (VAMC) before being invoked.
documentation. The sites medical record review committee should document
the decision to run the patch to administrative close the undocumented
PRN if the site chooses to use this option. In those cases where the sites
have reviewed the charts and find that the PRN documentation appears in
the patient record in other than the BCMA PRN field, the site should
individually enter "documented in progress note."
The person installing the patch will receive a MailMan message when
the process has completed. The subject line will read, "BCMA PRN
DOCUMENTATION Notification."
Problem: Sites are experiencing a large number of undocumented
Pro Re Nata (PRN) effectiveness in the counter displaying under the
"BCMA Clinical Reminders" section of the GUI Bar Code Medication
Administration (BCMA) Virtual Due List (VDL).
Solution: The Bar Code Medication Administration Manager [PSB MGR]
The VistA Bar Code Medical Administration Backup System (Patch PSB*2*17)
on a Pharmacy Medical Administration Record (MAR) and Medical
Administration History (MAH). Workstation(s) are updated using the
VA Health Level (HL7) package and are available for use according to
local policies concerning VistA, BCMA or network outages.
software being released will provide a Class I solution to the BCMA
Contingency IRA #20020403. This plan reflects the intent of VHA Directive
6210, The Automated Information Systems (AIS) Security, which states that
all facilities are responsible for the development, maintenance, and
annual testing of individual AIS contingency. This software maintains a
current copy, on the designated workstation, of all the inpatient pharmacy
activities including the inpatient medical orders(Unit Dose and IV),
medication administration and patient allergies, that are included
Problem: NOIS SAJ-0803-71312
The BCMA Due List [PSBODL] option, and the VDL will generate a Due List
Error Notification message for IV Piggyback medication orders with a
Schedule Type of Continuous that have Admin times, and A frequency set to
null. The BCMA Due List [PSBODL] option, and the VDL will generate a Due
List Error Notification message for orders with Schedule Type of
Continuous that are Unit Dose and IV Piggyback orders that have schedules
names in the format of administration times but the Admin times do not
exist on the order (i.e., schedule = 1200-1600 admin times = NULL).
An IV Piggyback order with a Schedule Type of Continuous that has Admin
times, (i.e., Q12H with admin times of 0800-2000), and a frequency set to
null, does not display on the Bar Code Medication Administration (BCMA)
Graphical User Interface (GUI) Virtual Due List (VDL) IVP/IVPB Medication
Tab and the Due List [PSBODL] option. The VDL and the Due List [PSBODL]
option also do not generate a Due List Error Notification message.
Corrective Action:
1. Problem: NOIS ISB-1102-30304
selection process used in other provider system applications such as
Inpatient Medication V 5.0 and Pharmacy Data Management V 1.0.
2. Problem: NOIS NCH-1102-40363
The Medication Variance Log [PSBO MV] option will inappropriately display
variance information related to medication orders with a status of
"REMOVED" on the BCMA Variance Log Report.
Corrective Action: The Medication Variance Log [PSBO MV] option will not
display variance information related to medication orders with a status
The Drug File Inquiry [PSB DRUG INQUIRY] option does not resemble or
of "REMOVED" on the BCMA Variance Log Report.
3. Problem: NOIS MAD-0902-42331
The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT] option will
improperly allow users an opportunity to enter a comment for PRN
medication orders that do not have a status of "GIVEN".
Corrective Action: The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT]
option will only allow users an opportunity to enter a comment for PRN
medication orders with a status of "GIVEN".
follow a similar drug selection process used in other provider system
4. Problem: NOIS CLL-0203-40445
The Label Print [PSBO BL] option will not retrieve the correct drug name
if the user enters the drug name as lower case letters.
Corrective Action: The Label Print [PSBO BL] option will retrieve the
correct drug name if the user enters the drug name as lower case letters.
5. Problem: NOIS ISB-1102-32339
The Medication Variance Log [PSBO MV] option will only display variance
applications such as Inpatient Medication V 5.0 and Pharmacy Data
information related to patients currently assigned to the selected ward
on the BCMA Variance Log Report. The option will not display variances
information associated with previous patients assigned to the selected
wards.
Corrective Action: The Medication Variance Log [PSBO MV] option will
rebuild the data structure used to sort, store, and display the variance
information related to all patients assigned to the selected ward stored
in the BCMA MEDICATION VARIANCE LOG file (#53.78).
Management V 1.0. A site is requesting modifications that will add
6. Problem: NOIS MWV-0102-23190
The Medication Variance Log [PSBO MV] option will not display variance
information on the BCMA Variance Log Report when the user selects to
print the report by ward names. Several sites are experiencing this
problem as a result of incompatible ward names between the BCMA
MEDICATION VARIANCE LOG file (#53.78) and the NURS LOCATION file
(#211.4). In addition, sites should populate their NURS LOCATION file
(#211.4) with the proper ward name from the WARD LOCATION file (#42) to
prevent this problem from reoccurring.
consistency to the drug selection process.
Corrective Action: The Medication Variance Log [PSBO MV] option will
compare the ward's internal entry number (IEN) stored in the BCMA
MEDICATION VARIANCE LOG file (#53.78) to the ward's IEN stored in the
WARD LOCATION file (#42). The BCMA application will store the ward's IEN
for future variances. Site must use the new Ward Name Conversion Process
[PSB WARD CONVERSION] option under the Bar Code Medication Administration
Manager [PSB MGR] option to convert the ward name associated with
previous variance information stored in the BCMA MEDICATION VARIANCE LOG
file (#53.78) in order to print a BCMA Variance Log Report based on
previous variance information.
The Ward Name Conversion Process [PSB WARD CONVERSION] option is
temporary. However, in the future, Bar Code Medication Administration
patch PSB*2*23 will remove the temporary Ward Name Conversion Process
option from your system. The Ward Name Conversion Process option will
perform the following functions:
a. Allow users to select a specified date range, which will control the
amount of data and time needed to complete the process.
b. Convert the ward's name to the ward's internal entry number (IEN) if
Corrective Action: The Drug File Inquiry [PSB DRUG INQUIRY] option has a
the Ward Name in BCMA MEDICATION VARIANCE LOG file (#53.78) is
identical to the Ward Name in the WARD LOCATION file (#42).
c. Display a list of un-identifiable ward names and allows the user to
make the appropriate corrections.
revised continuous search index function that resembles the drug
1. Problem: NOIS AAA-0303-N1449
2. Problem: NOIS ISB-0503-30409
After a medication patch order is "Given," if that order expires or is
discontinued, and the patient has no other active orders, the patch
does not display on the VDL; the message "No Active Orders" displays
instead.
Corrective Action:
If a patch is "Given" and not "Removed," it should display on the VDL
The "Last Action" column on the Bar Code Medication Administration
until it is marked as "Removed." A patch with the status of "Given"
will display on the VDL until it is marked as "Removed."
3. Problem: NOIS ISB-0503-30409
After a large volume IV order is "Infusing," if that order expires or
is discontinued and the patient has no other active orders, the
infusing IV does not always display on the VDL; the message "No
Active Orders" displays instead.
(BCMA) Virtual Due List (VDL) displays inaccurate information via a
Corrective Action:
If an IV is "Infusing" and not "Completed," it should display on the
VDL up to 7 days after the order is expired/discontinued or until the
order is marked as "Completed." An IV that is "Infusing" will
display on the VDL for 7 days after the order is expired/discontinued
or until it is marked as "Completed."
sequence of administrative actions upon two distinct orders having the
4. Problem: NOIS HAM-0103-22522, HUN-0403-21086
The Edit Medication Log [PSB MED LOG EDIT] option does not allow the
user to change the status of a medication patch from "Given" to
"Removed." An attempt to change the status from "Given" to "Removed"
using the Edit Medication Log [PSB MED LOG EDIT] option displays the
message "Allowed status codes are Given, Not Given, Held, and
Refused," preventing the status change of the medication patch.
same orderable item.
Corrective Action:
The Edit Medication Log [PSB MED LOG EDIT] option will allow the
status of a "Given" medication patch to be changed to "Removed."
5. Problem: NOIS ISB-0703-30098
The Manual Medication Entry [PSB MED LOG NEW ENTRY] allows the user to
enter any administration status for any order type. For example, the
user can create a new BCMA Medication Log entry for a medication
patch order, with an administration status of "Completed."
Corrective Action:
The Manual Medication Entry [PSB MED LOG NEW ENTRY] will only allow
the user to enter "Given," "Held," or "Refused" for orders which are
not IV orders. A status for an IV order will not be allowed since IV
medications cannot be entered via this menu option.
6. Problem: NOIS ISB-0703-30653
The "Schedule:" prompt in the Manual Medication Entry [PSB MED LOG NEW
Corrective Action:
ENTRY] option screen displays the schedule type instead of the
schedule.
Corrective Action:
The "Schedule:" prompt in the Manual Medication Entry [PSB MED LOG NEW
ENTRY] option screen will display the schedule.
7. Problem: NOIS CLL-0303-40554
The Manual Medication Entry [PSB MED LOG NEW ENTRY] option allows the
The "Last Action" column on the BCMA VDL will display appropriate and
user to enter a future date and time for a medication administration,
which sometimes causes inaccurate information on BCMA reports.
Corrective Action:
The Manual Medication Entry [PSB MED LOG NEW ENTRY] option will not
allow the user to enter a future date and time for a medication
administration.
accurate status, date and time information per orderable item.
*** ATTENTION: This patch includes a new Graphical User Interface (GUI)
Patch PSB*2*30 presents some changes to the 'look and feel' of the Bar
Corrective Action:
BCMA will allow the user to submit a Missing Dose Request for a
medication patch order when another patch from that order displays a
status of "GIVEN" on the VDL.
9. Problem: NOIS ISB-0703-31421
When the user submits a Missing Dose Request for a PRN medication and
immediately (without refreshing the BCMA VDL) marks that PRN as "GIVEN,"
Code Medication Administration (BCMA) GUI. One change is the additive and
BCMA files into the BCMA Medication Log a null value as the PRN Reason.
Corrective Action:
BCMA will file into the BCMA Medication Log the PRN Reason as selected by
the user for the respective PRN administration.
10. Problem: NOIS SDC-0803-60738
When a Global Trade Identification Number (GTIN) bar code was scanned,
BCMA would strip out the National Drug Code (NDC) number from the GTIN
solution display automatically for an infusing bag in the IV chronology
and perform a search on it. This would result in BCMA not finding a match
and displaying the error message "Invalid Medication Lookup. DO NOT
GIVE!!"
Corrective Action:
The logic that performs the lookup has been modified to not strip out the
NDC number.
11. Enhancement: E3R#18328
section of the Virtual Due List (VDL). Another change is during the
BCMA GUI will allow a medication patch to be marked as "HELD" or
"REFUSED" while another patch from the same order displays as "GIVEN" and
not marked "REMOVED."
12. Enhancement: E3R#13940
BCMA GUI will provide the user access to the BCMA Medication Variance Log
Report from the Reports menu of the VDL.
administration of a Pro Re Nata (PRN) the PRN reason may be selected by
typing the first letter of the PRN Reason. BCMA will focus on the PRN
Reasons that start with the first letter typed in the PRN Reason
selection area.
executable file.
1. Problem: NOIS CPH-0703-40060
When an IV medication order becomes expired while an IV bag is
"INFUSING" or "STOPPED," the un-administered bags of that order are still
"available" for administration.
Corrective Action:
When an IV medication order expires, the un-administered IV bags will not
display on the BCMA VDL.
Installation of this GUI is NOT required immediately after the
2. Problem: NOIS RIC-0703-20366
The "Scanner Status:" indicator on the BCMA VDL displays red when the
user switches from another application back to the BCMA GUI.
Corrective Action:
The BCMA VDL Scanner Status indicator will display green when it is
possible to scan medication using BCMA.
3. Problem: NOIS ISB-0303-31005
KIDS install for the Patch to function. ***
Multiple IV bags of an order may be "INFUSING" simultaneously. BCMA does
not allow proper maintenance of any of these administered IV bags. For
example the user cannot "COMPLETE" any of the "INFUSING" IV bags.
Corrective Action:
BCMA will allow the maintenance of an order with multiple "INFUSING" IV
bags.
4. Problem: NOIS ISB-0703-31029
If the BCMA GUI user enters a space alone as documentation of PRN
Effectiveness, an "information box" displays because the space is
inappropriately treated as a special character.
Corrective Action:
When documenting PRN Effectiveness using the BCMA GUI via a lone space
character, the lone space will not be treated as a special character;
instead the user will be asked to re-enter the data.
5. Problem: NOIS ISB-0703-30373
The user must scroll the list of output devices to select the most
recently used print device.
Corrective Action:
The print device most recently selected by the user will display first in
the list of selectable print devices.
6. Problem: NOIS ISB-0703-30480
For retrieval and installation instructions, please see the Client
Using the BCMA Site Parameter GUI application, the user can seemingly
create an unlimited number of entries for a "Default Answer List" such as
the BCMA "Injection Site" list . These entries should then be selectable
from the respective list box during certain medication administration
using the BCMA GUI. Without notice to the user, BCMA limits the number
of entries/selections to 60.
Corrective Action:
Using the BCMA Site Parameter GUI application, the user will be able to
create up to 100 entries for a BCMA "Default Answer List" list box.
Installation Instructions section.
Therefore it will be possible for the user to have up to 100 entries to
select from the respective BCMA GUI list box.
7. Problem: NOIS ISB-0703-30478
Using the BCMA Site Parameter GUI application the user can seemingly
create entries for a BCMA "Default Answer List" box, such as the BCMA
"Injection Site" list, longer than 30 characters. Without notice to the
user, BCMA limits the number of characters for a list entry to 30.
Corrective Action:
Using the BCMA Site Parameter GUI application the user will not be able
to create entries for a BCMA "Default Answer List" more than 30
characters in length.
8. Problem: NOIS ISB-0703-30290
Using the BCMA GUI, the user cannot submit a Missing Dose Request for a
medication patch order when another patch from that order displays a
status of "GIVEN" on the VDL.
1. The user is allowed to view and print the Bar Code Medication
within the last 7 days.
3. When the user opens a patient record from the BCMA GUI application, the
Vitals Cumulative Report can be accessed from the Reports menu.
4. When enabled, BCMA will broadcast BCMA Medication Log data to
applications that subscribe to BCMA Heath Level 7 (HL7) Messaging.
The events or transactions tht trigger the message broadcasts are
MEDPASS, UPDATE, STATUS, ADD COMMENT, and PRN EFFECTIVENESS. Upon the
completion of each "trigger event," BCMA will send HL7 version 2.4
Administration (BCMA) ward specific reports via the BCMA GUI (Graphical
compliant messages to COTS and other subscribing products or
applications. The BCMA HL7 interface must be activated after
installation for messaging to occur.
5. When the user launches the BCMA GUI application, the message box
displays information regarding BCMA 508 compliance. This information
can also be found in the BCMA Help, About dialog box.
6. When the user scans a currently infusing or stopped bag on the VDL IV
tab and the associated order has had any changes made to it since the
user interface) application without having to open a patient record.
infusing or stopped bag's label was printed, the Scan IV box will
display Order changes including bag status and changes made on the
associated order.
7. A new column "Bag Information" has been added to the VDL IV tab. This
column contains the administration status, date and time of the
currently infusing or stopped bag on its associated order and one of
the following messages if the order has changed since the bag label
was printed. "INFUSING bag on changed order" or"STOPPED bag on changed
order". This column is updated every time the patient record is opened
or the VDL is refreshed.
8. Problem: NOIS MIN-0703-42067
The Bar Code Medication Administration (BCMA) Graphical User Interface
(GUI) does not print the Medication History Report for large volume
IV's under the GUI IV Medication Tab.
Corrective Action:
The BCMA GUI Medication History Report for IV Medications will print
for large volume IV's under the GUI IV Medication Tab.
2. When administering a PRN medication or documenting a PRN
9. Problem: NOIS TAB-0903-40220
When users take BCMA offline by unchecking the BCMA on-line check box
on the GUI BCMA Site Parameters Facility Tab, the users are unable to
sign in again to the BCMA Site Parameters application and get the
following error: "The BCMA Application is not active for this
division", followed by an application error.
Corrective Action: When users take BCMA offline by unchecking the
BCMA on-line check box on the GUI BCMA Site Parameters Facility Tab,
Effectiveness, the Medication Log dialog box or the PRN Effectiveness
the users will be able to sign in again to the BCMA Site Parameters
application without receiving the above errors.
10. Problem: NOIS ISB-0703-30291
When a user selects a report from the BCMA GUI Reports menu, the
"Print by" area of the associated dialog box does not display all
wards in the Ward list box.
Corrective Action:
The "Print by" area of the BCMA GUI report dialog boxes displays all
Log respectively will display a vitals table with the vital signs:
wards in the Ward list box.
11. Problem: NOIS MAD-0203-42078
When the user attempts to enter an order via the Computerized Patient
Record System (CPRS) Med Order Button, the order is being cancelled
due to an error, "missing data, unable to file"
Corrective Action:
The user will be able to successfully enter an order via CPRS Med
Order Button without receiving the above error.
Temperature (Temp), Pulse, Respiration (Resp), Blood Pressure (BP) and
Pain. Each of the vital signs will list up to 4 vital entries made
1. Problem: The Missed Medications [PSBO MM] option does not display a
Provider takes if Off Hold, no verbiage is displayed next to the
medication.
Corrective Action: The Missed Medications [PSBO MM] option displays
"(On Hold)" date and time below a medication when the Provider places
it on Hold. When the Provider takes if off Hold, it displays the
"(On Hold)" date and time as well as the "(Off Hold)": date and time
below the medication.
One-Time order for the new ward after a patient is transferred to
another ward.
Corrective Action: The Missed Medications [PSBO MM] option displays a
One-Time order after a patient is transferred to another ward.
2. Problem: The Missed Medications [PSBO MM] option displays "(Hold)"
next to a medication when a Provider places it on Hold. When the
1. Problem: The Bar Code Medication Administration (BCMA) Order Manager
a ward stock entry on GUI BCMA.
Corrective Action: GUI BCMA has been modified to regconize the synonym
number of an IV medication.
3. Problem: When using the CPRS Med Order button, the orderable item
lookup was using a direct global read.
Correction: The orderable item lookup has been modified to call a
Computerized Patient Record System (CPRS) Application Program Interface
dialogue box from the CPRS Med Order button displays the
(API) instead of using a direct global read.
"Invalid Medication Lookup, DO NOT GIVE!!"
Corrective Action: The BCMA Order Manager dialogue box has been
corrected to perform a lookup on the drug synonym number.
2. Problem: The user will receive the "Invalid Medication Lookup,
DO NOT GIVE!!" error message box when scanning an IV bag to create
1. Problem: NOIS ISB-0503-30379
option display the PRN Effectiveness reasons using word wrap.
2 Problem: NOIS ISB-0503-31838
A medication order with a Day-of-the-Week schedule, will use
the frequency from Inpatient Medication, and incorrectly display the
data on the Graphical User Interface (GUI) Bar Code Medication
Administration (BCMA) Virtual Due List (VDL) as being due everyday.
Corrective Action: A medication order with a Day-of-the-Week
schedule correctly displays on the GUI BCMA VDL on the day scheduled.
The Medication Administration History [PSBO MH] option
3. Problem: NOIS LIT-0303-72207
The Medication Administration History [PSBO MH] option will not
display medication orders with an odd schedule, which include
administration times.
Corrective Action: The Medication Administration History [PSBO MH]
option displays odd schedules with administration times, along with
the following message, "NOTE - ODD SCHEDULE NO LONGER ALLOWS
ADMIN TIMES."
and the Medication Administration Log [PSBO ML] option displays
4. Problem: NOIS ISB-1102-30781
The Medication Administration History [PSBO MH] option and the
Medication History Report are not accessible to the user when
a medication is not due.
Corrective Action: The Medication Administration History [PSBO MH]
Option and the Medication History report displays three asterisks
("***") in the Date column when a medication is not due.
the Pro Re Nata (PRN) Effectiveness reasons on one continuous
5. Problem: NOIS AMA-0403-70477
The Patient Due List Report and the Ward Administration Time Report
will not display a "due" medication, on the correct day, for
schedules with frequencies greater than 24 hours, (i.e.,Q36).
Corrective Action: The Patient Due List Report and the Ward
Administration Time Report display "due" medication, on the correct
day, for schedules with a frequency greater then 24 hours.
6. Problem: NOIS MAD-0303-40194
sentence rather than wrapping the information to several lines for
The Medication Administration Log [PSBO ML] option, Medication Log
Report displays the medication as "GIVEN" with the incorrect dosage
value, after the medication status was marked as "Not Given" on the
VDL.
Corrective Action: The Medication Administration Log [PSBO ML] option
and the Medication Log Report display the medications administration
units of zero when the medication is set to "NOT GIVEN" on the VDL.
7. Problem: NOIS ISB-0703-30482
viewing.
The Medication Administration History [PSBO MH] option,
Medication History Report, will display the word "HOLD" in the Date
column, for all days on the report, even after the medication is
taken Off Hold.
Corrective Action: The Medication Administration History [PSBO MH]
option, Medication History Report, displays "HOLD" in the Date column
on the days that the medication was placed On Hold, through the end
date of the report. When the medication is taken Off Hold, the word
"HOLD" Appears on the Report from the On Hold date to the Off Hold
date.
8. Problem: NOIS ISB-0703-30482
The Medication Administration History [PSBO MH] option incorrectly
displays orders with a Schedule Type of Continuous, with a Schedule in
the format of administration times (i.e. Schedule = 1200-1400) but
where the Admin times have been deleted. Continuous schedules with
valid admin times that are not Day-of-the-Week Schedules but have a
NULL frequency are also incorrectly displayed.
Corrective Action: The Medication Administration History [PSBO MH]
Corrective Action: The Medication Administration History [PSBO MH]
option will not display orders that meet the above criteria.
9. Enhancement: E3R NO.15232
The Medication Administration History [PSBO MH]
option and the Medication History report displays the date as well
as the time the order was started on the report.
option and the Medication Administration Log [PSBO ML]
*** DUE TO PURGED PENDING-ORDERS, BCMA MAY NOT BE ABLE TO TRACK AND
Medications with a Schedule Type of Continuous and marked as "Held" may
not display on the Due List [PSBO DL] option report.
This issue becomes very apparent when the Bar Code Medication
Administration (BCMA) system is generating Internal Entry Numbers
(IEN) for the BCMA Medication Log file (#53.79) which exceed the date
numerically.
Corrective Action:
Medications with a Schedule Type of Continuous and marked as "Held"
will display on the Due List [PSBO DL] option report.
DISPLAY ORDER HISTORY AND ORDER CHANGES. WITH INSTALLATION OF
2. Problem: NOIS ISB-0703-30657
When creating an administration for a Pro Re Nata (PRN) order in the
Manual Medication Entry [PSB MED LOG NEW ENTRY] option, the "Brief
Administration History" displays the status of "Not Given" as one of
the last four actions.
Corrective Action:
When creating an administration for a PRN order in the Manual Medication
PSB*2.0*35, BCMA ERRORS CAUSED BY PURGED PENDING-ORDERS ARE INTERCEPTED,
Entry [PSB MED LOG NEW ENTRY] option, the "Brief Administration
History" will not display the status of "Not Given" as one of the last
four actions.
3. Problem: NOIS WPB-0503-31999
The latest printed label for an IV medication order may not display
on the BCMA Virtual Due List (VDL) as an "available bag" when it
should.
BUT WILL NOT ALLOW BCMA TO TRACK AND DISPLAY COMPLETE ORDER HISTORY AND
Corrective Action:
All printed labels that are valid and should be available for
administration will appropriately display as "available" on the VDL.
4. Problem: NOIS NCH-1003-41434
The BCMA Label Print [PSBO BL] option does not allow the use of a drugs
internal entry number (IEN) alone to select a "Drug Name" for a
printed label.
ORDER CHANGE DATA. ***
Corrective Action:
The BCMA Label Print [PSBO BL] option will select the appropriate
drug when the user enters solely the drugs IEN to select a "Drug
Name" for a printed label.
5. Problem: NOIS UNY-1003-10407
Allergy data is being displayed in the report header "Reactions:"
field of reports printed via the VDL, such as the Medication Due
List report.
Corrective Action:
Adverse Drug Reaction information will display in the report
header, "Reactions:" field of reports printed via the VDL.
6. Problem: NOIS ALX-1103-70256
An error occurs when the user attempts to access a
patients VDL and that patient has an active medication order
with an ACTION STATUS field (#.09) of the BCMA MEDICATION LOG
file (#53.79) equal to null. The error message encountered is
"$ZE=<SUBSCRIPT>EN+75^PSBVDLUD."
Corrective Action:
A patients VDL will display without error when that patient has
an active medication order with an ACTION STATUS field (#.09) of the
BCMA MEDICATION LOG file (#53.79) equal to null.
1. Problem NOIS HIN-0703-41481:
****NOTE**** Patch PSB*2*23 will remove the Ward Name Conversion
time that a patch was "Removed," instead of "Given," under the "Admin
Time" column.
Corrective Action: The PRN Effectiveness List [PSBO PE] option will
display the date and time that a patch is "Given" under the "Admin Time"
column.
2. Problem: NOIS ISB-0303-30557
The PRN Effectiveness List [PSBO PE] option displays a PRN medication
entry twice on the PRN Effectiveness List Report when the user enters a
Process [PSB WARD CONVERSION] option from your system. Please complete
Missing Dose Request and administers the medication at a later time.
Corrective Action: The PRN Effectiveness List [PSBO PE] option will not
display a PRN medication entry twice on the PRN Effectiveness List
Report when the user enters a Missing Dose Request and administers the
medication at a later time.
3. Problem: NOIS ISB-0903-31938
The Missing Dose Report [PSBO MD] option will display the header "Dosage
Schedule" on the Bar Code Medication Administration (BCMA) Character
the ward name conversion process before installing patch PSB*2*23,
User Interface (CHUI) Missing Dose Report. This header is not
consistent with the naming scheme that describes the medication order
schedule information sent to the Pharmacy via the e-mail notification
message.
Corrective Action: The Missing Dose Request [PSBO MD] option displays
the header "Schedule" on the BCMA CHUI Missing Dose Report. This
information coincides with the BCMA naming scheme that describes the
medication order schedule information sent to the Pharmacy via the
e-mail notification message.
using the Ward Name Conversion Process [PSB WARD CONVERSION] option in
4. Problem: NOIS ISB-0703-30029
The Missing Dose Request [PSB MISSING DOSE REQUEST] option creates a
variance entry in the BCMA MEDICATION VARIANCE LOG File (#53.78) when
the user enters a Missing Dose Request outside the timeframe specified
for the "Allowable Time Limits" parameter within the Parameters Tab of
the GUI BCMA Site Parameters application.
Corrective Action: The Missing Dose Request [PSB MISSING DOSE REQUEST]
option will not create a variance entry in the BCMA MEDICATION VARIANCE
patch PSB*2*14.
LOG File (#53.78) when the user enters a Missing Dose Request outside
the timeframe specified for the "Allowable Time Limits" parameter within
the Parameters Tab of the GUI BCMA Site Parameters application.
5. Enhancement: E3R #13009
The Missing Dose Request [PSB MISSING DOSE REQUEST] option will display
the medication order schedule information in the e-mail notification
message sent from BCMA to the Pharmacy for a Missing Dose Request.
6. Enhancement: E3R #17312
The Missing Dose Request [PSB MISSING DOSE REQUEST] option displays the
medication order schedule information on the Missing Dose Report sent
from BCMA to the Pharmacy-selected printing device.
1. Problem: NOIS ISB-0203-31993
Pro Ra Nata (PRN)
The PRN Effectiveness List [PSBO PE] option displays the date and
*** ATTENTION: This patch includes a new Graphical User Interface (GUI)
Installation Instructions section.
1. When administering a Pro Re Nata (PRN) medication or documenting a PRN
Effectiveness and the PRN Reason is one set via the Bar Code Medication
Administration (BCMA) Site Parameters settings to initiate a pain score
reading, BCMA will automatically initiate a pain score reading to be
filed with other Vital Measurement information.
2. Problem: NOIS DUB-0803-31307
executable file. Installation of this new GUI is REQUIRED in order
When all of a patient's active medication orders of an order type have no
scheduled administrations within the date range of the BCMA Virtual Due
List (VDL), the message "No Active Orders at this Time" displays.
This message is not accurate.
Corrective Action:
When all a patient's active medication orders of an order type have no
scheduled administrations within the date range of the BCMA Virtual Due
List (VDL), the message "No Administration(s) due at this time" will
display.
for the patch to function. The new GUI MUST be installed IMMEDIATELY
3. Problem: NOIS NYH-0903-10598
BCMA is not showing the correct number of PRN Reminders for patients.
BCMA calculates the number of PRN Reminders based on the date/time of
patient's transfer and not the date/time of the patient's admission.
Corrective Action:
BCMA will identify and display PRN Reminders based on the date/time of
the patient's admission.
after the KIDS install in order for the software to function. ***
4. Problem: NOIS ISB-1103-31688
The error "$ZE= NTE+16^PSBSVHL7:1, %DSM-E-UNDEF, undefined variable "
may occur when comment internal entity numbers (IEN), of the BCMA Medication
Log are not in sync with the BCMA Medication Log comment sub-file index. BCM
Health Level 7 (HL7) messaging may attempt to transmit a comment which
does not exist, causing the error.
Corrective Action:
BCMA HL7 messaging will transmit the appropriate comment independent
of the BCMA Medication Log comment sub-file index.
5. Problem: NOIS ISB-1103-31567
The BCMA Cumulative Vitals report does not display the vital changes if
only one measurement was changed for the designated date range.
Corrective Action: The Cumulative Vitals report will show all changes
that occur within the designated date range.
For retrieval and installation instructions, please see the Client
1. Problem: When a user attempts to log on to the GUI BCMA, they receive
2. Problem: Sites are unable to access the GUI, due to the VISTA side
needing the most current version of BCMA.
Corrective Action: The code which checks the version number has been
corrected to properly return the correct version.
the following messages:
RPC BOWDPS5 GETUDID in Option PSB GUI CONTEXT - USER **NOT FOUND**
RPC BOWDPS5 GETIVID in Option PSB GUI CONTEXT - USER **NOT FOUND**
Corrective Action: The RPC's ORBCMA5 GETUDID and ORBCMA5 GETIVID were
added to BCMA Client Context [PSB GUI CONTEXT - USER] option.
1. Problem: When a medication was given and then not given the Gui did
to the log file, which caused BCMA to shut down.
Corrective Action: Additional error trapping was added to report the
error to the user without shutting down.
3. Problem: When attempting to mark multiple patches as removed, the user
receives the following error message:
"Error(s) Filing Transaction MEDPASS"
Business Logic Error: PRN Medications MUST Have a PRN Reason
not validate.
Business Logic Error: PRN Orders cannot be marked NOT Given
Corrective Action: BCMA GUI has been modified to not allow the
multiple marking of patches as removed.
4. Problem: User was receiving an undefined variable error in routine
PSBVDLU1 when attempting to log on to the BCMA GUI application.
Corrective Action: The code was modified to not error when logging on
to the GUI application.
5. Problem: When using the CPRS Med Order button, the IV Fluid Order
screen is not displaying the same volume as the BCMA Order Manager
screen.
Corrective Action: The IV Fluid Order screen is now displaying the
same volume as the BCMA Order Manager screen.
6. Problem: The user would recieve an error when trying to launch
multiple copies of the BCMA GUI.
Corrective Action:The GUI will validate when a user marks a med from
Corrective Action: The GUI has been corrected to display the
Open Error message, "There is already one copy of Bar Code
Medication Administration running on this machine!"
7. Problem: When launching the BCMA Site Parameters application, the focus
was not on the electronic signature box.
Corrective Action: The BCMA Site Parameters application has been
modified to place focus on the electronic signature box.
Given to Not Given that the user either has the "PSB MANAGER" key or
8. Problem: One-time orders were printing on the Due List [PSBO DL]
option after the stop date of the order.
Corrective Action: The printed Due List [PSBO DL] option was modified
to not print one-time orders past the stop date of the order.
that the user id matches the user id that made the entry in the med
log.
2. Problem: An error would occur if the user did not have write access
1. Problem: Patient's who did not have a PRN medication administered were
incorrectly displaying on the PRN Effectiveness List [PSBO PE] option.
Corrective Action: There is a post install routine, which runs to clean
up erroneous file entries that were causing the patient's to display
on the PRN Effectiveness List [PSBO PE] option. The routine has also
been corrected to not create the erroneous file entries.
1. Problem: An allocation error was being generated when starting the Bar
Corrective Action: The GUI has been corrected to allow printing when
selecting a mnemonic.
3. Problem: The data entered in the Enter Quantity and Units dialogue box
from the IVP/PB tab was not being stored in the medication log.
Corrective Action: The data is now being properly stored in the
medicatin log.
Code Medication Administration (BCMA) GUI application. The error
4. Problem: The Not Given action was not available on the Virtual Due
List (VDL) unless the user performed a refresh.
Corrective Action: The Not Given action is now available with out
the user having to perform a refresh on the VDL.
5. Problem: The Multiple Doses to Scan dialogue box does not display to
the user when a multiple unit per dose order is administered from the
GUI IVP/IVPB Virtual Due List (VDL) tab.
was a result of a large number of printers in the DEVICE file (#3.5).
Corrective Action: The GUI IVP/IVPB VDL tab has been corrected to
properly display when a unit dose order has multiple units per dose.
Corrective Action: The software has been modified to allow for a large
number of entries in the DEVICE file (#3.5).
2. Problem: Users could not print from the GUI application when selecting
a mnemonic name from the DEVICE file (#3.5)
1. Problem: If a gap of time exists between the original continuous IV
order stop date/time and the renewed order start date/time,
the Bar Code Medication Administration (BCMA) Virtual Due List (VDL)
IV tab would not display the original order until the expected stop
date and time.
Correction: The BCMA VDL IV tab will now display the original order
until the stop date/time of the order is reached.
Patch Description:
Corrective Action: The BCMA Print Label [PSBO BL] option was modified to
perform the drug validate process before the device selection process.
Therefore, the drug validation process will be performed if the system
device was set to BROWSER or queued to a device.
Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem
was discovered in the coding logic that created an entry in the BCMA
Report Request file (#53.69). If the user canceled the label print
process as a result of a mismatch between the selected drug and patient,
an impartial or bogus entry would remain in the BCMA Report Request file
=================
(#53.69) occupying vital system resources.
Corrective Action: The BCMA Print Label [PSBO BL] option was modified by
inserting the necessary coding logic to delete the impartial or bogus
entry in the BCMA Report Request file (#53.69) when the print label
procedure is cancelled as a result of a mismatch between the selected
drug and patient.
Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem
was discovered in the ScreenMan data input functions. If the selected
patient requires a Means Test, the option will abruptly display a message
to the user indicating "*** Patient Requires a Means Test ***" and the
ScreenMan data input process was rearranged out of order.
Corrective Action: The BCMA Print Label [PSBO BL] option was modified by
inserting the necessary coding logic to refresh the ScreenMan data input
screen when the Means Test notification message rearranged the data input
process. By refreshing the screen, the data input flow will return to
the next data input field.
Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem
Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem
was discovered in the coding logic used to set a variable that contained
the internal entry number of the selected drug. This problem was not
discovered in the initial release of BCMA V 2.0.
Corrective Action: The BCMA Print Label [PSBO BL] option was modified by
inserting the correct coding logic to extract and store the selected drug
internal entry number in the proper variable.
Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem
was discovered in the drug validation process used to compare the
was discovered in the drug validation process used to check the patient
medication orders. The option only validated medication orders that were
classified a Unit Dose and it did not validate medication orders that
were classified as IV orders containing IV Additives and IV Solutions.
Corrective Action: The BCMA Print Label [PSBO BL] option was modified
by inserting the proper coding logic to validate IV orders that contained
IV Additives and IV Solutions.
selected drug with medication orders listed for the patient. The drug
validate process was performed only if the system device was set to
BROWSER or the user device.
Install both patches on to the Vista Server and the PSB*3*7
on to the Contingency Workstations as close together as
possible during non-peak times. Since the location of the
Pharmacy Orders "Admin Times" data has been changed
in the HL7 message you could see orders on the workstation
missing this data on orders updated due to transitions of data
during the installation of these patches. The missing data will
correct itself when that order is updated.
Once installed it is suggested that the sites review the
Contingency System reports. Any missing "Admin Times"
can be corrected by running the Single Patient Init
[PSB BCBU INIT SINGLE PT] option or the Workstation
can be re-initialized.
*****************************************************
1. A fix for the '&' delimiter problem with the admin times. The
admin times was moved to another Field of the HL7 message
in the pharmacy patch PSJ*5.0*123.
This patch compensates for the pharmacy change.
*******************Important Note********************
2. When a user was added, edited or terminated, BCMA Contingency
Software would be called and the user would be evaluated,
and if appropriate be transmitted to the BCMA Contingency
Workstations. This evaluation was not occurring correctly.
As a result, all users added, changed or terminated were being
transmitted to the workstations. An additional screen was added
to ensure that only the appropriate users accounts were
transmitted to the workstation.
3. When a user had multiple divisions defined under their user
account and the workstations were setup using the
multidivisional capability the users divisions were not
interpreted correctly. A bug was found in the code that
looped through the user's division multiple and was corrected.
4. The user Update portion of the BCMA Contingency was not checking
the status of the "PSB BKUP ONLINE" parameter. Additional code
was added to check for the status of the "PSB BKUP ONLINE"
Sites running the Bar Code Medication Administration (BCMA)
parameter. If the parameter is set to "NO" then no updates
will be transmitted to the workstation from the user portion
of the package.
Contingency Software must install this patch on all
Contingency workstations in addition to being installed
on to the Vista Server. This patch is being released in
conjunction with the Inpatient Pharmacy patch PSJ*5*123.
BCMA will ignore all BCMA Medication Log (file #53.79)records with
Action Status field (field #.09) equal to ""; and when appropriate,
BCMA will send an electronic message (e-message) to members of the
mail group that is specified via the BCMA Site Parameter - "Mail
Groups/Due List Error", when such a record is processed. The
subject line of this e-message will read "BCMA - Admin XXXX
Problem". The subject line of this e-message will contain the
internal entry number (IEN), identifying the errant BCMA Medication
Log (file #53.79) record. That IEN is represented above by the
text "XXXX". PSB*3.0*11 will allow access to the errant records via
1. Problem: Remedy #HD0000000092269
Manual Medication Entry [PSB MED LOG NEW ENTRY] option for deletion
or correction. The errant records may be accessed using
Manual Medication Entry [PSB MED LOG NEW ENTRY] option
by users possessing the PSB Manager Key or the user who initiated
that administration. Details about the errant administration are
within the e-message sent. The e-message will contain data
necessary to reprocess, via the Manual Medication Entry [PSB MED LOG
NEW ENTRY] option, that incomplete and errant administration.
The following is an example e-message:
**************************************************************************
Bar Code Medication Administration (BCMA) software errors at line
Subj: BCMA - Admin 11111 Problem [#22222222] 07/13/05@13:37 12 lines
From: JACKSON,TODD ELLIS In 'IN' basket. Page 1
-----------------------------------------------------------------------
The following administration was NOT displayed
on the Virtual Due List
Order Number....: 21V
Orderable Item..: HEPARIN SOLN
Patient.........: BCMAPATIENT,ONE (000-00-9678)
"EN+78^PSBVDLPB" when a BCMA Medication Log (file #53.79) record
Ward/Bed........: 7A GEN MED 724-A
Reason..........: JUL 13, 2005@07:00 admin's ACTION STATUS is "UNKNOWN".
Schedule........: Q3H
Action Dt/Tm....: JUL 13, 2005@11:32:50
BCMA Med Log IEN: 11111
User............: ( # 00000000000 ) BCMAUSER,ONE
**************************************************************************
Per the above example, to correct the example, errant entry #11111,
the specified "User" or a person holding the PSB Manager Key may use
being processed has its Action Status (field #.09) equal to "" .
the Manual Medication Entry [PSB MED LOG NEW ENTRY] option and
correct the "Reason" for the "BCMA - Admin Problem"; that person can
correct that "JUL 13, 2005@07:00 admin's ACTION STATUS" per the
specified patient and order, via corresponding responses to Manual
Medication Entry [PSB MED LOG NEW ENTRY] option prompts. The
"correction" is to properly complete or delete that incomplete
administration.
An e-message triggered by an incomplete administration of a Pro
Re Nata (PRN) [As Needed] medication must be maintained via VISTA
The errant record is the result of an administration not properly
File Manager (FileMan). The IEN of the entry that needs corrected
is labeled "BCMA Med Log IEN:" within the e-message as well as
displayed in the e-message's subject line, immediately after the
text "BCMA - Admin".
It is possible to correct any errant BCMA Medication Log (file
#53.79) entry using FileMan and the IEN supplied by this e-message.
2. Problem: Remedy #HD0000000093022
saved/discarded via Manual Medication Entry[PSB MED LOG NEW ENTRY]
The Manual Medication Entry [PSB MED LOG NEW ENTRY] option does not
maintain the "Given" status per medication patch administrations on
the BCMA Virtual Due List (VDL). The user is unable to determine
which administered patch must be removed when the VDL does not
display the patch as "Given".
Corrective Action:
A patch administered via the Manual Medication Entry [PSB MED LOG
NEW ENTRY] option will show as "Given" on the BCMA VDL.
3. Problem: Remedy #HD0000000103739
The Manual Medication Entry [PSB MED LOG NEW ENTRY] option
malfunctions when attempting to administer an "odd schedule" order
on days the order is not scheduled to be administered.
Corrective Action:
Display appropriate data when "odd schedule" order administrations
are attempted.
Corrective Action:
This patch, in conjunction with PSJ*5*406, will resolve the following issue:
Problem:
--------
The VA North Texas Health Care System reported that when displaying and
printing patient order the print out includes removal times for medications
that does not require removal. The source of the problem was identified in
the schedule used for these orders. If it contains the ampersand character
(&), e.g. AC&HS, it shifts fields within the HL7 message communicated between
the main VistA system and the BCBU workstation, which causes it to populate
the REMOVE TIMING field (#7.4) within the ORDER NUMBER sub-file (#53.701) in
the BCMA BACKUP DATA file (#53.7).
Solution:
--------
Changed the routine PSJHL3 via the PSJ*5*406 patch to escape the schedule
field value before including it in the HL7 message bound to the BCBU
workstation and changed the processing of the incoming message to un-scape
schedule field value before parsing when at the BCBU workstation.
Technical Resolution:
1) INC11397447 - BCMA Backup workstation patient print out and order display
---------------------
This patch changes the routine ALPBHL1U at line tag RXE+29 to un-escape the
schedule field value before parsing when processing the incoming HL7 message
at the BCBU workstation.
removal times for INHALATION Medications
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1) INC11397447 - BCMA Backup workstation patient print out and order display
removal times for INHALATION Medications
130b
DATE APPLIED: 2021-04-29 00:00:00
DESCRIPTION:
Backup of PSB*3.0*130 on Apr 29, 2021
Warning: Installing this backup patch message will install older versions
of routines and Build Components (options, protocols, templates, etc.).
Please verify with the Development Team that it is safe to install.
This patch will resolve the following issues:
Problem:
-------
The Audie L. Murphy Memorial Veterans' Hospital reported that when they
submitted a missing dose for an inpatient order with 3 or more dispense drugs
associated with it and later scanned the medication received BCMA Med Logs only
had a record of the first and last dispense drug associated with the order.
Some orders require a combination of dispense drugs to achieve the exact dose
ordered. For example: an order of 75MG for Prednisone would require a
combination of 3 20MG tablets, plus 1 10MG table plus 1 5MG tablet. Upon
research it was determined that this issue was introduced by patch PSB*3*99,
issue #3 (I9892810FY16). In addressing that issue the patch accidentally
introduced the issue reported above. This issue is also being considered a
Patient Safety Issue (PSI) and the number assigned by the Patient Safety team
is HITPS-7596.
Resolution:
----------
The software was modified to prevent the deletion of some of the dispense
drugs in the BCMA Medication Log when 3 or more dispense drugs are marked
1) INC14580997 - BCMA Missing Dose Routing BUG
missing doses on an order and later are scanned.
Technical Resolution:
--------------------
Modified the line UPDATED+97 on the routine PSBML2 to not mark a dispense drug
to be deleted from the BCMA Medication Log if it was previously populated with
an valid dispense drug in the order.
Patient Safety Issues (PSIs):
HITPS-7596
-----------------------------
HITPS-7596
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1) INC14580997 - BCMA Missing Dose Routing BUG
HITPS-7596
123b
DATE APPLIED: 2021-05-12 00:00:00
DESCRIPTION:
Backup of PSB*3.0*123 on May 12, 2021
Warning: Installing this backup patch message will install older versions
of routines and Build Components (options, protocols, templates, etc.).
Please verify with the Development Team that it is safe to install.
Backup of PSB*3.0*106 on Jul 13, 2021
Warning: Installing this backup patch message will install older versions
of routines and Build Components (options, protocols, templates, etc.).
Please verify with the Development Team that it is safe to install.
The description of this build can be found in the National Patch Module
under PSB*3*106.
108b
DATE APPLIED: 2021-07-13 00:00:00
DESCRIPTION:
Backup of PSB*3.0*108 on Jul 13, 2021
Warning: Installing this backup patch message will install older versions
of routines and Build Components (options, protocols, templates, etc.).
Please verify with the Development Team that it is safe to install.
Backup of PSB*3.0*82 on Aug 09, 2021
Warning: Installing this backup patch message will install older versions
of routines and Build Components (options, protocols, templates, etc.).
Please verify with the Development Team that it is safe to install.
The following enhancements were made in this patch:
1. The Status and Schedule Type will have their own columns with their
values spelled out, e.g., G will be 'Given' and P will be 'PRN'.
2. Units Ordered is being added as a new column.
3. Previous statuses will be displayed in reverse chronological order.
This patch will resolve the following issue:
Backup (BCBU) is pulling information from vista incorrectly into the
BCMA BACKUP DATA file (#53.7) for the field name "SUPPLEMENTAL COMMENTS".
This field contains all special instructions, provider comments, or other
print information pertinent to this order. The NTE notes segment in the
HL7 message (i.e. "NTE^6^L" and "NTE^21^L") is not removing the data
correctly when it gets an update into the BCMA BACKUP DATA file (#53.7).
This is the reason why it is displaying incorrectly in BCBU workstation.
1) INC15616683 - BCMA (Bar Code Medication Administration) Backup (BCBU)
workstation patient prints out and order display is
incorrect for the field name "SUPPLEMENTAL COMMENTS"
in BCMA BACKUP DATA file (#53.7)
Problem:
--------
The Honolulu VA Pacific Islands Health Care System reported the Barcode
This patch addresses the following issues:
Problem:
--------
The "B" index for fields ADDITIVES or SOLUTIONS is not created when the
IEN of either is 1. The ADDITIVES field points to the IV ADDITIVES file
#52.6 and the SOLUTIONS field points to the IV SOLUTIONS file #52.7. In
routine PSBMD these fields are set to a value of 1 as a placeholder
before the filer routine (FILE^DIE) is called. When the IEN of the field
is also 1 (pointer in file #52.6 or file #52.7) the index does not get
created because the filer routine doesn't detect a change and doesn't set
the index. This issue was found while analyzing another ticket.
Resolution:
-----------
Routine PSBMD is modified to set the value of the placeholder to 0
instead of 1. This ensures that the filer routine will create the "B"
index correctly.
Technical Resolution:
---------------------
1. INC19372204 - Missing "B" index for solution, Addictive in File 53.68
Lines modified: RPC+37, RPC+39, RPC+42, RPC+43
Before this patch these lines set the following
^PSB(53.68,+PSBIENS,.6,I,0)=I
^PSB(53.68,+PSBIENS,.7,I,0)=I
^PSB(53.68,+PSBIENS,.6,I,0)=X
^PSB(53.68,+PSBIENS,.7,I,0)=X
After the patch these lines set the following:
^PSB(53.68,+PSBIENS,.6,I,0)=0
^PSB(53.68,+PSBIENS,.7,I,0)=0
^PSB(53.68,+PSBIENS,.6,I,0)=0
^PSB(53.68,+PSBIENS,.7,I,0)=0
Defect Tracking System Ticket(s) & Overview:
1. INC19372204 - Missing "B" index for solution, Addictive in File 53.68
Description:
Defect Tracking System Ticket(s) & Overview:
1. INC21077835 - BCBU NOT SHOWING ACCURATE PRN MEDICATION EXPIRE DATE
Problem:
--------
Patient with 2 PRN medications (both oral medications) set to expire
1/21/22@2359 printed contingency MAR that shows medication expires
1/20/22@2359. Further testing showed that the same issue is seen with IV
===========
orders.
Resolution:
-----------
Modify routine ALPBFRM1 so that the column for the day of the stop will
not be asterisks.
Technical Resolution:
---------------------
Routine ALPBFRM1 is modified as follows:
Line added at ADMTIM+16:
. . S
ALPBNOAS=$S(ALPBPRNG:0,$$OTYP^ALPBUTL($P($G(DATA(3)),"^"))="IV":0,1:1)
This line sets ALPBNOAS to 0 when the order is PRN or IV
Line ADMTIM+17 is modified:
&ALPBNOAS is added to the IF condition so time is not stripped from
START/STOP times when the order is PRN or IV
This patch addresses the following issues:
Line ASTER+3 is modified:
&(ALPBNOAS) is added to the IF condition so that '******' is not
populated in the column on STOP day
1. INC21077835 - BCBU NOT SHOWING ACCURATE PRN MEDICATION EXPIRE DATE
This build introduces changes to allow the BCMA GUI to display additional
allergy information in the Patient Allergy List, add the CPRS Order Check
to the Display Order report, and add remote allergies to the VDL
Allergies list.
Defect Tracking System Ticket(s) & Overview:
Resolution:
-----------
The BCMA code (routine PSBVDLU1) was trying to decide if the med should
be given on Tuesday using the 2 letter code TU, the schedule name
SATURDAY contains TU and determines that it should be given on Tuesday,
which was incorrect. The code is modified to prevent this from occurring.
Technical Resolution:
---------------------
Lines OKAY+40 through OKAY+43 is changed from
S PSBDOW=$P("SU^MO^TU^WE^TH^FR^SA",U,%Y+1) ;p145
I $F(PSBSCH,PSBDOW)>0 S PSBOKAY=1 Q PSBOKAY
S PSBOKAY=0
Q PSBOKAY
To
;PSB*3*145 Prevent Saturday schedule from being given on Tuesday
N PSBSCH1 S PSBSCH1=PSBSCH
I PSBSCH1["SATU" S PSBSCH1=$TR(PSBSCH1,"SATU","SATA")
1. INC30190209 - SATURDAY SCHEDULE PROMPT BCMA VDL TO ADMINISTER DRUG SAT
S PSBDOW=$P("SU^MO^TU^WE^TH^FR^SA",U,%Y+1)
;I $F(PSBSCH,PSBDOW)>0 S PSBOKAY=1 Q PSBOKAY
I $F(PSBSCH1,PSBDOW)>0 S PSBOKAY=1 Q PSBOKAY
S PSBOKAY=0
Q PSBOKAY
AND TUESDAY
Problem:
--------
SATURDAY, pharmacy standard schedule prompts BCMA Virtual Due List to
also administer the drug on Tuesday.
This patch addresses one issue: Discharge edits cause deletion of a
patient's record in the BCBU BACKUPDATA (#53.7) file even though the
patient is currently an inpatient.
***
***
This patch is a component of the Bar Code Medication Administration
(BCMA) - Health Services Commitee (HSC) project and is the development of
phase one of the BCMA-HSC Coversheet. PSB*3.0*16 will interface between
BCMA databases and the new BCMA Coversheet and its Graphical User
Interface (GUI).
*************************************************
HD0000000118033
Test Sites:
===========
UPSTATE NEW YORK HCS
SAN FRANCISCO, CA
MEMPHIS, TN
LITTLE ROCK, AR
Routine Summary:
================
The second line now reads as follows:
<TAB>;;3.0;BAR CODE MED ADMIN;**[patch list]**;Mar 2004
CHECK^XTSUMBLD results:
Routine Before Patch After Patch Patch List
------- ------------ ----------- ------------------
ALPB8 ------ 1016866 8
ALPBOP ------ 1898706 8
ALPBPWRD 7025105 9768019 8
ALPBPALL 6006540 6414482 8
ALPBPPAT 5702674 5081715 8
ALPBFRM1 9887439 11248156 8
ALPBUTL3 3052806 4245189 8
ALPBCBU 1637834 1710946 8
ALPBINP 9416944 10451599 8
ALPBUTL1 6143314 6275666 8
Enhancements and issues addressed in this patch are as follows:
ALPBHL1 14736637 14979457 7,8
ALPBBK 6214167 6214134 8
ALPBELOG 6391337 6391337 8
ALPBFRM2 8886579 8886579 8
ALPBFRMU 4053521 4295514 8
ALPBGEN 10414189 10201828 7,8
ALPBGEN1 8591971 8809016 8
ALPBGEN2 2679718 2679718 8
ALPBIN 4105691 4105691 8
ALPBIND 5809117 5809117 8
ALPBPARM 8937865 9127203 8
ALPBSP1 4545482 4545482 8
ALPBSP2 845669 845669 8
ALPBSPAT 2404489 2404489 8
ALPBSWRD 5435921 5435921 8
ALPBUTL 9642997 9642997 8
ALPBUTL2 1954969 1954969 8
Patch retrieval Instructions:
====================================
To obtain the software use one the following OI Field Offices'
ANONYMOUS.SOFTWARE directories:
Albany ftp.fo-albany.domain.ext anonymous.software
Hines ftp.fo-hines.domain.ext anonymous.software
Salt Lake City ftp.fo-slc.domain.ext anonymous.software
The distribution file is as follows.
1. It was reported by a site that Lodgers and Dom patients were
PSB_3_8.KID
PSB_3_8.ZIP (optional see note below)
****************Note for optional zip file********************
The Zip file in this patch contains an updated Cache.Dat file.
On new installations it is recommended that you use the new
Cache.dat file released with this patch. If this is used for
an existing workstation then the workstation would need to
be initialized with patient data.
creating alerts. Lodgers and Dom patient are now screened.
**************************************************************
The documentation distribution includes:
FILE NAME DESCRIPTION
PSB_3_BCBU_IG_R0206.PDF BCMA Backup System (BCBU)
INSTALLATION GUIDE
Installation Instructions:
==========================
This patch can be installed with users on the system. Installation will
take less than 1 minute.
Suggested time to install: non-peak requirement hours.
1. From the Kernel Installation & Distribution System menu, select
2. It was reported that when a patient was discharged the discharged
the LOAD DISTRIBUTION option and load PSB_3_8.KID
2. Review your mapped set. If the routines are mapped, they should
be removed from the mapped set at this time.
3. From the Kernel Installation & Distribution System menu, select
the Installation menu.
4. From this menu, you may select to use the following options
(when prompted for INSTALL NAME, enter PSB*3.0*8):
message was not always being sent to the workstations and an alert
a. Backup a Transport Global - this option will create a backup
message of any routines exported with the patch. It will NOT
backup any other changes such as DDs or templates.
b. Compare Transport Global to Current System - this option will
allow you to view all changes that will be made when the patch
is installed. It compares all components of the patch (routines,
DDs, templates, etc.).
c. Verify Checksums in Transport Global - this option will ensure
the integrity of the routines that are in the transport global.
was being generated. The problem was caused by how movements were
5. Use the Install Package(s) option and select the package PSB*3.0*8.
6. When prompted "Want KIDS to INHIBIT LOGONs during the install?
YES//" respond NO.
7. When prompted "Want to DISABLE Scheduled Options, Menu Options, and
Protocols? YES//" respond NO.
8. If any routines were unmapped as part of step 2, they should be
returned to the mapped set once the installation has run to
sent to the Contingency by Patient Movements. The Contingency will
completion.
Post-Installation Steps (Important)
A new option, PSB BCBU WRKSTN PURGE ORDERS, was released as part of
PSB*3.0*8 build. IRM staff must add it to the list of Scheduled Startup
Options in TaskMan on the workstations. To do this, access menu
compensates for these issues now.
Schedule/Unschedule Options on the TaskMan Management menu. This option
should be queued to run during non peak hours and set with a rescheduling
frequency of 1D. Review the Workstation parameter settings using the PSB
BCBU WRKSTN PARAMETER EDIT option to make changes on how much patient
historical data is retained
Example Installation:
=====================
Select Installation Option: 1 Load a Distribution
Enter a Host File: C:\BCMABU\PSB_3_8.KID
KIDS Distribution saved on Jun 16, 2005@09:04:12
Comment: BCBU UPDATES AND CORRECTIONS
This Distribution contains Transport Globals for the following Package(s):
3. When printing the Medication Administration Report (MAR) for current
Build PSB*3.0*8
Distribution OK!
Want to Continue with Load? YES//
PSB*3.0*8
Use INSTALL NAME: PSB*3.0*8 to install this Distribution.
orders it would also include any non-active orders for the current
Select Installation Option: 6 Install Package(s)
Select INSTALL NAME: PSB*3.0*8 Loaded from Distribution Loaded
from Distribution 6/16/05@08:09:36
=> BCBU UPDATES AND CORRECTIONS ;Created on Jun 16, 2005@09:04:12
day being printed. The report now goes by date and time.
This Distribution was loaded on Jun 16, 2005@08:09:36 with header of
BCBU UPDATES AND CORRECTIONS ;Created on Jun 16, 2005@09:04:12
It consisted of the following Install(s):
PSB*3.0*8
Checking Install for Package PSB*3.0*8
Install Questions for PSB*3.0*8
Incoming Files:
53.7 BCMA BACKUP DATA
Note: You already have the 'BCMA BACKUP DATA' File.
53.71 BCMA BACKUP PARAMETERS
4. A new purge utility has been introduced for the workstation. It
Note: You already have the 'BCMA BACKUP PARAMETERS' File.
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO
Want KIDS to INHIBIT LOGONs during the install? YES// NO
********************Important Note***************
allows the site to define how much historical data to maintain on the
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// TCP/IP Terminal
Install Started for PSB*3.0*8 :
workstation. Any unwanted data will be removed from the workstation.
Jun 16, 2005@08:12:22
Build Distribution Date: Jun 16, 2005
Installing Routines:
Jun 16, 2005@08:12:22
Installing Data Dictionaries:
Jun 16, 2005@08:12:22
Installing PACKAGE COMPONENTS:
Installing FORM
Installing OPTION
Jun 16, 2005@08:12:23
5. The way the Med Log information is being displayed on the MAR has
Running Post-Install Routine: POST^ALPB8
Updating Routine file...
Updating KIDS files...
PSB*3.0*8 Installed.
Jun 16, 2005@08:12:23
changed. In the previous version the information was displayed by date
Install Message sent #2318
Install Completed
entered and the user had to select a starting date when running the
MAR. Depending on the frequency of the MED Log this could cause the
report to be long. The report now reverses the order of the Med Log
information so the report displays the most recent first. The user can
then opt for how many to display by numeric value such as 1, 2 or more.
6. A blank page was added between the patients on multi patient
reports for easier sorting.
7. Provider comments were moved to be displayed along with the Drug
and Give information.
8. The sorting of orders on the MAR reports have been grouped by the
order type. Types include Pending, Unit Dose, IV and PRN.
If the site is running the BCMA Contingency software then this
9. A place holder for the Last Action of drugs has been added to the
reports. A future patch will complete the functionality.
10. A problem with Pending orders remaining on the workstation when
replacement orders are done by pharmacy has been resolved.
11. A problem was discovered with the user access updater. When a user's
name changed it did not update the Contingency workstations
correctly.
patch must also be installed on the workstations. Once installed
12. A <UNDEFINED>NURV+16^ALPBCBU error has been resolved.
13. A problem with updating the Contingency workstations during a patient
movement activity has been addressed.
14. Added the function to sort MARS by Room/Bed or by Patient Name.
15. Patients that had no allergies reported to the contingency do not
display any allergies data on a MAR. Now when no allergies are found
on the contingency, the following will display on the MAR. "Allergies:
it is suggested that the sites review the Contingency system
No allergies reported to the Contingency"
16. Possibility of routine ALPBPWRD erroring out at line
..S ^TMP($J,"BCBU",+ALPRM,ALPRM,ALPBD,ALPBPTN)=ALPBIEN
When sorting by room/bed Cache tries to convert certain room/beds like
5E155 and produces a <MAXNUM> error. The problem occurs when the
variable is manipulated. Cache will take the 5E155 and convert it to
"5" appended with 155 zeros. A code change was made to prevent this
issue.
reports.
Associated Tickets
=================
HD0000000093730
HD0000000068823
HD0000000068579
HD0000000068341
HD0000000068274
HD0000000068227
HD0000000068220
HD0000000068196
HD0000000068158
HD0000000068107
HD0000000068024
HD0000000068021
HD0000000067859
HD0000000067827
HD0000000067769
HD0000000067729
HD0000000067714
HD0000000096190
This patch addresses three Remedy tickets, HD68121, HD113034, and HD90393.
the undefined error will not occur. This locking fix was created by the
Minneapolis IRM staff, and has been working in their production area for
months. The fix is being brought back to the VMP group so it can become
part of a national patch release, and other sites can avoid this error in
the future.
The second issue, HD113034, happens when a medication PATCH (such as
Fentanyl) is marked as REMOVED after initially being given to the
patient. If you right-click the mouse on the order in BCMA and mark the
patch as "REMOVED", when you subsequently check the med log, the units
given remains 1. However, if you use the BCMA menu option FILE/EDIT Med
Log and mark it "REMOVED", the units given becomes 0, and the audit trail
shows "Doses given '1' deleted". The correct value for units given is
actually 1 (as right-clicking the mouse shows), because the medication
was indeed given, but the patch was subsequently removed, not deleted or
refused.
The third issue in this patch, HD90393, addresses a printing problem with
the PRN Effectiveness report when it is printed by Ward/Room-Bed. When
this printing filter is applied, the report prints in patient DFN order,
not Ward/Room-Bed order. This fix corrects a problem in the BCMA code so
that when the Ward/Room-bed filter is applied, the report will print
properly.
The first issue, HD68121, is the result of a file locking problem with
the routine PSBMD. This error only appeared after the site converted to
Cache' version 5. There is an undefined variable error created with
Missing Dose reports in Pharmacy, even though a record is created in
^PSB(53.68). By attempting to lock the ^PSB(53.68) file before
attempting to print the report, it will ensure that the file exists so
This patch addresses Remedy Ticket HD127231, which arose after the
the first six lines of the orderable item in duplicate.
The fix included in this patch will still print the patient header
information on subsequent MAH pages, but it will not reprint the first
six lines of the orderable item information.
**NOTE** This fix only affects the report when printed to a printer.
This does not affect the GUI display or printing the report to the
terminal screen.
install of patch PSB*3*20. Patch PSB*3*20 added the patient header
information to the MAH report if the report for a medication ran longer
than one page. Additionally, PSB*3*20 was designed to reprint the first
six lines of the orderable item information on subsequent pages to help
the nurses keep track of what medication they were viewing
on the MAH report. However, when the next medication on the report was
due to be printed, and a page break occurred before the orderable item
information was printed, the second page of the report printed
1. Problem: NOIS MAD-0104-40858
2. Problem: NOIS BUT-0204-20463
The Medication Administration History [PSBO MH] option and the Due
List [PSBO DL] option add an exclamation point (i.e., Spec Inst:
!Please verify) to the prefix of a Special Instruction.
Corrective Action: The Medication Administration History [PSBO MH]
option and the Due List [PSBO DL] option correctly removes
the exclamation point (i.e., Spec Inst: Please verify) added
to a Special Instruction.
The Bar Code Medication Administration (BCMA) reports,
3. Problem: NOIS BED-0204-10327
When a clinician administers a Pro Rea Nata (PRN) medication using
the Manual Medication Entry [PSB MED LOG NEW ENTRY] option, and the
administration date/time is set to an earlier timeframe, the PRN
administration date/time displays incorrectly on BCMA PRN
Effectiveness Log Report as the entered date/time of this
administration occurred.
Corrective Action: When a clinician administers a PRN medication
with the exception of the Cumulative/Vitals Measurement Report, does
using the Manual Medication Entry [PSB MED LOG NEW ENTRY] option, and
the administration date/time is set to an earlier timeframe, the PRN
administration date/time displays correctly on the BCMA PRN
Effectiveness Log Report as the actual date/time of the
administration.
4. Problem: NOIS NTH-0304-72663
A "Null subscript" error occurs at routine line "EN+4^PSBVDLPA"
when there is single patient with data entered in the BCMA Medication
Log File (#53.79) and indexes. This error occurs during the
not display allergy information in the reports header.
initial implementation of the BCMA Graphical User Interface (GUI)
system.
Corrective Action: The initial implementation of the BCMA GUI will
not generate a "Null subscript" error at routine line "EN+4^PSBVDLPA".
Corrective Action: The BCMA Reports, with the exception of the
Cumulative/Vitals Measurement Report, displays allergy information in
the reports header. The Reactions header has also been removed
from the report and replaced with the "ADRs:" header.
***************************Important Note*************************
1. It was reported that after loading Patch PSB*3*8, the medication log
Select Installation Option: 1 Load a Distribution
Enter a Host File: USER$:[COWNIEK]PSB_3_29.KID
KIDS Distribution saved on Apr 13, 2006@16:09:30
Comment: patch 29
This Distribution contains Transport Globals for the following Package(s):
history was no longer printing.
PSB*3.0*29
Distribution OK!
Want to Continue with Load? YES//
Loading Distribution...
PSB*3.0*29
Use INSTALL NAME: PSB*3.0*29 to install this Distribution.
Select Installation Option: 6 Install Package(s)
Select INSTALL NAME: PSB*3.0*29 Loaded from Distribution
4/17/06@12:31:58
=> patch 29 ;Created on Apr 13, 2006@16:09:30
Example:...
This Distribution was loaded on Apr 17, 2006@12:31:58 with header of
patch 29 ;Created on Apr 13, 2006@16:09:30
It consisted of the following Install(s):
PSB*3.0*29
Checking Install for Package PSB*3.0*29
Install Questions for PSB*3.0*29
Incoming Files:
53.7 BCMA BACKUP DATA (Partial Definition)
Note: You already have the 'BCMA BACKUP DATA' File.
Want KIDS to INHIBIT LOGONs during the install? YES// NO
BCMA MEDICATION LOG HISTORY
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// UCX TELNET SESSION
Install Started for PSB*3.0*29 :
Log Date Message Log Entry Person
PSB*3.0*29
--------------------------------------------------------------------------
Apr 17, 2006@12:34
Build Distribution Date: Apr 13, 2006
Installing Routines:
Apr 17, 2006@12:34
No entries since the above date are on file.
Installing Data Dictionaries:
Apr 17, 2006@12:34
Updating Routine file...
Updating KIDS files...
PSB*3.0*29 Installed.
Apr 17, 2006@12:34
Install Message sent #1504712
Install Completed
Routine Summary:
This was caused by a missing cross reference (IMLOG) in file 53.7.
================
The second line now reads as follows:
<TAB>;;3.0;BAR CODE MED ADMIN;**[patch list]**;Mar 2004
CHECK^XTSUMBLD results:
Routine Before Patch After Patch Patch List
If the site is running the BCMA Contingency software then this
Cross reference has been added.
------- ------------ ----------- ----------
ALPBPALL 6414482 6407974 8,29
Routine Information:
====================
Routine Name: ALPBPALL
Checksum:
CHECK1^XTSUMBLD results:
Routine Before Patch After Patch Patch List
------- ------------ ----------- ----------
ALPBPALL 25867705 25843033 8,29
2. It was reported that the Print all option was not working correctly.
Routine ALPBPALL has been corrected.
Associated Tickets
==================
HD0000000139114
HD0000000138995
patch must also be installed on the workstations. Once installed
HD0000000135330
Test Sites:
===========
BIRMINGHAM, AL
BRONX, NY
MILWAUKEE, WI
MOUTAIN HOME, TN
it is suggested that the sites review the Contingency system
Patch retrieval Instructions:
====================================
To obtain the software use one the following OI Field Offices'
ANONYMOUS.SOFTWARE directories:
Albany ftp.fo-albany.domain.ext anonymous.software
Hines ftp.fo-hines.domain.ext anonymous.software
reports.
Salt Lake City ftp.fo-slc.domain.ext anonymous.software
The distribution file is as follows.
PSB_3_29.KID
There is no documentation distribution included in this patch.
******************************************************************
Installation Instructions:
==========================
This patch can be installed with users on the system. Installation will
take less than 1 minute.
Suggested time to install: non-peak requirement hours.
1. From the Kernel Installation & Distribution System menu, select
the LOAD DISTRIBUTION option and load PSB_3_29.KID
2. From the Kernel Installation & Distribution System menu, select
the Installation menu.
3. From this menu, you may select to use the following options
(when prompted for INSTALL NAME, enter PSB*3.0*29):
a. Backup a Transport Global - this option will create a backup
message of any routines exported with the patch. It will NOT
backup any other changes such as DDs or templates.
Issues addressed in this patch are as follows:
b. Compare Transport Global to Current System - this option will
allow you to view all changes that will be made when the patch
is installed. It compares all components of the patch (routines,
DDs, templates, etc.).
c. Verify Checksums in Transport Global - this option will ensure
the integrity of the routines that are in the transport global.
4. Use the Install Package(s) option and select the package PSB*3.0*29.
5. When prompted "Want KIDS to INHIBIT LOGONs during the install?
YES//" respond NO.
6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and
Protocols? YES//" respond NO.
Example Installation:
=====================
Issues (PSI) and Remedy Ticket resolution and BCMA Coversheet refinement.
8. Enhancement: Enhanced "*UNKNOWN* Action Status" support.
BCMA Medication Log File (File #53.79) entries having unknown
Action Status (field #.09) data can be maintained via the GUI BCMA
Edit Med Log only. These entries may be maintained by persons holding
the BCMA manager's key [PSB MANAGER] or that user unable to complete
the original administration. PSB*3.0*13 supports the VISTA "Unknown
Action Status Report" option [PSBO XA]. The [PSBO XA] option
provides persons holding the BCMA manager's key [PSB MANAGER]
resource to generate a report to display BCMA Medication Log File
(#53.79) entries having "unknown" Action Status (field #.09) data.
***
Users holding the BCMA manager's key [PSB MANAGER] can access the
PSBO XA report via the BCMA GUI as well. BCMA has been enhanced to
display a "pop-up box" when a user begins an action on an order
9. Enhancement: Saved Coversheet Personal Parameters
PSB*3.0*13 will maintain personal parameters per BCMA Coversheet
views to be saved and retrieved when using BCMA.
1. Problem: PSI-05-064
BCMA functionality enables a BCMA user to edit the free text
BCMA MEDICATION LOG FILE-DISPENSE DRUG SUBFILE (# 53.795) "Units
of Administration" (field #.04) for an administered medication, when
using the Edit Medication Log. Consequently, the GUI Edit
Medication Log (Edit Med Log) allows a BCMA user to modify text in
the field labeled "Units" of the "BCMA - Edit Med Log" dialog box.
***
The user is able to change the "Units" from "PATCH" to any other text
value. Changing a "PATCH" medication to some other "Units", causes
BCMA to not process the administration properly; and causes the BCMA
Virtual Due List (VDL) to not present the administration properly.
Corrective Action:
The BCMA GUI Edit Med Log will not allow any BCMA user to edit the
BCMA MEDICATION LOG FILE/DISPENSE DRUG SUBFILE (# 53.795) "Units
of Administration" (field # .04) of an administered "PATCH"
medication.
2. Problem: PSI-05-032
The VDL displays a GIVEN medication patch until it has been marked as
"REMOVED". This is causing some confusion to users.
Corrective Action:
BCMA will provide a site parameter that will specify the number of
days (7-14) a GIVEN patch will display on the VDL. The count of
days the GIVEN patch displays on the VDL begins when the
medication order expires. This parameter may be set to ""
This patch is a component of the Bar Code Medication Administration
(null) to allow GIVEN patches to display on the VDL until it is
marked as REMOVED.
3. Problem: PSI-05-115
The Special Instructions on the VDL will display the entire Special
Instructions by wrapping the text as needed using the spaces in the
Special Instructions. However, ff a word or phrase (without spaces)
in the Special Instructions can not be wrapped due to the word or
phrase being longer then the width of the column, the text would be
(BCMA) Version 3.0. The main function of PSB*3.0*13 and the
truncated when the text ran into the right side of the column. In
addition, when the above happens, some of the ending words in the
special instructions may be omitted as well.
Correction Action:
When a word or phrase (without spaces) can not be wrapped and does
not fit in the column width, the text will be truncated with an
ellipsis to indicate that a portion of the word or phrase was
truncated. The occasional omission of ending words in the special
instructions will be corrected.
corresponding BCMA Graphical User Interface (GUI) software (BCMA Version 3
4. Problem: HD0000000121694
While a medication patch is being "administered" using Manual
Medication Entry[PSB MED LOG NEW ENTRY], that particular scheduled
administration does not display on the BCMA Virtual Due List (VDL).
Corrective Action:
Display the saved "action status" of an administration, while it is
being administered using Manual Medication Entry [PSB MED LOG NEW
Patch 13 [3.0.13]) is to support BCMA v3.0 Clinical Context Object
ENTRY]
5. Problem: HD0000000127625
An error occurs when the BCMA coversheet is to display data for one
order only; and that order is an expired, large volume IV.
Corrective Action:
The BCMA Coversheet will display without error when the only order
information to display on the BCMA coversheet pertains to an expired,
Workgroup (CCOW) compliance. The PSB*3.0*13 GUI and this Character User
large volume IV.
6. Problem: HD0000000132184
An error occurs when the BCMA GUI Computerized Patient Record System
(CPRS)/BCMA Medication Order Button (MOB) is used and ORDER
File (#100) PATIENT LOCATION (field #6) data does not link to a
WARD LOCATION File (#42) entry.
Corrective Action:
Interface (CHUI) software (PSB*3.0*13) also support Patient Safety
BCMA will provide HOSPITAL LOCATION File (#44) data per ORDER File
(#100) PATIENT LOCATION (field #6) data when the CPRS/BCMA MOB is
used. CPRS will ORDER File (#100) PATIENT LOCATION (field #6) data
to a HOSPITAL LOCATION File (#44) entry
7. Enhancement: CCOW compliancy
This patch (PSB*3.0*13) will enable BCMA CCOW compliancy.
Enhancement - Compliance with Section 508 of the Rehabilitation Act of
1973:
PSB*3.0*10 and its corresponding BCMA GUI[Version 3 Patch 10
(3.0.10.9)] will assure BCMA is compliant with Section 508 of the
Rehabilitation Act of 1973, after proper installation as defined in
the BCMA 508 Software Requirements Specifications.
Problem #HD0000000159234 - Means Test Pop-up Does Not Display:
Enhancement - Signal BCMA Idle Timeout:
BCMA GUI Version 3 Patch 10 will signal to the user as BCMA Idle
Timeout limit is approaching. There will be an audible "beep" thirty
(30) seconds, twenty (20) seconds, and ten (10) seconds prior to the
idle time limit set via the "BCMA Idle Timeout" site parameter.
Enhancement - Indication When not all Drugs Have Been Scanned Per a
Multiple Drug Order :
Bar Code Medication Administration (BCMA) Graphical User Interface
BCMA GUI Version 3 Patch 10 will display a message box when
the user has not scanned all the dispensed drugs per a medication
order that includes multiple dispensed drugs. The message box will
display, requesting user confirmation.
(GUI) Means Test Pop-Up Does Not Display after the installation of
BCMA GUI Version 3 Patch 13.
Corrective Action:
Modify the BCMA GUI to allow the BCMA GUI Means Test Pop-up to display
when appropriate.
1. Problem: PSI-06-029/HD0000000126326
Processing the BCMA Missed Medications Report causes the client to
"time-out" when the report is to display within the BCMA GUI
Application and prior to sending the report to a printer.
Corrective Action:
Make the Missed Medications Report process faster so the client
does not "time-out".
2. Problem: PSI-06-019/HD0000000130671
There is difficulty determining the application of a medical patch
that has not been marked as REMOVED when that order has expired or
discontinued.
Corrective Action:
Allow the user to view and act on patches for expired or discontinued
orders when the patient's BCMA Virtual Due List (VDL) first opens.
This patch is a component of the Bar Code Medication Administration
3. Problem: PSI-06-056/HD0000000131075
Issues related to extra Pro Re Nata (PRN) doses of medication
ordered as QDPRN or BIDPRN and reports of nurses missing the last
administration time, have cause patient safety concerns.
Corrective Action:
The BCMA PRN administration dialog box will be enhanced to provide the
following features for all PRN administrations: Icon, Schedule, Last
(BCMA) Health Systems Committee (HSC) Phase III project. The main
Given and Reminder checkbox and statement.
4. Problem: PSI-06-014/HD0000000128909
Administration problems have been caused when Med Route abbreviations
on the VDL have been confused.
Corrective Action:
Display the expanded version of the Med Route.
function of PSB*3*32 and the corresponding BCMA Graphical User
5. Problem: PSI-06-060/HD0000000143603
Due to a limitation in the Delphi application, there is a 255-pixel
limit on the row height in the BCMA GUI VDL that results in truncation
of an order when there are a large number of additives/solutions on
the order.
Corrective Action:
Adjust display area of medications on the VDL to compensate for orders
with a large number of items to display.
Interface (GUI) software (BCMA Version 3 Patch 32 [3.0.32.*]) is to
6. Enhancement: New Coversheet Overview Reports.
As a part of the BCMA HSC Phase III, patch PSB*3.0*32 and
PSB.3.0.32 GUI will provide BCMA users with reports that display
Coversheet Overview data. There is a new Coversheet Report for each
Coversheet Overview.
7. Enhancement: Global Report Enhancements.
provide the BCMA user with additional BCMA Coversheet and reporting
Various enhancements have been made to BCMA reports in general. These
enhancements are presented in BCMA HSC Phase III documentation.
8. Enhancement: Coversheet and Other Miscellaneous Enhancements.
A variety of new Coversheet and miscellaneous feature will be
supported with the installation of this patch. The BCMA HSC Phase
III documentation provides details of these new features.
support.
*** ATTENTION: This patch includes a new Graphical User Interface
use. The correct GUI must be installed to support BCMA
Computerized Patient Record System (CPRS) Med Order
functionality ***
For retrieval and installation instructions, please see the Client
Installation Instructions section.
1. Problem: NOIS HWH-0204-41213
The Instructor information does not display in the legend of the
Medication Administration History [PSBO MH] option, and the audit log
(GUI) executable file. Installation of this new GUI is
of the Medication Administration Log [PSBO ML] option.
Corrective Action: The Instructor information displays in the legend
of the Medication Administration History [PSBO MH] option, and the
audit log of the Medication Administration Log [PSBO ML] option.
2. Corrective Action: When student and instructor information is
present at login the GUI BCMA CPRS Med Order button is disabled.
3. Problem: NOIS HUN-0104-20931
REQUIRED in order for the patch to function. The new GUI
Infusing IV bags are duplicated on a "following" order after the
order that was active when the IV bag was infusing has become
"discontinued". The Virtual Due List (VDL) attempts to display
duplicate bags and associates the same IV bags with multiple orders.
Corrective Action:
When an order with an infusing bag is discontinued, the VDL will
either continue to display the infusing bag with the discontinued
order, or the VDL will display the infusing bag with an active
"following" order, but not both.
MUST be installed IMMEDIATELY after the KIDS install in
4. Problem: NOIS ISB-0304-30352
If an IV order with an infusing bag expires and the patient's record
is not accessed using Inpatient Medications (IPM) (e.g., the
Inpatient Order Entry [PSJ OE] option) the following message may
appear, hindering an user's attempt to take action on the order:
"Either the order status or the current scan status displayed
on the VDL does not match the status recorded in VistA! This
may be due to someone editing the order in VistA or another
order for the software to function. This Patch includes a
individual scanning the medication. Your current action will
be canceled and the VDL will be refreshed to reflect the most
current order information."
Corrective Action:
A user will be able to take action on an expired IV order having an
infusing bag via the BCMA GUI VDL as appropriate.
5. Problem: NOIS MOU-0304-32821
The temporary, scratch global ^PSBORDA is automatically monitored and
Post install that corrects problem number six below. The
documented via journaling procedures. It is not necessary to journal
this temporary global since it is used solely as a temporary data
storage area.
Corrective Action:
The global ^PSBORDA will be renamed as an appropriate scratch "^TMP"
global with the first two subscripts being "PSB" followed by "$J".
6. Problem: NOIS ISB-0404-31737
With the release of BCMA Version 2 (PSB*2.0), any unit dose
installation time frame for this post install will vary based
order that is displayed on the "IVP/IVPB" tab and administered will
have a Ward Stock number generated and placed in the IV Unique
ID field (FIELD #.26) of the BCMA Medication Log (FILE #53.79)
The Ward Stock number is stored in the BCMA Medication Log global and
is not displayed on the VDL or any BCMA Report.
Corrective Action:
A unit dose order that is displayed on the "IVP/IVPB" tab and
administered will not have a Ward Stock number generated and placed
in the IV Unique ID field (FIELD #.26) of the BCMA Medication Log
on the size of the site. This build will validate the correct
(FILE #53.79). A post install will clean up all incorrect previous
entries.
version of Bar Code Medication Administration (BCMA) GUI is in
This patch will add the new Barcode Label Print [PSBO BZ] option
to the Bar Code Medication Administration application. Review
the patch description for detail functionality.
This patch contains miscellaneous fixes for the BCMA Contingency plan
functionality.
backup system.
This patch addresses the following remedy tickets:
HD139965 -- Patient data not available on clients after PSB*3.0*8
HD150133 -- Problem with new Contigency set up.
HD189870 -- Variable needs to be NEW'd
This patch also contains an enhancement to the BCBU user init
This patch corrects the following remedy tickets for BCMA issues:
HD189271 - A piece of code in PSBOPM needs to be changed.
HD167891 - Medication Administration History display problem in CPRS
Version 3.0 Managing Scanning Failures (MSF) project. The main function
of PSB*3*28 and the corresponding BCMA GUI software (BCMA Version 3 Patch
28 [3.0.28]) is to document scanning failures during BCMA patient and
medication verification. Please see Release Notes document for more
details on the following enhancements.
1. Enhancement: Document Unable to Scan events. This patch will enable
the user to document Unable to Scan events that occur during BCMA
patient and medication verification. The Computerized Patient Record
System Medical Order Button and the creation of ward stock orders in
ATTENTION: This patch includes a new Graphical User Interface (GUI)
BCMA will not be fully supported by the Unable to Scan functionality.
2. Enhancement: Send a MailMan message for each Unable to Scan event.
When a user documents an Unable to Scan event, a message will
be sent to persons who are members of the mail group established
via the BCMA Site Parameter's Unable to Scan mail group field
setting. This message will also be sent to the user submitting
the Unable to Scan event documentation.
3. Enhancement: Add two new Unable to Scan Reports.
executable file. Installation of this GUI is required immediately
Detailed and summary reports of BCMA Unable to Scan data may be
executed by persons holding the PSB UNABLE TO SCAN security key.
4. Enhancement: Added Division Filtering to Unable to Scan Reports.
The user's division is detected upon login, and used to filter
Entire Facility and Nurse Unit options on the Summary Report, and All
Patients/Wards option on the Detailed Report.
5. Enhancement: Added new PSB*3*32 functionality to the MSF reports.
Patch PSB*3*32 created new report functionality requirements, such as
after the KIDS install for the Patch to function.
allowing a start and stop time, and report preview. For consistency,
these have been included in the MSF reports.
6. Enhancement: Usability.
Made changes based on feedback from the MSF usability study.
7. Enhancement: Allow Action on Infusing or Stopped IV Bags.
Added Take Action on Bag option to the IV Bag Chronology Window to
allow user to take action on infusing or stopped bags without having
to rescan the IV bag.
For retrieval and installation instructions, please see the Client
Installation Instructions section.
This patch is a component of the Bar Code Medication Administration (BCMA)
This patch will correct the following issues.
HD226037 - Initials don't show on MAH or Med log for first action on med
HD190817 - Record needs to show the initials of the nurse who
administered the medication not the initials of nurse who
created the error.
HD255639 - Missing Field Definition.
Partial Correction for
HD260760 - Routine's Don't meet 1995 M standard.
This patch provides the components for the Class III to Class I conversion
project Immunizations Documentation by BCMA.
Included in this patch is a new option named Immunizations Documentation
by BCMA Nightly Task [PSB PX BCMA2PCE TASK].
Patch PSS*1*141 provides the Pharmacy Data Management portion of the
project.
*** ATTENTION: This patch includes a new Graphical User Interface (GUI)
1. Problem: NOIS BUT-1203-21780
chronological order; chronologically latter order activities will display
before earlier order activities.
Bar Code Medication Administration (BCMA) users are not able to re-
instate a medication patch if it had been unintentionally marked as
'REMOVED' via BCMA. This issue has been delegated a 'PATIENT SAFETY'
keyword.
Corrective Action:
The removal of a medication patch may be undone if it had been
unintentionally marked as 'REMOVED'; this may be accomplished by the
user who marked the medication patch as 'REMOVED' or by a user
executable file. Installation of this new GUI is REQUIRED in order
allocated the "PSB MANAGER" key.
2. Problem: NOIS ISB-0204-30176
The prompt "Enter the DATE of Administration: Today//" of the Manual
Medication Entry [PSB MED LOG NEW ENTRY] option has caused confusion.
The user unintentionally accepts the default (i.e. "Today") when
attempting to document a past administration.
Corrective Action:
for the patch to function. The new GUI MUST be installed IMMEDIATELY
The prompt "Enter the DATE of Administration: Today //" will be
replaced by the prompt "Enter the DATE the medication was
administered: //" when using the Manual Medication Entry
[PSB MED LOG NEW ENTRY] option. Also, this new prompt will not accept
the entry of a future date/time for an administration.
3. Problem: NOIS PHO-0904-61033
The BCMA Medication History report does not show large volume IV
medications data when viewed via the Computerized Patient Record System
after the KIDS install in order for the software to function. ***
(CPRS) GUI "Orders/View/Details..." option.
Corrective Action:
The BCMA Medication History report will display large volume IV
medications data when viewed via the CPRS GUI.
4. Problem: NOIS LAH-0404-61280
The user is unable to access a patient's VDL when receiving an error
message containing the text "GETPRNS+17^PSBPRN". These messages occur
when a patient is no longer admitted when that patient's VDL is
refreshed.
Corrective Action:
BCMA will continue, without error, when a patient is no longer admitted
while that patient's VDL is being viewed and refreshed.
5. Problem: NOIS MWV-0704-20690
The user is able to change the status of an order's patch medication
For retrieval and installation instructions, please see the Client
while that order concurrently has another 'GIVEN' and not 'REMOVED'
patch medication. After the initial status of a patch of that order has
been set to a status other than 'GIVEN', that patch can then be
administered via BCMA, without a warning to the user concerning a
concurrently 'GIVEN' patch.
Corrective Action:
BCMA will not allow multiple patches of a patch medication order to be
at the status of 'GIVEN' concurrently.
Installation Instructions section.
6. Problem: NOIS SFC-0704-60956
The user is unable to edit a 'NOT GIVEN' administration using the VISTA
"Edit Medication Log" [PSB MED LOG EDIT] option.
Corrective Action:
The user will be able to edit 'NOT GIVEN' administrations using the GUI
version of the "Edit Med Log" found under the "File" menu of the BCMA
VDL.
7. Problem: NOIS CLL-0704-40997
If an IV piggyback bag is marked as 'GIVEN', the VDL is not refreshed,
and the VDL "start/stop time" parameters are reset making that specific
administration no longer display on the VDL, then that 'GIVEN' bag can
be scanned and administered again.
Corrective Action:
BCMA will not allow an IV piggyback bag to be scanned and 'GIVEN' multiple
times.
8. Enhancement: Include Comments on the Medication History Report.
PSB*3.0*3 will provide the user the ability to include comments that
were documented during an administration to appear on the Medication
History Report. This new functionality is accessible via the BCMA GUI
and CPRS GUI.
9. Enhancement: Report Medication History in reverse chronological order.
PSB*3.0*3 will display the Medication History Report in reverse
This patch addresses 4 issues:
1. The PRN EFFECTIVENESS field (#.22) does not show up on the "Medication
Admin History" report but does on the "Medication Log" report.
2. MANUAL MEDICATION ENTRY [PSB MED LOG NEW ENTRY] Issue/Unknown Status
Report.
3. "Missed Medications" report in BCMA did not display a missed
medication.
4. Problems with "Missed Medication" report.
This Patch Addresses 4 issues:
4. Patients are Duplicating on Reports for wards with similar names.
1. An invalid MUMPS date (a date prior to 12/31/1840) entered for the
BCMA Administration Times report creates an infinite loop which sends
out BCMA Order Problem emails.
2. An undefined error occurs at PTLKUP+16^PSBMLLKU when a Nursing Ward
contains lowercase letters.
3. Orders with a Status of On Call do not print on the BCMA Missed Meds
Report or the BCMA Administration Times Report
This patch addresses Patient Safety issue PSPO #1401 and three
running the MANUAL MEDICATION ENTRY [PSB MED LOG NEW ENTRY] option.
3. Receiving error "<SUBSCRIPT>EN+12^PSBOMH1" when running the Medication
Administration History (MAH) report when the nurse has given a medication
and does not have his/her initials in the NEW PERSON file (#200).
4. The Medication Therapy report does not contain PRN Effectiveness
information.
additional issues in Bar Code Medication Administration (BCMA):
1. PSPO #1401 - When a pain score is entered through BCMA and then marked
"entered in error" in Vitals, the errant pain score still shows on the
BCMA Coversheet and other reports.
2. Receiving an error "Error - <UNDEFINED>SCANFAIL+9^PSBMLEN1" when
ATTENTION: This patch includes a new Graphical User Interface (GUI)
This enhancement will also bring the BCMA application compliant to
Section 508 of the Rehabilitation Act of 1973 and Rehabilitation Act
Amendments of 1998, which mandates that all software developed by federal
agencies allow access to and use of information and data by individuals
with disabilities.
Please see the Release Notes for more details on the following
enhancements.
executable file. Installation of this GUI is required immediately after
1. Enhancement: This will enable a single version of BCMA to be
maintained by VHA and yet be installed and operate in a "plug and play"
fashion in an IHS or Tribal facility running Resource and Patient
Management System (RPMS).
2. Enhancement: The BCMA Graphical User Interface (GUI) will display
vital measurements from the Veterans Administration (VA)
VITALS/MEASUREMENTS package for VHA sites or optionally use the
IHS PCC SUITE (APC) package which supports the V MEASURMENT file, if
operating at an IHS facility and that facility is configured to use the
the KIDS install for the Patch to function.
V MEASUREMENT file.
3. Enhancement: Section 508 Compliance including Edit Med Log
Administration Selection form and a list of forms which have labels
which will be converted to VA508StaticText.
This Patch also Addresses 7 reported issues:
1. PSI-07-223 (PSPO-823) - If an IV order is already infusing when it is
placed on provider hold, the IV can be stopped and then infused again
while still on provider hold.
2. PSPO-1678 - The MULTIPLE DOSE pop up form blocks the dosage on the
Virtual Due List (VDL).
3. All BCMA reports have a default date based on the Laptop Time instead
of the Server Time.
4. The MedLog form in BCMA will accept a space for the required comment.
5. 3 Missing Dose request reasons are missing from the Reason drop down
box on the BCMA Missing Dose form.
6. Remove the obsolete Scratch HFS Directory from the BCMA Parameters GUI.
7. The units ordered do not display on the BCMA Medication Log report
when a missing dose is requested and the order is held and then given.
This enhancement is intended to enable the BCMA application to recognize
whether it is operating in the Indian Health Service (IHS) or Veterans
Health Administration (VHA) environment, and respond by recognizing and
displaying the patient identifier appropriate to the environment.
This Patch Addresses 3 issues:
Scheduled administration time of tomorrow, the BCMA MAH shows
a medication as scheduled to be given today.
1. PSPO #1648 - The BCMA Medication Administration History Report
(MAH) does not line up the action taken on a medication with the
scheduled time of that administration.
2. The BCMA MAH displays active medications on hold when an order is
placed on Provider Hold, an additional action is taken in Inpatient Meds,
and then the order taken off provider hold.
3. When an order is created with a start date of today and a first
This Patch Addresses 2 issues:
2. A schedule with a frequency of greater than 1440 minutes
(24 hours) and a start date after today does not display as a Future
Order on the BCMA Due List Report.
1. When a user logs into BCMA and their device time is exactly
midnight, VistA will add the value of $H to the current time to
get the BCMA server time. This server time will be greater than
the highest allowable Fileman date, which is October 15, 2114.
If the BCMA Due List Report is run with the invalid default server
time, an infinite loop will be creating, eventually causing a "Disk Full"
error.
This Patch Addresses 3 issues:
time.
1. The error "<SUBSCRIPT>ADM+3^PSBCSUTX" occurs
when selecting the BCMA Coversheet tab if the patient
only has an IV Order and no Unit Dose Orders.
2. The BCMA Medication Variance Report does not paginate
correctly.
3. The BCMA Medication Variance Report displays a variance
when a patch is removed, even if the patch was given on
This Patch Addresses 3 issues:
indicate what is causing the error.
1. An error occurs when running the BCMA Unable to Scan Detailed
report, causing BCMA to shut down.
2. The Missed Medications Report is displaying invalid Start and
Stop Date and Date/Times for One Time orders.
3. The Missed Medications Report is displaying an invalid comment and
status for a given medication.
4. The BCMA "Filing Transaction MEDPASS" error message does not
ATTENTION: This patch includes a new Graphical User Interface (GUI)
Request Analysis (IMR SFG IRA) Phase III/Phase IV, as well as
modifications requested by the BCMA and Inpatient Medications
workgroups. The Inpatient Pharmacy patch PSJ*5*153 is also being
released as part of these enhancements.
1. In order to allow facilities to select a timeframe that better matches
their site policies, the site parameter that sets the amount of time
that nurses have to document the PRN Effectiveness assessment is being
expanded from 240 to 960 minutes.
executable file. Installation of this GUI is required immediately after
2. A new site parameter was added to the PARAMETERS file (#8989.5) &
PARAMETERS DEFINTION file (#8989.51) to allow sites to prohibit
administration of non-nurse verified medication orders, or to display a
warning before administering non-nurse verified medication orders.
Facilities will be able to set this option by division.
3. The Missed Medications report will now include a "Verified" column that
will contain the initials of the nurse who verified the order, or three
asterisks, indicating that the order was not nurse verified.
the KIDS install for the Patch to function.
4. A visual indicator will be displayed on the BCMA Virtual Due List (VDL)
which will reflect whether an order has provider override reasons
associated with the order.
5. If the override information exists for an order, it will also be
displayed on the order detail report.
For retrieval and installation instructions, please see the Client
Installation Instructions section.
The Allergy and Alerts Project addresses enhancements identified during
Inpatient Medications Requirementxs for Special Focus Group Initial
This Patch Addresses 4 issues:
the BCMA Medication Log forms omit the leading zero if the Units
Given field value is a decimal less than one.
4. PSPO #2015 - BCMA is accepting "Spacebar" as a valid
input for scanning a Drug IEN and returning the last
medication the BCMA User Scanned.
1. The PSB BAG DETAIL RPC is returning duplicate entries for
a single action, causing the action to be displayed twice in
the Details section of the BCMA IV Tab.
2. The message "Error @ -100" is seen in Details section
on the BCMA IV Tab if a site has the optional AU05 cross
reference turned on.
3. The Units Given fields on the PRN Effectiveness Log and
1. Enhancement: Read Only Bar Code Medication Administration (BCMA).
This patch deploys the BCMA-HSC project "Read Only BCMA"
functionality. After the installation of this build (PSB*3.0*4)
and installation of the released Read Only BCMA GUI executable
file, users allocated the "PSB READ ONLY" security key will be
granted documented Read Only BCMA functionality. Also, as
documented, users allocated the "PSB STUDENT" security key using
BCMA while no BCMA instructor is using BCMA, will be granted Read
Only BCMA functionality until a BCMA Instructor has accessed BCMA.
*** ATTENTION: This patch includes a new Graphical User Interface (GUI)
2. Enhancement: Patient Record Flag Reporting.
This patch provides "Patient Record Flag" reporting functionality.
During patient selection, information about any active Patient
Record Flag(s) associated with the selected patient will be
presented to the user. This patch also give the user the ability
to display and print details of all active Patient Record Flags.
This patch will also display a "FLAG" button via the patient's GUI
Virtual Due List. This "FLAG" button gives the user access to a
report of the all the active Patient Record Flags associated with
executable file. Installation of this GUI is required immediately
the patient.
after the KIDS install for the Patch to function. ***
For retrieval and installation instructions, please see the Client
Installation Instructions section.
This patch addresses the following issues:
displayed on the BCBU MAR report. PSPO# 1613
3. A prompt and help message in VistA under the BCMA Backup System
[PSB BCBU WRKSTN MAIN] option is currently not displaying properly
or consistently among the following three BCBU MAR print options
Print MAR for All Wards, Print MAR for Selected Patient, and Print MAR
for Selected Ward.
4. While using Room/Bed sort in the BCMA Backup System (Wrkstn) option
Print MAR for Selected Ward, the system produces an error if a patient
1. Future medication orders display on the Bar Code Medication
has no Room or Bed assigned.
Administration Backup System (BCBU) Medication Administration Record
(MAR) as current. An asterisk should be displaying in the
administration time fields until the actual start dates have
been reached.
2. Held medications are currently being displayed on the BCBU MAR option
Print MAR for a Selected Patient. Held medications should not be
This Patch Addresses 3 issues:
3. The BCMA MAH displays all meds as not due until the day after
the start date.
1. PSPO 2134 - A Given dose does not display on the BCMA
Medication Administration History (MAH) report when another dose is
given for the same Administration time on the wrong day.
2. A given dose of an IVPB will not display on the BCMA MAH report
if the time given is edited to a time prior to the original given time
of the medication.
This Patch Addresses 2 issues:
1. The BCMA Missed Medications Report may be inconsistent
when run for a whole day versus incremental times if
the order's Administration Times are edited.
2. The Initials of the Nurse who marked an IV Bag infusing
do not display in the Legend of the BCMA IV Overview
Coversheet report when a different Nurse marks the bag
Stopped or Completed.
*************************************************************************
ATTENTION: This patch includes a new Graphical User Interface (GUI)
executable file. Installation of this GUI is required immediately after
the KIDS install for the Patch to function.
This version of BCMA was successfully tested in the field against Wireless
Medication Administration version 4.8 at Pittsburgh and Loma Linda.
For retrieval and installation instructions, please see the Client
Installation Instructions section.
IMPORTANT: PATCH PSJ*5*267 MUST BE INSTALLED BEFORE THE INSTALLATION
The Special Instructions and Other Print Info Project addresses
enhancements identified during Inpatient Medications Requirements for
Special Focus Group Initial Request Analysis (IMR SFG IRA) Phase
III/Phase IV, as well as modifications requested by the Bar Code
Medication Administration (BCMA) and Inpatient Medications workgroups.
The Inpatient Pharmacy patch PSJ*5*267 is also being released as part of
these enhancements. The projects purpose is to Standardize the character
length between CPRS Provider's Comment, Inpatient Medications Special
Instructions, and the IV Pharmacy Other Print Information fields.
OF THIS PATCH.
The Inpatient Pharmacy patch PSJ*5*267 will add new fields to Inpatient
Medication to support an unlimited amount of text for Special
Instructions and Other Print Info (SI/OPI).
1. BCMA Remote Procedure Calls (RPC) will be modified to send over the new
Inpatient Medications SI/OPI fields in an unlimited format to the BCMA
GUI client.
2. For backwards compatibility, of existing Active orders on file that
were using the old fixed length SI/OPI fields, then this information
will be included in the new unlimited format also.
3. Modify the following reports to print the unlimited SI/OPI information:
a. Medication Administration History (MAH) Report
b. Display Order detail Report
c. Due List Report
d. IV Bag Status Report
e. Cover Sheet Report - Medication Overview Report
f. Cover Sheet Report - PRN Overview Report
BCMA patch PSB*3*68 contains changes that will not function until patch
g. Cover Sheet Report - IV Overview Report
h. Cover Sheet Report - Expired/DC'd/Expiring Report
i. BCMA Backup System (BCBU) Print MAR for All Wards
j. BCMA Backup System (BCBU) Print MAR for Selected Patient
k. BCMA Backup System (BCBU) Print MAR for Selected Ward
4. Add new check box field to allow if the unlimited text will be printed
on the following reports:
a. Due List Report
b. IV Bag Status Report
PSJ*5*267 is installed. Both patches, PSJ*5*267 and PSB*3*68 need to be
c. Cover Sheet Report - Medication Overview Report
d. Cover Sheet Report - PRN Overview Report
e. Cover Sheet Report - IV Overview Report
f. Cover Sheet Report - Expired/DC'd/Expiring Report
5. BCMA Client:
a. Added window to display unlimited Special Instructions / Other
Print Info via menu, right-click, and function key (F6). This
window is also used to display Special Instructions / Other Print
Info when an order is flagged in Inpatient Medications and is given
installed for Inpatient Medications and BCMA to function correctly.
in BCMA.
b. Fields which displayed Special Instructions / Other Print Info in
forms were widened to 80 characters and have vertical scroll.
c. Added Last Injections Site column to the Unit Dose VDL to show the
what the last site was per Orderable item.
d. Enhanced the Injection Site dialog window to show two
history tables.
1) To show the last 4 sites per the medication being given.
2) To show last 10 sites per the patient for any medication.
The tables above will use a new Division parameter, "Injection Site
*************************************************************************
History Max Hours", added with this patch that controls how many
hours to look back when compiling these history tables. The default
will be initialized to 72 hours, with this patch.
This Patch also Addresses 3 reported Remedy ticket issues:
1. After scanning a medication that requires multiple doses
or dosage strengths, the multiple dose dialog box's
invalid medication pop-up functionality appears to be broken.
2. Unable to view all allergies/ADRs on BCMA GUI for patient with
numerous allergies/ADRs.
3. The Patient Record Flag changes from Red to Black if you lock
your computer.
Please refer to the release notes for a full detailed list and examples
of items included in this patch.
***********************************************************************
The Special Instructions and Other Print Info Project addresses
enhancements identified during Inpatient Medications Requirements for
Special Focus Group Initial Request Analysis (IMR SFG IRA) Phase
III/Phase IV, as well as modifications requested by the Bar Code
Medication Administration (BCMA) and Inpatient Medications workgroups.
The Inpatient Pharmacy patch PSJ*5*267 is also being released as part of
these enhancements. The projects purpose is to Standardize the character
length between CPRS Provider's Comment, Inpatient Medications Special
Instructions, and the IV Pharmacy Other Print Information fields.
IMPORTANT: PATCH PSJ*5*267 MUST BE INSTALLED IMMEDIATELY BEFORE
The Inpatient Pharmacy patch PSJ*5*267 will add new fields to Inpatient
Medication to support an unlimited amount of text for Special
Instructions and Other Print Info (SI/OPI).
The enhacnement in this patch will support the new unlimited lines of
text that will now be sent by Inpatient Medications to the BCMA
Contingency software workstations, in the HL7 NTE|21 segement.
Please refer to the release notes for a full detailed list and examples
INSTALLATION OF THIS PATCH.
of items included in this patch.
If the site is running the BCMA Contingency software then this patch
must also be installed on the workstations. Once installed it is
suggested that the sites review the Contingency system MAR reports.
***********************************************************************
This Patch Addresses 2 issues:
1. PSPO 2012 - IV Bag Parameters are not defined for an Institution
which contains active wards.
2. After Multiple edits of solutions, invalid IV bags in BCMA may be
administered.
This Patch Addresses 3 issues:
day of the week schedule.
1. An order with an Unknown Action status is unavailable
when using the Edit Med Log option if another user runs
the BCMA Medication Administration History (MAH) report.
2. A fatal error occurs when using the Unable to Scan function
in BCMA and then scanning another medication.
3. A fatal error occurs when clicking on the BCMA Coversheet if
a patient's only current order is an IV Piggyback which has a
This Patch Addresses 3 issues:
1. A broker error occurs when attempting to open BCMA (Bar Code
Medication Administration) for a patient who has and Intravenous
Piggyback (IVPB) medication with an unknown Action Status.
2. The header on several reports do not delineate a patient's room
number with a colon.
3. The BCMA Missed Medications Report does not contain meds that
are held or refused when run in VistA.
This Patch Addresses 2 issues:
the BCMA UNABLE TO SCAN LOG (#53.77) file is greater than 40
characters.
1. An Undefined error occurs at LINE+13^PSBOML when the
BCMA Med Log report is run and finds a BCMA MED LOG
(#53.79) entry without a corresponding PHARMACY PATIENT (#55)
entry.
2. When giving an IV via the Unable to Scan feature, the user will
receive a "Incomplete Data Returned from Vista" pop up box if the
data attempting to be stored in the ORDERABLE ITEM (#15) field of
appropriate.
2. Problem: NOIS MIW-0504-40557
Scheduled administration times are reported and totaled on the
Ward Administration Times Report per each clock hour. If an
order s stop time is between clock hours, that order s final
scheduled administration is neither reported nor added to the
report totals.
1. Problem: NOIS CTX-0804-70321
Corrective Action:
The BCMA Ward Administration Times Report will report and
total all appropriate scheduled administration times.
3. Problem: NOIS LIT-0704-71393
The initial administration of an order which displays on the BCMA
Graphical User Interface (GUI) Intravenous/Piggyback (IVPB) Tab
may result with an administration status of "GIVEN", "HELD", or
"REFUSED". When this same order is administered via the VISTA
Large volume IV orders do not show on the Due List Report. The
Manual Medication Entry [PSB MED LOG NEW ENTRY] option, the
initial administration status can only be "GIVEN".
Corrective Action:
The Manual Medication Entry [PSB MED LOG NEW ENTRY] option will
allow the initial administration of an IVPB order to result in
an administration status of "GIVEN", "HELD", or "REFUSED".
4. Problem: NOIS UNY-0304-10606
Bar Code Medication Administration (BCMA) Due List Report does
When the user prints a Medication Administration History (MAH)
report with a date range exceeding seven (7) days, Pro Re Nata
(PRN) order activity, which occurred that last day of the
report s date range, does not display.
Corrective Action:
PRN activity occurring within the selected MAH report date range
will display on that MAH report.
not display information for large volume IV orders that have
5. Problem:
When creating a MAH report, the administration times of orders
that have start time between the report's date range do not
display properly.
Corrective Action:
The MAH report will display order administration times properly.
6. Problem: NOIS ISB-0105-30190
been created on the date selected for reporting.
When using the GUI Edit Med Log to add a comment for an
administration having units given less than 1.0, the message - "When
changing the admin status to Given, at least one dispensed drug must
have a units given ..." - is displayed and the comment is not filed.
This error is due to the value in the Units Given field of the GUI
Edit Med Log being presented without the "leading zero" when the
value is less than 1.0.
Corrective Action:
When the Units Given value of an administration is less than zero,
it will be presented via the GUI Edit Med Log with the leading zero.
7. Problem: NOIS ISB-1104-31950
The Medication History Report does not display a leading zero in
its "Units GIVEN" data field when display a numerical fraction.
Corrective Action:
A leading zero will display in the Medication History Report,
"Units GIVEN" data field when appropriate.
Corrective Action:
8. Problem: NOIS BUT-1204-21117
There are instances when the "Units Of Administration" data field
of the Medication History Report does not "break" and remain legible.
Corrective Action:
The "Units Of Administration" data field of the Medication History
Report will "break" and maintain whole words and legibility.
The BCMA Due List Report will display large volume IV data when
9. Problem: NOIS UNY-0105-11034
The heading for the Due List Report, "Future Orders" section is
displayed and is not followed by "Future Order" data when at least
one future active order exists, and no future order has a scheduled
administration within the selected report time parameters.
Corrective Action:
The heading for the Due List Report, "Future Orders" section will not
display, unless "Future Order" data is to be displayed.
This Patch Addresses 2 issues.
in the PHARMACY PATIENT IV subfile (#55.01) cannot be marked
as given using the Manual Medication Entry [PSB MED LOG NEW ENTRY]
option.
1. When the INFUSION RATE field (#.08) in the PHARMACY PATIENT IV subfile
(#55.01) is greater than 27 characters (30 character max) for an
Intravenous Piggyback (IVPB) order, the text added by the software
will cause the infusion rate to exceed the 47 character maximum
in BCMA.
2. An IVPB order with a SCHEDULE (#.09) and a STATUS (#100) of "On Call"
This Patch Addresses 2 issues:
printed by ward.
1. An order will not display on the Bar Code Medication
Administration (BCMA) Virtual Due List (VDL) properly
if the order has its first administration time not on the
hour and the start date and time are not exactly on the hour.
2. The BCMA PRN Effectiveness Report and Medication
Variance Report do not display the ward name when
This Patch Addresses 6 issues:
History (MAH) report.
4. The undefined error <UNDEFINED>FILEIT+10^PSBML *PSBHDR occurs
when logging into BCMA.
5. Immunizations given as Clinic orders in BCMA are not recorded in the
V IMMUNIZATIONS (#9000010.11) file.
6. BCMA accepts a partial scan of a patient's SSN when scanning a
patient's wristband.
1. The Bar Code Medication Administration (BCMA) Missed Medications
report does not include orders with a status of "Renewed"
2. BCMA incorrectly rounds a patient's height down on the BCMA Virtual
Due List (VDL) and on report headers, and incorrectly calculates a
patient's weight on report headers.
3. Orders with a start time exactly the same as the last administration
time will display as not due in the BCMA Medication Administration
This Patch Addresses 5 issues:
of Last 4 digits of a patient's Social Security Number (SSN) as the
patient identifier.
4. A dangling "AADT" index causes an undefined error to occur when
a site runs the BCMA Extract (ECXBCM) option.
5. The Meds on Patient section of the BCMA Virtual Due List (VDL)
displays an Intravenous (IV) bag as infusing after it has been marked
completed if the Action Date/Time was edited using the Edit Med Log
option.
1. The Bar Code Medication Administration (BCMA) Medication History
report displays data prior to the report start date when run in the
Computerized Records System (CPRS) application.
2. BCMA Labels for Unit dose drugs are missing the Indian Health
Services (HIS) Health Record Number (HRN) in place of Last 4 digits of a
patient's Social Security Number (SSN) as the patient Identifier.
3. The BCMA Unknown Actions Report does not display IHS HRN in place
This Patch Addresses 7 issues:
3. The BCMA Medication Log and Medication Variance report headers
do not display the time frame of the report.
4. The BCMA AUDIT LOG (#53.799) sub-file does not include an entry
for Pro Re Nada (PRN) Effectiveness when a PRN is "Un-Given"
5. The Legend of the Medication Therapy report does not include users
who entered comments for an order.
6. The 2nd line of routine PSBOPE has an invalid format.
7. Update the unsupported $$UCASE^XUSG Application Programming
Interface (API) to the supported API $$UP^XLFSTR in routine PSBMLLKU.
1. The Medication History report in Bar Code Medication
Administration (BCMA) displays amounts in the Units Given
field for an order that has not been given.
2. When a user makes a change to an order using the Edit Med Log
option which does not change the action status, several reports
display the initials of the person who edited the order instead of
who created the action on the order.
This Patch Addresses 6 issues:
a different division.
4. The BCMA Administration Times report does not display historical
data when run by ward.
5. The BCMA Clinical Reminders tab does not display that a PRN
Effectiveness is needed when the PRN is given on the same day as the
patient is admitted.
6. The Unable to Scan detailed report does not display the full Health
Record Number (HRN) for Indian Health Services (IHS) sites.
1. The Bar Code Medication Administration (BCMA) MEDICATION
VARIANCE LOG (#53.78) file does not save data in DRUG SCANNED
(#.07) field.
2. BCMA stores the initials of the user who viewed the patient's record
instead of the initials of the user who marked a Vital Entered in Error.
3. The BCMA Unable to Scan Detailed report does not display any data
when run for a Nursing Ward if the user running the report is logged into
This Patch Addresses 7 issues:
Record System (CPRS) application when converting weight from pounds
to kilograms.
4. BCMA report headers display the diagnosis for a patient's last
admission after the patient has been discharged.
5. The BCMA Coversheet is loading slowly for long term care patients.
6. The Unit Dose tab of the BCMA VDL loads slowly for long term care
patients.
7. The BCMA Medication Variance report displays the medication name twice
under the medication field of the report
1. An Undefined error occurs at SCANPT+49^PSBRPC if an accent (`) mark is
passed in when manually keying in a patient's wristband.
2. Bar Code Medication Administration (BCMA) report headers display the
last ward and room/bed the patient was admitted to after they are
discharged.
3. BCMA report headers and the BCMA Virtual Due List (VDL) round a
patient's weight to less significant digits than the Computerized
******************************* ATTENTION ********************************
3. PSB*3*83
12. BCMA Due List report now includes Remove Times on the report below
the admin times that are due per Medication.
13. BCMA Coversheet Medication Overview report and the Coversheet
Expired/DC'd/Expiring Orders report will now include Missed-Removals
and Removals on the reports.
14. BCMA Medication Log report changed the heading from "Inj Site" to
"Body Site". The Medication detail body text will display the proper
4. OR*3*417
label of "Inj Site:" or "Derm Site:" just prior to the name of the
Body site for that medication.
15. BCMA Medication History Heading line changed from "Injection Site" to
"Body Site".
16. A body site diagram will be added to the BCMA Parameter GUI client
application for the purpose of showing a dot on the body diagram that
is associated with the Text representation of that site location on
the body.
5. PSB*3*87
17. The BCMA Parameter GUI client application has access to a new kernel
parameter titled in GUI application as "Dermal Site History Max
Days:". This allows the BCMA coordinator the ability to control how
many days of prior dermal body site location history will appear, when
a clinician is giving a new dermal medication that is prompting for a
body site location.
18. The Orders for MRRs With Removal Properties [PSS MRR ORDERS DIAGNOSTIC
RPT] option found on the Pharmacy Data Management [PSS MGR] menu,
will also be placed on the Bar Code Medication Administration Manager
[PSB MGR] menu.
*NOTE* Non-standard schedules such as DAY@HHMM, HHMM, or other Odd
schedules, are not capable of calculating removal times due to a
lack of a Frequency. Regardless of the Prompt for Removal in BCMA
code value they will not prompt for removal in BCMA and should be
avoided.
ATTENTION: This enhancement also includes a new Graphical User Interface
(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is
required immediately after the KIDS install for the Patch to function.
For retrieval and installation instructions, please see the Client
Installation Instructions section.
**************************************************************************
The Clinical Ancillary Services Development-Delivery of Pharmacy
Enhancements (CAS DDPE) project addresses several NSR's, which center
around providing a means for properly handling Transdermal Medications
Requiring Removal (MRR) beyond the current medications of dosage form
Patch. These enhancements interface with Inpatient Pharmacy package,
which will be storing Scheduled Removal Times, for inpatient orders that
are designated as MRR type medications. See associated patches PSS*1*191
and PSJ*5*315, for details on how MRR medications are designated.
Clinical Ancillary Services (CAS) Development-Delivery of Pharmacy
This BCMA enhancement also includes a new Graphical User Interface (GUI)
executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is required
immediately after the KIDS install for the Patch to function.
Features of the BCMA GUI provided by this project are listed below.
1. Change the current GUI Unit Dose tab column labeled "Admin Time" to
"Next Dose Action".
Enhancements (DDPE) VA Inpatient Medication Administration - Transdermal
2. The "Next Dose Action" column will now contain both the next admin
times for scheduled administrations as well as the next Removal time
for MRR type medications. The initial login to BCMA, will sort the
Unit Dose tab in ascending order by this column, so older actions for
medications will be at the top of the VDL display.
a. The Next Action of an administration will contain the word "DUE"
followed by the scheduled admin time in the standard date@admin
time format currently in use.
b. The Next Action of a removal will contain the word "REMOVE"
enhancement includes 5 patches which must be installed in the following
followed by the scheduled removal time in the standard
date@time format.
c. The Next Action of an administration that is past due to be
given will contain the word "LATE" followed by the scheduled
admin time in the standard date@admin time format currently in
use.
d. The Next Action of a removal that is past due to be removed will
contain the word "LATE-RM" followed by the scheduled removal time
in the standard date@time format.
order:
3. Change the current GUI column labeled "Wit" to "Alert".
4. The Alert column will still have the ability to display the Witness
required icon and will also be able to display a new Remove icon.
a. The icon is displayed only for MRR type meds that were Given and
their next Action is for Removal.
5. Early/Late warnings will also be associated with medications being
removed early or late using the same early late time range that is
used for early or late medication admins.
a. User comments are prompted for and stored upon continuing with
the Early/Late removal action.
6. Variances will also be tracked for Early/Late Removals in the same
manner as they are currently for Early/Late medication
administrations and will appear on the Medication Variance Log report.
7. BCMA Medication Administration History (MAH) report will now print
the associated Give, which was previously overwritten by the Remove
action, chronologically after the Remove for the Print by Patient
1. PSS*1*191
report. The print by Ward report will now include the count of
Removals scheduled for the report time period.
8. BMCA Medication Log will now show the historical Give date/time below
the current status of the medication, which shows the Remove
date/time.
9. BCMA Missed Medications report will also show Removals that were
missed or up and coming, similar to how missed Gives are currently
notated. The column Heading has been changed from "Admin Date/Time"
2. PSJ*5*315
to "Missed Date/Time".
10. BCMA Display Order report now includes the Removal Times for this
order directly below the current Admin Times.
11. BCMA Medication History report now includes a prior Give line item
directly below the current status line item of Remove (RM). The Remove
last action on this administration overwrites the Give information and
was no longer printing on this report. This information is now being
retrieved from the Audit log and printed on this report.
******************************* ATTENTION ********************************
5. PSB*3*87
ATTENTION: This enhancement also includes a new Graphical User Interface
(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is
required immediately after the KIDS install for the Patch to function.
For retrieval and installation instructions, please see the Client
Installation Instructions section.
**************************************************************************
PSB*3*87 will enhance the BAR CODE MEDICATION ADMINISTRATION (BCMA) Backup
System (BCBU) to support Medications Requiring Removal (MRR). The Backup
System will be able to store the Removal times and duration of
administration associated with each medication order.
This patch will add two new fields to the ORDER NUMBER (#53.702)
sub-file under the BCMA BACKUP DATA (#53.7) file. The two new fields
are the REMOVE TIMING (#7.4) field and DURATION OF ADMINISTRATION (#7.5)
field. These fields implement changes that will support enhancements to
Medical Administration Record(s) MAR reports in the BCBU application.
CASDDPE VA Inpatient Medication Administration - Transdermal enhancement
The MAR reports will print each Scheduled Removal times for MRR
medications in the Grid in the same manner as Admin times. The Remove
times will appear below the current scheduled Administration time in the
Grid and will be separated by the Label "Remove" in the times column.
Asterisks will print in the body of the Grid in each Removal action box
for removal times that are not valid per the Date in that column heading.
The MAR reports will also no longer display the Order number of the
medications being administered.
includes 5 patches which must be installed in the following order:
Please refer to the BCMA Backup System (BCBU) Installation Guide for
PSB*3*87 for installation details.
1. PSS*1*191
2. PSJ*5*315
3. PSB*3*83
4. OR*3*417
This patch will resolve the following issues:
3. The BCMA Drug IEN Synonym Check [PSB DRUG IEN CHECK] option needs to
be added to the Medication Administration Menu Pharmacy [PSB PHARMACY]
menu.
4. The IV Bag Detail on the IV tab does not display for a patient when
opening the patient's Virtual Due List (VDL) after having another
patient's VDL open.
1. The Bar code Medication Administration (BCMA) Due List Report does not
display Intravenous Piggy Back (IVPB) orders with an Inpatient
Pharmacy Status of "On Call".
2. The Missed Medication Report shows missed administrations prior to an
edit when an order's Administration time are edited.
Patch PSB*3*97 will change the version number of the Bar Code
Some reports that print Legends had some issues where the user name and
initials were inaccurate for transdermal type medications.
Medication Administration (BCMA) client application to version 97
from version 83 to correct an issue discovered immediately after release
of version 83.
A hard error can occur in the BCMA client application with a new button
provided that displays a Body Site Image for selecting body location of
transdermal type medications.
This patch will resolve the following issues:
3. Medications cannot be administered in BCMA after Nurse's initials
deleted.
4. Medications Orders requiring removal with a schedule type of "One-Time"
and Frequency greater than zero do not display the correct removal
time in the "Next Dose Action" field on the BCMA VDL.
1. The Bar Code Medication Administration (BCMA) Order Mode indicator
light is not displaying when the only active orders have a pharmacy
status of renewed, on call, or provider hold.
2. The BCMA Active Order Indicator light is not displaying for the Unit
Dose tab when the only active orders have a Pharmacy Status of Renewed
or Provider Hold.
This patch will resolve the following issues:
3. The BCMA Display Order report displays dates in the data field in
internal Fileman format.
4. An Undefined error occurs when the Medication Therapy report is run
with no schedule types selected.
1. The Bar Code Medication Administration (BCMA) IVP/IVPB tab continues
to display orders with a Schedule Type of On Call after the order is
administered.
2. The BCMA Display Order report displays both BCMA EXPIRED and BCMA
EXPIRE DENIED in the data field of the Pharmacy Activity section when a
one time dose medication is administered.
This patch will resolve the following issues:
then
Resolution:
-----------
Routine PSBML2 was modified to store the correct medication dosages
in the DISPENSE DRUG (#53.795) sub-file when the edited order is
administered.
4. R12817870FY17 - PRN requiring effective is not showing on BCMA Clinical
Reminders
infusing, the medication log shows each ingredient of the infusing IV
Problem:
--------
A PRN medication requiring a PRN Effectiveness does not display on the
BCMA Clinical Reminders if the patient is discharged and re-admitted.
Resolution:
-----------
Routine PSBPRN was modified to display the order under the BCMA
Clinical
Reminders when the patient is discharged and re-admitted, as long as
Order
the
order falls within the PRN Documentation parameter.
5. I10114492FY16 - Mark Documenting Backlog PRNs option OOO
Problem:
--------
The unsupported Documenting Backlog PRNs [PSB PRN DOCUMENTING] option
needs to be marked out of order and removed from the Bar Code
Medication
to have units of zero.
Administration Manager [PSB MGR] menu option. This option runs a
version
2 routine in BCMA (currently on version 3), and should not be active
on a nationally released menu option.
Resolution:
-----------
Post Install routine PSB399P will mark the Documenting Backlog PRNs
option [PSB PRN DOCUMENTING] "out of order" and remove the option
from the Bar Code Medication Administration Manager [PSB MGR] menu.
6. I6216135FY16 - <UNDEFINED>RESETADM+7^PSBUTL error in BCMA
Problem:
--------
An error occurs the first time an order is administered in BCMA.
Resolution:
-----------
3. When a multiple dose medication has been edited prior to
Routine PSBUTL was modified to properly record the first BCMA
medication administration.
7. I10181534FY16 - Extra Data populated when pulling by Ward
Problem:
--------
A BCMA user was attempting to pull data by ward. When data populated
it listed patients that are not associated with the ward selected.
administration,
The problem happened because the ward searched had a name that the
first
characters were similar to a date (e.g., 8-8, 10-11, etc.). The
routine
PSBMLLKU (line tag PTLKUP) used to perform a Fileman lookup using all
cross-references in the PATIENT file (#2). This lookup approach
sometimes produced wrong entries because it would match with a date
from
the "E" x-ref (CV DATED EDITED) because for example "8-8" would trigger
it will display on the Missed Meds report after administration.
a match a 08/08/17 (current year) causing such patients to be included
in the lookup result.
Resolution:
-----------
The code at the PTLKUP^PSBMLLKU was modified to only include the cross-
references that are relevant to the patient lookup popup window (last
name, first name, SSN, ward, room and bed).
4. A PRN medication requiring a PRN Effectiveness does not display in the
BCMA Clinical Reminders section if the patient is discharged and
re-admitted.
5. The unsupported Documenting Backlog PRNs [PSB PRN DOCUMENTING] option
needs to be marked out of order, and removed from the Bar Code
Medication
Administration Manager [PSB MGR] menu option.
6. An error occurs when a site new to BCMA attempts to create their first
order.
1. The Bar Code Medication Administration (BCMA) GUI does not store the
7. The patient lookup window sometimes lists the wrong patient when users
are doing a search by the ward name and the first part of the ward name
matches with a valid date.
ASSOCIATED NSR(S):
==================
N/A
initials of the 2nd user who witnesses a high risk/high alert
ASSOCIATED CA TICKET(S):
============================
1. I9892136FY16 - 2nd Witness Initials not stored
2. I9842129FY16 - TPN shows 0 units for each ingredient - Med Log
3. I9892810FY16 - False missed med when Inpatient Pharmacy edits
dispense drug
4. R12817870FY17 - PRN requiring effective is not showing on BCMA
Clinical Reminders
5. I10114492FY16 - Mark Documenting Backlog PRNs option OOO
6. I6216135FY16 - <UNDEFINED>RESETADM+7^PSBUTL error in BCMA
continuous
7. I10181534FY16 - Extra Data populated when pulling by Ward
PARTICIPATING TEST SITES:
=========================
TBD
CA OVERVIEW:
================
intravenous (IV) order which has been marked stopped and then marked
1. I9892136FY16 - 2nd Witness Initials not stored
Problem:
--------
The second witness' information is not stored in the ADMIN WITNESSED BY
(#.29) field of the BCMA MEDICATION LOG (#53.79) file when an IV bag
with a high risk/high alert medication is marked stopped and then
infusing again.
Resolution:
infusing again.
-----------
Routine PSBML2 was modified to remove the first witness' information
and store the second's information in the ADMIN WITNESSED BY (#.29)
field. The first user's information will be preserved in the AUDIT LOG
sub-file (#53.799).
2. I9842129FY16 - TPN shows 0 units for each ingredient - Med Log
Problem:
--------
When a missing dose is requested for an IV order, then as held or
refused,
and then infusing, the Medication History report shows each ingredient
of
the infusing IV Order to display units of zero.
Resolution:
-----------
Routine PSBML2 was modified to store the correct units for each IV bag
ingredient in the UNIT OF ADMINISTRATION (#.04) field of both the
2. If an IV order is marked as a missing dose, then as held or refused,
ADDITIVES (#53.796) and SOLUTIONS (#53.797) sub-files.
3. I9892810FY16 - False missed med when Inpatient Pharmacy edits
dispense drug
Problem:
--------
A multiple dose medication will incorrectly display on the BCMA Missed
Medications report when the dosage form of the order was edited after
a missing dose request is made on the order.
This patch will resolve the following issues.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1. I9592038FY16 - Frequently, BCMA users are not able to access the BCBU
database
Problem:
--------
Frequently, BCMA users are not able to access the BCBU database. This result
in local IT support spending time to resolve what should be a minor issue.
However, the fix is not always simple or straight forward. Typically, the
problem is that the user has had a Verify Code change since they last
accessed a contingency. Normally, doing a User Initialization does not
resolve the issue and IT support has to either replace the database or
manually give the user a new Verify code on the contingency computer.
Resolution:
-----------
Modified the routines ALPBGEN, ALPBGEN1 and ALPBGEN2 to remove some
unnecessary restrictions for sending a user update over to the BCBU
1. I9592038FY16 - Frequently, BCMA users are not able to access the BCBU
workstation. For example, if a user was terminated in the main VistA System
it would not be sent to the BCBU workstation. This caused terminated users
in the main VistA System to remain active in the BCBU workstation.
2. I8652828FY16 - Getting ALERT BCBU Contingency Error 46364090 / Missing HLL
Links Array Med-Log
Problem:
--------
database
In a multi-divisional BCBU configuration all Divisions are required to have
an HL7 Logical Link associated. When a division is missing the association an
alert is generated for every transaction that is supposed to go to the BCBU
workstation for that division. The problem is that the Alert does not identify
which division is missing the Logical Link, which makes it hard for the users
to identify the source of the problem and resolve it. Furthermore, the fact
that the Alert does not identify which patient was being processed when the
issue happened makes it hard to troubleshoot and fix the problem as well.
Resolution:
2. I8652828FY16 - Getting ALERT BCBU Contingency Error 46364090 / Missing HLL
-----------
Modified the routine ALPBCBU to include the site number and the patient DFN
number in the Alert subject. This way users will know exactly which division
and the patient that was being processed when a BCBU Alert is generated due to
an error.
Here is how the Alert text will be modified:
Before: BCBU Contingency Error
Missing HLL Links Array Med-Log
Links Array Med-Log
After: BCBU Contingency Error / Site: 442 / DFN: 1930382
Missing HLL Links Array Med-Log
3. I6161931FY16 - Received the error $ZE= <UNDEFINED>ZPD+5^IVMPREC8 *HLFS
I16851052FY18 - Undefined: GENACK+10^RGADTP *HL("MID")
Problem:
--------
3. I6161931FY16 - Received the error $ZE= <UNDEFINED>ZPD+5^IVMPREC8 *HLFS
When an HL7 message is received from an Income Verification Match (IVM) Center
containing demographics data for a patient that includes a date of death the
BCBU application is automatically invoked if such patient has active inpatient
orders. Many other subscribing applications are automatically invoked by the
same process and they all share the same local variables from the invoking
process. The routine ALPBINP was incorrectly killing HL7 local variables such
as HL, HLA, HLCS, HLCTR and HLFS, which were being used by other applications
and in these two specific incidents reported caused the Income Verification
Match (IVM) and Registration applications to error out.
I16851052FY18 - Undefined: GENACK+10^RGADTP *HL("MID")
Resolution:
-----------
Modified the routine ALPBCBU to NEW the variables HL, HLA, HLECH and HLQ and
also modified the routine ALPBINP to no longer kill the HL7 variables HLCS,
HLCTR and HLFS.
NOTE: This fix could not be tested in a development or an SQA environments
because it requires an incoming HL7 message from an external entity.
all administration and order processing has occurred and BCMA
begins to free memory per MOB activity. Because a variable
needed by BCMA MOB exit activities has been cleared, BCMA generates
the "<UNDEFINED>MOBR+25^PSBAPIPM" before processing has completed.
Corrective Action:
PSB*3*15 will allow BCMA MOB exiting processing to complete
without error.
1. Problem: HD000000088329
The Medication Order Button (MOB) within the Graphical User
Interface, Bar Code Medication Administration system (BCMA)
malfunctions after the Installation of patch PSB*3*9. When the
BCMA MOB is used to administer medications and create orders,
all data is stored and maintained properly. The malfunction
occurs when the post PSB*3*9, BCMA system frees memory after
This patch will resolve the following issue.
Problem:
--------
Milwaukee VAMC reported getting a RPC Broker Timeout error when running the
BCMA Missed Medications Report for one specific ward (9C). The reason they
were getting this error is because Ward 9C has quite a few long term care
patients and the report retrieves information for every single order with
medication that requires removal (e.g., patches) for all patients in that
ward before deciding whether the order should be in the report or not.
Resolution:
-----------
Modified the routine PBUTL at the REMOVES line tag and moved the screening
filters up before the call to D PSJ1^PSBVT. This change will have no impact
whatsoever on the output of the report and it will considerably decrease the
amount of time it takes to run it.
1. R16686630FY17 - Ward 9C keeps getting this error (Timeout) intermittently
when trying to run the Missed Medications Report
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1. R16686630FY17 - Ward 9C keeps getting this error (Timeout) intermittently
when trying to run the Missed Medications Report
This patch will resolve the following issues.
Problem:
--------
It was reported that almost all of the BCBU Contingency Error Alerts that
Divisional sites receive continually are for patients who are not admitted
or are deceased. Furthermore, testing of BCBU data for Clinic Orders reveals
that the patient records for clinics using BCMA are rarely complete causing
the menu options in BCBU to be placed OUT of ORDER to prevent medication
errors during contingency operations.
Resolution:
-----------
It was identified that updates for BCMA Medication Logs for patients that are
no longer inpatient fail to identify the correct division for which the HL7
message should be sent to. A fix was made to retrieve the correct Division
using the Institution in the Medication Log if the patient is no longer
inpatient. In addition, the BCBU Contingeny Error Alerts will no longer be
generated for patients that are deceased.
1. R18279880FY18 - BCBU not consistently updating Clinic Orders
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1. R18279880FY18 - Frequently, BCMA users are not able to access the BCBU
database
This patch will resolve the following issue.
Problem:
--------
An issue was discovered when loading the BCMA coversheet and the patient
has an order with an administration schedule that does not have a whole
number of hour(s) frequency between administrations (e.g., 7 TIMEs A DAY,
ONCE EVERY 3.5 HOURS, etc.). The reason is because the program that
calculates the next dose's administration date/time assumed the frequency to
be a whole number of hours like 4 or 6 and not 3.1466 or 3.5. Since the
program could not come up with a valid date/time it went into an infinite
loop which would freeze the BCMA application when the users tried to view the
patient's coversheet.
Resolution:
-----------
The routine PSBCSUTX was modified at line tag NEXTADM+24 to take into account
that the frequency of a schedule does not necessarily produces a whole number
of hours and it will calculate the next administration date/time for such
frequencies.
R19023599FY18 - PSB GUI Context consuming a lot of CPU on Bay Pines VistA
Front ends
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
R19023599FY18 - PSB GUI Context consuming a lot of CPU on Bay Pines VistA
Front ends
This patch provides multi-division sites the ability to run the report
'Missing Dose Followup' by division. Single division sites are not
affected by the changes in this patch.
This patch will resolve the following issue.
--------
An issue was discovered with the Barcode Medication Administration (BCMA)
Missed Medications Report for 'odd' (non-standard) schedule orders, e.g.
Q18H - ONCE EVERY 18 HOURS. When the report is run for a date range that
starts prior to the start date/time of such orders in some cases it will
mistakenly include these orders in the report even if the order does not
have any missing dose for the date range selected for the report.
Resolution:
-----------
The routine PSBOMM was modified at line tag EN1+49 to prevent it from
calculating a dose date/time that is prior to the order start date/time.
INC0328665 - Issue with BCMA Missed Medications Report
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
INC0328665 - Issue with BCMA Missed Medications Report
Problem:
This patch will resolve the following issue.
INC0962039 - WNY - Vista Not Updating BCBU orders when patients are
discharged/deceased
INC1002829 - BCBU patient census not updating
(Duplicate)
Problem:
--------
An issue was discovered with the Barcode Medication Administration (BCMA)
Backup System (BCBU) after the installation of patch PSB*3*105. After the
patient is discharged or a date of death is entered for him/her the patient
data is not being properly removed from the BCBU workstation. In the case of
discharged patient that are later admitted or have a clinic appointment their
orders from their previous admission are still visible on the BCBU
workstation and are listed on the patient's Medication Administration Reports
(MAR).
Resolution:
-----------
Removed the filter introduced by PSB*3*110 to prevent alerts from being
generated for patient movements if the patient is no longer inpatient. The
INC0962039 - WNY - Vista Not Updating BCBU orders when patients are
reason is because such filter prevented patient discharge events, which are
handled as patient movements, from removing he patient's data from the
BCBU workstation. The filter was re-introduced at the Alert generation point
and exclude patient discharge movements.
Technical Resolution:
---------------------
Changed the routine ALPBCBU to remove the filter from the PMOV line tag and
placed a check in the ERRLOG line tag to prevent Alerts for patient movement
events after the patient had already been discharged.
discharged/deceased
INC1002829 - BCBU patient census not updating
(Duplicate)
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
Patch PSB*3.0*111 corrects one issue in the report 'Missing Dose
Followup'. The issue reported by a single site at a multidivisional
setting is that after one record is selected for completion and is saved,
it is not dropping off the list of available records. The expected
bahavior is that after one record in the report is completed and saved, it
should no be part of the list.
Reference: INC1537335 - GLA - PBS*3*100 Patch Missing Dose Followup list
is not updating after resolving the missing dose.
This patch will resolve the following issue.
Problem:
--------
Bath VA Medical Center reported a problem with the BCMA Medication Admin
History report for patch medication orders. For certain situations the report
omits a patch given action if the same patch removal date falls outside the
date range selected to run the report. In the report example below run
on 08/30/2018, for the date range 08/27/18 thru 08/29/2018 the 'G0800' under
the 08/29/2018 column would not be displayed because the patch applied on
08/29/2018 was already removed on 08/30/2018 and 08/30/2018 was not included
in the report date range.
=============================================================================
Location | | | | |
Start Date Stop Date | Admin | | | |
and Time and Time | Times | 08/27/2018 | 08/28/2018 | 08/29/2018|
-----------------------------------------------------------------------------
INPATIENT | | | | |
08/25/2018 09/14/2018| 0800 | RM0755 | RM0755 | RM0755 |
@07:00 @08:00 | | G0800 | G0800 | G0800 <-- |
INC1697793 - BCMA med log and medication administration history reports
| | | | |
FENTANYL TRANSDERMAL PATCH | | | | |
FENTANYL TRANSDERMAL | | | | |
50MCG/HR PATCH Give: ONE | | | | |
(50MCG/HR) PATCH TOP MISC Q24H| | | | |
| | | | |
Removal Times: 0800 | | | | |
RPH: RN: | | | | |
Special Instructions:
TESTING BCMA PATCH ISSUE
display
-----------------------------------------------------------------------------
Resolution:
-----------
Modified the VistA code responsible for generating the report content to check
the 'Given' Date/Time when the 'Removal' Date/Time falls outside the date
range selected for the report. If the 'Given' Date/Time is within the date
range selected then the entry will be included in the report.
Technical Resolution:
---------------------
Changed the routine PSBOMH1 at EN+5 and EN+9 to check for the 'Given' date
when the 'Removal' date falls outside the date range selected for the report.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
INC1697793 - BCMA med log and medIcation administration history reports
display
In preparation for the VA's transition to become two factor authentication
(2FA) compliant the BCMA Graphical User Interface (GUI) requires an
upgrade to Delphi version XE8 in order to implement the new Remote
Procedure Call (RPC) Broker allowing compliance.
This patch also updates the Med Order Button to utilize the same version
of the Dynamically Linked Library (DLL) as the Computerized Patient
Record System (CPRS). The version number is controlled by the PSB MOB
DLL REQUIRED VERSION parameter.
This patch addresses the request from NSR #20170515 - Adds Respiratory
Therapy Report.
After this patch is installed, Respiratory Therapists will have access to
the new option Report for Respiratory Therapy Medications [PSB
RPT RESP THERAPY MEDS] VistA to produce a report of patients on
Respiratory Therapy medications.
This patch will resolve the following issue.
Problem:
--------
Captain James A. Lovell Federal Health Care Center reported a problem with
the BCBU Initialize options below:
Default Workstation Initialize [PSB BCBU INIT WRKSTN DFT]
Divisional Workstation Initialize [PSB BCBU INIT WRKSTN DIV]
Whenever these options were executed and one or more Workstation Link were
selected for the initialization the option still generated and sent HL7
message updates to all other existing BCBU Workstation Links.
Solution:
--------
The two Workstation Initialize options above were modified to screen out any
Workstation Link not selected from the HL7 update if the user selects one or
more specific Workstation Link(s) to update when executing these options. In
other words, only the selected Workstation Link(s) will be initialized.
INC2794138 - When BCBU init is ran and only one HL7 link is entered it still
Technical Resolution:
---------------------
The routines ALPBIN, ALPBIND and ALPBINP were modified to keep track and
screen out Workstation Link(s) not selected for the HL7 initialization
update.
updates numerous links
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
INC2794138 - When BCBU init is ran and only one HL7 link is entered it still
updates numerous links
This patch will resolve the following issue.
--------
James A. Haley VA Medical Center reported a problem with the BCMA Missed
Medication Report. They were getting an error whenever they tried to run it
for a patient that had a PATCH medication order and the dispense drug had
been edited using the BCMA GUI. An additional side effect was the fact that
the order no longer showed on the patient's VDL.
Resolution:
-----------
The error happened because the Transdermal Project patch PSB*3*83 assumed the
IEN for the DISPENSE DRUG sub-file (#53.796) in the BCMA MEDICATION LOG file
(#53.79) would always be 1 (one) for a PATCH medication order. Such
assumption turned out to be incorrect because when the user edits the
dispense drug for an order in BCMA the IEN 1 gets deleted and IEN 2 gets
created. If a second edit is performed IEN 2 is then deleted and IEN 3 gets
created and so forth. That's the reason the order would not show up on the
BCMA Patient's VDL and also caused the Missed Medication Report to error out.
Technical Resolution:
---------------------
INC2383720 - Error at REMOVES+23^PSBULTL unable to run report in BCMA
Changed the following routines: PSBMLEN, PSBMLEN1, PSBO1, PSBUTL, PSBVDLPA,
PSBVDLRM and PSBVDLVL to retrieve the first dispense drug in the DISPENSE
DRUG sub-file (#53.795) instead of assuming the IEN 1 to contain the order
dispense drug. For PATCH medication orders there should only be one dispense
drug.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
INC2383720 - Error at REMOVES+23^PSBULTL unable to run report in BCMA
Problem:
This patch will resolve the following issue.
INC4109840 - CPRS shuts down repeatedly when trying to access BCMA
(Duplicate) medication history record in CPRS reports tab
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
INC3683945 - AEU can't look at med admin history (BCMA) due to an error after
inputting a date range
INC3570947 - CPRS error caused by patch PSB*3*112, installed at our site on
(Duplicate) 12/11/2018
INC3507924 - In CPRS trying to run the Med Admin History report for 11-29
(Duplicate) through 12-5 get the attached error message <UNDEFINED>EN+112^
PSBOMH1 *PSBAR(64988)
INC4109840 - CPRS shuts down repeatedly when trying to access BCMA
(Duplicate) medication history record in CPRS reports tab
Problem:
--------
After the release of PSB*3*112 a new issue was introduced that caused the
BCMA Medication Admin History Report to cause an <UNDEFINED> error and exit
the BCMA GUI application. The problem is specific to a patient with a PATCH
INC3683945 - AEU can't look at med admin history (BCMA) due to an error after
Medication with a ONE TIME schedule (ex: Start Date of D and End Date of D+1)
and after the PATCH is given on day D and marked removed on day D+1, when the
user ran the report for the date Range D thru D the error happens.
Resolution:
-----------
This patch prevents the error from happening when the BCMA Medication Admin
History Report is run following the instructions above.
Technical Resolution:
inputting a date range
---------------------
Changed the routines PSBOMH and PSBOMH1 to prevent the PSBAR array from
crashing when the subscript is undefined.
INC3570947 - CPRS error caused by patch PSB*3*112, installed at our site on
(Duplicate) 12/11/2018
INC3507924 - In CPRS trying to run the Med Admin History report for 11-29
(Duplicate) through 12-5 get the attached error message <UNDEFINED>EN+112^
PSBOMH1 *PSBAR(64988)
This patch will resolve the following issue.
--------
The South Texas Veterans Health Care Medical Center reported two problems
with the the Initialize a Backup Workstation with BCMA Users [PSB BCBU USER
INIT] option:
1) Users were not able to access the BCBU workstations with their ACCESS/
VERIFY codes after the option above was run. Thei ACCESS/VERIFY codes
should match what they use in the main VistA account. Usually, a re-run
of the option resolves the problem, which is not ideal.
2) If there are two users with similar names (e.g., 'NURSE,USER' and
'NURSE,USER A' existed, the user with the shorter name would not be able
to access the BCBU workstation, even after the second initialization.
Resolution:
-----------
1) The setting of cross-references for the newly created users at the
initialized BCBU workstation was being executed before their ACCESS/
VERIFY codes were saved. To resolve the problem the cross-references
setting was moved to run after the ACCESS/VERIFY codes are saved and it
will address this problem.
2) The problem happened because the user lookup for 'NURSE,USER' would
INC3062938 - BCBU/VISTA
find more than one match, 'NURSE,USER' and 'NURSE,USER A' which would
prevent it from being updated. To resolve this problem the lookup call
to find the user record was changed to perform and EXACT match for the
user name. This way a lookup for 'NURSE,USER' will not find 'NURSE,USER
A' as a possible match.
Technical Resolution:
---------------------
1) Moved the call to IX1^DIK from line FILE+19 to FILE+23 in the ALPBGEN1
routine, which is past the setting of the ACCESS/VERIFY codes.
2) Changed the DIC(0)="LM" to DIC(0)="LMX" at line FILE+9 in the ALPBGEN1
routine, which will force an exact match of the user name.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
INC3062938 - BCBU/VISTA
Problem:
This patch will resolve the following issue:
N/A
Patient Safety Issues (PSIs):
-----------------------------
N/A
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1. INC5649941 - Medication Patches with a continuous schedule (daily)
do not show as administered when viewing the medication
administration history report in CPRS with a date
Problem:
-------
The Canandaigua VA Medical Center reported that the Medication
Administration History (MAH) Report does not display all the
administration activity (given/removed) of continuous patch medication
orders depending on the date range selected for the report. When the date
range selected for the MAH report exceeds 7 days and there is a Given
activity for a patch medication on the last day of the first week, the
1. INC5649941 - Medication Patches with a continuous schedule (daily)
report will not display it if the patch was already Removed at the time
the report was ran.
Resolution:
----------
This patch will correct the code to include the Given activity for a
patch on the last day of the first week in the report.
Technical Resolution:
--------------------
do not show as administered when viewing the medication
The code at the EN+62 on the PSBOMH1 routine was not taking into account
that the Given date for the order being processed could fall on the week
before the week of the Removal in the report. The code was changed to
include the Given activity in the correct week of the report.
administration history report in CPRS with a date
New Service Requests (NSRs):
----------------------------
This patch will resolve the following issues:
--------------------------------------------
1) INC8817299 -BCBU MAR Shows Expired Meds as Requiring Administration
Problem:
--------
BCBU MAR reports were showing medications on the grid as needing
administration on their Stop date/time, when the time value ends in a zero,
e.g. 0900 & 0930.
Solution:
--------
Correct BCBU routine ALPBFRM1 to put asterisks in that time cell on the MAR
Grid.
Technical Resolution:
---------------------
In routine ALPBFRM1, "+" the variable, when it is created after it
concatenates the time to the end of the date. This will trim off
insignificant trailing zeros, prior to later compare operations checking if
the grid cell date.time is = to the stop date.time of this order.
1) INC8817299 - BCBU MAR Shows Expired Meds as Requiring Administration
2) INC9226190 - BCMA Contingency program requires verify code be changed
each time you log into the program
Problem:
--------
VA Western New York Healthcare System at Buffalo reported that after patch
PSB*3*122 was installed the Initialize a Backup Workstation with BCMA Users
[PSB BCBU USER INIT] option which is used to send BCMA users over from VistA
to the BCBU workstation was forcing the users to change their VERIFY CODE at
2) INC9226190 - BCMA Contingency program requires verify code be changed
the BCBU workstations when they tried to logon. It was confirmed that the
issue was introduced by PSB*3*122. In order to fix the problem that required
the option above to be run twice in order for the new users ACCESS/VERIFY
CODEs to work the re-indexing of the new records on the NEW PERSON file (#200)
was moved past the "hard setting" of ACCESS/VERIFY CODEs, which resolved the
original but the re-indexing also treats the ACCESS CODE as new and therefore
forces a new VERIFY CODE to be entered by the user at the BCBU workstation.
Solution:
--------
each time you log into the program
Kept the "hard setting" of the ACCESS CODE prior to re-indexing the new record
in the NEW PERSON file (#200) but moved the "hard setting" of the VERIFY CODE
information after the re-indexing which addresses the issue.
Technical Resolution:
---------------------
Moved the call "D IX1^DIK" up to FILE+20, before setting the VERIFY CODE
information.
INC9209704(d) - Modify MIW BCMA BU devices to prevent users from needing
to create a secondary Verify Code
Defect Tracking System Ticket(s) & Overview:
*** Bar Code Medication Administration (BCMA) Version 3.0 ***
1. Problem: NOIS ISB-0603-31561
previous order will display on the new order based on the IV Site
Parameter settings in the GUI BCMA Site Parameters application.
A medication order that has administration times set for today, but
before the Start Time of the order, displays on the Bar Code Medication
Administration (BCMA) Due List Report.
Corrective Action:
The Due List Report will not display medication orders until the Start
Date/Time of the medication order takes affect.
2. Problem: NOIS ISB-0903-31964
When the user selects a time frame for the Medication Administration
History (MAH) Report and no administrations are due, the report lists the
medication order number from Inpatient Medications V. 5.0 under the
"Initial-Name Legend" section.
Corrective Action:
The MAH Report will not display the order number from Inpatient
Medications V. 5.0 under the "Initial-Name Legend" section when no
administrations are due for a specific time frame.
This build consists of BCMA Version 3.0 rollover code and resolution to a
3. Problem: NOIS LAH-1203-61493
The user receives the following error message, "BCMA failed to
communicate with VISTA," if the Graphical User Interface (GUI) BCMA times
out and is unable to connect to the server.
Corrective Action:
The processing time for the GUI BCMA software to display the patient s
record on the BCMA Virtual Due List (VDL) has been reduced.
4. Problem: NOIS LIT-0603-71923
few outstanding BCMA defects.
Users sometimes receive an "allocation failure" error message when
accessing a patient s record using the GUI BCMA.
Corrective Action:
The "allocation failure" error message has been corrected.
5. Problem: NOIS MAD-1203-42204
The MAH Report takes an extended amount of time to run if the Start Date
and the Stop Date of the report, requested by the user, are for different
years. For example, if the Start Date is 12/28/03 and the Stop Date is
01/03/04.
Corrective Action:
The user can now request different years for the MAH Report without
experiencing extended delays as BCMA accesses the data.
6. Problem: NOIS MIN-1203-41637
Users sometimes experience an "Invalid Medication Lookup" error message
after scanning a medication in the "Scan Medication Bar Code:" field of
the "Order Manager" dialog box when using the BCMA Med Order Button in
Listed below are primary National Online Information Sharing ticket
GUI BCMA.
Corrective Action:
The BCMA medication lookup process has been corrected to properly
validate the medications scanned in the "Scan Medication Bar Code:" field
of the "Order Manager" dialog box in GUI BCMA.
7. Problem: NOIS UNY-0104-10174
Multiple IV medication orders display as merged on the IV Medication Tab
after an order is discontinued, but the IV bag is still infusing.
(NOIS) identification information representing BCMA defects/problems
Corrective Action:
Multiple IV medication orders will display properly on the IV Medication
Tab.
8. Problem: NOIS TNV-0104-30647
Users sometimes experience the following error message, "ERROR: 16^Server
Protocol Disabled," when using the Edit Medication Log [PSB MED LOG EDIT]
option. This occurs when the PSB BCMA RASO17 SRV Health Level Seven (HL7)
server protocol is being disabled.
and their respective corrective action.
Corrective Action:
The error message is only intended to notify the BCMA software that the
protocol is being disabled. BCMA will now validate the message and not
display it to users.
9. Problem: NOIS ISB-0104-31384
When an IV medication order with an infusing bag is "Renewed," the
renewed order continues to display on the IV Medication Tab of the BCMA
VDL until the infusing bag is "Completed," even if the "Renewed" order's
Start Date/Time has expired.
Corrective Action:
When an IV medication order with an infusing bag is "Renewed," the
renewed order will continue to display on the IV Medication Tab of the
BCMA VDL until the infusing bag is "Completed," or until the Start
Date/Time of the new order that was created during the renewal process.
Once the new order is active, the infusing bag from the previous order
will display on the BCMA VDL with the new order, along with any
additional bags created from the new order. Any available bags from the
