| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | patient(+) | 0;1 | POINTER | 2 | B | This field contains a pointer to the Patient file (#2) for this transaction. |
| .011 | ssn (c) | COMPUTED | This field contains the computed value of the patient's SSN from the Patient file (#2). | |||
| .012 | dob (c) | COMPUTED | This field contains the computed value of the patient's DOB from the Patient file (#2). | |||
| .02 | created date/time(+) | 0;2 | DATE-TIME | This field contains the date/time the transaction was created. | ||
| .03 | created by(+) | 0;3 | POINTER | 200 | This field contains the DUZ of the user that created this transaction. | |
| .04 | cp definition(+) | 0;4 | POINTER | 702.01 | ACP | This field contains a pointer to the CP DEFINITION file (#702.01) indicating the procedure of the transaction. |
| .05 | consult number | 0;5 | FREE TEXT | ACON | This field contains an Consult number from Request/Consultation file (#123). This field represents the Consult order that is matched up to this transaction. (Reference IA #3162) | |
| .06 | tiu note | 0;6 | POINTER | 8925 | ATIU | This field contains a pointer to the TIU DOCUMENT file (#8925) representing the note that contains the interpretation of this transaction as well as the links to the associated images. (Reference IA #3376) |
| .07 | vstring | 0;7 | FREE TEXT | This field contains the vstring. The vstring is in the following format: Visit type_";"_Visit Date/Time_";"_Hospital Location (internal entry number of the visit). | ||
| .08 | transaction message | 0;8 | FREE TEXT | This field contains a short 80 characters text message of the transaction status update. | ||
| .09 | transaction status | 0;9 | SET OF CODES | 0:New 1:Submitted 2:Error 3:Complete 4:Ready to Complete 5:Pending Instrument Data 6:Cancelled | AS | This field contains the status of this transaction. Available statuses are listed below with a description of each. 0: New This transaction has been created by an external application and needs to be checked-in with the CPUser application and submitted to an instrument. An example of this status would be a consent form scanned in via the VistA Imaging Capture Workstation that creates a CP Study record stub with a TIU document but allows further input with the CPUser application. 1: Submitted This transaction has been submitted to the VistA Imaging Background Processor and is awaiting the copy process to place the attachments for the study on the VistA Imaging server. A study in this status is not accessible until VistA Imaging returns a status of Complete or Error and logs any errors encountered in the submission process. 2: Error This transaction has encountered an error while being submitted to VistA Imaging. The error may be due to the TIU note creation or a problem with the attachments sent to the VistA Imaging server. Error messages are logged with the transaction and can be reviewed by users when opening the transaction in an error status. 3: Complete This transaction has completed the process and has successfully created a TIU note for interpretation on the selected Consult and if any attachments were included they have been successfully copied to the VistA Imaging server. 4: Ready to Complete This transaction has been checked in and alternatively, if submitted to a bi-directional instrument, has received the data back from the instrument. Users may open these transactions and view the Consult/Procedure order as well as assign instrument results to the study. Once these steps have been done this study can be submitted to VistA Imaging. 5: Pending Instrument Data This transaction has been submitted to a bi-directional instrument and is awaiting that instrument to return the results of the procedure. Transactions in this status should not be opened until the instrument has returned the results, assigned them to the study, and marked it as Ready to Complete. 6: Cancelled This transaction has been cancelled when the procedure request in Consult Report Tracking and CPRS has been cancelled or discontinued. |
| .091 | error messages | .091;0 | MULTIPLE | 702.091 | This multiple contains the information on the error messages that Clinical Procedures receive from API calls with Consults, TIU, CPRS, and VistA Imaging. | |
| .1 | image | .1;0 | MULTIPLE | 702.1 | This multiple contains the image attachment information for the transaction. | |
| .11 | submitted to instrument | 0;11 | POINTER | 702.09 | AINST | Points to the instrument definition that this study was submitted to at the time of check-in. |
| .12 | instrument order number | 0;12 | FREE TEXT | AION | Contains the unique order number for this study that is sent to the instrument if it is bi-directional so the results can be auto-matched back to this study by the CP Gateway. Field is 1-22 characters and contains only numeric characters. | |
| .13 | visit | 1;1 | POINTER | 9000010 | AVISIT | This is the Visit entry returned from PCE. (Reference IA# 1902) |
| .14 | scheduled date/time | 3;1 | DATE-TIME | ASD | This field contains the date/time when the HL7 message should be sent by CP to the device for this CP transaction. | |
| .3 | conversion id reference | 2;1 | FREE TEXT | ACONV | This field is the Reference Conversion ID. It is a variable pointer to the Medicine files. It indicates which converted Medicine report record is associated with the CP Transaction study. This field helps to keep track which CP Transaction study was created for the Medicine report conversion. This field is a variable pointer to the following files: 691 ECHO 691.1 CARDIAC CATHETERIZATION 691.5 ELECTROCARDIOGRAM (EKG) 691.6 HOLTER 691.7 EXERCISE TOLERANCE TEST 691.8 ELECTROPHYSIOLOGY (EP) 694 HEMATOLOGY 694.5 CARDIAC SURGERY RISK ASSESSMENT 698 GENERATOR IMPLANT 698.1 V LEAD IMPLANT 698.2 A LEAD IMPLANT 698.3 PACEMAKER SURVEILLANCE 699 ENDOSCOPY/CONSULT 699.5 GENERALIZED PROCEDURE/CONSULT 700 PULMONARY FUNCTION TESTS 701 RHEUMATOLOGY | |
| .991 | image count | COMPUTED | Computed field to return the total number of images associated with this transaction. |