PSO*7.0*496 (10799)    BUILD (9.6)

Name Value
NAME PSO*7.0*496
DATE DISTRIBUTED 2018-01-26 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*444
    ACTION:   Don't install, leave global
  • PSO*7.0*427
    ACTION:   Don't install, leave global
  • PSO*7.0*451
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
This patch will resolve the following issues.
 
Information Processing Standard (FIPS) code for Canada is "CA", however the
SPMP standard requires "CN" for Canada. 
  
Resolution:
-----------
Changed the retrieval of the patient's state and postal code fields to
first check for the country. For foreign countries (non-US) it will
retrieve the Province and Postal Codes values returned in the VAPA(23)
and VAPA(24) return array from the ADD^VADPT API. Also changed it to send
"CN" for PAT22 (Country of Non-US Resident) for Canada.
Associated NSR(s)
   
Technical Resolution:
---------------------
Modified the routines PSOASAP and PSOASAP0 to check whether the country is
non-US (foreign). If so, it will use the value in VAPA(24) and VAPA(23) for
the fields PAT15 and PAT16 respectively. Also, changed the line tag PAT22 
on the PSOASAP0 routine to return "CN" instead of "CA" for Canada.
=================
 N/A 
 
Test Sites:
==========
 
Associated CA SDM Ticket(s):
============================
 
1. I10127879FY16 - It is possible to suspend a script past the expiration
                   date. 
2. I16514233FY17 - Vista transmits two instances of the same prescription
                   to the external interface. 
   R14795402FY17(d) - Vista is sending over prescription data twice for 
                      SOME prescriptions, resulting in duplicates showing
                      up in ScriptPro
3. I11517650FY17 - Need assistance with SPMP Patient Address errors 
 
  
1. It is possible to suspend a script past the expiration date.
Defect Tracking System Ticket(s) & Overview:
============================================
1. I10127879FY16 - It is possible to suspend a script past the expiration
                   date.  
Problem:
--------
Currently in Outpatient Pharmacy the users are able to enter a REFILL DATE 
that is past the Rx EXPIRATION DATE. The software should not allow a refill
date that is past the expiration date because it is an invalid date and the
prescription will be expired before it can be dispensed.
 
 
Resolution:
-----------
The Data Dictionary for the PRESCRIPTION file (#52) was modified to include 
restrictions on the following fields: FILL DATE (#22) and REFILL DATE (#.01)
in the REFILL sub-file (#52.1). The restrictions will require that the value
entered for either one of these two fields cannot be before the Rx ISSUE
DATE or after the Rx EXPIRATION DATE.
 
Technical Resolution:
2. Vista transmits two instances of the same prescription to the external
---------------------
Created new INPUT TRANSFORM code (FLDTINTR^PSOUTLA(Fill_Type)) and new 
EXECUTABLE HELP code (FLDTHELP^PSOUTLA(Fill_Type)) and modified the fields
mentioned above to replace the current M code with calls to these two new
entry points in the PSOUTLA routine.
 
Files & Fields Associated:
------------------------- 
File Name (#)      Field Name (#)                         New/Modified/Deleted
-----------------  -------------------------------------- --------------------
   interface. 
PRESCRIPTION(#52)  FILL DATE (#22)                        Modified 
                   REFILL (#52.1)
                   -REFILL DATE (#.01)                    Modified
  
 
2. I16514233FY17 - Vista transmits two instances of the same prescription
                   to the external interface. 
   R14795402FY17(d) - Vista is sending over prescription data twice for SOME
                      prescriptions, resulting in duplicates showing up in
                      ScriptPro
    
  
Problem: 
--------
There is at least one scenario in Outpatient Pharmacy that will cause a 
prescription fill to be sent twice to the external interface. This happens
because sometimes when the user pulls a CMOP prescription from suspense to 
print locally it will be sent to the print queue twice and consequently it
was also being sent to the external interface twice.
  
Resolution:
3.  Need assistance with SPMP Patient Address errors  
-----------
Added a check in the routine that handles the pull from suspense to prevent
it from adding a prescription to the print queue if the prescription is
already on the queue.
  
Technical Resolution:
---------------------
Modified the routine PSOSUPOE to prevent it from setting the variable PPL
with the same prescription twice.
 
 
 
3. I11517650FY17 - Need assistance with SPMP Patient Address errors    
 
Problem: 
--------
The State Prescription Monitoring Program (SPMP) module did not retrieve the
correct State/Province (SPMP field PAT15 - State Address) and Postal Code 
(SPMP field PAT16 - ZIP Code Address) for patients that have a foreign
address on file. The software was retrieving the US state and Zip Code 
fields, which were both blank for such patients. In addition, the Federal
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
FILE
  • DD NUMBER:
    • PRESCRIPTION (File-top level)
      FIELD NUMBER:
      • FILL DATE
    • REFILL (sub-file)
      FIELD NUMBER:
      • REFILL DATE
    UPDATE THE DATA DICTIONARY:   YES
    SEND SECURITY CODE:   YES
    SEND FULL OR PARTIAL DD:   PARTIAL
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
SEQ# 421
BUILD COMPONENTS
  • ENTRIES:
    • PSOUTLA
      ACTION:   SEND TO SITE
      CHECKSUM:   B52204149
    • PSOASAP
      ACTION:   SEND TO SITE
      CHECKSUM:   B85756536
    • PSOASAP0
      ACTION:   SEND TO SITE
      CHECKSUM:   B169084201
    • PSOSUPOE
      ACTION:   SEND TO SITE
      CHECKSUM:   B81628813