Patient Registration and Template Utility Help
brought to you by
By George Timson BellFelder Prod. LLC
Technical Installation

The original intent of this product was to be able to simply add a new case to the main database, the Patient file. Through time and one forced programmer "hiatus", it has grown to its current configuration. This, more importantly, is untested code, and might even be considered "Alpha-sub-Alpha" level. Development was on win7-10, using a VMWare host, Delphi2006, version dEWDrop5, which includes the WorldVistA EHR (commonly called CPRS), in Fileman.

Author Jim Bell (BellFelder Prod., LLC), et al, volunteer with WorldVistA.
Environment Linux (Dist. of choice)
Operating System GT.m
Language M
Database & Manager Fileman 22.0
EHR Content FOIA VistA, from WorldVistA
Incoming files
  • 64850001 PATIENT FILE FIELD EXCLUSIONS: These are fields in the patient file that the author (ahem - me...) considers to be VA pertinent. Most of the fields are computed and/or triggered by other fields for specific VA tracking/reporting requirements, and in my opinion, are not very meaningful or pertinent to civilian use.
  • 64850002 CIVILIAN PATIENT FIELDS: Fields selected by the author that are considered to be non-VA mandates.
  • 64850003 FIELD GROUPS: Fields, on build or File structure editing, can have an optional ID to group them by category(s). This is a list of field groups I, and others, consider valid.
  • NOTE: These 3 files will be filed in the DIZ global and all 3 are editable for local need.
  • 64850004 VERBOTEN TEMPLATES: These templates are VA specific templates and contain navigation jumps in the template lines for a "roll 'n scroll" environment. They are 1) fields not likely used in civilian work, and 2) GUIs do not need these kind of jumps. The templates also cause a communication error in that templates asking for a read response (e.g., YES or NO) causes a fatal error in the VA Broker.
  • Application Routine Set
  • Remote Procedure Calls
  • VW REG AHF->AHF^VWREGITX: "ad hoc" field selection and retrieval
  • VW REG ALIST->ALIST^VWREGITX: Returns alpha list via Patient Select
  • VW REG EGF->EGF^VWREGITT: Returns fields for selected template
  • VW REG FGNA->FGNA^VWREGITX: Sort sub-routine for Temp. man. client
  • VW REG FLD BY GRP->LF^VWREGITX: Returns fields via group ID for "ad hoc"
  • VW REG GPD->GPD^VWREGITP: Returns patient data
  • VW REG GPDM->GPDM^VWREGITP: Returns multiple data on a patient
  • VW REG GRP LIST->RETGRP^VWREGITX: List of group id for fields for "ad hoc"
  • VW REG MAIN->EN^VWREGIT: First call and set up for the application
  • VW REG MF->M^VWREGITU: Displays Multiple Field Input form.
  • VW REG MISC->MISC^VWREGITU: Get simple value from VWDD ID
  • VW REG NEW PT^^^NPT^VWREGIT: Returns template fields and [optional] patient info
  • VW REG PF->PF^VWREGIT: Returns data from reference files (e.g., STATE(#5), etc)
  • VW REG RTF->RTF^VWREGITT: Send a refresh of regit.txt to client
  • VW REG SAVE->SAVE^VWREGITS: Saves input sent by the client/user
  • VW REG TEMPLATE->EN^VWREGITT: Template management
  • VW REG ZIP->ZPC^VWREGITU: Returns zip/postal code data(e.g., city, county, state, etc)
  • Menu Options
  • VW REG IT CONTROL: Manager level application management
  • Incoming Parameters
  • Zip File
  • VWREG Folder
  • BFP_Proj1.exe; GUI application

  • Top


    Step 1 Make a folder and place on your C drive. The folder should be named VWREG (c:\VWREG)
    Step 2 Unzip the zip and place all the contents in your new c:\VWREG folder
    Step 3      0. Transfer the .KID file to your *preferred or *working directory
            (and for safety-sake make a copy of the .KID in your dowload/or
            other preferred directory)
         1. chmod 777 [current VWREG KID].KID      2. Run dos2unix on the .KID file
         3. mkdir regparam**
         4. From this directory go to GTM
         5. Do the install procedures through EVE->Programmer Options->KIDS
         * The KIDS installation and M application will use this directory as your home directory
         **This directory in your home directory is where the GUI gets its lists
            of template names from the file regit.txt. It can be manually edited. Note that the
            template name consists of the NAME(INTERNAL RECORD NUMBER).

    NOTE: If you are doing a second install over the first You may have to re-enter your parameter data (see the "Editing Parameters Example" below)
    Step 4 Create a shortcut to the .exe file
    Step 5 Place the shortcut in the c:\Users\Public folder (Example: c:\Users\Public\BFP_Proj1.exe)
    Step 6 Edit your shortcut properties to add your server IP and port No.
    Example:"C:\Users\Public\BFP_Proj1.exe" S= P=9430
    Step 7 There is a backup to the short-cut IP and Port. It is the c:\VWREG\connect.txt file. The application will first look for the shortcut, and, if not found, will then look for the c:\VWREG\connect.txt file. Enter your IP and Port. Line 1 is the IP and line 2 is the port. Example:
    Installation Example c:\VWREG\VWREG_Install.rtf
    Editing Parameters Example c:\VWREG\VWREG_ParameterExample.rtf