ADVANCED MEDICATION PLATFORM (237)    PACKAGE (9.4)

This patch exports the new option PREA AMPL GUI. This patch also contains
validate that AMPL is an entry in the REMOTE APPLICATION (#8994.5) File,
and then the VistA can add that user to the NEW PERSON (#200) File without
user intervention and return the requested data.
a post-init routine that adds ADVANCED MEDICATION PLATFORM (AMPL) as an
entry in the REMOTE APPLICATION (#8994.5) File, and links it to the new
PRE AMPL GUI option. This must occur prior to the release of the full AMPL
project. When using the AMPL application, if a user makes a request to see
VistA data from a VistA instance where the user does not have an entry in
the NEW PERSON (#200) File, this VistA system will use the Security
Assertion Mark-up Language (SAML) token to authenticate the user and
authorize that user to view the requested data. Part of that process is to

This patch exports the new option PREA AMPL GUI. This patch also contains
validate that AMPL is an entry in the REMOTE APPLICATION (#8994.5) File,
and then the VistA can add that user to the NEW PERSON (#200) File without
user intervention and return the requested data.
a post-init routine that adds ADVANCED MEDICATION PLATFORM (AMPL) as an
entry in the REMOTE APPLICATION (#8994.5) File, and links it to the new
PRE AMPL GUI option. This must occur prior to the release of the full AMPL
project. When using the AMPL application, if a user makes a request to see
VistA data from a VistA instance where the user does not have an entry in
the NEW PERSON (#200) File, this VistA system will use the Security
Assertion Mark-up Language (SAML) token to authenticate the user and
authorize that user to view the requested data. Part of that process is to

This patch exports a new option that will identify the users who will 
option exported with this patch.
 
 
The option will work as follows:
 
The stand-alone option, PREA AMPL GUI ACCESS, when invoked creates the
list of users that will receive AMPL access based on VistA Security Key
ownership and Person Class affiliation. When the option is run in the test
account, the list will only be sent to the person who ran the option, in a
VistA Mail Message. The message might also be sent in outlook, but that
receive access to the Advanced Medication Platform (AMPL) GUI application
depends on the mail configuration at each site. When the option is run in
production the user will be given the choice to only send the list to the
person who ran the option, or additionally send it to the VA IT EPMO EPMD
PRE Pharm GUI SSOi Outlook Mail Group that will handle the granting of
AMPL access to everyone on the list. When the option is run and the list
goes to the mail group, the option will be inactivated. The list will not
be submitted immediately to get the access granted, so until that time it
is submitted, the site contact can request changes to the user list by
messaging the VA IT EPMO EPMD PRE Pharm GUI SSOi Outlook Mail Group. The
site will be notified when the list is submitted. After submission, access
when it is initially installed at each site at a later date.
can still be granted to users or removed from users on an individual basis
by following the steps provided by Appendix A of the PREA Technical
Manual.
 
The option uses the following hierarchy to determine the granting of AMPL
access:
 
1) A user is not granted AMPL access if the user has a past date or the 
current date in the TERMINATION DATE Field (#9.2) of the NEW PERSON File
(#200).
 
 
2) A user is not granted AMPL access if the DISUSER Field (#7) of the NEW 
PERSON File (#200) is set to '1' (YES) for that user.
 
3) A user is granted AMPL access if they are assigned any of the following
VistA Security Keys:
 
        PSORPH
        PSO TECH ADV
        PSD TECH
Other than verifying successful patch PREA*1*3 installation, no further 
        PSD TECH ADV
        PSDRPH
        PSDMGR
        PSJ PHARM TECH
        PSJ RPHARM
        PSJI MGR
        PSJI PHARM TECH
        PSJU MGR
        PSJU RPH
  
action is required at this time. The AMPL application will be a phased 
4) A user is granted AMPL access if that user has an active entry in the
PERSON CLASS Subfile (#200.05) of the NEW PERSON File (#200), and that
Person Class entry in the PERSON CLASS File (#8932.1) has the text "PHARM"
contained in the PROVIDER TYPE Field (.01) or the CLASSIFICATION Field 
(#1). The text "PHARM" can be in uppercase, lowercase, or any combination.
                      
 
Note: Routine PREAPO2 is included in this patch only to correct some minor
issues to non-executable code to adhere to the M Programming Standards 
and Conventions.
rollout, and the AMPL Implementation Manager will be in contact with each
site at the appropriate time prior to the site's AMPL implementation, and
will coordinate with the appropriate site personnel the running of the