(General Information, Eligibility, and Entitlement Manual)

a. Shared System Maintainer (SSM) production problem prevents a MAC from completing a specific task in the TDL;   b. Non-MAC maintained system (e.g., PECOS, HIGLAS, CWF, etc.) production problem prevents a MAC from completing a specific task in the TDL;   c. MAC is unable to accomplish a specific task in the TDL without SSM system changes.  04 (TDL extension approved or pending)   Applies only in situations where the CMS Contracting Officer Representative (COR) has approved an extension of the due date specified in the TDL.  05 (Deadline past quarter  end date)   Applies only in the situations where some or all of the tasks in the TDL are due to be completed beyond the reporting period of the TCR report.  06 (Other)   Applies in all other situations where compliance with the TDL was delayed, but Reason s for Delay 01 through 05 does not apply.   9.Item 13: Additional Explanation. MACs shall enter additional comments regarding the compliance of the TDL in this field if a Reason for Delay is selected in Item 12.  Do not update this field for TDLs complied wi th timely.   For the following Reasons for Delay (Item 12), MACs shall include the following data in Item 13:  01 (Due date changed due to TDL)   TDL reference number (TDL -######) of the specific TDL which corrects and replaces the previous TDL.  Note the actual date of compliance with the TDL.  02 (Due date changed due to CR)   CR number and issued date of the CR which supersedes the TDL.  Note the implementation date of the CR.  03 (System Changes Required to Comply)   If a production problem prevents compliance, provide: name of the system, specific production problem identification number, and resolution date (if applicable). Note the actual date of compliance with the TDL.  If shared system changes are needed to comply, describe necessary change and any steps taken to notify CMS of the discrepancy.  04 (TDL extension approved or pending)   Name of the COR, date approval received, and the revised due date.  Note the actual date of compliance with the TDL.  05 (Deadline past quarter end date)   Note specific tasks and the due dates beyond the TCR reporting period. MACs shall add this TDL to the bottom of the TCR report in red font for the TCR report of the quarter where MACs completed their work.  06 (Other)   Explanation of the delay for situations not applica ble to Reasons for Delay 01 through 05. Use the space allowed in Item 13.  If additional space is needed, MACs may submit with the completed TCR report a separate explanation document.  Provide the following information in a clear and precise manner:  a. Cause of the delay;  b. If not the entire TDL, reference the specific delayed task;  c. Description of specific tasks that were delayed;  d. Indicate what is the impact to the government and resolution of the issue with the TDL implementation; e. Note the actual date of compl iance with the TDL.   10. TCR Totals. This section summarizes the totals for the detail rows.   a. Item 14 (Total number of TDLs in this report)  This field is calculated.  The contractor shall not update this field.  NOTE:  this formula sums both TDLs added by CM S and any additional rows of TDLs added by the contractor on the spreadsheet.   b. Item 15 (Number of TDLs applicable to the contractor)  This field is calculated.  The contractor shall not update this field.  NOTE:  this formula counts TDLs that the contracto r has indicated are applicable by marking an x in Column F.   c. Item 16 (Number of applicable TDLs by compliance date)  This field is calculated. The contractor shall not update this field.  NOTE:  This formula counts TDLs that the contractor has indicated were completed timely by marking a y in Column G.  d. Item 17 (% of applicable TDLs by compliance date)  This field is calculated.  The contractor shall not update this field.  This field reflects the percentage of applicable TDLs complied with by the due date, regardless of CMS or contractor controlled reasons for delay.  NOTE: This formula calculates a percentage from Item 15 and Item 16.   e. Item 18 (% of applicable TDLs completed timely)  This field is calculated.  The contractor shall not update this fie ld.  This field reflects the percentage of applicable TDLs complied with timely, regardless of contractor controlled reasons for delay, as indicated by a selection of Reason for Delay 6 (Other).  NOTE:  This formula calculates a percentage from the total nu mber of Reason for Delay 06 indicated in Item 19 and the total number of TDLs applicable to the contractor in Item 15.   11. Each MAC shall complete and submit one TCR report by jurisdiction, a cover Letter/Attestation Statement (located on tab 1 of the TCR Rep ort Template or in Section 50.3), and if necessary, a separate explanation document.  MACs with multiple jurisdictions may complete a separate sheet within a single Excel workbook for each jurisdiction.  By the quarterly due date, each MAC shall submit the  TCR report, via e -mail to the CMS CO mailbox.  [The CMS CO mailbox is: CR_IMPL_REPORTS@cms.hhs.gov. NOTE:   There are no spaces in this Web address.  Underscore _ separates the words CR_IMPL_REPORTS.]  If the report due date of the 28th falls on a weeken d or a holiday, each contractor, including MACs, shall submit the report on the next business day following the due date.   12. Each MAC shall upload the report to the CMS ART system.   50.1 - CR Implementation Report (CRIR) Template  (Rev. 90, Issued: 02- 12-15, Effective: 08 -28-14- Begin with Quarter 3 in 2014.Implementation: 08- 28-14- Begin with Quarter 3 in 2014)   Upon direction from CMS via a Technical Direction Letter, MACs shall download the updated CR Implementation Report Template from Electronic Change Information Management Portal (ECHIMP), Help page.  From there, MACs shall click the link from the List of Documents for the CRIR Template.   50.2 - TDL Compliance Report (TCR) Template  (Rev. 90, Issued: 02- 12-15, Effective: 08- 28-14- Begin with Quarter 3 i n 2014.Implementation: 08- 28-14- Begin with Quarter 3 in 2014)   Upon direction from CMS via a Technical Direction Letter, MACs shall download the updated TCR Template from ECHIMP, Help page.  From there, MACs shall click the link from the List of Documents  for the TCR Template.   50.3 - Sample Cover Letter/Attestation Statement (Rev. 90, Issued: 02- 12-15, Effective: 08- 28-14- Begin with Quarter 3 in 2014.Implementation: 08- 28-14- Begin with Quarter 3 in 2014)     CR Implementation Report   Contractor Name:  Contractor/Jurisdiction Number:  Date Report Submitted to CMS: [MM/DD/CCYY]  Subject:  Attestation Statement: Implementation of Change Requests, Qtr.__, FY__ [Include the appropriate quarter and fiscal year in the Subject line.]   Attention: CMS Central Of fice (CO) Medicare Contractor Management Group (MCMG)   In accordance with the Centers for Medicare & Medicaid Services (CMS) Change Requests 2884, 6102, and 8598, I attest that all instructions required to be implemented within Quarter __ [1, 2, 3 or 4  select appropriate quarter] of FY __ [Enter appropriate fiscal year.] have been implemented. Exceptions are explained in Item 13 of the CR Implementation Report or attached in a separate document.     Sincerely,   [Name of Contractor Certifying Official.]  [Title of Contractor Certifying Official.]   Technical Direction Letter Compliance Report   Contractor Name:  Contractor/Jurisdiction Number:  Date Report Submitted to CMS: [MM/DD/CCYY]  Subject:  Attestation Statement: Compliance with Technical Direction Letters, Qtr.__, FY__ [Include the appropriate quarter and fiscal year in the Subject line.]   Attention: CMS Central Office (CO) Medicare Contractor Management Group (MCMG)   In accordance with  the Centers for Medicare & Medicaid Services (CMS) Change Request 8598, I attest that all instructions required to be complied with within Quarter __ [1, 2, 3 or 4  select appropriate quarter] of FY __ [Enter appropriate fiscal year.] have been complied with. Exceptions are explained in Item 13 of the TDL Compliance Report or attached in a separate document.   Sincerely,   [Name of Contractor Certifying Official.]  [Title of Contractor Certifying Official.]    50.4 - Change Request (CR) Definitions (Rev.  66, Issued: 01- 07-11, Effective: 02- 08-11, Implementation: 02- 08-11)  50.4.1 - Issue Date  (Rev.  66, Issued: 01- 07-11, Effective: 02- 08-11, Implementation: 02- 08-11)  The date the Centers for Medicare and Medicaid Services (CMS) publishes a change request (CR).   When a CR has passed through all phases of the change management process, it is then ready for publication; that is, the CMS is ready to make the instructions contained in the CR available to contractors, maintainers, providers, beneficiarie s and/or any group or organization that may be affected, as appropriate.  The CMS publishes CRs by posting them as Transmittals , on the CMS Web site.   Note: The issue date is named Date on the Transmittal form, One- Time Notification, Recurring Update Not ification, and the Standard CR forms.  It is sometimes referred to as the transmittal date.   50.4.2 - Implementation Date  (Rev.  66, Issued: 01- 07-11, Effective: 02- 08-11, Implementation: 02- 08-11)  The implementation date identified in a change request ( CR) is the date by which Medicare fee-for-service contractors and shared system maintainers shall apply all changes detailed in the business requirements, unless otherwise specified.  It is the date when all necessary updates to infrastructure, business pr ocesses and/or supporting technology changes shall be completed and operational in order to execute new/modified policy and procedure.   For CRs that do not require changes to the shared systems (non- system changes), contractors are usually given 30 to 90 days from issuance to implement the CR.   For CRs that do require changes to the shared systems (system changes), a date is specified that usually corresponds with one of the quarterly shared system release dates.  The date is usually the first Monday of the  quarter (for example, January 3, April 4, July 5, or October 3 for 2011).   Unless otherwise stated, the implementation date is the same for all business requirements listed within a specific CR.  In some instances, a separate implementation date(s) may be given for a particular business requirement(s) within a CR.  Implementation and effective dates are frequently not the same. The list below contains the scenarios for the differences:    The effective date and implementation date are different because the f irst day of the quarter is not a Monday;    The effective date and the implementation date are different because the effective date occurs after the implementation date;   The effective date and the implementation date are different because the effective date occurs before the implementation date, but both dates are in the future; or    The effective date and the implementation date are different because the effective date occurs before the implementation date, and the effective date is in the past, while the implementation date is in the future.   50.4.3 - Effective Date  (Rev.  66, Issued: 01- 07-11, Effective: 02- 08-11, Implementation: 02- 08-11)   The effective date identified in a change request (CR) is the date on which any new rules, laws, processes and/or poli cies become active.   Beginning on this date, Medicare contractors shall apply the new rules to process Medicare claims according to their updated business processes and supporting technology.   The effective date is normally a mandated date resulting from l egislation or a regulation.  In the case of National Coverage Determinations (NCDs), the effective date is the first day the item or service that is the subject of the NCD is covered nationally under the Medicare Program.