STANDARD DATA DICTIONARY #391.91 -- TREATING FACILITY LIST FILE                                                   3/24/25    PAGE 1
STORED IN ^DGCN(391.91,  *** NO DATA STORED YET ***   SITE: WWW.BMIRWIN.COM   UCI: VISTA,VISTA                     (VERSION 5.3)   

DATA          NAME                  GLOBAL        DATA
ELEMENT       TITLE                 LOCATION      TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file holds the Treating Facility List, a list of institutions where the patient has had treatment.  


              DD ACCESS: @
              RD ACCESS: @
              WR ACCESS: @
             DEL ACCESS: @
           LAYGO ACCESS: @
           AUDIT ACCESS: @
IDENTIFIED BY: INSTITUTION (#.02)[R]

CROSS
REFERENCED BY: PATIENT(AINST), INSTITUTION(AINST2), PATIENT(APAT), INSTITUTION(APAT2), PATIENT(B), INSTITUTION(C)

INDEXED BY:    PATIENT & ADT/HL7 EVENT REASON (AEVN), SOURCE ID & ASSIGNING AUTHORITY & SOURCE ID TYPE & INSTITUTION (AISS),
               PATIENT & INSTITUTION & SOURCE ID TYPE & ASSIGNING AUTHORITY (AKEY), PATIENT & ASSIGNING AUTHORITY (AKEY2), SOURCE
               ID & INSTITUTION (ASID)




391.91,.01    PATIENT                0;1 POINTER TO PATIENT FILE (#2) (Required)

              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)

391.91,.02    INSTITUTION            0;2 POINTER TO INSTITUTION FILE (#4) (Required) (audited)

              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)

391.91,.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.  


391.91,.07    ADT/HL7 EVENT REASON   0;7 POINTER TO ADT/HL7 EVENT REASON FILE (#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)

391.91,.08    ROI SIGNED INDICATOR   0;8 SET

              Release of Information Signed Indicator   
                                '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.  


391.91,.09    SOURCE ID TYPE         0;9 SET (audited)

              Source ID Type   
                                '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)

391.91,10     ASSIGNING AUTHORITY    2;1 FREE TEXT (audited)

              Assigning Authority   
              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)

391.91,11     SOURCE ID              2;2 FREE TEXT (audited)

              SourceID   
              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)

391.91,12     IDENTIFIER STATUS      2;3 SET

              Identifier Status   
                                '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).  



      FILES POINTED TO                      FIELDS

ADT/HL7 EVENT REASON (#391.72)    ADT/HL7 EVENT REASON (#.07)

INSTITUTION (#4)                  INSTITUTION (#.02)

PATIENT (#2)                      PATIENT (#.01)


File #391.91

  Record Indexes:

  AEVN (#12)    RECORD    REGULAR    IR    SORTING ONLY
      Short Descr:  This cross-reference links a patient and an event reason.
      Description:  This cross-reference stores the patient pointer value and the event reason pointer value under the same index. 
                    This allows us to track specific event reasons for a given patient.  
        Set Logic:  S ^DGCN(391.91,"AEVN",X(1),X(2),DA)=""
       Kill Logic:  K ^DGCN(391.91,"AEVN",X(1),X(2),DA)
       Whole Kill:  K ^DGCN(391.91,"AEVN")
             X(1):  PATIENT  (391.91,.01)  (Subscr 1)  (forwards)
             X(2):  ADT/HL7 EVENT REASON  (391.91,.07)  (Subscr 2)  (forwards)

  AISS (#878)    RECORD    REGULAR    IR    SORTING ONLY
      Short Descr:  X-REF for fully qualified ID fields
      Description:  The AISS cross-reference will be used to determine the INSTITUTION associated with the fully qualified ID,
                    which is comprised of the SOURCE ID, ASSIGNING AUTHORITY, and SOURCE ID TYPE.  
        Set Logic:  S ^DGCN(391.91,"AISS",$E(X(1),1,150),$E(X(2),1,70),$E(X(3),1,10),$E(X(4),1,10),DA)=""
       Kill Logic:  K ^DGCN(391.91,"AISS",$E(X(1),1,150),$E(X(2),1,70),$E(X(3),1,10),$E(X(4),1,10),DA)
       Whole Kill:  K ^DGCN(391.91,"AISS")
             X(1):  SOURCE ID  (391.91,11)  (Subscr 1)  (Len 150)  (forwards)
             X(2):  ASSIGNING AUTHORITY  (391.91,10)  (Subscr 2)  (Len 70)  (forwards)
             X(3):  SOURCE ID TYPE  (391.91,.09)  (Subscr 3)  (Len 10)  (forwards)
             X(4):  INSTITUTION  (391.91,.02)  (Subscr 4)  (Len 10)  (forwards)

  AKEY (#1018)    RECORD    REGULAR    IR    SORTING ONLY
      Short Descr:  Find entry using all identifier fields.
      Description:  This cross-reference will facilitate finding a specific unique identifier by PATIENT, INSTITUTION, SOURCE ID
                    TYPE, and ASSIGNING AUTHORITY.  
        Set Logic:  S ^DGCN(391.91,"AKEY",$E(X(1),1,150),X(2),X(3),$E(X(4),1,70),DA)=""
       Kill Logic:  K ^DGCN(391.91,"AKEY",$E(X(1),1,150),X(2),X(3),$E(X(4),1,70),DA)
       Whole Kill:  K ^DGCN(391.91,"AKEY")
             X(1):  PATIENT  (391.91,.01)  (Subscr 1)  (Len 150)  (forwards)
             X(2):  INSTITUTION  (391.91,.02)  (Subscr 2)  (forwards)
             X(3):  SOURCE ID TYPE  (391.91,.09)  (Subscr 3)  (forwards)
             X(4):  ASSIGNING AUTHORITY  (391.91,10)  (Subscr 4)  (Len 70)  (forwards)

  AKEY2 (#1019)    RECORD    REGULAR    IR    SORTING ONLY
      Short Descr:  Lookup by PATIENT and ASSIGNING AUTHORITY.
      Description:  This cross-reference will facilitate finding a specific unique identifier by PATIENT and ASSIGNING AUTHORITY
                    when only those data fields are present, for example for a National Health Information Exchange (NHIE) 
                    location.  
        Set Logic:  S ^DGCN(391.91,"AKEY2",$E(X(1),1,150),$E(X(2),1,70),DA)=""
       Kill Logic:  K ^DGCN(391.91,"AKEY2",$E(X(1),1,150),$E(X(2),1,70),DA)
       Whole Kill:  K ^DGCN(391.91,"AKEY2")
             X(1):  PATIENT  (391.91,.01)  (Subscr 1)  (Len 150)  (forwards)
             X(2):  ASSIGNING AUTHORITY  (391.91,10)  (Subscr 2)  (Len 70)  (forwards)

  ASID (#737)    RECORD    REGULAR    IR    SORTING ONLY
      Short Descr:  X-REF on SOURCE ID and INSTITUTION
      Description:  The ASID cross-reference will be used to determine the INSTITUTION associated with the SOURCE ID.  
        Set Logic:  S ^DGCN(391.91,"ASID",$E(X(1),1,150),X(2),DA)=""
       Kill Logic:  K ^DGCN(391.91,"ASID",$E(X(1),1,150),X(2),DA)
       Whole Kill:  K ^DGCN(391.91,"ASID")
             X(1):  SOURCE ID  (391.91,11)  (Subscr 1)  (Len 150)  (forwards)
             X(2):  INSTITUTION  (391.91,.02)  (Subscr 2)  (forwards)


INPUT TEMPLATE(S):

PRINT TEMPLATE(S):

SORT TEMPLATE(S):

FORM(S)/BLOCK(S):