| VERSION |
-
- 3.0
- DATE DISTRIBUTED: 2005-11-19 00:00:00
- PATCH APPLICATION HISTORY:
-
-
- 4 SEQ #1
- DATE APPLIED: 1999-06-02 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
The following changes were made to address Y2K compliance issues.
Routine: PSUCP
Line Tag: AUTO+11
Exception: The calculations performed incorrectly when Y2K dates were provided.
Resolution: Changed S...to
S PSUSDT=PSUMON_"01"
S PSULY=$$LEAPYR(PSUMON)
S X=U_$E(PSUMON,4,5)_U
Routine: PSUCP
Line Tag: TIMINGQ+1
Exception: The calculations performed incorrectly when Y2K dates were provided.
Resolution: Added...
;
LEAPYR(FMYR); Check to see if year is a leap year: 1=leap year, 0=not leap year
N YYYY
S YYYY=1700+$E(FMYR,1,3)
Q (((YYYY#4=0)&(YYYY#100'=0))!((YYYY#100=0)&(YYYY#400=0)))
Routine: PSUCP
Line Tag: AUTO+10
Exception: The calculations performed incorrectly when Y2K dates were provided.
Resolution: Changed I...to
I $E(PSUMON,4,5)="00" S PSUMON=($E(PSUMON,1,3)-1)_"12" ; set to
...Dec. of previous year if this month is Jan.
-
- 11 SEQ #10
- DATE APPLIED: 2000-06-12 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problem:
The AR/WS data report is printing spurious items in the message when the
report is reporting "No data to report"
Resolution:
The array being passed to Mailman had left over data in non-numbered nodes
from previous calculations. The array is now properly initialized.
-
- 12 SEQ #11
- DATE APPLIED: 2000-10-27 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
1. Problem: The Pharmacy Benefits Controlled Substance extract is dropping
the breakdown unit and package size information from some of the category
2 drug prescriptions in the PBM CS Statistical Data report.
Resolution:
The coding has been corrected and the appropriate breakdown unit and
package size information is being presented.
-
- 14 SEQ #12
- DATE APPLIED: 2001-01-03 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Pharmacy Benefits Management (PBM) has requested additional data elements
to be included in the pharmacy extracts. This patch adds those additional elements.
-
- 15 SEQ #13
- DATE APPLIED: 2001-02-02 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
The IV solution data record has an extra ^^^^ element and several NO DATA
entries that should not be there.
Resolution:
The code within the IV solution data record building has been modified so
that the data elements are proper.
-
- 17 SEQ #14
- DATE APPLIED: 2001-05-07 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
1. Problem:
Some PBM reports do not process correctly and other reports are
incorrect.
Resolution:
Routine PSUPR2 modified to accommodate new location naming conventions.
-
- 16 SEQ #15
- DATE APPLIED: 2001-11-06 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
1. The outpatient extracts utilize the fill date of prescriptions for
2. The current extracts are shipping data for test patients which is
undesirable.
Resolution:
The extracts have been coded to exclude test patients.
3. The procurement extracts generates an error when an alpha-numeric prime
vendor number is encountered.
processing. It is desired to use the release date instead of the fill date
Resolution:
The procurement extract has been corrected to allow alpha-numeric prime
vendor numbers.
for processing.
Resolution:
The outpatient extracts have been reprogrammed to process prescriptions by
their release date.
-
- 18 SEQ #16
- DATE APPLIED: 2001-11-21 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problem:
In some instances, the right node does not exist, causing the
error to be generated.
Resolution:
The solution is to check for the existence of the right node. If it does
not exist, the program bypasses the line of code without error.
When the Automatic Pharmacy Statistics [PSU PBM AUTO] option extract is
run,
the following error is generated:
<UNDEFINED>COMVAR+2
S PSUSIG=$P( ^TMP("PSOR",$J,PSURXIEN,"SIG",1,0),U,1)
-
- 19 SEQ #17
- DATE APPLIED: 2002-06-26 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch includes the creation of new Pharmacy Benefits Management
Modified extracts are (1) IV, (2) Unit Dose, (3) Prescription, (4)
Controlled Substance.
Users are also provided with the ability to generate a detailed MailMan
message without having to transmit to the PBM database at Hines.
extracts and summary reports as well as modifications to existing
extracts.
New extracts are (1) Patient Demographics, (2) Outpatient Visits, (3)
Inpatient PTF Records, (4) Provider data.
New summary reports are (1) Patient Demographic summaries for the IV,
Unit Dose, and Prescription extracts, (2) Provider data summary.
-
- 21 SEQ #18
- DATE APPLIED: 2003-01-09 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch contains modifications to the Pharmacy Benefits Management
2. This patch also corrects the following problem: Sites that are not
using the Surgery package receive a "missing routine" error
because the PBM extract incorrectly makes a call to a supported Surgery
API.
Solution: The code is altered to omit reference to the Surgery API, and
replaces it with a call appropriate to PBM.
package.
1. The Patient Demographics extract will transmit new Ethnicity and
multiple Race fields. The new fields comply with the new Race and
Ethnicity Standards as set forth by the Office of Management and Budget.
Old race information will continue to be extracted when it is present.
New ethnicity and race information will be extracted as it is available.
-
- 20 SEQ #19
- DATE APPLIED: 2003-01-23 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problem 1:
29 is not recognized as a legitimate end date for the February extract in
non-leap years. Therefore the end date defaults to the start date and the
date range displays as February 1 to February 1.
Resolution 1:
The code for the Manual Pharmacy Statistics [PSU PBM MANUAL]
option is altered to take leap years into account so that the correct
February date range is displayed on all PBM messages.
Problem 2:
At some facilities the Mailman message subject header on the PBM
Messages displays only the facility/division number, and does not
display the name of the facility/division.
Resolution 2:
There are two possible solutions to this problem. (1) Some sites have
For the Manual Pharmacy Statistics [PSU PBM MANUAL] option, the date range
assigned more than one division name to a division number in file
#40.8. In these instances, a user at the site should correct the file
definitions so that only one division name is assigned to one division
number. (2) The code is altered to correct missing division names on
the message headers when the problem is not user error.
for the February extract does not distinguish leap years from non-leap
years. The end date for the February extract on all reports other than
the Timing and Confirmation messages is always recorded as February
29, regardless of whether it is a leap year or not.
In addition, on the PBM Timing and Confirmation messages, February
-
- 5 SEQ #2
- DATE APPLIED: 1999-07-19 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problems resolved with this patch:
2. "Pharamacy" is used and is misspelled in PSUCP.
Resolution:
"Pharamacy" has been changed to "Pharmacy"
1. The domain for the transmissions to Hines has changed.
Resolution:
The domain has been changed to be CMOP-HINES.DOMAIN.EXT
-
- 23 SEQ #20
- DATE APPLIED: 2003-03-29 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch contains modifications to the Pharmacy Benefits Management
prevents an error from occurring.
(PBM) package.
Problem: When the monthly Prescription extract runs, an error occurs in
the prescription patient demographics report if social security numbers
are missing on patients included in the extract.
Solution: Code has been altered to omit patients from the prescription
patient demographics report if social security numbers are missing. This
-
- 22 SEQ #21
- DATE APPLIED: 2003-04-30 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch makes a correction in the Pharmacy Benefits Management Provider
Solution: If any of the following provider classifications are listed as
missing a subspecialty only, they are omitted from the Provider summary
report.
Resident - Allopathic
Resident - Osteopathic
Intern - Allopathic
Intern - Osteopathic
extract summary report. It removes providers from the summary report who
have erroneous missing data.
1. Problem: At teaching hospitals, interns and residents are reported as
having missing subspecialties on the Provider extract summary report.
This
is incorrect, since by definition interns and residents never have
subspecialties. Therefore these should be removed from the report.
-
- 28 SEQ #22
- DATE APPLIED: 2003-09-12 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
PHASE II of the TRANSITIONAL PHARMACY BENEFIT project requires a new
If a prescription in the PRESCRIPTION file #52 has a TPB RX status of
"YES", both the Prescription Patient Status and the Provider Type
elements in the transmission will be set to "NVA".
category to be added to each of the set of codes for the Prescription
Patient Status and the Provider Type elements of the outpatient
prescription transmission of the Pharmacy Benefits Management (PBM)
extracts.
The new element added to each set of codes is "NVA", which stands for
NoN-VA.
-
- 30 SEQ #23
- DATE APPLIED: 2003-10-23 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problem: The PBM extract element PATIENT STATUS would be set to 'NVA' if
the SC/A&A/OTHER/INPATIENT/NVA field (#6) were NULL in the RX PATIENT
STATUS file (#53).
Resolution: The code has been changed that for the above condition the
PBM PATIENT STATUS element will be set to "" (null).
-
- 26 SEQ #24
- DATE APPLIED: 2003-10-23 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
REMOVE FORM FEEDS
-
- 32 SEQ #25
- DATE APPLIED: 2004-01-31 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Lab Data Summary. Send in email message but do not print hard copy as the
report is not in a usable format.
Outpatient Statistics will be modified to print all divisions.
-
- 24 SEQ #26
- DATE APPLIED: 2004-09-17 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch decrease processing time, truncation of the ICN and prevents
duplicate jobs.
-
- 34
- DATE APPLIED: 2004-10-15 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Phase I of the Inpatient Medications Requirements for the Special Focus
OR*3*213 ORDER ENTRY/RESULTS REPORTING V. 1.0
PSU*3*34 PHARMACY BENEFITS MANAGEMENT V. 3.0
Patches PSS*1*79, OR*3*213, and PSU*3*34 contain changes to support the
following enhancements in PSJ*5*110:
1. The Extend Stop Date on Renewal enhancements will allow an order to be
renewed without creating a new order. Editing of the start date will no
longer be allowed during the renewal process. In addition, limits have
been set on the length of time after an order expires that it may be
Group IRA project consists of four patches. The patches are combined in
renewed. This is outlined in the BCMA 2001 Special Focus Report,
Requirement #11.
2. The Complex Order enhancements will change the way complex orders are
handled by linking complex components (child orders) together. If the
actions Finish, Verify, Discontinue, or Renew are taken on one child
order, the user will be alerted that the action must be taken on all of
the complex component orders in the set. The user will then be prompted
to take the appropriate action on each child order in the complex order
set. This is outlined in BCMA 2001 Special Focus Report, Requirement #8.
host file PSJ_PSS_OR_PSU_110.KID in order to simplify installation at VHA
3. The STAT and NOW Order Notification enhancements will alert users
subscribing to new mail group PSJ STAT NOW PENDING ORDER when a pending
STAT or NOW order has been received from Computerized Patient Record
System (CPRS) V. 1.0. Users subscribing to the new mail group PSJ STAT
NOW ACTIVE ORDER will receive an alert when a STAT or NOW order is made
active. This is outlined in BCMA 2001 Special Focus Report, Requirement
#12.
Changes to PHARMACY BENEFITS MANAGEMENT (PBM) V. 3.0 have been included
facilities. Installation of this host file should be coordinated among
in this patch to address the following issues:
1. Problem: The changes to renewed orders introduced by the Inpatient
Medications Requirements for the Special Focus Group IRA, Phase I project
will allow renewed orders to have an active status for periods of time
that exceed the current PHARMACY BENEFITS MANAGEMENT (PBM) V. 3.0 time
period parameters.
Solution: The code searching for IV and Unit Dose activity within the
transmitting period has been modified to accommodate the extended periods
the four packages affected since only one installation is necessary. The
of time orders may contain an active status as a result of the changes
introduced by the Inpatient Medications Requirements for the Special
Focus Group IRA, Phase I project.
2. Problem: In several extracts only the first portion of the patient
Integration Control Number is being extracted. The entire Integration
Control Number needs to be exported.
Solution: Patch PSU*3*34 will correct and extract the entire Integration
Control Number in the IV multiple (#100) in the Pharmacy Patient file
patches, in order of install, are:
(#55) and the UNIT DOSE multiple (#62) in the Pharmacy Patient file
(#55).
Patch PSU*3*24 will correct the problem in all other applicable files.
This is being done so that patch 24 and 34 can move forward without
conflict.
PSS*1*79 PHARMACY DATA MANAGEMENT V. 1.0
PSJ*5*110 INPATIENT MEDICATIONS V. 5.0
-
- 31 SEQ #28
- DATE APPLIED: 2004-12-28 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
MISSING DIVISION NAMES ON OUTPATIENT DATA WHEN THERE ARE MULTIPLE ENTRIES
IN FILE 59 (OUTPATIENT SITE) WITH THE SAME SITE NUMBER.
-
- 35 SEQ #29
- DATE APPLIED: 2005-01-18 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
UNDEFINED ERROR IN PSUIV1 WHEN CREATING MONTHLY EXTRACT.
-
- 1 SEQ #3
- DATE APPLIED: 1999-07-19 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problems resolved with this patch:
HIN-1198-41911
9. Some Mail message headers showing a 'null' user identity. The variable
XMDUZ was not being reset for subsequent messages.
Resolution:
The variable XMDUZ is set for each message generated.
10. IV statistics are wrong. A mix of calculation variables being used
were wrong.
NTH-0199-72479
Resolution:
The proper variables were identified and calculations re-coded.
11. The Controlled Substance Statistical Data report columns need to be
better aligned and the footnotes "* Non-Formulary" and "# Not on National
Formulary"" are missing.
Resolution:
The Controlled Substance Statistical Data report has been modified.
TAM-0299-30835
12. The Controlled Substance extract errors out when a type 2 transaction
has a quantity = 0.
NOIS:
MUR-0199-31080
Resolution:
The logic has been modified to quit the transmission of a record when the
quantity = 0.
13. The procurement extract was building lines in the MailMan messages
that were exceeding MailMan acceptable parameters.
NOIS:
LON-1198-60747
LEB-0299-20160
Resolution:
The length of the description of items contained in the extract have been
limited to 50 characters.
Resolution:
14. Undefined variable error in the procurement extract was generated due
to data arrays not being initialized properly.
NOIS:
EKH-0199-42100
NAS-0299-30308
WPB-0299-31308
Resolution:
The XMY array is now properly reset providing the address for the
The data arrays are properly initialized.
15. Controlled Substance reports are improperly flagging formulary drugs
as non-formulary.
NOIS:
MAR-0299-21304
Resolution:
The logic for flagging the formulary status has been corrected.
subsequent messages.
16. The AR extracts would send out multiple detailed messages whose
contents were duplicates. This was caused by the array holding the data
not being initialized properly.
NOIS:
HIN-0199-41269
Resolution:
The code has been modified to properly initialize the data array.
17. The costing formula in the procurement extract includes a $J function
which failed when the parameters of the formula were modified. The formula
was proper but the calculation was then too complex for the $J function.
NOIS:
CAH-1298-30287
Resolution:
The code was changed to perform the calculation first outside of the $J
2. Unit Dose generates an allocation error. The PSUTA array used in the
function and then hand the result to the $J function.
unit dose extract grows too large for the local partition.
NOIS:
ALX-1298-71646
DEN-0199-51099
BED-0299-11199
Resolution:
The PSUTA array has been moved to the ^TMP global.
3. Procurement generates an allocation error. The PSUMIT array grows too
1. The XM mailer hung in the background looking for user input. Modules
large for the local partition.
NOIS:
IOW-1198-40646
Resolution:
The PSUMIT array has been moved to the ^TMP global.
4. The procurement module has cost calculation and dividing by zero
errors.
needing to send more than one detailed message to Hines for a division
The procurement costing equation was wrong and there were cases when one
of the cost-per-unit factors used in the calculations were not available
and zero was being used for division.
NOIS:
NYN-1298-10759
Resolution:
The formulas for costing factors have been amended. In cases
where the cost factors are not available the reports have been amended
were getting hung in the background. The XMY array needed to be recreated
to reflect null or NA in the reports.
5. The outpatient extracts shows the wrong division in the message
headers. The software was pulling division names from File #40.8 instead
of File #59.
NOIS:
IOW-0199-41095
Resolution:
for each subsequent message.
Routines PSUOP4, PSUOP6 have been modified to pull division names from
File #59.
6. Division names for AR/WS, Procurement, and CS in the headers are not
matching the facility numbers. The coded lookup from File #40.8 is pulling
up entries associated with IENs instead of facility numbers.
NOIS:
CTX-1198-71660
MON-1298-52507
POR-0199-52307
Resolution:
The existence of a .001 field allows the pulling up of names by IEN
numbers. The lookups for names by facility number is now coded to limit
the search to the 'C' cross-reference only.
7. The AR/WS extract is generating subscript errors at DIV+6^PSUAR1. There
are inpatient locations that may not be linked to the PHARMACY AOU STOCK
file (#58.1).
NOIS:
NOIS:
MON-1198-50086
CLA-1298-20491
CHA-0199-30249
Resolution:
The coding in PSUAR1 has been modified to accommodate cases where
inpatient locations are not linked within the PHARMACY AOU Stock File
(#58.1).
RIC-1198-20912
8. The PSUARNM array is growing too large for the local partition in the
AR/WS extract and generates allocation errors.
NOIS:
OKL-1198-70175
Resolution:
The PSUARNM array has been moved to ^TMP for storage and processing in
routine PSUAR4.
-
- 3 SEQ #4
- DATE APPLIED: 1999-10-03 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problems resolved with this patch:
2. The AR/WS extract was setting the division number to zero when it
didn't find data to transmit.
Resolution:
The division indicator is set to the default facility ID when no data is
found for transmission.
NOIS:
ISH-0399-40149
3. The IV extract was using a logic test incorrectly and the formulary
flag indicator was not being set properly for extraction.
Resolution:
The logic statement being used has been corrected.
NOIS:
MAR-0399-20146
1. The local array PSUMIT needed to be moved to ^TMP.
4. Some quantity fields have alpha suffixes which needed to be removed
prior to being entered into the data export.
Resolution:
The quantity fields now have all alpha suffixes removed prior to message
construction.
Resolution:
The array was moved into ^TMP( storage.
NOIS:
LIT-0499-70942
-
- 7 SEQ #5
- DATE APPLIED: 1999-10-19 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch contains DBIA notation additions to routines that were
released within PSU*3*1. No functional changes have been made to these
routines.
-
- 6 SEQ #6
- DATE APPLIED: 1999-12-10 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problems resolved with this patch:
1. The CS reports were reporting statistics incorrectly.
Resolution:
The code in the CS statistics has been corrected.
-
- 8 SEQ #7
- DATE APPLIED: 1999-12-10 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
1. Problem:
pulled and returns only the fields specified from the multiple identified.
2. Problem:
The automatic completion checker is falsely reporting incomplete runs. It
is scheduled to run 24 hours after the extract has started. Large sites
are seeing extracts that are taking more than 24 hours.
Resolution:
The automatic completion checker is now scheduled to run 72 hours after
the start of the extract.
3. Problem:
The procurement extract for File #58.8 DRUG ACCOUNTABILITY STATS is
looking for IV rooms in the wrong file.
Resolution:
The GETM^PSUTL API pulls all data fields within a specified multiple. This
The code has been changed to look for IV rooms in the file # 58.8.
may lead to generation of allocation errors and makes DBIA tracking
difficult.
Resolution:
The GETM^PSUTL was modified to require the itemizing of fields to be
-
- 9 SEQ #8
- DATE APPLIED: 2000-04-17 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Problem:
portions of the program.
The Controlled Substances extract is sending records that it should not.
It has tested them and found them to fail the sending criteria. The
software still sends the record.
Resolution:
Proper rejection flags were put in place between the testing and sending
-
- 10 SEQ #9
- DATE APPLIED: 2000-05-25 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
1. Problem:
2. Problem:
The auto error checker is sending a false error message even though the
extract ran to completion and reports were sent.
Resolution:
The error checker tracking of the start time has been adjusted to reflect
the three day interval between starting the extract and the queuing of the
checker's task.
The AR/WS Statistical Summary reports "NO DATA" when in fact data is
present in other reports and is being extracted and sent.
Resolution:
Code has been corrected and the report reflects statistical data properly.
- DATE INSTALLED AT THIS SITE: 1998-10-26 00:00:00
- INSTALLED BY: USER,ONE
- DESCRIPTION OF ENHANCEMENTS:
Pharmacy Benefits Managment Package
-
- 4.0
- DATE DISTRIBUTED: 2005-03-15 00:00:00
- PATCH APPLICATION HISTORY:
-
-
- 4 SEQ #1
- DATE APPLIED: 2005-10-20 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch corrects the IV AMIS Summary report for the Pharmacy
Benefits Management (PBM) Version 4.0 extract in cases where there is
very little or no IV data available for the date range of an IV extract.
-
- 13 SEQ #10
- DATE APPLIED: 2008-05-26 19:10:52
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch will correct the following,
HD198412 - PBM UNmapped locations showing again
HD227109 - PBM EXTRACT COPAY FIELD NOT FUNCTIONING
-
- 14 SEQ #11
- DATE APPLIED: 2009-04-23 12:36:53
- APPLIED BY: USER,SEVENTEEN
- DESCRIPTION:
Associated Remedy Tickets:
==========================
HD261253 - a loop in PSUAA1
d HD280061 - 2 Monthly report will not run to completion - PSUAA1 loop.
-
- 15 SEQ #12
- DATE APPLIED: 2009-07-08 14:56:11
- APPLIED BY: USER,SEVENTEEN
- DESCRIPTION:
Associated Remedy Tickets:
==========================
HD288563 - 6 PBM EXTRACT DOES NOT COLLECT ALL ICD9 CODES
HD286672 - 8 <SUBSCRIPT>VITALS+55^PSUVIT1
HD290578 - 5 <UNDEFINED>RPT+9^PSUCP1
HD293287 - 6 CONSISTENCY IN PBM EXTRACT MAIL MSG SUBJECT
HD251472 - 2 Undefined error DAT2+11~PSUDEM2
-
- 5
- DATE APPLIED: 2009-07-14 15:21:30
- APPLIED BY: USER,SEVENTEEN
- DESCRIPTION:
This patch addresses a request which support the Pharmacy Benefits
to the RACE INFORMATION field #2 or ETHNICITY INFORMATION field #6 in
the PATIENT File #2, an entry is queued in the PBM PATIENT DEMOGRAPHICS
File #59.9. Currently, because of flawed logic when edits are made to
either of these two fields, an entry is not queued.
The integration agreement #4803 was added to record the usage of routine
PSUHL by other packages.
2. The Automatic Pharmacy Statistics [PSU PBM AUTO] report generated a
Management (PBM) Extracts Enhancement #3 project. In order to allow the
<SUSBCRIPT> error condition. This error was created when the report was
run before any monthly data was filed. Routine PSUHL was modified to quit
the FOR loop at line tag CLEANUP when the DAY variable is NULL.
3. Sites reported getting <STORE>SETDPT+9^DPTLK1 errors which was traced
to the protocol PSU PATIENT DEMOGRAPHIC CHANGE called by the DG FIELD
MONITOR protocol. Line tag LOGDFN was changed to use the DBS call
UPDATE^DIE instead of the Fileman call FILE^DICN.
retransmission of only those patients who have had demographic updates,
4. During internal testing, a problem was discovered with the handling
of local data elements in routine PSUHL. The killing of those variables
presents the potential for problems later in other areas. This patch
corrects the way in which these variables are handled.
Outpatient Pharmacy V. 7.0, Inpatient Medications V. 5.0, Registration
v. 5.3 and Pharmacy Data Management V. 1.0 were modified to build an entry
for re-transmission in PBM PATIENT DEMOGRAPHICS File #59.9.
The following issues are addressed in this patch:
1. The logic in routine PSUHL was corrected so that when an edit is made
-
- 16 SEQ #14
- DATE APPLIED: 2010-05-18 15:23:18
- APPLIED BY: USER,SEVENTEEN
- DESCRIPTION:
Currently, the Pharmacy Benefits Management (PBM) extract blocks the
Problem:
========
Several facilities were reporting that selected laboratory tests were not
present in the Structured Query Language (SQL) database used by PBM to
perform medication use safety surveillance, while the source data was
clearly available in local VistA and Computerized Patient Record
System (CPRS). Upon further investigation, it was discovered that the
laboratory results did transmit as expected, but the lab test name did
not, resulting in database search failures.
transmission of chemistry lab results for "Employee Veteran" and
Resolution:
===========
The source of the error was traced to laboratory tests with a National
Lab Test (NLT) Name containing a tilde (~) character. This character
is also used as the delimiter in HL7 message processing, and the extra
tilde caused the routines that parse the transmitted data to be offset by
one data element. The correction is to translate any tilde characters in
the NLT name into an underscore (_) character, so that any remaining
tilde characters are solely present as the expected HL7 delimiters.
"Employee Non-Veteran." This patch addresses the New Service Request (NSR)
#20080810 to transmit the chemistry lab results for "Employee Veteran"
via Health Level 7 (HL7) messaging to the PBM extract database while
continuing to block the chemistry lab results for "Employee Non-Veteran."
This patch also addresses the following.
-
- 17 SEQ #15
- DATE APPLIED: 2010-08-02 15:10:42
- APPLIED BY: USER,SEVENTEEN
- DESCRIPTION:
This patch will correct an issue at CMOP-NAT sites in which a patient who
have an alias name, but no alias SSN would have their SSN overwritten
with the empty ("") alias SSN.
-
- 18 SEQ #16
- DATE APPLIED: 2011-07-19 09:59:58
- APPLIED BY: USER,SEVENTEEN
- DESCRIPTION:
When a user runs PSU PBM MANUAL reports for a large timeframe. This would
cause the XTMP global to fill up in some cases and prevent users from
logging into CPRS.
Controlled substances are showing up as being linked incorrectly to an
outpatient clinic.
Integrated facilities are not correctly distinguished between in
national reports.
-
- 20 SEQ #17
- DATE APPLIED: 2012-08-29 12:19:11
- APPLIED BY: USER,SEVENTEEN
- DESCRIPTION:
This patch will correct the following issues:
1. The technical manual is missing a note to refer users to
FORUM as a source of information for APIs and callable routines.
2. Allergy extract transmissions contain an extra delimiter if
they are longer than 254 characters.
-
- 19 SEQ #18
- DATE APPLIED: 2014-09-02 12:54:21
- APPLIED BY: USER,SEVENTEEN
-
- 1 SEQ #19
- DATE APPLIED: 2016-07-01 14:14:02
- APPLIED BY: USER,FIFTYFOUR
- DESCRIPTION:
This patch addresses the following problem:
INC1244256
The pharmacy patient IV report of the Pharmacy
Benefits Management (PBM) extract does not calculate values for returned,
destroyed, or canceled IV orders. This is because the inpatient option
Returns and Destroyed Entry (IV)(PSJI RETURNS) does not place a value for
the DAILY USAGE field that the PBM software is checking in order to add
the total number of returned, destroyed, or canceled IVs.
-
- 3 SEQ #2
- DATE APPLIED: 2006-03-08 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
The Pharmacy Benefits Management (PBM) Extract Enhancement III project
the link is configured incorrectly, the installation lists what is wrong
with the link and then aborts. The IRM can troubleshoot the link and run
the installation of PSU*4*3 once he has the link defined as specified.
This patch also includes the listening software employed at the CMOP-NAT
server. It is routines PSULRHL2 & PSULRHL3. NEITHER OF THESE ROUTINES
SHOULD BE USED AT SITES. These should only be deployed on the CMOP-NAT
server for PBM.
provides enhancements to send all chemistry lab test results to the
Consolidated Mail Outpatient Pharmacy (CMOP) National Server. These
results are sent via Health Level 7 (HL7) messages using the Health Level
Seven Optimized (HLO) messaging service.
This patch includes an environmental check routine. The preinstallation
steps require the logical link, PSU SEND, to be defined correctly. It
checks to see if it is unfurling within a test area or a live area and if
-
- 22 SEQ #20
- DATE APPLIED: 2017-11-28 12:48:09
- APPLIED BY: USER,FIFTYFOUR
- DESCRIPTION:
This patch will resolve the following issues.
Problem:
--------
The PBMAMIS reports generated by the Manual Pharmacy Statistics [PSU PBM
MANUAL] option sometimes will calculate the Total Cost column incorrectly.
There is a specific situation where the cost from an IV order of one type can
be added to the cost of a different IV type. Below you can see all the all
the reports generated by the that are affected by this issue:
IV AMIS Summary for MMM DD,YYYY through MMM DD,YYYY for DIVISION NAME
LVPs LVPs LVPs LVPs LVPs Total NET LVPs
Division DISP RET DES CAN DISP Cost DISP
-----------------------------------------------------------------------------
DIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99
-----------------------------------------------------------------------------
Total 999 999 999 999 999 $ 999.99 $ 999.99
NET Cost/
1. R15508923FY17 - PBM IV Total Cost column incorrect
IVPBs IVPBs IVPBs IVPBs IVPBs Total NET IVPBs
Division DISP RET DES CAN DISP Cost DISP
-----------------------------------------------------------------------------
DIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99
-----------------------------------------------------------------------------
Total 999 999 999 999 999 $ 999.99 $ 999.99
NET Cost/
TPNs TPNs TPNs TPNs TPNs Total NET TPNs
Division DISP RET DES CAN DISP Cost DISP
-----------------------------------------------------------------------------
DIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99
-----------------------------------------------------------------------------
Total 999 999 999 999 999 $ 999.99 $ 999.99
NET Cost/
CHEMO CHEMO CHEMO CHEMO CHEMO Total NET CHEMOs
Division DISP RET DES CAN DISP Cost DISP
-----------------------------------------------------------------------------
DIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99
-----------------------------------------------------------------------------
Total 999 999 999 999 999 $ 999.99 $ 999.99
NET Cost/
SYRs SYRs SYRs SYRs SYRs Total NET SYRs
Division DISP RET DES CAN DISP Cost DISP
-----------------------------------------------------------------------------
Defect Tracking System Ticket(s) & Overview:
DIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99
-----------------------------------------------------------------------------
Total 999 999 999 999 999 $ 999.99 $ 999.99
The discrepancy happens for patients with an order that has an internal
number that matches the number of a subsequent record of the last IV counted
for the Total Cost, then the cost of that order will get included into the
total even if it is of the different type.
--------------------------------------------
Resolution:
-----------
Modified the routines PSUV6, PSUV7, PSUV8, PSUV9 and PSUV10 to include the
patient Social Security Number (SSN) when comparing the order number for
calculating the total for the IV type. This will prevent an order from a
different to be included in the total for the wrong IV type.
1. R15508923FY17 - PBM IV Total Cost column incorrect
-
- 23 SEQ #21
- DATE APPLIED: 2018-04-03 15:29:05
- APPLIED BY: USER,FIFTYFOUR
- DESCRIPTION:
This patch will resolve the following issue:
Problem:
--------
The CMOP-Nat VistA system migrated to the Region 1 Denver Data Center on
July 29, 2017. During the migration a problem was identified with the HL
Logical Link "PSU SEND". It was discovered that the HL Logical Link entry
on all VAMC VistA systems was set with an invalid DNS DOMAIN of
"CMOP-NAT.DOMAIN.EXT". The Region 1 Denver Data Center migration team along
with the National VistA Migration Team requested that a national software
patch be created and released to update the "PSU SEND" entry in the HL
Logical Link file to use the correct DNS DOMAIN "HL7.CMOP-NAT.DOMAIN.EXT".
This change is required so that when there are hardware changes to the
CMOP-Nat VistA system, VistA HL7's DNS-aware functionality will automatically
update the link's IP address without requiring individual, manual updates at
each site. During the migration as a work-around, "CMOP-NAT.DOMAIN.EXT" and
its associated IP were broadcasted nationally so there would be no disruption
to message traffic being sent by the VAMCs, but "HL7.CMOP-NAT.DOMAIN.EXT" is
the preferred and best long-term solution. The PSU SEND logical link was
created during the pre-install steps of PSU*4*3 (PBM EXTRACT ENHANCEMENT
III).
1. I16082026FY17 - PSU SEND has incorrect DNS DOMAIN
Resolution:
-----------
A post-install routine (PSO23PI) will be executed following the installation
of this patch and will perform the following update if necessary:
1. Loop through all the records in the HL LOGICAL LINK file (#870) and
retrieve the value for the DNS DOMAIN field (#.08)
2. If the DNS DOMAIN value (converted to uppercase) is different than
"CMOP-NAT.DOMAIN.EXT", skip the record (no update)
3. If the DNS DOMAIN uppercase value is equal to "CMOP-NAT.DOMAIN.EXT",
update it to "HL7.CMOP-NAT.DOMAIN.EXT"
Once the patch PSU*4*23 successfully installs a Mailman message will be sent
to the PSU MAIL group and the person who installed the patch with the
following information:
Subj: PSU*4*23 DNS DOMAIN CMOP-NAT.DOMAIN.EXT Update [#2737116]
From: POSTMASTER In 'IN' basket. Page 1 *New*
--------------------------------------------------------------------------
The post-install routine performed the following updates:
HL LOGICAL LINK DNS DOMAIN (Before Patch) DNS DOMAIN (After Patch)
--------------------- ------------------------- ------------------------
PSU SEND CMOP-NAT.DOMAIN.EXT HL7.CMOP-NAT.DOMAIN.EXT
Enter message action (in IN basket): Ignore//
In case the post-install routine does not find any entries in the HL LOGICAL
LINK file that needs to be updated it will instead send this message:
Defect Tracking System Ticket(s) & Overview:
Subj: PSU*4*23 DNS DOMAIN CMOP-NAT.DOMAIN.EXT Update [#2737114]
From: POSTMASTER In 'IN' basket. Page 1
-------------------------------------------------------------------------
The post-install routine found no records in the HL LOGICAL LINK file
(#870) with the DNS DOMAIN field (#.08) set to 'CMOP-NAT.DOMAIN.EXT'.
No updates performed.
Enter message action (in IN basket): Ignore//
--------------------------------------------
Note: Non-production accounts usually have the DNS DOMAIN field (#.08) in
HL LOGICAL LINK file (#870) set to null/blank and for this reason this
patch will make no update in most of these accounts.
1. I16082026FY17 - PSU SEND has incorrect DNS DOMAIN
-
- 7 SEQ #3
- DATE APPLIED: 2006-04-10 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
When printing a mapping report in Map Pharmacy Locations [PSU MAP PHARMACY
LOCATIONS] option, an undefined error occurs.
-
- 6 SEQ #4
- DATE APPLIED: 2006-05-04 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch corrects the AR/WS AMIS Summary report for the Pharmacy
Benefits Management (PBM) Version 4.0 extract in cases where there is no
AR/WS data available for the date range of an AR/WS extract.
This patch also corrects the Prescription Extract MailMan messages
containing mismatched data elements for partial fill prescriptions.
-
- 8 SEQ #5
- DATE APPLIED: 2006-08-24 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
Issue #1: The Provider Summary report is reporting missing data. When a
Pharmacy Benefits Management package.
Provider has a Service/Section, the Provider will incorrectly show up on
the report as missing specific data.
Issue #2: When running Manual Pharmacy Statistics [PSU PBM MANUAL]
option, the clinic that appears in a mailman message is not
the same clinic that appears in the PRESCRIPTION file (#52).
Issue #3: This patch will clean up routines no longer being used in the
-
- 10 SEQ #6
- DATE APPLIED: 2006-12-27 14:39:18
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch will address the ALLERGIC/ADVERS REACTIONS report.
Issue #1 (REMEDY HD167841):
The PBM Allergic/Advers Reactions report has missing and incorrect data
being reported.
-
- 9 SEQ #7
- DATE APPLIED: 2007-09-04 22:39:21
- APPLIED BY: USER,ONE
- DESCRIPTION:
PBM FIXES: MAPPED LOCATIONS/PHARM IEN/AMIS REPORT HEADER
-
- 11 SEQ #8
- DATE APPLIED: 2008-02-03 21:41:44
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch will address the subscript error that occurs on mircbiology
records for verified chemistry lab results on the PBM/HL7 interface.
-
- 12 SEQ #9
- DATE APPLIED: 2008-02-03 22:35:51
- APPLIED BY: USER,ONE
- DESCRIPTION:
PBM Pharmacy Statistics Report
- DATE INSTALLED AT THIS SITE: 2005-04-01 00:00:00
- INSTALLED BY: USER,ONE
- DESCRIPTION OF ENHANCEMENTS:
The PBM V. 4.0 application contains enhancements to support the VA
extracts, and existing PBM options. New summary reports have been
created for Automated Management Information System (AMIS) reporting. New
options have also been created to support the added functionality.
National Formulary (VANF), disease management issues and patient safety
initiatives.
Two new extracts have been created to gather patient vital/immunization
and allergy/adverse reaction data. Modifications have also been
made to existing Prescription, Unit Dose, Intravenous (IV),
Controlled Substance (CS), Automatic Replenishment/Ward Stock (AR/WS),
Procurement, Patient Demographic, Outpatient Visits, Laboratory
-
- 2.0
- DATE DISTRIBUTED: 1995-08-11 00:00:00
- PATCH APPLICATION HISTORY:
-
-
- 3
- DATE APPLIED: 1996-10-18 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
The National D&PPM Section has gotten their own domain name to reduce
the amount of traffic coming into the Hines VAMC. Therefore the address
name needs to be changed.
-
- 2
- DATE APPLIED: 1997-02-17 00:00:00
- APPLIED BY: USER,ONE
- DESCRIPTION:
This patch addresses NOISs CHA-0296-31865 and NYN-1295-11103. It was
reported that when the D&PPM software is collecting the Outpatient
Pharmacy data, an endless loop can occur when collecting data from
partials. The problem was an incorrect $Select statement which repeatedly
looped on the first node.
- DATE INSTALLED AT THIS SITE: 1996-08-19 00:00:00
- DESCRIPTION OF ENHANCEMENTS:
For the Outpatient & IV statistics, the number of Social Security numbers
a confirmation MailMan message will be generated at the facility
providing information about the number of drugs extracted for
each package.
for each drug is extracted.
Consolidated Mail Out Pharmacy (CMOP) data is extracted from Host CMOP
facilities.
Procurement and Controlled Substances data is now extracted.
After the monthly D&PPM report is sent to the D&PPM Section,
|
