PSO*7.0*99 (4339)    BUILD (9.6)

Name Value
NAME PSO*7.0*99
DATE DISTRIBUTED 2002-07-12 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*100
    ACTION:   Don't install, leave global
  • PSO*7.0*101
    ACTION:   Don't install, leave global
  • PSO*7.0*103
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
1. When finishing a pending order entered through Computerized Patient
with the order contains a 2, 3, 4, or 5. This patch makes this change. A
message has also been added that will be displayed during the finish
process only when the quantity is automatically updated by the software,
due to edits of any of these fields.
 
2. There are occurrences throughout the Outpatient Pharmacy package where 
Possible Dosages and Dispense Units per Dose are displayed, and if that 
numeric data begins with a decimal point, such as ".5," then that is how
it is displayed, as ".5". This patch will make change to add a leading
zero to these displays, so ".5" will now be displayed as "0.5". This
Record System (CPRS), and fields are edited during the finish process that
change will not apply to Local Possible Dosages. It will only apply to
Possible Dosages and Dispense Units per Dose.
 
3. When prescriptions are entered that contain Possible Dosages, the Noun 
that is applied to the Dosing Instruction comes from the DOSAGE FORM file 
(#50.606). If that Noun ends in "(S)" or "(s)", such as TABLET(S) or 
CAPSULE(S), the software will adjust the Noun based on the Dispense Units 
per Dose. For example, if the Noun is TABLET(S), then the software will 
change the Noun to TABLET if the Dispense Units per Dose is one or 
less, and the software will change the Noun to TABLETS if the Dispense 
are used in the automatic Quantity calculation such as Days Supply or
Units per Dose is greater than one. When prescriptions and pending orders 
are edited, this conversion of the Noun does not always take place. This 
patch makes the change to convert the Noun to it's proper form when edits 
are made.
 
4. When finishing a pending order using either the Patient Prescription 
Processing [PSO LM BACKDOOR ORDERS] option, or the Complete Orders from
OERR [PSO LMOE FINISH] option, an undefined error could occur if the
ListMan action "EA Enter/Edit Allergy/ADR Data" is selected to add or edit
allergy information. This patch fixes this problem.
Schedule, a recalculation is done on the Quantity of the prescription,
 
5. There is an order check for drugs with data entered in the MAXIMUM DOSE
PER DAY field (#4) of the DRUG file (#50), that divides Quantity by Days
Supply, and if that's greater than the MAXIMUM DOSE PER DAY, an order
check is given. A problem occurred when this order check was given when
finishing an order entered through Computerized Patient Record System
(CPRS). If an '^' is entered at the 'Do You Want to Edit Days Supply and
Quantity Fields?' prompt, the user will exit the process, but the
subsequent prompts for that order are still given, even though the order
will not be finished because of the '^' that was entered. This patch will
whether the edits created a new order or not. A request has been made to
suppress those remaining prompts after the '^' is entered.
 
6. When an active prescription is copied using the CO Copy (OP) hidden
action in Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,
and if the CONJUNCTION field (#5) of the MEDICATION INSTRUCTIONS sub-file
(#52.0113) of the PRESCRIPTION file (#52) is deleted using the @ key, then
the software does not trigger the duplicate drug check and as a result
duplicate active prescriptions are created. Also it was observed that
deleting this field by using the @ key during the process of
creating/editing a prescription, the software prompts the question
not recalculate the Quantity based on these edits when finishing a pending
"Deleting this conjunction will delete the dosing sequence that follows!",
even when no conjunctions are defined. In such a situation this patch will
display a message "Invalid Entry - nothing to delete" and will loop back
to the CONJUNCTION field (#5) of the MEDICATION INSTRUCTIONS sub-file 
(#52.0113) of the PRESCRIPTION file (#52) prompt.
order from CPRS if any of the Schedules associated with the order contain
PRN, or if the drug is a Schedule 2, 3, 4, or 5, meaning the DEA,
SPECIAL HDLG field (#3) of the DRUG file (#50) for the drug associated
TRACK PACKAGE NATIONALLY YES
BUILD COMPONENTS
  • ENTRIES:
    • PSOSIG
      ACTION:   SEND TO SITE
      CHECKSUM:   B63476674
    • PSOLMUTL
      ACTION:   SEND TO SITE
      CHECKSUM:   B8918529
    • PSOORNE4
      ACTION:   SEND TO SITE
      CHECKSUM:   B70918843
    • PSOHLSN1
      ACTION:   SEND TO SITE
      CHECKSUM:   B76800851
    • PSORXVW1
      ACTION:   SEND TO SITE
      CHECKSUM:   B68881085
    • PSOORNE5
      ACTION:   SEND TO SITE
      CHECKSUM:   B70035409
    • PSOORFI3
      ACTION:   SEND TO SITE
      CHECKSUM:   B71267250
    • PSOORFI4
      ACTION:   SEND TO SITE
      CHECKSUM:   B69081130
    • PSOBKDED
      ACTION:   SEND TO SITE
      CHECKSUM:   B72942995
    • PSOORED5
      ACTION:   SEND TO SITE
      CHECKSUM:   B81044357
    • PSOORED3
      ACTION:   SEND TO SITE
      CHECKSUM:   B75951189
    • PSOORED4
      ACTION:   SEND TO SITE
      CHECKSUM:   B80015418