Standard Claims Extract Format - Pharmacy and Reference File Download Link
https://eu2.contabostorage.com/00f3241116844f24b628f46d81abb929:st1/folder6/6408/1655969401_appendix3_-_Standar_Format.xls
2026-05-30 04:30:13 - Admin
<style> body { font-family: Arial, Helvetica, sans-serif; line-height: 1.6; margin: 0; padding: 0 20px; background-color: #f9f9f9; color: #333; } h1, h2, h3 { color: #2c3e50; } nav { background-color: #ffffff; border-bottom: 1px solid #ddd; padding: 10px 0; margin-bottom: 20px; } nav a { margin: 0 15px; text-decoration: none; color: #2980b9; font-weight: bold; } nav a:hover { text-decoration: underline; } table { width: 100%; border-collapse: collapse; margin: 20px 0; } th, td { border: 1px solid #ccc; padding: 8px; text-align: left; } th { background-color: #eaeaea; } .container { max-width: 960px; margin: auto; background-color: #fff; padding: 30px; box-shadow: 0 0 5px rgba(0,0,0,0.1); } </style> <nav> <a href="#overview">Overview</a> <a href="#structure">File Structure</a> <a href="#field-list">Key Fields</a> <a href="#usage">Usage & Benefits</a> <a href="#implementation">Implementation Tips</a> </nav> <div class="container"> <h1>Standard Claims Extract Format Pharmacy</h1> <section id="overview"> <h2>What is the Standard Claims Extract Format?</h2> <p>The Standard Claims Extract (SCE) Format is a nationallyadopted data specification that defines how pharmacy claim information is exchanged between health plans, pharmacies, clearinghouses, and government agencies. It provides a single, consistent layout for claimlevel data, eliminating the need for custom mappings and reducing processing errors.</p> <p>Originally created by the Centers for Medicare & Medicaid Services (CMS) as part of the Medicare Part D reporting requirements, the format has been extended to commercial plans and other payerpharmacy networks. It is designed to be flexible enough to support a wide range of pharmacy services retail, specialty, longterm care, and mailorder while still delivering the granularity needed for analytics, compliance, and reimbursement.</p> </section> <section id="structure"> <h2>File Structure and Delivery Mechanisms</h2> <p>Each SCE file is a plaintext, pipedelimited (|) file that contains a series of records. The first record is a header, followed by a variable number of claim detail records, and ends with a trailer record that summarizes the file. The main components are:</p> <ul> <li><strong>Header (H)</strong> identifies the file type, creation date, sending organization, and version of the specification.</li> <li><strong>Claim Detail (D)</strong> one line per pharmacy claim, containing information about the patient, drug, prescriber, pharmacy, and financials.</li> <li><strong>Trailer (T)</strong> provides record counts and a checksum to verify file integrity.</li> </ul> <p>Files are typically transferred via secure FTP (SFTP), AS2, or directly through API endpoints that support bulk uploads. Encryption (AES256) and hash verification (SHA256) are recommended to meet HIPAA security standards.</p> </section> <section id="field-list"> <h2>Key Fields in a Claim Detail Record</h2> <p>Although the full specification includes more than 150 fields, the most commonly used elements for routine reporting are summarized below.</p> <table> <thead> <tr> <th>Field Name</th> <th>Position (Example)</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>Record Type</td> <td>1</td> <td>Always D for claim detail.</td> </tr> <tr> <td>Claim Identifier</td> <td>221</td> <td>Unique identifier assigned by the payer.</td> </tr> <tr> <td>Member ID</td> <td>2241</td> <td>Encrypted subscriber or patient identifier.</td> </tr> <tr> <td>Service Date</td> <td>4249</td> <td>Date the medication was dispensed (YYYYMMDD).</td> </tr> <tr> <td>National Drug Code (NDC)</td> <td>5064</td> <td>11digit identifier for the drug product.</td> </tr> <tr> <td>Quantity Dispensed</td> <td>6570</td> <td>Number of units (e.g., tablets, mL).</td> </tr> <tr> <td>Days Supply</td> <td>7173</td> <td>Prescribed days of therapy.</td> </tr> <tr> <td>Prescriber NPI</td> <td>7488</td> <td>National Provider Identifier of the prescriber.</td> </tr> <tr> <td>Pharmacy NPI</td> <td>89103</td> <td>National Provider Identifier of the dispensing pharmacy.</td> </tr> <tr> <td>Gross Amount</td> <td>104113</td> <td>Total charge before discounts (in cents).</td> </tr> <tr> <td>Paid Amount</td> <td>114123</td> <td>Amount actually paid to the pharmacy (in cents).</td> </tr> <tr> <td>CoPay Amount</td> <td>124133</td> <td>Members responsibility.</td> </tr> <tr> <td>Benefit Type</td> <td>134136</td> <td>Indicates generic, brand, specialty, etc.</td> </tr> <tr> <td>Claim Status</td> <td>137139</td> <td>Paid, Rejected, Pending, etc.</td> </tr> </tbody> </table> <p>All numeric values are rightjustified and padded with leading zeros. Text fields are leftjustified and padded with spaces. Empty fields must be represented by the appropriate number of delimiters.</p> </section> <section id="usage"> <h2>Why Use the Standard Claims Extract Format?</h2> <p><strong>Interoperability</strong> By adhering to a single, prescribed layout, pharmacies and payers can exchange data without custom transformations, which accelerates onboarding and reduces integration costs.</p> <p><strong>Regulatory Compliance</strong> Many state Medicaid programs, Medicare Part D, and large commercial carriers require SCE submissions for rebate reporting, utilization monitoring, and fraud detection.</p> <p><strong>Data Quality</strong> The format enforces strict field lengths, data types, and mandatory elements, which helps catch errors early in the transmission process.</p> <p><strong>Analytics & Business Intelligence</strong> Consistent claim-level data enable robust trend analysis, cost forecasting, and performance benchmarking across multiple plans and pharmacy networks.</p> </section> <section id="implementation"> <h2>Implementation Tips and Best Practices</h2> <h3>1. Validation Before Transmission</h3> <ul> <li>Run a schema validator against the latest CMS SCE specification.</li> <li>Check date fields for valid calendar dates and ensure that numeric fields contain only digits.</li> <li>Confirm that NDC numbers match the FDAs NDC directory.</li> </ul> <h3>2. Secure File Transfer</h3> <ul> <li>Use SFTP with dedicated user accounts per trading partner.</li> <li>Implement GPG or PGP encryption for an additional layer of security.</li> <li>Maintain an audit log of uploads, downloads, and checksum results.</li> </ul> <h3>3. Error Handling & Reconciliation</h3> <ul> <li>Process the trailer record to verify record counts and checksum.</li> <li>Create a rejection file that lists line numbers, field positions, and error codes for any invalid records.</li> <li>Schedule daily or weekly reconciliation reports that compare sent vs. received claim totals.</li> </ul> <h3>4. Version Management</h3> <p>The specification is periodically updated (e.g., 2022, 2023 versions). Include the version number in the header and maintain backwardcompatible parsers for partners that have not migrated.</p> <h3>5. Testing with Public Test Files</h3> <p>CMS publishes sample files for each version. Use these to verify that your parsing logic correctly handles edge cases such as:</p> <ul> <li>Multiple claim lines for a single prescription (e.g., split fills).</li> <li>Zerovalue paid amounts (e.g., 100% patient responsibility).</li> <li>Special characters in freetext fields (e.g., pharmacy name).</li> </ul> <h3>6. Documentation and Support</h3> <p>Maintain an internal datadictionary that maps each field to business rules and downstream system requirements. Establish a single point of contact for each trading partner to resolve format questions quickly.</p> </section> </div>