| DESCRIPTION OF ENHANCEMENTS |
This patch will resolve the following issues.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1. I9592038FY16 - Frequently, BCMA users are not able to access the BCBU
database
Problem:
--------
Frequently, BCMA users are not able to access the BCBU database. This result
in local IT support spending time to resolve what should be a minor issue.
However, the fix is not always simple or straight forward. Typically, the
problem is that the user has had a Verify Code change since they last
accessed a contingency. Normally, doing a User Initialization does not
resolve the issue and IT support has to either replace the database or
manually give the user a new Verify code on the contingency computer.
Resolution:
-----------
Modified the routines ALPBGEN, ALPBGEN1 and ALPBGEN2 to remove some
unnecessary restrictions for sending a user update over to the BCBU
1. I9592038FY16 - Frequently, BCMA users are not able to access the BCBU
workstation. For example, if a user was terminated in the main VistA System
it would not be sent to the BCBU workstation. This caused terminated users
in the main VistA System to remain active in the BCBU workstation.
2. I8652828FY16 - Getting ALERT BCBU Contingency Error 46364090 / Missing HLL
Links Array Med-Log
Problem:
--------
database
In a multi-divisional BCBU configuration all Divisions are required to have
an HL7 Logical Link associated. When a division is missing the association an
alert is generated for every transaction that is supposed to go to the BCBU
workstation for that division. The problem is that the Alert does not identify
which division is missing the Logical Link, which makes it hard for the users
to identify the source of the problem and resolve it. Furthermore, the fact
that the Alert does not identify which patient was being processed when the
issue happened makes it hard to troubleshoot and fix the problem as well.
Resolution:
2. I8652828FY16 - Getting ALERT BCBU Contingency Error 46364090 / Missing HLL
-----------
Modified the routine ALPBCBU to include the site number and the patient DFN
number in the Alert subject. This way users will know exactly which division
and the patient that was being processed when a BCBU Alert is generated due to
an error.
Here is how the Alert text will be modified:
Before: BCBU Contingency Error
Missing HLL Links Array Med-Log
Links Array Med-Log
After: BCBU Contingency Error / Site: 442 / DFN: 1930382
Missing HLL Links Array Med-Log
3. I6161931FY16 - Received the error $ZE= <UNDEFINED>ZPD+5^IVMPREC8 *HLFS
I16851052FY18 - Undefined: GENACK+10^RGADTP *HL("MID")
Problem:
--------
3. I6161931FY16 - Received the error $ZE= <UNDEFINED>ZPD+5^IVMPREC8 *HLFS
When an HL7 message is received from an Income Verification Match (IVM) Center
containing demographics data for a patient that includes a date of death the
BCBU application is automatically invoked if such patient has active inpatient
orders. Many other subscribing applications are automatically invoked by the
same process and they all share the same local variables from the invoking
process. The routine ALPBINP was incorrectly killing HL7 local variables such
as HL, HLA, HLCS, HLCTR and HLFS, which were being used by other applications
and in these two specific incidents reported caused the Income Verification
Match (IVM) and Registration applications to error out.
I16851052FY18 - Undefined: GENACK+10^RGADTP *HL("MID")
Resolution:
-----------
Modified the routine ALPBCBU to NEW the variables HL, HLA, HLECH and HLQ and
also modified the routine ALPBINP to no longer kill the HL7 variables HLCS,
HLCTR and HLFS.
NOTE: This fix could not be tested in a development or an SQA environments
because it requires an incoming HL7 message from an external entity.
|
