| ICR LINK | Subscribing Package(s) | Fields Referenced | Description |
|---|---|---|---|
| ICR #29 | |||
| ICR #135 | |||
| ICR #171 | |||
| ICR #192 | |||
| ICR #299 | |||
| ICR #314 | |||
| ICR #316 | |||
| ICR #345 | |||
| ICR #352 | |||
| ICR #395 | |||
| ICR #508 | Used to format date. | ||
| ICR #842 | |||
| ICR #903 | |||
| ICR #987 | |||
| ICR #999 | |||
| ICR #1111 | This node is used in the input transform and in thescreen of the DUPLICATE RESOLUTION FILE 15.1. It's used in a variable pointertype field to restrict the user to only those files which have been set up forthe merge.These global references are used in displaying thefields that can be compared and assigned a matching value. The 0 node of thefield is referenced in order to screen out 'computed' and 'multi-valued'fields from this display and comparison. One use of these references can beseen in the executable help of field .05, FIELD TO BE CHECKED.These global references are used in displaying thefields that can be compared and assigned a matching value. The 0 node of thefield is referenced in order to screen out 'computed' and 'multi-valued'fields from this display and comparison. One use of these references can beseen in the executable help of field .05, FIELD TO BE CHECKED. | ||
| ICR #1126 | The VA Cross-Referencer utility in Toolkit needs to reference several ^DDnodes in order to cross-reference a package. Several of the referenced DDnodes contain M code. They are inspected to find items such asglobal/variables names and label /external references. Some of the referencednodes are the "LAYGO", "DEL" nodes. A specific example of a DD referencefollows:>>>>>%INDX10+25S INDEL="" F G=0:0 S INDEL=$O(^DD(INDFN,INDF,"LAYGO",INDEL)) Q:INDEL=""I $D(^(INDEL,0))#2 S INDC=INDF_"LAYGO"_INDEL_" ; LAYGO CHECK CODE",INDX=^(0)D ADDThe DD references are found in routines %INDX10, %INDX11, %INDX53. | ||
| ICR #1168 | The modification here is to change:^DD(124.6,.01,1,1,1)=S ^GMRD(124.6,"B",$E(X,1,30),DA)="" to:^DD(124.6,.01,1,1,1)=S ^GMRD(124.6,"B",$E(X,1,60),DA)=""The modification here is to change:^DD(124.6,.01,1,1,2)=K ^GMRD(124.6,"B",$E(X,1,30),DA) to:^DD(124.6,.01,1,1,2)=K ^GMRD(124.6,"B",$E(X,1,60),DA) | ||
| ICR #1206 | |||
| ICR #1237 | |||
| ICR #1258 | |||
| ICR #1412 | LABEL (.01). Access: Direct Global Read & w/Fileman POINTER (.3). Access: Direct Global Read & w/Fileman INPUT TRANSFORM (.5). Access: Direct Global Read & w/Fileman 'HELP'-PROMPT (3). Access: Direct Global Read & w/Fileman XECUTABLE 'HELP' (4). Access: Direct Global Read & w/Fileman READ ACCESS (OPTIONAL) (8). Access: Direct Global Write & w/Fileman WRITE ACCESS (OPTIONAL) (9). Access: Direct Global Write & w/Fileman DESCRIPTION (21). Access: Direct Global Read & w/Fileman SET STATEMENT (1). Access: Direct Global Read & w/Fileman KILL STATEMENT (2). Access: Direct Global Read & w/Fileman |
Nursing and Text Generator have permission to kill thisnode to uncompile cross-references on the Aggregate Term (124.2) file.Nursing and the Text Generator are allowed direct globalread access to ^DD(file,field,1,xref_ien) in order to loop through thecross-reference multiple for their files, where file is in the packagenumberspace assigned by the DBA, field is a valid field in file, and xref_ienis the ien of the cross-reference for field in file.Nursing can direct global read the ^DD(file,"SB")cross-reference to determine the sub-files for a particular file/sub-file.file is a valid number in the Nursing numberspace as assigned by the DBA.Vitals, Nursing & Text Generator have permission to killoff this node.Vitals, Nursing & Text Generator have permission to killoff this node.Nursing has permission to direct global kill/write thisnode when setting up the "ANURS" cross-reference in the Patient file. MAS hasalready approved this, see MailMessage #18109934.Nursing can direct global write the following nodes:^DD(2,.1,1,xref_ien,0)="2^ANURS^MUMPS", ^DD(2,.1,1,xref_ien,1)="S%X=X,X=""NURSCPL"" X ^%ZOSF(""TEST"") S X=%X D:$T EN1^NURSCPL",^DD(2,.1,1,xref_ien,2)="S %X=X,X=""NURSCPL"" X ^%ZOSF(""TEST"") S X=%XD:$T EN2^NURSCPL". xref_ien is the next available cross-reference ien forfield .1. A direct global read is allowed on ^DD(2,.1,1,xref_ien) to loopthrough the xrefs of field .1. Nursing can direct global kill the ANURScross-reference via a direct global kill of the ^DD(2,.1,1,xref_ien) node.xref_ien is ien of the ANURS xref (where$P(^DD(2,.1,xref_ien,0),"^",2)="ANURS"). MAS has already approved this use oftheir file, ref. msg #18109934. | |
| ICR #1450 | Direct global read/kill to loop through thecross-reference multiple of the .01 field of File 120.8 to find and kill theANKA01 cross-reference. D0 is the cross-reference internal entry number.Direct global read of the second piece of the zero nodeto determine the cross-reference name. D0 is the internal entry number of thecross-reference.Direct kill of this node. | ||
| ICR #1941 | (ALL). Access: Direct Global Write & w/Fileman (ALL). Access: Direct Global Write & w/Fileman (ALL). Access: Direct Global Write & w/Fileman |
||
| ICR #2023 | |||
| ICR #2036 | SPECIFIER (.2). Access: Direct Global Read & w/Fileman POINTER (.3). Access: Direct Global Read & w/Fileman |
||
| ICR #2255 | POINTER SCREEN (12). Access: Direct Global Read & w/Fileman |
||
| ICR #2631 | |||
| ICR #2642 | |||
| ICR #2807 | Allows hard setting of node for file or subfile. | ||
| ICR #2991 | |||
| ICR #3040 | |||
| ICR #3261 | Code in routines ^LRBLJCK and ^LRBLJD1 perform Xecutionof the input transform stored at this node in piece 5 to 99 of the data value.This input transform is defined for the UNIT ID field (#.01) of the BLOODINVENTORY file (#65). Routine ^LRBLPED performs a Write of the field namestored at this node in piece 1. This field name is defined for the UNIT IDfield (#.01) of the BLOOD INVENTORY file (#65).Code in routines LRBLJCK and LRBLJD1 perform aconditional Write of help prompt message stored at this node. This help promptmessage is defined for the UNIT ID field (.01) of the BLOOD INVENTORY file(#65).Code in routines LRBLJCK and LRBLJD1 perform conditionalexecution of the executable help stored at this node. This executable help isdefined for the UNIT ID field (#.01) of the BLOOD INVENTORY file (#65).Code in routine ^LRBLJCK performs 1) the Write of thefield name stored at piece 1 of this node, and 2) performs the Xecution of theinput transform stored at piece 5 to 99 of this node. The field name andinput transform is defined for the INVOICE# field (#.03) of the BLOODINVENTORY file (#65).Code in routine ^LRBLJCK performs a conditional write ofthe help prompt message stored at this node. This help prompt message isdefined for the INVOICE# field (#.03) of the BLOOD INVENTORY file (#65).Code in routine LRBLJCK performs a conditional executionof the executable help stored at this node. The executable help is defined forthe INVOICE# field (#.03) of the BLOOD INVENTORY file (#65).Code in routine ^LRBLJD performs variable assignmentequal to the data type stored at piece 3 at this node. This data type isdefined for the DISPOSITION field (#4.1) of the BLOOD INVENTORY file (#65).Code in routine ^LRBLJD and ^LRBLJD1 perform conditionalXecution of the Mumps X-references stored at the following nodes:^DD(65,4.1,1,1,1) = node 1 of "AC" x-ref ^DD(65,4.1,1,2,1) = node 1 of "APS"x-ref ^DD(65,4.1,1,1,2) = node 2 of "AC" x-ref ^DD(65,4.1,1,2,2) = node 2 of"APS" x-ref ^DD(65,4.1,1,3,2) = node 2 of "AG" x-ref These Mumps x-referencesis defined for the DISPOSITION field (#4.1) of the BLOOD INVENTORY file (#65).Code in routine ^LRBLJD1 performs conditional executionof the Regular x-reference stored at this node. This "AC" Regular x-ref isdefined for DISPOSITION DATE filed (#4.2) of the BLOOD INVENTORY file (#65).Code in routine ^LRBLJLA performs a conditional Write ofthe help prompt message stored at this node. This help prompt message isdefined for the LINES IN A LABLE field (#.07) of the LAB SECTION PRINT file(#69.2).Code in routine ^LRBLJLA performs conditional Xecutionof the executable help stored at this node. This executable help is definedfor the LINES IN A LABEL field (#.07) of the LAB SECTION PRINT file (#69.2).Code in routine ^LRBLJLA performs Xecution of the inputtransform stored at piece 5 to 99 of this node. This input transform isdefined for LINES IN A LABEL field (#.07) of the LAB SECTION PRINT file(#69.2).Code in routine ^LRBLPED performs a Write of the fieldname stored at this node in piece 1 of the data string. This field name isfor the SPECIFIC GRAVITY field (#.23) of the BLOOD PRODUCT file (#66).Code in routine ^LRBLPED performs a Write of the fieldname stored at this node in piece 1. This field name is for the PEDIATRICPRODUCT field (#.22) of the BLOOD PRODUCT file (#66).Code in routine ^LRBLQST performs variable assignmentequal to the data type stored at piece 3 at this node. This data type isdefined for the POS/INCOMPLETE SCREENING TESTS (#8.1) of the BLOOD INVENTORYfile (#65).Code in routine ^LRBLQST performs variable assignmentequal to the data type stored at piece 3 at this node. This data type isdefined for the DONATION TYPE (#8.3) for the BLOOD INVENTORY file (#65). | ||
| ICR #3357 | |||
| ICR #3404 | |||
| ICR #3626 | The current write access in the #20.51 field of the#300.11 file is set to the "^" character, which prevent any updates (includingprogrammer updates). This access will be changed to "@" with the followingcode: S ^DD(300.11,20.51,9)="@" | ||
| ICR #3805 | This is an undocumented data dictionary node thatrestricts a file from a VistA user.This is an undocumented data dictionary node thatrestricts a file from a VistA user.This is an undocumented data dictionary node thatrestricts a file from a VistA user.This is an undocumented data dictionary node thatrestricts a file from a VistA user.This is an undocumented data dictionary node thatrestricts a file from a VistA user.This is an undocumented data dictionary node thatrestricts a file from a VistA user.This is an undocumented data dictionary node thatrestricts a file from a VistA user. | ||
| ICR #3815 | |||
| ICR #4229 | |||
| ICR #4281 | |||
| ICR #4309 | |||
| ICR #4379 | |||
| ICR #4475 | |||
| ICR #4634 | To loop through all file/subfile numbers in VistA asdescribed in the details section.To determine the existence of VUID-related fields.Field 99.991 is one of several fields that contain VUID-related data. | ||
| ICR #4768 | Access to the 'NM' node of a subfile is requested to getthe name of the corresponding field at the previous level. | ||
| ICR #4816 | |||
| ICR #5038 | DD(D0,0,'IX') - Where D0 is the number of a Lexiconfile, and the 'IX' subscript contains a listing of Lexicon fields that arecross-referenced. | ||
| ICR #5067 | |||
| ICR #5163 | |||
| ICR #5164 | |||
| ICR #5200 | |||
| ICR #5551 | |||
| ICR #5692 | CLERK (6). Access: Direct Global R/W & w/Fileman BATCH NUMBER (7). Access: Direct Global R/W & w/Fileman SUPERVISOR (25). Access: Direct Global R/W & w/Fileman |
Data Dictionary Global | |
| ICR #5749 | |||
| ICR #5819 | |||
| ICR #5906 | |||
| ICR #5907 | |||
| ICR #6410 | Set this node to null to prevent a user from being ableto purge data audits for a given file. Setting this node will cause this fileto be screened from the list of selectable files when running option PurgeData Audits [DIAUDIT PURGE DATA].e.g. ^DD(file #,0,"AUDPURGEFORBID")=""Set this node to null to prevent a user from being ableto purge data dictionary (DD) audits for a given file. Setting this node willcause this file to be screened from the list of selectable files when runningoption Purge DD Audits [DIAUDIT PURGE DD].e.g. ^DD(file #,0,"DDAUDPURGEFORBID")="" | ||
| ICR #6793 | This index lists all of the files and their fields thatpoint to the VISIT file (#9000010).The third piece of this node differentiates MUMPS typecross-references from other types of cross-references.This node contains executable M code that will SET thecross-reference. | ||
| ICR #6892 | CROSS-REFERENCE (1). Access: Direct Global Read & w/Fileman |
||
| ICR #7079 | |||
| ICR #7145 |
