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

Last change on this file since 1687 was 737, checked in by Kevin Toppenberg, 15 years ago

Fixed Text Object Parameters

File size: 175.0 KB
Line 
1KIDS Distribution saved on Apr 18, 2010@22:43:40
2TMG CPRS TEXT OBJ FM FLD 1.0*1
3**KIDS**:TMG-CPRS-TEXTOBJ-FMFLD*1.0*1^
4
5**INSTALL NAME**
6TMG-CPRS-TEXTOBJ-FMFLD*1.0*1
7"BLD",7633,0)
8TMG-CPRS-TEXTOBJ-FMFLD*1.0*1^^0^3100418^n
9"BLD",7633,1,0)
10^^50^50^3100418^^
11"BLD",7633,1,1,0)
12This patch provides a TIU TEXT object that can be included
13"BLD",7633,1,2,0)
14on templates in CPRS. This object will allow fetching the
15"BLD",7633,1,3,0)
16value of any field from the PATIENT file.
17"BLD",7633,1,4,0)
18
19"BLD",7633,1,5,0)
20Usage
21"BLD",7633,1,6,0)
22 |TMG PATIENT FLD{Field(s)^Flags^FormatString}
23"BLD",7633,1,7,0)
24
25"BLD",7633,1,8,0)
26 Field(s) -- required. Options for input:
27"BLD",7633,1,9,0)
28 - A single field number or name
29"BLD",7633,1,10,0)
30 - A list of field numbers (or names), separated by semicolons
31"BLD",7633,1,11,0)
32 - A range of field numbers (or names), in the form M:N,
33"BLD",7633,1,12,0)
34 where M and N are the end points of the inclusive range.
35"BLD",7633,1,13,0)
36 All field numbers within this range are retrieved.
37"BLD",7633,1,14,0)
38 - A '*' for all fields at the top level (no sub-multiple record).
39"BLD",7633,1,15,0)
40 - A '**' for all fields including all fields and data in sub-multiple fields.
41"BLD",7633,1,16,0)
42 - Field number (or name) of a multiple followed by an * to indicate all
43"BLD",7633,1,17,0)
44 fields and records in the sub-multiple for that field.
45"BLD",7633,1,18,0)
46 Invalid field names will be ignored
47"BLD",7633,1,19,0)
48 Flags -- Optional.
49"BLD",7633,1,20,0)
50 - 'F' -- include field name in results with value. e.g. "AGE: 43" instead of just "43"
51"BLD",7633,1,21,0)
52 - This flag is ignored if a FormatString is provided (see below)
53"BLD",7633,1,22,0)
54 - 'S' -- Keep all data values on a single line, separated by ';'.
55"BLD",7633,1,23,0)
56 - If flag not provided, and multiple data fields are requested,
57"BLD",7633,1,24,0)
58 - then the default is that each data value will be separated by a
59"BLD",7633,1,25,0)
60 - CRLF [$C(13)_$C(10)]
61"BLD",7633,1,26,0)
62 - This flag is ignored if a FormatString is provided (see below)
63"BLD",7633,1,27,0)
64 - 'R' -- Resolve fields to NAMES, even if a field NUMBER was used for input request
65"BLD",7633,1,28,0)
66 - Note: this will affect the sorting order of the output (see FormatString
67"BLD",7633,1,29,0)
68 - info below). I.e. if R not specified, and field NUMBERS are used for input,
69"BLD",7633,1,30,0)
70 - then results will be returned in numerical field number order by default.
71"BLD",7633,1,31,0)
72 - If R is specified, then field numbers are converted to field NAMES, and that
73"BLD",7633,1,32,0)
74 - is used to determine the order of output.
75"BLD",7633,1,33,0)
76 - 'N' -- Don't return values for empty fields. This is helpful if ALL fields
77"BLD",7633,1,34,0)
78 - were requested via '*'
79"BLD",7633,1,35,0)
80 FormatString -- A string to determine how results are passed back....
81"BLD",7633,1,36,0)
82 NOTE: without a format string, results will be passed back in the order returned
83"BLD",7633,1,37,0)
84 by fileman. I.e. if user requested fields "SEX;.01;AGE", then Fileman will
85"BLD",7633,1,38,0)
86 place results into an array, which MUMPS will sort alphabetically, e.g.
87"BLD",7633,1,39,0)
88 .01, then AGE, then SEX. If "*" fields are requested, it would be even
89"BLD",7633,1,40,0)
90 more complex. A format string will allow the user to specify ORDER.
91"BLD",7633,1,41,0)
92 Format: e.g. "Any arbitrary text %FieldNameOrNum% more text %FieldNameOrNum% ..."
93"BLD",7633,1,42,0)
94 (The goal was to follow the method used by printf in the c language.)
95"BLD",7633,1,43,0)
96 - Any arbitrary text can be included.
97"BLD",7633,1,44,0)
98 - Field numbers or names should be enclosed by the '%' character
99"BLD",7633,1,45,0)
100 These will be replaced with actual data values.
101"BLD",7633,1,46,0)
102 - '\n' can be included to specify line breaks
103"BLD",7633,1,47,0)
104 - '%%' will be used to show a '%' in the output text
105"BLD",7633,1,48,0)
106 - Invalid, or non-matching, field names/numbers will be ignored.
107"BLD",7633,1,49,0)
108
109"BLD",7633,1,50,0)
110Results: returns a string that will be sent back to CPRS, to be included in a text note
111"BLD",7633,4,0)
112^9.64PA^8925.1^1
113"BLD",7633,4,8925.1,0)
1148925.1
115"BLD",7633,4,8925.1,222)
116n^y^f^^n^TMG PATIENT FLD^y^o^n
117"BLD",7633,4,8925.1,224)
118
119"BLD",7633,4,"B",8925.1,8925.1)
120
121"BLD",7633,6.3)
1221
123"BLD",7633,"KRN",0)
124^9.67PA^8989.52^19
125"BLD",7633,"KRN",.4,0)
126.4
127"BLD",7633,"KRN",.401,0)
128.401
129"BLD",7633,"KRN",.402,0)
130.402
131"BLD",7633,"KRN",.403,0)
132.403
133"BLD",7633,"KRN",.5,0)
134.5
135"BLD",7633,"KRN",.84,0)
136.84
137"BLD",7633,"KRN",3.6,0)
1383.6
139"BLD",7633,"KRN",3.8,0)
1403.8
141"BLD",7633,"KRN",9.2,0)
1429.2
143"BLD",7633,"KRN",9.8,0)
1449.8
145"BLD",7633,"KRN",9.8,"NM",0)
146^9.68A^1^1
147"BLD",7633,"KRN",9.8,"NM",1,0)
148TMGTIUO2^^0^B57347468
149"BLD",7633,"KRN",9.8,"NM","B","TMGTIUO2",1)
150
151"BLD",7633,"KRN",19,0)
15219
153"BLD",7633,"KRN",19.1,0)
15419.1
155"BLD",7633,"KRN",101,0)
156101
157"BLD",7633,"KRN",409.61,0)
158409.61
159"BLD",7633,"KRN",771,0)
160771
161"BLD",7633,"KRN",870,0)
162870
163"BLD",7633,"KRN",8989.51,0)
1648989.51
165"BLD",7633,"KRN",8989.52,0)
1668989.52
167"BLD",7633,"KRN",8994,0)
1688994
169"BLD",7633,"KRN","B",.4,.4)
170
171"BLD",7633,"KRN","B",.401,.401)
172
173"BLD",7633,"KRN","B",.402,.402)
174
175"BLD",7633,"KRN","B",.403,.403)
176
177"BLD",7633,"KRN","B",.5,.5)
178
179"BLD",7633,"KRN","B",.84,.84)
180
181"BLD",7633,"KRN","B",3.6,3.6)
182
183"BLD",7633,"KRN","B",3.8,3.8)
184
185"BLD",7633,"KRN","B",9.2,9.2)
186
187"BLD",7633,"KRN","B",9.8,9.8)
188
189"BLD",7633,"KRN","B",19,19)
190
191"BLD",7633,"KRN","B",19.1,19.1)
192
193"BLD",7633,"KRN","B",101,101)
194
195"BLD",7633,"KRN","B",409.61,409.61)
196
197"BLD",7633,"KRN","B",771,771)
198
199"BLD",7633,"KRN","B",870,870)
200
201"BLD",7633,"KRN","B",8989.51,8989.51)
202
203"BLD",7633,"KRN","B",8989.52,8989.52)
204
205"BLD",7633,"KRN","B",8994,8994)
206
207"BLD",7633,"QUES",0)
208^9.62^^
209"DATA",8925.1,1452,0)
210TMG PATIENT FLD^^TMG PATIENT FLD^O^^55^11
211"DATA",8925.1,1452,9)
212S X=$$GETPTFLD^TMGTIUO2($G(DFN),X)
213"DATA",8925.1,1452,99)
21461831,73983
215"FIA",8925.1)
216TIU DOCUMENT DEFINITION
217"FIA",8925.1,0)
218^TIU(8925.1,
219"FIA",8925.1,0,0)
2208925.1I
221"FIA",8925.1,0,1)
222n^y^f^^n^TMG PATIENT FLD^y^o^n
223"FIA",8925.1,0,10)
224
225"FIA",8925.1,0,11)
226
227"FIA",8925.1,0,"RLRO")
228^DIBT(913,1)
229"FIA",8925.1,8925.1)
2300
231"FIA",8925.1,8925.11)
2320
233"FIA",8925.1,8925.111)
2340
235"FIA",8925.1,8925.112)
2360
237"FIA",8925.1,8925.113)
2380
239"FIA",8925.1,8925.114)
2400
241"FIA",8925.1,8925.12)
2420
243"FIA",8925.1,8925.13)
2440
245"FIA",8925.1,8925.14)
2460
247"MBREQ")
2480
249"QUES","XPF1",0)
250Y
251"QUES","XPF1","??")
252^D REP^XPDH
253"QUES","XPF1","A")
254Shall I write over your |FLAG| File
255"QUES","XPF1","B")
256YES
257"QUES","XPF1","M")
258D XPF1^XPDIQ
259"QUES","XPF2",0)
260Y
261"QUES","XPF2","??")
262^D DTA^XPDH
263"QUES","XPF2","A")
264Want my data |FLAG| yours
265"QUES","XPF2","B")
266YES
267"QUES","XPF2","M")
268D XPF2^XPDIQ
269"QUES","XPI1",0)
270YO
271"QUES","XPI1","??")
272^D INHIBIT^XPDH
273"QUES","XPI1","A")
274Want KIDS to INHIBIT LOGONs during the install
275"QUES","XPI1","B")
276NO
277"QUES","XPI1","M")
278D XPI1^XPDIQ
279"QUES","XPM1",0)
280PO^VA(200,:EM
281"QUES","XPM1","??")
282^D MG^XPDH
283"QUES","XPM1","A")
284Enter the Coordinator for Mail Group '|FLAG|'
285"QUES","XPM1","B")
286
287"QUES","XPM1","M")
288D XPM1^XPDIQ
289"QUES","XPO1",0)
290Y
291"QUES","XPO1","??")
292^D MENU^XPDH
293"QUES","XPO1","A")
294Want KIDS to Rebuild Menu Trees Upon Completion of Install
295"QUES","XPO1","B")
296NO
297"QUES","XPO1","M")
298D XPO1^XPDIQ
299"QUES","XPZ1",0)
300Y
301"QUES","XPZ1","??")
302^D OPT^XPDH
303"QUES","XPZ1","A")
304Want to DISABLE Scheduled Options, Menu Options, and Protocols
305"QUES","XPZ1","B")
306NO
307"QUES","XPZ1","M")
308D XPZ1^XPDIQ
309"QUES","XPZ2",0)
310Y
311"QUES","XPZ2","??")
312^D RTN^XPDH
313"QUES","XPZ2","A")
314Want to MOVE routines to other CPUs
315"QUES","XPZ2","B")
316NO
317"QUES","XPZ2","M")
318D XPZ2^XPDIQ
319"RTN")
3201
321"RTN","TMGTIUO2")
3220^1^B57347468
323"RTN","TMGTIUO2",1,0)
324TMGTIU02 ;TMG/TIU Text Object Expansion Fns;04/15/10
325"RTN","TMGTIUO2",2,0)
326 ;;1.0;TMG-LIB;**1**;04/15/10;Build 1
327"RTN","TMGTIUO2",3,0)
328 ;
329"RTN","TMGTIUO2",4,0)
330 ;"Kevin Toppenberg MD
331"RTN","TMGTIUO2",5,0)
332 ;"GNU General Public License (GPL) applies
333"RTN","TMGTIUO2",6,0)
334 ;"04/15/10
335"RTN","TMGTIUO2",7,0)
336 ;
337"RTN","TMGTIUO2",8,0)
338 ;"=======================================================================
339"RTN","TMGTIUO2",9,0)
340 ;"PUBLIC FUNCTIONS
341"RTN","TMGTIUO2",10,0)
342 ;"=======================================================================
343"RTN","TMGTIUO2",11,0)
344 ;
345"RTN","TMGTIUO2",12,0)
346 ;"=======================================================================
347"RTN","TMGTIUO2",13,0)
348 ;"PRIVATE FUNCTIONS
349"RTN","TMGTIUO2",14,0)
350 ;"=======================================================================
351"RTN","TMGTIUO2",15,0)
352 ;
353"RTN","TMGTIUO2",16,0)
354 ;"=======================================================================
355"RTN","TMGTIUO2",17,0)
356 ;
357"RTN","TMGTIUO2",18,0)
358GETPTFLD(DFN,PARAM) ;
359"RTN","TMGTIUO2",19,0)
360 ;"Purpose: This is the server-side code for the TIU TEXT OBJECT, which
361"RTN","TMGTIUO2",20,0)
362 ;" will allow the user to retrieve a field from the PATIENT file.
363"RTN","TMGTIUO2",21,0)
364 ;"NOTE: This requires that patch TMG-CPRS-TEXTOBJ-PARAM*1.0*1 or later
365"RTN","TMGTIUO2",22,0)
366 ;" be installed, to allow passing in of parameters from the CPRS client.
367"RTN","TMGTIUO2",23,0)
368 ;"Input: DFN -- This should be the IEN of the currently open patient
369"RTN","TMGTIUO2",24,0)
370 ;" Param -- Field(s)^Flags^FormatString. Details below
371"RTN","TMGTIUO2",25,0)
372 ;" Field(s) -- required. Options for input:
373"RTN","TMGTIUO2",26,0)
374 ;" - A single field number or name
375"RTN","TMGTIUO2",27,0)
376 ;" - A list of field numbers (or names), separated by semicolons
377"RTN","TMGTIUO2",28,0)
378 ;" - A range of field numbers (or names), in the form M:N,
379"RTN","TMGTIUO2",29,0)
380 ;" where M and N are the end points of the inclusive range.
381"RTN","TMGTIUO2",30,0)
382 ;" All field numbers within this range are retrieved.
383"RTN","TMGTIUO2",31,0)
384 ;" - A '*' for all fields at the top level (no sub-multiple record).
385"RTN","TMGTIUO2",32,0)
386 ;" - A '**' for all fields including all fields and data in sub-multiple fields.
387"RTN","TMGTIUO2",33,0)
388 ;" - Field number (or name) of a multiple followed by an * to indicate all
389"RTN","TMGTIUO2",34,0)
390 ;" fields and records in the sub-multiple for that field.
391"RTN","TMGTIUO2",35,0)
392 ;" Invalid field names will be ignored
393"RTN","TMGTIUO2",36,0)
394 ;" Flags -- Optional.
395"RTN","TMGTIUO2",37,0)
396 ;" - 'F' -- include field name in results with value. e.g. "AGE: 43" instead of just "43"
397"RTN","TMGTIUO2",38,0)
398 ;" - This flag is ignored if a FormatString is provided (see below)
399"RTN","TMGTIUO2",39,0)
400 ;" - 'S' -- Keep all data values on a single line, separated by ';'.
401"RTN","TMGTIUO2",40,0)
402 ;" - If flag not provided, and multiple data fields are requested,
403"RTN","TMGTIUO2",41,0)
404 ;" - then the default is that each data value will be separated by a
405"RTN","TMGTIUO2",42,0)
406 ;" - CRLF [$C(13)_$C(10)]
407"RTN","TMGTIUO2",43,0)
408 ;" - This flag is ignored if a FormatString is provided (see below)
409"RTN","TMGTIUO2",44,0)
410 ;" - 'R' -- Resolve fields to NAMES, even if a field NUMBER was used for input request
411"RTN","TMGTIUO2",45,0)
412 ;" - Note: this will affect the sorting order of the output (see FormatString
413"RTN","TMGTIUO2",46,0)
414 ;" - info below). I.e. if R not specified, and field NUMBERS are used for input,
415"RTN","TMGTIUO2",47,0)
416 ;" - then results will be returned in numerical field number order by default.
417"RTN","TMGTIUO2",48,0)
418 ;" - If R is specified, then field numbers are converted to field NAMES, and that
419"RTN","TMGTIUO2",49,0)
420 ;" - is used to determine the order of output.
421"RTN","TMGTIUO2",50,0)
422 ;" - 'N' -- Don't return values for empty fields. This is helpful if ALL fields
423"RTN","TMGTIUO2",51,0)
424 ;" - were requested via '*'
425"RTN","TMGTIUO2",52,0)
426 ;" FormatString -- A string to determine how results are passed back....
427"RTN","TMGTIUO2",53,0)
428 ;" NOTE: without a format string, results will be passed back in the order returned
429"RTN","TMGTIUO2",54,0)
430 ;" by fileman. I.e. if user requested fields "SEX;.01;AGE", then Fileman will
431"RTN","TMGTIUO2",55,0)
432 ;" place results into an array, which MUMPS will sort alphabetically, e.g.
433"RTN","TMGTIUO2",56,0)
434 ;" .01, then AGE, then SEX. If "*" fields are requested, it would be even
435"RTN","TMGTIUO2",57,0)
436 ;" more complex. A format string will allow the user to specify ORDER.
437"RTN","TMGTIUO2",58,0)
438 ;" Format: e.g. "Any arbitrary text %FieldNameOrNum% more text %FieldNameOrNum% ..."
439"RTN","TMGTIUO2",59,0)
440 ;" (The goal was to follow the method used by printf in the c language.)
441"RTN","TMGTIUO2",60,0)
442 ;" - Any arbitrary text can be included.
443"RTN","TMGTIUO2",61,0)
444 ;" - Field numbers or names should be enclosed by the '%' character
445"RTN","TMGTIUO2",62,0)
446 ;" These will be replaced with actual data values.
447"RTN","TMGTIUO2",63,0)
448 ;" - '\n' can be included to specify line breaks
449"RTN","TMGTIUO2",64,0)
450 ;" - '%%' will be used to show a '%' in the output text
451"RTN","TMGTIUO2",65,0)
452 ;" - Invalid, or non-matching, field names/numbers will be ignored.
453"RTN","TMGTIUO2",66,0)
454 ;"
455"RTN","TMGTIUO2",67,0)
456 ;"Results: returns a string that will be sent back to CPRS, to be included in a text note
457"RTN","TMGTIUO2",68,0)
458 ;"NOTE: I have chosen to make this function work with only file 2 (PATIENT FILE). I think
459"RTN","TMGTIUO2",69,0)
460 ;" it could be a security violation if any CPRS user was able to look at any arbitrary file.
461"RTN","TMGTIUO2",70,0)
462 ;"
463"RTN","TMGTIUO2",71,0)
464 ;"Examples of PARAM inputs:
465"RTN","TMGTIUO2",72,0)
466 ;" '.01' -- returns .01 field, which is the patients NAME, e.g. "SMITH,JOHN A"
467"RTN","TMGTIUO2",73,0)
468 ;" 'NAME' -- returns same value as above, e.g. "SMITH,JOHN A"
469"RTN","TMGTIUO2",74,0)
470 ;" 'NAME^F' -- e.g result "NAME: SMITH,JOHN A"
471"RTN","TMGTIUO2",75,0)
472 ;" 'NAME;SEX;AGE^F' --> "AGE: 34"_$C(13)_$C(10)_"NAME: SMITH,JOHN A"_$C(13)_$C(10)_"SEX: MALE"
473"RTN","TMGTIUO2",76,0)
474 ;" 'NAME;SEX;AGE^S' --> "34; SMITH,JOHN A; MALE"
475"RTN","TMGTIUO2",77,0)
476 ;" 'NAME;SEX;AGE^^"NAME: %NAME%, %AGE% yrs., %SEX%"' --> "NAME: SMITH,JOHN A, 34 YRS., MALE"
477"RTN","TMGTIUO2",78,0)
478 ;"
479"RTN","TMGTIUO2",79,0)
480 NEW TMGFLDS,TMGFLAGS
481"RTN","TMGTIUO2",80,0)
482 NEW TMGFILE SET TMGFILE=2
483"RTN","TMGTIUO2",81,0)
484 NEW RESULT SET RESULT=""
485"RTN","TMGTIUO2",82,0)
486 SET PARAM=$GET(PARAM)
487"RTN","TMGTIUO2",83,0)
488 SET TMGFLDS=$PIECE(PARAM,"^",1)
489"RTN","TMGTIUO2",84,0)
490 IF TMGFLDS="" DO GOTO GPDN
491"RTN","TMGTIUO2",85,0)
492 . SET RESULT="ERROR: No input parameter. Example of use: |TMG PATIENT FLD{AGE}|"
493"RTN","TMGTIUO2",86,0)
494 SET DFN=$GET(DFN)
495"RTN","TMGTIUO2",87,0)
496 IF +DFN'>0 DO GOTO GPDN
497"RTN","TMGTIUO2",88,0)
498 . SET RESULT="ERROR: Internal patient value DFN not defined. Contact IRM"
499"RTN","TMGTIUO2",89,0)
500 NEW TMGIENS SET TMGIENS=DFN_","
501"RTN","TMGTIUO2",90,0)
502 SET TMGFLAGS=""
503"RTN","TMGTIUO2",91,0)
504 NEW TMGTEMP SET TMGTEMP=$$UP^XLFSTR($PIECE(PARAM,"^",2))
505"RTN","TMGTIUO2",92,0)
506 IF TMGTEMP["N" SET TMGFLAGS=TMGFLAGS_"N"
507"RTN","TMGTIUO2",93,0)
508 IF TMGTEMP["F" SET TMGFLAGS=TMGFLAGS_"R"
509"RTN","TMGTIUO2",94,0)
510 NEW TMGFORMAT SET TMGFORMAT=$PIECE(PARAM,"^",3)
511"RTN","TMGTIUO2",95,0)
512 NEW TMGOUT,TMGMSG
513"RTN","TMGTIUO2",96,0)
514 DO GETS^DIQ(TMGFILE,TMGIENS,TMGFLDS,TMGFLAGS,"TMGOUT","TMGMSG")
515"RTN","TMGTIUO2",97,0)
516 IF $DATA(TMGMSG("DIERR")) DO GOTO GPDN
517"RTN","TMGTIUO2",98,0)
518 . SET RESULT=$$GetErrStr^TMGDEBUG(.TMGMSG)
519"RTN","TMGTIUO2",99,0)
520 NEW FLD,FLDNAME
521"RTN","TMGTIUO2",100,0)
522 SET FLD=""
523"RTN","TMGTIUO2",101,0)
524 IF TMGFORMAT="" DO
525"RTN","TMGTIUO2",102,0)
526 . FOR SET FLD=$ORDER(TMGOUT(TMGFILE,TMGIENS,FLD)) QUIT:(FLD="") DO
527"RTN","TMGTIUO2",103,0)
528 . . IF $DATA(TMGOUT(TMGFILE,TMGIENS,FLD,0)) QUIT ;"For now, WP fields are not supported. Could add later if needed.
529"RTN","TMGTIUO2",104,0)
530 . . NEW VALUE SET VALUE=$GET(TMGOUT(TMGFILE,TMGIENS,FLD))
531"RTN","TMGTIUO2",105,0)
532 . . IF VALUE="",TMGTEMP["N" QUIT
533"RTN","TMGTIUO2",106,0)
534 . . IF RESULT'="" DO
535"RTN","TMGTIUO2",107,0)
536 . . . IF TMGTEMP["S" SET RESULT=RESULT_"; "
537"RTN","TMGTIUO2",108,0)
538 . . . ELSE SET RESULT=RESULT_$CHAR(13)_$CHAR(10)
539"RTN","TMGTIUO2",109,0)
540 . . IF TMGTEMP["F" DO
541"RTN","TMGTIUO2",110,0)
542 . . . IF FLD'=+FLD SET FLDNAME=FLD
543"RTN","TMGTIUO2",111,0)
544 . . . ELSE SET FLDNAME=$PIECE($GET(^DD(TMGFILE,FLD,0)),"^",1)
545"RTN","TMGTIUO2",112,0)
546 . . . SET RESULT=RESULT_FLDNAME_": "
547"RTN","TMGTIUO2",113,0)
548 . . SET RESULT=RESULT_VALUE
549"RTN","TMGTIUO2",114,0)
550 ELSE DO ;"Handle format strings.
551"RTN","TMGTIUO2",115,0)
552 . SET RESULT=TMGFORMAT
553"RTN","TMGTIUO2",116,0)
554 . FOR QUIT:(RESULT'["%") DO
555"RTN","TMGTIUO2",117,0)
556 . . NEW SUBA,SUBB
557"RTN","TMGTIUO2",118,0)
558 . . SET SUBA=$PIECE(RESULT,"%",1)
559"RTN","TMGTIUO2",119,0)
560 . . SET FLD=$PIECE(RESULT,"%",2)
561"RTN","TMGTIUO2",120,0)
562 . . SET SUBB=$PIECE(RESULT,"%",3,999)
563"RTN","TMGTIUO2",121,0)
564 . . NEW VALUE
565"RTN","TMGTIUO2",122,0)
566 . . IF FLD="" SET VALUE="<@!@>" ;"protect %%, later convert back to '%'
567"RTN","TMGTIUO2",123,0)
568 . . ELSE SET VALUE=$GET(TMGOUT(TMGFILE,TMGIENS,FLD))
569"RTN","TMGTIUO2",124,0)
570 . . IF VALUE="" DO
571"RTN","TMGTIUO2",125,0)
572 . . . IF FLD=+FLD DO
573"RTN","TMGTIUO2",126,0)
574 . . . . SET FLD=$PIECE($GET(^DD(TMGFILE,FLD,0)),"^",1) ;"Convert # to name
575"RTN","TMGTIUO2",127,0)
576 . . . ELSE DO
577"RTN","TMGTIUO2",128,0)
578 . . . . SET FLD=$ORDER(^DD(TMGFILE,"B",FLD,"")) ;"Convert name to #
579"RTN","TMGTIUO2",129,0)
580 . . . IF FLD'="" SET VALUE=$GET(TMGOUT(TMGFILE,TMGIENS,FLD))
581"RTN","TMGTIUO2",130,0)
582 . . . IF VALUE="" SET VALUE="??"
583"RTN","TMGTIUO2",131,0)
584 . . SET RESULT=SUBA_VALUE_SUBB
585"RTN","TMGTIUO2",132,0)
586 . NEW TMGALT
587"RTN","TMGTIUO2",133,0)
588 . SET TMGALT("<@!@>")="%"
589"RTN","TMGTIUO2",134,0)
590 . SET TMGALT("\n")=$CHAR(13)_$CHAR(10)
591"RTN","TMGTIUO2",135,0)
592 . SET RESULT=$$REPLACE^XLFSTR(RESULT,.TMGALT)
593"RTN","TMGTIUO2",136,0)
594 ;
595"RTN","TMGTIUO2",137,0)
596GPDN QUIT RESULT
597"SEC","^DD",8925.1,8925.1,.01,8.5)
598
599"SEC","^DIC",8925.1,8925.1,0,"AUDIT")
600@
601"SEC","^DIC",8925.1,8925.1,0,"DD")
602@
603"SEC","^DIC",8925.1,8925.1,0,"DEL")
604@
605"SEC","^DIC",8925.1,8925.1,0,"RD")
606@
607"SEC","^DIC",8925.1,8925.1,0,"WR")
608@
609"VER")
6108.0^22.0
611"^DD",8925.1,8925.1,0)
612FIELD^^99^54
613"^DD",8925.1,8925.1,0,"DDA")
614N
615"^DD",8925.1,8925.1,0,"DT")
6162970227
617"^DD",8925.1,8925.1,0,"ID","W.04")
618W " ",@("$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)")
619"^DD",8925.1,8925.1,0,"ID","W.1501")
620S %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
621"^DD",8925.1,8925.1,0,"IX","AC",8925.1,.06)
622
623"^DD",8925.1,8925.1,0,"IX","ACL",8925.1,.01)
624
625"^DD",8925.1,8925.1,0,"IX","ACL02",8925.1,.02)
626
627"^DD",8925.1,8925.1,0,"IX","ACL03",8925.1,.03)
628
629"^DD",8925.1,8925.1,0,"IX","ACL07",8925.1,.07)
630
631"^DD",8925.1,8925.1,0,"IX","ACL1001",8925.14,.01)
632
633"^DD",8925.1,8925.1,0,"IX","AD",8925.14,.01)
634
635"^DD",8925.1,8925.1,0,"IX","ALOINC",8925.1,1501)
636
637"^DD",8925.1,8925.1,0,"IX","AM",8925.1,99)
638
639"^DD",8925.1,8925.1,0,"IX","AM1",8925.1,.03)
640
641"^DD",8925.1,8925.1,0,"IX","AMM",8925.14,.01)
642
643"^DD",8925.1,8925.1,0,"IX","AMM2",8925.14,2)
644
645"^DD",8925.1,8925.1,0,"IX","AMM3",8925.14,3)
646
647"^DD",8925.1,8925.1,0,"IX","AMM4",8925.14,4)
648
649"^DD",8925.1,8925.1,0,"IX","AP",8925.1,.05)
650
651"^DD",8925.1,8925.1,0,"IX","APOST",8925.1,.14)
652
653"^DD",8925.1,8925.1,0,"IX","AS",8925.1,.07)
654
655"^DD",8925.1,8925.1,0,"IX","AT",8925.1,.04)
656
657"^DD",8925.1,8925.1,0,"IX","B",8925.1,.01)
658
659"^DD",8925.1,8925.1,0,"IX","C",8925.1,.02)
660
661"^DD",8925.1,8925.1,0,"IX","D",8925.1,.03)
662
663"^DD",8925.1,8925.1,0,"IX","E",8925.1,.01)
664
665"^DD",8925.1,8925.1,0,"NM","TIU DOCUMENT DEFINITION")
666
667"^DD",8925.1,8925.1,0,"PT",26.11,.07)
668
669"^DD",8925.1,8925.1,0,"PT",26.15,.07)
670
671"^DD",8925.1,8925.1,0,"PT",142.14,.01)
672
673"^DD",8925.1,8925.1,0,"PT",702.01,.04)
674
675"^DD",8925.1,8925.1,0,"PT",703.91,.05)
676
677"^DD",8925.1,8925.1,0,"PT",783.9,.04)
678
679"^DD",8925.1,8925.1,0,"PT",783.9,.05)
680
681"^DD",8925.1,8925.1,0,"PT",783.9,.06)
682
683"^DD",8925.1,8925.1,0,"PT",2006.5841,6)
684
685"^DD",8925.1,8925.1,0,"PT",8925,.01)
686
687"^DD",8925.1,8925.1,0,"PT",8925,.04)
688
689"^DD",8925.1,8925.1,0,"PT",8925.14,.01)
690
691"^DD",8925.1,8925.1,0,"PT",8925.95,.01)
692
693"^DD",8925.1,8925.1,0,"PT",8925.98,.02)
694
695"^DD",8925.1,8925.1,0,"PT",8925.98,.03)
696
697"^DD",8925.1,8925.1,0,"PT",8925.9801,.01)
698
699"^DD",8925.1,8925.1,0,"PT",8927,.19)
700
701"^DD",8925.1,8925.1,0,"PT",8930.1,.01)
702
703"^DD",8925.1,8925.1,0,"VRPK")
704TEXT INTEGRATION UTILITIES
705"^DD",8925.1,8925.1,.01,0)
706NAME^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
707"^DD",8925.1,8925.1,.01,.1)
708
709"^DD",8925.1,8925.1,.01,1,0)
710^.1
711"^DD",8925.1,8925.1,.01,1,1,0)
7128925.1^B
713"^DD",8925.1,8925.1,.01,1,1,1)
714S ^TIU(8925.1,"B",$E(X,1,60),DA)=""
715"^DD",8925.1,8925.1,.01,1,1,2)
716K ^TIU(8925.1,"B",$E(X,1,60),DA)
717"^DD",8925.1,8925.1,.01,1,2,0)
7188925.1^E^KWIC
719"^DD",8925.1,8925.1,.01,1,2,1)
720S %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)=""
721"^DD",8925.1,8925.1,.01,1,2,2)
722S %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)
723"^DD",8925.1,8925.1,.01,1,2,"%D",0)
724^^2^2^2960302^
725"^DD",8925.1,8925.1,.01,1,2,"%D",1,0)
726This KWIK cross-reference on document name will allow look-up based on
727"^DD",8925.1,8925.1,.01,1,2,"%D",2,0)
728sub-names, etc.
729"^DD",8925.1,8925.1,.01,1,2,"DT")
7302960302
731"^DD",8925.1,8925.1,.01,1,3,0)
7328925.1^ACL^MUMPS
733"^DD",8925.1,8925.1,.01,1,3,1)
734D SACL^TIUDD1(X,.01)
735"^DD",8925.1,8925.1,.01,1,3,2)
736D KACL^TIUDD1(X,.01)
737"^DD",8925.1,8925.1,.01,1,3,"%D",0)
738^^7^7^3040831^
739"^DD",8925.1,8925.1,.01,1,3,"%D",1,0)
740This is a complex cross-reference on the .01 (NAME) field. Its format
741"^DD",8925.1,8925.1,.01,1,3,"%D",2,0)
742will be as follows:
743"^DD",8925.1,8925.1,.01,1,3,"%D",3,0)
744
745"^DD",8925.1,8925.1,.01,1,3,"%D",4,0)
746 ^TIU(8925.1,"ACL",Parent document class IEN, Title NAME, Title IEN)=""
747"^DD",8925.1,8925.1,.01,1,3,"%D",5,0)
748
749"^DD",8925.1,8925.1,.01,1,3,"%D",6,0)
750The purpose of this cross-reference will be to help CPRS GUI perform
751"^DD",8925.1,8925.1,.01,1,3,"%D",7,0)
752faster title look-ups by document class.
753"^DD",8925.1,8925.1,.01,1,3,"DT")
7542971016
755"^DD",8925.1,8925.1,.01,3)
756This 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.
757"^DD",8925.1,8925.1,.01,4)
758D NAME^TIUFXHLX:$G(TIUFXNOD)["Add/Create"&($G(TIUFSTMP)="T")
759"^DD",8925.1,8925.1,.01,21,0)
760^^51^51^2980127^^^^
761"^DD",8925.1,8925.1,.01,21,1,0)
762The name of a Document Definition entry (.01 field) must be between 3
763"^DD",8925.1,8925.1,.01,21,2,0)
764and 60 characters long and may not begin with a punctuation character.
765"^DD",8925.1,8925.1,.01,21,3,0)
766Although names can be entered in any case, they are transformed to
767"^DD",8925.1,8925.1,.01,21,4,0)
768upper case before being stored.
769"^DD",8925.1,8925.1,.01,21,5,0)
770
771"^DD",8925.1,8925.1,.01,21,6,0)
772It functions as the Technical Name of the entry. Some sites have put KWIC
773"^DD",8925.1,8925.1,.01,21,7,0)
774cross references on it to get, say, all Titles from a given Service.
775"^DD",8925.1,8925.1,.01,21,8,0)
776
777"^DD",8925.1,8925.1,.01,21,9,0)
778Name can be used when entering documents as the name of the Title being
779"^DD",8925.1,8925.1,.01,21,10,0)
780entered. Print Name and Abbreviation will also be accepted.
781"^DD",8925.1,8925.1,.01,21,11,0)
782
783"^DD",8925.1,8925.1,.01,21,12,0)
784Since it is the Technical, .01 Name, the Document Definition Utility
785"^DD",8925.1,8925.1,.01,21,13,0)
786(TIUF) uses this name throughout.
787"^DD",8925.1,8925.1,.01,21,14,0)
788
789"^DD",8925.1,8925.1,.01,21,15,0)
790The .01 name differs from the Print Name, which appears in lists of
791"^DD",8925.1,8925.1,.01,21,16,0)
792documents and functions as the Title of the document.
793"^DD",8925.1,8925.1,.01,21,17,0)
794
795"^DD",8925.1,8925.1,.01,21,18,0)
796It also differs from Item Menu Text (1-20 characters), which is used when
797"^DD",8925.1,8925.1,.01,21,19,0)
798selecting documents from 3-COLUMN MENUS.
799"^DD",8925.1,8925.1,.01,21,20,0)
800
801"^DD",8925.1,8925.1,.01,21,21,0)
802The ORDER of names in TIUF options Edit Document Definitions and Create
803"^DD",8925.1,8925.1,.01,21,22,0)
804Document Definitions is by Item Sequence under the parent. Order is
805"^DD",8925.1,8925.1,.01,21,23,0)
806alphabetic by Menu Text if an Item has no Item Sequence.
807"^DD",8925.1,8925.1,.01,21,24,0)
808
809"^DD",8925.1,8925.1,.01,21,25,0)
810When a new entry is added to file 8925.1, the Document Definition Utility
811"^DD",8925.1,8925.1,.01,21,26,0)
812(TIUF) enters the Name as the default Print Name. The Print Name can be
813"^DD",8925.1,8925.1,.01,21,27,0)
814edited if a different Print Name is desired.
815"^DD",8925.1,8925.1,.01,21,28,0)
816
817"^DD",8925.1,8925.1,.01,21,29,0)
818File 8925.1 permits more than 1 entry with the same name as long as they
819"^DD",8925.1,8925.1,.01,21,30,0)
820don't have the same Type. In that sense, NAMES are reusable. However,
821"^DD",8925.1,8925.1,.01,21,31,0)
822ENTRIES are NOT reusable (except specially marked Components): an entry is
823"^DD",8925.1,8925.1,.01,21,32,0)
824NOT allowed to be an item under more than one parent unless it is a Shared
825"^DD",8925.1,8925.1,.01,21,33,0)
826Component. (See Type Component.)
827"^DD",8925.1,8925.1,.01,21,34,0)
828
829"^DD",8925.1,8925.1,.01,21,35,0)
830Name is a BASIC Field.
831"^DD",8925.1,8925.1,.01,21,36,0)
832
833"^DD",8925.1,8925.1,.01,21,37,0)
834 OBJECT Name
835"^DD",8925.1,8925.1,.01,21,38,0)
836Object Names, like any other names are 3-60 characters, not starting with
837"^DD",8925.1,8925.1,.01,21,39,0)
838punctuation. Sites may want to namespace object names, use the object
839"^DD",8925.1,8925.1,.01,21,40,0)
840Print Name as a more familiar name, and use object Abbreviation as a short
841"^DD",8925.1,8925.1,.01,21,41,0)
842name to embed in boilerplate text. Unlike other Types, Object
843"^DD",8925.1,8925.1,.01,21,42,0)
844Abbreviation and Print Name as well as Name must be uppercase.
845"^DD",8925.1,8925.1,.01,21,43,0)
846
847"^DD",8925.1,8925.1,.01,21,44,0)
848Object Name, Abbreviation, or Print Name can be embedded in boilerplate
849"^DD",8925.1,8925.1,.01,21,45,0)
850text. Since TIU must be able to determine from this which object is
851"^DD",8925.1,8925.1,.01,21,46,0)
852intended, object Names, Abbreviations, and Print Names must be unique. In
853"^DD",8925.1,8925.1,.01,21,47,0)
854fact, an object Name must differ not only from every other object name,
855"^DD",8925.1,8925.1,.01,21,48,0)
856but also from every other object Abbreviation and from every other object
857"^DD",8925.1,8925.1,.01,21,49,0)
858Print Name. Same for Abbreviations and Print Names. For example, if some
859"^DD",8925.1,8925.1,.01,21,50,0)
860object has abbreviation 'CND', then 'CND' cannot be used for any other
861"^DD",8925.1,8925.1,.01,21,51,0)
862object Name, Abbreviation, or Print Name.
863"^DD",8925.1,8925.1,.01,"AUDIT")
864
865"^DD",8925.1,8925.1,.01,"DEL",.01,0)
866I 1
867"^DD",8925.1,8925.1,.01,"DT")
8683020107
869"^DD",8925.1,8925.1,.02,0)
870ABBREVIATION^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
871"^DD",8925.1,8925.1,.02,1,0)
872^.1
873"^DD",8925.1,8925.1,.02,1,1,0)
8748925.1^C
875"^DD",8925.1,8925.1,.02,1,1,1)
876S ^TIU(8925.1,"C",$E(X,1,30),DA)=""
877"^DD",8925.1,8925.1,.02,1,1,2)
878K ^TIU(8925.1,"C",$E(X,1,30),DA)
879"^DD",8925.1,8925.1,.02,1,1,"%D",0)
880^^2^2^2940711^
881"^DD",8925.1,8925.1,.02,1,1,"%D",1,0)
882This cross reference will be used by the router/filer to identify a given
883"^DD",8925.1,8925.1,.02,1,1,"%D",2,0)
884report type.
885"^DD",8925.1,8925.1,.02,1,1,"DT")
8862921020
887"^DD",8925.1,8925.1,.02,1,2,0)
8888925.1^ACL02^MUMPS
889"^DD",8925.1,8925.1,.02,1,2,1)
890D SACL^TIUDD1(X,.02)
891"^DD",8925.1,8925.1,.02,1,2,2)
892D KACL^TIUDD1(X,.02)
893"^DD",8925.1,8925.1,.02,1,2,"%D",0)
894^^2^2^3010417^
895"^DD",8925.1,8925.1,.02,1,2,"%D",1,0)
896This complex cross-reference by class and name will help optimize the
897"^DD",8925.1,8925.1,.02,1,2,"%D",2,0)
898title look-up for the GUI.
899"^DD",8925.1,8925.1,.02,1,2,"DT")
9003010417
901"^DD",8925.1,8925.1,.02,3)
902Enter from 2 to 4 letters. If OBJECT, Abbreviation must be unique among all object Names, Abbreviations, and Print Names, and must be uppercase.
903"^DD",8925.1,8925.1,.02,21,0)
904^^3^3^2990504^^^^
905"^DD",8925.1,8925.1,.02,21,1,0)
906Abbreviation can be entered at the Title: prompt when entering a document.
907"^DD",8925.1,8925.1,.02,21,2,0)
908Since all Titles with that abbreviation will then be listed, Abbreviation
909"^DD",8925.1,8925.1,.02,21,3,0)
910can serve to group Titles. BASIC Field. For Objects, see NAME.
911"^DD",8925.1,8925.1,.02,"DT")
9123020107
913"^DD",8925.1,8925.1,.03,0)
914PRINT 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
915"^DD",8925.1,8925.1,.03,1,0)
916^.1
917"^DD",8925.1,8925.1,.03,1,1,0)
9188925.1^AM1^MUMPS
919"^DD",8925.1,8925.1,.03,1,1,1)
920D REDO^TIUDD
921"^DD",8925.1,8925.1,.03,1,1,2)
922D REDO^TIUDD
923"^DD",8925.1,8925.1,.03,1,1,"%D",0)
924^^2^2^2950911^^^
925"^DD",8925.1,8925.1,.03,1,1,"%D",1,0)
926This MUMPS-type cross-reference is used to update the TIMESTAMP on both
927"^DD",8925.1,8925.1,.03,1,1,"%D",2,0)
928the current document, and its parents, when its PRINT NAME changes.
929"^DD",8925.1,8925.1,.03,1,1,"DT")
9302940720
931"^DD",8925.1,8925.1,.03,1,2,0)
9328925.1^D
933"^DD",8925.1,8925.1,.03,1,2,1)
934S ^TIU(8925.1,"D",$E(X,1,30),DA)=""
935"^DD",8925.1,8925.1,.03,1,2,2)
936K ^TIU(8925.1,"D",$E(X,1,30),DA)
937"^DD",8925.1,8925.1,.03,1,2,"%D",0)
938^^1^1^2950126^
939"^DD",8925.1,8925.1,.03,1,2,"%D",1,0)
940This REGULAR FileMan cross-reference by PRINT NAME will facilitate look-up.
941"^DD",8925.1,8925.1,.03,1,2,"DT")
9422950126
943"^DD",8925.1,8925.1,.03,1,3,0)
9448925.1^ACL03^MUMPS
945"^DD",8925.1,8925.1,.03,1,3,1)
946D SACL^TIUDD1(X,.03)
947"^DD",8925.1,8925.1,.03,1,3,2)
948D KACL^TIUDD1(X,.03)
949"^DD",8925.1,8925.1,.03,1,3,"%D",0)
950^^2^2^3010417^
951"^DD",8925.1,8925.1,.03,1,3,"%D",1,0)
952This complex cross-reference by class and name will help optimize the
953"^DD",8925.1,8925.1,.03,1,3,"%D",2,0)
954title look-up for the GUI.
955"^DD",8925.1,8925.1,.03,1,3,"DT")
9563010417
957"^DD",8925.1,8925.1,.03,3)
958Print 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.
959"^DD",8925.1,8925.1,.03,21,0)
960^^3^3^2990504^^^^
961"^DD",8925.1,8925.1,.03,21,1,0)
962Print Name is the name used in lists of documents. For entries of Type
963"^DD",8925.1,8925.1,.03,21,2,0)
964Title, Print Name is used as the document Title in the Patient Chart.
965"^DD",8925.1,8925.1,.03,21,3,0)
966BASIC field. For Objects, see NAME.
967"^DD",8925.1,8925.1,.03,"DT")
9683020107
969"^DD",8925.1,8925.1,.04,0)
970TYPE^RSX^CL:CLASS;DC:DOCUMENT CLASS;DOC:TITLE;CO:COMPONENT;O:OBJECT;^0;4^K:'$G(TIUFPRIV) X
971"^DD",8925.1,8925.1,.04,1,0)
972^.1
973"^DD",8925.1,8925.1,.04,1,1,0)
9748925.1^AT
975"^DD",8925.1,8925.1,.04,1,1,1)
976S ^TIU(8925.1,"AT",$E(X,1,30),DA)=""
977"^DD",8925.1,8925.1,.04,1,1,2)
978K ^TIU(8925.1,"AT",$E(X,1,30),DA)
979"^DD",8925.1,8925.1,.04,1,1,3)
980Please don't delete!
981"^DD",8925.1,8925.1,.04,1,1,"%D",0)
982^^2^2^2950615^
983"^DD",8925.1,8925.1,.04,1,1,"%D",1,0)
984This regular cross reference is used for listing Document Definitions by
985"^DD",8925.1,8925.1,.04,1,1,"%D",2,0)
986Type.
987"^DD",8925.1,8925.1,.04,1,1,"DT")
9882950615
989"^DD",8925.1,8925.1,.04,3)
990Types 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.
991"^DD",8925.1,8925.1,.04,4)
992
993"^DD",8925.1,8925.1,.04,21,0)
994^^99^99^2970521^^
995"^DD",8925.1,8925.1,.04,21,1,0)
996Type determines the nature of the entry and what sort of items the entry
997"^DD",8925.1,8925.1,.04,21,2,0)
998may have. There are 5 possible types:
999"^DD",8925.1,8925.1,.04,21,3,0)
1000
1001"^DD",8925.1,8925.1,.04,21,4,0)
1002CL CLASS: Classes group documents.
1003"^DD",8925.1,8925.1,.04,21,5,0)
1004
1005"^DD",8925.1,8925.1,.04,21,6,0)
1006Example: "Progress Notes" is a class with many kinds of progress notes
1007"^DD",8925.1,8925.1,.04,21,7,0)
1008under it.
1009"^DD",8925.1,8925.1,.04,21,8,0)
1010
1011"^DD",8925.1,8925.1,.04,21,9,0)
1012Classes may themselves be subdivided into items of Type Class or may have
1013"^DD",8925.1,8925.1,.04,21,10,0)
1014items of Type Document Class if no further Class subdivisions are desired.
1015"^DD",8925.1,8925.1,.04,21,11,0)
1016
1017"^DD",8925.1,8925.1,.04,21,12,0)
1018If a hierarchy deeper than Class-Document Class-Title is desired, Class is
1019"^DD",8925.1,8925.1,.04,21,13,0)
1020the place to insert another level into the hierarchy: Class-Class-Document
1021"^DD",8925.1,8925.1,.04,21,14,0)
1022Class-Title.
1023"^DD",8925.1,8925.1,.04,21,15,0)
1024
1025"^DD",8925.1,8925.1,.04,21,16,0)
1026Besides grouping documents, Classes also store behavior which is then
1027"^DD",8925.1,8925.1,.04,21,17,0)
1028inherited by lower level entries.
1029"^DD",8925.1,8925.1,.04,21,18,0)
1030
1031"^DD",8925.1,8925.1,.04,21,19,0)
1032DC DOCUMENT CLASS: Document Classes group documents. Document Class is
1033"^DD",8925.1,8925.1,.04,21,20,0)
1034the lowest level of class, and has items of Type Title under it.
1035"^DD",8925.1,8925.1,.04,21,21,0)
1036
1037"^DD",8925.1,8925.1,.04,21,22,0)
1038Example: "Day Pass Note" could be a Document Class under class Progress
1039"^DD",8925.1,8925.1,.04,21,23,0)
1040Note.
1041"^DD",8925.1,8925.1,.04,21,24,0)
1042
1043"^DD",8925.1,8925.1,.04,21,25,0)
1044Document Classes also store behavior which is then inherited by lower
1045"^DD",8925.1,8925.1,.04,21,26,0)
1046entries.
1047"^DD",8925.1,8925.1,.04,21,27,0)
1048
1049"^DD",8925.1,8925.1,.04,21,28,0)
1050TL TITLE: Titles are used to enter documents. They store the behavior
1051"^DD",8925.1,8925.1,.04,21,29,0)
1052of the documents which use them.
1053"^DD",8925.1,8925.1,.04,21,30,0)
1054
1055"^DD",8925.1,8925.1,.04,21,31,0)
1056Titles may have predefined boilerplate ("Overprint") text. They may have
1057"^DD",8925.1,8925.1,.04,21,32,0)
1058Components as items. Boilerplate Text can have objects in it.
1059"^DD",8925.1,8925.1,.04,21,33,0)
1060
1061"^DD",8925.1,8925.1,.04,21,34,0)
1062Examples: "Routine Day Pass Note" could be a Title under document class
1063"^DD",8925.1,8925.1,.04,21,35,0)
1064Day Pass Note. Another example might be "Exceptional Circumstances Day
1065"^DD",8925.1,8925.1,.04,21,36,0)
1066Pass Note."
1067"^DD",8925.1,8925.1,.04,21,37,0)
1068
1069"^DD",8925.1,8925.1,.04,21,38,0)
1070Titles store their own behavior. They also inherit behavior from higher
1071"^DD",8925.1,8925.1,.04,21,39,0)
1072levels of the hierarchy. However, behavior stored in the Title itself
1073"^DD",8925.1,8925.1,.04,21,40,0)
1074overrides inherited behavior.
1075"^DD",8925.1,8925.1,.04,21,41,0)
1076
1077"^DD",8925.1,8925.1,.04,21,42,0)
1078CO COMPONENT: Components are "sections" or "pieces" of documents.
1079"^DD",8925.1,8925.1,.04,21,43,0)
1080In the Hierarchy, Components are hung as items from Titles.
1081"^DD",8925.1,8925.1,.04,21,44,0)
1082
1083"^DD",8925.1,8925.1,.04,21,45,0)
1084Examples: "Reason for Pass" could be a component of Routine Day Pass Note.
1085"^DD",8925.1,8925.1,.04,21,46,0)
1086Subjective is a component of a SOAP Note.
1087"^DD",8925.1,8925.1,.04,21,47,0)
1088
1089"^DD",8925.1,8925.1,.04,21,48,0)
1090Components may have (sub)Components as items. They may have Boilerplate
1091"^DD",8925.1,8925.1,.04,21,49,0)
1092Text. Components may be designated Shared (see Field Description for
1093"^DD",8925.1,8925.1,.04,21,50,0)
1094Shared). Shared Components are shown in Document Definition Utility
1095"^DD",8925.1,8925.1,.04,21,51,0)
1096Displays as Type: 'CO S'.
1097"^DD",8925.1,8925.1,.04,21,52,0)
1098
1099"^DD",8925.1,8925.1,.04,21,53,0)
1100There are advantages and disadvantages in splitting a document up into
1101"^DD",8925.1,8925.1,.04,21,54,0)
1102separate components (rather than writing sections into the Boilerplate
1103"^DD",8925.1,8925.1,.04,21,55,0)
1104Text of the Title): Since Components are stored as separate file entries,
1105"^DD",8925.1,8925.1,.04,21,56,0)
1106they are inherently accessable and even 'moveable'. Using Fileman, sites
1107"^DD",8925.1,8925.1,.04,21,57,0)
1108can access components of documents the same way they can access documents
1109"^DD",8925.1,8925.1,.04,21,58,0)
1110for reports, etc.. Also, in the future, TIU may have options to move/copy
1111"^DD",8925.1,8925.1,.04,21,59,0)
1112certain components from one document into another. The disadvantage is
1113"^DD",8925.1,8925.1,.04,21,60,0)
1114speed: Components make the structure more complex and therefore slow down
1115"^DD",8925.1,8925.1,.04,21,61,0)
1116processing.
1117"^DD",8925.1,8925.1,.04,21,62,0)
1118
1119"^DD",8925.1,8925.1,.04,21,63,0)
1120O OBJECT: Objects are names which may be embedded in the predefined
1121"^DD",8925.1,8925.1,.04,21,64,0)
1122boilerplate text of Titles. Example: 'PATIENT AGE'. Objects are typed
1123"^DD",8925.1,8925.1,.04,21,65,0)
1124into the boilerplate text of a Title, enclosed by '|'s. For example,
1125"^DD",8925.1,8925.1,.04,21,66,0)
1126suppose a Title has boilerplate text:
1127"^DD",8925.1,8925.1,.04,21,67,0)
1128
1129"^DD",8925.1,8925.1,.04,21,68,0)
1130 Patient is a healthy |PATIENT AGE| year old male ...
1131"^DD",8925.1,8925.1,.04,21,69,0)
1132
1133"^DD",8925.1,8925.1,.04,21,70,0)
1134Then a user who enters such a note for a patient known by the system to be
1135"^DD",8925.1,8925.1,.04,21,71,0)
113656 years old would be presented with the text:
1137"^DD",8925.1,8925.1,.04,21,72,0)
1138
1139"^DD",8925.1,8925.1,.04,21,73,0)
1140 Patient is a healthy 56 year old male ...
1141"^DD",8925.1,8925.1,.04,21,74,0)
1142
1143"^DD",8925.1,8925.1,.04,21,75,0)
1144The user can then add to the text and or edit the text, including the age
1145"^DD",8925.1,8925.1,.04,21,76,0)
1146(56) of the patient. From this point on, the patient age (56) is regular
1147"^DD",8925.1,8925.1,.04,21,77,0)
1148text and is not updated in this note.
1149"^DD",8925.1,8925.1,.04,21,78,0)
1150
1151"^DD",8925.1,8925.1,.04,21,79,0)
1152Objects must always have uppercase names, abbreviations, and print names.
1153"^DD",8925.1,8925.1,.04,21,80,0)
1154When embedding objects in boilerplate text, users may embed any of these
1155"^DD",8925.1,8925.1,.04,21,81,0)
1156three (name, abbreviation, print name) in boilerplate text, enclosed by
1157"^DD",8925.1,8925.1,.04,21,82,0)
1158'|'s. Objects must always be embedded in uppercase.
1159"^DD",8925.1,8925.1,.04,21,83,0)
1160
1161"^DD",8925.1,8925.1,.04,21,84,0)
1162Objects are stored in the Document Definition File, but are not part of
1163"^DD",8925.1,8925.1,.04,21,85,0)
1164the Hierarchy. They are accessible through the Option Create Objects.
1165"^DD",8925.1,8925.1,.04,21,86,0)
1166(They are also accessible through the Option Sort Document Definitions, by
1167"^DD",8925.1,8925.1,.04,21,87,0)
1168selecting Sort by Type and selecting Type Object.)
1169"^DD",8925.1,8925.1,.04,21,88,0)
1170
1171"^DD",8925.1,8925.1,.04,21,89,0)
1172TIU exports a small library of objects. Sites can also create their own.
1173"^DD",8925.1,8925.1,.04,21,90,0)
1174
1175"^DD",8925.1,8925.1,.04,21,91,0)
1176Only an owner can edit an object and should do so only after consulting
1177"^DD",8925.1,8925.1,.04,21,92,0)
1178with others who use it. The object must be inactive for editing. It
1179"^DD",8925.1,8925.1,.04,21,93,0)
1180should be thoroughly tested. See Object Status, under Status.
1181"^DD",8925.1,8925.1,.04,21,94,0)
1182
1183"^DD",8925.1,8925.1,.04,21,95,0)
1184Entries of type Object cannot be changed to any other type. Entries of
1185"^DD",8925.1,8925.1,.04,21,96,0)
1186type Class, Document Class, Title, or Component cannot be changed to type
1187"^DD",8925.1,8925.1,.04,21,97,0)
1188Object.
1189"^DD",8925.1,8925.1,.04,21,98,0)
1190
1191"^DD",8925.1,8925.1,.04,21,99,0)
1192Type is a BASIC field.
1193"^DD",8925.1,8925.1,.04,"DT")
11942970114
1195"^DD",8925.1,8925.1,.05,0)
1196PERSONAL OWNER^P200'X^VA(200,^0;5^Q
1197"^DD",8925.1,8925.1,.05,1,0)
1198^.1
1199"^DD",8925.1,8925.1,.05,1,1,0)
12008925.1^AP
1201"^DD",8925.1,8925.1,.05,1,1,1)
1202S ^TIU(8925.1,"AP",$E(X,1,30),DA)=""
1203"^DD",8925.1,8925.1,.05,1,1,2)
1204K ^TIU(8925.1,"AP",$E(X,1,30),DA)
1205"^DD",8925.1,8925.1,.05,1,1,3)
1206Please don't delete!
1207"^DD",8925.1,8925.1,.05,1,1,"%D",0)
1208^^2^2^2950615^
1209"^DD",8925.1,8925.1,.05,1,1,"%D",1,0)
1210This regular cross reference is used for listing Document Definitions by
1211"^DD",8925.1,8925.1,.05,1,1,"%D",2,0)
1212Personal Owner.
1213"^DD",8925.1,8925.1,.05,1,1,"DT")
12142950615
1215"^DD",8925.1,8925.1,.05,3)
1216Enter 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.
1217"^DD",8925.1,8925.1,.05,4)
1218
1219"^DD",8925.1,8925.1,.05,21,0)
1220^^41^41^2970520^
1221"^DD",8925.1,8925.1,.05,21,1,0)
1222Document Definition Ownership has nothing to do with who can USE the entry
1223"^DD",8925.1,8925.1,.05,21,2,0)
1224to enter a document. It determines responsibilty for the Document
1225"^DD",8925.1,8925.1,.05,21,3,0)
1226Definition itself.
1227"^DD",8925.1,8925.1,.05,21,4,0)
1228
1229"^DD",8925.1,8925.1,.05,21,5,0)
1230An entry can be EDITED by its owner. (The Manager menu permits override of
1231"^DD",8925.1,8925.1,.05,21,6,0)
1232ownership so that Ownership can be assigned to a clinician who can then
1233"^DD",8925.1,8925.1,.05,21,7,0)
1234fill in boilerplate text with the Clinician menu, while the Manager can
1235"^DD",8925.1,8925.1,.05,21,8,0)
1236still edit the entry, since there are many fields the clinician does not
1237"^DD",8925.1,8925.1,.05,21,9,0)
1238have access to.) Exception: the Manager menu does NOT override ownership
1239"^DD",8925.1,8925.1,.05,21,10,0)
1240of Objects or of Shared Components. Only owners can edit Objects and
1241"^DD",8925.1,8925.1,.05,21,11,0)
1242Shared Components, regardless of menu.
1243"^DD",8925.1,8925.1,.05,21,12,0)
1244
1245"^DD",8925.1,8925.1,.05,21,13,0)
1246If Title owner edits the boilerplate text of the Title, that person can
1247"^DD",8925.1,8925.1,.05,21,14,0)
1248edit the boilerplate text of all components of the Title as well, without
1249"^DD",8925.1,8925.1,.05,21,15,0)
1250regard to component ownership. In order to edit components individually,
1251"^DD",8925.1,8925.1,.05,21,16,0)
1252however, the user must own the component. This allows users to assign
1253"^DD",8925.1,8925.1,.05,21,17,0)
1254ownership of components to different people, for example, for (future)
1255"^DD",8925.1,8925.1,.05,21,18,0)
1256multidisciplinary documents.
1257"^DD",8925.1,8925.1,.05,21,19,0)
1258
1259"^DD",8925.1,8925.1,.05,21,20,0)
1260A PERSONAL OWNER is a person who uniquely owns the entry. An entry may
1261"^DD",8925.1,8925.1,.05,21,21,0)
1262have a Personal Owner OR a Class Owner but not both. When entering a
1263"^DD",8925.1,8925.1,.05,21,22,0)
1264Personal Owner, be sure to delete any existing Class Owner.
1265"^DD",8925.1,8925.1,.05,21,23,0)
1266
1267"^DD",8925.1,8925.1,.05,21,24,0)
1268The Document Definition Utility TIUF uses the term 'Individual Owner'.
1269"^DD",8925.1,8925.1,.05,21,25,0)
1270Someone is an Individual Owner of an entry if s/he is the personal owner
1271"^DD",8925.1,8925.1,.05,21,26,0)
1272OR, if the entry is CLASS Owned, if s/he belongs to the Owner Class.
1273"^DD",8925.1,8925.1,.05,21,27,0)
1274
1275"^DD",8925.1,8925.1,.05,21,28,0)
1276The Document Definition Utility TIUF enters the user as the Personal Owner
1277"^DD",8925.1,8925.1,.05,21,29,0)
1278if a user enters a new entry without assigning ownership. This person can
1279"^DD",8925.1,8925.1,.05,21,30,0)
1280then reassign ownership if they choose.
1281"^DD",8925.1,8925.1,.05,21,31,0)
1282
1283"^DD",8925.1,8925.1,.05,21,32,0)
1284If the person responsible for an entry plays a role corresponding to a
1285"^DD",8925.1,8925.1,.05,21,33,0)
1286User Class, e.g. Clinical Coordinator, it may be more efficient to assign
1287"^DD",8925.1,8925.1,.05,21,34,0)
1288ownership to the class rather than to the person. Owners are then
1289"^DD",8925.1,8925.1,.05,21,35,0)
1290automatically updated as the class is updated.
1291"^DD",8925.1,8925.1,.05,21,36,0)
1292
1293"^DD",8925.1,8925.1,.05,21,37,0)
1294Editing privilege is affected not only by Owner but also by Status, by
1295"^DD",8925.1,8925.1,.05,21,38,0)
1296Shared, by In Use, and by menu. Manager menus, for example, provide
1297"^DD",8925.1,8925.1,.05,21,39,0)
1298fuller editing capabilities than Clinician menus.
1299"^DD",8925.1,8925.1,.05,21,40,0)
1300
1301"^DD",8925.1,8925.1,.05,21,41,0)
1302Personal Owner is a BASIC field.
1303"^DD",8925.1,8925.1,.05,"DT")
13042961022
1305"^DD",8925.1,8925.1,.06,0)
1306CLASS OWNER^P8930'X^USR(8930,^0;6^Q
1307"^DD",8925.1,8925.1,.06,1,0)
1308^.1
1309"^DD",8925.1,8925.1,.06,1,1,0)
13108925.1^AC
1311"^DD",8925.1,8925.1,.06,1,1,1)
1312S ^TIU(8925.1,"AC",$E(X,1,30),DA)=""
1313"^DD",8925.1,8925.1,.06,1,1,2)
1314K ^TIU(8925.1,"AC",$E(X,1,30),DA)
1315"^DD",8925.1,8925.1,.06,1,1,3)
1316Please don't delete!
1317"^DD",8925.1,8925.1,.06,1,1,"%D",0)
1318^^2^2^2950615^
1319"^DD",8925.1,8925.1,.06,1,1,"%D",1,0)
1320This regular cross reference is used to list Document Definitions by Class
1321"^DD",8925.1,8925.1,.06,1,1,"%D",2,0)
1322Owner.
1323"^DD",8925.1,8925.1,.06,1,1,"DT")
13242950615
1325"^DD",8925.1,8925.1,.06,3)
1326If 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.
1327"^DD",8925.1,8925.1,.06,4)
1328
1329"^DD",8925.1,8925.1,.06,21,0)
1330^^31^31^2970227^
1331"^DD",8925.1,8925.1,.06,21,1,0)
1332Document Definition Ownership has nothing to do with who can USE the entry
1333"^DD",8925.1,8925.1,.06,21,2,0)
1334to enter a document. It determines responsibility for the Document
1335"^DD",8925.1,8925.1,.06,21,3,0)
1336Definition itself.
1337"^DD",8925.1,8925.1,.06,21,4,0)
1338
1339"^DD",8925.1,8925.1,.06,21,5,0)
1340An entry can be EDITED by its owner. (The Manager menu permits override
1341"^DD",8925.1,8925.1,.06,21,6,0)
1342of ownership so that ownership can be assigned to a clinician (person with
1343"^DD",8925.1,8925.1,.06,21,7,0)
1344Clinician Menu) who can then fill in boilerplate text, while the manager
1345"^DD",8925.1,8925.1,.06,21,8,0)
1346can still edit the entry, since there are many fields the clinician does
1347"^DD",8925.1,8925.1,.06,21,9,0)
1348not have access to.) Exception: the Manager menu does NOT override
1349"^DD",8925.1,8925.1,.06,21,10,0)
1350ownership of Objects or of Shared Components. These can ONLY be edited by
1351"^DD",8925.1,8925.1,.06,21,11,0)
1352an owner, regardless of menu.
1353"^DD",8925.1,8925.1,.06,21,12,0)
1354
1355"^DD",8925.1,8925.1,.06,21,13,0)
1356If a Title owner edits the boilerplate text of the Title, that person can
1357"^DD",8925.1,8925.1,.06,21,14,0)
1358edit the boilerplate text of all components of the title as well, without
1359"^DD",8925.1,8925.1,.06,21,15,0)
1360regard to component ownership. However, the user must own the component
1361"^DD",8925.1,8925.1,.06,21,16,0)
1362in order to edit it individually, permitting separate ownership of
1363"^DD",8925.1,8925.1,.06,21,17,0)
1364components.
1365"^DD",8925.1,8925.1,.06,21,18,0)
1366
1367"^DD",8925.1,8925.1,.06,21,19,0)
1368A Class Owner is a User Class from the USR CLASS file whose members may
1369"^DD",8925.1,8925.1,.06,21,20,0)
1370edit the entry. An entry may have a Personal OR a Class Owner (not both).
1371"^DD",8925.1,8925.1,.06,21,21,0)
1372The Document Definition Utility TIUF does not prompt for Class Owner if
1373"^DD",8925.1,8925.1,.06,21,22,0)
1374the entry has a Personal Owner. To change to Class Owner, first delete
1375"^DD",8925.1,8925.1,.06,21,23,0)
1376the Personal Owner by entering '@' at the Personal Owner prompt.
1377"^DD",8925.1,8925.1,.06,21,24,0)
1378
1379"^DD",8925.1,8925.1,.06,21,25,0)
1380For new entries, users are prompted to enter the Class Owner Clinical
1381"^DD",8925.1,8925.1,.06,21,26,0)
1382Coordinator as the default. To enter a different Class Owner, enter the
1383"^DD",8925.1,8925.1,.06,21,27,0)
1384appropriate class after the //'s. If there are no //'s and the
1385"^DD",8925.1,8925.1,.06,21,28,0)
1386Replace...with editor is being used, enter ... to replace the whole
1387"^DD",8925.1,8925.1,.06,21,29,0)
1388class and then enter the appropriate class.
1389"^DD",8925.1,8925.1,.06,21,30,0)
1390
1391"^DD",8925.1,8925.1,.06,21,31,0)
1392Class Owner is a BASIC field.
1393"^DD",8925.1,8925.1,.06,"DT")
13942961022
1395"^DD",8925.1,8925.1,.07,0)
1396STATUS^*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
1397"^DD",8925.1,8925.1,.07,1,0)
1398^.1
1399"^DD",8925.1,8925.1,.07,1,1,0)
14008925.1^AS
1401"^DD",8925.1,8925.1,.07,1,1,1)
1402S ^TIU(8925.1,"AS",$E(X,1,30),DA)=""
1403"^DD",8925.1,8925.1,.07,1,1,2)
1404K ^TIU(8925.1,"AS",$E(X,1,30),DA)
1405"^DD",8925.1,8925.1,.07,1,1,3)
1406Please don't delete!
1407"^DD",8925.1,8925.1,.07,1,1,"%D",0)
1408^^2^2^2950615^
1409"^DD",8925.1,8925.1,.07,1,1,"%D",1,0)
1410This regular cross reference is used to list Document Definitions by
1411"^DD",8925.1,8925.1,.07,1,1,"%D",2,0)
1412Status.
1413"^DD",8925.1,8925.1,.07,1,1,"DT")
14142950615
1415"^DD",8925.1,8925.1,.07,1,2,0)
14168925.1^ACL07^MUMPS
1417"^DD",8925.1,8925.1,.07,1,2,1)
1418D SACL^TIUDD1(X,.07)
1419"^DD",8925.1,8925.1,.07,1,2,2)
1420D KACL^TIUDD1(X,.07)
1421"^DD",8925.1,8925.1,.07,1,2,"%D",0)
1422^^2^2^2971016^
1423"^DD",8925.1,8925.1,.07,1,2,"%D",1,0)
1424This MUMPS-type cross-reference on STATUS support the identification of
1425"^DD",8925.1,8925.1,.07,1,2,"%D",2,0)
1426Active and TEST Titles within a given class.
1427"^DD",8925.1,8925.1,.07,1,2,"DT")
14282971016
1429"^DD",8925.1,8925.1,.07,3)
1430 Documents can be entered on ACTIVE Titles. Only the Owner can enter a document on TEST Titles. Only INACTIVE Document Definitions can be edited.
1431"^DD",8925.1,8925.1,.07,4)
1432
1433"^DD",8925.1,8925.1,.07,12)
1434STATSCRN limits Status to Status file entries that are appropriate for Document Definitions: Active, Inactive, and Test.
1435"^DD",8925.1,8925.1,.07,12.1)
1436S DIC("S")="I 1 X $$STATSCRN^TIUFLF5"
1437"^DD",8925.1,8925.1,.07,21,0)
1438^^183^183^2990225^^^
1439"^DD",8925.1,8925.1,.07,21,1,0)
1440Status provides a way of making Document Definitions 'Offline' to
1441"^DD",8925.1,8925.1,.07,21,2,0)
1442documents. Document Definitions need to be 'Offline' if they are new and
1443"^DD",8925.1,8925.1,.07,21,3,0)
1444not ready for use, if they are being edited, or if they are retired from
1445"^DD",8925.1,8925.1,.07,21,4,0)
1446further use.
1447"^DD",8925.1,8925.1,.07,21,5,0)
1448
1449"^DD",8925.1,8925.1,.07,21,6,0)
1450Status is limited to those Statuses in the Status File which apply to
1451"^DD",8925.1,8925.1,.07,21,7,0)
1452Document Definitions: Inactive, Test, and Active. The Document Definition
1453"^DD",8925.1,8925.1,.07,21,8,0)
1454Utility TIUF further limits Statuses to those appropriate for the entry
1455"^DD",8925.1,8925.1,.07,21,9,0)
1456Type (see below), limits the Status of entries with Inactive ancestors to
1457"^DD",8925.1,8925.1,.07,21,10,0)
1458Inactive, and limits the Status of faulty entries to Inactive.
1459"^DD",8925.1,8925.1,.07,21,11,0)
1460
1461"^DD",8925.1,8925.1,.07,21,12,0)
1462Status applies to all Document Definitions, but its meaning and possible
1463"^DD",8925.1,8925.1,.07,21,13,0)
1464values vary somewhat with the Document Definition Type. Exception: Shared
1465"^DD",8925.1,8925.1,.07,21,14,0)
1466Components: See COMPONENT STATUS, below.
1467"^DD",8925.1,8925.1,.07,21,15,0)
1468
1469"^DD",8925.1,8925.1,.07,21,16,0)
1470Status is a BASIC field.
1471"^DD",8925.1,8925.1,.07,21,17,0)
1472
1473"^DD",8925.1,8925.1,.07,21,18,0)
1474 TITLE STATUS
1475"^DD",8925.1,8925.1,.07,21,19,0)
1476
1477"^DD",8925.1,8925.1,.07,21,20,0)
1478Status has its most basic meaning for Titles [Document Definitions of Type
1479"^DD",8925.1,8925.1,.07,21,21,0)
1480Title]:
1481"^DD",8925.1,8925.1,.07,21,22,0)
1482
1483"^DD",8925.1,8925.1,.07,21,23,0)
1484A Title can have Status Inactive, Test, or Active. If it has Status
1485"^DD",8925.1,8925.1,.07,21,24,0)
1486Inactive, it cannot be used to enter documents (EXCEPT through the
1487"^DD",8925.1,8925.1,.07,21,25,0)
1488Try Action, which deletes the document when done). If it has Status
1489"^DD",8925.1,8925.1,.07,21,26,0)
1490Test, it can be used to enter documents only by its Owner. Titles should
1491"^DD",8925.1,8925.1,.07,21,27,0)
1492be tested (and Tried) using TEST PATIENTS ONLY. If a Title has Status
1493"^DD",8925.1,8925.1,.07,21,28,0)
1494Active, it can be used to enter documents by any one with access and
1495"^DD",8925.1,8925.1,.07,21,29,0)
1496authorization.
1497"^DD",8925.1,8925.1,.07,21,30,0)
1498
1499"^DD",8925.1,8925.1,.07,21,31,0)
1500 ***************
1501"^DD",8925.1,8925.1,.07,21,32,0)
1502NOTE on Availability of Titles for entering documents:
1503"^DD",8925.1,8925.1,.07,21,33,0)
1504Although Status affects availability for entering documents, there are
1505"^DD",8925.1,8925.1,.07,21,34,0)
1506other factors which also affect availability: A Document Definition is not
1507"^DD",8925.1,8925.1,.07,21,35,0)
1508available to a given user for entering documents (excepting the Document
1509"^DD",8925.1,8925.1,.07,21,36,0)
1510Definition Utility Try Action) unless all of the following 3 criteria are
1511"^DD",8925.1,8925.1,.07,21,37,0)
1512met:
1513"^DD",8925.1,8925.1,.07,21,38,0)
1514
1515"^DD",8925.1,8925.1,.07,21,39,0)
1516 1) It is a Document Definition of Type Title.
1517"^DD",8925.1,8925.1,.07,21,40,0)
1518
1519"^DD",8925.1,8925.1,.07,21,41,0)
1520 2) It has Status Active or Test. If it has Status Test, the user
1521"^DD",8925.1,8925.1,.07,21,42,0)
1522entering a document must own the Title.
1523"^DD",8925.1,8925.1,.07,21,43,0)
1524
1525"^DD",8925.1,8925.1,.07,21,44,0)
1526 3) If authorization for using the Title to enter documents is restricted
1527"^DD",8925.1,8925.1,.07,21,45,0)
1528by Business Rules, the user must be a member of the authorized user
1529"^DD",8925.1,8925.1,.07,21,46,0)
1530class.
1531"^DD",8925.1,8925.1,.07,21,47,0)
1532
1533"^DD",8925.1,8925.1,.07,21,48,0)
1534Unless these criteria are all met, users trying to enter documents will
1535"^DD",8925.1,8925.1,.07,21,49,0)
1536not SEE the Document Definition. Therefore it is wise to warn users when
1537"^DD",8925.1,8925.1,.07,21,50,0)
1538taking definitions offline for edit, and/or to do so at nonpeak hours for
1539"^DD",8925.1,8925.1,.07,21,51,0)
1540entering documents.
1541"^DD",8925.1,8925.1,.07,21,52,0)
1542
1543"^DD",8925.1,8925.1,.07,21,53,0)
1544The above description applies to document entry BOTH manually through
1545"^DD",8925.1,8925.1,.07,21,54,0)
1546menu options AND via upload. It does NOT apply to autoentry of documents
1547"^DD",8925.1,8925.1,.07,21,55,0)
1548via the TIU application interface. Adverse Reaction/Allergy notes entered
1549"^DD",8925.1,8925.1,.07,21,56,0)
1550by the Allergy package are an example of such autoentry. The TIU
1551"^DD",8925.1,8925.1,.07,21,57,0)
1552application interface for autoentering documents disregards Title status
1553"^DD",8925.1,8925.1,.07,21,58,0)
1554and Business Rules.
1555"^DD",8925.1,8925.1,.07,21,59,0)
1556 *******************
1557"^DD",8925.1,8925.1,.07,21,60,0)
1558
1559"^DD",8925.1,8925.1,.07,21,61,0)
1560When being upgraded to Status Active or Test, a Title is examined for
1561"^DD",8925.1,8925.1,.07,21,62,0)
1562rudimentary completeness and must be judged OK before the upgrade takes
1563"^DD",8925.1,8925.1,.07,21,63,0)
1564place. If desired, users can perform the same examination themselves by
1565"^DD",8925.1,8925.1,.07,21,64,0)
1566selecting action TRY. For Titles, Action TRY also permits the user to
1567"^DD",8925.1,8925.1,.07,21,65,0)
1568enter a document on the entry. The document is deleted immediately after
1569"^DD",8925.1,8925.1,.07,21,66,0)
1570the trial.
1571"^DD",8925.1,8925.1,.07,21,67,0)
1572
1573"^DD",8925.1,8925.1,.07,21,68,0)
1574Availability for entering documents is the central meaning of Status.
1575"^DD",8925.1,8925.1,.07,21,69,0)
1576However, Status also controls edit/deletion of Document Definitions: A
1577"^DD",8925.1,8925.1,.07,21,70,0)
1578Title can be edited ONLY if it has Status Inactive, ensuring that no one
1579"^DD",8925.1,8925.1,.07,21,71,0)
1580is using it to enter a document while its behavior is changing. Titles
1581"^DD",8925.1,8925.1,.07,21,72,0)
1582can be deleted only with Status Inactive.
1583"^DD",8925.1,8925.1,.07,21,73,0)
1584
1585"^DD",8925.1,8925.1,.07,21,74,0)
1586NOTE: Although Status affects Editing ability, it is not the only factor
1587"^DD",8925.1,8925.1,.07,21,75,0)
1588affecting editing: If an entry is already IN USE by documents,
1589"^DD",8925.1,8925.1,.07,21,76,0)
1590editing/deletion is restricted to aspects which will not harm existing
1591"^DD",8925.1,8925.1,.07,21,77,0)
1592TIU documents.
1593"^DD",8925.1,8925.1,.07,21,78,0)
1594
1595"^DD",8925.1,8925.1,.07,21,79,0)
1596Components under a Title have the same status as the Title: When a Title's
1597"^DD",8925.1,8925.1,.07,21,80,0)
1598status is changed, the statuses of its descendant Components are
1599"^DD",8925.1,8925.1,.07,21,81,0)
1600automatically changed with it. (Shared Components are an exception: see
1601"^DD",8925.1,8925.1,.07,21,82,0)
1602COMPONENT STATUS, below.)
1603"^DD",8925.1,8925.1,.07,21,83,0)
1604
1605"^DD",8925.1,8925.1,.07,21,84,0)
1606 CLASS/DOCUMENT CLASS STATUS
1607"^DD",8925.1,8925.1,.07,21,85,0)
1608
1609"^DD",8925.1,8925.1,.07,21,86,0)
1610A Document Definition of Type Class or Document Class can have Status
1611"^DD",8925.1,8925.1,.07,21,87,0)
1612Inactive or Active.
1613"^DD",8925.1,8925.1,.07,21,88,0)
1614
1615"^DD",8925.1,8925.1,.07,21,89,0)
1616Basics for a Class or Document Class cannot be edited (except for Owner
1617"^DD",8925.1,8925.1,.07,21,90,0)
1618and Status) unless it is Inactive. Since Inactivating a Class/Document
1619"^DD",8925.1,8925.1,.07,21,91,0)
1620Class automatically inactivates its descendants, this ensures that all
1621"^DD",8925.1,8925.1,.07,21,92,0)
1622Titles which inherit behavior from it are neither Active nor Test, and are
1623"^DD",8925.1,8925.1,.07,21,93,0)
1624thus 'Offline' while inherited behavior is edited.
1625"^DD",8925.1,8925.1,.07,21,94,0)
1626
1627"^DD",8925.1,8925.1,.07,21,95,0)
1628In contrast to Basics, the ability to add/edit ITEMS of a Class/Document
1629"^DD",8925.1,8925.1,.07,21,96,0)
1630Class depends on the Status of the item, not the parent: it is NOT
1631"^DD",8925.1,8925.1,.07,21,97,0)
1632necessary to Inactivate a Class such as Progress Notes in order to
1633"^DD",8925.1,8925.1,.07,21,98,0)
1634edit/add items.
1635"^DD",8925.1,8925.1,.07,21,99,0)
1636
1637"^DD",8925.1,8925.1,.07,21,100,0)
1638Activating a Class/Document Class differs from Inactivating the
1639"^DD",8925.1,8925.1,.07,21,101,0)
1640Class/Document Class: When a Class/Document Class is ACTIVATED, its
1641"^DD",8925.1,8925.1,.07,21,102,0)
1642descendants may have any Status which their Type permits: they are not
1643"^DD",8925.1,8925.1,.07,21,103,0)
1644REQUIRED to be Active. Hence, they are not automatically Activated when
1645"^DD",8925.1,8925.1,.07,21,104,0)
1646the parent is Activated.
1647"^DD",8925.1,8925.1,.07,21,105,0)
1648
1649"^DD",8925.1,8925.1,.07,21,106,0)
1650 COMPONENT STATUS
1651"^DD",8925.1,8925.1,.07,21,107,0)
1652
1653"^DD",8925.1,8925.1,.07,21,108,0)
1654A Document Definition of Type Component has the same status as its parent:
1655"^DD",8925.1,8925.1,.07,21,109,0)
1656Its status can be changed only by changing the Status of its Parent, if it
1657"^DD",8925.1,8925.1,.07,21,110,0)
1658has one. Components without parents are always Inactive.
1659"^DD",8925.1,8925.1,.07,21,111,0)
1660
1661"^DD",8925.1,8925.1,.07,21,112,0)
1662NOTE: The above implies that Test or Active Titles cannot have Inactive
1663"^DD",8925.1,8925.1,.07,21,113,0)
1664Components. In other words, Inactivating a Component is NOT a way of
1665"^DD",8925.1,8925.1,.07,21,114,0)
1666retiring it. If a Component is no longer a useful section of a Title, it
1667"^DD",8925.1,8925.1,.07,21,115,0)
1668should be edited so as to make it useful, or it should be deleted AS AN
1669"^DD",8925.1,8925.1,.07,21,116,0)
1670ITEM from the Title of which it is a part. As with all retired Document
1671"^DD",8925.1,8925.1,.07,21,117,0)
1672Definitions, it should NOT be deleted FROM THE FILE if it has been used by
1673"^DD",8925.1,8925.1,.07,21,118,0)
1674documents.
1675"^DD",8925.1,8925.1,.07,21,119,0)
1676
1677"^DD",8925.1,8925.1,.07,21,120,0)
1678Components can be edited only if they have status Inactive. This ensures
1679"^DD",8925.1,8925.1,.07,21,121,0)
1680that all Titles using them are offline while the components are being
1681"^DD",8925.1,8925.1,.07,21,122,0)
1682edited.
1683"^DD",8925.1,8925.1,.07,21,123,0)
1684
1685"^DD",8925.1,8925.1,.07,21,124,0)
1686Shared Components are a special case since they can have multiple parents.
1687"^DD",8925.1,8925.1,.07,21,125,0)
1688They DO NOT HAVE A STATUS. They can be edited only when all parent Titles
1689"^DD",8925.1,8925.1,.07,21,126,0)
1690have Status Inactive. (The Detailed Display screen shows parents.) This
1691"^DD",8925.1,8925.1,.07,21,127,0)
1692ensures that all parent Titles of Shared Components are offline while the
1693"^DD",8925.1,8925.1,.07,21,128,0)
1694component is being edited. Edit of Shared Components is permitted only
1695"^DD",8925.1,8925.1,.07,21,129,0)
1696through the Option Sort Document Definitions.
1697"^DD",8925.1,8925.1,.07,21,130,0)
1698
1699"^DD",8925.1,8925.1,.07,21,131,0)
1700Edit of Shared Components is severely restricted by Ownership, since they
1701"^DD",8925.1,8925.1,.07,21,132,0)
1702may be used multiple times and across the site. Even an Inactive Status
1703"^DD",8925.1,8925.1,.07,21,133,0)
1704does not permit a manager (person with Manager menu) to override ownership
1705"^DD",8925.1,8925.1,.07,21,134,0)
1706and edit a Shared Component they don't own. See Shared Components, under
1707"^DD",8925.1,8925.1,.07,21,135,0)
1708Description of Type. See Description of Shared.
1709"^DD",8925.1,8925.1,.07,21,136,0)
1710
1711"^DD",8925.1,8925.1,.07,21,137,0)
1712 OBJECT STATUS
1713"^DD",8925.1,8925.1,.07,21,138,0)
1714
1715"^DD",8925.1,8925.1,.07,21,139,0)
1716Document Definitions of Type Object have Status Inactive or Active.
1717"^DD",8925.1,8925.1,.07,21,140,0)
1718
1719"^DD",8925.1,8925.1,.07,21,141,0)
1720Only ACTIVE objects function. That is, if a user enters a document on a
1721"^DD",8925.1,8925.1,.07,21,142,0)
1722Title with boilerplate text containing an inactive object, the object
1723"^DD",8925.1,8925.1,.07,21,143,0)
1724doesn't do anything; the user sees the name of the object and an error
1725"^DD",8925.1,8925.1,.07,21,144,0)
1726message in place of the object data.
1727"^DD",8925.1,8925.1,.07,21,145,0)
1728
1729"^DD",8925.1,8925.1,.07,21,146,0)
1730Only ACTIVE objects should be embedded in boilerplate text. Exception:
1731"^DD",8925.1,8925.1,.07,21,147,0)
1732owners who are creating/editing objects. Others should NOT embed inactive
1733"^DD",8925.1,8925.1,.07,21,148,0)
1734objects in boilerplate text since they may not be ready for use and since
1735"^DD",8925.1,8925.1,.07,21,149,0)
1736they do not function when users enter documents against them. Titles whose
1737"^DD",8925.1,8925.1,.07,21,150,0)
1738boilerplate text contains inactive objects cannot be activated. (This
1739"^DD",8925.1,8925.1,.07,21,151,0)
1740does NOT imply that active titles never have inactive objects embedded in
1741"^DD",8925.1,8925.1,.07,21,152,0)
1742them since users can, after a warning, inactivate objects even when they
1743"^DD",8925.1,8925.1,.07,21,153,0)
1744are embedded in active titles.)
1745"^DD",8925.1,8925.1,.07,21,154,0)
1746
1747"^DD",8925.1,8925.1,.07,21,155,0)
1748Only INACTIVE objects can be edited (and only by an owner). Only an owner
1749"^DD",8925.1,8925.1,.07,21,156,0)
1750can activate/inactivate an object. (Exception: if a user owns an object
1751"^DD",8925.1,8925.1,.07,21,157,0)
1752and edits the owner to someone else, the user is not prevented from going
1753"^DD",8925.1,8925.1,.07,21,158,0)
1754on to edit the status in the same edit session since they WERE the owner a
1755"^DD",8925.1,8925.1,.07,21,159,0)
1756few seconds ago.) Active objects are assumed to be ready for use in any
1757"^DD",8925.1,8925.1,.07,21,160,0)
1758boilerplate text.
1759"^DD",8925.1,8925.1,.07,21,161,0)
1760
1761"^DD",8925.1,8925.1,.07,21,162,0)
1762Since the owner is essentially caretaker of the object for the entire
1763"^DD",8925.1,8925.1,.07,21,163,0)
1764site, the owner should consult with all who use it before editing it. An
1765"^DD",8925.1,8925.1,.07,21,164,0)
1766object can be tested by embedding it in the boilerplate text of a Title
1767"^DD",8925.1,8925.1,.07,21,165,0)
1768and selecting action Try for the Title. It need not have status Active
1769"^DD",8925.1,8925.1,.07,21,166,0)
1770for this testing (and SHOULD not have status Active until testing is
1771"^DD",8925.1,8925.1,.07,21,167,0)
1772complete). Owners who inactivate objects for editing should make SURE to
1773"^DD",8925.1,8925.1,.07,21,168,0)
1774reactivate them if they are being used.
1775"^DD",8925.1,8925.1,.07,21,169,0)
1776
1777"^DD",8925.1,8925.1,.07,21,170,0)
1778Sites should either inactivate relevant Titles before editing objects or
1779"^DD",8925.1,8925.1,.07,21,171,0)
1780edit objects only when users are not likely to be ENTERING documents since
1781"^DD",8925.1,8925.1,.07,21,172,0)
1782Inactive objects do not function.
1783"^DD",8925.1,8925.1,.07,21,173,0)
1784
1785"^DD",8925.1,8925.1,.07,21,174,0)
1786If a site changes the name or behavior of an Object, it is up to the SITE
1787"^DD",8925.1,8925.1,.07,21,175,0)
1788to change the name wherever it has already been embedded in Boilerplate
1789"^DD",8925.1,8925.1,.07,21,176,0)
1790Text, and to inform users of the change.
1791"^DD",8925.1,8925.1,.07,21,177,0)
1792
1793"^DD",8925.1,8925.1,.07,21,178,0)
1794An object which is no longer wanted for future documents can be removed
1795"^DD",8925.1,8925.1,.07,21,179,0)
1796from the boilerplate text of all Titles and Components and then deleted
1797"^DD",8925.1,8925.1,.07,21,180,0)
1798from file 8925.1. Only an owner can delete it. All of the documents that
1799"^DD",8925.1,8925.1,.07,21,181,0)
1800used it have already got it in hard words so there is no need to keep it
1801"^DD",8925.1,8925.1,.07,21,182,0)
1802for their sake. Old Objects should be edited so they are useful or
1803"^DD",8925.1,8925.1,.07,21,183,0)
1804deleted, not kept around forever as Inactive.
1805"^DD",8925.1,8925.1,.07,"DT")
18062971016
1807"^DD",8925.1,8925.1,.08,0)
1808IN USE^CJ6^^ ; ^S X=$S($L($T(^TIUFLF)):$$DDEFUSED^TIUFLF(D0),1:"?")
1809"^DD",8925.1,8925.1,.08,.1)
1810
1811"^DD",8925.1,8925.1,.08,9)
1812^
1813"^DD",8925.1,8925.1,.08,9.01)
1814
1815"^DD",8925.1,8925.1,.08,9.1)
1816S X=$S($L($T(^TIUFLF)):$$DDEFUSED^TIUFLF(D0),1:"?")
1817"^DD",8925.1,8925.1,.08,21,0)
1818^^55^55^2970125^
1819"^DD",8925.1,8925.1,.08,21,1,0)
1820IN USE applies to all entries except those of Type Object. It cannot be
1821"^DD",8925.1,8925.1,.08,21,2,0)
1822edited since it gets its value automatically.
1823"^DD",8925.1,8925.1,.08,21,3,0)
1824
1825"^DD",8925.1,8925.1,.08,21,4,0)
1826IN USE may have values 'Yes', 'No', or '?'.
1827"^DD",8925.1,8925.1,.08,21,5,0)
1828
1829"^DD",8925.1,8925.1,.08,21,6,0)
1830A Document Definition of Type Title or Component is In Use (Yes) if there
1831"^DD",8925.1,8925.1,.08,21,7,0)
1832are entries IN THE TIU DOCUMENT file which store it as their Document
1833"^DD",8925.1,8925.1,.08,21,8,0)
1834Definition. If not, it is NOT used (No).
1835"^DD",8925.1,8925.1,.08,21,9,0)
1836
1837"^DD",8925.1,8925.1,.08,21,10,0)
1838NOTE: It is possible for Document Definitions to be used by documents in
1839"^DD",8925.1,8925.1,.08,21,11,0)
1840files other than the TIU Document file and still be NOT In Use since In
1841"^DD",8925.1,8925.1,.08,21,12,0)
1842Use means in use by documents in the TIU Document Definition file. See
1843"^DD",8925.1,8925.1,.08,21,13,0)
1844Warning, below.
1845"^DD",8925.1,8925.1,.08,21,14,0)
1846
1847"^DD",8925.1,8925.1,.08,21,15,0)
1848A Document Definition of Type Class or Document Class is In Use (Yes) if
1849"^DD",8925.1,8925.1,.08,21,16,0)
1850it has children of Type Title which are In Use. That is, it is Used by
1851"^DD",8925.1,8925.1,.08,21,17,0)
1852Documents (Yes) if there are entries in the TIU Document file which
1853"^DD",8925.1,8925.1,.08,21,18,0)
1854inherit behavior from it. If not, it is NOT used (No).
1855"^DD",8925.1,8925.1,.08,21,19,0)
1856
1857"^DD",8925.1,8925.1,.08,21,20,0)
1858IN USE has value '?' for a Document Definition File entry if routine
1859"^DD",8925.1,8925.1,.08,21,21,0)
1860TIUFLF is missing or if the program encounters a nonexistent item and the
1861"^DD",8925.1,8925.1,.08,21,22,0)
1862entry is not In Use so far as the check has been able to go.
1863"^DD",8925.1,8925.1,.08,21,23,0)
1864
1865"^DD",8925.1,8925.1,.08,21,24,0)
1866Note: Since Shared Components can be items of more than one Title, a
1867"^DD",8925.1,8925.1,.08,21,25,0)
1868Shared Component may be In Use even when a particular parent Title is
1869"^DD",8925.1,8925.1,.08,21,26,0)
1870NOT In Use. This simply means that it is also a Component of another
1871"^DD",8925.1,8925.1,.08,21,27,0)
1872Title which IS In Use.
1873"^DD",8925.1,8925.1,.08,21,28,0)
1874
1875"^DD",8925.1,8925.1,.08,21,29,0)
1876If IN USE has the explicit value 'No' for a particular Document Definition
1877"^DD",8925.1,8925.1,.08,21,30,0)
1878entry, the entry can be deleted by the Owner without harming documents IN
1879"^DD",8925.1,8925.1,.08,21,31,0)
1880TIU DOCUMENT FILE 8925. Deleting it will, however, orphan any descendant
1881"^DD",8925.1,8925.1,.08,21,32,0)
1882Document Definitions.
1883"^DD",8925.1,8925.1,.08,21,33,0)
1884
1885"^DD",8925.1,8925.1,.08,21,34,0)
1886WARNING: If a site is using TIU to upload documents into a file other than
1887"^DD",8925.1,8925.1,.08,21,35,0)
1888the TIU Document file, it may create Document Definition entries to store
1889"^DD",8925.1,8925.1,.08,21,36,0)
1890upload information. For example, it may create an Operative Reports title
1891"^DD",8925.1,8925.1,.08,21,37,0)
1892containing instructions for uploading documents into the Surgery file.
1893"^DD",8925.1,8925.1,.08,21,38,0)
1894These document definitions will be orphans and will be NOT In Use, since
1895"^DD",8925.1,8925.1,.08,21,39,0)
1896documents using them are not stored in the TIU Document file. They must
1897"^DD",8925.1,8925.1,.08,21,40,0)
1898NOT be deleted from the Document Definition file.
1899"^DD",8925.1,8925.1,.08,21,41,0)
1900
1901"^DD",8925.1,8925.1,.08,21,42,0)
1902Note: Deleting Objects will not harm existing documents, but WILL HARM
1903"^DD",8925.1,8925.1,.08,21,43,0)
1904future documents if the Object is embedded in existing Document Definition
1905"^DD",8925.1,8925.1,.08,21,44,0)
1906Boilerplate Text.
1907"^DD",8925.1,8925.1,.08,21,45,0)
1908
1909"^DD",8925.1,8925.1,.08,21,46,0)
1910If IN USE has value 'Yes' or '?', the Document Definition Utility TIUF
1911"^DD",8925.1,8925.1,.08,21,47,0)
1912does not permit the entry to be deleted. Deleting the entry would cause
1913"^DD",8925.1,8925.1,.08,21,48,0)
1914documents in file 8925 not to function. This is true even if the entry
1915"^DD",8925.1,8925.1,.08,21,49,0)
1916has status 'Inactive' and documents are no longer being written on the
1917"^DD",8925.1,8925.1,.08,21,50,0)
1918entry.
1919"^DD",8925.1,8925.1,.08,21,51,0)
1920
1921"^DD",8925.1,8925.1,.08,21,52,0)
1922Technical Note: A Document Definition of Type Title or Component is IN
1923"^DD",8925.1,8925.1,.08,21,53,0)
1924USE if and only if it appears in file 8925's 'B' Cross Reference.
1925"^DD",8925.1,8925.1,.08,21,54,0)
1926
1927"^DD",8925.1,8925.1,.08,21,55,0)
1928In Use is a BASIC field.
1929"^DD",8925.1,8925.1,.08,"DT")
19302960618
1931"^DD",8925.1,8925.1,.1,0)
1932SHARED^SX^1:YES;0:NO;^0;10^K:'$G(TIUFPRIV) X
1933"^DD",8925.1,8925.1,.1,.1)
1934SHARED COMPONENT
1935"^DD",8925.1,8925.1,.1,3)
1936Enter 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.
1937"^DD",8925.1,8925.1,.1,21,0)
1938^^48^48^2970220^
1939"^DD",8925.1,8925.1,.1,21,1,0)
1940Applies to entries of Type Component only.
1941"^DD",8925.1,8925.1,.1,21,2,0)
1942
1943"^DD",8925.1,8925.1,.1,21,3,0)
1944Document Definitions of Type Component may be designated SHARED by Owners
1945"^DD",8925.1,8925.1,.1,21,4,0)
1946who have the Manager menu. This means the Component can be an item under
1947"^DD",8925.1,8925.1,.1,21,5,0)
1948multiple parents, and any user who owns a Title can add it as an item.
1949"^DD",8925.1,8925.1,.1,21,6,0)
1950
1951"^DD",8925.1,8925.1,.1,21,7,0)
1952Shared Components are the ONLY members of the Document Definition
1953"^DD",8925.1,8925.1,.1,21,8,0)
1954hierarchy which can appear in more than one place in the hierarchy.
1955"^DD",8925.1,8925.1,.1,21,9,0)
1956(Objects can be used in multiple entries, but are not members of the
1957"^DD",8925.1,8925.1,.1,21,10,0)
1958hierarchy.)
1959"^DD",8925.1,8925.1,.1,21,11,0)
1960
1961"^DD",8925.1,8925.1,.1,21,12,0)
1962Shared Components are intended for broad use across the site. An example
1963"^DD",8925.1,8925.1,.1,21,13,0)
1964might be a Privacy Act Component. Since a Shared Component may be used in
1965"^DD",8925.1,8925.1,.1,21,14,0)
1966many different Document Definitions, its Owner is essentially caretaker
1967"^DD",8925.1,8925.1,.1,21,15,0)
1968for it, hospital wide, and must take into account all users before editing
1969"^DD",8925.1,8925.1,.1,21,16,0)
1970it. Users who disagree with a proposed change can opt to create and use
1971"^DD",8925.1,8925.1,.1,21,17,0)
1972their own copy instead of using the Shared Component.
1973"^DD",8925.1,8925.1,.1,21,18,0)
1974
1975"^DD",8925.1,8925.1,.1,21,19,0)
1976Parents of a Shared Component are listed in the Detailed Display Screen.
1977"^DD",8925.1,8925.1,.1,21,20,0)
1978
1979"^DD",8925.1,8925.1,.1,21,21,0)
1980Shared Field values are 1 for YES and 0 for NO, with a default value of
1981"^DD",8925.1,8925.1,.1,21,22,0)
19820 for NO if the field is empty.
1983"^DD",8925.1,8925.1,.1,21,23,0)
1984
1985"^DD",8925.1,8925.1,.1,21,24,0)
1986An entry may not be designated Shared unless it is of Type Component. Only
1987"^DD",8925.1,8925.1,.1,21,25,0)
1988a Manager (person with Manager menu) and only an Owner can designate a
1989"^DD",8925.1,8925.1,.1,21,26,0)
1990Component as Shared. Only an OWNER can edit it. (Normally Managers can
1991"^DD",8925.1,8925.1,.1,21,27,0)
1992override ownership and edit entries. Manager Options do NOT override
1993"^DD",8925.1,8925.1,.1,21,28,0)
1994Ownership for editing Shared Components). Shared Components can only be
1995"^DD",8925.1,8925.1,.1,21,29,0)
1996edited from the Sort Document Definitions Option.
1997"^DD",8925.1,8925.1,.1,21,30,0)
1998
1999"^DD",8925.1,8925.1,.1,21,31,0)
2000Shared Components cannot be deleted. If they do not have multiple
2001"^DD",8925.1,8925.1,.1,21,32,0)
2002parents, they can, however, be edited to NOT shared and THEN deleted,
2003"^DD",8925.1,8925.1,.1,21,33,0)
2004assuming they are not In Use by documents and the parent is Inactive.
2005"^DD",8925.1,8925.1,.1,21,34,0)
2006
2007"^DD",8925.1,8925.1,.1,21,35,0)
2008Shared Components do NOT HAVE a Status. They can be edited only if all
2009"^DD",8925.1,8925.1,.1,21,36,0)
2010parent Titles are Inactive. This ensures that parent Titles are offline
2011"^DD",8925.1,8925.1,.1,21,37,0)
2012for entering documents while their components are being edited. Parents
2013"^DD",8925.1,8925.1,.1,21,38,0)
2014are listed on the Detailed Display Screen.
2015"^DD",8925.1,8925.1,.1,21,39,0)
2016
2017"^DD",8925.1,8925.1,.1,21,40,0)
2018If a Shared Component has subcomponents, they are automatically Shared,
2019"^DD",8925.1,8925.1,.1,21,41,0)
2020since they, with their parents, can be used in more than one place in the
2021"^DD",8925.1,8925.1,.1,21,42,0)
2022hierarchy.
2023"^DD",8925.1,8925.1,.1,21,43,0)
2024
2025"^DD",8925.1,8925.1,.1,21,44,0)
2026Sharing of Document Definitions other than Components is not permitted
2027"^DD",8925.1,8925.1,.1,21,45,0)
2028because it unduly restricts the owner's right to edit/delete the Document
2029"^DD",8925.1,8925.1,.1,21,46,0)
2030Definition and adds undue complexity to the Hierarchy.
2031"^DD",8925.1,8925.1,.1,21,47,0)
2032
2033"^DD",8925.1,8925.1,.1,21,48,0)
2034Shared is a BASIC field.
2035"^DD",8925.1,8925.1,.1,"DT")
20362961022
2037"^DD",8925.1,8925.1,.11,0)
2038ORPHAN^CJ8^^ ; ^S X=$S($L($T(^TIUFLF4)):$$ORPHAN^TIUFLF4(D0,^TIU(8925.1,D0,0)),1:"?")
2039"^DD",8925.1,8925.1,.11,9)
2040^
2041"^DD",8925.1,8925.1,.11,9.01)
2042
2043"^DD",8925.1,8925.1,.11,9.1)
2044S X=$S($L($T(^TIUFLF4)):$$ORPHAN^TIUFLF4(D0,^TIU(8925.1,D0,0)),1:"?")
2045"^DD",8925.1,8925.1,.11,21,0)
2046^^57^57^2970220^
2047"^DD",8925.1,8925.1,.11,21,1,0)
2048Orphan applies to Document Definitions of all Types except Objects
2049"^DD",8925.1,8925.1,.11,21,2,0)
2050and Shared Components.
2051"^DD",8925.1,8925.1,.11,21,3,0)
2052
2053"^DD",8925.1,8925.1,.11,21,4,0)
2054Orphan is not editable since it gets its value automatically.
2055"^DD",8925.1,8925.1,.11,21,5,0)
2056
2057"^DD",8925.1,8925.1,.11,21,6,0)
2058Document Definitions are Orphans if they do not belong to the Clinical
2059"^DD",8925.1,8925.1,.11,21,7,0)
2060Documents Hierarchy, i.e., they cannot trace their ancestry all the way
2061"^DD",8925.1,8925.1,.11,21,8,0)
2062back to the Class Clinical Documents. If an Orphan is not In Use, it
2063"^DD",8925.1,8925.1,.11,21,9,0)
2064may be "dead wood" which should be deleted from the file. Orphans not In
2065"^DD",8925.1,8925.1,.11,21,10,0)
2066Use which SHOULD NOT BE DELETED include those being kept for later
2067"^DD",8925.1,8925.1,.11,21,11,0)
2068possible use, those temporarily orphaned in order to move them around in
2069"^DD",8925.1,8925.1,.11,21,12,0)
2070the hierarchy, and those used for uploading documents into files other
2071"^DD",8925.1,8925.1,.11,21,13,0)
2072than the TIU Document file.
2073"^DD",8925.1,8925.1,.11,21,14,0)
2074
2075"^DD",8925.1,8925.1,.11,21,15,0)
2076(Orphan does not apply to Objects since they don't ever belong to the
2077"^DD",8925.1,8925.1,.11,21,16,0)
2078hierarchy. Orphan does not apply to Shared Components since they may
2079"^DD",8925.1,8925.1,.11,21,17,0)
2080have more than one line of ancestry.)
2081"^DD",8925.1,8925.1,.11,21,18,0)
2082
2083"^DD",8925.1,8925.1,.11,21,19,0)
2084Warning: The DOCUMENT DEFINITION file may contain orphan entries which
2085"^DD",8925.1,8925.1,.11,21,20,0)
2086are not used by documents in the TIU Document file but which contain
2087"^DD",8925.1,8925.1,.11,21,21,0)
2088upload instructions for storing documents somewhere else. For example, if
2089"^DD",8925.1,8925.1,.11,21,22,0)
2090a site is uploading Operative Reports into the Surgery file, there may be
2091"^DD",8925.1,8925.1,.11,21,23,0)
2092an orphan Operative Report Document Definition in the DOCUMENT DEFINITION
2093"^DD",8925.1,8925.1,.11,21,24,0)
2094file. These should NOT be deleted just because they are orphans. Such
2095"^DD",8925.1,8925.1,.11,21,25,0)
2096entries can be identified by edit/viewing them through the Sort Option
2097"^DD",8925.1,8925.1,.11,21,26,0)
2098and looking for Upload fields.
2099"^DD",8925.1,8925.1,.11,21,27,0)
2100
2101"^DD",8925.1,8925.1,.11,21,28,0)
2102NOTE: Orphan as used in the Document Definition Utility TIUF does NOT mean
2103"^DD",8925.1,8925.1,.11,21,29,0)
2104having no parents. For example, suppose Exceptional Day Pass Note has
2105"^DD",8925.1,8925.1,.11,21,30,0)
2106parent Day Pass Note. If Day Pass Note has no parent, then Exceptional
2107"^DD",8925.1,8925.1,.11,21,31,0)
2108Day Pass Note cannot trace its ancestry back to Clinical Documents and is
2109"^DD",8925.1,8925.1,.11,21,32,0)
2110an Orphan even though it has a parent.
2111"^DD",8925.1,8925.1,.11,21,33,0)
2112
2113"^DD",8925.1,8925.1,.11,21,34,0)
2114Orphans are invisible to TIU users and cannot be used to enter documents.
2115"^DD",8925.1,8925.1,.11,21,35,0)
2116
2117"^DD",8925.1,8925.1,.11,21,36,0)
2118When an item under a non-orphan is deleted as an item, it becomes an
2119"^DD",8925.1,8925.1,.11,21,37,0)
2120orphan along with all of its descendants. TIUF, the Document Definition
2121"^DD",8925.1,8925.1,.11,21,38,0)
2122Utility, does not permit non-orphan Titles to become orphaned if they are
2123"^DD",8925.1,8925.1,.11,21,39,0)
2124In Use. Titles already used but being retired from further use should
2125"^DD",8925.1,8925.1,.11,21,40,0)
2126be Inactivated, NOT orphaned. Components are a different story;
2127"^DD",8925.1,8925.1,.11,21,41,0)
2128components being retired from further use can and should be orphaned
2129"^DD",8925.1,8925.1,.11,21,42,0)
2130(deleted as items from the Title).
2131"^DD",8925.1,8925.1,.11,21,43,0)
2132
2133"^DD",8925.1,8925.1,.11,21,44,0)
2134Reason: Titles inherit attributes and therefore require a complete
2135"^DD",8925.1,8925.1,.11,21,45,0)
2136ancestry in order to process existing documents. Since components, on the
2137"^DD",8925.1,8925.1,.11,21,46,0)
2138other hand, do not inherit attributes, they do NOT require a complete
2139"^DD",8925.1,8925.1,.11,21,47,0)
2140ancestry to process existing documents (although they must remain in the
2141"^DD",8925.1,8925.1,.11,21,48,0)
2142file.)
2143"^DD",8925.1,8925.1,.11,21,49,0)
2144
2145"^DD",8925.1,8925.1,.11,21,50,0)
2146Since Orphans do not belong to the Hierarchy, they do NOT appear on the
2147"^DD",8925.1,8925.1,.11,21,51,0)
2148Edit Document Definitions Option. They can be accessed through the Sort
2149"^DD",8925.1,8925.1,.11,21,52,0)
2150Document Definitions Option.
2151"^DD",8925.1,8925.1,.11,21,53,0)
2152
2153"^DD",8925.1,8925.1,.11,21,54,0)
2154The field Orphan may have values 'Yes', 'No', or '?'. Orphan has value '?'
2155"^DD",8925.1,8925.1,.11,21,55,0)
2156if there are technical errors making its value unknown.
2157"^DD",8925.1,8925.1,.11,21,56,0)
2158
2159"^DD",8925.1,8925.1,.11,21,57,0)
2160Orphan is a BASIC field.
2161"^DD",8925.1,8925.1,.11,"DT")
21622960201
2163"^DD",8925.1,8925.1,.12,0)
2164HAS 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
2165"^DD",8925.1,8925.1,.12,.1)
2166HAS BOILERPLATE TEXT
2167"^DD",8925.1,8925.1,.12,9)
2168^
2169"^DD",8925.1,8925.1,.12,9.01)
2170
2171"^DD",8925.1,8925.1,.12,9.1)
2172S 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
2173"^DD",8925.1,8925.1,.12,21,0)
2174^^3^3^2970128^
2175"^DD",8925.1,8925.1,.12,21,1,0)
2176Applies to Types Title and Component only. Cannot be edited since value
2177"^DD",8925.1,8925.1,.12,21,2,0)
2178is automatic. A Document Definition Has Boiltxt if it or its descendant
2179"^DD",8925.1,8925.1,.12,21,3,0)
2180Components have Boilerplate Text (Field 3). BASIC field.
2181"^DD",8925.1,8925.1,.12,"DT")
21822960118
2183"^DD",8925.1,8925.1,.13,0)
2184NATIONAL STANDARD^SX^1:YES;0:NO;^0;13^K:'$G(TIUFPRIV) X
2185"^DD",8925.1,8925.1,.13,3)
2186Enter YES if entry is Standard across the nation, i.e. sites mustn't edit
2187"^DD",8925.1,8925.1,.13,4)
2188
2189"^DD",8925.1,8925.1,.13,21,0)
2190^^47^47^2990223^
2191"^DD",8925.1,8925.1,.13,21,1,0)
2192Some Document Definitions, for example, CWAD's, are developed nationally
2193"^DD",8925.1,8925.1,.13,21,2,0)
2194and sent out as standardized entries across the nation. TIU and other
2195"^DD",8925.1,8925.1,.13,21,3,0)
2196packages depend on their standard definition, and they must not be edited
2197"^DD",8925.1,8925.1,.13,21,4,0)
2198by sites but only by the persons who are nationally responsible for them.
2199"^DD",8925.1,8925.1,.13,21,5,0)
2200
2201"^DD",8925.1,8925.1,.13,21,6,0)
2202Such entries are marked NATIONAL STANDARD (field has value 1 for YES),
2203"^DD",8925.1,8925.1,.13,21,7,0)
2204which generally prevents sites from editing the entry.
2205"^DD",8925.1,8925.1,.13,21,8,0)
2206
2207"^DD",8925.1,8925.1,.13,21,9,0)
2208In two cases, sites are permitted to edit National Standard entries. The
2209"^DD",8925.1,8925.1,.13,21,10,0)
2210first case concerns Titles. Sites can edit Status and Abbreviation for
2211"^DD",8925.1,8925.1,.13,21,11,0)
2212National Titles. Status INACTIVE for a National Title prevents manual and
2213"^DD",8925.1,8925.1,.13,21,12,0)
2214upload entry of documents for the Title, while continuing to permit
2215"^DD",8925.1,8925.1,.13,21,13,0)
2216automatic entry for the Title via the TIU application interface for new
2217"^DD",8925.1,8925.1,.13,21,14,0)
2218notes. (Example: Adverse Reaction/Allergy notes are automatically
2219"^DD",8925.1,8925.1,.13,21,15,0)
2220entered by the Allergy package.) Editing Abbreviation gives sites a means
2221"^DD",8925.1,8925.1,.13,21,16,0)
2222of grouping national titles with other National and non-National Titles as
2223"^DD",8925.1,8925.1,.13,21,17,0)
2224they please.
2225"^DD",8925.1,8925.1,.13,21,18,0)
2226
2227"^DD",8925.1,8925.1,.13,21,19,0)
2228The second case where edit of National entries is permitted concerns the
2229"^DD",8925.1,8925.1,.13,21,20,0)
2230Item Multiple:
2231"^DD",8925.1,8925.1,.13,21,21,0)
2232
2233"^DD",8925.1,8925.1,.13,21,22,0)
2234If a National Standard entry has Type Class or Document Class, sites can
2235"^DD",8925.1,8925.1,.13,21,23,0)
2236add/delete Nonnational items as they please, and can edit ALL items AS
2237"^DD",8925.1,8925.1,.13,21,24,0)
2238ITEMS (e.g. Item Sequence, etc.). Sites CANNOT add/delete National items.
2239"^DD",8925.1,8925.1,.13,21,25,0)
2240
2241"^DD",8925.1,8925.1,.13,21,26,0)
2242If a National Standard entry has Type Title or Component, sites
2243"^DD",8925.1,8925.1,.13,21,27,0)
2244cannot add or delete items, but can still edit items AS ITEMS.
2245"^DD",8925.1,8925.1,.13,21,28,0)
2246
2247"^DD",8925.1,8925.1,.13,21,29,0)
2248Sites cannot add National Standard entries as Items to parents. There is
2249"^DD",8925.1,8925.1,.13,21,30,0)
2250one exception: Sites can add National Shared Components to (nonnational)
2251"^DD",8925.1,8925.1,.13,21,31,0)
2252Titles if they wish. Sites can delete National Standard Items from
2253"^DD",8925.1,8925.1,.13,21,32,0)
2254nonnational parents. (Unless there has been a mistake, such items will be
2255"^DD",8925.1,8925.1,.13,21,33,0)
2256limited to Shared Components only.)
2257"^DD",8925.1,8925.1,.13,21,34,0)
2258
2259"^DD",8925.1,8925.1,.13,21,35,0)
2260Field is NOT heritable. If field has no value for an entry, value is 0 by
2261"^DD",8925.1,8925.1,.13,21,36,0)
2262default. This means that entries created by sites are NOT National
2263"^DD",8925.1,8925.1,.13,21,37,0)
2264Standard.
2265"^DD",8925.1,8925.1,.13,21,38,0)
2266
2267"^DD",8925.1,8925.1,.13,21,39,0)
2268Technical Note:
2269"^DD",8925.1,8925.1,.13,21,40,0)
2270
2271"^DD",8925.1,8925.1,.13,21,41,0)
2272National entries (except for Shared Components) must have National
2273"^DD",8925.1,8925.1,.13,21,42,0)
2274ancestors: if a National entry has a nonNational ancestor, the
2275"^DD",8925.1,8925.1,.13,21,43,0)
2276Document Definition Utility TIUF does not permit it to be activated.
2277"^DD",8925.1,8925.1,.13,21,44,0)
2278(Shared Components need not have National ancestors, and do not have a
2279"^DD",8925.1,8925.1,.13,21,45,0)
2280Status.)
2281"^DD",8925.1,8925.1,.13,21,46,0)
2282
2283"^DD",8925.1,8925.1,.13,21,47,0)
2284National Standard is a BASIC field.
2285"^DD",8925.1,8925.1,.13,"DT")
22862970128
2287"^DD",8925.1,8925.1,.14,0)
2288POSTING INDICATOR^S^C:crisis note;W:warning;A:allergy/ADR;D:directive;^0;14^Q
2289"^DD",8925.1,8925.1,.14,1,0)
2290^.1
2291"^DD",8925.1,8925.1,.14,1,1,0)
22928925.1^APOST
2293"^DD",8925.1,8925.1,.14,1,1,1)
2294S ^TIU(8925.1,"APOST",$E(X,1,30),DA)=""
2295"^DD",8925.1,8925.1,.14,1,1,2)
2296K ^TIU(8925.1,"APOST",$E(X,1,30),DA)
2297"^DD",8925.1,8925.1,.14,1,1,"%D",0)
2298^^3^3^2970227^
2299"^DD",8925.1,8925.1,.14,1,1,"%D",1,0)
2300This REGULAR FileMan Cross-reference by Posting Indicator will help to
2301"^DD",8925.1,8925.1,.14,1,1,"%D",2,0)
2302identify which Document Classes are associated with each of the currently
2303"^DD",8925.1,8925.1,.14,1,1,"%D",3,0)
2304supported Posting Types.
2305"^DD",8925.1,8925.1,.14,1,1,"DT")
23062970227
2307"^DD",8925.1,8925.1,.14,3)
2308Please choose an indicator corresponding to the Posting Type
2309"^DD",8925.1,8925.1,.14,21,0)
2310^^2^2^2970515^
2311"^DD",8925.1,8925.1,.14,21,1,0)
2312This field is used to help identify indicators of the Patient Posting Type
2313"^DD",8925.1,8925.1,.14,21,2,0)
2314to which the Document Definition should be ascribed.
2315"^DD",8925.1,8925.1,.14,"DT")
23162970227
2317"^DD",8925.1,8925.1,.15,0)
2318PRF FLAG^CJ30^^ ; ^S X=$S($L($T(CFLDFLAG^TIUPRFL)):$$CFLDFLAG^TIUPRFL(D0),1:"?")
2319"^DD",8925.1,8925.1,.15,.1)
2320ASSOCIATED PATIENT RECORD FLAG
2321"^DD",8925.1,8925.1,.15,9)
2322^
2323"^DD",8925.1,8925.1,.15,9.01)
2324
2325"^DD",8925.1,8925.1,.15,9.1)
2326S X=$S($L($T(CFLDFLAG^TIUPRFL)):$$CFLDFLAG^TIUPRFL(D0),1:"?")
2327"^DD",8925.1,8925.1,.15,21,0)
2328^^14^14^3050405^
2329"^DD",8925.1,8925.1,.15,21,1,0)
2330PRF FLAG applies only to PRF titles. The PRF FLAG of a PRF title is the
2331"^DD",8925.1,8925.1,.15,21,2,0)
2332name of the Patient Record Flag associated with the title. (Notes cannot
2333"^DD",8925.1,8925.1,.15,21,3,0)
2334be written using a PRF title unless the title is associated with a flag
2335"^DD",8925.1,8925.1,.15,21,4,0)
2336and that flag is assigned to the given patient.)
2337"^DD",8925.1,8925.1,.15,21,5,0)
2338
2339"^DD",8925.1,8925.1,.15,21,6,0)
2340If the title is not associated with a flag or the associated flag cannot
2341"^DD",8925.1,8925.1,.15,21,7,0)
2342be found, the field has value "?". If the Document Definition is not a
2343"^DD",8925.1,8925.1,.15,21,8,0)
2344title under Document Class PATIENT RECORD FLAG CAT I or PATIENT RECORD
2345"^DD",8925.1,8925.1,.15,21,9,0)
2346FLAG CAT II, the field has value NA for non-applicable.
2347"^DD",8925.1,8925.1,.15,21,10,0)
2348
2349"^DD",8925.1,8925.1,.15,21,11,0)
2350Technical Note: Flags and their associations with titles are stored in
2351"^DD",8925.1,8925.1,.15,21,12,0)
2352file PRF LOCAL FLAG (#26.11) or in file PRF NATIONAL FLAG (#26.15).
2353"^DD",8925.1,8925.1,.15,21,13,0)
2354
2355"^DD",8925.1,8925.1,.15,21,14,0)
2356PRF FLAG is a BASIC field.
2357"^DD",8925.1,8925.1,.15,"DT")
23583050405
2359"^DD",8925.1,8925.1,1,0)
2360UPLOAD DELIMITED ASCII HEADER^8925.11I^^ITEM;0
2361"^DD",8925.1,8925.1,1,21,0)
2362^^7^7^2970108^^
2363"^DD",8925.1,8925.1,1,21,1,0)
2364This multiple contains the upload record header format of the Document
2365"^DD",8925.1,8925.1,1,21,2,0)
2366Definition, to be used by the upload/router/filer when the preferred
2367"^DD",8925.1,8925.1,1,21,3,0)
2368header format is Delimited string (as opposed to captioned).
2369"^DD",8925.1,8925.1,1,21,4,0)
2370
2371"^DD",8925.1,8925.1,1,21,5,0)
2372Delimited string is useful only if the site has a way of automating
2373"^DD",8925.1,8925.1,1,21,6,0)
2374creation of upload record headers. If they are being created by a human
2375"^DD",8925.1,8925.1,1,21,7,0)
2376transcriber, use Captioned Record Headers instead.
2377"^DD",8925.1,8925.1,1,"DT")
23782960729
2379"^DD",8925.1,8925.1,1.01,0)
2380UPLOAD 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
2381"^DD",8925.1,8925.1,1.01,3)
2382Select the DHCP file in which the document will be stored.
2383"^DD",8925.1,8925.1,1.01,12)
2384Only files with the "TIU" application group may be selected.
2385"^DD",8925.1,8925.1,1.01,12.1)
2386S DIC("S")="I $D(^DIC(+Y,""%"",""B"",""TIU""))"
2387"^DD",8925.1,8925.1,1.01,21,0)
2388^^20^20^2970506^
2389"^DD",8925.1,8925.1,1.01,21,1,0)
2390 -------------
2391"^DD",8925.1,8925.1,1.01,21,2,0)
2392NOTE ON UPLOAD:
2393"^DD",8925.1,8925.1,1.01,21,3,0)
2394Upload fields (Upload Target File, Laygo Allowed, Target Text Field
2395"^DD",8925.1,8925.1,1.01,21,4,0)
2396Subscript, Upload Look-Up Method, Upload Post-Filing Code, Upload Filing
2397"^DD",8925.1,8925.1,1.01,21,5,0)
2398Error Code, and multiple fields Upload Delimited ASCII Header and Upload
2399"^DD",8925.1,8925.1,1.01,21,6,0)
2400Captioned ASCII Header) apply to Document Definitions of Type Class,
2401"^DD",8925.1,8925.1,1.01,21,7,0)
2402Document Class, and Title. Multiple fields Upload Delimited ASCII Header
2403"^DD",8925.1,8925.1,1.01,21,8,0)
2404and Upload Captioned ASCII Header are heritable AS A GROUP. Do NOT set
2405"^DD",8925.1,8925.1,1.01,21,9,0)
2406partial information at a lower level; if you set ANY information at a
2407"^DD",8925.1,8925.1,1.01,21,10,0)
2408lower level, it should be COMPLETE. For information on editing heritable
2409"^DD",8925.1,8925.1,1.01,21,11,0)
2410fields, see Technical field: Edit Template.
2411"^DD",8925.1,8925.1,1.01,21,12,0)
2412
2413"^DD",8925.1,8925.1,1.01,21,13,0)
2414TIUF, the Document Definition Utility does NOT display inherited Upload
2415"^DD",8925.1,8925.1,1.01,21,14,0)
2416information. To see/edit existing upload information, edit/view at the
2417"^DD",8925.1,8925.1,1.01,21,15,0)
2418level it is set.
2419"^DD",8925.1,8925.1,1.01,21,16,0)
2420
2421"^DD",8925.1,8925.1,1.01,21,17,0)
2422 --------------
2423"^DD",8925.1,8925.1,1.01,21,18,0)
2424The UPLOAD TARGET FILE is the VA FileMan file in which fixed-field header
2425"^DD",8925.1,8925.1,1.01,21,19,0)
2426information and associated text will be stored. Only files which include
2427"^DD",8925.1,8925.1,1.01,21,20,0)
2428the TIU Application Group may be selected.
2429"^DD",8925.1,8925.1,1.01,"DT")
24302960729
2431"^DD",8925.1,8925.1,1.02,0)
2432LAYGO ALLOWED^S^0:NO;1:YES;^1;2^Q
2433"^DD",8925.1,8925.1,1.02,3)
2434Please indicate whether new entries may be added to the TARGET FILE.
2435"^DD",8925.1,8925.1,1.02,21,0)
2436^^2^2^2970128^
2437"^DD",8925.1,8925.1,1.02,21,1,0)
2438This field indicates whether or not a new entry can be created in
2439"^DD",8925.1,8925.1,1.02,21,2,0)
2440the TARGET FILE for documents defined by this Document Definition.
2441"^DD",8925.1,8925.1,1.02,"DT")
24422970128
2443"^DD",8925.1,8925.1,1.03,0)
2444TARGET TEXT FIELD SUBSCRIPT^F^^1;3^K:$L(X)>15!($L(X)<1) X
2445"^DD",8925.1,8925.1,1.03,3)
2446Select the Word-processing field in the target file.
2447"^DD",8925.1,8925.1,1.03,21,0)
2448^^2^2^2970620^^
2449"^DD",8925.1,8925.1,1.03,21,1,0)
2450This is the subscript of the word-processing field in the TARGET FILE, in
2451"^DD",8925.1,8925.1,1.03,21,2,0)
2452which the body of the narrative report will be stored.
2453"^DD",8925.1,8925.1,1.03,"DT")
24542940331
2455"^DD",8925.1,8925.1,1.04,0)
2456BOILERPLATE ON UPLOAD ENABLED^S^0:NO;1:YES;^1;4^Q
2457"^DD",8925.1,8925.1,1.04,3)
2458Indicate whether boilerplate logic will be executed on upload
2459"^DD",8925.1,8925.1,1.04,21,0)
2460^^2^2^2961210^
2461"^DD",8925.1,8925.1,1.04,21,1,0)
2462This field determines whether the filer will attempt to execute
2463"^DD",8925.1,8925.1,1.04,21,2,0)
2464boilerplate logic for uploaded documents. Not used in version 1.
2465"^DD",8925.1,8925.1,1.04,"DT")
24662951016
2467"^DD",8925.1,8925.1,2,0)
2468UPLOAD CAPTIONED ASCII HEADER^8925.12A^^HEAD;0
2469"^DD",8925.1,8925.1,2,21,0)
2470^^11^11^2970506^^
2471"^DD",8925.1,8925.1,2,21,1,0)
2472This multiple contains the upload record header format of the Document
2473"^DD",8925.1,8925.1,2,21,2,0)
2474Definition, to be used by the upload/router/filer when the preferred
2475"^DD",8925.1,8925.1,2,21,3,0)
2476header format is captioned (as opposed to delimited string).
2477"^DD",8925.1,8925.1,2,21,4,0)
2478
2479"^DD",8925.1,8925.1,2,21,5,0)
2480Under captioned header format, header items are distinguished from each
2481"^DD",8925.1,8925.1,2,21,6,0)
2482other by captions such as SSN which are entered by the transcriber,
2483"^DD",8925.1,8925.1,2,21,7,0)
2484followed by the data.
2485"^DD",8925.1,8925.1,2,21,8,0)
2486
2487"^DD",8925.1,8925.1,2,21,9,0)
2488Use the captioned header format if documents are transcribed by a human
2489"^DD",8925.1,8925.1,2,21,10,0)
2490transcriber. Delimited format is useful only if the site has some way of
2491"^DD",8925.1,8925.1,2,21,11,0)
2492automatically generating upload record headers.
2493"^DD",8925.1,8925.1,2,"DT")
24942960729
2495"^DD",8925.1,8925.1,3,0)
2496BOILERPLATE TEXT^8925.13^^DFLT;0
2497"^DD",8925.1,8925.1,3,"DT")
24982950421
2499"^DD",8925.1,8925.1,3.02,0)
2500OK TO DISTRIBUTE^S^1:YES;0:NO;^3;2^Q
2501"^DD",8925.1,8925.1,3.02,3)
2502Enter 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.
2503"^DD",8925.1,8925.1,3.02,21,0)
2504^^13^13^2970224^^
2505"^DD",8925.1,8925.1,3.02,21,1,0)
2506Presently applies only to National Programmers; does not appear on
2507"^DD",8925.1,8925.1,3.02,21,2,0)
2508Manager or Clinician Menus.
2509"^DD",8925.1,8925.1,3.02,21,3,0)
2510
2511"^DD",8925.1,8925.1,3.02,21,4,0)
2512If field is 1 for YES, then entry should be included for export. If field
2513"^DD",8925.1,8925.1,3.02,21,5,0)
2514has no value or has value 0, entry should not be included for export.
2515"^DD",8925.1,8925.1,3.02,21,6,0)
2516
2517"^DD",8925.1,8925.1,3.02,21,7,0)
2518Since TIU is hierarchical, the entry's behavior depends on entries above
2519"^DD",8925.1,8925.1,3.02,21,8,0)
2520it in the hierarchy. It is the responsibility of the exporter to make
2521"^DD",8925.1,8925.1,3.02,21,9,0)
2522sure all ancestors which are necessary for the proper behavior of an
2523"^DD",8925.1,8925.1,3.02,21,10,0)
2524exported entry are also exported with it (or are already present at sites
2525"^DD",8925.1,8925.1,3.02,21,11,0)
2526receiving the exported entries).
2527"^DD",8925.1,8925.1,3.02,21,12,0)
2528
2529"^DD",8925.1,8925.1,3.02,21,13,0)
2530Field is NOT heritable. BASIC field.
2531"^DD",8925.1,8925.1,3.02,"DT")
25322970128
2533"^DD",8925.1,8925.1,3.03,0)
2534SUPPRESS VISIT SELECTION^S^1:YES;0:NO;^3;3^Q
2535"^DD",8925.1,8925.1,3.03,3)
2536Enter 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.
2537"^DD",8925.1,8925.1,3.03,21,0)
2538^^17^17^2970220^
2539"^DD",8925.1,8925.1,3.03,21,1,0)
2540Applies to entries of Type Class, Document Class, and Title.
2541"^DD",8925.1,8925.1,3.03,21,2,0)
2542
2543"^DD",8925.1,8925.1,3.03,21,3,0)
2544For most documents it is very important that the user entering a document
2545"^DD",8925.1,8925.1,3.03,21,4,0)
2546select the appropriate visit to link the document with. However,
2547"^DD",8925.1,8925.1,3.03,21,5,0)
2548certain administrative documents for outpatients have no particular visit
2549"^DD",8925.1,8925.1,3.03,21,6,0)
2550that they should be linked with. For example, a clinician could have a
2551"^DD",8925.1,8925.1,3.03,21,7,0)
2552chance encounter with a patient in the corridor and want to document the
2553"^DD",8925.1,8925.1,3.03,21,8,0)
2554discussion, or a clinician could simply want to remind him/herself of
2555"^DD",8925.1,8925.1,3.03,21,9,0)
2556something for a given patient. Documents for such purposes can be set to
2557"^DD",8925.1,8925.1,3.03,21,10,0)
2558automatically create their own historical visit when they are entered, so
2559"^DD",8925.1,8925.1,3.03,21,11,0)
2560that the user is not asked to select a visit.
2561"^DD",8925.1,8925.1,3.03,21,12,0)
2562
2563"^DD",8925.1,8925.1,3.03,21,13,0)
2564Warning: Such documents DO NOT GIVE WORKLOAD CREDIT.
2565"^DD",8925.1,8925.1,3.03,21,14,0)
2566
2567"^DD",8925.1,8925.1,3.03,21,15,0)
2568Heritable. BASIC field. If field has no value and there is no value
2569"^DD",8925.1,8925.1,3.03,21,16,0)
2570to inherit, default value is NO. For information on editing heritable
2571"^DD",8925.1,8925.1,3.03,21,17,0)
2572fields, see Technical Field Edit Template.
2573"^DD",8925.1,8925.1,3.03,"DT")
25742970124
2575"^DD",8925.1,8925.1,4,0)
2576UPLOAD LOOK-UP METHOD^K^^4;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2577"^DD",8925.1,8925.1,4,3)
2578Please enter the MUMPS code to be executed for record location.
2579"^DD",8925.1,8925.1,4,9)
2580@
2581"^DD",8925.1,8925.1,4,21,0)
2582^^12^12^2970107^^
2583"^DD",8925.1,8925.1,4,21,1,0)
2584Sometimes when an entry is uploaded into the target file, a new entry is
2585"^DD",8925.1,8925.1,4,21,2,0)
2586created for it. However, in other cases such as for Operative Reports, or
2587"^DD",8925.1,8925.1,4,21,3,0)
2588for an addendum, the file entry already exists and must be looked-up and
2589"^DD",8925.1,8925.1,4,21,4,0)
2590edited.
2591"^DD",8925.1,8925.1,4,21,5,0)
2592
2593"^DD",8925.1,8925.1,4,21,6,0)
2594Look-Up Method is the MUMPS code invoked to perform such a look-up on the
2595"^DD",8925.1,8925.1,4,21,7,0)
2596target file. If a look-up is necessary and this field is blank, a regular
2597"^DD",8925.1,8925.1,4,21,8,0)
2598DIC lookup is performed. If the regular DIC lookup is not sufficient to
2599"^DD",8925.1,8925.1,4,21,9,0)
2600locate the appropriate entry, this field should contain the lookup. It
2601"^DD",8925.1,8925.1,4,21,10,0)
2602should expect any look-up special variables named in the header fields as
2603"^DD",8925.1,8925.1,4,21,11,0)
2604input variables, and should return the variable Y in DIC-compatible format
2605"^DD",8925.1,8925.1,4,21,12,0)
2606(i.e., IEN^EXTERNAL VALUE[^1]).
2607"^DD",8925.1,8925.1,4,"DT")
26082960729
2609"^DD",8925.1,8925.1,4.1,0)
2610COMMIT ACTION^K^^4.1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2611"^DD",8925.1,8925.1,4.1,3)
2612This is Standard MUMPS code.
2613"^DD",8925.1,8925.1,4.1,9)
2614@
2615"^DD",8925.1,8925.1,4.1,21,0)
2616^^3^3^2980122^
2617"^DD",8925.1,8925.1,4.1,21,1,0)
2618This M-Code is executed when the TIU document is "committed" to the
2619"^DD",8925.1,8925.1,4.1,21,2,0)
2620database (i.e., when the document is saved, and prior to release,
2621"^DD",8925.1,8925.1,4.1,21,3,0)
2622verification, or signature). Heritable. TECHNICAL field.
2623"^DD",8925.1,8925.1,4.1,"DT")
26242971126
2625"^DD",8925.1,8925.1,4.2,0)
2626RELEASE ACTION^K^^4.2;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2627"^DD",8925.1,8925.1,4.2,3)
2628This is Standard MUMPS code.
2629"^DD",8925.1,8925.1,4.2,9)
2630@
2631"^DD",8925.1,8925.1,4.2,21,0)
2632^^2^2^2980126^^
2633"^DD",8925.1,8925.1,4.2,21,1,0)
2634This M-Code is executed upon Release of the document. Heritable.
2635"^DD",8925.1,8925.1,4.2,21,2,0)
2636TECHNICAL field.
2637"^DD",8925.1,8925.1,4.2,"DT")
26382971126
2639"^DD",8925.1,8925.1,4.3,0)
2640VERIFICATION ACTION^K^^4.3;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2641"^DD",8925.1,8925.1,4.3,3)
2642This is Standard MUMPS code.
2643"^DD",8925.1,8925.1,4.3,9)
2644@
2645"^DD",8925.1,8925.1,4.3,21,0)
2646^^2^2^2980122^
2647"^DD",8925.1,8925.1,4.3,21,1,0)
2648This M-Code is executed upon Verification of the document. Heritable.
2649"^DD",8925.1,8925.1,4.3,21,2,0)
2650TECHNICAL field.
2651"^DD",8925.1,8925.1,4.3,"DT")
26522971126
2653"^DD",8925.1,8925.1,4.4,0)
2654DELETE ACTION^K^^4.4;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2655"^DD",8925.1,8925.1,4.4,3)
2656This is Standard MUMPS code.
2657"^DD",8925.1,8925.1,4.4,9)
2658@
2659"^DD",8925.1,8925.1,4.4,21,0)
2660^^2^2^2980122^
2661"^DD",8925.1,8925.1,4.4,21,1,0)
2662This M-Code is executed upon Deletion of the document. Heritable.
2663"^DD",8925.1,8925.1,4.4,21,2,0)
2664TECHNICAL field.
2665"^DD",8925.1,8925.1,4.4,"DT")
26662971126
2667"^DD",8925.1,8925.1,4.45,0)
2668PACKAGE REASSIGNMENT ACTION^K^^4.45;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2669"^DD",8925.1,8925.1,4.45,3)
2670This is Standard MUMPS code.
2671"^DD",8925.1,8925.1,4.45,9)
2672@
2673"^DD",8925.1,8925.1,4.45,21,0)
2674^^2^2^2980122^
2675"^DD",8925.1,8925.1,4.45,21,1,0)
2676This M-Code is executed when a document with a link to a client
2677"^DD",8925.1,8925.1,4.45,21,2,0)
2678application is Reassigned. Heritable. TECHNICAL field.
2679"^DD",8925.1,8925.1,4.45,"DT")
26802971202
2681"^DD",8925.1,8925.1,4.5,0)
2682UPLOAD POST-FILING CODE^K^^4.5;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2683"^DD",8925.1,8925.1,4.5,3)
2684This is Standard MUMPS code.
2685"^DD",8925.1,8925.1,4.5,9)
2686@
2687"^DD",8925.1,8925.1,4.5,21,0)
2688^^4^4^2970522^
2689"^DD",8925.1,8925.1,4.5,21,1,0)
2690This field specifies code to be executed following the successful filing
2691"^DD",8925.1,8925.1,4.5,21,2,0)
2692of an uploaded record. It may be used to send bulletins or alerts,
2693"^DD",8925.1,8925.1,4.5,21,3,0)
2694evaluate expected signers/cosigners, trigger events, update statuses, or
2695"^DD",8925.1,8925.1,4.5,21,4,0)
2696whatever the designer of the application deems appropriate.
2697"^DD",8925.1,8925.1,4.5,"DT")
26982960729
2699"^DD",8925.1,8925.1,4.6,0)
2700ENTRY ACTION^KX^^4.6;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2701"^DD",8925.1,8925.1,4.6,3)
2702This is Standard MUMPS code.
2703"^DD",8925.1,8925.1,4.6,9)
2704@
2705"^DD",8925.1,8925.1,4.6,21,0)
2706^^3^3^2980126^^
2707"^DD",8925.1,8925.1,4.6,21,1,0)
2708This M-Code is executed during the Entry/Editing of a document, after
2709"^DD",8925.1,8925.1,4.6,21,2,0)
2710selection of the Title, and prior to selection of the Patient. It may be
2711"^DD",8925.1,8925.1,4.6,21,3,0)
2712used to set up environmental variables, etc. Heritable. TECHNICAL field.
2713"^DD",8925.1,8925.1,4.6,"DT")
27142961022
2715"^DD",8925.1,8925.1,4.7,0)
2716EXIT ACTION^KX^^4.7;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2717"^DD",8925.1,8925.1,4.7,3)
2718This is Standard MUMPS code.
2719"^DD",8925.1,8925.1,4.7,9)
2720@
2721"^DD",8925.1,8925.1,4.7,21,0)
2722^^3^3^2980126^^
2723"^DD",8925.1,8925.1,4.7,21,1,0)
2724This M-Code is executed just prior to Exit from the entry/edit process
2725"^DD",8925.1,8925.1,4.7,21,2,0)
2726for a document. It may be used to send alerts or bulletins, clean up
2727"^DD",8925.1,8925.1,4.7,21,3,0)
2728temporary global variables, etc. Heritable. TECHNICAL field.
2729"^DD",8925.1,8925.1,4.7,"DT")
27302961022
2731"^DD",8925.1,8925.1,4.8,0)
2732UPLOAD FILING ERROR CODE^K^^4.8;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2733"^DD",8925.1,8925.1,4.8,.1)
2734UPLOAD FILING ERROR RESOLUTION CODE
2735"^DD",8925.1,8925.1,4.8,3)
2736This is Standard MUMPS code.
2737"^DD",8925.1,8925.1,4.8,9)
2738@
2739"^DD",8925.1,8925.1,4.8,21,0)
2740^^6^6^2970106^
2741"^DD",8925.1,8925.1,4.8,21,1,0)
2742This MUMPS-type field specifies the code to be executed when the user
2743"^DD",8925.1,8925.1,4.8,21,2,0)
2744attempts to resolve a filing error. Filing Errors may be resolved either
2745"^DD",8925.1,8925.1,4.8,21,3,0)
2746by responding to a Filing Error Alert or through the option to Review
2747"^DD",8925.1,8925.1,4.8,21,4,0)
2748Upload Events. Typically, the code will offer the user an opportunity to
2749"^DD",8925.1,8925.1,4.8,21,5,0)
2750look up online information necessary to resolve the error (e.g.,
2751"^DD",8925.1,8925.1,4.8,21,6,0)
2752demographic, or case-related information).
2753"^DD",8925.1,8925.1,4.8,"DT")
27542960729
2755"^DD",8925.1,8925.1,4.9,0)
2756POST-SIGNATURE CODE^K^^4.9;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2757"^DD",8925.1,8925.1,4.9,3)
2758This is Standard MUMPS code.
2759"^DD",8925.1,8925.1,4.9,9)
2760@
2761"^DD",8925.1,8925.1,4.9,21,0)
2762^^2^2^2980126^^
2763"^DD",8925.1,8925.1,4.9,21,1,0)
2764This M-Code is executed following Signature (or Cosignature) of a TIU
2765"^DD",8925.1,8925.1,4.9,21,2,0)
2766document. Heritable. TECHNICAL field.
2767"^DD",8925.1,8925.1,4.9,"DT")
27682971001
2769"^DD",8925.1,8925.1,5,0)
2770EDIT TEMPLATE^FX^^5;E1,245^K:$L(X)>60!($L(X)<2) X
2771"^DD",8925.1,8925.1,5,3)
2772Enter the name of the Input Template for documents defined by this entry.
2773"^DD",8925.1,8925.1,5,4)
2774D HELP1^TIUFXHLX(5)
2775"^DD",8925.1,8925.1,5,9)
2776@
2777"^DD",8925.1,8925.1,5,21,0)
2778^^19^19^2980126^^
2779"^DD",8925.1,8925.1,5,21,1,0)
2780Applies to Classes, Document Classes, Titles. This is the Input Template
2781"^DD",8925.1,8925.1,5,21,2,0)
2782for Entering/Editing documents defined by this entry. Template
2783"^DD",8925.1,8925.1,5,21,3,0)
2784includes fixed field information such as Patient, etc. Enter Edit
2785"^DD",8925.1,8925.1,5,21,4,0)
2786Template in Format [TEMPLATE NAME], or as a "field-string" (e.g.,
2787"^DD",8925.1,8925.1,5,21,5,0)
2788.01;1;3;5). Heritable. TECHNICAL field.
2789"^DD",8925.1,8925.1,5,21,6,0)
2790
2791"^DD",8925.1,8925.1,5,21,7,0)
2792NOTE on editing heritable fields:
2793"^DD",8925.1,8925.1,5,21,8,0)
2794
2795"^DD",8925.1,8925.1,5,21,9,0)
2796When editing heritable fields, the user is presented with the EFFECTIVE
2797"^DD",8925.1,8925.1,5,21,10,0)
2798value of the field as the default (e.g. NO//). This is the same as the
2799"^DD",8925.1,8925.1,5,21,11,0)
2800value shown in the display and is the field's own value if it has one, the
2801"^DD",8925.1,8925.1,5,21,12,0)
2802inherited value if the field does not have its own value, or the default
2803"^DD",8925.1,8925.1,5,21,13,0)
2804for the field if the field has neither its own nor an inherited value. If
2805"^DD",8925.1,8925.1,5,21,14,0)
2806the user accepts this default by pressing return, the value is made
2807"^DD",8925.1,8925.1,5,21,15,0)
2808explicit, i.e., entered into the field. If a user does NOT want to make
2809"^DD",8925.1,8925.1,5,21,16,0)
2810the value explicit, the user should enter @, which leaves a blank field
2811"^DD",8925.1,8925.1,5,21,17,0)
2812blank. If the user want to delete an explicit value, the user should
2813"^DD",8925.1,8925.1,5,21,18,0)
2814enter @, which deletes the field value, leaving TIU to use the effective
2815"^DD",8925.1,8925.1,5,21,19,0)
2816value for the field.
2817"^DD",8925.1,8925.1,5,"DT")
28182961022
2819"^DD",8925.1,8925.1,6,0)
2820PRINT METHOD^KX^^6;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
2821"^DD",8925.1,8925.1,6,3)
2822Please enter the MUMPS code to be executed to print a record.
2823"^DD",8925.1,8925.1,6,4)
2824D HELP1^TIUFXHLX(6)
2825"^DD",8925.1,8925.1,6,9)
2826@
2827"^DD",8925.1,8925.1,6,21,0)
2828^^5^5^2980126^^
2829"^DD",8925.1,8925.1,6,21,1,0)
2830Applies to Types Class, Document Class, Title. This M-Code is executed
2831"^DD",8925.1,8925.1,6,21,2,0)
2832when a document is Printed from the TIU List Manager screen (as opposed to
2833"^DD",8925.1,8925.1,6,21,3,0)
2834a separate print option which may have its own code.) Heritable. TECHNICAL
2835"^DD",8925.1,8925.1,6,21,4,0)
2836field. For more information on editing heritable fields, see Technical
2837"^DD",8925.1,8925.1,6,21,5,0)
2838field Edit Template.
2839"^DD",8925.1,8925.1,6,"DT")
28402961022
2841"^DD",8925.1,8925.1,6.1,0)
2842PRINT FORM HEADER^FX^^6.1;1^K:$L(X)>40!($L(X)<3) X
2843"^DD",8925.1,8925.1,6.1,3)
2844Answer must be 3-40 characters in length.
2845"^DD",8925.1,8925.1,6.1,4)
2846D HELP1^TIUFXHLX(6.1)
2847"^DD",8925.1,8925.1,6.1,21,0)
2848^^12^12^2970108^^
2849"^DD",8925.1,8925.1,6.1,21,1,0)
2850For basic information on Print Form Header see Technical field Allow
2851"^DD",8925.1,8925.1,6.1,21,2,0)
2852Custom Form Headers.
2853"^DD",8925.1,8925.1,6.1,21,3,0)
2854
2855"^DD",8925.1,8925.1,6.1,21,4,0)
2856The Print Form Header is the official medical record title of the document
2857"^DD",8925.1,8925.1,6.1,21,5,0)
2858which has been approved by the Medical Record Committee based on national
2859"^DD",8925.1,8925.1,6.1,21,6,0)
2860guidelines.
2861"^DD",8925.1,8925.1,6.1,21,7,0)
2862
2863"^DD",8925.1,8925.1,6.1,21,8,0)
2864Examples: Progress Notes, Physical Examination, History - Part 1, etc.
2865"^DD",8925.1,8925.1,6.1,21,9,0)
2866
2867"^DD",8925.1,8925.1,6.1,21,10,0)
2868This field is heritable with lower level values overriding higher ones AS
2869"^DD",8925.1,8925.1,6.1,21,11,0)
2870LONG AS the field is applicable. See Allow Custom Form Headers. Print
2871"^DD",8925.1,8925.1,6.1,21,12,0)
2872Form Header is a TECHNICAL field.
2873"^DD",8925.1,8925.1,6.1,23,0)
2874^^6^6^2970108^^^^
2875"^DD",8925.1,8925.1,6.1,23,1,0)
2876The narrative stored in this field will display as the form header of a
2877"^DD",8925.1,8925.1,6.1,23,2,0)
2878document. If entered at a CLASS level such as FORMS, all forms documents
2879"^DD",8925.1,8925.1,6.1,23,3,0)
2880will display entered header as the form header of the document. If
2881"^DD",8925.1,8925.1,6.1,23,4,0)
2882the free text is entered at a lower level (i.e., TITLE), this form header
2883"^DD",8925.1,8925.1,6.1,23,5,0)
2884will override the one entered at the higher level and will be displayed on
2885"^DD",8925.1,8925.1,6.1,23,6,0)
2886the form.
2887"^DD",8925.1,8925.1,6.1,"DT")
28882961022
2889"^DD",8925.1,8925.1,6.12,0)
2890PRINT FORM NUMBER^FX^^6.1;2^K:$L(X)>20!($L(X)<3) X
2891"^DD",8925.1,8925.1,6.12,3)
2892Answer must be 3-20 characters in length.
2893"^DD",8925.1,8925.1,6.12,4)
2894D HELP1^TIUFXHLX(6.12)
2895"^DD",8925.1,8925.1,6.12,21,0)
2896^^13^13^2970106^
2897"^DD",8925.1,8925.1,6.12,21,1,0)
2898For basic information on Print Form Number see Technical field Allow
2899"^DD",8925.1,8925.1,6.12,21,2,0)
2900Custom Form Headers.
2901"^DD",8925.1,8925.1,6.12,21,3,0)
2902
2903"^DD",8925.1,8925.1,6.12,21,4,0)
2904The Print Form Number is the official medical record form number of the
2905"^DD",8925.1,8925.1,6.12,21,5,0)
2906document which has been approved by the Medical Record Committee based
2907"^DD",8925.1,8925.1,6.12,21,6,0)
2908on national guidelines.
2909"^DD",8925.1,8925.1,6.12,21,7,0)
2910
2911"^DD",8925.1,8925.1,6.12,21,8,0)
2912Example: Progress Note - Vice SF 509, Consult - SF 513, Physicial
2913"^DD",8925.1,8925.1,6.12,21,9,0)
2914Examination - SF 506.
2915"^DD",8925.1,8925.1,6.12,21,10,0)
2916
2917"^DD",8925.1,8925.1,6.12,21,11,0)
2918Field is heritable with lower level values overriding higher ones AS LONG
2919"^DD",8925.1,8925.1,6.12,21,12,0)
2920AS the field is applicable. See field Allow Custom Form Headers. Print
2921"^DD",8925.1,8925.1,6.12,21,13,0)
2922Form Header is a TECHNICAL field.
2923"^DD",8925.1,8925.1,6.12,23,0)
2924^^6^6^2970106^^^^
2925"^DD",8925.1,8925.1,6.12,23,1,0)
2926The free text stored in this field will be displayed as the form number of
2927"^DD",8925.1,8925.1,6.12,23,2,0)
2928a document. If entered at a CLASS level such as Forms, all Forms
2929"^DD",8925.1,8925.1,6.12,23,3,0)
2930documents will display the entered value as the form number of the
2931"^DD",8925.1,8925.1,6.12,23,4,0)
2932document. If the free text is entered at a lower level (i.e., TITLE),
2933"^DD",8925.1,8925.1,6.12,23,5,0)
2934this value will override the one entered at the higher level and will be
2935"^DD",8925.1,8925.1,6.12,23,6,0)
2936displayed on the form.
2937"^DD",8925.1,8925.1,6.12,"DT")
29382961022
2939"^DD",8925.1,8925.1,6.13,0)
2940PRINT GROUP^NJ2,0X^^6.1;3^K:+X'=X!(X>10)!(X<1)!(X?.E1"."1N.N) X
2941"^DD",8925.1,8925.1,6.13,3)
2942Type a Number between 1 and 10, 0 Decimal Digits. Enter ?? for help.
2943"^DD",8925.1,8925.1,6.13,4)
2944D HELP1^TIUFXHLX(6.13)
2945"^DD",8925.1,8925.1,6.13,21,0)
2946^^19^19^2970106^
2947"^DD",8925.1,8925.1,6.13,21,1,0)
2948For basic information on Print Group see Technical field Allow Custom Form
2949"^DD",8925.1,8925.1,6.13,21,2,0)
2950Headers.
2951"^DD",8925.1,8925.1,6.13,21,3,0)
2952
2953"^DD",8925.1,8925.1,6.13,21,4,0)
2954Print Group is an integer number which serves to group by print form
2955"^DD",8925.1,8925.1,6.13,21,5,0)
2956headers/numbers related documents that share a common print method; e.g.,
2957"^DD",8925.1,8925.1,6.13,21,6,0)
2958Progress Notes, H&P's, and other documents may share a common print
2959"^DD",8925.1,8925.1,6.13,21,7,0)
2960method, but have differing form headers/numbers and should each print in
2961"^DD",8925.1,8925.1,6.13,21,8,0)
2962their own, separate collation. Specifying a common print group for
2963"^DD",8925.1,8925.1,6.13,21,9,0)
2964documents with the same headers/numbers (for example, Progress Notes have
2965"^DD",8925.1,8925.1,6.13,21,10,0)
2966Print Group 2, H&P's might have Print Group 7) causes such documents
2967"^DD",8925.1,8925.1,6.13,21,11,0)
2968from each print group to collate together when a mixed print is called
2969"^DD",8925.1,8925.1,6.13,21,12,0)
2970for.
2971"^DD",8925.1,8925.1,6.13,21,13,0)
2972
2973"^DD",8925.1,8925.1,6.13,21,14,0)
2974Since documents collate first by print method, then by print group, print
2975"^DD",8925.1,8925.1,6.13,21,15,0)
2976group is not necessary unless documents share a common print method.
2977"^DD",8925.1,8925.1,6.13,21,16,0)
2978
2979"^DD",8925.1,8925.1,6.13,21,17,0)
2980Print Group is heritable with lower level values overriding higher ones AS
2981"^DD",8925.1,8925.1,6.13,21,18,0)
2982LONG AS the field is applicable. See Allow Custom Form Headers. Print
2983"^DD",8925.1,8925.1,6.13,21,19,0)
2984Group is a TECHNICAL field.
2985"^DD",8925.1,8925.1,6.13,"DT")
29862961022
2987"^DD",8925.1,8925.1,6.14,0)
2988ALLOW CUSTOM FORM HEADERS^SX^1:YES;0:NO;^6.1;4^Q
2989"^DD",8925.1,8925.1,6.14,.1)
2990ALLOW CUSTOM FORM HEADERS/NUMBERS AT LOWER LEVELS
2991"^DD",8925.1,8925.1,6.14,3)
2992May 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.
2993"^DD",8925.1,8925.1,6.14,4)
2994D CUSTOM^TIUFXHLX
2995"^DD",8925.1,8925.1,6.14,21,0)
2996^^69^69^2980122^
2997"^DD",8925.1,8925.1,6.14,21,1,0)
2998Allow Custom Form Headers may be set for entries of Type Class or Document
2999"^DD",8925.1,8925.1,6.14,21,2,0)
3000Class and affects DESCENDANTS of the entry for which it is set.
3001"^DD",8925.1,8925.1,6.14,21,3,0)
3002
3003"^DD",8925.1,8925.1,6.14,21,4,0)
3004Information on Form Headers, Form Numbers, Print Group, and Allow Custom
3005"^DD",8925.1,8925.1,6.14,21,5,0)
3006Form Headers:
3007"^DD",8925.1,8925.1,6.14,21,6,0)
3008
3009"^DD",8925.1,8925.1,6.14,21,7,0)
3010Some clinical documents use Forms with Form Headers and Form Numbers, for
3011"^DD",8925.1,8925.1,6.14,21,8,0)
3012example, Progress Note Forms have Header 'Progress Notes' and Number 'Vice
3013"^DD",8925.1,8925.1,6.14,21,9,0)
3014SF 509.'
3015"^DD",8925.1,8925.1,6.14,21,10,0)
3016
3017"^DD",8925.1,8925.1,6.14,21,11,0)
3018The Owner of a Document Definition must decide whether all documents
3019"^DD",8925.1,8925.1,6.14,21,12,0)
3020descending from the entry will have the SAME Header/Number, or whether to
3021"^DD",8925.1,8925.1,6.14,21,13,0)
3022allow CUSTOM (varying) Headers/Numbers at lower levels.
3023"^DD",8925.1,8925.1,6.14,21,14,0)
3024
3025"^DD",8925.1,8925.1,6.14,21,15,0)
3026Allow Custom Headers holds the decision: If the field has value 0 for NO,
3027"^DD",8925.1,8925.1,6.14,21,16,0)
3028then ALL descendant documents use a COMMON Header/Number (or perhaps they
3029"^DD",8925.1,8925.1,6.14,21,17,0)
3030all use NO Header/Number); they also collate together in printouts.
3031"^DD",8925.1,8925.1,6.14,21,18,0)
3032
3033"^DD",8925.1,8925.1,6.14,21,19,0)
3034For example, Class Progress Notes does NOT Allow Custom Form Headers. This
3035"^DD",8925.1,8925.1,6.14,21,20,0)
3036means that ALL Progress Note Titles have the same header and the same form
3037"^DD",8925.1,8925.1,6.14,21,21,0)
3038number. For Class Progress Notes, Field Print Form Header holds the
3039"^DD",8925.1,8925.1,6.14,21,22,0)
3040header 'Progress Notes', Field Print Form Number holds Form Number 'Vice
3041"^DD",8925.1,8925.1,6.14,21,23,0)
3042SF 509', and Field Print Group holds '2'. Since Class Progress Notes does
3043"^DD",8925.1,8925.1,6.14,21,24,0)
3044not Allow Custom Form Headers, these field values apply for ALL Progress
3045"^DD",8925.1,8925.1,6.14,21,25,0)
3046Note Titles. That is, all Progress Notes have header 'Progress Notes',
3047"^DD",8925.1,8925.1,6.14,21,26,0)
3048Form Number 'Vice SF 509', and collate together in printouts.
3049"^DD",8925.1,8925.1,6.14,21,27,0)
3050
3051"^DD",8925.1,8925.1,6.14,21,28,0)
3052Field Allow Custom Field Headers also determines whether or not related
3053"^DD",8925.1,8925.1,6.14,21,29,0)
3054Fields Print Form Header, Print Form Number, Print Group, (and even Allow
3055"^DD",8925.1,8925.1,6.14,21,30,0)
3056Custom Field Headers) are applicable at lower levels. If an entry at a
3057"^DD",8925.1,8925.1,6.14,21,31,0)
3058particular level DOES allow Custom Form Headers, then these related fields
3059"^DD",8925.1,8925.1,6.14,21,32,0)
3060DO APPLY to descendants at the next lower level. If an entry at a
3061"^DD",8925.1,8925.1,6.14,21,33,0)
3062particular level DOES NOT allow Custom Form Headers, then ALL LOWER LEVELS
3063"^DD",8925.1,8925.1,6.14,21,34,0)
3064inherit the the prohibition, and the related fields DO NOT APPLY at ANY
3065"^DD",8925.1,8925.1,6.14,21,35,0)
3066lower levels.
3067"^DD",8925.1,8925.1,6.14,21,36,0)
3068
3069"^DD",8925.1,8925.1,6.14,21,37,0)
3070Example: Since Class Progress Notes does NOT Allow Custom Form Headers,
3071"^DD",8925.1,8925.1,6.14,21,38,0)
3072fields Print Form Header, Print Form Number, Print Group, and Allow Custom
3073"^DD",8925.1,8925.1,6.14,21,39,0)
3074Field Headers DO NOT APPLY to Document Classes or Titles under Progress
3075"^DD",8925.1,8925.1,6.14,21,40,0)
3076Notes. This means that Document Definitions for documents requiring
3077"^DD",8925.1,8925.1,6.14,21,41,0)
3078different Form Headers/Numbers must be placed under a separate line of
3079"^DD",8925.1,8925.1,6.14,21,42,0)
3080descent in the hierarchy; they cannot be under Progress Notes.
3081"^DD",8925.1,8925.1,6.14,21,43,0)
3082
3083"^DD",8925.1,8925.1,6.14,21,44,0)
3084Example: Class Clinical Documents, the Mother of all Document Definitions,
3085"^DD",8925.1,8925.1,6.14,21,45,0)
3086does not want to REQUIRE all Document Definitions under it to use one
3087"^DD",8925.1,8925.1,6.14,21,46,0)
3088common Header. So Clinical Documents DOES Allow Custom Form Headers.
3089"^DD",8925.1,8925.1,6.14,21,47,0)
3090Classes/Document Classes UNDER CLinical Documents can decide for
3091"^DD",8925.1,8925.1,6.14,21,48,0)
3092themselves whether or not to Allow Custom Headers for their own Items.
3093"^DD",8925.1,8925.1,6.14,21,49,0)
3094
3095"^DD",8925.1,8925.1,6.14,21,50,0)
3096Example: Class DISCHARGE SUMMARY has only one Form Header and Number which
3097"^DD",8925.1,8925.1,6.14,21,51,0)
3098is used by all Discharge Summary documents. So Class Discharge Summary
3099"^DD",8925.1,8925.1,6.14,21,52,0)
3100does NOT Allow Custom Headers.
3101"^DD",8925.1,8925.1,6.14,21,53,0)
3102
3103"^DD",8925.1,8925.1,6.14,21,54,0)
3104Example: Class FORMS might contain miscellaneous documents, each using
3105"^DD",8925.1,8925.1,6.14,21,55,0)
3106a different Form with its own Form Header and Form Number. So Class Forms
3107"^DD",8925.1,8925.1,6.14,21,56,0)
3108would Allow Custom Headers.
3109"^DD",8925.1,8925.1,6.14,21,57,0)
3110
3111"^DD",8925.1,8925.1,6.14,21,58,0)
3112Field Allow Custom Form Headers may be set for Document Definitions of
3113"^DD",8925.1,8925.1,6.14,21,59,0)
3114Type Class or Document Class only, and affects the DESCENDANTS of the
3115"^DD",8925.1,8925.1,6.14,21,60,0)
3116entry for which it is set.
3117"^DD",8925.1,8925.1,6.14,21,61,0)
3118
3119"^DD",8925.1,8925.1,6.14,21,62,0)
3120If a DOCUMENT CLASS Allows Custom Form Headers, then TIUF, the Document
3121"^DD",8925.1,8925.1,6.14,21,63,0)
3122Definition Utility, does not permit a descendant Title to be activated
3123"^DD",8925.1,8925.1,6.14,21,64,0)
3124unless fields Print Form Header, Print Form Number, and Print Group have a
3125"^DD",8925.1,8925.1,6.14,21,65,0)
3126value (of their own or inherited). If NO Header, or Number is desired,
3127"^DD",8925.1,8925.1,6.14,21,66,0)
3128enter 'NONE'. If NO Print Group is desired, enter '0'.
3129"^DD",8925.1,8925.1,6.14,21,67,0)
3130
3131"^DD",8925.1,8925.1,6.14,21,68,0)
3132For information on editing heritable fields, see Technical field Edit
3133"^DD",8925.1,8925.1,6.14,21,69,0)
3134Template.
3135"^DD",8925.1,8925.1,6.14,"DT")
31362970128
3137"^DD",8925.1,8925.1,6.5,0)
3138ON BROWSE EVENT^K^^6.5;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3139"^DD",8925.1,8925.1,6.5,3)
3140This is Standard MUMPS code.
3141"^DD",8925.1,8925.1,6.5,9)
3142@
3143"^DD",8925.1,8925.1,6.5,21,0)
3144^^2^2^3010215^
3145"^DD",8925.1,8925.1,6.5,21,1,0)
3146This is MUMPS code which is invoked on browsing a document to fetch data
3147"^DD",8925.1,8925.1,6.5,21,2,0)
3148from the Requesting Package that will be included in the display.
3149"^DD",8925.1,8925.1,6.5,"DT")
31503010215
3151"^DD",8925.1,8925.1,6.51,0)
3152ON RETRACT EVENT^K^^6.51;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3153"^DD",8925.1,8925.1,6.51,3)
3154This is Standard MUMPS code.
3155"^DD",8925.1,8925.1,6.51,9)
3156@
3157"^DD",8925.1,8925.1,6.51,21,0)
3158^^2^2^3010301^
3159"^DD",8925.1,8925.1,6.51,21,1,0)
3160This is MUMPS code which is invoked on retraction of a document to perform
3161"^DD",8925.1,8925.1,6.51,21,2,0)
3162any processing task that the Requesting Package may require.
3163"^DD",8925.1,8925.1,6.51,"DT")
31643010301
3165"^DD",8925.1,8925.1,7,0)
3166VISIT LINKAGE METHOD^KX^^7;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3167"^DD",8925.1,8925.1,7,3)
3168Please enter the MUMPS code to be executed to establish Visit Linkage.
3169"^DD",8925.1,8925.1,7,4)
3170D HELP1^TIUFXHLX(7)
3171"^DD",8925.1,8925.1,7,9)
3172@
3173"^DD",8925.1,8925.1,7,21,0)
3174^^6^6^2980122^
3175"^DD",8925.1,8925.1,7,21,1,0)
3176Applies to Types Class, Document Class, Title. This M-Code is executed to
3177"^DD",8925.1,8925.1,7,21,2,0)
3178establish Visit Linkage, usually displaying appropriate visits and
3179"^DD",8925.1,8925.1,7,21,3,0)
3180prompting the user to select the correct one.
3181"^DD",8925.1,8925.1,7,21,4,0)
3182
3183"^DD",8925.1,8925.1,7,21,5,0)
3184Heritable. TECHNICAL Field. For information on editing heritable fields,
3185"^DD",8925.1,8925.1,7,21,6,0)
3186see Technical Field Edit Template.
3187"^DD",8925.1,8925.1,7,"DT")
31882961022
3189"^DD",8925.1,8925.1,8,0)
3190VALIDATION METHOD^KX^^8;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3191"^DD",8925.1,8925.1,8,3)
3192Please enter the MUMPS code to be executed to validate the selection of patient and Visit/Admission.
3193"^DD",8925.1,8925.1,8,4)
3194D HELP1^TIUFXHLX(8)
3195"^DD",8925.1,8925.1,8,9)
3196@
3197"^DD",8925.1,8925.1,8,21,0)
3198^^7^7^2980126^^
3199"^DD",8925.1,8925.1,8,21,1,0)
3200Applies to Types Class, Document Class, Title. This is the M-Code to be
3201"^DD",8925.1,8925.1,8,21,2,0)
3202invoked when Validating the visit and other fixed field information on a
3203"^DD",8925.1,8925.1,8,21,3,0)
3204record during entry/edit. User is asked to OK or to correct the
3205"^DD",8925.1,8925.1,8,21,4,0)
3206information.
3207"^DD",8925.1,8925.1,8,21,5,0)
3208
3209"^DD",8925.1,8925.1,8,21,6,0)
3210Heritable. TECHNICAL field. For information on editing heritable fields,
3211"^DD",8925.1,8925.1,8,21,7,0)
3212see Technical field Edit Template.
3213"^DD",8925.1,8925.1,8,"DT")
32142961022
3215"^DD",8925.1,8925.1,9,0)
3216OBJECT METHOD^KX^^9;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3217"^DD",8925.1,8925.1,9,3)
3218This is Standard MUMPS code.
3219"^DD",8925.1,8925.1,9,9)
3220@
3221"^DD",8925.1,8925.1,9,21,0)
3222^^3^3^2980122^
3223"^DD",8925.1,8925.1,9,21,1,0)
3224Applies to Objects. This M-Code is invoked when a document is entered
3225"^DD",8925.1,8925.1,9,21,2,0)
3226whose boilerplate text contains the object. Extracted data are inserted
3227"^DD",8925.1,8925.1,9,21,3,0)
3228into document text. Author then edits/adds to text. TECHNICAL field.
3229"^DD",8925.1,8925.1,9,"DT")
32302961022
3231"^DD",8925.1,8925.1,10,0)
3232ITEM^8925.14P^^10;0
3233"^DD",8925.1,8925.1,11,0)
3234STAT AUTO PRINT EVENT^8925.111SA^^11;0
3235"^DD",8925.1,8925.1,11,21,0)
3236^^35^35^2970220^
3237"^DD",8925.1,8925.1,11,21,1,0)
3238This parameter applies only to stat documents.
3239"^DD",8925.1,8925.1,11,21,2,0)
3240
3241"^DD",8925.1,8925.1,11,21,3,0)
3242This parameter determines at what stage(s) a document should be
3243"^DD",8925.1,8925.1,11,21,4,0)
3244automatically printed for chart, either singly when document is ready, or
3245"^DD",8925.1,8925.1,11,21,5,0)
3246in batch mode.
3247"^DD",8925.1,8925.1,11,21,6,0)
3248
3249"^DD",8925.1,8925.1,11,21,7,0)
3250Some documents will need to be printed for chart only when they are
3251"^DD",8925.1,8925.1,11,21,8,0)
3252complete, ie have obtained all expected signatures and cosignatures.
3253"^DD",8925.1,8925.1,11,21,9,0)
3254Others should perhaps be printed for chart at an earlier stage, allowing
3255"^DD",8925.1,8925.1,11,21,10,0)
3256earlier chart access, and then be reprinted when complete. Documents may
3257"^DD",8925.1,8925.1,11,21,11,0)
3258also need to be reprinted AFTER completion for certain events such as
3259"^DD",8925.1,8925.1,11,21,12,0)
3260amendment.
3261"^DD",8925.1,8925.1,11,21,13,0)
3262
3263"^DD",8925.1,8925.1,11,21,14,0)
3264Any event which should trigger auto printing of the document should be
3265"^DD",8925.1,8925.1,11,21,15,0)
3266entered as an auto print event.
3267"^DD",8925.1,8925.1,11,21,16,0)
3268
3269"^DD",8925.1,8925.1,11,21,17,0)
3270- SIGNED means firstline signature, as opposed to secondline cosignature.
3271"^DD",8925.1,8925.1,11,21,18,0)
3272- COSIGNED, OPTIONAL, INCOMPLETE means when an incomplete document obtains
3273"^DD",8925.1,8925.1,11,21,19,0)
3274an optional cosignature.
3275"^DD",8925.1,8925.1,11,21,20,0)
3276- COSIGNED, OPTIONAL, COMPLETED means when a previously completed
3277"^DD",8925.1,8925.1,11,21,21,0)
3278document obtains an optional cosignature, namely, a walkup.
3279"^DD",8925.1,8925.1,11,21,22,0)
3280- COMPLETED means when some event occurs that completes the document, for
3281"^DD",8925.1,8925.1,11,21,23,0)
3282example the document obtains its last expected optional cosignature.
3283"^DD",8925.1,8925.1,11,21,24,0)
3284
3285"^DD",8925.1,8925.1,11,21,25,0)
3286If one event occurs to a document and corresponds to two selected print
3287"^DD",8925.1,8925.1,11,21,26,0)
3288events (such as COMPLETED and COSIGNED OPTIONAL INCOMPLETE), the document
3289"^DD",8925.1,8925.1,11,21,27,0)
3290will only print once.
3291"^DD",8925.1,8925.1,11,21,28,0)
3292
3293"^DD",8925.1,8925.1,11,21,29,0)
3294If parameter is not entered and Document Definition has no ancestor to
3295"^DD",8925.1,8925.1,11,21,30,0)
3296inherit from, parameter assumes default value N for NONE. If parameter is
3297"^DD",8925.1,8925.1,11,21,31,0)
3298not entered and Document Definition has a parent to inherit from, then
3299"^DD",8925.1,8925.1,11,21,32,0)
3300parameter assumes value (assumed or explicit) of parent print events. If
3301"^DD",8925.1,8925.1,11,21,33,0)
3302parameter is non applicable because Document Definition does not allow
3303"^DD",8925.1,8925.1,11,21,34,0)
3304stat documents, or because Document Definition does not allow auto
3305"^DD",8925.1,8925.1,11,21,35,0)
3306printing, enter N for NONE.
3307"^DD",8925.1,8925.1,11,"DT")
33082940621
3309"^DD",8925.1,8925.1,12,0)
3310ROUTINE AUTO PRINT EVENT^8925.112SA^^12;0
3311"^DD",8925.1,8925.1,12,21,0)
3312^^5^5^2970220^
3313"^DD",8925.1,8925.1,12,21,1,0)
3314This parameter applies to routine (non-stat) documents only. Documents
3315"^DD",8925.1,8925.1,12,21,2,0)
3316whose Document Definitions do not allow stat documents are considered
3317"^DD",8925.1,8925.1,12,21,3,0)
3318routine.
3319"^DD",8925.1,8925.1,12,21,4,0)
3320
3321"^DD",8925.1,8925.1,12,21,5,0)
3322See parameter STAT AUTO PRINT EVENT for description.
3323"^DD",8925.1,8925.1,13,0)
3324PROCESSING STEPS^8925.113P^^13;0
3325"^DD",8925.1,8925.1,13,21,0)
3326^^3^3^2950216^^
3327"^DD",8925.1,8925.1,13,21,1,0)
3328This sub-file contains the optional and required steps for processing any
3329"^DD",8925.1,8925.1,13,21,2,0)
3330document, along with the states (e.g., unverified -> unsigned) that a given
3331"^DD",8925.1,8925.1,13,21,3,0)
3332step (e.g., verification) moves the document between.
3333"^DD",8925.1,8925.1,14,0)
3334DIALOG^8925.114^^DIALOG;0
3335"^DD",8925.1,8925.1,14,21,0)
3336^^2^2^2950606^
3337"^DD",8925.1,8925.1,14,21,1,0)
3338This sub-file contains the data necessary to handle server-based definition
3339"^DD",8925.1,8925.1,14,21,2,0)
3340for fixed-field data capture in TIU.
3341"^DD",8925.1,8925.1,99,0)
3342TIMESTAMP^F^^99;1^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>15!($L(X)<1) X
3343"^DD",8925.1,8925.1,99,1,0)
3344^.1
3345"^DD",8925.1,8925.1,99,1,1,0)
33468925.1^AM^MUMPS
3347"^DD",8925.1,8925.1,99,1,1,1)
3348D SET^TIUDD
3349"^DD",8925.1,8925.1,99,1,1,2)
3350D KILL^TIUDD
3351"^DD",8925.1,8925.1,99,1,1,"%D",0)
3352^^2^2^2950911^^^
3353"^DD",8925.1,8925.1,99,1,1,"%D",1,0)
3354This cross-reference invokes menu compilation in ^XUTL("XQORM",
3355"^DD",8925.1,8925.1,99,1,1,"%D",2,0)
3356DA;TIU(8925.1, when the TIMESTAMP field is modified.
3357"^DD",8925.1,8925.1,99,1,1,"DT")
33582940720
3359"^DD",8925.1,8925.1,99,3)
3360Answer must be 1-15 characters in length.
3361"^DD",8925.1,8925.1,99,"DT")
33622940720
3363"^DD",8925.1,8925.1,1501,0)
3364VHA 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
3365"^DD",8925.1,8925.1,1501,1,0)
3366^.1
3367"^DD",8925.1,8925.1,1501,1,1,0)
33688925.1^ALOINC
3369"^DD",8925.1,8925.1,1501,1,1,1)
3370S ^TIU(8925.1,"ALOINC",$E(X,1,30),DA)=""
3371"^DD",8925.1,8925.1,1501,1,1,2)
3372K ^TIU(8925.1,"ALOINC",$E(X,1,30),DA)
3373"^DD",8925.1,8925.1,1501,1,1,3)
3374** DO NOT DELETE **
3375"^DD",8925.1,8925.1,1501,1,1,"%D",0)
3376^^2^2^3070306^
3377"^DD",8925.1,8925.1,1501,1,1,"%D",1,0)
3378This REGULAR FileMan cross-reference will facilitate searching by VHA
3379"^DD",8925.1,8925.1,1501,1,1,"%D",2,0)
3380Enterprise Standard Titles.
3381"^DD",8925.1,8925.1,1501,1,1,"DT")
33823070306
3383"^DD",8925.1,8925.1,1501,3)
3384Please identify the VHA Enterprise Title to which this local title should be mapped.
3385"^DD",8925.1,8925.1,1501,12)
3386Only ACTIVE Enterprise Titles may be selected.
3387"^DD",8925.1,8925.1,1501,12.1)
3388S DIC("S")="I '$$SCREEN^XTID(8926.1,"""",Y_"","")"
3389"^DD",8925.1,8925.1,1501,21,0)
3390^.001^2^2^3070321^^
3391"^DD",8925.1,8925.1,1501,21,1,0)
3392This reference to the VHA ENTERPRISE STANDARD TITLE FILE provides for the
3393"^DD",8925.1,8925.1,1501,21,2,0)
3394mapping of local titles to the Enterprise Standard Titles.
3395"^DD",8925.1,8925.1,1501,"DT")
33963070321
3397"^DD",8925.1,8925.1,1502,0)
3398MAP ATTEMPTED^D^^15;2^S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
3399"^DD",8925.1,8925.1,1502,3)
3400Enter the date/time at which mapping was attempted.
3401"^DD",8925.1,8925.1,1502,21,0)
3402^^2^2^3060301^
3403"^DD",8925.1,8925.1,1502,21,1,0)
3404This is the date/time at which the user attempted to map the Local Title
3405"^DD",8925.1,8925.1,1502,21,2,0)
3406to a VHA Enterprise Title.
3407"^DD",8925.1,8925.1,1502,"DT")
34083060301
3409"^DD",8925.1,8925.1,1503,0)
3410MAP ATTEMPTED BY^P200'^VA(200,^15;3^Q
3411"^DD",8925.1,8925.1,1503,3)
3412Specify the person who attempted to map the title.
3413"^DD",8925.1,8925.1,1503,21,0)
3414^^2^2^3060301^
3415"^DD",8925.1,8925.1,1503,21,1,0)
3416This is the person who attempted to map the Local Title to a VHA
3417"^DD",8925.1,8925.1,1503,21,2,0)
3418Enterprise Title.
3419"^DD",8925.1,8925.1,1503,"DT")
34203060301
3421"^DD",8925.1,8925.11,0)
3422UPLOAD DELIMITED ASCII HEADER SUB-FIELD^^1^8
3423"^DD",8925.1,8925.11,0,"DT")
34242951004
3425"^DD",8925.1,8925.11,0,"ID",.02)
3426W " ",$P(^(0),U,2)
3427"^DD",8925.1,8925.11,0,"IX","B",8925.11,.01)
3428
3429"^DD",8925.1,8925.11,0,"IX","C",8925.11,.02)
3430
3431"^DD",8925.1,8925.11,0,"IX","D",8925.11,.03)
3432
3433"^DD",8925.1,8925.11,0,"IX","E",8925.11,.04)
3434
3435"^DD",8925.1,8925.11,0,"NM","UPLOAD DELIMITED ASCII HEADER")
3436
3437"^DD",8925.1,8925.11,0,"UP")
34388925.1
3439"^DD",8925.1,8925.11,.01,0)
3440HEADER PIECE^MNJ2,0X^^0;1^K:+X'=X!(X>30)!(X<1)!(X?.E1"."1N.N) X S:$D(X) DINUM=X
3441"^DD",8925.1,8925.11,.01,1,0)
3442^.1
3443"^DD",8925.1,8925.11,.01,1,1,0)
34448925.11^B
3445"^DD",8925.1,8925.11,.01,1,1,1)
3446S ^TIU(8925.1,DA(1),"ITEM","B",$E(X,1,30),DA)=""
3447"^DD",8925.1,8925.11,.01,1,1,2)
3448K ^TIU(8925.1,DA(1),"ITEM","B",$E(X,1,30),DA)
3449"^DD",8925.1,8925.11,.01,3)
3450Enter the delimiter-piece for the next header item.
3451"^DD",8925.1,8925.11,.01,21,0)
3452^^2^2^2970107^
3453"^DD",8925.1,8925.11,.01,21,1,0)
3454This is the number for this piece (item) of the header. Start with
3455"^DD",8925.1,8925.11,.01,21,2,0)
3456number 1 for the first piece.
3457"^DD",8925.1,8925.11,.01,"DT")
34582921021
3459"^DD",8925.1,8925.11,.02,0)
3460ITEM NAME^F^^0;2^K:$L(X)>30!($L(X)<2) X
3461"^DD",8925.1,8925.11,.02,1,0)
3462^.1
3463"^DD",8925.1,8925.11,.02,1,1,0)
34648925.11^C
3465"^DD",8925.1,8925.11,.02,1,1,1)
3466S ^TIU(8925.1,DA(1),"ITEM","C",$E(X,1,30),DA)=""
3467"^DD",8925.1,8925.11,.02,1,1,2)
3468K ^TIU(8925.1,DA(1),"ITEM","C",$E(X,1,30),DA)
3469"^DD",8925.1,8925.11,.02,1,1,"%D",0)
3470^^2^2^2921021^
3471"^DD",8925.1,8925.11,.02,1,1,"%D",1,0)
3472This REGULAR FileMan cross-reference on the ITEM NAME is used in the
3473"^DD",8925.1,8925.11,.02,1,1,"%D",2,0)
3474look-up and edit process.
3475"^DD",8925.1,8925.11,.02,1,1,"DT")
34762920605
3477"^DD",8925.1,8925.11,.02,3)
3478Enter the name of the header item.
3479"^DD",8925.1,8925.11,.02,21,0)
3480^^2^2^2970107^
3481"^DD",8925.1,8925.11,.02,21,1,0)
3482This is the name of the item in the ASCII message header. Item Name is
3483"^DD",8925.1,8925.11,.02,21,2,0)
3484used in help messages for the person dictating a document.
3485"^DD",8925.1,8925.11,.02,"DT")
34862921021
3487"^DD",8925.1,8925.11,.03,0)
3488FIELD NUMBER^F^^0;3^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>10!($L(X)<1) X
3489"^DD",8925.1,8925.11,.03,1,0)
3490^.1
3491"^DD",8925.1,8925.11,.03,1,1,0)
34928925.11^D
3493"^DD",8925.1,8925.11,.03,1,1,1)
3494S ^TIU(8925.1,DA(1),"ITEM","D",$E(X,1,30),DA)=""
3495"^DD",8925.1,8925.11,.03,1,1,2)
3496K ^TIU(8925.1,DA(1),"ITEM","D",$E(X,1,30),DA)
3497"^DD",8925.1,8925.11,.03,1,1,"%D",0)
3498^^3^3^2921021^
3499"^DD",8925.1,8925.11,.03,1,1,"%D",1,0)
3500This REGULAR FileMan cross-reference by field number is used by the
3501"^DD",8925.1,8925.11,.03,1,1,"%D",2,0)
3502filer/router to identify header-pieces with field numbers in the target
3503"^DD",8925.1,8925.11,.03,1,1,"%D",3,0)
3504file.
3505"^DD",8925.1,8925.11,.03,1,1,"DT")
35062921021
3507"^DD",8925.1,8925.11,.03,3)
3508Enter the FIELD # of the item in the target file.
3509"^DD",8925.1,8925.11,.03,21,0)
3510^^2^2^2970107^
3511"^DD",8925.1,8925.11,.03,21,1,0)
3512This is the field number in the target file which corresponds to this
3513"^DD",8925.1,8925.11,.03,21,2,0)
3514header item.
3515"^DD",8925.1,8925.11,.03,"DT")
35162921021
3517"^DD",8925.1,8925.11,.04,0)
3518LOOKUP 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
3519"^DD",8925.1,8925.11,.04,1,0)
3520^.1
3521"^DD",8925.1,8925.11,.04,1,1,0)
35228925.11^E
3523"^DD",8925.1,8925.11,.04,1,1,1)
3524S ^TIU(8925.1,DA(1),"ITEM","E",$E(X,1,30),DA)=""
3525"^DD",8925.1,8925.11,.04,1,1,2)
3526K ^TIU(8925.1,DA(1),"ITEM","E",$E(X,1,30),DA)
3527"^DD",8925.1,8925.11,.04,1,1,"%D",0)
3528^^3^3^2921109^
3529"^DD",8925.1,8925.11,.04,1,1,"%D",1,0)
3530This cross-reference is used by the router/filer to determine which pieces
3531"^DD",8925.1,8925.11,.04,1,1,"%D",2,0)
3532of the header should be set into special variables which may be required by
3533"^DD",8925.1,8925.11,.04,1,1,"%D",3,0)
3534the lookup routine.
3535"^DD",8925.1,8925.11,.04,1,1,"DT")
35362921109
3537"^DD",8925.1,8925.11,.04,3)
3538Enter the required local variable into which this piece will be set.
3539"^DD",8925.1,8925.11,.04,21,0)
3540^^11^11^2970107^
3541"^DD",8925.1,8925.11,.04,21,1,0)
3542This field specifies the local variable name into which this piece of the
3543"^DD",8925.1,8925.11,.04,21,2,0)
3544message header will be set. The local variable is used by the Look-Up
3545"^DD",8925.1,8925.11,.04,21,3,0)
3546Method. For example, if this piece of the header is the patient social
3547"^DD",8925.1,8925.11,.04,21,4,0)
3548security number, the Lookup Local Variable Name might be TIUSSN. The
3549"^DD",8925.1,8925.11,.04,21,5,0)
3550social security number as written by the transcriptionist is first
3551"^DD",8925.1,8925.11,.04,21,6,0)
3552transformed by any existing Transform Code, and then set into this
3553"^DD",8925.1,8925.11,.04,21,7,0)
3554variable (e.g. TIUSSN) for use in Look-Up Method code.
3555"^DD",8925.1,8925.11,.04,21,8,0)
3556
3557"^DD",8925.1,8925.11,.04,21,9,0)
3558Lookup Local Variable Name is necessary only if the information in this
3559"^DD",8925.1,8925.11,.04,21,10,0)
3560piece is required in order to look up the appropriate entry in the target
3561"^DD",8925.1,8925.11,.04,21,11,0)
3562file.
3563"^DD",8925.1,8925.11,.04,"DT")
35642921109
3565"^DD",8925.1,8925.11,.05,0)
3566EXAMPLE ENTRY^F^^0;5^K:$L(X)>39!($L(X)<2) X
3567"^DD",8925.1,8925.11,.05,3)
3568Answer must be 2-39 characters in length.
3569"^DD",8925.1,8925.11,.05,21,0)
3570^^10^10^2970108^^
3571"^DD",8925.1,8925.11,.05,21,1,0)
3572This field is used to store sample data for this item in the form the
3573"^DD",8925.1,8925.11,.05,21,2,0)
3574transcriptionist is expected to use when transcribing it. For example, if
3575"^DD",8925.1,8925.11,.05,21,3,0)
3576a patient has Social Security Number 555-12-1212, and the transcriptionist
3577"^DD",8925.1,8925.11,.05,21,4,0)
3578is expected to write 555-12-1212, then an Example Entry should have the
3579"^DD",8925.1,8925.11,.05,21,5,0)
3580form 555-12-1212.
3581"^DD",8925.1,8925.11,.05,21,6,0)
3582
3583"^DD",8925.1,8925.11,.05,21,7,0)
3584The Transform Code, if it exists, then transforms the transcribed Social
3585"^DD",8925.1,8925.11,.05,21,8,0)
3586Security Number 555-12-1212 into the appropriate format for the target
3587"^DD",8925.1,8925.11,.05,21,9,0)
3588file before using the Social Security Number to look-up the appropriate
3589"^DD",8925.1,8925.11,.05,21,10,0)
3590target file entry and/or before entering it in the target file.
3591"^DD",8925.1,8925.11,.05,"DT")
35922930224
3593"^DD",8925.1,8925.11,.06,0)
3594CLINICIAN MUST DICTATE^S^1:YES;0:NO;^0;6^Q
3595"^DD",8925.1,8925.11,.06,3)
3596Answer yes if this field needs to be dictated by the clinician
3597"^DD",8925.1,8925.11,.06,21,0)
3598^^5^5^2970108^
3599"^DD",8925.1,8925.11,.06,21,1,0)
3600States whether or not this piece of the header should be dictated by the
3601"^DD",8925.1,8925.11,.06,21,2,0)
3602Clinician. Will be used by the Clinician Help routine to determine if
3603"^DD",8925.1,8925.11,.06,21,3,0)
3604this field should be shown as data that should be dictated. (Some pieces
3605"^DD",8925.1,8925.11,.06,21,4,0)
3606can be entered by the transcriber without being dictated, such as the
3607"^DD",8925.1,8925.11,.06,21,5,0)
3608transcriber identification).
3609"^DD",8925.1,8925.11,.06,"DT")
36102930423
3611"^DD",8925.1,8925.11,.07,0)
3612REQUIRED FIELD?^S^1:YES;0:NO;^0;7^Q
3613"^DD",8925.1,8925.11,.07,3)
3614Please indicate whether the field is required.
3615"^DD",8925.1,8925.11,.07,21,0)
3616^^5^5^2970108^
3617"^DD",8925.1,8925.11,.07,21,1,0)
3618This field is used to determine whether a given header piece is required
3619"^DD",8925.1,8925.11,.07,21,2,0)
3620by the application (e.g., Author and Attending Physician may be required
3621"^DD",8925.1,8925.11,.07,21,3,0)
3622for the ongoing processing of a Discharge Summary). Records lacking
3623"^DD",8925.1,8925.11,.07,21,4,0)
3624required fields WILL be entered if possible into the target file but will
3625"^DD",8925.1,8925.11,.07,21,5,0)
3626generate Missing Field Error Alerts.
3627"^DD",8925.1,8925.11,.07,"DT")
36282951004
3629"^DD",8925.1,8925.11,1,0)
3630TRANSFORM CODE^K^^1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3631"^DD",8925.1,8925.11,1,3)
3632This is Standard MUMPS code.
3633"^DD",8925.1,8925.11,1,9)
3634@
3635"^DD",8925.1,8925.11,1,21,0)
3636^^11^11^2970108^
3637"^DD",8925.1,8925.11,1,21,1,0)
3638This standard MUMPS code transforms the transcribed value of the header
3639"^DD",8925.1,8925.11,1,21,2,0)
3640piece into a format acceptable to FileMan (e.g., patient social security
3641"^DD",8925.1,8925.11,1,21,3,0)
3642number 555-12-1212 must be transformed to 555121212 or to whatever
3643"^DD",8925.1,8925.11,1,21,4,0)
3644(external) format FileMan accepts when a user edits the social security
3645"^DD",8925.1,8925.11,1,21,5,0)
3646number field in the target file).
3647"^DD",8925.1,8925.11,1,21,6,0)
3648
3649"^DD",8925.1,8925.11,1,21,7,0)
3650Field values are transformed before being set into Special Lookup
3651"^DD",8925.1,8925.11,1,21,8,0)
3652Variables and before being set into Target Text File Fields.
3653"^DD",8925.1,8925.11,1,21,9,0)
3654
3655"^DD",8925.1,8925.11,1,21,10,0)
3656Field is necessary only if transcribed piece is not in the format Fileman
3657"^DD",8925.1,8925.11,1,21,11,0)
3658accepts for the target file.
3659"^DD",8925.1,8925.11,1,"DT")
36602930219
3661"^DD",8925.1,8925.111,0)
3662STAT AUTO PRINT EVENT SUB-FIELD^^.01^1
3663"^DD",8925.1,8925.111,0,"DT")
36642940621
3665"^DD",8925.1,8925.111,0,"IX","B",8925.111,.01)
3666
3667"^DD",8925.1,8925.111,0,"NM","STAT AUTO PRINT EVENT")
3668
3669"^DD",8925.1,8925.111,0,"UP")
36708925.1
3671"^DD",8925.1,8925.111,.01,0)
3672STAT 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
3673"^DD",8925.1,8925.111,.01,1,0)
3674^.1
3675"^DD",8925.1,8925.111,.01,1,1,0)
36768925.111^B
3677"^DD",8925.1,8925.111,.01,1,1,1)
3678S ^TIU(8925.1,DA(1),11,"B",$E(X,1,30),DA)=""
3679"^DD",8925.1,8925.111,.01,1,1,2)
3680K ^TIU(8925.1,DA(1),11,"B",$E(X,1,30),DA)
3681"^DD",8925.1,8925.111,.01,3)
3682Enter every event which should trigger auto printing of document whenever the event occurs.
3683"^DD",8925.1,8925.111,.01,"DT")
36842941027
3685"^DD",8925.1,8925.112,0)
3686ROUTINE AUTO PRINT EVENT SUB-FIELD^^.01^1
3687"^DD",8925.1,8925.112,0,"DT")
36882940621
3689"^DD",8925.1,8925.112,0,"IX","B",8925.112,.01)
3690
3691"^DD",8925.1,8925.112,0,"NM","ROUTINE AUTO PRINT EVENT")
3692
3693"^DD",8925.1,8925.112,0,"UP")
36948925.1
3695"^DD",8925.1,8925.112,.01,0)
3696ROUTINE 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
3697"^DD",8925.1,8925.112,.01,1,0)
3698^.1
3699"^DD",8925.1,8925.112,.01,1,1,0)
37008925.112^B
3701"^DD",8925.1,8925.112,.01,1,1,1)
3702S ^TIU(8925.1,DA(1),12,"B",$E(X,1,30),DA)=""
3703"^DD",8925.1,8925.112,.01,1,1,2)
3704K ^TIU(8925.1,DA(1),12,"B",$E(X,1,30),DA)
3705"^DD",8925.1,8925.112,.01,3)
3706Enter an event which should trigger auto printing of routine documents.
3707"^DD",8925.1,8925.112,.01,"DT")
37082940621
3709"^DD",8925.1,8925.113,0)
3710PROCESSING STEPS SUB-FIELD^^.05^5
3711"^DD",8925.1,8925.113,0,"DT")
37122950216
3713"^DD",8925.1,8925.113,0,"IX","B",8925.113,.01)
3714
3715"^DD",8925.1,8925.113,0,"NM","PROCESSING STEPS")
3716
3717"^DD",8925.1,8925.113,0,"UP")
37188925.1
3719"^DD",8925.1,8925.113,.01,0)
3720PROCESSING STEP^MP8930.8'^USR(8930.8,^0;1^Q
3721"^DD",8925.1,8925.113,.01,1,0)
3722^.1
3723"^DD",8925.1,8925.113,.01,1,1,0)
37248925.113^B
3725"^DD",8925.1,8925.113,.01,1,1,1)
3726S ^TIU(8925.1,DA(1),13,"B",$E(X,1,30),DA)=""
3727"^DD",8925.1,8925.113,.01,1,1,2)
3728K ^TIU(8925.1,DA(1),13,"B",$E(X,1,30),DA)
3729"^DD",8925.1,8925.113,.01,3)
3730Please indicate a step involved in processing this document.
3731"^DD",8925.1,8925.113,.01,21,0)
3732^^2^2^2950216^
3733"^DD",8925.1,8925.113,.01,21,1,0)
3734This is a step or action (e.g., verification) in the processing of a document
3735"^DD",8925.1,8925.113,.01,21,2,0)
3736that moves it from one state (e.g., unverified) to another (e.g., unsigned).
3737"^DD",8925.1,8925.113,.01,"DT")
37382950216
3739"^DD",8925.1,8925.113,.02,0)
3740SEQUENCE^NJ3,0^^0;2^K:+X'=X!(X>999)!(X<0)!(X?.E1"."1N.N) X
3741"^DD",8925.1,8925.113,.02,3)
3742Indicate the order in processing this document where this step should occur.
3743"^DD",8925.1,8925.113,.02,21,0)
3744^^4^4^2950216^
3745"^DD",8925.1,8925.113,.02,21,1,0)
3746This is the serial sequence in the processing of the document in which the
3747"^DD",8925.1,8925.113,.02,21,2,0)
3748current step should ordinarily occur. This field is only necessary when the
3749"^DD",8925.1,8925.113,.02,21,3,0)
3750process in question must occur in a particular sequence (e.g., to insure
3751"^DD",8925.1,8925.113,.02,21,4,0)
3752that a document is always released from draft before it is verified).
3753"^DD",8925.1,8925.113,.02,"DT")
37542950216
3755"^DD",8925.1,8925.113,.03,0)
3756REQUIRED?^S^1:REQUIRED;0:OPTIONAL;^0;3^Q
3757"^DD",8925.1,8925.113,.03,3)
3758Indicate whether the step is required or optional
3759"^DD",8925.1,8925.113,.03,21,0)
3760^^4^4^2950216^
3761"^DD",8925.1,8925.113,.03,21,1,0)
3762This field specifies whether the step is required or optional for completion
3763"^DD",8925.1,8925.113,.03,21,2,0)
3764of the document (e.g., Dictation and transcription is the typical means by
3765"^DD",8925.1,8925.113,.03,21,3,0)
3766which Discharge Summaries are acquired, but they may be entered directly by
3767"^DD",8925.1,8925.113,.03,21,4,0)
3768the provider, if preferred).
3769"^DD",8925.1,8925.113,.03,"DT")
37702950216
3771"^DD",8925.1,8925.113,.04,0)
3772RESULTING STATUS^P8930.6'^USR(8930.6,^0;4^Q
3773"^DD",8925.1,8925.113,.04,3)
3774Indicate the status resulting from the step being taken.
3775"^DD",8925.1,8925.113,.04,21,0)
3776^^4^4^2950216^
3777"^DD",8925.1,8925.113,.04,21,1,0)
3778This is the status of the document following completion of the step in
3779"^DD",8925.1,8925.113,.04,21,2,0)
3780question. For instance, if a discharge summary is to be registered as
3781"^DD",8925.1,8925.113,.04,21,3,0)
3782unsigned following verification, this would be indicated in the RESULTING
3783"^DD",8925.1,8925.113,.04,21,4,0)
3784STATUS field.
3785"^DD",8925.1,8925.113,.04,"DT")
37862950216
3787"^DD",8925.1,8925.113,.05,0)
3788CONDITION TEXT^F^^0;5^K:$L(X)>40!($L(X)<3) X
3789"^DD",8925.1,8925.113,.05,3)
3790Condition under which the step will result in the status as indicated.
3791"^DD",8925.1,8925.113,.05,"DT")
37922950216
3793"^DD",8925.1,8925.114,0)
3794DIALOG SUB-FIELD^^117^12
3795"^DD",8925.1,8925.114,0,"DT")
37962951002
3797"^DD",8925.1,8925.114,0,"IX","AS",8925.114,.03)
3798
3799"^DD",8925.1,8925.114,0,"IX","B",8925.114,.01)
3800
3801"^DD",8925.1,8925.114,0,"NM","DIALOG")
3802
3803"^DD",8925.1,8925.114,0,"UP")
38048925.1
3805"^DD",8925.1,8925.114,.01,0)
3806PROMPT^MF^^0;1^K:$L(X)>30!($L(X)<2) X
3807"^DD",8925.1,8925.114,.01,1,0)
3808^.1
3809"^DD",8925.1,8925.114,.01,1,1,0)
38108925.114^B
3811"^DD",8925.1,8925.114,.01,1,1,1)
3812S ^TIU(8925.1,DA(1),"DIALOG","B",$E(X,1,30),DA)=""
3813"^DD",8925.1,8925.114,.01,1,1,2)
3814K ^TIU(8925.1,DA(1),"DIALOG","B",$E(X,1,30),DA)
3815"^DD",8925.1,8925.114,.01,3)
3816Enter the caption with which the user will be prompted.
3817"^DD",8925.1,8925.114,.01,21,0)
3818^^2^2^2950606^^^
3819"^DD",8925.1,8925.114,.01,21,1,0)
3820This is the prompt with which the user will be presented during interactive
3821"^DD",8925.1,8925.114,.01,21,2,0)
3822entry of the document.
3823"^DD",8925.1,8925.114,.01,"DT")
38242950606
3825"^DD",8925.1,8925.114,.02,0)
3826ITEM NAME^F^^0;2^K:$L(X)>50!($L(X)<2) X
3827"^DD",8925.1,8925.114,.02,3)
3828Answer must be 2-50 characters in length.
3829"^DD",8925.1,8925.114,.02,21,0)
3830^^2^2^2950606^^
3831"^DD",8925.1,8925.114,.02,21,1,0)
3832This is a descriptive name for the datum which will help descibe the prompt
3833"^DD",8925.1,8925.114,.02,21,2,0)
3834for the user.
3835"^DD",8925.1,8925.114,.02,"DT")
38362950606
3837"^DD",8925.1,8925.114,.03,0)
3838SEQUENCE^NJ3,0^^0;3^K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X
3839"^DD",8925.1,8925.114,.03,1,0)
3840^.1
3841"^DD",8925.1,8925.114,.03,1,1,0)
38428925.114^AS
3843"^DD",8925.1,8925.114,.03,1,1,1)
3844S ^TIU(8925.1,DA(1),"DIALOG","AS",$E(X,1,30),DA)=""
3845"^DD",8925.1,8925.114,.03,1,1,2)
3846K ^TIU(8925.1,DA(1),"DIALOG","AS",$E(X,1,30),DA)
3847"^DD",8925.1,8925.114,.03,1,1,"%D",0)
3848^^2^2^2950606^
3849"^DD",8925.1,8925.114,.03,1,1,"%D",1,0)
3850This REGULAR FileMan Cross-reference on the sequence sub-field of the
3851"^DD",8925.1,8925.114,.03,1,1,"%D",2,0)
3852Dialog Multiple will facilitate appropriate serialization of prompts.
3853"^DD",8925.1,8925.114,.03,1,1,"DT")
38542950606
3855"^DD",8925.1,8925.114,.03,3)
3856Type a Number between 1 and 999, 0 Decimal Digits
3857"^DD",8925.1,8925.114,.03,21,0)
3858^^2^2^2950606^
3859"^DD",8925.1,8925.114,.03,21,1,0)
3860This is the sequence of the prompt within the dialog. On the Windows Client
3861"^DD",8925.1,8925.114,.03,21,2,0)
3862this will correspond with the Tab Order Property of the prompt.
3863"^DD",8925.1,8925.114,.03,"DT")
38642950606
3865"^DD",8925.1,8925.114,.04,0)
3866FIELD^FX^^0;4^K:$L(X)>10!($L(X)<1)!(+X<0) X
3867"^DD",8925.1,8925.114,.04,3)
3868Enter the field in the TARGET FILE in which the response is to be stored.
3869"^DD",8925.1,8925.114,.04,4)
3870
3871"^DD",8925.1,8925.114,.04,21,0)
3872^^2^2^2970116^^
3873"^DD",8925.1,8925.114,.04,21,1,0)
3874This is the field in the target file in which the user's response will be
3875"^DD",8925.1,8925.114,.04,21,2,0)
3876stored.
3877"^DD",8925.1,8925.114,.04,"DT")
38782970116
3879"^DD",8925.1,8925.114,.05,0)
3880REQUIRED^S^1:YES;0:NO;^0;5^Q
3881"^DD",8925.1,8925.114,.05,3)
3882Indicate whether a response is required.
3883"^DD",8925.1,8925.114,.05,21,0)
3884^^2^2^2950607^
3885"^DD",8925.1,8925.114,.05,21,1,0)
3886Please indicate whether a response to this prompt is required, in order to
3887"^DD",8925.1,8925.114,.05,21,2,0)
3888complete the dialog.
3889"^DD",8925.1,8925.114,.05,"DT")
38902950607
3891"^DD",8925.1,8925.114,.06,0)
3892VISIBLE^S^0:NO;1:YES;^0;6^Q
3893"^DD",8925.1,8925.114,.06,3)
3894Indicate wheter the prompt will be visible to the user.
3895"^DD",8925.1,8925.114,.06,21,0)
3896^^2^2^2950607^
3897"^DD",8925.1,8925.114,.06,21,1,0)
3898This field specifies whether a given datum will be prompted for, or
3899"^DD",8925.1,8925.114,.06,21,2,0)
3900"stuffed," based on execution of the SET METHOD for a given prompt.
3901"^DD",8925.1,8925.114,.06,"DT")
39022950607
3903"^DD",8925.1,8925.114,1,0)
3904SET METHOD^K^^1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3905"^DD",8925.1,8925.114,1,3)
3906This is Standard MUMPS code.
3907"^DD",8925.1,8925.114,1,9)
3908@
3909"^DD",8925.1,8925.114,1,21,0)
3910^^5^5^2950607^^^
3911"^DD",8925.1,8925.114,1,21,1,0)
3912This is the mumps code for determining the default value of an interactive
3913"^DD",8925.1,8925.114,1,21,2,0)
3914("visible") prompt, and for setting the value to be non-interactively
3915"^DD",8925.1,8925.114,1,21,3,0)
3916"stuffed" on invokation of an "invisible" prompt. Regardless of the
3917"^DD",8925.1,8925.114,1,21,4,0)
3918syntactic approach (e.g., subroutine or extrinsic function, the return
3919"^DD",8925.1,8925.114,1,21,5,0)
3920value of the method should be placed in the local varible X.
3921"^DD",8925.1,8925.114,1,"DT")
39222950607
3923"^DD",8925.1,8925.114,101,0)
3924WINDOWS CONTROL^S^1:LongList;2:SimpleList;3:Edit;4:Memo;^W;1^Q
3925"^DD",8925.1,8925.114,101,3)
3926Enter the Windows control appropriate for this prompt
3927"^DD",8925.1,8925.114,101,21,0)
3928^^2^2^2950907^
3929"^DD",8925.1,8925.114,101,21,1,0)
3930Stores the type of Windows control necessary to get the data for this
3931"^DD",8925.1,8925.114,101,21,2,0)
3932prompt.
3933"^DD",8925.1,8925.114,101,"DT")
39342950907
3935"^DD",8925.1,8925.114,102,0)
3936API NAME^F^^W;2^K:$L(X)>30!($L(X)<3) X
3937"^DD",8925.1,8925.114,102,3)
3938Answer must be 3-30 characters in length.
3939"^DD",8925.1,8925.114,102,21,0)
3940^^3^3^2950907^
3941"^DD",8925.1,8925.114,102,21,1,0)
3942This is the API that should be called by the broker when the control is
3943"^DD",8925.1,8925.114,102,21,2,0)
3944used. How the API is used varies with the control. Examples are:
3945"^DD",8925.1,8925.114,102,21,3,0)
3946filling list boxes, getting boilerplate text, etc.
3947"^DD",8925.1,8925.114,102,"DT")
39482951002
3949"^DD",8925.1,8925.114,103,0)
3950API PARAMETER #1^F^^W;3^K:$L(X)>30!($L(X)<1) X
3951"^DD",8925.1,8925.114,103,3)
3952Answer must be 1-30 characters in length.
3953"^DD",8925.1,8925.114,103,21,0)
3954^^1^1^2950907^
3955"^DD",8925.1,8925.114,103,21,1,0)
3956A parameter that is used by the API may be stored here.
3957"^DD",8925.1,8925.114,103,"DT")
39582950907
3959"^DD",8925.1,8925.114,113,0)
3960WINDOWS CONDITION^K^^W3;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3961"^DD",8925.1,8925.114,113,3)
3962This is Standard MUMPS code.
3963"^DD",8925.1,8925.114,113,9)
3964@
3965"^DD",8925.1,8925.114,113,21,0)
3966^^3^3^2950907^
3967"^DD",8925.1,8925.114,113,21,1,0)
3968This is silent code which is executed when building the dialog for
3969"^DD",8925.1,8925.114,113,21,2,0)
3970Windows. It identifies which prompts should be included in the dialog.
3971"^DD",8925.1,8925.114,113,21,3,0)
3972The condition should leave $T failse if the prompt should not be asked.
3973"^DD",8925.1,8925.114,113,"DT")
39742950907
3975"^DD",8925.1,8925.114,117,0)
3976WINDOWS DEFAULT^K^^W7;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
3977"^DD",8925.1,8925.114,117,3)
3978This is Standard MUMPS code.
3979"^DD",8925.1,8925.114,117,9)
3980@
3981"^DD",8925.1,8925.114,117,21,0)
3982^^2^2^2950907^
3983"^DD",8925.1,8925.114,117,21,1,0)
3984This code should silently set the default value of a prompt when it is
3985"^DD",8925.1,8925.114,117,21,2,0)
3986selected.
3987"^DD",8925.1,8925.114,117,"DT")
39882950907
3989"^DD",8925.1,8925.12,0)
3990UPLOAD CAPTIONED ASCII HEADER SUB-FIELD^^1^8
3991"^DD",8925.1,8925.12,0,"DT")
39922951004
3993"^DD",8925.1,8925.12,0,"IX","B",8925.12,.01)
3994
3995"^DD",8925.1,8925.12,0,"IX","C",8925.12,.02)
3996
3997"^DD",8925.1,8925.12,0,"IX","D",8925.12,.03)
3998
3999"^DD",8925.1,8925.12,0,"IX","E",8925.12,.04)
4000
4001"^DD",8925.1,8925.12,0,"NM","UPLOAD CAPTIONED ASCII HEADER")
4002
4003"^DD",8925.1,8925.12,0,"UP")
40048925.1
4005"^DD",8925.1,8925.12,.01,0)
4006CAPTION^MF^^0;1^K:$L(X)>40!($L(X)<2) X
4007"^DD",8925.1,8925.12,.01,1,0)
4008^.1
4009"^DD",8925.1,8925.12,.01,1,1,0)
40108925.12^B
4011"^DD",8925.1,8925.12,.01,1,1,1)
4012S ^TIU(8925.1,DA(1),"HEAD","B",$E(X,1,30),DA)=""
4013"^DD",8925.1,8925.12,.01,1,1,2)
4014K ^TIU(8925.1,DA(1),"HEAD","B",$E(X,1,30),DA)
4015"^DD",8925.1,8925.12,.01,3)
4016Answer must be 2-40 characters in length.
4017"^DD",8925.1,8925.12,.01,21,0)
4018^^7^7^2970108^
4019"^DD",8925.1,8925.12,.01,21,1,0)
4020NOTE: Users can choose between two possible kinds of Upload Record
4021"^DD",8925.1,8925.12,.01,21,2,0)
4022Headers: Captioned or Delimited. Captioned headers should be used UNLESS
4023"^DD",8925.1,8925.12,.01,21,3,0)
4024the site has a way to generate upload headers automatically.
4025"^DD",8925.1,8925.12,.01,21,4,0)
4026
4027"^DD",8925.1,8925.12,.01,21,5,0)
4028CAPTION is the caption which the transcriber enters into the captioned
4029"^DD",8925.1,8925.12,.01,21,6,0)
4030upload record header immediately preceeding the item data. It serves to
4031"^DD",8925.1,8925.12,.01,21,7,0)
4032distinguish one item of data from the next. Example: PATIENT NAME
4033"^DD",8925.1,8925.12,.01,"DT")
40342930218
4035"^DD",8925.1,8925.12,.02,0)
4036ITEM NAME^F^^0;2^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>20!($L(X)<2) X
4037"^DD",8925.1,8925.12,.02,1,0)
4038^.1
4039"^DD",8925.1,8925.12,.02,1,1,0)
40408925.12^C
4041"^DD",8925.1,8925.12,.02,1,1,1)
4042S ^TIU(8925.1,DA(1),"HEAD","C",$E(X,1,30),DA)=""
4043"^DD",8925.1,8925.12,.02,1,1,2)
4044K ^TIU(8925.1,DA(1),"HEAD","C",$E(X,1,30),DA)
4045"^DD",8925.1,8925.12,.02,1,1,"%D",0)
4046^^2^2^2930122^
4047"^DD",8925.1,8925.12,.02,1,1,"%D",1,0)
4048This REGULAR FileMan cross-reference on the ITEM NAME is used in the look-up
4049"^DD",8925.1,8925.12,.02,1,1,"%D",2,0)
4050and filing processes.
4051"^DD",8925.1,8925.12,.02,1,1,"DT")
40522930122
4053"^DD",8925.1,8925.12,.02,3)
4054Enter the name of the header item.
4055"^DD",8925.1,8925.12,.02,21,0)
4056^^2^2^2970108^
4057"^DD",8925.1,8925.12,.02,21,1,0)
4058This is the name of the item in the ASCII message header. Item Name is
4059"^DD",8925.1,8925.12,.02,21,2,0)
4060used in help messages for the person dictating a document.
4061"^DD",8925.1,8925.12,.02,"DT")
40622930122
4063"^DD",8925.1,8925.12,.03,0)
4064FIELD NUMBER^F^^0;3^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>10!($L(X)<1) X
4065"^DD",8925.1,8925.12,.03,1,0)
4066^.1
4067"^DD",8925.1,8925.12,.03,1,1,0)
40688925.12^D
4069"^DD",8925.1,8925.12,.03,1,1,1)
4070S ^TIU(8925.1,DA(1),"HEAD","D",$E(X,1,30),DA)=""
4071"^DD",8925.1,8925.12,.03,1,1,2)
4072K ^TIU(8925.1,DA(1),"HEAD","D",$E(X,1,30),DA)
4073"^DD",8925.1,8925.12,.03,1,1,"%D",0)
4074^^2^2^2930122^
4075"^DD",8925.1,8925.12,.03,1,1,"%D",1,0)
4076This REGULAR FileMan cross-reference is used by the filer router to identify
4077"^DD",8925.1,8925.12,.03,1,1,"%D",2,0)
4078header fields with field numbers in the target file.
4079"^DD",8925.1,8925.12,.03,1,1,"DT")
40802930122
4081"^DD",8925.1,8925.12,.03,3)
4082Enter the FIELD # of the item in the target file.
4083"^DD",8925.1,8925.12,.03,21,0)
4084^^2^2^2970108^
4085"^DD",8925.1,8925.12,.03,21,1,0)
4086This is the FIELD # in the target file which corresponds to this header
4087"^DD",8925.1,8925.12,.03,21,2,0)
4088item and where this item of data will be stored.
4089"^DD",8925.1,8925.12,.03,"DT")
40902930122
4091"^DD",8925.1,8925.12,.04,0)
4092LOOKUP 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
4093"^DD",8925.1,8925.12,.04,1,0)
4094^.1
4095"^DD",8925.1,8925.12,.04,1,1,0)
40968925.12^E
4097"^DD",8925.1,8925.12,.04,1,1,1)
4098S ^TIU(8925.1,DA(1),"HEAD","E",$E(X,1,30),DA)=""
4099"^DD",8925.1,8925.12,.04,1,1,2)
4100K ^TIU(8925.1,DA(1),"HEAD","E",$E(X,1,30),DA)
4101"^DD",8925.1,8925.12,.04,1,1,"%D",0)
4102^^3^3^2930122^
4103"^DD",8925.1,8925.12,.04,1,1,"%D",1,0)
4104This REGULAR FileMan cross-reference is used by the router/filer to determine
4105"^DD",8925.1,8925.12,.04,1,1,"%D",2,0)
4106which fields of the header should be set into special variables which may be
4107"^DD",8925.1,8925.12,.04,1,1,"%D",3,0)
4108required by the lookup routine.
4109"^DD",8925.1,8925.12,.04,1,1,"DT")
41102930122
4111"^DD",8925.1,8925.12,.04,3)
4112Enter the required local variable into which this item will be set.
4113"^DD",8925.1,8925.12,.04,21,0)
4114^^11^11^2970108^
4115"^DD",8925.1,8925.12,.04,21,1,0)
4116This field specifies the local variable name into which this item of the
4117"^DD",8925.1,8925.12,.04,21,2,0)
4118upload header will be set. The local variable is used by the Look-Up
4119"^DD",8925.1,8925.12,.04,21,3,0)
4120Method. For example, if this item of the header is the patient social
4121"^DD",8925.1,8925.12,.04,21,4,0)
4122security number, the Lookup Local Variable Name might be TIUSSN. The
4123"^DD",8925.1,8925.12,.04,21,5,0)
4124social security number as written by the transcriptionist is first
4125"^DD",8925.1,8925.12,.04,21,6,0)
4126transformed by any existing Transform Code, and then set into this
4127"^DD",8925.1,8925.12,.04,21,7,0)
4128variable (e.g. TIUSSN) for use in Look-Up Method code.
4129"^DD",8925.1,8925.12,.04,21,8,0)
4130
4131"^DD",8925.1,8925.12,.04,21,9,0)
4132Lookup Local Variable Name is necessary only if the information in this
4133"^DD",8925.1,8925.12,.04,21,10,0)
4134piece is required in order to look up the appropriate entry in the target
4135"^DD",8925.1,8925.12,.04,21,11,0)
4136file.
4137"^DD",8925.1,8925.12,.04,"DT")
41382930122
4139"^DD",8925.1,8925.12,.05,0)
4140EXAMPLE ENTRY^F^^0;5^K:$L(X)>80!($L(X)<2) X
4141"^DD",8925.1,8925.12,.05,3)
4142Answer must be 2-80 characters in length.
4143"^DD",8925.1,8925.12,.05,21,0)
4144^^9^9^2970108^
4145"^DD",8925.1,8925.12,.05,21,1,0)
4146This field is used to store sample data for this item in the form the
4147"^DD",8925.1,8925.12,.05,21,2,0)
4148transcriptionist is expected to use when transcribing it. For example, if
4149"^DD",8925.1,8925.12,.05,21,3,0)
4150a patient has social security number 555-12-1212, and the transcriptionist
4151"^DD",8925.1,8925.12,.05,21,4,0)
4152is expected to write 555-12-1212, than an Example Entry should have the
4153"^DD",8925.1,8925.12,.05,21,5,0)
4154form 555-12-1212.
4155"^DD",8925.1,8925.12,.05,21,6,0)
4156
4157"^DD",8925.1,8925.12,.05,21,7,0)
4158The Upload needs to know the exact form the transcriptionist is expected
4159"^DD",8925.1,8925.12,.05,21,8,0)
4160to use in case it needs to transform it to make it acceptable to FileMan.
4161"^DD",8925.1,8925.12,.05,21,9,0)
4162In this case, the transcriptionist also needs to know the exact form.
4163"^DD",8925.1,8925.12,.05,"DT")
41642930224
4165"^DD",8925.1,8925.12,.06,0)
4166CLINICIAN MUST DICTATE^S^1:YES;0:NO;^0;6^Q
4167"^DD",8925.1,8925.12,.06,3)
4168Answer yes if this field needs to be dictated by the clinician.
4169"^DD",8925.1,8925.12,.06,21,0)
4170^^5^5^2970108^
4171"^DD",8925.1,8925.12,.06,21,1,0)
4172States whether or not this item should be dictated by the Clinician. Will
4173"^DD",8925.1,8925.12,.06,21,2,0)
4174be used by the Clinician Help routine to determine if this field should be
4175"^DD",8925.1,8925.12,.06,21,3,0)
4176shown as data that should be dictated. (Some items can be entered by the
4177"^DD",8925.1,8925.12,.06,21,4,0)
4178transcriber without being dictated, such as the transcriber
4179"^DD",8925.1,8925.12,.06,21,5,0)
4180identification).
4181"^DD",8925.1,8925.12,.06,"DT")
41822930423
4183"^DD",8925.1,8925.12,.07,0)
4184REQUIRED FIELD?^S^1:YES;0:NO;^0;7^Q
4185"^DD",8925.1,8925.12,.07,3)
4186Please indicate whether field is required by application.
4187"^DD",8925.1,8925.12,.07,21,0)
4188^^5^5^2970108^
4189"^DD",8925.1,8925.12,.07,21,1,0)
4190This field is used to determine whether a given header item is required
4191"^DD",8925.1,8925.12,.07,21,2,0)
4192by the application (e.g., Author and Attending Physician may be required
4193"^DD",8925.1,8925.12,.07,21,3,0)
4194for the ongoing processing of a Discharge Summary). Records lacking
4195"^DD",8925.1,8925.12,.07,21,4,0)
4196required fields WILL be entered into the target file, if possible, but
4197"^DD",8925.1,8925.12,.07,21,5,0)
4198will generate Missing Field Error Alerts.
4199"^DD",8925.1,8925.12,.07,"DT")
42002951004
4201"^DD",8925.1,8925.12,1,0)
4202TRANSFORM CODE^K^^1;E1,245^K:$L(X)>245 X D:$D(X) ^DIM
4203"^DD",8925.1,8925.12,1,3)
4204This is Standard MUMPS code.
4205"^DD",8925.1,8925.12,1,9)
4206@
4207"^DD",8925.1,8925.12,1,21,0)
4208^^11^11^2970108^
4209"^DD",8925.1,8925.12,1,21,1,0)
4210This standard MUMPS code transforms the transcribed value of the header
4211"^DD",8925.1,8925.12,1,21,2,0)
4212item into a format acceptable to FileMan (e.g., patient social security
4213"^DD",8925.1,8925.12,1,21,3,0)
4214number 555-12-1212 must be transformed to 555121212 or to whatever
4215"^DD",8925.1,8925.12,1,21,4,0)
4216(external) format FileMan accepts when a user edits the social security
4217"^DD",8925.1,8925.12,1,21,5,0)
4218number field in the target file).
4219"^DD",8925.1,8925.12,1,21,6,0)
4220
4221"^DD",8925.1,8925.12,1,21,7,0)
4222Field values are transformed before being set into Special Lookup
4223"^DD",8925.1,8925.12,1,21,8,0)
4224Variables and before being set into target file fields.
4225"^DD",8925.1,8925.12,1,21,9,0)
4226
4227"^DD",8925.1,8925.12,1,21,10,0)
4228Field is necessary only if transcribed item is not in the format Fileman
4229"^DD",8925.1,8925.12,1,21,11,0)
4230accepts for the target file.
4231"^DD",8925.1,8925.12,1,"DT")
42322930219
4233"^DD",8925.1,8925.13,0)
4234BOILERPLATE TEXT SUB-FIELD^^.01^1
4235"^DD",8925.1,8925.13,0,"NM","BOILERPLATE TEXT")
4236
4237"^DD",8925.1,8925.13,0,"UP")
42388925.1
4239"^DD",8925.1,8925.13,.01,0)
4240BOILERPLATE TEXT^WL^^0;1^Q
4241"^DD",8925.1,8925.13,.01,3)
4242Enter default Report Format
4243"^DD",8925.1,8925.13,.01,21,0)
4244^^51^51^2970506^
4245"^DD",8925.1,8925.13,.01,21,1,0)
4246Applies to Titles and Components.
4247"^DD",8925.1,8925.13,.01,21,2,0)
4248
4249"^DD",8925.1,8925.13,.01,21,3,0)
4250Site can preload the text field of a document with default text/default
4251"^DD",8925.1,8925.13,.01,21,4,0)
4252format/overprint data which is presented to the user when entering the
4253"^DD",8925.1,8925.13,.01,21,5,0)
4254document. User can then edit and/or add to the boilerplate text.
4255"^DD",8925.1,8925.13,.01,21,6,0)
4256
4257"^DD",8925.1,8925.13,.01,21,7,0)
4258If document is formatted into columns, users entering documents should use
4259"^DD",8925.1,8925.13,.01,21,8,0)
4260replace mode rather than insert mode (or Find/RePlace Text) to preserve
4261"^DD",8925.1,8925.13,.01,21,9,0)
4262the columns.
4263"^DD",8925.1,8925.13,.01,21,10,0)
4264
4265"^DD",8925.1,8925.13,.01,21,11,0)
4266Boilerplate Text may be used as an alternative to components to split a
4267"^DD",8925.1,8925.13,.01,21,12,0)
4268document up into sections, but such sections are stored together and
4269"^DD",8925.1,8925.13,.01,21,13,0)
4270cannot be separately accessed the way components can. See Type Component,
4271"^DD",8925.1,8925.13,.01,21,14,0)
4272under Basic field Type.
4273"^DD",8925.1,8925.13,.01,21,15,0)
4274
4275"^DD",8925.1,8925.13,.01,21,16,0)
4276Titles/Components must be inactive in order to edit boilerplate text.
4277"^DD",8925.1,8925.13,.01,21,17,0)
4278
4279"^DD",8925.1,8925.13,.01,21,18,0)
4280Boilerplate Text is the place to embed objects which go fetch data. For
4281"^DD",8925.1,8925.13,.01,21,19,0)
4282example, suppose a Title has boilerplate text:
4283"^DD",8925.1,8925.13,.01,21,20,0)
4284
4285"^DD",8925.1,8925.13,.01,21,21,0)
4286 Patient is a healthy |PATIENT AGE| year old male...
4287"^DD",8925.1,8925.13,.01,21,22,0)
4288
4289"^DD",8925.1,8925.13,.01,21,23,0)
4290Then a user who enters such a note for a patient known by the system to be
4291"^DD",8925.1,8925.13,.01,21,24,0)
429256 years old would be presented with the text:
4293"^DD",8925.1,8925.13,.01,21,25,0)
4294
4295"^DD",8925.1,8925.13,.01,21,26,0)
4296 Patient is a healthy 56 year old male...
4297"^DD",8925.1,8925.13,.01,21,27,0)
4298
4299"^DD",8925.1,8925.13,.01,21,28,0)
4300The user can then add to the text and/or edit the text, including the age
4301"^DD",8925.1,8925.13,.01,21,29,0)
4302(56) of the patient. From this point on, the patient age (56) is regular
4303"^DD",8925.1,8925.13,.01,21,30,0)
4304text and is not updated in this note.
4305"^DD",8925.1,8925.13,.01,21,31,0)
4306
4307"^DD",8925.1,8925.13,.01,21,32,0)
4308If a user enters a document when an embedded object is Inactive, the
4309"^DD",8925.1,8925.13,.01,21,33,0)
4310object does not function; the user sees the object name and an error
4311"^DD",8925.1,8925.13,.01,21,34,0)
4312message. Similarly, if an object has been misspelled in the boilerplate
4313"^DD",8925.1,8925.13,.01,21,35,0)
4314text, or deleted from the file, or if the object name in the boilerplate
4315"^DD",8925.1,8925.13,.01,21,36,0)
4316text is not unique among objects, the object does not function.
4317"^DD",8925.1,8925.13,.01,21,37,0)
4318
4319"^DD",8925.1,8925.13,.01,21,38,0)
4320When embedding objects in boilerplate text, users should make sure the
4321"^DD",8925.1,8925.13,.01,21,39,0)
4322entire object name is on one line rather than split between two lines.
4323"^DD",8925.1,8925.13,.01,21,40,0)
4324Split names generate "NOT found" error messages. Users must also allow
4325"^DD",8925.1,8925.13,.01,21,41,0)
4326enough white space in the boilerplate text for whatever data the object
4327"^DD",8925.1,8925.13,.01,21,42,0)
4328imports. Users can check boilerplate text using action TRY.
4329"^DD",8925.1,8925.13,.01,21,43,0)
4330
4331"^DD",8925.1,8925.13,.01,21,44,0)
4332Any user who can edit boilerplate text can embed any object in it.
4333"^DD",8925.1,8925.13,.01,21,45,0)
4334However, except for object owners who are testing an object, USERS SHOULD
4335"^DD",8925.1,8925.13,.01,21,46,0)
4336EMBED ONLY ACTIVE OBJECTS in boilerplate text. An object can be embedded
4337"^DD",8925.1,8925.13,.01,21,47,0)
4338in as many different Document Definitions as desired.
4339"^DD",8925.1,8925.13,.01,21,48,0)
4340
4341"^DD",8925.1,8925.13,.01,21,49,0)
4342A document with multiple components can have boilerplate text in the entry
4343"^DD",8925.1,8925.13,.01,21,50,0)
4344itself and/or in any component. Boilerplate text in the entry itself
4345"^DD",8925.1,8925.13,.01,21,51,0)
4346appears first.
4347"^DD",8925.1,8925.13,.01,"DT")
43482930305
4349"^DD",8925.1,8925.14,0)
4350ITEM SUB-FIELD^^4^4
4351"^DD",8925.1,8925.14,0,"DT")
43522970212
4353"^DD",8925.1,8925.14,0,"IX","AC",8925.14,3)
4354
4355"^DD",8925.1,8925.14,0,"IX","B",8925.14,.01)
4356
4357"^DD",8925.1,8925.14,0,"IX","C",8925.14,4)
4358
4359"^DD",8925.1,8925.14,0,"NM","ITEM")
4360
4361"^DD",8925.1,8925.14,0,"UP")
43628925.1
4363"^DD",8925.1,8925.14,.01,0)
4364ITEM^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
4365"^DD",8925.1,8925.14,.01,1,0)
4366^.1
4367"^DD",8925.1,8925.14,.01,1,1,0)
43688925.14^B
4369"^DD",8925.1,8925.14,.01,1,1,1)
4370S ^TIU(8925.1,DA(1),10,"B",$E(X,1,30),DA)=""
4371"^DD",8925.1,8925.14,.01,1,1,2)
4372K ^TIU(8925.1,DA(1),10,"B",$E(X,1,30),DA)
4373"^DD",8925.1,8925.14,.01,1,2,0)
43748925.1^AD
4375"^DD",8925.1,8925.14,.01,1,2,1)
4376S ^TIU(8925.1,"AD",$E(X,1,30),DA(1),DA)=""
4377"^DD",8925.1,8925.14,.01,1,2,2)
4378K ^TIU(8925.1,"AD",$E(X,1,30),DA(1),DA)
4379"^DD",8925.1,8925.14,.01,1,2,"%D",0)
4380^^2^2^2940719^
4381"^DD",8925.1,8925.14,.01,1,2,"%D",1,0)
4382This cross-reference facilitates traversal from child to parent, up the
4383"^DD",8925.1,8925.14,.01,1,2,"%D",2,0)
4384class hierarchy.
4385"^DD",8925.1,8925.14,.01,1,2,"DT")
43862940719
4387"^DD",8925.1,8925.14,.01,1,3,0)
43888925.1^AMM^MUMPS
4389"^DD",8925.1,8925.14,.01,1,3,1)
4390D REDOX^TIUDD
4391"^DD",8925.1,8925.14,.01,1,3,2)
4392D REDOX^TIUDD
4393"^DD",8925.1,8925.14,.01,1,3,"%D",0)
4394^^2^2^2940720^^
4395"^DD",8925.1,8925.14,.01,1,3,"%D",1,0)
4396This MUMPS-type cross-reference will update the timestamp on the parent
4397"^DD",8925.1,8925.14,.01,1,3,"%D",2,0)
4398document when the ITEM, MNEMONIC, or SEQUENCE changes.
4399"^DD",8925.1,8925.14,.01,1,3,"DT")
44002940720
4401"^DD",8925.1,8925.14,.01,1,4,0)
44028925.1^ACL1001^MUMPS
4403"^DD",8925.1,8925.14,.01,1,4,1)
4404D SACL^TIUDD1(X,10.01)
4405"^DD",8925.1,8925.14,.01,1,4,2)
4406D KACL^TIUDD1(X,10.01)
4407"^DD",8925.1,8925.14,.01,1,4,"%D",0)
4408^^2^2^2971016^
4409"^DD",8925.1,8925.14,.01,1,4,"%D",1,0)
4410This MUMPS-type cross-reference by class and name will help to identify
4411"^DD",8925.1,8925.14,.01,1,4,"%D",2,0)
4412the titles within a given class.
4413"^DD",8925.1,8925.14,.01,1,4,"DT")
44142971016
4415"^DD",8925.1,8925.14,.01,3)
4416ITEM must be a new or pre-existing Document Definition with appropriate Type which you own, which is not already an Item elsewhere.
4417"^DD",8925.1,8925.14,.01,4)
4418D NAME^TIUFXHLX
4419"^DD",8925.1,8925.14,.01,12)
4420See Technical Description.
4421"^DD",8925.1,8925.14,.01,12.1)
4422S DIC("S")="I $G(TIUFPRIV) X:$D(TIUFISCR) ""I Y=TIUFISCR"""
4423"^DD",8925.1,8925.14,.01,21,0)
4424^.001^6^6^3050125^^^^
4425"^DD",8925.1,8925.14,.01,21,1,0)
4426Items are themselves Document Definitions. The Type of the parent entry
4427"^DD",8925.1,8925.14,.01,21,2,0)
4428determines what Types of items it has. A parent entry of type Class has
4429"^DD",8925.1,8925.14,.01,21,3,0)
4430items of type Class or Document Class. A Document Class entry has items
4431"^DD",8925.1,8925.14,.01,21,4,0)
4432of type Title. If a Title entry has more than a single section, it has
4433"^DD",8925.1,8925.14,.01,21,5,0)
4434items of type Component. Components may also be multi-section with items
4435"^DD",8925.1,8925.14,.01,21,6,0)
4436of type Component. Objects do not have items.
4437"^DD",8925.1,8925.14,.01,23,0)
4438^.001^8^8^3050125^^^^
4439"^DD",8925.1,8925.14,.01,23,1,0)
4440The Item subfield of Item Field 10 in File 8925.1 is screened when using
4441"^DD",8925.1,8925.14,.01,23,2,0)
4442the TIUF Document Definition Utility to add items (i.e. when variable
4443"^DD",8925.1,8925.14,.01,23,3,0)
4444TIUFISCR is defined.
4445"^DD",8925.1,8925.14,.01,23,4,0)
4446
4447"^DD",8925.1,8925.14,.01,23,5,0)
4448This screen is needed in ADDTEN^TIUFLF4, which noninteractively adds an
4449"^DD",8925.1,8925.14,.01,23,6,0)
4450item to the Item multiple. The screen limits the lookup to the 8925.1 IFN
4451"^DD",8925.1,8925.14,.01,23,7,0)
4452of the item being added to the Item multiple. Without the screen, the
4453"^DD",8925.1,8925.14,.01,23,8,0)
4454lookup fails when there are multiple 8925.1 entries of the same name.
4455"^DD",8925.1,8925.14,.01,"DEL",.01,0)
4456I 1
4457"^DD",8925.1,8925.14,.01,"DT")
44582971016
4459"^DD",8925.1,8925.14,2,0)
4460MNEMONIC^F^^0;2^K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>4!($L(X)<1) X
4461"^DD",8925.1,8925.14,2,1,0)
4462^.1
4463"^DD",8925.1,8925.14,2,1,1,0)
44648925.1^AMM2^MUMPS
4465"^DD",8925.1,8925.14,2,1,1,1)
4466D REDOX^TIUDD
4467"^DD",8925.1,8925.14,2,1,1,2)
4468D REDOX^TIUDD
4469"^DD",8925.1,8925.14,2,1,1,"%D",0)
4470^^2^2^2961210^^^^
4471"^DD",8925.1,8925.14,2,1,1,"%D",1,0)
4472This MUMPS-type cross-reference will update the TIMESTAMP on the parent
4473"^DD",8925.1,8925.14,2,1,1,"%D",2,0)
4474document when either the ITEM, MNEMONIC, or SEQUENCE changes.
4475"^DD",8925.1,8925.14,2,1,1,"DT")
44762940720
4477"^DD",8925.1,8925.14,2,3)
4478Mnemonic 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.
4479"^DD",8925.1,8925.14,2,21,0)
4480^^3^3^2970127^
4481"^DD",8925.1,8925.14,2,21,1,0)
4482Item Mnemonic is a handle by which to select Classes/Document Classes from
4483"^DD",8925.1,8925.14,2,21,2,0)
4484a menu. 1-4 characters long. Mnemonic is usually numeric with the same
4485"^DD",8925.1,8925.14,2,21,3,0)
4486value as the Sequence. Alpha mnemonics are permitted if preferred.
4487"^DD",8925.1,8925.14,2,"DT")
44882940720
4489"^DD",8925.1,8925.14,3,0)
4490SEQUENCE^NJ6,2^^0;3^K:+X'=X!(X>999)!(X<.01)!(X?.E1"."3N.N) X
4491"^DD",8925.1,8925.14,3,1,0)
4492^.1
4493"^DD",8925.1,8925.14,3,1,1,0)
44948925.1^AMM3^MUMPS
4495"^DD",8925.1,8925.14,3,1,1,1)
4496D REDOX^TIUDD
4497"^DD",8925.1,8925.14,3,1,1,2)
4498D REDOX^TIUDD
4499"^DD",8925.1,8925.14,3,1,1,"%D",0)
4500^^2^2^2940720^^
4501"^DD",8925.1,8925.14,3,1,1,"%D",1,0)
4502This MUMPS-type cross-reference will update the TIMESTAMP of the parent
4503"^DD",8925.1,8925.14,3,1,1,"%D",2,0)
4504document when the ITEM, MNEMONIC, or SEQUENCE change.
4505"^DD",8925.1,8925.14,3,1,1,"DT")
45062940720
4507"^DD",8925.1,8925.14,3,1,2,0)
45088925.14^AC
4509"^DD",8925.1,8925.14,3,1,2,1)
4510S ^TIU(8925.1,DA(1),10,"AC",$E(X,1,30),DA)=""
4511"^DD",8925.1,8925.14,3,1,2,2)
4512K ^TIU(8925.1,DA(1),10,"AC",$E(X,1,30),DA)
4513"^DD",8925.1,8925.14,3,1,2,3)
4514Please don't delete!
4515"^DD",8925.1,8925.14,3,1,2,"%D",0)
4516^^2^2^2950412^^^
4517"^DD",8925.1,8925.14,3,1,2,"%D",1,0)
4518This REGULAR Fileman cross reference is used to list items by sequence
4519"^DD",8925.1,8925.14,3,1,2,"%D",2,0)
4520number.
4521"^DD",8925.1,8925.14,3,1,2,"DT")
45222950410
4523"^DD",8925.1,8925.14,3,3)
4524Item Sequence determines display order under the parent. For alphabetic order, do not enter sequences. Sequence is between .01 and 999, 2 Decimal Digits.
4525"^DD",8925.1,8925.14,3,21,0)
4526^^3^3^2970102^^^
4527"^DD",8925.1,8925.14,3,21,1,0)
4528Item Sequence, if entered, determines item's order under its parent. If
4529"^DD",8925.1,8925.14,3,21,2,0)
4530items have no sequence, item order is alphabetic by item Menu Text.
4531"^DD",8925.1,8925.14,3,21,3,0)
4532Sequence must be between .01 and 999.
4533"^DD",8925.1,8925.14,3,"DT")
45342961021
4535"^DD",8925.1,8925.14,4,0)
4536MENU 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
4537"^DD",8925.1,8925.14,4,1,0)
4538^.1
4539"^DD",8925.1,8925.14,4,1,1,0)
45408925.1^AMM4^MUMPS
4541"^DD",8925.1,8925.14,4,1,1,1)
4542D REDOX^TIUDD
4543"^DD",8925.1,8925.14,4,1,1,2)
4544D REDOX^TIUDD
4545"^DD",8925.1,8925.14,4,1,1,"%D",0)
4546^^2^2^2940720^
4547"^DD",8925.1,8925.14,4,1,1,"%D",1,0)
4548This MUMPS-type cross-reference updates the TIMESTAMP on the parent
4549"^DD",8925.1,8925.14,4,1,1,"%D",2,0)
4550document when the DISPLAY NAME changes.
4551"^DD",8925.1,8925.14,4,1,1,"DT")
45522940720
4553"^DD",8925.1,8925.14,4,1,2,0)
45548925.14^C^MUMPS
4555"^DD",8925.1,8925.14,4,1,2,1)
4556S ^TIU(8925.1,DA(1),10,"C",$E(X,1,30),DA)=""
4557"^DD",8925.1,8925.14,4,1,2,2)
4558K ^TIU(8925.1,DA(1),10,"C",$E(X,1,30),DA)
4559"^DD",8925.1,8925.14,4,1,2,"%D",0)
4560^^3^3^2961210^^
4561"^DD",8925.1,8925.14,4,1,2,"%D",1,0)
4562This M cross reference could have been regular. It is used to display
4563"^DD",8925.1,8925.14,4,1,2,"%D",2,0)
4564items with no sequence in alpha order by Menu Text.
4565"^DD",8925.1,8925.14,4,1,2,"DT")
45662961210
4567"^DD",8925.1,8925.14,4,3)
4568This 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.
4569"^DD",8925.1,8925.14,4,4)
4570
4571"^DD",8925.1,8925.14,4,21,0)
4572^^20^20^2990114^^
4573"^DD",8925.1,8925.14,4,21,1,0)
4574Item Menu Text is the short name users will see for Classes and Document
4575"^DD",8925.1,8925.14,4,21,2,0)
4576Classes when selecting them from 3-COLUMN MENUS. Document Definitions are
4577"^DD",8925.1,8925.14,4,21,3,0)
4578selected from 3-column menus when viewing documents across many patients
4579"^DD",8925.1,8925.14,4,21,4,0)
4580and when viewing many kinds of documents at the same time (e.g. Progress
4581"^DD",8925.1,8925.14,4,21,5,0)
4582Notes and Discharge Summaries).
4583"^DD",8925.1,8925.14,4,21,6,0)
4584
4585"^DD",8925.1,8925.14,4,21,7,0)
4586To edit the Menu Text of a Document Definition, you must be viewing the
4587"^DD",8925.1,8925.14,4,21,8,0)
4588Document Definition as an ITEM of its PARENT. Select 'Detailed Display'
4589"^DD",8925.1,8925.14,4,21,9,0)
4590for the PARENT and then 'Items'.
4591"^DD",8925.1,8925.14,4,21,10,0)
4592
4593"^DD",8925.1,8925.14,4,21,11,0)
4594Menu Text has 1 - 20 characters. Menu Text must not begin with a space or
4595"^DD",8925.1,8925.14,4,21,12,0)
4596with 'All'. The Document Definition Utility TIUF automatically sets the
4597"^DD",8925.1,8925.14,4,21,13,0)
4598Item Menu Text to the first 20 characters of the Item's Name when an entry
4599"^DD",8925.1,8925.14,4,21,14,0)
4600is first added as an item. (If an entry's Name begins with 'All' its Menu
4601"^DD",8925.1,8925.14,4,21,15,0)
4602Text is given 'AlX' as its first 3 characters.) The utility does NOT
4603"^DD",8925.1,8925.14,4,21,16,0)
4604update Menu Text if the entry Name is later changed, since this would
4605"^DD",8925.1,8925.14,4,21,17,0)
4606overwrite what a site may have carefully set up. Menu Text is required.
4607"^DD",8925.1,8925.14,4,21,18,0)
4608
4609"^DD",8925.1,8925.14,4,21,19,0)
4610Menu Text can affect item order under a parent since order is alphabetic
4611"^DD",8925.1,8925.14,4,21,20,0)
4612by menu text if items do not have sequence numbers.
4613"^DD",8925.1,8925.14,4,23,0)
4614^^10^10^2990114^^^^
4615"^DD",8925.1,8925.14,4,23,1,0)
4616Menu Text cannot begin with 'All' because XQOR, the Unwinder Utility,
4617"^DD",8925.1,8925.14,4,23,2,0)
4618misinterprets it. The result (for titles) is that when a user selects a
4619"^DD",8925.1,8925.14,4,23,3,0)
4620Document Class of titles to view from a three column menu, and one of the
4621"^DD",8925.1,8925.14,4,23,4,0)
4622titles has menu text starting with 'All,' then no documents are found for
4623"^DD",8925.1,8925.14,4,23,5,0)
4624titles AFTER the title starting with 'All', even though such documents may
4625"^DD",8925.1,8925.14,4,23,6,0)
4626exist. Similar problems occur with types other than titles.
4627"^DD",8925.1,8925.14,4,23,7,0)
4628
4629"^DD",8925.1,8925.14,4,23,8,0)
4630Menu Text cannot begin with a space because such Menu Text cannot be used
4631"^DD",8925.1,8925.14,4,23,9,0)
4632to select the entry from a menu: if the space is left off, it is
4633"^DD",8925.1,8925.14,4,23,10,0)
4634questioned, and if the space is left in, it is still questioned.
4635"^DD",8925.1,8925.14,4,"DT")
46362990121
4637"^DIC",8925.1,8925.1,0)
4638TIU DOCUMENT DEFINITION^8925.1
4639"^DIC",8925.1,8925.1,0,"GL")
4640^TIU(8925.1,
4641"^DIC",8925.1,8925.1,"%",0)
4642^1.005^2^1
4643"^DIC",8925.1,8925.1,"%",2,0)
4644GMTS
4645"^DIC",8925.1,8925.1,"%","B","GMTS",2)
4646
4647"^DIC",8925.1,8925.1,"%D",0)
4648^^76^76^2970604^^^
4649"^DIC",8925.1,8925.1,"%D",1,0)
4650This file stores Document Definitions, which identify and define behavior
4651"^DIC",8925.1,8925.1,"%D",2,0)
4652for documents stored in the TIU DOCUMENTS FILE (#8925). For consistency
4653"^DIC",8925.1,8925.1,"%D",3,0)
4654with the V-file schema, it may be viewed as the "Attribute Dictionary" for
4655"^DIC",8925.1,8925.1,"%D",4,0)
4656the Text Integration Utilities.
4657"^DIC",8925.1,8925.1,"%D",5,0)
4658
4659"^DIC",8925.1,8925.1,"%D",6,0)
4660It also stores Objects, which can be embedded in a Document Definition's
4661"^DIC",8925.1,8925.1,"%D",7,0)
4662Boilerplate Text (Overprint). Objects contain M code which gets a piece of
4663"^DIC",8925.1,8925.1,"%D",8,0)
4664data and inserts it in the document's Boilerplate Text when a document is
4665"^DIC",8925.1,8925.1,"%D",9,0)
4666entered.
4667"^DIC",8925.1,8925.1,"%D",10,0)
4668
4669"^DIC",8925.1,8925.1,"%D",11,0)
4670Warning: objects embedded in boilerplate text are looked up by multiple
4671"^DIC",8925.1,8925.1,"%D",12,0)
4672index (i.e. DIC(0) contains 'M'). Current code (see routine CHECK^TIUFLF3)
4673"^DIC",8925.1,8925.1,"%D",13,0)
4674checks all present indexes to make sure object names, abbreviations and
4675"^DIC",8925.1,8925.1,"%D",14,0)
4676print names are not ambiguous for this lookup. If new indexes are added,
4677"^DIC",8925.1,8925.1,"%D",15,0)
4678this code MUST BE UPDATED to check the new index as well.
4679"^DIC",8925.1,8925.1,"%D",16,0)
4680
4681"^DIC",8925.1,8925.1,"%D",17,0)
4682Some entries in this file are developed Nationally and exported across the
4683"^DIC",8925.1,8925.1,"%D",18,0)
4684country. Others are created by local sites. Entries in the first
4685"^DIC",8925.1,8925.1,"%D",19,0)
4686category are marked National Standard and are not editable by sites.
4687"^DIC",8925.1,8925.1,"%D",20,0)
4688
4689"^DIC",8925.1,8925.1,"%D",21,0)
4690This file does NOT allow multiple entries OF THE SAME TYPE with the same
4691"^DIC",8925.1,8925.1,"%D",22,0)
4692name. That is, within a given Type, there are no duplicate names. (This
4693"^DIC",8925.1,8925.1,"%D",23,0)
4694refers to the .01 field, the Technical name of the entry.)
4695"^DIC",8925.1,8925.1,"%D",24,0)
4696
4697"^DIC",8925.1,8925.1,"%D",25,0)
4698This file does not allow a parent to have items with the same name, even
4699"^DIC",8925.1,8925.1,"%D",26,0)
4700if the items have different internal file numbers (i.e. are different file
4701"^DIC",8925.1,8925.1,"%D",27,0)
4702entries). Again, this refers to the .01 Technical name of the entry.
4703"^DIC",8925.1,8925.1,"%D",28,0)
4704
4705"^DIC",8925.1,8925.1,"%D",29,0)
4706Because of ownership considerations, the file does NOT allow an entry to
4707"^DIC",8925.1,8925.1,"%D",30,0)
4708be an item under more than 1 parent. If the same item is desired under
4709"^DIC",8925.1,8925.1,"%D",31,0)
4710more than 1 parent, the item must be copied into a new entry. There is
4711"^DIC",8925.1,8925.1,"%D",32,0)
4712one exception: Document Definitions of Type Component which have been
4713"^DIC",8925.1,8925.1,"%D",33,0)
4714marked Shared may have more than one parent.
4715"^DIC",8925.1,8925.1,"%D",34,0)
4716
4717"^DIC",8925.1,8925.1,"%D",35,0)
4718The Document Definition Utility TIUF categorizes certain fields as Basic,
4719"^DIC",8925.1,8925.1,"%D",36,0)
4720Technical, or Upload, and displays these fields together as a group when
4721"^DIC",8925.1,8925.1,"%D",37,0)
4722user edits or views a Document Definition. BASIC fields include Name,
4723"^DIC",8925.1,8925.1,"%D",38,0)
4724Abbreviation, Print Name, Type, Personal Owner, Class Owner, Status, In
4725"^DIC",8925.1,8925.1,"%D",39,0)
4726Use, Shared, Orphan, Has Boiltxt, National Standard, OK to Distribute, and
4727"^DIC",8925.1,8925.1,"%D",40,0)
4728Suppress Visit Selection. TECHNICAL fields include Entry Action, Exit
4729"^DIC",8925.1,8925.1,"%D",41,0)
4730Action, Edit Template, Print Method, Print Form Header, Print Form Number,
4731"^DIC",8925.1,8925.1,"%D",42,0)
4732Print Group, Allow Custom Form Headers, Visit Linkage Method, Validation
4733"^DIC",8925.1,8925.1,"%D",43,0)
4734Method, and Object Method. UPLOAD fields include Upload Target File, Laygo
4735"^DIC",8925.1,8925.1,"%D",44,0)
4736Allowed, Target Text Field Subscript, Upload Look-up Method, Upload
4737"^DIC",8925.1,8925.1,"%D",45,0)
4738Post-Filing Code, Upload Filing Error Code, and multiples Upload Captioned
4739"^DIC",8925.1,8925.1,"%D",46,0)
4740ASCII Header and Upload Delimited ASCII Header.
4741"^DIC",8925.1,8925.1,"%D",47,0)
4742
4743"^DIC",8925.1,8925.1,"%D",48,0)
4744The Document Definition file contains extensive, detailed field
4745"^DIC",8925.1,8925.1,"%D",49,0)
4746descriptions. Likewise, some protocols (File 101) used in TIU have
4747"^DIC",8925.1,8925.1,"%D",50,0)
4748extensive and careful descriptions in the Protocol file. Many of these
4749"^DIC",8925.1,8925.1,"%D",51,0)
4750descriptions are used in TIU for online help. If it becomes necessary for
4751"^DIC",8925.1,8925.1,"%D",52,0)
4752a national programmer to edit these descriptions, the programmer should
4753"^DIC",8925.1,8925.1,"%D",53,0)
4754check to make sure all online help is still displayed properly.
4755"^DIC",8925.1,8925.1,"%D",54,0)
4756
4757"^DIC",8925.1,8925.1,"%D",55,0)
4758Users are expected to use the Document Definition Utility TIUF to enter,
4759"^DIC",8925.1,8925.1,"%D",56,0)
4760edit, and delete file entries. In fact, the file prohibits the deletion
4761"^DIC",8925.1,8925.1,"%D",57,0)
4762of entries through generic Fileman Options. It also prohibits the edit
4763"^DIC",8925.1,8925.1,"%D",58,0)
4764through generic Fileman of a few critical fields: Type, Status, Shared,
4765"^DIC",8925.1,8925.1,"%D",59,0)
4766and National Standard. Adding and Deleting (but not editing) Items is
4767"^DIC",8925.1,8925.1,"%D",60,0)
4768also prohibited through generic Fileman options. Abbreviation and Print
4769"^DIC",8925.1,8925.1,"%D",61,0)
4770Name of OBJECTS cannot be edited through generic Fileman Options.
4771"^DIC",8925.1,8925.1,"%D",62,0)
4772
4773"^DIC",8925.1,8925.1,"%D",63,0)
4774This does NOT imply that it is SAFE to use generic Fileman to edit other
4775"^DIC",8925.1,8925.1,"%D",64,0)
4776fields. Users are cautioned that edit through generic Fileman bypasses
4777"^DIC",8925.1,8925.1,"%D",65,0)
4778many safeguards built in to the Document Definition Utility and can create
4779"^DIC",8925.1,8925.1,"%D",66,0)
4780havoc unless the user THOROUGHLY UNDERSTANDS the File and its uses.
4781"^DIC",8925.1,8925.1,"%D",67,0)
4782
4783"^DIC",8925.1,8925.1,"%D",68,0)
4784If users find needs which are not met through TIUF, please communicate
4785"^DIC",8925.1,8925.1,"%D",69,0)
4786them to the TIU development team.
4787"^DIC",8925.1,8925.1,"%D",70,0)
4788
4789"^DIC",8925.1,8925.1,"%D",71,0)
4790 *****************
4791"^DIC",8925.1,8925.1,"%D",72,0)
4792
4793"^DIC",8925.1,8925.1,"%D",73,0)
4794WARNING: Using generic Fileman options to edit entries can cause SERIOUS
4795"^DIC",8925.1,8925.1,"%D",74,0)
4796database problems.
4797"^DIC",8925.1,8925.1,"%D",75,0)
4798
4799"^DIC",8925.1,8925.1,"%D",76,0)
4800 ****************
4801"^DIC",8925.1,"B","TIU DOCUMENT DEFINITION",8925.1)
4802
4803**END**
4804**END**
Note: See TracBrowser for help on using the repository browser.