| 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 |
| 54 | DBIA54 | Other | ACCOUNTS RECEIVABLE | 1990/07/05 | APPROVED | Active | Private | MAS version 4.7 will be exporting the following: Routine PRCASVC3 FILE 430.4 AR BILL NUMBER FILE wit input template PRCAF COMMON SERIES Following options make the indicated forgien calls: OPTION ACTION DGCR FILLING SUPERVISOR MENU calls COUNT^PRCAUT2 DGCR BILLING CLERK MENU calls COUNT^PRCAUT2 DGCR RETURNED BILL LIST calls RETN^PRCALST DGCR CANCEL BILL calls CANCEL^PRCASVC1 Return of edited bill calls REL^PRCASVC |
||||
| 127 | DBIA127-A | Routine | ACCOUNTS RECEIVABLE | 1991/11/06 | APPROVED | Active | Private |
PRCASER This routine is used for setting up or establishing a new charge (bill) for a debtor. When calling this routine, a new charge (pharmacy Co-Pay, etc, should be added to the patients account. Input Variable: X $P1: Site. This is the site number the charge is being created by. For example: 503, 516, etc. This is the station number field from the Institution file (4). $P2: Service. This is the service that is creating the bill. This is the pointer to the Service/Section file (49). $P3: Category Number. This is the AR Category that the charge should fall under. This is the pter to the AR Category file (430.2). $P4: Debtor. This is the debtor that the charge should fall under. This is a variable pointer to the following files: Vendor, Person, Insurance, Institution. For Pharmacy Co-Pay the debtor should be the patient in the format of "36;DPT(" whe re 36 is the internal number of the patient in the patient file. $P5: Fiscal Year. Fiscal Year charge should be charged to. $P6: Amount. Must be zero or greater and less than 9999999.99. $P7: User. The person who created the charge. Pointer to the User file (3). $P8: Date charge generated. This is the internal VA FileMan date the charge was issued. Output Variable: Y (if no error is encountered) P1: Internal Bill Number. This is the internal file number from the Accounts Receivable file (430). $P2: Charge ID. This is the .01 field from the Accounts Receivable file (430) and will be 10 characters in length. $P3: Transaction Number. Since an "OPEN" bill may already exist and can be used, it may be necessary to add this charge to an already existing bill as a transaction, then this would be the pointer value to the AR Transaction file (433). Howev er, if a new bill is set up for the current charges then this piece equals zero. Variable: Y (if error is encountered) $P1: Error Indicator. -1 . $P2: Error Code. This is the error code from the IB Action Error file. $P3: Additional Text. If additional text is required to describe the error it is in the third piece. |
PRCASER | |||
| 193 | DBIA193 | Routine | ACCOUNTS RECEIVABLE | 1992/09/15 | APPROVED | Active | Private | To activate the data extraction process of the Accounts Receivable package, the MCCR National Database - Field Component, using indirection, will issue the following call using parameter passing: D EN1^PRCANRU(PRQDAT,PRQSTR,PRQIDN,.PRQERR) Where: PRQDAT is a pieced variable, with ^ as the piece delimiter, as follows: site number ^ batch number ^ from date ^ to date PRQSTR is a variable which defines a global root where the package extraction routine will place the data according to the format below. PRQIDN is a unique identifier number PRQERR is an error flag which will be set to "1 DATA COLLECTION ABORTED". The extract routine must reset this variable so it evaluates to zero as an indicator that the extraction process ran to completion. Data is stored using the global root as follows: PRQSTR_","_criteria#1_"-"_criteria#2)=#count^$amount for example: ^TMP("PRQ","2020D611","1-1")=50^25000 The actual line of code in the MCCR National Database - Field Component will appear as: D @(extractor entry point) D DRIVER^PRQSD. Finally, the code for invoking the routine will exist as an entry in the MCCR Collections Routine file. The AR package may directly enter an extractor routine into the MCCR Collection Routines file (file #466), as part of its installation procedure. The entry must include routine name and status, and proper cross-references for these two fields. The routine name should include a "#" character to indicate the proper position of the "^". Status may be either active or inactive. Inactive extractors will not be invoked by the MCCR National Database software. The following extractor will be entered during installation of the MCCR National Database - Field Component: EN1#PRCANRU(PRQDAT,PRQSTR,PRQIDN,.PRQERR). This entry may be modified, or other entries added, in subsequent AR releases with prior notification to, and concurrence of, the San Francisco ISC. |
PRCANRU | |||
| 283 | DBIA283 | Other | ACCOUNTS RECEIVABLE | 1993/10/05 | APPROVED | Active | Private | The Electronic Signature encode created for IFCAP V4.0 for the Electronic Signature codes will work with AR V3.7 code sheet creator without having to modifiy any AR routines. The exception to the above is, the 'Forward IRS Offsets to Austin' option in the AR package. This option is used thru the 15th - 21st days of the month. Since this option generates code sheets in the background AR uses the PRCAOFF2 routine to create code sheets. This one routine is not compatible with IFCAP V4.0 AR plans to create a patch (not to be released till IFCAP V4.0 is released) to include the change. This patch was forwarded to the IFCAP V4.0 test sites and were considered as test sites for the AR patch. Since the sites have until the 21st of the month to send the IRS code sheets, this patch should not delay the implementation plans for IFCAP V4.0. The patch number is PRCA*3.7*17 IFCAP version 4 will export this routine in the IFCAP namespace as routine PRC4OFF2 and renamed back to PRCAOFF2 during the pre- initialization routine. |
||||
| 284 | DBIA284 | File | ACCOUNTS RECEIVABLE | 1993/10/05 | APPROVED | Active | Private | 340 | Data Dictionary integration - IFCAP calls to AR IFCAP FILES FIELD - RELATION TO IFCAP CALM/LOG Code Sheet File 423 VA IDENT NO. Field 1005.17 (1005;17) - points to the AR Debtor File (#340) Procurement & Accounting Transaction File 442 Debtor Field 5.1 (1;16) - points to the AR Debtor File 340 Purchase Order Number Field .01 (0;1) - Executable Help checks for AR variable $D(PRCAREF) |
|||
| 380 | DBIA380 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | The following function calls are made to the routine PRCAFN. The input X for each call is the internal entry number of an entry in the BILL/CLAIMS (#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430) file. Each function will return -1 if a legitimate value cannot be returned. Also note that these functions only work for categories of receivables which are not PATIENT or MEANS TEST PATIENT (except for the PST, PUR, and CATN functions). |
PRCAFN(X) | |||
| 381 | DBIA381 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | This Accounts Receivable routine is the entry point for the Returned Bill List output. The routine is invoked by the Integrated Billing option IB RETURN BILL LIST. |
PRCALST | |||
| 382 | DBIA382 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | This routine call displays the number of bills that have been returned to the service from Fiscal. There is no variable input required to make the call. This routine is invoked as an Entry Action of the following Integrated Billing menu options: IB BILLING CLERK MENU IB BILLING SUPERVISOR MENU IB RETURN BILL MENU |
PRCAUT2 | |||
| 383 | DBIA383 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | This call is used in Pharmacy copay exemption processing to cancel Pharmacy copay charges who become exempt from copay. |
PRCAX(DFN,BEG,END,.ERR) | |||
| 384 | DBIA384 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | This call is made just prior to passing a claim to the Accounts Receivable package. This routine call performs a check on all data required to establish a receivable and passes errors back to Integrated Billing. |
PRCASVC6 | |||
| 385 | DBIA385 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | This call is used to pass a new or returned bill to the Accounts Receivable package. This call is made right after the call D ^PRCASVC6, if that call returns PRCASV("OKAY") as a positive number. |
PRCASVC | |||
| 386 | DBIA386 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | This call sets up a stub receivable in Accounts Receivable. The internal entry number for the receivable is used as the internal entry number of the bill in the BILL/CLAIMS (#399) file. |
PRCASVC3 | 2010/08/06 | ||
| 387 | DBIA387 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | These calls are made when a bill is cancelled in Integrated Billing. If the receivable has the AR Status of New Bill, Bill Incomplete, or Returned From AR (NEW), the bill is cancelled using the call D CANCEL^PRCASVC1; otherwise, the bill is amended using the call D AMEND^PRCASVC1. |
PRCASVC1 | |||
| 388 | DBIA388 | Routine | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | This call is used to find the internal entry number for a bill in file #430, so it may be used as input to the function $$PUR^PRCAFN(X). Note that a check is done to determine if the routine RCFN03 exists on the system before the call is made. |
RCFNO3(X) | |||
| 389 | DBIA389 | File | ACCOUNTS RECEIVABLE | 1994/03/15 | APPROVED | Active | Private | 430 | Integrated Billing has permission to reference this file in a ^DIC call to do a look-up on the bill number. It also has permission to access the following fields and cross-references: Revision History: 11/22/24 - Added CURRENT STATUS Field (#8) to ^PRCA(430,BN,0) Global Reference for Automated Community Claims (ACC) project for use in IB*2.0*770. |
|||
| 1105 | DBIA1105 | File | ACCOUNTS RECEIVABLE | 1995/01/06 | Withdrawn | Private | 423.5 | This file contains a listing of the transactions that can be handled by the PRCOISM IFCAP server. This file also contains the mailgroup that will receive any transaction processing error message and the entry point (TAG^ROUTINE) for each different transaction processing. It contains only four fields: TRANSACTION CODE, MAILGROUP, TAG and ROUTINE. |
||||
| 1277 | DBIA1277 | Routine | ACCOUNTS RECEIVABLE | 1995/06/01 | APPROVED | Active | Private | These routine calls are used by Integrated Billing to determine (1) How a user may be allowed to delete an Insurance Company from the INSURANCE COMPANY (#36) file, and (2) To cause the Accounts Receivable module to re-point the debtor (which corresponds to the Insurance Company being deleted) of all applicable AR records to a new debtor. |
RCAMINS | |||
| 1451 | DBIA1451 | Routine | ACCOUNTS RECEIVABLE | 1996/01/03 | APPROVED | Active | Private | The following calls are made to routine RCJIBFN1 and are used to display bill transaction information. Each call returns data on a specific entry in the AR TRANSACTION FILE (#433). All data is returned in internal/unformated form unless otherwise stated. |
RCJIBFN1 | |||
| 1452 | DBIA1452 | Routine | ACCOUNTS RECEIVABLE | 1996/01/04 | APPROVED | Active | Private | The following calls are made to routine RCJIBFN2. The AR specific information returned for a bill/claim is displayed in Third Party Joint Inquiry. |
RCJIBFN2 | |||
| 1453 | DBIA1453 | Routine | ACCOUNTS RECEIVABLE | 1996/01/04 | APPROVED | Active | Private |
This call is used by the Third Party Joint Inquiry to allow the person viewing a bill to add a comment transaction to the AR bill record. |
RCJIBFN3 | |||
| 2024 | DBIA2024 | Routine | ACCOUNTS RECEIVABLE | 1997/05/20 | APPROVED | Active | Private | We are making a call to BN1^PRCAFN to return the AR bill number regardless of the type of bill. |
PRCAFN | |||
| 2068 | AR PACKAGE FILE UPDATE | Other | ACCOUNTS RECEIVABLE | 1997/07/24 | APPROVED | Active | Private | This is a one time agreement to allow the updating of patch information in the AR package file for a consolidated patch release. |
||||
| 3336 | IB REFERENCING 433 | File | ACCOUNTS RECEIVABLE | 2001/03/07 | APPROVED | Active | Private | 433 | Various places in the IB package, such as MRA Extract and Diagnostic Measures, need to pull transactions from AR. This agreement allows IB to directly access the AR Transaction file (433). |
2021/11/09 | ||
| 3337 | IB referencing 430.3 | File | ACCOUNTS RECEIVABLE | 2006/04/27 | APPROVED | Active | Private | 430.3 | ||||
| 3346 | DBIA3346 | Routine | ACCOUNTS RECEIVABLE | 2001/03/28 | APPROVED | Active | Private | Integrated Billing has permission to make the following calls to AR in order get information about Repayment Plans. This information is used in 2 reports: First Party Follow-up Report and Repayment Plan Follow-up Report. Both of these reports belong to the Diagnostic Measures module. |
RCBECHGA | |||
| 3347 | DBIA3347 | File | ACCOUNTS RECEIVABLE | 2001/03/28 | APPROVED | Active | Private | 340 | Integrated Billing has permission to access the following fields on the AR DEBTOR file (#340): |
|||
| 3348 | DBIA3348 | Routine | ACCOUNTS RECEIVABLE | 2001/03/28 | APPROVED | Active | Private | Integrated Billing has permission to make the following calls to AR in order to get information about Transactions (File #433): |
RCRJRCOT | |||
| 3374 | DBIA3374 | Routine | ACCOUNTS RECEIVABLE | 2001/05/10 | APPROVED | Active | Private |
Integrated Billing has permission to make the following call to AR to determine if AR has cancelled a specific receivable associated with a bill. The IB option [IB CANCEL BILL] allows a clerk to cancel a bill which then invokes the call $$CANCEL^RCBEIB. |
RCBEIB | 2011/03/21 | ||
| 3601 | DBIA3601 | Routine | ACCOUNTS RECEIVABLE | 2002/06/28 | APPROVED | Active | Private | This IA is between PRCA and IB as a temporary IA in relation to the Hartford/USAA settlement agreement. |
RCBEADJI | |||
| 3633 | DBIA3633 | File | ACCOUNTS RECEIVABLE | 2002/08/05 | APPROVED | Active | Private | 340 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3635 | DBIA3635 | File | ACCOUNTS RECEIVABLE | 2002/08/06 | APPROVED | Active | Private | 342.1 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3636 | DBIA3636 | File | ACCOUNTS RECEIVABLE | 2002/08/06 | APPROVED | Active | Private | 430 | MDE will pull the data from this file to support the population of the new CoreFLS system. This IA is short-term and will be retired after the data has been extracted from all sites. |
|||
| 3847 | dba-test | File | ACCOUNTS RECEIVABLE | 2002/11/20 | Withdrawn | Private | 430 | testing |
||||
| 4043 | DBIA4043 | Routine | ACCOUNTS RECEIVABLE | 2003/04/02 | APPROVED | Active | Private | It has been decided that an auto-audit of bills in AR should be performed when certain electronic claim status messages are received in IB. A new entrypoint is needed with AR to accomplish this. ACTION NEEDED: PERFORM AUTO-AUDIT OF A SPECIFIC BILL IN AR |
PRCAUDT | |||
| 4260 | AR/CSL Application ACK process | Routine | ACCOUNTS RECEIVABLE | 2004/01/13 | APPROVED | Active | Controlled Subscription | After process the acknowledgement from CoreFLS, CSL will pass the information to AR. |
PRCAFLS3 | |||
| 4261 | AR/CSL Status Update Process | Routine | ACCOUNTS RECEIVABLE | 2003/09/26 | Withdrawn | Controlled Subscription | After process the Status Update from CoreFLS, CSL will pass the information back to AR. |
PRCAFLS6 | ||||
| 4289 | PRCAHV | Routine | ACCOUNTS RECEIVABLE | 2003/10/30 | APPROVED | Active | Private | PRCAHV | ||||
| 4349 | AR DATA QUEUE FILE | File | ACCOUNTS RECEIVABLE | 2004/02/18 | APPROVED | Active | Private | 348.4 | The Integrated Billing Package desires an Integration Agreement with the Accounts Receivable package to add bill number entries in to the AR DATA QUEUE File (#348.4) as they are modified in the BILL/CLAIMS File (#399). BILL NUMBER entries will be created with the standard FileMan functions; FILE^DICN, UPDATE^DIE, and FILE^DIE. The bill number will be retrieved from the ACCOUNTS RECEIVABLE File (#430) by a direct global read from the BILL NO. cross-reference. [PRCA(430,"D",BillNumber] |
|||
| 4370 | AR API to return Billing Data | Routine | ACCOUNTS RECEIVABLE | 2007/03/28 | APPROVED | Active | Private | This API is being implemented in support of the Automated Service Connected Designation (ASCD) project. The ASCD project has a Recovered Cost Report where they want to look for bills and payments for encounters that have had their Service Connected status changed by the ASCD options. This project has requested access to the Accounts Receivable (AR) package data in support of this report. It should be noted that it was recommended that this access to the AR package not be given because the data for this report is not accurate at the encounter level. This recommendation was overridden. |
PRCAAPI | 2007/09/27 | ||
| 4388 | PRCA(430 | File | ACCOUNTS RECEIVABLE | 2004/03/29 | Pending | Private | 430 | Integrated Billing system is referencing the AR global: ^PRCA(430,D0,13). The two data elements checked by the IB system and stored at this level are: Medicare Contractual Adjustment and Medicare Unreimbursable Amount. |
||||
| 4407 | DBIA4407 | File | ACCOUNTS RECEIVABLE | 2004/04/19 | Withdrawn | Private | In order to protect against loosing the set up for the customization features in the ^DISV global, patch PRCA*4.5*217 requests approval to create the ^RCCSTM global to store the selections within the CU Customize option. This will allow the most recently selected parameters and printers to be recalled by a user when customizing the screen and setting up the printer options. The information is stored in ^RCCSTM(DUZ,"RCDPRPLM",SCREEN/OPTION). An example is in routine RCDPRPL2 at line RCDPRPL2+124: S ^RCCSTM(DUZ,"RCDPRPLM","RECEIPT")=TYPE_"^"_DEVICE |
|||||
| 4553 | DBIA4553 | Routine | ACCOUNTS RECEIVABLE | 2006/03/10 | APPROVED | Active | Private | Accounts Receivable will release the routine RCKATP with patch PRCA*4.5*241. The patch post initialization process will queue a task that invokes this routine to make adjustments to the financial accounts of veterans affected by Hurricane Katrina. DBIA4552 has been developed to allow this routine to invoke the Integrated Billing routine IBAKAT to identify co-payment charges that should be cancelled. IBAKAT, in turn, will invoke several APIs in routine RCKATP to adjust the veteran's account in Accounts Receivable. This DBIA defines the APIs that IBAKAT may call back into to credit the veteran's account. |
RCKATP | |||
| 4590 | DBIA4589-B | Other | ACCOUNTS RECEIVABLE | 2005/02/03 | APPROVED | Active | Controlled Subscription | The Health Revenue Center (HRC) will be using a special telnet feature in CAPRI-Remote to view patient data across all Vista Systems. They need access to the menu options listed in this IA in order to review various records for any given patient. |
2010/06/08 | |||
| 5218 | ACCESS REQUEST TO CALL AR ROUTINE | Routine | ACCOUNTS RECEIVABLE | 2008/06/11 | APPROVED | Active | Private | The subscriber of this ICR is a Class 3 product in the "KPA" package namespace for the Consolidated Patient Account Center (CPAC). The original development effort is an interface between the Stockamp TRAC application and VistA AR. The TRAC application is a COTS product used for AR follow-up and management. This interface will file AR comments entered into the TRAC tool and automatically create AR comment transactions in the AR transaction file (File# 433). This is a request to be able to call 2 procedures in AR in order to create a stub AR transaction entry in file 433. These 2 procedure calls are very common throughout AR and is the normal method to create new entries in file 433. |
PRCAUTL | |||
| 5219 | KPA ACCESS TO AR FILE 430 | File | ACCOUNTS RECEIVABLE | 2008/06/26 | APPROVED | Active | Private | 430 | The subscriber of this ICR is a Class 3 product in the "KPA" package namespace for the Consolidated Patient Account Center (CPAC). The original development effort is an interface between the Stockamp TRAC application and VistA AR. The TRAC application is a COTS product used for AR follow-up and management. This interface will file AR comments entered into the TRAC tool and automatically create AR comment transactions in the AR transaction file (File# 433). This is a request to be able to reference several fields in file 430 in preparation for being able to file new AR comment transactions in file 433. |
2008/06/30 | ||
| 5220 | KPA ACCESS TO AR FILE 433 | File | ACCOUNTS RECEIVABLE | 2008/06/26 | APPROVED | Active | Private | 433 | The subscriber of this ICR is a Class 3 product in the "KPA" package namespace for the Consolidated Patient Account Center (CPAC). The original development effort is an interface between the Stockamp TRAC application and VistA AR. The TRAC application is a COTS product used for AR follow-up and management. This interface will file AR comments entered into the TRAC tool and automatically create AR comment transactions in the AR transaction file (File# 433). This is a request to be able to reference several fields in file 433 and also to edit (write) several fields in file 433 to be able to add a new AR comment transaction in file 433 using the FILE^DIE FileMan API. |
2008/06/30 | ||
| 5549 | DBIA5549 | Routine | ACCOUNTS RECEIVABLE | 2010/08/12 | APPROVED | Active | Private | This agreement allows by the Third Party Joint Inquiry to display contact information from the AR ERA files and also allows a comment transaction to be added to the AR bill record if payer contact information is available for the bill. |
RCDPAYER | 2010/09/09 | ||
| 5630 | DETERMINE IF A CLAIN IS A NON-ACCRUED ACCOUNT | Routine | ACCOUNTS RECEIVABLE | 2011/04/19 | APPROVED | Active | Private | Integrated Billing has permission to make the following call to AR to determine if a claim is a non-accrued account: $ACCK^PRCAACC. When the user is attempting to use the IB option: [IB CORRECT REJECTED/DENIED], if the claim is non-accrued ('$$ACCK^PRCAACC(IBIFN)), the user will be prevented from using the option and directed instead to IB option: [IB COPY AND CANCEL]. |
PRCAACC | 2011/04/19 | ||
| 5696 | Add the MDA comments into a List Manager array | Routine | ACCOUNTS RECEIVABLE | 2011/07/25 | APPROVED | Active | Private | The following subroutine call is made to the routine PRCAMDA2. The input PRCABN is the internal entry number of an entry in the BILL/CLAIMS (#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430) file. The input PRCALN is a line counter for the List Manager screen array. The subroutine will load the List Manager VALMAR array. |
PRCAMDA2 | 2011/07/25 | ||
| 6237 | ALLOW IB ACCESS TO AR EDI RARC DATA | File | ACCOUNTS RECEIVABLE | 2015/09/30 | APPROVED | Active | Private | 346 | This integration agreement allows Integrated Billing (IB) to have read access to the code (.01) and description (#4) field of AR file #346 - AR EDI RARC DATA. This is a read-only action and does not modify any fields in the file. |
2015/12/31 | ||
| 6238 | IB ACCESS TO AR EDI CARC DATA | File | ACCOUNTS RECEIVABLE | 2015/09/30 | APPROVED | Active | Private | 345 | This integration agreement allows Integrated Billing (IB) to have read access to the code (.01) and description (#4) field of AR file #345 - AR EDI CARC DATA. This is a read-only action and does not modify any fields in the file. |
2015/12/31 | ||
| 6401 | ACCOUNT PROFILE | Routine | ACCOUNTS RECEIVABLE | 2016/04/08 | APPROVED | Active | Controlled Subscription | Users working the Copay on Hold will be able to access the Patient Account Profile report while still in the Copays on Hold List Manager. This will aid them in determining if the copay may be released or not. |
PRCAAPR1 | 2016/08/31 | ||
| 6403 | ACCOUNT PROFILE REPORT | Routine | ACCOUNTS RECEIVABLE | 2016/04/08 | APPROVED | Active | Controlled Subscription | Users working the Copay on Hold will be able to access the Patient Account Profile report while still in the Copays on Hold List Manager. This will aid them in determining if the copay may be released or not. |
PRCAAPR | 2016/08/31 | ||
| 6750 | ACCOUNT PROFILE FOR OUTPATIENT PHARMACY | Routine | ACCOUNTS RECEIVABLE | 2017/03/28 | Withdrawn | Controlled Subscription | Users working Patient Medication Worklist will be able to access the patient Account Profile report while still in the worklist. This will aid them in determinig if the charge needs to be canceled or not. |
PRCAAPR1 | ||||
| 6751 | ACCOUNT PROFILE REPORT FOR OUTPATIENT PHARMACY | Routine | ACCOUNTS RECEIVABLE | 2017/03/28 | Withdrawn | Controlled Subscription | Users working Patient Medication Worklist will be able to access the patient Account Profile report while still in the worklist. This will aid them in determinig if the charge needs to be canceled or not. |
PRCAAPR | ||||
| 6851 | GET FMS DOCUMENT STATUS FOR AR BATCH PAYMENT | Routine | ACCOUNTS RECEIVABLE | 2017/12/08 | APPROVED | Active | Private | The subroutine FMSSTAT^RCDPUREC is used to get the status and FMS document given the internal entry number from the AR BATCH PAYMENT FILE [#344]. There is a need to access this call from within the INTEGRATED BILLING (IB) package to provide the FMS DOCUMENT number and STATUS for information on IB reports and worklists. |
RCDPUREC | 2018/02/08 | ||
| 7221 | IB ACCESS TO AR REPAYMENT PLAN FILE | File | ACCOUNTS RECEIVABLE | 2021/01/28 | APPROVED | Active | Private | 340.5 | This ICR allows Integrated Billing to access data in the AR REPAYMENT PLAN file (#340.5) for the following reports: 1. First Party Follow-up Report [IBJD FOLLOW-UP FIRST PARTY] 2. Repayment Plan Follow-up Report [IBJD FOLLOW-UP REPAYMENT PLAN] |
2021/05/05 | ||
| 7230 | REPAYMENT PLAN STATUS REPORT | Routine | ACCOUNTS RECEIVABLE | 2021/02/25 | Pending | Private | Integrated Billing needs access to the new Repayment Plan Status report [PRCAC PLAN STATUS REPORT] in the Diagnostic Measures Follow-up Reports Menu as a replacement to the retired (as of PRCA*4.5*378) REPAYMENT PLAN FOLLOW-UP REPORT [IBJD FOLLOW-UP REPAYMENT PLAN]. |
RCRPSTR | ||||
| 7240 | RCDMCR6 50-100SC EXMPT RPT Option | Other | ACCOUNTS RECEIVABLE | 2021/04/01 | Pending | Private | ||||||
| 7241 | RCDMCR7 10-40% COPAY RPT Option | Other | ACCOUNTS RECEIVABLE | 2021/04/01 | Pending | Private | ||||||
| 7269 | PRCA FP VETERAN CHRG RPT ADD TO DVBA HRC MENUS | Other | ACCOUNTS RECEIVABLE | 2021/06/07 | APPROVED | Active | Private | HRC is requesting the addition of the FIRST PARTY VETERAN CHARGE REPORT [PRCA FP VETERAN CHRG RPT] OPTION to the following DVBA/HRC menus: DVBA HRC MENU PHARMACY DVBA HRC MENU PHARMACY CC DVBA HRC MENU EXTENDED SVCS |
2021/06/15 | |||
| 7321 | PRCA AR SUSPENSION TYPE | File | ACCOUNTS RECEIVABLE | 2022/01/13 | Pending | Controlled Subscription | 433.001 | Allow external packages access to the fields in the AR SUSPENSION TYPE file, #433.001 for reporting filters in Integrated Billing. |