Global: ^GMR(123

FileMan FileNo	FileMan Filename	Package
123	REQUEST/CONSULTATION	Consult Request Tracking

Package	Total	Routines
Consult Request Tracking	111	ASSOCIATED RESULTS GMRC CONSULTS LIST GMRC110P GMRC113P GMRCA1 GMRCAAC GMRCACMT GMRCACTM GMRCAD31 GMRCADC GMRCAFRD GMRCALOR GMRCAPI GMRCAR GMRCART GMRCASF GMRCASV GMRCAU GMRCCB GMRCCCR1 GMRCCCRA GMRCCCRI GMRCCP GMRCCPRS GMRCCXDC GMRCDIS GMRCDPCK GMRCDST GMRCEDIT GMRCEDT1 GMRCEDT2 GMRCEDT3 GMRCEDT4 GMRCEDT5 GMRCGUIA GMRCGUIB GMRCGUIC GMRCGUIS GMRCGUIU GMRCHL7 GMRCHL72 GMRCHL7A GMRCHL7B GMRCHL7H GMRCHL7I GMRCHL7U GMRCIAC1 GMRCIAC2 GMRCIACT GMRCIBKG GMRCIERR GMRCIEV1 GMRCIEVT GMRCILKP GMRCIMSG GMRCINC GMRCIR GMRCISEG GMRCISG1 GMRCITR GMRCIUTL GMRCMED GMRCMSS GMRCONS1 GMRCP GMRCP5 GMRCP50 GMRCP5A GMRCP5B GMRCP5D GMRCP98 GMRCPSL2 GMRCQCST GMRCR GMRCRA GMRCSLDT GMRCSLM1 GMRCSLM2 GMRCSLM3 GMRCSLM4 GMRCSTL2 GMRCSTL8 GMRCSTLB GMRCSTS GMRCSTS1 GMRCSTSU GMRCSTU GMRCSUBS GMRCT GMRCTIU GMRCTIU1 GMRCTIUA GMRCTIUE GMRCTIUL GMRCTIUP GMRCUTL1 GMRCUTL2 GMRCXR GMRCY73 GMRCYP15 GMRCYP27 GMRCYP31 GMRCYP41 GMRCYP68 GMRCYP69 GMRCYP70 GMRSPRE REMOTE RESULTS REQUEST PROCESSING ACTIVITY ^GMR(123 UPDATE USER CLASSES W/O NOTIFS
Scheduling	20	SD53P496 SD686PST SDAM1 SDAM3 SDCCRSCU SDCNP0 SDCNSLT SDEC07 SDEC07A SDEC50 SDEC51 SDEC54 SDECINI2 SDECRMG2 SDHLAPT2 SDM2 SDQQCN2 SDRPA07 SDTMBUS SDTMPHLA
Imaging	6	MAGDHOW5 MAGDQR12 MAGNU003 MAGREADER MAGSTATUS MAGVRS82
Order Entry Results Reporting	5	OR3C100A ORQ2 ORQQCN1 ORQQCN2 ORWTIU
Clinical Procedures	2	MDCONUTL MDWCHK
Text Integration Utility	2	TIU144 TIUCOPR1
Care Management	1	ORRCACK
Health Summary	1	GMTSCNB
Medicine	1	MCPOS04
Mental Health	1	YTQCONS
Prosthetics	1	RMPRFC3
Radiology Nuclear Medicine	1	RAORDR
Virtual Patient Record	1	VPRP15

Package	Total	Routines
Consult Request Tracking	41	GMRC110P GMRCACMT GMRCAD31 GMRCADG GMRCAFRD GMRCAPI GMRCCB GMRCCC GMRCCCR1 GMRCCCRA GMRCCD GMRCCXDC GMRCDIS GMRCDST GMRCEDT2 GMRCEDT3 GMRCEDT5 GMRCGUIA GMRCGUIB GMRCGUIC GMRCHL7A GMRCHL7B GMRCHL7H GMRCIAC1 GMRCIACT GMRCIAIT GMRCIEVT GMRCITR GMRCP5A GMRCP5D GMRCSLM2 GMRCSTS1 GMRCSTSU GMRCSUBS GMRCTIU1 GMRCTIUA GMRCXR GMRCYP23 GMRCYP27 GMRCYP31 GMRCYP41
Imaging	30	MAGDCCS2 MAGDCCS3 MAGDGMRC MAGDHLSV MAGDHOW1 MAGDHOW3 MAGDHOW4 MAGDHOW5 MAGDHOWC MAGDHOWP MAGDHOWS MAGDIR8A MAGDIR9E MAGDQR06 MAGDQR73 MAGDRCU2 MAGDRPC4 MAGDRPC9 MAGDRPCA MAGDRPCC MAGDTR01 MAGDTR03 MAGDTR05 MAGDTRLU MAGGTIA2 MAGNGMR MAGVIM02 MAGVIM06 MAGVORDR MAGVRS82
Scheduling	14	SDCCRCOR SDCCRSEN SDEC07A SDEC51 SDEC51A SDEC54 SDECGMR SDECINI2 SDECUTL SDHL7APU SDHLAPT2 SDRPA07 SDTMBUS SDTMPHLA
Clinical Procedures	10	MDHL7BH MDHL7U2 MDHL7XXX MDNCHK MDPS1 MDPS3 MDPSU MDRPCOT1 MDWCHK MDWORSR
Virtual Patient Record	5	VPRDJ03 VPRDMC VPRENC VPREVNT VPRHS
Enterprise Health Management Platform	3	HMPDJ03 HMPDMC HMPEQLM
Automated Medical Information Exchange	2	DVBA8861 DVBAVRX1
Order Entry Results Reporting	2	OR3C100A ORQ20
Radiology Nuclear Medicine	2	RAORDR RAORDR1
Text Integration Utility	2	TIU144 TIUHL7P3
Health Summary	1	GMTSCNB
Mobile Scheduling Applications Suite	1	MBAADAL1
VA Point of Service	1	VPSRPC13

Package	Total	FileMan Files
Medicine	15	ECHO(#691)[1001] CARDIAC CATHETERIZATION(#691.1)[1001] ELECTROCARDIOGRAM (EKG)(#691.5)[1001] HOLTER(#691.6)[1001] EXERCISE TOLERANCE TEST(#691.7)[1001] ELECTROPHYSIOLOGY (EP)(#691.8)[1001] HEMATOLOGY(#694)[1001] GENERATOR IMPLANT(#698)[1001] V LEAD IMPLANT(#698.1)[1001] A LEAD IMPLANT(#698.2)[1001] PACEMAKER SURVEILLANCE(#698.3)[1001] ENDOSCOPY/CONSULT(#699)[1001] GENERALIZED PROCEDURE/CONSULT(#699.5)[1001] PULMONARY FUNCTION TESTS(#700)[1001] RHEUMATOLOGY(#701)[1001]
Prosthetics	2	RECORD OF PROS APPLIANCE/REPAIR(#660)[8.9] PROSTHETIC SUSPENSE(#668)[20]
Scheduling	2	HOSPITAL LOCATION(#44)[#44.003(688)] SDEC APPOINTMENT(#409.84)[.22]
Automated Medical Information Exchange	1	FORM 28-8861(#396.9)[#396.914(.01)]
Imaging	1	TELEREADER READ/UNREAD LIST(#2006.5849)[.01]
Registration	1	HOME TELEHEALTH PATIENT(#391.31)[3]
Text Integration Utility	1	TIU DOCUMENT(#8925)[1405]

Package	Total	FileMan Files
Medicine	15	ECHO(#691)[11, #123.03(.01)] CARDIAC CATHETERIZATION(#691.1)[11, #123.03(.01)] ELECTROCARDIOGRAM (EKG)(#691.5)[11, #123.03(.01)] HOLTER(#691.6)[11, #123.03(.01)] EXERCISE TOLERANCE TEST(#691.7)[11, #123.03(.01)] ELECTROPHYSIOLOGY (EP)(#691.8)[11, #123.03(.01)] HEMATOLOGY(#694)[11, #123.03(.01)] GENERATOR IMPLANT(#698)[11, #123.03(.01)] V LEAD IMPLANT(#698.1)[11, #123.03(.01)] A LEAD IMPLANT(#698.2)[11, #123.03(.01)] PACEMAKER SURVEILLANCE(#698.3)[11, #123.03(.01)] ENDOSCOPY/CONSULT(#699)[11, #123.03(.01)] GENERALIZED PROCEDURE/CONSULT(#699.5)[#123.03(.01)] PULMONARY FUNCTION TESTS(#700)[11, #123.03(.01)] RHEUMATOLOGY(#701)[11, #123.03(.01)]
Kernel	4	DEVICE(#3.5)[#123.02(8)] INSTITUTION(#4)[.05, .07, #123.051(.03)] PROTOCOL(#101)[4, 5, 6] NEW PERSON(#200)[7, 10, #123.02(3), #123.02(4), #123.02(7)]
Consult Request Tracking	3	REQUEST ACTION TYPES(#123.1)[9, #123.02(1)] GMRC PROCEDURE(#123.3)[4] REQUEST SERVICES(#123.5)[1, #123.02(6)]
Order Entry Results Reporting	2	ORDER(#100)[.03] ORDER STATUS(#100.01)[8]
Clinical Procedures	1	CP DEFINITION(#702.01)[1.01]
Registration	1	PATIENT(#2)[.02]
Scheduling	1	HOSPITAL LOCATION(#44)[.04, 2]
Text Integration Utility	1	TIU DOCUMENT(#8925)[16, #123.02(9), #123.03(.01)]

Fields, Total: 43

Field #	Name	Loc	Type	Details
.001	NUMBER		NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `JUN 04, 1991` HELP-PROMPT: `Type a Number between 0 and 99999999, 0 Decimal Digits`
.01	FILE ENTRY DATE	0;1	DATE	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `S %DT="ETXR" D ^%DT S X=$P($H,",",2),Y=Y_"."_$E(0,1,2-$L(X\3600))_(X\3600)_$E(0,1,2-$L(X#3600\60))_(X#3600\60)_$E(0,1,2-$L(X#60))_(X#60),Y=+Y,X=Y K:Y<1 X` HELP-PROMPT: `This is the date/time of the entry of the consultation/request.` DESCRIPTION: `Date of actual entry of consultation request into the file. Transparent to user.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` CROSS-REFERENCE: `123^B` `1)= S ^GMR(123,"B",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"B",$E(X,1,30),DA)`
.02	PATIENT NAME	0;2	POINTER TO PATIENT FILE (#2)	**********************REQUIRED FIELD********************** PATIENT(#2) LAST EDITED: `OCT 08, 2001` HELP-PROMPT: `Enter the name of a patient or the last 4 digits of the SSN.` DESCRIPTION: `This is the Patient who the consult or request was ordered for. Enter the patient's name, or the last four digits of the SSN.` CROSS-REFERENCE: `123^AD^MUMPS` `1)= I $P(^GMR(123,DA,0),"^",7) S GMRCD=9999999-$P(^GMR(123,DA,0),"^",7),^GMR(123,"AD",X,GMRCD,DA)="" K GMRCD` `2)= I $P(^GMR(123,DA,0),"^",7) S GMRCD=9999999-$P(^GMR(123,DA,0),"^",7) K ^GMR(123,"AD",X,GMRCD,DA),GMRCD` `The "AD" cross-reference allows look up of patient consults in reverse chronological "DATE OF REQUEST" order.` CROSS-REFERENCE: `123^F` `1)= S ^GMR(123,"F",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"F",$E(X,1,30),DA)` RECORD INDEXES: `ACP (#102)`
.03	OE/RR FILE NUMBER	0;3	POINTER TO ORDER FILE (#100)	ORDER(#100) LAST EDITED: `NOV 03, 1998` HELP-PROMPT: `Enter the File 100 internal entry number of this record.` DESCRIPTION: `This is the internal entry number of the order in the Orders File (100). The consult sends CPRS information about the consult which is stored in File 100. This is the IEN of the consult in that file.` CROSS-REFERENCE: `123^AC` `1)= S ^GMR(123,"AC",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"AC",$E(X,1,30),DA)` `This cross-reference allows determining the request entry in 123 based on the ORIFN from OE/RR.`
.04	PATIENT LOCATION	0;4	POINTER TO HOSPITAL LOCATION FILE (#44)	HOSPITAL LOCATION(#44) LAST EDITED: `OCT 15, 2001` HELP-PROMPT: `Enter the Hospital Location of this patient.` DESCRIPTION: `This is the location of the patient when the consult/request order was placed.` CROSS-REFERENCE: `123^AL` `1)= S ^GMR(123,"AL",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"AL",$E(X,1,30),DA)`
.05	ORDERING FACILITY	0;21	POINTER TO INSTITUTION FILE (#4)	INSTITUTION(#4) LAST EDITED: `MAY 02, 1996` HELP-PROMPT: `If this is a consult/request sent to another Institution, then this is the SENDING hospital/institution.` DESCRIPTION: `This field contains the number, from file 4, of the institution/hospital that is requesting the consult. This field is mandatory if the consult/ request is being sent to another hospital/institution, so that routing` `information can be obtained in order to return the results to the sending hospital/institution.`
.06	REMOTE CONSULT FILE ENTRY	0;22	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999999999999)!(X<1)!(X?.E1"."1.N) X` LAST EDITED: `DEC 03, 2001` HELP-PROMPT: `Type a number between 1 and 999999999999, 0 Decimal Digits` DESCRIPTION: `This is the ^GMR(123, file number of the consult from a foreign database. It is stored here so that when the consult is returned in an HL7 message, it can be located at the sending facility. Also, if the sending facility` `needs to send updated consult information to the receiving facility, this number will reference the consult number there so that the data can be added/ammended and tracking information can be updated.` RECORD INDEXES: `AIFC (#111)`
.07	ROUTING FACILITY	0;23	POINTER TO INSTITUTION FILE (#4)	INSTITUTION(#4) LAST EDITED: `DEC 03, 2001` HELP-PROMPT: `Enter the institution for routing updates` DESCRIPTION: `This field will contain the INSTITUTION to which communications and updates regarding this request will be routed. If the request is being requested and performed locally, this field will be blank.` RECORD INDEXES: `AIFC (#111)`
.1	DISPLAY TEXT OF ITEM ORDERED	1.11;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>80!($L(X)<1) X` LAST EDITED: `JUL 12, 1998` HELP-PROMPT: `Enter the display text the user selected to place the order.` DESCRIPTION: `This is the display text of the item ordered. If the order was placed using a quick order, then the Display text is the text from the Order Dialog File. If the order was placed by selecting an Orderable Item, then the` `text is the Print Name from the Orderable Item file.`
.125	IFC ROLE	12;5	SET	'P' FOR PLACER; 'F' FOR FILLER; LAST EDITED: `JUL 13, 2001` DESCRIPTION: `This field will define the role of the particular VistA system in the fullfillment of the inter-facility consult. This facilitates proper HL7 message formats.` `PLACER indicates that this VistA system originated and ordered this request.` `FILLER indicates that this request was generated at the institution in the ORDERING FACILITY field.`
.126	REMOTE ORDERING PROVIDER	12;6	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>40!($L(X)<2) X` LAST EDITED: `FEB 04, 2002` HELP-PROMPT: `Answer must be 2-40 characters in length` DESCRIPTION: `This field contains the name of the requesting provider of an inter-facility consult. This field is only defined on an inter-facility consult on file at a consulting site.` CROSS-REFERENCE: `123^AIP^MUMPS` `1)= S ^GMR(123,"AIP",$E(X,1,40),DA)=""` `2)= K ^GMR(123,"AIP",$E(X,1,40),DA)`
.131	IFC REMOTE SERVICE NAME	13;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>63!($L(X)<3) X` LAST EDITED: `NOV 07, 2001` HELP-PROMPT: `Answer must be 3-63 characters in length.` DESCRIPTION: `This field holds the name of the service that will perform the Inter- facility Consult at the remote facility.`
.132	REMOTE REQUESTOR PHONE	13;2	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>20!($L(X)<1) X` LAST EDITED: `DEC 20, 2001` HELP-PROMPT: `Answer must be 1-20 characters in length` DESCRIPTION: `This field will contain the telephone number of the remote requestor of an inter-facility consult. This will be displayed with the consult and can expedite communication between requesting provider and consultant.` `This field is derived from the OFFICE PHONE field of the NEW PERSON file.`
.133	REMOTE REQUESTOR DIG PAGER	13;3	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>20!($L(X)<1) X` LAST EDITED: `DEC 20, 2001` HELP-PROMPT: `Answer must be 1-20 characters in length` DESCRIPTION: `This field contains the digital pager number of a remote requesting provider if this is an inter-facility consult. This may expedite communication between the requesting provider and the consultant.` `This data in this field is derived from the DIGITAL PAGER field of the NEW PERSON file.`
1	TO SERVICE	0;5	POINTER TO REQUEST SERVICES FILE (#123.5)	**********************REQUIRED FIELD********************** REQUEST SERVICES(#123.5) LAST EDITED: `FEB 06, 2008` HELP-PROMPT: `Enter the name of the service that will complete the consult.` DESCRIPTION: `This is the "TO" service/specialty. This service is responsible for completion of the consult/request.` CROSS-REFERENCE: `123^C` `1)= S ^GMR(123,"C",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"C",$E(X,1,30),DA)` `This cross reference allows searching for all consults/requests by specific service/specialty.` CROSS-REFERENCE: `^^TRIGGER^123^70` `1)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(1)=$S($D(^GMR(123,D0,70)):^(70),1:"") S X=$P(Y(1),U,1),X=X S DIU=X K Y X ^DD(123,1,1,2,1.1) S DIH=$G(^GMR(123,DIV(0),70)),DIV=X S $P(^(70),U,1)=DIV,DIH=123,DIG=70 D ^DICR` `1.1)= S X=DIV X ^DD(123,1,1,2,49.2) S X=$P($P(Y(102),$C(59)_$P(Y(101),U,1)_":",2),$C(59)) S D0=I(0,0)` `2)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(1)=$S($D(^GMR(123,D0,70)):^(70),1:"") S X=$P(Y(1),U,1),X=X S DIU=X K Y X ^DD(123,1,1,2,2.1) S DIH=$G(^GMR(123,DIV(0),70)),DIV=X S $P(^(70),U,1)=DIV,DIH=123,DIG=70 D ^DICR` `2.1)= S X=DIV X ^DD(123,1,1,2,59.2) S Y(101)=$S($D(^GMR(123.5,D0,30)):^(30),1:"") S X=$P($P(Y(102),$C(59)_$P(Y(101),U,1)_":",2),$C(59)) S D0=I(0,0)` `49.2)= S I(0,0)=$G(D0),D0=DIV S:'D0!'$D(^GMR(123.5,+D0,0)) D0=-1 S Y(102)=$C(59)_$P($G(^DD(123.5,150,0)),U,3),Y(101)=$S($D(^GMR(123.5,D0,30)):^(30),1:"")` `59.2)= S I(0,0)=$G(D0),Y(1)=$S($D(^GMR(123,D0,0)):^(0),1:""),D0=$P(Y(1),U,5) S:'D0!'$D(^GMR(123.5,+D0,0)) D0=-1 S Y(102)=$C(59)_$P($G(^DD(123.5,150,0)),U,3)` `CREATE VALUE)= TO SERVICE:ADMIN` `DELETE VALUE)= TO SERVICE:ADMIN` `FIELD)= ADMIN` `Whenever the TO SERVICE field is updated, this trigger will set the ADMINISTRATIVE field of the REQUEST/CONSULTATION file (#123) to the value of the ADMINISTRATIVE field in the REQUEST SERVICES file (#123.5). Requests` `marked as administrative shall be excluded from the Consults Performance Monitor report [GMRC RPT PERF MONITOR]` RECORD INDEXES: `AE (#81)`
1.01	CLINICAL PROCEDURE	1;1	POINTER TO CP DEFINITION FILE (#702.01)	CP DEFINITION(#702.01) LAST EDITED: `OCT 08, 2001` HELP-PROMPT: `Enter a CP DEFINITION` DESCRIPTION: `This field contains the CP DEFINITION that is associated with this request.` RECORD INDEXES: `ACP (#102)`
2	FROM	0;6	POINTER TO HOSPITAL LOCATION FILE (#44)	HOSPITAL LOCATION(#44) LAST EDITED: `JUL 12, 1998` HELP-PROMPT: `Enter the hospital location that is sending the order.` DESCRIPTION: `This field represents the location that sent the order to the receiving location.` CROSS-REFERENCE: `123^H` `1)= S ^GMR(123,"H",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"H",$E(X,1,30),DA)` `This cross-reference allows the location that sent the consult to track what happened to their consults.`
3	DATE OF REQUEST	0;7	DATE	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `S %DT="ESTX" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `FEB 18, 1992` HELP-PROMPT: `Enter the date/time this order was released from CPRS.` DESCRIPTION: `This is the date and time the order was released from OE/RR. If the TO service entered the order stub through the Add Order (AD) action, this is the service-specified request date.` CROSS-REFERENCE: `123^AD1^MUMPS` `1)= I $P(^GMR(123,DA,0),"^",2) S ^GMR(123,"AD",$P(^GMR(123,DA,0),"^",2),9999999-X,DA)=""` `2)= I $P(^GMR(123,DA,0),"^",2) K ^GMR(123,"AD",$P(^GMR(123,DA,0),"^",2),9999999-X,DA)` `This cross-reference provides consults by patient by inverted order date.` CROSS-REFERENCE: `123^E` `1)= S ^GMR(123,"E",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"E",$E(X,1,30),DA)` `This cross reference allows searching for consults based on Date of Request.` RECORD INDEXES: `AE (#81)`
4	PROCEDURE/REQUEST TYPE	0;8	VARIABLE POINTER	PROTOCOL(#101) GMRC PROCEDURE(#123.3) LAST EDITED: `OCT 15, 2001` HELP-PROMPT: `Enter the type of procedure being requested (e.g., EKG, UGI, etc.).` DESCRIPTION: `This is the procedure that was requested via CPRS while ordering.` CROSS-REFERENCE: `123^AP` `1)= S ^GMR(123,"AP",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"AP",$E(X,1,30),DA)`
5	URGENCY	0;9	POINTER TO PROTOCOL FILE (#101)	PROTOCOL(#101) LAST EDITED: `JUL 09, 1997` HELP-PROMPT: `Enter the urgency for this order (STAT, ROUTINE, NEXT AVAILABLE, EMERGENCY, TODAY, WITHIN 24 HOURS, WITHIN 48 HOURS, WITHIN 72 HOURS, etc.)` DESCRIPTION: `This field describes the urgency of the consult. Urgencies are sent in the PROTOCOL File (#101) as: STAT, EMERGENCY, INPATIENT, NEXT AVAILABLE, NOW, ROUTINE, TODAY, WITHIN 24 HOURS, WITHIN 48 HOURS, WITHIN 72 HOURS, WITHIN` `1 WEEK, WITHIN 1 MONTH.`
6	PLACE OF CONSULTATION	0;10	POINTER TO PROTOCOL FILE (#101)	PROTOCOL(#101) LAST EDITED: `JUN 11, 1997` HELP-PROMPT: `Type The Place Of Consultation: Bedside, Consultant's Choice, On Call, Emergency Room, EKG Lab.` DESCRIPTION: `This is the place where the consultation will take place. Choose from:` `B - Bedside` `C - Consultant's Choice` `E - Emergency Room` `O - On Call` `EKG - EKG Lab`
7	ATTENTION	0;11	POINTER TO NEW PERSON FILE (#200)	NEW PERSON(#200) LAST EDITED: `JUN 05, 1991` HELP-PROMPT: `Enter the name of the Consult Service provider to be alerted about the consult.` DESCRIPTION: `Enter the name of a person you would like to alert about the consult. This person will be sent a notification that a new consult exists. In order for the person to see this type of notification, the person must be set up` `to receive "New service consult" notifications.`
8	CPRS STATUS	0;12	POINTER TO ORDER STATUS FILE (#100.01)	ORDER STATUS(#100.01) INPUT TRANSFORM: `S DIC("S")="I '$$SCREEN^XTID(100.01,,Y_"","")" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X` LAST EDITED: `MAY 03, 2006` HELP-PROMPT: `Enter the CPRS STATUS of this consult (e.g., pending, active, complete, etc.).` DESCRIPTION: `This is the current CPRS status of the consult or request order. The Action Types which may be taken from the "Select Action: " prompt update the status in this file as well as in the Orders File (100).` SCREEN: `S DIC("S")="I '$$SCREEN^XTID(100.01,,Y_"","")"` EXPLANATION: `Data Standardization of Order Status (#100.01) file.` CROSS-REFERENCE: `123^D` `1)= S ^GMR(123,"D",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"D",$E(X,1,30),DA)` `This cross-reference allows searching based on the OE/RR status.` CROSS-REFERENCE: `123^AF^MUMPS` `1)= I "^5^6^"[(U_X_U) N B,C,D I $D(^SC("AWAS1",DA)) S B=$O(^SC("AWAS1",DA,0)),C=$O(^SC("AWAS1",DA,B,0)),D=$O(^SC("AWAS1",DA,B,C,0)) S $P(^SC(B,"S",C,1,D,"CONS"),U)="" K ^SC("AWAS1",DA)` `2)= Q` `This x-ref removes the consult link to an appointment, if one exists, when this field has a status change to Pending (5) or Active (6).` RECORD INDEXES: `AE (#81)`
9	LAST ACTION TAKEN	0;13	POINTER TO REQUEST ACTION TYPES FILE (#123.1)	REQUEST ACTION TYPES(#123.1) LAST EDITED: `DEC 06, 1991` HELP-PROMPT: `Enter the last action taken on the consult (From file 123.1).` DESCRIPTION: `This is the last Action Type taken that updated the activity tracking audit trail.`
10	SENDING PROVIDER	0;14	POINTER TO NEW PERSON FILE (#200)	NEW PERSON(#200) LAST EDITED: `DEC 12, 2001` HELP-PROMPT: `Enter the name of the Ordering Provider.` DESCRIPTION: `This is the provider who originated the order.` CROSS-REFERENCE: `123^G` `1)= S ^GMR(123,"G",$E(X,1,30),DA)=""` `2)= K ^GMR(123,"G",$E(X,1,30),DA)` `This index allows look-up of consults by sending provider.`
11	RESULT	0;15	VARIABLE POINTER	ECHO(#691) CARDIAC CATHETERIZATION(#691.1) ELECTROCARDIOGRAM (EKG)(#691.5) HOLTER(#691.6) EXERCISE TOLERANCE TEST(#691.7) ELECTROPHYSIOLOGY (EP)(#691.8) HEMATOLOGY(#694) GENERATOR IMPLANT(#698) V LEAD IMPLANT(#698.1) A LEAD IMPLANT(#698.2) PACEMAKER SURVEILLANCE(#698.3) ENDOSCOPY/CONSULT(#699) PULMONARY FUNCTION TESTS(#700) RHEUMATOLOGY(#701) LAST EDITED: `DEC 06, 1991` HELP-PROMPT: `Enter the record number for the result in the MEDICINE PACKAGE that contains the results for this consult.` DESCRIPTION: `This is a variable pointer used by the GMRC MEDICINE PKG INTERFACE option to associate results in the Medicine Procedure Files with a consult/request order.`
12	MODE OF ENTRY	0;16	SET	'1' FOR SERVICE FORCED ENTRY; LAST EDITED: `APR 25, 1998` HELP-PROMPT: `Enter '1' if this is a service-entered consult.` DESCRIPTION: `When a consult or request is entered by the service, rather than through CPRS order processing, this field will be set to "1" to indicate the Service forced the entry. This forcing means there is no electronic signature` `related to the order.`
13	REQUEST TYPE	0;17	SET	**********************REQUIRED FIELD********************** 'C' FOR Consult; 'P' FOR Procedure; LAST EDITED: `DEC 14, 1999` DESCRIPTION: `This field will indicate whether the order is a consult or procedure request order. Based on this fields value, the Consultation Body Header alters to indicate "Consult Type: " or "Procedure Request: ".`
14	SERVICE RENDERED AS IN OR OUT	0;18	SET	'I' FOR inpatient; 'O' FOR outpatient; LAST EDITED: `SEP 25, 1991` HELP-PROMPT: `Type I if the service is on an inpatient basis, O if outpatient.` DESCRIPTION: `This field allows the ordering person to indicate if the service is to be rendered on an outpatient or inpatient basis. This is to alleviate the confusion if patient is currently an inpatient/outpatient but is just about` `to be discharged/admitted and become a outpatient/inpatient.`
15	SIGNIFICANT FINDINGS	0;19	SET	'Y' FOR yes; 'N' FOR no; 'U' FOR unknown; LAST EDITED: `APR 23, 1998` HELP-PROMPT: `Enter a value to indicate if significant findings are in the results.` DESCRIPTION: `If significant findings are noted in the consult results, then this field may be marked "Yes", and appropriate comments may be entered in the "Comment" field. "Unknown" is the default. "No" may also be specified to` `indicate the results do not include significant findings.`
16	TIU RESULT NARRATIVE	0;20	POINTER TO TIU DOCUMENT FILE (#8925)	TIU DOCUMENT(#8925) LAST EDITED: `MAY 14, 1996` HELP-PROMPT: `Enter the File 8925 internal entry number where the TIU narrative for this consult is stored.` DESCRIPTION: `Pointer to the Text Integration Utilities file (#8925) where consult/request results narrative is stored.`
17	CLINICALLY INDICATED DATE	0;24	DATE	INPUT TRANSFORM: `S %DT="E" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `FEB 25, 2015` HELP-PROMPT: `Enter the clinically indicated date for consultation.` DESCRIPTION: `The Clinically Indicated Date (CID) is entered by a provider ordering a consult and should be the date by which it is clinically appropriate to complete the consult. This date is used by the Consults Performance Monitor` `Report to help determine the wait times for specialty care.` `This field was formerly named EARLIEST DATE, and was commonly referred to as "Earliest Appropriate Date". It was introduced with GMRC3.066 as part of CPRS GUI v28 (OR3280). The new name was introduced via GMRC3.081` `as part of CPRS GUI v30.B (OR3350).`
20	REASON FOR REQUEST	20;0	WORD-PROCESSING #123.01	DESCRIPTION: `This is the reason for requesting the Consult or Procedure Request.`
30	PROVISIONAL DIAGNOSIS	30;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>245!($L(X)<2) X` LAST EDITED: `JUL 10, 2012` HELP-PROMPT: `Enter a Provisional Diagnosis, 2 to 245 characters in length.` DESCRIPTION: `This is the Provisional Diagnosis the ordering clinician would specify on the Consult Form 513.`
30.1	PROVISIONAL DIAGNOSIS CODE	30.1;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>20!($L(X)<2) X` LAST EDITED: `FEB 21, 2012` HELP-PROMPT: `Answer must be 2-20 characters in length` DESCRIPTION: `This field is used to store the coded portion of the Provisional Diagnosis if a coded diagnosis is sent via CPRS.`
30.2	PROVISIONAL DIAGNOSIS DATE	30.1;2	DATE	INPUT TRANSFORM: `S %DT="E" D ^%DT S X=Y K:X<1 X` LAST EDITED: `FEB 21, 2012` HELP-PROMPT: `(No range limit on date)` DESCRIPTION: `This is the date of the provisional diagnosis and will contain a value if the request is filed with a coded diagnosis. This field is used internally to help identify if a given code is active.`
30.3	PROVISIONAL DIAGNOSIS SYSTEM	30.1;3	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>3!($L(X)<1) X` LAST EDITED: `MAR 29, 2012` HELP-PROMPT: `Answer must be 1-3 characters in length.` DESCRIPTION: `This is the 3-character Source Abbreviation (SAB) for the coding system to which a given diagnosis code belongs. This field will only contain a value when a given service is configured to receive a coded diagnosis. This` `field is used internally to check if a given code is active. For example, ICD is stored if the coding system is ICD-9. 10D is stored if the coding system is ICD-10.`
40	REQUEST PROCESSING ACTIVITY	40;0	DATE Multiple #123.02	123.02 LAST EDITED: `JUN 19, 2002` DESCRIPTION: `Maintains history of processing actions.` INDEXED BY: `ACTIVITY & REMOTE DATE/TIME OF FILING & DATE/TIME OF ACTUAL ACTIVITY (AC)`
50	ASSOCIATED RESULTS	50;0	VARIABLE POINTER Multiple #123.03	123.03
51	REMOTE RESULTS	51;0	DATE Multiple #123.051	123.051 LAST EDITED: `JUL 30, 2001` INDEXED BY: `REMOTE ASSOCIATED RESULT & RESULTING SITE (AR)`
70	ADMINISTRATIVE	70;1	SET	'0' FOR NO; '1' FOR YES; LAST EDITED: `FEB 08, 2008` HELP-PROMPT: `Field is set via a Trigger on TO SERVICE` DESCRIPTION: `This field is set via a trigger on TO SERVICE which will set this field to the value found in the ADMINISTRATIVE field of the REQUEST SERVICES file (#123.5). Requests marked as administrative shall be excluded from the` `Consults Performance Monitor report [GMRC RPT PERF MONITOR]` `WRITE AUTHORITY: ^` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` `TRIGGERED by the TO SERVICE field of the REQUEST/CONSULTATION File`
80	UNIQUE CONSULT ID	UCID;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>15!($L(X)<1) X` `MAXIMUM LENGTH: 15` LAST EDITED: `DEC 15, 2017` HELP-PROMPT: `Answer must be 1-15 characters in length.` DESCRIPTION: `A Unique Consult record identifier across all VistA systems.` TECHNICAL DESCR: `The UCID value is created from the value in the GMRC UNIQUE CONSULT SITE ID entry in the PARAMETER file for this site concatenated with the IEN of this record. This field is populated when a record is created and should` `not be modified.`
81	DIVISION ID OF ENTERING PERSON	5;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>10!($L(X)<3) X` `MAXIMUM LENGTH: 10` LAST EDITED: `APR 14, 2020` HELP-PROMPT: `Answer must be 3-10 characters in length.` DESCRIPTION: `This field is populated the Community Care Referrals and Authorization process when the consult is first sent to the HealthShare Referral Management system. This field stores the division id of the user entering the` `consult.`

Name	Field # of Occurrence
^%DT	.01+1, 3+1, 17+1, 30.2+1
^DIC	8+1
^DICR	1(XREF 2S), 1(XREF 2K)
Y^DIQ	ID.02+1

Name	Line Occurrences (* Changed, ! Killed)
^DD(123	1(XREF 2S), 1(XREF 2n1.1), 1(XREF 2K), 1(XREF 2n2.1)
^DD(123.5	1(XREF 2n49.2), 1(XREF 2n59.2)
^DD(2	ID.02+1
^DPT - [#2]	ID.02+1
^GMR(123 - [#123]	.01(XREF 1S), .01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .02(XREF 3S), .02(XREF 3K), .03(XREF 1S), .03(XREF 1K), .04(XREF 1S), .04(XREF 1K) , .126(XREF 1S), .126(XREF 1K), 1(XREF 1S), 1(XREF 1K), 1(XREF 2S), 1(XREF 2K), 1(XREF 2n59.2), 2(XREF 1S), 2(XREF 1K), 3(XREF 2S) , 3(XREF 2K), 3(XREF 3S), 3(XREF 3K), 4(XREF 1S), 4(XREF 1K), 8(XREF 1S), 8(XREF 1K), 10(XREF 1S), 10(XREF 1K)
^GMR(123.5 - [#123.5]	1(XREF 2n2.1), 1(XREF 2n49.2), 1(XREF 2n59.2)
^SC - [#44]	8(XREF 2S)
^SC("AWAS1"	8(XREF 2S)

>>	Not killed explicitly
*	Changed
!	Killed
~	Newed

Name	Field # of Occurrence
>> %DT	.01+1, 3+1, 17+1, 30.2+1
%I	ID.02+1*!
B	8(XREF 2S)
C	ID.02+1*, 8(XREF 2S)
D	8(XREF 2S)
>> D0	1(XREF 2S), 1(XREF 2n1.1), 1(XREF 2K), 1(XREF 2n2.1), 1(XREF 2n49.2), 1(XREF 2n59.2)
>> DA	.01(XREF 1S), .01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .02(XREF 3S), .02(XREF 3K), .03(XREF 1S), .03(XREF 1K), .04(XREF 1S), .04(XREF 1K) , .126(XREF 1S), .126(XREF 1K), 1(XREF 1S), 1(XREF 1K), 1(XREF 2S), 1(XREF 2K), 2(XREF 1S), 2(XREF 1K), 3(XREF 2S), 3(XREF 2K) , 3(XREF 3S), 3(XREF 3K), 4(XREF 1S), 4(XREF 1K), 8(XREF 1S), 8(XREF 1K), 8(XREF 2S), 10(XREF 1S), 10(XREF 1K)
DIC	ID.02+1, 8+1!*
DIC("S"	8+1, 8SCR+1
>> DIE	8+1
>> DIG	1(XREF 2S), 1(XREF 2K)
>> DIH	1(XREF 2S), 1(XREF 2K)
>> DIU	1(XREF 2S), 1(XREF 2K)
DIV	1(XREF 2S), 1(XREF 2n1.1), 1(XREF 2K), 1(XREF 2n2.1), 1(XREF 2n49.2)
DIV(0	1(XREF 2S), 1(XREF 2K)
GMRCD	.02(XREF 1S), .02(XREF 1K)
>> I(0	1(XREF 2n1.1), 1(XREF 2n2.1), 1(XREF 2n49.2), 1(XREF 2n59.2)
U	ID.02+1, 1(XREF 2S), 1(XREF 2n1.1), 1(XREF 2K), 1(XREF 2n2.1), 1(XREF 2n49.2), 1(XREF 2n59.2), 8(XREF 2S)
X	.001+1!, .01+1!, .01(XREF 1S), .01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .02(XREF 3S), .02(XREF 3K), .03(XREF 1S), .03(XREF 1K) , .04(XREF 1S), .04(XREF 1K), .06+1!, .1+1!, .126+1!, .126(XREF 1S), .126(XREF 1K), .131+1!, .132+1!, .133+1! , 1(XREF 1S), 1(XREF 1K), 1(XREF 2S), 1(XREF 2n1.1), 1(XREF 2K), 1(XREF 2n2.1), 2(XREF 1S), 2(XREF 1K), 3+1!, 3(XREF 2S) , 3(XREF 2K), 3(XREF 3S), 3(XREF 3K), 4(XREF 1S), 4(XREF 1K), 8+1!, 8(XREF 1S), 8(XREF 1K), 8(XREF 2S), 10(XREF 1S) , 10(XREF 1K), 17+1!, 30+1!, 30.1+1!, 30.2+1*!, 30.3+1!, 80+1!, 81+1!
Y	ID.02+1, .01+1, 1(XREF 2S), 1(XREF 2K), 3+1, 8+1, 17+1, 30.2+1
Y(1	1(XREF 2S), 1(XREF 2K), 1(XREF 2n59.2)
Y(101	1(XREF 2n1.1), 1(XREF 2n2.1), 1(XREF 2n49.2)
Y(102	1(XREF 2n1.1), 1(XREF 2n2.1), 1(XREF 2n49.2), 1(XREF 2n59.2)

Customize PDF page

Package: Consult Request Tracking

Global: ^GMR(123

Information

Description

Directly Accessed By Routines, Total: 168

Accessed By FileMan Db Calls, Total: 114

Pointed To By FileMan Files, Total: 23

Pointer To FileMan Files, Total: 28

Fields, Total: 43

External References

Global Variables Directly Accessed

Naked Globals

Local Variables

Legend:

Name	Field # of Occurrence
^(0	ID.02+1, 1(XREF 2n59.2)
^(30	1(XREF 2n2.1), 1(XREF 2n49.2)
^(70	1(XREF 2S), 1(XREF 2K)