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 |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All
Print Page as PDF
Global: ^AUPNPROB

Package: Problem List

Global: ^AUPNPROB


Information

FileMan FileNo FileMan Filename Package
9000011 PROBLEM Problem List

Description

Directly Accessed By Routines, Total: 54

Package Total Routines
Problem List 33 GMPL    GMPL1    GMPL15P    GMPL31P    GMPLCLNP    GMPLCODE    GMPLDISP    GMPLDUP2
GMPLEDIT    GMPLEDT2    GMPLEDT3    GMPLENFM    GMPLHS    GMPLMGR    GMPLMGR1    GMPLMGR2
GMPLNTFT    GMPLNTRT    GMPLPRNT    GMPLPXRM    GMPLRPTR    GMPLRPTS    GMPLSAVE    GMPLUTL
GMPLUTL1    GMPLUTL2    GMPLUTL3    GMPLX    GMPLX1    NOTE    NOTE FACILITY    ^AUPNPROB
MAPPING TARGETS    
PCE Patient Care Encounter 6 PX1P94    PXCADXP1    PXCAPL    PXCAPL1    PXCAPL2    PXCAPOV    
Order Entry Results Reporting 4 ORCPROB    ORQQPL1    ORQQPL2    ORQQPL3    
Automated Information Collection System 2 IBDFBK3    IBDFN11    
Virtual Patient Record 2 VPREVNT    VPRSDA    
Clinical Case Registries 1 RORHL17    
Enterprise Health Management Platform 1 HMPDJ02    
Health Summary 1 GMTSPLSZ    
Quasar 1 ACKQUTL6    

Accessed By FileMan Db Calls, Total: 25

Package Total Routines
Problem List 14 GMPL1    GMPLCLNP    GMPLCODE    GMPLEDT3    GMPLNTFT    GMPLNTRT    GMPLP37I    GMPLP44I
GMPLPXRM    GMPLRPTR    GMPLSAVE    GMPLUTL2    GMPLX    GMPLY47    
Enterprise Health Management Platform 2 HMPDGMPL    HMPDJ02    
Virtual Patient Record 2 VPRDGMPL    VPRDJ02    
Clinical Case Registries 1 RORHL17    
Clinical Reminders 1 PXRMPROB    
Emergency Department Integration Software 1 EDPDTL    
Lexicon Utility 1 LEXAR8    
National Health Information Network 1 NHINVPL    
Order Entry Results Reporting 1 ORQQPL2    
Scheduling 1 SCRPW1    

Pointed To By FileMan Files, Total: 3

Package Total FileMan Files
PCE Patient Care Encounter 1 V POV(#9000010.07)[.16]    
Problem List 1 PROBLEM LIST AUDIT(#125.8)[.01]    
Text Integration Utility 1 TIU PROBLEM LINK(#8925.9)[.02]    

Pointer To FileMan Files, Total: 8

Package Total FileMan Files
PCE Patient Care Encounter 3 PATIENT/IHS(#9000001)[.02]    PROVIDER NARRATIVE(#9999999.27)[.05]    LOCATION(#9999999.06)[.06#9000011.11(.01)]    
Kernel 2 SERVICE/SECTION(#49)[1.06]    NEW PERSON(#200)[1.031.041.05#9000011.1111(.06)]    
DRG Grouper 1 ICD DIAGNOSIS(#80)[.01]    
Lexicon Utility 1 EXPRESSIONS(#757.01)[1.01]    
Scheduling 1 HOSPITAL LOCATION(#44)[1.08]    

Fields, Total: 39

Field # Name Loc Type Details
.01 DIAGNOSIS 0;1 POINTER TO ICD DIAGNOSIS FILE (#80)
************************REQUIRED FIELD************************
ICD DIAGNOSIS(#80)

  • INPUT TRANSFORM:  S DIC("S")="I 1 Q:$G(DUZ(""AG""))=""V"" I $E(^(0))'=""E"",$P(^(0),U,9)="""" Q:$P(^(0),U,10)="""" I $P(^(0),U,10)=AUPNSEX" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  NOV 30, 2012
  • HELP-PROMPT:  Enter the ICD Code for this problem.
  • DESCRIPTION:  
    This is the ICD coded diagnosis of the narrative entered describing this problem.
  • TECHNICAL DESCR:  The DHCP Problem List application derives its entries from a lookup into the Clinical Lexicon Utility rather than the ICD Diagnosis file. If the term selected from the CLU is not coded to ICD, then code 799.99 "Other
    Unknown or Unspecified Cause, NEC" will be used here in order to be able to create a new entry.  This field may later be edited.
  • SCREEN:  S DIC("S")="I 1 Q:$G(DUZ(""AG""))=""V"" I $E(^(0))'=""E"",$P(^(0),U,9)="""" Q:$P(^(0),U,10)="""" I $P(^(0),U,10)=AUPNSEX"
  • EXPLANATION:  Cannot be an E code or an inactive code and must be appropriate for the sex of the Patient.
  • CROSS-REFERENCE:  9000011^B
    1)= S ^AUPNPROB("B",$E(X,1,30),DA)=""
    2)= K ^AUPNPROB("B",$E(X,1,30),DA)
  • CROSS-REFERENCE:  9000011^AV9^MUMPS
    1)= S:$D(APCDLOOK) DIC("DR")=""
    2)= Q
    Controls the behaviour of the input templates used by IHS to populate and maintain this file.
  • RECORD INDEXES:  ACR01 (#703)
.02 PATIENT NAME 0;2 POINTER TO PATIENT/IHS FILE (#9000001)
************************REQUIRED FIELD************************
PATIENT/IHS(#9000001)

  • LAST EDITED:  NOV 30, 2012
  • HELP-PROMPT:  Enter the name of the patient for whom this problem has been observed.
  • DESCRIPTION:  
    This is the patient for whom this problem has been observed and recorded.
    UNEDITABLE
  • CROSS-REFERENCE:  9000011^AC
    1)= S ^AUPNPROB("AC",$E(X,1,30),DA)=""
    2)= K ^AUPNPROB("AC",$E(X,1,30),DA)
  • CROSS-REFERENCE:  9000011^AATOO^MUMPS
    1)= I $P(^AUPNPROB(DA,0),U,6)]"",$P(^(0),U,7)]"" S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7),".",2),^AUPNPROB("AA",X,$P(^(0),U,6)," "_$E("000",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2)-1),DA)="" K X1,X2
    2)= I $P(^AUPNPROB(DA,0),U,6)]"",$P(^(0),U,7)]"" S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7),".",2) K ^AUPNPROB("AA",X,$P(^(0),U,6)," "_$E("000",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2)-1),DA),X1,X2
    Allows problem retrieval by patient, facility, and problem number (Nmbr); the number is used as a string in " 000.00" format to assure a consistent ordering.
  • CROSS-REFERENCE:  9000011^ACTIVE1^MUMPS
    1)= S:$L($P(^AUPNPROB(DA,0),U,12)) ^AUPNPROB("ACTIVE",X,$P(^(0),U,12),DA)=""
    2)= K:$L($P(^AUPNPROB(DA,0),U,12)) ^AUPNPROB("ACTIVE",X,$P(^(0),U,12),DA)
    Allows problem retrieval by patient and status, in order of entry.
  • RECORD INDEXES:  ACR01 (#703), ACRSCT (#755)
.03 DATE LAST MODIFIED 0;3 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="EX" D ^%DT S X=Y K:DTX) X
  • LAST EDITED:  NOV 30, 2012
  • HELP-PROMPT:  TYPE A DATE BETWEEN 1900 AND TODAY
  • DESCRIPTION:  
    This is the last date/time this problem was changed.
    SOURCE OF DATA:   018/PRCOND
  • CROSS-REFERENCE:  9000011^MODIFIED^MUMPS
    1)= K ^AUPNPROB("MODIFIED",$P(^AUPNPROB(DA,0),"^",2)) D NOW^%DTC S ^AUPNPROB("MODIFIED",$P(^AUPNPROB(DA,0),"^",2),%)=""
    2)= Q
    This Index will keep track of the last time this Patients problem list was modified.  ^AUPNPROB("MODIFIED"),PATIENT,DATE
  • RECORD INDEXES:  ACR01 (#703), ACRMTA (#429), ACRSCT (#755)
.04 CLASS 0;4 SET
  • 'P' FOR PERSONAL HISTORY;
  • 'F' FOR FAMILY HISTORY;

  • LAST EDITED:  OCT 07, 1987
  • HELP-PROMPT:  If this problem is historical, indicate if it is Personal or Family history.
  • DESCRIPTION:  
    This flag is used by the IHS Problem List to indicate if this problem is documented for historical purposes.
  • TECHNICAL DESCR:  
    VA sites using the DHCP Problem List application will not be prompted for this information.
.05 PROVIDER NARRATIVE 0;5 POINTER TO PROVIDER NARRATIVE FILE (#9999999.27)
************************REQUIRED FIELD************************
PROVIDER NARRATIVE(#9999999.27)

  • INPUT TRANSFORM:  S DIC(0)=$S($D(APCDALVR):"LO",1:"EMQLO") D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  NOV 28, 1988
  • HELP-PROMPT:  Enter a description of this patient's problem.
  • DESCRIPTION:  
    This contains the actual text used by the provider to describe this problem.
  • SCREEN:  S DIC(0)=$S($D(APCDALVR):"LO",1:"EMQLO")
  • EXPLANATION:  OLD LOOKUP
.06 FACILITY 0;6 POINTER TO LOCATION FILE (#9999999.06)
************************REQUIRED FIELD************************
LOCATION(#9999999.06)

  • LAST EDITED:  JAN 10, 1994
  • HELP-PROMPT:  Enter the location at which this problem was first observed and recorded.
  • DESCRIPTION:  
    This is the facility at which this problem was originally observed and documented.
    UNEDITABLE
  • CROSS-REFERENCE:  9000011^AV1^MUMPS
    1)= Q
    2)= Q
    No longer in use.
  • CROSS-REFERENCE:  9000011^AATOO2^MUMPS
    1)= I $P(^AUPNPROB(DA,0),U,2)]"",$P(^(0),U,7)]"" S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7),".",2),^AUPNPROB("AA",$P(^(0),U,2),X," "_$E("000",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2)-1),DA)="" K X1,X2
    2)= I $P(^AUPNPROB(DA,0),U,2)]"",$P(^(0),U,7)]"" S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7),".",2) K ^AUPNPROB("AA",$P(^(0),U,2),X," "_$E("000",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2)-1),DA),X1,X2
    Allows problem retrieval by patient, facility, and problem number (Nmbr); the number is used as a string in " 000.00" format to assure a consistent ordering.
.07 NMBR 0;7 NUMBER
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:+X'=X!(X>999.99)!(X<1)!(X?.E1"."3N.N) X Q:'$D(X) K:$D(^AUPNPROB("AA",$P(^AUPNPROB(DA,0),U,2),$P(^(0),U,6)," "_$E("000",1,4-$L($P(X,".",1))-1)_$P(X,".",1)_"."_$P(X,".",2)_$E("00",1,3-$L($P(X,".",2))-1))) X
  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  TYPE A NUMBER BETWEEN 1 AND 999.99
  • DESCRIPTION:  This is a number which, together with the Patient (#.02) and Facility (#.06) fields, serves as a unique identifier for this problem. Up to 2 decimal places may be used to indicate that a problem is a result of, or related
    to, another problem.
    SOURCE OF DATA:   018/PRNUMB
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  9000011^AA^MUMPS
    1)= S ^AUPNPROB("AA",$P(^AUPNPROB(DA,0),U,2),$P(^(0),U,6)," "_$E("000",1,4-$L($P(X,".",1))-1)_$P(X,".",1)_"."_$P(X,".",2)_$E("00",1,3-$L($P(X,".",2))-1),DA)=""
    2)= K ^AUPNPROB("AA",$P(^AUPNPROB(DA,0),U,2),$P(^(0),U,6)," "_$E("000",1,4-$L($P(X,".",1))-1)_$P(X,".",1)_"."_$P(X,".",2)_$E("00",1,3-$L($P(X,".",2))-1),DA)
    Allows problem retrieval by patient, facility, and problem number (Nmbr); the number is used as a string in " 000.00" format to assure a consistent ordering.
.08 DATE ENTERED 0;8 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="EX" D ^%DT S X=Y K:DTX) X
  • LAST EDITED:  JUN 07, 2012
  • HELP-PROMPT:  TYPE A DATE BETWEEN 1900 AND TODAY
  • DESCRIPTION:  
    This is the date this problem was entered into this file.
    SOURCE OF DATA:   018/PREDAT
    UNEDITABLE
  • RECORD INDEXES:  DM (#756)
.12 STATUS 0;12 SET
************************REQUIRED FIELD************************
  • 'A' FOR ACTIVE;
  • 'I' FOR INACTIVE;

  • LAST EDITED:  NOV 30, 2012
  • HELP-PROMPT:  Enter the current status of this problem, active or inactive.
  • DESCRIPTION:  
    This is the current activity status of this problem, whether active or inactive; if more detail is needed, a notation may be filed with this problem.
    SOURCE OF DATA:   018/PRSTAT
  • CROSS-REFERENCE:  9000011^ACTIVE^MUMPS
    1)= S:$P(^AUPNPROB(DA,0),U,2) ^AUPNPROB("ACTIVE",+$P(^(0),U,2),X,DA)=""
    2)= K ^AUPNPROB("ACTIVE",+$P(^AUPNPROB(DA,0),U,2),X,DA)
    Allows problem retrieval by patient and status, in order of entry.
  • RECORD INDEXES:  ACR01 (#703), ACRMTA (#429), ACRSCT (#755)
.13 DATE OF ONSET 0;13 DATE

  • INPUT TRANSFORM:  S %DT="E" D ^%DT S X=Y K:DTX) X
  • LAST EDITED:  JUN 13, 1993
  • HELP-PROMPT:  TYPE A DATE BETWEEN 1880 AND TODAY
  • DESCRIPTION:  
    This is the approximate date this problem appeared, as precisely as known.
1.01 PROBLEM 1;1 POINTER TO EXPRESSIONS FILE (#757.01) EXPRESSIONS(#757.01)

  • LAST EDITED:  JUL 28, 1993
  • HELP-PROMPT:  Enter the problem observed for this patient.
  • DESCRIPTION:  
    This field contains the standardized text stored in the Clinical Lexicon for this problem.
  • CROSS-REFERENCE:  9000011^C
    1)= S ^AUPNPROB("C",$E(X,1,30),DA)=""
    2)= K ^AUPNPROB("C",$E(X,1,30),DA)
1.02 CONDITION 1;2 SET
  • 'T' FOR TRANSCRIBED;
  • 'P' FOR PERMANENT;
  • 'H' FOR HIDDEN;

  • LAST EDITED:  NOV 30, 2012
  • DESCRIPTION:  
    This reflects the current condition of this entry, whether transcribed by a clerk from the paper chart, entered or verified by a provider, or marked as removed from the patient's list.
  • TECHNICAL DESCR:  This flag is used internally by the DHCP Problem List; entries having an H in this field have been "deleted" and are maintained for historical use but are generally ignored. If the parameter "Verify Transcribed Entries"
    is turned on in File #125.99, entries made by a clerk will have a T here, and a flag will appear on the clinician's display of the list.  P entries have been entered or verified by a provider.
  • RECORD INDEXES:  ACR01 (#703), ACRMTA (#429), ACRSCT (#755)
1.03 ENTERED BY 1;3 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter the name of the current user.
  • DESCRIPTION:  
    This is the user who actually entered this problem into this file.
1.04 RECORDING PROVIDER 1;4 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  MAY 02, 1996
  • HELP-PROMPT:  Enter the name of the provider who first recorded this data.
  • DESCRIPTION:  
    This is the provider who first recorded this problem, either on the paper chart or online.
  • SCREEN:  S DIC("S")="I $S('$D(^(""PS"")):1,'$P(^(""PS""),U,4):1,DT')$P(^(""PS""),U,4):1,1:0)&($D(^XUSEC(""PROVIDER"",Y)))"
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
1.05 RESPONSIBLE PROVIDER 1;5 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter the name of the local provider treating this problem.
  • DESCRIPTION:  
    This is the provider currently responsible for treating this problem.
1.06 SERVICE 1;6 POINTER TO SERVICE/SECTION FILE (#49) SERVICE/SECTION(#49)

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter the service to be associated with this problem.
  • DESCRIPTION:  This is the service primarily involved in the treatment of this problem; the DHCP Problem List defaults this field to the service defined in File #200 for the Recording Provider of this problem, upon entry of the problem.
    It may later be used to categorize problems for screening and sorting.
1.07 DATE RESOLVED 1;7 DATE

  • INPUT TRANSFORM:  S %DT="E" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter the date this problem became resolved or inactive, as precisely as known.
  • DESCRIPTION:  
    This is the date this problem was resolved or inactivated, as precisely as known.
1.08 CLINIC 1;8 POINTER TO HOSPITAL LOCATION FILE (#44) HOSPITAL LOCATION(#44)

  • INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U,3)=""C""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  APR 12, 1994
  • HELP-PROMPT:  Enter the clinic in which the patient is being seen for this problem.
  • DESCRIPTION:  
    This is the clinic in which this patient is being seen for this problem.  The problem list may be screened based on this value, to change one's view of the list.
  • SCREEN:  S DIC("S")="I $P(^(0),U,3)=""C"""
  • EXPLANATION:  Only clinics are allowed here.
1.09 DATE RECORDED 1;9 DATE

  • INPUT TRANSFORM:  S %DT="E" D ^%DT S X=Y K:DTX) X
  • LAST EDITED:  JAN 11, 1994
  • HELP-PROMPT:  Enter the date this problem was first recorded, as precisely as known.
  • DESCRIPTION:  
    This is the date this problem was originally recorded, either online or in the paper chart; it may be the same as, or earlier than, the Date Entered.
1.1 SERVICE CONNECTED 1;10 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  If this problem is service connected, enter YES here.
  • DESCRIPTION:  
    If the patient has service connection on file in the DHCP Patient file #2, this problem specifically may be flagged as being service connected.
  • TECHNICAL DESCR:  
    This data will be prompted for in the DHCP Problem List only if the patient is indicated for service connection.  Non-VA sites will not be prompted for this information.
1.11 AGENT ORANGE EXPOSURE 1;11 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter YES if this problem is related to exposure to Agent Orange.
  • DESCRIPTION:  
    If this problem is related to a patient's exposure to Agent Orange, it may be flagged here.
  • TECHNICAL DESCR:  
    This data will be prompted for in the DHCP Problem List only if a patient has Agent Orange exposure indicated.  Non-VA sites will not be prompted for this information.
1.12 IONIZING RADIATION EXPOSURE 1;12 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter YES if this problem is related to exposure to ionizing radiation.
  • DESCRIPTION:  
    If this problem is related to a patient's exposure to ionizing radiation, it may be flagged here.
  • TECHNICAL DESCR:  
    This data will be prompted for in the DHCP Problem List only if the patient has ionizing radiation exposure indicated.  Non-VA sites will not be prompted for this information.
1.13 PERSIAN GULF EXPOSURE 1;13 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 26, 1993
  • HELP-PROMPT:  Enter YES if this problem is related to a Persian Gulf exposure.
  • DESCRIPTION:  
    If this problem is related to a patient's service in the Persian Gulf, it may be flagged here.
  • TECHNICAL DESCR:  
    This data will be prompted for only if a patient has Persian Gulf service indicated.  Non-VA sites will not be prompted for this information.
1.14 PRIORITY 1;14 SET
  • 'A' FOR ACUTE;
  • 'C' FOR CHRONIC;

  • LAST EDITED:  NOV 30, 2012
  • HELP-PROMPT:  You may further refine the status of this problem by assigning it a priority.
  • DESCRIPTION:  
    This is a flag to indicate how critical this problem is for this patient; problems marked as Acute will be flagged on the Problem List display.
  • RECORD INDEXES:  ACR01 (#703), ACRMTA (#429), ACRSCT (#755)
1.15 HEAD AND/OR NECK CANCER 1;15 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  MAR 07, 2002
  • DESCRIPTION:  
    If this problem is related to the treatment of head and/or neck cancer associated with nose or throat radium treatments, it may be flagged here.
  • TECHNICAL DESCR:  
    This data will be prompted for only if a patient has received nose or throat radium treatments.
1.16 MILITARY SEXUAL TRAUMA 1;16 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  MAR 07, 2002
  • DESCRIPTION:  
    If this problem is related to the treatment of military sexual trauma, it may be flagged here.
  • TECHNICAL DESCR:  
    This data will be prompted for only if a patient has been treated for military sexual trauma.
1.17 COMBAT VETERAN 1;17 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  NOV 25, 2003
  • HELP-PROMPT:  If this problem is a result of combat it may be flagged here
1.18 SHIPBOARD HAZARD & DEFENSE 1;18 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  SEP 18, 2006
  • HELP-PROMPT:  If this problem is a result of SHAD, it may be flagged here
1101 NOTE FACILITY 11;0 POINTER Multiple #9000011.11 9000011.11

  • DESCRIPTION:  
    This is the location at which the notes in this multiple originated.
80001 SNOMED CT CONCEPT CODE 800;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1)!'(X?1.40N) X
  • LAST EDITED:  JUN 07, 2012
  • HELP-PROMPT:  Answer must be 1-40 numeric characters in length.
  • DESCRIPTION:  
    A clinical idea to which a unique ConceptID has been assigned in SNOMED CT. Each Concept is represented by a row in the Concepts Table.
  • TECHNICAL DESCR:  
    NOTE: This field is filed programmatically. The user should never be directly prompted for it.
  • CROSS-REFERENCE:  9000011^ASCT
    1)= S ^AUPNPROB("ASCT",$E(X,1,30),DA)=""
    2)= K ^AUPNPROB("ASCT",$E(X,1,30),DA)
    3)= ** DO NOT DELETE **
    This REGULAR FileMan cross-reference on SNOMED CT Concept will help to automate the updating of problems when SNOMED Concepts are mapped or re-mapped to ICD-9-CM codes.
  • RECORD INDEXES:  ACRSCT (#755)
80002 SNOMED CT DESIGNATION CODE 800;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1)!'(X?1.40N) X
  • LAST EDITED:  JUN 06, 2012
  • HELP-PROMPT:  Answer must be 1-40 numeric characters in length.
  • DESCRIPTION:  A single SNOMED Concept may have multiple Designations, where a Designation may be considered an alternate way of expressing the concept. Synonyms, lexical variants, abbreviations are all different types of designations.
    In many cases, a problem (as reported by the patient) and a finding indicating a problem will share the same concept and concept code (e.g., abdominal pain), but will have different designation codes (i.e., the generic
    "abdominal pain  and "abdominal pain (finding)  share the concept code 21522001, but they have the designation codes 36112013 and 750827015 respectively.
  • TECHNICAL DESCR:  
    NOTE: This field is filed programmatically. The user should never be directly prompted for it.
80003 VHAT CONCEPT VUID (FUTURE) 800;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>20!($L(X)<1)!'(X?1.20N) X
  • LAST EDITED:  JUN 06, 2012
  • HELP-PROMPT:  Answer must be 1-20 characters in length.
  • DESCRIPTION:  VHA Unique ID (VUID) for the VHAT Concept. A unique meaningless integer assigned to a corresponding concept VHA wide.
    This field is being implemented to allow a more rapidly extensible vocabulary for VA, while international normative standard coding systems continue to evolve more slowly. The precise definition of the concept Polytrauma
    may prove to be a useful example. Although the term has become common among US Military and VA physicians to describe a seriously injured (i.e., Injury Severity Score (ISS) >= 16) soldier with multiple traumatic injuries,
    it is not yet available as a coded concept in either SNOMED CT, ICD-9-CM, or ICD-10-CM. Allowing the definition and deployment of VHAT Concept/Designation VUID pairs to identify such problems in advance of their acceptance
    by the international medical community will help to provide coded, computable documentation in a much more timely manner than waiting for inclusion in SNOMED CT or ICD.
    When the infrastructure in VA's Enterprise Terminology Server (ETS) & New Term Rapid Turn-around (NTRT) service are ready to deploy VHAT Concepts, this field will allow us to store patient problems encoded with them.
  • TECHNICAL DESCR:  
    NOTE: This field is filed programmatically. The user should never be directly prompted for it.
80004 VHAT DESIGNATION VUID (FUTURE) 800;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>20!($L(X)<1)!'(X?1.20N) X
  • LAST EDITED:  JUN 06, 2012
  • HELP-PROMPT:  Answer must be 1-20 numeric characters in length.
  • DESCRIPTION:  VHA Unique ID (VUID) for the VHAT Designation. A unique meaningless integer assigned to a corresponding designation VHA wide.
    VHAT Concept/Designation Code pairs function in a manner identical to that of SNOMED CT Concept/Designation Codes (i.e., they support the unique identification of clinical concepts, along with the many alternative ways in
    which a given concept may be expressed).
  • TECHNICAL DESCR:  
    NOTE: This field is filed programmatically. The user should never be directly prompted for it.
80005 SNOMED CT-TO-ICD MAP STATUS 800;5 SET
  • '0' FOR N/A;
  • '1' FOR PENDING;
  • '2' FOR COMPLETED;

  • LAST EDITED:  JUN 07, 2012
  • HELP-PROMPT:  Set by program to reflect mapping status of a finding
  • DESCRIPTION:  This Set of Codes type field is set to PENDING when an unmapped Clinical Finding is selected as a patient's problem. It is updated programmatically to COMPLETE when NTRT deploys a new SNOMED CT to ICD mapping for the
    problem in question.
    NOTE: THIS FIELD SHOULD NEVER BE UPDATED BY AN END USER.
  • TECHNICAL DESCR:  This Set of Codes type field is set to PENDING when an unmapped Clinical Finding is selected as a patient's problem. It is updated programmatically to COMPLETE when NTRT deploys a new SNOMED CT to ICD mapping for the
    problem in question.
  • RECORD INDEXES:  DM (#756)
80101 UNIQUE NEW TERM REQUESTED 801;1 SET
  • '0' FOR False;
  • '1' FOR True;

  • LAST EDITED:  JUN 06, 2012
  • HELP-PROMPT:  Indicate whether a New Term was requested (NTRT)
  • DESCRIPTION:  Indicates whether the user requested a new term during the process of entering a freetext problem. It should only be populated automatically by program code.
    NOTE: THIS FIELD SHOULD NEVER BE UPDATED BY AN END USER.
  • TECHNICAL DESCR:  This Boolean field indicates whether the provider requested a new term to be proposed and considered for inclusion in SNOMED CT. If accepted, the term will be deployed by the NTRT process. It should only be populated
    automatically by program code. The user will never be prompted for a value for this field.
80102 UNIQUE TERM REQUEST COMMENT 801;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>80!($L(X)<2) X
  • LAST EDITED:  JUN 06, 2012
  • HELP-PROMPT:  Answer must be 2-80 characters in length.
  • DESCRIPTION:  
    Please provide clarification of the new term request. For example, if the requested term is an acronym or abbreviation, the comment field accommodates the fully specified name, etc.
  • TECHNICAL DESCR:  This freetext field supports the storage of a one-line explanatory comment, to provide clarification of the new term request. For example, if the requested term is an acronym or abbreviation, the comment field accommodates
    the fully specified name, etc.
80201 DATE OF INTEREST 802;1 DATE

  • INPUT TRANSFORM:  S %DT="EX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUL 24, 2012
  • HELP-PROMPT:  (No range limit on date)
  • DESCRIPTION:  
    This is the date when the DIAGNOSIS (#.01) and CODING SYSTEM (#80202) fields were filed or modified. This allows proper resolution of the code, irrespective of code set versions, etc.
80202 CODING SYSTEM 802;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>3!($L(X)<3) X
  • LAST EDITED:  JUL 17, 2012
  • HELP-PROMPT:  Answer must be 3 characters in length.
  • DESCRIPTION:  This identifies the Coding System to which the Code belongs. It corresponds to the Coding System Abbreviation in the ICD Coding Systems File, to optimize internal/external API calls for resolving codes, independent of
    their code set version, and to facilitate transition from ICD-9-CM to ICD-10-CM.
    Examples include:
    CODING SYS
    ABBREV       NOMENCLATURE    ICD FILE
    ---------------------------------------------
    10D          ICD-10-CM      ICD Diagnosis
    ICD          ICD-9-CM       ICD Diagnosis
  • TECHNICAL DESCR:  This field is populated via M code and utilizes incremental/decremental timed locks to the PROBLEM file #9000011 for new problem entries. The Coding System Source Abbreviation (SAB) is programmatically filed in
    NEW^GMPLSAVE. The Coding System SAB is further validated before storage by utilizing the following ICD API's: $$CSI^ICDEX and $$SAB^ICDEX. This ensures that the correct code version or SAB is getting filed.
  • RECORD INDEXES:  ACR01 (#703)
80300 MAPPING TARGETS 803;0 Multiple #9000011.803 9000011.803

  • DESCRIPTION:  This multiple includes mapped expressions: complications, comorbidities, and compound diagnoses. e.g., the single SNOMED CT concept Diabetic neuropathy (230572002) is mapped to two ICD-9-CM diagnoses: DIABETES WITH
    NEUROLOGICAL MANIFESTATIONS, TYPE II OR UNSPECIFIED TYPE, NOT STATED AS UNCONTROLLED (250.60) and POLYNEUROPATHY IN DIABETES (357.2).

External References

Name Field # of Occurrence
^%DT .03+1, .08+1, .13+1, 1.07+1, 1.09+1, 80201+1
NOW^%DTC .03(XREF 1S)
^DIC .01+1, .05+1, 1.08+1
Y^DIQ ID.06+1
KPROB01^GMPLPXRM IXACR01KL+1
KPROBMT^GMPLPXRM IXACRMTKL+1
KPROBMTA^GMPLPXRM IXACRMTAKL+1
KPROBSCT^GMPLPXRM IXACRSCTKL+1
SPROB01^GMPLPXRM IXACR01SL+1
SPROBMT^GMPLPXRM IXACRMTSL+1
SPROBMTA^GMPLPXRM IXACRMTASL+1
SPROBSCT^GMPLPXRM IXACRSCTSL+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^AUPNPROB - [#9000011] .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K), .03(XREF 1S), .06(XREF 2S), .06(XREF 2K), .07+1, .07(XREF 1S), .07(XREF 1K)
.12(XREF 1S), .12(XREF 1K)
^AUPNPROB("AA" .02(XREF 2S), .02(XREF 2K), .06(XREF 2S), .06(XREF 2K), .07+1, .07(XREF 1S), .07(XREF 1K)
^AUPNPROB("AC" .02(XREF 1S), .02(XREF 1K)
^AUPNPROB("ACTIVE" .02(XREF 3S), .02(XREF 3K), .12(XREF 1S), .12(XREF 1K)
^AUPNPROB("ASCT" 80001(XREF 1S), 80001(XREF 1K)
^AUPNPROB("B" .01(XREF 1S), .01(XREF 1K)
^AUPNPROB("C" 1.01(XREF 1S), 1.01(XREF 1K)
^AUPNPROB("DM" IXDMSL+1*, IXDMKL+1!, IXDMKEIC+1!
^AUPNPROB("MODIFIED" .03(XREF 1S)
^DD(4 ID.06+1
^DIC(4 - [#4] ID.06+1
^DPT - [#2] ID.02+1

Naked Globals

Name Field # of Occurrence
^(0 ID.02+1, ID.06+1, ID.07+1, .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K), .06(XREF 2S), .06(XREF 2K), .07+1
.07(XREF 1S), .07(XREF 1K), .12(XREF 1S)

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> % .03(XREF 1S)
>> %DT .03+1*, .08+1*, .13+1*, 1.07+1*, 1.09+1*, 80201+1*
%I ID.06+1*!
>> APCDALVR .05+1, .05SCR+1
>> APCDLOOK .01(XREF 2S)
>> C ID.06+1*
>> DA IXACR01SL+1, IXACR01KL+1, IXACRMTSL+1, IXACRMTKL+1, IXACRMTASL+1, IXACRMTAKL+1, IXACRSCTSL+1, IXACRSCTKL+1, IXDMSL+1, IXDMKL+1
.01(XREF 1S), .01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K), .03(XREF 1S), .06(XREF 2S)
.06(XREF 2K), .07+1, .07(XREF 1S), .07(XREF 1K), .12(XREF 1S), .12(XREF 1K), 1.01(XREF 1S), 1.01(XREF 1K), 80001(XREF 1S), 80001(XREF 1K)
DIC ID.02+1, ID.06+1, .01+1!*, .05+1!*, 1.08+1!*
DIC("DR" .01(XREF 2S)
DIC("S" .01+1*, .01SCR+1*, .03SCR+1*, .08SCR+1*, 1.08+1*, 1.08SCR+1*
DIC(0 .05+1*, .05SCR+1*
>> DIE .01+1, .05+1, 1.08+1
DT .03+1, .08+1, .13+1, 1.09+1
U ID.02+1, ID.06+1, ID.07+1, .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K), .06(XREF 2S), .06(XREF 2K), .07+1
.07(XREF 1S), .07(XREF 1K), .12(XREF 1S), .12(XREF 1K)
X IXACR01SL+1, IXACR01KL+1, IXACRMTSL+1, IXACRMTKL+1, IXACRMTASL+1, IXACRMTAKL+1, IXACRSCTSL+1, IXACRSCTKL+1, .01+1*!, .01(XREF 1S)
.01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K), .03+1*!, .05+1*!, .06(XREF 2S)
.06(XREF 2K), .07+1!, .07(XREF 1S), .07(XREF 1K), .08+1*!, .12(XREF 1S), .12(XREF 1K), .13+1*!, 1.01(XREF 1S), 1.01(XREF 1K)
, 1.07+1*!, 1.08+1*!, 1.09+1*!, 80001+1!, 80001(XREF 1S), 80001(XREF 1K), 80002+1!, 80003+1!, 80004+1!, 80102+1!
, 80201+1*!, 80202+1!
X(1 IXDMSL+1, IXDMKL+1
X(2 IXDMSL+1, IXDMKL+1
X1 .02(XREF 2S), .02(XREF 2K), .06(XREF 2S), .06(XREF 2K)
X2 .02(XREF 2S), .02(XREF 2K), .06(XREF 2S), .06(XREF 2K)
>> Y ID.06+1*, .01+1, .03+1, .05+1, .08+1, .13+1, 1.07+1, 1.08+1, 1.09+1, 80201+1
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All