Set up claim options, Medical Necessity tab

Menu location: Maintenance menu, System Administration, Claim Options, Medical Necessity tab

Medical Necessity is a safety tool that warns you about claims that contain code pairs that the Medicare LMRP has ruled are not medically necessary and thus will not be paid. During validation, the Medical Necessity Edit (MNEdit) compares procedure codes to diagnosis codes and checks them against the LMRP Medical Necessity rules. If the rules state that a procedure will be disallowed because it is not medically necessary for any diagnosis on the claim, an MNEdit error is placed on the offending code.

By default, this product will run Medical Necessity edits and display any errors in red just like other payer-specific errors. When these edits are suppressed in the main tab, the function is essentially disabled, and no edits are performed. Use the configuration features in this tab to set up partial suppression of MN checking, apply MN checks to other claims, or to change the severity level of a policy under review:

  • Use the General configuration to suppress MN edits based on claim content such as the presence of certain revenue codes and procedure codes.
  • Use the Payer Selection configuration to apply MN edits to other types of claims based on the line of business or payer.
  • Use the Policy Selection configuration to set a Medical Necessity policy to a warning for review purposes.
Note

Changes to Medical Necessity edits require 30 minutes to take effect. Claims validated before that time elapses will not use the updated Medical Necessity edits.

How MN suppression works

When MN Edit runs, it first checks to see if global suppression is in place (completely disabled from the Main tab). If completely disabled, MN checking stops there. No edits are made on any claims. If MN Edit is not globally suppressed, the function checks to see if general suppression rules are configured based on revenue codes, occurrence codes, condition codes, or other suppression rules. With general configuration, when MN checking encounters an exception code or set of codes, it will not add the error that is triggered by that code or code set to the claim. All other MN errors will be placed on the claim.

General MN configuration

Items entered under this configuration apply to all payers that are enabled for MN Edit.

Field suppression

These settings are useful for when you want to run the Medical Necessity edits on your claims with a few exceptions, depending on the billing situation. You can set up either Claim Level or Service Line Level exceptions.

Claim level

The system will skip running MN edits whenever any of the entered revenue codes, occurrence codes, condition codes, financial class entries, or bill types are present on a claim. Separate multiple values with commas. If MN finds even one of the entered codes, the system will not place MN errors on the claim.

Service line level

Use this group of fields to suppress MN edits on a n individual service line of a claim. If the system finds any one of the codes entered on a service line, it will not place an error on that service line. However, other MN errors are added to the claim as applicable.

The Service Line Charge list applies to both institutional and professional claims. To suppress MN edits on service lines that do not contain charges, select one of these options:

  • SL_TOT = 0
    If the service line value equals $0, the system skips MN edits for the service line.
  • SL_TOT = SL_NCC
    If the service line value is equal to the service line non-covered charge, the system skips MN edits for the service line.

Code set suppression

Use this section if you need the system to skip MN edits on the service line of an institutional claim that contains a specific combination of procedure codes and revenue codes. The section begins with a list of the revenue/procedure code sets that have already been established. Below the list, use the two entry fields to add or change sets.

  • To change an existing code set, select the entry. Change the codes, and click Update to hold your change. Click OK to save your work.
  • To remove an existing code set, select the entry. Click Remove. Click OK to save your work.
  • To add a new code set, type the combination of Revenue Code(s) and Procedure Code(s) that should trigger the suppression of MN edits on the service line. You can enter multiple codes or ranges of codes. Click Add to hold your work, and click OK to save it.
Caution

If you create a code set, it will be applied to all LOBs.

Payer selection configuration

Use these configuration settings to add MN edits to claims for another LOB or payer. These settings are not suppression settings. You can also select the fiscal intermediary (FI) content you need for running the MN edits on the applicable claims.

Follow these steps to set up a MN Edits for another LOB or payer:

  1. Click Professional or Institutional in Form Type. This action populates the LOB or Payer fields and FI Data Content Selection list.
  2. Click the LOB, Payer, or Alias radio button. Then click on the entry you need.
  3. Click on an entry for the FI Data Content Selection to determine which MN edits to use for the payer or LOB claims.
  4. Click Add. Repeat steps 1-4 add other payers/LOBs.
  5. Click OK to save the settings.

When reviewing the list of your MN Edit Custom Settings, if the FI Data Content column lists "unknown," then the payer was removed from the FI list.

Policy selection configuration

Use the Policy Selection configuration to set a MN policy severity level to a warning. While this action does not change Medicare's LMRP rules for medical necessity, it does allow you to release claims to the payer while reviewing the requirements for a specific policy. Remember to reset the warnings to errors after completing research to ensure claims are reviewed appropriately. Follow these steps to set a policy as a warning:

  1. Use the search fields to locate the policy. Type all or part of the policy in the Description field, and/or select the current Severity level. Then, click Search.
  2. Select the Severity drop-down field in the table of listings to switch between the default Error setting and the Warning setting.
  3. Click OK to save any changed settings.

Use the Clear button to empty and reset the Description field for a new Search.

Filtering for MN edits

The user-selectable field list in Claim Filter allows you to locate claims to which MN errors have been added:

  • Select Edit Error and type MNError to locate edits on any claim form.
  • Select Edit Error and type MNLmtd to locate procedures for which there is only limited coverage.
  • Select Edit Error and type MNDocRqd to locate procedure codes for which Medicare requires extra documentation.
  • To locate all types of Medical Necessity errors on UB claims, select Edit Error and type MN
Notes
  • See suppression tips for allowed wildcards and other entries.
  • In the Payer Selection area, use an asterisk (*) in the FI DATA CONTENT SELECTION field to search only for non-Medicare FIs.
  • In the Policy Selection area, you can click the Policy ID value to open the referenced policy in a new window.
  • Request the Claim Options Maintenance Setup system report to create a printed copy of your settings. (The Policy Selection settings and the two most recent fields added for claim-level suppression are not yet available in this report.)
  • Remember, you can override any Medical Necessity error on an individual basis, if needed.