STANDARD DATA DICTIONARY #80.1 -- ICD OPERATION/PROCEDURE FILE 3/24/25 PAGE 1
STORED IN ^ICD0( (86606 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 18.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
ICD Operations/Procedure file #80.1 contains codes from the International Classification of Diseases (ICD) Procedure Coding System
(PCS) provided by the Centers for Medicare and Medicaid Services (CMS) and the National Center for Health Statistics (NCHS). This
file contains both the 9th (ICD-9-PCS) and 10th (ICD-10-PCS) Revisions.
If an entry needs to be added, modified or deleted, a patch will be issued containing the change.
This table file should NOT be edited in anyway by the site.
SPECIAL LOOKUP ROUTINE : ICDEXLK
DD ACCESS: @
RD ACCESS: d
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS:
APPLICATION GROUP(S): PXRS, QAM
IDENTIFIED BY: CODING SYSTEM (#1.1)
POINTED TO BY: ICD OR CPT CODE field (#3) of the CATASTROPHIC DISABILITY REASONS File (#27.17)
PROCEDURE 1 field (#45.01) of the PTF File (#45)
PROCEDURE 2 field (#45.02) of the PTF File (#45)
PROCEDURE 3 field (#45.03) of the PTF File (#45)
PROCEDURE 4 field (#45.04) of the PTF File (#45)
PROCEDURE 5 field (#45.05) of the PTF File (#45)
OPERATION CODE 1 field (#8) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 2 field (#9) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 3 field (#10) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 4 field (#11) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 5 field (#12) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 6 field (#13) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 7 field (#14) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 8 field (#15) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 9 field (#16) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 10 field (#17) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 11 field (#18) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 12 field (#19) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 13 field (#20) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 14 field (#21) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 15 field (#22) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 16 field (#23) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 17 field (#24) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 18 field (#25) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 19 field (#26) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 20 field (#27) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 21 field (#28) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 22 field (#29) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 23 field (#30) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 24 field (#31) of the 401 sub-field (#45.01) of the PTF File (#45)
OPERATION CODE 25 field (#32) of the 401 sub-field (#45.01) of the PTF File (#45)
PROCEDURE CODE 1 field (#4) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 2 field (#5) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 3 field (#6) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 4 field (#7) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 5 field (#8) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 6 field (#9) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 7 field (#10) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 8 field (#11) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 9 field (#12) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 10 field (#13) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 11 field (#14) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 12 field (#15) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 13 field (#16) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 14 field (#17) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 15 field (#18) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 16 field (#19) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 17 field (#20) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 18 field (#21) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 19 field (#22) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 20 field (#23) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 21 field (#24) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 22 field (#25) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 23 field (#26) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 24 field (#27) of the 601 sub-field (#45.05) of the PTF File (#45)
PROCEDURE CODE 25 field (#28) of the 601 sub-field (#45.05) of the PTF File (#45)
DIAGNOSIS/PROCEDURE CODE field (#.02) of the PTF EXPANDED CODE File (#45.89)
PROCEDURE CODES field (#.01) of the PROCEDURE CODES sub-field (#80.63) of the DRG HAC File (#80.6)
ONE OF field (#.01) of the ONE OF sub-field (#82.1111) of the BLOCK sub-field (#82.111) of the DRG PROCEDURE CODE
COMBINATIONS File (#82.11)
WITH ONE OF 1 field (#.01) of the WITH ONE OF 1 sub-field (#82.1112) of the BLOCK sub-field (#82.111) of the DRG
PROCEDURE CODE COMBINATIONS File (#82.11)
WITH ONE OF 2 field (#.01) of the WITH ONE OF 2 sub-field (#82.1113) of the BLOCK sub-field (#82.111) of the DRG
PROCEDURE CODE COMBINATIONS File (#82.11)
WITH ONE OF 3 field (#.01) of the WITH ONE OF 3 sub-field (#82.1114) of the BLOCK sub-field (#82.111) of the DRG
PROCEDURE CODE COMBINATIONS File (#82.11)
WITH ONE OF 4 field (#.01) of the WITH ONE OF 4 sub-field (#82.1115) of the BLOCK sub-field (#82.111) of the DRG
PROCEDURE CODE COMBINATIONS File (#82.11)
PROCEDURE field (#.01) of the DRG PROCEDURE File (#83.6)
PROCEDURE field (#.01) of the PROCEDURES sub-field (#83.6102) of the DRG PROCEDURE GROUPS File (#83.61)
PROC1 field (#40) of the FEE BASIS INVOICE File (#162.5)
PROC2 field (#41) of the FEE BASIS INVOICE File (#162.5)
PROC3 field (#42) of the FEE BASIS INVOICE File (#162.5)
PROC4 field (#43) of the FEE BASIS INVOICE File (#162.5)
PROC5 field (#44) of the FEE BASIS INVOICE File (#162.5)
PROC6 field (#44.06) of the FEE BASIS INVOICE File (#162.5)
PROC7 field (#44.07) of the FEE BASIS INVOICE File (#162.5)
PROC8 field (#44.08) of the FEE BASIS INVOICE File (#162.5)
PROC9 field (#44.09) of the FEE BASIS INVOICE File (#162.5)
PROC10 field (#44.1) of the FEE BASIS INVOICE File (#162.5)
PROC11 field (#44.11) of the FEE BASIS INVOICE File (#162.5)
PROC12 field (#44.12) of the FEE BASIS INVOICE File (#162.5)
PROC13 field (#44.13) of the FEE BASIS INVOICE File (#162.5)
PROC14 field (#44.14) of the FEE BASIS INVOICE File (#162.5)
PROC15 field (#44.15) of the FEE BASIS INVOICE File (#162.5)
PROC16 field (#44.16) of the FEE BASIS INVOICE File (#162.5)
PROC17 field (#44.17) of the FEE BASIS INVOICE File (#162.5)
PROC18 field (#44.18) of the FEE BASIS INVOICE File (#162.5)
PROC19 field (#44.19) of the FEE BASIS INVOICE File (#162.5)
PROC20 field (#44.2) of the FEE BASIS INVOICE File (#162.5)
PROC21 field (#44.21) of the FEE BASIS INVOICE File (#162.5)
PROC22 field (#44.22) of the FEE BASIS INVOICE File (#162.5)
PROC23 field (#44.23) of the FEE BASIS INVOICE File (#162.5)
PROC24 field (#44.24) of the FEE BASIS INVOICE File (#162.5)
PROC25 field (#44.25) of the FEE BASIS INVOICE File (#162.5)
SURGICAL PROCEDURE CODE field (#10.07) of the HCS REVIEW TRANSMISSION File (#356.22)
PROCEDURE #1 field (#1.02) of the SERVICE LINE sub-field (#356.2216) of the HCS REVIEW TRANSMISSION File (#356.22)
PROCEDURE CODE #2 field (#1.03) of the SERVICE LINE sub-field (#356.2216) of the HCS REVIEW TRANSMISSION File
(#356.22)
PROCEDURE field (#.01) of the INPATIENT PROCEDURE File (#356.91)
*ICD PROCEDURE CODE (1) field (#54) of the BILL/CLAIMS File (#399)
*ICD PROCEDURE CODE (2) field (#55) of the BILL/CLAIMS File (#399)
*ICD PROCEDURE CODE (3) field (#56) of the BILL/CLAIMS File (#399)
PROCEDURES field (#304) of the BILL/CLAIMS File (#399)
PROCEDURES field (#.01) of the PROCEDURES sub-field (#399.0304) of the BILL/CLAIMS File (#399)
CODE field (#.01) of the CODE sub-field (#694.801) of the PROCEDURE TERM File (#694.8)
ICD CODE field (#.09) of the WV PROCEDURE TYPE File (#790.2)
ICD PROCEDURE CODE field (#.01) of the ICD PROCEDURE CODE sub-field (#798.52) of the ROR ICD SEARCH File (#798.5)
ENTRY field (#.02) of the LOCAL KEYWORD File (#8984.1)
ENTRY field (#.02) of the LOCAL SHORTCUT File (#8984.2)
CROSS
REFERENCED BY: CODE NUMBER(ACT1), STATUS EFFECTIVE DATE(ACT2), STATUS(ACT3), CODING SYSTEM(ACT4), DESCRIPTION(AD),
CODING SYSTEM(AD2), WORD(AD3), DESCRIPTION EFFECTIVE DATE(ADS), DESCRIPTION EFFECTIVE DATE(ADSS1),
CODING SYSTEM(ADSS2), OPER/PROCEDURE EFFECTIVE DATE(AST), OPER/PROCEDURE EFFECTIVE DATE(ASTS1),
CODING SYSTEM(ASTS2), DESCRIPTION(D)
INDEXED BY: CODE NUMBER (AB), CODING SYSTEM & CODE NUMBER (ABA), CODE NUMBER (AEXC), CODING SYSTEM & CODE NUMBER (AN), CODE
NUMBER & ICD EXPANDED (AVA), CODE NUMBER (BA)
80.1,.01 CODE NUMBER 0;1 FREE TEXT (Required)
OPERATION/PROCEDURE CODE
INPUT TRANSFORM: K:$L(X)>7!($L(X)<1) X
LAST EDITED: OCT 06, 2011
HELP-PROMPT: Answer must be 1-7 characters in length.
DESCRIPTION:
ICD-9 or ICD-10 procedure code
TECHNICAL DESCR: ICD-9 Procedure Code Pattern Match
1 2 3 4 5
- - - - -
N N . N N
n n
"N" Numeric
"n" Character
ICD-10 Procedure Code Pattern Match
1 2 3 4 5 6 7
- - - - - - -
U U U U U U U
N N N N N N N
Z Z Z Z Z
"U" Uppercase
"Z" N/A or None
"N" Numeric
LAYGO TEST: 1,0)= I 1
CROSS-REFERENCE: 80.1^ACT1^MUMPS
1)= D SAHC^ICDIDX2(80.1)
2)= D KAHC^ICDIDX2(80.1)
^ICD0("ACT",(CODE_" "),STA,EF,IEN1,IEN2) ^ICD0("ACTS",SYS,(CODE_" "),STA,EF,IEN1,IEN2) Where CODE
is the ICD code, STA is either 1 (active) or 0 (inactive), EF is the effective date of the status,
IEN1 is the internal entry number in file #80.1 and IEN2 is the internal entry number of the STATUS
multiple sub-file 80.166 where the status is stored. The subscript SYS is added to the ACTS
cross-reference to create a coding system specific cross-reference.
FIELD INDEX: AB (#1131) REGULAR IR SORTING ONLY
Short Descr: AB Code Cross-Reference
Description: ^ICD0("AB",(CODE_" "),IEN) - Where CODE is the ICD code and IEN is the internal entry number in
file #80.1. Appending a space character to CODE forces the code to be regarded as a string, thus
disallowing the dropping of leading '0's.
Set Logic: S ^ICD0("AB",$E(X,1,30),DA)=""
Set Cond: S X=$S(+($$GET1^DIQ(80.1,(+DA_","),1.8))'>0:1,1:0)
Kill Logic: K ^ICD0("AB",$E(X,1,30),DA)
Whole Kill: K ^ICD0("AB")
X(1): CODE NUMBER (80.1,.01) (Subscr 1) (Len 30) (forwards)
Transform (Storage): S X=(X_" ")
FIELD INDEX: AEXC (#1133) REGULAR IR SORTING ONLY
Short Descr: AEXC Exclusion Cross-Reference for all Coding Systems
Description: ^ICD0("AEXC",(CODE_" "),IEN) - Where CODE is an ICD code and IEN is the internal entry number in
file #80.1 where the code is stored. This cross-reference is used to track those records that were
either entered or edited in error. When a record is either entered or edited in error, it cannot
be deleted because there may be applications pointing to the record. Instead the record is retired
from lookup so future lookups will not find or return the errant record. This is done by leaving
the code and descriptive text in place and removing the activation history. The lookup (either
Fileman or Special Lookup) acts as if the record was never active, thus preventing the users from
accessing the record.
Set Logic: S ^ICD0("AEXC",$E(X,1,30),DA)=""
Set Cond: S X=$S(($O(^ICD0(+DA,66,0))'>0&($O(^ICD0(+DA,68,0))>0)):1,1:0)
Kill Logic: K ^ICD0("AEXC",$E(X,1,30),DA)
Whole Kill: K ^ICD0("AEXC")
X(1): CODE NUMBER (80.1,.01) (Subscr 1) (Len 30) (forwards)
Transform (Storage): S X=(X_" ")
FIELD INDEX: BA (#1136) REGULAR IR LOOKUP & SORTING
Short Descr: BA Cross-Reference for all Coding Systems
Description: ^ICD0("BA",(CODE_" "),IEN) - Where CODE is an ICD code and IEN is the internal entry number in file
#80.1 where the code is stored. Appending a space character to CODE forces the code to be regarded
as a string, thus disallowing the dropping of leading '0's. The BA cross-references is used by
Fileman during unassisted lookups when DIC(0) contains "I"
Set Logic: S ^ICD0("BA",$E(X,1,30),DA)=""
Set Cond: S X=$S(+($$GET1^DIQ(80.1,(+DA_","),1.8))'>0:1,1:0)
Kill Logic: K ^ICD0("BA",$E(X,1,30),DA)
Whole Kill: K ^ICD0("BA")
X(1): CODE NUMBER (80.1,.01) (Subscr 1) (Len 30) (forwards)
Transform (Storage): S X=(X_" ")
RECORD INDEXES: ABA (#1132), AN (#1134), AVA (#1135)
80.1,1.1 CODING SYSTEM 1;1 POINTER TO ICD CODING SYSTEMS FILE (#80.4)
INPUT TRANSFORM: I $P($G(^ICDS(+Y,0)),"^",4)=80.1 D ^DIC K DIC S DIC=$G(DIE),X=+Y K:Y<0 X
LAST EDITED: OCT 05, 2011
HELP-PROMPT: Enter a coding system.
DESCRIPTION:
This is the coding system to which the code belongs.
SCREEN: I $P($G(^ICDS(+Y,0)),"^",4)=80.1
EXPLANATION: The screen limits the coding system to those allowed in file 80.1.
CROSS-REFERENCE: 80.1^ACT4^MUMPS
1)= D SAHCS^ICDIDX2(80.1)
2)= D KAHCS^ICDIDX2(80.1)
^ICD0("ACT",(CODE_" "),STA,EF,IEN1,IEN2) ^ICD0("ACTS",SYS,(CODE_" "),STA,EF,IEN1,IEN2) Where SYS is
the coding system, CODE is the ICD code, STA is either 1 (active) or 0 (inactive), EF is the
effective date of the status, IEN1 is the internal entry number in file #80.1 and IEN2 is the
internal entry number of the STATUS multiple sub-file 80.166 where the status is stored. The
subscript SYS is added to the ACTS cross reference to create a coding system specific
cross-reference.
CROSS-REFERENCE: 80.1^AD2^MUMPS
1)= D SAD2^ICDIDX(80.1)
2)= D KAD2^ICDIDX(80.1)
^ICD0("AD",SYS,WORD,IEN1,DATE,IEN2) - Where SYS is the coding system in file 80.1, WORD is a single
word extracted from the description, IEN1 is the internal entry number in file #80.1 where the
description is stored, DATE is the effective date of the description and IEN2 is the internal entry
number of the DESCRIPTION multiple sub-file #80.168 where the description containing the extracted
word is stored. This is a modification of Fileman KWIC (Key Word In Context) cross-reference.
Like the Fileman KWIC cross-reference, each word in the description is indexed. Unlike the KWIC
cross-reference the index contains the effective date of the description. This is done to allow
date sensitive keyword searches of the Operations/Procedure file.
CROSS-REFERENCE: 80.1^ASTS2^MUMPS
1)= D SASTS2^ICDIDX(80.1)
2)= D KASTS2^ICDIDX(80.1)
^ICD0("ASTS",SYS,(CODE_" "),EFF,IEN1,IEN2) - Where SYS is the coding system, CODE is the ICD
procedure code, EFF is the effective date for the Operation/Procedure (short text), IEN1 is the
internal entry number in the ICD Operation/Procedure file (#80.1) and IEN2 is the internal entry
number in the OPERATION/PROCEDURE multiple (#80.167) where the short text is stored.
CROSS-REFERENCE: 80.1^ADSS2^MUMPS
1)= D SADSS2^ICDIDX(80.1)
2)= D KADSS2^ICDIDX(80.1)
^ICD0("ADSS",SYS,(CODE_" "),EFF,IEN1,IEN2) - Where SYS is the coding system, CODE is the ICD
procedure code, EFF is the effective date for the description (long text), IEN1 is the internal
entry number in the ICD Operation/Procedure file (#80.1) and IEN2 is the internal entry number in
the DESCRIPTION multiple (#80.168) where the long text is stored.
RECORD INDEXES: ABA (#1132), AN (#1134)
80.1,1.2 IDENTIFIER 1;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>10!($L(X)<1) X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter one or more valid codes.
DESCRIPTION:
This field contains Operations Identifiers.
EXECUTABLE HELP: D ^ICDHLPO
80.1,1.5 MDC24 1;5 SET
'1' FOR CRANIAL;
'2' FOR LIMB;
'3' FOR OTHER;
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter procedure type for Multiple Significant Trauma.
DESCRIPTION:
Set of codes refers to body site of procedure, when for a Multiple Significant Trauma (MDC 24)
80.1,1.7 ICD EXPANDED 1;7 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 05, 2011
HELP-PROMPT: Is this ICD code expanded by the VA?
DESCRIPTION:
This field is a flag indicating that the ICD code was expanded by the VA (local code).
RECORD INDEXES: AVA (#1135)
80.1,1.8 EXCLUDE FROM LOOKUP ; COMPUTED
MUMPS CODE: S X=$S((($O(^ICD0(+D0,66,0))'>0)&($O(^ICD0(+D0,68,0))>0))!($P($G(^ICD0(+D0,1)),"^",7)>0):1,1:0)
ALGORITHM: S X=$S((($O(^ICD0(+D0,66,0))'>0)&($O(^ICD0(+D0,68,0))>0))!($P($G(^ICD0(+D0,1)),"^",7)>0):1,1:0)
LAST EDITED: OCT 05, 2011
DESCRIPTION: This is a computed field to indicate if a record in the Operations/Procedure file #80.1 should be
excluded from lookup. Records excluded from lookup either have no activation history (sub-file
80.166) or have been modified by the VA (ICD EXPANDED field 1.7). If this computed field returns a
1, then it should not be used for lookup or included in lookup cross-references.
80.1,10 SEX 3;0 DATE Multiple #80.11
DESCRIPTION: This is a history of the Sex designation (Male/Female) for the procedure and includes the Sex with
the date it became effective.
80.11,.01 SEX EFFECTIVE DATE 0;1 DATE
INPUT TRANSFORM: S %DT="E" D ^%DT S X=Y K:X<1 X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter the date the Sex designation became effective.
DESCRIPTION:
This is the date that the Sex designation became effective.
CROSS-REFERENCE: 80.11^B
1)= S ^ICD0(DA(1),3,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(1),3,"B",$E(X,1,30),DA)
^ICD0(IEN1,3,"B",EFF,IEN2) - Where IEN1 is the internal entry number in the ICD Procedure file
#80.1, EFF is the effective date for the Sex designation and IEN2 is the internal entry number in
the SEX multiple where the Sex designation is stored.
80.11,1 SEX 0;2 SET
'M' FOR MALE;
'F' FOR FEMALE;
'N' FOR NOT APPLICABLE;
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter the sex designation of the procedure.
DESCRIPTION:
This is the sex designation for this procedure.
80.1,20 MAJOR O.R. PROC M;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>10!($L(X)<1) X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter one or more Major O.R. Procedures.
DESCRIPTION: This is the Major O.R procedure for this procedure code. See routine D MAJ^ICDHLPD for a listing
of acceptable values for this field.
EXECUTABLE HELP: D MAJ^ICDHLPD
80.1,66 STATUS 66;0 DATE Multiple #80.166 (Add New Entry without Asking)
LAST EDITED: SEP 15, 2011
DESCRIPTION: This multiple contains versioned information for an ICD code. A new entry is created whenever an
ICD code's status is changed.
80.166,.01 STATUS EFFECTIVE DATE 0;1 DATE (Required)
INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:X<1 X
LAST EDITED: OCT 05, 2011
HELP-PROMPT: Enter the Status Effective date.
DESCRIPTION:
This is the effective date of the status.
CROSS-REFERENCE: 80.166^B
1)= S ^ICD0(DA(1),66,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(1),66,"B",$E(X,1,30),DA)
^ICD0(IEN1,66,"B",DATE,IEN2) - Where IEN1 is the internal entry number in file #80.1, DATE is the
effective date of the status, and IEN2 is the internal entry number of the STATUS multiple
sub-file 80.166 where the effective date is stored.
CROSS-REFERENCE: 80.1^ACT2^MUMPS
1)= D SAHD^ICDIDX2(80.1)
2)= D KAHD^ICDIDX2(80.1)
^ICD0("ACT",(CODE_" "),STA,EF,IEN1,IEN2) ^ICD0("ACTS",SYS,(CODE_" "),STA,EF,IEN1,IEN2) Where CODE
is the ICD code, STA is either 1 (active) or 0 (inactive), EF is the effective date of the
status, IEN1 is the internal entry number in file #80.1 and IEN2 is the internal entry number of
the STATUS multiple sub-file 80.166 where the status is stored. The subscript SYS is added to
the ACTS cross reference to create a coding system specific cross-reference.
80.166,.02 STATUS 0;2 SET (Required)
'0' FOR INACTIVE;
'1' FOR ACTIVE;
LAST EDITED: SEP 19, 2011
HELP-PROMPT: Enter code status.
DESCRIPTION:
Status set to 1 when the code is active and 0 when the code is inactive.
CROSS-REFERENCE: 80.1^ACT3^MUMPS
1)= D SAHS^ICDIDX2(80.1)
2)= D KAHS^ICDIDX2(80.1)
^ICD0("ACT",(CODE_" "),STA,EF,IEN1,IEN2) ^ICD0("ACTS",SYS,(CODE_" "),STA,EF,IEN1,IEN2) Where CODE
is the ICD code, STA is either 1 (active) or 0 (inactive), EF is the effective date of the
status, IEN1 is the internal entry number in file #80.1 and IEN2 is the internal entry number of
the STATUS multiple sub-file 80.166 where the status is stored. The subscript SYS is added to the
ACTS cross reference to create a coding system specific cross-reference.
80.1,67 OPERATION/PROCEDURE 67;0 DATE Multiple #80.167
LAST EDITED: SEP 15, 2011
DESCRIPTION: This is a history of the operation/procedure (short text) to include the date the text was first
used along with the text.
80.167,.01 OPER/PROCEDURE EFFECTIVE DATE 0;1 DATE (Required) (Multiply asked)
INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:2781001>X X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter a date not earlier than Oct 1, 1978.
DESCRIPTION:
This is the date the operation/procedure became effective.
CROSS-REFERENCE: 80.167^B
1)= S ^ICD0(DA(1),67,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(1),67,"B",$E(X,1,30),DA)
^ICD0(IEN1,67,"B",EFF,IEN2) - Where IEN1 is the internal entry number in the ICD
Operation/Procedure file #80.1, EFF is the effective date for the operation/procedure (short
text), and IEN2 is the internal entry number in the OPERATION/PROCEDURE (VERSIONED) multiple
where the versioned short text is stored.
CROSS-REFERENCE: 80.1^AST^MUMPS
1)= D SAST^ICDIDX(80.1)
2)= D KAST^ICDIDX(80.1)
^ICD0("AST",(CODE_" "),EFF,IEN1,IEN2) - Where CODE is the ICD operation/procedure Code, EFF is
the effective date for the operation/procedure (short text), IEN1 is the internal entry number in
the ICD-9 Operation/Procedure file (#80.1) and IEN2 is the internal entry number in the
OPERATION/PROCEDURE multiple where the short text is stored.
CROSS-REFERENCE: 80.1^ASTS1^MUMPS
1)= D SASTS1^ICDIDX(80.1)
2)= D KASTS1^ICDIDX(80.1)
^ICD0("ASTS",SYS,(CODE_" "),EFF,IEN1,IEN2) - Where SYS is the coding system, CODE is the ICD
procedure code, EFF is the effective date for the Operation/Procedure (short text), IEN1 is the
internal entry number in the ICD Operation/Procedure file (#80.1) and IEN2 is the internal entry
number in the OPERATION/PROCEDURE multiple (#80.167) where the short text is stored.
80.167,1 OPERATION/PROCEDURE 0;2 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>60!($L(X)<1) X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Answer must be 1-60 characters in length.
DESCRIPTION:
This is the operations/procedure (short text) that was used beginning on the effective date.
80.1,68 DESCRIPTION 68;0 DATE Multiple #80.168
LAST EDITED: SEP 15, 2011
DESCRIPTION: This is a history of the descriptive text to include the date the text was first used and the text
used.
80.168,.01 DESCRIPTION EFFECTIVE DATE 0;1 DATE (Required) (Multiply asked)
INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:2781001>X X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter a date not earlier than Oct 1, 1978.
DESCRIPTION:
This is the date the description became effective.
CROSS-REFERENCE: 80.168^B
1)= S ^ICD0(DA(1),68,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(1),68,"B",$E(X,1,30),DA)
^ICD0(IEN1,68,"B",EFF,IEN2) - Where IEN1 is the internal entry number in the ICD-9
Operation/Procedure file #80.1, EFF is the effective date for the description (long text), and
IEN2 is the internal entry number in the DESCRIPTION (VERSIONED) multiple where the versioned
procedure description is stored.
CROSS-REFERENCE: 80.1^ADS^MUMPS
1)= D SADS^ICDIDX(80.1)
2)= D KADS^ICDIDX(80.1)
^ICD0("ADS",(CODE_" "),EFF,IEN1,IEN2) - Where CODE is the ICD Operation/Procedure code, EFF is
the effective date for the description (long text), IEN1 is the internal entry number in the ICD
Operation/Procedure file (#80.1) and IEN2 is the internal entry number in the DESCRIPTION
multiple (#80.168) where the description is stored.
CROSS-REFERENCE: 80.1^ADSS1^MUMPS
1)= D SADSS1^ICDIDX(80.1)
2)= D KADSS1^ICDIDX(80.1)
^ICD0("ADSS",SYS,(CODE_" "),EFF,IEN1,IEN2) - Where SYS is the coding system, CODE is the ICD
procedure code, EFF is the effective date for the description (long text), IEN1 is the internal
entry number in the ICD Operation/Procedure file (#80.1) and IEN2 is the internal entry number in
the DESCRIPTION multiple (#80.168) where the long text is stored.
80.168,1 DESCRIPTION 1;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>245!($L(X)<1) X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Answer must be 1-245 characters in length.
DESCRIPTION:
This is the description (long text) that was in use on the effective date.
CROSS-REFERENCE: 80.1^D^MUMPS
1)= D SD^ICDIDX(80.1)
2)= D KD^ICDIDX(80.1)
^ICD0("D",WORD,IEN1,DATE,IEN2) - Where WORD is a single word extracted from the description, IEN1
is the internal entry number in file #80.1 where the description is stored, DATE is the effective
date of the description and IEN2 number of the internal entry number of the DESCRIPTION multiple
sub-file #80.168 where the description containing the extracted word is stored. This is a
modification of a Fileman KWIC (Key Word In Context) cross-reference. Like the Fileman KWIC
cross-reference, each word in the description is indexed. Unlike the KWIC cross-reference the
index contains the effective date of the description. This is done to allow date sensitive
keyword searches of the Operations/Procedure file.
CROSS-REFERENCE: 80.1^AD^MUMPS
1)= D SAD^ICDIDX(80.1)
2)= D KAD^ICDIDX(80.1)
^ICD0("AD",SYS,WORD,IEN1,DATE,IEN2) - Where SYS is the coding system in file 80.1, WORD is a
single word extracted from the description, IEN1 is the internal entry number in file #80.1 where
the description is stored, DATE is the effective date of the description and IEN2 is the internal
entry number of the DESCRIPTION multiple sub-file #80.168 where the description containing the
extracted word is stored. This is a modification of a Fileman KWIC (Key Word In Context)
cross-reference. Like the Fileman KWIC cross-reference, each word in the description is indexed.
Unlike the KWIC cross-reference the index contains the effective date of the description. This is
done to allow date sensitive keyword searches of the Operations/Procedure file.
80.168,2 SUPPLEMENTAL 2;0 Multiple #80.1682
DESCRIPTION: This is a list of Supplemental keywords which should be included in the word index to assist in
look-up operations.
80.1682,.01 WORD 0;1 FREE TEXT (Multiply asked)
INPUT TRANSFORM: K:$L(X)>63!($L(X)<1) X
LAST EDITED: AUG 25, 2012
HELP-PROMPT: Answer must be 1-63 characters in length.
DESCRIPTION:
This field contains a single word that should be included in the word index.
CROSS-REFERENCE: 80.1682^B
1)= S ^ICD0(DA(2),68,DA(1),2,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(2),68,DA(1),2,"B",$E(X,1,30),DA)
^ICD0(OP,68,DES,2,"B",WORD,IEN) - where OP is the internal entry number (IEN) of the ICD
Operation/Procedure file, DES is the internal entry number of the DESCRIPTION multiple
(sub-file #80.168) of the description containing supplemental keywords, WORD an alternate
keyword to be used in lookups and IEN is the internal entry number of the SUPPLEMENTAL multiple
(sub-file #80.1682) where the supplemental keyword is stored.
CROSS-REFERENCE: 80.1^AD3^MUMPS
1)= D SAD3^ICDIDX(80.1)
2)= D KAD3^ICDIDX(80.1)
^ICD0("AD",SYS,WD,FI,CDT,DI,WI) - where SYS is the coding system (field 1.1), WD is a keyword
from the SUPPLEMENTAL sub-file (80.1682), FI is the internal entry number to the ICD Operation
Procedure file, CDT is the date the keyword became effective (sub-file 80.168, .01 field), DI
is the internal entry number of the DESCRIPTION multiple (sub-file 80.168) and WI is the
internal entry number of the SUPPLEMENTAL multiple (sub-file 80.1682) where the key word is
stored.
80.1,71 DRG GROUPER 2;0 DATE Multiple #80.171
LAST EDITED: SEP 15, 2011
DESCRIPTION: This is a history of the DRG Grouper Major Diagnostic Codes and DRGs for an ICD procedure code and
contains the date the MDCs/DRGs became effective along with the MDCs and DRGs.
80.171,.01 DRG GROUPER EFFECTIVE DATE 0;1 DATE (Multiply asked)
INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:X<1 X
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter the DRG Grouper effective date.
DESCRIPTION: This is the effective date for the MDCs and DRGs for a fiscal year. It should normally be the
first day of October of the fiscal year. Each year a new entry will be created and the DRG's
hierarchy will reside within this field.
CROSS-REFERENCE: 80.171^B
1)= S ^ICD0(DA(1),2,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(1),2,"B",$E(X,1,30),DA)
^ICD0(IEN1,2,"B",EFF,IEN2) - Where IEN1 is the internal entry number in the OPERATIONS/PROCEDURE
file 80.1, EFF is the effective date of the MDCs/DRGs, and IEN2 is the internal entry number of
the DRG GROUPER multiple 80.171 where the MDCs/DRGs are stored.
80.171,1 MAJOR DIAGNOSTIC CATEGORIES 1;0 POINTER Multiple #80.1711
LAST EDITED: SEP 30, 2011
DESCRIPTION:
Major Diagnostic Categories (MDC) associated with the ICD Operation/Procedure.
80.1711,.01 MAJOR DIAGNOSTIC CATEGORY 0;1 POINTER TO MAJOR DIAGNOSTIC CATEGORY FILE (#80.3) (Multiply asked)
LAST EDITED: OCT 05, 2011
HELP-PROMPT: Enter MDC associated with the ICD code.
DESCRIPTION:
This is a Major Diagnostic Category (MDC) associated with the ICD Operation/Procedure.
CROSS-REFERENCE: 80.1711^B
1)= S ^ICD0(DA(2),2,DA(1),1,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(2),2,DA(1),1,"B",$E(X,1,30),DA)
^ICD0(IEN1,2,IEN2,1,"B",MDC,IEN3) - Where IEN1 is the internal entry number in the
OPERATIONS/PROCEDURE file 80.1, IEN2 is the internal entry in the DRG GROUPER multiple 80.171,
MDC is a pointer to the MAJOR DIAGNOSTIC CATEGORY file #80.3 and IEN3 is the internal entry
number on the MAJOR DIAGNOSTIC CATEGORY multiple 80.1711 where the MDC is stored.
80.1711,1 DRG 1;0 POINTER Multiple #80.17111
DESCRIPTION:
DRG(s) associated with corresponding ICD Operation/Procedure for a given fiscal year.
80.17111,.01 DRG 0;1 POINTER TO DRG FILE (#80.2) (Multiply asked)
LAST EDITED: SEP 30, 2011
HELP-PROMPT: Enter a DRG associated with the MDC for the ICD code.
DESCRIPTION:
This is a DRG Group associated with the procedure.
CROSS-REFERENCE: 80.17111^B
1)= S ^ICD0(DA(3),2,DA(2),1,DA(1),1,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(3),2,DA(2),1,DA(1),1,"B",$E(X,1,30),DA)
^ICD0(IEN1,2,IEN2,1,IEN3,1,"B",DRG,IEN4) - Where IEN1 is the internal entry number in the
OPERATIONS/PROCEDURE file 80.1, IEN2 is the internal entry number in the DRG GROUPER multiple
80.171, IEN3 is the internal entry number in the MAJOR DIAGNOSTIC CATEGORY multiple 80.1711,
DRG is a pointer to the DRG file #80.2 and IEN4 is the enternal entry number of the DRG
multiple #80.17111 where the DRG is stored.
80.1,73 DRG PROCEDURE IDENTIFIER CODES 73;0 POINTER Multiple #80.173
LAST EDITED: MAY 30, 2012
DESCRIPTION:
This is a listing of identifier codes used in the DRG rules processing to determine DRG.
80.173,.01 DRG PROCEDURE IDENTIFIER CODE 0;1 POINTER TO DRG PROCEDURE IDENTIFIER CODES FILE (#82.1) (Multiply asked)
LAST EDITED: MAY 30, 2012
HELP-PROMPT: Enter a DRG Procedure Identifier Code.
DESCRIPTION:
This is an identifier code used in the DRG rules processing to determine DRG.
CROSS-REFERENCE: 80.173^B
1)= S ^ICD0(DA(1),73,"B",$E(X,1,30),DA)=""
2)= K ^ICD0(DA(1),73,"B",$E(X,1,30),DA)
^ICD0(IEN1,73,"B",ID,IEN2) - Where IEN1 is the internal entry number in file #80, ID a procedure
identifier code (a pointer to the DRG PROCEDURE IDENTIFIER CODES file #82.1), and IEN2 is the
internal entry number of the DRG PROCEDURE IDENTIFIER CODES multiple sub-file 80.173 where the
procedure identifier code is stored.
FILES POINTED TO FIELDS
DRG (#80.2) DRG:DRG (#.01)
DRG PROCEDURE IDENTIFIER CODES
(#82.1) DRG PROCEDURE IDENTIFIER CODES:DRG PROCEDURE IDENTIFIER CODE (#.01)
ICD CODING SYSTEMS (#80.4) CODING SYSTEM (#1.1)
MAJOR DIAGNOSTIC CATEGORY
(#80.3) MAJOR DIAGNOSTIC CATEGORIES:MAJOR DIAGNOSTIC CATEGORY (#.01)
File #80.1
Record Indexes:
ABA (#1132) RECORD REGULAR IR SORTING ONLY
Short Descr: BA Cross-Reference by Coding System for Sorting
Description: ^ICD0("ABA",SYS,(CODE_" "),IEN) - Where SYS is the coding system to which the ICD code belongs, CODE is the ICD
code, and IEN is the internal entry number in file #80.1 where the code is stored. This is similar to the BA
cross-reference except it is not used by Fileman during lookup. The ABA cross-reference is used by the special
lookup routine during lookup by code. Appending a space character to CODE forces the code to be regarded as a
string, thus disallowing the dropping of leading '0's.
Set Logic: S ^ICD0("ABA",$E(X(1),1,10),$E(X(2),1,30),DA)=""
Set Cond: S X=$S(+($$GET1^DIQ(80.1,(+DA_","),1.8))'>0:1,1:0)
Kill Logic: K ^ICD0("ABA",$E(X(1),1,10),$E(X(2),1,30),DA)
Whole Kill: K ^ICD0("ABA")
X(1): CODING SYSTEM (80.1,1.1) (Subscr 1) (Len 10) (forwards)
X(2): CODE NUMBER (80.1,.01) (Subscr 2) (Len 30) (forwards)
Transform (Storage): S X=(X_" ")
AN (#1134) RECORD REGULAR IR SORTING ONLY
Short Descr: Numeric Code Cross-Reference
Description: ^ICD0("AN",SYS,NUM,IEN) - Where SYS is the coding system, NUM is a numeric representation of an ICD code, and
IEN is the internal entry number in the ICD Diagnosis file (#80.1) where the code is stored. The Numeric
representation of a code is used to determine the next or previous code.
Set Logic: S ^ICD0("AN",$E(X(1),1,10),$E(X(2),1,30),DA)=""
Set Cond: S X=$S(+($$GET1^DIQ(80.1,(+DA_","),1.8))'>0:1,1:0)
Kill Logic: K ^ICD0("AN",$E(X(1),1,10),$E(X(2),1,30),DA)
Whole Kill: K ^ICD0("AN")
X(1): CODING SYSTEM (80.1,1.1) (Subscr 1) (Len 10) (forwards)
Transform (Storage): S X=+X
X(2): CODE NUMBER (80.1,.01) (Subscr 2) (Len 30) (forwards)
Transform (Storage): S X=$$NUM^ICDEXS(X)
AVA (#1135) RECORD MUMPS IR SORTING ONLY
Short Descr: AVA Cross-Reference of VA ICD Expanded Codes
Description: ^ICD0("AVA",(CODE_" "),IEN) - This cross-reference is set only when a code is designated as a local VA code,
where CODE is an ICD code that has been expanded for use in the VA (local code) and IEN is the internal entry
number in file 80.1 where the VA local code is stored.
Set Logic: S ^ICD0("AVA",$E(X(1),1,30),DA)=""
Set Cond: S X=X(2)
Kill Logic: K ^ICD0("AVA",$E(X(1),1,30),DA)
Whole Kill: K ^ICD9("AVA")
X(1): CODE NUMBER (80.1,.01) (Subscr 1) (Len 30) (forwards)
Transform (Storage): S X=(X_" ")
X(2): ICD EXPANDED (80.1,1.7) (Len 10) (forwards)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):