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 | Fields | Found Entries | All

Print Page as PDF

Global: ^ORD(100.02

Package: Order Entry Results Reporting

Global: ^ORD(100.02

Information

FileMan FileNo	FileMan Filename	Package
100.02	NATURE OF ORDER	Order Entry Results Reporting

Description

This file should not be added to or deleted from. It determines the actions that are to be taken based on the nature of an order or change to an order. Per VHA Directive 2005-044, this file has been "locked down" by Data Standardization (DS). The file definition (i.e. data dictionary) shall not be modified. All additions, changes and deletions to entries in the file shall be done by Enterprise Reference Terminology (ERT) using the Master File Server (MFS), provided by Common Services (CS). Creating and/or editing locally defined fields in the file are not permitted. Use of locally defined fields that were created prior to VHA Directive 2005-044 shall not be supported. The Orders Domain has approved editing of the following fields in this file: - PRINT CHART COPY (#.12) - PRINT DAILY SUMMARY (#.13) - PRINT WORK COPY (#.15) - INCLUDE IN ACTIVE ORDERS (#.16) This may be accomplished via the option "Print Parameters for Nature of Order" [ORCL NATURE], on the "Print/Report Parameters" [OR PARAM PRINTS] menu.

Directly Accessed By Routines, Total: 43

Package	Total	Routines
Order Entry Results Reporting	39	OR3C100 ORCACT0 ORCACT2 ORCSAVE ORCSAVE2 ORCSEND ORCSEND1 ORCSEND3 ORCSIGN OREVNT1 ORMBLD ORMBLDPS ORMEVNT1 ORMEVNT2 ORMFH ORMGMRC ORMLR ORMPS ORMRA ORPR07 ORPRPM1 ORPRS02 ORPRS04 ORPRS10 ORQ11 ORQ20 ORWD1 ORWD2 ORWDPS5 ORWDX2 ORWDXA ORWDXR ORWOR1 ORX1 ORY141ED ORY242 ORY56 ORY7 ORY92
IHS Laboratory Point of Care	1	BLRPOC
IHS Mods To Text Integration Utilities	1	BTIULO12
Lab Service	1	LROR6
Patient Care Component Table Maintiance	1	APCM11E2

Accessed By FileMan Db Calls, Total: 2

Package	Total	Routines
Order Entry Results Reporting	1	ORX1
Outpatient Pharmacy	1	PSONEW

Pointed To By FileMan Files, Total: 4

Package	Total	FileMan Files
Order Entry Results Reporting	2	ORDER(#100)[61, #100.008(12)] ORDER REASON(#100.03)[.07]
IHS Changes To Pharmacy	1	APSP CONTROL(#9009033)[407]
Lab Service	1	LABORATORY SITE(#69.9)[150.1]

Fields, Total: 16

Field #	Name	Loc	Type	Details
.001	NUMBER		NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>9999)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `DEC 10, 1996` HELP-PROMPT: `Type a Number between 1 and 9999, 0 Decimal Digits` WRITE AUTHORITY: ^
.01	NAME	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>30!(X?.N)!($L(X)<3)!'(X'?1P.E) X` HELP-PROMPT: `NAME MUST BE 3-30 CHARACTERS, NOT NUMERIC OR STARTING WITH PUNCTUATION` DESCRIPTION: This is the name of the Nature of Order. PRE-LOOKUP: `I $G(DIC(0))["L",'$D(XUMF) K X D EN^DDIOL("Entries must be edited via the Master File Server (MFS).","","!?5,$C(7)")` DELETE TEST: `1,0)= D:'$D(XUMF) EN^DDIOL("Entries must be inactivated via the Master File Server (MFS).","","!?5,$C(7)") I $D(XUMF)` LAYGO TEST: `1,0)= D:'$D(XUMF) EN^DDIOL("Entries must be added via the Master File Server (MFS).","","!?5,$C(7)") I $D(XUMF)` WRITE AUTHORITY: ^ CROSS-REFERENCE: `100.02^B` 1)= S ^ORD(100.02,"B",$E(X,1,30),DA)="" 2)= K ^ORD(100.02,"B",$E(X,1,30),DA)
.02	CODE	0;2	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>3!($L(X)<1) X` LAST EDITED: `DEC 18, 1996` HELP-PROMPT: `Answer must be 1-3 characters in length.` DESCRIPTION: This is a single character abbreviation that is used in HL7 messages between CPRS and the ancillary packages. WRITE AUTHORITY: ^ CROSS-REFERENCE: `100.02^C` 1)= S ^ORD(100.02,"C",$E(X,1,30),DA)="" 2)= K ^ORD(100.02,"C",$E(X,1,30),DA)
.03	NON-INTERACTIVE	0;3	SET	'0' FOR INTERACTIVE; '1' FOR NON-INTERACTIVE; LAST EDITED: `DEC 11, 1996` DESCRIPTION: This field identifies this entry for interactive or non-interactive use. WRITE AUTHORITY: ^ CROSS-REFERENCE: `100.02^AC` 1)= S ^ORD(100.02,"AC",$E(X,1,30),DA)="" 2)= K ^ORD(100.02,"AC",$E(X,1,30),DA)
.04	INACTIVE	0;4	SET	'0' FOR ACTIVE; '1' FOR INACTIVE; LAST EDITED: `DEC 10, 1996` DESCRIPTION: This field is used to inactivate a nature of order. WRITE AUTHORITY: ^
.05	FRONT/BACKDOOR	0;5	SET	'F' FOR frontdoor; 'B' FOR backdoor; 'X' FOR both; LAST EDITED: `DEC 11, 1996` DESCRIPTION: This field is used to identify entries that are used during an OE/RR dialog (frontdoor), and entries that are used by ancillary services (backdoor). WRITE AUTHORITY: ^
.06	DC ONLY	0;6	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `JAN 08, 1997` HELP-PROMPT: `Enter YES if this entry is only used for DC actions.` DESCRIPTION: This is a flag that determines if this nature is to be used only when discontinuing an order. WRITE AUTHORITY: ^
.11	CREATE ACTION	1;1	SET	'0' FOR NO; '1' FOR YES; LAST EDITED: `FEB 28, 1997` HELP-PROMPT: `Enter YES if an order action should be created and signed, or NO to simply update the status of this order` DESCRIPTION: This field determines if an entry will be created in the Order Action multiple for this order; if not, then only a status update will occur. WRITE AUTHORITY: ^
.12	PRINT CHART COPY	1;2	SET	'0' FOR NO; '1' FOR YES; LAST EDITED: `DEC 10, 1996` DESCRIPTION: This field determines if this entry/action should generate a Chart copy. WRITE AUTHORITY: ^
.13	PRINT DAILY SUMMARY	1;3	SET	'0' FOR NO; '1' FOR YES; LAST EDITED: `DEC 10, 1996` DESCRIPTION: This field determines if this entry/action should appear on the Daily Order Summary. WRITE AUTHORITY: ^
.14	DEFAULT SIGNATURE STATUS	1;4	SET	'0' FOR ON CHART w/written orders; '1' FOR ELECTRONIC; '2' FOR NOT SIGNED; '3' FOR NOT REQUIRED; '4' FOR ON CHART w/printed orders; '5' FOR NOT REQUIRED due to cancel; '6' FOR SERVICE CORRECTION to signed order; LAST EDITED: `FEB 28, 1997` HELP-PROMPT: `Enter the signature status to be assigned for this nature of order` DESCRIPTION: This is the signature status that will be assigned to an order having this nature; if a signature is not applicable, this field should be null. WRITE AUTHORITY: ^
.15	PRINT WORK COPY	1;5	SET	'0' FOR NO; '1' FOR YES; LAST EDITED: `JAN 22, 1997` DESCRIPTION: This field determines if this entry/action should generate a Work Copy. WRITE AUTHORITY: ^
.16	INCLUDE IN ACTIVE ORDERS	1;6	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `JUL 12, 2000` HELP-PROMPT: `Enter YES if an order dc'd with this nature should appear in the Active Orders list.` DESCRIPTION: This determines if orders dc'd with this nature are included in the Active Orders list; if so, they will be shown for the number of hours specified by the Active Orders Context Hours parameter, as with other dc'd orders. WRITE AUTHORITY: ^
99.98	MASTER ENTRY FOR VUID	VUID;2	SET	**********************REQUIRED FIELD********************** '1' FOR YES; '0' FOR NO; LAST EDITED: `NOV 18, 2005` DESCRIPTION: This field identifies the Master entry for a VUID associated with a Term/Concept. WRITE AUTHORITY: ^ UNEDITABLE RECORD INDEXES: `AMASTERVUID (#464)`
99.99	VUID	VUID;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `S X=+X K:$L(X)>20!($L(X)<1)!'(X?1.20N) X` LAST EDITED: `NOV 18, 2005` HELP-PROMPT: `Answer must be 1-20 digits in length.` DESCRIPTION: VHA Unique ID (VUID). A unique meaningless integer assigned to reference terms VHA wide. WRITE AUTHORITY: ^ UNEDITABLE NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` CROSS-REFERENCE: `100.02^AVUID` 1)= S ^ORD(100.02,"AVUID",$E(X,1,30),DA)="" 2)= K ^ORD(100.02,"AVUID",$E(X,1,30),DA) This cross-reference is by VUID. RECORD INDEXES: `AMASTERVUID (#464)`
99.991	EFFECTIVE DATE/TIME	TERMSTATUS;0	DATE Multiple #100.0299	100.0299 DESCRIPTION: Describes the pair Status and Effective Date/Time for each reference term.

Found Entries, Total: 12

NAME: AUTO	NAME: CHANGED	NAME: DUPLICATE	NAME: ELECTRONICALLY ENTERED	NAME: MAINTENANCE	NAME: POLICY	NAME: REJECTED	NAME: SERVICE CORRECTION
NAME: SERVICE REJECT	NAME: TELEPHONED	NAME: VERBAL	NAME: WRITTEN

Info | Desc | Directly Accessed By Routines | Accessed By FileMan Db Calls | Pointed To By FileMan Files | Fields | Found Entries | All