(A) For purposes of this rule, the following definitions apply:
(1) "Covered entity," as defined by 45 C.F.R. 160.103 (rev. 2/2006), is a health plan, a health care clearinghouse, or a health care provider that transmits health care information in an electronic format in connection with a transaction covered by this rule. The following definitions apply:
(a) "Health plan" is an individual or group health plan that provides, or pays the cost of medical care.
(b) "Health care clearinghouse" is a public or private entity, including a billing service, repricing company, community health management information system or community health information system, and value-added networks and switches, that does either of the following functions:
(i) Processes or facilitates the processing of health information received from another entity in a nonstandard format or containing nonstandard data content into standard data elements or a standard transaction; or
(ii) Receives a standard transaction from another entity and processes or facilitates the processing of health information into a nonstandard format or nonstandard data content for the receiving entity.
(c) "Health care provider" is a provider of medical or health services, and any person or organization who furnishes, bills for, or is paid for health care services in the normal course of business.
(2) "Electronic data interchange (EDI) transactions" are transactions developed by standards development organizations recognized by the federal centers for medicare and medicaid services (CMS) and adopted by the Ohio department of job and family services (ODJFS). The different EDI transactions are defined as follows:
(a) "ANSI X12 820 premium payment" is a transaction used to make a payment and/or send a remittance advice.
(b) "ANSI X12 834 monthly member roster or enrollment/disenrollment in a health plan" is a transaction used to establish communication between the sponsor of the insurance product and the payer.
(c) "ANSI X12 835 health care claims payment/remittance advice" is a transaction used to make a payment and/or send an explanation of benefits remittance advice.
(d) "ANSI X12 837 health care claim" is a transaction used to submit health care claim billing/encounter information, or both, from providers (institutional, professional, or dental) of health care services to payers, either directly or via clearinghouses.
(e) "ANSI X12 270 eligibility, coverage, or benefit inquiry" is a transaction used to inquire about the eligibility, benefits or coverage under a subscriber's health care policy.
(f) "ANSI X12 271 eligibility, coverage, or benefit information response" is a transaction used to communicate information about, or changes to, eligibility, benefits, and/or coverage.
(g) "ANSI X12 276 health care claim status request" is a transaction used to request the status of a health care claim.
(h) "ANSI X12 277 health care claim status notification" is a transaction used to respond to a request regarding the status of a health care claim.
(i) "ANSI X12 278 health care services review information request and response" is a transaction used to transmit health care service information for the purpose of referral, certification/authorization, notification, or reporting the outcome of a health care services review.
(3) "Trading partner" is a covered entity that submits, receives, routes, and/or translates EDI transactions directly related to the administration or provision of medical assistance provided under a public assistance program.
(B) Trading partners submitting EDI transactions.
(1) Trading partners must meet the definition of a covered entity and be a health plan, a healthcare clearinghouse or a health care provider.
(2) To enroll as a medicaid EDI trading partner with ODJFS under the Health Insurance Portability and Accountability Act (HIPAA) of 1996, and be issued a trading partner number, a covered entity must complete the following:
(a) The JFS 01957 "Trading Partner Profile" form (rev. 5/2006).
(b) The JFS 06306 "Designation of an 835 or 834-820 Trading Partner" form (rev. 12/2006). This form is required only if the trading partner will be receiving the 835 remittance advice on behalf of its clients.
(c) A trading partner agreement. Two original trading partner agreements must be signed by an authorized representative of the trading partner and submitted to ODJFS. A countersigned original will be returned to the trading partner and must be kept on file.
(3) Once the medicaid trading partner number is assigned, the trading partner is eligible to submit claims for the testing process in accordance with paragraph (C) of this rule.
(C) Testing requirements.
(1) To become an active trading partner with ODJFS, all trading partners must abide by all ODJFS testing requirements as outlined in this paragraph and in the "Electronic Data Interchange Trading Partner Information Guide." The "Electronic Data Interchange Trading Partner Information Guide" is available athttp://jfs.ohio.gov/OHP/tradingpartners/pdfs/EDITradingPartnerInformationGuide.pdf (rev. 1/2011).
(a) Trading partners are required to submit three files per the following transaction types that must pass testing: 837 (professional, institutional and dental), 270 (eligibility) and 276 (claim status inquiry).
(b) Trading partners must test the transaction types that they will be submitting in production.
(c) Each file must contain a minimum of fifty claims.
(d) All EDI files must completely pass X12 integrity testing, HIPAA syntax, and HIPAA situation testing. Trading partners are required to modify their EDI files in accordance with any new federally mandated HIPAA standards.
(e) During testing, trading partners may submit one claim file per day, per transaction (one professional, one institutional, and one dental) and/or one eligibility inquiry and/or one claim status inquiry per day.
(f) Test files are considered passing when ninety per cent of the claims submitted pass the test adjudication process. A ninety per cent pass rate must be reached for each transaction type tested.
(D) Trading partners that are not actively submitting and receiving 837 health care claim transaction sets may not submit and receive 270/271 and 276/277 transaction sets.
Replaces: 5101:3-1- 20.1, 5101:3-1- 20.2
R.C. 119.032 review dates: 11/01/2016
Promulgated Under: 119.03
Statutory Authority: 5111.02
Rule Amplifies: 5111.01 , 5111.02
Prior Effective Dates: 10/16/03 (Emer), 1/1/04, 11/15/04, 5/23/07