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 |  Pointer To FileMan Files |  Fields |  ICR |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All
Print Page as PDF
Global: ^DGCN(391.91

Package: Registration

Global: ^DGCN(391.91


Information

FileMan FileNo FileMan Filename Package
391.91 TREATING FACILITY LIST Registration

Description

Directly Accessed By Routines, Total: 40

Package Total Routines
Registration 16 DG53800P    DG53856P    DGROUT    DPTLK    VAFCOTFU    VAFCPDAT    VAFCQRY1    VAFCQRY2
VAFCRAUD    VAFCTFIN    VAFCTFMF    VAFCTFU    VAFCTFU1    VAFCTFU3    ^DGCN(391.91    VAFCTFU2
Master Patient Index VistA 8 MPIFA31I    MPIFBT2    MPIFCMRP    MPIFEXT    MPIFQUE4    MPIFRCMP    MPIFUTL    MPIFVTQ
Clinical Information Resource Network 7 RGDRM02    RGFICLN    RGI15PST    RGMTMONX    RGMTUT01    RGRPDAT    RGRSDYN1    
Scheduling 5 SDWLE11    SDWLE6    SDWLFUL1    SDWLRP1    SDWLRP4    
Automated Medical Information Exchange 1 DVBCENQ    
Enterprise Health Management Platform 1 HMPTFU2    

Accessed By FileMan Db Calls, Total: 9

Package Total Routines
Registration 6 DG53800P    VAFCOTFU    VAFCPDAT    VAFCQRY2    VAFCTFMF    VAFCTFU    
Clinical Information Resource Network 2 RGDRM02    RGMTMONX    
Master Patient Index VistA 1 MPIFBT2    

Pointer To FileMan Files, Total: 3

Package Total FileMan Files
Registration 2 PATIENT(#2)[.01]    ADT/HL7 EVENT REASON(#391.72)[.07]    
Kernel 1 INSTITUTION(#4)[.02]    

Fields, Total: 9

Field # Name Loc Type Details
.01 PATIENT 0;1 POINTER TO PATIENT FILE (#2)
************************REQUIRED FIELD************************
PATIENT(#2)

  • LAST EDITED:  DEC 02, 1999
  • HELP-PROMPT:  Enter the patient name, between 1 and 30 characters.
  • DESCRIPTION:  
    This is a pointer to the patient in question that was seen at this treating facility.
  • CROSS-REFERENCE:  391.91^B
    1)= S ^DGCN(391.91,"B",$E(X,1,30),DA)=""
    2)= K ^DGCN(391.91,"B",$E(X,1,30),DA)
  • CROSS-REFERENCE:  391.91^APAT^MUMPS
    1)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,2) I TMPA S ^DGCN(391.91,"APAT",$E(X,1,30),TMPA,DA)=""
    2)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,2) I TMPA K ^DGCN(391.91,"APAT",$E(X,1,30),TMPA,DA)
    This cross-reference is used to uniquely identify the institutions where the patient has been treated.
  • CROSS-REFERENCE:  391.91^AINST^MUMPS
    1)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,2) I TMPA S ^DGCN(391.91,"AINST",TMPA,$E(X,1,30),DA)=""
    2)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,2) I TMPA K ^DGCN(391.91,"AINST",TMPA,$E(X,1,30),DA)
    This cross-reference is used to uniquely identify the patients for a particular institution.
  • RECORD INDEXES:  AEVN (#12), AKEY (#1018), AKEY2 (#1019)
.02 INSTITUTION 0;2 POINTER TO INSTITUTION FILE (#4)
************************REQUIRED FIELD************************
INSTITUTION(#4)

  • LAST EDITED:  MAY 21, 2012
  • HELP-PROMPT:  Enter the institution where the patient was seen, between 1 and 30 characters.
  • DESCRIPTION:  
    This is the institution where the patient was treated.
  • AUDIT:  YES, ALWAYS
    WRITE AUTHORITY:  @
    UNEDITABLE
  • CROSS-REFERENCE:  391.91^C
    1)= S ^DGCN(391.91,"C",$E(X,1,30),DA)=""
    2)= K ^DGCN(391.91,"C",$E(X,1,30),DA)
    This is a lookup cross-reference on the institution.
  • CROSS-REFERENCE:  391.91^APAT2^MUMPS
    1)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,1) I TMPA S ^DGCN(391.91,"APAT",TMPA,$E(X,1,30),DA)=""
    2)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,1) I TMPA K ^DGCN(391.91,"APAT",TMPA,$E(X,1,30),DA)
    This cross-reference is used to uniquely identify the institutions at which a patient has been seen.
  • CROSS-REFERENCE:  391.91^AINST2^MUMPS
    1)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,1) I TMPA S ^DGCN(391.91,"AINST",$E(X,1,30),TMPA,DA)=""
    2)= N TMPA S TMPA=$P($G(^DGCN(391.91,DA,0)),U,1) I TMPA K ^DGCN(391.91,"AINST",$E(X,1,30),TMPA,DA)
    This cross-reference is used to uniquely identify the patients for a particular institution.
  • RECORD INDEXES:  AISS (#878), AKEY (#1018), ASID (#737)
.03 DATE LAST TREATED 0;3 DATE

  • INPUT TRANSFORM:  S %DT="EST" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  SEP 09, 1996
  • HELP-PROMPT:  Enter the date the patient was treated at the facility.
  • DESCRIPTION:  
    This is the date the patient was treated at the facility.
.07 ADT/HL7 EVENT REASON 0;7 POINTER TO ADT/HL7 EVENT REASON FILE (#391.72) ADT/HL7 EVENT REASON(#391.72)

  • LAST EDITED:  DEC 02, 1999
  • HELP-PROMPT:  Enter the reason for the event experienced by the patient at this treating facility.
  • DESCRIPTION:  
    This field tracks the reason for an event experienced by a patient at a given facility.  Some event reasons might be patient admission, patient discharge, etc.
  • RECORD INDEXES:  AEVN (#12)
.08 ROI SIGNED INDICATOR 0;8 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  DEC 07, 2011
  • HELP-PROMPT:  Enter YES when the Release of Information has been submitted to MHV.
  • DESCRIPTION:  The MyHealtheVet (MHV) application allows veterans to create an online account. Once created, the veteran can choose to share the information in their personal health record with all their health care providers, inside
    and outside the VA.
    A registered MHV user completes a remote proofing process with MHV and when that process is finalized, an update message is sent to the Master Veteran Index (MVI) to set the ROI SIGNED INDICATOR field to YES.  MVI, in
    turn, updates this same field on VistA.  This allows the MHV system to be viewed via CPRS Remote Data Views and/or VistAWeb, providing the ability to view the electronic medical record using the on-line MyHealtheVet web
    portal.
.09 SOURCE ID TYPE 0;9 SET
  • 'NI' FOR National unique individual identifier;
  • 'PI' FOR Patient internal identifier;
  • 'PN' FOR Person number;
  • 'EI' FOR Employee number;
  • 'SS' FOR Social Security number;
  • 'NPI' FOR National provider identifier;

  • LAST EDITED:  MAY 21, 2012
  • HELP-PROMPT:  Enter the SOURCE ID TYPE value for this entry.
  • DESCRIPTION:  The SOURCE ID TYPE field defines the data source for this entry. The source ID type is a reference to the HL7 Table 0203, Identifier Type, and the VA Identity Management user defined values: NI (National Identifier), PI
    (Patient Identifier), PN (Person Number), EI (Employee Identifier), SS (Social Security Number), and NPI (National Provider Identifier).
  • AUDIT:  YES, ALWAYS
  • RECORD INDEXES:  AISS (#878), AKEY (#1018)
10 ASSIGNING AUTHORITY 2;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>70!($L(X)<1) X
  • LAST EDITED:  MAY 10, 2012
  • HELP-PROMPT:  ASSIGNING AUTHORITY must be 1-70 characters in length.
  • DESCRIPTION:  ASSIGNING AUTHORITY stores a portion of the data used to assemble fully qualified identifiers used for either the HL7 v2.4 or v3.0 standard. It is based on the Health Level Seven (HL7) standardized table 0363 and contains
    the universal ID subcomponent of the assigning authority component in the standard PID-3 identifier.
    The fully qualified HL7 identifier is composed of the PATIENT (#.01), INSTITUTION (#.02), SOURCE ID (#11), ASSIGNING AUTHORITY (#10), and SOURCE ID TYPE (#.09), which constitute a unique entry.
  • AUDIT:  YES, ALWAYS
  • RECORD INDEXES:  AISS (#878), AKEY (#1018), AKEY2 (#1019)
11 SOURCE ID 2;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>150!($L(X)<1) X
  • LAST EDITED:  MAY 10, 2012
  • HELP-PROMPT:  Answer must be 1-150 characters in length.
  • DESCRIPTION:  SOURCE ID is the unique system assigned identifier at the identified facility for the patient record. The value of SOURCE ID varies, depending on the source facility.
    If SOURCE ID is from the Master Patient Index, the value is the Integration Control Number (ICN).  If SOURCE ID is from the Department of Defense (DoD), the value is the Electronic Data Interchange Personal Identifier
    (EDIPI), which is their equivalent of an ICN.  In the future, SOURCE ID may come from other sources due to additional initiatives.
  • AUDIT:  YES, ALWAYS
  • RECORD INDEXES:  AISS (#878), ASID (#737)
12 IDENTIFIER STATUS 2;3 SET
  • 'A' FOR Active;
  • 'H' FOR Merged;

  • LAST EDITED:  OCT 31, 2011
  • HELP-PROMPT:  Enter the status for this SourceID.
  • DESCRIPTION:  The IDENTIFIER STATUS field supports joint VA/DoD medical centers, Veteran's Record Management (VRM), and Virtual Lifetime Electronic Record (VLER) initiatives. This field allows the capture of the resolved duplicate
    events and exposes the related identifier and identifier status to the consuming applications.
    A value of "A" indicates that the patient record is an active record on the identifying system (e.g., VAMC or DoD).  A value of "H" indicates that the patient record was identified as part of a duplicate pair, has been
    merged, and is no longer active on the identifying system (e.g., VAMC or DoD).

ICR, Total: 5

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #2751
  • MASTER PATIENT INDEX VISTA
  • INSTITUTION (.02).
    Access: Write w/Fileman

    PATIENT (.01).
    Access: Write w/Fileman

    Checking for the existance of the^DGCN(391.91,"APAT",,) so that an additionto the file won't occur if it already exists.Adding an entry to the Treating Facilit file viaFILE^DICN call populating .01 and .02 fields.
    ICR #2911
  • Clinical Information Resource Network
  • INSTITUTION (.02).
    Access: Direct Global Read & w/Fileman

    DATE LAST TREATED (.03).
    Access: Direct Global Read & w/Fileman

    ADT/HL7 EVENT REASON (.07).
    Access: Write w/Fileman

    PATIENT (.01).
    Access: Read w/Fileman

    This is a M type cross-reference. It builds thecross-reference from PATIENT (#.01) and INSTITUTION (#.02) field data. Thestructure is as follows:^DGCN(391.91,"APAT", PATIENT (#2) file pointer , INSTITUTION (#4) file pointer, internal entry number)=""This is a M type cross-reference. It builds thecross-reference from PATIENT (#.01) and INSTITUTION (#.02) field data. Thestructure is as follows:^DGCN(391.91,"AINST", INSTITUTION (#4) file pointer , PATIENT (#2) filepointer , internal entry number)=""x-ref build from INSTITUTION (#.02) and PATIENT (#.01)fields.
    ICR #4943
  • SPINAL CORD DYSFUNCTION
  • SCHEDULING
  • (n/a).
    Access: Direct Global Read & w/Fileman

    INSTITUTION (.02).
    Access: Direct Global Read & w/Fileman

    DATE LAST TREATED (.03).
    Access: Direct Global Read & w/Fileman

    B Cross-reference
    ICR #6106
  • VA Point of Service
  • PATIENT (.01).
    Access: Read w/Fileman

    SOURCE ID (11).
    Access: Read w/Fileman

    ICR #6284
  • Enterprise Health Management Platform
  • PATIENT (.01).
    Access: Direct Global Read & w/Fileman

    INSTITUTION (.02).
    Access: Direct Global Read & w/Fileman

    SOURCE ID TYPE (.09).
    Access: Direct Global Read & w/Fileman

    ASSIGNING AUTHORITY (10).
    Access: Direct Global Read & w/Fileman

    SOURCE ID (11).
    Access: Direct Global Read & w/Fileman

    IDENTIFIER STATUS (12).
    Access: Direct Global Read & w/Fileman

    External References

    Name Field # of Occurrence
    ^%DT .03+1
    Y^DIQ ID.02+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^DD(4 ID.02+1
    ^DGCN(391.91 - [#391.91] IXAEVNSL+1*, IXAEVNKL+1!, IXAEVNKEIC+1!, IXAISSSL+1*, IXAISSKL+1!, IXAISSKEIC+1!, IXAKEYSL+1*, IXAKEYKL+1!, IXAKEYKEIC+1!, IXAKEY2SL+1*
    , IXAKEY2KL+1!, IXAKEY2KEIC+1!, IXASIDSL+1*, IXASIDKL+1!, IXASIDKEIC+1!, .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), .01(XREF 3S)
    .01(XREF 3K), .02(XREF 1S), .02(XREF 1K), .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K)
    ^DIC(4 - [#4] ID.02+1

    Naked Globals

    Name Field # of Occurrence
    ^(0 ID.02+1

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> %DT .03+1*
    %I ID.02+1*!
    >> C ID.02+1*
    >> DA IXAEVNSL+1, IXAEVNKL+1, IXAISSSL+1, IXAISSKL+1, IXAKEYSL+1, IXAKEYKL+1, IXAKEY2SL+1, IXAKEY2KL+1, IXASIDSL+1, IXASIDKL+1
    .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), .01(XREF 3S), .01(XREF 3K), .02(XREF 1S), .02(XREF 1K), .02(XREF 2S), .02(XREF 2K)
    .02(XREF 3S), .02(XREF 3K)
    >> DIC ID.02+1
    TMPA .01(XREF 2S), .01(XREF 2K), .01(XREF 3S), .01(XREF 3K), .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K)
    U ID.02+1, .01(XREF 2S), .01(XREF 2K), .01(XREF 3S), .01(XREF 3K), .02(XREF 2S), .02(XREF 2K), .02(XREF 3S), .02(XREF 3K)
    X .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), .01(XREF 3S), .01(XREF 3K), .02(XREF 1S), .02(XREF 1K), .02(XREF 2S), .02(XREF 2K)
    .02(XREF 3S), .02(XREF 3K), .03+1*!, 10+1!, 11+1!
    X(1 IXAEVNSL+1, IXAEVNKL+1, IXAISSSL+1, IXAISSKL+1, IXAKEYSL+1, IXAKEYKL+1, IXAKEY2SL+1, IXAKEY2KL+1, IXASIDSL+1, IXASIDKL+1
    X(2 IXAEVNSL+1, IXAEVNKL+1, IXAISSSL+1, IXAISSKL+1, IXAKEYSL+1, IXAKEYKL+1, IXAKEY2SL+1, IXAKEY2KL+1, IXASIDSL+1, IXASIDKL+1
    X(3 IXAISSSL+1, IXAISSKL+1, IXAKEYSL+1, IXAKEYKL+1
    X(4 IXAISSSL+1, IXAISSKL+1, IXAKEYSL+1, IXAKEYKL+1
    >> Y ID.02+1*, .03+1
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  ICR |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All