| DESCRIPTION OF ENHANCEMENTS |
General Information
SYSTEM ACCESS DURING INSTALLATION
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*38
DSIC 1.3
TEST SITES SYSTEM ALPHA/BETA
======================================================================
Installation of this patch does not require users to be off of the system.
Black Hills, SD (W2K Cache/Thin Client) ALPHA
Westhaven, CT VMS/Cache BETA
ROUTINE SUMMARY
======================================================================
Second line of routines will look like:
;;1.2;DENTAL;<patch list>;AUG 10, 2001
Routine Before Patch After Patch Patch List
-------- ------------ ----------- ------------------------
However, if your site is not a DRM Plus (patch 39) site, then the
DENTV040 n/a 3046754 40
DENTVHL n/a 13088143 40
DENTVHL1 n/a 8156724 40
DENTVHL2 n/a 5154609 40
DENTVHL3 n/a 4139460 40
DENTVHLB n/a 16225605 40
DENTVHLF n/a 7363704 40
DENTVHLU n/a 3937615 40
DENTVRF1 5236302 5245545 31,37,40
DENTVRF2 4641313 4658656 31,37,40
following instructions apply: Dental users should not use the DRM GUI
DENTVRF4 8576541 8692191 31,37,38,40
DENTVUT1 [*** to be deleted***]
=========================================================================
INSTALLATION INSTRUCTIONS FOR DENT*1.2*40
=========================================================================
1. Obtain the Dent_1_2p40.kid file
application while the patch is being installed: all Dental users MUST
2. For DSM sites review your mapped set. Disable any of the above
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_2p40.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
close any open DRM GUI application prior to the patch being installed:
INSTALL NAME, enter DENT*1.2*40)
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*40
7. For the install prompts, enter either Yes or No depending upon the
normal practice at your facility. This example shows answering NO:
Install Questions for DENT*1.2*40
Once the patch has completed the users can use
Incoming Mail Groups:
Enter the Coordinator for Mail Group 'DENTV HL7 MESSAGES':[Name here]
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO
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
the DRM application.
=========================================================================
POST-INSTALLATION PROCESS
=========================================================================
The post-install routine will stuff the facility ID of the installing
site into the HL7 APPPLICATION PARAMTER file for the two parameters being
sent with the package. It will also set the DAS turnoff date in the
new parameter DENTV DRM DAS TURNOFF to 10/31.2004.
The post-install will also re-index some entries for the "AXMIT"
cross-reference in file 228.2 (used by the HL7 interface) due to
potential issues with the Create Date being set as a string.
************************************************************************
* *
* THE FOLLOWING STEPS MUST BE COMPLETED FOR THIS PATCH TO WORK PROPERLY*
* *
************************************************************************
Step 1 is only applicable for sites which have not installed DENT*1.2*39.
========================================================================
********************************************************************
All sites must perform steps 2-x.
-------------------------------------------------------------------------
1 Move dentalmrm.exe
-------------------------------------------------------------------------
This step is only applicable for sites which have not installed
DENT*1.2*39. '...\' indicates your UNC/path for where the current DRM
v3.12 dentalmrm.exe is located.
Move dentalmrm.exe to ..\DOCSTORE
* There is a new DRM executable exported with this patch. This *
-------------------------------------------------------------------------
2 Set up HL7 link for transmitting DES data to the AAC
-------------------------------------------------------------------------
This will demonstrate one way of editing the HL7 link.
Note: VIE stands for Vitria Interface Engine
VAH>D ^XUP
Select OPTION NAME: HL MAIN MENU HL7 Main Menu
------------
* executable is only for DRM sites (not DRM Plus sites!) and MUST *
Select HL7 Main Menu Option: FILER and Link Management Options
-----
Select Filer and Link Management Options Option: Link Edit
----
Select HL LOGICAL LINK NODE: DENTVHLAAC
----------
You will now be in a Screenman display. These instructions will direct
you to the field that needs editing without actually displaying that
Screenman display. You will see the field:
* be deployed PRIOR to Dental users accessing the DRM application *
LLP TYPE: TCP
Move to the LLP TYPE field. With TCP highlighted, press <ENTER>
You should now be in another Screenman display entitled:
TCP LOWER LEVEL PARAMETERS
You will see these three fields on this display:
TCP/IP SERVICE TYPE: CLIENT (SENDER)
TCP/IP ADDRESS: [ip address]
TCP/IP PORT: [port]
* after the patch has been installed. *
A. The TCP/IP SERVICE TYPE should be 'CLIENT {SENDER}'
B. Change the TCP/IP ADDRESS to your VIE IP address
1) If you don't know the VIE IP address, please go to
http://vista.domain.ext/messaging/vie/vie_projectdocs.asp
2) Open the document named VIE Cluster IPs.
3) Find your site and use the IP address listed there.
C. The TCP/IP PORT should be 8090
This port number is assigned by the VIE team for Dental
********************************************************************
Move the cursor to the line: COMMAND:
Enter CLOSE to close the TCP LOWER LEVEL PARAMETERS screen
At the COMMAND: prompt on the HL7 LOGICAL LINK screen
Enter EXIT to save your changes
NOTE: the other logical link, DENTVHLHDR, sent in this patch will be used
in the future to send messages to the Health Data Repository. Do not set
this up yet.
-------------------------------------------------------------------------
3 Turn on the HL7 link DENTVHLAAC
-------------------------------------------------------------------------
This step will turn the link on to enable the messages to be sent.
Within the same Filer and Link Management Options menu in the previous
step:
FIXES TO THE DRM APPLICATION
Select Filer and Link Management Options Option: Start/Stop Links
-----
Select HL LOGICAL LINK NODE: DENTVHLAAC
----------
The link will be enabled. To stop the link, follow the same steps and
you will be prompted if it is Okay to shut down the job. Answer Yes if
you want to stop the link.
--------------------------------------------------------------------------
4 Set up Weekly Scheduled Task
========================================================================
--------------------------------------------------------------------------
You need to schedule the Dental HL7 Batch option to run once a week. The
VIE team is responsible for scheduling communication jobs that use the
VIE. As such, they have assigned SUNDAY as the day that all VAMCs should
schedule this job to run. The time that the job runs on Sunday is left
up to the individual sites. On Monday evening, the VIE team will batch
all the dental HL7 messages received from all VAMCs into a single file
which will be sent to the AAC for processing.
VAH>D ^XUP
A. When transactions are filed only to the History file and not to DAS,
Select OPTION NAME: XUTM MGR Taskman Management
--------
Select Taskman Management Option: SCHedule/Unschedule Options
---
Select OPTION to schedule or reschedule: DENTVHLB BATCH Dental HL7 Batch
--------------
These two fields need to be properly set:
QUEUED TO RUN AT WHAT TIME: select a Sunday date/time
This patch contains the enhancement to send the Dental Encounter and
the system will now file the DAS Disposition in the Dental History
RESCHEDULING FREQUENCY: U@2200
Here is an example of setting up the weekly scheduled option:
Edit Option Schedule
Option Name: DENTVHLB BATCH
Menu Text: Dental HL7 Batch TASK ID:
________________________________________________________________________
QUEUED TO RUN AT WHAT TIME: NOV 7,2004@22:00
(#228.1) file correctly. This field contains the 'in progress',
DEVICE FOR QUEUED JOB OUTPUT:
QUEUED TO RUN ON VOLUME SET:
RESCHEDULING FREQUENCY: U@2200
TASK PARAMETERS:
SPECIAL QUEUEING:
'completed' or 'terminated' flag. The system will also correctly
__________________________________________________________________________
Exit Save Next Page Refresh
Enter a command or '^' followed by a caption to jump to a specific field.
COMMAND: EXIT Press <PF1>H for help
Insert
file the Create Date in this case.
--------------------------------------------------------------------------
5 Set up a Historical One-Time Scheduled Task
--------------------------------------------------------------------------
The Dental Encounter System (DES) has been gathering data since Oct 2000
in file 228. Dental VAHQ would like all that data downloaded to the new
DES database at the AAC. The amount of data at some sites might be
extensive. The VIE team and Capacity Management prefer that an option be
made available to the sites to move that data to
a CD instead of using bandwidth on the VA WAN for moving those HL7
historical messages to the AAC. Thus we have provided an option for the
B. Billing awareness changes were made for the procedure/diagnosis
site to schedule at a time that is convenient for the site.
To estimate the size of the file that will be generated, perform a
Fileman Inquire on file 228.2. The number of records will give you a
ballpark estimate as to the size of the Historical file - each
transaction will take just under 1K when formatted as an HL7 message.
So, a record count of 55,024 will produce a file of < 55,000K or just
under 55meg. Not all records will be sent via the Historical batch of
course, since all records created since the installation of DENT*1.2*38
will be sent via the Vista Interface Engine and the weekly process.
data being sent to PCE.
NOTE: The historical CD is expected at the AAC within one month of the
release of patch 40.
Here are the instructions for setting up a one-time Scheduled Task for
the DENTVHL PROCESS HISTORIC option [menu text: Process one-time
historical extract (Dental)]. Please note that this option will generate
a HFS file with a name like DENTV_HISTORICAL_<site#>.TXT. The file will
be located in the directory as defined
in your Kernel Site Parameters. You can easily see what this value is
from the programmer's prompt as shown in this example:
VAH>W $$PWD^%ZISH
c:\hfs\_TO CD\
Once the historical option has completed, you will need to copy that file
to a CD. You will then mail that CD to the AAC. If you choose to FTP
the file from your VMS system to another network server, then please
remember to FTP the file in ASCII (or text) mode. Here is the mailing
address for that CD:
ENHANCEMENTS TO THE DRM APPLICATION
George Dankworth
Records Management (396B)
Dental Encounter System
1615 Woodward Street
Austin, TX 78772
Example of setting up the one-time queue option:
VAH>D ^XUP
========================================================================
Select OPTION NAME: XUTM MGR Taskman Management
--------
Select Taskman Management Option: SCHedule/Unschedule Options
---
Select OPTION to schedule or reschedule: DENTVHL PROCESS HISTORIC
------------------------
Here is a screen capture of the Taskman Screenman screen showing the
scheduling of this job:
Edit Option Schedule
Option Name: DENTVHLB BATCH
Menu Text: Dental HL7 Batch TASK ID:
________________________________________________________________________
QUEUED TO RUN AT WHAT TIME: AUG 31,2004@22:00
DEVICE FOR QUEUED JOB OUTPUT:
QUEUED TO RUN ON VOLUME SET:
Dental Fee Basis data to the Austin Automation Center (AAC) via an HL7
A. Dental Encounter (DES) and Dental Fee Basis data will be transmitted
RESCHEDULING FREQUENCY:
TASK PARAMETERS:
SPECIAL QUEUEING:
__________________________________________________________________________
Exit Save Next Page Refresh
to the Austin Automation Center (AAC) via HL7 compliant messages. HL7
Enter a command or '^' followed by a caption to jump to a specific field.
COMMAND: EXIT Press <PF1>H for help
Insert
--------------------------------------------------------------------------
6 Add Members to Mail Group
--------------------------------------------------------------------------
messages will be combined into batches that are compiled weekly and
An new mail group has been added called DENTV HL7 MESSAGES. Please add
members to this mail group. These should be individuals who will be
responsible for taking action if the acknowledgement messages that come
back from the AAC which contain error codes. These problems need to be
addressed in the VistA DES database. Those transactions, once fixed,
will need to be flagged for retransmission. A good candidate for a
member would be the dental administrator for DRM in the Dental Service.
This is an example of adding a member to this mail group. There are
sent to the AAC using the Vista interface engine. Batches are
several Kernel options that allow the adding of members to a mail group
including using Fileman. This example just shows one of those options'
display:
Select MAIL GROUP NAME: DENTV HL7 MESSAGES
------------------
Select MEMBER: [add the name of the person to become a member]
TYPE:
==========================================================================
limited to 1000 HL7 msgs. There are at least two batches being sent
SAMPLE INSTALLATION EXAMPLE
==========================================================================
Select Installation Option: INstall Package(s)
Select INSTALL NAME: DENT*1.2*40 Loaded from Distribution
8/31/04@10:09:43
=> DENT*1.2*40 ;Created on Aug 25, 2004@14:15:23
This Distribution was loaded on Aug 31, 2004@10:09:43 with header of
DENT*1.2*40 ;Created on Aug 25, 2004@14:15:23
It consisted of the following Install(s):
from the local sites, one containing Dental Encounter data and one
DENT*1.2*40
Checking Install for Package DENT*1.2*40
Install Questions for DENT*1.2*40
Incoming Files:
228.2 TREATMENT PLAN TRANSACTION/EXAM (Partial Definition)
Note: You already have the 'TREATMENT PLAN TRANSACTION/EXAM' File.
for Dental Fee Basis data. The data transfer will be initialized
228.25 DES/HL7 TRANSMISSION
Note: You already have the 'DES/HL7 TRANSMISSION' File.
228.5 DENTAL FEE BASIS EXTRACT (Partial Definition)
Note: You already have the 'DENTAL FEE BASIS EXTRACT' File.
Incoming Mail Groups:
Enter the Coordinator for Mail Group 'DENTV HL7 MESSAGES': [enter name]
through a weekly queued option. The site no longer has to manually
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO
Want KIDS to INHIBIT LOGONs during the install? YES// NO
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
DEVICE: HOME// ;P-DEC;80;999 TELNET PORT
Install Started for DENT*1.2*40 : Aug 31, 2004@10:10:17
Build Distribution Date: Aug 25, 2004
Installing Routines:........... Aug 31, 2004@10:10:17
Installing Data Dictionaries: .... Aug 31, 2004@10:10:18
start the transmission to the AAC as they did for the Dental Activity
Installing PACKAGE COMPONENTS:
Installing MAIL GROUP..
Installing HL LOGICAL LINK...
Installing HL7 APPLICATION PARAMETER......
Installing PROTOCOL....
Located in the DENT (DENTAL) namespace..
Located in the DENT (DENTAL) namespace..
Installing OPTION...
Installing PARAMETER DEFINITION.. Aug 31, 2004@10:10:19
Running Post-Install Routine: POST^DENTV040.
System (DAS) data. DAS transmissions will be disabled in another
>>>>> Updating the DENTV-C, DENTV-F HL7 params with your Facility Name
<<<<<
>>>>> Updating the DENTV DRM DAS TURNOFF param with date 10/31/2004
<<<<<
Update of file 228.2 CREATE DATE field successfully queued, task# 361543
Updating Routine file
Updating KIDS files.......
DENT*1.2*40 Installed. Aug 31, 2004@10:10:20
interface. It also contains enhancements to the Dental Record Manager
DRM patch.
B. Historical Dental Encounter data (transactions filed before DRM patch
38 was installed) will be sent to the AAC via a CD. An option is
available to create these HL7 messages and put them into a file on
a server. The file needs to be copied onto a CD and mailed to the
AAC.
C. A new parameter DENTV DRM DAS TURNOFF contains a date which controls
the filing of data to DAS (file 221). When the date is reached, DRM
(DRM) application.
will no longer offer the File DAS Only option and will not file any
data to file 221 even when filing to All (DES, PCE are now the only
filing choices). Also, the old 4 digit Provider ID will no longer
be required when adding/editing dental providers. The turnoff date
is defaulted to 10/31/2004.
D. When the user looks up providers (in the Extract, Provider Add/Edit
options, the provider list will now contain their initials and title
to help differentiate users with the same name.
E. Combat Veteran status has been added to the Service Connected
selection page.
F. The text of the filing options was changed from "File DAS/PCE..." to
"File Data...".
NOIS ADDRESSED BY THIS PATCH
========================================================================
BRX-0804-10469 NOL-0804-70250 CLL-0804-40357 MON-0804-51726
The patch installation process should take be less than 5 minutes.
INSTALLATION FILES
========================================================================
How to Obtain KIDS File
File Name: DENT_1_2P40.zip FTP format: binary
DENT_1_2P40.zip file will contain the following files:
FTP
File Name Description Format
----------------------- ------------------------------------- ------
Dent_1_2p40.kid Installable KIDS file ASCII
Dentalmrm.exe DRM Version 3.13 executable Binary
Dent_1_2p40_ug.doc Dental Record Manager's user guide Binary
The guide was updated for HL7/DAS turnoff
and Combat Veteran status flag
Dent_1_2p40_rn_ig.pdf DENT*1.2*40 Release Notes and Binary
Installation Guide
P40_patch_description.doc A copy of the patch description Binary
|
