| DESCRIPTION OF ENHANCEMENTS |
General Information
(DAS FIELD, DAS DATA) based on the ADA table. The second conversion
Most of these fields are used in DES Reports.
G. A Fileman error was occurring when entering single letter look-ups
(e.g., "B") in the Provider lookup screen. This screen is displayed
when clicking the New button on the Provider Edit screen, or
when selecting the optional Provider checkbox on the Extract screen,
or when selecting to file an encounter under another provider's
name. The error has been fixed. This type of error was also
occurring on the User lookup screens (User Inquiry and user selection
within the Administrator Toolbox), and was also fixed.
changes the DIVISION pointer in file 228.1 from a pointer to file 40.8
H. CPT code search was returning D2950 when the code D2951 was entered.
This has been fixed.
I. The word 'Extract' was spelled incorrectly on the old Extract History
Data screen. It's now correct.
J. Consults were not being completed when the user Double-Clicked them,
only when the consult was single-clicked. Now they will complete
either way. NOIS: MIA-0304-30860
to a pointer to file 4. The DD is being sent for this field to change
K. Change the field definition for field 1.18 in the TREATMENT PLAN
TRANSACTION/EXAM file (#228.2). This field was not used, and will
now store the HL7 transmission status.
L. A new field called TP RECORD (.06) was added to the TREATMENT PLAN
TRANSACTION/EXAM file (#228.2). The field will be set to 1 for
Treatment Plan (DRM+) transactions to differentiate them from DRM.
M. A new field called TREATMENT FLAGS (1.202) was added to the TREATMENT
the pointers. The final conversion removes the TIU Note pointer data
PLAN TRANSACTION/EXAM file (#228.2). The field will be contain the
tooth-related flag.
N. The SURFACES (.16) field in the TREATMENT PLAN TRANSACTION/EXAM file
(#228.2) was renamed to SURFACES/ROOTS and the field definition now
allows 1-7 characters (upper/lower) vs only uppercase characters.
ENHANCEMENTS TO THE DRM APPLICATION
========================================================================
from file 228.1.
A. DES Reports are part of this patch. This enhancement provides six
dental reports for the local VistA system. The reports are:
Provider Summary, Clinic Summary, Sittings by Provider, Individual
Sittings, Non-Clinical Time Report, Dental Fee Basis Report. These
reports are similar to DAS reports of the same name. Reports are
available on the Tools menu for all users.
B. Provider Add/Edit is part of this patch. This enhancement allows the
dental administrator to add or edit the dental staff in the DENTAL
PROVIDER (#220.5) file. A new eight character Dental Provider Id has
been created and will be used in the DES Reports. The old four
character Dental Provider Id is still required for DAS, but will be
deprecated when DAS is replaced. Provider Add/Edit is available on
the Tools menu for administrative users.
C. A new Extract History data option is available on the Tools menu.
This option does not use RPC calls to get history data, but uses
instead, a TCP/IP process running on the local machine. When the
user wants to run the new extract, a process will start in the
user's system tray and will wait for data from Vista. When the data
The patch installation process should take be less than 5 minutes.
has been sent, the Vista M code will send a Shutdown message to stop
the TCP/IP server. During the patch testing phase for Patch 38, the
old Extract option will remain enabled along with the new Extract
option. NOTE! Users will have to contact IRM to get a valid Port#
to be used with the extract! The user must also know the IP address
of their workstation in order for the Vista M code to correctly
connect to the TCP/IP process running on their machine! These
parameters will be stored on Vista and can be edited/viewed via the
Parameters button on the new Extract History Data screen.
The post-installation conversion process may take several hours
D. Fee Basis and Dental Transaction records will start setting the
"AXMIT" cross-reference correctly ("P" for pending, "C" for canceled)
in preparation for transmitting HL7 records to AAC.
NOIS ADDRESSED BY THIS PATCH
========================================================================
MIA-0304-30860
depending upon the number of records in file 228.1 and 228.2.
INSTALLATION FILES
========================================================================
How to Obtain KIDS File
File Name: DENT_1_2P38.zip FTP format: binary
DENT_1_2P38.zip file will contain the following files:
FTP
File Name Description Format
------------------------ -------------------------------------- ------
Dent_1_2p38.kid Installable KIDS file ASCII
This conversion process will be tasked off in the background.
Dentalmrm.exe DRM Version 3.12 executable Binary
DRMEXTSRV.exe DRM TCP/IP executable Binary
Dent_1_2p38_ug.doc Dental Record Manager's user guide Binary
Updated w/ Reports/Prov Edit/Extract
Dent_1_2p38_rn_ig.doc DENT*1.2*38 Release Notes and Binary
Installation Guide
P38_patch_description.txt A copy of the patch description ASCII
Patch 38 Enhancements.doc Describing just the enhancements Binary
The zip file listed above may be obtained via FTP. The preferred method
========================================================================
is to FTP the files from download.vista.domain.ext
This transmits the files from the first available FTP server. Sites may
also elect to retrieve software directly from a specific server as
follows:
CIO FIELD OFFICE FTP ADDRESS DIRECTORY
---------------- ------------------------- --------------------
Albany ftp.fo-albany.domain.ext [anonymous.software]
Hines ftp.fo-hines.domain.ext [anonymous.software]
Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]
REQUIRED BUILDS: DENT*1.2*37
TEST SITES SYSTEM ALPHA/BETA
========================================================================
Fargo, ND (W2K Cache/Thin Client) ALPHA
Manhattan, NY (VMS DSM) BETA
SYSTEM ACCESS DURING INSTALLATION
ROUTINE SUMMARY
=======================================================================
Second line of routines will look like:
;;1.2;DENTAL;<patch list>;AUG 10, 2001
Routine Before Patch After Patch Patch List
-------- ------------ ----------- ------------------------
DENTV037 [*** to be deleted***]
========================================================================
DENTV038 n/a 4808142 38
DENTV03C n/a 21799174 38
DENTV03D n/a 21047556 38
DENTV03E n/a 21447147 38
DENTV03F n/a 19998119 38
DENTV03G n/a 1622718 38
DENTVA1 n/a 10886320 38
DENTVA2 n/a 12235826 38
DENTVAU n/a 2285628 38
DENTVDD1 4809284 5137431 31,38
Installation of this patch does not require users to be off of the
DENTVFB 2775003 2787426 37,38
DENTVIP3 3716294 3714758 31,38
DENTVRF4 7883662 8576541 31,37,38
DENTVRH 6429972 6800370 31,37,38
DENTVRP5 n/a 3121694 38
DENTVRP8 n/a 3913187 38
DENTVRP9 6021923 6021572 30,32,34,31,38
DENTVTP2 n/a 3443632 38
DENTVUT1 3413708 3440255 31,38
system. However, all Dental users should not use the DRM GUI option
INSTALLATION INSTRUCTIONS FOR DENT*1.2*38
=======================================================================
This patch must be installed when there are no dental DRM processes
running. All open DRM GUI applications must be closed.
The installation time should take less than 5 minutes.
1. Obtain the Dent_1_2p38.kid file
2. For DSM sites review your mapped set. Disable any of the above
while the patch is being installed. All Dental users MUST close any
routines if necessary
3. From the Kernel Installation and Distribution System Menu, select
the Installation menu
4. Use Load a Distribution and enter Dent_1_2p38.kid when prompted
for a Host file. You may need to attach a directory name
5. You may elect to use the following options (when prompted for
INSTALL NAME, enter DENT*1.2*38)
open DRM GUI application prior to the patch being installed. Once the
a. Backup a Transport Global
b. Compare Transport Global to Current System
c. Verify Checksums in Transport Global
6. Use the Install Package(s) option and select package DENT*1.2*38
7. For the install prompts, enter either Yes or No depending upon the
normal practice at your facility. This example shows answering NO:
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO
patch has completed the users can use the DRM application. Until
Want KIDS to INHIBIT LOGONs during the install? YES// NO
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
8. AXP/DSM Sites - After the patch has been installed, rebuild your map
set, if necessary
9. This step must be completed for this patch to work properly
a. ...\ will indicate your UNC/path for where the current DRM
v3.11 dentalmrm.exe is located
b. Move dentalmrm.exe to ...\DOCSTORE
the conversions are complete, the new DRM reports may not give accurate
c. Move DRMEXTSRV.exe to ...\DOCSTORE
(Do not add CPRS menu for this new executable! It is called
within the DRM application.)
This patch contains fixes and enhancements to the Dental Record Manager
results since they need the new DAS FIELD and DAS DATA data in file
228.2, and they search for data based on the DIVISION field which is
also being changed.
********************************************************************
* There is a new DRM executable exported with this patch. This *
* executable MUST be deployed PRIOR to Dental users accessing the *
* DRM application after the patch has been installed. *
********************************************************************
(DRM) application. This patch also contains new M Globals for DRM in
PRE-INSTALLATION PROCESS
========================================================================
The pre-install process will delete field .18(DIVISION) from file 228.1.
This field will be reinstalled as part of the patch.
The pre-install process will delete the TIU Note pointer from file 228.1.
This field is no longer used.
The pre-install process will also delete field .16(SURFACE) and 1.18
the DENT namespace - ^DENT(220.51 and ^DENT(220.52 to support the new
(TEMP TRANS ID) from file 228.2. These fields will be reinstalled as
SURFACES/ROOTS and HL7 STATUS, respectively.
POST-INSTALLATION PROCESS
========================================================================
The post-install routine will queue up a Taskman job to convert files
228.1, (division pointer and removing any TIU Note pointer data) and
228.2, (setting DES reporting fields). It will also create a new index
on file 228.1 for DES reporting ("AG") and re-index the "AF" cross-ref
eight character Dental Provider Id.
on file 228.1.
***********************************************************************
* *
* THE FOLLOWING STEP BE COMPLETED FOR THIS PATCH TO WORK PROPERLY *
* *
***********************************************************************
At this point, the KIDS install will have completed. IRM needs to place
the DRM GUI executable in the appropriate directory. The placement of
this DRM executable can be done at the same time the KIDS build is being
installed. The executable must be placed as follows where ...\
indicates your UNC/path for where the current DRM v3.11
dentalmrm.exe is located:
Move dentalmrm.exe to ...\DOCSTORE
Also... the new extract executable needs to be placed in the
same directory where dentalmrm.exe resides.
Move DRMEXTSRV.ext to ...\DOCSTORE
Three database conversions will be run as part of the post installation.
FIXES TO THE DRM APPLICATION
========================================================================
A. The list of Visits that display when the user wants to Delete a
Dental Encounter will now display in reverse chronological order with
no duplicates.
B. The information on the Dental History tab will display in reverse
chronological order by date/time, not just date.
C. If there are no Vital signs to be imported, an extra linefeed was
The first conversion seeds the new fields in 228.2 for the DES Reports
appearing in the note - the extra linefeed has been removed.
D. Change the .18 field (DIVISION) in the DENTAL HISTORY file (#228.1)
From a pointer to file 40.8 (MEDICAL CENTER DIVISION) to a pointer to
file 4 (INSTITUTION).
F. Add fields DAS FIELD, DAS DATA to the TREATMENT PLAN TRANSACTION/EXAM
file (#228.2). These fields will be seeded with data during the post
install conversion. These fields, along with the CTV, VA-DSS GROUP
fields will be set appropriately when transactions are filed.
|
