STANDARD DATA DICTIONARY #2006.68 -- MAGJ USER DATA FILE 3/24/25 PAGE 1
STORED IN ^MAG(2006.68, (1 ENTRY) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 3.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file stores various Vistarad user settings, preferences, etc., that are created on the Vistarad workstation.
DD ACCESS: @
RD ACCESS: @
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
POINTED TO BY: DEFAULT VISTARAD USERPREF RAD field (#202) of the IMAGING SITE PARAMETERS File (#2006.1)
DEFAULT VISTARAD USERPREF NON field (#203) of the IMAGING SITE PARAMETERS File (#2006.1)
CROSS
REFERENCED BY: USER(AC), DESCRIPTION(B)
2006.68,.01 DESCRIPTION 0;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>30!($L(X)<3)!'(X'?1P.E) X
LAST EDITED: JAN 15, 2003
HELP-PROMPT: Answer must be 3-30 characters in length.
DESCRIPTION:
The User Data entry name.
CROSS-REFERENCE: 2006.68^B
1)= S ^MAG(2006.68,"B",$E(X,1,30),DA)=""
2)= K ^MAG(2006.68,"B",$E(X,1,30),DA)
2006.68,1 USER 0;2 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: FEB 13, 2004
DESCRIPTION:
The name of the user; pointer the New Person file (200)
CROSS-REFERENCE: 2006.68^AC
1)= S ^MAG(2006.68,"AC",$E(X,1,30),DA)=""
2)= K ^MAG(2006.68,"AC",$E(X,1,30),DA)
2006.68,1.5 USER TYPE 0;3 SET (Required)
'0' FOR Non-Radiology;
'1' FOR Rad Tech;
'2' FOR Resident Radiologist;
'3' FOR Staff Radiologist;
'9' FOR sysAdmin;
LAST EDITED: APR 04, 2005
HELP-PROMPT: Enter User Type code
2006.68,2 VR-WS VR-WS;0 Multiple #2006.682 (Add New Entry without Asking)
LAST EDITED: FEB 18, 2004
DESCRIPTION:
Vistarad workstation preferences stored under this node.
2006.682,.01 TAG 0;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>80!($L(X)<1) X
LAST EDITED: MAR 07, 2006
HELP-PROMPT: Answer must be 1-80 characters in length.
DESCRIPTION:
Tag, or label, that identifies this collection of settings/preferences.
TECHNICAL DESCR: The details of the data stored are defined by the client software, and are aggregated under
separate tags for different w/s types. Each tag's data is independently accessible by the
client,which can query for:
1) Tags stored; or,
2) Data for named tags, or
3) Tags and associated KEYS (described below)
CROSS-REFERENCE: 2006.682^B
1)= S ^MAG(2006.68,DA(1),"VR-WS","B",$E(X,1,30),DA)=""
2)= K ^MAG(2006.68,DA(1),"VR-WS","B",$E(X,1,30),DA)
2006.682,1 DATA 1;0 WORD-PROCESSING #2006.6821 (NOWRAP)
LAST EDITED: APR 04, 2003
DESCRIPTION:
Client data is stored here.
LAST EDITED: APR 04, 2003
2006.682,3 KEYS 2;0 WORD-PROCESSING #2006.6823 (NOWRAP)
DESCRIPTION: Keys data are strings that are structured by the client for containing search values for the
internal operation of the workstation preferences, whenever and/or if applicable. The Vistarad
RPCs can provide access to the Keys data separately from the full set of user preference data.
LAST EDITED: MAY 04, 2004
2006.68,3 VR-HP VR-HP;0 Multiple #2006.683 (Add New Entry without Asking)
DESCRIPTION:
Hanging Protocols, templates, and related data stored under this node.
2006.683,.01 TAG 0;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>80!($L(X)<3) X
LAST EDITED: MAR 07, 2006
HELP-PROMPT: Answer must be 3-80 characters in length.
DESCRIPTION:
Tag, or label, that identifies the HP or Template.
TECHNICAL DESCR: The details of the data stored are defined by the client software, and are aggregated under
separate tags for each Hanging protocol or template. Each tag's data is independently accessible
by the client, which can query for:
1) Tags stored; or,
2) Data for named tags, or
3) Tags and associated KEYS (described below)
CROSS-REFERENCE: 2006.683^B
1)= S ^MAG(2006.68,DA(1),"VR-HP","B",$E(X,1,30),DA)=""
2)= K ^MAG(2006.68,DA(1),"VR-HP","B",$E(X,1,30),DA)
2006.683,1 DATA 1;0 WORD-PROCESSING #2006.6831 (NOWRAP)
DESCRIPTION:
The actual hanging protocol and template data is stored here.
LAST EDITED: APR 04, 2005
DESCRIPTION:
HP and Template data, formatted by client in XML format.
2006.683,2 KEYS 2;0 WORD-PROCESSING #2006.6832 (NOWRAP)
DESCRIPTION: Keys data are strings that are structured by the client for containing search values for the
internal operation of the hanging protocols, whenever and/or if applicable. The Vistarad RPCs
can provide access to the Keys data separately from the full HP definition data.
LAST EDITED: APR 04, 2005
DESCRIPTION: Keys data are strings that are structured by the client for containing search values for the
internal operation of the HP logic. The Keys are exerpted from the XML data to support
client operations and/or logic outside the HP which complements logic inside the HP.
FILES POINTED TO FIELDS
NEW PERSON (#200) USER (#1)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):