oc8f38lb2bdx~notused~CSSC Operations will be closed Monday, January 18, 2021 in observance of the Martin Luther King Jr. holiday. The Front-End Systems (FERAS, PDFS, and EDFES) will be available during this time for RAPS, PDE, Medicare Encounter and Medicare-Medicaid data submissions.~none~_blank~blue~01-12-2021 12:40~01-20-2021 06:00||oc8f38lb2bcc~notused~CSSC Operations will be closed Monday, May 31, 2021 in observance of the Memorial day holiday. The Front-End Systems (FERAS, PDFS, and EDFES) will be available during this time for RAPS, PDE, Medicare Encounter and Medicare-Medicaid data submissions.~none~_blank~blue~05-27-2021 12:40~06-01-2021 06:00||cje8ri2xp9zd~notused~CSSC Operations will be closed Monday, July 5, 2021 in observance of the Independence Day holiday. The Front-End Systems (FERAS, PDFS, and EDFES) will be available during this time for RAPS, PDE, Medicare Encounter and Medicare-Medicaid data submissions.~~_blank~blue~07-01-2021 06:00~07-06-2021 06:00||cje8ri2xp9dd~notused~CSSC Operations will be closed Monday, September 6, 2021 in observance of the Labor Day holiday. The Front-End Systems (FERAS, PDFS, and EDFES) will be available during this time for RAPS, PDE, Medicare Encounter and Medicare-Medicaid data submissions.~~_blank~blue~09-03-2021 06:00~09-07-2021 06:00||3samv18vpxkk~notused~CSSC Operations will be closed Thursday, November 25, 2020 and Friday, November 25, 2020 in observance of the Thanksgiving holiday. The Front-End Systems (FERAS, PDFS, and EDFES) will be available during this time for RAPS, PDE, Medicare Encounter and Medicare-Medicaid data submissions.~none~_blank~blue~11-23-2021 07:00~11-28-2021 07:00||p35y937gpjsx~notused~CSSC Operations will be closed Friday, December 23, 2021 and Monday, December 27, 2021 in observance of the Christmas holiday. The Front-End Systems (FERAS, PDFS, and EDFES) will be available during this time for RAPS, PDE, Medicare Encounter and Medicare-Medicaid data submissions~none~_blank~blue~12-22-2021 07:00~12-28-2021 07:00||vpphkwmwueaa~notused~CSSC Operations will be closed Friday, December 31, 2021 in observance of the New Year's Day holiday. The Front-End Systems (FERAS, PDFS, and EDFES) will be available during this time for RAPS, PDE, Medicare Encounter and Medicare-Medicaid data submissions.~none~_blank~blue~12-28-2021 07:00~01-02-2022 07:00
CMS guidance allows MAOs and other entities, in certain circumstances, to add modifiers to lines within a record to bypass the line-level duplicate check, when each line represents a unique service. Is it acceptable for MAOs and other entities to modify the encounter on the backend for EDPS submission purposes? Or does the billing provider need to rebill with those modifiers?
Encounter and Risk Adjustment Program (Part C)~FAQs
CMS guidance allows MAOs and other entities, in certain circumstances, to add modifiers to lines within a record to bypass the line-level duplicate check, when each line represents a unique service. Is it acceptable for MAOs and other entities to modify the encounter on the backend for EDPS submission purposes? Or does the billing provider need to rebill with those modifiers?
Answer:
Since the Encounter Data Record (EDR) is a report to CMS from the MAO or other entity, and not a provider bill, the MAO or other entity can report data on the EDR that was not submitted by a provider, per CMS guidance. See Tables 1 and 2 below for CMS’ guidance on how to bypass the line-level duplicate check in the back-end Encounter Data Processing System (EDPS) when the MAO or other entity has determined that the lines represent distinct items or services, but will be identified as duplicates by the CMS line-level duplicate logic. The bypass logic described is not intended to be instructions for how providers should bill the MAO or other entity.
MAOs and other entities are permitted to use the CMS-specified procedure code modifiers so that the duplicate logic is bypassed. Another option for preventing a duplicate line rejection is to include the actual payment amount on each line (assuming the actual payment amount for each line differs).
Table 1. EDPS - Data Elements Used to Identify Duplicate Lines (Edit 98325)
Professional/Durable Medical Equipment
Institutional - Outpatient
Beneficiary identifier
Beneficiary identifier
Date of Service
Date of Service
Procedure Code and up to 4 modifiers
Procedure Code and up to 4 modifiers
Paid Amount (2320 AMT02/2430 SVD02)
Paid Amount (2320 AMT02/2430 SVD02)
Billed Amount
Billed Amount
Place of Service (POS)
Type of Bill (TOB)
Rendering Provider NPI
Billing Provider NPI
Revenue Code
Table 2. EDPS - Data Elements Used in Bypass Logic for Edit 98325
Professional/Durable Medical Equipment
Institutional - Outpatient
59 - Distinct Procedural Service
59 - Distinct Procedural Service
76 - Repeat Procedure by Same Physician
62 - Two Surgeons
77 - Repeat Procedure by Another Physician
66 - Surgical Team
91 - Repeat Clinical Diagnostic Laboratory Test
76 - Repeat Procedure by Same Physician
77 - Repeat Procedure by Another Physician
91 - Repeat Clinical Diagnostic Laboratory Test
Note: There is an additional by-pass condition for Ambulatory Surgery Center (ASC) Fee Schedule EDRs: populate the field “Multiple Procedure Discount Indicator” with a value of “1” in order to by-pass the duplicate line edit.
In situations in which none of the data elements included in the Encounter Data System’s (EDS’) duplicate logic check are changing, but other data elements on a line (edit 98325) or record (edit 98300) may have changed, CMS recommends that the subsequent encounter data record be submitted as a replacement or that the previously submitted and accepted encounter data record be voided and a new original record resubmitted in order to prevent rejection for duplicate submission.
Source: CMS HPMS Memo with subject “Guidance for Encounter Data Submission” (October 30, 2017)
The URL you have just viewed was automatically launched for your convenience.