national programs 13-0-1 release notes final

National Programs – 13.0.1 Release Notes

Release: 13.0

Initial Software Release Date: 11/08/2012

Software Implementation Date: 04/14/2013

Release Version: 13.0.1

Document Version: 1.1

Publication Date: 02/25/2013

Revised Publication Date:

Version

1.0

Created

02/21/2013

Revised

Authors

Blue Cross Blue Shield Association


Version 1.0

Created 02/21/2013

Revised:

QUESTIONS? CONTACT THE IPPT HELP DESK: 312.297.5500, [email protected] You are reminded that this material is the property of the Blue Cross and Blue Shield Association. Pursuant to the Inter-Plan Teleprocessing Services License Agreement, and the Amendment, the Consent and Confidentiality Agreement, and the Consent to Removal Agreement, this material is to be treated as confidential. J:\IPP-Tech\TECHBUL\Release_13.0\ Release Documents\National_Programs_13.0.1_Release_Notes.FINAL.doc

2 of 43

Revision History Date Version Description Author

02/21/2013 1.0 Initial Publication BCBSA

02/25/2013 1.1 Corrected file name in Appendix G BCBSA


Version 1.0

Created 02/21/2013

Revised:


3 of 43

Table of Contents

National Programs – 13.0.1 Release Notes .......... ................................................................................ 1

Introduction ...................................... ...................................................................................................... 6

Key Release Dates for 13.0 .................................................................................................................................. 6 About The Release Notes ..................................................................................................................................... 6

General Announcements ............................. .......................................................................................... 7

Enhancements ...................................... ................................................................................................. 8

e_82050 – DF Message Code 1050 and 1051 Edits ............................................................................................ 8 e_82376 – Minnesota Plan Code 724 Change ..................................................................................................... 8 e_82574 – Add New Place of Service (POS) Code 18 ......................................................................................... 9 e_81864 – Incorporate the Blue2 Reprocess Utility into the Core Blue2 Software ............................................ 10

Production Defects ................................ .............................................................................................. 11

ITS ...................................................................................................................................................................... 11 pd_67659 – Formats Purge Archive File Maintenance is Writing Empty Archive History .................................. 11 pd_72082 – Global Purge Restore Issue with Streamlined Adjustments ........................................................... 11 pd_74619 – DF Edits DA013 and DRL23 Errors in Real-Time ........................................................................... 11 pd_80076 – LDLA Transmit Special Notation Records When Indicator Has Space .......................................... 12 pd_80436 – ITMQGET1 is not Recognizing Failed Host SF's ........................................................................... 12 pd_80813 – Incorrect Job Return Code .............................................................................................................. 13 pd_81278 – ITCQ1000 - More instances of transactions being triggered than defined in MAX handle ............. 13 pd_81910 – S0C7 in Adjustment SF Compare Report ....................................................................................... 14 pd_81912 – Bad message length errors when extracting RTT SFs ................................................................... 14 pd_81923 – ITCA9024-01 Claims Admin SF Detail Missing Program Code ...................................................... 14 pd_81989 – Error Messages in Case of Real Time Abends ............................................................................... 15 pd_82220 – Unable to Release a Resubmit SF when a Valid SF and Invalid DF are Present .......................... 15 pd_82295 – Blue2 Failing to Display NF Details if Special Characters Present .................................................. 16 pd_82344 – DEN with Multiple Errors ................................................................................................................. 16 pd_82349 – Modifications to ITS Edit DRL2A ..................................................................................................... 16 pd_82387 – DEN Numbers P306 W002 Do Not Exist in Claims Admin ............................................................. 17 pd_82600 – Home SF’s Routed to Wrong Queue .............................................................................................. 18 pd_82756 – SF Message 1018 Not Removed When Released ......................................................................... 18 pd_82781 – Incomplete Special Notation Posting .............................................................................................. 18 pd_83690 – S0C7 Abend in IULP9144 ............................................................................................................... 19 Blue2 .................................................................................................................................................................. 19 pd_ 75394 – ‘Accommodation Rate’ Field is Misspelled ..................................................................................... 19 pd_ 80665 – Benefit Management Treatment Auth Numbers and Service Eligibility Code-Claim are not displayed correctly ......................................................................................................................................... 19 pd_ 81192 – Payer B Claim Adjustment Information is not displayed correctly in the Line of Service Tab ...................................................................................................................................................................... 20 pd_ 81518 – Other Physician Name and Other Physician Number are not Displaying Correctly ...................... 20 pd_ 81921 – ‘Estimate Indicator’ and ‘Reason Code’ are not displayed in the Dropdown Lists Correctly .............................................................................................................................................................. 21 pd_ 81922 – ‘Open/Closed’ Filter Resets to “Select One” in the Listing Search ................................................ 21 pd_ 81998 – Requested Attachment(s) are Not Displaying ................................................................................ 22 pd_ 82074 – Incorrect Error Message Displays for Claim Appeal Response ..................................................... 22 pd_ 83496 – Medical Record Comments are not displaying correctly ................................................................ 23


Version 1.0

Created 02/21/2013

Revised:


4 of 43

pd_ 83497 – Medical Record ‘Requested Information Source’ Value Displayed Incorrectly .............................. 23 pd_ 83498 – Medical Record Type Error Message is concatenated .................................................................. 24 Claims Admin ................................................................................................................................................. 24 pd_ 78927 – “Invalid” is missing from Message .................................................................................................. 24 pd_ 80251 – Search Results are not displayed correctly when searching by local Plan Receipt Date .............. 25 pd_ 81508 – Subscriber Zip Code Field does Not Display in OPL Payer A or Payer B Sub Tabs ..................... 25 pd_ 81776 – Claims Admin and Blue2 are Not Displaying Leading Spaces in the Special Notations Data Field ............................................................................................................................................................ 26 pd_ 81787 – ‘Administrative Expense Allowance’ is misspelled ......................................................................... 26 pd_ 81918 – Field is not highlighted for ITS Edit IPP02 ..................................................................................... 27 pd_ 82106 – Copy, Delete and Move Buttons are Disabled ............................................................................... 27 pd_ 82249 – Tooth Numbers between 01-09 Create ITS Edit PT080 ................................................................ 28 pd_ 83250 – OPL Payer B Information is displaying in OPL Payer A Fields ...................................................... 28 IPDS ................................................................................................................................................................... 29 N/A ....................................................................................................................................................................... 29 IPOR ................................................................................................................................................................... 29 PD_84137 : Open/Close information is not carried from Source DataMart to Target DataMart whenever a claim is opened/closed at the Source DataMart. ............................................................................. 29

Test Defects ...................................... ................................................................................................... 30

ITS ...................................................................................................................................................................... 30 td_81662 – Account Type Codes for OPM Multi-State ....................................................................................... 30 td_82365 – CBF Conversion Failure with Invalid Dates ..................................................................................... 30 td_82846 –CBFELOAD Failing ........................................................................................................................... 31 td_83030 –Network Availability not Highlighting ................................................................................................. 31 td_83447 – DF Claim Level Error vs Line Level ................................................................................................. 31 td_83499 – Count Field Size too Small ............................................................................................................... 32 td_83940 – ITMQGET1 Abend on Duplicate Records ........................................................................................ 32 td_84062 – The Transaction IRT0/IRT1 is Looping ............................................................................................ 33 td_84177 – HPA Edit UE089 Should Be Accompanied by FM003 ..................................................................... 33 td_84561 – CBF Unable to Change Sub Group and Bill End Date .................................................................... 34 Blue2 .................................................................................................................................................................. 35 td_82720 – Blue2: NASCO 13.0 Blue2 - Premature end of file error in log ........................................................ 35 td_83619 – User Incorrectly Able to View PQI Message Summary ................................................................... 35 Claims Admin ................................................................................................................................................. 35 Td_83158 – Blue2: Technical Defect: Claims Admin (SF) Not Launching with Special Multi-BOID Environment. ....................................................................................................................................................... 35 IPDS ................................................................................................................................................................... 36 N/A ....................................................................................................................................................................... 36 IPOR ................................................................................................................................................................... 36 TD_84118 : Change Blue2 DataMart extract file length to 2000 bytes ............................................................... 36

Issues ............................................ ....................................................................................................... 37

ITS ...................................................................................................................................................................... 37 i_82091 – ITS Blue2 Processing Times Need to be Available at the Hub ........................................................... 37 i_83845 – Utility to Provide Portability of ITS Formats Database ....................................................................... 37 i_84593 – Change to ITCDPT06 ......................................................................................................................... 38 Blue2 .................................................................................................................................................................. 38 N/A ....................................................................................................................................................................... 38


Version 1.0

Created 02/21/2013

Revised:


5 of 43

Claims Admin ................................................................................................................................................. 38 N/A ....................................................................................................................................................................... 38 IPDS ................................................................................................................................................................... 38 N/A ....................................................................................................................................................................... 38 IPOR ................................................................................................................................................................... 38 I_83612 : Retrofitting 12.3 changes in 13.0 code ............................................................................................... 38 I_84256 : DDL changes to use NOT LOGGED option in creating Level2 open fact tables. ............................... 39

Appendix A: Software Log .......................... ........................................................................................ 40

Appendix B: Metadata and Online Help .............. ................................................................................ 40

Metadata .......................................................................................................................................................... 40

Blue2 and Claims Administration Online Help..................................................................................... 40

Appendix C: Global Certification .................. ...................................................................................... 40

Appendix D: Update ITS Release dates in APPL_PARM 1 9 .............................................................. 40

Appendix E: New or Modified ITS Reports ........... .............................................................................. 40

Appendix F: New and Modified ITS Error Messages ... ...................................................................... 41

Appendix G: Datasets .............................. ............................................................................................ 41

Appendix H: DDLs .................................. ............................................................................................. 42

Plan Readiness & Defect Reporting ................. .................................................................................. 43


Version 1.0

Created 02/21/2013

Revised:


6 of 43

Introduction

This document details the scope of National Programs Release 13.0.1. This addendum release addresses changes to support issues, production and test defects, and enhancements. Additional detailed technical documentation regarding this release is posted on BlueWeb at National Programs Release 13.0. This release notes provide the information for ITS, Blue2, Claims Administration, IPDS Extract and IPOR.

Key Release Dates for 13.0

For this code release, partner Plan testing is required. Global Certification test cases have been published in Appendix C of the Release 13.0 Milestone Document located on Blue Web Doc ID 24421. All Plans are required to complete Global Certification testing prior to implementing Release 13.0 on April 14, 2013.

A summary of key dates is provided in the table below:

Milestones Key Dates

Beta (ITS and Blue2) Release of 13.0 to Plans 09/20/2012

General Release of 13.0 to All Plans 11/08/2012

Release 13.0.1 (Scheduled Addendum) to Plans 02/21/2013

Plan Implementation of Release 13.0 04/14/2013

About The Release Notes

Each section corresponding to enhancements, defects and issues contains a write-up providing the details of the topic. A separate document called the “Software Log” will be posted for ITS, IPDS Extract and IPOR Release 13.0. This Software Log is available on BlueWeb at National Programs Release 13.0.

If you have suggestions for improving the format of this document, please contact the IPPT Help Desk through the BCBSA Self-Service Portal at https://bcbsa.service-now.com or via email at [email protected] or by phone at 312 297 5500.

Your feedback is welcome and encouraged. The IPPT Help Desk can also assist you with any technical questions.


Version 1.0

Created 02/21/2013

Revised:


7 of 43

General Announcements

Documentation of software modifications for National Programs Release 13.0, will be available as of the November 08, 2012 release date. The following documents are also available for reference.

ITS User Manuals Blue2 13.0 User Manual and Blue2 Claims Administration 13.0 User Manual

The key business capabilities for this release are documented in the “National Programs Release 13.0 combined scope” document.

This Release 13.0 includes Data Definition Language (DDL) changes and is integrated tightly with Blue2. The DDL contains new data elements and changes to the database including (but not limited to) indexes to support the new functionality in this release. Please refer to Appendix H for list of DDL changes.

BlueWeb page 19077 includes a System Software Standards document which identifies the BCBSA-established standards for required system software packages used to support Inter-Plan Programs hosted application software and Inter-Plan Programs application software deployed at Plans, such as ITS, Blue², Claims Administration and various other software applications.


Version 1.0

Created 02/21/2013

Revised:


8 of 43

Enhancements

e_82050 – DF Message Code 1050 and 1051 Edits

Short Description Details

Ensure claims that have DF Message Codes 1050 or 1051 are rejected

In UAT testing it was discovered that DF message codes 1050 and 1051 were allowed at the line level for partially approved claims. An edit was created for this enhancement to prevent the use of the DF message codes 1050 and 1051 at the claim level when the “adjudication status” was other than rejected. Allowing these DF message codes at the line level on an “approved” claim negates the purpose of the e_51433 enhancement. Business Value: Provide consistency when using these two DF Message Codes, and supports the Blue strategic priority of improving efficiency and cost management. Plan Technical Impacts: None. Products Impacted: ITS

e_82376 – Minnesota Plan Code 724 Change


Plan Code 724 will be rolled in to Plan Code 720

Minnesota Plan Code 724 should be removed from Northern Plains Alliance Plan 019. For Performance Reporting it should be included with Minnesota Plan Code 720. Business Value: Effective 1/1/2013 Minnesota Plan Code 724 should be removed from Northern Plains Alliance Plan 019 and then roll Plan Code 724 into Minnesota Plan Code 720 for Performance Reporting. Plan Technical Impacts: None. Products Impacted: ITS


Version 1.0

Created 02/21/2013

Revised:


9 of 43

e_82574 – Add New Place of Service (POS) Code 18


Add POS code 18 specifically for physical therapy provided at a “place of employment worksite”.

With 11.3, the Place of Service (POS) Codes were placed on REFDATA (ITCDBD00) to be able to be updated off release. APTA's request for a new POS code to indicate that a physical therapist delivered services at a patient's worksite recently was granted by the Centers for Medicare and Medicaid Services (CMS). POS codes are 2-digit codes placed on health care claims to indicate the setting in which a service was provided. The new code is available for use effective January 1, 2013, but will not be effective for Medicare until May 1, 2013. The new code, POS 18, is named "place of employment-worksite". Per the description, the code should be used when physical therapy is delivered at “a location, not described by any other POS code, owned or operated by a public or private entity where the patient is employed, and where a health professional provides on-going or episodic occupational medical, therapeutic or rehabilitative services to the individual". Physical therapist delivering services that are appropriately reported using POS codes should check with payers to determine if they are prepared to accept POS 18. Examples of situations in which POS 18 can be used include, but are not limited to: − Job site analysis to identify potential accommodations -

patient present and participating in the service − Job coaching to improve biomechanics at the work site -

patient present and participating in the service − Physical therapy evaluation and treatment at the worksite − Functional capacity evaluations at the worksite to determine

the worker's ability to perform specific job duties

Currently, physical therapists are likely to report POS 99, known as "other place of service" when delivering services at the worksite. The addition of POS 18 will enable physical therapists, payers, and others using POS code data to more accurately identify where services are delivered. Health care Plans can use this information to implement payment differentials when providers are required to travel in order to deliver services, and to study the costs and benefits of alternative service delivery options. In its request to CMS for the new POS code, APTA noted that the provision of physical therapy (and other medical) services at the place of work reduces lost productivity, enhances the effectiveness of job-specific training, and improves access to services where transportation and other barriers may exist. The association also


Version 1.0

Created 02/21/2013

Revised:


10 of 43

told the agency that workers are more likely to receive the health care services they need in order to remain productive in the workforce when services are easily accessible. Additionally, job-specific evaluation and training services, including job and/or ergonomic analysis, must be performed at the work site and therefore are not appropriately reported using other place of service codes (except POS 99, which is nonspecific). CMS maintains POS codes used throughout the health care industry. Additional information about POS codes is available on CMS' website. CMS will publish a change request in the near future to inform payers of the change. Business Value: Plan Technical Impacts: The REFDATA file (ITCDBD00) must be downloaded for testing. Refer to Appendix G for details. Products Impacted: ITS

e_81864 – Incorporate the Blue2 Reprocess Utility i nto the Core Blue2 Software


Merge the Reprocess Utility into the Blue2 application.

TN plan requested to merge reprocess utility into Blue2 application since this utility is not optional any more. All plans are using this utility on regular basis. It will help plans to avoid separate deployment for reprocess utility and maintenance. Business Value:

This enhancement will eliminate the need for separate deployment and maintenance of the Blue2 Reprocess Utility. This enhancement supports the Blue strategic priority of improved efficiency and cost management. Plan Technical Impacts: It will require configuration changes on Plan Side. Products Impacted: Blue²


Version 1.0

Created 02/21/2013

Revised:


11 of 43

Production Defects

ITS pd_67659 – Formats Purge Archive File Maintenance i s Writing Empty Archive History


FDBRVRY3 writes empty Archive history file when input restore file is empty

In FDBRVRY3, Formats Purge Archive File Maintenance, is executed when a selective restore is being done, program ITCP9944 writes out an empty OHSTARCH file when IRESTORE is empty. The program is not completing this. Resolution Details: Set warning switch to ‘N’ prior to reading file. Plan Impacts: None.

pd_72082 – Global Purge Restore Issue with Streamli ned Adjustments


Streamlined Adjustment Restore Issue

An issue was noticed when a streamlined adjustment failed the Global Restore – 803 on insert to FMR_PRCS_CNTL table for original ‘00’ claims as it already has an entry. Except FMT_PRCS_CNTL table all rows were inserted/restored successfully. Plan can’t view them in ITFI, because of the wrong FMT_PRCS_CNTL entries. Resolution Details: If duplicate insert error encountered on insert, modify key and then insert. Plan Impacts: None.

pd_74619 – DF Edits DA013 and DRL23 Errors in Real- Time



Version 1.0

Created 02/21/2013

Revised:


12 of 43


When a Home DF that has a health care policy id on a line is created in real-time, it is failing the DF edits for DA013 and DRL23 errors.

When a Home DF that has a health care policy id on a line is created in real-time, it is failing the DF edits for DA013 and DRL23. Plan is receiving these errors even though the “Additional Line of Business” on the corresponding 4A record is populated with an "I" (major medical). When taking the real-time DF's and running them thru the DF edits in batch, the DF's go valid. The records are tabled in CIADF-4D-1-999-INST-SLOT. It also seems to only occur when the first line of the DF does not have a health care policy id on it but other lines do. Resolution Details: Modify setting of subscript. Plan Impacts: None.

pd_80076 – LDLA Transmit Special Notation Records W hen Indicator Has Space


LDLA Formats retrieval process is extracting and transmitting special notation records that should not be transmitted.

The LDLA program that retrieves the required SF and DF Formats pair from the Formats database does not omit special notation records that should not be transmitted. Special notation records are not included in the trailer record count for the SF, nor the DF. This happens only when the special notation transmission indicator (FM146-SPEC-NOTE-TRNSM-IND) is not set to a “N”. When the indicator is set to a “N”, the special notation records will not get transmitted. The records get transmitted when the indicator is set to a “Y” or “space”.

Resolution Details: Only move special notation when indicator is Y or space. Plan Impacts: None.

pd_80436 – ITMQGET1 is not Recognizing Failed Host SF's



Version 1.0

Created 02/21/2013

Revised:


13 of 43


ITMQGET1 not recognizing failed Host SFs.

While trying to extract Host SFs using ITMQGET1 and Host SF extract parameters (SF YYN 1QXXC QUEUE-NAME), the GET job is extracting HOME SF. The job should have extracted HOST SFs since it had DUMMY for HOME SF. Resolution Details: Reset Host/Home Code on failed transmissions. Plan Impacts: None

pd_80813 – Incorrect Job Return Code


Job issues Zero return code when it should be 3600.

If there is a bad SQL code while executing the FDB extract program ITCP2220, the sysout is displaying 3600 return code but the job is not having return code '3600'. Please refer to incident INC0026327 for more details.

Resolution Details: Return to calling program when fatal error encountered. Plan Impacts: None.

pd_81278 – ITCQ1000 - More instances of transaction s being triggered than defined in MAX handle


More instances of transactions being triggered than defined in MAX handle.

An issue was noticed where more number of ITRI transactions is being executed that what is defined in the MAX-HANDLES of appl parm 90 record. These results in CICS terminating any extra transactions based on the TCLAS parameter. Resolution Details: Changed check for MAX-HANDLES. Plan Impacts: None


Version 1.0

Created 02/21/2013

Revised:


14 of 43

pd_81910 – S0C7 in Adjustment SF Compare Report


S0C7 in adjustment SF Compare Report

Adjusted SF Compare Report program ITCP9068 is abending with S0C7 when comparing record type 65 and the actual ambulance mileage field (FM165-ACT-AMB-MILEAGE) has spaces in it. Resolution Details: Moved zero to ACT-AMB-MILEAGE if not numeric. Plan Impacts: None.

pd_81912 – Bad message length errors when extractin g RTT SFs


Bad message length errors are encountered when extracting RTT SFs.

This is an issue with the SAMMY module. Getting the error "message length errors” when extracting messages from RQ4L3A and RP4L3A queues with MQGETALL job when extracting RTT SFs. SAMMY does not adjust the message length after removing RFH2 header. It causes the MQGETALL job to issue the above errors.

Resolution Details: Recalculate the message length after removing RFH2 Header. Plan Impacts: None.

pd_81923 – ITCA9024-01 Claims Admin SF Detail Missi ng Program Code


Missing program code in ITCA9024-01 Claims Admin SF detail.

ITCA9024-01 the Claims Admin SF Detail (also see CA SF Inventory Summary) does not have the Program Code element as specified in the requirements.

Resolution Details: Added Program Code to report. Plan Impacts: None.


Version 1.0

Created 02/21/2013

Revised:


15 of 43

pd_81989 – Error Messages in Case of Real Time Aben ds


An issue was noted in Real Time processing, when Abends occur partial or no messages are being created in SAM or SAMMY

In case of any abend in real-time, only partial message is currently moved to the ERRL02 queue and could not be recovered for reprocessing. (Refer INC0033992 for additional information.)

SAM and SAMMY are supposed to preserve the input message when abend in ITDUTLS1 module. In case of abend in ITDUTLS1 module, SAM and SAMMY modules are not saving the input message in any queue. As a result all the messages are getting lost. (Refer INC0033987 for additional information.) Resolution Details: If abend in ITDUTLS1, set trigger OFF on the input queue. When putting message to the ERRL02 queue, do not recalculate the message length. Plan Impacts: None

pd_82220 – Unable to Release a Resubmit SF when a V alid SF and Invalid DF are Present


Plans are unable to Release a Resubmit SF (Batch or Real-Time) when Valid SF and Invalid DF present.

When valid SF carry invalid DF along, the system is unable to release a “resubmit” SF either in batch or real-time environment for both institutional and professional SFs. Instead, it displayed an error message:

− PXR53- A valid DF already exists on the Formats database for this “resubmitted” SF

− IXR53- A valid DF already exists on the Formats database for this “resubmitted” SF

Resolution Details: Issue IXR53/PXR53 only if DF on the FDB is valid. The valid DF is identified by the PTS LDLA DF Date on the FPCT table to be less than 9999-12-31. Plan Impacts: None.


Version 1.0

Created 02/21/2013

Revised:


16 of 43

pd_82295 – Blue 2 Failing to Display NF Details if Special Characters Present


Blue2 failing to display NF details if some special characters are present in NOTIF_TXT.

There are some cases where the details of NF records cannot be viewed in Blue2. When trying to obtain NF Detail, the system freezes and spins as if waiting to load. It was identified that this was due to the presence of some special characters in the NOTIF_TXT column of the NF table. In this case, the special character was X’41’.

Resolution Details: The NF Edits will replace any X’41’ character in the text field with spaces for all NF records. Plan Impacts: None.

pd_82344 – DEN with Multiple Errors


DEN with multiple errors not working correctly

When same DEN Number fields are present in many tabs, in such scenarios when an ITS Edit error occurs, application does not take the cursor to the first tab in error and also does not highlight all the fields in error.

Resolution Details: Changed file ITCDB110. Plan Impacts: None.

pd_82349 – Modifications to ITS Edit DRL2A



Version 1.0

Created 02/21/2013

Revised:


17 of 43


DF Edit DRL2A when charge and price amounts are zero on SF with 42 price method and multiple inclusive groupings.

As part of ITS Release 12.0, an ITS DF Edit ‘DRL2A’ was introduced. This edit is issued when all four amounts below are zero for an Inclusive Grouping Claim (Pricing Method = 42).

- Amount Approved to Pay - Patient Liability Amount - Payment Reduction Amount – Line (1 – 10) - Amount Paid Other Carrier

Plans have reported that there are claims where Charge and Price, both amounts are zero. The SF Edits allow such SFs as valid. If Charge and Price, both amounts are zero, it results all four amounts (as mentioned above) to be zeros on the DF and therefore we receive edit DRL2A. Resolution Details: Modified when DRL2A is issued. Plan Impacts: None.

pd_82387 – DEN Numbers P306 W002 Do Not Exist in Cl aims Admin


DEN numbers P306 and W002 do not exist in Claims Admin.

DEN numbers P306 and W002 do not exist in Claims Admin. Impacted ITS Edits are IRL3C, PRL2R and PP306. 1. ITS edit PP306 when occurs, the cursor is not placed is any field

nor any fields are highlighted. Per Claims Admin Data Dictionary document, the associated Den number is P306. The Den number P306 doesn't exist. But when National Provider Id field under Performing Provider tab was entered with a value, the ITS Edit PP306 got corrected. so the associated Den number must be P301.

2. ITS edit, which refer to Den number W002, doesn't exist on

Claims Admin SF. Impacted ITS edits are IRL3C and PRL2R. Resolution Details: Changed file ITCDB110. Plan Impacts: None.


Version 1.0

Created 02/21/2013

Revised:


18 of 43

pd_82600 – Home SF’s Routed to Wrong Queue


Corrected realtime processed SF routed to wrong queue.

Home SF's are routing to the wrong queue. This is happening if the SF is corrected (for the 1083 DF reject) with the new alpha prefix and processed on realtime. The application header is populated with the old control plan code/station code values and it is routed to wrong queue when released from claims admin.

Resolution Details: Use only SF fields to build application header. Plan Impacts: None.

pd_82756 – SF Message 1018 Not Removed When Release d


When an SF is released from Claim Admin, message code 1018 is not being removed

When released from Claims Admin the SF message code 1018 is not removed. If the same SF is processed on batch edit, SF message code 1018 is removed in the valid file

Resolution Details: Call ITCP9158 even if no info message only present. Plan Impacts: None.

pd_82781 – Incomplete Special Notation Posting


ITS not posting all Special Notations from Claim Admin

ITS is not properly posting all Special Notations that display in Claims Administration while creating a SF.

Resolution Details: Search all 999 occurrences of special notations. Plan Impacts: None.


Version 1.0

Created 02/21/2013

Revised:


19 of 43

pd_83690 – S0C7 Abend in IULP9144


IULP9144 using wrong subscript causing S0C7

ALIM module IULP9144 is getting S0C7 since wrong subscript is used in the program. Plan tried to correct the Program to use the correct subscript and tested fine.

Resolution Details: IULP9144 and IULP9294 were both changed to use correct subscript. Plan Impacts: None.

Blue2

pd_ 75394 – ‘Accommodation Rate’ Field is Misspelle d


‘Accommodation Rate’ Field is Misspelled

The Accommodation Rate field is spelled incorrectly as ‘Accomodation’ Rate in the DF Line of Service tab in Blue2. Resolution Details: JSP files were modified to fix the issue. Plan Impacts: None.

pd_ 80665 – Benefit Management Treatment Auth Numbe rs and Service Eligibility Code-Claim are not displayed correctly



Version 1.0

Created 02/21/2013

Revised:


20 of 43


Benefit Management Treatment Auth Numbers and Service Eligibility Code-Claim are Not Displayed Correctly

Blue2 displays only the first occurrence of the Benefit Management Treatment Auth Number from the CLM_SUB_INST table in the Institutional SF details page. If the second and/or third occurrence is populated on the SF, they are not displayed. Also, the fourth occurrence of the Service Eligibility Code-Claim (S008) is not displaying in the Professional SF details page. Resolution Details: JSP files and Schema for Data objects was modified to fix the issue. Plan Impacts: None.

pd_ 81192 – Payer B Claim Adjustment Information is not displayed correctly in the Line of Service Tab


Payer B Claim Adjustment Information is Not Displayed Correctly in the Line of Service Tab

When the SF contains Payer B Claim Adjustment information without the OPL Value Codes, the Payer B Claim Adjustment information is not viewable in the Line of Service tab when the user first clicks on the line number in Blue². The information is viewable when the user clicks a second time. Resolution Details: Struts Action class was modified to fix the issue. Plan Impacts: None.

pd_ 81518 – Other Physician Name and Other Physicia n Number are not Displaying Correctly



Version 1.0

Created 02/21/2013

Revised:


21 of 43


Other Physician Name and Other Physician Number are not Displaying Correctly

For Professional SF, the Other Physician Name and Other Physician Number are not displaying in the Member and Provider tab, Other Physician Details section in Blue2.

Resolution Details: Schema for Data Objects, SDO utility was modified to fix the issue. Plan Impacts: None.

pd_ 81921 – ‘Estimate Indicator’ and ‘Reason Code’ are not displayed in the Dropdown Lists Correctly


‘Estimate Indicator’ and ‘Reason Code’ are Not Displayed in the Dropdown Lists Correctly

‘Estimate Indicator’ dropdown is incorrectly displayed as enabled when the user returns to the Listing tab with the "Return to Listing Search Results" link from either the SCCF History or Create New Message tab. Also, ‘Reason Code’ dropdown is incorrectly displayed as "Select One" when the user returns to the Listing tab with the "Return to Listing Search Results" link from either the SCCF History or Create New Message tab. Resolution Details: JSP file modified to fix the issue. Plan Impacts: None.

pd_ 81922 – ‘Open/Closed’ Filter Resets to “Select One” in the Listing Search



Version 1.0

Created 02/21/2013

Revised:


22 of 43


‘Open/Closed’ Filter Resets to “Select One” in the Listing Search

When the user selects “Unknown” for the ‘Open/Closed’ filter to perform a Listing search and then selects the “Return to Listing Search Results” link, the ‘Open/Closed’ filter resets to “Select One” instead of maintaining the user selection of “Unknown”.

Resolution Details: JSP was modified to fix the issue. Plan Impacts: None.

pd_ 81998 – Requested Attachment(s) are Not Display ing


Requested Attachment(s) are Not Displaying

The requested attachment(s) are not displaying on the General Inquiry, PQI and Claim Misroute response data entry pages, under the sections titled “General Inquiry Request”, “PQI Request” and “Claim Misroute Detail”. If an attachment exists for these messages, Blue2 must display the attachment on the message response data entry page. Resolution Details: JSP, Java Script and Action class was modified to fix the issue. Plan Impacts: None.

pd_ 82074 – Incorrect Error Message Displays for Cl aim Appeal Response



Version 1.0

Created 02/21/2013

Revised:


23 of 43


Incorrect Error Message Displays for Claim Appeal Response

When the user attempts to send a Claim Appeal response message where the ‘Response Reason’ field is blank, Blue2 incorrectly displays “Response is required”, instead of “Response Reason is required”.

Resolution Details: Xml file was modified to fix the issue. Plan Impacts: None.

pd_ 83496 – Medical Record Comments are not display ing correctly


Medical Record Comments are Not Displaying Correctly

When there is a line break in the text, Blue2 will not allow the pasting of the comments in the Comments field for the Medical Record Request and Response messages. In addition, the user is unable to paste the text in the Cancel Comments field for a cancellation message. Blue2 will allow only the characters before the line break to paste into the Comments and Cancel Comments fields. Resolution Details: JSP files modified to fix the issue. Plan Impacts: None.

pd_ 83497 – Medical Record ‘Requested Information S ource’ Value Displayed Incorrectly



Version 1.0

Created 02/21/2013

Revised:


24 of 43


Medical Record ‘Requested Information Source’ Value Displayed Incorrectly

The ‘Requested Information Source’ value is concatenated on the Medical Record Response data entry page in Blue2. For example, “Rendering Provider” is reading as “RenderingProvider”. Resolution Details: A Builder class was modified to fix the issue. Plan Impacts: None.

pd_ 83498 – Medical Record Type Error Message is co ncatenated


Medical Record Type Error Message is Concatenated

When the “No Attachment Included” checkbox is selected, but comments are not included on a Medical Record Response, Blue2 displays an error message with a concatenated Medical Record Type. For example, instead of “Comments are required for Medical Record Type Emergency Services”, Blue2 is displaying “Comments are required for Medical Record Type EmergencyServices”. Resolution Details: Validator and Utility classes modified to fix the issue. Plan Impacts: None.

Claims Admin pd_ 78927 – “Invalid” is missing from Message



Version 1.0

Created 02/21/2013

Revised:


25 of 43


For the ITS edit IPP02, the corresponding field is not highlighted in Claims Admin.

When the user releases an SF that fails an edit(s), Claims Admin incorrectly displays “The SF is being held in the Suspense Database [SCCF Number]”, instead of “The invalid SF is being held in the Suspense Database [SCCF Number]”.. Resolution Details: Action scripts, xml modified to fix the issue. Plan Impacts: None.

pd_ 80251 – Search Results are not displayed correc tly when searching by local Plan Receipt Date


Search Results are Not Displayed Correctly when Searching by Local Plan Receipt Date

When the user performs a suspense search for an SF in Claims Admin using the Local Plan Receipt Date as a filter, the results are displayed based on the date parameters as determined by the user’s desktop time zone instead of the configured time zone. Resolution Details: Action scripts and utility java classes modified to fix the issue. Plan Impacts: None.

pd_ 81508 – Subscriber Zip Code Field does Not Disp lay in OPL Payer A or Payer B Sub Tabs



Version 1.0

Created 02/21/2013

Revised:


26 of 43


For the ITS edit IPP02, the corresponding field is not highlighted in Claims Admin.

For Institutional SFs, the Subscriber Zip Code field displays in the Member tab, Subscriber sub-tab, but not in the OPL tab, Payer A or Payer B sub-tabs. If an SF is created with data in the Subscriber Zip Code fields for Payer A or Payer B incorrectly, users have no way to access to this field(s) in Claims Admin in order to remove the data. Resolution Details: A mxml file was modified to fix the issue. Plan Impacts: None.

pd_ 81776 – Claims Admin and Blue 2 are Not Displaying Leading Spaces in the Special Notations Data Field


Claims Admin and Blue2 are Not Displaying Leading Spaces in the Special Notations Data Field

If there are leading spaces in the Special Notations Data field of the SF, the spaces are retained on the physical records and database tables but not displayed on the SF in Claims Admin or Blue2.

Resolution Details: Action scripts, mxml files, Xml utility, String converter Java classes modified to fix the issue. Plan Impacts: None.

pd_ 81787 – ‘Administrative Expense Allowance’ is m isspelled



Version 1.0

Created 02/21/2013

Revised:


27 of 43


‘Administrative Expense Allowance’ is misspelled

For Institutional SF, the ‘Administrative Expense Allowance’ field is misspelled as ‘Adminstrative Expense Allowance’ on the Claim tab, Claim Pricing sub-tab. Resolution Details: A mxml file was modified to fix the issue. Plan Impacts: None.

pd_ 81918 – Field is not highlighted for ITS Edit I PP02


Field is not highlighted for ITS Edit IPP02

When the ITS Edit IPP02 ‘KEY FIELD FOR PLAN PROFILE ACCESS IN ERROR’ is displayed and the user selects the edit, Claims Admin does not highlight the Group Number field on the Member tab, Subscriber sub tab.

Resolution Details: Mxml and action scripts modified to fix the issue. Plan Impacts: None.

pd_ 82106 – Copy, Delete and Move Buttons are Disab led


Copy, Delete and Move Buttons are Disabled

When the user first enters the SF Details page, the Copy, Delete and Move buttons remains disabled under the Line of Service tab in Claims Admin. The buttons are enabled after the user click on multiple line numbers when creating the SF.

Resolution Details:


Version 1.0

Created 02/21/2013

Revised:


28 of 43


Action scripts and mxml files modified to fix the issue. Plan Impacts: None.

pd_ 82249 – Tooth Numbers between 01-09 Create ITS Edit PT080


Tooth Numbers Between 01-09 Create ITS Edit PT080

When the user selects a tooth number from the drop down list between the numeric values of ‘01’ to ‘09’, Claims Admin displays ITS Edit PT080 ‘IF PRESENT, TOOTH NUMBER-CLM MUST = 1-32 OR A-T’. There is no ITS edit when the user manually enters the tooth number without the leading zeros (1, 2, 3…9).

Resolution Details: Claims Admin reference Data xml was modified to fix this issue. Plan Impacts: None.

pd_ 83250 – OPL Payer B Information is displaying i n OPL Payer A Fields


OPL Payer B Information is Displaying in OPL Payer A Fields

When the user keys data into the OPL Payer B fields, but leaves the OPL Payer A fields blank, the data originally keyed into the OPL Payer B detail sub tab displays in the OPL Payer A detail sub tab. However, the data originally keyed in the OPL Payer B tab, Claim Adjustment sub tab remains in the OPL Payer B tab, Claim Adjustment sub tab.


Version 1.0

Created 02/21/2013

Revised:


29 of 43


Resolution Details: Action class, SDO utility class, constants and JSP was modified to fix the issue. Plan Impacts: None.

IPDS N/A

IPOR PD_84137 : Open/Close information is not carried fr om Source DataMart to Target DataMart whenever a claim is opened/closed at the S ource DataMart.


Open/Close information is not carried from Source DataMart to Target DataMart when ever a claim is opened/closed at the Source DataMart.

When any existing open claim is closed in the source DataMart during daily IPOR load, that information (open to close) is not carried from source DataMart to target DataMart in the daily ITS DataMart export/import process. Due to this there will be claims closed in source DataMart but still open in the target DataMart. Resolution Details: Set the audit_updt_ts to current timestamp whenever IPOR DataMart is updated. Plan Impacts:

1. Programs IPORDDFL, IPORDSFL, IPOROCLD, IPORRFLD and IPORCLDT are changed, Install changed programs.

2. Run one time fix job IPORADUP at source DataMart only


Version 1.0

Created 02/21/2013

Revised:


30 of 43

Test Defects

ITS td_81662 – Account Type Codes for OPM Multi-State


Account Type Codes for OPM Multi-State

In 13.0, in the BlueCard for Exchanges enhancement, business had asked for two Account Type Codes be reserved for OPM Multi-State. These were not done within the software, because there were many unknowns at that time. For OPM Multi-State, these Account Type Codes will need to be available in Plan Profile prior to the implementation of 13.5 Resolution Details: Account Types G and H were added as valid values in the Plan Profile online application. Plan Impacts: None.

td_82365 – CBF Conversion Failure with Invalid Date s


CBF Conversion failure with invalid dates

When invalid dates exist on CBF records being converted to DB2, the ITCV9300 job is failing with “3600”. In the example reported by Beta Plans, they had numerous CBF records on their database with a Billing End Date of 2/29/2011 which is an invalid date. The job is abending due to a bad return code from DB2 when trying to insert the invalid date into the database. The conversion software was unable to handle the bad data.

Resolution Details: Modified date edit for leap year. Plan Impacts: None.


Version 1.0

Created 02/21/2013

Revised:


31 of 43

td_82846 –CBFELOAD Failing


Empty file causing CBFELOAD to fail

CBFELOAD is failing with 3600 if the input file is empty.

Resolution Details: Initialized error code during initialization process. Plan Impacts: None.

td_83030 –Network Availability not Highlighting


Network Availability field not highlighting on PRL1Q

As per the definition, when edit PRL1Q is triggered highlight and place the cursor on Class of Provider - Claims (C023). Also highlight in the following order Network Availability (P096), Account Type Code (A008), Provider Type Availability (P171) and Class of Provider - Line (C052). But Network Availability is not highlighting when setting the PRL1Q. Cursor placement is correct and all other fields are highlighting

Resolution Details: Changed file ITCDB110. Plan Impacts: None.

td_83447 – DF Claim Level Error vs Line Level


Claim Level DF errors setting with line level errors

In 13.0 several new claim level only DF messages have been added (e_66016 added 1290 - 1292 and e_51433(e_82050) changed 1050 - 1051 to claim level only). ALIM needs to be able to reject a claim using both a full claim reject (90) and using L1/L2/L3 calls. When L1/L2/L3 calls are used, each L2 line call will pass the DF Message Code set to 1290-1292 or 1050-1051 with the line set to non-covered. The finalization call will set the claim to rejected and set the claim DF Message Codes from the line DF Message Codes. Currently, UE018 is being issued on the L2 call when 1290-1292 or 1050-1051 are being set at the line level because they are now


Version 1.0

Created 02/21/2013

Revised:


32 of 43


defined as claim level only. Processing needs to be changed to bypass UE018 on claim level only DF Message Codes for ALIM L2 calls (IUCP9132) and the ALIM L3 build module needs to clear the claim level only DF Message Codes from the line after they have been rolled to the claim level (IULP9308).

Resolution Details: Change assignment of error for line level vs claim level. Plan Impacts: None.

td_83499 – Count Field Size too Small


Record Count field needs to be expanded

In program ITCV9300 record count's are defined as 5 byte field, so the counts will not be displayed correctly in the report if there are more than 99,999 input records

Resolution Details: Increase size of counters. Plan Impacts: None.

td_83940 – ITMQGET1 Abend on Duplicate Records


Duplicate SF on queue causes ITMQGET1 to abend

When extracting the duplicate SF's from Input Queue, the ITMQGET1 job abended and Job got return code of 3600 because BAD INSERT INTO EVENT LOG table. Also EVENT_TS column is populated with local (not GMT like all other events) time for events 306 and 506.

Resolution Details: When -803 received on INSERT, change timestamp and then do another INSERT. Also populate the EVENT_TS column with GMT time for event 306 and 506. Plan Impacts:


Version 1.0

Created 02/21/2013

Revised:


33 of 43


None.

td_84062 – The Transaction IRT0/IRT1 is Looping


MQ error prior to message being extracted.

The problem occurs when RT/MLE process is invoked by IRT0 transaction and MQ error happens before a message has been extracted by SAM from the input queue. For example Input queue is REQL01, the system attempts to open all the RT/MLE related queues and RQ4L03 is not defind. It'll cause an infinite loop. Resolution Details:

Check Trigger Control and stop if OFF. Plan Impacts: None.

td_84177 – HPA Edit UE089 Should Be Accompanied by FM003


HPA edit UE089 should be accompanied by FM003 (SINF record not found on the Formats database for streamlined adjustment errors)

7.2.1. Create an HPA Edit, UE089 to issue an error when attempting to reject a Re-Issue DF (Adjudication Status Indicator (A015) equals "2") when the prior DF was approved (Adjudication Status Indicator (A015) equals "1"). UE089 - PREV APPROVED CLAIM CANNOT BE REJECTED THROUGH STREAMLINED ADJUSTMENT _ If Release Number is equal to or greater than 13.0.If the Adjudication Status Indicator (A015) on the prior DF is equal


Version 1.0

Created 02/21/2013

Revised:


34 of 43


to "1" (Paid). _ If Adjudication Status Indicator (A015) on the Re-issue DF is equal to "2" (Rejected). _ If Streamline Adjustment Indicator (S089) is equal to "Y". HPA edit 'UE089' should be accompanied by FM003 "SINF record not found on the Formats database for streamlined adjustment errors". When a user attempts to process a streamlined adjustment that fails based on the criteria in UE089, they should not only get the UE089 error message but the FM003 should precede the UE089. When an adjustment does not meet the streamlined adjustment criteria, HPA sets error message FM003. In addition to the FM003 HPA may also return additional messages with indicate why the streamlined adjustment could not be performed.

Resolution Details: Issue FM003 when UE089 is issued. Plan Impacts: None.

td_84561 – CBF Unable to Change Sub Group and Bill End Date


Can no longer change the CBF Sub Group Number and Bill End Date

Plans use to be able to do an online change to the CBF Sub Group Number and Bill End Date. They are not able to do this any longer. Resolution Details: Modified software to allow these fields to be updated. Plan Impacts: None.


Version 1.0

Created 02/21/2013

Revised:


35 of 43

Blue2 td_82720 – Blue2: NASCO 13.0 Blue2 - Premature end of file error in log


Blue2: NASCO 13.0 Blue2 - Premature end of file error in log

After installing 13.0 , Blue2 continuously started logging Premature end of file errors in log Resolution Details: A java utility class was modified to fix the issue. Plan Impacts: None.

td_83619 – User Incorrectly Able to View PQI Messag e Summary


User Incorrectly Able to View PQI Message Summary.

A user is able to view a PQI message summary without the PQIMsgUser and PQIMsgSummaryUser user security roles. A user should not be able to view a PQI message summary if the above noted user security roles are not applied to the user account. Resolution Details: An Action class was modified to fix the issue. Plan Impacts: None.

Claims Admin Td_83158 – Blue2: Technical Defect: Claims Admin (S F) Not Launching with Special Multi-BOID Environment.



Version 1.0

Created 02/21/2013

Revised:


36 of 43


Technical Defect: Claims Admin (SF) Not Launching with Special Multi-BOID Environment.

The "Claims Admin" button is not displaying properly with certain environmental configurations. The user is unable to log into Claims Administration (SF) via Blue², even for a BOID where Claims Administration is enabled. Resolution Details: A java utility class was modified to fix the issue. Plan Impacts: None.

IPDS N/A

IPOR TD_84118 : Change Blue2 DataMart extract file lengt h to 2000 bytes


Blue2 DataMart extract file length should be changed from 1996 bytes to 2000 bytes in DataMart export/import process.

In 13.0 when new fields are added to Blue2 DataMart, they are added to Blue2 DataMart extract file layout also. Field Provider Name is incorrectly added as 36 byte field when it is a 40 byte field. Due to this total file length has to be changed from 1996 bytes to 2000 bytes. Resolution Details: Change Blue2 DataMart extract file length from 1996 to 2000 bytes. Plan Impacts:

1. Programs IPORDEXT, IPORDLOD, IPORIEX2, IPORILD1 are changed, install changed programs.

2. JCLs IPORDEXT and IPORIEXT are changed, install changed JCLs.


Version 1.0

Created 02/21/2013

Revised:


37 of 43

Issues

ITS i_82091 – ITS Blue 2 Processing Times Need to be Available at the Hub


ITS - Blue2 Processing Times Need to be Available at the Hub

Plan is attaching additional information to the RFH2 header. As a result, tags for events being pushed outside the expected area of up to 1000 bytes. Plan is requesting to increase the size of the work area. (Refer ticket INC0034686 for additional information.) This request was identified in Blue2 12.0 e_IPPT00068003 - Blue2 Processing Times Need to be Available at the Hub Resolution Details: Increase the length of working area to process RFH2 header from 1000 to 2000 bytes. Plan Impacts: None.

i_83845 – Utility to Provide Portability of ITS For mats Database


Create portability of the ITS Formats database cross platforms.

Requesting a utility program that can unload the ITS Formats database from one source and then a reload utility that will add the records to the target database. For many of the Plans that are consolidating ITS platforms, this would support that process. It would also build upon the multi-Plan functionality that was introduced with ITS 10.0. Note that this should also include the Plan Profile database. Resolution Details: A process is built to allow parameter driven conversion of BOID and/or Partition Key for the ITS and Blue2 tables. Plan Impacts: None.


Version 1.0

Created 02/21/2013

Revised:


38 of 43

i_84593 – Change to ITCDPT06


Triple-S/USVI need change to copylib ITCDPT06

Triple-S/USVI needs the following changes done on COMM.COPYLIB(ITCDPT06).

Add:

465465 USVI/TRIPLE-S, INC.

965965 USVI/TRIPLE-S, INC.

Change:

973973 TRIPLE-S, INC. Resolution Details: Modified copybook as requested. Plan Impacts: None.

Blue2 N/A

Claims Admin N/A

IPDS N/A

IPOR

I_83612 : Retrofitting 12.3 changes in 13.0 code


Changes made in R12.3 are not available in R13.0

IPOR 12.3 is released to Plans after IPOR 13.0 is released. Changes made in 12.3 need to be retrofitted in 13.0 code where ever applicable. Resolution Details: Apply 12.3 changes in 13.0 code Plan Impacts: Apply DDLs ITS0554D, ITS0555D and ITS0556D from DLTA DDL


Version 1.0

Created 02/21/2013

Revised:


39 of 43


library

Programs IPORITSV and IPORLVL2 are changed, Install changed programs.

I_84256 : DDL changes to use NOT LOGGED option in c reating Level2 open fact tables.


DDL changes to use NOT LOGGED option in creating Level2 open fact tables.

DDLs provided in 12.3 to create Level2 open fact tables have default LOGGED option in create tablespace definition. These Level2 open fact tables are deleted and recreated everyday, so there is no need to use LOGGED option which will have adverse impact on the performance of the job. ALTER DDLs are provided to change LOGGED to NOT LOGGED option in create tablespace definition. Resolution Details: Provide ALTER DDLs to change LOGGED to NOT LOGGED option. Plan Impacts:

Apply DDLs ITS0554I, ITS0555I and ITS0556I from DLTA DDL library.


Version 1.0

Created 02/21/2013

Revised:


40 of 43

Appendix A: Software Log

The Software Log for the ITS, IPDS and IPOR 13.0 code release is available on BlueWeb at National Programs Release 13.0. (BlueWeb Page 24421) or search keyword “13.0”. The software log information for IPDS Extract is included in the ITS software log.

Appendix B: Metadata and Online Help

Metadata

Metadata information is available at http://blueweb.bcbs.com/metadata This is a high-level link. Plans need to choose the release from the menu page. The link from Blue² directly to the release-specific page will be made available at general release.

Blue2 and Claims Administration Online Help

For Blue2 13.0, the online help for Blue2 and Claims Administration applications will be hosted in the Association the same way as the Metadata information link.

Blue² online help is available at the following location: https://blueweb.bcbs.com/metadata/b2help/Index.htm

Claims Administration online help is available at the following location:

https://blueweb.bcbs.com/metadata/cahelp/Index.htm

Appendix C: Global Certification

More detailed information regarding Global Certification testing can be found in Appendix C of the Release 13.0 Milestone Document, available via the National Programs Release 13.0 page (BlueWeb Page 24421) or search keyword “Release 13.0”.

Appendix D: Update ITS Release dates in APPL_PARM 1 9


The Parameter database had no additional changes for this addendum release.

Appendix E: New or Modified ITS Reports

All new or modified reports can be found in their respective enhancement’s functional specifications.


Version 1.0

Created 02/21/2013

Revised:


41 of 43

Appendix F: New and Modified ITS Error Messages

There are no new error codes in this addendum release. But the text for one code has been modified to match the functional specs.

DF Modified

DRL84 DF MESSAGE CODE 1083 NOT ALLOWED ON ANY RE-ISSUE DF

A complete list of all ITS error messages is listed in the Edit Definitions Manual available via BlueWeb page 10372 or search “ITS User Manuals” to locate the page.

Appendix G: Datasets

The following datasets that contain data changes must be downloaded for this release:

1. BZAP.ITPROD.B13V0A1.D130221.DATA.ITCDBD00

• File contains Reference Data.

• File is needed for changes related to e_82574 – Add New Places of Service (POS) Code 18

• Program ITCP2106/ITCP6106 is used to update REF_DATA table with this file.

• This is a test version only.

• Prior to implementation in April, a production vers ion of the file will be sent via GFT10551. A bulletin will be sent at that time with more details.

2. BZAP.ITPROD.R13V0A1.D130221.DATA.ITCDB110

• This is the 13.0.1 addendum Error Code - DEN file.

• A full file containing all the Error Code-DEN mapping from all previous release and release 13.0, BZAP.ITPROD.R13V0.D121108.DATA.ITCDB110, was released with 13.0.

• Plans must concatenate the addendum file after the 13.0 file.

• These files are used to load the error code/message table (IPP_ERR_MSG_ELEMENT) for Claim Administration.

• If Plans have internal Error Code-DEN mapping file, it should be concatenated along with this file before loading.

• Loading to ERR_MSG table must be completed before l oading to IPP_ERR_MSG_ELEMENT table

• Plan must run delete job DLDENTBL to delete IPP_ERR _MSG_ELEMENT table before loading the file.

• Use job LDDENTBL to load the file IPP_ERR_MSG_ELEME NT table.


Version 1.0

Created 02/21/2013

Revised:


42 of 43

Appendix H: DDLs

There are no additional DDL changes in this addendum release.


Version 1.0

Created 02/21/2013

Revised:


43 of 43

Plan Readiness & Defect Reporting

The implementation date for release 13.0 and 13.0.1 addendum is April 14, 2013. Plans are expected to be prepared to accept the release for deployment into their testing environment. Readiness includes all hardware and software setup and configuration for environmental requirements.

In addition, BlueWeb page 19077 includes a System Software Standards document which identifies the BCBSA-established standards for required system software packages used to support Inter-Plan Programs hosted application software and Inter-Plan Programs application software deployed at Plans, such as ITS, Blue², Claims Administration and various other software applications.

Any defects and/or issues must be reported to the IPPT Help Desk via the BCBSA Self-Service Portal at https://bcbsa.service-now.com, email at [email protected], or telephone at 312.297.5500.