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 |  All
Print Page as PDF
Global: ^MAG(2005

Package: Imaging

Global: ^MAG(2005


Information

FileMan FileNo FileMan Filename Package
2005 IMAGE Imaging

Description

Directly Accessed By Routines, Total: 186

Package Total Routines
Imaging 148 MAG REPORT 1    MAG REPORT 2    MAG REPORT 3    MAG REPORT 4    MAGBAPI    MAGBAPIP    MAGBRTE3    MAGBRTE4
MAGBRTE5    MAGBRTLD    MAGBRTUT    MAGCRPT    MAGDHOW0    MAGDIR81    MAGDIR84    MAGDIR9A
MAGDIR9B    MAGDIR9E    MAGDIR9F    MAGDIRVE    MAGDMEDL    MAGDOD01    MAGDQR02    MAGDQR03
MAGDQR04    MAGDQR05    MAGDQR06    MAGDQR08    MAGDQR09    MAGDQR10    MAGDQR11    MAGDQR13
MAGDQR20    MAGDQR21    MAGDQR23    MAGDQR32    MAGDRCU2    MAGDRPC2    MAGDRPC3    MAGDRPC4
MAGDRPC7    MAGDRPC9    MAGDRPCA    MAGDRTIM    MAGDTR02    MAGFILEB    MAGGA02    MAGGA03U
MAGGAII    MAGGI11    MAGGI12    MAGGI14    MAGGNTI    MAGGSFT    MAGGSIA    MAGGSIA1
MAGGSIM    MAGGSIU2    MAGGSIU4    MAGGSIU5    MAGGSIV    MAGGSPP    MAGGSQI    MAGGSTI
MAGGTAU    MAGGTIA    MAGGTIA1    MAGGTID    MAGGTIG    MAGGTII    MAGGTLB1    MAGGTMC1
MAGGTPT1    MAGGTRA    MAGGTRAI    MAGGTRP1    MAGGTRPT    MAGGTSR    MAGGTSR1    MAGGTSY2
MAGGTSYS    MAGGTU3    MAGGTU31    MAGGTU6    MAGGTU7    MAGGTU71    MAGGTUX    MAGGTUX1
MAGGTUX2    MAGGTUX4    MAGIPT20    MAGJEX3    MAGJRPT    MAGJUPD2    MAGJUTL2    MAGJUTL4
MAGJVAPI    MAGLOG    MAGMC2CP    MAGNAN03    MAGNGMR    MAGNTRAI    MAGNUID2    MAGNVIC
MAGNVQ06    MAGQBAB    MAGQBGCC    MAGQBJB    MAGQBJH    MAGQBJHR    MAGQBPG1    MAGQBPG2
MAGQBPRG    MAGQBTM    MAGQBU6A    MAGQBUT1    MAGQBUT2    MAGQBUT5    MAGQE1    MAGQE2
MAGQE3    MAGQE7    MAGSANNO    MAGSDEL2    MAGSDEL3    MAGSDEL5    MAGSDHCP    MAGSDLGR
MAGSFTCH    MAGSHEC    MAGSIMBR    MAGT7MA    MAGUE001    MAGUF    MAGUXRF    MAGVCQRY
MAGVD003    MAGVD006    MAGVD010    MAGVGUID    MAGVIM06    MAGVRS61    MAGXCVC    MAGXCVI
MAGXCVI1    MAGXCVP    MAGXCVR    MAGXCVX    
MailMan 5 XMA2B    XMRFTP    XMRFTPUX    XMS0BLOB    XMSFTPUX    
Health Summary 3 GMTSMAG    GMTSMAGE    GMTSP26    
Medicine 1 MCPOS04A    
Radiology Nuclear Medicine 1 RARIC1    
Text Integration Utility 1 TIUSRVPL    

Accessed By FileMan Db Calls, Total: 24

Package Total Routines
Imaging 23 MAGDRPC2    MAGGI11    MAGGNTI    MAGGSIU1    MAGGSIU2    MAGGSIU5    MAGGTIA    MAGGTIA1
MAGGTID    MAGIP106    MAGIPS93    MAGNAN03    MAGNTRAI    MAGNU003    MAGNWRK1    MAGSDLGR
MAGSFTCH    MAGSIXG3    MAGSIXGT    MAGXCVC    MAGXCVE    MAGXCVR    MAGXCVX    
MailMan 1 XMR0BLOB    

Pointed To By FileMan Files, Total: 25

Package Total FileMan Files
Imaging 12 IMAGE(#2005)[14#2005.04(.01)]    IMAGING STUDY(#2005.001)[#2005.031(.01)]    IMAGING ANNOTATION(#2005.002)[.01]    DICOM LAB TEMP LIST(#2006.5838)[4]    DICOM GMRC TEMP LIST(#2006.5839)[3]    IMAGING WINDOWS SESSIONS(#2006.82)[6]    IMAGE ACCESS LOG(#2006.95)[3]    MULTI IMAGE PRINT(#2006.961)[#2006.9613(1)]    DICOM GATEWAY PARAMETER(#2006.563)[4773200]
DICOM OBJECT EXPORT(#2006.574)[2#2006.5744(.01)]    SEND QUEUE(#2006.035)[.01]    ROUTE LOAD BALANCE(#2006.5906)[#2006.59061(.01)]    
Medicine 7 ECHO(#691)[#691.02005(.01)]    CARDIAC CATHETERIZATION(#691.1)[#691.12005(.01)]    ELECTROCARDIOGRAM (EKG)(#691.5)[#691.52005(.01)]    HEMATOLOGY(#694)[#694.02005(.01)]    ENDOSCOPY/CONSULT(#699)[#699.02005(.01)]    GENERALIZED PROCEDURE/CONSULT(#699.5)[#699.52005(.01)]    RHEUMATOLOGY(#701)[#701.02005(.01)]    
MailMan 2 MESSAGE(#3.9)[#3.92005(.01)]    MAILMAN OUTSTANDING FTP TRANSACTIONS(#4.2995)[3]    
Lab Service 1 LAB DATA(#63)[#63.22005(.01)#63.28(.01)#63.45(.01)#63.82005(.01)#63.92005(.01)]    
Radiology Nuclear Medicine 1 RAD/NUC MED REPORTS(#74)[#74.02005(.01)]    
Surgery 1 SURGERY(#130)[#130.02005(.01)]    
Text Integration Utility 1 TIU EXTERNAL DATA LINK(#8925.91)[.02]    

Pointer To FileMan Files, Total: 20

Package Total FileMan Files
Imaging 14 IMAGE(#2005)[14#2005.04(.01)]    OBJECT TYPE(#2005.02)[3]    PARENT DATA FILE(#2005.03)[16]    IMAGE AUDIT(#2005.1)[115.1]    NETWORK LOCATION(#2005.2)[22.12.2102103#2005.01(.01)#2005.0106(2)#2005.0111(2)]    MAG DESCRIPTIVE CATEGORIES(#2005.81)[100]    IMAGE INDEX FOR CLASS(#2005.82)[41]    IMAGE INDEX FOR TYPES(#2005.83)[42]    IMAGE INDEX FOR SPECIALTY/SUBSPECIALTY(#2005.84)[44]    IMAGE INDEX FOR PROCEDURE/EVENT(#2005.85)[43]    MAG REASON(#2005.88)[113.3]    ACQUISITION DEVICE(#2006.04)[107]    DICOM SOP CLASS(#2006.532)[251]    DICOM TRANSMIT DESTINATION(#2006.587)[#2005.0111(3)]    
Kernel 2 INSTITUTION(#4)[.05]    NEW PERSON(#200)[830#2005.05(3)#2005.099(.03)112.2113.2]    
Radiology Nuclear Medicine 2 RAD/NUC MED PROCEDURES(#71)[62]    RAD/NUC MED REPORTS(#74)[61]    
Registration 1 PATIENT(#2)[5]    
Scheduling 1 HOSPITAL LOCATION(#44)[101]    

Fields, Total: 73

Field # Name Loc Type Details
.001 NUMBER NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  JUN 16, 1994
  • HELP-PROMPT:  Type a Number between 1 and 999999, 0 Decimal Digits
  • DESCRIPTION:  .001 NUMBER Field is the Internal Entry Number of the Image File Entry. i.e. "DA" of the Image File entry. Imaging routines and RPC's use the Image DA for lookups. The Image Files associated with this entry are stored
    on a Networked Image A name for the Image Files is generated from the Image DA, the Extension is appropriate to the Type of Image.  i.e. I0014432.JPG
.01 OBJECT NAME 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>70!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  APR 07, 2009
  • HELP-PROMPT:  Answer must be 3-70 characters in length.
  • DESCRIPTION:  
    Each object has a natural language name; this usually consists of the patient name, social security number, and object description.  This field is automatically defined by the Imaging software.
  • CROSS-REFERENCE:  2005^B
    1)= S ^MAG(2005,"B",$E(X,1,60),DA)=""
    2)= K ^MAG(2005,"B",$E(X,1,60),DA)
  • RECORD INDEXES:  AUDIT100 (#513), AUDIT2 (#514), AUDIT40 (#515)
.05 ACQUISITION SITE 100;3 POINTER TO INSTITUTION FILE (#4)
************************REQUIRED FIELD************************
INSTITUTION(#4)

  • LAST EDITED:  JUN 15, 2011
  • HELP-PROMPT:  Enter the name of the site where the image was created.
  • DESCRIPTION:  The 'origin' location is the location where an image is created. For instance, a site like 'St. Louis' may process images for several other locations, such as Topeka, Wichita and Leavenworth. Any reference to a site
    identifier will return the name of the primary location. For the purpose of finding the 'origin' of images, the more specific sub-site is needed.  This field contains the name of this 'sub-site'.
  • FIELD INDEX:  D (#168) REGULAR IR LOOKUP & SORTING
    Short Descr:  INSTUTION(AKA ACQUISITION SITE)
    Set Logic:  S ^MAG(2005,"D",X,DA)=""
    Kill Logic:  K ^MAG(2005,"D",X,DA)
    Whole Kill:  K ^MAG(2005,"D")
    X(1):  ACQUISITION SITE  (2005,.05)  (Subscr 1)  (forwards)
  • RECORD INDEXES:  ADTDUZ (#661)
.06 EXPORT LOCATION 5;0 POINTER Multiple #2005.01 2005.01

  • DESCRIPTION:  
    This table contains audit information regarding the export locations of file copies generated by the generic carbon copy (GCC) utility.  This utility is used by the Health Eligibility Center functionality.
1 FILEREF 0;2 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>30!($L(X)<1) X
  • LAST EDITED:  APR 12, 2005
  • HELP-PROMPT:  Answer must be 1-30 characters in length.
  • DESCRIPTION:  This field contains the unique image filename of the image stored on the Vista Imaging file servers. It is either 12 or 18 characters long. It contains three elements: the facility's Imaging Namespace, from the Current
    Namespace field (#.02) of the IMAGING SITE PARAMETERS file (#2006.1), the Image IEN, and padded with zeros if needed, and the extension that indicates the format of the image. Supported formats are stored in the IMAGE FILE
    TYPES (#2005.021) file.  This field is automatically set by the Imaging software.
  • FIELD INDEX:  f (#658) MUMPS IR LOOKUP & SORTING
    Short Descr:  FILEREF minus the extention
    Set Logic:  S ^MAG(2005,"F",$P($E(X,1,60),"."),DA)=""
    Kill Logic:  K ^MAG(2005,"F",$P($E(X,1,60),"."),DA)
    X(1):  FILEREF  (2005,1)  (Subscr 1)  (forwards)
2 DISK & VOLUME, MAGNETIC 0;3 POINTER TO NETWORK LOCATION FILE (#2005.2) NETWORK LOCATION(#2005.2)

  • LAST EDITED:  NOV 12, 1998
  • HELP-PROMPT:  Enter the disk name and volume set name where the image will be stored
  • DESCRIPTION:  This field gives the path for the network location of the stored image (i.e. on which server it resides). After a specified time period during which the image is not viewed, the image is deleted from the magnetic server
    but remains available upon request from the jukebox. It takes slightly longer to display from the jukebox, but if requested, it is moved back to the server until it is no longer being viewed. This field is set
    automatically by the Imaging software.
2.1 DISK & VOLUME, ABSTRACT 0;4 POINTER TO NETWORK LOCATION FILE (#2005.2) NETWORK LOCATION(#2005.2)

  • LAST EDITED:  NOV 12, 1998
  • DESCRIPTION:  This field points to the path of the network storage location for the image abstract. An abstract is a miniature copy of the captured image. If the parent image has not been viewed during the specified time period (if
    there is a jukebox), this file will be deleted along with the parent image file. Should the abstract be requested for viewing, it will be copied back onto the server currently being used to write captured images.  This
    field is automatically set by the Imaging software.
2.2 DISK & VOLUME, WORM 0;5 POINTER TO NETWORK LOCATION FILE (#2005.2) NETWORK LOCATION(#2005.2)

  • LAST EDITED:  NOV 12, 1998
  • DESCRIPTION:  
    This field is a pointer to the Network Location file giving the jukebox platter where the image is stored (provided there is a jukebox in the Imaging System). If it is a WORM, this file can never be deleted.
3 OBJECT TYPE 0;6 POINTER TO OBJECT TYPE FILE (#2005.02) OBJECT TYPE(#2005.02)

  • LAST EDITED:  APR 02, 1994
  • DESCRIPTION:  This field is a pointer to the Object Type file (2005.02) which defines the object type of this object, e.g., still image, black & white image, x-ray etc. The image type determines how various actions are performed i.e.,
    how the full resolution image is displayed, or how and when the image abstract is displayed.  This field is automatically set by the Imaging software at the time of image capture.
4 OBJECT GROUP 1;0 POINTER Multiple #2005.04 2005.04

  • DESCRIPTION:  The object group is a multiple field pointing back to the Image file (2005). Only objects with an object type of GROUP have the Object Group field defined. These objects can be thought of as the "parent" of a set of
    images.
    Generally, instead of having their own abstract, objects of the GROUP type use the abstract of the first entry in their object group multiple.  Sometimes, text will be used in place of the GROUP abstract for speed.
    Methods for viewing a GROUP object generally allow viewing of all the members of the group, either selectively or altogether.  A good example would be a set of thirty CT scan images.  Using the Integrated View menu option,
    the tiled display of image abstracts would contain only one abstract for the group.  Selecting the group object for viewing provides the user with a tiled display of the abstracts of the individual CT scan images.  The
    user can then identify individual images for full resolution viewing.
  • TECHNICAL DESCR:  In the future, when the IMAGE AUDIT file (#2005.1) is eliminated and deleted image entries are merged into the IMAGE file (#2005), this multiple must reference only non-deleted images (as it currently does). The "AGPD"
    index will be used to find images deleted from the group.
5 PATIENT 0;7 POINTER TO PATIENT FILE (#2) PATIENT(#2)

  • LAST EDITED:  JUN 30, 1997
  • DESCRIPTION:  This field is a pointer to the VistA Patient file (#2), and contains the DFN of the patient that the image or object belongs to. The image or object is part of this patient's medical record. This pointer ties the image to
    the patient and is automatically set by the Imaging software.
  • TECHNICAL DESCR:  
  • CROSS-REFERENCE:  2005^AC
    1)= S ^MAG(2005,"AC",$E(X,1,30),DA)=""
    2)= K ^MAG(2005,"AC",$E(X,1,30),DA)
    This cross-reference will produce a simple "AC" on the Patient's DFN.
  • CROSS-REFERENCE:  2005^APPXDT^MUMPS
    1)= I $P(^MAG(2005,DA,0),U,10)="" D SETPPXD^MAGUXRF
    2)= I $P(^MAG(2005,DA,0),U,10)="" D KILPPXD^MAGUXRF
    3)= PATIENT,DATETIME,PROCEDURE & PATIENT,PROC,DATETIME
    This Mumps routine will create two cross-references to relate the following variables: DFN (patient), Procedure, Date/time of Procedure
    or secondly: DFN (patient), Date/time of Procedure, Procedure NOTE: any record that is a child of a parent, i.e. member of a group is NOT included in the cross-references; only independent members or parents.
    This cross-reference set is the same for the fields #6 (Procedure) and #15 (Procdedure date and time). For all three of these fields: #5,#6,#15 the set and kill of the cross-reference produce the same result. The only
    difference is the 'X' used which is dependant upon which field.  Each set produces two cross-references, that differ only by the order of the variables as described above. Other descriptions will be referred to this one to
    explain the purpose of the cross-reference.
    The cross-references produced have the following structure:
    ^MAG(2005,"APPXDT",DFN,PROC,DT,DA)=""
    ^MAG(2005,"APDTPX",DFN,DT,PROC,DA)=""
6 PROCEDURE 0;8 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>10!($L(X)<1) X
  • LAST EDITED:  DEC 28, 1993
  • HELP-PROMPT:  Answer must be 1-10 characters in length.
  • DESCRIPTION:  
    This field is an abbreviation for the procedure (e.g., COL for colonoscopy, SUR for surgery, SP for surgical pathology, X-ray for radiology).  This field is automatically set by the Imaging software.
  • CROSS-REFERENCE:  2005^APPXDT6^MUMPS
    1)= I $P(^MAG(2005,DA,0),U,10)="" D SETPPXD6^MAGUXRF
    2)= I $P(^MAG(2005,DA,0),U,10)="" D KILPPXD6^MAGUXRF
    3)= PATIENT,DATETIME,PROCEDURE & PATIENT,PROC,DATETIME
    This MUMPS routine will create two cross references to relate the follwing variables. DFN (patient), Procedure, Date/Time of Procedure or secondly: DFN (patient), Date/Time of Procedure.  Procedure Note: any record that is
    a child of a parent, i.e. member of a group is NOT included in the cross-references; only independent members or parents.  This cross reference set is the same for the fields #15 (Procedure Date\Time) and #5 (Patient).
    For all three of these fields, #5, #6 and #15, the set and kill of the cross reference produces the same results.  The only difference is the 'X' used which is dependant upon which field is being used.
    The cross references produced have the following structure:
    ^MAG(2005,"APPXDT",DFN,PROC,RDT,DA)=""
    ^MAG(2005,"APDTPX",DFN,,RDT,PROC,DA)=""
  • RECORD INDEXES:  AUDIT2 (#514)
7 DATE/TIME IMAGE SAVED 2;1 DATE

  • INPUT TRANSFORM:  S %DT="ETX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 15, 2011
  • HELP-PROMPT:  This is the date and time of image capture.
  • DESCRIPTION:  This field is the date and time the image was captured. It is automatically stuffed into the file as "NOW". It is not the same as the date and time of the procedure or exam. This field is set automatically by the Imaging
    software.
  • FIELD INDEX:  AD (#527) REGULAR IR SORTING ONLY
    Short Descr:  Created by Patch 77
    Set Logic:  S ^MAG(2005,"AD",X,DA)=""
    Kill Logic:  K ^MAG(2005,"AD",X,DA)
    Whole Kill:  K ^MAG(2005,"AD")
    X(1):  DATE/TIME IMAGE SAVED  (2005,7)  (Subscr 1)  (forwards)
    Transform (Storage):  S X=$P(X,".")
  • RECORD INDEXES:  ADTDUZ (#661)
8 IMAGE SAVE BY 2;2 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  JUN 15, 2011
  • DESCRIPTION:  This field is a pointer to the New Person file and thus equal to the DUZ of the person who logged in to capture the image. It identifies who captured or saved the image and is automatically stuffed into the Image file.
    An image received via a Multimedia Mail message will not have data in this field.
  • RECORD INDEXES:  ADTDUZ (#661)
8.1 CAPTURE APPLICATION 2;12 SET
  • 'C' FOR Capture Workstation;
  • 'D' FOR DICOM Gateway;
  • 'I' FOR Import API;

  • LAST EDITED:  JUN 15, 2011
  • HELP-PROMPT:  Select code of the application that captured the image.
  • DESCRIPTION:  Code stored in this field indicates the application that captured this image and created the image entry.
    This field cannot be edited; it is auto-populated by the "ACA" action index.
  • TECHNICAL DESCR:  
    Added by the patch MAG*3*93.
    DELETE AUTHORITY: @
    WRITE AUTHORITY:  ^
  • GROUP:  MAG*3*93
  • RECORD INDEXES:  ADTDUZ (#661)
9 SUMMARY OBJECT 2;3 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  MAY 04, 1994
  • HELP-PROMPT:  Enter 1 for 'Yes' and 0 (or null) for 'No'.
  • DESCRIPTION:  This field is used to indicate whether the image or object is to be used as a summary for a group of objects. For example, in a GROUP of images, normally the abstract of the first object in the group multiple is used for
    the integrated view display.  This field allows the user to select a summary image to be used for this purpose.  This field is currently not in use.
10 SHORT DESCRIPTION 2;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<1) X
  • LAST EDITED:  SEP 14, 1990
  • HELP-PROMPT:  Answer must be 1-60 characters in length.
  • DESCRIPTION:  This field allows the user to store a brief, one line description with the image or object record. For images associated with patients, this data is appended to the patient's name and SSN to create the .01 field of the
    Image file.  It is also permanently written on the upper left corner of the image to provide visible identification.
  • RECORD INDEXES:  AUDIT2 (#514)
11 LONG DESCRIPTION 3;0 WORD-PROCESSING #2005.011

  • DESCRIPTION:  This word processing field allows the user to describe the image at length. The user may only choose to append this long description on selected images - those which are "classic" or "unusual" cases. It can be used to
    summarize a group of images which have been put together for a conference or consult.  It will be used in the future to a greater extent, as options for image capture (independent of VistA packages) are provided.
12 LAST ACCESS DATE 0;9 DATE

  • INPUT TRANSFORM:  S %DT="ET" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  AUG 18, 1992
  • HELP-PROMPT:  Date image last accessed
  • DESCRIPTION:  This is the date and time the image was last viewed or accessed. Each time an abstract or image is requested for viewing, this field is automatically set with the current date and time. In conjunction with the appropriate
    site parameter, this field is used for automatic file migration.  That is, when an image has not been accessed within the predefined time period, it will be deleted from the magnetic server and will only be accessible from
    the optical disk jukebox.
13 IQ 0;11 SET
  • '1' FOR YES;

  • LAST EDITED:  AUG 24, 2001
  • DESCRIPTION:  
    This indicates that this image entry has questionable integrity.
  • TECHNICAL DESCR:  
    This field is set by various integrity checkers in the Imaging software.  This field is set if an entry has questionable integrity.
  • CROSS-REFERENCE:  2005^AIQ
    1)= S ^MAG(2005,"AIQ",$E(X,1,30),DA)=""
    2)= K ^MAG(2005,"AIQ",$E(X,1,30),DA)
    This cross reference exists to quickly list all images that have questionable integrity.
13.5 DUPE 0;12 SET
  • '1' FOR YES;

  • LAST EDITED:  JUN 20, 2005
  • DESCRIPTION:  This field is to allow screening of images that have duplicate instances in the archive file and the image file. The intent is to prevent purging of these images on the raid until a utility to store this file on the
    Jukebox is implemented.
14 GROUP PARENT 0;10 POINTER TO IMAGE FILE (#2005) IMAGE(#2005)

  • LAST EDITED:  DEC 15, 2008
  • HELP-PROMPT:  If this object is a member of a group, enter the parent.
  • DESCRIPTION:  This field is used for images that are part of a group, for example a CT exam might contain 30 images. This field contains a pointer back to the Image file (2005), to the object whose type is "GROUP" that points to this
    object as a member of its group.  A pointer to this object will be found in the Object Group multiple of the parent GROUP object.
  • RECORD INDEXES:  ADTDUZ (#661), AGPD (#511), APDT (#512)
15 PROCEDURE/EXAM DATE/TIME 2;5 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  MAY 27, 1994
  • HELP-PROMPT:  Enter the DATE-TIME of the Procedure or Exam
  • DESCRIPTION:  This is the date/time of the procedure or the exam. It is obtained from the Parent Data file (i.e. the date/time of the X-ray exam, the Medical Procedure, the time the Laboratory specimen was obtained from the patient, or
    the date/time of the Surgical procedure). This often is not the same as the date/time the image was captured. In a long surgical procedure the image capture time may be several hours later than the start of the operation.
    When a lab specimen is collected from a patient, it may be several days before images are captured from the slide.  If images are initially stored on an intermediate media such as x-ray film or video tape, the capture time
    can be long after the procedure time.
  • CROSS-REFERENCE:  2005^APPXDT5^MUMPS
    1)= I $P(^MAG(2005,DA,0),U,10)="" D SETPPXD5^MAGUXRF
    2)= I $P(^MAG(2005,DA,0),U,10)="" D KILPPXD5^MAGUXRF
    3)= PATIENT,DATETIME,PROCEDURE & PATIENT,PROC,DATETIME
    This MUMPS routine will create two cross references to relate the following variables. DFN (patient), Procedure, Date/Time of Procedure or secondly: DFN (patient), Date/Time of Procedure.  Procedure Note: any record that
    is a child of a parent, i.e. member of a group is NOT included in the cross-references; only independent members or parents.  This cross reference set is the same for the fields #6 (Procedure) and #5 (Patient).  For all
    three of these fields, #5, #6 and #15, the set and kill of the cross reference produces the same results.  The only difference is the 'X' used which is dependant upon which field is being used.
    The cross references produced have the following structure:
    ^MAG(2005,"APPXDT",DFN,PROC,RDT,DA)=""
    ^MAG(2005,"APDTPX",DFN,RDT,PROC,DA)=""
  • RECORD INDEXES:  APDT (#512), AUDIT2 (#514)
16 PARENT DATA FILE# 2;6 POINTER TO PARENT DATA FILE FILE (#2005.03) PARENT DATA FILE(#2005.03)

  • LAST EDITED:  OCT 09, 1995
  • HELP-PROMPT:  The Parent Report file (or sub-file) number.
  • DESCRIPTION:  The values of fields 16, 17, 18 and 63 are numbers. These numbers are internal entry numbers. Which field corresponds to which internal entry number is explained below.
    Together, the values of these fields establish a link back to the entry in the "parent" file, that holds the information that describes why the image was collected.
    The link to the "parent" information is brought about by the combination of the values of fields 16, 17, and, 18, and optionally also field 63.
    The value of field 16 is a number that indicates the internal entry number of the "parent file" in the VA-FileMan data dictionary.  Common parent files are:
    File    Name
    ====    ====
    3.9:  MAIL MESSAGE
    63:    AUTOPSY (MICROSCOPIC)
    63.02: ELECTRON MICROSCOPY
    63.08: SURGICAL PATHOLOGY
    63.09: CYTOLOGY
    63.2:  AUTOPSY (GROSS)
    74:    RADIOLOGY
    130:    SURGERY
    691:    ECHOCARDIOGRAM
    691.1:  CARDIAC CATHETERIZATION
    691.5:  ELECTROCARDIOGRAPHY
    694:    HEMATOLOGY
    699:    ENDOSCOPY
    699.5:  GENERIC MEDICINE
    8925:    TIU
    The records in each of these "parent" files contain a multiple that itemizes the list of images that belong to that record.
    The field numbers and fixed indexes for those multiples all have the number 2005. The entries within these multiples all have a field that is a pointer back to the image file.  The entries in these multiples identify the
    various images that belong with the record in question.
    The various parent files each have their own structure, for instance
    Type Number     Form of Root
    ===========     ============
    1           ^RARPT(D0,2005,D1,0)=image...
    2           ^MCAR(699,D0,2005,D1,0)=image...
    3           ^LR(D0,"SP",D1,2005,D2,0)=image...
    Depending on the nature of the file structure of the parent file, the imaging software will need either just the value of D0 (type 1 and type 2) to find the correct entry, or the values of D0 as well as D1 (type 3).
    The values of the fields in the image file correspond to the values of the indices in the parent file as follows:
    Type Number   Field Number and FileMan Index
    ===========   ==============================
    1         field 17 = D0, field 18 = D1
    2         field 17 = D0, field 18 = D1
    3         field 17 = D0, field 63 = D1, field 18 = D2
    In the case of type 3, the value of D0 is equal to the value of LRDFN.
17 PARENT GLOBAL ROOT D0 2;7 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>9999999999.9999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  DEC 18, 2001
  • HELP-PROMPT:  Type a Number between 1 and 9999999999.9999, 0 Decimal Digits
  • DESCRIPTION:  The values of fields 16, 17, 18 and 63 are numbers. These numbers are internal entry numbers. Which field corresponds to which internal entry number is explained below.
    Together, the values of these fields establish a link back to the entry in the "parent" file, that holds the information that describes why the image was collected.
    The link to the "parent" information is brought about by the combination of the values of fields 16, 17, and, 18, and optionally also field 63.
    The value of field 16 is a number that indicates the internal entry number of the "parent file" in the VA-FileMan data dictionary.  Common parent files are:
    File    Name
    ====    ====
    3.9:  MAIL MESSAGE
    63:    AUTOPSY (MICROSCOPIC)
    63.02: ELECTRON MICROSCOPY
    63.08: SURGICAL PATHOLOGY
    63.09: CYTOLOGY
    63.2:  AUTOPSY (GROSS)
    74:    RADIOLOGY
    130:    SURGERY
    691:    ECHOCARDIOGRAM
    691.1:  CARDIAC CATHETERIZATION
    691.5:  ELECTROCARDIOGRAPHY
    694:    HEMATOLOGY
    699:    ENDOSCOPY
    699.5:  GENERIC MEDICINE
    8925:    TIU
    The records in each of these "parent" files contain a multiple that itemizes the list of images that belong to that record.
    The field numbers and fixed indexes for those multiples all have the number 2005. The entries within these multiples all have a field that is a pointer back to the image file.  The entries in these multiples identify the
    various images that belong with the record in question.
    The various parent files each have their own structure, for instance
    Type Number     Form of Root
    ===========     ============
    1           ^RARPT(D0,2005,D1,0)=image...
    2           ^MCAR(699,D0,2005,D1,0)=image...
    3           ^LR(D0,"SP",D1,2005,D2,0)=image...
    Depending on the nature of the file structure of the parent file, the imaging software will need either just the value of D0 (type 1 and type 2) to find the correct entry, or the values of D0 as well as D1 (type 3).
    The values of the fields in the image file correspond to the values of the indices in the parent file as follows:
    Type Number   Field Number and FileMan Index
    ===========   ==============================
    1         field 17 = D0, field 18 = D1
    2         field 17 = D0, field 18 = D1
    3         field 17 = D0, field 63 = D1, field 18 = D2
    In the case of type 3, the value of D0 is equal to the value of LRDFN.
18 PARENT DATA FILE IMAGE POINTER 2;8 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>9999999.9999)!(X<1)!(X?.E1"."5N.N) X
  • LAST EDITED:  MAY 04, 1994
  • HELP-PROMPT:  Type a Number between 1 and 9999999.9999, 4 Decimal Digits
  • DESCRIPTION:  The values of fields 16, 17, 18 and 63 are numbers. These numbers are internal entry numbers. Which field corresponds to which internal entry number is explained below.
    Together, the values of these fields establish a link back to the entry in the "parent" file, that holds the information that describes why the image was collected.
    The link to the "parent" information is brought about by the combination of the values of fields 16, 17, and, 18, and optionally also field 63.
    The value of field 16 is a number that indicates the internal entry number of the "parent file" in the VA-FileMan data dictionary.  Common parent files are:
    File    Name
    ====    ====
    3.9:  MAIL MESSAGE
    63:    AUTOPSY (MICROSCOPIC)
    63.02: ELECTRON MICROSCOPY
    63.08: SURGICAL PATHOLOGY
    63.09: CYTOLOGY
    63.2:  AUTOPSY (GROSS)
    74:    RADIOLOGY
    130:    SURGERY
    691:    ECHOCARDIOGRAM
    691.1:  CARDIAC CATHETERIZATION
    691.5:  ELECTROCARDIOGRAPHY
    694:    HEMATOLOGY
    699:    ENDOSCOPY
    699.5:  GENERIC MEDICINE
    8925:    TIU
    The records in each of these "parent" files contain a multiple that itemizes the list of images that belong to that record.
    The field numbers and fixed indexes for those multiples all have the number 2005. The entries within these multiples all have a field that is a pointer back to the image file.  The entries in these multiples identify the
    various images that belong with the record in question.
    The various parent files each have their own structure, for instance
    Type Number     Form of Root
    ===========     ============
    1           ^RARPT(D0,2005,D1,0)=image...
    2           ^MCAR(699,D0,2005,D1,0)=image...
    3           ^LR(D0,"SP",D1,2005,D2,0)=image...
    Depending on the nature of the file structure of the parent file, the imaging software will need either just the value of D0 (type 1 and type 2) to find the correct entry, or the values of D0 as well as D1 (type 3).
    The values of the fields in the image file correspond to the values of the indices in the parent file as follows:
    Type Number   Field Number and FileMan Index
    ===========   ==============================
    1         field 17 = D0, field 18 = D1
    2         field 17 = D0, field 18 = D1
    3         field 17 = D0, field 63 = D1, field 18 = D2
    In the case of type 3, the value of D0 is equal to the value of LRDFN.
19 EXPORT REQUEST STATUS 2;9 SET
  • '1' FOR EXPORT REQUESTED;
  • '0' FOR EXPORTED;

  • LAST EDITED:  JAN 02, 1994
  • HELP-PROMPT:  USED BY MULTIMEDIA MAIL - REQUEST TO COPY IMAGE
  • DESCRIPTION:  This field is used by Multimedia MailMan when an image needs to be sent to another site. The Imaging software sets the field automatically, after checking its status. After the request is carried out, it will be
    automatically reset.
  • CROSS-REFERENCE:  2005^AEXPORT^MUMPS
    1)= I X S ^MAG(2005,"AEXPORT",DA)=""
    2)= K ^MAG(2005,"AEXPORT",DA)
    3)= IMAGE EXPORT REQUEST
    Used by Multimedia Mail as a signal to request an image to be copied from the image directory to the export directory. The cross-reference is set when the request is made and killed when the image has been copied over for
    export.
30 DELETED BY 30;1 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  MAY 19, 2004
  • HELP-PROMPT:  This is system added field. The Person who deleted the image.
  • DESCRIPTION:  
    This is the person who deleted the image.  It is a pointer to the new person file.  The system uses the DUZ variable to set the field.
30.1 DELETED DATE 30;2 DATE

  • INPUT TRANSFORM:  S %DT="EST" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JAN 24, 2007
  • HELP-PROMPT:  This is the date the Image was deleted from the Image File.
  • DESCRIPTION:  
    This is the date the Image was deleted from the Image File.
30.2 DELETED REASON 30;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<10) X
  • LAST EDITED:  MAY 19, 2004
  • HELP-PROMPT:  The Reason that the Image was deleted from the Patient record.
  • DESCRIPTION:  
    This is the Reason that the Image was deleted.
40 PACKAGE INDEX 40;1 SET
  • 'RAD' FOR RAD;
  • 'LAB' FOR LAB;
  • 'MED' FOR MED;
  • 'NOTE' FOR NOTE;
  • 'CP' FOR CP;
  • 'SUR' FOR SUR;
  • 'PHOTOID' FOR PHOTOID;
  • 'NONE' FOR NONE;
  • 'CONS' FOR CONS;

  • LAST EDITED:  FEB 03, 2003
  • HELP-PROMPT:  The Package associated with the Image
  • DESCRIPTION:  
    This is an abbreviation of the package that the Image is attached to.
  • RECORD INDEXES:  AUDIT40 (#515)
41 CLASS INDEX 40;2 POINTER TO IMAGE INDEX FOR CLASS FILE (#2005.82) IMAGE INDEX FOR CLASS(#2005.82)

  • LAST EDITED:  FEB 03, 2003
  • DESCRIPTION:  
    The Classification of the Image.  CLASS is an index field used for sorting and searching.
42 TYPE INDEX 40;3 POINTER TO IMAGE INDEX FOR TYPES FILE (#2005.83) IMAGE INDEX FOR TYPES(#2005.83)

  • LAST EDITED:  FEB 03, 2003
  • DESCRIPTION:  
    The TYPE of Image.  TYPE is an index field used for sorting and searching.
  • RECORD INDEXES:  AUDIT40 (#515)
43 PROC/EVENT INDEX 40;4 POINTER TO IMAGE INDEX FOR PROCEDURE/EVENT FILE (#2005.85) IMAGE INDEX FOR PROCEDURE/EVENT(#2005.85)

  • LAST EDITED:  FEB 03, 2003
  • DESCRIPTION:  
    The PROCEDURE/EVENT of Image.  PROCEDURE/EVENT is an index field used for sorting and searching.
  • RECORD INDEXES:  AUDIT40 (#515)
44 SPEC/SUBSPEC INDEX 40;5 POINTER TO IMAGE INDEX FOR SPECIALTY/SUBSPECIALTY FILE (#2005.84) IMAGE INDEX FOR SPECIALTY/SUBSPECIALTY(#2005.84)

  • LAST EDITED:  FEB 03, 2003
  • DESCRIPTION:  The SPECIALTY/SUBSPECIALTY of Image.
    SPECIALTY/SUBSPECIALTY is an index field used for sorting and searching.
  • RECORD INDEXES:  AUDIT40 (#515)
45 ORIGIN INDEX 40;6 SET
  • 'V' FOR VA;
  • 'N' FOR NON-VA;
  • 'D' FOR DOD;
  • 'F' FOR FEE;
  • 'I' FOR IHS;

  • LAST EDITED:  OCT 07, 2015
  • HELP-PROMPT:  Select Origin Index.
  • DESCRIPTION:  
    This field indicates whether this image originated inside or outside of VA.
  • TECHNICAL DESCR:  NOTE: IHS(RPMS) has extra index, Origin: TRIBAL, URBAN *p163
    VA(VistA) does not list them.
  • RECORD INDEXES:  AUDIT40 (#515)
50 PATH ACCESSION NUMBER PATH;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>9!($L(X)<5) X
  • LAST EDITED:  FEB 11, 1993
  • HELP-PROMPT:  Answer must be 5-9 characters in length.
  • DESCRIPTION:  
    This is the Anatomic Pathology accession number - the identifying number for the slide.
51 SPECIMEN DESCRIPTION PATH;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3) X
  • LAST EDITED:  JUL 09, 1993
  • HELP-PROMPT:  Answer must be 3-30 characters in length.
  • DESCRIPTION:  
    This is the description given to the specimen in the Lab Data file - the information is carried over and stuffed into the Image file.
52 SPECIMEN# PATH;3 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>10)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  FEB 16, 1993
  • HELP-PROMPT:  Type a Number between 1 and 10, 0 Decimal Digits
  • DESCRIPTION:  
    This is the specimen number of the slide given in the Lab Data file.
53 STAIN PATH;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<2) X
  • LAST EDITED:  APR 14, 1997
  • HELP-PROMPT:  Answer must be 2-30 characters in length.
  • DESCRIPTION:  
    Free text description of the Histological Stain. It is the stain used in the preparation of the specimen and is chosen by the pathologist from the Histological Stain file list.
54 MICROSCOPIC OBJECTIVE PATH;5 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>10!($L(X)<1) X
  • LAST EDITED:  APR 14, 1997
  • HELP-PROMPT:  Answer must be 1-10 characters in length.
  • DESCRIPTION:  
    Free text description of the Microscopic Objective selected by the pathologist. It identifies the power of the microscope objective used when capturing the image of the slide.
60 PACS UID PACS;1 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>64!($L(X)<1) X
  • LAST EDITED:  NOV 07, 2000
  • HELP-PROMPT:  Answer must be 1-64 characters in length.
  • DESCRIPTION:  
    This field is used by the VISTA-PACS interface and is the unique (up to) 64 character image identifier of the PACS image.
  • CROSS-REFERENCE:  2005^P
    1)= S ^MAG(2005,"P",X,DA)=""
    2)= K ^MAG(2005,"P",X,DA)
    3)= PACS UNIVERSAL IDENTIFIER
    This cross reference is set by images captured from VistA Imaging DICOM Gateways. The cross reference is set to the Study Instance UID (0020,000D) for a Group Entry, and the SOP Instance UID (0008,0018), or Image UID, for
    an Image Entry.  (These values are set in ^MAGDIR2A and ^MAGDIR2B, respectively.)
61 RADIOLOGY REPORT PACS;2 POINTER TO RAD/NUC MED REPORTS FILE (#74) RAD/NUC MED REPORTS(#74)

  • LAST EDITED:  JUN 15, 1993
  • DESCRIPTION:  
    Pointer to Radiology Report file used by the PACS interface to tie the image to the correct radiology report.
62 PACS PROCEDURE PACS;3 POINTER TO RAD/NUC MED PROCEDURES FILE (#71) RAD/NUC MED PROCEDURES(#71)

  • LAST EDITED:  JUL 08, 1993
  • HELP-PROMPT:  RADIOLOGICAL PROCEDURE
  • DESCRIPTION:  
    This field is used by the VistA-PACS interface and is a backwards pointer to the Radiology Reports file with which this radiological image is associated.
63 PARENT GLOBAL ROOT D1 2;10 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAR 16, 1995
  • HELP-PROMPT:  Type a Number between 0 and 999999999, 0 Decimal Digits
  • DESCRIPTION:  The values of fields 16, 17, 18 and 63 are numbers. These numbers are internal entry numbers. Which field corresponds to which internal entry number is explained below.
    Together, the values of these fields establish a link back to the entry in the "parent" file, that holds the information that describes why the image was collected.
    The link to the "parent" information is brought about by the combination of the values of fields 16, 17, and, 18, and optionally also field 63.
    The value of field 16 is a number that indicates the internal entry number of the "parent file" in the VA-FileMan data dictionary.  Common parent files are:
    File    Name
    ====    ====
    3.9:  MAIL MESSAGE
    63:    AUTOPSY (MICROSCOPIC)
    63.02: ELECTRON MICROSCOPY
    63.08: SURGICAL PATHOLOGY
    63.09: CYTOLOGY
    63.2:  AUTOPSY (GROSS)
    74:    RADIOLOGY
    130:    SURGERY
    691:    ECHOCARDIOGRAM
    691.1:  CARDIAC CATHETERIZATION
    691.5:  ELECTROCARDIOGRAPHY
    694:    HEMATOLOGY
    699:    ENDOSCOPY
    699.5:  GENERIC MEDICINE
    8925:    TIU
    The records in each of these "parent" files contain a multiple that itemizes the list of images that belong to that record.
    The field numbers and fixed indexes for those multiples all have the number 2005. The entries within these multiples all have a field that is a pointer back to the image file.  The entries in these multiples identify the
    various images that belong with the record in question.
    The various parent files each have their own structure, for instance
    Type Number     Form of Root
    ===========     ============
    1           ^RARPT(D0,2005,D1,0)=image...
    2           ^MCAR(699,D0,2005,D1,0)=image...
    3           ^LR(D0,"SP",D1,2005,D2,0)=image...
    Depending on the nature of the file structure of the parent file, the imaging software will need either just the value of D0 (type 1 and type 2) to find the correct entry, or the values of D0 as well as D1 (type 3).
    The values of the fields in the image file correspond to the values of the indices in the parent file as follows:
    Type Number   Field Number and FileMan Index
    ===========   ==============================
    1         field 17 = D0, field 18 = D1
    2         field 17 = D0, field 18 = D1
    3         field 17 = D0, field 63 = D1, field 18 = D2
    In the case of type 3, the value of D0 is equal to the value of LRDFN.
64 PARENT ASSOCIATION DATE 2;11 DATE

  • INPUT TRANSFORM:  S %DT="EST" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  DEC 22, 2005
  • HELP-PROMPT:  (No range limit on date)
  • DESCRIPTION:  
    This is the Date that the Document/Image was associated with the Parent Data File. Field # 16
99 AUDIT 99;0 DATE Multiple #2005.099 2005.099

  • LAST EDITED:  MAR 21, 2008
  • DESCRIPTION:  This multiple stores previous values of the record fields (audit trail).
    See the "AUDIT2", "AUDIT40", and "AUDIT100" cross-references for more details.
  • TECHNICAL DESCR:  
    Added by the patch MAG*3*93.
    WRITE AUTHORITY:  @
  • GROUP:  MAG*3*93
  • INDEXED BY:  FIELD NUMBER & DATE/TIME RECORDED (FD)
100 DESCRIPTIVE CATEGORY 100;1 POINTER TO MAG DESCRIPTIVE CATEGORIES FILE (#2005.81) MAG DESCRIPTIVE CATEGORIES(#2005.81)

  • LAST EDITED:  JUL 14, 1995
  • HELP-PROMPT:  Enter the Category of the Image.
  • DESCRIPTION:  
    This is mainly for Document Imaging, it further describes the type of document image.
101 CLINIC 100;2 POINTER TO HOSPITAL LOCATION FILE (#44) HOSPITAL LOCATION(#44)

  • LAST EDITED:  JUL 10, 1996
  • HELP-PROMPT:  This is a pointer to the hospital location file.
  • DESCRIPTION:  Points to the Hospital location file and will be used mainly for document images. If an image is associated with a patient encounter (visit), this is the clinic they had (will have) the appointment. The appointment
    date/time is in field #15, PROCEDURE/EXAM DATE/TIME.
102 BIG MAGNETIC PATH FBIG;1 POINTER TO NETWORK LOCATION FILE (#2005.2) NETWORK LOCATION(#2005.2)

  • LAST EDITED:  MAY 05, 1998
  • HELP-PROMPT:  This is the BIG file, i.e. the 2k by 2k Radiology image
  • DESCRIPTION:  
    Full file path description for Image file of .BIG file types.  This field will indicate on which magnetic server this file resides.
103 BIG JUKEBOX PATH FBIG;2 POINTER TO NETWORK LOCATION FILE (#2005.2) NETWORK LOCATION(#2005.2)

  • LAST EDITED:  MAY 05, 1998
  • HELP-PROMPT:  The JukeBox location of the BIG file. (the 2k by 2k Rad image)
  • DESCRIPTION:  
    Full file path on jukebox for images of .BIG file extension.  This field will indicate whether this file is located on the Jukebox.
104 BIG FILE EXTENSION FBIG;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>5!($L(X)<3) X
  • LAST EDITED:  MAY 13, 2009
  • HELP-PROMPT:  Enter a 3-5 character file extension.
  • DESCRIPTION:  
    This is the Image File Extension (e.g. DCM, BIG).
106 ROUTING TIMESTAMP 4;0 DATE Multiple #2005.0106 2005.0106

  • LAST EDITED:  FEB 20, 2003
  • DESCRIPTION:  
    This field keeps track of any routing activity.
107 ACQUISITION DEVICE 100;4 POINTER TO ACQUISITION DEVICE FILE (#2006.04) ACQUISITION DEVICE(#2006.04)

  • LAST EDITED:  JAN 14, 2001
  • HELP-PROMPT:  Enter the device that performed the Image Acquisition.
108 TRACKING ID 100;5 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3) X
  • LAST EDITED:  MAR 12, 2001
  • HELP-PROMPT:  Package ID that performed the Import ";" Internal package identifier
  • DESCRIPTION:  
    This field tracks the packages that are using the Import API.  It is an ";" (semicolon) delimited free text field.  First piece is the Package ID that performed the Import Second piece is the Internal package identifier
  • CROSS-REFERENCE:  2005^ATRKID
    1)= S ^MAG(2005,"ATRKID",$E(X,1,30),DA)=""
    2)= K ^MAG(2005,"ATRKID",$E(X,1,30),DA)
    Cross reference of images imported using the Import API.  TrkID is a unique identifier of the package, or OTS Application that initiated the Import using Imagings Import API. ( silent call)
109 CREATE METHOD METHOD;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>245!($L(X)<3) X
  • LAST EDITED:  JAN 30, 2001
  • HELP-PROMPT:  This field holds the command that either has created the image(s), or will dynamically access the Image from the Display GUI.
  • DESCRIPTION:  This field holds the command that either
    has created the image(s)
    or will dynamically access the Image when called from the Display GUI an example is a DLL provided by a COTS product.  When the DLL is called, it generates the image.
110 DOCUMENT DATE 100;6 DATE

  • INPUT TRANSFORM:  S %DT="EST" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JAN 18, 2007
  • HELP-PROMPT:  Enter the date (optionally time too) when this document was created.
  • DESCRIPTION:  
    Document Images can have a separate date, unlike clinical images that are attached to a procedure, and only procedure date is needed.
  • RECORD INDEXES:  AUDIT100 (#513)
111 ROUTING LOG 6;0 Multiple #2005.0111 2005.0111
112 CONTROLLED IMAGE 100;7 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  JUL 18, 2008
  • HELP-PROMPT:  Select YES, if the image must not be shown until the user explicitly selects it.
  • DESCRIPTION:  In the Clinical Display application, the abstract of a controlled image is not shown in the Abstracts or Group Abstracts window. A "canned" bitmap is shown in place of the image. It has a text that states that the image is
    controlled.
    Controlled images are not displayed until the user explicitly selects the image to be viewed.
    If the value of this field is 'NO' or the field is empty, then the image is handled "as usual": the actual abstract of the image is shown in the Abstracts and Group Abstracts windows.
  • TECHNICAL DESCR:  
    Added by the patch MAG*3*93.
  • GROUP:  MAG*3*93
  • RECORD INDEXES:  AUDIT100 (#513)
112.1 CONTROLLED DATE COMPUTED DATE

  • MUMPS CODE:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,D0_",",112),"^",2),1:"")
  • ALGORITHM:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,DO_",",112),"^",2),1:"")
  • LAST EDITED:  JUL 17, 2008
  • DESCRIPTION:  
    This field indicates date/time of the most recent change of the image controlled status (see the CONTROLLED IMAGE field (112)).
  • TECHNICAL DESCR:  See the $$LASTAUDT^MAGUTL04 function for more details.
    Added by the patch MAG*3*93.
  • GROUP:  MAG*3*93
112.2 CONTROLLED BY COMPUTED POINTER TO NEW PERSON FILE (#200)

  • MUMPS CODE:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,D0_",",112),"^",3),1:"")
  • ALGORITHM:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,D0_",",112),"^",3),1:"")
  • LAST EDITED:  JUL 17, 2008
  • DESCRIPTION:  
    This field references the user who made the most recent change of the image controlled status (see the CONTROLLED IMAGE field (112)).
  • TECHNICAL DESCR:  See the $$LASTAUDT^MAGUTL04 function for more details.
    Added by the patch MAG*3*93.
  • GROUP:  MAG*3*93
113 STATUS 100;8 SET
************************REQUIRED FIELD************************
  • '1' FOR Viewable;
  • '2' FOR QA Reviewed;
  • '10' FOR In Progress;
  • '11' FOR Needs Review;
  • '12' FOR Deleted;
  • '13' FOR Image Never Existed;

  • LAST EDITED:  FEB 22, 2013
  • HELP-PROMPT:  Select the current status of the image.
  • DESCRIPTION:  Viewable
    By default, all images are viewable, and images
    with no status are considered viewable.
    QA Reviewed
    A user has viewed the image and verified that
    the patient identifier and values of index
    fields are correct for this image.
    In Progress
    When capturing image groups, this status will
    indicate that the images are being added to the
    group of images. When the process is complete,
    the status will change to Viewable.
    Needs Review
    Indicates that value(s) of the index fields or
    patient identifier have been found to be
    incorrect. VistA Imaging Display application
    will block images with this status from being
    viewed. The Image Edit utility can be used to
    modify the incorrect values of the index fields.
    Deleted
    Marks the image as deleted.
    Image Never Existed
    There was an Error while copying the Image to
    the Image Share.  The Image entry is deleted
    and the status is set as Image Never Existed.
  • TECHNICAL DESCR:  Use only positive canonic numbers for internal values.
    Added by the patch MAG*3*93.  Updated by the patch MAG*3*135
  • GROUP:  MAG*3*93
  • RECORD INDEXES:  AGPD (#511), AUDIT100 (#513)
113.1 STATUS DATE COMPUTED DATE

  • MUMPS CODE:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,D0_",",113),"^",2),1:"")
  • ALGORITHM:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,D0_",",113),"^",2),1:"")
  • LAST EDITED:  JUL 18, 2008
  • DESCRIPTION:  
    This field indicates date/time of the most recent change of the image status (see the STATUS field (113)).
  • TECHNICAL DESCR:  See the $$LASTAUDT^MAGUTL04 function for more details.
    Added by the patch MAG*3*93.
  • GROUP:  MAG*3*93
113.2 STATUS BY COMPUTED POINTER TO NEW PERSON FILE (#200)

  • MUMPS CODE:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,D0_",",113),"^",3),1:"")
  • ALGORITHM:  S X=$S($G(D0)>0:$P($$LASTAUDT^MAGUTL04(2005,D0_",",113),"^",3),1:"")
  • LAST EDITED:  JUL 18, 2008
  • DESCRIPTION:  
    This field references the user who made the most recent change of the image status (see the STATUS field (113)).
  • TECHNICAL DESCR:  See the $$LASTAUDT^MAGUTL04 function for more details.
    Added by the patch MAG*3*93.
  • GROUP:  MAG*3*93
113.3 STATUS REASON 100;9 POINTER TO MAG REASON FILE (#2005.88) MAG REASON(#2005.88)

  • INPUT TRANSFORM:  S DIC("S")="I $P($G(^(0)),""^"",2)[""S""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  OCT 06, 2008
  • HELP-PROMPT:  Select the reason for the image status change.
  • DESCRIPTION:  
    This field indicates the reason for the latest image status change (see the STATUS field (113)).
  • TECHNICAL DESCR:  
    Added by the patch MAG*3*93.
  • SCREEN:  S DIC("S")="I $P($G(^(0)),""^"",2)[""S"""
  • EXPLANATION:  Only reasons applicable to image status changes can be selected.
  • GROUP:  MAG*3*93
  • CROSS-REFERENCE:  2005^ASTRSN^MUMPS
    1)= S ^MAG(2005.88,"AREF",X,2005,DA_",",113.3)=""
    2)= K ^MAG(2005.88,"AREF",X,2005,DA_",",113.3)
    The logic of the ASTRSN cross-reference maintains a list of references from the STATUS REASON field (113.3) of the IMAGE file (#2005) to the MAG REASON file (#2005.88).
    This list is used by the logic of the "DELETE" node of the REASON field (.01) of the MAG REASON file (#2005.88) to prevent deletion of reasons that are referenced by records of other files.
    The list is stored under the "AREF" subscript in the MAG REASON file (#2005.88) and has the following structure:
    ^MAG(2005.88,"AREF",,2005,,113.3) = ""
    The  is the IEN of the reason that is pointed by the STATUS REASON field (113.3).
    The 2005 is the number of the file from where the reason is referenced (IMAGE).
    The  is the IENS of the record of the IMAGE file (#2005) that references the reason.
    The 113.3 is the number of the field that points to the reason (STATUS REASON).
  • RECORD INDEXES:  AUDIT100 (#513)
114 NUMBER OF PAGES 100;10 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 15, 2008
  • HELP-PROMPT:  Enter number of pages in a multi-page image (between 1 and 999999999).
  • DESCRIPTION:  
    This field stores number of pages in a multi-page document (e.g. multi-page TIFF image).
  • TECHNICAL DESCR:  
    Added by the patch MAG*3*93.
  • GROUP:  MAG*3*93
115.1 LINKED IMAGE 100;11 POINTER TO IMAGE AUDIT FILE (#2005.1) IMAGE AUDIT(#2005.1)

  • LAST EDITED:  JUN 30, 2011
  • HELP-PROMPT:  If this object is linked, enter the original.
  • DESCRIPTION:  This is a pointer to the rescinded image. For example, when an image is rescinded a new image entry is created and the original is deleted. A link is established between the new image and the rescinded image. The value of
    the field is the rescinded image.
  • TECHNICAL DESCR:  
    Added in patch MAG*3.0*121.
115.2 LINKED TYPE 100;12 SET
  • '1' FOR RESCINDED;

  • LAST EDITED:  MAR 08, 2011
  • HELP-PROMPT:  Enter the type of the relationship between the linked images.
  • DESCRIPTION:  This is the type of the image link. For example, when image is rescinded a new image entry is created and the original is deleted. A link is established between the new image and the rescinded image. The value of the
    LINKED TYPE will be "RESCINDED".
  • TECHNICAL DESCR:  
    Added in patch MAG*3.0*121.
115.3 LINKED DATE 100;13 DATE

  • INPUT TRANSFORM:  S %DT="ETX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  MAY 19, 2011
  • HELP-PROMPT:  Enter the date and time when the image was linked.
  • DESCRIPTION:  
    This is the date that the Document/Image was associated with the LINKED IMAGE.
  • TECHNICAL DESCR:  
    Added in patch MAG*3.0*121.
210 PRESENTATION STATE 210;0 Multiple #2005.05 2005.05

  • LAST EDITED:  JUL 07, 2004
  • DESCRIPTION:  
    Image Presentation state data stored below; this is free-text in XML format.  Annotations are included in this data.
251 DICOM SOP CLASS SOP;1 POINTER TO DICOM SOP CLASS FILE (#2006.532) DICOM SOP CLASS(#2006.532)

  • LAST EDITED:  JAN 11, 2005
  • HELP-PROMPT:  Identify the SOP Class that was used to acquire this image.
  • DESCRIPTION:  
    The value of this field is a pointer. The pointed to record identifies the DICOM SOP Class that was used to acquire this image.
252 NEW SOP INSTANCE UID SOP;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>64!($L(X)<1)!'($TR(X,"1234567890.")="") X
  • LAST EDITED:  NOV 09, 2004
  • HELP-PROMPT:  Enter the VA's new SOP instance UID for the corrected image.
  • DESCRIPTION:  The value of this field is a string that represents a DICOM UID. The DICOM standard defines the format of a UID: a string containing only digits and periods that does not exceed a length of 64 characters. This field is
    populated when a corrected version of an image is exported, and the corrections are of such a nature that the image cannot be exported with its original SOP Instance UID.  Note that this UID value is assigned by VA
    software, and thus will always start with the characters "1.2.840.113754.".
  • FIELD INDEX:  P (#212) MUMPS IR LOOKUP & SORTING
    Short Descr:  UID for corrected images
    Description:  This cross-reference includes SOP Instance UIDs for corrected images in the cross-reference on the original SOP Instance UIDs.
    Set Logic:  S ^MAG(2005,"P",X,DA)=""
    Kill Logic:  K ^MAG(2005,"P",X,DA)
    Whole Kill:  K ^MAG(2005,"P")
    X(1):  NEW SOP INSTANCE UID  (2005,252)  (Subscr 1)  (forwards)
253 SERIES UID SERIESUID;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>64!($L(X)<1)!'(X?1.64(1N,1".")) X
  • LAST EDITED:  AUG 03, 2005
  • HELP-PROMPT:  Enter the Series UID for the current image.
  • DESCRIPTION:  The value of this field is a DICOM unique identifier for the series to which an image belongs. A DICOM UID looks like a series of digits and periods, is not longer than 64 characters, starts and ends with a digit and
    never has two consecutive periods.
  • FIELD INDEX:  SERIESUID (#671) REGULAR IR LOOKUP & SORTING
    Short Descr:  Images sorted by Series UID
    Description:  This cross-reference keeps track of which images have which Series UID.
    Set Logic:  S ^MAG(2005,"SERIESUID",X,DA)=""
    Kill Logic:  K ^MAG(2005,"SERIESUID",X,DA)
    Whole Kill:  K ^MAG(2005,"SERIESUID")
    X(1):  SERIES UID  (2005,253)  (Subscr 1)  (forwards)

ICR, Total: 8

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #459
  • MAILMAN
  • Image Name (.01).
    Access: Both R/W w/Fileman

    DISK & VOL,MAGNETIC (2).
    Access: Both R/W w/Fileman

    FILEREF (1).
    Access: Both R/W w/Fileman

    OBJECT TYPE (3).
    Access: Both R/W w/Fileman

    COLLECTION DATE (14).
    Access: Both R/W w/Fileman

    DISK & VOLUME. - ABSTRACT (2.1).
    Access: Both R/W w/Fileman

    DISK & VOL.: WORM (2.2).
    Access: Both R/W w/Fileman

    MailMan $ORDERs from here to test to see if there areimages in the system and if there are none, assumes that imaging is notinstalled.
    ICR #470
  • CLINICAL PROCEDURES
  • The Medicine package is pointing to File 2005 toreference each Medicine Procedure that has images.
    ICR #1324
  • RADIOLOGY/NUCLEAR MEDICINE
  • The Radiology/Nuclear Medicine package performs thefollowing test to determine if the Image File #2005 is populated:I $O(^MAG(2005,0))
    ICR #2791
  • HEALTH SUMMARY
  • PATIENT (5).
    Access: Read w/Fileman

    PATIENT (5).
    Access: Read w/Fileman

    PROCEDURE (6).
    Access: Read w/Fileman

    PROCEDURE/EXAM DATE/TIME (15).
    Access: Read w/Fileman

    SHORT DESCRIPTION (10).
    Access: Read w/Fileman

    Cross reference on patient dfn.
    ICR #2927
  • Text Integration Utility
  • Internal Entry Number (IEN).
    Access: Pointed to

    ICR #4009
  • Text Integration Utility
  • ICR #5291
  • INSURANCE CAPTURE BUFFER
  • Cross reference of images imported using the Import API
    ICR #6192
  • VA Point of Service
  • PATIENT (5).
    Access: Read w/Fileman

    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  All