| 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 |
| 43 | DBIA43 | File | IFCAP | 1990/06/18 | APPROVED | Active | Private | 442 | ||||
| 50 | DBIA50 | File | IFCAP | 1990/10/17 | Retired | Private | 420.1 | DMMS Points to and reads the .01 field (cost center) of file 420.1 |
||||
| 89 | DBIA89 | File | IFCAP | 1991/08/08 | APPROVED | Active | Controlled Subscription | 411 | Read access to File 411, ADMIN. ACTIVITY SITE PARAMETER, following fields: field 15 HOSPITAL STREET ADDR.1 field 16 HOSPITAL STREET ADDR.2 field 17 HOSPITAL CITY field 18 HOSPITAL STATE field 19 HOSPITAL ZIP field 19.2 HOSPITAL PHONE |
|||
| 140 | DBIA140-A | Routine | IFCAP | 1992/01/07 | Retired | Private | 1. EN3^PRCSUT - Checks for Fund Control Point user authorization access. |
PRCSUT | ||||
| 141 | DBIA141 | Routine | IFCAP | 1992/01/07 | APPROVED | Active | Private | ^PRCSDIC - Routine to perform lookup into File 410 (Control Point Activity). Variables: DIC DIC(0) DIC("A") |
PRCSDIC | |||
| 198 | DBIA198 | File | IFCAP | 1992/11/24 | APPROVED | Active | Controlled Subscription | 410 | In an effort to provide a receiving mechanism for Controlled Substances module, several look-ups and pointers are necessary for an interim interface. For Purchase Order receipts, a lookup to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442, screened by cost center [822400] is used. For Issue Receipts, a lookup occurs, screened by cost center [822400], in CONTROL POINT ACTIVITY file 410. A connection between the DRUG file 50 and ITEM MASTER file 441 is crucial for posting receipt information. This may be a one-to-many relationship and therefore involves the creation of a multiple IFCAP ITEM NUMBER field (#50.0441) in the DRUG file 50 pointing to the ITEM MASTER file 441. This field includes an input transform similar to that found in the NDC field in the ITEM MASTER file 441 preventing the linking of the same item to more than one drug. It also includes an 'AB' whole file cross-reference. Pointer to CONTROL POINT ACTIVITY file 410 Pointer to ITEM MASTER file 441 Pointer to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442 References information (Read only) from CONTROL POINT ACTIVITY file 410 .01 TRANSACTION NUMBER 10 ITEM .01 LINE ITEM NUMBER 1 DESCRIPTION 2 QUANTITY 3 UNIT OF PURCHASE 5 REPETITIVE (PR CARD) NO. 6 STOCK NUMBER 7 EST. ITEM (UNIT) COST 13 QUANTITY POSTED (WHSE) 14 QUANTITY REC'D (PRIMARY) IFCAP files are used solely to gather and display receipt information and so the Controlled Substances files 58.8 and 58.81 can accumulate a receipt history. DURATION: Till otherwise agreed, when the GIP & Drug Accountability interf ace is available |
|||
| 214 | DBIA214 | Other | IFCAP | 1993/02/22 | APPROVED | Active | Controlled Subscription | The following is entered as DBIA until the next version of DA: All components indentified in this integration request involve reading from IFCAP files. Drug Accountability does not write to any IFCAP files. Looking toward an interface with the IFCAP Generic Inventory Package, Drug Accountability (PSA) begins the process with a Connection Menu. The PSAINIT creates in the DRUG file (#50) a multiple (#50.0441) pointing to the IFCAP ITEM MASTER file (#441), enabling a direct link between the DRUG file (#50) and the ITEM MASTER file (#441). The first connecting tool provided in the Connection Menu is a sub- menu using the National Drug Code (NDC) to attempt matching entries. In the ITEM MASTER file (#441), the NDC field (#4) is located in the VENDOR multiple (#6). This field has an input transform that prevents a user from using the same NDC for more than one ITEM MASTER file entry. In studying an ITEM MASTER file from a local site, it was discovered that there were several entries in their ITEM MASTER file that did possess the same NDC. Since this situation might lead a connector to link a drug to a potentially less active item, the first option in the NDC Menu is the NDC Duplicates Report (ITEM file). This report loops through the NDC ("F") x-ref in #441. If more than one item contains the same NDC and is not inactive (field #16, '$G(^PRC(441,D0,3))), the duplicates are listed. The report displays the NDC that has more than one item attached to it, the item numbers attached, their SHORT DESCRIPTION (#.05), and the VENDOR (#6) => VENDOR file (#440,#1) that contains the duplicated NDC. The second item on the NDC Menu is the Report Potential NDC Matches option. This report loops through the active, unlinked (to #441) entries in the DRUG file (#50) that have an NDC. If a corresponding NDC is found in the "F" x-ref in the ITEM MASTER file (#441), the NDC and drug name are listed from the DRUG file (#50) and the ITEM NUMBER (#.01) and DESCRIPTION (#.1) listed from the ITEM MASTER file (#441). Using the ITEM NUMBER ("AB") x-ref in the DRUG file (#50), a check is made to see if the matched ITEM MASTER file entry is already linked to another DRUG file entry. If so the user is informed of the existing connection. Using this same loop and display criteria, the Controlled Connection by NDC Match allows the user the opportunity to actually link matched entries. If the user approves the displayed match, a ^DIE stuff of the item number into the item multiple (#50.0441) in the DRUG file occurs. Likewise, the Automated DRUG/ITEM file link by NDC option uses the same loop and display criteria and the ^DIE stuff for all matches in the loop. In the event that the user requires more information about a selected drug from either the DRUG file or the ITEM MASTER file before linking, the Inquire/Compare DRUG file/ITEM file option is available. This option uses a FM inquire with a no-link pointer jump from the DRUG file to the ITEM MASTER file via the NDC "F" x-ref in #441. The user selects the drug from the DRUG file and along with corresponding info from the DRUG file the DESCRIPTION (#.1), NSN (#5), NDC (VENDOR (#6),#4) by which the jump occurred, and from that same VENDOR multiple the UNIT COST (#1), UNIT OF PURCHASE (#1.5), DATE OF UNIT PRICE (#2.5), PACKAGING MULTIPLE (#1.6), calculated unit cost = UNIT COST (#1)/DISPENSE UNITS PER ORDER UNIT from the DRUG file, VENDOR (#.01), CREATED BY (#15), and with a jump to #200 their OFFICE PHONE NUMBER. Using this same jump, the DRUG file/ITEM file Comparison Report displays the same data with the user selecting a range of drugs from the DRUG file. The FSN Menu functions similar to the NDC Menu. The Report Potential FSN Matches option loops through the active, unlinked (to #441) entries in the DRUG file that have an FSN. If a corresponding NSN is found in the "BA" x-ref in the ITEM MASTER file, the FSN and drug name are listed from the DRUG file and the ITEM NUMBER (#.01) and DESCRIPTION (#.1) listed from the ITEM MASTER file. Using the ITEM NUMBER ("AB") x-ref in the DRUG file, a check is made to see if the matched ITEM MASTER file entry is already linked to another DRUG file entry. If so the user is informed of the existing connection. Using this same loop and display criteria the Controlled Connection by FSN Match option allows the user to actually link matched entries. If the user approves the displayed match, a ^DIE stuff of the item number into the item multiple (#50.0441) in the DRUG file occurs. Likewise, the Automated DRUG/ITEM File Link by FSN option uses the same loop and display criteria and the ^DIE stuff for all matches in the loop. The Single Drug Match option uses both the NDC and FSN/NSN tools described previously to offer a connection for a single selection from the DRUG file. If a link to an ITEM MASTER file entry already exists, it is displayed to the user and they may edit the connection in the DRUG file. Using the ITEM NUMBER multiple pointer (#50.0441) in the DRUG file, the user can also do look-ups to the ITEM MASTER file via available x-refs (NSN (BA), SHORT DESCRIPTION (C), VENDOR STOCK # (D), or NDC (F)) in order to select additional connections. The Report of Unlinked DRUG/ITEM File Entries lists active drugs from the DRUG file which do not yet have any entries in the ITEM NUMBER multiple (#50.0441). The Connect Unlinked DRUG/ITEM file Entries option loops through these unlinked entries and offers all the tools described in the Single Drug Match option to perform the links. The Active, Unlinked Drugs in the ITEM File option allows the user to select a purchase date from which to consider an ITEM MASTER file drug active. It then loops through the ITEM MASTER file and when an entry's FSC (#2) = 6505 (Federal Supply Classification for drugs), is not an INACTIVATED ITEM? (#16), is not linked to a drug('$O(^PSDRUG,"AB",ITEM,"")), has an entry in the FCP (#1) multiple, and has within at least one FCP entry, an entry in the PURCHASE ORDER (#1) multiple, the P.O. DATE(s) (#442,#.1) are checked against the user selected purchase date. For entries that pass this criteria, the ITEM NUMBER (#.01), SHORT DESCRIPTION (#.05), NSN (#5), LAST VENDOR ORDERED (#9), NDC (#6,#4) (for the LAST VENDOR ORDERED), and the DESCRIPTION (#.1) are displayed. The Display Connected Drug option allows the user to print both a vendor catalog for a selected item as well as a procurement history. The user selects an entry from the DRUG file. If it is connected to more than one entry in the ITEM MASTER file the user is asked to select one of the connected entries from the ITEM NUMBER multiple (#50.0441). From the ITEM MASTER file, the ITEM NUMBER (#.01), SHORT DESCRIPTION (#.05),and NSN are displayed. If the selected ITEM MASTER file entry has only one VENDOR (#6) or has a MANDATORY SOURCE (#10), then that vendor is displayed along with the VENDOR STOCK # (#3), NDC (#4), PACKAGING MULTIPLE (#1.6), UNIT OF PURCHASE (#1.5), UNIT COST (#1), MINIMUM ORDER (#8), DATE OF UNIT PRICE (#2.5), and REQUIRED ORDER MULTIPLE (#9). If there is more than one vendor for the item, the LAST VENDOR ORDERED (#9) is displayed as well as each available vendor sorted by DATE OF UNIT PRICE (#2.5), beginning with the most recent date. For each vendor the PACKAGING MULTIPLE (#1.6), UNIT OF PURCHASE (#1.5), UNIT COST (#1), DATE OF UNIT PRICE(#2.5), and whether or not the vendor has a current contract is listed. The contract verification is made by looping through the CONTRACT NUMBER multiple (#6) in the VENDOR file (#440) and checking the EXPIRATION DATE (#1). If there is an entry in the FCP (#1) multiple for the selected item and any of the FCP entries have an entry in their PURCHASE ORDER (#1) multiple, the user is offered a procurement history. They can enter a date from which they wish to view the history. They must also select an FCP. For each purchase order that passes the criteria, the PURCHASE ORDER NUMBER (#.01), VENDOR (#5), P.O. DATE (#.1), QUANTITY (#40,#2) (LINE ITEM NUMBER located using the "AE" x-ref in the ITEM (#40) multiple), UNIT OF PURCHASE (#3), TOTAL COST(#15), and QUANTITY PREVIOUSLY RECEIVED (#11) are displayed. Average ordered/month, total ordered, and total cost are also listed. If the MANDATORY SOURCE (#10) for the selected item is flagged in the VENDOR file (#440) with an "S" in the SUPPLY WHSE. INDICATOR (#.05), then the user is informed that the Supply Warehouse is the mandatory source. Using the "AD" x-ref in the INVENTORY TRANSACTION file (#445.2) a check is made for any distribution by the warehouse of this item. If procurement history exists, the user is informed and allowed to enter a date from which to view the history. By looping through the "AD" x-ref in #445.2 and checking the TRANSACTION ID (#1)?1"R".N and the DATE POSTED (#2.5) is not less than the user entered date, a history is displayed. From the INVENTORY TRANSACTION file (#445.2), the DATE POSTED (#2.5), TRANSACTION/P.O. NUMBER (#410), -QUANTITY (#6), PACKAGING UNIT (#5), SELLING UNIT PRICE (#8), and OTHER INVENTORY POINT AFFECTED (#14) are displayed. The Unposted Procurement History and Posted Drug Procurement History options are an effort to restore some of the drug accountability lost with the disappearance of the LOG 036 report. For the Unposted Procurement History, the user is asked to select a month to review. A loop through the PROCUREMENT & ACCOUNTING TRANSACTION file (#442), using the P.O. DATE ("AB") x-ref collects PO's for the user selected month. If the COST CENTER (#2) = 822400 (Pharmacy) and the SUPPLY STATUS (#.5)>14 & <45 (basically ordered), the PO's are sorted into ^TMP by Station/FCP. For each Station/FCP the PO's are listed, displaying PURCHASE ORDER NUMBER (#.01), P.O. DATE (#.1), FCP(#1), VENDOR (#5), and TOTAL AMOUNT (#91). While looping through these PO's another ^TMP is created, sorted by the DESCRIPTION (#1) of each ITEM (#40) on each PO. The user is asked if they would like to print item totals. If so, an alphabetical listing occurs displaying each ITEM's (#40) DESCRIPTION (#1) and REPETITIVE (PR CARD) NO. (#1.5) and each PURCHASE ORDER NUMBER (#.01), P.O. DATE (#.1), FCP (#1), QUANTITY (#40,#2), ACTUAL UNIT COST (#40,#5), and TOTAL COST (#40,#15). Finally, the user is if they would like a list of high dollar items. They are invited to enter a cut-off dollar amount and each item exceeding that amount is listed beginning with the highest total cost. The total cost was determined by totaling the TOTAL COST (#40,#15) amounts for each item listed in the previous display and building a ^TMP to sort from high to low. Each ITEM's (#40) DESCRIPTION (#1), total TOTAL COST (#15), and Station/FCP is shown. The Posted Drug Procurement History option uses the TYPE OF INVENTORY POINT ("AC") x-ref in the GENERIC INVENTORY file (#445) to locate a "W" or the warehouse inventory. A loop through the INVENTORY ITEM (#1) multiple, using the ITEM NO. (#.01) to check in the ITEM MASTER (#441) file for a FSC (#2) = 6505 (Federal Supply Classification for drugs) isolates the warehouse drugs in ^TMP. Looping through ^TMP a check is made using the INVENTORY POINT ("AD") x-ref in the INVENTORY TRANSACTION (#445.2) file to isolate items that have had distribution (TRANSACTION ID (#1)?"R".N) and fall within the user selected month (DATE POSTED (#2.5)). These transactions are sorted by the OTHER INVENTORY POINT AFFECTED (#14) and the OTHER INVENTORY POINT AFFECTED (#14) , -QUANTITY (#6), QUANTITY (#410,#10,#2) obtained by using the TRANSACTION /P.O. NUMBER (#445.2,#410), PACKAGING UNIT (#5), SELLING UNIT PRICE (#8), total cost (-QUANTITY (#6) * SELLING UNIT PRICE (#8)), DATE POSTED (#2.5), and TRANSACTION/P.O. NUMBER (#410). Similar to the Unposted Procurement History, a high dollar sort is also offered. As stated in the opening paragraph, the Connection Menu lays the groundwork for an interface with the IFCAP Generic Inventory Package. Phase two of this process is contained in a Pharmacy Location Menu. With this menu the Pharmacy user will create and edit the parameters of a Drug Accountability location such as Inpatient, Outpatient, or a Combined (IP/OP) operation. The purpose of the interface is to allow the receiving that occurs in the Inventory Package to pass the converted dispensing unit quantity of a connected drug (ITEM/DRUG file) from a Generic Inventory point (#445) to a Drug Accountability location (#58.8). To establish a direct link between these two files, a PRIMARY INVENTORY POINT field exists in the DRUG ACCOUNTABILITY STATS file (#58.8). This field points to the GENERIC INVENTORY file (#445) uses the TYPE OF INVENTORY POINT (#.7) = "P" and COST CENTER (#.9) = 822400 (Pharmacy) fields as screens. The input transform also contains a call to ^PSAUTL where the "E" x-ref in #58.8 is checked to prevent the linking of one primary inventory point to more than one DA location. The Set up/edit a Pharmacy Location option allows the user to edit this link. If a DA location (#58.8)is linked to an Inventory point (#445), the INVENTORY ITEMS (#1) are checked both against the "AB" x-ref in the DRUG (#50) file and the "C" x-ref in the DA (#58.8) file to see if all Inventory items are tracked in DA. If not the user is given the ability (^DIE) to add Inventory items to the DA location. The Display Location option shows the PRIMARY INVENTORY POINT (#11) currently linked to the selected DA location. The Inventory Interface sub-menu contains three report options and a populate option. The Report of Inventory items' link to DRUG file displays from a selected GENERIC INVENTORY point (#445), selection screened by COST CENTER (#.9) = 822400 and TYPE OF INVENTORY POINT (#.7) = "P", the ITEM NO. (#445,#1,#.01), either the DESCRIPTION (#.7) or from the ITEM MASTER file (#441), the SHORT DESCRIPTION (#.05)and if connected the DRUG (#50) name. The Loadable Inventory Items Report operates exactly the same, however, only lists connected items. The Populate Pharmacy Location with Inventory items option uses the same criteria and if a connected drug within an inventory point does not yet exist in the DRUG (#10) multiple in the selected DA location (#58.8), a ^DIE stuff occurs with a list of drugs loaded displayed at a user selected device. The Display Drugs Not Loaded in Primary option loops through the DRUG (#10) multiple in a selected DA location (#58.8) and using the "AB" x-ref in the DRUG (#50) file, checks the "AE" x-ref in the GENERIC INVENTORY (#445) file for the existance of each drug in the linked Primary Inventory Point. Those drugs not found in the Inventory point are displayed along with their ITEM MASTER (#441) file NUMBER (#.01) and SHORT DESCRIPTION (#.05). CONDENSED DATA DICTIONARY---DRUG FILE (#50) VERSION: 6 STORED IN: ^PSDRUG( 01/26/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: ITEM NUMBER(AB) FILE STRUCTURE FIELD FIELD NUMBER NAME .001 NUMBER (NJ5,0), [ ] .01 GENERIC NAME (RF), [0;1] 6 FSN (F), [0;6] 12 ORDER UNIT (P51.5'), [660;2] 13 PRICE PER ORDER UNIT (NJ7,2), [660;3] 14.5 DISPENSE UNIT (F), [660;8] 15 DISPENSE UNITS PER ORDER UNIT (NJ4,0), [660;5] 16 PRICE PER DISPENSE UNIT (NJ6,2), [660;6] 17 SOURCE OF SUPPLY (F), [660;7] 31 NDC (FX), [2;4] 100 INACTIVE DATE (D), [I;1] 441 IFCAP ITEM NUMBER (Multiple-50.0441), [441;0] .01 ITEM NUMBER (M*P441'X), [0;1] CONDENSED DATA DICTIONARY---ITEM MASTER FILE (#441)UCI: LTL,VAA STORED IN: ^PRC(441, 01/26/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: SHORT DESCRIPTION(AC) INACTIVATED ITEM?(AD) NUMBER(B) NSN(BA) NSN(BB) SHORT DESCRIPTION(C) VENDOR STOCK #(D) NDC(F) NSN(G) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 NUMBER (RNJ6,0X), [0;1] .05 SHORT DESCRIPTION (RFX), [0;2] .1 DESCRIPTION (Multiple-441.02), [1;0] .01 DESCRIPTION (W), [0;1] 1 FCP (Multiple-441.03), [4;0] .01 FCP (RFX), [0;1] 1 PURCHASE ORDER (Multiple-441.04), [1;0] .01 PURCHASE ORDER (P442'X), [0;1] 3 PREFERRED VENDOR (*P440'), [0;3] 2 FSC (RP441.2'), [0;3] 5 NSN (FX), [0;5] 6 VENDOR (Multiple-441.01), [2;0] .01 VENDOR (MP440X), [0;1] 1 UNIT COST (RNJ10,3), [0;2] 1.5 UNIT OF PURCHASE (RP420.5'), [0;7] 1.6 PACKAGING MULTIPLE (RNJ6,0), [0;8] 2 CONTRACT (NJ6,0XO), [0;3] 2.2 CONTRACT EXP. DATE (CJ8), [ ; ] 2.5 DATE OF UNIT PRICE (RD), [0;6] 3 VENDOR STOCK # (FX), [0;4] 4 NDC (FX), [0;5] 8 MINIMUM ORDER (NJ6,0), [0;12] 9 REQUIRED ORDER MULTIPLE (NJ6,0), [0;11] 9 LAST VENDOR ORDERED (P440'), [0;4] 10 MANDATORY SOURCE (*P440'), [0;8] 14 DATE ITEM CREATED (D), [0;9] 15 CREATED BY (P3'), [0;11] 16 INACTIVATED ITEM? (S), [3;1] CONDENSED DATA DICTIONARY---VENDOR FILE (#440) UCI: LTL,VAA STORED IN: ^PRC(440, 01/26/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: SUPPLY WHSE. INDICATOR(AC) NAME(AD) INACTIVATED VENDOR(AE) NAME(B) SYNONYM(C) FILE STRUCTURE FIELD FIELD NUMBER NAME .001 NUMBER (NJ6,0), [ ] .01 NAME (RFX), [0;1] .05 SUPPLY WHSE. INDICATOR (SX), [0;11] 6 CONTRACT NUMBER (Multiple-440.03), [4;0] .01 CONTRACT NUMBER (MFX), [0;1] 1 EXPIRATION DATE (RD), [0;2] CONDENSED DATA DICTIONARY---NEW PERSON FILE (#200) VERSION: 6.5 STORED IN: ^VA(200, 01/27/93 -------------------------------------------------------------------------- FILE STRUCTURE FIELD FIELD NUMBER NAME .01 NAME (RFX), [0;1] .132 OFFICE PHONE (F), [.13;2] CONDENSED DATA DICTIONARY---PROCUREMENT & ACCOUNTING TRANSACTIONS FILE (#442) STORED IN: ^PRC(442, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: P.O. DATE(AB) FCP(AC) ISSUE VOUCHER NO.(SUPPLY)(AD) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 PURCHASE ORDER NUMBER (RFX), [0;1] .1 P.O. DATE (RDX), [1;15] .5 SUPPLY STATUS (*P442.3'), [7;1] 1 FCP (RFX), [0;3] 2 COST CENTER (FX), [0;5] 5 VENDOR (R*P440X), [1;1] 40 ITEM (Multiple-442.01), [2;0] .01 LINE ITEM NUMBER (RMNJ2,0X), [0;1] 1 DESCRIPTION (Multiple-442.05), [1;0] .01 DESCRIPTION (W), [0;1] 1.5 REPETITIVE (PR CARD) NO. (*P441'X), [0;5] 2 QUANTITY (RNJ9,2), [0;2] 3 UNIT OF PURCHASE (RP420.5'X), [0;3] 5 ACTUAL UNIT COST (RNJ9,2X), [0;9] 11 QUANTITY PREVIOUSLY RECEIVED (NJ9,2), [2;8] 15 TOTAL COST (RNJ9,2), [2;1] 91 TOTAL AMOUNT (RNJ10,2), [0;15] CONDENSED DATA DICTIONARY---INVENTORY TRANSACTION FILE (#445.2) STORED IN: ^PRCP(445.2, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: DATE POSTED(ABEG) ITEM NO.(AC) INVENTORY POINT(AD) ITEM NO.(AE) INVENTORY POINT(ANXT) INVENTORY POINT(B) TRANSACTION/P.O. NUMBER(C) TRANSACTION ID(T) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 INVENTORY POINT (RP445'), [0;1] 1 TRANSACTION ID (RF), [0;2] 2.5 DATE POSTED (D), [0;17] 5 PACKAGING UNIT (F), [0;6] 6 QUANTITY (NJ6,0), [0;7] 8 SELLING UNIT PRICE (NJ11,3), [0;9] 14 OTHER INVENTORY POINT AFFECTED (P445'), [0;18] 410 TRANSACTION/P.O. NUMBER (F), [0;19] CONDENSED DATA DICTIONARY---GENERIC INVENTORY FILE (#445) STORED IN: ^PRCP(445, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: DISTRIBUTION POINT(AB) TYPE OF INVENTORY POINT(AC) INVENTORY USER(AD) ITEM NO.(AE) ABBREVIATED NAME(AF) KEEP PERPETUAL INVENTORY?(AG) INVENTORY POINT(B) INVENTORY POINT(C) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 INVENTORY POINT (RFX), [0;1] .7 TYPE OF INVENTORY POINT (R*SX), [0;3] .9 COST CENTER (P420.1'), [0;7] 1 INVENTORY ITEM (Multiple-445.01), [1;0] .01 ITEM NO. (MP441'X), [0;1] CONDENSED DATA DICTIONARY---DRUG ACCOUNTABILITY STATS FILE (#58.8) STORED IN: ^PSD(58.8, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: DRUG(C) PRIMARY INVENTORY POINT(E) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 PHARMACY LOCATION (RF), [0;1] 10 DRUG (Multiple-58.8001), [1;0] .01 DRUG (MR*P50'X), [0;1] 11 PRIMARY INVENTORY POINT (*P445'X), [0;6] This DBIA is effective until 18 months following Drug Accountability V2.0. |
||||
| 227 | DBIA227-A | File | IFCAP | 1993/05/05 | APPROVED | Active | Private | 445 | Prosthetics is granted permission to make the following calls to the IFCAP package (GIP and 1358 Modules). As stated below this is until the next version of either IFCAP or Prosthetics. For GIP (Items 1 - 3): Item 1 is needed so that we can check to see if an item that is being returned from loan is in an inventory point, so that it can be placed back into inventory. Item 2 is needed to so that we can do a lookup to make sure that the user returning a loaned item is an Inventory User. Item 3 is needed so that we can make sure that the user returning an item is an Inventory User for that particular Inventory Point. Item 1 Description: Read Only access to File #445, GENERIC INVENTORY, to look at the cross-referenced node ^PRCP(445,"AE",ITEM#,DA). Item 2 Description: Read Only access to File #445, GENERIC INVENTORY, so that we can look at the "AD" cross-reference in the file. Item 3 Description: Read Only access File #445, field 6, INVENTORY USER. Item 5 DIC lookup on File #445 Generic Inventory. Read access only to the .01 field. The variable PRCPPRIV may be set by Prosthetics. |
|||
| 245 | DBIA245 | Other | IFCAP | 1993/06/28 | APPROVED | Active | Private | Engineering version 7.0 has permission to export the following: FILE 446.4 BARCODE PROGRAM with two entries (ENNX and ENPM) FILE 446.6 SPECIALTY COMMANDS with one entry (TRAKKER 9440) These files and entries are necessary for uploading equipment data from portable bar code readers into the Engineering database. |
||||
| 246 | DBIA246 | Other | IFCAP | 1993/06/28 | APPROVED | Active | Private |
Version 4.0 of IFCAP will call an Engineering routine whenever an Engineering work order is entered into the SORT GROUP of a Control Point Activity Transaction (Field 49 of File 410). The effect of this call will be to enter a pointer to the Control Point Activity Transaction in the Work Order File and to update the work order status. MUMPS cross-reference AR on Field 49 of File 410 will call ACCX^ENLIB2. Before calling this foreign routine, the IFCAP cross-reference will make sure that ^ENG("VERSION") is greater than 6.4. This insures the existence of the foreign routine. |
||||
| 259 | DBIA259 | Routine | IFCAP | 1993/08/03 | APPROVED | Active | Controlled Subscription | Drug Accountability, V2.0, has established agreement with IFCAP to make the following calls: IFCAP inventory provides a Primary Inventory Point with the SPECIAL INVENTORY POINT TYPE = "D" for Drug Accountability, the ability to update a Drug Accountability Location with all receiving activity. IFCAP has added two new fields to the INVENTORY ITEM multiple in the GENERIC INVENTORY file (#445), the DISPENSING UNIT and DISPENSING UNIT CONV FACTOR. Each item that a Primary Inventory Point receives, the IFCAP routines PRCPPOL1, PRCPWPL4, PRCPWPP3, and PRCPUUIW call EN^PSAGIP to update drug accountability. It is here that Drug Accountability is called (EN^PSAGIP) passing the Primary Inventory Point, the item, the quantity*dispensing unit conv factor, the PO#, the CP transaction #, the inventory transaction #, and the total price and in some cases the NDC. Drug Accountability adds each item received to a temporary global. After the receipt is processed, the IFCAP routines PRCPAWI1, PRCPPOL1, PRCPWPL5, and PRCPWPP3 call EX^PSAGIP to complete the drug accountability update. At this time a task is started, looping through the temporary global and either updating the Drug Accountability Location or building and sending a mailman message listing those items that could not be updated and why. In version 2.0 of Drug Accountability the cost center screen on the Primary Inventory pointer in the DRUG ACCOUNTABILITY STATS file (#58.8) has been replaced with the "D" for special inventory type. Also the IFCAP security variable, PRCPPRIV is used to enable this pointer. ^DD(58.8445,.01,0) = PRIMARY INVENTORY POINT(S)^M*P445'X ^PRCP(445,^0;1^S PRCPPRIV=1,DIC("S")="I $P(^(0),U,20)=""D""" D ^DIC K DIC S DIC=DIE,X=+Y K PRCPPRIV K:Y<0 X S:$D(X) DINUM=X Wherever available, calls to IFCAP extrinsics have replaced Drug Accountability version 1.0 look-ups to ^PRC globals. The IFCAP inventory routine PRCPUX1 is called extensively throughout the Drug Accountability package at the following line tags: UNITVAL(V1,V2,V3) ; unit per issue for values passed as follows ; v1=packaging multiple, v2=units da, ; v3=delimiter; UNITCODE(V1) ; get 2 character unit code from file 420.5 ; for entry v1; NSN(V1) ; return nsn for item v1; DESCR(V1,V2) ; description from inventory point or item ; master file for item v2 and inventory point ; v1; INVNAME(V1) ; inventory point name for inventory point v1; VENNAME(V1) ; return vendor name for da;global (445 or ; 440). |
PRCPUX1 | |||
| 282 | DBIA282-A | Routine | IFCAP | 1993/09/20 | APPROVED | Active | Private | PRCS58 | ||||
| 285 | DBIA285-A | File | IFCAP | 2003/09/02 | Retired | Private | 442 | Also see DBIA's 804-810 Most of the calls below are interfaces between AR and IFCAP for the creation of CALM code sheets. After all of the sites convert to FMS, these calls will no longer be needed. These calls will need to be supported in future versions of the packages or until all of the sites convert to FMS. Integration agreements between IFCAP and AR for use of tje IFCAP Vendor File 440 will be needed through-out the life of the AR package. The AR routine calls to IFCAP to support the CALM code sheets. Fields that AR routines set and/or reference in the Procurement & Accounting Transaction File (#442) of IFCAP include: 442,.01 - Purchase Order Number (0;1) 442.09 - Obligation Data sub-file 442.09,.01 - TT/DATE/REF (0;1) 442.09,1 - Obligated By (0;2) 442.09,3 - Code Sheet Number (0;4) 442,.1 - P.O. Date (1;15) 442,.02 - Method of Processing (0;2) 442,5.1 - Debtor (1;16) 442,19 - Agent Assigned P.O. (12;4) 442,19.2 - Date P.O. Assigned (12;5) 442,102 - Document Identifier/Common No. (18;3) Fiscal Year sub-file 430.01, Pat Ref. No. Field 430.01,2 (0;3) - points to Procurement & Accounting Transaction File (#442) |
||||
| 315 | DBIA315-A | Routine | IFCAP | 1993/11/01 | APPROVED | Active | Controlled Subscription | PRCS58 | ||||
| 318 | DBIA318 | Other | IFCAP | 1993/11/03 | APPROVED | Active | Private | See DBIA #315. |
||||
| 319 | DBIA319 | Routine | IFCAP | 1993/11/02 | APPROVED | Active | Private |
Version 7.0 of the Engineering Work Order Module will call IFCAP to display Control Point Activity information related to specific Engineering work orders. Routine ^ENWOD will call ^PRCSP13. Before calling this foreign routine, ^ENWOD will execute ^%ZOSF("TEST") to make sure that ^PRCSP13 exists. Upon entry into ^PRCSP13, local variable DA must contain the internal entry number of the Control Point Activity that is to be displayed. Local variable DA is not returned by ^PRCSP13. If local variables DIWL, DIWR, and/or DIWF are defined when the call to ^PRCSP13 is made, they will not be preserved. |
PRCSP13 | |||
| 353 | DBIA353 | Routine | IFCAP | 1994/02/28 | APPROVED | Active | Private | PRCPUX1 | ||||
| 375 | DBIA375 | File | IFCAP | 2003/09/02 | Retired | Private | 424 |
Request a one time DBA agreement for patch RMRP*2*4. When a Prosthetics New Purchase is initiated the estimated amount of the Purchase is calculated using the %Discount and the total cost for all items or services. On occasion the estimated amount may be a four decimal digit (e.g. 165.4321) after the calculation is done. Once the calculation is completed the New Purchase is posted to IFCAP and a 1358 Daily Record entry is created. When the Prosthetics New Purchase Estimated amount is posted to IFCAP it is rejected by Fileman because the Data Dictionary for the Authorization amount field for file 424 will only accept a two decimal digit number. A incomplete 1358 Daily Record is created and the Authorization number is passed back to the Prosthetics New Purchase. Upon Close out of the Prosthetics Purchase an error message 'Insufficient authorization funds to post payment' is displayed and the Prosthetics Purchase cannot be closed out because the estimated amount was not posted when the Purchase was initiated. Patch RMPR*2*4 corrects this problem by using $JUSTIFY to ensure that the Estimated amount for the initial Prosthetics Purchase is rounded to a two decimal digit. Patch RMPR*2*4 also has a conversion routine that will correct the Phantom 1358 entries and allow the Prosthetics Service to close out purchases associated with the incomplete 1358 Daily Record entries. The Conversion Routine RMPSCON finds all 1358 daily record entries created by the DHCP Prosthetics Package that are missing the authorization balance. Routine RMPSCON reads and updates the following fields in Files #442 (PROCUREMENT AND ACCOUNTING TRANSACTIONS), 442.3 (PURCHASE ORDER STATUS), 424 (1358 DAILY RECORD FILE), and 424.1 (1358 AUTHORIZATION DETAIL). |
||||
| 376 | DBIA376 | File | IFCAP | 1994/03/15 | APPROVED | Active | Private | 442.3 | See DBIA375. |
|||
| 377 | DBIA377 | File | IFCAP | 1994/03/15 | APPROVED | Active | Private | 424.1 | See DBIA375 |
|||
| 378 | DBIA378 | Routine | IFCAP | 1994/03/15 | APPROVED | Active | Private | 442 | See DBIA375 |
PRCH58 | ||
| 390 | DBIA390 | File | IFCAP | 1994/03/16 | APPROVED | Active | Private | 442 | See DBIA 375. |
|||
| 492 | DBIA492 | File | IFCAP | 1994/06/13 | APPROVED | Active | Private | 420.1 | DMMS units must be associated with a cost center to make it possible associate the work for the unit as gathered in DHCP with financial data contained in reports from the AAC. To this end, we request read access to the COST CENTER file (420.1). Currently the CC field is a 6 digit code with the first 4 being Cost Center and the last two being Sub-cost center. Thats how it is broken up to pass to FMS for IFCAP V5.0. Current plans are to increase the code to 8 digits. There are discussions going on between OF&IRM and VAH's CFO's office. At some point IFCAP will be changing the content of the file. When that happens, this DBIA will have to be revisited. |
|||
| 593 | DBIA127-B | Routine | IFCAP | 1991/11/06 | APPROVED | Active | Private | This routine is used for making transactions to an already existing bill. This would be used, for example, if a Pharmacy Co-Pay was charged and later canceled because the patient did not receive the RX. INPUT Variable: X $P1: Transaction type. This is the pointer to the Accounts Receivable Trans.Type file (430.3. Currently this program will support two types of transactions: INCREASE ADJUSTMENT Number: 1 DECREASE ADJUSTMENT Number: 21 This piece should be set to the internal value for these types, this may be found by direct accessing the "AC" cross-reference on the Number to determine the internal value. $P2: Amount. This would be the amount of the transaction. This number must be greater than 0 and less than 9999999.99. $P3: Bill Number. This must be the .01 value of the bill from the Accounts Receivable file (430) and must be 10 characters in length. (ex: 503-K10001). $P4: User. this is the person who is making the adjustment. Pointer to the User file (3). $P5: Adjustment Date. This is the internal VA FileMan date when the adjustment occurred. $P6: Reason. This is the free text reason that the adjustment took place (optional). Output Variable: Y $P1: Success flag. Equals 1 if successful, -1 if unsuccessful $P2: Error Code. This is the error code from the IB Error file. $P3: Addition Text. If additional text is required to describe the error then it is in the third piece. |
PRCASER1 | |||
| 594 | DBIA127-C | File | IFCAP | 1991/11/06 | APPROVED | Active | Private | 430.2 | Integrated Billing has permission to access the following fields: |
|||
| 595 | DBIA127-D | File | IFCAP | 1991/11/06 | Retired | Private | 430 | Look-up of the Accounts Receivable file (430) by Integrated Billing for an option to print by Coarge ID (bill number). |
||||
| 596 | DBIA127-E | Other | IFCAP | 1991/11/06 | APPROVED | Active | Private | Export of data, files, functions, options, routines, templates and security keys by Version 1 of Integrated Billing as necessary to successfully implement the Pharmacy Co-pay project as follows: File Data ACCOUNTS RECEIVABLE (partial) (430) NO ACCOUNTS RECEIVABLE CATEGORY (430.2) YES ACCOUNTS RECEIVABLE TRANS.TYPE (430.3) YES ACCOUNTS RECEIVABLE FORM LETTER (434) YES BATCH TRANSACTION (435) YES AR DEBTOR (412) NO VENDOR (partial) (440) NO Functions PRCADDR1, PRCADDR2, PRCACITY, PRCASTATE, PRCAZIP Security keys PRCAY PAYMENT SUP Options PRCAL LIST MENU Accounts Receivable Status Reports PRCAD REPORT MENU Report Menu for Accounts Receivable PRCA CLERK`MENU Clerk's AR Menu PRCAC TR PAYMENT Enter a Payment Transaction PRCAC PROFILE Profile of Accounts Receivable PRCAE FOLLOW-UP Follow-up Letter Menu PRCAC TRANSACTION Adjustment to Accounts Receivable PRCAC CHANGE Update Accounts Receivable PRCAA SET/AUDIT NEW BILL Audit/Set up a New Accounts Receivable PRCAD RECON CASHIER Agent Cashier Report PRCAL REFER DC DC Pending Referral AR Listing PRCAL REF DOJ DOJ Pending Referral AR Listing PRCAL STATUS LIST Status listing for Bills PRCAB PRINT BILLS New Bill Forms Print PRCAA OLD BILL Establish/Edit Old Bills PRCAC TRANS PROFILE Transaction Profile PRCAL MEANS LIST Means Test AR List PRCAL OTHER LIST Other Category AR List PRCA FORWARD IRS OFFSETS Forward IRS OFFSETs to Austin PRCAY CREATE/EDIT BATCH Create/Edit Payment Batch PRCAT CREATE CALM Create CALM Code Sheet for Other AR Transactions PRCAT LIST NEW TRANSACTION Other Bills pending CALM Transaction (Print) PRCAT PAT REF NUMBER AR (New) Processing PRCAT USER AR - Accounts Receivable Menu PRCAT PAT COMMON Establish PAT Common Number Series PRCAY APPROVE BATCH Approve Batch PRCAY POST TRANS Post an approved batch to A/R PRCAY MASTER Agent Cashier PRCAY BATCH STATUS Batch Status Report PRCAY ENTER A PAYMENT Enter a Payment (Agent Cashier) Routines PRCAAD, PRCABIL, PRCABD, PRCABP1, PRCABP2, PRCABP3, PRCABP31, PRCACLM, PRCADJ, PRCADR, PRCADR1, PRCALST, PRCALT, PRCALT1, PRCAOFF, PRCAOFF2, PRCAPAT, PRCAPAY, PRCAPAY1, PRCAPAY2, PRCAPCL, PRCAPRO, PRCAPTR, PRCAREPT, PRCARLT, PRCASER, PRCASER1 , PRCASTA, PRCASVC3, PRCASVC4, PRCASVC5, PRCAUDT, PRCAUT1, PRCAWO, PRCAY, PRCAYAPP, PRCAYE, PRCAYHLP, PRCAYPT, PRCAYUT, PRCFACX0 Templates Type File --------------------------------------- PRCABILLVEN Input VENDOR PRCA FY ADJ2 BATCH Input AR TRANSACTION PRCA FY ADJ1 Input AR TRANSACTION PRCA FY ADJ2 Input AR TRANSACTION PRCA BATCH PAYMENT Input AR TRANSACTION PRCA PAYMENT Input AR TRANSACTION PRCA OLD SET Input ACCOUNTS RECEIVABLE PRCA SET Input ACCOUNTS RECEIVABLE PRCASVC STATUS Input ACCOUNTS RECEIVABLE PRCASV REL Input ACCOUNTS RECIEVABLE PRCAE AUDIT Input ACCOUNTS RECEIVABLE PRCAC LOCATE DEBTOR Input ACCOUNTS RECEIVABLE PRCAY TRANSACTION EDIT Input BATCH TRANSACTION PRCAY BATCH STATUS Print BATCH TRANSACTION PRCAR CASH Print AR TRANSACTION |
||||
| 597 | DBIA127-F | Other | IFCAP | 1991/11/06 | Retired | Private | Updating of pointer values in data by Version 1 of Integrated Billings post-initialization routine as necessary. |
|||||
| 598 | DBIY127-G | File | IFCAP | 2003/09/02 | Retired | Private | 412 | Direct reference to the global ^PRC(412 in the Version 1 post initialization routine to set the STATEMENT DAY field. |
||||
| 599 | DBIA127-H | File | IFCAP | 1991/11/06 | APPROVED | Active | Private | 430.6 | Direct reference to the global ^PRCA(430.6, to add a new entry in version 1 on the post initialization routine. Direct refe rence to global ^PRCA(430.6 to determine and set pointer values in the ACCOUNTS RECEIVABLE CATEGORY file and in the IB ACTION TYPE file in the post initialization routine. |
|||
| 600 | DBIA127-I | File | IFCAP | 1991/11/06 | APPROVED | Active | Private | 430.3 | Direct reference to global ^PRCA(430.3, to determine the internal number of the decrease adjustment type when doing a decrease adjustment and to determing the internal number of the increase adjustment type when doing an increase adjustment type (required for input to supported call PRCASER1). |
|||
| 607 | DBIA140-B | Routine | IFCAP | 1992/01/07 | Retired | Private | 2. ^PRCS58CC - Support for the close/complete action on a 1358 daily record. Variables: PRCSX - 5-piece variable delimited by '^' piece 1 = Internal daily reference no. piece 2 = Date/Time (internal format) piece 3 = Amount of Payment piece 4 = Comments (limited to 78 characters) piece 5 = Completed flag Y - a one or two '^'-piece delimited variable where piece 1 = 0 (zero) or 1 (0ne) piece 2 = a free-text error message. |
PRCS58CC | ||||
| 608 | DBIA140-C | File | IFCAP | 1992/01/07 | Retired | Private | 420.5 | 3. Read access to file 420.5 (Unit of Issue) |
||||
| 609 | DBIA140-D | File | IFCAP | 1992/01/07 | Retired | Private | 440 | 4. Prosthetics to have Read, Write, and LAYGO access to files 440 (vendor) and 441 (Item Master), thru options PRCHPC ITEM EDIT and PRCHRC VEN EDIT, restricted through assignment of the RMPRSUPERVISOR key. This key will be issued to a prosthetics clerk who has completed training by Supply Service on the IFCAP conventions and procedures for entering data into the above named files. |
||||
| 610 | DBIA140-E | File | IFCAP | 1992/01/07 | Retired | Private | 441 | 4. Prosthetics to have Read, Write, and LAYGO access to files 440 (vendor) and 441 (Item Master), thru options PRCHPC ITEM EDIT and PRCHRC VEN EDIT, restricted through assignment of the RMPRSUPERVISOR key. This key will be issued to a prosthetics clerk who has completed training by Supply Service on the IFCAP conventions and procedures for entering data into the above named files. |
||||
| 611 | DBIA140-F | File | IFCAP | 1992/01/07 | Retired | Private | 410 | Read access to file 410 (Control Point Activity) - Access required to check the status of 2237's. |
||||
| 682 | DBIA198-B | File | IFCAP | 1992/11/24 | APPROVED | Active | Private | 442 | In an effort to provide a receiving mechanism for Controlled Substances module, several look-ups and pointers are necessary for an interim interface. For Purchase Order receipts, a lookup to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442, screened by cost center [822400] is used. For Issue Receipts, a lookup occurs, screened by cost center [822400], in CONTROL POINT ACTIVITY file 410. A connection between the DRUG file 50 and ITEM MASTER file 441 is crucial for posting receipt information. This may be a one-to-many relationship and therefore involves the creation of a multiple IFCAP ITEM NUMBER field (#50.0441) in the DRUG file 50 pointing to the ITEM MASTER file 441. This field includes an input transform similar to that found in the NDC field in the ITEM MASTER file 441 preventing the linking of the same item to more than one drug. It also includes an 'AB' whole file cross-reference. Pointer to CONTROL POINT ACTIVITY file 410 Pointer to ITEM MASTER file 441 Pointer to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442 References information (Read only) from PROCUREMENT & ACCOUNTING TRANSACTIONS file 442 .01 PURCHASE ORDER NUMBER .6 PARTIAL 40 ITEM .01 LINE ITEM NUMBER 1 DESCRIPTION 1.5 REPETITIVE (PR CARD) NO. 3.1 PACKAGING MULTIPLE 9 VENDOR STOCK NUMBER 5 ACTUAL UNIT COST 20 DATE RECEIVED 1 QTY BEING RECEIVED "AB" X-REF ON P.O. DATE (FIELD .1) IFCAP files are used solely to gather and display receipt information and so the Controlled Substances files 58.8 and 58.81 can accumulate a receipt history. DURATION: Till otherwise agreed, when the GIP & Drug Accountability interf ace is available |
|||
| 698 | DBIA225-B | File | IFCAP | 1993/04/21 | APPROVED | Active | Private | 445 | Read only access to the .01 field of File 445 to get the IEN of the Inventory Point so that we can set it in variable PRCP("I") and use it to a call to routine PRCPUSA. The look-up to the .01 field would be through a Fileman call to ^DIC, and a successful lookup would return the IEN which would then be used in setting the above IFCAP variable. |
|||
| 704 | DBIA227-B | File | IFCAP | 1993/05/05 | APPROVED | Active | Private | 442 | Prosthetics is granted permission to make the following calls to the IFCAP package (GIP and 1358 Modules). As stated below this is until the next version of either IFCAP or Prosthetics. For the 1358 Module: Item 4 is needed so that Prosthetics can calculate the amount remaining on the original 1358 obligation by subtracting Field #94 from field #96. Item 4 Description: Read Only access to File #442, PROCUREMENT & TRANSACTIONS FILE, fields 94, ACTUAL 1358 BALANCE, and 96, ESTIMATED 1358 BALANCE. |
|||
| 797 | DBIA282-B | Routine | IFCAP | 1993/09/20 | APPROVED | Active | Private | PRCS58 | ||||
| 798 | DBIA282-C | Routine | IFCAP | 1993/09/20 | APPROVED | Active | Private | PRCS58CC | ||||
| 799 | DBIA282-D | File | IFCAP | 1993/09/20 | APPROVED | Active | Controlled Subscription | 420.5 | Read access to file 420.5 (Unit of Issue) |
|||
| 800 | DBIA282-E | File | IFCAP | 1993/09/20 | APPROVED | Active | Controlled Subscription | 440 | Prosthetics to have Read, Write, and LAYGO access to files 440 (vendor) and 441 (Item Master), through options PRCHPC ITEM EDIT and PRCHRC VEN EDIT, restricted through assignment of the RMPRSUPERVISOR key. This key will be issued to a prosthetics clerk who has completed training by Supply Service on the IFCAP conventions and procedures for entering data into the above named files. Read access to file 440 VENDOR FILE - Field #.01 NAME and Field #6 CONTRACT NUMBER MULTIPLE, global node ^PRC(440,D0,4) and Global Node ^PRC(440,D0,4,D1,0). Display Vendor Name and check for valid or expired contract number. |
|||
| 801 | DBIA282-F | File | IFCAP | 1993/09/20 | APPROVED | Active | Controlled Subscription | 441 | Prosthetics to have Read, Write, and LAYGO access to files 440 (vendor) and 441 (Item Master), through options PRCHPC ITEM EDIT and PRCHRC VEN EDIT, restricted through assignment of the RMPRSUPERVISOR key. This key will be issued to a prosthetics clerk who has completed training by Supply Service on the IFCAP conventions and procedures for entering data into the above named files. Read access to file 441 IFCAP ITEM MASTER FILE Field #.05 SHORT DESCRIPTION, global node ^PRC(441,D0,0) and Index ^PRC(441,"C",X,DA). Display IFCAP ITEM MASTER Short Description. |
|||
| 802 | DBIA282-G | File | IFCAP | 1993/09/20 | APPROVED | Active | Controlled Subscription | 410 | Read access to file 410 (Control Point Activity) - Access required to check the status of 2237's. |
|||
| 803 | DBIA282-H | File | IFCAP | 1993/09/20 | APPROVED | Active | Private | 442 | Read access to file 442 PROCUREMENT & ACCOUNTING TRANSACTION To get Obligation number through a ^DIC lookup. Obligation # is returned in Y(0). |
|||
| 804 | DBIA285-B | File | IFCAP | 1993/10/05 | APPROVED | Active | Private | 423 | CALM/LOG Code Sheet File (#423) of IFCAP sets and/or references to the entire file are under this agreement. Access to the CALM/LOG Code Sheet File 423 and the Procurement & Accounting Transaction File 442 is needed to repoint AR Debtor File 412 pointers to the AR V4.0 AR Debtor File 340. (included in inits) |
|||
| 805 | DBIA285-C | File | IFCAP | 1993/10/05 | APPROVED | Active | Private | 440 | AR Debtor File 340 Debtor Field .01V5 (0;1) - variable pointer to the Vendor File (#440) |
|||
| 806 | DBIA285-D | File | IFCAP | 1993/10/05 | APPROVED | Active | Private | 442 | AR File 430 Fiscal Year sub-file 430.01, Pat Ref. No. Field 430.01,2 (0;3) - points to Procurement & Accounting Transaction File (#442) |
|||
| 807 | DBIA285-E | Routine | IFCAP | 1993/10/05 | APPROVED | Active | Private | Appropriation Symbol Field 430.01,3 (0;4) - input transform calls EN1^PRCHPAT |
PRCHPAT | |||
| 808 | DBIA285-F | File | IFCAP | 1993/10/05 | APPROVED | Active | Private | 420.3 |
Ald Code Field 430.01,4 (0;5) - points to the Ald Code File (#420.3) Ald Code Field 4 (0;5) - points to the Ald Code File (#420.3) |
|||
| 809 | DBIA285-G | File | IFCAP | 1993/10/05 | APPROVED | Active | Private | 420.5 | Unit Field 430.02,5 (0;5) - points to the Unit of Issue File (#420.5) |
|||
| 810 | DBIA285-H | File | IFCAP | 1993/10/05 | APPROVED | Active | Private | 411 | The AR V4.0 PRCACV* Conversion routines call to IFCAP. Access to the Admin. Activity Site Parameter File, #411, is needed to populate the AR V4.0 AR Site Parameter File 342. Admin. Activity Site Parameter File 411 Station Number Filed .01 (0;1) - Global reference Primary Station Field 21 (0;2) - "AC" Cross-reference global reference Admin. Activity Site Parameter File 411, Printer Location sub-file 411.02 Printer Location Field 411.02,.01 (0;1) - Global references UB for UB-82 and A for Accounts Receivable Device Field 411.02,1 (0;2) - Global reference |
|||
| 831 | DBIA315-B | Routine | IFCAP | 1993/11/01 | APPROVED | Active | Controlled Subscription | PRCS58CC | 2012/04/26 | |||
| 832 | DBIA315-C | Routine | IFCAP | 1993/11/01 | APPROVED | Active | Private | PRCSUT31 | ||||
| 954 | DBIA954 | Routine | IFCAP | 1994/08/19 | APPROVED | Active | Controlled Subscription | PRCSREC2 | ||||
| 988 | LIBRARY USE OF VENDOR FILE | File | IFCAP | 1994/09/26 | APPROVED | Retired | Private | 440 |
************************************************************************ The Library package was decommissioned with LBR*2.5*15. This ICR was retired with the release of the Library patch. ************************************************************************ |
|||
| 1020 | PBM | File | IFCAP | 1998/10/23 | APPROVED | Active | Private | 442 | All the fields are read from the file using Fileman calls, except the P.O. DATE. The P.O. DATE's "AB" cross reference is used for sorting purposes. |
|||
| 1021 | D&PPM | File | IFCAP | 1998/06/01 | APPROVED | Active | Private | 445 | ||||
| 1022 | D&PPM | File | IFCAP | 1994/10/12 | APPROVED | Active | Private | 420.5 | ||||
| 1198 | IFCAP FUND CONTROL POINT INFORMATION | Routine | IFCAP | 1995/04/17 | APPROVED | Active | Private | This integration agreement allows Generic Code Sheets (version 2.0) to call IFCAP routines from within distributed input templates. The calls will return fund control points and information pertaining to the fund control point which is used to build the FMS code sheets. |
PRCSUT | |||
| 1483 | DBIA1483 | File | IFCAP | 1996/02/26 | APPROVED | Active | Private | 420.8 | Engineering Package is given permission to point to File #420.8 SOURCE CODE. |
|||
| 1484 | DBIA1484 | File | IFCAP | 1996/02/26 | APPROVED | Active | Private | 420.1 | The Engineering Package is given permission to point to File 420.1. (COST CENTER). |
|||
| 1485 | DBIA1485 | File | IFCAP | 1996/02/26 | APPROVED | Active | Private | 441.2 | The Engineering Package is given permission to point to File 441.2. (FEDERAL SUPPLY CLASSIFICATION) |
|||
| 1497 | DBIA1497 | File | IFCAP | 1996/02/26 | APPROVED | Active | Private | 420.2 | The Engineering Package is given permission to point to File 420.2. (BUDGET OBJECT CODE). |
|||
| 1498 | DBIA1498 | File | IFCAP | 1996/02/26 | APPROVED | Active | Private | 440 | The Engineering Package is given permission to point to File 440 (Vendor). |
|||
| 1499 | DBIA1499 | File | IFCAP | 1996/02/26 | APPROVED | Active | Private | 442 | The Engineering package is given permission to read data from the following fields in file #442 (PROCUREMENT AND ACCOUNTING TRANSACTIONS) using FileMan utilities and to loop through the global nodes of the ITEM and BOC multiples to obtain the internal entry number of the multiple for use in FileMan calls. |
|||
| 1500 | Returns Accounting Data | Routine | IFCAP | 1996/02/26 | APPROVED | Active | Private | The Engineering Package is given permission to call $$ACC^PRC0C. |
PRC0C | |||
| 1520 | DBIA1520-A | Routine | IFCAP | 1996/04/04 | APPROVED | Active | Private | The NX Module (Equipment/Turn-In) requests permission to use IFCAP program PRCFSITE to set special IFCAP variables used in the package. |
PRCFSITE | |||
| 1521 | DBIA1520-B | Routine | IFCAP | 1996/04/04 | APPROVED | Active | Private | The NX module (Equipment/Turn-In) requests permission to reference program PRCSEB when creating 2237s. |
PRCSEB | |||
| 1522 | DBIA1520-C | Routine | IFCAP | 1996/04/04 | APPROVED | Active | Private | This agreement will allow the NX (Equipment/Turn-In) module to call IFCAP routines from within a distributed input template, used to create 2237s. The calls will return fund control points and information pertaining to the fund control point used to create the 2237. |
PRCSUT | |||
| 1523 | DBIA1520-D | Routine | IFCAP | 1996/04/04 | APPROVED | Active | Private | This agreement will allow the NX (Equipment/Turn-In) module to call the IFCAP transaction utility program when creating 2237s which will create the record in file 410 and process all checks on creating a 2237. |
PRCSUT3 | |||
| 1524 | DBIA1520-E | File | IFCAP | 1996/04/04 | APPROVED | Active | Private | 410 | The NX (Equipment/Turn-In) module requests permission to reference file 410 to create/edit 2237s which are the end product of this module. Includes addition of two templates to file 410, PRCN2237 and PRCN2237E. |
|||
| 1525 | DBIA1520-F | File | IFCAP | 1996/04/04 | APPROVED | Active | Private | 440 | This agreement requests permission for the NX (Equipment/Turn-In) module to point, with read access only, to the Vendor file (440). |
|||
| 1526 | DBIA1526 | Routine | IFCAP | 1996/04/04 | Pending | Private | The NX module requests permission to use checks currently in use when creating a 2237. |
PRCSCK | ||||
| 1549 | DBIA1548-B | File | IFCAP | 1996/06/19 | APPROVED | Active | Private | 411 | The Equipment/Turn-In Request package would like access to IFCAP's file ADMIN. ACITIVITY SITE PARAMETER (#411) to identify a station for requests and 2237s. |
|||
| 1550 | DBIA1548-C | File | IFCAP | 1996/06/19 | APPROVED | Active | Private | 410.2 | A CLASSIFICATION OF REQUEST may be assigned to a 2237. The Equipment/Turn-In Request package would like to be able to assign this field early in the request package and transfer it to the 2237. |
|||
| 1551 | DBIA1548-D | File | IFCAP | 1996/06/19 | APPROVED | Active | Private | 410.7 | The SORT GROUP file (#410.7) is used as a sorting mechanism of requests to categorize their particular cost distribution for 2237s. The Equipment/Turn-In Request package would like to prompt for this information early in the request and then pass it on to the 2237. |
|||
| 1552 | DBIA1548-E | Routine | IFCAP | 1996/06/19 | APPROVED | Active | Private | The Equipment/Turn-In Request package would like permission to use PRCUSESIG to check for the electronic signature code. |
PRCUESIG | |||
| 2005 | DBIA2005 | Routine | IFCAP | 1997/04/15 | APPROVED | Active | Supported | Integrated Funds of Patient routines PRPFPURG and PRPFSCV2 are invoking an IFCAP programming call ADD^PRCGPM1. |
PRCGPM1 | |||
| 2071 | CODE INDEX (FPDS) | File | IFCAP | 1997/08/12 | APPROVED | Active | Private | 420.6 | This agreement permits FEE BASIS to point to the CODE INDEX (#420.6) file and also to access data in the 0 node to support a screen of choices. The CODE INDEX file contains the list of vendor FPDS socio-econonomic groups. |
|||
| 2135 | DBIA2135 | Routine | IFCAP | 1997/09/08 | APPROVED | Active | Private | The Prosthetics package requests permission to use IFCAP program PRCFSITE to set special IFCAP variables used in the package. |
PRCFSITE | |||
| 2278 | DBIA2278 | File | IFCAP | 1998/02/02 | APPROVED | Active | Private | 441 | The purpose of this agreement is to allow another package to lookup Item Master file (#441) entries by the short description (field #.05) using the "C" cross reference on that field or extract the value of the short description for a item whose Item Master File (IMF) number is known. |
|||
| 2345 | D&PPM | File | IFCAP | 1998/06/01 | APPROVED | Active | Private | 410 | ||||
| 2409 | 2409 | File | IFCAP | 1998/05/11 | APPROVED | Active | Private | 410 | ||||
| 2526 | PRCHUTL | Routine | IFCAP | 1998/09/03 | APPROVED | Active | Private | This integration agreement will allow Accounts Receivable to call two functions in this routine. $$VENSEL will return the internal number of a user selected Vendor from the IFCAP Vendor file. $$VEN will return the Vendor ID number when the internal number of a Vendor is sent to this function. |
PRCHUTL | |||
| 2606 | DBIA2606 | File | IFCAP | 1998/10/14 | APPROVED | Active | Private | 440 | ||||
| 2749 | ABC | Other | IFCAP | 1999/02/08 | Withdrawn | Private | ||||||
| 2859 | TAXID FIELDS IN 440 | File | IFCAP | 1999/07/21 | APPROVED | Active | Private | 440 | Accounts Receivable needs to pull data from fields 38 and 39 in IFCAP file 440. This is necessary to place the Tax ID number on the TOP (Treasury Offset Program) documents. |
|||
| 2897 | DBIA2897 | Routine | IFCAP | 1999/08/25 | APPROVED | Active | Private | Routine PRCH7D is used as an interface between Prosthetics Package, Administrative Home Oxygen Module and IFCAP for purchase card transactions. |
PRCH7D | |||
| 3007 | DBIA3007 | File | IFCAP | 1999/12/02 | APPROVED | Active | Private | 423.6 | This agreement allows AR to reference the IFCAP file ISMS/FMS TRANS #423.6. |
|||
| 3427 | Purchase Card info | File | IFCAP | 2001/11/14 | APPROVED | Active | Controlled Subscription | 440.6 | This is a one time request, limited duration integration agreement. This request is limited to use within changes to Prosthetics version 3.0 made by patch RMPR*3*67. This agreement and the changes made by patch RMPR*3*67 will be terminated at the time that IFCAP releases patch PRC*5.1*45 which is an updated API that meets the extended needs of Prosthetics. This agreement is needed to allow sites to reconcile Prosthetics Orders that had their Purchase Card numbers changed by the credit card supplier. This agreement includes a direct global read only access of the "D" cross- reference at ^PRCH(440.6,"D",date) for processing time needs. As part of this one time request, limited duration integration agreement, direct global read only access of ^PRC(442,ien,0) first piece is requested. |
|||
| 3672 | DBIA3672 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 410.2 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3673 | DBIA3673 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 410.4 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3674 | DBIA3674 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 410.5 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3675 | DBIA3675 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 410.6 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3676 | DBIA3676 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 410.7 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3677 | DBIA3677 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 410.8 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3678 | DBIA3678 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 411 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3679 | DBIA3679 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 420 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3680 | DBIA3680 | File | IFCAP | 2002/08/14 | APPROVED | Active | Controlled Subscription | 420.2 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3681 | DBIA3681 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 420.6 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3682 | DBIA3682 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 420.7 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3683 | DBIA3683 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 420.8 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3684 | DBIA3684 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 421 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3685 | DBIA3685 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 421.1 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3686 | DBIA3686 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 421.5 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3687 | DBIA3687 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 424 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3688 | DBIA3688 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 424.1 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3689 | DBIA3689 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 440.2 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3690 | DBIA3690 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 440.5 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3691 | DBIA3691 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 440.6 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3692 | DBIA3692 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 440.7 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3693 | DBIA3693 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 441.2 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3694 | DBIA3694 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 441.3 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3695 | DBIA3695 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 441.6 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3696 | DBIA3696 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 441.7 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3697 | DBIA3697 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 442 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3698 | DBIA3698 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 442.7 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3699 | DBIA3699 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 442.8 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3700 | DBIA3700 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 443 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3701 | DBIA3701 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 443.4 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3702 | DBIA3702 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 443.6 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3703 | DBIA3703 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 443.8 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3704 | DBIA3704 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 444 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3705 | DBIA3705 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 444.1 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3706 | DBIA3706 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 445 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3707 | DBIA3707 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 445.2 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3708 | DBIA3708 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 445.3 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3709 | DBIA3709 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 445.4 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3710 | DBIA3710 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 445.6 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3711 | DBIA3711 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 445.7 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3712 | DBIA3712 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 445.8 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3713 | DBIA3713 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 446 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3714 | DBIA3714 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 446.1 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3715 | DBIA3715 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 446.5 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3716 | DBIA3716 | File | IFCAP | 2002/08/14 | APPROVED | Active | Private | 446.6 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 4151 | CoreFLS/Legacy Software Shut Down Status Check | Routine | IFCAP | 2003/07/30 | APPROVED | Active | Supported | As the legacy software packages IFCAP, Engineering (AEMS/MERS) and Equipment/Turn-In Request are converted to Read-Only functionality, data conversions are started and then CoreFLS comes on-line for each site, a new PRCL LSSD SHUTDOWN STATUS parameter in VistA will be updated. The API described below will enable other packages to check its value, perhaps directing the flows their software execution on the basis of it. For example, the IFCAP interface partners might continue to use APIs to IFCAP code if IFCAP is fully functional and switch to use APIs to the Communications Service Library (CSL) code if CoreFLS is on-line. |
PRCLOP4 | |||
| 4348 | 1358 DAILY RECORD ACCESS | File | IFCAP | 2004/02/17 | Withdrawn | Private | 424 | Fee Basis will be accessing record entries (read-access only) contained in the 1358 DAILY RECORD (#424) for use during the conversion of FEE BASIS 7078 documents (file 162.4). Conversion program(s) in the Fee Basis namespace will be evaluating the data stored in specific record entries contained in file 424 to logically decide if a specific record in file 162.4 should be converted determinant on certain criteria. |
||||
| 4400 | DBIA4400 MODIFY OPTIONS FOR LSSD SHUTDOWN | Routine | IFCAP | 2004/04/12 | Withdrawn | Controlled Subscription |
At the beginning of a site's conversion to CoreFLS software, the Legacy Software Shut Down (LSSD) program is run to convert the IFCAP, AEMS/MERS, and Equipment/Turn-In Request packages to a read-only state. These packages will be referred to as legacy packages. One of the steps in the program is disabling any options in the legacy systems which could effect an addition, modification, or deletion of data to the site's VistA database. All legacy options are disabled except those in a pre-determined list, which is known as the 'Options to Leave ALone' list. The list is in the LSSD (#449.1) file and will be referred to here as the List. Before a site converts to CoreFLS, the site will continue to install patches as necessary to fix bugs or add functionality to the legacy packages. When adding functionality, a patch may add or enhance or delete an option or group of options. Later on, when the site runs the LSSD shutdown and converts to CoreFLS, the site may need to continue using the functionality provided by those new options. In that case, it will become necessary to prevent those options from being disabled by the shutdown. To do this, the options must have been added to the List before the shutdown was run. Likewise, there may be options in the List that a future patch may remove or enhance such that those options should be disabled by the legacy shutdown. Those options should then be removed from the List before the legacy shutdown is run. This IA describes the API that patch developers should use to add or remove options from the List. The API must be invoked in the post-install executable of a patch. In any patch that uses this API, the patch must also include a patch dependency for the LSSD patch, PRC*5.1*65. |
PRCLOP11 | ||||
| 4599 | VENDOR FILE READ | File | IFCAP | 2005/02/07 | APPROVED | Active | Private | 440 | ||||
| 4676 | DBIA4676 | File | IFCAP | 2005/06/08 | APPROVED | Active | Controlled Subscription | 440 | Allow FileMan read of the VENDOR file (#440), NAME field (#.01). |
|||
| 4704 | DBIA4704 | File | IFCAP | 2005/06/27 | APPROVED | Active | Private | 442.6 | ||||
| 5159 | DBIA5159 | File | IFCAP | 2008/03/18 | Pending | Private | 441 | Integrated Billing requires one time access to the IFCAP Item Master file (#441). Prosthetics changed from using the Item Master file as the source of the Prosthetics Item description to using the Prosthetics HCPCS. Integrated Billing is now being updated to correspond to this change in Prosthetics. However for already billed items the bill must not change, therefore for historical purposes, the Item Master description will be pulled and saved with the old/existing billed Prosthetics Items. The Integrated Billing patch IB*2*389 post-init will access the Item Master file to get then store (#362.5,.05) the Item description for every prosthetic item billed at the time of the installation, not directly related to a Patient Item (#660). This agreement will expire at the end of the IB*2*389 compliance date. |
||||
| 5214 | PRCS58 For FBCS (DSS) | Routine | IFCAP | 2008/06/10 | Withdrawn | Controlled Subscription | PRCS58 | |||||
| 5215 | PRCS58CC for FBCS (DSS) | Routine | IFCAP | 2008/06/11 | Withdrawn | Controlled Subscription | PRCS58CC | |||||
| 5274 | FBCS FILE 442 | File | IFCAP | 2008/10/15 | Retired | Controlled Subscription | 442 | The Fee Basis Claims system accesses the PROCUREMENT & ACCOUNTING TRANSACTIONS (#442) file in order to return a list of obligations based upon Control point and number of years past for reports, as well as lookup obligations by control point. ^PRC(442,D0,0) .01 PURCHASE ORDER NUMBE 0;1 Read w/Fileman 1 FCP 0;3 Fileman r/global r 1.4 APPROPRIATION 0;4 Global r 2 COST CENTER 0;5 Global r 3 SUBACCOUNT1 0;6 Global r 3.4 SUBAMOUNT1 0;7 Global r 4 SUBACCOUNT2 0;8 Global r 4.4 SUBAMOUNT2 0;9 Global r 91 TOTAL AMOUNT 0;15 Read w/Fileman .07 PRIMARY 2237 0;12 Fileman r/global r ^PRC(442,D0,1) .1 P.O. DATE 1;15 Read w/Fileman ^PRC(442,D0,7) .5 SUPPLY STATUS 7;1 Fileman r/global r ^PRC(442,D0,8) 94 ACTUAL 1358 BALANCE 8;1 Fileman r/global r 96 EST 1358 BALANCE 8;3 Fileman r/global r ^PRC(442,D0,23) 31 SUBSTATION 23;7 Global r ^PRC(442,"B") Used for IEN lookup ^PRC(442,"C") Used for IEN lookup ^PRC(442,"E") Used for FCP lookups |
2009/01/06 | |||
| 5300 | FBCS FILE 424 | File | IFCAP | 2009/03/12 | Retired | Controlled Subscription | 424 | The Fee Basis Claims system accesses the 1358 DAILY RECORD (#424) file in order to look up entries using either the Interface ID cross-reference or the B cross reference. ^PRC(424,"B") Used for IEN lookups ^PRC(424,"E") Used for Interface ID lookups ^PRC(424,"AD") Used to check for existence of the Authorization IEN |
||||
| 5301 | FBCS FILE 420 | File | IFCAP | 2009/03/12 | Retired | Controlled Subscription | 420 | The Fee Basis Claims system accesses the FUND CONTROL POINT. It uses this access to validate FCP/Site combinations for users. $D(^PRC(420,FBSTA,1,+FBFCP,1,DUZ,0)) ^PRC(420,SITE,1,"B",FBFCP) $D(^PRC(420,"A",DUZ,SITE,+FBFCP)) $P(^PRC(420,FBSTA,1,+FBFCP,1,DUZ,0),U,2) $O(^PRC(420,"B") added with DSIF*3.2*1 (to obtain all station numbers for a user) |
||||
| 5330 | FBCS ACCESS TO PRCSUT | Routine | IFCAP | 2008/12/31 | Retired | Controlled Subscription | PRCSUT | |||||
| 5336 | FBCS ACCESS TO GLOBAL PRC(411 | File | IFCAP | 2009/01/12 | Retired | Controlled Subscription | 411 | The Fee Basis Claims System accesses the .01 field of the ADMIN. ACTIVITY SITE PARAMETER (#411) file in order to setup a new obligation sequence number for a 7078. ^PRC(411,D0,0) .01 STATION/SUBSTATION CODE 0;1 Global Read |
||||
| 5465 | IFCAP Option Access | IFCAP | 2011/01/26 | Withdrawn | ||||||||
| 5539 | COTS INV LOG | Routine | IFCAP | 2010/06/22 | APPROVED | Active | Controlled Subscription | IFCAP API to log messaging transactions between VistA and remote COTS Inventory System. |
PRCMCM | 2010/06/22 | ||
| 5573 | User OK as Certifier for a 1358? | Routine | IFCAP | 2010/10/28 | APPROVED | Active | Controlled Subscription | This agreement allows subscribers to call an API UOKCERT^PRCEMOA. This API verifies that a person would not violate segregation of duty when certifying an invoice associated with a 1358 miscellaneous obligation by ensuring that they have not previously acted as a requestor, approver, or obligator on that 1358. |
PRCEMOA | 2011/01/11 | ||
| 5574 | Events (and Actors) for a 1358 | Routine | IFCAP | 2010/10/28 | APPROVED | Active | Controlled Subscription | This agreement allows subscribers to call an API $$EV1358^PRCEMOA. This API provides information on the events (initial obligation and increase/decrease adjustments) and IFCAP actors (requestor, approving official, obligator) for a specified 1358 miscellaneous obligation. |
PRCEMOA | 2011/01/11 | ||
| 5582 | FILE 411 ACCESS | File | IFCAP | 2010/11/18 | APPROVED | Active | Controlled Subscription | 411 | This IA provides read-only access to the ADMIN. ACTIVITY SITE PARAMETER (#411) file via FileMan for lookups. |
2011/01/11 | ||
| 5921 | READ ACCESS TO FILE #441 (ITEM MASTER) | File | IFCAP | 2013/05/16 | APPROVED | Active | Private | 441 | Request permission for READ access via FileMan calls to file #441 in order to complete RPC queries from WaveMark. This is part of the RTLS National project to facilitate tracking clinical supplies in the Cathlab inventory point for GIP. |
VIAAIMUP | 2014/06/30 | |
| 5922 | READ ACCESS TO FILE #440 (VENDOR) | File | IFCAP | 2013/05/16 | APPROVED | Active | Private | 440 | Request permission for READ access via FileMan calls to file #440 in order to complete RPC queries from WaveMark. This is part of the RTLS National project to facilitate tracking clinical supplies in the Cath lab inventory point for GIP. |
VIAAIMUP | 2014/07/02 | |
| 5923 | READ/WRITE ACCESS TO FILE #445 (GENERIC INVENTORY) | File | IFCAP | 2013/05/16 | APPROVED | Active | Private | 445 | Request permission for READ and WRITE access via FileMan calls to file #445 in order to complete RPC queries from WaveMark. This is part of the RTLS National project to facilitate tracking clinical supplies in the Cathlab inventory point for GIP. |
VIAAIPDE | 2014/07/07 | |
| 6067 | READ ACCESS TO FILE #445.6 (GROUP CATEGORY) | File | IFCAP | 2014/06/19 | APPROVED | Active | Private | 445.6 | Request permission for READ access via FileMan calls to file #445.6 in order to complete RPC queries from WaveMark. This is part of the RTLS National project to facilitate tracking clinical supplies in the Cath lab inventory point for GIP. |
2014/07/02 | ||
| 6068 | READ ACCESS TO FILE #420.5 (UNIT OF ISSUE) | File | IFCAP | 2014/06/19 | APPROVED | Active | Private | 420.5 | Request permission for READ access via FileMan calls to file #420.5 in order to complete RPC queries from WaveMark. This is part of the RTLS National project to facilitate tracking clinical supplies in the Cath lab inventory point for GIP. |
2014/07/02 | ||
| 6374 | PROSTHETICS-POINT OF USE-GIP LOOKUP | File | IFCAP | 2016/02/26 | APPROVED | Active | Private | 445 | The IFCAP Generic Inventory Package (GIP) provides the ability for sites to use Point of Use (POU) supply stations. An INVENTORY POINT (#.01), which is stored and managed in the GENERIC INVENTORY file (#445) can be linked to a Point of Use supply station with a pointer from its SS PROVIDER field (#22). The SS PROVIDER field points to the AUTOMATED SUPPLY STATIONS file (#445.5). When an INVENTORY POINT in file 445 has an entry in field 22 that points to an AUTOMATED SUPPLY STATION entry, then the INVENTORY POINT is known to be linked to a POU supply cabinet. These are special cabinets that automatically update GIP inventory balances, via HL7 messaging, when stock is removed. This DBIA gives the Prosthetics package permission to read the SS PROVIDER FIELD (#22) and determine if that field points to a valid entry in the AUTOMATED SUPPLY STATIONS file (#445.5). |
2016/03/16 | ||
| 6394 | PROSTHETICS-DYNAMED LOOKUP | Other | IFCAP | 2016/03/18 | APPROVED | Active | Private | The Prosthetics package needs the ability to determine whether a site is using DynaMed for inventory. Sites using DynaMed will continue to use Prosthetics Inventory Package (PIP) until a better solution is devised. This DBIA grants the Prosthetics package the permission to read the system parameter "PRCV COTS INVENTORY" with the following kernel call: ($$GET^XPAR("SYS","PRCV COTS INVENTORY",1,"Q")). The "PRCV COTS INVENTORY" parameter identifies which COTS product is being utilized for the inventory management system of the site. The current values are: NAME: PRCV COTS INVENTORY DISPLAY TEXT: COTS Inventory MULTIPLE VALUED: No VALUE TERM: 0 or 1 VALUE DATA TYPE: set of codes VALUE DOMAIN: 0:NONE;1:DYNAMED VALUE HELP: ?/ INSTANCE DATA TYPE: numeric DESCRIPTION: This parameter identifies which COTS product is being utilized for the inventory management system of the site. The current values are: 0 NONE - means no COTS product is being used and the inventory management system in use is GIP/IFCAP 1 DYNAMED - means the DynaMed product is being used |
2016/03/23 | |||
| 6518 | REPETITIVE ITEM LIST ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Under Revision | Private | 410.3 | Above PAR requests permission to write to the REPETITIVE ITEM LIST File #410.3 to record additions and edits of Repetitive Item Requests within the Inventory function. |
2022/02/17 | ||
| 6520 | PURCHASE ORDER STATUS ACCESS | File | IFCAP | 2016/10/17 | Withdrawn | Controlled Subscription | 442.3 | Above PAR requests permission to read from the PURCHASE ORDER STATUS File #442.3 to display information within the Inventory function. APAT reads from the PURCHASE ORDER STATUS (#442.3) file to determine the status of a purchase card order. |
||||
| 6521 | SIC CODE FILE ACCESS | File | IFCAP | 2016/10/17 | Withdrawn | Private | 444.2 | Above PAR requests permission to read from the SIC CODE File #444.2 to display information within the Inventory function. |
||||
| 6522 | INTERNAL DISTRIBUTION ORDER/ADJ. ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Private | 445.3 | Above PAR requests permission to read and write to the INTERNAL DISTRIBUTION ORDER/ADJ. FILE #445.3 to display and record Distribution Orders within the Inventory function. Above PAR Ad-Hoc Reporting includes the INTERNAL DISTRIBUTION ORDER/ADJ FILE #445.3. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2022/02/17 | ||
| 6523 | AUTOMATED SUPPLY STATIONS ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Private | 445.5 | Above PAR requests permission to read from the AUTOMATED SUPPLY STATIONS File #445.5 to validate that the Automated Supply Station is defined. Permission is also requested in order to: 1. Retrieve the value of the INVENTORY UPDATES field for use in logic for populating the Item Name subfield the HL7 message's RQD segment. 2. Retrieve the value of the LINK NAME for use in specifying the link over which the HL7 message will be sent to the Supply Station's database. |
2018/12/07 | ||
| 6524 | GROUP CATEGORY FILE ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Private | 445.6 | Above PAR requests permission to read and write to the GROUP CATEGORY FILE #445.6 to display, add, edit, and delete GROUP CATEGORY entries. Above PAR Ad-Hoc Reporting includes the GROUP CATEGORY FILE #445.6. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2022/03/04 | ||
| 6525 | INVENTORY DISTRIBUTED PATIENT SUPPLIES ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Private | 446.1 | Above PAR requests permission to read and write to the INVENTORY DISTRIBUTED PATIENT SUPPLIES FILE #446.1 to display and edit the inventory point within the file if a Distribution Order is posted with patient supplies. Above PAR Ad-Hoc Reporting includes the INVENTORY DISTRIBUTED PATIENT SUPPLIES FILE #446.1. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2018/03/26 | ||
| 6526 | BARCODE PROGRAM FILE ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Private | 446.4 | Above PAR requests permission to read and write to the BARCODE PROGRAM File #446.4 to record and display uploads from the Bar Code Reader. |
2022/03/04 | ||
| 6527 | CUSTOM LABEL FILE ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Private | 446.5 | Above PAR requests permission to read from the CUSTOM LABEL File # 446.5 to display information within the Inventory function. |
2018/03/26 | ||
| 6528 | INVENTORY LOCK MANAGEMENT | File | IFCAP | 2016/10/17 | APPROVED | Active | Private | 447 | Above PAR requests permission to read and write to the INVENTORY LOCK MANAGEMENT File #447 to display and update the Lock management information within the Inventory function. |
2018/03/26 | ||
| 6530 | VENDOR FILE ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Controlled Subscription | 440 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request permission to read from the VENDOR FILE #440 to display information within the Equipment, Work Order and Inventory functions and when creating and displaying purchasing documents. Above PAR also updates the VENDOR (#440) File. Above PAR Ad-Hoc Reporting includes the VENDOR FILE #440. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2023/03/30 | ||
| 6531 | ITEM MASTER FILE ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Controlled Subscription | 441 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request permission to add, edit, and display ITEM MASTER FILE #441 data. Above PAR adds, edits, and displays items in the ITEM MASTER FILE #441 as part of its Inventory functionality. Above PAR Ad-Hoc Reporting provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. The Advanced Prosthetics Acquisition Tool (APAT) reads from the ITEM MASTER FILE #441 when creating patient-centric purchase card orders, detailed purchase card orders, and GIP and PIP stock issues as well as when displaying Prosthetic appliance transaction information on the 2319. The detailed purchase card order functionality also performs FileMan writes to specified fields of the ITEM MASTER #441 as each item is added to the order. |
2023/01/12 | ||
| 6532 | FEDERAL SUPPLY CLASSIFICATION ACCESS | File | IFCAP | 2016/10/17 | APPROVED | Active | Controlled Subscription | 441.2 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request permission to read from the FEDERAL SUPPLY CLASSIFICATION File (#441.2) to display information within the Inventory and Create Detailed Purchase Card Order functionality. |
2023/04/28 | ||
| 6546 | FIRST DATE OF QUARTER | Routine | IFCAP | 2016/10/18 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRC0D. This extrinsic function returns the first date of the specified quarter. |
PRC0D | 2019/06/07 | ||
| 6547 | GENERIC INVENTORY FILE ACCESS | File | IFCAP | 2016/10/18 | APPROVED | Active | Controlled Subscription | 445 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request permission to read and write to the GENERIC INVENTORY FILE #445 to display and edit both Distribution Points and Items within a Distribution Point within the Inventory function. Inventory levels are also adjusted by the APAT stock issue and edit 2319 functionality. Above PAR will address the conversion of a secondary to a primary in a future version. Above PAR Ad-Hoc Reporting includes the GENERIC INVENTORY FILE #445. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2022/03/04 | ||
| 6548 | INVENTORY TRANSACTION FILE ACCESS | File | IFCAP | 2016/10/18 | APPROVED | Active | Controlled Subscription | 445.2 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request permission to read and write to the INVENTORY TRANSACTION FILE #445.2 to update Inventory Transactions within the Inventory and Stock Issue functionality. Above PAR Ad-Hoc Reporting includes the INVENTORY TRANSACTION FILE #445.2. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2019/06/07 | ||
| 6549 | STORAGE LOCATION ACCESS | File | IFCAP | 2016/10/18 | APPROVED | Active | Controlled Subscription | 445.4 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request permission to read and write to the STORAGE LOCATION FILE #445.4 to maintain a master list of storage locations within the Inventory function. Above PAR Ad-Hoc Reporting includes the STORAGE LOCATION FILE #445.4. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2021/11/18 | ||
| 6550 | FMS DOCUMENTS FOR SUPPLY FUND SPECIAL CTL PT | Routine | IFCAP | 2016/10/18 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCFFMO. |
PRCFFMO | 2019/07/02 | ||
| 6551 | CREATE 2237 FOR NEW PURCHASE CARD ORDER | Routine | IFCAP | 2016/10/18 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCH410 to create the 2237 record, record the electronic signature, and update due-ins. |
PRCH410 | 2018/11/21 | ||
| 6552 | CHECKSUM GENERATION | Routine | IFCAP | 2016/10/18 | APPROVED | Active | Private | The Advanced Prosthetics Acquisition Tool (APAT) requests access to IFCAP checksum generation. |
PRCUESIG | 2019/06/07 | ||
| 6553 | REFORMAT WORD PROCESSING VALUE | Routine | IFCAP | 2016/10/18 | APPROVED | Active | Private | The Advanced Prosthetics Acquisition Tool (APAT) uses the IFCAP Word Processing Reformatting utility. |
PRCUTL | 2019/06/07 | ||
| 6555 | IFCAP FCP ACCOUNTING INFORMATION | Routine | IFCAP | 2016/10/18 | APPROVED | Active | Controlled Subscription | The Advanced Prosthetics Acquisition Tool (APAT) and Above PAR use extrinsic functions in PRC0C to retrieve fund control point parameters and to convert calendar dates to Fiscal Year and Fiscal Quarter. This data is used during the creation and display of detailed purchase card orders. |
PRC0C | 2019/06/07 | ||
| 6563 | PURCHASE ORDERS: FIND AMENDMENTS | Routine | IFCAP | 2016/10/25 | Pending | Private | This integration agreement allows the call START^PRCHDP5 to retrieve for subsequent display what changes were made by a specified amendment to a purchase order. |
PRCHDP5 | ||||
| 6564 | PURCHASE ORDER: SET UP AMENDMENT HISTORY | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call AMENDS^PRCHDP6 to set up a ^TMP($J,"PRCHDP6" temp file with the amendment history for a purchase order. |
PRCHDP6 | 2019/07/02 | ||
| 6565 | PURCHASE ORDER: E-SIGNATURE ON RECEIVING PARTIAL | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This is called to encode the e-signature on the PARTIAL entry during receipt into inventory. |
PRCHES2 | 2019/06/07 | ||
| 6566 | PURCHASE ORDER: RETURN FACILITY TYPE | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call FTYP^PRCHFPNT to return the free-text facility type for a purchase order. |
PRCHFPNT | 2019/07/02 | ||
| 6567 | PURCHASE ORDER: RETURN EDI STATUS | Routine | IFCAP | 2016/10/25 | Withdrawn | Private | This integration agreement allows the call EDISTAT^PRCHUTL to determine the EDI status of a purchase order. |
PRCHUTL | ||||
| 6568 | REPETITIVE ITEM LIST - ADD OR DELETE ITEMS | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the calls to $$ADDITEM^PRCPAGPR which adds to REPETITIVE ITEM LIST (RIL) (#410.3), to $$NEWRIL^PRCPAGPR which creates new RIL items, and to DELRIL^PRCPAGPR which deletes RIL items. |
PRCPAGPR | 2019/06/07 | ||
| 6569 | DELETE TEMP STOCK LEVEL | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call DELTEMP^PRCPAGU1 to delete the temporary stock level in the Generic Inventory File ^PRCP(445). |
PRCPAGU1 | 2019/06/07 | ||
| 6570 | INVENTORY: BUILD HL7 FOR ITEM DELETION | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call BLDSEG^PRCPHLFM which builds an HL7 segment whenever a secondary inventory item is deleted. This updates the inventory in the automated supply stations. |
PRCPHLFM | 2019/06/07 | ||
| 6571 | DISTRIBUTION ORDER: SEND ORDER DELETED MESSAGE | Routine | IFCAP | 2016/10/25 | Pending | Private | This integration agreement allows the call MESSAGE^PRCPOPD which sends the user a message if a Distribution Order is deleted. |
PRCPOPD | ||||
| 6572 | DISTRIBUTION ORDER: ITEM CHECK | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call $$ITEMCHK^PRCPOPER to check items within a distribution order. |
PRCPOPER | 2019/06/07 | ||
| 6573 | DISTRIBUTION ORDER: POSTING | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the following calls: RECEIPT^PRCPOPPP to Receive Items at a Secondary Distribution Point SALE^PRCPOPPP to Disburse Items from a Primary Distribution Point These calls are used when a Distribution Order is Posted within the Inventory function. |
PRCPOPPP | 2019/06/07 | ||
| 6574 | DISTRIBUTION ORDER: CREATE NEW ORDER | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the following calls: NEWORDER^PRCPOPUS to get the next Order # available $$ADDNEW^PRCPOPUS to create the new order in ^PRCP(445.3) This extrinsic function is used when creating a new Distribution Order in the Inventory function. |
PRCPOPUS | 2019/06/07 | ||
| 6575 | INVENTORY: DELETE ITEM, UPDATE CODESHEET | Routine | IFCAP | 2016/10/25 | Withdrawn | Private | This integration agreement allows Above PAR to call CODESHT^PRCPSMGO to update the Code Sheet if deleting the item from a Warehouse. |
PRCPSMGO | ||||
| 6576 | INVENTORY: DELETE ITEM, GET DELETE SEGMENT | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call DELETE^PRCPSMS0 to get segments needed to delete an item from the Supply Fund Warehouse inventory point. |
PRCPSMS0 | 2019/06/07 | ||
| 6577 | INVENTORY: UPDATE ITEM BALANCE | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration allows the following calls: BALANCE^PRCPUBAL in order to file in the INVENTORY BALANCE file (#445.1) the beginning monthly balances for an item in that inventory point. $$GETOPEN^PRCPUBAL to obtain an Inventory item's current inventory point balance. |
PRCPUBAL | 2019/06/07 | ||
| 6578 | DISTRIBUTION ORDER: RECEIVE AND UPDATE COST CENTER | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call COSTCNTR^PRCPUCC to create the initial year_month/cost_center/inventory_point entry in the DISTRIBUTION /USAGE HISTORY file (#446) or update the entry's total cost field's value when an issue book or internal distribution order is received by an inventory point. |
PRCPUCC | 2019/06/07 | ||
| 6579 | DISTRIBUTION ORDER: INVENTORY ITEM DELETION | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call DELITEM^PRCPUITM to delete the item from the inventory point and any supply station that was linked to that (secondary) inventory point during an AutoGen process when the item is flagged as KILL WHEN ZERO. The call to DELITEM is a sub-process of DSIYGO01 (cloned PRCPAGP1 process) and DSIYGO07 (cloning PRCPAGS1 process). |
PRCPUITM | 2019/06/07 | ||
| 6580 | INVENTORY: SCREEN VENDOR FOR ITEM | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call SCREEN^PRCPUMAN to screen selection of source vendor when adding to an Item within a Distribution Point. |
PRCPUMAN | 2019/07/02 | ||
| 6581 | DISTRIBUTION ORDER: CREATE PATIENT ENTRY | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call $$PATIENT^PRCPUPAT() to create an entry in the INVENTORY DISTRIBUTED PATIENT SUPPLIES file (#446.1) during posting of the distribution order if it includes patient supplies. |
PRCPUPAT | 2019/06/07 | ||
| 6582 | INVENTORY: BARCODE UPDATE | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call $$UPDATE^PRCPUSA() to update Distribution Points when reading data from a bar code scanner. |
PRCPUSA | 2018/08/15 | ||
| 6583 | INVENTORY - UPDATE ITEM RECEIPT HISTORY RECEIPTS | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call RECEIPTS^PRCPUSAG to update the Inventory Item's Receipts History in the Generic Inventory file (#445) Receipts History By Item subfile (#445.06) when a replenishment order is received into a Distribution Point. NOTE: Although the order for Primary Inventory Points would be a Purchase Order, for Secondary Inventory Points, the order would be a Distribution Order. (If sites were operating a Supply Fund Warehouse, the order for Primary Inventories would be either Issue Book for receipt from Warehouse or Purchase Order for receipt from external vendor.) |
PRCPUSAG | 2019/06/07 | ||
| 6584 | INVENTORY: UPDATE QTY ORD'D,DUE-IN,OR DEL OUTSTANDING REQST | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the following calls: KILLTRAN^PRCPUTRA to kill any outstanding transactions OUTST^PRCPUTRA to add Quantity to outstanding transactions |
PRCPUTRA | 2019/06/07 | ||
| 6585 | INVENTORY: GET INVENTORY TRANSACTION # & CREATE TRANS | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows these calls: ADDTRAN^PRCPUTRX to add a transaction entry to the Transaction Register ^PRCP(445.2) to record a received Purchase Order, Distribution Order, or Issue Book $$ORDERNO^PRCPUTRX() to receive a new transaction entry # |
PRCPUTRX | 2019/06/07 | ||
| 6586 | INVENTORY: BARCODE PRINT | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call EN^PRCTLAB to print Bar Code labels. |
PRCTLAB | 2018/11/21 | ||
| 6587 | INVENTORY: BARCODE TASKMAN REQUEST | Routine | IFCAP | 2016/10/25 | APPROVED | Active | Private | This integration agreement allows the call TASK^PRCTREAD to create the TaskMan process to run entry points in routine PRCPBALM to update the inventory counts or calculate inventory usage based on the data uploaded from the barcode reader after barcode scanning inventory stock. |
PRCTREAD | 2018/08/27 | ||
| 6588 | DISTRIBUTION ORDER: NEW DOCUMENT ID | Routine | IFCAP | 2016/10/25 | Withdrawn | Private | This integration agreement allows the call EN1^PRCUTL1(.X) to either add a new entry in the Transaction Number file (#410.1) or to update the value in the COUNTER field (#1) of an existing entry of this file of counters. This call gets a new Document ID. The stub of the transaction number is set into a variable which is passed by reference to the API. After the call, the assigned transaction number is passed back in that variable. |
PRCUTL1 | ||||
| 6590 | RIL: UPDATE DELIVERY ORDER ITEM FIELD | Routine | IFCAP | 2016/10/27 | APPROVED | Active | Private | This integration agreement allows the call CHECK^PRCSRIE1 to update for a given REPETITIVE ITEM LIST file (#410.3) item entry, the DELIVER ORDER ITEM field (#5) the based on whether that item is under contract for the assigned vendor. |
PRCSRIE1 | 2019/06/07 | ||
| 6591 | GUI PURCHASE CARD PROS ORDER INTERFACE | Routine | IFCAP | 2016/10/28 | APPROVED | Active | Private | The Advanced Prosthetics Acquisition Tool (APAT) uses the existing IFCAP GUI interface to create Prosthetic Purchase Card Orders. |
PRCH7PUC | 2019/06/07 | ||
| 6592 | PURCHASE ORDER NUMBER RETRIEVAL | Routine | IFCAP | 2016/10/28 | APPROVED | Active | Private | The Advanced Prosthetics Acquisition Tool (APAT) uses the existing IFCAP API to take the specified Common Numbering Series and update the PAT NUMBER (#442.6) File for the next number. An entry in the PROCUREMENT & ACCOUNTING TRANSACTIONS (#442) File is also created for use in obligation. |
PRCH7PA1 | 2019/06/07 | ||
| 6595 | ADMIN. ACTIVITY SITE PARAMETER FILE ACCESS | File | IFCAP | 2016/11/03 | APPROVED | Active | Controlled Subscription | 411 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request READ access to the ADMIN. ACTIVITY SITE PARAMETER FILE #411 to retrieve Receiving Locations and Substation data when creating or displaying detailed purchase card orders and when verifying that a site is an IFCAP site. If SCREEN FOR FISCAL USER (#39) is set, APAT may require that the user is an AUTHORIZED FISCAL USER (#40 (subfile 411.05)). Above PAR Ad-Hoc Reporting includes the ADMIN. ACTIVITY SITE PARAMETER FILE #411. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2019/06/07 | ||
| 6600 | FACILITY TYPE (TEMPORARY) FILE ACCESS | File | IFCAP | 2016/11/04 | APPROVED | Active | Private | 411.2 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the Facility type/name in the Facility Type (Temporary) file in order to display it on the detailed purchase card order. |
2023/04/04 | ||
| 6601 | DIRECT DELIVERY PATIENTS FILE ACCESS | File | IFCAP | 2016/11/04 | APPROVED | Active | Controlled Subscription | 440.2 | The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the patient name and address in the DIRECT DELIVERY PATIENTS FILE #440.2 for display on the detailed purchase card order. Above PAR Ad-Hoc Reporting includes the DIRECT DELIVERY PATIENTS FILE #440.2. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2018/11/21 | ||
| 6602 | PURCHASE AUTHORITY FILE ACCESS | File | IFCAP | 2016/11/04 | APPROVED | Active | Controlled Subscription | 442.4 |
Permission for read access to the Purchase Authority Abbreviation in the PURCHASE AUTHORITY file (#442.4) is requested for display on the detailed purchase card order. |
2019/06/07 | ||
| 6603 | PAT NUMBER FILE ACCESS | File | IFCAP | 2016/11/04 | APPROVED | Active | Private | 442.6 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the PAT Number file (#442.6) when presenting the available Common Numbering Series to be chosen when creating a purchase card order. |
2019/06/07 | ||
| 6604 | ADMINISTRATIVE CERTIFICATIONS FILE ACCESS | File | IFCAP | 2016/11/04 | APPROVED | Active | Private | 442.7 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the ADMINISTRATIVE CERTIFICATIONS File (#442.7) when displaying the Administrative Certifications on the detailed purchase card order. |
2019/06/07 | ||
| 6605 | DELIVERY SCHEDULE (ORDER) FILE ACCESS | File | IFCAP | 2016/11/04 | APPROVED | Active | Private | 442.8 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the DELIVERY SCHEDULE (ORDER) file (#442.8) when displaying the delivery schedule on a purchase order. |
2019/07/02 | ||
| 6608 | FUND CONTROL POINT FILE ACCESS | File | IFCAP | 2016/11/10 | APPROVED | Active | Controlled Subscription | 420 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request READ access to the FUND CONTROL POINT FILE #420. Above PAR Ad-Hoc Reporting includes the FUND CONTROL POINT FILE #420. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2019/06/07 | ||
| 6615 | TRANSACTION NUMBER FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Private | 410.1 |
The Advanced Prosthetics Acquisition Tool (APAT) checks for new transaction number availability for detailed purchase card orders. |
2019/06/07 | ||
| 6616 | DELIVERY POINT FILE ACCESS | File | IFCAP | 2016/11/16 | Withdrawn | Private | 410.8 |
The Advanced Prosthetics Acquisition Tool (APAT) pulls data from the DELIVERY POINT (#410.8) file for reporting on detailed purchase card orders. |
||||
| 6617 | SORT GROUP FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Private | 410.7 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the SORT GROUP (#410.7) file. |
2019/06/07 | ||
| 6618 | SUB-CONTROL POINT FILE ACCESS | File | IFCAP | 2016/11/16 | Pending | Private | 410.4 |
The Advanced Prosthetics Acquisition Tool (APAT) pulls data from file SUB-CONTROL POINT (#410.4) when creating detailed purchase card orders. |
||||
| 6619 | CLASSIFICATION OF REQUEST FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Private | 410.2 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the CLASSIFICATION OF REQUEST File (#410.2). |
2019/06/07 | ||
| 6620 | INSTRUMENT KITS FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 445.8 | The Advanced Prosthetics Acquisition Tool (APAT) and ABOVE PAR determine whether a given INSTRUMENT KIT exists within the INSTRUMENT KITS FILE #445.8. Above PAR Ad-Hoc Reporting includes the INSTRUMENT KITS FILE #445.8. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2019/07/02 | ||
| 6621 | CASE CARTS FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 445.7 | The Advanced Prosthetics Acquisition Tool (APAT) and ABOVE PAR request read access to the CASE CARTS FILE #445.7 in order to determine whether a given Case Cart exists. Above PAR Ad-Hoc Reporting includes the CASE CARTS FILE #445.7. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2019/06/07 | ||
| 6622 | CODE INDEX FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 420.6 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the CODE INDEX File (#420.6). |
2019/07/02 | ||
| 6623 | EVALUATED PREFERENCE FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Private | 420.54 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the EVALUATED PREFERENCE File (#420.54). |
2019/06/07 | ||
| 6624 | EXTENT COMPETED FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Private | 420.53 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the EXTENT COMPETED File (#420.53). |
2019/06/12 | ||
| 6625 | SOLICITATION PROCEDURE FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Private | 420.52 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the SOLICITATION PROCEDURE File (#420.52). |
2019/06/12 | ||
| 6626 | REASON NOT COMPETED FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Private | 420.51 |
The Advanced Prosthetics Acquisition Tool (APAT) requests read access to the REASON NOT COMPETED file (#420.51). |
2019/06/12 | ||
| 6627 | PURCHASE CARD INFORMATION FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 440.5 |
Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request READ access to specific fields of the Purchase Card Information file (#440.5). |
2018/11/21 | ||
| 6628 | PROCUREMENT & ACCOUNTING TRANSACTIONS FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 442 | The Advanced Prosthetics Acquisition Tool (APAT) requests read and write access to the PROCUREMENT & ACCOUNTING TRANSACTIONS FILE (#442). APAT creates and displays simplified and detailed purchase card orders in this file. Simplified purchase card orders are based on those created by the Prosthetic VistA Suite GUI, and detailed purchase card orders are based on those created in option PRCH ENTER DETAILED ORDER (New Detailed Purchase Card Order). Above PAR requests read access to the PROCUREMENT & ACCOUNTING TRANSACTIONS FILE #442 for display and reporting purposes. Above PAR Ad-Hoc Reporting includes the PROCUREMENT & ACCOUNTING TRANSACTIONS FILE #442. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2023/05/01 | ||
| 6629 | TYPE OF SPECIAL HANDLING FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 443.4 |
Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request READ access to specific fields of the Type of Special Handling file (#443.4). |
2018/11/21 | ||
| 6630 | COST CENTER FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 420.1 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request READ access to the COST CENTER FILE #420.1. Above PAR Ad-Hoc Reporting includes the COST CENTER FILE #420.1. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2023/04/28 | ||
| 6631 | BUDGET OBJECT CODE FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 420.2 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request read access the BUDGET OBJECT CODE FILE #420.2. Above PAR Ad-Hoc Reporting includes the BUDGET OBJECT CODE FILE #420.2. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2018/11/21 | ||
| 6632 | SOURCE CODE FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 420.8 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request read access to the SOURCE CODE FILE #420.8. Above PAR Ad-Hoc Reporting includes the SOURCE CODE FILE #420.8. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2018/11/21 | ||
| 6633 | PAT TYPE FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 442.5 |
Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request read access to specific fields of the PAT TYPE (#442.5) File. |
2019/06/13 | ||
| 6634 | CONTROL POINT ACTIVITY FILE ACCESS | File | IFCAP | 2016/11/16 | APPROVED | Active | Controlled Subscription | 410 | Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) request permission to reference the CONTROL POINT ACTIVITY FILE #410 to create/edit 2237's during the creation of purchase card orders and 2237's and during purchase card reconciliation/close-out. Above PAR Ad-Hoc Reporting includes the CONTROL POINT ACTIVITY FILE #410. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2018/11/14 | ||
| 6636 | FPDS HL7 MESSAGE GENERATION FOR AAC | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine AAC^PRCHAAC. When a detailed purchase card order is created, this functionality will gather FPDS data for the report requested by the Austin Automation Center (AAC), create an HL7 message, and send it to the Austin server via the VistA HL7 package. |
PRCHAAC | 2019/06/12 | ||
| 6637 | ENCODING E-SIGNATURE ON PC ORDER | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine ENCODE^PRCHES5 to encode an esignature when a detailed purchase card order is created. |
PRCHES5 | 2019/06/12 | ||
| 6638 | ENTER NEW PURCHASE CARD ORDER | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCHNPO when creating a detailed purchase card order. |
PRCHNPO | 2020/10/15 | ||
| 6639 | FPDS CODE SELECTION SCREEN | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call EN7^PRCHNPO2 when creating a detailed purchase card order. |
PRCHNPO2 | 2019/06/13 | ||
| 6640 | AUDITS OF PURCHASE CARD ORDER LINE ITEMS | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCHNPO7 when creating a detailed purchase card order. |
PRCHNPO7 | 2019/06/12 | ||
| 6641 | BBFY OF PURCHASE CARD ORDER | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call BBFY^PRCHNPO8 when creating a detailed purchase card order. |
PRCHNPO8 | 2019/06/12 | ||
| 6642 | PCDO TRANSACTION NUMBER VALIDATION | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCHNPOA when creating a detailed purchase card order. |
PRCHNPOA | 2019/06/12 | ||
| 6643 | USAGE OF PRCHNPOB | Routine | IFCAP | 2016/11/22 | Withdrawn | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCHNPOB when creating a detailed purchase card order. |
PRCHNPOB | ||||
| 6644 | ESIG PROBLEM ERROR MESSAGE | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCHQQ when creating a detailed purchase card order. |
PRCHQQ | 2019/06/13 | ||
| 6645 | STATUS UPDATE PURCHASE CARD ORDER | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCHSTAT when creating a detailed purchase card order. |
PRCHSTAT | 2019/07/02 | ||
| 6646 | PRCHOBL BASED ON FCP SWITCHES/MOP | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCHSWCH when creating a detailed purchase card order. |
PRCHSWCH | 2019/06/13 | ||
| 6647 | PRCHLOG VARIABLE SETUP | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call SWITCH^PRCHUTL when creating a detailed purchase card order. |
PRCHUTL | 2019/07/02 | ||
| 6648 | PHA FIELD VALIDATION | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call NEW^PRCOEDC when creating a detailed purchase card order. |
PRCOEDC | 2019/06/13 | ||
| 6649 | INVENTORY DUE-IN RECALCULATION | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call UPDATE^PRCPWIU when creating a detailed purchase card order. |
PRCPWIU | 2019/06/13 | ||
| 6650 | FUNDS AVAILABILITY CHECK | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call $$OVCOM^PRCS0A when creating a detailed purchase card order. |
PRCS0A | 2019/06/13 | ||
| 6651 | COMMITTED BALANCE DETAILED PC ORDER | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call COMM^PRCSPC when creating a detailed purchase card order. |
PRCSPC | 2019/06/13 | ||
| 6652 | BBFY OF FCP | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call $$BBFY^PRCSUT() when creating a detailed purchase card order. |
PRCSUT | 2019/06/13 | ||
| 6653 | PURCHASE ORDER DATA FOR DYNAMED | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call UPD^PRCV442A() when creating a detailed purchase card order. |
PRCV442A | 2019/07/02 | ||
| 6654 | PC ORDER NET, TOTAL & BOC $ UPDATES | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call ^PRCHSF when creating a detailed purchase card order. |
PRCHSF | 2019/06/13 | ||
| 6655 | PHA TXN FOR EDI & PHA QUEUES | Routine | IFCAP | 2016/11/22 | APPROVED | Active | Private |
This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCOEDI when creating or amending a detailed purchase card order. |
PRCOEDI | 2019/07/02 | ||
| 6734 | CANCEL 2237 FROM PC ORDER | Routine | IFCAP | 2017/02/13 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call C2237^PRCH442A. The call will cancel a 2237 from a purchase card order. |
PRCH442A | 2019/06/13 | ||
| 6830 | PURCHASE CARD RECONCILE FILE ACCESS | File | IFCAP | 2017/11/13 | APPROVED | Active | Private | 440.6 | The ADVANCED PROSTHETICS ACQUISITION TOOL requests permission to use FileMan APIs to read from and write to the PURCHASE ORDER RECONCILE file (#440.6). |
2019/06/13 | ||
| 6853 | ITEM - VERIFY ITEM MASTER NUMBER | Routine | IFCAP | 2017/12/13 | Withdrawn | Private | This integration agreement allows ABOVE PAR to call IFCAP routine PRCVITMU to verify the ITEM MASTER item number. |
PRCVITMU | ||||
| 6854 | VENDOR - CHECK ONE VENDOR'S CHECKSUM | Routine | IFCAP | 2017/12/13 | Pending | Private | This integration agreement allows ABOVE PAR to call ONECHK routine PRCVNDR to verify the vendor record and, if necessary, send updated data to DynaMed. |
PRCVNDR | ||||
| 6856 | COUNTER FILE ACCESS | File | IFCAP | 2017/12/13 | Withdrawn | Private | 422.2 | Above PAR requests permission to update the COUNTER (#422.2) file when sending a FMS VENDOR REQUEST to Austin. Above PAR will create a COUNTER entry to support the FMS VENDOR REQUEST if the COUNTER NAME (.01) is not defined. Above PAR will increment the COUNTER field COUNTER (1). |
||||
| 6857 | AUTOMATED SUPPLY STATION PROCESSING QUEUE FILE ACCESS | File | IFCAP | 2017/12/13 | APPROVED | Active | Private | 447.1 | ABOVE PAR requests permission to check the AUTOMATED SUPPLY STATION PROCESSING QUEUE (#447.1) file's STATION NUMBER (#1) and SECONDARY INVENTORY POINT (#2) fields. |
2018/11/21 | ||
| 6858 | INVENTORY BALANCES FILE ACCESS | File | IFCAP | 2017/12/13 | APPROVED | Active | Private | 445.1 | The INVENTORY BALANCE (#445.1) file stores the beginning monthly balances for the items stored in the inventory points, GENERIC INVENTORY (#445) file. ABOVE PAR checks determines whether the inventory item balance is available and will create the balance record if the item has no balance record. |
2018/12/07 | ||
| 6866 | IFCAP API: BACKGROUND BATCH PRINT CODE SHEETS | Routine | IFCAP | 2018/01/23 | APPROVED | Active | Private | This integration agreement allows the call ^PRCFACB when batching code sheets for inventory transactions. |
PRCFACB | 2018/11/29 | ||
| 6867 | IFCAP API: BACKGROUND RELEASE OF CODE SHEETS | Routine | IFCAP | 2018/01/23 | APPROVED | Active | Private | This integration agreement allows the call ^PRCFACBT to transmit code sheets. |
PRCFACBT | 2018/11/29 | ||
| 6868 | IFCAP API - BUILD AND TRANSMIT CODE SHEET | Routine | IFCAP | 2018/01/23 | APPROVED | Active | Private | This integration agreement allows the call ^PRCFACX2 when creating ISMS code sheet - BUILD AND TRANSMIT CODE SHEET when items are deleted from the Supply Fund Warehouse inventory. |
PRCFACX2 | 2018/11/29 | ||
| 6879 | CREATE BREAKOUT CODES | Routine | IFCAP | 2018/02/26 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call BREAK^PRCHFPDS to create BREAKOUT CODE (#442.16) sub-file entries in the AMOUNT (#442.1) sub-file of the PROCUREMENT & ACCOUNTING TRANSACTIONS (#442) file. |
PRCHFPDS | 2019/06/12 | ||
| 6887 | UNIT OF ISSUE FILE ACCESS (#420.5) | File | IFCAP | 2018/03/05 | APPROVED | Active | Private | 420.5 | Allow direct read of file 420.5, UNIT OF ISSUE. |
2018/03/07 | ||
| 6958 | RETREIVE NEXT COUNTER NUMBER FILE 422.2 | Routine | IFCAP | 2018/08/31 | APPROVED | Active | Private | This integration agreement allows the ABOVE PAR package to call COUNTER^PRCFACP to retrieve next Counter number from file COUNTER (422.2). |
PRCFACP | 2018/11/01 | ||
| 6979 | VENDOR EDIT FILE ACCESS | File | IFCAP | 2018/10/22 | APPROVED | Active | Private | 440.3 | Consistent with IFCAP, Above PAR calls XY^%RCR to back-up the current Vendor entry in file (#440) into a corresponding entry in file (#440.3) so that if the user decides to cancel the update, the original values can be restored. Above PAR deletes the VENDOR EDIT entry when the user confirms that a verification needs to be sent to Austin. |
2019/06/07 | ||
| 7090 | GET SPECIALTY COMMANDS FOR BARCODE PRINT | File | IFCAP | 2019/07/16 | APPROVED | Active | Private | 446.6 | Above PAR requests permission to read the Specialty Commands file in order to print Barcode labels with the command lines After Open, Before Each Label, and After Each Label. |
2019/07/29 | ||
| 7148 | IFCAP API: WORK ORDER XREF UPDATE | Routine | IFCAP | 2020/04/23 | Pending | Private | This integration agreement allows the call to ST^ENWOINV associated with Generate PMI Worklists which creates or finds work orders for a specified PM worklist and then makes calls to print that document. ST component will update the Work Order. |
ENWOINV | ||||
| 7149 | IFCAP API: PMWO WORK ORDER LIST | Routine | IFCAP | 2020/04/23 | Pending | Private | This integration agreement allows the call to LST2^ENEQPMS2 to identify Work Orders associated with specified PM Work Order. |
ENEQPMS2 | ||||
| 7150 | IFCAP API: PMWO WORK ORDER COMPLETED | Routine | IFCAP | 2020/04/23 | Pending | Private | This integration agreement allows the call to TEST^ENWOCOMP to check if the Work Orders can be marked completed. |
ENWOCOMP | ||||
| 7151 | IFCAP API: FRCMR GENERATE FR DOC | Routine | IFCAP | 2020/04/23 | Pending | Private | This integration agreement allows the call to $$$$FRCMR^ENFAEIL, used to generate FR Documents without user interaction. It's called when a batch of FR Documents are being sent due to a change of CMR name or EIL cost center. |
ENFAEIL | ||||
| 7158 | ERT - CONTROL POINT ACTIVITY | File | IFCAP | 2020/05/08 | Withdrawn | Private | 410.2 | Enterprise Reporting Tool (ERT) requests read access to Control Point Activity (#410.2) field NAME (#.01). |
||||
| 7159 | ERT - CALM/LOG CODE SHEET | File | IFCAP | 2020/05/08 | Withdrawn | Private | 423 | Enterprise Reporting Tool (ERT) requests read access to Calm/Log Code Sheet (#423) field ID# (#.01). |
||||
| 7172 | ERT - PURCHASE ORDER STATUS | File | IFCAP | 2020/05/08 | Withdrawn | Private | 442.3 | Enterprise Reporting Tool (ERT) requests read access to PURCHASE ORDER STATUS (#442.3) fields NAME (#.01), SUPPLY STATUS ORDER (#.02), and FISCAL STATUS ORDER (#.03). |
||||
| 7235 | ET DDA Segments for PC Charge and PC Order | Routine | IFCAP | 2021/03/22 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP APIs for building the DDA segment for the Purchase Card Charge and the DDA for the Purchase Card Order. The DDAs are then compared to determine if an ET transaction needs to be generated to correct the accounting string for the charge's expense in FMS. |
PRCH0A | 2021/04/20 | ||
| 7236 | AUTO-GENERATE FMS ET-DOCUMENTS | Routine | IFCAP | 2021/03/22 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCH8A to auto-generate a Financial Management System (FMS) Expenditure Transfer (ET)-document. |
PRCH8A | 2021/04/21 | ||
| 7237 | PRCD FUND/APPROPRIATION CODE FILE ACCESS | File | IFCAP | 2021/03/22 | APPROVED | Active | Private | 420.3 | The Advanced Prosthetics Acquisition Tool (APAT) requests permission to read the PRCD FUND/APPROPRIATION CODE FILE (#420.3) file when reconciling purchase card orders. APAT will look up the Fund entry in file #420.3 using the "B" cross reference in order to determine if the fund is a revolving fund based on the entry's value in the YES/NO field REVOLVING FUND (#7). |
2021/04/20 | ||
| 7248 | EDIT 2237 RUNNING BALANCE FIELDS | Routine | IFCAP | 2021/04/19 | APPROVED | Active | Private | This integration agreement allows the Advanced Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRC0G during purchase card order reconciliation and during the removal of a reconciliation to edit RUNNING BALANCE QUARTER DATE (#449) and RUNNING BALANCE STATUS (#450), if necessary, in the CONTROL POINT ACTIVITY #410 file. |
PRC0G | 2021/05/14 | ||
| 7324 | REQUEST WORKSHEET FILE ACCESS | File | IFCAP | 2022/01/31 | APPROVED | Active | Controlled Subscription | 443 | Above PAR requests permission to read from the REQUEST WORKSHEET FILE #443 to validate the WORKSHEET REQUEST has a VALIDATION CODE field (#3). Above PAR Ad-Hoc Reporting includes the REQUEST WORKSHEET file #443. Ad-Hoc functionality provides the ability to select fields from the file for display on user-defined reports. Ad-Hoc offers only FileMan read access and only if the user has permission to view the file. |
2022/02/17 | ||
| 7328 | VENDOR UEI VALIDATION | Routine | IFCAP | 2022/03/04 | APPROVED | Active | Controlled Subscription | This integration agreement grants permission to invoke IFCAP APIs used to validate the GSA SAM UEI (Unique Entity Identifier) field (#55) in the Vendor file (#440). The UEI is a 12-character field. The 12th character is the check digit. The UEI cannot contain the letter O or I and cannot begin with digit 0. |
PRCHEUI | 2022/08/17 | ||
| 7411 | MANUFACTURER File Access | File | IFCAP | 2023/01/10 | APPROVED | Active | Private | 440.4 | The ADVANCED PROSTHETICS ACQUISITION TOOL (APAT) requests FileMan read access to the MANUFACTURER (#440.4) file to determine if a manufacturer is active or inactive. Navigation to the MANUFACTURER file will use ITEM MASTER (#441) field MANUFACTURER (#25) which points to file 440.4. |
2023/01/10 | ||
| 7547 | GENERIC INVENTORY FILE ACCESS | File | IFCAP | 2025/04/22 | Active | Controlled Subscription | 445 | Provides ability to read the GENERIC INVENTORY FILE #445 to display the Inventory Point. |
||||
| 10085 | PRCPUSA | Routine | IFCAP | APPROVED | Active | Supported | PRCPUSA |