Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables  | All
Print Page as PDF
Global: ^DG(391

Package: Registration

Global: ^DG(391


Information

FileMan FileNo FileMan Filename Package
391 TYPE OF PATIENT Registration

Description

Directly Accessed By Routines, Total: 52

Package Total Routines
Registration 35 DG53114T    DG876PST    DGENL    DGENLCD    DGENLEH    DGENLUP    DGENUPL3    DGENUPL4
DGLOCK    DGMTHL    DGOTHFS2    DGPMVBUR    DGPPDRPT    VADPT4    VAFHAPV1    ^DG(391
DGRP    DGRP11    DGRP7    DGRPC    DGRPC1    DGRPC2    DGRPDB    DGRPDD
DGRPE1    DGRPP    DGRPV    DGRRLU2    DGRRLU6    DGRRLUA    DGRRPSEE    DGSEC
DPTLK2    VAFHCPV    VAFHLZE1    
Integrated Billing 4 IB20PT87    IB20PT8B    IBAECB1    IBXBCR2    
Automated Medical Information Exchange 3 DVBCXFR2    DVBCXFRB    DVBCXFRC    
Order Entry Results Reporting 2 ORWPCE    ORWPT    
Scheduling 2 SDPPAT1    SDROUT2    
Clinical Information Resource Network 1 RGRSPARS    
DSS Extracts 1 ECXUTL5    
Income Verification Match 1 IVMZ7CR    
Master Patient Index VistA 1 MPIFRES    
Outpatient Pharmacy 1 PSOMLLD2    
VBECS 1 VBECLU    

Accessed By FileMan Db Calls, Total: 12

Package Total Routines
Registration 7 DG53114T    DGADDLST    DGRP1152A    DGRP6CL    DGRP6EF    DGRPCF    DGRPU    
Automated Information Collection System 1 IBDFN    
Clinical Procedures 1 MDRPCW    
E Claims Management Engine 1 BPSVRX2    
Medicine 1 MCARAM6    
VistA Integration Adapter 1 VIABRPC    

Pointed To By FileMan Files, Total: 1

Package Total FileMan Files
Registration 1 PATIENT(#2)[391]    

Pointer To FileMan Files, Total: 1

Package Total FileMan Files
Registration 1 IDENTIFICATION FORMAT(#8.2)[8.2]    

Fields, Total: 34

Field # Name Loc Type Details
.01 NAME 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  SEP 19, 2012
  • HELP-PROMPT:  Answer must be 3-30 characters in length.
  • DESCRIPTION:  
    This field contains the names of the various types of patients seen at VA facilities. This file should not be added to or altered or it could affect daily operations of the MAS software.
    UNEDITABLE
  • CROSS-REFERENCE:  391^B
    1)= S ^DG(391,"B",$E(X,1,30),DA)=""
    2)= K ^DG(391,"B",$E(X,1,30),DA)
.02 IGNORE VETERAN CHECKS? 0;2 SET
************************REQUIRED FIELD************************
  • '0' FOR NO;
  • '1' FOR YES;

  • DESCRIPTION:  If this particular type of patient is non-veteran, but the patient can respond to questions meant for veterans, respond yes. An example would be MILITARY RETIREE. These patients are seen as non-veterans, but may have
    veteran periods of service, prisoner of war dates, etc.
.03 *INFO TO ASK 0;3 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1)!'(X?.N) X
  • LAST EDITED:  NOV 12, 1991
  • HELP-PROMPT:  ANSWER MUST BE 1-40 CHARACTERS IN LENGTH
  • DESCRIPTION:  
    This field is no longer used by the MAS package. It will be removed in a future release.
.04 MAKE RECORD SENSITIVE? 0;4 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  SEP 29, 1988
  • HELP-PROMPT:  Answer YES if you want this record automatically made sensitive when using the registration screens.
  • DESCRIPTION:  If it is desirable to automatically make a record sensitive if the patient has this patient type, answer yes here. An example would be EMPLOYEE. Any record for a patient added to your system with a patient type of
    EMPLOYEE will automatically be recorded as sensitive in the security system.
.05 VETERAN? 0;5 SET
************************REQUIRED FIELD************************
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 25, 1992
  • HELP-PROMPT:  Enter 1 (or yes) if patients of this type are veterans. Otherwise, respond 0 (or no).
  • DESCRIPTION:  Enter YES (or 1) at this prompt if patients of this patient type are veterans. Respond NO otherwise. This information is necessary to determine whether certain screens may be turned off. If this is a non-veteran patient
    type, but patients with this patient type COULD be veterans, respond YES to the IGNORE VETERAN CHECKS? prompt (field .02).
  • CROSS-REFERENCE:  ^^TRIGGER^391^9
    1)= X ^DD(391,.05,1,1,1.3) I X S X=DIV S Y(1)=$S($D(^DG(391,D0,"S")):^("S"),1:"") S X=$P(Y(1),U,9),X=X S DIU=X K Y S X=DIV S X=1 X ^DD(391,.05,1,1,1.4)
    1.3)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(0)=X S Y(1)=$C(59)_$S($D(^DD(391,.05,0)):$P(^(0),U,3),1:"") S X=$P($P(Y(1),$C(59)_Y(0)_":",2),$C(59),1)="YES"
    1.4)= S DIH=$S($D(^DG(391,DIV(0),"S")):^("S"),1:""),DIV=X S $P(^("S"),U,9)=DIV,DIH=391,DIG=9 D ^DICR:$N(^DD(DIH,DIG,1,0))>0
    2)= Q
    CREATE CONDITION)= VETERAN?="YES"
    CREATE VALUE)= S X=1
    DELETE VALUE)= NO EFFECT
    FIELD)= SHOW INCOME SCREENING SCREEN
    This trigger will automatically stuff YES into the SHOW INCOME SCREENING SCREEN field if this field (VETERAN?) is answered YES.
3 SHOW CONTACT SCREEN? S;3 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAY 31, 1988
  • DESCRIPTION:  
    Answer yes if you would like to have the contact screen displayed for any patient of this patient type. This screen contains names and addresses of next of kin, emergency contacts, and designees.
4 *SHOW EMPLOYMENT SCREEN? S;4 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 24, 1992
  • HELP-PROMPT:  This field is no longer used. The employment screen will now for all patients.
  • DESCRIPTION:  This field is no longer used by the MAS package. Due to the increased need for employment data due to billing, the employment screen can no longer be turned off. This field will be removed in a future release of the MAS
    package.
5 *SHOW INSURANCE SCREEN? S;5 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  NOV 12, 1991
  • DESCRIPTION:  
    This field is no longer used by the MAS package (the insurance screen is now displayed for ALL patients). It will be removed in a future release.
6 SHOW SERVICE SCREEN? S;6 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAY 31, 1988
  • DESCRIPTION:  Answer yes if you would like the service screen to display for all patients added to your system with this patient type. The service record screen contains data about service history, prisoner of war status, combat,
    Vietnam service, agent orange and ionizing radiation exposure, military retirement/disability, and service dental history. For non-veterans, you may choose not to display this screen.
7 *SHOW MONETARY SCREEN? S;7 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  NOV 12, 1991
  • DESCRIPTION:  
    This field is no longer used by the MAS package. It will be removed in a future version of MAS.
8 SHOW FAMILY INFO SCREEN S;8 SET
************************REQUIRED FIELD************************
  • '0' FOR NO;
  • '1' FOR YES;

  • INPUT TRANSFORM:  D FAMINF^DGRPDD
  • LAST EDITED:  JUN 29, 1992
  • HELP-PROMPT:  Enter yes to display the family demographic screen during registration.
  • DESCRIPTION:  To display the family demographic screen during registration (screen 8), respond yes here. You must answer yes for NSC patients as income screening is required for all non-service connected veterans. You may chose to
    show this screen for service connected patients or non-veterans.
    The family demographic screen holds the name, SSN, date of birth, and sex for all dependents of the patient.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
8.2 ID FORMAT 8.2;1 POINTER TO IDENTIFICATION FORMAT FILE (#8.2) IDENTIFICATION FORMAT(#8.2)

  • LAST EDITED:  NOV 06, 1989
  • DESCRIPTION:  
    This field contains a pointer to the IDENTIFICATION FORMAT file (#8.2). This field will contain the default ID format for all patients with this patient type. For most VA purposes, this will be the SSN.
9 SHOW INCOME SCREENING SCREEN S;9 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • INPUT TRANSFORM:  D INCSCR^DGRPDD
  • LAST EDITED:  JUN 29, 1992
  • HELP-PROMPT:  Enter yes if you want the income screening screen to show for all patients of this patient type.
  • DESCRIPTION:  Enter yes if the income screening screen should be displayed for this type of patient. Answer no otherwise. You will be unable to edit this question if the VETERAN? prompt (field .05) is answered yes. This data must be
    collected for all veterans seen. This screen will contain information on a patient's income for the previous calendar year. It will also contain information on the patient's spouse and dependents. This data will, in
    turn, be used for IRS matching.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
    TRIGGERED by the VETERAN? field of the TYPE OF PATIENT File
10 SHOW INELIGIBLE SCREEN S;10 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 25, 1992
  • DESCRIPTION:  
    Enter yes if you wish the ineligible data screen to show for all patients of this patient type. This screen contains information on the a patient's ineligibility for care and data on missing patients.
11 SHOW VERIFICATION SCREEN? S;11 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 25, 1992
  • HELP-PROMPT:  If you want users to be able to see the verification screen for this type of patient, answer yes. Otherwise, respond no.
  • DESCRIPTION:  Enter yes if you wish the service verification screen to show for all patients of this patient type. This screen contains information on the verification of eligility and service record data. It also contains data on VA
    rated disabilities.
41 *EDIT APPLICANT EMPLOYER? E;41 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 26, 1992
  • DESCRIPTION:  
    Respond yes if you want users to be able to edit the employer data for the applicant (veteran). If you say no, this information will appear on the screen display, but will not be editable.
42 *EDIT SPOUSE'S EMPLOYER? E;42 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 26, 1992
  • DESCRIPTION:  
    Respond yes if you want users to be able to edit the spouse's employer information for this type of patient. If you say no, this information will appear on the screen display, but will not be editable.
61 *EDIT SERVICE HISTORY? E;61 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  
    Enter yes if you wish to allow users to edit the service history data for this type of patient. If you say no, this information will appear on the screen display, but will not be editable.
62 *EDIT PRISONER OF WAR DATA? E;62 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  Enter yes if you wish to allow users to edit the prisoner of war data (from/to dates, where imprisoned, etc.) for this type of patient. If you say no, this information will appear on the screen display, but will not be
    editable.
63 *EDIT COMBAT DATA? E;63 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  Enter yes if you want the users to be able to edit combat data for patients of this type. This data includes combat from/to dates as well as where the combat occurred. If you respond no, this data will appear on the
    screen, but will not be editable.
64 *EDIT VIETNAM SERVICE DATA? E;64 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  Enter yes if you want users to be able to edit Vietnam service data for patients of this type. This data includes the dates from and to which the veteran served in Vietnam. If you respond no, this data will appear on the
    screen, but will be uneditable.
65 *EDIT AGENT ORANGE DATA? E;65 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  Enter yes if you want users to be able to edit agent orange exposure data for patients of this type. This data includes the dates of test for AO exposure. If you respond no, this data will appear on the screen, but will
    be uneditable.
66 *EDIT RADIATION EXPOSURE DATA? E;66 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  Enter yes if you want to be able to edit radiation exposure data for patients with this patient type. This data includes dates of test for radiation. If you respond no, this data will appear on the screen, but will be
    uneditable.
67 *EDIT MILITARY DISABILITY DATA E;67 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  
    Enter yes if you want the users to be able to edit data relating to military disability for patients of this type. If you respond no, the data element will appear on the screen, but will not be editable.
68 *EDIT DENTAL HISTORY DATA? E;68 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  APR 23, 1992
  • DESCRIPTION:  
    Enter yes if you want users to be able to edit data relating to dental history in service if the patient is of this type. If you respond no, the data element will appear on the screen, but will not be editable.
71 *EDIT VA MONETARY BENEFITS? E;71 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  NOV 12, 1991
  • DESCRIPTION:  
    This field is no longer used by the MAS package and will be removed in a future version.
72 *EDIT OTHER MONETARY BENEFITS? E;72 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  NOV 12, 1991
  • DESCRIPTION:  
    This field is no longer used by the MAS package and will be removed in a future version.
74 EDIT SC CONDITIONS PER PT? E;74 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  DEC 04, 1991
  • HELP-PROMPT:  Enter YES if you want to allow the user to edit SC conditions as stated by the applicant.
  • DESCRIPTION:  If the user should be allowed to edit SC conditions as stated by the applicant for patients of this patient type, answer yes here. Otherwise respond no. This data appears on registration screen 7 (Eligibility Status
    Data).
83 *EDIT SC CONDITIONS PER PT? E;83 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  NOV 13, 1991
  • DESCRIPTION:  Respond yes if you want to give users the ability to edit service conditions as stated by the patient for patients of this patient type. If you respond no, the question will appear on the screen, but it will not be
    editable.
    Note: Due to a change in screen numbering, this field is being *'d for
    deletion and will no longer be used (affective with installation
    of this version). A new field 73 has been added which is the
    same prompt. This is in keeping with the present field numbering
    sequence.
91 *EDIT INELIGIBLE DATA? E;91 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 25, 1992
  • DESCRIPTION:  
    Enter yes if you want users to be allowed to edit data about a patients eligibility for patients of this patient type. If you respond no, the question will appear on the screen, but it will not be editable.
92 *EDIT MISSING DATA? E;92 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 25, 1992
  • DESCRIPTION:  
    Enter yes if you want the user to be allowed to edit data on missing veterans for patients of this patient type. If you respond no, the question will appear on the screen, but will not be editable.
101 EDIT INELIGIBLE DATA? E10;1 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 25, 1992
  • HELP-PROMPT:  Enter yes if you want users to be allowed to edit data about a patients ineligiblility for care.
  • DESCRIPTION:  If, when editing data for patients of this type, you want users to be able edit data about a patient's ineligibility for care, respond yes here. If you respond no, the data will display on the screen, but will not be
    editable by the users.
  • TECHNICAL DESCR:  This data has been placed on the E10 node. Because FM does not allow more than 100 pieces on a node, it must be kept on a separate node. The registration code will have to check if screen number is 10 or greater and
    check the E10 node rather than the E node.
102 EDIT MISSING DATA? E10;2 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  SEP 19, 2012
  • HELP-PROMPT:  If you want users to be able to edit the missing data for patients of this type, answer yes.
  • DESCRIPTION:  
    If, for patients of the specified patient type, you want users to be able to edit data about missing veterans, answer yes. If you respond no, the user will see the screen, but will not be able to edit the missing data.
  • TECHNICAL DESCR:  Because FM will not allow more than 100 pieces on a node, editable items on screen 10 or greater had to be moved to the new E10 node. The fields were numbered so that the field number was equal to screen#_item# and the
    piece position on the node was equal to the field number. Because the missing data is on screen 10, it is not possible to put it on the same node (because there can not be more than 100 pieces). Registration will need to
    check to see if the screen is 10 or greater and, if so, look at this new node.
200 NEW PATIENT INPUT DR DR;E1,240 FREE TEXT

  • INPUT TRANSFORM:  W:$S('$D(DUZ(0)):1,DUZ(0)'="@":1,1:0) !?5,"Must have Programmer Access!!! " K:$S('$D(DUZ(0)):1,DUZ(0)'="@":1,1:0) X I $D(X) K:$L(X)>240!($L(X)<2) X I $D(X) D ^DIM
  • LAST EDITED:  JUN 01, 1991
  • HELP-PROMPT:  Enter the fields (DR string) to be asked for new patients of this type who are entered into the system. Must have programmer access!!
  • DESCRIPTION:  This field contains a line of code which sets the variable DR for use in a filemanager enter/edit (DIE) call. In order to add to this field or edit what is in it, you must have programmer mode.
    This DR string should contain a listing of the fields you wish to ask whenever a patient of this patient type is added to the system. These fields would be in addition to the prompts normally given for NAME, SSN, DOB,
    VET?, etc. If blank, only the standard questions will be asked.
    DELETE AUTHORITY: @
    WRITE AUTHORITY: @
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

Found Entries, Total: 10

NAME: SC VETERAN    NAME: ALLIED VETERAN    NAME: MILITARY RETIREE    NAME: ACTIVE DUTY    NAME: COLLATERAL    NAME: EMPLOYEE    NAME: NSC VETERAN    NAME: NON-VETERAN (OTHER)    
NAME: TRICARE    NAME: NEWBORN OF VETERAN    

ICR, Total: 2

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #649
  • Integrated Billing
  • Automated Information Collection System
  • Clinical Procedures
  • VistA Integration Adapter
    		•  IGNORE VETERAN CHECKS? (.02).
    Access: Read w/Fileman
    ICR #2966
  • Order Entry Results Reporting
    		•  IGNORE VETERAN CHECKS? (.02).
    Access: Direct Global Read & w/Fileman

    External References

    Name Field # of Occurrence
    ^DICR .05(XREF 1n1.4)
    ^DIM 200+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^DD( .05(XREF 1n1.4)
    ^DD(391 .05(XREF 1S), .05(XREF 1n1.3)
    ^DG(391 - [#391] .01(XREF 1S), .01(XREF 1K), .05(XREF 1S), .05(XREF 1n1.4)

    Naked Globals

    Name Field # of Occurrence
    ^("S" .05(XREF 1S), .05(XREF 1n1.4)
    ^(0 .05(XREF 1n1.3)

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> D0 .05(XREF 1S), .05(XREF 1n1.3)
    >> DA .01(XREF 1S), .01(XREF 1K), .05(XREF 1n1.3)
    >> DIG .05(XREF 1n1.4)
    >> DIH .05(XREF 1n1.4)
    >> DIU .05(XREF 1S)
    DIV .05(XREF 1S), .05(XREF 1n1.3), .05(XREF 1n1.4)
    DIV(0 .05(XREF 1n1.3), .05(XREF 1n1.4)
    DUZ(0 200+1
    U .05(XREF 1S), .05(XREF 1n1.3), .05(XREF 1n1.4)
    X .01+1!, .01(XREF 1S), .01(XREF 1K), .03+1!, .05(XREF 1S), .05(XREF 1n1.3), .05(XREF 1n1.4), 200+1!
    Y .05(XREF 1S)
    Y(0 .05(XREF 1n1.3)
    Y(1 .05(XREF 1S), .05(XREF 1n1.3)
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables  | All