PSO*7.0*662 (12978)    BUILD (9.6)

Name Value
NAME PSO*7.0*662
DATE DISTRIBUTED 2022-05-11 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*659
    ACTION:   Don't install, remove global
  • PSO*7.0*630
    ACTION:   Don't install, remove global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
It was reported that the Meds by Mail logic added to the State 
2. INC19848615 - View/Export Single Prescription [PSO SPMP SINGLE RX
option to display the appropriate state.
 
Technical Resolution:
---------------------
Routine PSOSPML4 in the EN tag, change the STATEIEN variable lookup so the
appropriate state displays.
 
4. INC21661107 - the View/Export Void Prescriptions [PSO SPMP VOID RX
VIEW/EXPORT] option only transmits to the dispensing pharmacy's state.
 
VIEW/EXPORT] option only sends to state of dispensing pharmacy
Problem:
--------
The View/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT]
option only transmits to the dispensing pharmacy's state.
 
Resolution:
-----------
Fix the logic for the View/Export Void Prescriptions [PSO SPMP VOID RX
VIEW/EXPORT] option to look at the dispensing pharmacy state and the
patient state, and then look at the SEND EXPORT STATE PARAMETER (#21) 
 
field in the SPMP STATE PARAMETERS (#58.41) file to determine what 
state(s) the batch needs to be sent.
 
Technical Resolution:
---------------------
Routine PSOSPMV in the RXLOOP tag, change the logic to look at the
dispensing pharmacy state and the patient address state, and then look at 
the SEND EXPORT STATE PARAMETER (#21) field in the SPMP STATE PARAMETERS
(#58.41) file to determine what state(s) the batch needs to be sent.
3. INC19851935 - Export Batch Processing [PSO SPMP BATCH PROCESSING] 
option only displays ASAP version of the dispensing state
 
4. INC21661107 - Manual Voids sent to state of dispensing pharmacy, not 
patient's home state
 
 
Prescription Monitoring Program (SPMP) patch, PSO*7.0*630, was not working
Patient Safety Issues (PSIs):
-----------------------------
N/A
 
 
Defect Tracking System Ticket(s) & Overview: 
 
1. INC19848427 - the Scheduled SPMP Data Export [PSO SPMP SCHEDULED
EXPORT] option and CS Prescriptions Not Transmitted [PSO SPMP RX
NOT TRANSMITTED] option are both gathering prescriptions for incorrect
correctly for some of the SPMP options. This patch will resolve the
states.
 
Problem:
--------
A single prescription can incorrectly be sent to multiple states.  This 
happens if the state being transmitted has a state IEN which is a single 
digit, and the patient's home state has a state IEN that contains that 
transmitting state's IEN.  This will affect both the transmission for the 
previous day (including return to stock) and the 30 day look back.
 
following SPMP issues:
Resolution:
-----------
Fix the logic for the Scheduled SPMP Data Export [PSO SPMP SCHEDULED
EXPORT] option and CS Prescriptions Not Transmitted [PSO SPMP RX NOT
TRANSMITTED] option to look at the dispensing pharmacy state and the
patient state, and then look at the SEND EXPORT STATE PARAMETER (#21) 
field in the SPMP STATE PARAMETERS (#58.41) file to determine what
state(s) the batch needs to be sent.
 
Technical Resolution:
 
---------------------
Routine PSOSPMU1 in the GATHER tag, change the contains from "'[STATE" to
"'[("^"_STATE_"^")" when checking for the STATE variable. This will fix
the issue with the prescriptions being sent to incorrect states.
 
2. INC19848615 - the View/Export Single Prescription [PSO SPMP SINGLE RX
VIEW/EXPORT] option only transmits to the dispensing pharmacy's state.
 
Problem:
--------
1. INC19848427 - The same RX fills are being transmitted in multiple 
Patch PSO*7.0*630 added functionality to allow Meds By Mail to transmit 
control substance prescriptions to the SPMP state of the patient's 
geographic state.  However, when using View/Export Single Prescription 
[PSO SPMP SINGLE RX VIEW/EXPORT] option
to send a single RX, it will only send to the state of the dispensing 
pharmacy and cannot be changed to transmit to the patient's geographical 
state.
 
Resolution:
-----------
batches and also to states not associated with the patient or dispensing 
Fix the logic for the View/Export Single Prescription [PSO SPMP SINGLE RX
VIEW/EXPORT] option to look at the dispensing pharmacy state and the
patient state, and then look at the SEND EXPORT STATE PARAMETER (#21) 
field in the SPMP STATE PARAMETERS (#58.41) file to determine what
state(s) the batch needs to be sent.
 
Technical Resolution:
---------------------
Routine PSOSPML4 in the EXPORT tag, look at the dispensing pharmacy state
and the patient state, and then look at the SEND EXPORT STATE PARAMETER 
pharmacy
(#21) field in the SPMP STATE PARAMETERS (#58.41) file to determine what
state(s) the batch needs to be sent.
 
3. INC19851935 - the Export Batch Processing [PSO SPMP BATCH PROCESSING] 
option reverts to dispensing pharmacy's state.
 
Problem:
--------
Patch PSO*7.0*630 added functionality to allow Meds By Mail to transmit 
control substance prescriptions to the SPMP state of the patient's 
 
geographic state.  However, when using Export Batch Processing [PSO SPMP 
BATCH PROCESSING] option to view transmissions for states other than the 
dispensing pharmacy's state, then the prescription details will display 
the ASAP version for the dispensing pharmacy's state.  As the user backs 
out of the option, the state changes away from what the state the user 
initially picked and instead changes to the dispensing pharmacy's state.
 
Resolution:
-----------
Fix the logic for the Export Batch Processing [PSO SPMP BATCH PROCESSING]
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 564
BUILD COMPONENTS
  • ENTRIES:
    • PSOSPMU1
      ACTION:   SEND TO SITE
      CHECKSUM:   B142616954
    • PSOSPML4
      ACTION:   SEND TO SITE
      CHECKSUM:   B109923547
    • PSOSPMV
      ACTION:   SEND TO SITE
      CHECKSUM:   B40484462