EDI: Electronic Data Interchange
The Ohio Department of Medicaid (ODM) is providing additional clarification relevant to EDI-related claims submissions on February 1 and later concerning rendering providers. ODM will require one rendering provider per claim at the header level, rather than the detail level, for professional claims for both fee-for-service (FFS) and managed care recipients to ensure claims can be properly priced and paid. Examples of claims submissions with the rendering practitioner are as follows:
- A client receives one service during the visit. The rendering practitioner’s NPI is recorded in the header field on the claim. The service is recorded at the detail level on the claim without the rendering practitioner’s NPI.
- A client receives multiple services from the same rendering practitioner during the visit. The rendering practitioner’s NPI is recorded in the header field on the claim. Each service is recorded at a separate detail level without a rendering practitioner NPI.
- The client receives multiple services, each from a different rendering practitioner during the visit. The billing provider must create separate claims for each service provided by each rendering practitioner during the visit. Each claim must record the rendering practitioner NPI at the header level on each claim, and the service they rendered to the client is recorded at the detail level.
There is one exception to this rule for services provided by FFS Federally Qualified Health Centers (FQHC) and Rural Health Clinics (RHC) providers.
FQHC/RHC claims submitted to ODM for payment may include multiple rendering providers at the detail level because ODM pays FQHC/RHC providers based on an encounter. In these specific scenarios, multiple rendering providers on a claim will not cause a pricing/paying issue because the rendering providers are not utilized in determining payment for FFS FQHC/RHC wraparound claims. For additional guidance related to FQHC/RHC providers, please review the Medicaid Advisory Letter located here: Medicaid Advisory Letter 622.
As part of the Next Generation of Ohio Medicaid program, we are taking a hands-on approach to resolving Electronic Data Interchange (EDI) implementation issues that trading partners have experienced.
As we move into Certification Testing (CERT) and are preparing for production, the level of security required to interact with these systems is increasing. Trading partners leveraging the EDI Trading Partner Management Application will be required to:
- Obtain a State of Ohio ID (OH|ID)
- Establish Multi-Factor Authentication (MFA) via the State’s InnovateOhio Platform (IOP).
The additional security aims to improve user connectivity and to prevent hacking and the inadvertent exposure of sensitive data. To keep information secure, the EDI trading partner management application can only be accessed by logging in with OH|ID credentials and successfully completing the MFA setup. The MFA process is well documented, and many providers already use it in production within other state systems.
Please complete the following steps:
- As soon as possible, but no later than Thursday, January 12: Review the attached OH|ID/MFA guide and the complete the steps within.
- After successfully completing the OH|ID and MFA setup activities: Review the trading partner management application user guide and the functionalities offered in the tool.
Thank you for your participation so far. We especially appreciate your willingness to help us test and troubleshoot new parts of the Ohio Medicaid Enterprise System (OMES).
If you have any questions or feedback, please do not hesitate to reach out to usomesedisupport@deloitte.com.
From ODM: November 3, 2022
On February 1, 2023, the Ohio Department of Medicaid (ODM) will implement the new Electronic Data Interchange (EDI) module as part of the Next Generation program. The new EDI vendor is Deloitte. The EDI will be the exchange point for trading partners on all claims-related activities. Buckeye Health Plan providers are expected to educate and prepare their trading partners for the February 1 launch. To assist in preparations, ODM compiled a list of important changes to keep in mind.
Important changes for all EDI claims
With the launch of the new EDI vendor, Deloitte, changes in claim submission will be required for the trading partners to exchange transactions in the new EDI. Please note that MyCare is not included in the Next Generation program and will continue to be submitted using the current processes. Key changes are as follows:
- Billing providers must be enrolled with ODM as a provider type who is permitted to be a billing provider and be paid for services. Non-billing provider types must be affiliated with the billing provider on the claim. Claims without appropriate affiliation will be rejected on an 824 transaction.
- Dates of service after February 1 must be submitted through the new EDI vendor.
- Fee-for-service (FFS) claims may only include one Rendering Provider per claim. Different rendering providers at the detail are no longer acceptable for FFS claims.
- Each claim must include the internal managed care payer ID listed in the ODM Companion guides so the managed care entity (MCE) can route claims appropriately within their systems.
- Each claim must also use the 12-digit, ODM-assigned member ID even if one of the MCEs is the destination payer.
- Separate files must be submitted using the Receiver ID assigned by ODM for each plan, e.g., a CareSource Payer file can only contain claims for members covered by CareSource.
- Please see the companion guides for a list of Receiver IDs.
- Providers who wish to receive an 835 Electronic Remittance Advice (ERA) must use the ODM-06306 835 Designation form to choose the ODM-authorized trading partner to receive the 835 on their behalf. Providers who are already enrolled for the 835 with ODM do not need to re-enroll. Please note that this enrollment will also direct all 835s from the Medicaid managed care plans.
- Upon claim submission, EDI will validate code sets. Claims with invalid codes will be rejected with an 824 transaction.
- Deloitte EDI will provide an attachment+control file option for trading partners who do not have the EDI 275 attachment transaction built yet.
- Billing providers must be enrolled with ODM as a provider type who is permitted to be a billing provider and be paid for services. Non-billing provider types must be affiliated with the billing provider on the claim. Claims without appropriate affiliation will be rejected on an 824 transaction.
Important changes for all EDI prior authorizations
Beginning February 1, 2023, all prior authorizations (PA) for FFS must be entered via the Provider Network Management (PNM) module. MyCare prior authorizations will continue to be submitted using the current processes. Prior authorizations for members covered by the managed care entities can be submitted either using the PNM module or by using the EDI 278 transaction in the new EDI.
Additionally, attachments that are submitted to the new EDI to support PAs and forwarded to the MCE must use the attachment+control file option. Deloitte EDI will provide an attachment+control file option for trading partners who do not have the EDI 275 attachment transaction built yet.
Information about the PNM module
For awareness, when the new EDI launches, providers will still have the option to direct data enter (DDE) their claims. DDE will be accessible to providers via the PNM on February 1, 2023. More information regarding the PNM can be found on the Ohio Medicaid Managed Care PNM & Centralized Credentialing webpage.
As we approach the February 1, 2023, launch, trading partners will need to work with their providers to determine the specific changes that may be needed to their systems and staff training. We hope this information will help in educating and preparing your providers. More informatoion can be found on the Ohio Medicaid Enterprise System website.
EDI Support