Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables  | All
Print Page as PDF
Global: ^IBE(357.6

Package: Automated Information Collection System

Global: ^IBE(357.6


Information

FileMan FileNo FileMan Filename Package
357.6 PACKAGE INTERFACE Automated Information Collection System

Description

Directly Accessed By Routines, Total: 71

Package Total Routines
Automated Information Collection System 70 DATA DESCRIPTION    DYNAMIC LIST ITEMS    IBD3P63    IBDECLN1    IBDF18A1    IBDF18E1    IBDF4    IBDF4C
IBDF5    IBDF5C    IBDFDE1    IBDFDE2    IBDFDE3    IBDFDE5    IBDFDE9    IBDFGRP
IBDFQSL1    IBDFRPC2    IBDFRPC4    IBDFU1B    IBDFU5    IBDFU91    IBDFUTL3    IBDFUTL5
OVERFLOW DATA    ^IBE(357.2    IBDFU9    IBDFUTL    IBDXI2    IBDXI21    IBDY2117    IBDY340
PROTECTED LOCAL VARIABLES    ^IBE(357.6    REQUIRED LOCAL VARIABLES    ^SDAUDIT    ALLOWABLE QUALIFIERS    IBD3KPT    IBD3P63A    IBDECLN
IBDF14A    IBDF17    IBDF18    IBDF18A    IBDF4A    IBDF5B    IBDF5D    IBDF6A
IBDF7    IBDF9A    IBDF9A3    IBDF9B    IBDF9B1    IBDFBKS2    IBDFBKS3    IBDFC2B
IBDFDE    IBDFDE21    IBDFDE41    IBDFFV3    IBDFRPC    IBDFRPC1    IBDFU1    IBDFU3
IBDFUTL1    IBDFUTL2    IBDX24    IBDXI25    IBDY214    IBDY338    
PCE Patient Care Encounter 1 PXIPOST    

Accessed By FileMan Db Calls, Total: 7

Package Total Routines
Automated Information Collection System 7 IBD3KPT    IBD3P63    IBDF11    IBDF16    IBDF9A    IBDF9B    IBDFUTL    

Pointed To By FileMan Files, Total: 12

Package Total FileMan Files
Automated Information Collection System 12 FORM DEFINITION(#357.95)[#357.951(.03), #357.952(.04)]    ENCOUNTER FORM TRACKING(#357.96)[#357.961(.03), #357.962(.03)]    AICS ERROR AND WARNING LOG(#359.3)[.1]    ENCOUNTER FORM BLOCK(#357.1)[#357.13(.03), #357.14(.04)]    SELECTION LIST(#357.2)[.11]    DATA FIELD(#357.5)[.03]    PACKAGE INTERFACE(#357.6)[.13]    MULTIPLE CHOICE FIELD(#357.93)[.06]    IMP/EXP HAND PRINT FIELD(#358.94)[.06]    HAND PRINT FIELD(#359.94)[.06]    PRINT MANAGER CLINIC SETUP(#409.95)[#409.9501(.01), #409.9502(.01)]    PRINT MANAGER DIVISION SETUP(#409.96)[#409.961(.01)]    

Pointer To FileMan Files, Total: 6

Package Total FileMan Files
Automated Information Collection System 4 AICS DATA QUALIFIERS(#357.98)[13, #357.613(.01)]    PACKAGE INTERFACE(#357.6)[.13]    IMP/EXP AICS DATA ELEMENTS(#358.99)[13, #357.613(.01)]    AICS DATA ELEMENTS(#359.1)[13, 16.2, 16.6, #357.613(.01)]    
DRG Grouper 1 ICD CODING SYSTEMS(#80.4)[.22]    
Health Summary 1 HEALTH SUMMARY TYPE(#142)[.11]    

Fields, Total: 58

Field # Name Loc Type Details
.01 NAME 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  JUL 11, 1997
  • HELP-PROMPT:  The name should be prefixed with the namespace of the package that provides the data.
  • DESCRIPTION:  
    The name of the Package Interface. The name should be preceded with the namespace of the package.
  • TECHNICAL DESCR:  
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  357.6^B
    1)= S ^IBE(357.6,"B",$E(X,1,30),DA)=""
    2)= K ^IBE(357.6,"B",$E(X,1,30),DA)
  • CROSS-REFERENCE:  357.6^E^MUMPS
    1)= N IBDXE S IBDXE=$E(X,$F(X," "),40) S:$A(IBDXE)<33 IBDXE=X S ^IBE(357.6,"E",IBDXE,DA)=""
    2)= N IBDXE S IBDXE=$E(X,$F(X," "),40) S:$A(IBDXE)<33 IBDXE=X K ^IBE(357.6,"E",IBDXE,DA)
    For package interfaces that are output routines the name has the custodial package's name space as a prefix. This cross-reference removes that prefix. It is used to improve the display of output routines for the user.
.02 ENTRY POINT 0;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<1) X
  • LAST EDITED:  OCT 18, 1994
  • HELP-PROMPT:  What entry point into the routine does this package interface use?
  • DESCRIPTION:  
    The entry point in the routine that should be called.
.03 ROUTINE 0;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<1) X
  • LAST EDITED:  NOV 25, 1992
  • HELP-PROMPT:  What routine does this package interface use?
  • DESCRIPTION:  
    The routine that should be called.
.04 CUSTODIAL PACKAGE 0;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3) X
  • LAST EDITED:  OCT 17, 1995
  • HELP-PROMPT:  Answer must be 3-30 characters in length.
  • DESCRIPTION:  
    This is a free text pointer to the package file. It serves only to document the custodial package of the data.
  • CROSS-REFERENCE:  357.6^C
    1)= S ^IBE(357.6,"C",$E(X,1,30),DA)=""
    2)= K ^IBE(357.6,"C",$E(X,1,30),DA)
.05 VARIABLE DATA? 0;5 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  NOV 24, 1993
  • HELP-PROMPT:  Enter YES if the data returned is variable, NO if the data is always the same.
  • DESCRIPTION:  
    This field is used in the batch printing of encounter forms. The purpose is to avoid recomputing fields whose data does not change from patient to patient.
.06 ACTION TYPE 0;6 SET
************************REQUIRED FIELD************************
  • '1' FOR INPUT;
  • '2' FOR DISPLAY;
  • '3' FOR SELECTION;
  • '4' FOR PRINT REPORT;

  • LAST EDITED:  AUG 25, 1995
  • HELP-PROMPT:  Is this interface for inputting data, displaying data to a form, for creating lists that will appear on a form, or for printing reports?
  • DESCRIPTION:  Enter 1 for INPUT if the interface accepts data input from the user
    and transmits the data to the appropriate package. Enter 2 for DISPLAY if the interface retrieves data for display to a form. Enter 3 for SELECTION if the interface is for building a list to display
    to a form. Enter 4 if the interface is for printing a report.
    If the ACTION TYPE is SELECTION then the data type must be a record and the first piece must be the ID use to uniquely identify the selection.
  • TECHNICAL DESCR:  
.07 DATA TYPE 0;7 SET
  • '1' FOR SINGLE VALUE;
  • '2' FOR RECORD;
  • '3' FOR LIST OF SINGLE VALUES;
  • '4' FOR LIST OF RECORDS;
  • '5' FOR WORD PROCESSING;

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  What format will the data be in?
  • DESCRIPTION:  Only applies to selection or display interfaces, both of which retrieve data for display to a form. It is the type of format the data should be in.
    A single value is a string without pieces. A record is a set of strings concatenated together with "^" separating the pieces. A list is an indefinite number of values, each numbered, each containing the same type of
    information. A word processing data type will be in FM format. If the ACTION TYPE is SELECTION then the data type must be record.
.08 PRINT COMPLETE 0;8 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAY 07, 1993
  • HELP-PROMPT:  If there is insufficient room on the form to print the data, should it be re-printed in full on a separate page?
  • DESCRIPTION:  
    This field is used to determine what should happen if the data does not fit in the space allocated to it on the form. If answered YES the data will be printed on another page.
.09 AVAILABLE? (Y/N) 0;9 SET
************************REQUIRED FIELD************************
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  DEC 13, 1992
  • HELP-PROMPT:  Is this package interface now available for use?
  • DESCRIPTION:  
    This field should be set to YES if the interface is available, NO if it is not available. Interfaces that are not available are not called.
.1 HEALTH SUMMARY? 0;10 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  JUN 16, 1993
  • HELP-PROMPT:  Are you requesting a HEALTH SUMMARY to print?
  • DESCRIPTION:  This field will determine how to go about printing the report or form. It applies only to Package Interfaces of ACTION TYPE = PRINT REPORT. Health Summaries use the field HEALTH SUMMARY to determine the type of Health
    Summary to print. The process of printing Health Summaries dos not use the fields ENTRY POINT or ROUTINE, since all Health Summaries are printed in the same way.
.11 TYPE OF HEALTH SUMMARY 0;11 POINTER TO HEALTH SUMMARY TYPE FILE (#142) HEALTH SUMMARY TYPE(#142)

  • INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U)'=""GMTS HS ADHOC OPTION""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  JUN 17, 1993
  • HELP-PROMPT:  Which Health Summary do you want printed?
  • DESCRIPTION:  
    This identifies the Health Summary that should be printed when this Package Interface is invoked. It should be null unless the HEALTH SUMMARY? field #.1 is coded YES.
  • SCREEN:  S DIC("S")="I $P(^(0),U)'=""GMTS HS ADHOC OPTION"""
  • EXPLANATION:  EXCLUDES AD HOC HEALTH SUMMARIES
.12 TOOLKIT MEMBER? 0;12 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  JUL 11, 1995
  • HELP-PROMPT:  Enter YES if this PACKAGE INTERFACE was added by the package developers as part of the toolkit, enter NO otherwise.
  • DESCRIPTION:  
    Package Interfaces that are developed for national use will be documented as being part of the toolkit.
.13 PACKAGE INTERFACE FOR INPUT 0;13 POINTER TO PACKAGE INTERFACE FILE (#357.6) PACKAGE INTERFACE(#357.6)

  • INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U,6)=1,$P(^(0),U,9)=1,$P(^(0),U,16)[""S""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  AUG 25, 1995
  • HELP-PROMPT:  What interface should be used for inputting data entered on the selection list?
  • DESCRIPTION:  
    Used to map scanned data to DHCP.
  • SCREEN:  S DIC("S")="I $P(^(0),U,6)=1,$P(^(0),U,9)=1,$P(^(0),U,16)[""S"""
  • EXPLANATION:  Must be an available interfaces for accepting input from selection lists.
.14 DYNAMIC SELECTIONS 0;14 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  DEC 21, 1994
  • HELP-PROMPT:  Only for selection routines. Enter YES if the Package Interface builds the selection list each time the form is printed.
  • DESCRIPTION:  
    This is used to indicate whether the interface is used to build selection lists at print time.
.15 DO NOT USE DFN AS A SUBSCRIPT 0;15 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 13, 1995
  • HELP-PROMPT:  If the patient DFN should not be used as a subscript when passing data enter YES.
  • DESCRIPTION:  Originally, the patient DFN was used as a subscript when returning data for Package Interfaces of type output, but not for other types of interfaces. It is no longer necessary for any new Package Interface to use DFN as a
    subscript, but, to maintain compatibilty, output routines must set this field to YES if DFN is not to be used as a subscript. This field has no effect on other types of interfaces.
  • SCREEN:  S DIC("S")="I (Y=1)!($P(^IBE(357.6,DA,0),U,6)=2)"
  • EXPLANATION:  If the action type is not OUTPUT ROUTINE then this field should not be set to NO.
.16 ALLOWED OBJECT USE 0;16 FREE TEXT

  • INPUT TRANSFORM:  S X=$$UPPER^VALM1(X) K:$L(X)>4!("SMHP"'[$E(X,1))!("SMHP"'[$E(X,2))!("SMHP"'[$E(X,3))!("SMHP"'[$E(X,4)) X
  • LAST EDITED:  SEP 13, 1995
  • DESCRIPTION:  This field applies only to package interfaces for input and is used to determine which package interfaces a particular type of form object may point to. Some combinations don't make sense. For example, it would not make
    sense to allow a multiple choice question to point to vitals, which is used to input data such as temperature and blood pressure.
  • EXECUTABLE HELP:  D HELP7^IBDFU5A
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
.17 ASK FOR ADDITIONAL NARRATIVE 0;17 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  DEC 07, 1995
  • DESCRIPTION:  Enter whether users should be prompt for specifying the provider narrative that will be sent to PCE (and problem list) when creating a selection list. If this is answered no and the narrative is sent to PCE then the text
    as it appears on the form will be used as the provider narrative.
    Generally only dianosis and clinical lexicon entries will want this field set to Yes.
.18 ASK FOR CLINICAL LEXICON 0;18 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  FEB 05, 1996
  • HELP-PROMPT:  Enter 'Yes' if you want to map entries from this interface to the clinical lexicon
  • DESCRIPTION:  If this field is answered 'Yes' then users who are editing or creating selection lists based on this interface will be asked to map each entry (thought it is optional) to a clinical lexicon entry. This is highly
    recommended for user who are scanning diagnosis entries and trying to add entries to the Patients Problem list.
    The primary purpose of this field is to allow sites who have built selection lists using the ICD9 Diagnosis file to map each entry to the clinical lexicon. The Problem List EP has recommended that each problem added to
    the problem list be associated with a clinical lexicon entry.
.19 DQ REQUIRED 0;19 SET
  • '1' FOR YES;

  • LAST EDITED:  FEB 12, 1996
  • DESCRIPTION:  
    Field used to determine if a data qualifier is required for this input interface.
.2 ASK FOR CLINICAL REMINDERS 0;20 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  OCT 02, 1997
  • HELP-PROMPT:  If this package interface is for display of clinical reminders answer yes, otherwise answer no.
  • DESCRIPTION:  
    If this package interface is for display of clinical reminders answer yes, otherwise answer no.
.21 ASK FOR CPT MODIFIERS? 0;21 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAY 24, 1999
  • HELP-PROMPT:  If this package interface is to prompt for CPT Modifiers, answer yes, otherwise answer no.
  • DESCRIPTION:  
    ASK FOR CPT MODIFIERS field will be used when selecting CPT codes. If answered "YES" and data is a procedure, CPT Modifiers should be asked during Forms Design and Manual Data Entry.
.22 ICD CODING SYSTEM 0;22 POINTER TO ICD CODING SYSTEMS FILE (#80.4) ICD CODING SYSTEMS(#80.4)

  • LAST EDITED:  FEB 06, 2012
  • HELP-PROMPT:  Select ICD coding system to use with the package interface.
  • DESCRIPTION:  
    This field is used to indicate the ICD coding system that should be used for the package interface.
1 DESCRIPTION 1;0 WORD-PROCESSING #357.61

  • DESCRIPTION:  
    Should describe the data being exchanged by the package interface.
  • LAST EDITED:  FEB 10, 1993
  • HELP-PROMPT:  Enter a description of the data being exchanged.
  • DESCRIPTION:  
    This should describe the data being exchanged b the package interface.
2.01 PIECE 1 DESCRIPTIVE NAME 2;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3) X
  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Answer must be 3-30 characters in length.
  • DESCRIPTION:  
    Should be a descriptive name of the first field in the record returned by the interface.
2.02 PIECE 1 MAXIMUM LENGTH 2;2 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>210)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Type a Number between 0 and 210, 0 Decimal Digits
  • DESCRIPTION:  
    The maximum length of the first field of the record returned by the interface.
2.16 PIECE 1 RECOMMENDED HEADER 2;16 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>20!($L(X)<1) X
  • LAST EDITED:  APR 17, 1995
  • HELP-PROMPT:  Answer must be 1-20 characters in length.
  • DESCRIPTION:  
    The recommended header will be used as the default when designing a form.
2.17 IS PIECE 1 DISPLAYABLE? 2;17 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  AUG 10, 1993
  • HELP-PROMPT:  The first piece of the returned record is reserved for the unique id of the selection. Enter no if it should not be displayed, for example, if it is a pointer.
  • DESCRIPTION:  
    This is used only for selection type interfaces. If NO, then the value can not be displayed to the encounter form. The first piece must contain the unique id of the selection.
2.18 EXPORT SELECTIONS/CHOICES? 2;18 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  AUG 25, 1995
  • HELP-PROMPT:  Enter NO if the ID returned by the PACKAGE INTERFACE is not constant between sites, for example, if it is a pointer. Otherwise answer YES.
  • DESCRIPTION:  
    Applies to selection and input routines. Determines whether selections appearing on selection lists and choices in a multiple choice field will be exported along with the form that they appear on. The import/export utility
    will not resolve pointers, so if the id used by the package interface is a pointer that differs between sites this field should contain NO.
3 USER LOOKUP 3;1 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>240!($L(X)<1) X
  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter words separated with spaces. They will be indexed to assist in lookup.
  • DESCRIPTION:  
    This field is used to create a KWIC index for this file. The purpose is to assist the user in locating the package interface he needs to display a particular item of data to a form.
  • EXECUTABLE HELP:  D LOOKUP^IBDF16
  • CROSS-REFERENCE:  357.6^D^KWIC
    1)= S %1=1 F %=1:1:$L(X)+1 S I=$E(X,%) I "(,.?! '-/&:;)"[I S I=$E($E(X,%1,%-1),1,30),%1=%+1 I $L(I)>2,^DD("KWIC")'[I S ^IBE(357.6,"D",I,DA)=""
    2)= S %1=1 F %=1:1:$L(X)+1 S I=$E(X,%) I "(,.?! '-/&:;)"[I S I=$E($E(X,%1,%-1),1,30),%1=%+1 I $L(I)>2 K ^IBE(357.6,"D",I,DA)
    This index is meant to assist the user in locating the correct package interface needed to display a particular item of data to a form.
4.01 ENTRY ACTION 4;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  MAY 21, 1993
  • HELP-PROMPT:  This is Standard MUMPS code.
  • DESCRIPTION:  
    This code will be executed after the PROTECTED VARIABLES are newed, but before the interface routine is called.
    WRITE AUTHORITY: @
5.01 EXIT ACTION 5;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  MAY 18, 1993
  • HELP-PROMPT:  This is Standard MUMPS code.
  • DESCRIPTION:  
    This code will be executed after the interface routine is called. The effect of the NEW done on the PROTECTED VARIABLES is still in effect.
    WRITE AUTHORITY: @
6 PROTECTED LOCAL VARIABLES 6;0 Multiple #357.66 357.66

  • DESCRIPTION:  This is a list of variables that should be newed before the entry action or calling the interface routine. It is protection against interfaces that alter or kill variables, or entry actions that do so. Note that REQUIRED
    VARIABLES should not also be PROTECTED VARIABLES. If an interface routine changes a required variable, however, there is a way to protect it. Supposing, for example, DFN is killed by the interface. This will protect it:
    PROTECTED VARIABLE: IBDFN
    ENTRY ACTION: S IBDFN=DFN
    EXIT ACTION: S DFN=IBDFN
7 REQUIRED LOCAL VARIABLES 7;0 Multiple #357.67 357.67

  • DESCRIPTION:  
    The interface may require inputs. This field is a list of the required local variables. The interface will not be called unless the variables are determined to exist.
9 PCE DIM INPUT TRANSFORM 9;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  APR 01, 1996
  • HELP-PROMPT:  The input transform should transform X to the value that should be passed.
  • DESCRIPTION:  
    Used to transform X, the identifier stored with the form object, to the form that should be passed to the PCE Device Interface Module. It may, for example, transform a code to an ien.
    WRITE AUTHORITY: @
10 HELP TEXT 10;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>245!($L(X)<1) X
  • LAST EDITED:  MAY 22, 1995
  • HELP-PROMPT:  This should provide some help to the user who is trying to enter a value associated with a bubble.
  • DESCRIPTION:  
    This should provide some help to the user who is trying to enter a value associated with a bubble.
11 VALIDATOR 11;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  SEP 08, 1995
  • HELP-PROMPT:  This is Standard MUMPS code will kill X if X no longer identifies a valid code.
  • DESCRIPTION:  This field is used to validate codes currently on a form. The variable X should be set to the identifier that was returned by the Package Interface. For selection interfaces, the identifier is always piece 1 of the 0 node
    of the entry in the selection list. Xecuting this field will result in X being killed if the value is not valid. This is used by the maintanance utility, for example, to find CPT codes that have been inactivated.
    WRITE AUTHORITY: @
12.01 PCE DIM NODE 12;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<1) X
  • LAST EDITED:  OCT 17, 1995
  • HELP-PROMPT:  What node will be used to pass the data?
  • DESCRIPTION:  
    The node used to pass the data to PCE, using the PCE DEVICE INTERFACE MODULE.
12.02 PCE DIM PIECE, VALUE 12;2 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 17, 1995
  • HELP-PROMPT:  What piece should be used to pass the value?
  • DESCRIPTION:  
    The piece in the PXCA node used to pass the input value.
12.03 PCE DIM PIECE, NARRATIVE 12;3 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 17, 1995
  • HELP-PROMPT:  What piece should be used to pass the text displayed on the form?
  • DESCRIPTION:  
    The piece in the PCXA node used to pass the text displayed on the form.
12.04 PCE DIM PIECE, HEADER 12;4 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 17, 1995
  • HELP-PROMPT:  What piece should be used to pass the header displayed on the form?
  • DESCRIPTION:  
    The piece on the node specified by the PCE DIM that the header is mapped to.
12.05 PCE DIM PIECE, DATA QUALIFIER 12;5 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 17, 1995
  • HELP-PROMPT:  What piece should be used to pass the data qualifier?
  • DESCRIPTION:  
    The piece of the PXCA node where the data modifier belongs.
12.06 PCE DIM PIECE, QUANTITY 12;6 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 15, 1996
  • HELP-PROMPT:  Type a Number between 1 and 99, 0 Decimal Digits
  • DESCRIPTION:  
    An entry in this field indicates which piece of the array the quantity should be passed on when sending data to PCE.
13 ALLOWABLE QUALIFIERS 13;0 VARIABLE POINTER Multiple #357.613 357.613

  • DESCRIPTION:  
    This mulitiple contains the list of qualifiers that may apply to the data.
14 PCE DIM OUTPUT TRANSFORM 14;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  APR 01, 1996
  • HELP-PROMPT:  This should change Y, the value to be passed, to a value suitable for display.
  • DESCRIPTION:  
    This transform should set Y, the value to be passed to the PCE Device Interface Module (DIM), to a value that is suitable for display. It may, for example, change an ien to a code.
    WRITE AUTHORITY: @
15 DATA DESCRIPTION 15;0 Multiple #357.615 357.615

  • DESCRIPTION:  
    For interfaces that return records, this multiple stores information on the fields, other than the first field.
  • IDENTIFIED BY:  
    "WRITE": D EN^DDIOL(" PIECE="_$P(^(0),U,3),"","?0")
16.1 ALLOW INPUT OF NARRATIVE? 16;1 SET
  • 'n' FOR NO;
  • 'o' FOR OPTIONAL;
  • 'r' FOR REQUIRED;

  • LAST EDITED:  APR 21, 1995
  • HELP-PROMPT:  Should the user be allowed to enter a narrative? Answer n=NO, o=OPTIONAL, r=REQUIRED
  • DESCRIPTION:  
    For selection interfaces, this field determines whether a narrative is allowed by the PCE Generic Device Interface.
16.2 NARRATIVE DATA TYPE 16;2 POINTER TO AICS DATA ELEMENTS FILE (#359.1) AICS DATA ELEMENTS(#359.1)

  • LAST EDITED:  APR 26, 1995
  • HELP-PROMPT:  What data type definition describes the narrative?
  • DESCRIPTION:  
    This determines, among other things, how much space to allocate for the narrative.
16.3 NARRATIVE HEADER 16;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1) X
  • LAST EDITED:  AUG 15, 1995
  • HELP-PROMPT:  Answer must be 1-40 characters in length.
  • DESCRIPTION:  
    Used to label the narrative field.
16.5 ALLOW INPUT OF PRIMARY VALUE? 16;5 SET
  • 'n' FOR NO;
  • 'o' FOR OPTIONAL;
  • 'r' FOR REQUIRED;

  • LAST EDITED:  APR 26, 1995
  • HELP-PROMPT:  Should a code be entered? n=NO, o=OPTIONAL, r=REQUIRED
  • DESCRIPTION:  
    For selectin interfaces this determines whether a value, other than a narrative, can be entered.
16.6 PRIMARY VALUE DATA TYPE 16;6 POINTER TO AICS DATA ELEMENTS FILE (#359.1) AICS DATA ELEMENTS(#359.1)

  • LAST EDITED:  APR 26, 1995
  • HELP-PROMPT:  What type of data is the primary value?
  • DESCRIPTION:  
    For selection interfaces this determines, among other things, the data type of the value to be entered.
16.7 PRIMARY VALUE HEADER 16;7 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1) X
  • LAST EDITED:  AUG 15, 1995
  • HELP-PROMPT:  Answer must be 1-40 characters in length.
  • DESCRIPTION:  
    Used to label the primary value field.
16.8 ALLOW MULTIPLIERS 16;8 SET
  • '1' FOR YES;

  • LAST EDITED:  OCT 08, 1996
  • HELP-PROMPT:  Enter yes if this interface will allow entry of quantity at form development time.
  • DESCRIPTION:  
    For selection interfaces, this determines whether 'quantity' should be asked at form development time to pass multiple occurrences of a selection to PCE.
16.9 ALLOW INPUT OF MULTIPLE CODES? 16;9 SET
  • '1' FOR YES;

  • LAST EDITED:  OCT 21, 1996
  • HELP-PROMPT:  Enter a 1 for 'YES'.
  • DESCRIPTION:  Enter a one in this field if the users will be allowed to add more than one code to pass along to PCE when one entry is bubbled. Data in this field REQUIRES that field 17 be populated with mumps code that will allow
    selection of the code if the entry is edited.
17 SELECTOR 17;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  SEP 08, 1995
  • HELP-PROMPT:  Enter mumps code that will allow the form designer to add a choice to a multiple choice field.
  • DESCRIPTION:  This field only applies to input interfaces. It is executed as by an input transform when creating a multiple choice field. It should: 1) Kill X if an nothing is selected, otherwise set X to a value suitable for display,
    perhaps the code. 2) Set IBLABEL to a suitable label for the choice. 3) Set IBID to an identifier. The identifier should ideally be exportable, meaning the same from site to site. This usually means a coded value rather
    than an ien. The identfier should match that of a corresponding selection interface, if there is one.
    WRITE AUTHORITY: @
18 MANUAL DATA ENTRY ROUTINE 18;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  DEC 08, 1995
  • HELP-PROMPT:  Enter the code to be executed during manual data entry for this interface. This is Standard MUMPS code.
  • DESCRIPTION:  Enter the code to be executed to do manual data entry for this interface.
    This field should only be completed for input package interfaces. This code will be executed to provide quick data entry for a user trying to input data for a form. It is expected that the output of this field will be
    used to format the PXCA array prior to calling PCE to file the data for the encounter.
    Developers writing routines for this entry should provide a roll and scroll interface for manaul entry of items only on the form.
    WRITE AUTHORITY: @
19 EXTERNAL DISPLAY VALUES 19;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  FEB 14, 1996
  • HELP-PROMPT:  This is Standard MUMPS code.
  • DESCRIPTION:  Executable code used to translate the internal value that is to be passed to PCE into its external value for display purposes. It is used by the data validation routines to display the external values and descriptions of
    what is to be passed, to the user for verification.
    WRITE AUTHORITY: @
20 PASS DQ AS VALUE 20;1 SET
  • '1' FOR YES;

  • LAST EDITED:  OCT 01, 1996
  • HELP-PROMPT:  Enter Yes if the Data Qualifier should be passed as the Value when sending data to PCE.
  • DESCRIPTION:  If the value of the Data Qualifier shall be passed to PCE as the VALUE, this field should be set to one. Doing so will prevent the data in the VALUE from populating the PCE DIM NODE, but instead, will allow the Data
    Qualifier to pass as the VALUE. This is used mostly for YES/NO Data Qualifiers, where the value may be a question, and the Data Qualifier Value, if bubbled, is the value that must be placed on the PCE DIM NODE.
21 PCE DIM PIECE, VARIABLE VALUE 21;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  OCT 01, 1996
  • HELP-PROMPT:  This is Standard MUMPS code.
  • DESCRIPTION:  This field should be populated when the PCE DIM PIECE VALUE is not constant. If the value of that field is dependent upon specific conditions, those conditions may be evaluated by placing the MUMPS code in this field.
    Ultimately, the code should return a value that will be used as the PCE DIM PIECE VALUE. If the return value is null, the original PCE DIM PIECE VALUE field will be used to determine the piece location to pass the VALUE
    on.
    WRITE AUTHORITY: @

Found Entries, Total: 122

NAME: DPT PATIENT'S NAME    NAME: DPT PATIENT'S SEX    NAME: DPT PATIENT'S DOB/AGE    NAME: GMRA PATIENT'S ALLERGIES    NAME: DG SELECT CPT PROCEDURE CODES    NAME: DPT PATIENT'S SC CONDITIONS    NAME: DG SELECT ICD-9 DIAGNOSIS CODES    NAME: DPT PATIENT'S PID    
NAME: IBDF UTILITY FOR SELECTING BLANKS    NAME: DPT PATIENT ADDRESS LINES    NAME: DPT PATIENT'S TELEPHONE NUMBER    NAME: DPT IS PATIENT INSURED?    NAME: DPT PATIENT'S INSURANCE POLICIES    NAME: IBDF UTILITY FOR BLANK LINES    NAME: IBDF UTILITY FOR LABELS ONLY    NAME: GMP PATIENT ACTIVE PROBLEMS    
NAME: DPT PATIENT'S EMPLOYER NAME    NAME: DPT PATIENT'S EMPLOYER ADDRESS LINES    NAME: DPT PATIENT'S EMPLOYER TELEPHONE    NAME: DPT SPOUSE'S EMPLOYER NAME    NAME: DPT SPOUSE'S EMPLOYER ADDRESS LINES    NAME: DPT SPOUSE'S EMPLOYER TELEPHONE    NAME: DPT PATIENT'S MARITAL STATUS    NAME: DPT PATIENT'S EMPLOYMENT STATUS    
NAME: SD CLINIC NAME    NAME: SD APPOINTMENT DATE/TIME    NAME: DPT PATIENT ELIGIBILITY DATA    NAME: DPT SERVICE HISTORY RELATED DATA    NAME: DPT PATIENT'S MEANS TEST DATA    NAME: GMP SELECT CLINIC COMMON PROBLEMS    NAME: ACTION PROFILE - 45 DAYS    NAME: INFORMATION PROFILE - 45 DAYS    
NAME: ROUTING SLIP    NAME: IB CURRENT DATE    NAME: IB CURRENT DATE@TIME    NAME: IB CURRENT TIME    NAME: SD DIVISION NAME    NAME: SD INSTITUTION NAME    NAME: DPT PATIENT SHORT ADDRESS    NAME: DPT SC HIDDEN LABELS    
NAME: DPT SC TREATMENT QUESTIONS    NAME: SD FUTURE APPTS, SAME DAY    NAME: SD FUTURE APPTS, ALL    NAME: SD FUTURE APPTS, SAME CLINIC    NAME: DPT PATIENT'S INSURANCE - ALL    NAME: DPT PATIENT'S INSURANCE - ACTIVE ONLY    NAME: INPUT PROCEDURE CODE (CPT4)    NAME: DG SELECT VISIT TYPE CPT PROCEDURES    
NAME: INPUT PROVIDER    NAME: INPUT VISIT TYPE    NAME: INPUT SC RELATED?    NAME: INPUT AO RELATED?    NAME: INPUT IR RELATED?    NAME: INPUT EC RELATED?    NAME: INPUT PROVIDER INDICATOR    NAME: PX INPUT ATTENDING PHYSICIAN    
NAME: INPUT DIAGNOSIS CODE (ICD9)    NAME: INPUT EDIT INFORMATION    NAME: SD SELECT PROVIDER    NAME: IBDF FORM ID ASSIGNED BY FORM TRACKING    NAME: GMP SELECT PATIENT ACTIVE PROBLEMS    NAME: PX INPUT PATIENT ACTIVE PROBLEM    NAME: DPT PATIENT'S SC CONDITIONS    NAME: SD FUTURE APPTS, SAME DAY    
NAME: SD FUTURE APPTS, ALL    NAME: SD FUTURE APPTS, SAME CLINIC    NAME: DPT PATIENT'S INSURANCE - ALL    NAME: DPT PATIENT'S INSURANCE - ACTIVE ONLY    NAME: DPT PATIENT'S INSURANCE POLICIES    NAME: GMRA PATIENT'S ALLERGIES    NAME: PX SELECT EDUCATION TOPICS    NAME: PX SELECT IMMUNIZATIONS    
NAME: PX SELECT EXAMS    NAME: PX SELECT TREATMENTS    NAME: PX SELECT SKIN TESTS    NAME: PX SELECT HEALTH FACTORS    NAME: PX INPUT EDUCATION TOPICS    NAME: PX INPUT EXAMS    NAME: PX INPUT HEALTH FACTORS    NAME: PX INPUT IMMUNIZATION    
NAME: PX INPUT CHECKOUT TIME    NAME: PX INPUT TREATMENTS    NAME: PX INPUT SKIN TESTS    NAME: PX INPUT VITALS    NAME: PX INPUT VISIT CLASSIFICATION    NAME: DG APPOINTMENT DISPOSITION    NAME: PX INPUT VISIT TYPE    NAME: GMP INPUT CLINIC COMMON PROBLEMS    
NAME: LAB    NAME: LABB    NAME: SD PRIMARY CARE TEAM    NAME: SD PRIMARY CARE PRACTIONER    NAME: DPT SC HIDDEN TREATMENT QUESTIONS    NAME: PX INPUT SC TREATMENT QUESTIONS    NAME: SD OTHER INFO    NAME: DPT SC HIDDEN TREATMENT QUESTIONS    
NAME: IBD INPUT CANCEL/NOSHOW    NAME: TEST    NAME: TEST    NAME: LABB    NAME: LABB    NAME: DG 1010F PRINT    NAME: PX CLINICAL REMINDERS PRINT    NAME: ICPT CPT MODIFIER DISPLAY    
NAME: DPT SERVICE HISTORY RELATED DATA (MST)    NAME: DPT SC TREATMENT QUESTIONS (MST)    NAME: DPT SC HIDDEN TREATMENT QUESTIONS (MST)    NAME: PX INPUT SC TREATMENT QUESTIONS (MST)    NAME: DGMST STATUS    NAME: PX INPUT NO CLASSIFICATIONS    NAME: DGMST SELECT MST CLASSIFICATN    NAME: DGMST INPUT MST CLASSIFICATION    
NAME: DG ENROLLMENT PRIORITY    NAME: GAF SCORE HANDPRINT    NAME: SELECT GAF PROVIDER    NAME: INPUT GAF PROVIDER    NAME: PREVIOUS GAF SCORE    NAME: INPUT GAF SCORE TABLE    NAME: INPUT GAF SCORE TABLE 2    NAME: INPUT GAF SCORE TABLE 3    
NAME: INPUT DIAGNOSIS CODE (ICD10)    NAME: DG SELECT ICD-10 DIAGNOSIS CODES    

External References

Name Field # of Occurrence
EN^DDIOL IDWRITE+1, IDWRITE1+1
^DIC .11+1, .13+1
^DIM 4.01+1, 5.01+1, 9+1, 11+1, 14+1, 17+1, 18+1, 19+1, 21+1
LOOKUP^IBDF16 3(HELP )
LIST^IBDFDE2 18(IEN:59), 18(IEN:61), 18(IEN:62), 18(IEN:69), 18(IEN:74), 18(IEN:91), 18(IEN:92), 18(IEN:93), 18(IEN:94), 18(IEN:96)
, 18(IEN:97), 18(IEN:103), 18(IEN:166), 18(IEN:171)
GAFSCOR^IBDFDE23 18(IEN:164), 18(IEN:168), 18(IEN:169), 18(IEN:170)
HNDPR^IBDFDE3 18(IEN:99)
$$CPT^IBDFN12 9(IEN:7)
SLCTCLS^IBDFN12 17(IEN:100)
SLCTCPT^IBDFN12 17(IEN:59)
SLCTDX^IBDFN12 17(IEN:9), 17(IEN:69)
SLCTDX10^IBDFN12 17(IEN:171), 17(IEN:172)
SLCTED^IBDFN12 17(IEN:91)
SLCTEX^IBDFN12 17(IEN:92)
SLCTHF^IBDFN12 17(IEN:93)
SLCTIMM^IBDFN12 17(IEN:94)
SLCTSKN^IBDFN12 17(IEN:97)
SLCTTR^IBDFN12 17(IEN:88), 17(IEN:96)
SLCTVST^IBDFN12 17(IEN:62), 17(IEN:102)
SLCTYN^IBDFN12 17(IEN:63), 17(IEN:64), 17(IEN:65), 17(IEN:66)
CPT^IBDFN14 19(IEN:59)
DX^IBDFN14 19(IEN:9), 19(IEN:69)
DX10^IBDFN14 19(IEN:171), 19(IEN:172)
ED^IBDFN14 19(IEN:91)
EXAM^IBDFN14 19(IEN:92)
HF^IBDFN14 19(IEN:93)
IMMUN^IBDFN14 19(IEN:94)
ST^IBDFN14 19(IEN:97)
TREAT^IBDFN14 19(IEN:96)
VST^IBDFN14 19(IEN:62), 19(IEN:102)
YN^IBDFN14 19(IEN:63), 19(IEN:64), 19(IEN:65), 19(IEN:66)
TESTCPT^IBDFN7 11(IEN:7), 11(IEN:59)
TESTICD^IBDFN7 11(IEN:9), 11(IEN:69)
TESTICD0^IBDFN7 11(IEN:171), 11(IEN:172)
TESTLEX^IBDFN7 11(IEN:33)
TESTVST^IBDFN7 11(IEN:60), 11(IEN:62), 11(IEN:102)
INPICD10^IBDFN8 9(IEN:171), 9(IEN:172)
INPUTCPT^IBDFN8 9(IEN:59), 9(IEN:62), 9(IEN:102)
INPUTICD^IBDFN8 9(IEN:9), 9(IEN:69)
$$DSPICD10^IBDFN9 14(IEN:171)
$$DSPLYCPT^IBDFN9 14(IEN:59), 14(IEN:62), 14(IEN:102)
$$DSPLYICD^IBDFN9 14(IEN:69)
$$DSPLYPRV^IBDFN9 14(IEN:61), 14(IEN:68), 14(IEN:166)
$$DSPLYYN^IBDFN9 14(IEN:63), 14(IEN:64), 14(IEN:65), 14(IEN:66), 14(IEN:109), 14(IEN:151), 14(IEN:155)
$$VARVAL^IBDFN9 21(IEN:100), 21(IEN:109), 21(IEN:151), 21(IEN:155)
HELP7^IBDFU5A .16(HELP )
ASK^IBDFU9 ACT+1
$$DSPLYED^PXAPIIB 14(IEN:91)
$$DSPLYEX^PXAPIIB 14(IEN:92)
$$DSPLYHF^PXAPIIB 14(IEN:93)
$$DSPLYIM^PXAPIIB 14(IEN:94)
$$DSPLYSK^PXAPIIB 14(IEN:97)
TESTEDT^PXAPIIB 11(IEN:85), 11(IEN:91)
TESTEXM^PXAPIIB 11(IEN:87), 11(IEN:92)
TESTHF^PXAPIIB 11(IEN:90), 11(IEN:93)
TESTIMM^PXAPIIB 11(IEN:86), 11(IEN:94)
TESTSK^PXAPIIB 11(IEN:89), 11(IEN:97)
TESTTRT^PXAPIIB 11(IEN:88), 11(IEN:96)
$$UPPER^VALM1 .16+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^DD("KWIC" 3(XREF 1S)
^IBE(357.6 - [#357.6] .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), .04(XREF 1S), .04(XREF 1K), 3(XREF 1S), 3(XREF 1K)

Naked Globals

Name Field # of Occurrence
^(0 IDWRITE+1, IDWRITE1+1

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> % 3(XREF 1S), 3(XREF 1K)
>> %1 3(XREF 1S), 3(XREF 1K)
>> ACT 4.01(IEN:15), 4.01(IEN:55), 4.01(IEN:56), 4.01(IEN:79), 4.01(IEN:80), 4.01(IEN:81)
>> DA .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), .04(XREF 1S), .04(XREF 1K), 3(XREF 1S), 3(XREF 1K)
DIC .11+1!*, .13+1!*
DIC("S" .11+1*, .11SCR+1*, .13+1*, .13SCR+1*, .15SCR+1*
>> DIE .11+1, .13+1
>> I 3(XREF 1S), 3(XREF 1K)
>> IBDF 18(IEN:59), 18(IEN:61), 18(IEN:62), 18(IEN:69), 18(IEN:74), 18(IEN:91), 18(IEN:92), 18(IEN:93), 18(IEN:94), 18(IEN:96)
, 18(IEN:97), 18(IEN:99), 18(IEN:103), 18(IEN:166), 18(IEN:171)
>> IBDF("LEXICON" 18(IEN:103)
>> IBDF("OTHER" 18(IEN:59), 18(IEN:61), 18(IEN:62), 18(IEN:69), 18(IEN:91), 18(IEN:92), 18(IEN:93), 18(IEN:94), 18(IEN:96), 18(IEN:97)
, 18(IEN:103), 18(IEN:166), 18(IEN:171)
>> IBDSEL 18(IEN:59), 18(IEN:61), 18(IEN:62), 18(IEN:69), 18(IEN:74), 18(IEN:91), 18(IEN:92), 18(IEN:93), 18(IEN:94), 18(IEN:96)
, 18(IEN:97), 18(IEN:99), 18(IEN:103), 18(IEN:166), 18(IEN:171)
IBDWNAM IDWRITE+1~*
IBDWTYPE IDWRITE1+1~*
IBDXE .01(XREF 2S), .01(XREF 2K)
>> PI 17(IEN:100)
>> PSDAYS 4.01(IEN:40), 4.01(IEN:41)
>> PSTYPE 4.01(IEN:40), 4.01(IEN:41)
U IDWRITE+1
X .01+1!, .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), .02+1!, .03+1!, .04+1!, .04(XREF 1S), .04(XREF 1K)
, .11+1*!, .13+1*!, .16+1*!, 2.01+1!, 2.02+1!, 2.16+1!, 3+1!, 3(XREF 1S), 3(XREF 1K), 4.01+1!
, 5.01+1!, 9+1!, 9(IEN:7), 9(IEN:9), 9(IEN:59), 9(IEN:62), 9(IEN:69), 9(IEN:102), 9(IEN:171), 9(IEN:172)
, 10+1!, 11+1!, 12.01+1!, 12.02+1!, 12.03+1!, 12.04+1!, 12.05+1!, 12.06+1!, 14+1!, 16.3+1!
, 16.7+1!, 17+1!, 17(IEN:9), 17(IEN:59), 17(IEN:62), 17(IEN:63), 17(IEN:64), 17(IEN:65), 17(IEN:66), 17(IEN:69)
, 17(IEN:88), 17(IEN:91), 17(IEN:92), 17(IEN:93), 17(IEN:94), 17(IEN:96), 17(IEN:97), 17(IEN:100), 17(IEN:102), 17(IEN:171)
, 17(IEN:172), 18+1!, 19+1!, 19(IEN:9), 19(IEN:59), 19(IEN:62), 19(IEN:63), 19(IEN:64), 19(IEN:65), 19(IEN:66)
, 19(IEN:69), 19(IEN:91), 19(IEN:92), 19(IEN:93), 19(IEN:94), 19(IEN:96), 19(IEN:97), 19(IEN:102), 19(IEN:171), 19(IEN:172)
, 21+1!, 21(IEN:100), 21(IEN:109), 21(IEN:151), 21(IEN:155)
>> Y .11+1, .13+1, 14(IEN:59), 14(IEN:61), 14(IEN:62), 14(IEN:63), 14(IEN:64), 14(IEN:65), 14(IEN:66), 14(IEN:68)
, 14(IEN:69), 14(IEN:91), 14(IEN:92), 14(IEN:93), 14(IEN:94), 14(IEN:97), 14(IEN:102), 14(IEN:109), 14(IEN:151), 14(IEN:155)
, 14(IEN:166), 14(IEN:171), 21(IEN:100), 21(IEN:109), 21(IEN:151), 21(IEN:155)
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables  | All