# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | FREE TEXT | B | Enter only data that is actually part of the person's name. Do not include extra titles, identification, flags, local information, etc. Enter the person's name in 'LAST,FIRST MIDDLE SUFFIX' format. This value must be 3-35 characters in length and may contain only uppercase alpha characters, spaces, apostrophes, hyphens and one comma. All other characters and parenthetical text will be removed. | |
.111 | street address 1 | .11;1 | FREE TEXT | This is the first line of the street address of the permanent address of the new person. | ||
.112 | street address 2 | .11;2 | FREE TEXT | This is the second line of the street address of the permanent address of the new person. | ||
.113 | street address 3 | .11;3 | FREE TEXT | This is the third line of the street address of the permanent address of the new person. | ||
.114 | city | .11;4 | FREE TEXT | This is the city of the permanent address of the new person. | ||
.115 | state | .11;5 | POINTER | 5 | This is the state of the permanent address of the new person. | |
.116 | zip code | .11;6 | FREE TEXT | This is the postal ZIP code of the permanent address of the new person. | ||
.1211 | temporary address 1 | .121;1 | FREE TEXT | This is the first line of a temporary address for the new person. | ||
.1212 | temporary address 2 | .121;2 | FREE TEXT | This is the second line of a temporary address for the new person. | ||
.1213 | temporary address 3 | .121;3 | FREE TEXT | This is the third line of a temporary address for the new person. | ||
.1214 | temporary city | .121;4 | FREE TEXT | This is the city of the temporary location for the new person. | ||
.1215 | temporary state | .121;5 | POINTER | 5 | This is the state of the temporary location for the new person. | |
.1216 | temporary zip code | .121;6 | FREE TEXT | This is the postal ZIP code for the temporary location for the new person. | ||
.1217 | start date of temp addres | .121;7 | DATE-TIME | This is the beginning date for use of the temporary address for the new person. | ||
.1218 | end date of temp address | .121;8 | DATE-TIME | This is the ending date for use of the temporary address for the new person. | ||
.131 | phone (home) | .13;1 | FREE TEXT | This is the telephone number for the new person. | ||
.132 | office phone | .13;2 | FREE TEXT | This is the business/office telephone for the new person. | ||
.133 | phone #3 | .13;3 | FREE TEXT | This is an alternate telephone number where the new person might also be reached. | ||
.134 | phone #4 | .13;4 | FREE TEXT | This is another alternate telephone number where the new person might also be reached. | ||
.135 | commercial phone | .13;5 | FREE TEXT | This is a commercial phone number used by IFCAP. | ||
.136 | fax number | .13;6 | FREE TEXT | This field holds a phone number for a FAX machine for this user. It needs to be a format that can be understood by a sending MODEM. | ||
.137 | voice pager | .13;7 | FREE TEXT | This field holds a phone number for an ANALOG PAGER that this person carries with them. It needs to be a format that can be understood by a sending MODEM. | ||
.138 | digital pager | .13;8 | FREE TEXT | This field holds a phone number for a DIGITAL PAGER that this person carries with them. It needs to be a format that can be understood by a sending MODEM. | ||
.141 | room | .14;1 | FREE TEXT | This is the room number assigned to the new person. | ||
.151 | email address | .15;1 | FREE TEXT | This field contains the e-mail address to which an outside person or vendor can send correspondence. (i.e. firstname.lastname@domain.ext or lastname.firstname@domain.ext or lastname.firstname_i+@domain.ext as in smith.robert_b+@domain.ext for Robert B. Smith on Forum). (* Note: period replaces comma in lastname.firstname syntax, underscore replaces space, and plus sign replaces period following middle initial for VISTA MailMan addresses.) This address may appear on documents going to vendors. | ||
1 | initial | 0;2 | FREE TEXT | C | These are the initials of the user, which may be entered for naming users. | |
2 | access code | 0;3 | FREE TEXT | This is a unique code to identify a user to the system. This code is hashed so that it can't be looked up to find out the code. The access code will appear as a string of numbers, but must be entered as a separate entry. Users who have no access code will not receive mail. *** This field should never be edited directly - do not remove WRITE ACCESS! | ||
2.1 | want to edit access code (y/n) | .1;10 | FREE TEXT | Entering a YES to this field calls the KERNEL routine for entering ACCESS codes. No data is stored for this field. | ||
2.2 | date access code last changed | COMPUTED | This is the date the ACCESS CODE was last changed. It is used to see that codes are changed on a regular basis. | |||
3 | file manager access code | 0;4 | FREE TEXT | This is the string that is put in DUZ(0) for use by fileman to check file and field access. | ||
4 | sex | 1;2 | SET OF CODES | M:MALE F:FEMALE | This is the gender for the new person. | |
5 | dob | 1;3 | DATE-TIME | This is the date of birth of the new person. | ||
7 | disuser | 0;7 | BOOLEAN | 0:NO 1:YES | This field, if set to YES (1), marks a user that is not allowed to log on to this system. It will leave all Menus, Keys and other attributes exabled for the user. An example would be an external support person that you only want to be able to log on to your system when you are monitoring them. Setting this field would prevent them from loging on to the system untill you cleared the field. | |
7.2 | verify code never expires | 0;8 | BOOLEAN | 0:No 1:Yes | This field will control if the users VERIFY code will expire at the interval set by the Kernel System Parameter LIFETIME OF VERIFY CODE. This field should only be used for access to the VistA system from other systems making connection with the RPCBroker and have very controlled access. Only persons with the XUMGR key are allowed to set this flag. | |
8 | title | 0;9 | POINTER | 3.1 | This is the title for the new person. | |
9 | ssn | 1;9 | FREE TEXT | SSN | This is the social security number of the new person. | |
9.2 | termination date | 0;11 | DATE-TIME | This is the date after which the computer will no longer recognize this user's ACCESS CODE. Once this date has passed, when the USER TERMINATE job runs it will clean out this users data based on flags in the NEW PERSON file. | ||
9.21 | delete all mail access | 0;5 | BOOLEAN | y:YES n:NO | This gives you the ability to purge all of a user's mail related information. This includes Mail messages, Mail Boxes, Mail Groups, Surrogate privlages when that user is terminated. This is recomended. | |
9.22 | delete keys at termination | 0;6 | BOOLEAN | y:YES n:NO | This gives you the ability to delete all of a user's security keys, and delagated keys when the user is terminated. This is recomended. | |
9.3 | terminal type last used | 1.2;1 | POINTER | 3.2 | This field holds a pointer to the last terminal type the user selected at sign-on or in edit user char. | |
9.4 | termination reason | 0;13 | FREE TEXT | This field holds a short description of why the user has been terminated or has DISUSER flag set. | ||
9.5 | user class | USC3;0 | MULTIPLE | 200.07 | ||
10 | alias | 3;0 | MULTIPLE | 200.04 | Other names used by this new person. | |
10.1 | name components(+) | 3.1;1 | POINTER | 20 | Answer with the entry in the NAME COMPONENTS file that contains the components of the person's name. | |
10.6 | degree | 3.1;6 | FREE TEXT | This field holds any academic or professional degree that have been earned by the user. This would be things like BS, BA, MD, and PHD. | ||
11 | verify code | .1;2 | FREE TEXT | This is the code that is used to verify that the ACCESS CODE was not found by accident. It may be entered at logon time immediately after the ACCESS CODE by typing a semicolon, then the VERIFY CODE. Verify codes may be changed by the user with the CHANGE USER CHARACTERISTICS option. The kernel site parameter field LIFETIME OF VERIFY CODE forces the user to periodically enter a new verify code. | ||
11.1 | want to edit verify code (y/n) | .1;11 | FREE TEXT | Entering a YES to this field calls the KERNEL routine for entering VERIFY codes. No data is stored for this field. | ||
11.2 | date verify code last changed | .1;1 | FREE TEXT | This field is triggered by a change in the VERIFY CODE. It is used to determine when the USER must be notified to change their code. | ||
11.6 | allow ara access | .1;6 | BOOLEAN | 0:NO 1:YES | This field is for a control that is under development. | |
11.7 | ara value | .1;7 | FREE TEXT | ARA | This value is used to identify the user in non interactive connections. | |
12.1 | current degree level | 12;1 | POINTER | 771.9 | This is the current degree level upon entry into the current training program/residency at this VA medical facility. | |
12.2 | program of study | 12;2 | POINTER | 8932.2 | This is the discipline that best describes the trainee's current program of study at this VA medical facility. | |
12.3 | last training month & year | 12;3 | FREE TEXT | This is the MONTH and LAST year the trainee anticipates being in a training program at this VA medical facility. | ||
12.4 | vha training facility | 12;4 | POINTER | 4 | ||
12.5 | date hl7 trainee record built | 12;5 | DATE-TIME | AOAA | This is the date that the trainee information was built and sent to the OAA server. | |
12.6 | clinical core trainee | 12;6 | BOOLEAN | Y:YES N:NO | This field designates whether or not the person is an active Trainee. | |
12.7 | date no longer trainee | 12;7 | DATE-TIME | This is the date when a Registered Trainee is no longer to be considered an trainee. This may be at the end of a rotation period or at the end VA training experience. | ||
12.8 | start of training | 12;8 | DATE-TIME | |||
13 | nick name | .1;4 | FREE TEXT | This is a string that is used in the sign-on greeting and for mailman user lookup. | ||
14 | pac | .1;5 | FREE TEXT | This is a code to be checked before a user is allowed to get into programmer mode. | ||
14.9 | hinq employee number | .1;9 | FREE TEXT | AC | The employee number associated with HINQ passwords from the DVB should be entered here. | |
15 | prohibited times for sign-on | 0;12 | FREE TEXT | This is a pair of times within which the user will not be allowed access to the computer. They should be entered in Military format, for example 0900-1300 would prohibit signons from 9AM to 1PM each day. | ||
16 | division | 2;0 | MULTIPLE | 200.02 | This is the one or more divisions that this user may sign-on and do work for. | |
19 | delegate of | 19;1 | POINTER | 200 | This field holds the name of the person who has delegated menu manager authority to the user. The user is thus the 'delegate of' the person named here. | |
19.1 | delegation date | 19;2 | DATE-TIME | This field records the data that the user became a delegate. | ||
19.2 | delegation level | 19;3 | NUMERIC | This field records the level of delegation authority with respect to the systems manager, level zero. When the systems manager delegates authority to someone else, that person will be at level one. Levels are maintained so that lower level delegates cannot interfere with the menus of higher level delegates. | ||
19.4 | alert date/time | XQA;0 | MULTIPLE | 200.194 | This is a multiple field which is used to generate alerts to the users. The data for alerts is filed by date and time. | |
19.5 | delegated options | 19.5;0 | MULTIPLE | 200.19 | This is a sub-file of pointers to the Option File which detail those options this user may delegate to others. | |
19.6 | allowable new menu prefix | 19.6;0 | MULTIPLE | 200.196 | This subfile holds the set of namespaces available to this user in the creation of menus with delegated options. | |
19.8 | menu template | 19.8;0 | MULTIPLE | 200.198 | This multiple holds sets of predefined menus which can be envoked by the user by entering a right-square-bracket ("[") followed by a template's name. | |
20 | uci | .2;0 | MULTIPLE | 200.01 | This is the set of UCI's that this user must choose from at sign-on time. | |
20.1 | date e-sig last changed | 20;1 | FREE TEXT | A $H date of the last time the E-Sig code was changed. Triggered by a X-ref on the ELECTRONIC SIGNATURE CODE field. | ||
20.2 | signature block printed name | 20;2 | FREE TEXT | The name entered must contain the surname of the user. The name must be 2 to 40 characters in length. This field can then contain the name of the user as they wish it to be displayed with the notation that they signed the document electronically. For example: John R. Doe, M.D. or Fred A. Sample, RN. | ||
20.3 | signature block title | 20;3 | FREE TEXT | This field should contain the title of the person who is electronically signing a document. Examples of titles are Chief of Surgery, Dietician, Clinical Pharmacist, etc. This title will print next to the name of the person who signs the document. The person's name will be taken from the SIGNATURE BLOCK PRINTED NAME field. The title must be 2 to 50 characters in length. | ||
20.4 | electronic signature code | 20;4 | FREE TEXT | This field contains the encrypted code which the user types when signing documents electronically. The user's input will be compared to this field when validating his electronic signature. All electronic signature codes should be treated as confidential. | ||
28 | mail code | 5;2 | FREE TEXT | This is the mail code for the new person. | ||
29 | service/section(+) | 5;1 | POINTER | 49 | E | This is the name of the service or section for the new person. |
30 | date entered | 1;7 | DATE-TIME | This is the date on which the user was entered into the user file. It is automatically inserted into the file by the ADD USER option. | ||
31 | creator | 1;8 | POINTER | 200 | This is the name of the user who entered this user into the user file. It is automatically set by the ADD USER option. | |
31.1 | file range | 1;1 | FREE TEXT | This field limits a user to a specific range of file numbers. When creating new files, only a number within this range can be assigned to the new file. | ||
31.2 | text terminator | 1;4 | FREE TEXT | If specified, the character string in this field will be used instead of a carriage return to mark the end of word-processing text. It will be used in all VA FileMan word-processing contexts, e.g. in mail messages. It can facilitate the uploading of files from a PC environment. Note that the VA FileMan edit menu provides an option for temporarily specifying a text terminator for that edit session only. | ||
31.3 | preferred editor | 1;5 | POINTER | 1.2 | If an entry exists in this field, then whenever a user edits data in a FileMan word-processing field, they will automatically be transferred into their preferred editor. If this field is blank, then the default editor will be either the FileMan screen editor when editing within ScreenMan format, or the standard FileMan line editor in all other cases. | |
32 | accessible file | FOF;0 | MULTIPLE | 200.032 | This multiple-valued field contains the list of files the user may access. The type of access granted to the user is included for each file that appears on the list. The user may be allowed to look at records (READ access), edit existing records (WRITE access), add new record (LAYGO access), delete records (DELETE access), or modify the file structure (DATA DICTIONARY ACCESS). | |
41 | allowed to use spooler | SPL;1 | BOOLEAN | y:YES n:NO | If set to 'YES', this user will be able to use the spool device to create spool documents. | |
41.1 | multi-device despooling | SPL;2 | BOOLEAN | y:YES n:NO | If set to 'YES', the user will be able to print (despool) a spooled document to more than one device simultaneously. | |
41.2 | can make into a mail message | SPL;3 | BOOLEAN | y:YES n:NO | If set to 'YES', the document is given the status of a mail message and the user will be able to use all MailMan functions such as copying and forwarding. As a mail message, the document can no longer be manipulated with the spooler since its flag in the Spool Document File has been deleted. | |
41.97 | authorize release of npi | NPI;3 | BOOLEAN | 1:Yes | Answer 1 (Yes) if this disclosure of an individual practitioner's NPI is to a non-VA health care provider or its agent to support, or in anticipation of supporting, the submission of health care reimbursement claims by non-VA health care providers or their agents (ex., display of FEE Basis authorizations). Per Routine Use Amendment #18 to the Privacy Act of 1974 this disclosure can be made without requiring consent (Blanket Authority) from the practitioner. | |
41.98 | npi entry status | NPI;2 | SET OF CODES | N:NEEDS ENTRY E:EXEMPT D:DONE | This field is used in tracking the entry status of NPI d ata for those providers who require an NPI. The providers needing this value are identified based on data entered in the PERSON CLASS subfile which indicates providers that may be related to billing activities. The value is initially set to N or NEEDS ENTRY. It can be changed to E or EXEMPT for individuals who have been identified, but who due to administrative activities, etc., will not be involved in activities requiring billing. When the NPI value is entered, the value is changed to D or DONE. | |
41.99 | npi | NPI;1 | FREE TEXT | ANPI | Each VHA Billable Practitioner should have applied for the NPI through CMS' National Plan and Provider Enumeration System (NPPES). NPI Confirmation Letters are sent by CMS and indicate the NPI assigned. Practitioners may present their NPI Confirmation Letter as a source document to verify the accuracy of the NPI or you may contact your Local NPI Maintenance Team Leader for assistance. | |
42 | effective date/time | NPISTATUS;0 | MULTIPLE | 200.042 | ||
50.1 | key delegation level | 50;1 | NUMERIC | This a simple, numeric value which prevents removing delegated keys from someone with a lower level number. | ||
51 | keys | 51;0 | MULTIPLE | 200.051 | These are "keys" that define the characteristic(s), authorization(s), or privilege(s) of the person. | |
52 | delegated keys | 52;0 | MULTIPLE | 200.052 | This subfile contains pointers to the Key File of those keys that this person is allowed to allocate to other users. | |
53.1 | authorized to write med orders | PS;1 | BOOLEAN | 1:YES | This field is used to determin if the provider is authorized to write orders. | |
53.11 | detox/maintenance id number | PS;11 | FREE TEXT | This field holds the Detoxification/Maintenance ID number used for the substance abuse providers that is "DATA-waived". (one X, one alpha, 7 numbers) | ||
53.2 | dea# | PS;2 | FREE TEXT | PS1 | This field is used to enter the Drug Enforcement Agency (DEA) number. Enter the DEA number as two upper case letters followed by 7 digits. e.g., AA1234567. Each provider must have a unique number. | |
53.3 | va# | PS;3 | FREE TEXT | PS2 | This field is used to enter the VA number. The VA number must be unique. | |
53.4 | inactive date | PS;4 | DATE-TIME | This field is used to show the inactive date of a provider whereas they can no longer write orders. | ||
53.5 | provider class | PS;5 | POINTER | 7 | This field is used to show the providers class. | |
53.6 | provider type | PS;6 | SET OF CODES | 1:FULL TIME 2:PART TIME 3:C & A 4:FEE BASIS 5:HOUSE STAFF | This field is used to show the type of provider (staff, fee, etc.) | |
53.7 | requires cosigner | PS;7 | BOOLEAN | 1:YES | This field is used to determine if the provider needs a cosigner. | |
53.8 | usual cosigner | PS;8 | POINTER | 200 | This field is used to show the usual cosigner for the provider. | |
53.9 | remarks | PS;9 | FREE TEXT | This field is used to enter remarks and or comments about the provider. | ||
53.91 | non-va prescriber | TPB;1 | BOOLEAN | 1:YES 0:NO | The Transitional Pharmacy Care Project (TPB) introduces fields 53.91 - 53.96, to allow a NON-VA Physician to be added to the New Person file (#200), so that Outpatient Pharmacy could process medication prescribed by such physicians. A value of 1 indicates that this person is a NON-VA Physician. | |
53.92 | tax id | TPB;2 | FREE TEXT | TAX ID of the NON-VA Physician's Private Clinic, where the prescription was written. | ||
53.93 | exclusionary check performed | TPB;3 | BOOLEAN | 1:YES | Department of Health and Human Services provides an exclusionary list of Medical Practitioners (providers excluded are those who are not allowed to receive payment for government services due to various reasons). When adding NON-VA Physicians, they must be checked against this list. A value of 1 indicates that an Exclusionary Check was performed for this physician. | |
53.94 | date exclusionary list checked | TPB;4 | DATE-TIME | The date Exclusionary Check was performed. | ||
53.95 | on exclusionary list | TPB;5 | BOOLEAN | 1:YES 0:NO | Was the NON-VA Physician on the Exclusionary Check List? A value of 1 indicates that the Physician was on the Exclusionary Check. | |
53.96 | exclusionary checked by | TPB;6 | POINTER | 200 | User ID of the person who made the entry. | |
54.1 | licensing state | PS1;0 | MULTIPLE | 200.541 | This multiple contains credentialing information about a provider that is used by the state. | |
54.2 | state issuing dea number | PS2;0 | MULTIPLE | 200.55 | This mutiple contains the DEA# issued by a state in order to allow providers to write medication orders for controlled medications. | |
55.1 | schedule ii narcotic | PS3;1 | BOOLEAN | 1:Yes 0:No | This field is used to determine if the provider has privileges for Schedule II narcotic. | |
55.2 | schedule ii non-narcotic | PS3;2 | BOOLEAN | 1:Yes 0:No | This field is used to determine if the provider has privileges for Schedule II non-narcotic. | |
55.3 | schedule iii narcotic | PS3;3 | BOOLEAN | 1:Yes 0:No | This field is used to determine if the provider has privileges for Schedule III narcotic. | |
55.4 | schedule iii non-narcotic | PS3;4 | BOOLEAN | 1:Yes 0:No | This field is used to determine if the provider has privileges for Schedule III non-narcotic. | |
55.5 | schedule iv | PS3;5 | BOOLEAN | 1:Yes 0:No | This field is used to determine if the provider has privileges for Schedule IV controlled substances. | |
55.6 | schedule v | PS3;6 | BOOLEAN | 1:Yes 0:No | This field is used to determine if the provider has privileges for Schedule V controlled substances. | |
70 | staff review required | RA;1 | BOOLEAN | Y:yes N:no | This field applies to 'Interpreting Resident' personnel. If it contains a 'yes', an interpreting staff is required to review this resident's report results. | |
71 | allow verifying of others | RA;2 | BOOLEAN | y:YES n:NO | If this field is set to 'YES' and the 'ALLOW VERIFYING BY RESIDENTS' division parameter is also set to 'YES' then this resident is allowed to verify reports associated with another interpreting physician. (If both parameters are set to 'YES' the 'On-line Verifying of Reports' option will prompt the user to 'Select Interpreting Physician: ' allowing the user to select an interpreting physician other than him/herself.) If this field is set to 'NO' then this resident is only allowed to verify his/her own reports. If the division parameter 'ALLOW VERIFYING BY RESIDENT' is set to 'NO' then regardless of how this field is set, the resident will not be allowed to verify other interpreting physicians' reports. If the user is classified as Interpreting Staff, s/he will be allowed to select another interpreting physician's name and reports if this field is set to 'YES'. | |
72 | rad/nuc med classification | RAC;0 | MULTIPLE | 200.072 | This multiple field contains information about the classification assigned to Rad/Nuc Med personnel. Possible classifications are Technologist, Interpreting Resident, Interpreting Staff, and Clerk. | |
73 | rad/nuc med inactive date | RA;3 | DATE-TIME | This field contains the date that this person was inactivated as a Rad/Nuc Med user. | ||
74 | rad/nuc med location access | RAL;0 | MULTIPLE | 200.074 | This field will allow the user to access all data specific to a particular Radiology/Nuclear Medicine location. | |
101.01 | restrict patient selection | 101;1 | BOOLEAN | 0:NO 1:YES | Answer 'YES' to restrict this user to selecting only those patients associated with the list pointed to by the PATIENT SELECTION LIST field (#101.02). | |
101.02 | patient selection list | 101;2 | POINTER | 100.21 | If a value is entered into this field, the user is allowed to select only those patients associated with this OE/RR LIST. | |
101.13 | cprs tab | ORD;0 | MULTIPLE | 200.010113 | ||
125 | problem list primary view | 125;1 | FREE TEXT | This string contains the user's preferred view of the problem list. Problems are assigned a category based upon the service of the provider who entered and/or is treating the problem; a screen may then be invoked allowing a filtered view of the problem list. | ||
125.1 | problem selection list | 125;2 | POINTER | 125 | This is the user's preferred default list of problems to select from when adding to a patient's problem list. If there is a list specified here from the Problem Selection List File (#125), it will be automatically presented to the user when the "Add New Problem(s)" action is selected; otherwise, the user will simply be prompted to select a problem from the Clinical Lexicon Utility. | |
200.04 | multiple sign-on | 200;4 | SET OF CODES | 0:NOT ALLOWED 1:ALLOWED 2:Only one IP | This field, if filled in, overrides the SITE and DEVICE Files as to whether this user can sign-on to multiple terminals at the same time, or is limited to one workstation (IP), only one connection. If you select "Only one IP" be sure to put a value into the "MULTIPLE SIGN-ON LIMIT" field so users can sign-on at least once. Values are: 0 = Only one connection. 1 = Multiple connections from multiple IP's. 2 = Only one IP address. | |
200.05 | ask device type at sign-on | 200;5 | SET OF CODES | 1:ASK 0:DON'T ASK | This field controls if the user/terminal should be asked for a terminal type during sign-on. If set to YES then the system will try and get the terminal type from the terminal. If this doesn't work, then user is prompted. If set to NO then the one from the users Last Sign-on field or the device subtype will be used. | |
200.06 | auto menu | 200;6 | SET OF CODES | 0:NO MENUS GENERATED 1:YES, MENUS GENERATED | This field controls whether the user will see menus automatically displayed (as if he had typed a "?") each time a new option is presented. | |
200.07 | language | 200;7 | POINTER | .85 | The value in this field replaces the Default Language field in the Kernel Site Parameters file. It points to the Language file for the VA FileMan Dialog file. | |
200.08 | reserved | XUS;8 | FREE TEXT | Place holder, see file 3.5 #51.8 | ||
200.09 | type-ahead | 200;9 | SET OF CODES | Y:ALLOWED N:NOT ALLOWED | If type ahead is selected, the user will be able to type text ahead of what the computer is actually reading. The computer stores the keystrokes from the user, which may be confusing if the computer is slow but more efficient if the user is careful. | |
200.1 | timed read (# of seconds) | 200;10 | NUMERIC | This field, if filled in, overrides the SITE and DEVICE files as to the time this user has to respond to a timed read. Stored in DTIME. | ||
200.11 | always show secondaries | 200;11 | BOOLEAN | 1:YES | This field is a flag used by the menu system to control if the user is shown there secondary menu list with one '?' or two. | |
200.18 | auto sign-on | 200;18 | BOOLEAN | 0:No 1:Yes | This field will control if the Auto Sign-on (Single Sign-on) is enabled for use with terminal sessions. | |
200.19 | multiple sign-on limit | 200;19 | NUMERIC | This field, if filled in, overrides the SITE file. This field sets an upper limit on the number of concurrent sessions that this user can have from one IP address when the Multiple Sign-on field (#204) is set to "One IP" | ||
201 | primary menu option | 201;1 | POINTER | 19 | AP | This is the menu option that this user will be dropped into if none of the following are set: (in the order checked) Tied routine, Device primary menu. |
201.1 | primary window | 201;2 | POINTER | 19 | This is the lead or first window launched at startup. | |
201.2 | startup default | 201;3 | SET OF CODES | M:Primary Menu Option W:Primary Window | This field determines if the Primary Menu or the Primary Window is loaded at logon. | |
202 | last sign-on date/time | 1.1;1 | DATE-TIME | This field is set when a user signs on to the system. | ||
202.02 | xus logon attempt count | 1.1;2 | NUMERIC | This is used to let the user know about unsuccessful logon atempts. | ||
202.03 | xus active user | 1.1;3 | BOOLEAN | 0:No 1:Yes | If a user gets the ** MULTIPULE SIGN-ON NOT ALLOWED ** message this field can be set to NO to allow them to sign-on again. This flag is set by XUS and XUSCLEAN. | |
202.04 | entry last edit date | 1.1;4 | DATE-TIME | This field holds the date time this entry in the file was last edited. The following fields now trigger the current date to the ENTRY LAST EDIT DATE field: DISUSER (#7), ACCESS CODE (#2), and TERMINATION DATE (#9.2). | ||
202.05 | lockout user until | 1.1;5 | DATE-TIME | This field is used by the signon code to lockout users that have tried bad VERIFY codes too many times. This field holds the date/time that the user should be locked out of the system until. It is set with the current time plus the lockout time. | ||
202.1 | last option accessed | 202.1;1 | POINTER | 19 | This field holds the last option accessed by the user, when the user selects the CONTINUE option instead of HALTing. When the user logs on again, he will be able to continue directly at that option. | |
202.2 | last option main menu | 202.1;2 | FREE TEXT | This field holds an indicator of which primary or secondary menu a user was in, after selecting the CONTINUE option. It is used in con- junction with the LAST OPTION ACCESSED to resume when a user logs back on. | ||
203 | secondary menu options | 203;0 | MULTIPLE | 200.03 | Options awarded a user not on his or her primary menu option | |
203.1 | timestamp | 203.1;1 | FREE TEXT | This is the time at which this option was last modified. It is triggered automatically by the appropriate fields. If a CPU references an option which has been modified since it was last rebuilt, it triggers a rebuilding of the options. | ||
205.1 | secid | 205;1 | FREE TEXT | ASECID | Identity and Access Management SECID field used to uniquely identify a VistA user by Security ID. *** This field should never be edited directly - do not remove WRITE ACCESS! | |
205.2 | subject organization | 205;2 | FREE TEXT | Identity and Access Management SUBJECT ORGANIZATION field used to identify the Organization of an externally authenticated user (Subject). Examples: "Department of Veterans Affairs" or "Department of Defense" *** This field should never be edited directly - do not remove WRITE ACCESS! | ||
205.3 | subject organization id | 205;3 | FREE TEXT | Identity and Access Management SUBJECT ORGANIZATION ID field used to uniquely identify the Organization that is providing the identification for an externally authenticated user (Subject). The organization ID may be an Object Identifier (OID), using the urn format (that is, "urn:oid:" appended with the OID); or it may be a URL assigned to that organization. For SSOi this will be hard-coded to Department of Veterans Affairs official Home Community ID. NHIN standards specify that the web address of the Subject Organization is typically stored in this field (example: http://familymedicalclinic.org). *** This field should never be edited directly - do not remove WRITE ACCESS! | ||
205.4 | unique user id | 205;4 | FREE TEXT | Identity and Access Management UNIQUE USER ID field used to uniquely identify a user (Subject) within the Subject Organization. The combination of Subject Organization ID (OID) and Unique User ID (UID) is cross-referenced in VistA and must be unique. For VA SSOi, this will be the user SecID. Within NHIN this could be the subject of the NHIN SAML token which would contain email address of a X.509 name. *** This field should never be edited directly - do not remove WRITE ACCESS! | ||
205.5 | adupn | 205;5 | FREE TEXT | ADUPN | Identity and Access Management Active Directory User Principle Name (AD UPN) field. | |
351 | personal diagnoses list | 351;0 | MULTIPLE | 200.0351 | This is the provider's personal list of preferred diagnoses codes. | |
400 | supply employee | 400;1 | SET OF CODES | 1:WAREHOUSE 2:PPM ACCOUNTABLE OFFICER 3:PURCHASING AGENT 4:MANAGER | ||
450 | paid employee | 450;1 | POINTER | 450 | This field is a pointer to the PAID EMPLOYEE (#450) file. | |
500 | network address | 500;0 | MULTIPLE | 200.005 | This is the begining of a network address. Enter the Lastname of the user or an identifier that he is known as on the receiving system. | |
501.1 | network username | 501;1 | FREE TEXT | This is the username that is used by the Windows Active Directory. It should be 'VHA' + 3 char station ID + first 5 of last name + first character of first name. Holders of the XUMGR key can override this. | ||
501.2 | subject alternative name | 501;2 | FREE TEXT | ASAN | This is a name from the PIV card field SUBJECT ALTERNATIVE NAME also known as USER PRINCIPLE NAME. The subject alternative name extension allows identities to be bound to the subject of the certificate. These identities may be included in addition to or in place of the identity in the subject field of the certificate. Subject alternative name is defined by an Internet electronic mail address. When the subjectAltName extension contains an Internet mail address, the address MUST be stored in the rfc822Name. | |
654 | social worker ? | 654;1 | BOOLEAN | 1:YES 0:NO | This field will be used to indicate if the user is a Social Worker. It will also act as a screen for lookups. | |
654.1 | immediate supervisor | 654;2 | POINTER | 200 | ASWC | This field is used to indicate the immediate supervisor of the social worker. |
654.15 | position/title | 654;5 | SET OF CODES | 1:SW CHIEF 2:ASST. CHIEF 3:SUPERVISOR 4:SW COORDINATOR 5:SOCIAL WORKER 6:SW ASSOCIATE 7:SECRETARY 8:SW CLERK/STENO 9:STUDENT 10:VOLUNTEER 11:WOC | This field will be used to indicate the position/title of the social worker. | |
654.2 | social worker's number | 654;3 | NUMERIC | ASWD | Unique number assigned to social worker by service. Enter a number 01-999. | |
654.3 | surrogate | 654;4 | POINTER | 200 | ACSW | This field will be used to indicate a surrogate supervisor. When this field has data, the surrogate supervisor will have access to data pertaining to worker information for the surrogated supervisor. |
720 | dmms units | EC;0 | MULTIPLE | 200.72 | This multiple field contains the DMMS units to which this person has access for entering data and generating reports. | |
747.11 | appointment status | QAR12;1 | SET OF CODES | 1:FULL-TIME 2:PART-TIME 3:CONSULTING 4:CONTRACT 5:RESIDENT 6:FEE BASIS, ON STATION 7:SPECIALTY FELLOW 8:WOC 9:OTHER | Contains the Appointment Status for this person. | |
747.113 | renew date | QAR8;2 | DATE-TIME | Contains the Renewal Date for our General Privilege. | ||
747.44 | dea expiration date | QAR;9 | DATE-TIME | This field contains the expiration date for DEA #. | ||
900 | enumeration initiated | MPI;1 | DATE-TIME | This field notes the date/time the VPID enumeration attempt was initiated. | ||
901 | enumeration completed | MPI;2 | DATE-TIME | This field notes the date/time the VPID assignment was completed. | ||
902 | requires transmission | MPI;3 | BOOLEAN | Y:Yes | This field is used to note that this record was just added to this file, or that an edit was made to the fields that MPI cares about capturing and a VPID needs to be assigned or an update message needs to be sent. Fields being monitored for change are: .01 NAME .111 STREET ADDRESS 1 .112 STREET ADDRESS 2 .113 STREET ADDRESS 3 .114 CITY .115 STATE .116 ZIP CODE .131 PHONE (HOME) 4 SEX 5 DOB 9 SSN 41.99 NPI 53.2 DEA# 200.06,.01 VISITED FROM 200.06,2 DUZ AT HOME SITE | |
910.1 | badge number | ESP;1 | NUMERIC | Enter the badge number assigned to the VA police officer. | ||
910.2 | rank | ESP;2 | FREE TEXT | Enter the VA police officer's assigned rank designation, i.e., CHIEF, LIEUTENANT, PATROL OFFICER, etc. | ||
8910 | visited from | 8910;0 | MULTIPLE | 200.06 | This subfile stores the information that travels along with visitors using the CPRS Foreign Views software to look at medical data of a patient which resides on a system where the visitor may not have valid access or verify codes. When that person name and Social Security Number is put into the visited system's New Person File this multiple is updated to provide the ability to trace the visitors back to the system from which they are visiting. This field (.01) stores the number of the site where the visitor was authenticated. | |
8932.001 | provider key | COMPUTED | This Computed field gets a 1 if the user holds the provider key. It is expected that the field will be removed or changed after the Person class field conversion is completed. | |||
8932.1 | person class | USC1;0 | MULTIPLE | 200.05 | ||
8932.2 | pgyear | USC2;1 | NUMERIC | This field holds what Post Graduate year a person is. | ||
8932.21 | pgy assigned | USC2;2 | DATE-TIME | This field holds the date that the PGYear field was last edited. | ||
8932.3 | fyear | USC2;3 | NUMERIC | This field is the Fellowship year of a person. | ||
8932.31 | fy assigned | USC2;4 | DATE-TIME | This field holds the Date that the FYear field was edited. | ||
8980.16 | person file pointer(+) | 0;16 | POINTER | 16 | A16 | This field holds a pointer to the person file so there will be a way to provide a cross reference to help convert 'person file' pointers into 'new person file' pointer after the person file is removed. |
8983.11 | display help at entry to lm | LM;1 | BOOLEAN | y:YES n:NO | If set to yes, a help text will be displayed before entering the editor. This is used primarily for new users. | |
8983.12 | ask terminal type at lm entry | LM;2 | BOOLEAN | y:YES n:NO | If set to yes, the terminal type will be asked upon entry to the editor. | |
8983.13 | default terminal type for lm | LM;3 | POINTER | 3.2 | This field stores the default terminal type for a user. | |
8983.14 | display lm commands | LM;4 | BOOLEAN | y:YES n:NO | If set to yes, the list of commands will be displayed at the bottom of the screen when entering the command mode. | |
8983.15 | bright chars at exit from lm | LM;5 | BOOLEAN | y:YES n:NO | If set to yes, the terminal will be left in high intensity after exiting. | |
8983.16 | date last accessed lm wp | LM;6 | DATE-TIME | The date and time a user last accessed the LetterMan word processor document editor. | ||
8983.17 | total minutes using lm wp | LM;7 | NUMERIC | The total minutes a user has used the LetterMan word processor document editor. | ||
8983.18 | keystrokes from lm wp | LM;8 | NUMERIC | This field stores the total number of keystrokes a user has typed from the word processor document editor. | ||
8983.5 | spelling exception dictionary | LM1;0 | MULTIPLE | 200.0089831 | This field stores the exception spelling dictionary for the user. | |
8983.51 | defined formats for lm | LM2;0 | MULTIPLE | 200.0089832 | This field is used to store predefined format lines which a user can select from during editing. | |
8983.52 | defined phrases for lm | LM3;0 | MULTIPLE | 200.0089833 | This field stores predefined phrases which can be inserted into the document during editing. | |
8983.6 | lm limit wp fields to edit | LM4;0 | MULTIPLE | 200.0089834 | This field is used by the user to limit which word processing fields should be edited by LetterMan. | |
9000 | vpid | VPID;1 | FREE TEXT | AVPID | The VA Person Identification Number which was assigned by the Person Service central system. Used to uniquely identify a Person. |