| 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 |
| 34 | DBIA34-A | File | OUTPATIENT PHARMACY | 2003/06/10 | Retired | Private | 50.5 | Direct references are made to the globals to get allergy information. |
||||
| 53 | DBIA53 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | DSS Extracts references the following data from the PRESCRIPTION file(#52). For the extract date range, DSS uses the following cross references: "AD" cross reference ^PSRX("AD",DATE,D0,REFILL# or 0 for NEW RX "AL" cross reference ^PSRX("AL",DATE,D0,REFILL# or 0 for NEW RX "AM" cross reference ^PSRX("AM",DATE,D0,PARTIAL_REFILL# "AR" cross reference ^PSRX("AR",DATE,D0,FILL# This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 60 | DBIA60-A | Routine | OUTPATIENT PHARMACY | 1990/12/11 | Retired | Private | Version 1 of Health summaries exports and calls routine PSOHCSUM. It is exported as routine GMTSPSZO and renamed if needed. Health Summary post-inits check the environment for existance of PSOHCSUM. - If PSOHCSUM does not exist or is an earlier version than 6, GMTSPSZO is renamed PSOHCSUM. - If PSOHCSUM exists and is version 6 or greater, no changes are made. ^GMTSPSO is the component driver, which sets up the context and calls the extract routine prior to printing. ^PSOHCSUM extracts data from the pharmacy files for use with the Health Summary. |
PSOHCSUM | ||||
| 90 | DBIA90-A | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 52 | Amended November 1, 1993. Amended August 30, 1994. Amended October 28, 1997. This agreement will be retired on 12/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 PSO*7*213. 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 Pharmacy Reengineering developers in the C 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 1, 2006. |
||||
| 124 | DBIA124-A | Routine | OUTPATIENT PHARMACY | 1991/11/06 | APPROVED | Active | Private |
Routine PSOCPVW is called by Integrated Billing to display information from the Prescription file (52) to provide a full profile of the prescription that caused the Co-Pay Charges. Input Variable: X $P1: RX Entry Number. The pointer to the Prescription file. $P2: Refill. The second piece is delimited by a colon is optional, if defined is expected to be the entry number of the refill multiple that caused the charges if the charges were created by a refill. Output Writes pertinent data from the prescription file for the requested entry in captioned format. |
PSOCPVW | |||
| 138 | DBIA138 | Routine | OUTPATIENT PHARMACY | 1991/12/09 | Retired | Private | PSOHCSUM | |||||
| 183 | DBIA183 | Routine | OUTPATIENT PHARMACY | 1992/07/16 | Retired | Controlled Subscription | Health Summary will use the entry point DFN^PSOSD1, which can be called with DFN and PSTYPE=1, to print the Action Profile. NOTE: This DBIA has been replaced by DBIA #1281. |
PSOSD1 | ||||
| 184 | DBIA184 | Routine | OUTPATIENT PHARMACY | 1992/07/16 | Retired | Private | OE/RR will use the entry point DFN^PSOSD1, which can be called with DFN and PSTYPE=1, to print the Action Profile. NOTE: This DBIA has been replaced by DBIA #1281. |
PSOSD1 | ||||
| 212 | DBIA212 | File | OUTPATIENT PHARMACY | 1993/02/18 | APPROVED | Active | Private | 59 | ||||
| 236 | DBIA236 | Routine | OUTPATIENT PHARMACY | 1993/06/15 | Retired | Private | PIMS (MAS) users often have a need to print a Drug Profile after printing the 10-10. PIMS, therefore, is given permission from Outpatient Pharmacy to allow PIMS to call the line tag DFN^PSOSD1. This call allows tasked or non-tasked Drug Profile printout. NOTE: This DBIA has been replaced by DBIA #1281. |
PSOSD1 | ||||
| 237 | DBIA237-A | Routine | OUTPATIENT PHARMACY | 1993/06/15 | APPROVED | Active | Private | Integrated Billing is given permission from Outpatient Pharmacy to call HD^PSOSD2 and PAT^PSOSD for the purpose of printing the Action Profile and the Information Profile in batch. CONDITIONS: The entry points may only be used in an approved fashion. The following subroutine uses the entry points in an acceptable manner: RXPROF ;For printing the Outpatient Pharmacy Action Profile or the ;Information Profile for a single patient whose DFN is defined. ;Does not ask for the device nor close the device. ;INPUTS: ;PSDAYS = number of days to print the medication profile for ;PSTYPE=1 for the Action Profile, =0 for the Information Profile ;DFN ; N IBDFN,ADDR,ADDRFL,CLASS,CNDT,DRUG,HDFL,I,II,J,L,LINE,P,PAGE, PSDOB,PSII X,PSNAME,PSOI,PSSN,PSIX,PGM,PRF,PSDATE,VAL,VAR,RX, RX0,RX2,ST,ST0,PSDAY,RF,RFS,PSOPRINT,X1,X2,ZTSK,X,Y,PSII,PSDT,LMI S IBDFN=DFN S X1=DT,X2=-PSDAYS D C^%DTC S (PSDATE,PSDAY)=X S LINE="" F I=1:1:132 S LINE=LINE_"-" S PAGE=1 D HD^PSOSD2,PAT^PSOSD W @IOF S DFN=IBDFN Q |
PSOSD2 | |||
| 254 | DBIA254 | File | OUTPATIENT PHARMACY | 1993/07/26 | APPROVED | Active | Private | 52 | Drug Accountability has permission from Outpatient Pharmacy for the following: To collect dispensing data, the Drug Accountability ^PSAOP* routines loop through the "AL" (original & refills), "AJ" (return to stock), "AM" & "AN" (partials), and "AR" (status) x-refs in the PRESCRIPTION (#52) file. A date/time is stored as a starting point for each drug. Using these x-refs, the 6th piece of ^PSRX(D0,0) is checked to see if the drug is stocked in a Drug Accountability location and the 9th piece of ^PSRX(D0,2) is checked for Outpatient site. Quantity for original prescriptions, the 7th piece of ^PSRX(D0,0) is used. For refills, the 4th piece of ^PSRX(D0,1,D1,0) is used. For partials, the 4th piece of ^PSRX(D0,P,D1,0) is used. GLOBAL MAP DATA DICTIONARY #52 -- PRESCRIPTION FILE STORED IN ^PSRX( (VERSION 6.0) -------------------------------------------------------------- CROSS REFERENCED BY: RETURNED TO STOCK(AJ),RETURNED TO STOCK(AJ1) RELEASED DATE/TIME(AL), RELEASED DATE/TIME(AL1), RELEASED DATE/TIME(AM), RETURNED TO STOCK(AN), ^PSRX(D0,0)= (#.01) RX # [1F] ^ (#6) DRUG [6P] ^ (#7) QTY [7N] ^PSRX(D0,1,0)=^52.1DA^^ (#52) REFILL ^PSRX(D0,1,D1,0)=^ (#1) QTY [4N] ^ (#14) RETURNED TO STOCK[16D] ==>^ (#17) RELEASED DATE/TIME [18D] ^PSRX(D0,2)=^(#20) DIVISION [9P] ^(#31) RELEASED DATE/TIME[13D] ==>^ (#32.1) RETURNED TO STOCK[15D] ^ ^PSRX(D0,P,0)=^52.2DA^^ (#60) PARTIAL DATE ^PSRX(D0,P,D1,0)=^(#.04) QTY [4N] ^(#5)RETURNED TO STOCK [16D] ==>^ (#8) RELEASED DATE/TIME [19D] ^ |
|||
| 328 | DBIA328 | Routine | OUTPATIENT PHARMACY | 1994/01/11 | APPROVED | Active | Private | Routine call to POT^PSOCOPAY to pass the DFN, the internal entry number for the patient and returns a number for 30 days Rx supplies. Input Variable: DFN-the patient's internal entry number Output Variable: X-a number, of 30 day supplies that a patient has for potential bills. |
PSOCOPAY | |||
| 330 | PSOHCSUM | Routine | OUTPATIENT PHARMACY | 1994/01/12 | APPROVED | Active | Controlled Subscription | Provides a list of active Rxs (Active/Non-Verified/Hold/Suspend/Provider Hold) and Non-VA MEDS (Not dispensed by VA) sorted in the reverse fill date order for a given DFN. Revision History: - Added 3/4/25 effective with PSO*7*650 and OR*3*561 to add the Complex Doses for Non-VA medications. |
PSOHCSUM | 2025/03/04 | ||
| 465 | DBIA465 | File | OUTPATIENT PHARMACY | 1994/04/26 | APPROVED | Active | Private | 52 | The Pharmacy Benefits Management software will use the prescription file to extract drug statistics for a selected time frame. |
|||
| 517 | DBIA34-C | File | OUTPATIENT PHARMACY | 1989/03/13 | Retired | Private | 57 | Direct references are made to the globals to get allergy information. |
||||
| 523 | DBIA60-C | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 566 | DBIA106-B | File | OUTPATIENT PHARMACY | 2005/06/20 | Retired | Private | 52 | Routine QIP3POLY reads the following fields: In file 52, PRESCRIPTION 6 - DRUG 101 - LAST DISPENSED DATE 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. Add under #52 PRESCRIPTION file 100 STATUS |
||||
| 589 | DBIA124-B | Other | OUTPATIENT PHARMACY | 1991/11/06 | Retired | Private |
Export of options PSOCP TRANSACTION and PSOCP RESET COPAY STATUS in version 1 of the Integrated Billing Package.Export of the IB SERVICE/SECTION field of the Pharmacy Site file (59) and the CO-PAY TRANSACTION TYPE, IB NUMBER and REFILL DATE (entire multiple) fields of the Prescription file in version 1 of the Integrated Billing Package. Export of routines PSOCP, PSOCPA, PSOCPB, PSOCPC, PSOCPD, PSOCPVW, PSOLBL, PSONEW, PSONEW3,PSORENW1, PSORXDL, PSORXED, PSORXL, PSOSD0, PSOSD1,PSOSD 2, PSOSULB1, and PSOSULBL. Export PSO NEWSITE input template of the Pharmacy Site file (59). |
|||||
| 591 | DBIA124-D | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 |
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. Direct reference to ^PSRX by Integrated Billing to determine if the link between Integrated Billing and the Prescription file is intact. Direct global reads of the ICD DIAGNOSIS multiple's fields. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 675 | DBIA191-C | Routine | OUTPATIENT PHARMACY | 1992/08/18 | APPROVED | Active | Private |
STAT^PSOFUNC: This is the Pharmacy treatment status function and is used in the Pharmacy patient profile. The required variables are RX0, RX2, and J. |
PSOFUNC | |||
| 678 | DBIA191-F | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 |
^PSRX(DA, for prescription data. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 707 | DBIA237-B | Routine | OUTPATIENT PHARMACY | 1993/06/15 | APPROVED | Active | Private | Integrated Billing is given permission from Outpatient Pharmacy to call HD^PSOSD2 and PAT^PSOSD for the purpose of printing the Action Profile and the Information Profile in batch. CONDITIONS: The entry points may only be used in an approved fashion. The following subroutine uses the entry points in an acceptable manner: RXPROF ;For printing the Outpatient Pharmacy Action Profile or the ;Information Profile for a single patient whose DFN is defined. ;Does not ask for the device nor close the device. ;INPUTS: ;PSDAYS = number of days to print the medication profile for ;PSTYPE=1 for the Action Profile, =0 for the Information Profile ;DFN ; N IBDFN,ADDR,ADDRFL,CLASS,CNDT,DRUG,HDFL,I,II,J,L,LINE,P,PAGE, PSDOB,PSII X,PSNAME,PSOI,PSSN,PSIX,PGM,PRF,PSDATE,VAL,VAR,RX, RX0,RX2,ST,ST0,PSDAY,RF,RFS,PSOPRINT,X1,X2,ZTSK,X,Y,PSII,PSDT,LMI S IBDFN=DFN S X1=DT,X2=-PSDAYS D C^%DTC S (PSDATE,PSDAY)=X S LINE="" F I=1:1:132 S LINE=LINE_"-" S PAGE=1 D HD^PSOSD2,PAT^PSOSD W @IOF S DFN=IBDFN Q |
PSOSD | |||
| 780 | DBIA273-B | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | #52 PRESCRIPTION FILE ^PSRX( 52,.01 RX # 0;1 FREE TEXT (Required) 52,4 PHYSICIAN 0;4 POINTER TO PROVIDER FILE (#6) 52,6 DRUG 0;6 POINTER TO DRUG FILE (#50) (Required) 52,20 DIVISION 2;9 POINTER TO PHARMACY SITE FILE (#59) 52,301 CLOZAPINE DOSAGE (MG/DAY) SAND;1 NUMBER 52,302 WBC RESULTS SAND;2 NUMBER 52,303 DATE OF WBC TEST SAND;3 DATE This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 782 | DBIA273-D | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52.52 | #52.52 CLOZAPINE PRESCRIPTION OVERRIDES FILE ^PS(52.52 Entire File This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 783 | DBIA273-E | File | OUTPATIENT PHARMACY | 1993/08/30 | Retired | Private | 59 | 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. #59 -- PHARMACY SITE FILE ^PS(59 59,1 SITE DEA NUMBER SAND;1 FREE TEXT 59,2 SITE (NATIONAL NAME) SAND;2 POINTER TO QUIC SORT DATA FILE (#736) |
||||
| 785 | DBIA276-B | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 786 | DBIA785-C | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 52.5 | This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 824 | DBIA302-D | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 |
File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 52 .01 0;1 RX # B 1 0;13 ISSUE DATE 4 0;4 PROVIDER 6 0;6 DRUG << see note (i) >> 7 0;7 QTY 8 0;8 DAYS SUPPLY 9 0;9 # OF REFILLS 10 0;10 SIG << see note (ii) >> 12 3;7 REMARKS 16 0;16 CLERK CODE 20 2;9 DIVISION 22 2;2 FILL DATE 26 2;6 EXPIRATION DATE 52 (multiple in REFILL B file 52.1) 100 0;15 STATUS << see note (iii) >> 101 3;1 LAST DISPENSED DATE << see note (iv) >> File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 52.1 .01 0;1 REFILL DATE B Notes: (i) Points to the DRUG file (#50), not the NATIONAL DRUG file (#50.6). This could give incorrect drug name if pointer is in the NATIONAL DRUG file. (ii) This is parsed by spaces within the free text. If an entry is not found in the MEDICATION INSTRUCTION file (#51), the & free text is used. (iii) This is calculated using the module STAT^PSOEXDT (iv) This will always be the last fill, not just last refill This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 885 | DBIA885 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 52 | This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 920 | DBIA920 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | Read only access for the ^PSRX(x,0) node. In routines LRBLPE1 and LRBLPH: ...I $D(^PSRX(Y,0)) S ^TMP($J,+$P(^(0),"^",6))=O We are $O(^PS(55,DFN,"P",X)) to build the ^TMP( array. We then use that array for possible data. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 980 | PSODISP | Routine | OUTPATIENT PHARMACY | 1994/08/30 | APPROVED | Active | Private | To display help at the prescription selection prompt. |
PSODISP | |||
| 981 | PSOFUNC | Routine | OUTPATIENT PHARMACY | 1994/08/30 | APPROVED | Active | Private | To determine the status of a prescription |
PSOFUNC | |||
| 982 | PSOLSET | Routine | OUTPATIENT PHARMACY | 1994/08/30 | APPROVED | Active | Private | To kill Outpatient variables. |
PSOLSET | |||
| 983 | PSOCSRL | Routine | OUTPATIENT PHARMACY | 1994/08/30 | APPROVED | Active | Private | To release prescriptions from a vault. |
PSOCSRL | |||
| 985 | RX PATIENT STATUS | File | OUTPATIENT PHARMACY | 1994/08/30 | Pending | Controlled Subscription | 53 | |||||
| 986 | DBIA986 | File | OUTPATIENT PHARMACY | 1994/08/30 | APPROVED | Active | Private | 52 | For the Controlled Substances/Outpatient interface, read access is required for several fields in the PRESCRIPTION file. |
|||
| 1030 | DBIA1030-A | Routine | OUTPATIENT PHARMACY | 1994/11/09 | APPROVED | Active | Controlled Subscription | These entry points can be used to batch process prescriptions received via telecommunications. |
PSOBBC | |||
| 1060 | DBIA1030-B | Routine | OUTPATIENT PHARMACY | 1994/11/09 | Retired | Controlled Subscription | This entry point can be used to get the site number of the site running the Outpatient Pharmacy package. |
PSOLSET | ||||
| 1079 | DBIA1079-A | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | Direct read access to PS global. Used to extract pharmacy outpatient RX data. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
|||||
| 1081 | DBIA1079-C | Routine | OUTPATIENT PHARMACY | 1994/12/13 | Retired | Private | This routine needs to maintain the calls to Pharmacy Prescription Practices (PPP). |
PSOBBC | ||||
| 1082 | DBIA1079-D | Routine | OUTPATIENT PHARMACY | 1994/12/13 | Retired | Private | This routine needs to maintain the calls to Pharmacy Prescription Practices (PPP). |
PSONUM | ||||
| 1084 | DBIA1079-F | Routine | OUTPATIENT PHARMACY | 1994/12/13 | Retired | Private | This routine needs to maintain the calls to Pharmacy Prescription Practices (PPP). |
PSORX | ||||
| 1086 | DBIA1079-H | Other | OUTPATIENT PHARMACY | 1994/12/13 | Retired | Private | The following PSO routines will be distributed as part of the PPP v1.0 release. The routines will be sent in the PPP namespace and then translated back to their PSO namespace as part of the PPP post init. At that point PSO becomes custodian of the routines and will be responsible for any reported problems. PSO will be responsible for entering an informational patch describing the destribution of the PSO routines by PPP. The routines are: 1. PSOBBC PPPSE01 2. PSONUM PPPSE02 3. PSOPRF PPPSE03 4. PSORX PPPSE04 5. PSOSD PPPSE05 The patch number is PSO*6*105 |
PSOSD | ||||
| 1221 | DBIA1220-B | File | OUTPATIENT PHARMACY | 1998/07/31 | Retired | Private | 52 | The Consolidated Mail Outpatient Pharmacy package will extract data on a daily basis. Fields noted with write access will be updated on a daily basis. The extensive overhead associated with building transmission data prevents the CMOP software from utilizing the supported reference for Outpatient Pharmacy Version 7.0 as described in DBIA 1878. This agreement is PRIVATE and designed for use ONLY by the CMOP software. |
||||
| 1222 | DBIA1220-C | File | OUTPATIENT PHARMACY | 1995/05/09 | Retired | Private | 52.5 | The Consolidated Mail Outpatient Pharmacy package will extract data from this file on a daily basis. The CMOP INDICATOR field (#3) is created by the CMOP software and is used to manage the prescription data for CMOP transmission. |
||||
| 1281 | DBIA183 - A | Routine | OUTPATIENT PHARMACY | 1995/06/06 | APPROVED | Active | Controlled Subscription | PSOSD1 | ||||
| 1336 | DBIA1030-C | Routine | OUTPATIENT PHARMACY | 1995/09/12 | APPROVED | Active | Controlled Subscription | This entry point is used to build an Outpatient prescription profile for a patient. This profile is in the form of an array, names PSOSD. |
PSORX | |||
| 1527 | DBIA1527 | Other | OUTPATIENT PHARMACY | 1996/04/05 | APPROVED | Active | Private | Inpatient Medications would like to include the PSO INTERVENTION MENU andrelated options as a component. This would allow pharmacists to have thesame functionality for interventions in Inpatient Medications that existsin Outpatient Pharmacy. The options included on this menu are: PSO INTERVENTION NEW ENTRY PSO INTERVENTION EDIT PSO INTERVENTION PRINTOUT PSO INTERVENTION DELETE PSO INTERVENTION VIEW |
||||
| 1876 | DBIA1876 | File | OUTPATIENT PHARMACY | 1996/12/06 | APPROVED | Active | Controlled Subscription | 59 | The DSS PRESCRIPTION EXTRACT file (#727.81) contains the DIVISION field (9) which is a pointer to the OUTPATIENT SITE file (#59). Direct global read of the 'B' Cross Reference is permitted into this file. |
|||
| 1878 | DBIA1878 | Routine | OUTPATIENT PHARMACY | 1996/12/11 | APPROVED | Active | Supported | Open subscription for Outpatient Pharmacy prescription data. |
PSOORDER | |||
| 1968 | DBIA1968 | Routine | OUTPATIENT PHARMACY | 1997/03/27 | APPROVED | Active | Private | In the CMOP routine PSXEDIT, a call is made to EN1^PSONEW2 to complete the editing of a prescription. |
PSONEW2 | |||
| 1969 | DBIA1969 | Routine | OUTPATIENT PHARMACY | 1997/03/27 | APPROVED | Active | Private | The CMOP package calls the Outpatient Pharmacy routine, PSORXL in order to print prescription labels at the medical center pharmacy. |
PSORXL | |||
| 1970 | DBIA1970 | Routine | OUTPATIENT PHARMACY | 1997/03/27 | APPROVED | Active | Private | The CMOP package makes a call to the Outpatient Pharmacy routine, PSOSURST in order to reset and print pharmacy labels. This call is made when the user selects the option to reset and print window labels. There aren't any I/O variables. |
PSOSURST | |||
| 1971 | DBIA1971 | Routine | OUTPATIENT PHARMACY | 1997/03/27 | APPROVED | Active | Private | The CMOP package makes a call to the Outpatient Pharmacy routine, PSOSULBL. This call is made from the CMOP routine, PSXRSUS when the user selects the option to Print Standard Suspense at the medical center pharmacy. There aren't any I/O variables in this call. |
PSOSULBL | |||
| 1972 | DBIA1972 | Routine | OUTPATIENT PHARMACY | 1997/03/27 | APPROVED | Active | Private | The CMOP package makes a call to the Outpatient Pharmacy routine, PSOSUCHG. This call is made when a user is using the Change Suspense Date option on the Suspense Menu for Outpatient Pharmacy. Any Rx that is entered by the user is screened for CMOP. This screening process is handled by the CMOP routine, PSXCH. Once the screening is finished PSXCH calls PSOSUCHG to complete the processing. |
PSOSUCHG | |||
| 1973 | DBIA1973 | Routine | OUTPATIENT PHARMACY | 1997/03/27 | APPROVED | Active | Controlled Subscription | The CMOP package makes a call to the Outpatient Pharmacy routine, PSOLSET. This call is made to set up the required OP system variables that are necessary for pulling Rx's from suspense during the CMOP transmission process or when CMOP labels are printed at the medical center pharmacy. |
PSOLSET | |||
| 1974 | DBIA1974 | Routine | OUTPATIENT PHARMACY | 1997/03/27 | APPROVED | Active | Private | The CMOP package makes a call to the Outpatient Pharmacy routine, PSOCP. This call is made when the CMOP process is filing the release data that is returned by the CMOP facility. The call is made in order to generate any copay charges for the Rx. |
PSOCP | |||
| 1975 | DBIA1975 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 53 | This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 1976 | DBIA1976 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 59 | The subscribing pharmacy packages are allowed direct global read access to all fields and cross-references of file #59. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 1977 | DBIA1977 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 52 | The CMOP package requires direct R/W access to all fields and cross-references in file 52. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 1978 | DBIA1978 | File | OUTPATIENT PHARMACY | 1997/03/28 | APPROVED | Active | Private | 52.5 | The CMOP package requires direct R/W access to all fields and cross-references in file 52.5. |
|||
| 1998 | DBIA1998 | Routine | OUTPATIENT PHARMACY | 1997/04/09 | APPROVED | Active | Controlled Subscription | This integration agreement allows a call in to routine PSODACT and line tag ENSTUFF for purposes of printing the Drug Use Evaluations (DUE). |
PSODACT | |||
| 2020 | DBIA2020 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | A direct reference to the Prescription file is requested for the Unit Price of Drug field so the VA Cost of a prescription fill can be calculated and billed. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2029 | DBIA2029 | Routine | OUTPATIENT PHARMACY | 1997/06/02 | APPROVED | Active | Private | Integrated Billing requests permission to call three entry points in the Outpatient Pharmacy routine PSOCPTRI. This routine contains the interface points between IB and Pharmacy which are needed to support the real-time billing of Tricare prescriptions using a commercial pharmacy billing software package. |
PSOCPTRI | |||
| 2099 | PSORPH | Other | OUTPATIENT PHARMACY | 1997/09/05 | APPROVED | Active | Private | PDM requests permission to check for the PSORPH security key. |
||||
| 2122 | DBIA2122 | Routine | OUTPATIENT PHARMACY | 1997/09/05 | APPROVED | Active | Private | PDM requests permission to call PSOHELP1. This routine is called by a compiled cross-reference routine (PSSJXR) ON PHARMACY PATIENT file 55. PSOHELP1 sets two cross-references in file #55 ("A" and "P") involked from VA FileMan. |
PSOHELP1 | |||
| 2188 | DBIA2188 | Routine | OUTPATIENT PHARMACY | 1997/10/16 | APPROVED | Active | Private | Inpatient Medications requests permission to call (Outpatient Pharmacy) EN^PSOHLNEW. This entry point allows the order message array from OERR to be passed to Outpatient Pharmacy for processing. All message arrays from OERR come through the Inpatient Meds routine. The PATIENT CLASS field comes in the array from OERR. If the value is "I", it is processed as an Inpatient Order. If the value is "O" this call is made to process the order as an Outpatient order. Variables are described below. Input: EN^PSOHLNEW(.MSG) MSG - The message array from OERR. Output: none |
PSOHLNEW | |||
| 2189 | DBIA2189 | Routine | OUTPATIENT PHARMACY | 1997/10/17 | APPROVED | Active | Private | Inpatient Medications request permission to call (Outpatient Pharmacy) EN^PSODRDU2. If the inpatient has a drug-drug interaction, drug class, or duplicate drug with an outpatient order with call is made. The call displays the outpatient order's information. The call occurs during the inpatient order entry. Variables are described below. Input: EN^PSODRDU2(DFN,RXNUM) DFN - Patient's internal entry number is ^DPT. RXNUM - P1_P2_;_P3 where P1= Order number P2= Order Type, either "P" for pending or "R" for active RX P3= Pharmacy package code, either "I" or "O" Output: none |
PSODRDU2 | |||
| 2190 | DBIA2190 | Routine | OUTPATIENT PHARMACY | 1997/10/21 | APPROVED | Active | Controlled Subscription |
Inpatient Medications request permission to call (Outpatient Pharmacy) ^PSOORDRG. This call returns drug-drug order checks. |
PSOORDRG | |||
| 2211 | DBIA2211 | Routine | OUTPATIENT PHARMACY | 1997/10/29 | APPROVED | Active | Private | Inpatient Medications requests permission to call (Outpatient Pharmacy) ^PSOORDA. This call builds the ^TMP("PSJAL" and ^TMP("PSJDA" globals that contain the patients Allergy/Adverse Reaction information to display on the ListMan screen. |
PSOORDA | |||
| 2257 | DBIA2257 | Routine | OUTPATIENT PHARMACY | 1998/01/06 | APPROVED | Active | Private | Inpatient Medications requests permission to call INPAT^PSOBUILD. This entry point is used to display a patient's current Outpatient medications. Input variable: PSODFN Output variable: <none> |
PSOBUILD | |||
| 2258 | DBIA2258 | Routine | OUTPATIENT PHARMACY | 1998/01/06 | APPROVED | Active | Private | Inpatient Medications requests permission to call ^PSOVWI (Outpatient Pharmacy). This entry point is used to display a Pharmacy intervention in a captioned format. |
PSOVWI | |||
| 2259 | DBIA2259 | Other | OUTPATIENT PHARMACY | 1998/01/06 | APPROVED | Active | Private | Inpatient Medications requests permission to use the following Outpatient Pharmacy templates. These templates are used by Inpatient Medications to Enter, Edit, and Print Pharmacy interventions. Input Template [PSO INTERVENTION EDIT] [PSO INTERVENTION NEW] Print Template [PSO INTERVENTIONS] Sort Template [PSO INTERVENTIONS] These templates are used by the following Inpatient Medication protocols: PSJ LM INTERVENTION EDIT PSJ LM INTERVENTION NEW ENTRY PSJ LM INTERVENTION PRINTOUT PSJ LM INTERVENTION VIEW |
||||
| 2260 | DBIA1030-D | Routine | OUTPATIENT PHARMACY | 1998/01/09 | APPROVED | Active | Controlled Subscription | This entry point is used to build an Outpatient prescription profile for a patient. The profile is returned in the form of an array, named PSOSD. |
PSORX1 | |||
| 2358 | DISCONTINUE OP MEDS ON DATE OF DEATH | Routine | OUTPATIENT PHARMACY | 1998/04/03 | APPROVED | Active | Private | PSOCAN3 | ||||
| 2385 | DBIA2385 | Routine | OUTPATIENT PHARMACY | 1998/05/07 | APPROVED | Active | Private | The Consolidated Mail Outpatient Pharmacy (CMOP) Package requests an integration agreement with the Outpatient Pharmacy (OP) V. 7.0 package. The agreement covers a single entry point in the OP package at EN^PSOHLSN1(IEN #52, "ZD"). These two parameters are the only ones that are required. Others are optional. Prescription event data is passed through the OP package to the Clinical Information Resources Network (CIRN) package in the form of the Rx internal entry # from file 52. No data is returned to the CMOP package from the CIRN package. This agreement also covers the same entry point in the OP package at EN^PSOHLSN1(IEN #52, "SC"). These two parameters are the only ones that are required. Others are optional. In this case, the prescription event data is passed to the Computerized Patient Record System (CPRS) package to update status information for CMOP prescriptions. No data is returned to the CMOP package. |
PSOHLSN1 | |||
| 2397 | OE/RR CALL TO PSOHLUP | Routine | OUTPATIENT PHARMACY | 1998/05/10 | APPROVED | Active | Private | Order Entry/Results Reporting calls PSOHLUP during the CPRS orders conversion. |
PSOHLUP | |||
| 2398 | OE/RR CALL TO PSORENW | Routine | OUTPATIENT PHARMACY | 1998/05/10 | APPROVED | Active | Private | The Order Entry/Results Reporting would like approval to call the extrinsic function $$RENEW^PSORENW(ien). |
PSORENW | |||
| 2399 | OE/RR CALL TO PSOREF FOR REFILL CHECK | Routine | OUTPATIENT PHARMACY | 1998/05/10 | APPROVED | Active | Private | Order Entry/Results Reporting requests permission to call REFILL^PSOREF to determine whether an order is refillable. |
PSOREF | |||
| 2400 | OE/RR CALLS TO PSOORRL | Routine | OUTPATIENT PHARMACY | 1998/05/10 | APPROVED | Active | Controlled Subscription | Order Entry/Results Reporting requests approval to make the following calls to PSOORRL. Patch PSO*7*622 updated OCL^PSOORRL with two new parameters to accept a second set of date ranges for Inpatient Medications. Previously, this API only supported one set of date ranges used for both Outpatient Medications and Inpatient Medications. Existing callers of this API will not see any change in behavior, as if nothing is passed into the new parameters, it will behave as it did previously. Only if a caller wishes to use different date ranges for Outpatient/Non-VA Medications and Inpatient Medication they need to utilize the new parameters. |
PSOORRL | 2008/07/28 | ||
| 2471 | DBIA2471 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | CIRN needs read access to ^PSRX, to calculate the Master of Record score. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2476 | PSOCMOP | Routine | OUTPATIENT PHARMACY | 1998/07/09 | APPROVED | Active | Private | This integration agreement between the Consolidated Mail Outpatient Pharmacy (CMOP) package with the Outpatient Pharmacy V 7.0 (OP) package allows CMOP to call the routine PSOCMOP (used exclusively for CMOP purposes) at line tag TEST from routine PSXRESUB. This call allows an Rx fill that has been rejected by a CMOP host facility to be resubmitted to that facility a single time. Two input variables are passed to PSOCMOP: PPL = IEN of Rx in Prescription file (#52) ZD(IEN of Rx in 52) = Current Date/Time One output variable is returned: PPL = If contains a value indicates that Rx was not eligible for CMOP resubmission. If null, then Rx has been placed in suspense for CMOP transmission. CMOP Routine OP Routine Variables in Variables out PSXRESUB TEST^PSOCMOP PPL PPL ZD(IEN 52) |
PSOCMOP | |||
| 2477 | DBIA2477 | Routine | OUTPATIENT PHARMACY | 1998/07/14 | APPROVED | Active | Private | PSOLBL | ||||
| 2478 | DBIA2478 | Routine | OUTPATIENT PHARMACY | 1998/07/14 | Other | Private | PSOSULB1 | |||||
| 2510 | DBIA2510 | File | OUTPATIENT PHARMACY | 1998/08/24 | APPROVED | Active | Private | 59 | Pharmacy Benefits Management extracts data from the division fields of the prescription file (#52) and outpatient site field of the drug accountability stats file (#58.8). These fields point to the Outpatient site file #59 from which the outpatient site name and number can be extracted. |
|||
| 2511 | DBIA2511 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 53 | Pharmacy Benefits Management extracts the Rx Patient status from the Prescription file to determine the AMIS workload category for a prescription. THIS REQUEST IS FOR VERSION 6 OF OUTPATIENT PHARMACY ONLY. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2512 | DBIA2512 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | Pharmacy Benefits Management extracts various data elements from the PRESCRIPTION file #52 for a selected time frame. In order to obtain the data desired and to use the supported DBIA 1878 provided for version 7 of Outpatient Pharmacy access is needed to the following. DBIA 1878 requires the DFN and RX IEN, i.e. D EN^PSOORDER(DFN,RX). This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2513 | DBIA2513 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | Pharmacy Benefits Management extracts data elements from the PRESCRIPTION file (#52) for a selected time frame. This is for version Outpatient Pharmacy V. 6.0 only. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2534 | DBIA2534 | Routine | OUTPATIENT PHARMACY | 1998/09/08 | APPROVED | Active | Controlled Subscription | This agreement provides CPRS two entry points to call that will return flags that indicate whether or not to ask various Copay-related questions concerning the Outpatient order being entered through CPRS. Prior to the effective date of the Veterans Millennium Health Care and Benefits Act, the only question that should be asked in CPRS is the Service Connected question. After the effective date of the Bill, seven additional questions can potentially be asked during the medication order process in CPRS. |
PSOCP | |||
| 2616 | DBIA2616 | Routine | OUTPATIENT PHARMACY | 1998/10/19 | APPROVED | Active | Controlled Subscription | This agreement allows the Controlled Substances package to call the Outpatient Pharmacy package to request that the last refill of a prescription be deleted. This will be for Outpatient Version 7.0 and greater. The Outpatient Pharmacy version check will be done by the Controlled Substances package. |
PSOCAN | |||
| 2621 | DBIA2621 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Controlled Subscription | 59 | This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2678 | DBIA2678 | File | OUTPATIENT PHARMACY | 1998/12/30 | Pending | Private | 52 | The CIRN Outpatient Pharmacy data extraction routine (^RGHORXO - HL7 Message Generation for Prescriptions), makes several references to fields in the PRESCRIPTION file (#52), Version 6 only, for the purpose of creating the HL7 transmission records. *Note: Some of the referenced PRESCRIPTION file fields have already been defined in DBIA: 824. |
||||
| 2680 | OE/RR use of PSRX global | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | As part of the pre-CPRS functionality that is released with OR*2.5*49, an estimate of global growth is given. One of the components of that growth is the backfilling of outpatient pharmacy prescriptions. In order to calculate the number of prescriptions that might be backfilled, we loop through the PHARMACY PATIENT file and then through the "A" x-ref of the PRESCRIPTION PROFILE multiple (#55.03). We then get the pointer to the PRESCRIPTION file (from the cross-reference) where we check the status of the prescription and the existence of a PATIENT file pointer. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2844 | DBIA 2844 | File | OUTPATIENT PHARMACY | 1999/06/14 | APPROVED | Active | Private | 52.41 | This agreement gives the Pharmacy Data Management package access to the PLACER NUMBER (#.01) field in the PENDING OUTPATIENT ORDERS (#52.41) file. This access will be needed every time an action is taken on a pending Outpatient order, for the purpose of locking the order in Outpatient Pharmacy and in Computerized Patient Record System (CPRS). |
2020/01/29 | ||
| 2845 | DBIA 2845 | File | OUTPATIENT PHARMACY | 1999/06/14 | APPROVED | Active | Private | 52 | This agreement gives the Pharmacy Data Management package access to the PLACER ORDER # (#39.3) field in the PRESCRIPTION (#52) file. This access will be needed every time an action is taken on a prescription, for the purpose of locking the order in Outpatient Pharmacy and in Computerized Patient Record System (CPRS). |
2020/01/29 | ||
| 2905 | TIU MEDICATION OBJECTS READ PHARMACY FILE | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | 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: ^PSRX( - PRESCRIPTION FILE (#52) Node 0, piece 6 - DRUG FIELD (#6) Node "OR1", piece 1 - PHARMACY ORDERABLE ITEM FIELD (#39.2) This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 2906 | TIU MEDICATION OBJECTS READ PHARMACY FILE | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52.41 | 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.41, - PENDING OUTPATIENT ORDERS FILE (#52.41) Node 0, piece 8 - PHARMACY ORDERABLE ITEM FIELD (#8) Node 0, piece 9 - DRUG FIELD (#11) This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 3064 | CONTROLLED SUBSTANCE API | Routine | OUTPATIENT PHARMACY | 2000/03/14 | APPROVED | Active | Private |
When a prescription is returned to stock in Outpatient Pharmacy 7.0, the entry is deleted from the prescription file. If the prescription was a controlled substance, the pharmacy location's balance is not updated. This API will check the prescription when it is being returned. If the prescription is for a controlled substance, the user will be asked if they want to update the balances for the associated pharmacy location. |
PSDOPT0 | |||
| 3142 | DBIA3142 | Routine | OUTPATIENT PHARMACY | 2000/07/13 | APPROVED | Active | Controlled Subscription | This agreement allows the Clinical Reminders package to call the Outpatient Pharmacy package for patient and prescription information, based on a specified date range and a specified list of medications. |
PSOORAPI | |||
| 3237 | DBIA3237 | Routine | OUTPATIENT PHARMACY | 2000/10/30 | APPROVED | Active | Private | This call, provided by Outpatient Pharmacy, will return a default Quantity value or a default Days Supply to CPRS for the Outpatient medication order entry process through CPRS. A value will only be returned if a value can appropriately be determined, based on data passed into the call. If a Quantity value is not received in this call, then a default Quantity value will be calculated. If a Quantity value is received in this call, then a default Days Supply value will be calculated. |
PSOSIG | |||
| 3278 | DBIA3278 | Routine | OUTPATIENT PHARMACY | 2000/12/29 | APPROVED | Active | Private | These calls, provided by Outpatient Pharmacy, will return default values to Computerized Patient Record System (CPRS) for Days Supply and Maximum Number of Refills for the medication order entry process. |
PSOSIGDS | |||
| 3349 | DBIA3349 | File | OUTPATIENT PHARMACY | 2001/03/28 | Withdrawn | Private | 52 | Integrated Billing has permission to access the following fields on the PRESCRIPTION file (#52): GLOBAL REFERENCE: ^PSRX(D0,0) .01 RX # 0;1 Direct Global Read 6 DRUG 0;6 Direct Global Read |
||||
| 3462 | DBIA3462 | Routine | OUTPATIENT PHARMACY | 2001/10/01 | APPROVED | Active | Private | A private IA for IB to call PSO to make them aware of a billing event that has taken place. |
PSOCPIB | |||
| 3478 | PSODRG | Routine | OUTPATIENT PHARMACY | 2001/11/15 | APPROVED | Active | Private | Allows CPRS to use EN^PSODRG to obtain information regarding lab tests linked to clozapine medications. |
PSODRG | |||
| 3500 | PDM CONVERSION ACCESS | File | OUTPATIENT PHARMACY | 2002/01/16 | APPROVED | Active | Private | 52 | Pharmacy Data Management (PDM) requests a one-time DBIA with Outpatient Pharmacy to allow direct read access to the PRESCRIPTION file (#52), to retrieve the LOGIN DATE field (#21). As part of the Pharmacy Benefits Management project, PDM is processing through all Unit Dose, IV and Outpatient Pharmacy orders/prescriptions to find the first Pharmacy service date. In order to do this, PDM needs to be able to retrieve the login date information for a prescription. This will be in a multi-package build titled PSS PSJ PSO Service Date. |
|||
| 3501 | DBIA3501 | File | OUTPATIENT PHARMACY | 2002/01/17 | APPROVED | Active | Private | 52 | ||||
| 3768 | DBIA3768 | Routine | OUTPATIENT PHARMACY | 2002/09/25 | APPROVED | Active | Private | The purpose of this agreement is to provide the APIs necessary for the My HealtheVet system to make refill requests via the internet. The APIs will provide the ability to submit a request and get the status of each request. |
PSOPRA | |||
| 3792 | PXRM DIRECT READ OF THE PRESCRIPTION FILE | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | Clinical Reminders requests the ability to do a global read on the PRESCRIPTION FILE #52 specifically, ^PSRX(, using multiple fields from the Refill multiple, and the Partial Date multiple to populate the new Clinical Reminders Index. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 3793 | PSOPXRM1 | Routine | OUTPATIENT PHARMACY | 2002/10/21 | Under Revision | Controlled Subscription | PSOPXRM1 | |||||
| 3848 | DBIA 3848 | File | OUTPATIENT PHARMACY | 2002/11/20 | APPROVED | Active | Private | 52.41 | This agreement gives the Controlled Substance package read access to the PENDING OUTPATIENT ORDERS (#52.41) file and the "AD" (LOGIN DATE) cross reference. This access will be needed to generate the Digitally Signed CS Order Report for controlled substance orders entered electronically and signed digitally through Computerized Patient Record System (CPRS) as part of the DEA/VA PKI project. |
|||
| 4071 | 4071 | Routine | OUTPATIENT PHARMACY | 2003/04/01 | APPROVED | Active | Private | PSOLBL3 | ||||
| 4182 | DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52 | The following global references are made: Global Nodes PSRX $O(^PSRX(DA)) $P(^PSRX(DA,0),U,M) M=2,6,8 $P(^PSRX(DA,2),U,13) $O(^PSRX(DA,1,DA1)) $P(^PSRX(DA,1,DA1,0),U,M) M=10,18 $O(^PSRX(DA, P ,DA1)) $P(^PSRX(DA, P ,DA1,0),U,M) M=10,19 This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 4195 | DBIA4195 | Routine | OUTPATIENT PHARMACY | 2003/08/11 | APPROVED | Active | Private | This call tells a subscribing package if a prescription has been designated as a Transitional Pharmacy Benefit prescription. |
PSOTPCUL | |||
| 4223 | DBIA4223 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52.91 | The Scheduling package looks at the 0 node of the TPB ELIGIBILITY file (#52.91) to see if an entry has already been created for a patient in that file. This is done so that on subsequent installs of patch PSO*7*145 (Phase I of the Transitional Pharmacy Benefit project), a patient is not flagged as potentially being automatically entered in that file by the Appointment and EWL logic, if a patient is already in the file from a previous install. This is done to prevent automatic changes to an entry that has already been manually edited. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 4275 | VDEF EVENTS AND EXTRACTION LISTS | Other | OUTPATIENT PHARMACY | 2004/08/23 | Retired | Supported | The following VDEF events are under the custody of OUTPATIENT PHARMACY: RDE^O11^PRES RDS^O13^PPAR RDS^O13^PREF The following VDEF extraction lists are under the custoday of OUTPATIENT PHARMACY: PID-0-PRES PV1-0-PRES PV2-0-PRES ORC-0-PRES RXE-0-PRES RXE-2-PRES-1 RXE-2-PRES-2 RXE-21-PRES-S-PI RXR-0-PRES-S-MR OBX-0-PRES-SVCCNCT OBX-0-PRES-MST OBX-0-PRES-AGENTORA OBX-0-PRES-RADEXP OBX-0-PRES-ENVCONT OBX-0-PRES-HNCA NTE-0-PRES-RE NTE-0-PRES-S-SIG1 NTE-3-PRES-S-SIG1 NTE-0-PRES-S-PC NTE-3-PRES-S-PC NTE-0-PRES-PAT NTE-0-PRES-S-PAT2 NTE-3-PRES-S-PAT2 Z14-0-PRES Z14-1-PRES Z14-11-PRES-S-SCHEDS Z15-0-PRES-S-REFILL Z16-0-PRES-S-PARTIAL Z17-0-PRES-S-MEDINSTRS Z18-0-PRES-S-LOTEXP |
|||||
| 4302 | DBIA4302 | File | OUTPATIENT PHARMACY | 2005/11/17 | Retired | Private | 52 | The Electronic Claims Management Engine (ECME) package requests direct read/write access to store the billed NDC in the Prescription file (#52). |
||||
| 4303 | DBIA4303 | File | OUTPATIENT PHARMACY | 2006/01/06 | Retired | Private | 59 | The Electronic Claims Management Engine (ECME) package requests read access to the Outpatient Site file (#59). |
||||
| 4304 | DBIA4304 | Routine | OUTPATIENT PHARMACY | 2003/12/03 | APPROVED | Active | Private | CMOP requests access to call Outpatient Pharmacy's function $$EN^PSONCPDP. |
PSONCPDP | |||
| 4470 | DBIA4470 | Routine | OUTPATIENT PHARMACY | 2005/12/29 | Withdrawn | Private | This DBIA will provide NON-VA Medication information from the NON-VA MEDS sub-file (#55.05) of the PHARMACY PATIENT File (#55) to the subscribing package. |
PSOMHV2 | ||||
| 4522 | 4522 | Routine | OUTPATIENT PHARMACY | 2004/11/02 | APPROVED | Active | Private | This routine and entry point is used for building the Clinical Reminders Index for the PRESCRIPTION file, #52. There are no required variables. |
PSOPXRMI | |||
| 4595 | DBIA4589-G | Other | OUTPATIENT PHARMACY | 2005/02/10 | APPROVED | Active | Controlled Subscription | The Health Revenue Center (HRC) will be using a special telnet feature in CAPRI-Remote. This allows a user to be automatically logged into the local VistA system and provides access to the site's regular VistA functionality. The HRC requires access to the menu options listed in this Integration Agreement in order to access various records for a given patient. HRC First Party Call Center contact representatives will use the HRC Pharmacy Menu [DVBA HRC MENU PHARMACY] option to handle calls from veterans related to the Consolidated Co-payment Processing Center (CCPC) billing statements. The menu option will be available through the CAPRI application, which provides local common service to VistA for HRC CAPRI remote users. Users of the HRC Pharmacy Menu [DVBA HRC MENU PHARMACY] option will typically be licensed and registered personnel (i.e. pharmacists and pharmacy technicians). NOTES ====================================================================== * The Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS] and Reset Copay Status List Manager [PSOCP RESET COPAY STATUS LM] options may be used to change the patients Copay. * Pharmacy Benefits Management endorses the addition of the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] to the HRC Pharmacy Menu [DVBA HRC MENU PHARMACY] menu option, with the understanding that HRC users will not use the option to alter existing Outpatient Pharmacy records. |
2010/07/27 | |||
| 4666 | DBIA4666 | Routine | OUTPATIENT PHARMACY | 2005/05/05 | APPROVED | Active | Private | CPRS requests permission to use the EN^PSOHLNE3 API to pass updated SC, EI, and ICD-9 Diagnosis information to Outpatient Pharmacy. When a verbal or telephone order is place and it requires electronic signature, the provider may update the SC, EI's, or ICD Diagnosis information. This API updates this information in Prescription file (#52). |
PSOHLNE3 | 2019/11/19 | ||
| 4687 | DBIA4687 | Routine | OUTPATIENT PHARMACY | 2005/06/22 | APPROVED | Active | Controlled Subscription | This agreement provides the calling program, details of all (active, verified, on hold, suspended, discontinued, pending and expired), prescriptions within a given date for a patient. It provides complete details of Rx(s) in a sorted order in a TMP global depending on the entry point being called EN, EN2 or EN3. The EN call sorts data by the Rx Status (TR) and the dispensed drug (TD). The EN2 call returns data for a specified Rx or list of Rxs sorted by the Rx Status (TR) and the dispensed drug (TD). The EN3 call sorts data by the Rx Status (TR) and the Rx IEN# (TD). Please see at the component level for more details. For all Rx except PENDING orders, the following details are included in the TMP global: ^TMP("PSO",$J,TR,TD,0)=DISPENSED DRUG^^RX EXPIRATION DATE^REFILLS REMAINING^ISSUE DATE^RX STATUS^DAYS SUPPLY^QUANTITY^^^PLACER ORDER #^LAST FILLED DATE^^ ^TMP("PSO",$J,TR,TD,"RXN",0)=EXTERNAL Rx NUMBER^LAST RELEASE DATE^ORIGINAL FILL ROUTING (W or M)^Remarks^FINISHED BY^ORIGINAL FILL DATE^ORIGINAL RELEASE DATE^^RX IEN# ^TMP("PSO",$J,TR,TD,"DIV",0)=DIVISION^OP DIVISION DETAILS ^TMP("PSO",$J,TR,TD,"P",0)=PROVIDER IEN^PROVIDER NAME ^TMP("PSO",$J,TR,TD,"REF",0)=# of refill dispensed ^TMP("PSO",$J,TR,TD,"REF",REF IEN#,0)=REFILL DATE^DAYS SUPPLY^QUANTITY^RELEASED DATE^ROUTING (M/W)^REMARKS ^TMP("PSO",$J,TR,TD,"PAR",0)=# of partials dispensed ^TMP("PSO",$J,TR,TD,"PAR",PAR IEN#,0)=PARTIAL DATE^DAYS SUPPLY^QUANTITY^RELEASED DATE^ROUTING (M/W)^REMARKS ^TMP("PSO",$J,TR,TD,"MDR",0)=# of MEDICATION ROUTES ^TMP("PSO",$J,TR,TD,"MDR",D1,0)=MEDICATION ROUTES ABBR. ^TMP("PSO",$J,TR,TD,"SCH",0)=# of schedule entries ^TMP("PSO",$J,TR,TD,"SCH",D1,0)=SCHEDULES ^TMP("PSO",$J,TR,TD,"SIG",0)=# of Sig entries ^TMP("PSO",$J,TR,TD,"SIG",D1,0)=SIG ^TMP("PSO",$J,TR,TD,"PC",0)=# of provider comment entries ^TMP("PSO",$J,TR,TD,"PC",D1,0)=PROVIDER COMMENTS ^TMP("PSO",$J,TR,TD,"DD",0)=1 ^TMP("PSO",$J,TR,TD,"DD",1,0)=DISPENSED DRUG IEN#^^ For Pending orders, the data is sorted by the DISPENSED DRUG (name)/PHARMACY ORDERABLE ITEM (name) (TD) and returns the following: ^TMP("PSO",$J,"PND",TD,0)=DISPENSED DRUG (if entered in CPRS)/NAME of the PHARMACY ORDERABLE ITEM concatenated with the NAME OF THE DOSAGE FORM^^MEDICATION ROUTE ABBR.^^# OF REFILLS^EFFECTIVE DATE^ORDER TYPE (PENDING/ONHOLD)^^QUANTITY^^PLACER NUMBER ^TMP("PSO",$J,"PND",TD,"SCH",0)= # of SCHEDULE ^TMP("PSO",$J,"PND",TD,"SCH",D1,0)=SCHEDULE ^TMP("PSO",$J,"PND",TD,"SIG",0)= # of SIG ^TMP("PSO",$J,"PND",TD,"SIG",D1,0)=SIG ^TMP("PSO",$J,"PND",TD,"SIO",0)= # of Lines ^TMP("PSO",$J,"PND",TD,"SIO",D1,0)=PROVIDER COMMENTS (packed to 80 characaters) ^TMP("PSO",$J,"PND",TD,"DD",0) = 1 ^TMP("PSO",$J,"PND",TD,"DD",1,0)=DISPENSED DRUG IEN# (if entered in CPRS)^^ |
PSOMHV1 | |||
| 4689 | DIC(59 | File | OUTPATIENT PHARMACY | 2007/04/20 | APPROVED | Active | Private | 59 | This DBIA allows the DSS EXTRACTS PACKAGE to do a direct read to a old global location to retrieve Outpatient Sites. This read is exempt from the Pharmacy encapsulation effort, since the current global location is different, and we are not encapsulating pre-V7.0 Outpatient Pharmacy direct reads. |
2007/04/22 | ||
| 4701 | PSOBPSUT | Routine | OUTPATIENT PHARMACY | 2005/06/27 | APPROVED | Active | Controlled Subscription | This routine contains apis used mainly by ePharmacy (Electronic Third Party Billing). |
PSOBPSUT | |||
| 4702 | PSOBPSU1 | Routine | OUTPATIENT PHARMACY | 2005/06/27 | APPROVED | Active | Controlled Subscription | This routine contains apis used mainly by ePharmacy (Electronic Third Party Billing). |
PSOBPSU1 | |||
| 4703 | DBIA4703 | File | OUTPATIENT PHARMACY | 2005/12/02 | Retired | Private | 52.5 | The ECME routines are accessing "B" x-ref and reading (#3) CMOP INDICATOR field to determine the Window/Mail/CMOP status of the RX. This agreement will be retired on 12/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 PSO*7*213. 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 1, 2006. |
||||
| 4705 | PSONDCUT | Routine | OUTPATIENT PHARMACY | 2005/06/27 | APPROVED | Active | Controlled Subscription | This routine contains apis for retrieving, editing and saving NDC in the PRESCRIPTION file (#52). |
PSONDCUT | |||
| 4706 | PSOREJUT | Routine | OUTPATIENT PHARMACY | 2005/06/27 | APPROVED | Active | Controlled Subscription | This routine contains APIs used for handling rejects from Third Party Payers that have clinical significance, such as DUR and REFILL TOO SOON rejects. These rejects are part of the ePharmacy project. Amendment: Effective 5/15/23, added Component CLSALL |
PSOREJUT | 2023/05/15 | ||
| 4711 | DBIA4711 | Routine | OUTPATIENT PHARMACY | 2005/06/27 | APPROVED | Active | Private | This call is needed to allow ECME to invoke View Prescription functionality provided by Outpatient Pharmacy package. This is needed to prevent users from having to exit one menu option and access another option. |
PSORXVW | |||
| 4732 | DBIA4732 | Routine | OUTPATIENT PHARMACY | 2005/07/15 | APPROVED | Active | Controlled Subscription | This agreement provides the Integration Billing (IB) package the following IENs for a given Prescription and Refill number that was released: 1. Pharmacist who released the prescription. 2. Initiator of Activity - last entry in the activity log with an INITIATOR OF ACTIVITY field (#.03) value defined. If none are found, default to the releasing pharmacist. Null values are not to be passed. 3. IB Service Section of the dispensing division from the OUTPATIENT SITE file (#59). The format is Pharmacist IEN^Last Activity Initiator IEN^IB Service Section IEN. If this API is called for unreleased prescriptions, null values will be returned for all fields. |
PSOPFSU0 | |||
| 4820 | PRESCRIPTION FILE (#52) DATA ELEMENTS | Routine | OUTPATIENT PHARMACY | 2005/12/07 | APPROVED | Active | Supported | The PSO52API routine shall be used to return requested data elements for the PRESCRIPTION file (#52). |
PSO52API | 2007/03/04 | ||
| 4821 | DBIA4821 | Routine | OUTPATIENT PHARMACY | 2005/12/07 | APPROVED | Active | Supported | The 'PEN' component returns data from the PENDING OUTPATIENT ORDERS (#52.41) File. The 'NONVA' component returns data from the NON-VA MEDS (#55.05) Subfile of the PHARMACY PATIENT (#55) File. |
PSO5241 | 2020/06/01 | ||
| 4822 | DBIA4822 | Routine | OUTPATIENT PHARMACY | 2005/12/07 | APPROVED | Active | Supported | The routine PSO525AP shall be used to return requested data elements for the RX SUSPENSE file (#52.5). Various data elements shall be returned by parameter passing. The following requirements shall describe what is passed in and what is returned. |
PSO525AP | |||
| 4823 | DBIA4823 | Routine | OUTPATIENT PHARMACY | 2005/12/07 | APPROVED | Active | Supported | This API shall return the following fields from the CLOZAPINE PRESCRIPTION OVERRIDES file (#52.52) for the IEN or free text entry received: DATE/TIME, PRESCRIPTION NUMBER, USER ENTERING, APPROVING TEAM MEMBER, REASON FOR LOCKOUT, and COMMENTS. |
PSO5252 | |||
| 4824 | DBIA4824 | Routine | OUTPATIENT PHARMACY | 2005/12/07 | APPROVED | Active | Supported | This API shall return the following fields from the TPB ELIGIBILITY file (#52.91) for the IEN or free text entry received: PATIENT, DATE PHARMACY BENEFITS BEGAN, INACTIVATION OF BENEFITS DATE, INACTIVATION REASON CODE, DESIRED APPOINTMENT DATE, WAIT TYPE, STATION NUMBER, INSTITUTION, EXCLUSION REASON, PRIMARY CARE SCHEDULED APPT DATE, RX#, and DATE LETTER PRINTED. |
PSO5291 | |||
| 4825 | DBIA4825 | Routine | OUTPATIENT PHARMACY | 2005/12/07 | APPROVED | Active | Supported | This API shall be provided to scan the NAME field (#.01) of RX PATIENT STATUS file (#53) utilizing the "B" cross-reference and return a listing of records for a specific value based on logical criteria received for the patient status. The following fields shall be included: NAME, ABBR, DAYS SUPPLY, REFILLS, RENEWABLE, SC/A&A/OTHER/INPATIENT/NVA, EXEMPT FROM COPAYMENT, and EXEMPT FROM CHAMPUS BILLING. |
PSO53 | |||
| 4827 | OUTPATIENT SITE FILE | Routine | OUTPATIENT PHARMACY | 2005/12/07 | APPROVED | Active | Supported | This API shall return the following fields from the OUTPATIENT SITE file (#59) for the IEN or free text entry received: NAME, MAILING FRANK STREET ADDRESS, AREA CODE, PHONE NUMBER, MAILING FRANK ZIP+4 CODE, SITE NUMBER, MAILING FRANK CITY, MAILING FRANK STATE, SITE DEA NUMBER, RELATED INSTITUTION, NPI INSTITUTION, IB SERVICE/SECTION and NCPDP NUMBER. |
PSO59 | 2011/02/16 | ||
| 4858 | DBIA 4858 | Routine | OUTPATIENT PHARMACY | 2006/05/15 | APPROVED | Active | Supported | This DBIA is provided by PSO (Outpatient Pharmacy) 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 the PRESCRIPTION file (#52) and the OUTPATIENT SITE file (#59) as all the Pharmacy packages are being re-engineered. |
PSODI | 2007/07/10 | ||
| 4902 | OBTAIN FILLS, REFILLS, PARTIAL FILLS FROM PRESCRIPTION FILE | Routine | OUTPATIENT PHARMACY | 2006/09/13 | APPROVED | Active | Supported | This ICR is provided by Outpatient Pharmacy as an API to extract information related to original prescription fills, refills, and partial fills. This API is to be used by all packages needing to retrieve data from the "AD", "AL", and "AM" cross references and the "STA" and "PARK" nodes in the PRESCRIPTION file (#52). |
PSO52EX | 2021/11/15 | ||
| 4910 | DBIA4910 | Routine | OUTPATIENT PHARMACY | 2006/09/29 | APPROVED | Active | Controlled Subscription | This agreement provides CMOP an entry point to determine if the patient has a known bad address and no active temporary address. |
PSOBAI | |||
| 4963 | DBIA4963 | File | OUTPATIENT PHARMACY | APPROVED | Active | Private | 59 | The NPI Extract needs to extract the NCPDP number from the OUTPATIENT SITE file (#59). This is a read-only action and does not modify any fields in the file. The NPI Extract also needs to use the NPI INSTITUTION field to get the correct NPI entry from file #4. |
2007/03/04 | |||
| 4970 | PSOBPSU2 | Routine | OUTPATIENT PHARMACY | 2007/01/22 | APPROVED | Active | Controlled Subscription | This routine contains Outpatient Pharmacy APIs related to the electronic billing of prescription claims (ePharmacy). |
PSOBPSU2 | 2007/03/15 | ||
| 5000 | Pointing to the PRESCRIPTION (#52) File | File | OUTPATIENT PHARMACY | 2007/06/05 | APPROVED | Active | Supported | 52 | This agreement allows for other applications to store a pointer to the Vista PRESCRIPTION (#52) file. This number can be used as an Identification Number to retrieve data. |
2007/06/20 | ||
| 5014 | Pointing to the OUTPATIENT SITE (#59) File | File | OUTPATIENT PHARMACY | 2007/07/11 | APPROVED | Active | Supported | 59 | This agreement allows for other applications to store a pointer to the Vista OUTPATIENT SITE (#59) file. This number can be used as an Identification Number to retrieve data. |
2007/07/12 | ||
| 5063 | PSOREJU4 | Routine | OUTPATIENT PHARMACY | 2007/12/14 | APPROVED | Active | Private | This routine contains APIs to be used by ECME package to pass Third Party Reject information to the Pharmacy Reject Worklist. |
PSOREJU4 | 2013/07/23 | ||
| 5065 | IA 5065 | Routine | OUTPATIENT PHARMACY | 2007/12/27 | Pending | Private | API to allow ECME to call the INLIST API to check for allowable reject codes that are allowed to be passed to the Pharmacy Reject Worklist manually by the OPECC. |
|||||
| 5186 | PSOREJU3 | Routine | OUTPATIENT PHARMACY | 2008/04/22 | APPROVED | Active | Private | This routine contains an API used by CMOP to validate ePharmacy third party Tricare insurance response information. |
PSOREJU3 | 2008/04/25 | ||
| 5188 | CLINICAL REMINDERS API | Routine | OUTPATIENT PHARMACY | 2008/04/24 | Pending | Private | This agreement gives the Clinical Reminders package APIs for extracting data from the Prescription (#52) file. |
PSO52CLR | ||||
| 5197 | TIU CALLS TO PSOQ0496 | Routine | OUTPATIENT PHARMACY | 2008/05/08 | APPROVED | Active | Private | TIU requests approval to make the following call to PSOQ0496. |
PSOQ0496 | 2008/05/08 | ||
| 5205 | PLACER ORDER # FOR CPRS | File | OUTPATIENT PHARMACY | 2008/05/29 | Expired | Private | 52 | This agreement gives the Computerized Patient Record System (CPRS) package access in patch OR*3*281 to directly read the PLACER ORDER # (#39.3) Field of the PRESCRIPTION (#52) File for a one-time clean-up. After the patch is released, this Integration Agreement will be retired. |
2008/06/16 | |||
| 5263 | Call to API UPDEXDT in routine PSOEXDT | Routine | OUTPATIENT PHARMACY | 2008/09/23 | APPROVED | Active | Private | Call to API UPDEXDT^PSOEXDT. This API updates the Expiration Date for the following scenarios: normal release of an Rx, return to stock or reinstate. Release update only occurs if the last refill is being released. |
PSOEXDT | 2008/10/01 | ||
| 5366 | PHARMACY ENHANCED ORDER CHECKS MED PROFILE BUILDER | Routine | OUTPATIENT PHARMACY | 2009/02/12 | APPROVED | Active | Controlled Subscription | This API is used currently by CPRS and Inpatient Meds to build med profile data for both IP meds and OP meds to return enhanced order checks by using the new interface by First Data Bank (FDB). |
PSODDPR4 | 2023/11/14 | ||
| 5427 | PSOSUCH1 | Routine | OUTPATIENT PHARMACY | 2009/04/07 | APPROVED | Active | Controlled Subscription | When an Rx is placed on 3/4 days supply hold for ePharamcy, CMOP updates the fill/refill date with the date that the Rx may be filled and calls CHANGE^PSOSUCH1 to update file 52.5 and all cross references. |
PSOSUCH1 | 2009/06/23 | ||
| 5505 | OUTPATIENT PHARMACY VDEF EVENTS | Other | OUTPATIENT PHARMACY | 2009/11/02 | APPROVED | Active | Private | Outpatient Pharmacy provides access to the subscribing package to use the following protocols: PSO VDEF RDE O11 OP PHARM PRES VS PSO VDEF RDS O13 OP PHARM PPAR VS PSO VDEF RDS O13 OP PHARM PREF VS |
2009/10/30 | |||
| 5579 | OPAI ACCESS TO 52.53 | File | OUTPATIENT PHARMACY | 2010/11/18 | APPROVED | Active | Private | 52.53 | This ICR grants access to the automated dispensing devices defined in the PHARMACY AUTOMATED DISPENSING DEVICES file (#52.53). |
2010/11/22 | ||
| 5720 | WITHDRAWN | OUTPATIENT PHARMACY | 2011/09/01 | Withdrawn | ||||||||
| 5740 | PSOFDAUT | Routine | OUTPATIENT PHARMACY | 2011/10/31 | APPROVED | Active | Private | This Outpatient Pharmacy utility routine contains APIs related to the printing of FDA Medication Guides. |
PSOFDAUT | 2012/03/07 | ||
| 5760 | EXCEPTIONS DISPLAYED | Routine | OUTPATIENT PHARMACY | 2012/01/04 | Pending | Controlled Subscription | PSODDPR5 | |||||
| 5761 | DISPLAY ORDER CHECKS RETURNED | Routine | OUTPATIENT PHARMACY | 2012/01/04 | Withdrawn | Controlled Subscription | PSODDPR2 | |||||
| 5764 | PSODGAL1 | Routine | OUTPATIENT PHARMACY | 2012/01/12 | APPROVED | Active | Private | This API displays drug allergy order checks. |
PSODGAL1 | 2012/04/11 | ||
| 5765 | ENTERED IN ERROR | Routine | OUTPATIENT PHARMACY | 2012/01/31 | Pending | Controlled Subscription | ||||||
| 5784 | DBIA 5784 Duplicate Supply Check | Routine | OUTPATIENT PHARMACY | 2012/03/27 | APPROVED | Active | Private | The DBIA documents the API that CPRS can call to do a duplicate Supply check against a patient's profile for orders being entered through the Pharmacy dialogues in CPRS. |
PSODDPR8 | 2012/10/02 | ||
| 5912 | PSOREJP2 | Routine | OUTPATIENT PHARMACY | 2013/05/09 | APPROVED | Active | Private | Retrieve the most recent last date of service and last days supply from the previous prescription. |
PSOREJP2 | 2013/07/23 | ||
| 6036 | National Utility Clean-up | Routine | OUTPATIENT PHARMACY | 2014/04/02 | Withdrawn | Private | This agreement describes the call made from Computerized Patient Record System (CPRS) to Outpatient Pharmacy as part of a combined build that contains patches OR*3.0*378 and PSO*7.0*433. |
PSOUT433 | ||||
| 6070 | Pending Outpatient Orders Lookup | File | OUTPATIENT PHARMACY | 2014/07/09 | APPROVED | Active | Private | 52.41 | Inpatient Pharmacy allergy order checks need to include all prescription ordering processes. Inpatient Medications requests direct global read access to the following pharmacy file: ^PS(52.41, - PENDING OUTPATIENT ORDERS FILE (#52.41) Node 0, piece 8 - PHARMACY ORDERABLE ITEM FIELD (#8) Node 0, piece 9 - DRUG FIELD (#9) |
2014/09/04 | ||
| 6071 | Outpatient Pharmacy Allergy | File | OUTPATIENT PHARMACY | 2014/07/09 | Pending | Private | This global is used to return the data from a call to DAOC^PSONEWOA. It contains data split into drug classes, drug ingredients and pharmacy interventions. Inpatient Medications must access Outpatient Pharmacy namespaced ^TMP global to perform allergy order checks. This global is generated by an Inpatient Medications process calling an Outpatient routine. Inpatient Medications requests direct global Read/Write access to the following pharmacy ^TMP file: ^TMP("PSODAOC",$J,"ALLERGY",) - Outpatient Pharmacy Allergy Data Inpatient Meds kills the TMP global before and after the call to the Outpatient Pharmacy API. VARIABLES: Input TMP GLOBAL Nodes descendant from ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT) are stored. ROUTINE: PSONEWOA COMPONENT: DAOC INPUT: ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT)=List of allergy order checks ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT,"ALLERGY DD")=DRUG File IEN ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT,"ALLERGY PKG")="IP" Hard Set ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT,"INTERVENTION")=APSP INTERVENTION File IEN ^TMP("PSODAOC",$J,"ALLERGY","ALLERGY PKG") $P1 = "IP" Hard Set $P2 = Process ID i.e., "COPY IV","RENEW UD" $P3 = Prescription Order Number $P4 = ORDER File IEN ^TMP("PSODAOC",$J,"ALLERGY","PROVR")= Provider Override Reason |
|||||
| 6072 | Allergy Order Check Filing | Routine | OUTPATIENT PHARMACY | 2014/07/09 | APPROVED | Active | Private | This DBIA provides the DAOC^PSONEWOA routine call for Inpatient Medications to make to Outpatient Pharmacy. It takes the ^TMP global input data sent in from Inpatient Medications that contains allergy order check data and creates an entry in the ORDER CHECK INSTANCES File (#100.05), by invoking SAVEOC^OROCAPI1. |
PSONEWOA | 2017/11/14 | ||
| 6074 | Stored Order Check Display | OUTPATIENT PHARMACY | Private | |||||||||
| 6075 | Pharmacy Order Check Display | Routine | OUTPATIENT PHARMACY | 2014/07/14 | APPROVED | Active | Private | This is an internal Pharmacy API used to display stored pharmacy order checks. |
PSOOCKV1 | 2014/07/25 | ||
| 6148 | VPS READ OF 52.41 | File | OUTPATIENT PHARMACY | 2015/01/26 | APPROVED | Active | Controlled Subscription | 52.41 | This IA provides for the Fileman read of the PLACER NUMBER, ORDER TYPE, # OF REFILLS, REASON ORDER CREATED, PATIENT of the PENDING OUTPATIENT ORDERS FILE #52.41, CONJUNCTION, UNITS fields of the QUANTITY TIMING SUB-FILE subfile #52.413 of the PENDING OUTPATIENT ORDERS file #52.41, and the DISPENSING INSTRUCTIONS field of the DISPENSING INSTRUCTIONS subfile #52.4124 in the PENDING OUTPATIENT ORDERS file #52.41. |
2015/03/19 | ||
| 6149 | VPS READ OF 52 | File | OUTPATIENT PHARMACY | 2015/01/26 | APPROVED | Active | Controlled Subscription | 52 | This IA provides for the Fileman read of the RX #, PLACER ORDER #, STATUS, NDC, # OF REFILLS, REMARKS, RELEASED DATE/TIME, PREVIOUS ORDER #, FORWARD ORDER # fields in the PRESCRIPTION file #52. |
2015/03/11 | ||
| 6151 | VPS READ OF 52.4124 | File | OUTPATIENT PHARMACY | 2015/01/26 | APPROVED | Withdrawn | Controlled Subscription | 52.41 | This IA provides for the Fileman read of the DISPENSING INSTRUCTIONS field in the DISPENSING INSTRUCTIONS sub-file #52.4124. |
2015/03/06 | ||
| 6156 | PSOTRI | Routine | OUTPATIENT PHARMACY | 2015/01/28 | APPROVED | Active | Private | The ECME application requires the ability to create entries in the PSO Audit Log (#52.87) file by using the AUDIT^PSOTRI entry point that is already used internally by the Outpatient Pharmacy package. |
PSOTRI | 2015/02/02 | ||
| 6227 | OUTPATIENT PHARMACY REJECT COMMENTS | Routine | OUTPATIENT PHARMACY | 2015/09/11 | APPROVED | Active | Private | This is an API to allow the Pharmacist comments entered and stored in Outpatient Pharmacy to be shared with the subscribing package. These are pharmacist comments pertaining to ePharmacy rejections received and the pharmacist comments about those rejections. |
PSOREJU4 | 2016/02/12 | ||
| 6228 | MEDICATION PROFILE/PATIENT INFORMATION LIST MANAGER | Routine | OUTPATIENT PHARMACY | 2015/09/14 | APPROVED | Active | Private | This is an Integration Agreement between Outpatient Pharmacy and ECME. The Chief Business Office eBusiness Solutions ePharmacy team requests the ability for the Outpatient Pharmacy Electronic Claims Coordinator (OPECC) using the ECME User Screen to be able to view both the Outpatient Pharmacy Medication Profile List Manager screen and the Outpatient Pharmacy Patient Information List Manager screen. This agreement allows ECME to call these PSO API entry points to display these List Manager screens. |
PSOREJU4 | 2016/02/12 | ||
| 6719 | OE/RR CALL TO PSOORCPY | Routine | OUTPATIENT PHARMACY | 2017/01/11 | APPROVED | Active | Private | The Order Entry/Results Reporting would like approval to call the extrinsic function $$ORCOPY^PSOORCPY(Placer). |
PSOORCPY | 2017/07/10 | ||
| 6749 | REJECT INFORMATION | Routine | OUTPATIENT PHARMACY | 2017/03/22 | APPROVED | Active | Controlled Subscription | Pull and return reject information from subfile 52.25. |
PSOREJU2 | 2017/04/10 | ||
| 6763 | ELIGIBILITY | Routine | OUTPATIENT PHARMACY | 2017/05/19 | APPROVED | Active | Controlled Subscription | APIs in PSOREJP1 concern third-party payer information. |
PSOREJP1 | 2017/08/02 | ||
| 6863 | PSO Medication Profile | Routine | OUTPATIENT PHARMACY | 2018/01/16 | APPROVED | Active | Private | Allow ECME routine to access Medication Profile information from Outpatient Pharmacy. |
PSOPMP0 | 2018/02/05 | ||
| 6907 | IB FM ACCESS TO PSRX FOR SHRPE | File | OUTPATIENT PHARMACY | 2018/04/10 | Withdrawn | Controlled Subscription | 52 | Read w/Fileman |
||||
| 6980 | TITRATION API | Routine | OUTPATIENT PHARMACY | 2018/10/23 | APPROVED | Active | Controlled Subscription | PSOUTL | 2019/02/11 | |||
| 6996 | File 52 | File | OUTPATIENT PHARMACY | 2018/12/01 | Pending | Private | 52 | This is the replacement agreement for DBIA #824. It gives permission to read various fields in the PRESCRIPTION File (#52). |
||||
| 6997 | File 53 | File | OUTPATIENT PHARMACY | 2018/12/01 | Pending | Controlled Subscription | 53 | This is the replacement agreement for DBIA 1975. It gives permission to read various fields in the RX PATIENT STATUS File (#53). |
||||
| 6998 | File 59 | File | OUTPATIENT PHARMACY | 2018/12/01 | Pending | Controlled Subscription | 59 | This is the replacement agreement for DBIA 1976. It gives permission for other packages to directly read and read with FileMan all fields in the OUTPATIENT SITE File (#59). |
||||
| 6999 | File 59 | File | OUTPATIENT PHARMACY | 2018/12/01 | Pending | Private | 59 | This is the replacement agreement for DBIA #2621. It gives permission to read various fields in the OUTPATIENT SITE File (#59). |
||||
| 7084 | Electronically Billable Indicator | Routine | OUTPATIENT PHARMACY | 2019/06/05 | APPROVED | Active | Private | The $$ECME^PSOBPSUT call returns one of two values. An 'e' is returned if the last fill of the prescription is electronically billable, else null is returned. |
PSOBPSUT | 2019/06/06 | ||
| 7123 | PSOCLO1 | Routine | OUTPATIENT PHARMACY | 2020/01/08 | APPROVED | Active | Private | This routine performs Clozapine Order checks. It also grants permission to dispense a clozapine marked drug to an eligible clozapine patient. |
PSOCLO1 | 2020/01/24 | ||
| 7175 | YSCL UPDATE PHARMACY PATIENT CLOZAPINE | Routine | OUTPATIENT PHARMACY | 2020/05/13 | APPROVED | Active | Private | Mental Health (YS) Clozapine software invokes Outpatient Pharmacy (PSO) API to update the CLOZAPINE REGISTRATION NUMBER field (#53) and the CLOZAPINE STATUS field (#54) in the PHARMACY PATIENT file (#55) when a new entry is filed in the CLOZAPINE PATIENT LIST file (#603.01) via a database trigger x-ref. |
PSOCLADD | 2020/06/16 | ||
| 7207 | CLOZAPINE OVERRIDES | File | OUTPATIENT PHARMACY | 2020/10/21 | Pending | Private | 52.52 | The MENTAL HEALTH (YS) Clozapine module has a need to read the SECOND APPROVING TEAM MEMBER field (#6) in the CLOZAPINE PRESCRIPTION OVERRIDES file (#52.52) via FileMan. The MENTAL HEALTH (YS) package formerly had access to the file via expired ICR DBIA273-D, which was replaced by Pharmacy Data Management API PSO5252. The PSO5252 API does not include this field. When the field becomes available via Pharmacy API, the FileMan reference should be converted to API call and this ICR should be retired. |
||||
| 7212 | PSOBPSU4 | Routine | OUTPATIENT PHARMACY | 2020/12/07 | APPROVED | Active | Controlled Subscription | This routine contains a subroutine associated with the Bypass 3/4 Day Supply Logic flags in the Prescription file (52) and the Refill subfile (52.1) of the Prescription file (52). |
PSOBPSU4 | 2021/05/05 | ||
| 7213 | PSOSULB2 | Routine | OUTPATIENT PHARMACY | 2020/12/30 | APPROVED | Active | Controlled Subscription | This routine contains a function, $$EBILLABLE, which checks whether a prescription is ebillable (i.e. can be electronically billed to a third party payer). |
PSOSULB2 | 2021/01/04 | ||
| 7222 | PSOERXU9 | Routine | OUTPATIENT PHARMACY | 2021/02/02 | APPROVED | Active | Private | The routine PSOERXU9 has entry points to return a pointer to the ERX HOLDING QUEUE file (#52.49) based on a PRESCRIPTION IEN or PENDING OUTPATIENT ORDER IEN, return a pointer to the ERX HOLDING QUEUE file (#52.49) based on an ORDER IEN, and return data from the ERX HOLDING QUEUE file (#52.49) based on the ERX HOLDING QUEUE IEN. |
PSOERXU9 | 2021/02/16 | ||
| 7227 | PSOSIG | Routine | OUTPATIENT PHARMACY | 2021/02/12 | APPROVED | Active | Private | This call, provided by Outpatient Pharmacy, will return the expanded version of an ADMINISTRATION SCHEDULE. For example, a schedule of BID will return TWICE A DAY or a schedule TU will return TUESDAY. |
PSOSIG | 2021/06/07 | ||
| 7262 | PROVIDER CLASS (#53.5) field in the NEW PERSON (#200) file | File | OUTPATIENT PHARMACY | 2021/05/15 | APPROVED | Active | Controlled Subscription | 200 | The Home Based Primary Care (HBPC - formerly known as Hospital Based Home Care) package displays the PROVIDER CLASS (#53.5) field from the NEW PERSON (#200) file in the option "Provider File Data Entry". The display aids users in ensuring the correct entry is being added as a provider for HBPC. |
2021/06/08 | ||
| 7279 | XU EPCS ADD DEA | Remote Procedure | OUTPATIENT PHARMACY | 2021/08/17 | Pending | Controlled Subscription | TESTING |
XU EPCS ADD DEA | ||||
| 7313 | PSO VCC REFILL | Remote Procedure | OUTPATIENT PHARMACY | 2021/11/09 | APPROVED | Active | Controlled Subscription | The purpose of this agreement is to provide Outpatient Medication Prescription Refill support for client systems such as the Veteran Contact Center (VCC). The PSO VCC REFILL remote procedure was delivered originally with patch PSO*7*642, and has been modified, effective with PSO*7*679, to include the REFILL SOURCE from which the REFILL request originated (e.g., VCC, and VSE). This modified RPC will support new functionality in Scheduling and Lighthouse package. CHIP web services will be exposing the refill RPC as an endpoint for use by the VistA Scheduling Enhancements (VSE) GUI for Clinical Staff. Patch PSO*7*679 will support that implementation. PSO VCC REFILL remote procedure capture: The RPC: PSO VCC REFILL performs a refill on an outpatient pharmacy order request. In addition, the RPC will provide the ability in Outpatient Pharmacy to store the source of a refill request (eg. VCC, Computerized Patient Record System (CPRS), Outpatient Pharmacy) as well as the person making the request - if the name is known. OUTPUT: ARRAY Depending on the value of the Return Flag input parameter, either a single code is returned or a code and free text description of the code. When the Return Flag input parameter equals 1, then the code and text description will be returned. Exception condition when attempting to refill the prescription: ARRAY(0)=0 ARRAY(1)=error text on why the prescription was not filled The following is an example of one of several types of exceptions that could be returned: ARRAY(0)=0 ARRAY(1)=" Cannot refill Rx # 2769331 Rx is in SUSPENDED status" Successful refill: ARRAY(0)="1 - Prescription successfully refilled" Data validation error which will be one of the following: ARRAY(0)="-3 - Missing or Invalid Prescription Number" ARRAY(0)="-4 - Missing or Invalid Patient ID" ARRAY(0)="-5 - Prescription Number does not match to the Patient" ARRAY(0)="-6 - Patient is not assigned an ICN" (note: code -6 will only be generated when the RETURN FLAG is equal 1) When the Return Flag is equal null, then only the code will be returned. Exception condition when attempting to refill the prescription: ARRAY(0)=0 Successful refill: ARRAY(0)=1 Data Validation error which will be one of the following: ARRAY(0)=-3 ARRAY(0)=-4 ARRAY(0)=-5 INPUT: DFN [REQUIRED] - Internal Entry Number of the patient record for the PATIENT file (#2) RX# [REQUIRED] - the external representation of the prescription number from the PRESCRIPTION file (#52,.01). USER[OPTIONAL] - USER requesting the refill (free text value) REFILL SOURCE [OPTIONAL] - the source system from which the REFILL request Originated (e.g., VCC, VSE CS, AUDIOCARE). If this value is not sent by the client, the REFILL SOURCE will be reported as "UNKNOWN". RETURN FLAG [OPTIONAL] - Value will be 1 or null. If = 1 then the RPC will return the numeric code with text describing the code. If = null then the RPC will only return the numeric code (-5, -4, -3, 0, 1) |
PSO VCC REFILL | 2022/07/07 | ||
| 7314 | PSOCLUTL | Routine | OUTPATIENT PHARMACY | 2021/11/24 | APPROVED | Active | Private | The Mental Health package needs to call $$GETREGYS^PSOCLUTL(DFN) to get use frequency from registered cloz auth number, otherwise most recently assigned cloz number. The Mental Health routine, YSCLTST2, was released in May 2020, effective with YS*5.01*166. This is an after-the-fact ICR documentation. |
PSOCLUTL | 2021/11/26 | ||
| 7329 | OUTPATIENT PHARMACY MEDICATION RECONCILIATION | File | OUTPATIENT PHARMACY | 2022/03/14 | Active | Controlled Subscription | 52 | This ICR is to support the medication reconciliation feature in COMPREHENSIVE CARE COORDINATION. Reading from file 52 will allow COMPREHENSIVE CARE COORDINATION to display order details for verified outpatient orders. |
2022/04/07 | |||
| 7412 | PSO VDEF RDS O13 OP PHARM PPAR VS | Other | OUTPATIENT PHARMACY | 2023/01/18 | APPROVED | Active | Private | The PSO VDEF RDS O13 OP PHARM PPAR VS protocol is used to send HL7 messages to the Health Data Repository (HDR). See the Outpatient Pharmacy Technical Manual for message specifications. This documents the protocols allowed to subscribe to this event. Supported HL7 utilities may be used to read the attached message; the message itself and HL7 application variables may not be altered. |
2023/01/23 | |||
| 7413 | PSO VDEF RDS O13 OP PHARM PREF VS | Other | OUTPATIENT PHARMACY | 2023/01/18 | APPROVED | Active | Private | The PSO VDEF RDS O13 OP PHARM PREF VS protocol is used to send HL7 messages to the Health Data Repository (HDR). See the Outpatient Pharmacy Technical Manual for message specifications. This documents the protocols allowed to subscribe to this event. Supported HL7 utilities may be used to read the attached message; the message itself and HL7 application variables may not be altered. |
2023/01/23 | |||
| 7428 | PSOPRKA | Routine | OUTPATIENT PHARMACY | 2023/06/07 | APPROVED | Active | Private | ORDER ENTRY/RESULTS REPORTING (OE/RR) is allowed to utilize the UNPARK^PSOPRKA api in order to complete the unparking of a prescription functionality introduced with CPRSv32B and the following patch of PSO*7*712 which will make it available for activation. |
PSOPRKA | 2023/10/16 | ||
| 7492 | PSO EPCS PSDRPH FILER | Remote Procedure | OUTPATIENT PHARMACY | 2024/09/09 | APPROVED | Active | Private | The Web Veteran's Health Information Systems and Technology Architecture (VistA) Remote Access Management (WebVRAM) application requires a Remote Procedure Call (RPC) that allocates and deallocates the PSDRPH key to a specific user and logs the event in the XUEPCS PSDRPH AUDIT file (#8991.7). The PSO EPCS PSDRPH FILER RPC has been created to allocate and de-allocate and audit the assignment/unassignment of the PSDRPH key. Remote Procedure: PSO EPCS PSDRPH FILER --------------------------------------- ROUTINE: PSOEPUT2 COMPONENT: PSDKEY DESCRIPTION: The PSDKEY entry point is invoked by the PSO EPCS PSDRPH FILER Remote Procedure Call (RPC) to perform allocation and deallocation of the PSDRPH key, and log the event in the XUEPCS PSDRPH AUDIT file (#8991.7). VARIABLES: PSOSUBJ (Input) The NEW PERSON (#200) file Internal Entry Number (IEN) of the user to whom the PSDRPH key is being allocated or deallocated. VARIABLES: PSOACTOR (Input) The NEW PERSON (#200) file Internal Entry Number (IEN) of the user performing the allocation or deallocation of the PSDRPH key. VARIABLES: PSOACTION (Input) A flag indicating the type of action to be taken, either "A" to allocate the PSDRPH key, or "D" to deallocate the PSDRPH key. VARIABLES: RESULTS (Output) The return value is 1 if the allocation or deallocation was successful. The return value is 0^Error Message Text if the allocation or deallocation was unsuccessful. Revision History - 10/16/24 The WebVRAM and Outpatient Pharmacy development teams are working together on the release of the RPC and the WebVRAM GUI changes to invoke the RPC. The Pharmacy patch is PSO*7*732 and the WEBG patch is WEBG*3*21. The ICR that authorizes Pharmacy's reference to file 8991.7 is #7016. This RPC performs the same function as the Allocate/De-Allocate of PSDRPH Key (Audited) [PSO EPCS PSDRPH KEY]. WebVRAM's subscription to ICR 7016 is valid only as long as ICR 7492 is active. |
PSOEPUT2 | 2024/10/16 | ||
| 7527 | PSO MED ORDER PROFILE FOR PGX SUPPRESSION | Routine | OUTPATIENT PHARMACY | 2025/03/19 | APPROVED | Active | Private | Builds a profile of an Outpatient's medication orders to be used for PGx Order Checks suppression logic. |
PSOOCPGX | 2025/04/21 | ||
| 7533 | VCRS | File | OUTPATIENT PHARMACY | 2025/03/31 | Pending | Private | 59 | VDIF API call to retrive all field data from outpatient site file 59 |
||||
| 7548 | Field # 100.2 Mail Exemption | File | OUTPATIENT PHARMACY | 2025/04/25 | APPROVED | Active | Private | 52 | Read FM for PRESCRIPTION (#52) FILE Mail Exemption FIELD 100.2 |
2025/04/25 | ||
| 7581 | PSORPC | Remote Procedure | OUTPATIENT PHARMACY | 2025/08/28 | Active | Private | This RPC evaluates the passed option parameter to take the associated action on a given prescription or drug. RPC^PSORPC01(RESULTS,OPTION,P1,P2,P3,P4,P5,P6) RESULTS: Indicates if the option is allowable on the order or drug. OPTION: PARK, UNPARK, PARKDRG, PARKORD P1: IEN of Order or Drug P2: Pickup value (Mail, Clinic, Window) P3: Patient DFN P4: Encounter provider P5: Encounter location P6: <reserved> PARK: Place this prescription in a Parked state. UNPARK: Remove this prescription from a Parked state. PARKDRG: Check if this drug is unable to be Parked. PARKORD: Check if the drug associated with a supplied order number is unable to be Parked. PSORPC was introduced via PSO*7.0*441 as part of the CPRS GUI v32b combined build, CPRS_V32B_COMBINED_BUILD_1_0.KID. At this time, PSORPC was added to the OR CPRS GUI CHART context option. The need for this ICR was discovered during ICR review of the OR CPRS GUI CHART context option for CPRS GUI v33CON, OR*3.0*508. |
PSORPC | PSORPC01 |