PSO*7.0*139 (5126)    BUILD (9.6)

Name Value
NAME PSO*7.0*139
DATE DISTRIBUTED 2003-09-13 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*112
    ACTION:   Don't install, leave global
  • PSO*7.0*146
    ACTION:   Don't install, leave global
  • PSO*7.0*73
    ACTION:   Don't install, leave global
  • PSO*7.0*70
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
 
   exist.
 
       NTE|3|
        :
 
7. WIM-0603-20338
   The Print from Suspense File [PSO PNDLBL] option allows an user
   to queue the printing of the labels at a later time by Taskman. A
   problem was found when the original task was re-queued through the
   Taskman Requeue Tasks [XUTM REQ] option by a different user. Once
   the labels printed, the label print activity log for the prescription
 
   was recorded as being performed by the second user, the one who
   re-queued the Taskman task, which is wrong. This patch makes the
   correction to keep the user who queued the label print through the
   Print from Suspense File [PSO PNDLBL] option in the label print
   activity log.
 
8. MAC-0603-60315
   Patch PSO*7*124 introduced the following change:
 
         Currently, if a non-controlled substance prescription is entered
 
         with a day supply less than 5 days and there are no refills, the
         expiration date defaults to 5 days from the issue date. If a
         controlled substance prescription is entered with a day supply
         less than 5 days without refills, the expiration date is the
         Issue Date plus the Days Supply. The primary problem is that
         when these prescriptions were being transmitted to the CMOPs and
         they were behind on dispensing, the prescriptions were being
         rejected because the prescriptions had already expired. The
         default of 5 is being changed to 30 to accommodate the CMOPs and
         to allow the patients to receive their medications in a timely
2. CLA-0303-20198
         manner. Prescriptions will no longer expire before 30 days
         elapses from the Issue Date when the day supply is less than 30
         days and there are no refills.  If a minimum of 1 refill is
         entered the one year/six month rule still applies.
 
   This created a problem for some sites with a rehab unit where some
   patients go out on Authorized Absence every weekend. The site then
   enters a prescription with a patient status of AUTHORIZED ABSENCE and
   no refills and a small number for days supply (3 or 4 days). Before,
   such prescriptions expired within 5 days from the issue date and no
   The Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] option was
   longer showed on the Medication Profile screen. Now, after PSO*7*124
   was installed, such prescriptions remain active for at least 30 days.
   The result is that multiple prescriptions for a single drug are listed
   in the Medication Profile screen. Active prescriptions with a patient
   status of AUTHORIZED ABSENCE can contain the same drug already in
   another active prescription for the same patient.
   Once this patch is installed, prescriptions with a patient status of
   AUTHORIZED ABSENCE and no refills will have the expiration date
   calculation reversed to a minimum of 5 days from the issue date,
   instead of the 30 days introduced by patch PSO*7*124.
   initially provided to synchronize the expired order status between
 
9. PUG-0603-50491
   This NOIS call reported a problem with the patient security check for
   the Complete Orders from OERR [PSO LMOE FINISH] option. An example of
   a patient security check is when an employee tries to get access to
   his own medical record and is denied. In the case of the menu option
   mentioned above, such security checks were not being performed when
   the user selected to process ALL the patients with pending orders.
   Also, when processing by clinic, route or priority, there were no
   security checks performed. The only time the security checks were
   Outpatient Pharmacy prescriptions and Computerized Patient Record
   performed was when the user selected to process a single patient.
   When this patch is installed, this problem will be resolved and the
   Complete Orders from OERR [PSO LMOE FINISH] option will perform the
   security checks consistently for all the possible selections when
   finishing pending orders.
 
10. CON-0703-11685, MAR-0703-21567 & SBY-0703-31538
    When trying to reinstate discontinued prescriptions for a patient that
    had the DATE OF DEATH field (#.351) in the PATIENT file (#2) entered
    and then deleted, the user was getting an "Undefined variable DA"
   System (CPRS) V. 1.0 order entries. And as such, the start date was set
    error. This problem was introduced by patch PSO*7*117, more
    specifically by the changes described in item #2b which was made to
    address NOIS call CAH-0402-31866. This patch corrects the problem
    with the use of that variable.
 
11. MIN-1202-40079, FRE-0303-60233 & RIC-0603-21344
    In some situations where a patient is being accessed by Inpatient
    Pharmacy Version 5.0, if an attempt is made to finish orders in
    Outpatient Pharmacy Version 7.0, a message is received that the
    patient is in use. Then if an "^" is entered for the PATIENT STATUS
   to the date Outpatient Pharmacy Version 7.0 was installed minus 120
    prompt, the cross-reference entries in the PHARMACY PATIENT file (#55)
    could be deleted for that patient. This patch corrects the problem.  A
    follow-up patch will provide a clean up to rebuild missing
    cross-references.
 
12. HUN-0603-21419 & WPB-0803-30273
    There has been some instances where a prescription from one patient
    was being displayed on the Bingo Board for a different patient. This
    patch kills a variable that could accidentally get carried over    
    between patients.
   days. A few sites have reported that some of the very old
1. BIR-0203-30502
   prescriptions, specifically those that are 120 days prior to the date
   Outpatient Pharmacy Version 7.0 was installed, show an active status
   when viewed via FileMan. In order to scan the PRESCRIPTION file (#52)
   and flag such orders as expired, this option has been modified to
   provide the user the flexibility to select a start date and the default
   is set to the date Outpatient Pharmacy Version 7.0 was installed minus
   120 days.
 
3. CLE-0303-42391
   This NOIS call reported that the PROVIDER COMMENTS field (#39) of the
   This NOIS call reported the following software error that happened
   PRESCRIPTION file (#52) was being lost when a prescription was renewed
   from Outpatient Pharmacy. A correction was made to send the comments to
   CPRS when the prescription is renewed from Outpatient Pharmacy.
 
4. ISB-0403-31630
   This NOIS call reported a problem in the display of Allergy severity
   in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
   option, on the Detailed Allergy Display screen. The content of the
   field "Severity:" was limited to one, and only one, value. The possible
   values were: MILD, MODERATE or SEVERE. The first Severity on file was
   with a FastFill machine:
   displayed. Since it is possible to have more than one Severity per
   Allergy, this display was changed to show all the Severities on file,
   along with the dates on which each one was observed. See example below:
 
        Before:     Severity: MODERATE
 
        Now:        Severity: 04/07/03 MODERATE
                              04/15/03 MILD
                              04/17/03 SEVERE
 
 
   Besides the changes to this display, the HL7 message for External
   Interfaces was also changed. The ZAL segment will have one for each
   severity observed. Before, it would have only one entry for the
   oldest severity observed. Furthermore, the date the severity was
   observed is being added as field #8 of this segment. From the same
   example from above, here is how the ZAL segment will look:
 
     Before:
      ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MODERATE
 
   $ZE= ACK+2^PSOHLSG:1, %DSM-E-UNDEF, undefined variable HL("APAT"),
     Now:
      ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MODERATE|20030407|
      ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MILD|20030415|
      ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|SEVERE|20030417|
 
5. ANN-0902-40951
   An undefined error was reported when using the Patient Prescription
   Processing [PSO LM BACKDOOR ORDERS] option. If the drug of an active
   order is edited, but the user quits without saving the changes and a
   new order for the same drug is placed immediately afterwards, the error
        -DSM-I-ECODE, MUMPS error code: M6
   could occur. This patch fixes this issue.
 
6. LAS-0503-60830 & BRX-0603-11755
   The "NTE|2|" segment in the HL7 message generated for external
   interfaces is composed by the concatenation of the following Freetext
   fields from the OUTPATIENT SITE file (#59) in this order:
 
       Field #   Name
       ------------------------------------------
       1005      NARRATIVE FOR REFILLABLE RX
 
       1006      NARRATIVE FOR NON-REFILLABLE RX
       1004      NARRATIVE FOR COPAY DOCUMENT
 
   When building this segment, the routine PSOHLSG2 was skipping one line
   between the content of each field. This line is being interpreted by
   some external interfaces, such as Optifill, as the end of the "NTE|2|"
   segment, because all it contains is a carriage return character. This
   caused the external interface to reject messages with only a carriage
   return in the line. To solve this problem a blank space will be
   inserted between the content of each field. In the example below, the
   The routine was corrected to reinitialize the variable if it does not
   blank space will be added where the arrow ("->") is pointing.
 
        :
       NTE|2|
       Call in your refill on your touch-tone phone.
       Outside the metropolitan area: 1-800-123-4567.
     ->
       The copay required is $7.00 for every 30 day or less supply of
       medication or $21.00 for a 90-day supply. Be sure to indicate your
       complete SSN on your check.
TRACK PACKAGE NATIONALLY YES
BUILD COMPONENTS
  • ENTRIES:
    • PSO MANUAL AUTO EXPIRE
      ACTION:   ATTACH TO MENU
    • PSO MAINTENANCE
      ACTION:   USE AS LINK FOR MENU/ITEM/SUBSCRIBERS
  • ENTRIES:
    • PSOMAUEX
      ACTION:   SEND TO SITE
      CHECKSUM:   B20634322
    • PSOORNE3
      ACTION:   SEND TO SITE
      CHECKSUM:   B65570103
    • PSOSULBL
      ACTION:   SEND TO SITE
      CHECKSUM:   B29094297
    • PSOSUTL
      ACTION:   SEND TO SITE
      CHECKSUM:   B56530343
    • PSON52
      ACTION:   SEND TO SITE
      CHECKSUM:   B54932017
    • PSOORFIN
      ACTION:   SEND TO SITE
      CHECKSUM:   B69450551
    • PSOORFI3
      ACTION:   SEND TO SITE
      CHECKSUM:   B74230538
    • PSODPT
      ACTION:   SEND TO SITE
      CHECKSUM:   B2383499
    • PSOCAN3
      ACTION:   SEND TO SITE
      CHECKSUM:   B70668962
    • PSOHLSN1
      ACTION:   SEND TO SITE
      CHECKSUM:   B80417617
    • PSORX1
      ACTION:   SEND TO SITE
      CHECKSUM:   B37212288
    • PSOHLSG
      ACTION:   SEND TO SITE
      CHECKSUM:   B30890253
    • PSOHLSG1
      ACTION:   SEND TO SITE
      CHECKSUM:   B61005791
    • PSOHLSG2
      ACTION:   SEND TO SITE
      CHECKSUM:   B45812306
    • PSODRG
      ACTION:   SEND TO SITE
      CHECKSUM:   B24089194
    • PSOORDA
      ACTION:   SEND TO SITE
      CHECKSUM:   B53990786
    • PSODIR2
      ACTION:   SEND TO SITE
      CHECKSUM:   B26172135
    • PSONEW2
      ACTION:   SEND TO SITE
      CHECKSUM:   B27542190