evekhm/cms_iom_500 huggingface dataset:
(Medicare Claims Processing Manual)
40.4 - Referral of Critical Cases to the Regional O ffice (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  When the MAC identifies a claim meeting the criteria listed below, it contacts the RO via established referral methods.  The MAC identifies the beneficiary by name and MBI,  specifies the nature of the problem, states that the criteria are met, and gives the dates of all actions.  The MAC provides all available supporting documentation.  Examples of such documentation are:    Social Security Administration's (SSA) reply to Form  CMS -1980 in the case of entitlement questions; and    A copy of the Health Insurance Master Record Entitlement Status Query (ESQ) received from an SSA District Office.   The criteria are:   Two follow -ups have been made to the Social Security Office (SSO) and the CWF Master Record has not been corrected;   At least 60 days have elapsed since the correction procedures were initiated;   A serious hardship to the beneficiary or a public relations problem has developed;   Corrections or changes to HMO termination dat es are necessary; and   The SSO response indicates that both the MBR and HI Master Records are correct.   The MAC marks the information "CRITICAL CASE." The MAC flags the file for special handling and expedites the claim as soon as the reply is received.   The MAC must diary the case for 30 calendar days.  By that time the RO should have a response and advise the MAC. If the MAC receives a positive basic reply record before hearing from the RO, it notifies the RO.   50 - Requesting or Providing Assistance to Res olve CWF Rejects  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  When a MAC has difficulty processing a bill because a prior bill was incorrectly processed and posted to CWF by another MAC (A/B MAC or DME MAC), the two  A/B MACs or DME MACs must work together to resolve the error. Where help is needed from another A/B MAC or DME MAC, the submitting MAC requests assistance from the contractor whose bill was processed incorrectly.  The A/B MAC or DME MAC that processed the bill i s identified in the CWF reject trailer.
(Medicare Claims Processing Manual)
50.1 - Requesting A/B MAC or DME MAC Action  (Rev. 3468, Issued: 02- 18-16, Effective: 12 -02-15, Implementation: 12- 02-15)  The requesting A/B MAC or DME MAC  furnishes the assisting A/B MAC or DME MAC  with sufficient information to identify the issue and perform the necessary resolution actions.  The data shown on the Request for Assistance Form (see Exhibit 1) is needed.  This format must be used when designing a form letter so that both the requesting A/B MAC or DME MAC 's address and the assisting A/B MAC or DME MAC 's address will be visible through a window envelope.  A separate page is used for each request to enable the assisting A/ B MAC or DME MAC  to return each claim as completed instead of holding claims until all claims on a request are completed.  The requesting A/B MAC or DME MAC  enters its request after "The following action is requested."  The requesting A/B MAC or DME MAC  provides claim -identifying information as shown.  The requesting A/B MAC or DME MAC  adds information to help it associate the response with its pending record, if needed.   If a response has not been received within 30 calendar days of the request, the requesting A/ B MAC or DME MAC  sends a follow -up request.  If no response is received within an additional 15 days, follow -up with the RO responsible for the assisting A/B MAC or DME MAC .  A status report indicating and defining problems that prevent processing of the request is considered a response in deciding whether to follow -up with the RO.  In addition, the requesting A/B MAC or DME MAC  considers whether an interim payment  to the provider without CWF approval is appropriate.  (See 60 of this chapter for procedures for paying without CWF approval.)   50.2 - Assisting A/B MAC or DME MAC Action  (Rev. 3468, Issue d: 02 -18-16, Effective: 12 -02-15, Implementation: 12- 02-15)
(Medicare Claims Processing Manual)
50.2 - Assisting A/B MAC or DME MAC Action  (Rev. 3468, Issue d: 02 -18-16, Effective: 12 -02-15, Implementation: 12- 02-15)  Upon receipt of a request for assistance, the assisting A/B MAC or DME MAC  adjusts or cancels the posted bill, as appropriate, and informs the requesting A/B MAC or DME MAC  by annotating the request form (under explanation of action taken by assisting A/B MAC or DME MAC ) with a description of its action (e.g., adjustment cleared CWF (date), current dates of service are __________.)  The assisting A/B MAC or DME MAC  completes corrective actions wit hin 30 calendar days of receiving the request.  If it cannot complete action within 30 days, provide a status reply explaining the reasons on a copy of the request form.  The assisting A/B MAC or DME MAC  sends a copy of the reply to the RO.  The assisting A/B MAC or DME MAC  uses the request form on all correspondence to the requesting A/B MAC or DME MAC  to facilitate association of its response with the pending action.  50.3 - Format for Requesting Assistance From  Another A/B MAC or DME MAC on CWF Edits (Rev. 4009, Issued: 03- 23-18, Effective: 04-23-18, Implementation: 04-23-18)  Exhibit 1 contains the required format for requesting assistance.  The requesting A/B MAC or DME MAC uses that format in designing its form letter so that both its address and the assisting A/B MAC or DME MAC's  address will be visible through a window envelope.  The requesting A/B MAC or DME MAC  completes all data elements. Note that the form is designed so that a standard number 10 - 4 1/8 by 9 1/2 inch window envelope can be used for your request.  The assisting A/B MAC or DME MAC  may refold the form and use the same size window envelope in its reply.  The requesting A/B MAC or DME MAC  enters its address in the bottom address space, and uses the following in the top address space:   A/B Medicare Administrative Contractor or DME MAC (as applicable) or   Name of Contractor PO Box or Street Address City, State, ZIP Code
(Medicare Claims Processing Manual)
A/B Medicare Administrative Contractor or DME MAC (as applicable) or   Name of Contractor PO Box or Street Address City, State, ZIP Code  Exhibit 1 - Request for Assistance     Date ___________      To:  Request:  ___ First     ___ Follow up     ___ RO copy        Date of First Request  _______________     (If Follow up)      We request assistance in resolving CWF reject, edit code _______________________    enter code #   The following action is requested:   IDENTIFYING INFORMATION    ______________________________  ___________________________________  Medicare beneficiary identifier  Beneficiary Name    ______________________________  ______________________________  Your ICN  Your Provider    ______________________________  ______________________________  From Date  Through Date    Explanation of action taken by assisting A/B MAC or DME MAC:     REQUESTOR INFORMATION     __________________________________   Claim #     __________________________________   Dates of Service
(Medicare Claims Processing Manual)
Claim #     __________________________________   Dates of Service    Response Date  __________________________________  ____ Final  Provider  ____ Status  __________________________________   Other  Return To:   Requesting Contractor Name   Address Line 1  __________________________________  Address Line 2  Contact Person and Phone #  Address Line 3 (if needed)    60 - Paying Claims Outside of CWF (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  The CWF approves each claim before it is paid.  However, there may be special circumstances when it is necessary to pay claims outside the CWF/CWF system.  The CMS will notify the A/B MAC or DME MAC of these instances.  They include, but may not be limited to:    New coverage policies are enacted by Congress with effective dates that preclude making the necessary changes to CWF timely; and,    Errors are discovered in CWF that cannot be cor rected timely.  All  A/B MACs and DME MACs  are responsible for reporting CWF problems to their host sites.  60.1 - Requesting to Pay Claims Outside of CWF  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  A/B MACs or DME MACs  may  also request approval from CMS in specific situations to pay claims without CWF approval.  Examples of such situations are:    Other A/B MACs or DME MACs  cannot complete action to remove an impediment that blocks a contractor from processing of a claim; and/or    A systems error cannot be corrected timely, and the provider's cash flow will be seriously endangered.
(Medicare Claims Processing Manual)
 A systems error cannot be corrected timely, and the provider's cash flow will be seriously endangered.    Administrative Law Judge (ALJ) decisions, court decisions, and CMS instructions in particular cases may necessitate that payment be made outside th e normal CWF process.   A/B MACs or DME MACs  shall obtain approval from CMS to pay a claim without CWF approval prior to processing that claim outside the CWF/CWF system.  A/B MACs and DME MACs  shall submit a written request to their CMS Contracting Officer Representative (COR)  for approval to make payment without CWF approval.  Such requests shall be submitted by facsimile transmission or via the Internet.  To ensure the protection of the Personal Health Information (PHI) and Personally Identifiable Information (PII) contained in contractor requests  to pay claims without CWF approval, contractors shall encrypt their E -mail submitted requests.   A/B MACs or DME MACs  shall provide the following information to their CMS COR when requesting to pay a claim without CWF approval:   a) A/B MAC or DME MACs  Internal Claim Control Number,  b) Medicare beneficiary identifier,  c) Beneficiary Name,  d) Provider Number (National Provider Identification (NPI) Number),  e) From and To Date of Service,  f) Procedure Code(s),  g) Total Charges,  h) Amount to be Paid, i) CWF Er ror Code/Condition Preventing Payment (including error code definition), and j) Rationale for Paying the Claim Outside the CWF/CWF System.   60.2 - Procedures for Paying Claims Outside of CWF  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04 -23-18)  Before a claim can be paid outside the CWF/CWF system, A/B MACs or DME MACs  shall obtain approval from their CMS COR, or  his/her designee.  In all instances involving payment outside the CWF/CWF system, A/B MACs or DME MACs  shall  apply the following procedures , unless otherwise specified:
(Medicare Claims Processing Manual)
 Submit the claims with an "X" in the tape -to-tape flag, and the system will determine payment as if the payment were final.  Inpatient PPS payments shall be processed through MCE, Grouper and Pricer.  Hospice payments shall be made using the appropriate hos pice rate.  ESRD visits shall be paid using the composite rate.  The appropriate fee schedules or interim rates shall be used.  Deductible and coinsurance shall be applied based on the most current data available.  Do not apply the CMS -prescribed  percent r eduction applicable to accelerated payment.    Follow shared system procedures to avoid sending a claim to the CWF at time of payment, but shall also maintain a record for later submission.    Pay interest accrued through the date payment is made on clean clai ms.  Do not pay any additional interest.   Maintain a record of payment and implement controls to be sure that duplicate payment is not made (i.e., when the claim record is updated to CWF or in response to a duplicate request by the provider).    Monitor the CWF to determine when the impediment to CWF processing is removed.  Additionally, A/B MACs and DME MACs  shall update the CWF when the impediment is removed so that the actual payment date outside the CWF is shown in the scheduled payment data field.    Consider the claim processed for workload and expenditure reports when it is paid.   60.3  Contractor Monthly Reports of Claims Paid Outside of CWF   (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)
(Medicare Claims Processing Manual)
60.3  Contractor Monthly Reports of Claims Paid Outside of CWF   (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  A/B MACs and DME MACs shall submi t, by the 20th day of the following month, a monthly report of all claims paid without CWF approval to their CMS COR.  A/B MACs and DME MACs shall encrypt reports submitted via the Internet to ensure the protection of the Personal Health Information (PHI) and Personally Identifiable Information (PII) contained in these reports.  The monthly reports of claims paid outside the CWF/ CWF system shall include summary data for each edit code showing claim volume and payment.  The reports shall also identify the c laims and summary edit code volume and payment data as to whether it is a Part A or Part B Service.  The monthly reports shall provide the data listed below for each claim paid without CWF approval for that reporting month:   a) Medicare beneficiary identifier,  b) Beneficiary Name,  c) Provider Number (National Provider Identification Number (NPI),  d) From and to Date of Service,  e) Total Charges,  f) Amount Paid, g) Paid Date, and  h) CWF Error Code/Condition Preventing Payment.  70 - Change Control Procedures (Rev. 4088, Issued: 07- 13-18, Effective: 08 -14-18, Implementation: 08- 14- 18)   The CWF software is changed quarterly to accommodate revised CMS requirements, new provisions of law, to correct errors, or to enhance the system.  A/B MACs and DME MACs may also request changes to CWF through certain change control procedures.   70.1 - MAC Procedure  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  When a MAC has a recommendation for software changes, it follows the change control process below:    Enter change requests into the CWF Information Management System (INFOMAN).     After entering change requests into INFOMAN, submit all supporting documentation to the Host for review and forwarding to both CMS and the CWF Maintenance Contractor (CWFM) for consideration and entry into the Change Control System.    Monitor progress of all changes submitted from your site through INFOMAN.
(Medicare Claims Processing Manual)
 Monitor progress of all changes submitted from your site through INFOMAN.   Review implementation of all changes from your own site to insure that needs a re addressed.   70.2 - Process Flow of a Change Request  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)   Complete a CWF Change Request (CR) through INFOMAN. When the CR is created a CR number will automatically be assigned.    Forward three copies of all supporting documentation to the Host site. Include the CR number on all documentation.  The Host will review it and the CR for accuracy, completeness, and relevance.  The review may also determine whether a problem reported is a CW F problem or a problem with the MAC's software.    When the Host approves the CR, it releases the Change Request to the CWFM and to the CMS central office (CO) in accordance with current procedures.    CMS and the CWFM review the Change Requests as received th roughout the month.   CMS distributes all change requests to the appropriate CMS component for review and approval as they are received.    A monthly Change Control meeting of CMS and CWFM staff is held to schedule approved Change Requests for release.    Following the meeting, the CWFM enters approval and priority status of all Change Requests into the automated system.  As work progresses, the CWFM enters the status of all changes, Quality Assurance (QA) activities and work performed.   70.3 - Handling Eme rgency Problems and Problems With Recent CWF Releases  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  A problem is considered an emergency if a large number of claims are paid incorrectly, cannot be paid, or the MAC/Host system abnormally ends (abends).  When an emergency occurs, the MAC follows these procedures:   1. The MAC will convey information about the emergency to the Host immediately.  The MAC must be able to submit documentation of the problem.   2. The Host wil l report the problem to the CWFM immediately via CWFM customer service.  The service is available 24 hours a day, 7 days a week.   3. During business hours, CWFM will respond immediately.  After business hours, CWFM will contact the Host within one hour of report of the problem.
(Medicare Claims Processing Manual)
3. During business hours, CWFM will respond immediately.  After business hours, CWFM will contact the Host within one hour of report of the problem.   70.4 - Distribution of "CWF Change Control" Reports Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)   CWFM distributes a monthly "Status of CWF Changes" report and "Schedule of CWF Changes" report to all Host  sites, CMS ROs, and CMS CO staff.    Each Host site distributes the reports to its MAC sites within three working days of receipt.   70.5 - Channels of Communication  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)  All MAC inquiries should be made to the Host staff, according to locally established procedures.   70.6 - Schedule of CWF Software Releases  (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18)   Regular Releases  - Scheduled quarterly releases  normally contain changes due to both routine maintenance and new CMS mandates. Other changes included in a regular release shall be in response to issues submitted through the CWF Change Control Process or Sustainability CRs requested by CMS .   Emergency Releases  - Emergency off -quarter releases shall be in response to a critical problem prioritized as a P1 or P2, which causes a delay in processing, or causes claims not to be paid or paid incorrectly. An effective date for an emergency release shall be det ermined in advance by the CMS CWF team.   Generally, an emergency release shall be distributed by the CWFM via telecommunications facilities and installed immediately by the CWF Hosts with the formal approval of CMS. The CWFM shall open a problem into the INFOMAN system for error tracking purposes when the emergency is confirmed. Technical assistance shall include analyzing requirements and debugging programs, data, or file structures that result in operational problems or that interferes with normal operat ional processing. The CWFM shall review, analyze, develop, and document each problem. The CWFM shall group problems according to functionality for the purpose of updating, correcting, modifying, and enhancing the CWF system software .
(Medicare Claims Processing Manual)
 Special Releases  - Special off -quarterly releases shall be provided as needed in response to situations which are of a particular or unusual date dependent nature. These releases shall be provided, for example, in response to a special project approved by CMS that may be of a high priority nature. The CWFM shall not move special releases to production without the permission of CMS. N o less than 24 hours prior to the release moving to production, the CWFM shall send an email to the CMS CWF team requesting approval for implementing the special release. The email shall list all CRs and problem fixes scheduled for implementation.    Priority Releases  - Priority off -quarter releases are scheduled in response to resolve as a follow -up to incomplete or inaccurate changes that are made due to any previous software release. They generally arise from problems in the system that was not evident prior to a relea se being implemented. Priority releases are generally scheduled bi -weekly, except during the final month of each quarter, where minimal changes are permitted. A production release date for a priority release shall be determined in advance by CMS CWF team, the CWFM and implemented with the formal approval of CMS. No less than 24 hours prior to the release moving to production the CWFM shall send an email to the CMS CWF team requesting approval for implementing the priority release. The email shall list all C Rs and problem fixes scheduled for implementation.  80 - Processing Disposition and Error Codes  (Rev. 4088, Issued: 07- 13-18, Effective: 08 -14-18, Implementation: 08- 14- 18)   The results of CWF processing are communicated through a set of codes categorized as either disposition or error codes.  There are specific disposition codes for inquiry, transfer/not in file request, and each claim type.  Claims have consistency, utilizat ion, A/B crossover, and duplicate error codes.   Transactions for End Stage Renal Disease (ESRD), Medicare Secondary Payer (MSP), and Certificate of Medical Necessity (CMN) error codes, as still applicable, are also available.  If the Host rejects a claim, the A/B MAC or DME MAC shall either adjudicate the claim systematically or suspend the claim and review it.  After the review is complete and corrections made, the A/B MAC or DME MAC resubmits the claim with an indication that a review was performed and co rrections made.
(Medicare Claims Processing Manual)
80.1 - Disposition Codes (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18) Each reply record will contain a disposition code that indicates the action taken on the bill by the Host and what action the MACs shoul d take next.   Below are the list of common disposition codes applicable to CWF processing 01  -Approved  03  -Cancel Accepted  04  -Accrete History (Action Code 07 or Entry Code 09) Accepted  50  -Not in file  51  -Not in file on CMS batch system  52  -Master Record housed at another CWF site  53  -Record in CMS alpha match  54  -Matched to Cross -referenced HICN  55  -Does not match master record  56  -MBI/HICN mismatch  60  -I/O Error on database  61  -Cross reference/database problem  AA -Auto Adjust error  AB -Transaction caused CICS ABEND  BO -Beneficiary Other Information (HUBO) edits  CI  -CICS processing problem  CM -Certified Medical Necessity (HUCM) Edits  CR A/B Crossover Reject  ER  -Consistency Edit Reject  EP -Libby Montana (HUEP) project edits  IV -Intravenous Immune Globulin transaction (HUIV) edits  PA -Prior Authorization transaction (HUPA) edits  RD - End Stage Renal (HURD) transaction edits  SP  -Medicare Secondary Payer transaction (HUSP) edits  UR - Utilization Reject  80.2 - Error Codes                                                                                       (Rev. 4009, Issued: 03- 23-18, Effective: 04 -23-18, Implementation: 04- 23-18) The results of CWF error processing is controlled by different set of components. There are specific  error codes for each claim type and maintenance transactions. Claims have a Consistency, Utilization, A/B Crossover, and Duplicate error codes.