| DESCRIPTION OF ENHANCEMENTS |
***********************************NOTE***********************************
(HDR) to receive clinical data about patients the patient must have an
Integration Control Number (ICN) and Treating Facility (TF) List. VistA
under certain circumstances allows backdoor entry of clinical activity to
be recorded for a patient without "requiring" a patient to have an ICN.
The immediate needs of the HDR have identified several issues within the
existing PIM to uniquely identify patients through the ICN enumeration
process. PIM services are tied into VistA at several points. In the
current VistA structure, up front identity management is done only within
Registration via several different menu options, as that has been the
traditional entry point of patients into the system. In addition, there
This patch does NOT conflict with CoreFLS and can be installed at CoreFLS
are "hooks" within Appointment Management, which assign a local ICN after
the patient has received care. Subsequently, the national ICN is obtained
through a nightly job or via manual resolution of the local ICN. The
requester states that the current method does not support good business
practices for updating patient identity traits at appropriate entry points
and does not provide the full functionality of the benefit of the ICN in
linking all patient data together.
This is the Outpatient Pharmacy patch PSO*7*185 that places the ICN check
(hooks) within the Outpatient Pharmacy V. 7.0 options, to dynamically
sites.
assign a local ICN for a patient if one was not found.
Outpatient Pharmacy will not make any changes to options where the
patient look up is done via the FileMan DIC call on the PATIENT file
(#2). As part of the PIM project, the Master Patient Index V. 1.0 package
will send out a separate patch that will have the ICN "hooks" in place.
In Outpatient Pharmacy, the following options do not use the standard
patient lookup (FileMan DIC call on the PATIENT file (#2)), as the
primary input for selecting orders.
**************************************************************************
Release Medication [PSO RELEASE]
Return Medication to Stock [PSO RETURNED STOCK]
Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS]
Complete Orders from OERR [PSO LMOE FINISH]
Barcode Batch Prescription Entry [PSO BATCH BARCODE]
Discontinue Prescription(s) [PSO C]
Edit Prescriptions [PSO RXEDIT]
Reprint an Outpatient Rx Label [PSO RXRPT]
View Prescriptions [PSO VIEW]
Pull Early from Suspense [PSO PNDRX]
For these options, a check is put in place to see if the INTEGRATION
CONTROL NUMBER (ICN) field (#991.01) of the PATIENT file (#2) is populated
by calling the API #2701, $$GETICN^MPIF001(DFN). If it is not populated
then a call is made to the API #3300, $$MPIQQ^MPIFAPI(DFN) that will
populate the INTEGRATION CONTROL NUMBER (ICN) field (#991.01) of the
PATIENT file (#2).
Note: This patch also carries a fix for NOIS PAL-0804-60841.
PATCH OVERVIEW
Patch PSO*7*175 - FEE REPLACEMENT ENCAPSULATION PROJECT, calls the API
#4395, $$RXSUM^FBRXUTL(DATE,STATION_NUMBER), to collect the fee basis
prescription count and cost for a given date and the approving Veterans
Affairs Medical Center (VAMC) station number. The station number that is
passed to the API is the STATION NUMBER field (#99) of the INSTITUTION
file (#4), which constitutes a 3 digit station number plus any modifiers.
The API #4395 requires only the first 3 digits of the station number
otherwise it will return an error message, "Valid station number not
specified". This patch fixes this problem.
Gail Graham, Director of Information Assurance requested that a process
of Patient Identity Management (PIM) be created that uniquely identifies a
patient prior to providing care. In order for the Health Data Repository
|
