Developer Documentation » VDM » TIU_Parameters-8925_99
TIU Parameters (8925.99)
This file contains the site-configurable parameters for the Text Integration Utilities package. It will have one entry for each division, to support variable definition of package behavior at multi-divisional facilities.
|Label/Field Name||Field #||Description||Datatype||Attributes||Range|
||.01||Please enter the DIVISION these parameters apply to.||POINTER||INDEXED
|Enable Electronic Signature
||.02||Electronic signature is enabled when this parameter is set to 1. Until
such time as electronic signature is enabled, signatures are to be written
on the chart copy of the TIU document, and provision must be made for TIU
documents to be marked Signed on Chart.
|Characters Per Line
||.03||This value (default 60) is divided into the total number of ‘actual’
characters in a given transcribed document to derive the line count for
that document. By ‘actual’ characters, we mean all printable ASCII
characters, with multiple white space characters stripped. This prevents
transcriptionists from “stuffing” line counts by adding white space.
|Grace Period For Purge
||.04||OUT OF SERVICE. Purging is disabled.
This is the number of days following transcription for which a document
will be kept, prior to purge. Allowable range is from 90 to 7300 days (20
NOTE: Progress Notes and their addenda are not subject to purge,
regardless of this parameter. IF YOU WANT TO DISABLE PURGING ALTOGETHER,
LEAVE THIS PARAMETER EMPTY (or delete any existing value).
|Grace Period For Signature
||.05||This is the number of days following transcription before an author or
Attending Physician is notified of a deficiency. If no grace period is
entered, clinicians are not notified of overdue signatures.
|Optimize List Building For
||.06||This parameter determines whether or not TIU list building functions
invoke business rules, excluding from the list any documents the user is
not authorized to see. Checking business rules in this way optimizes
list building for security. It may be costly in terms of performance.
When optimized for performance (the default behavior of TIU), business
rules excluding notes from view are bypassed when building lists of
NOTE: This applies only to lists: when an unauthorized user attempts to
view the contents of a document from the resulting list, he is prevented
from doing so, with the following explanation:
Reviewing Item #1
You may not VIEW this UNSIGNED NURSE’S NOTE.
RETURN to continue…
|Suppress Review Notes Prompt
||.07||Applies to Progress Notes only. When this parameter is set to YES, TIU
suppresses the prompt which asks if the user wishes to see available
progress notes before entering a new note. This parameter is overridden
by the Personal Preference of same name. If neither parameter is entered,
the Review Notes prompt is NOT suppressed.
|Default Primary Provider
||.08||This parameter determines the behavior of the Primary Provider prompt for
a standalone encounter.
If the parameter has no value, the prompt has no default. If the parameter
has value 0, the user is not prompted for primary provider. If the
parameter has value 1, the default for the Primary Provider prompt is the
site’s default provider for the given location. If the parameter has
value 2, the default is the author if the author is a provider; if the
author is not a provider, the prompt has no default.
|ENUMERATION||AUTHOR (IF PROVIDER): 2
DEFAULT, BY LOCATION: 1
NONE, DON'T PROMPT: 0
|Ascii Upload Source
||.09||Applies only when the ASCII upload protocol is used. This field specifies
the source from which documents are uploaded. (H)ost indicates to the
upload processor that the source of the data is an ASCII host file (VMS or
DOS), while (R)emote indicates that the data is read from an ASCII stream
coming to VISTA from a terminal emulator on a remote computer (for
example, an IBM PC or compatible, or an Apple Macintosh).
|ENUMERATION||host file server: H
remote computer: R
|Record Header Signal
||.1||This is a free text tag or signal used by the upload process to determine
that a new document record header has been encountered. It may be as
simple as the three-character string “MSH” or as complex as “HEADERBEGIN”.
The signal “@@@”, used by the Surgery Package option to transmit operative
notes, is another possibility.
NOTE: Although you may define this parameter independently for each
DIVISION, we recommend that you choose just one such signal per site.
|End Of Message Signal
||.11||Applies only to transfers made using the ASCII protocol. This is the free
text signal to the upload process that the entire file/stream has been
transmitted without difficulty, and no more lines of data need to be read.
|Begin Report Text Signal
||.12||This is the signal to the upload processor that the fixed-field header for
a given report record has been fully read, and that the body of the
narrative report follows.
||.13||This ASCII character separates the various pieces of fixed-field
information in the message header. Please avoid using delimiters such as
”,”, or “:”, which may be contained within the data itself, using instead
less common symbols such as “”, “" or “~”.
|Future Appointment Range
||.14||This parameter determines how far in advance a future appointment may
be selected when entering a document for outpatient care.
Allowable values range from 1 to 180 days, defaulting to 1 day.
||.15||Applies only to transfers which use the ASCII protocol.
This is the ASCII value of the character which VISTA sends to the remote
computer to acknowledge receipt of the previous text line and to prompt
the remote to transmit another line. You may choose any character with an
ASCII value between 1 and 126.
If you are using the same remote to upload both MailMan messages and
textual reports, then we recommend using the “>” symbol, ASCII 62.
Otherwise, we suggest using the ACK character (ASCII 6).
NOTE: you may need to specify the same character as part of the ASCII
PROTOCOL parameters of the terminal emulation software on the remote.
|Upload Header Format
||.16||This field determines whether the upload filer expects delimited string or
captioned formats for the header of each document.
delimited string: D
||.17||This is the upload protocol used to transmit documents,
with a for ASCII, or k for KERMIT.
|Run Upload Filer In Foreground
||.18||This parameter specifies whether to run the filer for the upload process
in the foreground or in the background (as a Task).
If no preference is specified, the filer runs in the BACKGROUND.
|Enable Chart Copy Prompt
||.22||OUT OF SERVICE. See TIU Document Parameter ALLOW CHART PRINT OUTSIDE MAS.||BOOLEAN||false: 0
|Amendment Signature Block
||1.05||OUT OF SERVICE. The signer’s normal signature block is used for
This parameter allows the site to specify the format of the signature
block for an amendment.
While Business Rules determine who may amend documents, generally it is
the user class CHIEF,MIS who may do so. If this user is not the site’s
Privacy Act officer, then it may be desirable to enter a statement
indicating that the user is signing on behalf of the Privacy Act Officer.
For example, if the user’s name is John Smith, while the site’s Privacy
Act Officer is Jane Doe, RRT, then the AMENDMENT SIGNATURE BLOCK might be
entered as: “for Jane Doe, RRT, PRIVACY ACT OFFICER”.
The amendment information on the document would then appear as:
/es/ JOHN SMITH
for Jane Doe, RRT, PRIVACY ACT OFFICER
|Blank Character String
||1.06||This string of characters is used by the transcriptionist to represent a
“blank” when a word or phrase in the dictation cannot be understood for
inclusion in the transcription.
|Enable Notifications Date
||1.07||This date indicates to TIU when to begin sending signature notifications
(available/overdue for signature) to expected signers/cosigners.
Notifications are sent beginning on this date, and only for documents
entered on/after this date.
|Upload Error Alert Recipient
||2||These persons receive alerts from the upload/filer process when a document
cannot be filed/located or has missing fields.
This field is OVERRIDDEN by recipients set for the given document type in
parameter FILING ERROR ALERT RECIPIENTS in the TIU DOCUMENT PARAMETERS
|Start Of Add Sgnr Alert Period
||3.1||This is the start date for evaluating documents that have overdue
additional signatures. The value must be in a FileMan date range format
such as 6D, 3W or 4M. If this field is left blank, all documents
evaluated that have a date less than the END OF ADD SGNR ALERT PERIOD
date will be included.
Since the addition of the LENGTH OF SIGNER ALERT PERIOD parameter this
field should be set to the same value as that field. If LENGTH OF
SIGNER ALERT PERIOD is left blank then set this field to 12M, the
default value of the LENGTH OF SIGNER ALERT PERIOD when no value is
entered. LENGTH OF SIGNER ALERT PERIOD determines how far back in time
documents are evaluated.
|End Of Add Sgnr Alert Period
||3.2||This is the length in time from the current date that the TIU NIGHTLY
TASK will stop regenerating alerts for overdue additional signatures.
The value must be in a FileMan date range format such as 6D, 3W or 4M.
If no value is entered, the TIU NIGHTLY TASK will search for documents
in the TIU DOCUMENT File (8925) up to the current date.
|Length Of Signer Alert Period
||3.3||This is the length of time that the TIU NIGHTLY TASK will go back prior
to “today” when searching for documents that have overdue signatures.
The value must be in a FileMan date range format such as 6D, 3W or 4M.
If no value is entered, the TIU NIGHTLY TASK will begin searching for
documents starting at 1 year prior to “today” in the TIU DOCUMENTS file
Document generated on August 31st 2017, 2:55:41 pm