Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 868 Date: March 9, 2011

Similar documents
Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 2150 Date: February 4, 2011

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 2167 Date: February 25, 2011

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 1029 Date: January 26, 2012

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 947 Date: August 12, 2011

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 3438 Date: January 8, 2016

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 895 Date: May 6, 2011

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services(CMS) Transmittal 1727 Date: May 1, 2009

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 1634 Date: March 11, 2016

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 3288 Date: July 2, 2015

Department of Health & Human Services (DHHS) Centers for Medicare & Medicaid Services (CMS) Transmittal 1026 Date: January 26, 2012

277 STATUS RESPONSE - Outbound Translation

276 STATUS REQUEST - Inbound Translation

I. SUMMARY OF CHANGES: The purpose of this update is to communicate to Medicare Contractors changes to CMS and NIST requirements and procedures.

Chapter 2 Section 2.3

Chapter 2 Section 2.3. Data Requirements - Header Record Data

ecms Processes and Procedures Contractor Users Update August 2017 Prepared by CACI International, Inc.

DATE: August 3, Cheri Rice, Director Medicare Plan Payment Group. Revised MAO-004 File Layout

HIPAA FINAL SECURITY RULE 2004 WIGGIN AND DANA LLP

JD Edwards World EDI Error Notification. Version A9.2

UNCLASSIFIED. UNCLASSIFIED Navy Page 1 of 9 P-1 Line #9

MEDICARE Texas (TRAILBLAZERS) PRE-ENROLLMENT INSTRUCTIONS 00900

Legislative update. December 2013

TEXAS MEDICARE (TRAILBLAZERS) CHANGE FORM MR085

MEDICAID MARYLAND PART A (MCDMD) PRE-ENROLLMENT INSTRUCTIONS

RST Standards Committee Friday 13 July 2018 Record of Decisions

Common Operating Environment (COE) Platform Certification Program. Certification Policy

R UNIT 2. Transmission Media DPW

Data Submission Dispenser Guide Florida Department of Health Prescription Drug Monitoring Program

ACH Rules Update for Originating Companies

MEDICARE IDAHO PRE ENROLLMENT INSTRUCTIONS MR003

Oracle Technology Network Developer License Terms for Java Card Classic Edition and Java Card Connected Edition Software Development Kits

WV MMIS EDI File Exchange User Guide Version 1.0 West Virginia Trading Partner Account Electronic Data Interchange (EDI) File Exchange User Guide

2017 MOC PEDIATRIC PRACTICE LOG TEMPLATE:

Provider Monitoring Process

Any symbols displayed within these pages are for illustrative purposes only, and are not intended to portray any recommendation.

ISP Order Form Field Definitions

MISSISSIPPI MEDICAID DENTAL ELECTRONIC CLAIMS ENROLLMENT REGISTRATION

Business Requirements Specification for the. Nomination and Matching Procedures. In Gas Transmission Systems (NOM BRS)

Mississippi Medicaid. Mississippi Medicaid Program Provider Enrollment P.O. Box Jackson, Mississippi Complete form and mail original to:

Overview of DIR Reporting Requirements, P2P Reconciliation, and Reconciliation Exclusion Process

HP points of contact for EDI technical support. HP point of contact for extracts. Questions or concerns. Testing timeline

Service Segments. Edition 2012

Additional License Authorizations for HPE OneView for Microsoft Azure Log Analytics

HIPAA--The Medicare Experience September, Kathy Simmons Technical Advisor OIS/Division of Data Interchange Standards

MEDICAID MARYLAND PRE-ENROLLMENT INSTRUCTIONS MCDMD

Change Healthcare ERA Provider Information Form *This form is to ensure accuracy in updating the appropriate account

PCI Interrupt Controller for Industry Standard PCI-ISA Bus Architecture using PCI-to-PCI Bridge Technology. Ross L. Armstrong

LEADER ICT System Technical Guidance for Local Authorities on Article 48 Checks

ENABLING REPROGRAMMABLE CRYPTOGRAPHIC PRODUCTS IN SPACE. Joseph D. Bull ACSAC 2008 December 11, 2008

Change Healthcare CLAIMS Provider Information Form *This form is to ensure accuracy in updating the appropriate account

ACA Cloud Compliance Solution

Brooklyn-Kiev Port LLC IT Department APERAK. Client Guide Release: D95B Version: 1.0

Brooklyn-Kiev Port LLC IT Department COARRI. Client Guide Release: D95B Version: 1.2. Alexander V. Stolyarov, CIO Ilya V. Kryukin, EDI Engineer

1- How do you register for an account with Alberta Transportation s Online Services?

Bar Code Discovery. Administrator's Guide

Instructions for Caorda Web Solutions T4E/T4A Portal

MEDICARE FLORIDA PRE ENROLLMENT INSTRUCTIONS MR025

MEDICAID MARYLAND PRE ENROLLMENT INSTRUCTIONS MCDMD

SHORT TERM OPERATING RESERVE E-TENDER GUIDANCE DOCUMENT

Standard COM-002-2a Communications and Coordination

BESNet Training Manual

Guide 15. ICAP Reference System User s Guide

IBM Managed Security Services for Security

NEPOOL GIS User Guide

NEPOOL GIS User Guide

UBT IT&T Terms & Conditions of Sale

COMPUTER & INFORMATION TECHNOLOGY CENTER. Information Transfer Policy

New Hampshire State Requirements

Dispenser s Implementation Guide

Gatekeeper and Notice Requirements For Direct Electronic Access and Routing Arrangements

DATA SUBMISSION REQUIREMENTS MANUAL

University of North Carolina at Charlotte

` Hispanic / Latino ` Not Hispanic / Latino A B C D E F G H I J K L M N O P Q R S T U V W X Y Z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Internet Transaction System User Guide

MegaStat Installation Instructions

Please print or type. Complete all areas of Agreement and Enrollment form, unless otherwise indicated.

Early Intervention Indiana First Steps Indiana First Steps HIPAA Testing Plan

DO NOT SEND DUPLICATE COPIES OF YOUR LOG AND DO NOT SEND A PRINTED COPY.

MiPCT Dashboard Report Writer

Licensing Guide. BlackBerry Enterprise Service 12. Version 12.0

PLC CPUs IC697CPU780. Features. 16 MHz, 32-Bit Floating Point Expandable Central Processing Unit for Hot Standby CPU Applications

LACS Link Product Developer Licensee Performance Requirements

DynacViews. User Guide. Version 2.0 May 1, 2009

Maryland Health Insurance Exchange (MHBE) Standard Companion Guide Transaction Information

TOP/IRO Standards. RC Users Group January 21, Vic Howell Manager, Operations Engineering Support

EDI ENROLLMENT AGREEMENT INSTRUCTIONS

Electronic Disclosure and Electronic Statement Agreement and Consent

Q&A for Citco Fund Services clients The General Data Protection Regulation ( GDPR )

VFO ISP Order Request Form Form Field Name Field Characteristics Valid Values Description R/O/C (R-Required, C-Conditional, O-Optional)

End User Licence. PUBLIC 31 January 2017 Version: T +44 (0) E ukdataservice.ac.uk

Change Healthcare CLAIMS Provider Information Form *This form is to ensure accuracy in updating the appropriate account

Making trust evident Reporting on controls at Service Organizations

Guide: HIPAA. GoToMeeting and HIPAA Compliance. Privacy, productivity and remote support. gotomeeting.com

Grade 8. ` Hispanic / Latino ` Not Hispanic / Latino A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

* Free calls from landlines and public phones. Some standard network charge applies.

Technical Note DDR2 Package Sizes and Layout Requirements

Streamline SmartCare Network180 EHR

CMDB AND C ONFIGURATION M ANAGEMENT P ROCESS, S OFTWARE T OOLS C REATION AND M AINTENANCE, P LANNING AND I MPLEMENTATION G UIDE

Encounter Data Industry Update Q&A Documentation

Alberta Reliability Standards Compliance Monitoring Program. Version 1.1

Transcription:

anual ystem Pub 100-20 One-Time Notification Department of ealth & uman ervices (D) enters for edicare & edicaid ervices () Transmittal 868 Date: arch 9, 2011 hange equest 7289 Transmittal 855, dated ebruary 4, 2011 is being rescinded and replaced by Transmittal 868 dated arch 9, 2011. orrection to the Error eport ecord to fix typos and incorrect formulas that were not identified during the s PO reviews. ll other information remains the same. UBJET: July ommon Edits and Enhancements odule (E) and eceipt, ontrol, and Balancing Updates. UY O NGE: The purpose of this hange equest () is to instruct the E developers, Part and B edicare dministrative ontractors (), and the Durable edical Equipment (DE) ommon Electronic Data nterchange (ED) contractor in their continuing development efforts of the E and eceipt, ontrol, and Balancing software and environment requirements. This instruction includes issues identified during the lpha, Beta and User cceptance Testing (UT) test periods. EETVE DTE: July 1, 2011 PLEENTTON DTE: July 5, 2011 Disclaimer for manual changes only: The revision date and transmittal number apply only to red italicized material. ny other material was previously published and remains unchanged. owever, if this revision contains a table of contents, you will receive the new/revised information only, and not the entire table of contents.. NGE N NUL NTUTON: (N/ if manual is not updated) =EVED, N=NEW, D=DELETED-Only One Per ow. /N/D N/ PTE / ETON / UBETON / TTLE. UNDNG: or iscal ntermediaries (s), egional ome ealth ntermediaries (s) and/or arriers: Not pplicable. or edicare dministrative ontractors (s): The edicare dministrative ontractor is hereby advised that this constitutes technical direction as defined in your contract. does not construe this as a change to the tatement of Work. The contractor is not obligated to incur costs in excess of the amounts allotted in your contract unless and until specifically authorized by the ontracting Officer. f the contractor considers anything provided, as described above, to be outside the current scope of work, the contractor shall withhold performance on the part(s) in question and immediately notify the ontracting Officer, in writing or by e-mail, and request formal directions regarding continued performance requirements.

V. TTENT: One-Time Notification *Unless otherwise specified, the effective date is the date of service.

ttachment One-Time Notification Pub. 100-20 Transmittal: 868 Date: arch 9, 2011 hange equest: 7289 Transmittal 855, dated ebruary 4, 2011 is being rescinded and replaced by Transmittal 868, dated arch 9, 2011. orrection to the Error eport ecord to fix typos and incorrect formulas that were not identified during the s PO reviews. ll other information remains the same. UBJET: July ommon Edits and Enhancements odule (E) and eceipt, ontrol, and Balancing Updates Effective Date: July 1, 2011 mplementation Date: July 5, 2011. GENEL NOTON. Background: The enters for edicare and edicaid ervices () is in the process of implementing the next version of the ealth nsurance Portability and ccountability ct transactions. The ecretary of the Department of ealth and uman ervices (D) has adopted ccredited tandards ommittee () X12 Version 5010 and the National ouncil for Prescription Drug Programs (NPDP) Version D.0 as the next P transaction standards for covered entities to exchange P transactions. The final rule was published on January 16, 2009. ome of the important dates in the implementation process are: Effective Date of the regulation: arch 17, 2009 Level compliance by: December 31, 2010 Level compliance by: December 31, 2011 ll covered entities have to be fully compliant on: January 1, 2012 Level compliance means that a covered entity can demonstrate that it could create and receive compliant transactions, resulting from the compliance of all design/build activities and internal testing. Level compliance means that a covered entity has completed end-to-end testing with each of its trading partners, and is able to operate in production mode with the new versions of the standards. D has promulgated in the inal ules provisions which permit dual use of existing standards ( X12 40101 and NPDP 5.1) and the new standards (5010 and D.0) from the arch 17, 2009, effective date until the January 1, 2012 compliance date to facilitate testing subject to trading partner agreement. The purpose of this hange equest () is to instruct the E developers, Part and B edicare dministrative ontractors (), and the Durable edical Equipment (DE) ommon Electronic Data nterchange (ED) contractor in their continuing development efforts of the E and eceipt, ontrol, and Balancing software and environment requirements. This instruction includes issues identified during the lpha, Beta and User cceptance Testing (UT) test periods. This instructs the /B s, ED, and the hared ystem aintainers of the E software in the development and implementation of new error reporting capabilities for version 5010 claims. has been holding weekly work group meetings with the s, ED, and E developers for several months to determine the requirements.

Estimates for this should include a breakdown as part of the Level of Effort (LOE) response, utilizing the following table to be included in the Estimate-pecific omments portion of the LOE template, to follow the nvestment Lifecycle Phases. nvestment Lifecycle Phase Total ours Total ost Pre-mplementation/ eview Design & Engineering Phase Development Phase Testing Phase mplementation Phase Note that the Pre-mplementation/ eview costs will not be funded under the unique funding situation for the 5010/D.0 project, but instead out of the s pot of hours for Pre-mplementation/ eview. B. Policy: ealth nsurance eform: odifications to the ealth nsurance Portability and ccountability ct (P): inal ules published in the ederal egister on January 16, 2009, by the D at 45 Part 162.. BUNE EQUEENT TBLE Number equirement esponsibility (place an X in each applicable column) / D hared- ystem OT E B E aintainers 7289.1 The /B contractors shall generate an error record as output from their translator corresponding to each instance of a 277 T error (as documented in the 837 Edits preadsheet) occurring at the T-E level during translation from the X12 format to the flat file for version 5010 837 claim transactions. 7289.2 The DE ED contractor shall generate an error record as output from their translator corresponding to each instance of a 277 T and/or a 277 error (as documented in the 837 Edits preadsheet) occurring at the T-E level during translation from the X12 format to the flat file for version 5010 837 claim transactions. 7289.3 The DE ED contractor shall generate an error record as output from their translator for all business level edits encountered during translation from the NPDP D.0 format to the flat file for version D.0 transactions. 7289.4 The /B contractors shall place the error records in an input folder (to be developed by the E developers) for inclusion in the Error ecord X X E V W ED ED

Number equirement esponsibility (place an X in each applicable column) / D hared- ystem OT E B E aintainers data base for future reporting. 7289.5 The DE ED contractor shall place the error in the Error ecord data base for future reporting. 7289.6 The hared ystem aintainers of the ommon Edits and Enhancement odule (E) software shall generate an error record as output from the E to each instance of a 277 error (as documented in the 837 Edits preadsheet) occurring at the T-E level during the E processing of the translated flat file for version 5010 837 claim transactions. 7289.7 The hared ystem aintainers of the E software shall create a process for the collection of error records from both the /B s translator output and the E software error records for the purposes of database normalization prior to insertion in the newly developed Error eporting Database. 7289.8 The hared ystem aintainers of the E software shall create a process for the extraction of error records from the newly developed Error eporting Database for the purposes of creating the /B s Top 10 Error eport and the ubmitter Error ate eport. These extract files shall be in a omma eparated Value (V) format in icrosoft Excel Version 2003 or higher in compliance with the /B s tatement of Work under deliverables. 7289.9 The /B s and the ED contractor shall post to its internet web page(s) the /B s Top 10 Error eport. This extract file shall be in a omma eparated Value (V) format in icrosoft Excel Version 2003 or higher in compliance with the /B s tatement of Work under deliverables. 7289.9.1 The /B s shall use the V from business requirement 7289.8 to generate the readable report for postings and listserv messages. 7289.10 The hared ystem aintainers of the E software shall create a process for the purging of error records from the newly developed Error eporting Database. This purge process shall be parameter driven in order for the /B s to control the size and performance of the database in its LD environment. 7289.11 The hared ystem aintainers of the E software shall create a process for the backing-up of records X X E V W ED E E E ED E E

Number equirement esponsibility (place an X in each applicable column) / D hared- ystem OT E B E aintainers contained the newly developed Error eporting Database as appropriate for the LD environment which shall include processes to synchronize E Editing processes with the Error eporting processes. 7289.12 The ED contractor shall create a process for the extraction of error records from the newly developed Error eporting Database for the purposes of creating the ED/DE s Top 10 Error eport. This extract file shall be in a oma eparated Value (V) format in icrosoft Excel Version 2003 or higher in compliance with the DE s and ED tatement of Work under deliverables. 7289.13 The ED contractor shall create a process for the purging of error records from the newly developed Error eporting Database. This purge process shall be parameter driven in order for the ED contractor to control the size and performance of the database in its LD environment 7289.14 The ED contractor shall create a process for the backing-up of records contained the newly developed Error eporting Database as appropriate for the LD environment which shall include processes to synchronize ED Editing processes with the Error eporting processes. 7289.15 The hared ystem aintainers of the E software shall create a Edit Business Description table (to be driven from the Part and Part B edits spreadsheets) within the newly developed Error eporting Database. 7289.15.1 The hared ystem aintainers of the E software shall create a process in the newly developed Error eporting Database to crosswalk from the edit numbers, being reported on the ETD reports, and populate the edit business description on the extract from the /B s Top 10 Error eport and the ubmitter Error ate eport. 7289.16 The hared ystem aintainers of the E software shall create a purge process (if already developed, this could mimic the process put in place for the Dupe table from 7090) keying on values ET11 and ET13 from the Error ate eport ecord. E V W ED ED ED E E E

. POVDE EDUTON TBLE Number equirement esponsibility (place an X in each applicable column) / D hared- ystem OT E B E aintainers None. E V W V. UPPOTNG NOTON ection : or any recommendations and supporting information associated with listed requirements, use the box below: N/ X-ef equirement Number ecommendations or other supporting information: ection B: or all other recommendations and supporting information, use this space: N/ V. ONTT Pre-mplementation ontact(s): Jason Jackson (410) 786-6156 jason.jackson3@cms.hhs.gov ichael abral (410) 786-6168 michael.cabral @cms.hhs.gov Post-mplementation ontact(s): ontact your ontracting Officer s Technical epresentative (OT) or ontractor anager, as applicable and the pre-implementation contacts: Jason Jackson (410) 786-6156 jason.jackson3@cms.hhs.gov ichael abral (410) 786-6168 michael.cabral @cms.hhs.gov V. UNDNG ection : or iscal ntermediaries (s), egional ome ealth ntermediaries (s), and/or arriers: Not pplicable ection B: or edicare dministrative ontractors (s): The edicare dministrative ontractor is hereby advised that this constitutes technical direction as defined in your contract. does not construe this as a change to the tatement of Work. The contractor is not obligated to incur costs in excess of the amounts allotted in your contract unless and until specifically authorized by the ontracting Officer. f the contractor considers anything provided, as described above, to be outside the current scope of work, the contractor shall withhold performance on the part(s) in question and immediately notify the ontracting Officer, in writing or by e-mail, and request formal directions regarding continued performance requirements. ttachments - 2

Payer D/tate Workload Number Edit Number Number of Edit occurences Business Edit essage

- Error eport ecord Element dentifier ontrol ecord ross-walk Description Data Type ecord Position tart ecord Position End Length Picture lause Values ET T Error eport ecord ET01 Error eport ecord D /N 1 4 4 Pic X(04) ETD - Error record for T-E level error information ET - Error record for -E level error information (ET records are to contain roll-up information for their associated ETD records) ET02 T02 Transaction Type /N 5 9 5 Pic X(05) 837, NPDP ET03 T04 Transaction Line of Business /N 10 10 1 Pic X(01) laims only - nstitutional P- Professional N- NPDP ET04 T05 nterchange ender D /N 11 25 15 Pic X(15) 837-06 data element NPDP - 880-K1 NPDP batch header ET05 T14 nterchange ontractor D /N 26 40 15 Pic X(15) 837 - T14 NPDP - 880-K7 NPDP batch header ET06 T07 nterchange reate Date NU 41 48 8 Pic 9(08) 837-09 data element Note: 09 is format YYDD (6 bytes) this field will require the (20) to be appended to the beginning of the 09 value so final format is YYDD NPDP - 880-K2 NPDP batch header ET07 T08 nterchange reate Time NU 49 52 4 Pic 9(04) 837-10 data element NPDP - 880-K3 NPDP batch header ET08 T09 nterchange ontrol Number NU 53 61 9 Pic 9(09) 837-13 data element NPDP - 806-5 NPDP batch header ET09 T10 nterchange Version /N 62 66 5 Pic X(05) 837-00501 (12 data element) NPDP - D.0 ET10 T11 nterchange Test/Prod ndicator /N 67 67 1 Pic X(01) T- Test P- Production ET11 N/ ycle Date NU 68 74 7 Pic 9(07) YYYYDDD (Julian Date) To be populated by the ET12 N/ reate Time NU 75 80 6 Pic 9(06) To be populated by the ET13 T15 E ycle Date NU 81 87 7 Pic 9(07) YYYYDDD (Julian Date) To be populated by the E ET14 T16 E reate Time NU 88 93 6 Pic 9(06) To be populated by the E ET15 T17 Local Data enter Tracking /N 94 123 30 Pic X(30) ET16 T20 Total number of UNT segments ent ET17 T22 Total dollar amount sent submitted charges NU 124 132 9 Pic 9(09) Total number of the units counted for the transaction type. 837- L NPDP- 00 (this value is based on the segment D in positions 27-28 of the flat file) NU 133 145 13 Pic 9(11)v99 837 - This is the total dollar value T-E NPDP - 430-DU ET18 N/ Error percentage holder NU 146 150 5 Pic 9(03)v99 ET only - alculation is: (ET24 / ET16) x 100 ET19 N/ Edit eference Number /N 151 180 30 Pic X(30) ETD only This is the edit number from the 837 Edit spreadsheet ET20 N/ Edit ount NU 181 184 4 Pic 9(04) ETD - number of times the edit set in that T-E ET - number of times the edit set within an -E ET21 N/ Business Edit Language /N 185 436 252 Pic X(252) ETD only ET22 T01 ontrol ecord D /N 437 440 4 Pic X(04) TD or T ET23 N/ Transaction et ontrol Number /N 441 449 9 Pic X(09) ETD - T02 from inbound 837 file ET - Blank ET24 N/ # of laims in Error NU 450 458 9 Pic 9(09) ETD - total number of units counted in ET20 with error reported in ET19 ET - ll claims in error - shoud align with T30 from the 277 control record ET25 N/ iller /N 459 500 42 Pic X(42) evised 01/24/2011 1 of 1 Error Key