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.

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)

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

Saved successfully!

Ooh no, something went wrong!