Electronic Data Interchange (EDI) Technical Documents
The Mississippi Division of Medicaid (DOM) is in the process of implementing a new Medicaid Management Information System (MMIS), named MESA: Medicaid Enterprise System Assistance, in collaboration with Gainwell Technologies.
In preparation for go-live, each DOM trading partner must undergo Electronic Data Interchange (EDI) testing to ensure the integrity of electronic transactions. EDI testing will begin in the coming months, and trading partners will need to register to be able to test EDI submissions to MESA.
To help trading partners prepare for testing, DOM Companion Guides are available below, which describe the specific technical and procedural requirements for interfaces between DOM and its trading partners. *These are preliminary Companion Guides and will be updated as details are finalized.
DOM Companion Guides
- 270/271 – Health Care Eligibility Benefit Inquiry and Response Transaction
- 276/277 – Health Care Claim Status Request and Response Transactions
- 278 – Health Care Services Review – Request and Response Transactions – Updated July 14, 2021
- 820 – Payroll Deducted and Other Group Premium Payment for Insurance Products Transaction
- 834 – Benefit Enrollment and Maintenance Transaction – Updated July 7, 2021
- 835 – Health Care Payment/Advice Transaction – Updated July 21, 2021
- 837D – Health Care Claim Dental Transaction – Updated July 21, 2021
- 837I – Health Care Claim Institutional Transaction – Updated July 21, 2021
- 837P – Health Care Claim Professional Transaction – Updated July 21, 2021
- NCPDP – D.0 Claim Billing or Encounter Payer Sheet – Updated July 21, 2021
- NCPDP – D.0 Reversal Payer Sheet – Updated July 21, 2021
Submission of EDI Transactions
EDI Transaction Testing is conducted to verify the integrity of the format, not the integrity of the data. However, to simulate what will happen in production, trading partners will be asked to send live transmission data to a non-production MESA environment. More than one test transmission may be required depending on the number of format errors on a transmission and the relative severity of these errors.
Click on the image below for instructions on how to create transaction.