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 />

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

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

Saved successfully!

Ooh no, something went wrong!