Global: ^IBE(357

The name of the encounter form.

1)= S ^IBE(357,"B",$E(X,1,30),DA)=""

2)= K ^IBE(357,"B",$E(X,1,30),DA)

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.

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.

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.

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.

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.

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.

A brief description of the contents of the form and its intended use. This description will be displayed to the user.

couple of forms (WORKCOPY, TOOL KIT), TYPE OF USE is RESERVED FOR UTILITY, that are not real forms.

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.

This indicates whether a compiled version of the form exists. The compiled version is much faster to print.

This field, if set to YES, means that the form can not be deleted and can not be added to a clinic setup.

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.

The number of characters wide the form is.

This is the number of usable lines on the page.

This field is to indicate the total number of pages for the entire form.

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 v2.1 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 DHCP, 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 DHCP, enter NO.

forms (its used in scanning).

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.

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.

"WRITE":    N DIERR,IBDMSG D EN^DDIOL($$EXTERNAL^DILFD(357.02,.02,"",$P(^(0),U,2),"IBDMSG"),"","?0")