The VistA Integration Adapter (VIA) team needs to create two new proxy
and the new Application Proxy is implemented by the post-init routine
VIABRPC5. After successful installation, the site will need to
manually create the Connector Proxy utilizing Foundations Manager
as detailed in the Post-Installation instructions.
************************ Important Information ***********************
** **
** Note: A VistaLink listener port needs to be open, available and **
users in order to connect via VistALink and to allow Remote Procedure
** maintained by each production site. **
** **
** Note: The host name/address and VistALink port must be correctly **
** defined in the VistALink **
** gov.va.med.vistalink.connectorConfig.xml file **
** **
**********************************************************************
Calls (RPC) to be invoked. These users are VIABCONNECTORPROXY,VIAB
for the Connector Proxy and VIABAPPLICATIONPROXY,VIAB for the
Application Proxy. In addition, a new menu option is created.
In order to implement the changes required for this patch, a
combination of patch updates and post-installation steps are required.
The new VIAB WEB SERVICES OPTION option is installed by the patch
VIAB*1.0*15
that omission.
(2). Moves LISTORDERS on the 'AF' cross reference
(3). Uses DATE/TIME ORDERED in LISTORDERS and LISTORDERACTIONS compare
Changes include:
(1). Add a $GET to ORDACT2+4^VIABMS4
The remote procedure VIABMS contains a target LISTORDERACTIONS that
filters orders by ORDER ACTION. When checking the STATUS field which is
defined on the 3-node of the file, it does not include a $GET to protect
against the possibility that the node might not be present. This corrects
This patch adds the RPC SDEC APPSLOTS for odd clinic start times to
the VIAB WEB SERVICES option to register this RPC. See ICR 7071 for
approval to call the RPC.
This patch fixes the following COVID-19 VIA applications:
1. Bed Management Solutions (BMS). [ListOrderActions] fix when Order
Text field has '[' in its result.
2. Adds a new RPC to the REMOTE PROCEDURE CALL file (#8994), VIAB GETDEM
to return patient demographic data using the PIMS supported DEM^VADPT
API call.
3. Adds RPC VIAB GETDEM to VIA's VIAB WEB SERVICES OPTION option.
ADD RPC VIAB PATCH, SO THAT VIAB WEB SERVICES CAN DETERMINE WHEN VISTA
PATCHES ARE PRESENT. EX: OR*3.0*524
21b
DATE APPLIED: 2021-05-12 00:00:00
DESCRIPTION:
Backup of VIAB*1.0*21 on May 12, 2021
Warning: Installing this backup patch message will install older versions
of routines and Build Components (options, protocols, templates, etc.).
Please verify with the Development Team that it is safe to install.
The VistA Integration Adapter (VIA) team needs to create two new proxy
and the new Application Proxy is implemented by the post-init routine
VIABRPC5. After successful installation, the site will need to
manually create the Connector Proxy utilizing Foundations Manager
as detailed in the Post-Installation instructions.
************************ Important Information ***********************
** **
** Note: A VistaLink listener port needs to be open, available and **
users in order to connect via VistALink and to allow Remote Procedure
** maintained by each production site. **
** **
** Note: The host name/address and VistALink port must be correctly **
** defined in the VistALink **
** gov.va.med.vistalink.connectorConfig.xml file **
** **
**********************************************************************
Calls (RPC) to be invoked. These users are VIABCONNECTORPROXY,VIAB
for the Connector Proxy and VIABAPPLICATIONPROXY,VIAB for the
Application Proxy. In addition, a new menu option is created.
In order to implement the changes required for this patch, a
combination of patch updates and post-installation steps are required.
The new VIAB WEB SERVICES OPTION option is installed by the patch
PCE changes brought on by PX*1.0*211 require changes for mobile
applications. This patch will change the return for saveNoteandEncounter
service of Vista Integration Adapter to provide better messaging for the
calling application. However, this patch is NOT dependent on PX*1.0*211.
The return array may contain some new values if PX*1.0*211 is present.
Description:
characters, LIST^DIC returns an 'overflow' error "The data requested for
the record is too long to pack together." and the result doesn't pass over
to BMS.
Resolution: In an effort to pass the result to BMS, the text will get
truncated after 3675 characters with the trailing tag:
"<*NOTE: order text reached max length, please check appropriate system
for full order text*>"
===========
This patch addresses the return text value from the Bed Management System
(BMS) LISTORDERACTIONS call when the result string exceeds a number of
characters.
Problem: LISTORDERACTIONS uses the LIST^DIC call within its code. If the
size of the Order's Order Text field is too wordy and exceeds a number of
The VistA integration Adaptor (VIA) project requires access to certain
Remote Procedure Calls (RPCs). The purpose of this patch is to publish
those RPCs in the OPTION file (#19), RPC field (#320) which allows VIA
to access.
