| 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 |
| 25 | DBIA25 | File | PHARMACY DATA MANAGEMENT | 1989/09/18 | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at REDACTED OI SDD PHARM REENG DEV using Microsoft Outlook. Redaction applied since Retired. |
||||
| 106 | DBIA106 | File | PHARMACY DATA MANAGEMENT | 2005/06/20 | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. Routine QIP3POLY reads the following fields: In file 50, DRUG .01 - GENERIC NAME 2 - VA CLASSIFICATION 3 - DEA, SPECIAL HDLG |
||||
| 117 | DBIA117 | File | PHARMACY DATA MANAGEMENT | 2005/11/14 | Retired | Controlled Subscription | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at REDACTED OI SDD PHARM REENG DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Amended August 30, 1994. |
||||
| 129 | DBIA129 | Routine | PHARMACY DATA MANAGEMENT | 1991/11/21 | APPROVED | Active | Private | Call to STAT^PSOEXDT: The routine expects the 0 node of the prescription in RX0, the 2 node of the prescription in RX2 and returns the printable form of the prescription status in ST. The call will be abandonded when Health Summary provides the clinical information. |
PSOEXDT | |||
| 191 | DBIA191-A | Routine | PHARMACY DATA MANAGEMENT | 1992/08/18 | Retired | Private |
^PSOPS: This entry point(and re-entry point) is the functional Pharmacy Patient profile. This tool is used for acquisition of display only data for use in Rheumatology reports. |
PSOPS | ||||
| 208 | PSSGIU | Routine | PHARMACY DATA MANAGEMENT | 1993/02/18 | APPROVED | Active | Private | The Surgery package is given formal permission from Inpatient Medications to make calls to the routine PSGIU to mark and unmark entries in the DRUG file (#50) for anesthesia use. The entry points ENS^PSGIU and END^PSGIU are the same entry points Surgery Version 2.12 has been using and we want to continue using them in Version 3.0. Both entry points are documented in the Inpatient Medications Technical Manual for Version 4.0. |
PSSGIU | |||
| 221 | DBIA221-A | File | PHARMACY DATA MANAGEMENT | 1999/05/24 | APPROVED | Active | Controlled Subscription | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 50 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. |
|||
| 270 | DBIA270-A | File | PHARMACY DATA MANAGEMENT | 1993/08/26 | APPROVED | Active | Private | 52.6 | Drug Accountability will use the IV STATS (#50.8) file to update IV dispensing activity in a Drug Accountability Location. To correctly identify the DRUG (#50) file entry a look up is first made to the IV ADDITIVES (#52.6) and/or the IV SOLUTION (#52.7) files. Looping through ^PS(50.8,D0), all IV Rooms are checked. Looping through ^PS(50.8,D0,2,D1), dates are checked. Looping through ^PS(50.8,D0,2,D1,2,D2), drugs are checked with support from the "AC" x-ref. Looping through ^PS(50.8,D0,2,D1,2,D2,3,D3), ward is checked. It is here that, if a match occurs, $P($G(^PS(50.8,D0,2,D1,2,D2,3,D3,0)),U,2)-$P($G(^(0)),U,5) is used to update the balance in Drug Accountability. GLOBAL MAP DATA DICTIONARY #52.6 -- IV ADDITIVES FILE STORED IN ^PS(52.6, (1 ENTRY) SITE: BIRMINGHAM ISC ------------------------------------------------------------------------ CROSS REFERENCED BY: GENERIC DRUG(AC) ^PS(52.6,D0,0)= (#1) GENERIC DRUG [2P] |
|||
| 273 | DBIA273-A | File | PHARMACY DATA MANAGEMENT | 1993/08/30 | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. #50 DRUG FILE ^PSDRUG( To maintain backward compatibility with Outpatient Pharmacy V5.6 50,623001 DALLAS COMMENTS 623001;1 FREE TEXT 50,623002 LAB TEST MONITOR 623002;1 POINTER TO LABORATORY TEST FILE (#60) 50,623003 MONITOR MAX DAYS 623002;2 NUMBER 50,623004 SPECIMEN TYPE 623002;3 POINTER TO TOPOGRAPHY FIELD FILE (#61) 50,623008 MONITOR ROUTINE 623008;1 FREE TEXT To maintain compatibility with Outpatient Pharmacy V6.0 50,17.2 LAB TEST MONITOR CLOZ;1 POINTER TO LABORATORY TEST FILE (#60) 50,17.3 MONITOR MAX DAYS CLOZ;2 NUMERIC 50,17.4 SPECIMEN TYPE CLOZ;3 POINTER TO TOPOGRAPHY FIELD FILE (#61) 50,17.5 MONITOR ROUTINE CLOZ1;1 FREE TEXT |
||||
| 276 | DBIA276-A | File | PHARMACY DATA MANAGEMENT | 1993/09/09 | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. Mental Health V. 5.0 references the following Outpatient pharmacy files and fields: File #50 - Drug Field #.01 - Generic Name - ^PSDRUG(D0,0) piece 1 |
||||
| 302 | DBIA302-A | File | PHARMACY DATA MANAGEMENT | 1993/10/25 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. The PDX application is granted read access to the following fields and, if listed, their associated cross references: File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 50 .01 0;1 GENERIC NAME B 20 ND;1 NATIONAL DRUG FILE ENTRY |
|||
| 436 | DBIA436 | File | PHARMACY DATA MANAGEMENT | 1994/04/11 | APPROVED | Active | Controlled Subscription | 52.6 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. |
|||
| 437 | DBIA437 | File | PHARMACY DATA MANAGEMENT | 1994/04/11 | APPROVED | Active | Controlled Subscription | 52.7 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. |
|||
| 473 | DBIA473 | File | PHARMACY DATA MANAGEMENT | 1994/04/26 | Retired | Private | 52.6 | D&PPM uses the IV Additives file to obtain the Generic Drug name. |
||||
| 474 | DBIA473 | File | PHARMACY DATA MANAGEMENT | 1994/04/26 | Retired | Private | 52.7 | Pharmacy Benefits Management uses the IV solutions file to obtain the generic drug name. |
||||
| 477 | DBIA477 | File | PHARMACY DATA MANAGEMENT | 1994/06/13 | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. DSS Extracts will reference the following data from the DRUG file (#50). DSS uses the "B" cross reference on the GENERIC NAME field. The DSS Extracts IV EXTRACT DATA file (#728.113) and UNIT DOSE EXTRACT DATA file (#728.904) contain a field, DRUG, which is a pointer to the DRUG file (#50). |
||||
| 516 | DBIA34-B | File | PHARMACY DATA MANAGEMENT | 1989/03/13 | Retired | Private | 50 | Direct references are made to the globals to get allergy information. |
||||
| 522 | DBIA60-B | File | PHARMACY DATA MANAGEMENT | 1990/12/11 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006 |
||||
| 533 | DBIA68-B | File | PHARMACY DATA MANAGEMENT | 1991/01/31 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 50 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. The following fields are accessed from ^PS( and ^PSDRUG( in a read-only manner: For verified orders: ^PS( 55 PHARMACY PATIENT FILE 55.06 1 Provider 3 Medicinal Route (pointer to ^PS(51.2,) 7 Schedule Type 10 Start Date/Time 26 Schedule 28 Status 34 Stop Date/Time 55.07 .01 Drug (pointer to ^PSDRUG() 1 Dosage Ordered The following cross-references are used: ^PS( 55.06 "AUS" Stop Date/Time |
||||
| 535 | DBIA69-B | File | PHARMACY DATA MANAGEMENT | 2005/11/14 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. The following fields are accessed from ^PS( and ^PSDRUG( in a read-only manner: ^PS(55, PHARMACY PATIENT FILE 55.01 .02 Start Date/Time .03 Stop Date/Time .06 Physician .08 Infusion Rate .09 Schedule 100 Status 55.02 .01 Additive (Pointer to ^PS(52.6,) .02 Strength 55.11 .01 Solution (Pointer to ^PS(52.7,) 1 Volume |
||||
| 536 | DBIA69-C | File | PHARMACY DATA MANAGEMENT | 1991/01/31 | Retired | Private | 52.6 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. ^PS(52.6, IV ADDITIVE FILE 52.6 .01 Additive Name |
||||
| 537 | DBIA69-D | File | PHARMACY DATA MANAGEMENT | 1991/01/31 | APPROVED | Active | Private | 52.7 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. ^PS(52.7, IV SOLUTION FILE 52.7 .01 Solution Name |
|||
| 552 | DBIA90-B | File | PHARMACY DATA MANAGEMENT | 1993/11/01 | Retired | Controlled Subscription | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. |
||||
| 553 | DBIA90-C | File | PHARMACY DATA MANAGEMENT | 1993/11/01 | Retired | Controlled Subscription | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. Amended August 30, 1994. |
||||
| 567 | DBIA106-C | File | PHARMACY DATA MANAGEMENT | 2005/06/20 | Retired | Private | 55 | Routine QIP3POLY reads the following fields: In file 55, PHARMACY PATIENT, the cross reference ^PS(55,DFN,"P","A",DATE,RX) The above references will be made from the QIP3POLY routine which, while belonging to the QIP namespace, will be maintained by the pharmacy developers. Coordination of release and patches will be through the QIP custodial ISC. Amendment to DBIA 106 approved 10/10/93: QUIC is requesting the following be added to DBIA #106. The additional files/fields will be used to report the rate of completion of at least one Glycosalated Hemoglobin measurement within one year for diabetic patients on a medication regimen. #55, PHARMACY PATIENT file .01 NAME 55.06,55.02,.01 DISPENSED DRUG 55.06,28 STATUS 55.01,55.02,.01 ADDITIVES 55.01,100 STATUS Cross reference ^PS(55,DFN,5,"AUS",DATE/TIME,DA) With the "AUS" cross reference, I am referencing the DISPENSE DRUG and TATUS (#28) fields. 5,D0,5,D1,0)=^^^^^^^^ (#28) STATUS [9S] ^ (55,D0,5,D1,1,D2,0)= (#.01) DISPENSE DRUG [1P] ^ |
||||
| 568 | DBIA106-D | File | PHARMACY DATA MANAGEMENT | 2005/06/20 | Retired | Private | 52.6 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. Amendment to DBIA 106 approved 10/10/93: QUIC is requesting the following be added to DBIA #106. The additional files/fields will be used to report the rate of completion of at least one Glycosalated Hemoglobin measurement within one year for diabetic patients on a medication regimen. #52.6, IV ADDITIVES file .01 PRINT NAME |
||||
| 590 | DBIA124-C | File | PHARMACY DATA MANAGEMENT | 1991/11/06 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. C. Direct reference to ^PSRX(n,0) and ^PSDRUG(n,0) by Integrated Billing for use to determine prescription number and drug name when calculating the Brief Description field. The MUMPS code to do this is stored in the IB ACTION TYPE file. D. Direct reference to ^PSRX by Integrated Billing to determine if the link between Integrated Billing and the Prescription file is intact. |
|||
| 619 | DBIA149-D | File | PHARMACY DATA MANAGEMENT | 1995/02/27 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. The Adverse Reaction Tracking (ART) package will point to the Drug (50) file. The ART package will: a. Use a direct global read on the GENERIC NAME (.01) field of the DRUG (50) file to get the Name of an entry, e.g., Name=$P(^PSDRUG(DA,0),"^"). b. Use a direct global read on the VA CLASSIFICATION (2) field of the DRUG (50) file to get the VA Drug Class of an entry, e.g., VA Class=$P(^PSDRUG(DA,0),"^",2). c. Use a direct global read on the NATIONAL DRUG CLASS (25) field of the DRUG (50) file to get the VA Drug Class of an entry, e.g., Drug Class=$P(^PSDRUG(DA,"ND"),"^",6). In each of these examples DA is an entry in the DRUG (50) file. |
|||
| 674 | DBIA191-B | Routine | PHARMACY DATA MANAGEMENT | 1992/08/18 | APPROVED | Active | Private |
^PSODEM: This is Pharmacy's MAS patient demographic function which is used in conjunction with the Pharmacy Patient profile. The input variable is DA and is the internal entry number of the VA Patient file and is equivalent to the DFN. |
PSODEM | |||
| 676 | DBIA191-D | Routine | PHARMACY DATA MANAGEMENT | 1992/08/18 | APPROVED | Active | Private |
DOIT^PSOP: This is the Pharmacy queue report entry point. |
PSOP | |||
| 677 | DBIA191-E | File | PHARMACY DATA MANAGEMENT | 1992/08/18 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006 ^PS(55,DA,"P") and ^PS(55,DA,"ARC") in order to screen the file for relevant data. |
||||
| 679 | DBIA191-G | File | PHARMACY DATA MANAGEMENT | 1992/08/18 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. ^PSDRUG(DA, for drug data. |
|||
| 693 | DBIA221-C | File | PHARMACY DATA MANAGEMENT | 1993/04/21 | Retired | Private | 55 | Outpatient Pharmacy is given permission by Pharmacy to make the following calls: GLOBAL MAP DATA DICTIONARY #55 -- PHARMACY PATIENT FILE 2/26/93 STORED IN ^PS(55, SITE: ISC BIRMINGHAM ---------------------------------------------------------------------- ^PS(55,D0,0)= (#.01) NAME [1P] ^ (#.02) CAP [2S] ^ (#.03) MAIL [3S] ^ ==>(#.04) DIALYSIS PATIENT [4S] ^ ^PS(55,D0,1)= (#1) NARRATIVE [1F] ^ ^PS(55,D0,40)= (#40) COMMUNITY NURSING HOME [1S] ^ (#40.1) NURSING HOME ==>CONTRACT [2S] ^ (#40.2) LAST DATE OF CONTRACT [3D] ^ ==>(#41) RESPITE PATIENT START DATE [4D] ^ (#41.1) RESPITE ==>PATIENT END DATE [5D] ^ ^PS(55,D0,ARC,0)=^55.13DA^^ (#101) ARCHIVE DATE ^PS(55,D0,ARC,D1,0)= (#.01) ARCHIVE DATE [1D] ^ ^PS(55,D0,P,0)=^55.03P^^ (#52) PRESCRIPTION PROFILE ^PS(55,D0,P,D1,0)= (#.01) PRESCRIPTION PROFILE [1P] ^ ^PS(55,D0,PS)= (#3) PATIENT STATUS [1P] ^ ^PS(55,D0,SAND)= (#53) CLOZAPINE REGISTRATION NUMBER [1F] ^ (#54) ==>CLOZAPINE STATUS [2S] ^ (#55) DATE OF LAST CLOZAPINE RX [3D] ^ ==>(#56) DEMOGRAPHICS SENT [4S] ^ (#57) RESPONSIBLE PROVIDER ==>[5P] ^ (#58) REGISTRATION DATE [6D] ^ |
||||
| 694 | READ AND WRITE ACCESS TO FILE 59.7 | File | PHARMACY DATA MANAGEMENT | 1993/04/21 | APPROVED | Active | Controlled Subscription | 59.7 | Outpatient Pharmacy is given permission by Pharmacy Data Mgmt for direct global read/write access and read/write access with Fileman to the fields listed explicitly in this agreement which reside on the 47 multiple. CMOP and OPT PS are given read with FM/DGR access permission to all other fields listed explicitly in this agreement. |
2007/04/17 | ||
| 695 | DBIA221-E | File | PHARMACY DATA MANAGEMENT | 2005/07/27 | Retired | Private | 59.9 | Outpatient Pharmacy is given permission by Pharmacy to make the following calls: GLOBAL MAP DATA DICTIONARY #59.9 -- *PHARMACY FUNCTIONS FILE STORED IN ^DIC(59.9 SITE: ISC BIRMINGHAM all fields in the file. |
||||
| 770 | DBIA270-B | File | PHARMACY DATA MANAGEMENT | 1993/08/26 | APPROVED | Active | Private | 52.7 | Drug Accountability will use the IV STATS (#50.8) file to update IV dispensing activity in a Drug Accountability Location. To correctly identify the DRUG (#50) file entry a look up is first made to the IV ADDITIVES (#52.6) and/or the IV SOLUTION (#52.7) files. Looping through ^PS(50.8,D0), all IV Rooms are checked. Looping through ^PS(50.8,D0,2,D1), dates are checked. Looping through ^PS(50.8,D0,2,D1,2,D2), drugs are checked with support from the "AC" x-ref. Looping through ^PS(50.8,D0,2,D1,2,D2,3,D3), ward is checked. It is here that, if a match occurs, $P($G(^PS(50.8,D0,2,D1,2,D2,3,D3,0)),U,2)-$P($G(^(0)),U,5) is used to update the balance in Drug Accountability. GLOBAL MAP DATA DICTIONARY #52.7 -- IV SOLUTIONS FILE STORED IN ^PS(52.7, *** NO DATA STORED YET *** SITE: BIRMINGHAM ISC ------------------------------------------------------------------------ CROSS REFERENCED BY: GENERIC DRUG(AC) ^PS(52.7,D0,0)= (#1) GENERIC DRUG [2P] |
|||
| 781 | DBIA273-C | File | PHARMACY DATA MANAGEMENT | 1993/08/30 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. #55 PHARMACY PATIENT FILE ^PS(55 55,53 CLOZAPINE REGISTRATION NUMBER SAND;1 FREE TEXT 55,54 CLOZAPINE STATUS SAND;2 SET 55,55 DATE OF LAST CLOZAPINE RX SAND;3 DATE 55,56 DEMOGRAPHICS SENT SAND;4 SET 55,57 RESPONSIBLE PHYSICIAN SAND;5 POINTER TO PROVIDER FILE (#6) 55,58 REGISTRATION DATE SAND;6 DATE |
||||
| 787 | DBIA786-D | File | PHARMACY DATA MANAGEMENT | 1993/09/09 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006 File #55 - Pharmacy Patient Field #52 - Prescription Profile - ^PS(55,D0,P,0)=^55.03^^ Field #.01 - Prescription Profile - ^PS(55,D0,P,D1,0) 1 Pointer to the Prescription file #52 |
||||
| 823 | DBIA302-C | File | PHARMACY DATA MANAGEMENT | 1993/10/25 | APPROVED | Active | Private | 51 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 51 .01 0;1 NAME B,A .5 0;3 SYNONYM AD 1 0;2 EXPANSION 0 AB 9 9;1 PLURAL AC |
|||
| 825 | DBIA302-E | File | PHARMACY DATA MANAGEMENT | 1993/10/25 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 55 .01 0;1 NAME B 1 1;1 NARRATIVE 52 (multiple in PRESCRIPTION PROFILE file 55.03) File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 55.03 .01 0;1 PRESCRIPTION PROFILE B,A |
||||
| 886 | DBIA886 | File | PHARMACY DATA MANAGEMENT | 1994/11/17 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. As described in DBIA885, External Peer Review needs to identify patients receiving prescriptions in certain VA classes. |
|||
| 895 | PSSGIU | Routine | PHARMACY DATA MANAGEMENT | 1994/06/24 | APPROVED | Active | Controlled Subscription | Gives the ability to mark entries in the Drug file (50) for use with various packages. |
PSSGIU | |||
| 901 | PSSJEEU | Routine | PHARMACY DATA MANAGEMENT | 1994/06/24 | APPROVED | Active | Controlled Subscription | This is a set of utilities that can be used to create, validate and process order timing schedules. |
PSSJEEU | |||
| 921 | DBIA921 | File | PHARMACY DATA MANAGEMENT | 1994/07/27 | APPROVED | Active | Private | 52.6 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. Read only access for the ^PS(52.6,X,0) node. In routines LRBLPE1 and LRBLPH: ...I $D(^PS(52.6,X,0)...W !,"IV DRUG: ",$P(^(0),"^") |
|||
| 922 | DBIA922 | File | PHARMACY DATA MANAGEMENT | 1994/07/27 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006 Read only access to the following nodes in the Pharmacy Patient file #55. All these references are found in routines LRBLPE1 and LRBLPH. ^PS(55,DFN,"IV",X,"AD",Y,0) K ^TMP($J) F X=0:0 S X=$O(^PS(55,DFN,"IV",X)) Q:'X!(R[U) F Y=0:0 S Y=$O(^PS(55,DFN,"IV",X,"AD",Y)) Q:'Y!(R[U) S ^TMP($J,+^(Y,0))="" ^PS(55,DFN,5,X,1,Y,0) K ^TMP($J) F X=0:0 S X=$O(^PS(55,DFN,5,X)) Q:'X!(R[U) F Y=0:0 S Y=$O(^PS(55,DFN,X,1,Y)) Q:'Y!(R[U) S ^TMP($J,+^(Y,0)="" NOTE: Inpatient Medication allows direct access to the Inpatient Medication data, with the understanding that this structure may change in Inpatient Meds version 5.0. If a change is necessary, Lab will need to supply a patch to call an Inpatient utility to provide this data rather than directly accessing the global. |
||||
| 934 | DBIA934 | Routine | PHARMACY DATA MANAGEMENT | 1994/08/05 | APPROVED | Active | Private | This is for Pharmacy 6.0 and greater. |
PSOP | |||
| 984 | MED ROUTES | File | PHARMACY DATA MANAGEMENT | 1994/08/30 | Pending | Controlled Subscription | 51.2 | |||||
| 995 | DBIA995 | File | PHARMACY DATA MANAGEMENT | 1994/08/31 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Read only access to the following nodes in the Pharmacy Patient file #55. This reference is found in routines LRBLPE1 and LRBLPH. ^PS(55,DFN,"P",X,0) F X=0:0 S X=$O(^PS(55,DFN,"P",X)) Q:'X I $D(^(X,0)) S Y=+^(0) I $D(^PSRX(Y,0))... |
||||
| 1080 | DBIA1079-B | File | PHARMACY DATA MANAGEMENT | 1994/12/13 | APPROVED | Active | Private | 55 | ||||
| 1223 | DBIA1220-D | File | PHARMACY DATA MANAGEMENT | 1995/05/09 | APPROVED | Active | Private | 54 | The Consolidated Mail Outpatient Pharmacy package modified the input transform for the .01 to prevent the editing of the first 21 entries after the CMOP installation. This will provide consistency in the drug warnings transmitted with drugs to be dispensed by the CMOP. |
|||
| 1224 | DBIA1220-E | File | PHARMACY DATA MANAGEMENT | 1995/05/08 | Retired | Private | 50 | The CONSOLIDATED MAIL OUTPATIENT PHARMACY package creates and maintains data in these fields. |
||||
| 1231 | DBIA1231 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Controlled Subscription | 52.6 | This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 1299 | DBIA1299 | File | PHARMACY DATA MANAGEMENT | 1997/05/15 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. A direct reference to the Drug file is requested for the Price Per Dispense Unit field so the VA Cost of a drug can be calculated and billed. |
|||
| 1427 | PHARMACY SYSTEM | File | PHARMACY DATA MANAGEMENT | 1995/11/20 | Retired | Private | 59.7 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Vitals/Measurements can access the Pharmacy Sytsem (59.7) file as described in this DBIA. |
||||
| 1880 | DBIA1880 | File | PHARMACY DATA MANAGEMENT | 1996/12/12 | APPROVED | Active | Private | 52.6 | DSS Extracts references the following data from the IV ADDITIVES file (#52.6). This reference is used ONLY for the small number of sites who are still running a version of Inpatient Meds prior to version 4.5. For version 4.5 (or greater), this information comes from the IV EXTRACT DATA holding file (#728.113) which is populated by PSIVSTAT. |
|||
| 1881 | DBIA1881 | File | PHARMACY DATA MANAGEMENT | 1996/12/12 | Retired | Private | 52.7 | DSS Extracts references the following data from the IV SOLUTIONS file (#52.7). This reference is used ONLY for the small number of sites who are still running a version of Inpatient Meds prior to version 4.5. For version 4.5 (or greater), this information comes from the IV EXTRACT DATA holding file (#728.113) which is populated by PSIVSTAT. |
||||
| 1883 | DBIA1883 | File | PHARMACY DATA MANAGEMENT | 1996/12/13 | Retired | Private | 55 | DSS Extracts references the following data from the PHARMACY PATIENT file (#55). This integration agreement is for version 4.5 (or less) of Inpatient Medications. When version 5.0 of Inpatient Medications is released, this reference must be replaced. At that time, the information will be returned as part of the data stream that is passed in PSIVSTAT. |
||||
| 1930 | DBIA1930 | File | PHARMACY DATA MANAGEMENT | 1997/02/13 | APPROVED | Active | Private | 59.7 | Controlled Substances needs to check the DATE OP INSTALLED field before posting outpatient prescriptions and the DATE V2 CS/DA CONVERSION field before doing a conversion in a post-init. |
|||
| 1931 | DBIA1931 | File | PHARMACY DATA MANAGEMENT | 1997/02/13 | APPROVED | Active | Controlled Subscription | 51.5 | Various pharmacy packages need read access to this file. |
|||
| 1961 | DBIA1961 | File | PHARMACY DATA MANAGEMENT | 1997/03/20 | Retired | Private | 51.5 | Drug Accountability v3.0 needs write access to the ORDER UNIT (51.5) file. A new SYNONYM multiple needs to be written to. |
||||
| 1967 | DBIA1967 | File | PHARMACY DATA MANAGEMENT | 1997/03/27 | APPROVED | Active | Private | 51.5 |
This data is accessed when a drug is marked for CMOP. |
|||
| 1979 | DBIA1979 | File | PHARMACY DATA MANAGEMENT | 1997/03/28 | APPROVED | Active | Private | 54 | The Consolidated Mail Outpatient Pharmacy package has modified the input transform for the .01 field in the RX CONSULT file (#54). This modification will prevent the first 20 entries in the file from being edited. This is necessary to provide uniformity in the drug warnings that are transmitted to the CMOP with each prescription. The drug warnings are passed by their record number in the RX CONSULT file from the hospital to the CMOP facility and then on to the vendor system. These numbers must match between all the medical centers using the CMOP software, the CMOP Facility, and the vendor system, or the incorrect drug warning could be printed on the prescription label. The modified input transform is shown below: ^DD("54",".01","0")="NAME^RFX^^0;1^K:$L(X)>25!($L(X)<1)!"(X"?1P.E)!(($G(DA )>0)&($G(DA)<21)) X" |
|||
| 1980 | DBIA1980 | File | PHARMACY DATA MANAGEMENT | 1997/03/28 | APPROVED | Active | Controlled Subscription | 51 | The Consolidated Mail Outpatient Pharmacy package accesses the 'A' cross reference in the MEDICATION INSTRUCTION file (#51). This cross reference used to expand the SIG in order to send this data with the prescription when it is transmitted to the CMOP facility to be filled. The CMOP package only reads the data in this cross reference. |
|||
| 1981 | DBIA1981 | File | PHARMACY DATA MANAGEMENT | 1997/03/28 | Retired | Private | 59.7 | |||||
| 1982 | DBIA1982 | File | PHARMACY DATA MANAGEMENT | 1997/03/28 | Retired | Private | 55 | |||||
| 1983 | DBIA1983 | File | PHARMACY DATA MANAGEMENT | 1997/03/28 | APPROVED | Active | Private | 50 | The CMOP package requires direct R/W access to all fields and cross-references in file 50. |
|||
| 2015 | DBIA2015 | File | PHARMACY DATA MANAGEMENT | 1997/04/29 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. The Immunology Case Registry package (ICR) extracts Outpatient Pharmacy data to the National registry for the tracking of disease categories such as HIV and Renal Failure. The ICR SITE PARAMETERS file (#158.9) contains two fields, ENTRY IN DRUG FILE and NDF ENTRY, which is a pointer to the Drug file (#50) and NATIONAL DRUG FILE ENTRY field (#20). In order to consolidate local drug names with the National Drug File name for reporting purposes in the national registry, the Immunology Case Registry package requests a DBIA to point to the following file. Global: ^PSDRUG( Drug File #50 Field : .01 GENERIC NAME 0;1 DIRECT GLOBAL READ 20 NATIONAL DRUG FILE ENTRY ND;1 DIRECT GLOBAL READ |
|||
| 2095 | DBIA2095 | File | PHARMACY DATA MANAGEMENT | 1997/09/04 | APPROVED | Active | Private | 50 | Drug Accountability/Inventory Interface (DA) v3.0 interfaces with the DRUG (#50) file to assist Pharmacy in maintaining a perpetual inventory. DA contains two methods of maintaining the drug balances. The site can either interface with the Generic Inventory Package (GIP) or with the prime vendor's electronic invoice data. The DRUG file is used to store matches between drugs and either an item in GIP or the NDC in the prime vendor's invoice data. It is also used to identify matched drugs when they are received and dispensed drugs via other VISTA Pharmacy packages. When the fields are read, it is by a direct global read. When the fields are written to, it is by a FileMan DIE call. Read fields: ============ GLOBAL MAP DATA DICTIONARY #50 -- DRUG FILE -------------------------------------------------------------------------- ^PSDRUG(D0,0)= (#.01) GENERIC NAME [1F] ^ ^ ^ ^ ^ (#6) FSN [6F] ^ ^ ^ ==>(#51) NON-FORMULARY [9S] ^ ^ ^PSDRUG(D0,1,0)=^50.1A^^ (#9) SYNONYM ^PSDRUG(D0,1,D1,0)= (#.01) SYNONYM [1F] ^ (#2) NDC CODE [2F] ^ ==>(#1) INTENDED USE [3S] ^ (#400) VSN [4F] ^ (#401) ==>ORDER UNIT [5P] ^ (#402) PRICE PER ORDER UNIT [6N] ^ ==>(#403) DISPENSE UNITS PER ORDER UNIT [7N] ^ (#404) ==>PRICE PER DISPENSE UNIT [8N] ^ (#405) VENDOR [9F] ^ ^PSDRUG(D0,2)= ^ ^ (#63) APPLICATION PACKAGES' USE [3F] ^ (#31) NDC [4F] ^ ^PSDRUG(D0,441,0)=^50.0441P^^ (#441) IFCAP ITEM NUMBER ^PSDRUG(D0,441,D1,0)= (#.01) ITEM NUMBER [1P] ^ ^PSDRUG(D0,660)= ^ (#12) ORDER UNIT [2P] ^ (#13) PRICE PER ORDER UNIT [3N] ==>^ ^ (#15) DISPENSE UNITS PER ORDER UNIT [5N] ^ (#16) ==>PRICE PER DISPENSE UNIT [6N] ^ ^ (#14.5) DISPENSE UNIT ==>[8F] ^ ^PSDRUG(D0,660.1)= (#50) CURRENT INVENTORY [1N] ^ ^PSDRUG(D0,I)= (#100) INACTIVE DATE [1D] ^ ^PSDRUG(D0,ND)= (#20) NATIONAL DRUG FILE ENTRY [1P] ^ (#21) VA PRODUCT ==>NAME ENTRY [2N] ^ (#22) PSNDF VA PRODUCT NAME ENTRY [3N] ^ ==>(#23) PACKAGE SIZE [4P] ^ (#24) PACKAGE TYPE [5P] ^ Cross-references Read: ===================== ITEM NUMBER(AB), VSN(AVSN), SYNONYM(C), VA PRODUCT NAME(VAPN), NDC(NDC) Fields Written to: ================== GLOBAL MAP DATA DICTIONARY #50 -- DRUG FILE -------------------------------------------------------------------------- ^PSDRUG(D0,0)= (#.01) GENERIC NAME [1F] ^ ^PSDRUG(D0,1,0)=^50.1A^^ (#9) SYNONYM ^PSDRUG(D0,1,D1,0)= (#.01) SYNONYM [1F] ^ (#2) NDC CODE [2F] ^ ==>(#1) INTENDED USE [3S] ^ (#400) VSN [4F] ^ (#401) ==>ORDER UNIT [5P] ^ (#402) PRICE PER ORDER UNIT [6N] ^ ==>(#403) DISPENSE UNITS PER ORDER UNIT [7N] ^ (#404) ==>PRICE PER DISPENSE UNIT [8N] ^ (#405) VENDOR [9F] ^ ^PSDRUG(D0,2)= ^ ^ ^ (#31) NDC [4F] ^ ^PSDRUG(D0,441,0)=^50.0441P^^ (#441) IFCAP ITEM NUMBER ^PSDRUG(D0,441,D1,0)= (#.01) ITEM NUMBER [1P] ^ ^PSDRUG(D0,660)=^ (#12) ORDER UNIT [2P] ^ (#13) PRICE PER ORDER UNIT [3N] ==>^ ^ (#15) DISPENSE UNITS PER ORDER UNIT [5N] ^ (#16) ==>PRICE PER DISPENSE UNIT [6N] ^^ (#14.5) DISPENSE UNIT [8F] ^PSDRUG(D0,660.1)= (#50) CURRENT INVENTORY [1N] ^ Three print templates are used to print two reports. PSADRIP and PSADRIH are used to print the DRUG file/ITEM MASTER file Comparison Report from a selected sort range The report contains information on packaging and pricing. PSADRIH is the header on this report. PSADRI is used to print the Inquire/Compare DRUG file/ITEM MASTER file report that compares the packaging and pricing between the DRUG file and the ITEM MASTER file. |
|||
| 2127 | DBIA2127 | File | PHARMACY DATA MANAGEMENT | 1997/09/08 | APPROVED | Active | Private | 50.3 | This file was originally associated with Inpatient Medications as the custodial package. Due to the conversion of Rational to GitHub, this file is now assigned to the Pharmacy Data Management Package, making this ICR no longer necessary because PDM was the only subscribing package. Additionally the 50.3 file is no longer used, but has not gone through a formal retirement in the ICRs. Old text before 9/1/20: PDM requests permission to look at PRIMARY DRUG file 50.3. |
2020/09/01 | ||
| 2141 | DBIA2141 | File | PHARMACY DATA MANAGEMENT | 1997/09/09 | Pending | Private | 51.5 | Drug Accountability/Inventory Interface (DA) is requesting an integration agreement with Pharmacy Data Management to create and write to a new SYNONYM field in a new SYNONYM multiple. In the DA v3.0 prime vendor interface, the prime vendor sends an invoice data file containing line items that were shipped. Each line item has a two-character order unit. If their order unit is not in the ORDER UNIT FILE, the user is asked to match it to an existing order unit. When the data is verified, the prime vendor's two-character order unit is added to the SYNONYM field (#.01) in the SYNONYM multiple and in a new "APV" cross-reference. The next time the order unit is received the link is used to the ABBREVIATION field (#.01). This is done by reading the "APV" cross-reference. |
||||
| 2173 | DBIA2173 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Controlled Subscription | 52.7 | This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 2174 | DBIA2174 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Controlled Subscription | 50.606 | Inpatient Medications request permission to look at DOSAGE FORM file 50.606. This file was previously in National Drug File. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 2175 | DBIA2175 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Private | 50.4 | Inpatient Medications requests permission to look at DRUG ELECTROLYTES file 50.4. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 2176 | DBIA2176 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Private | 51 | Inpatient Medications request permission to look at MEDICATION INSTRUCTION file 51. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 2177 | DBIA2177 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Private | 51.1 | Inpatient Medications requests permission to look at ADMINISTRATION SCHEDULE file 51.1. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 2178 | DBIA2178 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Controlled Subscription | 51.2 | Inpatient Medications request permission to look at MEDICATION ROUTES file 51.2. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 2179 | DBIA2179 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Private | 9009032.4 | Inpatient Medications requests permission to look at APSP INTERVENTION file 9009032.4. |
2025/05/28 | ||
| 2180 | DBIA2180 | File | PHARMACY DATA MANAGEMENT | 1997/10/14 | APPROVED | Active | Controlled Subscription | 50.7 | Inpatient Medications request permission to look at PHARMACY ORDERABLE ITEM file 50.7. This is a new file with Pharmacy Data Management v1.0. It is used extensively throughout our routines. We are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. |
|||
| 2181 | DBIA2181 | File | PHARMACY DATA MANAGEMENT | 1997/10/15 | APPROVED | Active | Private | 59.7 | Inpatient Medications requests permission to look at the following fields in the PHARMACY SYSTEM file 59.7. Revisions: The CPRS33 project included updates to add two new fields, approved by the DBA: 59.7,103 DURATION OVERRIDE HANDLING 62;1 59.7,104 DURATION OVERRIDE MESSAGE 62;2 The new fields will be used (read) by the INPATIENT MEDICATIONS application, PSS*1*251 and PSJ*5.0*375. FIELD NUMBER NAME NODE AND PIECE 59.7,20.01 IV STATS/200 CONVERSION STATUS 20;10 59.7,20.1 VERSION NUMBER LAST INITS RUN 20;1 59.7,20.11 NEW PERSON CONVERSION DATE 20;11 59.7,20.12 PRIMARY DRUG CONVERSION DATE 20;12 59.7,20.13 DATE V4 PRE-PACKET INSTALLED 20;13 59.7,20.14 LAST N-V ORDER CONVERTED TO V4 20;14 59.7,20.15 DATE NON-VERIFIED CONVERTED 20;15 59.7,20.16 ORDERABLE ITEM CONVERSION DATE 20;16 59.7,20.2 DATE INITS LAST RUN 20;2 59.7,20.3 USER TO LAST RUN INITS 20;3 59.7,20.4 SITE FOR BACKGROUND JOB 20;4 59.7,20.401 UD STATS/200 CONVERSION MARKER 20.4;1 59.7,20.402 IV STATS/200 CONVERSION STATUS 20.4;2 59.7,20.403 NEW PERSON CONVERSION DATE 20.4;3 59.7,20.404 LAST N-V ORDER CONVERTED TO V4 20.4;4 59.7,20.405 DATE NON-VERIFIED CONVERTED 20.4;5 59.7,20.406 LAST PAT CONVERTED FOR VER 4 20.4;6 59.7,20.407 LAST PICK LIST TO PD MARKER 20.4;7 59.7,20.408 DATE PICK LISTS CONVERT TO PD 20.4;8 59.7,20.409 ORDER SET CONVERSION MARKER 20.4;9 59.7,20.41 ORDER SET CONVERSION DATE 20.4;10 59.7,20.411 DATE UD STATS FILE CONVERTED 20.4;11 59.7,20.5 DATE ATC DATA CONVERTED 20;5 59.7,20.6 DEFAULT WARD 20;6 59.7,20.8 LAST PATIENT CONVERTED TO V4 20;8 59.7,20.9 UD STATS/200 CONVERSION STATUS 20;9 59.7,21 NON-FORMULARY MESSAGE 21;0 59.7,22 WARD ACTIONS 22;0 59.722,.01 FROM WARD 0;1 59.722,1 TO WARD 1;0 59.7221,.01 TO WARD 0;1 59.722,2 'ON PASS' ACTION 0;2 59.722,3 ACTION ON AUTHORIZED ABSENCE 0;3 59.722,4 ACTION ON UNAUTHORIZED ABSENCE 0;4 59.7,23 D/C ON SERVICE TRANSFER 23;0 59.723,.01 FROM SERVICE 0;1 59.723,1 TO SERVICE 1;0 59.7231,.01 TO SERVICE 0;1 59.7,25 INPATIENT ORDER NUMBER 25;E1,245 59.7,25.1 DATE 5.0 UD VER CONV FINISHED 20.5;1 59.7,25.2 DATE 5.0 CONVERSION COMPLETED 20.5;2 59.7,25.3 DATE 5.0 PICK LIST CONV FINISH 20.5;3 59.7,25.4 DATE 5.0 ORDER SET CONV FINISH 20.5;4 59.7,26 PRINT 6 BLOCKS FOR THE PRN MAR 26;1 59.7,26.2 ATC SORT PARAMETER 26;2 59.7,26.3 PRINT DIET ABBR LABEL ON MAR 26;3 59.7,26.4 MAR SORT 26;4 59.7,26.5 CALC UNITS NEEDED PRN ORDERS 26;5 59.7,26.6 DAYS UNTIL STOP FOR ONE-TIME 26;6 59.7,26.7 ROUND ATC PICK LIST UNITS 26;7 59.7,26.8 EFD SCHEDULE 26;8 59.7,30.1 DATE IV ORDERS CONVERTED 30;1 59.7,30.2 LAST PATIENT CONVERTED (IV) 30;2 59.7,31 DAYS TO RETAIN IV STATISTICS 31;1 59.7,32 IV IDENTIFIER 31;2 59.7,34 EXPIRED IV TIME LIMIT 31;4 59.7,60.02 LAST PAT CONVERTED FOR VER 4 60;2 59.7,61.2 DAYS NEW LABELS LAST 61;2 59.7,63.51 PICK LIST AUTO-PURGE 63.5;1 59.7,63.52 DATE/TIME AUTO-PURGE EDITED 63.5;2 59.7,63.53 USER LAST EDITING AUTO-PURGE 63.5;3 59.7,63.54 DATE PICK LIST LAST FILED AWAY 63.5;4 59.7,64 PARAM FILE CONVERSION STATUS 20.4;12 59.7,65 PICK LIST CONVERSION DATE 20.4;13 59.7,66 V4.5 PICK LIST CONVERT MARKER 20.4;14 59.7,67 V4.5 PICK LIST CONVERT STATUS 20.4;15 59.7,80 PSS VERSION 80;1 59.7,81 ORDERABLE ITEM STATUS TRACKER 80;2 59.7,103 DURATION OVERRIDE HANDLING 62;1 59.7,104 DURATION OVERRIDE MESSAGE 62;2 Use of input template PSJ OAOPT is also requested. GLOBAL MAP DATA DICTIONARY #59.7 -- PHARMACY SYSTEM FILE 10/17/97 STORED IN ^PS(59.7, (1 ENTRY) SITE: SALT LAKE ISC UCI: OEX,OER -------------------------------------------------------------------------- This file contains data that pertains to the entire Pharmacy system of a medical center, and not to any one site or division. The number ranges for the nodes and field numbers are as follows: 0 - 9.99 RESERVED 10 - 19.99 National Drug File 20 - 29.99 Inpatient 30 - 39.99 IV's 40 - 49.99 Outpatient 50 - 59.99 Ward Stock/AR 60 - 69.99 Unit Dose 70 - 79.99 Drug Accountability 80 - 89.99 Pharmacy Data Management |
2023/08/17 | ||
| 2191 | DBIA2191 | File | PHARMACY DATA MANAGEMENT | 1997/10/21 | APPROVED | Active | Private | 55 | This file is used extensively throughout our routines. We request read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. The fields we use are listed below. The UNIT DOSE multiple and IV multiple represent the majority of the fields in the file. Because they are so numerous, we would like full access to the file. |
|||
| 2192 | DBIA2192 | File | PHARMACY DATA MANAGEMENT | 1997/10/21 | APPROVED | Active | Private | 50 | This file was previously under Outpatient Pharmacy. Now, Pharmacy Data Management 1.0 sends it out. This file is used extensively throughout our routines. We use a majority of the fields in this file. We request read and write access to the entire file, cross-references and templates via FileMan utilities and direct writes/reads. |
|||
| 2222 | DBIA2222 | File | PHARMACY DATA MANAGEMENT | 1997/11/03 | Retired | Private | 50.606 | The Outpatient Pharmacy package request permission to look at DOSAGE FORM file 50.606. This file was previously in National Drug File, but now it has been moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. Therefore, we are requesting read/write access to the entire file and cross-references through Fileman and direct reads/write. |
||||
| 2223 | DBIA2223 | File | PHARMACY DATA MANAGEMENT | 1997/11/03 | APPROVED | Active | Private | 50.7 | The Outpatient Pharmacy package request permission to look at PHARMACY ORDERABLE ITEM file 50.7. This is a new file of Pharmacy Data Management 1.0. It is used extensively throughout our routines. We are requesting read/write access to the entire file and cross-references through direct reads/writes and VA Fileman utilities. |
|||
| 2224 | DBIA2224 | File | PHARMACY DATA MANAGEMENT | 1997/11/03 | APPROVED | Active | Private | 51 | The Outpatient Pharmacy package request permission to look at MEDICATION INSTRUCTION file 51. |
|||
| 2225 | DBIA2225 | File | PHARMACY DATA MANAGEMENT | 1997/11/03 | APPROVED | Active | Private | 51.1 | The Outpatient Pharmacy package request permission to look at ADMINISTRATION SCHEDULE file 51.1. We use the 'B' cross reference to $Order through the file to get the expansion of the Administration Schedule for the prescription. |
|||
| 2226 | DBIA2226 | File | PHARMACY DATA MANAGEMENT | 1997/11/03 | APPROVED | Active | Private | 51.2 | The Outpatient Pharmacy package request permission to look at MEDICATION ROUTES file 51.2. |
|||
| 2227 | DBIA2227 | File | PHARMACY DATA MANAGEMENT | 1997/11/04 | APPROVED | Active | Controlled Subscription | 54 | This Outpatient Pharmacy package request permission to look at RX CONSULT file 54. |
|||
| 2228 | DBIA2228 | File | PHARMACY DATA MANAGEMENT | 2005/11/14 | APPROVED | Active | Controlled Subscription | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. The Outpatient Pharmacy and CMOP packages request full access to PHARMACY PATIENT file 55. This file is used extensively throughout our routines. Therefore, we request read and write access to the entire file and cross references through Fileman utilities and direct reads/writes. |
|||
| 2254 | DBIA-2254 | File | PHARMACY DATA MANAGEMENT | 1997/12/09 | Retired | Private | 50.5 | Outpatient Pharmacy package request permission to look at DRUG CLASSIFICATION file 50.5 via direct global read and Fileman. |
||||
| 2352 | READ/WRITE DRUG FILE (#50) | File | PHARMACY DATA MANAGEMENT | 1999/10/15 | Retired | Private | 50 |
National Drug File is given permission by Pharmacy Data Management to make the following references with direct global reads and writes to the fields and direct global references to the fields' cross-references. 1. (#2) VA CLASSIFICATION $P(^PSDRUG(D0,0),"^",2) 2. (#2.1) PHARMACY ORDERABLE ITEM $P(^PSDRUG(D0,1),"^",2) 3. (#213) CMOP DISPENSE $P(^PSDRUG(D0,3),"^",1) 4. (#51) LOCAL NON-FORMULARY $P(^PSDRUG(D0,0),"^",9) 5. (#52) VISN NON-FORMULARY $P(^PSDRUG(D0,0),"^",11) 6. (#37) DRUG TEXT ENTRY (multiple) $P(^PSDRUG(D0,9,D1,0),"^") 7. All fields contained on the "ND" Node ^PSDRUG(D0,"ND")= (#20) NATIONAL DRUG FILE ENTRY [1P] ^ (#21) VA PRODUCT ==>NAME [2F] ^ (#22) PSNDF VA PRODUCT NAME ENTRY [3N] ^ (#23) ==>PACKAGE SIZE [4P] ^ (#24) PACKAGE TYPE (#25) NATIONAL DRUG ==>CLASS [6P] ^ ^ ^ ^ (#27) CMOP ID [10F] ^ (#29) NATIONAL ==>FORMULARY INDICATOR [11S] ^ 8. ^PSDRUG(D0,"OND") This global node was eliminated by previous versions of the software. NDF V3.18 is the last version that will include the cleanup routine containing code to delete this node if it exists. 9. Hard Coded sets and kills to the following cross references; ^PSDRUG("AND") ^PSDRUG("APC") ^PSDRUG("AQ") ^PSDRUG ("AQ1") ^PSDRUG("NDC") ^PSDRUG("VAC") ^PSDRUG("VAPN") ^PSDRUG("APN") |
||||
| 2367 | DBIA2367 | File | PHARMACY DATA MANAGEMENT | 1998/04/28 | Retired | Private | 50 | Consolidated Mail Outpatient Pharmacy is given permission by Pharmacy Data Management to make the following references to ^PSDRUG. 1. (#213) CMOP DISPENSE $P(^PSDRUG(D0,3),"^",1) 2. All fields contained on the "ND" node - Global Read Access only ^PSDRUG(D0,"ND")= (#20) NATIONAL DRUG FILE ENTRY [1P] ^ (#21) VA PRODUCT ==>NAME [2F] ^ (#22) PSNDF VA PRODUCT NAME ENTRY [3N] ^ (#23) ==>PACKAGE SIZE [4P] ^ (#24) PACKAGE TYPE (#25) NATIONAL DRUG ==>CLASS [6P] ^ ^ ^ ^ (#27) CMOP ID [10F] ^ 3. Hard coded sets and kills to the following cross references: ^PSDRUG("AQ") ^PSDRUG("AQ1") 4. (#2.1) PHARMACY ORDERABLE ITEM $P(^PSDRUG(D0,1),"^",2) |
||||
| 2381 | OE/RR REFERENCES TO PS(51.2, | File | PHARMACY DATA MANAGEMENT | 1998/05/06 | APPROVED | Active | Controlled Subscription | 51.2 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. The Order Entry/Results Reporting package requests permission to access the NAME and ABBREVIATION fields in the MEDICATION ROUTES file (#51.2). |
|||
| 2392 | OE/RR ACCESS TO PS(51.1, | File | PHARMACY DATA MANAGEMENT | 1998/05/10 | APPROVED | Active | Private | 51.1 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. Order Entry/Results Reporting requests permission to access the following fields and cross-reference in the Administration Schedule file (#51.1). |
|||
| 2396 | OE/RR USAGE OF PS(55, | File | PHARMACY DATA MANAGEMENT | 1998/05/10 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Order Entry/Results Reporting requests global read access to the Pharmacy Patient file (#55) for the fields listed below. |
||||
| 2405 | OE/RR CALLS TO PSSHL1 | Routine | PHARMACY DATA MANAGEMENT | 1998/05/10 | APPROVED | Active | Private | Order Entry/Results Reporting wishes to document the call to EN1^PSSHL1 which is used to populate pharmacy orderables into the OE/RR ORDERABLE ITEM file. |
PSSHL1 | |||
| 2415 | PS EVSEND OR | Other | PHARMACY DATA MANAGEMENT | 1998/05/15 | APPROVED | Active | Controlled Subscription | The PS EVSEND OR protocol is used to pass order messages from Pharmacy packages to other packages. This protocol is exported by the Pharmacy Data Management package, and is invoked by other Pharmacy Packages. |
||||
| 2416 | PS EVSEND OR | Other | PHARMACY DATA MANAGEMENT | 1998/05/15 | Retired | Controlled Subscription | This agreement will allow certain packages to attach protocols as Items under the PS EVSEND OR protocol, which is an Extended Action protocol used to pass Pharmacy order information from Pharmacy packages to other packages in the form of an array. |
|||||
| 2418 | OE/RR CALL TO PSSJORDF | Routine | PHARMACY DATA MANAGEMENT | 1998/05/20 | APPROVED | Active | Controlled Subscription | This DBIA allows use of START^PSSJORDF and START1^PSSJORDF as documented in the OE/RR Developer Interface Specification. |
PSSJORDF | 2011/05/10 | ||
| 2423 | Inpatient Medications Quick Order Conversion | Routine | PHARMACY DATA MANAGEMENT | 1998/05/21 | APPROVED | Active | Private | Used by OR*2.5*49 to convert existing Inpatient Medication Quick Orders for use with CPRS v1.0. |
PSSQOC | |||
| 2441 | Obtain data from the Drug (50) file. | File | PHARMACY DATA MANAGEMENT | 1998/06/29 | APPROVED | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. Radiology/Nuclear Medicine obtains the following data from Pharmacy Data Management's (PDM) Drug file: field name field number node;piece purpose -------------------------------------------------------------------------- Generic Name .01 0;1 display Generic Name VA Classification 2 0;2 radiopharmaceutical check Inactive Date 100 I;1 check if an active drug |
|||
| 2470 | DBIA2470 | File | PHARMACY DATA MANAGEMENT | 1998/07/07 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. CIRN needs read access to ^PS(55 to calculate the Master of Record score. |
||||
| 2474 | DBIA2474 | File | PHARMACY DATA MANAGEMENT | 1998/07/09 | APPROVED | Active | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. |
|||
| 2475 | DBIA2475 | File | PHARMACY DATA MANAGEMENT | 1998/07/09 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. |
||||
| 2494 | DBIA-2494 PDM-Delete bad field global | File | PHARMACY DATA MANAGEMENT | 1998/08/11 | APPROVED | Active | Supported | 50 | To resolve NOIS # EKH-0798-41058, we are inserting a line of code to delete the impartial field data found in File #50. We believe that the ^DD(50,0,"ID",534016) global is a local site-specific field. We do not have a zero node that identifies the field name. We are adding a line of code to routine PSSPCH13 that checks for the zero node. If not there, it will delete the data related to the field number 534016. Example. I '$D(^DD(50,534016)) K ^DD(50,0,"ID",534016). This change is included in patch PSS*1*13. |
|||
| 2497 | DBIA2497 | File | PHARMACY DATA MANAGEMENT | 1998/08/12 | APPROVED | Active | Controlled Subscription | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Pharmacy Benefits Management extracts data from the following Pharmacy Patient File #55 fields. |
|||
| 2514 | ACCESS TO DRUG INGREDIENTS FILE (#50.606) | File | PHARMACY DATA MANAGEMENT | 1998/08/24 | APPROVED | Active | Private | 50.606 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. National Drug File has need to do a direct global read to the zero node of file 50.606. |
|||
| 2612 | DBIA2612 | File | PHARMACY DATA MANAGEMENT | 1998/10/18 | APPROVED | Active | Private | 50.3 | As of 9/1/20 the ICR Team were requested to change the custodial package to Pharmacy Data Management, instead of Inpatient Medications. This resulted from the alignment of file ranges under specific packages for the conversions from Rational to GitHub. Actual Description from prior to 9/1/20: National Drug File (NDF) request permission to look at the PRIMARY DRUG file (#50.3). Direct Global Read. Field Name Node & Piece .01 NAME 0;1 |
2020/09/01 | ||
| 2613 | DBIA2613 | File | PHARMACY DATA MANAGEMENT | 1998/10/18 | APPROVED | Active | Private | 59.7 | National Drug File (NDF) requests to look at the PHARMACY SYSTEM file (59.7). Direct Global R/W. |
2010/10/04 | ||
| 2614 | DBIA2614 | Other | PHARMACY DATA MANAGEMENT | 1998/10/18 | APPROVED | Active | Private | National Drug File (NDF) requests permission to export templates to DRUG file (#50). Print Templates --------------- PSNFRMPRT PSNHEAD PSNLDG1 PSNRPT2 PSNRPT4 Sort Templates -------------- PSNFRMSRT |
||||
| 2629 | EXPANSION FIELD FOR CIRN | File | PHARMACY DATA MANAGEMENT | 1998/11/09 | APPROVED | Active | Private | 51 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. TO GENERATE HL7 PRESCRIPTION MESSAGING. |
|||
| 2654 | CIRN access to PSDRUG file | File | PHARMACY DATA MANAGEMENT | 1998/11/30 | APPROVED | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. CIRN needs a read access to the PSDRUG (file #50) to generate HL7 prescription messaging |
|||
| 2682 | OE/RR references to PS(59.7, | File | PHARMACY DATA MANAGEMENT | 1998/12/30 | Retired | Private | 59.7 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. OR*2.5*49 performs a check to ensure pharmacy data management matching is complete prior to letting OR*2.5*49 be installed. |
||||
| 2789 | DBIA2789 | Routine | PHARMACY DATA MANAGEMENT | 1999/03/25 | APPROVED | Active | Controlled Subscription | This is the common lock routine for patient locks in Inpatient Medications and Outpatient pharmacy. It also contains the entry points for single order locks between Inpatient/Outpatient and Computerized Patient Record System (CPRS). |
PSSLOCK | |||
| 2841 | TIU MEDICATION OBJECTS READ DRUG FILE | File | PHARMACY DATA MANAGEMENT | 1999/09/15 | APPROVED | Retired | Private | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. TIU's medication objects now allow for the sorting of medications by drug class, including pending orders for medications that may not yet have a dispense drug. They also allow for the exclusion of supply items from medication lists, if desired. To accomodate this functionality, TIU requests direct global read access to the following pharmacy file: ^PSDRUG( - DRUG FILE (#50): "B" cross reference "ASP" cross reference Node 0, piece 2 - VA CLASSIFICATION FIELD (#2). Node 0, piece 3 - DEA, SPECIAL HDLG FIELD (#3) |
|||
| 2854 | DBIA2854 | File | PHARMACY DATA MANAGEMENT | 1999/06/24 | APPROVED | Active | Private | 59.7 | Pharmacy Benefits Managment requests the usage of the PSU PBM JOB field (#90) in the PHARMACY SYSTEM file (#59.7) for monitoring the status of current and previous extracts of the PSU PBM software. |
|||
| 2858 | DBIA2858 | File | PHARMACY DATA MANAGEMENT | 2000/02/17 | APPROVED | Active | Controlled Subscription | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. |
|||
| 2879 | DBIA2879 | File | PHARMACY DATA MANAGEMENT | 1999/07/28 | APPROVED | Active | Private | 51.1 | ||||
| 2880 | DBIA2880 | File | PHARMACY DATA MANAGEMENT | 1999/07/28 | APPROVED | Active | Private | 50.7 | ||||
| 2908 | TIU MEDICATION OBJECTS READ PHARMACY FILE | File | PHARMACY DATA MANAGEMENT | 1999/09/15 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. TIU's medication objects now allow for the sorting of medications by drug class, including pending orders for medications that may not yet have a dispense drug. They also allow for the exclusion of supply items from medication lists, if desired. To accomodate this functionality, TIU requests direct global read access to the following pharmacy file: ^PS(55, - PHARMACY PATIENT FILE (#55) ^PS(55,DFN,5, - UNIT DOSE SUB-FILE (#55.06) Node .2, piece 1 - ORDERABLE ITEM FIELD (#108) ^PS(55,DFN,5,DA,1 - DISPENSE DRUG SUB-FILE (#55.07) Node 0, Piece 1 - DISPENSE DRUG FIELD (#.01) ^PS(55,DFN,"IV", - IV SUB-FILE (#55.01) Node .2, piece 1 - ORDERABLE ITEM FIELD (#130) ^PS(55,DFN,"IV",DA,"AD", - ADDITIVE SUB-FILE (#55.02) Node 0, piece 1 - ADDITIVE FIELD (#.01) |
||||
| 2909 | TIU MEDICATION OBJECTS READ PHARMACY FILE | File | PHARMACY DATA MANAGEMENT | 1999/09/15 | APPROVED | Retired | Private | 52.6 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. TIU's medication objects now allow for the sorting of medications by drug class, including pending orders for medications that may not yet have a dispense drug. They also allow for the exclusion of supply items from medication lists, if desired. To accomodate this functionality, TIU requests direct global read access to the following pharmacy file: ^PS(52.6, - IV ADDITIVES FILE (#52.6) Node 0, piece 2 - GENERIC DRUG FIELD (#1) |
|||
| 2935 | DRUG TEXT file | File | PHARMACY DATA MANAGEMENT | 2000/02/08 | APPROVED | Active | Private | 51.7 | National Drug File (NDF) requests permission to do direct global reads on the Pharmacy Data Management's DRUG TEXT file (#51.7). This file stores rapidly changing drug restrictions, guidelines, and protocols to help assure medications are being used according to formulary specifications. |
|||
| 2946 | Calls to PSSGSGUI | Routine | PHARMACY DATA MANAGEMENT | 1999/10/29 | APPROVED | Active | Controlled Subscription | This call provides a Schedule validation check for medication orders entered through Computerized Patient Record System (CPRS). |
PSSGSGUI | |||
| 3013 | DBIA3013 | File | PHARMACY DATA MANAGEMENT | 1999/12/21 | APPROVED | Active | Private | 52.7 | Controlled Substances is given permission to reference the fields identified in this integration agreement. The refernces are made using the VA Fileman API ^DIC. GLOBAL MAP DATA DICTIONARY #52.7 -- IV SOLUTIONS FILE STORED IN ^PS(52.7, (3 ENTRIES) SITE: BIRMINGHAM ISC (#14) ^PS(52.7,D0,0)= (#.01) PRINT NAME [1F] Read w/Fileman ^PS(52.7,D0,0)= (#2) VOLUME [3F] Read w/Fileman |
|||
| 3034 | DRUG ACCOUNTABILITY | File | PHARMACY DATA MANAGEMENT | 2000/02/04 | Withdrawn | Private | 59.7 |
When the Drug Acountability package is trying to link the Drug/Item file, the last drug linked is stored in the LAST DRUG LINKED (#70) field. This field is also used as a point at which to resume the loop upon re-entry. |
||||
| 3077 | Direct global access to the DRUG file (#50) | File | PHARMACY DATA MANAGEMENT | 2000/04/11 | Retired | Private | 50 | Pharmacy Data Management has defined certain data change events within National Drug File that should delete certain fields in the DRUG file (#50). To meet that request, National Drug File requests permission to do direct global KILLs to nodes ^PSDRUG(D0,"DOS"), ^PSDRUG(D0,"DOS1"), and ^PSDRUG(D0,"DOS2"). |
||||
| 3107 | DBIA3107 | Routine | PHARMACY DATA MANAGEMENT | 2000/05/08 | APPROVED | Active | Private | National Drug File requests permission to call entry points in the Pharmacy Data Management package to perform updates related to matching, re-matching and un-matching Dispense Drugs in the DRUG file (#50) to and from NDF VA Products in the VA PRODUCT file (#50.68). Note: These entry points should only be used for approved drug matching, re-matching and un-matching functions. |
PSSUTIL | |||
| 3136 | Health Summary Component Outpat Pharm (RXOP) | File | PHARMACY DATA MANAGEMENT | 2000/06/28 | Retired | Private | 59.7 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Health Summary needs to access the parameters of the Pharmacy System to determine the appropriate displays for Outpatient Pharmacy components. |
||||
| 3165 | DRUG FILE ACTIVITY LOG ADD/EDIT BY OUTPATIENT PHARMACY | File | PHARMACY DATA MANAGEMENT | 2000/08/14 | APPROVED | Active | Private | 50 | CMOP functionality in the Outpatient Pharmacy application has a need to enter comments into the ACTIVITY LOG field (# 214) multiple of the Drug file (# 50). This functionality also reads and sets the CMOP DISPENSE field (# 215) and its index "^PSDRUG("AQ"," within the Drug file (# 50). The node ^PSDRUG(D0,4,D1) is looped through to find the last entry in the Activity Log multiple prior to inserting a new comment. If the header node for the Activity Log field multiple is not present a header node is inserted into the database. |
|||
| 3166 | CALL FOR PSSDIN - NFI TEXT AVAIL. FOR ORD.ITEM/DISP.DRUG | Routine | PHARMACY DATA MANAGEMENT | 2000/08/15 | APPROVED | Active | Controlled Subscription | Outpatient Pharmacy, Inpatient Medications and Computerized Patient Record System all request permission to call the function provided by the Pharmacy Data Management package - routine name ^PSSDIN. This call builds the temporary global ^TMP("PSSDIN" with the National Formulary Indicator text for both orderable items and dispense drugs that are marked as restricted items. Sending input of either orderable items or dispense drugs is optional and the routine will only return text where it receives either or both variables. The text may be displayed upon request. |
PSSDIN | |||
| 3179 | 3179 | Routine | PHARMACY DATA MANAGEMENT | 2000/08/30 | APPROVED | Active | Private | This API provides Inpatient Medications and Outpatient Pharmacy a means of getting the strength and unit for a specified drug from the DRUG file (#50). |
PSSUTIL1 | |||
| 3229 | DBIA3229 | Routine | PHARMACY DATA MANAGEMENT | 2000/10/24 | Withdrawn | Private | If the APPLICATION PACKAGES' USE field (#63) in DRUG file (#50) for at least one of the dispense drugs associated with the orderable item is marked for IV use and at least one of the IV additives/IV solutions associated with the dispense drug are flagged for IV FLUID ORDER ENTRY, this field shall be optional. If not, a value in the schedule field shall be mandatory. CPRS shall be passed this information from Pharmacy Data Management to make this determination. |
PSSCPRS | ||||
| 3233 | DBIA3233 | Routine | PHARMACY DATA MANAGEMENT | 2000/10/27 | APPROVED | Active | Controlled Subscription | With the implementation of the Pharmacy Ordering Enhancements project, Dosages will now be stored in the DRUG file (#50), in the form of Possible Dosages and Local Possible Dosages. When a medication (Orderable Item) is selected in CPRS (Computerized Patient Record System) in the medication order entry process, that Orderable Item will be passed to the Pharmacy Data Management package, along with the Pharmacy application and patient internal entry number. The Pharmacy Data Management package will pass back to CPRS Dosage information from the Drugs in the DRUG file (#50) that are matched to that Orderable Item. |
PSSORUTL | 2015/12/15 | ||
| 3234 | DBIA3234 | Routine | PHARMACY DATA MANAGEMENT | 2000/10/30 | APPROVED | Active | Controlled Subscription | With the implementation of the Pharmacy Ordering Enhancements project, Dosages will now be stored in the DRUG file (#50), in the form of Possible Dosages and Local Possible Dosages. When a Dispense Drug is selected during the medication order entry process in the Outpatient Pharmacy and Inpatient Medications applications, that drug will be passed to the Pharmacy Data Management application, along with the Pharmacy application and Patient. Pharmacy Data Management will pass back the available Dosages from the DRUG file (#50) and other related information. |
PSSORPH | 2015/09/02 | ||
| 3239 | DBIA3239 | Routine | PHARMACY DATA MANAGEMENT | 2000/10/31 | APPROVED | Active | Private | This agreement allows Computerized Patient Record System (CPRS) to pass into Pharmacy Data Management a Pharmacy Orderable Item, and the Pharmacy application for which a medication order is being entered in CPRS. In return, Pharmacy Data Management will return an array of active Dispense Drugs for that Pharmacy application that are tied to the Pharmacy Orderable Item. This call will be used by CPRS so order checks can be performed on all Dispense Drugs tied to an Orderable Item, when a Dispense Drug cannot be associated with a medication order in CPRS. |
PSSUTIL1 | 2015/10/26 | ||
| 3271 | Direct writes to the DRUG file (#50) | File | PHARMACY DATA MANAGEMENT | 2000/12/19 | Retired | Private | 50 | National Drug File requests approval to directly write to the ACTIVITY LOG multiple field (#4) in the DRUG file (#50). |
||||
| 3373 | PSSUTLA1 | Routine | PHARMACY DATA MANAGEMENT | 2001/05/10 | APPROVED | Active | Controlled Subscription | Pharmacy Data Management returns a DEA Special Handling code for a Pharmacy Orderable Item, based on the Dispense Drugs that are matched to that Pharmacy Orderable Item. Pharmacy Data Management also returns the Computerized Patient Record System (CPRS) Order Number when a Pharmacy Order Number is passed into the PLACER component. Pharmacy Data Management also returns the most appropriate Order Location when a Pharmacy Order Number is passed into the LOC component. |
PSSUTLA1 | 2019/10/02 | ||
| 3423 | DBIA3423 | Routine | PHARMACY DATA MANAGEMENT | 2001/07/25 | APPROVED | Active | Private | This call provides a Schedule validation check for medication orders entered through Computerized Patient Record System (CPRS). |
PSSGS0 | |||
| 3424 | DBIA3424 | Routine | PHARMACY DATA MANAGEMENT | 2001/07/25 | APPROVED | Active | Private | When phase 2 of the Pharmacy Ordering Enhancements project is installed, a rematching process will occur at the time of install, where IV Additives and IV Solutions will be matched to new Pharmacy Orderable Items. Pharmacy needs to provide this new information to CPRS, so CPRS can update as many of their Quick Orders as possible. The old pointer values will be stored in an XTMP global for 30 days to assist in this process. |
PSSQORD | |||
| 3502 | PHARMACY DATA MANAGEMENT | File | PHARMACY DATA MANAGEMENT | 2002/01/24 | APPROVED | Active | Private | 55 | ||||
| 3621 | Data updates | Routine | PHARMACY DATA MANAGEMENT | 2002/07/17 | APPROVED | Active | Controlled Subscription | In support of the Hawaii DoD project, Pharmacy Data Management needs to know when changes are made to entries in the DRUG file (#50). National Drug File data updates make changes to entries in this file. To meet this need, NDF requests permission to call routine PSSHUIDG at entry point PSN. The array ^TMP($J,"^",IEN where IEN is the internal entry number in the DRUG file (#50) wil be sent to this entry point. The matching and unmatching processes also make changes to the drug file that need to be sent to PDM. To this end, NDF requests permission to call routine PSSHUIDG at entry point DRG with the variable PSNB (if an entry is being matched) or DA (if an entry is being unmatched) representing the internal entry number in the drug file. |
PSSHUIDG | |||
| 3737 | PSSOPKI | Routine | PHARMACY DATA MANAGEMENT | 2002/08/29 | APPROVED | Active | Controlled Subscription | Pharmacy Data Management returns the most restrictive CS FEDERAL SCHEDULE code / DEA SPECIAL HDLG code for a Pharmacy Orderable Item, based on the Dispense Drugs that are associated with that Pharmacy Orderable Item. The CS FEDERAL SCHEDULE code / DEA SPECIAL HDLG code is derived as follows: If any of the active dispense drugs associated with the orderable item for the specified package are matched to an entry in the National Drug File, then the most restrictive CS FEDERAL SCHEDULE code from the National Drug File will be returned. If there is no match or the CS FEDERAL SCHEDULE code is undefined then the most restrictive DEA SPECIAL HDLG code mapped to the corresponding CS FEDERAL SCHEDULE code as listed below will be returned. DEA, SPECIAL HDLG CS FEDERAL SCHEDULE 1 1 (Schedule I narcotics) 2A 2 (Schedule II narcotics) 2C 2n (Schedule II non-narcotics) 3A 3 (Schedule III narcotics) 3C 3n (Schedule III non-narcotics) 4 4 (Schedule IV narcotics) 5 5 (Schedule V narcotics) |
PSSOPKI | 2011/12/07 | ||
| 3739 | PSSOPKI1 | Routine | PHARMACY DATA MANAGEMENT | 2002/08/29 | APPROVED | Active | Controlled Subscription | When a medication (Orderable Item) is selected in Computerized Patient Record System (CPRS) in the medication order entry process, that Orderable Item will be passed to the Pharmacy Data Management package (PDM), along with the Pharmacy application and patient internal entry number. The PDM will pass back to CPRS, Dosage information from the Drugs in the DRUG file (#50) that are associated to that Orderable Item. |
PSSOPKI1 | 2015/12/15 | ||
| 3784 | DEA SPECIAL HANDLING CODE | Routine | PHARMACY DATA MANAGEMENT | 2002/10/15 | APPROVED | Active | Private | Pharmacy Data Management will return a DEA Special Handling code to Computerized Patient Record System (CPRS) for an Orderable Item, when selected through the CPRS IV Fluids order dialogue, for an outpatient. This DEA code will be based on the Dispense Drugs matched to that Orderable Item. If the second parameter in this call is an "A" for Additive, then a DEA Special Handling code will only be evaluated for a Dispense Drug if that Dispense Drug has at least one active IV Additive matched to the Dispense Drug. If the second parameter is an "S" for Solution, then a DEA Special Handling code will only be evaluated for a Dispense Drug if that Dispense Drug has at least one active IV Solution matched to the Dispense Drug. |
PSSUTIL1 | |||
| 3785 | PXRM DIRECT READ OF PHARMACY PATIENT FILE | File | PHARMACY DATA MANAGEMENT | 2002/10/15 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Clinical Reminders requests the ability to do a global read on the Patient File #55 specifically, ^PS(55, using multiple fields from the Unit Dose multiple, and the IV multiple to populate the new Clinical Reminders Index. |
PXRMSXRD | |||
| 3786 | PXRM RETRIEVE THE DRUG VALUE FROM FILE 52.6 | File | PHARMACY DATA MANAGEMENT | 2002/10/15 | APPROVED | Active | Private | 52.6 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. Clinical Reminders request the ability to populate the new Clinical Reminders Index with the IEN of the Drug file found in the IV ADDITIVES File, file 52.6 (piece two of the zero node). |
PXRMSXRD | ||
| 4025 | GMTS reference to 55 | File | PHARMACY DATA MANAGEMENT | 2003/03/18 | Withdrawn | Private | 55 | |||||
| 4098 | PSSPOIDT | Routine | PHARMACY DATA MANAGEMENT | 2003/05/19 | APPROVED | Active | Private | Allow CPRS to use EN1^PSSPOIDT during the post-installation of patch OR*3*176. EN1^PSSPOIDT will update CPRS files to be in synch with Pharmacy files for the Herbal/OTC/Non-VA Meds project. |
PSSPOIDT | |||
| 4099 | PHARMACY ORDERABLE ITEM FILE | File | PHARMACY DATA MANAGEMENT | 2003/05/05 | Pending | Private | 50.7 | Allow CPRS to use the Pharmacy Orderable Item file [^PS(50.7] during the post-installation of patch OR*3*176. OR*3*176 post-init routine ORY176 loops through ^PS(50.7 for each call into EN1^PSSPOIDT to synch CPRS files with Pharmacy files for the Herbal/OTC/Non-VA Meds project. |
||||
| 4172 | BUILD CLINICAL REMINDERS INDEX | Routine | PHARMACY DATA MANAGEMENT | 2003/08/01 | APPROVED | Active | Private | This integration agreement grants Clinical Reminders the access to call a routine in Pharmacy Data Management to build an index for the PHARMACY PATIENT file (#55). |
PSSSXRD | |||
| 4181 | DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS | File | PHARMACY DATA MANAGEMENT | 2004/06/29 | Retired | Private | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. The following global references are made: Global Nodes PS(55) $O(^PS(55,DFN)) $O(^PS(55,DFN,5,DA) $P(^PS(55,DFN,5,DA,2),U,M) M=2,4 $O(^PS(55,DFN,5,DA,1,DA1)) $P(^PS(55,DFN,5,DA,1,DA1,0),U,1) $O(^PS(55,DFN, IV ,DA)) $P(^PS(55,DFN, IV ,DA,0),U,M) M=2,3 $O(^PS(55,DFN, IV ,DA, AD ,DA1)) ADD=$P(^PS(55,DFN, IV ,DA, AD ,DA1,0),U,1) $P(^PS(52.6,ADD,0),U,2) $O(^PS(55,DFN, IV ,DA, SOL ,DA1)) SOL=$P(^PS(55,DFN, IV ,DA, SOL ,DA1,0),U,1) $P(^PS(52.7,SOL,0),U,2) |
||||
| 4237 | DBIA4237 | Routine | PHARMACY DATA MANAGEMENT | 2003/09/22 | APPROVED | Active | Supported | This supported reference is available to allow users to pass in a patient's internal file number (dfn) in the form of a function call to indicate if that patient has at least one active prescription. S X=$$EN^PSSRXACT(DFN). 1 is returned if the patient has at least one active Rx, else 0 (zero) is returned indicating no active prescriptions. |
PSSRXACT | |||
| 4394 | Data updates | Routine | PHARMACY DATA MANAGEMENT | 2004/04/07 | APPROVED | Active | Controlled Subscription | In support of the Outpatient Pharmacy Automation Dispense project, Pharmacy Data Management needs to know when changes are made to entries in the DRUG file (#50). National Drug File data updates make changes to entries in this file. To meet this need, NDF requests permission to call routine PSSDGUPD at entry point PSN. The array ^TMP($J,"^",IEN where IEN is the internal entry number in the DRUG file (#50) wil be sent to this entry point. The matching and unmatching processes also make changes to the drug file that need to be sent to PDM. To this end, NDF requests permission to call routine PSSHUIDG at entry point DRG with the variable PSNB (if an entry is being matched) or DA (if an entry is being unmatched) representing the internal entry number in the drug file. |
PSSDGUPD | |||
| 4444 | DRUG WARNING TEXT | Routine | PHARMACY DATA MANAGEMENT | 2004/07/02 | APPROVED | Active | Controlled Subscription | The purpose of this call is to return the freetext warning label text for a given warning number. |
PSSWRNA | |||
| 4449 | WARNING LABEL LIST | Routine | PHARMACY DATA MANAGEMENT | 2004/07/06 | APPROVED | Active | Controlled Subscription | This call will return the warning label list associated with a drug. The list will consist of numbers or numbers followed by the letter "N", separated by commas. Entries without the "N" are from the old RX CONSULT file (#54) and entries with the "N" are from the new commercial data source's WARNING LABEL-ENGLISH file (#50.625) or WARNING LABEL-SPANISH file (#50.626). |
PSSWRNA | |||
| 4480 | DBIA4480 | Routine | PHARMACY DATA MANAGEMENT | 2006/02/06 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the PHARMACY PATIENT file (#55). This API is to used in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS781 | |||
| 4483 | DBIA4483 | Routine | PHARMACY DATA MANAGEMENT | 2005/09/15 | Retired | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the DRUG file (#50). This API is to used in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS50 | ||||
| 4484 | READ OF STATUS FIELD FOR NON-VA MEDS | File | PHARMACY DATA MANAGEMENT | 2004/08/26 | Retired | Controlled Subscription | 55 | This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Clinical Reminders is requesting permission to do a FileMan read on the Non-VA meds status field. This read is to allow the user to define what the Non-VA meds status must for Clinical Reminders to consider the Non-VA meds finding item as true. Clinical Reminders will use the NVA^PSOPXRM1 API to retrieve the data related to a Non-VA med. This API is documented in DBIA #3793. |
||||
| 4533 | DBIA4533 | Routine | PHARMACY DATA MANAGEMENT | 2004/12/14 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the DRUG file (#50). This API is to used in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS50 | |||
| 4546 | ADMINISTRATION SCHEDULE | Routine | PHARMACY DATA MANAGEMENT | 2004/12/14 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the ADMINISTRATION SCHEDULE file (#51.1). This API must be used by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS51P1 | 2008/07/28 | ||
| 4548 | MEDICATION ROUTES APIs | Routine | PHARMACY DATA MANAGEMENT | 2004/12/14 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the MEDICATION ROUTES file (#51.2). This API is to used in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS51P2 | |||
| 4549 | DBIA4549 | Routine | PHARMACY DATA MANAGEMENT | 2004/12/14 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the IV ADDITIVES file (#52.6). This API is to used in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS52P6 | |||
| 4550 | DBIA4550 | Routine | PHARMACY DATA MANAGEMENT | 2004/12/14 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the IV SOLUTIONS file (#52.7). This API is to use in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS52P7 | 2017/11/29 | ||
| 4551 | DBIA4551 | Routine | PHARMACY DATA MANAGEMENT | 2004/12/14 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to do simulated VA FileMan calls. This API is to be used in the future by all packages needing to use FileMan to look at PDM files as all the Pharmacy packages are being re-engineered. |
PSSDI | |||
| 4555 | FIND STATUS OF PHARMACY ORDERS | Routine | PHARMACY DATA MANAGEMENT | 2006/03/15 | Other | Private | The purpose of this call is to provide the status of any Pharmacy order. The order could be Inpatient Medications, Outpatient Pharmacy or Non-VA Medications. Additionally, the $$DOSE API will be used to reformat dosages and units as described below. |
PSSORUTE | ||||
| 4662 | DBIA4662 | Routine | PHARMACY DATA MANAGEMENT | 2005/04/26 | APPROVED | Active | Supported | This API will return information from the PHARMACY ORDERABLE ITEM file (#50.7). |
PSS50P7 | 2019/05/22 | ||
| 4707 | PSSNDCUT | Routine | PHARMACY DATA MANAGEMENT | 2005/06/27 | APPROVED | Active | Controlled Subscription | This routine contains apis for retrieving and saving NDC in the DRUG file (#50). |
PSSNDCUT | |||
| 4708 | PSSDAWUT | Routine | PHARMACY DATA MANAGEMENT | 2005/06/27 | APPROVED | Active | Controlled Subscription | This routine contains apis related to DAW (Dispensed As Written) code for ePharmacy. |
PSSDAWUT | |||
| 4826 | DBIA4826 | Routine | PHARMACY DATA MANAGEMENT | 2005/11/15 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the PHARMACY PATIENT file (#55). This API is to used in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS55 | |||
| 4828 | DBIA4828 | Routine | PHARMACY DATA MANAGEMENT | 2005/11/15 | APPROVED | Active | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to the PHARMACY SYSTEM file (#59.7). This API is to used in the future by all packages accessing this file as all the Pharmacy packages are being re-engineered. |
PSS59P7 | |||
| 4846 | DBIA4846 | File | PHARMACY DATA MANAGEMENT | 2006/04/13 | APPROVED | Active | Supported | 50 | This DBIA allows for subscribing packages to store a pointer to the Vista DRUG (#50) file. This number can be used as an Identification Number to retrieve data. |
|||
| 4928 | DATA RETRIEVAL FROM FILE 55 | Routine | PHARMACY DATA MANAGEMENT | 2006/11/24 | APPROVED | Active | Supported | This DBIA is provided by Pharmacy Data Management (PSS) as an API to do data retrieval from File 55 using various methods. |
PSS55MIS | |||
| 4992 | PSSBPSUT | Routine | PHARMACY DATA MANAGEMENT | 2007/05/14 | APPROVED | Active | Controlled Subscription | This routine contains APIs used mainly by ePharmacy (Electronic Third Party Billing). |
PSSBPSUT | 2007/09/05 | ||
| 5165 | WDDE DISPENSING CABINET | File | PHARMACY DATA MANAGEMENT | 2008/04/02 | Withdrawn | Controlled Subscription | 59.72 | This ICR allows access to the automated dispensing cabinets defined in the AUTOMATED DISPENSING CABINET file. |
2009/02/02 | |||
| 5166 | WDDE DISPENSING SYSTEM | File | PHARMACY DATA MANAGEMENT | 2008/04/02 | Withdrawn | Controlled Subscription | 59.71 | This ICR allows access to the automated dispensing systems defined in the AUTOMATED DISPENSING SYSTEM file. |
2009/02/02 | |||
| 5183 | PHARMACY DATA MANAGEMENT | File | PHARMACY DATA MANAGEMENT | 2008/04/18 | Withdrawn | Private | 55 | The Ward Drug Dispensing Equipment (WDDE) project is requesting access to two fields and a cross-reference of the PHARMACY PATIENT file 55 that are not provided by current APIs. |
2009/02/02 | |||
| 5187 | CLINICAL REMINDERS API | Routine | PHARMACY DATA MANAGEMENT | 2008/04/24 | APPROVED | Active | Private | 50 | PSSCLINR | 2011/03/23 | ||
| 5369 | PHARMACY ENHANCED ORDER CHECKS FDB INTERFACE | Routine | PHARMACY DATA MANAGEMENT | 2009/02/13 | APPROVED | Active | Private | This API is used to request and get back order check results from a server using First DataBank's Drug Information Framework (DIF). This interface uses the Web Services to make the requests and get back results. |
PSSHRQ2 | 2014/10/28 | ||
| 5422 | WDDE WARD ASSIGNMENT | Routine | PHARMACY DATA MANAGEMENT | 2009/03/24 | Withdrawn | Private | This API checks if a ward is assigned to a specific ward drug dispensing equipment (WDDE). |
PSSWDLL | 2009/03/24 | |||
| 5425 | DBIA 5425 | Routine | PHARMACY DATA MANAGEMENT | 2009/04/07 | APPROVED | Active | Private | This DBIA provides various components that will be used for Pharmacy Re-engineering order checking functionality. |
PSSDSAPI | 2014/06/19 | ||
| 5426 | DBIA 5426 | Routine | PHARMACY DATA MANAGEMENT | 2009/04/07 | APPROVED | Active | Private | This DBIA is for the call to perform Dosing checks on Medication orders. For full Input and Output details, see the 'VistA to MOCHA Interface Document', located under the 'Pharm: Data Management (PDM)' section, under the 'Clinical' section of the VA Software Document Library (VDL). Last Updated: June/2018 Patch: PSS*1.0*224 Update: Changed one of the output subscripts for the Informational output message for the X(3) output. |
PSSDSAPD | 2024/10/28 | ||
| 5496 | PSSFDBRT | Routine | PHARMACY DATA MANAGEMENT | 2009/09/03 | APPROVED | Active | Private | This DBIA is provided by PDM (Pharmacy Data Management) as an API to return a list of possible Medication Routes from First DataBank (FDB) for a dispense drug. |
PSSFDBRT | 2014/06/20 | ||
| 5497 | DBIA 5497 | Routine | PHARMACY DATA MANAGEMENT | 2009/09/04 | APPROVED | Active | Controlled Subscription | This DBIA provides various components that will be used for Pharmacy Re-engineering order checking functionality. |
PSSDSAPK | 2023/10/30 | ||
| 5504 | DBIA 5504 | Routine | PHARMACY DATA MANAGEMENT | 2009/10/27 | Pending | Private | This DBIA provides a component that will be used for Pharmacy Re-engineering order checking functionality. |
PSSDSAPA | ||||
| 5570 | DBIA 5570 | Routine | PHARMACY DATA MANAGEMENT | 2010/09/14 | APPROVED | Active | Controlled Subscription | This entry point will return the best entry from the DRUG (#50) File to use for order checks (Drug Interaction, Duplicate Therapy and Dosing), when there is only a Pharmacy Orderable Item associated with the medication order. It will consider package, the match to National Drug File, and whether the matched entry in the VA PRODUCT (#50.68) File has a GCNSEQNO number. |
PSSDSAPM | 2015/06/11 | ||
| 5617 | PSSDSAPD Duration | Routine | PHARMACY DATA MANAGEMENT | 2011/03/21 | APPROVED | Active | Private | This DBIA returns the number of minutes to the calling application based on the duration passed in. |
PSSDSAPD | 2018/05/29 | ||
| 5737 | CHECK DRUG INTERACTIONS UTILITY | Routine | PHARMACY DATA MANAGEMENT | 2011/10/18 | APPROVED | Active | Controlled Subscription | This utility routine is called to determine what Drug Interactions exist for Inpatient and Outpatient Pharmacy. |
PSSDIUTL | 2014/10/24 | ||
| 5803 | PHARMACY PATIENT file information for data extract | File | PHARMACY DATA MANAGEMENT | 2012/05/25 | APPROVED | Active | Private | 55 | The decision support software (DSS) package had a need to obtain specific information related to UNIT DOSE orders. This information is in a multiple within the PHARMACY PATIENT file (#55). |
2012/07/03 | ||
| 5884 | INFUSION INSTRUCTIONS (#53.47) FILE | File | PHARMACY DATA MANAGEMENT | 2012/11/19 | APPROVED | Active | Private | 53.47 | Inpatient Medications requests read and write permission to the INFUSION INSTRUCTIONS (#53.47) file. This file is used to expand abbreviated free text entered in the INFUSION RATE (#.08) field in the IV multiple (#100) in the PHARMACY PATIENT (#55) file. |
2014/05/30 | ||
| 6229 | PSSUTIL1 | Routine | PHARMACY DATA MANAGEMENT | 2015/09/16 | APPROVED | Active | Private | This agreement allows the Outpatient Pharmacy application to invoke APIs in the PSSUTIL1 routine related to the dispensing of Outpatient Pharmacy prescriptions. |
PSSUTIL1 | 2015/10/26 | ||
| 6245 | RETURN EBILLABLE & SENSITIVE DIAGNOSIS DRUG FLDS | Routine | PHARMACY DATA MANAGEMENT | 2015/10/06 | APPROVED | Active | Controlled Subscription | This function returns the EPHARMACY BILLABLE, EPHARMACY BILLABLE (TRICARE), EPHARMACY BILLABLE (CHAMPVA) and SENSITIVE DIAGNOSIS DRUG fields from the DRUG File (#50) "EPH" node to subscribing packages. |
PSS50 | 2016/02/12 | ||
| 6369 | HMP ACCESS TO PS(51.2 | File | PHARMACY DATA MANAGEMENT | 2016/02/19 | APPROVED | Retired | Controlled Subscription | 51.2 | The Electronic Health MGMT Platform (HMP) is accessing the MEDICATION ROUTES File (#51.2) using direct global reads to collect data when syncing the HMP data domains during the intial sync for a patient. The sync process syncs data from the local VistA system with the HMP JDS database system. |
2016/04/20 | ||
| 6371 | ROUTINE PSSREF | Routine | PHARMACY DATA MANAGEMENT | 2016/02/24 | APPROVED | Active | Private | The National Drug File makes a call to routine ^PSSREF from routine ^PSNPPSNW to create an Activity Log entry in the DRUG file (#50). |
PSSREF | 2018/04/25 | ||
| 6395 | HMP READ ACCESS TO PS(55 | File | PHARMACY DATA MANAGEMENT | 2016/03/18 | APPROVED | Retired | Private | 55 |
The Enterprise Health MGMT Platform (HMP) request permission to do a Pharmacy Patient to retrieve the ORDERS FILE ENTRY (#110) on the IV Multiple and the ORDERS FILE ENTRY (#66) on the Unit Dose Multiple. HMP request temporary approval to do direct global reads rather than using FileMan or the existing APIs because of the need to get the data quickly so the process doesn't slow down the data retrieval and impact the user interface. HMP collects this data as part of the sync actions that syncs the patients medication data between the local VistA system and the eHMP JDS database. |
2016/03/23 | ||
| 6426 | HMP ACCESS TO ORDRNUM~PSSUTLA2 | Routine | PHARMACY DATA MANAGEMENT | 2016/07/06 | APPROVED | Retired | Controlled Subscription | The Enterprise Health MGMT Platform (HMP) calls the PSS API, ORDRNUM^PSSUTLA2 in order to retrieve the order number for a specific inpatient med order. ********************************************************************** This ICR was retired as of 10/27/17 when HMP was shut down. HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps for the sites to shut down the application. If HMP is reactivated in the future, the HMP project team should review the access provided by this ICR with the custodial application before the ICR is reactivated. See VistA Document Library (VDL) for list of retired HMP ICRs. ********************************************************************* |
PSSUTLA2 | 2017/10/13 | ||
| 6794 | IV SOLUTIONS FILE (#52.7) PREMIX FIELD (#18) FROM PSO | File | PHARMACY DATA MANAGEMENT | 2017/07/13 | APPROVED | Active | Private | 52.7 | VistA code decides which orders need to go through enhanced order checking in PSODDPR* routines, including IV Fluids. This ICR will allow the IV SOLUTION File (52.7), PREMIX field (18) to be checked from within PSO. GLOBAL REFERENCE: ^PS(52.7,D0,0) 18 PREMIX 0;14 Direct Global Read & w/Fileman |
2017/07/26 | ||
| 6896 | HDI READ PHARMACY ORDERABLE ITEM FILE (#50.7) | File | PHARMACY DATA MANAGEMENT | 2018/03/27 | Pending | Private | 50.7 | Allows Health Data & Informatics (HDI) to read the following fields in the PHARMACY ORDERABLE ITEM File (#50.7) in support of the HDI SDO API effort. |
||||
| 6897 | HDI READ PHARMACY DOSAGE FORM FILE (#50.606) | File | PHARMACY DATA MANAGEMENT | 2018/03/27 | Pending | Private | 50.606 | Allows Health Data & Informatics (HDI) to read the following fields in the PHARMACY DOSAGE FORM File (#50.606) in support of the HDI SDO API effort. |
||||
| 6898 | HDI READ PHARMACY MASTER DOSAGE FORM FILE (#50.60699) | File | PHARMACY DATA MANAGEMENT | 2018/03/27 | Pending | Private | 50.60699 | Allows Health Data & Informatics (HDI) to read the following fields in the PHARMACY MASTER DOSAGE FORM File (#50.60699) in support of the HDI SDO API effort. |
||||
| 6899 | HDI READ PHARMACY DRUG FILE (#50) | File | PHARMACY DATA MANAGEMENT | 2018/03/27 | Pending | Private | 50 | Allows Health Data & Informatics (HDI) to read the following fields in the PHARMACY DRUG File (#50) in support of the HDI SDO API effort. |
||||
| 6918 | PSS50P66 | Routine | PHARMACY DATA MANAGEMENT | 2018/05/29 | Pending | Supported | The purpose of this ICR is to grant the ability to return information related to the DOSAGE FORM file (#50.606). |
PSS50P66 | 2018/12/27 | |||
| 6941 | PSSUTIL HAZ | Routine | PHARMACY DATA MANAGEMENT | 2018/07/11 | Pending | Supported | This IA is provided by PDM (Pharmacy Data Management) as an API Function to return Hazardous To Handle and Hazardous To Dispose indication flags per a drug in the DRUG file (#50) or Orderable Item in the PHARMACY ORDERABLE ITEM file (#50.7). Note: Hazardous indications are fields stored in the PSNDF file VA PRODUCT file (#50.68). If any drug has a Hazardous to Handle or Dispose indication, then the Pharmacy Orderable Item (OI) and any drugs pointing to that same OI will be considered Hazardous for the same indications. |
PSSUTIL | ||||
| 6942 | PSSUTIL HAZWARNG | Routine | PHARMACY DATA MANAGEMENT | 2018/07/11 | Pending | Supported | This DBIA is provided by PDM (Pharmacy Data Management) as an API to return the Hazardous To Handle and Hazardous To Dispose alert text generated for a specific drug in the DRUG file (#50) appropriate for the package that is calling it. Note: Hazardous indications are fields stored in the PSNDF file VA PRODUCT file (#50.68). If any drug has a Hazardous to Handle or Dispose indication, then the Pharmacy Orderable Item (OI) and any drugs pointing to that same OI will be considered Hazardous for the same indications. |
PSSUTIL | ||||
| 6987 | PHARMACY PATIENT (#55) FILE | File | PHARMACY DATA MANAGEMENT | 2018/11/08 | Pending | Controlled Subscription | 55 | The Outpatient Pharmacy and CMOP packages request full access to the PHARMACY PATIENT (#55) file. This file is used extensively throughout our routines. Therefore, we request read and write access to the entire file and cross references through Fileman utilities and direct reads/writes. This integration agreement replaces IA #2228. |
||||
| 7206 | Clozapine Inpatient Reference | File | PHARMACY DATA MANAGEMENT | 2020/10/21 | Pending | Private | 55.06 | The MENTAL HEALTH (YS) Clozapine module has a need to read the DATE VERIFIED BY PHARMACIST field (#19) in the UNIT DOSE multiple (#62) (sub-file 55.06) in the PHARMACY PATIENT file (#55) via FileMan. This field is not included in the PHARMACY DATA MANAGEMENT (PDM) API's. When the field becomes available via PDM API, the FileMan reference should be converted to API call and this ICR should be retired. |
||||
| 7330 | INPATIENT PHARMACY MEDICATION RECONCILIATION | File | PHARMACY DATA MANAGEMENT | 2022/03/14 | Pending | Controlled Subscription | 55 | This ICR supports the medication reconciliation feature in COMPREHENSIVE CARE COORDINATION. Reading from file 55 will allow COMPREHENSIVE CARE COORDINATION to display order details for verified Unit Dose, verified IV medications, and Non-VA medications. |
||||
| 7344 | EXCLUDE ONETIME SCHEDULE PARAMETERS | Other | PHARMACY DATA MANAGEMENT | 2022/07/20 | APPROVED | Active | Private | Provide read-only access to the 'PSS EXCLUDE 1TIME STRSTP MODS' parameter entries in the PARAMETER file (#8989.5). |
2022/07/29 | |||
| 7347 | PSSEXLST | Routine | PHARMACY DATA MANAGEMENT | 2022/07/25 | APPROVED | Active | Private | API to check if the ONE-TIME prescription admin schedule is excluded from start/stop dates modifications. |
PSSEXLST | 2022/08/30 | ||
| 7524 | PDM ACCESS FOR PGX ORDER CHECKS VIA CPRS | Routine | PHARMACY DATA MANAGEMENT | 2025/03/17 | APPROVED | Active | Private | With the implementation of Pharmacogenomic (PGx) order checks in MOCHA 3.0, the Computerized Patient Record System (CPRS) will use this API to retrieve PGx order check data from both the Health Data Repository (HDR) and First Data Bank (FDB) during the medication order entry process using a specified internal entry number (IEN) from the DRUG (#50) file for a selected patient. |
PSSPGXOR | 2025/03/20 | ||
| 7526 | PGX GENETIC TEST RESULTS FROM HDR FOR PGX ORDER CHECKS | Routine | PHARMACY DATA MANAGEMENT | 2025/03/19 | APPROVED | Active | Private | Pharmacogenomics findings for Inpatient Medications, Outpatient Pharmacy, and Order Entry/Results Reporting (CPRS). For full input and output details, see the VistA to MOCHA Version 3.0 Interface Document, located under the "Pharm: Data Management (PDM)" section within the "Clinical" section of the VA Software Document Library (VDL). |
PSSPGX | 2025/04/21 | ||
| 7566 | VCRS | PHARMACY DATA MANAGEMENT | Withdrawn | |||||||||
| 10043 | DRUG FILE | File | PHARMACY DATA MANAGEMENT | 2005/06/08 | Retired | Supported | 50 | This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at EMAIL GROUP DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. |