PSX*2.0*94 (12532)    BUILD (9.6)

Name Value
NAME PSX*2.0*94
DATE DISTRIBUTED 2021-08-05 00:00:00
PACKAGE FILE LINK CMOP
REQUIRED BUILD
  • PSX*2.0*58
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
This patch will resolve the following issue:
--------
The Castle Point VA Medical Center reported that its PSX Resource device was
hung for hours in and they had to manually released and the process that was
holding the device had to be terminated. The Clin1 researched the problem
and determined that the sequence that caused the problem was this:
    
   1. The CMOP prescription release information arrives at the site in the
      form of a Mailman message that contains all prescriptions released by
      CMOP. This message is sent to the S.PSXX CMOP SERVER recipient.
 
  
   2. Each line of the Mailman message is processed to reflect the release
      event (e.g., Release date and CMOP information like Lot# is recorded,
      3rd party billing is updated, etc.)
 
   3. An existing 3rd party billing claim will be reversed and resubmitted if
      the NDC from CMOP does not match the original sent to the 3rd party
      payer when the prescription was transmitted to CMOP. 
 
   4. Some of these updates will cause ePharmacy (BPS) to call out to the
      Integrated Billing (IB) application to cancel a Bill.
1) INC18186175 - NFL Stuck PSX resource
 
   5. Depending on the update that the IB application performs it may
      automatically create and send a Mailman message to its users.
 
   6. The creation of the Mailman message by IB is interfering with the
      processing of the Mailman message sent from CMOP to the site. More 
      specifically, it changes the value of the variable XMZ that is used as
      an index in the step #2 above to indicate which line is being processed.
   
   7. This caused the processing of the CMOP message to go into an infinite
   
      loop and cause the problem reported by the site. 
 
Resolution:
----------
A change was made to the processing of the CMOP Mailman message to protect
the variable XMZ from being overwritten when other functionalities or
applications are called.
   
Technical Resolution:
--------------------
Defect Tracking System Ticket(s) & Overview:
The FOR loop in the EN+3 line of the PSXVND routine was re-written to address
two problems:
  
   1. Protect the variable XMZ from being overwritten 
 
   2. Removed GOTO commands from inside the FOR loop and placed them outside
      without changing the original logic
--------------------------------------------
1) INC18186175 - NFL Stuck PSX resource
 
Problem: 
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 78
BUILD COMPONENTS
  • ENTRIES:
    • PSXVND
      ACTION:   SEND TO SITE
      CHECKSUM:   B41060377