28.11.2014 Views

Medicare Advantage and Prescription Drug Plans December 28 ...

Medicare Advantage and Prescription Drug Plans December 28 ...

Medicare Advantage and Prescription Drug Plans December 28 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Medicare</strong> <strong>Advantage</strong><br />

<strong>and</strong> <strong>Prescription</strong> <strong>Drug</strong><br />

<strong>Plans</strong><br />

<strong>December</strong> <strong>28</strong>, 2012<br />

Plan Communications<br />

User Guide<br />

Appendices<br />

Version 6.3


Plan Communications User Guide Appendices, Version 6.3<br />

Section<br />

Changes<br />

Change Log<br />

<strong>December</strong> <strong>28</strong>, 2012 Updates<br />

Global Changes Updated the version from 6.2 to 6.3<br />

Updated the publication date to <strong>December</strong> <strong>28</strong>, 2012<br />

Updated Table, Section, <strong>and</strong> Appendix references<br />

Changed references to the Financial Alignment Demonstration from "FA/FA Demo" to<br />

"<strong>Medicare</strong> <strong>and</strong> Medicaid Plan" (MMP)<br />

Updated “Center for Beneficiary Choices (CBC)” to “Center for <strong>Medicare</strong> (CM)”<br />

Appendix A<br />

Appendix B<br />

Appendix C<br />

Appendix D<br />

Appendix E<br />

Appendix F<br />

Appendix G<br />

Appendix H<br />

No Change<br />

Updated CMS Central Office - Division of Payment Operations (DPO) Representatives table<br />

Added Year 2013 MARx Plan Monthly Schedule<br />

No Change<br />

No Change<br />

Updated Table F.6.3, Transaction Type 61 Layout, Enrollment Transaction<br />

No Change<br />

No Change<br />

Appendix I Updated Transaction Reply Codes (TRCs) definitions for 116 <strong>and</strong> 144<br />

Added TRCs 316, 317 <strong>and</strong> 718<br />

Appendix J<br />

Appendix K<br />

Appendix L<br />

Appendix M<br />

No Change<br />

No Change<br />

No Change<br />

No Change<br />

<strong>December</strong> <strong>28</strong>, 2012 iii Change Log


Plan Communications User Guide Appendices, Version 6.3<br />

THIS PAGE INTENTIONALLY BLANK<br />

<strong>December</strong> <strong>28</strong>, 2012<br />

iv


Plan Communications User Guide Appendices, Version 6.3<br />

Table of Contents<br />

A: Glossary <strong>and</strong> List of Abbreviations <strong>and</strong> Acronyms ......................................................... A-1<br />

A.1 List of Abbreviations <strong>and</strong> Acronyms .................................................................................. A-4<br />

B: CMS Central Office Contact Information ..........................................................................B-1<br />

B.1 CMS Central Office ..............................................................................................................B-2<br />

B.2 Payment Information Form ...................................................................................................B-2<br />

C: Monthly Schedule ................................................................................................................ C-1<br />

D: Enrollment Data Transmission Schedule .......................................................................... D-1<br />

E: ESRD Network Contact Information Table .......................................................................E-1<br />

F: Record Layouts...................................................................................................................... F-1<br />

DTRR Data File Detailed Record Layout ..................................................................... F-1<br />

F.1 820 Format Payment Advice Data File ................................................................................. F-3<br />

F.1.1 Header Record ...................................................................................................... F-4<br />

F.1.2 Detail Record ........................................................................................................ F-5<br />

F.1.3 Trailer Record ...................................................................................................... F-6<br />

F.2 Batch Completion Status Summary Data File ....................................................................... F-7<br />

F.2.1 Failed Record ....................................................................................................... F-7<br />

F.2.2 BCSS ‘Failed Transaction’ Layout ...................................................................... F-8<br />

F.3 BIPA 606 Payment Reduction Data File .............................................................................. F-9<br />

F.4 Bonus Payment Data File ................................................................................................... F-10<br />

F.5 Coordination of Benefits (COB); Validated Other Health Insurance Data File .................. F-11<br />

F.5.1 General Organization of Records ....................................................................... F-11<br />

F.5.2 Detail Records: Indicates the Beginning of a Series of Beneficiary<br />

Subordinate Detail Records ........................................................................ F-11<br />

F.5.3 Primary Records: Subordinate to Detail Record (Unlimited Occurrences) ....... F-12<br />

F.5.4 Supplemental Records: Subordinate to DTL (Unlimited Occurrences) ............. F-15<br />

F.6 MARX Batch Input Transaction Data File .......................................................................... F-18<br />

F.6.1 Header Record .................................................................................................... F-18<br />

F.6.2 Disenrollment Transaction (TC 51/54) Detailed Record Layout ....................... F-19<br />

F.6.3 Enrollment Transaction (TC 61) Detailed Record Layout ................................. F-20<br />

F.6.4 Miscellaneous Change Transactions – Detailed Record Layouts ...................... F-22<br />

F.6.5 Cancellation Transactions – Detailed Record Layouts ...................................... F-<strong>28</strong><br />

F.6.6 Correction Record .............................................................................................. F-30<br />

F.6.7 Notes for All Plan-Submitted Transaction Types .............................................. F-31<br />

F.7 Failed Transaction Data File - OBSOLETE ........................................................................ F-35<br />

F.8 Monthly Membership Detail Data File ................................................................................ F-36<br />

<strong>December</strong> <strong>28</strong>, 2012 v Table of Contents


Plan Communications User Guide Appendices, Version 6.3<br />

F.9 Monthly Membership Summary Data File .......................................................................... F-44<br />

F.10 Monthly Premium Withholding Report Data File (MPWR) ............................................. F-47<br />

F.10.1 Header Record .................................................................................................. F-47<br />

F.10.2 Detail Record .................................................................................................... F-48<br />

F.10.3 Trailer Record .................................................................................................. F-49<br />

F.11 Part B Claims Data File ..................................................................................................... F-50<br />

F.11.1 Record Type 1 .................................................................................................. F-50<br />

F.11.2 Record Type 2 .................................................................................................. F-51<br />

F.12 Part C Risk Adjustment Model Output Data File .............................................................. F-52<br />

F.12.1 Header Record .................................................................................................. F-52<br />

F.12.2 Detail Record Type A ...................................................................................... F-52<br />

F.12.3 Detail Record Type B ....................................................................................... F-60<br />

F.12.4 Trailer Record .................................................................................................. F-70<br />

F.13 Risk Adjustment System (RAS) <strong>Prescription</strong> <strong>Drug</strong> Hierarchical Condition Category<br />

(RxHCC) Model Output Data File - aka Part D RA Model Output Data File ............ F-71<br />

F.13.1 Header Record .................................................................................................. F-71<br />

F.13.2 Detail/Beneficiary Record ................................................................................ F-71<br />

F.13.3 Trailer Record .................................................................................................. F-80<br />

F.14 Daily Transaction Reply Report (DTRR) Data File .......................................................... F-81<br />

F.14.1 DTRR Data File Detailed Record Layout ........................................................ F-81<br />

F.14.2 Verbatim Plan Submitted Transaction on Daily Transaction Reply Report<br />

(DTRR) ....................................................................................................... F-89<br />

F.15 Monthly Full Enrollment Data File ................................................................................... F-90<br />

F.16 LIS/LEP Data File ............................................................................................................. F-92<br />

F.16.1 Header Record .................................................................................................. F-92<br />

F.16.2 Detail Record .................................................................................................... F-92<br />

F.17 Loss of Subsidy Data File .................................................................................................. F-95<br />

F.17.1 Loss of Subsidy Data File Detail Record ......................................................... F-95<br />

F.18 LIS/Part D Premium Data File .......................................................................................... F-97<br />

F.19 LIS History Data File (LISHIST) ...................................................................................... F-98<br />

F.19.1 Header Record .................................................................................................. F-98<br />

F.19.2 Detail Record (Transaction) ............................................................................. F-99<br />

F.19.3 Trailer Record ................................................................................................ F-101<br />

F.20 NoRx File......................................................................................................................... F-102<br />

F.20.1 Header Record ................................................................................................ F-102<br />

F.20.2 Detail Record .................................................................................................. F-103<br />

F.20.3 Trailer Record ................................................................................................ F-105<br />

F.21 Batch Eligibility Query (BEQ) Request File ................................................................... F-106<br />

F.21.1 Header Record ................................................................................................ F-106<br />

F.21.2 Detail Record (Transaction) ........................................................................... F-107<br />

F.21.3 Trailer Record ................................................................................................ F-108<br />

<strong>December</strong> <strong>28</strong>, 2012 vi Table of Contents


Plan Communications User Guide Appendices, Version 6.3<br />

F.22 BEQ Response File .......................................................................................................... F-109<br />

F.22.1 Header Record ................................................................................................ F-109<br />

F.22.2 Detail Record (Transaction) ........................................................................... F-110<br />

F.22.3 Trailer Record ................................................................................................ F-121<br />

F.23 MA Full Dual Auto Assignment Notification File .......................................................... F-122<br />

F.23.1 Header Record ................................................................................................ F-122<br />

F.23.2 Detail Record (Transaction) ........................................................................... F-123<br />

F.23.3 Trailer Record ................................................................................................. F-123<br />

F.24 Auto Assignment (PDP) Address Notification File......................................................... F-125<br />

F.24.1 Header Record ................................................................................................ F-125<br />

F.24.2 Detail Record .................................................................................................. F-126<br />

F.24.3 Trailer Record ................................................................................................ F-1<strong>28</strong><br />

F.25 Plan Payment Report (PPR)/Interim Plan Payment Report (IPPR) Data File .......... F-129<br />

F.25.1 Header Record .......................................................................................... F-129<br />

F.25.2 Capitated Payment – Current Activity ...................................................... F-130<br />

F.25.3 Premium Settlement .................................................................................. F-131<br />

F.25.4 Fees ........................................................................................................... F-131<br />

F.25.5 Special Adjustments ................................................................................. F-132<br />

F.25.6 Previous Cycle Balance Summary ............................................................ F-133<br />

F.25.7 Payment Summary ........................................................................................ F-134<br />

F.25.8 Payment Balance Carried Forward ............................................................... F-136<br />

F.26 Long-Term Institutionalized (LTI) Resident Report Data File ................................. F-138<br />

F.27 Agent Broker Compensation Report Data File ......................................................... F-140<br />

F.<strong>28</strong> Monthly <strong>Medicare</strong> Second Payer (MSP) Information Data File ............................... F-142<br />

F.<strong>28</strong>.1 Header Record ....................................................................................... F-142<br />

F.<strong>28</strong>.2 Detail Record ........................................................................................ F-142<br />

F.<strong>28</strong>.3 Trailer Record ........................................................................................ F-143<br />

F.29 Other Health Coverage Information Data File ......................................................... F-144<br />

F.29.1 Header Record ....................................................................................... F-144<br />

F.29.2 Detail Record ........................................................................................ F-144<br />

F.29.3 Trailer Record ........................................................................................ F-149<br />

F.30 No Premium Due Data File Layout .......................................................................... F-150<br />

F.31 Failed Payment Reply Report (FPRR) Data File ............................................................. F-152<br />

F.32 Missing Payment Exception Report (MPER) Data File ............................................ F-153<br />

G: Screen Hierarchy ................................................................................................................. G-1<br />

H: Validation Messages ............................................................................................................ H-1<br />

I: Codes ........................................................................................................................................ I-1<br />

I.1 Transaction Codes .......................................................................................................... I-1<br />

I.2 Transaction Reply Codes ................................................................................................ I-2<br />

<strong>December</strong> <strong>28</strong>, 2012 vii Table of Contents


Plan Communications User Guide Appendices, Version 6.3<br />

I.3 Obsolete Transaction Reply Codes .............................................................................. I-84<br />

I.4 Transaction Reply Code (TRC) Groupings .................................................................. I-91<br />

I.5 Payment Reply Codes ................................................................................................. I-100<br />

I.6 MMR Adjustment Reason Codes ............................................................................... I-101<br />

I.7 State Codes ................................................................................................................. I-103<br />

I.8 Entitlement Status <strong>and</strong> Enrollment Reason Codes ..................................................... I-105<br />

I.9 Disenrollment Reason Codes ..................................................................................... I-108<br />

I.10 BEQ Response File Error Condition Table ................................................................ I-111<br />

I.10.1 Request File Error Conditions .......................................................................... I-111<br />

I.10.2 Request Transaction Detail Record Error Conditions ...................................... I-112<br />

J: Report Files ............................................................................................................................ J-1<br />

J.1 BIPA 606 Payment Reduction Report..................................................................................... J-2<br />

J.2 Bonus Payment Report ............................................................................................................ J-6<br />

J.3 HMO Bill Itemization Report................................................................................................ J-11<br />

J.4 Monthly Membership Detail Report – <strong>Drug</strong> Report (Part D) ............................................... J-12<br />

J.5 Monthly Membership Detail Report – Non-<strong>Drug</strong> Report (Part C) ....................................... J-13<br />

J.6 Monthly Membership Summary Report (MMSR) ................................................................ J-15<br />

J.7 Monthly Summary of Bills Report ........................................................................................ J-19<br />

J.8 Part C Risk Adjustment Model Output Report ..................................................................... J-21<br />

J.9 RAS RxHCC Model Output Report - aka - Part D RA Model Output Report ..................... J-22<br />

J.10 Payment Records Report ........................................................................................................23<br />

J.11 Plan Payment Report (APPS Payment Letter) .......................................................................24<br />

J.12 Interim Plan Payment Report (IPPR) .................................................................................. J-29<br />

J.13 No Premium Due Report Format ........................................................................................ J-30<br />

J.14 Sample BEQ Request File Pass <strong>and</strong> Fail Acknowledgments .............................................. J-36<br />

K: All Transmissions Overview ............................................................................................... K-1<br />

L: MA Plan Connectivity Checklist .........................................................................................L-1<br />

M: Valid Election Types for Plan-Submitted Transactions ................................................. M-1<br />

<strong>December</strong> <strong>28</strong>, 2012 viii Table of Contents


Plan Communications User Guide Appendices, Version 6.3<br />

A: Glossary <strong>and</strong> List of Abbreviations <strong>and</strong> Acronyms<br />

Table A-1: Glossary<br />

Term<br />

Accepted Transaction<br />

Account Number<br />

Application Date<br />

Batch Transaction<br />

Beneficiary<br />

Identification Code<br />

(BIC)<br />

Benefit Stabilization<br />

Fund (BSF)<br />

Button<br />

Cancellation<br />

Transaction<br />

Checkbox<br />

Connect:Direct<br />

Correction<br />

Cost Plan<br />

Current Calendar<br />

Month (CCM)<br />

Current Processing<br />

Month<br />

Current Payment Month<br />

(CPM)<br />

Creditable Coverage<br />

Data entry field<br />

Deductible<br />

Disenrollment<br />

Dropdown list<br />

Definition<br />

The successful application of a requested action that was processed by MARx.<br />

A number obtained from the Resource Access Control Facility (RACF) or<br />

system administrator.<br />

The date that the beneficiary applies to enroll in a Plan. Enrollments submitted<br />

by CMS or its contractors, such as the <strong>Medicare</strong> Beneficiary Contact Center, do<br />

not need application dates.<br />

An automated systems approach to processing in which data items to be<br />

processed must be grouped <strong>and</strong> processed in bulk.<br />

The portion of the <strong>Medicare</strong> health insurance claim number that identifies a<br />

specific beneficiary.<br />

Established by CMS upon request of an HMO or CMP, when the HMO or CMP<br />

must provide its <strong>Medicare</strong> enrollees with additional benefits, to prevent<br />

excessive fluctuation in the provision of those benefits in subsequent contract<br />

periods.<br />

A rectangular icon on a screen which, when clicked, engages an action. The<br />

button is labeled with word(s) that describe the action, such as Find or Update.<br />

A cancellation may result from an action by the beneficiary, CMS, or another<br />

Plan before the effective date of the election. A cancelled enrollment restores<br />

the beneficiary to his/her prior enrollment state.<br />

A field that is part of a group of options, for which the user may select any<br />

number of options. Each option is represented with a small box, where ‘x’<br />

means “on” <strong>and</strong> an empty box means “off.” When a checkbox is clicked, an ‘x’<br />

appears in the box. When the checkbox is clicked again, the ‘x’ is removed.<br />

The proprietary software that transfers files between systems.<br />

A record submitted by a Plan or CMS office to correct or update existing<br />

Beneficiary data.<br />

A type of contract under which a Plan is reimbursed by CMS for its reasonable<br />

costs.<br />

Represents the calendar month <strong>and</strong> year at the time of transaction submission.<br />

For batch, the current month is derived from the batch file transmission date; for<br />

User Interface transactions, the current month is derived from the system data at<br />

the time of transaction submission.<br />

The calendar month in which processing occurs to generate payments. The<br />

Current Processing Month is distinguished from the CPM, the month in which<br />

<strong>Plans</strong> receive payment from CMS.<br />

The month for which <strong>Plans</strong> receive payment from CMS, not the current calendar<br />

month.<br />

<strong>Prescription</strong> drug coverage, generally from an employer or union, that is<br />

equivalent to, or better than, <strong>Medicare</strong> st<strong>and</strong>ard prescription drug coverage.<br />

A field that requires the user to enter information.<br />

The amount a Beneficiary must pay for medical services or prescription drugs<br />

before a Plan starts paying benefits.<br />

A record submitted by a Plan, Social Security Administration District Office<br />

(SSA DO), <strong>Medicare</strong> Customer Service Center (MCSC), or CMS when a<br />

beneficiary discontinues membership in the Plan.<br />

A field that contains a list of values from which the user chooses. Clicking on<br />

the down arrow on the right of the field enables the user to view the list of<br />

values, <strong>and</strong> then click on a value to select it.<br />

<strong>December</strong> <strong>28</strong>, 2012 A-1 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

Term<br />

Dual Eligible<br />

Election Period<br />

Enrollment<br />

Enrollment Process<br />

Exception<br />

Failed Payment Reply<br />

Codes<br />

Failed Transaction<br />

Formulary<br />

Gentran<br />

Hospice<br />

Logoff<br />

Logon<br />

Lookup field<br />

Medicaid<br />

Managed Care<br />

Organization (MCO)<br />

Menu<br />

Network Data Mover<br />

(NDM)<br />

MicroStrategy<br />

Nursing Home<br />

Certifiable (NHC)<br />

Off-cycle<br />

Definition<br />

Individuals entitled to both <strong>Medicare</strong> <strong>and</strong> Medicaid benefits<br />

Time periods during which a Beneficiary may elect to join, change, or leave<br />

<strong>Medicare</strong> Part C <strong>and</strong>/or Part D <strong>Plans</strong>. These periods are fully defined in CMS<br />

Enrollment <strong>and</strong> Disenrollment guidance for Part C <strong>and</strong> D <strong>Plans</strong> available on the<br />

Web at: http://www.cms.gov/home/medicare.asp under “Eligibility <strong>and</strong><br />

Enrollment.”<br />

A record submitted when a Beneficiary joins an MCO or a drug plan.<br />

A process in which a Plan submits a request to enroll in a Plan, change<br />

enrollment, or disenroll.<br />

A transaction that is unprocessed due to errors or internal inconsistencies.<br />

Codes used for the Failed Payment Reply Report that identify incomplete<br />

payment calculations for a beneficiary.<br />

A transaction that did not complete due to problems with the format of the<br />

transaction or internal system problems.<br />

The medications covered by an MA organization or prescription drug plan.<br />

The Gentran servers provide Electronic Data Interchange (EDI) capabilities<br />

between CMS <strong>and</strong> CMS business partners. These servers provide MARx with<br />

transaction files from the <strong>Plans</strong>, <strong>and</strong> provide the <strong>Plans</strong> with MARx reports.<br />

A health facility for the terminally ill.<br />

The method of exiting an online system.<br />

The method for gaining entry to an online system.<br />

A field that provides a list of possible values. When the user clicks on the<br />

“binocular” button next to the field, a window pops up with a list of values for<br />

that field. Clicking on one of those values closes the pop-up window <strong>and</strong> the<br />

field is filled with the value chosen.<br />

A jointly funded, Federal-State health insurance program for certain low-income<br />

<strong>and</strong> needy people. It covers approximately 36 million individuals including<br />

children, the aged, blind, <strong>and</strong>/or disabled, <strong>and</strong> people eligible to receive<br />

Federally assisted income maintenance payments.<br />

A type of contract under which CMS pays for each member, based on<br />

demographic characteristics <strong>and</strong> health status; also referred to as Risk. In a Risk<br />

contract, the MCO accepts the risk if the payment does not cover the cost of<br />

services, but keeps the difference if the payment is greater than the cost of<br />

services. Risk is managed through a membership where the high costs for very<br />

sick members are balanced by the lower cost for a larger number of relatively<br />

healthy members.<br />

A horizontal list of items at the top of a screen. Clicking on a menu item<br />

displays a screen <strong>and</strong> may display a submenu of items corresponding to the<br />

selected menu item.<br />

Software used for transmitting <strong>and</strong> receiving data; replaced by Connect:Direct.<br />

A tool used for generating <strong>and</strong> viewing st<strong>and</strong>ard <strong>and</strong> ad hoc reports.<br />

A code that reflects the relative frailty of an individual. NHC Beneficiaries are<br />

those whose condition would ordinarily require nursing home care. The code is<br />

only acceptable for certain social health maintenance organization (SHMO)-<br />

type <strong>Plans</strong>.<br />

A retroactive transaction awaiting CMS approval because its effective date is<br />

too old for automatic acceptance.<br />

<strong>December</strong> <strong>28</strong>, 2012 A-2 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

Term<br />

Online<br />

Premium<br />

Premium Payment<br />

Option (PPO)<br />

Program for All<br />

Inclusive Care for the<br />

Elderly (PACE) <strong>Plans</strong><br />

Radio button<br />

Required field<br />

Risk<br />

Special Needs Plan<br />

(SNP)<br />

Submenu<br />

TIBCO MFT Internet<br />

Server<br />

Transaction Code (TC)<br />

Transaction Reply Code<br />

(TRC)<br />

User ID<br />

User Interface<br />

Definition<br />

An automated systems approach that processes data in an interactive manner,<br />

normally through computer input.<br />

The monthly payment a Beneficiary makes to <strong>Medicare</strong>, an insurance company,<br />

or a healthcare Plan.<br />

The method selected by the beneficiary to pay the premium owed to the Plan.<br />

PPO choices are: (1) withhold from SSA (S) or RRB (R) benefit check or (2)<br />

Direct self-pay (D) to the Plan.<br />

PACE is a unique capitated managed care benefit for the frail elderly provided<br />

by a not-for-profit or public entity that features a comprehensive medical <strong>and</strong><br />

social service delivery system. It uses a multidisciplinary team approach in an<br />

adult day health center supplemented by in-home <strong>and</strong> referral service in<br />

accordance with participants' needs.<br />

A field that is part of a group of options, of which the user may only select one<br />

option. A radio button is represented with a small circle; a filled circle indicates<br />

the button is selected, <strong>and</strong> an empty circle means it is not selected. Clicking a<br />

radio button selects that option <strong>and</strong> deselects the existing selection.<br />

A field that the user must complete before a button is clicked to engage an<br />

action. If the button is clicked <strong>and</strong> the field is not filled in, an error message<br />

displays <strong>and</strong> the action does not occur.<br />

There are two types of required fields:<br />

• Always required, which are marked with an asterisk (*)<br />

• Conditionally required, where the user must fill in at least one or only one of<br />

the conditionally required fields. These are marked with a plus sign (+).<br />

A contract under which Beneficiaries are “locked in” to network providers <strong>and</strong> a<br />

payment is received from CMS for each member, based on demographic<br />

characteristics <strong>and</strong> health status. In a Risk contract, the MCO accepts the risk if<br />

the payment does not cover the cost of services, but keeps the difference if the<br />

payment is greater than the cost of services. Risk is managed through a<br />

membership where the high costs for very sick members are balanced by the<br />

lower costs for a larger number of relatively healthy members.<br />

A certain type of MA Plan that serves a limited population of individuals in<br />

CMS special-needs categories, as defined in CMS Part C Enrollment <strong>and</strong><br />

Eligibility Guidance. This Plan is fully defined on the Web at:<br />

http://www.cms.gov/home/medicare.asp under “Health <strong>Plans</strong>.”<br />

A horizontal list of items below the screen’s menu. Clicking on a submenu item<br />

displays a screen.<br />

The TIBCO MFT Internet Servers provide Electronic Data Interchange (EDI)<br />

capabilities between CMS <strong>and</strong> CMS business partners. These servers provide<br />

MARx <strong>and</strong> MBD with transaction files from the <strong>Plans</strong>, <strong>and</strong> provide the <strong>Plans</strong><br />

with MARx <strong>and</strong> MBD reports.<br />

Identifies batch transactions submitted by the <strong>Plans</strong> or CMS.<br />

The code that explains the action taken by the system in response to new<br />

information from CMS systems or in response to input from MCOs, CMS, or<br />

other users.<br />

Valid user identification code for accessing the CMS Data Center <strong>and</strong> the<br />

<strong>Medicare</strong> Data Communications Network.<br />

The screens, forms, <strong>and</strong> menus that display to a user logged on to an automated<br />

system.<br />

<strong>December</strong> <strong>28</strong>, 2012 A-3 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

A.1 List of Abbreviations <strong>and</strong> Acronyms<br />

AAPCC Adjusted Average Per Capita Cost<br />

ADAP AIDS <strong>Drug</strong> Assistance Program<br />

AE-FE Automated Enrollment-Facilitated Enrollment<br />

AEP<br />

Annual Enrollment Period<br />

APPS Automated Plan Payment System<br />

BBA Balanced Budget Act of 1997<br />

BCSS Batch Completion Status Summary<br />

BEQ<br />

Beneficiary Eligibility Query<br />

BIC<br />

Beneficiary Identification Code<br />

BIN<br />

Beneficiary Identification Number<br />

BIPA Benefits Improvement & Protection Act of 2000<br />

BSF<br />

Benefit Stabilization Fund<br />

CAN<br />

Claim Account Number<br />

CCIP/FFS Chronic Care Improvement Program/Fee-for-Service<br />

CCM Current Calendar Month<br />

C:D<br />

Connect:Direct<br />

CHF<br />

Congestive Heart Failure<br />

CM<br />

Center for <strong>Medicare</strong><br />

CMP<br />

Competitive Medical Plan<br />

CMS<br />

Centers for <strong>Medicare</strong> & Medicaid Services<br />

CO<br />

Central Office<br />

COB<br />

Close of Business<br />

COB<br />

Coordination of Benefits<br />

COBA Coordination of Benefits Agreement<br />

COBC Coordination of Benefits Contractor<br />

COM Current Operation Month<br />

CPM<br />

Current Payment Month<br />

CR<br />

Change Request<br />

CSR<br />

Customer Service Representative<br />

CWF<br />

Common Working File database (CMS’ beneficiary database)<br />

DCG<br />

Diagnostic Cost Group<br />

DDPS <strong>Drug</strong> Data Processing System<br />

DO<br />

District Office<br />

DOB<br />

Date of Birth<br />

DOD<br />

Date of Death<br />

<strong>December</strong> <strong>28</strong>, 2012 A-4 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

DPO<br />

DSA<br />

DTL<br />

DTRR<br />

ECRS<br />

EDB<br />

EFT<br />

EGHP<br />

EIN<br />

EOY<br />

EPOC<br />

ESRD<br />

FAQ<br />

FEFD<br />

FERAS<br />

FFS<br />

FTR<br />

GHP<br />

GUIDE<br />

HCC<br />

HCFA<br />

HCPP<br />

HIC<br />

HICN<br />

HIPAA<br />

HMO<br />

HPMS<br />

HTML<br />

HTTPS<br />

IACS<br />

ICD<br />

ICD-9-CM<br />

ICEP<br />

ID<br />

IEP<br />

IPPR<br />

IRMAA<br />

Division of Payment Operations<br />

Data Sharing Agreement<br />

Detail<br />

Daily Transaction Reply Report<br />

Electronic Correspondence Referral System<br />

Enrollment Database<br />

Enterprise File Transfer<br />

Employer Group Health Plan<br />

Employee Identification Number<br />

End of Year<br />

External Point of Contact<br />

End Stage Renal Disease<br />

Frequently Asked Question<br />

Full Enrollment File Data<br />

Front End Risk Adjustment System<br />

Fee-For-Service<br />

Failed Transaction Report<br />

Group Health Plan<br />

Plan Communications User Guide<br />

Hierarchical Condition Category<br />

Health Care Financing Administration (renamed to CMS)<br />

Health Care Premium Plan<br />

Health Insurance Claim<br />

Health Insurance Claim Number<br />

Health Insurance Portability <strong>and</strong> Accountability Act<br />

Health Maintenance Organization<br />

Health Plan Management System<br />

Hypertext Markup Language<br />

Hypertext Transfer Protocol Secure<br />

Individuals Authorized Access to CMS Computer Services<br />

Interface Control Document<br />

International Classification of Diseases, 9 th Edition<br />

Initial Coverage Election Period<br />

Identification<br />

Initial Enrollment Period<br />

Interim Plan Payment Report<br />

Income-Related Monthly Adjustment Amount<br />

<strong>December</strong> <strong>28</strong>, 2012 A-5 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

IRS<br />

IT<br />

LEP<br />

LICS<br />

LIPS<br />

LIS<br />

LISHIST<br />

LISPRM<br />

LTC<br />

LTI<br />

MA<br />

MA BSF<br />

MADP<br />

MAPD<br />

MARx<br />

MARx UI<br />

MBD<br />

MCO<br />

MDS<br />

MCSC<br />

MMA<br />

MMCM<br />

MMDR<br />

MMP<br />

MMR<br />

MMSR<br />

MPWE<br />

MPWR<br />

MSA<br />

MSHO<br />

MSP<br />

NCPDP<br />

NDM<br />

NMEC<br />

NHC<br />

NUNCMO<br />

OEPI<br />

Internal Revenue Service<br />

Information Technology<br />

Late Enrollment Penalty<br />

Low-Income Cost Sharing<br />

Low-Income Premium Subsidy<br />

Low-Income Subsidy<br />

LIS History Data File<br />

LIS Premium Data File<br />

Long-Term Care<br />

Long-Term Institutional<br />

<strong>Medicare</strong> <strong>Advantage</strong><br />

<strong>Medicare</strong> <strong>Advantage</strong> Benefit Stabilization Fund<br />

<strong>Medicare</strong> <strong>Advantage</strong> Disenrollment Period<br />

<strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> Part D<br />

<strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> <strong>Prescription</strong> <strong>Drug</strong> System<br />

<strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> <strong>Prescription</strong> <strong>Drug</strong> System User Interface<br />

<strong>Medicare</strong> Beneficiary Database<br />

Managed Care Organization<br />

Minimum Data Set<br />

<strong>Medicare</strong> Customer Service Center (1-800-MEDICARE)<br />

<strong>Medicare</strong> Modernization Act<br />

<strong>Medicare</strong> Managed Care Manual<br />

Monthly Membership Detail Report<br />

<strong>Medicare</strong> <strong>and</strong> Medicaid Plan<br />

Monthly Membership Report<br />

Monthly Membership Summary Report<br />

Monthly Premium Withhold Extract<br />

Monthly Premium Withholding Report Data File<br />

Medical Savings Account<br />

Minnesota Senior Health Options<br />

<strong>Medicare</strong> Secondary Payer<br />

National Council of <strong>Prescription</strong>s <strong>Drug</strong> Programs<br />

Network Data Mover<br />

National <strong>Medicare</strong> Education Campaign<br />

Nursing Home Certifiable<br />

Number of Uncovered Months<br />

Open Enrollment Period for Institutionalized Individuals<br />

<strong>December</strong> <strong>28</strong>, 2012 A-6 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

OHI<br />

OMB<br />

OPM<br />

PACE<br />

PAP<br />

PBM<br />

PBO<br />

PBP<br />

PCN<br />

PDE<br />

PDP<br />

PFFS<br />

PIP<br />

POS<br />

PPO<br />

PPR<br />

PRM<br />

PWS<br />

QMB<br />

RA<br />

RACF<br />

RAS<br />

RDS<br />

REMIS<br />

RO<br />

RRB<br />

RRE<br />

RxHCC<br />

SCC<br />

SEP<br />

SFTP<br />

SHMO<br />

SIMS<br />

SLMB<br />

SNP<br />

SPAP<br />

SSA<br />

Other Health Insurance<br />

Office of Management <strong>and</strong> Budget<br />

Office of Personnel Management<br />

Program of All-Inclusive Care for the Elderly<br />

Patient Assistance Program<br />

Pharmacy Benefit Manager<br />

Payment Bill Option<br />

Plan Benefit Package<br />

Processor Control Number<br />

<strong>Prescription</strong> <strong>Drug</strong> Event<br />

<strong>Prescription</strong> <strong>Drug</strong> Plan<br />

Private Fee-for-Service<br />

Principal Inpatient Diagnostic Cost Group<br />

Point-of-Sale<br />

Premium Payment Option<br />

Plan Payment Report<br />

Primary Record<br />

Premium Withhold System<br />

Qualified <strong>Medicare</strong> Beneficiary Program<br />

Risk Adjustment/Risk Adjusted<br />

Resource Access Control Facility<br />

Risk Adjustment System<br />

Retiree <strong>Drug</strong> Subsidy<br />

Renal Management Information System<br />

CMS Regional Office<br />

Railroad Retirement Board<br />

Responsible Reporting Entity<br />

<strong>Prescription</strong> <strong>Drug</strong> Hierarchical Condition Category<br />

State <strong>and</strong> County Code<br />

Special Election Period<br />

Secure Shell File Transfer Protocol<br />

Social Health Maintenance Organization<br />

St<strong>and</strong>ard Information Management System<br />

Specified Low-Income <strong>Medicare</strong> Beneficiary Program<br />

Special Needs Plan<br />

State Pharmaceutical Assistance Program<br />

Social Security Administration<br />

<strong>December</strong> <strong>28</strong>, 2012 A-7 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

SSA DO<br />

SSN<br />

SUP<br />

TC<br />

TIN<br />

TRC<br />

TrOOP<br />

TRR<br />

UI<br />

WC<br />

WCSA<br />

WPP<br />

Social Security Administration District Office<br />

Social Security Number<br />

Supplemental Record<br />

Transaction Code<br />

Tax Identification Number<br />

Transaction Reply Code<br />

True Out-of-Pocket<br />

Transaction Reply Report<br />

User Interface<br />

Workers Compensation<br />

Workers Compensation Set-Aside<br />

Wisconsin Partnership Program<br />

<strong>December</strong> <strong>28</strong>, 2012 A-8 Glossary <strong>and</strong> List of Abbreviations<br />

<strong>and</strong> Acronyms


Plan Communications User Guide Appendices, Version 6.3<br />

B: CMS Central Office Contact Information<br />

This appendix contains consolidated contact information for <strong>Plans</strong> to reference when they need<br />

assistance with questions or issues on information contained in the Plan Communications User<br />

Guide (the Guide) or on other issues or topics as summarized in the tables below.<br />

Note: For questions or issues on payment or premium information contained in this guide or on<br />

any of the topics listed below, <strong>Plans</strong> should contact their Center for <strong>Medicare</strong> <strong>and</strong> Medicaid<br />

Services (CMS) Central Office (CO) Health Insurance Specialist in the Division of Payment<br />

Operations (DPO) for their particular region. See DPO contact list by region on page B-2 below.<br />

Table B-1: DPO Central Office Contact Information<br />

Full Dual Eligibility; Business Questions Only<br />

Dual eligibility in general<br />

Rules for auto assignment<br />

Rules for passive enrollment<br />

Info on Special Needs Plan (SNP) - NOT<br />

the files<br />

Late Enrollment Penalty (LEP); Business Only<br />

CMS Plan Reporting Requirements; Not file<br />

format<br />

Reports<br />

<br />

Report Contents, Timing, <strong>and</strong> Payment;<br />

<strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> <strong>Prescription</strong><br />

<strong>Drug</strong> System (MARx)<br />

Full Dual Eligibility; (Business Only)<br />

Plan Payments<br />

Calculation of payment<br />

Delivery of payment<br />

Payment errors<br />

Premium calculations<br />

Automated Plan Payment System (APPS)<br />

operation <strong>and</strong> APPS reports<br />

Actual payments going to the <strong>Plans</strong><br />

Payment rules<br />

Payment operations<br />

Interim payments<br />

Monthly Membership Report (MMR)<br />

Center for <strong>Medicare</strong> (CM) Plan Payment Letters<br />

All APPS Payment Reports; (Business Only)<br />

Plan Communications User Guide<br />

<strong>December</strong> <strong>28</strong>, 2012 B-1 CMS Central Office Contact Information


Plan Communications User Guide Appendices, Version 6.3<br />

B.1 CMS Central Office<br />

Table B-2: Division of Payment Operations (DPO) Representatives<br />

Region Contact Telephone Number E-mail Address<br />

1. Boston <strong>and</strong><br />

Kansas City<br />

2. New York,<br />

Demos/PACE<br />

Terry Williams (410) 786-0705 Terry.Williams@cms.hhs.gov<br />

William Bucksten (410) 786-7477 William.Bucksten@cms.hhs.gov<br />

3. Philadelphia James Krall (410) 786-6999 James.Krall@cms.hhs.gov<br />

4. Atlanta Louise Matthews (410) 786-6903 Louise.Matthews@cms.hhs.gov<br />

5. Chicago Mary Stojak (410) 786-6939 Mary.Stojak@cms.hhs.gov<br />

6. Dallas Michelle Page (410) 786-6937 Michelle.Page@cms.hhs.gov<br />

7. San Francisco Kim Miegel (410) 786-3311 Kim.Miegel@cms.hhs.gov<br />

<strong>and</strong> Denver<br />

8. Seattle Shaw<strong>and</strong>a Perkins 410-786-7412 Shaw<strong>and</strong>a.Perkins@cms.hhs.gov<br />

9. DPO Director John Scott (410) 786-3636 John.Scott@cms.hhs.gov<br />

B.2 Payment Information Form<br />

Government vendor organizations with <strong>Medicare</strong> contracts receive payment from the<br />

Department of Treasury through an Electronic Funds Transfer (EFT) program. On the expected<br />

payment date, government vendor receive payments as direct deposits into corporate accounts at<br />

financial institutions. Additionally, CMS must have the Employee Identification Number<br />

(EIN)/Tax Identification Number (TIN) <strong>and</strong> associated name as registered with the Internal<br />

Revenue Service (IRS).<br />

<strong>December</strong> <strong>28</strong>, 2012 B-2 CMS Central Office Contact Information


Plan Communications User Guide Appendices, Version 6.3<br />

NAME OF ORGANIZATION:<br />

DBA, if any:<br />

ORGANIZATION INFORMATION<br />

ADDRESS:<br />

CITY: STATE: ZIP CODE:<br />

CONTACT PERSON NAME:<br />

TELEPHONE NUMBER:<br />

CONTRACT NO’s.: H ; H ; H ; H<br />

(If known)<br />

EIN/TIN NAME of business for tax purposes (as registered with the IRS: a W-9 may be<br />

required)<br />

EMPLOYER/TAX IDENTIFICATION NUMBER (EIN or TIN):<br />

Mailing address for 1099 tax form:<br />

STR1:<br />

STR2:<br />

CITY:<br />

STATE: ZIP: -<br />

FINANCIAL INSTITUTION<br />

NAME OF BANK:<br />

ADDRESS:<br />

CITY: STATE: ZIP CODE: -<br />

ACH/EFT COORDINATOR NAME:<br />

TELEPHONE NUMBER:<br />

_____<br />

NINE DIGIT ROUTING TRANSIT (ABA) NUMBER:<br />

DEPOSITOR ACCOUNT TITLE:<br />

DEPOSITOR ACCOUNT NUMBER:<br />

CIRCLE ACCOUNT TYPE: CHECKING SAVINGS (Please attach a copy of a voided<br />

check)<br />

SIGNATURE & TITLE OF ORGANIZATION’S AUTHORIZED REPRESENTATIVE:<br />

Signature<br />

Title<br />

DATE: ____________________<br />

_____________________________________________<br />

Print Name<br />

______________________<br />

Phone Number<br />

3/12/03<br />

<strong>December</strong> <strong>28</strong>, 2012 B-3 CMS Central Office Contact Information


Plan Communications User Guide Appendices, Version 6.3<br />

Special Note:<br />

For assistance with Beneficiary-specific issues with enrollments, disenrollments, cancellations,<br />

<strong>and</strong> changes, <strong>Plans</strong> should contact their designated CMS regional caseworker.<br />

<strong>Plans</strong> should e-mail their inquiry or research request for enrollment issues to the home Regional<br />

Office (RO) associated with their Beneficiary’s address at PartDComplaints_RO#@cms.hhs.gov<br />

Note: Replace the # sign in the above e-mail address with the specific RO number from the list<br />

above. For example: if the Beneficiary resides in Baltimore, send the inquiry to the Philadelphia<br />

RO using the following e-mail address:<br />

Example: PartDComplaints_RO3@cms.hhs.gov<br />

Please Note: <strong>Plans</strong> should report premium or other Plan Payment issues directly to their DPO<br />

contact listed on Page B-2 <strong>and</strong> not to the ROs/caseworkers. Also, if MARx reflects that the<br />

Beneficiary is in SSA Deduct <strong>and</strong> the Plan is not getting paid, then the Plan should contact its<br />

DPO representative.<br />

For non-payment-related software, database questions, errors or issues related to any of the<br />

topics listed below, <strong>Plans</strong> may contact the <strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> <strong>Prescription</strong> <strong>Drug</strong> (MAPD)<br />

Help Desk at 1-800-927-8069 or via e-mail at MAPDHelp@cms.hhs.gov.<br />

Table B-3: MAPD Help Desk Contact Information<br />

<br />

<br />

<br />

<br />

<br />

File transfer software; Connect:Direct, Secure FTP, Gentran HTTPS, <strong>and</strong> TIBCO MFT Internet<br />

Server<br />

Ongoing Connectivity, File Transmission Support <strong>and</strong> Troubleshooting<br />

Supporting access to CMS systems; Individuals Authorized Access to CMS Computer Services<br />

(IACS) <strong>and</strong> Common User Interface (UI)<br />

Coordination with other help desks for proper routing of issues<br />

Questions related to file layouts; MAPD Help <strong>and</strong> OIS system letters, user guides, Frequently<br />

Asked Questions (FAQs), etc.<br />

<strong>December</strong> <strong>28</strong>, 2012 B-4 CMS Central Office Contact Information


Plan Communications User Guide Appendices, Version 6.3<br />

Plan Manager; <strong>Medicare</strong> <strong>Advantage</strong> (MA) <strong>Plans</strong> only – Contact regional Plan Manager for<br />

questions or issues related to the topics listed below:<br />

Table B-4: Plan Manager Contact Information<br />

<br />

Special Needs Plan questions, unless<br />

drug related<br />

<br />

Regional Premium Payment Option (PPO) Plan<br />

Questions, unless drug related<br />

<br />

MA Medical Savings Account (MSA)<br />

- Part C Plan manager issue, unless drug<br />

related<br />

<br />

Part C Managed Care Appeals Policy<br />

<br />

MA only Plan Finder Tool<br />

Account Manager (Part D <strong>Plans</strong> Only) – Contact Account Manager for questions or issues<br />

related to the topics listed below:<br />

Table B-5: Account Manager Contact Information<br />

Online Enrollment Center General Part D Information<br />

General Part D <strong>Medicare</strong> Information General Part D MMA Information<br />

General Part D Policy Questions Part D Managed Care Appeals Policy<br />

Part D vs. Part B <strong>Drug</strong> Coverage Health Insurance Portability <strong>and</strong> Accountability<br />

Act (HIPAA) Privacy<br />

Creditable Coverage Marketing Requirements<br />

Financial Solvency – Application COB Survey<br />

Plan Finder & Formulary<br />

<strong>December</strong> <strong>28</strong>, 2012 B-5 CMS Central Office Contact Information


Plan Communications User Guide Appendices, Version 6.3<br />

THIS PAGE INTENTIONALLY BLANK<br />

<strong>December</strong> <strong>28</strong>, 2012<br />

vi


C: Monthly Schedule<br />

Plan Communications User Guide Appendices, Version 6.3<br />

The following pages contain the 2011 Plan <strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> <strong>Prescription</strong> <strong>Drug</strong> System<br />

(MARx) Monthly Schedule, which provides dates for the following:<br />

<br />

<br />

<br />

<br />

<br />

<br />

Plan Data Due<br />

Down Days<br />

Availability of Monthly Reports<br />

Due Date for Certification of Enrollment, Payment, <strong>and</strong> Premium Reports<br />

Payments Due to <strong>Plans</strong><br />

Holidays<br />

Note: The Daily Transaction Reply Report (DTRR), is not indicated on this schedule because it is<br />

a daily report.<br />

This calendar is also available as a single document in the <strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> <strong>Prescription</strong><br />

<strong>Drug</strong> (MAPD) Help Desk Web site downloads section: http://www.cms.gov/mapdhelpdesk/. Both<br />

color <strong>and</strong> text 508 compliant versions of this schedule are available at the above link.<br />

C.1 MARx Plan Payment Processing Schedule Description - Calendar Year 2013<br />

It is vital that everyone involved in the <strong>Medicare</strong> enrollment <strong>and</strong> payment operations of the<br />

contract is aware of target dates schedule attached to this description. The schedule includes:<br />

(1) PLAN DATA DUE - This is the last day for <strong>Plans</strong> to transmit records to the CMS Data<br />

Center for processing in the month. <strong>Plans</strong> must complete the transmission by the close of<br />

business (8 p.m. ET) on the date noted.<br />

(2) PAYMENT DUE PLANS - This is the date that CMS deposits the CMS monthly payment<br />

to the <strong>Plans</strong>; all deposits are made to arrive on the first calendar day of the month unless<br />

the first day falls on a weekend or a Federal holiday. In this case, the deposit arrives on the<br />

last workday prior to the first of the month.<br />

Note: The January deposit is the first business day of the month.<br />

(3) MONTHLY REPORTS AVAIL - This is the date all the CMS monthly reports are<br />

available for downloading from the mailbox or received in the system.<br />

Note: These reports are not mailed; the Plan must download them to receive them!<br />

(3) ANNUAL ELECTION PERIOD BEGINS AND ENDS - The Annual Election Period (AEP)<br />

is October 15 through <strong>December</strong> 7 every year. Elections made during the AEP are<br />

effective January 1 of the following year.<br />

(4) CERTIFICATION DUE - This is the date by which <strong>Plans</strong> must certify the accuracy of the<br />

enrollment information of the MARx Report. <strong>Plans</strong> must send the Certification to the<br />

Retroactive Processing Contractor.<br />

(5) APPROVED RETROS TO CMS - Any records processed as batch retroactive files must<br />

arrive at CMS by noon on the date shown, along with the appropriate paperwork approved<br />

by CMS.<br />

<strong>December</strong> <strong>28</strong>, 2012 C-1 Monthly Schedule


Plan Communications User Guide Appendices, Version 6.3<br />

<strong>December</strong> <strong>28</strong>, 2012 C-2 Monthly Schedule


Plan Communications User Guide Appendices, Version 6.3<br />

<strong>December</strong> <strong>28</strong>, 2012 C-3 Monthly Schedule


Plan Communications User Guide Appendices, Version 6.3<br />

D: Enrollment Data Transmission Schedule<br />

The following is a recommendation for the best time to transmit data:<br />

<br />

<br />

Monday through Friday - 24 hours.<br />

Data IS received for monthly processing.<br />

Saturday, Sunday, <strong>and</strong> system down days.<br />

Data IS RECEIVED AND HELD for monthly processing.<br />

Refer to the Plan Monthly Schedule. (Appendix C)<br />

<br />

Enrollment Data Cutoff Day - Data is due by 8 p.m. ET.<br />

The Plan Monthly Schedule in Appendix C lists cutoff dates for each month.<br />

Note: Retros are due by noon two days prior to the Plan Data Due/Submission<br />

cutoff day.<br />

<strong>December</strong> <strong>28</strong>, 2012 D-1 Enrollment Transmission Schedule


Plan Communications User Guide Appendices, Version 6.3<br />

THIS PAGE INTENTIONALLY BLANK<br />

<strong>December</strong> <strong>28</strong>, 2012 D-2 Enrollment Transmission Schedule


Plan Communications User Guide Appendices, Version 6.3<br />

E: ESRD Network Contact Information Table<br />

Network Region States Name & Address Contact Information<br />

1 1 Connecticut<br />

Maine<br />

Massachusetts<br />

New Hampshire<br />

Rhode Isl<strong>and</strong><br />

Vermont<br />

ESRD Network of New Engl<strong>and</strong><br />

Jaya Bhargava, Data Manager<br />

30 Hazel Terrace.<br />

Woodbridge, Connecticut 06525<br />

Phone: (203) 387-9332<br />

Fax: (203) 389-9902<br />

2 2 New York IPRO/CKD Network for New York<br />

Bernadette Cobb, Data Manager<br />

1979 Marcus Avenue<br />

Lake Success, New York 11042-1002<br />

3 2 New Jersey<br />

Puerto Rico<br />

Virgin Isl<strong>and</strong>s<br />

4 3 Delaware<br />

Pennsylvania<br />

5 3 D of Columbia<br />

Maryl<strong>and</strong><br />

Virginia<br />

West Virginia<br />

6 4 Georgia<br />

North Carolina<br />

South Carolina<br />

Trans-Atlantic Renal Council<br />

Chris Milkosky, Data Manager<br />

Cranbury Gate Office Park<br />

109 S. Main St., Suite 21<br />

Cranbury, New Jersey 08512-9595<br />

ESRD Network 4 Inc.<br />

Rhonda Lockett, Data Manager<br />

40 24 th Street, Suite 410<br />

Pittsburgh, Pennsylvania 15222<br />

Mid-Atlantic Renal Coalition<br />

Jason Robins, Data Manager<br />

1527 Huguenot Road<br />

Midlothian, Virginia 23113<br />

Southeastern Kidney Council, Inc.<br />

Margo Clay, Data Manager<br />

1000 St. Albans Drive, Suite 270<br />

Raleigh, North Carolina 27609<br />

7 4 Florida ESRD Network of Florida, Inc.<br />

LeChrystal Williams, Data Manager<br />

5201 W Kennedy Boulevard, Suite 900<br />

Tampa, Florida 33606<br />

8 4 Alabama<br />

Mississippi<br />

Tennessee<br />

9 5 Kentucky<br />

Indiana<br />

Ohio<br />

ESRD Network Eight, Inc.<br />

Robert Bain, Data Manager<br />

1755 Lelia Drive, Suite 400<br />

Jackson, Mississippi 39210<br />

The Renal Network, Inc.<br />

Christy Harper, Data Manager<br />

911 East 86th Street, Suite 202<br />

Indianapolis, Indiana 46240<br />

10 5 Illinois The Renal Network, Inc.<br />

Christy Harper, Data Manager<br />

911 E 86th Street, Suite 202<br />

Indianapolis, Indiana 46240<br />

11 5 Michigan<br />

Minnesota<br />

North Dakota<br />

South Dakota<br />

Wisconsin<br />

12 7 Iowa<br />

Kansas<br />

Missouri<br />

Nebraska<br />

Renal Network of the Upper Midwest<br />

Tom Kysilko, Data Manager<br />

1360 Energy Park Drive, Suite 200<br />

St. Paul, Minnesota 55108<br />

ESRD Network 12<br />

Jeff Arnell, Data Manager<br />

7306 NW Tiffany Springs Parkway<br />

Suite 230<br />

Kansas City, Missouri 64153<br />

Phone: (516) 209-5619<br />

Fax: (516) 326-8929<br />

Phone: (609) 490-0310<br />

Fax: (609) 490-0835<br />

Phone: (412) 325-2250<br />

Fax: (412) 325-1811<br />

Phone: (804) 794-3757<br />

Fax: (804) 794-3793<br />

Phone: (919) 855-0882<br />

Fax: (919) 855-0753<br />

Phone: (813) 383-1530<br />

Fax: (813) 354-1514<br />

Phone: (601) 936-9260<br />

Fax: (601) 932-4446<br />

Phone: (317) 257-8265<br />

Fax: (317) 257-8291<br />

Phone: (317) 257-8265<br />

Fax: (317) 257-8291<br />

Phone: (651) 644-9877<br />

Fax: (651) 644-9853<br />

Phone: (816) 880-9990<br />

Fax: (816) 880-9088<br />

<strong>December</strong> <strong>28</strong>, 2012 E-1 ESRD Network Contact Information<br />

Table


Plan Communications User Guide Appendices, Version 6.3<br />

Network Region States Name & Address Contact Information<br />

13 6 Arkansas<br />

Louisiana<br />

Oklahoma<br />

ESRD Network 13<br />

Cindy Smith, Data Manager<br />

4200 Perimeter Center Drive, Suite 102<br />

Phone: (405) 942-6000<br />

Fax: (405) 942-6884<br />

Oklahoma City, Oklahoma 73112<br />

14 6 Texas ESRD Network of Texas, Inc.<br />

Nathan Muzos, Data Manager<br />

4040 McEwen, Suite 350<br />

Dallas, Texas 75244<br />

15 10 Arizona<br />

Colorado<br />

Nevada<br />

New Mexico<br />

Utah<br />

Wyoming<br />

16 10 Alaska<br />

Idaho<br />

Montana<br />

Oregon<br />

Washington<br />

17 10 Amer Samoa<br />

Hawaii<br />

N. California<br />

Pacific Isl<strong>and</strong>s<br />

Intermountain ESRD Network, Inc.<br />

Matt Howard, Data Manager<br />

165 S. Union Blvd<br />

Suite 466<br />

Lakewood, Colorado 802<strong>28</strong><br />

Northwest Renal Network<br />

Donna Swenson, Data Manager<br />

4702 42nd Avenue, SW<br />

Seattle, Washington 98116<br />

Western Pacific Renal Network<br />

Susan Tanner, Data Manager<br />

505 San Marin Drive, Bldg A, Suite 300<br />

Novata, California 94945<br />

18 10 S. California Southern California Renal Disease<br />

Council<br />

Svetlana Lyulkin, Data Manager<br />

6255 Sunset Boulevard, Suite 2211<br />

Los Angeles, California 900<strong>28</strong><br />

Phone: (972) 503-3215<br />

Fax: (972) 503-3219<br />

Phone: (303) 831-8818<br />

Fax: (303) 860-8392<br />

Phone: (206) 923-0714<br />

Fax: (206) 923-0716<br />

Phone: (415) 897-2400<br />

Fax: (415) 897-2422<br />

Phone: (323) 962-2020<br />

Fax: (323) 962-<strong>28</strong>91<br />

<strong>December</strong> <strong>28</strong>, 2012 E-2 ESRD Network Contact Information<br />

Table


Plan Communications User Guide Appendices, Version 6.3<br />

F: Record Layouts<br />

This appendix provides record layouts for data files exchanged with <strong>Plans</strong>. Field lengths, formats, <strong>and</strong> descriptions<br />

are included along with expected values where applicable. Table F-1 below lists the names of all the layouts <strong>and</strong> on<br />

which page of Appendix F to find them. Appendix K identifies the naming conventions of for all files exchanged<br />

between CMS <strong>and</strong> the <strong>Plans</strong>.<br />

Table F-1: Record Layouts Lookup Table<br />

Section Name Page<br />

F.1 820 Format Payment Advice Data File F-3<br />

F.2 Batch Completion Status Summary Data File F-7<br />

F.3 BIPA 606 Payment Reduction Data File F-8<br />

F.4 Bonus Payment Data File F-9<br />

F.5 Coordination of Benefits (COB) Validated Other Insurer Information Data File F-10<br />

F.6 MARx Batch Input Transaction Data File F-17<br />

F.6.1 Header Record F-17<br />

F.6.2 Disenrollment Transaction (TC 51/54) F-18<br />

F.6.3 Enrollment Transaction (TC 61) F-19<br />

F.6.4.1 RX Change (TC 72) F-22<br />

F.6.4.2 NUNCMO Change (TC 73) F-23<br />

F.6.4.3 EGHP Change (TC 74) F-24<br />

F.6.4.4 Premium Payment Option (POP) Change (TC 75) F-24<br />

F.6.4.5 Residence Address Change (TC 76) F-25<br />

F.6.4.6 Segment ID Change (TC 77) F-26<br />

F.6.4.7 Part C Premium Change (TC 78) F-26<br />

F.6.4.8 Part D Opt-Out Change (TC 79) F-27<br />

F.6.5.1 Cancel Enrollment (TC 80) F-<strong>28</strong><br />

F.6.5.2 Cancel Disenrollment (TC 81) F-<strong>28</strong><br />

F.6.5.3 MMP Enrollment Cancellation (TC 82) Detail Record Layout F-29<br />

F.6.5.4 MMP Opt-Out Update (TC 83) Layout F-29<br />

F.6.6 Correction Record F-30<br />

F.6.7 Notes for All Plan-Submitted Transaction Types F-31<br />

F.7 Failed Transaction Data File - OBSOLETE F-35<br />

F.8 Monthly Membership Detail Data File F-36<br />

F.9 Monthly Membership Summary Data File F-44<br />

F.10 Monthly Premium Withholding Report Data File (MPWR) F-47<br />

F.11 Part B Claims Data File F-50<br />

F.12 Part C Risk Adjustment Model Output Data File F-52<br />

F.13<br />

RAS RxHCC Model Output Data File aka Part D Risk Adjustment Model Output<br />

Data File<br />

F-59<br />

F.14 Daily Transaction Reply Report (DTRR) Data File F-81<br />

F.14.1 DTRR Data File Detailed Record Layout F-81<br />

F.14.2 Verbatim Plan Submitted Transaction on Transaction Reply Report F-89<br />

F.15 Monthly Full Enrollment Data File F-89<br />

<strong>December</strong> <strong>28</strong>, 2012 F-1 Record Layouts


Plan Communications User Guide Appendices, Version 6.3<br />

Section Name Page<br />

F.16 Low Income Subsidy (LIS)/Late Enrollment Penalty (LEP) Data File F-92<br />

F.17 Loss of Subsidy Data File F-95<br />

F.18 LIS/Part D Premium Data File F-97<br />

F.19 LIS History Data File (LISHIST) F-98<br />

F.20 NoRx File F-102<br />

F.21 Batch Eligibility Query (BEQ) Request File F-106<br />

F.22 Batch Eligibility Query (BEQ) Response File F-109<br />

F.23 MA Full Dual Auto Assignment Notification File F-122<br />

F.24 Auto Assignment PDP Address Notification File F-125<br />

F.25 Plan Payment Report (PPR) / Interim Plan Payment Report (IPRR) Data File F-129<br />

F.26 Long-Term Institutionalized Resident Report Data File F-138<br />

F.27 Agent Broker Compensation Report Data File F-140<br />

F.<strong>28</strong> Monthly <strong>Medicare</strong> Secondary Payer (MSP) Information Data File F-142<br />

F.29 Other Health Coverage Information Data File F-144<br />

F.30 No Premium Due Data File Layout F-150<br />

F.31 Failed Payment Reply Report Data File F-152<br />

F.32 Missing Payment Exception Report F-153<br />

<strong>December</strong> <strong>28</strong>, 2012 F-2 Record Layouts


Plan Communications User Guide Appendices, Version 6.3<br />

F.1 820 Format Payment Advice Data File<br />

The 820 Format Payment Advice data file is a Health Insurance Portability & Accountability Act<br />

(HIPAA)-compliant version of the Plan Payment Report, which is also known as the Automated<br />

Plan Payment System (APPS) Payment Letter. The data file itemizes the final monthly payment to<br />

the Plan. It is produced by APPS when final payments are calculated, <strong>and</strong> is available to <strong>Plans</strong> as<br />

part of the month-end processing. This file is not available through <strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong><br />

<strong>Prescription</strong> <strong>Drug</strong> System (MARx).<br />

The following records are included in this file:<br />

Header Record (numbers 1-6 below)<br />

Detail Record (numbers 7-10 below)<br />

Summary Record (number 11 below)<br />

The segments are listed in a required order:<br />

1. ST, 820 Header<br />

2. BPR, Financial Information<br />

3. TRN, Re-association Key<br />

4. DTM, Coverage Period<br />

5. N1, Premium Receiver’s Name<br />

6. N1, Premium Payer’s Name<br />

7. RMR, Organization Summary Remittance Detail<br />

8. IT1, Summary Line Item<br />

9. SLN, Member Count<br />

10. ADX, Organization Summary Remittance Level Adjustment<br />

11. SE, 820 Trailer<br />

The physical layout of a segment is:<br />

Segment Identifier, an alphanumeric code, followed by<br />

Each selected field (data element) preceded by a data element separator (“*”)<br />

And terminated by a segment terminator (“~”).<br />

Fields are mostly variable in length <strong>and</strong> do not contain leading/trailing spaces. If fields are empty,<br />

they are skipped by inserting contiguous data element separators (“*”) unless they are at the end of<br />

the segment. Fields that are not selected are represented in the same way as fields that are selected,<br />

but as this particular iteration of the transaction set contain no data, they are skipped.<br />

For example, in fictitious segment XXX, fields 2, 3, <strong>and</strong> 5 (the last field) are skipped:<br />

BALANCING REQUIREMENTS 1<br />

XXX*field 1 content***field 4 content~<br />

1 See pp.16 in National EDI Transaction Set Implementation Guide for 820, ASCX12N, 820 (004010X061), dated<br />

May 2000<br />

<strong>December</strong> <strong>28</strong>, 2012 F-3 820 Format Payment<br />

Advice Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Following two balancing rules are given:<br />

1. BPR02 = total of all RMR04<br />

2. RMR04 = RMR05 + ADX01<br />

To comply with balancing rules, BPR02 <strong>and</strong> RMR04 are set equal to Net Payment (paid amount),<br />

RMR05 is set equal to Gross/Calculated Payment (billed amount), <strong>and</strong> ADX01 is set equal to<br />

Adjustment amount.<br />

On Cost/Health Care Premium Plan (HCPP) contracts, <strong>Plans</strong> should enter the actual dollars billed,<br />

rather than the “risk equivalent” dollar amounts, into RMR05.<br />

F.1.1 Header Record<br />

Item<br />

Segment<br />

Data<br />

Element<br />

Description Length Type Contents<br />

820 Header Segment ID 2 AN “ST”<br />

ST01 Transaction Set ID Code 3/3 ID “820”<br />

ST02<br />

Transaction Set Control<br />

Number<br />

4/9 AN Begin with “00001”<br />

Increment each Run<br />

Beginning Segment For<br />

3 AN “BPR”<br />

Payment Order/Remittance<br />

Advice<br />

BPR BPR01 Transaction H<strong>and</strong>ling Code 1/2 ID “I”(Remittance Information<br />

Only)<br />

BPR BPR02 Total Premium Payment<br />

Amount<br />

1/18 R Payment Letter – Net<br />

Payment<br />

See discussion on Balancing.<br />

BPR BPR03 Credit/Debit Flag Code 1/1 ID “C” (Credit)<br />

BPR BPR04 Payment Method Code 3/3 ID “BOP” (Financial Institution<br />

Option)<br />

BPR BPR16 Check Issue or EFT Effective<br />

Date<br />

8/8 DT Use Payment Letter –<br />

Payment Date in<br />

CCYYMMDD format<br />

Re-Association Key 3 AN “TRN”<br />

TRN TRN01 Trace Type Code 1/2 ID “3” (Financial Re-association<br />

Trace Number)<br />

TRN TRN02 Check or EFT Trace Number 1/30 AN “USTREASURY”<br />

Coverage Period 3 AN “DTM”<br />

DTM DTM01 Date/Time Qualifier 3/3 ID “582” (Report Period)<br />

DTM DTM05 Date/Time Period Format<br />

Qualifier<br />

2/3 ID “RD8”(Range of dates<br />

expressed in format<br />

CCYYMMDD –<br />

CCYYMMDD)<br />

DTM DTM06 Date/Time Period 1/35 AN Range of Dates for Payment<br />

Month. See DTM05.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-4 820 Format Payment<br />

Advice Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item<br />

Segment<br />

Data<br />

Element<br />

Description Length Type Contents<br />

Premium Receiver’s Name 2 AN “N1”<br />

1000A N101 Entity Identifier Code 2/3 ID “PE” (Payee)<br />

1000A N102 Name 1/60 AN Contract Name<br />

1000A N103 Identification Code Qualifier 1/2 ID “EQ” Insurance Company<br />

Assigned ID Number<br />

1000A N104 Identification Code 2/80 AN Contract Number<br />

Premium Payer’s Name 2 AN “N1”<br />

1000B N101 Entity Identifier Code 2/3 ID “PR” (Payer)<br />

1000B N102 Name 1/60 AN “CMS”<br />

1000B N103 Identification Code Qualifier 1/2 ID “EQ” Insurance Company<br />

Assigned ID Number<br />

1000B N104 Identification Code 2/80 AN “CMS”<br />

F.1.2 Detail Record<br />

Item<br />

Segment<br />

Data<br />

Element<br />

Description Length Type Contents<br />

Organization Summary 3 AN “RMR”<br />

Remittance Detail<br />

2300A RMR01 Reference Identification 2/3 ID “CT”<br />

Qualifier<br />

2300A RMR02 Contract Number 1/30 AN Payment Letter – Contract #<br />

2300A RMR04 Detail Premium Payment<br />

Amount<br />

1/18 R Payment Letter – Net Payment<br />

See discussion on Balancing.<br />

2300A RMR05 Billed Premium Amount 1/18 R Payment Letter – Capitated Payment.<br />

See discussion on Balancing.<br />

Summary Line Item 3 AN “IT1”<br />

2310A IT101 Line Item Control 1/20 AN “1” (Assigned for uniqueness)<br />

Number<br />

Member Count 3 AN “SLN”<br />

2315A SLN01 Line Item Control<br />

Number<br />

1/20 AN “1” (Assigned for uniqueness)<br />

2315A SLN03 Information Only<br />

1/1 ID “O” (For Information only)<br />

Indicator<br />

2315A SLN04 Head Count 1/15 R Payment Letter – Total Members<br />

2315A<br />

SLN05-<br />

1<br />

Unit or Basis for<br />

Measurement Code<br />

2/2 ID “IE” - used to identify that the value<br />

of SLN04 represents the number of<br />

contract holders with individual<br />

coverage<br />

Organization Summary 3 AN “ADX”<br />

Remittance Level<br />

Adjustment<br />

2320A ADX01 Adjustment Amount 1/18 R Payment Letter – Total Adjustments is<br />

the difference between Capitated<br />

Payment <strong>and</strong> Net Payment. See<br />

discussion on Balancing.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-5 820 Format Payment<br />

Advice Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item<br />

Segment<br />

Data<br />

Element<br />

Description Length Type Contents<br />

2320A ADX02 Adjustment Reason Code 2/2 ID “H1” - Information forthcoming –<br />

detailed information related to the<br />

adjustment is provided through a<br />

separate mechanism<br />

F.1.3 Trailer Record<br />

Item Segment<br />

Data<br />

Element<br />

Description Length Type Contents<br />

Summary 820 Trailer AN “SE”<br />

SE01 Number of Included<br />

Segments<br />

1/10 N0 “11”<br />

SE02<br />

Transaction Set Control<br />

Number<br />

4/9 AN Use control number,<br />

same as in 820 Header.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-6 820 Format Payment<br />

Advice Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.2 Batch Completion Status Summary (BCSS) Data File<br />

As of the April 2011 release, the Batch Completion Status Summary (BCSS) file is a hybrid file<br />

that communicates the status of file transmissions, as well as reporting <strong>and</strong> reports on submitted<br />

transaction records that failed due to formatting issues. Previously, this file also returned the<br />

processing results of accepted <strong>and</strong> rejected transactions, but as of the April 2011 release, those<br />

are reported only on the Daily Transaction Reply Report (DTRR) Data file. Note: The<br />

Enrollment Transmission Message File (STATUS) discontinued as of the April 2011 Release.<br />

This data file is sent to the submitter after a batch of submitted transactions is processed. It<br />

provides a count of all transactions within the batch <strong>and</strong> details the number of rejected <strong>and</strong><br />

accepted transactions. It also provides an image of each failed transaction.<br />

F.2.1 Failed Record<br />

Below, the example of a BCSS report displays the format of the file transmission status. <strong>Plans</strong><br />

get a sense of how the file status incorporates the new Transaction Codes (TCs) 76 through 83<br />

<strong>and</strong> that the counts for accepted, rejected <strong>and</strong> failed transactions are displayed.<br />

Beginning of Message Text<br />

H1 TRANSACTIONS RECEIVED ON 2012-03-27 AT 16.59.49<br />

H2 TRANSACTIONS PROCESSED ON 2012-03-27 AT 17.03.50<br />

H3 ENROLLMENT PROCESSING COMPLETED<br />

H4 HEADER CODE= AAAAAAHEADER<br />

H5 HEADER DATE= 032012<br />

H6 REQUEST ID =<br />

H7 BATCH ID = 0123456789<br />

H8 USER ID = X7YZ<br />

C1 TRAN CNTS1 = 00000019 T01 0000000 T51 0000000 T61 0000000 T72 0000001<br />

C2 TRAN CNTS2 = T73 0000002 T74 0000000 T75 0000000 T76 0000000<br />

C3 TRAN CNTS3 = T77 0000000 T78 0000000 T79 0000002 T80 0000002<br />

C4 TRAN CNTS4 = T81 0000003 T82 0000004 T83 0000005 TXX 0000000<br />

P1 TOTAL TRANSACTIONS PROCESSED= 00000043<br />

P2 TOTAL ACCEPTED TRANSACTIONS = 00000041<br />

P3 TOTAL REJECTED TRANSACTIONS = 00000002<br />

P4 TOTAL FAILED TRANSACTIONS = 00000000<br />

F………………failed transaction text image………………<br />

End of Message Text<br />

All BCSS records begin with a two-character record type identifier. The first character<br />

designates the type of data reported in that section.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-7 BCSS Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.2.2 BCSS ‘Failed Transaction’ Layout<br />

Item Field Size Position Description<br />

1 Record Type Identifier 2 1-2 Failed Record Type: “F ” (‘F’ <strong>and</strong> space)<br />

2 Filler 1 3 Spaces<br />

3<br />

Failed Input Transaction Record<br />

Text<br />

300 4-303 Failed transaction text<br />

4 Filler 5 304-308 Spaces<br />

5 Transaction Reply Codes (TRCs) 3 309-311 First TRC<br />

6 TRCs 3 312- 314 Second TRC; otherwise, spaces<br />

7 TRCs 3 315 - 317 Third TRC; otherwise, spaces<br />

8 TRCs 3 318-320 Fourth TRC; otherwise, spaces<br />

9 TRCs 3 321-323 Fifth TRC; otherwise, spaces<br />

Total Length = 323<br />

<strong>December</strong> <strong>28</strong>, 2012 F-8 BCSS Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.3 BIPA 606 Payment Reduction Data File<br />

Item Field Size Position Description<br />

1 Contract Number 5 1-5 Contract Number<br />

2 PBP Number 3 6-8 999<br />

3 Run Date 8 9-16 YYYYMMDD<br />

4 Payment Month 6 17-22 YYYYMM<br />

5 Adjustment Reason Code 2 23-24 99; SPACES = Payment<br />

6 Payment/Adjustment Start Month 6 25-30 YYYYMM<br />

7 Payment/Adjustment End Month 6 31-36 YYYYMM<br />

8 HIC 12 37-48 External Format<br />

9 Surname First 7 7 49-55<br />

10 First Initial 1 56<br />

11 Sex 1 57 M = Male; F = Female<br />

12 Date of Birth 8 58-65 YYYYMMDD<br />

13 BIPA606 Payment Reduction Rate 6 66-71 999.99; must be GE ZERO<br />

14<br />

Total Net Blended Payment/Adjustment<br />

Excluding BIPA606 Reduction Amount<br />

9 72-80 -99999.99<br />

15 BIPA606 Net Payment Reduction Amount 8 81-88<br />

-9999.99; Normally negative, may<br />

include positive adjustments<br />

Applies only to Part B amounts<br />

16 Net Part A Blended Amount 9 89-97 -99999.99; Same as MMR amount<br />

17<br />

18<br />

Net Part B Blended Amount plus BIPA606<br />

Net Payment Reduction<br />

Total Net Blended Payment/Adjustment<br />

Including BIPA606 Reduction Amount<br />

9 98-106 -99999.99<br />

9 107-115 -99999.99<br />

19 Filler 18 116-133 Spaces<br />

Total Length = 13<br />

<strong>December</strong> <strong>28</strong>, 2012 F-9 BIPA 606 Payment Reduction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.4 Bonus Payment Data File<br />

Item Field Size Position Description<br />

1 Contract Number 5 1-5 Plan contract number<br />

2 Run Date 8 6-13<br />

YYYYMMDD; date the report<br />

was created<br />

3 Payment Month 6 14-19<br />

YYYYMM; the month that<br />

payments are effective<br />

4 Adjustment Reason Code 2 20-21<br />

Reason for the adjustment; equal<br />

to spaces if a payment<br />

5 Payment/Adjustment Start Month 6 22-27 YYYYMM<br />

6 Payment/Adjustment End Month 6 <strong>28</strong>-33 YYYYMM<br />

7 State <strong>and</strong> County Code 5 34-38<br />

2-digit state code followed by 3-<br />

digit county code of residence<br />

8 HIC 12 39-50 Beneficiary’s claim number<br />

9 Surname 7 51-57 First 7 letters of the last name<br />

10 Initial 1 58 Initial of the first name<br />

11 Sex 1 59 Gender; M=male, F=female<br />

12 Date of Birth 8 60-67 YYYYMMDD<br />

13 Bonus Percentage 5 68-72<br />

14<br />

Total Blended Payment/Adjustment w/o<br />

Bonus<br />

9 73-81<br />

Bonus payment percent; 5.000%<br />

or 3.000%<br />

Total Payment/Adjustment<br />

without bonus<br />

15 Bonus Part A Payment/Adjustment 8 82-89 Part A bonus payment/adjustment<br />

16 Bonus Part B Payment/Adjustment 8 90-97 Part B bonus payment/adjustment<br />

17 Total Bonus Payment/Adjustment 9 98-106 Total bonus payment/adjustment<br />

18<br />

Blended + Bonus Payment/Adjustment<br />

Part A<br />

9 107-115<br />

19 Blended + Bonus Payment/Adjustment 9 116-124<br />

20<br />

Total Blended + Bonus<br />

Payment/Adjustment<br />

Total Length = 133<br />

9 125-133<br />

Part A payment/adjustment with<br />

bonus<br />

Part B payment/adjustment with<br />

bonus Part B<br />

Total payment/adjustment with<br />

bonus<br />

<strong>December</strong> <strong>28</strong>, 2012 F-10 Bonus Payment Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.5 Coordination of Benefits (COB); Validated Other Health Insurance Data<br />

File<br />

This file contains members’ primary <strong>and</strong> secondary coverage, validated through COB<br />

processing. MARx forwards this report whenever a Plan’s enrollees are affected, which may<br />

occur as often as daily. The enrollees included on the report are those newly enrolled who have<br />

known Other Health Insurance (OHI) <strong>and</strong> those Plan enrollees with changes to their OHI.<br />

The following records are included in this file:<br />

<br />

<br />

<br />

Detail Record<br />

Primary Record<br />

Supplemental Record<br />

F.5.1 General Organization of Records<br />

Detail Record (DTL) Record 1 (Beneficiary A)<br />

Primary (PRM) records associated with ‘DTL’ Record 1 (Beneficiary A)<br />

Supplemental (SUP) records associated with ‘DTL’ Record 1 (Beneficiary A)<br />

‘DTL’ Record 2 (Beneficiary B)<br />

‘PRM’ records associated with ‘DTL’ Record 2 (Beneficiary B)<br />

‘SUP’ records associated with ‘DTL’ Record 2 (Beneficiary B)<br />

‘DTL’ Record 3 (Beneficiary C)<br />

‘PRM’ records associated with ‘DTL’ Record 3 (Beneficiary C)<br />

‘SUP’ records associated with ‘DTL’ Record 3 (Beneficiary C)<br />

‘DTL Record n<br />

‘PRM’ records associated with ‘DTL’ Record n<br />

‘SUP’ records associated with ‘DTL’ Record n<br />

F.5.2 Detail Records: Indicates the Beginning of a Series of Beneficiary Subordinate Detail<br />

Records<br />

Item Field Size Position Format Valid Values/Description<br />

1 Record Type 3 1-3 CHAR "DTL"<br />

2 HICN/RRB Number 12 4-15 CHAR Spaces if unknown<br />

3 SSN 9 16-24 ZD 000000000 if unknown<br />

4 Date of Birth (DOB) 8 25-32 CHAR YYYYMMDD<br />

5 Gender Code 1 33 CHAR<br />

0=unknown, 1 = male, 2 =<br />

female<br />

6 Contract Number 5 34-38 CHAR<br />

7 Plan Benefit Package 3 39-41 CHAR<br />

8 Action Type 1 42 CHAR 2 = Full replacement<br />

9 Filler 958 43-1000 CHAR Spaces<br />

Note: Record Length = 1000<br />

<strong>December</strong> <strong>28</strong>, 2012 F-11 COB; Validated Other Health Insurance<br />

Data


Plan Communications User Guide Appendices, Version 6.3<br />

F.5.3 Primary Records: Subordinate to Detail Record (Unlimited Occurrences)<br />

Item Field Size Position Format Valid Values/Description<br />

1 Record Type 3 1-3 CHAR "PRM"<br />

2 HICN/RRB Number 12 4-15 CHAR Spaces if unknown<br />

3 SSN 9 16-24 ZD 000000000 if unknown<br />

4 Date of Birth (DOB) 8 25-32 CHAR YYYYMMDD<br />

5 Gender Code 1 33 CHAR 0=unknown, 1 = male, 2 = female<br />

6 RxID Number* 20 34-53 CHAR<br />

7 RxGroup Number* 15 54-68 CHAR<br />

8 RxBIN Number* 6 69-74 ZD<br />

9 RxPCN Number* 10 75-84 CHAR<br />

10<br />

Rx Plan Toll Free<br />

Number*<br />

18 85-102 CHAR<br />

11 Sequence Number* 3 103-105 CHAR<br />

12<br />

COB Source Code*<br />

Note: There may be<br />

instances where an<br />

unknown COB Source<br />

Code will be provided.<br />

<strong>Plans</strong> should contact<br />

COBC for clarification<br />

on any unknown Source<br />

Codes.<br />

5 106-110 CHAR<br />

11100 Non Payment/Payment Denial<br />

11101 IEQ<br />

11102 Data Match<br />

11103 HMO<br />

11104 Litigation Settlement BCBS<br />

11105 Employer Voluntary Reporting<br />

11106 Insurer Voluntary Reporting<br />

11107 First Claim Development<br />

11108 Trauma Code Development<br />

11109 Secondary Claims Investigation<br />

11110 Self Report<br />

11111 411.25<br />

11112 BCBS Voluntary Agreements<br />

11113 Office of Personnel<br />

Management (OPM) Data Match<br />

11114 Workers' Compensation Data<br />

Match<br />

11118 Pharmacy Benefit Manager<br />

(PBM)<br />

11120 COBA<br />

11125 Recovery Audit Contractor<br />

(RAC) 1 (April Release)<br />

11126 RAC 2 (April Release)<br />

11127 RAC 3 (April Release)<br />

P0000 PBM<br />

S0000 Assistance Program<br />

Note: Contractor numbers 11100 -<br />

11199 are reserved for COB<br />

<strong>December</strong> <strong>28</strong>, 2012 F-12 COB; Validated Other Health Insurance<br />

Data


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Format Valid Values/Description<br />

13<br />

MSP Reason<br />

(Entitlement Reason<br />

from COB)<br />

1 111 CHAR<br />

14 Coverage Code* 1 112 CHAR<br />

15 Insurer's Name* 32 113-144 CHAR<br />

16 Insurer's Address-1* 32 145-176 CHAR<br />

17 Insurer's Address-2* 32 177-208 CHAR<br />

18 Insurer's City* 15 209-223 CHAR<br />

19 Insurer's State* 2 224-225 CHAR<br />

20 Insurer's Zip Code* 9 226-234 CHAR<br />

21 Insurer TIN 10 235-244 CHAR<br />

22<br />

Individual Policy<br />

Number*<br />

17 245-261 CHAR<br />

23 Group Policy Number* 20 262-<strong>28</strong>1 CHAR<br />

24 Effective Date* 8 <strong>28</strong>2-<strong>28</strong>9 ZD CCYYMMDD<br />

A=Working Aged<br />

B=ESRD<br />

C=Conditional Payment<br />

D=Automobile Insurance, No fault<br />

E=Workers Compensation<br />

F=Federal (public)<br />

G=Disabled<br />

H=Black Lung<br />

I=Veterans<br />

L=Liability<br />

A=Hospital <strong>and</strong> Medical<br />

U=<strong>Drug</strong> (network benefit)<br />

V=<strong>Drug</strong> with Major Medical (nonnetwork<br />

benefit)<br />

W=Comprehensive, Hospital, Medical,<br />

<strong>Drug</strong> (network)<br />

X=Hospital <strong>and</strong> <strong>Drug</strong> (network)<br />

Y=Medical <strong>and</strong> <strong>Drug</strong> (network)<br />

Z=Health Reimbursement Account<br />

(hospital, medical, <strong>and</strong> drug)<br />

25 Termination Date* 8 290-297 ZD CCYYMMDD<br />

26 Relationship Code* 2 298-299 CHAR<br />

01=Bene is Policy Holder<br />

02=Spouse<br />

03=Child<br />

04=Other<br />

27 Payer ID* 10 300-309 CHAR This is a future element.<br />

<strong>28</strong> Person Code* 3 310-312 CHAR<br />

29 Payer Order* 3 313-315 ZD<br />

30<br />

Policy Holder's First<br />

Name<br />

9 316-324 CHAR<br />

31<br />

Policy Holder's Last<br />

Name<br />

16 325-340 CHAR<br />

32 Policy Holder's SSN 12 341-352 CHAR<br />

33<br />

Employee Information<br />

Code<br />

1 353 CHAR<br />

34 Employer's Name 32 354-385 CHAR<br />

P=Patient<br />

S=Spouse<br />

M=Mother<br />

F=Father<br />

<strong>December</strong> <strong>28</strong>, 2012 F-13 COB; Validated Other Health Insurance<br />

Data


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Format Valid Values/Description<br />

35 Employer's Address 1 32 386-417 CHAR<br />

36 Employer's Address 2 32 418-449 CHAR<br />

37 Employer's City 15 450-464 CHAR<br />

38 Employer's State 2 465-466 CHAR<br />

39 Employer's Zip Code 9 467-475 CHAR<br />

40 Filler 20 476-495 CHAR<br />

41 Employer TIN 10 496-505 CHAR<br />

42 Filler 20 506-525 CHAR<br />

43 Claim Diagnosis Code 1 10 526-535 CHAR<br />

44 Claim Diagnosis Code 2 10 536-545 CHAR<br />

45 Claim Diagnosis Code 3 10 546-555 CHAR<br />

46 Claim Diagnosis Code 4 10 556-565 CHAR<br />

47 Claim Diagnosis Code 5 10 566-575 CHAR<br />

48 Attorney's Name 32 576-607 CHAR<br />

49 Attorney's Address 1 32 608-639 CHAR<br />

50 Attorney's Address 2 32 640-671 CHAR<br />

51 Attorney's City 15 672-686 CHAR<br />

52 Attorney's State 2 687-688 CHAR<br />

53 Attorney's Zip 9 689-697 CHAR<br />

54 Lead Contractor 9 698-706 CHAR<br />

55 Class Action Type 2 707-708 CHAR<br />

56 Administrator Name 32 709-740 CHAR<br />

57 Administrator Address 1 32 741-772 CHAR<br />

58 Administrator Address 2 32 773-804 CHAR<br />

59 Administrator City 15 805-819 CHAR<br />

60 Administrator State 2 820-821 CHAR<br />

61 Administrator Zip 9 822-830 CHAR<br />

62 WCSA Amount 9 831-842 ZD Integer value<br />

63 WCSA Indicator 2 843-844 CHAR<br />

64<br />

WCMSA Settlement<br />

Date<br />

8 845-852 ZD CCYYMMDD<br />

65<br />

Administrator’s<br />

Telephone Number<br />

18 853-870 CHAR<br />

66<br />

Total Rx Settlement<br />

Includes decimal point:<br />

12 871-882 CHAR<br />

Amount<br />

9999999999.99<br />

67<br />

Rx $ included in the<br />

Y = Yes<br />

WCMSA Settlement 1 883 CHAR<br />

N = No<br />

Amount<br />

68 Filler 120 884-1000 CHAR<br />

Total Length = 1000<br />

*Indicates that these fields have same position in PRM <strong>and</strong> SUP record layouts.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-14 COB; Validated Other Health Insurance<br />

Data


Plan Communications User Guide Appendices, Version 6.3<br />

F.5.4 Supplemental Records: Subordinate to DTL (Unlimited Occurrences)<br />

Item Field Size Position Format Valid Values/Description<br />

1 Record Type 3 1-3 CHAR "SUP"<br />

2<br />

HICN/RRB<br />

Number<br />

12 4-15 CHAR Spaces if unknown<br />

3 SSN 9 16-24 ZD 000000000 if unknown<br />

4<br />

Date of Birth<br />

(DOB)<br />

8 25-32 CHAR YYYYMMDD<br />

5 Gender Code 1 33 CHAR 0=unknown, 1 = male, 2 = female<br />

6<br />

7<br />

8<br />

9<br />

10<br />

11<br />

12<br />

RxID<br />

Number*<br />

RxGroup<br />

Number*<br />

RxBIN<br />

Number*<br />

RxPCN<br />

Number*<br />

Rx Plan Toll<br />

Free Number*<br />

Sequence<br />

Number*<br />

COB Source<br />

Code*<br />

20 34-53 ZD<br />

15 54-68 CHAR<br />

6 69-74 ZD<br />

10 75-84 CHAR<br />

18 85-102 CHAR<br />

3 103-105 CHAR<br />

5 106-110 CHAR<br />

11100 Non Payment/Payment Denial<br />

11101 IEQ<br />

11102 Data Match<br />

11103 HMO<br />

11104 Litigation Settlement BCBS<br />

11105 Employer Voluntary Reporting<br />

11106 Insurer Voluntary Reporting<br />

11107 First Claim Development<br />

11108 Trauma Code Development<br />

11109 Secondary Claims Investigation<br />

11110 Self Report<br />

11111 411.25<br />

11112 BCBS Voluntary Agreements<br />

11113 Office of Personnel Management (OPM) Data<br />

Match<br />

11114 Workers' Compensation Data Match<br />

11118 Pharmacy Benefit Manager (PBM)<br />

11120 COBA<br />

11125 Recovery Audit Contractor (RAC) 1 (April<br />

Release)<br />

11126 RAC 2 (April Release)<br />

11127 RAC 3 (April Release)<br />

P0000 PBM<br />

S0000 Assistance Program<br />

Note: Contractor numbers 11100 - 11199 are reserved<br />

for COB<br />

<strong>December</strong> <strong>28</strong>, 2012 F-15 COB; Validated Other Health Insurance<br />

Data


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Format Valid Values/Description<br />

13<br />

Supplemental<br />

Type Code<br />

1 111 CHAR<br />

L=Supplemental<br />

M=Medigap<br />

N=State Program (Non-Qualified SPAP)<br />

O=Other<br />

P=Patient Assistance Program<br />

Q=Qualified State Pharmaceutical Assistance Program<br />

(SPAP)<br />

R=Charity<br />

S=AIDS <strong>Drug</strong> Assistance Program<br />

T=Federal Health Program<br />

1=Medicaid<br />

2=Tricare<br />

3 = Major Medical<br />

14<br />

15<br />

16<br />

17<br />

Coverage<br />

Code*<br />

Insurer's<br />

Name*<br />

Insurer's<br />

Address-1*<br />

Insurer's<br />

Address-2*<br />

1 112 CHAR<br />

32 113-144 CHAR<br />

32 145-176 CHAR<br />

32 177-208 CHAR<br />

18 Insurer's City* 15 209-223 CHAR<br />

U=<strong>Drug</strong> (network benefit)<br />

V=<strong>Drug</strong> with Major Medical (non-network benefit)<br />

19 Insurer's State* 2 224-225 CHAR<br />

20<br />

Insurer's Zip<br />

Code*<br />

9 226-234 CHAR<br />

21 Filler 10 235-244 CHAR Spaces<br />

22<br />

23<br />

Individual<br />

Policy<br />

Number*<br />

Group Policy<br />

Number*<br />

17 245-261 CHAR<br />

20 262-<strong>28</strong>1 CHAR<br />

24<br />

Effective<br />

Date*<br />

8 <strong>28</strong>2-<strong>28</strong>9 ZD CCYYMMDD<br />

25<br />

Termination<br />

Date*<br />

8 290-297 ZD CCYYMMDD<br />

26<br />

Relationship<br />

Code*<br />

2 298-299 CHAR<br />

01=Bene is Policy Holder<br />

02=Spouse<br />

03=Child<br />

04=Other<br />

27 Payer ID* 10 300-309 CHAR<br />

<strong>December</strong> <strong>28</strong>, 2012 F-16 COB; Validated Other Health Insurance<br />

Data


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Format Valid Values/Description<br />

<strong>28</strong> Person Code* 3 310-312 CHAR<br />

29 Payer Order* 3 313-315 ZD<br />

30 Filler 685 316-1000 SPACES<br />

Total Length = 1,000<br />

*Indicates that these fields have same position in PRM <strong>and</strong> SUP record layouts<br />

<strong>December</strong> <strong>28</strong>, 2012 F-17 COB; Validated Other Health Insurance<br />

Data


Plan Communications User Guide Appendices, Version 6.3<br />

F.6 MARX Batch Input Transaction Data File<br />

A transaction file is submitted to CMS by a Plan, <strong>and</strong> consists of a header record followed by<br />

individual transaction records. The transaction code (TC) identifies the type of transaction record.<br />

This section details the contents <strong>and</strong> format that each record type may include in the transaction<br />

file.<br />

This file may include the following records:<br />

• Header Record<br />

• Disenrollment (51/54) Detail Record<br />

• Enrollment (61) Detail Record<br />

• Miscellaneous Change Detail Records:<br />

- Correction (01) Record<br />

- 4Rx Data Change (72)<br />

- Number of Uncovered Months (NUNCMO) Change (73)<br />

- Employer Group Health Plan (EGHP) Change (74)<br />

- Premium Payment Option (PPO) Change (75)<br />

- Residence Address Change (76)<br />

- Segment ID Change (77)<br />

- Part C Premium Change (78)<br />

- Part D Opt-Out (79)<br />

- MMP Opt-Out Update (TC83)<br />

• Cancellation of Enrollment (80) <strong>and</strong> Cancellation of Disenrollment (81) Detail Records<br />

- MMP Enrollment Cancelation (TC82)<br />

F.6.1 Header Record<br />

Item Field Size Position Description<br />

1<br />

Header<br />

Message<br />

12 1-12 "AAAAAAHEADER"<br />

2 Filler 1 13 Spaces<br />

3<br />

Batch File<br />

Type<br />

5 14-18<br />

“RETRO” = retroactive batch file submission;<br />

“POVER” = Plan rollover batch file submission;<br />

“SVIEW” = Special organization review batch file submission.<br />

4 Filler 1 19 Spaces<br />

5<br />

CMS Approval<br />

Request ID<br />

10 20-29<br />

6 Filler 4 30-33 Spaces<br />

7<br />

Current<br />

Calendar<br />

Month (CCM)<br />

6 34-39<br />

8 Filler 261 40-300 Spaces<br />

Total Length = 300<br />

"Spaces" when “Batch File Type,” field #3, contains spaces;<br />

otherwise, the right justified CMS pre-approval request ID from the<br />

special batch request utility.<br />

Reference month for enrollment processing formatted MMYYYY.<br />

The CCM date determines whether to accept a file <strong>and</strong> evaluates the<br />

appropriate effective date for submitted transactions.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-18 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.2 Disenrollment Transaction (TC 51/54) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 Required<br />

8 PBP 3 43-45 Optional<br />

9 Election Type 1 46<br />

Required for all Plan types except HCPP, COST<br />

1 without drug, COST 2 without drug, CCIP/FFS<br />

demo, MDHO demo, MSHO demo, <strong>and</strong> PACE<br />

National <strong>Plans</strong><br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 Transaction Codes (TCs)* 2 60-61 “51” or “54”<br />

13 DRC 2 62-63<br />

14<br />

Effective Date<br />

(YYYYMMDD)<br />

8 64-71 Required<br />

15 Segment ID 3 72-74 Optional<br />

16 Filler 24 75-98 N/A<br />

Required for Involuntary Disenrollments.<br />

Optional for Voluntary Disenrollments.<br />

17 Part D Opt-Out Flag 1 99 Optional for all Part D <strong>Plans</strong>; otherwise blank<br />

18 MMP Opt-Out Flag 1 100 Optional for all <strong>Plans</strong><br />

19 Filler 109 101-209 N/A<br />

20<br />

Plan Transaction Tracking<br />

ID**<br />

15 210-224 Optional<br />

21 Filler 76 225-300 N/A<br />

Total Length = 300<br />

*The “51” transaction is Plan submitted. The “54” is submitted by 1-800-<strong>Medicare</strong> without a header record.<br />

**Plan Transaction Tracking ID field is not used by 1-800-<strong>Medicare</strong>.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-19 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.3 Enrollment Transaction (TC 61) Detailed Record Layout<br />

Item Fields Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 EGHP Flag 1 42 Blank field has a meaning.<br />

8 PBP # 3 43-45 Required<br />

9 Election Type 1 46<br />

10 Contract # 5 47-51 Required<br />

11 Application Date 8 52-59 Required<br />

12 Transaction Code 2 60-61 Required<br />

13 Disenrollment Reason 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Segment ID 3 72-74<br />

16 Filler 5 75-79 N/A<br />

17 ESRD Override 1 80<br />

18<br />

19<br />

Premium Withhold Option/Parts C-<br />

D<br />

Part C Premium Amount<br />

(XXXXvXX)<br />

1 81<br />

6 82-87<br />

20 Filler 6 88-93 N/A<br />

Required: for all Plan types when Note 3 is true;<br />

otherwise not required for HCPP, COST 1 without<br />

drug, COST 2 without drug, CCIP/FFS demo,<br />

MDHO demo, MSHO demo, <strong>and</strong> PACE National<br />

<strong>Plans</strong>.<br />

Optional: if provided, must have three digits <strong>and</strong> a<br />

valid Segment for the Contract/PBP.<br />

Required: for MA <strong>Plans</strong> to successfully enroll<br />

ESRD exceptions.<br />

Required: for all Plan types except HCPP, COST 1<br />

without drug, COST 2 without drug, CCIP/FFS<br />

demo, MSA/MA <strong>and</strong> MSA/demo <strong>Plans</strong>.<br />

Required: for all Plan types except HCPP, COST<br />

1, COST 2, CCIP/FFS demo, MSA/MA <strong>and</strong><br />

MSA/demo <strong>Plans</strong>.<br />

21 Creditable Coverage Flag 1 94 Required: for all Part D <strong>Plans</strong>; otherwise blank.<br />

22 Number of Uncovered Months 3 95-97<br />

23<br />

Employer Subsidy Enrollment<br />

Override Flag<br />

1 98<br />

24 Part D Opt-Out Flag 1 99<br />

25 Filler 35 100-134 N/A<br />

26 Secondary <strong>Drug</strong> Insurance Flag 1 135<br />

Required: for all Part D <strong>Plans</strong>; otherwise blank.<br />

Blank = zero, meaning no uncovered months.<br />

Required: if beneficiary has Employer Subsidy<br />

status for Part D; otherwise blank.<br />

Required: when changing PBPs; 'Y' when Opting<br />

Out of Part D; 'N' when Opting in for Part D;<br />

otherwise, blank.<br />

Required: for Part D <strong>Plans</strong>. Value is 'Y' or 'N' or<br />

blank. For auto/facilitated enrollments <strong>and</strong><br />

<strong>December</strong> <strong>28</strong>, 2012 F-20 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Fields Size Position Description<br />

27 Secondary Rx ID 20 136-155<br />

<strong>28</strong> Secondary Rx Group 15 156-170<br />

29 Enrollment Source 1 171<br />

30 Filler 38 172-209 N/A<br />

31<br />

Plan Assigned Transaction<br />

Tracking ID<br />

15 210-224 Optional<br />

32 Part D Rx BIN 6 225-230<br />

33 Part D Rx PCN 10 231-240<br />

34 Part D Rx Group 15 241-255<br />

35 Part D Rx ID 20 256-275<br />

36 Secondary <strong>Drug</strong> BIN 6 276-<strong>28</strong>1<br />

37 Secondary <strong>Drug</strong> PCN 10 <strong>28</strong>2-291<br />

38 Filler 9 292-300 N/A<br />

Total Length = 300<br />

rollovers, value is blank. For non-Part D <strong>Plans</strong>,<br />

value is blank.<br />

Required: if secondary insurance; otherwise,<br />

blank.<br />

Required: if secondary insurance; otherwise,<br />

blank.<br />

Required: for Point of Service (POS) submitted<br />

enrollment transactions; otherwise, optional.<br />

Required: for all Part D <strong>Plans</strong> except PACE<br />

National <strong>and</strong> MMP; otherwise, blank.<br />

Change-to value for all Part D <strong>Plans</strong>, otherwise<br />

blank.<br />

Change-to value for all Part D <strong>Plans</strong>, otherwise<br />

blank.<br />

Required: for all Part D <strong>Plans</strong> except PACE<br />

National <strong>and</strong> MMP; otherwise, blank.<br />

Required: if secondary insurance; otherwise,<br />

blank.<br />

Required: if secondary insurance; otherwise,<br />

blank.<br />

*The “51” transaction is Plan submitted. The “54” is submitted by 1-800-<strong>Medicare</strong> without a<br />

header record.<br />

**Plan Transaction Tracking ID field is not used by 1-800-<strong>Medicare</strong>.<br />

Note: Election type rules do apply to HCPP, COST 1 without drug, COST 2 without drug,<br />

CCIP/FFS demos, MDHO demo, MSHO demo <strong>and</strong> PACE National enrollments in cases where<br />

such an enrollment would causes an automatic disenrollment from another plan requiring an<br />

election type. It is important that the election type for the Plan on the enrollment request is<br />

consistent with the election type required for automatic disenrollment.<br />

Note: MA organizations <strong>and</strong> cost plans that auto/facilitate enroll LIS Beneficiaries on behalf of<br />

CMS should use the appropriate newly-designated enrollment source code when submitting autoenrollments<br />

or facilitated enrollments: E = Plan-submitted auto-enrollment, F = Plan-submitted<br />

facilitated enrollment, G = Point-of-Sale (POS) submitted enrollment; for use by POS contractor<br />

only, H = CMS reassignment enrollment, I = Assigned to Plan-submitted enrollment with<br />

enrollment source other than any of the following: B, E, F, G, H <strong>and</strong> blank.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-21 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.4 Miscellaneous Change Transactions – Detailed Record Layouts<br />

F.6.4.1 RX Change (TC 72) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1 – 12 Required<br />

2 Surname 12 13 – 24 Required<br />

3 First Name 7 25 – 31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34 – 41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43 – 45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47 – 51 Required<br />

11 Filler 8 52 – 59 N/A<br />

12 Transaction Code (TC) 2 60 – 61 Required<br />

13 Filler 2 62 – 63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64 – 71 Required<br />

15 Filler 63 72-134 N/A<br />

16<br />

17<br />

18<br />

Secondary <strong>Drug</strong> Insurance Flag<br />

Secondary Rx ID<br />

Secondary Rx Group<br />

1 135<br />

20 136-155<br />

15 156-170<br />

19 Filler 54 171-209 N/A<br />

20 Transaction Tracking ID 15 210-224 Optional<br />

21<br />

22<br />

23<br />

Part D Rx BIN<br />

Part D Rx PCN<br />

Part D Rx Group<br />

6 225-230<br />

10 231-240<br />

15 241-255<br />

Blank or new value. Blank does not remove or replace<br />

existing data.<br />

Blank or new additional value. Blank does not remove or<br />

replace existing data.<br />

Blank or new additional value. Blank does not remove or<br />

replace existing data.<br />

Required together with Part D Rx ID when changing 4Rx<br />

primary insurance information. Must include either the<br />

beneficiary’s current field value or the change-to value.<br />

Blank is appropriate when not changing a beneficiary’s 4Rx<br />

primary insurance information.<br />

Change-to value, either a new value or a blank. Blank<br />

removes the beneficiary’s existing value.<br />

Change-to value, either a new value or a blank. Blank<br />

removes the beneficiary’s existing value.<br />

24 Part D Rx ID 20 256-275 Required together with Part D Rx ID when changing 4Rx<br />

primary insurance information. Must include either the<br />

beneficiary’s current field value or the change-to value.<br />

Blank is appropriate when not changing a beneficiary’s 4Rx<br />

primary insurance information.<br />

25<br />

Secondary <strong>Drug</strong> BIN<br />

6 276-<strong>28</strong>1<br />

Blank or new additional value. Blank does not remove or<br />

replace existing data.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-22 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

26<br />

Secondary <strong>Drug</strong> PCN<br />

10 <strong>28</strong>2-291<br />

27 Filler 9 292-300 N/A<br />

Total Length = 300<br />

F.6.4.2 NUNCMO Change (TC 73) Detailed Record Layout<br />

Blank or new additional value. Blank does not remove or<br />

replace existing data.<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43-45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 TC 2 60-61 Required<br />

13 Filler 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Filler 22 72-93 N/A<br />

16 Creditable Coverage Flag 1 94 Required<br />

17 NUNCMO 3 95-97 Blank or change-to value<br />

18 Filler 112 98-209 N/A<br />

19 Transaction Tracking ID 15 210-224 Optional<br />

20 Filler 76 225-300 N/A<br />

Total Length = 300<br />

<strong>December</strong> <strong>28</strong>, 2012 F-23 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.4.3 EGHP Change (TC 74) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 EGHP Flag 1 42 Required change-to value<br />

8 PBP # 3 43-45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 TC 2 60-61 Required<br />

13 Filler 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Filler 138 72-209 N/A<br />

16 Transaction Tracking ID 15 210-224 Optional<br />

17 Filler 76 225-300 N/A<br />

Total Length = 300<br />

F.6.4.4 Premium Payment Option (PPO) Change (TC 75) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43-45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 TC 2 60- 61 Required<br />

13 Filler 2 62- 63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Filler 9 72-80 N/A<br />

<strong>December</strong> <strong>28</strong>, 2012 F-24 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

16 PPO/ Parts C-D 1 81 Required change-to value<br />

17 Filler 1<strong>28</strong> 82-209 N/A<br />

18 Transaction Tracking ID 15 210-224 Optional<br />

19 Filler 76 225- 300 N/A<br />

Total Length = 300<br />

F.6.4.5 Residence Address Change (TC 76) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6<br />

Birth Date<br />

(YYYYMMDD)<br />

8 34-41<br />

7 Filler 5 42-46 N/A<br />

Required<br />

8 Contract # 5 47-51 Required<br />

9 Filler 8 52-59 N/A<br />

10 TC 2 60-61 76<br />

11 Filler 2 62-63 N/A<br />

12<br />

Effective Date<br />

(YYYYMMDD)<br />

8 64-71<br />

13 Filler 3 72-74 N/A<br />

14<br />

Residence Address Line 1<br />

65 75-139<br />

Required<br />

15 Residence Address Line 2 65 140-204 Optional<br />

16 Filler 4 205-208 N/A<br />

17<br />

Address Update/Delete<br />

Flag<br />

1 209-209<br />

Required when Address Update/Delete Flag indicates<br />

“Update” code<br />

Required<br />

18 Transaction Tracking ID 15 210-224 Optional<br />

19<br />

20<br />

21<br />

Residence City<br />

Residence State<br />

Residence Zip Code<br />

57 225-<strong>28</strong>1<br />

2 <strong>28</strong>2-<strong>28</strong>3<br />

5 <strong>28</strong>4-<strong>28</strong>8<br />

22 Residence Zip Code+4 4 <strong>28</strong>9-292 Optional<br />

23 End Date 8 293-300 Optional<br />

Total Length = 300<br />

Required when Address Update/Delete Flag indicates<br />

“Update” code<br />

Required when Address Update/Delete Flag indicates<br />

“Update” code<br />

Required when Address Update/Delete Flag indicates<br />

“Update” code<br />

<strong>December</strong> <strong>28</strong>, 2012 F-25 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.4.6 Segment ID Change (TC 77) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43-45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 TC 2 60-61 Required<br />

13 Filler 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Segment ID 3 72-74 Required<br />

16 Filler 135 75-209 N/A<br />

17 Transaction Tracking ID 15 210-224 Optional<br />

18 Filler 76 225-300 N/A<br />

Total Length = 300<br />

F.6.4.7 Part C Premium Change (TC 78) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HIC# 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Sex 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43-45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 TC 2 60-61 Required<br />

13 Filler 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Filler 10 72-81 N/A<br />

<strong>December</strong> <strong>28</strong>, 2012 F-26 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

16 Part C Premium Amount (XXXXvXX) 6 82-87 Required<br />

17 Filler 122 88-209 N/A<br />

18 Transaction Tracking ID 15 210-224 Optional<br />

19 Filler 76 225-300 N/A<br />

Total Length = 300<br />

F.6.4.8 Part D Opt-Out Change (TC 79) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43-45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 TC 2 60-61 Required<br />

13 Filler 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Filler 27 72-98 N/A<br />

16 Part D Opt-Out Flag 1 99 Required<br />

17 Filler 110 100-209 N/A<br />

18 Transaction Tracking ID 15 210-224 Optional<br />

19 Filler 76 225-300 N/A<br />

Total Length = 300<br />

<strong>December</strong> <strong>28</strong>, 2012 F-27 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.5 Cancellation Transactions – Detailed Record Layouts<br />

F.6.5.1 Cancel Enrollment (TC 80) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HIC# 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Sex 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43-45 Required: if Plan has PBPs<br />

9 Filler 1 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 Transaction Code (TC) 2 60-61 Required<br />

13 Filler 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Filler 138 72-209 N/A<br />

16 Transaction Tracking ID 15 210-224 Optional<br />

17 Filler 76 225-300 N/A<br />

Total Length = 300<br />

F.6.5.2 Cancel Disenrollment Transaction (TC 81) Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Sex 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 5 42-46 N/A<br />

8 Contract # 5 47-51 Required<br />

9 Filler 8 52-59 N/A<br />

10 Transaction Code 2 60-61 Required<br />

11 Filler 2 62-63 N/A<br />

12 Effective Date (YYYYMMDD) 8 64-71 Required<br />

13 Filler 138 72-209 N/A<br />

14 Transaction Tracking ID 15 210-224 Optional<br />

15 Filler 76 225– 300 N/A<br />

Total Length = 300<br />

<strong>December</strong> <strong>28</strong>, 2012 F-<strong>28</strong> MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.5.3 MMP Enrollment Cancellation (TC 82) Detail Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP 3 43-45 Required for PBP contracts; otherwise, spaces<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 Transaction Code (TC) 2 60-61 Required<br />

13 DRC 2 62-63 Optional<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required (must equal the enrollment date)<br />

15 Filler <strong>28</strong> 72-99 N/A<br />

16 MMP Opt-Out Flag 1 100 Optional<br />

17 Filler 109 101-209 N/A<br />

18 Plan Transaction Tracking ID 15 210-224 Optional<br />

19 Filler 76 225-300 N/A<br />

Total Length = 300<br />

<strong>December</strong> <strong>28</strong>, 2012 F-29 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.5.4 MMP Opt-Out Update (TC 83) Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Required<br />

2 Surname 12 13-24 Required<br />

3 First Name 7 25-31 Required<br />

4 M. Initial 1 32 Optional<br />

5 Gender Code 1 33 Required<br />

6 Birth Date (YYYYMMDD) 8 34-41 Required<br />

7 Filler 1 42 N/A<br />

8 PBP # 3 43-45 Required<br />

9 Filler 1 46 N/A<br />

10 Contract # 5 47-51 Required<br />

11 Filler 8 52-59 N/A<br />

12 TC 2 60-61 Required<br />

13 Filler 2 62-63 N/A<br />

14 Effective Date (YYYYMMDD) 8 64-71 Required<br />

15 Filler <strong>28</strong> 72-99 N/A<br />

16 MMP Opt-Out Flag 1 100 Required<br />

17 Filler 109 101-209 N/A<br />

18 Plan Transaction Tracking ID 15 210-224 Optional<br />

19 Filler 76 225-300 N/A<br />

Total Length = 300<br />

F.6.6 Correction Record<br />

Note: The effective date for ‘01’ transactions comes from the file header.<br />

Item Field Size Position Correction Description<br />

1 HICN 12 1-12 R<br />

Nine-byte SSN of primary Beneficiary Claim Account<br />

Number (CAN); two-byte Beneficiary Identification Code<br />

(BIC) one-byte filler (except RRB)<br />

-2 Surname 12 13-24 R Beneficiary’s last name<br />

3 First Name 7 25-31 R Beneficiary’s first name<br />

4 M. Initial 1 32 Beneficiary’s middle initial<br />

D = Institutional ON<br />

E = Medicaid ON<br />

5 Action Code 1 33 R<br />

F = Medicaid OFF<br />

G = Nursing Home Certifiable (NHC) ON<br />

6 Filler 13 34-41 N/A Spaces<br />

7 Contract # 5 47-51 R Contract Number<br />

8 Filler 8 52-59 N/A Spaces<br />

Transaction<br />

9<br />

Code (TC)<br />

2 60-61 R ‘01’ = Correction<br />

10 Filler 239 62-300 N/A Spaces<br />

Total Length = 300<br />

<strong>December</strong> <strong>28</strong>, 2012 F-30 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.6.7 Notes for All Plan-Submitted Transaction Types<br />

Item Field Description<br />

1 HICN Health Insurance Claim Number - CAN plus BIC<br />

2 Surname Beneficiary’s last name<br />

3 First Name Beneficiary’s first name<br />

4 M. Initial Beneficiary’s middle initial<br />

5 Gender Code<br />

1 = male<br />

2 = female<br />

0 = unknown<br />

6<br />

Birth Date<br />

The date of the beneficiary’s birth<br />

(YYYYMMDD) YYYYMMDD<br />

This flag indicates whether the Plan associated with this transaction is an Employer<br />

Group Health Plan (EGHP).<br />

For an Enrollment (TC 61) Transaction:<br />

Y = EGHP<br />

7 EGHP Flag<br />

blank for all others<br />

8 PBP #<br />

9 Election Type<br />

For an EGHP Change (TC 74) Transaction:<br />

Y = EGHP<br />

N = not EGHP<br />

blank = no change<br />

Three-character Plan Benefit Package (PBP) identifier, 001 – 999 (zero padded), for<br />

the plan associated with this transaction.<br />

PBP is required for all organizations except HCPP <strong>and</strong> CCIP/FFS demos. For these<br />

non-PBP organizations, populate with blanks.<br />

The election type associated with the enrollment or disenrollment associated with this<br />

transaction.<br />

A = AEP<br />

D = MADP<br />

E = IEP<br />

F = IEP2<br />

I = ICEP<br />

R = 5 Star Quality Rating SEP<br />

S = Other SEP<br />

T = OEPI<br />

U = Dual/LIS SEP<br />

V = Permanent Change in Residence SEP<br />

W = EGHP SEP<br />

X = Administrative SEP<br />

Y = CMS/Case Worker SEP.<br />

10 Contract #<br />

I, A, D, O, S, N, U, V, W, X, Y <strong>and</strong> T are valid for MA only enrollments.<br />

I, A, D, O, S, U, V, W, X, Y, T, E, F, N, <strong>and</strong> T are valid for MAPD enrollments.<br />

A, S, U, V, W, X, Y, E <strong>and</strong> F are valid for PDP enrollments.<br />

The contract number associated with the transaction.<br />

Hxxxx = local <strong>Plans</strong><br />

Rxxxx = regional <strong>Plans</strong><br />

Sxxxx = PDPs<br />

Fxxxx = fallback <strong>Plans</strong><br />

Exxxx = employer sponsored MA/MAPD <strong>and</strong> PDP <strong>Plans</strong>.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-31 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Description<br />

11 Application Date<br />

12 TC<br />

13 Disenrollment Reason<br />

14<br />

Effective Date<br />

(YYYYMMDD)<br />

15 Segment ID<br />

The application date associated with this enrollment transaction. The application date<br />

is generally the date the enrollment request was initially received by the Plan, as<br />

further defined in the CMS plan enrollment manual guidance.<br />

YYYYMMDD<br />

This identifies the type of transaction submitted on this record.<br />

01 = Internal corrections or cleanups<br />

30 = Turn Bene-Level Demonstration Factor On (Demos Only)<br />

31 = Turn Bene-Level Demonstration Factor Off (Demos Only)<br />

41 = Part D Opt-Out Change (Submitted by CMS)<br />

42 = MMP Opt-Out Update<br />

51 = Disenrollment (MCO or CMS)<br />

54 = Disenrollment (Submitted by 1-800-MEDICARE)<br />

61 = Single Enrollment<br />

72 = 4Rx Record Update<br />

73 = NUNCMO Update<br />

74 = Employer Group Health Plan (EGHP) Update<br />

75 = Premium Payment Option (PPO) Update<br />

76 = Residence Address Update<br />

77 = Segment ID Update<br />

78 = Part C Premium Update<br />

79 = Part D Opt-Out Update<br />

80 = Cancellation of Enrollment<br />

81= Cancellation of Disenrollment<br />

82 = MMP Enrollment Cancellation<br />

83 = MMP Opt-Out Update<br />

The reason the beneficiary is disenrolled from the Plan. This is required for all Plan<br />

submitted Disenrollment transactions. Refer to the published Disenrollment Reason<br />

Code (DRC) list <strong>and</strong> the appropriate CMS plan enrollment manual instructions.<br />

The effective date for the action taken by the submitted transaction.<br />

YYYYMMDD<br />

The three character segment identifier, 001-999 (zero-padded), associated with this<br />

transaction. This is only required for segmented <strong>Plans</strong>. Only local MA/MAPD <strong>Plans</strong><br />

(Hxxxx) may have segments.<br />

For non-segmented plans, this field is populated with blanks.<br />

16 Filler Blank<br />

17 ESRD Override<br />

This is populated to enroll an End Stage Renal Disease (ESRD) beneficiary into a<br />

non-PDP Plan.<br />

Any alpha-numeric value (1-9 <strong>and</strong> A-F) indicates an override.<br />

Zero (0) or blank indicates no override.<br />

18 PPO/ Parts C-D<br />

This indicates the premium payment option (PPO) requested by the beneficiary on<br />

this transaction.<br />

D = Direct self-pay<br />

S = Deduct from SSA benefits<br />

N = No Premium<br />

R = RRB benefits<br />

O = Deduct from OPM benefits (future)<br />

19<br />

Part C Premium<br />

Amount (XXXXvXX)<br />

The option applies to both Part C <strong>and</strong> D premiums.<br />

The amount of the Part C Premium is formatted as six digits with leading zeroes. A<br />

decimal point is assumed 2-digits from right; XXXXvXX. Zero is interpreted as an<br />

actual value. If Part C premium does not apply to the transaction, this field is treated<br />

as blank.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-32 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Description<br />

20 Filler Blank<br />

21<br />

Creditable Coverage<br />

Flag<br />

22 NUNCMO<br />

23<br />

Employer Subsidy<br />

Enrollment Override<br />

Flag<br />

24 Part D Opt-Out Flag<br />

25 MMP Opt-Out Flag<br />

26<br />

Secondary <strong>Drug</strong><br />

Insurance Flag<br />

This indicates whether the beneficiary has creditable drug coverage in the period prior<br />

to this enrollment in a Part D prescription plan. It is also used to reset the count of<br />

uncovered months to zero due to a new IEP or LIS change <strong>and</strong> to remove resets that<br />

were set in error.<br />

For enrollment (TC 61) transactions, valid values are Y, N, R <strong>and</strong> blank.<br />

For NUNCMO change (TC 73), valid values are Y, N, R, U <strong>and</strong> blank.<br />

Y = the beneficiary has creditable coverage.<br />

N = the beneficiary does not have creditable coverage.<br />

R = the accumulated NUNCMO is reset to zero as of the effective date on the<br />

transaction.<br />

U = the previous reset associated with the effective date on the transaction is<br />

removed <strong>and</strong> the total uncovered month accumulation reinstated.<br />

The number of months during which the beneficiary did not have creditable coverage<br />

in the period prior to this enrollment, as determined by the Plan according to the<br />

applicable CMS policy.<br />

A NUNCMO is greater than 0 only if the Creditable Coverage Flag is N.<br />

This field is populated with zero if the Creditable Coverage Flag is Y, R or U.<br />

This flag indicates that the Beneficiary is currently in a Plan receiving an employer<br />

subsidy, but still wants to enroll in a Part D Plan.<br />

Y = override the employer subsidy check <strong>and</strong> enroll the beneficiary<br />

Blank = No override<br />

This flag indicates that the beneficiary does not want AE in a Part D Plan. It applies to<br />

LIS beneficiaries who are subject to AE-FE into Part D.<br />

Y = add the flag to opt-out of Part D AE-FE.<br />

N = remove the flag to opt-out of Part D AE-FE.<br />

Blank = no change to opt-out status<br />

This flag indicates the beneficiary does not want passive enrollment into an MMP.<br />

Y = add the flag to opt-out of passive enrollment into MMPs.<br />

N = remove the flag to opt-out of passive enrollment into an MMP.<br />

Blank = no change to opt-out status<br />

This flag indicates whether that beneficiary has secondary drug insurance.<br />

Y = beneficiary has secondary drug insurance<br />

N = beneficiary does not have secondary drug insurance<br />

blank = status of beneficiary’s secondary drug insurance is unknown<br />

27 Secondary Rx ID<br />

<strong>28</strong> Secondary Rx Group<br />

Secondary insurance Plan's Identifier for a Beneficiary. It can consist of any<br />

combination of alphanumeric characters.<br />

Secondary insurance Plan's Group ID for a Beneficiary. It can consist of any<br />

combination of alphanumeric characters.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-33 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Description<br />

Indicates the source of the enrollment.<br />

A = AE by CMS<br />

B = Beneficiary election (Default when a blank enrollment source is submitted).<br />

C = FE by CMS<br />

D = System generated rollover<br />

E = Plan submitted AE<br />

F = Plan submitted FE<br />

29 Enrollment Source<br />

G = Point of Sale (POS) submitted enrollment<br />

H = Re-assignment submitted by CMS or Plan<br />

J = State-submitted passive enrollment<br />

K = CMS-submitted passive enrollment<br />

L = MMP beneficiary election<br />

M= Default for MMP enrollments submitted without an Enrollment Source<br />

Code (M is not submitted on an enrollment)<br />

30 Filler Blank<br />

31 Transaction Tracking ID Optional value created <strong>and</strong> used by the Plan to track the replies of the transaction.<br />

Part D insurance Plan's Beneficiary Identification Number (BIN)<br />

Numeric <strong>and</strong> right justified<br />

32 Part D Rx BIN<br />

Example: If BIN is five-position numeric (12345), the submitted BIN is a sixposition<br />

numeric with zero added in the first position (012345).<br />

Part D insurance Plan's Pharmacy Control Number (PCN) for the Beneficiary.<br />

33 Part D Rx PCN<br />

Alphanumeric (upper case <strong>and</strong>/or numeric) <strong>and</strong> left justified<br />

Default value = spaces<br />

Part D insurance Plan's group identifier for the Beneficiary.<br />

34 Part D Rx Group Alphanumeric (upper case <strong>and</strong>/or numeric) <strong>and</strong> left justified<br />

Default value = spaces<br />

Part D insurance Plan's ID for the Beneficiary.<br />

35 Part D Rx ID<br />

Alphanumeric (upper case <strong>and</strong>/or numeric) <strong>and</strong> left justified<br />

Default value = spaces<br />

Secondary insurance Plan's BIN number for the Beneficiary.<br />

36 Secondary Rx BIN<br />

Numeric <strong>and</strong> right justified<br />

Secondary insurance Plan's PCN identifier for a Beneficiary.<br />

37 Secondary Rx PCN Alphanumeric (upper case <strong>and</strong>/or numeric) <strong>and</strong> left justified<br />

Default value = spaces<br />

38 Filler Blank<br />

<strong>December</strong> <strong>28</strong>, 2012 F-34 MARX Batch Input<br />

Transaction Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.7 Failed Transaction Data File - OBSOLETE<br />

Effective with the April 2011 Software Release, CMS no longer generates the Failed<br />

Transaction Data File. The reporting of failed records was incorporated into the BCSS Data<br />

file.<br />

The Failed Transaction data file details transactions that CMS cannot load into MARx for<br />

processing due to formatting errors with the file header, user authentication, transaction format or<br />

incorrect data types for transaction data elements. It is sent to the user who submitted the batch.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-35 Failed Transaction Data<br />

File - OBSOLETE


Plan Communications User Guide Appendices, Version 6.3<br />

F.8 Monthly Membership Detail Data File<br />

This is a data file version of the Monthly Membership Detail Report (MMDR). The report lists<br />

every Part C <strong>and</strong> Part D <strong>Medicare</strong> member of the contract <strong>and</strong> provides details about the<br />

payments <strong>and</strong> adjustments made for each. This file contains the data for both Part C <strong>and</strong> Part D<br />

members <strong>and</strong> is generated monthly.<br />

Item Field Size Position Description<br />

1<br />

MCO Contract<br />

Number<br />

5 1-5 MCO Contract Number<br />

2 Run Date of the File 8 6-13 YYYYMMDD<br />

3 Payment Date 6 14-19 YYYYMM<br />

4 HIC Number 12 20-31 Member’s HIC #<br />

5 Surname 7 32-38<br />

6 First Initial 1 39-39<br />

7 Sex 1 40-40 M = Male, F = Female<br />

8 Date of Birth 8 41-48 YYYYMMDD<br />

9 Age Group 4 49-52 BBEE; BB = Beginning Age; EE = Ending Age<br />

10 State & County Code 5 53-57<br />

11 Out of Area Indicator 1 58-58 Y = Out of contract-level service area<br />

12 Part A Entitlement 1 59-59 Y = Entitled to Part A<br />

13 Part B Entitlement 1 60-60 Y = Entitled to Part B<br />

14 Hospice 1 61-61 Y = Hospice<br />

15 ESRD 1 62-62 Y = ESRD<br />

16 Aged/Disabled MSP 1 63-63<br />

‘Y’ = aged/disabled factor applicable to beneficiary;<br />

‘N’ = aged/disabled factor not applicable to beneficiary<br />

17 Institutional 1 64-64 Y = Institutional (monthly)<br />

18 NHC 1 65-65 Y = Nursing Home Certifiable<br />

<strong>December</strong> <strong>28</strong>, 2012 F-36 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

1. Prior to 2008, payments/payment adjustments report:<br />

Y = Medicaid status,<br />

Blank = not Medicaid.<br />

2. In 2008, payments <strong>and</strong> payment adjustments report:<br />

Y = Beneficiary is Medicaid <strong>and</strong> a default risk factor<br />

was used,<br />

N = Beneficiary is not Medicaid <strong>and</strong> a default risk<br />

factor was used,<br />

Blank = CMS is not using a default risk factor or the<br />

beneficiary is Part D only.<br />

3. Beginning in 2009:<br />

Payment adjustments with effective dates in 2008 <strong>and</strong><br />

after, <strong>and</strong> all prospective payments report:<br />

19<br />

Y = Beneficiary is Medicaid <strong>and</strong> a default risk factor<br />

New <strong>Medicare</strong><br />

was used,<br />

Beneficiary Medicaid 1 66-66<br />

Status Flag<br />

N = Beneficiary is not Medicaid <strong>and</strong> a default risk<br />

factor was used,<br />

Blank = CMS is not using a default risk factor or the<br />

beneficiary is Part D only.<br />

Payment adjustments with effective dates in 2007 <strong>and</strong><br />

earlier report as follows:<br />

Y = A payment adjustment was made at a “Medicaid”<br />

rate to the demographic component of a blended<br />

payment.<br />

N = A payment adjustment was made to the<br />

demographic payment component of a blended<br />

payment, not at “Medicaid” rate.<br />

Blank = Either the adjusted payment had no<br />

demographic component, or only the risk portion of a<br />

blended payment was adjusted.<br />

20 LTI Flag 1 67-67 Y = Part C Long-Term Institutional<br />

21 Medicaid Indicator 1 68-68<br />

When:<br />

An RAS-supplied factor is used in the payment, <strong>and</strong><br />

Part C Default Indicator in the Payment Profile is<br />

blank, <strong>and</strong><br />

Medicaid Switch present in the RAS-supplied data that<br />

corresponds to the risk factor used in payment is not<br />

blank then value is Y = Medicaid Add-on Otherwise<br />

the value is blank.<br />

22 PIP-DCG 2 69-70 PIP-DCG Category - Only on pre-2004 adjustments<br />

<strong>December</strong> <strong>28</strong>, 2012 F-37 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

23<br />

24<br />

25<br />

26<br />

27<br />

<strong>28</strong><br />

29<br />

30<br />

31<br />

32<br />

33<br />

Default Risk Factor<br />

Code<br />

Risk Adjuster Factor<br />

A<br />

Risk Adjuster Factor<br />

B<br />

Number of<br />

Paymt/Adjustmt<br />

Months Part A<br />

Number of<br />

Paymt/Adjustmt<br />

Months Part B<br />

Adjustment Reason<br />

Code<br />

Paymt/Adjustment/M<br />

SA Start Date<br />

Paymt/Adjustment/M<br />

SA End Date<br />

Demographic<br />

Paymt/Adjustmt<br />

Amount A<br />

Demographic<br />

Paymt/Adjustmt<br />

Amount B<br />

Monthly<br />

Paymt/Adjustmt<br />

Amount A<br />

1 71-71<br />

7 72-78 NN.DDDD<br />

7 79-85 NN.DDDD<br />

2 86-87 99<br />

2 88-89 99<br />

2 90-91<br />

Prior to 2004, ‘Y’ indicates a new enrollee risk adjustment<br />

(RA) factor was in use.<br />

In the period 2004 through 2008, ‘Y’ indicates that a<br />

default factor was generated by the system due to lack of a<br />

RA factor.<br />

For 2009 <strong>and</strong> after, for payments <strong>and</strong> payment adjustments<br />

<strong>and</strong> regardless of the effective date of the adjustment, the<br />

following applies:<br />

‘1’ = Default Enrollee- Aged/Disabled<br />

‘2’ = Default Enrollee- ESRD dialysis<br />

‘3’ = Default Enrollee- ESRD Transplant Kidney, Month 1<br />

‘4’ = Default Enrollee- ESRD Transplant Kidney, Months 2-<br />

3<br />

‘5’ = Default Enrollee- ESRD Post Graft, Months 4-9<br />

‘6’ = Default Enrollee- ESRD Post Graft, 10+Months<br />

‘7’ = Default Enrollee Chronic Care SNP<br />

Blank = The beneficiary is not a default enrollee.<br />

FORMAT: 99<br />

Always Spaces on Payment <strong>and</strong> MSA Deposit or Recovery<br />

Records<br />

8 92-99 FORMAT: YYYYMMDD<br />

8 100-107 FORMAT: YYYYMMDD<br />

9 108-116<br />

9 117-125<br />

9 126-134<br />

FORMAT: -99999.99<br />

Prior to 2008, Demographic Paymt/Adjustmt Amount A is<br />

displayed.<br />

In 2008 <strong>and</strong> beyond, Demographic Paymt/Adjustmt Amount<br />

A is displayed as 0.00.<br />

FORMAT: -99999.99<br />

Prior to 2008, Demographic Paymt/Adjustmt Amount B is<br />

displayed.<br />

In 2008 <strong>and</strong> beyond, Demographic Paymt/Adjustmt Amount<br />

B is displayed as 0.00.<br />

Part A portion for the beneficiary’s payment or payment<br />

adjustment dollars. For <strong>Medicare</strong> Savings Account (MSA)<br />

<strong>Plans</strong>, the amount does not include any lump sum deposit or<br />

recovery amounts. It is the Plan capitated payment only,<br />

which includes the MSA monthly deposit amount as a<br />

negative term.<br />

FORMAT: -99999.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-38 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

34<br />

35<br />

Monthly<br />

Paymt/Adjustmt<br />

Amount B<br />

LIS Premium<br />

Subsidy<br />

9 135-143<br />

36 ESRD MSP Flag 1 152-152<br />

37<br />

38<br />

39<br />

MSA Part A<br />

Deposit/Recovery<br />

Amount<br />

MSA Part B<br />

Deposit/Recovery<br />

Amount<br />

MSA<br />

Deposit/Recovery<br />

Months<br />

40 Current Medicaid<br />

Status<br />

41<br />

42<br />

Risk Adjuster Age<br />

Group (RAAG)<br />

Previous Disable<br />

Ratio (PRDIB)<br />

Part B portion for the beneficiary’s payment or payment<br />

adjustment dollars. For MSA <strong>Plans</strong>, the amount does not<br />

include any lump sum deposit or recovery amounts. It is the<br />

Plan capitated payment only, which includes the MSA<br />

monthly deposit amount as a negative term.<br />

FORMAT: -99999.99<br />

8 144-151 FORMAT: -9999.99<br />

8 153-160<br />

8 161-168<br />

2 169-170<br />

1 171-171<br />

4 172-175<br />

7 176-182<br />

43 De Minimis 1 183-183<br />

As of January 2011:<br />

T = Transplant/Dialysis<br />

P = Post Graft<br />

Blank = ESRD MSP not applicable<br />

Prior to 2011:<br />

Format X. Values = ‘Y’ or ‘N’(default)<br />

Indicates if <strong>Medicare</strong> is the Secondary Payer<br />

MSA lump sum Part A dollars for deposit/recovery. Deposits<br />

are positive values <strong>and</strong> recoveries are negative.<br />

FORMAT: -9999.99<br />

MSA lump sum Part B dollars for deposit/recovery. Deposits<br />

are positive values <strong>and</strong> recoveries are negative.<br />

FORMAT: -9999.99<br />

Number of months associated with MSA deposit or recovery<br />

dollars<br />

Beginning mid-2008, this field reports the beneficiary current<br />

Medicaid status. (Prior to 11/07, Medicaid status was<br />

reported in field #19.)<br />

‘1’ = Beneficiary is determined as Medicaid as of CPM minus<br />

two (CPM –2) or minus one (CPM – 1),<br />

‘0’ = Beneficiary was not determined as Medicaid as of CPM<br />

minus two (CPM – 2) or minus one (CPM – 1),<br />

Blank = This is a retroactive transaction <strong>and</strong> Medicaid status<br />

is not reported.<br />

The four sources to determine Current Medicaid Status are:<br />

1. MMA State files or Dual <strong>Medicare</strong> Table<br />

2. Low Income Territory Table<br />

3. Medicaid Eligibility Table (Only valid records with a<br />

Medicaid source code of "003U" <strong>and</strong> "003C" are used.)<br />

4. Point of Sale Table<br />

BBEE<br />

BB = Beginning Age<br />

EE = Ending Age<br />

Beginning in 2011, if the risk adjuster factor is from RAS, the<br />

RAAG reported is the one used by RAS in calculating the risk<br />

factor<br />

NN.DDDD<br />

Percentage of Year (in months) for Previous Disable Add-On.<br />

Only on pre-2004 adjustments<br />

Prior to 2008, flag is spaces.<br />

Beginning 2008:<br />

‘N’ = “de minimis” does not apply,<br />

‘Y’ = “de minimis” applies.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-39 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

44<br />

45<br />

Beneficiary Dual <strong>and</strong><br />

Part D Enrollment<br />

Status Flag<br />

Plan Benefit Package<br />

Id<br />

1 184-184<br />

3 185-187<br />

46 Race Code 1 188-188<br />

47<br />

RA Factor Type<br />

Code<br />

2 189-190<br />

0’ – Non-<strong>Drug</strong> Plan without drug benefit, Beneficiary not<br />

dual enrolled<br />

’1’ – <strong>Drug</strong> Plan with drug benefit, Beneficiary not dual<br />

enrolled<br />

‘2’ – Non-<strong>Drug</strong> Plan without drug benefit, Beneficiary dual<br />

enrolled<br />

‘3’ – <strong>Drug</strong> Plan with drug benefit, Beneficiary dual enrolled.<br />

Plan Benefit Package Id<br />

FORMAT 999<br />

Format X<br />

Values:<br />

0 = Unknown<br />

1 = White<br />

2 = Black<br />

3 = Other<br />

4 = Asian<br />

5 = Hispanic<br />

6 = N. American Native<br />

Type of factors in use (see Fields 24-25):<br />

C = Community<br />

C1 = Community Post-Graft I (ESRD)<br />

C2 = Community Post-Graft II (ESRD)<br />

D = Dialysis (ESRD)<br />

E = New Enrollee<br />

ED = New Enrollee Dialysis (ESRD)<br />

E1 = New Enrollee Post-Graft I (ESRD)<br />

E2 = New Enrollee Post-Graft II (ESRD)<br />

G1 = Graft I (ESRD)<br />

G2 = Graft II (ESRD)<br />

I = Institutional<br />

I1 = Institutional Post-Graft I (ESRD)<br />

I2 = Institutional Post-Graft II (ESRD)<br />

SE=New Enrollee Chronic Care SNP<br />

48 Frailty Indicator 1 191-191 Y = MCO-level Frailty Factor Included<br />

49<br />

Original Reason for<br />

Entitlement Code<br />

(OREC)<br />

1 192-192<br />

50 Lag Indicator 1 193-193<br />

51 Segment ID 3 194-196<br />

52 Enrollment Source 1 197<br />

53 EGHP Flag 1 198<br />

54<br />

Part C Basic<br />

Premium – Part A<br />

Amount<br />

8 199-206<br />

0 = Beneficiary insured due to age<br />

1 = Beneficiary insured due to disability<br />

2 = Beneficiary insured due to ESRD<br />

3 = Beneficiary insured due to disability <strong>and</strong> current ESRD<br />

9 = None of the above<br />

Y = Encounter data used to calculate RA factor lags payment<br />

year by 6 months<br />

Identification number of the segment of the PBP. Blank if<br />

there are no segments.<br />

The source of the enrollment. Values are:<br />

A = Auto-enrolled by CMS,<br />

B = Beneficiary election,<br />

C = Facilitated enrollment by CMS,<br />

D = Systematic enrollment by CMS (rollover)<br />

Employer Group flag;<br />

Y = member of employer group,<br />

N = member is not in an employer group<br />

The premium amount for determining the MA payment<br />

attributable to Part A. It is subtracted from the MA Plan<br />

payment for <strong>Plans</strong> that bid above the benchmark. -9999.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-40 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

55<br />

Part C Basic<br />

Premium – Part B<br />

Amount<br />

8 207-214<br />

The premium amount for determining the MA payment<br />

attributable to Part B. It is subtracted from the MA Plan<br />

payment for <strong>Plans</strong> that bid above the benchmark. -9999.99<br />

56<br />

57<br />

58<br />

59<br />

60<br />

61<br />

62<br />

63<br />

64<br />

65<br />

66<br />

Rebate for Part A<br />

Cost Sharing<br />

Reduction<br />

Rebate for Part B<br />

Cost Sharing<br />

Reduction<br />

Rebate for Other Part<br />

A M<strong>and</strong>atory<br />

Supplemental<br />

Benefits<br />

Rebate for Other Part<br />

B M<strong>and</strong>atory<br />

Supplemental<br />

Benefits<br />

Rebate for Part B<br />

Premium Reduction –<br />

Part A Amount<br />

Rebate for Part B<br />

Premium Reduction –<br />

Part B Amount<br />

Rebate for Part D<br />

Supplemental<br />

Benefits – Part A<br />

Amount<br />

Rebate for Part D<br />

Supplemental<br />

Benefits – Part B<br />

Amount<br />

Total Part A MA<br />

Payment<br />

Total Part B MA<br />

Payment<br />

Total MA Payment<br />

Amount<br />

8 215-222<br />

8 223-230<br />

8 231-238<br />

8 239-246<br />

8 247-254<br />

8 255-262<br />

8 263–270<br />

8 271–278<br />

The amount of the rebate allocated to reducing the member’s<br />

Part A cost-sharing. This amount is added to the MA Plan<br />

payment for <strong>Plans</strong> that bid below the benchmark. -9999.99<br />

The amount of the rebate allocated to reducing the member’s<br />

Part B cost-sharing. This amount is added to the MA Plan<br />

payment for <strong>Plans</strong> that bid below the benchmark. -9999.99<br />

The amount of the rebate allocated to providing Part A<br />

supplemental benefits. This amount is added to the MA Plan<br />

payment for <strong>Plans</strong> that bid below the benchmark. -9999.99<br />

The amount of the rebate allocated to providing Part B<br />

supplemental benefits. This amount is added to the MA Plan<br />

payment for <strong>Plans</strong> that bid below the benchmark. -9999.99<br />

The Part A amount of the rebate allocated to reducing the<br />

member’s Part B premium. This amount is retained by CMS<br />

for non ESRD members <strong>and</strong> it is subtracted from ESRD<br />

member’s payments. -9999.99<br />

The Part B amount of the rebate allocated to reducing the<br />

member’s Part B premium. This amount is retained by CMS<br />

for non ESRD members <strong>and</strong> it is subtracted from ESRD<br />

member’s payments. -9999.99<br />

Part A Amount of the rebate allocated to providing Part D<br />

supplemental benefits. -9999.99<br />

Part B Amount of the rebate allocated to providing Part D<br />

supplemental benefits. -9999.99<br />

10 279–<strong>28</strong>8 The total Part A MA payment. -999999.99<br />

10 <strong>28</strong>9–298 The total Part B MA payment. -999999.99<br />

11 299-309<br />

67 Part D RA Factor 7 310-316<br />

68<br />

69<br />

70<br />

Part D Low-Income<br />

Indicator<br />

Part D Low-Income<br />

Multiplier<br />

Part D Long-Term<br />

Institutional Indicator<br />

1 317<br />

7 318-324<br />

1 325<br />

The total MA A/B payment including MMA adjustments.<br />

This also includes the Rebate Amount for Part D<br />

Supplemental Benefits -9999999.99<br />

The member’s Part D risk adjustment factor.<br />

NN.DDDD<br />

From 2006 through 2010, an indicator to identify if the Part D<br />

Low-Income multiplier is included in the Part D payment.<br />

Values are 1 (subset 1), 2 (subset 2) or blank. Beginning<br />

2011, value ‘Y’ indicates the beneficiary is Low Income,<br />

value ‘N’ indicates the beneficiary is not Low Income for the<br />

payment/adjustment being made.<br />

The member’s Part D low-income multiplier. NN.DDDD<br />

For 2011 payment months <strong>and</strong> beyond, field is zero.<br />

From 2006 through 2010, an indicator to identify if the Part D<br />

Long-Term Institutional multiplier is included in the Part D<br />

payment. Values are A (aged), D (disabled) or blank. For<br />

2011 payment months <strong>and</strong> beyond, this field is blank.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-41 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

Part D Long-Term<br />

The member’s Part D institutional multiplier. NN.DDDD<br />

71 Institutional<br />

7 326-332<br />

For 2011 payment months <strong>and</strong> beyond, field is zero.<br />

Multiplier<br />

72<br />

73<br />

74<br />

Rebate for Part D<br />

Basic Premium<br />

Reduction<br />

Part D Basic<br />

Premium Amount<br />

Part D Direct Subsidy<br />

Monthly Payment<br />

Amount<br />

8 333-340<br />

Amount of the rebate allocated to reducing the member’s<br />

basic Part D premium. -9999.99<br />

8 341-348 The Plan’s Part D premium amount. -9999.99<br />

10 349-358<br />

The total Part D Direct subsidy payment for the member.<br />

When POS contract (X is first character of contract number),<br />

then it is total POS Direct Subsidy for the member. -<br />

999999.99<br />

The amount of the reinsurance subsidy included in the<br />

payment. -999999.99<br />

The amount of the low-income subsidy cost-sharing amount<br />

included in the payment. -999999.99<br />

75<br />

Reinsurance Subsidy<br />

Amount<br />

10 359-368<br />

76<br />

Low-Income Subsidy<br />

Cost-Sharing Amount<br />

10 369-378<br />

77 Total Part D Payment 11 379-389 The total Part D payment for the member -9999999.99<br />

Number of<br />

78 Paymt/Adjustmt 2 390-391 99<br />

Months Part D<br />

79<br />

80<br />

81<br />

PACE Premium Add<br />

On<br />

PACE Cost Sharing<br />

Add-on<br />

Part C Frailty Score<br />

Factor<br />

10 392-401 Total Part D Pace Premium Add-on amount -999999.99<br />

10 402-411 Total Part D Pace Cost Sharing Add-on amount -999999.99<br />

7 412-418<br />

82 MSP Factor 7 419-425<br />

83<br />

84<br />

85<br />

MSP<br />

Reduction/Reduction<br />

Adjustment Amount<br />

– Part A<br />

MSP<br />

Reduction/Reduction<br />

Adjustment Amount<br />

– Part B<br />

Medicaid Dual Status<br />

Code<br />

10 426-435<br />

10 436-445<br />

2 446-447<br />

Beneficiary’s Part C frailty score factor, NN.DDDD;<br />

otherwise, spaces<br />

Beneficiary’s MSP secondary payor reduction factor,<br />

NN.DDDD; otherwise, spaces<br />

Net MSP reduction or reduction adjustment dollar amount–<br />

Part A, SSSSSS9.99<br />

Net MSP reduction or reduction adjustment dollar amount –<br />

Part B, SSSSSS9.99<br />

Entitlement status for the dual eligible beneficiary.<br />

The valid values when Field 40 = 1 are:<br />

01 = Eligible is entitled to <strong>Medicare</strong>- QMB only<br />

02 = Eligible is entitled to <strong>Medicare</strong>- QMB AND Medicaid<br />

coverage<br />

03 = Eligible is entitled to <strong>Medicare</strong>- SLMB only<br />

04 = Eligible is entitled to <strong>Medicare</strong>- SLMB AND Medicaid<br />

coverage<br />

05 = Eligible is entitled to <strong>Medicare</strong>- QDWI<br />

06 = Eligible is entitled to <strong>Medicare</strong>- Qualifying individuals<br />

08 = Eligible is entitled to <strong>Medicare</strong>- Other Dual Eligibles<br />

(Non QMB, SLMB,QDWI or QI) with Medicaid coverage<br />

09 = Eligible is entitled to <strong>Medicare</strong> – Other Dual Eligibles<br />

but without Medicaid coverage<br />

99=Unknown<br />

The valid value when Field 40 = 0 is:<br />

00 = No Medicaid Status<br />

The valid value when Field 40 is blank is: Blank<br />

<strong>December</strong> <strong>28</strong>, 2012 F-42 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

Part D Coverage Gap<br />

The amount of the Coverage Gap Discount Amount included<br />

86<br />

8 448-455<br />

Discount Amount<br />

in the payment. -9999.99<br />

Beginning with January 2011 payment, factors in use (see<br />

Field 67):<br />

D1 = Community Non-Low Income Continuing Enrollee,<br />

D2 = Community Low Income Continuing Enrollee,<br />

D3 = Institutional Continuing Enrollee,<br />

D4 = New Enrollee Community Non-Low Income Non-<br />

Part D RA Factor<br />

87<br />

2 456-457 ESRD,<br />

Type<br />

D5 = New Enrollee Community Non-Low Income ESRD,<br />

D6 = New Enrollee Community Low Income Non-ESRD,<br />

D7 = New Enrollee Community Low Income ESRD,<br />

D8 = New Enrollee Institutional Non-ESRD,<br />

D9 = New Enrollee Institutional ESRD,<br />

Blank when it does not apply.<br />

88<br />

89<br />

90<br />

91<br />

Default Part D Risk<br />

Factor Code<br />

Part A Risk Adjusted<br />

Monthly Rate<br />

Amount for Pymt/Adj<br />

Part B Risk Adjusted<br />

Monthly Rate<br />

Amount for Pymt/Adj<br />

Part D Direct Subsidy<br />

Monthly Rate<br />

Amount for Pymt/Adj<br />

1 458<br />

9 459-467<br />

9 468-476<br />

9 477-485<br />

92 Cleanup ID 10 486-495<br />

Total Length = 495<br />

Beginning with January 2011 payment :<br />

1=Not ESRD, Not Low Income, Not Originally Disabled,<br />

2=Not ESRD, Not Low Income, Originally Disabled,<br />

3=Not ESRD, Low Income, Not Originally Disabled,<br />

4=Not ESRD, Low Income, Originally Disabled,<br />

5= ESRD, Not Low Income, Not Originally Disabled,<br />

6= ESRD, Low Income, Not Originally Disabled,<br />

7= ESRD, Not Low Income, Originally Disabled,<br />

8= ESRD, Low Income, Originally Disabled,<br />

Blank when it does not apply.<br />

Beginning August 2011:<br />

Payments = Rate amount in effect for payment period<br />

Adjustments = Rate amount in effect for adjustment period<br />

Format: -99999.99<br />

Beginning August 2011:<br />

Payments = Rate amount in effect for payment period<br />

Adjustments = Rate amount in effect for adjustment period<br />

Format: -99999.99<br />

Beginning August 2011:<br />

Payments = Rate amount in effect for payment period<br />

Adjustments = Rate amount in effect for adjustment period<br />

Format: -99999.99<br />

Cleanup Identifier, a reference linking to further<br />

documentation about a specific cleanup.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-43 Monthly Membership<br />

Detail Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.9 Monthly Membership Summary Data File<br />

This is a data file version of the Monthly Membership Summary Report (MMSR) for both Part C<br />

<strong>and</strong> Part D members, summarizing payments made to a Plan for the month, in several categories;<br />

<strong>and</strong> the adjustments, by all adjustment categories.<br />

Item Field Size Position Description<br />

1 MCO Contract Number 5 1-5 MCO Contract Number<br />

2 Run Date of the File 8 6-13 YYYYMMDD<br />

3 Payment Date 6 14-19 YYYYMM<br />

4 Adjustment Reason Code 2 20-21 Adjustment Reason Code<br />

5 Record Description 10 22-31<br />

Description of the record:<br />

TOTAL PAYM<br />

ESRD<br />

HOSPICE<br />

MCAID<br />

OTHER<br />

WA<br />

OUTOFAREA<br />

DIR SUBSDY<br />

LIS CSTSHR<br />

EST REINS<br />

PACE PRM<br />

PACE CSHR<br />

PTC PREM<br />

RBT AB CSR<br />

RBT AB MSB<br />

RBT D PRRE<br />

RBT D SUBE<br />

PTB PRM RE<br />

B PRM RE A<br />

B PRM RE D<br />

BSF MNTHLY<br />

AD MSP<br />

COV GAP<br />

TOTAL ADJ<br />

HOSPIC ON<br />

HOSPIC OFF<br />

ESRD ON<br />

ESRD OFF<br />

INST ON<br />

INST OF<br />

MCAID ON<br />

MCAID OFF<br />

WKAGE ON<br />

WKAGE OFF<br />

NHC ON<br />

NHC OFF<br />

DEATH<br />

RETRO ENRO<br />

RETRO DISEN<br />

CORR PARTA<br />

RETRO SCC C<br />

CORR DEATH<br />

<strong>December</strong> <strong>28</strong>, 2012 F-44 Monthly Membership<br />

Summary Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

CORR BIRTH<br />

CORR SEX<br />

PTC RATE<br />

CORR PARTB<br />

DISENROLL P<br />

DEMO FACTO<br />

PTC RSK AD<br />

PTCRAF MID<br />

RETRO CHF<br />

HOSPICE RAT<br />

RTRO PTC P<br />

RTRO PTD L<br />

RTRO CST S<br />

RTRO EST R<br />

RTRO PTC R<br />

RTRO REBAT<br />

PTD RATE C<br />

PTD RAF<br />

SEG ID CHG<br />

PTDRAF MID<br />

RETRO MSP<br />

PLN SUB PREM<br />

ESRD MSP<br />

LIPS<br />

XRF MRG<br />

PYMT CORR<br />

CLNUP ADJ<br />

6<br />

Payment Adjustment<br />

Count<br />

7 32-38 Beneficiary Count<br />

7 Month count 7 39-45<br />

For payment record it is Beneficiary Count, but for<br />

adjustment record it is spaces.<br />

8 Part A Member count 7 46-52<br />

For payment records, Beneficiary count for Part A; for<br />

adjustment records, spaces.<br />

9 Part A Month count 7 53-59<br />

For payment record Beneficiary count for Part A , but<br />

for adjustment record it is the number of months<br />

adjusted for Part A.<br />

10 Part B Member count 7 60-66<br />

For payment record Beneficiary count for Part B; for<br />

11 Part B Month count 7 67-73<br />

12<br />

13<br />

Part A<br />

Payment/Adjustment<br />

Amount<br />

Part B<br />

Payment/Adjustment<br />

13 74-86 PART A Amount<br />

13 87-99 PART B Amount<br />

adjustment records, spaces.<br />

For payment record Beneficiary count for Part B but<br />

for adjustment record it is the number of months<br />

adjusted for Part B.<br />

Amount<br />

14 Total Amount 13 100-112 Total Payment/Adjustment Amount<br />

15 Part A Average 9 113-121 Average Part A Amount per Part A Member<br />

16 Part B Average 9 122-130 Average Part B Amount per Part B Member<br />

17<br />

Payment/Adjustment<br />

Indicator<br />

1 131-131 ‘P’ for Payments <strong>and</strong> ‘A’ for Adjustments<br />

18 PBP Number 3 132-134 Plan Benefit Package Number<br />

19 Segment Number 3 135-137 Segment Number<br />

<strong>December</strong> <strong>28</strong>, 2012 F-45 Monthly Membership<br />

Summary Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

20 Part D Member Count 7 138-144<br />

For payment records, beneficiary count for PART D;<br />

for adjustment records, spaces.<br />

21 Part D Month Count 7 145-151<br />

For payment record Beneficiary count for Part D but<br />

for adjustment record it is the number of months<br />

adjusted for Part D.<br />

22 Part D Amount 13 152-164 Part D Amount<br />

23 Part D Average 9 165-173 Average Part D Amount per Part D Member<br />

24<br />

LIS B<strong>and</strong> 25% member<br />

count<br />

7 174-180 Count of Beneficiaries in the 25% LIS b<strong>and</strong><br />

25<br />

LIS B<strong>and</strong> 50% member<br />

count<br />

7 181-187 Count of Beneficiaries in the 50% LIS b<strong>and</strong><br />

26<br />

LIS B<strong>and</strong> 75% member<br />

count<br />

7 188-194 Count of Beneficiaries in the 75% LIS b<strong>and</strong><br />

27<br />

LIS B<strong>and</strong> 100% member<br />

count<br />

7 195-201 Count of Beneficiaries in the 100% LIS b<strong>and</strong><br />

Total Length = 201<br />

<strong>December</strong> <strong>28</strong>, 2012 F-46 Monthly Membership<br />

Summary Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.10 Monthly Premium Withholding Report Data File (MPWR)<br />

This is a monthly reconciliation file of premiums withheld from Social Security Administration<br />

(SSA), Railroad Retirement Board (RRB), or Office of Personnel Management (OPM) checks. It<br />

includes Part C <strong>and</strong> Part D premiums <strong>and</strong> any Part D Late Enrollment Penalties (LEPs). This file<br />

is produced by the Premium Withhold System (PWS), which makes this report available to <strong>Plans</strong><br />

as part of the month-end processing.<br />

The file includes the following records:<br />

<br />

<br />

<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

F.10.1 Header Record<br />

Item Field Size Position Description<br />

1 Record Type 2 1-2<br />

H = Header Record<br />

PIC XX<br />

MCO Contract Number<br />

2 MCO Contract Number 5 3-7<br />

PIC X(5)<br />

YYYYMMDD<br />

3 Payment Date 8 8-15<br />

PIC 9(8)<br />

First 6 digits contain payment month<br />

4 Report Date 8 16-23<br />

YYYYMMDD<br />

Date this report created<br />

PIC 9(8)<br />

5 Filler 142 24-165 Spaces<br />

Total Length = 165<br />

<strong>December</strong> <strong>28</strong>, 2012 F-47 MPWR Data File


F.10.2 Detail Record<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

1 Record Type 2 1-2 D = Detail Record PIC XX<br />

2 MCO Contract Number 5 3-7 MCO Contract Number PIC X(5)<br />

3 Plan Benefit Package Id 3 8-10 Plan Benefit Package ID PIC X(3)<br />

4 Plan Segment Id 3 11-13 PIC X(3)<br />

5 HIC Number 12 14-25 Member’s HIC # PIC X(12)<br />

6 Surname 7 26-32 PIC X(7)<br />

7 First Initial 1 33 PIC X<br />

8 Sex 1 34 M = Male, F = Female PIC X<br />

9 Date of Birth 8 35-42 YYYYMMDD PIC 9(8)<br />

PPO in effect for this Pay Month<br />

“SSA” = Withholding by SSA<br />

10 PPO 3 43-45 “RRB” = Withholding by RRB<br />

“OPM” = Withholding by OPM<br />

PIC X(3)<br />

11 Filler 1 46 Space<br />

12 Premium Period Start Date 8 47-54<br />

Starting Date of Period Premium Payment<br />

Covers<br />

YYYYMMDD PIC 9(8)<br />

13 Premium Period End Date 8 55-62<br />

Ending Date of Period Premium Payment<br />

Covers<br />

YYYYMMDD PIC 9(8)<br />

Number of Months in Premium<br />

14<br />

Period<br />

2 63-64 PIC 99<br />

Part C Premiums Collected for this<br />

Beneficiary, Plan, <strong>and</strong> premium period. A<br />

negative amount indicates a refund by<br />

15 Part C Premiums Collected 8 65-72<br />

withholding agency to Beneficiary of<br />

premiums paid in a prior premium period.<br />

PIC -9999.99<br />

Part D Premiums Collected (excluding LEP)<br />

for this Beneficiary, Plan, <strong>and</strong> premium<br />

period. A negative amount indicates a refund<br />

16 Part D Premiums Collected 8 73-80<br />

by withholding agency to Beneficiary of<br />

premiums paid in a prior premium period.<br />

PIC -9999.99<br />

17<br />

Part D Late Enrollment Penalties<br />

Collected<br />

8 81-88<br />

18 Filler 77 89-165 Spaces<br />

Total Length = 165<br />

Part D Late Enrollment Penalties Collected<br />

for this Beneficiary, Plan, <strong>and</strong> premium<br />

period. A negative amount indicates a refund<br />

by withholding agency to Beneficiary of<br />

penalties paid in a prior premium period. PIC<br />

-9999.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-48 MPWR Data File


F.10.3 Trailer Record<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

1 Record Type 2 1-2 T1 = Trailer Record, withheld totals at<br />

segment level<br />

T2 = Trailer Record, withheld totals at<br />

PBP level<br />

T3 = Trailer record, withheld totals at<br />

contract level<br />

PIC XX<br />

2 MCO Contract Number 5 3-7 MCO contract number<br />

PIC X(5)<br />

3 Plan Benefit Package (PBP) ID 3 8-10 PBP ID, not populated on T3 records<br />

PIC X(3)<br />

4 Plan Segment Id 3 11-13 Not populated on T2 or T3 records<br />

PIC X(3)<br />

5 Total Part C Premiums Collected 14 14-27 Total withholding collections as specified<br />

by Trailer Record type, field (1)<br />

PIC -9(10).99<br />

6 Total Part D Premiums Collected 14 <strong>28</strong>-41 Total withholding collections as specified<br />

by Trailer Record type, field (1)<br />

PIC -9(10).99<br />

7 Total Part D LEPs Collected 14 42-55 Total withholding collections as specified<br />

by Trailer Record type, field (1)<br />

PIC -9(10).99<br />

8 Total Premiums Collected 14 56-69 Total Premiums Collected =<br />

+ Total Part C Premiums Collected<br />

+ Total Part D Premiums Collected<br />

+ Total Part D Penalties Collected<br />

PIC -9(10).99<br />

9 Filler 96 70-165 Spaces<br />

Total Length = 165<br />

<strong>December</strong> <strong>28</strong>, 2012 F-49 MPWR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.11 Part B Claims Data File<br />

F.11.1 Record Type 1<br />

Item Field Size Position Description<br />

1 Contract Number 5 1-5 MCO contract number<br />

2 Record Type 1 6 Record Type Number 6 –<br />

Physician/Supplier<br />

Record Type Number 7 – Durable<br />

Medical Equipment<br />

3 CAN-BIC 12 7-18 HIC Number<br />

4 Period From 8 19-26 Start Date – YYYYMMDD<br />

5 Period To 8 27-34 End Date – YYYYMMDD<br />

6 Date of Birth 8 35-42 Beneficiary's Date of Birth –<br />

YYYYMMDD<br />

7 Surname 6 43-48 First six positions of Beneficiary’s<br />

surname.<br />

8 First Name 1 49 First letter of Beneficiary’s first<br />

name.<br />

9 Middle Initial 1 50 First letter of Beneficiary’s middle<br />

name.<br />

10 Reimbursement Amount 11 51-61 Reimbursement amount for claim.<br />

11 Total Allowed Charges 11 62-72 Total allowed charges for claim.<br />

12 Report Date 6 73-78 Claims processed through date –<br />

YYYYMM. Assigned by the system<br />

as this file is produced. This is the<br />

cut-off date for including a claim in<br />

this file.<br />

13 Contractor identification number 5 79-83 Identification number of the<br />

contractor that processed claim.<br />

14 Provider identification number 10 84-93 Provider’s identification number.<br />

15 Internal Control Number 15 94-108 Internal control number assigned by<br />

the <strong>Medicare</strong> contractor to claim.<br />

16 Provider Payment Amount 11 109-119 Total amount paid to provider for this<br />

claim.<br />

17 Beneficiary Payment Amount 11 120-130 Total amount paid to Beneficiary for<br />

this claim.<br />

18 Filler 57 131-187 Spaces<br />

Total Length = 187<br />

<strong>December</strong> <strong>28</strong>, 2012 F-50 Part B Claims Data File


F.11.2 Record Type 2<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

1 Contract Number 5 1-5 MCO contract number<br />

2 Record Type 1 6 Record Type Number 5 – Home Health Agency<br />

3 CAN-BIC 12 7-18 HIC Number<br />

4 Period From 8 19-26 Start Date – YYYYMMDD<br />

5 Period To 8 27-34 End Date – YYYYMMDD<br />

6 Date of Birth 8 35-42 Beneficiary's Date of Birth – YYYYMMDD<br />

7 Surname 6 43-48 First six positions of Beneficiary’s surname.<br />

8 First Name 1 49 First letter of Beneficiary’s first name.<br />

9 Middle Name 1 50 First letter of Beneficiary’s middle name.<br />

10 Reimbursement 11 51-61 Reimbursement amount for claim.<br />

Amount<br />

11 Total Charges 11 62-72 Total charges on the claim.<br />

12 Report Date 6 73-78 Claims processed through date – YYYYMM. Assigned by the<br />

system when processing claims. This is the cut-off date for<br />

including a claim in this file.<br />

13 Contractor<br />

identification<br />

number<br />

14 Provider<br />

identification<br />

number<br />

5 79-83 Identification number of the contractor that processed the<br />

claim.<br />

6 84-89 Provider’s identification number.<br />

15 Filler 98 90-187 Spaces<br />

Total Length = 187<br />

<strong>December</strong> <strong>28</strong>, 2012 F-51 Part B Claims Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.12 Part C Risk Adjustment Model Output Data File<br />

This is the data file version of the Part C Risk Adjustment Model Output Report, which shows the<br />

Hierarchical Condition Codes (HCCs) used by the RAS to calculate Part C risk adjustment factors<br />

for each Beneficiary. RAS produces the report, <strong>and</strong> MARx forwards it to <strong>Plans</strong> as part of the<br />

month-end processing.<br />

The following records are included in this file:<br />

<br />

<br />

<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

F.12.1 Header Record<br />

Item Field Size Position Comment Description<br />

1 Record Type Code 1 1 Set to "1"<br />

1 = Header<br />

A = Details for old V12 PTC MOR<br />

B = Details for new V21 PTC MOR<br />

3 = Trailer<br />

2 Contract Number 5 2-6 Unique identification for a <strong>Medicare</strong><br />

<strong>Advantage</strong> Contract<br />

3 Run Date 8 7-14 Format as<br />

yyyymmdd<br />

The run date when this file was<br />

created<br />

4 Payment Year <strong>and</strong><br />

Month<br />

6 15-20 Format as<br />

yyyymm<br />

This identifies the risk adjustment<br />

payment year <strong>and</strong> month for the<br />

model run.<br />

5 Filler 180 21-200 Spaces Filler<br />

Total Length = 200<br />

F.12.2 Detail Record Type A<br />

Item Field Size Position Comment Description<br />

1 Record Type<br />

Code<br />

2 Health Insurance<br />

Claim Account<br />

Number<br />

1 1 Set to "A" 1 = Header<br />

A = Details for old V12 PTC<br />

MOR<br />

B = Details for new V21 PTC<br />

MOR<br />

3 = Trailer<br />

12 2-13 Also known as HICAN The HICAN identifies the<br />

primary <strong>Medicare</strong> Beneficiary<br />

under the SSA or RRB programs.<br />

The HICAN, consisting of<br />

Beneficiary Claim Number<br />

(BENE_CAN_NUM) along with<br />

the Beneficiary Identification<br />

Code (BIC_CD), uniquely<br />

identifies a <strong>Medicare</strong> Beneficiary.<br />

For the RRB program, the claim<br />

<strong>December</strong> <strong>28</strong>, 2012 F-52 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

account number is a 12-byte<br />

account number.<br />

3<br />

Beneficiary Last<br />

Name<br />

12 14-25 First 12 bytes of the<br />

Bene Last Name<br />

Beneficiary Last Name<br />

4<br />

Beneficiary First<br />

Name<br />

7 26-32 First 7 bytes of the bene<br />

First Name<br />

Beneficiary First Name<br />

5 Beneficiary Initial 1 33 1-byte Initial Beneficiary Initial<br />

6<br />

Date of Birth 8 34-41 Formatted as yyyymmdd The date of birth of the <strong>Medicare</strong><br />

Beneficiary<br />

7<br />

Sex 1 42 0=unknown, 1=male, Represents the sex of the<br />

2=female<br />

<strong>Medicare</strong> Beneficiary. Examples<br />

include Male <strong>and</strong> Female.<br />

8<br />

9<br />

10<br />

11<br />

12<br />

13<br />

14<br />

15<br />

16<br />

17<br />

Social Security<br />

Number<br />

Age Group<br />

Female0_34<br />

Age Group<br />

Female35_44<br />

Age Group<br />

Female45_54<br />

Age Group<br />

Female55_59<br />

Age Group<br />

Female60_64<br />

Age Group<br />

Female65_69<br />

Age Group<br />

Female70_74<br />

Age Group<br />

Female75_79<br />

Age Group<br />

Female80_84<br />

9 43-51 Also known as<br />

SSN_NUM<br />

1 52 Set to “1” if applicable,<br />

otherwise "0"<br />

1 53 Set to “1” if applicable,<br />

otherwise "0"<br />

1 54 Set to “1” if applicable,<br />

otherwise "0"<br />

1 55 Set to “1” if applicable,<br />

otherwise "0"<br />

1 56 Set to “1” if applicable,<br />

otherwise "0"<br />

1 57 Set to “1” if applicable,<br />

otherwise "0"<br />

1 58 Set to “1” if applicable,<br />

otherwise "0"<br />

1 59 Set to “1” if applicable,<br />

otherwise "0"<br />

1 60 Set to “1” if applicable,<br />

otherwise "0"<br />

The beneficiary's current<br />

identification number that was<br />

assigned by the Social Security<br />

Administration<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 0 <strong>and</strong><br />

34, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 35 <strong>and</strong><br />

44, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 45 <strong>and</strong><br />

54, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 55 <strong>and</strong><br />

59, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 60 <strong>and</strong><br />

64, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 65 <strong>and</strong><br />

69, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 70 <strong>and</strong><br />

74, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 75 <strong>and</strong><br />

79, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages of 80<br />

<strong>December</strong> <strong>28</strong>, 2012 F-53 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

<strong>and</strong> 84, inclusive<br />

18<br />

19<br />

20<br />

21<br />

22<br />

23<br />

24<br />

25<br />

26<br />

27<br />

<strong>28</strong><br />

29<br />

30<br />

Age Group<br />

Female85_89<br />

Age Group<br />

Female90_94<br />

Age Group<br />

Female95_GT<br />

Age Group<br />

Male0_34<br />

Age Group<br />

Male35_44<br />

Age Group<br />

Male45_54<br />

Age Group<br />

Male55_59<br />

Age Group<br />

Male60_64<br />

Age Group<br />

Male65_69<br />

Age Group<br />

Male70_74<br />

Age Group<br />

Male75_79<br />

Age Group<br />

Male80_84<br />

Age Group<br />

Male85_89<br />

1 61 Set to "1" if applicable,<br />

otherwise "0"<br />

1 62 Set to "1" if applicable,<br />

otherwise "0"<br />

1 63 Set to "1" if applicable,<br />

otherwise "0"<br />

1 64 Set to "1" if applicable,<br />

otherwise "0"<br />

1 65 Set to "1" if applicable,<br />

otherwise "0"<br />

1 66 Set to "1" if applicable,<br />

otherwise "0"<br />

1 67 Set to "1" if applicable,<br />

otherwise "0"<br />

1 68 Set to "1" if applicable,<br />

otherwise "0"<br />

1 69 Set to "1" if applicable,<br />

otherwise "0"<br />

1 70 Set to "1" if applicable,<br />

otherwise "0"<br />

1 71 Set to "1" if applicable,<br />

otherwise "0"<br />

1 72 Set to "1" if applicable,<br />

otherwise "0"<br />

1 73 Set to "1" if applicable,<br />

otherwise "0"<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages of 85<br />

<strong>and</strong> 89, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages of 90<br />

<strong>and</strong> 94, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female, age 95 or greater<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 0 <strong>and</strong><br />

34, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 35<br />

<strong>and</strong> 44, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 45<br />

<strong>and</strong> 54, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 55<br />

<strong>and</strong> 59, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date. Male between ages of 60<br />

<strong>and</strong> 64, inclusive.<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 65<br />

<strong>and</strong> 69, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 70<br />

<strong>and</strong> 74, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 75<br />

<strong>and</strong> 79, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 80<br />

<strong>and</strong> 84, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 85<br />

<strong>and</strong> 89, inclusive<br />

<strong>December</strong> <strong>28</strong>, 2012 F-54 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

31<br />

32<br />

33<br />

34<br />

35<br />

36<br />

37<br />

38<br />

39<br />

40<br />

41<br />

42<br />

43<br />

44<br />

45<br />

46<br />

47<br />

48<br />

49<br />

Age Group<br />

Male90_94<br />

Age Group<br />

Male95_GT<br />

Medicaid Female<br />

Disabled<br />

Medicaid Female<br />

Aged<br />

Medicaid Male<br />

Disabled<br />

Medicaid Male<br />

Aged<br />

Originally<br />

Disabled Female<br />

Originally<br />

Disabled Male<br />

Disease<br />

Coefficients<br />

HCC1<br />

Disease<br />

Coefficients<br />

HCC2<br />

Disease<br />

Coefficients<br />

HCC5<br />

Disease<br />

Coefficients<br />

HCC7<br />

Disease<br />

Coefficients<br />

HCC8<br />

Disease<br />

Coefficients<br />

HCC9<br />

Disease<br />

Coefficients<br />

HCC10<br />

Disease<br />

Coefficients<br />

HCC15<br />

Disease<br />

Coefficients<br />

HCC16<br />

Disease<br />

Coefficients<br />

HCC17<br />

Disease<br />

Coefficients<br />

1 74 Set to "1" if applicable,<br />

otherwise "0"<br />

1 75 Set to "1" if applicable,<br />

otherwise "0"<br />

1 76 Set to "1" if applicable,<br />

otherwise "0"<br />

1 77 Set to "1" if applicable,<br />

otherwise "0"<br />

1 78 Set to "1" if applicable,<br />

otherwise "0"<br />

1 79 Set to "1" if applicable,<br />

otherwise "0"<br />

1 80 Set to "1" if applicable,<br />

otherwise "0"<br />

1 81 Set to "1" if applicable,<br />

otherwise "0"<br />

1 82 Set to "1" if applicable,<br />

otherwise "0"<br />

1 83 Set to "1" if applicable,<br />

otherwise "0"<br />

1 84 Set to "1" if applicable,<br />

otherwise "0"<br />

1 85 Set to "1" if applicable,<br />

otherwise "0"<br />

1 86 Set to "1" if applicable,<br />

otherwise "0"<br />

1 87 Set to "1" if applicable,<br />

otherwise "0"<br />

1 88 Set to "1" if applicable,<br />

otherwise "0"<br />

1 89 Set to "1" if applicable,<br />

otherwise "0"<br />

1 90 Set to "1" if applicable,<br />

otherwise "0"<br />

1 91 Set to "1" if applicable,<br />

otherwise "0"<br />

1 92 Set to "1" if applicable,<br />

otherwise "0"<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 90<br />

<strong>and</strong> 94, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male, age 95 or greater<br />

Beneficiary is a female disabled<br />

<strong>and</strong> also entitled to Medicaid.<br />

Beneficiary is a female aged (><br />

64) <strong>and</strong> also entitled to Medicaid.<br />

Beneficiary is a male disabled <strong>and</strong><br />

also entitled to Medicaid.<br />

Beneficiary is a male aged (> 64)<br />

<strong>and</strong> also entitled to Medicaid.<br />

Beneficiary is a female <strong>and</strong><br />

original <strong>Medicare</strong> entitlement was<br />

due to disability.<br />

Beneficiary is a male <strong>and</strong> original<br />

<strong>Medicare</strong> entitlement was due to<br />

disability.<br />

HIV/AIDS<br />

Septicemia/Shock<br />

Opportunistic Infections<br />

Metastatic Cancer <strong>and</strong> Acute<br />

Leukemia<br />

Lung, Upper Digestive Tract, <strong>and</strong><br />

Other Severe Cancers<br />

Lymphatic, Head <strong>and</strong> Neck,<br />

Brain, <strong>and</strong> Other Major Cancers<br />

Breast, Prostate, Colorectal <strong>and</strong><br />

Other Cancers <strong>and</strong> Tumors<br />

Diabetes with Renal or Peripheral<br />

Circulatory Manifestation<br />

Diabetes with Neurologic or<br />

Other Specified Manifestation<br />

Diabetes with Acute<br />

Complications<br />

Diabetes with Ophthalmologic or<br />

Unspecified Manifestation<br />

<strong>December</strong> <strong>28</strong>, 2012 F-55 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

HCC18<br />

50<br />

51<br />

52<br />

53<br />

54<br />

55<br />

56<br />

57<br />

58<br />

59<br />

60<br />

61<br />

62<br />

63<br />

64<br />

65<br />

66<br />

Disease<br />

Coefficients<br />

HCC19<br />

Disease<br />

Coefficients<br />

HCC21<br />

Disease<br />

Coefficients<br />

HCC25<br />

Disease<br />

Coefficients<br />

HCC26<br />

Disease<br />

Coefficients<br />

HCC27<br />

Disease<br />

Coefficients<br />

HCC31<br />

Disease<br />

Coefficients<br />

HCC32<br />

Disease<br />

Coefficients<br />

HCC33<br />

Disease<br />

Coefficients<br />

HCC37<br />

Disease<br />

Coefficients<br />

HCC38<br />

Disease<br />

Coefficients<br />

HCC44<br />

Disease<br />

Coefficients<br />

HCC45<br />

Disease<br />

Coefficients<br />

HCC51<br />

Disease<br />

Coefficients<br />

HCC52<br />

Disease<br />

Coefficients<br />

HCC54<br />

Disease<br />

Coefficients<br />

HCC55<br />

Disease<br />

Coefficients<br />

HCC67<br />

1 93 Set to "1" if applicable,<br />

otherwise "0"<br />

1 94 Set to "1" if applicable,<br />

otherwise "0"<br />

1 95 Set to "1" if applicable,<br />

otherwise "0"<br />

1 96 Set to "1" if applicable,<br />

otherwise "0"<br />

1 97 Set to "1" if applicable,<br />

otherwise "0"<br />

1 98 Set to "1" if applicable,<br />

otherwise "0"<br />

1 99 Set to "1" if applicable,<br />

otherwise "0"<br />

1 100 Set to "1" if applicable,<br />

otherwise "0"<br />

1 101 Set to "1" if applicable,<br />

otherwise "0"<br />

1 102 Set to "1" if applicable,<br />

otherwise "0"<br />

1 103 Set to "1" if applicable,<br />

otherwise "0"<br />

1 104 Set to "1" if applicable,<br />

otherwise "0"<br />

1 105 Set to "1" if applicable,<br />

otherwise "0"<br />

1 106 Set to "1" if applicable,<br />

otherwise "0"<br />

1 107 Set to "1" if applicable,<br />

otherwise "0"<br />

1 108 Set to "1" if applicable,<br />

otherwise "0"<br />

1 109 Set to "1" if applicable,<br />

otherwise "0"<br />

Diabetes without Complication<br />

Protein-Calorie Malnutrition<br />

End-Stage Liver Disease<br />

Cirrhosis of Liver<br />

Chronic Hepatitis<br />

Intestinal Obstruction/Perforation<br />

Pancreatic Disease<br />

Inflammatory Bowel Disease<br />

Bone/Joint/Muscle<br />

Infections/Necrosis<br />

Rheumatoid Arthritis <strong>and</strong><br />

Inflammatory Connective Tissue<br />

Disease<br />

Severe Hematological Disorders<br />

Disorders of Immunity<br />

<strong>Drug</strong>/Alcohol Psychosis<br />

<strong>Drug</strong>/Alcohol Dependence<br />

Schizophrenia<br />

Major Depressive, Bipolar, <strong>and</strong><br />

Paranoid Disorders<br />

Quadriplegia, Other Extensive<br />

Paralysis<br />

<strong>December</strong> <strong>28</strong>, 2012 F-56 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

Disease<br />

67 Coefficients<br />

1 110 Set to "1" if applicable,<br />

otherwise "0"<br />

Paraplegia<br />

HCC68<br />

Disease<br />

68 Coefficients<br />

1 111 Set to "1" if applicable,<br />

otherwise "0"<br />

Spinal Cord Disorders/Injuries<br />

HCC69<br />

Disease<br />

69 Coefficients<br />

1 112 Set to "1" if applicable,<br />

otherwise "0"<br />

Muscular Dystrophy<br />

HCC70<br />

Disease<br />

70 Coefficients<br />

1 113 Set to "1" if applicable,<br />

otherwise "0"<br />

Polyneuropathy<br />

HCC71<br />

Disease<br />

71 Coefficients<br />

1 114 Set to "1" if applicable,<br />

otherwise "0"<br />

Multiple Sclerosis<br />

HCC72<br />

Disease<br />

1 115 Set to "1" if applicable, Parkinson’s <strong>and</strong> Huntington’s<br />

72 Coefficients<br />

otherwise "0"<br />

Diseases<br />

HCC73<br />

73<br />

74<br />

75<br />

76<br />

77<br />

78<br />

79<br />

80<br />

81<br />

82<br />

83<br />

84<br />

Disease<br />

Coefficients<br />

HCC74<br />

Disease<br />

Coefficients<br />

HCC75<br />

Disease<br />

Coefficients<br />

HCC77<br />

Disease<br />

Coefficients<br />

HCC78<br />

Disease<br />

Coefficients<br />

HCC79<br />

Disease<br />

Coefficients<br />

HCC80<br />

Disease<br />

Coefficients<br />

HCC81<br />

Disease<br />

Coefficients<br />

HCC82<br />

Disease<br />

Coefficients<br />

HCC83<br />

Disease<br />

Coefficients<br />

HCC92<br />

Disease<br />

Coefficients<br />

HCC95<br />

Disease<br />

Coefficients<br />

1 116 Set to "1" if applicable,<br />

otherwise "0"<br />

1 117 Set to "1" if applicable,<br />

otherwise "0"<br />

1 118 Set to "1" if applicable,<br />

otherwise "0"<br />

1 119 Set to "1" if applicable,<br />

otherwise "0"<br />

1 120 Set to "1" if applicable,<br />

otherwise "0"<br />

1 121 Set to "1" if applicable,<br />

otherwise "0"<br />

1 122 Set to "1" if applicable,<br />

otherwise "0"<br />

1 123 Set to "1" if applicable,<br />

otherwise "0"<br />

1 124 Set to "1" if applicable,<br />

otherwise "0"<br />

1 125 Set to "1" if applicable,<br />

otherwise "0"<br />

1 126 Set to "1" if applicable,<br />

otherwise "0"<br />

1 127 Set to "1" if applicable,<br />

otherwise "0"<br />

Seizure Disorders <strong>and</strong><br />

Convulsions<br />

Coma, Brain<br />

Compression/Anoxic Damage<br />

Respirator<br />

Dependence/Tracheostomy Status<br />

Respiratory Arrest<br />

Cardio-Respiratory Failure <strong>and</strong><br />

Shock<br />

Congestive Heart Failure<br />

Acute Myocardial Infarction<br />

Unstable Angina <strong>and</strong> Other Acute<br />

Ischemic Heart Disease<br />

Angina Pectoris/Old Myocardial<br />

Infarction<br />

Specified Heart Arrhythmias<br />

Cerebral Hemorrhage<br />

Ischemic or Unspecified Stroke<br />

<strong>December</strong> <strong>28</strong>, 2012 F-57 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

HCC96<br />

85<br />

86<br />

87<br />

88<br />

89<br />

90<br />

91<br />

92<br />

93<br />

94<br />

95<br />

96<br />

97<br />

98<br />

99<br />

100<br />

101<br />

Disease<br />

Coefficients<br />

HCC100<br />

Disease<br />

Coefficients<br />

HCC101<br />

Disease<br />

Coefficients<br />

HCC104<br />

Disease<br />

Coefficients<br />

HCC105<br />

Disease<br />

Coefficients<br />

HCC107<br />

Disease<br />

Coefficients<br />

HCC108<br />

Disease<br />

Coefficients<br />

HCC111<br />

Disease<br />

Coefficients<br />

HCC112<br />

Disease<br />

Coefficients<br />

HCC119<br />

Disease<br />

Coefficients<br />

HCC130<br />

Disease<br />

Coefficients<br />

HCC131<br />

Disease<br />

Coefficients<br />

HCC132<br />

Disease<br />

Coefficients<br />

HCC148<br />

Disease<br />

Coefficients<br />

HCC149<br />

Disease<br />

Coefficients<br />

HCC150<br />

Disease<br />

Coefficients<br />

HCC154<br />

Disease<br />

Coefficients<br />

HCC155<br />

1 1<strong>28</strong> Set to "1" if applicable,<br />

otherwise "0"<br />

1 129 Set to "1" if applicable,<br />

otherwise "0"<br />

1 130 Set to "1" if applicable,<br />

otherwise "0"<br />

1 131 Set to "1" if applicable,<br />

otherwise "0"<br />

1 132 Set to "1" if applicable,<br />

otherwise "0"<br />

1 133 Set to "1" if applicable,<br />

otherwise "0"<br />

1 134 Set to "1" if applicable,<br />

otherwise "0"<br />

1 135 Set to "1" if applicable,<br />

otherwise "0"<br />

1 136 Set to "1" if applicable,<br />

otherwise "0"<br />

1 137 Set to "1" if applicable,<br />

otherwise "0"<br />

1 138 Set to "1" if applicable,<br />

otherwise "0"<br />

1 139 Set to "1" if applicable,<br />

otherwise "0"<br />

1 140 Set to "1" if applicable,<br />

otherwise "0"<br />

1 141 Set to "1" if applicable,<br />

otherwise "0"<br />

1 142 Set to "1" if applicable,<br />

otherwise "0"<br />

1 143 Set to "1" if applicable,<br />

otherwise "0"<br />

1 144 Set to "1" if applicable,<br />

otherwise "0"<br />

Hemiplegia/Hemiparesis<br />

Cerebral Palsy <strong>and</strong> Other<br />

Paralytic Syndromes<br />

Vascular Disease with<br />

Complications<br />

Vascular Disease<br />

Cystic Fibrosis<br />

Chronic Obstructive Pulmonary<br />

Disease<br />

Aspiration <strong>and</strong> Specified<br />

Bacterial Pneumonias<br />

Pneumococcal Pneumonia,<br />

Empyema, Lung Abscess<br />

Proliferative Diabetic<br />

Retinopathy <strong>and</strong> Vitreous<br />

Hemorrhage<br />

Dialysis Status<br />

Renal Failure<br />

Nephritis<br />

Decubitus Ulcer of Skin<br />

Chronic Ulcer of Skin, Except<br />

Decubitus<br />

Extensive Third-Degree Burns<br />

Severe Head Injury<br />

Major Head Injury<br />

<strong>December</strong> <strong>28</strong>, 2012 F-58 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

102<br />

103<br />

104<br />

105<br />

106<br />

107<br />

108<br />

109<br />

110<br />

111<br />

112<br />

113<br />

114<br />

115<br />

116<br />

117<br />

118<br />

119<br />

120<br />

Disease<br />

Coefficients<br />

HCC157<br />

Disease<br />

Coefficients<br />

HCC158<br />

Disease<br />

Coefficients<br />

HCC161<br />

Disease<br />

Coefficients<br />

HCC164<br />

Disease<br />

Coefficients<br />

HCC174<br />

Disease<br />

Coefficients<br />

HCC176<br />

Disease<br />

Coefficients<br />

HCC177<br />

Disabled Disease<br />

HCC5<br />

Disabled Disease<br />

HCC44<br />

Disabled Disease<br />

HCC51<br />

Disabled Disease<br />

HCC52<br />

Disabled Disease<br />

HCC107<br />

Disease<br />

Interactions INT1<br />

Disease<br />

Interactions INT2<br />

Disease<br />

Interactions INT3<br />

Disease<br />

Interactions INT4<br />

Disease<br />

Interactions INT5<br />

Disease<br />

Interactions INT6<br />

1 145 Set to "1" if applicable,<br />

otherwise "0"<br />

1 146 Set to "1" if applicable,<br />

otherwise "0"<br />

1 147 Set to "1" if applicable,<br />

otherwise "0"<br />

1 148 Set to "1" if applicable,<br />

otherwise "0"<br />

1 149 Set to "1" if applicable,<br />

otherwise "0"<br />

1 150 Set to "1" if applicable,<br />

otherwise "0"<br />

1 151 Set to "1" if applicable,<br />

otherwise "0"<br />

Vertebral Fractures without<br />

Spinal Cord Injury<br />

Hip Fracture/Dislocation<br />

Traumatic Amputation<br />

Major Complications of Medical<br />

Care <strong>and</strong> Trauma<br />

Major Organ Transplant Status<br />

Artificial Openings for Feeding or<br />

Elimination<br />

Amputation Status, Lower<br />

Limb/Amputation Complications<br />

1 152 Set to "1" if applicable, Disabled (Age


Plan Communications User Guide Appendices, Version 6.3<br />

F.12.3 Detail Record Type B<br />

Item Field Size Position Comment Description<br />

1 Record Type<br />

Code<br />

2 Health<br />

Insurance<br />

Claim Account<br />

Number<br />

1 1 Set to "B" 1 = Header<br />

A = Details for old V12 PTC MOR<br />

B = Details for new V21 PTC<br />

MOR<br />

3 = Trailer<br />

12 2-13 Also known as HICAN This is the Health Insurance Claim<br />

Account Number (known as<br />

HICAN) identifying the primary<br />

<strong>Medicare</strong> Beneficiary under the<br />

SSA or RRB programs. The<br />

HICAN, consisting of Beneficiary<br />

Claim Number<br />

(BENE_CAN_NUM) along with<br />

the Beneficiary Identification Code<br />

(BIC_CD), uniquely identifies a<br />

<strong>Medicare</strong> Beneficiary. For the<br />

RRB program, the claim account<br />

number is a 12-byte account<br />

number.<br />

3 Beneficiary<br />

Last Name<br />

4 Beneficiary<br />

First Name<br />

12 14-25 First 12 bytes of the Bene<br />

Last Name<br />

7 26-32 First 7 bytes of the bene<br />

First Name<br />

Beneficiary Last Name<br />

Beneficiary First Name<br />

5 Beneficiary<br />

Initial<br />

1 33 1-byte Initial Beneficiary Initial<br />

6 Date of Birth 8 34-41 Formatted as yyyymmdd The date of birth of the <strong>Medicare</strong><br />

Beneficiary<br />

7 Sex 1 42 0=unknown, 1=male,<br />

2=female<br />

Represents the sex of the <strong>Medicare</strong><br />

Beneficiary. Examples include<br />

Male <strong>and</strong> Female.<br />

8 Social Security<br />

Number<br />

9 RAS ESRD<br />

Indicator<br />

Switch<br />

10 Age Group<br />

Female0_34<br />

9 43-51 Also known as<br />

SSN_NUM<br />

1 52 Y = ESRD<br />

N = not ESRD<br />

1 53 Set to “1” if applicable,<br />

otherwise "0"<br />

The beneficiary's current<br />

identification number that was<br />

assigned by the Social Security<br />

Administration<br />

The beneficiary's ESRD status as of<br />

the model run. Also indicates if the<br />

beneficiary was processed by the<br />

ESRD models in the model run.<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 0 <strong>and</strong><br />

34, inclusive<br />

<strong>December</strong> <strong>28</strong>, 2012 F-60 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

11 Age Group<br />

Female35_44<br />

12 Age Group<br />

Female45_54<br />

13 Age Group<br />

Female55_59<br />

14 Age Group<br />

Female60_64<br />

15 Age Group<br />

Female65_69<br />

16 Age Group<br />

Female70_74<br />

17 Age Group<br />

Female75_79<br />

18 Age Group<br />

Female80_84<br />

19 Age Group<br />

Female85_89<br />

20 Age Group<br />

Female90_94<br />

21 Age Group<br />

Female95_GT<br />

1 54 Set to “1” if applicable,<br />

otherwise "0"<br />

1 55 Set to “1” if applicable,<br />

otherwise "0"<br />

1 56 Set to “1” if applicable,<br />

otherwise "0"<br />

1 57 Set to “1” if applicable,<br />

otherwise "0"<br />

1 58 Set to “1” if applicable,<br />

otherwise "0"<br />

1 59 Set to “1” if applicable,<br />

otherwise "0"<br />

1 60 Set to “1” if applicable,<br />

otherwise "0"<br />

1 61 Set to “1” if applicable,<br />

otherwise "0"<br />

1 62 Set to "1" if applicable,<br />

otherwise "0"<br />

1 63 Set to "1" if applicable,<br />

otherwise "0"<br />

1 64 Set to "1" if applicable,<br />

otherwise "0"<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 35 <strong>and</strong><br />

44, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 45 <strong>and</strong><br />

54, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 55 <strong>and</strong><br />

59, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 60 <strong>and</strong><br />

64, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 65 <strong>and</strong><br />

69, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 70 <strong>and</strong><br />

74, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages 75 <strong>and</strong><br />

79, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages of 80<br />

<strong>and</strong> 84, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages of 85<br />

<strong>and</strong> 89, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female between ages of 90<br />

<strong>and</strong> 94, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: female, age 95 or greater<br />

<strong>December</strong> <strong>28</strong>, 2012 F-61 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

22 Age Group<br />

Male0_34<br />

23 Age Group<br />

Male35_44<br />

24 Age Group<br />

Male45_54<br />

25 Age Group<br />

Male55_59<br />

26 Age Group<br />

Male60_64<br />

27 Age Group<br />

Male65_69<br />

<strong>28</strong> Age Group<br />

Male70_74<br />

29 Age Group<br />

Male75_79<br />

30 Age Group<br />

Male80_84<br />

31 Age Group<br />

Male85_89<br />

32 Age Group<br />

Male90_94<br />

1 65 Set to "1" if applicable,<br />

otherwise "0"<br />

1 66 Set to "1" if applicable,<br />

otherwise "0"<br />

1 67 Set to "1" if applicable,<br />

otherwise "0"<br />

1 68 Set to "1" if applicable,<br />

otherwise "0"<br />

1 69 Set to "1" if applicable,<br />

otherwise "0"<br />

1 70 Set to "1" if applicable,<br />

otherwise "0"<br />

1 71 Set to "1" if applicable,<br />

otherwise "0"<br />

1 72 Set to "1" if applicable,<br />

otherwise "0"<br />

1 73 Set to "1" if applicable,<br />

otherwise "0"<br />

1 74 Set to "1" if applicable,<br />

otherwise "0"<br />

1 75 Set to "1" if applicable,<br />

otherwise "0"<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 0 <strong>and</strong><br />

34, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 35 <strong>and</strong><br />

44, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 45 <strong>and</strong><br />

54, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 55 <strong>and</strong><br />

59, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 60 <strong>and</strong><br />

64, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 65 <strong>and</strong><br />

69, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 70 <strong>and</strong><br />

74, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 75 <strong>and</strong><br />

79, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 80 <strong>and</strong><br />

84, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 85 <strong>and</strong><br />

89, inclusive<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male between ages of 90 <strong>and</strong><br />

94, inclusive<br />

<strong>December</strong> <strong>28</strong>, 2012 F-62 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

33 Age Group<br />

Male95_GT<br />

34 Medicaid<br />

Female<br />

Disabled<br />

35 Medicaid<br />

Female Aged<br />

36 Medicaid Male<br />

Disabled<br />

37 Medicaid Male<br />

Aged<br />

38 Originally<br />

Disabled<br />

Female<br />

39 Originally<br />

Disabled Male<br />

1 76 Set to "1" if applicable,<br />

otherwise "0"<br />

1 77 Set to "1" if applicable,<br />

otherwise "0"<br />

1 78 Set to "1" if applicable,<br />

otherwise "0"<br />

1 79 Set to "1" if applicable,<br />

otherwise "0"<br />

1 80 Set to "1" if applicable,<br />

otherwise "0"<br />

1 81 Set to "1" if applicable,<br />

otherwise "0"<br />

1 82 Set to "1" if applicable,<br />

otherwise "0"<br />

The sex <strong>and</strong> age group for the<br />

beneficiary based on a given as of<br />

date: male, age 95 or greater<br />

Beneficiary is a female disabled<br />

<strong>and</strong> also entitled to Medicaid.<br />

Beneficiary is a female aged (> 64)<br />

<strong>and</strong> also entitled to Medicaid.<br />

Beneficiary is a male disabled <strong>and</strong><br />

also entitled to Medicaid.<br />

Beneficiary is a male aged (> 64)<br />

<strong>and</strong> also entitled to Medicaid.<br />

Beneficiary is a female <strong>and</strong> original<br />

<strong>Medicare</strong> entitlement was due to<br />

disability.<br />

Beneficiary is a male <strong>and</strong> original<br />

<strong>Medicare</strong> entitlement was due to<br />

disability.<br />

40 HCC001 1 83 Set to "1" if applicable,<br />

otherwise "0"<br />

41 HCC002 1 84 Set to "1" if applicable,<br />

otherwise "0"<br />

42 HCC006 1 85 Set to "1" if applicable,<br />

otherwise "0"<br />

43 HCC008 1 86 Set to "1" if applicable,<br />

otherwise "0"<br />

44 HCC009 1 87 Set to "1" if applicable,<br />

otherwise "0"<br />

45 HCC010 1 88 Set to "1" if applicable,<br />

otherwise "0"<br />

46 HCC011 1 89 Set to "1" if applicable,<br />

otherwise "0"<br />

47 HCC012 1 90 Set to "1" if applicable,<br />

otherwise "0"<br />

48 HCC017 1 91 Set to "1" if applicable,<br />

otherwise "0"<br />

49 HCC018 1 92 Set to "1" if applicable,<br />

otherwise "0"<br />

HIV/AIDS<br />

Septicemia, Sepsis, Systemic<br />

Inflammatory Response<br />

Syndrome/Shock<br />

Opportunistic Infections<br />

Metastatic Cancer <strong>and</strong> Acute<br />

Leukemia<br />

Lung <strong>and</strong> Other Severe Cancers<br />

Lymphoma <strong>and</strong> Other Cancers<br />

Colorectal, Bladder, <strong>and</strong> Other<br />

Cancers<br />

Breast, Prostate, <strong>and</strong> Other Cancers<br />

<strong>and</strong> Tumors<br />

Diabetes with Acute Complications<br />

Diabetes with Chronic<br />

Complications<br />

<strong>December</strong> <strong>28</strong>, 2012 F-63 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

50 HCC019 1 93 Set to "1" if applicable,<br />

otherwise "0"<br />

51 HCC021 1 94 Set to "1" if applicable,<br />

otherwise "0"<br />

52 HCC022 1 95 Set to "1" if applicable,<br />

otherwise "0"<br />

53 HCC023 1 96 Set to "1" if applicable,<br />

otherwise "0"<br />

54 HCC027 1 97 Set to "1" if applicable,<br />

otherwise "0"<br />

55 HCC0<strong>28</strong> 1 98 Set to "1" if applicable,<br />

otherwise "0"<br />

56 HCC029 1 99 Set to "1" if applicable,<br />

otherwise "0"<br />

57 HCC033 1 100 Set to "1" if applicable,<br />

otherwise "0"<br />

58 HCC034 1 101 Set to "1" if applicable,<br />

otherwise "0"<br />

59 HCC035 1 102 Set to "1" if applicable,<br />

otherwise "0"<br />

60 HCC039 1 103 Set to "1" if applicable,<br />

otherwise "0"<br />

61 HCC040 1 104 Set to "1" if applicable,<br />

otherwise "0"<br />

62 HCC046 1 105 Set to "1" if applicable,<br />

otherwise "0"<br />

63 HCC047 1 106 Set to "1" if applicable,<br />

otherwise "0"<br />

64 HCC048 1 107 Set to "1" if applicable,<br />

otherwise "0"<br />

65 HCC051 1 108 Set to "1" if applicable,<br />

otherwise "0"<br />

66 HCC052 1 109 Set to "1" if applicable,<br />

otherwise "0"<br />

67 HCC054 1 110 Set to "1" if applicable,<br />

otherwise "0"<br />

Diabetes without Complication<br />

Protein-Calorie Malnutrition<br />

Morbid Obesity<br />

Other Significant Endocrine <strong>and</strong><br />

Metabolic Disorders<br />

End-Stage Liver Disease<br />

Cirrhosis of Liver<br />

Chronic Hepatitis<br />

Intestinal Obstruction/Perforation<br />

Chronic Pancreatitis<br />

Inflammatory Bowel Disease<br />

Bone/Joint/Muscle<br />

Infections/Necrosis<br />

Rheumatoid Arthritis <strong>and</strong><br />

Inflammatory Connective Tissue<br />

Disease<br />

Severe Hematological Disorders<br />

Disorders of Immunity<br />

Coagulation Defects <strong>and</strong> Other<br />

Specified Hematological Disorders<br />

Dementia With Complications<br />

Dementia Without Complication<br />

<strong>Drug</strong>/Alcohol Psychosis<br />

<strong>December</strong> <strong>28</strong>, 2012 F-64 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

68 HCC055 1 111 Set to "1" if applicable,<br />

otherwise "0"<br />

69 HCC057 1 112 Set to "1" if applicable,<br />

otherwise "0"<br />

70 HCC058 1 113 Set to "1" if applicable,<br />

otherwise "0"<br />

71 HCC070 1 114 Set to "1" if applicable,<br />

otherwise "0"<br />

72 HCC071 1 115 Set to "1" if applicable,<br />

otherwise "0"<br />

73 HCC072 1 116 Set to "1" if applicable,<br />

otherwise "0"<br />

74 HCC073 1 117 Set to "1" if applicable,<br />

otherwise "0"<br />

75 HCC074 1 118 Set to "1" if applicable,<br />

otherwise "0"<br />

76 HCC075 1 119 Set to "1" if applicable,<br />

otherwise "0"<br />

77 HCC076 1 120 Set to "1" if applicable,<br />

otherwise "0"<br />

78 HCC077 1 121 Set to "1" if applicable,<br />

otherwise "0"<br />

79 HCC078 1 122 Set to "1" if applicable,<br />

otherwise "0"<br />

80 HCC079 1 123 Set to "1" if applicable,<br />

otherwise "0"<br />

81 HCC080 1 124 Set to "1" if applicable,<br />

otherwise "0"<br />

82 HCC082 1 125 Set to "1" if applicable,<br />

otherwise "0"<br />

83 HCC083 1 126 Set to "1" if applicable,<br />

otherwise "0"<br />

84 HCC084 1 127 Set to "1" if applicable,<br />

otherwise "0"<br />

85 HCC085 1 1<strong>28</strong> Set to "1" if applicable,<br />

otherwise "0"<br />

86 HCC086 1 129 Set to "1" if applicable,<br />

otherwise "0"<br />

<strong>Drug</strong>/Alcohol Dependence<br />

Schizophrenia<br />

Major Depressive, Bipolar, <strong>and</strong><br />

Paranoid Disorders<br />

Quadriplegia<br />

Paraplegia<br />

Spinal Cord Disorders/Injuries<br />

Amyotrophic Lateral Sclerosis <strong>and</strong><br />

Other Motor Neuron Disease<br />

Cerebral Palsy<br />

Polyneuropathy<br />

Muscular Dystrophy<br />

Multiple Sclerosis<br />

Parkinson’s <strong>and</strong> Huntington’s<br />

Diseases<br />

Seizure Disorders <strong>and</strong> Convulsions<br />

Coma, Brain Compression/Anoxic<br />

Damage<br />

Respirator<br />

Dependence/Tracheostomy Status<br />

Respiratory Arrest<br />

Cardio-Respiratory Failure <strong>and</strong><br />

Shock<br />

Congestive Heart Failure<br />

Acute Myocardial Infarction<br />

<strong>December</strong> <strong>28</strong>, 2012 F-65 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

87 HCC087 1 130 Set to "1" if applicable,<br />

otherwise "0"<br />

88 HCC088 1 131 Set to "1" if applicable,<br />

otherwise "0"<br />

89 HCC096 1 132 Set to "1" if applicable,<br />

otherwise "0"<br />

90 HCC099 1 133 Set to "1" if applicable,<br />

otherwise "0"<br />

91 HCC100 1 134 Set to "1" if applicable,<br />

otherwise "0"<br />

92 HCC103 1 135 Set to "1" if applicable,<br />

otherwise "0"<br />

93 HCC104 1 136 Set to "1" if applicable,<br />

otherwise "0"<br />

94 HCC106 1 137 Set to "1" if applicable,<br />

otherwise "0"<br />

95 HCC107 1 138 Set to "1" if applicable,<br />

otherwise "0"<br />

96 HCC108 1 139 Set to "1" if applicable,<br />

otherwise "0"<br />

97 HCC110 1 140 Set to "1" if applicable,<br />

otherwise "0"<br />

98 HCC111 1 141 Set to "1" if applicable,<br />

otherwise "0"<br />

99 HCC112 1 142 Set to "1" if applicable,<br />

otherwise "0"<br />

100 HCC114 1 143 Set to "1" if applicable,<br />

otherwise "0"<br />

101 HCC115 1 144 Set to "1" if applicable,<br />

otherwise "0"<br />

102 HCC122 1 145 Set to "1" if applicable,<br />

otherwise "0"<br />

103 HCC124 1 146 Set to "1" if applicable,<br />

otherwise "0"<br />

104 HCC134 1 147 Set to "1" if applicable,<br />

otherwise "0"<br />

105 HCC135 1 148 Set to "1" if applicable,<br />

otherwise "0"<br />

Unstable Angina <strong>and</strong> Other Acute<br />

Ischemic Heart Disease<br />

Angina Pectoris<br />

Specified Heart Arrhythmias<br />

Cerebral Hemorrhage<br />

Ischemic or Unspecified Stroke<br />

Hemiplegia/Hemiparesis<br />

Monoplegia, Other Paralytic<br />

Syndromes<br />

Atherosclerosis of the Extremities<br />

with Ulceration or Gangrene<br />

Vascular Disease with<br />

Complications<br />

Vascular Disease<br />

Cystic Fibrosis<br />

Chronic Obstructive Pulmonary<br />

Disease<br />

Fibrosis of Lung <strong>and</strong> Other Chronic<br />

Lung Disorders<br />

Aspiration <strong>and</strong> Specified Bacterial<br />

Pneumonias<br />

Pneumococcal Pneumonia,<br />

Emphysema, Lung Abscess<br />

Proliferative Diabetic Retinopathy<br />

<strong>and</strong> Vitreous Hemorrhage<br />

Exudative Macular Degeneration<br />

Dialysis Status<br />

Acute Renal Failure<br />

<strong>December</strong> <strong>28</strong>, 2012 F-66 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

106 HCC136 1 149 Set to "1" if applicable,<br />

otherwise "0"<br />

107 HCC137 1 150 Set to "1" if applicable,<br />

otherwise "0"<br />

108 HCC138 1 151 Set to "1" if applicable,<br />

otherwise "0"<br />

109 HCC139 1 152 Set to "1" if applicable,<br />

otherwise "0"<br />

110 HCC140 1 153 Set to "1" if applicable,<br />

otherwise "0"<br />

111 HCC141 1 154 Set to "1" if applicable,<br />

otherwise "0"<br />

112 HCC157 1 155 Set to "1" if applicable,<br />

otherwise "0"<br />

113 HCC158 1 156 Set to "1" if applicable,<br />

otherwise "0"<br />

114 HCC159 1 157 Set to "1" if applicable,<br />

otherwise "0"<br />

115 HCC160 1 158 Set to "1" if applicable,<br />

otherwise "0"<br />

116 HCC161 1 159 Set to "1" if applicable,<br />

otherwise "0"<br />

117 HCC162 1 160 Set to "1" if applicable,<br />

otherwise "0"<br />

118 HCC166 1 161 Set to "1" if applicable,<br />

otherwise "0"<br />

119 HCC167 1 162 Set to "1" if applicable,<br />

otherwise "0"<br />

120 HCC169 1 163 Set to "1" if applicable,<br />

otherwise "0"<br />

121 HCC170 1 164 Set to "1" if applicable,<br />

otherwise "0"<br />

122 HCC173 1 165 Set to "1" if applicable,<br />

otherwise "0"<br />

123 HCC176 1 166 Set to "1" if applicable,<br />

otherwise "0"<br />

Chronic Kidney Disease, Stage 5<br />

Chronic Kidney Disease, Severe<br />

(Stage 4)<br />

Chronic Kidney Disease, Moderate<br />

(Stage 3)<br />

Chronic Kidney Disease, Mild or<br />

Unspecified (Stages 1-2 or<br />

Unspecified)<br />

Unspecified Renal Failure<br />

Nephritis<br />

Pressure Ulcer of Skin with<br />

Necrosis Through to Muscle,<br />

Tendon, or Bone<br />

Pressure Ulcer of Skin with Full<br />

Thickness Skin Loss<br />

Pressure Ulcer of Skin with Partial<br />

Thickness Skin Loss<br />

Pressure Pre-Ulcer Skin Changes or<br />

Unspecified Stage<br />

Chronic Ulcer of Skin, Except<br />

Pressure<br />

Severe Skin Burn or Condition<br />

Severe Head Injury<br />

Major Head Injury<br />

Vertebral Fractures without Spinal<br />

Cord Injury<br />

Hip Fracture/Dislocation<br />

Traumatic Amputations <strong>and</strong><br />

Complications<br />

Complications of Specified<br />

Implanted Device or Graft<br />

<strong>December</strong> <strong>28</strong>, 2012 F-67 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

124 HCC186 1 167 Set to "1" if applicable,<br />

otherwise "0"<br />

125 HCC188 1 168 Set to "1" if applicable,<br />

otherwise "0"<br />

126 HCC189 1 169 Set to "1" if applicable,<br />

otherwise "0"<br />

Major Organ Transplant or<br />

Replacement Status<br />

Artificial Openings for Feeding or<br />

Elimination<br />

Amputation Status, Lower<br />

Limb/Amputation Complications<br />

127 Disabled<br />

Disease<br />

HCC006<br />

1<strong>28</strong> Disabled<br />

Disease<br />

HCC034<br />

129 Disabled<br />

Disease<br />

HCC046<br />

130 Disabled<br />

Disease<br />

HCC054<br />

131 Disabled<br />

Disease<br />

HCC055<br />

132 Disabled<br />

Disease<br />

HCC110<br />

133 Disabled<br />

Disease<br />

HCC176<br />

134 CANCER_<br />

IMMUNE<br />

1 170 Set to "1" if applicable,<br />

otherwise "0"<br />

1 171 Set to "1" if applicable,<br />

otherwise "0"<br />

1 172 Set to "1" if applicable,<br />

otherwise "0"<br />

1 173 Set to "1" if applicable,<br />

otherwise "0"<br />

1 174 Set to "1" if applicable,<br />

otherwise "0"<br />

1 175 Set to "1" if applicable,<br />

otherwise "0"<br />

1 176 Set to "1" if applicable,<br />

otherwise "0"<br />

1 177 Set to "1" if applicable,<br />

otherwise "0"<br />

Disabled (Age


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

140 Medicaid 1 183 Set to "1" if applicable,<br />

otherwise "0"<br />

Beneficiary is entitled to Medicaid.<br />

141 Originally<br />

Disabled<br />

142 Disabled<br />

Disease<br />

HCC039<br />

143 Disabled<br />

Disease<br />

HCC077<br />

144 Disabled<br />

Disease<br />

HCC085<br />

145 Disabled<br />

Disease<br />

HCC161<br />

1 184 Set to "1" if applicable,<br />

otherwise "0"<br />

1 185 Set to "1" if applicable,<br />

otherwise "0"<br />

1 186 Set to "1" if applicable,<br />

otherwise "0"<br />

1 187 Set to "1" if applicable,<br />

otherwise "0"<br />

1 188 Set to "1" if applicable,<br />

otherwise "0"<br />

Beneficiary original <strong>Medicare</strong><br />

entitlement was due to disability.<br />

Disabled (Age


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

154 SEPSIS_<br />

ASP_SPEC_<br />

BACT_<br />

PNEUM<br />

155 SEPSIS_<br />

PRESSURE_<br />

ULCER<br />

1 197 Set to "1" if applicable SEPSIS_ASP_SPEC_BACT_<br />

PNEUM<br />

1 198 Set to "1" if applicable SEPSIS_PRESSURE_ULCER<br />

156 Filler 1 199 - 200 Spaces Filler<br />

Total Length = 200.<br />

NOTE: Fields 140-155 are associated with the CMS HCC V21 Institutional Score only.<br />

F.12.4 Trailer Record<br />

Item Field Size Position Comment Description<br />

1 Record Type 1 1 Set to "3" 1 = Header<br />

A = Details for old V12<br />

PTC MOR<br />

B = Details for new V21<br />

PTC MOR<br />

3 = Trailer<br />

2<br />

3<br />

Contract<br />

Number<br />

Total Record<br />

Count<br />

5 2-6<br />

9 7-15<br />

Also known as MCO Plan number<br />

Includes all header <strong>and</strong> trailer records<br />

4 Filler 185 16-200 Spaces Filler<br />

Total Length = 200<br />

Unique identification for a<br />

Managed Care Organization<br />

(MCO) enabling the MCO<br />

to provide coverage to<br />

eligible beneficiaries<br />

Record count in display<br />

format<br />

<strong>December</strong> <strong>28</strong>, 2012 F-70 Part C Risk Adjustment Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.13 Risk Adjustment System (RAS) <strong>Prescription</strong> <strong>Drug</strong> Hierarchical Condition<br />

Category (RxHCC) Model Output Data File - aka Part D RA Model Output Data<br />

File<br />

The following records are included in this file:<br />

<br />

<br />

<br />

Header Record<br />

Detail/Beneficiary Record Format<br />

Trailer Record<br />

F.13.1 Header Record<br />

The Contract Header Record signals the beginning of the detail/Beneficiary records for a<br />

<strong>Medicare</strong> <strong>Advantage</strong> or st<strong>and</strong>-alone PDP contract.<br />

Item Field Size Position Comment Description<br />

1<br />

2<br />

Record Type<br />

Code<br />

Contract<br />

Number<br />

1 1 Set to "1"<br />

5 2-6<br />

3 Run Date 8 7-14<br />

4<br />

Payment Year<br />

<strong>and</strong> Month<br />

6 15-20<br />

Also known as<br />

MCO plan<br />

number<br />

Format as<br />

yyyymmdd<br />

Format as<br />

yyyymm<br />

5 Filler 148 21-168 Spaces Filler<br />

Total Length = 168<br />

1 = Header<br />

2 = Details<br />

3 = Trailer<br />

Unique identification for a Managed Care<br />

Organization (MCO) enabling the MCO to provide<br />

coverage to eligible beneficiaries.<br />

The run date when this file was created.<br />

This identifies the risk adjustment payment year <strong>and</strong><br />

month for the model run.<br />

F.13.2 Detail/Beneficiary Record<br />

Each Detail/Beneficiary Record contains information for an HCC beneficiary in a <strong>Medicare</strong><br />

<strong>Prescription</strong> <strong>Drug</strong> contract/plan, as of the last RAS model run for the current calendar/payment<br />

year.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-71 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

1<br />

2<br />

3<br />

4<br />

Record Type<br />

Code<br />

Health Insurance<br />

Claim Account<br />

Number<br />

Beneficiary Last<br />

Name<br />

Beneficiary First<br />

Name<br />

1 1 Set to "2" 1 = Header, 2 = Details, 3 = Trailer<br />

12 2-13<br />

12 14-25<br />

7 26-32<br />

Also known as<br />

HICAN<br />

First 12 bytes<br />

of the Bene<br />

Last Name<br />

First 7 bytes of<br />

the bene First<br />

Name<br />

This is the Health Insurance Claim Account Number<br />

(known as HICAN) identifying the primary <strong>Medicare</strong><br />

Beneficiary under the SSA or RRB programs. The<br />

HICAN, consisting of Beneficiary Claim Number<br />

(BENE_CAN_NUM) along with the Beneficiary<br />

Identification Code (BIC_CD), uniquely identifies a<br />

<strong>Medicare</strong> Beneficiary. For the RRB program, the claim<br />

account number is a 12-byte account number.<br />

Beneficiary Last Name<br />

Beneficiary First Name<br />

5 Beneficiary Initial 1 33 1 byte Initial Beneficiary Initial<br />

6 Date of Birth 8 34-41<br />

7 Sex 1 42<br />

8<br />

9<br />

10<br />

11<br />

12<br />

13<br />

14<br />

15<br />

Social Security<br />

Number<br />

Age Group<br />

Female 0-34<br />

Age Group<br />

Female35_44<br />

Age Group<br />

Female45_54<br />

Age Group<br />

Female55_59<br />

Age Group<br />

Female60_64<br />

Age Group<br />

Female65_69<br />

Age Group<br />

Female70_74<br />

9 43-51<br />

1 52<br />

1 53<br />

1 54<br />

1 55<br />

1 56<br />

1 57<br />

1 58<br />

Formatted as<br />

yyyymmdd<br />

0=unknown,<br />

1=male,<br />

2=female<br />

Also known as<br />

SSN_NUM<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

The date of birth of the <strong>Medicare</strong> Beneficiary<br />

Represents the sex of the <strong>Medicare</strong> Beneficiary.<br />

The beneficiary's current identification number that was<br />

assigned by the Social Security Administration.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 0 <strong>and</strong> 34.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 35 <strong>and</strong> 44,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 45 <strong>and</strong> 54,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 55 <strong>and</strong> 59,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 60 <strong>and</strong> 64,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 65 <strong>and</strong> 69,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 70 <strong>and</strong> 74,<br />

inclusive.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-72 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

16<br />

17<br />

18<br />

19<br />

20<br />

21<br />

22<br />

23<br />

24<br />

25<br />

26<br />

27<br />

<strong>28</strong><br />

29<br />

30<br />

Age Group<br />

Female75_79<br />

Age Group<br />

Female80_84<br />

Age Group<br />

Female85_89<br />

Age Group<br />

Female90_94<br />

Age Group<br />

Female95_GT<br />

Age Group<br />

Male0_34<br />

Age Group<br />

Male35_44<br />

Age Group<br />

Male45_54<br />

Age Group<br />

Male55_59<br />

Age Group<br />

Male60_64<br />

Age Group<br />

Male65_69<br />

Age Group<br />

Male70_74<br />

Age Group<br />

Male75_79<br />

Age Group<br />

Male80_84<br />

Age Group<br />

Male85_89<br />

1 59<br />

1 60<br />

1 61<br />

1 62<br />

1 63<br />

1 64<br />

1 65<br />

1 66<br />

1 67<br />

1 68<br />

1 69<br />

1 70<br />

1 71<br />

1 72<br />

1 73<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 75 <strong>and</strong> 79,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 80 <strong>and</strong> 84,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 85 <strong>and</strong> 89,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female between ages of 90 <strong>and</strong> 94,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Female, age 95 <strong>and</strong> greater.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 0 <strong>and</strong> 34,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 35 <strong>and</strong> 44,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 45 <strong>and</strong> 54,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 55 <strong>and</strong> 59,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 60 <strong>and</strong> 64,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 65 <strong>and</strong> 69,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 70 <strong>and</strong> 74,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 75 <strong>and</strong> 79,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 80 <strong>and</strong> 84,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 85 <strong>and</strong> 89,<br />

inclusive.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-73 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

31<br />

32<br />

33<br />

34<br />

35<br />

36<br />

37<br />

38<br />

39<br />

40<br />

41<br />

42<br />

43<br />

44<br />

45<br />

Age Group<br />

Male90_94<br />

Age Group<br />

Male95_GT<br />

Originally<br />

Disabled Female<br />

Originally<br />

Disabled Male<br />

Disease<br />

Coefficients<br />

RXHCC1<br />

Disease<br />

Coefficients<br />

RXHCC5<br />

Disease<br />

Coefficients<br />

RXHCC8<br />

Disease<br />

Coefficients<br />

RXHCC9<br />

Disease<br />

Coefficients<br />

RXHCC10<br />

Disease<br />

Coefficients<br />

RXHCC11<br />

Disease<br />

Coefficients<br />

RXHCC14<br />

Disease<br />

Coefficients<br />

RXHCC15<br />

Disease<br />

Coefficients<br />

RXHCC18<br />

Disease<br />

Coefficients<br />

RXHCC19<br />

Disease<br />

Coefficients<br />

RXHCC20<br />

1 74<br />

1 75<br />

1 76<br />

1 77<br />

1 78<br />

1 79<br />

1 80<br />

1 81<br />

1 82<br />

1 83<br />

1 84<br />

1 85<br />

1 86<br />

1 87<br />

1 88<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male between ages of 90 <strong>and</strong> 94,<br />

inclusive.<br />

The sex <strong>and</strong> age group for the beneficiary based on a<br />

given as of date. Male, age 95 <strong>and</strong> greater.<br />

Beneficiary is a female <strong>and</strong> original <strong>Medicare</strong><br />

entitlement was due to disability.<br />

Beneficiary is a male <strong>and</strong> original <strong>Medicare</strong> entitlement<br />

was due to disability.<br />

HIV/AIDS<br />

Opportunistic Infections<br />

Chronic Myeloid Leukemia<br />

Multiple Myeloma <strong>and</strong> Other Neoplastic Disorders<br />

Breast, Lung, <strong>and</strong> Other Cancers <strong>and</strong> Tumors<br />

Prostate <strong>and</strong> Other Cancers <strong>and</strong> Tumors<br />

Diabetes with Complications<br />

Diabetes without Complication<br />

Diabetes Insipidus <strong>and</strong> Other Endocrine <strong>and</strong> Metabolic<br />

Disorders<br />

Pituitary, Adrenal Gl<strong>and</strong>, <strong>and</strong> Other Endocrine <strong>and</strong><br />

Metabolic Disorders<br />

Thyroid Disorders<br />

<strong>December</strong> <strong>28</strong>, 2012 F-74 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

46<br />

47<br />

48<br />

49<br />

50<br />

51<br />

52<br />

53<br />

54<br />

55<br />

56<br />

57<br />

58<br />

59<br />

60<br />

Disease<br />

Coefficients<br />

RXHCC21<br />

Disease<br />

Coefficients<br />

RXHCC23<br />

Disease<br />

Coefficients<br />

RXHCC25<br />

Disease<br />

Coefficients<br />

RXHCC30<br />

Disease<br />

Coefficients<br />

RXHCC31<br />

Disease<br />

Coefficients<br />

RXHCC32<br />

Disease<br />

Coefficients<br />

RXHCC33<br />

Disease<br />

Coefficients<br />

RXHCC38<br />

Disease<br />

Coefficients<br />

RXHCC40<br />

Disease<br />

Coefficients<br />

RXHCC41<br />

Disease<br />

Coefficients<br />

RXHCC42<br />

Disease<br />

Coefficients<br />

RXHCC45<br />

Disease<br />

Coefficients<br />

RXHCC47<br />

Disease<br />

Coefficients<br />

RXHCC48<br />

Disease<br />

Coefficients<br />

RXHCC49<br />

1 89<br />

1 90<br />

1 91<br />

1 92<br />

1 93<br />

1 94<br />

1 95<br />

1 96<br />

1 97<br />

1 98<br />

1 99<br />

1 100<br />

1 101<br />

1 102<br />

1 103<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Morbid Obesity<br />

Disorders of Lipoid Metabolism<br />

Chronic Viral Hepatitis<br />

Chronic Pancreatitis<br />

Pancreatic Disorders <strong>and</strong> Intestinal Malabsorption,<br />

Except Pancreatitis<br />

Inflammatory Bowel Disease<br />

Esophageal Reflux <strong>and</strong> Other Disorders of Esophagus<br />

Aseptic Necrosis of Bone<br />

Psoriatic Arthropathy<br />

Rheumatoid Arthritis <strong>and</strong> Other Inflammatory<br />

Polyarthropathy<br />

Systemic Lupus Erythematosus, Other Connective<br />

Tissue Disorders, <strong>and</strong> Inflammatory Spondylopathies<br />

Osteoporosis, Vertebral <strong>and</strong> Pathological Fractures<br />

Sickle Cell Anemia<br />

Myelodysplastic Syndromes, Except High-Grade<br />

Immune Disorders<br />

<strong>December</strong> <strong>28</strong>, 2012 F-75 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

61<br />

62<br />

63<br />

64<br />

65<br />

66<br />

67<br />

68<br />

69<br />

70<br />

71<br />

72<br />

73<br />

74<br />

75<br />

Disease<br />

Coefficients<br />

RXHCC50<br />

Disease<br />

Coefficients<br />

RXHCC54<br />

Disease<br />

Coefficients<br />

RXHCC55<br />

Disease<br />

Coefficients<br />

RXHCC58<br />

Disease<br />

Coefficients<br />

RXHCC59<br />

Disease<br />

Coefficients<br />

RXHCC60<br />

Disease<br />

Coefficients<br />

RXHCC61<br />

Disease<br />

Coefficients<br />

RXHCC62<br />

Disease<br />

Coefficients<br />

RXHCC63<br />

Disease<br />

Coefficients<br />

RXHCC65<br />

Disease<br />

Coefficients<br />

RXHCC66<br />

Disease<br />

Coefficients<br />

RXHCC67<br />

Disease<br />

Coefficients<br />

RXHCC68<br />

Disease<br />

Coefficients<br />

RXHCC71<br />

Disease<br />

Coefficients<br />

RXHCC72<br />

1 104<br />

1 105<br />

1 106<br />

1 107<br />

1 108<br />

1 109<br />

1 110<br />

1 111<br />

1 112<br />

1 113<br />

1 114<br />

1 115<br />

1 116<br />

1 117<br />

1 118<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Aplastic Anemia <strong>and</strong> Other Significant Blood Disorders<br />

Alzheimer's Disease<br />

Dementia, Except Alzheimer's Disease<br />

Schizophrenia<br />

Bipolar Disorders<br />

Major Depression<br />

Specified Anxiety, Personality, <strong>and</strong> Behavior Disorders<br />

Depression<br />

Anxiety Disorders<br />

Autism<br />

Profound or Severe Mental Retardation/Developmental<br />

Disability<br />

Moderate Mental Retardation/Developmental Disability<br />

Mild or Unspecified Mental Retardation/Developmental<br />

Disability<br />

Myasthenia Gravis, Amyotrophic Lateral Sclerosis <strong>and</strong><br />

Other Motor Neuron Disease<br />

Spinal Cord Disorders<br />

<strong>December</strong> <strong>28</strong>, 2012 F-76 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

76<br />

77<br />

78<br />

79<br />

80<br />

81<br />

82<br />

83<br />

84<br />

85<br />

86<br />

87<br />

88<br />

89<br />

90<br />

Disease<br />

Coefficients<br />

RXHCC74<br />

Disease<br />

Coefficients<br />

RXHCC75<br />

Disease<br />

Coefficients<br />

RXHCC76<br />

Disease<br />

Coefficients<br />

RXHCC78<br />

Disease<br />

Coefficients<br />

RXHCC79<br />

Disease<br />

Coefficients<br />

RXHCC80<br />

Disease<br />

Coefficients<br />

RXHCC81<br />

Disease<br />

Coefficients<br />

RXHCC83<br />

Disease<br />

Coefficients<br />

RXHCC86<br />

Disease<br />

Coefficients<br />

RXHCC87<br />

Disease<br />

Coefficients<br />

RXHCC88<br />

Disease<br />

Coefficients<br />

RXHCC89<br />

Disease<br />

Coefficients<br />

RXHCC93<br />

Disease<br />

Coefficients<br />

RXHCC97<br />

Disease<br />

Coefficients<br />

RXHCC98<br />

1 119<br />

1 120<br />

1 121<br />

1 122<br />

1 123<br />

1 124<br />

1 125<br />

1 126<br />

1 127<br />

1 1<strong>28</strong><br />

1 129<br />

1 130<br />

1 131<br />

1 132<br />

1 133<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Polyneuropathy<br />

Multiple Sclerosis<br />

Parkinson's Disease<br />

Intractable Epilepsy<br />

Epilepsy <strong>and</strong> Other Seizure Disorders, Except<br />

Intractable Epilepsy<br />

Convulsions<br />

Migraine Headaches<br />

Trigeminal <strong>and</strong> Postherpetic Neuralgia<br />

Pulmonary Hypertension <strong>and</strong> Other Pulmonary Heart<br />

Disease<br />

Congestive Heart Failure<br />

Hypertension<br />

Coronary Artery Disease<br />

Atrial Arrhythmias<br />

Cerebrovascular Disease, Except Hemorrhage or<br />

Aneurysm<br />

Spastic Hemiplegia<br />

<strong>December</strong> <strong>28</strong>, 2012 F-77 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

91<br />

92<br />

93<br />

94<br />

95<br />

96<br />

97<br />

98<br />

99<br />

100<br />

101<br />

102<br />

103<br />

104<br />

105<br />

Disease<br />

Coefficients<br />

RXHCC100<br />

Disease<br />

Coefficients<br />

RXHCC101<br />

Disease<br />

Coefficients<br />

RXHCC103<br />

Disease<br />

Coefficients<br />

RXHCC104<br />

Disease<br />

Coefficients<br />

RXHCC105<br />

Disease<br />

Coefficients<br />

RXHCC106<br />

Disease<br />

Coefficients<br />

RXHCC111<br />

Disease<br />

Coefficients<br />

RXHCC113<br />

Disease<br />

Coefficients<br />

RXHCC120<br />

Disease<br />

Coefficients<br />

RXHCC121<br />

Disease<br />

Coefficients<br />

RXHCC122<br />

Disease<br />

Coefficients<br />

RXHCC123<br />

Disease<br />

Coefficients<br />

RXHCC124<br />

Disease<br />

Coefficients<br />

RXHCC125<br />

Disease<br />

Coefficients<br />

RXHCC126<br />

1 134<br />

1 135<br />

1 136<br />

1 137<br />

1 138<br />

1 139<br />

1 140<br />

1 141<br />

1 142<br />

1 143<br />

1 144<br />

1 145<br />

1 146<br />

1 147<br />

1 148<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Venous Thromboembolism<br />

Peripheral Vascular Disease<br />

Cystic Fibrosis<br />

Chronic Obstructive Pulmonary Disease <strong>and</strong> Asthma<br />

Pulmonary Fibrosis <strong>and</strong> Other Chronic Lung Disorders<br />

Gram-Negative/Staphylococcus Pneumonia <strong>and</strong> Other<br />

Lung Infections<br />

Diabetic Retinopathy<br />

Open-Angle Glaucoma<br />

Kidney Transplant Status<br />

Dialysis Status<br />

Chronic Kidney Disease Stage 5<br />

Chronic Kidney Disease Stage 4<br />

Chronic Kidney Disease Stage 3<br />

Chronic Kidney Disease Stage 1, 2, or Unspecified<br />

Nephritis<br />

<strong>December</strong> <strong>28</strong>, 2012 F-78 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

106<br />

107<br />

108<br />

109<br />

110<br />

111<br />

112<br />

113<br />

114<br />

115<br />

116<br />

117<br />

118<br />

119<br />

120<br />

Disease<br />

Coefficients<br />

RXHCC142<br />

Disease<br />

Coefficients<br />

RXHCC145<br />

Disease<br />

Coefficients<br />

RXHCC147<br />

Disease<br />

Coefficients<br />

RXHCC156<br />

Disease<br />

Coefficients<br />

RXHCC166<br />

Disease<br />

Coefficients<br />

RXHCC167<br />

Disease<br />

Coefficients<br />

RXHCC168<br />

Originally<br />

Disabled<br />

NONAGED<br />

RXHCC1<br />

NONAGED<br />

RXHCC58<br />

NONAGED<br />

RXHCC59<br />

NONAGED<br />

RXHCC60<br />

NONAGED<br />

RXHCC61<br />

NONAGED<br />

RXHCC62<br />

NONAGED<br />

RXHCC63<br />

1 149<br />

1 150<br />

1 151<br />

1 152<br />

1 153<br />

1 154<br />

1 155<br />

1 156<br />

1 157<br />

1 158<br />

1 159<br />

1 160<br />

1 161<br />

1 162<br />

1 163<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Chronic Ulcer of Skin, Except Pressure<br />

Pemphigus<br />

Psoriasis, Except with Arthropathy<br />

Narcolepsy <strong>and</strong> Cataplexy<br />

Lung Transplant Status<br />

Major Organ Transplant Status, Except Lung, Kidney,<br />

<strong>and</strong> Pancreas<br />

Pancreas Transplant Status<br />

The original reason for <strong>Medicare</strong> entitlement was due to<br />

disability.<br />

Non-Aged <strong>and</strong> HIV/AIDS<br />

Non-Aged <strong>and</strong> Schizophrenia<br />

Non-Aged <strong>and</strong> Bipolar Disorders<br />

Non-Aged <strong>and</strong> Major Depression<br />

Non-Aged <strong>and</strong> Specified Anxiety, Personality, <strong>and</strong><br />

Behavior Disorders<br />

Non-Aged <strong>and</strong> Depression<br />

Non-Aged <strong>and</strong> Anxiety Disorders<br />

<strong>December</strong> <strong>28</strong>, 2012 F-79 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Comment Description<br />

121<br />

122<br />

123<br />

124<br />

125<br />

NONAGED<br />

RXHCC65<br />

NONAGED<br />

RXHCC75<br />

NONAGED<br />

RXHCC78<br />

NONAGED<br />

RXHCC79<br />

NONAGED<br />

RXHCC80<br />

1 164<br />

1 165<br />

1 166<br />

1 167<br />

1 168<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Set to "1" if<br />

applicable,<br />

otherwise "0"<br />

Non-Aged <strong>and</strong> Autism<br />

Non-Aged <strong>and</strong> Multiple Sclerosis<br />

Non-Aged <strong>and</strong> Intractable Epilepsy<br />

Non-Aged <strong>and</strong> Epilepsy <strong>and</strong> Other Seizure Disorders,<br />

Except Intractable Epilepsy<br />

Non-Aged <strong>and</strong> Convulsions<br />

Total Length = 168<br />

NOTE: Fields 113-125 are associated with the Rx HCC Continuing Enrollee Institutional Score only.<br />

F.13.3 Trailer Record<br />

The Contract Trailer Record signals the end of the detail/Beneficiary records for a MA or st<strong>and</strong>-alone PDP contract.<br />

This record has a length of 164.<br />

Item Field Size Position Comment Description<br />

1<br />

2<br />

3<br />

Record<br />

Type Code<br />

Contract<br />

Number<br />

Total<br />

Record<br />

Count<br />

1 1 Set to "3"<br />

5 2-6<br />

9 7-15<br />

<br />

<br />

<br />

1 = Header<br />

2 = Details<br />

3 = Trailer<br />

Unique identification for a Managed Care<br />

Also known as<br />

Organization (MCO) enabling the MCO to provide<br />

MCO plan number<br />

coverage to eligible beneficiaries.<br />

Includes all header<br />

<strong>and</strong> trailer records<br />

Record count in display format 9(9).<br />

4 Filler 153 16-168 Spaces Filler<br />

Total Length = 168<br />

<strong>December</strong> <strong>28</strong>, 2012 F-80 RAS RxHCC Model Output<br />

Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.14 Daily Transaction Reply Report (DTRR) Data File<br />

The DTRR is created each evening, Monday through Saturday, <strong>and</strong> is available for <strong>Plans</strong> the<br />

following business day. All <strong>Plans</strong> receive a DTRR for all contracts whether the Plan has or has not<br />

submitted transactions for processing by MARx. The TRC of 000 indicates that there is no data<br />

within the DTRR for processing by the Plan. In turn, the Plan does not need to take any action <strong>and</strong><br />

may discard this file.<br />

The file also contains records that report the submitted transactions verbatim back to the <strong>Plans</strong><br />

(F.14.1).<br />

F.14.1 DTRR Data File Detailed Record Layout<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 Health Insurance Claim Number<br />

2 Surname 12 13-24 Beneficiary Surname<br />

3 First Name 7 25-31 Beneficiary Given Name<br />

4 Middle Initial 1 32 Beneficiary Middle Initial<br />

5 Gender Code 1 33 Beneficiary Gender Identification Code<br />

‘0’ = Unknown;<br />

‘1’ = Male;<br />

‘2’ = Female.<br />

6 Date of Birth 8 34-41 YYYYMMDD Format<br />

7 Record Type 1 42 ‘T’ = TRC record<br />

8 Contract<br />

5 43-47 Plan Contract Number<br />

Number<br />

9 State Code 2 48-49 Beneficiary Residence State Code; otherwise, spaces if not<br />

applicable.<br />

10 County Code 3 50-52 Beneficiary Residence County Code; otherwise, spaces if not<br />

applicable.<br />

11 Disability<br />

Indicator<br />

12 Hospice<br />

Indicator<br />

13 Institutional/NH<br />

C/HCBS<br />

Indicator<br />

14 14. ESRD<br />

Indicator<br />

15 15. Transaction<br />

Reply Code<br />

(TRC)<br />

1 53 ‘1’ = Disabled;<br />

‘0’ = No Disability;<br />

Space = not applicable.<br />

1 54 ‘1’ = Hospice;<br />

‘0’ = No Hospice;<br />

Space = not applicable.<br />

1 55 ‘3’ = HCBS;<br />

‘1’ = Institutional;<br />

‘2’ = NHC;<br />

‘0’ = No Institutional;<br />

Space = not applicable<br />

1 56 ‘1’ = End-Stage Renal Disease;<br />

‘0’ = No End-Stage Renal Disease;<br />

Space = not applicable.<br />

3 57-59 TRC, see TRC list on page I-2 for values<br />

<strong>December</strong> <strong>28</strong>, 2012 F-81 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

16 16. Transaction<br />

Code (TC)<br />

17 17. Entitlement<br />

Type Code<br />

18 18. Effective<br />

Date<br />

19 19. Working<br />

Aged (WA)<br />

Indicator<br />

2 60-61 TC<br />

1 62 Beneficiary Entitlement Type Code:<br />

‘Y’ = Entitled to Part A <strong>and</strong> B,<br />

‘Z’ = Entitled to Part A or B;<br />

Space = not applicable<br />

Space reported with TRCs 121, 194, <strong>and</strong> 223, has no meaning.<br />

8 63-70 YYYYMMDD Format;<br />

Effective date is present for all TRCs.<br />

However, for UI TRCs, field content is TRC dependent:<br />

701 – New enrollment period start date,<br />

702 – Fill-in enrollment period start date,<br />

703 – Start date of cancelled enrollment period,<br />

704 – Start date of enrollment period cancelled for Plan Benefit<br />

Package (PBP) correction,<br />

705 – Start date of enrollment period for corrected PBP,<br />

706 – Start date of enrollment period cancelled for segment<br />

correction,<br />

707 – Start date of enrollment period for corrected segment,<br />

708 – Enrollment period end date assigned to existing opened ended<br />

enrollment,<br />

709 & 710 – New start date resulting from update,<br />

711 & 712 – New end date resulting from update,<br />

713 – “00000000” – End date removed. Original end date is in field<br />

24.X,<br />

091 – Previously reported incorrect death date,<br />

121, 194, <strong>and</strong> 223 – PBP enrollment effective date.<br />

305 – New ZIP Code Start Date<br />

293 – Enrollment End Date; Last day of the month<br />

1 71 ‘1’ = WA;<br />

‘0’ = No WA;<br />

Space = not applicable.<br />

3 72-74 PBP number<br />

20 20. Plan Benefit<br />

Package ID<br />

21 21. Filler 1 75 Spaces<br />

22 22. Transaction 8 76-83 YYYYMMDD Format; Present for all TRCs. For TRCs 121, 194,<br />

Date<br />

<strong>and</strong> 223, the report generation date.<br />

23 23. UI Initiated 1 84 ‘1’ = transaction created through user interface;<br />

Change Flag<br />

‘0’ = transaction from source other than user interface;<br />

24 24. Positions 85<br />

– 96 are<br />

dependent<br />

upon the<br />

TRC value.<br />

There are<br />

spaces for<br />

all codes<br />

except<br />

where<br />

indicated<br />

below.<br />

Space = not applicable.<br />

8 85-92 This field value depends on the TRC that is returned on the reply.<br />

See the TRC-related values below:<br />

<strong>December</strong> <strong>28</strong>, 2012 F-82 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

a. Effective<br />

Date of the<br />

Disenrollme<br />

nt<br />

b. New<br />

Enrollment<br />

Effective<br />

Date<br />

c. Claim<br />

Number<br />

(old)<br />

d. Date of<br />

Death<br />

e. Hospice<br />

Start Date<br />

f. Hospice End<br />

Date<br />

g. ESRD Start<br />

Date<br />

h. ESRD End<br />

Date<br />

i. Institutional/<br />

NHC Start<br />

Date<br />

j. Medicaid<br />

Start Date<br />

k. Medicaid<br />

End Date<br />

l. Part A End<br />

Date<br />

m. WA Start<br />

Date<br />

n. WA End<br />

Date<br />

o. Part A<br />

Reinstate<br />

Date<br />

p. Part B End<br />

Date<br />

q. Part B<br />

Reinstate<br />

Date<br />

r. Old State<br />

<strong>and</strong> County<br />

Codes<br />

s. t. Attempted<br />

Enroll<br />

Effective Date<br />

u. v. PBP<br />

Effective<br />

Date<br />

8 85-92 YYYYMMDD Format; Present only when TRC is one of<br />

the following: 13, 14, 18, 293<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 17<br />

12 85-96 Present only when TRC is one of the following: 22, 25, 86<br />

8 85-92 YYYYMMDD Format; Present only when TRC is one of the<br />

following: 90 (with TC 01), 92<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 71<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 72<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 73<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 74<br />

8 85-92 YYYYMMDD Format; Present only when TRC is one of the<br />

following: 48, 75, 158, 159<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 77<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 78<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 79<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 66<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 67<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 80<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 81<br />

8 85-92 YYYYMMDD Format; Present only when TRC is 82<br />

5 85-89 Beneficiary’s prior state <strong>and</strong> county code; Present only when TRC is<br />

85<br />

8 85-92 The effective date of an enrollment transaction that was submitted<br />

but rejected. Present only when TRC is the following: 35, 36, 45, 56<br />

8 85-92 YYYYMMDD Format. Effective date of a beneficiary’s PBP<br />

change. Present only when TRC is 100.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-83 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

w. x. Correct Part<br />

D Premium<br />

Rate<br />

y. z. Date<br />

Identifying<br />

Information<br />

Changed by<br />

UI User<br />

aa. bb. Modified<br />

Part C<br />

Premium<br />

Amount<br />

cc. dd. Date of<br />

Death<br />

Removed<br />

ee. ff. Dialysis End<br />

Date<br />

gg. hh. Transplant<br />

Failure Date<br />

ii. jj. New ZIP<br />

Code<br />

25 District Office<br />

Code<br />

26 Previous Part D<br />

Contract/PBP<br />

for TrOOP<br />

Transfer.<br />

12 85-96 ZZZZZZZZ9.99 Format; Part D premium amount reported by HPMS<br />

for the Plan. Present only when the TRC is 181.<br />

8 85-92 YYYYMMDD Format;<br />

Field content is dependent on TRC:<br />

702 – Fill-in enrollment period end date,<br />

705 – End date of enrollment period for corrected PBP, blank when<br />

end date not provided by user,<br />

707 – End date of enrollment period for corrected segment, blank<br />

when end date not provided by user,<br />

709 & 710 – Enrollment period start date prior to start date change,<br />

711, 712, & 713 – Enrollment period end date prior to end date<br />

change.<br />

12 85-96 ZZZZZZZZ9.99 Format; Part C premium amount reported by HPMS<br />

for the Plan. Present only when the TRC is 182.<br />

8 85-92 YYYYMMDD Format; previously reported erroneous date of death.<br />

Present only when TRC is 091.<br />

8 85-92 YYYYMMDD Format; present when TRC is 268 <strong>and</strong> the dialysis<br />

period has an end date.<br />

8 85-92 YYYYMMDD Format; present when TRC is 269 <strong>and</strong> the transplant<br />

has an end date.<br />

10 85-94 #####-#### Format; present when TRC is 305<br />

3 97-99 Code of the originating district office; Present only when TC is 53;<br />

otherwise, spaces if not applicable.<br />

8 100-107 CCCCCPPP Format; Present only if previous enrollment exists<br />

within reporting year in Part D Contract. Otherwise, field is spaces.<br />

CCCCC = Contract Number; PPP = PBP Number.<br />

27 Filler 8 108-115 Spaces<br />

<strong>28</strong> Source ID 5 116-120 Transaction Source Identifier<br />

29 Prior Plan<br />

Benefit Package<br />

ID<br />

30 Application<br />

Date<br />

31 UI User<br />

Organization<br />

Designation<br />

32 Out of Area<br />

Flag<br />

33 Segment<br />

Number<br />

3 121-123 Prior PBP Number; present only for TC 71; otherwise, spaces if not<br />

applicable.<br />

8 124-131 The date the plan received the beneficiary’s completed enrollment<br />

(electronic) or the date the beneficiary signed the enrollment<br />

application (paper). Format: YYYYMMDD; otherwise, spaces if not<br />

applicable.<br />

2 132-133 ‘01’ = Plan<br />

‘02’ = Regional Office;<br />

‘03’ = Central Office;<br />

Spaces = not UI transaction<br />

1 134 ‘Y’ = Out of area;<br />

‘N’ = Not out of area;<br />

Space = not applicable<br />

3 135-137 Further definition of PBP by geographic boundaries; otherwise,<br />

spaces when not applicable.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-84 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

34 Part C<br />

Beneficiary<br />

Premium<br />

35 Part D<br />

Beneficiary<br />

Premium<br />

8 138-145 Cost to beneficiary for Part C benefits; otherwise, spaces if not<br />

applicable.<br />

8 146-153 Cost to beneficiary for Part D benefits; otherwise, spaces if not<br />

applicable.<br />

36 Election Type 1 154 ‘A’ = AEP;<br />

‘E’ = IEP;<br />

’I’ = ICEP;<br />

‘O’ = OEP;<br />

‘N’ = OEPNEW;<br />

‘T’ = OEPI;<br />

‘R’ = 5 Star SEP;<br />

‘S’ = Other SEP;<br />

‘U’ = Dual/LIS SEP;<br />

‘V’ = Permanent Change in Residence SEP;<br />

‘W’ = EGHP SEP;<br />

‘X’ = Administrative Action SEP;<br />

‘Y’ = CMS/Case Work SEP;<br />

Space = not applicable.<br />

37 Enrollment<br />

Source<br />

38 Part D Opt-Out<br />

Flag<br />

39 Premium<br />

Withhold<br />

Option/Parts C-<br />

D<br />

(MAs use I, A, N, O, R, S, T, U, V, W, X, <strong>and</strong> Y.<br />

MAPDs use I, A, E, N, O, R, S, T, U, V, W, X, Y.<br />

PDPs use A, E, R, S, U, V, W, X, <strong>and</strong> Y.)<br />

1 155 ‘A’ = Auto enrolled by CMS;<br />

‘B’ = Beneficiary Election;<br />

‘C’ = Facilitated enrollment by CMS;<br />

‘D’ = CMS Annual Rollover;<br />

‘E’ = Plan initiated AE;<br />

‘F’ = Plan initiated FE;<br />

‘G’ = Point-of-sale enrollment;<br />

‘H’ = CMS or Plan reassignment;<br />

‘I’ = Invalid submitted value (transaction is not rejected);<br />

‘J’ = State-submitted Passive Enrollment<br />

‘K’ = CMS-submitted passive Enrollment<br />

‘L’ = Beneficiary Election in Financial Alignment Demonstration<br />

‘M’ = Defaulted value for Financial Alignment Demonstration<br />

Space = not applicable.<br />

1 156 ‘Y’ = Opted out of Part D AE/FE;<br />

‘N’ = Not opted out of Part D AE/FE;<br />

Space = No change to opt-out status<br />

1 157 ‘D’ = Direct self-pay;<br />

‘S’ = Deduct from SSA benefits;<br />

‘R’ = Deduct from RRB benefits;<br />

‘O’ = Deduct from OPM benefits;<br />

‘N’ = No premium applicable;<br />

Option applies to both Part C <strong>and</strong> D Premiums;<br />

Space = not applicable.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-85 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

40 Number of<br />

Uncovered<br />

Months<br />

(NUNCMO)<br />

41 Creditable<br />

Coverage<br />

Flag<br />

42 Employer<br />

Subsidy<br />

Override Flag<br />

43 Processing<br />

Timestamp<br />

44 Filler 20 178-197 Spaces<br />

45 Secondary <strong>Drug</strong><br />

Insurance Flag<br />

46 Secondary Rx<br />

ID<br />

47 Secondary Rx<br />

Group<br />

3 158-160 Total months without drug coverage; otherwise, spaces if not<br />

applicable.<br />

1 161 ‘Y’ = Covered;<br />

‘N’ = Not Covered;<br />

‘R’ = Setting uncovered months to zero due to a new IEP;<br />

‘U’ = Setting uncovered months to the value prior to using R;<br />

Space = not applicable.<br />

1 162 ‘Y’ = Beneficiary is in a Plan receiving an employer subsidy, flag<br />

allows enrollment in a Part D Plan;<br />

Space = no flag submitted by Plan.<br />

15 163-177 Transaction processing time, or, for TRCs 121, 194, <strong>and</strong> 223, the<br />

report generation time.<br />

Format: HH.MM.SS.SSSSSS<br />

1 198 (TC 61) MAPD <strong>and</strong> PDP transactions:<br />

‘Y’ = Beneficiary has secondary drug insurance;<br />

‘N’ = Beneficiary does not have secondary drug insurance available;<br />

Space = No flag submitted by Plan.<br />

(TC 72) MAPD <strong>and</strong> PDP transactions:<br />

‘Y’ = Secondary drug insurance available<br />

‘N’ = No secondary drug insurance available<br />

Space = no change.<br />

Space returned with any other TC has no meaning.<br />

20 199-218 Beneficiary’s secondary insurance Plan’s ID number from input TC<br />

61 or 72; otherwise, spaces for any other TC.<br />

15 219-233 Beneficiary’s secondary insurance Plan’s Group ID number from<br />

input TC 61 or 72; otherwise, spaces for any other TC.<br />

48 EGHP 1 234 TC 61:<br />

‘Y’ = EGHP;<br />

Space = not EGHP.<br />

49 Part D Low-<br />

Income<br />

Premium<br />

Subsidy Level<br />

(Part D LIPS)<br />

TC 74:<br />

‘Y’ = EGHP;<br />

‘N’ = Not EGHP;<br />

Space = no change.<br />

Space reported with any other TC that has no meaning.<br />

3 235-237 Part D LIPS percentage category:<br />

‘000’ = No subsidy,<br />

‘025’ = 25% subsidy level;<br />

‘050’ = 50% subsidy level;<br />

‘075’ = 75% subsidy level;<br />

‘100’ = 100% subsidy level;<br />

Spaces = not applicable.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-86 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

50 Low-Income<br />

Co-Pay<br />

Category<br />

51 Low-Income<br />

Period Effective<br />

Date<br />

52 Part D Late<br />

Enrollment<br />

Penalty (LEP)<br />

Amount<br />

53 Part D LEP<br />

Waived<br />

Amount<br />

54 Part D LEP<br />

Subsidy<br />

Amount<br />

55 Low-Income<br />

Part D Premium<br />

Subsidy<br />

Amount<br />

1 238 Definitions of the co-payment categories:<br />

‘0’ = none, not low-income<br />

‘1’ = (High);<br />

‘2’ = (Low);<br />

‘3’ = (0);<br />

‘4’ = 15%;<br />

‘5’ = Unknown;<br />

Space = not applicable.<br />

8 239-246 Date low income period starts.<br />

Format: YYYYMMDD<br />

Spaces if not applicable.<br />

8 247-254 Calculated Part D LEP, not including adjustments indicated by items<br />

(53) <strong>and</strong> (54).<br />

Format: -9999.99; otherwise, spaces if not applicable.<br />

8 255-262 Amount of Part D LEP waived.<br />

Format: -9999.99; otherwise, spaces if not applicable.<br />

8 263-270 Amount of Part D LEP low-income subsidy.<br />

Format: -9999.99; otherwise, spaces if not applicable.<br />

8 271-278 Amount of Part D low-income premium subsidy as of the enrollment<br />

period start date.<br />

Format: -9999.99; otherwise, spaces if not applicable.<br />

56 Part D Rx BIN 6 279-<strong>28</strong>4 Beneficiary’s Part D Rx BIN taken from the input transaction (TC 61<br />

or 72); otherwise, spaces for any other TC.<br />

57 Part D Rx PCN 10 <strong>28</strong>5-294 Beneficiary’s Part D Rx PCN taken from the input transaction (TC<br />

61 or 72); otherwise, spaces if not provided via a transaction.<br />

58 Part D Rx<br />

Group<br />

15 295-309 Beneficiary’s Part D Rx Group taken from the input transaction (TC<br />

61 or 72); otherwise, spaces for any other TC.<br />

59 Part D Rx ID 20 310-329 Beneficiary’s Part D Rx ID taken from the input transaction (TC 61<br />

or 72); otherwise, spaces for any other TC.<br />

60 Secondary Rx<br />

BIN<br />

6 330-335 Beneficiary’s secondary insurance BIN taken from the input<br />

transaction (TC 61 or 72); otherwise, spaces for any other TC.<br />

61 Secondary Rx<br />

PCN<br />

10 336-345 Beneficiary’s secondary insurance PCN taken from the input<br />

transaction (TC 61 or 72); otherwise, spaces for any other TC.<br />

62 De Minimis<br />

Differential<br />

Amount<br />

63 MSP Status<br />

Flag<br />

64 Low-Income<br />

Period End<br />

Date<br />

8 346-353 Amount by which a Part D de minimis Plan’s beneficiary premium<br />

exceeds the applicable regional low-income premium subsidy<br />

benchmark.<br />

Format: -9999.99; otherwise, spaces if not applicable.<br />

1 354 ‘P’ = <strong>Medicare</strong> primary payer;<br />

‘S’ = <strong>Medicare</strong> secondary payer;<br />

‘N’ = Non-respondent beneficiary;<br />

Space = not applicable.<br />

8 355-362 Date low income period closes. The end date is either the last day of<br />

the PBP enrollment or the last day of the low income period itself,<br />

whichever is earlier. This field is blank for LIS applicants with an<br />

open ended award or when the TRC is not one of the LIS TRCs 121,<br />

194, 223.<br />

FORMAT: YYYYMMDD; otherwise, spaces if not applicable.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-87 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

65 LIS Source<br />

Code<br />

66 Enrollee Type<br />

Flag, PBP Level<br />

67 Application<br />

Date<br />

Indicator<br />

1 363 ‘A’ = Approved SSA applicant;<br />

‘D’ = Deemed eligible by CMS;<br />

Space = not applicable.<br />

1 364 Designation relative to the report generation date (Transaction Date,<br />

field #22)<br />

‘C’ = Current PBP enrollee;<br />

‘P’ = Prospective PBP enrollee;<br />

‘Y’ = Previous PBP enrollee;<br />

Spaces = not applicable.<br />

1 365 Identifies whether the application date associated with a UI<br />

submitted enrollment has a system generated default value:<br />

‘Y’ = Default value for UI enrollment;<br />

Space = Not applicable<br />

15 366-380 TRC’s short-name identifier<br />

68 TRC Short<br />

Name<br />

69 DRC 2 381-382 Disenrollment Reason Code, see DRC list for values<br />

70 MMP Opt-Out<br />

Flag<br />

1 383 “Y” = Opted out of passive enrollment into an MMP<br />

“N” = Not opted out of passive enrollment into MMP<br />

Space = Not applicable<br />

71 Filler 91 384-474 Spaces<br />

72 System<br />

11 475-485 System assigned transaction tracking ID.<br />

Assigned<br />

Transaction<br />

Tracking ID<br />

73 Plan Assigned<br />

Transaction<br />

Tracking ID<br />

15 486-500 Plan submitted batch input transaction tracking ID.<br />

Total Length = 500<br />

<strong>December</strong> <strong>28</strong>, 2012 F-88 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.14.2 Verbatim Plan Submitted Transaction on Daily Transaction Reply Report (DTRR)<br />

Item Field Size Position Description<br />

1 HICN 12 1-12 HICN<br />

2 Surname 12 13-24 Beneficiary Surname<br />

3 First Name 7 25-31 Beneficiary Given Name<br />

4 Middle Initial 1 32 Beneficiary Middle Initial<br />

5 Gender Code 1 33 Beneficiary Gender Identification Code<br />

‘0’ = Unknown;<br />

‘1’ = Male;<br />

‘2’ = Female.<br />

6 Date of Birth 8 34-41 YYYYMMDD Format<br />

7 Record Type 1 42 ‘P’ = Plan submitted transaction text.<br />

8 Contract Number 5 43-47 Plan Contract Number<br />

9 Plan Transaction Text 300 48-347 Copy of plan submitted transaction.<br />

10 Filler 126 348-473 Spaces<br />

11 Transaction Accept/Reject Status Flag 1 474 ‘A’ = System accepted transaction or<br />

‘R’ = System Rejected transaction.<br />

12 System Assigned Transaction Tracking ID 11 475-485 System assigned request tracking ID.<br />

13 Plan Assigned Transaction Tracking ID 15 486-500 Plan submitted batch input transaction<br />

tracking ID.<br />

Total Length = 500<br />

<strong>December</strong> <strong>28</strong>, 2012 F-89 DTRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.15 Monthly Full Enrollment Data File<br />

This file includes all active Plan membership for the date that the file published. This file is<br />

considered a definitive statement of current Plan enrollment. CMS announces the availability of<br />

each month’s file with the proper dataset name <strong>and</strong> file transfer date. To distinguish this file from<br />

other TRRs, the TRC on all records is 999.<br />

Item Field Size Position Description<br />

1 HICN 12 1 – 12 HICN<br />

2 Surname 12 13 – 24 Beneficiary Surname<br />

3 First Name 7 25 – 31 Beneficiary Given Name<br />

4 Middle Initial 1 32 Beneficiary Middle Initial<br />

5 Gender Code 1 33 Beneficiary Gender Identification Code<br />

0 = Unknown<br />

1 = Male<br />

2 = Female<br />

6 Date of Birth 8 34 – 41 YYYYMMDD – Format<br />

7 Medicaid Indicator 1 42 Spaces<br />

8 Contract Number 5 43 – 47 Plan Contract Number<br />

9 State Code 2 48 – 49 Beneficiary State Code<br />

10 County Code 3 50 – 52 Beneficiary County Code<br />

11 Disability Indicator 1 53 Spaces<br />

12 Hospice Indicator 1 54 Spaces<br />

13 Institutional/NHC/HCBS<br />

1 55 Spaces<br />

Indicator<br />

14 ESRD Indicator 1 56 Spaces<br />

15 TRC 3 57 – 59 TRC; Defaulted to ‘999’<br />

16 TC 2 60 – 61 TC; Defaulted to ‘01’ for special reports<br />

17 Entitlement Type Code 1 62 Spaces<br />

18 Effective Date 8 63 – 70 YYYYMMDD – Format<br />

19 WA Indicator 1 71 Spaces<br />

20 Plan Benefit Package (PBP) ID 3 72 – 74 PBP number<br />

21 Filler 1 75 Spaces<br />

22 Transaction Date 8 76 – 83 Set to Current Date (YYYYMMDD )<br />

23 Filler 1 84 Spaces<br />

24 Subsidy End Date 12 85 – 96 End date of LIS Period (Present if Bene is deemed<br />

for the full year, or if the Bene is losing Low Income<br />

status before the end of the current year.)<br />

25 District Office Code 3 97 – 99 Spaces<br />

26 Filler 8 100 – 107 Spaces<br />

27 Filler 8 108 – 115 Spaces<br />

<strong>28</strong> Source ID 5 116 – 120 Spaces<br />

29 Prior Plan Benefit Package ID 3 121 – 123 Spaces<br />

30 Application Date 8 124 – 131 Spaces<br />

31 Filler 2 132 – 133 Spaces<br />

32 Out of Area Flag 1 134 – 134 Spaces<br />

33 Segment Number 3 135 – 137 Default to ‘000’ if blank<br />

<strong>December</strong> <strong>28</strong>, 2012 F-90 Monthly Full Enrollment Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

34 Part C Beneficiary Premium 8 138 – 145 Part C Premium Amount; the amount submitted on<br />

the enrollment record for Part C premium<br />

35 Part D Beneficiary<br />

Premium<br />

8 146 – 153 Part D Premium Amount: the Part D Total Premium<br />

Net of Rebate from the HPMS file.)<br />

36 Election Type 1 154 – 154 Spaces<br />

37 Enrollment Source 1 155 – 155 A = Auto Enrolled by CMS;<br />

B = Beneficiary Election;<br />

C = Facilitated Enrollment by CMS;<br />

D = CMS Annual rollover;<br />

E = Plan initiated auto-enrollment;<br />

F = Plan initiated facilitated-enrollment;<br />

G = Point-of-Sale enrollment;<br />

H= CMS or Plan reassignment;<br />

I = Invalid submitted value (transaction is not<br />

rejected).<br />

38 Part D Opt-Out Flag 1 156 – 156 Spaces<br />

39 Filler 1 157 – 157 Spaces<br />

40 Number of Uncovered Months 3 158 – 160 Spaces<br />

41 Creditable Coverage Flag 1 161 – 161 Spaces<br />

42 Employer Subsidy Override Flag 1 162 – 162 Spaces<br />

43 Rx ID 20 163 – 182 Spaces<br />

44 Rx Group 15 183 – 197 Spaces<br />

45 Secondary <strong>Drug</strong> Insurance Flag 1 198-198 Spaces<br />

46 Secondary Rx ID 20 199 – 218 Spaces<br />

47 Secondary Rx Group 15 219 – 233 Spaces<br />

48 EGHP 1 234 - 234 Spaces<br />

49 Part D LIPS Level 3 235 – 237 Part D LIPS category:<br />

‘000’ = No subsidy (default for blank)<br />

‘025’ = 25% subsidy level,<br />

‘050’ = 50% subsidy level,<br />

‘075’ = 75% subsidy level,<br />

‘100’ = 100% subsidy level<br />

50<br />

Low-Income Co-Pay Category 1 238 – 238 Definitions of the co-payment categories:<br />

‘0’ = none, not low-income (default for blank)<br />

‘1’ = (High)<br />

‘2’ = (Low)<br />

‘3’ = $0 (0)<br />

‘4’ = 15%<br />

‘5’ = unknown<br />

51<br />

Low-Income Co-Pay Effective 8 239 - 246 YYYYMMDD – Format<br />

Date<br />

52 Part D LEP Amount 8 247 - 254 Spaces<br />

53 Part D LEP Waived Amount 8 255 - 262 Spaces<br />

54 Part D LEP Subsidy Amount 8 263 - 270 Spaces<br />

55 Low-Income Part D Premium 8 271- 278 Part D Low-Income Premium Subsidy Amount<br />

Subsidy Amount<br />

Total Length = 278<br />

<strong>December</strong> <strong>28</strong>, 2012 F-91 Monthly Full Enrollment Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.16 LIS/LEP Data File<br />

F.16.1 Header Record<br />

Item Field Size Position Description<br />

1 Record Type 3 1-3<br />

2 MCO Contract Number 5 4-8<br />

3<br />

Payment/Payment<br />

Adjustment Date<br />

6 9-14<br />

4 Data file Date 8 15-22<br />

5 Filler 143 23-165 Spaces<br />

Total Length = 165<br />

F.16.2 Detail Record<br />

H = Header Record<br />

PIC XXX<br />

MCO Contract Number<br />

PIC X(5)<br />

YYYYMM<br />

First 6 digits contain Current Payment Month<br />

(CPM)<br />

PIC 9(6)<br />

YYYYMMDD<br />

Date this data file created<br />

PIC 9(8)<br />

Item Field Name Size Position Description<br />

PD = Prospective Detail Record<br />

“Prospective” means Premium Period<br />

equals Payment Month reflected in Header<br />

Record<br />

1 Record Type 3 1-3<br />

AD = Adjustment Detail Record<br />

“Adjustment” means all Premium Periods<br />

other than Prospective<br />

*** PLAN IDENTIFICATION<br />

2 MCO Contract Number 5 4-8<br />

3 PBP Number 3 9-11<br />

4 Plan Segment Number 3 12-14<br />

*** BENEFICIARY<br />

IDENTIFICATION &<br />

PREMIUM SETTINGS<br />

5 HIC Number 12 15-26<br />

PIC XXX<br />

MCO Contract Number<br />

PIC X(5)<br />

PBP Number<br />

PIC X(3)<br />

Plan Segment Number<br />

PIC X(3)<br />

Member’s HIC #<br />

PIC X(12)<br />

6 Surname 7 27-33 PIC X(7)<br />

7 First Initial 1 34 PIC X<br />

8 Sex 1 35<br />

M = Male, F = Female<br />

PIC X<br />

<strong>December</strong> <strong>28</strong>, 2012 F-92 LIS/LEP Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Name Size Position Description<br />

9 DOB 8 36-43<br />

10 Filler 1 44 Space<br />

11<br />

12<br />

13<br />

14<br />

*** PREMIUM PERIOD<br />

Premium/Adjustment Period Start<br />

Date<br />

Premium/Adjustment Period End<br />

Date<br />

Number of Months in<br />

Premium/Adjustment Period<br />

PD: Net Monthly Part D Basic<br />

Premium<br />

AD: Net Monthly Part D Basic<br />

Premium Amount<br />

6 45-50<br />

6 51-56<br />

2 57-58 PIC 99<br />

8 59-66<br />

15 LIPS Percentage 3 67- 69<br />

16 PPO 1 70<br />

*** ACTIVITY FOR PREMIUM<br />

PERIOD<br />

17 Premium LIS Amount 8 71-78<br />

YYYYMMDD<br />

PIC 9(8)<br />

PD: current processing month.<br />

AD: adjustment period.<br />

YYYYMM<br />

PIC 9(6)<br />

PD: current processing month.<br />

AD: adjustment period.<br />

YYYYMM<br />

PIC 9(6)<br />

Plan’s Part D Basic Rate in effect for this<br />

premium period<br />

Net is Monthly Part D Basic Premium<br />

(minus)<br />

DE MINIMIS DIFFERENTIAL<br />

Note: PD always equals AD for this field<br />

PIC -9999.99<br />

LIPS Percentage<br />

Subsidy percentage in effect for this<br />

premium period<br />

Valid values: 100, 075, 050, 025, Blank<br />

PIC 999<br />

Current view of PPO.<br />

Valid values:<br />

D (direct bill)<br />

S (SSA withhold)<br />

R (RRB withhold)<br />

O (OPM withhold)<br />

N (no premium applicable)<br />

PIC X<br />

PD: Premium LIS Amount – the portion of<br />

the Part D basic premium paid by the<br />

Government on behalf of a lowincome<br />

individual<br />

AD: For adjustments, compute the<br />

adjustment for each month in the<br />

affected payment period if the payment<br />

is already made.<br />

PIC -9999.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-93 LIS/LEP Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Name Size Position Description<br />

18<br />

Net LEP Amount for Direct Billed<br />

Members<br />

8 79-86<br />

19 Net Amount Payable to Plan 8 87-94<br />

20 Filler 71 95-165 Spaces<br />

Total Length = 165<br />

PD: LEP Amount for Direct Billed<br />

Members owed by Beneficiary for<br />

premium period. This amount is net of<br />

any subsidized amounts for eligible LIS<br />

members.<br />

Net LEP Amount for Direct Billed<br />

Members =<br />

LEP Amount (minus) LEP Subsidy Amount<br />

(minus)<br />

Part D Penalty Waived Amount<br />

AD: For adjustments, compute the<br />

adjustment for each month in the<br />

(affected) payment period if the<br />

payment was already made.<br />

PIC -9999.99<br />

PD:<br />

Net Amount Payable to Plan =<br />

Premium LIS Amount (field 16)<br />

(minus)<br />

Net LEP Amount for Direct<br />

Billed Members (field 17)<br />

AD:<br />

For adjustments, compute the adjustment<br />

for each month in the (affected)<br />

payment period if the payment was<br />

already made.<br />

PIC -9999.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-94 LIS/LEP Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.17 Loss of Subsidy Data File<br />

This is a file sent to notify <strong>Plans</strong> about Beneficiaries’ loss of LIS deemed status for the following<br />

calendar year based on CMS’ annual re-determination of deemed status or SSA’s redetermination<br />

of LIS awards. The file is sent to <strong>Plans</strong> twice per year, once in September <strong>and</strong><br />

once in <strong>December</strong>.<br />

The September file is informational only <strong>and</strong> is used to assist <strong>Plans</strong> in reaching out to the<br />

affected population <strong>and</strong> encouraging them to file an application to qualify for the upcoming<br />

calendar year.<br />

The <strong>December</strong> file is for transactions <strong>and</strong> is used by <strong>Plans</strong> to determine who has lost the LIS as<br />

of January 1 st of the coming year. The TRC is 996, which indicates the loss of the LIS. This<br />

means the Beneficiary is not LIS eligible as of January 1 st of the upcoming year.<br />

F.17.1 Loss of Subsidy Data File Detail Record<br />

Item<br />

Field Size Position Description<br />

1 HICN 12 1-12 Health Insurance Claim Number<br />

2 Surname 12 13-24 Beneficiary Surname<br />

3 First Name 7 25-31 Beneficiary Given Name<br />

4 Middle Initial 1 32 Beneficiary Middle Initial<br />

5<br />

Gender Code 1 33<br />

Beneficiary Gender Identification Code<br />

0 = Unknown<br />

1 = Male<br />

2 = Female<br />

6 Date of Birth 8 34-41 YYYYMMDD – Format<br />

7 Filler 1 42 Spaces<br />

8 Contract Number 5 43-47 Plan Contract Number<br />

9 State Code 2 48-49 Beneficiary State Code<br />

10 County Code 3 50-52 Beneficiary County Code<br />

11 Filler 4 53-56 Spaces<br />

12 TRC 3 57-59 TRC ‘996’<br />

13 Transaction Type<br />

Code<br />

2 60-61 Transaction Type Code ‘01’<br />

14 Filler 1 62 Spaces<br />

15<br />

YYYYMMDD – Format is 01/01 of the next year. Start<br />

Effective Date 8 63-70<br />

of Beneficiary’s Loss of LIS status.<br />

16 Filler 1 71 Spaces<br />

17 Plan Benefit<br />

Package ID<br />

3 72-74 PBP number<br />

18 Filler 1 75 Spaces<br />

19 Transaction Date 8 76-83 Set to Current Date (YYYYMMDD), is the run date.<br />

20 Filler 1 84 Spaces<br />

21 Low-Income<br />

End Date of Beneficiary’s LIS Period (YYYYMMDD),<br />

8 85-92<br />

Subsidy End Date<br />

is 12/31 of the current year.<br />

22 Filler 42 93-134 Spaces<br />

23 Segment Number 3 135-137 ‘000’ if no segment in PBP<br />

24 Filler 97 138-234 Spaces<br />

<strong>December</strong> <strong>28</strong>, 2012 F-95 Loss of Subsidy Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Description<br />

25 Part D Low-Income<br />

Premium Subsidy<br />

Level<br />

26 Low-Income Co-<br />

Pay Category<br />

3 235-237<br />

1 238<br />

Part D low-income premium subsidy category:<br />

‘000’ = No subsidy<br />

Co-payment category:<br />

‘0’ = none, not low-income<br />

27 Filler 124 239-362 Spaces<br />

<strong>28</strong><br />

‘A’ = Approved SSA Applicant;<br />

LIS Source Code 1 363<br />

‘D’ = Deemed eligible by CMS<br />

29 Filler 137 364-500 Spaces<br />

Total Length = 500<br />

<strong>December</strong> <strong>28</strong>, 2012 F-96 Loss of Subsidy Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.18 LIS/Part D Premium Data File<br />

Field Size Position Description<br />

1. Claim Number 12 1-12 Beneficiary’s CAN<br />

2. Contract Number 5 13-17 Contract Identification Number<br />

3. PBP Number 3 18-20 Beneficiary’s PBP ID, blank if none<br />

4. Segment Number 3 21-23 Beneficiary’s Segment Identification Number, blank if none<br />

5. Run Date 8 24-31<br />

6. Subsidy Start Date 8 32-39<br />

7. Subsidy End Date 8 40-47<br />

8. Part D Premium<br />

Subsidy Percentage<br />

9. Low-Income Co-<br />

Payment Level ID<br />

10. Beneficiary<br />

Enrollment<br />

Effective Date<br />

11. Beneficiary<br />

Enrollment End<br />

Date<br />

12. Part C Premium<br />

Amount<br />

13. Part D Premium<br />

Amount<br />

14. Part D Late<br />

Enrollment Penalty<br />

Amount<br />

3 48-50<br />

1 51<br />

8 52-59<br />

8 60-67<br />

8 68-75<br />

8 76-83<br />

8 84-91<br />

15. LIS Subsidy Amount 8 92-99<br />

16. LIS Penalty Subsidy<br />

Amount<br />

17. Part D Penalty<br />

Waived Amount<br />

18 Total Premium<br />

Amount<br />

19. De Minimis<br />

Differential Amount<br />

8 100-107<br />

8 108-115<br />

8 116-123<br />

8 124-131<br />

20. Filler 147 132- 278 Filler<br />

Total Length = 278<br />

Data File Generation Date<br />

YYYYMMDD – Format<br />

Beneficiary’s Subsidy Start Date<br />

YYYYMMDD – Format<br />

Beneficiary’s Subsidy End Date<br />

YYYYMMDD – Format<br />

Beneficiary’s LIPS Percent<br />

‘100’ = 100% Premium Subsidy<br />

‘075’ = 75% Premium Subsidy<br />

‘050’ = 50% Premium Subsidy<br />

‘025’ = 25% Premium Subsidy<br />

Co-Payment Category Definitions: ‘1’=High; ‘2’=Low;<br />

‘3’=$0; ‘4’=15%<br />

Beneficiary’s Enrollment effective date,<br />

YYYYMMDD – Format<br />

Beneficiary’s Enrollment End Date<br />

YYYYMMDD – Format Space can remain blank<br />

Beneficiary’s Part C Premium Amount<br />

(----9.99)<br />

Beneficiary’s Part D Premium Amount Net of De Minimis if<br />

Applicable, (----9.99)<br />

Beneficiary’s Part D LEP Amount<br />

(––9.99)<br />

Beneficiary’s LIS Subsidy Amount<br />

(----9.99)<br />

Beneficiary’s LIS Penalty Subsidy Amount,<br />

(----9.99)<br />

Beneficiary’s Part D Penalty Waived Amount,<br />

(----9.99)<br />

Total Calculated Premium for Beneficiary<br />

(----9.99)<br />

Amount by which a Part D De Minimis Plan’s beneficiary<br />

premium exceeds the applicable regional low-income<br />

premium subsidy benchmark.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-97 LIS/Part D Premium Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.19 LIS History Data File (LISHIST)<br />

The Monthly LISHIST provides the most complete picture of LIS eligibility over a period not to<br />

exceed 36 months. This data file includes LIS activity for past, present, <strong>and</strong> future enrollees.<br />

Please note the following limitations:<br />

The LIS History Data File displays those LIS contract history changes during active,<br />

contiguous enrollment over a period of time not to exceed 36 months.<br />

Note: This file was updated to include a Data Activity Flag in field 16 (position 80) of the Detail<br />

Record.<br />

F.19.1 Header Record<br />

Item Field Size Position Format Description<br />

1 Record Type 1 1 CHAR ‘H’ = Header Record<br />

2<br />

MCO Contract<br />

Number<br />

5 2-6 CHAR<br />

3 Data file Date 8 7-14 CHAR<br />

4 Calendar Month 6 15-20 CHAR<br />

5 Filler 145 21-165 CHAR SPACES<br />

Total Length = 165<br />

Contract ID: 9xxxx, Exxxx, Fxxxx, Hxxxx, Rxxxx, or<br />

Sxxxx, where “xxxx” is the contract’s numeric<br />

designation.<br />

Date this data file created<br />

YYYYMMDD – Format<br />

First six digits contain Calendar Month the report<br />

generated;<br />

YYYYMMDD – Format<br />

<strong>December</strong> <strong>28</strong>, 2012 F-98 LIS History Data File (LISHIST)


Plan Communications User Guide Appendices, Version 6.3<br />

F.19.2 Detail Record (Transaction)<br />

Item Field Size Position Position Description<br />

1 Record Type 1 1 CHAR ‘D’ = Detail Record<br />

2<br />

MCO Contract<br />

Number<br />

5 2-6 CHAR<br />

Contract ID: 9xxxx, Exxxx, Fxxxx, Hxxxx, Rxxxx, or<br />

Sxxxx, where “xxxx” is the contract’s numeric<br />

designation.<br />

3 PBP Number 3 7-9 CHAR<br />

PBP Number, blank when Beneficiary premium<br />

profile is unavailable.<br />

4 HIC Number 12 10-21 CHAR Beneficiary’s HIC #<br />

5 Surname 12 22-33 CHAR Beneficiary’s Surname<br />

6 First Name 7 34-40 CHAR Beneficiary’s First Initial<br />

7 Middle Initial 1 41 CHAR Beneficiary’s Middle Initial<br />

8 Sex 1 42 CHAR M = Male, F = Female<br />

9 Date of Birth 8 43-50 CHAR Date of Birth YYYYMMDD – Format<br />

10<br />

11<br />

Low Income<br />

Period Start<br />

Date<br />

Low Income<br />

Period End Date<br />

8 51-58 CHAR<br />

8 59-66 CHAR<br />

12 LIPS Percentage 3 67-69 CHAR<br />

13<br />

Premium LIS<br />

Amount<br />

8 70-77 CHAR<br />

Start date for beneficiary’s Low Income Period<br />

Amount:<br />

YYYYMMDD – Format<br />

End date for beneficiary’s Low Income Period<br />

Amount:<br />

YYYYMMDD – Format<br />

Beneficiary’s LIPS Percentage<br />

‘100’ = 100% Premium subsidy<br />

‘075’ = 75% Premium subsidy<br />

‘050’ = 50% Premium subsidy<br />

‘025’ = 25% Premium subsidy<br />

The portion of the Part D basic premium paid by the<br />

Government on behalf of a low-income individual. A<br />

zero dollar amount here represents several<br />

possibilities:<br />

1. There is no Plan premium <strong>and</strong> therefore no<br />

premium subsidy.<br />

2. Although the Beneficiary is enrolled <strong>and</strong> LIS<br />

eligible, a system error occurred making premium data<br />

unavailable.<br />

Premium LIS Amount is entered in spaces when data<br />

is unavailable.<br />

99999.99 – Format<br />

14<br />

Low Income<br />

Co-pay Level<br />

ID<br />

1 78 CHAR<br />

Co-Payment Category Definitions:<br />

‘1’ = High<br />

‘2’ = Low<br />

‘3’ = $0<br />

‘4’ = 15%<br />

Co-pay level IDs 1 <strong>and</strong> 2 change each year.<br />

In 2007, 1 = $2.15/$5.35 <strong>and</strong> 2 = $1/$3.10.<br />

In 2006 1 = $2/$5 <strong>and</strong> 2 = $1/$3.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-99 LIS History Data File (LISHIST)


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Size Position Position Description<br />

15<br />

16<br />

Beneficiary<br />

Source of<br />

Subsidy Code<br />

LIS Activity<br />

Flag<br />

1 79 CHAR<br />

1 80 CHAR<br />

17 PBP Start Date 8 81-88 CHAR<br />

18<br />

Net Part D<br />

Premium<br />

Amount<br />

8 89-96 CHAR<br />

19 Contract Year 4 97-100 CHAR<br />

20<br />

21<br />

Institutional<br />

Status Indicator<br />

PBP Enrollment<br />

Termination<br />

Date<br />

1 101 CHAR<br />

8 102-109 CHAR<br />

22 Filler 56 110-165 CHAR Spaces<br />

Total Length = 165<br />

Source of beneficiary subsidy.<br />

Valid values are:<br />

A = Determined Eligible for LIS by the Social<br />

Security Administration or a State Medicaid Agency<br />

D = Deemed Eligible for LIS<br />

‘N’ = No change in reported LIS data since last<br />

month’s data file<br />

‘Y’ = One of the following may have changed since<br />

the last month’s data file:<br />

Co-payment level<br />

Low-income premium subsidy level<br />

Low-income period start or end date<br />

Changes occur to low-income information that do not<br />

impact the Plan. The changes are not yet separable<br />

from variations in which the Plan is interested.<br />

Although it is possible that data records are flagged as<br />

representing a change, the data of interest to the Plan<br />

is unaffected.<br />

PBP enrollment effective start date:<br />

YYYYMMDD – Format<br />

The total Part D premium net of any Part A/B rebates<br />

less the Beneficiary’s premium subsidy amount.<br />

Spaces when the premium record is unavailable.<br />

99999.99 – Format<br />

Calendar Year associated with the low income<br />

premium subsidy amount;<br />

YYYY – Format<br />

‘1’ (Institutionalized)<br />

‘2’ (Non Institutionalized)<br />

‘3’ (Home <strong>and</strong> Community- Based Services [HCBS])<br />

‘9’ (Not applicable)<br />

PBP enrollment termination date:<br />

YYYYMMDD – Format<br />

<strong>December</strong> <strong>28</strong>, 2012 F-100 LIS History Data File (LISHIST)


Plan Communications User Guide Appendices, Version 6.3<br />

F.19.3 Trailer Record<br />

Item Field Size Position Format Description<br />

1 Record Type 1 1 CHAR ‘T’ = Trailer Record<br />

2<br />

MCO Contract<br />

Number<br />

5 2-6 CHAR<br />

Contract ID: 9xxxx, Exxxx, Fxxxx, Hxxxx, Rxxxx, or<br />

Sxxxx, where “xxxx” is the contract’s numeric<br />

designation.<br />

3 Totals 8 7-14 CHAR Total number of Detail Records<br />

4 Filler 151 15-165 CHAR Spaces<br />

Total Length = 165<br />

<strong>December</strong> <strong>28</strong>, 2012 F-101 LIS History Data File (LISHIST)


Plan Communications User Guide Appendices, Version 6.3<br />

F.20 NoRx File<br />

This file contains records identifying those enrollees with no current 4Rx information stored in<br />

CMS files. A Detail Record Type containing a value of “NRX” in positions 1 – 3 of the file<br />

layout indicates that this record requests the organization to send CMS 4Rx information for the<br />

Beneficiary.<br />

The NoRx File is in the same format as the 4Rx Notification File <strong>and</strong> contains records<br />

identifying those enrollees who do not currently have 4Rx information stored in CMS. The only<br />

distinction between the two files is that the NoRx file detail record shows blanks, or no<br />

information, in fields such as REC TYPE, DATE OF BIRTH, RX BIN, etc.<br />

The following records are included in this file:<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

F.20.1 Header Record<br />

Note: A “Critical Field” must contain a value. A “Not Critical Field” may contain a value or all<br />

spaces.<br />

Field Size Position Form<br />

at<br />

Valid<br />

Values<br />

File ID Name 8 1-8 X(8) “CMSNRX<br />

0H”<br />

Sending Entity 8 9-16 X(8) “MBD “<br />

(MBD + 5<br />

spaces)<br />

File Creation<br />

Date<br />

8 17-24 X(8) YYYYMM<br />

DD<br />

Description<br />

Critical Field<br />

This field is always set to the value "CMSNRX0H."<br />

This code allows recognition of the record as the<br />

Header Record of a NoRx File.<br />

Critical Field<br />

This field is always set to the value “MBD “. The<br />

value specifically is “MBD” followed by five spaces.<br />

Critical Field<br />

The date on which the NoRx file was created by<br />

CMS. This value is formulated as YYYYMMDD.<br />

File Control<br />

Number<br />

9 25-33 X(9) Spaces No meaningful values are supplied in this field. This<br />

field is set to SPACES <strong>and</strong> is not referenced for<br />

meaningful information.<br />

Filler 717 34-750 X(71<br />

7<br />

)<br />

Total Length = 750<br />

Spaces<br />

No meaningful values are supplied in this field. This<br />

field is set to SPACES <strong>and</strong> is not referenced for<br />

meaningful information.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-102 NoRx File


Plan Communications User Guide Appendices, Version 6.3<br />

F.20.2 Detail Record<br />

Note: A “Critical Field” must contain a value. A “Not Critical Field” may contain a value or all<br />

spaces.<br />

Field Size Position Format Valid Values Description<br />

Record Type 3 1-3 X(3) “NRX” Critical Field<br />

This field is set to the value "NRX,"<br />

indicating that this detail record is a NoRx<br />

record. This code allows recognition of the<br />

detail record as a No Rx record from CMS.<br />

Record Type<br />

from Original<br />

Detail<br />

HICN or RRB<br />

Number<br />

5 4-8 X(5) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

12 9-20 X(9) HICN or RRB Critical Field<br />

This field contains either the HICN or the<br />

RRB Number of the Beneficiary without<br />

4Rx data.<br />

SSN 9 21-29 X(9) SSN from CMS Not a Critical Field<br />

This field may contain the SSN of the<br />

Beneficiary that does not have 4Rx data.<br />

Beneficiary Date<br />

of Birth from<br />

Original Detail<br />

Beneficiary<br />

Gender Code<br />

from Original<br />

Detail<br />

Rx BIN from<br />

Original Detail<br />

Rx PCN from<br />

Original Detail<br />

Rx ID Number<br />

from Original<br />

Detail<br />

Rx Group from<br />

Original Detail<br />

8 30-37 X(8) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

1 38 X(1) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

6 39-44 X(6) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

10 45-54 X(10) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

20 55-74 X(20) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

15 75-89 X(15) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

Contract Number 5 90- 94 X(5) Contract Number<br />

from CMS<br />

PBP Number 3 95- 97 X(3) PBP Number from<br />

CMS<br />

PBP Enrollment<br />

Effective Date<br />

from Original<br />

Detail<br />

Critical Field<br />

This field contains the Contract Number of<br />

the beneficiary that does not have 4Rx data.<br />

Critical Field<br />

This field contains the beneficiary PBP<br />

number but does not have 4Rx data.<br />

8 98-105 X(8) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-103 NoRx File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Record Sequence<br />

Number from<br />

Original Detail<br />

7 106-112 X(7) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

Processed Flags 3 113-115 X(3) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

Error Return<br />

Codes<br />

Sending Entity<br />

from Original<br />

File<br />

File Control<br />

Number from<br />

Original File<br />

File Creation<br />

Date<br />

36 116-151 X(36) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

8 152-159 X(8) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

9 160-168 X(9) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information.<br />

8 169-176 X(8) YYYYMMDD Critical Field<br />

This field contains the date the NoRx record<br />

was created.<br />

Filler 574 177-750 X(574) Spaces No meaningful values are supplied in this<br />

field. This field will be set to SPACES <strong>and</strong><br />

should not be referenced for meaningful<br />

information.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-104 NoRx File


Plan Communications User Guide Appendices, Version 6.3<br />

F.20.3 Trailer Record<br />

Note: A “Critical Field” must contain a value. A “Not Critical Field” may contain a value or all<br />

spaces.<br />

Field Size Position Format Valid Values Description<br />

File ID<br />

Name<br />

Sending<br />

Entity<br />

File<br />

Creation<br />

Date<br />

File<br />

Control<br />

Number<br />

File<br />

Record<br />

Count<br />

8 1-8 X(8) “CMSNRX0T” Critical Field<br />

This field is always set to the value "CMSNRX0T.”<br />

This code allows recognition of the record as the<br />

Trailer Record of a NoRx File.<br />

8 9-16 X(8) “MBD “ Critical Field<br />

(MBD + 5 This field is always set to the value “MBD “. The<br />

spaces) value specifically is “MBD” followed by five spaces.<br />

8 17-24 X(8) YYYYMMDD Critical Field<br />

The date that CMS created the NoRx file. This value<br />

is formulated as YYYYMMDD.<br />

9 25-33 X(9) Spaces No meaningful values are supplied in this field. This<br />

field is set to SPACES <strong>and</strong> is not referenced for<br />

meaningful information.<br />

7 34-40 9(7) Numeric value<br />

greater than<br />

Zero.<br />

Critical Field<br />

The total number of NoRx records on this file. This<br />

value is right-justified in the field with leading zeros.<br />

Filler 710 41-750 X(710) Spaces No meaningful values are supplied in this field. This<br />

field is set to SPACES <strong>and</strong> is not referenced for<br />

meaningful information.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-105 NoRx File


Plan Communications User Guide Appendices, Version 6.3<br />

F.21 Batch Eligibility Query (BEQ) Request File<br />

The BEQ Request File includes transactions submitted by <strong>Plans</strong> to request eligibility information<br />

for prospective Plan enrollees. The file is used to conduct initial eligibility checks against CMS<br />

MBD system to verify member is Part A / B eligible.<br />

This file includes the following records:<br />

<br />

<br />

<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

F.21.1 Header Record<br />

Field Size Position Format Valid Values Description<br />

File ID<br />

Name<br />

Sending<br />

Entity:<br />

CMS<br />

File<br />

Creatio<br />

n Date<br />

File<br />

Control<br />

Number<br />

8 1- 8 X(8) “MMABEQRH” Critical Field: This field is always set to the value<br />

"MMABEQRH.” This code identifies the file as a<br />

BEQ Request File <strong>and</strong> this record as the Header<br />

Record of the file.<br />

8 9-16 X(8) Sending<br />

Organization (left<br />

justified space<br />

filled)<br />

Acceptable<br />

Values:<br />

5-position<br />

Contract. (3<br />

Spaces are for<br />

Future use)<br />

Critical Field: This field provides CMS with the<br />

identification of the entity that is sending the BEQ<br />

Request File. The value for this field is provided to<br />

CMS <strong>and</strong> used in connection with CMS electronic<br />

routing <strong>and</strong> mailbox functions. The value in this field<br />

should agree with the corresponding value in the<br />

Trailer Record.<br />

The Sending Entity may participate in Part D.<br />

8 17-24 X(8) CCYYYYMMDD Critical Field: The date that the Sending Entity created<br />

the BEQ Request File. This value’s format is<br />

YYYYMMDD. For example, January 3 2010 is the<br />

value 20100103. This value should agree with the<br />

corresponding value in the Trailer Record. CMS<br />

returns this information to the Sending Entity on all<br />

Transactions (Detail Records) of a BEQ Response<br />

File.<br />

9 25-33 X(9) Assigned by<br />

Sending Entity<br />

Critical Field<br />

The specific Control Number assigned by the Sending<br />

Entity to the BEQ Request File. CMS returns this<br />

information to the Sending Entity on all Transactions<br />

(Detail Records) of a BEQ Response File. This value<br />

should agree with the corresponding value in the<br />

Trailer Record.<br />

Filler 717 34-750 X(717) Spaces No meaningful values are supplied in this field. This<br />

field is set to SPACES <strong>and</strong> is not referenced for<br />

meaningful information.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-106 BEQ Request File


F.21.2 Detail Record (Transaction)<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Record<br />

Type<br />

HICN/RRB<br />

Number<br />

5 1-5 X(5) “DTL01” = BEQ<br />

Transaction<br />

Note: The value<br />

above is DTLzero-one.<br />

12 6-17 X(12) HICN<br />

Or<br />

RRB<br />

Filler 9 18-26 X(9) Spaces<br />

Critical Field<br />

This field is set to the value "DTL01," which<br />

indicates that this detail record is a BEQ<br />

Transaction. This code identifies the record as a<br />

detail record for processing specifically for BEQ<br />

Service.<br />

Critical Field<br />

This field provides either the HICN or the RRB<br />

Number for identification of the individual. The<br />

Plan should provide either the HICN or the RRB<br />

Number, whichever the Plan has available <strong>and</strong><br />

active for the individual. The value is left justified<br />

in the field <strong>and</strong> does not include dashes, decimals,<br />

or commas.<br />

DOB 8 27-34 X(8) CCYYYYMMDD Critical Field<br />

The date of the individual’s birth; value format is<br />

YYYYMMDD. The value should not include<br />

dashes, decimals, or commas. The value should<br />

include only numbers.<br />

Gender<br />

Code<br />

Detail<br />

Record<br />

Sequence<br />

Number<br />

1 35 X(1) 0 (Zero) =<br />

Unknown;<br />

1 = Male;<br />

2 = Female<br />

7 36-42 9(7) Seven-byte<br />

number unique<br />

within the BEQ<br />

Request File<br />

Not Critical Field<br />

The gender of the individual. The acceptable values<br />

include<br />

0 (Zero) = Unknown, 1 = Male, 2 = Female.<br />

Critical Field<br />

A unique number assigned by the Sending Entity to<br />

the Transaction (Detail Record). This number<br />

should uniquely identify the Transactions (Detail<br />

Record) within the BEQ Request File.<br />

Filler 708 43-750 X(708) Spaces No meaningful values are supplied in this field.<br />

This field is set to SPACES <strong>and</strong> is not referenced<br />

for or used to store meaningful information, unless<br />

specifically documented otherwise.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-107 BEQ Request File


F.21.3 Trailer Record<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

File ID<br />

Name<br />

Sending<br />

Entity<br />

(CMS)<br />

8 1-8 X(8) “MMABEQRT” Critical Field<br />

This field is always set to the value "MMABEQRT.”<br />

This code identifies the record as the Trailer Record of<br />

a BEQ Request File.<br />

8 9-16 X(8) Sending<br />

Organization (left<br />

justified space<br />

filled)<br />

Acceptable<br />

Values:<br />

5-position<br />

Contract Identifier<br />

+ 3 Spaces<br />

(3 Spaces for<br />

Future use)<br />

Critical Field<br />

This field provides CMS with the identification of the<br />

entity that is sending the BEQ Request File. The value<br />

for this field is provided to CMS <strong>and</strong> used in<br />

connection with CMS electronic routing <strong>and</strong> mailbox<br />

functions. The value in this field should agree with the<br />

corresponding value in the Header Record.<br />

The Sending Entity may participate in Part D.<br />

File<br />

Creatio<br />

n Date<br />

File<br />

Control<br />

Number<br />

Record<br />

Count<br />

8 17-24 X(8) CCYYYYMMDD Critical Field<br />

The date when the Sending Entity created the BEQ<br />

Request File. This value’s format is YYYYMMDD.<br />

For example, January 3, 2010 is the value 20100103.<br />

This value should agree with the corresponding value<br />

in the Header Record. CMS will pass this information<br />

back to the Sending Entity on all Transactions (Detail<br />

Records) of a BEQ Response File.<br />

9 25-33 X(9) Assigned by<br />

Sending Entity<br />

7 34-40 9(7) Numeric value<br />

greater than Zero.<br />

Critical Field<br />

The specific Control Number assigned by the Sending<br />

Entity to the BEQ Request File. CMS will return this<br />

information to the Sending Entity on all Transactions<br />

(Detail Records) of a BEQ Response File. This value<br />

should agree with the corresponding value in the<br />

Header Record.<br />

Critical Field<br />

The total number of Transactions (Detail Records)<br />

supplied on the BEQ Request File. This value is rightjustified<br />

in the field, with leading zeros. This value<br />

should not include non-numeric characters, such as<br />

commas, spaces, dashes, decimals.<br />

Filler 710 41-750 X(710) Spaces No meaningful values are supplied in this field. This<br />

field is set to SPACES <strong>and</strong> is not referenced for<br />

meaningful information nor used to store meaningful<br />

information, unless specifically documented otherwise.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-108 BEQ Request File


Plan Communications User Guide Appendices, Version 6.3<br />

F.22 BEQ Response File<br />

The BEQ Response File contains records produced from processing the transactions of accepted<br />

BEQ Request files. Detail records for all submitted records that are successfully processed<br />

contain Processed Flag = Y. Detail records for all submitted records that are not successfully<br />

processed contain Processed Flag = N.<br />

CMS sends BEQ Response Files to <strong>Plans</strong> in the following format. The BEQ Response Files are<br />

flat files created as a result of processing the Transactions, i.e., Detail Records, of Accepted<br />

BEQ Request Files.<br />

The following records are included in this file:<br />

<br />

<br />

<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

F.22.1 Header Record<br />

Field Size Position Format Valid Values Field Definition<br />

File ID<br />

Name<br />

Sending<br />

Entity<br />

(MBD)<br />

File<br />

Creation<br />

Date<br />

File<br />

Control<br />

Number<br />

8 1-8 X(8) “CMSBEQRH” This field is always set to the value "CMSBEQRH.” This<br />

code identifies the record as the Header Record of a BEQ<br />

Response File.<br />

8 9-16 X(8) “MBD ”<br />

(MBD + 5<br />

Spaces)<br />

This field is always set to the value "MBD .” The value<br />

specifically is MBD + 5 following Spaces. This value<br />

agrees with the corresponding value in the Trailer Record.<br />

8 17-24 X(8) CCYYMMDD The date that CMS created the BEQ Response File. This<br />

value is in the format of CCYYMMDD. For example,<br />

January 3, 2010 is the value 20100103. This value agrees<br />

with the corresponding value in the Trailer Record.<br />

9 25-33 X(9) Assigned by<br />

Sending Entity<br />

(MBD)<br />

The specific Control Number assigned by CMS to the<br />

BEQ Response File. CMS utilizes this value to track the<br />

BEQ Response File through CMS processing <strong>and</strong> archive.<br />

This value agrees with the corresponding value in the<br />

Trailer Record.<br />

Filler 717 34-750 X(717) Spaces No meaningful values are supplied in this field. This field<br />

is set to SPACES <strong>and</strong> is not referenced for or used to store<br />

meaningful information, unless specifically documented<br />

otherwise.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-109 BEQ Response File


F.22.2 Detail Record (Transaction)<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Record Type 3 1-3 X(3) "DTL" This field is set to the value "DTL,"<br />

indicating that this is a detail record.<br />

Original Detail<br />

Record<br />

42 4-45 X(42) The first 42<br />

positions of the<br />

original Transaction<br />

or Detail Record as<br />

supplied by the<br />

Sending Entity.<br />

Processed Flag 1 46 X(1) "Y" = Detail record<br />

accepted for<br />

processing.<br />

"N" = Detail record<br />

not accepted for<br />

processing.<br />

Beneficiary<br />

Match Flag<br />

<strong>Medicare</strong> Part A<br />

Entitlement Start<br />

Date<br />

<strong>Medicare</strong> Part A<br />

Entitlement End<br />

Date<br />

1 47 X(1) "Y" = Beneficiary<br />

matched (located)<br />

successfully.<br />

"N" = Beneficiary<br />

not matched<br />

(located)<br />

successfully.<br />

" " (SPACE) =<br />

Beneficiary Match<br />

not attempted due to<br />

an Invalid condition<br />

in the Transaction<br />

8 48-55 X(8) CCYYMMDD<br />

Spaces = Not<br />

currently enrolled or<br />

Data Not Found.<br />

8 56-63 X(8) CCYYMMDD<br />

Spaces = Not<br />

currently enrolled or<br />

Data Not Found.<br />

This field provides the meaningfully<br />

populated area of the BEQ Request File<br />

Transaction provided by the Sending Entity.<br />

The breakdown includes:<br />

Record Type X95) position 4 … 8<br />

Bene. HICN / RRB # X(12) position 9 … 20<br />

Filler position 21 … 29<br />

Beneficiary DOB X(8) position 30 … 37<br />

Beneficiary Gender Code X(1) position 38<br />

Detail Record Sequence # 9(7) pos 39 … 45<br />

A flag that indicates if the Transaction<br />

(Detail Record) was accepted for processing.<br />

A Transaction is accepted for processing if<br />

all critical fields contain valid values.<br />

A flag that indicates whether or not the<br />

Beneficiary in the Transaction successfully<br />

matched to a Beneficiary on the CMS MBD.<br />

The Entitlement Start Date of the<br />

beneficiary's most recent or active <strong>Medicare</strong><br />

Part A entitlement period.<br />

The Entitlement End Date of the<br />

beneficiary's most recent or active <strong>Medicare</strong><br />

Part A entitlement period.<br />

<strong>Medicare</strong> Part B<br />

Entitlement Start<br />

Date<br />

<strong>Medicare</strong> Part B<br />

Entitlement End<br />

Date<br />

Medicaid<br />

Indicator<br />

8 64-71 X(8) CCYYMMDD<br />

Spaces = Not<br />

currently enrolled or<br />

Data Not Found.<br />

8 72-79 X(8) CCYYMMDD<br />

Spaces = Not<br />

currently enrolled or<br />

Data Not Found.<br />

1 80 X(1) "0" = Beneficiary<br />

with no current or<br />

active Medicaid<br />

The Entitlement Start Date of the<br />

beneficiary's most recent or active <strong>Medicare</strong><br />

Part B entitlement period.<br />

The Entitlement End Date of the<br />

beneficiary's most recent or active <strong>Medicare</strong><br />

Part B entitlement period.<br />

An indicator of the presence of current<br />

Medicaid coverage for the beneficiary. The<br />

value for this field is based upon the<br />

<strong>December</strong> <strong>28</strong>, 2012 F-110 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Part D<br />

Enrollment<br />

Effective Date<br />

/Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 1)<br />

Part D<br />

Disenrollment<br />

Date/ Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 1)<br />

Part D<br />

Enrollment<br />

Effective Date/<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 2)<br />

Part D<br />

Disenrollment<br />

Date/ Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 2)<br />

Part D<br />

Enrollment<br />

Effective Date/<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 3)<br />

Part D<br />

Disenrollment<br />

Date/ Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 3)<br />

Part D<br />

Enrollment<br />

Effective Date/<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 4)<br />

Part D<br />

Disenrollment<br />

Date / Employer<br />

coverage;<br />

"1" = Beneficiary<br />

has current or active<br />

Medicaid coverage.<br />

8 81-88 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

coverage period for<br />

this occurrence or<br />

Data Not Found.<br />

8 89-96 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 97-104 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 105-112 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 113-120 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 121-1<strong>28</strong> X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 129-136 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 137-144 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

presence of Medicaid reported for the<br />

beneficiary by states in the previous calendar<br />

month via the MMA State Files.<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary;(most recent or presently<br />

active.<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary;(most<br />

recent or presently active.<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary; second most recent.<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary; second<br />

most recent.<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary; third most recent.<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary; third<br />

most recent.<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary; fourth most recent.<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary (fourth<br />

<strong>December</strong> <strong>28</strong>, 2012 F-111 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Subsidy End<br />

Date<br />

(Occurrence 4)<br />

Part D<br />

Enrollment<br />

Effective Date/<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 5)<br />

Part D<br />

Disenrollment<br />

Date / Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 5)<br />

Part D<br />

Enrollment<br />

Effective Date /<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 6)<br />

Part D<br />

Disenrollment<br />

Date / Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 6)<br />

Part D<br />

Enrollment<br />

Effective Date/<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 7)<br />

Part D<br />

Disenrollment<br />

Date / Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 7)<br />

Part D<br />

Enrollment<br />

Effective Date/<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 8)<br />

Part D<br />

Disenrollment<br />

Date / Employer<br />

Subsidy End<br />

this occurrence or<br />

Data Not Found.<br />

8 145-152 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 153-160 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 161-168 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 169-176 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 177-184 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 185-192 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 193-200 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 201-208 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

most recent).<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary (fifth most recent).<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary (fifth<br />

most recent).<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary (sixth most recent).<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary (sixth<br />

most recent).<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary (seventh most recent)<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary<br />

(seventh most recent)<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary (eighth most recent).<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary (eighth<br />

most recent).<br />

<strong>December</strong> <strong>28</strong>, 2012 F-112 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Date<br />

(Occurrence 8)<br />

Part D<br />

Enrollment<br />

Effective Date/<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 9)<br />

Part D<br />

Disenrollment<br />

Date / Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 9)<br />

Part D<br />

Enrollment<br />

Effective Date /<br />

Employer<br />

Subsidy Start<br />

Date<br />

(Occurrence 10)<br />

Part D<br />

Disenrollment<br />

Date / Employer<br />

Subsidy End<br />

Date<br />

(Occurrence 10)<br />

Data Not Found.<br />

8 209-216 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 217-224 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 225-232 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

8 233-240 X(8) CCYYMMDD<br />

Spaces = No <strong>Drug</strong><br />

Coverage Period for<br />

this occurrence or<br />

Data Not Found.<br />

Sending Entity 8 241-248 X(8) Sending Part D<br />

Organization (left<br />

justified space<br />

filled)<br />

Acceptable Values:<br />

5-position Contract<br />

Identifier + 3<br />

Spaces. 3 Spaces for<br />

Future Use.<br />

File Control<br />

Number<br />

File Creation<br />

Date<br />

Part D Eligibility<br />

Start Date<br />

Deemed / LIS<br />

Effective Date<br />

(occurrence 1)<br />

9 249-257 X(9) Assigned by<br />

Sending Entity<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary (ninth most recent).<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary (ninth<br />

most recent)<br />

Effective start date of the Part D Plan or the<br />

Start Date of the Employer Subsidy coverage<br />

for the beneficiary (tenth most recent).<br />

Effective disenrollment date of the Part D<br />

Plan or the End Date of the Employer<br />

Subsidy coverage for the beneficiary (tenth<br />

most recent).<br />

The Sending Entity provided on the Header<br />

Record of the BEQ Request File in which<br />

the Transaction (Detail Record) was found.<br />

The Sending Entity may participate in Part<br />

D.<br />

The File Control Number provided by the<br />

Sending Entity on the Header record of the<br />

BEQ Request File in which the Transaction<br />

(Detail Record) was found.<br />

8 258-265 X(8) CCYYMMDD The File Creation Date provided on the<br />

Header Record of the BEQ Request File in<br />

which the Transaction (Detail Record) was<br />

found.<br />

8 266-273 X(8) CCYYMMDD This field identifies the date the beneficiary<br />

became eligible for Part D Benefits.<br />

8 274-<strong>28</strong>1 X(8) CCYYMMDD Effective start date of the Deeming period or<br />

LIS. This is the first day of the month in<br />

which the Deeming was made or the start<br />

date of the LIS (most recent or presently<br />

active).<br />

<strong>December</strong> <strong>28</strong>, 2012 F-113 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Deemed / LIS<br />

End Date<br />

(Occurrence 1)<br />

Co-payment<br />

Level Identifier<br />

(Occurrence 1)<br />

8 <strong>28</strong>2-<strong>28</strong>9 X(8) CCYYMMDD The end date of the Deemed period or LIS<br />

(most recent or presently active).<br />

1 290 X(1) Deemed: This field indicates the Beneficiary copayment<br />

level.<br />

Part D Premium<br />

Subsidy Percent<br />

(Occurrence 1)<br />

Deemed/Low<br />

Income Subsidy<br />

Effective Date<br />

(Occurrence 2)<br />

Deemed/ Low<br />

Income Subsidy<br />

End Date<br />

(Occurrence2)<br />

Co-payment<br />

Level Identifier<br />

(Occurrence 2)<br />

Part D Premium<br />

Subsidy Percent<br />

(Occurrence 2)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 1<br />

for date fields<br />

beginning in<br />

position 81)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 2<br />

for date fields<br />

beginning in<br />

position 97)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 3<br />

for date fields<br />

beginning in<br />

position 113)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 4<br />

for date fields<br />

beginning in<br />

position 129)<br />

RDS/Part D<br />

Indicator<br />

3 291-293 X(3)<br />

‘100’, ‘075’, ‘050’,<br />

‘025’ or ‘000’<br />

If beneficiary is Deemed, subsidy is 100<br />

percent. If beneficiary is LIS, this field<br />

identifies the portion of Part D Premium<br />

subsidized.<br />

8 294-301 X(8) CCYYMMDD Effective start date of the Deeming period or<br />

LIS. This is the first day of the month in<br />

which the Deeming was made or the start<br />

date of the LIS (second most recent).<br />

8 302-309 X(8) CCYYMMDD The end date of the Deemed period or LIS<br />

(second most recent).<br />

1 310 X(1) Deemed: This field indicates the Beneficiary’s copayment<br />

level.<br />

3 311-313 X(3) ‘100’, ‘075’, ‘050’,<br />

‘025’ or ‘000’<br />

1 314 X(1) R = RDS<br />

D = Part D<br />

1 315 X(1) R = RDS<br />

D = Part D<br />

1 316 X(1) R = RDS<br />

D = Part D<br />

1 317 X(1) R = RDS<br />

D = Part D<br />

1 318 X(1) R = RDS<br />

D = Part D<br />

If beneficiary is Deemed, subsidy is 100<br />

percent. If beneficiary is LIS, this field<br />

identifies the portion of Part D Premium<br />

subsidized.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-114 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

(Occurrence 5<br />

for date fields<br />

beginning in<br />

position 145)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 6<br />

for date fields<br />

beginning in<br />

position 161)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 7<br />

for date fields<br />

beginning in<br />

position 177)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 8<br />

for date fields<br />

beginning in<br />

position 193)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 9<br />

for date fields<br />

beginning in<br />

position 209)<br />

RDS/Part D<br />

Indicator<br />

(Occurrence 10<br />

for date fields<br />

beginning in<br />

position 225)<br />

Start Date<br />

(Occurrence 1)<br />

Number of<br />

Uncovered<br />

Months<br />

(NUNCMO)<br />

(Occurrence 1)<br />

NUNCMO<br />

Indicator<br />

(Occurrence 1)<br />

NUNCMO<br />

(Occurrence 1)<br />

Start Date<br />

(Occurrence 2)<br />

NUNCMO<br />

(Occurrence 2)<br />

NUNCMO<br />

Status Indicator<br />

1 319 X(1) R = RDS<br />

D = Part D<br />

1 320 X(1) R = RDS<br />

D = Part D<br />

1 321 X(1) R = RDS<br />

D = Part D<br />

1 322 X(1) R = RDS<br />

D = Part D<br />

1 323 X(1) R = RDS<br />

D = Part D<br />

8 324-331 X(8) CCYYMMDD<br />

3 332-334 9(3) Right justified with leading zeros.<br />

1 335 X(1) Right justified with leading zeros.<br />

3 336-338 9(3) Right justified with leading zeros.<br />

8 339-346 X(8) CCYYMMDD<br />

3 347-349 9(3) Right justified with leading zeros.<br />

1 350 X(1) Right justified with leading zeros.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-115 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

(Occurrence 2)<br />

NUNCMO<br />

(Occurrence 2)<br />

Start Date<br />

(Occurrence 3)<br />

NUNCMO<br />

(Occurrence 3)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 3)<br />

NUNCMO<br />

(Occurrence 3)<br />

Start Date<br />

(Occurrence 4)<br />

NUNCMO<br />

(Occurrence 4)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 4)<br />

NUNCMO<br />

(Occurrence 4)<br />

Start Date<br />

(Occurrence 5)<br />

NUNCMO<br />

(Occurrence 5)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 5)<br />

NUNCMO<br />

(Occurrence 5)<br />

Start Date<br />

(Occurrence 6)<br />

NUNCMO<br />

(Occurrence 6)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 6)<br />

NUNCMO<br />

(Occurrence 6)<br />

Start Date<br />

(Occurrence 7)<br />

NUNCMO<br />

(Occurrence 7)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 7)<br />

NUNCMO<br />

(Occurrence 7)<br />

3 351-353 9(3) Right justified with leading zeros.<br />

8 354-361 X(8) CCYYMMDD<br />

3 362-364 9(3) Right justified with leading zeros.<br />

1 365 X(1) Right justified with leading zeros.<br />

3 366-368 9(3) Right justified with leading zeros.<br />

8 369-376 X(8) CCYYMMDD<br />

3 377-379 9(3) Right justified with leading zeros.<br />

1 380 X(1) Right justified with leading zeros.<br />

3 381-383 9(3) Right justified with leading zeros.<br />

8 384-391 X(8) CCYYMMDD<br />

3 392-394 9(3) Right justified with leading zeros.<br />

1 395 X(1) Right justified with leading zeros.<br />

3 396-398 9(3) Right justified with leading zeros.<br />

8 399-406 X(8) CCYYMMDD<br />

3 407-409 9(3) Right justified with leading zeros.<br />

1 410 X(1) Right justified with leading zeros.<br />

3 411-413 9(3) Right justified with leading zeros.<br />

8 414-421 X(8) CCYYMMDD<br />

3 422-424 9(3) Right justified with leading zeros.<br />

1 425 X(1) Right justified with leading zeros.<br />

3 426-4<strong>28</strong> 9(3) Right justified with leading zeros.<br />

Start Date 8 429-436 X(8) CCYYMMDD<br />

<strong>December</strong> <strong>28</strong>, 2012 F-116 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

(Occurrence 8)<br />

NUNCMO<br />

(Occurrence 8)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 8)<br />

NUNCMO<br />

(Occurrence 8)<br />

Start Date<br />

Occurrence 9)<br />

NUNCMO<br />

(Occurrence 9)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 9)<br />

NUNCMO<br />

(Occurrence 9)<br />

Start Date<br />

(Occurrence 10)<br />

NUNCMO<br />

(Occurrence 10)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 10)<br />

NUNCMO<br />

(Occurrence 10)<br />

Start Date<br />

(Occurrence 11)<br />

NUNCMO<br />

(Occurrence 11)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 11)<br />

NUNCMO<br />

(Occurrence 11)<br />

Start Date<br />

(Occurrence 12)<br />

NUNCMO<br />

(Occurrence 12)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 12)<br />

NUNCMO<br />

(Occurrence 12)<br />

Start Date<br />

(Occurrence 13)<br />

NUNCMO<br />

(Occurrence 13)<br />

3 437-439 9(3) Right justified with leading zeros.<br />

1 440 X(1) Right justified with leading zeros.<br />

3 441-443 9(3) Right justified with leading zeros.<br />

8 444-451 X(8) CCYYMMDD<br />

3 452-454 9(3) Right justified with leading zeros.<br />

1 455 X(1) Right justified with leading zeros.<br />

3 456-458 9(3) Right justified with leading zeros.<br />

8 459-466 X(8) CCYYMMDD<br />

3 467-469 9(3) Right justified with leading zeros.<br />

1 470 X(1) Right justified with leading zeros.<br />

3 471-473 9(3) Right justified with leading zeros.<br />

8 474-481 X(8) CCYYMMDD<br />

3 482-484 9(3) Right justified with leading zeros.<br />

1 485 X(1) Right justified with leading zeros.<br />

3 486-488 9(3) Right justified with leading zeros.<br />

8 489-496 X(8) CCYYMMDD<br />

3 497-499 9(3) Right justified with leading zeros.<br />

1 500 X(1) Right justified with leading zeros.<br />

3 501-503 9(3) Right justified with leading zeros.<br />

8 504-511 X(8) CCYYMMDD<br />

3 512-514 9(3) Right justified with leading zeros.<br />

NUNCMO 1 515 X(1) Right justified with leading zeros.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-117 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

Status Indicator<br />

(Occurrence 13)<br />

NUNCMO<br />

(Occurrence 13)<br />

Start Date<br />

(Occurrence 14)<br />

NUNCMO<br />

(Occurrence 14)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 14)<br />

NUNCMO<br />

(Occurrence 14)<br />

Start Date<br />

(Occurrence 15)<br />

NUNCMO<br />

(Occurrence 15)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 15)<br />

NUNCMO<br />

(Occurrence 15)<br />

Start Date<br />

(Occurrence 16)<br />

NUNCMO<br />

(Occurrence 16)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 16)<br />

NUNCMO<br />

(Occurrence 16)<br />

Start Date<br />

(Occurrence 17)<br />

3 516-518 9(3) Right justified with leading zeros.<br />

8 519-526 X(8) CCYYMMDD<br />

3 527-529 9(3) Right justified with leading zeros.<br />

1 530 X(1) Right justified with leading zeros.<br />

3 531-533 9(3) Right justified with leading zeros.<br />

8 534-541 X(8) CCYYMMDD<br />

3 542-544 9(3) Right justified with leading zeros.<br />

1 545 X(1) Right justified with leading zeros.<br />

3 546-548 9(3) Right justified with leading zeros.<br />

8 549-556 X(8) CCYYMMDD<br />

3 557-559 9(3) Right justified with leading zeros.<br />

1 560 X(1) Right justified with leading zeros.<br />

3 561-563 9(3) Right justified with leading zeros.<br />

8 564-571 X(8) CCYYMMDD<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 17)<br />

NUNCMO<br />

(Occurrence 17)<br />

Start Date<br />

(Occurrence 18)<br />

NUNCMO<br />

(Occurrence 18)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 18)<br />

Total Number of<br />

Uncovered<br />

Months<br />

1 575 X(1) Right justified with leading zeros.<br />

3 576-578 9(3) Right justified with leading zeros.<br />

8 579-586 X(8) CCYYMMDD<br />

3 587-589 9(3) Right justified with leading zeros.<br />

1 590 X(1) Right justified with leading zeros.<br />

3 591-593 9(3) Right justified with leading zeros.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-118 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

(Occurrence 18)<br />

Start Date<br />

(Occurrence 19)<br />

NUNCMO<br />

(Occurrence 19)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 19)<br />

NUNCMO<br />

(Occurrence 19)<br />

Start Date<br />

(Occurrence 20)<br />

NUNCMO<br />

(Occurrence 20)<br />

NUNCMO<br />

Status Indicator<br />

(Occurrence 20)<br />

NUNCMO<br />

(Occurrence 20)<br />

Beneficiary’s<br />

Retrieved Date of<br />

Birth<br />

Beneficiary’s<br />

Retrieved Gender<br />

Code<br />

8 594-601 X(8) CCYYMMDD<br />

3 602-604 9(3) Right justified with leading zeros.<br />

1 605 X(1) Right justified with leading zeros.<br />

3 606-608 9(3) Right justified with leading zeros.<br />

8 609-616 X(8) CCYYMMDD<br />

3 617-619 9(3) Right justified with leading zeros.<br />

1 620 X(1) Right justified with leading zeros.<br />

3 621-623 9(3) Right justified with leading zeros.<br />

8 624-631 X(8) CCYYMMDD Beneficiary’s Retrieved Date of Birth (as<br />

retrieved from CMS database for matching<br />

beneficiary).<br />

1 632 X(1) 0 = Unknown<br />

1 = Male<br />

2 = Female<br />

Beneficiary’s Retrieved Gender Code (as<br />

retrieved from CMS database for matching<br />

beneficiary).<br />

Last Name 40 633-672 X(40) CHAR Beneficiary’s Last Name<br />

First Name 30 673-702 X(30) CHAR Beneficiary’s First Name<br />

Middle Initial 1 703 X(1) CHAR First Initial of Beneficiary’s Middle Name<br />

Current State<br />

Code<br />

2 704-705 X(2) CHAR<br />

Current County 3 706-708 X(3) CHAR<br />

Code<br />

Date of Death 8 709-716 X(8) CCYYMMDD<br />

format<br />

Part C/D<br />

Contract Number<br />

(if available)<br />

Part C/D<br />

Enrollment Start<br />

Date (if<br />

available)<br />

5 717-721 X(5) CHAR<br />

8 722-729 X(8) CHAR<br />

Part D Indicator 1 730 X(1) CHAR Y = yes; N = no; space<br />

Part C Contract<br />

Number<br />

Part C<br />

Enrollment Start<br />

Date (if<br />

available)<br />

5 731-735 X(5) CHAR<br />

8 736-743 X(8) CHAR<br />

Part C Indicator 1 744 X(1) CHAR N = no; space<br />

<strong>December</strong> <strong>28</strong>, 2012 F-119 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Format Valid Values Description<br />

(if available)<br />

Filler 6 745-750 X(6) SPACES No meaningful values are supplied in this<br />

field. This field is set to SPACES <strong>and</strong> is not<br />

referenced for meaningful information or<br />

used to store meaningful information, unless<br />

specifically documented otherwise.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-120 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

F.22.3 Trailer Record<br />

Field Size Position Format Valid Values Description<br />

File ID Name 8 1-8 X(8) “CMSBEQRT” This field is always set to the value<br />

"CMSBEQRT.” This code identifies the<br />

record as the Trailer Record of a BEQ<br />

Response File.<br />

Sending Entity:<br />

MBD<br />

8 9-16 X(8) “MBD ” (MBD<br />

+ 5 Spaces)<br />

This field is always set to the value "MBD<br />

.” The value specifically is MBD + 5<br />

following Spaces. This value agrees with<br />

the corresponding value in the Header<br />

Record.<br />

File Creation Date 8 17-24 X(8) CCYYMMDD The date when CMS created the BEQ<br />

Response File. This value is formatted as<br />

CCYYMMDD. For example, January 3,<br />

2010 is the value 20100103. This value<br />

agrees with the corresponding value in the<br />

Header Record.<br />

File Control<br />

Number<br />

9 25-33 X(9) Assigned by<br />

Sending Entity:<br />

MBD<br />

Record Count 7 34-40 9(7) Numeric value<br />

greater than Zero.<br />

The specific Control Number assigned by<br />

CMS to the BEQ Response File. CMS<br />

utilizes this value to track the BEQ<br />

Response File through CMS processing<br />

<strong>and</strong> archive. This value agrees with the<br />

corresponding value in the Header Record.<br />

The total number of Transactions or Detail<br />

Records on the BEQ Response File. This<br />

value is right justified in the field, with<br />

leading zeros. This value does not include<br />

non-numeric characters, such as commas,<br />

spaces, dashes, decimals.<br />

Filler 710 41-750 X(710) Spaces No meaningful values are supplied in this<br />

field. This field is set to SPACES is not<br />

referenced for or used to store meaningful<br />

information, unless specifically<br />

documented otherwise.<br />

Total Length = 750<br />

<strong>December</strong> <strong>28</strong>, 2012 F-121 BEQ Response File


Plan Communications User Guide Appendices, Version 6.3<br />

F.23 MA Full Dual Auto Assignment Notification File<br />

This cumulative monthly file identifies organizations’ enrollees who are full-benefit dual eligible.<br />

The following records are included in this file:<br />

Header Record This first record of the file only occurs once.<br />

Detail Record (Transaction) This record contains Beneficiary information <strong>and</strong><br />

may occur multiple times.<br />

Trailer Record This last record of the file only occurs once.<br />

F.23.1 Header Record<br />

Field Size Position Format Valid Values Description<br />

File ID<br />

Name<br />

Sending<br />

Entity:<br />

MBD<br />

File<br />

Creatio<br />

n Date<br />

File<br />

Control<br />

Number<br />

Filler<br />

8 1-8 X(8) “MMAADUAH”<br />

8 9-16 X(8)<br />

“MBD ”<br />

(MBD + 5<br />

Spaces)<br />

8 17-24 X(8) YYYYMMDD<br />

9 25-33 X(9)<br />

67 34-100 X(67) Spaces<br />

Total Length = 100<br />

Assigned by<br />

Sending Entity<br />

(MBD)<br />

This field is always set to the value "MMAADUAH.”<br />

This code identifies the record as the Header Record of an<br />

Auto Assignment Full Dual Notification File.<br />

This is always set to the value "MBD .” The value<br />

specifically is MBD + 5 following Spaces. This value<br />

agrees with the corresponding value in the Trailer Record.<br />

The date on which the Full Dual File was created by<br />

CMS. This value is in the format of YYYYMMDD. For<br />

example, January 3, 2010 is the value 20100103. This<br />

value agrees with the corresponding value in the Trailer<br />

Record.<br />

The specific Control Number assigned by CMS to the Full<br />

Dual Notification File. CMS utilizes this value to track the<br />

Full Dual Notification File through CMS processing <strong>and</strong><br />

archive. This value agrees with the corresponding value in<br />

the Trailer Record.<br />

No meaningful values are supplied in this field. This field<br />

is set to SPACES <strong>and</strong> is not referenced for or used to store<br />

meaningful information, unless specifically documented<br />

otherwise.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-122 MA Full Dual Auto Assignment<br />

Notification File


F.23.2 Detail Record (Transaction)<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Field Name Size Position<br />

Contract Number<br />

(This field provides the Contract assigned to the beneficiary; CNTRCT_NUM in<br />

CME_SRVC_DEL_ELCT)<br />

Run Date<br />

(This field provides the creation date of the file in CCYYMMDD format)<br />

Filler<br />

(This field is all spaces)<br />

Beneficiary’s HICN/RRB<br />

(This field provides either the HICN or the RRB Number for identification of the<br />

individual; BENE_CAN_NUM <strong>and</strong> BIC_CD or RRB_HIC_NUM in CME_BENE)<br />

Beneficiary’s Surname<br />

(This field provides the last name of the individual; BENE_LAST_NAME in<br />

CME_BENE_NAME)<br />

Initial of Beneficiary’s First Name<br />

(This field provides the initial of the first name of the individual; BENE_1ST_NAME in<br />

CME_BENE_NAME)<br />

Beneficiary’s Gender<br />

(This field provides the gender of the individual; BENE_SEX_CD in MBD_BENE; ‘0’,<br />

‘1’, or ‘2’)<br />

Beneficiary’s Date of Birth<br />

(This field provides the date of birth of the individual in CCYYMMDD format;<br />

BENE_BIRTH_DT in CME_BENE)<br />

Filler<br />

(This field is all spaces)<br />

Total Length = 100<br />

F.23.3 Trailer Record<br />

5 1-5<br />

8 6-13<br />

6 14-19<br />

12 20-31<br />

12 32-43<br />

1 44<br />

1 45<br />

8 46-53<br />

47 54-100<br />

Data Field<br />

File ID<br />

Name<br />

Sending<br />

Entity<br />

MBD<br />

File<br />

Creation<br />

Date<br />

File<br />

Control<br />

Number<br />

Size<br />

Positio<br />

n<br />

8 1- 8 X(8)<br />

8 9-16 X(8)<br />

Format Valid Values Field Definition<br />

“MMAADUAT<br />

”<br />

“MBD ”<br />

(MBD + 5<br />

Spaces)<br />

This field is always set to the value "MMAADUAT.”<br />

This code identifies the record as the Trailer Record of<br />

an Auto Assignment Full Dual Notification File.<br />

This field is always set to the value "MBD .” The<br />

value specifically is MBD + 5 following Spaces. This<br />

value agrees with the corresponding value in the<br />

Header Record.<br />

8 17-24 X(8) YYYYMMDD The date on which the Full Dual Notification File was<br />

created by CMS. This value is formatted as<br />

YYYYMMDD. For example, January 3, 2010 is the<br />

value 20100103. This value agrees with the<br />

corresponding value in the Header Record.<br />

9 25-33 X(9)<br />

Assigned by<br />

Sending Entity<br />

(MBD)<br />

The specific Control Number assigned by CMS to the<br />

Full Dual Notification File. CMS utilizes this value to<br />

track the Full Dual Notification File through CMS<br />

processing <strong>and</strong> archive. This value agrees with the<br />

corresponding value in the Header Record.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-123 MA Full Dual Auto Assignment<br />

Notification File


Plan Communications User Guide Appendices, Version 6.3<br />

Data Field<br />

Record<br />

Count<br />

Size<br />

Positio<br />

n<br />

9 34-42 9(9)<br />

Filler 58 43-100 X(58) Spaces<br />

Total Length = 100<br />

Format Valid Values Field Definition<br />

Numeric value<br />

greater than<br />

Zero.<br />

The total number of Transactions or Detail Records<br />

on the Full Dual Notification File. This value is right<br />

justified in the field, with leading zeros. This value<br />

does not include non-numeric characters, such as<br />

commas, spaces, dashes, decimals.<br />

No meaningful values are supplied in this field. This<br />

field is set to SPACES <strong>and</strong> is not referenced for or<br />

used to store meaningful information, unless<br />

specifically documented otherwise.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-124 MA Full Dual Auto Assignment<br />

Notification File


Plan Communications User Guide Appendices, Version 6.3<br />

F.24 Auto Assignment (PDP) Address Notification File<br />

This file contains monthly addresses of Beneficiaries that are either AE, FE, or reassigned to<br />

PDPs. This file contains a header record, detail records, <strong>and</strong> a trailer record. Please see the Main<br />

Guide section 4.4.5 for details on its use.<br />

Header Record This first record of the file only occurs once.<br />

Detail Record This record contains Beneficiary information <strong>and</strong> may<br />

occur multiple times.<br />

Trailer Record This last record of the file only occurs once.<br />

The full address, including city/state/zip code, is “wrapped” in the fields “Beneficiary Address<br />

Line 1” through “Beneficiary Address Line 6,” with the result that street address, city, <strong>and</strong> state<br />

may appear on different lines for different beneficiaries. Different parts of the address appears<br />

only on certain lines, as follows:<br />

<br />

<br />

<br />

<br />

<br />

Beneficiary Address Lines 1-6 is limited to Representative Payee Name (if applicable),<br />

<strong>and</strong> street address, <strong>and</strong> these elements “wrap.”<br />

When a Beneficiary has a Representative Payee, the Beneficiary Representative Payee<br />

Name prints on Address Line 1, <strong>and</strong> may use more Address Lines.<br />

The actual street address in such cases is printed on the line after the name concludes.<br />

Address Lines print on fewer than six lines with the remainder of the lines padded with<br />

space prior to printing.<br />

City/State/Zip Code data only appear in the fields labeled as City/State/Zip Code data<br />

fields.<br />

F.24.1 Header Record<br />

Field Size Position<br />

Header Code (This field used for file/record identification purposes,<br />

‘MMAAPDPGH’)<br />

Sending Entity (This field used to identify the sending entity, ‘MBD<br />

‘(MBD + 5 spaces) )<br />

9 1-9<br />

8 10-17<br />

File Creation Date (The date the file was created in CCYYMMDD format) 8 18-25<br />

File Control Number (Unique file identifier created by Sending Entity) 9 26-34<br />

Filler (This field is all spaces) 581 35-615<br />

Total Length = 615<br />

<strong>December</strong> <strong>28</strong>, 2012 F-125 Auto Assignment (PDP)<br />

Address Notification File


Plan Communications User Guide Appendices, Version 6.3<br />

F.24.2 Detail Record<br />

Field Size Position<br />

Beneficiary’s HICN (This field provides the HICN for identification of the<br />

individual; RRB_HIC_NUM in MBD_BENE)<br />

Beneficiary’s Last Name (This field provides the first twelve characters of<br />

the last name of the individual; BENE_LAST_NAME in MBD_BENE)<br />

Beneficiary’s First name (This field provides the first seven characters of<br />

the first name of the individual; BENE_1ST_NAME in MBD_BENE)<br />

Beneficiary’s Middle Initial (This field provides the middle initial of the<br />

individual; MDL_INITL_NAME in MBD_BENE)<br />

Beneficiary’s Gender (This field provides the gender of the individual;<br />

BENE_SEX_CD in MBD_BENE; ‘0’, ‘1’, or ‘2’)<br />

Beneficiary’s DOB (This field provides the date of birth of the individual in<br />

CCYYMMDD format; BENE_BIRTH_DT in MBD_BENE)<br />

Medicaid Indicator (This field indicates the beneficiary’s Medicaid<br />

eligibility; MDCD_ELGBL_STUS_SW in MBQ_DUAL_MDCR; ‘Y’ or<br />

‘N’)<br />

Contract Number (This field provides the Contract assigned to the<br />

beneficiary; ASGN_CNTRCT_NUM in MBQ_AA)<br />

State Code (This field provides the beneficiary’s state of residency;<br />

SSA_STD_STATE_CD in MBD_BENE_ADR)<br />

County Code (This field provides the beneficiary’s county of residency;<br />

SSA_STD_CNTY_CD in MBD_BENE_ADR)<br />

12 1-12<br />

12 13-24<br />

7 25-31<br />

1 32<br />

1 33<br />

8 34-41<br />

1 42<br />

5 43-47<br />

2 48-49<br />

3 50-52<br />

Filler (This field is all spaces) 7 53-59<br />

TC (This field identifies the type of record; ‘61’) 2 60-61<br />

Filler (This field is all spaces) 1 62<br />

Effective Date (The effective date of the assignment in CCYYMMDD<br />

format; ASGN_EFCTV_DT in MBQ_AA)<br />

8 63-70<br />

Filler (This field is all spaces) 1 71<br />

PBP (This field notes the PBP of the auto-assigned contract;<br />

ASGN_PBP_NUM in MBQ_AA)<br />

3 72-74<br />

Filler (This field is all spaces) 49 75-123<br />

Application Date (The date of the application in CCYYMMDD format) 8 124-131<br />

Filler (This field is all spaces) 30 132-161<br />

Election Type (This field indicates the type of election; ‘S’) 1 162<br />

Enrollment Source (This field indicates the source of the enrollment; ‘A’) 1 163<br />

Filler (This field is all spaces) 1 164<br />

Premium Withhold Option/Parts C-D (This field indicates the payment<br />

option for payment of Part C <strong>and</strong> D premiums; PRM_WTHLD_OPT_CD<br />

in MBQ_PREMIUM; ‘D’)<br />

1 165<br />

Filler (This field is all spaces) 3 166-168<br />

Creditable Coverage Flag (This field indicates if the beneficiary has 1 169<br />

<strong>December</strong> <strong>28</strong>, 2012 F-126 Auto Assignment (PDP)<br />

Address Notification File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position<br />

creditable coverage; derived from MBQ_MARX_CRED_CVRG; ‘Y’, ‘N’,<br />

or ‘ ‘)<br />

Filler (This field is all spaces) 73 170-242<br />

Part D Subsidy Level (This field identifies the portion of the Part D<br />

Premium subsidized; PTD_PRM_SBSDY_PCT in MBQ_LIS; For<br />

monthly, value is always ‘100’; For Facilitated, values are either ‘100’,<br />

‘075’, ‘050’, or ‘025’)<br />

Co-Payment Category (This field indicates the Subsidy Co-Payment level<br />

for the beneficiary; LIS_COPMT_LVL_ID in MBQ_LIS; ‘1’ or ‘4’)<br />

Co-Payment Effective Date (The date the LIS begins;<br />

SBSDY_STRT_DATE in MBQ_LIS; For monthly, is always<br />

MMDDYYYY; For Facilitated, value is spaces)<br />

Beneficiary Address Line 1 (First line in the mailing address;<br />

BENE_LINE_1_ADR in MBD_BENE_ADR)<br />

Beneficiary Address Line 2 (Second line in the mailing address;<br />

BENE_LINE_2_ADR in MBD_BENE_ADR)<br />

Beneficiary Address Line 3 (Third line in the mailing address;<br />

BENE_LINE_3_ADR in MBD_BENE_ADR)<br />

Beneficiary Address Line 4 (Fourth line in the mailing address;<br />

BENE_LINE_4_ADR in MBD_BENE_ADR)<br />

Beneficiary Address Line 5 (Fifth line in the mailing address;<br />

BENE_LINE_5_ADR in MBD_BENE_ADR)<br />

Beneficiary Address Line 6 (Sixth line in the mailing address;<br />

BENE_LINE_6_ADR in MBD_BENE_ADR)<br />

Beneficiary Address City (The city in the mailing address;<br />

BENE_ADR_CITY_NAME in MBD_BENE_ADR)<br />

Beneficiary Address State (The state in the mailing address;<br />

ADR_PSTL_STATE_CD in MBD_BENE_ADR)<br />

Beneficiary Zip Code (The zip code in the mailing address;<br />

BENE_ADR_ZIP_CD in MBD_BENE_ADR)<br />

Full Last Name (This field provides the last name of the individual;<br />

BENE_LAST_NAME in MBD_BENE)<br />

Full First Name (This field provides the first name of the individual;<br />

BENE_1ST_NAME in MBD_BENE)<br />

Total Length = 615<br />

3 243-245<br />

1 246<br />

8 247-254<br />

40 255-294<br />

40 295-334<br />

40 335-374<br />

40 375-414<br />

40 415-454<br />

40 455-494<br />

40 495-534<br />

2 535-536<br />

9 537-545<br />

40 546-585<br />

30 586-615<br />

<strong>December</strong> <strong>28</strong>, 2012 F-127 Auto Assignment (PDP)<br />

Address Notification File


Plan Communications User Guide Appendices, Version 6.3<br />

F.24.3 Trailer Record<br />

Field Size Position<br />

Trailer Code<br />

(This field used for file/record identification purposes, ‘MMAAPDPGT’)<br />

Sending Entity<br />

(This field used to identify the sending entity, ‘MBD ‘(MBD + 5 spaces) )<br />

File Creation Date<br />

(The date the file was created in CCYYMMDD format)<br />

File Control Number<br />

(Unique file identifier created by Sending Entity)<br />

Record Count<br />

(Number of Detail Records, right justified with leading zeros)<br />

Filler<br />

This field is all spaces<br />

Total Length = 615<br />

9 1-9<br />

8 10-17<br />

8 18-25<br />

9 26-34<br />

9 35-43<br />

572 44-615<br />

<strong>December</strong> <strong>28</strong>, 2012 F-1<strong>28</strong> Auto Assignment (PDP)<br />

Address Notification File


Plan Communications User Guide Appendices, Version 6.3<br />

F.25 Plan Payment Report (PPR)/Interim Plan Payment Report (IPPR) Data<br />

File<br />

Also known as the APPS Payment Letter, this data file itemizes the final monthly payment to the<br />

MCO. This data file <strong>and</strong> subsequent report is produced by the APPS when final payments are<br />

calculated. CMS makes this report available to MCOs as part of month-end processing.<br />

The IPPR is provided when a Plan is approved for an interim payment outside of the normal<br />

monthly process. The data file/report contains the amount <strong>and</strong> reason for the interim payment to<br />

the Plan.<br />

F.25.1<br />

Header Record<br />

Item Field Position Length Type Definition<br />

1 Contract<br />

Number<br />

1-5 5 Character Contract Number<br />

2 Record<br />

Identification<br />

Code<br />

6-6 1 Character Record Type Identifier<br />

H = Header Record<br />

3 Contract Name 7-56 50 Character Name of the Contract<br />

4 Payment Cycle<br />

Date<br />

57-62 6 Character Identified the month <strong>and</strong> year of payment:<br />

Format = YYYYMM<br />

5 Run Date 63-70 8 Character Identifies the date file was created:<br />

Format = YYYYMMDD<br />

6 Filler 71-200 130 Character Spaces<br />

Total Length = 200<br />

<strong>December</strong> <strong>28</strong>, 2012 F-129 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.25.2<br />

Capitated Payment – Current Activity<br />

Item Field Position Length Type Description<br />

7 Contract<br />

Number<br />

1-5 5 Contract Number<br />

8 Record<br />

Identification<br />

Code<br />

9 Table ID<br />

Number<br />

10 Adjustment<br />

Reason Code<br />

6 1 Record Type Identifier<br />

C = Capitated Payment<br />

7 1 1<br />

8-9 2 Blank = for prospective pay<br />

For list of adjustment reasons codes consult<br />

section H.3 of the <strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong><br />

<strong>Prescription</strong> <strong>Drug</strong> Plan Communication Guide.<br />

11 Part A Total<br />

Members<br />

12 Part B Total<br />

Members<br />

13 Part D Total<br />

Members<br />

14 Part A Payment<br />

Amount<br />

10-17 8 Numeric Number of beneficiaries Part A payments is being<br />

made prospectively.<br />

Format: ZZZZZZZ9<br />

18-25 8 Numeric Number of beneficiaries Part B payments is being<br />

made prospectively.<br />

Format: ZZZZZZZ9<br />

26-33 8 Numeric Number of beneficiaries Part D payments is being<br />

made prospectively.<br />

Format: ZZZZZZZ9<br />

34-46 13 Numeric Total Part A Amount<br />

Format: SSSSSSSSS9.99<br />

15 Part B Payment<br />

Amount<br />

47-59 13 Numeric Total Part B Amount<br />

Format: SSSSSSSSS9.99<br />

16 Part D Payment<br />

Amount<br />

60-72 13 Numeric Total Part D Amount<br />

Format: SSSSSSSSS9.99<br />

17 Coverage Gap<br />

Discount<br />

Amount<br />

73-85 13 Numeric The Coverage Gap Discount included in Part D<br />

Payment.<br />

Format: SSSSSSSSS9.99<br />

18 Total Payment 86- 98 13 Numeric Total Payment<br />

Format: SSSSSSSSS9.99<br />

19 Filler 99-200 102 Character Spaces<br />

Total Length = 200<br />

<strong>December</strong> <strong>28</strong>, 2012 F-130 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.25.3<br />

Premium Settlement<br />

Item Field Position Length Type Description<br />

20 Contract<br />

Number<br />

1-5 5 Character Contract Number<br />

21 Record 6 1 Character Record Type Identifier<br />

Identification<br />

P = Premium Settlement<br />

Code<br />

22 Table ID<br />

Number<br />

7 1 Character 2<br />

23 Part C Premium 8-20 13 Numeric Total Part C Premium Amount<br />

Withholding<br />

Format: SSSSSSSSS9.99<br />

Amount<br />

24 Part D Premium 21-33 13 Numeric Total Part D Premium Amount<br />

Withholding<br />

Format: SSSSSSSSS9.99<br />

Amount<br />

25 Part D Low<br />

Income<br />

34-46 13 Numeric Total Low Income Premium Subsidy<br />

Format: SSSSSSSSS9.99<br />

Premium<br />

Subsidy<br />

26 Part D Late 47-59 13 Numeric Total Late Enrollment Penalty<br />

Enrollment<br />

Format: SSSSSSSSS9.99<br />

Penalty<br />

27 Total Premium<br />

Settlement<br />

60-72 13 Numeric Total Premium Settlement<br />

Format: SSSSSSSSS9.99<br />

Amount<br />

<strong>28</strong> Filler 73-200 1<strong>28</strong> Character Spaces<br />

Total Length = 200<br />

F.25.4<br />

Fees<br />

Leng<br />

Item Field Position<br />

Type<br />

Description<br />

th<br />

29 Contract 1-5 5 Character Contract Number<br />

Number<br />

30 Record 6 1 Character Record Type Identifier<br />

Identification<br />

F = FEES<br />

Code<br />

31 Table ID 7 1 Character 3<br />

Number<br />

32 NMEC Part A<br />

Subject to Fee<br />

33 NMEC Part A<br />

Rate<br />

34 Part A Fee<br />

Amount<br />

35 NMEC Part B<br />

Subject to Fee<br />

36 NMEC Part B<br />

Rate<br />

8-20 13 Numeric Part A amount subject to National <strong>Medicare</strong><br />

Educational Campaign fees.<br />

Format:ZZZZZZZZZ9.99<br />

21-27 7 Numeric Rate used to calculate the fees for Part A.<br />

Format: 0.99999<br />

<strong>28</strong>-40 13 Numeric Fee Assessed for Part A<br />

Format:SSSSSSSSS9.99<br />

41-53 13 Numeric Part B amount subject to National <strong>Medicare</strong><br />

Educational Campaign fees.<br />

Format: ZZZZZZZZZ9.99<br />

54-60 7 Numeric Rate used to calculate the fees for Part B.<br />

Format: 0.99999<br />

<strong>December</strong> <strong>28</strong>, 2012 F-131 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Position<br />

Leng<br />

th<br />

Type<br />

Description<br />

37 Part B Fee<br />

Amount<br />

61-73 13 Numeric Fee Assessed for Part B<br />

Format: SSSSSSSSS9.99<br />

38 NMEC Part D<br />

Subject to Fee<br />

74-86 13 Numeric Part D amount subject to National <strong>Medicare</strong><br />

Educational Campaign fees.<br />

Format: ZZZZZZZZZ9.99<br />

39 NMEC Part D<br />

Rate<br />

87-93 7 Numeric Rate used to calculate the fees for Part D.<br />

Format: 0.99999<br />

40 Part D Fee<br />

Amount<br />

94-106 13 Numeric Fee Assessed for Part D<br />

Format: SSSSSSSSS9.99<br />

41 Total NMEC<br />

Fee Assessed<br />

107- 119 13 Numeric Total NMEC Fee Assessed for Part A, B <strong>and</strong> D<br />

Format: SSSSSSSSS9.99<br />

42 Total<br />

Prospective<br />

Part D<br />

Members<br />

43 Rate for COB<br />

Fees<br />

44 Amount of<br />

COB Fees<br />

45 Total of<br />

Assessed Fees<br />

120- 127 8 Numeric Total members for Part D<br />

Format: ZZZZZZZ9<br />

1<strong>28</strong>- 131 4 Numeric Rate used to calculate the COB fees.<br />

Format: 0.99<br />

132- 144 13 Numeric COB Fee<br />

Format: SSSSSSSSS9.99<br />

145- 157 13 Numeric Total of all Fees Assessments<br />

Format: SSSSSSSSS9.99<br />

46 Filler 158- 200 43 Character Spaces<br />

Total Length = 200<br />

F.25.5<br />

Special Adjustments<br />

Item Field Position Length Type Description<br />

47 Contract 1 – 5 5 Character Contract Number<br />

Number<br />

48 Record<br />

Identification<br />

6 – 6 1 Character Record Type Identifier<br />

S = Special Adjustments<br />

Code<br />

49 Table ID 7 – 7 1 Character 4<br />

Number<br />

50 Document ID 8 – 15 8 Numeric The document ID for identifying the adjustment.<br />

51 Source 16-20 5 Character The CMS division responsible for initiating the<br />

adjustments.<br />

52 Description 21 – 70 50 Character The reason the adjustment was made.<br />

53 Type 71 – 90 20 Character The payment component the adjustment is for:<br />

• CGD=Coverage Gap Discount Invoice<br />

• CMP=Civil Monetary Penalty<br />

• CST=Cost Plan Adjustment<br />

• PTD=Part D Risk Adjustment<br />

• PRS=Annual Part D Reconciliation<br />

• RAC=Recovery Audit Contract Adjustment<br />

• RSK=Risk Adjustment<br />

• HTC=HITECH Incentive Payment<br />

• OTH=default non-specific group.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-132 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Position Length Type Description<br />

54 Adjustment to<br />

Part A<br />

55 Adjustment to<br />

Part B<br />

56 Adjustment to<br />

Part D or<br />

Adjustment to<br />

HITECH<br />

Incentive<br />

Payment<br />

57 Premium C<br />

Withholding<br />

Part A<br />

58 Premium C<br />

Withholding<br />

Part B<br />

59 Premium D<br />

Withholding<br />

60 Part D Low<br />

Income<br />

Premium<br />

Subsidy<br />

61 Total<br />

Adjustment<br />

Amount<br />

91 – 103 13 Numeric Adjustment amount for Part A<br />

Format: SSSSSSSSS9.99<br />

104 – 116 13 Numeric Adjustment amount for Part B<br />

Format: SSSSSSSSS9.99<br />

117 – 129 13 Numeric Adjustment amount for HITECH Incentive<br />

Payment when the adjustment type in data item<br />

53 is “HTC”. The adjustment amount is for Part<br />

D for the rest of the types.<br />

Format: SSSSSSSSS9.99<br />

130 - 142 13 Numeric Adjustment amount for Premium Withholding<br />

Part A.<br />

Format: SSSSSSSSS9.99<br />

143 – 155 13 Numeric Adjustment amount for Premium Withholding<br />

Part B.<br />

Format: SSSSSSSSS9.99<br />

156 – 168 13 Numeric Adjustment amount for Premium D<br />

Withholding.<br />

Format: SSSSSSSSS9.99<br />

169 - 181 13 Numeric Adjustment amount for Low Income Subsidy.<br />

Format: SSSSSSSSS9.99<br />

182 – 194 13 Numeric Total Adjustments<br />

Format: SSSSSSSSS9.99<br />

62 Filler 195 – 200 6 Character Spaces<br />

Total Length = 200<br />

F.25.6<br />

Previous Cycle Balance Summary<br />

Item Field Position Length Type Description<br />

63 Contract Number 1 – 5 5 Character Contract Number<br />

64 Record<br />

Identification<br />

Code<br />

6 – 6 1 Character Record Type Identifier<br />

L = Last Period Carry Over<br />

Amounts carried over to this month from<br />

previous months<br />

65 Table ID Number 7 – 7 1 Character 5<br />

66 Part A Carry<br />

Over Amount<br />

67 Part B Carry Over<br />

Amount<br />

68 Part D Carry Over<br />

Amount<br />

8 – 20 13 Numeric Part A Carry Over Amount from Table 5 ** -<br />

Previous Balance Column.<br />

Format: SSSSSSSSS9.99<br />

21 – 33 13 Numeric Part B Carry Over Amount from Table 5 ** -<br />

Previous Balance Column.<br />

Format: SSSSSSSSS9.99<br />

34 – 46 13 Numeric Part D Carry Over Amount from Table 5 ** -<br />

Previous Balance Column.<br />

Format: SSSSSSSSS9.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-133 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Position Length Type Description<br />

69 Part C Premium<br />

Withholding<br />

Carry Over<br />

Amount<br />

70 Part D Premium<br />

Withholding<br />

Carry Over<br />

Amount<br />

71 Part D Low<br />

Income Premium<br />

Subsidy Carry<br />

Over Amount<br />

72 Part D Late<br />

Enrollment<br />

Penalty Carry<br />

Over Amount<br />

73 Education User<br />

Fee Carry Over<br />

Amount<br />

74 Part D COB User<br />

Fee Carry Over<br />

Amount<br />

75 CMS Special<br />

Adjustments<br />

Carry Over<br />

Amount<br />

76 Total Carry Over<br />

Amount<br />

47 – 59 13 Numeric Part C Premium Withholding Carry Over<br />

Amount from Table 5 ** - Previous Balance<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

60 – 72 13 Numeric Part D Premium Withholding Carry Over<br />

Amount from Table 5 ** - Previous Balance<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

73 – 85 13 Numeric Part D Low Income Premium Subsidy Carry<br />

Over Amount from Table 5 ** - Previous Balance<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

86 – 98 13 Numeric Part D Late Enrollment Penalty Carry Over<br />

Amount from Table 5 ** - Previous Balance<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

99 – 111 13 Numeric Education User Fee Carry Over Amount from<br />

Table 5 ** - Previous Balance Column.<br />

Format: SSSSSSSSS9.99<br />

112 – 124 13 Numeric Part D COB User Fee Carry Over Amount from<br />

Table 5 ** - Previous Balance Column.<br />

Format:SSSSSSSSS9.99<br />

125 – 137 13 Numeric CMS Special Adjustments Carry Over Amount<br />

from Table 5 ** - Previous Balance Column.<br />

Format: SSSSSSSSS9.99<br />

138 – 150 13 Numeric Sum of amounts in Previous Balance Column<br />

Format: SSSSSSSSS9.99<br />

77 Filler 151 – 200 50 Character Spaces.<br />

Total Length = 200<br />

F.25.7 Payment Summary<br />

Item Field Position Length Type Description<br />

78 Contract<br />

Number<br />

79 Record<br />

Identification<br />

Code<br />

80 Table ID<br />

Number<br />

81 Part A<br />

Amount<br />

1 – 5 5 Character Contract Number<br />

6 – 6 1 Character Record Type Identifier<br />

A = Payment Summary<br />

Amounts included in this month’s payment<br />

from Tables 1 thru 4 plus Carry Over (from<br />

Previous Balance Column).<br />

7 – 7 1 Character 5<br />

8 – 20 13 Numeric Part A amount from Table 5 ** -Net Payment<br />

Column.<br />

Format: ZZZZZZZZZ9.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-134 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item Field Position Length Type Description<br />

82 Part B Amount 21 – 33 13 Numeric Part B amount from Table 5 ** -Net Payment<br />

Column.<br />

Format: ZZZZZZZZZ9.99<br />

83 Part D<br />

Amount<br />

84 Part C<br />

Premium<br />

Withholding<br />

Amount<br />

85 Part D<br />

Premium<br />

Withholding<br />

Amount<br />

86 Part D Low<br />

Income<br />

Premium<br />

Subsidy<br />

Amount<br />

87 Part D Late<br />

Enrollment<br />

Penalty<br />

Amount<br />

88 Education<br />

User Fee<br />

Amount<br />

89 Part D COB<br />

User Fee<br />

Amount<br />

90 CMS Special<br />

Adjustments<br />

Amount<br />

91 Total Net<br />

Payment<br />

34 – 46 13 Numeric Part D amount from Table 5 ** -Net Payment<br />

Column.<br />

Format: ZZZZZZZZZ9.99<br />

47 – 59 13 Numeric Part C Premium Withholding Amount from<br />

Table 5 ** -Net Payment Column.<br />

Format: ZZZZZZZZZ9.99<br />

60 – 72 13 Numeric Part D Premium Withholding Amount from<br />

Table 5 ** -Net Payment Column.<br />

Format: ZZZZZZZZZ9.99<br />

73 – 85 13 Numeric Part D Low Income Subsidy Amount from<br />

Table 5 ** -Net Payment Column.<br />

Format: ZZZZZZZZZ9.99<br />

86 – 98 13 Numeric Part D Late Enrollment Penalty Amount from<br />

Table 5 ** -Net Payment Column.<br />

Format: SSSSSSSSS9.99<br />

99 – 111 13 Numeric Education User Fee Amount from Table 5 ** -<br />

Net Payment Column.<br />

Format: SSSSSSSSS9.99<br />

112 – 124 13 Numeric Part B COB Fee Amount from Table 5 ** -Net<br />

Payment Column.<br />

Format: SSSSSSSSS9.99<br />

125 – 137 13 Numeric CMS Special Adjustments Amount from Table<br />

5 ** -Net Payment Column.<br />

Format: SSSSSSSSS9.99<br />

138 – 150 13 Numeric Sum of amounts in Net Payment Column. This<br />

is the plan’s Net Payment Amount for this<br />

month. If the amount is negative, the payment<br />

will be carried forward.<br />

Format: SSSSSSSSS9.99<br />

92 Filler 151 – 200 50 Character Spaces.<br />

Total Length = 200<br />

<strong>December</strong> <strong>28</strong>, 2012 F-135 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.25.8 Payment Balance Carried Forward<br />

Item<br />

#<br />

Data Element Position Length Type Description<br />

93 Contract<br />

Number<br />

94 Record<br />

Identification<br />

Code<br />

95 Table ID<br />

Number<br />

96 Part A Amount<br />

Carry Forward<br />

to Next Cycle<br />

97 Part B Amount<br />

Carry Forward<br />

to Next Cycle<br />

98 Part D Amount<br />

Carry Forward<br />

to Next Cycle<br />

99 Part C Premium<br />

Withholding<br />

Amount Carry<br />

Forward to<br />

Next Cycle<br />

100 Part D<br />

Premium<br />

Withholding<br />

Amount Carry<br />

Forward to<br />

Next Cycle<br />

101 Part D Low<br />

Income<br />

Premium<br />

Subsidy<br />

Amount Carry<br />

Forward to<br />

Next Cycle<br />

102 Part D Late<br />

Enrollment<br />

Penalty<br />

Amount Carry<br />

Forward to<br />

Next Cycle<br />

103 Education User<br />

Fee Amount<br />

Carry Forward<br />

to Next Cycle<br />

104 Part D COB<br />

User Fee<br />

Amount Carry<br />

Forward to<br />

Next Cycle<br />

1 – 5 5 Character Contract Number<br />

6 – 6 1 Character Record Type Identifier<br />

N = Balance Carried Forward to Next Cycle.<br />

Amounts carried forward (<strong>and</strong> not paid) to next<br />

month from this month<br />

7 – 7 1 Character 5<br />

8 – 20 13 Numeric Part A Amount Carry Forward from Table 5 ** -<br />

Balance Forward Column.<br />

Format: SSSSSSSSS9.99<br />

21 – 33 13 Numeric Part B Amount Carry Forward from Table 5 ** -<br />

Balance Forward Column.<br />

Format: SSSSSSSSS9.99<br />

34 – 46 13 Numeric Part D Amount Carry Forward from Table 5 ** -<br />

Balance Forward Column.<br />

Format: SSSSSSSSS9.99<br />

47 – 59 13 Numeric Part C Premium Withholding Amount Carry<br />

Forward from Table 5 ** -Balance Forward<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

60 – 72 13 Numeric Part D Premium Withholding Amount Carry<br />

Forward from Table 5 ** -Balance Forward<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

73 – 85 13 Numeric Part D Low Income Subsidy Amount Carry<br />

Forward from Table 5 ** -Balance Forward<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

86 – 98 13 Numeric Part D Late Enrollment Penalty Amount Carry<br />

Forward from Table 5 ** -Balance Forward<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

99 – 111 13 Numeric Education User Fee Amount Carry Forward<br />

from Table 5 ** -Balance Forward Column.<br />

Format: SSSSSSSSS9.99<br />

112 – 124 13 Numeric Part B COB Fee Amount Carry Forward from<br />

Table 5 ** -Balance Forward Column.<br />

Format:SSSSSSSSS9.99<br />

<strong>December</strong> <strong>28</strong>, 2012 F-136 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item<br />

#<br />

Data Element Position Length Type Description<br />

105 CMS Special<br />

Adjustments<br />

Amount Carry<br />

Forward to<br />

Next Cycle<br />

106 Total Carry<br />

Forward<br />

Amount<br />

125 – 137 13 Numeric CMS Special Adjustments Amount Carry<br />

Forward from Table 5 ** -Balance Forward<br />

Column.<br />

Format: SSSSSSSSS9.99<br />

138 – 150 13 Numeric Sum of amounts in Balance Forward Column<br />

Format: SSSSSSSSS9.99<br />

107 Filler 151 – 200 50 Character Spaces.<br />

Total Length = 200<br />

<strong>December</strong> <strong>28</strong>, 2012 F-137 PPR/IPPR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.26 Long-Term Institutionalized (LTI) Resident Report Data File<br />

The LTI Resident Report provides Part D sponsors with a list of their beneficiaries who are LTI<br />

residents during July <strong>and</strong> January annually. This report contains basic information on the<br />

beneficiaries <strong>and</strong> their institutions, i.e., Skilled Nursing Home or Nursing Home.<br />

This new report provides information to Part D Sponsors on which of their enrollees are<br />

institutionalized, as well as the names <strong>and</strong> addresses of the particular long-term care (LTC)<br />

facilities in which those beneficiaries reside. This information is obtained by linking <strong>Medicare</strong><br />

enrollment information with data from the Minimum Data Set (MDS) of nursing home<br />

assessments. The list of beneficiaries represents those who are LTI residents as of July <strong>and</strong><br />

January annually with a reported length of stay of more than 90 days.<br />

The file is sent via HPMS to Part D sponsors in late April <strong>and</strong> late September. The report is<br />

provided in a fixed-length text format <strong>and</strong> the record layout is described below.<br />

Item<br />

Field<br />

Field<br />

Type<br />

1 Part D Contract Number CHAR 5 1-5<br />

2 Part D Plan Number CHAR 3 6-8<br />

3 Part D Plan Name CHAR 50 9-58<br />

Length Position Description<br />

Part D Contract Number associated with<br />

the resident during the month of the last<br />

nursing home assessment date.<br />

Part D Plan Number associated with the<br />

resident during the month of the last<br />

nursing home assessment date.<br />

Part D Plan Name associated with the<br />

resident during the month of the last<br />

nursing home assessment date.<br />

4 Last Name CHAR 24 59-82 Beneficiary Last Name<br />

5 First Name CHAR 15 83-97 Beneficiary First Name<br />

6 HICN CHAR 12 98109 HICN associated with the resident.<br />

7 Date of Birth DATE 8 110-117<br />

Beneficiary’s Date of Birth<br />

CCYYMMDD – Format<br />

8 Gender CHAR 1 118<br />

Beneficiary Gender Code<br />

1 = Male<br />

2 = Female<br />

0 = Unknown<br />

9 Nursing Home Length of Stay CHAR 6 119-124<br />

Nursing Home Length of Stay in days<br />

(0 – 999999) at the time of the last<br />

Nursing Home assessment.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-138 LTI Resident Report Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Item<br />

Field<br />

Field<br />

Type<br />

Length Position Description<br />

10 Nursing Home Admission Date DATE 8 125-132<br />

11<br />

Last Nursing Home<br />

Assessment Date<br />

DATE 8 133-140<br />

12 Part A Indicator CHAR 1 141<br />

13 Nursing Home Name CHAR 50 142-191<br />

14 <strong>Medicare</strong> Provider ID CHAR 12 192-203<br />

15 Provider Telephone Number CHAR 13 204-216<br />

16 Provider Address CHAR 50 217-266<br />

17 Provider City CHAR 20 267-<strong>28</strong>6<br />

18 Provider State Code CHAR 2 <strong>28</strong>7-<strong>28</strong>8<br />

19 Provider Zip Code CHAR 11 <strong>28</strong>9-299<br />

Total Length = 299<br />

Admission date associated with the last<br />

assessment for the resident.<br />

CCYYMMDD – Format<br />

Target date of the last assessment for<br />

the resident.<br />

CCYYMMDD – Format<br />

Reason for assessment (AA8B)<br />

associated with the last assessment for<br />

the resident.<br />

0 = No<br />

1 = Yes<br />

Name of Nursing Home associated with<br />

the last assessment for the resident.<br />

<strong>Medicare</strong> Provider ID of Nursing Home<br />

associated with the last assessment for<br />

the resident.<br />

Telephone Number of Nursing Home<br />

associated with the last assessment for<br />

the resident.<br />

Address of Nursing Home associated<br />

with the last assessment for the resident.<br />

City of Nursing Home associated with<br />

the last assessment for the resident.<br />

State Code of Nursing Home associated<br />

with the last assessment for the resident.<br />

Zip Code of Nursing Home associated<br />

with the last assessment for the resident.<br />

<strong>December</strong> <strong>28</strong>, 2012 F-139 LTI Resident Report Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.27 Agent Broker Compensation Report Data File<br />

For Plan enrollments, MARx establishes a status of initial or renewal as well as a six-year<br />

compensation cycle, which provides <strong>Plans</strong> with the information necessary to determine how to<br />

pay agents for specific Beneficiary enrollments. <strong>Plans</strong> can pay agents an initial amount or a<br />

renewal amount as provided in the CMS agent compensation guidance.<br />

Based on the qualification rules, year 1 is the initial year <strong>and</strong> years 2 through 6 are the renewal<br />

years. <strong>Plans</strong> are responsible for using this information in conjunction with their internal payment<br />

<strong>and</strong> enrollment tracking systems to determine an agent’s use <strong>and</strong> how much to pay the agent.<br />

The Agent Broker Compensation Report Data File is generated <strong>and</strong> sent to <strong>Plans</strong> along with the<br />

first DTRR of each calendar month.<br />

Item Field Length Position Description<br />

1<br />

Contract<br />

Number**<br />

5 1-5 Contact identification<br />

2 PBP 3 6-8 Plan Benefit Package<br />

3 HICN 12 9-20 HICN, composed of CAN <strong>and</strong> BIC<br />

4 First Name 30 21-50 Beneficiary first name<br />

5 Middle Name 15 51-65 Beneficiary middle name<br />

6 Last Name 40 66-105 Beneficiary last name<br />

7 Filler 173 106-278 Spaces<br />

8<br />

9<br />

10<br />

Enrollment<br />

Effective Start<br />

Date<br />

Cycle-Year as<br />

of Enrollment<br />

Effective Start<br />

Date<br />

Report<br />

Generation Date<br />

8 279-<strong>28</strong>6<br />

3 <strong>28</strong>7-<strong>28</strong>9<br />

8 290-297<br />

Date Beneficiary's Plan enrollment starts, YYYYMMDD –<br />

Format.<br />

Numeric value representing the broker compensation cycle-year<br />

count as of enrollment effective start date:<br />

'1' = first calendar year,<br />

'2' = second calendar year,<br />

'3' = third calendar year,<br />

'4' = fourth calendar year,<br />

'5' = fifth calendar year,<br />

'6' = sixth calendar year.<br />

Date report created<br />

YYYYMMDD – Format<br />

<strong>December</strong> <strong>28</strong>, 2012 F-140 Agent Broker Compensation Report


Item<br />

#<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Field Name Length Position Description<br />

Numeric value representing the broker compensation cycle-year<br />

as of the report generation date:<br />

11<br />

Cycle-Year as<br />

of Report<br />

Generation Date<br />

3 298-300<br />

‘-1’ = no compensation cycle exists for this enrollment because the<br />

report generation date does not fall within the enrollment period.<br />

This occurs for both the prospective <strong>and</strong> retroactive enrollments.<br />

‘0’ = reporting date falls within the enrollment period but the<br />

compensation cycle completed in a prior year,<br />

'1' = first calendar year,<br />

'2' = second calendar year,<br />

'3' = third calendar year,<br />

'4' = fourth calendar year,<br />

'5' = fifth calendar year,<br />

'6' = sixth calendar year.<br />

Broad classification of Beneficiary's immediately prior Plan-type:<br />

"None" = no prior Plan,<br />

"MA" = non-drug MA Plan,<br />

12 Prior Plan Type 7 301-307<br />

"MAPD" = MA Plan offering prescription drugs,<br />

"COST" = Non-drug <strong>Medicare</strong> COST Plan,<br />

"COST/PD" = <strong>Medicare</strong> COST Plan providing prescription drugs,<br />

"PDP" = PDP <strong>and</strong> sometimes representative of a POS transaction,<br />

"PACE" = Program for All-inclusive Care of the Elderly<br />

13 Filler 79 308-386 Spaces<br />

Total Length = 386<br />

<strong>December</strong> <strong>28</strong>, 2012 F-141 Agent Broker Compensation Report


Plan Communications User Guide Appendices, Version 6.3<br />

F.<strong>28</strong> Monthly <strong>Medicare</strong> Second Payer (MSP) Information Data File<br />

The Monthly MSP Information data file is sent directly to <strong>Plans</strong> on the first Monday after the<br />

MARx month-end processing completes. This file contains a subset of information to assist <strong>Plans</strong><br />

with reconciling payment; the full monthly MSP COB file distributed at the beginning of each<br />

month contains more detail.<br />

F.<strong>28</strong>.1<br />

Header Record<br />

FIELD NAME SIZE POSITION TYPE COMMENTS<br />

Header Code 8 1-8 CHAR<br />

File/record identification purposes only,<br />

'CMSMSPIH'.<br />

Sending Entity 3 9-11 CHAR Hard Coded as 'MBD'<br />

File Creation Date 8 12-19 ZD CCYYMMDD – Format<br />

Filler 481 20-500 CHAR All spaces<br />

Total Length = 500<br />

F.<strong>28</strong>.2<br />

Detail Record<br />

FIELD NAME SIZE POSITION TYPE COMMENTS<br />

RRB-HIC-NUM 12 1-12 CHAR Use RRB_HIC_NUM if available; else, use<br />

first 9 bytes mapped to BENE_CAN_NUM;<br />

next 2 bytes mapped to BIC_CD ; 12th byte is<br />

a space<br />

Date of Birth 8 13-20 CHAR CCYYMMDD FORMAT<br />

Gender Code 1 21 CHAR<br />

Direct Mapping: 0 = Unknown, 1 = Male, 2 =<br />

Female<br />

Contract Number 5 22-26 CHAR Direct Mapping<br />

PBP Number 3 27-29 CHAR Direct Mapping<br />

MSP Coverage<br />

Effective Date<br />

8 30-37 INT CCYYMMDD FORMAT<br />

MSP Coverage<br />

Termination Date<br />

8 38-45 INT CCYYMMDD FORMAT<br />

Primary Insurance<br />

Code<br />

COB Contractor<br />

Number<br />

1 46 CHAR<br />

Convert as follows:<br />

12…A (Working Aged)<br />

13…B (ESRD)<br />

43…G (Disabled)<br />

5 47-51 CHAR Direct Mapping<br />

Insurer Name 32 52-83 CHAR Direct Mapping<br />

Insurer Address Line 1 32 84-115 CHAR Direct Mapping<br />

Insurer Address Line 2 32 116-147 CHAR Direct Mapping<br />

Insurer City name 15 148-162 CHAR Direct Mapping<br />

Insurer State Code 2 163-164 CHAR Direct Mapping<br />

Insurer Zip Code 9 165-173 CHAR Direct Mapping<br />

Policy Number 17 174-190 CHAR Direct Mapping<br />

Filler 310 191-500 CHAR Hard Coded as Spaces<br />

Total Length = 500<br />

<strong>December</strong> <strong>28</strong>, 2012 F-142 MSP Information Data File


F.<strong>28</strong>.3<br />

Trailer Record<br />

Plan Communications User Guide Appendices, Version 6.3<br />

FIELD NAME SIZE POSITION SIZE COMMENTS<br />

Trailer Code 8 1-8 CHAR<br />

File/record identification purposes only,<br />

'CMSMSPIT'.<br />

Sending Entity 3 9-11 CHAR Hard Coded as 'MBD'<br />

File Creation Date 8 12-19 ZD CCYYMMDD – Format<br />

Detail Record Count 9 20-<strong>28</strong> ZD<br />

Number of detail records, excluding header<br />

<strong>and</strong> trailer<br />

Filler 472 29-500 CHAR All spaces<br />

Total Length = 50<br />

<strong>December</strong> <strong>28</strong>, 2012 F-143 MSP Information Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.29 Other Health Coverage Information Data File<br />

CMS provides <strong>Plans</strong> with a file listing the beneficiaries who are enrolled in their Plan(s) where<br />

<strong>Medicare</strong> is listed secondary. As a monthly report, this vehicle provides <strong>Plans</strong> with regular<br />

updates to the MSP data.<br />

F.29.1<br />

Header Record<br />

Field Size Position Type Comments<br />

Header Code 8 1-8 CHAR<br />

File/record identification purposes only,<br />

'CMSMSPDH'.<br />

Sending Entity 8 9-16 CHAR Hard Coded as 'MBD ' (MBD + 5 spaces)<br />

File Creation Date 8 17-24 ZD CCYYMMDD – Format<br />

Filler 10976 25-11000 CHAR All spaces<br />

Total Length = 11,000<br />

F.29.2<br />

Detail Record<br />

Field Size Position Type Comments<br />

CAN 12 1-12 CHAR Beneficiary HICN/RRB number<br />

BIC 2 13-14 CHAR Beneficiary HICN/RRB number<br />

MSP Data – Occurs 17 times<br />

Delete Indicator 1 15 CHAR D – Occurrence in process of deletion<br />

Validity Indicator 1 16 CHAR<br />

MSP Code 1 17 CHAR<br />

Validity of MSP Coverage<br />

Y = Beneficiary has MSP Coverage<br />

N = Beneficiary does not have MSP Coverage<br />

MSP Coverage Type<br />

A-Working Aged<br />

B-ESRD<br />

D-No-Fault<br />

E-Workers' Compensation<br />

F-Federal (Public Health)<br />

G-Disabled<br />

H-Black Lung<br />

I-Veterans<br />

L-Liability<br />

W-Worker’s Compensation Set Aside<br />

Contractor Number 5 18-22 CHAR Identifies Contractor Establishing Entry<br />

Data Entry Added 8 23-30 ZD Date Entry created (CCYYMMDD)<br />

Updating Contractor 5 31-35 CHAR Identifies Contractor that updated entry<br />

<strong>December</strong> <strong>28</strong>, 2012 F-144 Other Health Coverage<br />

Information Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Type Comments<br />

Maintenance Date 8 36-43 ZD Date Entry created (CCYYMMDD)<br />

CWF Occurrence Number 2 44-45 ZD Number of occurrence as provided by CWF<br />

Filler 4 46 – 49 CHAR Spaces<br />

Insurer Type 1 50 CHAR<br />

Type of Primary Insurer<br />

A – M, Spaces<br />

Insurer’s Name 32 51-82 CHAR Primary Insurer’s Name<br />

Insurer’s Address -1 32 83-114 CHAR Primary Insurer’s Address Line 1<br />

Insurer’s Address -2 32 115-146 CHAR Primary Insurer’s Address Line 2<br />

Insurer’s City 15 147-161 CHAR Primary Insurer’s City<br />

Insurer’s State Code 2 162-163 CHAR Primary Insurer’s State Code<br />

Insurer’s Zip Code 9 164-172 CHAR Primary Insurer’s Zip Code<br />

Policy Number 17 173-189 CHAR Primary Insurance Policy Number of Insured<br />

MSP Effective Date 8 190-197 CHAR<br />

Effective Date of MSP Coverage<br />

(CCYYMMDD)<br />

MSP Termination 8 198-205 ZD<br />

Termination Date of MSP Coverage<br />

(CCYYMMDD)<br />

Patient Relationship 2 206-207 CHAR<br />

Relationship of Patient to Insured<br />

01-Patient is Ins<br />

02-Spouse<br />

03-Natural Child, Insured has Financial<br />

Responsibility<br />

04-Natural Child, Insured does not have<br />

Financial Responsibility<br />

05-Step Child<br />

06-Foster Child<br />

07-Ward of the Court<br />

08-Employee<br />

09-Unknown<br />

10-H<strong>and</strong>icapped Dependent<br />

11-Organ Donor<br />

12-Cadaver Donor<br />

13-Gr<strong>and</strong>child<br />

14-Niece/Nephew<br />

15-Injured Plaintiff<br />

16-Sponsored Dependent<br />

17-Minor Dependent of a Minor Dependent<br />

18-Parent<br />

19-Gr<strong>and</strong>parent dependent<br />

20-Life Partner<br />

Subscriber First Name 9 208-216 CHAR First Name of Policy Holder<br />

Subscriber Last Name Policy<br />

holder<br />

16 217-232 CHAR Last Name of Policy Holder<br />

<strong>December</strong> <strong>28</strong>, 2012 F-145 Other Health Coverage<br />

Information Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Type Comments<br />

Employee ID Number 12 233-244 CHAR Employee ID Number assigned by Employer<br />

Source Code 2 245-246 CHAR<br />

First Byte of Source Code:<br />

A-Claim Processing<br />

B-IRS/SSA/CMS Data Match<br />

C-First Claim Development<br />

D-IRS/SSA/CMS Data Match II<br />

E-Black Lung (DOL)<br />

F-Veterans (VA)<br />

G-Other Data Matches<br />

H-Worker's Compensation<br />

I-Notified by Beneficiary<br />

J-Notified by Provider<br />

K-Notified by Insurer<br />

L-Notified by Employer<br />

M-Notified by Attorney<br />

N-Notified by Group Health Plan/Primary<br />

Payer<br />

O-Initial Enrollment Questionnaire<br />

P-HMO Rate Cell Adjustment<br />

Q-Voluntary Insurer Reporting<br />

R-Office of Personnel Management Data<br />

Match<br />

S-Miscellaneous Reporting<br />

T-IRS/SSA/CMS Data Match III<br />

U-IRS/SSA/CMS Data Match IV<br />

V-IRS/SSA/CMS Data Match V<br />

W-IRS/SSA/CMS Data Match VI<br />

X-Self reports<br />

Y-411.25<br />

SPACES-Unknown<br />

Second Byte of Source Code:<br />

0-COB Contractor<br />

1-Initial Enrollment questionnaire<br />

2-IRS/SSA/CMS/data match<br />

3-HMO Rate cell<br />

4-Litigation settlement<br />

5-Employer Voluntary Reporting<br />

6-Insurer Voluntary Reporting<br />

7-First claim development<br />

8-Trauma Code development<br />

9-Secondary claims investigation<br />

Employee Data Code 1 247 CHAR<br />

To Whom the Employment Data Applies:<br />

P-Patient<br />

S-Spouse<br />

M-Mother<br />

F-Father<br />

Employer Name 32 248-279 CHAR Employer providing coverage<br />

Employer’s Address1 32 <strong>28</strong>0-311 CHAR Employer’s Street Address 1<br />

Employer’s Address2 32 312-343 CHAR Employer’s Street Address 2<br />

<strong>December</strong> <strong>28</strong>, 2012 F-146 Other Health Coverage<br />

Information Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Type Comments<br />

Employer’s City 15 344-358 CHAR Employer’s City<br />

Employer’s State 2 359-360 CHAR Employer’s State<br />

Employer’s Zip Code 9 361-369 CHAR Employer’s Zip Code<br />

Insurance Group Number 20 370-389 CHAR Group Number Assigned by Primary Payer<br />

Insurance Group 17 390-406 CHAR Name of Group Plan<br />

Prepaid Health Plan Date 8 407-414 ZD<br />

Date Beneficiary notified that <strong>Medicare</strong> is<br />

secondary payer for services performed<br />

outside the prepaid health Plan when a prepaid<br />

health Plan provider can perform the services.<br />

(CCYYMMDD)<br />

Remarks Code -1 2 415-416 CHAR<br />

'1-3', '01-12', '20-26', '30-44', '50-62', '70-72',<br />

<strong>and</strong> spaces<br />

Remarks Code -2 2 417-418 CHAR<br />

'1-3', '01-12', '20-26', '30-44', '50-62', '70-72',<br />

<strong>and</strong> spaces<br />

Remarks Code -3 2 419-420 CHAR<br />

'1-3', '01-12', '20-26', '30-44', '50-62', '70-72',<br />

<strong>and</strong> spaces<br />

Diagnosis Codes – Occurs 25 Times<br />

Diagnosis Code Indicator 1 421 CHAR ‘9’ – ICD-9 code default<br />

Diagnosis Code 7 422-4<strong>28</strong> CHAR Diagnosis code ICD-9<br />

Diagnosis Code Occurrence 2 8 429-436 CHAR<br />

Diagnosis Code Occurrence 3 8 437-444 CHAR<br />

Diagnosis Code Occurrence 4 8 445-452 CHAR<br />

Diagnosis Code Occurrence 5 8 453-460 CHAR<br />

Diagnosis Code Occurrence 6 8 461-468 CHAR<br />

Diagnosis Code Occurrence 7 8 469-476 CHAR<br />

Diagnosis Code Occurrence 8 8 477-484 CHAR<br />

Diagnosis Code Occurrence 9 8 485-492 CHAR<br />

Diagnosis Code Occurrence<br />

10<br />

8 493-500 CHAR<br />

Diagnosis Code Occurrence<br />

11<br />

8 501-508 CHAR<br />

Diagnosis Code Occurrence<br />

12<br />

8 509-516 CHAR<br />

Diagnosis Code Occurrence<br />

13<br />

8 517-524 CHAR<br />

Diagnosis Code Occurrence<br />

14<br />

8 525-532 CHAR<br />

Diagnosis Code Occurrence<br />

15<br />

8 533-540 CHAR<br />

Diagnosis Code Occurrence<br />

16<br />

8 541-548 CHAR<br />

Diagnosis Code Occurrence<br />

17<br />

8 549-556 CHAR<br />

Diagnosis Code Occurrence<br />

18<br />

8 557-564 CHAR<br />

Diagnosis Code Occurrence<br />

19<br />

8 565-572 CHAR<br />

Diagnosis Code Occurrence 8 573-580 CHAR<br />

<strong>December</strong> <strong>28</strong>, 2012 F-147 Other Health Coverage<br />

Information Data File


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Type Comments<br />

20<br />

Diagnosis Code Occurrence<br />

21<br />

8 581-588 CHAR<br />

Diagnosis Code Occurrence<br />

22<br />

8 589-596 CHAR<br />

Diagnosis Code Occurrence<br />

23<br />

8 597-604 CHAR<br />

Diagnosis Code Occurrence<br />

24<br />

8 605-612 CHAR<br />

Diagnosis Code Occurrence<br />

25<br />

8 613-620 CHAR<br />

Payer ID 10 621-630 CHAR<br />

MSP Data Occurrence<br />

Number 2<br />

616 631-1246 CHAR<br />

MSP Data Occurrence<br />

Number 3<br />

616 1247-1862 CHAR<br />

MSP Data Occurrence<br />

Number 4<br />

616 1863-2478 CHAR<br />

MSP Data Occurrence<br />

Number 5<br />

616 2479-3094 CHAR<br />

MSP Data Occurrence<br />

Number 6<br />

616 3095-3710 CHAR<br />

MSP Data Occurrence<br />

Number 7<br />

616 3711-4326 CHAR<br />

MSP Data Occurrence<br />

Number 8<br />

616 4327-4942 CHAR<br />

MSP Data Occurrence<br />

Number 9<br />

616 4943-5558 CHAR<br />

MSP Data Occurrence<br />

Number 10<br />

616 5559-6174 CHAR<br />

MSP Data Occurrence<br />

Number 11<br />

616 6175-6790 CHAR<br />

MSP Data Occurrence<br />

Number 12<br />

616 6791-7406 CHAR<br />

MSP Data Occurrence<br />

Number 13<br />

616 7407-8022 CHAR<br />

MSP Data Occurrence<br />

Number 14<br />

616 8023-8638 CHAR<br />

MSP Data Occurrence<br />

Number 15<br />

616 8639-9254 CHAR<br />

MSP Data Occurrence<br />

Number 16<br />

616 9255-9870 CHAR<br />

MSP Data Occurrence<br />

Number 17<br />

616 9871-10486 CHAR<br />

Filler 515<br />

10487-<br />

11000<br />

Total Length = 11,000<br />

<strong>December</strong> <strong>28</strong>, 2012 F-148 Other Health Coverage<br />

Information Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.29.3<br />

Trailer Record<br />

FIELD NAME SIZE POSITION SIZE COMMENTS<br />

Trailer Code 8 1-8 CHAR<br />

Sending Entity 8 9-16 CHAR<br />

File/record identification purposes only,<br />

'CMSMSPDT'.<br />

Identifies the sending entity, ‘MDB “ (MBD<br />

+ 5 spaces”<br />

File Creation Date 8 17-24 ZD CCYYMMDD – Format<br />

Record Count 7 25-31 ZD Total number of detail records<br />

Filler 10969 32-11000 CHAR All spaces<br />

Total Length = 11,000<br />

<strong>December</strong> <strong>28</strong>, 2012 F-149 Other Health Coverage<br />

Information Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.30 No Premium Due Data File Layout<br />

MA enrollees who elect optional supplemental benefits may also elect SSA premium<br />

withholding. In mid-November, MARx begins preparing the premium records for the next year.<br />

Since MARx cannot anticipate which optional premiums an enrollee may elect for next year, an<br />

enrollee only paying optional premiums may convert from “SSA Premium Withholding” status<br />

in one year to “No Premium Due” status for the next year. <strong>Plans</strong> should use the No Premium Due<br />

Data File to identify enrollees in a “No Premium Due” status for the next year. <strong>Plans</strong> should<br />

review the report <strong>and</strong> submit both a Part C Premium Update (TC 78) to update the Part C<br />

premium Amount, <strong>and</strong> a PPO Update (TC 75) to request SSA Withholding Status, for enrollees<br />

who are renewing both elections for the next year.<br />

Field Size Position Description<br />

HICN 12 1-12 Health Insurance Claim Number<br />

Surname 12 13-24 Beneficiary Surname<br />

First Name 7 25-31 Beneficiary Given Name<br />

Middle Initial 1 32 Beneficiary Middle Initial<br />

Gender Code 1 33 Beneficiary Gender Identification Code<br />

‘0’ = Unknown;<br />

‘1’ = Male;<br />

‘2’ = Female.<br />

Date of Birth 8 34-41 YYYYMMDD – Format<br />

Filler 1 42 Space<br />

Contract Number 5 43-47 Plan Contract Number<br />

State Code 2 48-49 Spaces<br />

County Code 3 50-52 Spaces<br />

Disability Indicator 1 53 Space<br />

Hospice Indicator 1 54 Space<br />

Institutional/NHC Indicator 1 55 Space<br />

ESRD Indicator 1 56 Space<br />

TRC 3 57-59 TRC Defaulted to ‘267’<br />

Transaction Code 2 60-61 TC Defaulted to ‘01’ for special reports<br />

Entitlement Type Code 1 62 Space<br />

Effective Date 8 63-70 YYYYMMDD – Format; Example: 20110101 (set to first<br />

of January of the upcoming year)<br />

WA Indicator 1 71 Space<br />

PBP ID 3 72-74 PBP number<br />

Filler 1 75 Space<br />

Transaction Date 8 76-83 YYYYMMDD – Format; Set to the report generation date.<br />

UI Initiated Change Flag 1 84 Space<br />

FILLER 12 85-96 Spaces<br />

District Office Code 3 97-99 Spaces<br />

Previous Part D Contract/PBP 8 100-107 Spaces<br />

for TrOOP Transfer.<br />

End Date 8 108-115 Spaces<br />

Source ID 5 116-120 Spaces<br />

Prior PBP ID 3 121-123 Spaces<br />

Application Date 8 124-131 Spaces<br />

<strong>December</strong> <strong>28</strong>, 2012 F-150 No Premium Due Data<br />

File Layout


Plan Communications User Guide Appendices, Version 6.3<br />

Field Size Position Description<br />

UI User Organization<br />

2 132-133 Spaces<br />

Designation<br />

Out of Area Flag 1 134 Space<br />

Segment Number 3 135-137 Further definition of PBP by geographic boundaries;<br />

Default to ‘000’ when blank.<br />

Part C Beneficiary Premium 8 138-145 Part C Premium Amount: Since this report is only reporting<br />

on Beneficiaries that have No Premium Due, by definition,<br />

this amount is zero<br />

Part D Beneficiary Premium 8 146-153 Part D Premium Amount: Since this report is only reporting<br />

on Beneficiaries that have No Premium Due, by definition,<br />

this amount is zero<br />

Election Type 1 154 Space<br />

Enrollment Source 1 155 Space<br />

Part D Opt-Out Flag 1 156 Space<br />

Premium Withhold Option/Parts 1 157 ‘N’ = No premium applicable;<br />

C-D<br />

Number of Uncovered Months 3 158-160 Spaces<br />

Creditable Coverage Flag 1 161 Space<br />

Employer Subsidy Override Flag 1 162 Space<br />

Processing Timestamp 15 163-177 The report generation time. Format: HH.MM.SS.SSSSSS<br />

Filler 20 178-197 Spaces<br />

Secondary <strong>Drug</strong> Insurance Flag 1 198 Space<br />

Secondary Rx ID 20 199-218 Spaces<br />

Secondary Rx Group 15 219-233 Spaces<br />

EGHP 1 234 Space<br />

Part D LIPS Level 3 235-237 Spaces<br />

Low-Income Co-Pay Category 1 238 Space<br />

Low-Income Period Effective 8 239-246 Spaces<br />

Date<br />

Part D LEP Amount 8 247-254 Spaces<br />

Part D LEP Waived Amount 8 255-262 Spaces<br />

Part D LEP Subsidy Amount 8 263-270 Spaces<br />

Low-Income Part D Premium<br />

Subsidy Amount<br />

8 271-<br />

278<br />

Spaces<br />

Part D Rx BIN 6 279-<strong>28</strong>4 Spaces<br />

Part D Rx PCN 10 <strong>28</strong>5-294 Spaces<br />

Part D Rx Group 15 295-309 Spaces<br />

Part D Rx ID 20 310-329 Spaces<br />

Secondary Rx BIN 6 330-335 Spaces<br />

Secondary Rx PCN 10 336-345 Spaces<br />

De Minimis Differential Amount 8 346-353 Spaces<br />

MSP Status Flag 1 354 Space<br />

Low Income Period End Date 8 355-362 Spaces<br />

LIS Source Code 1 363 Space<br />

Enrollee Type Flag, PBP Level 1 364 Space<br />

Application Date Indicator 1 365 Space<br />

Filler 135 366-500 Spaces<br />

Total Length = 500<br />

<strong>December</strong> <strong>28</strong>, 2012 F-151 No Premium Due Data<br />

File Layout


Plan Communications User Guide Appendices, Version 6.3<br />

F.31 Failed Payment Reply Report (FPRR) Data File<br />

Along with the other monthly payment reports, MARx generates the FPRR. If payment<br />

calculation for a beneficiary cannot complete, MARx identifies the beneficiary <strong>and</strong> time period<br />

for which the payment calculation is not performed. The records in this file are the same length<br />

as those in the TRR <strong>and</strong> contain their own unique reply codes.<br />

Field Size Position Description<br />

1.HICN 12 1-12 Beneficiary’s HICN, included with PRC 264<br />

2. Surname 12 13-24 Beneficiary’s last name, included with PRC 264<br />

3. First Name 7 25-31 Beneficiary’s given name, included with PRC 264<br />

4. Middle Name 1 32 First initial of beneficiary’s middle name, included with PRC 264<br />

5. Gender Code 1 33 Beneficiary’s gender identification code, included with TRC 264:<br />

‘0’ = Unknown, ‘1’ = Male, ‘2’ = Female<br />

6. Date of Birth 8 34-41 Beneficiary’s birth date, formatted YYYYMMDD, included with<br />

PRC 264<br />

7. FILLER 1 42 Spaces<br />

8. Contract Number 5 43-47 Plan Contract Number, included with TRC 000 <strong>and</strong> TRC 264<br />

9. State Code 2 48-49 Beneficiary’s residence SSA state code, included with TRC 264;<br />

otherwise, spaces if not available<br />

10. County Code 3 50-52 Beneficiary’s residence SSA county code, included with TRC 264;<br />

otherwise, spaces if not available<br />

11. FILLER 4 53-56 Spaces<br />

12. Payment Reply<br />

Code<br />

3 57-59 “000” = no missing payments; “264” = payment not yet completed<br />

“299” = Correction to Previously Failed Payment<br />

13. FILLER 3 60-62 Spaces<br />

14 Effective Date 8 63-70 Enrollment effective date, formatted YYYYMMDD <strong>and</strong> included<br />

with TRC 264<br />

15. FILLER 1 71 Spaces<br />

16. PBP ID 3 72-74 PBP number, included with both TRC 000 <strong>and</strong> TRC 264<br />

17. FILLER 1 75 Spaces<br />

18. Transaction Date 8 76-83 Report generation date, formatted YYYYMMDD <strong>and</strong> included with<br />

both TRC 000 <strong>and</strong> TRC 264<br />

19. FILLER 1 84 Spaces<br />

20. CPM 12 85- 96 CPM, formatted YYYYMM, left justified with six spaces<br />

completing the field, <strong>and</strong> included with both TRC 000 <strong>and</strong> TRC<br />

264, <strong>and</strong> TRC 299<br />

21. FILLER 38 97-134 Spaces<br />

22. Segment Number 3 135-137 Segment in PBP, included with TRC 264<br />

23. FILLER 25 138-162 Spaces<br />

24. Processing<br />

Timestamp<br />

15 163-177 Report generation time, formatted HH.MM.SS.SSSSSS <strong>and</strong><br />

included with both TRC 000 <strong>and</strong> TRC 264<br />

25. FILLER 188 178-365 Spaces<br />

26. PRC Short Name 15 366-380 TRC short name associated with TRC 000 is “NO REPORT,” with<br />

TRC 264 is “NO PAYMENT,” <strong>and</strong> with TRC 299 is “RESTORED<br />

PYMT.” Text is left justified with following spaces completing the<br />

field.<br />

27. FILLER 120 381-500 Spaces<br />

Total Length = 500<br />

<strong>December</strong> <strong>28</strong>, 2012 F-152 FPRR Data File


Plan Communications User Guide Appendices, Version 6.3<br />

F.32 Missing Payment Exception Report (MPER) Data File<br />

Along with the other monthly payment reports, MARx generates a Plan communication in a<br />

report named the MPER. If payment calculation for a beneficiary cannot complete, MARx<br />

identifies the beneficiary <strong>and</strong> time period for which the payment calculation was not performed.<br />

Item Field Size Position Description<br />

1 Claim Number 12 1 – 12 Beneficiary’s HICN, included with TRC-264<br />

2 Surname 12 13 – 24 Beneficiary’s last name, included only with TRC-264<br />

3 First Name 7 25 – 31 Beneficiary’s given name, included when TRC-264<br />

4 Middle Name 1 32 First initial of beneficiary’s middle name, included with TRC-264<br />

5 Sex Code 1 33 Beneficiary’s gender identification code, included with TRC-264:<br />

‘0’ = Unknown<br />

‘1’ = Male<br />

‘2’ = Female<br />

6 Date of Birth 8 34 – 41 Beneficiary’s birth date, formatted YYYYMMDD, included with<br />

TRC-264<br />

7 FILLER 1 42 Spaces<br />

8 Contract Number 5 43 – 47 Plan Contract Number, included with both TRC-000 <strong>and</strong> TRC-<br />

264<br />

9 State Code 2 48 – 49 Beneficiary’s residence SSA state code, included with TRC-264;<br />

otherwise, spaces if not available<br />

10 County Code 3 50 – 52 Beneficiary’s residence SSA county code, included with TRC-<br />

264; otherwise, spaces if not available<br />

11 FILLER 4 53-56 Spaces<br />

12 TRC 3 57 – 59 “000” = no missing payments<br />

“264” = payment not completed<br />

13 FILLER 3 60 - 62 Spaces<br />

14 Effective Date 8 63 – 70 Enrollment effective date, formatted YYYYMMDD <strong>and</strong> include<br />

with TRC-264<br />

15 FILLER 1 71 Spaces<br />

16 PBP ID 3 72 – 74 PBP number, included with both TRC-000 <strong>and</strong> TRC-264<br />

17 FILLER 1 75 Spaces<br />

18 Transaction Date 8 76 – 83 Report generation date, formatted YYYYMMDD <strong>and</strong> included<br />

with both TRC-000 <strong>and</strong> TRC-264<br />

19 FILLER 1 84 Spaces<br />

20 Current Payment<br />

Month<br />

12 85 – 96 CPM formatted YYYYMM, left justified with six spaces<br />

completing the field, <strong>and</strong> included with both TRC-000 <strong>and</strong> TRC-<br />

264<br />

21 FILLER 38 97 – 134 Spaces<br />

22 Segment Number 3 135 – 137 Segment in PBP, included with TRC-264<br />

23 FILLER 25 138 – 162 Spaces<br />

24 Processing<br />

Timestamp<br />

15 163 – 177 Report generation time, formatted HH.MM.SS.SSSSSS <strong>and</strong><br />

included with both TRC-000 <strong>and</strong> TRC-264<br />

25 FILLER 188 178 – 365 Spaces<br />

26 TRC Short Name 15 366 - 380 TRC short name associated with TRC-000 is “NO REPORT” <strong>and</strong><br />

with TRC_264 is “NO PAYMENT.” Text is left justified with<br />

following spaces completing the field.<br />

27 FILLER 120 381 - 500 Spaces<br />

Total Length = 500<br />

<strong>December</strong> <strong>28</strong>, 2012 F-153 MPER Data File


Plan Communications User Guide Appendices, Version 6.3<br />

G: Screen Hierarchy<br />

The Common User Interface (UI) screens are accessed via the drill-down method of navigation.<br />

Functions are grouped together under a common menu item. For example, most of the<br />

Beneficiary-specific information is found under the Beneficiary menu item. Table G-1 lists the<br />

names of the Common UI screens accessible to Managed Care Organizations (MCOs) <strong>and</strong> their<br />

screen numbers, for reference only.<br />

Table G-1: Screen Lookup Table<br />

Screen Name<br />

Logon, Logoff, <strong>and</strong> Welcome Screens<br />

MARx Logout<br />

User Security Role Selection<br />

Welcome<br />

MARx Calendar<br />

Beneficiaries Screens<br />

Beneficiaries: Find<br />

Beneficiaries: Search Results<br />

Beneficiary Detail: Snapshot<br />

Beneficiary Detail: Enrollment<br />

Beneficiary Detail: Status<br />

Beneficiary Detail: Payments<br />

Beneficiary Detail: Adjustments<br />

Beneficiaries: New Enrollment<br />

Payment/Adjustment Detail<br />

Beneficiary Detail: Factors<br />

Beneficiaries: Update Enrollment<br />

Enrollment Detail<br />

Beneficiary Detail: Update Premiums<br />

Rx Insurance View<br />

Beneficiaries: Additional Update Enrollment<br />

Beneficiary Detail: Premiums<br />

Beneficiaries: Eligibility<br />

Beneficiary Detail: Utilization<br />

Part D AE-FE Opt-Out<br />

Beneficiary Detail: MSA Lump Sum<br />

Beneficiary Detail: Medicaid<br />

Beneficiary Detail: SSA/RRB Transaction Status<br />

Update Premium Withhold Collection<br />

Update SSA R&R<br />

Update Residence Address View<br />

Residence Address View<br />

Rx Insurance View<br />

Transactions Screens<br />

M002<br />

M101<br />

M105<br />

M201<br />

M202<br />

M203<br />

M204<br />

M205<br />

M206<br />

M207<br />

M212<br />

M215<br />

M220<br />

M221<br />

M222<br />

M226<br />

M2<strong>28</strong><br />

M230<br />

M231<br />

M232<br />

M233<br />

M234<br />

M235<br />

M236<br />

M237<br />

M240<br />

M241<br />

M242<br />

M243<br />

M244<br />

Screen Number<br />

<strong>December</strong> 30, 2012 G-1 Screen Hierarchy


Plan Communications User Guide Appendices, Version 6.3<br />

Screen Name<br />

Transactions: Batch Status<br />

Batch File Details<br />

Special Batch Approval Request<br />

View Special Batch File Request<br />

Payments Screens<br />

Payments: MCO<br />

Payments: MCO Payments<br />

Payments: Beneficiary<br />

Payments: Beneficiary Search Results<br />

Beneficiary Payment History<br />

Adjustment Detail<br />

Payments: Premiums <strong>and</strong> Rebates<br />

Reports Screens<br />

Reports: Find<br />

Reports: Search Results<br />

Screen Number<br />

M307<br />

M314<br />

M316<br />

M317<br />

M401<br />

M402<br />

M403<br />

M404<br />

M406<br />

M408<br />

M409<br />

M601<br />

M602<br />

<strong>December</strong> 30, 2012 G-2 Screen Hierarchy


Plan Communications User Guide Appendices, Version 6.3<br />

H: Validation Messages<br />

Table H-1 lists validation messages that appear directly on the screen during data<br />

entry/processing in the status line (the line just below the title line, as in Figure H-1).<br />

Figure H-1: Validation Message Placement on Screen<br />

These are common validation messages, not specific to a single screen but related to the fields<br />

that appear on many screens. Note that screen/function-specific messages appear in the section<br />

related to the specific function <strong>and</strong> are associated with the specific screen.<br />

Table H-1: Validation Messages<br />

Error Messages<br />

User must enter a contract number<br />

A contract number must start with an ‘E’, ‘H’, ‘R’,<br />

‘S’, ‘X,’ or ‘9’, followed by four characters<br />

User must enter a sex<br />

User must select a state<br />

Invalid Contract/PBP combination<br />

Invalid Contract/PBP/segment combination<br />

is invalid. Must have format<br />

(M)M/(D)D/YYYY<br />

User must enter <br />

PBP number must have three alphanumeric characters<br />

Please enter at least one of the required fields<br />

Please enter user ID or password<br />

Segment number must have three digits<br />

The claim number is not a valid SSA or RRB number,<br />

or CMS Internal number<br />

The last name contains invalid characters<br />

The user ID contains invalid characters<br />

You do not have access rights to this contract<br />

Suggested Action<br />

Enter the field specified by the message.<br />

Re-enter the field <strong>and</strong> follow the format indicated in the<br />

message.<br />

Enter the field specified by the message.<br />

Enter the field specified by the message.<br />

Check the combination <strong>and</strong> re-enter.<br />

Check the combination <strong>and</strong> re-enter.<br />

Re-enter the field <strong>and</strong> follow the format indicated in the<br />

message.<br />

Enter the field specified by the message.<br />

Re-enter the field <strong>and</strong> follow the format indicated in the<br />

message.<br />

Make sure to enter all the required fields.<br />

Make sure to enter one of the fields specified by the<br />

message.<br />

Re-enter the field <strong>and</strong> follow the format indicated in the<br />

message.<br />

Re-enter the field in SSA, RRB, or CMS Internal<br />

format.<br />

Re-enter the field using only letters, apostrophes,<br />

hyphens, or blanks.<br />

Re-enter the field <strong>and</strong> follow the format indicated in the<br />

message.<br />

First, make sure that the Contract # correctly is entered<br />

correctly. If not, re-enter it. If the user did, he/she<br />

should have rights to this contract; see the Security<br />

Administrator who can update the user profile for these<br />

rights.<br />

<strong>December</strong> <strong>28</strong>, 2012 H-1 Validation Messages


Plan Communications User Guide Appendices, Version 6.3<br />

THIS PAGE INTENTIONALLY BLANK<br />

<strong>December</strong> <strong>28</strong>, 2012<br />

ii


Plan Communications User Guide Appendices, Version 6.3<br />

I: Codes<br />

This appendix lists the numerical value <strong>and</strong> descriptions for codes that are highly visible to users.<br />

I.1 Transaction Codes<br />

Table I-1 lists the <strong>Medicare</strong> <strong>Advantage</strong> <strong>and</strong> <strong>Prescription</strong> <strong>Drug</strong> System (MARx) Transaction Codes <strong>and</strong> the description of each code.<br />

Table I-1: Transaction Codes<br />

Code<br />

Description<br />

01 MCO Correction<br />

30 Turn Bene-Level Demonstration Factor On (Demos Only)<br />

31 Turn Bene-Level Demonstration Factor Off (Demos Only)<br />

41 Update to Opt-Out Flag (Submitted by CMS)<br />

42 MMP Opt-Out Change (Submitted by 1-800 MEDICARE)<br />

51 Disenrollment (MCO or CMS)<br />

54 Disenrollment (Submitted by 1-800-MEDICARE)<br />

61 Enrollment<br />

72 4Rx Record Update<br />

73 NUNCMO Record Update<br />

74 EGHP s Record Update<br />

75 Premium Payment Option (PPO) Update<br />

76 Residence Address Record Update<br />

77 Segment ID Record Update<br />

78 Part C Premium Record Update<br />

79 Part D Opt-Out Record Update<br />

80 Cancellation Enrollment<br />

81 Cancellation Disenrollment<br />

82 MMP Enrollment Cancellation<br />

83 MMP Opt-Out Update<br />

<strong>December</strong> <strong>28</strong>, 2012 I-1 Transaction Codes (TCs)


Plan Communications User Guide Appendices, Version 6.3<br />

I.2 Transaction Reply Codes<br />

Table I-2 lists the reply codes returned for transactions found in Table I-1.<br />

Transaction Reply Code (TRC) Types:<br />

A - Accepted - A transaction is accepted <strong>and</strong> the requested action is applied (Example: enrollment or disenrollment)<br />

R - Rejected - A transaction is rejected due to an error or other condition. The requested action is not applied to the<br />

CMS System. The TRC indicates the reason for the transaction rejection. The Plan should analyze the<br />

rejection to validate the submitted transaction <strong>and</strong> to determine whether to resubmit the transaction with<br />

corrections.<br />

I -<br />

M -<br />

Informational - These replies accompany Accepted TRC replies <strong>and</strong> provide additional information about the<br />

transaction or Beneficiary. For example: If an enrollment transaction for a Beneficiary who is “out of<br />

area” is accepted, the Plan receives an accepted TRC (TRC 011) <strong>and</strong> an additional reply is included in<br />

the Transaction Reply Report (TRR) that gives the Plan the additional information that the Beneficiary<br />

is “Out of Area” (TRC 016).<br />

Maintenance - These replies provide information to <strong>Plans</strong> about the Beneficiaries enrolled in their <strong>Plans</strong>. They are sent<br />

in response to information received by CMS. For example: If CMS is informed of a change in a<br />

Beneficiary’s claim number, a reply is included in the Plan’s TRR with TRC 086, giving the Plan the<br />

new claim number.<br />

F - Failed - A transaction failed due to an error or other condition <strong>and</strong> the requested action did not occur. The TRC<br />

code indicates the reason for the transaction’s failure. The Plan should analyze the failed transaction <strong>and</strong><br />

determine whether to resubmit with corrections.<br />

Legend for Type: A = Accepted R = Rejected I = Informational M = Maintenance F = Failed<br />

<strong>December</strong> <strong>28</strong>, 2012 I-2 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Table I-2: Transaction Reply Codes<br />

Code Type Title Short Definition Definition<br />

000 I No Data to<br />

Report<br />

001 F Invalid<br />

Transaction<br />

Code<br />

002 F Invalid<br />

Correction<br />

Action Code<br />

003 F Invalid<br />

Contract<br />

Number<br />

NO REPORT<br />

BAD TRANS<br />

CODE<br />

BAD ACTION<br />

CODE<br />

BAD CONTRACT<br />

#<br />

This TRC can appear on both the Daily Transaction Reply Report (DTRR) <strong>and</strong> the Failed Payment<br />

Reply Report (FPRR) data files.<br />

On the TRR it indicates that none of the following occurred during the reporting period for the given<br />

contract/PBP, a beneficiary status change, user interface (UI) activity, or CMS or plan transaction<br />

processing. The reporting period is the span between the previous TRR <strong>and</strong> the current TRR.<br />

On the FPRR it indicates the presence of all prospective payments for the plan (contract/PBP), none<br />

are missing.<br />

Plan Action: None<br />

A transaction failed because the Transaction Code (field 16) contained an invalid value.<br />

Valid Transaction Code values are 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81. This transaction<br />

should be resubmitted with a valid Transaction Code.<br />

Note: Transaction Types 41 <strong>and</strong> 54 are valid but not submitted by the <strong>Plans</strong>.<br />

This TRC will be returned in the Batch Completion Status Summary (BCSS) Report along with the<br />

failed record <strong>and</strong> is not returned in the TRR.<br />

Plan Action: Correct the Transaction Code <strong>and</strong> resubmit if appropriate.<br />

A correction transaction (Transaction Type 01) failed because the supplied action code was an<br />

invalid value. The valid action code values are D, E, F <strong>and</strong> G. The transaction should be resubmitted<br />

with a valid action code.<br />

This TRC is returned in the Batch Completion Status Summary (BCSS) Report along with the failed<br />

record. This TRC is not returned in the TRR.<br />

Plan Action: Correct the Action Code <strong>and</strong> resubmit if appropriate.<br />

A transaction (Transaction Types 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) failed because<br />

CMS did not recognize the contract number.<br />

This TRC is returned in the BCSS Report along with the failed record. This TRC is not returned in<br />

the TRR.<br />

Plan Action: Correct the Contract Number <strong>and</strong> resubmit if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-3 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

004 R Beneficiary<br />

Name<br />

Required<br />

006 R Incorrect<br />

Birth Date<br />

007 R Invalid Claim<br />

Number<br />

008 R Beneficiary<br />

Claim<br />

Number Not<br />

Found<br />

NEED MEMB<br />

NAME<br />

BAD BIRTH<br />

DATE<br />

BAD HICN<br />

FORMAT<br />

CLAIM NOT<br />

FOUND<br />

A transaction (Transaction Types 01, 41, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) was rejected,<br />

because both of the beneficiary name fields (Surname <strong>and</strong> First Name) were blank. The<br />

beneficiary’s name must be provided. The transaction should be resubmitted with beneficiary name<br />

included.<br />

Plan Action: Populate the Beneficiary Name fields <strong>and</strong> resubmit if appropriate.<br />

A transaction (Transaction Types 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) was rejected<br />

because the Birth Date, while non-blank <strong>and</strong> formatted correctly as YYYYMMDD (year, month,<br />

<strong>and</strong> day), is before 1870 or greater than the current year. The system tried to identify the beneficiary<br />

with the remaining demographic information but could not.<br />

Note: A blank Birth Date does not result in TRC 006 but may affect the ability to identify the<br />

appropriate beneficiary. See TRC 009.<br />

Plan Action: Correct the Birth Date <strong>and</strong> resubmit if appropriate.<br />

A transaction (Transaction Types 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, <strong>and</strong> 81) was rejected,<br />

because the beneficiary claim number was not in a valid format.<br />

The valid format for a claim number could take one of two forms:<br />

HICN is an 11-position value, with the first 9 positions numeric <strong>and</strong> the last 2 positions<br />

alphanumeric.<br />

RRB is a 7 to 12 position value, with the first 1 to 3 positions alpha <strong>and</strong> the last 6 or 9<br />

positions numeric.<br />

Plan Action: Determine the correct claim number (HICN or RRB) for the beneficiary <strong>and</strong> resubmit<br />

the transaction if appropriate.<br />

A transaction (Transaction Types 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, <strong>and</strong> 81) was rejected,<br />

because a beneficiary with this claim number was not found. The transaction should be resubmitted<br />

with a valid claim number.<br />

Plan Action: Determine the correct claim number (HICN or RRB) for the beneficiary <strong>and</strong> resubmit<br />

the transaction if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-4 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

009 R No<br />

beneficiary<br />

match<br />

011 A Enrollment<br />

Accepted as<br />

Submitted<br />

013 A Disenrollmen<br />

t Accepted as<br />

Submitted<br />

NO BENE<br />

MATCH<br />

ENROLL<br />

ACCEPTED<br />

DISENROL<br />

ACCEPT<br />

A transaction (Transaction Types 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, <strong>and</strong> 81) attempted to<br />

process but the system was unable to find the beneficiary based on the identifying information<br />

submitted in the transaction.<br />

A HICN is required, along with a match on 3 of the following 4 fields: surname, first initial, date of<br />

birth <strong>and</strong> sex code.<br />

Plan Action: Correct the beneficiary identifying information <strong>and</strong> resubmit if appropriate.<br />

The new enrollment (Transaction Type 61) has been successfully processed. The effective date of<br />

the new enrollment is reported in TRR data record field 18.<br />

This is the definitive enrollment acceptance record. Other accompanying replies with different<br />

TRCs may give additional information about this enrollment.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

A disenrollment transaction (Transaction Type 51) has been successfully processed. The last day of<br />

the enrollment is reported in TRR data record fields 18 <strong>and</strong> 24.<br />

The disenrollment date is always the last day of the month.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record <strong>and</strong><br />

that the beneficiary’s disenrollment date matches the date in field 24. Take the appropriate actions<br />

as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-5 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

014 A Disenrollmen<br />

t Due to<br />

Enrollment in<br />

Another Plan<br />

015 A Enrollment<br />

Cancelled<br />

DISNROL-NEW<br />

MCO<br />

ENROLL<br />

CANCELED<br />

This TRC is returned on a reply with the successful processing of Transaction Type 51<br />

(disenrollment) <strong>and</strong> Transaction Type 61 (enrollment).<br />

The last day of the enrollment is reported in TRR data record fields 18 <strong>and</strong> 24. This date will<br />

always be the last day of the month.<br />

For the Transaction Type 51 transaction, the beneficiary has been disenrolled from this Plan because<br />

they were successfully enrolled in another Plan The Source ID (field <strong>28</strong>) contains the Contract<br />

number of the Plan that submitted the new enrollment which caused this disenrollment.<br />

For the Transaction Type 61 transaction, the TRC is issued whenever a retroactive enrollment runs<br />

into an existing enrollment that prevails according to application date edits. The Source ID (field <strong>28</strong>)<br />

contains the Contract number of the prevailing plan.<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary’s information<br />

matches the data included in the TRR record <strong>and</strong> that the beneficiary’s disenrollment date matches<br />

the date in field 24. Take the appropriate actions as per CMS enrollment guidance.<br />

An existing enrollment was cancelled. The effective date of the enrollment which has been<br />

cancelled is reported in the TRR data record Effective Date field (18). This is always a<br />

disenrollment Transaction Type 51.<br />

A cancellation may be the result of an action on the part of the beneficiary, CMS or another Plan.<br />

When an enrollment is cancelled, it means that the enrollment never occurred.<br />

Plan Action: Because it was cancelled, this entire enrollment that was scheduled to begin on the<br />

date in field 18 should be removed from the Plan’s enrollment records. Take the appropriate actions<br />

as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-6 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

016 I Enrollment<br />

Accepted,<br />

Out Of Area<br />

017 I Enrollment<br />

Accepted,<br />

Payment<br />

Default Rate<br />

018 A Automatic<br />

Disenrollmen<br />

t<br />

019 R Enrollment<br />

Rejected - No<br />

Part A & Part<br />

B Entitlement<br />

ENROLL-OUT<br />

AREA<br />

ENROLL-BAD<br />

SCC<br />

AUTO<br />

DISENROLL<br />

NO ENROLL-NO<br />

AB<br />

The beneficiary’s residence state <strong>and</strong> county codes placed the beneficiary outside of the Plan’s<br />

approved service area.<br />

This TRC provides additional information about a new enrollment or PBP change (Transaction<br />

Type 61) for which an acceptance was sent in a separate Transaction Reply record with an<br />

enrollment acceptance TRC. The Effective Date of the enrollment for which this information is<br />

pertinent is reported in TRR data record field 18.<br />

Plan Action: Investigate the apparent discrepancy <strong>and</strong> take the appropriate actions as per CMS<br />

enrollment guidance.<br />

CMS was unable to derive a valid state <strong>and</strong> county code for the beneficiary who has been<br />

successfully enrolled. Part C payment for this beneficiary is at the Plan bid rate with no geographic<br />

adjustment.<br />

This TRC provides additional information about a new enrollment or PBP change (Transaction<br />

Type 61) for which an acceptance was sent in a separate Transaction Reply with an enrollment<br />

acceptance TRC. The effective date of the new enrollment for which this information is pertinent is<br />

reported in TRR data record fields 18 <strong>and</strong> 24.<br />

Plan Action: Contact your CMS Central Office Health Insurance Specialist for assistance.<br />

The beneficiary has been disenrolled from the Plan. The last day of enrollment is reported in TRR<br />

data record fields 18 <strong>and</strong> 24. This date is always the last day of the month.<br />

The disenrollment may result from an action on the part of the beneficiary, CMS or another Plan.<br />

A TRR reply with this TRC is usually accompanied by one or more replies, which make the reason<br />

for automatic disenrollment evident. For example, in the case of beneficiary death, the reply with<br />

TRC 018 is accompanied by two replies with TRC 090.<br />

Plan Action: Update the Plan’s records to reflect the disenrollment using the date in field 24. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

A submitted enrollment or PBP change transaction (Transaction Type 61) was rejected because the<br />

beneficiary does not have <strong>Medicare</strong> entitlement as of the effective date of the transaction.<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-7 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

020 R Enrollment<br />

Rejected -<br />

Under 55<br />

022 A Transaction<br />

Accepted,<br />

Claim<br />

Number<br />

Change<br />

023 A Transaction<br />

Accepted,<br />

Name<br />

Change<br />

NO ENROLL-<br />

NOT55<br />

NEW HICN<br />

NEW NAME<br />

A submitted enrollment or PBP change transaction (Transaction Type 61) for a PACE plan was<br />

rejected because the beneficiary is not yet 55 years of age.<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

A transaction (Transaction Types 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) has been successfully<br />

processed. The effective date of the transaction is shown in TRR data file field 18.<br />

Additionally, the claim number for this beneficiary has changed. The new claim number is in TRR<br />

data file field 1 <strong>and</strong> the old claim number is reported in field 24.<br />

For enrollment acceptance (Transaction Type 61), TRC 022 is reported in lieu of TRC 011. Other<br />

accompanying replies with different TRCs may give additional information about this enrollment.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS guidance. Change the beneficiary’s claim number in the Plan’s<br />

records. Any future submitted transactions for this beneficiary must use the new claim number.<br />

A transaction (Transaction Types 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) has been successfully<br />

processed. The effective date of the transaction is reported in TRR data record field 18.<br />

Additionally, the beneficiary’s name has changed. The new name is reported in TRR data file<br />

fields 2, 3 <strong>and</strong> 4.<br />

For enrollment acceptance (Transaction Type 61), TRC 023 is reported in lieu of TRC 011. Other<br />

accompanying replies with different TRCs may give additional information about this enrollment.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance. Change the beneficiary’s name in the<br />

Plan’s records. To ensure accurate identification of the beneficiary, future submitted transactions<br />

for this beneficiary should use the new name.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-8 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

025 A Disenrollmen<br />

t Accepted,<br />

Claim<br />

Number<br />

Change<br />

026 A Disenrollmen<br />

t Accepted,<br />

Name<br />

Change<br />

032 R Transaction<br />

Rejected,<br />

Beneficiary<br />

Not Entitl<br />

Part B<br />

DISROL-NEW<br />

HICN<br />

DISROL-NEW<br />

NAME<br />

MEMB HAS NO B<br />

A disenrollment transaction (Transaction Type 51) submitted by the Plan has been successfully<br />

processed. The effective date of the disenrollment is reported in TRR data file field 18. The<br />

disenrollment date will always be the last day of the month.<br />

Additionally, the claim number for this beneficiary has changed. The new claim number is in TRR<br />

data file field 1 <strong>and</strong> the old claim number is reported in field 24.<br />

Plan Action: Update the Plan’s records to reflect the disenrollment using the date in field 24. Take<br />

the appropriate actions as per CMS enrollment guidance. Change the beneficiary’s claim number in<br />

the Plan’s records. Future submitted transactions for this beneficiary must use the new claim<br />

number.<br />

A disenrollment transaction (Transaction Type 51) submitted by the Plan has been successfully<br />

processed. The effective date of the disenrollment is reported in the TRR data record field 18. The<br />

disenrollment date will always be the last day of the month.<br />

Additionally, The beneficiary’s name has changed. The new name is reported in TRR data file<br />

fields 2, 3 <strong>and</strong> 4 <strong>and</strong> in the corresponding columns in the printed report.<br />

Plan Action: Update the Plan’s records to reflect the disenrollment using the date in field 24. Take<br />

the appropriate actions as per CMS enrollment guidance. Change the beneficiary’s name in the<br />

Plan’s records. To ensure accurate identification of the beneficiary, future submitted transactions<br />

for this beneficiary should use the new name.<br />

This TRC is returned for an enrollment or PBP change transaction (Transaction Type 61) or a<br />

disenrollment cancellation transaction (Transaction Type 81) [enrollment reinstatement] . Part B<br />

entitlement is required for enrollment in a MCO. (MA, MAPD, HCPP, Cost 1, Cost 2 or Demos).<br />

TC61 – transaction was rejected because the submitted enrollment date is outside the<br />

beneficiary’s Part B entitlement period<br />

TC81 – transaction was rejected because the enrollment reinstatement period is outside the<br />

beneficiary’s Part B entitlement period<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-9 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

033 R Transaction<br />

Rejected,<br />

Beneficiary<br />

Not Entitl<br />

Part A<br />

034 R Enrollment<br />

Rejected,<br />

Beneficiary is<br />

Not Age 65<br />

035 R Enrollment<br />

Rejected,<br />

Beneficiary is<br />

in Hospice<br />

036 R Transaction<br />

Rejected,<br />

Beneficiary is<br />

Deceased<br />

MEMB HAS NO A<br />

MEMB NOT AGE<br />

65<br />

MEMB IN<br />

HOSPICE<br />

MEMB<br />

DECEASED<br />

This TRC is returned for an enrollment or PBP change transaction (Transaction Type 61) or a<br />

disenrollment cancellation transaction (Transaction Type 81) [enrollment reinstatement] . Part A<br />

entitlement is required for enrollment in a MCO (MA, MAPD, or Demos).<br />

TC61 – transaction was rejected because the submitted enrollment date is outside the<br />

beneficiary’s Part A entitlement period<br />

TC81 – transaction was rejected because the enrollment reinstatement period is outside the<br />

beneficiary’s Part A entitlement period<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

A submitted enrollment or PBP change transaction (Transaction Type 61) was rejected because the<br />

beneficiary was not age 65 or older. The age requirement is Plan-specific.<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

A submitted enrollment or PBP change transaction (Transaction Type 61) was rejected because the<br />

beneficiary was in Hospice status. The Hospice requirement is Plan-specific (e.g. applies only to<br />

MSA/MA, MSA/Demo, OFM Demo, ESRD I Demo, ESRD II Demo, <strong>and</strong> PACE National <strong>Plans</strong>).<br />

The attempted enrollment date is reported in TRR data record field 18 <strong>and</strong> 24.<br />

Plan Action: Update the Plan records accordingly <strong>and</strong> take the appropriate actions as per CMS<br />

enrollment guidance.<br />

A submitted enrollment or PBP change transaction (Transaction Type 61) or disenrollment<br />

cancellation transaction (Transaction Type 81) enrollment reinstatement was rejected because the<br />

beneficiary is deceased. The beneficiary DOD is reported in TRR data record fields 18 <strong>and</strong> 24.<br />

Plan Action: Update the Plan records accordingly <strong>and</strong> take the appropriate actions as per CMS<br />

enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-10 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

037 R Transaction<br />

Rejected,<br />

Incorrect<br />

Effective<br />

Date<br />

038 R Enrollment<br />

Rejected,<br />

Duplicate<br />

Transaction<br />

039 R Enrollment<br />

Rejected,<br />

Currently<br />

Enrolled in<br />

Same Plan<br />

042 R Transaction<br />

Rejected,<br />

Blocked<br />

BAD ENROLL<br />

DATE<br />

DUPLICATE<br />

ALREADY<br />

ENROLL<br />

ENROLL<br />

BLOCKED<br />

A transaction (Transaction Types 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) was rejected<br />

because the submitted effective date is not appropriate. Inappropriate effective dates include:<br />

For all transaction types, date is not first day of the month<br />

For all transaction types, date is greater than current calendar year plus one, or, date does<br />

not meet Current Calendar Month (CCM) constraints<br />

For Transaction Type 61, non-EGHP enrollment, date is more than one month prior to<br />

CCM or greater than three months after CCM<br />

For Transaction Type 61 transaction, EGHP enrollment, date is more than three months<br />

prior to the CCM or greater than three months after CCM<br />

Transaction Type 72 4Rx Record Update transaction with an effective date not equal to the<br />

effective date of an existing enrollment period<br />

Transaction Type 73 Uncovered Months Change transaction (Creditable Coverage Flag = N<br />

or Y) with an effective date not equal to the effective date of an existing enrollment period<br />

Transaction Type 80 Enrollment Cancellation transaction with an effective date not equal to<br />

the effective date of an existing enrollment<br />

Transaction Type 81 Disenrollment Cancellation transaction with an effective date not<br />

equal to the effective date of an existing disenrollment<br />

Plan Action: Correct the Effective Date <strong>and</strong> resubmit if appropriate. If this is a retroactive<br />

transaction, contact CMS for instructions on submitting retroactive transactions.<br />

An enrollment transaction (Transaction Type 61) was rejected because it was a duplicate<br />

transaction. CMS has already processed another enrollment transaction submitted for the same<br />

contract, PBP, application date <strong>and</strong> effective date.<br />

Plan Action: None required<br />

An enrollment or PBP change transaction (Transaction Type 61) was rejected because the<br />

beneficiary is already enrolled in this contract/PBP.<br />

Plan Action: None required<br />

An enrollment or PBP change transaction (Transaction Type 61) or disenrollment cancellation<br />

transaction (Transaction Type 81) [enrollment reinstatement] was rejected because the Plan is<br />

currently blocked from enrolling new beneficiaries.<br />

Plan Action: Check HPMS <strong>and</strong> contact CMS.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-11 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

044 R Transaction<br />

Rejected,<br />

Outside<br />

Contracted<br />

Period<br />

NO CONTRACT This TRC is returned for an enrollment or PBP change transaction (Transaction Type 61) ,<br />

enrollment cancellation transaction (Transaction Type 80) or a disenrollment cancellation<br />

transaction (Transaction Type 81) enrollment reinstatement.<br />

TC61 – transaction was rejected because the submitted enrollment date is outside the<br />

Plan’s contracted period<br />

TC80 <strong>and</strong> TC81 – transaction was rejected because the enrollment reinstatement period is<br />

outside the Plan’s contracted period<br />

045 R Enrollment<br />

Rejected,<br />

Beneficiary is<br />

in ESRD<br />

048 A Nursing<br />

Home<br />

Certifiable<br />

Status Set<br />

050 R Disenrollmen<br />

t Rejected,<br />

Not Enrolled<br />

MEMB HAS<br />

ESRD<br />

NHC ON<br />

NOT ENROLLED<br />

Plan Action: Check HPMS <strong>and</strong> contact CMS.<br />

An enrollment or PBP change transaction (Transaction Type 61) was rejected because the<br />

beneficiary is in ESRD (end-stage renal disease) status. The attempted enrollment effective date is<br />

reported in TRR data file field 18 <strong>and</strong> 24.<br />

Affected <strong>Plans</strong> cannot enroll ESRD members unless the individual was previously enrolled in the<br />

commercial side of the plan or the plan has been previously approved for such enrollments.<br />

Plan Action: Review full CMS guidance on enrollment of ESRD beneficiaries in the <strong>Medicare</strong><br />

Managed Care Manual (MMCM) or PDP Enrollment Guidance. If the Plan has approval to enroll<br />

ESRD members, they should resubmit the enrollment with an A in the Prior Commercial Indicator<br />

field (position 80).<br />

A correction transaction (Transaction Type 01) placed the beneficiary in Nursing Home Certifiable<br />

(NHC) status. The NHC health status is Plan specific, e.g., applies to SHMO I, Mass. Dual Eligible,<br />

MDHO <strong>and</strong> MSHO plans. The effective date of the NHC status is reported in TRR data record field<br />

18 <strong>and</strong> 24.<br />

Note: This TRC is only applicable for effective dates prior to 1/1/2008.<br />

Plan Action: Update the Plan records.<br />

A disenrollment transaction (Transaction Type 51) was rejected, because the beneficiary was not<br />

enrolled in the contract as of the effective date of the disenrollment.<br />

Plan Action: Verify the Plan’s enrollment information for this beneficiary.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-12 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

051 R Disenrollmen<br />

t Rejected,<br />

Incorrect<br />

Effective<br />

Date<br />

052 R Disenrollmen<br />

t Rejected,<br />

Duplicate<br />

Transaction<br />

054 R Disenrollmen<br />

t Rejected,<br />

Retroactive<br />

Effective<br />

Date<br />

BAD DISENR<br />

DATE<br />

DUPLICATE<br />

RETRO DISN<br />

DATE<br />

A disenrollment transaction (Transaction Type 51) or a disenrollment cancellation transaction<br />

(Transaction Type 81) was rejected because the submitted enrollment effective date was either:<br />

Not the first day of the month, or<br />

More than three months beyond the Current Calendar Month (CCM+3)<br />

Note: Transactions with effective dates prior to CCM are returned with TRC 054.<br />

Plan Action: Correct the Effective Date <strong>and</strong> resubmit if appropriate. If this is a retroactive<br />

transaction, contact CMS for instructions on submitting retroactive transactions<br />

A disenrollment transaction (Transaction Type 51), enrollment cancellation transaction (Transaction<br />

Type 80), or disenrollment cancellation transaction (Transaction Type 81) was rejected because it<br />

was a duplicate transaction. CMS has already processed another a similar transaction submitted for<br />

the same contract with the same effective date.<br />

The effective date of the disenrollment is reported in the Effective Date field (18) on the TRR data<br />

file.<br />

Plan Action: None required<br />

A disenrollment transaction (Transaction Type 51 or 54) was rejected because the submitted<br />

effective date was prior to the earliest allowed date for disenrollment transactions. Effective dates<br />

for disenrollment transactions (Transaction Type 51) can be no earlier than one month prior to the<br />

Current Calendar Month (CCM) or two months prior for Transaction Type 54 transactions.<br />

The requested disenrollment effective date is reported in the Effective Date field (18) on the TRR<br />

data file.<br />

Plan Action: Correct the Effective Date <strong>and</strong> resubmit if appropriate. If this is a retroactive<br />

transaction, contact CMS for instructions on submitting retroactive transactions.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-13 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

055 M ESRD<br />

Cancellation<br />

056 R Demonstratio<br />

n Enrollment<br />

Rejected<br />

ESRD<br />

CANCELED<br />

FAILS DEMO<br />

REQ<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary was previously in End State Renal Disease (ESRD) status. That status has been<br />

cancelled. The effective date of the ESRD status cancellation is reported in TRR data file field 18<br />

<strong>and</strong> 24.<br />

Plan Action: Update the Plan records.<br />

An enrollment transaction (Transaction Type 61) was rejected because the beneficiary did not meet<br />

the Demonstration requirements. For example, the beneficiary is currently known to be Working<br />

Aged or not known to be ESRD. These requirements are Plan specific.<br />

The attempted enrollment effective date is reported in TRR data file fields 18 <strong>and</strong> 24.<br />

060 R Transaction<br />

Rejected, Not<br />

Enrolled<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

NOT ENROLLED A Correction (Transaction Type 01), Cancellation of Enrollment (Transaction Type 80),<br />

Cancellation of Disenrollment (Transaction Type 81), or change transaction (Transaction Types 74,<br />

75, 76, 77, 78, 79) was rejected because the beneficiary was not enrolled in a Plan as of the<br />

submitted effective date.<br />

062 R Correction<br />

Rejected,<br />

Overlaps<br />

Other Period<br />

INS-NHC<br />

OVERLAP<br />

For NUNCMO Change transactions, Transaction Type 73, either the beneficiary is not enrolled in<br />

the plan submitting this transaction as of the month of the submission, or, the submitted effective<br />

date does not fall within a Part D plan enrollment.<br />

Plan Action: Verify the beneficiary identifying information <strong>and</strong> resubmit the transaction with<br />

updated information, if appropriate.<br />

A correction transaction (Transaction Type 01) was rejected because this transaction would have<br />

resulted in overlapping Institutional <strong>and</strong> Nursing Home Certifiable (NHC) periods. The beneficiary<br />

is not allowed to be in both Institutional <strong>and</strong> NHC status. These two types of periods are mutually<br />

exclusive.<br />

Note: This TRC is only applicable for effective dates prior to 1/1/2008.<br />

Plan Action: Ensure that the Plan’s records reflect the correct dates.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-14 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

071 M Hospice<br />

Status Set<br />

072 M Hospice<br />

Status<br />

Terminated<br />

HOSPICE ON<br />

HOSPICE OFF<br />

This TRC is returned on a reply with Transaction Type 01 <strong>and</strong> occasionally with Transaction Type<br />

51, <strong>and</strong> Transaction Type 61. When returned with Transaction Type 01, the TRC is in response to a<br />

change in beneficiary Hospice status. It is not a reply to a submitted transaction but is intended to<br />

supply the Plan with additional information about the beneficiary.<br />

In the case of Transaction Type 01, a notification has been received that this beneficiary is in<br />

Hospice status. The date on which Hospice Status became effective is reported in TRR data file<br />

fields 18 <strong>and</strong> 24.<br />

The effective date for Hospice Status is not restricted to the first or last day of the month. It may be<br />

any day of the month.<br />

When this TRC is returned with Transaction Type 61 the TRC is in response to a retroactive<br />

enrollment <strong>and</strong> is identifying the fact that an enrollment end date has been established due to the<br />

beneficiary’s hospice status. The enrollment start date is in TRR data file field 18 <strong>and</strong> the<br />

enrollment end date is in field 24. In this circumstance it is accompanied by TRC 018, Automatic<br />

Disenrollment, as well.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

A notification has been received that this beneficiary’s Hospice Status has been terminated. The end<br />

date for the Hospice Status is reported in TRR data file fields 18 <strong>and</strong> 24.<br />

The date for termination of Hospice Status is not restricted to the first or last day of the month. It<br />

may be any day of the month.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-15 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

073 M ESRD Status<br />

Set<br />

074 M ESRD Status<br />

Terminated<br />

075 A Institutional<br />

Status Set<br />

ESRD ON<br />

ESRD OFF<br />

INSTITUTION ON<br />

This TRC is returned on a reply with Transaction Type 01 <strong>and</strong> occasionally with Transaction Type<br />

61. When returned with Transaction Type 01, the TRC is in response to a change in beneficiary<br />

ESRD status. It is not a reply to a submitted transaction but is intended to supply the Plan with<br />

additional information about the beneficiary.<br />

In the case of Transaction Type 01, a notification has been received that this beneficiary is in End<br />

Stage Renal Disease (ESRD) status. The date on which ESRD Status became effective reported in<br />

TRR data file fields 18 <strong>and</strong> 24.<br />

When this TRC is returned with Transaction Type 61 the TRC is in response to a retroactive<br />

enrollment <strong>and</strong> is identifying the fact that an enrollment end date has been established due to the<br />

beneficiary’s ESRD status. The enrollment start date is in TRR data file field 18 <strong>and</strong> the enrollment<br />

end date is in field 24. In this circumstance it is accompanied by TRC 018, Automatic<br />

Disenrollment, as well.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

A notification has been received that this beneficiary’s End Stage Renal Disease (ESRD) Status has<br />

been terminated. The end date for the ESRD Status is reported in TRR data file fields 18 <strong>and</strong> 24.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

A correction transaction (Transaction Type 01) placed the beneficiary in Institutional status. The<br />

effective date of the Institutional status is shown in TRR data record field 24.<br />

Institutional status automatically ends each month; therefore, there is no Institutional Status<br />

termination transaction. This TRC is only applicable for application dates prior to 01/01/2008.<br />

Plan Action: Update the Plan records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

Note: This TRC is only applicable for effective dates prior to 01/01/2008.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-16 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

077 M Medicaid<br />

Status Set<br />

MEDICAID ON A reply with this TRC is seen for plan submitted retroactive Transaction Type 01 <strong>and</strong> 30<br />

transactions <strong>and</strong> occasionally Transaction Type 61 enrollment transactions.<br />

078 M Medicaid<br />

Status<br />

Terminated<br />

MEDICAID OFF<br />

In the case of Transaction Type 01, this beneficiary has been placed in Medicaid Status by the plan.<br />

The effective date of the Medicaid Status is reported in the TRR in field 18. This date is always the<br />

first of the month <strong>and</strong> is retroactive.<br />

When this TRC is returned with Transaction Type 61, the TRC is in response to a retroactive<br />

enrollment <strong>and</strong> is identifying the fact that an enrollment end date has been established due to the<br />

beneficiary having a Medicaid status. The enrollment start date is in TRR data file field 18 <strong>and</strong> the<br />

enrollment end date is in field 24. In this circumstance it is accompanied by TRC 018, Automatic<br />

Disenrollment, as well.<br />

Transaction type 30, when provided with the request type 22, is a rate recalculation for a Medicaid<br />

status change.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

A reply with this TRC may be informational from CMS Transaction Type 30 or in response to a<br />

Transaction Type 01 transaction submitted by the Plan.<br />

This beneficiary’s Medicaid Status has been terminated. The effective date of the termination of<br />

Medicaid Status is reported in TRR data file fields 18 <strong>and</strong> 24 of the TRR. This date is always the<br />

last day of the month.<br />

Transaction type 30, when provided with the request type 22, is a rate recalculation for a Medicaid<br />

status change.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-17 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

079 M Part A<br />

Termination<br />

MEDICARE A<br />

OFF<br />

This TRC is returned on a reply with Transaction Type 01 <strong>and</strong> occasionally with Transaction Type<br />

61. When returned with Transaction Type 01, the TRC is in response to a change in beneficiary Part<br />

A Entitlement. It is not a reply to a submitted transaction but is intended to supply the Plan with<br />

additional information about the beneficiary.<br />

In the case of Transaction Type 01, this beneficiary’s Part A Entitlement has been terminated. The<br />

effective date of the termination is reported in TRR data file fields 18 <strong>and</strong> 24.<br />

When this TRC is returned with Transaction Type 61, the TRC is in response to a retroactive<br />

enrollment <strong>and</strong> is identifying the fact that an enrollment end date has been established due to the<br />

beneficiary’s termination of Part A. The enrollment start date is in TRR data file field 18 <strong>and</strong> the<br />

enrollment end date is in field 24. In this circumstance it is accompanied by TRC 018, Automatic<br />

Disenrollment, as well.<br />

Note: A TRR record with this reply code is only reported to the Plan in which the beneficiary is<br />

currently enrolled, even if it affects periods of enrollment in other <strong>Plans</strong>.<br />

080 M Part A<br />

Reinstatemen<br />

t<br />

MEDICARE A ON<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary’s Part A Entitlement has been reinstated. The effective date of the start of Part A<br />

entitlement is reported in fields TRR data file 18 <strong>and</strong> 24.<br />

Note: A TRR record with this reply code is only reported to the Plan in which the beneficiary is<br />

currently enrolled, even if it affects periods of enrollment in other <strong>Plans</strong>. If, as a result of a loss of<br />

Part A entitlement, the beneficiary has been disenrolled <strong>and</strong> does not continue to be enrolled in<br />

some managed care contract, the reply code is not issued.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-18 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

081 M Part B<br />

Termination<br />

MEDICARE B<br />

OFF<br />

This TRC is returned on a reply with Transaction Type 01 <strong>and</strong> occasionally with Transaction Type<br />

51 <strong>and</strong> Transaction Type 61. When returned with Transaction Type 01, the TRC is in response to a<br />

change in beneficiary Part B Entitlement. It is not a reply to a submitted transaction but is intended<br />

to supply the Plan with additional information about the beneficiary.<br />

In the case of Transaction Type 01, this beneficiary’s Part B Entitlement has been terminated. The<br />

effective date of the termination is reported in TRR data file fields 18 <strong>and</strong> 24.<br />

When this TRC is returned with Transaction Types 51 or 61, the TRC is in response to a retroactive<br />

enrollment <strong>and</strong> is identifying the fact that an enrollment end date has been established due to the<br />

beneficiary’s termination of Part B. The enrollment start date is in TRR data file field 18 <strong>and</strong> the<br />

enrollment end date is in field 24. In this circumstance it is accompanied by TRC 018, Automatic<br />

Disenrollment, as well.<br />

Note: A TRR record with this reply code is only reported to the Plan in which the beneficiary is<br />

currently enrolled, even if it affects periods of enrollment in other <strong>Plans</strong>.<br />

082 M Part B<br />

Reinstatemen<br />

t<br />

MEDICARE B ON<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary’s Part B Entitlement has been reinstated. The effective date of the start of Part B<br />

entitlement is reported in TRR data file fields 18 <strong>and</strong> 24.<br />

Note: A TRR record with this reply code is only reported to the Plan in which the beneficiary is<br />

currently enrolled, even if it affects periods of enrollment in other <strong>Plans</strong>. If, as a result of a loss of<br />

Part B entitlement, the beneficiary has been disenrolled, but not re-enrolled, the reply code is not<br />

issued.<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-19 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

085 M State <strong>and</strong><br />

County Code<br />

Change<br />

086 M Claim<br />

Number<br />

Change<br />

087 M Name<br />

Change<br />

088 M Sex Code<br />

Change<br />

NEW SCC<br />

NEW HICN<br />

NEW NAME<br />

NEW SEX CODE<br />

This TRC is returned either on a reply with Transaction Type 01. It is intended to supply the Plan<br />

with additional information about the beneficiary.<br />

This beneficiary’s State <strong>and</strong> County Code (SCC) information has changed. The new SCC<br />

information will be reported in TRR data record fields 9 (state code), 10 (county code), <strong>and</strong> together<br />

in field 24.<br />

Plan Action: Update the Plan’s records.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary’s HICN has changed. The new claim number is reported in TRR data record field<br />

1 <strong>and</strong> the old claim number is in Field 24.<br />

Plan Action: Update the Plan’s records. The new claim number must be used on all future<br />

transactions for this beneficiary.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary’s name has changed. The new name is reported in the TRR data record name fields<br />

(2, 3 <strong>and</strong> 4), SURNAME, FIRST NAME <strong>and</strong> MI. The effective date field (field 18) reports the date<br />

the name change was processed by CMS.<br />

Plan Action: Update the Plan’s records. To ensure accurate identification of the beneficiary, future<br />

submitted transactions for this beneficiary should use the new name.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary’s sex code has changed. The new sex code is reported in TRR data file field 5. The<br />

effective date field (field 18) reports the date the sex code change was processed by CMS.<br />

Plan Action: Update the Plan’s records. To ensure accurate identification of the beneficiary, future<br />

submitted transactions for this beneficiary should use the new sex code.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-20 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

089 M Date of Birth<br />

Change<br />

090 M Date of Death<br />

Established<br />

NEW BIRTH<br />

DATE<br />

MEMB<br />

DECEASED<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary’s date of birth has changed. The new date of birth is reported in TRR data file field<br />

6 (DOB) <strong>and</strong> field 24. Field 18 (Effective Date) reports the date the DOB change was processed by<br />

CMS.<br />

Plan Action: Update the Plan’s records. To ensure accurate identification of the beneficiary, future<br />

submitted transactions for this beneficiary should use the new date of birth.<br />

This TRC is not a reply to a submitted transaction but is intended to supply the Plan with additional<br />

information about the beneficiary.<br />

When CMS is notified of a beneficiary’s death, the Plan receives three replies in their TRR.<br />

Transaction Type 01 with TRC 090 - only received by the Plan in which the beneficiary is<br />

enrolled during the CPM.<br />

Transaction Type 51 with TRC 090<br />

Transaction Type 51 with TRC 018 or TRC 015<br />

Transaction replies with other TRCs may also accompany these three replies. Examples<br />

include status terminations <strong>and</strong> SSA responses.<br />

On a Transaction Type 01 transaction with TRC 090, the beneficiary’s actual date of death is<br />

reported in TRR data file fields 18 <strong>and</strong> 24.<br />

On a Transaction Type 51 transaction with TRC 090, fields 18 <strong>and</strong> 24 report the effective date of the<br />

disenrollment that results from the death. This will always be the 1 st of the month following the<br />

death if the beneficiary is actively enrolled in a plan. If the Plan’s enrollment is not yet effective,<br />

these fields will report the effective date of the enrollment being cancelled.<br />

Plan Action: Update the Plan’s records with the beneficiary’s date of death from the Transaction<br />

Type 01 transaction. It is the Transaction Type 51 transaction with TRC 018 or 015 that should be<br />

processed as the auto-disenrollment or cancellation. Take the appropriate actions as per CMS<br />

enrollment guidance.<br />

Note: The above three transaction replies may not appear in the same weekly TRR<br />

<strong>December</strong> <strong>28</strong>, 2012 I-21 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

091 M Date Of<br />

Death<br />

Removed<br />

092 M Date of Death<br />

Corrected<br />

097 R Medicaid<br />

Previously<br />

Turned On<br />

DEATH DATE<br />

OFF<br />

NEW DEATH<br />

DATE<br />

MCAID PREV ON<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

Although the Plan has previously received a transaction reply reporting a date of death for this<br />

beneficiary, the date of death has been removed. The beneficiary is still alive. TRR data file fields<br />

18 <strong>and</strong> 24 contain the date of death that was previously reported to the Plan.<br />

If the date of death is removed after the auto disenrollment has taken effect, the Plan will not receive<br />

this transaction reply. The removal of the Date of Death may initiate the reinstatement of an<br />

enrollment. (See TRC <strong>28</strong>7)<br />

Plan Action: Update the Plan’s records <strong>and</strong> restore the beneficiary’s enrollment with the original<br />

enrollment start <strong>and</strong> end dates. Take the appropriate actions as per CMS enrollment guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

The date of death for this beneficiary has been corrected. The corrected date of death is reported in<br />

TRR data file field 24. The correction of the DOD may initiate the reinstatement of an enrollment.<br />

(See TRC <strong>28</strong>7)<br />

Plan Action: Update the Plan’s records. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

A correction transaction (Transaction Type 01) was rejected because this transaction attempted to<br />

set the Medicaid status for the beneficiary to ON. The Medicaid status for the beneficiary was<br />

already ON for the month in question.<br />

Note: This TRC is only applicable for submitted correction transactions (01) with effective dates<br />

prior to 1/1/2008.<br />

Plan Action: None required. Verify the Plan records.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-22 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

098 R Medicaid<br />

Previously<br />

Turned Off<br />

MCAID PREV<br />

OFF<br />

A correction transaction (Transaction Type 01) was rejected because this transaction attempted to<br />

set the Medicaid status for the beneficiary to OFF. The Medicaid status for the beneficiary was<br />

already OFF for the month in question.<br />

Note: This TRC is only applicable for submitted correction transactions (Transaction Type 01) with<br />

effective dates prior to 1/1/2008.<br />

099 M Medicaid<br />

Period<br />

Change/Canc<br />

ellation<br />

100 A PBP Change<br />

Accepted as<br />

Submitted<br />

102 R Rejected;<br />

Incorrect or<br />

Missing<br />

Application<br />

Date<br />

MCAID CHANGE<br />

PBP CHANGE OK<br />

BAD APP DATE<br />

Plan Action: None required. Verify the Plan records.<br />

A change has been made to a period of Medicaid status information for the beneficiary.<br />

Plan Action: Plan should update beneficiary record.<br />

A submitted PBP Change transaction (Transaction Type 61) has been successfully processed. The<br />

beneficiary has been moved from the original PBP to the new PBP. The effective date of<br />

enrollment in the new PBP is reported in fields 18 <strong>and</strong> 24 of the TRR data record. The effective<br />

date will always be the first day of the month.<br />

This is the definitive PBP Change acceptance record. Other accompanying replies with different<br />

TRCs may give additional information about this accepted PBP Change.<br />

Field 20 (Plan Benefit Package ID) contains the new PBP identifier. The old PBP is reported in<br />

field 29 (Prior Plan Benefit Package ID).<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

If the Application Date on an enrollment transaction (Transaction Type 61) is blank or contains a<br />

valid date that is not appropriate for the submitted transaction, TRC 102 is returned in the TRR<br />

record. Examples of inappropriate application dates:<br />

Date is blank<br />

Date is later than the submitted Effective Date.<br />

Date does not lie within the election period specified on the submitted transaction<br />

Note: <strong>Plans</strong> should see Chapter 2 of the MMCM or the PDP Guidance on Eligibility, Enrollment<br />

<strong>and</strong> Disenrollment for detailed descriptions of the Election Periods.<br />

Plan Action: Correct the Application Date <strong>and</strong> resubmit if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-23 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

103 R ICEP/IEP<br />

Election,<br />

Missing A/B<br />

Entitlement<br />

Date<br />

104 R Rejected;<br />

Invalid or<br />

Missing<br />

Election Type<br />

ICEP/IEP NO ENT<br />

BAD ELECT TYPE<br />

An enrollment transaction (Transaction Type 61) was rejected because the beneficiary does not have<br />

entitlement for Part A <strong>and</strong>/or enrollment in Part B on record (required for enrollment transactions).<br />

This TRC is only returned on enrollment transactions submitted with election type I (Initial<br />

Coverage Election Period) or E (Initial Enrollment Period for Part D).<br />

Plan Action: Verify the beneficiary’s Part A / Part B entitlement / enrollment. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

An enrollment (Transaction Type 61) or disenrollment (Transaction Type 51) was rejected because<br />

the submitted Election Type is either missing, contains an invalid value or is not appropriate for the<br />

plan or for the transaction type.<br />

The valid Election Type values are:<br />

A - Annual Election Period (AEP)<br />

D - MA Annual Disenrollment Period (MADP)<br />

E - Initial Enrollment Period for Part D (IEP)<br />

F - Second Initial Enrollment Period for Part D (IEP2)<br />

I - Initial Coverage Election Period (ICEP)<br />

O - Open Enrollment Period (OEP) (Valid through 3/31/2010)<br />

N - Open Enrollment for Newly Eligible Individuals (OEPNEW) (Valid through 12/31/2010)<br />

T - Open Enrollment Period for Institutionalized Individuals (OEPI)<br />

Special Enrollment Periods<br />

U - SEP for Loss of Dual Eligibility or for Loss of LIS<br />

V - SEP for Changes in Residence<br />

W - SEP EGHP (Employer/Union Group Health Plan)<br />

Y - SEP for CMS Casework Exceptional Conditions<br />

X - SEP for Administrative Change<br />

Plan Submitted “Rollover”<br />

Involuntary Disenrollment<br />

PPO Change<br />

Plan-submitted “Canceling” Transaction<br />

<strong>December</strong> <strong>28</strong>, 2012 I-24 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

104<br />

Con’t<br />

R<br />

Rejected;<br />

Invalid or<br />

Missing<br />

Election Type<br />

BAD ELECT TYPE<br />

Z - SEP for:<br />

Auto-Enrollment (Enrollment Source Code = A)<br />

Facilitated Enrollment (Enrollment Source Code = C)<br />

Plan-Submitted Auto-Enrollment (Enrollment Source Code = E) <strong>and</strong> Transaction<br />

Type 61 (PBP Change) <strong>and</strong> MA or Cost Plan (all conditions must be met)<br />

POS Enrollment (Enrollment Source Code = G)<br />

S - Special Enrollment Period (SEP)<br />

The value expected in Election Type depends on the Plan <strong>and</strong> transaction type, as well as on when<br />

the beneficiary gains entitlement. Each Election Type Code can be used only during the election<br />

period associated with that election type. Additionally, there are limits on the number of times each<br />

election type may be used by the beneficiary.<br />

105 R Rejected;<br />

Invalid<br />

Effective<br />

Date for<br />

Election Type<br />

BAD ELECT<br />

DATE<br />

Plan Action: Review the detailed information on Election Periods in Chapter 2 of the MMCM or<br />

the PDP Guidance on Eligibility, Enrollment <strong>and</strong> Disenrollment. Determine the appropriate<br />

Election Type value <strong>and</strong> resubmit, if appropriate.<br />

An enrollment or disenrollment transaction (Transaction Types 61, 51) was rejected because the<br />

effective date was not appropriate for the election type or for the submitted application date.<br />

Examples of inappropriate effective dates:<br />

Date is outside of the election period defined by the submitted election type.<br />

(ex: Election Type = A <strong>and</strong> Effective Date = 2/1/2007)<br />

Date is not appropriate for the application date<br />

(ex: App date = 6/10/2007 & Eff Date =11/01/2007)<br />

Plan Action: Correct the Effective Date or Election Type <strong>and</strong> resubmit if appropriate. Review<br />

Chapter 2 of the MMCMor the PDP Guidance on Eligibility, Enrollment <strong>and</strong> Disenrollment for<br />

detailed descriptions of the Election Periods <strong>and</strong> corresponding effective dates.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-25 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

106 R Rejected,<br />

Another<br />

Trans Rcvd<br />

with Later<br />

App Date<br />

107 R Rejected,<br />

Invalid or<br />

Missing PBP<br />

Number<br />

108 R Rejected,<br />

Election<br />

Limits<br />

Exceeded<br />

LATER APPLIC<br />

BAD PBP<br />

NUMBER<br />

NO MORE<br />

ELECTS<br />

An enrollment transaction (Transaction Type 61) was rejected because a transaction with a more<br />

recent application date or same date as another application date was received for the same effective<br />

date. The submitted enrollment has been overridden by an enrollment in another contract/PBP.<br />

When multiple transactions are received for the same beneficiary with the same effective date but<br />

with different contract/PBP #s, the application date is used to determine which enrollment to accept.<br />

If the application dates are different, the system will accept the election containing the most recent<br />

date. .<br />

Plan Action: The beneficiary is not enrolled in the Plan. Update the Plan records.<br />

An enrollment or Record Update transaction (Transaction Types 61, 72, 73, 74, 75, 77, 78, 79, 80)<br />

was rejected because the PBP # was missing or invalid. The PBP # must be of the correct format<br />

<strong>and</strong> be valid for the contract on the transaction.<br />

Note: PBP # is not required on Disenrollment, Residence Address, <strong>and</strong> Disenrollment Cancellation<br />

transactions, (Transaction Types 51, 76, 81) but when submitted it must be valid for the contract<br />

number on the transaction.<br />

Plan Action: Correct the PBP # <strong>and</strong> resubmit the transaction if appropriate.<br />

A transaction for which an election type is required (Transaction Types 51, 61) was rejected because<br />

the transaction will exceed the beneficiary’s election limits for the submitted election type.<br />

The valid Election Type values which have limits are:<br />

A - Annual Election Period (AEP)<br />

1 per calendar year<br />

E - Initial Enrollment Period for Part D (IEP)<br />

1 per lifetime<br />

F - Initial Enrollment Period for Part D (IEP2)<br />

1 per lifetime<br />

I - Initial Coverage Election Period (ICEP)<br />

1 per lifetime<br />

Plan Action: Review the discussion of election type requirements in Chapter 2 of the MMCMor the<br />

PDP Guidance on Eligibility, Enrollment <strong>and</strong> Disenrollment. Correct the election type <strong>and</strong> resubmit<br />

the transaction if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-26 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

109 R Rejected,<br />

Duplicate<br />

PBP Number<br />

110 R Rejected; No<br />

Part A <strong>and</strong><br />

No EGHP<br />

Enrollment<br />

Waiver<br />

114 R <strong>Drug</strong><br />

Coverage<br />

Change<br />

Rejected; not<br />

AEP or OEPI<br />

ALREADY<br />

ENROLL<br />

NO PART<br />

A/EGHP<br />

RX NOT<br />

AEP/OEPI<br />

An enrollment transaction (Transaction Type 61) was rejected because the member is already<br />

enrolled in the PBP # on the transaction.<br />

The effective date of the requested enrollment is reported in TRR data file field 18.<br />

Plan Action: If the submitted PBP was correct, no Plan action is required. If another PBP was<br />

intended, correct the PBP # <strong>and</strong> resubmit if appropriate.<br />

A PBP enrollment change transaction (Transaction Type 61) was rejected because the beneficiary<br />

lacks Part A <strong>and</strong> there was no EGHP Part B-only waiver in place.<br />

<strong>Plans</strong> can offer a PBP for EGHP members only, <strong>and</strong>, if the Plan chooses, it can define such PBPs for<br />

individuals who do not have Part A.<br />

Plan Action: Review CMS enrollment guidance in Chapter 2 of the MMCMor the PDP Guidance<br />

on Eligibility, Enrollment <strong>and</strong> Disenrollment <strong>and</strong> notify the beneficiary.<br />

An enrollment change transaction (Transaction Type 61) was rejected because the beneficiary is not<br />

allowed to add or drop drug coverage using an O (OEP) or N (OEPNEW) election types.<br />

Using O or N, a beneficiary who is in a Plan that includes drug coverage may only move to another<br />

Plan with drug coverage. Likewise, if in a Plan without drug coverage, the beneficiary may not<br />

enroll in a Plan with drug coverage or a PDP.<br />

Occasionally, if a beneficiary is moving from a Plan with drug coverage to a combination of st<strong>and</strong>alone<br />

MA <strong>and</strong> PDP plans, the enrollment transaction in the MA-only plan may be processed prior<br />

to the enrollment transaction in the PDP plan. Since this appears to CMS as if the beneficiary is<br />

trying to drop drug coverage, the enrollment into the MA only Plan will be rejected with TRC 114.<br />

Once the enrollment in the PDP is processed, the enrollment in the MA-only may be resubmitted.<br />

Plan Action: Review CMS enrollment guidance on the O <strong>and</strong> N election type limitations in<br />

Chapter 2 of the MMCMor the PDP Guidance on Eligibility, Enrollment <strong>and</strong> Disenrollment. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

Note: If TRC 114 is received by an MA-only Plan when using the OEP or OEPNEW, the Plan<br />

should determine if the beneficiary is enrolled in an accompanying PDP. Once that enrollment is<br />

complete, the MA-Only Plan may resubmit their enrollment transaction.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-27 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

116 R Transaction<br />

Rejected;<br />

Invalid Segmt<br />

num<br />

BAD SEGMENT<br />

NUM<br />

An enrollment transaction (Transaction Type 61) rejects because the enrollment is for a Segmented<br />

PBP, <strong>and</strong> the Segment number on the submitted transaction is invalid<br />

-OR-<br />

A Segment change transaction (Transaction Type 77) is submitted with an invalid Segment number,<br />

for a Segmented PBP<br />

-OR-<br />

A disenrollment cancellation transaction (Transaction Type 81) [enrollment reinstatement] is<br />

submitted <strong>and</strong> the reinstated enrollment has a non-blank Segment, which is no longer valid for the<br />

PBP.<br />

<strong>Plans</strong> must submit a valid Segment number for the Contract/PBP combination. A Segment number is<br />

not required for a disenrollment transaction (Transaction Type 51).<br />

Plan Action: Correct or delete the Segment number <strong>and</strong> resubmit the transaction if appropriate for<br />

Transaction Type 61. Correct the Segment number <strong>and</strong> resubmit the transaction if appropriate for<br />

Transaction Type 77. Submit enrollment for Transaction Type 81 if appropriate. An enrollment<br />

transaction (Transaction Type 61) was rejected because the enrollment is for a PBP that has been<br />

segmented, <strong>and</strong> the segment number on the submitted transaction was missing or invalid.<br />

-OR-<br />

A segment change transaction (Transaction Type 77) was submitted with a non-blank segment<br />

number, <strong>and</strong> the segment number was invalid for the PBP.<br />

‘OR’<br />

A disenrollment cancellation transaction (Transaction Type 81) [enrollment reinstatement] was<br />

submitted <strong>and</strong> the enrollment being reinstated has a non-blank segment which is no longer valid for<br />

the PBP.<br />

Any submitted segment number must be valid for the Contract / PBP combination. Segment number<br />

is not required for a disenrollment transaction (Transaction Type 51).<br />

Plan Action: Correct the Segment number <strong>and</strong> resubmit the transaction if appropriate for<br />

transaction types 61 <strong>and</strong> 77. Submit enrollment for transaction type 81 if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-<strong>28</strong> Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

117 A FBD Auto<br />

Enrollment<br />

Accepted<br />

118 A LIS<br />

Facilitated<br />

Enrollment<br />

Accepted<br />

119 A Premium<br />

Amount<br />

Change<br />

Accepted<br />

FBD AUTO<br />

ENROLL<br />

LIS FAC ENROLL<br />

PREM AMT CHG<br />

This new enrollment transaction (Transaction Type 61) was the result of a Plan-submitted or CMSinitiated<br />

auto-enrollment of a full-benefit dual-eligible beneficiary into a Part D Plan. The<br />

enrollment was accepted. The effective date of the new enrollment is shown in the Effective Date<br />

(field 18) of the TRR data record.<br />

Other accompanying replies with different TRCs may give additional information about this new<br />

enrollment.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

This new enrollment transaction (Transaction Type 61) was the result of a Plan-submitted or CMSinitiated<br />

facilitated enrollment of a low income beneficiary into a Part D Plan. The effective date of<br />

the new enrollment is shown in the Effective Date (field 18) of the TRR data record.<br />

Other accompanying replies with different TRCs may give additional information about this new<br />

enrollment.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

A Part C Premium Change transaction (Transaction Type 78) was accepted. The Part C premium<br />

amount has been updated with the amount submitted on the transaction. The amount may have also<br />

been updated by CMS.<br />

The effective date of the new premium will be reported in TRR data record field 18. The amount of<br />

the new Part C premium will be reported in field 19 of the TRR record.<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary’s premium<br />

amounts are implemented as of the effective date in field 18. Take the appropriate actions as per<br />

CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-29 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

120 A PPO Change<br />

Sent to W/H<br />

Agency<br />

WHOLD UPDATE<br />

As a result of an accepted Plan-submitted transaction (Transaction Types 51, 61, 73, 74, 75) or UI<br />

update to a beneficiary’s records, information has been forwarded to SSA/RRB to update SSA/RRB<br />

records <strong>and</strong> implement any requested premium withholding changes.<br />

Any requested change will not take effect until an SSA/RRB acceptance is received. <strong>Plans</strong> are<br />

notified of the SSA/RRB acceptance with a TRC 185 in a future TRR data file.<br />

Plan Action: None required. Take the appropriate actions as per CMS enrollment guidance.<br />

Note: The Plan will not see the result of any PPO change until they have received a TRC 185 on a<br />

future TRR.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-30 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

121 M Low Income<br />

Period Status<br />

LIS UPDATE<br />

This TRC is returned on a reply with Transaction Types 01, 51, 61, 80, <strong>and</strong> 81. It is not a reply to a<br />

submitted transaction but is intended to supply the Plan with additional information about the<br />

beneficiary. It is created in response to an enrollment transaction or change in a beneficiary’s low<br />

income profile. Each TRC 121 returns start <strong>and</strong> end dates if the beneficiary is Deemed (start date<br />

only if the beneficiary is an SSA Applicant), premium subsidy percentage, <strong>and</strong> copayment category<br />

for one low income period affecting a PBP enrollment. There may be more than one TRC 121<br />

returned.<br />

TRC 121 is issued for all periods of low income benefits that fall within the Plan’s enrollment<br />

period. The enrollment period description is identified in Field 66 with a ‘C’ for current enrollees,<br />

‘P’ for prospective enrollees, <strong>and</strong> ‘Y’ for previous enrollees.<br />

The beneficiary’s Low-Income Subsidy source will be identified in Field 65 with an ‘A’ for<br />

Approved SSA Applicants or a ‘D’ for Deemed beneficiary by CMS.<br />

The following LIS information is displayed on the Transaction Reply Report (TRR) for TRC 121:<br />

PBP Enrollment Effective Date (Field 18)<br />

Part D Low-income Premium Subsidy Level (Field 49)<br />

Low-income Co-Pay Category (Field 50)<br />

Low-income Period start date (Field 51)<br />

Low-income Period End Date (Field 64)<br />

Low-income Period Subsidy Source (Field 65)<br />

Enrollment Period Description (Field 66)<br />

Low income subsidy TRC 223 may accompany TRC 121. These three TRCs convey the<br />

beneficiary’s low income subsidy profile affecting the identified PBP enrollment period.<br />

Plan Action: Update the Plan’s records to reflect the given data for the beneficiary’s LIS period.<br />

Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-31 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

122 R Enrollment/C<br />

hange<br />

Rejected,<br />

Invalid<br />

Premium<br />

Amount<br />

123 R Enrollment/C<br />

hange<br />

Rejected,<br />

Invalid Prm<br />

Pay Opt Cd<br />

BAD PREMIUM<br />

AMT<br />

BAD W/HOLD<br />

OPT<br />

An enrollment or premium change transaction (Transaction Type 61, or 78) was rejected because<br />

the submitted Part C premium amount was non-blank <strong>and</strong> not numeric.<br />

If the Part C premium field is blank on a submitted enrollment transaction (Transaction Type 61),<br />

the blank will be converted to zeros. Any submitted value must be numeric.<br />

A blank or invalid Part C premium field is not permitted on the Part C premium change transaction<br />

(Transaction Type 78).<br />

Plan Action: Correct the Part C premium amounts <strong>and</strong> resubmit if appropriate.<br />

An Enrollment or PPO Change transaction (Transaction Types 61, 75) was rejected because the<br />

value submitted in the PPO Code field was an invalid value.<br />

The valid values include:<br />

D - Direct Bill - Self Pay<br />

R - Deduct from RRB benefits<br />

S - Deduct from SSA benefits<br />

N - No premium applicable<br />

O (Deduct from OPM benefits) is not currently available. It is scheduled for future implementation.<br />

Plan Action: Correct the PPO code <strong>and</strong> resubmit if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-32 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

124 R Enrollment/C<br />

hange<br />

Rejected;<br />

Invalid<br />

Uncov<br />

Months<br />

126 R Enrollment/C<br />

hange<br />

Rejected;<br />

Invalid Cred<br />

Cvrg Flag<br />

127 R Part D<br />

Enrollment<br />

Rejected;<br />

Employer<br />

Subsidy<br />

Status<br />

BAD UNCOV<br />

MNTHS<br />

BAD CRED COV<br />

FL<br />

EMP SUB REJ<br />

An enrollment or number of uncovered months change transaction (Transaction Types 61, 73) was<br />

rejected because the Number of Uncovered Months field was not correctly populated.<br />

This rejection could be the result of the following conditions:<br />

The field contained a non-numeric value<br />

The Uncovered Months field was zero when the Creditable Coverage Switch was set to N<br />

For Transaction Type 61, the Uncovered Months field was greater than zero when the<br />

Creditable Coverage Switch was set to Y or blank.<br />

For Transaction Type 73, the Uncovered Months field was greater than zero when the<br />

Creditable Coverage Switch was set to Y.<br />

Plan Action: Correct the Number of Uncovered Months value <strong>and</strong> resubmit the transaction if<br />

appropriate. Verify that the Creditable Coverage Flag <strong>and</strong> Number of Uncovered Months<br />

combination is valid.<br />

An enrollment or number of uncovered months change transaction (Transaction Types 61, 73) was<br />

rejected because the Creditable Coverage Flag field was not correctly populated.<br />

For Transaction Type 61, the valid values for the Creditable Coverage Flag are Y, N, <strong>and</strong> blank.<br />

For Transaction Type 73, the valid values for the Creditable Coverage Flag are Y <strong>and</strong> N.<br />

Plan Action: Correct the Creditable Coverage Flag value <strong>and</strong> resubmit the transaction if<br />

appropriate. Verify that the Creditable Coverage Flag <strong>and</strong> Number of Uncovered Months<br />

combination is valid.<br />

An enrollment transaction (Transaction Type 61) was rejected because the beneficiary has employer<br />

subsidy periods overlapping with the requested enrollment period.<br />

The requested effective date is reported in TRR data file field 18.<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance. Contact the<br />

beneficiary to explain the potential consequences of this enrollment. If the beneficiary elects to join<br />

the Part D plan anyway, the enrollment should be resubmitted with the Employer Subsidy Override<br />

Flag set to Y.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-33 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

1<strong>28</strong> R Part D Enroll<br />

Reject;<br />

Emplyr<br />

Sbsdy set: No<br />

Prior Trn<br />

EMP SUB OVR<br />

REJ<br />

An enrollment transaction (Transaction Type 61) was rejected because the beneficiary has employer<br />

subsidy periods overlapping with the requested enrollment period.<br />

Even through this transaction was submitted with the Employer Subsidy Override Flag set to Y, the<br />

override is not valid because there is no record that the enrollment was previously submitted <strong>and</strong><br />

rejected with TRC 127 (Part D Enrollment Rejected; Employer Subsidy Status).<br />

CMS enforces this two-step process to ensure that the Plan discusses the potential consequences of<br />

the Part D enrollment (i.e. possible loss of employer health coverage) with the beneficiary before<br />

CMS accepts the employer subsidy override.<br />

129 I Part D Enroll<br />

Accept;Emp<br />

Sbsdy set;<br />

Prior Trn<br />

Reject<br />

EMP SUB ACC<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance. Contact the<br />

beneficiary to explain the potential consequences of this enrollment. If the beneficiary elects to join<br />

the Part D plan anyway, the enrollment should be resubmitted with the Employer Subsidy Override<br />

Flag set.<br />

This TRC provides additional information about a new enrollment (Transaction Type 61). The<br />

effective date of the enrollment for which this information is pertinent is reported in TRR data<br />

record field 18.<br />

This newly enrolled beneficiary had employer subsidy periods overlapping with the requested<br />

enrollment period. A prior enrollment transaction was rejected with TRC 127 or 1<strong>28</strong>. The Plan<br />

resubmission of the enrollment transaction with the Employer Subsidy Override Flag set to Y<br />

indicates that the Plan has contacted the beneficiary to explain the potential consequences of this<br />

enrollment, <strong>and</strong> that the beneficiary elected to join the Part D Plan anyway.<br />

Plan Action: No action required. Process the accompanying transaction enrollment acceptance<br />

transaction.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-34 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

130 R Part D Opt-<br />

Out Rejected,<br />

Opt-Out Flag<br />

Not Valid<br />

131 A Part D Opt-<br />

Out Accepted<br />

BAD OPT OUT<br />

CD<br />

OPT OUT OK<br />

An opt-out from CMS, disenrollment, PBP enrollment change, or plan submitted Opt-Out<br />

transaction (Transaction Types 41, 51, 54, 61, 79) was rejected because the Part D Opt-Out Flag<br />

field was not correctly populated.<br />

The valid values for Part D Opt-Out Flag are:<br />

Transaction Types 41 or 79 transactions - ‘Y’ or ‘N’<br />

All other Transaction Types - ‘Y,’ ‘N,’ or blank<br />

Plan Action: If submitted by the Plan (Transaction Types 51, 61, 79), correct the Part D Opt-Out<br />

Flag value <strong>and</strong> resubmit the transaction if appropriate. If submitted by CMS (Transaction Types 41,<br />

54), no Plan action is required.<br />

A transaction (Transaction Types 51, 79) was received that specified a Part D opt-out flag value or a<br />

change to the Part D opt-out flag value. The Part D opt-out flag has been accepted.<br />

The new Part D Opt-Out Flag value is reported in TRR data record field 38.<br />

133 R Part D Enroll<br />

Rejected;<br />

Invalid<br />

Secndry Insur<br />

Flag<br />

Plan Action: No action necessary.<br />

BAD 2 INS FLAG An enrollment, PBP change transaction or 4Rx record update transaction (Transaction Types 61, 72)<br />

was rejected because the TRR data file’s Secondary <strong>Drug</strong> Coverage Flag field was not correctly<br />

populated.<br />

The valid values for Secondary <strong>Drug</strong> Coverage Flag are Y, N or blank.<br />

Plan Action: Correct the Secondary <strong>Drug</strong> Coverage Flag <strong>and</strong> resubmit the transaction if<br />

appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-35 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

134 I Missing<br />

Secondary<br />

Insurance<br />

Information<br />

135 M Beneficiary<br />

Has Started<br />

Dialysis<br />

Treatments<br />

136 M Beneficiary<br />

Has Ended<br />

Dialysis<br />

Treatments<br />

NO 2 INS INFO<br />

DIALYSIS START<br />

DIALYSIS END<br />

An Enrollment, PBP Change, or 4Rx Record Update transaction (Transaction Types 61, 72) was<br />

submitted with the Secondary Insurance Flag set to Y, but the associated secondary insurance fields<br />

(Secondary RxID <strong>and</strong> Secondary RxGroup) were not populated. No changes to the beneficiary’s<br />

secondary insurance information were made.<br />

This is not a transaction rejection. The submitted transaction was accepted <strong>and</strong> a reply was<br />

provided in the TRR with an appropriate acceptance TRC. This reply provides additional<br />

information about the transaction. The Effective Date of the transaction for which this information<br />

is pertinent is reported in TRR data record field 18. The Transaction Type will reflect the<br />

Transaction Type of the submitted transaction. (Transaction Types 61 or 72).<br />

Plan Action: If appropriate, submit a 4Rx Record Update transaction (Transaction Type 72) with<br />

the correct Secondary Insurance RxID <strong>and</strong> Secondary Insurance RxGroup values.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has been notified that the beneficiary has ESRD <strong>and</strong> has begun dialysis treatments. The<br />

effective date of the change is reported in TRR data file field 18.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has been notified that the beneficiary has ESRD <strong>and</strong> is no longer receiving dialysis treatments.<br />

The effective date of the change is reported in DTRR data file field 18.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the DTRR. Process the<br />

TRC 136 to remove the prior period , if the effective date of the TRC 136 (field 18) is equal to the<br />

“start” date of an ESRD period reported to the Plan previously. Alternatively, process the TRC 136<br />

to update the prior period, if the effective date of the TRC 136 (field 18) is not equal to the “start”<br />

date of an ESRD period reported to the Plan in a prior DTRR. Then process the TRC 135 to add the<br />

new corrected period as of the start date in field 18. The end date of the new, corrected period, if<br />

there is one, is not included.. Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-36 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

137 M Beneficiary<br />

Has Received<br />

a Kidney<br />

Transplant<br />

138 M Beneficiary<br />

Address<br />

Change to<br />

Outside the<br />

U.S.<br />

139 A EGHP Flag<br />

Change<br />

Accepted<br />

TRANSPLANT<br />

ADD<br />

ADDR NOT U.S.<br />

EGHP FLAG CHG<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has been notified that the beneficiary has ESRD <strong>and</strong> has received a transplanted kidney. The<br />

effective date of the change is reported in TRR data file field 18.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has been notified that the beneficiary’s address is now outside of the U.S. The effective date<br />

of the change is reported in TRR data record field 18.<br />

Plan Action: Research the beneficiary’s new address <strong>and</strong> update the Plan’s beneficiary records.<br />

Take the appropriate actions as per CMS enrollment guidance.<br />

An EGHP Update transaction (Transaction Type 74) was accepted. This transaction changed the<br />

beneficiary’s EGHP flag.<br />

The EGHP Update transaction may have been submitted by the Plan or initiated by a CMS User.<br />

The value in TRR data record field 48 on the TRR record will contain the new EGHP flag. The<br />

effective date of the change is reported in field 18 of the TRR record <strong>and</strong> in the EFF DATE column<br />

on the printed report.<br />

All data provided for change other than the EGHP Flag fields has been ignored.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-37 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

140 A Segment ID<br />

Change<br />

Accepted<br />

141 A Uncovered<br />

Months<br />

Change<br />

Accepted<br />

143 A Secondary<br />

Insurance Rx<br />

Number<br />

Change<br />

Accepted<br />

SEGMENT ID<br />

CHG<br />

UNCOV MNTHS<br />

CHG<br />

4RX SCD INS<br />

CHG<br />

A Segment ID Update transaction (Transaction Type 77) was accepted. This transaction changed<br />

the Segment ID for the beneficiary.<br />

The value in TRR data record field 33 contains the new Segment ID. The effective date of the<br />

change is reported in field 18<br />

All data provided for change other than the Segment ID field has been ignored.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

A Number of Uncovered Months Record Update transaction (Transaction Type 73) was accepted.<br />

This transaction updated the creditable coverage information (Creditable Coverage Flag <strong>and</strong>/or<br />

Number of Uncovered Months) for the beneficiary.<br />

The values in TRR data record fields 40 <strong>and</strong> 41 on the TRR record will contain the new creditable<br />

coverage values. The effective date of the change is reported in field 18. Total uncovered months<br />

are displayed in field 24.<br />

All data provided for change, other than the Uncovered Months fields, has been ignored.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

A 4Rx Record Update transaction (Transaction Type 72) was accepted. This transaction updated<br />

the secondary drug insurance information (Secondary RxID, Secondary RxBIN, Secondary Rx<br />

Group, Secondary RxPCN) for the beneficiary. The 4Rx Record Update transaction may have been<br />

submitted by the Plan or initiated by a CMS User.<br />

The values in TRR data record fields 46, 47, 60 & 61 on the TRR record will contain the new<br />

secondary drug insurance information. The effective date of the change is reported in field 18.<br />

All data provided for change, other than the 4Rx fields, has been ignored.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-38 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

144 M PPO changed<br />

to Direct Bill<br />

150 I Enrollment<br />

accepted,<br />

Exceeds<br />

Capacity<br />

Limit<br />

PREM WH OPT<br />

CHG<br />

OVER CAP LIMIT<br />

CMS has changed the Premium Payment Option (PPO) specified on the transaction to “D – Direct<br />

Bill” for one of the following reasons:<br />

Retroactive premium withholding was requested.<br />

The beneficiary’s retirement system [Social Security Administration (SSA), RRB or Office of<br />

Personnel Management (OPM)] was unable to withhold the entire premium amount from the<br />

beneficiary’s monthly check.<br />

The beneficiary has a BIC of M or T <strong>and</strong> chose “SSA” as the withhold option. SSA cannot<br />

withhold premiums for these beneficiaries as there is no benefits check from which to<br />

withhold.<br />

The beneficiary chose “OPM” as the withhold option. OPM is not withholding premiums at<br />

this time.<br />

The Plan has submitted a Part C premium amount that exceeds the maximum Part C premium<br />

value provided by HPMS.<br />

RRB Withholding was requested for an effective date prior to 06/01/2011.<br />

The beneficiary is Out-of-Area for a segmented Contract/PBP.<br />

Retroactive premium withhold was requested <strong>and</strong> during one of the periods the beneficiary was<br />

Out-of-Area for a segmented Contract/PBP.<br />

This TRC may generate in response to an accepted Enrollment, PBP change, or PPO Change<br />

transaction (Transaction Types 61, 75) or CMS may initiate it.<br />

Plan Action: Update the Plan’s beneficiary records to reflect the direct bill payment method. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

Although a submitted enrollment or PBP change transaction (Transaction Type 61) was accepted,<br />

the resulting enrollment count exceeds the capacity limit for the contract or PBP.<br />

This TRC provides additional information about a new enrollment or PBP change (Transaction<br />

Type 61) for which an acceptance was sent in a separate TRR data record with an enrollment<br />

acceptance TRC. The effective date of the new enrollment for which this information is pertinent is<br />

reported in field 18.<br />

Plan Action: Follow the procedures in CMS enrollment guidance <strong>and</strong> contact your CMS Central<br />

Office Health Insurance Specialist.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-39 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

152 M Race Code<br />

Change<br />

154 M Out of Area<br />

Status<br />

155 M Incarceration<br />

Notification<br />

Received<br />

156 F Transaction<br />

Rejected,<br />

User Not<br />

Authrzed for<br />

Cntrct<br />

NEW RACE<br />

CODE<br />

OUT OF AREA<br />

INCARCERATED<br />

BAD USR FOR<br />

PLN<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has been notified that the beneficiary’s race code has changed. The effective date of the<br />

change is reported in TRR data file field 18. The new race code will be reported in the next<br />

Monthly Membership Detail Report (MMR).<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary’s information<br />

matches the data included in the TRR record.<br />

This TRC is returned either on a reply with Transaction Type 01 in response to a state <strong>and</strong> county<br />

code change or ZIP Code change. It is intended to supply the Plan with additional information about<br />

the beneficiary.<br />

In the case of the 01 transaction, CMS has information that the beneficiary is no longer in the Plan’s<br />

service area. This can be the result of:<br />

A change in the Plan’s service area <strong>and</strong> the beneficiary’s address is outside the new area<br />

A change in the beneficiary’s address which places them Out of area<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has been notified that the beneficiary is incarcerated. The effective date of the change is<br />

reported in TRR data file field 18.<br />

Plan Action: Contact the beneficiary to confirm the incarceration. Review full CMS guidance on<br />

enrollment of incarcerated beneficiaries in the MMCMor PDP Enrollment Guidance <strong>and</strong> take<br />

appropriate actions.<br />

This transaction (Transaction Types 01, 51, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) was failed<br />

because it was submitted by a user who is not authorized to submit transactions for the contract.<br />

This TRC will not be returned in the TRR.<br />

Plan Action: Resubmit using the correct submitter if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-40 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

157 R Contract Not<br />

Authorized<br />

for<br />

Transaction<br />

Code<br />

158 M Institutional<br />

Period<br />

Change/Canc<br />

ellation<br />

159 M NHC Period<br />

Change/Canc<br />

ellation<br />

162 R Invalid<br />

EGHP Flag<br />

Value<br />

165 R Processing<br />

delayed due<br />

to MARx<br />

system<br />

problems<br />

UNAUT<br />

REQUEST<br />

INST CHANGE<br />

NHC CHANGE<br />

BAD EGHP FLAG<br />

SYSTEM DELAY<br />

A transaction (Transaction Types 41, 51, 54, 61, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81) was rejected<br />

because the Plan is not authorized to submit that type of transaction.<br />

Plan Action: Correct the Transaction Type <strong>and</strong> resubmit if appropriate.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has changed or cancelled an Institutional period for the beneficiary.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has changed or cancelled a NHC period for the beneficiary.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

An enrollment or EGHP change transaction (Transaction Types 61, 74) was rejected because the<br />

submitted EGHP Flag value was invalid.<br />

The valid values for EGHP Flag is Y or blank for enrollment Transaction Type 61. Y or N id<br />

accepted for EGHP change Transaction Type 74.<br />

Plan Action: Correct the EGHP Flag value <strong>and</strong> resubmit if appropriate.<br />

Processing of this transaction has been delayed due to CMS system conditions. No action is required<br />

by the user. CMS will process the transaction as soon as possible.<br />

Plan Action: Wait for further information from CMS.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-41 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

166 R Part D FBD<br />

Auto Enroll<br />

or Facilitated<br />

Enroll Reject<br />

169 R Reinsurance<br />

Demonstratio<br />

n Enrollment<br />

Rejected<br />

170 I Premium<br />

Withhold<br />

Option<br />

Changed to<br />

Direct Billing<br />

171 R Record<br />

Update<br />

Rejected,<br />

Invalid Chg<br />

Effective Dt<br />

PARTD AUTO<br />

REJ<br />

EMP SUBSIDY<br />

PREM WH OPT<br />

CHG<br />

BAD CHG EFF<br />

DT<br />

A plan-submitted auto or facilitated Part D enrollment was rejected because CMS has a record of an<br />

‘opt out’ option on file for the beneficiary. This beneficiary has “opted out” of auto or facilitated<br />

enrollment.<br />

Plan Action: Update the Plan’s records to ensure that the beneficiary is not enrolled in the Plan.<br />

Take the appropriate actions as per CMS enrollment guidance.<br />

An enrollment transaction (Transaction Type 61) placing the beneficiary into a reinsurance<br />

demonstration Plan was rejected because the beneficiary has employer subsidy periods overlapping<br />

with the requested enrollment period.<br />

This TRC is equivalent to TRC 127 except that it applies to Reinsurance Demonstration <strong>Plans</strong> only.<br />

The requested effective date is reported in TRR data file field 18.<br />

Plan Action: Contact the beneficiary to explain the potential consequences of this enrollment. If<br />

the beneficiary elects to join the Part D plan anyway, the enrollment should be resubmitted with the<br />

Employer Subsidy Override Flag set to Y.<br />

The beneficiary’s PPO was changed to Direct Billing (D) because the beneficiary is a member of an<br />

employer group. Retirees who are members of an employer group cannot elect SSA withholding.<br />

This TRC provides additional information about an enrollment, PBP change, or PPO Change<br />

transaction (Transaction Types 61, 75) for which an acceptance was sent in a separate Transaction<br />

Reply with an enrollment acceptance TRC. The Effective Date of the enrollment for which this<br />

information is pertinent is reported in TRR data record field 18.<br />

Plan Action: Update the Plan’s billing method <strong>and</strong> contact the beneficiary to explain the<br />

consequences of this change.<br />

An EGHP Change, PPO Change, Segment ID Change, or Part C Premium Change (Transaction<br />

Types 74, 75, 77, 78) was rejected because the submitted transaction effective date was incorrect.<br />

The Effective Date on the Transaction Type 75 must be in the CPM to CPM+2 range.<br />

The Effective Date on the Transaction Types 78 must be in the CPM-3 to CPM+2 range.<br />

The Effective date on the Transaction Types 74, 76 must be in the CCM-1 to CCM+3 range.<br />

Plan Action: Correct the effective date <strong>and</strong> resubmit the transaction if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-42 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

172 R Change<br />

Rejected;<br />

Creditable<br />

Coverage/2<br />

<strong>Drug</strong> Info NA<br />

173 R Change<br />

Rejected;<br />

Premium Not<br />

Previously<br />

Set<br />

176 R Transaction<br />

Rejected,<br />

Another<br />

Transaction<br />

Accepted<br />

CRED COV/RX<br />

NA<br />

NO PREMIUM<br />

INFO<br />

TRANS REJ<br />

A 4RX or Number of Uncovered Months transaction (Transaction Type 72 or 73) was rejected<br />

because the information was not applicable to the selected plan type (Mas <strong>and</strong> other plans without<br />

drug coverage). Non-drug plans should not submit drug plan information.<br />

The inappropriate information included on the transaction could be any or all of the following:<br />

Creditable Coverage Information (Creditable Coverage Flag <strong>and</strong> Number of Uncovered<br />

Months)<br />

Primary <strong>Drug</strong> Insurance Information (Rx ID, Rx GRP, Rx PCN <strong>and</strong> Rx BIN)<br />

Secondary <strong>Drug</strong> Insurance Information (Secondary Insurance Flag, Rx ID, Rx GRP, Rx PCN<br />

<strong>and</strong> Rx BIN)<br />

Plan Action: Verify that the above fields are not populated <strong>and</strong> resubmit the transaction if<br />

appropriate.<br />

An Uncovered Months, PPO, or Part C premium amount change transaction (Transaction Types 73,<br />

75, 78) was rejected because the beneficiary’s premium was not established as of the transaction<br />

effective date.<br />

Plan Action: Review the beneficiary’s premium data <strong>and</strong> resubmit if appropriate.<br />

An enrollment transaction (Transaction Type 61) was rejected.<br />

A transaction enrolling the beneficiary into another contract was previously accepted. That<br />

transaction <strong>and</strong> this submitted one had the same effective <strong>and</strong> application dates.<br />

The beneficiary is not enrolled in the Plan in this newly submitted transaction.<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-43 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

177 M Change in<br />

Late<br />

Enrollment<br />

Penalty<br />

178 M Late<br />

Enrollment<br />

Penalty<br />

Rescinded<br />

179 A Transaction<br />

Accepted, No<br />

Change to<br />

Premium<br />

Record<br />

NEW PENALTY<br />

AMT<br />

PNLTY<br />

RESCINDED<br />

NO CHNG TO<br />

PREM<br />

This TRC is intended to supply the Plan with additional information about the beneficiary.<br />

The beneficiary’s total late enrollment penalty has changed. This may be the result of:<br />

A change to the beneficiary’s number of uncovered months (but there are still uncovered<br />

months);<br />

A change to the beneficiary’s LIS status;<br />

A new Initial Election Period (IEP); or<br />

The addition, withdrawal, or change in the CMS-granted waiver of penalty.<br />

Plan Action: Adjust the beneficiary’s payment amount. The new total penalty amount can be<br />

determined by subtracting amounts in TRR data record fields 53 (waived amount) <strong>and</strong> 54<br />

(subsidized amount) from field 52 (base penalty). Take the appropriate actions as per CMS<br />

enrollment guidance.<br />

This TRC is intended to supply the Plan with additional information about the beneficiary.<br />

The incremental number of uncovered months associated with the specified effective date has been<br />

rescinded to zero. The resulting LEP penalty amount reported in TRR data record field 52 (base<br />

penalty) is the computed penalty associated with all remaining periods of uncovered months.<br />

Plan Action: Adjust the beneficiary’s payment amount. Take the appropriate actions as per CMS<br />

enrollment guidance.<br />

A Record Update transaction (Transaction Type 73, 75, 78) was submitted, however, no data change<br />

was made to the beneficiary’s premium. The submitted transaction contained premium data values<br />

that matched those already on record with CMS for the specified period.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: Ensure that the Plan’s system reflects the amounts in the TRR record.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-44 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

182 I Invalid PTC<br />

Premium<br />

Submitted,<br />

Corrected<br />

184 R Enrollment<br />

Rejected,<br />

Beneficiary is<br />

in Medicaid<br />

PTC PRM<br />

OVERIDE<br />

MBR IN<br />

MEDICAID<br />

The Part C premium submitted on the enrollment, PBP change, Enrollment Cancellation,<br />

Disenrollment Cancellation or Part C Premium Record Update transaction (Transaction Types 61,<br />

78, 80, 81) does not agree with the Plan’s defined Part C premium rate. The premium has been<br />

adjusted to reflect the defined rate. The correct Part C premium rate is reported in TRR data record<br />

field 24.<br />

If the submitted Part C premium is less than the Basic Part C premium for the plan, MARx will reset<br />

the premium to the Part C Basic plus M<strong>and</strong>atory Supplemental Premium Rate, Net of Rebate from<br />

the HPMS file.<br />

This TRC provides additional information about an enrollment, PBP change, Enrollment<br />

Cancellation, Disenrollment Cancellation or Part C Premium Record Update transaction<br />

(Transaction Types 61, 78, 80, 81) for which an acceptance was sent in a separate Transaction Reply<br />

with an enrollment acceptance TRC. The effective date of the enrollment for which this information<br />

is pertinent is reported in TRR data record field 18.<br />

Plan Action: Update the Plan’s beneficiary records with the premium information in the TRR<br />

record. Take the appropriate actions as per CMS enrollment guidance.<br />

An enrollment transaction (Transaction Type 61) was rejected because the beneficiary was in<br />

Medicaid status <strong>and</strong> the Plan is not eligible to enroll Medicaid beneficiaries.<br />

This TRC is Plan specific. It only applies to MSA/MA <strong>and</strong> MSA/Demo plans.<br />

Plan Action: Update the Plan’s beneficiary records to reflect the fact that the beneficiary is not<br />

enrolled in the Plan. Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-45 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

185 M Withholding<br />

Agency<br />

Accepted<br />

Transaction<br />

ACCEPTED<br />

CMS submitted information on a beneficiary to SSA/RRB (See TRC 120). TRC 185 is sent to the<br />

Plan when SSA/RRB acknowledges that they have accepted <strong>and</strong> processed the beneficiary data.<br />

If the submittal to SSA/RRB was the result of a requested premium withholding change, TRC 185<br />

informs the Plan that SSA/RRB has accepted <strong>and</strong> processed the change. The beneficiary’s PPO is<br />

reported in DTRR field 39. The effective date of the PPO change is reported in field 18.<br />

Note: The reported new PPO may be the same as the existing PPO.<br />

<strong>Plans</strong> will not see the results of any requested premium withholding changes until TRC 185 is<br />

received.<br />

186 I Withholding<br />

Agency<br />

Rejected<br />

Transaction<br />

REJECTED<br />

Plan Action: Ensure the Plan’s system matches the information, primarily the PPO, included in the<br />

DTRR.<br />

CMS submitted information on a beneficiary to SSA/RRB (See TRC 120). This data transmittal<br />

was rejected by SSA/RRB.<br />

This is exclusive to the communication between CMS <strong>and</strong> SSA/RRB. CMS will continue to<br />

interface with SSA/RRB to resolve the rejection.<br />

If CMS is unable to resolve this rejection <strong>and</strong> the Beneficiary-requested PPO is changed, the Plan<br />

may receive a TRC 144.<br />

187 R No Change in<br />

Number of<br />

Uncovered<br />

Mths<br />

Information<br />

DUP NO UNCV<br />

MTH<br />

Plan Action: No action required.<br />

A Number of Uncovered Months Record Change transaction (Transaction Type 73) was rejected.<br />

No data change was made to the beneficiary’s record. The submitted transaction contained Number<br />

of Uncovered Months Information that matched those already on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-46 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

188 A No Change in<br />

Segment ID<br />

189 A No Change in<br />

EGHP Flag<br />

190 A No Change in<br />

Secondary<br />

<strong>Drug</strong><br />

Information<br />

DUP SEGMENT<br />

ID<br />

DUP EGHP FLAG<br />

DUP SECNDARY<br />

RX<br />

A Segment ID Update transaction (Transaction Type 77) was accepted, however, no data change<br />

was made to the beneficiary’s record. The submitted transaction contained a Segment ID value that<br />

matched the Segment ID already on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required.<br />

An EGHP Record Update transaction (Transaction Type 74) was submitted, however, no data<br />

change was made to the beneficiary’s record. The submitted transaction contained an EGHP Flag<br />

value that matched the EGHP Flag already on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required.<br />

A 4Rx Record Update transaction (Transaction Type 72) was submitted, however, no data change<br />

was made to the beneficiary’s record. The submitted transaction contained Secondary <strong>Drug</strong><br />

Insurance Information (Secondary <strong>Drug</strong> Insurance flag, Secondary Rx ID, Secondary Rx Group,<br />

Secondary Rx BIN, Secondary Rx PCN) that matched the Secondary <strong>Drug</strong> Insurance values already<br />

on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-47 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

191 A No Change in<br />

Premium<br />

Withhold<br />

Option<br />

DUP PRM WH<br />

OPTN<br />

A PPO Change transaction (Transaction Type 75) was submitted, however, no data change was<br />

made to the beneficiary’s record for one of the following reasons:<br />

1. The submitted transaction contained a PPO value that matched the PPO already on record<br />

with CMS.<br />

2. Beneficiary has a premium. Setting the PPO to “no premium”, “N”, is not acceptable.<br />

Beneficiary premium may be due wholly or in part to a late enrollment penalty.<br />

3. Beneficiary premiums are zero. Withholding cannot be established.<br />

4 .A PPO request of ‘Deduct from SSA (S)’ or ‘Deduct from RRB (R)’ was submitted on a<br />

PPO Change transaction (Transaction Type 75) when the beneficiary has ‘No Premiums’. The<br />

PPO was set to ‘N’, which matches the PPO already on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-48 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

194 M Deemed<br />

Correction<br />

DEEMD CORR<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS has manually added or updated a co-pay period for this beneficiary. This added or updated<br />

co-pay period occurs within a period during which the beneficiary is DEEMED by CMS. This is a<br />

correction.<br />

Each TRC 194 returns start <strong>and</strong> end dates, premium subsidy percentage, <strong>and</strong> copayment category<br />

for one low income subsidy period affecting a beneficiary’s PBP enrollment. There may be more<br />

than one TRC 194 returned. The effective date for the added or updated deemed low-income<br />

subsidy period is shown in the Transaction Reply Report data record Low-Income Period Effective<br />

Date field (field 51). The new co-pay level is reported in the Low-Income Co-Pay Category field<br />

(field 50). The Effective Date field (field 18) contains the PBP enrollment period start date.<br />

Low income scenarios TRC 121 <strong>and</strong>/or TRC 223 may accompany TRC 194. These three TRCs<br />

convey the beneficiary’s low income subsidy profile at the time of report generation. They provide<br />

a full replacement set of low income subsidy data affecting the identified PBP enrollment period.<br />

This code is considered obsolete as of 1/1/2010.<br />

195 M SSA<br />

Unsolicited<br />

Response<br />

SSA WHOLD<br />

UPDT<br />

Plan Action: Update the Plan’s records to reflect the given data for the beneficiary’s LIS period.<br />

Take the appropriate actions as per CMS enrollment guidance.<br />

An unsolicited response has been received from SSA. The PPO for this beneficiary is set to Direct<br />

Bill. This action is not in response to a Plan-initiated transaction.<br />

The effective date of the change is reported in TRR data record field 18.<br />

Plan Action: Change the beneficiary to direct bill as of the effective date in field 18. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-49 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

196 R Transaction<br />

Rejected,<br />

Bene not<br />

Eligible for<br />

Part D<br />

197 M Part D<br />

Eligibility<br />

Termination<br />

NO PART D<br />

PART D OFF<br />

An enrollment transaction or PBP change transaction (Transaction Type 61) or disenrollment<br />

cancellation transaction (Transaction Type 81) [enrollment reinstatement] was rejected. Part D<br />

eligibility is required for Part D plan enrollment.<br />

TC61 – transaction was rejected because the submitted enrollment date is outside the<br />

beneficiary’s Part D eligibility period<br />

TC81 – transaction was rejected because the enrollment reinstatement period is outside the<br />

beneficiary’s Part D eligibility period<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

This TRC is returned on a reply with Transaction Type 01 <strong>and</strong> occasionally with Transaction Type<br />

51 <strong>and</strong> Transaction Type 61. When returned with Transaction Type 01, the TRC is in response to a<br />

change in beneficiary Part D Eligibility. It is not a reply to a submitted transaction but is intended to<br />

supply the Plan with additional information about the beneficiary.<br />

In the case of Transaction Type 01, this beneficiary’s Part D eligibility has been terminated. The<br />

effective date of the termination is reported in TRR data record fields 18 <strong>and</strong> 24.<br />

If applicable, CMS will automatically disenrolls the beneficiary from the plan. A Transaction Type<br />

51 transaction will be sent in this or another TRR.<br />

When this TRC is returned with Transaction Type 61 the TRC is in response to a retroactive<br />

enrollment <strong>and</strong> is identifying the fact that an enrollment end date has been established due to the<br />

beneficiary’s termination of Part D. The enrollment start date is in TRR data record field 18 <strong>and</strong> the<br />

enrollment end date is in field 24. In this circumstance it is accompanied by TRC 018, Automatic<br />

Disenrollment, as well.<br />

Note: A TRR record with this reply code is only reported to the Plan in which the beneficiary is<br />

currently enrolled, even if it affects periods of enrollment in other <strong>Plans</strong>.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-50 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

198 M Part D<br />

Eligibility<br />

Reinstatemen<br />

t<br />

200 R Rx BIN<br />

Blank or Not<br />

Valid<br />

201 R Rx ID Blank<br />

or Not Valid<br />

202 R Rx Group<br />

Not Valid<br />

PART D ON<br />

BIN<br />

BLANK/INVLD<br />

ID<br />

BLANK/INVLID<br />

RX GRP INVALID<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary’s Part D eligibility has been reinstated. The effective date Part D eligibility start<br />

date is reported in TRR data record fields 18 <strong>and</strong> 24.<br />

Note: A TRR record with this reply code is only reported to the Plan in which the beneficiary is<br />

currently enrolled, even if it affects periods of enrollment in other <strong>Plans</strong>. If, as a result of a loss of<br />

Part D eligibility, the beneficiary has been disenrolled, but not re-enrolled, the reply code is not<br />

issued.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

An enrollment transaction or 4Rx change transaction (Transaction Types 61, 72) was rejected<br />

because the primary drug insurance Rx BIN field was either blank or did not have a valid value.<br />

Exception: Rx Bin for primary drug insurance is not a m<strong>and</strong>atory field for enrollments transactions<br />

for PACE National Part D plans.<br />

Plan Action: Correct the Primary Rx BIN value <strong>and</strong> resubmit the transaction if appropriate.<br />

An enrollment transaction or 4Rx change transaction (Transaction Types 61, 72) was rejected<br />

because the primary drug insurance Rx ID field was either blank or does not have a valid value.<br />

Exception: Rx ID for primary drug insurance is not a m<strong>and</strong>atory field for enrollments transactions<br />

for PACE National Part D plans.<br />

Plan Action: Correct the Primary Rx ID value <strong>and</strong> resubmit the transaction if appropriate.<br />

An enrollment transaction or 4Rx change transaction (Transaction Types 61, 72) was rejected<br />

because the primary drug insurance Rx GRP field does not have a valid value.<br />

Plan Action: Correct the Primary Rx GRP value <strong>and</strong> resubmit the transaction if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-51 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

203 R Rx PCN Not<br />

Valid<br />

204 A Record<br />

Update for<br />

Primary 4Rx<br />

Data<br />

Successful<br />

205 I Invalid<br />

Disenrollmen<br />

t Reason<br />

Code<br />

206 I Part C<br />

Premium has<br />

been<br />

corrected to<br />

zero<br />

RX PCN INVALID<br />

4RX CHNG<br />

ACPTED<br />

INV DISENRL<br />

RSN<br />

PTC PREM<br />

ZEROED<br />

An enrollment or 4Rx change transaction (Transaction Types 61, 72) was rejected because the<br />

primary drug insurance Rx PCN field does not have a valid value.<br />

Plan Action: Correct the Primary Rx PCN value <strong>and</strong> resubmit the transaction if appropriate.<br />

A submitted 4Rx Record Update transaction (Transaction Type 72) included a request to change<br />

primary drug insurance 4Rx data. The 4Rx data were successfully changed.<br />

Note: At a minimum, values must be provided for both of the m<strong>and</strong>atory primary 4Rx fields, RX<br />

BIN <strong>and</strong> RX ID<br />

Plan Action: No action required.<br />

A disenrollment transaction (Transaction Type 51) was submitted with a blank or invalid<br />

disenrollment reason code. CMS substituted the default value of ‘99’ for the disenrollment reason<br />

code.<br />

See Page I-103 for CMS enrollment guidance regarding valid disenrollment reason codes.<br />

This TRC provides the Plan with additional information on a disenrollment that was processed<br />

successfully. It is received in addition to the appropriate disenrollment acceptance TRC.<br />

Plan Action: None required.<br />

An enrollment, PBP change or Part C Premium Update transaction (Transaction Types 61, 78) was<br />

submitted <strong>and</strong> accepted for a Part D only Plan. This transaction contained an amount other than<br />

zero in the Part C premium field. Since a Part C premium does not apply to a Part D only Plan, the<br />

Part C premium has been corrected to be zero.<br />

This TRC provides additional information about an enrollment, PBP change, or Part C Premium<br />

Update transaction (Transaction Types 61, 78) for which an acceptance was sent in a separate<br />

Transaction Reply with an acceptance TRC. The effective date of the enrollment for which this<br />

information is pertinent is reported in TRR data record field 18.<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary’s information<br />

matches zero Part C premium amount included in the TRR record.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-52 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

209 R 4Rx Change<br />

Rejected,<br />

Invalid<br />

Change<br />

Effective<br />

Date<br />

210 A POS<br />

Enrollment<br />

Accepted<br />

211 R Re-<br />

Assignment<br />

Enrollment<br />

Rejected<br />

212 A Re-<br />

Assignment<br />

Enrollment<br />

Accepted<br />

NO ENROLL<br />

MATCH<br />

POS<br />

ENROLLMENT<br />

RE-ASN ENRL<br />

REJ<br />

REASSIGN<br />

ACCEPT<br />

A 4Rx change transaction (Transaction Type 72) for 4Rx information for primary drug insurance<br />

was rejected because the beneficiary was not enrolled as of the submitted transaction effective date.<br />

<strong>Plans</strong> may only submit 4Rx data for periods when the beneficiary is enrolled in the Plan.<br />

Plan Action: Correct the dates <strong>and</strong> resubmit the transaction if appropriate.<br />

An enrollment into a POS designated Part D plan that was submitted by a Point Of Sale (POS/POS<br />

10) contractor or CMS (MBD) has been successfully processed. The effective date of the new<br />

enrollment is shown in the Effective Date (field 18) of the TRR data record. The date in field 18<br />

will always be the first day of the month.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

A reassignment enrollment request transaction (Transaction Type 61) which would move the<br />

beneficiary into another Part D plan was rejected because CMS has record of an “Opt-Out” option<br />

on file for the beneficiary. The beneficiary has ‘opted out’ of auto or facilitated enrollment.<br />

Plan Action: Do not move the beneficiary’s enrollment to the new Plan. Keep the beneficiary in<br />

the Plan in which they are currently enrolled. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

A reassignment enrollment request transaction (Transaction Type 61) to move the beneficiary into a<br />

new Part D Plan has been successfully processed. The beneficiary has been moved from the<br />

original contract <strong>and</strong> PBP to the new contract <strong>and</strong> PBP. The effective date of enrollment in the new<br />

PBP is reported in fields 18 <strong>and</strong> 24 of the TRR data record.<br />

Other accompanying replies with different TRCs may give additional information about this<br />

accepted reassignment.<br />

Field 20 (Plan Benefit Package ID) contains the new PBP identifier <strong>and</strong> the old PBP is reported in<br />

field 29 (Prior Plan Benefit Package ID).<br />

Plan Action: Update the Plan’s records accordingly with the information in the TRR record,<br />

ensuring that the Plan’s beneficiary’s information reflects enrollment in the new contract <strong>and</strong> PBP.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-53 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

213 I Premium<br />

Withhold<br />

Exceeds<br />

Safety Net<br />

Amount<br />

215 R Uncovered<br />

Months Chng<br />

Rejected,<br />

Incorrect Eff<br />

Date<br />

216 I Uncovered<br />

months<br />

exceeds max<br />

possible<br />

value<br />

217 R Cant Change<br />

number of<br />

uncovered<br />

months<br />

EXCEED SNET<br />

AMT<br />

BAD NUNCMO<br />

EFF<br />

NUNCMO EXDS<br />

MAX<br />

CANT CHG<br />

NUNCMO<br />

CMS has changed the PPO specified on the transaction to “D – Direct Bill” because the transaction<br />

would result in SSA withholding exceeding the Safety Net amount from the beneficiary’s check in<br />

one month.<br />

This TRC may be generated in response to an accepted enrollment or PBP change (Transaction<br />

Type 61), NUNCMO Record Update (Transaction Type 73), Part C Premium Update (Transaction<br />

Type 78), PPO Change (Transaction Type 75), or may be initiated by CMS.<br />

Plan Action: Change the beneficiary to Direct Bill <strong>and</strong> contact them to explain the consequences of<br />

the PPO change. Take the appropriate actions as per CMS enrollment guidance.<br />

A NUNCMO Change (Transaction Type 73) transaction was rejected because the submitted<br />

effective date is incorrect. The date may have been incorrect for one of the following reasons:<br />

The submitted effective date is prior to August 1, 2006;<br />

The submitted effective date is after the Current Calendar Month (CCM) plus 3; or<br />

The submitted effective date falls within a Part D plan enrollment but does not match the<br />

contract enrollment start date.<br />

Plan Action: Correct the effective date <strong>and</strong> resubmit the transaction if appropriate. If the Plan is<br />

trying to correct the uncovered months value for a beneficiary who is no longer enrolled in the Plan,<br />

contact their CMS Representative.<br />

The NUNCMO provided on an accepted enrollment transaction (Transaction Type 61) exceeds the<br />

maximum possible value.<br />

This will NOT cause the rejection of the enrollment transaction but zero uncovered months (000) is<br />

associated with the effective date of the enrollment.<br />

This informational TRC is generated in addition to the transaction’s acceptance TRC.<br />

Plan Action: Update the Plan’s beneficiary records to reflect the zero uncovered months. If the<br />

NUNCMO should be another value, review CMS enrollment guidance <strong>and</strong> correct the NUNCMO<br />

value using a new NUNCMO Record Update (Transaction Type 73) transaction.<br />

An uncovered months change transaction (Transaction Type 73) was rejected because the submitted<br />

transaction attempted to change the number of uncovered months for an effective date<br />

corresponding to a “LEP Reset” transaction in the CMS database.<br />

Plan Action: Review CMS enrollment guidance. If appropriate, submit a Number of Uncovered<br />

Months Record Update transaction (Transaction Type 73) to UNDO the LEP Reset.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-54 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

218 M LEP Reset<br />

Undone<br />

219 M LEP Reset<br />

Accepted<br />

220 R Transaction<br />

Rejected;<br />

Invalid POS<br />

Enroll Source<br />

CD<br />

222 I Bene<br />

Excluded<br />

from<br />

Transmission<br />

to SSA/RRB<br />

LEP RESET<br />

UNDNE<br />

LEP RESET<br />

BAD POS<br />

SOURCE<br />

BENE<br />

EXCLUSION<br />

CMS has reestablished the beneficiary’s late enrollment penalty (LEP). The previous LEP RESET<br />

was removed.<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary’s LEP<br />

information matches the data included in the TRR record. Take the appropriate actions as per CMS<br />

enrollment guidance.<br />

CMS has reset the beneficiary’s number of uncovered months to zero. The Late Enrollment Penalty<br />

(LEP) amount is now zero.<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary’s LEP<br />

information matches the data included in the TRR record. Take the appropriate actions as per CMS<br />

enrollment guidance.<br />

Enrollment source code submitted by a POS/POS 10 contractor for a POS/POS 10 enrollment<br />

transaction was other than ‘G’. Transaction rejected.<br />

Plan Action: Correct the Enrollment Source Code <strong>and</strong> resubmit transaction if appropriate.<br />

This TRC can be returned on a reply with various Transaction Types (51, 61, 73, 78) <strong>and</strong> the<br />

maintenance Transaction Type (01). It is intended to supply the Plan with additional information<br />

about the beneficiary.<br />

CMS has excluded beneficiary from transmission to SSA/RRB.<br />

Plan Action: None required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-55 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

223 M Low Income<br />

Period<br />

Removed<br />

from<br />

Enrollment<br />

Period<br />

LIS REMOVED<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary. It is<br />

returned for each low income subsidy period removed <strong>and</strong> not replaced over the course of a PBP<br />

enrollment.<br />

The enrollment period description is identified in Field 66 with a ‘C’ for current enrollees, ‘P’ for<br />

prospective enrollees, <strong>and</strong> ‘Y’ for previous enrollees.<br />

The beneficiary’s Low-Income Subsidy source will be identified in Field 65 with an ‘A’ for<br />

Approved SSA Applicants or a ‘D’ for Deemed beneficiary by CMS.<br />

The following LIS information is displayed on the Transaction Reply Report (TRR) for TRC 223:<br />

PBP Enrollment Effective Date (Field 18)<br />

Part D Low-income Premium Subsidy Level (Field 49)<br />

Low-income Co-Pay Category (Field 50)<br />

Low-income Period start date (Field 51)<br />

Low-income Period End Date (Field 64)<br />

Low-income Period Subsidy Source (Field 65)<br />

Enrollment Period Description (Field 66)<br />

Low income subsidy TRC 121 may accompany TRC 223. These three TRCs convey the<br />

beneficiary’s low income subsidy profile at the time of report generation. They provide a full<br />

replacement set of low income subsidy data affecting the PBP enrollment period.<br />

Plan Action: Update the Plan’s records to reflect the given data for the beneficiary’s LIS period.<br />

Take the appropriate actions as per CMS enrollment guidance.<br />

224 A A/D MSP<br />

Beneficiary<br />

Transaction<br />

Accepted<br />

MSP ACCEPTED<br />

Aged/Disabled MSP Beneficiary transaction (85) accepted.<br />

Plan Action: None Required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-56 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

225 I Exceeds SSA<br />

Benefit &<br />

Safety Net<br />

Amount<br />

INSUF<br />

FUND&SNET<br />

CMS has changed the PPO specified on the transaction to “D – Direct Bill” because the transaction<br />

would result in the SSA benefit being insufficient to cover the withholding <strong>and</strong> the withholding<br />

would exceed the Safety Net amount.<br />

This TRC may be generated in response to an accepted enrollment or PBP change (Transaction<br />

Type 61), NUNCMO Record Update (Transaction Type 73), Part C Premium Update (Transaction<br />

Type 78), PPO Change (Transaction Type 75), or may be initiated by CMS.<br />

235 I SSA<br />

Accepted Part<br />

B Reduction<br />

Transaction<br />

236 I SSA Rejected<br />

Part B<br />

Reduction<br />

Transaction<br />

SSA PT B<br />

ACCEPT<br />

SSA PT B REJECT<br />

Plan Action: Change the beneficiary to direct bill <strong>and</strong> contact them to explain the consequences of<br />

the PPO change. Take the appropriate actions as per CMS enrollment guidance.<br />

CMS submitted Part B Reduction information on a beneficiary to SSA (See TRC 237). TRC 235 is<br />

sent to the Plan when SSA acknowledges that they have accepted <strong>and</strong> processed the beneficiary<br />

data.<br />

If the submittal to SSA was the result of a requested Part B Reduction change, TRC 235 informs the<br />

Plan that SSA has accepted <strong>and</strong> processed the change.<br />

<strong>Plans</strong> will not see the results of any requested Part B Reduction changes until TRC 235 is received.<br />

Plan Action: No action required.<br />

CMS submitted Part B Reduction information on a beneficiary to SSA (See TRC 237). This data<br />

transmittal was rejected by SSA.<br />

This is exclusive to the communication between CMS <strong>and</strong> SSA. CMS will continue to interface<br />

with SSA to resolve the rejection.<br />

Plan Action: No action required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-57 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

237 I Part B<br />

Premium<br />

Reduction<br />

Sent to SSA<br />

PT B RED<br />

UPDATE<br />

As a result of an accepted Plan-submitted transaction (Transaction Types 51, 61, 72, 73, 75, 78) or<br />

UI update to a beneficiary’s records, information has been forwarded to SSA to update SSA records<br />

<strong>and</strong> implement any requested Part B premium reduction changes.<br />

Any requested change will not take effect until an SSA acceptance is received. <strong>Plans</strong> are notified of<br />

the SSA acceptance with a TRC 235 on a future TRR.<br />

Plan Action: None required. Take the appropriate actions as per CMS enrollment guidance.<br />

240 A Transaction<br />

Received,<br />

Withholding<br />

Pending<br />

241 I No Change in<br />

Part D Opt<br />

Out Flag<br />

WHOLD UPDATE<br />

DUP PTD OPT<br />

OUT<br />

Note: The Plan will not see the result of any Part B Reduction change until they have received a<br />

TRC 235 on a future TRR.<br />

As a result of an accepted Plan-submitted transaction to update a beneficiary’s PPO (Transaction<br />

Type 75) or a UI update of same, a request will soon be forwarded to SSA.<br />

<strong>Plans</strong> will receive TRC 120 when this request is forwarded to SSA. <strong>Plans</strong> are notified of the<br />

subsequent SSA acceptance or rejection of the PPO change with a TRC 185 or 186, respectively, on<br />

a future TRR.<br />

All data provided for change other than the PPO field was ignored.<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

Note: The Plan will not see the result of any PPO change until they have received a TRC 185 on a<br />

future TRR.<br />

A Part D Opt-Out Record Update transaction (Transaction Type 79) was submitted, however, no<br />

data change was made to the beneficiary’s record. The submitted transaction contained a Part D Opt<br />

Out Flag value that matched the Part D Opt Out Flag already on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-58 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

242 I No Change in<br />

Primary <strong>Drug</strong><br />

Information<br />

DUP PRIMARY<br />

RX<br />

A 4Rx Record Update transaction (72) was submitted, however, no data change was made to the<br />

beneficiary’s record. The submitted transaction contained Primary <strong>Drug</strong> Insurance Information<br />

(Primary Rx ID, Primary Rx Group, Primary Rx BIN, Primary Rx PCN) that matched the Primary<br />

<strong>Drug</strong> Insurance values already on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

243 R Change to<br />

SSA<br />

Withholding<br />

rejected due<br />

to no SSN<br />

NO SSN AT CMS<br />

Plan Action: None required.<br />

A PPO Change transaction (Transaction Type 75) was submitted to change the beneficiary’s PPO to<br />

SSA withholding, however, there is no Social Security Number (SSN) on file at CMS. The<br />

beneficiary’s PPO is not changed to SSA withholding.<br />

The beneficiary’s records were unchanged.<br />

245 M Member has<br />

MSP period<br />

252 I Prem<br />

Payment<br />

Option<br />

Changed to<br />

Direct Bill;<br />

No SSN<br />

253 M Changed to<br />

Direct Bill;<br />

no Funds<br />

Withheld<br />

MEMBER IS MSP<br />

W/O CHG;NO<br />

SSN<br />

W/O CHG;NO<br />

W/H<br />

Plan Action: Update the Plan’s beneficiary record accordingly. Take the appropriate action with<br />

member as per CMS enrollment guidance.<br />

The beneficiary has other insurance <strong>and</strong> <strong>Medicare</strong> is secondary payer.<br />

All plans whose payments are impacted by the MSP notification will receive the TRC.<br />

Plan Action: Update the Plan’s records accordingly.<br />

CMS has changed the PPO specified on the transaction to “D – Direct Bill” because the beneficiary<br />

does not have a Social Security number on file at CMS.<br />

This TRC may be generated in response to an accepted Enrollment, PBP change or PPO Change<br />

transaction (Transaction Types 61 or, 75) or may be initiated by CMS.<br />

Plan Action: Update the Plan’s beneficiary records to reflect the direct bill payment method. Take<br />

the appropriate actions with member as per CMS enrollment guidance.<br />

CMS has changed the PPO to “D-Direct Bill” because no funds have been withheld by the<br />

withholding agency in the two months since withholding was accepted.<br />

Plan Action: Update the Plan’s beneficiary records to reflect the direct bill payment method. Take<br />

the appropriate actions with member as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-59 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

254 I Beneficiary<br />

set to Direct<br />

Bill, spans<br />

jurisdiction<br />

DIR BIL<br />

JRSDCTN<br />

CMS has changed the PPO to “D-Direct Bill” because the withholding request spans two different<br />

withholding agency jurisdictional periods. This could occur for one of the following reasons:<br />

SSA is the beneficiary’s current withholding agency but the withholding request contains<br />

one or more periods from when RRB was the beneficiary’s withholding agency.<br />

RRB is the beneficiary’s current withholding agency but the withholding request contains<br />

one or more periods from when SSA was the beneficiary’s withholding agency.<br />

255 I Plan<br />

Submitted<br />

RRB W/H for<br />

SSA<br />

Beneficiary<br />

256 I Plan<br />

Submitted<br />

SSA W/H for<br />

RRB<br />

Beneficiary<br />

257 F Failed; Birth<br />

Date Invalid<br />

for Database<br />

Insertion<br />

RRB WHOLD 4<br />

SSA<br />

SSA WHOLD 4<br />

RRB<br />

Plan Action: Update the Plan’s beneficiary records to reflect the Direct Bill payment method.<br />

Take the appropriate actions with member as per CMS enrollment guidance.<br />

CMS has changed the PPO to “S-SSA Withhold” because SSA is the correct withholding agency for<br />

this beneficiary.<br />

Plan Action: None required.<br />

CMS has changed the PPO to “R-RRB Withhold” because RRB is the correct withholding agency<br />

for this beneficiary.<br />

Plan Action: None required.<br />

INVALID DOB An Enrollment transaction (Transaction Type 61), change transaction (Transaction Types 72, 73, 74,<br />

75, 77, 78, 79), residence address transaction (Transaction Type 76), or cancellation transaction<br />

(Transaction Types 80, 81) failed because the submitted birth date was either<br />

Not formatted as YYYYMMDD (e.g., “Aug 1940”), or<br />

Formatted correctly but contained a nonexistent month or day (e.g., “19400199”).<br />

As a result, the beneficiary could not be identified. The transaction record will not appear on the<br />

TRR (TRR) data file but will be returned on the Batch Completion Status Summary (BCSS) data<br />

file along with the failed record.<br />

Plan Action: Correct the date format <strong>and</strong> resubmit transaction.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-60 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

258 F Failed; Efctv<br />

Date Invalid<br />

for Database<br />

Insertion<br />

INVALID EFF DT<br />

A disenrollment transaction (Transaction Types 51, 54), enrollment transaction (Transaction Type<br />

61), change transaction (Transaction Types 72, 73, 74, 75, 77, 78, 79), residence address transaction<br />

(Transaction Type 76), or cancellation transaction (Transaction Types 80, 81) failed because the<br />

submitted effective date was either,<br />

Blank,<br />

Not formatted as YYYYMMDD (e.g., “Aug 1940”), or<br />

Formatted correctly but contained a nonexistent month or day (e.g., “19400199”).<br />

The transaction record does not appear on the TRR data file is returned on the BCSS data file along<br />

with the failed record.<br />

259 F Failed; End<br />

Date Invalid<br />

for Database<br />

Insertion<br />

INVALID END<br />

DT<br />

Plan Action: Correct the date format <strong>and</strong> resubmit transaction.<br />

A residence address transaction (Transaction Type 76) failed because the submitted end date was<br />

either not formatted as YYYYMMDD (e.g., “Aug 1940”) or was formatted correctly but contained a<br />

nonexistent month or day (e.g., “19400199”). The transaction record does not appear on the TRR<br />

data file is returned on the BCSS data file along with the failed record.<br />

260 R Rejected; Bad<br />

End Date on<br />

Residence<br />

Address<br />

Change<br />

BAD RES END<br />

DT<br />

Plan Action: Correct the date format <strong>and</strong> resubmit transaction.<br />

A residence address transaction (Transaction Type 76) was rejected because the End Date is not<br />

appropriate for one or more of the following reasons:<br />

It is earlier than address change start date,<br />

It is not the last day of the month, or<br />

It is not within the contract enrollment period.<br />

Plan Action: Correct the End Date <strong>and</strong> resubmit.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-61 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

261 R Rejected;<br />

Incomplete<br />

Residence<br />

Address<br />

Information<br />

BAD RES ADDR<br />

A residence address transaction (Transaction Type 76) was rejected for one of the following<br />

reasons:<br />

The residence address information was incomplete –<br />

Residence Address Line 1 was empty,<br />

Residence City was empty,<br />

USPS state code was missing,<br />

Residence zip code was missing or non-numeric,<br />

The value specified for the Address Update/Delete Flag was blank or not valid,<br />

The supplied residence address information could not be resolved in terms of identifiable<br />

address components, or<br />

The address was not a U.S. address.<br />

262 R Bad RRB<br />

Premium<br />

Withhold<br />

Effective<br />

Date<br />

263 F Failed;<br />

Aplctn Date<br />

Invalid for<br />

Database<br />

Insertion<br />

264 I Payment Not<br />

Yet<br />

Completed<br />

INVALID EFF<br />

DTE<br />

INVALID APP DT<br />

NO PAYMENT<br />

Plan Action: Correct address information <strong>and</strong> resubmit.<br />

A PPO Change Transaction (Transaction Type 75) was rejected because request for RRB<br />

withholding is NOT allowed for effective date prior to 6/1/2011.<br />

Plan Action: Correct the Effective date <strong>and</strong> resubmit.<br />

An enrollment transaction (Transaction Type 61) failed <strong>and</strong> did not process because the submitted<br />

application date was either not formatted as YYYYMMDD (e.g., “Aug 1940”) or was formatted<br />

correctly but contained a nonexistent month or day (e.g., “19400199”). The transaction record does<br />

not appear on the TRR data file is returned on the BCSS data file along with the failed record.<br />

Plan Action: Correct the date format <strong>and</strong> resubmit transaction.<br />

A transaction was accepted requiring a payment calculation. This calculation was not completed.<br />

Plan Action: No action is required.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-62 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

265 A Residence<br />

Address<br />

Change<br />

Accepted,<br />

New SCC<br />

266 R Unable to<br />

Resolve SSA<br />

State County<br />

Codes<br />

267 M PPO set to N<br />

due to No<br />

Premium<br />

268 I Beneficiary<br />

Has Dialysis<br />

Period<br />

RES ADR SCC<br />

SCC<br />

UNRESOLVED<br />

PPO SET TO N<br />

DIALYSIS<br />

EXISTS<br />

A residence address change transaction (Transaction Type 76) was accepted. This beneficiary’s<br />

state <strong>and</strong> county code (SCC) information may have changed. SCC values are returned in TRR data<br />

record fields 9 (state code) <strong>and</strong> 10 (county code) <strong>and</strong> together in field 24. The residence address<br />

period start date is in field 18. Any provided end date is in field 24.<br />

This TRC is accompanied by TRC 085 if the submitted residence address has changed the<br />

beneficiary’s SCC.<br />

This TRC may be accompanied by TRC 154 if the submitted residence address has placed the<br />

beneficiary outside the plan’s service area.<br />

Plan Action: Update the Plan’s records.<br />

A residence address transaction (Transaction Type 76) was rejected because SSA state <strong>and</strong> county<br />

codes (SCC) could not be resolved. The beneficiary’s residence address was not changed.<br />

Plan Action: Confirm the address specified in the transaction. Update <strong>and</strong> resubmit the transaction<br />

if necessary; otherwise, contact your district office for assistance.<br />

The beneficiary’s PPO was set to N because their premium is $0. This occurs as part of an end-ofyear<br />

process based on the Plan’s basic Part C premium for the upcoming year.<br />

Plan action: Submit a transaction to reset the Part C premium <strong>and</strong> to renew a request for<br />

withholding status if appropriate.<br />

This TRC is returned on an enrollment. It is intended to supply the Plan with additional information<br />

about the beneficiary. Each TRC 268 returns start <strong>and</strong> end dates for each dialysis period that<br />

overlaps the enrollment period. There may be more than one TRC 268 returned.<br />

The effective date for the dialysis period is shown in the Effective Date field (field 18). The end<br />

date, if one exists, is in the Open Data field (field 24).<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-63 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

269 I Beneficiary<br />

Has<br />

Transplant<br />

TRNSPLNT<br />

EXISTS<br />

This TRC is returned on an enrollment. It is intended to supply the Plan with additional information<br />

about the beneficiary. Each TRC 269 returns transplant <strong>and</strong> failure dates for each kidney transplant<br />

that overlaps the enrollment period. There may be more than one TRC 269 returned.<br />

The transplant date is shown in the Effective Date field (field 18). The end date, if one exists, is<br />

shown in Transplant End Date (field 24).<br />

270 M Beneficiary<br />

Transplant<br />

Has Ended<br />

<strong>28</strong>0 I Member MSP<br />

Period Ended<br />

<strong>28</strong>2 A Residence<br />

Address<br />

Deleted<br />

<strong>28</strong>3 R Residence<br />

Address<br />

Delete<br />

Rejected<br />

TRANSPLANT<br />

END<br />

MEMBER NOT<br />

MSP<br />

RES ADR DELTD<br />

RJCTD ADR<br />

DELT<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

CMS was notified that the beneficiary’s transplant s failed or was an error. The effective date of<br />

the failure or removal is reported in field 18 of the TRR record <strong>and</strong> in the EFF DATE column on the<br />

printed report.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

The beneficiary’s <strong>Medicare</strong> as Secondary Payer period has ended.<br />

All plans whose payments are impacted by the MSP notification will receive the TRC.<br />

Plan Action: Update the Plan’s records accordingly.<br />

The residence address associated with the TRR data record effective date (in field 18) has been<br />

deleted <strong>and</strong> is no longer valid.<br />

The address was removed either through “delete” action via the 76 transaction or because an<br />

overlapping residence address change was submitted with the same or earlier effective date.<br />

Plan Action: None required.<br />

The residence address delete attempted was rejected. No residence address exists for the effective<br />

date provided. See TRR data record, field 18.<br />

Plan Action: Correct effective date <strong>and</strong> resubmit.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-64 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

<strong>28</strong>4 R Cancellation<br />

Rjctd, Prior<br />

Enroll/Disenr<br />

oll Changed<br />

<strong>28</strong>5 I Enrollment<br />

Cancellation<br />

Accepted<br />

<strong>28</strong>6 R Enrollment<br />

Cancellation<br />

Rejected<br />

<strong>28</strong>7 A Enrollment<br />

Reinstated<br />

NO REINSTATE<br />

ACPT ENROLL<br />

CAN<br />

RJCT ENROLL<br />

CAN<br />

ENROLL<br />

REINSTAT<br />

A Disenrollment Cancellation (Transaction Type 81) was rejected. The cancellation action<br />

attempted the reinstatement of the enrollment <strong>and</strong> this reinstatement could not be accomplished.<br />

The reinstatement could not be accomplished because some aspect of the enrollment, or the<br />

beneficiary’s status during that enrollment, has been changed by the Plan (examples include: 4Rx,<br />

Residence Address or Segment ID) prior to their issuance of this current cancellation transaction.<br />

Plan Action: Enroll the beneficiary using a Transaction Type 61, Enrollment.<br />

An Enrollment Cancellation (Transaction Type 80) transaction was accepted. The identified<br />

enrollment is cancelled. The start date of the cancelled enrollment period is reported in the TRR data<br />

record Effective Date field, field 18.<br />

Plan Action: Update the Plan’s records accordingly.<br />

An Enrollment Cancellation (Transaction Type 80) transaction was rejected. Rejection occurred for<br />

one of the following reasons: The cancellation was submitted more than one month after the<br />

enrollment became active, the transaction attempts to cancel a Rollover, Auto or Facilitated<br />

Enrollment, or when the transaction attempts to cancel a closed enrollment period.<br />

Plan Action: Submit a Disenrollment transaction.<br />

The identified enrollment period was reinstated. The start date of the reinstated period is reported in<br />

the TRR data record Effective Date field, field 18. The reinstatement occurred for one of the<br />

following reasons:<br />

For Transaction Type 80, cancellation of another plan’s enrollment;<br />

For Transaction Type 01, change or removal of a date of death.<br />

If the reinstated enrollment has an end date, it is reported in the TRR data record field 24. The end<br />

date may or may not have existed with the enrollment originally.<br />

Plan Action: Update the Plan’s records accordingly following CMS guidance for enrollment<br />

reinstatement.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-65 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

<strong>28</strong>8 A Disenrollmen<br />

t Cancellation<br />

Accepted<br />

<strong>28</strong>9 R Disenrollmen<br />

t Cancellation<br />

Rejected<br />

290 I IEP<br />

NUNCMO<br />

Reset<br />

ACPT DISNRL<br />

CAN<br />

RJCT DISNRL<br />

CAN<br />

NUNCMO RSET<br />

IEP<br />

A Disenrollment Cancellation (Transaction Type 81) transaction was accepted. The identified<br />

disenrollment was cancelled. The start date of the cancelled disenrollment period is reported in the<br />

TRR data record Effective Date field, field 18.<br />

The Disenrollment Cancellation (Transaction Type 81) may have been submitted by a Plan or the<br />

result of a Date of Death Change or Date of Death Rescinded notification that cancels an autodisenrollment<br />

that was created by a Date of Death notification.<br />

Plan Action: Update the Plan’s records accordingly.<br />

A Disenrollment Cancellation (Transaction Type 81) transaction was rejected. Rejection occurred<br />

for one of the following reasons:<br />

Beneficiary was still enrolled in plan, never disenrolled;<br />

Beneficiary was not enrolled in the plan;<br />

Disenrollment being cancelled was not submitted by the Plan<br />

Cannot restore prior enrollment due to associated disenrollment reason codes 5, 6, 8, 9, 10, 13,<br />

15, 18, 19, 54, 56, 57, 61<br />

Reinstated enrollment would conflict with another existing enrollment.<br />

Plan Action: Submit Enrollment transaction.<br />

This TRC was the result of an automatic system reset, or zeroing, of the cumulative uncovered<br />

months for the identified beneficiary. This reset occurred for one of the following reasons:<br />

Disabled beneficiary became age-qualified for <strong>Medicare</strong>,<br />

An aged beneficiary had a retroactive NUNCMO transaction with an effective date prior to<br />

aged qualification at the beginning of the IEP period.<br />

Reset effective date is in TRR data record, field 18.<br />

Plan Action: Update plan records accordingly.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-66 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

291 I Enrollment<br />

Reinstated,<br />

Disenrollmen<br />

t Cancellation<br />

292 R Disenrollmen<br />

t Rejected,<br />

Was<br />

Cancellation<br />

Attempt<br />

293 A Disenroll,<br />

Failure to Pay<br />

Part D<br />

IRMAA<br />

294 I No 4Rx<br />

Insurance<br />

Changed<br />

295 M Low Income<br />

NUNCMO<br />

RESET<br />

ENROLL<br />

REINSTAT<br />

NOT<br />

CANCELLATN<br />

FAIL PAY PTD<br />

IRMAA<br />

NO INSUR<br />

CHANGE<br />

NUNCMO RSET<br />

LIS<br />

A Disenrollment Cancellation (Transaction Type 81) transaction cancelled a disenrollment <strong>and</strong> the<br />

enrollment was reinstated. The start date of the reinstated period is reported in the TRR data record<br />

Effective Date field, field 18.<br />

If the reinstated enrollment has an end date, it is reported in the TRR data record, field 24. The end<br />

date may or may not have existed with the enrollment originally.<br />

Plan Action: Update the Plan’s records accordingly following CMS guidance for enrollment<br />

reinstatement.<br />

A Disenrollment transaction (Transaction Type 51) was rejected. The submitted disenrollment<br />

effective date is the same as the enrollment start date. Only Auto or Facilitated enrollments may be<br />

cancelled using the Transaction Type 51.<br />

Plan Action: Submit an Enrollment Cancellation transaction (Transaction Type 80) if it is desired<br />

to cancel the enrollment; otherwise, correct the disenrollment effective date <strong>and</strong> resubmit.<br />

A disenrollment transaction (Transaction Type 51) has been successfully processed due to failure to<br />

pay Part D IRMAA. The last day of the enrollment is reported in TRR data record fields 18 <strong>and</strong> 24.<br />

The disenrollment date is always the last day of the month.<br />

Plan Action: Ensure the Plan’s system matches the information included in the TRR record <strong>and</strong> that<br />

the beneficiary’s disenrollment date matches the date in field 24. Take the appropriate actions as<br />

per CMS enrollment guidance.<br />

A 4Rx Change (Transaction Type 72) transaction was received with no primary or secondary<br />

insurance information provided on the transaction. No insurance data changes took place for this<br />

beneficiary.<br />

Plan Action: Resubmit with new 4Rx data as needed.<br />

This TRC was the result of an automatic system reset, or zeroing, of the cumulative uncovered<br />

months for the identified beneficiary. This reset occurred because the beneficiary has been<br />

identified as having the Part D low-income subsidy.<br />

Reset effective date is in TRR data record, field 18.<br />

Plan Action: Update plan records accordingly.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-67 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

299 M Correction to<br />

Previously<br />

Failed<br />

Payment<br />

300 R NUNCMO<br />

Change<br />

Rejected,<br />

Exceeds Max<br />

Possible<br />

Value<br />

301 M Merged<br />

Beneficiary,<br />

Claim<br />

Number<br />

Change<br />

RESTORED<br />

PYMT<br />

NM CHG EXDS<br />

MAX<br />

BENE HICN<br />

MERGE<br />

This TRC was generated to indicate that a previously incomplete payment calculation has been<br />

completed.<br />

Plan Action: None required.<br />

A NUNCMO Record Update transaction (73) was rejected because the NUNCMO provided exceeds<br />

the maximum possible value. The original (existing) number of uncovered months has been<br />

retained.<br />

Plan Action: Review the number of uncovered months <strong>and</strong>/or the effective date submitted. If the<br />

number of uncovered months <strong>and</strong>/or the effective date should be another value, review CMS<br />

enrollment guidance <strong>and</strong> correct the NUNCMO value using a new NUNCMO Record Update (73)<br />

transaction.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary had multiple conflicting claim numbers (HICNs) which were merged under a single<br />

HICN. This TRR reports the VALID HICN in field 1 <strong>and</strong> the INVALID HICN in field 24.<br />

302 M Enrollment<br />

Cancelled,<br />

Claim<br />

Number<br />

Change<br />

ENRL CNCL<br />

MERGE<br />

Plan Action: Update the Plan’s records to use the VALID HICN from field 1 for this<br />

beneficiary. The valid claim number must be used on all future transactions for this beneficiary.<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary had multiple conflicting HICNs, which were merged into one. Plan enrollments for<br />

the conflicting HICNs have been combined under a valid HICN. This enrollment conflicted with<br />

another existing enrollment. As a result, the conflicting enrollment period was cancelled. The<br />

effective date of the enrollment which has been cancelled is reported in the Effective Date field (18).<br />

The termination date of the enrollment (if present) is reported in field 24.<br />

Plan Action: Because the enrollment period is now cancelled, the enrollment period should be<br />

adjusted in the Plan’s enrollment records. This change may impact premiums that you collected<br />

directly from the beneficiary. Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-68 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

303 M Termination<br />

Date Change<br />

due to<br />

Beneficiary<br />

Merge<br />

TRM DT CHG<br />

MERGE<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a submitted<br />

transaction but is intended to supply the Plan with additional information about the beneficiary.<br />

This beneficiary had multiple conflicting claim numbers (HICNs) which were merged into<br />

one. Plan enrollments for the conflicting HICNs have been combined under a valid HICN. This<br />

enrollment conflicted with another existing enrollment. Current enrollment rules regarding the<br />

application signature date were applied <strong>and</strong> this enrollment’s termination date was changed from the<br />

original date. The effective date of the enrollment with the changed termination date is reported in<br />

the Effective Date field (18). The new termination date of this enrollment is reported in Field 24.<br />

305 M ZIP Code<br />

Change<br />

306 R NUNCMO<br />

Change<br />

Rejected, No<br />

Part D<br />

Eligibility<br />

307 A MMP Passive<br />

Enrollment<br />

Accepted<br />

ZIP CODE<br />

CHANGE<br />

NUNCMO, NO<br />

PTD<br />

PASSIVE<br />

ACCEPT<br />

Plan Action: Because the termination date has changed, the enrollment period should be adjusted<br />

in the Plan’s enrollment records. This change may impact premiums that you collected directly<br />

from the beneficiary. Take the appropriate actions as per CMS enrollment guidance.<br />

A notification has been received that this beneficiary’s zip code has changed. The new zip code is<br />

reported in field 24 of the TRR. The effective date of the change is reported in field 18.<br />

Note: A reply with this TRC only reports changes in the Zip Code the beneficiary has on file with<br />

SSA/CMS. It does not report changes in a Plan-submitted Residence Address.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Take the<br />

appropriate actions as per CMS enrollment guidance.<br />

A NUNCMO Change transaction (Transaction Type 73) was rejected because beneficiary does not<br />

have Part D Eligibility as of the submitted effective date.<br />

Plan Action: Verify the beneficiary identifying information <strong>and</strong> resubmit the transaction with<br />

updated information, if appropriate.<br />

An MMP passive enrollment transaction (TC 61) successfully processed. The effective date of the<br />

new enrollment is reported in DTRR field 18.<br />

This is the definitive enrollment acceptance record. Other accompanying replies with different<br />

TRCs may give additional information about this enrollment.<br />

Plan Action: Ensure the Plan’s system matches the information included in the DTRR record. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-69 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

308 R MMP Passive<br />

Enrollment<br />

Rejected<br />

309 I No Change in<br />

MMP Opt-<br />

Out Flag<br />

310 R MMP Opt-<br />

Out Rejected,<br />

Invalid Opt-<br />

Out Code<br />

311 A MMP Opt-<br />

Out Accepted<br />

312 A MMP<br />

Enrollment<br />

Cancellation<br />

Accepted<br />

313 R MMP<br />

Enrollment<br />

Cancellation<br />

Rejected<br />

PASSIVE REJECT<br />

DUP FA OPT OUT<br />

BAD FA OPT<br />

OUT<br />

FA OPT OUT<br />

ACPT<br />

ACPT FA<br />

CANCEL<br />

RJCT FA<br />

CANCEL<br />

An MMP passive enrollment transaction (TC 61) was rejected because the beneficiary did not meet<br />

the MMP requirements or the beneficiary opted out of passive enrollment.<br />

The attempted enrollment effective date is reported in DTRR fields 18 <strong>and</strong> 24.<br />

Plan Action: Take the appropriate actions as per CMS enrollment guidance.<br />

An MMP Opt-Out Record Update transaction (TCs 42, 83) was submitted; however, no data change<br />

was made to the beneficiary’s record. The submitted transaction contained an MMP Opt-Out Flag<br />

value that matched the MMP Opt-Out already on record with CMS.<br />

This transaction did not affect the beneficiary’s records.<br />

Plan Action: None required.<br />

An opt-out from CMS, disenrollment, or Plan submitted Opt-Out transaction (TCs 42, 51, 54, 82,<br />

83) was rejected because the MMP Opt-Out Flag field was incorrectly populated.<br />

The valid values for MMP Opt-Out are:<br />

TCs 42 or 83 transactions - ‘Y’ or ‘N’<br />

All other TCs - ‘Y,’ ‘N,’ or blank<br />

Plan Action: If submitted by the Plan (TCs 51, 82, 83), correct the MMP Opt-Out Flag value <strong>and</strong><br />

resubmit the transaction if appropriate.<br />

A transaction (TCs 42, 51, 54, 82, 83) was received that specified an MMP Opt-Out Flag value or a<br />

change to the MMP Opt-Out Flag value. The MMP Opt-Out Flag was accepted.<br />

The new MMP Opt-Out Flag value is reported in DTRR field 70.<br />

Plan Action: No action necessary.<br />

An Enrollment Cancellation (TC 82) was accepted. The identified enrollment was cancelled. The<br />

start date of the cancelled enrollment period is reported in DTRR field 18.<br />

Plan Action: Update the Plan’s records accordingly.<br />

An MMP Enrollment Cancellation (TC 82) transaction was rejected because the cancellation was<br />

submitted after the enrollment became active.<br />

Plan Action: Submit a Disenrollment transaction.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-70 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

314 R Invalid<br />

Cancellation<br />

TC<br />

BAD CANCEL<br />

CODE<br />

An enrollment cancellation transaction was rejected because the wrong transaction type code (Field<br />

16) was used.<br />

TC 82 can only be used for cancelling MMP enrollments. TC 80 is only used for cancelling non-<br />

MMP enrollments.<br />

316 I Default<br />

Segment ID<br />

Assignment<br />

DEFAULT SEG ID<br />

Plan Action: Correct the TC <strong>and</strong> resubmit if appropriate.<br />

A default Segment ID is assigned because the beneficiary is Out-of-Area for the Contract/PBP. The<br />

default Segment ID is the lowest valid Segment for the Contract/PBP.<br />

The following fields populate in the DTRR when this TRC is returned:<br />

Field 1: HICN<br />

Field 2: Surname<br />

Field 3: First Name<br />

Field 4: Middle Initial<br />

Field 5: Gender Code<br />

Field 6: Date of Birth<br />

Field 7: Record Type<br />

Field 8: Contract Number<br />

Field 9: State Code<br />

Field 10: County Code<br />

Field 15: TRC<br />

Field 16: Transaction Type<br />

Field 18: Request effective Date<br />

Field 20: PBP ID<br />

Field 22: Transaction Date<br />

Field 24: Comment (Previous Segment Number, if applicable)<br />

Field <strong>28</strong>: Source ID<br />

Field 30: Application Date<br />

Field 33: Segment Number<br />

Field 36: Election Type<br />

Field 37: Enrollment Source<br />

Field 43: Processing Timestamp<br />

Field 68: TRC Short Name<br />

Field 75: System-Assigned Transaction Tracking ID<br />

Field 76: Plan-Assigned Transaction Tracking ID<br />

Plan Action: Verify the beneficiary’s address is correct. Submit a Residence Address Change if<br />

<strong>December</strong> <strong>28</strong>, 2012 I-71 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

317 I Segment ID<br />

Reassigned<br />

after Address<br />

Update<br />

SEG ID<br />

REASSIGN<br />

appropriate.<br />

A Segment ID is reassigned because updated address information is received. The updated address<br />

information either results from a Plan-submitted Residence Address Change (Transaction Type 76)<br />

or a SCC change notification.<br />

The following fields populate in the DTRR when this TRC is returned:<br />

Field 1: HICN<br />

Field 2: Surname<br />

Field 3: First Name<br />

Field 4: Middle Initial<br />

Field 5: Gender Code<br />

Field 6: Date of Birth<br />

Field 7: Record Type<br />

Field 8: Contract Number<br />

Field 9: State Code<br />

Field 10: County Code<br />

Field 15: TRC<br />

Field 16: Transaction Type<br />

Field 18: Request effective Date<br />

Field 20: PBP ID<br />

Field 22: Transaction Date<br />

Field 24: Comment (Previous Segment Number, if applicable)<br />

Field <strong>28</strong>: Source ID<br />

Field 30: Application Date<br />

Field 33: Segment Number<br />

Field 36: Election Type<br />

Field 37: Enrollment Source<br />

Field 43: Processing Timestamp<br />

Field 68: TRC Short Name<br />

Field 75: System-Assigned Transaction Tracking ID<br />

Field 76: Plan-Assigned Transaction Tracking ID<br />

Plan Action: Verify the Segment ID is correct. Submit a Residence Address Change or a Segment<br />

ID change if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-72 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

600 R UI<br />

Transaction<br />

Override<br />

UI OVERRIDE<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

A discrepancy enrollment transaction (Transaction Type 61) was rejected because it attempted to<br />

change an existing enrollment record that was previously entered by a CMS User through the User<br />

Interface.<br />

601 R Casework<br />

Beneficiary<br />

602 R No<br />

Discrepancy<br />

CASEWORK<br />

BENE<br />

NO<br />

DISCREPANCY<br />

Plan Action: Update plan records accordingly <strong>and</strong> take the appropriate actions as per CMS<br />

enrollment guidance (send “Enrollment Status Update” notice to the beneficiary).<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

A discrepancy enrollment transaction (Transaction Type 61) was rejected because the beneficiary’s<br />

enrollment was updated by CMS casework.<br />

Plan Action: Update plan records accordingly <strong>and</strong> take the appropriate actions as per CMS<br />

enrollment guidance (send “Enrollment Status Update” notice to the beneficiary).<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

A discrepancy enrollment transaction (Transaction Type 61) was rejected because the enrollment<br />

effective date <strong>and</strong> contract/PBP in the submitted transaction matches the existing enrollment on file.<br />

There is no update to the beneficiary’s enrollment period.<br />

603 R 2007 Date is<br />

Not Valid<br />

Plan Action: None required<br />

2007 DT INVALID This TRC is used for special Enrollment Reconciliation TRRs.<br />

A discrepancy enrollment transaction (Transaction Type 61) was rejected because 2007 effective<br />

dates were not considered for the 2006 enrollment reconciliation. This rejection could have been<br />

caused by one of the following reasons:<br />

A 2007 enrollment or PBP was submitted <strong>and</strong> rejected because there was not a 2006<br />

discrepancy submitted along with the 2007 enrollment.<br />

A 2006 enrollment transaction AND a 2007 PBP change record attempted to process as a<br />

Rollover. The transaction rejected because the enrollment record <strong>and</strong> the PBP change record did<br />

not have the same application signature date.<br />

Plan Action: Update plan records accordingly. If the Plan has a 2007 enrollment to correct,<br />

contact the DMS DPO representative to process a retroactive enrollment transaction.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-73 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

604 A Disenrollmen<br />

t<br />

605 R Recon<br />

Transaction<br />

Denied<br />

DISENROLLMEN<br />

T<br />

TRANS DENIED<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

Check dates code puts in TRR fields 18 <strong>and</strong> 24(maybe) <strong>and</strong> update text.<br />

As a result of the Enrollment Reconciliation process, this beneficiary was disenrolled due to<br />

enrollment in another Plan.<br />

Plan Action: Update plan records accordingly <strong>and</strong> take the appropriate actions as per CMS<br />

enrollment guidance (send “Enrollment Status Update” notice to the beneficiary).<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

A discrepancy enrollment transaction (Transaction Type 61) was denied following reconciliation<br />

processing.<br />

Plan Action: Update plan records accordingly <strong>and</strong> take the appropriate actions as per CMS<br />

enrollment guidance (send “Enrollment Status Update” notice to the beneficiary).<br />

606 I Direct Bill DIRECT BILL This TRC is used for special Enrollment Reconciliation TRRs.<br />

This beneficiary has been changed to “Direct Bill” for this enrollment period. Even though a PPO<br />

other than D was specified in the transaction, Direct Bill is the only valid option for reconciliation<br />

transactions.<br />

This transaction response will accompany the acceptance TRC for the submitted discrepancy<br />

transaction.<br />

607 A Enrollment<br />

Accepted as<br />

Submitted<br />

ENROLL OK<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary is in direct bill<br />

status for the enrollment period. Take the appropriate actions as per CMS enrollment guidance.<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

The submitted discrepancy enrollment transaction (Transaction Type 61) was accepted. The<br />

effective date of the enrollment period is reported in TRR data record field 18.<br />

Plan Action: Ensure that the Plan records correctly represent this enrollment. Take the appropriate<br />

actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-74 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

608 A Enrl<br />

Accepted,<br />

CMS<br />

Established<br />

Eff <strong>and</strong> End<br />

Dates<br />

609 A Enrollment<br />

Accepted<br />

with CMS<br />

established<br />

Eff date<br />

610 A Enrollment<br />

Accepted<br />

with CMS<br />

Established<br />

End Date<br />

ENRLD/CMS DTS<br />

ENRLD/CMS EFF<br />

ENRLD/CMS<br />

END<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

The submitted discrepancy enrollment transaction (Transaction Type 61) was accepted but the<br />

effective date <strong>and</strong> end date for the enrollment period were provided by CMS. The new effective<br />

date of the enrollment period is reported in TRR data record field 18.<br />

Plan Action: Update Plan records to be consistent with the dates in fields 18 <strong>and</strong> 54(?). Review<br />

ALL enrollment periods in the Full Enrollment file to determine the beneficiary’s status. Take the<br />

appropriate actions as per CMS enrollment guidance (send appropriate “Enrollment Status Update”<br />

notice).<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

The submitted discrepancy enrollment transaction (Transaction Type 61) was accepted but the<br />

effective date for the enrollment period was provided by CMS. The effective date of the new<br />

enrollment period is reported in TRR data record field 18.<br />

Plan Action: Update Plan records to be consistent with the dates in fields 18. Review ALL<br />

enrollment periods in the Full Enrollment file to determine the beneficiary’s status. Determine if a<br />

premium refund is required. Take the appropriate actions as per CMS enrollment guidance (send<br />

appropriate “Enrollment Status Update” notice).<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

The submitted discrepancy enrollment transaction (Transaction Type 61) was accepted but the end<br />

date for the enrollment period was provided by CMS. The submitted effective date of the enrollment<br />

period is reported in TRR data record field 18.<br />

Plan Action: Update Plan records to be consistent with the dates in fields 18. Review ALL<br />

enrollment periods in the Full Enrollment file to determine the beneficiary’s status. Determine if a<br />

premium refund is required. Take the appropriate actions as per CMS enrollment guidance (send<br />

appropriate “Enrollment Status Update” notice).<br />

<strong>December</strong> <strong>28</strong>, 2012 I-75 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

611 R No<br />

Discrepancy<br />

in 2006<br />

701 A New UI<br />

Enrollment<br />

(Open Ended)<br />

702 A UI Fill-In<br />

Enrollment<br />

NO DISCREP<br />

2006<br />

UI<br />

ENROLLMENT<br />

UI FILL-IN ENRT<br />

This TRC is used for special Enrollment Reconciliation TRRs.<br />

A discrepancy enrollment transaction (Transaction Type 61) was rejected because the enrollment<br />

matched exactly what CMS has on file for the calendar year of the reconciliation. However, CMS<br />

has identified an enrollment discrepancy which exists in another contract or calendar year.<br />

Plan Action: Review ALL enrollment periods in the Full Enrollment file to confirm the status of<br />

the beneficiary. The Plan should work through the established retroactive process to correct<br />

discrepancies associated with a calendar year other than the year being reconciled.<br />

A CMS User or a Plan User with Update Authority enrolled this beneficiary in this contract under<br />

the indicated PBP (if applicable) <strong>and</strong> segment (if applicable). TRR data record, field 18 contains the<br />

enrollment effective date. This is an open-ended enrollment which does not have a disenrollment<br />

date.<br />

The Part C Premium amount may have been populated automatically with the base Part C premium<br />

amount.<br />

Plan Action: Update the Plan’s beneficiary records with the information in the TRR. Verify the<br />

Part C premium amount <strong>and</strong> submit a Record Update transaction if necessary. Take the appropriate<br />

actions as per CMS enrollment guidance.<br />

A CMS User or Plan User with Update Authority enrolled this beneficiary in this contract under the<br />

indicated PBP (if applicable) <strong>and</strong> segment (if applicable). This enrollment is a Fill-In Enrollment<br />

<strong>and</strong> represents a complete enrollment period that begins on the date in TRR data record field 18 <strong>and</strong><br />

ends on the date in field 24. This is a distinct enrollment period <strong>and</strong> does not affect any existing<br />

enrollments.<br />

The Part C Premium amount may have been populated automatically with the base Part C premium<br />

amount.<br />

Plan Action: Update the Plan’s records to reflect the beneficiary’s enrollment as of the effective<br />

date in TRR data record field 18 <strong>and</strong> the ending on the date in field 24. This end date should not<br />

affect the beginning of any existent enrollment periods. Verify the Part C premium amount <strong>and</strong><br />

submit a Record Update transaction if necessary. Take the appropriate actions as per CMS<br />

enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-76 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

703 A UI<br />

Enrollment<br />

Cancel<br />

(Delete)<br />

704 A UI<br />

Enrollment<br />

Cancel PBP<br />

Correction<br />

705 A UI<br />

Enrollment<br />

PBP<br />

Correction<br />

UI ENROLL<br />

CANCL<br />

UI CNCL PBP<br />

COR<br />

UI ENR PBP COR<br />

A CMS User cancelled the beneficiary’s existing enrollment <strong>and</strong> the beneficiary is disenrolled.<br />

When an enrollment is cancelled, it means that the enrollment never occurred. TRR data record<br />

field 18 contains the effective date (start date) of the cancelled enrollment period.<br />

Plan Action: Remove the indicated enrollment from the Plan’s records. Take the appropriate<br />

actions as per CMS enrollment guidance.<br />

A CMS User updated the PBP on an existing enrollment. This generates two transaction replies, a<br />

Transaction Type 51 with TRC 704 <strong>and</strong> a Transaction Type 61 with TRC 705. This reply with TRC<br />

704 (Transaction Type 51) represents the cancellation of the enrollment in the original PBP. The<br />

effective (start) <strong>and</strong> disenrollment (end) dates of the enrollment being cancelled are found in TRR<br />

data record fields 18 & 24, respectively. When an enrollment is cancelled it means that the<br />

enrollment never occurred.<br />

Plan Action: Remove the indicated enrollment in the original PBP from the Plan’s records. Look<br />

for the accompanying reply with TRC 705 to determine the replacement enrollment period. Take<br />

the appropriate actions as per CMS enrollment guidance.<br />

A CMS User updated the PBP on an existing enrollment. This generates two transaction replies, a<br />

Transaction Type 51 with TRC 704 <strong>and</strong> a Transaction Type 61 with TRC 705. This reply with TRC<br />

705 (Transaction Type 61) represents the enrollment in the new PBP. The effective (start) <strong>and</strong><br />

disenrollment (end) dates of the enrollment in this new PBP are found in TRR data record fields 18<br />

& 24, respectively. This enrollment should replace the enrollment cancelled by the associated<br />

Transaction Type 51 transaction (TRC 704).<br />

The Part C Premium amount may have been populated automatically with the base Part C premium<br />

amount.<br />

Plan Action: Update the Plan records to reflect the beneficiary’s enrollment in the new Contract,<br />

PBP. Look for the accompanying reply with TRC 704 to ensure that the original PBP enrollment<br />

was cancelled. Verify the Part C premium amount <strong>and</strong> submit a Record Update transaction if<br />

necessary. Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-77 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

706 A UI<br />

Enrollment<br />

Cancel<br />

Segment<br />

Correction<br />

707 A UI<br />

Enrollment<br />

Segment<br />

Correction<br />

708 A UI Assigns<br />

End Date<br />

UI CNCL SEG<br />

COR<br />

UI ENR SEG COR<br />

UI ASSGN END<br />

DT<br />

A CMS User updated the Segment on an existing enrollment. This generates two transaction<br />

replies, a Transaction Type 51 with TRC 706 <strong>and</strong> a Transaction Type 61 with TRC 707. This reply<br />

(Transaction Type 51) represents the cancellation of the enrollment in the original Segment. When<br />

an enrollment is cancelled it means that the enrollment never occurred. The effective (start) <strong>and</strong><br />

disenrollment (end) dates of the enrollment being cancelled are found in TRR data record fields 18<br />

& 24, respectively.<br />

Plan Action: Remove the indicated enrollment in the original Segment from the Plan’s records.<br />

Look for the accompanying reply with TRC 707 to determine the replacement enrollment period.<br />

Take the appropriate actions as per CMS enrollment guidance.<br />

A CMS User updated the Segment on an existing enrollment. This generates two transaction replies,<br />

a Transaction Type 51 with TRC 706 <strong>and</strong> a Transaction Type 61 with TRC 707. This reply<br />

(Transaction Type 61) represents the enrollment in the new Segment. The effective (start) <strong>and</strong><br />

disenrollment (end) dates of the enrollment in this new Segment are found in TRR data record fields<br />

18 & 24, respectively. This enrollment should replace the enrollment cancelled by the associated<br />

Transaction Type 51 transaction (TRC 706).<br />

The Part C Premium amount may have been populated automatically with the base Part C premium<br />

amount.<br />

Plan Action: Update the Plan records to reflect the beneficiary’s enrollment in the new Contract,<br />

PBP. Segment. Look for the accompanying reply with TRC 706 to ensure that the original Segment<br />

enrollment was cancelled. Verify the Part C premium amount <strong>and</strong> submit a Record Update<br />

transaction if necessary. Take the appropriate actions as per CMS enrollment guidance.<br />

A CMS User or Plan User with Update Authority assigned an end date to existing open-ended<br />

enrollment. The last day of enrollment is in TRR data record field 18. The enrollment effective<br />

date (start date) remains unchanged.<br />

Plan Action: Update the Plan records to reflect the beneficiary’s disenrollment from the Plan.<br />

Take the appropriate actions as per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-78 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

709 A UI Moved<br />

Start Date<br />

Earlier<br />

710 A UI Moved<br />

Start Date<br />

Later<br />

711 A UI Moved<br />

End Date<br />

Earlier<br />

UI ERLY STRT<br />

DT<br />

UI LATE STRT<br />

DT<br />

UI ERLY END DT<br />

A CMS User updated the start date of an existing enrollment to an earlier date. This reply has a<br />

Transaction Type of 61. The new start date is reported in TRR data record field 18 (Effective Date)<br />

<strong>and</strong> the original start date is reported in field 24. The existing enrollment was changed to begin on<br />

the date in TRR data record field 18. The end date of the existing enrollment (if it exists) remains<br />

unchanged.<br />

The Part C Premium amount may have been populated automatically with the base Part C premium<br />

amount.<br />

Plan Action: Locate the enrollment for this beneficiary that starts on the date in field 24. Update<br />

the Plan records for this enrollment to start on the date in field 18. Verify the Part C premium<br />

amount <strong>and</strong> submit a Record Update transaction if necessary. Take the appropriate actions as per<br />

CMS enrollment guidance.<br />

A CMS User updated the start date of an existing enrollment to a later date. This reply has a<br />

Transaction Type of 51. The new start date is reported in field 18 (effective date) <strong>and</strong> the original<br />

start date is reported in TRR data record field 24. The existing enrollment has been reduced to<br />

begin on the date in TRR data record field 18. The end date of the existing enrollment (if it exists)<br />

remains unchanged.<br />

Plan Action: Locate the enrollment for this beneficiary that starts on the date in field 24. Update<br />

the Plan records for this enrollment to start on the date in field 18. Take the appropriate actions as<br />

per CMS enrollment guidance.<br />

A CMS User or Plan User with Update Authority updated the end date of an existing enrollment to<br />

an earlier date. This reply has a Transaction Type of 51. The new end date is reported in field 18<br />

(effective date) <strong>and</strong> the original end date is reported in TRR data record field 24. The existing<br />

enrollment was reduced to end on the date in TRR data record field 18. The start date of the<br />

existing enrollment remains unchanged.<br />

Plan Action: Locate the enrollment for this beneficiary that ends on the date in field 24. Update<br />

the Plan records for this enrollment to end on the date in field 18. Take the appropriate actions as<br />

per CMS enrollment guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-79 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

712 A UI Moved<br />

End Date<br />

Later<br />

713 A UI Removed<br />

Enrollment<br />

End Date<br />

714 I UI Part D<br />

Opt-Out<br />

Change<br />

Accepted<br />

UI LATE END DT<br />

UI REMVD END<br />

DT<br />

UI OPT OUT OK<br />

A CMS User updated the end date of an existing enrollment to a later date. This reply has a<br />

Transaction Type of 61. The new end date is reported in field 18 (effective date) <strong>and</strong> the original<br />

end date is reported in TRR data record field 24. The existing enrollment was extended to end on<br />

the date in TRR data record field 18. The start date of the existing enrollment remains unchanged.<br />

The Part C Premium amount may have been populated automatically with the base Part C premium<br />

amount.<br />

Plan Action: Locate the enrollment for this beneficiary that ends on the date in field 24. Update<br />

the Plan records for this enrollment to end on the date in field 18. Verify the Part C premium<br />

amount <strong>and</strong> submit a Record Update transaction if necessary. Take the appropriate actions as per<br />

CMS enrollment guidance.<br />

A CMS User removed the end date from an existing enrollment. This reply has a Transaction Type<br />

of 61. TRR data record field 18 (effective date) contains zeroes (00000000) <strong>and</strong> the original end<br />

date is reported in field 24. The existing enrollment was extended to be an open-ended enrollment.<br />

The start date of the existing enrollment remains unchanged.<br />

The Part C Premium amount may have been populated automatically with the base Part C premium<br />

amount.<br />

Plan Action: Locate the enrollment for this beneficiary that ends on the date in TRR data record<br />

field 24. Update the Plan records for this enrollment to remove the end date <strong>and</strong> to extend this<br />

enrollment to be an open-ended enrollment. Verify the Part C premium amount <strong>and</strong> submit a<br />

Record Update transaction if necessary. Take the appropriate actions as per CMS enrollment<br />

guidance.<br />

A CMS User or Plan User with Update Authority added or changed the value of the Part D Opt-Out<br />

Flag for this beneficiary. The new Opt-Out Flag is reported in TRR data record field 38 on the TRR<br />

record.<br />

Plan Action: Update the Plan’s records accordingly.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-80 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

715 M Medicaid<br />

Change<br />

Accepted<br />

716 I UI changed<br />

the Number<br />

of Uncovered<br />

Months<br />

717 I UI changed<br />

only the<br />

Application<br />

Date<br />

MCAID CHG<br />

ACEPT<br />

UI CHGD<br />

NUNCMO<br />

UI CHGD APP DT<br />

A CMS User changed the beneficiary’s Medicaid status. This may or may not have changed the<br />

beneficiary’s actual status since multiple sources of Medicaid information are used to determine the<br />

beneficiary’s actual Medicaid status.<br />

The Plan will see the result of any changes to the beneficiary’s actual Medicaid status included in<br />

the next scheduled update of Medicaid status.<br />

Plan Action: Update the Plan’s records accordingly.<br />

A CMS User or Plan User with Update Authority updated the beneficiary’s Number of Uncovered<br />

Months.<br />

Plan Action: Update the Plan’s records accordingly. Ensure that the Plan is billing the correct<br />

amount for the LEP. Take the appropriate actions as per CMS enrollment guidance.<br />

A CMS User updated only the Application Date of a beneficiary's enrollment, which results in a<br />

blank TC on the DTRR, Field 16.<br />

Plan Action: Update the Plan’s records accordingly.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-81 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

718 I UI MMP<br />

Opt-Out<br />

Change<br />

Accepted<br />

990 –<br />

995<br />

996 I EOY Loss of<br />

Low Income<br />

Subsidy<br />

Status<br />

UI MMP OPTOUT<br />

OK<br />

EOY LOSS<br />

SBSDY<br />

A CMS User or Plan User with Update Authority added or changed the value of the MMP Opt-Out<br />

Flag for this beneficiary. The new MMP Opt-Out Flag is reported in TRR data record field 70.<br />

The following fields populate in the daily TRR when this TRC is returned:<br />

Field 1: HICN<br />

Field 2: Surname<br />

Field 3: First Name<br />

Field 4: Middle Initial<br />

Field 5: Gender Code<br />

Field 6: Date of Birth<br />

Field 7: Record Type<br />

Field 8: Contract Number<br />

Field 9: State Code<br />

Field 10: County Code<br />

Field 15: Transaction Reply Code<br />

Field 16: Transaction Type Code<br />

Field 18: Request Effective Date<br />

Field 20: Plan Benefit Package ID<br />

Field 22: Transaction Date<br />

Field <strong>28</strong>: Source ID<br />

Field 31: UI User Organization Designation<br />

Field 43: Processing Timestamp<br />

Field 68: TRC Short Name<br />

Field 70: MMP Opt Out Flag<br />

Field 72: System Assigned Transaction Tracking ID<br />

These codes appear only on special TRRs that are generated for specific purposes; for example,<br />

those generated to communicate Full Enrollment or to report beneficiaries losing low-income<br />

deeming. When a special TRR produces one of these TRCs, CMS will provide the <strong>Plans</strong> with<br />

communications which define the TRC descriptions <strong>and</strong> Plan actions (if applicable).<br />

Identifies those beneficiaries who are losing their deemed or LIS Applicant status as of <strong>December</strong><br />

31 st of the current year with no low income status determined for January of the following year.<br />

Plan Action: Update Plan records accordingly.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-82 Transaction Reply Codes (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

997 –<br />

999<br />

These codes appear only on special TRRs that are generated for specific purposes; for example,<br />

those generated to communicate Full Enrollment or to report beneficiaries losing low-income<br />

deeming. When a special TRR produces one of these TRCs, CMS will provide the <strong>Plans</strong> with<br />

communications which define the TRC descriptions <strong>and</strong> Plan actions (if applicable).<br />

<strong>December</strong> <strong>28</strong>, 2012 I-83 Transaction Reply Codes (TRCs)


I.3 Obsolete Transaction Reply Codes<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Table I-3 lists the obsolete TRCs marked for deletion beginning November 2006.<br />

Table I-3: Obsolete Transaction Reply Codes<br />

Code Type Title Short Definition Definition<br />

027 A Demonstration<br />

Beneficiary Factor Set<br />

0<strong>28</strong> A Demonstration<br />

Beneficiary Factor<br />

Terminated<br />

040 R Enrollment Rejected,<br />

Multiple Enrollment<br />

Trans<br />

041 R Invalid Demonstration<br />

Beneficiary Factor<br />

Date<br />

OBSOLETE<br />

OBSOLETE<br />

OBSOLETE<br />

OBSOLETE<br />

A transaction to turn on the beneficiary-level demonstration factor (Transaction Type<br />

30) was successfully processed. The effective start date of the factor is shown in TRR<br />

data record field 24.<br />

Note: This reply code is only applicable to transactions that update beneficiaryspecific<br />

risk adjustment factors for certain demonstration contracts.<br />

Plan Action: Update the Plan’s records.<br />

A transaction to turn off the beneficiary-level demonstration factor (Transaction Type<br />

31) was successfully processed. The effective end date of the factor is show in TRR<br />

data record field 24.<br />

Note: This reply code is only applicable to transactions that update beneficiaryspecific<br />

risk adjustment factors for certain demonstration contracts.<br />

Plan Action: Update the Plan’s records.<br />

An enrollment transaction (Transaction Type 61) was rejected because it was one of<br />

several that were submitted with the same effective date <strong>and</strong> application date.<br />

Plan Action: None required.<br />

A beneficiary factor update request attempted to process. This was rejected because<br />

the effective start <strong>and</strong>/or end date was not in a valid format or the request specified an<br />

effective start date that was greater than the end date.<br />

Plan Action: If this TRC is included in the Plan’s TRR, call the MMA Helpdesk to<br />

request guidance.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-84 Obsolete Transaction Reply Code (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

057 M Risk Adjuster Factor<br />

Change<br />

111 R PBP Rejected; Invalid<br />

Contract Number<br />

112 R Rejected; Conflicting<br />

Effective Dates<br />

115 R Enrollment Rejected;<br />

Plan Not Open<br />

OBSOLETE<br />

OBSOLETE<br />

OBSOLETE<br />

OBSOLETE<br />

This is an informational TRC.<br />

The Risk Adjuster System (RAS) has created new factors for this beneficiary, which<br />

may result in payment adjustments.<br />

Plan Action: Refer to the monthly RAS reports to update the Plan’s records.<br />

A PBP enrollment change transaction (Transaction Type 61) was rejected because the<br />

contract number submitted on the transaction does not match the contract number of<br />

the Plan in which the beneficiary is currently enrolled. The requested effective date of<br />

enrollment in the new PBP is reported in TRR data file field 18.<br />

Plan Action: If appropriate, resubmit the transaction with the correct contract<br />

number. If the Plan is attempting to move the beneficiary to a new contract number,<br />

an enrollment transaction (Transaction Type 61) must be used.<br />

A PBP change transaction (Transaction Type 61) was rejected because beneficiary<br />

was not enrolled in the submitted contract as of the effective date for the PBP change.<br />

A beneficiary must be enrolled in a PBP of a contract in order to change to another<br />

PBP. The effective date of the enrollment within the contract must be equal to or<br />

before the effective date of the PBP change.<br />

Plan Action: Correct the effective date of the PBP Change transaction <strong>and</strong> resubmit<br />

if appropriate. If the Plan is attempting to enroll a beneficiary in a different PBP with<br />

an effective date earlier than the original enrollment, the Plan must us an Enrollment<br />

transaction (Transaction Type 61).<br />

An enrollment or PBP change transaction (Transaction Type 61) was rejected because<br />

this Plan is closed to enrollments using an O (OEP), N (OEPNEW) or OEPI (T)<br />

election type.<br />

Plan Action: Correct the enrollment type <strong>and</strong> resubmit the transaction if appropriate.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-85 Obsolete Transaction Reply Code (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

146 A Rollover successful OBSOLETE A termination-rollover action was processed. These actions allow all members of a<br />

terminating Plan (contract or PBP) to be ‘rolled over’ (automatically enrolled) in a<br />

new Plan.<br />

This normally occurs at year end if a contract or PBP changes for the new year. The<br />

transaction is an Enrollment Transaction (Transaction Type 61) <strong>and</strong> has the new<br />

contract, PBP, <strong>and</strong> segment in TRR data record fields 8, 20 <strong>and</strong> 33, respectively. The<br />

effective date of the rollover is reported in field 18 <strong>and</strong> in the EFF DATE column on<br />

the printed report.<br />

148 I Rollover successful,<br />

Secondary <strong>Drug</strong><br />

Insurance 4Rxupdate<br />

required<br />

OBSOLETE<br />

Plan Action: Submit a 4Rx Record Update transaction (Transaction Type 72)<br />

supplying the beneficiary’s new insurance field (4Rx) values. If the move resulted in<br />

beneficiaries being moved incorrectly, contract your CMS plan representative.<br />

A beneficiary was “rolled over” into a new Plan (Contract <strong>and</strong>/or PBP). Updated 4RX<br />

drug insurance information is needed by CMS for the primary drug coverage <strong>and</strong> the<br />

secondary if applicable.<br />

This TRC provides the Plan with additional information on a rollover transaction that<br />

was processed successfully. It will be received by <strong>Plans</strong> which offer Part D coverage<br />

(PDP, MA-PD, demonstration or other Plan with Part D). The effective date of the<br />

new rolled-over enrollment will be reported in field 18 <strong>and</strong> in the EFF DATE column<br />

on the printed report.<br />

Plan Action: Submit a 4Rx Change transaction (Transaction Type 72) supplying the<br />

beneficiary’s new insurance field (4Rx) values.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-86 Obsolete Transaction Reply Code (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

167 M Change in Beneficiary<br />

Low Income Premium<br />

Subsidy<br />

OBSOLETE<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a<br />

submitted transaction but is intended to supply the Plan with additional information<br />

about the beneficiary.<br />

This beneficiary’s Part D low-income subsidy amount <strong>and</strong>/or percentage have<br />

changed. The effective date of the change is reported in field 18 of the TRR record<br />

<strong>and</strong> in the EFF DATE column on the printed report. Field 55 reports the beneficiary’s<br />

Part D premium subsidy amount as of the effective date of the transaction.<br />

If the change affects the Part D low-income subsidy for the Current Payment Month<br />

(CPM), the new amount will be reported in field 24.<br />

Replies with TRC 167 are often accompanied by replies with TRC 168 <strong>and</strong> TRC 121.<br />

Note: Fields 24 <strong>and</strong> 49 – 54 always represent the beneficiary’s LIS <strong>and</strong> LEP values<br />

for the current CPM. If this change is retroactive, these values may not reflect the<br />

values of the period being changed. Refer to the LISHIST report to determine the<br />

correct values for retroactive changes. TRC167will continue to be generated for<br />

internal purposes <strong>and</strong> will not be sent to the plans.<br />

Plan Action: Adjust the beneficiary’s Part D LIS amount <strong>and</strong>/or percentage as of the<br />

effective date in field 18. Take the appropriate actions as per CMS enrollment<br />

guidance. If the change is retroactive, refer to the LISHIST report to verify the correct<br />

amount for the affected period.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-87 Obsolete Transaction Reply Code (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

168 M Change in Beneficiary<br />

Low Income Cost<br />

Sharing Subsidy<br />

174 R Transaction Rejected;<br />

No Data Updates<br />

Submitted<br />

OBSOLETE<br />

OBSOLETE<br />

This TRC is returned on a reply with Transaction Type 01. It is not a reply to a<br />

submitted transaction but is intended to supply the Plan with additional information<br />

about the beneficiary.<br />

This beneficiary’s Part D low-income cost sharing level (co-pay) has changed. The<br />

effective date of the change is reported in field 18 of the TRR record <strong>and</strong> in the EFF<br />

DATE column on the printed report.<br />

If the change affects the Part D low-income cost sharing level for the Current Payment<br />

Month (CPM), the new level will be reported in field 24.<br />

Replies with TRC 168 are often accompanied by replies with TRC 167 <strong>and</strong> TRC 121.<br />

Note: Fields 24 <strong>and</strong> 49 – 54 always represent the beneficiary’s LIS <strong>and</strong> LEP values<br />

for the current CPM. If this change is retroactive, these values may not reflect the<br />

values of the period being changed. Refer to the LISHIST report to determine the<br />

correct values for retroactive changes. Field 55 reports the beneficiary’s Part D<br />

premium subsidy amount as of the effective date of the transaction.<br />

Plan Action: Adjust the beneficiary’s Part D LIS cost-sharing level as of the<br />

effective date in field 18. Take the appropriate actions as per CMS enrollment<br />

guidance. If the change is retroactive, refer to the LISHIST report to verify the correct<br />

level for the affected period.<br />

An EGHP, Segment ID, Part C premium, or Part D Opt-Out change transaction<br />

(Transaction Types 74, 77, 78, 79) was rejected because none of the change-to fields,<br />

EGHP Flag, Segment ID, Opt-Out Flag or Part C Premium, were populated in the<br />

submitted transaction.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required unless a change was intended. If a change was intended,<br />

populate the correct field(s) <strong>and</strong> resubmit the transaction.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-88 Obsolete Transaction Reply Code (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

181 I Invalid PTD premium<br />

submitted, corrected<br />

192 I No Change in Part C<br />

Premium Amount<br />

199 R Rejected, Return to<br />

Plan for Additional<br />

Research<br />

OBSOLETE<br />

OBSOLETE<br />

OBSOLETE<br />

The Part D premium submitted on the enrollment or PBP change transaction<br />

(Transaction Type 61) does not agree with the Plan’s defined Part D premium rate.<br />

The premium has been adjusted to reflect the defined rate. The correct Part D<br />

premium rate is reported in TRR data record field 24.<br />

This TRC provides additional information about an enrollment or PBP change<br />

transaction (Transaction Type 61) for which an acceptance was sent in a separate<br />

Transaction Reply with an enrollment acceptance TRC. The effective date of the<br />

enrollment for which this information is pertinent is reported in TRR data record field<br />

18.<br />

Plan Action: Update the Plan’s beneficiary records with the premium information in<br />

the TRR record. Take the appropriate actions as per CMS enrollment guidance.<br />

A Part C Premium Update transaction (Transaction Type 78) was submitted, however,<br />

no data change was made to the beneficiary’s record. The submitted transaction<br />

contained a Part C Premium Amount value that matched the Part C Premium Amount<br />

already on record with CMS.<br />

This transaction had no effect on the beneficiary’s records.<br />

Plan Action: None required.<br />

A submitted transaction (Transaction Types 51, 61, 72, 73, 74, 75, 01, 85) was<br />

rejected. This transaction was placed into a pending status due to multiple<br />

transactions that were concurrently processed for the same beneficiary.<br />

Subsequent transactions may have been processed while this transaction was pending.<br />

As a result, this transaction may no longer be valid.<br />

Plan Action: Research the beneficiary’s current status <strong>and</strong> resubmit any appropriate<br />

transactions.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-89 Obsolete Transaction Reply Code (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

Code Type Title Short Definition Definition<br />

207 I Part D Premium has<br />

been corrected to zero<br />

OBSOLETE<br />

An enrollment or PBP change transaction (Transaction Type 61) was submitted <strong>and</strong><br />

accepted for a Part C only Plan. This transaction contained an amount other than zero<br />

in the Part D premium field. Since a Part D premium does not apply to a Part C only<br />

Plan, the Part D premium has been corrected to be zero.<br />

This TRC provides additional information about an enrollment or PBP change<br />

transaction (Transaction Type 61) for which an acceptance was sent in a separate<br />

Transaction Reply with an acceptance TRC. The effective date of the enrollment for<br />

which this information is pertinent is reported in TRR data record field 18.<br />

208 R Plan Change Rejected<br />

Both 4Rx <strong>and</strong> non 4Rx<br />

Changes<br />

OBSOLETE<br />

Plan Action: Update the Plan’s records accordingly, ensuring that the beneficiary’s<br />

information matches zero Part D premium amount included in the TRR record.<br />

A 4Rx Record Update transaction (Transaction Type 72) was rejected because it<br />

contained information for both 4Rx <strong>and</strong> non-4Rx record updates.<br />

If any of the 4Rx (primary <strong>and</strong> secondary drug insurance) fields are populated, no<br />

other record updates can be included on the transaction.<br />

Plan Action: Submit separate Record Update transactions (Transaction Type 72) for<br />

4Rx <strong>and</strong> non-4Rx record updates.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-90 Obsolete Transaction Reply Code (TRCs)


Plan Communications User Guide Appendices, Version 6.3<br />

I.4 Transaction Reply Code (TRC) Groupings<br />

Transaction Type<br />

Code<br />

TRC TITLE<br />

Batch TRCs<br />

4RX TRC GROUPING<br />

143A<br />

190A<br />

200R<br />

201R<br />

202R<br />

203R<br />

204A<br />

209R<br />

242I<br />

294I<br />

SECONDARY INSURANCE RX NUMBER CHANGE ACCEPTED<br />

NO CHANGE IN SECONDARY DRUG INFORMATION<br />

RX BIN BLANK OR NOT VALID<br />

RX ID BLANK OR NOT VALID<br />

RX GROUP NOT VALID<br />

RX PCN NOT VALID<br />

RECORD UPDATE FOR PRIMARY 4RX DATA SUCCESSFUL<br />

4RX CHANGE REJECTED, INVALID CHANGE EFFECTIVE DATE<br />

NO CHANGE IN PRIMARY DRUG INFORMATION<br />

NO 4RX INSURANCE CHANGED<br />

ALL TRANSACTIONS TRC GROUPING<br />

001 F INVALID TRANSACTION CODE<br />

002 F INVALID CORRECTION ACTION CODE<br />

003 F INVALID CONTRACT NUMBER<br />

004 R BENEFICIARY NAME REQUIRED<br />

006 R INCORRECT BIRTH DATE<br />

007 R INVALID CLAIM NUMBER<br />

008 R BENEFICIARY CLAIM NUMBER NOT FOUND<br />

009R NO BENEFICIARY MATCH<br />

022A TRANSACTION ACCEPTED CLAIM NUMBER CHANGE<br />

023A TRANSACTION ACCEPTED, NAME CHANGE<br />

037R TRANSACTION REJECTED INCORRECT EFFECTIVE DATE<br />

104R REJECTED; INVALID OR MISSING ELECTION TYPE<br />

105R REJECTED; INVALID EFFECTIVE DATE FOR ELECTION TYPE<br />

106R REJECTED, ANOTHER TRANS RCVD WITH LATER APP DATE<br />

107R REJECTED; INVALID OR MISSING PBP NUMBER<br />

108R REJECTED, ELECTION LIMITS EXCEEDED<br />

109R REJECTED, DUPLICATE PBP NUMBER<br />

156F TRANSACTION REJECTED, USER NOT AUTHORIZED FOR CONTRACT<br />

157R CONTRACT NOT AUTHORIZED FOR TRANSACTION CODE<br />

165R PROCESSING DELAYED DUE TO MARX SYSTEM PROBLEMS<br />

AUTOMATIC RESET OF NUMBER OF UNCOVERED MONTHS (NUNCMO)<br />

060R<br />

290I<br />

295M<br />

TRANSACTION REJECTED, NOT ENROLLED<br />

IEP NUNCMO RESET<br />

LOW INCOME NUNCMO RESET<br />

<strong>December</strong> <strong>28</strong>, 2012 I-91 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

BENEFICIARY CROSS REFERENCE MERGE<br />

301M<br />

302M<br />

701A<br />

702A<br />

703A<br />

704A<br />

705A<br />

706A<br />

707A<br />

708A<br />

709A<br />

710A<br />

711A<br />

712A<br />

713A<br />

714I<br />

715M<br />

716I<br />

717I<br />

MERGED BENEFICIARY, CLAIM NUMBER CHANGE<br />

ENROLLMENT CANCELLED, CLAIM NUMBER CHANGE (BENEFICIARY MERGE)<br />

CMS-ONLINE UPDATES TRC GROUPING<br />

NEW UI ENROLLMENT (OPEN ENDED)<br />

UI FILL-IN ENROLLMENT<br />

UI ENROLLMENT CANCEL (DELETE)<br />

UI ENROLLMENT CANCEL-PBP CORRECTION<br />

UI ENROLLMENT PBP CORRECTION<br />

UI ENROLLMENT CANCEL SEGMENT CORRECTION<br />

UI ENROLLMENT SEGMENT CORRECTION<br />

UI ASSIGNS END DATE<br />

UI MOVED START DATE EARLIER<br />

UI MOVED START DATE LATER<br />

UI MOVED END DATE EARLIER<br />

UI MOVED END DATE LATER<br />

UI REMOVED ENROLLMENT END DATE<br />

UI PART D OPT OUT CHANGE ACCEPTED<br />

MEDICAID CHANGE ACCEPTED<br />

UI CHANGED THE NUMBER OF UNCOVERED MONTHS<br />

UI CHANGED ONLY THE APPLICATION DATE<br />

DEMONSTRATION TRC GROUPING<br />

056R<br />

169R<br />

307A<br />

308R<br />

309I<br />

310R<br />

311A<br />

312A<br />

313R<br />

314R<br />

DEMONSTRATION ENROLLMENT REJECTED<br />

REINSURANCE DEMONSTRATION ENROLLMENT REJECTED<br />

MMP PASSIVE ENROLLMENT ACCEPTED<br />

MMP PASSIVE ENROLLMENT REJECTED<br />

NO CHANGE IN MMP OPT-OUT FLAG<br />

MMP OPT-OUT REJECTED; INVALID OPT-OUT CODE<br />

MMP OPT-OUT ACCEPTED<br />

MMP ENROLLMENT CANCELLATION ACCEPTED<br />

MMP ENROLLMENT CANCELLATION REJECTED<br />

INVALID CANCELLATION TRANSACTION<br />

<strong>December</strong> <strong>28</strong>, 2012 I-92 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

013 A DISENROLLMENT ACCEPTED AS SUBMITTED<br />

DISENROLLMENT TRC GROUPING<br />

014 A DISENROLLMENT DUE TO ENROLLMENT IN ANOTHER PLAN<br />

018 A AUTOMATIC DISENROLLMENT<br />

025 A DISENROLLMENT ACCEPTED, CLAIM NUMBER CHANGE<br />

026 A DISENROLLMENT ACCEPTED, NAME CHANGE<br />

050 R DISENROLLMENT REJECTED, NOT ENROLLED<br />

051 R DISENROLLMENT REJECTED, INCORRECT EFFECTIVE DATE<br />

052 R DISENROLLMENT REJECTED, DUPLICATE TRANSACTION<br />

054 R DISENROLLMENT REJECTED, RETROACTIVE EFFECTIVE DATE<br />

090M<br />

104R<br />

105R<br />

108R<br />

114R<br />

120A<br />

DATE OF DEATH ESTABLISHED<br />

REJECTED; INVALID OR MISSING ELECTION TYPE<br />

REJECTED; INVALID EFFECTIVE DATE FOR ELECTION TYPE<br />

REJECTED; ELECTION LIMITS EXCEEDED<br />

DRUG COVERAGE CHANGE REJECTED; NOT AEP<br />

PREMIUM PAYMENT OPTION CHANGE SENT TO W/H AGENCY<br />

151 I DISENROLLMENT ACCEPTED, INVALID DISENR REASON CODE<br />

205 I INVALID DISENROLLMENT REASON CODE<br />

036R<br />

042R<br />

044R<br />

116R<br />

<strong>28</strong>4R<br />

<strong>28</strong>8A<br />

<strong>28</strong>9R<br />

291I<br />

296R<br />

292R<br />

110R<br />

127R<br />

1<strong>28</strong>R<br />

129I<br />

139A<br />

162R<br />

164R<br />

189A<br />

DISENROLLMENT CANCELLATION TRC GROUPING<br />

TRANSACTION REJECTED BENEFICIARY IS DECEASED<br />

TRANSACTION REJECTED, BLOCKED<br />

TRANSACTION REJECTED, OUTSIDE CONTRACT PERIOD<br />

ENROLLMENT OR CHANGE REJECTED; INVALID SEGMT NUM<br />

CANCELLATION REJECTED, ENROLL/DISENROLL CANCELLATION<br />

DISENROLLMENT CANCELLATION ACCEPTED<br />

DISENROLLMENT CANCELLATION REJECTED<br />

ENROLLMENT REINSTATED, DISENROLLMENT CANCELLATION<br />

DISENROLL CANCEL REJECTED, REINSTATEMENT CONFLICT (CONFLICTS WITH AN EXISTING<br />

ENROLLMENT)<br />

DISENROLLMENT TRANSACTION (TC 51)<br />

Rejected when used to attempt an enrollment Cancellation<br />

DISENROLLMENT REJECTED, WAS CANCELLATION ATTEMPT<br />

EGHP TRC GROUPING<br />

REJECTED; NO PART A AND NO EGHP ENROLLMENT WAIVER<br />

PART D ENROLLMENT REJECTED, EMPLOYER SUBSIDY<br />

PART D ENROLL REJECT, EMPLYR SBSDY SET: NO PRIOR TRN<br />

PART D ENROLL ACCEPT, EMP SBSDY SET: PRIOR TURN REJECT<br />

EGHP FLAG CHANGE ACCEPTED<br />

INVALID EGHP FLAG VALUE<br />

EGHP FLAG VALUE NOT 'Y'<br />

NO CHANGE IN EGHP FLAG<br />

<strong>December</strong> <strong>28</strong>, 2012 I-93 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

ENROLLMENT RECON TRC GROUPING<br />

600R UI TRANSACTION OVERRIDE<br />

601R CASEWORK BENEFICIARY<br />

602R NO DISCREPANCY<br />

603R 2007 DATE IS NOT VALID<br />

604A DISENROLLMENT<br />

605R RECON TRANSACTION DENIED<br />

606I DIRECT BILL<br />

607A ENROLLMENT ACCEPTED AS SUBMITTED<br />

608A ENROLLMENT ACCEPTED WITH CMS ESTABLISHED EFFECTIVE AND CMS END DATE<br />

609A ENROLLMENT ACCEPTED WITH CMS ESTABLISHED EFFECTIVE<br />

610A ENROLLMENT ACCEPTED WITH CMS ESTABLISHED END DATE<br />

611R NO DISCREPANCY IN 2006<br />

ENROLLMENT TRC GROUPING<br />

011 A ENROLLMENT ACCEPTED AS SUBMITTED<br />

015 A ENROLLMENT CANCELED<br />

016 I ENROLLMENT ACCEPTED, OUT OF AREA<br />

017 I ENROLLMENT ACCEPTED, PAYMENT DEFAULT RATE<br />

019 R ENROLLMENT REJECTED- NO PART- A & PART-B ENTITLEMENT<br />

020 R ENROLLMENT REJECTED-PACE UNDER 55<br />

032 R ENROLLMENT REJECTED, BENEFICIARY NOT ENTIT PART B<br />

033 R ENROLLMENT REJECTED, BENEFICIARY NOT ENTIT PART A<br />

034 R ENROLLMENT REJECTED, BENEFICIARY IS NOT AGE 65<br />

035 R ENROLLMENT REJECTED, BENEFICIARY IS IN HOSPICE<br />

036 R TRANSACTION REJECTED, BENEFICIARY IS DECEASED<br />

038 R ENROLLMENT REJECTED, DUPLICATE TRANSACTION<br />

039 R ENROLLMENT REJECTED, CURRENTLY ENOLL IN SAME PLAN<br />

042 R TRANSACTION REJECTED, BLOCKED<br />

044 R TRANSACTION REJECTED, OUTSIDE CONTRACT PERIOD<br />

045 R ENROLLMENT REJECTED, BENEFICIARY IS IN ESRD<br />

056R DEMONSTRATION ENROLLMENT REJECTED<br />

100 A PBP CHANGE ACCEPTED AS SUBMITTED<br />

102 R REJECTED; INCORRECT OR MISSING APPLICATION DATE<br />

103 R ICEP/IEP ELECTION, MISSING A/B ENTITLEMENT DATE<br />

104R REJECTED; INVALID OR MISSING ELECTION TYPE<br />

105R REJECTED; INVAILD EFFECTIVE DATE FOR ELECTION TYPE<br />

106R REJECTED; ANOTHER TRANSACTION RECEIVED WITH LATER APPLICATION DATE<br />

108R REJECTED; ELECTION LIMITS EXCEEDED<br />

114R DRUG COVERAGE CHANGE REJECTED; NOT AEP<br />

116R ENROLLMENT OR CHANGE REJECTED; INVALID SEGMT NUM<br />

120A PREMIUM PAYMENT OPTION CHANGE SENT TO W/H AGENCY<br />

124R ENROLLMENT/CHANGE REJECTED; INVALID UNCOVERED MONTHS<br />

126R ENROLLMENT/CHANGE REJECTED; INVALID CRED CVRG FLAG<br />

<strong>December</strong> <strong>28</strong>, 2012 I-94 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

127R<br />

1<strong>28</strong>R<br />

129I<br />

133R<br />

134I<br />

150I<br />

176R<br />

184R<br />

196R<br />

211R<br />

212A<br />

246A<br />

247A<br />

248R<br />

249R<br />

250R<br />

251R<br />

268I<br />

269I<br />

307A<br />

308R<br />

312A<br />

313R<br />

PART D ENROLLMENT REJECTED; EMPLOYER SUBSIDY STATUS<br />

PART D ENROLLMENT REJECT, EMPLYR SBSDY SET; NO PRIOR TRN<br />

PART D ENROLL ACCEPT; EMP SBSDY SET; PRIOR TRN REJECT<br />

PART D ENROLL REJECTED; INVALID SECNDRY INSUR FLAG<br />

MISSING SECONDARY INSURANCE INFORMATION<br />

ENROLLMENT ACCEPTED, EXCEEDS CAPACITY LIMIT<br />

TRANSACTION REJECTED, ANOTHER TRANSACTION ACCEPTED<br />

ENROLLMENT REJECTED, BENEFICIARY IS Medicaid<br />

TRANSACTION REJECTED, BENE NOT ELIGIBLE FOR PART D<br />

RE-ASSIGNMENT ENROLLMENT REJECTED<br />

RE-ASSIGNMENT ENROLLMENT ACCEPTED<br />

GAP ENROLLMENT ACCEPTED; NO CHANGE TO DATES<br />

GAP ENROLLMENT ACCEPTED; NEW END DATE<br />

GAP ENROLLMENT REJECTED; INVALID END DATE<br />

GAP ENROLLMENT OVERLAP AE, FE OR POS/LI NET PERIOD<br />

GAP ENROLLMENT DATES FALL WITHIN ANOTHER ENROLLMENT<br />

GAP ENROLLMENT NOT IN RETRO FILE<br />

BENEFICIARY HAS DIALYSIS PERIOD<br />

BENEFICIARY HAS TRANSPLANT<br />

MMP PASSIVE ENROLLMENT ACCEPTED<br />

MMP PASSIVE ENROLLMENT REJECTED<br />

MMP ENROLLMENT CANCELLATION ACCEPTED<br />

MMP ENROLLMENT CANCELLATION REJECTED<br />

060R<br />

<strong>28</strong>5A<br />

<strong>28</strong>6R<br />

<strong>28</strong>7A<br />

292R<br />

312A<br />

313R<br />

ENROLLMENT CANCELLATION TRC GROUPING<br />

TRANSACTION REJECTED, NOT ENROLLED<br />

ENROLLMENT CANCELLATION ACCEPTED<br />

ENROLLMENT CANCELLATION REJECTED<br />

ENROLLMENT REINSTATED<br />

DISENROLLMENT REJECTED, WAS CANCELLATION ATTEMPT<br />

MMP ENROLLMENT CANCELLATION ACCEPTED<br />

MMP ENROLLMENT CANCELLATION REJECTED<br />

314R<br />

INVALID CANCELLATION TRANSACTION<br />

ESRD TRC GROUPING<br />

055 M ESRD CANCELLATION<br />

073 M ESRD STATUS SET<br />

074 M ESRD STATUS TERMINIATED<br />

135 M BENEFICIARY HAS STARTED DIALYSIS TREATMENTS<br />

136 M BENEFICIARY HAS ENDED DIALYSIS TREATMENTS<br />

137 M BENEFICIARY HAS RECEIVED A KIDNEY TRANSPLANT<br />

268I<br />

269I<br />

BENEFICIARY HAS DIALYSIS PERIOD<br />

BENEFICIARY HAS TRANSPLANT<br />

<strong>December</strong> <strong>28</strong>, 2012 I-95 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

000I<br />

264I<br />

299I<br />

257F<br />

258F<br />

259F<br />

263F<br />

071M<br />

072M<br />

177M<br />

178M<br />

218M<br />

219M<br />

117A<br />

118A<br />

121M<br />

166R<br />

194M<br />

223I<br />

077M<br />

078M<br />

097R<br />

098R<br />

099M<br />

184R<br />

227R<br />

245M<br />

<strong>28</strong>0I<br />

120A<br />

124R<br />

126R<br />

141A<br />

187A<br />

215R<br />

216I<br />

217R<br />

NO DATA TO REPORT<br />

PAYMENT NOT YET COMPLETED<br />

CORRECTION TO PREVIOUSLY FAILED PAYMENT<br />

FAILED PAYMENT<br />

FAILED TRCs GROUPING<br />

FAILED; BIRTH DATE INVALID FOR DATABASE INSERTION<br />

FAILED; EFFECTIVE DATE INVALID FOR DATABASE INSERTION<br />

FAILED; END DATE INVALID FOR DATABASE INSERTION<br />

APPLICATION DATE INVALID FOR DATABASE INSERTION<br />

HOSPICE TRC GROUPING<br />

HOSPICE STATUS SET<br />

HOSPICE STATUS TERMINATED<br />

CHANGE IN LATE ENROLLMENT PENALTY<br />

LATE ENROLLMENT PENALTY RESCINDED<br />

LEP RESET UNDONE<br />

LEP RESET ACCEPTED<br />

FBD AUTO ENROLLMENT ACCEPTED<br />

LIS FACILITATED ENROLLMENT ACCEPTED<br />

LOW INCOME PERIOD STATUS<br />

LATE ENROLLMENT PENALTY/LEP TRC GROUPING<br />

LIS/AUTO/FACI TRC GROUPING<br />

PART D FBD AUTO ENROLLMENT OR FACILITATED ENROLLMENT REJECTED<br />

DEEMED CORRECTION<br />

LOW INCOME PERIOD CLOSED<br />

MEDICAID STATUS SET<br />

MEDICAID STATUS TERMINATED<br />

MEDICAID PREVIOUSLY TURNED ON<br />

MEDICAID PREVIOUSLY TURNED OFF<br />

MEDICAID PERIOD CHANGE/CANCELLATION<br />

MEDICAID TRC GROUPING<br />

ENROLLMENT REJECTED, BENEFICIARY IS IN MEDICAID<br />

MEDICARE SECONDARY PAYER/MSP TRC GROUPING<br />

AGED/DISABLED TRANSACTION REJECTED-INVALID TRANSACTION TYPE<br />

MEMBER HAS MSP PERIOD<br />

MEMBER MSP PERIOD HAS ENDED<br />

NUMBER OF UNCOVERED MONTHS/NUNCMO TRC GROUPING<br />

PREMIUM PAYMENT OPTION CHANGE SENT TO W/H AGENCY<br />

ENROLLMENT/CHANGE REJECTED, INVALID UNCOV MONTHS<br />

ENROLLMENT/CHANGE REJECTED, INVALID CRED CVRG FLAG<br />

UNCOVERED MONTHS CHANGE ACCEPTED<br />

NO CHANGE IN NUMBER OF UNCOVERED MONTHS INFORMATION<br />

UNCOVERED MONTHS CHANGE REJECTED, INCORRECT EFF DATE<br />

UNCOVERED MONTHS EXCEEDS MAX POSSIBLE VALUE<br />

CAN'T CHANGE NUMBER OF UNCOVERED MONTHS<br />

<strong>December</strong> <strong>28</strong>, 2012 I-96 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

290I<br />

295M<br />

300R<br />

060R<br />

116R<br />

134I<br />

140A<br />

171R<br />

172R<br />

188A<br />

130R<br />

131A<br />

241I<br />

210A<br />

220R<br />

119A<br />

120A<br />

122R<br />

123R<br />

144M<br />

170I<br />

173R<br />

179A<br />

182I<br />

191A<br />

206I<br />

213I<br />

222I<br />

237I<br />

240A<br />

243R<br />

252I<br />

253M<br />

267M<br />

IEP NUNCMO RESET<br />

LOW INCOME NUNCMO RESET<br />

NUNCMO CHANGE REJECTED, EXCEEDS MAX POSSIBLE VALUE<br />

PLAN CHANGES TRC GROUPING<br />

TRANSACTION REJECTED, NOT ENROLLED IN PLAN<br />

ENROLLMENT OR CHANGE REJECTED; INVALID SEGMT NUM<br />

MISSING SECONDARY INSURANCE INFORMATION<br />

SEGMENT ID CHANGE ACCEPTED<br />

RECORD UPDATE REJECTED, INVALID CHG EFFECTIVE DATE<br />

CHANGE REJECTED; CREDITABLE COVERAGE//2 DRUG INFO NOT APPLICABLE<br />

NO CHANGE IN SEGMENT ID<br />

PART D OPT OUT TRC GROUPING<br />

PART D OPT-OUT REJECTED, OPT-OUT FLAG NOT VALID<br />

PART D OPT-OUT ACCEPTED<br />

NO CHANGE IN PART D OPT OUT FLAG<br />

POINT OF SALE (POS) TRC GROUPING<br />

POS ENROLLMENT ACCEPTED<br />

TRANSACTION REJECTED; INVALID POS ENROLL SOURCE CODE<br />

PREMIUM PAYMENT TRC GROUPING<br />

PREMIUM AMOUNT CHANGE ACCEPTED<br />

PREMIUM PAYMENT OPTION CHANGE SENT TO W/H AGENCY<br />

ENROLLMENT/CHANGE REJECTED, INVALID PREM AMT<br />

ENROLLMENT/CHANGE REJECTED, INVALID PREM PAY OPT CD<br />

PREMIUM PAYMENT OPTION CHANGED TO DIRECT BILL<br />

PREMIUM WITHHOLD OPTION CHANGE TO DIRECT BILL<br />

CHANGE REJECTED; PREMIUM NOT PREVIOUSLY SET<br />

TRANSACTION ACCEPTED- NO CHANGE TO PREMIUM RECORD<br />

INVALID PTC PREMIUM SUBMITTED, CORRECTED<br />

NO CHANGE IN PREMIUM WITHHOLD OPTION<br />

PART C PREMIUM HAS BEEN CORRECTED TO ZERO<br />

PREMIUM WITHHOLD OPTION CHANGE TO DIRECT BILL<br />

BENE EXCLUDED FROM TRANSMISSION TO SSA/RRB<br />

PART B PREMIUM REDUCTION SENT TO SSA<br />

TRANSACTION RECEIVED, WITHHOLDING PENDING<br />

CHANGE TO SSA WITHHOLDING REJECTED DUE TO NO SSN<br />

PREM PAYMENT OPTION CHANGED TO DIRECT BILL, NO SSN<br />

CHANGED TO DIRECT BILL; NO FUNDS WITHHELD<br />

PREMIUM PAYMENT OPTION SET TO "N" DUE TO NO PREMIUM<br />

<strong>December</strong> <strong>28</strong>, 2012 I-97 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

154M<br />

260R<br />

261R<br />

265A<br />

266R<br />

<strong>28</strong>2A<br />

<strong>28</strong>3R<br />

RESIDENCE ADDRESS CHANGE TRC GROUPING<br />

OUT OF AREA STATUS<br />

REJECTED; BAD END DATE, REJECT RESIDENCE ADDRESS CHANGE<br />

REJECTED; INCOMPLETE RESIDENCE ADDRESS INFORMATION<br />

RESIDENCE ADDRESS CHANGE ACCEPTED, NEW SCC<br />

UNABLE TO RESOLVE SSA STATE COUNTY CODES<br />

RESIDENCE ADDRESS DELETED<br />

RESIDENCE ADDRESS DELETE REJECTED<br />

120A<br />

PPO CHANGE SENT TO W/H AGENCY<br />

RRB TRC GROUPING<br />

123R<br />

144M<br />

185M<br />

186I<br />

191A<br />

222I<br />

252I<br />

254I<br />

255I<br />

256I<br />

ENROLLMENT/CHANGE REJECTED, INVALID PRE PAY OPT CD<br />

PREMIUM PAYMENT OPTION CHANGED TO DIRECT BILL<br />

WITHHOLDING AGENCY ACCEPTED TRANSACTION<br />

WITHHOLDING AGENCY REJECTED TRANSACTION<br />

NO CHANGE IN PREMIUM WITHHOLD OPTION<br />

BENE EXCLUDED FROM TRANSMISSION TO SSA/RRB<br />

PRE PAYMENT OPTION CHANGED TO DIRECT BILL; NO SSN<br />

BENE SET TO DIRECT BILL, SPANS JURISDICTION<br />

PLAN SUBMITTED RRB W/H FOR SSA BENE<br />

PLAN SUBMITTED SSA W/H FOR RRB BENE<br />

262R<br />

085M<br />

138M<br />

154M<br />

305M<br />

BAD RRB PREMIUM WITHHOLD EFFECTIVE DATE<br />

SCC ADDRESS TRC GROUPING<br />

STATE AND COUNTY CODE CHANGE<br />

BENEFICIARY ADDRESS CHANGE TO OUTSIDE THE U.S.<br />

OUT OF AREA STATUS<br />

ZIP CODE CHANGE<br />

SPECIAL REPLY TRC GROUPING<br />

990-995 APPEAR ON SPECIAL TRR GENERATED FOR SPECIFIC PURPOSE. WHEN A SPECIAL TRR PRODUCES ONE<br />

OF THESE CODES, CMS WILL PROVIDE COMMUNICATIONS TO EXPLAIN THE TRC<br />

996 EOY LOSS OR LOW INCOME SUBSIDY STATUS<br />

997-999 APPEAR ON SPECIAL TRR GENERATED FOR SPECIFIC PURPOSE. WHEN A SPECIAL TRR PRODUCES ONE<br />

OF THESE CODES, CMS WILL PROVIDE COMMUNICATIONS TO EXPLAIN THE TRC<br />

185M<br />

186I<br />

195M<br />

235I<br />

236I<br />

243R<br />

WITHHOLDING AGENCY ACCEPTED TRANSACTION<br />

WITHHOLDING AGENCY REJECTED TRANSACTION<br />

SSA TRC GROUPING<br />

SSA UNSOLICITED RESPONSE (SSA WITHHOLD UPDATE)<br />

SSA ACCEPTED PART B REDUCTION TRANSACTION<br />

SSA REJECTED PART B REDUCTION TRANSACTION<br />

CHANGE TO SSA WITHHOLDING REJECTED DUE TO NO SSN<br />

048 R NURSEING HOME CERTIFIABLE STATUS SET<br />

SYSTEM NOTIFICATION TRC GROUPING<br />

<strong>December</strong> <strong>28</strong>, 2012 I-98 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

062 R CORRECTION REJECTED, OVERLAPS OTHER PERIOD<br />

075 A INSTITUTIONAL STATUS SET<br />

079 M PART A TERMINATION<br />

080 M PART A REINSTATEMENT<br />

081 M PART B TERMINIATION<br />

082 M PART B REINSTATEMENT<br />

086 M CLAIM NUMBER CHANGE<br />

087 M NAME CHANGE<br />

088 M SEX CODE CHANGE<br />

089 M DATE OF BIRTH CHANGE<br />

090 M DATE OF DEATH ESTABLISHED<br />

091 M DATE OF DEATH REMOVED<br />

092 M DATE OF DEATH CORRECTED<br />

121M LOW INCOME PERIOD STATUS<br />

152 M RACE CODE CHANGE<br />

154M OUT OF AREA STATUS<br />

155 M INCARCERATION NOTIFICATION RECEIVED<br />

158 M INSTITUTIONAL PERIOD CHANGE/CANCELLATION<br />

159 M NURSING HOME CERT PERIOD CHANGE/CANCELLATION<br />

165 R PROCESSING DELAYED DUE TO MARX SYSTEM PROBLEMS<br />

194M DEEMED CORRECTION<br />

197M PART D ELIGIBILITY TERMINATION<br />

198M PART D ELIGIBILITY REINSTATEMENT<br />

267M PREMIUM PAYMENT OPTION SET TO "N" DUE TO NO PREMIUM<br />

270M BENEFICIARY TRANSPLANT HAS ENDED<br />

<strong>December</strong> <strong>28</strong>, 2012 I-99 TRC Groupings


Plan Communications User Guide Appendices, Version 6.3<br />

I.5 Payment Reply Codes<br />

Table I-4 lists the reply codes returned for transactions found in Table I-1.<br />

PRC Types:<br />

A - Accepted - A transaction is accepted <strong>and</strong> the requested action is applied<br />

(Example: enrollment or disenrollment)<br />

R - Rejected - A transaction is rejected due to an error or other condition. The<br />

requested action is not applied to the CMS System. The TRC code<br />

indicates the reason for the transaction rejection. The Plan should<br />

analyze the rejection to validate the submitted transaction <strong>and</strong> to<br />

determine whether to resubmit the transaction with corrections.<br />

I -<br />

Informational - These replies accompany Accepted TRC replies <strong>and</strong> provide<br />

additional information about the transaction or Beneficiary. For<br />

example: If an enrollment transaction for a Beneficiary who is “out of<br />

area” is accepted, the Plan receives an accepted TRC (TRC 011) <strong>and</strong><br />

an additional reply is included in the TRR that gives the Plan the<br />

additional information that the Beneficiary is “Out of Area” (TRC<br />

016).<br />

M - Maintenance - These replies provide information to <strong>Plans</strong> about their Beneficiaries<br />

enrolled in their Plan. They are sent in response to information<br />

received by CMS. For example: If CMS is informed of a change in a<br />

Beneficiary’s claim number, a reply is included in the Plan’s TRR<br />

with TRC 086, giving the Plan the new claim number.<br />

F - Failed - A transaction failed due to an error or other condition <strong>and</strong> the<br />

requested action did not occur. The TRC code indicates the reason for<br />

the transaction’s failure. The Plan should analyze the failed<br />

transaction <strong>and</strong> determine whether to resubmit with corrections.<br />

Table I-4: Payment Reply Codes<br />

Code/Type* Title Short<br />

Definition<br />

Definition<br />

000<br />

I<br />

264<br />

I<br />

299<br />

I<br />

No Data to<br />

Report<br />

Payment Not<br />

Yet Completed<br />

Correction to<br />

Previously<br />

Failed Payment<br />

NO REPORT<br />

Monthly Payment Exception Report:<br />

On the MPER it indicates the presence of all prospective<br />

payments for the plan (contract/PBP), none are missing.<br />

Plan Action: None<br />

NO PAYMENT A transaction was accepted requiring a payment calculation. The<br />

calculation has not been completed.<br />

Plan Action: None<br />

RESTORED<br />

PYMT<br />

A previously incomplete payment calculation is now completed.<br />

Plan Action: None required.<br />

<strong>December</strong> <strong>28</strong> , 2012 I-100 Payment Reply Codes


Plan Communications User Guide Appendices, Version 6.3<br />

I.6 MMR Adjustment Reason Codes<br />

Table I-5 lists the adjustment reasons <strong>and</strong> their associated codes.<br />

Table I-5: Adjustment Reason Codes<br />

Code<br />

Description<br />

01 Notification of Death of Beneficiary<br />

02 Retroactive Enrollment<br />

03 Retroactive Disenrollment<br />

04 Correction to Enrollment Date<br />

05 Correction to Disenrollment Date<br />

06 Correction to Part A Entitlement<br />

07 Retroactive Hospice Status<br />

08 Retroactive ESRD Status<br />

09 Retroactive Institutional Status<br />

10 Retroactive Medicaid Status<br />

11 Retroactive Change to State County Code<br />

12 Date of Death Correction<br />

13 Date of Birth Correction<br />

14 Correction to Sex Code<br />

15 Obsolete<br />

16 Obsolete<br />

17 For APPS use only<br />

18 Part C Rate Change<br />

19 Correction to Part B Entitlement<br />

20 Retroactive Working Aged Status<br />

21 Retroactive NHC Status<br />

22 Disenrolled Due to Prior ESRD<br />

23 Demo Factor Adjustment<br />

24 Retroactive Change to Bonus Payment<br />

25 Part C Risk Adj Factor Change/Recon<br />

26 Mid-year Part C Risk Adj Factor Change<br />

27 Retroactive Change to Congestive Heart Failure (CHF) Payment<br />

<strong>28</strong> Retroactive Change to BIPA Part B Premium Reduction Amount<br />

29 Retroactive Change to Hospice Rate<br />

30 Retroactive Change to Basic Part D Premium<br />

31 Retroactive Change to Part D Low Income Premium Subsidy Change<br />

32 Retroactive Change to Estimated Cost-Sharing Amount<br />

33 Retroactive Change to Estimated Reinsurance Amount<br />

34 Retroactive Change Basic Part C Premium<br />

<strong>December</strong> <strong>28</strong>, 2012 I-101 MMR Adjustment<br />

Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

Code<br />

Description<br />

35 Retroactive Change to Rebate Amount<br />

36 Part D Rate Change<br />

37 Part D Risk Adjustment Factor Change<br />

38 Part C Segment ID Change<br />

41 Part D Risk Adjustment Factor Change (ongoing)<br />

42 Retroactive MSP Status<br />

43 Retroactive Plan Premium Waiver Update<br />

44 Retroactive correction of previously failed Payment (affects Part C <strong>and</strong> D)<br />

45 Disenroll for Failure to Pay Part D IRMAA Premium – Reported for Pt C <strong>and</strong> Pt D<br />

46 Correction of Part D Eligibility – Reported for Pt D<br />

50 Payment adjustment due to Beneficiary Merge<br />

90 System of Record History Alignment<br />

94 Special Payment Adjustment Due to Clean-Up<br />

<strong>December</strong> <strong>28</strong>, 2012 I-102 MMR Adjustment<br />

Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

I.7 State Codes<br />

Table I-6 lists the numeric <strong>and</strong> character code for all states.<br />

Table I-6: State Code Table<br />

State / Territory Numeric Code Character Code<br />

Alabama 01 AL<br />

Alaska 02 AK<br />

Arizona 03 AZ<br />

Arkansas 04 AR<br />

California 05 CA<br />

Colorado 06 CO<br />

Connecticut 07 CT<br />

Delaware 08 DE<br />

District of Columbia (Washington DC) 09 DC<br />

Florida 10 FL<br />

Georgia 11 GA<br />

Hawaii 12 HI<br />

Idaho 13 ID<br />

Illinois 14 IL<br />

Indiana 15 IN<br />

Iowa 16 IA<br />

Kansas 17 KS<br />

Kentucky 18 KY<br />

Louisiana 19 LA<br />

Maine 20 ME<br />

Maryl<strong>and</strong> 21 MD<br />

Massachusetts 22 MA<br />

Michigan 23 MI<br />

Minnesota 24 MN<br />

Mississippi 25 MS<br />

Missouri 26 MO<br />

Montana 27 MT<br />

Nebraska <strong>28</strong> NE<br />

Nevada 29 NV<br />

New Hampshire 30 NH<br />

New Jersey 31 NJ<br />

New Mexico 32 NM<br />

New York 33 NY<br />

North Carolina 34 NC<br />

North Dakota 35 ND<br />

Ohio 36 OH<br />

Oklahoma 37 OK<br />

Oregon 38 OR<br />

Pennsylvania 39 PA<br />

Puerto Rico 40 PR<br />

<strong>December</strong> <strong>28</strong>, 2012 I-103 State Codes


Plan Communications User Guide Appendices, Version 6.3<br />

State / Territory Numeric Code Character Code<br />

Rhode Isl<strong>and</strong> 41 RI<br />

South Carolina 42 SC<br />

South Dakota 43 SD<br />

Tennessee 44 TN<br />

Texas 45 TX<br />

Utah 46 UT<br />

Vermont 47 VT<br />

Virgin Isl<strong>and</strong>s 48 VI<br />

Virginia 49 VA<br />

Washington 50 WA<br />

West Virginia 51 WV<br />

Wisconsin 52 WI<br />

Wyoming 53 WY<br />

Africa 54<br />

Asia 55<br />

Canada 56<br />

Ctrl America/West Indies/Alvarado (Honduras) 57<br />

Himariotis (Greece) (Europe) 58<br />

Ibarra (Mexico) 59<br />

Oceania (Australia & Isl<strong>and</strong>s in the Pacific) 60<br />

Bush (Philippine Isl<strong>and</strong>s) 61<br />

South America 62<br />

U.S. Possessions 63<br />

American Samoa 64<br />

Gogue (Guam) 65<br />

Dirksz (Aruba) 78<br />

Lynch (APO NE) 94<br />

Correa (APO) 95<br />

St. Peter (Plaisted) 99<br />

<strong>December</strong> <strong>28</strong>, 2012 I-104 State Codes


Plan Communications User Guide Appendices, Version 6.3<br />

I.8 Entitlement Status <strong>and</strong> Enrollment Reason Codes<br />

The tables below list the codes for Part A <strong>and</strong> Part B Enrollment, Entitlement <strong>and</strong> Non-Entitlement<br />

1.8.1 Entitlement Status Code Tables<br />

Part A – Entitlement Status Codes<br />

The following codes occur when the Part A Entitlement Date is present <strong>and</strong> the Part A<br />

Termination Date is blank:<br />

Code<br />

E<br />

G<br />

Y<br />

Definition<br />

Free Part A Entitlement<br />

Entitled due to good cause<br />

Currently entitled, premium is payable<br />

The following codes occur when the Part A Entitlement Date is present <strong>and</strong> the Part A<br />

Termination Date is also present:<br />

Code<br />

C<br />

S<br />

T<br />

W<br />

X<br />

Definition<br />

No longer entitled due to disability cessation<br />

Terminated, no longer entitled under ESRD provision<br />

Terminated for non-payment of premiums<br />

Voluntary withdrawal from premium Part A coverage<br />

Free Part A terminated because of Title II termination<br />

Part A – Non Entitlement Status Codes<br />

The following codes occur when there is no Part A Entitlement<br />

Date <strong>and</strong> no Part A Termination Date:<br />

Code<br />

D<br />

F<br />

H<br />

N<br />

R<br />

Definition<br />

Coverage denied<br />

Terminated due to invalid enrollment or enrollment voided<br />

Ineligible for free Part A, or did not enroll for premium Part A<br />

Not valid SSA HIC, used by CMS 3 rd party sys for potential PTA entitled date<br />

Refused benefits<br />

<strong>December</strong> <strong>28</strong>, 2012 I-105 Entitlement Status <strong>and</strong><br />

Enrollment Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

Part A - Enrollment Reason Codes<br />

Code Definition<br />

A Attainment of age 65<br />

B<br />

Equitable relief<br />

Code Definition<br />

D Disability – Under age 65 entitlement<br />

G General Enrollment Period<br />

I<br />

Initial Enrollment Period<br />

J<br />

MQGE entitlement<br />

K Renal disease not reason for entitled prior to 65 or 25 th month of disability<br />

L<br />

Late filing<br />

M Termination based on renal entitlement but disability based on entitlement continues<br />

N Age 65 <strong>and</strong> uninsured<br />

P<br />

Potentially insured beneficiary is enrolled for <strong>Medicare</strong> coverage only<br />

Q Quarters of coverage requirements are involved<br />

R<br />

Residency requirements are involved<br />

T<br />

Disabled working individual<br />

U Unknown blank = not applicable; e.g. Part A data is generated at age 64 years, 8 months<br />

Part B - Entitlement Status Codes<br />

The following codes occur when the Part B Entitlement Date is present <strong>and</strong> the Part B<br />

Termination Date is blank:<br />

Code<br />

G<br />

Y<br />

Entitled due to good cause<br />

Currently entitled, premium is payable<br />

Definition<br />

The following codes occur when the Part B Entitlement Date is present <strong>and</strong> the Part B<br />

Termination Date is also present:<br />

Code<br />

C<br />

F<br />

S<br />

T<br />

W<br />

Definition<br />

No longer entitled due to cessation of disability<br />

Terminated due to invalid enrollment or enrollment voided<br />

Terminated, no longer entitled under ESRD provision<br />

Terminated for non-payment of premiums<br />

Voluntary withdrawal from coverage<br />

<strong>December</strong> <strong>28</strong>, 2012 I-106 Entitlement Status <strong>and</strong><br />

Enrollment Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

Part B – Non Entitlement Reason Codes<br />

The following codes occur when there is no Part B Entitlement Date <strong>and</strong> no Part B<br />

Termination Date:<br />

Code<br />

D<br />

N<br />

R<br />

Definition<br />

Coverage denied<br />

No Foreign/Puerto Rican Beneficiary is not entitled to SMI or dually/Technically entitled<br />

Beneficiary ID not entitled to SMI.<br />

Refused benefits<br />

Part B - Enrollment Reason Codes<br />

Code<br />

B<br />

C<br />

D<br />

F<br />

G<br />

I<br />

K<br />

M<br />

R<br />

S<br />

T<br />

U<br />

Definition<br />

Equitable Relief<br />

Good Cause<br />

Deemed date of birth<br />

Working aged<br />

General enrollment period<br />

Initial enrollment period<br />

Renal disease was a reason for entitlement prior to age 65 or prior to the 25 th month of disability<br />

Renal entitlement terminated, but disability based entitlement continues<br />

Residency requirements are involved<br />

State buy-in<br />

Disabled working Individual *<br />

* = future – current CMS program edits do not create this code<br />

Unknown<br />

<strong>December</strong> <strong>28</strong>, 2012 I-107 Entitlement Status <strong>and</strong><br />

Enrollment Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

I.9 Disenrollment Reason Codes<br />

Table I-7 lists the reason codes for Disenrollment.<br />

Table I-7: Disenrollment Reason Code Table<br />

Disenrollment<br />

Reason Number<br />

Disenrollment Reason Description<br />

MARx<br />

UI<br />

AUTO-<br />

DIS<br />

PLAN<br />

SUB’D<br />

1 FAILURE TO PAY PREMIUMS N/A N/A N/A<br />

2<br />

3<br />

RELOCATION OUT OF PLAN SERVICE AREA<br />

(NO SPECIAL PROVISIONS)<br />

FAILURE TO CONVERT TO RISK<br />

PROVISIONS<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

4 FRAUD N/A N/A N/A<br />

5 LOSS OF PART B ENTITLEMENT N/A Y N/A<br />

6<br />

LOSS OF PART A ENTITLEMENT (PLAN-<br />

SPECIFIC)<br />

N/A Y N/A<br />

7 FOR CAUSE Y N/A N/A<br />

8 REPORT OF DEATH N/A Y N/A<br />

9<br />

10<br />

11<br />

12<br />

13<br />

TERMINATION OF CONTRACT (CMS-<br />

INITIATED)<br />

TERMINATION OF<br />

CONTRACT/PBP/SEGMENT (PLAN<br />

WITHDRAWAL)<br />

VOLUNTARY DISENROLLMENT THROUGH<br />

PLAN<br />

VOLUNTARY DISENROLLMENT THROUGH<br />

DISTRICT OFFICE<br />

DISENROLLMENT BECAUSE OF<br />

ENROLLMENT IN ANOTHER PLAN<br />

N/A Y N/A<br />

N/A Y N/A<br />

Y N/A Y<br />

N/A N/A N/A<br />

N/A Y N/A<br />

14 RETROACTIVE N/A N/A N/A<br />

15 TERMINATED IN ERROR BY CMS SYSTEM N/A N/A N/A<br />

16<br />

17<br />

END OF SCC CONDITIONAL ENROLLMENT<br />

PERIOD<br />

BENE DOES NOT MEET AGE CRITERION<br />

(PLAN-SPECIFIC)<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

18 ROLLOVER N/A Y N/A<br />

19 TERMINATED BY SSA DISTRICT OFFICE N/A N/A N/A<br />

20 INVALID ENROLLMENT WITH ESRD N/A Y N/A<br />

21<br />

22<br />

23<br />

CANNOT TRAVEL/POOR HEALTH/TO<br />

HMO/PLAN DOCTORS<br />

SPOUSE IS NO LONGER MEMBER OF<br />

HMO/PLAN<br />

COULDN'T USE MEDICARE CARD TO SEE<br />

OTHER PLAN<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

<strong>December</strong> <strong>28</strong>, 2012 I-108 Disenrollment Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

Disenrollment<br />

Reason Number<br />

Disenrollment Reason Description<br />

MARx<br />

UI<br />

AUTO-<br />

DIS<br />

PLAN<br />

SUB’D<br />

24 DID NOT KNOW I JOINED THIS HMO N/A N/A N/A<br />

25<br />

26<br />

27<br />

<strong>28</strong><br />

DIFFICULTY REACHING HMO/PLAN<br />

DOCTOR BY PHONE PROBLEM<br />

CALLED HMO/PLAN COULD NOT GET HELP<br />

WITH PROBLEM<br />

DISSATISFIED WITH MEDICAL CARE/DOCS<br />

OR HOSPITAL<br />

TOLD BY PLAN DOCTORS OR STAFF I<br />

SHOULD DISENROLL<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

29 PREFER TRADITIONAL MEDICARE N/A N/A N/A<br />

30<br />

HAVE OTHER HEALTH INSURANCE<br />

BENEFITS AVAILABLE<br />

N/A N/A N/A<br />

31 FOUND HMO/PLAN TOO CONFUSING N/A N/A N/A<br />

32 MY CLAIMS/BILLS WERE NOT PAID N/A N/A N/A<br />

33 HAD LITTLE OR NO CHOICE OF SPECIALIST N/A N/A N/A<br />

34<br />

35<br />

36<br />

37<br />

41<br />

42<br />

43<br />

44<br />

TREATED DISCOURTEOUSLY BY<br />

DOCTOR/NURSE/STAFF<br />

DOCTOR COULDN'T IMPROVE MY<br />

CONDITION<br />

HMO/PLAN MEDICAL GROUP WAS<br />

LOCATED TOO FAR AWAY<br />

HAD LIMITED OR NO CHOICE OF MY<br />

PRIMARY DOCTOR<br />

YOU MOVED PERMANENTLY OUT OF<br />

AREA WHERE PLAN PROVIDES SERVIC<br />

YOUR DOCTOR OR THE PLAN TOLD YOU<br />

TO DISENROLL<br />

YOUR DOCTOR DIDN'T GIVE YOU GOOD<br />

QUALITY CARE<br />

YOU USED UP THE PRESCRIPTION<br />

ALLOWANCE<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

45 THE PLAN COST YOU TOO MUCH N/A N/A N/A<br />

46<br />

YOU COULDN'T GET CARE WHEN YOU<br />

NEEDED IT<br />

N/A N/A N/A<br />

47 YOUR DOCTOR ISN'T IN THE PLAN N/A N/A N/A<br />

48<br />

49<br />

YOU DIDN'T KNOW YOU SIGNED UP FOR<br />

THIS PLAN<br />

YOU DIDN'T LIKE HOW THE PLAN<br />

WORKED<br />

N/A N/A N/A<br />

N/A N/A N/A<br />

54 PART A OR B START DATE CHANGE N/A Y N/A<br />

56<br />

BENEFICIARY MEDICAID PERIOD<br />

RECEIVED<br />

N/A N/A N/A<br />

<strong>December</strong> <strong>28</strong>, 2012 I-109 Disenrollment Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

Disenrollment<br />

Reason Number<br />

Disenrollment Reason Description<br />

MARx<br />

UI<br />

AUTO-<br />

DIS<br />

PLAN<br />

SUB’D<br />

57 BENEFICIARY HOSPICE PERIOD RECEIVED N/A Y N/A<br />

59 INVALID ENROLLMENT WITH HOSPICE N/A Y N/A<br />

60<br />

BENEFICIARY LIVES IN USA LESS THAN<br />

183 DAYS A YEAR<br />

N/A N/A N/A<br />

61 LOSS OF PART D ELIGIBILITY N/A Y N/A<br />

62<br />

PART D DISENROLLMENT DUE TO FAILURE<br />

TO PAY IRMAA<br />

N/A Y N/A<br />

63** MMP OPT-OUT AFTER ENROLLED Y Y Y<br />

64** LOSS OF DEMONSTRATION ELIGIBILITY Y Y Y<br />

88 CONVERSION N/A N/A N/A<br />

90<br />

ENROLLMENT CANCELLED DUE TO<br />

BENEFICIARY MERGE<br />

N/A Y N/A<br />

91 FAILURE TO PAY PREMIUMS Y N/A Y<br />

92 RELOCATION OUT OF PLAN SERVICE AREA Y N/A Y<br />

93<br />

LOST SPECIFIC PLAN ELIGIBILITY (SNP<br />

ONLY)<br />

Y N/A Y<br />

99 OTHER (NOT SUPPLIED BY BENE) N/A N/A Y*<br />

*Plan cannot submit 99; it is assigned as a default value by the system only.<br />

**Only valid for MMP Disenrollments, Disenrollment Cancellations or Enrollment Cancellations.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-110 Disenrollment Reason Codes


Plan Communications User Guide Appendices, Version 6.3<br />

I.10 BEQ Response File Error Condition Table<br />

I.10.1 Request File Error Conditions<br />

The following table contains File Level Error information. File Level Errors represent conditions<br />

in which a BEQ Request File is rejected <strong>and</strong> not processed.<br />

Table I-8: File Level Error information<br />

SOURCE OF<br />

ERROR<br />

Header Record<br />

Header Record<br />

Trailer Record<br />

Trailer Record<br />

File Content<br />

ERROR MESSAGE<br />

The Header Record is<br />

missing.<br />

The Header Record is<br />

Invalid.<br />

The Trailer Record is<br />

missing.<br />

The Trailer Record is<br />

invalid.<br />

The File has no<br />

Transactions.<br />

ERROR CONDITION<br />

● The Header Record is not provided on the file.<br />

● The Header Record is unreadable.<br />

● More than one Header Record is provided on the file.<br />

● The Header Record is incorrectly formatted.<br />

● The Header Record contains invalid values.<br />

● The Header Record contains Critical Fields that are not<br />

provided.<br />

● The Trailer Record is not provided on the file.<br />

● The Trailer Record is unreadable.<br />

● More than one Trailer Record is provided on the file.<br />

● The Trailer Record is incorrectly formatted.<br />

● The Trailer Record contains invalid values.<br />

● The Trailer Record contains Critical Fields that are not<br />

populated.<br />

● The Record Count in the Trailer Record is more than 2<br />

different from the actual number of Detail Records<br />

(Transactions) in the file.<br />

● There are no Transactions (Detail Records) found in the file.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-111 BEQ Response File Error Condition<br />

Table


Plan Communications User Guide Appendices, Version 6.3<br />

I.10.2 Request Transaction Detail Record Error Conditions<br />

The following Flag fields are provided in the Response File Detail Record. Flag fields represent<br />

the successful or unsuccessful result of processing data within a Transaction Detail Record of the<br />

input file.<br />

Table I-9: Error Conditions<br />

FLAG FLAG CODE FLAG CODE RESULT FLAG RESULT CONDITION<br />

Processed Flag Y The Transaction is<br />

accepted for processing.<br />

All critical fields on the Transaction are populated<br />

with valid values.<br />

Processed Flag N The Transaction is not<br />

accepted for processing.<br />

At least one critical field on the Transaction is<br />

populated with a value other than the prescribed<br />

valid values.<br />

Beneficiary<br />

Match Flag<br />

Y<br />

The beneficiary on the<br />

Transaction is<br />

successfully located in<br />

the MBD.<br />

The beneficiary is successfully located by the<br />

combination of the HICN or RRB, SSN; date of<br />

birth, <strong>and</strong> gender.<br />

Beneficiary<br />

Match Flag<br />

N<br />

The beneficiary on the<br />

Transaction is not<br />

successfully located in<br />

the MBD.<br />

The beneficiary is not successfully located by the<br />

combination of the HICN or RRB, SSN; date of<br />

birth, <strong>and</strong> gender.<br />

Beneficiary<br />

Match Flag<br />

SPACE<br />

No attempt made to<br />

locate the beneficiary on<br />

the MBD.<br />

An invalid condition exists in the Transaction Detail<br />

Record such as an unexpected, absent, or invalid<br />

value in a Critical Field.<br />

<strong>December</strong> <strong>28</strong>, 2012 I-112 BEQ Response File Error Condition<br />

Table


Plan Communications User Guide Appendices, Version 6.3<br />

J: Report Files<br />

This appendix provides a description <strong>and</strong> sample snapshot of each report file. Table J-1 lists the<br />

names of all the accessible reports to <strong>Plans</strong> <strong>and</strong> on which page of this appendix J they are<br />

located. Note that the examples provided for the reports do not identify any person living or<br />

dead; all Beneficiary, contract, <strong>and</strong> user information is fictional. Appendix J identifies the<br />

naming conventions for all reports sent to <strong>Plans</strong>. The user needs dataset names to request a report<br />

through the mainframe.<br />

Table J-1: Reports Lookup Table<br />

Section Name Page<br />

J.1 BIPA 606 Payment Reduction Report J-2<br />

J.2 Bonus Payment Report J-6<br />

J.3 HMO Bill Itemization Report J-11<br />

J.4 Monthly Membership Detail Report – <strong>Drug</strong> Report (Part D) J-12<br />

J.5 Monthly Membership Detail Report – Non <strong>Drug</strong> Report (Part C) J-13<br />

J.6 Monthly Membership Summary Report J-15<br />

J.7 Monthly Summary of Bills Report J-19<br />

J.8 Part C Risk Adjustment Model Output Report J-21<br />

J.9 RAS RxHCC Model Output Report<br />

J-22<br />

AKA - Part D Risk Adjustment Model Output Report<br />

J.10 Payment Records Report J-23<br />

J.11 Plan Payment Report (PPR) (APPS Payment Letter) J-24<br />

J.12 Interim Plan Payment Report (IPPR) J-29<br />

J.13 No Premium Due Report Format J-30<br />

J.14 Sample BEQ Request File Pass <strong>and</strong> Fail Acknowledgement J-36<br />

Note: See Appendix K for complete information on Dataset Names.<br />

<strong>December</strong> <strong>28</strong>, 2012 J-1 Report Files


Plan Communications User Guide Appendices, Version 6.3<br />

J.1 BIPA 606 Payment Reduction Report<br />

Description<br />

This report lists members for whom the MCO is paying a portion of the Part B premium. This report only reflects data for periods prior to 2006.<br />

Example<br />

1 RUN DATE: 2003/12/10<br />

PAY MONTH: 2004/01 BIPA606 PAYMENT REDUCTION REPORT PAGE: 1<br />

CONTRACT#: H3333 REPORT DATE: 2003/12/10<br />

0 PBP ID: 026<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BIPA BLEND TOT BIPA BLEND BLEND PT-B BLEND TOT<br />

NUMBER I E DATE RC DATES RATE W/O BIPA AMOUNT PT-A PLUS BIPA PLUS BIPA<br />

X<br />

123456789A PARR H F 191211<strong>28</strong> 200401-200401 31.25 609.52 -31.25 362.64 215.63 578.27<br />

123456789A MONET M F 19170402 200401-200401 31.25 677.32 -31.25 400.05 246.02 646.07<br />

123456789D GARRISO M F 19130812 200401-200401 31.25 744.55 -31.25 437.15 276.15 713.30<br />

123456789A GEISEL A M 19190407 200401-200401 31.25 687.<strong>28</strong> -31.25 387.95 268.08 656.03<br />

123456789A BLAZE H M 19170901 200401-200401 31.25 688.39 -31.25 406.45 250.69 657.14<br />

123456789D AMES E F 19061027 200401-200401 31.25 607.62 -31.25 361.59 214.78 576.37<br />

123456789D KLEIN P F 19270531 200401-200401 31.25 459.05 -31.25 243.34 184.46 427.80<br />

123456789A DAVIDS J M 19200513 200401-200401 31.25 787.43 -31.25 444.78 311.40 756.18<br />

123456789B DAVIDS E F 19180521 200401-200401 31.25 744.30 -31.25 443.<strong>28</strong> 269.77 713.05<br />

123456789A MURRAY E F 19190614 200401-200401 31.25 724.95 -31.25 418.69 275.01 693.70<br />

123456789A MURDOCK P M 19161126 200401-200401 31.25 734.80 -31.25 433.85 269.70 703.55<br />

123456789D TROTTER S F 19230411 200401-200401 31.25 905.11 -31.25 518.10 355.76 873.86<br />

123456789A RUSS D M 19220119 200401-200401 31.25 860.56 -31.25 486.14 343.17 829.31<br />

123456789A PRINCE A F 19041104 200401-200401 31.25 646.97 -31.25 384.27 231.45 615.72<br />

123456789A LONG I M 19190101 200401-200401 31.25 723.08 -31.25 427.31 264.52 691.83<br />

123456789A SHAPIRO S M 19100313 200401-200401 31.25 858.29 -31.25 506.54 320.50 827.04<br />

<strong>December</strong> <strong>28</strong>, 2012 J-2 BIPA 606 Payment Reduction Report


Plan Communications User Guide Appendices, Version 6.3<br />

123456789A WEISMAN W M 19160511 200401-200401 31.25 900.15 -31.25 5<strong>28</strong>.34 340.56 868.90<br />

123456789A BERGER B F 19190910 200401-200401 31.25 641.60 -31.25 370.61 239.74 610.35<br />

123456789A KELLER H F 19190906 200401-200401 31.25 580.79 -31.25 335.44 214.10 549.54<br />

123456789A RYAN J M 19181027 200401-200401 31.25 857.21 -31.25 505.94 320.02 825.96<br />

123456789A FALK S M 19080704 200401-200401 31.25 749.63 -31.25 442.25 276.13 718.38<br />

123456789A DUFFY S F 19120426 200401-200401 31.25 640.90 -31.25 381.26 2<strong>28</strong>.39 609.65<br />

123456789D ADAMS E F 19101114 200401-200401 31.25 657.82 -31.25 391.<strong>28</strong> 235.29 626.57<br />

123456789A TATE V F 19160825 200401-200401 31.25 643.82 -31.25 382.53 230.04 612.57<br />

123456789A SCOTT P F 19140929 200401-200401 31.25 709.80 -31.25 422.54 256.01 678.55<br />

123456789D SMALL T F 19110616 200401-200401 31.25 633.83 -31.25 377.02 225.56 602.58<br />

123456789A WILEY R F 19100427 200401-200401 31.25 573.46 -31.25 341.11 201.10 542.21<br />

123456789D DENNIS D F 19020517 200401-200401 31.25 641.90 -31.25 381.47 229.18 610.65<br />

123456789A HAMMIL J M 19090425 200401-200401 31.25 822.26 -31.25 483.25 307.76 791.01<br />

123456789A VOSS E F 19060220 200401-200401 31.25 664.03 -31.25 394.51 238.27 632.78<br />

123456789A TUTTLE A M 19140320 200401-200401 31.25 948.38 -31.25 559.93 357.20 917.13<br />

123456789A BARTLET A M 19190119 200401-200401 31.25 939.40 -31.25 530.59 377.56 908.15<br />

123456789D GREEN H F 192206<strong>28</strong> 200401-200401 31.25 641.60 -31.25 370.61 239.74 610.35<br />

123456789A RUSK M M 19171115 200401-200401 31.25 859.79 -31.25 507.03 321.51 8<strong>28</strong>.54<br />

123456789A POWELL W M 19061121 200401-200401 31.25 850.31 -31.25 501.80 317.26 819.06<br />

123456789D MCDONAL H F 19191007 200401-200401 31.25 565.59 -31.25 326.62 207.72 534.34<br />

123456789D KING L F 19130321 200401-200401 31.25 839.02 -31.25 498.73 309.04 807.77<br />

123456789D LEWIS M F 19150407 200401-200401 31.25 781.74 -31.25 464.48 <strong>28</strong>6.01 750.49<br />

PBP ID: 026 TOTALS: 38 $ 27,602.25 $ -1,187.50 $ 26,414.75<br />

AGED REDUCTION: $ -1,187.50<br />

DIB REDUCTION: $ 0.00<br />

1 RUN DATE: 2003/12/10<br />

PAY MONTH: 2004/01 BIPA606 PAYMENT REDUCTION REPORT PAGE: 2<br />

CONTRACT#: H3333 REPORT DATE: 2003/12/10<br />

<strong>December</strong> <strong>28</strong>, 2012 J-3 BIPA 606 Payment Reduction Report


Plan Communications User Guide Appendices, Version 6.3<br />

0 PBP ID: 027<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BIPA BLEND TOT BIPA BLEND BLEND PT-B BLEND TOT<br />

NUMBER I E DATE RC DATES RATE W/O BIPA AMOUNT PT-A PLUS BIPA PLUS BIPA<br />

X<br />

123456789B MARKS E F 19220112 200401-200401 73.38 685.30 -73.38 395.50 216.42 611.92<br />

123456789A MONTGOM M F 19111113 200401-200401 73.38 723.40 -73.38 430.47 219.55 650.02<br />

123456789D SCHREIB A F 19190814 200401-200401 73.38 520.09 -73.38 300.46 146.25 446.71<br />

123456789A BECKER V F 19191224 200401-200401 73.38 520.09 -73.38 300.46 146.25 446.71<br />

123456789A BRIDGE H M 19171219 200401-200401 73.38 715.74 -73.38 422.51 219.85 642.36<br />

123456789A EDELMAN S M 19160825 200401-200401 73.38 765.94 -73.38 452.29 240.27 692.56<br />

123456789A ZEMLACK A F 19090715 200401-200401 73.38 640.90 -73.38 381.26 186.26 567.52<br />

123456789A ROSENST L M 19180629 200401-200401 73.38 712.25 -73.38 420.62 218.25 638.87<br />

123456789B ROSENST L F 19231014 200401-200401 73.38 558.72 -73.38 322.85 162.49 485.34<br />

123456789D ROLNICK I F 19090215 200401-200401 73.38 633.83 -73.38 377.02 183.43 560.45<br />

123456789D KAIN M F 19150907 200401-200401 73.38 831.80 -73.38 494.02 264.40 758.42<br />

123456789A SHANK W M 19200707 200401-200401 73.38 756.68 -73.38 427.40 255.90 683.30<br />

123456789A KAY T M 19121119 200401-200401 73.38 926.09 -73.38 546.43 306.<strong>28</strong> 852.71<br />

123456789A GOLDMAN S M 19160221 200401-200401 73.38 734.80 -73.38 433.85 227.57 661.42<br />

123456789D MILLMAN E F 19110709 200401-200401 73.38 692.33 -73.38 411.35 207.60 618.95<br />

123456789A JARRETT J M 19110519 200401-200401 73.38 722.82 -73.38 426.42 223.02 649.44<br />

123456789B JARRETT E F 19170417 200401-200401 73.38 643.79 -73.38 382.51 187.90 570.41<br />

123456789C1 MENG A M 19500301 200401-200401 73.38 347.11 -73.38 189.69 84.04 273.73<br />

123456789A BLACK M F 19151205 200401-200401 73.38 665.44 -73.38 395.27 196.79 592.06<br />

123456789A TAUBMAN E F 19420723 200401-200401 73.38 689.25 -73.38 376.64 239.23 615.87<br />

123456789D DRUSKIN M F 19290303 200401-200401 73.38 424.51 -73.38 216.96 134.17 351.13<br />

123456789A SMITH V F 19130908 200401-200401 73.38 631.21 -73.38 375.57 182.26 557.83<br />

123456789D JEFFRIE C F 19000201 200401-200401 73.38 646.99 -73.38 384.<strong>28</strong> 189.33 573.61<br />

123456789A PRITZKE S M 19120929 200401-200401 73.38 722.86 -73.38 426.44 223.04 649.48<br />

123456789A SAMUELS S M 19180331 200401-200401 73.38 713.94 -73.38 421.52 219.04 640.56<br />

123456789A KANTER D F 19150103 200401-200401 73.38 653.71 -73.38 389.01 191.32 580.33<br />

123456789D NORMAN F F 19230914 200401-200401 73.38 559.86 -73.38 323.49 162.99 486.48<br />

<strong>December</strong> <strong>28</strong>, 2012 J-4 BIPA 606 Payment Reduction Report


Plan Communications User Guide Appendices, Version 6.3<br />

123456789A MARTIN L F 19150709 200401-200401 73.38 653.71 -73.38 389.01 191.32 580.33<br />

123456789A COHEN R M 19171019 200401-200401 73.38 811.54 -73.38 479.27 258.89 738.16<br />

123456789D RUBIN J F 19121124 200401-200401 73.38 857.74 -73.38 509.52 274.84 784.36<br />

123456789A TROUTMA J M 19110502 200401-200401 73.38 980.15 -73.38 577.46 329.31 906.77<br />

123456789A ROUND P F 19170127 200401-200401 73.38 569.89 -73.38 339.14 157.37 496.51<br />

123456789A AZMAN F F 19180203 200401-200401 73.38 734.82 -73.38 436.59 224.85 661.44<br />

123456789D PRATT F F 19080919 200401-200401 73.38 746.11 -73.38 443.95 2<strong>28</strong>.78 672.73<br />

123456789A LOMBARD F F 19160926 200401-200401 73.38 834.62 -73.38 496.76 264.48 761.24<br />

123456789D BALTIMO M F 19080301 200401-200401 73.38 837.34 -73.38 498.26 265.70 763.96<br />

123456789D HOWARD J F 19070402 200401-200401 73.38 580.51 -73.38 345.61 161.52 507.13<br />

123456789A COLUMBU F M 19180904 200401-200401 73.38 1,004.55 -73.38 593.51 337.66 931.17<br />

123456789C2 CARROLL K M 19580202 200401-200401 73.38 333.27 -73.38 182.23 77.66 259.89<br />

PBP ID: 027 TOTALS: 39 $ 26,783.70 $ -2,861.82 $ 23,921.88<br />

AGED REDUCTION: $ -2,568.30<br />

DIB REDUCTION: $ -293.52<br />

0 CONTRACT: H3333 TOTALS: 77 $ 54,385.95 $ -4,049.32 $ 50,336.63<br />

AGED REDUCTION: $ -3,755.80<br />

DIB REDUCTION: $ -293.52<br />

<strong>December</strong> <strong>28</strong>, 2012 J-5 BIPA 606 Payment Reduction Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.2 Bonus Payment Report<br />

Description<br />

This report lists members for whom the MCO receives a bonus. (MCOs are paid a bonus for extending services to beneficiaries in some underserved areas.) This<br />

report only reflects data for periods prior to 2004.<br />

Example<br />

1 RUN DATE: 2003/10/03<br />

PAY MONTH: 2003/03 BONUS PAYMENT REPORT PAGE: 2<br />

CONTRACT#: H5555 REPORT DATE: 2003/10/03<br />

0 STATE/COUNTY CODE: 27030<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

123456789A JONES J M 19<strong>28</strong>0611 200303-200303 3.00 480.44 7.66 6.75 14.41 263.03 231.82 $ 494.85<br />

123456789A CHANG A M 19140222 200303-200303 3.00 647.58 11.47 7.96 19.43 393.75 273.26 $ 667.01<br />

123456789B CHANG F F 19151105 200303-200303 3.00 569.89 10.17 6.92 17.09 349.31 237.67 $ 586.98<br />

123456789A COHEN A M 19250714 200303-200303 3.00 650.30 10.65 8.86 19.51 365.74 304.07 $ 669.81<br />

123456789A PULASKI W M 19290909 200303-200303 3.00 449.12 7.14 6.33 13.47 245.23 217.36 $ 462.59<br />

* STATE/COUNTY 27030 TOTALS: 5 $ 2,797.33 $ 83.91 $ 2,881.24<br />

0 STATE/COUNTY CODE: 27040<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

123456789A KIRBY C M 19220222 200303-200303 3.00 599.47 10.16 7.83 17.99 348.73 268.73 $ 617.46<br />

<strong>December</strong> <strong>28</strong>, 2012 J-6 Bonus Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

* STATE/COUNTY 27040 TOTALS: 1 $ 599.47 $ 17.99 $ 617.46<br />

0 STATE/COUNTY CODE: 27080<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

123456789C1 TAPLEY P F 19500322 200303-200303 3.00 398.14 5.60 6.34 11.94 192.42 217.66 $ 410.08<br />

123456789A WALT A F 19350710 200303-200303 3.00 340.68 5.16 5.06 10.22 177.24 173.66 $ 350.90<br />

123456789A ZIMMER J M 19351008 200303-200303 3.00 358.55 5.46 5.29 10.75 187.58 181.72 $ 369.30<br />

123456789B6 ZIMMER R F 19350717 200303-200303 3.00 307.84 4.62 4.62 9.24 158.58 158.50 $ 317.08<br />

* STATE/COUNTY 27080 TOTALS: 4 $ 1,405.21 $ 42.15 $ 1,447.36<br />

0 STATE/COUNTY CODE: 27110<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

123456789A DUNN W M 19460531 200303-200303 3.00 375.60 6.<strong>28</strong> 4.99 11.27 215.51 171.36 $ 386.87<br />

* STATE/COUNTY 27110 TOTALS: 1 $ 375.60 $ 11.27 $ 386.87<br />

1 RUN DATE: 2003/10/03<br />

PAY MONTH: 2003/03 BONUS PAYMENT REPORT PAGE: 3<br />

CONTRACT#: H5555 REPORT DATE: 2003/10/03<br />

0 STATE/COUNTY CODE: 27130<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

<strong>December</strong> <strong>28</strong>, 2012 J-7 Bonus Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

123456789A UNGER W M 19<strong>28</strong>0219 200303-200303 3.00 540.82 8.84 7.38 16.22 303.52 253.52 $ 557.04<br />

* STATE/COUNTY 27130 TOTALS: 1 $ 540.82 $ 16.22 $ 557.04<br />

0 STATE/COUNTY CODE: 27140<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

123456789A LABER E F 19290807 200303-200303 3.00 384.07 5.89 5.63 11.52 202.18 193.41 $ 395.59<br />

123456789A SESLER S F 19371109 200303-200303 3.00 307.79 4.62 4.62 9.24 158.55 158.48 $ 317.03<br />

123456789B TAPLEY M F 19250503 200303-200303 3.00 476.04 7.59 6.69 14.<strong>28</strong> 260.53 229.79 $ 490.32<br />

123456789A EVERETT S F 19551018 200303-200303 3.00 398.14 5.60 6.34 11.94 192.42 217.66 $ 410.08<br />

123456789A ROY R M 19240904 200303-200303 3.00 541.75 8.86 7.40 16.26 304.05 253.96 $ 558.01<br />

123456789A LEGAUL E F 19490514 200303-200303 3.00 398.14 5.60 6.34 11.94 192.42 217.66 $ 410.08<br />

123456789A NOYES J M 19350402 200303-200303 3.00 358.55 5.46 5.29 10.75 187.58 181.72 $ 369.30<br />

123456789A SAVAGE L F 19370220 200303-200303 3.00 309.36 4.64 4.64 9.<strong>28</strong> 159.44 159.20 $ 318.64<br />

123456789A BRUCAT P M 19210502 200303-200303 3.00 599.47 10.16 7.83 17.99 348.73 268.73 $ 617.46<br />

123456789A CAPOZZI I F 19220115 200303-200303 3.00 511.73 8.87 6.49 15.36 304.39 222.70 $ 527.09<br />

123456789A DYER D M 19301227 200303-200303 3.00 449.12 7.14 6.33 13.47 245.23 217.36 $ 462.59<br />

123456789D NAETHEL L F 19340427 200303-200303 3.00 307.84 4.62 4.62 9.24 158.58 158.50 $ 317.08<br />

123456789A DUFFY R M 19260410 200303-200303 3.00 541.75 8.86 7.40 16.26 304.05 253.96 $ 558.01<br />

123456789A RIVARD J M 19<strong>28</strong>0509 200303-200303 3.00 481.36 7.68 6.76 14.44 263.56 232.24 $ 495.80<br />

123456789A BROWN M F 19350908 200303-200303 3.00 307.84 4.62 4.62 9.24 158.58 158.50 $ 317.08<br />

123456789A TEEPLE A F 19450506 200303-200303 3.00 465.37 7.01 6.95 13.96 240.58 238.75 $ 479.33<br />

123456789A VICARY C M 19361021 200303-200303 3.00 360.94 5.50 5.32 10.82 188.94 182.82 $ 371.76<br />

123456789A HEATON G M 19170306 200303-200303 3.00 647.58 11.47 7.96 19.43 393.75 273.26 $ 667.01<br />

123456789A NOLLEY J M 19460216 200303-200303 3.00 407.91 6.81 5.43 12.24 233.87 186.<strong>28</strong> $ 420.15<br />

123456789A JAMIESO W M 19210627 200303-200303 3.00 599.47 10.16 7.83 17.99 348.73 268.73 $ 617.46<br />

123456789A HORNE J M 19171211 200303-200303 3.00 647.58 11.47 7.96 19.43 393.75 273.26 $ 667.01<br />

123456789A BROWN J M 19<strong>28</strong>04<strong>28</strong> 200303-200303 3.00 457.37 7.<strong>28</strong> 6.44 13.72 249.92 221.17 $ 471.09<br />

123456789A ARMSTRO V F 19360130 200303-200303 3.00 307.84 4.62 4.62 9.24 158.58 158.50 $ 317.08<br />

<strong>December</strong> <strong>28</strong>, 2012 J-8 Bonus Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

123456789A REESE T M 19<strong>28</strong>0415 200303-200303 3.00 457.37 7.<strong>28</strong> 6.44 13.72 249.92 221.17 $ 471.09<br />

123456789A BESSLER N F 19170530 200303-200303 3.00 569.89 10.17 6.92 17.09 349.31 237.67 $ 586.98<br />

123456789A WAMBEKE B F 19360803 200303-200303 3.00 310.39 4.66 4.65 9.31 160.03 159.67 $ 319.70<br />

123456789A STEINBE H F 19251012 200303-200303 3.00 451.39 7.18 6.36 13.54 246.52 218.41 $ 464.93<br />

* STATE/COUNTY 27140 TOTALS: 27 $ 12,056.05 $ 361.70 $ 12,417.75<br />

1 RUN DATE: 2003/10/03<br />

PAY MONTH: 2003/03 BONUS PAYMENT REPORT PAGE: 4<br />

CONTRACT#: H5555 REPORT DATE: 2003/10/03<br />

0 STATE/COUNTY CODE: 27150<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

123456789A COFFIN A M 19290424 200303-200303 3.00 449.12 7.14 6.33 13.47 245.23 217.36 $ 462.59<br />

123456789C1 CARACCA S M 19620723 200303-200303 3.00 296.38 5.20 3.69 8.89 178.49 126.78 $ 305.27<br />

123456789A ALTMAN R M 19251111 200303-200303 3.00 541.75 8.86 7.40 16.26 304.05 253.96 $ 558.01<br />

123456789A ROBICH R F 19241116 200303-200303 3.00 451.39 7.18 6.36 13.54 246.52 218.41 $ 464.93<br />

123456789A RACHES C M 19340308 200303-200303 3.00 358.55 5.46 5.29 10.75 187.58 181.72 $ 369.30<br />

123456789A WELLS A M 19340809 200303-200303 3.00 358.55 5.46 5.29 10.75 187.58 181.72 $ 369.30<br />

123456789A WASHBU H F 19140313 200303-200303 3.00 569.89 10.17 6.92 17.09 349.31 237.67 $ 586.98<br />

123456789A ROSE C M 19160131 200303-200303 3.00 647.58 11.47 7.96 19.43 393.75 273.26 $ 667.01<br />

123456789D BEARDS J F 19330729 200303-200303 3.00 318.53 4.80 4.76 9.56 164.66 163.43 $ 3<strong>28</strong>.09<br />

123456789A BENNETT E M 19370325 200303-200303 3.00 359.85 5.49 5.31 10.80 188.33 182.32 $ 370.65<br />

123456789D LOESER S F 19320223 200303-200303 3.00 384.07 5.89 5.63 11.52 202.18 193.41 $ 395.59<br />

123456789A ACKLEY P F 19190304 200303-200303 3.00 580.72 10.01 7.41 17.42 343.60 254.54 $ 598.14<br />

123456789A NEWMAN R F 19290129 200303-200303 3.00 384.07 5.89 5.63 11.52 202.18 193.41 $ 395.59<br />

123456789A LUZAR B F 19361016 200303-200303 3.00 342.80 5.20 5.09 10.29 178.45 174.64 $ 353.09<br />

123456789A CRAIG R F 19330708 200303-200303 3.00 311.53 4.68 4.67 9.35 160.68 160.20 $ 320.88<br />

123456789A ZUSSBLE N M 19310707 200303-200303 3.00 449.12 7.14 6.33 13.47 245.23 217.36 $ 462.59<br />

<strong>December</strong> <strong>28</strong>, 2012 J-9 Bonus Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

123456789A TEMPLE K M 19180322 200303-200303 3.00 645.95 11.44 7.94 19.38 392.82 272.51 $ 665.33<br />

123456789A COFFIN J F 19321201 200303-200303 3.00 384.07 5.89 5.63 11.52 202.18 193.41 $ 395.59<br />

* STATE/COUNTY 27150 TOTALS: 18 $ 7,833.92 $ 235.01 $ 8,068.93<br />

0 STATE/COUNTY CODE: 42380<br />

0 CLAIM SURNAME F S BIRTH ADJ PAY/ADJ BONUS BLENDED BONUS BONUS BONUS ----- BLENDED PLUS BONUS ----<br />

NUMBER I E DATE RC DATES PCT W/O BONUS PART A PART B TOTAL PART A PART B TOTAL<br />

X<br />

* STATE/COUNTY 42380 TOTALS: 0 $ 0.00 $ 0.00 $ 0.00<br />

0 ** CONTRACT H5555 TOTALS: 57 $ 25,608.40 $ 768.25 $ 26,376.65<br />

<strong>December</strong> <strong>28</strong>, 2012 J-10 Bonus Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.3 HMO Bill Itemization Report<br />

Description<br />

This report lists the Part A bills processed under <strong>Medicare</strong> fee-for-service for beneficiaries enrolled in the contract.<br />

Example<br />

1 PART A BILLS POSTED IN OCT 2002 PAGE 1<br />

BILL TYPE: INPATIENT<br />

* * * * * HMO H4444 * * * * *<br />

HMO ADM TOTAL NON-COV INP NC BLD COINSURANCE TOTAL FROM THRU COV REIM NP<br />

CLAIM NUM NAME PROV INTER PD DATE CHARGES CHARGES DED DEDUCT DAYS CHGS AMOUNT DEDUCT DATE DATE<br />

DAYS AMT CD CR<br />

123456789A BAKER 010084 00010 20020630 7821 0 812 0 0 0 0 812 20020630 20020703 0 0<br />

123456789C2 MILLER 014007 00010 20020819 8320 8320 0 0 0 0 0 0 20020819 20020920 0 0 N<br />

1 PART A BILLS POSTED IN OCT 2002 PAGE 2<br />

* * * * * HMO H4444 * * * * *<br />

BILL TYPE: HOSPICE<br />

HMO ADM TOTAL NON-COV INP NC BLD COINSURANCE TOTAL FROM THRU COV REIM NP<br />

CLAIM NUM NAME PROV INTER PD DATE CHARGES CHARGES DED DEDUCT DAYS CHGS AMOUNT DEDUCT DATE DATE<br />

DAYS AMT CD CR<br />

1234567891 CANDLE 011570 00380 20020826 3084 0 0 0 0 0 0 0 20020901 20020930 0 3084<br />

12345678946 FLICKE 011570 00380 20020912 1953 0 0 0 0 0 0 0 20020912 20020930 0 1953<br />

<strong>December</strong> <strong>28</strong>, 2012 J-11 HMO Bill Itemization Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.4 Monthly Membership Detail Report – <strong>Drug</strong> Report (Part D)<br />

Description<br />

This report lists every <strong>Medicare</strong> member of the contract <strong>and</strong> provides details about the payments <strong>and</strong> adjustments made for each Beneficiary. The two Monthly<br />

Membership Detail Reports are for drugs <strong>and</strong> for non-drugs.<br />

Example<br />

The example below is part of a Monthly Membership Detail Report containing drug information. The full report includes all members in the contract.<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

RUN DATE:20050115 MONTHLY MEMBERSHIP REPORT-DRUG PAGE: 1<br />

PAYMENT MONTH:200502 PLAN(Hzzzz) PBP(nnn) SEGMENT(mmm) PLAN NAME HERE<br />

BASIC PREMIUM | ESTIMATED REINSURANCE<br />

PART D $SS9.99 | $SS9.99<br />

S --- FLAGS ----- ------------------ PAYMENTS/ADJUSTMENTS ---------------------------<br />

CLAIM E AGE STATE P P S L L D C ADJ RA FCTR DATES LOW-INCOME COST LOW-INCOME COST<br />

NUMBER X GRP CNTY A A E 0 O I E M RES START END SHARING PERCENTAGE SHARING SUBSIDY<br />

------------ - ---- ----- O R R G U I N M C ---- -------------------------------------------------------------------<br />

SURNAME F DMG BIRTH O T T H R N S I A MTHS DIRECT SUBSIDY COVERAGE GAP<br />

I RA DATE A A B P C C T N I D PAYMENT AMT DISCOUNT TOTAL PAYMENT<br />

------------ - ---- ----- - - - - - - - - - ---- -------------------------------------------------------------------<br />

1234567890AB F 33800 XXXXXXXXXXXX 99 20.0405 200504 200505 ZZ $SSSSSS9.99<br />

FIRST G 8084 19200206 Y Y N N Y Z9 $SSSSSS9.99 $SSSSSS9.99 $SSSSSSS9.99<br />

0987654321AB M 8084 33800 Z9 20.0405 200504 200505 ZZ $SSSSSS9.99<br />

SECOND H 8084 19251008 Y Y Y Y N Z9 $SSSSSS9.99 $SSSSSS9.99 $SSSSSSS9.99<br />

<strong>December</strong> <strong>28</strong>, 2012 J-12 Monthly Membership Detail Report – <strong>Drug</strong> Report (Part D)


Plan Communications User Guide Appendices, Version 6.3<br />

J.5 Monthly Membership Detail Report – Non-<strong>Drug</strong> Report (Part C)<br />

Description<br />

This report lists every <strong>Medicare</strong> member of the contract <strong>and</strong> provides details about the payments <strong>and</strong> adjustments made for each beneficiary.<br />

Example<br />

The example below is one page of a Monthly Membership Detail Report containing non-drug information. The full report includes all members in the contract.<br />

(above benchmark bid)<br />

1 1 1 1<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

RUN DATE:20090124 MONTHLY MEMBERSHIP REPORT - NON DRUG PAGE: 1<br />

PAYMENT MONTH:200902 PLAN(Hzzzz) PBP(nnn) SEGMENT(mmm) PLAN NAME HERE<br />

------------------------------------------------- REBATES --------------------------------------------<br />

BASIC PREMIUM | COST SHR REDUC MAND SUPP BENEFIT PART D SUPP BENEFIT PART B BAS PRM REDUC PART D BAS PRM REDUC<br />

PART A $SSS9.99 | N/A N/A N/A N/A N/A<br />

PART B $SSS9.99 | N/A N/A N/A N/A N/A<br />

S ----------- FLAGS --------------- ------------------ PAYMENTS/ADJUSTMENTS --------------------<br />

CLAIM E AGE STATE P P M F A D S C MTHS PAYMENT DATE LAG FTYPE----FACTORS-------- AMOUNT<br />

NUMBER X GRP CNTY A A H E I C R O D E E O M A B START END FRAILTY-SCORE MSP MSP<br />

------------ - ---- ----- O R R O S N N A A R D F G U M C ---- --- ------------------------------------------------------------<br />

SURNAME F DMG BIRTH O T T S R S H I I E O A H R S A PIP ADJ<br />

I RA DATE A A B P D T C D L C N U P C P I DCG REA FCTR-A FCTR-B PART A PART B TOTAL PAYMENT<br />

------------ - ---- ----- - - - - - - - - - - - - - - - - --- -----------------------------------------------------------------<br />

123456789A F 8084 33800 200405 200405 Y C 99.9999 99.9999 $SSSS9.99<br />

FIRST G 8084 19200206 Y Y 1 A Y Z9Z9 ZZ 1.0650 1.0650 $SSSSSS9.99 $SSSSSS9.99 $SSSSSSS9.99<br />

987654321B M 8084 33800 200405 200405 Y C 99.9999 99.9999 $SSSS9.99<br />

SECOND H 8084 19251008 Y Y Y Y 4 T N Z9Z9 ZZ 1.0650 1.0650 $SSSSSS9.99 $SSSSSS9.99 $SSSSSSS9.99<br />

<strong>December</strong> <strong>28</strong>, 2012 J-13 Monthly Membership Detail Report –<br />

Non-<strong>Drug</strong> Report (Part C)


Plan Communications User Guide Appendices, Version 6.3<br />

(below benchmark bid)<br />

1 1 1 1<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

RUN DATE: 20090124 MONTHLY MEMBERSHIP REPORT – NON DRUG PAGE: 1<br />

PAYMENT MONTH:200902 PLAN(Hzzzz) PBP(nnn) SEGMENT(mmm) PLAN NAME HERE<br />

------------------------------------------------- REBATES --------------------------------------------<br />

BASIC PREMIUM | COST SHR REDUC MAND SUPP BENEFIT PART D SUPP BENEFIT PART B BAS PRM REDUC PART D BAS PRM REDUC<br />

PART A N/A | $SSS9.99 $SSS9.99 $SSS9.99 $SSS9.99 $SSS9.99<br />

PART B N/A | $SSS9.99 $SSS9.99 $SSS9.99 $SSS9.99 $SSS9.99<br />

S ----------- FLAGS --------------- ------------------ PAYMENTS/ADJUSTMENTS --------------------CLAIM E AGE STATE P P M F A D S C MTHS PAYMENT DATE<br />

LAG FTYPE----FACTORS-------- AMOUNT<br />

NUMBER X GRP CNTY A A H E I C R O D E E O M A B START END FRAILTY-SCORE MSP MSP<br />

------------ - ---- ----- O R R O S N N A A R D F G U M C ---- --- ------------------------------------------------------------<br />

SURNAME F DMG BIRTH O T T S R S H I I E O A H R S A PIP ADJ<br />

I RA DATE A A B P D T C D L C N U P C P I DCG REA FCTR-A FCTR-B PART A PART B TOTAL PAYMENT<br />

------------ - ---- ----- - - - - - - - - - - - - - - - - --- -----------------------------------------------------------------<br />

1234567890AB F 8084 33800 200405 200405 Y C 99.9999 $SSSS9.99<br />

FIRST G 8084 19200206 Y Y N 1 Y Z9Z9 ZZ 1.0650 1.0650 $SSSSSS9.99 $SSSSSS9.99 $SSSSSSS9.99<br />

0987654321AB M 8084 33800 200405 200405 Y C 99.9999 99.9999 $SSSS9.99<br />

SECOND H 8084 19251008 Y Y Y Y 4 P N Z9Z9 ZZ 1.0650 1.0650 $SSSSSS9.99 $SSSSSS9.99 $SSSSSSS9.99<br />

<strong>December</strong> <strong>28</strong>, 2012 J-14 Monthly Membership Detail Report –<br />

Non-<strong>Drug</strong> Report (Part C)


Plan Communications User Guide Appendices, Version 6.3<br />

J.6 Monthly Membership Summary Report (MMSR)<br />

Description<br />

This report summarizes payments to an MCO for the month, in several categories, <strong>and</strong> adjustments, by all adjustment categories. When the report automatically<br />

generates as part of month-end processing, it covers one contract in one payment month. When the report generates on user request, it is based on the transactions<br />

received to-date for the current payment month <strong>and</strong> may generate for one contract or for all contracts in a region.<br />

Example<br />

1 1 1 1<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

RUN DATE:yyyymmdd MONTHLY MEMBERSHIP SUMMARY REPORT (PAGE 1 OF 2)<br />

PAYMENT MONTH:yyyymm<br />

PLAN: H9999 PBP(mmm) SEG(nnn) Name-of-Provider-Here<br />

CURRENT PAYMENTS<br />

PART A ---------- COUNTS ----- TOTAL MONEY PART B -------- COUNTS ----- TOTAL MONEY PART D ---------- COUNTS ----- TOTAL MONEY<br />

HOSPICE z,zzz,zz9 $$,$$$,$$$,$$9.99 HOSPICE z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

ESRD z,zzz,zz9 $$,$$$,$$$,$$9.99 ESRD z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

WA z,zzz,zz9 $$,$$$,$$$,$$9.99 WA z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

INST z,zzz,zz9 $$,$$$,$$$,$$9.99 INST z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

NHC z,zzz,zz9 $$,$$$,$$$,$$9.99 NHC z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

MCAID z,zzz,zz9 $$,$$$,$$$,$$9.99 MCAID z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

PART C PREMIUM z,zzz,zz9 $$,$$$,$$$,$$9.99 PART C PREMIUM z,zzz,zz9 $$,$$$,$$$,$$9.99 DIR SUBSDY z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

A/B COST SHR z,zzz,zz9 $$,$$$,$$$,$$9.99 A/B COST SHR z,zzz,zz9 $$,$$$,$$$,$$9.99 LIS COST SHR z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

A/B MAN SUP BN z,zzz,zz9 $$,$$$,$$$,$$9.99 A/B MAN SUP BN z,zzz,zz9 $$,$$$,$$$,$$9.99 ESTIMATD REINS z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

D BAS PRM REDU z,zzz,zz9 $$,$$$,$$$,$$9.99 D BAS PRM REDU z,zzz,zz9 $$,$$$,$$$,$$9.99 PACE PRM ADDON z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

D SUPP BENFITS z,zzz,zz9 $$,$$$,$$$,$$9.99 D SUPP BENFITS z,zzz,zz9 $$,$$$,$$$,$$9.99 PACE CSR ADDON z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

B BAS PRM REDU z,zzz,zz9 $$,$$$,$$$,$$9.99 B BAS PRM REDU z,zzz,zz9 $$,$$$,$$$,$$9.99 COV GAP DISC z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

A/D MSP REDU z,zzz,zz9 $$,$$$,$$$,$$9.99 A/D MSP REDU z,zzz,zz9 $$,$$$,$$$,$$9.99 LIPS z,zzz,zz9 $$,$$$,$$$,SS9.99<br />

ESRD MSP REDU z,zzz,zz9 $$,$$$,$$$,$$9.99 ESRD MSP REDU z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

MEMBERS z,zzz,zz9 $$,$$$,$$$,$$9.99 MEMBERS z,zzz,zz9 $$,$$$,$$$,$$9.99 MEMBERS z,zzz,zz9 $$,$$$,$$$,$$9.99<br />

MONTHS z,zzz,zz9 MONTHS z,zzz,zz9 MONTHS z,zzz,zz9<br />

AVERAGE $$$$,$$$,$$9.99 AVERAGE $$$$,$$$,$$9.99 AVERAGE $$$$,$$$,$$9.99<br />

OUT OF AREA z,zzz,zz9<br />

B PRM REDU - A $$,$$$,$$$,$$9.99 B PRM REDU - A $$,$$$,$$$,$$9.99<br />

B PRM REDU - D $$,$$$,$$$,$$$.99 B PRM REDU - D $$,$$$,$$$,$$$.99<br />

1 1 1 1<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

RUN DATE:yyyymmdd MONTHLY MEMBERSHIP SUMMARY REPORT (PAGE 2 OF 2)<br />

<strong>December</strong> <strong>28</strong>, 2012 J-15 MMSR


Plan Communications User Guide Appendices, Version 6.3<br />

PAYMENT MONTH:yyyymm<br />

PLAN: H9999 PBP(mmm) SEG(nnn) Name-of-Provider-Here<br />

ADJUSTMENT PAYMENTS<br />

ADJ<br />

REA ADJUSTMENT NUMBER MONTHS MONTHS MONTHS ----------------------- ADJUSTMENT AMOUNT ------------------------<br />

CDE DESCRIPTION OF ADJS A B D PART A PART B PART D TOTAL<br />

--- ------------------- ------- ------- ------- ------- ------------------ ------------------ ------------------ -------------------<br />

01 DEATH zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

02 RETRO ENROLL zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

03 RETRO DISENR zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

04 CORR ENROLL zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

05 CORRT DISENR zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

06 CORR PARTA E zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

07 HOSPC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

08 ESRD zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

09 INSTNHC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

10 MCAID zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

11 RETRO SCC CH zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

12 CORR DT. OF zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

13 CORR DT. OF zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

14 CORR SEX zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

18 AAPCC RT FAC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

19 CORR PARTB E zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

20 WKAGE zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

21 INSTNHC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

22 DISENROLL PR zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

<strong>December</strong> <strong>28</strong>, 2012 J-16 MMSR


Plan Communications User Guide Appendices, Version 6.3<br />

1 1 1 1<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

RUN DATE:yyyymmdd MONTHLY MEMBERSHIP SUMMARY REPORT (PAGE 2 OF 2)<br />

PAYMENT MONTH:yyyymm<br />

PLAN: H9999 PBP(mmm) SEG(nnn) Name-of-Provider-Here<br />

ADJUSTMENT PAYMENTS<br />

ADJ<br />

REA ADJUSTMENT NUMBER MONTHS MONTHS MONTHS ----------------------- ADJUSTMENT AMOUNT ------------------------<br />

CDE DESCRIPTION OF ADJS A B D PART A PART B PART D TOTAL<br />

--- ------------------- ------- ------- ------- ------- ------------------ ------------------ ------------------ -------------------<br />

01 DEATH zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

02 RETRO ENROLL zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

03 RETRO DISENR zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

04 CORR ENROLL zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

05 CORRT DISENR zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

06 CORR PARTA E zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

07 HOSPC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

08 ESRD zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

09 INSTNHC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

10 MCAID zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

11 RETRO SCC CH zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

12 CORR DT. OF zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

13 CORR DT. OF zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

14 CORR SEX zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

18 AAPCC RT FAC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

19 CORR PARTB E zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

20 WKAGE zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

21 INSTNHC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

22 DISENROLL PR zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

<strong>December</strong> <strong>28</strong>, 2012 J-17 MMSR


Plan Communications User Guide Appendices, Version 6.3<br />

1 1 1 1<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

23 DEMO FACTOR zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

25 PTC RSK ADJF zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

26 RISK ADJ FAC zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

27 RETRO CHF zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

29 HOSPICE RATE zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

30 RTRO PTD PM zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

31 RTRO PTD LIP zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

32 RTRO CST SHR zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

33 RTRO EST REI zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

34 RTRO PTC PM zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

35 RTRO REBATE zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

36 PTD RATE CHG zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

37 PTD RAF CHG zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

38 SEG ID CHG zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

41 PTD RAF ONGO zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

42 RETRO MSP zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

43 PLN WVD PRM zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

44 PYMT CORR zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

50 XRF MRG zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

94 CLNUP ADJ zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

TOTAL ADJUSTMENT zzzzzz9 zzzzzz9 zzzzzz9 zzzzzz9 $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$,$$$,$$$,$$9.99- $$$,$$$,$$$,$$9.99-<br />

TOTAL ADJUSTMENTS<br />

Months A : zzzzzzz9 Part A Amount : $$$,$$$,$$$,$$9.99-<br />

Months B : zzzzzzz9 Part B Amount : $$$,$$$,$$$,$$9.99-<br />

Months D : zzzzzzz9 Part D Amount : $$$,$$$,$$$,$$9.99-<br />

Number of Adjustments : zzzzzzz9 Total Amount : $$$,$$$,$$$,$$9.99-<br />

TOTAL PYMT AMT A $$$,$$$,$$$,$$9.99-<br />

TOTAL PYMT AMT B $$$,$$$,$$$,$$9.99-<br />

TOTAL PYMT AMT D $$$,$$$,$$$,$$9.99-<br />

SUM TOTAL AMOUNT $$$$,$$$,$$$,$$9.99-<br />

<strong>December</strong> <strong>28</strong>, 2012 J-18 MMSR


Plan Communications User Guide Appendices, Version 6.3<br />

J.7 Monthly Summary of Bills Report<br />

Description<br />

This report summarizes all <strong>Medicare</strong> fee-for-service activity, both Part A <strong>and</strong> Part B, for Beneficiaries enrolled in the contract.<br />

Example<br />

1 MONTHLY SUMMARY OF CLAIMS PAID BY CARRIERS FOR HMO ENROLLEES<br />

0 HMO NO H123A HMO NAME ABC FOUNDATION, INC. HMO FY ENDING 12/2004 CURRENT MONTH 01/2009<br />

0 TOTALS FOR THIS MONTH<br />

0 CARRIER MEDICAL REIMB TOTAL<br />

NUMBER CHARGES AMOUNT BILLS<br />

NO ACTIVITY FOR THIS HMO FOR THIS PERIOD<br />

FY TOTAL $198,903- $151,602- 4,266<br />

1 MONTHLY SUMMARY OF BILLS PAID BY INTERMEDIARIES FOR HMO ENROLLEES<br />

0 HMO NO H123B HMO NAME ABC FOUNDATION, INC. HMO FY ENDING 12/2005 CURRENT MONTH 01/2009<br />

BILLS THROUGH 01/30/2009<br />

0 ------------------ INPATIENT BILLS -------------- ------ OUTPATIENT BILLS -------- -------------- HHA BILLS ------------<br />

NON<br />

TOTAL COVERED REIMB COVERED TOTAL COVERED REIMB TOTAL TOTAL REIMB TOTAL TOTAL<br />

CHARGES CHARGES AMOUNT DAYS BILLS CHARGES AMOUNT BILLS CHARGES AMOUNT VISITS BILLS<br />

NO ACTIVITY FOR THIS HMO FOR THIS PERIOD<br />

FY TOTAL $123,526,251 $113,627,247 42,572 $570,708- $245,326 9<br />

$1,315,398 16,614 $3,309,867- 1,606 $229,640 617<br />

1 MONTHLY SUMMARY OF CLAIMS PAID BY CARRIERS FOR HMO ENROLLEES<br />

0 HMO NO H123C HMO NAME ABC FOUNDATION, INC. HMO FY ENDING 12/2005 CURRENT MONTH 01/2009<br />

0 TOTALS FOR THIS MONTH<br />

0 CARRIER MEDICAL REIMB TOTAL<br />

NUMBER CHARGES AMOUNT BILLS<br />

NO ACTIVITY FOR THIS HMO FOR THIS PERIOD<br />

FY TOTAL $548,050- $4<strong>28</strong>,202- 8,315<br />

1 MONTHLY SUMMARY OF BILLS PAID BY INTERMEDIARIES FOR HMO ENROLLEES<br />

0 HMO NO H123D HMO NAME ABC FOUNDATION, INC. HMO FY ENDING 12/2006 CURRENT MONTH 01/2009<br />

BILLS THROUGH 01/30/2009<br />

0 ------------------ INPATIENT BILLS -------------- ------ OUTPATIENT BILLS -------- -------------- HHA BILLS ------------<br />

NON<br />

TOTAL COVERED REIMB COVERED TOTAL COVERED REIMB TOTAL TOTAL REIMB TOTAL TOTAL<br />

<strong>December</strong> <strong>28</strong>, 2012 J-19 Monthly Summary of Bills Report


Plan Communications User Guide Appendices, Version 6.3<br />

CHARGES CHARGES AMOUNT DAYS BILLS CHARGES AMOUNT BILLS CHARGES AMOUNT VISITS BILLS<br />

0INTER NO 0000A<br />

PROV NO<br />

00000A 1,147 0 1,147 0 1 0 0 0 0 0 0 0<br />

------------------------------------------------------------------------------------------------------------------------------------<br />

INT TOTAL 1,147 0 1,147 0 1 0 0 0 0 0 0 0<br />

0INTER NO 0000B<br />

PROV NO<br />

00000B 4,488 0 0 0 2 0 0 0 0 0 0 0<br />

00000C 0 0 0 0 0 78- 90- 1 0 0 0 0<br />

00000D 0 0 0 0 0 102- 90- 1 0 0 0 0<br />

------------------------------------------------------------------------------------------------------------------------------------<br />

INT TOTAL 4,488 0 0 0 2 180- 180- 2 0 0 0 0<br />

0INTER NO 0000C<br />

PROV NO<br />

00000E 182,012 0 0 23 2 0 0 0 0 0 0 0<br />

------------------------------------------------------------------------------------------------------------------------------------<br />

INT TOTAL 182,012 0 0 23 2 0 0 0 0 0 0 0<br />

-HMO TOTAL 187,647 0 1,147 23 5 180- 180- 2 0 0 0 0<br />

FY TOTAL $116,001,944 $85,570,972 34,354 $937,010- $159,078 102<br />

$2,835,588 14,675 $6,493,082- 2,876 $162,661 485<br />

1<br />

MONTHLY SUMMARY OF CLAIMS PAID BY CARRIERS FOR HMO ENROLLEES<br />

0 HMO NO H123E HMO NAME ABC FOUNDATION, INC. HMO FY ENDING 12/2006 CURRENT MONTH 01/2009<br />

0 TOTALS FOR THIS MONTH<br />

0 CARRIER MEDICAL REIMB TOTAL<br />

NUMBER CHARGES AMOUNT BILLS<br />

0 01192 224 161 1<br />

0 HMO TOTAL 224 161 1<br />

FY TOTAL $750,298- $574,946- 8,412<br />

<strong>December</strong> <strong>28</strong>, 2012 J-20 Monthly Summary of Bills Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.8 Part C Risk Adjustment Model Output Report<br />

Description<br />

This report shows the Hierarchical Condition Codes (HCCs) used by RAS to calculate risk adjustment factors for each beneficiary.<br />

Example<br />

Below is part of a Risk Adjustment Model Output report. The full report shows all of the Beneficiaries in the contract.<br />

1***GROUP=H8888,CONTRACT=H8888,<br />

1RUN DATE: 20031219 RISK ADJUSTMENT MODEL OUTPUT REPORT PAGE: 1<br />

PAYMENT MONTH: 200401 PLAN: H8888 CHAMPION INSURANCE RAPMORP1<br />

0 LAST FIRST DATE OF<br />

HIC NAME NAME I BIRTH SEX & AGE GROUP<br />

------------ --------------- --------------- - -------- ---------------<br />

123456789A WOOD CHARLES W 19250225 Male75-79<br />

123456789B TREE LILLIAN L 19270418 Female75-79<br />

123456789A GRASS ALBERT A 19421213 Male60-64<br />

HCC DISEASE GROUPS: HCC019 Diabetes without Complication<br />

HCC080 Congestive Heart Failure<br />

HCC092 Specified Heart Arrhythmias<br />

INTERACTIONS: INTI01 DM_CHF<br />

<strong>December</strong> <strong>28</strong>, 2012 J-21 Part C Risk Adjustment Model Output Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.9 RAS RxHCC Model Output Report - aka - Part D RA Model Output Report<br />

Description<br />

This report shows the Hierarchical Condition Codes (HCCs) used by RAS to calculate risk adjustment factors for each beneficiary.<br />

Example<br />

Below are the first few lines of a RA Model Output report. The full report shows all of the Beneficiaries in the contract.<br />

1RUN DATE: 20060124 RISK ADJUSTMENT MODEL OUTPUT REPORT PAGE: 1<br />

PAYMENT MONTH: 200602 PLAN: H9999 ACME INSURANCE COMPANY RAPMORP2<br />

0 LAST FIRST DATE OF<br />

HIC NAME NAME I BIRTH SEX & AGE GROUP<br />

------------ ---------------------------------------- ---------------------------------- - -------- ---------------<br />

123456789A TWO RUTH M 19181122 Female85-89<br />

RXHCC DISEASE GROUPS: RXHCC019 Disorders of Lipoid Metabolism<br />

RXHCC048 Other Musculoskeletal <strong>and</strong> Connective Tissue Disorders<br />

RXHCC092 Acute Myocardial Infarction <strong>and</strong> Unstable Angina<br />

RXHCC098 Hypertensive Heart Disease or Hypertension<br />

RXHCC159 Cellulitis, Local Skin Infection<br />

123456789A BREEZE WINDY T 19620730 Female35-44<br />

RXHCC DISEASE GROUPS: RXHCC045 Disorders of the Vertebrae <strong>and</strong> Spinal Discs<br />

RXHCC085 Migraine Headaches<br />

RXHCC098 Hypertensive Heart Disease or Hypertension<br />

RXHCC113 Acute Bronchitis <strong>and</strong> Congenital Lung/Respiratory Anomaly<br />

RXHCC129 Other Diseases of Upper Respiratory System<br />

RXHCC144 Vaginal <strong>and</strong> Cervical Diseases<br />

<strong>December</strong> <strong>28</strong>, 2012 J-22 RAS RxHCC Model Output Report aka Part D Risk<br />

Adjustment Model Output Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.10 Payment Records Report<br />

Description<br />

This report lists the Part B physician <strong>and</strong> supplier claims that were processed under <strong>Medicare</strong> fee-for-service for<br />

Beneficiaries enrolled in the contract.<br />

Example<br />

1 PART B CLAIMS RECORDS POSTED IN OCT 2002 PAGE<br />

1<br />

0 * * * * *HMO H2222 * * * * *<br />

0 CLAIM NAME EXPENSE DATES ALLOWED REIMB COINSURANCE DED PHYS<br />

PAY CARRIER CARRIER INFORMATION<br />

NUMBER FIRST LAST TOTAL AMT AMT APP SUPP ID IND NUMBER<br />

PAID CONTROL NUMBER<br />

CHARGES<br />

123456789A JONES 20020917 20020917 9.72 7.78 1.94 .00 L99999 1 11111 20021014<br />

620902<strong>28</strong>3027160<br />

123456789A JONES 20020920 20020920 12.00 9.60 2.40 .00 L88888 1 11111 20021014<br />

620902<strong>28</strong>3027550<br />

123456789A JONES 20020830 20020830 12.65 10.12 2.53 .00 P77777 1 11111 20021017<br />

620902<strong>28</strong>30<strong>28</strong>810<br />

123456789A JONES 20020831 20020831 12.00 9.60 2.40 .00 P77777 1 11111 20021014<br />

620902<strong>28</strong>30<strong>28</strong>800<br />

123456789A JONES 20020915 20020915 12.00 9.60 2.40 .00 P77777 1 11111 20021014<br />

620902<strong>28</strong>30<strong>28</strong>820<br />

123456789A HOWARD 20020708 20020708 5.43 5.43 .00 .00 0000000000 1 22222<br />

20021023 0226<strong>28</strong><strong>28</strong>553000<br />

123456789A WILLS 20020908 20020908 87.97 70.38 17.59 .00 666666666 1 22222<br />

20021018 02254815230000<br />

123456789A LEE 20020920 20020920 27.21 21.77 5.44 .00 555555555 1 22222 20021016<br />

02270301676000<br />

123456789A BRILL 20011019 20011119 26.46 21.17 5.29 .00 4444444444 1 33333<br />

20021013 02266171165000<br />

123456789D SOMMER 20020916 20020916 134.47 107.58 26.89 .00 333333333 1 22222<br />

20021023 0226<strong>28</strong>34339000<br />

123456789A JONES 20020917 20020919 115.79 92.63 23.16 .00 222222 1 11111 20021005<br />

620202275864060<br />

123456789A JONES 20020925 20020925 11.16 11.16 .00 .00 111111 1 11111 20021024<br />

620202294476660<br />

123456789A JONES 20021010 20021010 <strong>28</strong>.97 <strong>28</strong>.97 .00 .00 111111 1 11111 20021024<br />

620202294476670<br />

123456789A JONES 20021011 20021011 <strong>28</strong>.97 <strong>28</strong>.97 .00 .00 111111 1 11111 20021024<br />

620202294476680<br />

<strong>December</strong> <strong>28</strong>, 2012 J-23 Payment Records Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.11 Plan Payment Report (APPS Payment Letter)<br />

Description<br />

Also known as the APPS Payment Letter, this report itemizes the final monthly payment to the MCO. This report is<br />

produced by APPS when final payments are calculated. CMS makes this report available to MCOs as part of monthend<br />

processing.<br />

Plan Payment Report (PPR) - Final<br />

The PPR includes Part D payments <strong>and</strong> adjustments, the National <strong>Medicare</strong> Education Campaign (NMEC) <strong>and</strong> COB<br />

User Fees <strong>and</strong> premium settlement information. There is one version of the PPR applicable to all <strong>Plans</strong> <strong>and</strong> it is<br />

provided monthly.<br />

Following is an updated example of a PPR or APPS Payment Letter:<br />

<strong>December</strong> <strong>28</strong>, 2012 24 Plan Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

<strong>December</strong> <strong>28</strong>, 2012 J-25 Plan Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

<strong>December</strong> <strong>28</strong>, 2012 J-26 Plan Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

<strong>December</strong> <strong>28</strong>, 2012 J-27 Plan Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

<strong>December</strong> <strong>28</strong>, 2012 J-<strong>28</strong> Plan Payment Report


Plan Communications User Guide Appendices, Version 6.3<br />

J.12 Interim Plan Payment Report (IPPR)<br />

Description<br />

Also known as the Interim Payment Letter, this report itemizes interim payments to the MCO. It is produced by APPS when interim payments are calculated.<br />

CMS computes interim payments on an as-needed basis. When this occurs, the interim payment letter is pushed to the involved Plan(s).<br />

IPPR<br />

The APPS IPPR is provided when a Plan is approved for an interim payment outside of the normal monthly process. The report contains the amount <strong>and</strong> reason<br />

for the interim payment to the Plan.<br />

<strong>Plans</strong> may request the IPPR via the MARx User Interface under the weekly reports section of the menu.<br />

12 Plan Payment Report<br />

Note: For a sample of this report, refer to I- (PPR) for the file format.<br />

<strong>December</strong> <strong>28</strong>, 2012 J-29 IPPR


Plan Communications User Guide Appendices, Version 6.3<br />

J.13 No Premium Due Report Format<br />

No Premium Due Reports are no longer generated. Only a data file is produced. The report is here for reference<br />

1 2 3 4 5 6 7 8 9 0 1 2 3<br />

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123<br />

RUN DATE: 01/15/2005 TRANSACTION REPLIES/MONTHLY ACTIVITY REPORT ID: 10<br />

REPORTING MONTH: 12/2004 PLAN (Hzzzz) PBP (nnn) SGMT (mmm) Health Plan Name Here PAGE: 1<br />

* * * PLAN-SUBMITTED TRANSACTIONS: ACCEPTED * * *<br />

--------------------------- T R A N S A C T I O N ---------------------------------------------- R E P L Y -----------------<br />

S O E L CO-PAY<br />

F E DATE OF EFF O L SRCE SPECIAL I EFF --PREMIUMS-- RPLY<br />

TC CLAIM NUMBER SURNAME I X BIRTH DATE SCC A T ID STATUS S DATE PT C PT D CODE REMARKS<br />

------------------------------------------------------------------------------------------------------------------------------------<br />

61 1234567890AB DAVIDSO F M 09/10/26 01/01/05 45850 Y A SYSGN HEWIN 1 01/01/05 100.00 200.00 011 ENROLL ACCEPTED<br />

51 1234567890AB BELMORE M F 03/27/33 01/01/05 22000 N E TV6K N 2 04/01/05 .00 85.30 014 DISNROL-NEW MCO<br />

51 123456789A DUGAN D F 07/14/17 01/01/05 45180 Y I TOE8 E 3 05/01/05 .00 113.56 014 AUTO DISENROLL<br />

<strong>December</strong> <strong>28</strong>, 2012 J-30 No Premium Due Report Format


Plan Communications User Guide Appendices, Version 6.3<br />

J.13.1 Error Condition<br />

The six following STATUS file messages generate when an error condition prevents the transaction from processing.<br />

1. Invalid User Id<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON 2006-01-27 AT 16.59.49<br />

PROCESSING STOPPED ON 2006-01-27 AT 17.00.39<br />

USER ID (aaaa ) NOT AUTHENTICATED: 2-USER ID NOT FOUND<br />

HEADER CODE= AAAAAAHEADER<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

******************************** Bottom of Data ***************************<br />

2. Invalid Header Date<br />

********************************* Top of Data*****************************<br />

TRANSACTIONS RECEIVED ON 2006-01-27 AT 16.23.22<br />

PROCESSING STOPPED ON 2006-01-27 AT 16.23.42<br />

HEADER RECORD IS MISSING OR INVALID<br />

HEADER CODE= AAAAAAHEADER<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

******************************** Bottom of Data ***************************<br />

<strong>December</strong> <strong>28</strong>, 2012 J-31 Error Condition


Plan Communications User Guide Appendices, Version 6.3<br />

3. Missing Header Record<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON AT<br />

PROCESSING STOPPED ON 2006-01-25 AT 18.11.38<br />

HEADER RECORD IS MISSING OR INVALID<br />

HEADER CODE= XXXHEADERZZZ<br />

HEADER DATE= <br />

BATCH ID =<br />

USER ID =<br />

TRAN CNTS1 =<br />

TRAN CNTS2 =<br />

TRAN CNTS3 =<br />

******************************** Bottom of Data ***************************<br />

4. Future Header Date<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON 2006-01-30 AT 16.48.37<br />

PROCESSING STOPPED ON 2006-01-30 AT 16.48.55<br />

HEADER RECORD DATE IS A FUTURE PROCESSING MONTH<br />

RESUBMIT DURING THE CORRECT PROCESSING MONTH<br />

PROCESSING MONTH=<br />

HEADER CODE= AAAAAAHEADER<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

******************************** Bottom of Data ***************************<br />

5. Header Date earlier than CCM<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON 2006-01-30 AT 16.54.05<br />

<strong>December</strong> <strong>28</strong>, 2012 J-32 Error Condition


Plan Communications User Guide Appendices, Version 6.3<br />

PROCESSING STOPPED ON 2006-01-30 AT 16.54.13<br />

HEADER RECORD DATE IS NOT EQUAL TO THE CURRENT PAYMENT MONTH<br />

PROCESSING MONTH=<br />

HEADER CODE= AAAAAAHEADER<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

******************************** Bottom of Data ***************************<br />

6. Transaction File Rejection Reason<br />

After a Specialty file is reviewed by CMS, the following STATUS messages are generated upon rejection:<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON 2010-03-23 AT 13.55.15<br />

THIS FILE WAS REJECTED BY <br />

REJECTION REASONS: <br />

TRANSACTIONS REJECTED ON 24 Mar 2010 AT 14:39:33<br />

HEADER CODE= AAAAAAHEADER RETRO<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

TOTAL TRANSACTIONS REJECTED= nnnnnnnn<br />

******************************** Bottom of Data ***************************<br />

<strong>December</strong> <strong>28</strong>, 2012 J-33 Error Condition


Plan Communications User Guide Appendices, Version 6.3<br />

J.13.2 Specialty Files<br />

If the file is a Specialty file, the following STATUS messages generate upon initial receipt:<br />

Retro File Detected<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON 2006-01-27 AT 14.23.05<br />

HEADER CODE= AAAAAAHEADER RETRO<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

PROCESSING STOPPED ON 2006-01-27 AT 14:23:39<br />

RETRO FILE DETECTED FOR USERID <br />

HEADER CODE= AAAAAAHEADER RETRO<br />

HEADER DATE= 012006<br />

******************************** Bottom of Data ***************************<br />

Rollover File Detected<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON 2006-01-27 AT 14.23.05<br />

HEADER CODE= AAAAAAHEADER POVER<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

<strong>December</strong> <strong>28</strong>, 2012 J-34 Specialty Files


Plan Communications User Guide Appendices, Version 6.3<br />

PROCESSING STOPPED ON 2006-01-27 AT 14:23:39<br />

ROLLOVER FILE DETECTED FOR USERID <br />

HEADER CODE= AAAAAAHEADER POVER<br />

HEADER DATE= 012006<br />

******************************** Bottom of Data ***************************<br />

Review File Detected<br />

********************************* Top of Data *****************************<br />

TRANSACTIONS RECEIVED ON 2006-01-27 AT 14.23.05<br />

HEADER CODE= AAAAAAHEADER SVIEW<br />

HEADER DATE= <br />

BATCH ID = <br />

USER ID = <br />

TRAN CNTS1 = nnnnnnnn T01 nnnnnnnn T51 nnnnnnnn T60 nnnnnnnn T61 nnnnnnnn<br />

TRAN CNTS2 = T71 nnnnnnnn T72 nnnnnnnn TXX nnnnnnnn T62 nnnnnnnn<br />

TRAN CNTS3 = T73 nnnnnnnn T74 nnnnnnnn T75 nnnnnnnn T85 nnnnnnnn<br />

TRAN CNTS4 = T63 nnnnnnnn<br />

PROCESSING STOPPED ON 2006-01-27 AT 14:23:39<br />

REVIEW FILE DETECTED FOR USERID <br />

HEADER CODE= AAAAAAHEADER SVIEW<br />

HEADER DATE= 012006<br />

******************************** Bottom of Data ***************************<br />

<strong>December</strong> <strong>28</strong>, 2012 J-35 Specialty Files


Plan Communications User Guide Appendices, Version 6.3<br />

J.14 Sample BEQ Request File Pass <strong>and</strong> Fail Acknowledgments<br />

Description<br />

The Enrollment Processing System issues an e-mail acknowledgment of receipt <strong>and</strong> status to the Sending Entity. If the status is accepted, the file is processed. If<br />

the status is rejected, the e-mail informs the Sending Entity of the first File Error Condition that caused the BEQ Request File’s rejection. A rejected file is not<br />

returned.<br />

Example<br />

Sample e-mail notifications showing a Pass Acknowledgement <strong>and</strong> a Fail Acknowledgement appear below:<br />

TO: Jim.Doe@xxs.net<br />

TO: Chris.Doe@dxxx.org<br />

TO: Falcon.Doe@xxxx.org<br />

TO: eevs.helpdesk@ngc.com<br />

FROM:<br />

Subject:<br />

MBD#BQ94.HCFJES@cms.hhs.gov<br />

CMS MMA DATA EXCHANGE FOR MMABTCH<br />

Example of BEQ Request File “Pass” Acknowledgment<br />

MMABTCH file has been received <strong>and</strong> passed surface edits by CMS.<br />

QUESTIONS? Contact 1-800-927-8069 or E-mail mapdhelp@cms.hhs.gov<br />

INPUT HEADER RECORD<br />

MMABEQRHS0094 20070306F20070306<br />

INPUT TRAILER RECORD<br />

MMABEQRTS0094 20070306F200703060000074<br />

<strong>December</strong> <strong>28</strong>, 2012 J-36 Sample BEQ Request File Pass <strong>and</strong> Fail Acknowledgments


Plan Communications User Guide Appendices, Version 6.3<br />

Example of BEQ Request File “Fail” Acknowledgment<br />

TO: Jim.Doe@xxs.net<br />

TO: Chris.Doe@dxxx.org<br />

TO: Falcon.Doe@xxxx.org<br />

TO: eevs.helpdesk@ngc.com<br />

FROM: MBD#BQ30.HCFJES@cms.hhs.gov<br />

Subject: CMS MMA DATA EXCHANGE FOR MMABTCH<br />

MMABTCH file has been received <strong>and</strong> failed surface edits by CMS.<br />

QUESTIONS? Contact 1-800-927-8069 or E-mail mapdhelp@cms.hhs.gov<br />

INPUT HEADER RECORD<br />

MMABEQRHH0030 200702<strong>28</strong> 84433346<br />

INPUT TRAILER RECORD<br />

MMABEQRTH0030 20070221 844333460074065<br />

THE TRAILER RECORD IS INVALID<br />

<strong>December</strong> <strong>28</strong>, 2012 J-37 Sample BEQ Request File Pass <strong>and</strong> Fail Acknowledgments


Plan Communications User Guide Appendices, Version 6.3<br />

K: All Transmissions Overview<br />

Table K-1: All Transmissions Overview<br />

ID# Transmittal<br />

Dataset naming conventions key:<br />

[GUID] = 7 character IACS User ID<br />

P = Production Data<br />

[.ZIP] = Appended if the file is compressed<br />

[directory] = optional directory specification<br />

from non-mainframe C:D clients (if present,<br />

may consist of up to 60 characters). If none<br />

exists, directory defaults to the constant<br />

“EFTO.” for Production files <strong>and</strong> "EFTT." for<br />

Test files.<br />

Plan Submittals to CMS<br />

1<br />

MARx Batch Input Transaction<br />

Data File<br />

Header Record<br />

Enrollment Transaction (Employer<br />

& Plan - 61 Detail Record<br />

Disenrollment Transaction (51/54)<br />

Detail Record<br />

Plan Elections (PBP Change)<br />

Transaction (71) Detail Record<br />

4Rx Data Update (72)<br />

NUNCMO Update (73)<br />

Other Enrollment record Update<br />

(74)<br />

Premium Withhold Option Update<br />

(75)<br />

Description<br />

pn = Processing number of varying length assigned to the<br />

file by Gentran<br />

ccccc = Contract number<br />

Pccccc = Plan Contract Number for C:D<br />

Uuuu-uuuuuuu = 4-7 character transmitter RACF ID<br />

xxxxx = 5 character Contract ID<br />

yyyymmdd = Calendar year, month & day<br />

yymmdd = two digit year, month, day<br />

zzzzzzzz = Plan-provided high level qualifier<br />

eeee = Year for which final yearly RAS file was produced<br />

vvvvv = Sequence counter for final yearly RAS files<br />

Enrollment Transaction<br />

file to CMS MARx<br />

system requesting new<br />

enrollment, disenrollment,<br />

changes, etc.<br />

Only the 1-800-<strong>Medicare</strong><br />

group submits a Part D<br />

Opt-Out (41) transaction.<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

MARx<br />

Data<br />

File<br />

Annnnn & Bnnnnn = MARx batch transaction ID,<br />

nnnnnnnnnn split into two nodes A…<strong>and</strong> B …with<br />

leading zeroes as necessary to complete tencharacter<br />

batch ID<br />

hhmm = hour <strong>and</strong> minute<br />

ssssss= Sequentially assigned number<br />

mmyyyy = Calendar month & year<br />

hlq = High Level Qualifier or Directory per VSAM File<br />

freq = Frequency code of file<br />

Batch -<br />

Daily<br />

PRN<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACFID].MARX.D.xxxx<br />

x.FUTURE.[P/T][.ZIP]<br />

Note: FUTURE is part of the<br />

filename <strong>and</strong> does not change.<br />

Connect:Direct:<br />

P#EFT.IN.uuuuuuu.MARXTR.DY<br />

YMMDD.THHMMSST<br />

Note: DYYMMDD.THHMMSST<br />

must be coded as shown, as it is a<br />

literal<br />

PCUG Record Layout – F.6<br />

2<br />

Batch Eligibility Query (BEQ)<br />

Request File<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

PCUG Record Layout – F.21<br />

File of transactions<br />

submitted by <strong>Plans</strong> to<br />

request eligibility<br />

information for<br />

prospective Plan<br />

enrollees.<br />

Used to do initial<br />

eligibility checks against<br />

CMS MBD system to<br />

verify member is Part<br />

A./B eligible<br />

MBD<br />

Data<br />

File<br />

PRN<br />

(<strong>Plans</strong> can<br />

send<br />

multiple<br />

files in a<br />

day)<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACFID].MBD.D.xxxxx.<br />

BEQ.[P/T][.ZIP]<br />

Connect:Direct:<br />

P#EFT.IN.PLxxxxx.BEQ4RX.DY<br />

YMMDD.THHMMSST<br />

Note: DYYMMDD.THHMMSST<br />

must be coded as shown, as it is a<br />

literal<br />

3<br />

Electronic Correspondence<br />

Referral System (ECRS) Batch<br />

Submittal File<br />

File used by <strong>Plans</strong> to<br />

submit other healthcare<br />

information (OHI) to<br />

CMS (rather than<br />

submittal through the<br />

ECRS online system)<br />

ECRS<br />

Data<br />

File<br />

Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACFID].ECRS.D.ccccc.<br />

FUTURE.[P/T] [.ZIP]<br />

Connect:Direct: TRANSMITTED<br />

TO GHI<br />

4 <strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

Submittal File<br />

File of transactions<br />

submitted by the <strong>Plans</strong><br />

with <strong>Prescription</strong> <strong>Drug</strong><br />

Events.<br />

PDE<br />

Data<br />

File<br />

Can be<br />

Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACFID].PDE.D.ccccc.F<br />

UTURE.[P/T] [.ZIP]<br />

Connect:Direct:<br />

TRANSMITTED TO PALMETTO<br />

<strong>December</strong> <strong>28</strong>, 2012 K-1 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Plan Submittals to CMS<br />

Description<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

5<br />

MARx Batch Input Transaction<br />

Data File<br />

Header Record<br />

Enrollment Transaction (Employer<br />

& Plan - 61 Detail Record<br />

Disenrollment Transaction (51/54)<br />

Detail Record<br />

Plan Elections (PBP Change)<br />

Transaction (71) Detail Record<br />

4Rx Data Update (72)<br />

NUNCMO Update (73)<br />

Other Enrollment record Update<br />

(74)<br />

Premium Withhold Option Update<br />

(75)<br />

Enrollment Transaction<br />

file to CMS MARx<br />

system requesting new<br />

enrollment, disenrollment,<br />

changes, etc.<br />

Only the 1-800-<strong>Medicare</strong><br />

group submits a Part D<br />

Opt-Out (41) transaction.<br />

MARx<br />

Data<br />

File<br />

Batch -<br />

Daily<br />

PRN<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server: **<br />

[GUID].[RACFID].MARX.D.xxxx<br />

x.FUTURE.[P/T][.ZIP]<br />

Note: FUTURE is part of the<br />

filename <strong>and</strong> does not change.<br />

Connect:Direct:<br />

P#EFT.IN.uuuuuuu.MARXTR.DY<br />

YMMDD.THHMMSST<br />

Note: DYYMMDD.THHMMSST<br />

must be coded as shown, as it is a<br />

literal<br />

PCUG Record Layout – F.6<br />

6<br />

Batch Eligibility Query (BEQ)<br />

Request File<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

PCUG Record Layout – F.21<br />

File of transactions<br />

submitted by <strong>Plans</strong> to<br />

request eligibility<br />

information for<br />

prospective Plan<br />

enrollees.<br />

Used to do initial<br />

eligibility checks against<br />

CMS MBD system to<br />

verify member is Part<br />

A./B eligible<br />

MBD<br />

Data<br />

File<br />

PRN<br />

(<strong>Plans</strong> can<br />

send<br />

multiple<br />

files in a<br />

day)<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server: **<br />

[GUID].[RACFID].MBD.D.xxxxx.<br />

BEQ.[P/T][.ZIP]<br />

Connect:Direct:<br />

P#EFT.IN.PLxxxxx.BEQ4RX.DY<br />

YMMDD.THHMMSST<br />

Note: DYYMMDD.THHMMSST<br />

must be coded as shown, as it is a<br />

literal<br />

7<br />

Electronic Correspondence<br />

Referral System (ECRS) Batch<br />

Submittal File<br />

File used by <strong>Plans</strong> to<br />

submit other healthcare<br />

information (OHI) to<br />

CMS (rather than<br />

submittal through the<br />

ECRS online system)<br />

ECRS<br />

Data<br />

File<br />

Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACFID].ECRS.D.ccccc.<br />

FUTURE.[P/T] [.ZIP]<br />

Connect:Direct: TRANSMITTED<br />

TO GHI<br />

8 <strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

Submittal File<br />

File of transactions<br />

submitted by the <strong>Plans</strong><br />

with <strong>Prescription</strong> <strong>Drug</strong><br />

Events.<br />

PDE<br />

Data<br />

File<br />

Can be<br />

Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACFID].PDE.D.ccccc.F<br />

UTURE.[P/T] [.ZIP]<br />

Connect:Direct:<br />

TRANSMITTED TO PALMETTO<br />

9 RAPS Submittal File<br />

File of transactions<br />

submitted by the <strong>Plans</strong><br />

with diagnoses for FFS<br />

Beneficiaries<br />

RAPS<br />

Data<br />

File<br />

Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACFID].RAPS.D.ccccc.<br />

FUTURE.[P/T] [.ZIP]<br />

Connect:Direct:<br />

TRANSMITTED TO PALMETTO<br />

10<br />

Electronic Data Services (EDS)<br />

Submittal File<br />

File of transactions<br />

submitted by the <strong>Plans</strong><br />

with EDS.<br />

EDS<br />

Data<br />

File<br />

Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

[GUID].[RACF].EDS.D.xxxxx.FU<br />

TURE.[P/T][.ZIP]<br />

Connect:Direct:<br />

TRANSMITTED TO PALMETTO<br />

<strong>December</strong> <strong>28</strong>, 2012 K-2 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

CMS Transmittals to the Users<br />

(Submitters)<br />

Description<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

11<br />

Failed Transaction Data File<br />

Header Record<br />

Failed Record<br />

This report is no longer<br />

generated as a result of<br />

the November 2009<br />

software release. Failed<br />

Records are now reported<br />

on the BCSS data file.<br />

MARx<br />

Data File Response to<br />

transaction<br />

batch file<br />

Obsolete<br />

12<br />

Batch Completion Status<br />

Summary Data File<br />

Summary Record<br />

Failed Records<br />

PCUG Record Layout – F.2<br />

Data file sent to the<br />

submitter once a batch of<br />

submitted transactions has<br />

been processed. Provides a<br />

count of all transactions<br />

within the batch <strong>and</strong><br />

details the number of<br />

rejected <strong>and</strong> accepted<br />

transactions. It provides an<br />

image of the rejected <strong>and</strong><br />

accepted transactions.<br />

MARx<br />

Data File Once batch<br />

is processed<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.uuuuuuu.BCSSD.Annnnn.Bnnnnn.<br />

Thhmmss.pn<br />

Connect:Direct [Mainframe]:<br />

zzzzzzzz.uuuuuuu.BCSSD.Annnnn.B<br />

nnnnn.Thhmmss<br />

Connect:Direct [Non-mainframe]:<br />

[directory]uuuuuuu.BCSSD.Annnnn.<br />

Bnnnnn.Thhmmss<br />

13<br />

Enrollment Transmission<br />

Message File (STATUS)<br />

This message is no longer<br />

generated as a result of the<br />

April 2011 software<br />

release. This information<br />

is now incorporated into<br />

the Batch Completion<br />

Status Summary (BCSS)<br />

data file.<br />

MARx<br />

Report Response to<br />

transaction<br />

batch file<br />

Obsolete<br />

CMS Transmittals to the <strong>Plans</strong><br />

14<br />

Coordination of Benefits<br />

(Validated Other Insurer<br />

Information) Data File<br />

Detail Record<br />

Primary Record<br />

Supplemental Record<br />

PCUG Record Layout – F.5<br />

File containing members'<br />

primary <strong>and</strong> secondary<br />

coverage that has been<br />

validated through COB<br />

processing. MARx<br />

forwards this report<br />

whenever a Plan's<br />

enrollees are affected. It<br />

may be as often as<br />

daily.The enrollees<br />

included on the report are<br />

those newly enrolled who<br />

have known Other Health<br />

Insurance (OHI) <strong>and</strong> those<br />

Plan enrollees with<br />

changes to their OHI.<br />

MBD<br />

(MARx)<br />

Data File<br />

As Needed<br />

(can be<br />

daily)<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.MARXCOB.Dyymmdd.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.MARXCOB.Dyym<br />

mdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.MARXCOB.Dyy<br />

mmdd.Thhmmsst<br />

15<br />

MA Full Dual Auto Assignment<br />

Notification File<br />

Header Record<br />

Detail Record (Transaction)<br />

Trailer Record<br />

PCUG Record Layout – F.23<br />

Monthly file of Full Dual<br />

Beneficiaries in an<br />

existing Plan.<br />

MBD<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.#ADUA4.Dyymmdd.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.#ADUA4.Dyymmd<br />

d.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.#ADUA4.Dyymm<br />

dd.Thhmmsst<br />

ID# Transmittal Description Responsible Type Freq. Dataset Naming Conventions<br />

<strong>December</strong> <strong>28</strong>, 2012 K-3 All Transmissions Overview


CMS Transmittals to the <strong>Plans</strong><br />

Plan Communications User Guide Appendices, Version 6.3<br />

System<br />

16<br />

Auto Assignment (PDP) Address<br />

Notification File<br />

Header Record<br />

Detail Record(s)<br />

Trailer Record<br />

PCUG Record Layout – F.24<br />

Monthly file of addresses<br />

of Beneficiaries who have<br />

been either Auto Assigned<br />

or Facilitated Assigned to<br />

PDPs<br />

MBD<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.#APDP4.Dyymmdd.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.#APDP4.Dyymmd<br />

d.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.#APDP4.Dyymm<br />

dd.Thhmmsst<br />

17<br />

NoRx File<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

PCUG Record Layout – F.20<br />

File containing records<br />

identifying those enrollees<br />

that do not currently have<br />

4Rx information stored in<br />

CMS files. A Detail<br />

Record Type containing a<br />

value of “NRX” in<br />

positions 1 – 3 of the file<br />

layout will indicate that<br />

this record is a request for<br />

your organization to send<br />

CMS 4Rx information for<br />

the beneficiary.<br />

MBD<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.#NORX.Dyymmdd.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.#NORX.Dyymmdd<br />

.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.#NORX.Dyymmd<br />

d.Thhmmsst<br />

18<br />

19<br />

Batch Eligibility Query (BEQ)<br />

Request File Acknowledgment<br />

(Accept/Reject)<br />

PCUG Sample Report – J.14<br />

Batch Eligibility Query (BEQ)<br />

Response File<br />

Header Record<br />

Detail Record (Transaction)<br />

Trailer Record<br />

PCUG Record Layout – F.22<br />

MBD will determine if a<br />

BEQ Request File is<br />

Accepted or Rejected.<br />

MBD will issue an e-mail<br />

acknowledgment of<br />

receipt <strong>and</strong> status to the<br />

Sending Entity. If<br />

Accepted the file will be<br />

processed. If Rejected, the<br />

e-mail shall inform the<br />

Sending Entity of the first<br />

File Error Condition that<br />

caused the BEQ Request<br />

File to be Rejected. A<br />

rejected file will not be<br />

returned.<br />

File containing records<br />

produced as a result of<br />

processing the<br />

transactions of accepted<br />

BEQ Request files. Detail<br />

records for all submitted<br />

records that were<br />

successfully processed<br />

will contain Processed<br />

Flag = Y. Detail records<br />

for all submitted records<br />

that were not successfully<br />

processed contain<br />

Processed Flag = N.<br />

MBD E-mail Response<br />

to BEQ<br />

MBD<br />

Data File Response<br />

to BEQ<br />

N/A<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.#BQN4.Dyymmdd.Thhm<br />

msst.pn<br />

Connect:Direct [Mainframe]:<br />

zzzzzzzz.Rxxxxx.#BQN4.Dyymmdd.<br />

Thhmmsst<br />

Connect:Direct [Non-mainframe]:<br />

[directory]Rxxxxx.#BQN4.Dyymmd<br />

d.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-4 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

CMS Transmittals to the <strong>Plans</strong><br />

Description<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

20 ECRS Data File<br />

File containing errors <strong>and</strong><br />

statuses of ECRS<br />

submissions.<br />

ECRS Data File Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

PCOB.BA.ECRS.ccccc.RESPONSE.<br />

ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM GHI<br />

21<br />

<strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

PDFS Response Data File<br />

File containing responses<br />

if files are accepted or<br />

rejected.<br />

PDE Data File Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RSP.PDFS_RESP_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

22<br />

23<br />

<strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

<strong>Drug</strong> Data Processing System<br />

(DDPS Return Data File<br />

<strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

DDPS Transaction Error<br />

Summary Data File<br />

File provides feedback on<br />

every record processed in<br />

a batch. Up to 10 specific<br />

errors are reported for<br />

each PDE in the file.<br />

File provides frequency of<br />

occurrence for each error<br />

code encountered during<br />

the processing of a PDE<br />

file. The percentage to the<br />

total errors is also<br />

computed <strong>and</strong> displayed<br />

for each error code.<br />

PDE Data File Daily<br />

PDE Data File Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.DDPS_TRANS_VALIDATION<br />

_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.DDPS_ERROR_SUMMARY_s<br />

sssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

24<br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports<br />

Report indicates that the<br />

file was accepted or<br />

rejected by the Front-End<br />

Risk Adjustment System.<br />

FERAS Report Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RSP.FERAS_RESP_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

25<br />

Front-End Risk Adjustment<br />

System<br />

(FERAS) Response Data Files<br />

File contains all of the<br />

submitted transactions<br />

whether or not the file<br />

contains errors.<br />

FERAS Data File Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.RAPS_RETURN_FLAT_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

26<br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports Transaction Error<br />

Report<br />

Report lists the<br />

transactions that<br />

contained errors <strong>and</strong><br />

identifies the errors<br />

found.<br />

FERAS Report Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.RAPS_ERRORRPT_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

<strong>December</strong> <strong>28</strong>, 2012 K-5 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

CMS Transmittals to the <strong>Plans</strong><br />

Description<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

27<br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports Transaction Summary<br />

Report<br />

Report contains all of<br />

the transactions<br />

submitted, whether<br />

accepted or rejected.<br />

FERAS Report Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.RAPS_SUMMARY_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

<strong>28</strong><br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports Duplicate Diagnosis<br />

Cluster Report<br />

Report identifies<br />

diagnosis clusters with<br />

502 error message,<br />

clusters accepted, but not<br />

stored.<br />

FERAS Report Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.RAPS_DUPDX_RPT_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

29<br />

Transaction Reply Daily<br />

Activity Data File<br />

PCUG Record Layout – F.14<br />

Data file version of the<br />

Transaction Reply Daily<br />

Activity Report. MARx Data File Daily<br />

P.Rxxxxx.DTRRD.Dyymmdd.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.DTRRD.Dyymmdd<br />

.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.DTRRD.Dyymmd<br />

d.Thhmmsst<br />

30<br />

Electronic Data Services (EDS)<br />

Response Data File<br />

File containing responses<br />

if files are accepted or<br />

rejected.<br />

EDS Data File Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.xxxxx.EDS_RESPONSE.pn<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

31<br />

Electronic Data Services (EDS)<br />

Reject IC ISAIEA Data File<br />

File containing responses<br />

if files are accepted or<br />

rejected.<br />

EDS Data File Daily<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.xxxxx.EDS_REJT_IC_ISAIEA.pn<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

32<br />

Electronic Data Services (EDS)<br />

Reject Function Transaction<br />

Data File<br />

File containing responses<br />

if files are accepted or<br />

rejected.<br />

EDS Data File Daily<br />

P.xxxxx.EDS_REJT_FUNCT_TRAN<br />

S.pn<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

33<br />

Electronic Data Services (EDS)<br />

Accept Function Transaction<br />

Data File<br />

File containing responses<br />

if files are accepted or<br />

rejected.<br />

EDS Data File Daily<br />

P.xxxxx.EDS_ACCPT_FUNCT_TR<br />

ANS.pn<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

ID# Transmittal Description Responsible Type Freq. Dataset Naming Conventions<br />

<strong>December</strong> <strong>28</strong>, 2012 K-6 All Transmissions Overview


CMS Transmittals to the <strong>Plans</strong><br />

Plan Communications User Guide Appendices, Version 6.3<br />

System<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

34<br />

Electronic Data Services (EDS)<br />

Response Claim Number Data<br />

File<br />

File containing responses<br />

if files are accepted or<br />

rejected.<br />

EDS Data File Daily<br />

P.xxxxx.EDS_RESP_CLAIM_NUM.<br />

pn<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Weekly Transmittals (Data & Reports)<br />

35<br />

LIS/Part D Premium Data File<br />

PCUG Record Layout – F.18<br />

The data in the report<br />

reflects LIS info, premium<br />

subsidy levels, Low-income<br />

co-pay levels, etc. for all<br />

Beneficiaries who have a<br />

low-income designation<br />

enrolled in a Plan.<br />

This data file is produced<br />

bi-weekly. It is not<br />

automatically transmitted to<br />

the <strong>Plans</strong>. Through the<br />

MARx UI plans can request<br />

or reorder this data file.<br />

MARx<br />

Data File Biweekly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.LISPRMD.Dyymmdd.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.LISPRMD.Dyymm<br />

dd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.LISPRMD.Dyym<br />

mdd.Thhmmsst<br />

Monthly Transmittals (Data &<br />

Reports)<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

36<br />

Part C Monthly Membership<br />

Detail Report (Non <strong>Drug</strong><br />

Report)<br />

aka: Monthly Membership Report<br />

(MMR)<br />

PCUG Sample Report – J.5<br />

Report listing every Part<br />

C <strong>Medicare</strong> member of<br />

the contract <strong>and</strong> providing<br />

details about the payments<br />

<strong>and</strong> adjustments made for<br />

each.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

MARx Report Monthly<br />

P.Fxxxxx.MONMEMR.Dyymm01.T<br />

hhmmsst.pn<br />

P.Rxxxxx.MONMEMR.Dyymm01.T<br />

hhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Fxxxxx.MONMEMR.Dyy<br />

mm01.Thhmmsst<br />

zzzzzzzz.Rxxxxx.MONMEMR.Dyy<br />

mm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Fxxxxx.MONMEMR.Dyy<br />

mm01.Thhmmsst<br />

zzzzzzzz.Rxxxxx.MONMEMR.Dyy<br />

mm01.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-7 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

Description<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

37<br />

Part D Monthly Membership<br />

Detail Report (<strong>Drug</strong> Report)<br />

aka: Monthly Membership Report<br />

(MMR)<br />

PCUG Sample Report – J.4<br />

Report listing every Part<br />

D <strong>Medicare</strong> member of<br />

the contract <strong>and</strong> provides<br />

details about the payments<br />

<strong>and</strong> adjustments made for<br />

each.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

MARx Report Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Fxxxxx.MONMEMDR.Dyymm01.<br />

Thhmmsst.pn<br />

P.Rxxxxx.MONMEMDR.Dyymm01.<br />

Thhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Fxxxxx.MONMEMDR.Dyy<br />

mm01.Thhmmsst<br />

zzzzzzzz.Rxxxxx.MONMEMDR.Dy<br />

ymm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Fxxxxx.MONMEDR.Dyy<br />

mm01.Thhmmsst<br />

[directory]Rxxxxx.MONMEDR.Dyy<br />

mm01.Thhmmsst<br />

38<br />

Monthly Membership Detail<br />

Data File<br />

PCUG Record Layout – F.8<br />

Data file version of the<br />

Monthly Membership<br />

Detail Reports. This file<br />

contains the data for both<br />

Part C <strong>and</strong> Part D<br />

members.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

MARx<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Fxxxxx.MONMEMD.Dyymm01.T<br />

hhmmsst.pn<br />

P.Rxxxxx.MONMEMD.Dyymm01.T<br />

hhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Fxxxxx.MONMEMD.Dyy<br />

mm01.Thhmmsst<br />

zzzzzzzz.Rxxxxx.MONMEMD.Dyy<br />

mm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Fxxxxx.MONMEMD.Dyy<br />

mm01.Thhmmsst<br />

[directory]Rxxxxx.MONMEMD.Dyy<br />

mm01.Thhmmsst<br />

39<br />

Monthly Membership Summary<br />

Report<br />

PCUG Sample Report – J.6<br />

Report summarizing<br />

payments to a Plan for the<br />

month, in several<br />

categories, <strong>and</strong><br />

adjustments, by all<br />

adjustment categories.<br />

This report contains data<br />

for both Part C <strong>and</strong> Part D<br />

members.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

MARx Report Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Fxxxxx.MONMEMSR.Dyymm01.<br />

Thhmmsst.pn<br />

P.Rxxxxx.MONMEMSR.Dyymm01.<br />

Thhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Fxxxxx.MONMEMSR.Dyy<br />

mm01.Thhmmsst<br />

zzzzzzzz.Rxxxxx.MONMEMSR.Dyy<br />

mm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Fxxxxx.MONMEMSR.Dy<br />

ymm01.Thhmmsst<br />

[directory]Rxxxxx.MONMEMSR.Dy<br />

ymm01.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-8 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

40<br />

41<br />

42<br />

43<br />

Monthly Membership Summary<br />

Data File<br />

PCUG Record Layout – F.9<br />

RAS RxHCC Model Output<br />

Report<br />

AKA: Part D Risk Adjustment<br />

Model Output Report<br />

PCUG Sample Report – J.9<br />

RAS RxHCC Model Output Data<br />

File<br />

AKA: Part D Risk Adjustment<br />

Model Output Data File<br />

Header Record<br />

Detail / Beneficiary Record Format<br />

Trailer Record<br />

PCUG Record Layout – F.13<br />

Part C Risk Adjustment Model<br />

Output Report<br />

PCUG Sample Report – J.8<br />

Description<br />

Data file version of the<br />

Monthly Membership<br />

Summary Report for both<br />

Part C <strong>and</strong> Part D members.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Report showing the Part D<br />

risk adjustment factors for<br />

each beneficiary. MARx<br />

forwards this report that is<br />

produced by RAS to plans<br />

as part of the month-end<br />

processing.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Data file version of the<br />

RAS RxHCC Model Output<br />

Report. MARx forwards<br />

this report that is produced<br />

by RAS to <strong>Plans</strong> as part of<br />

the month-end processing.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Report showing the<br />

Hierarchical Condition<br />

Codes (HCCs) used by the<br />

Risk Adjustment System<br />

(RAS) to calculate Part C<br />

risk adjustment factors for<br />

each beneficiary. MARx<br />

forwards this report that is<br />

produced by RAS to plans<br />

as part of the month-end<br />

processing.<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

MARx<br />

RAS<br />

(MARx)<br />

RAS<br />

(MARx)<br />

RAS<br />

(MARx)<br />

Data File Monthly<br />

Report<br />

(.pdf)<br />

Monthly<br />

Data File Monthly<br />

Report<br />

Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Fxxxxx.MONMEMSD.Dyymm01.<br />

Thhmmsst.pn<br />

P.Rxxxxx.MONMEMSD.Dyymm01.<br />

Thhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Fxxxxx.MONMEMSD.Dyy<br />

mm01.Thhmmsst<br />

zzzzzzzz.Rxxxxx.MONMEMSD.Dyy<br />

mm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Fxxxxx.MONMEMSD.Dy<br />

ymm01.Thhmmsst<br />

[directory]Rxxxxx.MONMEMSD.Dy<br />

ymm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.PTDMODR.Dyymm01.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PTDMODR.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.PTDMODR.Dyy<br />

mm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.PTDMODD.Dyymm01.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PTDMODD.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.PTDMODD.Dyy<br />

mm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.HCCMODR.Dyymm01.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.HCCMODR.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.HCCMODR.Dyy<br />

mm01.Thhmmsst<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

<strong>December</strong> <strong>28</strong>, 2012 K-9 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

44<br />

45<br />

46<br />

Part C Risk Adjustment Model<br />

Output Data File<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

PCUG Record Layout – F.12<br />

BIPA 606 Payment Reduction<br />

Report<br />

PCUG Sample Report – J.1<br />

BIPA 606 Payment Reduction<br />

Data File<br />

PCUG Record Layout – F.3<br />

Description<br />

Data file version of the Risk<br />

Adjustment Model Output<br />

Report<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Report listing members for<br />

whom the plan is paying a<br />

portion of the Part B<br />

premium. Generated only if<br />

there are pre-2006<br />

adjustments that involve<br />

BIPA 606 premium<br />

reductions.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Data file version of the<br />

BIPA 606 Reduction<br />

Report.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

RAS<br />

(MARx)<br />

MARx<br />

MARx<br />

Data File Monthly<br />

Report<br />

Data File<br />

Monthly,<br />

if<br />

applicable<br />

Monthly,<br />

if<br />

applicable<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.HCCMODD.Dyymm01.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.HCCMODD.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.HCCMODD.Dyy<br />

mm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.BIPA606R.Dyymm01.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.BIPA606R.Dyymm<br />

01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.BIPA606R.Dyym<br />

m01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.BIPA606D.Dyymm01.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.BIPA606D.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.BIPA606D.Dyym<br />

m01.Thhmmsst<br />

47<br />

Bonus Payment Report<br />

PCUG Sample Report – J.2<br />

Report listing members for<br />

whom the plan is to be paid<br />

a bonus. (<strong>Plans</strong> are paid a<br />

bonus for extending<br />

services to Beneficiaries in<br />

some underserved areas.)<br />

Generated only if there are<br />

pre-2006 adjustments that<br />

involve bonus payments.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

MARx<br />

Report<br />

Monthly,<br />

if<br />

applicable<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.BONUSRPT.Dyymm01.T<br />

hhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.BONUSRPT.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.BONUSRPT.Dyy<br />

mm01.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-10 All Transmissions Overview


ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

48<br />

49<br />

Bonus Payment Data File<br />

PCUG Record Layout – F.4<br />

Monthly Summary of Bills Report<br />

PCUG Sample Report – J.7<br />

50 HMO Bill Itemization Report<br />

PCUG Sample Report – J.3<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Description<br />

Data file version of the<br />

Bonus Payment Report<br />

Note:<br />

The date in the file name<br />

will default to The date in<br />

the file name defaults to<br />

“01” denoting the first day<br />

of the current payment<br />

month<br />

Report summarizing all<br />

<strong>Medicare</strong> fee-for-service<br />

activity, both Part A <strong>and</strong><br />

Part B, for Beneficiaries<br />

enrolled in the contract<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Report listing the Part A<br />

bills that were processed<br />

under <strong>Medicare</strong> fee-forservice<br />

for Beneficiaries<br />

enrolled in the contract.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

MARx<br />

Data File<br />

Monthly,<br />

if<br />

applicable<br />

MARx Report Monthly<br />

MARx Report Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.BONUSDAT.Dyymm01.T<br />

hhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.BONUSDAT.Dyy<br />

mm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.BONUSDAT.Dyy<br />

mm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.SUMBILLS.Dyymm01.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.SUMBILLS.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.SUMBILLS.Dyy<br />

mm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.BILLITEM.Dyymm01.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.BILLITEM.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.BILLITEM.Dyym<br />

m01.Thhmmsst<br />

51<br />

Part B Claims Data File<br />

Record Type 1<br />

Record Type 2<br />

PCUG Record Layout – F.11<br />

52 Payment Records Report<br />

PCUG Sample Report – J.10<br />

Data file listing the Part B<br />

physician <strong>and</strong> supplier<br />

claims <strong>and</strong> Part B home<br />

health claims that were<br />

processed under <strong>Medicare</strong><br />

fee-for-service for<br />

Beneficiaries enrolled in the<br />

contract.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Report listing the Part B<br />

physician <strong>and</strong> supplier<br />

claims that were processed<br />

under <strong>Medicare</strong> fee-forservice<br />

for Beneficiaries<br />

enrolled in the contract.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

MARx<br />

Data File Monthly<br />

MARx Report Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.CLAIMDAT.Dyymm01.T<br />

hhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.CLAIMDAT.Dyy<br />

mm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.CLAIMDAT.Dyy<br />

mm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.PAYRECDS.Dyymm01.T<br />

hhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PAYRECDS.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.PAYRECDS.Dyy<br />

mm01.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-11 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

53<br />

54<br />

55<br />

56<br />

Monthly Premium Withholding<br />

Report Data File (MPWR)<br />

Header Record<br />

Detail Record<br />

Trailer - T1 - Total at segment<br />

level<br />

Trailer - T2 - Total at PBP level<br />

Trailer - T3 - Total at contract<br />

level<br />

PCUG Record Layout – F.10<br />

Failed Payment Reply Report<br />

Detail Record<br />

PCUG Record Layout – F.31<br />

Plan Payment Report (APPS<br />

Payment Letter)<br />

PCUG Sample Report – J.11<br />

Plan Payment Report (APPS<br />

Payment Letter) Data File<br />

PCUG Record Layout – F.25<br />

Description<br />

Monthly reconciliation file<br />

of premiums withheld from<br />

SSA, RRB, or OPM checks.<br />

Includes Part C <strong>and</strong> Part D<br />

premiums <strong>and</strong> any Part D<br />

Late Enrollment Penalties.<br />

This file is produced by the<br />

Premium Withhold System<br />

(PWS). MARx makes this<br />

report available to plans as<br />

part of the month-end<br />

processing.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Data file reporting payment<br />

actions which failed to<br />

complete.<br />

Report itemizing the final<br />

monthly payment to the<br />

plan. This report is<br />

produced by the APPS<br />

when final payments are<br />

calculated. MARx makes<br />

this report available to plans<br />

as part of the month-end<br />

processing.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

This data file itemizes the<br />

final monthly payment to<br />

the MCO. This data file <strong>and</strong><br />

subsequent report is<br />

produced by the APPS<br />

when final payments are<br />

calculated. CMS makes this<br />

report available to MCO’s<br />

as part of month-end<br />

processing.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

PWS<br />

(MARx)<br />

MARx<br />

Data File Monthly<br />

Data File<br />

Monthly<br />

Payment<br />

Cycle<br />

APPS Report Monthly<br />

APPS<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.MPWRD.Dyymm01.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.MPWRD.Dyymm0<br />

1.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.MPWRD.Dyymm<br />

01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.FPRRD.Dyymm01.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx<br />

FPRRD.Dyymm01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.<br />

FPRRD.Dyymm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Fxxxxx.PLANPAY.Dyymm01.Thh<br />

mmsst.pn<br />

P.Rxxxxx.PLANPAY.Dyymm01.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Fxxxxx.PLANPAY.Dyym<br />

m01.Thhmmsst<br />

zzzzzzzz.Rxxxxx.PLANPAY.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Fxxxxx.PLANPAY.Dyym<br />

m01.Thhmmsst<br />

[directory]Rxxxxx.PLANPAY.Dyym<br />

m01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.PPRD.Dyymm01.Thhmms<br />

st.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PPRD.Dyymm01.T<br />

hhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory].Rxxxxx.PPRD.Dyymm01.<br />

Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-12 All Transmissions Overview


ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

57<br />

58<br />

59<br />

60<br />

61<br />

Interim APPS Plan Payment<br />

Report<br />

PCUG Sample Report – J.12<br />

Interim APPS Plan Payment<br />

Report Data File<br />

PCUG Sample Layout – F.25<br />

820 Format Payment Advice Data<br />

File<br />

PCUG Record Layout – F.1<br />

Monthly Full Enrollment Data<br />

File<br />

PCUG Record Layout – F.15<br />

<strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

DBC Cumulative Beneficiary<br />

Summary Report<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Description<br />

When a Plan is approved<br />

for an interim payment<br />

outside of the normal<br />

monthly process, an interim<br />

Plan Payment Report is<br />

distributed to that Plan. The<br />

report contains the amount<br />

<strong>and</strong> reason for the interim<br />

payment. <strong>Plans</strong> can also<br />

request these reports via the<br />

MARx user interface under<br />

the weekly report section of<br />

the menu.<br />

The Interim APPS Plan<br />

Payment Data File <strong>and</strong><br />

Report is provided when a<br />

Plan is approved for an<br />

interim payment outside of<br />

the normal monthly<br />

process. The data file /<br />

report contains the amount<br />

<strong>and</strong> reason for the interim<br />

payment to the Plan.<br />

HIPAA-Compliant version<br />

of the Plan Payment Report.<br />

This data file itemizes the<br />

final monthly payment to the<br />

plan. This data file is not<br />

available through MARx.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the CCM<br />

File includes all active Plan<br />

membership on the date the<br />

file is run. This file is<br />

considered a definitive<br />

statement of current plan<br />

enrollment. This file uses<br />

the same format as the<br />

weekly TRR. The file is<br />

distributed on or about the<br />

first of the month.<br />

File includes summary for<br />

the beneficiary of<br />

accumulated overall totals<br />

in PDE amount fields with<br />

accumulated totals for<br />

covered drugs.<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

APPS Report As needed<br />

APPS<br />

APPS<br />

MARx<br />

PDE<br />

Data File As needed<br />

Data File Monthly<br />

Data File Monthly<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.PLNPAYI.Dyymm01.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PLNPAYI.Dyymm<br />

01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.PLNPAYI.Dyym<br />

m01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.PPRID.Dyymmdd.Thhmm<br />

sst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PPRID.Dyymmdd.<br />

Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory].Rxxxxx.PPRID.Dyymmd<br />

d.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.PLAN820D.Dyymm01.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PLAN820D.Dyym<br />

m01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.PLAN820D.Dyy<br />

mm01.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.FEFD.Dyymm01.Thhmms<br />

st.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.FEFD.Dyymm01.T<br />

hhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.FEFD.Dyymm01.<br />

Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.DDPS.CUM_BENE_ACT_CO<br />

V_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

<strong>December</strong> <strong>28</strong>, 2012 K-13 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

62<br />

63<br />

64<br />

65<br />

66<br />

<strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

DBC Cumulative Beneficiary<br />

Summary Report<br />

<strong>Prescription</strong> <strong>Drug</strong> Event (PDE)<br />

DBC Cumulative Beneficiary<br />

Summary Report<br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports<br />

Monthly Plan Activity Report<br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports<br />

Cumulative Plan Activity Report<br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports<br />

Frequency Report Monthly<br />

Report<br />

Description<br />

File includes summary for<br />

the beneficiary of<br />

accumulated overall totals<br />

in PDE amount fields with<br />

accumulated totals for<br />

enhanced drugs.<br />

File includes summary for<br />

the beneficiary of<br />

accumulated overall totals<br />

in PDE amount fields with<br />

accumulated totals for overthe-counter<br />

drugs.<br />

Report provides monthly<br />

summary of the status of<br />

submissions by submitter<br />

<strong>and</strong> plan number.<br />

Report provides cumulative<br />

summary of the status of<br />

submissions by Submitter<br />

ID <strong>and</strong> plan number.<br />

Report provides monthly<br />

summary of all errors on all<br />

file submissions within the<br />

month.<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

PDE<br />

PDE<br />

Data File Monthly<br />

Data File Monthly<br />

FERAS Report Monthly<br />

FERAS Report Monthly<br />

FERAS Report Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.DDPS_CUM_BENE_ACT_EN<br />

H_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.DDPS_CUM_BENE_ACT_OT<br />

C_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.RAPS_MONTHLY_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RPT.RAPS_CUMULATIVE_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RAPS_ERRORFREQ_MNTH_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

67<br />

LIS/LEP Data File<br />

Header Record<br />

Detail Record<br />

Trailer Record<br />

PCUG Record Layout – F.16<br />

This report provides<br />

information on low-income<br />

subsidized Beneficiaries<br />

<strong>and</strong> on direct-billed<br />

Beneficiaries with late<br />

enrollment penalties.<br />

Note:<br />

The date in the file name<br />

defaults to “01” denoting<br />

the first day of the current<br />

payment month.<br />

MARx<br />

Data File Monthly<br />

P.Fxxxxx.LISLEPD.Dyymm01.Thh<br />

mmsst.pn<br />

P.Rxxxxx.LISLEPD.Dyymm01.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Fxxxxx.LISLEPD.Dyymm0<br />

1.Thhmmsst<br />

zzzzzzzz.Rxxxxx.LISLEPD.Dyymm<br />

01.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Fxxxxx.LISLEPD.Dyymm<br />

01.Thhmmsst<br />

[directory]Rxxxxx.LISLEPD.Dyymm<br />

01.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-14 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Monthly Transmittals (Data &<br />

Reports)<br />

68<br />

LIS History Data File (LISHIST)<br />

PCUG Record Layout – F.19<br />

Description<br />

This file supplements<br />

existing files that provide<br />

LIS notifications. It<br />

provides a complete picture<br />

of a beneficiary’s LIS<br />

eligibility over a period of<br />

time not to exceed 36<br />

months.<br />

Note:<br />

The date in the file name<br />

defaults to “dd” denoting<br />

the day of the calendar<br />

month<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

MARx<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.LISHIST.Dyymmdd.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.LISHIST.Dyymmd<br />

d.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.LISHIST.Dyymm<br />

dd.Thhmmsst<br />

69<br />

Agent Broker Compensation Data<br />

File<br />

PCUG Record Layout – F.27<br />

This data file provides sixyear<br />

broker compensation<br />

cycle-year counts. Data is<br />

sent to <strong>Plans</strong> 1) when a<br />

beneficiary enrolls, 2) each<br />

January when the cycleyear<br />

count increments <strong>and</strong><br />

3) as necessary when<br />

retroactive change affects<br />

the compensation cycle.<br />

<strong>Plans</strong> may re-order the 6-<br />

year Broker Compensation<br />

Report Data File” via the<br />

UI.<br />

MARx<br />

Data File<br />

Monthly,<br />

generally<br />

with the<br />

first weekly<br />

TRR of the<br />

month<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rnnnnn.COMPRPT.Dyymmdd.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rnnnnn.COMPRPT.Dyym<br />

mdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rnnnnn.COMPRPT.Dyym<br />

mdd.Thhmmsst<br />

70<br />

Monthly MSP Information Data<br />

File<br />

PCUG Record Layout – F.<strong>28</strong><br />

This data file is sent<br />

directly to <strong>Plans</strong> on the first<br />

Monday after the MARx<br />

month-end processing<br />

completes. This file<br />

contains a subset of<br />

information to allow <strong>Plans</strong><br />

to reconcile payment; the<br />

full monthly MSP COB file<br />

distributed at the beginning<br />

of each month contains<br />

more detail.<br />

MDB<br />

Data File Monthly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.MSPCOBAD.Dyymmdd.T<br />

hhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.MSPCOBAD.Dyy<br />

mmdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory].Rxxxxx.MSPCOBAD.Dy<br />

ymmdd.Thhmmsst<br />

71<br />

Other Health Coverage<br />

Information Data File<br />

PCUG Record Layout – F.29<br />

CMS provides <strong>Plans</strong> with a<br />

file listing the Beneficiaries<br />

who are enrolled in their<br />

plan(s) where <strong>Medicare</strong> is<br />

listed secondary. As a<br />

monthly report, this vehicle<br />

provides <strong>Plans</strong> with regular<br />

updates to the MSP data.<br />

MDB<br />

Data File Monthly<br />

Gentran:<br />

P.Rxxxxx.MSPCOBMA.Dyymmdd.<br />

Thhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.MSPCOBMA.Dyy<br />

mmdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory].Rxxxxx.MSPCOBMA.Dy<br />

ymmdd.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-15 All Transmissions Overview


ID# Transmittal<br />

Quarterly Report<br />

72<br />

Front-End Risk Adjustment<br />

System (FERAS) Response<br />

Reports<br />

Frequency Report Quarterly<br />

Report<br />

Missing Payment Exception<br />

Report Data Record Layout<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Description<br />

Report provides quarterly<br />

summary of all errors on all<br />

file submissions within the<br />

three-month quarter.<br />

Data file reporting payment<br />

actions which failed to<br />

complete.<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

FERAS Report Quarterly<br />

MARx<br />

Data<br />

File<br />

Monthly<br />

Payment<br />

Cycle<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

RAPS_ERRORFREQ_QTR_ssssss<br />

Connect:Direct:<br />

TRANSMITTED FROM<br />

PALMETTO<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

73<br />

Yearly Report<br />

P.Rxxxxx.MPERD.Dyymmdd.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.<br />

MPERD.Dyymmdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.<br />

MPERD.Dyymmdd.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

74<br />

RAS Final Yearly Model<br />

Output Report, Part D<br />

Report indicates the year-end<br />

Part D risk adjustment factors for<br />

each beneficiary. MARx<br />

forwards this report, produced by<br />

RAS, to <strong>Plans</strong> as part of the<br />

month-end processing.<br />

RAS<br />

(MARx)<br />

Report<br />

(.pdf)<br />

Yearly<br />

P.Rxxxxx.PTDMOFR.Yeeee.Cvvvvv<br />

.Thhmmss.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PTDMOFR.Yeeee.<br />

Cvvvvv.Thhmmss<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.PTDMOFR.<br />

Yeeee.Cvvvvv.Thhmmss<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

75<br />

RAS Final Yearly Model<br />

Output Data File, Part D<br />

Data file version of the year end<br />

Part D RAS Model Output<br />

Report. MARx forwards this<br />

report, produced by RAS, to<br />

<strong>Plans</strong> as part of the month-end<br />

processing.<br />

RAS<br />

(MARx)<br />

Data File<br />

Yearly<br />

P.Rxxxxx.PTDMOFD.Yeeee.Cvvvvv<br />

.Thhmmss.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.PTDMOFD.Yeeee.<br />

Cvvvvv.Thhmmss<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.PTDMOFD.Yeeee<br />

.Cvvvvv.Thhmmss<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

76<br />

RAS Final Yearly Model<br />

Output Report, Part C<br />

Report indicates the year end<br />

Part C risk adjustment factors for<br />

each beneficiary. MARx<br />

forwards this report, produced by<br />

RAS, to <strong>Plans</strong> as part of the<br />

month-end processing.<br />

RAS<br />

(MARx)<br />

Report<br />

(.pdf)<br />

Yearly<br />

P.Rxxxxx.HCCMOFR.Yeeee.Cvvvv<br />

v.Thhmmss.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.HCCMOFR.Yeeee.<br />

Cvvvvv.Thhmmss<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.HCCMOFR.Yeee<br />

e.Cvvvvv.Thhmmss<br />

<strong>December</strong> <strong>28</strong>, 2012 K-16 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

ID# Transmittal<br />

Yearly Report<br />

Description<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

77<br />

RAS Final Yearly Model<br />

Output Data File, Part C<br />

Data file version of the year end<br />

Part C RAS Model Output<br />

Report. MARx forwards this<br />

report, produced by RAS, to<br />

<strong>Plans</strong> as part of the month-end<br />

processing.<br />

RAS<br />

(MARx)<br />

Data File<br />

Yearly<br />

P.Rxxxxx.HCCMOFD.Yeeee.Cvvvv<br />

v.Thhmmss.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.HCCMOFD.Yeeee.<br />

Cvvvvv.Thhmmss<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.HCCMOFD.Yeee<br />

e.Cvvvvv.Thhmmss<br />

78<br />

Loss of Subsidy Data File<br />

PCUG Record Layout – F.17<br />

79 PDP Loss Data File<br />

80 PDP Gain Data File<br />

The first file is sent in September<br />

<strong>and</strong> identifies members receiving<br />

a joint CMS <strong>and</strong> SSA letter<br />

informing them they will not<br />

have Deemed status for the<br />

following year. The second file is<br />

sent in <strong>December</strong> <strong>and</strong> is an<br />

updated version of the September<br />

file, indicating those<br />

Beneficiaries who still do not<br />

have Deemed status for the<br />

following year.<br />

The data file has a record length<br />

of 500 bytes. The TRC used for<br />

this special file type is 996. TRC<br />

996 indicates the loss of Deeming<br />

which means the Beneficiary will<br />

not be redeemed for the<br />

upcoming period.<br />

Once a year notification file sent<br />

by CMS providing a preliminary<br />

listing of LIS-eligible<br />

Beneficiaries whom CMS<br />

reassigns to a new PDP or to a<br />

new PBP within the same plan<br />

sponsor effective January 1,<br />

2008.<br />

The LOSS file notifies PDPs of<br />

the members they will lose as a<br />

result of reassignment to other<br />

<strong>Plans</strong>. These members are<br />

classified as losing members.<br />

Once a year notification file, sent<br />

by CMS, provides a preliminary<br />

listing of LIS-eligible<br />

Beneficiaries whom CMS<br />

reassigns to a new PDP or to a<br />

new PBP within the same Plan<br />

sponsor effective January 1,<br />

2008.<br />

The GAIN file notifies PDPs of<br />

members they will gain as a<br />

result of the yearly reassignment.<br />

These members are classified as<br />

gaining members.<br />

MARx Data File Twice<br />

Yearly<br />

MBD Data File Yearly<br />

MBD Data File Yearly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.EOYLOSD.Dyymmdd.Th<br />

hmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.EOYLOSD.Dyym<br />

mdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.EOYLOSD.Dyym<br />

mdd.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.APDP5.LOSS.Dyymmdd.<br />

Thhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.APDP5.LOSS.Dyy<br />

mmdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.APDP5.LOSS.Dy<br />

ymmdd.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.APDP5.GAIN.Dyymmdd.<br />

Thhmmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.APDP5.GAIN.Dyy<br />

mmdd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.APDP5.GAIN.Dy<br />

ymmdd.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-17 All Transmissions Overview


ID# Transmittal<br />

Yearly Report<br />

81<br />

82<br />

Long-Term Institutionalized<br />

Resident Report<br />

PCUG Record Layout – F.26<br />

No Premium Due Data File<br />

PCUG Record Layout – F.30<br />

Plan Communications User Guide Appendices, Version 6.3<br />

Description<br />

The Long-Term Institutionalized<br />

(LTI) Resident Report provides<br />

Part D sponsors a list of their<br />

Beneficiaries who are LTI<br />

residents during July <strong>and</strong> January<br />

of each year. This report contains<br />

basic information on the<br />

Beneficiaries <strong>and</strong> their<br />

institutions (Skilled Nursing<br />

Home or Nursing Home).<br />

The no premium due data file<br />

reports members that had a Part<br />

C premium, but will no longer<br />

have the Part C premium in the<br />

upcoming year. This data file is<br />

produced during MARx end of<br />

year processing.<br />

Responsible<br />

System Type Freq. Dataset Naming Conventions<br />

MDS<br />

Report<br />

Twice<br />

Yearly<br />

MARx Data File Yearly<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.LTCRPT.Dyymmdd.Thhm<br />

msst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.LTCRPT.Dyymmd<br />

d.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.LTCRPT.Dyymm<br />

dd.Thhmmsst<br />

Gentran Mailbox/TIBCO MFT<br />

Internet Server:<br />

P.Rxxxxx.SPCLPEX.Dyymmdd.Thh<br />

mmsst.pn<br />

Connect:Direct (Mainframe):<br />

zzzzzzzz.Rxxxxx.SPCLPEX.Dyymm<br />

dd.Thhmmsst<br />

Connect:Direct (Non-Mainframe):<br />

[directory]Rxxxxx.SPCLPEX.Dyym<br />

mdd.Thhmmsst<br />

<strong>December</strong> <strong>28</strong>, 2012 K-18 All Transmissions Overview


Plan Communications User Guide Appendices, Version 6.3<br />

L: MA Plan Connectivity Checklist<br />

Getting Started<br />

or N/A # Task Checkpoint Notes<br />

or N/A<br />

or N/A<br />

Security <strong>and</strong> Access<br />

1. Obtain a Contract Number from CMS/HPMS Once completed, Task #4<br />

may be initiated.<br />

2. Enter Connectivity Data into HPMS Plan Connectivity<br />

Data Module<br />

(<strong>Plans</strong> are required to mail/fax completed forms to<br />

MAPD Help Desk)<br />

3. Complete T1/Connect:Direct information in the PCD<br />

module<br />

1. CMS Connect:Direct data entry into HPMS<br />

2. CMS SPOE ID Request form<br />

Must be started at least 6<br />

weeks prior to target<br />

connectivity testing date.<br />

Contract #:<br />

or N/A # Task Checkpoint Notes<br />

or N/A<br />

or N/A<br />

4. Submit EPOC Designation Letter to CMS After completion of Task<br />

#1.<br />

5. EPOC registered in IACS<br />

(Allow 5 business days once EPOC letter is submitted<br />

before registering in IACS)<br />

6. EPOC approval received from CMS<br />

7. User/Submitter(s) registered in IACS for Enrollment,<br />

BEQ <strong>and</strong> ECRS<br />

8. User/Representative(s) registered in IACS for<br />

Enrollment, BEQ <strong>and</strong> ECRS<br />

After completion of Task<br />

#4.<br />

After EPOC registration is<br />

complete.<br />

After EPOC registration is<br />

complete.<br />

9. User/Submitter(s) registered in IACS for PDE/RAPS Gentran/TIBCO MFT<br />

Submitters only. May be<br />

completed the same time as<br />

Task #7 or at a later date.<br />

Connectivity – Setup<br />

Note: <strong>Plans</strong> perform either Task #10 or Task #11.<br />

or N/A<br />

or N/A<br />

or N/A<br />

or N/A<br />

or N/A<br />

# Task Checkpoint Notes<br />

10. Each item listed in this Task is required by <strong>Plans</strong><br />

submitting data via Connect:Direct.<br />

Set up T1/Connect:Direct to CMS:<br />

1. Contact AT&T or an AT&T reseller to establish<br />

connectivity to CMS via AGNS.<br />

2. Verify access to CMS via AGNS<br />

3. High-level qualifier <strong>and</strong>/or security designations<br />

verified as accessible to CMS.<br />

4. Obtain Connect:Direct Software from Sterling<br />

Commerce.<br />

Must be started at least 6<br />

weeks prior to target<br />

connectivity testing date.<br />

<strong>December</strong> <strong>28</strong>, 2012 L-1 MA Plan Connectivity Checklist


Plan Communications User Guide Appendices, Version 6.3<br />

or N/A<br />

or N/A<br />

or N/A<br />

5. Complete installation <strong>and</strong> configuration of<br />

Connect:Direct Software.<br />

6. Submitter successfully registered in IACS (see<br />

Task #8).<br />

7. Obtain SPOE ID from CMS (see Task #3.2).<br />

11. Each item listed in this Task is required by <strong>Plans</strong><br />

submitting data via Gentran/TIBCO MFT.<br />

or N/A<br />

or N/A<br />

or N/A<br />

Set up Gentran/TIBCO MFT access:<br />

1. Submitter successfully registered in IACS (see<br />

Task #7).<br />

2. Obtain <strong>and</strong> install SFTP Software (if not using<br />

HTTPS)<br />

3. Open required firewalls/ports:<br />

SFTP Port: 10022<br />

HTTPS Port: 3443<br />

Connectivity – Testing<br />

Note: <strong>Plans</strong> perform either Task #12 or Task #13. <strong>Plans</strong> submitting PDE/RAPS data must also perform Task #14.<br />

or N/A<br />

# Task Checkpoint Notes<br />

12. Each item listed in this Task is required by <strong>Plans</strong><br />

submitting data via Connect:Direct.<br />

or N/A<br />

or N/A<br />

or N/A<br />

or N/A<br />

or N/A<br />

or N/A<br />

or N/A<br />

Test T1/Connect:Direct to CMS:<br />

1. Appropriate telecommunications <strong>and</strong> technical<br />

resources participate in conference call with<br />

appropriate CMS Resources (initiated by MAPD Help<br />

Desk).<br />

2. Successfully transfer data to CMS<br />

3. Successfully receive data from CMS<br />

13. Each item listed in this Task is required by <strong>Plans</strong><br />

submitting data via Gentran/TIBCO MFT.<br />

Test Gentran/TIBCO MFT:<br />

1. Mailbox(s) established at CMS is accessible<br />

2. Screenshot of successful access to 1 Gentran<br />

mailbox e-mailed to the MAPD Help Desk.<br />

3. Send test file to Gentran mailbox/TIBCO MFT<br />

server<br />

14. Contact CSSC Help Desk for assistance with<br />

Connectivity Testing of PDE/RAPS data submission.<br />

Task # 7 must be<br />

completed successfully<br />

before this task can be<br />

completed.<br />

<strong>December</strong> <strong>28</strong>, 2012 L-2 MA Plan Connectivity Checklist


Plan Communications User Guide Appendices, Version 6.3<br />

M: Valid Election Types for Plan-Submitted Transactions<br />

Table M-1 shows the valid election types for Plan-submitted enrollment <strong>and</strong> disenrollment<br />

transactions. <strong>Plans</strong> must ensure the requirements in the CMS Enrollment <strong>and</strong> Disenrollment<br />

guidance applicable to the Plan type are followed to properly determine <strong>and</strong> report the election<br />

type.<br />

Table M-1:Valid Election Types for <strong>Plans</strong><br />

Election Types<br />

PLANS<br />

AEP (A) OEPI (T) SEP (Note 2) IEP (E/F) MADP ICEP (I)<br />

MA Y Y Y N Y Y<br />

MA-PD Y Y Y Y Y Y<br />

PDP<br />

Y<br />

N<br />

(Use coordinating<br />

SEP where<br />

appropriate per<br />

CMS guidance)<br />

Y Y N<br />

(Use<br />

coordinating<br />

SEP where<br />

appropriate<br />

per CMS<br />

guidance)<br />

N<br />

SHMO I Y Y Y Y<br />

SHMO II Y Y Y Y<br />

Cost with Part D<br />

Y<br />

N<br />

(Use coordinating<br />

SEP where<br />

appropriate per<br />

CMS guidance)<br />

Y<br />

Y<br />

Use<br />

coordinating<br />

SEP where<br />

appropriate<br />

per CMS<br />

guidance)<br />

Cost without<br />

Part D<br />

None required; however, if the beneficiary is currently enrolled in an MA Plan, a valid<br />

MA election period is required to leave that program <strong>and</strong> enroll in the cost Plan.<br />

WPP Y Y Y Y Y<br />

ESRD I<br />

ESRD II<br />

PACE National<br />

CCIP / FFS<br />

Demos<br />

MDHO Demo<br />

MSHO Demo<br />

Y<br />

Y<br />

None Required<br />

None Required<br />

None Required<br />

None Required<br />

<strong>December</strong> <strong>28</strong>, 2012 M-1 Valid Election Types for<br />

Plan-Submitted


Plan Communications User Guide Appendices, Version 6.3<br />

Election Types<br />

PLANS<br />

AEP (A) OEPI (T) SEP (Note 2) IEP (E/F) MADP ICEP (I)<br />

MSA Y N Y N N Y<br />

MSA Demo Y Y N Y<br />

Note 1: For code usage, refer to the previously released MMA Guidance <strong>and</strong> PDP Guidance.<br />

Note 2: For election type SEP, use the following values under these specific circumstances:<br />

<br />

<br />

<br />

<br />

<br />

U - for Duals <strong>and</strong> Individuals with LIS<br />

W - for EGHP<br />

V - for permanent moves<br />

Y - CMS Casework use only (not submitted by <strong>Plans</strong>)<br />

S - Any other SEP as provided in guidance that is not one of the above values.<br />

Note 3: In addition to these election period identifiers, CMS provides a valid value of ‘X’ for use<br />

in the election period identifier field. This value is an Administrative Action <strong>and</strong> <strong>Plans</strong> may use<br />

when a submitted transaction is not reflective of an actual Beneficiary election, as follows:<br />

<br />

<br />

<br />

<br />

Plan submitted “rollover”- Year-end processing occasionally requires that <strong>Plans</strong> submit<br />

transactions to accomplish the Plan crosswalk from one contract year to another. When<br />

required, as defined in the CMS Call Letter instructions, <strong>Plans</strong> should use the ‘X’ value<br />

in the election period field of the enrollment transaction submitted for this purpose.<br />

Involuntary Disenrollment - In limited circumstances, <strong>Plans</strong> may involuntarily disenroll<br />

individuals for specific reasons <strong>and</strong> when meeting all of the conditions provided in CMS<br />

enrollment guidance. Since these actions are not “elections,” <strong>Plans</strong> should use the value<br />

of ‘X’ in the election period field of the disenrollment transaction submitted for this<br />

purpose.<br />

Premium Option Change - <strong>Plans</strong> may submit changes to an individual’s premium<br />

withholding status via a 72 transaction. When doing so, <strong>Plans</strong> should use the ‘X’ value in<br />

the election period field of the 72 transaction submitted for this purpose.<br />

Plan-submitted “canceling” Transaction - Since beneficiaries may choose to cancel an<br />

enrollment or disenrollment request prior to the effective date of the request,<br />

occasionally <strong>Plans</strong> submit “canceling” transactions to CMS to cancel an already<br />

submitted action. <strong>Plans</strong> should use the value TC 80 to cancel an enrollment or TC 81 to<br />

cancel a disenrollment transaction.<br />

<strong>December</strong> <strong>28</strong>, 2012 M-2 Valid Election Types for<br />

Plan-Submitted

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!