The Master Data Model for Veteran Care

Developer Documentation » VDM » TIU_Document_Parameters-8925_95

TIU Document Parameters (8925.95)

This file stores parameters which modify the processing requirements of individual document types, and their decendents.

Global: ^TIU(8925.95,

Domain: Non-Clinical

Properties

Label/Field Name Field # Description Datatype Attributes Range
Document Definition
  document_definition
.01 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.)
POINTER INDEXED
REQUIRED
TIU_Document_Definition-8925_1
Require Release
  require_release
.02 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.
BOOLEAN   false: 0
true: 1
Require Mas Verification
  require_mas_verification
.03 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.
ENUMERATION   YES, ALWAYS: 1
DIRECT ENTRY ONLY: 3
UPLOAD ONLY: 2
NO: 0
Require Author To Sign
  require_author_to_sign
.04 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.
BOOLEAN   false: 0
true: 1
When May Chart Copy Be Printed
  when_may_chart_copy_be_printed
.05 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.
POINTER   TIU_Status-8925_6
Routine Print Event(s)
  routine_print_events
.06 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.
ENUMERATION   release: R
both: B
verification: V
Stat Print Event(s)
  stat_print_events
.07 This field is identical to ROUTINE PRINT EVENT(S), except that it
applies to documents of STAT urgency rather than ROUTINE urgency.
ENUMERATION   release: R
both: B
verification: V
Manual Print After Entry
  manual_print_after_entry
.08 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.
BOOLEAN   false: 0
true: 1
Allow Chart Print Outside Mas
  allow_chart_print_outside_mas
.09 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.
BOOLEAN   false: 0
true: 1
Allow >1 Records Per Visit
  allow_1_records_per_visit
.1 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.
BOOLEAN   false: 0
true: 1
Enable Irt Interface
  enable_irt_interface
.11 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.
BOOLEAN   false: 1
true: 0
Irt Deficiency
  irt_deficiency
.12 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.
POINTER   Irt_Type_Of_Deficiency-393_3
Default Printer
  default_printer
.13 NOT IN SERVICE.

When a user prints a document of the given type and is prompted for
DEVICE, this serves as the default.
POINTER   Device-3_5
Suppress Dx/cpt On Entry
  suppress_dx_cpt_on_entry
.14 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.
BOOLEAN   false: 0
true: 1
Force Response To Exposures
  force_response_to_exposures
.15 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.
BOOLEAN   false: 0
true: 1
Ask Dx/cpt On All Opt Visits
  ask_dx_cpt_on_all_opt_visits
.16 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.
BOOLEAN   false: 0
true: 1
Send Alerts On Addenda
  send_alerts_on_addenda
.17 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.
BOOLEAN   false: 0
true: 1
Order Id Entries By Title
  order_id_entries_by_title
.18 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.
BOOLEAN   false: 0
true: 1
Send Alerts On New Id Entry
  send_alerts_on_new_id_entry
.19 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.
BOOLEAN   false: 0
true: 1
Send Cosignature Alert
  send_cosignature_alert
.2 This parameter controls the sequence in which alerts are sent to the
expected cosigner of a document. Allowable choices are:
ENUMERATION   Immediately: 1
After Author has SIGNED: 0
Processing Steps
  processing_steps
1 OUT OF SERVICE OBJECT   Processing_Steps-8925_951
Division
  division
2 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.
OBJECT   Division-8925_952
Editor Set-up Code
  editor_setup_code
3 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.
STRING    
Filing Error Alert Recipients
  filing_error_alert_recipients
4 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.
POINTER   New_Person-200
Users Requiring Cosignature
  users_requiring_cosignature
5 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.
POINTER   Usr_Class-8930
Heading
  heading
6   STRING    
Footer
  footer
7   STRING    
Closing
  closing
8   STRING    
Justify Heading
  justify_heading
9.01   ENUMERATION   LEFT JUSTIFIED: LJ
CENTER JUSTIFIED: CJ
RIGHT JUSTIFIED: RJ
Justify Footer
  justify_footer
9.02   ENUMERATION   CENTER JUSTIFY: CJ
LEFT JUSTIFY: LJ
RIGHT JUSTIFY: RJ
Justify Closing
  justify_closing
9.03   ENUMERATION   CENTER JUSTIFY: CJ
LEFT JUSTIFY: LJ
RIGHT JUSTIFY: RJ
Page Numbers
  page_numbers
9.04   BOOLEAN   false: 0
true: 1
Justify Page Numbers
  justify_page_numbers
9.05   ENUMERATION   LEFT JUSTIFIED: LJ
CENTER JUSTIFIED: CJ
RIGHT JUSTIFIED: RJ
Insert Blank Lines
  insert_blank_lines
9.06   NUMERIC    

↑ Return to top

Sub-Files

Processing Steps (8925.951)

ID
Processing_Steps-8925_951

Properties

Label/Field Name Field # Description Datatype Attributes Range
Processing Steps
  processing_steps
.01 This is a step or action (e.g., verification) in the processing of a
document that moves it from one state (e.g., unverified) to another (e.g.,
unsigned).
POINTER INDEXED
REQUIRED
Usr_Action-8930_8
Sequence
  sequence
.02 This is the serial sequence in the processing of this document in which
the current step should ordinarily occur.
NUMERIC    
Required
  required
.03 Indicate whether this step is required or optional for completion of this
document (e.g., Progress Notes must be cosigned ONLY when the author is a
Medical Student).
ENUMERATION   REQUIRED: 1
OPTIONAL: 0
Resulting Status
  resulting_status
.04 This is the status of the document following completion of the step in
question. For instance, if a discharge summary should attain the status
UNSIGNED, following the verification step, this would be indicated here.
POINTER   TIU_Status-8925_6
Condition Text
  condition_text
.05 Describe the condition under which an optional step will be required
(e.g., cosignature of a Progress Note is required only when the author of
the note is a provider in training, e.g., a Medical Student).
STRING    
Condition Code
  condition_code
1 This is a line of MUMPS code which imposes the condition by which an
optional step must occur. It must modify the boolean special variable,
$TEST, to indicate whether the step must occur. e.g., in the case where a
medical student author’s a progress note, the MUMPS code for the condition
may look like:

I +$$ISA^USRLM(TIUAUTH,”MEDICAL STUDENT”)
STRING    

↑ Return to top

Division (8925.952)

ID
Division-8925_952

Properties

Label/Field Name Field # Description Datatype Attributes Range
Division
  division
.01 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.
POINTER INDEXED
REQUIRED
Medical_Center_Division-40_8
Chart Copy Printer
  chart_copy_printer
.02 This parameter is primarily useful for DISCHARGE SUMMARIES, or other
documents where automatic central printing of chart copies on site-
configurable events are most useful (e.g., INTERIM SUMMARIES or
OPERATIVE REPORTS at some point in the future).

When defined along with a STAT CHART COPY PRINTER, this is the device to
which chart copies of documents with ROUTINE urgencies will be sent
automatically. If no STAT CHART COPY PRINTER is defined, then ALL
documents of the current type will be sent to this device, regardless of
their urgencies.

Note: If field MANUAL PRINT AFTER ENTRY is set to YES, then auto-print
is ignored.
POINTER   Device-3_5
Stat Chart Copy Printer
  stat_chart_copy_printer
.03 This parameter is primarily useful for DISCHARGE SUMMARIES, or other
documents where automatic central printing of chart copies on site-
configurable events are most useful (e.g., INTERIM SUMMARIES or
OPERATIVE REPORTS at some point in the future).

When defined along with a CHART COPY PRINTER, this is the device to
which chart copies of documents with STAT urgencies will be sent
automatically.

Note: If field MANUAL PRINT AFTER ENTRY is set to YES, then auto-print
is ignored.
POINTER   Device-3_5

↑ Return to top


Document generated on August 31st 2017, 2:55:41 pm