| 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 |
| 61 | DBIA61 | File | INTEGRATED BILLING | 1990/11/05 | APPROVED | Active | Private | 36 | MAS may request Social Work to use an MAS supplied utility for future versions. |
|||
| 125 | DBIA125-A | Routine | INTEGRATED BILLING | 1991/11/06 | APPROVED | Active | Private | This private agreement between PSO and IB will allow for PSO to notify IB when an Outpatient Medication Co-payment bill needs to be created, updated, or cancelled. It will also allow PSO to cancel or update a potential charge. There are also entry points for PSO to verify that a patient is subject to Pharmacy Co-payment and allow PSO to check the status of a Co-payment charge. |
IBARX | |||
| 126 | DBIA126 | Routine | INTEGRATED BILLING | 1991/11/06 | APPROVED | Active | Private | IBOLK | ||||
| 228 | DBIA228-A | File | INTEGRATED BILLING | 1993/05/12 | APPROVED | Active | Private | 353.1 | ||||
| 257 | DBIA257 | Routine | INTEGRATED BILLING | 1993/07/28 | APPROVED | Active | Private | IVM is given permission from IB to use the following code (routine IVMUFNC): N DGCRINDT,DGCRINS,IBINDT,IBINS,X S X="IBCNS" X ^%ZOSF("TEST") I $T S:$G(IVMDT) IBINDT=IVMDT D ^IBCNS G IN SQ ; for IB 2.0 and higher S X="DGCRNS" X ^%ZOSF("TEST") I $T S:$G(IVMDT) DGCRINDT=IVMDT D ^DGCRNS ; remove when IB 2.0 is required INSQ Q $S($D(IBINS):IBINS,$D(DGCRINS):DGCRINS,1:"") IVM needs this code to determine whether the patient has insurance. If he does not, he is automatically sent to IVM for verification. |
IBCNS | |||
| 271 | DBIA271-A | Other | INTEGRATED BILLING | 1993/08/27 | APPROVED | Active | Private | The following routines and file entries will be exported by PDX with version 1.5: IBAPDX IBAPDX0 IBAPDX1 |
||||
| 300 | DBIA300 | Routine | INTEGRATED BILLING | 1993/10/25 | APPROVED | Active | Private | Routine call to SVDT^IBRFN returns service dates for a specific bill. Input Variable: BN, bill number (external form) VDT, name of array to hold outpatient visit dates, pass by value if needed. Output Variable: _________________________________________________________________ | Piece | Bill not found | Inpatient | Outpatient |-----------------------------------------------------------------| | 1 | 0 | 1 | 2 | 2 | -- | event Date | Event Date | 3 | -- | stmt from date | stmt from Date | 4 | -- | stmt to date | stmt to Date | 5 | -- | LOS (I) | LOS (I) | 6 | -- | # of visit date |# of visit date ----------------------------------------------------------------- all are internal form, any piece may be null if not defined for the bill array containing outpatient visit dates as subscripts/no data, if VDT passed by value. |
IBRFN | |||
| 301 | DBIA301 | Routine | INTEGRATED BILLING | 1993/10/25 | APPROVED | Active | Private |
Routine Call to STMT^IBRFN1 to pass clinical data to AR for the patient statement. INPUT VARIABLE: TRAN, AR Transaction Number, the pointer file 433. OUTPUT VARIABLE: Returns ^TMP("IBRFN1",$J,n)=1^2^3^4^5^6^7^8, where _________________________________________________________________ | | Transaction Type |___________ |____________________________________________________ | Piece | Pharmacy |Outpatient | Inpatient |-----------------------------------------------------------------| | 1 | IB REF # | IB REF # | IB REF # | 2 | Rx # | Visit Date | Adm Date | 3 | Drug | -- | Bill From Date | 4 | Day Supply | -- | Bill To Date | 5 | Physician | -- | Disc Date | 6 | Quantity | -- | -- | 7 |Fill/Refill Date | -- | -- | 8 | Charge Amt | Charge Amt | Charge Amt ----------------------------------------------------------------- |
IBRFN1 | |||
| 304 | DBIA304 | Routine | INTEGRATED BILLING | 1993/10/27 | APPROVED | Active | Private | Call to routine IB^IBRUTL to find if there are any IB Actions on hold for this bill. Input Variables: IEN - internal entry number of bill (#399) internal entry number of bill (#430) RETN (OPT) - want array of IB Actions? 1=yes, 0=no if yes, returns IBA(num)=ibn Output Variable: 1=Yes, 0=N0 |
IBRUTL | |||
| 306 | DBIA306 | Routine | INTEGRATED BILLING | 1993/10/27 | APPROVED | Active | Private | This option allows the agent cashier to release 'holds' on Means Test Bills. ENTRY ACTION: D ^IBRREL |
IBRREL | |||
| 307 | DBIA307 | Routine | INTEGRATED BILLING | 1993/10/27 | APPROVED | Active | Private | Routine call to REPRNT^IBCF13 to print 2nd and 3rd notice UB-82's. INPUT VARIABLES: PRCASV("ARREC")=internal number of bill PRCASV("NOTICE")=number of notice OUTPUT VARIABLES: IBAR("ERR")=ERROR MESSAGE IBAR("OKAY")=1 normal finish, 0 not finished |
IBCF13 | |||
| 308 | DBIA308 | Routine | INTEGRATED BILLING | 1993/10/27 | APPROVED | Active | Private | This option prints totals of Revenue Code amounts by Rate Type to collect data for AMIS Segments 295 and 296. ENTRY ACTION: D ^IBOAMS K DTOUT |
IBOAMS | |||
| 309 | DBIA309 | Routine | INTEGRATED BILLING | 1993/10/27 | APPROVED | Active | Private | Routine call to IBCAMS to determine amis segment for reimbursable insurance bills. 249 = NSC - outpatient 292 = SC - inpatient 293 = SC - outpatient 297 = NSC - inpatient INPUT VARIABLE: X = internal entry number in #399. OUTPUT VARIABLE: Y= amis segment number or -1 if can't determine. (With the 1st release 18 months) |
IBCAMS | |||
| 310 | DBIA310 | Routine | INTEGRATED BILLING | 1993/10/27 | APPROVED | Active | Private | Routine call to MESS^IBRFN to return an error message from File 350.8. INPUT VARIABLE: Y=error code - from File 350.8 (piece 3) OUTPUT: error message from piece 2 file 350.8. |
IBRFN | |||
| 324 | DBIA324 | Routine | INTEGRATED BILLING | 1993/12/23 | APPROVED | Active | Private | IVM has permission to use the following routine call in the Integrated Billing (IB) package: Means Test Billing module: $$IGN^IBEFUNC(Appt Type, Visit Date) The call is being made to determine if a patient may be billed the Means Test Outpatient copayment, given the visit date and the appointment Type for the visit. Function Call: $$IGN^IBEFUNC(Appt Type, Visit Date) Input Parameters: Appt Type: Pointer to file #409.1, APPOINTMENT TYPE. For a specific patient appointment, this specifies the type of appointment (Regular, Research, Employee,.) Visit Date: Fileman date. For a specific patient appointment, this is the date of the appointment. Output from the call: 1 : On the specified date, for an appointment with the specified appointment type, Means Test billing should be IGNORED (so the Means Test copay should NOT be billed) 0 : On the specified date, for an appointment with the specified appointment type, Means Test billing should NOT be IGNORED (so the Means Test copay SHOULD be billed) |
IBEFUNC | |||
| 396 | DBIA396 | Routine | INTEGRATED BILLING | 1994/04/04 | APPROVED | Active | Private | This agreement was updated on 3/3/97 to convert it from an 'Other' type agreement (to support IB v2.0 installation requirements with Fee Basis) to a 'Routine' type agreement to support IB's callable routine IBCNSP2. Please note that this agreement also supercedes agreement DBIA226-C which Fee Basis held with the Registration package. The terms under which IB exported the Fee Basis patch FB*3*5 are listed below, so they are not lost: IB will transport routine FBUINS in routine IB20PT8C, and ZSave as FBUINS during the installation process if version 3 is running and patch 5 has not been installed. Patch 5 of Fee contains the following special instructions: - Do not apply if version 3 of Fee is installed but Version 2 has not been installed. - If version 3 of Fee has been installed, IB 2 will automatically apply this patch. There is no need to apply. - If you install version 2 of IB prior to installing version 3 of Fee, then this patch needs to be applied prior to allowing Fee users back on the system. Verification of FB*3*5 is pending this agreement. |
IBCNSP2 | |||
| 592 | DBIA125-B | File | INTEGRATED BILLING | 1991/11/06 | APPROVED | Active | Private | 350.1 | 5. Direct reference to ^IBE(350.1,"B" to automatically determine the IB CHARGE REMOVAL REASON of "RX DELETED" when a prescription is deleted. . 6. Look-up by Outpatient Pharmacy to the IB CHARGE REMOVAL REASON file, as this is passed back to Integrated Billing with cancel transactions. The OUTPATIENT SITE File (#59) has a pointer field to the SERVICE/SECTION File (#49). For Pharmacy Copay to work, this field must match the SERVICE Field (#.04) for pharmacy action types in the IB ACTION TYPE File (#350.1). This is done by checking the "ANEW" cross reference on the SERVICE Field (#.04) in File 350.1 with a Direct Global read: I '$D(^IBE(350.1,"ANEW",pharmacy pointer,1,1))... |
|||
| 612 | DBIA142-B | File | INTEGRATED BILLING | 1992/01/23 | APPROVED | Active | Private | 36 | ||||
| 645 | DBIA186-E | File | INTEGRATED BILLING | 1992/07/22 | APPROVED | Active | Private | 36 | ||||
| 705 | DBIA228-B | File | INTEGRATED BILLING | 1993/05/12 | APPROVED | Active | Private | 353.2 | ||||
| 766 | DBIA268-B | File | INTEGRATED BILLING | 1993/08/25 | APPROVED | Active | Private | 36 |
FILE NO. FIELD NO NODE;PIECE DESCRIPT 36 .111 .11;1 STREET ADDRESS [LINE 1] .112 .11;2 STREET ADDRESS [LINE 2] .113 .11;3 STREET ADDRESS [LINE 3] .114 .11;4 CITY .115 .11;5 STATE .116 .11;6 ZIP CODE .131 .13;1 PHONE NUMBER |
|||
| 773 | DBIA271-B | Routine | INTEGRATED BILLING | 1993/08/27 | APPROVED | Active | Private | IBAPDX - Extraction means test billing data for PDX Entry: $$EXTR^IBAPDX(TRAN,DFN,ROOT) Input: TRAN -- pointer to transaction file 394.61 DFN -- pointer to patient file 2 ROOT -- root for the output extraction array Output: 0 -- extraction was successful, or -1^err -- if an error was encountered during extraction |
IBAPDX | |||
| 774 | DBIA271-C | Routine | INTEGRATED BILLING | 1993/08/27 | APPROVED | Active | Private | IBAPDX1 - Build display set for extracted PDX billing data Entry: $$DISP^IBAPDX(XTRACT,ROOT,SEGPTR,OFFSET) Input: XTRACT -- root for the input extract array ROOT -- root for the output display array SEGPTR -- pointer to extracted segment in file 394.71 OFFSET -- offset to begin line numbering Output: NUM -- number of lines in the output display array, or -1^ERR -- if an error was encountered |
IBAPDX | |||
| 794 | DBIA277-H | File | INTEGRATED BILLING | 1993/09/13 | APPROVED | Active | Controlled Subscription | 36 | ||||
| 944 | DBIA944 | Routine | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Private | IVM files patient insurance information into DHCP which has been received from the IVM Center. This call is used to identify a group plan for the policy when the policy is being filed. |
IBCNSU | |||
| 945 | DBIA945 | Routine | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Private | IVM files patient insurance information into DHCP which has been received from the IVM Center. This call is used to reconcile the field COVERED BY HEALTH INSURANCE? in the PATIENT (#2) file with the information stored in the INSURANCE TYPE multiple after the new policy received from the IVM Center has been filed. |
IBCNSM31 | |||
| 946 | DBIA946 | Routine | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Private | IVM files patient insurance information into DHCP which has been received from the IVM Center. This routine is used to invoke the IB Insurance Event Driver after a new patient policy which has been received from the IVM Center is filed. |
IBCNSEVT | |||
| 947 | DBIA947 | Routine | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Private | These routine calls are used by the IVM package to retrieve IVM-related billing and collections information from IB to transmit to the IVM Center. |
IBAMTV4 | |||
| 948 | DBIA948 | Other | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Private | This agreement is to request approval to perform the following activities when installing IVM v2.0: 1. Export the PATIENT (#.02) and STATUS (#.05) fields of the INTEGRATED BILLING ACTION (#350) file with the release. 2. Export the options IB MT ON HOLD MENU and IB MT REV PEND CHARGES with the release. 3. Export the List Templates (in file #409.61) IB MT REVIEW INDIV CHARGES and IB MT REVIEW PATIENT with the release. 4. Export the following IB protocols with this release: - IBAMTV REV PASS CHARGE - IBAMTV REV CANC CHARGE - IBAMTV REV IND CHARGES - IBAMTV SEL PATIENT - IBAMTV REV PATIENT 5. Attach the IVM protocol IVM INSURANCE EVENT to the IB protocol IBCN NEW INSURANCE EVENTS. 6. Add the new entry HOLD - REVIEW to the IB ACTION STATUS (#350.21) file. |
||||
| 949 | DBIA949 | File | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Private | 36 | IVM files patient insurance information into DHCP which has been received from the IVM Center. To file a complete policy, it may be necessary to add entries to the INSURANCE COMPANY (#36) file. |
|||
| 950 | DBIA950 | File | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Controlled Subscription | 2 | IVM files patient insurance information into DHCP which has been received from the IVM Center. The patient policy is filed in the PATIENT (#2) file. Update: IB*2*497 increased the length of the SUBSCRIBER ID field and the NAME OF INSURED field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 2 fields to new Data Dictionary nodes in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with a IB*2*518. Old and new fields are noted in the field list detail of this ICR. |
2014/02/21 | ||
| 951 | DBIA951 | File | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Controlled Subscription | 355.1 | IVM files patient insurance information into DHCP which has been received from the IVM Center. The type of plan is received from the IVM Center with the policy. This value points to the TYPE OF PLAN (#355.1) file and must be filed in the GROUP INSURANCE PLAN (#355.3) file. |
|||
| 952 | DBIA952 | File | INTEGRATED BILLING | 1994/08/19 | APPROVED | Active | Private | 355.3 | IVM files patient insurance information into DHCP which has been received from the IVM Center. This involves potentially filing a new entry in the GROUP INSURANCE PLAN (#355.3) file. |
|||
| 1045 | DBIA1045 | File | INTEGRATED BILLING | 1994/10/28 | APPROVED | Active | Private | 355.1 | IVM Center software utilizes the Type of Plan File (#355.1) to correctly categorize insurance policies identified through the IVM verification process. The type of plan (derived from file 355.1) is transmitted from the IVM Center database via HL7 IN1 (Insurance) Segment to DHCP facilities for insurance policies identified for veterans. The Type of Plan file is pointed to by an IVM specific file (IVM Verified Insurance - #300.122) -- local entries are not added (file 355.1 is utilized for reference purposes only). |
|||
| 1046 | DBIA1046 | Routine | INTEGRATED BILLING | 1994/10/28 | APPROVED | Active | Controlled Subscription | This function returns the value of various VA pension rates. These values are date sensitive and vary depending upon the number of dependents that a veteran has. These pension values are compared with the veteran's income to determine the veteran's eligibility for the medication copayment. This function is used primarily as an internal utility for Integrated Billing during the process of determining a veteran's medication copayment exemption status, but is also accessible to a limited number of applications for the purpose of accessing and displaying these values as they would apply to a specific veteran. |
IBARXEU1 | |||
| 1137 | DBIA1137 | Routine | INTEGRATED BILLING | 1995/09/19 | APPROVED | Active | Private | IBQ Package requests use of the routines to derive date ranges. |
IBOUTL | |||
| 1182 | NATIONAL DATA BASE CALL TO IB | Routine | INTEGRATED BILLING | 1995/03/24 | Withdrawn | Private | National Data Base Routine (RCNR4) calls $$CRIT^IBRFN2 to get insurance information. |
IBRFN2 | ||||
| 1194 | DBIA1194 | Routine | INTEGRATED BILLING | 1995/04/06 | Retired | Private | IBARXEU | |||||
| 1278 | DBIA1278 | Routine | INTEGRATED BILLING | 1995/06/01 | APPROVED | Active | Private |
The ACCOUNTS RECEIVABLE package will call the entry point BILL in the routine IBCNSCD1 to allow the IB package to merge or delete the Primary Insurance Carrier on corresponding bills in IB. |
IBCNSCD1 | |||
| 1327 | DBIA1327 | Routine | INTEGRATED BILLING | 1995/09/19 | APPROVED | Active | Private | The IBQ Package requests use of the function $$VNDT^IBTRV to extract Review date. |
IBTRV | |||
| 1329 | DBIA1329 | Other | INTEGRATED BILLING | 1995/09/19 | APPROVED | Active | Private | The IBQ package requests permission to perform the following actions during the initialization of IBQ 1.0. 1. Export the following fields/files: a. Claims Tracking File (#356) - add new field (#1.09) ACUTE CARE DISCHARGE DATE and add new cross-reference 'ADIS'. b. Hospital Review File (#356.1) - add trigger to existing field (#1.17) ACUTE CARE DISCHARGE DATE to update field (#1.09) ACUTE CARE DISCHARGE DATE of File (#356). 2. Post init call ENALL^DIK to index existing entries of field (#1.17) ACUTE CARE DISCHARGE DATE of File (#356.1). |
||||
| 1350 | DBIA1350 | File | INTEGRATED BILLING | 1995/09/21 | Withdrawn | Private | 356 | The IBQ package needs to retrieve information from the Claims Tracking File (#356) for rollup to the National Database. The "ADIS" x-ref is used to gather discharged patients from the Claims Tracking File (#356) for use in IBQ. |
||||
| 1351 | DBIA1351 | File | INTEGRATED BILLING | 1995/09/21 | APPROVED | Active | Private | 356.1 | The IBQ package needs to retrieve Hospital Review information out of the HOSPITAL REVIEW File (#356.1) for use in the rollup to the National Database. The 'C' x-ref is used for the gathering of review information, given the Claims Tracking entry number from the Claims Tracking File (#356). Refer to IA-1350 for the Claims Tracking IEN that is retrieved from the 'ADIS' x-ref. |
|||
| 1352 | DBIA1352 | File | INTEGRATED BILLING | 1995/09/21 | Withdrawn | Private | 356.94 | The IBQ package needs to retrieve the providers from the INPATIENT PROVIDER File (#356.94) that correspond to the patient's Claims Tracking information. The 'C' x-ref is used to retrieve the patient's providers, given the PATIENT MOVEMENT number. PATIENT MOVEMENT is retrieved in IA 1350 using the ADMISSION field from File (#356). |
||||
| 1354 | DBIA1354 | File | INTEGRATED BILLING | 1995/09/21 | APPROVED | Active | Private | 356.9 | The IBQ package needs to retrieve diagnosis data related to the patient's admission. The 'ADG' x-ref in the INPATIENT DIAGNOSIS File (#356.9) is used to return the patient's diagnosis, given the PATIENT MOVEMENT number. The PATINT MOVEMENT number retrieved in IA-1350 from ADMISSION in the Claims Tracking File (#356). |
|||
| 1356 | DBIA1356 | File | INTEGRATED BILLING | 1995/09/21 | Withdrawn | Private | 356.4 | The IBQ package needs to retrieve the external codes in the CLAIMS TRACKING NON-ACUTE CLASSIFICATION File (#356.4). Internal entry numbers of codes to convert come from the REASON fields in the Hospital Review File (#356.1). Refer to IA-1351 for use of the REASON fields in the IBQ package. |
||||
| 1357 | DBIA1357 | File | INTEGRATED BILLING | 1995/09/21 | Withdrawn | Private | 356.3 | The IBQ package needs to retrieve the external codes found in the CLAIMS TRACKING SI/IS CATEGORIES File (#356.3). Internal entry number of codes to convert come from the SI and IS fields in the HOSPITAL REVIEW File (#356.1). Refer to IA-1351 for use of the SI and IS fields in the IBQ package. |
||||
| 1457 | DBIA1457 | Other | INTEGRATED BILLING | 1996/01/12 | APPROVED | Active | Private | Third Party Joint Inquiry Menu [IBJ THIRD PARTY JOINT INQUIRY] will be added to the Agent Cashier [PRCAY MASTER] and Clerk's AR Menu [PRCA CLERK MENU]. This will be done by running the PRYQINIT init routine in patch PRCA*4.5*15. |
||||
| 1539 | DBIA1539 | Routine | INTEGRATED BILLING | 1996/06/12 | Withdrawn | Private | IB routine IBRFN3 This routine collects billing information from the Bill/Claims file (#399) which is used by the Regional Counsel interface of the Accounts Receivable package for the purpose of sending via E-mail to a site's Regional Counsel office. |
IBRFN3 | ||||
| 1936 | DBIA1936 | Other | INTEGRATED BILLING | 1997/02/14 | APPROVED | Active | Private | Distribute IB input template. |
||||
| 1992 | DBIA1992 | File | INTEGRATED BILLING | 1997/04/04 | APPROVED | Active | Controlled Subscription | 399 | This ingegration agreement allows access to the following global nodes within file 399: ^DGCR(399,"AOPV" use of the AOPV cross-reference for look-up ^DGCR(399,#,0) ^DGCR(399,#,"S") ^DGCR(399,#,"U1") ^DGCR(399,#,"OP",0) |
|||
| 2030 | DBIA2030 | Routine | INTEGRATED BILLING | 1997/06/03 | APPROVED | Active | Private | Outpatient Pharmacy requests permission to call two entry points in the Integrated Billing routine IBACUS. This routine contains the interface points between Outpatient Pharmacy and Integrated Billing which are needed to support the real-time billing of Tricare prescriptions using a commercial pharmacy billing software package. |
IBACUS | |||
| 2031 | DBIA2031 | Routine | INTEGRATED BILLING | 1997/06/04 | APPROVED | Active | Private | This is needed to get information about the type of charges on the receivables from integrated billing. |
IBRFN | 2010/12/13 | ||
| 2034 | DBIA2034 | Routine | INTEGRATED BILLING | 1997/06/16 | APPROVED | Active | Supported | This supported reference allows packages to retrieve Sponsor information which is associated with a patient. The sponsors are the people who are responsible for the patient's Tricare or CHAMPVA medical benefits coverage. |
IBCNSU4 | |||
| 2035 | DBIA2035 | Routine | INTEGRATED BILLING | 1997/06/04 | APPROVED | Active | Private | This is needed to allow the user to be alerted that there is another payer for a receivable for co-ordination of benefits purposes. |
IBCNSBL2 | |||
| 2037 | DBIA2037 | Routine | INTEGRATED BILLING | 2003/04/21 | APPROVED | Active | Private | This DBIA provides an entry point which may be invoked by a calling application to initiate an interactive session which will allow the user to add new sponsors or edit existing sponsors, and to relate a sponsor to a patient. |
IBCNSU41 | |||
| 2215 | INTEGRATION BILLING ACTION FILE ACCESS | File | INTEGRATED BILLING | 1997/10/30 | APPROVED | Active | Private | 350 | The Outpatient Pharmacy package requests permission to look at the INTEGRATED BILLING ACTION file 350. |
2018/03/09 | ||
| 2216 | DBIA2216 | File | INTEGRATED BILLING | 1997/10/30 | APPROVED | Active | Private | 350.3 | The Outpatient Pharmacy package requests access to the Pharmacy Copayment charge cancellation reasons that are stored in the IB CHARGE REMOVE REASONS (#350.3) file. Pharmacy needs to conduct two look-ups on this file. The first look-up allows the user to select a Pharmacy Copayment charge cancellation reason from this file. The second look-up is conducted internally by the application to find the entry RX DELETED from this file, when a prescription is deleted or returned to stock. |
|||
| 2245 | DBIA2245 | Routine | INTEGRATED BILLING | 1997/12/09 | APPROVED | Active | Private | Outpatient Pharmacy requests permission to pass an internal entry number from the SERVICE/SECTION File (#49) to Integrated Billing, and have a flag returned that indicates if the service can be used for Copay billing in Outpatient Pharmacy. |
IBARX1 | |||
| 2281 | DBIA2281 | File | INTEGRATED BILLING | 1998/02/02 | Pending | Private | 399 | |||||
| 2327 | DBIA2327 | Routine | INTEGRATED BILLING | 1998/02/17 | APPROVED | Active | Private | This is needed to determine if a bill has multiple Insurance Carriers. |
IBJTU31 | |||
| 2328 | DBIA2328 | Routine | INTEGRATED BILLING | 1998/02/17 | APPROVED | Active | Private | This call is needed to allow Accounts Receivable to call the Third Party Joint Inquiry List Template (Integated Billing) from an Accounts Receivable List Template option. This is needed to prevent users from having to exit one menu option and access another option. |
IBJTLA | |||
| 2351 | OUTPATIENT ENCOUNTER SEARCH | Routine | INTEGRATED BILLING | 1998/03/26 | APPROVED | Active | Private | IBSDU is a routine I written for IB that provides a generic interface to the ACRP APPLICATION INTERFACE TOOL (AIT) introduced by Scheduling patch SD*5.3*131. The particular function that AICS needs is the 'SCAN' functionality that allows for a search for data in the encounter file without using the now prohibited direct file access. |
IBSDU | |||
| 2537 | DBIA2537 | Routine | INTEGRATED BILLING | 1998/09/15 | APPROVED | Active | Private | The IVM package requests use of the function $$ADDSTF^IBCNBES to add a new entry to the INSURANCE BUFFER file (#355.33). This data was received at the site from HEC (IVM Center). |
IBCNBES | |||
| 2538 | DBIA2538 | Routine | INTEGRATED BILLING | 1998/09/15 | APPROVED | Active | Private | The Registration package requests use of REG^IBCNBME to add/edit a INSURANCE BUFFER file (#355.33) entry for registration and use of PREG^IBCNBME to add/edit a INSURANCE BUFFER file (#355.33) entry for pre-registration. |
IBCNBME | |||
| 2780 | DBIA2780 | File | INTEGRATED BILLING | 1999/03/23 | APPROVED | Active | Private | 2 | Integrated Billing allows PDX to read and write several patient insurance data elements to support the exchange of insurance information between facilities. Update: IB*2*497 increased the length of the SUBSCRIBER ID field and the NAME OF INSURED field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 2 fields to new Data Dictionary nodes in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with IB*2*518. New fields are noted in the field list detail of this ICR. |
2014/02/21 | ||
| 2781 | DBIA2781 | File | INTEGRATED BILLING | 1999/03/23 | APPROVED | Active | Controlled Subscription | 2 | This agreement allows certain applications to directly read the field 'Covered by Health Insurance?' for the purpose of display only. |
|||
| 2782 | DBIA2782 | File | INTEGRATED BILLING | 1999/03/23 | APPROVED | Active | Private | 2 | This agreement allows Mental Health to directly read specific patient insurance fields for the purpose of display only. Update: IB*2*497 increased the length of the SUBSCRIBER ID field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of this field to a new Data Dictionary node in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new field and remove the reference to the old field. When all subscribers have implemented the use of the new field, the old field will be deleted with IB*2*518. The new field is noted in the field list detail of this ICR. |
2014/02/21 | ||
| 2786 | DBIA2786 | File | INTEGRATED BILLING | 1999/03/24 | APPROVED | Active | Private | 2 | This agreement allows the DSS EXTRACTS application to directly read specific patient insurance information for extraction by VISN 19. |
|||
| 3124 | DBIA3124 | Routine | INTEGRATED BILLING | 2000/05/23 | APPROVED | Active | Private | Routine call to return ^TMP("IBRBT",$J,IBIFN,n and ^TMP("IBRBF",$J,IBIFN,n arrays which contain third party bill information and first party bill information respectively. The purpose of this call is to find associated Third and First Party bills. The call returns arrays containing Third and First Party bills that cover the same episodes of care as the Third Party bill that is passed in as input. |
IBRFN | |||
| 3130 | DBIA3130 | Routine | INTEGRATED BILLING | 2000/06/13 | APPROVED | Active | Private | This function returns the primary division associated with the care on a Third Party bill. |
IBJDF2 | |||
| 3275 | GET IB DATA | Routine | INTEGRATED BILLING | 2000/12/27 | Withdrawn | Private | The Smart Card GUI client side needs to gather Sponsor information for the GUI Load/Edit Registration process. A Registration RPC call will call the existiong IB API GET^IBCNSU4. |
DGLEG7 | ||||
| 3276 | DBIA3276 | Routine | INTEGRATED BILLING | 2003/04/21 | Retired | Private | This agreement allows the Smart Card GUI client to file sponsor information in Integrated Billing from the GUI Load/Edit Registration process. Smart Card will utilize a non-interactive call to the new routine IBCNSU42 (which mirrors the interactive routine IBCNSU41) to file the sponsor information collected from the GUI client. |
IBCNSU42 | ||||
| 3302 | DBIA3302 | Routine | INTEGRATED BILLING | 2001/01/31 | APPROVED | Active | Controlled Subscription | The ENROLLMENT APPLICATION SYSTEM (EAS) package requests use of the function $$BUFF^IBCNBES1 to add new entries to the INSURANCE BUFFER file (#355.33). Update: IB*2*497 increased the length of the SUBSCRIBER ID field, NAME OF INSURED field, and GROUP NUMBER field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 3 fields to new Data Dictionary nodes. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with IB*2*518. Old and new fields are noted in the field list detail of this ICR. |
IBCNBES1 | 2014/02/21 | ||
| 3343 | DBIA3343 | Routine | INTEGRATED BILLING | 2001/04/18 | APPROVED | Active | Private | Accounts Receivable has permission to make the following calls to IB in order to get information about bills: |
IBCOIVM1 | |||
| 3345 | DBIA3345 | Routine | INTEGRATED BILLING | 2001/04/18 | APPROVED | Active | Private | Accounts Receivable has permission to make the following calls to IB in order to get the classification (First or Third Party) for an AR Category. |
IBJD1 | |||
| 3350 | DBIA3350 | File | INTEGRATED BILLING | 2001/03/28 | APPROVED | Active | Private | 351.73 | Accounts Receivable has permission to access the following fields on the IB DM WORKLOAD PARAMETERS file (#351.73): |
|||
| 3595 | INSURANCE PLAN TYPE | File | INTEGRATED BILLING | 2002/06/11 | APPROVED | Active | Controlled Subscription | 355.1 | 2012/07/10 | |||
| 3596 | INSURANCE COMPANY NAME | File | INTEGRATED BILLING | 2002/06/11 | Pending | Controlled Subscription | 36 | |||||
| 3642 | DBIA3642 | File | INTEGRATED BILLING | 2002/08/07 | APPROVED | Active | Private | 36 | 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. |
|||
| 3717 | DBIA3717 | Routine | INTEGRATED BILLING | 2002/08/13 | APPROVED | Active | Private | Integrated Billing API to return the maximum daily rates for LTC copayments. |
IBAECU | |||
| 3733 | GMT Related IB utilities (IA#3733) | Routine | INTEGRATED BILLING | 2002/08/21 | APPROVED | Active | Supported | This IA provides one GMT-related API call from the IB Package to be used by the PRCA (Accounts Receivable) package. |
IBAGMT | |||
| 3777 | DBIA3777 | Routine | INTEGRATED BILLING | 2002/10/07 | APPROVED | Active | Private | Integrated Billing API to release billing charges that were placed on hold as of 10/1/02 (effective date for Geographic Means Testing). The charges will be released from hold when the during the conversion process that will determine if the veteran's means test status will become GMT Copay Required or remain MT Copay Required. |
IBAGMT | |||
| 3791 | DISPLAY COPAYMENT EXEMPTION INFO | Routine | INTEGRATED BILLING | 2002/10/20 | Pending | Controlled Subscription | IBARXEU | |||||
| 3804 | DBIA3804 | Routine | INTEGRATED BILLING | 2002/10/24 | APPROVED | Active | Private | Patch PRCA*4.5*179 formally releases the MCCF Data Mart Extract as an official part of the AR package. All sites have been running the monthly MCCF Extract for over 2 years as Class III software. This patch serves to convert the MCCF Data Mart Extract to Class I software. The extract now can be run from a menu option instead of programmer mode. It solely performs read-only processing on all data. The Revenue Office has assigned a name to the extract and the associated database on the VHA/CFO Data Mart. The name is VA Revenue Information (VARI). All previous references in the software and documentation have been changed from MCCF extract to VARI extract. The information and analysis derived from these data are currently shared with the VISNs and Facilities CFOs, as well as the Operations and Revenue Offices. MCCF Collections supports ADP procurements and other medical care operations. This Integration Agreement accesses the following functions within routine IBCVA1: PROC |
IBCVA1 | |||
| 3807 | DBIA3807 | Routine | INTEGRATED BILLING | 2002/10/25 | APPROVED | Active | Private | This Integration Agreement accesses function $$NAME^IBCSC61 for the MCCF Data Mart Extract. |
IBCSC61 | |||
| 3808 | DBIA3808 | Routine | INTEGRATED BILLING | 2002/10/25 | APPROVED | Active | Private | This Integration Agreement accesses function SET^IBCSC4D for the MCCF Data Mart Extract. |
IBCSC4D | |||
| 3809 | DBIA3809 | Routine | INTEGRATED BILLING | 2002/10/25 | APPROVED | Active | Private | This Integration Agreement accesses function 32^IBCF32 for the MCCF Data Mart Extract. |
IBCF32 | |||
| 3810 | DBIA3810 | Routine | INTEGRATED BILLING | 2002/10/25 | APPROVED | Active | Private | This Integration Agreement accesses functions $$PIN^IBCSC5B and SET^IBCSC5B for the MCCF Data Mart Extract. |
IBCSC5B | |||
| 3811 | DBIA3811 | Routine | INTEGRATED BILLING | 2002/10/25 | APPROVED | Active | Private | This Integration Agreement accesses function SET^IBCSC5A for the MCCF Data Mart Extract. |
IBCSC5A | |||
| 3820 | DBIA3820-A | File | INTEGRATED BILLING | 2002/11/03 | APPROVED | Active | Private | 399 | Requesting a direct global read of the following fields to file 399 Bill Claims. |
|||
| 3821 | DBIA3820-B | File | INTEGRATED BILLING | 2002/11/04 | APPROVED | Active | Private | 399.1 | The Accounts Receivable package is requesting a direct global read access of file 399.1 MCCR UTILITY file, for the following fields listed. |
|||
| 3822 | DBIA3820-C | File | INTEGRATED BILLING | 2002/11/04 | APPROVED | Active | Private | 399.3 | The subscribing packages are requesting direct global and FileMan read access to file 399.3 RATE TYPE for the NAME field (.01). |
2010/08/25 | ||
| 3823 | DBIA3820-D | File | INTEGRATED BILLING | 2002/11/04 | Pending | Controlled Subscription | 355.3 | The Accounts Receivable package is requesting direct global read access to file 355.3 GROUP INSURANCE PLAN for the following fields listed below. |
||||
| 3824 | DBIA3820-E | File | INTEGRATED BILLING | 2002/11/04 | Pending | Private | 362.3 | The Accounts Receivable package is requesting direct global read access to file 362.3 IB BILL/CLAIMS DIAGNOSIS for the following fields listed below. |
||||
| 3825 | DBIA3820-F | File | INTEGRATED BILLING | 2002/11/04 | Pending | Private | 362.4 | The Accounts Receivable package is requesting direct global read access to file 362.4 IB BILL/CLAIMS PRESCRIPTION REFILL for field (.02) BILL NUMBER on the AIFN1 cross-reference. |
||||
| 3826 | DBIA3820-G | File | INTEGRATED BILLING | 2002/11/04 | Pending | Private | 362.5 | The Accounts Receivable package is requesting direct global read access to file 362.5 IB BILL/CLAIMS PROSTHETICS for field (.02) BILL NUBER. |
||||
| 3827 | DBIA3820-H | File | INTEGRATED BILLING | 2002/11/04 | Pending | Private | 350.9 | The Accounts Receivable package is requesting direct global read access to file 350.9 IB SITE PARAMETERS for field (1.21) MEDICARE PROVIDER NUMBER. |
||||
| 3828 | DBIA3820-I | File | INTEGRATED BILLING | 2002/11/04 | APPROVED | Active | Controlled Subscription | 355.1 | The Accounts Receivable package is requesting direct global read access to file 355.1 TYPE OF PLAN for the following fields listed below.^ |
2002/11/20 | ||
| 3831 | DBIA3829-C | File | INTEGRATED BILLING | 2002/11/04 | Pending | Private | 36 | The Accounts Receivable package is requesting a Direct global read of the following fields in file 36 INSURANCE COMPANY to set into a variable for use by the package. |
||||
| 3877 | DBIA 3877 | File | INTEGRATED BILLING | 2003/01/16 | APPROVED | Active | Private | 354.7 | Purpose is to retrieve billing information with regard to missing Outpatient Pharmacy copay bills. |
|||
| 3971 | CALL TO IBDF18A | Routine | INTEGRATED BILLING | 2003/02/19 | Withdrawn | Private | IBDF18A | |||||
| 4042 | DBIA4042 | Routine | INTEGRATED BILLING | 2003/04/10 | APPROVED | Active | Private | File 361.1 EXPLANATION OF BENEFITS is shared by Accounts Receivable and Integrated Billing. While A/R has full read access to the data in this file, adding the data and updating it require entrypoints in Integrated Billing. There are also certain standard functions that are needed/used by both Integrated Billing and Accounts Receivable to manipulate the data in this file. AR would like to be able to use these functions. |
IBCEOB | |||
| 4044 | DBIA4044 | Routine | INTEGRATED BILLING | 2003/04/08 | APPROVED | Active | Private | Return the data from an EOB in a display format. |
IBCECSA6 | |||
| 4045 | DBIA4045 | Routine | INTEGRATED BILLING | 2003/04/14 | APPROVED | Active | Private | An entrypoint is needed by A/R to access the TPJI (Third Party Joint Inquiry) option from a PROTOCOL action. The level of entry needs to be at the point where a bill number can be assumed and the appropriate TPJI list manager screen will be invoked. This entry point already exists at line EN^IBJTCA and A/R would like to have access to this call. |
IBJTCA | |||
| 4047 | DBIA4047 | Routine | INTEGRATED BILLING | 2003/04/09 | APPROVED | Active | Private | Entrypoint to invoke the Cancel/Edit/Add Patient Charges option from Accounts Receivable ERA Worklist option. |
IBECEA | |||
| 4048 | DBIA4048 | Routine | INTEGRATED BILLING | 2003/04/11 | APPROVED | Active | Private | Entrypoint to invoke the LIST ON HOLD CHARGES option from Accounts Receivable ERA Worklist option. |
IBOHPT1 | |||
| 4049 | DBIA4049 | File | INTEGRATED BILLING | 2003/04/07 | Retired | Private | 350.9 | When an electronic EOB is received in error at a site, EDI Lockbox has functionality to transfer that EOB electronically to another site. The AGENT CASHIER PHONE NUMBER field contains the contact information for the receiving site to use to contact the sending site if there are questions regarding the EOB. Accounts Receivable needs to have read access to this data to allow it to be included in the transferred EOB. |
||||
| 4050 | DBIA4050 | Routine | INTEGRATED BILLING | 2003/04/07 | APPROVED | Active | Private | File 361.1 EXPLANATION OF BENEFITS is shared by Accounts Receivable and Integrated Billing. When an EOB is applied to A/R bills, sometimes a payment is made to the wrong bill or the payment is made to one bill and it should have been split between multiple bills. In order to keep the AR system in balance with the EOBs on file in file 361.1, AR needs to update the AR AMOUNTS DISTRIBUTION field in this file. This IA is requested for an entrypoint to a call within IB to allow A/R to update this data in file 361.1, field 8 AR DISTRIBUTION AMOUNTS (multiple field). |
IBCEOBAR | |||
| 4051 | DBIA4051 | File | INTEGRATED BILLING | 2003/04/07 | APPROVED | Active | Private | 361.1 | File 361.1 EXPLANATION OF BENEFITS is used by Integrated Billing to store Electronic Remittance Advices (ERA) that are received electronically from MEDICARE (MRAs). The Accounts Receivable system will be receiving Electronic Remittance Advices from payers other than MEDICARE via the Third Party Lockbox system. The file is currently structured to allow both types of ERAs to be stored, so it was decided to use the same file to store the data, since the data for both is derived from an X12 835 message and is delivered to VistA using the same file format. As a result of this decision, this IA is requested to allow Accounts Receivable to have full direct read access and the ability to use Fileman to define a field as a pointer to this file so it can access the data for functions specific to AR needs. |
|||
| 4115 | DBIA4115 | Routine | INTEGRATED BILLING | 2003/05/29 | APPROVED | Active | Private | The OUTPATIENT PHARMACY package will call the entry point PTCOV in the routine IBCNSU3 to allow Outpatient Pharmacy to provide a report of patients who had prescription insurance coverage on the fill date of prescriptions which had copay charges back-billed by patch PSO*7*123. |
IBCNSU3 | |||
| 4118 | ALLOW A/R TO UPDATE RATE TYPE FILE | File | INTEGRATED BILLING | 2003/06/05 | APPROVED | Active | Private | 399.3 | The EDI Third Party Lockbox module includes functionality where, when electronic bill status messages are received in Integrated Billing containing specific data, the auto-audit function of A/R is automatically invoked, based on the rate type of the bill. The IB portion of the patch is modifying the RATE TYPE file (#399.3 - which it owns) to add field #.11 BILL RESULTING FROM. From an A/R standpoint then, if this field is filled in for a rate type, then all bills with that rate type are eligible for the auto-audit function. As a result, a request is being made to grant A/R Fileman write access to the RATE TYPE file (#399.3) to allow A/R personnel to update this field in this file so they can control which rate types can be auto-audited. |
|||
| 4121 | A/R access to TPJI for patient name OR bill number | Routine | INTEGRATED BILLING | 2003/06/11 | APPROVED | Active | Private | An entrypoint is needed by A/R to access the TPJI (Third Party Joint Inquiry) option from a PROTOCOL action. The level of entry needs to be at the point where the user is prompted to enter EITHER a patient name OR a bill number and the appropriate TPJI list manager screen will be invoked. This entry point already exists at line OPTION^IBJTLA and A/R would like to have access to this call. |
IBJTLA | |||
| 4128 | REVENUE CODE | File | INTEGRATED BILLING | 2003/06/20 | APPROVED | Active | Private | 399.2 | This IA allows Fee Basis to establish a field that points to the REVENUE CODE (#399.2) file. LAYGO is not allowed. |
|||
| 4288 | RETRIEVE INSURANCE DATA | Routine | INTEGRATED BILLING | 2003/10/22 | APPROVED | Active | Private | Register Once Messaging will initiate a %ZTLOAD call to BACKGND^IBCNRDV to retrieve insurance data from sites of record each time a veteran is registered at a new site for the first time. IB*2.0*763 adds a switch to enable/disable retrieval of insurance data. DG*5.3*1102 checks the status of the switch. (See ICR 7429) |
IBCNRDV | 2023/07/17 | ||
| 4299 | EPHARMACY API | Routine | INTEGRATED BILLING | 2003/11/25 | APPROVED | Active | Controlled Subscription | The Outpatient Pharmacy, CMOP, and ECME packages request the usage of the Integrated Billing functions to support ePharmacy billing. |
IBNCPDP | 2011/12/22 | ||
| 4308 | NEW FILE #350 FIELD | File | INTEGRATED BILLING | 2003/12/02 | Withdrawn | Private | 350 | A new field called HOLD-REVIEW DATE (#17) will be added to the INTEGRATED BILLING ACTION (#350) file, so that when a charge is put in 'HOLD-REVIEW' status in the file, this field will be automatically "stuffed" with the current date. This will be similar to the file field ON HOLD DATE (#16), where if a charge in the file is put in 'ON HOLD' status, it's stuffed with the current date. |
||||
| 4385 | MRA related function Calls from AR into IB | Routine | INTEGRATED BILLING | 2004/03/31 | APPROVED | Active | Private | Two MRA related function calls made from AR into the IB system: 1) Determine the MRA Type for a given bill. Pre-MRA bills, post-MRA Medicare bills or post-MRA non-Medicare bills. This function returns 1, if the bill is a pre-MRA bill, returns 2 if the bill is a post-MRA Medicare bill, or 3 if the bill is a post-MRA Medicare bill. 2) Return the date Medicare Remittance Advice (MRA) was first activated at site. |
IBCEMU2 | |||
| 4391 | INSURANCE COMPANY FILE ACCESS | File | INTEGRATED BILLING | 2004/04/07 | APPROVED | Active | Private | 36 | It has come to my attention that Accounts Receivable has no Integration Agreement with Integrated Billing to allow A/R to access the insurance file (#36), even though A/R uses this file extensively for the following: INSURANCE COMPANY NAME (#.01 field), direct read INSURANCE COMPANY ADDRESS (fields #.111-#.116), direct read As a file lookup using ^DIC As a pointer directly to ^DIC(36) in ACCOUNTS RECEIVABLE file (#430 - 2 fields - SECONDARY INSURANCE CARRIER (#19) and TERTIARY INSURANCE CARRIER (#19.1)) As part of a variable pointer on the DEBTOR field (#.01) of the AR DEBTOR file (#340) An IA is needed to cover these usages. |
|||
| 4419 | DBIA4419 | Routine | INTEGRATED BILLING | 2004/05/07 | APPROVED | Active | Supported | IBBAPI is a new routine to return insurance data to calling VistA applications. |
IBBAPI | 2023/01/25 | ||
| 4434 | DBIA4434 | File | INTEGRATED BILLING | 2004/05/26 | APPROVED | Active | Private | 350 | ||||
| 4435 | DBIA4435 | Routine | INTEGRATED BILLING | 2004/05/27 | APPROVED | Active | Private | IB functions are to serve AR in matching the ECME number to the respective IB bill ($$RXBIL component) and to check the status of a claim in Claims Tracking ($$REJECT component). |
IBNCPDPU | 2010/12/13 | ||
| 4505 | DSIV CALL TO IBCNBLA1 | Routine | INTEGRATED BILLING | 2010/12/14 | Pending | Private | The Insurance Capture Buffer (ICB) application uses the ICB API in IBCNBLA1 to update the buffer symbol when retrieving or refreshing buffer entries. |
IBCNBLA1 | ||||
| 4506 | IIV STATUS TABLE ACCESS | File | INTEGRATED BILLING | 2010/12/14 | APPROVED | Active | Private | 365.15 | DSIV requests access to file 365.15 IIV STATUS TABLE to display the entire eIV error message for the Insurance Capture Buffer (ICB) application. This file is only read when there is an error condition. |
2023/01/12 | ||
| 4524 | DBIA4524 | Routine | INTEGRATED BILLING | 2004/10/14 | APPROVED | Active | Private | The REGAUTO^IBARXEU5 API updates the Billing Patient file (#354) with a patient's copay status and exemption reason. Registration queues this API as a background task from routine DGMTCOR. |
IBARXEU5 | |||
| 4538 | AR ACCESS TO FILE 350.1 | File | INTEGRATED BILLING | 2006/02/28 | APPROVED | Active | Private | 350.1 | As part of the Vista IB/AR Data Extract to the ARC, AR needs to access file 350.1 (IB ACTION TYPE). AR would like direct global access to the following: Direct global read access is requested for the following fields: .01 NAME .11 BILLING GROUP Direct global read access for record lookup by name to the following cross reference: ^IBE(350.1,"B" |
2010/03/03 | ||
| 4541 | AR access to INTEGRATED BILLING ACTION file 350 | File | INTEGRATED BILLING | 2006/03/02 | APPROVED | Active | Private | 350 | As part of the Vista IB/AR date extract to the ARC, AR needs to access file 350 (INTEGRATED BILLING ACTION). AR would like direct global access to the following: Access to "ABIL" cross-reference (AR BILL NUMBER) Access to "C" cross-reference (PATIENT) Direct global access to ^IB(DO,0) to place data in the AR DATA QUEUE (348.4) Fileman access to the .05 STATUS field of file 350 |
2020/11/17 | ||
| 4552 | DBIA4552 | Routine | INTEGRATED BILLING | 2006/03/10 | APPROVED | Active | Private | Integrated Billing is releasing the new routine IBAKAT, which contains an entry point that will be invoked by the patch PRCA*4.5*241 post initialization process. IBAKAT will identify all co-payment charges, for veterans affected by Hurricane Katrina, for care provided from 8/29/05 through 2/28/06. This routine will in turn invoke various APIs within Accounts Receivable to credit veterans' accounts. |
IBAKAT | |||
| 4594 | DBIA4589-F | Other | INTEGRATED BILLING | 2005/01/25 | 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. |
2005/02/15 | |||
| 4602 | GET CURRENT INSURANCE | Routine | INTEGRATED BILLING | 2005/02/07 | APPROVED | Active | Private | As part of the IB/AR data extract, AR must pull the current insurance IEN for a bill in order to determine the Payer. Routine RCXVDC3 uses the IB function $$CURR^IBCEF2(RCXVD0), where RCXVD0 is the internal number of the bill to get the internal number of the insurance file. This is then used to extract the payer from the insurance file. |
IBCEF2 | |||
| 4603 | FILE 361 | File | INTEGRATED BILLING | 2005/02/07 | APPROVED | Active | Private | 361 | As part of the AR/IB data extract, AR needs to determine whether a claim has had any MRA rejection messages. These messages are stored in file 361. Routine RCXVDC3 uses the "B" X-Ref of that file in order to determine all messages for a particular bill. It then checks piece 3 of the '0' node to determine if the message had a 'rejected' status and adds one to the count if it is rejected. |
|||
| 4604 | FILE 365.12 | File | INTEGRATED BILLING | 2005/02/07 | APPROVED | Active | Private | 365.12 | As part of the AR/IB data extract, the PAYER NAME and the VA NATIONAL ID needs to be extracted from file 365.12 for transmission to the ARC. RCXVDC3 uses a direct global read to extract this information. |
|||
| 4635 | ROUTINE IBRFN4 | Routine | INTEGRATED BILLING | 2005/08/15 | APPROVED | Active | Private | Accounts Receivable is seeking an integration agreement to call routine IBRFN4 to gather information from various integrated billing files. This information is then used as data elements in the IB AR Data Extract, which is sent via FTP to the ARC. |
IBRFN4 | |||
| 4646 | DSIV CALL TO IBCNEUT3 | Routine | INTEGRATED BILLING | 2010/12/14 | Pending | Private | The Insurance Capture Buffer (ICB) application uses the $$INSERROR API in IBCNEUT3 to retrieve a single line, user friendly eIV error message. This call is only made when there is a buffer error condition. |
IBCNEUT3 | ||||
| 4663 | PFSS ON/OFF SWITCH | Routine | INTEGRATED BILLING | 2005/05/23 | APPROVED | Active | Supported | The function $$SWSTAT^IBBAPI provides the calling application with the status of the PFSS On/Off Switch. When the switch is "ON", the calling application should proceed with processing required to conform with PFSS functionality. |
IBBAPI | |||
| 4664 | PFSS ACCOUNT | Routine | INTEGRATED BILLING | 2005/05/23 | APPROVED | Active | Controlled Subscription | This entry point is added to routine IBBAPI in order to accommodate Patient Financial Services System (PFSS) functionality requirements for establishing patient accounts in the commercial medical billing system. This entry point is called by a number of VistA applications involved in PFSS. |
IBBAPI | |||
| 4665 | PFSS CHARGE | Routine | INTEGRATED BILLING | 2005/05/23 | APPROVED | Active | Controlled Subscription | Two entry points are added to routine IBBAPI in order to accommodate Patient Financial Services System (PFSS) functionality requirements to provide charge data to the commercial medical billing system. These entry points are called by several VistA applications involved in PFSS. |
IBBAPI | |||
| 4692 | DBIA4692 | Routine | INTEGRATED BILLING | 2005/06/22 | APPROVED | Active | Private | This call is needed to allow ECME to call the Third Party Joint Inquiry List Template (Integated Billing) from an Accounts Receivable List Template option. This is needed to prevent users from having to exit one menu option and access another option. |
IBNCPDPI | |||
| 4693 | DBIA4693 | Routine | INTEGRATED BILLING | 2005/06/22 | APPROVED | Active | Private | This call is needed to allow ECME to call the IB CLAIM TRACKING / VIEW /EDIT EPISODE functionality. This is needed to prevent users from having to exit one menu option and access another option. |
IBNCPDPC | 2010/12/10 | ||
| 4694 | DBIA4694 | Routine | INTEGRATED BILLING | 2005/06/22 | APPROVED | Active | Private | This call is needed to allow ECME to call the IB Patient Insurance Info View/Edit functionality. This is needed to prevent users from having to exit one menu option and access another option. |
IBNCPDPI | |||
| 4695 | DBIA4695 | Routine | INTEGRATED BILLING | 2005/06/22 | APPROVED | Active | Private | This call is needed to allow ECME to call the IB Patient Eligibility functionality. This is needed to prevent users from having to exit one menu option and access another option. |
IBNCPDPL | |||
| 4696 | DBIA4696 | Routine | INTEGRATED BILLING | 2005/06/22 | APPROVED | Active | Private | This call is needed to allow ECME to call the IB List Current/Past Held Charges by Pt functionality. This is needed to prevent users from having to exit one menu option and access another option. |
IBNCPDPH | |||
| 4697 | DBIA4697 | Routine | INTEGRATED BILLING | 2005/06/22 | APPROVED | Active | Private | This call is needed to allow ECME to release Held Charges. This is needed to prevent users from having to exit one menu option and access another option. |
IBNCPDPR | |||
| 4698 | DBIA4698 | Routine | INTEGRATED BILLING | 2005/06/22 | APPROVED | Active | Private | This call is needed to allow ECME to invoke ECME Billing Events Report. |
IBNCPDPE | |||
| 4699 | DBIA4699 | File | INTEGRATED BILLING | 2005/07/14 | Retired | Private | 363.21 | ECME is storing the pointer to #363.21 BILLING ITEMS file in its #9002313.57 BPS LOG OF TRANSACTIONS file. |
||||
| 4700 | DBIA4700 | File | INTEGRATED BILLING | 2005/07/14 | Retired | Private | 363.2 | ECME is storing the pointer to #363.2 -- CHARGE ITEM FILE in its #9002313.51 -- BPS DATA INPUT FILE, field (#1.08) CPTIEN [8P:363.2] |
||||
| 4709 | PFSS PROCESS INSURANCE FROM DG REGISTRATION | Routine | INTEGRATED BILLING | 2005/06/27 | APPROVED | Active | Private | The Registration application (DG) will receive messages sent from the COTS Billing package and then pass these messages off to the Integrated Billing (IB) package for insurance processing. This IA will insure that Registration accesses the API used to pass the HL7 message off to IB for processing in the correct way. The routine IBBFINA will be called at the entry point EN, passing the parameter for the internal entry number of the HL7 message from file 772. The API will parse the HL7 message and store insurance data values pertinent to the patient inside the new file structures defined for PFSS Insurance. |
IBBFINA | |||
| 4710 | DBIA4710 | File | INTEGRATED BILLING | 2005/06/28 | APPROVED | Active | Private | 356.8 | ||||
| 4721 | DBIA4721 | Routine | INTEGRATED BILLING | 2005/07/07 | Other | Private | This agreement includes various INTEGRATED BILLING APIs for use by the E CLAIMS MGMT ENGINE to provide data necessary for processing electronic claims. |
IBNCPDPI | ||||
| 4729 | API FOR RX BILLING INFO | Routine | INTEGRATED BILLING | 2005/07/11 | APPROVED | Active | Controlled Subscription | The API returns billing information for specified prescription/refill. |
IBNCPDPI | 2010/08/25 | ||
| 4741 | PFSS ACCOUNT REFERENCE | File | INTEGRATED BILLING | 2005/07/27 | APPROVED | Active | Controlled Subscription | 375 | Allows VistA applications participating in Patient Financial Services System (PFSS) to store the PFSS Account Reference within their respective file structures. The PFSS Account Reference is a pointer to the PFSS ACCOUNT file (#375). |
|||
| 4772 | INSURANCE PROCESSING | Routine | INTEGRATED BILLING | 2005/08/22 | Retired | Private | This integration agrement between Integrated Billing and Registration is to allow the processing of Insurance Buffer entries before subsequent send to the COTS Billing package. Regsitration will call the IB routine IBBFINS in order to assign Financial Status Classifications (FSC) to insurance buffers entries that currently do not have a FSC assigned in order to interface them to the COTS Billing package along with Registration/Demographic changes. The call will be constructed as EN^IBBFINS(DFN) where DFN is the Internal Entry Number of the patient in the PATIENT (#2) file. IB will process the Insurance Buffer (#355.33) file entries and pass operations back to DG Registration for sending the message to COTS Billing. There is currently NO value passed back from IBBFINS to indicate completion. Once completed, Registration is able to send the message on to the COTS Billing package. |
IBBFINS | ||||
| 4777 | AR access to IB Patient Copay account data | File | INTEGRATED BILLING | 2005/08/17 | APPROVED | Active | Private | 354.7 | ||||
| 4785 | INSURANCE BUFFER FILE ACCESS | File | INTEGRATED BILLING | 2005/08/25 | APPROVED | Active | Private | 355.33 | Access to the Insurance Buffer file (#355.33) is granted solely for the purpose of creating HL7 messages for the PFSS project. Update: IB*2*497 increased the length of the SUBSCRIBER ID field, NAME OF INSURED field, GROUP NAME, and GROUP NUMBER field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 4 fields to new Data Dictionary nodes. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with IB*2*518. Old and new fields are noted in the field list detail of this ICR. |
2014/02/21 | ||
| 4786 | PATIENT FSC FILE ACCESS | File | INTEGRATED BILLING | 2005/08/25 | APPROVED | Active | Private | 370 | Access to the Patient FSC File (#370) is granted solely for the purpose of creating an HL7 message for the PFSS project. |
|||
| 4787 | VISTA FSC FILE ACCESS | File | INTEGRATED BILLING | 2005/08/25 | APPROVED | Active | Private | 370.1 | Access to the VISTA FSC File (#370.1) is granted solely for the purpose of building HL7 messages for the PFSS project. |
|||
| 4788 | COMMERCIAL INSURANCE FILE ACCESS | File | INTEGRATED BILLING | 2005/08/25 | APPROVED | Active | Private | 370.2 | Access to the Commercial Insurance File (#370.2) is granted for the sole purpose of building HL7 messages for the PFSS project. |
|||
| 4789 | PFSS PLAN FILE ACCESS | File | INTEGRATED BILLING | 2005/08/25 | APPROVED | Active | Private | 370.3 | Access is granted to the PFSS Plan File (#370.3) for the sole purpose of building HL7 messages for the PFSS project. |
|||
| 4790 | PFSS INSURANCE STATUS UPDATE | Routine | INTEGRATED BILLING | 2005/08/25 | APPROVED | Active | Private | 370.4 | IBBFINS | |||
| 4862 | DBIA4862 | Other | INTEGRATED BILLING | 2006/06/14 | APPROVED | Active | Private | The HL LOGICAL LINK file entry IBBPFSS1 may be referenced from the LOGICAL LINK field as packages export PROTOCOL file entries using that link. |
||||
| 4939 | AVOID NPI DUPLICATES | File | INTEGRATED BILLING | 2008/03/18 | Other | Private | 355.93 | When entering/editing an NPI to an entry in the NEW PERSON file (#200), the INSTITUTION file (#4) or the IB NON/OTHER VA BILLING PROVIDER file (#355.93), Kernel needs to check if the NPI is already used by an entry in any of the three files. If the NPI is already used, Kernel will issue either an error or a warning message, depending on which file is currently being edited. An NPI used by an entry in file 4 cannot be used in an entry in either of the other files regardless of whether the NPI is 'active' or 'inactive'. An NPI can be used in a single entry in both file 200 and file 355.93 at the same time, but a warning is issued in that case. |
2007/02/01 | |||
| 4957 | DBIA4957 | File | INTEGRATED BILLING | APPROVED | Active | Private | 355.93 | The CBO Extract needs to extract the National Provider Identifier (NPI) from the NON/OTHER VA BILLING PROVIDER file (#355.93) for both individual and organizational providers. This is a read-only action and does not modify any fields in the file. |
2007/03/04 | |||
| 4960 | INSURANCE CO AND PROVIDER ID | File | INTEGRATED BILLING | APPROVED | Active | Private | 355.9 | The NPI Extract needs to extract the INSURANCE CO and PROVIDER ID from the IB BILLING PRACTITIONER ID file (#355.9). This is a read-only action and does not modify any fields in the file. |
2007/02/01 | |||
| 4961 | GET PROVIDER ID FROM INSURANCE DATA | File | INTEGRATED BILLING | APPROVED | Active | Private | 355.91 | The NPI Extract needs to extract the PROVIDER ID from the IB INSURANCE CO LEVEL BILLING PROV ID file (#355.91). This is a read-only action and does not modify any fields in the file. |
2007/02/01 | |||
| 4962 | GET PROVIDER ID FROM FACILITY BILLING ID | File | INTEGRATED BILLING | APPROVED | Active | Private | 355.92 | The NPI Extract needs to extract the PROVIDER ID from the FACILITY BILLING ID file (#355.92). This is a read-only action and does not modify any fields in the file. |
2007/02/01 | |||
| 4964 | GET FACILITY NAME & FED TAX NUMBER FROM IB SITE PARAMS | File | INTEGRATED BILLING | 2010/08/26 | APPROVED | Active | Private | 350.9 | The NPI Extract needs to extract the FACILITY NAME, the FEDERAL TAX NUMBER and the PAY-TO PROVIDER data from the IB SITE PARAMETER FILE (#350.9). This is a read-only action and does not modify any fields in the file. |
2010/08/26 | ||
| 4965 | GET ZERO NODE INFO FROM IB NON/OTHER VA BILLING PROVIDER | File | INTEGRATED BILLING | APPROVED | Active | Private | 355.93 | The NPI Extract needs to extract several fields from the IB NON/OTHER VA BILLING PROVIDER file (#355.93). This is a read-only action and does not modify any fields in the file. |
2007/02/01 | |||
| 4971 | DBIA4971 | File | INTEGRATED BILLING | APPROVED | Active | Private | 36 | The NPI Extract extracts IB insurance company data during its run. The extract was developed as part of the HIPAA NPI project. The NAME and TYPE OF COVERAGE need to be extracted as part of the NPI Extract process. |
2007/03/04 | |||
| 4972 | DBIA4972 | File | INTEGRATED BILLING | APPROVED | Active | Private | 355.2 | The NPI Extract extracts IB insurance coverage data during its run. The extract was developed as part of the HIPAA NPI project. The NAME needs to be examined as part of the NPI Extract process. |
2007/03/04 | |||
| 4987 | IB BILLING DATA API | Routine | INTEGRATED BILLING | 2007/05/04 | APPROVED | Active | Private | This set of API's provide billing data related to Outpatient Encounters and allows the update of an encounters billable status. These are implemented to support the Automated Service Connected Designation (ASCD) project. This project may potentially update an encounters Service Connected designation after the encounter's check-out. |
IBRSUTL | 2007/09/19 | ||
| 4996 | EEOB Worklist NPI inclusion | File | INTEGRATED BILLING | 2007/05/25 | APPROVED | Active | Controlled Subscription | 399 | This DBIA is for allowing the Accounts Receivable package to utilize Fileman APIs to retrieve NPIs, provider types and provider names from the Bill/Claims file (#399). The fileman APIS to be used are GET1^DIQ and GETS^DIQ. |
2007/09/19 | ||
| 5029 | VERIFY SC APPOINTMENT TYPE | File | INTEGRATED BILLING | 2007/08/23 | APPROVED | Active | Private | 352.1 | Scheduling requires one time access to the Billable Appointment Type file to verify that the Service Connected entry is correctly defined. This entry was created to correspond to the new Service Connected Appointment Type but may have been incompletely added if there were local changes to the Billable Appointment Type file. The Scheduling patch SD*5.3*491 post-init will access the SERVICE CONNECTED (#11) node of the BILLABLE APPOINTMENT TYPE (#352.1) file to verify that it was correctly created and points to the SERVICE CONNECTED (#11) entry of the APPOINTMENT TYPE (#409.1) file. This agreement will expire at the end of the SD*5.3*491 compliance date. |
2008/07/28 | ||
| 5103 | 5103 - IBBFAPI for FBCS (DSS) | Routine | INTEGRATED BILLING | 2008/01/31 | Withdrawn | Controlled Subscription | IBBFAPI | |||||
| 5185 | Update IB NDC NON COVERED BY PLAN FILE #366.16 | Routine | INTEGRATED BILLING | 2008/04/21 | Retired | Private | The IB API to add/update a record in the file IB NDC NON COVERED BY PLAN FILE #366.16 |
IBNCDNC | 2008/04/21 | |||
| 5204 | DBIA5204 | Routine | INTEGRATED BILLING | 2008/05/28 | Pending | Private | IB grants permission to ECME to call the routine IBCNRE4 to provide access to the Edit PLAN APPLICATION Sub-file option through the ECME User Screen. This option is locked with the IBCNR E-PHARMACY SUPERVISOR security key. |
IBCNRE4 | ||||
| 5207 | DBIA5207 | Routine | INTEGRATED BILLING | 2008/06/05 | Pending | Private | IB grants permission to ECME to call the routine EN^IBCNRPMT to provide access to the Match Group Plan to a Pharmacy Plan option through the ECME User Screen. This option is locked with the IBCNR E-PHARMACY SUPERVISOR security key. |
IBCNRPMT | ||||
| 5208 | DBIA5208 | Routine | INTEGRATED BILLING | 2008/06/05 | Pending | Private | IB grants permission to ECME to call the routine EN^IBCNRPM1 to provide access to the Match Multiple Group Plans to a Pharmacy Plan option through the ECME User Screen. This option is locked with the IBCNR E-PHARMACY SUPERVISOR security key. |
IBCNRPM1 | ||||
| 5210 | IB DRUGS NON COVERED REPORT | Other | INTEGRATED BILLING | 2008/06/06 | APPROVED | Active | Private | Allows the E CLAIMS MGMT ENGINE package to use IB DRUGS NON COVERED REPORT menu option (Drugs non covered report) in its menu. |
2008/06/10 | |||
| 5281 | FBCS File #353.1 Read only | File | INTEGRATED BILLING | 2008/10/23 | Retired | Controlled Subscription | 353.1 | Using cross references: ^IBE(353.1,"B" to verify .01 field (external entries conversion to IEN) Also using fileman to get values for a pull down list (palce of service): D LIST^DIC(353.1,"",".01;.02","","","","","","","","ARRAY","MSG") |
2008/12/03 | |||
| 5282 | FBCS File #353.2 Read only | File | INTEGRATED BILLING | 2008/10/23 | Retired | Controlled Subscription | 353.2 | Verifying data at node: $D(^IBE(353.2,IEN,0) Also using FM to retrieve a list for the GUI of HCFA type of Service: D LIST^DIC(353.2,"",".01;.02","","","","","","","","ARRAY","MSG") |
2008/12/03 | |||
| 5286 | PAY-TO PROVIDER PHONE NUMBER API | Routine | INTEGRATED BILLING | 2008/11/06 | APPROVED | Active | Private | This is a replacement IA for IA# 4049. The purpose of the IA is the same. When an electronic EOB is received in error at a site, EDI Lockbox has functionality to transfer that EOB electronically to another site. The IB Site Parameters file (#350.9) contains the Pay-to Provider phone#. This phone# is the contact information for the receiving site to use to contact the sending site if there are questions regarding the EOB. Accounts Receivable needs to be able to retrieve this phone# from the IB Site Parameters file in order for it to be included in the transferred EOB. |
IBJPS3 | 2008/11/21 | ||
| 5292 | INSURANCE CO FILE ACCESS | File | INTEGRATED BILLING | 2008/11/23 | APPROVED | Active | Private | 36 | DSIV requests access to the Insurance Company file (#36) to do the following for its Insurance Capture Buffer (ICB) application: Using file #36 as a file lookup using ^DIC, and as a pointer directly to ^DIC(36) in DSI ICB AUDIT file (#19625 - INSURANCE DFN POINTER (#4.12)) Also these usages: ^DIC(36,D0,0) .01 NAME 0;1 Read w/FileMan 1 REIMBURSE? 0;2 Read w/FileMan 2 SIGNATURE REQUIRED ON BILL? 0;3 Read/Write w/FileMan .05 INACTIVE 0;5 Read w/FileMan .12 FILING TIME FRAME 0;12 Read/Write w/FileMan .13 TYPE OF COVERAGE 0;13 Read/Write w/FileMan and with pointer to the TYPE OF COVERAGE file (#355.2). This is the type of insurance coverage. .18 STANDARD FTF 0;18 Read/Write w/FileMan and with pointer to the INSURANCE FILING TIME FRAME file (#355.13). This is the standard filing time frame that applies to the insurance. .19 STANDARD FTF VALUE 0;19 Read/Write w/FileMan ^DIC(36,D0,.11) .111 STREET ADDRESS [LINE 1] .11;1 Read w/FileMan .112 STREET ADDRESS [LINE 2] .11;2 Read w/FileMan .113 STREET ADDRESS [LINE 3] .11;3 Read w/FileMan .114 CITY .11;4 Read w/FileMan .115 STATE .11;5 Read w/FileMan .116 ZIP CODE .11;6 Read w/FileMan .119 FAX NUMBER .11;9 Read/Write w/FileMan ^DIC(36,D0,.13) .131 PHONE NUMBER .13;1 Read w/FileMan .132 BILLING PHONE NUMBER .13;2 Read w/FileMan .133 PRECERTIFICATION PHONE NUMBER .13;3 Read w/FileMan ^DIC(36,D0,3) 3.01 TRANSMIT ELECTRONICALLY 3;1 Read/Write w/FileMan 3.09 ELECTRONIC INSURANCE TYPE 3;9 Read/Write w/FileMan ^DIC(36,D0,10,0) (#10) SYNOMYM Multiple (subfile #36.06) .01 SYNONYM 0;1 Read/Write w/FileMan ^DIC(36,D0,11,0) (#11) REMARKS Word-processing (subfile #36.011) .01 REMARKS 0;1 Read/Write w/FileMan |
2012/09/13 | ||
| 5293 | GROUP INSURANCE PLAN ACCESS | File | INTEGRATED BILLING | 2008/11/23 | APPROVED | Active | Private | 355.3 | Update: IB*2*497 increased the length of the GROUP NAME field and GROUP NUMBER field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 2 fields to new Data Dictionary nodes. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with IB*2*518. New fields are noted in the field list detail of this ICR. DSIV requests access to file 355.3 GROUP INSURANCE PLAN to do the following for its Insurance Capture Buffer (ICB) application: As a pointer directly to ^DIC(355.3 in ICB AUDIT FILE file (#19625) - GROUP PLAN IEN POINTER field (#4.14) Also these usages: ^IBA(355.3,D0,0) .01 INSURANCE COMPANY 0;1 Read w/FileMan .02 IS THIS A GROUP POLICY? 0;2 Read w/FileMan .03 *GROUP NAME 0;3 Read w/FileMan Note: IB*2*497 - replaced by GROUP NAME field (2.01) .04 *GROUP NUMBER 0;4 Read w/FileMan Note: IB*2*497 - replaced by GROUP NUMBER field (2.02) .05 IS UTILIZATION REVIEW REQUIRED 0;5 Read w/FileMan .06 IS PRE-CERTIFICATION REQUIRED? 0;6 Read w/FileMan .07 EXCLUDE PRE-EXISTING CONDITION 0;7 Read w/FileMan .08 BENEFITS ASSIGNABLE? 0;8 Read w/FileMan .09 TYPE OF PLAN 0;9 Read w/FileMan .1 INDIVIDUAL POLICY PATIENT 0;10 Read w/FileMan .11 INACTIVE 0;11 Read w/FileMan .12 AMBULATORY CARE CERTIFICATION 0;12 Read w/FileMan .13 PLAN FILING TIME FRAME 0;13 Read w/FileMan .15 ELECTRONIC PLAN TYPE 0;15 Read w/FileMan ^IBA(355.3,D0,2) 2.01 GROUP NAME 2;1 Read w/FileMan 2.02 GROUP NUMBER 2;2 Read w/FileMan ^IBA(355.3,D0,6) 6.02 BANKING IDENTIFICATION NUMBER 6;2 Read w/FileMan 6.03 PROCESSOR CONTROL NUMBER 6;3 Read w/FileMan ^IBA(355.3,D0,11,D1,0) .01 COMMENTS (WP) 0;1 FileMan read/write |
2014/02/21 | ||
| 5294 | INSURANCE BUFFER FILE ACCESS | File | INTEGRATED BILLING | 2008/11/23 | APPROVED | Active | Private | 355.33 | Update: IB*2*497 increased the length of the SUBSCRIBER ID field, NAME OF INSURED field, GROUP NAME field, and GROUP NUMBER field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 4 fields to new Data Dictionary nodes. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with IB*2*518 patch. New fields are noted in the field list detail of this ICR. DSIV requests access to file 355.33 INSURANCE BUFFER to do the following for its Insurance Capture Buffer (ICB) application to add/edit entries. ^IBA(355.33,D0,0) .01 DATE ENTERED 0;1 FileMan read/write .01 DATE ENTERED 0;1 Laygo new entry into file .02 ENTERED BY 0;2 FileMan read/write .03 SOURCE OF INFORMATION 0;3 FileMan read/write .04 STATUS 0;4 FileMan read .05 DATE PROCESSED 0;5 FileMan r,Direct Global r .06 PROCESSED BY 0;6 FileMan read .07 NEW COMPANY 0;7 FileMan read/write .08 NEW GROUP/PLAN 0;8 FileMan read/write .09 NEW POLICY 0;9 FileMan read/write .1 DATE VERIFIED 0;10 FileMan read/write .11 VERIFIED BY 0;11 FileMan read/write .12 IIV STATUS 0;12 FileMan read/write .13 OVERRIDE FRESHNESS FLAG 0;13 FileMan read .14 REMOTE LOCATION 0;14 FileMan read .15 IIV PROCESSED DATE 0;15 FileMan read .17 BPS RESPONSE 0;17 FileMan read ^IBA(355.33,D0,20) 20.01 INSURANCE COMPANY NAME 20;1 FileMan read/write 20.02 PHONE NUMBER 20;2 FileMan read/write 20.03 BILLING PHONE NUMBER 20;3 FileMan read/write 20.04 PRECERTIFICATION PHONE NUMBER 20;4 FileMan read/write 20.05 REIMBURSE? 20;5 FileMan read/write ^IBA(355.33,D0,21) 21.01 STREET ADDRESS [LINE 1] 21;1 FileMan read/write 21.02 STREET ADDRESS [LINE 2] 21;2 FileMan read/write 21.03 STREET ADDRESS [LINE 3] 21;3 FileMan read/write 21.04 CITY 21;4 FileMan read/write 21.05 STATE 21;5 FileMan read/write 21.06 ZIP CODE 21;6 FileMan read/write ^IBA(355.33,D0,40) 40.01 IS THIS A GROUP POLICY? 40;1 FileMan read/write 40.02 *GROUP NAME 40;2 FileMan read/write Note: IB*2*497 - replaced by field 90.01 40.03 *GROUP NUMBER 40;3 FileMan read/write Note: IB*2*497 - replaced by field 90.02 40.04 UTILITZATION REVIEW REQUIRED 40;4 FileMan read/write 40.05 PRECERTIFICATION REQUIRED 40;5 FileMan read/write 40.06 AMBULATORY CARE CERTIFICATION 40;6 FileMan read/write 40.07 EXCLUDE PREEXISTING CONDITION 40;7 FileMan read/write 40.08 BENEFITS ASSIGNABLE 40;8 FileMan read/write 40.09 TYPE OF PLAN 40;9 FileMan read/write 40.1 BANKING IDENTIFICATION NUMBER 40;10 FileMan read/write 40.11 PROCESSOR CONTROL NUMBER (PCN) 40;11 FileMan read/write ^IBA(355.33,D0,60) 60.01 PATIENT NAME 60;1 FileMan read/write 60.02 EFFECTIVE DATE 60;2 FileMan read/write 60.03 EXPIRATION DATE 60;3 FileMan read/write 60.04 *SUBSCRIBER ID 60;4 FileMan read/write Note: IB*2*497 - replaced by field 90.03 60.05 WHOSE INSURANCE 60;5 FileMan read/write 60.06 PT. RELATIONSHIP TO INSURED 60;6 FileMan read/write 60.07 *NAME OF INSURED 60;7 FileMan read/write Note: IB*2*497 - replaced by field 91.01 60.08 INSURED'S DOB 60;8 FileMan read/write 60.09 INSURED'S SSN 60;9 FileMan read/write 60.1 PRIMARY CARE PROVIDER 60;10 FileMan read/write 60.11 PRIMARY PROVIDER PHONE 60;11 FileMan read/write 60.12 COORDINATION OF BENEFITS 60;12 FileMan read/write 60.13 INSURED'S SEX 60;13 FileMan read/write 60.14 PT. RELATIONSHIP - HIPAA 60;14 FileMan read/write ^IBA(355.33,D0,61) 61.01 ESGHP? 61;1 FileMan read/write 61.02 SPONSORING EMPLOYER NAME 61;2 FileMan read/write 61.03 EMPLOYMENT STATUS 61;3 FileMan read/write 61.04 RETIREMENT DATE 61;4 FileMan read/write 61.05 SEND BILL TO EMPLOYER 61;5 FileMan read/write 61.06 EMPLOYER CLAIMS STREET LINE 1 61;6 FileMan read/write 61.07 EMPLOYER CLAIMS STREET LINE 2 61;7 FileMan read/write 61.08 EMPLOYER CLAIMS STREET LINE 3 61;8 FileMan read/write 61.09 EMPLOYER CLAIMS CITY 61;9 FileMan read/write 61.1 EMPLOYER CLAIMS STATE 61;10 FileMan read/write 61.11 EMPLOYER CLAIMS ZIP CODE 61;11 FileMan read/write 61.12 EMPLOYER CLAIMS PHONE NUMBER 61;12 FileMan read/write ^IBA(355.33,D0,62) 62.01 PATIENT ID 62;1 FileMan read/write ^IBA(355.33,D0,90) 90.01 GROUP NAME 90;1 FileMan read/write 90.02 GROUP NUMBER 90;2 FileMan read/write 90.03 SUBSCRIBER ID 90;3 FileMan read/write ^IBA(355.33,D0,91) 91.01 NAME OF INSURED 91;1 FileMan read/write "C" cross reference (Patient) Direct Global read "AEST" cross reference (Status) Direct Global read by Date Entered "E" entries |
2014/02/21 | ||
| 5296 | BILLING PATIENT ACCESS | File | INTEGRATED BILLING | 2008/11/23 | APPROVED | Active | Private | 354 | DSIV requests access to file 354 BILLING PATIENT to do the following for its Insurance Capture Buffer (ICB) application: ^IBA(354,DO) Direct global read ($D), lock/unlock ^IBA(354,D0,0) .01 PATIENT NAME 0;1 Filman read/write .01 PATIENT NAME 0;1 Laygo new entry ^IBA(354,D0,60) 60 NO COVERAGE VERIFICATION DATE 60;1 Fileman read/write |
2009/06/11 | ||
| 5297 | IIV RESPONSE ACCESS | File | INTEGRATED BILLING | 2008/11/24 | APPROVED | Active | Private | 365 | DSIV requests access to all fields in file #365 IIV RESPONSE to run an EIV Report for its Insurance Capture Buffer (ICB) application. |
2009/06/11 | ||
| 5298 | CLAIMS TRK REVIEW TYPE ACCESS | File | INTEGRATED BILLING | 2008/11/24 | APPROVED | Active | Private | 356.11 | The DSIV package is requesting FileMan read access to file #356.11 CLAIMS TRACKING REVIEW TYPE for the Insurance Capture Buffer application in order to list the review types for user selection in the insurance review add/edit. ^IBE(356.11,D0,0) .01 NAME 0;1 Read w/FileMan .02 CODE 0;2 Read w/FileMan |
2009/06/11 | ||
| 5299 | CLAIMS TRACKING ACTION ACCESS | File | INTEGRATED BILLING | 2008/11/24 | APPROVED | Active | Private | 356.7 | The DSIV package is requesting FileMan read access to file #356.7 CLAIMS TRACKING ACTION for the Insurance Capture Buffer application in order to list the actions for user selection in the insurance review add/edit. ^IBE(356.7,D0,0) .01 NAME 0;1 Read w/FileMan |
2009/06/11 | ||
| 5303 | DSIV INTEGRATED BILLING ACTION | File | INTEGRATED BILLING | 2008/11/24 | Withdrawn | Private | 350 | The DSIV package is requesting access to file #350 INTEGRATED BILLING ACTION for its Insurance Capture Buffer (ICB) application to search for all charges on hold due to insurance for a specific patient then update the On Hold Date to the current date, or send to the billing software to release the charges depending on the incoming flag. ^IB("AH" patient charges hold x-ref Direct Global read ^IB(D0,0) .05 STATUS 0;5 Direct Global read ^IB(D0,1) 16 ON HOLD DATE 1;6 Direct Global read, Fileman w |
||||
| 5304 | PATIENT INSURANCE ACCESS | File | INTEGRATED BILLING | 2008/11/24 | APPROVED | Active | Private | 2 | The DSIV package is requesting FileMan read access to the Insurance Type data in file #2 PATIENT for the Insurance Capture Buffer application in order to display insurance information to the user. IB*2*497 increased the length of the SUBSCRIBER ID field and the NAME OF INSURED field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 2 fields to new Data Dictionary nodes in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with a IB*2*518. Old and new fields are noted in the field list detail of this ICR. Update: IB*2*528 increased the length of the COMMENT-PATIENT POLICY field (2.312, 1.08) from 80 characters to 250 characters; and therefore it was necessary to move this field to a new subscript in the INSURANCE TYPE sub-file (2.312). All subscribers to this ICR will need to make the necessary changes in their applications to reference the new field. Old and new fields are noted in the INSURANCE TYPE multiple details below. ^DPT(D0,.31) .3192 COVERED BY HEALTH INSURANCE? .31;11 Fileman read/write insurance verification INSURANCE TYPE MULTIPLE access: ^DPT(D0,.312,D1,0) .01 INSURANCE TYPE 0;1 Read w/FileMan 1 *SUBSCRIBER ID 0;2 Read w/FileMan Note: IB*2*497 - Replaced by field 7.02 2 *GROUP NUMBER 0;3 Read w/FileMan 3 INSURANCE EXPIRATION DATE 0;4 Read w/FileMan 6 WHOSE INSURANCE 0;6 Read w/FileMan 8 EFFECTIVE DATE OF POLICY 0;8 Read w/FileMan 15 *GROUP NAME 0;15 Read w/FileMan 16 PT. RELATIONSHIP TO INSURED 0;16 Read w/FileMan 17 *NAME OF INSURED 0;17 Read w/FileMan Note: IB*2*497 - Replaced by field 7.01 .18 GROUP PLAN 0;18 Read w/FileMan .2 COORDINATION OF BENEFITS 0;20 Read w/FileMan ^DPT(D0,.312,D1,1) 1.01 DATE ENTERED 1;1 Read w/FileMan 1.02 ENTERED BY 1;2 Read w/FileMan 1.03 DATE LAST VERIFIED 1;3 Read w/FileMan 1.04 VERIFIED BY 1;4 Read w/FileMan 1.05 DATE LAST EDITED 1;5 Read w/FileMan 1.06 LAST EDITED BY 1;6 Read w/FileMan 1.08 *COMMENT - PATIENT POLICY 1;8 Read w/FileMan Note: IB*2*528 - 1.08 replaced by COMMENT-SUBSCRIBER POLICY multiple 1.09 SOURCE OF INFORMATION 1;9 Read w/FileMan 1.1 DATE OF SOURCE OF INFORMATION 1;10 Read w/FileMan ^DPT(D0,.312,D1,2) 2.01 SEND BILL TO EMPLOYER 2;1 Read w/FileMan 2.02 EMPLOYER CLAIMS STREET ADDRESS 2;2 Read w/FileMan 2.03 EMPLOY CLAIM ST ADDRESS LINE 2 2;3 Read w/FileMan 2.04 EMPLOY CLAIM ST ADDRESS LINE 3 2;4 Read w/FileMan 2.05 EMPLOYER CLAIMS CITY 2;5 Read w/FileMan 2.06 EMPLOYER CLAIMS STATE 2;6 Read w/FileMan 2.07 EMPLOYER CLAIMS ZIP CODE 2;7 Read w/FileMan 2.08 EMPLOYER CLAIMS PHONE 2;8 Read w/FileMan 2.015 SUBSCRIBER'S EMPLOYER NAME 2;9 Read w/FileMan 2.1 ESGHP 2;10 Read w/FileMan 2.11 EMPLOYMENT STATUS 2;11 Read w/FileMan 2.12 RETIREMENT DATE 2;12 Read w/FileMan ^DPT(D0,.312,D1,3) 3.01 INSURED'S DOB 3;1 Read w/FileMan 3.02 INSURED'S BRANCH 3;2 Read w/FileMan 3.03 INSURED'S RANK 3;3 Read w/FileMan 3.04 POLICY NOT BILLABLE 3;4 Read w/FileMan 3.05 INSURED'S SSN 3;5 Read w/FileMan 3.06 INSURED'S STREET 1 3;6 Read w/FileMan 3.07 INSURED'S STREET 2 3;7 Read w/FileMan 3.08 INSURED'S CITY 3;8 Read w/FileMan 3.09 INSURED'S STATE 3;9 Read w/FileMan 3.1 INSURED'S ZIP 3;10 Read w/FileMan 3.11 INSURED'S PHONE 3;11 Read w/FileMan 3.12 INSURED'S SEX 3;12 Read w/FileMan ^DPT(D0,.312,D1,4) 4.01 PRIMARY CARE PROVIDER 4;1 Read w/FileMan 4.02 PRIMARY PROVIDER PHONE 4;2 Read w/FileMan 4.03 PT. RELATIONSHIP - HIPAA 4;3 Read w/FileMan ^DPT(D0,.312,D1,5) 5.01 PATIENT ID 5;1 Read w/FileMan 5.02 SUBSCRIBER'S SEC QUALIFIER(1) 5;2 Read w/FileMan 5.03 SUBSCRIBER'S SEC ID(1) 5;3 Read w/FileMan 5.04 SUBSCRIBER'S SEC QUALIFIER(2) 5;4 Read w/FileMan 5.05 SUBSCRIBER'S SEC ID(2) 5;5 Read w/FileMan 5.06 SUBSCRIBER'S SEC QUALIFIER(3) 5;6 Read w/FileMan 5.07 SUBSCRIBER'S SEC ID(3) 5;7 Read w/FileMan 5.08 PATIENT'S SEC QUALIFIER(1) 5;8 Read w/FileMan 5.09 PATIENT'S SECONDARY ID(1) 5;9 Read w/FileMan 5.1 PATIENT'S SEC QUALIFIER(2) 5;10 Read w/FileMan 5.11 PATIENT'S SECONDARY ID(2) 5;11 Read w/FileMan 5.12 PATIENT'S SEC QUALIFIER(3) 5;12 Read w/FileMan 5.13 PATIENT'S SECONDARY ID(3) 5;13 Read w/FileMan ^DPT(D0,.312,D1,7) 7.01 NAME OF INSURED 7;1 Read w/FileMan 7.02 SUBSCRIBER ID 7;2 Read w/FileMan ^DPT(D0,.312,D1,13,D2,0) .01 COMMENT DATE 0;1 Read w/FileMan .02 LAST EDITED 0;2 Read w/FileMan ^DPT(D0,.312,D1,13,D2,1) .03 COMMENT 1;1 Read w/FileMan |
2017/07/24 | ||
| 5305 | SOURCE OF INFORMATION ACCESS | File | INTEGRATED BILLING | 2008/11/24 | APPROVED | Active | Private | 355.12 | The DSIV package is requesting FileMan read access to file #355.12 SOURCE OF INFORMATION for the Insurance Capture Buffer application in order to list the sources for user selection when creating a buffer entry. ^IBE(355.12,D0,0) .01 CODE 0;1 Read w/FileMan .02 DESCRIPTION 0;2 Read w/FileMan |
2009/06/11 | ||
| 5307 | DSIV CALLS TO IBCNBLL | Routine | INTEGRATED BILLING | 2008/12/10 | APPROVED | Active | Private | The Insurance Capture Buffer (ICB) application uses the following APIs in IBCNBLL to determine if there are bills on hold for a patient and to get the Symbol for the buffer entry. The symbol is displayed in the application and will also denote if the buffer entry has been manually verified. |
IBCNBLL | 2009/06/11 | ||
| 5309 | DSIV CALL TO IBCNERP2 | Routine | INTEGRATED BILLING | 2008/12/10 | APPROVED | Active | Private | The Insurance Capture Buffer (ICB) application uses the X12 API in IBCNERP2 to convert the X12 code to a readable format for a report. |
IBCNERP2 | 2009/06/11 | ||
| 5312 | PLAN LIMITATION CATEGORY ACCESS | File | INTEGRATED BILLING | 2008/12/10 | APPROVED | Active | Private | 355.31 | The DSIV package is requesting FileMan read access to file #355.31 PLAN LIMITATION CATEGORY for the Insurance Capture Buffer application in order to perform coverage limitation add/edits. ^IBE(355.31,D0,0) .01 NAME 0;1 Read w/FileMan |
2009/06/11 | ||
| 5313 | CLAIMS TRACKING ACCESS | File | INTEGRATED BILLING | 2008/12/10 | APPROVED | Active | Private | 356 | The DSIV package is requesting FileMan read access to file #356 CLAIMS TRACKING for the Insurance Capture Buffer application in order to look up and display a Claims Tracking record to be associated with an Insurance Review. ^IBT(356,D0,0) .01 ENTRY ID 0;1 Read w/FileMan .03 VISIT 0;3 Read w/FileMan .04 OUTPATIENT ENCOUNTER 0;4 Read w/FileMan .05 ADMISSION 0;5 Read w/FileMan .06 EPISODE DATE 0;6 Read w/FileMan .07 ADMISSION TYPE 0;7 Read w/FileMan .18 EVENT TYPE 0;18 Read w/FileMan .2 INACTIVE 0;20 Read w/FileMan .31 SPECIAL CONSENT ROI 0;31 Read w/FileMan |
2009/06/11 | ||
| 5314 | HOSPITAL TRACKING ACCESS | File | INTEGRATED BILLING | 2008/12/10 | APPROVED | Active | Private | 356.1 | The DSIV package is requesting FileMan read access to file #356.1 HOSPITAL TRACKING for the Insurance Capture Buffer application in order to look up and display a Hospital Tracking record to be associated with an Insurance Review as a Related Review. ^IBT(356.1,D0,0) .01 REVIEW DATE 0;1 Read w/FileMan .02 TRACKING ID 0;2 Read w/FileMan .07 SPECIALTY FOR REVIEW 0;7 Read w/FileMan .19 ACTIVE 0;19 Read w/FileMan .2 NEXT REVIEW DATE 0;20 Read w/FileMan .21 REVIEW STATUS 0;21 Read w/FileMan |
2009/06/11 | ||
| 5339 | ANNUAL BENEFITS ACCESS | File | INTEGRATED BILLING | 2009/01/12 | APPROVED | Active | Private | 355.4 |
The DSIV package is requesting FileMan read/write access to file #355.4 ANNUAL BENEFITS for the Insurance Capture Buffer application in order to add and edit entries. ^IBA(355.4,D0,0) .01 BENEFIT YEAR BEGINNING ON 0;1 FileMan read/write .01 BENEFIT YEAR BEGINNING ON 0;1 Laygo new entry into file .02 HEALTH INSURANCE POLICY 0;2 FileMan read/write .05 MAX. OUT OF POCKET 0;5 FileMan read/write .06 AMBULANCE COVERAGE (%) 0;6 FileMan read/write ^IBA(355.4,D0,1) 1.01 DATE ENTERED 1;1 FileMan read/write 1.02 ENTERED BY 1;2 FileMan read/write 1.03 DATE LAST VERIFIED 1;3 FileMan read 1.04 VERIFIED BY 1;4 FileMan read 1.05 DATE LAST EDITED 1;5 FileMan read 1.06 LAST EDIT BY 1;6 FileMan read 1.07 PERSON CONTACTED 1;7 FileMan read/write 1.08 COMMENTS 1;8 FileMan read/write 1.09 CONTACT'S PHONE NUMBER 1;9 FileMan read/write ^IBA(355.4,D0,2) 2.01 ANNUAL DEDUCTIBLE (OPT) 2;1 FileMan read/write 2.02 PER VISIT DEDUCTIBLE 2;2 FileMan read/write 2.03 OUTPATIENT LIFETIME MAXIMUM 2;3 FileMan read/write 2.04 OUTPATIENT ANNUAL MAXIMUM 2;4 FileMan read/write 2.05 MH LIFETIME OUTPATIENT MAX. 2;5 FileMan read/write 2.06 MH ANNUAL OUTPATIENT MAX. 2;6 FileMan read/write 2.07 DENTAL COVERAGE TYPE 2;7 FileMan read/write 2.08 DENTAL COVERAGE $ OR % 2;8 FileMan read/write 2.09 OUTPATIENT VISIT (%) 2;9 FileMan read/write 2.1 EMERGENCY OUTPATIENT (%) 2;10 FileMan read/write 2.11 MENTAL HEALTH OUTPATIENT (%) 2;11 FileMan read/write 2.12 PRESCRIPTION (%) 2;12 FileMan read/write 2.13 OUTPATIENT SURGERY (%) 2;13 FileMan read/write 2.14 MH OPT. MAX DAYS PER YEAR 2;14 FileMan read/write 2.15 OUTPATIENT VISITS PER YEAR 2;15 FileMan read/write 2.17 ADULT DAY HEALTH CARE 2;17 FileMan read/write ^IBA(355.4,D0,3) 3.01 HOME HEALTH CARE LEVEL 3;1 FileMan read/write 3.02 HOME HEALTH VISITS PER YEAR 3;2 FileMan read/write 3.03 HOME HEALTH MAX DAYS PER YEAR 3;3 FileMan read/write 3.04 HOME HEALTH MED. EQUIPMENT (%) 3;4 FileMan read/write 3.05 HOME HEALTH VISIT DEFINITION 3;5 FileMan read/write 3.06 OCCUPATIONAL THERAPY # VISITS 3;6 FileMan read/write 3.07 PHYSICAL THERAPY # VISITS 3;7 FileMan read/write 3.08 SPEECH THERAPY # VISITS 3;8 FileMan read/write 3.09 MEDICATION COUNSELING # VISITS 3;9 FileMan read/write ^IBA(355.4,D0,4) 4.01 HOSPICE ANNUAL DEDUCTIBLE 4;1 FileMan read/write 4.02 HOSPICE INPATIENT ANNUAL MAX 4;2 FileMan read/write 4.03 HOSPICE INPT. LIFETIME MAX 4;3 FileMan read/write 4.04 ROOM AND BOARD (%) 4;4 FileMan read/write 4.05 OTHER INPATIENT CHARGES (%) 4;5 FileMan read/write 4.06 IV INFUSION OPT. 4;6 FileMan read/write 4.07 IV INFUSION INPT. 4;7 FileMan read/write 4.08 IV ANTIBIOTICS OPT. 4;8 FileMan read/write 4.09 IV ANTIBIOTICS INPT. 4;9 FileMan read/write ^IBA(355.4,D0,5) 5.01 ANNUAL DEDUCTIBLE (INPATIENT) 5;1 FileMan read/write 5.02 PER ADMISSION DEDUCTIBLE 5;2 FileMan read/write 5.03 INPATIENT LIFETIME MAXIMUM 5;3 FileMan read/write 5.04 INPATIENT ANNUAL MAXIMUM 5;4 FileMan read/write 5.05 MH LIFETIME INPATIENT MAXIMUM 5;5 FileMan read/write 5.06 MH ANNUAL INPATIENT MAXIMUM 5;6 FileMan read/write 5.07 DRUG & ALCOHOL LIFETIME MAX 5;7 FileMan read/write 5.08 DRUG & ALCOHOL ANNUAL MAX 5;8 FileMan read/write 5.09 ROOM AND BOARD (%) (NJ3,0), 5;9 FileMan read/write 5.1 NURSING HOME (%) (NJ3,0), 5;10 FileMan read/write 5.11 MENTAL HEALTH INPATIENT (%) 5;11 FileMan read/write 5.12 OTHER INPATIENT CHARGES (%)) 5;12 FileMan read/write 5.14 MH INPT. MAX DAYS PER YEAR 5;14 FileMan read/write |
2009/06/11 | ||
| 5340 | INSURANCE REVIEW ACCESS | File | INTEGRATED BILLING | 2009/01/12 | APPROVED | Active | Private | 356.2 | The DSIV package is requesting FileMan read/write access to file #356.2 INSURANCE REVIEW for the Insurance Capture Buffer application in order to add and edit entries. ^IBT(356.2,D0,0) .01 REVIEW DATE 0;1 FileMan read/write .01 REVIEW DATE 0;1 Laygo new entry into file .02 TRACKING ID 0;2 FileMan read/write .03 RELATED REVIEW 0;3 FileMan read/write .04 TYPE OF CONTACT 0;4 FileMan read/write .05 PATIENT 0;5 FileMan read/write .06 PERSON CONTACTED 0;6 FileMan read/write .07 CONTACT PHONE # 0;7 FileMan read/write .08 INSURANCE COMPANY CONTACTED 0;8 FileMan read/write .1 APPEAL STATUS 0;10 FileMan read/write .11 ACTION 0;11 FileMan read/write .12 CARE AUTHORIZED FROM 0;12 FileMan read/write .13 CARE AUTHORIZED TO 0;13 FileMan read/write .14 DIAGNOSIS AUTHORIZED 0;14 FileMan read/write .15 DATES OF DENIAL FROM 0;15 FileMan read/write .16 DATES OF DENIAL TO 0;16 FileMan read/write .17 METHOD OF CONTACT 0;17 FileMan read/write .18 PARENT REVIEW 0;18 FileMan read/write .19 REVIEW STATUS 0;19 FileMan read/write .2 CASE PENDING 0;20 FileMan read/write .21 NO COVERAGE 0;21 FileMan read/write .22 FOLLOW-UP WITH APPEAL 0;22 FileMan read/write .23 TYPE OF APPEAL 0;23 FileMan read/write .24 NEXT REVIEW DATE 0;24 FileMan read/write .25 NUMBER OF DAYS PENDING APPEAL 0;25 FileMan read/write .26 OUTPATIENT TREATMENT 0;26 FileMan read/write .27 TREATMENT AUTHORIZED 0;27 FileMan read/write .29 FINAL OUTCOME OF APPEAL 0;29 FileMan read/write ^IBT(356.2,D0,1) 1.01 DATE ENTERED 1;1 FileMan read/write 1.02 ENTERED BY 1;2 FileMan read/write 1.03 DATE LAST EDITED 1;3 FileMan read/write 1.04 LAST EDITED BY 1;4 FileMan read/write 1.05 HEALTH INSURANCE POLICY 1;5 FileMan read/write 1.07 DENY ENTIRE ADMISSION 1;7 FileMan read/write 1.08 AUTHORIZE ENTIRE ADMISSION 1;8 FileMan read/write ^IBT(356.2,D0,2) 2.01 CALL REFERENCE NUMBER 2;1 FileMan read/write 2.02 AUTHORIZATION NUMBER 2;2 FileMan read/write ^IBT(356.2,D0,11,D1,0) .01 COMMENTS 0;1 FileMan read/write ^IBT(356.2,D0,12,D1,0) .01 REASONS FOR DENIAL 0;1 FileMan read/write ^IBT(356.2,D0,13,D1,0) .01 PENALTY 0;1 FileMan read/write .02 AMOUNT OF PENALTY 0;2 FileMan read/write ^IBT(356.2,D0,14,D1,0) .01 APPROVE ON APPEAL FROM 0;1 FileMan read/write .02 APPROVE ON APPEAL TO 0;2 FileMan read/write |
2013/03/22 | ||
| 5341 | PLAN COVERAGE LIMITATION | File | INTEGRATED BILLING | 2009/01/12 | APPROVED | Active | Private | 355.32 | The DSIV package is requesting FileMan read/write access to file #355.32 PLAN COVERAGE LIMITATION for the Insurance Capture Buffer application in order to add and edit entries. ^IBA(355.32,D0,0) .01 PLAN 0;1 FileMan read/write .01 PLAN 0;1 Laygo new entry into file .02 COVERAGE CATEGORY 0;2 FileMan read/write .03 EFFECTIVE DATE 0;3 FileMan read/write .04 COVERAGE STATUS 0;4 FileMan read/write ^IBA(355.32,D0,1) 1.03 DATE LAST EDITED 1;3 FileMan write 1.04 LAST EDITED BY 1;4 FileMan write ^IBA(355.32,D0,2,D1,0) .01 LIMITATION COMMENT 0;1 FileMan read/write |
2009/06/11 | ||
| 5353 | Accept/Reject Insurance Buffer data APIs | Routine | INTEGRATED BILLING | 2009/01/27 | APPROVED | Active | Private | This ICR provides APIs for the IB Insurance Application which will suppress the Write Statements and Interactive Fileman calls for the existing ACCEPT^IBCNBAR and REJECT^IBCNBAR logic. It includes logic to update the Patient Insurance Type (2.312) sub file with a new Group Insurance Plan and Insurance Company. There is also an API (UPDTICB) which will allow for fields that are not stored in the insurance buffer to be updated into the IB Insurance Files. Update: IB*2*528 increased the data length of the COMMENT-PATIENT POLICY field (2.312, 1.08) from 80 characters to 250 characters; and therefore a new DD definition COMMENT-SUSCRIBER POLICY (2.342) subfile was created to store the increased length and the history of comments entered. The UPDTICB component (API) will be affected by this change. All subscribers to this ICR will need to make the necessary changes in their applications to reference the new field. When all subscribers have implemented the use of the new fields, the old fields will need to be deleted with a subsequent IB patch. Old and new fields are noted at the UPDTICB component details. |
UPDTICB | 2009/06/11 | ||
| 5355 | BILL INFORMATION | Routine | INTEGRATED BILLING | 2009/02/02 | APPROVED | Active | Private | This APIs were created to provide detailed information about bills created for prescription/refills. |
IBNCPUT3 | 2010/08/25 | ||
| 5356 | BILL INFO | Routine | INTEGRATED BILLING | 2009/02/04 | Pending | Private | ||||||
| 5361 | IBOSRX | Routine | INTEGRATED BILLING | 2009/02/05 | APPROVED | Active | Controlled Subscription | This IA allows a subscribing package to call COLLECT^IBOSRX to identify and return potential secondary payer rx claims. |
IBOSRX | 2010/08/25 | ||
| 5389 | IBARXEU0 | Routine | INTEGRATED BILLING | 2009/03/16 | Withdrawn | Controlled Subscription | IBARXEU0 | |||||
| 5424 | INSURANCE FILING TIME FRAME | File | INTEGRATED BILLING | 2009/03/26 | APPROVED | Active | Private | 355.13 | The Insurance Capture Buffer application reads file #355.13 INSURANCE FILING TIME FRAME in order to display selections to the user and determine if time frame Values are needed. ^IBE(355.13,D0,0) .01 NAME 0;1 Fileman read .02 VALUE 0;2 Fileman read |
2009/06/11 | ||
| 5525 | DETERMINE COST OF COPAYMENT | Routine | INTEGRATED BILLING | 2010/03/02 | APPROVED | Retired | Private | AR package needs to determine the potential cost of a copayment bill. This DBIA will allow for lookup of the potential cost/charge. |
IBAUTL | 2010/03/03 | ||
| 5572 | IBNCPDPU | Routine | INTEGRATED BILLING | 2010/10/25 | APPROVED | Active | Private | This ICR provides access to data located in the GROUP INSURANCE PLAN file #355.3 that will allow the ECME package to determine the NCPDP version of a Payer Sheet. |
IBNCPDPU | 2011/01/18 | ||
| 5671 | COPY FUNCTIONS FOR IB EOB FILE #361.1 | Routine | INTEGRATED BILLING | 2011/05/11 | APPROVED | Active | Private | File 361.1 EXPLANATION OF BENEFITS is shared by Accounts Receivable and Integrated Billing. A/R already has full read access to the data in this file and options to add new entries. The additional functions defined below are required to allow AR to MOVE COPY, REMOVE or RESTORE erroneous entries in File 361.1 and update audit trail fields. |
IBCEOB4 | 2011/05/17 | ||
| 5710 | POTENTIAL COPAYMENT CHARGE AMOUNT | Routine | INTEGRATED BILLING | 2011/08/15 | APPROVED | Active | Private | This Integration Agreement will allow the AR package to look up a potential copayment charge amount based on the rate to be charged TODAY. |
IBAUTL | 2011/08/16 | ||
| 5711 | IB NCPDP EVENT LOG FILE | File | INTEGRATED BILLING | 2011/08/22 | APPROVED | Active | Private | 366.14 | The ECME package is performing direct global read-only access to the IB NCPDP EVENT LOG file (#366.14) for the purpose of generating data from the IB ECME EVENT LOG report to be included in the ECME report View ePharmacy Prescription. |
2011/09/14 | ||
| 5712 | PRINT IB ECME BILLING EVENTS REPORT | Routine | INTEGRATED BILLING | 2011/08/22 | APPROVED | Active | Private | The ECME report "View ePharmacy Rx" will include data from the IB ECME BILLING EVENT REPORT. The ECME report compile process will establish the necessary scratch global and set up the correct IB variables and will make a routine call to PRINT^IBNCPEV which will output the report to the open device. |
IBNCPEV | 2011/09/14 | ||
| 5713 | IB LIST MANAGER DISPLAY DATA | Routine | INTEGRATED BILLING | 2011/08/22 | APPROVED | Active | Controlled Subscription | This is a generic billing API which allows the subscribers to obtain the ListManager display array data from various IB ListManager list templates/screens. This IB API will return detailed billing information about TPJI third party bills and patient insurance policy information. The content of the data is strictly owned by IB and may be changed at any time. IB does not have to notify the subscribers that the content of the IB data which is to be returned to them may be changing. |
IBJTU6 | 2011/09/14 | ||
| 5714 | IB PHARMACY INSURANCE | Routine | INTEGRATED BILLING | 2011/08/22 | APPROVED | Active | Private | This IB API identifies all active pharmacy insurance policy data as of a given date of service and returns an array of insurance policies in COB (Coordination of Benefits) sequence order (primary, secondary, tertiary). |
IBNCPDPU | 2011/09/14 | ||
| 5715 | WITHDRAWN | INTEGRATED BILLING | 2011/08/22 | Withdrawn | ||||||||
| 5716 | WITHDRAWN | INTEGRATED BILLING | 2011/08/22 | Withdrawn | ||||||||
| 5717 | WITHDRAWN | INTEGRATED BILLING | 2011/08/22 | Withdrawn | ||||||||
| 5719 | WITHDRAWN | INTEGRATED BILLING | 2011/09/06 | Withdrawn | ||||||||
| 5721 | TPJI Comment Array | Routine | INTEGRATED BILLING | 2011/08/29 | Withdrawn | Private | The following subroutine call is made to the routine IBJTTC. The input IBIFN is the internal entry number of an entry in the BILL/CLAIMS (#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430) file. The subroutine will load the List Manager VALMAR array. |
IBJTTC | ||||
| 5722 | WITHDRAWN | INTEGRATED BILLING | Withdrawn | |||||||||
| 5806 | FB PROVIDER TO IB AUTOMATION | Routine | INTEGRATED BILLING | 2012/05/31 | APPROVED | Active | Private | This private agreement between FB and IB will allow Fee Basis to file Fee Vendor and 5010 Providers to the IB NON/OTHER VA BILLING PROVIDER (#355.93) file for paid Fee claims that are potentially billable by IB. The call is made during a nightly process (option FB PAID TO IB) within FB. |
IBCEP8C | 2012/07/11 | ||
| 5808 | INSURANCE MULTIPLE ACCESS | File | INTEGRATED BILLING | 2012/06/11 | Withdrawn | Private | 2.312 | The VA POINT OF SERVICE (KIOSK) package needs Fileman read access to the INSURANCE TYPE multiple of the PATIENT file (#2). The VPS GET PATIENT DEMOGRAPHIC remote procedure call will retrieve data from this multiple and return the data to the MDWS web service. MDWS will then push the data to the Vecna Kiosk located a the local VAMC. |
||||
| 6033 | IB BILL/CLAIMS PRESCRIPTION REFILL FILE ACCESS | File | INTEGRATED BILLING | 2014/03/25 | APPROVED | Active | Controlled Subscription | 362.4 | As part of the implementation of PRCA*4.5*298, the Accounts Receivable package is requesting read access to the BILL NUMBER (C) cross-reference and the zero node of IB BILL/CLAIMS PRESCRIPTION REFILL file (362.4). |
2014/06/12 | ||
| 6060 | IB CLAIM REJECT FLAG | Routine | INTEGRATED BILLING | 2014/05/23 | APPROVED | Active | Private | This function checks file #361 and returns a flag that indicates whether the bill that was input has a rejected status. Input: BILL - Bill number from #399 Output: REJECT - Reject status (blank = not found, 0 = not a reject, 1 = rejected) |
IBJTU6 | 2014/06/11 | ||
| 6061 | IBCNHUT1 (HPID/OEID) | Routine | INTEGRATED BILLING | 2014/05/28 | APPROVED | Active | Private | The purpose of the standardized HPID is to eliminate the ambiguity that presently exists in electronic standard healthcare transactions, and to streamline the numerous ways in which the term "health plan" is interpreted based on the different ways that health plans operate. This ambiguity undermines the value of electronic transactions by requiring repeated manual intervention. Both the IB and BPS (e-Claims Mgmt) namespaces will be displaying the HPID on various reports and screens, and BPS will need to be able to access the IB utility that was developed to find, validate and display the HPID for a particular health plan. The functions of IBCNHUT1 will return the HPID/OEID for an insurance company and validate that the HPID/OEID is in the correct format (10 numeric characters, 1st character is a 6 or 7 and the 10th character is the Luhn check-digit). |
IBCNHUT1 | 2014/06/19 | ||
| 6115 | IBA 354 | File | INTEGRATED BILLING | 2014/09/26 | Withdrawn | Controlled Subscription | 354 | |||||
| 6131 | IBNCPEV3 | Routine | INTEGRATED BILLING | 2014/11/20 | APPROVED | Active | Private | The ECME application requires access to the IB NCPDP EVENT LOG to extract data needed for the ECME Non-Billable Status Report. |
IBNCPEV3 | 2015/02/06 | ||
| 6136 | DB6136 | File | INTEGRATED BILLING | 2014/11/24 | APPROVED | Active | Private | 366.17 | The ECME application needs to extract the NON-BILLABLE REASON (#.01) field from the IB NCPDP NON-BILLABLE REASONS file. This is a read-only action and does not modify any fields in the file. The ECME application also requests lookup capabilities on the file via Fileman. No modification of the data will be done. |
2015/02/06 | ||
| 6142 | INSURANCE COMPANY LOOKUP | File | INTEGRATED BILLING | 2014/12/09 | APPROVED | Active | Private | 36 | Outpatient Pharmacy requires a lookup and extract on the NAME (#.01) field of the Insurance Company (#36) file via Fileman. No changes to the file will be made. |
2015/02/06 | ||
| 6143 | IB SITE PARAMETERS FILE ACCESS | File | INTEGRATED BILLING | 2015/01/08 | APPROVED | Active | Private | 350.9 | The Insurance Capture Buffer application reads file #350.9 IB SITE PARAMETERS to determine what field lengths the site wishes to use. |
2018/01/04 | ||
| 6208 | DB6208 | File | INTEGRATED BILLING | 2015/07/14 | APPROVED | Active | Private | 364 | The Accounts Receivable (AR) application needs to extract EDI transmission data from the EDI TRANSMIT BILL file (#364). This is a read-only action and does not modify any fields in the file. |
2015/08/06 | ||
| 6209 | DB6209 | File | INTEGRATED BILLING | 2015/07/14 | APPROVED | Active | Private | 364.1 | The Accounts Receivable (AR) application needs to extract the EDI transmission batch data from the EDI TRANSMISSION BATCH file (#364.1). This is a read-only action and does not modify any fields in the file. |
2015/08/06 | ||
| 6231 | Date of Death Triggers Insurance Termination | Routine | INTEGRATED BILLING | 2015/09/29 | APPROVED | Active | Controlled Subscription | A new style MUMPS cross reference is added to DATE OF DEATH field (#.351) in the Patient (#2) file which is invoked when the DATE OF DEATH is populated and has not previously been entered. The set code of this cross reference calls DEATH^IBCNEUT7. This IB code terms all of the patient's active insurance policies (without an expiration date). The term date is to be set to date of death. This functionality does not trump any existing or future validation/rules for the actual date of death. The patient insurance policies are stored in the INSURANCE TYPE (#2.312) subfile in the Patient (#2) file. |
IBCNEUT7 | 2016/01/08 | ||
| 6243 | EPHARMACY BILLABLE STATUS | Routine | INTEGRATED BILLING | 2015/10/06 | APPROVED | Active | Controlled Subscription | This function returns the ePharmacy Billable status to subscribing packages. The subscribing application shall pass in the PRESCRIPTION File #52 IEN and the BILLING ELIGIBILITY INDICATOR: TRICARE(T), CHAMPVA(C), or VETERAN(V) field of PRESCRIPTION file to make this determination. |
IBNCPDP | 2016/02/01 | ||
| 6244 | RETRIEVE SENSITIVE DIAGNOSIS DRUG FROM DRUG FILE | Routine | INTEGRATED BILLING | 2015/10/06 | APPROVED | Active | Controlled Subscription | This function returns the SENSITIVE DIAGNOSIS DRUG Field #87 from the DRUG File (#50) "EPH" node to subscribing packages. |
IBNCPDR | 2016/02/01 | ||
| 6250 | e-Pharmacy HL7 Processing | Routine | INTEGRATED BILLING | 2015/10/15 | APPROVED | Active | Controlled Subscription | ECME (Electronic Claims Management Engine) is the initial receiving point for incoming HL7 messages from FSC (Financial Services Center). When the system detects that an inbound MFN (Master File Notification) message is intended to update the IB (Integrated Billing) files of e-Pharmacy, then ECME makes the following calls into the IB processing routines to accomplish the task. |
IBCNRHLU | 2016/02/01 | ||
| 6391 | 6391 - Function INSUR in IBBAPI | Routine | INTEGRATED BILLING | 2016/03/10 | Withdrawn | Supported | Displays all insurance company information. |
IBBAPI | ||||
| 6392 | 6392 - IBFBUTIL FOR FEE BASIS | Routine | INTEGRATED BILLING | 2016/03/10 | APPROVED | Active | Private | Utility functions in Integrated Billing for use by Fee Basis. |
IBFBUTIL | 2016/05/09 | ||
| 6753 | OUTPATIENT PHARMACY BILL INQUIRY | Routine | INTEGRATED BILLING | 2017/03/29 | APPROVED | Active | Private | This allows users of the Patient Medication LM to do Bill Inquiry without leaving the List Manager. |
IBOLK | 2018/03/09 | ||
| 6768 | IBCEF75 PROVIDER ID APIS | Routine | INTEGRATED BILLING | 2017/06/19 | APPROVED | Active | Controlled Subscription | APIs that return Provider ID information. |
IBCEF75 | 2017/11/29 | ||
| 6891 | MVAH Insurance | File | INTEGRATED BILLING | 2018/03/21 | Pending | Controlled Subscription | 355.33 | This IA is for the mobilehealth package to be able to submit insurance information to the insurance buffer for processing |
||||
| 6906 | DBIA 6906 | File | INTEGRATED BILLING | 2018/04/10 | Pending | Private | 19625 | This ICR is used to file new insurance data fields from ICB to the DSIV ICB AUDIT (#19625) file that are not part of the INSURANCE BUFFER (#355.33) file so that they may be updated as part of buffer processing by insurance verifiers. |
||||
| 7007 | IBR TO RELEASE CHARGES FROM ACCOUNTS RECEIVABLE | Routine | INTEGRATED BILLING | 2019/01/17 | Pending | Private | The IB routine ^IBR can be used to release "ON HOLD" charges to ACCOUNTS RECEIVABLE (AR). E-Payments nightly process needs to use this call as part of the first party auto-decrease logic, so that first party charges can be released then auto-decreased when the matching third party bill is received. |
IBR | 2020/03/17 | |||
| 7010 | IBCN NEW INSURANCE | Other | INTEGRATED BILLING | 2019/01/24 | Pending | Controlled Subscription | The IBCN NEW INSURANCE event driver will be invoked whenever a new insurance type entry is created in the patient file, so that necessary actions can take place when a new insurance policy is added for a patient. This agreement 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. |
|||||
| 7017 | ERA DETAIL | File | INTEGRATED BILLING | 2019/02/07 | APPROVED | Active | Controlled Subscription | 361.1 | This IA will allow read and write access to the ERA DETAIL field (#104) in the EXPLANATION OF BENEFITS file (#361.1). This field is to be used to track Explanation of Benefits (EOB) data. The field label: ERA DETAIL 361.1,104 FREE TEXT Enter the ERA detail reference in the form nn,nnnnn, |
2020/03/17 | ||
| 7092 | IB CLAIM REJECT REVIEW INCOMPLETE | Routine | INTEGRATED BILLING | 2019/08/01 | Pending | Private | This function checks file #361 and returns a flag that indicates whether the bill has a reject message, where the review status is not complete. |
IBJTU6 | ||||
| 7202 | BILLING STATUS API | Routine | INTEGRATED BILLING | 2020/09/17 | APPROVED | Active | Private | This DBIA is for allowing the REGISTRATION package to call the EN^IBEFSMUT(DFN,BEGDT,ENDDT,LIST) entry point to return requested data elements stored in the INTEGRATED BILLING application. Listed below are the details on accessing this entry point and the data that should be returned. |
IBEFSMUT | 2021/02/18 | ||
| 7217 | DBIA7217 | File | INTEGRATED BILLING | 2021/01/22 | APPROVED | Active | Private | 399 | This integration agreement allows access to the following cross-reference within file 399: ^DGCR(399,"C" use of the "C" cross-reference for patient look-up and FileMan access to the fields listed below. |
2021/01/22 | ||
| 7218 | DBIA7218 | File | INTEGRATED BILLING | 2021/01/22 | APPROVED | Active | Private | 350 | This integration agreement allows FileMan access to the fields listed below. |
2021/01/22 | ||
| 7228 | SHRPE ACTIVATION DATE | File | INTEGRATED BILLING | 2021/02/17 | APPROVED | Active | Private | 350.9 | Accounts Receivable application needs to read the SHRPE activation date stored in the Integrated Billing file (#350.9) to determine when copays exemption rules and prorated RX copay amounts for patients with the High Risk for Suicide flag become applicable. |
2021/03/09 | ||
| 7238 | IB BILLING CLERK MENU Option | Other | INTEGRATED BILLING | 2021/04/01 | Pending | Private | Communication ICR: The RPA Revenue Operations Project developers have created a Robotic solution to replace a specific set of IB Clerk option steps to determine whether a patient should be billed. The RPA BOT project was written to utilize exact prompts available to a clerk, starting with the IB BILLING CLERK MENU option, which is the target option for this ICR. Background for project: The RPA Revenue Operations Project was approved by upper management for two bots to run a script to login (through WebVRAM) and then go to specific sites and run a couple IB and Accounts Receivable reporting options. The output of the first report is stored in a cloud and converted to excel as part of the bot processing from the first report run. Then the second option script is run, using the patients in the first report output to correct the billing status based on the Service Connected information. This ICR is a request for IB package developers to communicate with the RPA Project Manager (PM) when a patch that changes prompts related to the IB BILLING CLERK MENU option is within a month from going to IOC. This communication will help the RPA PM plan actions to minimize the impact on the RPA robotic functionality implemented at a site. The IB developers do not need to hold up the IB Agile development (IOC and release) to wait for the RPA BOT project to make software changes. The IB developers agree to provide the RPA BOT project manager with details about what has changed so the RPA BOT Team can assess impact and plan to coordinate changes to their product. |
|||||
| 7239 | IB CANCEL/EDIT/ADD CHARGES Option | Other | INTEGRATED BILLING | 2021/04/01 | Pending | Private | duplicate from 7238 |
|||||
| 7303 | LIGHTHOUSE INSURANCE COMPANY ICR | File | INTEGRATED BILLING | 2021/10/15 | Withdrawn | Private | 36 | Lighthouse requires access to the INSURANCE COMPANY file #36 to support the AMCMS/WellHive Insurance Capture initiative. |
||||
| 7304 | LIGHTHOUSE GROUP INSURANCE PLAN ICR | File | INTEGRATED BILLING | 2021/10/15 | Withdrawn | Private | 355.3 | Lighthouse requires access to the GROUP INSURANCE PLAN file #355.3 to support the AMCMS/WellHive Insurance Capture initiative. |
||||
| 7305 | LIGHTHOUSE PLAN COVERAGE LIMITATIONS ICR | File | INTEGRATED BILLING | 2021/10/15 | Withdrawn | Private | 355.32 | Lighthouse requires access to the PLAN COVERAGE LIMITATIONS file #355.32 to support the AMCMS/WellHive Insurance Capture initiative. |
||||
| 7306 | LIGHTHOUSE PAYER FILE ICR | File | INTEGRATED BILLING | 2021/10/15 | Withdrawn | Private | 365.12 | Lighthouse requires access to the PAYER file #365.12 to support the AMCMS/WellHive Insurance Capture initiative. |
||||
| 7307 | LIGHTHOUSE PATIENT INSURANCE TYPE SUBFILE ICR | File | INTEGRATED BILLING | 2021/10/15 | Withdrawn | Private | 2.312 | Lighthouse requires access to the Patient Insurance Type sub-file #2.312 to support the AMCMS/WellHive Insurance Capture initiative. |
||||
| 7308 | LIGHTHOUSE IIV RESPONSE FILE ICR | File | INTEGRATED BILLING | 2021/10/15 | Withdrawn | Private | 365 | Lighthouse requires access to the IIV RESPONSE file #365 to support the AMCMS/WellHive Insurance Capture initiative. |
||||
| 7318 | LIGHTHOUSE INSURANCE VERIFICATION PROCESSOR ICR | File | INTEGRATED BILLING | 2021/12/23 | Withdrawn | Private | 355.33 | Lighthouse requires access to the INSURANCE VERIFICATION PROCESSOR file #355.33 to support the AMCMS/WellHive Insurance Capture initiative. |
||||
| 7325 | DUPLICATE INSURANCE CHECK | Routine | INTEGRATED BILLING | 2022/02/02 | Withdrawn | Private | This routine provides a duplicate insurance check that is used by Lighthouse prior to writing potentially new insurance coverage to the Insurance Verification Processor file #355.33. |
IBLHS1 | ||||
| 7429 | Insurance Import Enabled Switch | File | INTEGRATED BILLING | 2023/07/13 | APPROVED | Active | Controlled Subscription | 350.9 | The Insurance Import Enabled switch lets the background job know whether the site is currently allowing insurance to be imported from other sites. |
2023/07/17 | ||
| 7473 | Import Insurance with CBOC Move | Routine | INTEGRATED BILLING | 2024/06/03 | APPROVED | Active | Private | Will initiate a %ZTLOAD call to BACKGND^IBCNRDV to retrieve insurance data from sites of record for brunswick cboc patients moved from Dublin to Charleston. This move will take place in Oct 2024. This ICR should expire 12/31/24. |
IBCNRDV | 2024/09/05 | ||
| 7525 | ACCESS TO VETERAN THIRD PARTY CHARGE REPORT | Other | INTEGRATED BILLING | 2025/03/18 | APPROVED | Active | Private | Allow access to the Veteran Third Party Charge Report [IB TP VETERAN CHRG RPT]. |
2025/03/20 | |||
| 7571 | DSIV X12 FILE 365.013 ACCESS | File | INTEGRATED BILLING | 2025/07/01 | Active | Private | 365.013 | This agreement allows INSURANCE CAPTURE BUFFER to read via FileMan fields needed to be displayed in a list to the user as well as filter out entries which are marked as INACTIVE?. |
||||
| 10145 | IBCNS1 | Routine | INTEGRATED BILLING | 1994/04/12 | Retired | Supported | IBCNS1 | |||||
| 10146 | IBCNS | Routine | INTEGRATED BILLING | 1994/04/12 | Retired | Supported | IBCNS | |||||
| 10147 | IBARXEU | Routine | INTEGRATED BILLING | 1994/04/12 | APPROVED | Active | Supported | IBARXEU |