Term |
Description |
<RET> |
Carriage return. |
Access Code |
A unique sequence of characters known by and assigned only to the user, the system manager and/or designated alternate(s). The access code (in conjunction with the verify code) is used by the computer to identify authorized users. |
Action |
A functional process that a clinician or clerk uses in the TIU computer program. For example, “Edit” and “Search” are actions. Protocol is another name for Action. |
ADP |
Automated Data Processing |
ADP Coordinator/ ADPAC/Application Coordinator |
Automated Data Processing Application Coordinator. The person responsible for implementing a set of computer programs (application package) developed to support a specific functional area such as clinical procedures, PIMS, etc. |
ADT |
Advanced Data Type (InterSystems Cache). Also Admissions, Discharges, Transfers. |
AP |
Arterial pressure |
API |
Application Programming Interface. An interface that a computer system, library, or application provides in order to accept requests for services from other programs, and/or to allow data to be exchanged between them. |
Application |
A system of computer programs and files that have been specifically developed to meet the requirements of a user or group of users. |
Archive |
The process of moving data to some other storage medium, usually a magnetic tape, and deleting the information from active storage in order to free-up disk space on the system. |
Assessment |
Assessment is the documentation of a clinician’s observations and interpretation of a patient’s clinical state based on a particular set of observations. The documentation is in the form of name-value pairs with values selected from a predetermined set, of name-value pairs in which the value is a number or set of numbers, or of free text. Examples of assessments from paper ICU flowsheets are coma scale, patient opens eyes, pupil size, reaction to light, and so on. |
ASU |
Authorization/Subscription Utility. An application that allows sites to associate users with user classes, allowing them to specify the level of authorization needed to sign or order specific document types and orderables. ASU is distributed with TIU in this version; eventually it will probably become independent, to be used by many VistA packages. |
Attachments |
Attachments are files or images stored on a network share that can be linked to the CP study. CP is able to accept data/final result report files from automated instruments. The file types that can be used as attachments are the following: .txt - Text files .rtf - Rich text files .jpg - JPEG Images .jpeg - JPEG Images .bmp - Bitmap Images .tiff - TIFF Graphics (group 3 and group 4 compressed and uncompressed types) .pdf - Portable Document Format .html - Hypertext Markup Language .DOC (Microsoft Word) files are not supported. Be sure to convert .doc files to .rtf or to .pdf format. |
Background Processing |
Simultaneous running of a "job" on a computer while working on another job. Examples would be printing of a document while working on another, or the software might do automatic saves while you are working on something else. |
Background Task |
A job running on a computer while simultaneously working on a second job. |
Backup Procedures |
The provisions made for the recovery of data files and program libraries and for restart or replacement of ADP equipment after the occurrence of a system failure. |
Boilerplate Text |
A pre-defined TIU template that can be filled in for Titles, Speeding up the entry process. TIU exports several Titles with boilerplate text which can be modified to meet specific needs; sites can also create their own. |
BP |
Blood Pressure. |
Broker |
Software which mediates between two objects, such as a client and a server or a repository and a requestor. |
Browse |
Lookup the file folder for a file that you would like to select and attach to the study. (e.g., clicking the “...” button to start a lookup). |
Bulletin |
A canned message that is automatically sent by MailMan to a user when something happens to the database. |
Business Rule |
Part of ASU, Business Rules authorize specific users or groups of users to perform specified actions on documents in particular statuses (e.g., an unsigned CP note may be edited by a provider who is also the expected signer of the note). |
CAC |
Clinical Application Coordinator. |
Care Action |
Care action is an intervention scheduled on a patient that may or may not be ordered. |
CCB |
Change Control Board. |
CCDSS |
Clinical Care Delivery Support System. |
CCOW |
Clinical Context Object Workgroup. An HL7 standard protocol through which applications can synchronize in real-time, enabling Single Sign On and Context Management. |
CDR |
Clinical Data Repository. |
CGI |
CliO Generic Interface. |
CIS |
Clinical Information System. An ICU Clinical Information System is any hardware/software system that works in concert to collect, store, display, and/or enable manipulation of potential, clinically relevant information. A CIS also acts as an HL7 Gateway. Vendors of monitors and other instruments used in an ICU provide the CIS. The primary distinguishing feature of this CIS is its ability to manually select a subset of all available data and send it to the EMR. |
Class |
Part of Document Definitions, Classes group documents. For example, “CLINICAL PROCEDURES” is a class with many kinds of Clinical Procedures notes under it. Classes may be subdivided into other Classes or Document Classes. Besides grouping documents, Classes also store behavior which is then inherited by lower level entries. |
Clinical Flowsheets |
A module of the Clinical Procedures package that allows the collection of discrete data from medical devices or a Clinical Information System. It is a complete HL7 standardized instrument interface developed and owned by the Department of Veterans Affairs. This module is comprised of three components: the CP Flowsheets application, the CP Console application, and the CliO Generic Interface. |
Clinical Reminders |
A system which allows caregivers to track and improve preventive healthcare and disease treatment for patients and to ensure timely clinical interventions. |
CliO |
Clinical Observations database. |
CM |
Configuration Management. |
Consult |
Referral of a patient by the primary care physician to another hospital service/ specialty, to obtain a medical opinion based on patient evaluation and completion of any procedures, modalities, or treatments the consulting specialist deems necessary to render a medical opinion. |
Contingency Plan |
A plan that assigns responsibility and defines procedures for use of the backup/restart/recovery and emergency preparedness procedures selected for the computer system based on risk analysis for that system. |
CP |
Clinical Procedures. |
CP Console |
An application used by Administrators to configure the CP Flowsheets application and its interface settings. |
CP Definition |
CP Definitions are procedures within Clinical Procedures. |
CP Flowsheets |
A GUI component of the Clinical Flowsheets package. Its primary functions are to provide a means to display data collected from a medical device and to allow manual entry of data. Additional functionality is provided to display and print reports, verify incoming observational data, add comments, correct erroneous information, and submit TIU Notes to CPRS. |
CP Gateway |
The service application that prepares the data contents of HL7 messages for use in CP Hemodialysis. It requires no direct user interaction. |
CP Manager |
The CP Manager application is no longer supported after the installation of MD*1.0*16; it has been superseded by. CP Console. |
CP Study |
A CP study is a process created to link the procedure result from the medical device or/and to link the attachments browsed from a network share to the procedure order. |
CPRS |
Computerized Patient Record System. A comprehensive VistA program, which allows clinicians and others to enter and view orders, Progress Notes and Discharge Summaries (through a link with TIU), Problem List, view results, reports (including health summaries), etc. |
Data Dictionary |
A description of file structure and data elements within a file. |
DBIA |
Database Integration Agreement. |
Delphi |
A programming language, also known as Object Pascal. |
Device |
A hardware input/output component of a computer system (e.g., CRT, printer). |
Display Interval |
The amount of time that displays in each column of a flowsheet view. Display interval is configurable from 1 minute to 24 hours. Shorter interval settings can improve readability when a large amount of data is received over a short period of time. Longer interval settings allow you to view longer periods of time while reducing the amount of horizontal scrolling necessary to view all columns. |
DLL |
Dynamically Linked Library. These files provide the benefit of shared libraries. |
DOB |
Date of Birth. |
Document Class |
Document Classes are categories that group documents (Titles) with similar characteristics together. For example, Cardiology notes might be a Document Class, with Echo notes, ECG notes, etc. as Titles under it. Or maybe the Document Class would be Endoscopy Notes, with Colonoscopy notes, etc. under that Document Class. |
Document Definition |
Document Definition is a subset of TIU that provides the building blocks for TIU, by organizing the elements of documents into a hierarchy structure. This structure allows documents (Titles) to inherit characteristics (such as signature requirements and print characteristics) of the higher levels, Class and Document Class. It also allows the creation and use of boilerplate text and embedded objects. |
DUZ |
Designated user. This is the internal FileMan number for a particular user. |
Edit |
Used to change/modify data typically stored in a file. |
EMR |
Electronic Medical Record. HealtheVet, is the permanent medical record for a patient in VistA |
Field |
A data element in a file. |
File |
The M construct in which data is stored for retrieval later. A computer record of related information. |
File Manager or FileMan |
Within this manual, FileManager or FileMan is a reference to VA FileMan. FileMan is a set of M routines used to enter, edit, print, and sort/search related data in a file, a database. |
File Server |
A machine where shared software is stored. |
Flowsheet |
A flowsheet is a table, chart, spreadsheet, or other method of displaying data on two axes. One axis represents time intervals and the other axis represents the readings from an ICU monitor documented at the various time intervals. |
Flowsheet view |
A customizable subsection (or page) of a flowsheet. Flowsheet views are created by adding and arranging terms and choosing their default qualifiers. Flowsheet views can be set up to display observations, provide a way to manually enter observations, and display reports. |
Fluid off |
Cumulative volume of fluid removed from patient. |
Gateway |
The software that performs background processing for Clinical Procedures. |
Global |
An M term used when referring to a file stored on a storage medium, usually a magnetic disk. |
GUI |
Graphical User Interface. A Windows-like screen that uses pull-down menus, icons, pointer devices, and other metaphor-type elements that can make a computer program more understandable, easier to use, allow multi-processing (more than one window or process available at once), etc. |
HDR |
Health Data Repository. |
HEP (CUM) |
Cumulative heparin infusion |
HFS |
Host File System. |
HIPAA |
Health Insurance Portability and Accountability Act. |
HL7 |
Health Level 7. A language which various healthcare systems use to interface with one another. |
HL7 Gateway |
Hardware or software provided by a vendor that is able to receive information in a vendor’s proprietary format from one or more ICU monitors and other instruments, to translate the data into standardized HL7 message format, and to pass the messages to other systems. |
HR |
Heart Rate. |
HSD&D |
Office of Information (OI), Health Systems Design & Development. |
HSITES |
Health Systems Implementation, Training, Education, and Support. |
ICU |
Intensive Care Unit. |
IEN |
Internal Entry Number. |
IJ |
Internal Jugular. |
Instrument |
An instrument is a device used to perform a medical function on a patient. In Clinical Flowsheets instrument refers to ICU monitors, which are electronic devices that collect and/or display information concerning the physical state of a patient. Usually, the monitor attaches to a patient and takes readings over time without requiring intervention for each reading. |
Interpreter |
Interpreter is a user role exported with USR*1*19 to support the Clinical Procedures Class. The role of the Interpreter is to interpret the results of a clinical procedure. Users who are authorized to interpret the results of a clinical procedure are sent a notification when an instrument report and/or images for a CP request are available for interpretation. Business rules are used to determine what actions an interpreter can perform on a document of a specified class, but the interpreter themselves are defined by the Consults application. These individuals are ‘clinical update users’ for a given consult service. |
IRM |
Information Resource Management. |
IRMS |
Information Resource Management Service. |
JCAHO |
Joint Commission on Accreditation of Healthcare Organizations. |
Kernel |
A set of software utilities. These utilities provide data processing support for the application packages developed within the VA. They are also tools used in configuring the local computer site to meet the particular needs of the hospital. The components of this operating system include MenuMan, TaskMan, Device Handler, Log-on/Security, and other specialized routines. |
Key |
A level of access assigned to a Flowsheets user that determines which Flowsheets functions the user may perform. Refer to “User Role” in this Glossary. |
LAYGO |
An acronym for Learn As You Go. A technique used by VA FileMan to acquire new information as it goes about its normal procedure. It permits a user to add new data to a file. |
LPES/CPS |
Legacy Product Enterprise Support/Clinical Product Support. Enterprise Product Support (formerly Enterprise VistA Support). |
log |
A list that provides the time and description of events as they occur. |
M |
Formerly known as MUMPS or the Massachusetts (General Hospital) Utility Multi-Programming System. This is the programming language used to write all VistA applications. |
MailMan |
An electronic mail, teleconferencing, and networking system. |
MAP |
Mean Arterial Pressure. |
Menu |
A set of options or functions available to users for editing, formatting, generating reports, etc. |
Module |
A component of a software application that covers a single topic or a small section of a broad topic. |
MUMPS |
Massachusetts General Hospital Utility Multi-Programming System. Obsolete; now known as "M" programming language. |
Namespace |
A naming convention followed in the VA to identify various applications and to avoid duplication. It is used as a prefix for all routines and globals used by the application. |
Network Server Share |
A machine that is located on the network where shared files are stored. |
Notebook |
This term refers to a GUI screen containing several tabs or pages. |
NTE |
Not To Exceed. |
OI |
Office of Information. Formerly known as Chief Information Office Field Office, Information Resource Management Field Office, and Information Systems Center. |
option |
A functionality that is invoked by the user. The information defined in the option is used to drive the menu system. Options are created, associated with others on menus, or given entry/exit actions. |
optional page |
One of two special types of flowsheet views which provides a way to track a specific condition (e.g., a pacemaker) on its own flowsheet view. An Optional Page can display only once in a given flowsheet. If an optional page is closed and then redisplayed, any data previously entered still displays. |
Package |
Otherwise known as an application. A set of M routines, files, documentation and installation procedures that support a specific function within VistA. |
page |
This term refers to a tab on a GUI screen or notebook. |
Password |
A protected word or string of characters that identifies or authenticates a user, a specific resource, or an access type (synonymous with Verify Code). |
PCE |
Patient Care Encounter. |
Permission |
Setting that can be used to allow access to particular views, flowsheets, etc. to one or more specific users and to control the type of access each user has. |
PIMS |
Patient Information Management System. |
Pivot |
Swap the axes of a table or chart. This causes the values that were displayed along the vertical axis to be displayed along the horizontal axis and the values that were displayed along the horizontal axis to be displayed along the vertical axis. |
PM |
Project Manager. |
Pointer |
A special data type of VA FileMan that takes its value from another file. This is a method of joining files together and avoiding duplication of information. |
PRN |
As needed. |
Procedure Request |
Any procedure (EKG, Stress Test, etc.) which may be ordered from another service/specialty without first requiring formal consultation. |
Program |
A set of M commands and arguments, created, stored, and retrieved as a single unit in M. |
Protocol |
A set of rules governing communication within and between computing endpoints. |
PS |
Provider Systems. |
PV |
Pulmonary Vascular. |
QG |
Quality Gate. |
Qualifiers |
A word or phrase that provides specific information about an observation. For example, an observation could have qualifiers such as Unit (f=degrees Fahrenheit, c=degrees Celsius, bpm=beats per minute, rpm=respirations per minute, etc.), Method (Cu=cuff BP, Dop=Doppler BP, etc.), Position (Ly=lying, Si=sitting, St=standing, etc.), Location (La=left arm, LL=left leg, RA=right arm, RL=right leg, etc.), Quality (A=accurate, E=Estimated), etc. |
Queuing |
The scheduling of a process/task to occur later. Queuing is normally done if a task is a heavy user of computer resources. |
RAID |
Redundant Array of Inexpensive Disks. A data storage scheme using multiple hard drives to share or replicate data among the drives. |
Result |
A consequence of an order. Refers to evaluation or status results. When you use the Complete Request (CT) action on a consult or request, you are transferred to TIU to enter the results. |
Routine |
A set of M commands and arguments, created, stored, and retrieved as a single unit in M. |
RPC |
Remote Procedure Call. A protocol that allows a computer program running on one host to cause code to be executed on another host. |
Rx |
Prescription. |
SAC |
Standards And Conventions. |
Security Key |
A function which unlocks specific options and makes them accessible to an authorized user. |
Sensitive Information |
Any information which requires a degree of protection and which should be made available only to authorized users. |
Service |
A long-running executable designed to perform specific functions without user intervention. Windows services can be configured to restart automatically when the operating system is rebooted. |
SGML |
Standard Generalized Markup Language. |
Shift |
A period of time that can be defined in CP Flowsheets. This often corresponds to the time an individual an individual works. |
Site Configurable |
A term used to refer to features in the system that can be modified to meet the needs of each site |
Software |
A generic term for a related set of computer programs, such as an operating system that enables user programs to run. |
SQA |
Software Quality Assurance. |
SRS |
Software Requirements Specification. |
SSN |
Social Security Number. |
Status Symbols |
Codes used in order entry and Consults displays to designate the status of the order. |
STS |
Standards and Terminology Services. An initiative to create and maintain standardized terminology throughout the VA by assigning a code to every term. |
Supplemental page |
One of two special types of flowsheet views which provides a way to track a specific condition (e.g., a pressure wound) on its own flowsheet view. Multiple supplemental pages can be added to a single flowsheet in order to track numerous specific conditions. If a supplemental page is closed and then a new supplemental page is added, the new supplemental page is blank. |
Tab |
One of the five primary GUI screens of the CP Flowsheets application: Flowsheet, Alarms, Reports, Log Files, and HL7 Monitor. |
Task Manager or TaskMan |
A part of Kernel which allows programs or functions to begin at specified times or when devices become available. See Queuing. |
Term |
As used in Flowsheets, a term is any piece of relevant data. A term, like “Blood Pressure” will typically have one or more associated measures, modifiers, or qualifiers. |
Terminology |
Standardization of words and terms used in Flowsheets. |
Title |
Titles are definitions for documents. They store the behavior of the documents which use them. |
TIU |
Text Integration Utilities. |
TMP |
Trans Membrane Pressure. |
UFR |
Ultrafiltration Rate. |
UI |
User Interface. |
UNC |
Universal Naming Convention. |
Untrusted device |
A medical instrument which has not been mapped for use with the Clinical Flowsheets package. Data sent from an untrusted device will not display in a flowsheet view until someone reviews it (on the CP Flowsheets Log Files tab) and marks it as verified. |
URL |
Uniform Resource Locator. A means of finding a resource (such as a web page or a device) on the Internet. |
URR |
Urea Reduction Ratio. The reduction in urea as a result of dialysis. |
User |
A person who enters and/or retrieves data in a system, usually utilizing a CRT. |
User Class |
User Classes are the basic components of the User Class hierarchy of ASU (Authorization/Subscription Utility) which allows sites to designate who is authorized to do what to documents or other clinical entities. |
User Role |
User Role (in a documentation context). The role of the user with respect to the document in question (e.g., Author/Dictator, Expected Signer, Expected Cosigner, Attending Physician, etc.). |
User Role |
User Role (in a Flowsheets setup context). The role of a Flowsheets user with respect to which Flowsheets functions the user will have permission to perform. Flowsheets User Role include the following. • MD ADMINISTRATOR • MD MANAGER • MD HL7 MANAGER • MD READ-ONLY • MD TRAINEE |
Utility |
An M program that assists in the development and/or maintenance of a computer system. |
UUEncoded format |
A form of binary to text encoding whose name derives from "Unix-to-Unix encoding”. |
VA |
Department of Veterans Affairs. Formerly the Veterans Administration. |
VAMC |
Department of Veterans Affairs Medical Center. |
VDEF |
VistA Data Extraction Framework. |
Verify Code |
A unique security code which serves as a second level of security access. Use of this code is site specific. This term is sometimes used interchangeably the term password. |
VHA |
Veteran Health Administration. |
VistA |
Veterans Health Information Systems and Technology Architecture. |
VP |
Venous Pressure. |
VUID |
Veterans Health Administration (VHA) Unique Identifier. A unique identifier that specifies individual data elements or observations. In Clinical Flowsheets, each term is assigned a VUID. |
Workstation |
A personal computer running the Windows 9x or NT operating system. |
XML |
Extensible Markup Language. A simplified subset of Standard Generalized Markup Language (SGML). Its primary purpose is to facilitate the sharing of data across different information systems. |
XMS |
Extended Memory Specification. The specification describing the use of extended memory in real mode for storing data. |