Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries  | All
Print Page as PDF
Global: ^TIU(8925.95

Package: Text Integration Utility

Global: ^TIU(8925.95


Information

FileMan FileNo FileMan Filename Package
8925.95 TIU DOCUMENT PARAMETERS Text Integration Utility

Description

Directly Accessed By Routines, Total: 13

Package Total Routines
Text Integration Utility 13 TIU DOCUMENT PARAMETER EDIT    TIU212B    TIUCOP    TIUDPEDT    TIUEPN12    TIUFLP1    TIUHL7U2    TIULC1
TIUP290A    TIUPD    TIUPEVN1    TIUPREF    TIUSRVA    

Accessed By FileMan Db Calls, Total: 2

Package Total Routines
Text Integration Utility 2 TIUDPEDT    TIUP290A    

Pointer To FileMan Files, Total: 8

Package Total FileMan Files
Authorization Subscription 2 USR CLASS(#8930)[#8925.955(.01)]    USR ACTION(#8930.8)[#8925.951(.01)]    
Kernel 2 DEVICE(#3.5)[.13#8925.952(.02)#8925.952(.03)]
NEW PERSON(#200)[#8925.954(.01)]    
Text Integration Utility 2 TIU DOCUMENT DEFINITION(#8925.1)[.01]    TIU STATUS(#8925.6)[.05#8925.951(.04)]    
Incomplete Records Tracking 1 IRT TYPE OF DEFICIENCY(#393.3)[.12]    
Registration 1 MEDICAL CENTER DIVISION(#40.8)[#8925.952(.01)]    

Fields, Total: 35

Field # Name Loc Type Details
.01 DOCUMENT DEFINITION 0;1 POINTER TO TIU DOCUMENT DEFINITION FILE (#8925.1)
************************REQUIRED FIELD************************
TIU DOCUMENT DEFINITION(#8925.1)

  • LAST EDITED:  JUN 30, 1995
  • HELP-PROMPT:  Choose the document definition to which these parameters apply.
  • DESCRIPTION:  This is the Document Definition to which the parameters apply.
    NOTE: All parameters are inherited from ancestor Classes or Document Classes, unless overridden at a subordinate level in the document definition hierarchy. (For example, if you Require Release for class Progress Notes,
    then all progress note titles require release, unless the parameter is set to NO for a subordinate Document Class or Title.)
  • CROSS-REFERENCE:  8925.95^B
    1)= S ^TIU(8925.95,"B",$E(X,1,30),DA)=""
    2)= K ^TIU(8925.95,"B",$E(X,1,30),DA)
  • RECORD INDEXES:  AC (#1572)
.02 REQUIRE RELEASE 0;2 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUN 30, 1995
  • HELP-PROMPT:  Indicate whether or not release is required.
  • DESCRIPTION:  This parameter determines whether the person entering the document is required (and prompted) to release the document from a draft state upon exit from the entry/editing process.
    Though designed for Discharge Summaries, release may be used for any kind of TIU document.
.03 REQUIRE MAS VERIFICATION 0;3 SET
  • '1' FOR YES, ALWAYS;
  • '0' FOR NO;
  • '2' FOR UPLOAD ONLY;
  • '3' FOR DIRECT ENTRY ONLY;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Indicate whether and when verification is required.
  • DESCRIPTION:  This parameter determines whether verification by MAS is required, prior to public access and signature of the document.
    Though designed for Discharge Summaries, verification may be used for any kind of TIU document, and is particularly helpful for documents that are uploaded from a transcription service.
    Allowable values are: 0 NO
    1 YES, ALWAYS
    2 UPLOAD ONLY
    3 DIRECT ENTRY ONLY
    where 1 indicates that these documents require verification regardless of how they originate; 2 indicates that verification is required only when the documents are Uploaded; and 3 indicates that verification is required
    only when documents are entered directly into VISTA.
.04 REQUIRE AUTHOR TO SIGN 0;4 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  NOV 18, 2002
  • HELP-PROMPT:  Indicate whether the author must sign the document.
  • DESCRIPTION:  This field indicates whether or not the author should sign the document before the expected cosigner (attending).
    If parameter is set to NO, only the expected cosigner is alerted for signature. Although the unsigned document appears in the author's unsigned list, and he is ALLOWED to sign it, his signature is not REQUIRED.
    If set to YES, then the author is alerted for signature, and if the expected cosigner should attempt to sign the document first, he is informed that the author has not yet signed.
.05 WHEN MAY CHART COPY BE PRINTED 0;5 POINTER TO TIU STATUS FILE (#8925.6) TIU STATUS(#8925.6)

  • LAST EDITED:  JUN 30, 1995
  • HELP-PROMPT:  Indicate when a chart copy may be printed.
  • DESCRIPTION:  OUT OF SERVICE. Printing for a given status is governed by business rules.
    Indicate the status which a document must attain before it can be printed for the chart.
.06 ROUTINE PRINT EVENT(S) 0;6 SET
  • 'R' FOR release;
  • 'V' FOR verification;
  • 'B' FOR both;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Indicate on which event(s) chart copies should be printed.
  • DESCRIPTION:  A document of the given type, and of ROUTINE urgency, is automatically printed whenever one of these events occurs.
    For example, a site may specify that ROUTINE documents print only upon Completion (i.e., signature or cosignature), while STAT documents print upon Release from Transcription, MAS Verification, or both, in addition to
    printing upon completion.
    If print events are not specified, and a CHART COPY DEVICE is defined for the Medical Center Division, then the document will be auto-printed only upon completion.
    If field MANUAL PRINT AFTER ENTRY is set to YES, then auto-print is ignored entirely.
    If urgency is not specified for some document, then its urgency is considered to be routine, and the document prints when a routine print event occurs.
.07 STAT PRINT EVENT(S) 0;7 SET
  • 'R' FOR release;
  • 'V' FOR verification;
  • 'B' FOR both;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Indicate the event(s) on which STAT documents will be printed.
  • DESCRIPTION:  
    This field is identical to ROUTINE PRINT EVENT(S), except that it applies to documents of STAT urgency rather than ROUTINE urgency.
.08 MANUAL PRINT AFTER ENTRY 0;8 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Specify whether user should be asked to print after entry.
  • DESCRIPTION:  This parameter is used for documents where a manually-printed hard copy is desired following document entry. If the parameter is set to YES, the user is prompted to print a copy on exit from their preferred editor, and
    auto-printing (as described in fields ROUTINE/STAT PRINT EVENT(S)) is ignored.
.09 ALLOW CHART PRINT OUTSIDE MAS 0;9 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Indicate whether non-MAS personnel may print CHART COPIES.
  • DESCRIPTION:  This field determines whether non-MAS users (for example, providers) are asked if they want WORK copies or CHART copies when they print a document. If the field is NOT set to YES, they are not asked, and the printout is a
    WORK copy.
    Generally, this is set to YES for PROGRESS NOTES, which are likely to be printed on the Ward or in the Clinic for immediate inclusion in the chart. For DISCHARGE SUMMARIES, which are typically printed centrally, it is
    usually set to NO, since duplicate CHART COPIES are a particular problem.
.1 ALLOW >1 RECORDS PER VISIT 0;10 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Indicate whether the user may enter more than one of these per visit.
  • DESCRIPTION:  This field determines whether a given document may be created more than once per visit. For example, it is often appropriate to enter multiple PROGRESS NOTES for a single HOSPITALIZATION or CLINIC VISIT, whereas only one
    DISCHARGE SUMMARY is usually entered per HOSPITALIZATION.
.11 ENABLE IRT INTERFACE 0;11 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Please indicate whether IRT Interface should be enabled.
  • DESCRIPTION:  This enables TIU's interface with Incomplete Record Tracking (IRT), which updates IRT's deficiencies when transcription, signature, or cosignature events are registered for a given document.
    NOTE: IRT is designed for DISCHARGE SUMMARIES, and is appropriate only for types of documents where only one document is expected per patient movement. We therefore ask you to leave this parameter undefined (or set it to
    NO) for PROGRESS NOTES.
.12 IRT DEFICIENCY 0;12 POINTER TO IRT TYPE OF DEFICIENCY FILE (#393.3) IRT TYPE OF DEFICIENCY(#393.3)

  • INPUT TRANSFORM:  S DIC("S")="I +$P(^VAS(393.3,+Y,0),U,7)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  DEC 06, 1995
  • HELP-PROMPT:  Please indicate the IRT DEFICIENCY that corresponds to this document
  • DESCRIPTION:  
    This field provides a mapping between the TIU DOCUMENT DEFINITION and the corresponding IRT DEFICIENCY TYPE. For example, TIU Class DISCHARGE SUMMARY maps to IRT Deficiency Type DISCHARGE SUMMARY.
  • SCREEN:  S DIC("S")="I +$P(^VAS(393.3,+Y,0),U,7)"
  • EXPLANATION:  Only TRACKED DEFICIENCIES may be selected.
.13 DEFAULT PRINTER 0;13 POINTER TO DEVICE FILE (#3.5) DEVICE(#3.5)

  • LAST EDITED:  MAR 06, 1996
  • HELP-PROMPT:  Please select the default printer for this document.
  • DESCRIPTION:  NOT IN SERVICE.
    When a user prints a document of the given type and is prompted for DEVICE, this serves as the default.
.14 SUPPRESS DX/CPT ON ENTRY 0;14 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Indicate whether to suppress Dx & CPT questions for the Visit following signature.
  • DESCRIPTION:  This parameter applies only to documents for outpatient care. Together with parameter ASK DX/CPT ON ALL OPT VISITS, it determines whether or not a user is prompted for diagnoses and procedures after signing or editing a
    document.
    If this parameter is set to YES (for suppress), the user is not prompted for this information.
    If this parameter is set to NO or is blank, the user may or may not be prompted, depending on the type of visit and on parameter ASK DX/CPT ON ALL OPT VISITS.
    If a site elects to suppress diagnoses and procedures, the site must capture this information by some other means (such as an AICS encounter form), in order to receive workload credit for these visits.
.15 FORCE RESPONSE TO EXPOSURES 0;15 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 08, 1999
  • HELP-PROMPT:  Indicate whether a response is required on SC Classification.
  • DESCRIPTION:  
    When set to YES, this parameter forces the user to respond when asked to specify a veteran's Service Connection Classification (AO, IR, or EC), when creating a standalone visit.
.16 ASK DX/CPT ON ALL OPT VISITS 0;16 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Indicate whether Dx/CPT should be asked for APPOINTMENTS & STANDALONE Visits alike.
  • DESCRIPTION:  This parameter applies only to documents for outpatient care, and is IGNORED if SUPPRESS DX/CPT ON ENTRY is set to YES.
    If DX/CPT prompts are NOT suppressed, and ASK DX/CPT ON ALL OPT VISITS is set to YES, the user is prompted for DX/CPT information for scheduled as well as unscheduled (stand-alone) visits.
    If DX/CPT prompts are NOT suppressed, and ASK DX/CPT ON ALL OPT VISITS is set to NO, the user is prompted for DX/CPT information for unscheduled visits ONLY.
.17 SEND ALERTS ON ADDENDA 0;17 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  DEC 05, 2002
  • HELP-PROMPT:  Should the AUTHOR (& COSIGNER) be alerted on addenda?
  • DESCRIPTION:  This parameter determines whether AUTHORS and COSIGNERS of a document of this kind (and any of its descendent types) will receive an informational alert when addenda are added by other persons.
    The addendum must be in a COMPLETED or AMENDED status for an alert to be generated.
    Like all document parameters, it may be overridden at descendent levels of the Document Definition Hierarchy. DEFAULT is NO.
.18 ORDER ID ENTRIES BY TITLE 0;18 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  To display/print interdisciplinary child entries alphabetically by title under the parent entry, answer YES. Otherwise they are ordered by date.
  • DESCRIPTION:  This prompt applies only to notes with interdisciplinary entries under them.
    When an ID note is displayed or printed, the child entries are normally ordered by reference date under the parent entry. In some cases it may be preferable to order them alphabetically by title. If this parameter is set
    to YES, child entries are displayed by title rather than by date.
    The default order is by date.
.19 SEND ALERTS ON NEW ID ENTRY 0;19 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  Should the signer (cosigner) of an interdisciplinary parent note be alerted when a new entry is added to the note?
  • DESCRIPTION:  This parameter applies only to interdisciplinary parent notes.
    If this parameter is set to YES, the signer (cosigner) of an interdisciplinary parent note is alerted when a new entry is added to the note.
    The default is NO.
.2 SEND COSIGNATURE ALERT 0;20 SET
  • '0' FOR After Author has SIGNED;
  • '1' FOR Immediately;

  • LAST EDITED:  JAN 30, 2003
  • HELP-PROMPT:  Specify when the alert for cosignature should be sent
  • DESCRIPTION:  
    This parameter controls the sequence in which alerts are sent to the expected cosigner of a document. Allowable choices are:
1 PROCESSING STEPS 1;0 POINTER Multiple #8925.951 8925.951

  • DESCRIPTION:  
    OUT OF SERVICE
2 DIVISION 2;0 POINTER Multiple #8925.952 8925.952

  • DESCRIPTION:  Parameters CHART COPY PRINTER and STAT CHART COPY PRINTER may be independently defined according to Medical Center Division.
    Please indicate the Medical Center Division for which these parameters are being defined.
3 EDITOR SET-UP CODE 3;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  JAN 21, 2003
  • HELP-PROMPT:  This is Standard MUMPS code.
  • DESCRIPTION:  This is M code which is executed prior to invoking the user's preferred editor. It ordinarily sets local variables, which are then used in the editor's header, etc.
    For example, code written at Boston VAMC sets a local array containing patient demographics. An M-based editor used at the site can then display demographic information in a fixed header when a user edits a document.
    WRITE AUTHORITY: @
4 FILING ERROR ALERT RECIPIENTS 4;0 POINTER Multiple #8925.954 8925.954

  • DESCRIPTION:  These persons receive alerts from the upload filer process when a document of the given type cannot be filed/located, or has a missing field.
    If a document being uploaded has a missing/bad title, then alert recipients defined at the title level cannot be found. In this case, recipients named at the class level are alerted. For example, if a Progress Note is
    being uploaded and has a missing/bad title, then Progress Note-level recipients are alerted.
    If recipients are not specified, then alert recipients named in parameter UPLOAD ERROR ALERT RECIPIENTS in the TIU PARAMETER file are alerted as defaults.
5 USERS REQUIRING COSIGNATURE 5;0 POINTER Multiple #8925.955 8925.955

  • DESCRIPTION:  Please indicate which groups of users (i.e., User Classes) require cosignature for the type of document in question. For example, STUDENTS, INTERNS, LPNs, and other user classes may be identified as requiring a
    cosignature for PROGRESS NOTES.
    NOTE: Users specified as requiring a cosignature for DISCHARGE SUMMARY documents cannot be selected as Attending Physicians for these documents. This ensures that users who require a cosignature cannot cosign these
    documents.
6 HEADING 6;0 WORD-PROCESSING #8925.956

  • LAST EDITED:  APR 26, 2007
7 FOOTER 7;0 WORD-PROCESSING #8925.957
8 CLOSING 8;0 WORD-PROCESSING #8925.958

  • LAST EDITED:  MAR 29, 2007
9.01 JUSTIFY HEADING 9;1 SET
  • 'LJ' FOR LEFT JUSTIFIED;
  • 'CJ' FOR CENTER JUSTIFIED;
  • 'RJ' FOR RIGHT JUSTIFIED;

  • LAST EDITED:  MAY 11, 2007
  • HELP-PROMPT:  Select where to display the HEADING.
9.02 JUSTIFY FOOTER 9;2 SET
  • 'LJ' FOR LEFT JUSTIFY;
  • 'CJ' FOR CENTER JUSTIFY;
  • 'RJ' FOR RIGHT JUSTIFY;

  • LAST EDITED:  MAY 11, 2007
  • HELP-PROMPT:  Select where to display the FOOTER.
9.03 JUSTIFY CLOSING 9;3 SET
  • 'LJ' FOR LEFT JUSTIFY;
  • 'CJ' FOR CENTER JUSTIFY;
  • 'RJ' FOR RIGHT JUSTIFY;

  • LAST EDITED:  MAY 11, 2007
  • HELP-PROMPT:  Select where to display the CLOSING.
9.04 PAGE NUMBERS 9;4 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  MAY 10, 2007
  • HELP-PROMPT:  Enter 'YES' to display page numbers.
9.05 JUSTIFY PAGE NUMBERS 9;5 SET
  • 'LJ' FOR LEFT JUSTIFIED;
  • 'CJ' FOR CENTER JUSTIFIED;
  • 'RJ' FOR RIGHT JUSTIFIED;

  • LAST EDITED:  MAY 11, 2007
  • HELP-PROMPT:  Select where to display page numbers.
9.06 INSERT BLANK LINES 9;6 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>10)!(X<0)!(X?.E1"."1.N) X
  • LAST EDITED:  MAY 12, 2007
  • HELP-PROMPT:  Enter the number of blank lines to be inserted AFTER the header (if present). If no header, the blank lines will be added before the note text. 1-10 lines may be added.
10.1 EXCLUDE FROM COPY/PASTE 10;1 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  FEB 14, 2020
  • HELP-PROMPT:  Answer YES (1) to excluded this document from copy/paste tracking.
  • DESCRIPTION:  This field defaults to NO (0) if no value is set for a specific document. This should be a rarely used field as most documents should allow tracking of copy/paste data. Each site will need to determine if they use any
    special TIU notes which should/need to be excluded based on pre-existing policies/procedures which emphasize the re-use of text which cannot be accomplished via templates or other mechanisms.
  • RECORD INDEXES:  AC (#1572)

Found Entries, Total: 2

DOCUMENT DEFINITION: 8925.1^244^DISCHARGE SUMMARY    DOCUMENT DEFINITION: 8925.1^3^PROGRESS NOTES    
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries  | All