| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | name(+) | 0;1 | FREE TEXT | B | The name of the encounter form. | |
| .02 | simplex/duplex | 0;2 | SET OF CODES | 0:SIMPLEX 1:DUPLEX,LONG-EDGE BINDING 2:DUPLEX,SHORT-EDGE BINDING | 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. | |
| .03 | brief description(+) | 0;3 | FREE TEXT | A brief description of the contents of the form and its intended use. This description will be displayed to the user. | ||
| .04 | type of use(+) | 0;4 | SET OF CODES | 0:RESERVED FOR UTILITY 1:OUTPATIENT ENCOUNTER FORM | D | 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. |
| .05 | compiled? | 0;5 | SET OF CODES | 0:NO 1:YES F:COMPILATION FAILED | This indicates whether a compiled version of the form exists. The compiled version is much faster to print. | |
| .06 | use icr? | 0;6 | BOOLEAN | 0:NO 1:YES | 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. | |
| .07 | toolkit(+) | 0;7 | BOOLEAN | 0:NO 1:YES | C | This field, if set to YES, means that the form can not be deleted and can not be added to a clinic setup. |
| .09 | right margin(+) | 0;9 | NUMERIC | The number of characters wide the form is. | ||
| .1 | page length(+) | 0;10 | NUMERIC | This is the number of usable lines on the page. | ||
| .11 | number of pages(+) | 0;11 | NUMERIC | The encounter form may have multiple pages. This field is to indicate the total number of pages for the entire form. | ||
| .12 | scanned/manual data entry | 0;12 | BOOLEAN | 0:NO 1:YES | 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. | |
| .13 | form type id | 0;13 | NUMERIC | ADEF | 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). | |
| .14 | paper size | 0;14 | SET OF CODES | 1:LETTER (8 1/2 x 11) | ||
| .15 | orientation | 0;15 | SET OF CODES | p:PORTRAIT | ||
| .16 | text size(+) | 0;16 | SET OF CODES | 1:133 COLUMNS x 80 LINES 2:96 COLUMNS x 72 LINES 3:80 COLUMNS x 60 LINES | ||
| .17 | version | 0;17 | NUMERIC | 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. | ||
| 2 | page information | 2;0 | MULTIPLE | 357.02 | Enter all pages that will have scannable data on them. | |
| 3 | coding system updates | 3;0 | MULTIPLE | 357.03 | This subfile stores tracking information on encounter form blocks' updates related to a specific coding system. |