{"aaData": [["VA-BMI", "
PXRMBMI
\n", "
BMI
\n", "
VA-Body Mass Index
\n", "
\nThe VA-BMI computed finding calculates the patient's body mass index. The\ngreater than 25.\n\nThis is a multi-occurrence computed finding.\n\n\n\n\nvalue returned, which can be used in the CONDITION field of the findings, is\nthe body mass index.\n \nAn example of using the VA-BMI computed finding:\n1)  Create a finding in a reminder that is the VA-BMI computed finding;\n2)  Add logic in the CONDITION field to check for a particular BMI value:\n"I V>25";\n3)  This finding will be evaluated to true for patients with a BMI that is\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-ADMISSIONS FOR A DATE RANGE", "
PXRMINPL
\n", "
ADM
\n", "
VA-Admissions for a Date Range
\n", "
\nThis list type computed finding can be used to build a list of\nfollowing CSUB subscripts:\n\nV or V("VALUE") = the ward to which the patient was admitted\n                  in the format of 9;3EAST (IEN;Ward Name)\n\nV("INSTITUTION") = the name of the INSTITUTION (file #4) entry \n                   with which the ward is associated in the format \n                   5000;ELY;660GC (IEN;Institution Name;Station Number) \n\nV("TYPE_OF_MVMT") = the type of movement entry from file 405.1\npatients who were admitted in the specified date range. A Reminder\n                    (e.g., REGULAR, OPT-NSC, OPT-SC, etc.)\n\n\n\n\n\n\n\n\n\nLocation List can be used to restrict the selection of patients to\nonly the ward locations included in the location list. To do this\nenter the exact .01 name of a Reminder Location List into the \nCOMPUTED FINDING PARAMETER field. If a Reminder Location List is not\nused then all ward locations will be included.\n\nThe CONDITION field may also be used to select entries by any of the\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", "
NO
\n"], ["VA-PATIENT TYPE", "
PXRMPDEM
\n", "
PATTYPE
\n", "
VA-Patient Type
\n", "
\nThis computed finding is a single value computed finding. If a patient type \n   ALLIED VETERAN   \n   COLLATERAL   \n   EMPLOYEE   \n   MILITARY RETIREE   \n   NON-VETERAN (OTHER)   \n   NSC VETERAN   \n   SC VETERAN   \n   TRICARE\nis found for the patient the computed finding will be true and type will be \nreturned as the Value.\n\nExample: I V="ACTIVE DUTY"\n\n\nPossible Values that can be returned from this computed finding are:\n   ACTIVE DUTY   \n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
SINGLE
\n", ""], ["VA-ETHNICITY", "
PXRMPDEM
\n", "
ETHNY
\n", "
VA-Patient's Ethnicity
\n", "
\nThis multiple occurrence computed finding will return the patient's\nethnicity values from the Patient file. If none are recorded then the\ncomputed finding will be false. This computed finding does not support date\nreversal.\n\nThe value of the computed finding that can be used in the Condition is\nthe patient's ethnicity.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-RACE 2003", "
PXRMPDEM
\n", "
NEWRACE
\n", "
VA-Patient's Race, 2003 and On.
\n", "
\nThis multiple occurrence computed finding returns entries from the Race\n  * ASIAN\n  * BLACK OR AFRICAN AMERICAN\n  * NATIVE HAWAIIAN OR OTHER PACIFIC ISLANDER\n  * WHITE\n  * DECLINED TO ANSWER\nInformation multiple of the Patient file. Patch DG*5.3*415, compliance\ndate January 31, 2003, made the Race field obsolete and replaced it\nwith the Race Information multiple.  The possible values are limited to\nthe nationally approved/supported races, which are:\n\n  Nationally Approved/Supported Races\n  -----------------------------------\n  * AMERICAN INDIAN OR ALASKA NATIVE\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-APPOINTMENTS FOR A PATIENT", "
PXRMRDI
\n", "
PAPPL
\n", "
VA-Appointments for a Patient
\n", "
\nThis multiple occurrence computed finding returns a list of\nspecific statuses, and LL: to specify a Reminder Location List \n    CCR    CANCELLED BY CLINIC, RESCHEDULED \n    NT     NO ACTION TAKEN\n\nIf STATUS is not specified, the default is R,I.\n\nThe APPOINTMENT STATUS returned by the API is a summarized list\nwhich does not include detailed statuses such as Future, Checked-In,\nor Checked Out. These  statuses are summarized as SCHEDULED/KEPT. \nAs a result, a CONDITION may be required to make sure you are\ngetting the correct results. For example, if you are looking for an\nto filter locations.  \nappointment that was kept, you would set STATUS:R combined with a\nCONDITION of I (+V("OUTPATIENT ENCOUNTER IEN")>0)!(+V("CHECK-OUT\nDATE/TIME")>0) with USE STATUS/COND IN SEARCH set to YES.\n\nLL information:\nLL:Reminder Location List specifies a list of locations so that only\nappointments for those locations will be returned. If LL is not\nspecified, then appointments for all locations will be returned.\n\n\n\nFLDS, STATUS, and LL are all optional and can be defined in any \norder in the computed finding parameter field.\nSome examples of how to use FLDS, STATUS and/or LL:\n  FLDS:1,2,16^STATUS:R^LL:DIABETIC LOCATIONS\n  STATUS:CP,CC^FLDS:25\n  LL:DIABETIC LOCATION\n\nappointments for a patient in the specified date range from \nFLDS parameter information:\nThe appointment data fields are specified as follows:  \nFLDS:F1,F2,... where F1,F2,... are any of the possible ID values\nlisted in the Available Appointment Data Fields table below.\nThe F1,F2,... ID values specify what data associated with the \nappointment will display in the clinical maintenance output. \nIf no FLDS is specified, the default display fields will be 1,2\nfor APPOINTMENT DATE/TIME and CLINIC. \n\nAdditionally, each F1,F2,... specified will be returned as CSUB \nthe Scheduling Package. \ndata that can also be used in the computed finding's CONDITION\nfield. The CONDITION can be used to further screen the filtered\nappointments, returned by Scheduling, by setting the USE STATUS/COND\nIN SEARCH field to YES. \n\nFor example, if you only want appointments that were checked out, \nuse FLDS: 1,2,11 to get the APPOINTMENT DATE/TIME, CLINIC, and \nCHECK-OUT DATE/TIME for display purposes. The FLDS:1,2,11 will\nreturn the CSUB data "APPOINTMENT DATE/TIME", "CLINIC" and \n"CHECK-OUT DATE/TIME".\n\n\nCSUB values are used in the CONDITION field to do a comparison to\nnumeric or string values. Using +V causes the CSUB data to be\ninterpreted as numeric. Strings that cannot be converted to a\nnumber are set to zero. For example, a CONDITION such as I\n+V("CHECK-OUT DATE/TIME")>0 would be true if the appointment had a\ncheck-out date/time.\n\nList of Available Appointment Data Fields table with assigned ID\n    ID      Field Name\nThe Computed Finding Parameter can be used to specify which \n--------------------------------------------------------\n\n     1     APPOINTMENT DATE/TIME\n     2     CLINIC\n     3     APPOINTMENT STATUS     \n     4     PATIENT\n     5     LENGTH OF APPOINTMENT\n     6     COMMENTS\n     7     OVERBOOK\n     8     ELIGIBILITY OF VISIT\nappointment data fields should be returned from the Scheduling \n     9     CHECK-IN DATE/TIME\n    10     APPOINTMENT TYPE\n    11     CHECK-OUT DATE/TIME\n    12     OUTPATIENT ENCOUNTER IEN\n    13     PRIMARY STOP CODE\n    14     CREDIT STOP CODE\n    15     WORKLOAD NON-COUNT\n    16     DATE APPOINTMENT MADE\n    17     DESIRED DATE OF APPOINTMENT\n    18     PURPOSE OF VISIT and SHORT DESCRIPTION\npackage and filter the results returned based on location \n    19     EKG DATE/TIME\n    20     X-RAY DATE/TIME\n    21     LAB DATE/TIME\n    22     STATUS\n    23     X-RAY FILMS\n    24     AUTO-REBOOKED APPOINTMENT DATE/TIME\n    25     NO-SHOW/CANCEL DATE/TIME\n    26     RSA APPOINTMENT ID\n    28     DATA ENTRY CLERK\n    29     NO-SHOW/CANCELED BY\nand status. The Computed Finding Parameter entry uses\n    30     CHECK-IN USER\n    31     CHECK-OUT USER\n    32     CANCELLATION REASON\n    33     CONSULT LINK\n\nSTATUS information:\nSTATUS: is used to set a filter on the appointment status; only\nthose appointments with a status that matches the STATUS: values\nlist will be returned. The possible values that the Scheduling\nAPI allows are:\nFLDS: to specify appointment data fields, STATUS: to filter \n\nVALUE     Description \n--------------------------------------------------------\n    R      SCHEDULED/KEPT\n    I      INPATIENT\n    NS     NO-SHOW\n    NSR    NO-SHOW, RESCHEDULED\n    CP     CANCELLED BY PATIENT\n    CPR    CANCELLED BY PATIENT, RESCHEDULED\n    CC     CANCELLED BY CLINIC\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", "
NO
\n"], ["VA-WH PAP SMEAR IN WH PKG", "
PXRMCWH
\n", "
PAP
\n", "
VA-Pap Smear in WH pkg
\n", "
\nThis computed finding calls an API to the WH package that returns up to n \nDATA(n,"WVIEN")=\n\nThe data assigned to the Link subscript is a Boolean value. If the value is \na 1, then the Pap smear procedure was entered through the Radiology package.\n\nThe data assigned to the Status subscript is used to determine if the \nprocedure is Open, Closed, or Pending. Pending means that the Pap smear \nprocedure in the Women's Health package needs to have a result entered. Open \nmeans that the Pap smear procedure has been resulted but the provider has \nnot closed the case. Closed means that a result has been entered for the \nnumber for a specific date range of Pap smear procedures found in the WH \nprocedure and it has been closed.\n\nThe data assigned to the Value subscript is used to determine diagnosis of \nthe Pap smear procedure. The diagnosis in the Women's Health package can \neither be Normal, Abnormal, or Unsatisfactory.\n\nThe data assigned to the WVIEN subscript is the Women's Health procedure \nIEN.\n\nThe text display in the Clinical Maintenance will be found in the Text \npackage.\narray.\n\nThe result from the computed finding will be returned in the Data Array; the \nformat of the array is:\nDATA(n,"LINK")=\nDATA(n,"STATUS")=\nDATA(n,"VALUE")=\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-ARCH REMINDER CUSTOM DUE DATE", "
PXRMARCH
\n", "
ISDUE
\n", "
VA-ARCH Reminder Custom Due Date
\n", "
\nThis multi-occurrence computed finding returns the date the Project ARCH \nReminder will be due based on the delay value for the Project ARCH\nClinical Reminder and the last time the patient declined or refused\nservices.\n
\n
\n", "
NATIONAL
\n", "
VHA OFFICE OF THE ASSISTANT DEPUTY UNDER SECRETARY FOR HEALTH FOR POLICY AND PLANNING
\n", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-WH MAMMOGRAM IN WH PKG", "
PXRMCWH
\n", "
MAM
\n", "
VA-Mammogram in WH pkg
\n", "
\nThis computed finding calls an API to the WH package that returns up to n \nDATA(n,"WVIEN")=\n\nThe data assigned to the Link subscript is a boolean value. If the value is \na 1, then the Mammogram procedure was entered through the Radiology package.\n\nThe data assigned to the Status subscript is used to determine if the \nprocedure is Open, Closed, or Pending. Pending means that the Mammogram \nprocedure in the Women's Health package needs to have a result entered. Open \nmeans that the Mammogram procedure has been resulted but the provider has \nnot closed the case. Closed means that a result has been entered for the \nnumber for a specific date range of Mammogram procedures found in the WH \nprocedure and it has been closed.\n\nThe data assigned to the Value subscript is used to determine the diagnosis \nof the Mammogram procedure. The diagnosis in the Women's Health package can \nbe either Normal, Abnormal, or Unsatisfactory. \n\nThe data assigned to the WVIEN subscript is the Women's Health procedure \nIEN.\n\nThe text display in the Clinical Maintenance will be found in the Text \npackage.\narray.\n\nThe results from the computed finding will be returned in the Data Array; \nthe format of the array is:\nDATA(n,"LINK")=\nDATA(n,"STATUS")=\nDATA(n,"VALUE")=\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-SEXUAL ORIENTATION", "
PXRMPDEM
\n", "
SEXOR
\n", "
Patient Sexual Orientation
\n", "
\nThis computed finding returns a list of a patient Sexual Orientations \n \nOr leave the computed finding parameters in-regardless of the Sexual \nOrientation status.\n \nOutput of the computed finding:\n \nVALUE("SEXUAL ORIENTATION DAS")=\nVALUE("SEXUAL ORIENTATION",N)= The external value of the Sexual \nOrientation value\nVALUE("SEXUAL ORIENTATION TYPE CODE",N)=The internal value of the Sexual \nthat are on file.\nOrientation value\nVALUE("SO STATUS")= The Sexual Orientation Status Value\nVALUE("OTHER DESCRIPTION")= Free Text value entered by the user or \npatient when selecting Other as a Sexual Orientation.\n \nThe following value are used by the Reminder Dialog Branching Logic and \nGeneral Finding functionality.\nVALUE("SEXUAL ORIENTATION DAS"),VALUE("DIALOG"),VALUE("PACKAGE"),\nVALUE("PACKAGE PREFIX")\n \nThe computed finding parameter field can be used to restrict the results \nto a certain Sexual Orientation Status value. The possible values are:\n \nA = for Active Sexual Orientations\nI = for Inactive Sexual Orientations\nE = for Sexual Orientation entries marked as Entered in Error\n
\n
\n", "
NATIONAL
\n", "
LGBTQ+ HEALTH PROGRAM
\n", "", "", "
MULTIPLE
\n", ""], ["VA-DATE OF BIRTH", "
PXRMPDEM
\n", "
DOB
\n", "
VA-Patient's Date of Birth
\n", "
\nThis is a single occurrence computed finding that returns the \npatient's date of birth as a FileMan date. It can be used as the value\nin the Condition. For example: I V>2850302. The date of the finding\nis the date of birth so that date range searches can be used to\nfind patients who were born in a certain time frame.\n \n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
SINGLE
\n", ""], ["VA-WH PATIENT DOCUMENTATION", "
PXRMCWH1
\n", "
DOCSTAT
\n", "
Women's Health Patient Documentation
\n", "
\nThis computed finding returns up to N number (within a specific date \n \n \nThe value assigned to the PREGNANCY LIKELIHOOD subscript is the \nlikelihood of the patient becoming pregnant while using the \ncontraceptives returned in the CONTRACEPTIVE METHOD USED subscript. This \nsubscript has a value of HIGH, LOW or UNKNOWN.\n \nThe value assigned to the LAST MENSTRUAL PERIOD DATE subscript is the \nstart date of the patient's last menstrual period.\n \nThe value assigned to the TWENTY-EIGHT WEEKS' GESTATION subscript is a \nThe second caret piece of the COMPUTED FINDING PARAMETER value is used to \ndate that is 12 weeks before the date in the EDD subscript.\n \nThe value assigned to the EDD subscript is the expected due date.\n \nThe value assigned to the EDD-GRACE subscript is the end date of the EDD \ngrace period. When a patient's EDD is in the past and there is no updated \ndocumentation on file, there is a grace period after which the system \nwill no longer consider the patient pregnant even though the \ndocumentation is not updated.\n \nidentify this finding's return data for use in the VA-WH UPDATE PREGNANCY \nThe value assigned to the OVERRIDE CALCULATED EDD REASON subscript is the \ntext entered by the provider in the VA-WH UDPATE PREGNANCY STATUS \nreminder dialog for why the expected due date was changed from the \ncalculated value.\n \nThe value assigned to the PREGNANCY END DATE subscript is the date the \npatient's pregnancy ended.\n \nThe value assigned to the REASON PREGNANCY ENDED subscript is the text \nentered by the provider in the VA-WH UPDATE PREGNANCY STATUS reminder \nSTATUS and VA-WH UPDATE LACTATION STATUS reminder dialogs. Setting this \ndialog for why the pregnancy ended.\n \nThe value assigned to the END DATE subscript is the date the patient \nstopped lactating.\n \nThe value assigned to the PREGNANCY DAS and the LACTATION DAS subscripts \nis the Internal Entry Number String (IENS) value identifying the record \nin the Women's Health software package from which this status data came.\n \nThe value assigned to the PREGNANCY DATA SOURCE and the LACTATION DATA \npiece to DATA will identify it.\nSOURCE subscripts is the entry in the PACKAGE file of the software \npackage that collected the status data from the end user.\n \nThe value assigned to the DATE/TIME subscript is the date and time the \nstatus was entered. Note that the DATE subscript does not contain the \ntime.\n \nThe value assigned to the DOCUMENTATION STATUS subscript is the \ncompleteness of the documentation. This subscript has a value of \nCOMPLETE, INCOMPLETE or NO DOCUMENTATION.\n \n \nThe value assigned to the VISIT subscript is the Text Integration \nUtilities (TIU) visit string value representing the entry in the VISIT \nfile associated with this status.\n \nThe value assigned to the DIALOG subscript is 1 and is part of the \nidentifier used to differentiate a specific instance of this finding for \nuse by the VA-WH UDPATE PREGNANCY STAUTS and VA-WH UPDATE LACTATION \nSTATUS reminder dialogs.\n \nThe third caret piece of the COMPUTED FINDING PARAMETER value is used to \nThe value assigned to the PACKAGE subscript is the name of the software \npackage from which the finding's data comes from; this value is WOMEN'S \nHEALTH.\n \nThe value assigned to the PACKAGE PREFIX subscript is the prefix for the \nsoftware package from which the finding's data comes from; this value is \nWV.\ncalculate the grace period during which a patient is considered pregnant. \nThe grace period begins on the expected delivery date and ends on the \ndate calculated from this piece. The format of this piece is NX where N \nrange) of pregnancy or lactation statuses found in the Women's Health \nis a whole number greater than zero and X is a letter representing an \ninterval of time (Y for year, M for month, W for week, D for day and H \nfor hour). If this piece is blank, four weeks ("4W") will be used to \ncalculate the grace period. This piece is only applicable when the first \ncaret piece is set to PREGNANCIES.\n \nFor example, \n  COMPUTED FINDING PARAMETER: PREGNANCIES^DATA^3W\n \nThis finding will always return true, even when no documentation is on \nsoftware package.\nfile. Refer to the DOCUMENTATION STATUS CSUB subscript to determine \nwhether documentation is on file.\n \nThe CONDITION field may make use of the following CSUB subscripts when \nthe first caret piece of the COMPUTED FINDING PARAMETER is set to \nPREGNANCIES: \n  V(N,"MEDICALLY UNABLE TO CONCEIVE")=\n  V(N,"MEDICAL REASON")=\n  V(N,"TRYING TO BECOME PREGNANT")=\n  V(N,"PREGNANCY STATE")=\n \n  V(N,"PREGNANCY DAS")=\n  V(N,"PREGNANCY DATA SOURCE")=\n  V(N,"CONTRACEPTIVE METHOD USED",X)=\n  V(N,"PREGNANCY LIKELIHOOD")=\n  V(N,"LAST MENSTRUAL PERIOD DATE")=\n  V(N,"EDD")=\n  V(N,"EDD-GRACE")=\n  V(N,"PREGNANCY END DATE")=\n  V(N,"REASON PREGNANCY ENDED")=\n  V(N,"OVERRIDE CALCULATED EDD REASON")=\nTo retrieve pregnancy statuses, set the first caret piece of the COMPUTED \n  V(N,"TWENTY-EIGHT WEEKS' GESTATION")=\n \nThe CONDITION field may make use of the following CSUB subscripts when \nthe first caret piece of the COMPUTED FINDING PARAMETER is set to \nLACTATIONS:\n  V(N,"LACTATION STATE")=\n  V(N,"LACTATION DAS")=\n  V(N,"LACTATION DATA SOURCE")=\n  V(N,"END DATE")=\n \nFINDING PARAMETER value to PREGNANCIES.\nThe CONDITION field may make use of the following CSUB subscripts when \nthe first caret piece of the COMPUTED FINDING PARAMETER is set to \nPREGNANCIES or LACTATIONS:\n  V(N,"DATE/TIME")=\n  V(N,"DOCUMENTATION STATUS")=\n  V(N,"VISIT")=\n \nThe CONDITION field may make use of the following CSUB subscripts when \nthe second caret piece of the COMPUTED FINDING PARAMETER is set to DATA \nand the first caret piece is set to PREGNANCIES or LACTATIONS:\n \n  V(N,"DIALOG")=\n  V(N,"PACKAGE")=\n  V(N,"PACKAGE PREFIX")=\n \nWhen retrieving pregnancy statuses, the value assigned to the PREGNANCY \nSTATE subscript is used to determine if the patient is pregnant and is \none of PREGNANT, NOT PREGNANT or DO NOT KNOW. When retrieving lactation \nstatuses, the value assigned to the LACTATION STATE subscript is used to \ndetermine if the patient is lactating and is one of LACTATING or NOT \nLACTATING.\nTo retrieve lactation statuses, set the first caret piece of the COMPUTED \n \nThe value assigned to the MEDICALLY UNABLE TO CONCEIVE subscript is used \nto determine if a patient is medically able to conceive and is one of YES \nor NO. Keep in mind that the values of this subscript are opposite of \nwhat you may think: a value of NO means the patient is medically able to \nconceive.\n \nThe value assigned to the MEDICAL REASON subscript is the text entered by \nthe provider for why the patient is medically unable to conceive.\n \nFINDING PARAMETER value to LACTATIONS.\nThe value assigned to the TRYING TO BECOME PREGNANT field is used to \ndetermine if a patient is consciously trying to become pregnant and is \none of YES or NO.\n \nThe data assigned to the CONTRACEPTIVE METHOD USED subscript is the \nmethod(s) the patient is using to avoid pregnancy. This subscript \ncontains a numbered list that starts at one and increments by one. For \nexample:\n  V(N,"CONTRACEPTIVE METHOD USED",1)="MALE CONDOM"\n  V(N,"CONTRACEPTIVE METHOD USED",2)="PILL, VAGINAL RING OR PATCH"\n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "", "
MULTIPLE
\n", ""], ["VA-WH PAP SMEAR IN LAB PKG", "
PXRMCWH
\n", "
PAPSCR
\n", "
VA-Lab Pap Smear SNOMED
\n", "
\nThis computed finding pulls a list of Topography and Morphology codes that \npackage for a specific data range of procedures that match the topography \nand morphology codes.\n\nThe output of the computed finding will be returned in the Data array. The \nformat of the data array is:\n\nDATA(n,"TOPH")=\nDATA(n,"VALUE")=\nDATA(n,"MORP")=\nDATA(n,"RESULT STATUS")=\nare mapped to the Pap smear entry in the Women Health package. The Pap Smear \n\nThe data found in the TOPH subscript is the Topography code in the following \nformat: \nT-SNOMED CODE\n\nThe data found in the VALUE subscript is the Topography code in the \nfollowing format: \nT-SNOMED CODE SNOMED CODE DESCRIPTION\n\nThe data found in the MOPH subscript is the Morphology code in the following \nentry is defined in file #790.2 the WV Procedure Type file.\nformat: \nM-SNOMED CODE\n\nThe data found in the RESULT STATUS subscript is the result that has been \nmapped to the Morphology code in the Women's Health package. The result will \neither be NEM, Abnormal, Unsatisfactory, or Unknown. \n\nThe text display in the Clinical Maintenance will be found in the Text \narray.\n\nThis computed finding requires that both the topography and morphology codes \nare mapped to the Pap smear procedure. The morphology codes must also have a \nresult assigned to them.\n\nThis computed search will return up to n number of entries found in the Lab \n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-PROGRESS NOTE", "
PXRMTIU
\n", "
NOTE
\n", "
VA-Progress Note
\n", "
\nThis computed finding will return multiple instances of a progress\n  2 = UNTRANSCRIBED\nnot longer than 255 characters).\n\n\n\n\n\n\n\n  3 = UNRELEASED\n  4 = UNVERIFIED\n  5 = UNSIGNED\n  6 = UNCOSIGNED\n  7 = COMPLETED\n  8 = AMENDED\n  9 = PURGED\n 10 = TEST\n 11 = ACTIVE\nnote based on the exact title of the TIU DOCUMENT DEFINTION or the\n 13 = INACTIVE\n 14 = DELETED\n 15 = RETRACTED\n\nIf status is not specified, then the default is to search for notes with\na status of COMPLETED.\n\nFor example, if the COMPUTED FINDING PARAMETER field contains:\n ADMITTING HISTORY & PHYSICAL^5\n\ninternal entry number (IEN) of the TIU DOCUMENT DEFINTION. If the\nthe search would be for notes with the exact title of "ADMITTING\nHISTORY & PHYSICAL" and a status of "UNSIGNED."\n\nIf the IEN were used then the COMPUTED FINDING PARAMETER filed would\nbe:\n `1091^5\n\nNote: The specified TIU DOCUMENT DEFINITION must have a TYPE of\n"DOC"; if it does not, the computed finding will always be false.\n\nIEN is used, it should be preceded by the "`" character. The note\nThe values returned by this computed finding that can be used in the\nCondition are V=note title, V("TITLE")=note title and\nV("AUTH")=author of note.\n\nAdditional data for use in the Condition can be obtained by\nappending "^1" after the status; for example:\n ADMITTING HISTORY & PHYSICAL^5^1\n ADMITTING HISTORY & PHYSICAL^^1\n\n(In the second example, since the status is blank, it would default to\ntitle or IEN is specified in the COMPUTED FINDING PARAMETER field.\nnotes with a status of COMPLETED.)\n\nThe additional data is:\n\nV("DISPLAY NAME")=Display name of TIU title.\n\nV("EPISODE BEGIN DATE/TIME")=String_":"_EPISODE BEGIN DATE/TIME\nwhere String is "Adm" for ward locations and "Visit" for all other\nlocation types. Date/time is in MM/DD/YY format.\n\nIf you want to search for notes with a certain status, then append\nV("EPISODE END DATE/TIME")=String_" "_EPISODE END DATE/TIME where\nstring is null if no date/time or "Dis: " if date/time exists.\nDate/time is in MM/DD/YY format\n\nV("EXPECTED COSIGNER")=EXPECTED COSIGNER that is identified on a note. \nIf this is used as a CONDITION, and the STATUS of the note is\nUNCOSIGNED, you must have the STATUS of 'UNCOSIGNED' appended to the\nNOTE TITLE or the IEN of the NOTE TITLE in the COMPUTED FINDING\nPARAMETER field. If the note is already 'COSIGNED', then you can use the\ndefault status of COMPLETED to check if the CONDITION is TRUE. If you\n"^status" to the title. Status can be any of the following:\nare trying to find a particular COSIGNER for a COMPLETED or UNCOSIGNED\nnote, you will have to have two instances of the finding with one of\nthem having the STATUS of UNCOSIGNED appended in the COMPUTED FINDING\nPARAMETER field and the other having no STATUS in the COMPUTED FINDING\nPARAMETER field.  An "OR" logic operator would be used to join these two\nfindings.\n\nV("EXPECTED SIGNER")=EXPECTED SIGNER that is identified on a note. If\nthis is used as a CONDITION, and the STATUS of the note is UNSIGNED, you\nmust have the STATUS of 'UNSIGNED' appended to the NOTE TITLE or the IEN\n\nof the NOTE TITLE in the COMPUTED FINDING PARAMETER field. If the note\nis already 'SIGNED' then you can use the default status of COMPLETED to\ncheck if the CONDITION is TRUE. If you are trying to find a particular\nSIGNER for a COMPLETED or UNSIGNED note, you will have to have two\ninstances of the finding with one of them having the STATUS of UNSIGNED\nappended in the COMPUTED FINDING PARAMETER field and the other having no\nSTATUS in the COMPUTED FINDING PARAMETER field. An "OR" logic operator\nwould be used to join these two findings.\n\nV("HOSPITAL LOCATION")=External format of HOSPITAL LOCATION from TIU\n  1 = UNDICTATED\nDOCUMENT file\n\nV("NUMBER OF IMAGES")=Number of images associated with TIU DOCUMENT\nentry\n\nV("REQUESTING PACKAGE")=REQUESTING PACKAGE REFERENCE field from TIU\nDOCUMENT file (internal format)\n\nV("SUBJECT")=SUBJECT (OPTIONAL description) field from TIU DOCUMENT\nfile (note that characters are limited to ensure returned string is\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-AGE", "
PXRMPDEM
\n", "
AGE
\n", "
VA-Patient Age
\n", "
\nThis is a single occurrence computed finding that returns the\npatient's age in years. It can be used as the value in the Condition.\nFor example: I V>50.\n\nIf the patient is deceased the age will be their age on the date of\ndeath and V("DECEASED")=1.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", ""], ["VA-WH PAP SMEAR ABNORMAL IN WH PKG", "
PXRMCWH
\n", "
PAPA
\n", "
VA-WH Pap Smear Abnormal in WH pkg
\n", "
\nThis computed finding calls an API to the WH package that returns up to n \nDATA(n,"WVIEN")=\n\nThe data assigned to the Link subscript is a boolean value. If the value is \na 1, then the Pap smear procedure was entered through the Radiology package.\n\nThe data assigned to the Status subscript is used to determine if the \nprocedure is Open, Closed, or Pending. Pending means that the Pap smear \nprocedure in the Women's Health package needs to have a result entered. Open \nmeans that the Pap Smear procedure has been resulted but the provider has \nnot closed the case. Closed means that a result has been entered for the \nnumber for a specific date range of Pap smear procedures found in the WH \nprocedure and it has been closed.\n\nThe data assigned to the Value subscript is used to determine the diagnosis \nof the Pap smear procedure. The diagnosis in the Women's Health package can \neither be Normal, Abnormal, or Unsatisfactory. For this computed finding, \nthe Value should always be Abnormal\n\nThe data assigned to the WVIEN subscript is the Women's Health procedure \nIEN.\n\npackage that have an abnormal diagnosis.\nThe text display in the Clinical Maintenance will be found in the Text \narray.\n\nThe results from the computed finding will be returned in the Data Array; \nthe format of the array is:\nDATA(n,"LINK")=\nDATA(n,"STATUS")=\nDATA(n,"VALUE")=\n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-WH MAMMOGRAM ABNORMAL IN WH PKG", "
PXRMCWH
\n", "
MAMA
\n", "
VA-WH Mammogram Abnormal in WH pkg
\n", "
\nThis computed finding calls an API to the WH package that returns up to n \nDATA(n,"WVIEN")=\n\nThe data assigned to the Link subscript is a boolean value. If the value is \na 1, then the Mammogram procedure was entered through the Radiology package.\n\nThe data assigned to the Status subscript is used to determine if the \nprocedure is Open, Closed, or Pending. Pending means that the Mammogram \nprocedure in the Women's Health package needs to have a result entered. Open \nmeans that the Mammogram procedure has been resulted but the provider has \nnot closed the case. Closed means that a result has been entered for the \nnumber for a specific date range of Mammogram procedures found in the WH \nprocedure and it has been closed.\n\nThe data assigned to the Value subscript is used to determine the diagnosis \nof the Mammogram procedure. The diagnosis in the Women's Health package can \neither be Normal, Abnormal, or Unsatisfactory. For this computed finding, \nthe Value should always be Abnormal\n\nThe data assigned to the WVIEN subscript is the Women's Health procedure \nIEN.\n\npackage that have an abnormal diagnosis.\nThe text display in the Clinical Maintenance will be found in the Text \narray.\n\nThe result from the computed finding will be returned in the Data Array; the \nformat of the array is:\nDATA(n,"LINK")=\nDATA(n,"STATUS")=\nDATA(n,"VALUE")=\n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-CPRS WRITE ACCESS", "
PXRMEHR
\n", "
CUTOVER
\n", "
CPRS Write Access Functionality
\n", "
\nThis computed finding returns the signed in user write access permission \nfor CPRS actions.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-SMART PATIENT HAS ALERT", "
PXRMCALT
\n", "
ALERT
\n", "
Smart Alert
\n", "
\nThis computed finding will return true if the patient and provider have an\nactive SMART Alert in CPRS. To check for an alert, pass the internal entry\nnumber of the OE/RR Notification (#100.9) entry as the computed finding\nparameter.\n \nReturn Values\nDATA("XQAID")=Alert XQAID string\nDATA("SOURCE")=The internal data source from the alert file.\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-PERSIAN GULF INDICATOR", "
PXRMMSER
\n", "
PGULF
\n", "
VA-Persian Gulf Indicator
\n", "
\nThis computed finding returns the PERSIAN GULF INDICATOR value.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", ""], ["VA-DATE OF DEATH", "
PXRMPDEM
\n", "
DOD
\n", "
VA-Patient's Date of Death
\n", "
\nThis is a single occurrence computed finding that returns the \npatient's date of death, if it exists, as a FileMan date. It can be\nused as the value in the Condition. For example: I V>2330304\nThe date of the finding is the date of death so that date range\nsearches can be used to find patients who died in a certain time\nframe.\n\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", ""], ["VA-WH UNSAFE ORDER COUNT", "
PXRMCWH1
\n", "
ORDERCNT
\n", "
Women's Health Unsafe Order Count
\n", "
\nThis computed finding returns the number of unsafe orders displayed in \nthe TIU objects VA-WH POTENTIAL TERATOGENIC ORDERS and VA-WH POTENTIAL \nUNSAFE ORDERS. To retrieve the number of teratogenic orders, set the \nCOMPUTED FINDING PARAMETER to PREGNANT. To retrieve the number of unsafe\norders, set the COMPUTED FINDING PARAMETER to LACTATING.\n \nThe count is returned in V("COUNT"). This finding is true \nif the count is greater than zero and false if it is zero. The date is \nset to the value of today.\n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "", "
MULTIPLE
\n", ""], ["VA-ALLERGY", "
PXRMART
\n", "
ARTCL
\n", "
VA-Allergy
\n", "
\nIdentifies any allergies that contain either the ingredient or drug\nNote: This computed finding does not support date reversal.\n\nThe CSUBs are:\n ALLERGY TYPE\n MECHANISM\n OBSERVED/HISTORICAL\n REACTANT\n\nclass that you specify via the Computed Finding Parameter. Ingredients\nwill be prefixed with IN: while DR: is used for drug classes. You may\nalso use the * as a wildcard on the end of your selection. For example,\nto search for the ingredient aspirin you would enter IN:ASPIRIN. For\ndrug class MS101 you would enter DR:MS101. For all ingredients\nbeginning with "ampi" you would type IN:AMPI*. For all MS1 related\ndrug classes you'd enter DR:MS1*.\n\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", "
YES
\n"], ["VA-SEX", "
PXRMPDEM
\n", "
SEX
\n", "
VA-Patient Sex
\n", "
\nThis is a single occurrence computed finding that returns a\npatient's sex as either "F" for female or "M" for male.\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
SINGLE
\n", ""], ["VA-REMINDER DEFINITION", "
PXRMCDEF
\n", "
RDEF
\n", "
VA-Reminder Definition
\n", "
\nThis computed finding will evaluate the reminder definition that is \noverridden by appending "^DATE=DUE DATE" or "^DATE=LAST DONE" to the\nreminder name. If a last done date cannot be determined then the date\nof the finding will be the evaluation date.\n \nExamples:\n  123\n  123^DATE=LAST DONE\n  VA-IHD LIPID PROFILE\n  VA-IHD LIPID PROFILE^DATE=LAST DONE\n  VA-IHD LIPID PROFILE^DATE=DUE DATE\nspecified in the COMPUTED FINDING PARAMETER field. This can be the\n \nThe VALUE array, which can be used in a Condition, will contain the\nevaluation status, due date, and last done date. The date values\nare in VA FileMan format. The variable V is the reminder evaluation\nstatus. Possible values for the reminder evaluation status are:\n CNBD\n CONTRA\n DONE\n DUE NOW\n DUE SOON\ninternal entry number of the reminder definition or the name that is\n ERROR\n N/A\n NEVER\n REFUSED\n RESOLVED\n \nExample of the Value array:\n  VALUE("STATUS")="DUE NOW" \n  VALUE("DUEDATE")=3051010.1220 \n  VALUE("LASTDONE")=3051010.1220 \nused is the NAME field (.01) of the reminder definition, not the PRINT\n \nCondition examples:\n  I V="DUE NOW" \n  I V("STATUS")="DUE NOW" \n  I V("DUEDATE")>3051010.1220 \n  I V("LASTDONE")=3051010.1220 \n  \n***WARNING*** This computed finding can be used to evaluate a reminder \ninside of a reminder evaluation - do not have this computed finding \nevaluate the same reminder as the one being evaluated.  \nNAME, additionally the definition must be active. The computed finding\nwill be false if the reminder evaluation status is CNBD or ERROR, in all\nother cases it will be true.\n \nThe default date of the finding is the evaluation date; this can be\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
SINGLE
\n", "
YES
\n"], ["VA-PATIENTS WITH APPOINTMENTS", "
PXRMRDI
\n", "
APPL
\n", "
VA-Patients with Appointments
\n", "
\nThis list computed finding returns a list of patients with\n return the Appointment Date/Time in piece 1 and Date Appointment Made in piece\n 16. A condition such as I $P(V,U,16)>3060301 would be true if the date the\n appointment was made was after March 1, 2006. If FLDS is not specified then the\n value will be ID=1 (Appointment Date/Time) and ID=2 (Clinic IEN and Name).\n \n STATUS sets a filter on the appointment status; only those\n appointments with status on the list will be returned. The possible\n values for STATUS are R (Scheduled/Kept), I (Inpatient), NS\n (No-show), NSR (No-show, Rescheduled), CP (Cancelled by Patient),\n \nappointments in the specified date range. The COMPUTED\n CPR (Cancelled by Patient, Rescheduled), CC (Cancelled by Clinic),\n CCR (Cancelled by Clinic, Rescheduled), NT (No Action Taken).\n If STATUS is not specified the default is R,I.\n \n LL:Reminder Location List specifies a list of locations so that only\n appointments for those locations will be returned. If LL is not\n specified, then appointments for all locations will be returned.\n \nFLDS, STATUS, and LL are all optional and can be given in any order.\nSome examples:\nFINDING PARAMETER can be used to filter the results. The values that\n \n FLDS:1,2,16^STATUS:R^LL:DIABETIC LOCATIONS\n STATUS:CP,CC^FLDS:25\n LL:DIABETIC LOCATION\n\n\n\ncan be used in the parameter are:\n FLDS:F1,F2,... where F1,F2 are any of the possible integer ID values listed in\n the table for this computed finding in the Computed Finding section of the\n Clinical Reminders Managers Manual. These specify what data associated with the\n appointment is to be returned; this data can be used in a CONDITION statement.\n Field number n will be the nth piece of the value. For example FLDS:1,16 would\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", "
NO
\n"], ["VA-TREATING FACILITY LIST", "
PXRMRDI
\n", "
TFL
\n", "
VA-Treating Facility List
\n", "
\nThis multi-occurrence computed finding returns a list of treating\nfile. If there is no ADT/HL7 EVENT REASON then DATE LAST TREATED\nwill also be null.\n \nSome examples of values that are returned:\n "516^BAY PINES VAMC^^^VAMC"\n "537^JESSE BROWN VAMC^3041122.110926^3^VAMC"\n "552^DAYTON^3001113.092056^3^VAMC"\n "556^NORTH CHICAGO VAMC^3050406.13^3^VAMC"\n "578^HINES, IL VAMC^3020919.2324^3^VAMC"\n "589^VA HEARTLAND - WEST, VISN 15^^^VAMC"\nfacilities i.e., systems that store data related to a patient. The\n "636^VA NWIHS, OMAHA DIVISION^^^VAMC"\n "673^TAMPA VAMC^3001215.1327^3^VAMC"\n "695^MILWAUKEE VAMC^3030328.13^3^VAMC"\n \nA CONDITION can be written that uses any of the pieces of the value.\nFor example, a CONDITION to check that the FACILITY TYPE is VAMC\nwould be: I $P(V,U,5)="VAMC"\n \nSince no date can be associated with an entry, the date of evaluation\nwill be used.\nvalue for each entry is:\n\n STATION NUMBER^NAME^DATE LAST TREATED^ADT/HL7 EVENT REASON^FACILITY\n TYPE\n \nSTATION NUMBER, NAME, and FACILITY TYPE are from the Institution\nfile. FACILITY TYPE is one of the entries found in the FACILITY TYPE\nfile. ADT/HL7 EVENT REASON is a code from the ADT/HL7 EVENT REASON\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-AGE BIRTH SEX LIST", "
PXRMASL
\n", "
CFAGESL
\n", "
VA-Age and Birth Sex List
\n", "
\nThis list type computed finding builds a list of all patients in the\npatients who fall in the age range will be included on the list.\n\nHere are some examples:\n30Y^65Y - all patients between the ages of 30 and 65 years\n40Y^65Y^F - all female patients between the ages of 40 and 65 years\n66Y^66Y^M - all male patients whose age is 66 years\n\nIf these parameters are not correctly specified no patients will be on\nthe list. Minimum age and maximum age cannot be null and maximum age\nmust be greater than or equal to minimum age.\ninclusive age range defined by a minimum age and a maximum age.\n\nNote that Beginning Date/Time, Ending Date/Time, and Occurrence Count\nare not relevant for this computed finding.\n\n\nOptionally, birth sex can used as an additional filter.\n\nThe Computed Finding Parameter is used to specify the search criteria in\nthe format: minimum age^maximum age^sex. Age is written as a number\nfollowed by a unit. The units are: D=days, W=weeks, M=months, or\nY=years. If the unit is not specified it defaults to years. Sex can be\nF=female, M=male, or null. If sex is null then both female and male\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", "
YES
\n"], ["VA-PRIMARY CARE PROVIDER", "
PXRMPCIN
\n", "
PROVIDER
\n", "
VA-PCMM Primary Care Provider
\n", "
\nThis single occurrence computed finding returns the patient's primary care\nprovider. This is the name field from the NEW PERSON file (#200).  If no\nprimary care provider has been assigned, the value will be null.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", ""], ["VA-PTF HOSPITAL DISCHARGE DATE", "
PXRMPDEM
\n", "
HDISCH
\n", "
VA-PTF Hospital Discharge Date
\n", "
\nThis multi-occurrence computed finding returns a list of hospital\ndischarge dates from the Patient Treatment File. The default is to\nnot include fee basis or census entries. The computed finding\nparameter can be used to include them. The format is IN:FEE to\ninclude fee bases and IN:CEN to include census. If you want to\ninclude both, the format is IN:FEE,CEN.\n\n\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-BIRTH DATE BIRTH SEX LIST", "
PXRMASL
\n", "
CFBDAYSL
\n", "
VA-Birth Date Birth Sex List
\n", "
\nThis list type computed finding builds a list of all patients in the\nbe included on the list.\n  \nHere are some examples:\n 10/01/1940^Oct 1, 1965 - all patients born between October 1, 1940 and\n                          October 1, 1965.\n 01-01-1970^01 Jan 1980^F - all female patients born between January 1,\n                            1970 and January 1, 1980\n Jun 1, 1969^Jun 1 1969^M - all male patients born on June 1, 1969.\n  \nIf these parameters are not correctly specified no patients will be on\ninclusive age defined by a minimum birth date and a maximum birth date.\nthe list. Minimum birth date and maximum birth date cannot be null and \nmaximum birth date must be greater than or equal to minimum birth date.  \n  \nNote that Beginning Date/Time, Ending Date/Time, and Occurrence Count\nare not relevant for this computed finding.\n\nOptionally, birth sex can used as an additional filter.  \n  \nThe Computed Finding Parameter is used to specify the search criteria in\nthe format: minimum birth date^maximum birth date^sex. The dates can be\nentered in any of the date formats that can be used in Clinical\nReminders. Sex can be F=female, M=male, or null. If sex is null then\nboth female and male patients whose birth date falls in the range will\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", "
YES
\n"], ["VA-WH BREAST PROCEDURES", "
PXRMCWH
\n", "
GETBRTST
\n", "
Most Recent Breast Procedure
\n", "
\nThis computed findings search the Women's Health Procedure file for \nReturn Values\nDATA("ACCESSION")=Women's Health Procedure file accession number\nDATA("STATUS")=Women's Health Procedure file status OPEN or CLOSED\nDATA("DIAGNOSIS")=Women's Health Procedure file primary result/diagnosis \nfield.\nDATA("PROVIDER")=Women's Health Procedure file provider entry.\nDATA("DAS")=The Women's Health Procedure file IEN.\n \nDATA("DIALOG")=1\nDATA("PACKAGE")="WOMEN'S HEALTH"\nprocedures related to a breast image treatment between the beginning and \nDATA("PACKAGE PREFIX")="WV"\n \nThe DIALOG subscript is used to let the Reminder Dialog Branching Logic \nbuild the dialog element/group display text from the TEXT node from the\ncomputed finding output. This subscript is also used by branching logic\nto map the results to a Reminder General Finding entry.\n \nThe PACKAGE and PACKAGE PREFIX subscripts are both used in the Reminder\nDialog Branching Logic process when mapping the computed finding results\nto Reminder General Finding entries.\nending date. This computed finding will only return one entry and it is \nalways the most recent based off the search date range.\n \n \nInput parameters:\nNone\n \n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-CASCADE INDEX", "
PXRMCEOC
\n", "
EPISODE
\n", "
Episode of Care
\n", "
\nThis computed finding can return multiple patient cascade(s). \nof open. "" Returns both OPEN and CLOSED cascades.\n \nIf searching for an open cascade the computed finding will return only \none cascade. If searching for all cascade the computed finding will \nreturn cascade when the START DATE is between the passed in start and \nstop date.\n \nThe data output is:\nDATA("STATUS")=STATUS (OPEN or CLOSED)\nDATA("NAME")=CASCADE NAME\nThe computed finding parameter field is mandatory. The parameter structure\nDATA("DIALOG")=1\n \nThe DIALOG parameter is used to let the Reminder Dialog Branching Logic\nbuild the dialog element/group display text from the TEXT node from the\ncomputed finding output.\nis:\n \nNAME:STATUS\n \nNAME is the type of cascade to search for:\n \nSTATUS is either OPEN or "". OPEN only returns cascade with a status \n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-WH OPEN PROCEDURE WITH NO NOTIFICATION", "
PXRMCWH
\n", "
NONOTIFL
\n", "
Procedures with no notification
\n", "
\nThis computed finding returns a list of patients with Open Women's Health \nprocedures with either no corresponding notification or open \nnotification within the computed finding date range.\n \nPARAM="ALL": Returns all procedure types\n \nPARAM="BR": Returns procedures related to Breast Treatments\n \nPARAM="CX": Returns procedures related to cervical treatments\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", "
YES
\n"], ["VA-WH PROCEDURES WITH NO NOTIFICATION", "
PXRMCWH
\n", "
NONOTIFD
\n", "
Procedures with no notification
\n", "
\nThis computed finding searches an active Cascade type to find any Women's \nDATA("DAS")=The internal entry number (IEN) from file 790.1. Multiple IEN \nare delimited by a colon ":".\nDATA("DIALOG")=1\nDATA("PACKAGE")="WOMEN'S HEALTH"\nDATA("PACKAGE PREFIX")="WV"\n \nThe DIALOG subscript is used to let the Reminder Dialog Branching Logic \nbuild the dialog element/group display text from the TEXT node from the\ncomputed finding output. This subscript is also used by branching logic\nto map the results to a Reminder General Finding entry.\nHealth Procedures between the beginning and ending dates that\n \nThe PACKAGE and PACKAGE PREFIX subscripts are both used in the Reminder\nDialog Branching Logic processes when mapping the computed finding results\nto a Reminder General Finding entry.\ndo not have a notification type on file or still have an\nopen notification entry on file.\n \nComputed Finding Parameter\nNAME = Cascade type to search for.\n \nReturn Values\n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-SMART PROCESSING ALERT DATA", "
PXRMCALT
\n", "
ACTALRTD
\n", "
Active SMART Alert
\n", "
\nTHIS COMPUTED FINDING ONLY HAS VALUE IN A REMINDER DIALOG BRANCHING LOGIC.\n \nThis computed finding does not honor the following fields:\n     Beginning Date\n     Ending Date\n     Occurence Count\n \nReturn Data:\nThe return data will vary based off the SMART alert. All alert will have \nan DATA("ACTIVE ALERT ID")=The active alert id.\nThis computed finding is used to check if the SMART alert that is opening \nthe Reminder Dialog is a specific SMART alert entry.\n \nInput parameters:\nalert id(s)\n \nA list of alert id to determine if the current alert id is one of them.\nMultiple alerts should be delimited by a semi-colon ";".\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-BSA", "
PXRMBMI
\n", "
BSA
\n", "
VA-Body Surface Area
\n", "
\nThis multi-occurrence computed finding returns the patient's body\nweight measurement. This may be before or after the weight\nmeasurement.\n\nCOMPUTED FINDING PARAMETER  FORMULA\n            M                Mosteller\n            D                DuBois and Dubois\n            H                Haycock\n            G                Gehan and George\n            B                Boyd\n\nsurface area (BSA) as a value that can be used in the CONDITION\nThe default is to use the Mosteller formula. Unless there is a\nreason to use one of the other formulas, the recommendation is to\nuse the default, because it is faster to calculate and the numerical\nresults are very close to those of the other formulas.\n\n\n\nfield. The COMPUTED FINDING PARAMETER can be used to select which\nformula is used to calculate the BSA.\n\nNote that date range searching is applied only to the weight and\nthat the date of the finding is the date of the weight measurement\nused in the BSA calculation. The height used in the calculation will\nbe the height measurement that occurred closest to the date of the\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-CURRENT INPATIENTS", "
PXRMINPL
\n", "
CURR
\n", "
VA-Current Inpatients
\n", "
\nThis list type computed finding can be used to build a list of\n\nThe CONDITION field may also be used to select entries by any of the\nfollowing CSUB subscripts:\n\nV or V("VALUE") = the ward to which the patient is currently admitted\n                  in the format of 9;3EAST (IEN;Ward Name)\n\nV("INSTITUTION") = the name of the INSTITUTION (file #4) entry\n                   with which the ward is associated in the format\n                   5000;ELY;660GC (IEN;Institution Name;Station Number)\nall current inpatients. Note that current refers to the actual\n\nV("ADMIT DATE") = the date of admission for the patient in the\n                  format 3010815.114255^AUG 15,2001@11:42:55\n                  (Internal^External)\n\n\n\n\n\n\ncalendar date so for this computed finding date ranges are\n\n\n\n\nirrelevant. A Reminder Location List can be used to restrict the\nselection of patients to only the ward locations included in the\nlocation list. To do this enter the exact .01 name of a Reminder\nLocation List into the COMPUTED FINDING PARAMETER field. If a\nReminder Location List is not used then all ward locations will be\nincluded.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", ""], ["VA-COMBAT VET ELIGIBILITY", "
PXRMMSER
\n", "
CVELIG
\n", "
VA-Combat Vet Eligibility
\n", "
\n\n\n\n\n\n\nThis computed finding will be true if the patient has ever qualified or\ncurrently qualifies as a combat vet.\n \nThe possible values that can be used in a Condition are: "ELIBIGLE"\nand "EXPIRED". "EXPIRED" will be returned if the veteran was not\neligible on the evaluation date. An example is:\n \nI V="EXPIRED"\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-PRIMARY CARE TEAM", "
PXRMPCIN
\n", "
TEAM
\n", "
VA-PCMM Primary Care Team
\n", "
\nThis single occurrence computed finding returns the name of the\npatient's PCMM primary care team as the value. If no team has been\nassigned, the value will be null.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", ""], ["VA-SMART PROCESSING ALERT ID", "
PXRMCALT
\n", "
ACTALERT
\n", "
Active SMART Alert ID
\n", "
\nTHIS COMPUTED FINDING ONLY HAS VALUE IN A REMINDER DIALOG THAT CONTAINS\n \nReturn Data\nDATA("ACTIVE ALERT ID")=The active alert id\nDATA("ACTIVE ALERT DATA")=This is the data id that trigger the alert.\nDATA("DAS")=The active alert id used by Reminder General Findings.\nDATA(NOTIFICATION NUMBER)="The alert IEN from file 100.9\nDATA("DIALOG")=1\nDATA("PACKAGE")="ORDER ENTRY/RESULTS REPORTING"\nDATA("PACKAGE PREFIX")="OR"\n \nGENERAL FINDINGS AND HAS BRANCHING LOGIC.\nThe DIALOG subscript is used to let the Reminder Dialog Branching Logic \nbuild the dialog element/group display text from the TEXT node from the\ncomputed finding output. This subscript is also used by branching logic\nto map the results to a Reminder General Finding entry.\n \nThe PACKAGE and PACKAGE PREFIX subscripts are both used in the Reminder\nDialog Branching Logic processes when mapping the computed finding results\nto Reminder General Finding entries.\n \nThis computed finding is used to determine which SMART Alert the user is \nprocessing so the Reminder Dialog can tell CPRS to clear the alert when \nit is appopriate based off the dialog setup.\n \nInput parameters:\nNone\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-AGENT ORANGE EXPOSURE", "
PXRMMSER
\n", "
AORANGE
\n", "
VA-Agent Orange Exposure
\n", "
\nThis computed finding will be true if the patient has an agent\n\n\norange exposure registration date in the date range specified by\nBeginning Date/Time and Ending Date/Time.\n\nSubscripts that can be used in a Condition are:\n "LOCATION"\n\nThe default value is "LOCATION".\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-WH OPEN PROCEDURE COUNT", "
PXRMCWH
\n", "
OPENPROC
\n", "
Number of open procedures
\n", "
\nThis computed finding searches an active Cascade type to find\nReturn Data\nDATA("DAS")=Internal entry from the WV Procedure File\nDATA("Number of Test Open")=The total number of Procedure from the \nWomen's Health Procedure file still in an open state.\nDATA("DIAGNOSIS")=The diagnosis value from the WV Procedure File\n \nDATA("DIALOG")=1\nDATA("PACKAGE")="WOMEN'S HEALTH"\nDATA("PACKAGE PREFIX")="WV"\n \n any open Women's Health Procedures in the active cascade. This computed \nThe DIALOG subscript is used to let the Reminder Dialog Branching Logic \nbuild the dialog element/group display text from the TEXT node from the\ncomputed finding output. This subscript is also used by branching logic\nto map the results to a Reminder General Finding entry.\n \nThe PACKAGE and PACKAGE PREFIX subscripts are both used in the Reminder\nDialog Branching Logic processes when mapping the computed finding results\nto a Reminder General Finding entry.\nfindings returns the total count of open procedures and the highest \nBI-BAD result from the Women's Health Procedures. If one of the \nopen procedures does not have a BI-RAD code then no diagnosis are \nreturned.\n \nComputed Finding Parameter NAME = Cascade name to search for.\n \n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-POW", "
PXRMMSER
\n", "
POW
\n", "
VA-POW
\n", "
\nThis computed finding will be true if the patient was a POW in the\ndate range specified by Beginning Date/Time and Ending Date/Time.\n\nSubscripts that can be used in a Condition are:\n "LOCATION"\n\nThe default value is "LOCATION".\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-COMBAT SERVICE", "
PXRMMSER
\n", "
COMBAT
\n", "
VA-Combat Service
\n", "
\nThis computed finding will be true if combat service is found in the\n\n\n\ndate range the date range specified by Beginning Date/Time and\nEnding Date/Time.\n\nSubscripts that can be used in a Condition are:\n "LOCATION"\n\nThe default value is "LOCATION".\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-PURPLE HEART", "
PXRMMSER
\n", "
PHEART
\n", "
VA-Purple Heart
\n", "
\nThis computed finding will be true if the patient is a Purple Heart\nrecipient.\n\nThere is no value for use in a Condition.\n\n\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", ""], ["VA-OIF SERVICE", "
PXRMMSER
\n", "
OIF
\n", "
VA-OIF Service
\n", "
\nThis multi-occurrence computed finding will search for periods of\n\n\nOIF service in the date range specified by Beginning Date/Time and\nEnding Date/Time.\n\nSubscripts that can be used in a Condition are:\n "LOCATION"\n\nThe default value is "LOCATION".\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-OEF SERVICE", "
PXRMMSER
\n", "
OEF
\n", "
VA-OEF Service
\n", "
\nThis multi-occurrence computed finding will search for periods of\n\nOEF service in the date range specified by Beginning Date/Time and\nEnding Date/Time.\n\nSubscripts that can be used in a Condition are:\n "LOCATION"\n\nThe default value is "LOCATION".\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-SERVICE SEPARATION DATES", "
PXRMMSER
\n", "
DISCHDT
\n", "
VA-Service Separation Date(s)
\n", "
\nThis multiple occurrence computed finding returns service separation\n  \n The default value is the separation date.\n\ninformation. The date of the finding is the separation date.\n \nCSUB data that can be used in a Condition are: \n  "BRANCH" \n  "DISCHARGE TYPE" \n  "ENTRY DATE" \n  "SEPARATION DATE" \n  "SERVICE COMPONENT" \n
\n
\n", "
NATIONAL
\n", "
OFFICE OF QUALITY & PERFORMANCE
\n", "", "
\n
\n\n
\n", "
MULTIPLE
\n", ""], ["VA-WH NEXT PROCEDURE", "
PXRMCWH
\n", "
NEXTPROC
\n", "
Women's Health Next Procedure
\n", "
\nThis computed finding returns the Next Procedure Name and the Next \nReturn Value\nDATA("Procedure")=the name of the appropriate next treatment need field \nProcedure Date from the Women's Health Patient File. This computed \nfinding will either return information related to the Breast or the\nCervical treatments based off the Computed Finding Parameter.\n \nComputer Parameter\nBR: Breast Procedure\nCX: Cervical Procedure\n \n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-UNKNOWN OEF/OIF SERVICE", "
PXRMMSER
\n", "
UNKOEIF
\n", "
VA-Unknown OEF/OIF Service
\n", "
\nThis multi-occurrence computed finding will search for periods of OEF/OIF\n\n\nservice with an unknown location in the date range specified by Beginning\nDate/Time and Ending Date/Time.\n\nSubscripts that can be used in a Condition are:\n "LOCATION"\n\nThe default value is "LOCATION".\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-RACE PRE 2003", "
PXRMPDEM
\n", "
RACE
\n", "
VA-Patient's pre-2003 Race
\n", "
\nThis single occurrence computed finding returns a patient's Race value\nfrom the Patient file. Patch DG*5.3*415, compliance date January 31,\n2003, made the Race field obsolete and replaced it with the Race\nInformation multiple. The possible values are those in the RACE file (#10).\nIf there is an entry, the computed finding will be true; otherwise it\nwill be false.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", ""], ["VA-DISCHARGES FOR A DATE RANGE", "
PXRMINPL
\n", "
DISCH
\n", "
VA-Discharges for a Date Range
\n", "
\nThis list type computed finding can be used to build a list of\nfollowing CSUB subscripts:\n\nV or V("VALUE") = the ward from which the patient was discharged\n                  in the format of 9;3EAST (IEN;Ward Name)\n\nV("INSTITUTION") = the name of the INSTITUTION (file #4) entry \n                   with which the ward is associated in the format \n                   5000;ELY;660GC (IEN;Institution Name;Station Number) \n\nV("TYPE_OF_MVMT") = the type of movement entry from file 405.1\npatients who have been discharged in the specified date range. A\n                     (e.g., REGULAR, OPT-NSC, OPT-SC, etc.)\n\n\n\n\n\n\nReminder Location List can be used to restrict the selection of\npatients to only the ward locations included in the location list.\nTo do this enter the exact .01 name of a Reminder Location List into\nthe COMPUTED FINDING PARAMETER field. If a Reminder Location List is\nnot used then all ward locations will be  included.\n\nThe CONDITION field may also be used to select entries by any of the\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", ""], ["VA-DATE FOR AGE", "
PXRMPDEM
\n", "
DFA
\n", "
VA-Date for Age
\n", "
\nThis computed finding returns the date on which the patient will\n\n\nreach the age (in years) specified by the value of the computed\nfinding parameter. Both the default value and date of the finding\nwill be the date in FileMan format when the patient reaches the\nspecified age.\n\nFractional ages like 59.5 are not allowed and the fractional part\nwill be ignored.\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-EMPLOYEE", "
PXRMPDEM
\n", "
EMPLOYE
\n", "
VA-Employee
\n", "
\nThis computed finding will be true if the patient was an employee\n\n2. If there is a match, a check is made to see if the patient's New\nPerson file entry has a pointer to the PAID file. If there is no\npointer, the computed finding is false.\n\n3. If there is a pointer, then Date Entered is compared with Ending\nDate/Time. If it is greater, the computing finding is false.\n\n4. Next, a check is made to see if there is a Termination Date. If\nthere is a Termination Date and it is prior to the Beginning\nduring the date range specified by the Beginning Date/Time and\nDate/Time, the computed finding is false.\n\n5. If steps one through four are passed, the computed finding is true.\n\nEnding Date/Time.\n\nThe following algorithm is used to determine if the patient was an\nemployee:\n\n1. A lookup based on the patient's SSN is made in the New Person\nfile. If there is no match, the computed finding is false.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-WH BREAST TREATMENT OVERDUE LIST", "
PXRMCWH
\n", "
BROVRDUE
\n", "
Overdue breast treatment list
\n", "
\nThis list computed finding return a list of patient overdue for the \nbreast treatment found between the beginning and end date.\n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "", "
LIST
\n", "
YES
\n"], ["VA-IS INPATIENT", "
PXRMPDEM
\n", "
INP
\n", "
VA-Is Inpatient
\n", "
\nThis computed finding will be true if the patient was/is an\n TREATING SPECIALTY\n WARD LOCATION\n\n\n\n\ninpatient on the evaluation date. The following "CSUB" values will\nbe available:\n\n ADMISSION DATE/TIME (FileMan format)\n ADMISSION TYPE\n ATTENDING PHYSICIAN\n DATE (FileMan format)\n PRIMARY PROVIDER\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-ACTIVE PATIENT RECORD FLAGS", "
PXRMPRF
\n", "
PRF
\n", "
VA-Active Patient Record Flags
\n", "
\nThis multiple occurrence computed finding will return active patient\n\nUse the "^" character to include more than one parameter in the\nsearch specification.\n\nSome examples:\n C:L - would search for local flags\n C:N^T:B - would search for national flags whose type is behavioral\n F:DRINKING PROBLEM - would search for the flag DRINKING PROBLEM\n T:C^F:INFECTIOUS DISEASE - would search for the flag INFECTIOUS\n   DISEASE whose type is clinical\nrecord flags. The Computed Finding Parameter is used to precisely\n\nOnly active flags that meet all the specified criteria will be\nreturned. If no search parameters are specified then no flags will be\nreturned.\n\nThe date associated with a flag is the assigned date.\n\nThe following "CSUB" data is returned for each flag that is found:\n\nAPPRVBY  - approved by\nspecify what flags to search for. There are three parameters that\nASSIGNDT - assigned date/time\nCATEGORY - category\nDATE     - assigned date/time\nFLAG     - flag name\nFLAGTYPE - flag type\nORIGSITE - originating site\nOWNER    - owner site\nREVIEWDT - review date/time\nTIULINK  - pointer to the TIU note (only applies if the flag is linked to a\n           TIU note)\ncan be used: C for category, T for type, and F for a specific flag.\nTIUTITLE - the note title (only applies if the flag is linked to a\n           TIU note)\n\n\n\n\n\n\n\n\nThe possible values are:\n\n\n Category - N (national), L (local)\n Type - B (behavioral), C (clinical), O (other), and R (research)\n Flag - exact name of the flag\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", "
YES
\n"], ["VA-ASU USER CLASS", "
PXRMASU
\n", "
CLASS
\n", "
VA-ASU User Class
\n", "
\nThis multi-occurrence computed finding returns a list of the ASU\nDate/Time and Ending Date/Time are used with the finding, then the \nperiod defined by the Activation Date and Expiration Date must\noverlap the period defined by the Beginning Date/Time and the Ending\nDate/Time in order for the finding to be true. When the Activation\nDate is missing, a 0 will be used in its place for determining the\noverlap. When the Expiration Date is missing, the evaluation date\nwill be used in its place for determining the overlap.\n  \nThe Computed Finding Parameter can be used to specify either the\ninternal entry number or the exact name of an ASU User Class. If\nUser Classes that the user belongs to. The user is the person who is\nthis option is used, then each User Class the user is a member of is\nchecked to see if it is either the specified User Class or a child\nof the specified User Class. Only the User Classes that pass this\ntest will remain on the list of the user's User Classes. For\nexample, if the user is a member of the user class ATTENDING \nPHYSICIAN, which is a child of the user class PHYSICIAN, and the\nComputed Finding Parameter is set to "PHYSICIAN," then ATTENDING\nPHYSICIAN will remain on the list. If the Computed Finding Parameter\nwas set to CARDIOLOGIST, then ATTENDING PHYSICIAN would be removed\nsince it is not a child of CARDIOLOGIST.\nrunning the reminder evaluation or processing a reminder dialog.\n\nIf you want to specify the user class as PHYSICIAN, in the computed\nfinding parameter field, type the following:\n COMPUTED FINDING PARAMETER:PHYSICIAN \n\nThis computed finding uses date ranges like drug findings do, so if\nthe user was an active member of the class anytime during the date\nrange, the computed finding will be true. If you want to know if the\nuser is active as of today, then use T for the beginning and ending\ndate/time.  \n  \n\n\nWhen a user is assigned to an ASU User Class, there can be an\nActivation Date and an Expiration Date. For the purpose of this\ncomputed finding, the date of the finding will be the Activation\nDate. In those cases when there is no Activation Date, 00/00/0000\nwill be displayed as the date of the finding. If a Beginning\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", "
NO
\n"], ["VA-WAS INPATIENT", "
PXRMPDEM
\n", "
WASINP
\n", "
VA-Was Inpatient
\n", "
\nThis multi-occurrence computed finding will search the Patient\nThe date of the finding will be the admission date, unless the\nComputed Finding Parameter is set to "DISCH," in which case the\ndischarge date will be used. If you want to use discharge date as\nthe finding date, in the computed finding parameter field, type the\nfollowing:\n COMPUTED FINDING PARAMETER:DISCH\n\nThe "CSUB" values returned by this computed finding are:\n "ADMISSION DATE"\n "ADMISSION WARD"\nMovement File for a list of patient admissions and associated\n "DISCHARGE DATE"\n "DISCHARGE WARD"\n "LENGTH OF STAY"\n\n\n\n\n\n\ndischarges. If the date range defined by the admission date and\ndischarge date overlaps the date range defined by the Beginning\nDate/Time and Ending Date/Time, the admission discharge pair will be\nkept on the list. If the patient's last admission does not have an\nassociated discharge, then the evaluation date will be used in place\nof the discharge date in the overlap calculation.\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-WH PATIENT IS PREGNANT/LACTATING", "
PXRMCWH1
\n", "
PATIS
\n", "
Women's Health Check If Patient is Pregnant or Lactating
\n", "
\nThis computed finding will check if a patient is documented as pregnant \nCaution: This computed finding groups the statuses NOT PREGNANT and DO \nNOT KNOW into a single NOT PREGNANT OR UNKNOWN status. If you need a \nprecise pregnancy status for a patient, use the VA-WH PATIENT \nDOCUMENTATION reminder computed finding.\n \nTo check if the patient is pregnant, set the first caret piece of \nthe COMPUTED FINDING PARAMETER value to PREGNANT.\n \nTo check if the patient is lactating, set the first caret piece \nof the COMPUTED FINDING PARAMETER value to LACTATING.\nor lactating. It will return true if a patient is pregnant/lactating\n \nThe second caret piece of the COMPUTED FINDING PARAMETER value determines \nhow the end date of a pregnancy is calculated when no end date is \nspecified. Setting this piece to DIALOG will set the end date to \ntomorrow's date. Leaving this piece empty will set the end date to the \ndate the NOT PREGNANT status was entered.\n \nThe CONDITION field may make use of the "STATUS" CSUB subscript. This \nsubscript contains a textual representation of the patient's status. When \nthe first caret piece of the COMPUTED FINDING PARAMETER value is PREGNANT,\non a specific date or was pregnant/lactating on at least one day within\npossible values are "PREGNANT" and "NOT PREGNANT OR UNKNOWN". When the\nfirst caret piece of the COMPUTED FINDING PARAMETER value is LACTATING,\npossible values are "LACTATING" and "NOT LACTATING OR UNKNOWN". For\nexample:\n \n  I V(1,"STATUS")="PREGNANT"\na date range. It will return false if the patient was not \npregnant/lactating or the status was unknown on a specific date or for all\ndays within a date range. If no date is specified, the value of TODAY is \nused. You may specify a specific date in either the Beginning Date/Time \nor Ending Date/Time parameters.  \n \n
\n
\n", "
NATIONAL
\n", "
WOMEN VETERANS HEALTH PROGRAM
\n", "", "", "
MULTIPLE
\n", ""], ["VA-FILEMAN DATE", "
PXRMDATE
\n", "
FMDATE
\n", "
VA-FileMan Date
\n", "
\nThe purpose of this computed finding is to allow the creation of a\nFileMan date/time formats and abbreviations. Additionally, you may\nuse the abbreviations T-NY or NOW-NY, where N is an integer and Y\nstands for years.\n\nFor example, setting the COMPUTED FINDING PARAMETER to T-3M would\ngive the finding a date and value of the evaluation date minus three\nmonths.\n\nIf you use a future date, such as T+NY, then EDT must be equal to or\ngreater than T+NY, otherwise the computed finding will be false.\nfinding that has a specific date to be used for comparison purposes\n \nNote that in addition to FileMan dates the global reminder dates\nPXRMDOB (date of birth), PXRMDOD (date of death), and PXRMLAD (last\nadmission date) may also be used. In the case where one of these is\nused and it does not exist, for example no last admission, then the\ncomputed finding will be false.\n\nin a function finding date function.\n\nThis computed finding takes any acceptable FileMan date, via the\nCOMPUTED FINDING PARAMETER, and sets the date of the finding and its\nvalue to that date.\n\nSee the FileMan Getting Started Manual to learn about acceptable\n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", "
YES
\n"], ["VA-SERVICE BRANCH", "
PXRMMSER
\n", "
SBRANCH
\n", "
VA-Service Branch
\n", "
\nThis multiple occurrence computed finding will return service branch\n \nThe default value is "BRANCH".\n\n\ninformation for one or more service periods in the date range.\n \nCSUB data that can be used in a Condition are:\n "BRANCH"\n "DISCHARGE TYPE"\n "ENTRY DATE"\n "SEPARATION DATE"\n "SERVICE COMPONENT"\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-RANDOM NUMBER", "
PXRMMATH
\n", "
RANDOM
\n", "
VA-Random number
\n", "
\nThis computed finding uses the MUMPS $RANDOM function to return\n\nWhere LB is the inclusive lower bound, UB is the inclusive upper\nbound, and NDD is the optional number of decimal digits. LB and UB\nmust be integers and UB must be greater than LB. If these conditions\nare not met then the computed finding will be false.\n\nSome examples:\n  0^500 - integers in the range 0 to 500\n  0^1^1 - numbers in the range 0 to 1 with one decimal place\n-1^1^2 - numbers in the range -1 to 1 with two decimal places\npseudo random numbers as the value. The Occurrence Count is the\n\n***Please note, this CF was developed for use with research program\nconsideration/use. No, clinical uses have been identified at\npresent. Every evaluation of this finding on a given patient will\nyield different results, thus the name RANDOM. Please use caution\nwhen using this Computed Finding in a clinical setting.***\n\nnumber of random numbers that will be returned and the Computed\nFinding Parameter is used to specify the range and optionally the\nnumber of decimal digits; the default is to generate integers, i.e.,\nno decimal digits. The Occurrence Count entry on the finding will be\nan absolute value. Entering an Occurrence Count of 5 or -5 will\nresult in 5 returns. \nThe format of the Computed Finding Parameter is: LB^UB^NDD\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-PCMM PC TEAM AND INSTITUTION", "
PXRMPCMM
\n", "
INSTPCTM
\n", "
VA-PCMM Primary Care Team & Institution
\n", "
\nThis computed finding returns the patient's primary care team and\ninstitution as of the evaluation date.\n\n\n\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-PCMM PRACTITIONERS ASSIGNED TO A PATIENT", "
PXRMPCMM
\n", "
PRPT
\n", "
VA-PCMM Practitioners Assigned to a Patient
\n", "
\nThis multiple valued computed finding returns a list of\n1 - include practitioners who were assigned for the entire date\n    range.\n\nThe default is 0.\n\nFor example, if you want the value of INCLUDE to be 1 then the\ncomputed finding parameter would be:\n\n\npractitioners assigned to a patient in the date range defined by the\n\n\n\nBeginning Date/Time and Ending Date/Time.\n\nThe Computed Finding Parameter can be used to pass the optional\nparameter INCLUDE. The possible values are:\n\n0 - include practitioners who were assigned anytime in the date\n    range.\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-PCMM PATIENTS ASSIGNED TO A PRACTITIONER", "
PXRMPCMM
\n", "
PTPR
\n", "
VA-PCMM Patients Assigned to a Practitioner
\n", "
\nThis list type computed finding returns a list of patients assigned\nParameter field, only patients who are directly linked to that\npractitioner will be included. Any patients that are only associated\nwith that practitioner in a PRECEPTOR role, through an assignment to an\nAssociate Provider, will NOT be included.  \n\nTo get patients who are linked to a Preceptor via an Associate\nProvider, you would need to run a separate report for the Resident\n(Associate Provider) or include an additional entry of the Computed\nFinding with the resident's name or IEN.\n\nto a list of practitioners in the date range defined by\nThe Computed Finding Parameter can also be used to pass the optional\nparameter INCLUDE. If you want to use this parameter, it is passed\nas the second piece of the Computed Finding Parameter. The possible\nvalues of INCLUDE are:\n\n0 - include patients who were assigned anytime in the date range.\n1 - include patients who were assigned for the entire date range.\n\nThe default is 0.\n\nBeginning Date/Time and Ending Date/Time. The Computed Finding\nThe format for the computed finding parameter is:\nPRACTITIONER(s)^INCLUDE\n\nHere is an example of how to specify a list of practitioners, two by\nname and one by IEN:\n\nPROVIDER,ONE;345;PROVIDER,SIX\n\nIn the above example, INCLUDE is not specified so it takes the\ndefault value of 0. To set the value of INCLUDE to 1 with the above\nParameter is used to specify the practitioners. Each\nlist, the computed finding parameter would be:\n\nPROVIDER,ONE;345;PROVIDER,SIX^1\n\n\n\n\n\n\n\npractitioner is separated by a semicolon.\n\n\n\nEither the IEN or the exact name (.01 field) from file #200,\nthe New Person file, can be used. IENs and names can be mixed.\n\nPlease note: When you identify a practitioner in the Computed Finding\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", "
YES
\n"], ["VA-PCMM PATIENTS ASSIGNED TO A TEAM", "
PXRMPCMM
\n", "
PTTM
\n", "
VA-PCMM Patients Assigned to a Team
\n", "
\nThis list type computed finding returns a list of patients assigned\nthe second piece of the Computed Finding Parameter. The possible\nvalues of INCLUDE are:\n\n0 - include patients who were assigned anytime in the date range.\n1 - include patients who were assigned for the entire date range.\n\nThe default is 0.\n\nThe format for the computed finding parameter is:\nTEAM^INCLUDE \nto a team in the date range specified by Beginning Date/Time and\n  \nFor example, if the team is TEAM ONE and you want the value of\nINCLUDE to be 1 then the computed finding parameter would be:\nTEAM ONE^1 \n\n\nEnding Date/Time. If the patient was assigned to the team at anytime\nduring the date range they will be on the list. The Computed Finding\nParameter is used to specify the team. It can be either the IEN or\nthe exact name (.01 field) from file #404.51, the Team file.\n\nThe Computed Finding Parameter can be used to pass the optional\nparameter INCLUDE. If you want to use this parameter, it is passed as\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
LIST
\n", "
YES
\n"], ["VA-PATIENT RECORD FLAG INFORMATION", "
PXRMPRF
\n", "
GETINF
\n", "
VA-Patient Record Flag Information
\n", "
\nThis multiple type computed finding returns information about a\nthe date range.\n\nThe following "CSUBS" are available:\n\n   "ACTION" The action\n  "APPRVBY" Approved by\n"ASSIGN DT" Date and time the flag was assigned\n "CATEGORY" The category\n     "DATE" Date of the action\n "FLAGTYPE" Flag type\nspecified patient record flag for a patient. The Computed Finding\n"REVIEW DT" Review date\n"TIU TITLE" TIU title associated with the flag\n\n\n\n\n\nParameter is used to specify the flag in the following format:\nFLAG NAME^FLAG TYPE\n\nWhere FLAG NAME is the exact name of the flag and FLAG TYPE is L for\nlocal or N for national. FLAG TYPE is optional and defaults to L.\n\nThe computed finding will be true if the flag was active at any time in\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", "
YES
\n"], ["VA-PATIENT RECORD FLAG LIST", "
PXRMPRF
\n", "
GETLST
\n", "
VA-Patient Record Flag List
\n", "
\nThis list type computed finding returns a list of all patients who\nhave a specified record flag active any time in the date range.\n\nThe Computed Finding Parameter is used to specify the flag in the\nfollowing format: FLAG NAME^FLAG TYPE \n  \nWhere FLAG NAME is the exact name of the flag and FLAG TYPE is L for\nlocal or N for national. FLAG TYPE is optional and defaults to L.\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", "
YES
\n"], ["VA-IMMUNIZATION AND LOCATION LOT INFO", "
PXRMCIMM
\n", "
LOTINFO
\n", "
IMMUNIZATION LOT INFO
\n", "
\nTHIS COMPUTED FINDING ONLY WORKS WHEN USED IN A REMINDER DIALOG BRANCHING \n \nOutput values\nV("LOT NUMBER")=\nV("MANUFACTURER")=""\nV("EXIRATION DATE")=""\nV("STARTING COUNT")=""\nV("DOSES UNUSED")=""\nV("NDC CODE")=\nLOGIC FUNCTIONALITY.\n \nThis computed finding will return the lot information for either a \nspecific vaccine or for vaccine associated with a specific CVX code.\n \nInput Value\nI:VACCINE NAME\nC:CVX CODE\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
MULTIPLE
\n", "
YES
\n"], ["VA-PROJECT ARCH ELIGIBILITY", "
PXRMARCH
\n", "
ELIG
\n", "
VA-ARCH Eligibility
\n", "
\nThis multi-occurrence computing finding returns the patient's Project ARCH\neligibility status for instances in the ARCH dataset that are in the\ndate range defined by Beginning Date/Time and Ending Date/Time.\n\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-MST STATUS", "
PXRMMST
\n", "
STATUS
\n", "
VA-MST Status
\n", "
\nThis computed finding uses $$GETSTAT^DGMSTAPI, DBIA #2716, to obtain a\npatient's MST status information.\n
\n
\n", "
NATIONAL
\n", "
MENTAL HEALTH SERVICES AND WOMEN VETERANS HEALTH PROGRAM
\n", "", "
\n
\n\n
\n", "", ""], ["VA-PROJECT ARCH ELIGIBILITY LIST", "
PXRMARCH
\n", "
LIST
\n", "
VA-Project ARCH Patient List
\n", "
\nThis list computed finding returns a list of all patients who were\nProject ARCH eligible in the date range defined by Beginning\nDate/Time and Ending Date/Time.\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", ""], ["VA-OEF/OIF SERVICE (LIST)", "
PXRMMSER
\n", "
OEIF
\n", "
VA-OEF/OIF Service List Patient List
\n", "
\nThis list type computed finding builds a list of patients who have\nthese two time periods. In other words, if patients had service\nat any time in the date range specified by BDT and EDT, they will be\nincluded.\n \nThe Computed Finding Parameter can be used to include only patients\nwho had service at a specific location. The locations can be OEF,\nOIF, or ANY. The value ANY, which is the default, will include all\nlocations. Each location is separated by the "^" character. For\nexample, to include patients who had OEF, service the Computed\nFinding Parameter is:\nbeen deployed in Operation Enduring Freedom (OEF) or Operation Iraqi\n OEF\nTo include patients who had either OEF or OIF service, the Computed\nFinding Parameter is:\n OEF^OIF\nTo include patients who had UNK, service the Computed Finding Parameter is:\n UNK\n\n\n\n\nFreedom (OIF). If the location was either OEF or OIF, but cannot be\ndisclosed/determined, then it is listed as unknown (UNK).\n  \nDate range searching is done by looking for an overlap in the\nperiod defined by Beginning Date/Time (BDT) and Ending Date/Time\n(EDT), with the period defined by OEF/OIF From and To Dates. In order\nfor a patient to be included on the list, there must be an overlap of\n
\n
\n", "
NATIONAL
\n", "", "", "", "
LIST
\n", ""], ["VA-PCMM MHTC", "
PXRMPCMM
\n", "
MHTC
\n", "
VA-PCMM Mental Health Treatment Coordinator
\n", "
\nThis computed finding returns the patient's current Mental Health\n\nMHTC - Mental Health Treatment Coordinator\nROLE - role\nTEAM - team\nTEAM POSITION - team position\n\nTreatment Coordinator (MHTC). The Scheduling API this computed\nfinding uses does not take a date as a parameter so it only returns\nthe MHTC as of the actual calendar date. Therefore, this computed\nfinding cannot be used to determine if the patient had an MHTC\nsometime in the past.\n\nThe default value of the computed finding is the MHTC. The following\nadditional CSUBs are returned:\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", ""], ["VA-INPATIENT/OUTPATIENT FINDINGS", "
PXRMIOPT
\n", "
IOPT
\n", "
VA-Inpatient/Outpatient Findings
\n", "
\nThis multi-occurrence computed finding is used to determine if the date of a\nThe Computed Finding Parameter has the format: FINDING^INP/OUT^FINDING\nMODIFIER. FINDING is specified in a manner like that used when creating a\nreminder definition. The first two characters are one of the two-character\nabbreviations for finding types followed by a period, followed by the exact\nname of the finding or its internal entry number. Some examples:\n  HF.CURRENT SMOKER USE^INP\n  HF.2^OUT\n  MH.PHQ-2+I9^OUT^MH SCALE:1012\n  DG.ASPIRIN^OUT^RXTYPE:O\n\nfinding is in a period where the patient was an inpatient. First, it searches\nThe INP or OUT piece of the parameter works as follows:\n INP - Any finding occurrences that are in an admission period will be a true\n       occurrence of the computed finding with the date set to the finding\n       date. This is the default value.\n OUT - Any finding occurrences that are outside an admission period will be a\n       true occurrence of the computed finding with the date set to the\n       finding date.\n\nThe FINDING MODIFIER piece is optional, it provides a way to input finding\nmodifiers that cannot be set when the computed finding is added as a finding.\nfor up to NOCC true occurrences of the finding in the date range specified by\nThe format is MODIFIER:VALUE where modifier is the exact name of the modifier.\n\nThe allowed modifiers are:\n  USE INACTIVE PROBLEMS\n  WITHIN CATEGORY RANK\n  MH SCALE\n  RXTYPE\n  USE START DATE\n  INCLUDE VISIT DATA\n\nBeginning Date/Time and Ending Date/Time, where NOCC is the Occurrence Count.\nExamples:\nUSE INACTIVE PROBLEMS:1\nWITHIN CATEGORY RANK:1\nMH SCALE:1012\nRXTYPE:O\nUSE START DATE:1\nINCLUDE VISIT DATE:1\n\nBe aware that the values for these modifiers are not checked to determine if\nthey are valid, you must make sure of that when setting up this computed\nNext, it finds up to 99 admission/discharge pairs in the date range. The final\nfinding.  \n\nUSE INACTIVE PROBLEMS - 1 for YES or 0 for NO, the default is 0.\nWITHIN CATEGORY RANK - The default value will be 0, a non-zero value can be\n  used if needed.\nMH SCALE - Enter the scale number.\nRXTYPE - The possible values for RXTYPE are "I" for inpatient, "N" for\n  non-VA meds, and "O" for outpatient. RXTYPE can be any combination of these\n  such as "NO" which will search for non-VA meds and outpatient medications.\n  If RXTYPE is blank it is equivalent to a value of "INO"\nstep is to determine if any of the finding dates are within any of the\nUSE START DATE - 1 for YES or 0 for NO.  The default is 0\nINCLUDE VISIT DATA - 1 for YES or 0 for NO.  The default is 0\n\nNote that for health factor findings, Within Category Rank will default to 0\nso all the occurrences within the date range will be included, not just the\nmost recent one.\n\nThis computed finding does not support reverse date ordering.\n\n\ninpatient episodes. The true or false value of this computed finding depends on\n\nthe input parameters as explained below.\n\n
\n
\n", "
NATIONAL
\n", "", "", "", "
MULTIPLE
\n", "
YES
\n"], ["VA-ELIGIBILITY", "
PXRMMSER
\n", "
ELIG
\n", "
VA-Eligibility
\n", "
\nThis computed finding calls the API: ELIG^VADPT to get a list of the patient's\nA patient's primary eligibility code is returned in VAEL(1), therefore to\ndetermine if the patient's primary eligibility code is Service Connected\n50-100%, the Computed Finding Parameter is: VAEL(1)["SERVICE CONNECTED 50% to\n100%". \n \nSecondary eligibilities are returned in VAEL(1,N), where N is the internal\nentry number of the eligibility in file #8. Because this file is\nnon-standard, the subscripts for various eligibilities can be different\nfrom site-to-site. To make secondary eligibilities usable, \nVAEL("SE",ELGIBILTY) is generated, where ELIGIBILITY is the name of the \neligibilities which are returned in the array VAEL. Note that ELIG^VADPT is\neligibility from file #8.\n \nYou can use multiple criteria: VAEL(1)["SERVICE CONNECTED 50% to\n100%",VAEL("SE,"PRISONER  OF WAR"). In this example, the finding would be\ntrue if the patient is service connected 50% to 100% AND has prisoner of\nwar as a secondary eligibilty.0\n \nThe Eligibility Logic must be written as a valid MUMPS statement. It can\ncontain MUMPS operators such as $P, &, !, [, and =.\n \ndocumented in the PIMS Technical Manual. Any of the returned VAEL values can\nIn addition to specifying the Eligibility Logic, the Computed Finding\nParameter can be used to pass optional text that will be displayed in the\nClinical Maintenance Output if the Eligibility Logic evaluates to true. The\nformat is: Eligibility Logic|Text\n \nThe documentation of ELIG^VADPT in the PIMS Technical Manual is not completely\nup to date, for example, it shows VAEL(1)="1^SERVICE CONNECTED 50-100%" when\nwhat is actually returned is VAEL(1)="1^SERVICE CONNECTED 50% to 100%". You\ncan use Reminder Test to see what is returned in VAEL for a patient. When a\nreminder definition, that has VA-ELIGIBILITY as a finding, is evaluated using\nbe used in Eligibility Logic, passed via the Computed Finding Parameter, to\nReminder Test a list of the VAEL values returned by ELIG^VADPT will be\ndisplayed.\n \nThe PIMS Technical Manual can be found in the VistA Documentation Library\n(www.domain.ext/vdl) in the ADT section. \ncreate a finding that will be true if the patient has certain eligibilities.\nIt can be very simple, such as determining if the patient is a Vietnam\nveteran. In this case the Computed Finding parameter would be:\nVAEL(2)["VIETNAM ERA".\n \n
\n
\n", "
NATIONAL
\n", "", "", "", "
SINGLE
\n", "
YES
\n"], ["VA-VETERAN", "
PXRMMSER
\n", "
VETERAN
\n", "
VA-Patient is a Veteran
\n", "
\nThis single occurrence computed finding is true if the patient is\na veteran and false otherwise.\n\nThere are no values that can be used in a Condition.\n\n
\n
\n", "
NATIONAL
\n", "", "", "
\n
\n\n
\n", "
SINGLE
\n", ""]]}