# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | FREE TEXT | B | 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) | |
.02 | treating specialty | 0;2 | POINTER | 45.7 | ASPEC | This field defines the specialty that this procedure falls under. |
.03 | require external data | 0;3 | BOOLEAN | 0:No 1:Yes | 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. | |
.04 | default tiu note | 0;4 | POINTER | 8925.1 | 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) | |
.05 | hospital location | 0;5 | POINTER | 44 | This is the location that will be used when creating the TIU note for interpretation. This location will be used for workload reporting. | |
.06 | processing application | 0;6 | SET OF CODES | 1:DEFAULT 2:HEMODIALYSIS | 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. | |
.07 | auto submit | 0;7 | SET OF CODES | 0:No, manually complete 1:Yes, Submit to VistA Imaging | 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. | |
.08 | external data directory | 0;8 | FREE TEXT | This field contains a reference to a network share where user supplied attachments are located for this procedure. | ||
.09 | active | 0;9 | BOOLEAN | 0:No 1:Yes | Yes/No to indicate active procedures that can be linked to Consults. | |
.1 | instrument | .1;0 | MULTIPLE | 702.011 | This multiple contains instruments that generate results for this procedure. | |
.11 | high volume | 0;10 | BOOLEAN | 0:No 1:Yes | This field is used as a flag indicator to specify if this procedure is high volume or not. | |
.12 | processed result | 0;11 | SET OF CODES | 0:Final Result 1:Multiple Results 2:Cumulative Result | This field is a flag which indicates whether a final result, multiple results, or cumulative result is associated with this procedure. | |
.13 | id(+) | ID;1 | FREE TEXT | 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}". | ||
.9 | description | .9;1 | FREE TEXT | This is a detailed DESCRIPTION of this procedure. A sample DESCRIPTION could be "ABD Paracentisis followup". |