| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
| 6 | DBIA6-A | Other | 1 | 1989/07/27 | APPROVED | Active | Private | The following variables are killed only: D0,DI,DIG,DIH,DIU,DIV,& DIQ DIROUT - Is used as a quick exit when ^^ is entered at prompts. DLAYGO - is used for calls to Fileman. |
||||
| 29 | DBIA29 | File | 1 | 1990/02/13 | APPROVED | Active | Private | Routines LRWU5 & LRWU7 Do direct sets to the Data Dictionary. The routines allow the user to add a new Data Name or Antibiotic without giving programmer access. |
||||
| 41 | DBIA41 | File | 1 | 1990/06/06 | APPROVED | Active | Private | Routine DGABTP30 (background job) sets the ^DIBT global. The routine checks for sort templates, specifically [DGPMABSENCES] & [DGPMAB30], through the crossreference, and uses the template's IFN to set node ^DIBT(IFN,1,MOVEMENT IFN) for selected records. |
||||
| 51 | DBIA51 | File | 1 | 1990/10/22 | APPROVED | Active | Private | 720 | The .01 field of file 720, "B" crossreference has been modified to be 50 characters rather than the standard 30. |
|||
| 52 | DBIA52 | File | 1 | 2003/06/10 | Retired | Private | 50 | The "B" cross reference on the .01 field of the Drug File is 40 characters rather than the standard 30. |
||||
| 55 | DBIA55 | File | 1 | 1990/11/28 | APPROVED | Active | Controlled Subscription | Since the use of ^DOPT has a long and honored history, it may be permitted to be used until further notice. |
||||
| 56 | DBIA56 | File | 1 | 1990/11/28 | APPROVED | Active | Private | Given the longstanding history of the use of ^DOPT, scheduling may continue to use it. |
||||
| 135 | DBIA135 | File | 1 | 1991/12/09 | Retired | Private |
The Allergy Tracking System is using +$G(^DD("VERSION")) to check for the version number of the VA FileManager currently installed at the site. If this value is less than 18, the INIT process will abort. |
|||||
| 168 | DBIA168 | File | 1 | 1992/06/16 | Retired | Private | 6 | DSS extracts information from a number of DHCP files. In many of the extracts, provider information is one of the data elements. Because this information is being shipped out of DHCP, we opted to send pointer values rather than names. Since most packages currently point to file 6 and will ultimately point to 200 and since we don't want to try to coordinate releases with all packages, we have chosen to send data in the form of pointer-file. We are looking at the second "P" piece of the second "^" piece of the zero node of the DD for the field in question. Till supported call is available. |
||||
| 171 | DBIA171 | File | 1 | 1992/06/17 | APPROVED | Active | Private | 1.) The SURGERY SITE PARAMETERS file contains a multiple titled REQUIRED FIELDS FOR SCHEDULING which containg fields that must be entered prior to allowing a surgical case to be scheduled. This field points to the global ^DD(130, allowing selection of filed names. ^DD(133.028,.01,0) = REQUIRED FIELDS FOR SCHEDULING^P130'^DD(130,^0;1^Q 2.) The same concept is used in the RISK MODEL LAB TEST file excep we're pointing to the DDs for one of the lab files or sub-files. ^DD(139.21,.01,0) = LABORATORY DATA NAME^M*P63'X^DD(63.04,^0;1^S DIC("S")="I Y>1" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X |
||||
| 180 | DBIA180 | Routine | 1 | 1992/06/18 | APPROVED | Active | Private | Surgery uses the entry point DI^DIU as follows: Prior to entry, the following input variables must be supplied: DI = file number N = 0 X = null (or you can set it to any combination of "WC.01" where W" will screen out word-processing fields, "C" will screen out computed fields, and ".01" will screen out the .01 field at both top and subfile levels.) At the end, all variables set by Surgery will be killed, and in addition, %,C,DA,DDH,DI,DIC,DISYS,I,J and Y will be killed. After calling this routine, varible N will tell how many levels down you went into subfiles (0 is top level, 1 is 1 level down, etc.). The I array will tell the subscript for each multiple level at which the data is located (ex., I(1) for first level down, I(2) for second). The J array will tell the subfile number at each multiple level (ex.,J(1) for first level down, J(2) for second). |
DIU | |||
| 182 | DBIA182 | Routine | 1 | 1992/07/14 | APPROVED | Active | Private | DGPTFMO1 AT LINE 17 ISSUES A CALL TO N^DIP1. This is currently being renegotiated to use a supported reference that will be available in version 21 of Fileman. V21 will still have the entry point N^DIP1, but it is recommended that the new supported reference be used when available. |
DIP1 | |||
| 192 | DBIA192 | File | 1 | 2005/06/20 | Retired | Private | FileMan agrees that Quality Improvement Checklist can call the following routine occurrences of ^DD references: ROUTINE OCCURRENCES OF ^DD REFERENCES: QIPEXT+2: I $D(QIPCUS) W !!,"This option displays the report specifications",!,"for the QUIC",$P($P(";"_$P (^DD(738.1,1,0),"^",3),";"_QIPCUS_":",2)," ;")," extract report(s).",! G EN QIPEXTR+9: I $D(QIPCUS) S PNAME=$P($P(";"_$P(^DD(738.1,1,0),"^",3), CUS_": ",2),";") QIPEXTR+18: K LOC,NAME,PM,PNAME S LOC=^QIP(738.1,OPTN,0),NAME=$P (LOC,"^"),PM=$P(LOC,"^",2),PNAME=$P($P(";"_$P(^DD(738.1,1,0),"^",3), ";"_PM_":",2),"; ") QIPEXTU1+21: W !?10,$J(CNT,2),". ",NAME," - ",$P($P(";"_$P(^DD (738.1,1,0),"^",3),";"_PM_":",2),";")_$S($G(^QIP(738.1,OPTN,"NA")) &(QIP'="V"):" <<NOT AVAILABLE>>",1:"") GLOBAL LISTINGS OF THE REFERENCED DDs: ^DD("42",".03","0")="SERVICE^RSX^M:MEDICINE;S:SURGERY;P:PSYCHIATRY; NH:NHCU;NE:NEUROLOGY;I:INTERMEDIATE MED;R:REHAB MEDICINE;SCI:SPINAL CORD INJURY;D:DOMICILIARY;B:BLIND REHAB;NC:NON-COUNT;^0;3^Q" ^DD("738.1","1","0")="PARENT MENU^RS^L:LABORATORY;M:MAS;N:NURSING; P:PHARMACY;S:SURGERY;Q:QUALITY MANAGEMENT;R:RADIOLOGY;^0;2^Q" |
|||||
| 229 | DBIA229-A | Routine | 1 | 1993/05/18 | APPROVED | Active | Private |
MailMan V7 has permission to make the following calls to FileMan: 1. MailMan has a special way of calling the FileMan editor. It calls EN^DIWE and supplies DWPK, DWLW, DIA, DIC and DIA("P"). The way that MailMan calls DIWE allows a slightly different set of functionalities. The transfer command is defaulted to use the 3.9 (Message) file if no file is specified. DWPK forces automatic wrapping of text at DWLW number of characters. Because of this the variable DC must have the appropriate value and MailMan kills it to may sure it is undefined. DWLW and DWPK have recently been released along with EN^DIWE as a callable entry point, but the use of DIC and DIA together still provide to MailMan special functionality in the FileMan line editor, namely the ability to transfer lines of text in from other messages that the user is the sender or a recipient of. |
DIWE | |||
| 233 | DBIA233 | Other | 1 | 1993/05/18 | APPROVED | Active | Private | MAILMAN has permission to make the following calls to VA Fileman: 1. FileMan has a special way of using the XMD interface and it also has special calls into the XMP series of routines so that it can load INITs directly into a message during a DIFROM. As such the variable DIFROM effects that way some of these routines work so that the DIFROM procedure can use them to enter data and routines reiteratively into messages. o In the routine XMD, if $D(DIFROM) security keys are not ignored. o In the routine XMD, if $D(DIFROM) will cause a call to XMD at either tag EN1 or tag EN2 to quit after text is added to a message, but before the message is delivered. o In the routine XMD, if $D(DIFROM) before delivery, security will be added automatically by a call to XMASEC. o In the routine XMASEC, if $D(DIFROM) security is forced onto the message. o In the routine XMP, if $D(DIFROM) the string " (DIFROM)" is added to the 1st line of the PackMan message to show how it was created. o In the routine XMPH a special prompt is provided where DIFROM loading into a message causes special help for the programmer. 2. Kernel modules to which this document refers are (even if they are at some point separated from the Kernel and become independent modules of their own): FileMan (DI*) |
||||
| 255 | DBIA255 | File | 1 | 1993/07/28 | APPROVED | Active | Private | IVM is granted permission from FM Integration to make the following calls: Permission to add cross-references to the PATIENT file. The cross- references have set and kill logic as follows: S IVMX=X,X="IVMPXFR" X ^%ZOSF("TEST") D:$T DPT^IVMPXFR S X=IVMX K IVMX The code in IVMPXFR looks as follows: DPT ; Update transmit status if patient file fields are updated ; N DFN S DFN=+DA I '$D(^DPT(DFN,0)) Q D IVM Q ; IVM ; check to see if patient needs to be retransmitted N DA,I,NODE,X Q:'$D(^IVM(301.5,"B",DFN)) F DA=0:0 S DA=$O(^IVM(301.5,"B",DFN,DA)) Q:'DA D .S X=$G(^IVM(301.5,DA,0)) .S $P(^IVM(301.5,DA,0),"^",3)=0 .F I=0:0 S I=$O(^DD(301.5,.03,1,I)) Q:'I I $G(^(I,0))'["TRIGGER" D ..S X=1 X ^DD(301.5,.03,1,I,2) ; kill xfr ..S X=0 X ^DD(301.5,.03,1,I,1) ; set xfr Q Permission is also given to execute the DD nodes. At this point, there is a single MUMPS cross-reference on the .03 field (TRANSMISSION STATUS) of the IVM PATIENT file (301.5). Its logic is: set I X=0 S ^IVM(301.5,"ATR",0,DA)="" kill I X=0 K ^IVM(301.5,"ATR",0,DA) The purpose is just to flag the record as needing to be transmitted and have the cross-reference only set for those that require transmission. |
||||
| 262 | DBIA262 | Other | 1 | 1993/08/09 | APPROVED | Active | Private | DataBase Integration Agreement between IFCAP V4.0 package and FileMan V19.0 for the use of and the KILLing of a local FileMan variable in an Input Template. The IFCAP Input Template uses the FileMan local variable D1 in the input transform for field #40 in File #423, the CALM/LOG CODE SHEET file. The local variable D1 is used as a counter for the multiple field 423.05, subfield .01. IFCAP uses the counter within the Input Template to ensure that no more than 10 entries are made into the code sheet for this multiple. Prior to prompting the user for entries into this field, the FileMan variable D1 is KILLed. The reason or reasons for KILLing the FileMan local variable D1 and subsequently using D1 as a counter have been obscured in the history of IFCAP development. The variable D1 is the internal record number within the multiple; it is stored as piece 3 of the file or subfile header. It is not necessarily accurate as the count of entries within the multiple. For example, the user may make one or more deletions within the template, reducing the number of entries. The user could then add more entries to the multiple. This scenario could possibly increase the internal record number (D1) to a number greater than 9, when there may actually be fewer than 9 entries. Based on the input transform, the user would not be able to make the additional entries, although in reality, more entries should be allowed. In addition, piece 4 of the file or subfile header contains the number of records in the file and/or subfile. Once again, this number cannot be guaranteed as the accurate number of records in the file or subfile. The use of D1 is an existing convention that has been in place for several versions of IFCAP. We request the Integration Agreement with FileMan to continue this use for IFCAP V4.0. The Input Templates are used in the creation of CALM code sheets. Since FMS will be replacing CALM, the use of the FileMan local variable will be needed until all sites have converted from CALM to FMS. The next planned release of IFCAP V5.0 will replace this function. INTEGRATION POINT: 1. The IFCAP Input Template PRCFA TT982.00 FIRST EDIT FIELD: .1///CLM// THEN EDIT FIELD: S Y=4// THEN EDIT FIELD: STATION NUMBER// THEN EDIT FIELD: TRANSACTION TYPE// THEN EDIT FIELD: TRANSACTION DATE// THEN EDIT FIELD: REFERENCE NUMBER// THEN EDIT FIELD: YALD CODE// THEN EDIT FIELD: K D1// THEN EDIT FIELD: REC STA OR FCP// THEN EDIT FIELD: REC STA OR FCP// THEN EDIT FIELD: 1ST QTR AMOUNT// THEN EDIT FIELD: 2ND QTR AMOUNT// THEN EDIT FIELD: W !," "// THEN EDIT FIELD: 3RD QTR AMOUNT// THEN EDIT FIELD: I X="$" S Y=""// THEN EDIT FIELD: 4TH QTR AMOUNT// THEN EDIT FIELD: 998///$// 2. The Input Transform Using the FileMan Variable STANDARD DATA DICTIONARY #423.05 -- REC STA OR FCP SUB-FILE 05/20/93 PAGE 1 STORED IN ^PRCF(423, (811 ENTRIES) SITE: IFA UCI: DVA,IFA DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ---------------------------------------------------------------- 423.05,.01 REC STA OR FCP 0;1 FREE TEXT (Multiply asked) INPUT TRANSFORM: K:$L(X)>3!($L(X)<3)!'(X?3N) X Q:'$D(X) I $D(D1),D1>9 W " ONLY 10 ENTRIES PER CODE SHEET ARE PERMITTED",*7 K X LAST EDITED: MAR 21, 1986 HELP-PROMPT: ANSWER MUST BE 3 CHARACTERS IN LENGTH DESCRIPTION: This is the 3 character receiving station or fund control point. NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER 3. FileMan Local Variable D1 When working below the main level of the file, DIE maintains the references to the file hierarchy being handled in the variables DA and Dn (D0, D1, etc) in which n varies according to the level of the file hierarchy. DA always contains the item number of the record being handled. Dn indicates the item numbers in the file hierarchy. D0 contains the main level record number; D1 contains the first sub-file level sub-record number and D2 contains the second sub-file level sub-record number. |
||||
| 291 | DBIA291 | File | 1 | 1993/10/18 | Retired | Private | The Allergy Tracking System V3.0 uses ^DD(142.1,0,"VR") to determine which version of the Health Summary package is currently running. This information is needed to determine which array will be returned by the GMTSLROE and GMTSLRSE utilities. |
|||||
| 299 | DBIA299-A | File | 1 | 1993/10/25 | APPROVED | Active | Private | The PDX (V 1.5) application is granted read access to the DD and DIC globals to accomplish the following tasks: 1) See DBIA 821 2) Get node a field/multiple is stored on $P($P(^DD(FILE,FIELD,0),"^",4),";",1) 3) Get field name $P(^DD(FILE,FIELD,0),"^",1) 4) Determine if a field is date valued $P(^DD(FILE,FIELD,0),"^",2)["D" 5) Determine if a subfile is a word processing field $P(^DD(SUBFILE,.01,0),"^",2)["W" 6) Determine what file a field points to +$P($P(^DD(FILE,FIELD,0),"^",2),"P",2) 7) Determine if a file is a subfile $G(^DD(FILE,0,"UP"))'="" 8) Determine main file number for a subfile $G(^DD(SUBFILE,0,"UP")) 9) Determine main field number for a subfile $O(^DD(MAINFILE,"SB",SUBFILE,"")) 10) Determine subfile number +$P(^DD(FILE,FIELD,0),"^",2) 11) Check for valid file number $D(^DD(FILE)) 12) Check for valid field number $D(^DD(FILE,FIELD)) |
||||
| 314 | DBIA314-A | File | 1 | 1993/11/01 | APPROVED | Active | Private | To support the table-driven upload of transcribed text to various DHCP files, the Discharge Summary application has permission to access the Data Dictionary and File of Files in the following ways: 1. In order to allow the site to specify the target file, fixed-field header elements, and word-processing field for each report type, Discharge Summary version 1 will make several references to either the File of Files or ^DD(. These are ONLY done in setting up a ^DIC call (to look-up a given field in the target file), or in screening logic (e.g., to exclude the programmer at the site from choosing a non-Word-Processing field in the target file as the destination for the body of a report). Needless to say, NO SETs or KILLs are ever executed on any of FileMan's supporting data structures (i.e., ^DD( or ^DIC(). All hard-coded references to ^DIC( or ^DD( are made from within the following code: GMRDUPAR ; SLC/JER - Upload Parameter Edit ;4/23/93 14:53 ;;1.0V2;Discharge Summary;;Sep 02, 1993 MAIN ; Controls branching N DIC,DA,DIE,DLAYGO,DR,GMRDPRM0,GMRDPRM1,GMRDPRM3,GMRDUSRC,GMRD1ST,X,Y D:'$D(GMRDPRM0) SETPARM^GMRDLIBE W !,"First edit Division-wide upload parameters:",! S (DIC,DLAYGO)=128.99,DIC(0)="AEMQL",DIC("A")="Select DIVISION: " D ^DIC K DLAYGO Q:+Y'>0 S DA=+Y S DIE=128.99,DR="[GMRD UPLOAD PARAMETER EDIT]" D ^DIE D SETPARM^GMRDLIBE W !!,"Now edit the REPORT TYPE file:",! F D Q:+$G(Y)'>0 . N GMRDREP,GMRDX . S DIC="^GMR(128.1,",DIC(0)="AEMQZ",DIC("A")="Select REPORT TYPE: " . I $D(^DISV(DUZ,DIC)),'$D(GMRD1ST) S DIC("B")=$G(^DISV(DUZ,DIC)), GMRD1ST=1 . D ^DIC K DIC Q:+Y'>0 S DA=+Y,GMRDREP=Y,GMRDREP(0)=Y(0) . S DIE=128.1,DR="[GMRD UPLOAD PARAMETER EDIT]" . D ^DIE S Y=1 . I $D(^GMR(128.1,+DA,"HEAD"))>9!($D(^GMR(128.1,+DA,"ITEM"))>9) D . . W !!,"The header for the ",$P(GMRDREP,U,2)," Report type is now defined as:" . . I $P(GMRDPRM0,U,16)="D" D DHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . I $P(GMRDPRM0,U,16)="C" D CHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . W ! Q TXTFLD(TFILE,GMRDFLT) ; Get Text Field # from ^DD(Target file #, N DIC,X,Y S DIC="^DD("_TFILE_",",DIC(0)="AEMQZ",DIC("A")="Select TARGET TEXT FIELD : " S DIC("S")="I +$$ISWP^GMRDUPAR(TFILE,+Y)" I $D(GMRDFLT) S DIC("B")=GMRDFLT D ^DIC G:+Y'>0 TXTFLDX S Y=+Y_";"_$P($P(Y(0),U,4),";") TXTFLDX Q Y ISWP(TFILE,TFLD) ; Is a given field a Word-processing type field N X,Y S Y=0 I +$P(^DD(TFILE,TFLD,0),U,2)>0 D . N SFILE S SFILE=+$P(^DD(TFILE,TFLD,0),U,2) . S Y=$S($P(^DD(SFILE,.01,0),U,2)="W":1,1:0) Q Y 2. The input transform for the TARGET FILE field (#.05) in the GMR REPORT TYPE file, which is a pointer to the File of Files, assures that only files which include the "GMRD" application group may be chosen for inclusion in the upload. This was done to assure that the site could not inadvertently choose an inappropriate target file (NOTE: the only file exported with this Application Group is the GMR REPORTS FILE (#128), where Discharge Summaries themselves are housed). The input transform looks like this: S DIC("S")="I $D(^DIC(+Y,""%"",""B"",""GMRD""))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X |
||||
| 316 | DBIA316-A | File | 1 | 1993/11/01 | APPROVED | Active | Private | 1. When a new file is configured for use with MTLU, the variable-pointer 'ENTRY' field is automatically updated in the LOCAL KEYWORD and LOCAL SHORTCUT files to reflect the new file. This must be handled via DIC/DIE calls with DIC/DIE being set to ^DD(file,.02,"V", It is fully compatible with the interactive way of creating variable pointer type fields. 2. MTLU uses the string maintained in ^DD("KWIC"). There is currently no way of retrieving this information without directly referencing this node. As stated there is currently no way of extracting data stored in the node except by direct global hit. *Amendment 5/11/94* Toolkit DBIA 316 has been amended to include the $order of ^DD in line QU+5^XTLKEFOP. This code identifies the variable pointer prefix associated with the selected lookup file and was inadvertently ommitted. S XTLKY=Y,XTLKPF=+$O(^DD(8984.2,.02,"V","B",+Y,"")) G:'XTLKPF KL S XTLKPF=$P(^DD(8984.2,.02,"V",XTLKPF,0),U,4),XTLKUT=1 |
||||
| 320 | DBIA320 | Other | 1 | 1993/11/23 | Retired | Private | An integration agreement is approved to use the VA FileMan undocumented variable DIWESUB. This variable will be set in the Enter/Edit option of all objects and sub-objects of the ADP Plan Manager Version 10 software. The variable will be used in conjunction the a VA FileMan call to EN^DIWE for users to edit both the Initiative Description and the Equipment Justification. When using the full screen editor to edit word processing fields, the entire screen is blanked, and could be potentially confusing to the user. In all cases the variable will be set immediately prior to the call to EN^DIWE, and will be killed immediately afterword. Following is a short sample of the code which is used to edit the Initiative Description. EDIT; S DIWEPSE=1 S DIC="^PRAPIN(PRASTN,""IN"",PRASIN,""ID""," S DWLW="75",DWPK="1" S DIWESUB="Description" D EN^DIWE K DIWESUB |
|||||
| 321 | MODIFY 'B' XREF OF 757.01 | File | 1 | 1993/12/01 | Expired | Private | 757.01 | The FM team grants the request of the Clinical Lexicon package to modify the "B" index of file 757.01 as follows: S ^GMP(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA)="" K ^GMP(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA) It is further agreed that the following tools will not be used with this file: DIFROM, COMPARE/MERGE and TRANSFER. These tools rely on an unmodified 'B' index to function properly. Using the modified 'B' index of file 757.01 along with any of the named tools may produce unexpected results. |
||||
| 327 | DBIA327 | File | 1 | 1994/01/11 | APPROVED | Active | Private | .401 | Laboratory V5.2 (only V5.2) is granted the following exemption: The laboratory is supplying a pre release 5.2 patch. The patch will allow the site to mimic the conversion process required for V5.2 install. As a part of the process a FileMan sort template is created of all providers the software was unable to repoint to VA(200. The creation of the sort template is done with a DIC call and a DR string. We are not aware of a method to load the actual data. Therefore, this function is hard coded. The exemption is only required for the one time conversion process. Listed below is the actual code involved. Please advise of any suggestion you feel will be of benefit. EXCEPT(LRFILE,LRD0) ;- LOGS EXCEPTIONS FROM THE CONVERSIONS OF DATA FROM 6 A ND 16 ; exceptions are put into a SORT template so the the site can ; then use fileman enter edit to correct problems found. ; N DIC,LRSORT,X,Y I '$D(^DIBT("B",LRFILE_"-EXCEPTIONS")) D ADD I '$D(LRSORT) S LRSORT=$O(^DIBT("B",LRFILE_"-EXCEPTIONS",0)) S ^DIBT(LRSORT,1,LRD0)="" Q ; ADD ; add a new sort template to be used for exception logging and editing N X,Y S DIC="^DIBT(",DIC(0)="L",DIC("DR")="2///^S X=""T"";4///^S X=$P(LR FILE," "-"",2);5///^S X=0;" S X=LRFILE_"-EXCEPTIONS" D FILE^DICN S LRSORT=+Y Q |
|||
| 329 | DBIA329-A | Routine | 1 | 1994/01/12 | APPROVED | Active | Private | DIP | ||||
| 345 | DBIA345-A | File | 1 | 1994/02/02 | APPROVED | Active | Private |
Read only access for the ^DD( Global Read ^DD(FN), where FN is a file number, to determine the existence of a file prior to initiating a look-up (GMPTA4). Read ^DD(757*,FLD in indexing routines to obtain the location (node/piece) of data in Clinical Lexicon files 757-757.3 prior to eXecuting Set/Kill logic (GMPTNDX2). |
||||
| 352 | DBIA352 | File | 1 | 1994/02/28 | APPROVED | Active | Private | PCE (PX) is granted permission to execute the DD nodes for completing cross-references in the 9000001 file from within cross-reference logic on the Social Security (.09) field in the Patient file. There is a Regular "B" cross-reference on the .01 field (NAME) of the PATIENT/IHS file (9000001). There is also a Regular "D" cross- reference on the .02 field of the 9000001.41 Health Record Number multiple. Since the fields in the 9000001 file are being populated from during the execution of the Patient File (2) PX09 cross- reference, the DD logic for setting these cross-references is being handled by executing the 9000001 and 9000001.41 DD nodes with the set and kill logic. Routine PXXDPT executes the set logic of the 'B' cross reference of file 9000001, (Patient/IHS File), field .01 (Name). It also executes the set and kill logic of the 'D' whole file cross reference of subfile 9000001.41, (Health Record Fac), field .02 (Health Record No.) In V21 of FileMan, the entry points in ^DIK that reindex cross references are reentrant. Thus, direct execution of set/kill logic will not be necessary. Also PCE's Debugging Utility does a Global Read in the form of '$D(^DD(2,.09,1,800)) to check that the cross reference to update the PATIENT/IHS file (#9000001) exists. |
||||
| 395 | DBIA395 | File | 1 | 1994/03/23 | APPROVED | Active | Private | VA FileMan grants this integration request. The following calls are allowed within the AMIE package. CHK+13^DVBAPLL S DIC="^DD(8984.1,.02,""V"",",DIC(0)="Z",D="P",X=VAR1 D IX^DIC CHK+19^DVBAPLL S DIC="^DD(8984.2,.02,""V"",",DIC(0)="Z",D="P",X=VAR1 D IX^DIC ADDV+1^DVBAPLL Calls using ^DIC and ^DIE to update the variable pointer field in the Local Keyword and Local Synonym file for use with MTLU. The ^DIE call is fully compatible with the interactive way of creating variable pointer type fields. |
||||
| 449 | DBIA449 | Other | 1 | 1994/04/12 | APPROVED | Active | Private | The CPT package currently has five table files which reside in the DIC global. These are as follows: o CPT CATEGORY (#81.1) data is in ^DIC(81.1, o CPT COPYRIGHT (#81.2) data is in ^DIC(81.2, o CPT MODIFIER (#81.3) data is in ^DIC(81.3, o CPT MODIFIER CATEGORY (#81.4) data is in ^DIC(81.4, o CPT SOURCE (#81.5) data is in ^DIC(81.5, |
||||
| 488 | DBIA488 | File | 1 | 1994/05/11 | APPROVED | Active | Private | 1. DLL^XTLKMGR: This procedure non-interactively removes an entry from file 8984.4 and the associated variable pointer in the DD of 8984.1 and 8984.2. Line DLL+7 $orders on the variable pointer node to set DA, then ^DIK is called to remove the entry. |
||||
| 508 | DBIA6-B | File | 1 | 1989/07/27 | APPROVED | Active | Private | |||||
| 509 | DBIA6-C | File | 1 | 2005/11/07 | Retired | Private | Fileman calls. |
|||||
| 510 | DISV | File | 1 | 1989/07/27 | APPROVED | Active | Controlled Subscription | Used to process 'space-bar return' on user input. |
2012/02/29 | |||
| 511 | DBIA6-D | File | 1 | 1989/07/27 | APPROVED | Active | Controlled Subscription |
^DIC("AC" - Screen lookup on files of a particular application group. |
||||
| 706 | DBIA229-B | Other | 1 | 1993/05/18 | APPROVED | Active | Private |
MailMan V7 has permission to make the following calls to FileMan: 2. MailMan has always used its text field such that non-integer nodes are not a problem to it. This is explicitly done for network mail headers, which are not expected to be in any way handled by FileMan. In this case the lines .001 through .999 are reserved for recording information passed by the network on message deliveries. 3. While editing the Message file users have a capability to 'transfer text' from other text processing fields. Currently they can reference the text fields of other messages that they either sent or are a recieient of and the responses to these messages. Other prospective files from which textual information may be extracted via this method include the Help Frame file. Security is kept for the privacy of each user by using the screen on the file during the look-up when transfering text from the Message file. |
||||
| 821 | DBIA299-B | File | 1 | 1993/10/25 | APPROVED | Active | Private | The PDX (V 1.5) application is granted read access to the DD and DIC globals to accomplish the following tasks: 1) Get global location for a file ^DIC(FILE,0,"GL") |
||||
| 830 | DBIA314-B | File | 1 | 1993/11/01 | APPROVED | Active | Private | To support the table-driven upload of transcribed text to various DHCP files, the Discharge Summary application has permission to access the Data Dictionary and File of Files in the following ways: 1. In order to allow the site to specify the target file, fixed-field header elements, and word-processing field for each report type, Discharge Summary version 1 will make several references to either the File of Files or ^DD(. These are ONLY done in setting up a ^DIC call (to look-up a given field in the target file), or in screening logic (e.g., to exclude the programmer at the site from choosing a non-Word-Processing field in the target file as the destination for the body of a report). Needless to say, NO SETs or KILLs are ever executed on any of FileMan's supporting data structures (i.e., ^DD( or ^DIC(). All hard-coded references to ^DIC( or ^DD( are made from within the following code: GMRDUPAR ; SLC/JER - Upload Parameter Edit ;4/23/93 14:53 ;;1.0V2;Discharge Summary;;Sep 02, 1993 MAIN ; Controls branching N DIC,DA,DIE,DLAYGO,DR,GMRDPRM0,GMRDPRM1,GMRDPRM3,GMRDUSRC,GMRD1ST,X,Y D:'$D(GMRDPRM0) SETPARM^GMRDLIBE W !,"First edit Division-wide upload parameters:",! S (DIC,DLAYGO)=128.99,DIC(0)="AEMQL",DIC("A")="Select DIVISION: " D ^DIC K DLAYGO Q:+Y'>0 S DA=+Y S DIE=128.99,DR="[GMRD UPLOAD PARAMETER EDIT]" D ^DIE D SETPARM^GMRDLIBE W !!,"Now edit the REPORT TYPE file:",! F D Q:+$G(Y)'>0 . N GMRDREP,GMRDX . S DIC="^GMR(128.1,",DIC(0)="AEMQZ",DIC("A")="Select REPORT TYPE: " . I $D(^DISV(DUZ,DIC)),'$D(GMRD1ST) S DIC("B")=$G(^DISV(DUZ,DIC)), GMRD1ST=1 . D ^DIC K DIC Q:+Y'>0 S DA=+Y,GMRDREP=Y,GMRDREP(0)=Y(0) . S DIE=128.1,DR="[GMRD UPLOAD PARAMETER EDIT]" . D ^DIE S Y=1 . I $D(^GMR(128.1,+DA,"HEAD"))>9!($D(^GMR(128.1,+DA,"ITEM"))>9) D . . W !!,"The header for the ",$P(GMRDREP,U,2)," Report type is now defined as:" . . I $P(GMRDPRM0,U,16)="D" D DHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . I $P(GMRDPRM0,U,16)="C" D CHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . W ! Q TXTFLD(TFILE,GMRDFLT) ; Get Text Field # from ^DD(Target file #, N DIC,X,Y S DIC="^DD("_TFILE_",",DIC(0)="AEMQZ",DIC("A")="Select TARGET TEXT FIELD : " S DIC("S")="I +$$ISWP^GMRDUPAR(TFILE,+Y)" I $D(GMRDFLT) S DIC("B")=GMRDFLT D ^DIC G:+Y'>0 TXTFLDX S Y=+Y_";"_$P($P(Y(0),U,4),";") TXTFLDX Q Y ISWP(TFILE,TFLD) ; Is a given field a Word-processing type field N X,Y S Y=0 I +$P(^DD(TFILE,TFLD,0),U,2)>0 D . N SFILE S SFILE=+$P(^DD(TFILE,TFLD,0),U,2) . S Y=$S($P(^DD(SFILE,.01,0),U,2)="W":1,1:0) Q Y 2. The input transform for the TARGET FILE field (#.05) in the GMR REPORT TYPE file, which is a pointer to the File of Files, assures that only files which include the "GMRD" application group may be chosen for inclusion in the upload. This was done to assure that the site could not inadvertently choose an inappropriate target file (NOTE: the only file exported with this Application Group is the GMR REPORTS FILE (#128), where Discharge Summaries themselves are housed). The input transform looks like this: S DIC("S")="I $D(^DIC(+Y,""%"",""B"",""GMRD""))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X |
||||
| 833 | DBIA316-B | Routine | 1 | 1993/11/01 | APPROVED | Active | Private | 3. The lookup routine, XTLKDICL, is often executed recursively by Fileman. under some conditions, it is not appropriate to proceed with the lookup and processing must pass back to DIC at the appropriate entry point. MTLU therefore needs support for the entry points, ASK^DIC and RTN^DIC. Some of the variables that are used by the ASK^DIC and RTN^DIC calls are: Variables: Used in: DO(2 EN2+3,EN2+5 DIC TS+1 DIC(0 XTLKDICL+3,EN1+2 DIE XTLKDICL+3 DIPGM(0 XTLKDICL+3,XTLKDICL+5 DO TS DO(2 TS,TS+1,TS+2 X XTLKDICL+4,EN2+1,EN2+3,EN2+5,TS+1,TS+4,TS+8,TS+9 Y EN2+1,TS,TS+8,TS+9 Label References: EN1 TS+9 EN2 XTLKDICL+5,TS+8 External References: ASK^DIC EN1+2 RTN^DIC XTLKDICL+3,EN2+3,EN2+5 The calls to RTN^DIC and ASK^DIC are granted for the exclusive use of the Kernel's Toolkit package. |
DIC | |||
| 840 | DBIA329-B | Routine | 1 | 1994/01/12 | APPROVED | Active | Private | DII | ||||
| 841 | DBIA329-C | File | 1 | 1994/01/12 | Retired | Private | DICRW+5^ESPFM, the reference to ^DIC(+Y,0,"GL") |
|||||
| 842 | DBIA329-D | File | 1 | 1994/01/12 | APPROVED | Active | Private | 1. Read only: ^DD(910.2,.01,0) - ESP POLICE REGISTRATION LOG File - Displays an identifier. 2. Read only: ^DD(910.7,IEN,0,U,R) - ESP SELECTABLES file - Displays the color field as an identifier. 3. ^DD(912,.01,1,2,1.4) - ESP OFFENSE REPORT file - Executes a trigger to stuff institution information. 4. Read only: ^DD(914,.03,0) - ESP VIOLATIONS file - Displays if courtesy or violation identifier. 5. ^DD("SITE" - IEN - INSTITIUTION file read only. 6. Read only: ^DD(915,.01,0) ESP OFFENSE CODES file - Displays Offense Code as an identifier. |
||||
| 853 | DBIA345-B | File | 1 | 1994/02/02 | Retired | Private |
Read only access for ^DIC(FN,0,"GL"), where FN is a file number, to verify the the value of DIC prior to initiating the look-up (GMPTA4). |
|||||
| 859 | DBIA351-C | File | 1 | 1994/02/28 | Retired | Controlled Subscription | ||||||
| 888 | MTLU setup | File | 1 | 1994/05/16 | APPROVED | Active | Private | 8984.1 | The Clinical Lexicon Utility needs to write to the DD of the Kernel Toolkit Multi-Term Look-up Utility (MTLU) during the Post-Init. |
|||
| 889 | MTLU setup | File | 1 | 1994/05/16 | APPROVED | Active | Private | 8984.2 | The Clinical Lexicon Utility needs to write to the DD of Kernel Toolkit Multi-Term Look-up Utility (MTLU) during the Post-Init. |
|||
| 903 | DBIA903 | File | 1 | 2003/07/08 | Retired | Private | Inpatient Medications version 5.0 accesses the zero node of fields in ^DD(42, ^DD(50, ^DD(50.3, ^DD(52.6, ^DD(53.1, ^DD(55, ^DD(59, and ^DD(101, |
|||||
| 912 | DBIA912 | File | 1 | 1994/07/21 | Retired | Private | ^DIC("AC" - Screen lookup on files for the Lab application group. ^DIC("AC","LR" |
|||||
| 916 | DBIA916 | File | 1 | 1994/07/25 | APPROVED | Active | Controlled Subscription | The current packages subscribing to this IA are expected to migrate to use DID calls. NO NEW FUTURE SUBSCRIBERS WILL BE ADDED. |
||||
| 917 | DBIA917 | File | 1 | 1994/07/26 | Retired | Private | NOTE: This DBIA has been combined into DBIA #510 and has been retired. Laboratory V 5.2 uses ^DISV(DUZ,"LRACC") and ^DISV(DUZ,"LRAN") to store items. An example is in routine LRACC at line LRACC+4: S:$L(X)>2 ^DISV(DUZ,"LRACC")=X S:X=" " X=$S($D(^DISV(DUZ,"LRACC")): ^("LRACC"),1:"?") Lab needs an agreement for read/write access to ^DISV(DUZ,"LRACC") and ^DISV(DUZ,"LRAN") |
|||||
| 937 | SEARCH TEMPLATE RESULTS | File | 1 | 1994/08/12 | APPROVED | Active | Supported |
^DIBT(SORT_TEMPLATE#,1,IEN)="" The 1 node indicates that the IEN list was created one of two ways: 1) The user was in FileMan INQUIRE mode, selected a number of records, and saved the list in a template. 2) The user ran the FileMan SEARCH, either through the interactive FileMan menu, or through the programmer entry point EN^DIS. In this case, the IEN list is the record numbers that met the search criteria. IEN - is the internal entry number of a record in the file indicated by the 4th piece of the 0 node of the template, ^DIBT(SORT_TEMPLATE#,0). Read, Write, Delete access allowed. |
||||
| 975 | DBIA975 | File | 1 | 1994/08/29 | APPROVED | Active | Private | 1.5 | This integration agreement permits LetterMan to install and reference the WORD LIST file #1.5 stored in global ^DIW(1.5,. The WORD LIST file is used by the LetterMan spell checker. |
|||
| 987 | DBIA987 | File | 1 | 1994/09/26 | APPROVED | Active | Private | The Laboratory package Version 5.2 requests agreement from the VA FileMan package to modify the B cross-references in the LABORATORY TEST FILE #60 and the WKLD CODE FILE #64 to be greater than 30 characters. The first 30 characters are quite frequently the same for more than one test or workload code. ^DD(60,.01,1,1,1)=S ^LAB(60,"B",$E(X,1,40),DA)="" ^DD(64,.01,1,1,1)=S ^LAM("B",$E(X,1,60),DA)="" ^DD(64.061,.01,1,1,1)=^LAB(64.061,"B",$E(X,1,50),DA) |
||||
| 999 | DBIA999 | File | 1 | 1994/09/02 | APPROVED | Active | Controlled Subscription | Read only access for the ^DD( Global. $O(^DD(FN,"GL",subscript,piece,0)) to get the field #. Read ^DD(FN,FLD,0), Custodial files only, where FN is a file # and FLD is a field #, to obtain the field name, the set of codes, or the input transform. |
||||
| 1016 | FIELD EDITOR - EN~DIR0() | Routine | 1 | 1994/10/17 | APPROVED | Active | Private | Kernel needs to use the screen-oriented field editor for the character based GUI emulation module. |
DIR0 | |||
| 1017 | CALLS TO FILEMAN FOR KIDS | Routine | 1 | 1994/10/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call the FileMan DIFROMSU Server routine. This call is used during the build and installation of a package. |
DIFROMSU | |||
| 1052 | DBIA1052-A | Routine | 1 | 1994/11/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. |
DIFROMS | |||
| 1053 | DBIA1052-B | Routine | 1 | 1994/11/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. |
DIFROMSO | |||
| 1054 | DBIA1052-C | Routine | 1 | 1994/11/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. |
DIFROMSI | |||
| 1055 | DBIA1052-D | Routine | 1 | 1994/11/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. The DIEZ routine is used to recompile input templates in non-interactive mode. |
DIEZ | |||
| 1056 | DBIA1052-E | Routine | 1 | 1994/11/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. The DIKZ routine is used to recompile a file's cross-references in non-interactive mode. |
DIKZ | |||
| 1057 | DBIA1052-F | Routine | 1 | 1994/11/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. The DIPZ routine is used to recompile print templates in non-interactive mode. |
DIPZ | |||
| 1058 | DBIA1052-G | Routine | 1 | 1994/11/07 | APPROVED | Active | Private | Kernel Installation and Distribution System needs to call two undocumented ScreenMan entry points from the 7.5 node of .01 fields of multiples in the Build file. These entry points are used to inform ScreenMan of subrecords that have been added or deleted during the execution of the 7.5 node. |
DDSUTL | |||
| 1059 | FILE SECURITY CODE ACCESS | File | 1 | 1994/11/08 | APPROVED | Active | Private | 1 | This integration agreement will allow the MAS package to release a patch to allow sites to review and update file security codes without having to install inits of all files. Due to problems reported in several recent NOIS mesages, we've had cause to review and update our recommended levels of access. We feel this is the best way to get the sites up-to-date. An informal message and a draft copy of the routines has already been submitted to FileMan development for review and concurrence. Our instructions will be that this is a one time only run. No options will be created for this patch. The patch is DG*5.3*49 and is currently under development. We are requesting the ability to view and edit the following nodes in the DIC global: ^DIC(filenum,0,"WR") file write access ^DIC(filenum,0,"DD") file DD access ^DIC(filenum,0,"RD") file read access ^DIC(filenum,0,"DEL") file delete access ^DIC(filenum,0,"LAYGO") file LAYGO access |
|||
| 1062 | 1062 | Other | 1 | 1995/01/12 | APPROVED | Active | Private | Kernel Toolkit needs this agreement with Fileman to be able to use the variable D0 in DD definitions. Here are some examples of the use of variable D0. 15,99991 LOOKUP1 ; COMPUTED MUMPS CODE: S X="`"_+^VA(15,D0,0) ALGORITHM: S X="`"_+^VA(15,D0,0) DESCRIPTION: This field is used to navigate to the file pointed to by RECORD1. TECHNICAL DESCR: This field is used to navigate to the file pointed to by RECORD1. 15,99992 LOOKUP2 ; COMPUTED MUMPS CODE: S X="`"_+$P(^VA(15,D0,0),U,2) ALGORITHM: S X="`"_+$P(^VA(15,D0,0),U,2) DESCRIPTION: This field is used to navigate to the file pointed to by RECORD2. TECHNICAL DESCR: This field is used to navigate to the file pointed to by RECORD2. 15,99993 LOOKUP3 ; COMPUTED MUMPS CODE: S X="`"_D0 ALGORITHM: S X="`"_D0 LAST EDITED: AUG 08, 1989 DESCRIPTION: This computed field provides navigational capability to any file that points to this file and has a DINUM relationship. TECHNICAL DESCR: This computed field provides navigational capability to any file that points to this file and has a DINUM relationship. |
||||
| 1091 | DBIA316-C | Other | 1 | 1995/01/05 | APPROVED | Active | Private | Multi Term Lookup (a component of TOOLKIT) requests the ability to read the "GL" node of ^DIC in order to retrieve a global root. This reference can be found in the routines XTLKEFOP, XTLKKWL, XTLKMGR, XTLKPRT and in the MUMPS X-REF of file 8984.3: CROSS-REFERENCE: 8984.3^AC^MUMPS 1)= I $D(^XT(8984.3,DA,0)),$P(^(0),U,2)'="" S J L=$P(^(0),U,2),JL=$P(^DIC(JL,0,"GL"),U,2),^XT(8 984.3,"AC",JL,$E(X,1,30),DA)="" K JL 2)= I $D(^XT(8984.3,DA,0)),$P(^(0),U,2)'="" S J L=$P(^(0),U,2),JL=$P(^DIC(JL,0,"GL"),U,2) K ^XT (8984.3,"AC",JL,$E(X,1,30),DA),JL Associates the synonym with the global root of the lookup file. ***** Amendment 1/23/95 ***** The above request should be modified to include both Multi-Term Lookup and the Duplicate Resolution modules of Toolkit. The 'GL' node is referenced for the same purpose in file 15.1, field .01, "AGL" x-reference. |
||||
| 1110 | 1110 | File | 1 | 2003/06/10 | Retired | Private | 15 | Kernel Toolkit needs this agreement with FileMan to be able to clean up some "IX" nodes in the data dictionary of the DUPLICATE RECORD (#15) file. The "IX" nodes which are killed during the post-init contain the names of the X-refs. which do not exist. |
||||
| 1111 | 1111 | File | 1 | 1995/01/10 | APPROVED | Active | Private | Kernel Toolkit files have a number of fields whose screens, input transforms, and executable helps contain code that directly references ^DD. |
||||
| 1126 | Index and the DD global. | File | 1 | 1995/02/01 | APPROVED | Active | Private | |||||
| 1127 | Lookup on B x-ref in globals DIE, DIBT, DIPT | File | 1 | 1995/02/03 | Retired | Controlled Subscription | ||||||
| 1128 | Killing global DOPT | Other | 1 | 1995/02/03 | APPROVED | Active | Private | This integration agreement allows the LetterMan pre-init to remove the old version namespace entries in the global ^DOPT. The globals killed are: ^DOPT("WPSE") ^DOPT("WPSE1") ^DOPT("WPSE2") ^DOPT("WPSE3") ^DOPT("WPSE4") |
||||
| 1160 | ONCOLOGY FILE NAME CLEAN-UP | File | 1 | 1995/03/14 | APPROVED | Active | Private | 1 | Clean-up of old file names. |
|||
| 1167 | DBIA1167 | Other | 1 | 1995/04/14 | APPROVED | Active | Private | When sites run Mental Health V. 5.01 inits and they have the DSM3 ^DIC(627, file that has the 2nd and 3rd pieces flipped the install gracefully aborts and tells the user that the DSM3 file is missing conversion node(s)!! The DSM conversion cannot continue and the correct versions of this file should have been installed during the Mental Health V. 5.01 initialization process. Permission from the FILEMAN community to do the following: 1. Hard KILL the node ^DIC(627,310.1) at END+1^YSD4PRE. 2. Reverse the values of the 2nd and third pieces on line Q+36^YSINI035. All routine changes will be sent out in patch YS*5.01*6. |
YSINI02Q | |||
| 1168 | FILE 124.2 B CROSS-REFERENCE CHANGE | File | 1 | 1995/03/21 | APPROVED | Active | Private | 0 | Since the .01 field of the TG Term (124.6) file is 2-60 characters in length, and there is no need to add a second regular cross-reference, the Text Generator would request an exemption to modify the "B" cross- reference so that it uses 60 characters instead of 30. |
|||
| 1195 | INPATIENT MEDICATIONS XREF CLEAN UP | File | 1 | 2003/06/10 | Retired | Private | 55 | Inpatient Medications 4.5 exported the AUDS cross reference on the START DATE/TIME(#10) field of the UNIT DOSE(#55.06) multiple of the PHARMACY PATIENT(#55) file. This cross reference is not referenced by the Inpatient Medications software, and since this field is "hard set", the cross reference is never set. This causes problems with locally created sort templates on this field when running VA FILEMAN V21. To elminate this problem, a routine will be exported in PSJ*4.5*12 that will identify and delete this cross reference from the Data Dictionary. The routine to be used for this is listed below: PSJUTL2 ;B'ham ISC/MLM - REMOVE AUDS XREF FROM 55.06,10 ; 14 Apr 95 / 9:59AM ;;4.5; Inpatient Medications ;**12**;7 Oct 94 ; EN ; Entry point from programmer mode to delete the AUDS xref. ; W "This routine was exported as part of PSJ*4.5*12 to delete the AUDS",! W "cross reference from the PHARMACY PATIENT(#55) file.",!! N X,DIR S DIR(0)="Y",DIR("B")="NO",DIR("A")="Delete this cross reference?" S DIR("?")="Enter ""YES"" to continue with this process or ""NO"" to abort." D ^DIR Q:$D(DIRUT) F X=0:0 S X=$O(^DD(55.06,10,1,X)) Q:'X D .K:$G(^DD(55.06,10,1,X,0))="55^AUDS" ^DD(55.06,10,1,X) K ^DD(55,0,"IX","AUDS",55.06,10) W !!,"Done." Q Inpatient Medications requests a PRIVATE DBIA with VA FILEMAN to directly K ^DD(55.06,10,1,X), where X is the IEN of the AUDS cross reference. |
||||
| 1200 | INPATIENT MEDICATIONS XREF CLEAN UP | File | 1 | 2003/06/10 | Retired | Private | 55 | Inpatient Medications 4.5 exported the AUDS cross reference on the START DATE/TIME(#10) field of the UNIT DOSE(#55.06) multiple of the PHARMACY PATIENT(#55) file. This cross reference is not referenced by the Inpatient Medications software, and since this field is "hard set", the cross reference is never set. This causes problems with locally created sort templates on this field when running VA FILEMAN V21. To elminate this problem, a routine will be exported in PSJ*4.5*12 that will identify and delete this cross reference from the Data Dictionary. The routine to be used for this is listed below: PSJUTL2 ;B'ham ISC/MLM - REMOVE AUDS XREF FROM 55.06,10 ; 14 Apr 95 / 9:59AM ;;4.5; Inpatient Medications ;**12**;7 Oct 94 ; EN ; Entry point from programmer mode to delete the AUDS xref. ; W "This routine was exported as part of PSJ*4.5*12 to delete the AUDS",! W "cross reference from the PHARMACY PATIENT(#55) file.",!! N X,DIR S DIR(0)="Y",DIR("B")="NO",DIR("A")="Delete this cross reference?" S DIR("?")="Enter ""YES"" to continue with this process or ""NO"" to abort." D ^DIR Q:$D(DIRUT) F X=0:0 S X=$O(^DD(55.06,10,1,X)) Q:'X D .K:$G(^DD(55.06,10,1,X,0))="55^AUDS" ^DD(55.06,10,1,X) K ^DD(55,0,"IX","AUDS",55.06,10) W !!,"Done." Q Inpatient Medications requests a PRIVATE DBIA with VA FILEMAN to directly K ^DD(55.06,0,"IX","AUDS",55.06,10). |
||||
| 1206 | DBIA1206 | File | 1 | 1995/04/28 | APPROVED | Active | Private | During the installation of IFCAP v. 5.0 (namespace PRC) and IFCAP's Generic Inventory Package v. 5.0 (namespace PRCP), direct MUMPS kills of erroneous ^DD nodes need to be done in the Pre-Init After User Commit and the Post-Init routines. The specific nodes are listed below: 1. IFCAP (namespace PRC): a. Field descriptions (node 21) for files and sub-files in the range from 410 to 443.99. The kills are done in the DESCRIP^PRC5INS1 module, which is called from PRC5A, the Pre-Init After User Commit routine. The clean up is necessary as the new description may have fewer lines than the previous description, and, with double question mark help, the left-over lines may appear. b. Erroneous Computed Field nodes for fields currently defined as Free-Text: ^DD(420.01,2,9.01), ^DD(420.01,2,9.1), ^DD(420.01,2,9.2) ^DD(420.01,3,9.01), ^DD(420.01,3,9.1), ^DD(420.01,3,9.2) The kills are done in routine PRC5A, the Pre-Init After User Commit routine. c. Erroneous "IX" node: ^DD(442.8,0,"IX","AE",442.8,.01) The kill is done in routine PRC5A. d. Erroneous "NM" node: ^DD(420.11,0,"NM","SUBACCOUNT") The kill is done in routine PRC5A. 2. Generic Inventory Package of IFCAP (namespace PRCP): a. Field descriptions (node 21) from files and sub-files in the range from 445 to 447. The kills are done in the DESCRIP^PRC5INS1 module, which is called from PRCP5PRE, the Pre-Init After User Commit routine. b. Erroneous "ID" node: ^DD(445.121,0,"ID","WRITE") The kill is done in routine PRCP5POS, the Post-Init routine. c. Erroneous "NM" node: ^DD(445.121,0,"NM","MEMBER OF SET/PACK") The kill is done in routine PRCP5POS. |
||||
| 1237 | DBIA1237 | File | 1 | 1995/05/31 | APPROVED | Active | Private | The pre-init routines for ROES V2.0 change several file names, clean up leftover DD nodes, and an obsolete cross-reference. These changes were suggested by the verifier to maintain consistency throughout the system. |NOWRAP| 1. The screen on the 'BATTERY TYPE FURNISHED' field is deleted with a Kill command. GLOBAL REFERENCE: ^DD(791810.0101,.02,12) ^DD(791810.0101,.02,12.1) 2. The old name of field 791810.0101 is cleaned up in ORDER^RMPFPOST. FileMan creates a duplicate NM node when a subfile name changes. GLOBAL REFERENCE: ^DD(791810.0101,0,"NM","TRANSACTION") 3. The 'AD' cross-reference on the .01 field of file number 791810 is killed with a direct kill in EXIT^RMPFPRE routines. The following is a capture of the code: EXIT F X=0:0 S X=$O(^DD(791810,.01,1,X)) Q:'X D .K:$G(^DD(791810,.01,1,X,0))="791810^AD^MUMPS" ^DD(791810,.01,1,X) K ^DD(791810,0,"IX","AD",791810,.01) GLOBAL REFERENCE: ^DD(791810,.01,X,0) ^DD(791810,0,"IX","AD",791810,.01) 4. The file names of files 791810, 791810.1, 791810.2, 791812 are changed using DIE like the following: S DIE=1,DA=701810,DR=".01////STATION ORDER" D ^DIE |
||||
| 1245 | ENGINEERING XREF CLEAN UP | File | 1 | 1995/07/20 | APPROVED | Active | Private | 6914 | Engineering exported a series of cross references in the Equipment Inv (#6914) file to support the upload of equipment data to the ISMS system. These mumps cross references were never activated because the ISMS system was not brought on line. These cross references are now obsolete and should be removed from the Equipment Inv file. The following cross references will be deleted with patch EN*7*25 using code in a PRE-INIT AFTER USER COMMIT routine. CROSS-REFERENCE FIELD # FIELD NAME --------------- ------- ---------------------- AI1 1 MANUFACTURER AI2 2 PARENT SYSTEM AI27 4 MODEL AI3 5 SERIAL # AI0 7 TYPE OF ENTRY AI5 10 VENDOR POINTER AI6 11 PURCHASE ORDER # AI7 12 ACQUISITION VALUE AI8 12.5 LEASE COST AI9 13 ACQUISITION DATE AI10 13.5 ACQUISITION SOURCE AI11 15 LIFE EXPECTANCY AI12 16 REPLACEMENT DATE AI13 18 CATEGORY STOCK NUMBER AI26 19 CMR AI14 20 USE STATUS AI15 20.1 OWNERSHIP AI16 20.5 TURN-IN DATE AI17 22 DISPOSITION DATE AI18 23 PHYSICAL INVENTORY DATE AI19 31 DISPOSITION METHOD AI20 32 DISPOSITION VALUE AI21 33 CONTROLLED ITEM? AI22 34 CAPITALIZED? AI23 36 COST CENTER AI24 38 GENERAL LEDGER ACCOUNT AI25 39 YALD CODE AI28 51 REPLACING (ENTRY NUMBER) Code similar to the following will be used in the pre-init to delete the cross references from the data dictionary. ENXGIPR ;WIRMFO/SAB-PRE INIT ;7/21/95 ;;7.0;ENGINEERING;**25**;Aug 17, 1993 N ENFX Q:'$D(DIFROM) W !,"Performing Pre-Init...",! XREF ; delete any obsolete ISMS cross references W !,"Deleting obsolete xrefs from Equipment Inv (#6914) file..." F ENFX="1^AI1","2^AI2","4^AI27","5^AI3","7^AI0","10^AI5", "11^AI6","12^AI 7","12.5^AI8","13^AI9","13.5^AI10" D DELXREF ($P(ENFX,U),$P(ENFX,U,2)) F ENFX="15^AI11","16^AI12","18^AI13","19^AI26","20^AI14" ,"20.1^AI15","20.5^AI16","22^AI17" D DELXREF($P(ENFX,U),$P(ENFX,U,2)) F ENFX="23^AI18","31^AI19","32^AI20","33^AI21","34^AI22", "36^AI23","38^AI24","39^AI25","51^AI28" D DELXREF($P(ENFX,U),$P(ENFX,U,2)) XREFEND ; end of delete obsolete ISMS cross references EXIT ; W !,"Completed Pre-Init",! Q DELXREF(ENF,ENX) ; for field number ENF delete xref ENX N ENI Q:'$D(^DD(6914,0,"IX",ENX,6914,ENF)) ; already deleted S ENI=0 F S ENI=$O(^DD(6914,ENF,1,ENI)) Q:'ENI D .K:$G(^DD(6914,ENF,1,ENI,0))=("6914^"_ENX_"^MUMPS") ^DD(6914,ENF,1,ENI) K ^DD(6914,0,"IX",ENX,6914,ENF) K:'$O(^DD(6914,ENF,1,0)) ^DD(6914,"IX",ENF) ; no xrefs left on field W !," ",ENX," xref deleted from field ",ENF Q The following DD nodes may be deleted ^DD(6914,field number,1,ien for xref) ^DD(6914,0,"IX",xref,6914,field number) ^DD(6914,"IX",field number) This will only be done if there are no cross references left on the field. (i.e. '$O(^DD(6914,field number,1,0)) is true). |
|||
| 1258 | VARIABLES IN PROGRAMMER HOOKS | File | 1 | 1995/08/08 | Withdrawn | Supported | The following DBIA describes the variables that are available and what values these variables are set to within programmer hooks. (define programmer hook here) |
|||||
| 1353 | DBIA1353 | File | 1 | 1995/09/21 | APPROVED | Active | Private | .402 | This DBIA documents a Radiology/Nuclear Medicine package look-up on FileMan's Edit template file. The look-up is done within an IRM option so that IRM can select one, many, or all Radiology/ Nuclear Med compiled templates for re-compiling. The look-up must be done through a Radiology program which calls DIC in order to provide the "one-many-all" look-up functionality. |
|||
| 1355 | DBIA1355 | File | 1 | 1995/09/21 | APPROVED | Active | Private | .4 | This DBIA documents a Radiology/Nuclear Medicine package look-up on FileMan's Print template file. The look-up is done within an IRM option so that IRM can select one, many, or all Radiology/Nuclear Med compiled tempaltes for re-compiling. the look-up must be done through a Radiology program which calls DIC in order to provide the "one-many-all" look-up functionality. |
|||
| 1370 | DDBRZIS/DDBDMSG | Other | 1 | 1995/10/03 | APPROVED | Active | Controlled Subscription | Progress Notes will check $G(DDBRZIS). If so, the variable DDBDMSG will be set equal to "Progress Notes". This will enable "Progress Notes" to display as the title if the BROWSER device has been selected. |
||||
| 1412 | DD GLOBAL | File | 1 | 1997/03/05 | APPROVED | Active | Controlled Subscription | 0 | The Nursing, Vitals/Measurements, and Text Generator packages have been granted permission to access the DD global as defined in this DBIA. |
|||
| 1450 | DELETE X-REF ON .01 FIELD OF FILE 120.8 | File | 1 | 1995/12/13 | APPROVED | Active | Private | 0 | With the release of Adverse Reaction Tracking v4.0, we would like to directly kill the "ANKA01" cross-reference on the .01 field of File 120.8. In our installation process, we will do the following: |
|||
| 1515 | Set File Security for ART files | File | 1 | 1996/03/12 | APPROVED | Active | Private | The Adverse Reaction Tracking (ART) package uses the KIDS utility to export the package software. ART exports the file level security codes for its data dictionaries. Currently, KIDS will not change the file level security codes on the target system if they already exist. This DBIA allows ART to check the file level security nodes on the package's data dictionaries and change the target system's file level security to match the ones being exported. They are: ^DIC(120.8,0,"AUDIT") = @ ^DIC(120.8,0,"DD") = @ ^DIC(120.8,0,"DEL") = @ ^DIC(120.8,0,"LAYGO") = @ ^DIC(120.8,0,"WR") = @ ^DIC(120.82,0,"AUDIT") = @ ^DIC(120.82,0,"DD") = @ ^DIC(120.82,0,"DEL") = @ ^DIC(120.83,0,"AUDIT") = @ ^DIC(120.83,0,"DD") = @ ^DIC(120.83,0,"DEL") = @ ^DIC(120.84,0,"AUDIT") = @ ^DIC(120.84,0,"DD") = @ ^DIC(120.84,0,"DEL") = @ ^DIC(120.84,0,"LAYGO") = @ ^DIC(120.84,0,"RD") = @ ^DIC(120.84,0,"WR") = @ ^DIC(120.85,0,"AUDIT") = @ ^DIC(120.85,0,"DD") = @ ^DIC(120.85,0,"DEL") = @ ^DIC(120.85,0,"LAYGO") = @ ^DIC(120.85,0,"WR") = @ ^DIC(120.86,0,"AUDIT") = @ ^DIC(120.86,0,"DD") = @ ^DIC(120.86,0,"DEL") = @ ^DIC(120.86,0,"LAYGO") = @ ^DIC(120.86,0,"RD") = @ ^DIC(120.86,0,"WR") = @ ^DIC(120.87,0,"AUDIT") = @ ^DIC(120.87,0,"DD") = @ ^DIC(120.87,0,"DEL") = @ ^DIC(120.87,0,"LAYGO") = @ ^DIC(120.87,0,"WR") = @ |
||||
| 1533 | DBIA1533 | File | 1 | 1996/05/07 | APPROVED | Active | Private | 725 | Event Capture requests to modify the "B" cross reference for the EC NATIONAL PROCEDURE file (#725) to be 63 characters rather than the standard 30 characters. As part of this agreement Event Capture will provide the following: 1. Add a description to the "B" cross reference indicating that it was modified and that ^DIC lookups into this file with DIC(0)["X" will not find exact matches greater than 30 characters in length. 2. Create a post-install routine that kills the "B" index of the file and then calls ENALL^DIK with DIK(1)=".01^B" to rebuild it. |
|||
| 1535 | 'DEL' node modification | File | 1 | 1996/05/17 | APPROVED | Active | Private | 0 | The health summary package needs permission to change the "DEL" node in the DD structure for file 142.1. This will be done with the SET command and will be done with patch 7. Here is the code to reset the "DEL" node: S ^DD(142.1,.01,"DEL",1,0)="I $S(+$G(DUZ(2))'>0:1,DUZ(2)=5000:0,(DA'<100 001)&(DA'>9999999):0,1:1) N GMZ S GMZ=$S(+$G(DUZ(2)):""ONLY Components Created a t your site can be deleted"",1:""DUZ(2) MUST equal your DIVISION"") D EN^DDIOL(GMZ)" S ^DD(142.1,.01,"DEL",2,0)="I '$D(GMCMP) D EN^DDIOL(""You may only delet e COMPONENTS using the GMTS IRM/ADPAC COMP EDIT option."","""",""!!"")" |
|||
| 1540 | Setting ID entries | File | 1 | 1996/06/13 | APPROVED | Active | Private | 0 | Since KIDS cannot presently support changing the ID entries for a file without also shipping all fields in the file, IFCAP wants to send a post-INIT to remove the old ID nodes and set a new ID node. This will change the ID display to alow 5 different entries (vendors) to be seen on a 24 line display without any entries scrolling off the top. This change will be used in patch PRC*5*69 only. |
|||
| 1543 | CHECK FOR DI*21*17 | Routine | 1 | 1996/06/18 | APPROVED | Active | Private | The Scheduling Developers would like the following one-time integration agreement with the FileMan Developers: For PCMM (SD*5.3*41), as part of the installation environment checker, SCMCENV, we check the second line of the following routine using $TEXT: ^DICA This is the part of VA FileMan's Updater engine. Patch #17 of Version 21.0 was specifically listed as necessary for proper functioning of the RPC Broker (which PCMM depends on). As such, we require that either: o The package version is 22 or higher o The package version is 21 and DICA has patch #17 indicated in its second line. |
DICA | |||
| 1547 | DD GLOBAL READ | File | 1 | 1996/06/18 | Withdrawn | Private | The Scheduling Developers would like the following integration agreement with the FileMan Developers: Read access to the DD global in the following fashion: IF $P($G(^DD(SCFILE,SCFLD,0)),U,4)[";0" SCFILE = Filenumber of concern SCFLD = Fieldnumber of concern This code is used to determine if the field is a word-processing field. When the PCMM software is updated to use VA FileMan's components, this DBIA will no longer be needed. Per previous discussions with FileMan Component developers, this DBIA is needed because of the poor response time that resulted from use of supported calls. |
|||||
| 1553 | DBIA1553 | Other | 1 | 1996/06/24 | APPROVED | Active | Private | This request is to allow Integrated Billing to hard-set an identifier node in the Procedures (#304) sub-file of the Bill/Claims (#399) file. File #399 is a very large file which we would prefer not to distribute just to update the modifier of one of its sub-files. The post-init to patch IB*2*62 will set this identifier. The following code will be executed: S ^DD(399.0304,0,"ID","WRITE")="D DISPID^IBCSC4D" |
||||
| 1556 | SCHEDULING REPORTS Field Points to File #1 | File | 1 | 1996/07/01 | APPROVED | Active | Private | 1 | The Scheduling Developers would like the following integration agreement with the FileMan Developers: With PCMM (SD*5.3*41), in the SCHEDULING REPORT File (#404.92), in the FILES multiple (#40), there is a FILE field (#.01) which points to the FILE file. This field contains the name of the file from which selections are made. |
|||
| 1568 | Set File Security for Medicine Files | File | 1 | 1996/07/30 | APPROVED | Active | Private | 1 | The Medicine package uses the KIDS utility to export the package software. Medicine exports file level security codes for its data dictionaries. Currently, KIDS will not change the file level security codes on the target system if they already exist. This DBIA allows Medicine to check the file level security nodes on the package's data dictionaries and change the target system's file level security to match the ones being exported. The nodes changed are: ^DIC(File,0,"DD")="@" and ^DIC(File,0,"AUDIT")="@" Where 'File' has the following values: 690 690.1 690.2 690.5 690.97 690.99 691 691.1 691.5 691.6 691.7 691.8 691.9 692 693 693.2 693.3 693.5 693.6 694 694.1 694.5 694.8 695 695.1 695.3 695.4 695.5 695.6 695.8 695.9 696 696.1 696.2 696.3 696.4 696.5 696.7 696.9 697 697.1 697.2 697.3 697.5 698 698.1 698.2 698.3 698.4 698.6 698.9 699 699.48 699.5 699.55 699.57 699.6 699.7 699.81 699.82 699.83 699.84 699.85 699.86 699.88 700 700.1 700.2 700.5 701 |
|||
| 1595 | FILE SECURITY | File | 1 | 1996/08/15 | APPROVED | Active | Private | 1 | Intake/Output V3 is asking for a one-time exemption to be able to read/write to the ^DIC(file,0,access) global where 126 <= file <= 126.95 and access=(DD,RD,WR,LAYGO,DEL). |
|||
| 1617 | Scheduling Reads DD(2,0,'ID',... | File | 1 | 1996/08/29 | Withdrawn | Private | 0 | |||||
| 1618 | DIV | Routine | 1 | 1996/09/13 | APPROVED | Active | Private | Lab is requesting a database agreement to call the DIV routine at line tag VER for the workload data Lab archiving verify option. The option is Verify Files for Archiving. This option allows the user to select either the WKLD DATA (64.1) or LAB MONTHLY WORKLOADS (67.9) file and choose to verify data in either the whole file or entries selected by the Select Entries for Archiving option. Routine name:LRARVER line: ALL D VER^DIV(LRART) where LRART = file # 64.1 or 67.9 line: VWD+1 D VER^DIV(64.11,.LRWIN) where LRWIN is an array of records to verify line: VLMW+1 D VER^DIV(67.911,.LRWIN) where LRWIN is an array of records to verify |
DIV | |||
| 1619 | Set ID nodes in post-install patch routine | File | 1 | 1996/09/24 | APPROVED | Active | Private | 357 | KIDS cannot support adding new Identifiers with a partial DD update, AICS wants to send a post-install routine to add a new Identifier and update existing data-file entries for the ENCOUNTER FORM file (357). The following ^DD and ^IBE(357 nodes will be set in a post-install routine: ^DD(357.02,0,"ID",.02)=W " ",@("$P($P($C(59)_$S($D(^DD(357.02,.02,0)): $P(^(0),U,3),1:0)_$E("_DIC_"Y,0),0),$C(59)_$P(^(0),U,2)_"":"",2), $C(59),1)") $P(^DD(357,2,0),"^",2)="357.02I" $P(^IBE(357,D0,2,0),"^",2)="357.02I" |
|||
| 1622 | DBIA1622 | File | 1 | 1996/10/18 | APPROVED | Active | Private | 3.8 | Request DBIA to allow MailMan to K ^DD(3.8,0,"ID",5.1) as a post-install routine on a patch. There currently is no other way to remove a field as an identifier. |
|||
| 1912 | DBIA1912 | Routine | 1 | 1997/01/28 | APPROVED | Active | Controlled Subscription | The MAS Developers would like a one-time integration agreement with the FileMan Developers: For patch DG*5.3*111, as part of the installation environment checker, DG53111E, we check the second line of the following routine using $TEXT: DIFROMSS The check is to ensure that the package version is 21 and DIFROMSS has patch #15 indicated in its second line. This environment checker routine is necessary because the prefix, "DI", is not unique to the VA FILEMAN package in the PACKAGE file (#9.4). An earlier package named FILEMAN shares the same Prefix, and as a result, the "Required Build" function in the KIDS Build does not function properly when referencing a FileMan patch. |
DIFROMSS | |||
| 1941 | SETTING DD NODES | File | 1 | 1997/02/21 | APPROVED | Active | Private | 1 | This integration agreement is for a one time use for AICS v3.0 to set the following three DD nodes. These nodes point to the Expressions file (757.01) which has changed global locations in Lexicon Utility v2.0 from ^GMP to ^LEX. Approximately half of VAMC's have installed Lexicon Utility v2.0. The setting of these nodes will set the Data Dictionaries to the correct global location for the version of Lexicon Utility. I $D(^LEX) D .S ^DD(357.3,2.02,0)="CLINICAL LEXICON ENTRY^P757.01'^LEX(757.01,^2;2^Q" .S ^DD(358.3,2.02,0)="CLINICAL LEXICON ENTRY^P757.01'^LEX(757.01,^2;2^Q" .S ^DD(357.951,2.02,0)="CLINICAL LEXICON^P757.01'^LEX(757.01,^2;2^Q" .D MES^XPDUTL(">>> AICS Data Dictionaries updated to use Lexicon Utility version 2.0") E D MES^XPDUTL(">>> AICS Data Dictionaries updated to use Clinical Lexicon Utility version 1.0") |
|||
| 1957 | File Security Codes | File | 1 | 1997/03/10 | APPROVED | Active | Private | 1 | The Gen. Med. Rec. - I/O (Intake and Output), Gen. Med. Red. - Vitals (Vitals/Measurements), Nursing Service and Text Generator packages have permission to set the security nodes (i.e., "DD", "RD", "DEL", "LAYGO", and "WR") in FILE 1 for those files within the package's number range. For example: S ^DIC(210,0,"DD")="@" Package Number Range ------- ------------ Intake & Output 126-126.95 Vitals/Measurments 120.5-120.57 Nursing Service 210-219.7 Text Generator 124-124.3 With the next release of each package, the installation process will allow the site to change its file security codes to match the codes as they appear in the documentation. The site can answer YES to change their file security codes to match the package documentation or NO to leave them as is. |
|||
| 1986 | EXECUTE DD NODES OF File 391.71 Cross-references | File | 1 | 1997/05/07 | APPROVED | Active | Controlled Subscription | 391.71 |
A cross-reference on a field in the Patient file #2 creates an entry in ADT/HL7 PIVOT file #391.71 and/or sets the cross-references in file #391 by executing the ^DD cross-reference nodes. ^DD(2,.01,1,991,0) = 2^AVAFC01^MUMPS ^DD(2,.02,1,991,0) = 2^AVAFC02^MUMPS ^DD(2,.03,1,991,0) = 2^AVAFC03^MUMPS ^DD(2,.05,1,991,0) = 2^AVAFC05^MUMPS ^DD(2,.08,1,991,0) = 2^AVAFC08^MUMPS ^DD(2,.09,1,991,0) = 2^AVAFC09^MUMPS ^DD(2,.111,1,991,0) = 2^AVAFC111^MUMPS ^DD(2,.1112,1,991,0) = 2^AVAFC1112^MUMPS ^DD(2,.112,1,991,0) = 2^AVAFC112^MUMPS ^DD(2,.113,1,991,0) = 2^AVAFC113^MUMPS ^DD(2,.114,1,991,0) = 2^AVAFC114^MUMPS ^DD(2,.115,1,991,0) = 2^AVAFC115^MUMPS ^DD(2,.117,1,991,0) = 2^AVAFC117^MUMPS ^DD(2,.131,1,991,0) = 2^AVAFC131^MUMPS ^DD(2,.132,1,991,0) = 2^AVAFC132^MUMPS ^DD(2,.211,1,991,0) = 2^AVAFC211^MUMPS ^DD(2,.219,1,991,0) = 2^AVAFC219^MUMPS ^DD(2,.2403,1,991,0) = 2^AVAFC2403^MUMPS ^DD(2,.301,1,991,0) = 2^AVAFC301^MUMPS ^DD(2,.302,1,991,0) = 2^AVAFC302^MUMPS ^DD(2,.31115,1,991,0) = 2^AVAFC31115^MUMPS ^DD(2,.323,1,991,0) = 2^AVAFC323^MUMPS ^DD(2,.351,1,991,0) = 2^AVAFC351^MUMPS ^DD(2,391,1,991,0) = 2^AVAFC391^MUMPS ^DD(2,1901,1,991,0) = 2^AVAFC1901^MUMPS Global ^DD(2,1901,1,991 DD(2,1901,1,991 ^DD(2,1901,1,991,0) = 2^AVAFC1901^MUMPS ^DD(2,1901,1,991,1) = D:($T(AVAFC^VAFCDD01)'="") AVAFC^VAFCDD01(DA) ^DD(2,1901,1,991,2) = D:($T(AVAFC^VAFCDD01)'="") AVAFC^VAFCDD01(DA) ^DD(391.71,.06,1,1,0) = 391.71^AC^MUMPS ^DD(391.71,.08,1,1,0) = 391.71^AXMIT2^MUMPS ^DD(391.71,.06,0) = TRANSMITTED^S^1:NEED TO TRANSMIT;^0;6^Q ^DD(391.71,.06,1,0) = ^.1 ^DD(391.71,.06,1,1,0) = 391.71^AC^MUMPS ^DD(391.71,.06,1,1,1) = S:+X ^VAT(391.71,"AC",$E(X,1,30),DA)="" ^DD(391.71,.06,1,1,2) = K ^VAT(391.71,"AC",$E(X,1,30),DA) ^DD(391.71,.08,0) = REQUIRES TRANSMISSION^S^0:NO;1:YES;^0;8^Q ^DD(391.71,.08,.1) = Requires Transmission ^DD(391.71,.08,1,0) = ^.1 ^DD(391.71,.08,1,1,0) = 391.71^AXMIT2^MUMPS ^DD(391.71,.08,1,1,1) = Q:(($G(VAFCA08))!('X)) N A S A=$P(^VAT(391.71,DA,0),"^",4) S:(+A) ^VAT(391.71,"AXMIT",A,DA)="" ^DD(391.71,.08,1,1,2) = N A S A=$P(^VAT(391.71,DA,0),"^",4) K:(+A) ^VAT(391.71,"AXMIT",A,DA) |
|||
| 2021 | FileMan Replace/With Editor Call | Routine | 1 | 1997/05/16 | APPROVED | Active | Private | This IA permits Capacity Management utilities to call the FileMan Replace/With Editor entry point at RW^DIR2. |
DIR2 | |||
| 2022 | RECOMPILATION OF INPUT TEMPLATES | File | 1 | 1997/05/19 | APPROVED | Active | Controlled Subscription | .402 | When installing a patch that includes changes to field definitions in a data dictionary, KIDS does not recompile the compiled input templates. This integration agreement covers recompilation of input templates. Recompilation of input templates may involve the following steps: (1) Traverse the "AF" cross-reference of the ^DIE global (file #.402) to obtain a list of compiled input templates for the affected fields. The structure of this cross-reference is ^DIE("AF",file,field,template)="" Subfields would be treated like fields of their respective subfiles, i.e. ^DIE("AF",subfile,subfield,template)="". (2) For each template that is being recompiled, access ^DIE(template,"ROU") to determine the compiled routine. (3) Invoke EN^DIEZ to recompile that input template. |
|||
| 2023 | DBIA2023 | Other | 1 | 1997/05/19 | APPROVED | Active | Private | PCE Patient Care Encounter and Visit Tracking is requesting permission to look at the following nodes of the Data Dictionary. 1) ^DD(FILE,0,"PT",FILE,FIELD) ;Pointer Nodes 2) ^DD(FILE,FIELD,1,SUB,0) ;Zero node of the Cross-reference Multiple 3) ^DD(FILE,FIELD,1,SUB,1) ;Set logic of the Cross-reference This will allow us to check for any FILE and FIELD that is pointing to the VISIT file #9000010 to make sure that a BROKEN pointer will not be created if an entry in the VISIT file is deleted by way of PCE OR VISIT TRACKING. It will also allow us to write reports to show who is pointing to a particular VISIT at times when it is necessary to Debug the Visit File Data Base. |
||||
| 2032 | DELETE C XREF | File | 1 | 1997/06/10 | APPROVED | Active | Controlled Subscription | 3.9 | Subj: Request for DBIA [#24183795] 09 Jun 97 11:11 10 Lines For MailMan patch XM*7.1*40, Request DBIA to delete "C" xref on field 1 (LAST RESPONSE READ) of RECIPIENT multiple of MESSAGE file. The following code to be included in a pre-init routine: K ^DD(3.91,1,1) K ^DD(3.91,0,"IX","C") K ^DD(3.91,"IX",1) |
|||
| 2036 | DD GLOBAL | File | 1 | 1997/06/06 | APPROVED | Active | Private | 0 | The Visit Tracking package have been granted permission to access the DD global as defined in this DBIA. |
|||
| 2050 | Database Server (DBS) API: DIALOG Utilities | Routine | 1 | 1997/07/02 | APPROVED | Active | Supported | DIALOG file utilities. BLD: DIALOG Extractor $$EZBLD: DIALOG Extractor (Single Line) MSG: Output Generator |
DIALOG | |||
| 2051 | Database Server API: Lookup Utilities | Routine | 1 | 1997/07/02 | APPROVED | Active | Supported | Lookup utilities. FIND: Finder $$FIND1: Finder (Single Record) LIST: Lister |
DIC | |||
| 2052 | Database Server API: Data Dictionary Utilities | Routine | 1 | 1997/07/02 | APPROVED | Active | Supported | Data dictionary utilities. FIELD: DD Field Retriever FIELDLST: DD Field List Retriever FILE: DD File Retriever FILELST: DD File List Retriever $$GET1: Attribute Retriever |
DID | |||
| 2053 | Data Base Server API: Editing Utilities | Routine | 1 | 1997/07/02 | APPROVED | Active | Supported | Editing Utilities CHK: Data Checker FILE: Filer HELP: Helper UPDATE: Updater VAL: Validator WP: Word Processing Filer $$KEYVAL^DIE( ): Key Validator VALS^DIE( ): Fields Validator |
DIE | |||
| 2054 | Data Base Server API: Misc. Library Functions | Routine | 1 | 1997/07/02 | APPROVED | Active | Supported | Various libaray functions. CLEAN: Array and Variable Clean-up $$CREF: Root Converter (Open to Closed Format) DA: DA( ) Creator DT: Date Converter FDA: FDA Loader $$IENS: IENS Creator $$OREF: Root Converter (Closed to Open Format) $$VALUE1: FDA Value Retriever (Single) VALUES: FDA Values Retriever |
DILF | |||
| 2055 | Data Base Server API: Misc. Data Libaray Functions | Routine | 1 | 1997/07/02 | APPROVED | Active | Supported | Data libaray functions. $$EXTERNAL: Converter to External $$FLDNUM: Field Number Retriever PRD: Package Revision Data Initializer RECALL: Recall Record Number $$ROOT: File Root Resolver $$VFIELD: Field Verifier $$VFILE: File Verifier |
DILFD | |||
| 2056 | Data Base Server API: Data Retriever Utilities | Routine | 1 | 1997/07/02 | APPROVED | Active | Supported | Data retriever utilities. $$GET1: Single Data Retriever GETS: Multiple Data Retriever |
DIQ | |||
| 2081 | DBIA2081 | Other | 1 | 1997/09/30 | APPROVED | Active | Private | Pharmacy Data Management requests an intergration agreement with the VA FileMan package. PDM requests to do a one-time hard kill of four triggers which are no longer valid in DRUG file 50. These triggers will be killed in a post install routine in Pharmacy Data Management version 1.0. The fields affected in DRUG file 50 are: Field 12 ORDER UNIT Field 13 PRICE PER ORDER UNIT Field 15 DISPENSE UNITS PER ORDER UNIT Field 16 PRICE PER DISPENSE UNIT In addition: Field 23 PACKAGE SIZE (input transform) Field 24 PACKAGE TYPE (input transform) Field 8 WARNING LABEL (overflow of input transform code) The KILL logic looks as follows: K ^DD(50,12,1,535000),^DD(50,203),^DD(50,13,1,535000),^DD(50,15,1,535000), ^DD(50,16,1,1),^DD(50,"TRB",16) K ^DD(50,0,"IX","AE",50,202),^DD(50,0,"IX","IV",50.03,.01) K ^DD(50,0,"IX","IV1",50,204),^DD(50,0,"IX","IV2",50,201.1),^DD(50,0,"PT",50.03,. 02) K ^DD(50,0,"IX","AV1",50,200),^DD(50,0,"IX","AD",50,201),^DD(50,0,"IX","AF",50,20 1.3),^DD(50,0,"IX","AV2",50,201),K ^DD(50,23,2),^DD(50,23,2.1),^DD(50,24,2),^DD(50,24,2.1),^DD(50,8,9.2) |
||||
| 2097 | DBIA2097 | File | 1 | 1997/08/29 | APPROVED | Active | Private | 1.1 |
CIRN needs to display the last date edited for a patient. CIRN recommends that sites turn on auditing for demographic fields. To get the last date edited, if auditing is turned on, CIRN checks the $P(^DIA(2,0),U,3)+1 for the last entry and then $O(^DIA(2,"B",DFN,LAST ENTRY),-1) to find the most recent edit, $P(^DIA(2,IEN,0),U,2). CIRN requests direct read access to these nodes. |
|||
| 2098 | DIQUIET TO SUPPRESS WRITES | Other | 1 | 1997/09/02 | APPROVED | Active | Controlled Subscription | 1. DESCRIPTION OF USE OF DIQUIET IN FILEMAN HISTORY OF DIQUIET: The purpose for creating DIQUIET was mostly that as we were creating the data-base server calls, we sometimes needed to call into Classic FileMan, and we absolutely didn't want FileMan to talk. DIQUIET was a variable that would let us know within those classic calls that we were being called from a DBS call, so we shouldn't talk. Therefore, at the start of almost all the DBS calls, we set DIQUIET=1. DIQUIET was also used as a flag in EN^DDIIOL, which is embedded in Xecutable code in the DD, to assure that text is placed in ^TMP instead of being Written when DBS calls are involved. SETTING DIQUIET WITHIN FILEMAN CODE: DIQUIET is set to 1 at the start of the following published calls: Finder FIND^DIC Finder (Single Record) $$FIND1^DIC Lister LIST^DIC DD Field Retriever FIELD^DID DD Field List Retriever FIELDLST^DID DD File Retriever FILE^DID DD File List Retriever FILELIST^DID Attribute Retriever $$GET1^DID Data Checker CHK^DIE Filer FILE^DIE Helper HELP^DIE Updater UPDATE^DIE Validator VAL^DIE Word-Processing Filer WP^DIE Single Data Retriever $$GET1^DIQ Data Retriever GETS^DIQ In addition, there are a few places that Classic FileMan sets DIQUIET for the same reason. Import Tool (DDMP, DDMPU) because the Import tool is designed to be silent like the DBS calls. DIED and DIEZ1 (classic DIE call to edit data) sets DIQUIET if the user is stuffing data in a SET OF CODES field, because it makes a call to ^DIR and does not want the Reader to talk. DIEZ, DIKZ and DIPZ (template and x-ref compilation) appear to have silent entry points (all labeled EN2) that set DIQUIET. I believe that these were created by Rick, I don't think they're documented. Perhaps KIDS uses them, I need to discuss this with him. DIP (the PRINT routine) sets DIQUIET if it is not already set, and if all the information that DIP normally prompts the user for has been sent (I.E., file and fields to print, sort criteria, device, etc.), or if the print job is queued. That was to avoid some places where FileMan was writing error messages. HONORING DIQUIET TO SUPPRESS WRITES: Mostly we made changes to classic FileMan as we needed to, in places where we were calling it from the new DBS calls and wanted it to be silent. The places are: DDIOL (The loader), where DIQUIET tells the routine to load the text that is passed into an array rather than writing it. That's why we were able to tell people that any writes that they have in their DDs should call ^DDIOL rather than just write. %DT (date validation routine) to keep the date from echoing back. DT^DICRW (routine that sets up required FileMan variables). Was writing a line-feed. DIE3 (enter/edit) Does not write "Searching for a..." when doing a lookup on a file pointed-to by a variable pointer, and does not ask OK when a pointed-to entry is found, even if the DD has been set up that way. DIP The changes to the print are described above, and were not done for the DBS calls, as we don't call the print from within any of them. DIR1 The Reader doesn't write a message when processing sets of codes if DIQUIET is set. This was required by DIE when stuffing a SET OF CODES field, as I described above. 2. REASON RPC BROKER NEEDS TO SET DIQUIET: Setting of DIQUIET variable, which is used within the VA FileMan package to suppress WRITEs from FileMan routines and DDs, to 1. Variable being set by RPC Broker when it is certain that no direct user-interaction is appropriate (client/server environment). The only FileMan code that the Broker does directly that requires DIQUIET to be set is DT^DICRW (a linefeed is suppressed). However, since the Broker performs the code written in RPCs, having DIQUIET set protects the code in the RPCs from inadvertently Writing because of a call to a FileMan routine or the Xecution of a DD node. |
||||
| 2159 | DBIA2159 | File | 1 | 1997/09/29 | APPROVED | Active | Private | PDM requests permission to look at the ^DD global for following files: Global route File # File -------------------------------------------------------------------- ^DD(50 50 DRUG File 50 DRUG MUMPS x-ref (AUDAP) Field .01 GENERIC NAME - ^DD(50,51,0). ^DD("50",".01","1","3","0")="50^AUDAP^MUMPS" ^DD("50",".01","1","3","1")="I '$D(PSGINITF) S ^PSDRUG("AUDAP")=$S($D(^PS(59.7,1 ,20)):$P(^(20),"^"),1:"")" ^DD("50",".01","1","3","1.1")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$P(Y(1),U,1) S XMB(1)=X" ^DD("50",".01","1","3","1.2")="S X=Y(0) S Y(2)=$C(59)_$S($D(^DD(50,51,0)):$P(^(0 ),U,3),1:""),Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$P($P(Y(2),$C(59)_$P(Y(1), U,9)_":",2),$C(59),1) S XMB(2)=X" ^DD("50",".01","1","3","1.3")="S X=Y(0) S Y(1)=$S($DPSDRUG(D0,0)):^(0),1:"") S X=$S('$D(^PS(50.5,+$P(Y(1),U,2),0)):"",1:$P(^(0),U,1)) S XMB(3)=X" ^DD("50",".01","1","3","1.4")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X1),U,10) S XMB(4)=X" ^DD("50",".01","1","3","2")="Q" ^DD("50",".01","1","3","2.2")="S X=Y(0) S Y(2)=$C(59)_$S($D(^DD(50,51,0)):$P(^(0 ),U,3),1:""),Y(1)=$S($D(^PSDRUG(D0,0)):^(0),P(Y(2),$C(59)_$P(Y(1), U,9)_":",2),$C(59),1) S XMB(2)=X" ^DD("50",".01","1","3","2.3")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$S('$D(^PS(50.5,+$P(Y(1),U,2),0)):"",(0),U,1)) S XMB(3)=X" ^DD("50",".01","1","3","2.4")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$P(Y(1),U,10) S XMB(4)=X" ^DD("50",".01","1","3","3")="Used by the Unit npatient Medications package s." **************** ^DD(51.1 51.1 ADMINISTRATION SCHEDULE File 52.6 IV ADDITIVES INPUT TRANSFORM Field 5 ADMINISTRATION TIMES - ^DD(51.1,1,0) ^DD("52.6","5","0")="ADMINISTRATION TIMES^FX^^0;6^X $P(^DD(51.1,1,0),"^",5,999) Q" ^DD("52.6","5","3")="Answer must be 2-119 characters in length." ^DD("52.6","5","20","0")="^.3LA^1^1" ^DD("52.6","5","20","1","0")="PSJI" ^DD("52.6","5","21","0")="^^3^3^2910412^^^^" ^DD("52.6","5","21","1","0")=" Enter the admin. times that this drug is given m ost frequently. This" ^DD("52.6","5","21","2","0")="field will be shown as default for the 'ADMIN. TIM ES: ' prompt during" ^DD("52.6","5","21","3","0")="ordry of IVPB's." ^DD("52.6","5","DT")="2910412" **************** ^DD(52.6 52.6 IV ADDITIVES File 52.6 IV ADDITIVES INPUT TRANSFORM Field 13 CONCENTRATION - ^DD(52.6,2,0) ^DD("52.6","13","0")="CONCENTRATION^FX^^0;10^K:X'=+X!(X>99999)!(X<0)!(X?.E1"."3 N .N) X I $D(X) S PSIVX=X,Y=^DD(52.6,2,0),X=$P(^PS(52.6,D0,0),"^",3) D ENC^PSIV D EN^DDIOL(" "_X_"/ML","","?0") S X=PSIVX_" "_X_"/ML" K PSIVX" ^DD("52.6","13","3")="Type a number between 0 and 99999 (no more than 2 decimal digits, and no trailing 0's are allowed)." **************** ^DD(50.4 50.4 DRUG ELECTROLYTES File 52.6 IV ADDITIVES INPUT TRANSFORM Subfile 52.62 Field 1 CONCENTRATION - ^DD(50.4,1,0) ^DD("52.62","1","0")="CONCENTRATION^RFX^^0;2^K:+X'=X!(X>99999)!(X<0)!(X?.E1"."5 N .N) X I $D(X) S PSIVX=X,Y=^DD(50.4,1,0),X=$P(^PS(50.4,+^PS(52.6,DA(1),2,DA,0),0) ,"^",2) D ENC^PSIV S X=PSIVX_" "_X K PSIVX D STRTH^PSSDDUT2" ^DD("52.62","1","3")="Type a number between 0 and 99999." **************** ^DD(59.723 59.7 PHARMACY SYSTEM File 59.7 PHARMACY SYSTEM INPUT TRANSFORM Subfile 59.723 Field .01 TO SERVICE - ^DD(59.723,.01,0) PSYS2 D EN^DDIOL("(""From"" service is "_$S('$D(PS(59.7,D0,23,D1,0)):"UNKNOWN" ,$P(^(0),"^")]"":$P(^PS(";"_$P(^DD(59.723,.01,0),"^",3),";"_$P(^PS(59.7,D0,23,D 1 ,0),"^")_":",2),";"),1:"UNKNOWN")_")") Q **************** ^DD(55.01 55 PHARMACY PATIENT File 52.6 IV ADDITIVES INPUT TRANSFORM Field 4 USUAL IV SCHEDULE - ^DD(55.01,.09,0) ^DD("52.61","4","0")="USUAL IV SCHEDULE^FX^^0;5^X $P(^DD(55.01,.09,0),"^",5,999) " ^DD("52.61","4","3")="Answer must be 1-22 characters in length." ^DD("52.61","4","20","0")="^.3LA^1^1" ^DD("52.61","4","20","1","0")="PSJI" ^DD("52.61","4","21","0")="^^2^2^2910305^^^" ^DD("52.61","4","21","1","0")=" Enter the schedule that should be 'stuffed' int o the schedule field" ^DD("52.61","4","21","2","0")="of the IV order using this quick code." ^DD("52.61","4","DT")="2860223" **************** ^DD(50.4 50.4 DRUG ELECTROLYTES File 52.7 IV SOLUTIONS INPUT TRANSFORM Subfile 52.702 Field 1 CONCENTRATION - ^DD(50.4,1,0) ^DD("52.702","1","0")="CONCENTRATION^RFX^^0;2^K:+X'=X!(X>99999)!(X<0)!(X?.E1"." 5 N.N) X I $D(X) S PSIVX=X,Y=^DD(50.4,1,0),X=$P(^PS(50.4,+^PS(52.7,DA(1),2,DA,0),0 ),"^",2) D ENC^PSIV S X=PSIVX_" "_X K PSIVX D STRTH^PSSDDUT2" ^DD("52.702","1","3")="Type a number between 0 and 99999." |
||||
| 2253 | DBIA2253 | File | 1 | 1997/12/30 | APPROVED | Active | Private | 55.06 | Inpatient Medications requests permission to call routine ^DIC with the variable DIC defined as "^DD(55.06," and DIC(0)="QEM" or DIC(0)="QE". This will perform a lookup on the field names of a particular file and return the needed variables. This is used in our routines to allow a user to up-arrow jump to another field during the editing of an order. Example: The user is editing an order and enters "^STA". The ^DIC lookup is performed, finds the START DATE field, and returns the field's internal entry number. That number is then used to go to the appropriate code to edit that field. |
DIC | ||
| 2255 | DBIA2255 | File | 1 | 1997/12/30 | APPROVED | Active | Private | 0 | Inpatient Medications requests direct read access to pharmacy files node ^DD(file #,field #,12). We are reading from this node to return the POINTER SCREEN description. |
|||
| 2256 | DBIA2256 | File | 1 | 1997/12/31 | APPROVED | Active | Private | 53.1 | Inpatient Medications requests permission to call routine ^DIC with the variable DIC defined as "^DD(53.1," and DIC(0)="QEM". This will perform a lookup on the field names of a particular file and return the needed variables. This is used in our routines to allow a user to up-arrow jump to another field during the editing of an order. Example: The user is editing an order and enters "^STA". The ^DIC lookup is performed, finds the START DATE field, and returns the field's internal entry number. That number is then used to go to the appropriate code to edit that field. |
|||
| 2298 | DBIA2298 | File | 1 | 1998/03/05 | APPROVED | Active | Private | HL7 Patch 14 brings in updates to reference files for version 2.3 of the standard. These files contain identifiers that have changed with the latest version. KIDS does not install the new data correctly unless these identifiers are removed before installing the patch. Permission is requested to execute the following code as pre and post install routines in patch 14. HLP14PRE ;SFIRMFO/JC - HL7 PATCH 14 PRE-INIT ;03/05/98 11:44 ;;1.6;HEALTH LEVEL SEVEN;**14**;Oct 13, 1995 PRE ; K ^DD(779.001,0,"ID") K ^DD(771.2,0,"ID") Q POST ; S ^DD(779.001,0,"ID",2)="W "_""""_" "_""""_",$P(^(0),U,2)" S ^DD(771.2,0,"ID",2)="W "_""""_" "_""""_",$P(^(0),U,2)" |
||||
| 2340 | DIU(0) | Routine | 1 | 1998/03/05 | APPROVED | Active | Controlled Subscription | Specific to preventing DIK from running cross-references which include a test for the value of DIU(0) not being present. |
DIK | |||
| 2361 | KILLING NODES IN DD FOR RATED DISABILITIES MULTIPLE | Other | 1 | 1998/04/16 | APPROVED | Active | Private | The Registration Package requests permission to kill 'extra' nodes descendant from ^DD(2.04,0,"NM") in the post-install for patch DG*5.3*147, leaving only ^DD(2.04,0,"NM","RATED DISABILITIES (VA)"). Justification ============= We are currently in testing for patch DG*5.3*147, which is National Enrollment. In part, this software consists of the transmission of patient data to local sites and its upload. We discovered that UPDATE^DIE was failing, resulting in the loss of the patient's rated disabilities. The cause was prior corruption of the DD for the 2.04 multiple (Rated Disabilities (VA)). There are extra nodes at the "NM" cross-reference. Deleting the nodes solved the problem. |
||||
| 2373 | DIST(1.2 REFERENCE IN OE/RR | File | 1 | 1998/04/29 | APPROVED | Active | Private | 1.2 | The Order Entry/Results Reporting module would like permission to reference the ALTERNATE EDITOR file. OE/RR uses the FM reader almost exclusively in the order dialog process. When taking actions such as copy and renew orders, it is necessary to allow comments (a word processing field) to be carried over. OE/RR would like to use the ALTERNATE EDITOR file to determine if the user is using the line editor. If not, it will display the text in the field prior to asking them if they want to edit it. Without this reference, always displaying the text in the field would cause those with the line editor to see it 2x. |
|||
| 2374 | TOOLKIT NEEDS NAME | File | 1 | 1998/04/29 | APPROVED | Active | Controlled Subscription | 1 | The Parameter Tools component of Toolkit is a generic tool to allow setting parameters at various levels (system, package, etc.). In order to achieve this goal, it is necessary to make a direct global read to DIC to determine file name. |
|||
| 2375 | TOOLKIT NEEDS TO ACCESS VARIABLE PTR DEF | File | 1 | 1998/04/29 | APPROVED | Active | Private | The Parameter Tools component of Toolkit allows setting of parameters at various levels. This necessitates a file structure with a variable pointer definition to point to the files which are allowed to be used through the Parameter Tools component. To ensure that no other files are pointed to, a check is done on the DD's "V" multiple, "B" cross-reference, to deterine whether an entry is in the variable pointer definitition. |
||||
| 2377 | DIR('V') usage in parameter tools | Other | 1 | 1998/04/30 | APPROVED | Active | Private | The parameter tools component of toolkit would like permission to use DIR("V") to ensure a silent interaction with the reader when doing data validation checks. |
||||
| 2386 | PARAMETER TOOLS POINTS TO FILE 1 | File | 1 | 1998/05/09 | APPROVED | Active | Private | 1 | The Parameter Tools portion of Toolkit requests approval to point to the file of files (file #1). Parameter Tools uses this pointer to determine allowable files for setting up parameters. |
|||
| 2540 | BROWSER SWITCHING | Routine | 1 | 1998/09/21 | APPROVED | Active | Private | The purpose of this DBIA is to provide a temporary method for switching between 'documents' without the user having to mentally resolve pointers between records in two different files. The needed functionality is currently planned by the VA Fileman developers to released in a patch. When that patch is released, the HL7 developers will modify the Transmission Log code to use the released functionality. See IA# 3594. |
DDBR2 | |||
| 2543 | DBIA2543 | File | 1 | 1998/10/07 | APPROVED | Active | Private | 1 | ||||
| 2592 | TRAVERSE DD FOR FILE CONVERSION | File | 1 | 1998/09/30 | APPROVED | Active | Private | The post-install routine in the Registration patch DG*5.3*172 is looping through the "PT" node in both the MARITAL STATUS file (#11) and RELIGION file (#13) to convert the non-standard entries into standard entries. The non-standard entries are deleted after the conversion. However, the conversion cannot convert entries within a subfile, so the patch identifies the subfile within the "PT" node and traverses back through the "UP" nodes looking at the subfile zero nodes to report the subfile NAMES that could not be converted. This information is placed in a mail message which is reported back to the installer of patch DG*5.3*172. |
||||
| 2602 | READING AUDIT FILE | File | 1 | 1998/10/02 | APPROVED | Active | Controlled Subscription | 1.1 | The NDF Management System uses entries in the AUDIT file (#1.1) to track changes made to files involved with NDF and to send these changes to VAMCs using KIDS. To this end, the NDF Management System requests permission to do direct global reads of entries in File #1.1 |
2016/02/05 | ||
| 2607 | Browser API | Routine | 1 | 1998/10/14 | APPROVED | Active | Supported | The Browser displays ASCII text on a terminal which supports a scroll region. |
DDBR | |||
| 2608 | Browser API | Routine | 1 | 1998/10/14 | APPROVED | Active | Supported | This function call returns a 1 or 0 (true or false) to determine if the CRT being used can support a scroll region and reverse index. |
DDBRT | |||
| 2609 | Browser API | Routine | 1 | 1998/10/14 | APPROVED | Active | Supported | Browser device handler functions. |
DDBRZIS | |||
| 2610 | ScreenMan API: Form Utilities | Routine | 1 | 1998/10/14 | APPROVED | Active | Supported | $$GET() - This extrinsic function retrieves data from a form-only field or a computed field. PUT() - This procedure stuffs data into a form-only field. |
DDSVALF | |||
| 2631 | DBIA2631 | File | 1 | 1998/10/27 | APPROVED | Active | Controlled Subscription | Knowledge of file and subfile hierarchies is sometimes required. The required information can be obtained from ^DD(D0,0,"UP"). |
||||
| 2642 | Set Rad/Nuc Med data dictionary 'ID','WRITE' node. | File | 1 | 1998/11/12 | APPROVED | Active | Private | 0 | Radiology/Nuclear Medicine intends to modify the following data dictionary attribute: before: ^DD(71,0,"ID","WRITE") = W ?54,$$PRCCPT^RADD1() after: ^DD(71,0,"ID","WRITE") = D EN^DDIOL($$PRCCPT^RADD1(),"","?54") The intention of this correction is to eliminate the WRITE command from the data dictionary. To execute this action, I must hard set the data dictionary node in a post-init. At present, FileMan does not have a generic tool to export specific file wide data dictionary attributes. I do not wish to carry over the entire data dictionary for the Rad/Nuc Med Procedures file. |
|||
| 2645 | Classic FileMan API: Sort Template Compliation | Routine | 1 | 1998/11/17 | Withdrawn | Supported | This entry point marks a sort template compiled or uncompiled. |
DIOZ | ||||
| 2648 | Import Tool API | Routine | 1 | 1998/11/19 | APPROVED | Active | Supported | This procedure imports data from ASCII host files into VA FileMan file entries. Format FILE^DDMP([FILE],[[.]FIELDS],[.CONTROL],.SOURCE,[.]FORMAT) |
DDMP | |||
| 2649 | Classic FileMan API: Max. Routine Size | Routine | 1 | 1998/11/19 | APPROVED | Active | Supported | This argumentless function returns the maximum routine size that should be used when compiling cross references, print templates, or input templates. |
DILF | |||
| 2658 | REMOVAL OF ID NODE | Other | 1 | 1998/12/10 | APPROVED | Active | Private | Deletion of "ID" node for identifier which is no longer required. |
||||
| 2661 | DIR Special variable | Other | 1 | 1998/12/11 | APPROVED | Active | Controlled Subscription | The Alert processor makes use of a special input parameter to Fileman DIR. This is done in XQALERT1, it makes a call with DIR(0)="LV^..." to get user input validated. |
||||
| 2695 | DD AUDIT ACCESS | File | 1 | 1999/01/04 | APPROVED | Active | Private | 2 | CIRN PD would like a DBIA for its direct global read of ^DD(2,"AUDIT". This direct global read is used to identify all of the top level PATIENT (#2) file fields that are currently marked for auditing. We realize this will not get subfile fields within the PATIENT (#2) and we are willing to disregard those fields in our report until an API is provided for all audited fields within the PATIENT (#2) file. |
|||
| 2696 | RECOMPILATION OF PRINT TEMPLATES | File | 1 | 1999/01/06 | APPROVED | Active | Controlled Subscription | .4 | When installing a patch that includes changes to field definitions in a data dictionary, KIDS does not recompile the compiled print templates. Recompilation of print templates may involve the following steps: (1) Traverse the "AF" cross-reference of the ^DIPT global (file #.4) to obtain a list of compiled print templates for the affected fields. The structure of this cross-reference is ^DIPT("AF",file,field,template)="" Subfields would be treated like fields of their respective subfiles, i.e. ^DIPT("AF",subfile,subfield,template)="". (2) For each template that is being recompiled, access ^DIPT(template,"ROU") to determine the compiled routine. (3) Invoke EN^DIPZ to recompile that print template. |
2012/04/03 | ||
| 2744 | CIRN Access to DPT File | File | 1 | 1999/01/29 | Withdrawn | Private | 2 | CIRN needs a read access to the DPT 0 node file (Patient File) in order to build the "B" cross reference to the DGCN(391.98 file. CIRN gets the first piece of the DPT 0 node field to build the "B" cross reference. CROSS-REFEREENCE: 391.98^B^MUMPS 1)= N A S A=$P($G(^DPT(X,0)),U,1) I A]"" S ^DGCN(391.98, "B",A,DA)="" 2)= N A S A=$P($G(^DPT(X,0)),U,1) I A]"" K ^DGCN(391.98, "B",A,DA)="" This is the external to help in the sorting. A precedent was set with DBIA 321 with the caveat: It is further agreed that the following tools will not be used with this file: KIDS, COMPARE/MERGE and TRANSFER. These tools rely on an unmodified "B" index to function properly. Using the modified "B" index of file 757.01 along with any of the named tools may produce unexpected results. |
||||
| 2752 | OUTPATIENT PHARMACY: DD UPDATES | Other | 1 | 1999/03/15 | APPROVED | Active | Private | Outpatient Pharmacy V. 7.0 has permission to kill the following ^DD entries in patch PSO*7*25. This is a one time agreement. ^DD(55,0,"P") ^DD(55,0,"PS") |
||||
| 2807 | OE/RR sets ID WRITE node | File | 1 | 1999/04/25 | APPROVED | Active | Controlled Subscription | 1 | This DBIA documents hard setting of the 'ID','WRITE' node for a multiple in the ORDER DIALOG file. We would like to make this a generic request, however, for OE/RR to set 'ID','WRITE' nodes as apporpriate. The only alternative to hard setting this node is to send the entire DD of a file out. Within a patch, sending the whole file can create an unnecessarily large distribution which can cause us to move to an HFS file rather than exporting the build via the National Patch Module. The specific instance that generated this DBIA sends out post-installation code in routine ORY46 as follows: ; -- Reset ID WRITE node for Items S ^DD(101.412,0,"ID","WRITE")="N OR0,ORNM S OR0=^(0) I $P(OR0,U,2) S ORNM=$P($G(^ORD(101.41,+$P(OR0,U,2),0)),U) D:$L(ORNM) EN^DDIOL(ORNM,,""? 10"")" |
|||
| 2813 | TIU REMOVE TYPE AS IDENTIFIER FROM DOC DEF FILE (#8925.1) | File | 1 | 1999/04/30 | APPROVED | Active | Private | 8925.1 | In initial test versions of TIU the .04 TYPE field of the DOCUMENT DEFINITIONS FILE (#8925.1) was defined as an identifier. This was changed prior to the release of TIU, but initial test sites still have the .04 field defined as an identifier. To remove this relationship, TIU requests permission to directly kill the Data Dictionary node defining this field as an identifier, i.e. K ^DD(8925.1,0,"ID",.04). This kill will be performed during the installation routine of TIU*1.0*38, which could not install properly without removal of the identifier status. |
|||
| 2821 | DIALOG File | Other | 1 | 1999/08/09 | APPROVED | Active | Supported | .84 | To qantify supported DIALOG entries in the DIALOG file #.84 |
|||
| 2847 | ALLOW DIE CALL WITHIN ANOTHER DIE | Routine | 1 | 1999/06/16 | APPROVED | Active | Private | This integration agreement is between IFCAP and FileMan. IFCAP is calling templates through a DIE programmer call. In the templates a routine is called. Within that routine a call is made to both DIC and DIE programmer calls to add a new sub-record entry and fill in additional data. This second DIE call is a recursive call. FileMan needs to save a group of variables to prevent the second DIE call from interfering with the first DIE call, the one handling the template. To properly call DIE the following variables need to be NEWed. DIAA,I,J,X,DO,DC,DA,DE,DG,DIE,DR,DIC,D,D0,D1,D2,D3,D4,D5,D6,DI,DH, DIA,DICR,DK,DIK,DL,DLAYGO,DM,DP,DQ,DU,DW,DIEL,DOV,DIOV,DIEC,DB, DV,DIFLD Any place within IFCAP that a recursive call to DIC/DIE needs to be done will be allowed by this agreement. This intregration agreement will stay in effect until FileMan DIC and DIE programmer calls become recursive. |
||||
| 2852 | Setting ID node (file #52) | File | 1 | 2003/06/10 | Retired | Private | 52 | Permission to re-set an ID node in file 52. |
||||
| 2866 | DDR DELETE ENTRY | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR DELETE ENTRY remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR DELETE ENTRY | |||
| 2867 | DDR FILER | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR FILER remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR FILER | |||
| 2868 | DDR FIND1 | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR FIND1 remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR FIND1 | |||
| 2869 | DDR FINDER | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR FINDER remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR FINDER | |||
| 2870 | DDR GET DD HELP | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR GET DD HELP remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR GET DD HELP | |||
| 2871 | DDR GETS ENTRY DATA | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR GETS ENTRY DATA remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR GETS ENTRY DATA | |||
| 2872 | DDR LISTER | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR LISTER remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR LISTER | |||
| 2873 | DDR LOCK/UNLOCK NODE | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR LOCK/UNLOCK NODE remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR LOCK/UNLOCK NODE | |||
| 2874 | DDR VALIDATOR | Remote Procedure | 1 | 1999/07/13 | APPROVED | Active | Private | The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR VALIDATOR remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. |
DDR VALIDATOR | |||
| 2878 | DELETE TRIGGER X-REF IN FILE 6926.01 FIELD .01 | File | 1 | 1999/07/28 | APPROVED | Active | Private | This IA permits patch EN*7*62 to delete the TRIGGER cross-reference (#2) of field #.01 in subfile #6926.01. Code similar to the following will be placed in a pre-install routine of the patch to perform the deletion. N DA,DIK S DIK="^DD(6926.01,.01,1," ;this is the root of "xref multiple" S DA(2)=6926.01,DA(1)=.01,DA=2 ;DA(2) = subfile# ;DA(1) = field# ;DA = xref# D ^DIK ;this deletes the xref definition Patch EN*7*62 will bring in a new #2 cross-reference (regular, whole-file) on the .01 field of #6926.01 during the install. The cross-reference deletion performed during the pre-install will ensure that all the trigger logic is completely removed. |
||||
| 2886 | Supported DataBase Server DIALOG Numbers | Other | 1 | 1999/08/11 | Withdrawn | Supported | The listed components are the supported DIALOG numbers that are associated with the DataBase Server calls and maybe used with the following supported DIALOG calls: BLD^DIALOG $$EZBLD^DIALOG MSG^DIALOG |
|||||
| 2903 | CHANGING WRITE IDENTIFIERS | Other | 1 | 1999/09/08 | APPROVED | Active | Private | This integration agreement allows the Accounts Receivable package to change the write identifiers on the AR TRANSACTION File #433. |
||||
| 2910 | Delete Read Protection on Files | File | 1 | 1999/10/05 | APPROVED | Active | Private | 1 | E3R PSN-4-12347 asked that the read protection on files related to National Drug File be removed. To meet this request, NDF requests a one time agreement with VA FileMan to KILL the global nodes ^DIC(50.6,0,"RD"), ^DIC(50.64,0,"RD"), ^DIC(50.67,0,"RD"), and ^DIC(50.68,0,"RD") |
|||
| 2916 | Data Base Server API: DD Modification Utilities | Routine | 1 | 1999/09/20 | APPROVED | Active | Supported | DDMOD | ||||
| 2928 | Delete Read Protection on PDM Files | File | 1 | 1999/10/15 | APPROVED | Active | Private | E3R PSN-4-12347 asked that the read protection on files related to and shared by National Drug File and Pharmacy Data Management be removed. To meet this request, PDM requests a one time agreement with VA Fileman to KILL the global nodes ^DIC(51.2,0,"RD") and ^DIC(50.606,0,"RD"). This this agreement is simular to and requested in conjunction with DBIA# 2910. |
||||
| 2989 | DBIA2989 | File | 1 | 2003/06/10 | Retired | Private | 90 | This is a one time DBIA request to modify the field definitions of two fields from the MENTAL HEALTH package's MEDICAL RECORDS file (#90.) This is in response to NOIS calls PUG-1099-51192 and HOU-0399-72142. Patch YS*5.01*58 was created to address these NOIS calls. Here is the patch description from YS*5.01*58: This patch corrects an error that occurs in menu option "Identify Potential Merge Problems [XDR VALID CHECK]" of the MEDICINE package. Although it originally appeared to be a FILEMAN error or a MEDICINE package error, it was later determined to be a data dictionary problem with the MEDICAL RECORDS file (#90) of the MENTAL HEALTH package. The error appears as follows: $ZE= DDENTRY+29^DIQGQ:3, %DSM-E-NAME, bad variable name ..D F S DIQGMDA=$O(@DIQGMGR@(DIQGMDA)) Q:DIQGMDA'>0 D EN($S('DIQGDD:DIQGMDD, 1:$$OREF(DIQGMGR)),.DIQGMDA,"**",DIQGPARM,.DIQGTA,"",$S('DIQGDD:"",1:1)) Last Global Ref: ^DIC(.12,0,"GL") The problem is caused by the DD definition of the COMMENTS field (Sub file #90.02, Sub field #30) of the PHY field (Sub file #90.01, Sub field #100) of the MEDICAL RECORDS file (#90.) The GETS^DIQ call in routine XDRDVAL was extracting all fields and sub fields for the given record (due to the "**" in the FIELD parameter.) See below: D GETS^DIQ(FILE,IEN,"**","EIN",DATAROOT,MESGROOT) The COMMENTS field (#30) is defined as a free text multiple but stored as a word-processing field. In a multiple field, the header (or 0) node contains the DD entry number of the sub file in the second piece. Because the DD definition of the COMMENTS field (#30) is defined as a multiple field, FILEMAN takes the value of the second piece (delimited by "^") of the header node and pluses it (+) to get the DD entry number of the sub file. See below: ^MR(7180189,"PE",7069286,19,0) = ^^1^1^2930713^ The node above resembles a word processing field but in the DD it is defined as a multiple. A multiple should have a sub file number in the second piece. Since nothing is in the second piece, the resulting number returned to FILEMAN was a 0 (zero) which confused FILEMAN, causing it to look at the wrong file. The same DD problem exists in the INITIAL IMPRESSION field (Sub file #90.03, Sub field #31.) This field is defined as a free text multiple but stored as a word-processing field. In this situation, no data problem exists. The data is correct and requires no modifications. The solution is to change the definitions of these fields from multiples to word-processing. Because MEDICAL RECORDS file is an old file, it is not possible to make the data dictionary changes using FILEMAN. Therefore, it is necessary to use hard SETS and KILLS to update the data dictionary. Here is the data as it exists prior to the installation of this patch. Please note that, for better readability, not all nodes have been displayed: COMMENTS field (#30) ^DD(90.01,30,0) = COMMENTS^90.02A^^19;0 ^DD(90.01,30,21,0) = ^^1^1^2930202^ ^DD(90.01,30,21,1,0) = Comments relating to the physical exam. ^DD(90.02,0) = COMMENTS SUB-FIELD^NL^.01^1 ^DD(90.02,.01,0) = COMMENTS^MF^^0;1^K:$L(X)>70!($L(X)<2) X ^DD(90.02,.01,3) = ANSWER MUST BE 2-70 CHARACTERS IN LENGTH ^DD(90.02,.01,21,0) = ^^2^2^2930202^ ^DD(90.02,.01,21,1,0) = Comments enter by the examiner relating to the physical exam of the ^DD(90.02,.01,21,2,0) = patient. INITIAL IMPRESSION field (#31) ^DD(90.01,31,0) = INITIAL IMPRESSION^90.03A^^20;0 ^DD(90.01,31,21,0) = ^^1^1^2930202^ ^DD(90.01,31,21,1,0) = Examiner's initial impression. ^DD(90.03,0) = INITIAL IMPRESSION SUB-FIELD^NL^.01^1 ^DD(90.03,0,"NM","INITIAL IMPRESSION") = ^DD(90.03,0,"UP") = 90.01 ^DD(90.03,.01,0) = INITIAL IMPRESSION^MF^^0;1^K:$L(X)>70!($L(X)<2) X ^DD(90.03,.01,3) = ANSWER MUST BE 2-70 CHARACTERS IN LENGTH Routine YS58POST will run during installation of YS*5.01*58 to perform the following: 1) Remove the "A" from the sub field number. The "A" indicates to automatically add entries without asking: "ARE YOU ADDING A NEW ENTRY?" This is no longer applicable for a word processing file. S $P(^DD(90.01,30,0),U,2)=90.02 (COMMENTS) S $P(^DD(90.01,31,0),U,2)=90.03 (INITITAL IMPRESSION) 2) Reset the field definition which is stored in the data dictionary's zero node, field .01, of the sub file. The "MF" originally in the second piece indicates this field is a multiple and free text. We replace it with "W" which indicates a word processing field. The input transform Mumps code is replaced with "Q" in the fifth piece. S ^DD(90.02,.01,0)="COMMENTS^W^^0;1^Q" S ^DD(90.03,.01,0)="INITIAL IMPRESSION^W^^0;1^Q" 3) Kill the help text in the 3 node. It is no longer needed. K ^DD(90.02,.01,3) (COMMENTS) K ^DD(90.03,.01,3) (INITIAL IMPRESSIONS) 4) Correct a spelling error for the COMMENTS field (#30.) S ^DD(90.02,.01,21,1,0)="Comments entered by the examiner relating to the physical exam" This is how the data dictionary entries appear after the changes are made. COMMENTS field (#30) ^DD(90.01,30,0) = COMMENTS^90.02^^19;0 ^DD(90.01,30,21,0) = ^^1^1^2930202^ ^DD(90.01,30,21,1,0) = Comments relating to the physical exam. ^DD(90.02,0) = COMMENTS SUB-FIELD^NL^.01^1 ^DD(90.02,.01,0) = COMMENTS^W^^0;1^Q ^DD(90.02,.01,21,0) = ^^2^2^2930202^ ^DD(90.02,.01,21,1,0) = Comments entered by the examiner relating to the physical exam of the INITIAL IMPRESSION field (#31) ^DD(90.01,31,0) = INITIAL IMPRESSION^90.03^^20;0 ^DD(90.01,31,21,0) = ^^1^1^2930202^ ^DD(90.01,31,21,1,0) = Examiner's initial impression. ^DD(90.03,0) = INITIAL IMPRESSION SUB-FIELD^NL^.01^1 ^DD(90.03,.01,0) = INITIAL IMPRESSION^W^^0;1^Q |
||||
| 2991 | DBIA2991 | File | 1 | 1999/11/23 | APPROVED | Active | Controlled Subscription | Variable pointer information is sometimes required. This information can be found in ^DD(file#,field#.,"V"). This DBIA provides for read-only access of the nodes ^DD(file#,field#,"V",. |
||||
| 3024 | ID Nodes in Patient (#2) file | File | 1 | 2003/06/10 | Retired | Private | 2 | DG*5.3*249, DGSEC Modifications and Privacy Act Compliance for Employees, modifies the identifiers on the DOB (#.03) and Social Security Number (#.09) fields in the Patient (#2) file to: ^DD(2,0,"ID",.03) = D EN^DDIOL($TR($$DOB^DPTLK1(Y,1),"/","-"),,"?$X+2") ^DD(2,0,"ID",.09) = D EN^DDIOL($$SSN^DPTLK1(Y),,"?$X+2") The DOB and SSN function calls in DPTLK1 are new with this patch. If the patient's primary eligibility code is Employee, *SENSITIVE* will be displayed for the DOB and SSN fields until the user verifies they want to access the restricted record. The post-init routine, DG53249P, will set the "ID" nodes: DG53249P ;ALB/JAP - Patch 249 postinstall ; 1/11/00 12:56pm ;;5.3;Registration;**249**;Aug 13, 1993 ; EN ;entry point from install ;update identifier code in patient file S ^DD(2,0,"ID",.03)="D EN^DDIOL($TR($$DOB^DPTLK1(Y,1),""/"",""-""),,""?$X+2"")" S ^DD(2,0,"ID",.09)="D EN^DDIOL($$SSN^DPTLK1(Y),,""?$X+2"")" Q |
||||
| 3040 | Direct set DD node | File | 1 | 2000/02/15 | APPROVED | Active | Private | Agreement allowing the direct setting of the ^DD(file,0,"ACT") node. |
||||
| 3060 | Reference to variable DICR | Other | 1 | 2000/03/08 | APPROVED | Active | Private | Reference to undocumented variable, DICR, for the purpose of determining if lookup by patient is originating in a file other than the PATIENT file. |
||||
| 3150 | DBIA 3150 | File | 1 | 2003/06/10 | Retired | Private | 50.7 | The Pharmacy Data Management (PDM) application would like to ask permission to create a new data dictionary global related to the ORDERABLE ITEM file (# 50.7). The new global will be used to set the INACTIVE DATE field (#.04) as an identifier in the ORDERABLE ITEM file (# 50.7). Here is an example of the new DD global and contents. ^DD(50.7,0,"ID",.04) = W " ",$$FMTE^DILIBF($P(^(0),U,4),6) The PSSP32 routine will contain the coding logic to set the new DD global. The PSSP32 routine will only be used by PDM patch # 32 and KIDS will delete the PSSP32 routine after the installation. Here is a copy of the routine. PSSP32 ;BIR/TTH-INACTIVE DATE FIELD IDENTIFIER ; 4-FEB-2000 14:17 ;;1.0;PHARMACY DATA MANAGEMENT;**32**;9/30/97 ; ID ;In the ORDERABLE ITEM file (#50.7), set the INACTIVE DATE field (#.04) a s an identifier. S ^DD(50.7,0,"ID",.04)="W "" "",$$FMTE^DILIBF($P(^(0),U,4),6)" Q |
||||
| 3180 | DBIA 3180 | File | 1 | 2000/08/29 | APPROVED | Active | Private | 27.16 | There is a "LAYGO" node on the .01 field of ENROLLMENT GROUP THRESHOLD file (#27.16). The code prevents any records from being added to the file. Since there are no FileMan tools to remove a "LAYGO" node once it's set, Enrollment would like permission to add an explicit KILL of the node in a post-install routine. The line of code would be: K ^DD(27.16,.01,"LAYGO") The ENROLLMENT GROUP THRESHOLD file is part of the Enrollment package. |
|||
| 3209 | DDR GETS ENTRY DATA | Remote Procedure | 1 | 2000/09/20 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3215 | DDR DELETE ENTRY | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3216 | DDR FILER | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3217 | DDR FIND1 | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3218 | DDR FINDER | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3219 | DDR KEY VALIDATOR | Remote Procedure | 1 | 2000/09/20 | Withdrawn | Private | This agreement indicates that the DDR KEY VALIDATOR RPC necessary for use of the Fileman Delphi Components is a supported reference. |
DDR KEY VALIDATOR | ||||
| 3220 | DDR GET DD HELP | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3221 | DDR LISTER | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3222 | DDR LOCK/UNLOCK NODE | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3223 | DDR VALIDATOR | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3224 | DDR KEY VALIDATOR | Remote Procedure | 1 | 2000/10/03 | APPROVED | Active | Supported | This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. |
||||
| 3261 | BLOOD BANK AND DIRECT ACCESS TO DD GLOBAL | File | 1 | 2000/11/24 | APPROVED | Active | Private | The Blood Bank module of the LAB SERVICES package has been granted permission by the custodial package (VA FileMan) to access the DD global as detailed in this DBIA. |
||||
| 3307 | DBIA 3307 - Imaging & Fileman routines | Other | 1 | 2005/03/10 | Retired | Private | Fileman gives Imaging permission to distribute and download Fileman routines onto their DICOM gateway. |
|||||
| 3308 | DBIA 3308 - Imaging points to file1 | Other | 1 | 2001/03/02 | Withdrawn | Private | Fileman gives permission to the Imaging package to point out to File #1 from the Imaging's PARENT DATA FILE (#2005.03). No LAYGO access is allowed to file #1. |
|||||
| 3315 | UPDATE DIE | Routine | 1 | 2001/02/14 | APPROVED | Active | Private | Registration is requesting to export a new cross reference to the .01 and .09 fields of the Patient file (#2) by hardsetting the ^DD("IX" global nodes and using UPDATE^DIE to get the IEN in ^DD("IX" to use. The reason to hardset the global rather than have KIDS export the x-ref is that the .01 of the Patient file (#2) is has changes in test in the field for the Name Standardization patch which is on indefinate hold. |
DIE | |||
| 3316 | HARSET DD('IX' | File | 1 | 2004/07/22 | Retired | Private | .11 | Registration is requesting to export a new cross reference to the .01 and .09 of the Patient file (#2) by hardsetting the ^DD("IX" global nodes and using UPDATE^DIE to get the IEN in ^DD("IX" to use. The reason to hardset the global rather than have KIDS export the x-ref is that the .01 and .09 of the Patient file (#2) is has changes in test in the field for the Name Standardization patch which is on indefinate hold. |
||||
| 3319 | DBIA3319 | File | 1 | APPROVED | Retired | Private |
************************************************************************ The Library package was decommissioned with LBR*2.5*15. This ICR was retired with the release of the Library patch. ************************************************************************ |
|||||
| 3352 | INPUT TEMPLATE RECOMPILATION | Routine | 1 | 2001/04/05 | APPROVED | Active | Controlled Subscription | Recompile compiled input templates that contain specific fields within a file. |
DIKCUTL3 | |||
| 3357 | DBIA3357 | File | 1 | 2001/04/16 | APPROVED | Active | Private | Inpatient Medications requests an agreement to allow the deletion of the 'V' level for the .01 field of the MAR LABELS file (#53.41). The level was apparently left over when the field was converted from a 'VARIABLE POINTER' data type to a 'SET OF CODES' data type. The 'V' level will be deleted in PSJ*5.0*57 with a direct KILL to the global. |
||||
| 3404 | UPDATE NEW-STYLE X-REF ONLY | File | 1 | 2001/06/01 | APPROVED | Active | Private | .11 |
Registration is requesting to export New Style-Cross References to registration files by setting the ^DD("IX" global nodes of the INDEX file using UPDATE^DIE and WP^DIE. This methodology allows us to create New Style cross-references without exporting the field itself. Listed below is an example how the Filer Array would be populated. ;Create filer array S DGFDA(.11,"+1,",.01)= ;FILE NUMBER S DGFDA(.11,"+1,",.02)= ;X-REF NAME S DGFDA(.11,"+1,",.11)="This X-ref invokes DG FIELD MONITOR " ;SHORT DESCRIPTION S DGFDA(.11,"+1,",.2)= ;TYPE S DGFDA(.11,"+1,",.4)= ;EXECUTION S DGFDA(.11,"+1,",.41)= ;ACTIVITY S DGFDA(.11,"+1,",.5)= ;ROOT TYPE S DGFDA(.11,"+1,",.51)= ;ROOT FILE NUMBER S DGFDA(.11,"+1,",.42)= ;USE S DGFDA(.11,"+1,",1.1)= ;SET LOGIC S DGFDA(.11,"+1,",2.1)= ;KILL LOGIC ;CROSS REFERENCE VALUES S DGFDA(.114,"+2,+1,",.01)= ;ORDER NUMBER S DGFDA(.114,"+2,+1,",1)= ;TYPE OF VALUE S DGFDA(.114,"+2,+1,",2)= ;FILE NUMBER S DGFDA(.114,"+2,+1,",3)= ;FIELD NUMBER S DGFDA(.114,"+2,+1,",7)= ;COLLATION ;DESCRIPTION S DGWP(1)="This cross reference activates the DG FIELD MONITOR event point." S DGWP(2)="Applications that wish to monitor edit activity related to this field may" S DGWP(3)="subscribe to that event point and take action as indicated by the changes" S DGWP(4)="that occur. Refer to the DG FIELD MONITOR protocol for a description of" S DGWP(5)="the information available at the time of the event." ;File INDEX record D UPDATE^DIE("","DGFDA","DGIEN","DGERR") I $D(DIERR) D Q ;CHECK FOR ERROR .N DGI S DGI="" .F S DGI=$O(DGERR("DIERR",1,"TEXT",DGI)) Q:DGI="" D ..D MES^XPDUTL(DGERR("DIERR",1,"TEXT",DGI)) ;DISPLAY ERROR ..Q .Q ;File DESCRIPTION field D WP^DIE(.11,DGIEN(1)_",",.1,"","DGWP") ;FILE DESCRIPTION Q |
|||
| 3405 | TRIG DICR | Routine | 1 | 2001/06/01 | APPROVED | Active | Controlled Subscription |
Registration is requesting to use TRIG^DICR for the purposes of updating the trigger logic when exporting New Style-Cross References in conjunction with DBIA 3404 to registration files. Usage of this routine is outlined below. TRIG^DICR(.fieldList,.outputList) Where, fieldList = (Input) Array of file/fields that may be triggered. The trigger logic of fields that trigger the fields in this list is modified, as necessary. Format: fieldList(file#,field#)="" outputList = (Output) This array is returned with the list of fields whose trigger logic was modified. Format: outputList(file#,field#)="" |
DICR | |||
| 3434 | DIALOG File Entry Deletion | File | 1 | 2001/08/13 | APPROVED | Active | Private | .84 |
When creating patch RGED*2.6*1 to remove Extensible Editor v.2.6, we tried to eliminate the DIALOG (#.84) file entries distributed with the package (9960001 - 9960070) by placing them in the build and marking them as DELETE AT SITE. KIDS did not remove them on the target system because delete access on File .84 is set to an "^". Therefore, a private integration agreement is established to allow the reference to ^DI(.84 using the following code in RGEDPST. ;Delete DIALOG file entries 9960001 through 9960070. N RGEDLOG W !!," Deleting Extensible Editor dialog entries.",!," " S DIK="^DI(.84," F RGEDLOG=9960001:1:9960070 S DA=RGEDLOG D ^DIK W "." W !!," DIALOG entries 9960001 through 9960070 have been deleted." |
|||
| 3446 | coreFLS Foreign File Format | File | 1 | 2001/08/23 | APPROVED | Active | Private | .44 | coreFLS needs to obtain data from various files to populate their tables with legacy data. One method being used is the FileMan data export tools. Since it is not possible to send FileMan Foreign File formats via KIDS, we will need to populate FOREIGN FORMAT file (#.44) with an entry. |
|||
| 3447 | coreFLS Export Templates | File | 1 | 2001/08/23 | APPROVED | Active | Private | .4 | With the new entry into the FOREIGN FORMAT file (#.44) (see IA 3446), the PRCL* namespaced export templates in the PRINT TEMPLATE file (#.4) will need to have the EXPORT FORMAT field (#105) updated to be the foreign format IEN. |
|||
| 3476 | DIEZ UNCOMPILE INPUT TEMPLATES/DELETE COMPILED ROUTINES | Routine | 1 | 2001/11/05 | APPROVED | Active | Controlled Subscription | UNC^DIEZ is a silent VA FileMan call that allows the deletion of compiled Input Templates and their associated compiled routines. The entry point 'UNC' can accept two input parameters: DIEZ = The IEN of the input template to uncompile. DIFLAGS = "D" indicates all associated compiled routines are to be deleted. The variable DIEZ is required; the variable DIFLAGS is optional. |
DIEZ | |||
| 3532 | Imaging DIBT read | File | 1 | 2002/02/27 | APPROVED | Active | Controlled Subscription | .401 | FileMan gives Imaging permission to read the DIBT global. The Fileman team reserves the right to make changes allowing Imaging developers 3 to 6 months notice prior modifications. This request is to read the search criteria stored in the DIBT global. A call to EN^DIS is initiated to start the FileMan search logic dialog. Imaging understands that the nodes read from the DIBT global are not documented and may change. |
|||
| 3534 | Setting DD fields in post-init routine | File | 1 | 2002/02/28 | APPROVED | Active | Private | An integration agreement is needed for Registration to set ^DD nodes for several PATIENT (#2) file fields in the post initialization routine DG53244R for patch DG*5.3*244, Patient Name Standardization. The INPUT TRANSFORM (#.5), 'HELP'-PROMPT (#3) and DESCRIPTION (#21) fields for the following PATIENT (#2) file fields and subfields is updated by DG*5.3*244. DG*5.3*620 will also set ^DD nodes for the following fields in its post initialization routine DG53620D. This patch will switch the API called from the ^DD, $$FORMAT^DPTNAME, to its equivalent in Kernel, $$FORMAT^XLFNAME7. Thus the Input transform referred to in patch DG244 is not longer valid. NAME (#.01) K-NAME OF PRIMARY NOK (#.211) K2-NAME OF SECONDARY NOK (#.2191) FATHER'S NAME (#.2401) MOTHER'S NAME (#.2402) MOTHER'S MAIDEN NAME (#.2403) E-NAME (#.331) E2-NAME OF SECONDARY CONTACT (#.3311) D-NAME OF DESIGNEE (#.341) Subfields: NAME (#.01) field in the ALIAS (#2.01) multiple ATTORNEY'S NAME (#30) field in the DISPOSITION LOG-IN DATE/TIME (#2.101) multiple Also, the SET and KILL logic will be updated for the name field. |
||||
| 3586 | New Style Xref and Fileman Variables | Other | 1 | 2002/05/22 | APPROVED | Active | Private | The HUI Project is using a new style cross-reference, type Action and is executed at the Record level. In the routine XUHUI the following Fileman array/variables are being read: DIFILE() to get the file and sub-file numbers and pass them on in a name spaced variable XUHUIFIL(). DIFLD() to get the field(s) and pass them on in a name spaced variable XUHUIFLD(). DA() to get the IEN(s) and pass them on in a name spaced variable XUHUIDA(). The being used is as follows: ZL XUHUI ZP S2:S2+6 S2 ;Section 2 N XUHUIFIL,XUHUIFLD,XUHUIDA,XUHUIX,XUHUIX1,XUHUIX2 S XUHUIFIL=DIFILE ;File # I $D(DIFLD) M XUHUIFLD=DIFLD ;Field # I '$D(DIFLD) S XUHUIFLD="" S XUHUIXR=$G(XUHUIXR) M XUHUIDA=DA ;IEN(s) of record It is realized some of these variables may be undefined or null and that Fileman reserves the right to changed the variables. It is with this intent that it would be nice if a notice was given to the XUHUI* developer that these are being changed so that patch coordination can happen. |
||||
| 3591 | Install 'AXUHUI' and 'AXUHUIKEY' Xrefs | File | 1 | 2002/05/29 | APPROVED | Active | Private | .11 | Patch XU*8*236 needs to install/tranport two New Style xrefs: 'AXUHUI' and 'AXUHUIKEY' without sending the necessary field DDs too. This request is for a one time IA. |
XUHUI236 | ||
| 3592 | DBIA3592 | File | 1 | 2003/06/10 | Retired | Private | 20 | Clean up routines, as part of the Patient Name Standardization (DG*5.3*244) patch, will need to be run at 8-10 test sites. This clean up will correct the name standardization performed in previous test versions of the patch. This is a one time only clean up. In addition to correcting the standardization of patient names, the clean up routines will need to populate the SOURCE NAME FORMAT FLAGS (#7) field of the NAME COMPONENTS (#20) file for every component entry not having a value. In this agreement we are requesting access to add a flag value to the SOURCE NAME FORMAT FLAGS (#7) field of the NAME COMPONENTS (#20) file. And, in order to prevent the ANAME cross reference from being executed we are requesting the ability to set XUNOTRIG=1 before making the DIE^FILE call to add a value to the field. |
||||
| 3594 | BROWSER SWITCHING | Routine | 1 | 2002/06/03 | APPROVED | Active | Private | The purpose of this DBIA is to provide a temporary method for switching between 'documents' without the user having to mentally resolve pointers between records in two different files. The needed functionality is currently planned by the VA Fileman developers to released in a patch. When that patch is released, the HL7 developers will modify the Transmission Log code to use the released functionality. See IA# 2540. (This is a continuation of IA# 2540, and is used to cover references to the PSR subroutine tag in routine DDBR0.) |
DDBR0 | |||
| 3597 | DIA(985 | File | 1 | 2002/06/12 | APPROVED | Active | Private | 1.1 | The MPI Austin software is running an audit purge to clean up the ^DIA(985 entries for a time range. The FileMan audit purge ran too slow and was not cleaning up completely each of the entries in the purge date range. So MPI Austin wrote its own purge for the ^DIA(985, entries. The MPI Austin software is therefore, requesting a DBIA to have direct global read and kill of ^DIA(985, ^DIA(985,"C" and direct global kill of ^DIA(985,"D" and ^DIA(985,"B". |
|||
| 3623 | DBIA3623 | File | 1 | 2002/07/23 | APPROVED | Active | Private | .46 | DSS is granted permission to export the INPUT TEMPLATE file via KIDS with a single entry. This entry is used when importing data into the DSS Department Table. This is a one time agreement. Patch number is ECX*3.0.45. |
|||
| 3626 | DBIA3626 | File | 1 | 2002/07/24 | APPROVED | Active | Private | 1 | This integration agreement is necessary in order to facilitate a change to the write access on field #20.51 (ADDRESS CHANGE DATE) of the #300.11 (VIVA) file. The write access is currently set to the "^" character, and will be changed to "@", in order to allow the filing of new data into the field. The PRE^IVMB686 tag will be used for this purpose. The patch number, IVMB*2*686, will only be installed on the HEC system, and this request is for a one-time use only. The Fileman team provided preliminary approval of this request. |
|||
| 3746 | DBIA3746 | File | 1 | 2003/02/03 | APPROVED | Active | Private | 0 | This IA will document that the Medicine package can loop through the ^DD(file number,0,"ID") with $O to get the identifier numbers. The file numbers that the Medicine will loop through ranges from 690 to 701. |
|||
| 3805 | File restriction issues within VistA Blood Bank. | File | 1 | 2002/10/25 | APPROVED | Active | Private | 0 | The purpose on this integration agreement is to restrict certain VistA Blood Bank files from all VistA users. The manipulation of data within these files is prohibited. The following VistA Blood Bank files are targeted for restricted status: File Name File Number File Restriction Method =============================================================== BLOOD INVENTORY 65 S ^DD(65,0,"DI")="^Y" BLOOD BANK UTILITY 65.4 S ^DD(65.4,0,"DI")="^Y" BLOOD DONOR 65.5 S ^DD(65.5,0,"DI")="^Y" BLOOD PRODUCT 66 S ^DD(66,0,"DI")="^Y" BLOOD BANK VALIDATION 66.2 S ^DD(66.2,0,"DI")="^Y" OPERATION (MSBOS) 66.5 S ^DD(66.5,0,"DI")="^Y" BLOOD COMPONENT REQUEST 66.9 S ^DD(66.9,0,"DI")="^Y" |
|||
| 3815 | DBIA3815 | File | 1 | 2002/10/30 | APPROVED | Active | Private | 1 | In order to protect against database corruption, this Integration Agreement will be used as a one-time only action to check for the existance of the ^DD(5.12,0,"UP") global node prior to the installation of patch XU*8*246. This node was found to have existed in one of our test accounts, and may exist in one or more Production VistA accounts. If this node exists during installation of the patch, the install will halt and prompt the user to contact NVS for further assistance. |
|||
| 3875 | ID Write identifier node File #441 | File | 1 | 2003/01/14 | APPROVED | Active | Private | 441 | The National Item File's Item Number (NIF ITEM NUMBER field #51) needs to be added as a write identifier to the ITEM MASTER File #441. Field #51, is not a user-editable field, therefore it can not be defined as a field identifier. As KIDS does not have a mechanism to transport write identifiers without exporting the entire file definition, it is requested that for patch PRC*5.1*63 (NATIONAL ITEM FILE - PHASE 1) IFCAP be permitted to set the ID node via the post-init routine PRC5163P. The proposed code is as follows: EN ;Entry point ;Adding NIF Item # as write identifier for ITEM MASTER file (#441) S ^DD(441,0,"ID","Z")="W:$P($G(^(0)),U,15)>0 "" NIF#""_ $P($G(^(0)),U,1 5)" Q |
|||
| 3885 | DI OPTIONS/MENUS ON SECURITY OFFICER MENU | Other | 1 | 2003/02/03 | APPROVED | Active | Private | Health Information Security Service is requesting to place some DI options/menu on INFORMATION SECURITY MENU [XUSPY]. DIPRINT on the XUDIACCESS FOR ISO menu. DISEARCH on the XUDIACCESS FOR ISO menu. DIINQUIRE on the XUDIACCESS FOR ISO menu. DILIST on the XUDIACCESS FOR ISO menu. DIAUDIT on the XUDIACCESS FOR ISO menu. DIAUDITED FIELDS on the DIAUDIT menu. DIAUDIT DD on the DIAUDIT menu. DIAUDIT PURGE DATA on the DIAUDIT menu. DIAUDIT PURGE DD on the DIAUDIT menu. DIAUDIT TURN ON/OFF on the DIAUDIT menu. |
||||
| 4017 | File 8927.1 | File | 1 | 2003/03/18 | Withdrawn | Private | 8927.1 | |||||
| 4078 | ID Node in PATIENT (#2) file, field 994 | File | 1 | 2003/04/09 | APPROVED | Active | Private | 2 |
DG*5.3*505 exports a new field, MULTIPLE BIRTH INDICATOR (#994), to the PATIENT (#2) file. This field is to be an identifier. KIDS does not automatically export the identifier on the new field, as it is distributed in a partial DD. The post-init routine, DG505PST, will set the "ID" node: DG505PST -- ;BIR/PTD-PATCH DG*5.3*505 POST INSTALLATION ROUTINE ;4/7/03 ;;5.3;Registration;**505**;Aug 13, 1993 ; EN ;Entry point ;Update identifier code for MULTIPLE BIRTH INDICATOR (#994) field in PATIENT (#2) file D BMES^XPDUTL(" Updating the identifier code for the MULTIPLE BIRTH INDICATOR (#994) field.") S ^DD(2,0,"ID",994)="D EN^DDIOL($$GET1^DIQ(2,Y_"","",994),"""", ""?$X+2"")" Q ; |
|||
| 4093 | Setting ID node (file #392.31) | File | 1 | 2003/04/24 | APPROVED | Active | Private | 392.31 | Beneficiary Travel would like to add a hard-set routine call in the "ID" node of the ^DD file of #392.31. This hard-set routine call will display phone, fax, and address information needed to distinguish between like vendors. The variable Y will be used as the input variable and the EN^DDIOL call will be used to output the information. Hard-set in the ^DD will look like the following: ^DD(392.31,0,"ID","Z") = G START^DGBTID With the letter 'I' being placed in the 2nd piece of the File Header: ^DGBT(392.31,0) = LOCAL VENDOR^392.31OI^12^11 |
|||
| 4136 | Look For 'PT' Nodes in File 5.12 | File | 1 | 2003/06/24 | APPROVED | Active | Private | 5.12 |
In routine XIPENV (enviroment check routine) it is necessary to look for "PT" nodes of files that should NOT be Pointing To this file. The need for this check is because in the pre-installation routine will be deleting this file prior to the new DD and data being installed. |
|||
| 4137 | Look For 'PT' Nodes in File 5.13 | File | 1 | 2003/06/24 | APPROVED | Active | Private | 5.13 | In routine XIPENV (enviroment check routine) it is necessary to look for "PT" nodes of files that should NOT be Pointing To this file. The need for this check is because in the pre-installation routine will be deleting this file prior to the new DD and data being installed. |
|||
| 4139 | PATIENT FILE (#2) DATE OF BIRTH FIELD (.03) IDENTIFIER | File | 1 | 2010/12/13 | APPROVED | Active | Private | 2 | This is a one-time agreement to allow Registration to set the IDENTIFIER node as follows for the PATIENT (#2) file: ^DD(2,0,"ID",.03)="D EN^DDIOL($TR($$DOB^DPTLK1(Y,1),""/"",""-""),,""?$X+2"")" This api will add the IDENTIFIER parameter back to the PATIENT file (#2). It was an unknown fact that the IDENTIFIER parameter would be removed when the DG*5.3*754 pre-init routine (DG53754P) initialized the field definition for the DATE OF BIRTH field (#.03) from the PATIENT file (#2). |
2010/12/13 | ||
| 4140 | Remove ID Node From File #5.12 | File | 1 | 2003/06/30 | APPROVED | Active | Private | 5.12 | During the install of data at the target site for patch XU*8*292 it is necessary to have 'UNIQUE KEY (VA)' (#8) field brought in as an Identifier so duplicate Zip Code entries can be resolved, then during the post-install it is necessary to remove it via: K ^DD(5.12,0,"ID",8) ; IA #4140 This would be a one time agreement. |
|||
| 4229 | DBIA 4229 | File | 1 | 2003/08/29 | APPROVED | Active | Private | A dangling "IX" node needs to be cleaned up for subfile 811.22102. |
||||
| 4252 | SET LAYGO NODE IN FILE 50.416 | File | 1 | 2004/08/31 | APPROVED | Active | Private | 50.416 | National Drug File requests a one time integration agreement with VA FileMan to set the LAYGO node in DD(50.416) to prevent sites from making local additions to this national file. Additions will only be made by data update patches. |
|||
| 4281 | Field selection/lookup based on DD global with call to DIC | File | 1 | 2010/12/14 | APPROVED | Active | Controlled Subscription | The LAB SERVICE package (LSRP project) has a requirement for the user to be able to select specific fields in the LABORATORY TEST (#60) file and to set auditing on and off for these fields. In order for the users to select the fields available for a file, a DIC call would be used with the variable DIC set to "^DD(". This ICR will allow the LAB SERVICE package to use ^DD in this manner. S DIC="^DD(60," S DIC(0)="AEQMZ",DIC("A")="Field: " D ^DIC |
2010/12/15 | |||
| 4293 | Update DIC(5,'%D' | File | 1 | 2003/11/06 | APPROVED | Active | Private | 5 | Update the file DESCRIPTION for the STATE(#5) file. |
|||
| 4309 | Allow looping through 'AUDIT' nodes of DD | File | 1 | 2010/12/14 | APPROVED | Active | Controlled Subscription | The LAB SERVICE package (LSRP project) has a requirement that we set specific fields to be audited on patch installation and remove any audit indicators on any fields that are not in the predefined list for the LABORATORY TEST file (#60) and for a few file 60 subfiles. In order to reset the existing audit indicators, it will be necessary to use hard code to traverse the ^DD(60,"AUDIT", fields. S LRFLD=0 F S LRFLD=$O(^DD(60,"AUDIT",LRFLD)) Q:'LRFLD D . If audit on and field LRFLD is not on list, turn audit off for LRFLD . If audit off and field LRFLD is on list, turn audit on for LRFLD The subfiles that are also included for this task are: Field # Field Name Subfile # Direct reference needed ================================================================== 100 SITE/SPECIMEN 60.01 ^DD(60.01,"AUDIT" 2 SYNONYM 60.1 ^DD(60.1,"AUDIT" 6 ACCESSION AREA 60.11 ^DD(60.11,"AUDIT" 500 VERIFY WKLD CODE 60.12 ^DD(60.12,"AUDIT" 500.1 ACCESSION WKLD CODE 60.13 ^DD(60.13,"AUDIT" |
2010/12/15 | |||
| 4323 | DBIA 4323 | File | 1 | 2004/09/01 | APPROVED | Active | Private | 0 | Pharmacy Data Management will have access to look at the ^DD(50,0,"IX" nodes to get the field number of the file based on the cross reference. Then by using the FIELD^DID API, the data type will be determined. |
|||
| 4326 | DBIA 4326 | File | 1 | 2004/09/01 | APPROVED | Active | Private | 0 | Pharmacy Data Management will have access to look at the ^DD(51.5,0,"IX" nodes to get the field number of the file based on the cross reference. Then by using the FIELD^DID API, the data type will be determined. |
|||
| 4376 | DBIA4376 | File | 1 | 2004/03/02 | APPROVED | Active | Private | 393 | DGBT*1*1 added a variable pointer L.LOCAL VENDOR to the TRANSCRIBED BY (#10.04) of the INCOMPLETE RECORDS (#393) file. Unknowingly to the developer, the DD entries were not cleaned up properly. Request killing off the bad DD node entries to clean up the problem. Request is one time only. |
|||
| 4379 | Post-Selection Action in Patient (#2) file | File | 1 | 2004/05/04 | Retired | Private | 2 |
DG*5.3*582, Registration is sending multiple ISO bulletins. A flag has been added to DGRPEIS1, and the post-selection action for the Patient (#2) file needs to be modified to check for this flag so additional bulletins will be suppressed. Old value: ^DD(2,0,"ACT")= I '$G(DICR),$G(DIC(0))'["I" D ^DGSEC Changing to: ^DD(2,0,"ACT")= I '$G(DICR),$G(DIC(0))'["I",'$G(DGBULSUP) D ^DGSEC DG53P582 ;ALB/BWF; Pre-Init; ; 3/19/2004 8:36am ;;5.3;Registration;**582**;Aug 13, 1993 ENV ;Environment check point S XPDABORT="" D PROGCHK(.XPDABORT) I XPDABORT="" K XPDABORT Q PROGCHK(XPDABORT) ;checks for necessary programmer variables I '$G(DUZ)!($G(DUZ(0))'="@")!('$G(DT))!($G(U)'="^") D . D BMES^XPDUTL("*****") . D MES^XPDUTL("Your programming variables are not set up properly.") . D MES^XPDUTL("Installation aborted.") . D MES^XPDUTL("*****") . S XPDABORT=2 Q PRE ; S ^DD(2,0,"ACT")="I '$G(DICR),$G(DIC(0))'["I",'$G(DGBULSUP) D ^DGSEC" Q |
||||
| 4397 | DIAUTL | Routine | 1 | 2004/04/08 | APPROVED | Active | Supported | Auditing Utilities. Auditing allows VA FileMan users and developers to look back through the dimension of time at prior values in any file. Auditing is not just a tool that enhances quality control and system security. It also allows the easy retrieval of "old" values (e.g., "address", "maiden name," and so on). |
DIAUTL | 2016/02/05 | ||
| 4399 | Local FileMan Array DIPA() | Other | 1 | 2004/04/13 | APPROVED | Active | Supported | Allow usage of the DIPA() array for developers. |
||||
| 4402 | ID Nodes in CPT file (#81) | File | 1 | 2004/04/22 | APPROVED | Active | Private | 81 | The Code Text Descriptors project modifies the identifier on the SHORT NAME (#2) field in the CPT file (81). The new identifier makes a function call into $$IDCPS^ICPTID to return versioned data for both the SHORT NAME and the status in the INACTIVE FLAG. The function has one input parameter, the Internal Entry Point for file #81. Routine ICPTID will also look to see if the package namespaced variable ICPTVDT is in the environment. ICPTVDT is a versioning date. If ICPTVDT is not found in the environment (not supplied) then TODAY will be used and the SHORT NAME and INACTIVE FLAG for TODAY will be displayed. If the variable ICPTVDT is found in the environment, and is a date other than TODAY, then the appropriate SHORT NAME and INACTIVE FLAG will be displayed for the date. The identifiers will be changed to: ^DD(81,0,"ID",2)= D EN^DDIOL((" "_$$IDCPS^ICPTID(+Y)),"","?0") D:$D(SRSITE) ^SROCPT This will be exported in the combined build CTD UTIL 1.0, containing ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30. |
|||
| 4403 | ID Nodes in CPT Modifier file (#81.3) | File | 1 | 2004/04/22 | APPROVED | Active | Private | 81.3 | The Code Text Descriptors project modifies the identifier on the NAME (#.02) field in the CPT Modifier file (81.3). The new identifier makes a function call into $$IDMDS^ICPTID to return versioned data for both the NAME and the status in the INACTIVE FLAG. The function has one input parameter, the Internal Entry Point for file #81.3. Routine ICPTID will also look to see if the package namespaced variable ICPTVDT is in the environment. ICPTVDT is a versioning date. If ICPTVDT is not found in the environment (not supplied) then TODAY will be used and the NAME and INACTIVE FLAG for TODAY will be displayed. If the variable ICPTVDT is found in the environment, and is a date other than TODAY, then the appropriate NAME and INACTIVE FLAG will be displayed for the date. The identifier will be changed to: ^DD(81.3,0,"ID",.02)= D EN^DDIOL((" "_$$IDMDS^ICPTID(+Y)),"","?0") This will be exported in the combined build CTD UTIL 1.0, containing ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30. |
|||
| 4404 | ID Nodes in ICD Dx file (#80) | File | 1 | 2004/04/22 | APPROVED | Active | Private | 80 | The Code Text Descriptors project modifies the identifier on the DIAGNOSIS (#3) field in the ICD DIAGNOSIS file (80). The new identifier makes a function call into $$IDDXS^ICDID to return versioned data for both the DIAGNOSIS and the status in the INACTIVE FLAG. The function has only one input parameter, the Internal Entry Number for file #80. Routine ICDID will also look to see if the package namespaced variable ICDVDT is in the environment. ICDVDT is a versioning date. If ICDVDT is not found in the environment (not supplied) then TODAY will be used and the DIAGNOSIS and INACTIVE FLAG for TODAY will be displayed. If the variable ICDVDT is found in the environment, and is a date other than TODAY, then the appropriate DIAGNOSIS and INACTIVE FLAG will be displayed for the date. The identifier will be changed to: ^DD(80,0,"ID",3)= D EN^DDIOL((" "_$$IDDXS^ICDID(+Y)),"","?0") This will be exported in the combined build CTD UTIL 1.0, containing ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30. |
|||
| 4405 | ID Nodes in ICD OP file (#80.1) | File | 1 | 2004/04/22 | APPROVED | Active | Private | 80.1 | The Code Text Descriptors project modifies the identifier on the OPERATION/PROCEDURE (#4) in the ICD OPERATION/PROCEDURE file (80.1). The new identifier makes a function call into $$IDOPS^ICDID to return versioned data for both the OPERATION/PROCEDURE and the status in the INACTIVE FLAG. The function has only one input parameter, the Internal Entry Number for file #80.1. Routine ICDID will also look to see if the package namespaced variable ICDVDT is in the environment. ICDVDT is a versioning date. If ICDVDT is not found in the environment (not supplied) then TODAY will be used and the OPERATION/PROCEDURE and INACTIVE FLAG for TODAY will be displayed. If the variable ICDVDT is found in the environment, and is a date other than TODAY, then the appropriate OPERATION/PROCEDURE and INACTIVE FLAG will be displayed for the date. The identifiers will be changed to: ^DD(80.1,0,"ID",4)= D EN^DDIOL((" "_$$IDOPS^ICDID(+Y)),"","?0") This will be exported in the combined build CTD UTIL 1.0, containing ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30. |
|||
| 4406 | ID Nodes in DRG file (#80.2) | File | 1 | 2004/04/22 | APPROVED | Active | Private | 80.2 | The Code Text Descriptors project modifies the identifier on the INACTIVE (#15) field of the DRG file (80.2). The new identifier makes a function call into $$IDDGS^ICDID to return versioned data for both the DESCRIPTION and the status in the INACTIVE field. The function has only one input parameter, the Internal Entry Number for file #80.2. Routine ICDID will also look to see if the package namespaced variable ICDVDT is in the environment. ICDVDT is a versioning date. If ICDVDT is not found in the environment (not supplied) then TODAY will be used and the DESCRIPTION and INACTIVE fields for TODAY will be displayed. If the variable ICDVDT is found in the environment, and is a date other than TODAY, then the appropriate DESCRIPTION and INACTIVE fields will be displayed for the date. The identifiers will be changed to: ^DD(80.2,0,"ID",15)= D EN^DDIOL((" "_$$IDDGS^ICDID(+Y)),"","?0") This will be exported in the combined build CTD UTIL 1.0, containing ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30. |
|||
| 4441 | Direct set DD node | File | 1 | 2004/06/29 | APPROVED | Active | Private | Kernel requests permission to directly set ^DD(file,field) from a post-installation routine. The routine will modify the data dictionary definition of the NEW PERSON file (#200). Direct setting of the ^DD global will allow updating the data dictionary definition wihout exporting the field. Directly set $P(^DD(200,.01,0),U,5,99), to call a differnt API to process the input of the Name field. Directly set $P(^DD(200,20.2,0),U,5,99) to update the input transform. Directly set ^DD(200,.01,21, to update the help text of the Name field. |
||||
| 4454 | Direct read of global DD('KWIC' | File | 1 | 2004/07/12 | APPROVED | Active | Supported | This IA covers the ability to read the global node ^DD("KWIC". There is currently no other way to access the string located in this node other than a direct global read. |
||||
| 4468 | VBECS set field level write access file 62.55 | File | 1 | 2004/07/23 | APPROVED | Active | Private | The VistA Blood Establishment Computer Software (VBECS) data conversion application would like to change the write access for specific fields in the AGGLUTINATION STRENGTH FILE (62.55). The fields in question are: .01 - NAME & 1 - WILL STAND FOR. The method to accomplish this task will be to set the write access node for the targeted field to the caret. Example: -------- S ^DD(62.55,.01,9)="^" S ^DD(62.55,1,9)="^" After the VBECS data conversion is run, these fields should not be edited or deleted through the use of VistA Blood Bank application. The hard set of the write access node ('9') will accomplish this goal. |
||||
| 4469 | VBECS set field level write access for file 63 | File | 1 | 2004/07/23 | Withdrawn | Private | The VistA Blood Establishment Computer Software (VBECS) data conversion application would like to change the write access for specific fields in the LAB DATA file (63). The following sub-files and fields will be targeted: ---------------------------------------------------- BLOOD BANK (Multiple-63.01), [BB;0] .01 DATE/TIME SPECIMEN TAKEN (RDX), [0;1] .03 DATE REPORT COMPLETED (RD), [0;3] .04 ENTERING PERSON (P200'), [0;4] .05 SPECIMEN (P61'), [0;5] .055 COLLECTION SAMPLE (RP62'), [0;11] .06 ACCESSION NUMBER (F), [0;6] .07 PHYSICIAN (*P200'X), [0;7] .08 WARD (F), [0;8] .09 PHLEBOTOMIST (P200'), [0;9] .1 DATE/TIME RECEIVED (RDX), [0;10] .12 ACCESSION LINK (FI), [0;12] .99 SPECIMEN COMMENT (Multiple-63.199), [99;0] .01 SPECIMEN COMMENT (MF), [0;1] 2.1 DIRECT AHG(POLYSPECIFIC) (FX), [2;1] 2.2 DIRECT AHG(5 min incub) (FX), [2;2] 2.3 DIRECT AHG CC (FX), [2;3] 2.4 ANTI-IgG (FX), [2;4] 2.5 ANTI-IgG CC (FX), [2;5] 2.6 ANTI-COMPLEMENT (FX), [2;6] 2.7 ANTI-COMPLEMENT (5 min incub) (FX), [2;7] 2.8 ANTI-COMPLEMENT CC (FX), [2;8] 2.9 DIRECT AHG INTERPRETATION (S), [2;9] 2.91 DIRECT AHG TEST COMMENT (FX), [2;10] 3 ELUATE ANTIBODY (Multiple-63.012), [EA;0] .01 ELUATE ANTIBODY (M*P61.3'X), [0;1] 4 SCREEN CELL METHOD (Multiple-63.014), [3;0] .01 SCREEN CELL METHOD (MS), [0;1] .02 TECHNIQUE (S), [0;2] 1 SCREEN CELL (Multiple-63.015), [1;0] .01 SCREEN CELL (MSX), [0;1] .02 SOURCE (P66'), [0;2] .03 INTERPRETATION (S), [0;3] .04 IS (FX), [0;4] .05 37 C (FX), [0;5] .06 AHG (FX), [0;6] .07 CONTROL CELL (FX), [0;7] .08 ROOM TEMP (FX), [0;8] .09 12-18 C (FX), [0;9] .1 4 C (FX), [0;10] 6 ANTIBODY SCREEN INTERPRETATION (S), [6;1] 6.1 RBC ANTIGEN PRESENT (Multiple-63.011), [1.1;0] .01 RBC ANTIGEN PRESENT (M*P61.3'X), [0;1] .02 COMMENT (F), [0;2] 6.2 RBC ANTIGEN ABSENT (Multiple-63.0112), [1.2;0] .01 RBC ANTIGEN ABSENT (M*P61.3'X), [0;1] .02 COMMENT (F), [0;2] 6.3 HLA ANTIGEN PRESENT (Multiple-63.013), [1.3;0] .01 HLA ANTIGEN PRESENT (M*P61.3'X), [0;1] .02 COMMENT (F), [0;2] 6.4 HLA ANTIGEN ABSENT (Multiple-63.0114), [1.4;0] .01 HLA ANTIGEN ABSENT (M*P61.3'X), [0;1] .02 COMMENT (F), [0;2] 7 SERUM ANTIBODY (Multiple-63.46), [5;0] .01 SERUM ANTIBODY (M*P61.3'X), [0;1] .02 ANTIBODY COMMENT (F), [0;2] 8 ANTIBODY SCREEN COMMENT (Multiple-63.48), [4;0] .01 ANTIBODY SCREEN COMMENT (MFX), [0;1] 9 RBC TYPING METHOD (Multiple-63.018), [1;0] .01 RBC TYPING METHOD (S), [0;1] .02 TECHNIQUE (S), [0;2] 1 ANTISERUM (Multiple-63.019), [1;0] .01 ANTISERUM (M*P66'), [0;1] .02 LOT # (F), [0;2] .03 INTERPRETATION (RS), [0;3] .04 IS (FX), [0;4] .05 37 C (FX), [0;5] .06 AHG (FX), [0;6] .07 CONTROL CELL (FX), [0;7] .08 ROOM TEMP (FX), [0;8] .09 12-18 C (FX), [0;9] .1 4 C (FX), [0;10] 121 PT CELLS+ANTI D (sal) (FX), [12;1] 122 PT CELLS+RH CTRL (sal) (FX), [12;2] 123 PT CELLS(sal)+ANTI D(hp IS) (FX), [12;3] 124 PT CELLS(ser)+ANTI D(hp IS) (RFX), [12;4] 125 PT CELLS+ANTI D (hp 37) (FX), [12;5] 126 PT CELLS+ANTI D (hp AHG) (FX), [12;6] 127 PT CELLS+ANTI D SLIDE (hp) (S), [12;7] 128 PT CELLS(sal)+RH CTRL (hp IS) (FX), [12;8] 129 PT CELLS(ser)+RH CTRL(hp IS) (RFX), [12;9] 129.1PT CELLS+RH CTRL (hp 37) (FX), [12;10] 129.11PT CELLS+RH CTRL (hp AHG) (FX), [12;11] 129.12PT CELLS+RH CTRL SLIDE (hp) (S), [12;12] 131 INTERPRETATION OF RH TESTING (RS), [13;1] 132 RH TEST COMMENT (F), [13;2] |
|||||
| 4475 | Code Set DD Fixes | File | 1 | 2006/01/25 | APPROVED | Active | Private | During the SQA of patch LEX*2.0*39, several anomalies were discovered with the Lexicon, CPT and ICD data files stemming from the Code Set Versioning and Code Text Descriptors projects. There were several identical fields identified by the cross-references, and a field that points to a non-existing file. Rather than delete the DD and refresh it, potentially wiping out local mods, the Lexicon team is requesting a one-time permission to write and delete directly from the Data Dictionary. The code is as follows: 1 File #757.28, Index "ACT" has duplicate Fields Field .01 ACTIVATION EFFECTIVE DATE Field 1 ACTIVATION STATUS S ^DD(757.02,1,1,2,0)="757.02^ACT1^MUMPS" S ^DD(757.28,.01,1,2,0)="757.02^ACT2^MUMPS" S ^DD(757.28,1,1,1,0)="757.02^ACT3^MUMPS" K ^DD(757.02,0,"IX","ACT",757.02,1) K ^DD(757.02,0,"IX","ACT",757.28,.01) K ^DD(757.02,0,"IX","ACT",757.28,1) S ^DD(757.02,0,"IX","ACT1",757.02,1)="" S ^DD(757.02,0,"IX","ACT2",757.28,.01)="" S ^DD(757.02,0,"IX","ACT3",757.28,1)="" 2 File #757.02, Index "APCODE" has duplicate Fields Field 1 EXPRESSION Field 4 PREFERENCE FLAG S ^DD(757.02,1,1,4,0)="757.02^APCODE1^MUMPS" S ^DD(757.02,4,1,1,0)="757.02^APCODE2^MUMPS" K ^DD(757.02,0,"IX","APCODE",757.02,1) K ^DD(757.02,0,"IX","APCODE",757.02,4) S ^DD(757.02,0,"IX","APCODE1",757.02,1)="" S ^DD(757.02,0,"IX","APCODE2",757.02,4)="" 3 File #81.02, Index "ACT" has duplicate Fields Field .01 EFFECTIVE DATE Field .02 STATUS S ^DD(81,.01,1,5,0)="81^ACT1^MUMPS" S ^DD(81.02,.01,1,2,0)="81^ACT2^MUMPS" S ^DD(81.02,.02,1,1,0)="81^ACT3^MUMPS" K ^DD(81,0,"IX","ACT",81,.01) K ^DD(81,0,"IX","ACT",81.02,.01) K ^DD(81,0,"IX","ACT",81.02,.02) S ^DD(81,0,"IX","ACT1",81,.01)="" S ^DD(81,0,"IX","ACT2",81.02,.01)="" S ^DD(81,0,"IX","ACT3",81.02,.02)="" 4 File #81.33, Index "ACT" has duplicate Fields Field .01 EFFECTIVE DATE Field .02 STATUS S ^DD(81.3,.01,1,3,0)="81.3^ACT1^MUMPS" S ^DD(81.33,.01,1,2,0)="81.3^ACT2^MUMPS" S ^DD(81.33,.02,1,1,0)="81.3^ACT3^MUMPS" K ^DD(81.3,0,"IX","ACT",81.3,.01) K ^DD(81.3,0,"IX","ACT",81.33,.01) K ^DD(81.3,0,"IX","ACT",81.33,.02) S ^DD(81.3,0,"IX","ACT1",81.3,.01)="" S ^DD(81.3,0,"IX","ACT2",81.33,.01)="" S ^DD(81.3,0,"IX","ACT3",81.33,.02)="" 5 File #80.066, Index "ACT" has duplicate Fields Field .01 EFFECTIVE DATE Field .02 STATUS S ^DD(80,.01,1,4,0)="80^ACT1^MUMPS" S ^DD(80.066,.01,1,2,0)="80^ACT2^MUMPS" S ^DD(80.066,.02,1,1,0)="80^ACT3^MUMPS" K ^DD(80,0,"IX","ACT",80,.01) K ^DD(80,0,"IX","ACT",80.066,.01) K ^DD(80,0,"IX","ACT",80.066,.02) S ^DD(80,0,"IX","ACT1",80,.01)="" S ^DD(80,0,"IX","ACT2",80.066,.01)="" S ^DD(80,0,"IX","ACT3",80.066,.02)="" |
||||
| 4494 | MODIFY 'B' XREF OF 757.01 | File | 1 | 2007/04/03 | APPROVED | Active | Private | 757.01 | The FM team grants the request of the Clinical Lexicon package to modify the "B" index of file 757.01 as follows: S ^LEX(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA)="" K ^LEX(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA) It is further agreed that the following tools will not be used with this file: DIFROM, COMPARE/MERGE and TRANSFER. These tools rely on an unmodified 'B' index to function properly. Using the modified 'B' index of file 757.01 along with any of the named tools may produce unexpected results. |
2007/04/03 | ||
| 4507 | DBIA4507 | File | 1 | 2004/09/24 | APPROVED | Active | Private | 1 | This IA documents that the CP Conversion file (#703.9) has a multiple field, MEDICINE FILE PARAMETERS (#703.91). The MEDICINE FILE PARAMETERS field (#.01) points to the FILE file (#1). This multiple field is used to store the pointer to the Medicine files so CP can store parameters for each Medicine files used for the medicine report conversion. The CP Conversion file (#703.9) will be added with patch MD*1*5. The files that will be used belong to the CP namespace. CP will screen for CP namespace files and populate this multiple. LAYGO will not be allowed. The following are files that will be used: 691 ECHO 691.1 CARDIAC CATHETERIZATION 691.5 ELECTROCARDIOGRAM (EKG) 691.6 HOLTER 691.7 EXERCISE TOLERANCE TEST 691.8 ELECTROPHYSIOLOGY (EP) 694 HEMATOLOGY 694.5 CARDIAC SURGERY RISK ASSESSMENT 698 GENERATOR IMPLANT 698.1 V LEAD IMPLANT 698.2 A LEAD IMPLANT 698.3 PACEMAKER SURVEILLANCE 699 ENDOSCOPY/CONSULT 699.5 GENERALIZED PROCEDURE/CONSULT 700 PULMONARY FUNCTION TESTS 701 RHEUMATOLOGY |
|||
| 4542 | DD Nodes in Patient (#2) file | File | 1 | 2006/04/13 | APPROVED | Active | Private | 2 | DG*5.3*705, FIX PATIENT FILE DATA DICTIONARY, deletes Fileman DD entries for fields on the PATIENT file (#2). The pre-init routine, DG53705I, will be run only once and it will delete the following nodes: D BMES^XPDUTL(">>> Deleting bad write access, help, audit, other miscel laneous nodes") K ^DD(2,.12113,9),^DD(2,.14112,9) K ^DD(2,.108,3) K ^DD(2,.391,4) F Z=.01,.2924,.3111,.3192,991.07 K ^DD(2,Z,"AUDIT") K ^DD(2.312,.18,"AUDIT") K ^DIC(2,0,"AUDIT") K ^DD(2,0,"VR") K ^DD(2,0,"VRPK") K ^DIC(2,"%",7,0) K ^DIC(2,"%","B","QAM",7) D PT^DDUCHK1 (">>> Deleting bad pointer nodes") (this deletes any "PT" reference node whose file and field either don't exist or don't point to file 2) D BMES^XPDUTL(">>> Deleting bad identifier nodes") F Z=.2924,.302,.351,"GARB","WARD","WR","ZREW" K ^DD(2,0,"ID",Z) D BMES^XPDUTL(">>> Deleting bad field description nodes") S Z=1 F S Z=$O(^DD(2,.107,21,Z)) Q:'Z K ^DD(2,.107,21,Z,0) D BMES^XPDUTL(">>> Deleting bad cross reference nodes") ^DD(2,0,"IX","AHL",.01) ^DD(2,0,"IX",AHL2",.02) ^DD(2,0,"IX","AHL3",.03) ^DD(2,0,"IX","AHL5",.06) ^DD(2,0,"IX","AHL4",.09) ^DD(2,0,"IX","A4EC",.102) ^DD(2,0,"IX","ACP",.302) ^DD(2,0,"IX","AP",.302) ^DD(2,0,"IX","CHK4",.3025) ^DD(2,0,"IX","AEMP",.31115) ^DD(2,0,"IX","MAC",.31115) ^DD (2,0,"IX","AI",.32102) ^DD(2,0,"IX","AK",.32103) ^DD(2,0,"IX","AEXP",.351) ^DD(2,0,"IX","AHL6",.351) ^DD(2,0,"IX","AT",.351) ^DD(2,0,"IX","AR",.361) ^DD(2,0,"IX","BEN",.36205) ^DD(2,0,"IX","CHK1",.36205) ^DD(2,0,"IX","CHK2,".36215) ^DD(2,0,"IX","CHK3",.36235) ^DD(2,0,"IX","AT",.381) |
|||
| 4577 | DIC(0) | Other | 1 | 2004/12/14 | APPROVED | Active | Controlled Subscription | FileMan determines if it can "talk" to the user if the variable DIC(0) contains the letter "E". |
||||
| 4578 | DINDEX | Other | 1 | 2004/12/14 | APPROVED | Active | Controlled Subscription | When DIC is being used to search the indexes for user matches, the local variable DINDEX reflects the current index that is being searched. |
||||
| 4579 | DD(200,0,'SCR') | File | 1 | 2004/12/15 | APPROVED | Active | Private | 200 | This is a one time IA for patch XU*8*373 to set the whole file screen code. The patch code is as follows: XU8P373 ;SFISC/SO- Add Whole File Screen to file 200 ;5:50 AM 13 Dec 2004 ;;8.0;KERNEL;**373**;Jul 10, 1995 ; IA # 4579 ; Test for file header node I '$D(^VA(200,0))#2 D MES^XPDUTL("NEW PERSON(#200) file is mis sing it's File Header node.") Q ; Test header node $P#2 for proper construction I +$P(^VA(200,0),U,2)'=200 D MES^XPDUTL("The second piece of N EW PERSON(#200) file is not correct.") Q ; Add the Whole File Screen S ^DD(200,0,"SCR")="I $$SCR200^XUSER" ; Add Screen flag to file header if not already there I $P(^VA(200,0),U,2)'["s" S $P(^VA(200,0),U,2)=$P(^VA(200,0),U ,2)_"s" ; D MES^XPDUTL("Added Screen to NEW PERSON(#200) file.") Q |
|||
| 4605 | GLOBAL READ OF DD(123 | File | 1 | 2005/02/08 | APPROVED | Active | Private | GMRC*3*41 proposes to delete 3 MUMPS style cross-references and replace them with a NEW-STYLE compound index. This approach should increase the efficiency and reliability of the cross-reference. To insure the deletion of the proper cross-references "AE", "AE1" and "AE2", Consult/Request Tracking will loop through: ^DD(123,1,1, ^DD(123,3,1, ^DD(123,8,1, in order to locate the number of the cross reference to delete via DELIX^DDMOD. |
||||
| 4634 | Data Dictionary global access | File | 1 | 2005/03/07 | APPROVED | Active | Private | to request the reading of the ^DD global to quickly search for files that are "VUID-enhanced." Users of the new VUID Kernel-Toolkin api have a subroutine to search for terms/concepts when given the VUID # and some filter parameters. When the "file" filter is not defined, the search must quickly look into every VistA file to look for the term. |
||||
| 4754 | SETTING DD('IX') | File | 1 | 2014/10/02 | APPROVED | Active | Private | 8925 | Text Integration Utilities (TIU) requests permission to directly set the ^DD("IX",DA,"NOREINDEX") node in a post-init. DIKCBLD is used to create the post-init routine that will install the new index, but the new NOREINDEX flag is not being picked up yet by this utility, and CREIXN^DDMOD does not currently accept the NOREINDEX designator as part of its input array. This is a one-time request for patch TIU*1*106. |
VPRVIT | 2014/11/04 | |
| 4768 | DIRECT DD ACCESS TO SUBFILE 'NM' node | File | 1 | 2010/12/15 | APPROVED | Active | Controlled Subscription | The LAB SERVICE package (LSRP project) needs to access the name of the sub-file, given its subfile number. We would like to access this via direct ^DD global read of the 'NM' node: S NAME=$O(^DD(subfile#,0,"NM","")) |
2010/12/15 | |||
| 4778 | DICRW | Routine | 1 | 2005/08/16 | APPROVED | Active | Controlled Subscription | Make sure DT and other VA FileMan variables are set without the need to set DIQUIET. |
DICRW | |||
| 4806 | ADD TEMPLATES TO AUDIT FILE | File | 1 | 2010/12/20 | APPROVED | Active | Controlled Subscription | 1.1 | LAB SERVICE has been approved to add a sort and two print templates to the AUDIT file (#1.1) to print/display audited entries. The templates are: Sort template: LRJ SYS DISPLAY FILE 60 CHANGE Print template: LRJ SYS DISPLAY FILE 60 CHANGE Print Template: LRJ SYS GET INDIRECT AUDIT They both run off the LABORATORY TEST file (#60) |
2013/06/04 | ||
| 4816 | DD Nodes for files 5, SUB-FILE 5.01, 5.12, & 5.13 | File | 1 | 2005/10/24 | APPROVED | Active | Private | This will be a one time agrement for patch XU*8*378 to se the following nodes: Routine: XU8P378 ; Set current C xrefs in 5 to Q S ^DD(5,1,1,1,1)="Q" S ^DD(5,1,1,1,2)="Q" S ^DD(5,1,1,1,3)="Used in conjunction with the 'ADUALC' xref." S ^DD(5,1,"DT")=$G(DT) S ^DD(5,2,1,1,1)="Q" S ^DD(5,2,1,1,2)="Q" S ^DD(5,2,1,1,3)="Used in conjunction with the 'ADUALC' xref." S ^DD(5,2,"DT")=$G(DT) Routine: XU8P378C ; Set DEL & LAYGO nodes for file 5 S ^DD(5,.01,"DEL",1,0)="D EN^DDIOL(""Deletions are not allowed."","""", ""!?5,$C(7)"") I 1" S ^DD(5,.01,"LAYGO",1,0)="D EN^DDIOL(""New State additions are not allowed."","""",""!?5,$C(7)"") I 0" S ^DD(5,.01,"DT")=$G(DT) ; ; Set DEL & LAYGO nodes for sub-file 5.01 S ^DD(5.01,.01,"DEL",1,0)="D EN^DDIOL(""Entries can only be Inactivated."","""",""!?5,$C(7)"") I 1" S ^DD(5.01,.01,"LAYGO",1,0)="D EN^DDIOL(""New County additions are not allowed."","""",""!?5,$C(7)"") I 0" S ^DD(5,.01,"DT")=$G(DT) ; ; Set DEL node for file 5.12 S ^DD(5.12,.01,"DEL",1,0)="D EN^DDIOL(""Entries can only be Inactivated."","""",""!?5,$C(7)"") I 1" S ^DD(5.12,.01,"DT")=$G(DT) ; ; Set Del & LAYGO nodes for file 5.13 S ^DD(5.13,.01,"DEL",1,0)="D EN^DDIOL(""Entries can only be Inactivated."","""",""!?5,$C(7)"") I 1" S ^DD(5.13,.01,"LAYGO",1,0)="D EN^DDIOL(""New County Code additions are not allowed."","""",""!?5,$C(7)"") I 0" S ^DD(5.13,.01,"DT")=$G(DT) |
||||
| 4870 | FILE 442 AND 443.6 FCPFIELD FIX FILE DD | File | 1 | 2011/01/04 | APPROVED | Active | Private | 443.6 | This is a one time aggreement via patch PRC*5.1*128. Kill node 9 from following field DD definition: ^DD(443.61,8,0)=FEDERAL SUPPLY CLASSIFICATION^RP441.2'X^PRC(441.2,^2;3^D EN100^PRCHNPO7 .1)=FSC/PSC ^DD(443.61,8,1,0)=^.1 ^DD(443.61,8,1,1,0)=443.61^AU^MUMPS 1)=I $G(PRCHNORE)=1 D:PRCHAMDA=21 EN1^PRCHAMXG Q:PRCHAMDA=21 D FLAG^PRCHMA Q:$T I PRCHAMDA=23 S PRCHX=X,X=0 D EN1^PRCHAMXD S X=PRCHX K PRCHX 2)=I $G(PRCHNORE)=1,PRCHAMDA=23 S FLAG=1 D EN1^PRCHAMXD ^DD(443.61,8,1,1,"%D",0)=^^5^5^2970416^^^^ ^DD(443.61,8,1,1,"%D",1,0)=This x-ref will update the CHANGES multiple whenever a 'Line Item Add' or a ^DD(443.61,8,1,1,"%D",2,0)='Line Item Edit' amendment changes this field. ^DD(443.61,8,1,1,"%D",3,0)= ^DD(443.61,8,1,1,"%D",4,0)=****NOTE-See routine PRCHAMXA for information on variable PRCHNORE and ^DD(443.61,8,1,1,"%D",5,0)=incidence of undefined DIK variable errors. ^DD(443.61,8,1,1,"DT")=2950321 ^DD(443.61,8,3)= 9)=^ <<<=========== kill this field ^DD(443.61,8,21,0)=^.001^2^2^3050909^^^^ ^DD(443.61,8,21,1,0)=This is the Federal Supply Classification for an item, or the Product ^DD(443.61,8,21,2,0)=Service Code for a service. ^DD(443.61,8,"DT")=3050909 Global ^DD(442.01,8 -- NOTE: translation in effect ^DD(442.01,8,0)=FEDERAL SUPPLY CLASSIFICATION^RP441.2'X^PRC(441.2,^2;3^D EN10^PRCHNPO7 .1)=FSC/PSC 3)=ANSWER MUST BE 1-24 CHARACTERS IN LENGTH 9)=^ <<<=========== kill this field ^DD(442.01,8,21,0)=^^2^2^3050809^ ^DD(442.01,8,21,1,0)=This is the Federal Supply Classification for an item, or the Product ^DD(442.01,8,21,2,0)=Service Code for a service. ^DD(442.01,8,"DT")=3050809 |
2011/01/10 | ||
| 4896 | CPT CATEGORY FILE 81.1 'B' CROSS REFERENCE | File | 1 | 2007/04/04 | APPROVED | Active | Private | 81.1 | The "B" cross-reference for the CPT Modifier file 81.1 needs to be extended to the maximum 63 characters to ensure uniqueness in the index. This file is pointed to only by the CPT file 81 and itself. New Set/Kill logic: S ^DIC(81.1,"B",$E(X,1,63),DA)="" K ^DIC(81.1,"B",$E(X,1,63),DA) |
2007/04/04 | ||
| 4909 | DILOCKTM | Other | 1 | 2006/09/27 | APPROVED | Active | Controlled Subscription | Access to the ^DD("DILOCKTM") global and the setting of the DILOCKTM variable. |
||||
| 4923 | Global DD sets to New Person (#200) file | File | 1 | 2006/10/23 | APPROVED | Active | Private | 200 | Person Services is setting the following DD nodes for the VPID (#9000) field in the New Person (#200) file in a post init routine: ^DD(200,9000,0)="VPID^F^^VPID;1^K:$L(X)>29!($L(X)<23) X" ^DD(200,9000,3)="Answer must be 23-29 characters in length." ^DD(200,9000,"DT")=DT |
|||
| 4986 | Temporary DBIA for use of TT in %DTC by VistA Imaging | Routine | 1 | 2007/05/04 | Pending | Supported | The purpose of this DBIA is to allow VistA Imaging to continue using the entry point TT^%DTC (convert $H-date into FileMan date) until a patch is released that replaces all subroutine calls in Imaging software that are currently to entry points in ^%DTC to be references to function-calls to entry points in XLFDT. It is expected that this patch will be released before the end of 2007. |
%DTC | ||||
| 4993 | TIU DOCUMENT DEFINITION FILE 8925.1 'B' CROSS-REFERENCE | File | 1 | 2007/05/23 | APPROVED | Active | Private | The "B" cross-reference for the TIU Document Definition file (#8925.1) needs to be extended to 60 characters to ensure uniqueness in the index. This file is pointed to by the TIU Document file (#8925), the HEALTH SUMMARY Type file (#142), and the FUNCTIONAL INDEPENDENCE Measurement Parameter file (#783.9). Revised Set/Kill Logic: S ^TIU(8925.1,"B",$E(X,1,60),DA)="" K ^TIU(8925.1,"B",$E(X,1,60),DA) |
2007/09/19 | |||
| 4994 | TIU VHA ENTERPRISE STANDARD TITLE file 'B' CROSS REFERENCE | File | 1 | 2007/05/23 | APPROVED | Active | Private | 8926.1 | The "B" cross-reference for the TIU VHA Enterprise Standard Title file (#8926.1) needs to be extended to 90 characters to ensure uniqueness in the index. This file is pointed to by the TIU Document Definition file (#8925.1) only. Revised Set/Kill Logic: S ^TIU(8926.1,"B",$E(X,1,90),DA)="" K ^TIU(8926.1,"B",$E(X,1,90),DA) |
2007/09/19 | ||
| 5002 | INPUT TEMPLATE FOR A MULTIPLE | File | 1 | 2007/06/13 | APPROVED | Active | Controlled Subscription | .402 | VA FileMan does not allow you to use an Input Template exclusively for fields within a multiple. For example, if you know the file top level IEN and you know the sub-file IEN and you want to only present for editing to the user the fields within the sub-file, you cannot do this with a VA FileMan Input Template. |
2009/07/13 | ||
| 5013 | READ ACCESS TO DD FOR FILE 9002313.58 | File | 1 | 2007/07/10 | APPROVED | Active | Private | The ECME application is granted read access to the DD(9002313.58 global in order to $ORDER through the FIELD subscript of the ^DD(9002313.58,FIELD). |
2007/07/12 | |||
| 5015 | READ ACCESS TO DD FOR FILE 9002313.59 | File | 1 | 2007/07/12 | APPROVED | Active | Private | 9002313.59 | The ECME application is granted read access to the DD global in order to $ORDER through the FIELD subscript of the ^DD(9002313.59,FIELD) global. |
2007/07/12 | ||
| 5037 | VISTAWEB/CPRS SURGERY DETAIL ACCESS | File | 1 | 2007/10/24 | Pending | Private | VISTAWEB/CPRS report routines need access to ^DD(130,.04,0 for a formatted surgery report detail, retrieved using classic Fileman API Y^DIQ. |
|||||
| 5038 | LEXICON READ OF DD(D0,0,'IX') | File | 1 | 2007/11/06 | APPROVED | Active | Private | 2007/11/07 | ||||
| 5067 | DD CHECKING AND TRAVERSING | File | 1 | 2008/01/10 | APPROVED | Active | Private | In support of APIs for Data Standardization, Kernel ToolKit is authorized to check a file's DD as follows: I ('$D(^DD(FILE,0,"PT",NEXTFILE,99.97))) Q and $O through a file's DD as follows: S NEXTFILE=+$O(^DD(FILE,0,"PT",NEXTFILE)) |
2008/02/06 | |||
| 5122 | Remove Rad/Nuc Med dd Screen of Sub field #70.15 | File | 1 | 2008/02/07 | Pending | Private | 70 | The Radiology/Nuclear Medicine intends to remove the following Data Dictionary: K ^DD(70.15,.01,12) K ^DD(70.15,.01,12.1) This correction will eliminate the a DIC("S") screen for a drug. Instead of a direct global read to the Pharmacy file #50, an API provided by Pharmacy will be used to check or access a drug. This will be a one-time IA with the installation of patch RA*5.0*65. |
||||
| 5123 | Remove Rad/Nuc Med dd Screen of Sub field #70.21 | File | 1 | 2008/02/08 | Pending | Private | 70 | The Radiology/Nuclear Medicine intends to remove the following Data Dictionary: K ^DD(70.21,.01,12) K ^DD(70.21,.01,12.1) This correction will eliminate the a DIC("S") screen for a drug. Instead of a direct global read to the Pharmacy file #50, an API provided by Pharmacy will be used to check or access a drug. This will be a one-time IA with the installation of patch RA*5.0*65. |
||||
| 5124 | Remove Rad/Nuc Med dd Screen of Sub field #71.055 | File | 1 | 2008/02/08 | Pending | Private | 71 | The Radiology/Nuclear Medicine intends to remove the following Data Dictionary: K ^DD(71.055,.01,12) K ^DD(71.055,.01,12.1) This correction will eliminate the a DIC("S") screen for a drug. Instead of a direct global read to the Pharmacy file #50, an API provided by Pharmacy will be used to check or access a drug. This will be a one-time IA with the installation of patch RA*5.0*65. |
||||
| 5125 | Remove Rad/Nuc Med dd Screen of Sub field #71.08 | File | 1 | 2008/02/08 | Pending | Private | 71 | The Radiology/Nuclear Medicine intends to remove the following Data Dictionary: K ^DD(71.08,.01,12) K ^DD(71.08,.01,12.1) This correction will eliminate the a DIC("S") screen for a drug. Instead of a direct global read to the Pharmacy file #50, an API provided by Pharmacy will be used to check or access a drug. This will be a one-time IA with the installation of patch RA*5.0*65. |
||||
| 5126 | Remove Rad/Nuc Med dd Screen of File 71.9 field #5 | File | 1 | 2008/02/08 | Pending | Private | 71.9 | The Radiology/Nuclear Medicine intends to remove the following Data Dictionary: K ^DD(71.9,5,12) K ^DD(71.9,5,12.1) This correction will eliminate the a DIC("S") screen for a drug. Instead of a direct global read to the Pharmacy file #50, an API provided by Pharmacy will be used to check or access a drug. This will be a one-time IA with the installation of patch RA*5.0*65. |
||||
| 5127 | Set Rad/Nuc Med data dictionary 'ID','WRIT | File | 1 | 2008/02/08 | Pending | Private | 71.9 | Radiology/Nuclear Medicine intends to modify the following data dictionary attribute: K ^DD(71.9,0,"ID",5) S ^DD(71.9,0,"ID","WRITE")="D EN^DDIOL($$EN5^RAPSAPI,"""",""?30"")" Instead of a direct global read to the Pharmacy file #50, an API provided by Pharmacy will be used to check or access a drug. This will be a one-time IA with the installation of patch RA*5.0*65. |
||||
| 5128 | MY PRIVATE | File | 1 | 2008/02/08 | Pending | Private | 70.15 | |||||
| 5131 | IB REMOVE IDENTIFIER DESIGNATION | File | 1 | 2008/02/12 | APPROVED | Active | Private | 355.93 | Integrating Billing (IB) needs to remove the IDENTIFIER label from the .09 field (FACILITY DEFAULT ID NUMBER) in file 355.93 (IB NON/OTHER VA BILLING PROVIDER). This field is not an identifier for this file because this field is only valid for non-VA facilities. The .09 field is not available for non-VA individual providers. This integration agreement exists so we can KILL ^DD(355.93,0,"ID",.09) with IB patch IB*2.0*377. |
2008/03/06 | ||
| 5149 | V Nodes in the DD | File | 1 | 2008/02/20 | APPROVED | Active | Controlled Subscription | This grants direct read access to the "V" nodes of a field's DD. Descendent from the "V" node is information regarding variable pointers including pointed-to file, message, order, prefix, screen, and LAYGO status. ^DD(File#, Field#, "V", n, 0) Where 'n' is a sequential number representing a different pointed-to file. The pieces within this 0 node are: ^-Piece Contents 1 File number of the pointed-to file 2 Message defined for the pointed-to file 3 Order defined for the pointed-to file 4 Prefix defined for the pointed-to file 5 y/n indicating whether a screen is set up for the pointed-to file 6 y/n indicating whether the user may add new entries to the pointed-to file ^DD(File#, Field#, "V", n, 1) contains the M code defined as a screen on the pointer to the file defined in the 0 node above. ^DD(File#, Field#, "V", n, 2) contains a description of the screen. Additionally, the following xrefs exist and may be read and traversed by direct means, too: ^DD(File#, Field#, "V", "B" - xref on ^-Piece 1 of the 0 node. "M" - 2 "O" - 3 "P" - 4 |
2024/03/14 | |||
| 5155 | Remove Rad/Nuc Med dd Screen from Subfield #70.03 | File | 1 | 2008/03/07 | Pending | Private | 70 | The Radiology/Nuclear Medicine application intends to remove the following Data Dictionary node K ^DD(70.03,26,9.2) This correction will eliminate the display warning message for a data screen that no longer exists. This will be a one-time IA with the installation of patch RA*5.0*56. |
||||
| 5156 | Remove Rad/Nuc Med dd Screen from File #79.1 | File | 1 | 2008/03/07 | Pending | Private | 79.1 | The Radiology/Nuclear Medicine application intends to remove the following Data Dictionary node K ^DD(79.1,21,9.2) This correction will eliminate the display warning message for a data screen that no longer exists. This will be a one-time IA with the installation of patch RA*5.0*56. |
||||
| 5163 | USE OF FILEMAN IN ROUTINE DGMTDD | File | 1 | 2008/03/25 | Pending | Private | Routine ^DGMTDD uses a direct global read with ^DD to get the cross-references for the Current Means Test Status field - file #2, field #.14. The code follows: CUR+15 .F S DGIX=$O(^DD(2,.14,1,DGIX)) Q:'DGIX X ^(DGIX,2) S X=DGCS CUR+19 .F S DGIX=$O(^DD(2,.14,1,DGIX)) Q:'DGIX X ^(DGIX,1) S X=DGMTS |
|||||
| 5164 | USE OF FILEMAN IN ROUTINE DGPMDDCN | File | 1 | 2008/03/25 | Pending | Private | Routine ^DGPMDDCN uses a direct global read with ^DD to set and kill cross-references for Patient file (#2) fields. The code follows SET+3 F DGIX=0:0 S DGIX=$O(^DD(2,DGFLD,1,DGIX)) Q:'DGIX X ^(DGIX,1) S X=DGPMX KILL+3 F DGIX=0:0 S DGIX=$O(^DD(2,DGFLD,1,DGIX)) Q:'DGIX X ^(DGIX,2) S X=DGPMX Fields included are: .1 Ward Location .102 Current Movement .013 Treating Specialty .104 Provider .1041 Attending Physician .105 Current Admission .108 Current Room .109 Exclude From Facility |
|||||
| 5200 | REMOVE 'CREATED BY' IDENTIFIER IN FILE 702 | File | 1 | 2008/05/14 | APPROVED | Active | Private | 702 | This DBIA documents the removal of an identifier in the CP Transaction file (#702) for the CREATED BY field (#.03) with a "K ^DD(702,0,ID,.03)" command in a post-init routine. |
2008/07/22 | ||
| 5289 | VA Fileman Option Access | 1 | Withdrawn | |||||||||
| 5378 | ONCOLOGY REMOVE IDENTIFIER DESIGNATION | File | 1 | 2009/03/04 | APPROVED | Active | Private | 164.18 | ONCOLOGY needs to remove the IDENTIFIER label from the 1 field (NSC NUMBER) in file 164.18 (CHEMOTHERAPEUTIC DRUGS). This field has been designated a "Key field" thereby making the IDENTIFIER redundant. This integration agreement exists so we can KILL ^DD(164.18,0,"ID",1) with ONCOLOGY patch ONC*2.11*49. |
2009/03/04 | ||
| 5413 | CPT File 81 Identifier Update | File | 1 | 2009/03/19 | APPROVED | Active | Private | 0 | 2009/03/19 | |||
| 5414 | CPT Modifier File 81.3 Identifier Update | File | 1 | 2009/03/19 | APPROVED | Active | Private | 0 | 2009/03/19 | |||
| 5415 | ICD Diagnosis File 80 Identifier Update | File | 1 | 2009/03/19 | APPROVED | Active | Private | 0 | 2009/04/04 | |||
| 5416 | ICD Procedure File 80.1 Identifier Update | File | 1 | 2009/03/19 | APPROVED | Active | Private | 0 | 2009/03/20 | |||
| 5418 | Set file 78.3 'ID','WRITE' | File | 1 | 2009/03/20 | APPROVED | Active | Private | 78.3 | Radiology/Nuclear Medicine intends to add the following node to file #78.3's Data Dictionary: ^DD(78.3,0,"ID","WRITE")=D EN^DDIOL($$EN1^RABIRAD,"","?33") This will be a one-time IA with the installation of patch RA*5.0*97. |
2009/03/22 | ||
| 5419 | Insert 'I' in file 78.3 header node | File | 1 | 2009/03/20 | APPROVED | Active | Private | 78.3 | Radiology/Nuclear Medicine intends to insert an "I" after the file number in the second piece of File 78.3's header node. Here are the "before" and "after" from a development account: "before": ^RA(78.3,0)=DIAGNOSTIC CODES^78.3^77^30 "after": ^RA(78.3,0)=DIAGNOSTIC CODES^78.3I^77^30 This will be a one-time IA with the installation of patch RA*5.0*97. |
2009/03/22 | ||
| 5452 | FILE 604 X-REFERENCE CLEAN UP | File | 1 | 2009/05/14 | APPROVED | Active | Private | 604 | This IA is for cleaning up the x-references from a faulty deletion of a field in file #604. Patch YS*5.01*100 will be used to run the post-init routine YS501100 which does the following: K ^DD(604,"B","PROGRESS NOTE POINTER",.53) and K ^DD(604,"GL",.5,3,.53) |
2009/06/02 | ||
| 5550 | VALIDATE FIELDS ON DD FOR REGULAR CROSS REFERENCES | File | 1 | 2010/08/16 | Other | Private | Read-only access for the ^DD( Global Read ^DD(filenum,"IX",fieldnum) to determine whether a field contains a regular cross reference, to optimize ad hoc searches. |
MAGVRS42 | 2010/08/17 | |||
| 5551 | RETRIEVE ALL FIELDS IN A FILE | File | 1 | 2010/08/19 | Pending | Private | Read-only access for the ^DD( global Read ^DD(FN,"B",FLDNAME,FLDN), where FN is a file number, FLDNAME is a field name, and FLDN is a field number. A function will be created to loop through ^DD(FN,"B",FLDNAME,FLDN) to create a list with all fields in a file. |
|||||
| 5552 | IFCAP SET DD NODES DURING POST INSTALL | File | 1 | 2010/08/24 | APPROVED | Active | Private | IFCAP needs to add ID nodes to files 410, 442, and 443.6 in support of patch PRC*5.1*146. As KIDS does not have a mechanism to transport ID nodes of a files DD without exporting the entire file definition, it is requested that for this patch IFCAP be permitted to set the ID node via the post-init routine PRC5146P. The proposed lines of code are as follows (without blank lines): S ^DD(410,0,"ID","Z3")="D:$P($G(^(14)),U,2)]"""" EN^DDIOL(""Maximo""_$P(^( 14),U,3)_""-""_$P(^(14),U,2),,""?0""),EN^DDIOL("" "",,""!?2"")" S ^DD(410.02,0,"ID","Z2")="D:$P($G(@(DIC_+Y_"",9)"")),U,2)]"""" EN^DDIOL(" "Maximo PR Line# ""_$P(^(9),U,2),,""!"")" S ^DD(442,0,"ID","Z.04")="N PRCZZ S PRCZZ=$$MAX^PRCMOUTL(+Y,442) D:PRCZZ]" """ EN^DDIOL("" ""_PRCZZ,,""?0"")" S ^DD(442.01,0,"ID","Z4")="N PRCZZ S PRCZZ=$$PRLINE^PRCMOUTL(D0,+Y,442) D: PRCZZ]"""" EN^DDIOL(PRCZZ,,""!,?9"")" S ^DD(443.6,0,"ID","Z.6")="N PRCZZ S PRCZZ=$$MAX^PRCMOUTL(+Y,443.6) D:PRCZ Z]"""" EN^DDIOL("" ""_PRCZZ,,""?0"")" S ^DD(443.61,0,"ID","Z2")="N PRCZZ S PRCZZ=$$PRLINE^PRCMOUTL(DA(1),+Y,443. 6) D:PRCZZ]"""" EN^DDIOL(PRCZZ,,""!,?9"")" |
2010/08/26 | |||
| 5692 | FIX TO OVERLENGTH NODE IN FILE 162 | File | 1 | 2011/06/30 | Withdrawn | Private | 162.03 | In 2004 a change was made to the FEE BASIS PAYMENT file (#162) which caused the node ^FBAAC(D3,1,D2,1,D1,1,DA,0) to exceed the maximum length allowed by the SACC. The Fee Basis patch FB*3.5*108 will also need to make changes to the Fee BASIS PAYMENT file (#162). These changes cannot be made with the node in its current length. During the pre-install for patch FB*3.5*108 the pre-install routine needs to make changes to the DD global to move 3 fields from the 0 node to the 2 node in order to make the 0 node of such a length the required changes can be made. |
||||
| 5705 | FILE 410 DESCRIPTION UPDATE | File | 1 | 2011/08/08 | APPROVED | Active | Private | 410 | Add to end of file 410 description the wording: *******DO NOT RE-INDEX THIS FILE******* per instructions from national support as re-indexing has been causing site errors. One time agreement in patch PRC*5.1*157. Post install routine PRC157P will add file description node in file global ^DIC: ^DIC(410,"%D",7,0)=" *********DO NOT RE-INDEX THIS FILE**********" |
2011/08/08 | ||
| 5706 | FILE 442 DESCRIPTION UPDATE | File | 1 | 2011/08/08 | APPROVED | Active | Private | 442 | Add to end of file 442 description the wording: *******DO NOT RE-INDEX THIS FILE******* per instructions from national support as re-indexing has been causing site errors. One time agreement in patch PRC*5.1*157. Post install routine PRC157P will add file description node in file global ^DIC: ^DIC(442,"%D",5,0)=" *********DO NOT RE-INDEX THIS FILE**********" |
2011/08/08 | ||
| 5707 | FILE 443.6 DESCRIPTION UPDATE | File | 1 | 2011/08/08 | APPROVED | Active | Private | 443.6 | Add to end of file 443.6 description the wording: *******DO NOT RE-INDEX THIS FILE******* per instructions from national support as re-indexing has been causing site errors. One time agreement in patch PRC*5.1*157. Post install routine PRC157P will add file description node in file global ^DIC: ^DIC(443.6,"%D",7,0)=" *********DO NOT RE-INDEX THIS FILE**********" |
2011/08/08 | ||
| 5746 | USE SCREENMAN DDS VARIABLE | Other | 1 | 2011/11/04 | APPROVED | Active | Controlled Subscription | The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable. In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before invoking the Browser. In summary, this ICR allows the application to read, kill, set, and NEW the DDS variable. Note that if List Manager is being invoked from ScreenMan the following Kernel calls should be made to restore the terminal settings required by ScreenMan before calling REFRESH^DDSUTL. N IOAWMO,X S X=0 X ^%ZOSF("RM"),^%ZOSF("TYPE-AHEAD") S X="IOAWM0" D ENDR^%ZISS W IOAWM0 If this is not done the ScreenMan display will be corrupted. |
2012/03/20 | |||
| 5749 | Updating DD 'VR' Nodes | File | 1 | 2011/11/30 | APPROVED | Active | Private | 2011/12/07 | ||||
| 5789 | Remove PROCEDURE field (#2006.5841,1) as identifier | File | 1 | 2012/04/13 | Withdrawn | Private | 2006.584 | IMAGING to remove PROCEDURE field (#2006.5841,1) as identifier: K ^DD(2006.5841,0,"ID",1) There currently is no other way to remove a field as an identifier. |
||||
| 5819 | IFCAP SET ID NODES DURING POST INSTALL | File | 1 | 2012/06/28 | APPROVED | Active | Private | IFCAP needs to add ID nodes to the Control Point Activity file (#410) at the header (#410) and at the Item subfile (#410.02) level in support of patch PRC*5.1*167 (eCMS Interface to IFCAP - Phase 1). As KIDS does not have a mechanism to transport ID nodes of a file's Data Dictionary without exporting the entire file definition, it is requested that for this patch IFCAP be permitted to set the ID nodes via the post-int routine PRC5167P. The proposed lines of code are as follows (without blank lines): S ^DD(410,0,"ID","Z3")="D:$P($G(^(1)),U,8)]"""" EN^DDIOL(""Sent to eCMS"",,""?0""),EN^DDIOL("" "",,""!?2"")" S ^DD(410.02,0,"ID","Z2")="D:$P($G(@(DIC_+Y_"",4)"")),U,3)]"""" EN^DDIOL(""eCMS Item Line ID ""_$P(^(4),U,3),,""!?10"")" |
2012/07/02 | |||
| 5846 | Clear ScreenMan Help Area | Routine | 1 | 2012/09/28 | APPROVED | Active | Controlled Subscription | DDS | 2012/11/05 | |||
| 5847 | Write to ScreenMan Help Area | Routine | 1 | 2012/09/28 | APPROVED | Active | Controlled Subscription | DDSMSG | 2012/11/05 | |||
| 5895 | PSS*1*174 POST INSTALL WITH DD(52.6 | File | 1 | 2013/01/25 | APPROVED | Active | Private | This is a one-time ICR valid only for the Post-Install Routine for patch PSS*1.0*174. A new field STRENGTH (#19) has been added to the IV ADDITIVES File (#52.6). The new STRENGTH (#19) field will be displayed on any lookup performed on the IV ADDITIVES File (#52.6) by creating a new "W19" node by direct global set into ^DD(52.6,0,"ID" by Post-Install Routine PSS0174. ^DD(52.6,0,"ID","W19") will be set to "W "" Additive Strength: "",$S($P(^(0),U,15)="""":""N/A"", 1:$P(^(0),U,15)_"" ""_$$GET1^DIQ(52.6,$P(^(0),U,3)_"","",2))" |
2013/02/04 | |||
| 5906 | RESTRICT IV FLAG WRITE ACCESS | File | 1 | 2013/03/26 | APPROVED | Active | Private | 50.7 | This request is to allow the Pharmacy Data Management package to edit the IV FLAG field to restrict write access from Fileman. This change will be used in patch PSS*1.0*150 only. |
|||
| 5907 | DELETE FIELD 64 FROM FILE 399 | File | 1 | 2013/03/26 | APPROVED | Active | Private | 399 | This agreement is to make a fileman call to delete the ICD DIAGNOSIS CODE field (#64) from the BILL/CLAIMS file (#399). This agreement is only for patch IB*2.0*481. |
2013/03/26 | ||
| 5924 | DESCRIPTION UPDATE FOR 627.8 FILE | File | 1 | 2013/05/16 | APPROVED | Active | Private | 627.8 | Important Note: This is a One-Time Agreement, just for Patch YS*5.01*107. Update of DESCRIPTION for File (#627.8) which is the DIAGNOSTIC RESULTS - MENTAL HEALTH File to replace occurrences of 'ICD9' to 'ICD DIAGNOSIS' to accommodate ICD-10 Remediation project for Patch YS*5.01*107. DESCRIPTION will be updated using Post-Init routine YS107P. Routine YS107P directly sets nodes in the File Description for File (#627.8). End result should be as below: ^DIC(627.8,"%D",7,0)="""AE"" Xref - Type (DSM or ICD DIAGNOSIS), DFN, System Dte, Dx, DFN." ^DIC(627.8,"%D",13,0)="""AG"" Xref - Type (DSM or ICD DIAGNOSIS), DFN, Dx, IFN." |
2013/05/23 | ||
| 5927 | EDIS POINTING TO FILE 1 | File | 1 | 2013/06/05 | APPROVED | Active | Private | 1 | The Adhoc worksheets and reports portions of EDIS requests approval to point to the file of files (File #1). EDIS will only point to files that belong to EDIS. This is to be used for building calls to File Manager API's dynamically. |
2013/07/02 | ||
| 5993 | RTLS POINTING TO FILE 1 | File | 1 | 2013/07/23 | APPROVED | Active | Private | 1 | The Real Time Location System (RTLS) is requesting approval to point to the file of files (#1), field FILE ID (#1), in the PENDING RTLS EVENTS file (#6930). This is to be used for building calls to File Manager API'S dynamically. |
2014/06/30 | ||
| 6018 | DESCRIPTION UPDATE FOR 9999999.17 FILE | File | 1 | 2013/10/09 | Retired | Private | 9999999.17 | Important Note: This is a One-Time Agreement, just for Patch PX*1.0*199. Update of DESCRIPTION for File (#9999999.17) which is the TREATMENT File to replace occurrences of 'ICD-9-CM' to 'ICD-CM' to accommodate ICD-10 Remediation project for Patch PX*1.0*199. DESCRIPTION will be updated using Pre-Init routine PX10P199. Routine PX10P199 directly sets nodes in the File Description for File (#9999999.17). End result should be as below: ^DIC(9999999.17,"%D",2,0)="of treatments that are not covered in the ICD-CM Procedures or the CPT" ^DIC(9999999.17,"%D",8,0)="the lack of a coded CPT or ICD-CM." |
||||
| 6019 | DESCRIPTION UPDATE FOR 9000010.07 FILE | File | 1 | 2013/10/10 | Retired | Private | 9000010.07 | Important Note: This is a One-Time Agreement, just for Patch PX*1.0*199. Update of DESCRIPTION for File (#9000010.07) which is the V POV File to replace occurrence of 'ICD9' to 'ICD' to acommodate ICD-10 Remediation project for Patch PX*1.0*199. DESCRIPTION will be updated using Pre-Init routine PX10P199. Routine PX10P199 directly sets node in the File Description for File (#9000010.07). End result should be as below: ^DIC(9000010.07,"%D",24,0)="appropriate ICD diagnosis code. Physician entered narrative which modifies" |
||||
| 6020 | DESCRIPTION UPDATE FOR ACR INDEX OF 9000010.07 FILE | File | 1 | 2013/10/10 | Pending | Private | Important Note: This is a One-Time Agreement, just for Patch PX*1.0*199. Update of DESCRIPTION for ACR Index of File (#9000010.07) which is the V POV File to replace occurrences of 'ICD9' to 'diagnosis' and 'ICD9 CODE' to 'ICD IEN' to accommodate ICD-10 Remediation project for Patch PX*1.0*199. DESCRIPTION for ACR Index will be updated using Pre-Init routine PX*1.0*199. Routine PX10P199 directly sets nodes in the File Description for the ACR Index for File (#9000010.07). ACR Index # should be retrieved by looping through those that are under ^DD("IX","IX","ACR") then looking at uparrow piece 1 of ^DD("IX",<ACR Index #>,0) node for each and, if it equals 9000010.07, then the end result should be as below: |
|||||
| 6021 | ACR INDEX DESCRIPTION UPDATE FOR 9000010.07 FILE | File | 1 | 2013/10/10 | Pending | Private | 9000010.07 | Important Note: This is a One-Time Agreement, just for Patch PX*1.0*199. Update of DESCRIPTION for ACR Index of File (#9000010.07) which is the V POV File to replace occurrences of 'ICD9' to 'diagnosis' and 'ICD9 CODE' to 'ICD IEN' to accommodate ICD-10 Remediation project for Patch PX*1.0*199. DESCRIPTION for ACR Index will be updated using Pre-Init routine PX*1.0*199. Routine PX10P199 directly sets nodes in the File Description for the ACR Index for File (#9000010.07). ACR Index # should be retrieved by looping through those that are under ^DD("IX","IX","ACR") then looking at uparrow piece 1 of ^DD("IX",<ACR Index #>,0) node for each and, if it equals 9000010.07, then the end result should be as below: ^DD("IX",<ACR Index #>,.1,2,0)="all patients with a particular diagnosis code and one for finding all" ^DD("IX",<ACR Index #>,.1,3,0)="the diagnosis codes a patient has." ^DD("IX",<ACR Index #>,.1,5,0)=" ^PXRMINDX(9000010.07,""IPP"",ICD IEN,PS,DSN,VISIT DATE,DAS) and" ^DD("IX",<ACR Index #>,.1,6,0)=" ^PXRMINDX(9000010.07,""PPI"",DFN,PS,ICD IEN,VISIT DATE,DAS)" |
||||
| 6034 | Editing Label Date/Time multiple HELP-PROMPT (file #52) | File | 1 | 2014/03/26 | Retired | Private | 52 | This request is to allow the Outpatient Pharmacy package to remove the HELP-PROMPT for multiple field Label Date/Time (#32) of the Prescription file (#52). This change will be used in patch PSO*7.0*370 only. |
||||
| 6062 | LANGUAGE file | File | 1 | 2014/06/02 | APPROVED | Active | Controlled Subscription | .85 | With VA FileMan 22.2, the LANGUAGE file (#.85) has been updated to contain ISO 639-1 and 639-2 compatible languages. This file can be used as a Pointer to file for any field that wants to reference a language. Any application that points to this file should set screening logic to constrict the user selection. The screening logic should use the TYPE field (#.07), $P(^(0),U,7), which is a set of codes: 'L' FOR Living 'C' FOR Constructed 'A' FOR Ancient 'H' FOR Historical 'E' FOR Extinct If you only want to allow selections of languages that are currently spoken, you can use the following: S DIC("S")="I $P(^(0),U,7)=""L""" Also, read access is permitted using FileMan APIs. Amended: 1/3/23 Added Field.03 THREE LETTER CODE for use by REGISTRATION, INCOME VERIFICATION MATCH effective with patch DG*5.3*1085/IVM*2.0*208 |
2023/01/03 | ||
| 6167 | READ ACCESS TO DD(409.68 | File | 1 | 2015/03/02 | APPROVED | Active | Private | Scheduling requests read access to ^DD(409.68,.08,0). This reference is in legacy code that is missing an ICR. It is retrieving the external value for a code in OUTPATIENT ENCOUNTER (#409.68) file, ORIGINATING PROCESS TYPE (#.08) field. |
2015/03/27 | |||
| 6168 | READ ACCESS TO DD(404.52 | File | 1 | 2015/03/02 | APPROVED | Active | Private | This is a onetime agreement via patch SD*5.3*603. Scheduling requests read access to ^DD(404.52,.09,1,2,0). The post-install routine, SD53P603, in SD*5.3*603 will delete the FTEXR trigger cross-reference on the POSITION ASSIGNMENT HISTORY (#404.52) file, FTEE EQUIVALENT (#.09) field. Access to the ^DD(404.52 global is required to verify the cross reference is present and the correct number prior to deleting it. Entry point in SD53P603: DELTRIGR ;Delete FTEE History trigger in 404.52 ; NEW SDERR DO BMES^XPDUTL("Delete the FTEXR Trigger in 404.52/.09") ; IF $DATA(^DD(404.52,.09,1,2,0)),^DD(404.52,.09,1,2,0)["FTEXR" DO . DO DELIX^DDMOD(404.52,.09,2,"","SDERR") . IF '$DATA(SDERR) DO . . DO BMES^XPDUTL("The FTEXR trigger was deleted.") . ELSE DO . . DO BMES^XPDUTL("ERROR encountered deleting the trigger.") ELSE DO . DO BMES^XPDUTL("The FTEXR trigger does not exist - previously deleted.") QUIT ; |
2015/03/27 | |||
| 6196 | DIA | File | 1 | 2015/05/19 | APPROVED | Active | Private | 1.1 | DSS request a one-time agreement allowing a direct global kill of the AUDIT file (#1.1) for 3 ECX related files in the post-install routine in patch ECX*3.0*154. Details of this request are below. The DSS extract software (ECX) audits certain fields in the PRESCRIPTION EXTRACT file (#727.81), the UNIT DOSE LOCAL EXTRACT file (#727.809) and the IV DETAIL EXTRACT file (#727.819) when they are edited using the Pharmacy Volume Edit [ECX PHA VOL EDIT] option. The auditing of the specified fields was to be turned on and off using this option. However, a bug in the software caused the auditing to never be turned off so when the monthly extract files were built, an audit log entry was created for every entry in the extract file. In order to make this option, and its associated information useful, DSS is requesting permission to delete the entire audit log for files 727.81, 727.809, and 727.819. This would be done by killing the entire audit log for each file via a direct global kill of ^DIA(File #). |
2015/06/11 | ||
| 6203 | Delete the 'RDE' cross reference and the data (70.03 ; 1.1) | Routine | 1 | 2015/06/15 | APPROVED | Active | Private | 2015/06/22 | ||||
| 6256 | DELETE SCREEN NODES | File | 1 | 2015/10/29 | APPROVED | Active | Private | There is a bug in FileMan that is not deleting the screen nodes (12 and 12.1) out of the DD global when a DD update is sent out via KIDS. The PCE team is therefore requesting a one-time direct delete access to the following nodes: ^DD(9000010.11,.01,12) ^DD(9000010.11,.01,12.1) This will be used in the PX*1*210 Post-Install Routine PXVP210. |
2015/11/04 | |||
| 6338 | PSS*1*189 POST INSTALL WITH DD(52.6 | File | 1 | 2015/12/21 | APPROVED | Active | Private | 52.6 | This is a one-time ICR valid only for the Post-Install Routine for patch PSS*1.0*189. The INACTIVATION DATE field (#12) field will be displayed on any lookup performed on the IV ADDITIVES File (#52.6) by creating a new "ID" node by direct global set into ^DD(52.6,0,"ID",12) by Post-Install Routine PSS*1*189. |
2016/07/12 | ||
| 6339 | PSS*1*189 POST INSTALL WITH DD(52.7 | File | 1 | 2015/12/21 | APPROVED | Active | Private | 52.7 | This is a one-time ICR valid only for the Post-Install Routine for patch PSS*1.0*189 The INACTIVATION DATE field (#8) field will be displayed on any lookup performed on the IV SOLUTIONS File (#52.7) by creating a new "ID" node by direct global set into ^DD(52.7,0,"ID",8) by Post-Install Routine PSS*1*189. |
2016/07/12 | ||
| 6410 | FORBID PURGING AUDITS | File | 1 | 2016/05/24 | APPROVED | Active | Controlled Subscription | The following data dictionary (DD) nodes can be set to restrict purging of data and/or DD audits. These nodes have to be set directly in programmer mode, since there is no utility to set them. These nodes can be transported using the KIDS utility, if you send the full file Data Dictionary. |
2016/07/08 | |||
| 6445 | DIUTC | Routine | 1 | 2016/08/05 | APPROVED | Active | Supported | This Coordinated Universal Time (UTC) API will convert a FileMan date/time into Greenwich Mean Time (GMT) with a time zone offset based on various input values entered by the user or the default institution in the DUZ(2) variable. The format of the default output will be a GMT represented in standard FileMan date/time format and an internal three digit time zone offset appended to the end. The calculation for the internal offset is the external offset converted to minutes, then divided by 5, and then added to 500. So -07:00 is -420 minutes, then divided by 5 is -84, and added to 500 is 416. There may be other output variables based on the value of the EXT input parameter. The details for the other output values are documented in the $$UTC variable below. To determine the offset, the API needs to have a TimeZone and Country. These values are determined using the following algorithm: 1. No optional input parameters are passed in. The user's default Institution will be used based on the DUZ(2) variable. The TimeZone and Country are determined by the new fields in the Institution file. 2. If only Institution is passed in as an input parameter, the TimeZone and Country are determined by the new fields in the Institution file. 3. The TimeZone and Country parameters are both passed in as input parameters. The UTC API will return an error for any of the following conditions: 1. If the TimeZone or Country cannot be determined from any of the methods documented above, an error will be returned. 2. If the TimeZone parameter is passed in without Country parameter or the Country parameter is passed in without a TimeZone parameter, an error will be returned. 3. If the Institution parameter is passed in with either the TimeZone or Country parameter, an error will be returned. 4. Once the TimeZone and Country are determined, they will be validated for consistency. An error will be returned if they are inconsistent e.g. if user passes in TimeZone = "Australian Eastern Time" and Country="Mexico", the UTC API will return an error. |
DIUTC | 2017/06/23 | ||
| 6696 | READ ACCESS TO DD(404.43 | File | 1 | 2017/01/03 | APPROVED | Active | Private | This is a onetime agreement via patch SD*5.3*659. Scheduling requests read access to the following ^DD(404.43 nodes to obtain the cross reference numbers that will be deleted by the patch post-install routine. ^DD(404.43,.01,1, ^DD(404.43,.02,1, ^DD(404.43,.03,1, ^DD(404.43,.04,1, ^DD(404.43,.05,1, The patch post-install routine will delete the following cross references. These cross references are associated with HL7 messaging that PCMM no longer performs. PATIENT TEAM POSITION ASSIGNMENT FILE (#404.43) .01 PATIENT TEAM ASSIGNMENT Xref-AEVENT1 .02 TEAM POSITION Xref-AEVENT3 .03 POSITION ASSIGNED DATE Xref-AEVENT4 .04 POSITION UNASSIGNED DATE Xref-AEVENT5 .05 PC ROLE Xref-AEVENT2 Code to delete cross references. DELXREF(SDFILE,SDFIELD,SDXREFNM) ; Delete traditional cross reference ;Inputs: SDFILE - file number ; SDFIELD - field number ; SDXREFNM - xref name ; NEW SDHIT,SDOUT,SDERR,SDXREF DO BMES^XPDUTL("Delete the "_SDXREFNM_" xref in "_SDFILE_"/"_SDFIELD_".") ; SET SDHIT=0 SET SDXREF=0 FOR SET SDXREF=$O(^DD(SDFILE,SDFIELD,1,SDXREF)) QUIT:('+SDXREF)!(SDHIT) DO . IF $GET(^DD(SDFILE,SDFIELD,1,SDXREF,0))[SDXREFNM DO . . ;W !,"SDXREF: ",SDXREF," Node: ",^DD(SDFILE,SDFIELD,1,SDXREF,0),! . . DO DELIX^DDMOD(SDFILE,SDFIELD,SDXREF,"","SDOUT","SDERR") . . IF '$DATA(SDERR) DO . . . DO MES^XPDUTL("The "_SDXREFNM_" cross reference was deleted.") . . . SET SDHIT=1 . . ELSE DO . . . DO MES^XPDUTL("ERROR encountered deleting the "_SDXREFNM_" cross reference.") ; DO:'SDHIT MES^XPDUTL("The "_SDXREFNM_" cross reference was not found.") ; QUIT ; |
2017/02/02 | |||
| 6721 | READ ACCESS TO DD(404.52 | File | 1 | 2017/01/20 | APPROVED | Active | Private | This is a onetime agreement via patch SD*5.3*659. Scheduling requests read access to the following ^DD(404.52 nodes to obtain the cross reference numbers that will be deleted by the patch post-install routine. ^DD(404.52,.01,1, ^DD(404.52,.02,1, ^DD(404.52,.03,1, ^DD(404.52,.04,1, ^DD(404.52,.09,1, The patch post-install routine will delete the following cross references. These cross references are associated with HL7 messaging that PCMM no longer performs. POSITION ASSIGNMENT HISTORY FILE (#404.52) .01 TEAM POSITION Xref-AEVENT1 .02 EFFECTIVE DATE Xref-AEVENT2 .03 PRACTITIONER Xref-AEVENT3 .04 STATUS Xref-ASTATUS .09 FTEE EQUIVALENT Xref-AFTEE Code to delete cross references. DELXREF(SDFILE,SDFIELD,SDXREFNM) ; Delete traditional cross reference ;Inputs: SDFILE - file number ; SDFIELD - field number ; SDXREFNM - xref name ; NEW SDOUT,SDERR,SDXREF DO BMES^XPDUTL("Delete the "_SDXREFNM_" xref in "_SDFILE_"/"_SDFIELD_".") ; SET SDXREF=0 FOR SET SDXREF=$O(^DD(SDFILE,SDFIELD,1,SDXREF)) QUIT:'+SDXREF DO . IF $GET(^DD(SDFILE,SDFIELD,1,SDXREF,0))[SDXREFNM DO . . ;W !,"SDXREF: ",SDXREF," Node: ",^DD(SDFILE,SDFIELD,1,SDXREF,0),! . . DO DELIX^DDMOD(SDFILE,SDFIELD,SDXREF,"","SDOUT","SDERR") . . IF '$DATA(SDERR) DO . . . DO MES^XPDUTL("The "_SDXREFNM_" cross reference was deleted.") . . ELSE DO . . . DO MES^XPDUTL("ERROR encountered deleting the "_SDXREFNM_" cross reference.") QUIT ; |
2017/02/02 | |||
| 6722 | READ ACCESS TO DD(404.53 | File | 1 | 2017/01/20 | APPROVED | Active | Private | This is a onetime agreement via patch SD*5.3*659. Scheduling requests read access to the following ^DD(404.53 nodes to obtain the cross reference numbers that will be deleted by the patch post-install routine. ^DD(404.53,.01,1, ^DD(404.53,.02,1, ^DD(404.53,.04,1, ^DD(404.53,.06,1, The patch post-install routine will delete the following cross references. These cross references are associated with HL7 messaging that PCMM no longer performs. PRECEPTOR ASSIGNMENT HISTORY FILE (#404.53) .01 TEAM POSITION Xref-AEVENT1 .02 EFFECTIVE DATE Xref-AEVENT2 .04 STATUS Xref-AEVENT3 .06 PRECEPTOR TEAM POSITION Xref-AEVENT4 Code to delete cross references. DELXREF(SDFILE,SDFIELD,SDXREFNM) ; Delete traditional cross reference ;Inputs: SDFILE - file number ; SDFIELD - field number ; SDXREFNM - xref name ; NEW SDOUT,SDERR,SDXREF DO BMES^XPDUTL("Delete the "_SDXREFNM_" xref in "_SDFILE_"/"_SDFIELD_".") ; SET SDXREF=0 FOR SET SDXREF=$O(^DD(SDFILE,SDFIELD,1,SDXREF)) QUIT:'+SDXREF DO . IF $GET(^DD(SDFILE,SDFIELD,1,SDXREF,0))[SDXREFNM DO . . ;W !,"SDXREF: ",SDXREF," Node: ",^DD(SDFILE,SDFIELD,1,SDXREF,0),! . . DO DELIX^DDMOD(SDFILE,SDFIELD,SDXREF,"","SDOUT","SDERR") . . IF '$DATA(SDERR) DO . . . DO MES^XPDUTL("The "_SDXREFNM_" cross reference was deleted.") . . ELSE DO . . . DO MES^XPDUTL("ERROR encountered deleting the "_SDXREFNM_" cross reference.") QUIT ; |
2017/02/02 | |||
| 6736 | Executable Help Deletion | Other | 1 | 2017/02/17 | Retired | Private | This is a temporary agreement to be used only if PSS*1*202, which is the RollBack patch for PSS*1*201, needs to be released or sent to any number of sites. The Post-Init routine (PSS202RB) will kill the 4 node of the NAME (#.01) Field and SYNONYM (#.5) Field of the MEDICATION INSTRUCTION (#51) File Data Dictionary. The 4 node contains the Executable Help. 0n 8/14/17, the developer said the 90-warranty period for PSS*1*201 was reached and the functionality provided by this ICR will not be needed for the rollback patch PSS*1*202. ICR #6736 was retired on 11/15/17. |
|||||
| 6740 | DD 'AUTOLINK' MULT .01 FLD TO REMOVE REF TO 44/409.67 FILES | File | 1 | 2017/02/24 | APPROVED | Active | Private | 100.21 | Patch OR*3.0*399 to remove AUTOLINK Multiple from Data Dictionary of OE/RR LINK File in a pre-install routine that is part of the patch and then the patch itself will rebuild the Multiple with only those Variable Pointer entries that should remain (all but refs to 44 and 409.67). Patch will rebuild 100.213,.01 AUTOLINK field of ^DD(100.213) leaving only the following in the VARIABLE POINTER field: FILE ORDER PREFIX LAYGO MESSAGE 42 1 W n WARD 405.4 2 R n ROOM-BED 200 3 P n PROVIDER 45.7 4 S n SPECIALTY Formerly it had a link to either File 44 or 409.67 (which OR*3.0*399 deletes), e.g.: 44 5 C n CLINIC Deletion of AUTOLINK Multiple is done by OR3P399 pre-install routine with the use of the following FileMan call: S DIU=100.213,DIU(0)="S" D EN^DIU2 K DIU |
2017/03/02 | ||
| 6793 | LOOK FOR ENTRIES POINTING TO VISIT ENTRIES | File | 1 | 2017/07/06 | APPROVED | Active | Private | This integration agreement allows the subscribing package to determine all of the entries that point to an entry in the VISIT file (#9000010). Read-only global access is granted to the global references listed below. |
2017/11/15 | |||
| 6864 | READ ACCESS TO DD(200 | File | 1 | 2018/01/17 | APPROVED | Active | Private | 200 | This is a one-time agreement via patch XU*8.0*687 to clean up a cross reference on two fields, MAIL CODE (#28) and SERVICE/SECTION (#29) of the NEW PERSON File (#200). This agreement will cover the removal of the E cross reference on Field 28. The code to remove the cross reference is: N XUHIT,XUOUT,XUERR,XUXREF S (XUHIT,XUXREF)=0 F S XUXREF=$O(^DD(200,28,1,XUXREF)) Q:('+XUXREF)!(XUHIT) D . I $P($G(^DD(200,28,1,XUXREF,0)),U,2)="E" D .. S XUHIT=1 .. D DELIX^DDMOD(200,28,XUXREF,"K","XUOUT","XUERR") .. ; .. ; No error, xRef deleted .. I '$D(XUERR) D MES^XPDUTL("The E cross reference was deleted.") Q .. ; .. ; Error encountered, xRef not deleted. .. D MES^XPDUTL("ERROR encountered deleting the E cross reference.") ; D:'XUHIT MES^XPDUTL("The E cross reference was not found.") ; Q |
2018/02/16 | ||
| 6875 | Repoint or Delete Existing File Entry | Routine | 1 | 2018/02/15 | APPROVED | Active | Supported | DITP | 2018/03/05 | |||
| 6876 | Check for Existing Pointers | Routine | 1 | 2018/02/15 | APPROVED | Active | Supported | The CHKPT^DIUTL API will find all entries that point to a record. |
DIUTL | 2018/03/05 | ||
| 6892 | VISTA RADIOLOGY UPDATES DD (CROSS REFERENCE #) | File | 1 | 2018/03/21 | APPROVED | Active | Private | 75.1 | What follows is a VA FileMan index print for the 'DATE DESIRED (Not guaranteed)' (75.1,21) field of the RAD/NUC MED ORDERS file. There are two "AP" subscripted indices with the same set/kill logic: one traditional, one new-style. The traditional index was left after RA*5.0*130 created the new-style "AP" index. The traditional index, named "AC", should have been deleted. It was not. RA*5.0*124 will correct this oversight. Radiology is requesting a one-time Integration Agreement to walk down the cross-reference number subscript to find the aforementioned cross- reference number identifying the "AC" index. Once the correct cross-reference number is identified Radiology will use the supported Application Programmer Interface (API) DELIX^DDMOD to delete the "AC" cross-reference. |
2018/03/22 | ||
| 6893 | Updating DD 'VR' and 'VRPK' Nodes | File | 1 | 2018/03/22 | APPROVED | Active | Private | 200 | IB*2.0*582 sent the entire data dictionary for the NEW PERSON (#200) file. This caused the 'VR' node to be changed from "8.0" to "2.0" and the 'VRPK' node to be changed from "XU" to "IB" in the data dictionary. This ICR is a onetime only request for patch XU*8.0*687 to restore the fields to their orignal state of "8.0" for 'VR' and "XU" for 'VRPK'. This will be done via a direct set: S ^DD(200,0,"VR")="8.0" S ^DD(200,0,"VRPK")="XU" |
2018/04/02 | ||
| 6920 | DBIA1052-D | Routine | 1 | 2018/06/05 | APPROVED | Active | Private | KIDS needs to call the VA FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forums, and Functions at a site during the installation of a package. |
DIFROMSR | 2018/06/05 | ||
| 6921 | INQUIRE OPTION FOR MENU MAN | Routine | 1 | 2018/06/05 | APPROVED | Active | Private | Allows Inquire type option for Menu Man |
DIP1 | 2019/03/08 | ||
| 6976 | DELETION OF INPUT TEMPLATES | File | 1 | 2018/09/27 | Pending | Controlled Subscription | .402 | This integration agreement covers the deletion of input templates used with patch DG*5.3*914 for Camp Lejeune. The pre-init routine DGPR914 will loop through a list of input templates used for the project Camp Lejeune and delete them. Upon installation of patch DG*5.3*914, all input templates will be automatically recompiled. Deletion of input templates will involve the following: 1. Using $$FIND1^DIC(.402,"","MX","INPUT TEMPLATE NAME") to get the Input Template IEN from file #.402. 2. Using ^DIK to delete the input template from file #.402. |
||||
| 7008 | Entity mapping APIs | Routine | 1 | 2019/01/24 | APPROVED | Active | Supported | APIs that can be used with the ENTITY file (#1.5) to retrieve data from VA FileMan files and format them in either XML or JSON. |
DDE | 2019/03/08 | ||
| 7014 | Entity File Cross Reference | File | 1 | 2019/01/30 | APPROVED | Active | Controlled Subscription | 1.5 | The ENTITY file (#1.5) has two cross reference that will be available to approved applications. These cross references allows an application to lookup a record by DATA MODEL field (#.06), DISPLAY NAME field (#.1), and DEFAULT FILE NUMBER field (#.02). Currently, there is only two Data Models: FHIR and SDA. The cross reference will look like: ^DDE("FHIR",display name, file number, ien)="" ^DDE("SDA", display name, file number, ien)="" |
2019/03/08 | ||
| 7053 | FIELD LABEL CHECK | File | 1 | 2019/04/04 | Pending | Controlled Subscription | 0 |
VistA Laboratory requests permission to read ^DD(63.04 in order to check for Field Label inconsistencies which have potential for causing downstream issues. Patch LR*5.2*519 will check all subscripts in the "B" cross reference of ^DD(63.04 and send a MailMan message to the "LMI" MailMan group if the following issues are found: 1. A Field Label subscript in the "B" cross reference does not match the field label of the corresponding internal entry number (IEN) in the first "^" data piece of ^DD(63.04,IEN,0). Example - Correct: ^DD(63.04,"B","ABC",100)="" ^DD(63.04,100,0)="ABC^FJ222^^RF;2^K:$L(X)>222!($L(X)<1) X" Example - Incorrect: ^DD(63.04,"B","ABC",100)="" ^DD(63.04,100,0)="XYZ^FJ222^^RF;2^K:$L(X)>222!($L(X)<1) X" And/Or: 2. A Field Label subscript in the "B" cross reference points to more than one IEN at ^DD(63.04,IEN,0). Example - Correct - Only one entry at the "B" cross reference ^DD(63.04,"B","ABC",100)="" Example - Incorrect - More than one entry at the "B" cross reference ^DD(63.04,"B","ABC",100)="" ^DD(63.04,"B","ABC",200)="" |
||||
| 7060 | DELETE FILES AND SUB-FILES TO BACKOUT PRCA313 FROM IOC | Routine | 1 | 2019/04/30 | APPROVED | Active | Private | The project for PRCA*4.5*313 is being cancelled, and since the patch is already in production at three IOC sites, the patch needs to be backed out of those three sites. This integration agreement is to allow use of a supported fileman API to delete files and sub-files so that they may be restored to their pre-patch condition. This API will be used in the pre-install routine PRCA313P. FileMan API being used: Deleting Files and Sub-files EN^DIU2: Delete Data Dictionary Reference Type: Supported Category: Classic VA FileMan ICR#: 10014 |
DIU2 | 2019/05/14 | ||
| 7061 | DELETE FIELDS TO BACKOUT PRCA313 FROM IOC | Routine | 1 | 2019/04/30 | APPROVED | Active | Private | The project for PRCA*4.5*313 is being cancelled, and since the patch is already in production at three IOC sites, the patch needs to be backed out of those three sites. This integration agreement is to allow use of a supported fileman API to delete fields so that they may be restored to their pre-patch condition. This API will be used in the pre-install routine PRCA313P. FileMan API being used: Deleting Fields ^DIK: Delete Data Dictionary Reference Type: Supported Category: Classic VA FileMan ICR#: 10014 |
DIK | 2019/05/14 | ||
| 7079 | SOCIAL WORK FILE DELETION | File | 1 | 2019/06/03 | APPROVED | Active | Private | Social Work patch SOW*3.0*65 contains post install routine SOW3P65, which will use the VA FileMan API, EN^DIU2, to completely remove all SOW files, data, and related data dictionary entries. The following files will be removed: -SOCIAL WORK CASE (#650) -SOCIAL WORK SITE PARAMETERS (#650.1) -COST DISTRIBUTION CENTER (#651) -RCH (#652) -RESOURCES/REFERRALS (#653) -SOCIAL WORK PATIENT (#655) -SWS ASSESSMENT DATA BASE (#655.2) -PSYCHO-SOCIAL PROBLEMS (#655.201) -DIRECT SERVICE CATEGORIES (#655.202) -PSYCHO-SOCIAL OUTCOMES (#655.203) -SWS RESOURCES (#656) The following code from SOW3P65 will be used to remove the files: S DIU(0)="DST" ;flags to delete data, subfile and templates F SOWFILE=650,650.1,651:1:653,655,655.2:.001:655.203,656 D ;loop through known social work files .S DIU=$$ROOT^DILFD(SOWFILE),SOWNODE=$$CREF^DILF(DIU) ;set diu=file root and sownode=closed file root .I '$$VFILE^DILFD(SOWFILE) Q ;verify file exists .D EN^DIU2 ;delete file and data in diu |
2019/06/03 | |||
| 7126 | DD 95.3 modification | File | 1 | 2020/02/09 | APPROVED | Active | Private | 95.3 | Temporary KILL and reset ~DD(95.3,0,"ID",80). Temporary KILL and reset ~DD(95.3,0,"SCR"). Temporary reset $P(^LAB(95.3,0),U,3) to 95.3I or 95.3Is This is a work around for the way KIDS looks up a record during the Install Process. The problem is KIDS uses the .01 field and the Identifiers to match an existing record and the incoming record has a different value for the Identifier. The solution is to send the DD with no Identifiers and to delete the Identifiers during the Pre-Install process and to set the Identifiers back during the Post-Install process. The same is for File Filter set into SCR node. |
2020/02/18 | ||
| 7127 | DD 64.061 modification | File | 1 | 2020/02/09 | APPROVED | Active | Private | 64.061 | Temporary KILL and reset ~DD(64.061,"ID",8). This is a work around for the way KIDS looks up a record during the Install Process. The problem is KIDS uses the .01 field and the Identifiers to match an existing record and the incoming record has a different value for the Identifier. The solution is to send the DD with no Identifiers and to delete the Identifiers during the Pre-Install process and to set the Identifiers back during the Post-Install process. |
2020/02/18 | ||
| 7145 | DD GLOBAL READ ACCESS | File | 1 | 2020/04/01 | Pending | Private | Above PAR requests permission to perform direct reads from the FILE Attribute file. Including all the fields as well as the 'GL' & 'IX' indexes. The 'IX' cross reference index is used to return information faster by using the cross references when searching for specific data. ^DD(File#, 0, "IX", Reference, File#, Field#) The 'GL' index is used to step through data using the global layout. ^DD(File#, "GL", node, piece, Field#) Global File & Field may be read and traversed by direct means. ^DD(File#, Field#,0) .01 LABEL 0;1 Direct Read & Fileman Read .2 SPECIFIER 0;2 Direct Read & Fileman Read .3 POINTER 0;3 Direct Read & Fileman Read .4 GLOBAL SUBSCRIPT LOCATION 0;4 Direct Read & Fileman Read INPUT TRANSFORM 0;5 Direct Read & Fileman Read ^DD(File#, Field#,1,SEQ CROSS-REFERENCE ^DD(File#, Field#,1,SEQ,0) File 0;1 Direct Read & Fileman Read INDEX 0;2 Direct Read & Fileman Read ^DD(File#, Field#,1,SEQ,1,1) SET STATEMENT Direct Read & Fileman Read ^DD(File#, Field#,1,SEQ,1,2) KILL STATEMENT Direct Read & Fileman Read ^DD(File#, Field#,1,SEQ,1,3) NO DELETE MESSAGE Direct Read & Fileman Read ^DD(File#, Field#,1,SEQ,1,"DT") DATE UPDATED Direct Read & Fileman Read ^DD(File#, Field#,1,SEQ,1,"%D") DESCRIPTION Direct Read & Fileman Read ^DD(File#, Field#,3) .01 'HELP'-PROMPT 0;1 Direct Read & Fileman Read ^DD(File#, Field#,21) .01 DATE LAST UPDATED 0;1 Direct Read & Fileman Read ^DD(File#, Field#,"DT") .01 DATE LAST UPDATED 0;1 Direct Read & Fileman Read Global Location may be read and traversed by direct means. ^DD(File#, "GL", Node, Piece, Field#) Global Indexes may be read and traversed by direct means. ^DD(File#, 0, "IX", Reference, File#, Field#) |
|||||
| 7152 | DELETE CERNER FIELD FROM THE INSTITUTION FILE | Routine | 1 | 2020/04/27 | APPROVED | Active | Private | CERNER field in the INSTITUTION file is no longer used and it needs to be removed from the file. This integration agreement is to allow use of a supported Fileman API to delete the field . This API will be used in the post-install routine XU8P729. FileMan API being used: Deleting Fields ^DIK: Delete Data Dictionary Reference Type: Supported Category: Classic VA FileMan ICR#: 10014 |
2020/05/04 | |||
| 7173 | ERT - DD READ ACCESS | File | 1 | 2020/05/08 | Pending | Private | 0 | Enterprise Reporting Tool (ERT) requests read access to Data Dictionary file attributes. Global File & Field may be read and traversed by direct means. ^DD(File#, Field#,0) .01 LABEL 0;1 Direct Read & Fileman Read .2 SPECIFIER 0;2 Direct Read & Fileman Read .3 POINTER 0;3 Direct Read & Fileman Read .4 GLOBAL SUBSCRIPT LOCATION 0;4 Direct Read & Fileman Read INPUT TRANSFORM 0;5 Direct Read & Fileman Read ^DD(PFile#,.01) Pfile pointer FILE# from .3 POINTER .01 LABEL 0;1 Direct Read & Fileman Read .2 SPECIFIER 0;2 Direct Read & Fileman Read |
||||
| 7387 | WORLD TIMEZONES FILE | File | 1 | 2022/12/07 | APPROVED | Active | Supported | 1.71 | All fields in the WORLD TIMEZONES file (#1.71) are available for read access using VA FileMan. |
2022/12/07 | ||
| 7422 | FILE NUMBER FROM FILE NAME | File | 1 | 2023/04/12 | APPROVED | Active | Controlled Subscription | 1 | There is no supported FileMan API to determine the file number from the file name. This ICR allows the use the FileMan API $$FIND1^DIC to determine the file number. |
2023/04/12 | ||
| 7434 | DELETE LANG NODES | File | 1 | 2023/08/15 | APPROVED | Active | Private | 399.047 | The following nodes will be deleted in patch IB*2.0*742. VALUE K ^DD(399.047,.02,.009,1,0) On a previous patch, IB*2.0*727, the VALUE field was given specific detailed executable help depending on the corresponding VALUE CODE. Extraneous data nodes in DD's at some sites display a generic message that contradicts the executable help. (ENTER FROM 1 TO 10 CHARACTERS OF FREE TEXT) This patch contains a one-time cleanup in the post install routine IBY742PO. |
2023/08/16 | ||
| 10000 | Classic FileMan API: Date/Time Manipulation | Routine | 1 | 1994/04/08 | APPROVED | Active | Supported | Date and Time manipulation and Number formating. |
%DTC | |||
| 10001 | Classic FileMan API: Internal to External Date | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | This entry point takes an internal date in the variable Y and writes out its external form. |
DIO2 | |||
| 10002 | Classic FileMan API: Input Template Compilation | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Input template compilation for inproved performance. |
DIEZ | |||
| 10003 | Classic FileMan API: Date/Time Input & Conversion | Routine | 1 | 1998/11/13 | APPROVED | Active | Supported | Validate date/time input and convert it to VA FileMan's conventional internal format:"YYYMMDD.HHMMSS", where: YYY = number of years since 1700 MM = Month number DD = Day number HH = Hour number MM = Minute number SS = Seconds number |
%DT | 2015/09/29 | ||
| 10004 | Classic FileMan API: Data Display | Routine | 1 | 1998/11/16 | APPROVED | Active | Supported | Provides ways to display data from file entries and ways to convert data from one format to another. |
DIQ | |||
| 10005 | Classic FileMan API: Required Variables | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Sets up the required variables of VA FileMan. |
DICRW | |||
| 10006 | Classic FileMan API: File Lookup/Add New Entries | Routine | 1 | 1998/11/18 | APPROVED | Active | Supported | Entry point DIC is for general file lookups. Entry point IX if for a single cross reference lookups. |
DIC | |||
| 10007 | Classic FileMan API: Custom Lookup & File Info. Setup | Routine | 1 | 1998/11/18 | APPROVED | Active | Supported | Entry point DO sets up certain file information. Entry point MIX does multi-index nonstandard order lookup. |
DIC1 | |||
| 10008 | Classic FileMan API: Entry Display For Lookups | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Displays the list of entries in a file a user can see. |
DICQ | |||
| 10009 | Classic FileMan API: Adding New Entries & YES/NO Prompt | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Can be used for adding new entries to a file. Or for YES/NO prompts. |
DICN | |||
| 10010 | Classic FileMan API: Print Data | Routine | 1 | 1995/01/12 | APPROVED | Active | Supported | Use EN1^DIP to print a range of entries, in columnar format. |
DIP | |||
| 10011 | Classic FileMan API: Word Processing | Routine | 1 | 1998/11/16 | APPROVED | Active | Supported | Call ^DIWP to format and (optionally) output any group of text lines. |
DIWP | |||
| 10012 | Classic FileMan API: Form Document Print | Routine | 1 | 1998/11/16 | APPROVED | Active | Supported | Designed to use the contents of a word processing field as a target document into which data can be inserted at print time. |
DIWF | |||
| 10013 | Classic FileMan API: Entry Deletion & File Reindexing | Routine | 1 | 2001/12/04 | APPROVED | Active | Supported | Multiple entry points to support entry deletion and file reindexing. |
DIK | |||
| 10014 | Classic FileMan API: Data Dictionary Deletion | Routine | 1 | 1998/11/16 | APPROVED | Active | Supported | Used to delete a file's data dictionary and its entry in ^DIC in order to properly update a running system. |
DIU2 | |||
| 10015 | Classic FileMan API: Data Retrieval | Routine | 1 | 1998/11/16 | APPROVED | Active | Supported | This entry point retrieves data from a file for a particular entry. |
DIQ1 | |||
| 10016 | Classic FileMan API: MUMPS Code Validation | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Checks that code conforms to the 1995 ANSI Standard and is also checked against aspects of VHA's Programming Standards and Conventions (SAC). |
DIM | |||
| 10017 | DD DATE FORMATER | File | 1 | APPROVED | Active | Supported | ||||||
| 10018 | Classic FileMan API: Edit Data | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | This routine handles input of selected data elements for a given file entry. |
DIE | |||
| 10019 | Classic FileMan API: Print Template Compilation | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Print templates can be compiled into MUMPS routines. The purpose of this DIPZ code generation is simply to improve overall system throughput. |
DIPZ | |||
| 10020 | Classic FileMan API: Print/Sort Template Display | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | DIPT | ||||
| 10021 | Classic FileMan API: Data Dictionary Listing | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Print/display a file's data dictionary listing. |
DID | |||
| 10022 | Classic FileMan API: Array Moving | Routine | 1 | 1998/11/13 | APPROVED | Active | Supported | This entry point can be used to move arrays from one location to another. The location can be local or global. |
%RCR | |||
| 10023 | Classic FileMan API: User Controlled Editing | Routine | 1 | 1998/11/18 | APPROVED | Active | Supported | Invokes the Enter or Edit File Entries option of VA FileMan to edit records in a given file, allowing the user to select which fields to edit. |
DIB | |||
| 10024 | Classic FileMan API: Wait Messages | Routine | 1 | 1998/11/18 | APPROVED | Active | Supported | Displays standard wait messages. |
DICD | |||
| 10025 | Classic FileMan API: Cross Reference Compilation | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Compiles cross references into MUMPS routines. |
DIKZ | |||
| 10026 | Classic FileMan API: Reader | Routine | 1 | 1998/11/20 | APPROVED | Active | Supported | DIR is a general purpose response reader that can be used to issue a prompt, read input interactively, perform syntax checking on the input, issue error messages or help text, and return input in a processed form. Its use is recommended to standardize user dialogue and to eliminate repetitive coding. |
DIR | |||
| 10027 | Classic FileMan API: Search File Entries | Routine | 1 | 1998/11/16 | APPROVED | Active | Supported | Search option for a specified file. |
DIS | |||
| 10028 | Classic FileMan API: Text Editing | Routine | 1 | 1994/04/28 | APPROVED | Active | Supported | This routine is used to edit word processing text using VA FileMan's editors. |
DIWE | |||
| 10029 | Classic FileMan API: Output Last Line of Text | Routine | 1 | 1998/11/16 | APPROVED | Active | Supported | Use ^DIWW to output the remaining text left in ^UTILITY($J,"W") by ^DIWP to the current device. The ^DIWW entry point is designed to be used in conjunction with the ^DIWP entry point. |
DIWW | |||
| 10030 | DD VERSION NODE | File | 1 | APPROVED | Active | Supported | ||||||
| 10031 | ScreenMan API: Form Processor | Routine | 1 | 1998/11/18 | APPROVED | Active | Supported | You can call this entry point directly from a MUMPS routine to invoke the specified form. |
DDS | |||
| 10032 | Classic FileMan API: File Access Determination | Routine | 1 | 1998/11/13 | APPROVED | Active | Supported | Used to determine if a user has access to a file. |
DIAC | |||
| 10033 | Other API: Filegram | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Generates a filegram. |
DIFGG | |||
| 10034 | Other API: Filegram | Routine | 1 | 1998/11/17 | APPROVED | Active | Supported | Used to to install filegrams. |
DIFG | |||
| 10142 | Classic FileMan API: Loader | Routine | 1 | 1994/04/11 | APPROVED | Active | Supported | Designed as a replacement for simple WRITE statements in any part of the data dictionary that has a programming 'hook', such as executable help. |
DDIOL | |||
| 10149 | ScreenMan API: Form Utilities | Routine | 1 | 1994/06/24 | APPROVED | Active | Supported | $$GET - This extrinsic function retrieves data from a data dictionary field. PUT - Stuffs data into form-only fields. |
DDSVAL | |||
| 10150 | ScreenMan API: Form Utilities | Routine | 1 | 1994/06/24 | APPROVED | Active | Supported | Help Messages: HLP, MSG; Refresh Screen: REFRESH; Run-Time Field Status: REQ, UNED Utilities. |
DDSUTL | |||
| 10151 | Extract Tool API | Routine | 1 | 1994/06/24 | APPROVED | Active | Supported | The Extract Tool lets you move or copy records from one VA FileMan file to another; a typical use is to archive records. |
DIAXU | |||
| 10152 | DD('ROU') | File | 1 | 1994/12/23 | APPROVED | Active | Supported | ^DD("ROU") - the default maximum routine size used by FileMan when compiling input and print templates, and cross-references. |
||||
| 10154 | DESCRIPTOR BLOCK | File | 1 | 1997/12/17 | APPROVED | Active | Supported | 0 | The 2nd piece of ^DD(filenumber,fieldnumber,0) is used in the "File Header" piece 2. This may be referenced since no FM APIs exist yet to return this information. |
|||
| 10155 | SET OF CODES | File | 1 | 1998/02/03 | APPROVED | Active | Supported | 0 | The 3rd piece of ^DD(filenumber,fieldnumber,0) is used in the call to Y^DIQ. This may be referenced since no FM APIs exist yet to return this field for input to the supported call Y^DIQ. |