STANDARD DATA DICTIONARY #9000010.07 -- V POV FILE 3/24/25 PAGE 1
STORED IN ^AUPNVPOV( *** NO DATA STORED YET *** SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 1.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file has been designed for joint use by the Indian Health Service and the Department of Veteran Affairs. POV is an
abbreviation for "Purpose of Visit" (descriptive name used by IHS) or "Problem of Visit" (descriptive name used by VA).
The V POV file is used to store clinical data related to the "Purpose of Visit" or "Problem of Visit", (POV). This is the
provider's definition of what diagnosis represents the patient care given at the visit. The POV entry is not the patient's "Chief
Complaint" text. It is the diagnosis as defined by the provider, which will have an ICD Diagnosis code related to it to support
Clinical needs and additionally support Administrative functions such as Billing, Workload, and DSS.
There should be at least one V POV entry for each patient visit, whether it is an inpatient, outpatient or field visit, and
regardless of the discipline of the provider, i.e., dental, CHN, mental health, etc. There is no limit to the number of POV's that
can be entered for a patient for a given encounter.
At IHS facilities, POV's are generated automatically at the time of discharge from the Admission, Discharge and Transfer (ADT)
system. POVs are entered in narrative form, and coded automatically to the appropriate ICD diagnosis code. Physician entered
narrative, which modifies the diagnosis, such as "doubtful", "suspect", "resolved" are entered by the data entry person in the
MODIFIER field. The file contains pointers to the IHS Patient file, and Visit file, and data must exist in both files for this
visit before a POV can be entered.
At VA facilities, POVs are primarily created for clinic visits from 3 sources:
1) In the CPRS encounter form on the Diagnosis Tab. Pre-existing problems from the patient's Problem List can be selected on this
tab.
2) The scheduling checkout process, in which case the information collected about the POV is limited to the ICD Diagnosis code.
The Provider Narrative becomes the ICD long description from the ICD Diagnosis file.
3) Encounters created by other packages using the API DATA2PCE^PXAPI. If the Provider Narrative is not passed it defaults to the
ICD Long Description.
DD ACCESS:
RD ACCESS:
WR ACCESS:
DEL ACCESS:
LAYGO ACCESS:
AUDIT ACCESS:
IDENTIFIED BY: PATIENT NAME (#.02)[R], VISIT (#.03)[R]
POINTED TO BY: PURPOSE OF VISIT field (#.03) of the TIU PROBLEM LINK File (#8925.9)
CROSS
REFERENCED BY: VISIT(AA), PATIENT NAME(AATOO), VISIT(AD), VISIT(AV10), POV(B), PATIENT NAME(C)
INDEXED BY: POV & PATIENT NAME & VISIT & PRIMARY/SECONDARY & OP (ACR)
LAST MODIFIED: MAY 4,2021@15:57:23
9000010.07,.01POV 0;1 POINTER TO ICD DIAGNOSIS FILE (#80) (Required)
INPUT TRANSFORM: S:$D(APCDEIN) APCDTPCC="" S DIC("S")="D ^AUPNSICD" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
LAST EDITED: SEP 18, 2018
HELP-PROMPT: Enter the ICD Diagnosis code or text for the problem treated at the encounter.
DESCRIPTION: POV is an abbreviation for "Purpose of Visit". Since Purpose of Visit is often confused with "Chief
complaint", another abbreviation might better be "Problem of Visit". This is the Provider's
conclusion about what was treated at the visit. The Provider should be able to indicate a preferred
narrative for what was treated and an ICD Diagnosis code. If the problem treated is from the
Problem List, then the Problem List entry information can be used for the "Problem of Visit" entry.
At VA facilities, the ICD Diagnosis is screened by Inactive Code and it must be appropriate for the
Patient's age and sex.
At IHS facilities, the ICD Diagnosis is screened by Inactive Code, appropriate for the Patient's
age and sex, and Not "E" codes.
TECHNICAL DESCR: This is a pointer to the ICD Diagnosis file, #80.
SCREEN: S DIC("S")="D ^AUPNSICD"
EXPLANATION: POV CANNOT BE AN INACTIVE CODE
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 9000010.07^B
1)= S ^AUPNVPOV("B",$E(X,1,30),DA)=""
2)= K ^AUPNVPOV("B",$E(X,1,30),DA)
RECORD INDEXES: ACR (#840)
9000010.07,.019ICD NARRATIVE ; COMPUTED
MUMPS CODE: S X="" I $T(SDESC^PXDXUTL)'="" S X=$$SDESC^PXDXUTL(D0)
ALGORITHM: S X="" I $T(SDESC^PXDXUTL)'="" S X=$$SDESC^PXDXUTL(D0)
LAST EDITED: FEB 13, 2012
DESCRIPTION: This is the computed diagnosis narrative that is defined in the ICD Diagnosis file for the ICD
Diagnosis code identified in the POV (.01) field.
9000010.07,.02PATIENT NAME 0;2 POINTER TO PATIENT/IHS FILE (#9000001) (Required)
LAST EDITED: OCT 23, 2018
HELP-PROMPT: Enter the name of the patient who had the POV treated.
DESCRIPTION: This is the patient whose problem or diagnosis was treated.
TECHNICAL DESCR: This is a pointer to the Patient/IHS file, #9000001, which is DINUMED to the Patient file, #2. This
field is always stuffed by the application. No editing is allowed.
UNEDITABLE
CROSS-REFERENCE: 9000010.07^AATOO^MUMPS
1)= I $P(^AUPNVPOV(DA,0),U,3)]"" S ^AUPNVPOV("AA",X,(9999999-$P(+^AUPNVSIT($P(^AUPNVPOV(DA,0),U,3),
0),".",1)),DA)=""
2)= I $P(^AUPNVPOV(DA,0),U,3)]"" K ^AUPNVPOV("AA",X,(9999999-$P(+^AUPNVSIT($P(^AUPNVPOV(DA,0),U,3),
0),".",1)),DA)
This cross-reference is used for searches in sequence by patient, inverted visit date, and internal
entry number.
"AA",PATIENT,VISIT,DA
CROSS-REFERENCE: 9000010.07^C
1)= S ^AUPNVPOV("C",$E(X,1,30),DA)=""
2)= K ^AUPNVPOV("C",$E(X,1,30),DA)
This cross-reference allows FileMan to look-up entries in the file for a patient.
RECORD INDEXES: ACR (#840)
9000010.07,.03VISIT 0;3 POINTER TO VISIT FILE (#9000010) (Required)
INPUT TRANSFORM: S DIC("S")="I $P(^(0),U,5)=$P(^AUPNVPOV(DA,0),U,2)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
LAST EDITED: SEP 18, 2018
HELP-PROMPT: Enter the visit date/time for the encounter where the problem was treated.
DESCRIPTION: The encounter entry in the Visit file that is associated with this problem treated.
In IHS facilities, this is the date and time the visit occurred.
In VA facilities, this is the date and time of the clinic appointment for the patient in the
Scheduling package, or the date and time the encounter occurred if there was no appointment. By
using the appointment date and time, clinic activity can be captured for clinical use as well as be
used for billing and workload information by the appropriate VA packages. If the visit was a
walk-in, an appointment should be entered in Scheduling first so the clinical information can also
be used for the administrative uses.
Non-clinic appointment encounters can be entered, but the clinical POV information is not accepted
for billing.
The patient encounter can be the result of an inpatient encounter. In this case, the ward would be
specified as the hospital location in the Visit file.
TECHNICAL DESCR: This is a pointer to the Visit file, #9000010. This field is stuffed by the applications. No
editing is allowed.
SCREEN: S DIC("S")="I $P(^(0),U,5)=$P(^AUPNVPOV(DA,0),U,2)"
EXPLANATION: VISIT MUST BE FOR CURRENT PATIENT
UNEDITABLE
CROSS-REFERENCE: 9000010.07^AD
1)= S ^AUPNVPOV("AD",$E(X,1,30),DA)=""
2)= K ^AUPNVPOV("AD",$E(X,1,30),DA)
This cross-reference is used for searches by the visit pointer and internal entry number.
"AD",VISIT pointer value, DA
CROSS-REFERENCE: 9000010.07^AA^MUMPS
1)= Q:$P(^AUPNVPOV(DA,0),U,2)="" S ^AUPNVPOV("AA",$P(^AUPNVPOV(DA,0),U,2),(9999999-$P(+^AUPNVSIT(X
,0),".",1)),DA)=""
2)= Q:$P(^AUPNVPOV(DA,0),U,2)="" K ^AUPNVPOV("AA",$P(^AUPNVPOV(DA,0),U,2),(9999999-$P(+^AUPNVSIT(X
,0),".",1)),DA)
This cross-reference is used for searches in sequence by patient, inverted visit date (from the
Visit file) and the internal entry number.
"AA",PATIENT,inverted VISIT,DA
CROSS-REFERENCE: 9000010.07^AV10^MUMPS
1)= D ADD^AUPNVSIT
2)= D SUB^AUPNVSIT
This cross-reference adds and subtracts from the dependent entry count in the VISIT file.
RECORD INDEXES: ACR (#840)
9000010.07,.04PROVIDER NARRATIVE 0;4 POINTER TO PROVIDER NARRATIVE FILE (#9999999.27) (Required)
INPUT TRANSFORM: S DIC(0)=$S($D(PXKLAYGO):"LOX",$D(APCDALVR):"LO",$D(ZTQUEUED):"LO",1:"EMQLO") D ^DIC K DIC S DIC=DI
E,X=+Y K:Y<0 X
LAST EDITED: OCT 23, 2018
HELP-PROMPT: Enter the provider's preferred text identifying the diagnosis treated at the encounter.
DESCRIPTION: This is the provider's text describing the diagnosis that was treated at the visit. The text may
contain additional information related specifically, to the patient at the time of the visit (e.g.,
hypertension, uncontrolled). The provider's narrative may be different from the ICD Diagnosis files
description for a code, but should not have a significantly different meaning. The ICD Diagnosis
code in the POV (.01) field should be the code that "most closely" represents the providers
narrative.
In IHS facilities, this narrative is entered by data entry clerks.
In VA facilities, this narrative may be entered manually or derived from: 1) the ICD Diagnosis text
from the ICD Diagnosis file (Scheduling interface) 2) the text defined on Encounter Forms when
defining the most common diagnosis treated for a clinic (AICS or other automated data capture) 3)
the Problem List entries' "provider narrative", captured from the Active Problem List being checked
off for problems treated at the encounter on an Encounter Form (AICS or other automated data
capture).
TECHNICAL DESCR: This is a pointer to the Provider Narrative file, #9999999.27. Disk space is saved by storing one
entry in the Provider Narrative file for each unique narrative. The provider narrative is often
repetitive, especially, if the data capture mode is automated.
The resulting entries in the Provider Narrative file builds a file of preferred provider
terminology.
9000010.07,.06MODIFIER 0;6 SET
'C' FOR CONSIDER;
'D' FOR DOUBTFUL;
'F' FOR FOLLOW UP;
'M' FOR MAYBE, POSSIBLE, PERHAPS;
'O' FOR RULE OUT;
'P' FOR PROBABLE;
'R' FOR RESOLVED;
'S' FOR SUSPECT, SUSPICIOUS;
'T' FOR STATUS POST;
LAST EDITED: SEP 18, 2018
HELP-PROMPT: Enter the provider's modifier of the diagnosis treated.
DESCRIPTION: (Optional) This is how a provider may modify the diagnosis or problem treated to reflect the status
of the diagnosis as of this visit. Common examples of modifiers are Rule Out, Follow-up, or Status
Post.
TECHNICAL DESCR: The VA uses a smaller set of modifiers than the IHS does. The file is distributed with the complete
set of codes originally defined by the Indian Health Service.
SCREEN: S:DUZ("AG")="V" DIC("S")="I ""FOT""[Y"
EXPLANATION: VA screens for Rule Out, Follow Up, and Status Post
SOURCE OF DATA: 061/DISPEC
9000010.07,.12PRIMARY/SECONDARY 0;12 SET
'P' FOR PRIMARY;
'S' FOR SECONDARY;
LAST EDITED: SEP 18, 2018
HELP-PROMPT: Enter the clinically pertinent ranking for this problem treated.
DESCRIPTION: This field represents the clinically pertinent ranking of problems treated. An encounter can have
only one primary diagnosis, all others are secondary.
SOURCE OF DATA: 061/DIPRIME
RECORD INDEXES: ACR (#840)
9000010.07,.13DATE OF INJURY 0;13 DATE
INPUT TRANSFORM: S %DT="EST" D ^%DT S X=Y K:Y<1 X
LAST EDITED: NOV 16, 2018
HELP-PROMPT: Enter the date and optional time of the injury.
DESCRIPTION: This is the date and optional time the injury occurred for the problem being treated, it must be
prior to the Visit Date and Time.
At VA facilities, Date of Injury is prompted for when the ICD diagnosis code is considered to be an
injury code. For ICD-9, this is when the code lies in the range 800-999.999. For ICD-10, this is
when the code starts with an 'S' or 'T'.
9000010.07,.15CLINICAL TERM 0;15 POINTER TO EXPRESSIONS FILE (#757.01)
LAST EDITED: SEP 18, 2018
HELP-PROMPT: Enter the provider narrative or clinical terminology for the diagnosis treated.
DESCRIPTION: This field is the Clinical Lexicon term which most closely represents the Provider Narrative of the
problem treated.
At VA facilities: The Clinical Lexicon is automatically captured via encounter form data capture
(AICS package) when the problem being treated is from the Active Problem List. In the manual data
entry process, there is currently no prompt for the clinical term.
TECHNICAL DESCR: This field was created by the VA to capture the Clinical Lexicon term, as an alternative to, or in
addition to the ICD Diagnosis code. This field will primarily be populated when the diagnosis being
treated at a visit is based on an entry in the Active Problem List.
9000010.07,.16PROBLEM LIST ENTRY 0;16 POINTER TO PROBLEM FILE (#9000011)
LAST EDITED: SEP 18, 2018
HELP-PROMPT: Enter the problem entry from the patient's problem list for the problem treated.
DESCRIPTION:
This field identifies what Problem List entry is related to the problem treated at the visit.
TECHNICAL DESCR: This field was added for use by PCE in the VA.
Automated data capture methods, that allow the problems treated at a visit to be selected from the
active problem list, will be able to provide the Problem List entry which is stored in this field.
9000010.07,.17ORDERING/RESULTING 0;17 SET
'O' FOR ORDERING;
'R' FOR RESULTING;
'OR' FOR BOTH O&R;
LAST EDITED: FEB 17, 2004
HELP-PROMPT: Enter O if the diagnosis is an ordering diagnosis, enter R if the diagnosis is a resulting
diagnosis and enter B if the diagnosis is used for both ordering and resulting.
DESCRIPTION:
This field identifies a diagnosis as being Ordering, Resulting, or both Ordering and Resulting.
TECHNICAL DESCR: Ordering diagnoses are used for facility charges in billing, resulting diagnoses are used in
professional services billing.
9000010.07,1201OP 12;1 DATE
INPUT TRANSFORM: S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: DEC 15, 2020
HELP-PROMPT: Enter the date and time this diagnosis was given.
DESCRIPTION: This is the date and time the diagnosis was given. This date and time may be different from the
visit date and time. For example, for clinic appointment visits, the Visit Date and Time is the
date and time of the appointment, not the time the provider performed the clinical event.
The date may be an imprecise date.
Date and time may be before or after the Visit date, with the restriction the date cannot be a
future date.
TECHNICAL DESCR: This field was added for use by PCE in the VA, to support the capture of the actual event date and
time of the encounter which is not reflected in the Visit file entry. IHS allows the Visit Date and
Time to be the actual date and time. But, the VA uses the Visit date and time as the Appointment
date and time, rather than the "actual" encounter date and time. The Appointment Date and Time
orientation of Visits allows the VA Scheduling, Billing and Workload functionality to understand
the linkage between the clinical data being captured for a Visit and the existing Outpatient
Scheduled events.
RECORD INDEXES: ACR (#840)
9000010.07,1202ORDERING PROVIDER 12;2 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: MAY 13, 1996
HELP-PROMPT: Enter the ordering provider.
DESCRIPTION: For consistency, this field was added to each V-file. However, for the V POV, the Ordering
Provider does not apply itself well, unless a provider is ordering another provider to treat a
problem. Optionally, in the future, this field may be able to represent the provider responsible
for the encounter providers work.
9000010.07,1204ENCOUNTER PROVIDER 12;4 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: DEC 19, 1994
HELP-PROMPT: Enter the care giver who treated the problem.
DESCRIPTION:
This is the provider who treated the diagnosis at the encounter.
9000010.07,80001SERVICE CONNECTED 800;1 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If this problem treated is service connected, enter 'YES' here.
DESCRIPTION: This field is used in the VA to indicate that this problem treated at this visit was service
connected.
TECHNICAL DESCR: This field is used by the VA. The data is only passed to PCE from the automated data capture of
encounter form data when a Problem from the Active Problem list has been identified as the problem
treated at the visit. If the Problem List identified the Problem as Service Connected, then this
Service Connected field would be automatically set to 1.
9000010.07,80002AGENT ORANGE EXPOSURE 800;2 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If the problem treated is related to Agent Orange Exposure, enter 'YES' here.
DESCRIPTION: This field is used in the VA to indicate that this problem treated at this visit was related to
agent orange exposure.
TECHNICAL DESCR: This field is used by the VA. The data is only passed to PCE from the automated data capture of
encounter form data. If a problem from the Active Problem List is identified as the problem treated
at the visit, and the problem has been associated with Agent Orange Exposure in the Problem List,
then the POV's Agent Orange Exposure will be set to "1".
9000010.07,80003IONIZING RADIATION EXPOSURE 800;3 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If this problem treated is related to Ionizing Radiation Exposure, enter 'YES'.
DESCRIPTION: This field is used in the VA to indicate that this problem treated at this visit was related to
ionizing radiation exposure.
TECHNICAL DESCR: This field is used by the VA. The data is only passed to PCE from the automated data capture of
encounter form data. If a problem on the Active Problem List is identified as a problem treated at
the visit, and the problem is defined as related to ionizing radiation exposure, then the POV
Ionizing Radiation Exposure will be set to "1".
9000010.07,80004SW ASIA CONDITIONS 800;4 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If this problem treated is related to SW Asia Conditions exposure, enter 'YES' here.
DESCRIPTION: This field is used in the VA to indicate that this problem treated at this visit was related to
Southwest Asia Conditions exposure.
TECHNICAL DESCR: This field is only passed to PCE from the automated data capture of encounter form data. If a
problem on the Active Problem List is identified as the problem treated at the visit, and the
problem defined as being related to Southwest Asia Conditions Exposure in the Problem List, then
the POV Southwest Asia Conditions Exposure will automatically be set to "1".
9000010.07,80005MILITARY SEXUAL TRAUMA 800;5 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If this diagnosis code is related to Military Sexual Trauma, enter 'YES' here.
DESCRIPTION: This field will be used to indicate if this diagnosis code was related to a Military Sexual Trauma
problem.
9000010.07,80006HEAD AND/OR NECK CANCER 800;6 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If this diagnosis code is related to Head/Neck Cancer, enter 'YES'.
DESCRIPTION: This field will be used to indicate if this diagnosis code was related to Head and/or Neck Cancer.
9000010.07,80007COMBAT VETERAN 800;7 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If this visit is treating a problem related to combat, enter 'YES'.
DESCRIPTION: This field is used to indicate that the visit represents treatment of a VA patient for a problem
that is related to combat.
TECHNICAL DESCR:
9000010.07,80008PROJ 112/SHAD 800;8 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: If this visit is treating a problem related to PROJ 112/SHAD, enter 'YES'.
DESCRIPTION: Project 112/SHAD was the name of the overall program for both shipboard and land-based biological
and chemical testing that was conducted by the United States (U.S.) military between 1962 and 1973.
Project SHAD (Shipboard Hazard and Defense) was the shipboard portion of these tests.
9000010.07,80101EDITED FLAG 801;1 SET
'1' FOR EDITED;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: Enter 1 if any data has been edited.
DESCRIPTION: This field is automatically set to 1 if PCE detects that any data in the V POV entry has been
edited.
TECHNICAL DESCR: PCE filing logic automatically compares the before and after pictures of the record to determine if
the edited flag should be set to "1".
9000010.07,80102AUDIT TRAIL 801;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>85!($L(X)<2) X
LAST EDITED: MAY 09, 1996
HELP-PROMPT: Answer must be 2-85 characters in length.
9000010.07,80201PROVIDER NARRATIVE CATEGORY 802;1 POINTER TO PROVIDER NARRATIVE FILE (#9999999.27)
INPUT TRANSFORM: S DIC(0)=$S($D(PXKLAYGO):"LOX",$D(APCDALVR):"LO",$D(ZTQUEUED):"LO",1:"EMQLO") D ^DIC K DIC S DIC=DI
E,X=+Y K:Y<0 X
LAST EDITED: APR 21, 1994
HELP-PROMPT: Enter the category narrative related to this problem treated.
DESCRIPTION:
This field is the category narrative related to the problem treated.
TECHNICAL DESCR: This field is used by the VA when capturing encounter form information via scanning (e.g., such as
AICS scanning) or workstation data capture methods. This field is used to document how providers
group the clinical terminology being used to document encounters. Providers may group the problems
which may be selected under specific headers on the encounter form definition. This field is used
to store the actual header text used by the provider.
SCREEN: S DIC(0)=$S($D(PXKLAYGO):"LOX",$D(APCDALVR):"LO",$D(ZTQUEUED):"LO",1:"EMQLO")
EXPLANATION: OLD LOOKUP
9000010.07,81101COMMENTS 811;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>245!($L(X)<1) X
LAST EDITED: JUL 11, 1995
HELP-PROMPT: Answer must be 1-245 characters in length.
9000010.07,81201VERIFIED 812;1 SET
'1' FOR ELECTRONICALLY SIGNED;
'2' FOR VERIFIED BY PACKAGE;
LAST EDITED: OCT 23, 2018
HELP-PROMPT: Enter 1 if electronically signed, 2 if verified by Package.
TECHNICAL DESCR: This field is uneditable.
UNEDITABLE
9000010.07,81202PACKAGE 812;2 POINTER TO PACKAGE FILE (#9.4)
LAST EDITED: OCT 23, 2018
HELP-PROMPT: Enter the Package associated with this V POV entry.
TECHNICAL DESCR: This field is uneditable.
UNEDITABLE
9000010.07,81203DATA SOURCE 812;3 POINTER TO PCE DATA SOURCE FILE (#839.7)
LAST EDITED: OCT 23, 2018
HELP-PROMPT: Enter the Data Source associated with this V POV entry.
TECHNICAL DESCR: This field is uneditable.
UNEDITABLE
FILES POINTED TO FIELDS
EXPRESSIONS (#757.01) CLINICAL TERM (#.15)
ICD DIAGNOSIS (#80) POV (#.01)
NEW PERSON (#200) ORDERING PROVIDER (#1202)
ENCOUNTER PROVIDER (#1204)
PACKAGE (#9.4) PACKAGE (#81202)
PATIENT/IHS (#9000001) PATIENT NAME (#.02)
PCE DATA SOURCE (#839.7) DATA SOURCE (#81203)
PROBLEM (#9000011) PROBLEM LIST ENTRY (#.16)
PROVIDER NARRATIVE (#9999999.27) PROVIDER NARRATIVE (#.04)
PROVIDER NARRATIVE CATEGORY (#80201)
VISIT (#9000010) VISIT (#.03)
File #9000010.07
Record Indexes:
ACR (#840) RECORD MUMPS IR ACTION
Short Descr: Clinical Reminders index.
Description: This cross-reference builds two indexes, one for finding all patients with a specific diagnosis code and one
for finding all the diagnosis codes a patient has.
For ICD-9 codes the indexes are stored in the Clinical Reminders Index global as:
^PXRMINDX(9000010.07,"IPP",ICD IEN,PS,DFN,DATE,DAS) and
^PXRMINDX(9000010.07,"PPI",DFN,PS,ICD IEN,DATE,DAS) respectively.
For ICD-10 codes the indexes are stored in the Clinical Reminders Index global as:
^PXRMINDX(9000010.07,CODING SYSTEM,"IPP",CODE,PS,DFN,DATE,DAS) and
^PXRMINDX(9000010.07,CODING SYSTEM,"PPI",DFN,PS,CODE,DATE,DAS)
Where
CODING SYSTEM is the Lexicon package's standard abbreviation for the coding system. For ICD-10 it is 10D.
ICD IEN is the internal entry number of the code in file #80.
CODE is the ICD-10 code.
PS is the primary/secondary code. Possible values are P (primary), S (secondary) or U (undefined).
DFN is a pointer to file #2.
DATE is EVENT DATE AND TIME, if it exists. If it does not, then it is VISIT/ADMIT DATE&TIME.
DAS is the internal entry number of the entry in file #9000010.07.
For all the details, see the Clinical Reminders Index Technical Guide/Programmer's Manual.
Set Logic: D SVFILEC^PXPXRM(9000010.07,.X,.DA)
Kill Logic: D KVFILEC^PXPXRM(9000010.07,.X,.DA)
Whole Kill: K ^PXRMINDX(9000010.07)
X(1): POV (9000010.07,.01) (Subscr 1) (forwards)
X(2): PATIENT NAME (9000010.07,.02) (Subscr 2) (forwards)
X(3): VISIT (9000010.07,.03) (Subscr 3) (forwards)
X(4): PRIMARY/SECONDARY (9000010.07,.12)
X(5): OP (9000010.07,1201) (forwards)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
ONC DISEASE INDEX OCT 06, 2015@11:56 USER #0 DISEASE INDEX
SORT TEMPLATE(S):
ONC DISEASE INDEX JUN 30, 2000@10:37 USER #0
SORT BY: 'VISIT// (User is asked range)
WITHIN VISIT, SORT BY: 'POV// (User is asked range)
WITHIN POV, SORT BY: PATIENT NAME// (PATIENT NAME not null)
ONC DISEASE INDEX CASEFINDING APR 08, 2010@14:22 USER #0
SORT BY: 'VISIT// (User is asked range)
WITHIN VISIT, SORT BY: PATIENT NAME// ( PATIENT NAME not null)
FORM(S)/BLOCK(S):