STANDARD DATA DICTIONARY #357 -- ENCOUNTER FORM FILE 6/27/25 PAGE 1
STORED IN ^IBE(357, (1130 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 3.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
Warning: Do Not Re-Index this file. If this file should accidentally
be re-indexed, use the option to Recompile All Forms. This will
correct any printing problems that might occur.
This file contains the descriptive information about an encounter form. An encounter form is composed of many encounter form
blocks. Encounter form blocks contain all the data and lists that appear on the form. The data from this file along with the
other encounter form files is used to design and print encounter forms.
COMPILED CROSS-REFERENCE ROUTINE: IBDX0
DD ACCESS: @
RD ACCESS: @
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
IDENTIFIED BY: BRIEF DESCRIPTION (#.03)[R]
POINTED TO BY: DEFAULT DATA ENTRY FORM field (#.04) of the ENCOUNTER FORM PARAMETERS File (#357.09)
FORM field (#.02) of the ENCOUNTER FORM BLOCK File (#357.1)
FORM NAME field (#.21) of the FORM DEFINITION File (#357.95)
CONVERTED FORM field (#.01) of the CONVERTED FORMS File (#359)
ORIGINAL FORM field (#.02) of the CONVERTED FORMS File (#359)
FORM NAME field (#.09) of the AICS ERROR AND WARNING LOG File (#359.3)
BASIC DEFAULT ENCOUNTER FORM field (#.02) of the PRINT MANAGER CLINIC SETUP File (#409.95)
SUPPLMNTL FORM - ESTBLSHED PT. field (#.03) of the PRINT MANAGER CLINIC SETUP File (#409.95)
SUPPLMNTL FORM - FIRST VISIT field (#.04) of the PRINT MANAGER CLINIC SETUP File (#409.95)
FORM W/O PATIENT DATA field (#.05) of the PRINT MANAGER CLINIC SETUP File (#409.95)
SUPPLMNTL FORM #1 ALL PATIENTS field (#.06) of the PRINT MANAGER CLINIC SETUP File (#409.95)
RESERVED FOR FUTURE USE field (#.07) of the PRINT MANAGER CLINIC SETUP File (#409.95)
SUPPLMNTL FORM #2 ALL PATIENTS field (#.08) of the PRINT MANAGER CLINIC SETUP File (#409.95)
SUPPLMNTL FORM #3 ALL PATIENTS field (#.09) of the PRINT MANAGER CLINIC SETUP File (#409.95)
CROSS
REFERENCED BY: NAME(AB), NAME(AC), FORM TYPE ID(ADEF), NAME(AG), NAME(AT), NAME(AU), NAME(B), TOOLKIT(C), TYPE OF USE(D)
357,.01 NAME 0;1 FREE TEXT (Required)
INPUT TRANSFORM: S X=$$UP^XLFSTR(X) K:$L(X)>30!($L(X)<3) X
LAST EDITED: SEP 25, 1995
HELP-PROMPT: The form name must be 3-30 uppercase characters in length.
DESCRIPTION:
The name of the encounter form.
DELETE TEST: 1,0)= I '$G(IBDEVICE("LISTMAN")) W "...Encounter Forms can only be deleted through the",!," DELETE
UNUSED FORM action in the Encounter Form Utilities!"
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 357^B
1)= S ^IBE(357,"B",$E(X,1,30),DA)=""
2)= K ^IBE(357,"B",$E(X,1,30),DA)
CROSS-REFERENCE: 357^AT^MUMPS
1)= Q
2)= Q
This cross-reference will be used to store the text of the compiled form. The format will be
..."AT",form ien,row #)=text line. The index will be created by the 'compile' action of the
encounter form utilities - it is optional. The option IBDF RECOMPILE ALL FORMS can be used to
recompiled all forms.
CROSS-REFERENCE: 357^AC^MUMPS
1)= Q
2)= Q
This cross-reference will be used to store the special controls needed (bold on, bold off, etc.) to
print the compiled form. The format will be ..."AC",form ien,row #,column # )=controls. The index
will be created by the 'compile' action of the encounter form utilities - it is optional. The
option IBDF RECOMPILE ALL FORMS can be used to recompiled all forms.
CROSS-REFERENCE: 357^AU^MUMPS
1)= Q
2)= Q
This cross-reference will be used to store the underlining of the compiled form. The format will be
...,"AU",form ien,row #)=underlining . The index will be created by the 'compile' action of the
encounter form utilities - it is optional. The option IBDF RECOMPILE ALL FORMS can be used to
recompiled all forms.
CROSS-REFERENCE: 357^AG^MUMPS
1)= Q
2)= Q
This cross-reference will be used to store strings of graphics characters (TLC,TRC, etc.) needed
for the compiled form. The format will be ..."AG",form ien,row #,column # )=graphics string . The
index will be created by the 'compile' action of the encounter form utilities - it is optional. The
option IBDF RECOMPILE ALL FORMS can be used to recompiled all forms.
CROSS-REFERENCE: 357^AB^MUMPS
1)= Q
2)= Q
This cross-reference will be used to store the boxes needed for the compiled forms. The format will
be ..."AB",form ien,row #,column #, Block ien)= box width^box height. The index will be created by
the 'compile' action of the encounter form utilities. The option IBDF RECOMPILE ALL FORMS can be
used to recompiled all forms.
357,.02 SIMPLEX/DUPLEX 0;2 SET
'0' FOR SIMPLEX;
'1' FOR DUPLEX,LONG-EDGE BINDING;
'2' FOR DUPLEX,SHORT-EDGE BINDING;
LAST EDITED: FEB 07, 2012
HELP-PROMPT: SIMPLEX means one-sided, DUPLEX means two-sided. SHORT-EDGE BINDING is for attaching forms by the
top, LONG-EDGE BINDING is for attaching forms along the side.
DESCRIPTION: Allows forms to be printed either one-sided or two-sided.
SIMPLEX - refers to a form that will print on one side of the paper. DUPLEX - refers to a form
that will print on both sides of the paper.
.SHORT-EDGE BINDING - prints from top to bottom on the front page and
prints from bottom to top on the back page.
.LONG-EDGE BINDING - prints from top to bottom on the front page and
prints from top to bottom on the back page.
357,.03 BRIEF DESCRIPTION 0;3 FREE TEXT (Required)
BRIEF DESCRIPTION OF FORM'S USE & CONTENT
INPUT TRANSFORM: K:$L(X)>80!($L(X)<1) X
LAST EDITED: MAR 09, 1994
HELP-PROMPT: Enter a brief description of the intended use of the form or its contents.
DESCRIPTION: A brief description of the contents of the form and its intended use. This description will be
displayed to the user.
357,.04 TYPE OF USE 0;4 SET (Required)
'0' FOR RESERVED FOR UTILITY;
'1' FOR OUTPATIENT ENCOUNTER FORM;
LAST EDITED: AUG 25, 1993
HELP-PROMPT: How will the form be used?
DESCRIPTION: This field will be used to categorize forms by type of use. It is possible that the form generator
that is part of the Encounter Form Utilities may be used to create forms other than encounter
forms. The utilities use a couple of forms (WORKCOPY, TOOL KIT), TYPE OF USE is RESERVED FOR
UTILITY, that are not real forms.
TECHNICAL DESCR:
SCREEN: S DIC("S")="I Y'=0"
EXPLANATION: Does not allow users to choose RESERVED FOR UTILITY
CROSS-REFERENCE: 357^D
1)= S ^IBE(357,"D",$E(X,1,30),DA)=""
2)= K ^IBE(357,"D",$E(X,1,30),DA)
Used to find forms of a particular type.
357,.05 COMPILED? 0;5 SET
'0' FOR NO;
'1' FOR YES;
'F' FOR COMPILATION FAILED;
LAST EDITED: OCT 03, 1995
HELP-PROMPT: Enter YES if the form is compiled, NO otherwise.
DESCRIPTION: This indicates whether a compiled version of the form exists. The compiled version is much faster
to print.
357,.06 USE ICR? 0;6 SET
Should ICR be used to automatically read hand print on this form?
'0' FOR NO;
'1' FOR YES;
LAST EDITED: APR 21, 1995
HELP-PROMPT: ICR is 'intelligent character recognition', used to automatically read hand print. Answer YES only
if your scanning software has ICR and you want to use it for this form.
DESCRIPTION: If this field is set to 'YES', the computer will attempt to read hand- written print; for
example, ICD diagnostic codes hand-written in an 'Other Diagnosis' encounter form block.
357,.07 TOOLKIT 0;7 SET (Required)
SHOULD THIS FORM BE PART OF THE TOOLKIT?
'0' FOR NO;
'1' FOR YES;
LAST EDITED: MAR 06, 1995
HELP-PROMPT: Is this form part of the toolkit?
DESCRIPTION: This field, if set to YES, means that the form can not be deleted and can not be added to a clinic
setup.
CROSS-REFERENCE: 357^C
1)= S ^IBE(357,"C",$E(X,1,30),DA)=""
2)= K ^IBE(357,"C",$E(X,1,30),DA)
Used to find all of the tool kit forms.
357,.09 RIGHT MARGIN 0;9 NUMBER (Required)
FORM'S RIGHT MARGIN (WIDTH IN CHARACTERS)
INPUT TRANSFORM: K:+X'=X!(X>200)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: JUL 11, 1994
DESCRIPTION:
The number of characters wide the form is.
EXECUTABLE HELP: W !,"How many columns (characters) wide should the form be?"
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
357,.1 PAGE LENGTH 0;10 NUMBER (Required)
FORM'S PAGE LENGTH (IN LINES)
INPUT TRANSFORM: K:+X'=X!(X>300)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: APR 20, 1993
HELP-PROMPT: How many lines should each page have?
DESCRIPTION:
This is the number of usable lines on the page.
357,.11 NUMBER OF PAGES 0;11 NUMBER (Required)
INPUT TRANSFORM: K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: JUN 02, 1993
HELP-PROMPT: How many pages should the encounter form have?
DESCRIPTION: The encounter form may have multiple pages.
This field is to indicate the total number of pages for the entire form.
357,.12 SCANNED/MANUAL DATA ENTRY 0;12 SET
'0' FOR NO;
'1' FOR YES;
LAST EDITED: MAY 23, 1997
HELP-PROMPT: Answer YES if it is planned that this form may at some time in the future be used with scanning.
DESCRIPTION: CREATING SCANNABLE FORMS
Each form created for scanning should contain at a minimum the following data elements:
1) Primary provider. 2) At least 1 procedure, usually the Evaluation and Management (EM) code. 3)
Reason for visit (diagnosis).
These steps must be taken during form design for each form type that is to be scanned:
1) The form field SCANNABLE? should be set to YES. 2) The form field USE ICR? (prompted as 'Should
ICR be used to auto-
matically read hand print on this form?') should be set to YES. It is
anticipated that the scanning software will include intelligent recog-
nition software (ICR) for reading hand print in future package releases. 3) A form can be
designed with scannable and non-scannable pages. Each page
to be scanned should have the SCANNABLE? field set to YES. For each page
selected in the PAGE INFORMATION multiple, the SCANNABLE? field is auto-
matically set to YES. 4) Selection lists should use bubbles as marking areas. The selection
rule
should be appropriate to the type of data. The selection rule will be
enforced by the scanning software. For example, if a diagnosis list has
the selection rule AT LEAST ONE, the form will be flagged as invalid if
no diagnosis is selected. Also, the proper data qualifier, if one
applies, should be entered. An example illustrating the use of data
qualifiers is a selection list for diagnosis codes where there is a sub
column for selecting the primary diagnosis and another sub column for
selecting secondary diagnoses. At the bottom of the selection list an
area can be created to contain 'other' codes not found on the list. 5) All hand print to be
scanned must use hand print fields, except for the
'other' feature of selection lists. 6) The PACKAGE INTERFACE file (357.6) contains the complete
list of data
that is currently scannable.
There are several forms that are included with AICS v3.0 that are scan- nable. There are also a
number of tool kit blocks included that were designed to be scannable. The best approach to
creating the forms needed by your facility is to first develop a few basic forms, without clinic
specific coding, suited to your site's needs. Those forms can then be placed in your tool kit and
used as the basis for developing the rest of your forms.
---------------------------------------------------------------------------
If ANY page of the form is to be scanned into VISTA, enter YES.
.Individual pages of the form to be scanned are selected later
at the PAGE INFORMATION prompt.
If NONE of the form pages are to be scanned into VISTA, enter NO.
357,.13 FORM TYPE ID 0;13 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>999999999)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: OCT 03, 1995
HELP-PROMPT: Type a Number between 1 and 999999999, 0 Decimal Digits
DESCRIPTION: This is the current form definition entry associated with this form. Each time the form is edited
and printed or recompiled and printed a new form definition is created leaving the old definition
for use with existing forms (its used in scanning).
CROSS-REFERENCE: 357^ADEF
1)= S ^IBE(357,"ADEF",$E(X,1,30),DA)=""
2)= K ^IBE(357,"ADEF",$E(X,1,30),DA)
This cross reference can be used to find the current form definition in file 357.95 for this form.
357,.14 PAPER SIZE 0;14 SET
'1' FOR LETTER (8 1/2 x 11);
LAST EDITED: JUN 14, 1994
HELP-PROMPT: What size paper should be used?
357,.15 ORIENTATION 0;15 SET
'p' FOR PORTRAIT;
LAST EDITED: JUN 14, 1994
HELP-PROMPT: How should the form be oriented?
357,.16 TEXT SIZE 0;16 SET (Required)
'1' FOR 133 COLUMNS x 80 LINES;
'2' FOR 96 COLUMNS x 72 LINES;
'3' FOR 80 COLUMNS x 60 LINES;
LAST EDITED: AUG 14, 1995
HELP-PROMPT: This choice will determine the size of the print and how much text will fit on the form.
357,.17 VERSION 0;17 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>99)!(X<0)!(X?.E1"."2N.N) X
LAST EDITED: OCT 24, 1995
HELP-PROMPT: Type a Number between 0 and 99, 1 Decimal Digit
DESCRIPTION: This is the version of AICS that created the form. This was implemented in version 2.1. All forms
with a null entry can be treated as version 2.0 forms.
357,2 PAGE INFORMATION 2;0 Multiple #357.02
DESCRIPTION: Enter all pages that will have scannable data on them.
IDENTIFIED BY:
"WRITE": N DIERR,IBDMSG D EN^DDIOL($$EXTERNAL^DILFD(357.02,.02,"",$P(^(0),U,2),"IBDMSG"),"","?0")
357.02,.01 PAGE INFORMATION 0;1 NUMBER (Multiply asked)
INPUT TRANSFORM: K:+X'=X!(X>8)!(X<1)!(X?.E1"."1N.N)!'$P(^IBE(357,D0,0),U,12)!(X>$P(^IBE(357,D0,0),U,11)) X
LAST EDITED: JUL 17, 1995
HELP-PROMPT: Enter the pages that should be scanned.
DESCRIPTION: Enter all pages that will have scannable data on them.
For example, if a form has a total of 2 pages, and page #1 is to be scanned and page #2 is not
scannable; at the PAGE INFORMATION prompt enter 1. When this form is printed, a small black box
will print at the bottom of page #1 to indicate that it is a scan- nable page.
At the time a form is scanned, the data from each scanned page is stored in the Encounter Form
Tracking file (357.96). If the form has multiple scannable pages, and the software has not
received all pages for the form, it will display a message to the user indicating that it is
awaiting additional pages. Once all pages have been scanned in, the data is sent to update the
PCE files.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 357.02^B
1)= S ^IBE(357,DA(1),2,"B",$E(X,1,30),DA)=""
2)= K ^IBE(357,DA(1),2,"B",$E(X,1,30),DA)
357.02,.02 SCANNABLE? 0;2 SET
'0' FOR NO, NOT SCANNABLE;
'1' FOR YES, PAGE SCANNABLE;
LAST EDITED: SEP 16, 1996
HELP-PROMPT: Is this page meant to be scanned?
DESCRIPTION:
Enter Yes if this page should be scanned or no if this page does not have any scannable parts.
357,3 CODING SYSTEM UPDATES 3;0 POINTER Multiple #357.03 (Add New Entry without Asking)
LAST EDITED: FEB 07, 2012
DESCRIPTION: This subfile stores tracking information on encounter form blocks' updates related to a specific
coding system.
357.03,.01 CODING SYSTEM 0;1 POINTER TO ICD CODING SYSTEMS FILE (#80.4)
LAST EDITED: FEB 16, 2012
HELP-PROMPT: Select the coding system for which the encounter form was updated.
DESCRIPTION:
This field stores the coding system identifier for which the block of the form has been updated.
CROSS-REFERENCE: 357.03^B
1)= S ^IBE(357,DA(1),3,"B",$E(X,1,30),DA)=""
2)= K ^IBE(357,DA(1),3,"B",$E(X,1,30),DA)
357.03,.02 UPDATE STATUS 0;2 SET
'C' FOR COMPLETE;
'R' FOR REVIEW;
LAST EDITED: FEB 16, 2012
HELP-PROMPT: Enter the coding system update status.
DESCRIPTION: This field will be set to 'C' if the migration to the coding system specified in the field #.01
of this multiple entry has been marked as completed and 'R' if changes were reviewed. To change
back to incomplete, delete its value.
357.03,.03 DATE LAST EDITED 0;3 DATE
INPUT TRANSFORM: S %DT="ETX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: FEB 16, 2012
HELP-PROMPT: Enter date and time when the block for the coding system in the form was last edited.
DESCRIPTION: This field stores the date and time when the block for the coding system in the form was last
edited - including adding, modifying or deleting blocks with the codes.
357.03,.04 CHANGES MADE BY 0;4 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: FEB 07, 2012
HELP-PROMPT: Select the person who last made changes to blocks for the coding system in the form.
DESCRIPTION:
The person who last updated ICD blocks of the form.
FILES POINTED TO FIELDS
ICD CODING SYSTEMS (#80.4) CODING SYSTEM UPDATES:CODING SYSTEM (#.01)
NEW PERSON (#200) CODING SYSTEM UPDATES:CHANGES MADE BY (#.04)
INPUT TEMPLATE(S):
IBDF EDIT NEW FORM NOV 03, 1995@13:43 USER #0
Used to edit a new form.
IBDF EDIT OLD OR COPIED FORM AUG 14, 1995@09:09 USER #0
Used to edit an existing form.
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):