STANDARD DATA DICTIONARY #702.01 -- CP DEFINITION FILE 6/27/25 PAGE 1
STORED IN ^MDS(702.01, *** NO DATA STORED YET *** SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 1.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file defines all the procedures used by the Clinical Procedures package. All elements that define a procedure are in this
file. This file is exported with data, but entries may be added by the site.
DD ACCESS: @
RD ACCESS:
WR ACCESS: #
DEL ACCESS: #
LAYGO ACCESS: #
AUDIT ACCESS:
IDENTIFIED BY: TREATING SPECIALTY (#.02)
PRIMARY KEY: A (#82)
Uniqueness Index: PK (#904)
File, Field: 1) ID (702.01,.13)
POINTED TO BY: CLINICAL PROCEDURE field (#1.01) of the REQUEST/CONSULTATION File (#123)
CONSULTS CLIN PROC field (#.01) of the CONSULTS CLIN PROC sub-field (#123.0334) of the GMRC CONSULT MAPPING File
(#123.033)
CLINICAL PROCEDURE field (#.04) of the GMRC PROCEDURE File (#123.3)
CP DEFINITION field (#.04) of the CP TRANSACTION File (#702)
CP DEFINITION field (#.02) of the MEDICINE FILE PARAMETERS sub-field (#703.91) of the CP CONVERSION File (#703.9)
CROSS
REFERENCED BY: INSTRUMENT(AINST), TREATING SPECIALTY(ASPEC), NAME(B), NAME(UC)
INDEXED BY: ID (PK)
702.01,.01 NAME 0;1 FREE TEXT (Required)
Procedure Name
INPUT TRANSFORM: K:$L(X)>30!($L(X)<3)!'(X?1A.E) X
LAST EDITED: AUG 05, 2002
HELP-PROMPT: Answer must be 3-30 characters in length.
DESCRIPTION: This field contains the name of the procedure. It should be descriptive of the procedure and
contain 3-30 alphanumeric characters. The first character MUST be a letter. To maintain
consistency it is recommended that all procedures be entered in UPPERCASE letters as well.
(Reference IA #3139)
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 702.01^B
1)= S ^MDS(702.01,"B",$E(X,1,30),DA)=""
2)= K ^MDS(702.01,"B",$E(X,1,30),DA)
Standard Fileman "B" index for the file.
CROSS-REFERENCE: 702.01^UC^MUMPS
1)= S ^MDS(702.01,"UC",$$UP^XLFSTR(X),DA)=""
2)= K ^MDS(702.01,"UC",$$UP^XLFSTR(X),DA)
Used to validate a new entry as unique without case sensitivity.
702.01,.02 TREATING SPECIALTY 0;2 POINTER TO FACILITY TREATING SPECIALTY FILE (#45.7)
Treating Specialty
LAST EDITED: FEB 23, 2001
HELP-PROMPT: Enter the associated Treating Specialty.
DESCRIPTION:
This field defines the specialty that this procedure falls under.
CROSS-REFERENCE: 702.01^ASPEC
1)= S ^MDS(702.01,"ASPEC",$E(X,1,30),DA)=""
2)= K ^MDS(702.01,"ASPEC",$E(X,1,30),DA)
Standard Fileman "ASPEC" index for the sub-file on the TREATING SPECIALTY field.
702.01,.03 REQUIRE EXTERNAL DATA 0;3 SET
Require External Data
'0' FOR No;
'1' FOR Yes;
LAST EDITED: DEC 11, 2001
HELP-PROMPT: Enter Yes or No
DESCRIPTION: Setting this field to Yes will force this procedure to be processed via the CPUser executable for
matching whether or not there are instruments associated with it.
702.01,.04 DEFAULT TIU NOTE 0;4 POINTER TO TIU DOCUMENT DEFINITION FILE (#8925.1)
TIU Note Title
LAST EDITED: JUL 24, 2007
HELP-PROMPT: Enter a TIU Note Title
DESCRIPTION: This field contains a TIU Note Title to use as the default when CP creates a note for
interpretation for this procedure. (Reference IA #3377)
702.01,.05 HOSPITAL LOCATION 0;5 POINTER TO HOSPITAL LOCATION FILE (#44)
Hospital Location
LAST EDITED: NOV 27, 2000
HELP-PROMPT: Enter a Hospital Location.
DESCRIPTION: This is the location that will be used when creating the TIU note for interpretation. This
location will be used for workload reporting.
702.01,.06 PROCESSING APPLICATION 0;6 SET
Processing Application
'1' FOR DEFAULT;
'2' FOR HEMODIALYSIS;
LAST EDITED: JUL 19, 2005
DESCRIPTION: This field is used to indicate if this is a Hemodialysis procedure or not. The field is a set of
codes, 1=DEFAULT so it will be processed by Clinical Procedures or 2=HEMODIALYSIS and the procedure
will be processed by the Hemodialysis application.
702.01,.07 AUTO SUBMIT 0;7 SET
Auto Submit To VistA Imaging
'0' FOR No, manually complete;
'1' FOR Yes, Submit to VistA Imaging;
LAST EDITED: JUL 29, 2002
DESCRIPTION: This field only applies to procedures that are performed by instruments with Bi-directional
interface capabilities. This field is used to indicate whether the image attachment should be
automatically submitted to VistA Imaging once the procedure is performed and the result is passed
to CP or the submission process of the image should be done manually with user interface.
702.01,.08 EXTERNAL DATA DIRECTORY 0;8 FREE TEXT
External Attachment Directory
INPUT TRANSFORM: K:$L(X)>150!($L(X)<3) X
LAST EDITED: APR 17, 2002
HELP-PROMPT: Answer must be 3-150 characters in length.
DESCRIPTION: This field contains a reference to a network share where user supplied attachments are located for
this procedure.
702.01,.09 ACTIVE 0;9 SET
Active
'0' FOR No;
'1' FOR Yes;
LAST EDITED: MAY 24, 2000
HELP-PROMPT: Enter Yes or No.
DESCRIPTION:
Yes/No to indicate active procedures that can be linked to Consults.
702.01,.1 INSTRUMENT .1;0 POINTER Multiple #702.011
DESCRIPTION:
This multiple contains instruments that generate results for this procedure.
702.011,.01 INSTRUMENT 0;1 POINTER TO CP INSTRUMENT FILE (#702.09) (Multiply asked)
Instrument
LAST EDITED: AUG 01, 2002
HELP-PROMPT: Enter a CP INSTRUMENT.
DESCRIPTION: This field contains a pointer to an instrument in the CP Instrument file (#702.09) that generates
results for this procedure.
CROSS-REFERENCE: 702.011^B
1)= S ^MDS(702.01,DA(1),.1,"B",$E(X,1,30),DA)=""
2)= K ^MDS(702.01,DA(1),.1,"B",$E(X,1,30),DA)
Standard Fileman "B" index for the sub-file.
CROSS-REFERENCE: 702.01^AINST
1)= S ^MDS(702.01,"AINST",$E(X,1,30),DA(1),DA)=""
2)= K ^MDS(702.01,"AINST",$E(X,1,30),DA(1),DA)
This cross reference is used to quickly retrieve the available instruments for a CP Definition
entry as well as prevent instruments from being deleted that are still pointed to.
702.01,.11 HIGH VOLUME 0;10 SET
High Volume
'0' FOR No;
'1' FOR Yes;
LAST EDITED: MAY 27, 2009
HELP-PROMPT: Answer whether this procedure is high volume or not.
DESCRIPTION:
This field is used as a flag indicator to specify if this procedure is high volume or not.
702.01,.12 PROCESSED RESULT 0;11 SET
Processed Result
'0' FOR Final Result;
'1' FOR Multiple Results;
'2' FOR Cumulative Result;
LAST EDITED: FEB 14, 2005
HELP-PROMPT: Enter the processed result.
DESCRIPTION: This field is a flag which indicates whether a final result, multiple results, or cumulative result
is associated with this procedure.
702.01,.13 ID ID;1 FREE TEXT (Required) (Key field)
INPUT TRANSFORM: K:$L(X)>38!($L(X)<38)!'(X?1"{"8UN1"-"4UN1"-"4UN1"-"4UN1"-"12UN1"}") X
LAST EDITED: MAY 27, 2009
HELP-PROMPT: Answer with the system generated GUID for this procedure.
DESCRIPTION: This is a Globally Unique IDentifier (GUID) for this procedure. This is maintained nationally so it
is the same throughout the enterprise. A sample ID could be
"{69DBD11E-9A8C-4ECE-AFA4-73947218807D}".
FIELD INDEX: PK (#904) REGULAR IR LOOKUP & SORTING
Unique for: Key A (#82), File #702.01
Short Descr: Uniqueness Index for Key 'A' of File #702.01
Description: This provides a quick reference to all unique procedures.
Set Logic: S ^MDS(702.01,"PK",$E(X,1,38),DA)=""
Kill Logic: K ^MDS(702.01,"PK",$E(X,1,38),DA)
Whole Kill: K ^MDS(702.01,"PK")
X(1): ID (702.01,.13) (Subscr 1) (Len 38)
702.01,.9 DESCRIPTION .9;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>250!($L(X)<1) X
LAST EDITED: MAY 27, 2009
HELP-PROMPT: Answer must be 1-250 characters in length.
DESCRIPTION: This is a detailed DESCRIPTION of this procedure. A sample DESCRIPTION could be "ABD Paracentisis
followup".
FILES POINTED TO FIELDS
CP INSTRUMENT (#702.09) INSTRUMENT:INSTRUMENT (#.01)
FACILITY TREATING SPECIALTY
(#45.7) TREATING SPECIALTY (#.02)
HOSPITAL LOCATION (#44) HOSPITAL LOCATION (#.05)
TIU DOCUMENT DEFINITION (#8925.1) DEFAULT TIU NOTE (#.04)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):