source: cprs/branches/tmg-cprs/Server_KIDS/TMG-CPRS-TEXTOBJ-FMFLD-1.0-1.KIDS@ 1547

KIDS Distribution saved on Apr 18, 2010@22:43:40
TMG CPRS TEXT OBJ FM FLD 1.0*1
**KIDS**:TMG-CPRS-TEXTOBJ-FMFLD*1.0*1^

**INSTALL NAME**
TMG-CPRS-TEXTOBJ-FMFLD*1.0*1
"BLD",7633,0)
TMG-CPRS-TEXTOBJ-FMFLD*1.0*1^^0^3100418^n
"BLD",7633,1,0)
^^50^50^3100418^^
"BLD",7633,1,1,0)
This patch provides a TIU TEXT object that can be included
"BLD",7633,1,2,0)
on templates in CPRS.  This object will allow fetching the
"BLD",7633,1,3,0)
value of any field from the PATIENT file.
"BLD",7633,1,4,0)

"BLD",7633,1,5,0)
Usage
"BLD",7633,1,6,0)
   |TMG PATIENT FLD{Field(s)^Flags^FormatString}
"BLD",7633,1,7,0)

"BLD",7633,1,8,0)
            Field(s) -- required.  Options for input:
"BLD",7633,1,9,0)
                -  A single field number or name
"BLD",7633,1,10,0)
                -  A list of field numbers (or names), separated by semicolons
"BLD",7633,1,11,0)
                -  A range of field numbers (or names), in the form M:N,
"BLD",7633,1,12,0)
                         where M and N are the end points of the inclusive range.
"BLD",7633,1,13,0)
                         All field numbers within this range are retrieved.
"BLD",7633,1,14,0)
                -  A '*' for all fields at the top level (no sub-multiple record).
"BLD",7633,1,15,0)
                -  A '**' for all fields including all fields and data in sub-multiple fields.
"BLD",7633,1,16,0)
                -  Field number (or name) of a multiple followed by an * to indicate all
"BLD",7633,1,17,0)
                         fields and records in the sub-multiple for that field.
"BLD",7633,1,18,0)
                Invalid field names will be ignored
"BLD",7633,1,19,0)
            Flags -- Optional.
"BLD",7633,1,20,0)
                -  'F' -- include field name in results with value.  e.g. "AGE: 43" instead of just "43"
"BLD",7633,1,21,0)
                -         This flag is ignored if a FormatString is provided (see below)
"BLD",7633,1,22,0)
                -  'S' -- Keep all data values on a single line, separated by ';'.
"BLD",7633,1,23,0)
                -         If flag not provided, and multiple data fields are requested,
"BLD",7633,1,24,0)
                -         then the default is that each data value will be separated by a
"BLD",7633,1,25,0)
                -         CRLF [$C(13)_$C(10)]
"BLD",7633,1,26,0)
                -         This flag is ignored if a FormatString is provided (see below)
"BLD",7633,1,27,0)
                -  'R' -- Resolve fields to NAMES, even if a field NUMBER was used for input request
"BLD",7633,1,28,0)
                -         Note: this will affect the sorting order of the output (see FormatString  
"BLD",7633,1,29,0)
                -         info below).  I.e. if R not specified, and field NUMBERS are used for input,
"BLD",7633,1,30,0)
                -         then results will be returned in numerical field number order by default.   
"BLD",7633,1,31,0)
                -         If R is specified, then field numbers are converted to field NAMES, and that
"BLD",7633,1,32,0)
                -         is used to determine the order of output.
"BLD",7633,1,33,0)
                -  'N' -- Don't return values for empty fields.  This is helpful if ALL fields
"BLD",7633,1,34,0)
                -         were requested via '*'
"BLD",7633,1,35,0)
            FormatString -- A string to determine how results are passed back....
"BLD",7633,1,36,0)
                NOTE: without a format string, results will be passed back in the order returned
"BLD",7633,1,37,0)
                      by fileman.  I.e. if user requested fields "SEX;.01;AGE", then Fileman will
"BLD",7633,1,38,0)
                      place results into an array, which MUMPS will sort alphabetically, e.g.
"BLD",7633,1,39,0)
                      .01, then AGE, then SEX.  If "*" fields are requested, it would be even
"BLD",7633,1,40,0)
                      more complex.  A format string will allow the user to specify ORDER.   
"BLD",7633,1,41,0)
                Format: e.g. "Any arbitrary text %FieldNameOrNum% more text %FieldNameOrNum% ..."
"BLD",7633,1,42,0)
                  (The goal was to follow the method used by printf in the c language.)
"BLD",7633,1,43,0)
                  -  Any arbitrary text can be included.
"BLD",7633,1,44,0)
                  -  Field numbers or names should be enclosed by the '%' character
"BLD",7633,1,45,0)
                       These will be replaced with actual data values.
"BLD",7633,1,46,0)
                  - '\n' can be included to specify line breaks
"BLD",7633,1,47,0)
                  - '%%' will be used to show a '%' in the output text
"BLD",7633,1,48,0)
                  - Invalid, or non-matching, field names/numbers will be ignored.
"BLD",7633,1,49,0)

"BLD",7633,1,50,0)
Results: returns a string that will be sent back to CPRS, to be included in a text note
"BLD",7633,4,0)
^9.64PA^8925.1^1
"BLD",7633,4,8925.1,0)
8925.1
"BLD",7633,4,8925.1,222)
n^y^f^^n^TMG PATIENT FLD^y^o^n
"BLD",7633,4,8925.1,224)

"BLD",7633,4,"B",8925.1,8925.1)

"BLD",7633,6.3)
1
"BLD",7633,"KRN",0)
^9.67PA^8989.52^19
"BLD",7633,"KRN",.4,0)
.4
"BLD",7633,"KRN",.401,0)
.401
"BLD",7633,"KRN",.402,0)
.402
"BLD",7633,"KRN",.403,0)
.403
"BLD",7633,"KRN",.5,0)
.5
"BLD",7633,"KRN",.84,0)
.84
"BLD",7633,"KRN",3.6,0)
3.6
"BLD",7633,"KRN",3.8,0)
3.8
"BLD",7633,"KRN",9.2,0)
9.2
"BLD",7633,"KRN",9.8,0)
9.8
"BLD",7633,"KRN",9.8,"NM",0)
^9.68A^1^1
"BLD",7633,"KRN",9.8,"NM",1,0)
TMGTIUO2^^0^B57347468
"BLD",7633,"KRN",9.8,"NM","B","TMGTIUO2",1)

"BLD",7633,"KRN",19,0)
19
"BLD",7633,"KRN",19.1,0)
19.1
"BLD",7633,"KRN",101,0)
101
"BLD",7633,"KRN",409.61,0)
409.61
"BLD",7633,"KRN",771,0)
771
"BLD",7633,"KRN",870,0)
870
"BLD",7633,"KRN",8989.51,0)
8989.51
"BLD",7633,"KRN",8989.52,0)
8989.52
"BLD",7633,"KRN",8994,0)
8994
"BLD",7633,"KRN","B",.4,.4)

"BLD",7633,"KRN","B",.401,.401)

"BLD",7633,"KRN","B",.402,.402)

"BLD",7633,"KRN","B",.403,.403)

"BLD",7633,"KRN","B",.5,.5)

"BLD",7633,"KRN","B",.84,.84)

"BLD",7633,"KRN","B",3.6,3.6)

"BLD",7633,"KRN","B",3.8,3.8)

"BLD",7633,"KRN","B",9.2,9.2)

"BLD",7633,"KRN","B",9.8,9.8)

"BLD",7633,"KRN","B",19,19)

"BLD",7633,"KRN","B",19.1,19.1)

"BLD",7633,"KRN","B",101,101)

"BLD",7633,"KRN","B",409.61,409.61)

"BLD",7633,"KRN","B",771,771)

"BLD",7633,"KRN","B",870,870)

"BLD",7633,"KRN","B",8989.51,8989.51)

"BLD",7633,"KRN","B",8989.52,8989.52)

"BLD",7633,"KRN","B",8994,8994)

"BLD",7633,"QUES",0)
^9.62^^
"DATA",8925.1,1452,0)
TMG PATIENT FLD^^TMG PATIENT FLD^O^^55^11
"DATA",8925.1,1452,9)
S X=$$GETPTFLD^TMGTIUO2($G(DFN),X)
"DATA",8925.1,1452,99)
61831,73983
"FIA",8925.1)
TIU DOCUMENT DEFINITION
"FIA",8925.1,0)
^TIU(8925.1,
"FIA",8925.1,0,0)
8925.1I
"FIA",8925.1,0,1)
n^y^f^^n^TMG PATIENT FLD^y^o^n
"FIA",8925.1,0,10)

"FIA",8925.1,0,11)

"FIA",8925.1,0,"RLRO")
^DIBT(913,1)
"FIA",8925.1,8925.1)
0
"FIA",8925.1,8925.11)
0
"FIA",8925.1,8925.111)
0
"FIA",8925.1,8925.112)
0
"FIA",8925.1,8925.113)
0
"FIA",8925.1,8925.114)
0
"FIA",8925.1,8925.12)
0
"FIA",8925.1,8925.13)
0
"FIA",8925.1,8925.14)
0
"MBREQ")
0
"QUES","XPF1",0)
Y
"QUES","XPF1","??")
^D REP^XPDH
"QUES","XPF1","A")
Shall I write over your |FLAG| File
"QUES","XPF1","B")
YES
"QUES","XPF1","M")
D XPF1^XPDIQ
"QUES","XPF2",0)
Y
"QUES","XPF2","??")
^D DTA^XPDH
"QUES","XPF2","A")
Want my data |FLAG| yours
"QUES","XPF2","B")
YES
"QUES","XPF2","M")
D XPF2^XPDIQ
"QUES","XPI1",0)
YO
"QUES","XPI1","??")
^D INHIBIT^XPDH
"QUES","XPI1","A")
Want KIDS to INHIBIT LOGONs during the install
"QUES","XPI1","B")
NO
"QUES","XPI1","M")
D XPI1^XPDIQ
"QUES","XPM1",0)
PO^VA(200,:EM
"QUES","XPM1","??")
^D MG^XPDH
"QUES","XPM1","A")
Enter the Coordinator for Mail Group '|FLAG|'
"QUES","XPM1","B")

"QUES","XPM1","M")
D XPM1^XPDIQ
"QUES","XPO1",0)
Y
"QUES","XPO1","??")
^D MENU^XPDH
"QUES","XPO1","A")
Want KIDS to Rebuild Menu Trees Upon Completion of Install
"QUES","XPO1","B")
NO
"QUES","XPO1","M")
D XPO1^XPDIQ
"QUES","XPZ1",0)
Y
"QUES","XPZ1","??")
^D OPT^XPDH
"QUES","XPZ1","A")
Want to DISABLE Scheduled Options, Menu Options, and Protocols
"QUES","XPZ1","B")
NO
"QUES","XPZ1","M")
D XPZ1^XPDIQ
"QUES","XPZ2",0)
Y
"QUES","XPZ2","??")
^D RTN^XPDH
"QUES","XPZ2","A")
Want to MOVE routines to other CPUs
"QUES","XPZ2","B")
NO
"QUES","XPZ2","M")
D XPZ2^XPDIQ
"RTN")
1
"RTN","TMGTIUO2")
0^1^B57347468
"RTN","TMGTIUO2",1,0)
TMGTIU02 ;TMG/TIU Text Object Expansion Fns;04/15/10
"RTN","TMGTIUO2",2,0)
         ;;1.0;TMG-LIB;**1**;04/15/10;Build 1
"RTN","TMGTIUO2",3,0)
 ;
"RTN","TMGTIUO2",4,0)
 ;"Kevin Toppenberg MD
"RTN","TMGTIUO2",5,0)
 ;"GNU General Public License (GPL) applies
"RTN","TMGTIUO2",6,0)
 ;"04/15/10
"RTN","TMGTIUO2",7,0)
 ;
"RTN","TMGTIUO2",8,0)
 ;"=======================================================================
"RTN","TMGTIUO2",9,0)
 ;"PUBLIC FUNCTIONS
"RTN","TMGTIUO2",10,0)
 ;"=======================================================================
"RTN","TMGTIUO2",11,0)
 ;
"RTN","TMGTIUO2",12,0)
 ;"=======================================================================
"RTN","TMGTIUO2",13,0)
 ;"PRIVATE FUNCTIONS
"RTN","TMGTIUO2",14,0)
 ;"=======================================================================
"RTN","TMGTIUO2",15,0)
 ;
"RTN","TMGTIUO2",16,0)
 ;"=======================================================================
"RTN","TMGTIUO2",17,0)
 ;
"RTN","TMGTIUO2",18,0)
GETPTFLD(DFN,PARAM) ;
"RTN","TMGTIUO2",19,0)
        ;"Purpose: This is the server-side code for the TIU TEXT OBJECT, which
"RTN","TMGTIUO2",20,0)
        ;"      will allow the user to retrieve a field from the PATIENT file.
"RTN","TMGTIUO2",21,0)
        ;"NOTE: This requires that patch TMG-CPRS-TEXTOBJ-PARAM*1.0*1 or later
"RTN","TMGTIUO2",22,0)
        ;"      be installed, to allow passing in of parameters from the CPRS client.
"RTN","TMGTIUO2",23,0)
        ;"Input: DFN -- This should be the IEN of the currently open patient
"RTN","TMGTIUO2",24,0)
        ;"       Param -- Field(s)^Flags^FormatString.  Details below
"RTN","TMGTIUO2",25,0)
        ;"            Field(s) -- required.  Options for input:
"RTN","TMGTIUO2",26,0)
        ;"                -  A single field number or name
"RTN","TMGTIUO2",27,0)
        ;"                -  A list of field numbers (or names), separated by semicolons
"RTN","TMGTIUO2",28,0)
        ;"                -  A range of field numbers (or names), in the form M:N,
"RTN","TMGTIUO2",29,0)
        ;"                         where M and N are the end points of the inclusive range.
"RTN","TMGTIUO2",30,0)
        ;"                         All field numbers within this range are retrieved.
"RTN","TMGTIUO2",31,0)
        ;"                -  A '*' for all fields at the top level (no sub-multiple record).
"RTN","TMGTIUO2",32,0)
        ;"                -  A '**' for all fields including all fields and data in sub-multiple fields.
"RTN","TMGTIUO2",33,0)
        ;"                -  Field number (or name) of a multiple followed by an * to indicate all
"RTN","TMGTIUO2",34,0)
        ;"                         fields and records in the sub-multiple for that field.
"RTN","TMGTIUO2",35,0)
        ;"                Invalid field names will be ignored
"RTN","TMGTIUO2",36,0)
        ;"            Flags -- Optional.
"RTN","TMGTIUO2",37,0)
        ;"                -  'F' -- include field name in results with value.  e.g. "AGE: 43" instead of just "43"
"RTN","TMGTIUO2",38,0)
        ;"                -         This flag is ignored if a FormatString is provided (see below)
"RTN","TMGTIUO2",39,0)
        ;"                -  'S' -- Keep all data values on a single line, separated by ';'.
"RTN","TMGTIUO2",40,0)
        ;"                -         If flag not provided, and multiple data fields are requested,
"RTN","TMGTIUO2",41,0)
        ;"                -         then the default is that each data value will be separated by a
"RTN","TMGTIUO2",42,0)
        ;"                -         CRLF [$C(13)_$C(10)]
"RTN","TMGTIUO2",43,0)
        ;"                -         This flag is ignored if a FormatString is provided (see below)
"RTN","TMGTIUO2",44,0)
        ;"                -  'R' -- Resolve fields to NAMES, even if a field NUMBER was used for input request
"RTN","TMGTIUO2",45,0)
        ;"                -         Note: this will affect the sorting order of the output (see FormatString
"RTN","TMGTIUO2",46,0)
        ;"                -         info below).  I.e. if R not specified, and field NUMBERS are used for input,
"RTN","TMGTIUO2",47,0)
        ;"                -         then results will be returned in numerical field number order by default.
"RTN","TMGTIUO2",48,0)
        ;"                -         If R is specified, then field numbers are converted to field NAMES, and that
"RTN","TMGTIUO2",49,0)
        ;"                -         is used to determine the order of output.
"RTN","TMGTIUO2",50,0)
        ;"                -  'N' -- Don't return values for empty fields.  This is helpful if ALL fields
"RTN","TMGTIUO2",51,0)
        ;"                -         were requested via '*'
"RTN","TMGTIUO2",52,0)
        ;"            FormatString -- A string to determine how results are passed back....
"RTN","TMGTIUO2",53,0)
        ;"                NOTE: without a format string, results will be passed back in the order returned
"RTN","TMGTIUO2",54,0)
        ;"                      by fileman.  I.e. if user requested fields "SEX;.01;AGE", then Fileman will
"RTN","TMGTIUO2",55,0)
        ;"                      place results into an array, which MUMPS will sort alphabetically, e.g.
"RTN","TMGTIUO2",56,0)
        ;"                      .01, then AGE, then SEX.  If "*" fields are requested, it would be even
"RTN","TMGTIUO2",57,0)
        ;"                      more complex.  A format string will allow the user to specify ORDER.
"RTN","TMGTIUO2",58,0)
        ;"                Format: e.g. "Any arbitrary text %FieldNameOrNum% more text %FieldNameOrNum% ..."
"RTN","TMGTIUO2",59,0)
        ;"                  (The goal was to follow the method used by printf in the c language.)
"RTN","TMGTIUO2",60,0)
        ;"                  -  Any arbitrary text can be included.
"RTN","TMGTIUO2",61,0)
        ;"                  -  Field numbers or names should be enclosed by the '%' character
"RTN","TMGTIUO2",62,0)
        ;"                       These will be replaced with actual data values.
"RTN","TMGTIUO2",63,0)
        ;"                  - '\n' can be included to specify line breaks
"RTN","TMGTIUO2",64,0)
        ;"                  - '%%' will be used to show a '%' in the output text
"RTN","TMGTIUO2",65,0)
        ;"                  - Invalid, or non-matching, field names/numbers will be ignored.
"RTN","TMGTIUO2",66,0)
        ;"
"RTN","TMGTIUO2",67,0)
        ;"Results: returns a string that will be sent back to CPRS, to be included in a text note
"RTN","TMGTIUO2",68,0)
        ;"NOTE: I have chosen to make this function work with only file 2 (PATIENT FILE).  I think
"RTN","TMGTIUO2",69,0)
        ;"      it could be a security violation if any CPRS user was able to look at any arbitrary file.
"RTN","TMGTIUO2",70,0)
        ;"
"RTN","TMGTIUO2",71,0)
        ;"Examples of PARAM inputs:
"RTN","TMGTIUO2",72,0)
        ;"    '.01'     -- returns .01 field, which is the patients NAME, e.g. "SMITH,JOHN A"
"RTN","TMGTIUO2",73,0)
        ;"    'NAME'    -- returns same value as above, e.g. "SMITH,JOHN A"
"RTN","TMGTIUO2",74,0)
        ;"    'NAME^F'  -- e.g result "NAME: SMITH,JOHN A"
"RTN","TMGTIUO2",75,0)
        ;"    'NAME;SEX;AGE^F' --> "AGE: 34"_$C(13)_$C(10)_"NAME: SMITH,JOHN A"_$C(13)_$C(10)_"SEX: MALE"
"RTN","TMGTIUO2",76,0)
        ;"    'NAME;SEX;AGE^S' --> "34; SMITH,JOHN A; MALE"
"RTN","TMGTIUO2",77,0)
        ;"    'NAME;SEX;AGE^^"NAME: %NAME%, %AGE% yrs., %SEX%"' --> "NAME: SMITH,JOHN A, 34 YRS., MALE"
"RTN","TMGTIUO2",78,0)
        ;"
"RTN","TMGTIUO2",79,0)
        NEW TMGFLDS,TMGFLAGS
"RTN","TMGTIUO2",80,0)
        NEW TMGFILE SET TMGFILE=2
"RTN","TMGTIUO2",81,0)
        NEW RESULT SET RESULT=""
"RTN","TMGTIUO2",82,0)
        SET PARAM=$GET(PARAM)
"RTN","TMGTIUO2",83,0)
        SET TMGFLDS=$PIECE(PARAM,"^",1)
"RTN","TMGTIUO2",84,0)
        IF TMGFLDS="" DO  GOTO GPDN
"RTN","TMGTIUO2",85,0)
        . SET RESULT="ERROR: No input parameter.  Example of use: |TMG PATIENT FLD{AGE}|"
"RTN","TMGTIUO2",86,0)
        SET DFN=$GET(DFN)
"RTN","TMGTIUO2",87,0)
        IF +DFN'>0 DO  GOTO GPDN
"RTN","TMGTIUO2",88,0)
        . SET RESULT="ERROR: Internal patient value DFN not defined.  Contact IRM"
"RTN","TMGTIUO2",89,0)
        NEW TMGIENS SET TMGIENS=DFN_","
"RTN","TMGTIUO2",90,0)
        SET TMGFLAGS=""
"RTN","TMGTIUO2",91,0)
        NEW TMGTEMP SET TMGTEMP=$$UP^XLFSTR($PIECE(PARAM,"^",2))
"RTN","TMGTIUO2",92,0)
        IF TMGTEMP["N" SET TMGFLAGS=TMGFLAGS_"N"
"RTN","TMGTIUO2",93,0)
        IF TMGTEMP["F" SET TMGFLAGS=TMGFLAGS_"R"
"RTN","TMGTIUO2",94,0)
        NEW TMGFORMAT SET TMGFORMAT=$PIECE(PARAM,"^",3)
"RTN","TMGTIUO2",95,0)
        NEW TMGOUT,TMGMSG
"RTN","TMGTIUO2",96,0)
        DO GETS^DIQ(TMGFILE,TMGIENS,TMGFLDS,TMGFLAGS,"TMGOUT","TMGMSG")
"RTN","TMGTIUO2",97,0)
        IF $DATA(TMGMSG("DIERR")) DO  GOTO GPDN
"RTN","TMGTIUO2",98,0)
        . SET RESULT=$$GetErrStr^TMGDEBUG(.TMGMSG)
"RTN","TMGTIUO2",99,0)
        NEW FLD,FLDNAME
"RTN","TMGTIUO2",100,0)
        SET FLD=""
"RTN","TMGTIUO2",101,0)
        IF TMGFORMAT="" DO
"RTN","TMGTIUO2",102,0)
        . FOR  SET FLD=$ORDER(TMGOUT(TMGFILE,TMGIENS,FLD)) QUIT:(FLD="")  DO
"RTN","TMGTIUO2",103,0)
        . . IF $DATA(TMGOUT(TMGFILE,TMGIENS,FLD,0)) QUIT  ;"For now, WP fields are not supported.  Could add later if needed.
"RTN","TMGTIUO2",104,0)
        . . NEW VALUE SET VALUE=$GET(TMGOUT(TMGFILE,TMGIENS,FLD))
"RTN","TMGTIUO2",105,0)
        . . IF VALUE="",TMGTEMP["N" QUIT
"RTN","TMGTIUO2",106,0)
        . . IF RESULT'="" DO
"RTN","TMGTIUO2",107,0)
        . . . IF TMGTEMP["S" SET RESULT=RESULT_"; "
"RTN","TMGTIUO2",108,0)
        . . . ELSE  SET RESULT=RESULT_$CHAR(13)_$CHAR(10)
"RTN","TMGTIUO2",109,0)
        . . IF TMGTEMP["F" DO
"RTN","TMGTIUO2",110,0)
        . . . IF FLD'=+FLD SET FLDNAME=FLD
"RTN","TMGTIUO2",111,0)
        . . . ELSE  SET FLDNAME=$PIECE($GET(^DD(TMGFILE,FLD,0)),"^",1)
"RTN","TMGTIUO2",112,0)
        . . . SET RESULT=RESULT_FLDNAME_": "
"RTN","TMGTIUO2",113,0)
        . . SET RESULT=RESULT_VALUE
"RTN","TMGTIUO2",114,0)
        ELSE  DO  ;"Handle format strings.
"RTN","TMGTIUO2",115,0)
        . SET RESULT=TMGFORMAT
"RTN","TMGTIUO2",116,0)
        . FOR  QUIT:(RESULT'["%")  DO
"RTN","TMGTIUO2",117,0)
        . . NEW SUBA,SUBB
"RTN","TMGTIUO2",118,0)
        . . SET SUBA=$PIECE(RESULT,"%",1)
"RTN","TMGTIUO2",119,0)
        . . SET FLD=$PIECE(RESULT,"%",2)
"RTN","TMGTIUO2",120,0)
        . . SET SUBB=$PIECE(RESULT,"%",3,999)
"RTN","TMGTIUO2",121,0)
        . . NEW VALUE
"RTN","TMGTIUO2",122,0)
        . . IF FLD="" SET VALUE="<@!@>"  ;"protect %%, later convert back to '%'
"RTN","TMGTIUO2",123,0)
        . . ELSE  SET VALUE=$GET(TMGOUT(TMGFILE,TMGIENS,FLD))
"RTN","TMGTIUO2",124,0)
        . . IF VALUE="" DO
"RTN","TMGTIUO2",125,0)
        . . . IF FLD=+FLD DO
"RTN","TMGTIUO2",126,0)
        . . . . SET FLD=$PIECE($GET(^DD(TMGFILE,FLD,0)),"^",1) ;"Convert # to name
"RTN","TMGTIUO2",127,0)
        . . . ELSE  DO
"RTN","TMGTIUO2",128,0)
        . . . . SET FLD=$ORDER(^DD(TMGFILE,"B",FLD,"")) ;"Convert name to #
"RTN","TMGTIUO2",129,0)
        . . . IF FLD'="" SET VALUE=$GET(TMGOUT(TMGFILE,TMGIENS,FLD))
"RTN","TMGTIUO2",130,0)
        . . . IF VALUE="" SET VALUE="??"
"RTN","TMGTIUO2",131,0)
        . . SET RESULT=SUBA_VALUE_SUBB
"RTN","TMGTIUO2",132,0)
        . NEW TMGALT
"RTN","TMGTIUO2",133,0)
        . SET TMGALT("<@!@>")="%"
"RTN","TMGTIUO2",134,0)
        . SET TMGALT("\n")=$CHAR(13)_$CHAR(10)
"RTN","TMGTIUO2",135,0)
        . SET RESULT=$$REPLACE^XLFSTR(RESULT,.TMGALT)
"RTN","TMGTIUO2",136,0)
        ;
"RTN","TMGTIUO2",137,0)
GPDN    QUIT RESULT
"SEC","^DD",8925.1,8925.1,.01,8.5)

"SEC","^DIC",8925.1,8925.1,0,"AUDIT")
@
"SEC","^DIC",8925.1,8925.1,0,"DD")
@
"SEC","^DIC",8925.1,8925.1,0,"DEL")
@
"SEC","^DIC",8925.1,8925.1,0,"RD")
@
"SEC","^DIC",8925.1,8925.1,0,"WR")
@
"VER")
8.0^22.0
"^DD",8925.1,8925.1,0)
FIELD^^99^54
"^DD",8925.1,8925.1,0,"DDA")
N
"^DD",8925.1,8925.1,0,"DT")
2970227
"^DD",8925.1,8925.1,0,"ID","W.04")
W "   ",@("$P($P($C(59)_$S($D(^DD(8925.1,.04,0)):$P(^(0),U,3),1:0)_$E("_DIC_"Y,0),0),$C(59)_$P(^(0),U,4)_"":"",2),$C(59),1)")
"^DD",8925.1,8925.1,0,"ID","W.1501")
S %I=Y,Y=$S('$D(^(15)):"",$D(^TIU(8926.1,+$P(^(15),U,1),0))#2:$P(^(0),U,1),1:"") N DIERR S:$L(Y) Y=$$EXTERNAL^DILFD(8926.1,.01,"",Y,"DIERR") D:$L(Y) EN^DDIOL("Std Title: "_Y,"","!?6") S Y=%I K %I
"^DD",8925.1,8925.1,0,"IX","AC",8925.1,.06)

"^DD",8925.1,8925.1,0,"IX","ACL",8925.1,.01)

"^DD",8925.1,8925.1,0,"IX","ACL02",8925.1,.02)

"^DD",8925.1,8925.1,0,"IX","ACL03",8925.1,.03)

"^DD",8925.1,8925.1,0,"IX","ACL07",8925.1,.07)

"^DD",8925.1,8925.1,0,"IX","ACL1001",8925.14,.01)

"^DD",8925.1,8925.1,0,"IX","AD",8925.14,.01)

"^DD",8925.1,8925.1,0,"IX","ALOINC",8925.1,1501)

"^DD",8925.1,8925.1,0,"IX","AM",8925.1,99)

"^DD",8925.1,8925.1,0,"IX","AM1",8925.1,.03)

"^DD",8925.1,8925.1,0,"IX","AMM",8925.14,.01)

"^DD",8925.1,8925.1,0,"IX","AMM2",8925.14,2)

"^DD",8925.1,8925.1,0,"IX","AMM3",8925.14,3)

"^DD",8925.1,8925.1,0,"IX","AMM4",8925.14,4)

"^DD",8925.1,8925.1,0,"IX","AP",8925.1,.05)

"^DD",8925.1,8925.1,0,"IX","APOST",8925.1,.14)

"^DD",8925.1,8925.1,0,"IX","AS",8925.1,.07)

"^DD",8925.1,8925.1,0,"IX","AT",8925.1,.04)

"^DD",8925.1,8925.1,0,"IX","B",8925.1,.01)

"^DD",8925.1,8925.1,0,"IX","C",8925.1,.02)

"^DD",8925.1,8925.1,0,"IX","D",8925.1,.03)

"^DD",8925.1,8925.1,0,"IX","E",8925.1,.01)

"^DD",8925.1,8925.1,0,"NM","TIU DOCUMENT DEFINITION")

"^DD",8925.1,8925.1,0,"PT",26.11,.07)

"^DD",8925.1,8925.1,0,"PT",26.15,.07)

"^DD",8925.1,8925.1,0,"PT",142.14,.01)

"^DD",8925.1,8925.1,0,"PT",702.01,.04)

"^DD",8925.1,8925.1,0,"PT",703.91,.05)

"^DD",8925.1,8925.1,0,"PT",783.9,.04)

"^DD",8925.1,8925.1,0,"PT",783.9,.05)

"^DD",8925.1,8925.1,0,"PT",783.9,.06)

"^DD",8925.1,8925.1,0,"PT",2006.5841,6)

"^DD",8925.1,8925.1,0,"PT",8925,.01)

"^DD",8925.1,8925.1,0,"PT",8925,.04)

"^DD",8925.1,8925.1,0,"PT",8925.14,.01)

"^DD",8925.1,8925.1,0,"PT",8925.95,.01)

"^DD",8925.1,8925.1,0,"PT",8925.98,.02)

"^DD",8925.1,8925.1,0,"PT",8925.98,.03)

"^DD",8925.1,8925.1,0,"PT",8925.9801,.01)

"^DD",8925.1,8925.1,0,"PT",8927,.19)

"^DD",8925.1,8925.1,0,"PT",8930.1,.01)

"^DD",8925.1,8925.1,0,"VRPK")
TEXT INTEGRATION UTILITIES
"^DD",8925.1,8925.1,.01,0)
NAME^RFX^^0;1^S:$L($T(^TIULS)) X=$$UPPER^TIULS(X) K:$L(X)>60!($L(X)<3)!'(X'?1P.E) X I $D(X),+$G(DA) K:$$BADNAP^TIUFLF1(X,+$G(DA)) X
"^DD",8925.1,8925.1,.01,.1)

"^DD",8925.1,8925.1,.01,1,0)
^.1
"^DD",8925.1,8925.1,.01,1,1,0)
8925.1^B
"^DD",8925.1,8925.1,.01,1,1,1)
S ^TIU(8925.1,"B",$E(X,1,60),DA)=""
"^DD",8925.1,8925.1,.01,1,1,2)
K ^TIU(8925.1,"B",$E(X,1,60),DA)
"^DD",8925.1,8925.1,.01,1,2,0)
8925.1^E^KWIC
"^DD",8925.1,8925.1,.01,1,2,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 ^TIU(8925.1,"E",I,DA)=""
"^DD",8925.1,8925.1,.01,1,2,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 ^TIU(8925.1,"E",I,DA)
"^DD",8925.1,8925.1,.01,1,2,"%D",0)
^^2^2^2960302^
"^DD",8925.1,8925.1,.01,1,2,"%D",1,0)
This KWIK cross-reference on document name will allow look-up based on
"^DD",8925.1,8925.1,.01,1,2,"%D",2,0)
sub-names, etc.
"^DD",8925.1,8925.1,.01,1,2,"DT")
2960302
"^DD",8925.1,8925.1,.01,1,3,0)
8925.1^ACL^MUMPS
"^DD",8925.1,8925.1,.01,1,3,1)
D SACL^TIUDD1(X,.01)
"^DD",8925.1,8925.1,.01,1,3,2)
D KACL^TIUDD1(X,.01)
"^DD",8925.1,8925.1,.01,1,3,"%D",0)
^^7^7^3040831^
"^DD",8925.1,8925.1,.01,1,3,"%D",1,0)
This is a complex cross-reference on the .01 (NAME) field.  Its format
"^DD",8925.1,8925.1,.01,1,3,"%D",2,0)
will be as follows:
"^DD",8925.1,8925.1,.01,1,3,"%D",3,0)
 
"^DD",8925.1,8925.1,.01,1,3,"%D",4,0)
   ^TIU(8925.1,"ACL",Parent document class IEN, Title NAME, Title IEN)=""
"^DD",8925.1,8925.1,.01,1,3,"%D",5,0)
 
"^DD",8925.1,8925.1,.01,1,3,"%D",6,0)
The purpose of this cross-reference will be to help CPRS GUI perform 
"^DD",8925.1,8925.1,.01,1,3,"%D",7,0)
faster title look-ups by document class.
"^DD",8925.1,8925.1,.01,1,3,"DT")
2971016
"^DD",8925.1,8925.1,.01,3)
This is the technical name, 3-60 characters, not starting with punctuation.  If OBJECT, Name must be unique among all object Names, Abbreviations, and Print Names.
"^DD",8925.1,8925.1,.01,4)
D NAME^TIUFXHLX:$G(TIUFXNOD)["Add/Create"&($G(TIUFSTMP)="T")
"^DD",8925.1,8925.1,.01,21,0)
^^51^51^2980127^^^^
"^DD",8925.1,8925.1,.01,21,1,0)
The name of a Document Definition entry (.01 field) must be between 3
"^DD",8925.1,8925.1,.01,21,2,0)
and 60 characters long and may not begin with a punctuation character.
"^DD",8925.1,8925.1,.01,21,3,0)
Although names can be entered in any case, they are transformed to
"^DD",8925.1,8925.1,.01,21,4,0)
upper case before being stored.
"^DD",8925.1,8925.1,.01,21,5,0)
 
"^DD",8925.1,8925.1,.01,21,6,0)
It functions as the Technical Name of the entry.  Some sites have put KWIC
"^DD",8925.1,8925.1,.01,21,7,0)
cross references on it to get, say, all Titles from a given Service.
"^DD",8925.1,8925.1,.01,21,8,0)
 
"^DD",8925.1,8925.1,.01,21,9,0)
Name can be used when entering documents as the name of the Title being
"^DD",8925.1,8925.1,.01,21,10,0)
entered.  Print Name and Abbreviation will also be accepted.
"^DD",8925.1,8925.1,.01,21,11,0)
 
"^DD",8925.1,8925.1,.01,21,12,0)
Since it is the Technical, .01 Name, the Document Definition Utility
"^DD",8925.1,8925.1,.01,21,13,0)
(TIUF) uses this name throughout.
"^DD",8925.1,8925.1,.01,21,14,0)
 
"^DD",8925.1,8925.1,.01,21,15,0)
The .01 name differs from the Print Name, which appears in lists of
"^DD",8925.1,8925.1,.01,21,16,0)
documents and functions as the Title of the document.
"^DD",8925.1,8925.1,.01,21,17,0)
 
"^DD",8925.1,8925.1,.01,21,18,0)
It also differs from Item Menu Text (1-20 characters), which is used when
"^DD",8925.1,8925.1,.01,21,19,0)
selecting documents from 3-COLUMN MENUS.
"^DD",8925.1,8925.1,.01,21,20,0)
 
"^DD",8925.1,8925.1,.01,21,21,0)
The ORDER of names in TIUF options Edit Document Definitions and Create
"^DD",8925.1,8925.1,.01,21,22,0)
Document Definitions is by Item Sequence under the parent.  Order is
"^DD",8925.1,8925.1,.01,21,23,0)
alphabetic by Menu Text if an Item has no Item Sequence.
"^DD",8925.1,8925.1,.01,21,24,0)
 
"^DD",8925.1,8925.1,.01,21,25,0)
When a new entry is added to file 8925.1, the Document Definition Utility
"^DD",8925.1,8925.1,.01,21,26,0)
(TIUF) enters the Name as the default Print Name.  The Print Name can be
"^DD",8925.1,8925.1,.01,21,27,0)
edited if a different Print Name is desired.
"^DD",8925.1,8925.1,.01,21,28,0)
 
"^DD",8925.1,8925.1,.01,21,29,0)
File 8925.1 permits more than 1 entry with the same name as long as they
"^DD",8925.1,8925.1,.01,21,30,0)
don't have the same Type.  In that sense, NAMES are reusable.  However,
"^DD",8925.1,8925.1,.01,21,31,0)
ENTRIES are NOT reusable (except specially marked Components): an entry is
"^DD",8925.1,8925.1,.01,21,32,0)
NOT allowed to be an item under more than one parent unless it is a Shared
"^DD",8925.1,8925.1,.01,21,33,0)
Component.  (See Type Component.)
"^DD",8925.1,8925.1,.01,21,34,0)
 
"^DD",8925.1,8925.1,.01,21,35,0)
Name is a BASIC Field.
"^DD",8925.1,8925.1,.01,21,36,0)
 
"^DD",8925.1,8925.1,.01,21,37,0)
                               OBJECT Name 
"^DD",8925.1,8925.1,.01,21,38,0)
Object Names, like any other names are 3-60 characters, not starting with
"^DD",8925.1,8925.1,.01,21,39,0)
punctuation.  Sites may want to namespace object names, use the object
"^DD",8925.1,8925.1,.01,21,40,0)
Print Name as a more familiar name, and use object Abbreviation as a short
"^DD",8925.1,8925.1,.01,21,41,0)
name to embed in boilerplate text.  Unlike other Types, Object
"^DD",8925.1,8925.1,.01,21,42,0)
Abbreviation and Print Name as well as Name must be uppercase.
"^DD",8925.1,8925.1,.01,21,43,0)
 
"^DD",8925.1,8925.1,.01,21,44,0)
Object Name, Abbreviation, or Print Name can be embedded in boilerplate
"^DD",8925.1,8925.1,.01,21,45,0)
text.  Since TIU must be able to determine from this which object is
"^DD",8925.1,8925.1,.01,21,46,0)
intended, object Names, Abbreviations, and Print Names must be unique.  In
"^DD",8925.1,8925.1,.01,21,47,0)
fact, an object Name must differ not only from every other object name,
"^DD",8925.1,8925.1,.01,21,48,0)
but also from every other object Abbreviation and from every other object
"^DD",8925.1,8925.1,.01,21,49,0)
Print Name.  Same for Abbreviations and Print Names.  For example, if some
"^DD",8925.1,8925.1,.01,21,50,0)
object has abbreviation 'CND', then 'CND' cannot be used for any other
"^DD",8925.1,8925.1,.01,21,51,0)
object Name, Abbreviation, or Print Name.
"^DD",8925.1,8925.1,.01,"AUDIT")

"^DD",8925.1,8925.1,.01,"DEL",.01,0)
I 1
"^DD",8925.1,8925.1,.01,"DT")
3020107
"^DD",8925.1,8925.1,.02,0)
ABBREVIATION^FX^^0;2^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>4!($L(X)<2)!'(X?2.4A) X I $D(X),+$G(DA) K:($P(^TIU(8925.1,DA,0),U,4)="O")&('(X?2.4U)!'$D(TIUFPRIV)) X I $D(X),+$G(DA) K:$$BADNAP^TIUFLF1(X,DA) X
"^DD",8925.1,8925.1,.02,1,0)
^.1
"^DD",8925.1,8925.1,.02,1,1,0)
8925.1^C
"^DD",8925.1,8925.1,.02,1,1,1)
S ^TIU(8925.1,"C",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,.02,1,1,2)
K ^TIU(8925.1,"C",$E(X,1,30),DA)
"^DD",8925.1,8925.1,.02,1,1,"%D",0)
^^2^2^2940711^
"^DD",8925.1,8925.1,.02,1,1,"%D",1,0)
This cross reference will be used by the router/filer to identify a given
"^DD",8925.1,8925.1,.02,1,1,"%D",2,0)
report type.
"^DD",8925.1,8925.1,.02,1,1,"DT")
2921020
"^DD",8925.1,8925.1,.02,1,2,0)
8925.1^ACL02^MUMPS
"^DD",8925.1,8925.1,.02,1,2,1)
D SACL^TIUDD1(X,.02)
"^DD",8925.1,8925.1,.02,1,2,2)
D KACL^TIUDD1(X,.02)
"^DD",8925.1,8925.1,.02,1,2,"%D",0)
^^2^2^3010417^
"^DD",8925.1,8925.1,.02,1,2,"%D",1,0)
This complex cross-reference by class and name will help optimize the
"^DD",8925.1,8925.1,.02,1,2,"%D",2,0)
title look-up for the GUI.
"^DD",8925.1,8925.1,.02,1,2,"DT")
3010417
"^DD",8925.1,8925.1,.02,3)
Enter from 2 to 4 letters.  If OBJECT, Abbreviation must be unique among all object Names, Abbreviations, and Print Names, and must be uppercase.
"^DD",8925.1,8925.1,.02,21,0)
^^3^3^2990504^^^^
"^DD",8925.1,8925.1,.02,21,1,0)
Abbreviation can be entered at the Title: prompt when entering a document.
"^DD",8925.1,8925.1,.02,21,2,0)
Since all Titles with that abbreviation will then be listed, Abbreviation
"^DD",8925.1,8925.1,.02,21,3,0)
can serve to group Titles.  BASIC Field.  For Objects, see NAME.
"^DD",8925.1,8925.1,.02,"DT")
3020107
"^DD",8925.1,8925.1,.03,0)
PRINT NAME^FX^^0;3^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>60!($L(X)<3) X I $D(X),+$G(DA) K:($P(^TIU(8925.1,DA,0),U,4)="O")&('(X?3.60UPN)!'$D(TIUFPRIV)) X I $D(X),+$G(DA) K:$$BADNAP^TIUFLF1(X,DA) X
"^DD",8925.1,8925.1,.03,1,0)
^.1
"^DD",8925.1,8925.1,.03,1,1,0)
8925.1^AM1^MUMPS
"^DD",8925.1,8925.1,.03,1,1,1)
D REDO^TIUDD
"^DD",8925.1,8925.1,.03,1,1,2)
D REDO^TIUDD
"^DD",8925.1,8925.1,.03,1,1,"%D",0)
^^2^2^2950911^^^
"^DD",8925.1,8925.1,.03,1,1,"%D",1,0)
This MUMPS-type cross-reference is used to update the TIMESTAMP on both
"^DD",8925.1,8925.1,.03,1,1,"%D",2,0)
the current document, and its parents, when its PRINT NAME changes.
"^DD",8925.1,8925.1,.03,1,1,"DT")
2940720
"^DD",8925.1,8925.1,.03,1,2,0)
8925.1^D
"^DD",8925.1,8925.1,.03,1,2,1)
S ^TIU(8925.1,"D",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,.03,1,2,2)
K ^TIU(8925.1,"D",$E(X,1,30),DA)
"^DD",8925.1,8925.1,.03,1,2,"%D",0)
^^1^1^2950126^
"^DD",8925.1,8925.1,.03,1,2,"%D",1,0)
This REGULAR FileMan cross-reference by PRINT NAME will facilitate look-up.
"^DD",8925.1,8925.1,.03,1,2,"DT")
2950126
"^DD",8925.1,8925.1,.03,1,3,0)
8925.1^ACL03^MUMPS
"^DD",8925.1,8925.1,.03,1,3,1)
D SACL^TIUDD1(X,.03)
"^DD",8925.1,8925.1,.03,1,3,2)
D KACL^TIUDD1(X,.03)
"^DD",8925.1,8925.1,.03,1,3,"%D",0)
^^2^2^3010417^
"^DD",8925.1,8925.1,.03,1,3,"%D",1,0)
This complex cross-reference by class and name will help optimize the
"^DD",8925.1,8925.1,.03,1,3,"%D",2,0)
title look-up for the GUI.
"^DD",8925.1,8925.1,.03,1,3,"DT")
3010417
"^DD",8925.1,8925.1,.03,3)
Print Name is used in lists of documents and as document Title in the Patient Chart.  3-60 Characters.  If OBJECT, Print Name must be unique among object Names/Abbreviations/PrintNames, and uppercase.
"^DD",8925.1,8925.1,.03,21,0)
^^3^3^2990504^^^^
"^DD",8925.1,8925.1,.03,21,1,0)
Print Name is the name used in lists of documents.  For entries of Type
"^DD",8925.1,8925.1,.03,21,2,0)
Title, Print Name is used as the document Title in the Patient Chart.
"^DD",8925.1,8925.1,.03,21,3,0)
BASIC field.  For Objects, see NAME.
"^DD",8925.1,8925.1,.03,"DT")
3020107
"^DD",8925.1,8925.1,.04,0)
TYPE^RSX^CL:CLASS;DC:DOCUMENT CLASS;DOC:TITLE;CO:COMPONENT;O:OBJECT;^0;4^K:'$G(TIUFPRIV) X
"^DD",8925.1,8925.1,.04,1,0)
^.1
"^DD",8925.1,8925.1,.04,1,1,0)
8925.1^AT
"^DD",8925.1,8925.1,.04,1,1,1)
S ^TIU(8925.1,"AT",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,.04,1,1,2)
K ^TIU(8925.1,"AT",$E(X,1,30),DA)
"^DD",8925.1,8925.1,.04,1,1,3)
Please don't delete!
"^DD",8925.1,8925.1,.04,1,1,"%D",0)
^^2^2^2950615^
"^DD",8925.1,8925.1,.04,1,1,"%D",1,0)
This regular cross reference is used for listing Document Definitions by
"^DD",8925.1,8925.1,.04,1,1,"%D",2,0)
Type.
"^DD",8925.1,8925.1,.04,1,1,"DT")
2950615
"^DD",8925.1,8925.1,.04,3)
Types Class and Document Class group documents.  Titles are used to enter documents.  Components are sections of documents.  Objects are M code for use in Boilerplate Text.
"^DD",8925.1,8925.1,.04,4)

"^DD",8925.1,8925.1,.04,21,0)
^^99^99^2970521^^
"^DD",8925.1,8925.1,.04,21,1,0)
Type determines the nature of the entry and what sort of items the entry
"^DD",8925.1,8925.1,.04,21,2,0)
may have. There are 5 possible types:
"^DD",8925.1,8925.1,.04,21,3,0)
 
"^DD",8925.1,8925.1,.04,21,4,0)
CL CLASS:  Classes group documents.
"^DD",8925.1,8925.1,.04,21,5,0)
 
"^DD",8925.1,8925.1,.04,21,6,0)
Example: "Progress Notes" is a class with many kinds of progress notes
"^DD",8925.1,8925.1,.04,21,7,0)
under it.
"^DD",8925.1,8925.1,.04,21,8,0)
 
"^DD",8925.1,8925.1,.04,21,9,0)
Classes may themselves be subdivided into items of Type Class or may have
"^DD",8925.1,8925.1,.04,21,10,0)
items of Type Document Class if no further Class subdivisions are desired.
"^DD",8925.1,8925.1,.04,21,11,0)
 
"^DD",8925.1,8925.1,.04,21,12,0)
If a hierarchy deeper than Class-Document Class-Title is desired, Class is
"^DD",8925.1,8925.1,.04,21,13,0)
the place to insert another level into the hierarchy: Class-Class-Document
"^DD",8925.1,8925.1,.04,21,14,0)
Class-Title.
"^DD",8925.1,8925.1,.04,21,15,0)
 
"^DD",8925.1,8925.1,.04,21,16,0)
Besides grouping documents, Classes also store behavior which is then
"^DD",8925.1,8925.1,.04,21,17,0)
inherited by lower level entries.
"^DD",8925.1,8925.1,.04,21,18,0)
 
"^DD",8925.1,8925.1,.04,21,19,0)
DC DOCUMENT CLASS: Document Classes group documents.  Document Class is
"^DD",8925.1,8925.1,.04,21,20,0)
the lowest level of class, and has items of Type Title under it.
"^DD",8925.1,8925.1,.04,21,21,0)
 
"^DD",8925.1,8925.1,.04,21,22,0)
Example: "Day Pass Note" could be a Document Class under class Progress
"^DD",8925.1,8925.1,.04,21,23,0)
Note.
"^DD",8925.1,8925.1,.04,21,24,0)
 
"^DD",8925.1,8925.1,.04,21,25,0)
Document Classes also store behavior which is then inherited by lower
"^DD",8925.1,8925.1,.04,21,26,0)
entries.
"^DD",8925.1,8925.1,.04,21,27,0)
 
"^DD",8925.1,8925.1,.04,21,28,0)
TL TITLE:  Titles are used to enter documents.  They store the behavior
"^DD",8925.1,8925.1,.04,21,29,0)
of the documents which use them.
"^DD",8925.1,8925.1,.04,21,30,0)
 
"^DD",8925.1,8925.1,.04,21,31,0)
Titles may have predefined boilerplate ("Overprint") text.  They may have
"^DD",8925.1,8925.1,.04,21,32,0)
Components as items.  Boilerplate Text can have objects in it.
"^DD",8925.1,8925.1,.04,21,33,0)
 
"^DD",8925.1,8925.1,.04,21,34,0)
Examples: "Routine Day Pass Note" could be a Title under document class
"^DD",8925.1,8925.1,.04,21,35,0)
Day Pass Note.  Another example might be "Exceptional Circumstances Day
"^DD",8925.1,8925.1,.04,21,36,0)
Pass Note."
"^DD",8925.1,8925.1,.04,21,37,0)
 
"^DD",8925.1,8925.1,.04,21,38,0)
Titles store their own behavior.  They also inherit behavior from higher
"^DD",8925.1,8925.1,.04,21,39,0)
levels of the hierarchy.  However, behavior stored in the Title itself
"^DD",8925.1,8925.1,.04,21,40,0)
overrides inherited behavior.
"^DD",8925.1,8925.1,.04,21,41,0)
 
"^DD",8925.1,8925.1,.04,21,42,0)
CO COMPONENT: Components are "sections" or "pieces" of documents.
"^DD",8925.1,8925.1,.04,21,43,0)
In the Hierarchy, Components are hung as items from Titles.
"^DD",8925.1,8925.1,.04,21,44,0)
 
"^DD",8925.1,8925.1,.04,21,45,0)
Examples: "Reason for Pass" could be a component of Routine Day Pass Note.
"^DD",8925.1,8925.1,.04,21,46,0)
Subjective is a component of a SOAP Note.
"^DD",8925.1,8925.1,.04,21,47,0)
 
"^DD",8925.1,8925.1,.04,21,48,0)
Components may have (sub)Components as items.  They may have Boilerplate
"^DD",8925.1,8925.1,.04,21,49,0)
Text.  Components may be designated Shared (see Field Description for
"^DD",8925.1,8925.1,.04,21,50,0)
Shared). Shared Components are shown in Document Definition Utility
"^DD",8925.1,8925.1,.04,21,51,0)
Displays as Type: 'CO S'.
"^DD",8925.1,8925.1,.04,21,52,0)
 
"^DD",8925.1,8925.1,.04,21,53,0)
There are advantages and disadvantages in splitting a document up into
"^DD",8925.1,8925.1,.04,21,54,0)
separate components (rather than writing sections into the Boilerplate
"^DD",8925.1,8925.1,.04,21,55,0)
Text of the Title): Since Components are stored as separate file entries,
"^DD",8925.1,8925.1,.04,21,56,0)
they are inherently accessable and even 'moveable'. Using Fileman, sites
"^DD",8925.1,8925.1,.04,21,57,0)
can access components of documents the same way they can access documents
"^DD",8925.1,8925.1,.04,21,58,0)
for reports, etc.. Also, in the future, TIU may have options to move/copy
"^DD",8925.1,8925.1,.04,21,59,0)
certain components from one document into another.  The disadvantage is
"^DD",8925.1,8925.1,.04,21,60,0)
speed: Components make the structure more complex and therefore slow down
"^DD",8925.1,8925.1,.04,21,61,0)
processing.
"^DD",8925.1,8925.1,.04,21,62,0)
 
"^DD",8925.1,8925.1,.04,21,63,0)
O OBJECT: Objects are names which may be embedded in the predefined
"^DD",8925.1,8925.1,.04,21,64,0)
boilerplate text of Titles. Example: 'PATIENT AGE'.  Objects are typed
"^DD",8925.1,8925.1,.04,21,65,0)
into the boilerplate text of a Title, enclosed by '|'s.  For example,
"^DD",8925.1,8925.1,.04,21,66,0)
suppose a Title has boilerplate text:
"^DD",8925.1,8925.1,.04,21,67,0)
 
"^DD",8925.1,8925.1,.04,21,68,0)
        Patient is a healthy |PATIENT AGE| year old male ...
"^DD",8925.1,8925.1,.04,21,69,0)
 
"^DD",8925.1,8925.1,.04,21,70,0)
Then a user who enters such a note for a patient known by the system to be
"^DD",8925.1,8925.1,.04,21,71,0)
56 years old would be presented with the text:
"^DD",8925.1,8925.1,.04,21,72,0)
 
"^DD",8925.1,8925.1,.04,21,73,0)
        Patient is a healthy 56 year old male ...
"^DD",8925.1,8925.1,.04,21,74,0)
 
"^DD",8925.1,8925.1,.04,21,75,0)
The user can then add to the text and or edit the text, including the age
"^DD",8925.1,8925.1,.04,21,76,0)
(56) of the patient.  From this point on, the patient age (56) is regular
"^DD",8925.1,8925.1,.04,21,77,0)
text and is not updated in this note.
"^DD",8925.1,8925.1,.04,21,78,0)
 
"^DD",8925.1,8925.1,.04,21,79,0)
Objects must always have uppercase names, abbreviations, and print names.
"^DD",8925.1,8925.1,.04,21,80,0)
When embedding objects in boilerplate text, users may embed any of these
"^DD",8925.1,8925.1,.04,21,81,0)
three (name, abbreviation, print name) in boilerplate text, enclosed by
"^DD",8925.1,8925.1,.04,21,82,0)
'|'s.  Objects must always be embedded in uppercase.
"^DD",8925.1,8925.1,.04,21,83,0)
 
"^DD",8925.1,8925.1,.04,21,84,0)
Objects are stored in the Document Definition File, but are not part of
"^DD",8925.1,8925.1,.04,21,85,0)
the Hierarchy.  They are accessible through the Option Create Objects.
"^DD",8925.1,8925.1,.04,21,86,0)
(They are also accessible through the Option Sort Document Definitions, by
"^DD",8925.1,8925.1,.04,21,87,0)
selecting Sort by Type and selecting Type Object.)
"^DD",8925.1,8925.1,.04,21,88,0)
 
"^DD",8925.1,8925.1,.04,21,89,0)
TIU exports a small library of objects.  Sites can also create their own.
"^DD",8925.1,8925.1,.04,21,90,0)
 
"^DD",8925.1,8925.1,.04,21,91,0)
Only an owner can edit an object and should do so only after consulting
"^DD",8925.1,8925.1,.04,21,92,0)
with others who use it.  The object must be inactive for editing.  It
"^DD",8925.1,8925.1,.04,21,93,0)
should be thoroughly tested.  See Object Status, under Status.
"^DD",8925.1,8925.1,.04,21,94,0)
 
"^DD",8925.1,8925.1,.04,21,95,0)
Entries of type Object cannot be changed to any other type.  Entries of
"^DD",8925.1,8925.1,.04,21,96,0)
type Class, Document Class, Title, or Component cannot be changed to type
"^DD",8925.1,8925.1,.04,21,97,0)
Object.
"^DD",8925.1,8925.1,.04,21,98,0)
 
"^DD",8925.1,8925.1,.04,21,99,0)
Type is a BASIC field.
"^DD",8925.1,8925.1,.04,"DT")
2970114
"^DD",8925.1,8925.1,.05,0)
PERSONAL OWNER^P200'X^VA(200,^0;5^Q
"^DD",8925.1,8925.1,.05,1,0)
^.1
"^DD",8925.1,8925.1,.05,1,1,0)
8925.1^AP
"^DD",8925.1,8925.1,.05,1,1,1)
S ^TIU(8925.1,"AP",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,.05,1,1,2)
K ^TIU(8925.1,"AP",$E(X,1,30),DA)
"^DD",8925.1,8925.1,.05,1,1,3)
Please don't delete!
"^DD",8925.1,8925.1,.05,1,1,"%D",0)
^^2^2^2950615^
"^DD",8925.1,8925.1,.05,1,1,"%D",1,0)
This regular cross reference is used for listing Document Definitions by
"^DD",8925.1,8925.1,.05,1,1,"%D",2,0)
Personal Owner.
"^DD",8925.1,8925.1,.05,1,1,"DT")
2950615
"^DD",8925.1,8925.1,.05,3)
Enter Person who can edit entry.  If owned by Class rather than Person, delete Personal Owner by typing '@' at Personal Owner prompt, and then enter Class Owner.
"^DD",8925.1,8925.1,.05,4)

"^DD",8925.1,8925.1,.05,21,0)
^^41^41^2970520^
"^DD",8925.1,8925.1,.05,21,1,0)
Document Definition Ownership has nothing to do with who can USE the entry
"^DD",8925.1,8925.1,.05,21,2,0)
to enter a document.  It determines responsibilty for the Document
"^DD",8925.1,8925.1,.05,21,3,0)
Definition itself.
"^DD",8925.1,8925.1,.05,21,4,0)
 
"^DD",8925.1,8925.1,.05,21,5,0)
An entry can be EDITED by its owner. (The Manager menu permits override of
"^DD",8925.1,8925.1,.05,21,6,0)
ownership so that Ownership can be assigned to a clinician who can then
"^DD",8925.1,8925.1,.05,21,7,0)
fill in boilerplate text with the Clinician menu, while the Manager can
"^DD",8925.1,8925.1,.05,21,8,0)
still edit the entry, since there are many fields the clinician does not
"^DD",8925.1,8925.1,.05,21,9,0)
have access to.)  Exception: the Manager menu does NOT override ownership
"^DD",8925.1,8925.1,.05,21,10,0)
of Objects or of Shared Components.  Only owners can edit Objects and
"^DD",8925.1,8925.1,.05,21,11,0)
Shared Components, regardless of menu.
"^DD",8925.1,8925.1,.05,21,12,0)
 
"^DD",8925.1,8925.1,.05,21,13,0)
If Title owner edits the boilerplate text of the Title, that person can
"^DD",8925.1,8925.1,.05,21,14,0)
edit the boilerplate text of all components of the Title as well, without
"^DD",8925.1,8925.1,.05,21,15,0)
regard to component ownership. In order to edit components individually,
"^DD",8925.1,8925.1,.05,21,16,0)
however, the user must own the component.  This allows users to assign
"^DD",8925.1,8925.1,.05,21,17,0)
ownership of components to different people, for example, for (future)
"^DD",8925.1,8925.1,.05,21,18,0)
multidisciplinary documents.
"^DD",8925.1,8925.1,.05,21,19,0)
 
"^DD",8925.1,8925.1,.05,21,20,0)
A PERSONAL OWNER is a person who uniquely owns the entry. An entry may
"^DD",8925.1,8925.1,.05,21,21,0)
have a Personal Owner OR a Class Owner but not both. When entering a
"^DD",8925.1,8925.1,.05,21,22,0)
Personal Owner, be sure to delete any existing Class Owner.
"^DD",8925.1,8925.1,.05,21,23,0)
 
"^DD",8925.1,8925.1,.05,21,24,0)
The Document Definition Utility TIUF uses the term 'Individual Owner'.
"^DD",8925.1,8925.1,.05,21,25,0)
Someone is an Individual Owner of an entry if s/he is the personal owner
"^DD",8925.1,8925.1,.05,21,26,0)
OR, if the entry is CLASS Owned, if s/he belongs to the Owner Class.
"^DD",8925.1,8925.1,.05,21,27,0)
 
"^DD",8925.1,8925.1,.05,21,28,0)
The Document Definition Utility TIUF enters the user as the Personal Owner
"^DD",8925.1,8925.1,.05,21,29,0)
if a user enters a new entry without assigning ownership. This person can
"^DD",8925.1,8925.1,.05,21,30,0)
then reassign ownership if they choose.
"^DD",8925.1,8925.1,.05,21,31,0)
 
"^DD",8925.1,8925.1,.05,21,32,0)
If the person responsible for an entry plays a role corresponding to a
"^DD",8925.1,8925.1,.05,21,33,0)
User Class, e.g. Clinical Coordinator, it may be more efficient to assign
"^DD",8925.1,8925.1,.05,21,34,0)
ownership to the class rather than to the person.  Owners are then
"^DD",8925.1,8925.1,.05,21,35,0)
automatically updated as the class is updated.
"^DD",8925.1,8925.1,.05,21,36,0)
 
"^DD",8925.1,8925.1,.05,21,37,0)
Editing privilege is affected not only by Owner but also by Status, by
"^DD",8925.1,8925.1,.05,21,38,0)
Shared, by In Use, and by menu.  Manager menus, for example, provide
"^DD",8925.1,8925.1,.05,21,39,0)
fuller editing capabilities than Clinician menus.
"^DD",8925.1,8925.1,.05,21,40,0)
 
"^DD",8925.1,8925.1,.05,21,41,0)
Personal Owner is a BASIC field.
"^DD",8925.1,8925.1,.05,"DT")
2961022
"^DD",8925.1,8925.1,.06,0)
CLASS OWNER^P8930'X^USR(8930,^0;6^Q
"^DD",8925.1,8925.1,.06,1,0)
^.1
"^DD",8925.1,8925.1,.06,1,1,0)
8925.1^AC
"^DD",8925.1,8925.1,.06,1,1,1)
S ^TIU(8925.1,"AC",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,.06,1,1,2)
K ^TIU(8925.1,"AC",$E(X,1,30),DA)
"^DD",8925.1,8925.1,.06,1,1,3)
Please don't delete!
"^DD",8925.1,8925.1,.06,1,1,"%D",0)
^^2^2^2950615^
"^DD",8925.1,8925.1,.06,1,1,"%D",1,0)
This regular cross reference is used to list Document Definitions by Class
"^DD",8925.1,8925.1,.06,1,1,"%D",2,0)
Owner.
"^DD",8925.1,8925.1,.06,1,1,"DT")
2950615
"^DD",8925.1,8925.1,.06,3)
If owned by Class rather than by Person enter User Class whose members may edit entry.  If owned by Person, delete Class Owner by entering '@' at Class Owner prompt.
"^DD",8925.1,8925.1,.06,4)

"^DD",8925.1,8925.1,.06,21,0)
^^31^31^2970227^
"^DD",8925.1,8925.1,.06,21,1,0)
Document Definition Ownership has nothing to do with who can USE the entry
"^DD",8925.1,8925.1,.06,21,2,0)
to enter a document.  It determines responsibility for the Document
"^DD",8925.1,8925.1,.06,21,3,0)
Definition itself.
"^DD",8925.1,8925.1,.06,21,4,0)
 
"^DD",8925.1,8925.1,.06,21,5,0)
An entry can be EDITED by its owner.  (The Manager menu permits override
"^DD",8925.1,8925.1,.06,21,6,0)
of ownership so that ownership can be assigned to a clinician (person with
"^DD",8925.1,8925.1,.06,21,7,0)
Clinician Menu) who can then fill in boilerplate text, while the manager
"^DD",8925.1,8925.1,.06,21,8,0)
can still edit the entry, since there are many fields the clinician does
"^DD",8925.1,8925.1,.06,21,9,0)
not have access to.)  Exception: the Manager menu does NOT override
"^DD",8925.1,8925.1,.06,21,10,0)
ownership of Objects or of Shared Components.  These can ONLY be edited by
"^DD",8925.1,8925.1,.06,21,11,0)
an owner, regardless of menu.
"^DD",8925.1,8925.1,.06,21,12,0)
 
"^DD",8925.1,8925.1,.06,21,13,0)
If a Title owner edits the boilerplate text of the Title, that person can
"^DD",8925.1,8925.1,.06,21,14,0)
edit the boilerplate text of all components of the title as well, without
"^DD",8925.1,8925.1,.06,21,15,0)
regard to component ownership.  However, the user must own the component
"^DD",8925.1,8925.1,.06,21,16,0)
in order to edit it individually, permitting separate ownership of
"^DD",8925.1,8925.1,.06,21,17,0)
components.
"^DD",8925.1,8925.1,.06,21,18,0)
 
"^DD",8925.1,8925.1,.06,21,19,0)
A Class Owner is a User Class from the USR CLASS file whose members may
"^DD",8925.1,8925.1,.06,21,20,0)
edit the entry.  An entry may have a Personal OR a Class Owner (not both).
"^DD",8925.1,8925.1,.06,21,21,0)
The Document Definition Utility TIUF does not prompt for Class Owner if
"^DD",8925.1,8925.1,.06,21,22,0)
the entry has a Personal Owner.  To change to Class Owner, first delete
"^DD",8925.1,8925.1,.06,21,23,0)
the Personal Owner by entering '@' at the Personal Owner prompt.
"^DD",8925.1,8925.1,.06,21,24,0)
 
"^DD",8925.1,8925.1,.06,21,25,0)
For new entries, users are prompted to enter the Class Owner Clinical
"^DD",8925.1,8925.1,.06,21,26,0)
Coordinator as the default.  To enter a different Class Owner, enter the
"^DD",8925.1,8925.1,.06,21,27,0)
appropriate class after the //'s.  If there are no //'s and the
"^DD",8925.1,8925.1,.06,21,28,0)
Replace...with editor is being used, enter ... to replace the whole
"^DD",8925.1,8925.1,.06,21,29,0)
class and then enter the appropriate class.
"^DD",8925.1,8925.1,.06,21,30,0)
 
"^DD",8925.1,8925.1,.06,21,31,0)
Class Owner is a BASIC field.
"^DD",8925.1,8925.1,.06,"DT")
2961022
"^DD",8925.1,8925.1,.07,0)
STATUS^*P8925.6'X^TIU(8925.6,^0;7^K:'$G(TIUFPRIV) X Q:'$D(X)  S DIC("S")="I 1 X $$STATSCRN^TIUFLF5" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
"^DD",8925.1,8925.1,.07,1,0)
^.1
"^DD",8925.1,8925.1,.07,1,1,0)
8925.1^AS
"^DD",8925.1,8925.1,.07,1,1,1)
S ^TIU(8925.1,"AS",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,.07,1,1,2)
K ^TIU(8925.1,"AS",$E(X,1,30),DA)
"^DD",8925.1,8925.1,.07,1,1,3)
Please don't delete!
"^DD",8925.1,8925.1,.07,1,1,"%D",0)
^^2^2^2950615^
"^DD",8925.1,8925.1,.07,1,1,"%D",1,0)
This regular cross reference is used to list Document Definitions by
"^DD",8925.1,8925.1,.07,1,1,"%D",2,0)
Status.
"^DD",8925.1,8925.1,.07,1,1,"DT")
2950615
"^DD",8925.1,8925.1,.07,1,2,0)
8925.1^ACL07^MUMPS
"^DD",8925.1,8925.1,.07,1,2,1)
D SACL^TIUDD1(X,.07)
"^DD",8925.1,8925.1,.07,1,2,2)
D KACL^TIUDD1(X,.07)
"^DD",8925.1,8925.1,.07,1,2,"%D",0)
^^2^2^2971016^
"^DD",8925.1,8925.1,.07,1,2,"%D",1,0)
This MUMPS-type cross-reference on STATUS support the identification of
"^DD",8925.1,8925.1,.07,1,2,"%D",2,0)
Active and TEST Titles within a given class.
"^DD",8925.1,8925.1,.07,1,2,"DT")
2971016
"^DD",8925.1,8925.1,.07,3)
 Documents can be entered on ACTIVE Titles.  Only the Owner can enter a document on TEST Titles.  Only INACTIVE Document Definitions can be edited.
"^DD",8925.1,8925.1,.07,4)

"^DD",8925.1,8925.1,.07,12)
STATSCRN limits Status to Status file entries that are appropriate for Document Definitions: Active, Inactive, and Test.
"^DD",8925.1,8925.1,.07,12.1)
S DIC("S")="I 1 X $$STATSCRN^TIUFLF5"
"^DD",8925.1,8925.1,.07,21,0)
^^183^183^2990225^^^
"^DD",8925.1,8925.1,.07,21,1,0)
Status provides a way of making Document Definitions 'Offline' to
"^DD",8925.1,8925.1,.07,21,2,0)
documents.  Document Definitions need to be 'Offline' if they are new and
"^DD",8925.1,8925.1,.07,21,3,0)
not ready for use, if they are being edited, or if they are retired from
"^DD",8925.1,8925.1,.07,21,4,0)
further use.
"^DD",8925.1,8925.1,.07,21,5,0)
 
"^DD",8925.1,8925.1,.07,21,6,0)
Status is limited to those Statuses in the Status File which apply to
"^DD",8925.1,8925.1,.07,21,7,0)
Document Definitions: Inactive, Test, and Active. The Document Definition
"^DD",8925.1,8925.1,.07,21,8,0)
Utility TIUF further limits Statuses to those appropriate for the entry
"^DD",8925.1,8925.1,.07,21,9,0)
Type (see below), limits the Status of entries with Inactive ancestors to
"^DD",8925.1,8925.1,.07,21,10,0)
Inactive, and limits the Status of faulty entries to Inactive.
"^DD",8925.1,8925.1,.07,21,11,0)
 
"^DD",8925.1,8925.1,.07,21,12,0)
Status applies to all Document Definitions, but its meaning and possible
"^DD",8925.1,8925.1,.07,21,13,0)
values vary somewhat with the Document Definition Type.  Exception: Shared
"^DD",8925.1,8925.1,.07,21,14,0)
Components: See COMPONENT STATUS, below.
"^DD",8925.1,8925.1,.07,21,15,0)
 
"^DD",8925.1,8925.1,.07,21,16,0)
Status is a BASIC field.
"^DD",8925.1,8925.1,.07,21,17,0)
 
"^DD",8925.1,8925.1,.07,21,18,0)
                                TITLE STATUS
"^DD",8925.1,8925.1,.07,21,19,0)
 
"^DD",8925.1,8925.1,.07,21,20,0)
Status has its most basic meaning for Titles [Document Definitions of Type
"^DD",8925.1,8925.1,.07,21,21,0)
Title]:
"^DD",8925.1,8925.1,.07,21,22,0)
 
"^DD",8925.1,8925.1,.07,21,23,0)
A Title can have Status Inactive, Test, or Active.  If it has Status
"^DD",8925.1,8925.1,.07,21,24,0)
Inactive, it cannot be used to enter documents (EXCEPT through the
"^DD",8925.1,8925.1,.07,21,25,0)
Try Action, which deletes the document when done). If it has Status
"^DD",8925.1,8925.1,.07,21,26,0)
Test, it can be used to enter documents only by its Owner. Titles should
"^DD",8925.1,8925.1,.07,21,27,0)
be tested (and Tried) using TEST PATIENTS ONLY.  If a Title has Status
"^DD",8925.1,8925.1,.07,21,28,0)
Active, it can be used to enter documents by any one with access and
"^DD",8925.1,8925.1,.07,21,29,0)
authorization.  
"^DD",8925.1,8925.1,.07,21,30,0)
 
"^DD",8925.1,8925.1,.07,21,31,0)
                              *************** 
"^DD",8925.1,8925.1,.07,21,32,0)
NOTE on Availability of Titles for entering documents: 
"^DD",8925.1,8925.1,.07,21,33,0)
Although Status affects availability for entering documents, there are
"^DD",8925.1,8925.1,.07,21,34,0)
other factors which also affect availability: A Document Definition is not
"^DD",8925.1,8925.1,.07,21,35,0)
available to a given user for entering documents (excepting the Document
"^DD",8925.1,8925.1,.07,21,36,0)
Definition Utility Try Action) unless all of the following 3 criteria are
"^DD",8925.1,8925.1,.07,21,37,0)
met:
"^DD",8925.1,8925.1,.07,21,38,0)
 
"^DD",8925.1,8925.1,.07,21,39,0)
  1) It is a Document Definition of Type Title.
"^DD",8925.1,8925.1,.07,21,40,0)
 
"^DD",8925.1,8925.1,.07,21,41,0)
  2) It has Status Active or Test.  If it has Status Test, the user
"^DD",8925.1,8925.1,.07,21,42,0)
entering a document must own the Title.
"^DD",8925.1,8925.1,.07,21,43,0)
 
"^DD",8925.1,8925.1,.07,21,44,0)
  3) If authorization for using the Title to enter documents is restricted
"^DD",8925.1,8925.1,.07,21,45,0)
by Business Rules, the user must be a member of the authorized user
"^DD",8925.1,8925.1,.07,21,46,0)
class.
"^DD",8925.1,8925.1,.07,21,47,0)
 
"^DD",8925.1,8925.1,.07,21,48,0)
Unless these criteria are all met, users trying to enter documents will
"^DD",8925.1,8925.1,.07,21,49,0)
not SEE the Document Definition.  Therefore it is wise to warn users when
"^DD",8925.1,8925.1,.07,21,50,0)
taking definitions offline for edit, and/or to do so at nonpeak hours for
"^DD",8925.1,8925.1,.07,21,51,0)
entering documents.
"^DD",8925.1,8925.1,.07,21,52,0)
 
"^DD",8925.1,8925.1,.07,21,53,0)
The above description applies to document entry BOTH manually through
"^DD",8925.1,8925.1,.07,21,54,0)
menu options AND via upload.  It does NOT apply to autoentry of documents
"^DD",8925.1,8925.1,.07,21,55,0)
via the TIU application interface.  Adverse Reaction/Allergy notes entered
"^DD",8925.1,8925.1,.07,21,56,0)
by the Allergy package are an example of such autoentry.  The TIU
"^DD",8925.1,8925.1,.07,21,57,0)
application interface for autoentering documents disregards Title status
"^DD",8925.1,8925.1,.07,21,58,0)
and Business Rules.
"^DD",8925.1,8925.1,.07,21,59,0)
                             *******************
"^DD",8925.1,8925.1,.07,21,60,0)
 
"^DD",8925.1,8925.1,.07,21,61,0)
When being upgraded to Status Active or Test, a Title is examined for
"^DD",8925.1,8925.1,.07,21,62,0)
rudimentary completeness and must be judged OK before the upgrade takes
"^DD",8925.1,8925.1,.07,21,63,0)
place.  If desired, users can perform the same examination themselves by
"^DD",8925.1,8925.1,.07,21,64,0)
selecting action TRY.  For Titles, Action TRY also permits the user to
"^DD",8925.1,8925.1,.07,21,65,0)
enter a document on the entry.  The document is deleted immediately after
"^DD",8925.1,8925.1,.07,21,66,0)
the trial.
"^DD",8925.1,8925.1,.07,21,67,0)
 
"^DD",8925.1,8925.1,.07,21,68,0)
Availability for entering documents is the central meaning of Status.
"^DD",8925.1,8925.1,.07,21,69,0)
However, Status also controls edit/deletion of Document Definitions:  A
"^DD",8925.1,8925.1,.07,21,70,0)
Title can be edited ONLY if it has Status Inactive, ensuring that no one
"^DD",8925.1,8925.1,.07,21,71,0)
is using it to enter a document while its behavior is changing.  Titles
"^DD",8925.1,8925.1,.07,21,72,0)
can be deleted only with Status Inactive.
"^DD",8925.1,8925.1,.07,21,73,0)
 
"^DD",8925.1,8925.1,.07,21,74,0)
NOTE: Although Status affects Editing ability, it is not the only factor
"^DD",8925.1,8925.1,.07,21,75,0)
affecting editing:  If an entry is already IN USE by documents,
"^DD",8925.1,8925.1,.07,21,76,0)
editing/deletion is restricted to aspects which will not harm existing
"^DD",8925.1,8925.1,.07,21,77,0)
TIU documents.
"^DD",8925.1,8925.1,.07,21,78,0)
 
"^DD",8925.1,8925.1,.07,21,79,0)
Components under a Title have the same status as the Title: When a Title's
"^DD",8925.1,8925.1,.07,21,80,0)
status is changed, the statuses of its descendant Components are
"^DD",8925.1,8925.1,.07,21,81,0)
automatically changed with it. (Shared Components are an exception: see
"^DD",8925.1,8925.1,.07,21,82,0)
COMPONENT STATUS, below.)
"^DD",8925.1,8925.1,.07,21,83,0)
 
"^DD",8925.1,8925.1,.07,21,84,0)
                       CLASS/DOCUMENT CLASS STATUS
"^DD",8925.1,8925.1,.07,21,85,0)
 
"^DD",8925.1,8925.1,.07,21,86,0)
A Document Definition of Type Class or Document Class can have Status
"^DD",8925.1,8925.1,.07,21,87,0)
Inactive or Active.  
"^DD",8925.1,8925.1,.07,21,88,0)
 
"^DD",8925.1,8925.1,.07,21,89,0)
Basics for a Class or Document Class cannot be edited (except for Owner
"^DD",8925.1,8925.1,.07,21,90,0)
and Status) unless it is Inactive.  Since Inactivating a Class/Document
"^DD",8925.1,8925.1,.07,21,91,0)
Class automatically inactivates its descendants, this ensures that all
"^DD",8925.1,8925.1,.07,21,92,0)
Titles which inherit behavior from it are neither Active nor Test, and are
"^DD",8925.1,8925.1,.07,21,93,0)
thus 'Offline' while inherited behavior is edited.
"^DD",8925.1,8925.1,.07,21,94,0)
 
"^DD",8925.1,8925.1,.07,21,95,0)
In contrast to Basics, the ability to add/edit ITEMS of a Class/Document
"^DD",8925.1,8925.1,.07,21,96,0)
Class depends on the Status of the item, not the parent: it is NOT
"^DD",8925.1,8925.1,.07,21,97,0)
necessary to Inactivate a Class such as Progress Notes in order to
"^DD",8925.1,8925.1,.07,21,98,0)
edit/add items.
"^DD",8925.1,8925.1,.07,21,99,0)
 
"^DD",8925.1,8925.1,.07,21,100,0)
Activating a Class/Document Class differs from Inactivating the
"^DD",8925.1,8925.1,.07,21,101,0)
Class/Document Class: When a Class/Document Class is ACTIVATED, its
"^DD",8925.1,8925.1,.07,21,102,0)
descendants may have any Status which their Type permits: they are not
"^DD",8925.1,8925.1,.07,21,103,0)
REQUIRED to be Active. Hence, they are not automatically Activated when
"^DD",8925.1,8925.1,.07,21,104,0)
the parent is Activated.
"^DD",8925.1,8925.1,.07,21,105,0)
 
"^DD",8925.1,8925.1,.07,21,106,0)
                            COMPONENT STATUS
"^DD",8925.1,8925.1,.07,21,107,0)
 
"^DD",8925.1,8925.1,.07,21,108,0)
A Document Definition of Type Component has the same status as its parent:
"^DD",8925.1,8925.1,.07,21,109,0)
Its status can be changed only by changing the Status of its Parent, if it
"^DD",8925.1,8925.1,.07,21,110,0)
has one. Components without parents are always Inactive.
"^DD",8925.1,8925.1,.07,21,111,0)
 
"^DD",8925.1,8925.1,.07,21,112,0)
NOTE: The above implies that Test or Active Titles cannot have Inactive
"^DD",8925.1,8925.1,.07,21,113,0)
Components.  In other words, Inactivating a Component is NOT a way of
"^DD",8925.1,8925.1,.07,21,114,0)
retiring it.  If a Component is no longer a useful section of a Title, it
"^DD",8925.1,8925.1,.07,21,115,0)
should be edited so as to make it useful, or it should be deleted AS AN
"^DD",8925.1,8925.1,.07,21,116,0)
ITEM from the Title of which it is a part.  As with all retired Document
"^DD",8925.1,8925.1,.07,21,117,0)
Definitions, it should NOT be deleted FROM THE FILE if it has been used by
"^DD",8925.1,8925.1,.07,21,118,0)
documents.
"^DD",8925.1,8925.1,.07,21,119,0)
 
"^DD",8925.1,8925.1,.07,21,120,0)
Components can be edited only if they have status Inactive. This ensures
"^DD",8925.1,8925.1,.07,21,121,0)
that all Titles using them are offline while the components are being
"^DD",8925.1,8925.1,.07,21,122,0)
edited.
"^DD",8925.1,8925.1,.07,21,123,0)
 
"^DD",8925.1,8925.1,.07,21,124,0)
Shared Components are a special case since they can have multiple parents.
"^DD",8925.1,8925.1,.07,21,125,0)
They DO NOT HAVE A STATUS. They can be edited only when all parent Titles
"^DD",8925.1,8925.1,.07,21,126,0)
have Status Inactive.  (The Detailed Display screen shows parents.)  This
"^DD",8925.1,8925.1,.07,21,127,0)
ensures that all parent Titles of Shared Components are offline while the
"^DD",8925.1,8925.1,.07,21,128,0)
component is being edited.  Edit of Shared Components is permitted only
"^DD",8925.1,8925.1,.07,21,129,0)
through the Option Sort Document Definitions.
"^DD",8925.1,8925.1,.07,21,130,0)
 
"^DD",8925.1,8925.1,.07,21,131,0)
Edit of Shared Components is severely restricted by Ownership, since they
"^DD",8925.1,8925.1,.07,21,132,0)
may be used multiple times and across the site.  Even an Inactive Status
"^DD",8925.1,8925.1,.07,21,133,0)
does not permit a manager (person with Manager menu) to override ownership
"^DD",8925.1,8925.1,.07,21,134,0)
and edit a Shared Component they don't own.  See Shared Components, under
"^DD",8925.1,8925.1,.07,21,135,0)
Description of Type.  See Description of Shared.
"^DD",8925.1,8925.1,.07,21,136,0)
 
"^DD",8925.1,8925.1,.07,21,137,0)
                               OBJECT STATUS
"^DD",8925.1,8925.1,.07,21,138,0)
 
"^DD",8925.1,8925.1,.07,21,139,0)
Document Definitions of Type Object have Status Inactive or Active.
"^DD",8925.1,8925.1,.07,21,140,0)
 
"^DD",8925.1,8925.1,.07,21,141,0)
Only ACTIVE objects function.  That is, if a user enters a document on a
"^DD",8925.1,8925.1,.07,21,142,0)
Title with boilerplate text containing an inactive object, the object
"^DD",8925.1,8925.1,.07,21,143,0)
doesn't do anything; the user sees the name of the object and an error
"^DD",8925.1,8925.1,.07,21,144,0)
message in place of the object data.
"^DD",8925.1,8925.1,.07,21,145,0)
 
"^DD",8925.1,8925.1,.07,21,146,0)
Only ACTIVE objects should be embedded in boilerplate text.  Exception:
"^DD",8925.1,8925.1,.07,21,147,0)
owners who are creating/editing objects.  Others should NOT embed inactive
"^DD",8925.1,8925.1,.07,21,148,0)
objects in boilerplate text since they may not be ready for use and since
"^DD",8925.1,8925.1,.07,21,149,0)
they do not function when users enter documents against them. Titles whose
"^DD",8925.1,8925.1,.07,21,150,0)
boilerplate text contains inactive objects cannot be activated.  (This
"^DD",8925.1,8925.1,.07,21,151,0)
does NOT imply that active titles never have inactive objects embedded in
"^DD",8925.1,8925.1,.07,21,152,0)
them since users can, after a warning, inactivate objects even when they
"^DD",8925.1,8925.1,.07,21,153,0)
are embedded in active titles.)
"^DD",8925.1,8925.1,.07,21,154,0)
 
"^DD",8925.1,8925.1,.07,21,155,0)
Only INACTIVE objects can be edited (and only by an owner).  Only an owner
"^DD",8925.1,8925.1,.07,21,156,0)
can activate/inactivate an object.  (Exception: if a user owns an object
"^DD",8925.1,8925.1,.07,21,157,0)
and edits the owner to someone else, the user is not prevented from going
"^DD",8925.1,8925.1,.07,21,158,0)
on to edit the status in the same edit session since they WERE the owner a
"^DD",8925.1,8925.1,.07,21,159,0)
few seconds ago.)  Active objects are assumed to be ready for use in any
"^DD",8925.1,8925.1,.07,21,160,0)
boilerplate text.
"^DD",8925.1,8925.1,.07,21,161,0)
 
"^DD",8925.1,8925.1,.07,21,162,0)
Since the owner is essentially caretaker of the object for the entire
"^DD",8925.1,8925.1,.07,21,163,0)
site, the owner should consult with all who use it before editing it.  An
"^DD",8925.1,8925.1,.07,21,164,0)
object can be tested by embedding it in the boilerplate text of a Title
"^DD",8925.1,8925.1,.07,21,165,0)
and selecting action Try for the Title.  It need not have status Active
"^DD",8925.1,8925.1,.07,21,166,0)
for this testing (and SHOULD not have status Active until testing is
"^DD",8925.1,8925.1,.07,21,167,0)
complete).  Owners who inactivate objects for editing should make SURE to
"^DD",8925.1,8925.1,.07,21,168,0)
reactivate them if they are being used.
"^DD",8925.1,8925.1,.07,21,169,0)
 
"^DD",8925.1,8925.1,.07,21,170,0)
Sites should either inactivate relevant Titles before editing objects or
"^DD",8925.1,8925.1,.07,21,171,0)
edit objects only when users are not likely to be ENTERING documents since
"^DD",8925.1,8925.1,.07,21,172,0)
Inactive objects do not function.
"^DD",8925.1,8925.1,.07,21,173,0)
 
"^DD",8925.1,8925.1,.07,21,174,0)
If a site changes the name or behavior of an Object, it is up to the SITE
"^DD",8925.1,8925.1,.07,21,175,0)
to change the name wherever it has already been embedded in Boilerplate
"^DD",8925.1,8925.1,.07,21,176,0)
Text, and to inform users of the change.
"^DD",8925.1,8925.1,.07,21,177,0)
 
"^DD",8925.1,8925.1,.07,21,178,0)
An object which is no longer wanted for future documents can be removed
"^DD",8925.1,8925.1,.07,21,179,0)
from the boilerplate text of all Titles and Components and then deleted
"^DD",8925.1,8925.1,.07,21,180,0)
from file 8925.1.  Only an owner can delete it.  All of the documents that
"^DD",8925.1,8925.1,.07,21,181,0)
used it have already got it in hard words so there is no need to keep it
"^DD",8925.1,8925.1,.07,21,182,0)
for their sake.  Old Objects should be edited so they are useful or
"^DD",8925.1,8925.1,.07,21,183,0)
deleted, not kept around forever as Inactive.
"^DD",8925.1,8925.1,.07,"DT")
2971016
"^DD",8925.1,8925.1,.08,0)
IN USE^CJ6^^ ; ^S X=$S($L($T(^TIUFLF)):$$DDEFUSED^TIUFLF(D0),1:"?")
"^DD",8925.1,8925.1,.08,.1)

"^DD",8925.1,8925.1,.08,9)
^
"^DD",8925.1,8925.1,.08,9.01)

"^DD",8925.1,8925.1,.08,9.1)
S X=$S($L($T(^TIUFLF)):$$DDEFUSED^TIUFLF(D0),1:"?")
"^DD",8925.1,8925.1,.08,21,0)
^^55^55^2970125^
"^DD",8925.1,8925.1,.08,21,1,0)
IN USE applies to all entries except those of Type Object.  It cannot be
"^DD",8925.1,8925.1,.08,21,2,0)
edited since it gets its value automatically.
"^DD",8925.1,8925.1,.08,21,3,0)
 
"^DD",8925.1,8925.1,.08,21,4,0)
IN USE may have values 'Yes', 'No', or '?'.
"^DD",8925.1,8925.1,.08,21,5,0)
 
"^DD",8925.1,8925.1,.08,21,6,0)
A Document Definition of Type Title or Component is In Use (Yes) if there
"^DD",8925.1,8925.1,.08,21,7,0)
are entries IN THE TIU DOCUMENT file which store it as their Document
"^DD",8925.1,8925.1,.08,21,8,0)
Definition.  If not, it is NOT used (No). 
"^DD",8925.1,8925.1,.08,21,9,0)
 
"^DD",8925.1,8925.1,.08,21,10,0)
NOTE: It is possible for Document Definitions to be used by documents in
"^DD",8925.1,8925.1,.08,21,11,0)
files other than the TIU Document file and still be NOT In Use since In
"^DD",8925.1,8925.1,.08,21,12,0)
Use means in use by documents in the TIU Document Definition file. See
"^DD",8925.1,8925.1,.08,21,13,0)
Warning, below.
"^DD",8925.1,8925.1,.08,21,14,0)
 
"^DD",8925.1,8925.1,.08,21,15,0)
A Document Definition of Type Class or Document Class is In Use (Yes) if
"^DD",8925.1,8925.1,.08,21,16,0)
it has children of Type Title which are In Use. That is, it is Used by
"^DD",8925.1,8925.1,.08,21,17,0)
Documents (Yes) if there are entries in the TIU Document file which
"^DD",8925.1,8925.1,.08,21,18,0)
inherit behavior from it. If not, it is NOT used (No).
"^DD",8925.1,8925.1,.08,21,19,0)
 
"^DD",8925.1,8925.1,.08,21,20,0)
IN USE has value '?' for a Document Definition File entry if routine
"^DD",8925.1,8925.1,.08,21,21,0)
TIUFLF is missing or if the program encounters a nonexistent item and the
"^DD",8925.1,8925.1,.08,21,22,0)
entry is not In Use so far as the check has been able to go.
"^DD",8925.1,8925.1,.08,21,23,0)
 
"^DD",8925.1,8925.1,.08,21,24,0)
Note: Since Shared Components can be items of more than one Title, a
"^DD",8925.1,8925.1,.08,21,25,0)
Shared Component may be In Use even when a particular parent Title is
"^DD",8925.1,8925.1,.08,21,26,0)
NOT In Use.  This simply means that it is also a Component of another
"^DD",8925.1,8925.1,.08,21,27,0)
Title which IS In Use.
"^DD",8925.1,8925.1,.08,21,28,0)
 
"^DD",8925.1,8925.1,.08,21,29,0)
If IN USE has the explicit value 'No' for a particular Document Definition
"^DD",8925.1,8925.1,.08,21,30,0)
entry, the entry can be deleted by the Owner without harming documents IN
"^DD",8925.1,8925.1,.08,21,31,0)
TIU DOCUMENT FILE 8925. Deleting it will, however, orphan any descendant
"^DD",8925.1,8925.1,.08,21,32,0)
Document Definitions.
"^DD",8925.1,8925.1,.08,21,33,0)
 
"^DD",8925.1,8925.1,.08,21,34,0)
WARNING: If a site is using TIU to upload documents into a file other than
"^DD",8925.1,8925.1,.08,21,35,0)
the TIU Document file, it may create Document Definition entries to store
"^DD",8925.1,8925.1,.08,21,36,0)
upload information.  For example, it may create an Operative Reports title
"^DD",8925.1,8925.1,.08,21,37,0)
containing instructions for uploading documents into the Surgery file.
"^DD",8925.1,8925.1,.08,21,38,0)
These document definitions will be orphans and will be NOT In Use, since
"^DD",8925.1,8925.1,.08,21,39,0)
documents using them are not stored in the TIU Document file. They must
"^DD",8925.1,8925.1,.08,21,40,0)
NOT be deleted from the Document Definition file.
"^DD",8925.1,8925.1,.08,21,41,0)
 
"^DD",8925.1,8925.1,.08,21,42,0)
Note: Deleting Objects will not harm existing documents, but WILL HARM
"^DD",8925.1,8925.1,.08,21,43,0)
future documents if the Object is embedded in existing Document Definition
"^DD",8925.1,8925.1,.08,21,44,0)
Boilerplate Text.
"^DD",8925.1,8925.1,.08,21,45,0)
 
"^DD",8925.1,8925.1,.08,21,46,0)
If IN USE has value 'Yes' or '?', the Document Definition Utility TIUF
"^DD",8925.1,8925.1,.08,21,47,0)
does not permit the entry to be deleted. Deleting the entry would cause
"^DD",8925.1,8925.1,.08,21,48,0)
documents in file 8925 not to function.  This is true even if the entry
"^DD",8925.1,8925.1,.08,21,49,0)
has status 'Inactive' and documents are no longer being written on the
"^DD",8925.1,8925.1,.08,21,50,0)
entry.
"^DD",8925.1,8925.1,.08,21,51,0)
 
"^DD",8925.1,8925.1,.08,21,52,0)
Technical Note: A Document Definition of Type Title or Component is IN
"^DD",8925.1,8925.1,.08,21,53,0)
USE if and only if it appears in file 8925's 'B' Cross Reference.
"^DD",8925.1,8925.1,.08,21,54,0)
 
"^DD",8925.1,8925.1,.08,21,55,0)
In Use is a BASIC field.
"^DD",8925.1,8925.1,.08,"DT")
2960618
"^DD",8925.1,8925.1,.1,0)
SHARED^SX^1:YES;0:NO;^0;10^K:'$G(TIUFPRIV) X
"^DD",8925.1,8925.1,.1,.1)
SHARED COMPONENT
"^DD",8925.1,8925.1,.1,3)
Enter Y for YES if this Component is intended for broad use across the site, i.e., it can be used more than once, and need not be owned by the user.
"^DD",8925.1,8925.1,.1,21,0)
^^48^48^2970220^
"^DD",8925.1,8925.1,.1,21,1,0)
Applies to entries of Type Component only.
"^DD",8925.1,8925.1,.1,21,2,0)
 
"^DD",8925.1,8925.1,.1,21,3,0)
Document Definitions of Type Component may be designated SHARED by Owners
"^DD",8925.1,8925.1,.1,21,4,0)
who have the Manager menu. This means the Component can be an item under
"^DD",8925.1,8925.1,.1,21,5,0)
multiple parents, and any user who owns a Title can add it as an item.
"^DD",8925.1,8925.1,.1,21,6,0)
 
"^DD",8925.1,8925.1,.1,21,7,0)
Shared Components are the ONLY members of the Document Definition
"^DD",8925.1,8925.1,.1,21,8,0)
hierarchy which can appear in more than one place in the hierarchy.
"^DD",8925.1,8925.1,.1,21,9,0)
(Objects can be used in multiple entries, but are not members of the
"^DD",8925.1,8925.1,.1,21,10,0)
hierarchy.)
"^DD",8925.1,8925.1,.1,21,11,0)
 
"^DD",8925.1,8925.1,.1,21,12,0)
Shared Components are intended for broad use across the site.  An example
"^DD",8925.1,8925.1,.1,21,13,0)
might be a Privacy Act Component.  Since a Shared Component may be used in
"^DD",8925.1,8925.1,.1,21,14,0)
many different Document Definitions, its Owner is essentially caretaker
"^DD",8925.1,8925.1,.1,21,15,0)
for it, hospital wide, and must take into account all users before editing
"^DD",8925.1,8925.1,.1,21,16,0)
it.  Users who disagree with a proposed change can opt to create and use
"^DD",8925.1,8925.1,.1,21,17,0)
their own copy instead of using the Shared Component.
"^DD",8925.1,8925.1,.1,21,18,0)
 
"^DD",8925.1,8925.1,.1,21,19,0)
Parents of a Shared Component are listed in the Detailed Display Screen.
"^DD",8925.1,8925.1,.1,21,20,0)
 
"^DD",8925.1,8925.1,.1,21,21,0)
Shared Field values are 1 for YES and 0 for NO, with a default value of
"^DD",8925.1,8925.1,.1,21,22,0)
0 for NO if the field is empty.
"^DD",8925.1,8925.1,.1,21,23,0)
 
"^DD",8925.1,8925.1,.1,21,24,0)
An entry may not be designated Shared unless it is of Type Component. Only
"^DD",8925.1,8925.1,.1,21,25,0)
a Manager (person with Manager menu) and only an Owner can designate a
"^DD",8925.1,8925.1,.1,21,26,0)
Component as Shared. Only an OWNER can edit it.  (Normally Managers can
"^DD",8925.1,8925.1,.1,21,27,0)
override ownership and edit entries.  Manager Options do NOT override
"^DD",8925.1,8925.1,.1,21,28,0)
Ownership for editing Shared Components).  Shared Components can only be
"^DD",8925.1,8925.1,.1,21,29,0)
edited from the Sort Document Definitions Option.
"^DD",8925.1,8925.1,.1,21,30,0)
 
"^DD",8925.1,8925.1,.1,21,31,0)
Shared Components cannot be deleted.  If they do not have multiple
"^DD",8925.1,8925.1,.1,21,32,0)
parents, they can, however, be edited to NOT shared and THEN deleted,
"^DD",8925.1,8925.1,.1,21,33,0)
assuming they are not In Use by documents and the parent is Inactive.
"^DD",8925.1,8925.1,.1,21,34,0)
 
"^DD",8925.1,8925.1,.1,21,35,0)
Shared Components do NOT HAVE a Status.  They can be edited only if all
"^DD",8925.1,8925.1,.1,21,36,0)
parent Titles are Inactive.  This ensures that parent Titles are offline
"^DD",8925.1,8925.1,.1,21,37,0)
for entering documents while their components are being edited.  Parents
"^DD",8925.1,8925.1,.1,21,38,0)
are listed on the Detailed Display Screen.
"^DD",8925.1,8925.1,.1,21,39,0)
 
"^DD",8925.1,8925.1,.1,21,40,0)
If a Shared Component has subcomponents, they are automatically Shared,
"^DD",8925.1,8925.1,.1,21,41,0)
since they, with their parents, can be used in more than one place in the
"^DD",8925.1,8925.1,.1,21,42,0)
hierarchy.
"^DD",8925.1,8925.1,.1,21,43,0)
 
"^DD",8925.1,8925.1,.1,21,44,0)
Sharing of Document Definitions other than Components is not permitted
"^DD",8925.1,8925.1,.1,21,45,0)
because it unduly restricts the owner's right to edit/delete the Document
"^DD",8925.1,8925.1,.1,21,46,0)
Definition and adds undue complexity to the Hierarchy.
"^DD",8925.1,8925.1,.1,21,47,0)
 
"^DD",8925.1,8925.1,.1,21,48,0)
Shared is a BASIC field.
"^DD",8925.1,8925.1,.1,"DT")
2961022
"^DD",8925.1,8925.1,.11,0)
ORPHAN^CJ8^^ ; ^S X=$S($L($T(^TIUFLF4)):$$ORPHAN^TIUFLF4(D0,^TIU(8925.1,D0,0)),1:"?")
"^DD",8925.1,8925.1,.11,9)
^
"^DD",8925.1,8925.1,.11,9.01)

"^DD",8925.1,8925.1,.11,9.1)
S X=$S($L($T(^TIUFLF4)):$$ORPHAN^TIUFLF4(D0,^TIU(8925.1,D0,0)),1:"?")
"^DD",8925.1,8925.1,.11,21,0)
^^57^57^2970220^
"^DD",8925.1,8925.1,.11,21,1,0)
Orphan applies to Document Definitions of all Types except Objects
"^DD",8925.1,8925.1,.11,21,2,0)
and Shared Components.
"^DD",8925.1,8925.1,.11,21,3,0)
 
"^DD",8925.1,8925.1,.11,21,4,0)
Orphan is not editable since it gets its value automatically.
"^DD",8925.1,8925.1,.11,21,5,0)
 
"^DD",8925.1,8925.1,.11,21,6,0)
Document Definitions are Orphans if they do not belong to the Clinical
"^DD",8925.1,8925.1,.11,21,7,0)
Documents Hierarchy, i.e., they cannot trace their ancestry all the way
"^DD",8925.1,8925.1,.11,21,8,0)
back to the Class Clinical Documents.  If an Orphan is not In Use, it
"^DD",8925.1,8925.1,.11,21,9,0)
may be "dead wood" which should be deleted from the file.  Orphans not In
"^DD",8925.1,8925.1,.11,21,10,0)
Use which SHOULD NOT BE DELETED include those being kept for later
"^DD",8925.1,8925.1,.11,21,11,0)
possible use, those temporarily orphaned in order to move them around in
"^DD",8925.1,8925.1,.11,21,12,0)
the hierarchy, and those used for uploading documents into files other
"^DD",8925.1,8925.1,.11,21,13,0)
than the TIU Document file.
"^DD",8925.1,8925.1,.11,21,14,0)
 
"^DD",8925.1,8925.1,.11,21,15,0)
(Orphan does not apply to Objects since they don't ever belong to the
"^DD",8925.1,8925.1,.11,21,16,0)
hierarchy.  Orphan does not apply to Shared Components since they may
"^DD",8925.1,8925.1,.11,21,17,0)
have more than one line of ancestry.)
"^DD",8925.1,8925.1,.11,21,18,0)
 
"^DD",8925.1,8925.1,.11,21,19,0)
Warning:  The DOCUMENT DEFINITION file may contain orphan entries which
"^DD",8925.1,8925.1,.11,21,20,0)
are not used by documents in the TIU Document file but which contain
"^DD",8925.1,8925.1,.11,21,21,0)
upload instructions for storing documents somewhere else.  For example, if
"^DD",8925.1,8925.1,.11,21,22,0)
a site is uploading Operative Reports into the Surgery file, there may be
"^DD",8925.1,8925.1,.11,21,23,0)
an orphan Operative Report Document Definition in the DOCUMENT DEFINITION
"^DD",8925.1,8925.1,.11,21,24,0)
file.  These should NOT be deleted just because they are orphans.  Such
"^DD",8925.1,8925.1,.11,21,25,0)
entries can be identified by edit/viewing them through the Sort Option
"^DD",8925.1,8925.1,.11,21,26,0)
and looking for Upload fields.
"^DD",8925.1,8925.1,.11,21,27,0)
 
"^DD",8925.1,8925.1,.11,21,28,0)
NOTE: Orphan as used in the Document Definition Utility TIUF does NOT mean
"^DD",8925.1,8925.1,.11,21,29,0)
having no parents.  For example, suppose Exceptional Day Pass Note has
"^DD",8925.1,8925.1,.11,21,30,0)
parent Day Pass Note.  If Day Pass Note has no parent, then Exceptional
"^DD",8925.1,8925.1,.11,21,31,0)
Day Pass Note cannot trace its ancestry back to Clinical Documents and is
"^DD",8925.1,8925.1,.11,21,32,0)
an Orphan even though it has a parent.
"^DD",8925.1,8925.1,.11,21,33,0)
 
"^DD",8925.1,8925.1,.11,21,34,0)
Orphans are invisible to TIU users and cannot be used to enter documents.
"^DD",8925.1,8925.1,.11,21,35,0)
 
"^DD",8925.1,8925.1,.11,21,36,0)
When an item under a non-orphan is deleted as an item, it becomes an
"^DD",8925.1,8925.1,.11,21,37,0)
orphan along with all of its descendants.  TIUF, the Document Definition
"^DD",8925.1,8925.1,.11,21,38,0)
Utility, does not permit non-orphan Titles to become orphaned if they are
"^DD",8925.1,8925.1,.11,21,39,0)
In Use.  Titles already used but being retired from further use should
"^DD",8925.1,8925.1,.11,21,40,0)
be Inactivated, NOT orphaned.  Components are a different story;
"^DD",8925.1,8925.1,.11,21,41,0)
components being retired from further use can and should be orphaned
"^DD",8925.1,8925.1,.11,21,42,0)
(deleted as items from the Title).
"^DD",8925.1,8925.1,.11,21,43,0)
 
"^DD",8925.1,8925.1,.11,21,44,0)
Reason: Titles inherit attributes and therefore require a complete
"^DD",8925.1,8925.1,.11,21,45,0)
ancestry in order to process existing documents.  Since components, on the
"^DD",8925.1,8925.1,.11,21,46,0)
other hand, do not inherit attributes, they do NOT require a complete
"^DD",8925.1,8925.1,.11,21,47,0)
ancestry to process existing documents (although they must remain in the
"^DD",8925.1,8925.1,.11,21,48,0)
file.)
"^DD",8925.1,8925.1,.11,21,49,0)
 
"^DD",8925.1,8925.1,.11,21,50,0)
Since Orphans do not belong to the Hierarchy, they do NOT appear on the
"^DD",8925.1,8925.1,.11,21,51,0)
Edit Document Definitions Option.  They can be accessed through the Sort
"^DD",8925.1,8925.1,.11,21,52,0)
Document Definitions Option.
"^DD",8925.1,8925.1,.11,21,53,0)
 
"^DD",8925.1,8925.1,.11,21,54,0)
The field Orphan may have values 'Yes', 'No', or '?'. Orphan has value '?'
"^DD",8925.1,8925.1,.11,21,55,0)
if there are technical errors making its value unknown.
"^DD",8925.1,8925.1,.11,21,56,0)
 
"^DD",8925.1,8925.1,.11,21,57,0)
Orphan is a BASIC field.
"^DD",8925.1,8925.1,.11,"DT")
2960201
"^DD",8925.1,8925.1,.12,0)
HAS BOILTXT^CJ7^^ ; ^S TIUFBTXT=$S($L($T(^TIUFLF)):$$HASBOIL^TIUFLF(D0,^TIU(8925.1,D0,0)),1:"UNKNOWN"),X=$S(TIUFBTXT:"YES",TIUFBTXT=0:"NO",1:TIUFBTXT) K TIUFBTXT
"^DD",8925.1,8925.1,.12,.1)
HAS BOILERPLATE TEXT
"^DD",8925.1,8925.1,.12,9)
^
"^DD",8925.1,8925.1,.12,9.01)

"^DD",8925.1,8925.1,.12,9.1)
S TIUFBTXT=$S($L($T(^TIUFLF)):$$HASBOIL^TIUFLF(D0,^TIU(8925.1,D0,0)),1:"UNKNOWN"),X=$S(TIUFBTXT:"YES",TIUFBTXT=0:"NO",1:TIUFBTXT) K TIUFBTXT
"^DD",8925.1,8925.1,.12,21,0)
^^3^3^2970128^
"^DD",8925.1,8925.1,.12,21,1,0)
Applies to Types Title and Component only.  Cannot be edited since value
"^DD",8925.1,8925.1,.12,21,2,0)
is automatic.  A Document Definition Has Boiltxt if it or its descendant
"^DD",8925.1,8925.1,.12,21,3,0)
Components have Boilerplate Text (Field 3).  BASIC field.
"^DD",8925.1,8925.1,.12,"DT")
2960118
"^DD",8925.1,8925.1,.13,0)
NATIONAL STANDARD^SX^1:YES;0:NO;^0;13^K:'$G(TIUFPRIV) X
"^DD",8925.1,8925.1,.13,3)
Enter YES if entry is Standard across the nation, i.e. sites mustn't edit
"^DD",8925.1,8925.1,.13,4)

"^DD",8925.1,8925.1,.13,21,0)
^^47^47^2990223^
"^DD",8925.1,8925.1,.13,21,1,0)
Some Document Definitions, for example, CWAD's, are developed nationally
"^DD",8925.1,8925.1,.13,21,2,0)
and sent out as standardized entries across the nation.  TIU and other
"^DD",8925.1,8925.1,.13,21,3,0)
packages depend on their standard definition, and they must not be edited
"^DD",8925.1,8925.1,.13,21,4,0)
by sites but only by the persons who are nationally responsible for them.
"^DD",8925.1,8925.1,.13,21,5,0)
 
"^DD",8925.1,8925.1,.13,21,6,0)
Such entries are marked NATIONAL STANDARD (field has value 1 for YES),
"^DD",8925.1,8925.1,.13,21,7,0)
which generally prevents sites from editing the entry.
"^DD",8925.1,8925.1,.13,21,8,0)
 
"^DD",8925.1,8925.1,.13,21,9,0)
In two cases, sites are permitted to edit National Standard entries.  The
"^DD",8925.1,8925.1,.13,21,10,0)
first case concerns Titles.  Sites can edit Status and Abbreviation for
"^DD",8925.1,8925.1,.13,21,11,0)
National Titles.  Status INACTIVE for a National Title prevents manual and
"^DD",8925.1,8925.1,.13,21,12,0)
upload entry of documents for the Title, while continuing to permit
"^DD",8925.1,8925.1,.13,21,13,0)
automatic entry for the Title via the TIU application interface for new
"^DD",8925.1,8925.1,.13,21,14,0)
notes. (Example: Adverse Reaction/Allergy notes are automatically
"^DD",8925.1,8925.1,.13,21,15,0)
entered by the Allergy package.) Editing Abbreviation gives sites a means
"^DD",8925.1,8925.1,.13,21,16,0)
of grouping national titles with other National and non-National Titles as
"^DD",8925.1,8925.1,.13,21,17,0)
they please.
"^DD",8925.1,8925.1,.13,21,18,0)
 
"^DD",8925.1,8925.1,.13,21,19,0)
The second case where edit of National entries is permitted concerns the
"^DD",8925.1,8925.1,.13,21,20,0)
Item Multiple:
"^DD",8925.1,8925.1,.13,21,21,0)
 
"^DD",8925.1,8925.1,.13,21,22,0)
If a National Standard entry has Type Class or Document Class, sites can
"^DD",8925.1,8925.1,.13,21,23,0)
add/delete Nonnational items as they please, and can edit ALL items AS
"^DD",8925.1,8925.1,.13,21,24,0)
ITEMS (e.g. Item Sequence, etc.).  Sites CANNOT add/delete National items.
"^DD",8925.1,8925.1,.13,21,25,0)
 
"^DD",8925.1,8925.1,.13,21,26,0)
If a National Standard entry has Type Title or Component, sites
"^DD",8925.1,8925.1,.13,21,27,0)
cannot add or delete items, but can still edit items AS ITEMS.
"^DD",8925.1,8925.1,.13,21,28,0)
 
"^DD",8925.1,8925.1,.13,21,29,0)
Sites cannot add National Standard entries as Items to parents.  There is
"^DD",8925.1,8925.1,.13,21,30,0)
one exception: Sites can add National Shared Components to (nonnational)
"^DD",8925.1,8925.1,.13,21,31,0)
Titles if they wish.  Sites can delete National Standard Items from
"^DD",8925.1,8925.1,.13,21,32,0)
nonnational parents. (Unless there has been a mistake, such items will be
"^DD",8925.1,8925.1,.13,21,33,0)
limited to Shared Components only.)
"^DD",8925.1,8925.1,.13,21,34,0)
 
"^DD",8925.1,8925.1,.13,21,35,0)
Field is NOT heritable.  If field has no value for an entry, value is 0 by
"^DD",8925.1,8925.1,.13,21,36,0)
default.  This means that entries created by sites are NOT National
"^DD",8925.1,8925.1,.13,21,37,0)
Standard.
"^DD",8925.1,8925.1,.13,21,38,0)
 
"^DD",8925.1,8925.1,.13,21,39,0)
Technical Note:
"^DD",8925.1,8925.1,.13,21,40,0)
 
"^DD",8925.1,8925.1,.13,21,41,0)
National entries (except for Shared Components) must have National
"^DD",8925.1,8925.1,.13,21,42,0)
ancestors:  if a National entry has a nonNational ancestor, the
"^DD",8925.1,8925.1,.13,21,43,0)
Document Definition Utility TIUF does not permit it to be activated.
"^DD",8925.1,8925.1,.13,21,44,0)
(Shared Components need not have National ancestors, and do not have a
"^DD",8925.1,8925.1,.13,21,45,0)
Status.)
"^DD",8925.1,8925.1,.13,21,46,0)
 
"^DD",8925.1,8925.1,.13,21,47,0)
National Standard is a BASIC field.
"^DD",8925.1,8925.1,.13,"DT")
2970128
"^DD",8925.1,8925.1,.14,0)
POSTING INDICATOR^S^C:crisis note;W:warning;A:allergy/ADR;D:directive;^0;14^Q
"^DD",8925.1,8925.1,.14,1,0)
^.1
"^DD",8925.1,8925.1,.14,1,1,0)
8925.1^APOST
"^DD",8925.1,8925.1,.14,1,1,1)
S ^TIU(8925.1,"APOST",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,.14,1,1,2)
K ^TIU(8925.1,"APOST",$E(X,1,30),DA)
"^DD",8925.1,8925.1,.14,1,1,"%D",0)
^^3^3^2970227^
"^DD",8925.1,8925.1,.14,1,1,"%D",1,0)
This REGULAR FileMan Cross-reference by Posting Indicator will help to
"^DD",8925.1,8925.1,.14,1,1,"%D",2,0)
identify which Document Classes are associated with each of the currently
"^DD",8925.1,8925.1,.14,1,1,"%D",3,0)
supported Posting Types.
"^DD",8925.1,8925.1,.14,1,1,"DT")
2970227
"^DD",8925.1,8925.1,.14,3)
Please choose an indicator corresponding to the Posting Type
"^DD",8925.1,8925.1,.14,21,0)
^^2^2^2970515^
"^DD",8925.1,8925.1,.14,21,1,0)
This field is used to help identify indicators of the Patient Posting Type
"^DD",8925.1,8925.1,.14,21,2,0)
to which the Document Definition should be ascribed.
"^DD",8925.1,8925.1,.14,"DT")
2970227
"^DD",8925.1,8925.1,.15,0)
PRF FLAG^CJ30^^ ; ^S X=$S($L($T(CFLDFLAG^TIUPRFL)):$$CFLDFLAG^TIUPRFL(D0),1:"?")
"^DD",8925.1,8925.1,.15,.1)
ASSOCIATED PATIENT RECORD FLAG
"^DD",8925.1,8925.1,.15,9)
^
"^DD",8925.1,8925.1,.15,9.01)

"^DD",8925.1,8925.1,.15,9.1)
S X=$S($L($T(CFLDFLAG^TIUPRFL)):$$CFLDFLAG^TIUPRFL(D0),1:"?")
"^DD",8925.1,8925.1,.15,21,0)
^^14^14^3050405^
"^DD",8925.1,8925.1,.15,21,1,0)
PRF FLAG applies only to PRF titles. The PRF FLAG of a PRF title is the
"^DD",8925.1,8925.1,.15,21,2,0)
name of the Patient Record Flag associated with the title.  (Notes cannot
"^DD",8925.1,8925.1,.15,21,3,0)
be written using a PRF title unless the title is associated with a flag 
"^DD",8925.1,8925.1,.15,21,4,0)
and that flag is assigned to the given patient.)
"^DD",8925.1,8925.1,.15,21,5,0)
 
"^DD",8925.1,8925.1,.15,21,6,0)
If the title is not associated with a flag or the associated flag cannot
"^DD",8925.1,8925.1,.15,21,7,0)
be found, the field has value "?".  If the Document Definition is not a
"^DD",8925.1,8925.1,.15,21,8,0)
title under Document Class PATIENT RECORD FLAG CAT I or PATIENT RECORD
"^DD",8925.1,8925.1,.15,21,9,0)
FLAG CAT II, the field has value NA for non-applicable.
"^DD",8925.1,8925.1,.15,21,10,0)
 
"^DD",8925.1,8925.1,.15,21,11,0)
Technical Note: Flags and their associations with titles are stored in 
"^DD",8925.1,8925.1,.15,21,12,0)
file PRF LOCAL FLAG (#26.11) or in file PRF NATIONAL FLAG (#26.15).
"^DD",8925.1,8925.1,.15,21,13,0)
 
"^DD",8925.1,8925.1,.15,21,14,0)
PRF FLAG is a BASIC field.
"^DD",8925.1,8925.1,.15,"DT")
3050405
"^DD",8925.1,8925.1,1,0)
UPLOAD DELIMITED ASCII HEADER^8925.11I^^ITEM;0
"^DD",8925.1,8925.1,1,21,0)
^^7^7^2970108^^
"^DD",8925.1,8925.1,1,21,1,0)
This multiple contains the upload record header format of the Document
"^DD",8925.1,8925.1,1,21,2,0)
Definition, to be used by the upload/router/filer when the preferred
"^DD",8925.1,8925.1,1,21,3,0)
header format is Delimited string (as opposed to captioned).
"^DD",8925.1,8925.1,1,21,4,0)
 
"^DD",8925.1,8925.1,1,21,5,0)
Delimited string is useful only if the site has a way of automating
"^DD",8925.1,8925.1,1,21,6,0)
creation of upload record headers.  If they are being created by a human
"^DD",8925.1,8925.1,1,21,7,0)
transcriber, use Captioned Record Headers instead.
"^DD",8925.1,8925.1,1,"DT")
2960729
"^DD",8925.1,8925.1,1.01,0)
UPLOAD TARGET FILE^*P1'^DIC(^1;1^S DIC("S")="I $D(^DIC(+Y,""%"",""B"",""TIU""))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
"^DD",8925.1,8925.1,1.01,3)
Select the DHCP file in which the document will be stored.
"^DD",8925.1,8925.1,1.01,12)
Only files with the "TIU" application group may be selected.
"^DD",8925.1,8925.1,1.01,12.1)
S DIC("S")="I $D(^DIC(+Y,""%"",""B"",""TIU""))"
"^DD",8925.1,8925.1,1.01,21,0)
^^20^20^2970506^
"^DD",8925.1,8925.1,1.01,21,1,0)
                           -------------
"^DD",8925.1,8925.1,1.01,21,2,0)
NOTE ON UPLOAD:
"^DD",8925.1,8925.1,1.01,21,3,0)
Upload fields (Upload Target File, Laygo Allowed, Target Text Field
"^DD",8925.1,8925.1,1.01,21,4,0)
Subscript, Upload Look-Up Method, Upload Post-Filing Code, Upload Filing
"^DD",8925.1,8925.1,1.01,21,5,0)
Error Code, and multiple fields Upload Delimited ASCII Header and Upload
"^DD",8925.1,8925.1,1.01,21,6,0)
Captioned ASCII Header) apply to Document Definitions of Type Class,
"^DD",8925.1,8925.1,1.01,21,7,0)
Document Class, and Title.  Multiple fields Upload Delimited ASCII Header
"^DD",8925.1,8925.1,1.01,21,8,0)
and Upload Captioned ASCII Header are heritable AS A GROUP.  Do NOT set
"^DD",8925.1,8925.1,1.01,21,9,0)
partial information at a lower level; if you set ANY information at a
"^DD",8925.1,8925.1,1.01,21,10,0)
lower level, it should be COMPLETE.  For information on editing heritable
"^DD",8925.1,8925.1,1.01,21,11,0)
fields, see Technical field: Edit Template.
"^DD",8925.1,8925.1,1.01,21,12,0)
 
"^DD",8925.1,8925.1,1.01,21,13,0)
TIUF, the Document Definition Utility does NOT display inherited Upload
"^DD",8925.1,8925.1,1.01,21,14,0)
information.  To see/edit existing upload information, edit/view at the
"^DD",8925.1,8925.1,1.01,21,15,0)
level it is set.
"^DD",8925.1,8925.1,1.01,21,16,0)
 
"^DD",8925.1,8925.1,1.01,21,17,0)
                           --------------
"^DD",8925.1,8925.1,1.01,21,18,0)
The UPLOAD TARGET FILE is the VA FileMan file in which fixed-field header
"^DD",8925.1,8925.1,1.01,21,19,0)
information and associated text will be stored.  Only files which include
"^DD",8925.1,8925.1,1.01,21,20,0)
the TIU Application Group may be selected.
"^DD",8925.1,8925.1,1.01,"DT")
2960729
"^DD",8925.1,8925.1,1.02,0)
LAYGO ALLOWED^S^0:NO;1:YES;^1;2^Q
"^DD",8925.1,8925.1,1.02,3)
Please indicate whether new entries may be added to the TARGET FILE.
"^DD",8925.1,8925.1,1.02,21,0)
^^2^2^2970128^
"^DD",8925.1,8925.1,1.02,21,1,0)
This field indicates whether or not a new entry can be created in
"^DD",8925.1,8925.1,1.02,21,2,0)
the TARGET FILE for documents defined by this Document Definition.
"^DD",8925.1,8925.1,1.02,"DT")
2970128
"^DD",8925.1,8925.1,1.03,0)
TARGET TEXT FIELD SUBSCRIPT^F^^1;3^K:$L(X)>15!($L(X)<1) X
"^DD",8925.1,8925.1,1.03,3)
Select the Word-processing field in the target file.
"^DD",8925.1,8925.1,1.03,21,0)
^^2^2^2970620^^
"^DD",8925.1,8925.1,1.03,21,1,0)
This is the subscript of the word-processing field in the TARGET FILE, in
"^DD",8925.1,8925.1,1.03,21,2,0)
which the body of the narrative report will be stored.
"^DD",8925.1,8925.1,1.03,"DT")
2940331
"^DD",8925.1,8925.1,1.04,0)
BOILERPLATE ON UPLOAD ENABLED^S^0:NO;1:YES;^1;4^Q
"^DD",8925.1,8925.1,1.04,3)
Indicate whether boilerplate logic will be executed on upload
"^DD",8925.1,8925.1,1.04,21,0)
^^2^2^2961210^
"^DD",8925.1,8925.1,1.04,21,1,0)
This field determines whether the filer will attempt to execute
"^DD",8925.1,8925.1,1.04,21,2,0)
boilerplate logic for uploaded documents.  Not used in version 1.
"^DD",8925.1,8925.1,1.04,"DT")
2951016
"^DD",8925.1,8925.1,2,0)
UPLOAD CAPTIONED ASCII HEADER^8925.12A^^HEAD;0
"^DD",8925.1,8925.1,2,21,0)
^^11^11^2970506^^
"^DD",8925.1,8925.1,2,21,1,0)
This multiple contains the upload record header format of the Document
"^DD",8925.1,8925.1,2,21,2,0)
Definition, to be used by the upload/router/filer when the preferred
"^DD",8925.1,8925.1,2,21,3,0)
header format is captioned (as opposed to delimited string).
"^DD",8925.1,8925.1,2,21,4,0)
 
"^DD",8925.1,8925.1,2,21,5,0)
Under captioned header format, header items are distinguished from each
"^DD",8925.1,8925.1,2,21,6,0)
other by captions such as SSN which are entered by the transcriber,
"^DD",8925.1,8925.1,2,21,7,0)
followed by the data.
"^DD",8925.1,8925.1,2,21,8,0)
 
"^DD",8925.1,8925.1,2,21,9,0)
Use the captioned header format if documents are transcribed by a human
"^DD",8925.1,8925.1,2,21,10,0)
transcriber.  Delimited format is useful only if the site has some way of
"^DD",8925.1,8925.1,2,21,11,0)
automatically generating upload record headers.
"^DD",8925.1,8925.1,2,"DT")
2960729
"^DD",8925.1,8925.1,3,0)
BOILERPLATE TEXT^8925.13^^DFLT;0
"^DD",8925.1,8925.1,3,"DT")
2950421
"^DD",8925.1,8925.1,3.02,0)
OK TO DISTRIBUTE^S^1:YES;0:NO;^3;2^Q
"^DD",8925.1,8925.1,3.02,3)
Enter 1 for YES if entry should be included when this file is exported with data.  Enter 0 for NO or leave blank if entry is for local use only.
"^DD",8925.1,8925.1,3.02,21,0)
^^13^13^2970224^^
"^DD",8925.1,8925.1,3.02,21,1,0)
Presently applies only to National Programmers; does not appear on
"^DD",8925.1,8925.1,3.02,21,2,0)
Manager or Clinician Menus.
"^DD",8925.1,8925.1,3.02,21,3,0)
 
"^DD",8925.1,8925.1,3.02,21,4,0)
If field is 1 for YES, then entry should be included for export.  If field
"^DD",8925.1,8925.1,3.02,21,5,0)
has no value or has value 0, entry should not be included for export.
"^DD",8925.1,8925.1,3.02,21,6,0)
 
"^DD",8925.1,8925.1,3.02,21,7,0)
Since TIU is hierarchical, the entry's behavior depends on entries above
"^DD",8925.1,8925.1,3.02,21,8,0)
it in the hierarchy.  It is the responsibility of the exporter to make
"^DD",8925.1,8925.1,3.02,21,9,0)
sure all ancestors which are necessary for the proper behavior of an
"^DD",8925.1,8925.1,3.02,21,10,0)
exported entry are also exported with it (or are already present at sites
"^DD",8925.1,8925.1,3.02,21,11,0)
receiving the exported entries).
"^DD",8925.1,8925.1,3.02,21,12,0)
 
"^DD",8925.1,8925.1,3.02,21,13,0)
Field is NOT heritable.  BASIC field.
"^DD",8925.1,8925.1,3.02,"DT")
2970128
"^DD",8925.1,8925.1,3.03,0)
SUPPRESS VISIT SELECTION^S^1:YES;0:NO;^3;3^Q
"^DD",8925.1,8925.1,3.03,3)
Enter 1 for YES ONLY IF this is an administrative note which creates its own historical visit.  You will NOT receive workload credit for such visits.
"^DD",8925.1,8925.1,3.03,21,0)
^^17^17^2970220^
"^DD",8925.1,8925.1,3.03,21,1,0)
Applies to entries of Type Class, Document Class, and Title.
"^DD",8925.1,8925.1,3.03,21,2,0)
 
"^DD",8925.1,8925.1,3.03,21,3,0)
For most documents it is very important that the user entering a document
"^DD",8925.1,8925.1,3.03,21,4,0)
select the appropriate visit to link the document with.  However, 
"^DD",8925.1,8925.1,3.03,21,5,0)
certain administrative documents for outpatients have no particular visit
"^DD",8925.1,8925.1,3.03,21,6,0)
that they should be linked with.  For example, a clinician could have a
"^DD",8925.1,8925.1,3.03,21,7,0)
chance encounter with a patient in the corridor and want to document the
"^DD",8925.1,8925.1,3.03,21,8,0)
discussion, or a clinician could simply want to remind him/herself of
"^DD",8925.1,8925.1,3.03,21,9,0)
something for a given patient.  Documents for such purposes can be set to
"^DD",8925.1,8925.1,3.03,21,10,0)
automatically create their own historical visit when they are entered, so
"^DD",8925.1,8925.1,3.03,21,11,0)
that the user is not asked to select a visit.
"^DD",8925.1,8925.1,3.03,21,12,0)
 
"^DD",8925.1,8925.1,3.03,21,13,0)
Warning:  Such documents DO NOT GIVE WORKLOAD CREDIT.
"^DD",8925.1,8925.1,3.03,21,14,0)
 
"^DD",8925.1,8925.1,3.03,21,15,0)
Heritable.  BASIC field.  If field has no value and there is no value
"^DD",8925.1,8925.1,3.03,21,16,0)
to inherit, default value is NO.  For information on editing heritable
"^DD",8925.1,8925.1,3.03,21,17,0)
fields, see Technical Field Edit Template.
"^DD",8925.1,8925.1,3.03,"DT")
2970124
"^DD",8925.1,8925.1,4,0)
UPLOAD LOOK-UP METHOD^K^^4;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4,3)
Please enter the MUMPS code to be executed for record location.
"^DD",8925.1,8925.1,4,9)
@
"^DD",8925.1,8925.1,4,21,0)
^^12^12^2970107^^
"^DD",8925.1,8925.1,4,21,1,0)
Sometimes when an entry is uploaded into the target file, a new entry is
"^DD",8925.1,8925.1,4,21,2,0)
created for it.  However, in other cases such as for Operative Reports, or
"^DD",8925.1,8925.1,4,21,3,0)
for an addendum, the file entry already exists and must be looked-up and
"^DD",8925.1,8925.1,4,21,4,0)
edited.
"^DD",8925.1,8925.1,4,21,5,0)
 
"^DD",8925.1,8925.1,4,21,6,0)
Look-Up Method is the MUMPS code invoked to perform such a look-up on the
"^DD",8925.1,8925.1,4,21,7,0)
target file.  If a look-up is necessary and this field is blank, a regular
"^DD",8925.1,8925.1,4,21,8,0)
DIC lookup is performed.  If the regular DIC lookup is not sufficient to
"^DD",8925.1,8925.1,4,21,9,0)
locate the appropriate entry, this field should contain the lookup.  It
"^DD",8925.1,8925.1,4,21,10,0)
should expect any look-up special variables named in the header fields as
"^DD",8925.1,8925.1,4,21,11,0)
input variables, and should return the variable Y in DIC-compatible format
"^DD",8925.1,8925.1,4,21,12,0)
(i.e., IEN^EXTERNAL VALUE[^1]).
"^DD",8925.1,8925.1,4,"DT")
2960729
"^DD",8925.1,8925.1,4.1,0)
COMMIT ACTION^K^^4.1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.1,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.1,9)
@
"^DD",8925.1,8925.1,4.1,21,0)
^^3^3^2980122^
"^DD",8925.1,8925.1,4.1,21,1,0)
This M-Code is executed when the TIU document is "committed" to the
"^DD",8925.1,8925.1,4.1,21,2,0)
database (i.e., when the document is saved, and prior to release,
"^DD",8925.1,8925.1,4.1,21,3,0)
verification, or signature).  Heritable. TECHNICAL field.
"^DD",8925.1,8925.1,4.1,"DT")
2971126
"^DD",8925.1,8925.1,4.2,0)
RELEASE ACTION^K^^4.2;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.2,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.2,9)
@
"^DD",8925.1,8925.1,4.2,21,0)
^^2^2^2980126^^
"^DD",8925.1,8925.1,4.2,21,1,0)
This M-Code is executed upon Release of the document.  Heritable.
"^DD",8925.1,8925.1,4.2,21,2,0)
TECHNICAL field.
"^DD",8925.1,8925.1,4.2,"DT")
2971126
"^DD",8925.1,8925.1,4.3,0)
VERIFICATION ACTION^K^^4.3;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.3,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.3,9)
@
"^DD",8925.1,8925.1,4.3,21,0)
^^2^2^2980122^
"^DD",8925.1,8925.1,4.3,21,1,0)
This M-Code is executed upon Verification of the document.  Heritable.
"^DD",8925.1,8925.1,4.3,21,2,0)
TECHNICAL field.
"^DD",8925.1,8925.1,4.3,"DT")
2971126
"^DD",8925.1,8925.1,4.4,0)
DELETE ACTION^K^^4.4;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.4,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.4,9)
@
"^DD",8925.1,8925.1,4.4,21,0)
^^2^2^2980122^
"^DD",8925.1,8925.1,4.4,21,1,0)
This M-Code is executed upon Deletion of the document.  Heritable.
"^DD",8925.1,8925.1,4.4,21,2,0)
TECHNICAL field.
"^DD",8925.1,8925.1,4.4,"DT")
2971126
"^DD",8925.1,8925.1,4.45,0)
PACKAGE REASSIGNMENT ACTION^K^^4.45;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.45,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.45,9)
@
"^DD",8925.1,8925.1,4.45,21,0)
^^2^2^2980122^
"^DD",8925.1,8925.1,4.45,21,1,0)
This M-Code is executed when a document with a link to a client
"^DD",8925.1,8925.1,4.45,21,2,0)
application is Reassigned.  Heritable.  TECHNICAL field.
"^DD",8925.1,8925.1,4.45,"DT")
2971202
"^DD",8925.1,8925.1,4.5,0)
UPLOAD POST-FILING CODE^K^^4.5;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.5,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.5,9)
@
"^DD",8925.1,8925.1,4.5,21,0)
^^4^4^2970522^
"^DD",8925.1,8925.1,4.5,21,1,0)
This field specifies code to be executed following the successful filing
"^DD",8925.1,8925.1,4.5,21,2,0)
of an uploaded record. It may be used to send bulletins or alerts,
"^DD",8925.1,8925.1,4.5,21,3,0)
evaluate expected signers/cosigners, trigger events, update statuses, or
"^DD",8925.1,8925.1,4.5,21,4,0)
whatever the designer of the application deems appropriate.
"^DD",8925.1,8925.1,4.5,"DT")
2960729
"^DD",8925.1,8925.1,4.6,0)
ENTRY ACTION^KX^^4.6;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.6,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.6,9)
@
"^DD",8925.1,8925.1,4.6,21,0)
^^3^3^2980126^^
"^DD",8925.1,8925.1,4.6,21,1,0)
This M-Code is executed during the Entry/Editing of a document, after
"^DD",8925.1,8925.1,4.6,21,2,0)
selection of the Title, and prior to selection of the Patient. It may be
"^DD",8925.1,8925.1,4.6,21,3,0)
used to set up environmental variables, etc.  Heritable.  TECHNICAL field.
"^DD",8925.1,8925.1,4.6,"DT")
2961022
"^DD",8925.1,8925.1,4.7,0)
EXIT ACTION^KX^^4.7;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.7,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.7,9)
@
"^DD",8925.1,8925.1,4.7,21,0)
^^3^3^2980126^^
"^DD",8925.1,8925.1,4.7,21,1,0)
This M-Code is executed just prior to Exit from the entry/edit process
"^DD",8925.1,8925.1,4.7,21,2,0)
for a document.  It may be used to send alerts or bulletins, clean up
"^DD",8925.1,8925.1,4.7,21,3,0)
temporary global variables, etc.  Heritable.  TECHNICAL field.
"^DD",8925.1,8925.1,4.7,"DT")
2961022
"^DD",8925.1,8925.1,4.8,0)
UPLOAD FILING ERROR CODE^K^^4.8;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.8,.1)
UPLOAD FILING ERROR RESOLUTION CODE
"^DD",8925.1,8925.1,4.8,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.8,9)
@
"^DD",8925.1,8925.1,4.8,21,0)
^^6^6^2970106^
"^DD",8925.1,8925.1,4.8,21,1,0)
This MUMPS-type field specifies the code to be executed when the user
"^DD",8925.1,8925.1,4.8,21,2,0)
attempts to resolve a filing error.  Filing Errors may be resolved either
"^DD",8925.1,8925.1,4.8,21,3,0)
by responding to a Filing Error Alert or through the option to Review
"^DD",8925.1,8925.1,4.8,21,4,0)
Upload Events.  Typically, the code will offer the user an opportunity to
"^DD",8925.1,8925.1,4.8,21,5,0)
look up online information necessary to resolve the error (e.g.,
"^DD",8925.1,8925.1,4.8,21,6,0)
demographic, or case-related information).
"^DD",8925.1,8925.1,4.8,"DT")
2960729
"^DD",8925.1,8925.1,4.9,0)
POST-SIGNATURE CODE^K^^4.9;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,4.9,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,4.9,9)
@
"^DD",8925.1,8925.1,4.9,21,0)
^^2^2^2980126^^
"^DD",8925.1,8925.1,4.9,21,1,0)
This M-Code is executed following Signature (or Cosignature) of a TIU
"^DD",8925.1,8925.1,4.9,21,2,0)
document.  Heritable.  TECHNICAL field.
"^DD",8925.1,8925.1,4.9,"DT")
2971001
"^DD",8925.1,8925.1,5,0)
EDIT TEMPLATE^FX^^5;E1,245^K:$L(X)>60!($L(X)<2) X
"^DD",8925.1,8925.1,5,3)
Enter the name of the Input Template for documents defined by this entry.
"^DD",8925.1,8925.1,5,4)
D HELP1^TIUFXHLX(5)
"^DD",8925.1,8925.1,5,9)
@
"^DD",8925.1,8925.1,5,21,0)
^^19^19^2980126^^
"^DD",8925.1,8925.1,5,21,1,0)
Applies to Classes, Document Classes, Titles.  This is the Input Template
"^DD",8925.1,8925.1,5,21,2,0)
for Entering/Editing documents defined by this entry.  Template
"^DD",8925.1,8925.1,5,21,3,0)
includes fixed field information such as Patient, etc.  Enter Edit
"^DD",8925.1,8925.1,5,21,4,0)
Template in Format [TEMPLATE NAME], or as a "field-string" (e.g.,
"^DD",8925.1,8925.1,5,21,5,0)
.01;1;3;5).  Heritable.  TECHNICAL field.
"^DD",8925.1,8925.1,5,21,6,0)
 
"^DD",8925.1,8925.1,5,21,7,0)
NOTE on editing heritable fields:
"^DD",8925.1,8925.1,5,21,8,0)
 
"^DD",8925.1,8925.1,5,21,9,0)
When editing heritable fields, the user is presented with the EFFECTIVE
"^DD",8925.1,8925.1,5,21,10,0)
value of the field as the default (e.g. NO//).  This is the same as the
"^DD",8925.1,8925.1,5,21,11,0)
value shown in the display and is the field's own value if it has one, the
"^DD",8925.1,8925.1,5,21,12,0)
inherited value if the field does not have its own value, or the default
"^DD",8925.1,8925.1,5,21,13,0)
for the field if the field has neither its own nor an inherited value. If
"^DD",8925.1,8925.1,5,21,14,0)
the user accepts this default by pressing return, the value is made
"^DD",8925.1,8925.1,5,21,15,0)
explicit, i.e., entered into the field.  If a user does NOT want to make
"^DD",8925.1,8925.1,5,21,16,0)
the value explicit, the user should enter @, which leaves a blank field
"^DD",8925.1,8925.1,5,21,17,0)
blank.  If the user want to delete an explicit value, the user should
"^DD",8925.1,8925.1,5,21,18,0)
enter @, which deletes the field value, leaving TIU to use the effective
"^DD",8925.1,8925.1,5,21,19,0)
value for the field.
"^DD",8925.1,8925.1,5,"DT")
2961022
"^DD",8925.1,8925.1,6,0)
PRINT METHOD^KX^^6;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,6,3)
Please enter the MUMPS code to be executed to print a record.
"^DD",8925.1,8925.1,6,4)
D HELP1^TIUFXHLX(6)
"^DD",8925.1,8925.1,6,9)
@
"^DD",8925.1,8925.1,6,21,0)
^^5^5^2980126^^
"^DD",8925.1,8925.1,6,21,1,0)
Applies to Types Class, Document Class, Title.  This M-Code is executed
"^DD",8925.1,8925.1,6,21,2,0)
when a document is Printed from the TIU List Manager screen (as opposed to
"^DD",8925.1,8925.1,6,21,3,0)
a separate print option which may have its own code.) Heritable. TECHNICAL
"^DD",8925.1,8925.1,6,21,4,0)
field.  For more information on editing heritable fields, see Technical
"^DD",8925.1,8925.1,6,21,5,0)
field Edit Template.
"^DD",8925.1,8925.1,6,"DT")
2961022
"^DD",8925.1,8925.1,6.1,0)
PRINT FORM HEADER^FX^^6.1;1^K:$L(X)>40!($L(X)<3) X
"^DD",8925.1,8925.1,6.1,3)
Answer must be 3-40 characters in length.
"^DD",8925.1,8925.1,6.1,4)
D HELP1^TIUFXHLX(6.1)
"^DD",8925.1,8925.1,6.1,21,0)
^^12^12^2970108^^
"^DD",8925.1,8925.1,6.1,21,1,0)
For basic information on Print Form Header see Technical field Allow
"^DD",8925.1,8925.1,6.1,21,2,0)
Custom Form Headers.
"^DD",8925.1,8925.1,6.1,21,3,0)
 
"^DD",8925.1,8925.1,6.1,21,4,0)
The Print Form Header is the official medical record title of the document
"^DD",8925.1,8925.1,6.1,21,5,0)
which has been approved by the Medical Record Committee based on national
"^DD",8925.1,8925.1,6.1,21,6,0)
guidelines.
"^DD",8925.1,8925.1,6.1,21,7,0)
  
"^DD",8925.1,8925.1,6.1,21,8,0)
Examples:  Progress Notes, Physical Examination, History - Part 1, etc.
"^DD",8925.1,8925.1,6.1,21,9,0)
 
"^DD",8925.1,8925.1,6.1,21,10,0)
This field is heritable with lower level values overriding higher ones AS
"^DD",8925.1,8925.1,6.1,21,11,0)
LONG AS the field is applicable.  See Allow Custom Form Headers.  Print
"^DD",8925.1,8925.1,6.1,21,12,0)
Form Header is a TECHNICAL field.
"^DD",8925.1,8925.1,6.1,23,0)
^^6^6^2970108^^^^
"^DD",8925.1,8925.1,6.1,23,1,0)
The narrative stored in this field will display as the form header of a
"^DD",8925.1,8925.1,6.1,23,2,0)
document. If entered at a CLASS level such as FORMS, all forms documents
"^DD",8925.1,8925.1,6.1,23,3,0)
will display entered header as the form header of the document.  If
"^DD",8925.1,8925.1,6.1,23,4,0)
the free text is entered at a lower level (i.e., TITLE), this form header
"^DD",8925.1,8925.1,6.1,23,5,0)
will override the one entered at the higher level and will be displayed on
"^DD",8925.1,8925.1,6.1,23,6,0)
the form.
"^DD",8925.1,8925.1,6.1,"DT")
2961022
"^DD",8925.1,8925.1,6.12,0)
PRINT FORM NUMBER^FX^^6.1;2^K:$L(X)>20!($L(X)<3) X
"^DD",8925.1,8925.1,6.12,3)
Answer must be 3-20 characters in length.
"^DD",8925.1,8925.1,6.12,4)
D HELP1^TIUFXHLX(6.12)
"^DD",8925.1,8925.1,6.12,21,0)
^^13^13^2970106^
"^DD",8925.1,8925.1,6.12,21,1,0)
For basic information on Print Form Number see Technical field Allow
"^DD",8925.1,8925.1,6.12,21,2,0)
Custom Form Headers.
"^DD",8925.1,8925.1,6.12,21,3,0)
 
"^DD",8925.1,8925.1,6.12,21,4,0)
The Print Form Number is the official medical record form number of the
"^DD",8925.1,8925.1,6.12,21,5,0)
document which has been approved by the Medical Record Committee based
"^DD",8925.1,8925.1,6.12,21,6,0)
on national guidelines.
"^DD",8925.1,8925.1,6.12,21,7,0)
 
"^DD",8925.1,8925.1,6.12,21,8,0)
Example:  Progress Note - Vice SF 509, Consult - SF 513, Physicial
"^DD",8925.1,8925.1,6.12,21,9,0)
Examination - SF 506.
"^DD",8925.1,8925.1,6.12,21,10,0)
 
"^DD",8925.1,8925.1,6.12,21,11,0)
Field is heritable with lower level values overriding higher ones AS LONG
"^DD",8925.1,8925.1,6.12,21,12,0)
AS the field is applicable.  See field Allow Custom Form Headers.  Print
"^DD",8925.1,8925.1,6.12,21,13,0)
Form Header is a TECHNICAL field.
"^DD",8925.1,8925.1,6.12,23,0)
^^6^6^2970106^^^^
"^DD",8925.1,8925.1,6.12,23,1,0)
The free text stored in this field will be displayed as the form number of
"^DD",8925.1,8925.1,6.12,23,2,0)
a document.  If entered at a CLASS level such as Forms, all Forms
"^DD",8925.1,8925.1,6.12,23,3,0)
documents will display the entered value as the form number of the
"^DD",8925.1,8925.1,6.12,23,4,0)
document.  If the free text is entered at a lower level (i.e., TITLE),
"^DD",8925.1,8925.1,6.12,23,5,0)
this value will override the one entered at the higher level and will be
"^DD",8925.1,8925.1,6.12,23,6,0)
displayed on the form.
"^DD",8925.1,8925.1,6.12,"DT")
2961022
"^DD",8925.1,8925.1,6.13,0)
PRINT GROUP^NJ2,0X^^6.1;3^K:+X'=X!(X>10)!(X<1)!(X?.E1"."1N.N) X
"^DD",8925.1,8925.1,6.13,3)
Type a Number between 1 and 10, 0 Decimal Digits.  Enter ?? for help.
"^DD",8925.1,8925.1,6.13,4)
D HELP1^TIUFXHLX(6.13)
"^DD",8925.1,8925.1,6.13,21,0)
^^19^19^2970106^
"^DD",8925.1,8925.1,6.13,21,1,0)
For basic information on Print Group see Technical field Allow Custom Form
"^DD",8925.1,8925.1,6.13,21,2,0)
Headers.
"^DD",8925.1,8925.1,6.13,21,3,0)
 
"^DD",8925.1,8925.1,6.13,21,4,0)
Print Group is an integer number which serves to group by print form
"^DD",8925.1,8925.1,6.13,21,5,0)
headers/numbers related documents that share a common print method; e.g.,
"^DD",8925.1,8925.1,6.13,21,6,0)
Progress Notes, H&P's, and other documents may share a common print
"^DD",8925.1,8925.1,6.13,21,7,0)
method, but have differing form headers/numbers and should each print in
"^DD",8925.1,8925.1,6.13,21,8,0)
their own, separate collation.  Specifying a common print group for
"^DD",8925.1,8925.1,6.13,21,9,0)
documents with the same headers/numbers (for example, Progress Notes have
"^DD",8925.1,8925.1,6.13,21,10,0)
Print Group 2, H&P's might have Print Group 7) causes such documents
"^DD",8925.1,8925.1,6.13,21,11,0)
from each print group to collate together when a mixed print is called
"^DD",8925.1,8925.1,6.13,21,12,0)
for.
"^DD",8925.1,8925.1,6.13,21,13,0)
 
"^DD",8925.1,8925.1,6.13,21,14,0)
Since documents collate first by print method, then by print group, print
"^DD",8925.1,8925.1,6.13,21,15,0)
group is not necessary unless documents share a common print method.
"^DD",8925.1,8925.1,6.13,21,16,0)
 
"^DD",8925.1,8925.1,6.13,21,17,0)
Print Group is heritable with lower level values overriding higher ones AS
"^DD",8925.1,8925.1,6.13,21,18,0)
LONG AS the field is applicable.  See Allow Custom Form Headers.  Print
"^DD",8925.1,8925.1,6.13,21,19,0)
Group is a TECHNICAL field.
"^DD",8925.1,8925.1,6.13,"DT")
2961022
"^DD",8925.1,8925.1,6.14,0)
ALLOW CUSTOM FORM HEADERS^SX^1:YES;0:NO;^6.1;4^Q
"^DD",8925.1,8925.1,6.14,.1)
ALLOW CUSTOM FORM HEADERS/NUMBERS AT LOWER LEVELS
"^DD",8925.1,8925.1,6.14,3)
May be set for Types CL and DC only.  Enter 1 for YES if descendent Titles can have individual (Custom) Form Headers/Numbers within their Document Class.  Otherwise enter 0.
"^DD",8925.1,8925.1,6.14,4)
D CUSTOM^TIUFXHLX
"^DD",8925.1,8925.1,6.14,21,0)
^^69^69^2980122^
"^DD",8925.1,8925.1,6.14,21,1,0)
Allow Custom Form Headers may be set for entries of Type Class or Document
"^DD",8925.1,8925.1,6.14,21,2,0)
Class and affects DESCENDANTS of the entry for which it is set.
"^DD",8925.1,8925.1,6.14,21,3,0)
 
"^DD",8925.1,8925.1,6.14,21,4,0)
Information on Form Headers, Form Numbers, Print Group, and Allow Custom
"^DD",8925.1,8925.1,6.14,21,5,0)
Form Headers:
"^DD",8925.1,8925.1,6.14,21,6,0)
 
"^DD",8925.1,8925.1,6.14,21,7,0)
Some clinical documents use Forms with Form Headers and Form Numbers, for
"^DD",8925.1,8925.1,6.14,21,8,0)
example, Progress Note Forms have Header 'Progress Notes' and Number 'Vice
"^DD",8925.1,8925.1,6.14,21,9,0)
SF 509.'
"^DD",8925.1,8925.1,6.14,21,10,0)
 
"^DD",8925.1,8925.1,6.14,21,11,0)
The Owner of a Document Definition must decide whether all documents
"^DD",8925.1,8925.1,6.14,21,12,0)
descending from the entry will have the SAME Header/Number, or whether to
"^DD",8925.1,8925.1,6.14,21,13,0)
allow CUSTOM (varying) Headers/Numbers at lower levels.
"^DD",8925.1,8925.1,6.14,21,14,0)
 
"^DD",8925.1,8925.1,6.14,21,15,0)
Allow Custom Headers holds the decision: If the field has value 0 for NO,
"^DD",8925.1,8925.1,6.14,21,16,0)
then ALL descendant documents use a COMMON Header/Number (or perhaps they
"^DD",8925.1,8925.1,6.14,21,17,0)
all use NO Header/Number); they also collate together in printouts.
"^DD",8925.1,8925.1,6.14,21,18,0)
 
"^DD",8925.1,8925.1,6.14,21,19,0)
For example, Class Progress Notes does NOT Allow Custom Form Headers. This
"^DD",8925.1,8925.1,6.14,21,20,0)
means that ALL Progress Note Titles have the same header and the same form
"^DD",8925.1,8925.1,6.14,21,21,0)
number.  For Class Progress Notes, Field Print Form Header holds the
"^DD",8925.1,8925.1,6.14,21,22,0)
header 'Progress Notes', Field Print Form Number holds Form Number 'Vice
"^DD",8925.1,8925.1,6.14,21,23,0)
SF 509', and Field Print Group holds '2'.  Since Class Progress Notes does
"^DD",8925.1,8925.1,6.14,21,24,0)
not Allow Custom Form Headers,  these field values apply for ALL Progress
"^DD",8925.1,8925.1,6.14,21,25,0)
Note Titles.  That is, all Progress Notes have header 'Progress Notes',
"^DD",8925.1,8925.1,6.14,21,26,0)
Form Number 'Vice SF 509', and collate together in printouts.
"^DD",8925.1,8925.1,6.14,21,27,0)
 
"^DD",8925.1,8925.1,6.14,21,28,0)
Field Allow Custom Field Headers also determines whether or not related
"^DD",8925.1,8925.1,6.14,21,29,0)
Fields Print Form Header, Print Form Number, Print Group, (and even Allow
"^DD",8925.1,8925.1,6.14,21,30,0)
Custom Field Headers) are applicable at lower levels.  If an entry at a
"^DD",8925.1,8925.1,6.14,21,31,0)
particular level DOES allow Custom Form Headers, then these related fields
"^DD",8925.1,8925.1,6.14,21,32,0)
DO APPLY to descendants at the next lower level.  If an entry at a
"^DD",8925.1,8925.1,6.14,21,33,0)
particular level DOES NOT allow Custom Form Headers, then ALL LOWER LEVELS
"^DD",8925.1,8925.1,6.14,21,34,0)
inherit the the prohibition, and the related fields DO NOT APPLY at ANY
"^DD",8925.1,8925.1,6.14,21,35,0)
lower levels.
"^DD",8925.1,8925.1,6.14,21,36,0)
  
"^DD",8925.1,8925.1,6.14,21,37,0)
Example: Since Class Progress Notes does NOT Allow Custom Form Headers,
"^DD",8925.1,8925.1,6.14,21,38,0)
fields Print Form Header, Print Form Number, Print Group, and Allow Custom
"^DD",8925.1,8925.1,6.14,21,39,0)
Field Headers DO NOT APPLY to Document Classes or Titles under Progress
"^DD",8925.1,8925.1,6.14,21,40,0)
Notes.  This means that Document Definitions for documents requiring
"^DD",8925.1,8925.1,6.14,21,41,0)
different Form Headers/Numbers must be placed under a separate line of
"^DD",8925.1,8925.1,6.14,21,42,0)
descent in the hierarchy; they cannot be under Progress Notes.
"^DD",8925.1,8925.1,6.14,21,43,0)
 
"^DD",8925.1,8925.1,6.14,21,44,0)
Example: Class Clinical Documents, the Mother of all Document Definitions,
"^DD",8925.1,8925.1,6.14,21,45,0)
does not want to REQUIRE all Document Definitions under it to use one
"^DD",8925.1,8925.1,6.14,21,46,0)
common Header.  So Clinical Documents DOES Allow Custom Form Headers.
"^DD",8925.1,8925.1,6.14,21,47,0)
Classes/Document Classes UNDER CLinical Documents can decide for
"^DD",8925.1,8925.1,6.14,21,48,0)
themselves whether or not to Allow Custom Headers for their own Items.
"^DD",8925.1,8925.1,6.14,21,49,0)
 
"^DD",8925.1,8925.1,6.14,21,50,0)
Example: Class DISCHARGE SUMMARY has only one Form Header and Number which
"^DD",8925.1,8925.1,6.14,21,51,0)
is used by all Discharge Summary documents. So Class Discharge Summary
"^DD",8925.1,8925.1,6.14,21,52,0)
does NOT Allow Custom Headers.
"^DD",8925.1,8925.1,6.14,21,53,0)
 
"^DD",8925.1,8925.1,6.14,21,54,0)
Example: Class FORMS might contain miscellaneous documents, each using
"^DD",8925.1,8925.1,6.14,21,55,0)
a different Form with its own Form Header and Form Number.  So Class Forms
"^DD",8925.1,8925.1,6.14,21,56,0)
would Allow Custom Headers.
"^DD",8925.1,8925.1,6.14,21,57,0)
 
"^DD",8925.1,8925.1,6.14,21,58,0)
Field Allow Custom Form Headers may be set for Document Definitions of
"^DD",8925.1,8925.1,6.14,21,59,0)
Type Class or Document Class only, and affects the DESCENDANTS of the
"^DD",8925.1,8925.1,6.14,21,60,0)
entry for which it is set.
"^DD",8925.1,8925.1,6.14,21,61,0)
 
"^DD",8925.1,8925.1,6.14,21,62,0)
If a DOCUMENT CLASS Allows Custom Form Headers, then TIUF, the Document
"^DD",8925.1,8925.1,6.14,21,63,0)
Definition Utility, does not permit a descendant Title to be activated
"^DD",8925.1,8925.1,6.14,21,64,0)
unless fields Print Form Header, Print Form Number, and Print Group have a
"^DD",8925.1,8925.1,6.14,21,65,0)
value (of their own or inherited).  If NO Header, or Number is desired,
"^DD",8925.1,8925.1,6.14,21,66,0)
enter 'NONE'. If NO Print Group is desired, enter '0'.
"^DD",8925.1,8925.1,6.14,21,67,0)
 
"^DD",8925.1,8925.1,6.14,21,68,0)
For information on editing heritable fields, see Technical field Edit
"^DD",8925.1,8925.1,6.14,21,69,0)
Template.
"^DD",8925.1,8925.1,6.14,"DT")
2970128
"^DD",8925.1,8925.1,6.5,0)
ON BROWSE EVENT^K^^6.5;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,6.5,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,6.5,9)
@
"^DD",8925.1,8925.1,6.5,21,0)
^^2^2^3010215^
"^DD",8925.1,8925.1,6.5,21,1,0)
This is MUMPS code which is invoked on browsing a document to fetch data
"^DD",8925.1,8925.1,6.5,21,2,0)
from the Requesting Package that will be included in the display.
"^DD",8925.1,8925.1,6.5,"DT")
3010215
"^DD",8925.1,8925.1,6.51,0)
ON RETRACT EVENT^K^^6.51;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,6.51,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,6.51,9)
@
"^DD",8925.1,8925.1,6.51,21,0)
^^2^2^3010301^
"^DD",8925.1,8925.1,6.51,21,1,0)
This is MUMPS code which is invoked on retraction of a document to perform
"^DD",8925.1,8925.1,6.51,21,2,0)
any processing task that the Requesting Package may require.
"^DD",8925.1,8925.1,6.51,"DT")
3010301
"^DD",8925.1,8925.1,7,0)
VISIT LINKAGE METHOD^KX^^7;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,7,3)
Please enter the MUMPS code to be executed to establish Visit Linkage.
"^DD",8925.1,8925.1,7,4)
D HELP1^TIUFXHLX(7)
"^DD",8925.1,8925.1,7,9)
@
"^DD",8925.1,8925.1,7,21,0)
^^6^6^2980122^
"^DD",8925.1,8925.1,7,21,1,0)
Applies to Types Class, Document Class, Title.  This M-Code is executed to
"^DD",8925.1,8925.1,7,21,2,0)
establish Visit Linkage, usually displaying appropriate visits and
"^DD",8925.1,8925.1,7,21,3,0)
prompting the user to select the correct one.
"^DD",8925.1,8925.1,7,21,4,0)
 
"^DD",8925.1,8925.1,7,21,5,0)
Heritable.  TECHNICAL Field.  For information on editing heritable fields,
"^DD",8925.1,8925.1,7,21,6,0)
see Technical Field Edit Template.
"^DD",8925.1,8925.1,7,"DT")
2961022
"^DD",8925.1,8925.1,8,0)
VALIDATION METHOD^KX^^8;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,8,3)
Please enter the MUMPS code to be executed to validate the selection of patient and Visit/Admission.
"^DD",8925.1,8925.1,8,4)
D HELP1^TIUFXHLX(8)
"^DD",8925.1,8925.1,8,9)
@
"^DD",8925.1,8925.1,8,21,0)
^^7^7^2980126^^
"^DD",8925.1,8925.1,8,21,1,0)
Applies to Types Class, Document Class, Title.  This is the M-Code to be
"^DD",8925.1,8925.1,8,21,2,0)
invoked when Validating the visit and other fixed field information on a
"^DD",8925.1,8925.1,8,21,3,0)
record during entry/edit.  User is asked to OK or to correct the
"^DD",8925.1,8925.1,8,21,4,0)
information.
"^DD",8925.1,8925.1,8,21,5,0)
 
"^DD",8925.1,8925.1,8,21,6,0)
Heritable.  TECHNICAL field.  For information on editing heritable fields,
"^DD",8925.1,8925.1,8,21,7,0)
see Technical field Edit Template.
"^DD",8925.1,8925.1,8,"DT")
2961022
"^DD",8925.1,8925.1,9,0)
OBJECT METHOD^KX^^9;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.1,9,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.1,9,9)
@
"^DD",8925.1,8925.1,9,21,0)
^^3^3^2980122^
"^DD",8925.1,8925.1,9,21,1,0)
Applies to Objects.  This M-Code is invoked when a document is entered
"^DD",8925.1,8925.1,9,21,2,0)
whose boilerplate text contains the object.  Extracted data are inserted
"^DD",8925.1,8925.1,9,21,3,0)
into document text.  Author then edits/adds to text.  TECHNICAL field.
"^DD",8925.1,8925.1,9,"DT")
2961022
"^DD",8925.1,8925.1,10,0)
ITEM^8925.14P^^10;0
"^DD",8925.1,8925.1,11,0)
STAT AUTO PRINT EVENT^8925.111SA^^11;0
"^DD",8925.1,8925.1,11,21,0)
^^35^35^2970220^
"^DD",8925.1,8925.1,11,21,1,0)
This parameter applies only to stat documents.
"^DD",8925.1,8925.1,11,21,2,0)
 
"^DD",8925.1,8925.1,11,21,3,0)
This parameter determines at what stage(s) a document should be
"^DD",8925.1,8925.1,11,21,4,0)
automatically printed for chart, either singly when document is ready, or
"^DD",8925.1,8925.1,11,21,5,0)
in batch mode.
"^DD",8925.1,8925.1,11,21,6,0)
 
"^DD",8925.1,8925.1,11,21,7,0)
Some documents will need to be printed for chart only when they are
"^DD",8925.1,8925.1,11,21,8,0)
complete, ie have obtained all expected signatures and cosignatures.
"^DD",8925.1,8925.1,11,21,9,0)
Others should perhaps be printed for chart at an earlier stage, allowing
"^DD",8925.1,8925.1,11,21,10,0)
earlier chart access, and then be reprinted when complete. Documents may
"^DD",8925.1,8925.1,11,21,11,0)
also need to be reprinted AFTER completion for certain events such as
"^DD",8925.1,8925.1,11,21,12,0)
amendment.
"^DD",8925.1,8925.1,11,21,13,0)
 
"^DD",8925.1,8925.1,11,21,14,0)
Any event which should trigger auto printing of the document should be
"^DD",8925.1,8925.1,11,21,15,0)
entered as an auto print event.
"^DD",8925.1,8925.1,11,21,16,0)
 
"^DD",8925.1,8925.1,11,21,17,0)
- SIGNED means firstline signature, as opposed to secondline cosignature.
"^DD",8925.1,8925.1,11,21,18,0)
- COSIGNED, OPTIONAL, INCOMPLETE means when an incomplete document obtains
"^DD",8925.1,8925.1,11,21,19,0)
an optional cosignature.
"^DD",8925.1,8925.1,11,21,20,0)
- COSIGNED, OPTIONAL, COMPLETED means when a previously completed
"^DD",8925.1,8925.1,11,21,21,0)
document obtains an optional cosignature, namely, a walkup.
"^DD",8925.1,8925.1,11,21,22,0)
- COMPLETED means when some event occurs that completes the document, for
"^DD",8925.1,8925.1,11,21,23,0)
example the document obtains its last expected optional cosignature.
"^DD",8925.1,8925.1,11,21,24,0)
 
"^DD",8925.1,8925.1,11,21,25,0)
If one event occurs to a document and corresponds to two selected print
"^DD",8925.1,8925.1,11,21,26,0)
events (such as COMPLETED and COSIGNED OPTIONAL INCOMPLETE), the document
"^DD",8925.1,8925.1,11,21,27,0)
will only print once.
"^DD",8925.1,8925.1,11,21,28,0)
 
"^DD",8925.1,8925.1,11,21,29,0)
If parameter is not entered and Document Definition has no ancestor to
"^DD",8925.1,8925.1,11,21,30,0)
inherit from, parameter assumes default value N for NONE.  If parameter is
"^DD",8925.1,8925.1,11,21,31,0)
not entered and Document Definition has a parent to inherit from, then
"^DD",8925.1,8925.1,11,21,32,0)
parameter assumes value (assumed or explicit) of parent print events. If
"^DD",8925.1,8925.1,11,21,33,0)
parameter is non applicable because Document Definition does not allow
"^DD",8925.1,8925.1,11,21,34,0)
stat documents, or because Document Definition does not allow auto
"^DD",8925.1,8925.1,11,21,35,0)
printing, enter N for NONE.
"^DD",8925.1,8925.1,11,"DT")
2940621
"^DD",8925.1,8925.1,12,0)
ROUTINE AUTO PRINT EVENT^8925.112SA^^12;0
"^DD",8925.1,8925.1,12,21,0)
^^5^5^2970220^
"^DD",8925.1,8925.1,12,21,1,0)
This parameter applies to routine (non-stat) documents only. Documents
"^DD",8925.1,8925.1,12,21,2,0)
whose Document Definitions do not allow stat documents are considered
"^DD",8925.1,8925.1,12,21,3,0)
routine.
"^DD",8925.1,8925.1,12,21,4,0)
 
"^DD",8925.1,8925.1,12,21,5,0)
See parameter STAT AUTO PRINT EVENT for description.
"^DD",8925.1,8925.1,13,0)
PROCESSING STEPS^8925.113P^^13;0
"^DD",8925.1,8925.1,13,21,0)
^^3^3^2950216^^
"^DD",8925.1,8925.1,13,21,1,0)
This sub-file contains the optional and required steps for processing any 
"^DD",8925.1,8925.1,13,21,2,0)
document, along with the states (e.g., unverified -> unsigned) that a given
"^DD",8925.1,8925.1,13,21,3,0)
step (e.g., verification) moves the document between.
"^DD",8925.1,8925.1,14,0)
DIALOG^8925.114^^DIALOG;0
"^DD",8925.1,8925.1,14,21,0)
^^2^2^2950606^
"^DD",8925.1,8925.1,14,21,1,0)
This sub-file contains the data necessary to handle server-based definition 
"^DD",8925.1,8925.1,14,21,2,0)
for fixed-field data capture in TIU.
"^DD",8925.1,8925.1,99,0)
TIMESTAMP^F^^99;1^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>15!($L(X)<1) X
"^DD",8925.1,8925.1,99,1,0)
^.1
"^DD",8925.1,8925.1,99,1,1,0)
8925.1^AM^MUMPS
"^DD",8925.1,8925.1,99,1,1,1)
D SET^TIUDD
"^DD",8925.1,8925.1,99,1,1,2)
D KILL^TIUDD
"^DD",8925.1,8925.1,99,1,1,"%D",0)
^^2^2^2950911^^^
"^DD",8925.1,8925.1,99,1,1,"%D",1,0)
This cross-reference invokes menu compilation in ^XUTL("XQORM",
"^DD",8925.1,8925.1,99,1,1,"%D",2,0)
DA;TIU(8925.1, when the TIMESTAMP field is modified.
"^DD",8925.1,8925.1,99,1,1,"DT")
2940720
"^DD",8925.1,8925.1,99,3)
Answer must be 1-15 characters in length.
"^DD",8925.1,8925.1,99,"DT")
2940720
"^DD",8925.1,8925.1,1501,0)
VHA ENTERPRISE STANDARD TITLE^*P8926.1'^TIU(8926.1,^15;1^S DIC("S")="I '$$SCREEN^XTID(8926.1,"""",Y_"","")" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
"^DD",8925.1,8925.1,1501,1,0)
^.1
"^DD",8925.1,8925.1,1501,1,1,0)
8925.1^ALOINC
"^DD",8925.1,8925.1,1501,1,1,1)
S ^TIU(8925.1,"ALOINC",$E(X,1,30),DA)=""
"^DD",8925.1,8925.1,1501,1,1,2)
K ^TIU(8925.1,"ALOINC",$E(X,1,30),DA)
"^DD",8925.1,8925.1,1501,1,1,3)
** DO NOT DELETE **
"^DD",8925.1,8925.1,1501,1,1,"%D",0)
^^2^2^3070306^
"^DD",8925.1,8925.1,1501,1,1,"%D",1,0)
This REGULAR FileMan cross-reference will facilitate searching by VHA
"^DD",8925.1,8925.1,1501,1,1,"%D",2,0)
Enterprise Standard Titles.
"^DD",8925.1,8925.1,1501,1,1,"DT")
3070306
"^DD",8925.1,8925.1,1501,3)
Please identify the VHA Enterprise Title to which this local title should be mapped.
"^DD",8925.1,8925.1,1501,12)
Only ACTIVE Enterprise Titles may be selected.
"^DD",8925.1,8925.1,1501,12.1)
S DIC("S")="I '$$SCREEN^XTID(8926.1,"""",Y_"","")"
"^DD",8925.1,8925.1,1501,21,0)
^.001^2^2^3070321^^
"^DD",8925.1,8925.1,1501,21,1,0)
This reference to the VHA ENTERPRISE STANDARD TITLE FILE provides for the
"^DD",8925.1,8925.1,1501,21,2,0)
mapping of local titles to the Enterprise Standard Titles.
"^DD",8925.1,8925.1,1501,"DT")
3070321
"^DD",8925.1,8925.1,1502,0)
MAP ATTEMPTED^D^^15;2^S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
"^DD",8925.1,8925.1,1502,3)
Enter the date/time at which mapping was attempted.
"^DD",8925.1,8925.1,1502,21,0)
^^2^2^3060301^
"^DD",8925.1,8925.1,1502,21,1,0)
This is the date/time at which the user attempted to map the Local Title 
"^DD",8925.1,8925.1,1502,21,2,0)
to a VHA Enterprise Title.
"^DD",8925.1,8925.1,1502,"DT")
3060301
"^DD",8925.1,8925.1,1503,0)
MAP ATTEMPTED BY^P200'^VA(200,^15;3^Q
"^DD",8925.1,8925.1,1503,3)
Specify the person who attempted to map the title.
"^DD",8925.1,8925.1,1503,21,0)
^^2^2^3060301^
"^DD",8925.1,8925.1,1503,21,1,0)
This is the person who attempted to map the Local Title to a VHA 
"^DD",8925.1,8925.1,1503,21,2,0)
Enterprise Title.
"^DD",8925.1,8925.1,1503,"DT")
3060301
"^DD",8925.1,8925.11,0)
UPLOAD DELIMITED ASCII HEADER SUB-FIELD^^1^8
"^DD",8925.1,8925.11,0,"DT")
2951004
"^DD",8925.1,8925.11,0,"ID",.02)
W "   ",$P(^(0),U,2)
"^DD",8925.1,8925.11,0,"IX","B",8925.11,.01)

"^DD",8925.1,8925.11,0,"IX","C",8925.11,.02)

"^DD",8925.1,8925.11,0,"IX","D",8925.11,.03)

"^DD",8925.1,8925.11,0,"IX","E",8925.11,.04)

"^DD",8925.1,8925.11,0,"NM","UPLOAD DELIMITED ASCII HEADER")

"^DD",8925.1,8925.11,0,"UP")
8925.1
"^DD",8925.1,8925.11,.01,0)
HEADER PIECE^MNJ2,0X^^0;1^K:+X'=X!(X>30)!(X<1)!(X?.E1"."1N.N) X S:$D(X) DINUM=X
"^DD",8925.1,8925.11,.01,1,0)
^.1
"^DD",8925.1,8925.11,.01,1,1,0)
8925.11^B
"^DD",8925.1,8925.11,.01,1,1,1)
S ^TIU(8925.1,DA(1),"ITEM","B",$E(X,1,30),DA)=""
"^DD",8925.1,8925.11,.01,1,1,2)
K ^TIU(8925.1,DA(1),"ITEM","B",$E(X,1,30),DA)
"^DD",8925.1,8925.11,.01,3)
Enter the delimiter-piece for the next header item.
"^DD",8925.1,8925.11,.01,21,0)
^^2^2^2970107^
"^DD",8925.1,8925.11,.01,21,1,0)
This is the number for this piece (item) of the header.  Start with
"^DD",8925.1,8925.11,.01,21,2,0)
number 1 for the first piece.
"^DD",8925.1,8925.11,.01,"DT")
2921021
"^DD",8925.1,8925.11,.02,0)
ITEM NAME^F^^0;2^K:$L(X)>30!($L(X)<2) X
"^DD",8925.1,8925.11,.02,1,0)
^.1
"^DD",8925.1,8925.11,.02,1,1,0)
8925.11^C
"^DD",8925.1,8925.11,.02,1,1,1)
S ^TIU(8925.1,DA(1),"ITEM","C",$E(X,1,30),DA)=""
"^DD",8925.1,8925.11,.02,1,1,2)
K ^TIU(8925.1,DA(1),"ITEM","C",$E(X,1,30),DA)
"^DD",8925.1,8925.11,.02,1,1,"%D",0)
^^2^2^2921021^
"^DD",8925.1,8925.11,.02,1,1,"%D",1,0)
This REGULAR FileMan cross-reference on the ITEM NAME is used in the
"^DD",8925.1,8925.11,.02,1,1,"%D",2,0)
look-up and edit process.
"^DD",8925.1,8925.11,.02,1,1,"DT")
2920605
"^DD",8925.1,8925.11,.02,3)
Enter the name of the header item.
"^DD",8925.1,8925.11,.02,21,0)
^^2^2^2970107^
"^DD",8925.1,8925.11,.02,21,1,0)
This is the name of the item in the ASCII message header.  Item Name is
"^DD",8925.1,8925.11,.02,21,2,0)
used in help messages for the person dictating a document.
"^DD",8925.1,8925.11,.02,"DT")
2921021
"^DD",8925.1,8925.11,.03,0)
FIELD NUMBER^F^^0;3^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>10!($L(X)<1) X
"^DD",8925.1,8925.11,.03,1,0)
^.1
"^DD",8925.1,8925.11,.03,1,1,0)
8925.11^D
"^DD",8925.1,8925.11,.03,1,1,1)
S ^TIU(8925.1,DA(1),"ITEM","D",$E(X,1,30),DA)=""
"^DD",8925.1,8925.11,.03,1,1,2)
K ^TIU(8925.1,DA(1),"ITEM","D",$E(X,1,30),DA)
"^DD",8925.1,8925.11,.03,1,1,"%D",0)
^^3^3^2921021^
"^DD",8925.1,8925.11,.03,1,1,"%D",1,0)
This REGULAR FileMan cross-reference by field number is used by the
"^DD",8925.1,8925.11,.03,1,1,"%D",2,0)
filer/router to identify header-pieces with field numbers in the target
"^DD",8925.1,8925.11,.03,1,1,"%D",3,0)
file.
"^DD",8925.1,8925.11,.03,1,1,"DT")
2921021
"^DD",8925.1,8925.11,.03,3)
Enter the FIELD # of the item in the target file.
"^DD",8925.1,8925.11,.03,21,0)
^^2^2^2970107^
"^DD",8925.1,8925.11,.03,21,1,0)
This is the field number in the target file which corresponds to this
"^DD",8925.1,8925.11,.03,21,2,0)
header item.
"^DD",8925.1,8925.11,.03,"DT")
2921021
"^DD",8925.1,8925.11,.04,0)
LOOKUP LOCAL VARIABLE NAME^F^^0;4^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>8!($L(X)<1)!'(X?1A1.7E) X
"^DD",8925.1,8925.11,.04,1,0)
^.1
"^DD",8925.1,8925.11,.04,1,1,0)
8925.11^E
"^DD",8925.1,8925.11,.04,1,1,1)
S ^TIU(8925.1,DA(1),"ITEM","E",$E(X,1,30),DA)=""
"^DD",8925.1,8925.11,.04,1,1,2)
K ^TIU(8925.1,DA(1),"ITEM","E",$E(X,1,30),DA)
"^DD",8925.1,8925.11,.04,1,1,"%D",0)
^^3^3^2921109^
"^DD",8925.1,8925.11,.04,1,1,"%D",1,0)
This cross-reference is used by the router/filer to determine which pieces
"^DD",8925.1,8925.11,.04,1,1,"%D",2,0)
of the header should be set into special variables which may be required by
"^DD",8925.1,8925.11,.04,1,1,"%D",3,0)
the lookup routine.
"^DD",8925.1,8925.11,.04,1,1,"DT")
2921109
"^DD",8925.1,8925.11,.04,3)
Enter the required local variable into which this piece will be set.
"^DD",8925.1,8925.11,.04,21,0)
^^11^11^2970107^
"^DD",8925.1,8925.11,.04,21,1,0)
This field specifies the local variable name into which this piece of the
"^DD",8925.1,8925.11,.04,21,2,0)
message header will be set.  The local variable is used by the Look-Up
"^DD",8925.1,8925.11,.04,21,3,0)
Method.  For example, if this piece of the header is the patient social
"^DD",8925.1,8925.11,.04,21,4,0)
security number, the Lookup Local Variable Name might be TIUSSN.  The
"^DD",8925.1,8925.11,.04,21,5,0)
social security number as written by the transcriptionist is first
"^DD",8925.1,8925.11,.04,21,6,0)
transformed by any existing Transform Code, and then set into this
"^DD",8925.1,8925.11,.04,21,7,0)
variable (e.g. TIUSSN) for use in Look-Up Method code.
"^DD",8925.1,8925.11,.04,21,8,0)
 
"^DD",8925.1,8925.11,.04,21,9,0)
Lookup Local Variable Name is necessary only if the information in this
"^DD",8925.1,8925.11,.04,21,10,0)
piece is required in order to look up the appropriate entry in the target
"^DD",8925.1,8925.11,.04,21,11,0)
file.
"^DD",8925.1,8925.11,.04,"DT")
2921109
"^DD",8925.1,8925.11,.05,0)
EXAMPLE ENTRY^F^^0;5^K:$L(X)>39!($L(X)<2) X
"^DD",8925.1,8925.11,.05,3)
Answer must be 2-39 characters in length.
"^DD",8925.1,8925.11,.05,21,0)
^^10^10^2970108^^
"^DD",8925.1,8925.11,.05,21,1,0)
This field is used to store sample data for this item in the form the
"^DD",8925.1,8925.11,.05,21,2,0)
transcriptionist is expected to use when transcribing it. For example, if
"^DD",8925.1,8925.11,.05,21,3,0)
a patient has Social Security Number 555-12-1212, and the transcriptionist
"^DD",8925.1,8925.11,.05,21,4,0)
is expected to write 555-12-1212, then an Example Entry should have the
"^DD",8925.1,8925.11,.05,21,5,0)
form 555-12-1212.
"^DD",8925.1,8925.11,.05,21,6,0)
 
"^DD",8925.1,8925.11,.05,21,7,0)
The Transform Code, if it exists, then transforms the transcribed Social
"^DD",8925.1,8925.11,.05,21,8,0)
Security Number 555-12-1212 into the appropriate format for the target
"^DD",8925.1,8925.11,.05,21,9,0)
file before using the Social Security Number to look-up the appropriate
"^DD",8925.1,8925.11,.05,21,10,0)
target file entry and/or before entering it in the target file.
"^DD",8925.1,8925.11,.05,"DT")
2930224
"^DD",8925.1,8925.11,.06,0)
CLINICIAN MUST DICTATE^S^1:YES;0:NO;^0;6^Q
"^DD",8925.1,8925.11,.06,3)
Answer yes if this field needs to be dictated by the clinician
"^DD",8925.1,8925.11,.06,21,0)
^^5^5^2970108^
"^DD",8925.1,8925.11,.06,21,1,0)
States whether or not this piece of the header should be dictated by the
"^DD",8925.1,8925.11,.06,21,2,0)
Clinician.  Will be used by the Clinician Help routine to determine if
"^DD",8925.1,8925.11,.06,21,3,0)
this field should be shown as data that should be dictated.  (Some pieces
"^DD",8925.1,8925.11,.06,21,4,0)
can be entered by the transcriber without being dictated, such as the
"^DD",8925.1,8925.11,.06,21,5,0)
transcriber identification).
"^DD",8925.1,8925.11,.06,"DT")
2930423
"^DD",8925.1,8925.11,.07,0)
REQUIRED FIELD?^S^1:YES;0:NO;^0;7^Q
"^DD",8925.1,8925.11,.07,3)
Please indicate whether the field is required.
"^DD",8925.1,8925.11,.07,21,0)
^^5^5^2970108^
"^DD",8925.1,8925.11,.07,21,1,0)
This field is used to determine whether a given header piece is required
"^DD",8925.1,8925.11,.07,21,2,0)
by the application (e.g., Author and Attending Physician may be required
"^DD",8925.1,8925.11,.07,21,3,0)
for the ongoing processing of a Discharge Summary).  Records lacking
"^DD",8925.1,8925.11,.07,21,4,0)
required fields WILL be entered if possible into the target file but will
"^DD",8925.1,8925.11,.07,21,5,0)
generate Missing Field Error Alerts.
"^DD",8925.1,8925.11,.07,"DT")
2951004
"^DD",8925.1,8925.11,1,0)
TRANSFORM CODE^K^^1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.11,1,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.11,1,9)
@
"^DD",8925.1,8925.11,1,21,0)
^^11^11^2970108^
"^DD",8925.1,8925.11,1,21,1,0)
This standard MUMPS code transforms the transcribed value of the header
"^DD",8925.1,8925.11,1,21,2,0)
piece into a format acceptable to FileMan (e.g., patient social security
"^DD",8925.1,8925.11,1,21,3,0)
number 555-12-1212 must be transformed to 555121212 or to whatever
"^DD",8925.1,8925.11,1,21,4,0)
(external) format FileMan accepts when a user edits the social security
"^DD",8925.1,8925.11,1,21,5,0)
number field in the target file).
"^DD",8925.1,8925.11,1,21,6,0)
 
"^DD",8925.1,8925.11,1,21,7,0)
Field values are transformed before being set into Special Lookup
"^DD",8925.1,8925.11,1,21,8,0)
Variables and before being set into Target Text File Fields.
"^DD",8925.1,8925.11,1,21,9,0)
 
"^DD",8925.1,8925.11,1,21,10,0)
Field is necessary only if transcribed piece is not in the format Fileman
"^DD",8925.1,8925.11,1,21,11,0)
accepts for the target file.
"^DD",8925.1,8925.11,1,"DT")
2930219
"^DD",8925.1,8925.111,0)
STAT AUTO PRINT EVENT SUB-FIELD^^.01^1
"^DD",8925.1,8925.111,0,"DT")
2940621
"^DD",8925.1,8925.111,0,"IX","B",8925.111,.01)

"^DD",8925.1,8925.111,0,"NM","STAT AUTO PRINT EVENT")

"^DD",8925.1,8925.111,0,"UP")
8925.1
"^DD",8925.1,8925.111,.01,0)
STAT AUTO PRINT EVENT^MS^N:NONE;T:TRANSCRIBED;R:RELEASED;V:VERIFIED;S:SIGNED;CSR:COSIGNED, REQUIRED;CSOINC:COSIGNED, OPTIONAL, INCOMPLETE;CSOCP:COSIGNED, OPTIONAL, COMPLETED;CP:COMLETED;AD:ADDENDUM ADDED;AM:AMENDED;^0;1^Q
"^DD",8925.1,8925.111,.01,1,0)
^.1
"^DD",8925.1,8925.111,.01,1,1,0)
8925.111^B
"^DD",8925.1,8925.111,.01,1,1,1)
S ^TIU(8925.1,DA(1),11,"B",$E(X,1,30),DA)=""
"^DD",8925.1,8925.111,.01,1,1,2)
K ^TIU(8925.1,DA(1),11,"B",$E(X,1,30),DA)
"^DD",8925.1,8925.111,.01,3)
Enter every event which should trigger auto printing of document whenever the event occurs.
"^DD",8925.1,8925.111,.01,"DT")
2941027
"^DD",8925.1,8925.112,0)
ROUTINE AUTO PRINT EVENT SUB-FIELD^^.01^1
"^DD",8925.1,8925.112,0,"DT")
2940621
"^DD",8925.1,8925.112,0,"IX","B",8925.112,.01)

"^DD",8925.1,8925.112,0,"NM","ROUTINE AUTO PRINT EVENT")

"^DD",8925.1,8925.112,0,"UP")
8925.1
"^DD",8925.1,8925.112,.01,0)
ROUTINE AUTO PRINT EVENT^MS^N:NONE;T:TRANSCRIBED;R:RELEASED;V:VERIFIED;S:SIGNED;CSR:COSIGNED, REQUIRED;CSOINC:COSIGNED, OPTIONAL, INCOMPLETE;CP:COMPLETED;CSOCP:CONSIGNED, OPTIONAL, COMPLETED;AD:ADDENDUM ADDED;AM:AMENDED;^0;1^Q
"^DD",8925.1,8925.112,.01,1,0)
^.1
"^DD",8925.1,8925.112,.01,1,1,0)
8925.112^B
"^DD",8925.1,8925.112,.01,1,1,1)
S ^TIU(8925.1,DA(1),12,"B",$E(X,1,30),DA)=""
"^DD",8925.1,8925.112,.01,1,1,2)
K ^TIU(8925.1,DA(1),12,"B",$E(X,1,30),DA)
"^DD",8925.1,8925.112,.01,3)
Enter an event which should trigger auto printing of routine documents.
"^DD",8925.1,8925.112,.01,"DT")
2940621
"^DD",8925.1,8925.113,0)
PROCESSING STEPS SUB-FIELD^^.05^5
"^DD",8925.1,8925.113,0,"DT")
2950216
"^DD",8925.1,8925.113,0,"IX","B",8925.113,.01)

"^DD",8925.1,8925.113,0,"NM","PROCESSING STEPS")

"^DD",8925.1,8925.113,0,"UP")
8925.1
"^DD",8925.1,8925.113,.01,0)
PROCESSING STEP^MP8930.8'^USR(8930.8,^0;1^Q
"^DD",8925.1,8925.113,.01,1,0)
^.1
"^DD",8925.1,8925.113,.01,1,1,0)
8925.113^B
"^DD",8925.1,8925.113,.01,1,1,1)
S ^TIU(8925.1,DA(1),13,"B",$E(X,1,30),DA)=""
"^DD",8925.1,8925.113,.01,1,1,2)
K ^TIU(8925.1,DA(1),13,"B",$E(X,1,30),DA)
"^DD",8925.1,8925.113,.01,3)
Please indicate a step involved in processing this document.
"^DD",8925.1,8925.113,.01,21,0)
^^2^2^2950216^
"^DD",8925.1,8925.113,.01,21,1,0)
This is a step or action (e.g., verification) in the processing of a document
"^DD",8925.1,8925.113,.01,21,2,0)
that moves it from one state (e.g., unverified) to another (e.g., unsigned).
"^DD",8925.1,8925.113,.01,"DT")
2950216
"^DD",8925.1,8925.113,.02,0)
SEQUENCE^NJ3,0^^0;2^K:+X'=X!(X>999)!(X<0)!(X?.E1"."1N.N) X
"^DD",8925.1,8925.113,.02,3)
Indicate the order in processing this document where this step should occur.
"^DD",8925.1,8925.113,.02,21,0)
^^4^4^2950216^
"^DD",8925.1,8925.113,.02,21,1,0)
This is the serial sequence in the processing of the document in which the 
"^DD",8925.1,8925.113,.02,21,2,0)
current step should ordinarily occur.  This field is only necessary when the
"^DD",8925.1,8925.113,.02,21,3,0)
process in question must occur in a particular sequence (e.g., to insure
"^DD",8925.1,8925.113,.02,21,4,0)
that a document is always released from draft before it is verified).
"^DD",8925.1,8925.113,.02,"DT")
2950216
"^DD",8925.1,8925.113,.03,0)
REQUIRED?^S^1:REQUIRED;0:OPTIONAL;^0;3^Q
"^DD",8925.1,8925.113,.03,3)
Indicate whether the step is required or optional
"^DD",8925.1,8925.113,.03,21,0)
^^4^4^2950216^
"^DD",8925.1,8925.113,.03,21,1,0)
This field specifies whether the step is required or optional for completion
"^DD",8925.1,8925.113,.03,21,2,0)
of the document (e.g., Dictation and transcription is the typical means by
"^DD",8925.1,8925.113,.03,21,3,0)
which Discharge Summaries are acquired, but they may be entered directly by
"^DD",8925.1,8925.113,.03,21,4,0)
the provider, if preferred).
"^DD",8925.1,8925.113,.03,"DT")
2950216
"^DD",8925.1,8925.113,.04,0)
RESULTING STATUS^P8930.6'^USR(8930.6,^0;4^Q
"^DD",8925.1,8925.113,.04,3)
Indicate the status resulting from the step being taken.
"^DD",8925.1,8925.113,.04,21,0)
^^4^4^2950216^
"^DD",8925.1,8925.113,.04,21,1,0)
This is the status of the document following completion of the step in 
"^DD",8925.1,8925.113,.04,21,2,0)
question.  For instance, if a discharge summary is to be registered as
"^DD",8925.1,8925.113,.04,21,3,0)
unsigned following verification, this would be indicated in the RESULTING 
"^DD",8925.1,8925.113,.04,21,4,0)
STATUS field.
"^DD",8925.1,8925.113,.04,"DT")
2950216
"^DD",8925.1,8925.113,.05,0)
CONDITION TEXT^F^^0;5^K:$L(X)>40!($L(X)<3) X
"^DD",8925.1,8925.113,.05,3)
Condition under which the step will result in the status as indicated.
"^DD",8925.1,8925.113,.05,"DT")
2950216
"^DD",8925.1,8925.114,0)
DIALOG SUB-FIELD^^117^12
"^DD",8925.1,8925.114,0,"DT")
2951002
"^DD",8925.1,8925.114,0,"IX","AS",8925.114,.03)

"^DD",8925.1,8925.114,0,"IX","B",8925.114,.01)

"^DD",8925.1,8925.114,0,"NM","DIALOG")

"^DD",8925.1,8925.114,0,"UP")
8925.1
"^DD",8925.1,8925.114,.01,0)
PROMPT^MF^^0;1^K:$L(X)>30!($L(X)<2) X
"^DD",8925.1,8925.114,.01,1,0)
^.1
"^DD",8925.1,8925.114,.01,1,1,0)
8925.114^B
"^DD",8925.1,8925.114,.01,1,1,1)
S ^TIU(8925.1,DA(1),"DIALOG","B",$E(X,1,30),DA)=""
"^DD",8925.1,8925.114,.01,1,1,2)
K ^TIU(8925.1,DA(1),"DIALOG","B",$E(X,1,30),DA)
"^DD",8925.1,8925.114,.01,3)
Enter the caption with which the user will be prompted.
"^DD",8925.1,8925.114,.01,21,0)
^^2^2^2950606^^^
"^DD",8925.1,8925.114,.01,21,1,0)
This is the prompt with which the user will be presented during interactive 
"^DD",8925.1,8925.114,.01,21,2,0)
entry of the document.
"^DD",8925.1,8925.114,.01,"DT")
2950606
"^DD",8925.1,8925.114,.02,0)
ITEM NAME^F^^0;2^K:$L(X)>50!($L(X)<2) X
"^DD",8925.1,8925.114,.02,3)
Answer must be 2-50 characters in length.
"^DD",8925.1,8925.114,.02,21,0)
^^2^2^2950606^^
"^DD",8925.1,8925.114,.02,21,1,0)
This is a descriptive name for the datum which will help descibe the prompt 
"^DD",8925.1,8925.114,.02,21,2,0)
for the user.
"^DD",8925.1,8925.114,.02,"DT")
2950606
"^DD",8925.1,8925.114,.03,0)
SEQUENCE^NJ3,0^^0;3^K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X
"^DD",8925.1,8925.114,.03,1,0)
^.1
"^DD",8925.1,8925.114,.03,1,1,0)
8925.114^AS
"^DD",8925.1,8925.114,.03,1,1,1)
S ^TIU(8925.1,DA(1),"DIALOG","AS",$E(X,1,30),DA)=""
"^DD",8925.1,8925.114,.03,1,1,2)
K ^TIU(8925.1,DA(1),"DIALOG","AS",$E(X,1,30),DA)
"^DD",8925.1,8925.114,.03,1,1,"%D",0)
^^2^2^2950606^
"^DD",8925.1,8925.114,.03,1,1,"%D",1,0)
This REGULAR FileMan Cross-reference on the sequence sub-field of the
"^DD",8925.1,8925.114,.03,1,1,"%D",2,0)
Dialog Multiple will facilitate appropriate serialization of prompts.
"^DD",8925.1,8925.114,.03,1,1,"DT")
2950606
"^DD",8925.1,8925.114,.03,3)
Type a Number between 1 and 999, 0 Decimal Digits
"^DD",8925.1,8925.114,.03,21,0)
^^2^2^2950606^
"^DD",8925.1,8925.114,.03,21,1,0)
This is the sequence of the prompt within the dialog.  On the Windows Client 
"^DD",8925.1,8925.114,.03,21,2,0)
this will correspond with the Tab Order Property of the prompt.
"^DD",8925.1,8925.114,.03,"DT")
2950606
"^DD",8925.1,8925.114,.04,0)
FIELD^FX^^0;4^K:$L(X)>10!($L(X)<1)!(+X<0) X
"^DD",8925.1,8925.114,.04,3)
Enter the field in the TARGET FILE in which the response is to be stored.
"^DD",8925.1,8925.114,.04,4)

"^DD",8925.1,8925.114,.04,21,0)
^^2^2^2970116^^
"^DD",8925.1,8925.114,.04,21,1,0)
This is the field in the target file in which the user's response will be 
"^DD",8925.1,8925.114,.04,21,2,0)
stored.
"^DD",8925.1,8925.114,.04,"DT")
2970116
"^DD",8925.1,8925.114,.05,0)
REQUIRED^S^1:YES;0:NO;^0;5^Q
"^DD",8925.1,8925.114,.05,3)
Indicate whether a response is required.
"^DD",8925.1,8925.114,.05,21,0)
^^2^2^2950607^
"^DD",8925.1,8925.114,.05,21,1,0)
Please indicate whether a response to this prompt is required, in order to 
"^DD",8925.1,8925.114,.05,21,2,0)
complete the dialog.
"^DD",8925.1,8925.114,.05,"DT")
2950607
"^DD",8925.1,8925.114,.06,0)
VISIBLE^S^0:NO;1:YES;^0;6^Q
"^DD",8925.1,8925.114,.06,3)
Indicate wheter the prompt will be visible to the user.
"^DD",8925.1,8925.114,.06,21,0)
^^2^2^2950607^
"^DD",8925.1,8925.114,.06,21,1,0)
This field specifies whether a given datum will be prompted for, or 
"^DD",8925.1,8925.114,.06,21,2,0)
"stuffed," based on execution of the SET METHOD for a given prompt.
"^DD",8925.1,8925.114,.06,"DT")
2950607
"^DD",8925.1,8925.114,1,0)
SET METHOD^K^^1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.114,1,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.114,1,9)
@
"^DD",8925.1,8925.114,1,21,0)
^^5^5^2950607^^^
"^DD",8925.1,8925.114,1,21,1,0)
This is the mumps code for determining the default value of an interactive
"^DD",8925.1,8925.114,1,21,2,0)
("visible") prompt, and for setting the value to be non-interactively 
"^DD",8925.1,8925.114,1,21,3,0)
"stuffed" on invokation of an "invisible" prompt.  Regardless of the 
"^DD",8925.1,8925.114,1,21,4,0)
syntactic approach (e.g., subroutine or extrinsic function, the return
"^DD",8925.1,8925.114,1,21,5,0)
value of the method should be placed in the local varible X.
"^DD",8925.1,8925.114,1,"DT")
2950607
"^DD",8925.1,8925.114,101,0)
WINDOWS CONTROL^S^1:LongList;2:SimpleList;3:Edit;4:Memo;^W;1^Q
"^DD",8925.1,8925.114,101,3)
Enter the Windows control appropriate for this prompt
"^DD",8925.1,8925.114,101,21,0)
^^2^2^2950907^
"^DD",8925.1,8925.114,101,21,1,0)
Stores the type of Windows control necessary to get the data for this
"^DD",8925.1,8925.114,101,21,2,0)
prompt.
"^DD",8925.1,8925.114,101,"DT")
2950907
"^DD",8925.1,8925.114,102,0)
API NAME^F^^W;2^K:$L(X)>30!($L(X)<3) X
"^DD",8925.1,8925.114,102,3)
Answer must be 3-30 characters in length.
"^DD",8925.1,8925.114,102,21,0)
^^3^3^2950907^
"^DD",8925.1,8925.114,102,21,1,0)
This is the API that should be called by the broker when the control is
"^DD",8925.1,8925.114,102,21,2,0)
used.  How the API is used varies with the control.  Examples are:
"^DD",8925.1,8925.114,102,21,3,0)
filling list boxes, getting boilerplate text, etc.
"^DD",8925.1,8925.114,102,"DT")
2951002
"^DD",8925.1,8925.114,103,0)
API PARAMETER #1^F^^W;3^K:$L(X)>30!($L(X)<1) X
"^DD",8925.1,8925.114,103,3)
Answer must be 1-30 characters in length.
"^DD",8925.1,8925.114,103,21,0)
^^1^1^2950907^
"^DD",8925.1,8925.114,103,21,1,0)
A parameter that is used by the API may be stored here.
"^DD",8925.1,8925.114,103,"DT")
2950907
"^DD",8925.1,8925.114,113,0)
WINDOWS CONDITION^K^^W3;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.114,113,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.114,113,9)
@
"^DD",8925.1,8925.114,113,21,0)
^^3^3^2950907^
"^DD",8925.1,8925.114,113,21,1,0)
This is silent code which is executed when building the dialog for
"^DD",8925.1,8925.114,113,21,2,0)
Windows.  It identifies which prompts should be included in the dialog.
"^DD",8925.1,8925.114,113,21,3,0)
The condition should leave $T failse if the prompt should not be asked.
"^DD",8925.1,8925.114,113,"DT")
2950907
"^DD",8925.1,8925.114,117,0)
WINDOWS DEFAULT^K^^W7;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.114,117,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.114,117,9)
@
"^DD",8925.1,8925.114,117,21,0)
^^2^2^2950907^
"^DD",8925.1,8925.114,117,21,1,0)
This code should silently set the default value of a prompt when it is
"^DD",8925.1,8925.114,117,21,2,0)
selected.
"^DD",8925.1,8925.114,117,"DT")
2950907
"^DD",8925.1,8925.12,0)
UPLOAD CAPTIONED ASCII HEADER SUB-FIELD^^1^8
"^DD",8925.1,8925.12,0,"DT")
2951004
"^DD",8925.1,8925.12,0,"IX","B",8925.12,.01)

"^DD",8925.1,8925.12,0,"IX","C",8925.12,.02)

"^DD",8925.1,8925.12,0,"IX","D",8925.12,.03)

"^DD",8925.1,8925.12,0,"IX","E",8925.12,.04)

"^DD",8925.1,8925.12,0,"NM","UPLOAD CAPTIONED ASCII HEADER")

"^DD",8925.1,8925.12,0,"UP")
8925.1
"^DD",8925.1,8925.12,.01,0)
CAPTION^MF^^0;1^K:$L(X)>40!($L(X)<2) X
"^DD",8925.1,8925.12,.01,1,0)
^.1
"^DD",8925.1,8925.12,.01,1,1,0)
8925.12^B
"^DD",8925.1,8925.12,.01,1,1,1)
S ^TIU(8925.1,DA(1),"HEAD","B",$E(X,1,30),DA)=""
"^DD",8925.1,8925.12,.01,1,1,2)
K ^TIU(8925.1,DA(1),"HEAD","B",$E(X,1,30),DA)
"^DD",8925.1,8925.12,.01,3)
Answer must be 2-40 characters in length.
"^DD",8925.1,8925.12,.01,21,0)
^^7^7^2970108^
"^DD",8925.1,8925.12,.01,21,1,0)
NOTE: Users can choose between two possible kinds of Upload Record
"^DD",8925.1,8925.12,.01,21,2,0)
Headers: Captioned or Delimited.  Captioned headers should be used UNLESS
"^DD",8925.1,8925.12,.01,21,3,0)
the site has a way to generate upload headers automatically.
"^DD",8925.1,8925.12,.01,21,4,0)
 
"^DD",8925.1,8925.12,.01,21,5,0)
CAPTION is the caption which the transcriber enters into the captioned
"^DD",8925.1,8925.12,.01,21,6,0)
upload record header immediately preceeding the item data.  It serves to
"^DD",8925.1,8925.12,.01,21,7,0)
distinguish one item of data from the next. Example: PATIENT NAME
"^DD",8925.1,8925.12,.01,"DT")
2930218
"^DD",8925.1,8925.12,.02,0)
ITEM NAME^F^^0;2^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>20!($L(X)<2) X
"^DD",8925.1,8925.12,.02,1,0)
^.1
"^DD",8925.1,8925.12,.02,1,1,0)
8925.12^C
"^DD",8925.1,8925.12,.02,1,1,1)
S ^TIU(8925.1,DA(1),"HEAD","C",$E(X,1,30),DA)=""
"^DD",8925.1,8925.12,.02,1,1,2)
K ^TIU(8925.1,DA(1),"HEAD","C",$E(X,1,30),DA)
"^DD",8925.1,8925.12,.02,1,1,"%D",0)
^^2^2^2930122^
"^DD",8925.1,8925.12,.02,1,1,"%D",1,0)
This REGULAR FileMan cross-reference on the ITEM NAME is used in the look-up
"^DD",8925.1,8925.12,.02,1,1,"%D",2,0)
and filing processes.
"^DD",8925.1,8925.12,.02,1,1,"DT")
2930122
"^DD",8925.1,8925.12,.02,3)
Enter the name of the header item.
"^DD",8925.1,8925.12,.02,21,0)
^^2^2^2970108^
"^DD",8925.1,8925.12,.02,21,1,0)
This is the name of the item in the ASCII message header.  Item Name is
"^DD",8925.1,8925.12,.02,21,2,0)
used in help messages for the person dictating a document.
"^DD",8925.1,8925.12,.02,"DT")
2930122
"^DD",8925.1,8925.12,.03,0)
FIELD NUMBER^F^^0;3^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>10!($L(X)<1) X
"^DD",8925.1,8925.12,.03,1,0)
^.1
"^DD",8925.1,8925.12,.03,1,1,0)
8925.12^D
"^DD",8925.1,8925.12,.03,1,1,1)
S ^TIU(8925.1,DA(1),"HEAD","D",$E(X,1,30),DA)=""
"^DD",8925.1,8925.12,.03,1,1,2)
K ^TIU(8925.1,DA(1),"HEAD","D",$E(X,1,30),DA)
"^DD",8925.1,8925.12,.03,1,1,"%D",0)
^^2^2^2930122^
"^DD",8925.1,8925.12,.03,1,1,"%D",1,0)
This REGULAR FileMan cross-reference is used by the filer router to identify
"^DD",8925.1,8925.12,.03,1,1,"%D",2,0)
header fields with field numbers in the target file.
"^DD",8925.1,8925.12,.03,1,1,"DT")
2930122
"^DD",8925.1,8925.12,.03,3)
Enter the FIELD # of the item in the target file.
"^DD",8925.1,8925.12,.03,21,0)
^^2^2^2970108^
"^DD",8925.1,8925.12,.03,21,1,0)
This is the FIELD # in the target file which corresponds to this header
"^DD",8925.1,8925.12,.03,21,2,0)
item and where this item of data will be stored.
"^DD",8925.1,8925.12,.03,"DT")
2930122
"^DD",8925.1,8925.12,.04,0)
LOOKUP LOCAL VARIABLE NAME^F^^0;4^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>8!($L(X)<1)!'(X?1A1.7E) X
"^DD",8925.1,8925.12,.04,1,0)
^.1
"^DD",8925.1,8925.12,.04,1,1,0)
8925.12^E
"^DD",8925.1,8925.12,.04,1,1,1)
S ^TIU(8925.1,DA(1),"HEAD","E",$E(X,1,30),DA)=""
"^DD",8925.1,8925.12,.04,1,1,2)
K ^TIU(8925.1,DA(1),"HEAD","E",$E(X,1,30),DA)
"^DD",8925.1,8925.12,.04,1,1,"%D",0)
^^3^3^2930122^
"^DD",8925.1,8925.12,.04,1,1,"%D",1,0)
This REGULAR FileMan cross-reference is used by the router/filer to determine
"^DD",8925.1,8925.12,.04,1,1,"%D",2,0)
which fields of the header should be set into special variables which may be
"^DD",8925.1,8925.12,.04,1,1,"%D",3,0)
required by the lookup routine.
"^DD",8925.1,8925.12,.04,1,1,"DT")
2930122
"^DD",8925.1,8925.12,.04,3)
Enter the required local variable into which this item will be set.
"^DD",8925.1,8925.12,.04,21,0)
^^11^11^2970108^
"^DD",8925.1,8925.12,.04,21,1,0)
This field specifies the local variable name into which this item of the
"^DD",8925.1,8925.12,.04,21,2,0)
upload header will be set.  The local variable is used by the Look-Up
"^DD",8925.1,8925.12,.04,21,3,0)
Method.  For example, if this item of the header is the patient social
"^DD",8925.1,8925.12,.04,21,4,0)
security number, the Lookup Local Variable Name might be TIUSSN.  The
"^DD",8925.1,8925.12,.04,21,5,0)
social security number as written by the transcriptionist is first
"^DD",8925.1,8925.12,.04,21,6,0)
transformed by any existing Transform Code, and then set into this
"^DD",8925.1,8925.12,.04,21,7,0)
variable (e.g. TIUSSN) for use in Look-Up Method code.
"^DD",8925.1,8925.12,.04,21,8,0)
 
"^DD",8925.1,8925.12,.04,21,9,0)
Lookup Local Variable Name is necessary only if the information in this
"^DD",8925.1,8925.12,.04,21,10,0)
piece is required in order to look up the appropriate entry in the target
"^DD",8925.1,8925.12,.04,21,11,0)
file.
"^DD",8925.1,8925.12,.04,"DT")
2930122
"^DD",8925.1,8925.12,.05,0)
EXAMPLE ENTRY^F^^0;5^K:$L(X)>80!($L(X)<2) X
"^DD",8925.1,8925.12,.05,3)
Answer must be 2-80 characters in length.
"^DD",8925.1,8925.12,.05,21,0)
^^9^9^2970108^
"^DD",8925.1,8925.12,.05,21,1,0)
This field is used to store sample data for this item in the form the
"^DD",8925.1,8925.12,.05,21,2,0)
transcriptionist is expected to use when transcribing it.  For example, if
"^DD",8925.1,8925.12,.05,21,3,0)
a patient has social security number 555-12-1212, and the transcriptionist
"^DD",8925.1,8925.12,.05,21,4,0)
is expected to write 555-12-1212, than an Example Entry should have the
"^DD",8925.1,8925.12,.05,21,5,0)
form 555-12-1212.
"^DD",8925.1,8925.12,.05,21,6,0)
 
"^DD",8925.1,8925.12,.05,21,7,0)
The Upload needs to know the exact form the transcriptionist is expected
"^DD",8925.1,8925.12,.05,21,8,0)
to use in case it needs to transform it to make it acceptable to FileMan.
"^DD",8925.1,8925.12,.05,21,9,0)
In this case, the transcriptionist also needs to know the exact form.
"^DD",8925.1,8925.12,.05,"DT")
2930224
"^DD",8925.1,8925.12,.06,0)
CLINICIAN MUST DICTATE^S^1:YES;0:NO;^0;6^Q
"^DD",8925.1,8925.12,.06,3)
Answer yes if this field needs to be dictated by the clinician.
"^DD",8925.1,8925.12,.06,21,0)
^^5^5^2970108^
"^DD",8925.1,8925.12,.06,21,1,0)
States whether or not this item should be dictated by the Clinician.  Will
"^DD",8925.1,8925.12,.06,21,2,0)
be used by the Clinician Help routine to determine if this field should be
"^DD",8925.1,8925.12,.06,21,3,0)
shown as data that should be dictated.  (Some items can be entered by the
"^DD",8925.1,8925.12,.06,21,4,0)
transcriber without being dictated, such as the transcriber
"^DD",8925.1,8925.12,.06,21,5,0)
identification).
"^DD",8925.1,8925.12,.06,"DT")
2930423
"^DD",8925.1,8925.12,.07,0)
REQUIRED FIELD?^S^1:YES;0:NO;^0;7^Q
"^DD",8925.1,8925.12,.07,3)
Please indicate whether field is required by application.
"^DD",8925.1,8925.12,.07,21,0)
^^5^5^2970108^
"^DD",8925.1,8925.12,.07,21,1,0)
This field is used to determine whether a given header item is required
"^DD",8925.1,8925.12,.07,21,2,0)
by the application (e.g., Author and Attending Physician may be required
"^DD",8925.1,8925.12,.07,21,3,0)
for the ongoing processing of a Discharge Summary).  Records lacking
"^DD",8925.1,8925.12,.07,21,4,0)
required fields WILL be entered into the target file, if possible, but
"^DD",8925.1,8925.12,.07,21,5,0)
will generate Missing Field Error Alerts.
"^DD",8925.1,8925.12,.07,"DT")
2951004
"^DD",8925.1,8925.12,1,0)
TRANSFORM CODE^K^^1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
"^DD",8925.1,8925.12,1,3)
This is Standard MUMPS code.
"^DD",8925.1,8925.12,1,9)
@
"^DD",8925.1,8925.12,1,21,0)
^^11^11^2970108^
"^DD",8925.1,8925.12,1,21,1,0)
This standard MUMPS code transforms the transcribed value of the header
"^DD",8925.1,8925.12,1,21,2,0)
item into a format acceptable to FileMan (e.g., patient social security
"^DD",8925.1,8925.12,1,21,3,0)
number 555-12-1212 must be transformed to 555121212 or to whatever
"^DD",8925.1,8925.12,1,21,4,0)
(external) format FileMan accepts when a user edits the social security
"^DD",8925.1,8925.12,1,21,5,0)
number field in the target file).
"^DD",8925.1,8925.12,1,21,6,0)
 
"^DD",8925.1,8925.12,1,21,7,0)
Field values are transformed before being set into Special Lookup
"^DD",8925.1,8925.12,1,21,8,0)
Variables and before being set into target file fields.
"^DD",8925.1,8925.12,1,21,9,0)
 
"^DD",8925.1,8925.12,1,21,10,0)
Field is necessary only if transcribed item is not in the format Fileman
"^DD",8925.1,8925.12,1,21,11,0)
accepts for the target file.
"^DD",8925.1,8925.12,1,"DT")
2930219
"^DD",8925.1,8925.13,0)
BOILERPLATE TEXT SUB-FIELD^^.01^1
"^DD",8925.1,8925.13,0,"NM","BOILERPLATE TEXT")

"^DD",8925.1,8925.13,0,"UP")
8925.1
"^DD",8925.1,8925.13,.01,0)
BOILERPLATE TEXT^WL^^0;1^Q
"^DD",8925.1,8925.13,.01,3)
Enter default Report Format
"^DD",8925.1,8925.13,.01,21,0)
^^51^51^2970506^
"^DD",8925.1,8925.13,.01,21,1,0)
Applies to Titles and Components.
"^DD",8925.1,8925.13,.01,21,2,0)
 
"^DD",8925.1,8925.13,.01,21,3,0)
Site can preload the text field of a document with default text/default
"^DD",8925.1,8925.13,.01,21,4,0)
format/overprint data which is presented to the user when entering the
"^DD",8925.1,8925.13,.01,21,5,0)
document.  User can then edit and/or add to the boilerplate text.
"^DD",8925.1,8925.13,.01,21,6,0)
 
"^DD",8925.1,8925.13,.01,21,7,0)
If document is formatted into columns, users entering documents should use
"^DD",8925.1,8925.13,.01,21,8,0)
replace mode rather than insert mode (or Find/RePlace Text) to preserve
"^DD",8925.1,8925.13,.01,21,9,0)
the columns.
"^DD",8925.1,8925.13,.01,21,10,0)
 
"^DD",8925.1,8925.13,.01,21,11,0)
Boilerplate Text may be used as an alternative to components to split a
"^DD",8925.1,8925.13,.01,21,12,0)
document up into sections, but such sections are stored together and
"^DD",8925.1,8925.13,.01,21,13,0)
cannot be separately accessed the way components can.  See Type Component,
"^DD",8925.1,8925.13,.01,21,14,0)
under Basic field Type.
"^DD",8925.1,8925.13,.01,21,15,0)
 
"^DD",8925.1,8925.13,.01,21,16,0)
Titles/Components must be inactive in order to edit boilerplate text.
"^DD",8925.1,8925.13,.01,21,17,0)
 
"^DD",8925.1,8925.13,.01,21,18,0)
Boilerplate Text is the place to embed objects which go fetch data. For
"^DD",8925.1,8925.13,.01,21,19,0)
example, suppose a Title has boilerplate text:
"^DD",8925.1,8925.13,.01,21,20,0)
 
"^DD",8925.1,8925.13,.01,21,21,0)
               Patient is a healthy |PATIENT AGE| year old male...
"^DD",8925.1,8925.13,.01,21,22,0)
 
"^DD",8925.1,8925.13,.01,21,23,0)
Then a user who enters such a note for a patient known by the system to be
"^DD",8925.1,8925.13,.01,21,24,0)
56 years old would be presented with the text:
"^DD",8925.1,8925.13,.01,21,25,0)
 
"^DD",8925.1,8925.13,.01,21,26,0)
               Patient is a healthy 56 year old male...
"^DD",8925.1,8925.13,.01,21,27,0)
 
"^DD",8925.1,8925.13,.01,21,28,0)
The user can then add to the text and/or edit the text, including the age
"^DD",8925.1,8925.13,.01,21,29,0)
(56) of the patient.  From this point on, the patient age (56) is regular
"^DD",8925.1,8925.13,.01,21,30,0)
text and is not updated in this note.
"^DD",8925.1,8925.13,.01,21,31,0)
 
"^DD",8925.1,8925.13,.01,21,32,0)
If a user enters a document when an embedded object is Inactive, the
"^DD",8925.1,8925.13,.01,21,33,0)
object does not function; the user sees the object name and an error
"^DD",8925.1,8925.13,.01,21,34,0)
message.  Similarly, if an object has been misspelled in the boilerplate
"^DD",8925.1,8925.13,.01,21,35,0)
text, or deleted from the file, or if the object name in the boilerplate
"^DD",8925.1,8925.13,.01,21,36,0)
text is not unique among objects, the object does not function.
"^DD",8925.1,8925.13,.01,21,37,0)
 
"^DD",8925.1,8925.13,.01,21,38,0)
When embedding objects in boilerplate text, users should make sure the
"^DD",8925.1,8925.13,.01,21,39,0)
entire object name is on one line rather than split between two lines.
"^DD",8925.1,8925.13,.01,21,40,0)
Split names generate "NOT found" error messages.  Users must also allow
"^DD",8925.1,8925.13,.01,21,41,0)
enough white space in the boilerplate text for whatever data the object
"^DD",8925.1,8925.13,.01,21,42,0)
imports.  Users can check boilerplate text using action TRY.
"^DD",8925.1,8925.13,.01,21,43,0)
 
"^DD",8925.1,8925.13,.01,21,44,0)
Any user who can edit boilerplate text can embed any object in it.
"^DD",8925.1,8925.13,.01,21,45,0)
However, except for object owners who are testing an object, USERS SHOULD
"^DD",8925.1,8925.13,.01,21,46,0)
EMBED ONLY ACTIVE OBJECTS in boilerplate text.  An object can be embedded
"^DD",8925.1,8925.13,.01,21,47,0)
in as many different Document Definitions as desired.
"^DD",8925.1,8925.13,.01,21,48,0)
 
"^DD",8925.1,8925.13,.01,21,49,0)
A document with multiple components can have boilerplate text in the entry
"^DD",8925.1,8925.13,.01,21,50,0)
itself and/or in any component.  Boilerplate text in the entry itself
"^DD",8925.1,8925.13,.01,21,51,0)
appears first.
"^DD",8925.1,8925.13,.01,"DT")
2930305
"^DD",8925.1,8925.14,0)
ITEM SUB-FIELD^^4^4
"^DD",8925.1,8925.14,0,"DT")
2970212
"^DD",8925.1,8925.14,0,"IX","AC",8925.14,3)

"^DD",8925.1,8925.14,0,"IX","B",8925.14,.01)

"^DD",8925.1,8925.14,0,"IX","C",8925.14,4)

"^DD",8925.1,8925.14,0,"NM","ITEM")

"^DD",8925.1,8925.14,0,"UP")
8925.1
"^DD",8925.1,8925.14,.01,0)
ITEM^M*P8925.1'X^TIU(8925.1,^0;1^S DIC("S")="I $G(TIUFPRIV) X:$D(TIUFISCR) ""I Y=TIUFISCR""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
"^DD",8925.1,8925.14,.01,1,0)
^.1
"^DD",8925.1,8925.14,.01,1,1,0)
8925.14^B
"^DD",8925.1,8925.14,.01,1,1,1)
S ^TIU(8925.1,DA(1),10,"B",$E(X,1,30),DA)=""
"^DD",8925.1,8925.14,.01,1,1,2)
K ^TIU(8925.1,DA(1),10,"B",$E(X,1,30),DA)
"^DD",8925.1,8925.14,.01,1,2,0)
8925.1^AD
"^DD",8925.1,8925.14,.01,1,2,1)
S ^TIU(8925.1,"AD",$E(X,1,30),DA(1),DA)=""
"^DD",8925.1,8925.14,.01,1,2,2)
K ^TIU(8925.1,"AD",$E(X,1,30),DA(1),DA)
"^DD",8925.1,8925.14,.01,1,2,"%D",0)
^^2^2^2940719^
"^DD",8925.1,8925.14,.01,1,2,"%D",1,0)
This cross-reference facilitates traversal from child to parent, up the
"^DD",8925.1,8925.14,.01,1,2,"%D",2,0)
class hierarchy.
"^DD",8925.1,8925.14,.01,1,2,"DT")
2940719
"^DD",8925.1,8925.14,.01,1,3,0)
8925.1^AMM^MUMPS
"^DD",8925.1,8925.14,.01,1,3,1)
D REDOX^TIUDD
"^DD",8925.1,8925.14,.01,1,3,2)
D REDOX^TIUDD
"^DD",8925.1,8925.14,.01,1,3,"%D",0)
^^2^2^2940720^^
"^DD",8925.1,8925.14,.01,1,3,"%D",1,0)
This MUMPS-type cross-reference will update the timestamp on the parent
"^DD",8925.1,8925.14,.01,1,3,"%D",2,0)
document when the ITEM, MNEMONIC, or SEQUENCE changes.
"^DD",8925.1,8925.14,.01,1,3,"DT")
2940720
"^DD",8925.1,8925.14,.01,1,4,0)
8925.1^ACL1001^MUMPS
"^DD",8925.1,8925.14,.01,1,4,1)
D SACL^TIUDD1(X,10.01)
"^DD",8925.1,8925.14,.01,1,4,2)
D KACL^TIUDD1(X,10.01)
"^DD",8925.1,8925.14,.01,1,4,"%D",0)
^^2^2^2971016^
"^DD",8925.1,8925.14,.01,1,4,"%D",1,0)
This MUMPS-type cross-reference by class and name will help to identify
"^DD",8925.1,8925.14,.01,1,4,"%D",2,0)
the titles within a given class.
"^DD",8925.1,8925.14,.01,1,4,"DT")
2971016
"^DD",8925.1,8925.14,.01,3)
ITEM must be a new or pre-existing Document Definition with appropriate Type which you own, which is not already an Item elsewhere.
"^DD",8925.1,8925.14,.01,4)
D NAME^TIUFXHLX
"^DD",8925.1,8925.14,.01,12)
See Technical Description.
"^DD",8925.1,8925.14,.01,12.1)
S DIC("S")="I $G(TIUFPRIV) X:$D(TIUFISCR) ""I Y=TIUFISCR"""
"^DD",8925.1,8925.14,.01,21,0)
^.001^6^6^3050125^^^^
"^DD",8925.1,8925.14,.01,21,1,0)
Items are themselves Document Definitions.  The Type of the parent entry
"^DD",8925.1,8925.14,.01,21,2,0)
determines what Types of items it has.  A parent entry of type Class has
"^DD",8925.1,8925.14,.01,21,3,0)
items of type Class or Document Class.  A Document Class entry has items
"^DD",8925.1,8925.14,.01,21,4,0)
of type Title.  If a Title entry has more than a single section, it has
"^DD",8925.1,8925.14,.01,21,5,0)
items of type Component.  Components may also be multi-section with items
"^DD",8925.1,8925.14,.01,21,6,0)
of type Component.  Objects do not have items.
"^DD",8925.1,8925.14,.01,23,0)
^.001^8^8^3050125^^^^
"^DD",8925.1,8925.14,.01,23,1,0)
The Item subfield of Item Field 10 in File 8925.1 is screened when using
"^DD",8925.1,8925.14,.01,23,2,0)
the TIUF Document Definition Utility to add items (i.e. when variable
"^DD",8925.1,8925.14,.01,23,3,0)
TIUFISCR is defined.  
"^DD",8925.1,8925.14,.01,23,4,0)
 
"^DD",8925.1,8925.14,.01,23,5,0)
This screen is needed in ADDTEN^TIUFLF4, which noninteractively adds an
"^DD",8925.1,8925.14,.01,23,6,0)
item to the Item multiple.  The screen limits the lookup to the 8925.1 IFN
"^DD",8925.1,8925.14,.01,23,7,0)
of the item being added to the Item multiple.  Without the screen, the
"^DD",8925.1,8925.14,.01,23,8,0)
lookup fails when there are multiple 8925.1 entries of the same name.
"^DD",8925.1,8925.14,.01,"DEL",.01,0)
I 1
"^DD",8925.1,8925.14,.01,"DT")
2971016
"^DD",8925.1,8925.14,2,0)
MNEMONIC^F^^0;2^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>4!($L(X)<1) X
"^DD",8925.1,8925.14,2,1,0)
^.1
"^DD",8925.1,8925.14,2,1,1,0)
8925.1^AMM2^MUMPS
"^DD",8925.1,8925.14,2,1,1,1)
D REDOX^TIUDD
"^DD",8925.1,8925.14,2,1,1,2)
D REDOX^TIUDD
"^DD",8925.1,8925.14,2,1,1,"%D",0)
^^2^2^2961210^^^^
"^DD",8925.1,8925.14,2,1,1,"%D",1,0)
This MUMPS-type cross-reference will update the TIMESTAMP on the parent
"^DD",8925.1,8925.14,2,1,1,"%D",2,0)
document when either the ITEM, MNEMONIC, or SEQUENCE changes.
"^DD",8925.1,8925.14,2,1,1,"DT")
2940720
"^DD",8925.1,8925.14,2,3)
Mnemonic is a handle by which to select Classes/Document Classes from a menu.  Enter the Sequence number, or 1-4 letters, or nothing if you don't want mnemonics.
"^DD",8925.1,8925.14,2,21,0)
^^3^3^2970127^
"^DD",8925.1,8925.14,2,21,1,0)
Item Mnemonic is a handle by which to select Classes/Document Classes from
"^DD",8925.1,8925.14,2,21,2,0)
a menu. 1-4 characters long.  Mnemonic is usually numeric with the same
"^DD",8925.1,8925.14,2,21,3,0)
value as the Sequence.  Alpha mnemonics are permitted if preferred.
"^DD",8925.1,8925.14,2,"DT")
2940720
"^DD",8925.1,8925.14,3,0)
SEQUENCE^NJ6,2^^0;3^K:+X'=X!(X>999)!(X<.01)!(X?.E1"."3N.N) X
"^DD",8925.1,8925.14,3,1,0)
^.1
"^DD",8925.1,8925.14,3,1,1,0)
8925.1^AMM3^MUMPS
"^DD",8925.1,8925.14,3,1,1,1)
D REDOX^TIUDD
"^DD",8925.1,8925.14,3,1,1,2)
D REDOX^TIUDD
"^DD",8925.1,8925.14,3,1,1,"%D",0)
^^2^2^2940720^^
"^DD",8925.1,8925.14,3,1,1,"%D",1,0)
This MUMPS-type cross-reference will update the TIMESTAMP of the parent
"^DD",8925.1,8925.14,3,1,1,"%D",2,0)
document when the ITEM, MNEMONIC, or SEQUENCE change.
"^DD",8925.1,8925.14,3,1,1,"DT")
2940720
"^DD",8925.1,8925.14,3,1,2,0)
8925.14^AC
"^DD",8925.1,8925.14,3,1,2,1)
S ^TIU(8925.1,DA(1),10,"AC",$E(X,1,30),DA)=""
"^DD",8925.1,8925.14,3,1,2,2)
K ^TIU(8925.1,DA(1),10,"AC",$E(X,1,30),DA)
"^DD",8925.1,8925.14,3,1,2,3)
Please don't delete!
"^DD",8925.1,8925.14,3,1,2,"%D",0)
^^2^2^2950412^^^
"^DD",8925.1,8925.14,3,1,2,"%D",1,0)
This REGULAR Fileman cross reference is used to list items by sequence
"^DD",8925.1,8925.14,3,1,2,"%D",2,0)
number.
"^DD",8925.1,8925.14,3,1,2,"DT")
2950410
"^DD",8925.1,8925.14,3,3)
Item Sequence determines display order under the parent.  For alphabetic order, do not enter sequences.  Sequence is between .01 and 999, 2 Decimal Digits.
"^DD",8925.1,8925.14,3,21,0)
^^3^3^2970102^^^
"^DD",8925.1,8925.14,3,21,1,0)
Item Sequence, if entered, determines item's order under its parent. If
"^DD",8925.1,8925.14,3,21,2,0)
items have no sequence, item order is alphabetic by item Menu Text.
"^DD",8925.1,8925.14,3,21,3,0)
Sequence must be between .01 and 999.
"^DD",8925.1,8925.14,3,"DT")
2961021
"^DD",8925.1,8925.14,4,0)
MENU TEXT^RFX^^0;4^K:X[""""!($A(X)=45)!($A(X)=32) X I $D(X) K:$L(X)>20!($L(X)<1) X I $D(X) K:$$UPPER^TIULS($E(X,1,3))="ALL" X
"^DD",8925.1,8925.14,4,1,0)
^.1
"^DD",8925.1,8925.14,4,1,1,0)
8925.1^AMM4^MUMPS
"^DD",8925.1,8925.14,4,1,1,1)
D REDOX^TIUDD
"^DD",8925.1,8925.14,4,1,1,2)
D REDOX^TIUDD
"^DD",8925.1,8925.14,4,1,1,"%D",0)
^^2^2^2940720^
"^DD",8925.1,8925.14,4,1,1,"%D",1,0)
This MUMPS-type cross-reference updates the TIMESTAMP on the parent
"^DD",8925.1,8925.14,4,1,1,"%D",2,0)
document when the DISPLAY NAME changes.
"^DD",8925.1,8925.14,4,1,1,"DT")
2940720
"^DD",8925.1,8925.14,4,1,2,0)
8925.14^C^MUMPS
"^DD",8925.1,8925.14,4,1,2,1)
S ^TIU(8925.1,DA(1),10,"C",$E(X,1,30),DA)=""
"^DD",8925.1,8925.14,4,1,2,2)
K ^TIU(8925.1,DA(1),10,"C",$E(X,1,30),DA)
"^DD",8925.1,8925.14,4,1,2,"%D",0)
^^3^3^2961210^^
"^DD",8925.1,8925.14,4,1,2,"%D",1,0)
This M cross reference could have been regular.  It is used to display
"^DD",8925.1,8925.14,4,1,2,"%D",2,0)
items with no sequence in alpha order by Menu Text.
"^DD",8925.1,8925.14,4,1,2,"DT")
2961210
"^DD",8925.1,8925.14,4,3)
This is the short name of the entry, used in 3 column menus.  1 to 20 characters.  Must not begin with 'All', or with a space.
"^DD",8925.1,8925.14,4,4)

"^DD",8925.1,8925.14,4,21,0)
^^20^20^2990114^^
"^DD",8925.1,8925.14,4,21,1,0)
Item Menu Text is the short name users will see for Classes and Document
"^DD",8925.1,8925.14,4,21,2,0)
Classes when selecting them from 3-COLUMN MENUS.  Document Definitions are
"^DD",8925.1,8925.14,4,21,3,0)
selected from 3-column menus when viewing documents across many patients
"^DD",8925.1,8925.14,4,21,4,0)
and when viewing many kinds of documents at the same time (e.g. Progress
"^DD",8925.1,8925.14,4,21,5,0)
Notes and Discharge Summaries).
"^DD",8925.1,8925.14,4,21,6,0)
 
"^DD",8925.1,8925.14,4,21,7,0)
To edit the Menu Text of a Document Definition, you must be viewing the
"^DD",8925.1,8925.14,4,21,8,0)
Document Definition as an ITEM of its PARENT. Select 'Detailed Display'
"^DD",8925.1,8925.14,4,21,9,0)
for the PARENT and then 'Items'.
"^DD",8925.1,8925.14,4,21,10,0)
 
"^DD",8925.1,8925.14,4,21,11,0)
Menu Text has 1 - 20 characters. Menu Text must not begin with a space or
"^DD",8925.1,8925.14,4,21,12,0)
with 'All'.  The Document Definition Utility TIUF automatically sets the
"^DD",8925.1,8925.14,4,21,13,0)
Item Menu Text to the first 20 characters of the Item's Name when an entry
"^DD",8925.1,8925.14,4,21,14,0)
is first added as an item. (If an entry's Name begins with 'All' its Menu
"^DD",8925.1,8925.14,4,21,15,0)
Text is given 'AlX' as its first 3 characters.) The utility does NOT
"^DD",8925.1,8925.14,4,21,16,0)
update Menu Text if the entry Name is later changed, since this would
"^DD",8925.1,8925.14,4,21,17,0)
overwrite what a site may have carefully set up.  Menu Text is required.
"^DD",8925.1,8925.14,4,21,18,0)
 
"^DD",8925.1,8925.14,4,21,19,0)
Menu Text can affect item order under a parent since order is alphabetic
"^DD",8925.1,8925.14,4,21,20,0)
by menu text if items do not have sequence numbers.
"^DD",8925.1,8925.14,4,23,0)
^^10^10^2990114^^^^
"^DD",8925.1,8925.14,4,23,1,0)
Menu Text cannot begin with 'All' because XQOR, the Unwinder Utility,
"^DD",8925.1,8925.14,4,23,2,0)
misinterprets it.  The result (for titles) is that when a user selects a
"^DD",8925.1,8925.14,4,23,3,0)
Document Class of titles to view from a three column menu, and one of the
"^DD",8925.1,8925.14,4,23,4,0)
titles has menu text starting with 'All,' then no documents are found for
"^DD",8925.1,8925.14,4,23,5,0)
titles AFTER the title starting with 'All', even though such documents may
"^DD",8925.1,8925.14,4,23,6,0)
exist.  Similar problems occur with types other than titles.
"^DD",8925.1,8925.14,4,23,7,0)
 
"^DD",8925.1,8925.14,4,23,8,0)
Menu Text cannot begin with a space because such Menu Text cannot be used
"^DD",8925.1,8925.14,4,23,9,0)
to select the entry from a menu: if the space is left off, it is
"^DD",8925.1,8925.14,4,23,10,0)
questioned, and if the space is left in, it is still questioned.
"^DD",8925.1,8925.14,4,"DT")
2990121
"^DIC",8925.1,8925.1,0)
TIU DOCUMENT DEFINITION^8925.1
"^DIC",8925.1,8925.1,0,"GL")
^TIU(8925.1,
"^DIC",8925.1,8925.1,"%",0)
^1.005^2^1
"^DIC",8925.1,8925.1,"%",2,0)
GMTS
"^DIC",8925.1,8925.1,"%","B","GMTS",2)

"^DIC",8925.1,8925.1,"%D",0)
^^76^76^2970604^^^
"^DIC",8925.1,8925.1,"%D",1,0)
This file stores Document Definitions, which identify and define behavior
"^DIC",8925.1,8925.1,"%D",2,0)
for documents stored in the TIU DOCUMENTS FILE (#8925).  For consistency
"^DIC",8925.1,8925.1,"%D",3,0)
with the V-file schema, it may be viewed as the "Attribute Dictionary" for
"^DIC",8925.1,8925.1,"%D",4,0)
the Text Integration Utilities.
"^DIC",8925.1,8925.1,"%D",5,0)
 
"^DIC",8925.1,8925.1,"%D",6,0)
It also stores Objects, which can be embedded in a Document Definition's
"^DIC",8925.1,8925.1,"%D",7,0)
Boilerplate Text (Overprint). Objects contain M code which gets a piece of
"^DIC",8925.1,8925.1,"%D",8,0)
data and inserts it in the document's Boilerplate Text when a document is
"^DIC",8925.1,8925.1,"%D",9,0)
entered.
"^DIC",8925.1,8925.1,"%D",10,0)
 
"^DIC",8925.1,8925.1,"%D",11,0)
Warning: objects embedded in boilerplate text are looked up by multiple
"^DIC",8925.1,8925.1,"%D",12,0)
index (i.e. DIC(0) contains 'M'). Current code (see routine CHECK^TIUFLF3)
"^DIC",8925.1,8925.1,"%D",13,0)
checks all present indexes to make sure object names, abbreviations and
"^DIC",8925.1,8925.1,"%D",14,0)
print names are not ambiguous for this lookup. If new indexes are added,
"^DIC",8925.1,8925.1,"%D",15,0)
this code MUST BE UPDATED to check the new index as well.
"^DIC",8925.1,8925.1,"%D",16,0)
 
"^DIC",8925.1,8925.1,"%D",17,0)
Some entries in this file are developed Nationally and exported across the
"^DIC",8925.1,8925.1,"%D",18,0)
country.  Others are created by local sites.  Entries in the first
"^DIC",8925.1,8925.1,"%D",19,0)
category are marked National Standard and are not editable by sites.
"^DIC",8925.1,8925.1,"%D",20,0)
 
"^DIC",8925.1,8925.1,"%D",21,0)
This file does NOT allow multiple entries OF THE SAME TYPE with the same
"^DIC",8925.1,8925.1,"%D",22,0)
name.  That is, within a given Type, there are no duplicate names. (This
"^DIC",8925.1,8925.1,"%D",23,0)
refers to the .01 field, the Technical name of the entry.)
"^DIC",8925.1,8925.1,"%D",24,0)
 
"^DIC",8925.1,8925.1,"%D",25,0)
This file does not allow a parent to have items with the same name, even
"^DIC",8925.1,8925.1,"%D",26,0)
if the items have different internal file numbers (i.e. are different file
"^DIC",8925.1,8925.1,"%D",27,0)
entries).  Again, this refers to the .01 Technical name of the entry.
"^DIC",8925.1,8925.1,"%D",28,0)
 
"^DIC",8925.1,8925.1,"%D",29,0)
Because of ownership considerations, the file does NOT allow an entry to
"^DIC",8925.1,8925.1,"%D",30,0)
be an item under more than 1 parent.  If the same item is desired under
"^DIC",8925.1,8925.1,"%D",31,0)
more than 1 parent, the item must be copied into a new entry.  There is
"^DIC",8925.1,8925.1,"%D",32,0)
one exception:  Document Definitions of Type Component which have been
"^DIC",8925.1,8925.1,"%D",33,0)
marked Shared may have more than one parent.
"^DIC",8925.1,8925.1,"%D",34,0)
 
"^DIC",8925.1,8925.1,"%D",35,0)
The Document Definition Utility TIUF categorizes certain fields as Basic,
"^DIC",8925.1,8925.1,"%D",36,0)
Technical, or Upload, and displays these fields together as a group when
"^DIC",8925.1,8925.1,"%D",37,0)
user edits or views a Document Definition. BASIC fields include Name,
"^DIC",8925.1,8925.1,"%D",38,0)
Abbreviation, Print Name, Type, Personal Owner, Class Owner, Status, In
"^DIC",8925.1,8925.1,"%D",39,0)
Use, Shared, Orphan, Has Boiltxt, National Standard, OK to Distribute, and
"^DIC",8925.1,8925.1,"%D",40,0)
Suppress Visit Selection. TECHNICAL fields include Entry Action, Exit
"^DIC",8925.1,8925.1,"%D",41,0)
Action, Edit Template, Print Method, Print Form Header, Print Form Number,
"^DIC",8925.1,8925.1,"%D",42,0)
Print Group, Allow Custom Form Headers, Visit Linkage Method, Validation
"^DIC",8925.1,8925.1,"%D",43,0)
Method, and Object Method. UPLOAD fields include Upload Target File, Laygo
"^DIC",8925.1,8925.1,"%D",44,0)
Allowed, Target Text Field Subscript, Upload Look-up Method, Upload
"^DIC",8925.1,8925.1,"%D",45,0)
Post-Filing Code, Upload Filing Error Code, and multiples Upload Captioned
"^DIC",8925.1,8925.1,"%D",46,0)
ASCII Header and Upload Delimited ASCII Header.
"^DIC",8925.1,8925.1,"%D",47,0)
 
"^DIC",8925.1,8925.1,"%D",48,0)
The Document Definition file contains extensive, detailed field
"^DIC",8925.1,8925.1,"%D",49,0)
descriptions. Likewise, some protocols (File 101) used in TIU have
"^DIC",8925.1,8925.1,"%D",50,0)
extensive and careful descriptions in the Protocol file. Many of these
"^DIC",8925.1,8925.1,"%D",51,0)
descriptions are used in TIU for online help. If it becomes necessary for
"^DIC",8925.1,8925.1,"%D",52,0)
a national programmer to edit these descriptions, the programmer should
"^DIC",8925.1,8925.1,"%D",53,0)
check to make sure all online help is still displayed properly.
"^DIC",8925.1,8925.1,"%D",54,0)
 
"^DIC",8925.1,8925.1,"%D",55,0)
Users are expected to use the Document Definition Utility TIUF to enter,
"^DIC",8925.1,8925.1,"%D",56,0)
edit, and delete file entries.  In fact, the file prohibits the deletion
"^DIC",8925.1,8925.1,"%D",57,0)
of entries through generic Fileman Options.  It also prohibits the edit
"^DIC",8925.1,8925.1,"%D",58,0)
through generic Fileman of a few critical fields: Type, Status, Shared,
"^DIC",8925.1,8925.1,"%D",59,0)
and National Standard.  Adding and Deleting (but not editing) Items is
"^DIC",8925.1,8925.1,"%D",60,0)
also prohibited through generic Fileman options.  Abbreviation and Print
"^DIC",8925.1,8925.1,"%D",61,0)
Name of OBJECTS cannot be edited through generic Fileman Options.
"^DIC",8925.1,8925.1,"%D",62,0)
 
"^DIC",8925.1,8925.1,"%D",63,0)
This does NOT imply that it is SAFE to use generic Fileman to edit other
"^DIC",8925.1,8925.1,"%D",64,0)
fields.  Users are cautioned that edit through generic Fileman bypasses
"^DIC",8925.1,8925.1,"%D",65,0)
many safeguards built in to the Document Definition Utility and can create
"^DIC",8925.1,8925.1,"%D",66,0)
havoc unless the user THOROUGHLY UNDERSTANDS the File and its uses.
"^DIC",8925.1,8925.1,"%D",67,0)
 
"^DIC",8925.1,8925.1,"%D",68,0)
If users find needs which are not met through TIUF, please communicate
"^DIC",8925.1,8925.1,"%D",69,0)
them to the TIU development team.
"^DIC",8925.1,8925.1,"%D",70,0)
                           
"^DIC",8925.1,8925.1,"%D",71,0)
                               *****************
"^DIC",8925.1,8925.1,"%D",72,0)
 
"^DIC",8925.1,8925.1,"%D",73,0)
WARNING: Using generic Fileman options to edit entries can cause SERIOUS
"^DIC",8925.1,8925.1,"%D",74,0)
database problems.
"^DIC",8925.1,8925.1,"%D",75,0)
 
"^DIC",8925.1,8925.1,"%D",76,0)
                               ****************
"^DIC",8925.1,"B","TIU DOCUMENT DEFINITION",8925.1)

**END**
**END**