evekhm/cms_iom_500 huggingface dataset:
(General Information, Eligibility, and Entitlement Manual)
c. Correction or Rescinded/Replaced CR changed the due date of specific Business Requirements.   Reason 03 ( CM S MLN Matters  Article Delay) -  Applies only in situations where CMS issued the MLN Matters Article more than three days after the CR was posted on the CMS website. The contractor should include a comment in Item 13 that explains the activity that was not completed and the quarter in which the activity will be completed.  If a contractors quarterly bulletin is due to go out in another quarter, the CR should be added as an add- on in the quarter in which the activity occurred, including a comment that all activity for that CR has been completed.   Reason 04 (CMS delay of file transmission)  - Applies only in situations when the file needed to complete work indicated in the CR was not available timely (i.e., payment files related to annual recurring CRs such a s the HCPCS, Pricer, and OPPS).   Reason 05 (System related delay)   Applies only in the following situations:   a. Shared System Maintainer (SSM) production problem prevents a MAC from completing a specific task in the CR;   b. Non-MAC maintained system (e.g., PECOS, HIGLAS, CWF, etc.) production problem prevents a MAC from completing a specific task in the CR.    Reason 06 (CR extension approved or pending)  - Applies only in situations where CMS Contracting Officer Representativ e (COR) has approved an extension of the implementation date specifically referencing this CR.   Reason 07 (Deadline past quarter end date)  - Applies only in the following situations:   a. CRs with multiple implementation dates;  b. CRs that contain instruction for work to be done after the implementation date listed in the CR.   Reason 08 (Other)  - Applies in all other situations where the implementation of the CR was delayed, and Reasons for Delay 01 through 07 do not apply.   9. Item 13 (Additional Explanation) -  MACs shall enter additional comments regarding the implementation of this CR in this field if a Reason for Delay is selected. Do not update this field for CRs implemented timely.   For the following Reasons for Delay, MACs shall include the following data :
(General Information, Eligibility, and Entitlement Manual)
For the following Reasons for Delay, MACs shall include the following data :  Reason 01 (Due date changed due to TDL)  - TDL reference number (TDL -######) of the specific TDL which grants an extension and the date to which the extension was granted.  Note the actual implementation date of the CR requirements.   Reason 02 (Due date changed due to CR)  - Issued date of the Correction final, CR number and issued date of replacement CR (if applicable), and the revised implementation date.  Note the actual implementation date of the CR requirements.   Reason 03 (MLN delay)  - Provide explanation for delay along with the MLN reference number of the specific MLN  and published date.  Reason 04 (CMS delay of file transmission)  - Name of the delayed file, date that the file was expected, and the date the file was actually received.  Note the actual implementation date of the CR requirements.   Reason 05 (System related delay)   Name of the system, specific production problem identification number, description of the issue, and resolution date (if applicable).  Note the actual implementation date of the CR requirements.  Reason 06 (CR extension approved or pending)  - Name of COR, date approval received, and the revised due date.  Note the actual implementation date of the CR requirements.   Reason 07 (Deadline past quarter end date)  - Note impacted business requirement numbers and the delayed implementation date(s).  MACs shall add this CR to the bottom of the CRIR report in red font for the CRIR report of the quarter where MACs completed their work.  Reason 08 (Other)   Explanation of the delay for situations not applicable to Reasons for Delay 01 through 07.  Use the space allowed in Item 13.  If additional space is needed, MACs may submit with the completed CR Implementation Report a separate explanation document.  P rovide the following information in a clear and concise manner:   a.   Cause of the delay;  b.  If not the entire CR, reference the specific delayed Business Requirements;  c.   Description of specific tasks that were delayed;  d.  Indicate what is the impact to the gov ernment and resolution of the issue that        delayed the CR implementation;  e.   Note the actual implementation date of the CR requirements.   10. CRIR Totals. This section summarizes the totals for the detail rows.
(General Information, Eligibility, and Entitlement Manual)
10. CRIR Totals. This section summarizes the totals for the detail rows.   a. Item 14 (Total number of CRs in this re port) -  This field is calculated. The contractor shall not update this field.  NOTE:  This formula sums both CRs added by CMS and any additional rows of CRs added by the contractor on the spreadsheet.   b. Item 15 (Number of CRs applicable to the contractor)  This field is calculated.  The contractor shall not update this field. NOTE:  This formula counts CRs that the contractor has indicated are applicable by marking an X in Column F.   c. Item 16 (Number of applicable CRs completed by the Implementation Date) -  This field is calculated. The contractor shall not update this field.  NOTE:  This formula counts CRs that the contractor has indicated were implemented timely by marking a Y in Column G.  d. Item 17 (% of applicable CRs completed by Implementation Date) -  This field is calculated. The contractor shall not update this field.  This field reflects the percentage of applicable CRs completed by the Implementation 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 CRs completed timely) -  This field is calculated.  The contractor shall not update this field.  This field reflects the percentage of applicable CRs implemented timely, regardless of contractor controlled reasons for delay, as indicated by a selection of Reason for Delay 8 (Other).  NOTE:  This formula calculates a percentage from the total number of Reason for Delay 08 indicated in Item 19 and the total number of CRs applicable to the contractor in Item 15.
(General Information, Eligibility, and Entitlement Manual)
11. Each MAC shall compl ete and submit one CRIR report by jurisdiction, a cover Letter/Attestation Statement (located on tab 1 of the CRIR Report Template or the Sample in Section 50.3), and if necessary, a separate explanation document.  MACs with multiple jurisdictions may comp lete a separate sheet within a single Excel workbook for each jurisdiction.  By the quarterly due date, each MAC shall submit the CRIR 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 weekend 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.   COMPLETING AND SUBMITTING THE QUARTERLY TDL COMPLIANCE REPORT   Medicare Administrative Contractors (MACs) shall complete the TDL Compliance Repo rt (TCR) for each jurisdiction as follows.  MACs with multiple jurisdictions may complete a separate sheet within a single Excel workbook for each jurisdiction (name each tab accordingly).   There are some TDLs not issued to all Contractors.  If a MAC recei ved a TDL in the reporting period, the TDL should be included on the report.  If CMS omitted a TDL that should have been included in the report, the contractor shall add the TDL to the bottom of the report in red font.  MACs shall update the report in the same manner as a CMS CO entered TDL, with the exception of Item 7 (CMS Component).  For Contractor added rows, Item 7 may remain blank.  Header Rows   The report contains four header rows.   1.Header Row 1, Contains the title, TDL Compliance Report (TCR)  Qu arter X (MMM -MMM) YYYY, where X is the number of the quarter, MMM -MMM are the months included in that quarter, and YYYY is the Calendar Year. This data will be completed by CMS CO.   2.Item 1: Header Row 2, MACs shall enter their Contractor Name and Jurisdiction identifier in Item 1 of the report.
(General Information, Eligibility, and Entitlement Manual)
2.Item 1: Header Row 2, MACs shall enter their Contractor Name and Jurisdiction identifier in Item 1 of the report.   3.Item 2: Header Row 2, MACs shall enter the Date Report Submitted to CMS in Item 2 of the report in MM/DD/YYYY format.  [This is the date the report is e -mailed to CMS CO.]   4.Item 3: Header Row 2, Report D ue.  This is the date the report is due to CMS CO.  This date will be completed by CMS CO.   5.Item 4: Header Row 3, TCR Contractor Contact (First Name, Last Name, Phone). MACs shall enter the first and last name of the individual CMS CO should contact to ask questions regarding information in this report.  The contact must be knowledgeable on the contents of the report.  Detail Rows  Below the Header Rows, Detail Rows shall be completed as follows:   1.Item 5: No. This field contains a consecutive number to track the number of TDLs on the report.  CMS CO will complete this field for all TDLs included on the report by CO. If the contractor adds additional TDLs, they should continue numbering from the previous CMS entered row in red font.  For example, if CMS included 15 TDLs on the report, the contractor shall begin numbering in this field with 16 in red font.   2.Item 6: TDL #.  CMS CO will complete this field with the TDL number for each public TDL issued during the quarter.   3.Item 7: CMS Component.  CMS CO will comp lete this field with the CMS Component responsible for issuing the TDL.  [If MACs added the TDL to the report, they do not need to complete item 7 for those TDLs. ]  4.Item 8: Subject.  CMS CO will complete this field with the subject for all TDLs issued during the quarter.   5.Item 9: CMS Issued Date MM/DD/YYYY. CMS CO will complete this field with the Issued date in MM/DD/YYYY format for all TDLs issued during the quarter.
(General Information, Eligibility, and Entitlement Manual)
5.Item 9: CMS Issued Date MM/DD/YYYY. CMS CO will complete this field with the Issued date in MM/DD/YYYY format for all TDLs issued during the quarter.   6.Item 10: Applicable Workload? (X or blank).  MACs shall complete this field with an X for all TDLs applicable to their workload or leave blank if the TDL is not applicable to their workload.  The TDL is considered applicable to the contractor if any action in the TDL were required to be completed by the contractor in the reporting perio d.  7.Item 11: Contractor Compliance? (Y, N or blank). MACs shall complete this field with a y for all applicable TDLs that the contractor has received, reviewed and complied with the instructions in the TDL.  MACs shall complete this field with a n for all applicable TDLs that the contractor has received and reviewed, but has not complied with the instructions in the TDL.  This field shall remain blank if the TDL is not applicable to the contractor (i.e. Item 10 is blank).   8.Item 12: Reason for Delay  (Leave blank if in compliance).  This field shall remain blank if the TDL has been complied with on or before the due date (i.e. Item 11 is a y) or is not applicable to contractor workload (i.e. Item 11 is blank).  If the contractor did not comply with the instructions in the TDL (i.e. Item 11 is a n), the contractor shall select one of the following reasons from the drop- down list in this field:  01. Due date changed due to TDL  02. Due date changed due to CR  03. System Changes Required to Comply  04. TDL extension approved or pending 05. Deadline past quarter end date  06. Other  01 (Due date changed due to TDL)   Applies only in situations where CMS has issued a subsequent TDL which corrects and/or replaces previous direction provided under the original TDL.  02 (Due date ch anged due to CR)  - Applies only in situations where CMS has issued a CR that supersedes direction provided previously in this specific TDL.  03 (System Changes Required to Comply)   Applies only in the following situations:
(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.
(General Information, Eligibility, and Entitlement Manual)
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.
(General Information, Eligibility, and Entitlement Manual)
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.
(General Information, Eligibility, and Entitlement Manual)
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
(General Information, Eligibility, and Entitlement Manual)
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).
(General Information, Eligibility, and Entitlement Manual)
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;