Home Package List Routine Alphabetical List Global Alphabetical List FileMan Files List FileMan Sub-Files List Package Component Lists Package-Namespace Mapping

Info | Desc | Directly Accessed By Routines | Accessed By FileMan Db Calls | Pointed To By FileMan Files | Pointer To FileMan Files | Fields | ICR | All

Print Page as PDF

Global: ^MDD(702

Package: Clinical Procedures

Global: ^MDD(702

Information

FileMan FileNo	FileMan Filename	Package
702	CP TRANSACTION	Clinical Procedures

Description

This file contains the transactions between the instruments and user generated data as it is matched to a consult order and a TIU document is created for the results. It also manages the interface between the images and the Imaging server.

Directly Accessed By Routines, Total: 57

Package	Total	Routines
Clinical Procedures	46	MDAPI MDAR7M MDARP3 MDCLN MDCVT MDCVT1 MDHL7A MDHL7B MDHL7BH MDHL7U2 MDHL7U3 MDHL7XXX MDKUTL MDKUTLR MDNCHK MDPCE MDPCE1 MDPCE2 MDPOST14 MDPOST6A MDPS1 MDPS3 MDPS4 MDPS5 MDPSU MDPURGE MDRPCNT MDRPCNT1 MDRPCOP MDRPCOT MDRPCOT1 MDRPCOT2 MDRPCOTA MDRPCOTH MDRPCOW MDRPCU MDRPCW MDRPCW1 MDSTUDL MDSTUDW MDWCAN MDWCHK MDWOR ^MDK(704.202 MDWORC MDWORSR
Medicine	4	MCARPS1 MCARPS2 MCARPS3 MCORMN
VA FileMan	2	ITEM YEAR
Imaging	1	MAGDHOWP

Accessed By FileMan Db Calls, Total: 34

Package	Total	Routines
Clinical Procedures	28	MDAPI MDAR7M MDCVT1 MDHL7A MDHL7BH MDHL7U2 MDHL7U3 MDNCHK MDPOST14 MDPOST6A MDPS1 MDPS3 MDPSU MDPURGE MDRPCNT1 MDRPCOP MDRPCOT MDRPCOT1 MDRPCOT2 MDRPCOTH MDRPCOW MDRPCW MDSTUDL MDSTUDW MDWOR MDWORC MDWORSR MDWORSR2
Virtual Patient Record	4	VPRDJ01 VPREVNT VPREVSND VPRSDAC
Enterprise Health Management Platform	1	HMPDJ01
Imaging	1	MAGDHOWP

Pointed To By FileMan Files, Total: 4

Package	Total	FileMan Files
Clinical Procedures	4	CP_HL7_LOG(#704.002)[.07] CP_TRANSACTION_TIU_HISTORY(#702.001)[.01] CP RESULT REPORT(#703.1)[.05] HEMODIALYSIS STUDY(#704.202)[.01]

Pointer To FileMan Files, Total: 7

Package	Total	FileMan Files
Clinical Procedures	3	CP RESULT REPORT(#703.1)[#702.1(.03)] CP DEFINITION(#702.01)[.04] CP INSTRUMENT(#702.09)[.11]
Kernel	1	NEW PERSON(#200)[.03]
PCE Patient Care Encounter	1	VISIT(#9000010)[.13]
Registration	1	PATIENT(#2)[.01]
Text Integration Utility	1	TIU DOCUMENT(#8925)[.06]

Fields, Total: 19

Field #	Name	Loc	Type	Details
.01	PATIENT	0;1	POINTER TO PATIENT FILE (#2)	**********************REQUIRED FIELD********************** PATIENT(#2) LAST EDITED: `APR 04, 2005` HELP-PROMPT: `Enter a patient name.` DESCRIPTION: `This field contains a pointer to the Patient file (#2) for this transaction.` CROSS-REFERENCE: `702^B` `1)= S ^MDD(702,"B",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"B",$E(X,1,30),DA)` `Contains the standard Fileman "B" index of the file.` RECORD INDEXES: `AVPR (#683)`
.011	SSN (C)		COMPUTED	MUMPS CODE: `X ^DD(702,.011,9.2) S X=$P(Y(702,.011,101),U,9) S D0=Y(702,.011,80)` `9.2 = S Y(702,.011,80)=$S($D(D0):D0,1:""),Y(702,.011,1)=$S($D(^MDD(702,D0,0)):^(0),1:""),D0=$P(Y(702,.011,1),U,1) S:'$D(^DPT(+D0,0)) D0=-1 S Y(702,.011,101)=$S($D(^DPT(D0,0)):^(0),1:"")` ALGORITHM: `#.01:#.09` LAST EDITED: `JUL 25, 2000` DESCRIPTION: `This field contains the computed value of the patient's SSN from the Patient file (#2).`
.012	DOB (C)		COMPUTED	MUMPS CODE: `X ^DD(702,.012,9.2) S Y(702,.012,102)=X,Y=$P(Y(702,.012,101),U,3) X:$D(^DD(2,.03,2)) ^(2) S X=Y S D0=Y(702,.012,80)` `9.2 = S Y(702,.012,80)=$G(D0),Y(702,.012,1)=$S($D(^MDD(702,D0,0)):^(0),1:""),D0=$P(Y(702,.012,1),U,1) S:'D0!'$D(^DPT(+D0,0)) D0=-1 S Y(702,.012,101)=$S($D(^DPT(D0,0)):^(0),1:"")` ALGORITHM: `#.01:#.03` LAST EDITED: `JUL 25, 2000` DESCRIPTION: `This field contains the computed value of the patient's DOB from the Patient file (#2).`
.02	CREATED DATE/TIME	0;2	DATE	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `S %DT="ESTXR",%DT(0)="-NOW" D ^%DT K %DT(0) S X=Y K:Y<1 X` LAST EDITED: `APR 04, 2005` HELP-PROMPT: `Enter the date/time the procedure was entered.` DESCRIPTION: `This field contains the date/time the transaction was created.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` RECORD INDEXES: `AVPR (#683)`
.03	CREATED BY	0;3	POINTER TO NEW PERSON FILE (#200)	**********************REQUIRED FIELD********************** NEW PERSON(#200) LAST EDITED: `APR 02, 2001` HELP-PROMPT: `User who created this transaction.` DESCRIPTION: `This field contains the DUZ of the user that created this transaction.`
.04	CP DEFINITION	0;4	POINTER TO CP DEFINITION FILE (#702.01)	**********************REQUIRED FIELD********************** CP DEFINITION(#702.01) LAST EDITED: `APR 04, 2005` HELP-PROMPT: `Enter a CP Procedure Definition.` DESCRIPTION: `This field contains a pointer to the CP DEFINITION file (#702.01) indicating the procedure of the transaction.` CROSS-REFERENCE: `702^ACP` `1)= S ^MDD(702,"ACP",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"ACP",$E(X,1,30),DA)` `This cross reference maintains a list of transactions by CP Definition for quick retrieval. It is also used to prevent deletion of CP Definitions that are being pointed to.` RECORD INDEXES: `AVPR (#683)`
.05	CONSULT NUMBER	0;5	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>30!($L(X)<1) X` LAST EDITED: `JUL 19, 2002` HELP-PROMPT: `Answer must be 1-30 characters in length.` DESCRIPTION: `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)` CROSS-REFERENCE: `702^ACON` `1)= S ^MDD(702,"ACON",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"ACON",$E(X,1,30),DA)` `This is the cross reference of the Consult.`
.06	TIU NOTE	0;6	POINTER TO TIU DOCUMENT FILE (#8925)	TIU DOCUMENT(#8925) LAST EDITED: `NOV 28, 2007` HELP-PROMPT: `TIU note for interpretation of this transaction` DESCRIPTION: `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)` CROSS-REFERENCE: `702^ATIU` `1)= S ^MDD(702,"ATIU",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"ATIU",$E(X,1,30),DA)` `3)= Cross Reference of the TIU Note` `This is the cross reference of the TIU Note.`
.07	VSTRING	0;7	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>50!($L(X)<1) X` LAST EDITED: `APR 13, 2001` HELP-PROMPT: `Answer must be 1-50 characters in length.` DESCRIPTION: `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	INPUT TRANSFORM: `K:$L(X)>80!($L(X)<1) X` LAST EDITED: `FEB 26, 2001` HELP-PROMPT: `Answer must be 1-80 characters in length.` DESCRIPTION: `This field contains a short 80 characters text message of the transaction status update.`
.09	TRANSACTION STATUS	0;9	SET	'0' FOR New; '1' FOR Submitted; '2' FOR Error; '3' FOR Complete; '4' FOR Ready to Complete; '5' FOR Pending Instrument Data; '6' FOR Cancelled; LAST EDITED: `APR 04, 2005` HELP-PROMPT: `Status of this transaction.` DESCRIPTION: `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.` CROSS-REFERENCE: `702^AS` `1)= S ^MDD(702,"AS",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"AS",$E(X,1,30),DA)` `It is a cross reference on the status of the CP study and it is used for quick look up.`
.091	ERROR MESSAGES	.091;0	Multiple #702.091	702.091 DESCRIPTION: `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	702.1 DESCRIPTION: `This multiple contains the image attachment information for the transaction.`
.11	SUBMITTED TO INSTRUMENT	0;11	POINTER TO CP INSTRUMENT FILE (#702.09)	CP INSTRUMENT(#702.09) LAST EDITED: `AUG 01, 2002` DESCRIPTION: `Points to the instrument definition that this study was submitted to at the time of check-in.` CROSS-REFERENCE: `702^AINST` `1)= S ^MDD(702,"AINST",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"AINST",$E(X,1,30),DA)` `This cross reference maintains a list of transactions by instrument for quick retrieval. It is also used to prevent deletion of instruments that are being pointed to.`
.12	INSTRUMENT ORDER NUMBER	0;12	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>22!($L(X)<1) X` LAST EDITED: `MAY 13, 2003` HELP-PROMPT: `Answer must be 1-22 characters in length.` DESCRIPTION: `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.` TECHNICAL DESCR: `Generated from $$NOW^XLFDT() padded to 14 characters and stripped of the decimal point. Guaranteed unique by comparison to the AION cross reference in this file.` CROSS-REFERENCE: `702^AION` `1)= S ^MDD(702,"AION",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"AION",$E(X,1,30),DA)` `This cross reference is used by the GETSTDY^MDRPCOT1 extrinsic to quickly retrieve the study ien from the instrument order number.`
.13	VISIT	1;1	POINTER TO VISIT FILE (#9000010)	VISIT(#9000010) LAST EDITED: `JUN 30, 2004` HELP-PROMPT: `Enter a Visit number.` DESCRIPTION: `This is the Visit entry returned from PCE. (Reference IA# 1902)` `UNEDITABLE` CROSS-REFERENCE: `702^AVISIT` `1)= S ^MDD(702,"AVISIT",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"AVISIT",$E(X,1,30),DA)` `3)= Do Not Delete.` `This cross reference is used to make sure that a Visit file entry is not deleted as long as there is an entry.` CROSS-REFERENCE: `702^AUPNV^MUMPS` `1)= D ADD^AUPNVSIT` `2)= D SUB^AUPNVSIT` `3)= Do Not Delete.` `This cross reference tells Visit Tracking how many file entries are using (point to) a Visit file entry.`
.14	SCHEDULED DATE/TIME	3;1	DATE	INPUT TRANSFORM: `S %DT="EST" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `MAY 17, 2007` DESCRIPTION: `This field contains the date/time when the HL7 message should be sent by CP to the device for this CP transaction.` CROSS-REFERENCE: `702^ASD` `1)= S ^MDD(702,"ASD",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"ASD",$E(X,1,30),DA)` `3)= This is the scheduled date/time needed for sending HL7 message.` `This cross reference contains the scheduled date/time as to when the HL7 message should be sent to the device for the CP transaction. It is used for easy look up to process the study.`
.3	CONVERSION ID REFERENCE	2;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>30!($L(X)<1) X` LAST EDITED: `SEP 20, 2004` HELP-PROMPT: `Answer must be 1-30 characters in length.` DESCRIPTION: `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` CROSS-REFERENCE: `702^ACONV` `1)= S ^MDD(702,"ACONV",$E(X,1,30),DA)=""` `2)= K ^MDD(702,"ACONV",$E(X,1,30),DA)` `3)= Do Not Delete.` `This cross reference is used to keep track of which CP transaction study was created during the Medicine report conversion and which Medicine record it is associated with.`
.991	IMAGE COUNT		COMPUTED	MUMPS CODE: `S X=0 X "F Y=0:0 S Y=$O(^MDD(702,D0,.1,Y)) Q:'Y S X=X+1" S X=$J(X,0,0)` ALGORITHM: `S X=0 X "F Y=0:0 S Y=$O(^MDD(702,D0,.1,Y)) Q:'Y S X=X+1" (ALWAYS 0 DECIMAL DIGITS)` DESCRIPTION: `Computed field to return the total number of images associated with this transaction.`

ICR, Total: 1

ICR LINK	Subscribing Package(s)	Fields Referenced	Description
ICR #6929	Imaging	PATIENT (.01). Access: Read w/Fileman CP DEFINITION (.04). Access: Read w/Fileman CONSULT NUMBER (.05). Access: Read w/Fileman VSTRING (.07). Access: Read w/Fileman SUBMITTED TO INSTRUMENT (.11). Access: Read w/Fileman CONSULT NUMBER (.05). Access: Direct Global Read & w/Fileman

Info | Desc | Directly Accessed By Routines | Accessed By FileMan Db Calls | Pointed To By FileMan Files | Pointer To FileMan Files | Fields | ICR | All