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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!