PSO*7.0*117 (4930)    BUILD (9.6)

Name Value
NAME PSO*7.0*117
DATE DISTRIBUTED 2003-06-24 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*88
    ACTION:   Don't install, leave global
  • PSO*7.0*115
    ACTION:   Don't install, leave global
  • PSO*7.0*124
    ACTION:   Don't install, leave global
  • PSS*1.0*47
    ACTION:   Don't install, leave global
  • PSO*7.0*130
    ACTION:   Don't install, leave global
  • PSO*7.0*92
    ACTION:   Don't install, leave global
  • PSO*7.0*104
    ACTION:   Don't install, leave global
  • PSO*7.0*114
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
1. This patch provides new functionality that allows the Veteran Affairs 
2. This patch also addresses the following NOIS issues: 
 
a) ISB-0702-32646 
 
For drugs that have possible dosages, if the dosage is edited using Patient
Prescription Processing [PSO LM BACKDOOR ORDERS] option, the software
calculates the new DISPENSE UNITS PER DOSE field (#1) of the MEDICATION
INSTRUCTIONS sub-file (#113) of the PRESCRIPTION file (#52), accordingly. At
the confirmation prompt that follows immediately if you respond "NO",
meaning not to accept the new value, the software does not revert the
Medical Centers to print a patient's prescription bottle label in another 
DISPENSE UNITS PER DOSE field (#1) back to it's original value. This patch
fixes this issue.  
 
b) CAH-0402-31866 
 
When entering a new prescription using the Patient Prescription Processing
[PSO LM BACKDOOR ORDERS] option, if that prescription is discontinued before
it goes to the label queue prompt, currently, the label "LABEL QUEUE/CHANGE
PRINTER/SUSPEND or '^' to bypass Q//" is prompted. If this is the only order
in that session then there is no label to print and therefore the label queue
language.  This functionality is accomplished by identifying which patients
prompt should not be displayed. This patch fixes this problem.  
 
c) ISH-0902-40182 
 
Between the time an order was placed in Computerized Patient Record System
(CPRS) V.1.0 and the time the order is processed in the backdoor pharmacy,
if the dispense drug is made inactive, then there is a possibility of
getting an undefined error if a "?" is entered when editing the dosage
prompt . Since the drug is inactive the software does not gather the
available dosages and as a result the undefined error. In order to process
have another language preference. To identify patients as having another
such an order (avoiding the undefined error), this patch will provide the
user the option of making a free text dosage entry.  
 
d) LIT-1102-71356 
 
When a site merges two patients together, the PHARMACY PATIENT file (#55)
contains all of the prescriptions from the "merged from" patient and the
"merged to" patient under the internal entry number of the "merged to"
patient. The old patient's internal entry number is kept in the PRESCRIPTION
file (#52) for any prescriptions that were originally filed with that
language preference use the Update Patient Record [PSO PAT] option and the
number. If a new prescription is ordered for a drug that is already in the
prescription profile, the order entry process will discontinue the old
prescription correctly.  The problem is that if the discontinued order
belongs to the old patient internal entry number, the new prescription order
is filed with the old patient's internal entry number in the PHARMACY
PATIENT file (#55) and the PRESCRIPTION file (#52) and doesn't appear on the
prescription profile. This patch corrects this problem.  
 
3. A more descriptive message will now be given to the user when an order is
accessed, and that order is locked by another user, when copying a 
Patient Record Update [PSO PATIENT RECORD UPDATE] protocol action and enter
prescription, selecting a pending order, discontinuing a prescription, and
processing a non-verified prescription.  
 
4. If pre-POE prescriptions are renewed or edited to create a new prescription,
the resulting prescription may have a missing SIG. This patch corrects the
problem.  
Yes in the new field OTHER LANGUAGE PREFERENCE field (#106) in the PHARMACY
PATIENT file (#55).  
 
TRACK PACKAGE NATIONALLY YES
FILE
  • DD NUMBER:
    • PRESCRIPTION (File-top level)
      FIELD NUMBER:
      • OTHER PATIENT INSTRUCTIONS
    • MEDICATION INSTRUCTIONS (sub-file)
      FIELD NUMBER:
      • OTHER LANGUAGE DOSAGE
    UPDATE THE DATA DICTIONARY:   YES
    SEND SECURITY CODE:   NO
    SEND FULL OR PARTIAL DD:   PARTIAL
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
BUILD COMPONENTS
  • ENTRIES:
    • PSOHLNEW
      ACTION:   SEND TO SITE
      CHECKSUM:   B70331758
    • PSON52
      ACTION:   SEND TO SITE
      CHECKSUM:   B52741182
    • PSORN52C
      ACTION:   SEND TO SITE
      CHECKSUM:   B47722106
    • PSOVER
      ACTION:   SEND TO SITE
      CHECKSUM:   B60175221
    • PSOCAN
      ACTION:   SEND TO SITE
      CHECKSUM:   B45767199
    • PSOCAN3
      ACTION:   SEND TO SITE
      CHECKSUM:   B63454426
    • PSOCAN4
      ACTION:   SEND TO SITE
      CHECKSUM:   B38999970
    • PSOORFIN
      ACTION:   SEND TO SITE
      CHECKSUM:   B65314545
    • PSORXDL
      ACTION:   SEND TO SITE
      CHECKSUM:   B56632798
    • PSOHLNE1
      ACTION:   SEND TO SITE
      CHECKSUM:   B59948882
    • PSOBKDED
      ACTION:   SEND TO SITE
      CHECKSUM:   B79359023
    • PSODIR
      ACTION:   SEND TO SITE
      CHECKSUM:   B27023092
    • PSOHELP
      ACTION:   SEND TO SITE
      CHECKSUM:   B48369441
    • PSOLBL2
      ACTION:   SEND TO SITE
      CHECKSUM:   B32653360
    • PSOLBL3
      ACTION:   SEND TO SITE
      CHECKSUM:   B10009062
    • PSOLMPAT
      ACTION:   SEND TO SITE
      CHECKSUM:   B2550692
    • PSONEW1
      ACTION:   SEND TO SITE
      CHECKSUM:   B13754015
    • PSOORCPY
      ACTION:   SEND TO SITE
      CHECKSUM:   B20977026
    • PSOORED1
      ACTION:   SEND TO SITE
      CHECKSUM:   B64105389
    • PSOORNE1
      ACTION:   SEND TO SITE
      CHECKSUM:   B67612798
    • PSOORNE5
      ACTION:   SEND TO SITE
      CHECKSUM:   B56977031
    • PSOORNW2
      ACTION:   SEND TO SITE
      CHECKSUM:   B39760381
    • PSOPAT
      ACTION:   SEND TO SITE
      CHECKSUM:   B4127186
    • PSORN52
      ACTION:   SEND TO SITE
      CHECKSUM:   B68818963
    • PSORX1
      ACTION:   SEND TO SITE
      CHECKSUM:   B36158267
    • PSORXVW
      ACTION:   SEND TO SITE
      CHECKSUM:   B61701109
    • PSOSPSIG
      ACTION:   SEND TO SITE
      CHECKSUM:   B63360791
    • PSOORNW1
      ACTION:   SEND TO SITE
      CHECKSUM:   B34015570
    • PSOBKDE1
      ACTION:   SEND TO SITE
      CHECKSUM:   B5760790
    • PSOORED3
      ACTION:   SEND TO SITE
      CHECKSUM:   B77631599
    • PSOORED2
      ACTION:   SEND TO SITE
      CHECKSUM:   B70666932
    • PSOORED5
      ACTION:   SEND TO SITE
      CHECKSUM:   B75039683
    • PSOORED4
      ACTION:   SEND TO SITE
      CHECKSUM:   B66575262
    • PSOORED6
      ACTION:   SEND TO SITE
      CHECKSUM:   B48640163
    • PSORENW1
      ACTION:   SEND TO SITE
      CHECKSUM:   B45620014
    • PSOORFI4
      ACTION:   SEND TO SITE
      CHECKSUM:   B55767803
    • PSORXVW2
      ACTION:   SEND TO SITE
      CHECKSUM:   B37914582
    • PSORXVW1
      ACTION:   SEND TO SITE
      CHECKSUM:   B54681066
    • PSOLBLN
      ACTION:   SEND TO SITE
      CHECKSUM:   B30185965
    • PSOLBLD
      ACTION:   SEND TO SITE
      CHECKSUM:   B27529765
    • PSOLBLD1
      ACTION:   SEND TO SITE
      CHECKSUM:   B9017238
    • PSORENW3
      ACTION:   SEND TO SITE
      CHECKSUM:   B40461998
    • PSORENW4
      ACTION:   SEND TO SITE
      CHECKSUM:   B52540927
    • PSOORFI3
      ACTION:   SEND TO SITE
      CHECKSUM:   B76769270
    • PSOORNE4
      ACTION:   SEND TO SITE
      CHECKSUM:   B66891316
    • PSOORNE6
      ACTION:   SEND TO SITE
      CHECKSUM:   B43831176
    • PSOORNE2
      ACTION:   SEND TO SITE
      CHECKSUM:   B64833577